Method, apparatus and computer program

Abstract

A method, apparatus and computer program are provided for execution by a home subscriber server or a unified data management function, the method comprising: receiving one or more Internet Protocol Multimedia Subsystem (IMS) application servers (IMS AS) from one or more IMS profiles, each IMS configuration file comprises IMS AS identification information and one or more parameters of the corresponding IMS AS in the one or more IMS AS; storing the received one or more IMS configuration files; receiving a second message from the consumer network function, the second message comprising a discovery request indicating that the target network function type is IMS AS and one or more target parameters; and sending an IMS profile including one or more parameters matching the one or more target parameters to the consumer network function.

Description

Technical Field

[0001] Various example embodiments of the present disclosure are directed to methods, apparatus, systems and computer programs, particularly but not limited to enabling (or otherwise facilitating) IMS AS discovery via an HSS or UDM. Background Art

[0002] A communication network can be seen as a facility that enables communication between two or more communication devices or provides communication devices with access to a data network. A mobile or wireless communication network is an example of a communication network. Communication devices may be served by application servers.

[0003] Such communication networks operate according to standards provided by 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards are the so-called 5G (fifth generation) standards provided by 3GPP.

[0004] In some communication networks, an Internet Protocol Multimedia Service (IMS) application server (AS) may be deployed. The IMS AS may provide IMS multimedia telephony services to devices within the network. For example, this may enable different network functions and different types of devices (e.g., augmented reality (AR), virtual reality (VR), extended reality (XR) devices, robots, etc.) to be supported. As used herein, the services provided by the IMS AS may be referred to as "IMS services". Summary of the invention

[0005] Some example embodiments of the present disclosure will be described with respect to certain aspects. These aspects are not intended to indicate the key or essential features of the embodiments of the present disclosure, nor are they intended to be used to limit the scope thereof. In view of the present disclosure, other features, aspects, and elements will be apparent to those skilled in the art.

[0006] According to one aspect, a device is provided, including a component for providing a home subscriber server or a unified data management function, the component being configured to perform: receiving one or more Internet Protocol Multimedia Subsystem (IMS) profiles from one or more IMS application servers (IMS ASs), each IMS profile including IMS AS identification information, and one or more parameters of a corresponding IMS AS in the one or more IMS ASs; storing the received one or more IMS profiles; receiving a second message including a discovery request from a consumer network function, the discovery request indicating that: a target network function type is IMS AS, and one or more target parameters; and sending the IMS profile to the consumer network function, the IMS profile including one or more parameters matching the one or more target parameters.

[0007] The one or more parameters may include at least one of the following: information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services that can be opened by the IMS AS, and one or more events.

[0008] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0009] One or more IMS profiles may be stored at a Home Subscriber Server or a Unified Data Management Function and associated with one or more user identifiers.

[0010] The one or more target parameters may include at least one of the following: information indicating one or more target IMS services provided by the IMS AS; information indicating one or more target users for which the IMS AS supports IMS services; information indicating one or more target user groups for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more target events.

[0011] The first message and / or the second message may include one of the following: a diameter protocol message, or a service-based interface message.

[0012] The first message may be a diameter protocol message and may include a configuration file update request or a server assignment request.

[0013] The component can be used to provide a home subscriber server or a unified data management function, and is also configured to perform: determining that no IMS profile including one or more parameters matching one or more target parameters is stored at the home subscriber server or the unified data management function; creating a subscription associated with a consumer network function based on the one or more target parameters; receiving an additional IMS profile from the IMS AS, wherein the additional IMS profile includes one or more parameters matching the one or more target parameters; and sending a notification message to the consumer network function, the notification message including the IMS profile, the IMS profile including one or more parameters matching the one or more target parameters.

[0014] According to one aspect, an apparatus is provided, comprising a component for providing a consumer network function, the component being configured to perform: sending a second message to a home subscriber server or a unified data management function, the second message comprising a discovery request, the discovery request indicating: a target network function type is an Internet Protocol Multimedia Subsystem Application Server IMS AS, and one or more filter parameters defining one or more target parameters; receiving an IMS profile from the home subscriber server or the unified data management function based on the one or more filter parameters; and connecting to the IMS AS based on the received IMS profile.

[0015] The one or more target parameters may include at least one of the following: information indicating one or more target IMS services provided by the IMS AS; information indicating one or more target users for which the IMS AS supports IMS services; information indicating one or more target user groups for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more target events.

[0016] The received IMS configuration file may include at least one of the following: IMS AS identification information; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more events.

[0017] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0018] The IMS AS identification information may include an IMS AS instance identifier or an IMS AS set identifier, wherein the component may be used to provide a consumer network function, and is further configured to: send a third message to a network repository function, the third message including an additional discovery request indicating the IMS AS instance identifier or the IMS AS set identifier; receive an IMS AS address based on the third message from the network repository function; and connect to the IMS AS based on the received IMS AS address.

[0019] The additional discovery request may also include at least one of the following: an indication that service exposure via a network exposure function is supported; information indicating supported capabilities of the IMS AS; information identifying one or more users of the IMS AS; information identifying one or more user groups of the IMS AS; or information indicating one or more user categories supported by the IMS AS.

[0020] The third message may include a diameter protocol request or a service-based interface request.

[0021] According to one aspect, a device is provided, including a component for providing an Internet Protocol Multimedia Subsystem Application Server IMS AS, which is configured to perform: providing IMS services to one or more users, or one or more user groups; and sending a first message to a home subscriber server or a unified data management function, the first message including an IMS profile of the IMS AS.

[0022] The first message may include one of the following: a diameter protocol message, or a service-based interface message.

[0023] Diameter protocol messages may include configuration file update requests or server assignment requests.

[0024] The IMS configuration file may include at least one of the following: IMS AS identification information; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more events.

[0025] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0026] The component can be used to provide an IMS AS, and is also configured to execute: sending a registration message to a network repository function, the registration message including at least one of the following: information indicating whether the IMS AS supports service opening via a network opening function; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users, for which the IMS AS supports IMS services; information indicating one or more user groups, for which the IMS AS supports IMS services; information indicating one or more user categories, for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS, and one or more events.

