CN107257331B

CN107257331B - Method, apparatus, and storage medium for providing IP service application

Info

Publication number: CN107257331B
Application number: CN201710402061.4A
Authority: CN
Inventors: 罗希尔·奥古斯特·卡斯帕·约瑟夫·诺尔德斯
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2012-04-20
Filing date: 2012-04-20
Publication date: 2021-01-01
Anticipated expiration: 2032-04-20
Also published as: CN107257331A

Abstract

A method, device, network and network entity for providing at least one IP service application from a subscriber multimedia device in an internet protocol, IP, multimedia network. The method includes executing at least one IP service application located on the device and/or an auxiliary device associated with the device. Providing a domain name system, DNS, service executing on the device, the DNS service relating to a domain associated with a subscriber. The DNS service has an associated memory. Storing in a memory information relating to DNS resource records that conform to the at least one IP service application that is being executed on the device and/or the auxiliary device at that time. Storing, over an IP multimedia network, an indication of the capability of the device to perform DNS services, the indication comprising network addresses of DNS services reachable for DNS queries.

Description

Method, apparatus, and storage medium for providing IP service application

The present application is a divisional application of the chinese patent application "method, apparatus, network entity, and computer program product for providing IP service applications" (application number 2012800725310), filed 10/20/2014.

Technical Field

The present invention relates to internet protocol multimedia networks. The invention also relates to a multimedia device of a subscriber.

Background

Internet Protocol (IP) communication from one subscriber terminal to another is known. In IP-based communication over an IP network, IP services are provided to subscribers. When the subscriber terminal is a multimedia terminal (e.g., a multimedia phone), an IP service, for example, regarding multimedia components is provided as an enhancement of voice IP communication. It is known to enhance voice calls through one or more multimedia components, such as video sharing, still picture sharing, music sharing, calendar sharing, file transfer, and the like. This is sometimes referred to as "rich communication". Such as an IP Multimedia Subsystem (IMS) -based network, facilitate multimedia components in these calls through IP sessions. During call setup, the calling party and the called party may exchange their respective capabilities for such IP-based multimedia call enhancements. The capability includes an IP address to be used for communication, etc.

It has been observed that with the prior art it is not possible to request execution of an Internet Protocol (IP) service application of a subscriber's multimedia terminal, e.g. an IP Multimedia Subsystem (IMS) terminal, outside the context of an existing IP communication session, such as a voice call.

The only exception in the prior art is formed by Session Initiation Protocol (SIP) based services. A SIP terminal deposits its contact address, i.e. IP address, at a registry in the IMS network formed by a serving call session control function entity (S-CSCF). The IP address is used to establish the SIP session. The terminal thus executes the SIP service application in the sense that it receives the initial SIP transaction. Receiving an initial SIP transaction constitutes a request for performing an IP service, such as establishing a communication session or receiving an instant message.

There is no general mechanism for subscriber multimedia terminals, such as IMS terminals, to provide IP-based communication services, such as hypertext transfer protocol (HTTP) services, mail servers, or File Transfer Protocol (FTP) services, other than SIP-based communication services.

Disclosure of Invention

It is an object of the present invention to obviate at least some of the above disadvantages and to provide an improved telecommunications device. It is also an object to provide a subscriber multimedia device for an IP multimedia network to provide better versatility. It is also an object of the invention to provide the functionality of a subscriber multimedia device for an IP multimedia network to provide better versatility.

Further in accordance with the present invention, there is provided a method of providing at least one IP service application from a subscriber's multimedia device in an IP multimedia network. The method comprises the following steps: executing at least one IP service application on the device and/or an auxiliary device associated with the device. Further, a Domain Name System (DNS) service is provided that is executing on the device. The DNS service relates to a domain associated with a subscriber. The DNS service has a memory associated therewith. Furthermore, information relating to DNS resource records that correspond to at least one IP service application executed on the device and/or the auxiliary device, i.e. information required for accessing the at least one IP service application, is stored in the memory at that time. Furthermore, an indication of the capability of performing DNS services with the IP multimedia network hosting device, the indication comprising network addresses of DNS services reachable for the DNS query.

Thus, the DNS service is performed by the subscriber multimedia device, i.e. the device plays the role of a DNS server for the domain of the user involved in the device. This is beneficial because in situations where IP addresses vary over time, dynamically installing and removing, activating and deactivating IP service applications is where the subscriber multimedia device. It is therefore the device that is optimally equipped to provide information about the IP service applications available on the device.

It will be appreciated that the apparatus may be mobile or stationary. The auxiliary device may also be mobile or stationary.

It will be appreciated that the apparatus may be a manually operated apparatus, such as a subscriber terminal, or an unmanned apparatus.

The indication of the capability of the device to perform a DNS service comprises the network addresses of the DNS services reachable for the DNS query, which aspect provides the advantage that the IP multimedia network hosting the indication knows the network addresses of the DNS services reachable. Thus, DNS queries for a domain associated with a subscriber can be efficiently forwarded to a DNS service executing on the subscriber's multimedia device.

Optionally, the indication is deposited at registration using an IP multimedia network. Depositing the indication using the IP multimedia network at registration provides the benefit of depositing the indication using the IP multimedia network at the time the device has been deemed to deposit information using the network.

According to one aspect, the information relating to the DNS resource record comprises information required to access the IP service application (e.g., an IP address at which the IP service application is accessible), wherein the DNS resource record conforms to at least one IP service application being executed on the device and/or the auxiliary device. Thus, the information provides information about where to go to access the IP service application.

According to one aspect, a DNS service is performed in a DNS server on a multimedia device. Thus, the device may be provided with dedicated hardware units to perform the required DNS server functions.

Optionally, the IP multimedia network is an IMS network.

Optionally, the method includes routing a DNS query destined for a DNS service executing on the multimedia device to an official DNS name server for a domain associated with the user group. The device is associated with a member of the user group. The DNS nameserver is configured to forward all DNS queries destined for a sub-domain of said domain to a home subscriber server, HSS, of an IMS operator serving users associated with said domain. The HSS acts as the authoritative naming server for DNS services performed on multimedia devices whose users are associated with sub-domains of the domain, providing the benefit of being able to use DNS iterative query forwarding.

