EP2839622B1 - Method, device, network entity and computer program product for providing an ip service application - Google Patents

Method, device, network entity and computer program product for providing an ip service application Download PDF

Info

Publication number
EP2839622B1
EP2839622B1 EP12721000.3A EP12721000A EP2839622B1 EP 2839622 B1 EP2839622 B1 EP 2839622B1 EP 12721000 A EP12721000 A EP 12721000A EP 2839622 B1 EP2839622 B1 EP 2839622B1
Authority
EP
European Patent Office
Prior art keywords
dns
service
subscriber
network
multimedia
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
EP12721000.3A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2839622A1 (en
Inventor
Rogier August Caspar Joseph Noldus
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP2839622A1 publication Critical patent/EP2839622A1/en
Application granted granted Critical
Publication of EP2839622B1 publication Critical patent/EP2839622B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • 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/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/256—NAT traversal
    • H04L61/2575—NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
    • 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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1059—End-user terminal functionalities specially adapted for real-time communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H04M3/2254—Arrangements for supervision, monitoring or testing in networks
    • H04M3/2263—Network management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/30—Types of network names
    • H04L2101/35—Types of network names containing special prefixes
    • 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/4588—Network directories; Name-to-address mapping containing mobile subscriber information, e.g. home subscriber server [HSS]

Definitions

  • the invention relates to Internet Protocol multimedia networks.
  • the invention also relates to subscriber's multimedia devices.
  • IP Internet Protocol
  • IP based communications over an IP network IP services are provided to subscribers.
  • the subscriber's terminals are multimedia terminals, e.g. multimedia phones
  • multimedia services e.g. relate to multimedia components provided as enhancement for voice over IP communication.
  • multimedia components such as video sharing, still picture sharing, music sharing, calendar sharing, file transfer etc. This is sometimes referred to as 'Enriched communication'.
  • IMS IP Multimedia Subsystems
  • Calling party and called party may during establishment of the call exchange their respective capability for such IP based multimedia enhancement to the call. This capability includes, among others, an IP address to be used for the communication.
  • IP Internet Protocol
  • IMS IP Multimedia Subsystem
  • Session Initiation Protocol SIP
  • SIP Session Initiation Protocol
  • the SIP terminal deposits its contact address, viz. IP address, at a registrar, in an IMS network formed by a Serving Call Session Control Function (S-CSCF) entity.
  • S-CSCF Serving Call Session Control Function
  • This IP address is used for establishing a SIP session.
  • the terminal hence executes a SIP service application, in the sense that it can receive an initial SIP transaction.
  • Receiving the initial SIP transaction constitutes a request for the execution of an IP service, such as establishing a communication session or accepting an Instant message.
  • IP based communication services such as a hypertext transfer protocol (HTTP) service, a Mail server, or a File Transfer Protocol (FTP) service.
  • HTTP hypertext transfer protocol
  • Mail server a Mail server
  • FTP File Transfer Protocol
  • International patent application WO2011/097179 relates to a method, apparatus, and system for discovering devices on a local area network, wherein the method comprises sending a DNS request from a host networking element, receiving the DNS request at one or more devices, and responding to the host networking element with one or more DNS responses.
  • International patent application WO 2011/046348 relates to a method for allowing a mobile terminated communication to a destination device through at least one mobile communication network from a source entity located in a public IP address network.
  • a method for providing at least one IP service application from a subscriber's multimedia device in an IP multimedia network comprises the step of executing at least one IP service application on the device and/or on an auxiliary device associated with the device. Further, a Domain Name System (DNS) service is provided being executed on the device. The DNS service relates to a domain associated with the subscriber. The DNS service has a memory associated therewith. Further, information relating to DNS resource records in accordance with, i.e. needed for accessing, the at least one IP service application that is being executed on the device and/or in the auxiliary device is stored in the memory at that moment. Further, an indication of the device's capability to execute a DNS service comprising a network address on which the DNS service can be reached for a DNS query is deposited with the IP multimedia network.
  • DNS Domain Name System
  • the subscriber's multimedia device that executes the DNS service, i.e. the device takes the role of DNS server for the domain related to the user of that device.
  • the device since it is the subscriber's multimedia device where IP service applications are dynamically installed and removed, activated and de-activated, with an IP address(es) that will differ over time. Therefore it is the device that is best equipped to provide information about available IP service applications on that device.
  • the device can be mobile or fixed.
  • the auxiliary device cab be mobile or fixed.
  • the device can be a human operated device, such as a subscriber's terminal, or a non-human operated device.
  • the aspect that the indication of the device's capability to execute a DNS service comprises a network address on which the DNS service can be reached for a DNS query provides the advantage that the IP multimedia network with which this indication is deposited is aware of the network address on which the DNS service can be reached. Hence, a DNS query for the domain associated with the subscriber can efficiently be forwarded to the DNS service being executed on the subscriber's multimedia device.
  • the indication is deposited with the IP multimedia network during registration. Depositing this indication with the IP network during registration provides the advantage that the indication is deposited with the IP multimedia network at a moment that the device is already supposed to deposit information with the network.
  • the information relating to DNS resource records in accordance with the at least one IP service application that is being executed on the device and/or in the auxiliary device includes information required for accessing the IP service application, such as an IP address at which the IP service application can be accessed.
  • the information provides information as to where to access the IP service application.
  • the DNS service is executed in a DNS server on the multimedia device.
  • the device can be provided with a dedicated hardware unit for performing the desired DNS server functionality.
  • the IP multimedia network is an IMS network.
  • the method includes routing a DNS query destined for the DNS service executed on the multimedia device to an authoritative DNS name server for the domain associated with a group of users.
  • the device is associated with a member of said group of users.
  • the DNS name server is configured to forward all DNS queries destined for a sub-domain of that domain to the Home Subscriber Server, HSS, of the IMS operator serving users associated with the domain.
  • HSS is acting as authoritative name server for the DNS service(s) executed on the multimedia device(s) of the user(s) associated with the sub-domain of that domain, which provides the advantage that DNS iterative query forwarding can be used.
  • the invention also relates to a subscriber's device being a multimedia device for an IP multimedia network.
  • the device or an auxiliary device communicatively connectable to the device, comprises a processing unit arranged for executing at least one IP service application.
  • the device further includes a DNS query receiver for receiving a DNS query.
  • the device further includes a requesting unit for requesting an identifier of the at least one IP service application.
  • the identifier can include a network address at which the at least one IP service application is accessible.
  • the device comprises the processing unit arranged for executing a DNS service and a memory arranged for storing information relating to DNS resource records in accordance with IP service applications that are being executed on the device at that moment.
  • the device further includes a depositing unit arranged for depositing, e.g. during registration, with the multimedia network, an indication of the device's capability to execute the DNS service.
  • the indication includes a network address on which the DNS service can be reached for a DNS query.
  • the invention also relates to an IP multimedia network including a multimedia device, or a combination of a multimedia device and an auxiliary device, and a network entity, wherein the network entity is arranged for storing the indication of the device's capability to execute a DNS service.
  • the network entity acts as authoritative name server for a domain including a plurality of sub-domains, each sub-domain being associated with a subscriber's public address, each subscriber being associated with a subscriber device.
  • the invention also relates to a network entity, such as an HSS, for an Internet Protocol, IP, multimedia network, wherein the network entity is arranged for receiving and storing an indication of a device's capability to execute a DNS service, the network entity acting as authoritative name server for a domain including a plurality of sub-domains, each sub-domain being associated with a subscriber's public address, each subscriber being associated with a subscriber device.
  • a network entity such as an HSS, for an Internet Protocol, IP, multimedia network
  • IP Internet Protocol
  • multimedia network wherein the network entity is arranged for receiving and storing an indication of a device's capability to execute a DNS service, the network entity acting as authoritative name server for a domain including a plurality of sub-domains, each sub-domain being associated with a subscriber's public address, each subscriber being associated with a subscriber device.
  • the invention also relates to a computer program product executable on a programmable subscriber's multimedia device.
  • the computer program product includes software code portions arranged for performing, when run on a programmable subscriber's Multimedia device, the following steps. Determining the presence of at least one IP service application that is being executed on the device and/or on an auxiliary device associated with the device at that moment. Providing on the device a DNS service relating to a domain associated with the subscriber.
  • the DNS service has a memory, e.g. of the device, associated therewith. Storing in the memory information relating to DNS resource records in accordance with, i.e. needed for accessing, the at least one IP service application that is being executed on the device and/or in the auxiliary device at that moment. Instructing the device to deposit, with a multimedia network with which the device is registered or requests to be registered, an indication of the device's capability to execute a DNS service. The indication comprises a network address on which the DNS service can be reached for a DNS query.
  • Providing the computer program product provides the advantage that the above described method can be executed on a programmable subscriber's multimedia device in the form of a computer program product, such as a software application.
  • the computer program product can be stored on a data carrier, or be provided over carrier waves such as the internet.
  • IP Internet Protocol
  • IMS IP Multimedia Subsystem
  • the SIP terminal deposits its contact address, an IP address, at a registrar.
  • this registrar is a Serving Call Session Control function (S-CSCF) entity.
  • S-CSCF Serving Call Session Control function
  • This contact address is used for establishing a SIP session with the SIP terminal.
  • the terminal hence acts as a SIP server, in the sense that it can receive an initial SIP transaction.
  • Receiving an initial SIP transaction constitutes a request for the execution of an IP service application, such as establishing a communication session or accepting an Instant message.
  • IP based communication services it is not possible to establish an IP service towards an IMS terminal outside the context of an existing SIP communication session.
  • IP based communication services there is no general mechanism for a subscriber's multimedia terminal, such as the IMS terminal, to offer IP based services such as a hypertext transfer protocol (HTTP) service, a Mail service, or a File Transfer Protocol (FTP) service.
  • HTTP hypertext transfer protocol
  • Mail a Mail service
  • FTP File Transfer Protocol
  • FIG 1 shows an example of a prior art IMS network 101.
  • the network contains a User Equipment (UE) 102 associated with an IMS subscriber with public user identity sip:john.smith@my-company.nl.
  • the subscriber John Smith is an enterprise subscriber, associated with the enterprise 'My Company', the domain name of which is 'my-company.nl'.
  • UE User Equipment
  • the network 101 in Figure 1 further includes an IP Connectivity Access Network (IP-CAN) 4, a registrar 6, here an S-CSCF entity 6, a Home Subscriber Server (HSS) 8, an Interrogating Call Session Control Function (I-CSCF) entity 10, an Interconnect Border Control Function (IBCF) entity 12, and a Domain Name System (DNS) server 14.
  • IP-CAN IP Connectivity Access Network
  • HSS Home Subscriber Server
  • I-CSCF Interrogating Call Session Control Function
  • IBCF Interconnect Border Control Function
  • DNS Domain Name System
  • the subscriber's IMS terminal 102 When the subscriber's IMS terminal 102 registers in the IMS network 101, it deposits its SIP binding in the registrar 6, i.e. in an S-CSCF entity 6 of the IMS network 101 the subscriber belongs to, as shown in Figure 2 .
  • a P-CSCF entity 5 forms part of the visited IMS network.
  • the S-CSCF entity 6 forms part of the home IMS network.
  • the I-CSCF entity 10 and HSS 8 are not shown in Figure 2 but can be seen in Figure 1 .
  • the terminal 102 has the role of a SIP server. This is depicted in Figure 3 . Again, the I-CSCF entity 10 and HSS 8 are not shown (refer to Figure 1 ).
  • FIG. 3 represents the registrar functionality 7 in the S-CSCF entity 6.
  • Figure 1 shows a SIP client 16 associated with a second subscriber (other party). For sending an initial SIP request to the subscriber's terminal 102, the subscriber's public identity is used. The SIP client 16 does not need to have any knowledge about the access network currently in use by the subscriber's terminal 102 and the IP address of the terminal 102.
  • the user from whom the SIP service is requested is identified as:
  • a three-step forwarding of the SIP request is specific for SIP services. It facilitates the establishment of a SIP service towards the IMS subscriber's terminal 102.
  • Each step of the three-step forwarding is based on a database containing static or dynamic data. Three relationships are used for extending an initial request for the establishment of a multimedia communication session (e.g. an Invite), or a non-session related request (e.g. a Message), to the terminal 102 currently in use by the subscriber.
  • a multimedia communication session e.g. an Invite
  • a non-session related request e.g. a Message
  • a DNS query with the DNS server 14 is used for extending the Invite from the SIP client 16 initiating the SIP session, towards the IMS network serving any subscriber ( ⁇ user>@my-company.nl) within the domain my-company.nl.
  • DNS constitutes the global DNS infrastructure and encompasses both external DNS and internal DNS. This DNS based routing of the Invite is based on static DNS configuration.
  • an HSS 8 query by the I-CSCF entity 10 is used for extending the Invite to the registrar, S-CSCF, 6 currently serving the subscriber john.smith@my-company.nl.
  • the data used for this extending is dynamic data, contained in the HSS 8 and is updated when the subscriber de-registers or when another S-CSCF entity 6 is assigned to the subscriber john.smith@my-company.nl.
  • a SIP contact binding is used for extending the Invite for the subscriber john.smith@my-company.nl to one or more of the terminals 102 currently registered by the subscriber John Smith.
  • This contact binding information is dynamic; it is updated when, for example, the terminal 102 changes IP access.
  • the subscriber John Smith is now ready to receive SIP session establishment requests (e.g. a SIP Invite) or non-session related SIP transaction requests (e.g. a SIP Message), as described.
  • SIP session establishment requests e.g. a SIP Invite
  • non-session related SIP transaction requests e.g. a SIP Message
  • the inventor has realised that the subscriber, in addition to the possibilities provided in the prior art network 101, would benefit from the possibility to offer additional IP services from his multimedia terminal, which IP services are accessible to third parties.
  • the inventor has realised that the subscriber e.g. wants to offer a (restricted) publicly available hypertext transfer protocol (HTTP) service from his mobile or fixed terminal.
  • HTTP hypertext transfer protocol
  • Such HTTP service could be accessible through the Uniform Resource Locator (URL) john.smith.my-company.nl.
  • URL Uniform Resource Locator
  • the subscriber would like to offer a File Transfer Protocol (FTP) service from his terminal. This FTP service could also be accessible through the URL john.smith.my-company.nl.
  • FTP File Transfer Protocol
  • a subscriber's multimedia device can be a human-operated device or a non-human operated device.
  • the subscriber's multimedia device can for instance be a subscriber's multimedia terminal or a subscriber's device in a machine-to-machine communication situation.
  • FIG 4 shows an example of a part of an IP multimedia network 1 according to the invention.
  • the network 1 includes a subscriber's multimedia device 2. It will be appreciated that the IP multimedia network 1 is similar to the prior art multimedia network 101 shown in Figure 1 , the main difference being in the functionality of the multimedia device 2 and terminal 102. Reference is also made to Figure 5 which shows a schematic representation of the multimedia device 2, and to Figure 6 which shows a flow chart which includes steps of the working of the network 1 as explained with respect to Figure 4 .
  • the subscriber has three IP service applications active 202 and operational on his (mobile) multimedia device 2.
  • the first IP service application is a SIP user agent 18, which is used for establishing and receiving SIP sessions or SIP stand-alone requests. This SIP user agent 18 is activated upon IMS registration. This SIP user agent 18 is accessed through the IMS network, e.g. via a P-CSCF entity and an S-CSCF as is known in the art.
  • the second IP service application is an FTP service application 20B, which can be activated any time when needed. This FTP service application 20B is accessed through the IP access network 4 used by the subscriber associated with the multimedia device 2.
  • the third IP service application is an HTTP service application 20A, which can be activated any time when needed. This HTTP service application 20A is accessed through the IP access network 4 used by the subscriber associated with the multimedia device 2.
  • the domain john.smith.my-company.nl associated with the subscriber John Smith is contained in DNS.
  • the (public) DNS name server 14 authoritative for this domain is then configured with DNS resource records that are needed (i.e. need to be obtained by the DNS resolver in the IP service client 16) for accessing IP service applications in the subscriber's IMS device 2.
  • the problem with such static configuration is that such DNS name server 14 configuration is static, whereas the IP address of the device 2 of the subscriber is dynamic.
  • the subscriber can have one or multiple IP service applications deployed on his multimedia device 2. The subscriber can activate and deactivate the IP service applications on his device 2 as and when required.
  • IETF RFC 2136 Dynamic Updates in the Domain Name System (DNS UPDATE)
  • DNS UPDATE Dynamic Updates in the Domain Name System
  • IETF RFC 2136 specifies a protocol by means of which an entity can update DNS Resource Records in a DNS server. The update of these Resource Records is static. This confirms the problems that are mentioned above, namely that the subscriber has to frequently update the (public) DNS server. Such update is required every time the subscriber acquires a new IP address for the device 2, every time the subscriber activates or de-activates an IP service application on his device 2, and every time the subscriber adds or removes an IP service application on his device 2.
  • DNS queries for the domain related to the subscriber i.e. the domain john.smith.my-company.nl, are forwarded 222, 224, 226 to the subscriber's device 2.
  • the subscriber's device 2 is arranged to execute thereon a DNS service 22 relating to the domain associated with the subscriber.
  • the subscriber's device 2 also stores 206 information relating to DNS resource records needed for accessing the IP service applications 20A, 20B that are being executed on the device 2 at that moment.
  • the subscriber's multimedia device 2 that executes 204 the DNS service 22, i.e. the device 2 takes the role of DNS server 22' for the domain related to the user of that device 2. Since it is the subscriber's multimedia device 2 where IP service applications 20A, 20B are dynamically installed and removed, activated and de-activated, with an IP address(es) that will differ over time, it is the device 2 that is best equipped to provide information about available IP service applications 20A, 20B on that device 2.
  • the device 2 will during registration also deposit 212 an indication of its capability to execute the DNS service.
  • the device 2 deposits a 'DNS Server binding' in the IMS network 1. This is depicted in Figure 7 .
  • the contact binding for SIP services is deposited in the S-CSCF entity 6 in accordance with IMS specification, which is therefore not further described.
  • the dashed line 112 symbolizes the depositing of the contact address for SIP services for this public user identity into the registrar 6.
  • the dashed line 312 symbolizes the depositing of the contact address for DNS services for this public user identity, into HSS 8.
  • An indication of the device's capability to execute the DNS service is included in the (protected) SIP Register message 213 and is deposited in HSS 8. This indication is included in the Diameter server assignment request, SAR, 215 sent 216 from the S-CSCF 6 to the HSS 8. Diameter SAR can, according to the IMS standard, carry a copy of the complete SIP Register message, including this indication of the device's capability to execute the DNS service. The validity, over time, of this indication is aligned with the IMS registration of the device 2. When the IMS registration of this device 2 expires or when the device de-registers, the indication of the device's capability to execute the DNS service is purged. Hence, the HSS 8 received an indication of the device's capability to execute the DNS service.
  • the HSS 8 does not (have to) have knowledge about actual IP service applications 20A, 20B active on the device 2.
  • the indication includes the network address for the DNS service 22 executed on the device 2.
  • the HSS 8 stores the network address for the DNS service executed 22 on the device 2.
  • the indication of the device's capability to execute the DNS service that the device 2 provides to the HSS 8 includes an IP address on which the DNS service 22 executed on this multimedia device 2 can be reached for a native DNS query.
  • This IP address can be the IP address that the device 2 had received during IMS registration for secure access to the IMS network.
  • This IP address for secure access to the IMS network is an IP address on the P-CSCF 5.
  • the DNS query towards the device 2 will be routed through the P-CSCF 5, which will forward the DNS query, over the secure connection, to the device 2.
  • the P-CSCF 5 In order to allow the P-CSCF 5 to forward the DNS query towards the subscriber's device 2, the P-CSCF 5 needs to be able to associate a DNS query with a particular registered subscriber. Therefore, when the IMS registration from the subscriber contains an indication of the device's capability to execute the DNS service, the P-CSCF 5 stores that indication in the subscriber profile of the subscriber. The indication includes the network address for the DNS service executed on the device 2. Hence, the P-CSCF entity stores the address for the DNS service executed on the device 2 upon registration of the device 2. This enables the P-CSCF 5 to forward a DNS query for the domain associated with the subscriber to the appropriate registered IMS device 2.
  • the device 2 can use the IP address related to the IP access network 4. In that case, the DNS query towards the device 2 will not traverse the secure IMS connection.
  • the domain for which the device 2 indicates that it is authoritative shall be a domain that is associated with ('owned by') the user of this device 2.
  • a domain name of this domain can be composed of the user part and domain part of one of the subscriber's IMS public user identities, IMPU, in the Implicit registration set (IRS) for this device 2.
  • IMS Implicit registration set
  • the public user identifier for DNS services has the form of a domain. In this example, the following address components are identified.
  • the 'my-company.nl' fields of the domain lead to forwarding the DNS service request to the IMS network serving users of the domain my-company.nl, in a manner comparable with forwarding a SIP service request to that IMS network.
  • the fields 'john.smith' together with the domain fields that were used for forwarding the DNS service request to the IMS network serving users of the domain my-company.nl are used to identify the sub-domain associated with the user from whom a DNS service is requested.
  • the DNS service request can be forwarded to the sub-domain, using the DNS contact address that was deposited in the HSS 8. The adherence to this rule may be enforced by the HSS 8.
  • FIG. 5 shows an example of a subscriber's multimedia device 2.
  • the device 2 includes a processing unit 26.
  • the processing unit 26 is arranged for executing at least one IP service application 20A, 20B.
  • the processing unit 26 further includes a requesting unit 23 arranged for determining information relating to the at least one IP service application (20A, 20B) that is being executed on the device 2.
  • the requesting unit can request the Operating System, OS, of the device 2 for information relating to the at least one IP service application 20A, 20B.
  • the information relating to the at least one IP service application 20A, 20B in this example includes a network address at which the at least one IP service application 20A, 20B is accessible.
  • the device 2 further includes a DNS query receiver 21 for receiving a DNS query relating to the domain associated with the subscriber associated with the device 2.
  • the processing unit 26 is further arranged for executing the DNS service 22 relating to the domain associated with the subscriber.
  • the device 2 includes a memory 30.
  • the memory 30 stores 206 the information relating to the DNS resource records.
  • the device 2 further includes a depositing unit 32 which will be explained below.
  • the DNS service 22 executed 204 in the processing unit 26 can, alternatively, also be provided by a DNS server 22', i.e. a dedicated hardware unit, provided in the device 2. In the latter case, the memory 30 can form part of the DNS server 22'.
  • the memory 30 contains DNS resource records in accordance with the IP service applications offered by the device 2 at that moment.
  • DNS resource records will typically comprise Naming Authority Pointer (NAPTR) records, Service (SRV) records and A records.
  • NAPTR Naming Authority Pointer
  • SSV Service
  • a records instead of A records (for IP version 4, IPv4, addressing), AAAA records (for IP version 6, IPv6, addressing) can be used. Where herein is referred to A records, this is to be understood as referring to A records or AAAA records, so far as appropriate, unless otherwise indicated.
  • the processing unit 26 of the subscriber's device 2 is executing 202 the HTTP service application 20A, on the domain john.smith.my-company.nl.
  • a third party 16 wants to access this HTTP service application 20A.
  • the third party 16 transmits 222 a DNS query for that address.
  • the DNS query is routed, by means of standard DNS iterative query forwarding to the authoritative DNS name server 14 for the domain my-company.nl (just as a request for a SIP server for that domain would be forwarded to that authoritative name server).
  • This authoritative DNS name server 14 is configured such that all DNS queries destined for sub-domains, i.e.
  • HSS 8 acts as authoritative name server for a domain including a plurality of sub-domains, each sub-domain being associated with a subscriber's public address, each subscriber being associated with a subscriber 2.
  • the HSS 8 stores the indication of the multimedia device's capability to execute the DNS service 22.
  • the public domain used for the IP service applications on the subscriber John Smith' device contains an additional, unique field associated with the IMS operator serving the subscriber, e.g. john.smith.mobile.my-company.nl.
  • the fields mobile.my-company.nl can then point to a DNS server in the IMS network serving the domain my-company.nl.
  • embodiments of the present invention exist which do not comply with the above described name structure for the sub-domain formed by the subscriber's device 2.
  • a DNS query for the sub-domain john.smith.my-company.nl is forwarded 222, 224, 226, e.g. through native DNS iterative DNS query forwarding, towards the device currently in use by the subscriber John.Smith@my-company.nl.
  • the network 1 does not need to have information about IP service applications that are active in the device 2 in use by the subscriber John.Smith@my-company.nl.
  • the network 1 only has to forward the DNS query to this device 2, using the contact address (e.g. IP address) on which that device 2 is currently contactable for DNS queries.
  • the HSS 8 having received the DNS query for the sub-domain john.smith.my-company.nl, has to forward this DNS query towards the device 2 of the subscriber John Smith, using the indication of the device's capability to execute the DNS service that the subscriber John Smith had provided to the HSS 8 during registration.
  • the HSS 8 can be deployed according to Data layered architecture, DLA.
  • the DNS query can be received in a HSS-DNS front-end, which forwards the DNS query to a Centralized user database, CUDB, which contains subscriber data.
  • the CUDB has an internal database to forward the DNS query to the correct application within the CUDB and to associate the DNS query with the subscriber's data.
  • the subscriber is identified in the DNS query (john.smith.my-company.nl). Hence, this shall be a valid search criterion for the CUDB data (just as sip:john.smith@my-company.nl is a valid search criterion for the CUDB data).
  • the subscriber record in the HSS 8 for the subscriber john.smith@my-company.nl contains an indication relating to the DNS service 26 being executed on the subscriber's device 2.
  • the indication comprises a network address on which DNS service being executed on the device 2 can be reached for a DNS query.
  • the HSS 8 can forward the DNS query to the subscriber's device 2.
  • the IP address for the DNS service 26 being executed on the subscriber's device 2 is an IP address at the P-CSCF 5 (as described, to utilize the secure IMS access) or at the Access Network 4 (as described, for access outside the secure IMS connection).
  • the DNS query is forwarded to the P-CSCF 5 through which the subscriber John Smith is registered with the IMS network 1, or to the access network 4 utilized by the device 2. If P-CSCF IP address is used as IP address for DNS queries, then the P-CSCF 5 had stored the DNS service address indication from the subscriber, during registration, so is able to forward this DNS request to the subscriber's device 2.
  • the S-CSCF 6 When the S-CSCF 6 sends a SIP request to the device 2, it addresses the device 2 with the device contact address and uses the Path header, received from the P-CSCF 5 during registration, to let the SIP request traverse the P-CSCF 5 (using the Path header as Route header). Such mechanism is not available for forwarding the DNS query. Therefore, the DNS query for the sub-domain john.smith.my-company.nl is sent to the P-CSCF 5, on port 53. The P-CSCF 5 forwards the DNS query to the device 2 associated with the sub-domain john.smith.my-company.nl. Hence, in general, the DNS query can be forwarded to a network address that corresponds to the IP address that the Multimedia device 2 had received during IMS registration. The address on which the device based DNS service 22 is reachable will generally not be identical to the IP address that the device 2 has received during registration, since the port number, which forms part of the address, will be different.
  • the subscriber's device 2 receives the DNS query (on port 53).
  • the processing unit 26 of the device 2 executes the DNS service 22, as explained above.
  • the device based DNS service 22 is authoritative for the sub-domain john.smith.my-company.nl associated with the subscriber associated with the device 2.
  • This device based DNS service 22 contains DNS resource records in accordance with the IP service applications that are active in the device 2 at that moment. For example, if the user had activated the HTTP service 20A in the device 2, then the respective service application 20A would have placed a corresponding A record in the device based DNS service 22, said A record containing information that is needed for accessing the HTTP service 20A in the device 2.
  • Placing the corresponding A record in the device based DNS service 22 can include storing the A record in memory 30. Specifically, this A record will contain the IP address on which this HTTP service 20A is accessible. Refer to Figure 9 .
  • the response to the DNS query can include a network address where the requested IP service application executed on the device 2 can be
  • the response to the DNS query is sent 228 towards the party 16 that originated the query.
  • the sending 228 of the response towards the party 16 is done in accordance with standard DNS message addressing and routing technique.
  • This embodiment allows for a service access authorization utility on the IMS subscriber's device 2.
  • the subscriber can, through the DNS service 22 on the device 2, control which requesting parties 16 gain access to this subscriber's IP service applications 20A, 20B.
  • the IP address that the device 2 provides in the A record can be the IP address of the IP access network 4. In that case, access to the HTTP service 20A in the device 2 does not traverse the secure IP access via the P-CSCF 5. It is advantageous to have the device 2 provide, in the A record, the IP address of the IP access network 4, since that is publicly accessible. If the device 2 would provide, in the A record, the IP address that the device 2 had obtained from the P-CSCF 5, in the network 1, then the IP session would need to be established through the IMS network 1.
  • the NAPTR record that is returned 228 in response to the query contains an instruction to apply an SRV record query.
  • the domain to be used for the SRV record query shall be a domain pointing to the same device 2 based DNS service 22.
  • an SRV query towards the device based DNS service 22 shall result in an instruction to apply an A record query.
  • the domain to be used for the A record query shall be a domain pointing to the same device based DNS service 26.
  • An A record query towards the device based DNS service 22 shall return an IPv4 address.
  • An AAAA record query towards the device based DNS service 22 shall return an IPv6 address.
  • the device 2 If the device 2 has, at the moment of receiving the DNS query, no IP service application active and operational, then there will not be a corresponding DNS record for such service application. Hence, the device 2 applies regular DNS response method to indicate that the requested DNS record does not exist.
  • the Time-to-live, TTL, of the DNS resource records returned by the device based DNS service 22 should be set appropriately (by the device application that sets these respective resource records).
  • a mobile device for example, would typically use a short TTL value.
  • This party 16 determines from the response the network address at which the requested IP service application 20A, 20B is to be accessed. The party 16 then sends 230 a request for the IP service application 20A, 20B to the device 2. Upon receiving 232 the latter request, the subscriber's multimedia device 2 provides the requested IP service to the party 16.
  • the device 2 based DNS service 22 is used to grant, by an IMS network subscriber, access to that subscriber's one or more auxiliary devices 24A, 24B.
  • the IMS subscriber has a plurality of IP service applications available, being executed on the plurality of auxiliary devices 24A, 24B that are under administrative control if this IMS subscriber.
  • These auxiliary devices 24A, 24B can be additional multimedia devices, e.g. multimedia terminals.
  • These devices 24A, 24B can also be other devices, e.g. dedicated devices for executing IP service applications.
  • These devices 24A, 24B are arranged for executing IP service applications 20A, 20B, such as an HTTP service or an FTP service.
  • FIG 11 shows a schematic representation of a device 2 and a device 24A (device 24B being essentially identical).
  • the subscriber's multimedia device 2 includes the processing unit 26 arranged for executing the DNS service 22 relating to the domain associated with the subscriber, including the devices 24A and 24B.
  • the device 2 further includes the DNS query receiver 21, the requesting unit 23, the memory 30 and the depositing unit 32 as described with respect to Figure 5 .
  • the requesting unit 23 is arranged for requesting (e.g. from the Operating System, OS) the device 24A for information relating to the at least one IP service application 20A, 20B.
  • the information relating to the at least one IP service application 20A, 20B in this example includes a network address at which the at least one IP service application 20A, 20B is accessible.
  • the DNS service 22 executed 204 in the processing unit 26 can, alternatively, also be provided by a DNS server 22', i.e. a dedicated hardware unit, provided in the device 2.
  • the memory 30 can form part of the DNS server 22'.
  • the device 24A includes a processing unit 27 arranged for executing one or more IP service applications 20A.
  • the processing unit is also arranged for gathering information relating to the at least one IP service application that is being executed on the device 24A and for providing this information to the device2.
  • the device 2 further includes a receiving unit 28 arranged for obtaining from the device 24A information relating to the at least one IP service application that is being executed on the device 24A.
  • the secure HTTP connection 25A, 25B between the device 2 and the devices 24A, 24B is used by the device 2 to obtain information about the active and operational IP service applications in these devices 24A, 24B, so it can configure the device based DNS service 22 accordingly.
  • the processing unit 26 of the device 2 is thereto arranged for, using this information, generating DNS resource records in accordance with the IP service applications 20A offered by the devices 24A, 24B at that moment.
  • the DNS resource records are stored in the memory 30. These DNS resource records will typically comprise NAPTR records, SRV records and/or A or AAAA records.
  • access to each of the IP service applications 20A, 20B on the devices 24A, 24B can be obtained through a DNS query towards the DNS service 22 being executed on this IMS subscriber's device 2.
  • this device 2 is an IMS device, e.g. an IMS terminal. Access to this device based DNS service 22 takes place as described above.
  • the IP service application 20A, 20B on the device 24A, 24B is accessible by means of addressing information obtained from the DNS service 22 executed on the multimedia device 2, and the device 2 obtains information about IP service applications being executed in the device 24A, 24B, so as to configure the DNS service 22 executed on the Multimedia device 2 accordingly.
  • the device 2 is arranged for establishing, maintaining and terminating a secure HTTP connection with the devices 24A, 24B.
  • the DNS service 22 executed on the multimedia device 2 maintains a secure HTTP connection 25A, 25B with the subscriber's associated other devices 24A, 24B.
  • This secure HTTP connection 25A, 25B is used to grant access to a designated IP service application(s) on these other devices 24A, 24B, said access being granted to another party (entity) 16 requesting such access.
  • the IP service application 20A, 20B on the device 24A, 24B is accessible for the requesting party 16 by means of addressing information obtained from the DNS service 22.
  • the DNS response to this other party 16 contains the IP address of such designated IP service application on such other (associated) device 24A, 24B.
  • This embodiment allows for a service access authorization utility on the IMS subscriber's device 2.
  • the subscriber can, through the DNS service 22 on the device 2, control which requesting parties 16 gain access to this subscriber's IP service applications 20A, 20B.
  • the IP service application 20A, 20B being executed on such other (associated) device 24A, 24B provides access only to entities 16 that are using the same sender's IP address for the access to said IP service, as was used for the query to the DNS server.
  • the secure HTTP connection 25A, 25B between the subscriber's device 2 and the subscriber's associated device(s) 24A, 24B can be using WLAN connectivity from the device 2 or can be using 3G or LTE access, i.e. not using the IMS registration for said secure HTTP.
  • the IP service applications 20A, 20B, the DNS query receiver 21, the DNS service 22, the requesting unit 23, the processing unit 26, the processing unit 27, the receiving unit 28, and the depositing unit 32 can be embodied as dedicated electronic circuits, possibly including software code portions.
  • the IP service applications 20A, 20B, the DNS query receiver 21, the DNS service 22, the requesting unit 23, the processing unit 26, the processing unit 27, the receiving unit 28, and the depositing unit 32 can also be embodied as software code portions executed on, and e.g. stored in, a memory of, a programmable apparatus such as a computer.
  • IP access roaming IMS registration runs via a P-CSCF entity in the subscriber's home network.
  • Access to the DNS service 22 being executed on the subscriber's device 2 runs via secure IMS access, via the P-CSCF entity.
  • the device 2 deposits the indication of its capability to execute the DNS service in the HSS, during registration.
  • IMS Roaming the subscriber uses a P-CSCF entity in the visited country. The functioning of the method of the invention depends on support, by the used P-CSCF entity, of the registration of the network address for the DNS service 22 executed on the device 2.
  • the subscriber can use wireline IP access in a foreign country.
  • the user attaches via a P-CSCF entity in the home IMS network. Registration of the network address for the DNS service 22 executed on the device 2 is done via this P-CSCF entity, as described.
  • the subscriber can have multiple IMS devices in operation. These devices can register with the same IMS public user identity, e.g. sip:john.smith@my-company.nl. Each of these devices can, independently, register a DNS service 22 for the domain john.smith.my-company.nl.
  • the HSS stores, at any moment, a single network address for the DNS service 22 for the domain john.smith.my-company.nl,
  • the HSS 8 stores the device based DNS service 22 that registers latest. Hence, one device based DNS service 22 replaces the other when it registers.
  • the HSS 8 stores the device based DNS service 22 that registers first. Hence, registration of a new device based DNS service is not accepted if there is already a device based DNS service registered.
  • the method herein can be expanded to allow for a distributed DNS service, whereby multiple devices 2 of a subscriber (e.g. john.smith.my-company.nl) have a DNS service 22 associated with this domain. This can be done, for example, by letting the HSS 8 forward the DNS request to multiple devices 2 that have deposited the network address for their DNS service and then construct an aggregate DNS result, based on the respective responses received from these devices.
  • a DNS service request is forwarded to at most one device.
  • the invention relates to a subscriber's device 2 being a multimedia device for an IP multimedia network 1.
  • the device 2 or an auxiliary device 24A, 24B communicatively connectable to the device 2 comprises a processing unit 26, 27 arranged for executing at least one IP service application 20A, 20B.
  • the device 2 further includes a DNS query receiver 21 for receiving a DNS query.
  • the device 2 further includes a requesting unit 3 for requesting an identifier of the at least one IP service application.
  • the identifier can include a network address at which the at least one IP service application is accessible.
  • the device 2 comprises the processing unit 26 arranged for executing a DNS service 22 and a memory 30 (arranged for) storing information relating to DNS resource records in accordance with IP service applications that are being executed on the device 2 at that moment.
  • the device 21 further includes a depositing unit 32 arranged for depositing, e.g. during registration, with the multimedia network 1, an indication of the devices capability to execute the DNS service 22.
  • the indication includes a network address on which the DNS service can be reached for a DNS query.
  • the invention also generally relates to a method for providing at least one IP service application from a subscriber's multimedia device 2 in an IP multimedia network 1.
  • the method comprises executing 202 at least one IP service application 20A, 20B on the device 2 and/or on an auxiliary device 24A, 24B associated with the device 2.
  • the method comprises providing 204 a DNS service 22 being executed on the device 2, the DNS service relating to a domain associated with the subscriber.
  • the DNS service 22 has a memory 30 associated therewith.
  • the method includes storing 206 in the memory 30 information relating to DNS resource records in accordance with the at least one IP service application 20A, 20B that is being executed on the device 2 and/or in the auxiliary device 24A, 24B at that moment.
  • the method also includes depositing 212, 216, e.g. during registration, with the IP multimedia network 1, an indication of the device's capability to execute a DNS service 22.
  • the indication includes a network address on which the DNS service can be reached for a DNS query.
  • IMS subscribers can install and run IP service applications on their devices.
  • the DNS resource records that are needed for accessing these IP service applications are set and maintained in the device.
  • the device registers the address for its DNS service in the network, e.g. in the HSS.
  • the method and the device form a generic framework for enhancing the usability of IP service applications for end-user devices. IP service applications that are executed on the device and that can be accessed outside the context of a SIP session can allow for many useful applications.
  • IP service applications can be installed and execute IP service applications on his/her multimedia device, and that these service applications can be used by external users outside the context of a call. Accessing these services is done through a normal DNS resource record query.
  • the domain name that is used for accessing these IP service applications is the subscriber's regular public user identity, constructed as an aggregated domain.
  • the subscriber's device does not deposit this DNS record information in public DNS.
  • the device registers its DNS service address, along with its contact address for DNS services with the IP network.
  • DNS resource records are set and maintained locally in a memory of the device, as required.
  • a DNS query for the domain associated with the subscriber can efficiently be forwarded to the DNS service being executed on the subscriber's multimedia device.
  • the device can, in this manner, offer IP service applications like an HTTP service, an FTP service etc..
  • IP service applications like an HTTP service, an FTP service etc.
  • Activating or de-activating an HTTP service executed on the device has no impact on the network information.
  • Activating or de-activating a device based HTTP service results only in an update of the DNS resource records in the device itself.
  • Other potential use cases include maintaining a picture gallery in a memory of the (mobile) subscriber's multimedia device. Pictures that are taken 'on the go' (or otherwise stored on the device) are kept in the device and are maintained in a local library of the device. Selected viewers have access to an IP service application being executed on the device, which service application gives these viewers access to these pictures stored on the device.
  • the device can execute an IP service application that gives (e.g. restricted) public access to a web page executed on the device. said web page contains information (e.g. still pictures, video footage, geographic coordinates) gathered in real-time by the device.
  • Roaming to another IP access network or accessing via other IP access network is transparent for the network.
  • a new IMS registration of the device results in an update of the contact address for the device based DNS server (in the HSS).
  • the method can be applied as a functional (complementary) enhancement, with suitable device applications, to Business communication suite (BCS), Multimedia telephony (MMTel) or Rich communication suite (RCS).
  • BCS Business communication suite
  • MMTel Multimedia telephony
  • RCS Rich communication suite
  • any reference signs placed between parentheses shall not be construed as limiting the claim.
  • the word 'comprising' does not exclude the presence of other features or steps than those listed in a claim.
  • the words 'a' and 'an' shall not be construed as limited to 'only one', but instead are used to mean 'at least one', and do not exclude a plurality.
  • the mere fact that certain measures are recited in mutually different claims does not indicate that a combination of these measures cannot be used to an advantage.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
EP12721000.3A 2012-04-20 2012-04-20 Method, device, network entity and computer program product for providing an ip service application Active EP2839622B1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/NL2012/050268 WO2013157927A1 (en) 2012-04-20 2012-04-20 Method, device, network entity and computer program product for providing an ip service application

Publications (2)

Publication Number Publication Date
EP2839622A1 EP2839622A1 (en) 2015-02-25
EP2839622B1 true EP2839622B1 (en) 2016-11-16

Family

ID=46085118

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12721000.3A Active EP2839622B1 (en) 2012-04-20 2012-04-20 Method, device, network entity and computer program product for providing an ip service application

Country Status (4)

Country Link
US (2) US9876863B2 (zh)
EP (1) EP2839622B1 (zh)
CN (1) CN104247362B (zh)
WO (1) WO2013157927A1 (zh)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104247362B (zh) * 2012-04-20 2017-06-20 瑞典爱立信有限公司 用于提供ip服务应用的方法、设备和网络实体
US10097977B2 (en) * 2013-10-18 2018-10-09 Samsung Electronics Co., Ltd. Communication method for electronic device in wireless communication network and system therefor
WO2015102493A1 (en) 2014-01-03 2015-07-09 Koninklijke Douwe Egberts B.V. Exchangeable supply pack for a beverage dispensing machine, doser, pump assembly and method of manufacturing.
DK3134332T3 (da) 2015-05-15 2019-08-26 Douwe Egberts Bv Kapsel, system til tilberedning af en drikkelig drikkevare ud fra en sådan kapsel og anvendelse af en sådan kapsel i en drikkevaretilberedningsindretning
NL2016775B1 (en) 2015-05-15 2017-01-31 Douwe Egberts Bv A capsule, a system for preparing a potable beverage from such a capsule and use of such a capsule in a beverage preparation device.
EP3594149A1 (en) 2015-05-15 2020-01-15 Koninklijke Douwe Egberts B.V. A capsule, a system for preparing a potable beverage from such a capsule and use of such a capsule in a beverage preparation device
CA2985975A1 (en) 2015-05-15 2016-11-24 Koninklijke Douwe Egberts B.V. A capsule, a system for preparing a potable beverage from such a capsule and use of such a capsule in a beverage preparation device
JP6934425B2 (ja) 2015-05-15 2021-09-15 コーニンクラケ ダウ エグバート ビー．ブイ． カプセル、そのようなカプセルから飲用可能な飲料を調製するためのシステム、および飲料調製装置におけるそのようなカプセルの使用方法
EP3134330B1 (en) 2015-05-15 2019-06-05 Koninklijke Douwe Egberts B.V. A capsule, a system for preparing a potable beverage from such a capsule and use of such a capsule in a beverage preparation device
ES2788645T3 (es) 2015-10-27 2020-10-22 Douwe Egberts Bv Cápsula, sistema y método para preparar una bebida
NL2016779B1 (en) 2016-05-13 2017-11-16 Douwe Egberts Bv A capsule and a system for preparing a potable beverage from such a capsule
NL2016780B1 (en) 2016-05-13 2017-11-16 Douwe Egberts Bv A capsule, a system for preparing a potable beverage from such a capsule and use of such a capsule in a beverage preparation device
US10574674B2 (en) * 2016-07-08 2020-02-25 Nec Corporation Host level detect mechanism for malicious DNS activities
NL2019254B9 (en) 2016-10-07 2018-09-10 Douwe Egberts Bv A capsule, a system for preparing a potable beverage from such a capsule and use of such a capsule in a beverage preparation device
US10708312B2 (en) * 2017-04-05 2020-07-07 T-Mobile Usa, Inc. Third party IMS services
US10666603B2 (en) * 2017-07-13 2020-05-26 T-Mobile Usa, Inc. Optimizing routing of access to network domains via a wireless communication network
NL2019253B1 (en) 2017-07-14 2019-01-28 Douwe Egberts Bv Assembly of a capsule and a brew chamber, brew chamber, beverage preparation machine, capsule and use of a capsule.
EP3949308B1 (en) * 2019-03-29 2023-07-26 Telefonaktiebolaget Lm Ericsson (Publ) Service based interface enabled home subscriber service selection

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6415323B1 (en) * 1999-09-03 2002-07-02 Fastforward Networks Proximity-based redirection system for robust and scalable service-node location in an internetwork
US7496652B2 (en) * 2000-07-17 2009-02-24 Teleservices Solutions, Inc. Intelligent network providing network access services (INP-NAS)
US7725602B2 (en) * 2000-07-19 2010-05-25 Akamai Technologies, Inc. Domain name resolution using a distributed DNS network
US7373644B2 (en) * 2001-10-02 2008-05-13 Level 3 Communications, Llc Automated server replication
US20050249152A1 (en) * 2004-05-04 2005-11-10 Krisztian Kiss Method for processing messages
US7626950B2 (en) * 2004-08-18 2009-12-01 At&T Intellectual Property, I,L.P. SIP-based session control among a plurality of multimedia devices
ATE545997T1 (de) 2004-12-17 2012-03-15 Tekelec Us Verfahren, systeme und computerprogrammprodukte zur unterstützung des datenbankzugriffs in einer netzwerkumgebung des internet-protokoll- multimedia-subsystems (ims)
US8090766B2 (en) * 2006-08-15 2012-01-03 Microsoft Corporation System and method to identify, rank, and audit network provided configurables
CN101192939A (zh) 2006-12-01 2008-06-04 朗迅科技公司 为终端用户提供互联网多媒体子系统服务的方法
US8032632B2 (en) * 2007-08-14 2011-10-04 Microsoft Corporation Validating change of name server
US7957373B2 (en) * 2007-12-12 2011-06-07 At&T Intellectual Property I, L.P. Method and system to provide contact services in a communication network
US8780738B2 (en) * 2008-05-15 2014-07-15 At&T Intellectual Property I, L.P. Method and apparatus for supporting enterprise addressing in networks
US8196163B2 (en) * 2008-05-21 2012-06-05 Telefonaktiebolaget L M Ericsson (Publ) Controlled delivery of event information to IPTV users
US8649378B2 (en) 2008-05-22 2014-02-11 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for controlling the routing of data packets
US8645565B2 (en) * 2008-07-31 2014-02-04 Tekelec, Inc. Methods, systems, and computer readable media for throttling traffic to an internet protocol (IP) network server using alias hostname identifiers assigned to the IP network server with a domain name system (DNS)
US20100146132A1 (en) * 2008-12-04 2010-06-10 Morris Robert P Methods, Systems, And Computer Program Products For Accessing A Resource Having A Network Address Associated With A Location On A Map
DK2205020T3 (en) 2008-12-31 2018-01-02 Telia Co Ab Capacity service in a communication system
BRPI0924885B1 (pt) 2009-03-19 2020-09-24 Telefonaktiebolaget Lm Ericsson(Publ) Método para modificar alocação de funções de controle de sessão de chamada de serviço a um usuário de uma rede de subsistema de multimídia de ip, e, função de controle de sessão de chamada de serviço
US9021014B2 (en) 2009-03-25 2015-04-28 Tekelec, Inc. Methods, systems, and computer readable media for providing home subscriber server (HSS) proxy
US9906947B2 (en) 2009-10-12 2018-02-27 Lg Electronics Inc. Mobile terminated communication method and related devices
US8305933B2 (en) 2010-02-03 2012-11-06 Vonage Nework LLC Method and apparatus for detecting devices on a local area network
EP2619964B1 (en) 2010-09-24 2018-02-07 Nexios IT Systems and methods for peer-to-peer ims
US8661146B2 (en) * 2011-10-13 2014-02-25 Cisco Technology, Inc. Systems and methods for IP reachability in a communications network
US10341288B2 (en) * 2012-01-11 2019-07-02 Saguna Networks Ltd. Methods circuits devices systems and associated computer executable code for providing conditional domain name resolution
US20130205018A1 (en) * 2012-02-06 2013-08-08 Samsung Electronics Co., Ltd. Extending service discovery into cloud computing
CN104247362B (zh) * 2012-04-20 2017-06-20 瑞典爱立信有限公司 用于提供ip服务应用的方法、设备和网络实体
FR3015835A1 (fr) * 2013-12-23 2015-06-26 Orange Procede de diagnostic de fonctions service dans un reseau ip

Also Published As

Publication number Publication date
CN104247362B (zh) 2017-06-20
WO2013157927A1 (en) 2013-10-24
US10893109B2 (en) 2021-01-12
EP2839622A1 (en) 2015-02-25
CN104247362A (zh) 2014-12-24
US20180109635A1 (en) 2018-04-19
US9876863B2 (en) 2018-01-23
US20150095499A1 (en) 2015-04-02

Similar Documents

Publication Publication Date Title
US10893109B2 (en) Method, device, network entity and computer program product for providing an IP service application
JP4856179B2 (ja) Ｉｍｓにおけるアプリケーションサーバの割当方法および装置
EP1774752B1 (en) Instance identification
JP5190072B2 (ja) Ｉｐマルチメディア・サブシステム・サービスへのグループ・アクセス
JP5001436B2 (ja) 通信ネットワークにおけるメッセージの処理
US8793388B2 (en) Method and apparatus for processing a call to an aggregate endpoint device
US20110142035A1 (en) Securing Uniform Resource Identifier Information for Multimedia Calls
US8451841B2 (en) Method and apparatus for processing a call to an aggregate endpoint device
US8588791B2 (en) Method for providing IMS support for enterprise PBX users
US8228900B2 (en) Message routing in the IP multimedia subsystem
US9762534B2 (en) System and method for geographic SIP scaling
CN107257331B (zh) 用于提供ip服务应用的方法、设备和存储介质
JP5467138B2 (ja) Ｉｐマルチメディア・サブシステム・サービスへのグループ・アクセス
US20130017853A1 (en) Wholesale Network User Identity Mapping in a Mobile Network
US9369430B2 (en) Method and arrangement for allowing enterprise and personal domains in the IMS
Lundqvist et al. Service program mobility—Dynamic service roaming
WO2016050033A1 (zh) 终呼处理方法、装置及系统

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20140923

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20160707

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 846852

Country of ref document: AT

Kind code of ref document: T

Effective date: 20161215

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602012025423

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20161116

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 846852

Country of ref document: AT

Kind code of ref document: T

Effective date: 20161116

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170216

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170217

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170316

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602012025423

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170216

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20170817

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170430

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170420

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170430

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170420

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170420

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20120420

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20161116

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170316

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602012025423

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04L0065000000

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20220427

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230425

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230427

Year of fee payment: 12

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602012025423

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20231103