[0027] According to one aspect, a device is provided, comprising at least one processor and at least one memory, wherein the at least one memory stores instructions, which, when executed by the at least one processor, causes the device to at least: receive one or more Internet Protocol Multimedia Subsystem (IMS) profiles from one or more IMS application servers (IMS ASs), each IMS profile comprising IMS AS identification information and one or more parameters of a corresponding IMS AS in the one or more IMS ASs; store the received one or more IMS profiles; receive a second message comprising a discovery request from a consumer network function, wherein the discovery request indicates that a target network function type is an IMS AS, and one or more target parameters; and send an IMS profile to the consumer network function, wherein the IMS profile comprises one or more parameters matching the one or more target parameters.

[0028] The one or more parameters may include at least one of the following: information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services that can be opened by the IMS AS, and one or more events.

[0029] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0030] One or more IMS profiles may be stored at a Home Subscriber Server or a Unified Data Management Function and associated with one or more user identifiers.

[0031] The one or more target parameters may include at least one of the following: information indicating one or more target IMS services provided by the IMS AS; information indicating one or more target users for which the IMS AS supports IMS services; information indicating one or more target user groups for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more target events.

[0032] The first message and / or the second message may include one of the following: a diameter protocol message, or a service-based interface message.

[0033] The first message may be a diameter protocol message and may include a configuration file update request or a server assignment request.

[0034] The instructions, when executed by at least one processor, may also cause the apparatus to: determine that no IMS profile including one or more parameters matching the one or more target parameters is stored at a home subscriber server or a unified data management function; create a subscription associated with a consumer network function based on the one or more target parameters; receive an additional IMS profile from the IMS AS, wherein the additional IMS profile includes one or more parameters matching the one or more target parameters; and send a notification message to the consumer network function, the notification message including the IMS profile including the one or more parameters matching the one or more target parameters.

[0035] According to one aspect, a device is provided, comprising at least one processor and at least one memory, wherein the at least one memory stores instructions, which when executed by the at least one processor causes the device to at least: send a second message to a home subscriber server or a unified data management function, the second message comprising a discovery request, the discovery request indicating that a target network function type is an Internet Protocol Multimedia Subsystem Application Server IMS AS, and one or more filter parameters defining one or more target parameters; receive an IMS profile from the home subscriber server or the unified data management function based on the one or more filter parameters; and connect to the IMS AS based on the received IMS profile.

[0036] The one or more target parameters may include at least one of the following: information indicating one or more target IMS services provided by the IMS AS; information indicating one or more target users for which the IMS AS supports IMS services; information indicating one or more target user groups for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more events.

[0037] The received IMS configuration file may include at least one of the following: IMS AS identification information; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more events.

[0038] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0039] The IMS AS identification information may include an IMS AS instance identifier or an IMS AS set identifier, wherein the component may be used to provide a consumer network function, and is further configured to: send a third message to a network repository function, the third message including an additional discovery request indicating the IMS AS instance identifier or the IMS AS set identifier; receive an IMS AS address based on the third message from the network repository function; and connect to the IMS AS based on the received IMS AS address.

[0040] The additional discovery request may also include at least one of the following: an indication that service exposure via a network exposure function is supported; information indicating supported capabilities of the IMS AS; information identifying one or more users of the IMS AS; information identifying one or more user groups of the IMS AS; or information indicating one or more user categories supported by the IMS AS.

[0041] The third message may include a diameter protocol request or a service-based interface request.

[0042] According to one aspect, a device is provided, comprising at least one processor and at least one memory, wherein the at least one memory stores instructions, which when executed by the at least one processor causes the device to at least: provide IMS services to one or more users, or one or more user groups; and send a first message to a home subscriber server or a unified data management function, wherein the first message includes an IMS profile of an IMS AS.

[0043] The first message may include one of the following: a diameter protocol message or a service-based interface message.

[0044] Diameter protocol messages may include configuration file update requests or server assignment requests.

[0045] The IMS configuration file may include at least one of the following: IMS AS identification information; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more events.

[0046] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0047] When executed by at least one processor, the instruction can also cause the device to: send a registration message to a network repository function, the registration message including at least one of the following: information indicating whether the IMS AS supports service opening via a network opening function; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users, for which the IMS AS supports IMS services; information indicating one or more user groups, for which the IMS AS supports IMS services; information indicating one or more user categories, for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS, and one or more events.

[0048] According to one aspect, a method performed by a home subscriber server or a unified data management function is provided, the method comprising: receiving one or more Internet Protocol Multimedia Subsystem (IMS) profiles from one or more IMS application servers (IMS ASs), each IMS profile comprising IMS AS identification information and one or more parameters of corresponding IMS ASs in one or more IMS ASs; storing the received one or more IMS profiles; receiving a second message comprising a discovery request from a consumer network function, the discovery request comprising an indication that the target network function type is an IMS AS, and one or more target parameters; and sending the IMS profile to the consumer network function, the IMS profile comprising one or more parameters matching the one or more target parameters.

[0049] The one or more parameters may include at least one of the following: information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services that can be opened by the IMS AS, and one or more events.

[0050] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0051] One or more IMS profiles may be stored at a Home Subscriber Server or a Unified Data Management Function and associated with one or more user identifiers.

[0052] The one or more target parameters may include at least one of the following: information indicating one or more target IMS services provided by the IMS AS; information indicating one or more target users for which the IMS AS supports IMS services; information indicating one or more target user groups for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more target events.

[0053] The first message and / or the second message may include one of the following: a diameter protocol message, or a service-based interface message.

[0054] The first message may be a diameter protocol message and may include a configuration file update request or a server assignment request.

[0055] The method may also include: determining that no IMS profile including one or more parameters matching the one or more target parameters is stored at the home subscriber server or the unified data management function; creating a subscription associated with the consumer network function based on the one or more target parameters; receiving an additional IMS profile from the IMS AS, wherein the additional IMS profile includes one or more parameters matching the one or more target parameters; and sending a notification message to the consumer network function, the notification message including the IMS profile including the one or more parameters matching the one or more target parameters.