The present invention relates to a subscriber device as a multimedia device for a multimedia network. The device, or an auxiliary device communicatively connected to the device, comprises a processing unit configured to execute at least one IP service application. The apparatus also includes a receiver for receiving a DNS query. The apparatus further comprises a requesting unit for requesting an identifier of the at least one IP service application. The identifier may include a network address at which the at least one IP service application may be accessed. The device comprises a processing unit arranged to perform a DNS service and a memory arranged to store information relating to DNS resource records that are in accordance with an IP service application that is being executed on the device at that time. The device further comprises a depositing unit arranged to deposit, during e.g. registration, an indication of the capability of the device to perform DNS services using the multimedia network. The indication includes a network address of a DNS service reachable for the DNS query.

The invention also relates to an IP multimedia network comprising a multimedia device, or a combination of a multimedia device and an auxiliary device, and a network entity, wherein the network entity is arranged to store an indication of the capability of the device to perform DNS services. The network entity acts as an official naming server for a domain comprising a plurality of sub-domains, each sub-domain being associated with a public address of a subscriber, each subscriber being associated with a subscriber device.

The invention also relates to a network entity, such as an HSS of an internet protocol, IP, multimedia network, wherein the network entity is stepped to receive and store an indication of a capability of a device to perform DNS services, the network entity acting as an official naming server for a domain comprising a plurality of sub-domains, each sub-domain being associated with a public address of a subscriber, each subscriber being associated with a subscriber device.

The invention also relates to a computer program product executable on a programmable subscriber multimedia device. The computer program product comprises software code portions arranged, when executed on a programmable subscriber multimedia device, to perform the following steps. It is determined that there is at least one IP service application executing on the device and/or an auxiliary device associated with the device at that time. DNS services are provided on a device that relate to a domain associated with a subscriber. The DNS service has associated with it, for example, a memory of a device. Information is stored in memory relating to DNS resource records that are consistent with (i.e., required to access) at least one IP service application that is being executed on the device and/or the secondary device at that time. The device is instructed to deposit an indication of the device's ability to perform DNS services using the multimedia network that the device is registered with or requesting registration for. The indication includes a network address of a DNS service reachable for the DNS query.

The advantage provided by providing the computer program product is that the method described above can be executed on a programmable subscriber multimedia device in the form of a computer program product. The computer program product may be stored on a data carrier or may be provided via a carrier wave, such as the internet.

Drawings

The invention will now be further elucidated by way of non-limiting examples with reference to the accompanying drawings, in which

FIG. 1 is a schematic representation of a portion of a prior art IP network;

FIG. 2 is a schematic representation of a portion of an existing IP network;

FIG. 3 is a schematic representation of a portion of a prior art IP network;

FIG. 4 is a schematic representation of an IP network;

FIG. 5 is a schematic representation of a multimedia device;

FIG. 6 is a flow chart showing a process;

FIG. 7 is a schematic representation of an IP network;

FIG. 8 is a schematic representation of an IP network;

FIG. 9 is a schematic representation of an IP network;

FIG. 10 is a schematic representation of an IP network; and

figure 11 is a schematic representation of a combination of a device and an auxiliary device.

Like reference numbers in the figures refer to like entities or processes.

Detailed Description

It has been observed that with the prior art it is not possible to request execution of an Internet Protocol (IP) service application of a subscriber multimedia terminal, such as an IP Multimedia Subsystem (IMS) terminal, outside the context of an existing IP communication session, such as a voice call.

The SIP terminal deposits a contact address (IP address) at the registry. In an IMS network, the registry is a serving call session control function entity (S-CSCF). The contact address is used to establish a SIP session with the SIP terminal. The terminal thus acts as a SIP server in the sense that it can receive the initial SIP transaction. Receiving an initial SIP transaction constitutes a request for executing an IP service application, such as establishing a communication session or receiving an instant message.

In addition to the SIP services described above, IP services cannot be established to IMS terminals outside the context of an existing SIP communication session. In addition to SIP-based communication services, there is no general mechanism for providing IP-based communication services, such as hypertext transfer protocol (HTTP) services, mail servers, or File Transfer Protocol (FTP) services, by subscriber multimedia terminals, such as IMS terminals.

Fig. 1 shows an example of a prior art IMS network 101. The network includes User Equipment (UE)102, UE 102 and a common user identifier sip: IMS subscribers of john.smith @ my-company.nl are associated. Subscriber John Smith is an enterprise subscriber, associated with the enterprise "My-company" and has a domain name of "My-company.

The network 101 in fig. 1 further comprises an IP connectivity access network (IP-CAN)4, a registry 6, here an S-CSCF entity 6, a Home Subscriber Server (HSS)8, an interrogating call session control function (I-CSCF) entity 10, an Interconnection Border Control Function (IBCF) entity 12, a Domain Name System (DNS) server 14. Subscriber John Smith registers with IMS network 101 as an IMS subscriber through a SIP terminal formed by UE 102. Thus, the IMS subscriber terminal 102 executes a SIP service application, i.e. the subscriber terminal 102 acts as a SIP server.

When a subscriber IMS terminal 102 registers in the IMS network 102, it leaves its SIP binding at the registry 6, i.e. the S-CSCF entity 6 of the IMS network 101 to which the subscriber belongs as shown in fig. 2. The P-CSCF entity 5 forms part of a visited IMS network. The S-CSCF entity 6 forms part of the home IMS network. The I-CSCF entity 10 and the HSS 8 are not shown in fig. 2, but are visible in fig. 1. Once the IP address of the subscriber terminal 102 has been stored in the S-CSCF entity 6, the terminal 102 is ready to receive a request for a SIP service. The terminal 102 has the role of a SIP server by being able to receive and process SIP requests (on a common IP address and port number). This is depicted in fig. 3. Again, the I-CSCF entity 10 and the HSS-8 are not shown (refer to fig. 1).

In fig. 3 "R" denotes a registrar function 7 in the S-CSCF entity 6. Fig. 1 shows a SIP client 16 associated with a second subscriber (the other party). To send an initial SIP request to the subscriber terminal 102, the public identity of the subscriber is used. The SIP client 16 does not need any knowledge of the access network currently used by the subscriber terminal 102 and the IP address of the terminal 102.

When a SIP service is requested from the terminal 102, the user requesting the SIP service is identified as SIP: smil @ my-company.nl. The public user identifier of the SIP service is in the form of a Universal Resource Identifier (URI). The following address components are identified. The pattern "sip: "indicates that a SIP service is requested. The protocol that routes the request to the destination party should be SIP. The domain "my-company.nl" is used to export an IMS network (e.g., IMS. provider.nl) that provides services for users requesting SIP services. This enables SIP service requests to be routed to the IMS network user according to DNS services and SIP routing methods. Smith, in conjunction with a domain, identifies a specific user served by the IMS network (derived by the domain). In the IMS network, the SIP service request is forwarded to a registry (S-CSCF)6 (e.g., S-CSCF1. im. provider. nl) currently assigned to the user. When the SIP request is forwarded to the registry 6, it may be further forwarded to the user terminal based on contact address information included in the registry (e.g., SIP: 173.68.81.221).

When the SIP client 16 sends a SIP request to an IMS subscriber associated with the UE 102, there is three steps of forwarding the SIP request, specific to the SIP service. Which facilitates the establishment of SIP services to the terminals 102 of IMS subscribers. Each of the three-step forwarding is based on a database that includes static or dynamic data. An initial request for establishing a multimedia communication session (e.g., invite), or a non-session related request (e.g., message), is extended to a terminal used by a current subscriber using three relationships. First, DNS queries to DNS servers are used to extend invitations from SIP clients 16 initiating SIP sessions to IMS networks serving any subscriber within the domain my-company.nl (< user > @ my-company.nl). The DNS constitutes the global DNS infrastructure and includes external DNS and internal DNS. This DNS-based routing of invitations is based on static DNS configuration. Secondly, in an IMS network serving subscriber < user > @ my-company.nl, the HSS 8 query using the I-CSCF entity 10 extends the invitation to the registrar S-CSCF entity 6 that is currently serving the subscriber john. The data for this extension is dynamic data, contained in the HSS 8, and is updated when the subscriber deregisters or another S-CSCF entity 6 is assigned to the subscriber john. Third, the invitation for the subscriber john.smith @ my-company.nl is extended from the S-CSCF entity 6 to one or more terminals 102 with which the subscriber John Smith is currently registered using SIP contact binding. The contact binding information is dynamic and is updated when, for example, the terminal 102 changes IP access.

As described, subscriber John Smith is now ready to receive a SIP session establishment request (e.g., SIP invite) or a non-session related SIP transaction request (e.g., SIP message).

The inventors have realized that in addition to the possibilities offered by the prior art network 101, subscribers would benefit from the possibility of providing additional IP services to their multimedia terminals, which IP services can be accessed by third parties. The inventors have realized that e.g. subscribers want to provide (limited) publicly available hypertext transfer protocol (HTTP) services from their mobile or fixed terminals. The HTTP service may be accessed through a Uniform Resource Locator (URL) john. The inventors have also realised that as another example, subscribers are willing to provide File Transfer Protocol (FTP) services from their terminals. The FTP service can also be accessed through the URL john. Also, the inventors have realized that subscribers would benefit from the possibility of providing these services on non-human operated devices. The following examples relate to subscriber multimedia devices. The subscriber multimedia device may be a manually operated device or a non-manually operated device. The subscriber multimedia device may for example be a subscriber multimedia terminal or a subscriber device in a machine-to-machine communication scenario.

Fig. 4 shows an example of a part of an IP multimedia network 1 according to the invention. The network 1 comprises a subscriber 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 the functionality of the multimedia device 2 and the terminal 102. Reference is also made to fig. 5, which shows a schematic representation of the multimedia device 2, and to fig. 6, which shows a flow chart comprising the working steps of the network 1 described in relation to fig. 4.

The subscriber has 3 IP service applications active 202 and working on his (mobile) multimedia device 2. The first IP service application is a SIP user agent 18 for establishing and receiving SIP sessions or SIP stand-alone requests. The SIP user agent 18 is activated at IMS registration. The SIP user agent 18 is accessed via an IMS network, such as a P-CSCF entity and an S-CSCF as known in the art. The second IP service application is the FTP service application 20B, which can be activated whenever needed. The 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 whenever needed. The HTTP service application 20A is accessed via the IP access network 4 used by the subscriber associated with the multimedia device 2.

According to the prior art, it can be envisaged that the DNS contains the domain John. The (public) official DNS naming server 14 of the domain is thus configured with DNS resource records required by the IP service application in the IMS device 2 of the visiting subscriber, i.e. required to be obtained through the DNS resolver in the IP service client 16. The problem with this static configuration is that this DNS name server 14 configuration is static, while the IP address of the subscriber's device 2 is dynamic. And, the subscriber can deploy one or more IP service applications on his multimedia device 2. The subscriber may activate or deactivate the IP service application on his device 2 when required. This flexible activation and deactivation cannot be configured on the (static) DNS name server 14. Also, the subscriber should have the possibility to add and remove IP service applications to and from his device 2. Such flexible IP service application addition and removal cannot be configured on the (static) DNS name server 14. It is noted here that IETF RFC 2136, dynamic UPDATE in domain name system (DNS UPDATE), describes how to UPDATE a (public) DNS server. In particular, IETF RFC 2136 specifies a protocol according to which entities can update DNS resource records in DNS servers. The updates to these resource records are static. This reinforces the problem mentioned above, that is, the subscriber must frequently update the (public) DNS server. The update is required whenever the subscriber acquires a new IP address for device 2, or whenever the subscriber activates or deactivates an IP service application on his device 2, or whenever the subscriber adds or removes an IP service application on his device 2.

These problems are solved by providing 204 a DNS service 22 executing on the device 2. DNS queries involving the subscriber's domain (i.e., the domain john. smith. my-company. nl) are forwarded 222, 224, 226 to the subscriber device 2. The subscriber device 2 is arranged to execute a DNS service 22 thereon relating to a domain associated with the subscriber. The subscriber device 2 also stores 206 information relating to DNS resource records required to access the