[0056] According to one aspect, a method performed by a consumer network function is provided, the method comprising: sending a second message to a home subscriber server or a unified data management function, the second message comprising a discovery request, the discovery request indicating that the target network function type is an Internet Protocol Multimedia Subsystem Application Server IMS AS, and one or more filter parameters defining one or more target parameters; receiving an IMS profile from the home subscriber server or the unified data management function based on the one or more filter parameters; and connecting to the IMS AS based on the received IMS profile.

[0057] The one or more target parameters may include at least one of the following: information indicating one or more target IMS services provided by the IMS AS; information indicating one or more target users for which the IMS AS supports IMS services; information indicating one or more target user groups for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more target events.

[0058] The received IMS configuration file may include at least one of the following: IMS AS identification information; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more events.

[0059] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0060] The IMS AS identification information may include an IMS AS instance identifier or an IMS AS set identifier, wherein the component may be used to provide a consumer network function, and is further configured to: send a third message to a network repository function, the third message including an additional discovery request indicating the IMS AS instance identifier or the IMS AS set identifier; receive an IMS AS address based on the third message from the network repository function; and connect to the IMS AS based on the received IMS AS address.

[0061] The additional discovery request may also include at least one of the following: an indication that service exposure via a network exposure function is supported; information indicating supported capabilities of the IMS AS; information identifying one or more users of the IMS AS; information identifying one or more user groups of the IMS AS; or information indicating one or more user categories supported by the IMS AS.

[0062] The third message may include a diameter protocol request or a service-based interface request.

[0063] According to one aspect, a method performed by an Internet Protocol Multimedia Subsystem Application Server (IMS AS) is provided, the method comprising: providing IMS services to one or more users, or one or more user groups; and sending a first message to a home subscriber server or a unified data management function, the first message comprising an IMS profile of the IMS AS.

[0064] The first message may include one of the following: a diameter protocol message or a service-based interface message.

[0065] Diameter protocol messages may include configuration file update requests or server assignment requests.

[0066] The IMS configuration file may include at least one of the following: IMS AS identification information; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more events.

[0067] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0068] The method may also include: sending a registration message to a network repository function, the registration message including at least one of the following: information indicating whether the IMS AS supports service opening via a network opening function; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users, for which the IMS AS supports IMS services; information indicating one or more user groups, for which the IMS AS supports IMS services; information indicating one or more user categories, for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS, and one or more events.

[0069] According to one aspect, a computer-readable medium is provided, the computer-readable medium comprising instructions, which when executed by an apparatus causes the apparatus to perform at least the following: receiving one or more Internet Protocol Multimedia Subsystem (IMS) profiles from one or more IMS application servers (IMS ASs), each IMS profile comprising IMS AS identification information and one or more parameters of a corresponding IMS AS in the one or more IMS ASs; storing the received one or more IMS profiles; receiving a second message comprising a discovery request from a consumer network function, the discovery request comprising an indication that a target network function type is an IMS AS, and one or more target parameters; and sending the IMS profile to the consumer network function, the IMS profile comprising one or more parameters matching the one or more target parameters.

[0070] The one or more parameters may include at least one of the following: information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services that can be opened by the IMS AS, and one or more events.

[0071] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0072] One or more IMS profiles may be stored at a Home Subscriber Server or a Unified Data Management Function and associated with one or more user identifiers.

[0073] The one or more target parameters may include at least one of the following: information indicating one or more target IMS services provided by the IMS AS; information indicating one or more target users for which the IMS AS supports IMS services; information indicating one or more target user groups for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more target events.

[0074] The first message and / or the second message may include one of the following: a diameter protocol message or a service-based interface message.

[0075] The first message may be a diameter protocol message and may include a configuration file update request or a server assignment request.

[0076] The instructions, when executed by the device, may cause the device to further perform: determining that no IMS profile including one or more parameters matching the one or more target parameters is stored at the home subscriber server or the unified data management function; creating a subscription associated with a consumer network function based on the one or more target parameters; receiving an additional IMS profile from the IMS AS, wherein the additional IMS profile includes one or more parameters matching the one or more target parameters; and sending a notification message to the consumer network function, the notification message including the IMS profile including the one or more parameters matching the one or more target parameters.

[0077] According to one aspect, a computer-readable medium is provided, the computer-readable medium comprising instructions, which when executed by an apparatus causes the apparatus to perform at least the following: sending a second message to a home subscriber server or a unified data management function, the second message comprising a discovery request, the discovery request indicating that: a target network function type is an Internet Protocol Multimedia Subsystem Application Server IMS AS, and one or more filter parameters defining one or more target parameters; receiving an IMS profile from the home subscriber server or the unified data management function based on the one or more filter parameters; and connecting to the IMS AS based on the received IMS profile.

[0078] The one or more target parameters may include at least one of the following: information indicating one or more target IMS services provided by the IMS AS; information indicating one or more target users for which the IMS AS supports IMS services; information indicating one or more target user groups for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more target events.

[0079] The received IMS configuration file may include at least one of the following: IMS AS identification information; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more events.

[0080] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0081] The IMS AS identification information may include an IMS AS instance identifier or an IMS AS set identifier, wherein the component may be used to provide a consumer network function, and is further configured to: send a third message to a network repository function, the third message including an additional discovery request indicating the IMS AS instance identifier or the IMS AS set identifier; receive an IMS AS address based on the third message from the network repository function; and connect to the IMS AS based on the received IMS AS address.

[0082] The additional discovery request may also include at least one of the following: an indication that service exposure via a network exposure function is supported; information indicating supported capabilities of the IMS AS; information identifying one or more users of the IMS AS; information identifying one or more user groups of the IMS AS; or information indicating one or more user categories supported by the IMS AS.

[0083] The third message may include a diameter protocol request or a service-based interface request.

[0084] According to one aspect, a computer-readable medium is provided, the computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: provide IMS services to one or more users, or one or more user groups; and send a first message to a home subscriber server or a unified data management function, the first message comprising an IMS profile of an IMS AS.