IP service applications

20A and 20B that are executing on the device 2 at the time.

Thus, it is the subscriber multimedia device 2 that performs the DNS service 204, i.e. the device 2 acts as a DNS server 22' for the domain of the user that relates to the device 2. It is the subscriber multimedia device 2 that activates and deactivates the

IP service applications

20A, 20B because they are dynamically installed and removed in the case that the IP addresses will differ over time. It is therefore this device 2 that is optimally equipped to provide information about the

IP service applications

20A, 20B available on the device 2.

The registration of the terminal 102 to the IP network 101 is described above with reference to fig. 2. For registering to the IMS network 1, the registration is also performed by the device 2.

During registration, device 2 also deposits an indication of its ability to perform DNS services. The device 2 deposits a "DNS server binding" in the IMS network 1, according to the principle of depositing a contact binding in the S-CSCF entity 6 for SIP services. This is depicted in fig. 7. According to the IMS specification, the contact binding for the SIP service is deposited in the S-CSCF entity 6 and will therefore not be described. The dashed line 112 indicates that the contact address for the SIP service for the public user identity is deposited in the registry 6. The dashed line 312 indicates that the contact address of the DNS service for the public user identity is stored in the HSS 8.

An indication of the capability of the device to perform DNS services is included in the (protected) SIP register message 213 and deposited in the HSS 8. This indication is included in a Diameter server assignment request SAR 215 sent 216 from the S-CSCF to HSS 8. According to the IMS standard, Diameter SAR may carry a copy of the complete SIP registration message, including an indication of the device's ability to perform DNS services. The validity of this indication over time is aligned with the IMS registration of the device 2. The indication that the device performs DNS service capability is cleared when IMS registration of device 2 expires or the device deregisters. Thus, the HSS 8 receives an indication of the capability of the device to perform DNS services. The HSS 8 is not (nor does it have to be) aware of the actual

IP service applications

20A and 20B that are active on the device 2. The indication comprises the network address of the DNS service 22 executing on the device 2. Thus, HSS 8 stores the network address of DNS service 22 executing on device 2.

The indication of the capability of the device 2 to perform DNS services to the HSS 8 comprises the IP address of the DNS service performed on the multimedia device 2 reachable for the local DNS query. The IP address may be an IP address received by the device 2 at IMS registration for secure access to the IMS network. The IP address for secure access to the IMS network is an IP address on the P-CSCF 5. Thus, the DNS query for device 2 will be routed to device 2 by P-CSCF5 and P-CSCF5 will forward the DNS query over the secure connection.

In order for the P-CSCF5 to forward the DNS query to the subscriber device 2, the P-CSCF5 is to be able to associate the DNS query with a particular registered subscriber. Thus, when the IMS registration from the subscriber includes an indication of the capability of the device to perform DNS services, the P-CSCF5 stores the indication in the subscriber profile of the subscriber. The indication comprises the network address of the DNS service performed on the device 2. Thus, when registering the device 2, the P-CSCF entity stores the network address of the DNS service performed on the device 2. This enables the P-CSCF5 to forward DNS queries for the domain associated with the subscriber to the appropriate registered IMS device 2.

Alternatively, the device 2 may use an IP address relating to the IP access network 4. In this case, the DNS query to device 2 will not go through the secure IMS connection.