[0085] The first message may include one of the following: a diameter protocol message or a service-based interface message.

[0086] Diameter protocol messages may include configuration file update requests or server assignment requests.

[0087] The IMS configuration file may include at least one of the following: IMS AS identification information; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS and one or more events.

[0088] The IMS AS identification information may include at least one of the following: an IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or an IMS AS diameter address of the IMS AS.

[0089] When the instruction is executed by the device, it can cause the device to also execute: sending a registration message to the network repository function, the registration message including at least one of the following: information indicating whether the IMS AS supports service opening via the network opening function; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users, for which the IMS AS supports IMS services; information indicating one or more user groups, for which the IMS AS supports IMS services; information indicating one or more user categories, for which the IMS AS supports IMS services; or information indicating services opened by the IMS AS, and one or more events.

[0090] According to one aspect, a non-transitory computer-readable medium is provided, comprising program instructions, which when executed by an apparatus causes the apparatus to at least perform a method according to any of the preceding aspects.

[0091] In the above, many different aspects have been described. It should be understood that further aspects can be provided by combining any two or more of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0092] Some example embodiments will now be described, by way of non-limiting and illustrative examples only, with reference to the accompanying drawings, in which:

[0093] Figure 1 A representation of a fifth generation communication system is shown;

[0094] Figure 2 A method for performing a Figure 1 Representation of the devices of the communication system;

[0095] Figure 3 shows representations of apparatus according to some example embodiments;

[0096] Figure 4 shows an example network architecture including an IMS AS for providing AR functionality according to some example embodiments;

[0097] FIG5 illustrates a method according to some example embodiments;

[0098] Figure 6 shows a signaling exchange according to some example embodiments; and

[0099] Figure 7 Schematic representations of non-volatile memory media are shown according to some example embodiments. DETAILED DESCRIPTION

[0100] A non-exhaustive list of some abbreviations used in this disclosure is provided below for reference:

[0101] AS – Application Server

[0102] DC – Data Channel

[0103] HSS – Home Subscriber Server

[0104] IMPI – IMS Private User Identity

[0105] IMPU – IMS Public User Identity

[0106] IMS – IP Multimedia Subsystem

[0107] MCC – Mission Critical Communications

[0108] MMTel – Multimedia Telephone

[0109] NEF – Network Open Function

[0110] RCS – Rich Communication Services

[0111] SDP – Session Description Protocol

[0112] SIP – Session Initiation Protocol

[0113] UDM – Unified Data Management

[0114] UE – User Equipment

[0115] In the following, various exemplary embodiments are explained with reference to a communication device capable of communicating with a communication system. Before explaining in detail various exemplary embodiments of the method and apparatus of the present disclosure, a fifth generation communication system (5GS), its access network and core network (5GC), and a communication device are explained with reference to Figure 1 , 2 and 3 are briefly explained.

[0116] Figure 1 A schematic representation of a 5G communication system (5GS) is shown. The 5GS may include a user equipment (UE) or terminal 100, an access network (such as a 5G radio access network (5G-RAN) 101 or a next generation radio access network (NG-RAN), a 5G core network 102, and one or more application functions 103. The application functions 103 may be deployed in the 5GS as trusted application functions, or may be deployed or hosted on one or more application servers of a data network (DN) 104. Such application functions are non-trusted application functions. The 5GS connects the UE to the data network, the access network, and the 5GC 102 (e.g., the UPF of the 5GC).

[0117] 5G-RAN 101 may include one or more radio access nodes, such as gNodeB (gNB). A gNB may include one or more gNodeB (GNB) distributed units connected to one or more gNodeB (GNB) centralized units.

[0118] 5GC may include the following network functions: network slice selection function (NSSF); network open function (NEF) 105; network repository function (NRF); policy control function (PCF); unified data management (UDM) 106; application function (AF) 103; authentication server function (AUSF) 107; access and mobility management function (AMF) 108; session management function (SMF) 109; and user plane function (UPF) 110. Figure 1 Also shown are various interfaces (N1, N2, etc.) that may be implemented between the various elements of the system.

[0119] Figure 2 Shows the control Figure 1 The access network shown in Figure 1 2. The control device 200 may include at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and a network interface 214. At least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215. The execution of the software code 215 may, for example, cause the device to perform operations for controlling functions of accessing the network. The software code 215 may be stored in the ROM 211b. The control device 200 may be interconnected with another control device 200 (for controlling another function of the 5G-RAN or NG-RAN). In some embodiments, each function of the 5G-RAN or NG-RAN is deployed or hosted on the control device 200. In an alternative embodiment, two or more functions of the 5G-RAN or NG-RAN may share a control device.

[0120] Figure 3 An example of a communication device 300 is shown, such as Figure 1UE shown in . The communication device 300 can be provided by any device capable of sending and receiving radio signals. Non-limiting and illustrative examples of the communication device 300 include user equipment, a mobile station (MS) or a mobile device (such as a mobile phone or a so-called "smartphone"), a computer provided with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA) or tablet computer provided with wireless communication capabilities, a machine type communication (MTC) device, an Internet of Things (IoT) type communication device, or any combination of these devices, etc. The communication device 300 may include a transceiver for sending and / or receiving, for example, wireless signals (e.g., radio signals) that carry communications. The communication may be one or more of voice, electronic mail (email), text messages, multimedia data, machine data, etc.

[0121] The communication device 300 may receive wireless signals (eg, radio signals) over the air or radio interface 307 via appropriate means for receiving, and may transmit wireless signals via appropriate means for transmitting radio signals. Figure 3 , a transceiver is schematically designated by block 306. The transceiver 306 may include, for example, a radio portion and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device and may include one or more antenna elements. The antenna arrangement may be a multiple input multiple output (MIMO) antenna.