The domain that the device 2 indicates as being official should be the domain associated with (owned by) the user of the device 2. The domain name of the domain may comprise a user part and a domain part of one of the subscriber IMS public user Identities (IMPUs) in the Implicit Registration Set (IRS) of the device 2. For a subscriber sip: smih @ my-company.nl, the domain of the DNS service is set to john.smith @ my-company.nl in this example. The public user identifier of the DNS service is in the form of a domain. The following address components are identified in this example. The domain field "my-company.nl" causes DNS service requests to be forwarded to IMS networks that serve users of the domain my-company.nl in a manner comparable to the forwarding of SIP service requests to IMS networks. Smith, and a domain field for forwarding DNS service requests to IMS networks serving users of the domain my-company.nl (in other words, the complete domain john. Using the DNS contact address stored in the HSS 8, DNS service requests can be forwarded to sub-domains. The rule may be enforced by the HSS 8.

Figure 5 shows an example of a subscriber multimedia device 2. The device 2 comprises a processing unit 26. The processing unit 26 is arranged to execute at least one

IP service application

20A, 20B. The processing unit 26 further comprises a requesting unit 23 arranged to determine information relating to at least one IP service application (20A, 20B) being executed on the device 2. The requesting unit may request information relating to the at least one

IP service application

20A, 20B from the operating system OS of the device 2. In this example, the information relating to the at least one

IP service application

20A, 20B comprises a network address at which the at least one

IP service application

20A, 20B is accessible. The device 2 further comprises a DNS query receiver for receiving a DNS query relating to a domain associated with a subscriber, wherein the subscriber is associated with the device 2. The processing unit 26 is further arranged to perform a DNS service, which relates to a domain associated with the subscriber. The device 2 comprises a memory 30. The memory 30 stores 206 information relating to DNS resource records. The apparatus 2 further comprises a storage unit 32, which will be explained below. It will be appreciated that the DNS service 22 executed in the processing unit 26 may alternatively 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 forms part of the DNS server 22'.

The memory 30 comprises DNS resource records that are in accordance with the IP service applications that are provided at that time in the device 2. These DNS resource records typically include a Naming Authority Pointer (NAPTR) record, a Service (SRV) record, and an a record. The a record (for IP version 4, IPv4, addressing) can be replaced with an AAAA record (for IP version 6, IPv6, addressing). Unless otherwise indicated, where appropriate, references herein to a records are to be understood as referring to a records or AAAA records.

In this example, the processing unit 26 on the subscriber device 2 executes the HTTP service application 20A on the domain john. The third party 16 wants to access the HTTP service application 20A. In addition, the third party 16 sends 222 a DNS query for the address. The DNS query is routed to the official DNS name server 14 of the domain my-company.nl (as would a request for a SIP server of the domain be forwarded to the official name server) by standard DNS iterative query forwarding. The official DNS naming server 14 is arranged to have all queries (i.e. my-company.nl) destined to a sub-domain associated with a subscriber within the domain forwarded 224 to the HSS 8 of the IMS operator, which services users of the domain my-company.nl. The HSS 8 then acts as the official naming server for the sub-domain my-company nl. The HSS 8 acts as an official naming server for a domain comprising a plurality of sub-domains, each sub-domain being associated with a subscriber public address, each subscriber being associated with a subscriber 2. The HSS 8 stores an indication of the capability of the multimedia device to perform DNS services 22.

It will be appreciated that the public domain for IP service applications on the device of subscriber John Smith may include additional, unique fields associated with the IMS operator providing services to the subscriber, such as John. My-company.nl may point to a DNS server in the IMS network that serves the domain my-company.nl. It will be appreciated that there are embodiments of the invention that differ from the naming structure of the sub-domains formed by the subscriber device 2 described above.

When requesting an

IP service application

20A, 20B from device 2, a DNS query for the subdomain john.smith.my-company.nl is forwarded to the device currently used by the subscriber john.smith @ my-company.nl by, for example, local DNS iterative DNS query forwarding. This is shown in fig. 8. The network 1 does not need information about the IP service applications in the devices used by the subscriber john. The network 1 only needs to forward the DNS query to the device 2 with the contact address (IP address) of the currently contactable device 2 for the DNS query.

The forwarding of the DNS query is performed by the following steps. HSS 8, after receiving the DNS query for the sub-domain john.smith.my-company.nl, has to forward the DNS query to device 2 of subscriber John Smith with an indication of the device's ability to perform DNS services, which indication is provided to HSS 8 by subscriber John Smith during registration. The HSS 8 is deployed according to a data hierarchy DLA. A DNS query is received in a front end of the HSS-DNS, and the front end of the HSS-DNS forwards the DNS query to a centralized user database CUDB containing subscriber data. The CUDB has an internal database to forward DNS queries to the correct applications within the CUDB and to associate DNS queries with subscriber data. The subscriber is identified in a DNS query (john. Therefore, this should be an effective lookup criterion for CUDB data (just as sip: john. smith @ my-company. nl is an effective lookup criterion for CUDB data).

The subscriber record in the HSS 8 for the subscriber john.smith @ my-company.nl includes an indication relating to the DNS service being performed on the subscriber device 2. The indication comprises the network addresses of DNS services performed on the device 2 reachable for the DNS query. Thus, the HSS 8 may forward the DNS query to the subscriber device 2. The IP address of the DNS service 26 executed on the subscriber device 2 is an IP address located at the P-CSCF5 (using secure IMS access as described) or at the access network 4 (access other than secure IMS access as described). Thus, the DNS query is forwarded to the P-CSCF5, and the subscriber registers with the IMS network 1 or the access network 4 used by the device 2 via the P-CSCF 5. If the IP address of the P-CSCF is used as the IP address for the DNS query, the P-CSCF5 has stored a DNS service address indication from the subscriber during registration so that the DNS request can be forwarded to the subscriber device 2.

When the S-CSCF 6 sends a SIP request to the device 2, it addresses the device 2 with the device contact address and passes the SIP request through the P-CSCF5 using the path header received from the P-CSCF5 at registration (using the path header as a routing header). This mechanism is not available for forwarding DNS queries. Thus, a query for the sub-domain john.smith.my-company.nl is sent to the P-CSCF5 on port 53. The P-CSCF5 forwards the DNS query to the device 2 associated with the sub-domain john. Thus, in general, the DNS query may be forwarded to a network address corresponding to the IP address received by the multimedia device 2 at the time of IMS registration. In general, the addresses reachable to the device-based DNS service 22 are different from the IP addresses received by the device 2 during registration, since the port numbers forming part of the addresses will be different.

The subscriber device 2 receives the DNS query (on port 53). As explained above, the processing unit 26 of the device 2 executes the DNS service 22. The device-based DNS service 22 is official for the sub-domain john.smith.my-company.nl associated with the subscriber associated with device 2. The device-based DNS service 22 includes DNS resource records that are consistent with the IP service applications that are active at that time in device 2. For example, if the user has activated the HTTP service 20A in the device 2, the corresponding service application 20A places a corresponding a record in the device-based DNS service 22, the a record containing information needed to access the HTTP service 20A in the device 2. Placing the corresponding a record in the device-based DNS service 22 may include storing the a record in the memory 30. Specifically, the a record will contain the IP address where the HTTP service 20A can be accessed. Refer to fig. 9. In general, the response to the DNS query may include a network address at which the execution of the IP service application on device 2 can be accessed.

A response to the DNS query is sent 228 to the query originator 16. The response is sent 228 to the query originator 16 according to standard DNS message addressing and routing techniques. This embodiment allows a service access authorization function (utity) on the IMS subscriber device 2. Through the DNS service 22 on the device 2, the subscriber is able to control which requestor 16 gains access to the subscriber's

IP service application

20A, 20B.

The IP address provided by the device 2 in the a record may be the IP address of the IP access network 4. In this case, access to the HTTP service 20A in the device 2 does not pass through a secure IP access via the P-CSCF 5. Providing the IP address of the IP access network 4 in record a by the device 2 is advantageous because it is publicly accessible. If the device 2 provides in record a the IP address obtained by the device 2 from the P-CSCF5 in the network 1, an IP session will need to be established over the IMS network 1.

If the DNS queries 222, 224, 226 sent to device 2 are for NAPTR records, the NAPTR records sent back in response to the query contain instructions to apply SRV record queries. The domain for the SRV record query should be the domain pointing to the DNS service 22 based on the same device 2. Similarly, an SRV query to the device-based DNS service 22 should result in an instruction to apply an A record query. The domain for the a-record query should be a domain that points to the same device-based DNS service 26. An a-record query for the device-based DNS service 22 should return an IPv4 address. An AAAA record query for the device-based DNS service 22 should return an IPv6 address.

If device 2 does not have an active and working IP service application at the time of receiving a DNS query, there is also no corresponding DNS record for such service application. Thus, device 2 applies the conventional DNS response method to indicate that there is no DNS record requested.

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 setting these corresponding resource records). For example, a mobile device will typically use a short TTL value.

When a response to the DNS query reaches the query originator 16, the query originator 16 determines from the response the network address of the

IP service application

20A, 20B to be accessed. The query originator 16 then sends 230A request for the

IP service application

20A, 20B to the device 2. Upon receiving the latter request, the subscriber multimedia device 2 provides the requested IP service to the query originator 16.

In one embodiment, an IMS network subscriber uses device 2-based DNS service 22 to authorize access to one or more

auxiliary devices

24A, 24B of the subscriber. This is depicted in fig. 10. The IMS subscriber has a plurality of IP service applications executing on a plurality of

auxiliary devices

24A, 24B, which are administratively controlled by the IMS subscriber. These

auxiliary devices

24A, 24B may be additional multimedia devices 2, such as multimedia terminals. These

auxiliary devices

24A, 24B may also be other devices 2, such as dedicated devices for executing IP service applications. These auxiliary devices 24A, 24 are arranged to execute

IP service applications

20A, 20B, e.g. HTTP services or FTP services.

Fig. 11 shows a schematic representation of device 2 and device 24A (device 24B is substantially identical). The subscriber multimedia device 2 comprises a processing unit 26 arranged to execute a DNS service 22 (comprising

devices

24A, 24B) relating to a domain associated with a subscriber. As described with respect to fig. 5, the device 2 further comprises a DNS query receiver 21, a requesting unit 23, a memory 30 and a storing unit 32. In this embodiment, the requesting unit 23 is arranged to request (as from the operating system OS) information relating to the at least one

IP service application

20A, 20B from the device 24A. In this example, the information relating to the at least one IP service application 2() a, 2() B comprises a network address to which the at least one

IP service application

20A, 20B can be accessed. It will be appreciated that the DNS service 22 executed in the processing unit 26 may alternatively 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 forms part of the DNS server 22'.

The device 24A comprises a processing unit 27 arranged to execute one or more IP service applications 20A. The processing unit is further arranged to collect information relating to at least one IP service application being executed on the device 24A and to provide the information to the device 2.

The device 2 further comprises a receiving unit 28 arranged to obtain information from the device 24A relating to at least one IP service application being executed on the device 24A. The device 2 uses the secure HTTP connections 25A, 25B between the device 2 and the

devices

24A, 24B to obtain information about the IP service applications that are active and working in these

devices

24A, 24B, so that it can configure the device-based DNS service 22 accordingly. The processing unit 26 of the device 2 is further arranged to use this information to generate DNS resource records in dependence on the IP service application 20A provided by the

devices

24A, 24B at that time. The DNS resource records are stored in the memory 30. These DNS resource records will typically include NAPTR records, SRV records, and/or a records or AAAA records.

Referring again to fig. 10, access to each of the

IP service applications

20A, 20B on the

devices

24A, 24B may be obtained by a DNS query for the DNS service 22 being executed on the IMS subscriber device 2. Here the device 2 is an IMS device, such as an IMS terminal. The device-based

service applications

20A, 20B are accessed as described above. Thus, the

IP service applications

20A, 20B on the

devices

24A, 24B can be accessed by addressing information obtained from the DNS service 22 executing on the multimedia device 2, and the device 2 obtains information about the IP service applications executing on the

devices

24A, 24B, so that the DNS service 22 executing on the multimedia device 2 can be configured accordingly.

The device 2 is arranged to establish, maintain, terminate a secure HTTP connection with the

devices

24A, 24B. The DNS service 22 executing on the multimedia device 2 maintains secure HTTP connections 25A, 25B with

other devices

24A, 24B associated with the subscriber. The secure HTTP connection 25A, 25B is used to grant access to a specified IP service application on these

other devices

24A, 24B, said access being granted to the other party (entity) 16 requesting the access. Through the addressing information obtained from the DNS service 22, the requestor 16 is able to access the

IP service applications

20A, 20B on the

devices

24A, 24B. The response to the other party 16 contains the IP address of the specified IP service application on the other (associated)

device

24A, 24B. This embodiment allows a service access authorization function on the IMS subscriber device 2. The subscriber may control which requestor 16 gains access to the subscriber's

IP service application

20A, 20B through the DNS service 22 on device 2.

For example, the

IP service application

20A, 20B executing on the other (associated)

device

24A, 24B provides access only to the entity 16 that accesses the service using the same sender IP address as used for the query to the DNS server.

The secure HTTP connection 25A, 25B between the subscriber device 2 and the

device

24A, 24B associated with the subscriber may use a WLAN connection from the device 2 or use 3G or LTE access, i.e. no IMS registration for said secure HTTP is used.

It will be appreciated that the

IP service applications

20A and 20B, DNS querying receiver 21, DNS service 22, requesting unit 23, processing unit 26, processing unit 27, receiving unit 28, depositing unit 32 may be implemented as dedicated electronic circuits, possibly comprising software code portions. The

IP service applications

20A and 20B, NDS querying the receiver 21, the DNS service 22, the requesting unit 23, the processing unit 26, the processing unit 27, the receiving unit 28, the depositing unit 32 may also be implemented as software code portions executed and stored on a memory of a programmable device, such as a computer.

In the foregoing specification, the invention has been described with reference to examples of specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit of the invention.

It will be appreciated that the above described method is equally applicable to roaming subscribers, including IP access roaming, IMS roaming and nomadic users. In IP access roaming, IMS registration is run via a P-CSCF entity in the home network of the subscriber. Access to DNS services 22 being executed on the subscriber device 2 is run via a secure IMS access, via a P-CSCF entity. During registration, device 2 deposits in the HSS an indication of its capability to perform DNS services. In IMS roaming, a subscriber uses a P-CSCF entity in the visited country. The method of the invention relies on the support of the network address registration of the DNS service 22 performed on the device 2 by the P-CSCF entity used. In the case of a nomadic user, the subscriber can use a foreign wired IP access. The user attaches via the P-CSCF of the home IMS network. As described, the network address registration of the DNS service 22 performed on the device 2 is done via this P-CSCF.