[0122] The communication device 300 may be provided with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b and possibly other components 303 (for use in software and hardware assisted execution of the tasks it is designed to perform), including control of access to a network (e.g. Figure 1 302a. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 may be configured to execute appropriate software code 308. The software code 308 may, for example, allow execution of one or more operations of the communication device. The software code 308 may be stored in the ROM 302a.

[0123] The processor, ROM, RAM, transceiver and other circuit systems (e.g., modem) of the communication device may be provided on a circuit board, or in a chipset or system on chip. The circuit board, chipset or system on chip is represented by reference numeral 304. The communication device 300 may optionally have a user interface, such as a keyboard 305, a touch screen or touchpad, a combination thereof, etc. Optionally, one or more of a display, a speaker and a microphone may be provided, depending on the type of communication device.

[0124] As described above, in some examples, an IMS AS may be deployed to provide IMS services to devices within a communications network. Figure 4 An example network architecture including an IMS AS for providing AR functionality according to some example embodiments is shown.

[0125] Figure 4 The example architecture 4 includes an AR application server 400, a network exposure function (NEF) 105, a data channel signaling function (DCSF) 401, a DC application repository (DCAR) 402, an (IMS) home subscriber server (HSS) 403, an IMS AS 404, a multimedia function (MF) / multimedia resource function (MRF) 405, an interrogation / serving call session control function (I / S-CSCF) 406, an interconnection border control function (IBCF) 407, a proxy-CSCF (P-CSCF) 408, an IMS application gateway (IMS-AGW) 409, a translation gateway (TrGW) 410, a remote IMS 411, and a UE 101. Various interfaces (e.g., N33, DC3, Mx, Mb, etc.) between various network elements are also shown.

[0126] AR AS 400 may be responsible for AR service control related to AR communication, including AR session media control, AR media capability negotiation with UE 101. MF / MRF 405 may support AR media processing, and may receive and store AR service media processing logic from AR AS 400, and provide augmented reality MF capabilities based on AR data received from UE 101. IMS AS 404 may receive media control instructions from DCSF 401 and interact with UE 101 to terminate the UE's audio / video media connection to the MF.

[0127] One challenge facing network deployments that include an IMS AS 404 is how to expose IMS AS services to consumer network functions within the network. For example, the following: how does a consumer network function determine the existence of an IMS AS 404, what services the IMS AS 404 can provide, the address of the IMS AS 404, which user(s) or user group(s) can be served by the IMS AS 404, etc. This may be important for a consumer network function to be able to discover the IMS AS 404 and subscribe to the IMS services provided by the IMS AS 404.

[0128] One potential solution to this problem would be to have the Network Open Function (NEF) 105 perform the service opening. To do this, the NEF 105 needs to determine the serving IMS AS 404 for one or more IMS users. However, this is not possible under existing standard network architectures because the necessary information is known to the S-CSCF 406. In addition, the S-CSCF 406 may only have information about the Session Initiation Protocol (SIP) address of the IMS AS 404, while in certain use cases, further information (such as an http address) may be necessary for appropriate service opening. Although the S-CSCF information is known to the HSS 403, the information is unknown to the NEF 105, so the NEF 105 has no direct way to discover the serving IMS AS 404 for a given user.

[0129] Some examples of the present disclosure provide mechanisms for enabling (or otherwise facilitating) discovery and service exposure of IMS AS 404. In some examples, HSS 403 or UDM 106 stores an IMS profile of IMS AS 404. In some examples, HSS 403 or UDM 106 provides information to a consumer network function to enable (or otherwise facilitate) the consumer network function to discover an IMS AS 404 with specific characteristics (e.g., an IMS AS that provides specific IMS services, an IMS AS that provides IMS services to certain users, etc.) and connect to the discovered IMS AS.

[0130] Referring to FIG. 5 , a method according to some example embodiments is shown.

[0131] Figure 5a A method performed by a home subscriber server or a unified data management function according to some examples is shown. At 500, the method includes receiving one or more Internet Protocol Multimedia Subsystem (IMS) profiles from one or more IMS application servers (IMS ASs), each IMS profile including IMS AS identification information, and one or more parameters of a corresponding IMS AS in one or more IMS ASs. At 502, the method includes storing the received one or more IMS profiles. At 504, the method includes receiving a second message from a consumer network function, the second message including a discovery request, the discovery request indicating that the target network function type is an IMS AS, and one or more target parameters. At 506, the method includes sending an IMS profile to the consumer network function, the IMS profile including one or more parameters matching the one or more target parameters.

[0132] In some examples, a home subscriber server (HSS) or a unified data management function (UDM) may receive a single IMS profile from a single IMS AS. In some examples, a home subscriber server (HSS) or a unified data management function (UDM) may receive multiple IMS profiles (e.g., an initial IMS profile and an updated IMS profile) from a single IMS AS. In some examples, a home subscriber server (HSS) or a unified data management function (UDM) may receive multiple IMS profiles from multiple IMS ASs (e.g., one IMS profile from each IMS AS, and any updates to the IMS profiles from the multiple IMS ASs).

[0133] Figure 5b A method performed by a consumer network function according to some examples is shown. At 508, the method includes sending a second message to a home subscriber server or a unified data management function, the second message including a discovery request, the discovery request indicating that the target network function type is an Internet Protocol Multimedia Subsystem Application Server IMS AS, and one or more filter parameters defining one or more target parameters. At 510, the method includes receiving an IMS profile from the home subscriber server or the unified data management function based on the one or more filter parameters. At 512, the method includes connecting to the IMS AS based on the received IMS profile.

[0134] Figure 5c shows a method performed by an Internet Protocol Multimedia Subsystem Application Server IMS AS according to some examples. At 514, the method includes: providing IMS services to one or more users, or one or more user groups. At 516, the method includes sending a first message including an IMS profile of the IMS AS to a home subscriber server or a unified data management function.

[0135] Although reference is made to the IMS AS in the present disclosure, it should be understood that in some examples, the IMS AS may be replaced by another network entity that performs the same (or substantially the same) functions as the IMS AS. That is, in some examples, a network entity (which may be referred to as the IMS AS or others) may perform methods belonging to the IMS AS as disclosed herein.

[0136] refer to Figure 6 , which illustrates a signaling exchange according to some example embodiments.

[0137] At 600, the IMS AS 404 sends a message including the NF profile of the IMS AS 404 to the NRF. The message may be, for example, an Nnrf_NFmanagement_Registration message. The NF profile may include one or more parameters defined in 3GPP TS 29.510 clause 6.1.6.2.2, and / or at least one of the following IMS AS parameters:

[0138] Information indicating whether the IMS AS 404 supports service opening via the NEF 105. For example, this may be a flag that is set when the IMS AS 404 supports service opening via the NEF 105 and is not set when the IMS AS 404 does not support service opening via the NEF 105;

[0139] Information indicating the IMS services supported by the IMS AS 404 - e.g., Data Channel (DC), Multimedia Telephony (MMTel), Rich Communication Services (RCC), Presence, Mission Critical Communications (MCC), etc.;

[0140] Information indicating one or more users for which the IMS AS 404 supports IMS services. For example, this may be provided as an IMS Public User Identity (IMPU) or an IMS Private Identity (IMPI);

[0141] Information indicating one or more user groups for which the IMS AS 404 supports IMS services. For example, this may be provided as an IMPU / IMPI or a wildcard IMPU (e.g., an IMPU containing a regular expression, such as all IMPUs starting with a certain sequence of digits, such as "1234") or a group identifier;

[0142] Information indicating one or more user categories for which the IMS AS 404 supports IMS services—e.g., whether the user is a regular user, a priority user, an enterprise user, etc.; or

[0143] Information indicating one or more events supported by the IMS AS 404 - for example, CallEstablished, CallTerminated, PresenceService, RCSService, etc.

[0144] At 602, the NRF stores the NF profile based on the message received at 600. In some examples, one or more IMS AS profiles may be stored at HSS 403 or UDM 106 and associated with one or more user identifiers. The NRF may send an acknowledgement to IMS AS 404 at 604 indicating that the NF profile has been stored.

[0145] At 606, IMS AS 404 starts providing IMS services to one or more users or one or more groups of users (eg, one or more UEs, such as UE 101).

[0146] At 608, IMS AS 404 registers with HSS 403 or UDM 106. For example, IMS AS 404 may send a first message to HSS 403 or UDM 106, the first message including an IMS profile of IMS AS 404.

[0147] The IMS configuration file may include IMS identification information and one or more parameters. The one or more parameters may include, for example, at least one of the following: information indicating one or more IMS services provided by the IMS AS 404; information indicating services opened by the IMS AS 404, or one or more events; or information indicating user identities of one or more users, group identities of one or more user groups, or users of one or more user categories to which the IMS AS 404 provides IMS services at 606, etc.

[0148] The IMS identification information may include at least one of the following:

[0149] IMS AS instance identifier or IMS AS set identifier;

[0150] a Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) via which the IMS AS 404 can be reached; or