A subscriber may have IMS devices in multiple operations. These devices may register with the same IMS public user identity, such as sip: smil @ my-company.nl. Each of these devices is capable of independently registering for services for the domain john. To accommodate this situation, the HSS stores the single network address for the DNS service 22 for the domain john.smith.my-company.nl at any time, e.g., the HSS stores the last registered device-based DNS service 22. Thus, when one device-based DNS service 22 registers, it takes over from the other. Alternatively, the HSS 8 stores the first registered device-based DNS service 22. Thus, if a device-based DNS service has already been registered, the newly registered device-based DNS service is not accepted.

The approach herein may be extended for distributed DNS services where multiple devices 2 of a subscriber (e.g., john. smith. my-company.nl) have a DNS service 22 associated with the domain. This is achieved, for example, by having the HSS 8 forward DNS requests to a plurality of devices 2, wherein the plurality of devices 2 deposit network addresses for their DNS services, and construct an aggregated DNS result based on responses received from the devices 2. Optionally, at any one time, the DNS service request is forwarded to at most one device.

However, other modifications, variations, and alternatives are possible. The specification, drawings, and examples are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.

The present invention relates generally to a subscriber device 2 being a multimedia device of an IP multimedia network 1. The device 2 or an

auxiliary device

24A, 24B communicatively connected to the device 2 comprises a processing unit 26, 27 arranged to execute at least one

IP service application

20A, 20B. The device 2 further comprises a DNS query receiver for receiving a DNS query. The device 2 further comprises a requesting unit 3 for requesting an identifier of at least one IP service application. The identifier includes a network address that enables access to at least one IP service application. The device 2 comprises a processing unit 26 arranged to execute the DNS service 22, and a memory 30 (arranged) to hold information relating to DNS resource records in line with the IP service application that is being executed on the device 2 at that time. The device 2 further comprises a depositing unit 32 arranged to deposit (e.g. during registration with the multimedia network 1) an indication of the capability of the device to perform the DNS service 22. The indication includes the network addresses of DNS services 22 reachable for the DNS query. The present invention also relates generally to a method for providing at least one IP service application from a subscriber 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 a DNS service 22 being executed on the device 2, the DNS service 22 relating to a domain associated with the subscriber. The DNS service 22 has a memory 30 associated therewith. The method comprises storing 206 in the memory 30 information relating to DNS resource records in line with the

IP service applications

20A, 20B that are at that time being executed on the device 2 and/or the

auxiliary devices

24A, 24B. The method further comprises depositing (e.g. during registration with the multimedia network 1) an indication of the capability of the device to perform DNS services 22. The indication includes the network addresses of DNS services 22 reachable for the DNS query.

Thus, IMS subscribers can install and run IP service applications on their devices. DNS resource records needed to access these IP service applications are set and maintained in the device. The device registers an address for its DNS service in the network (e.g. in the HSS). The method and apparatus form a general framework for enhancing the availability of IP service applications for end user devices. IP service applications that execute on a device and are accessible outside the context of a SIP session can implement many useful applications.

This provides the benefit that an IMS subscriber can install and execute IP service applications on his/her multimedia device, and that external users outside the call context can use these services. These services can be accessed through conventional DNS resource record queries. Optionally, the domain name used for accessing these IP service applications (and for DNS queries) is a regular public user identity of the subscriber structured as an aggregated domain.

The subscriber device does not deposit DNS record information in the public DNS. A device registers its DNS service address and its contact address for DNS services into the IP network. The DNS resource records are set and maintained locally in the memory of the device as required. The DNS query for the domain associated with the subscriber can be efficiently forwarded to the DNS service executing on the subscriber multimedia device 2.

In this way, the device may provide IP service applications like HTTP services, FTP services, etc. For example, activating or deactivating an HTTP service executing on a device has no impact on network information. Activating or deactivating a device-based HTTP service would only result in updating DNS resource records in the device itself.

Other possible use cases include maintaining a picture library in the memory of the (mobile) subscriber multimedia device. Photos taken in real time (or stored on the device) are saved in the device and maintained in a library local to the device. The selected viewers can access the IP service application executing on the device, which gives these viewers access to the pictures stored on the device. The device may execute an IP service application that gives (e.g., limits) public access to a web page executing on the device. The web page includes information (e.g., still pictures, video footage, geographic coordinates) collected by the device in real-time.

Roaming to or accessing via another IP access network is transparent to the network. The new device IMS registration may cause the contact address of the device based DNS server (in the HSS) to be updated.

Although an IMS network is shown in the example, it will be appreciated that the invention may be applied in other IP multimedia networks than IMS networks. For example, it is clear that the devices in fig. 5 and 11 are not limited to IMS networks by themselves.

In the claims, 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. Also, the terms "a" and "an" should not be construed as limiting to only one but are instead used to mean "at least one" and not to exclude a plurality. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Claims

1. A method for providing at least one IP service application from a terminal (2) of a subscriber in an internet protocol, IP, multimedia network (1), the method comprising the steps of:

-executing (202) at least one IP service application (20A, 20B) on the terminal (2) and/or on an auxiliary device (24A, 24B) associated with the terminal (2);

-providing (204) a domain name system, DNS, service (22) being executed on the terminal (2), the DNS service relating to a domain associated with the subscriber, the DNS service having a memory (30) associated therewith;

-storing (206), in the memory (30), information relating to DNS resource records conforming to the at least one IP service application (20A, 20B) being executed at that time on the terminal (2) and/or the secondary device (24A, 24B); and

-depositing (212, 216) with the IP multimedia network an indication of the capability of the terminal (2) to perform a DNS service (22), the indication comprising a network address of a DNS service reachable for a DNS query.

2. The method according to claim 1, wherein the domain name system DNS service (22) is performed in a DNS server on the terminal (2).

3. A method according to claim 1 or 2, wherein the IP multimedia network is an internet protocol multimedia subsystem, IMS, network, and the network address corresponds to an IP address that the terminal (2) has received at the time of IMS registration.

4. A method according to claim 1 or 2, comprising storing (212, 216) in a network entity (8) an indication of the terminal's ability to perform DNS services, the network entity (8) acting as an official naming server for a domain, the domain comprising a plurality of sub-domains, each sub-domain being associated with a public address of a subscriber, each subscriber being associated with a subscriber terminal (2).