[0151] The IMS AS diameter address of IMS AS 404.

[0152] In some examples, the first message may include a diameter protocol message (e.g., a profile update request message, a server assignment request message, or any other diameter protocol message may be used) or a service-based interface (SBI) message (e.g., a Nhss_imsUECM_registration message).

[0153] At 610, HSS 403 or UDM 106 stores the received one or more IMS profiles. Optionally, HSS 403 or UDM 106 may send an acknowledgment to one or more IMS ASs. For example, the acknowledgment may be a PUR response message.

[0154] In some examples, HSS 403 may receive the IMS profile(s) at 608 and store the IMS profile(s) at HSS 403 at 610. In some examples, UDM 106 may receive the IMS profile(s) at 608 and store the IMS profile(s) at UDM 106 at 610. In some examples, HSS 403 may receive the IMS profile(s) at 608 and store the IMS profile(s) at UDM 106 at 610, wherein HSS 403 communicates with UDM 106. For example, HSS 403 may receive the IMS profile(s) at 608 and send a message including the received IMS profile(s) to UDM 106, and UDM 106 may store the received IMS profile(s).

[0155] Although only one IMS AS 404 Figure 6 , but it should be understood that in some examples, there may be multiple IMS ASs. Each IMS AS may perform steps 600-610 as described above. Therefore, in some examples, HSS 403 or UDM 106 may receive an IMS configuration file from each of the multiple IMS ASs. More generally, there may be one or more IMS ASs, and HSS 403 or UDM 106 may receive an IMS configuration file from each of the one or more IMS ASs. That is, HSS 403 or UDM 106 may receive and store one or more IMS configuration files of one or more IMS ASs, wherein each IMS configuration file includes IMS AS identification information and one or more parameters of a corresponding IMS AS in the one or more IMS ASs.

[0156] At 612, the customer network function sends a second message including a discovery request to the HSS 403 or the UDM 106. The discovery request may indicate a target network function type of IMS AS, and one or more target parameters.

[0157] The one or more target parameters may define the parameters / characteristics of the IMS AS that the customer network function wants to discover. For example, the one or more target parameters may include at least one of the following:

[0158] One or more target IMS services provided by the IMS AS - e.g. DC, MMTel, RCS, Presence, MCC, etc.

[0159] One or more target users (e.g., IMPUs or IMPIs) for which the IMS AS supports IMS services;

[0160] one or more target user groups for which the IMS AS supports IMS services (e.g., IMPU / IMPI or wildcard IMPU or group identifier); or

[0161] One or more target events supported by the IMS AS (e.g., CallEstablished, CallTerminated, PresenceService, RCSService, MissionCriticalService, EmergencyService, etc.)

[0162] In some examples, the second message may include a diameter protocol message (e.g., a User Data Request message) or an SBI message (e.g., a Nhss_imsUECM_get message).

[0163] The consumer network function may be any network function, such as but not limited to NEF 105, DCSF 401, etc.

[0164] At 614, HSS 403 or UDM 106 sends the IMS profile (received at 608 and stored at 610) to the consumer network function, the profile including one or more parameters matching the one or more target parameters defined in the second message (received at 612). That is, HSS 403 or UDM 106 may send the IMS profile (including IMS AS identification information) to the consumer network function based on the stored IMS profile(s) of the IMS AS(s) and the second message.