5. The method according to claim 3, wherein the network entity (8) is a home subscriber server, HSS, of the network (1).

6. The method according to claim 5, wherein the indication of the capability of the terminal to perform DNS services (22) is included (213) in a registration message sent from the terminal (2) at the registration (5, 7) with the network and included (215) in a Diameter server assignment request, SAR, sent from the registration to the HSS (8).

7. A method according to claim 3, wherein the network address corresponds to a network address of a proxy call session control function, P-CSCF, (5) serving the terminal (2), and the P-CSCF stores an indication of the capability of the terminal to perform DNS services in a subscriber profile associated with the terminal (2) to enable the P-CSCF to forward DNS queries to the terminal.

8. A method according to claim 1 or 2, wherein the network address corresponds to an IP address of an IP access network (4), the terminal (2) accessing the network (1) via the IP access network (4).

9. The method according to claim 1 or 2, comprising:

-the terminal (2) receiving a DNS query forwarded to the terminal (2) using a network address at which a DNS service executed on the terminal (2) is currently reachable.

10. A method according to claim 3, comprising the steps of:

-routing DNS queries destined to DNS services (22) executed on the terminal (2) towards an official DNS naming server (14) of a domain associated with a group of users, the terminal being associated with a member of the group of users, wherein the naming server is configured to forward (224) all DNS queries destined to a sub-domain of the domain to a HSS (8) of an IMS operator serving the users associated with the domain, the HSS acting as the official naming server for the DNS services (22) executed on the terminals (2) of the users associated with the sub-domain of the domain.

11. The method according to claim 1 or 2, wherein a response to the DNS query received at the terminal (2) is sent to the originator (16) of the DNS query, and at least one of the at least one IP service application (20A, 20B) is provided (234) to the originator (16) of the DNS query.

12. The method according to claim 1 or 2, wherein the IP service application (20A, 20B) on the secondary device (24A, 24B) is accessible through addressing information obtained from a DNS service (22) executed on the terminal (2), wherein the terminal (2) obtains information about the IP service application being executed on the secondary device (24A, 24B) to enable the DNS service (22) executed on the terminal (2) to be configured accordingly.

13. The method of claim 12, comprising:

-a DNS service (22) executing on the terminal (2) maintaining a secure hypertext transfer protocol, HTTP, connection with the secondary device (24A, 24B).

14. A terminal (2) of a subscriber for an internet protocol, IP, multimedia network (1), the terminal comprising:

a processing unit (26) arranged to execute at least one IP service application (20A, 20B);

a receiver (21) for receiving a domain name system, DNS, query;

a requesting unit (23) for requesting an identifier of the at least one IP service application from an operating system, OS, of the terminal (2);

wherein the processing unit (26) is further arranged to perform a DNS service (22);

the terminal (2) further comprises:

a memory (30) arranged to store information relating to DNS resource records conforming to an IP service application being executed on the terminal (2) at that time; and

a depositing unit (32) arranged to deposit with the multimedia network (1) an indication of a capability of the terminal to perform a DNS service (22), the indication comprising a network address of a DNS service reachable for DNS queries.

15. A terminal (2) for a subscriber according to claim 14, arranged for use with an IP multimedia subsystem, IMS, network.

16. A terminal (2) of a subscriber for an Internet protocol, IP, multimedia network (1), the terminal being integrated with an auxiliary device (24A, 24B), the terminal (2) being communicatively connectable with the auxiliary device (24A, 24B),

the auxiliary device (24A, 24B) comprises:

-a processing unit (27) arranged to execute at least one IP service application (20A, 20B);

the terminal (2) comprises:

-a receiver (21) for receiving a domain name system, DNS, query;

-a requesting unit (23) for requesting an identifier of the at least one IP service application;

-a second receiver (28) for receiving information about an IP service application (20A, 20B) being executed in the auxiliary device (24A, 24B);

-a processing unit (26) arranged to perform a DNS service (22);

-a memory (30) arranged to store information relating to DNS resource records in line with IP service applications being executed in the secondary device (24A, 24B) at that time; and

-a depositing unit (32) arranged to deposit with the multimedia network (1) an indication of the capability of the terminal to perform a DNS service (22), the indication comprising a network address of a DNS service reachable for a DNS query.

17. A terminal for a subscriber according to claim 16, arranged for use with an IP multimedia subsystem, IMS, network.

18. A subscriber's terminal according to claim 16, wherein the terminal (2) comprises a secure connection unit for maintaining a secure hypertext transfer protocol, HTTP, connection with the auxiliary device (24A, 24B).

19. An internet protocol, IP, multimedia network (1) comprising a terminal (2) or a combination according to any of claims 14-18, and a network entity (8),

wherein the network entity (8) is arranged to store an indication of the terminal's ability to perform DNS services (22), the network entity acting as an official naming server for a domain comprising a plurality of sub-domains, each sub-domain being associated with a public address of a subscriber, each subscriber being associated with a subscriber terminal.

20. A network entity (8) for an internet protocol, IP, multimedia network, wherein the network entity (8) is arranged to receive and store an indication of a terminal's ability to perform DNS services (22), the network entity acting as an official naming server for a domain, the domain comprising a plurality of sub-domains, each sub-domain being associated with a public address of a subscriber, each subscriber being associated with a subscriber terminal.

21. A computer readable storage medium storing software code portions arranged, when run on a terminal of a programmable subscriber, to perform the steps of:

-determining the presence of at least one IP service application (20A, 20B) being executed on the terminal (2) and/or on an auxiliary device (24A, 24B) associated with the terminal (2);

-providing a domain name system, DNS, service (22) on the terminal (2), the DNS service relating to a domain associated with the subscriber, the DNS service having a memory (30) associated therewith;

-storing in said memory information relating to DNS resource records conforming to said at least one IP service application (20A, 20B) being executed at that time on said terminal (2) and/or said secondary device (24A, 24B); and

-an indication indicating that the IP multimedia network (1) with which the terminal (2) is registered or which requests registration with the terminal (2) deposits the capability of the terminal to perform DNS services (22), the indication comprising network addresses of DNS services reachable for DNS queries.