[0165] In some examples, there may not be an IMS profile for an IMS AS that matches one or more target parameters registered at HSS 403 or UDM 106. For example, there may not be an IMS AS registered at HSS 403 or UDM 106 that supports a certain target IMS service or is capable of providing an IMS service to a certain user or user group. As another example, there may not be an IMS subscriber with a certain subscriber identifier registered at HSS 403 or UDM 106.

[0166] In some examples, the consumer network function may subscribe to an IMS profile that matches the one or more target parameters at HSS 403 or UDM 106. Thus, when HSS 403 or UDM 106 receives an additional IMS profile that matches the one or more target parameters, HSS 403 or UDM 106 may send the additional IMS profile to the consumer network function at step 614 based on the subscription.

[0167] After step 614, the customer network function may have received an IMS configuration file including IMS identification information of an IMS AS that meets one or more target parameters set by the customer network function.

[0168] As described above, the IMS AS identification information may include at least one of the following:

[0169] IMS AS instance identifier or IMS AS set identifier;

[0170] a Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) via which the IMS AS can be reached; or

[0171] IMS AS diameter address of the IMS AS.

[0172] In some examples, when the IMS AS identification information is a SIP URI or an IMS AS diameter address, the customer network function can connect to the IMS AS based on the SIP URI / diameter address. Figure 6 Step 620 in FIG.

[0173] In some examples, when the IMS identification information is an IMS AS instance identifier or an IMS AS set identifier, then at 616, the consumer network function may send a third message to the NRF. The third message may include an additional discovery request indicating the IMS AS instance identifier or the IMS AS set identifier. In some example embodiments, the additional discovery request may include one or more of the one or more IMS AS parameters described above in connection with step 600.

[0174] At 618, the NRF sends a response to the customer network function, the response including an IMS AS address (e.g., IP address) based on the third message. For example, the NRF can determine the IMS AS address from a stored NF configuration file of the IMS AS based on the IMS AS instance / set identifier in the request.

[0175] At 620, the customer network function connects to the IMS AS based on the IMS AS address (in the IMS AS identification information received from the HSS 403 or UDM 106 at 614 or in the response received from the NRF at 618).

[0176] Examples of enabling (or otherwise facilitating) IMS AS discovery and service exposure via an HSS or UDM have been described. In some examples, the HSS or UDM stores IMS profiles for the IMS AS and provides information to the consumer network function to enable (or otherwise facilitate) the consumer network function to discover an IMS AS with specific characteristics (e.g., an IMS AS that provides specific IMS services, an IMS AS that provides IMS services to certain users, etc.) and connect to the discovered IMS AS. This may be beneficial because user-specific information may already be available to the HSS or UDM, while user-specific information may not be available at other network functions (e.g., the NRF may store service-specific information). Therefore, user-specific IMS AS discovery can be performed via the HSS or UDM with minimal impact on existing network functions.

[0177] In some examples, a device is provided, including a component for providing a home subscriber server or a unified data management function, the component being configured to perform: receiving one or more Internet Protocol Multimedia Subsystem (IMS) profiles from one or more IMS application servers (IMS ASs), each IMS profile including IMS AS identification information and one or more parameters of a corresponding IMS AS in one or more IMS ASs; storing the received one or more IMS profiles; receiving a second message including a discovery request from a consumer network function, the discovery request indicating that: a target network function type is an IMS AS, and one or more target parameters; and sending an IMS profile to the consumer network function, the IMS profile including one or more parameters matching the one or more target parameters.

[0178] In some examples, a device is provided, comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: receive one or more Internet Protocol Multimedia Subsystem (IMS) profiles from one or more IMS application servers (IMS ASs), each IMS profile including IMS AS identification information, and one or more parameters of a corresponding IMS AS in the one or more IMS ASs; store the received one or more IMS profiles; receive a second message including a discovery request from a consumer network function, the discovery request indicating that the target network function type is an IMS AS, and one or more target parameters; and send an IMS profile to the consumer network function, the IMS profile including one or more parameters matching the one or more target parameters.

[0179] In some examples, a device is provided, including a component for providing a consumer network function, the component being configured to perform: sending a second message to a home subscriber server or a unified data management function, the second message including a discovery request, the discovery request indicating: a target network function type is an Internet Protocol Multimedia Subsystem Application Server IMS AS, and one or more filter parameters defining one or more target parameters; receiving an IMS profile from the home subscriber server or the unified data management function based on the one or more filter parameters; and connecting to the IMS AS based on the received IMS profile.

[0180] In some examples, a device is provided, comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: send a second message to a home subscriber server or a unified data management function, the second message comprising a discovery request, the discovery request indicating that: a target network function type is an Internet Protocol Multimedia Subsystem Application Server IMS AS, and one or more filter parameters defining one or more target parameters; receive an IMS profile from the home subscriber server or the unified data management function based on the one or more filter parameters; and connect to the IMS AS based on the received IMS profile.

[0181] In some examples, a device is provided, including a component for providing an Internet Protocol Multimedia Subsystem Application Server IMS AS, which is configured to perform: providing IMS services to one or more users, or one or more user groups; and sending a first message to a home subscriber server or a unified data management function, the first message including an IMS profile of the IMS AS.

[0182] In some examples, a device is provided, comprising at least one processor and at least one memory, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the device to at least: provide IMS services to one or more users, or one or more user groups; and send a first message to a home subscriber server or a unified data management function, the first message including an IMS profile of the IMS AS.

[0183] Figure 7 Schematic representations of non-volatile memory media 700a (e.g., a computer compact disk (CD) or digital versatile disk (DVD)) and 700b (e.g., a universal serial bus (USB) memory stick) storing instructions and / or parameters 702 that, when executed by a processor, allow the processor to perform one or more steps of the method of FIG. 5 are shown.

[0184] It should be understood that various network functions (e.g., AMF, SMF, TNF, etc.) are mentioned above, and the device can be configured to operate as one or more network functions. In some examples, the device can be configured to perform at least some functions associated with AMF, SMF and / or TNF. In some examples, the device can include a virtual network function instance of AMF, SMF and / or TNF.

[0185] It should be understood that these devices may include or be coupled to other units or modules for transmission and / or reception, such as radio components or radio heads. Although these devices have been described as one entity, different modules and memories may be implemented in one or more physical or logical entities.

[0186] It should be noted that although some embodiments have been described in relation to 5G networks, similar principles may be applied with respect to other networks and communication systems. Thus, although certain embodiments have been described above by way of non-limiting and illustrative examples with reference to certain example architectures for wireless networks, technologies and standards, the embodiments may be applied to any other suitable form of communication system in addition to the communication system shown and described herein.

[0187] It is also noted herein that while the above describes exemplifying embodiments, there are numerous variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0188] As used herein, “at least one of: ” and “at least one of ” and similar expressions, where a list of two or more elements is connected by “and” or “or”, mean at least any one element, or at least two or more elements, or at least all elements.

[0189] In general, various embodiments may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Certain aspects of the present disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present disclosure is not limited thereto. Although various aspects of the present disclosure may be illustrated and described in block diagrams, flow charts, or using some other graphical representations, it is fully understood that, as non-limiting and illustrative examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0190] As used herein, the term "circuitry" may refer to one, more, or all of the following:

[0191] (a) hardware circuit implementation only (such as implementation in analog and / or digital circuitry only) and

[0192] (b) a combination of hardware circuitry and software such as (where applicable):

[0193] (i) a combination of analog and / or digital hardware circuits and software / firmware and

[0194] (ii) any portion of hardware processor(s) with software (including digital signal processor(s), software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions and

[0195] (c) Hardware circuits and / or processor(s), such as microprocessor(s) or portions of microprocessor(s), that require software (e.g., firmware) to operate, but the software may not be present when the software is not required for operation.

[0196] This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term "circuitry" also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term "circuitry" also covers, for example, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or network device, if applicable to the particular claim element.

[0197] The embodiments of the present disclosure may be implemented by computer software executable by a data processor of a mobile device (such as a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products) include software routines, applets and / or macros, which can be stored in a data storage medium readable by any device, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components, which are configured to perform an embodiment when the program is run. One or more computer executable components may be at least one software code or a portion thereof.

[0198] In this regard, it should also be noted that any blocks of the logic flow shown in the Figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on physical media such as memory chips or memory blocks implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as, for example, DVDs and their data variants CDs. Physical media are non-transitory media.

[0199] The term "non-transitory" as used herein refers to a limitation of the medium itself (ie, tangible, not a signal), not a limitation of data storage persistence (eg, RAM vs. ROM).

[0200] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0201] Various example embodiments of the present disclosure can be practiced in various components, such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available to convert a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0202] The scope of protection sought for various example embodiments of the present disclosure is set forth by the independent claims. Example embodiments described in the present disclosure and their features (if any) that do not fall within the scope of the independent claims should be interpreted as examples that help understand the various example embodiments of the present disclosure.

[0203] The foregoing description has provided a complete and informative description of various example embodiments of the present disclosure by way of non-limiting and illustrative examples. However, various modifications and adaptations may become apparent to those skilled in the relevant art in view of the above description when read in conjunction with the accompanying drawings and claims. However, all such and similar modifications of the teachings will still fall within the scope of the various example embodiments of the present disclosure described in the claims. As non-limiting and illustrative examples, there are additional example embodiments, including combinations of one or more example embodiments with any other example embodiments previously discussed.

Claims

1. A method performed by a Home Subscriber Server or a Unified Data Management Function, the method comprising: Receiving one or more Internet Protocol Multimedia Subsystem (IMS) configuration files from one or more IMS application servers (IMS ASs), each IMS configuration file comprising: IMS AS identification information, and one or more parameters of corresponding IMS ASs in the one or more IMS ASs; storing the received one or more IMS configuration files; receiving, from the consumer network function, a second message including a discovery request indicating: a target network function type of IMS AS, and one or more target parameters; and An IMS configuration file is sent to the consumer network function, the IMS configuration file comprising: one or more parameters matching the one or more target parameters.

2. The method according to claim 1, wherein the one or more parameters include at least one of the following: information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or Information indicating services that can be opened by the IMS AS and one or more events.

3. The method according to claim 1, wherein the IMS AS identification information includes at least one of the following: An IMS AS instance identifier or an IMS AS set identifier; a Session Initiation Protocol Uniform Resource Identifier via which the IMS AS can be reached; or The IMS AS diameter address of the IMS AS.

4. The method of claim 1, wherein the one or more IMS profiles are stored at the Home Subscriber Server, or Unified Data Management Function, and are associated with one or more user identifiers.

5. The method according to any preceding claim, wherein the one or more target parameters include at least one of the following: Information indicating one or more target IMS services provided by the IMS AS; information indicating one or more target users for which the IMS AS supports IMS services; Information indicating one or more target user groups for which the IMS AS supports IMS services; or Information indicating the services opened by the IMS AS and one or more target events.

6. A method performed by an Internet Protocol Multimedia Subsystem Application Server (IMS AS), the method comprising: Providing IMS services to one or more users, or one or more user groups; as well as A first message is sent to a home subscriber server or a unified data management function, wherein the first message includes an IMS profile of the IMS A server.

7. The method of claim 6, wherein the first message comprises one of: a diameter protocol message, or a service-based interface message.

8. The method according to claim 7, wherein the diameter protocol message comprises: Configuration file update request, or server assignment request.

9. The method according to any one of claims 6 to 8, wherein the IMS configuration file comprises at least one of the following: IMS AS identification information; information indicating one or more IMS services provided by the IMS AS; information indicating one or more users for which the IMS AS supports IMS services; information indicating one or more user groups for which the IMS AS supports IMS services; information indicating one or more user categories for which the IMS AS supports IMS services; or Information indicating services exposed by the IMS AS and one or more events.

10. An apparatus for communication, comprising at least one processor and at least one memory, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the apparatus to at least perform the method according to any one of claims 1 to 9.

Images