IMS DC service enhancements

Abstract

There are provided measures for enabling / implementing service enhancements for an IP Multimedia Subsystem (IMS) Data Channel (DC) architecture, for example, in an IMS DC. Such measures may exemplarily comprise: an information storage entity receiving and storing user-specific information of a first party and / or user-specific information of a second party of an IMS session involving an IMS DC, and the service providing entity receiving, from the information storage entity, user-specific information of the first party and / or user-specific information of the second party of the IMS session involving the IMS data channel, and providing the customized service via the IMS DC based on the user-specific information of the first party and / or the user-specific information of the second party.

Description

Technical Field

[0001] Various example embodiments generally relate to service enhancements for an IP Multimedia Subsystem (IMS) Data Channel (DC). More specifically, measurements / mechanisms (including, for example, methods, apparatuses, and computer program products) for enabling / implementing service enhancements for IMS DC in, for example, an IMS Data Channel (DC) architecture are described. Background Art

[0002] Various example embodiments relate to considerations in (e.g., mobile / wireless) communication systems or networks such as 5G / NR systems and next-generation systems beyond 5G. For example, various example embodiments are applicable to 3GPP standardized mobile / wireless communication systems or networks after Release 18.

[0003] Such considerations may relate to, for example, service provisioning for IMS DC in an IP Multimedia Subsystem (IMS) Data Channel (DC) architecture. List of Acronyms and Abbreviations 3GPP Third Generation Partnership Project 4G Fourth Generation 5G Fifth Generation AGW Access Gateway App Application AR Augmented Reality AS Application Server BGW Border Gateway CSP Communication Service Provider DC Data Channel DCAR Data Channel Application Repository DCMF Data Channel Media Function DCSF Data Channel Signaling Function HSS Home Subscriber Server I-CSCF Interrogating - Call Session Control Function ID Identity / Identifier IMS IP Multimedia Subsystem IP Internet Protocol MMS Multimedia Messaging Service MMTEL Multimedia Telephony MRF Media Resource Function MSISDN Mobile Subscriber Integrated Services Digital Network Number NEF Network Exposure Function NFV Network Function Virtualization NFVI Network Function Virtualization Infrastructure NR New Radio NTN Non-Terrestrial Network OTT Over-the-Top P-CSCF Proxy-Call Session Control Function PSAP Public Safety Answering Point QoS Quality of Service RCS Rich Communication Services RTP Real-Time Transport Protocol S-CSCF Serving-Call Session Control Function SDN Software Defined Network SDP Session Description Protocol SIP Session Initiation Protocol SMS Short Message Service UE User Equipment URL Uniform Resource Locator VoIP Voice over IP WebRTC Web Real-Time Communication Summary of the Invention

[0004] Various example embodiments solve at least a portion of the problems, difficulties, and / or disadvantages described herein or recognized by those of ordinary skill in the art.

[0005] The various example embodiments are set forth in the claims.

[0006] According to an example aspect, there is provided a method including: receiving, by a first IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party of an IMS session involving an IMS DC; storing, by the first IMS DC entity, the user-specific information of the first party; receiving, by the first IMS DC entity, user-specific information of a second party of the IMS session; and storing, by the first IMS DC entity, the user-specific information of the second party.

[0007] According to an example aspect, there is provided an apparatus including: means for receiving, by a first IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party of an IMS session involving an IMS DC; means for storing, by the first IMS DC entity, the user-specific information of the first party; means for receiving, by the first IMS DC entity, user-specific information of a second party of the IMS session; and means for storing, by the first IMS DC entity, the user-specific information of the second party.

[0008] According to an example aspect, there is provided an apparatus including: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive user-specific information of a first party of an IMS session involving an IMS DC from a first IP Multimedia Subsystem (IMS) Data Channel (DC) entity, store the user-specific information of the first party by the first IMS DC entity, receive user-specific information of a second party of the IMS session by the first IMS DC entity, and store the user-specific information of the second party by the first IMS DC entity.

[0009] According to an example aspect, there is provided an apparatus including: circuitry configured to receive user-specific information of a first party of an IMS session involving an IMS DC from a first IP Multimedia Subsystem (IMS) Data Channel (DC) entity, circuitry configured to store the user-specific information of the first party by the first IMS DC entity, circuitry configured to receive user-specific information of a second party of the IMS session by the first IMS DC entity, and circuitry configured to store the user-specific information of the second party by the first IMS DC entity.

[0010] According to various developments / modifications, any one of the above method-related example aspects and / or apparatus-related example aspects may include one or more of the following features: The method, function, operation or configuration includes or supports: receiving, by the first IMS DC entity, a request for user-specific information of the first party and / or user-specific information of the second party from a second IMS DC entity, and sending, to the second IMS DC entity, a message including the user-specific information of the first party and / or the user-specific information of the second party, Receiving, by the first IMS DC entity, user-specific information of the first party and user-specific information of the second party includes: receiving, by the first IMS DC entity, an IMS DC request, In response to a request for user-specific information from a third IMS DC entity, the user-specific information of the first party and / or the user-specific information of the second party is received by the first IMS DC entity, The user-specific information indicates at least one of the following: subscriber information associated with a service subscription, user-specific information of a network hosting or supporting the IMS DC architecture, user information, user equipment information, network information, a telephone number, a Mobile Subscriber Integrated Services Digital Network Number (MSISDN), a user identifier, user equipment capability information, a location, an access network, an access type, the first IMS DC entity is, implements, includes or consists of the following: a Data Channel Application Repository (DCAR) or an entity having a corresponding function. Specific user information of the first party and / or specific user information of the second party is received by the first IMS DC entity from an information providing entity, which is, implements, includes, or consists of the following: a data channel signaling function (DCSF) or an entity having a corresponding function, Specific user information of the first party and / or specific user information of the second party is received by the first IMS DC entity from an information providing entity, which is, implements, includes, or consists of the following: an IMS application server (IMS AS) or an entity having a corresponding function, The first IMS DC entity is, implements, includes, or consists of the following: a data channel signaling function (DCSF) or an entity having a corresponding function, Specific user information of the first party and / or specific user information of the second party is received by the first IMS DC entity from an information providing entity, which is, implements, includes, or consists of the following: an IMS application server (IMS AS) or an entity having a corresponding function, The first IMS DC entity is, implements, includes, or consists of the following: a data channel media function (DCMF) or an entity having a corresponding function, or the first IMS DC entity is, implements, includes, or consists of the following: an enhanced media resource function (MRF) or any entity having a corresponding function, Specific user information of the first party and / or specific user information of the second party is received by the first IMS DC entity from an information providing entity, which is, implements, includes, or consists of the following: an IMS application server (IMS AS) or an entity having a corresponding function, Specific user information of the first party and / or specific user information of the second party is received locally by the first IMS DC entity, where the first IMS DC entity is, implements, includes, or consists of the following: an IMS application server (IMSAS) or an entity having a corresponding function, The IMS DC application is or corresponds to at least one of the following: an over-the-top (OTT) application, an over-the-top (OTT) application related to a communication service, a rich communication service (RCS) application, a public safety application, an emergency service application, a public safety answering point (PSAP) application, an enhanced caller ID application, an enterprise application, or a communication service provider (CSP) application, The communication is based on a data channel media type and / or a WebRTC data channel protocol, The IMS session includes at least an IP voice (VoIP) call established or initiated between a first party and a second party, Either the first party or the second party relates to a user of the IMS DC and / or a subscriber of a network that hosts or supports the IMS DC architecture. The IMS DC architecture is based on a 3GPP network as a communication service provider network.

[0011] According to an example aspect, a method is provided that includes: receiving, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party and / or user-specific information of a second party of an IMS session involving the IMS DC from an information storage entity, and providing, by the IMS DC entity, a customized service via the IMS DC based on the user-specific information of the first party and / or the user-specific information of the second party.

[0012] According to an example aspect, a device is provided that includes: means for receiving, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party and / or user-specific information of a second party of an IMS session involving the IMS DC from an information storage entity, and means for providing, by the IMS DC entity, a customized service via the IMS DC based on the user-specific information of the first party and / or the user-specific information of the second party.

[0013] According to an example aspect, a device is provided that includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: receive, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party and / or user-specific information of a second party of an IMS session involving the IMS DC from an information storage entity, and provide, by the IMS DC entity, a customized service via the IMS DC based on the user-specific information of the first party and / or the user-specific information of the second party.

[0014] According to an example aspect, a device is provided that includes: circuitry configured to receive, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party and / or user-specific information of a second party of an IMS session involving the IMS DC from an information storage entity, and circuitry configured to provide, by the IMS DC entity, a customized service via the IMS DC based on the user-specific information of the first party and / or the user-specific information of the second party.

[0015] According to various developments / modifications, any one of the above method-related example aspects and / or device-related example aspects may include one or more of the following features: The method, function, operation or configuration includes or supports, or receives including: an IMS DC entity sending a request for user-specific information to an information storage entity, and the IMS DC entity receiving a response from the information storage entity, the response including user-specific information of a first party and / or user-specific information of a second party. The method, function, operation or configuration includes or supports, or provides a customized service including: an IMS DC entity obtaining service-related user information based on user-specific information of a first party and / or user-specific information of a second party, and the IMS DC entity customizing a service based on the service-related user information. User-specific information indicates at least one of the following: subscriber information associated with a service subscription, information specific to a service of an IMS DC application and / or an IMS DC application, user-specific information of a network hosting or supporting an IMS DC architecture, user information, user equipment information, network information, a telephone number, a mobile subscriber integrated services digital network number (MSISDN), a user identifier, user equipment capability information, a location, an access network, an access type. The IMS DC entity is, implements, includes the following or consists of the following: an IMS DC application server or an entity with corresponding functions, and / or the method is invoked or executed by an IMS DC application on the IMS DC application server or an entity with corresponding functions. The IMS DC entity is, implements, includes the following or consists of the following: a user equipment of a first party or a user equipment of a second party or an entity with corresponding functions, and / or the method is invoked or executed by an IMS DC application on the user equipment of a first party or a user equipment of a second party or an entity with corresponding functions. The information storage entity is, implements, includes the following or consists of the following: a data channel application repository (DCAR) or an entity with corresponding functions. The information storage entity is, implements, includes the following or consists of the following: a data channel signaling function (DCSF) or an entity with corresponding functions. The information storage entity is, implements, includes the following or consists of the following: a data channel media function (DCMF) or an entity with corresponding functions, or the information storage entity is, implements, includes the following or consists of the following: an enhanced media resource function (MRF) or an entity with corresponding functions. The information storage entity is, implements, includes the following or consists of the following: an IMS application server (IMS AS) or an entity with corresponding functions. The IMS DC application is or corresponds to at least one of the following: an Over-the-Top (OTT) communication application, an Over-the-Top (OTT) application involving communication services, a Rich Communication Services (RCS) application, a public safety application, an emergency services application, a Public Safety Answering Point (PSAP) application, an enhanced caller ID application, an enterprise application, or a Communication Service Provider (CSP) application. The communication is based on a data channel media type and / or the WebRTC data channel protocol. The IMS session includes an IP voice (VoIP) call that is established or initiated at least between a first party and a second party. Either the first party or the second party involves a user of the IMS DC and / or a subscriber to the network that hosts or supports the IMS DC architecture. The IMS DC architecture is based on a 3GPP network as a communication service provider network.

[0016] According to an example aspect, a method is provided that includes: providing, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party of an IMS session involving the IMS DC, and providing, by the IMS DC entity, user-specific information of a second party of the IMS session.

[0017] According to an example aspect, a device is provided that includes: means for providing, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party of an IMS session involving the IMS DC, and means for providing, by the IMS DC entity, user-specific information of a second party of the IMS session.

[0018] According to an example aspect, a device is provided that includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: provide, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party of an IMS session involving the IMS DC, and provide, by the IMS DC entity, user-specific information of a second party of the IMS session.

[0019] According to an example aspect, a device is provided that includes: circuitry configured to provide, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party of an IMS session involving the IMS DC, and circuitry configured to provide, by the IMS DC entity, user-specific information of a second party of the IMS session.

[0020] According to various developments / modifications, any one of the above method-related example aspects and / or device-related example aspects may include one or more of the following features: User-specific information indicates at least one of the following: subscriber information associated with a service subscription, user-specific information of a network hosting or supporting an IMS DC architecture, user information, user equipment information, network information, a telephone number, a mobile subscriber integrated services digital network number (MSISDN), a user identifier, user equipment capability information, a location, an access network, an access type. The IMS DC entity is, implements, includes, or consists of: a data channel signaling function (DCSF) or an entity having a corresponding function, or the IMS DC entity is, implements, includes, or consists of: an IMS application server (IMS AS) or an entity having a corresponding function, User-specific information of a first party and / or user-specific information of a second party are provided by the IMS DC entity to an information storage entity that is, implements, includes, or consists of: a data channel application repository (DCAR) or an entity having a corresponding function, The IMS DC entity is, implements, includes, or consists of: an IMS application server (IMS AS) or an entity having a corresponding function, User-specific information of a first party and / or user-specific information of a second party are provided by the IMS DC entity to an information storage entity that is, implements, includes, or consists of: a data channel signaling function (DCSF) or an entity having a corresponding function, The IMS DC entity is, implements, includes, or consists of: an IMS application server (IMS AS) or an entity having a corresponding function, User-specific information of a first party and / or user-specific information of a second party are provided by the IMS DC entity to an information storage entity that is, implements, includes, or consists of: a data channel media function (DCMF) or an entity having a corresponding function, or the information storage entity is, implements, includes, or consists of: an enhanced media resource function (MRF) or an entity having a corresponding function, The IMS DC entity is, implements, includes, or consists of: an IMS application server (IMS AS) or an entity having a corresponding function, User-specific information of a first party and / or user-specific information of a second party are provided by the IMS DC entity to an IMS application server (IMS AS) or an entity having a corresponding function, The IMS DC application is or corresponds to at least one of the following: over-the-top (OTT) communication applications, over-the-top (OTT) applications related to communication services, rich communication services (RCS) applications, public safety applications, emergency services applications, public safety answering point (PSAP) applications, enhanced caller ID applications, enterprise applications, or communication service provider (CSP) applications. The communication is based on a data channel media type and / or the WebRTC data channel protocol. The IMS session includes at least an IP voice (VoIP) call established or initiated between a first party and a second party. Either the first party or the second party involves a user of the IMS DC and / or a subscriber to the network hosting or supporting the IMS DC architecture. The IMS DC architecture is based on a 3GPP network as the communication service provider network.

[0021] According to an example aspect, a system is provided that includes at least two of the devices according to any one of the foregoing device-related aspects (and / or any of its developments / modifications).

[0022] According to an example aspect, a computer-readable medium including program instructions is provided, and the program instructions are used to cause a device (e.g., a device according to any one of the foregoing device-related example aspects (and / or any of its developments / modifications)) to at least execute a method according to any one of the foregoing method-related example aspects (and / or any of its developments / modifications).

[0023] According to an example aspect, a computer program product is provided that includes (computer-executable) computer program code, and when the program code is executed (or run) on a computer or the program runs on a computer (e.g., a computer of a device according to any one of the foregoing device-related example aspects (and / or any of its developments / modifications)), the computer program code is configured to cause the computer to at least execute a method according to the foregoing method-related example aspects (and / or any of its developments / modifications).

[0024] The computer program product may include or may be embodied as a (tangible / non-transitory) computer-readable (storage) medium, etc., on which computer-executable computer program code is stored, and / or the program may be directly loaded into the internal memory of the computer or its processor.

[0025] As used herein, the term "non-transitory" is a limitation of the medium itself (referring to, for example, a tangible medium rather than a signal), rather than a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0026] Further developments and / or modifications of the foregoing example aspects are set forth below.

[0027] Through example embodiments, techniques for (e.g., enabling / implementing) service enhancements for an IP Multimedia Subsystem (IMS) Data Channel (DC) can be provided, for example, in an IMS DC architecture.

[0028] This Summary is intended to provide a brief overview of some aspects and features in accordance with the present disclosure. Accordingly, it should be understood that the above aspects and features are merely examples and should not be construed as narrowing the scope of the present disclosure in any way. Other features, aspects, and advantages of the present disclosure will become apparent from the following detailed description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In the following, various example embodiments will be described with reference to the drawings, where

[0030] Figure 1 a schematic diagram of an example (mobile / wireless) communication system or network is shown;

[0031] Figure 2 a schematic diagram of an example wireless device or entity is shown;

[0032] Figure 3 a schematic diagram of an example network node or entity is shown;

[0033] Figure 4 a schematic diagram of an example configuration used by an application on an applicable IMS DC according to at least one example embodiment is shown;

[0034] Figure 5 a schematic diagram of an example configuration used by an application on an applicable IMS DC according to at least one example embodiment is shown;

[0035] Figure 6 a schematic diagram of an example IMS DC architecture applicable according to at least one example embodiment is shown;

[0036] Figure 7 a schematic diagram of an example IMDC architecture applicable according to at least one example embodiment is shown;

[0037] Figure 8 a flowchart of a method or process at / by a device according to at least one example embodiment is shown;

[0038] Figure 9 a flowchart of a method or process at / by a device according to at least one example embodiment is shown;

[0039] Figure 10 a flowchart of a method or process at / by a device according to at least one example embodiment is shown;

[0040] FIG. 11 (byFigure 11A and 11B constitute) shows a sequence diagram illustrating a process according to at least one example embodiment;

[0041] FIG. 12 (composed of Figure 12A and 12B constitute) shows a sequence diagram illustrating a process according to at least one example embodiment;

[0042] FIG. 13 (composed of Figure 13A and Figure 13B constitute) shows a sequence diagram illustrating a process according to at least one example embodiment;

[0043] FIG. 14 (composed of Figure 14A and Figure 14B constitute) shows a sequence diagram illustrating a process according to at least one example embodiment; and

[0044] Figure 15 shows a schematic block diagram of the structure of a device illustrated according to at least one example embodiment. DETAILED DESCRIPTION

[0045] Various example embodiments are described herein with reference to specific non - limiting and illustrative examples. Those skilled in the art will understand that these various example embodiments are not limited in any way by these non - limiting and illustrative examples, but can be applied more broadly.

[0046] References in the specification to "an embodiment", "embodiment", "example embodiment", etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but each embodiment does not necessarily include that particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, implementing such a feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described, is within the knowledge of those skilled in the art.

[0047] It should be noted that the detailed description sometimes refers to one or more specifications that serve as non - limiting and illustrative examples of certain architectures, network configurations, and system deployments. More specifically, the detailed description refers to 3GPP standards as non - limiting and illustrative examples. Thus, the example embodiments provided herein may specifically employ terms directly related thereto. Such terms are used only in the context of non - limiting and illustrative examples and are not intended to limit the example embodiments in any way. Instead, any other system configuration or deployment can be utilized while complying with what is described herein and / or the example embodiments applicable thereto.

[0048] For example, various example embodiments are applicable to any (e.g., mobile / wireless) communication system, such as 5G / NR systems and next-generation systems beyond 5G. For example, various example embodiments are applicable to 3GPP standardized mobile / wireless communication systems after Release 18.

[0049] In the following, several variations and / or alternatives are used to describe various example embodiments. Generally, it should be noted that, according to certain implementations or constraints, all the described variations and / or alternatives can be provided individually or in any conceivable combination (e.g., also including combinations of the respective features of these various variations and / or alternatives).

[0050] As used herein, the words "comprising" and "including" should be understood not to limit the example embodiments to only the features already mentioned, and the example embodiments can also include features, structures, units, modules, etc. that are not specifically mentioned, for example.

[0051] As used herein, "at least one of the following: <list of two or more elements>" and "at least one of <list of two or more elements>" and similar phrasings, where the list of two or more elements is joined by "and" or "or", means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0052] As used herein, according to various example embodiments, any operation of transmitting or receiving can include an actual transmission or communication operation, i.e., transmitting or communicating an associated message or signal, but additionally or alternatively can include associated processing operations, i.e., preparing / generating / issuing the associated message or signal before transmission and / or obtaining / coping with / processing the associated message or signal after reception. For example, transmitting a message at / by an entity can include generating / issuing and / or transmitting / communicating the message or corresponding signal in / at / by the entity, and receiving a message at / by an entity can include obtaining / coping with and / or processing the message or corresponding signal in / at / by the entity. As used herein, a message can refer to and / or cover any kind of corresponding information, signal, etc.

[0053] In the drawings, it should be noted that the lines / arrows interconnecting the various blocks or entities generally aim to show the operational coupling therebetween, which can be a physical and / or logical coupling, which is on the one hand independent of the implementation (e.g., wired or wireless), and on the other hand can also include any number of intermediate functional blocks or entities not shown. In a flowchart or sequence diagram, the order of the shown operations or actions is generally non-restrictive and illustrative, and any other order of the corresponding operations or actions can be conceived if feasible.

[0054] Before explaining the example embodiments in detail, refer to Figures 1 to 3 briefly explain the specific general principles of a (mobile / wireless) communication system or network to assist in understanding the underlying technology of the described example embodiments.

[0055] Figure 1 An example of a (mobile / wireless) communication system or network 100 that can be used for wireless communication is shown. The communication system or network 100 includes wireless device entities, such as UEs 110 (e.g., 110A - 110C), connected to one or more network nodes or entities 130 via an interconnect network 125, and network nodes or entities, such as radio access nodes 120 (e.g., 120A - 120B) (e.g., eNB, gNB, etc.). The communication system or network 100 can use any suitable deployment scenario. Each UE 110 within the coverage area 115 is capable of directly communicating with the radio access node 120 via a wireless interface. In some embodiments, the UEs 110 are also capable of communicating with each other via D2D communication.

[0056] As an example, UE 110A can communicate with radio access node 120A via a wireless interface. That is, UE 110A can send wireless signals to and / or receive wireless signals from radio access node 120A. The wireless signals can include voice services, data services, control signals, and / or any other suitable information.

[0057] As used herein, the term "user equipment" (UE) has the full breadth of its ordinary meaning and can refer to any type of wireless device or entity that can communicate with a network node or entity and / or with another UE in a cellular or mobile or wireless / mobile communication system. Examples of UEs are target devices, D2D UEs, machine type UEs or UEs capable of machine-to-machine (M2M) communication, personal digital assistants, tablet computers, mobile terminals, smart phones, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles, ProSe UEs, vehicle-to-vehicle (V2V) UEs, V2X UEs, MTC UEs, eMTC UEs, FeMTC UEs, UE Cat0, UE Cat M1, narrowband IoT (NB-IoT) UEs, UE Cat NB1, etc. The example embodiments of the UE are described in more detail below with reference to Figure 2 more detail.

[0058] In some embodiments, the wireless signal coverage area 115 associated with the radio access node 120 can be referred to as a cell. However, particularly with respect to the fifth generation (5G) / New Radio (NR) mobile communication concept, beams can be used instead of cells, so it is important to note that the concepts described herein apply equally to both cells and beams.

[0059] Regarding beam-based mobile communication systems, the radio access node 120 (base station) may transmit beamformed signals to the UE 110 in one or more transmission directions (transmission beams, Tx beams). The UE 110 may receive beamformed signals from the base station 120 in one or more reception directions (reception beams, Rx beams). The UE 110 may also transmit beamformed signals to the base station 120 in one or more directions, and the base station 120 may receive beamformed signals from the UE 110 in one or more directions. The base station 120 and the UE 110 may determine the optimal reception and transmission directions for each of the base station / UE pairs, e.g., optimal in the sense of these directions resulting in the highest link quality, or satisfying other quality conditions in the most appropriate manner.

[0060] The interconnected network 125 may refer to any interconnected system capable of transmitting audio, video, signals, data, messages, etc., or any combination of the foregoing. The interconnected network 125 may include all or part of the public switched telephone network (PSTN), public or private data networks, local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), local, regional, or global communication or computer networks (such as the Internet), wired or wireless networks, enterprise intranets, or any other suitable communication links (including combinations thereof).

[0061] In some embodiments, the network node 130 may be a core network node that manages the establishment of communication sessions and various other functions for the UE 110. Examples of the network node 130 may include a mobile switching center (MSC), MME, serving gateway (SGW), packet data network gateway (PGW), operations and maintenance (O&M), operations support system (OSS), SON, positioning node (e.g., enhanced serving mobile location center E-SMLC), location server node, MDT node, etc. The UE 110 may use the non-access stratum (NAS) layer to exchange certain signals with the network node 130. In non-access stratum signaling, the signals between the UE 110 and the network node 130 may transparently pass through the radio access network. In some embodiments, the radio access node 120 may interface with one or more network nodes 130 through an inter-node interface.

[0062] As used herein, the term "network node or entity" has the full breadth of its ordinary meaning and can correspond to any type of radio access node (or radio network node) or any network node that can communicate with a UE and / or with another network node in a cellular or mobile or wireless communication system. Examples of network nodes are NodeB, MeNB, SeNB, a network node can belong to an MCG or SCG, a base station (BS), a multi-standard radio (MSR) radio access node such as an MSR BS, an eNodeB, a network controller, a radio network controller (RNC), a base station controller (BSC), a repeater, a donor node controlled repeater, a transceiver base station (BTS), an access point (AP), a transmission point, a transmission node, an RRU, an RRH, a node in a distributed antenna system (DAS), a core network node (e.g., an MSC, an MME, etc.), an O&M, an OSS, a self-organizing network (SON), a positioning node (e.g., an E-SMLC), an MDT, a test device, etc. Example embodiments of network nodes are described in more detail below with reference to Figure 3 Example embodiments of network nodes are described in more detail.

[0063] In some embodiments, the radio access node 120 can be a distributed radio access node. The components of the radio access node 120 and their associated functions can be divided into two main units (or sub-radio network nodes), which can be referred to as a central unit (CU) and a distributed unit (DU). Different distributed radio network node architectures are possible. For example, in some architectures, the DU can be connected to the CU via a dedicated wired or wireless link (e.g., an optical fiber cable), while in other architectures, the DU can be connected to the CU via a transport network. Additionally, how the various functions of the radio access node 120 are separated between the CU and the DU can vary according to the selected architecture.

[0064] An example wireless communication system is an architecture standardized by the 3rd Generation Partnership Project (3GPP). The latest 3GPP-based developments are generally referred to as Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) Radio Access Technology (RAT). The various development stages of 3GPP specifications are referred to as releases. The latest development of LTE is generally referred to as LTE-Advanced (LTE-A). LTE (LTE-A) employs a radio access architecture called the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network called the Evolved Packet Core (EPC). The base stations of such systems are called evolved or enhanced Node Bs (eNBs) and provide E-UTRAN features such as user plane packet data convergence / radio link control / media access control / physical layer protocol (PDCP / RLC / MAC / PHY) towards communication devices and control plane radio resource control (RRC) protocol termination. Other examples of RATs include those provided by base stations of systems based on technologies such as WLAN and / or Worldwide Interoperability for Microwave Access (WiMax). The base station can provide coverage for an entire cell or a similar radio service area. Core network elements include a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a Packet Gateway (P-GW).

[0065] An example of a suitable communication system is the 5G or NR concept. The network architecture in NR can be similar to that of LTE-A. The base stations of an NR system can be called Next Generation Node Bs (gNBs). The changes to the network architecture can depend on the need to support various radio technologies and finer Quality of Service (QoS) support, as well as some requirements for QoS levels to support the Quality of Experience (QoE) from the user's perspective. Network-aware services and applications, as well as service and application-aware networks, can also bring changes to the architecture. These involve Information-Centric Networking (ICN) and User-Centric Content Delivery Network (UC-CDN) approaches. NR can use Multiple-Input Multiple-Output (MIMO) antennas, many more base stations or nodes than LTE (the so-called small cell concept), including macro sites operating in cooperation with smaller stations, and may also employ various radio technologies to achieve better coverage and enhanced data rates.

[0066] Future networks can utilize Network Function Virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that are operatively connected or linked together to provide services. Virtualized Network Functions (VNFs) can include one or more virtual machines that run computer program code using standard or generic types of servers instead of custom hardware. Cloud computing or data storage can also be utilized. In radio communications, this may mean performing node operations at least partially in a server, host, or node that is operatively coupled to a remote radio head. Node operations can also be distributed among multiple servers, nodes, or hosts. It should also be understood that the labor distribution between core network operations and base station operations can be different from or even non-existent compared to that of LTE.

[0067] An example 5G Core Network (CN) includes functional entities. The CN is connected to a UE via a Radio Access Network (RAN). The role of the UPF (User Plane Function), which is referred to as the PSA (PDU Session Anchor), can be responsible for forwarding frames back and forth between the DN (Data Network) and the UE that exchanges traffic with the data network (DN) via a tunnel established through 5G. The UPF is controlled by the SMF (Session Management Function) that receives policies from the PCF (Policy Control Function). The CN can also include an AMF (Access and Mobility Function).

[0068] In general, all concepts disclosed herein can be applicable to different communication networks, including but not limited to LTE, LTE-A, 5G, 5G Advanced, 6G, and other future or already implemented networks.

[0069] Figure 2 It is a schematic diagram of an example wireless device UE 110 according to certain example embodiments. The UE 110 can include one or more of the following: at least one transceiver 210, at least one processor 220, at least one memory 230, and at least one network interface 240. In certain example embodiments, the transceiver 210 facilitates sending wireless signals to and receiving wireless signals from a radio access node 120 (e.g., via a transmitter (Tx), a receiver (Rx), and an antenna). The processor 220 executes instructions to provide some or all of the functions described herein as being provided by the wireless device / entity or UE, and the memory 230 stores the instructions executed by the processor 220. In some embodiments, the processor 220 and the memory 230 form a processing circuit.

[0070] The processor 220 may include any suitable combination of hardware for executing instructions and manipulating data to perform some or all of the described functions of a wireless device or entity, such as the functions of the UE 110 described herein. In some embodiments, the processor 220 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs), and / or other logic.

[0071] The memory 230 is generally operable to store instructions, such as computer programs, software, applications including one or more of logic, rules, algorithms, code, tables, etc., and / or other instructions executable by the processor 220. Examples of the memory 230 include computer memory (e.g., random access memory (RAM) or read only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory computer-readable and / or computer-executable memory device storing information, data, and / or instructions usable by the processor 220 of the UE 110. For example, the memory 230 includes computer program code that causes the processor 220 to perform processing according to any of the corresponding methods described herein.

[0072] The network interface 240 is communicatively coupled to the processor 220 and may refer to any suitable device operable to receive inputs for the UE 110, send outputs from the UE 110, perform suitable processing of the inputs or outputs or both, communicate with other devices, or any combination thereof. The network interface 240 may include suitable hardware (e.g., ports, modems, network interface cards, etc.) and software, including protocol conversion and data processing capabilities, to communicate over a network.

[0073] Other embodiments of the UE 110 may include additional components in addition to those shown in Figure 2 which may be responsible for providing certain aspects of the wireless device functionality, including any of the functions described herein and / or any additional functions (including any functions necessary to support the mechanisms disclosed according to the present subject matter). By way of example, the UE 110 may include input devices and circuitry, output devices, and one or more synchronization units or circuitry, which may be part of the processor 220. The input devices include mechanisms for inputting data into the UE 110. For example, the input devices may include input mechanisms such as microphones, input elements, displays, etc. The output devices may include mechanisms for outputting data in audio, video, and / or hard copy format. For example, the output devices may include speakers, displays, etc.

[0074] In some example embodiments, the wireless device UE 110 may include a series of modules configured to implement the functions of the wireless device described herein.

[0075] It should be understood that the various modules may be implemented as a combination of hardware and software, for example, Figure 2 the processor, memory, and transceiver of the UE 110 as shown. Some example embodiments may also include additional modules to support additional and / or optional functions.

[0076] Figure 3 is a schematic diagram of an example radio access node 120 or network node or entity 130 according to some example embodiments. The radio access node 120 or network node or entity 130 may include one or more of the following: at least one transceiver 310, at least one processor 320, at least one memory 330, and at least one network interface 340. In some example embodiments, the transceiver 310 facilitates sending wireless signals to and receiving wireless signals from wireless devices (such as UE 110) (e.g., via a transmitter (Tx), a receiver (Rx), and an antenna). The processor 320 executes instructions to provide some or all of the functions described herein as being provided by the radio access node 120 or network node or entity 130, and the memory 330 stores the instructions executed by the processor 320. In some embodiments, the processor 320 and the memory 330 form a processing circuit. The network interface 340 may transmit signals to backend network components such as gateways, switches, routers, the Internet, the public switched telephone network (PSTN), core network nodes, or radio network controllers, etc.

[0077] The processor 320 may include any suitable combination of hardware for executing instructions and manipulating data to perform some or all of the described functions of the radio access node 120 or network node or entity 130, such as those described herein. In some embodiments, the processor 320 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs), and / or other logic.

[0078] Memory 330 is generally operable to store instructions, such as computer programs, software, applications including one or more of logic, rules, algorithms, code, tables, etc., and / or other instructions executable by processor 320. Examples of memory 330 include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory computer-readable and / or computer-executable memory device that stores information. For example, memory 330 includes computer program code that causes processor 320 to perform processing according to any of the corresponding methods described herein.

[0079] In certain example embodiments, network interface 340 is communicatively coupled to processor 320 and may refer to any suitable device that is operable to receive inputs for radio access node 120 or network node or entity 130, send outputs from radio access node 120 or network node or entity 130, perform suitable processing of the inputs or outputs or both, communicate with other devices, or any combination of the foregoing. Network interface 340 may include suitable hardware (e.g., ports, modems, network interface cards, etc.) and software, including protocol conversion and data processing capabilities, to communicate over a network.

[0080] Other example embodiments of radio access node 120 or network node or entity 130 may include additional components in addition to those shown, which may be responsible for providing certain aspects of the node functionality, including any of the functionality described herein and / or any additional functionality (including any functionality necessary to support the solutions described herein). Various different types of radio access nodes or network nodes may include components having the same physical hardware but configured (e.g., via programming) to support different radio access technologies, or may represent partially or completely different physical components. Figure 3 Similar processors, interfaces, and memories as described with respect to those shown may be included in other nodes or entities (e.g., UE 110, radio access node 120, etc.). Other nodes or entities may optionally include or not include a wireless interface (such as the transceiver described in).

[0081] Similar to those described with respect to Figure 3 Processors, interfaces, and memories may be included in other nodes or entities (e.g., UE 110, radio access node 120, etc.). Other nodes or entities may optionally include or not include a wireless interface (such as the transceiver described in). Figure 3 as described in.

[0082] In certain example embodiments, radio access node 120 or network node or entity 130 may include a series of modules configured to implement the functionality of radio access node 120 or network node or entity 130 described herein.

[0083] It should be understood that various modules can be implemented as a combination of hardware and software, for example, Figure 3 the processor, memory, and transceiver of the radio access node 120 or the network node or entity 130 as shown in

[0084] In reference Figures 8 to 1 Before referring to and describing in detail the techniques for (e.g., enabling / implementing) service enhancements for IMS DC in an IP Multimedia Subsystem (IMS) data channel (DC) architecture, some background information and aspects related to example embodiments will be provided. It should be noted that although described in a particular manner or context, all concepts described herein can be more generally applicable, for example, in another particular manner or context, which will be apparent to those skilled in the art.

[0085] In this document, reference is made to (use of) the IP Multimedia Subsystem (IMS) data channel (DC) and the IMS DC architecture, system, or network, respectively.

[0086] IMS DC is standardized by 3GPP to enrich the end-user call experience. To this end, in addition to the IMS voice channel (with the corresponding voice channel media type) and the IMS video channel (with the corresponding video channel media type), an IMS data channel (with the corresponding data channel media type) has been introduced. Thus, IMS data, voice, and video channels can be established in parallel within the MMTEL service via the IMS of at least one CSP.

[0087] IMS DC is configured to enhance the operability of mobile devices (UEs) with browser capabilities, such as a native dialer, enabling the incorporation of web pages, JavaScript programs, etc. Thus, IMS DC allows for in-call web applications provided by network operators (CSPs) without the need to install related applications, such as OTT applications, from, for example, the Play Store or App Store. Instead, the corresponding functionality is incorporated via in-call web applications (which are at least sometimes referred to herein as IMS DC applications) that can be dynamically downloaded from an IMS DC web server, application server, etc. to the mobile device (UE), and the corresponding functionality can be run / executed at / by the mobile device (UE) via the browser capabilities provided thereby.

[0088] Here, when referring to a party (e.g., a party to an IMS session / call), this can mean or be understood to refer to the user's user equipment (which can be, for example, a mobile device, a terminal device, or any other device) or the user, as the case may be.

[0089] Figure 4 A schematic diagram showing an example configuration for use of an application on an applicable IMS DC according to at least one example embodiment.

[0090] As Figure 4 shown, Party A and Party B hosted by different network operators (CSP A and CSP B) (i.e., by different underlying (mobile / wireless) communication systems or network services) have an ongoing IMS session / call. When Party A and Party B want to establish communication through or based on an application, they can both download the corresponding IMS DC application available at an IMS DC web server, etc. in the domain of at least one of CSP A and CSP B (here, for example, in the domain of CSP A). Using such a downloaded IMS DC application, an IMS DC can be established, and Party A and Party B can perform application-related communication on the IMS DC via IMS in the domain of at least one of CSP A and CSP B (here, for example, in the domain of CSP B). That is, an IMS DC is established between Party A and Party B, and application-related communication can be realized on this IMS DC, regardless of the type, number, or role of the parties involved, and / or regardless of which party initiates the IMS DC establishment or session / call / communication.

[0091] Figure 5 A schematic diagram showing an example configuration for use of an application on an applicable IMS DC according to at least one example embodiment.

[0092] As Figure 5As shown, Party A is served in a CSP (mobile / wireless) communication system or network and is assumed to represent the origin side / party, while Party B is served in a CSP (mobile / wireless) communication system or network and is assumed to represent the termination side / party. Both parties have a SIP client for establishing an IMS session / call and an IMS DC application for establishing an IMS DC on their mobile devices (UEs). When Party A and Party B want to establish communication through or based on an application (e.g., any one of FirstNet, Teams, WhatsApp, RCS, Enterprise, or E(nhanced)Caller ID, as shown in the upper part of the figure), they can both download the corresponding IMS DC application, which is available at an IMS DC web server, etc. in the domain of at least one of CSP A and CSP B (here, for example, in the domain of Party B's CSP). Using such a downloaded IMS DC application, an IMS DC can be established (i.e., first a bootstrap data channel and then an application data channel based on this), and Party A and Party B can perform application-related communication on the IMS DC via an IMS session / call. That is, an IMS DC is established between Party A and Party B, and application-related communication can be realized on this IMS DC.

[0093] Figure 6 A schematic diagram of an applicable example IMS DC architecture according to at least one example embodiment is shown.

[0094] As Figure 6 shown, the architecture of an IMS supporting DC may include a DC Media Function (DCMF), and a DC Application Repository (DCAR) may be implemented within or in combination with a DC Signaling Function (DCSF). It should be noted that the example IMS DC architecture shown herein is network-based or built on a network, e.g., a CSP (mobile / wireless) communication system or network that supports or hosts the IMS DC architecture.

[0095] Figure 7 A schematic diagram of an applicable example IMS DC architecture according to at least one example embodiment is shown.

[0096] As Figure 7 shown, the architecture of an IMS supporting DC may include an Enhanced Media Resource Function (MRF), and a DC Application Repository (DCAR) may be implemented within or in combination with a DC Signaling Function (DCSF). It should be noted that the example IMS DC architecture shown herein is network-based or built on a network, e.g., a CSP (mobile / wireless) communication system or network that supports or hosts the IMS DC architecture.

[0097] Regarding Figure 6 andFigure 7 For further details of the functions of individual entities in the exemplary IMS DC architecture, refer to Section 6.20 of 3GPP TR 23.700 - 87 V1.2.0.

[0098] In this document, Figure 6 and Figure 7 any entity in any of the exemplary IMS DC architectures can be referred to as an IMS DC entity or an entity in the IMS DC architecture, system, or network.

[0099] The exemplary embodiments described herein are based on or built on top of an IMS data channel architecture that can be defined in 3GPP, where such an architecture can include an IP multimedia subsystem and WebRTC (where an IMS data channel (DC) can be built, established, or implemented on top of, for example, WebRTC (data channel protocol) as a framework). Here, using the IMS data channel (DC) can optionally represent or include using WebRTC (e.g., as a framework). However, as described herein, the exemplary embodiments are pan - access, i.e., can be supported on devices using any access technology (wired or wireless, any access network, etc.).

[0100] Figure 8 A flowchart of a method or process at / by a device according to at least one exemplary embodiment is shown. The device can be, or in other words the method or process can be, a method or process of an IMS DC entity (or in other words, operable or used in an IMS DC entity), particularly an IMS DC entity configured to act as, serve as, or be used as an information storage entity.

[0101] As Figure 8 shown, the method or process includes: a step / operation (S810) of receiving user - specific information of a first party of an IMS session involving IMS DC, a step / operation (S820) of storing the user - specific information of the first party, a step / operation (S830) of receiving user - specific information of a second party of the IMS session, and a step / operation (S840) of storing the user - specific information of the second party.

[0102] According to various exemplary embodiments, the user - specific information of the first party and / or the user - specific information of the second party can be received from at least one information - providing entity. The IMS DC can be configured to or be used to communicate using or based on applications such as IMS DC applications (which can run or execute on the user equipment of any one or both parties), application servers, etc.

[0103] Furthermore, even if not in Figure 8As shown, the method or process includes: the step / operation of receiving a request for user-specific information of a first party and / or user-specific information of a second party from a second IMS DC entity, and the step / operation of sending a message including the user-specific information of the first party and / or the user-specific information of the second party to the second IMS DC entity. In this regard, the second IMS DC entity can be a network (side) node or entity.

[0104] In addition, the user-specific information of the first party and / or the user-specific information of the second party can be received by / using a request (such as an IMS DC request) from a third IMS DC entity, or received in response to a request (such as an information retrieval request) from a third IMS DC entity. In this aspect, the third IMS DC entity can be a network (side) node or entity or a user (side) / user equipment (side) node or entity.

[0105] It should be noted that the steps / operations of the method or process do not necessarily have to exhibit the sequence / order as Figure 8 shown. For example, the two receiving steps / operations can come first, and then there are two storing operations. The two receiving steps / operations and / or the two storing steps / operations can at least partially overlap or even be integrated into a single step / operation, and so on.

[0106] According to an example embodiment, although not shown, the method or process can include: at least one step / operation of receiving user-specific information of at least one party (such as the first party and / or the second party) involved in an IMS session related to the IMS DC, and at least one step / operation of storing the user-specific information of at least one party (such as the first party and / or the second party) involved in the IMS session.

[0107] Figure 9 A flowchart of a method or process at / by a device according to at least one example embodiment is shown. The device can be, or in other words the method or process can be a method or process of an IMS DC entity (or in other words, operable or used in / by an IMS DC entity), particularly an IMS DC entity configured to act as, serve as, or be used as a service providing entity.

[0108] As Figure 9 shown, the method or process includes: the step / operation (S910) of receiving user-specific information of a first party and / or user-specific information of a second party involved in an IMS session related to an IMS data channel, and the step / operation (S920) of providing a customized service via the IMS DC based on the user-specific information of the first party and / or the user-specific information of the second party.

[0109] According to various example embodiments, specific user information of a first party and / or specific user information of a second party can be received from at least one information storage entity. The IMS DC can be configured or available for communicating using or based on applications such as an IMSDC application (which can run or execute on the user equipment of any one or both parties), an application server, etc.

[0110] In addition, even though Figure 9 not shown, the method or process also includes: the step / operation of sending a request for specific user information to the information storage entity, and the step / operation of receiving a response including specific user information of a first party and / or specific user information of a second party from the information storage entity. In addition, the step / operation of providing a customized service can include: the step / operation of obtaining service-related user information based on specific user information of a first party and / or specific user information of a second party, and the step / operation of customizing the service based on the service-related user information.

[0111] According to an example embodiment, although not shown, the method or process can include: at least one step / operation of receiving specific user information of at least one party (such as a first party and / or a second party) involved in an IMS session related to an IMS data channel, and at least one step / operation of providing a customized service based on the specific user information of at least one party (such as a first party and / or a second party) of the IMS session, for example via the IMS DC.

[0112] Figure 10 A flowchart of a method or process at / by a device according to at least one example embodiment is shown. The device can be, or in other words the method or process can be, a method or process of an IMS DC entity (or in other words, operable or used in / by an IMS DC entity), in particular an IMS DC entity configured to act as, serve as, or function as an information providing entity.

[0113] As Figure 10 shown, the method or process includes: the step / operation of providing specific user information of a first party of an IMS session related to the IMS DC (S1010), and the step / operation of providing specific user information of a second party of the IMS session (S1020).

[0114] According to various example embodiments, specific user information of a first party and / or specific user information of a second party can be provided to at least one service providing entity. The IMS DC can be configured or available for communicating using or based on applications such as an IMS DC application (which can run or execute on the user equipment of any one or both parties), an application server, etc.

[0115] According to an example embodiment, although not shown, a method or process may include: providing at least one step / operation of user-specific information of at least one party (e.g., a first party and / or a second party) involved in an IMS session related to an IMS DC.

[0116] Reference Figures 8 to 10 , to the first and second parties of the IMS session. Note that such reference does not mean or is construed to specify that the IMS session involves only (these) two parties. Instead, the IMS session may involve any number of parties, such as 2 parties, 3 parties, 4 parties or more parties. Thus, the cited first and second parties represent a subset / collection of the parties of the IMS session. In other words, either of the first and second parties as referred to herein may represent any party (an example) involved in the IMS session, without specifying or limiting the total number of parties involved in such an IMS session.

[0117] According to various example embodiments, a method or process may include: one or more operations of receiving and storing user-specific information of at least two parties involved in an IMS session related to an IMS DC by a first IP Multimedia Subsystem (IMS) Data Channel (DC) entity. According to various example embodiments, a method or process may include: one or more operations of receiving, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of one or more parties out of at least two parties involved in an IMS session related to an IMS DC, for example, from an information storage entity, and one or more operations of providing a customized service via the IMS DC by the IMS DC entity based on the user-specific information of one or more parties out of at least two parties. According to various example embodiments, a method or process may include: one or more operations of providing, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of one or more parties out of at least two parties involved in an IMS session related to an IMS DC.

[0118] Reference Figures 8 to 10 , the user-specific information of any party may be any information about or identifying a user associated with a party (such as a user of an IMS DC application). For example, the user-specific information of any party may be one or more of the following: subscriber information associated with a service subscription, user-specific information of a network hosting or supporting the IMS DC architecture, user information, user equipment information, network information, a telephone number, a Mobile Subscriber Integrated Services Digital Network Number (MSISDN), a user identifier, user equipment capability information, a location, an access network, an access type, etc.

[0119] As an example embodiment, for example Figures 8 to 10In the method or process, the service providing entity can obtain user-specific information, which is required / effective for providing customized services for at least one party among the parties (i.e., the users related to the parties). Therefore, even in the case where, for example, one of the users related to the parties is not a subscriber of the relevant IMS DC application, is not logged in to the relevant IMS DC application, or the service providing entity does not have the required / effective user information of such a user for some other reason, the service can be enhanced. For example, user-specific information available (or inherent) in a supporting or hosting CSP (mobile / wireless) communication system or network can be advantageously utilized.

[0120] Hereinafter, various example embodiments are described in more detail for the purpose of illustrating the concepts of the present disclosure. The details thus described are for illustrative purposes only and do not correspondingly limit the present disclosure.

[0121] FIG. 11 (composed of Figure 11A and 11B shows a sequence diagram illustrating a process according to at least one example embodiment. In the example embodiment thus shown, the DCAR is configured to act as, serve as, or be used as an information storage entity (wherein the party information of Party A and Party B is stored), and the DCSF and / or IMS AS are configured to act as, serve as, or be used as information providing entities. The DCMF / Enhanced MRF represents the DCMF in the case of the IM DC architecture of Figure 6 or represents the Enhanced MRF in the case of the IM DC architecture of Figure 7

[0122] For example, the example embodiment of FIG. 11 shows the following steps / operations. 0. An IMS session and a boot data channel have been established. The data channel application has been downloaded to Party A and Party B. 1. Party A sends a SIP re-INVITE request with updated SDP to the IMS AS via the originating network P-CSCF and S-CSCF. The updated SDP contains the established boot data channel information and the application data channel establishment requirements indicated by the stream ID (dcmap value: greater than or equal to 1000), stream label, etc. 2. The IMS AS verifies the data channel media description information and / or user subscription data to determine whether a DC call request should be triggered to the DCSF. 3. The IMS AS notifies the DCSF of the call event and the request for the data channel for user-specific information specific to Party A (hereinafter referred to as the data of Party A), such as the E.164 number, MSISDN, access type, etc. 4. After receiving a DC call request, based on relevant parameters in the DC call request and / or operator policies, the DCSF determines the policy for handling the application data channel establishment requirement. 5. The DCSF stores the data of Party A in the DCAR. 6. The DCSF invokes the IMS AS service to send a data channel control request to the IMS AS using the application data channel establishment policy. If the DCMF or enhanced MRF needs to anchor the application data channel, the policy includes the following indications: - Initiate the application data channel establishment, which targets Party B via the originating DCMF or enhanced MRF. If the application data channel is not anchored on the DCMF or enhanced MRF, steps 7 and 14 are skipped. 7. If the DCMF needs to anchor the application data channel, the IMS AS invokes the DCMF service to indicate to the DCMF about the data channel establishment and data channel media resource reservation based on the DC media information received from the DCSF. To make the IMS AS independent of the DCMF, DC2 is used to reserve the data channel media resources. If the enhanced MRF is used, the IMS AS uses the Mr’ / Cr of the enhanced MRF to reserve the data channel media resources. 8. The IMS AS notifies the DCSF of the data channel control response to inform the result of the data channel control operation. 9 - 10. The IMS AS sends a reINVITE to the originating S-CSCF, and then to the remote network side and Party B. If the DCMF or enhanced MRF needs to anchor the application data channel, the IMS AS includes an updated SDP offer adding the media information of the DCMF or enhanced MRF. 11 - 13. Party B and the terminating network return a 200OK response with an SDP answer for the application DC to the originating network. 14 - 15. If the DCMF needs to anchor the application data channel, the IMS AS invokes the DCMF service to modify the data channel media resources based on the SDP answer for the application DC. To make the IMS AS independent of the DCMF, DC2 is used to modify the data channel media resources. If the enhanced MRF is used, the IMS AS uses the Mr’ / Cr of the enhanced MRF to modify the data channel media resources. 16. The IMS AS notifies the DCSF of the data channel modification, including user-specific information of Party B (hereinafter referred to as the data of Party B), such as the E.164 number, MSISDN, access type, etc. 17 - 18. The DCSF stores the data from Party B, including in the DCAR if applicable. 19. The IMS AS modifies the SDP answer for the application data channel of Party A in the 200 OK response and sends the 200 OK response to the S-CSCF and the P-CSCF. The originating network P-CSCF performs the QoS process for the application data channel media based on the SDP answer information from the 200 OK response. The P- CSCF returns the 200 OK response to Party A. 20. Party A sends an ACK to the terminating network. 21. An application data channel is established between Party A and Party B, which may or may not be anchored on the DCMF / Enhanced MRF.

[0123] In Option 1, the IMS DC application server is configured to act as, serve as, or be used as a service providing entity. Therefore, the IMS DC application server can retrieve user-specific information of one or both parties, i.e., the data of Party A and / or the data of Party B, from the information storage entity (i.e., DCAR).

[0124] In this option, the example embodiment of FIG. 11 shows the following steps / operations. 22. The IMS DC application server requests the caller data from the DCSF. 23 - 24. The DCSF retrieves the caller data from the DCAR. 25. The DCSF returns the data to the IMS DC application server. 26. The IMS DC application can use this data to provide customized services to the user.

[0125] In Option 2, Party A and / or Party B are configured to act as, serve as, or be used as a service providing entity. Therefore, Party A and / or Party B can retrieve user-specific information of one or both parties, i.e., the data of Party A and / or the data of Party B, from the information storage entity (i.e., DCAR).

[0126] In this option, the example embodiment of FIG. 11 shows the following steps / operations. 27 - 28. The IMS DC application in the UE of Party A retrieves the caller data from the DCAR. 29. The IMS DC application in the UE of Party A is able to use this data to provide customized services to the user. 30 - 33. The IMS DC application in the UE of Party B retrieves the caller data from the DCAR. 34. The IMS DC application in the UE of Party B is able to use this data to provide customized services to the user.

[0127] In FIG. 11, an example process is shown where data of Party A and data of Party B are pre-stored (i.e., before a potential information request) at the DCAR, e.g., in / during the establishment of an application data channel. Alternatively, even if not shown, data of Party A and data of Party B can be stored at the DCAR as needed (i.e., at the time of an information request), e.g., after the establishment of an application data channel. For example, data of Party A and data of Party B can be stored at the DCAR between steps / operations 23 and 24 in the case of Option 1 or between steps / operations 27 and 28 and / or between steps / operations 31 and 32 in the case of Option 2.

[0128] In FIG. 11, an example process is shown where data of Party A retrieved by a service providing entity and data of Party B are the same as the data of Party A and data of Party B stored at the DCAR (e.g., its entire range), such as E.164 number, MSISDN, access type, etc. Alternatively, even if not shown, data of Party A retrieved by a service providing entity and data of Party B may be different from the data of Party A and data of Party B stored at the DCAR (e.g., a subset thereof), such as one of E.164 number, MSISDN, access type, etc. For example, data retrieved by a service providing entity can be application - specific and / or service - specific, i.e., thus the user - specific information retrieved can be information specific to the IMS DC application and / or the service of the IMS DC application (at the service providing entity).

[0129] FIG. 12 (composed of Figure 12A and 12B shows a sequence diagram illustrating a process according to at least one example embodiment. In the example embodiment thus shown, the DCSF is configured to act as, serve as, or function as an information storage entity (where information of Party A and Party B is stored), and the IMS AS is configured to act as, serve as, or function as an information providing entity. The DCMF / Enhanced MRF represents the DCMF in the case of the IM DC architecture of Figure 6 or represents the Enhanced MRF in the case of the IM DC architecture of Figure 7

[0130] For example, the example embodiment of FIG. 12 shows the following steps / operations. 0. An IMS session and a bootstrap data channel have been established. The data channel application has been downloaded to Party A and Party B. 1. Party A sends a SIP re - INVITE request with updated SDP to the IMS AS via the originating network P - CSCF and S - CSCF. The updated SDP contains the established bootstrap data channel information and the application data channel establishment requirements indicated by a stream ID (dcmap value: greater than or equal to 1000), stream label, etc.​ 2. The IMS AS verifies the data channel media description information and / or user subscription data to determine whether a DC call request should be sent to the DCSF to trigger a DC call request. 3. The IMS AS notifies the DCSF of the call event and the request for the data channel for user-specific information including Party A (hereinafter referred to as the data of Party A), such as the E.164 number, MSISDN, access type, etc. 4. After receiving the DC call request, based on the relevant parameters in the DC call request and / or the operator's policy, the DCSF determines the policy for handling the application data channel establishment requirements. The DCSF stores the data of Party A. 5. The DCSF invokes the IMS AS service to send a data channel control request to the IMS AS using the application data channel establishment policy. If the DCMF or enhanced MRF needs to anchor the application data channel, the policy includes the following indications: - Initiate the establishment of the application data channel, which targets Party B via the originating DCMF or enhanced MRF. If the application data channel is not anchored on the DCMF or enhanced MRF, steps 6 and 13 are skipped. 6. If the DCMF needs to anchor the application data channel, the IMS AS invokes the DCMF service to instruct the DCMF regarding data channel establishment and data channel media resource reservation based on the DC media information received from the DCSF. To make the IMS AS independent of the DCMF, DC2 is used to reserve the data channel media resources. If the enhanced MRF is used, the IMS AS uses the Mr’ / Cr of the enhanced MRF to reserve the data channel media resources. 7. The IMS AS notifies the DCSF of the data channel control response to inform the result of the data channel control operation. 8 - 9. The IMS AS sends a reINVITE to the originating S-CSCF, and then to the remote network side and Party B. If the DCMF or enhanced MRF needs to anchor the application data channel, the IMS AS includes an updated SDP offer with the media information of the DCMF or enhanced MRF added. 10 - 12. Party B and the terminating network return a 200OK response with an SDP answer for the application DC to the originating network. 13 - 14. If the DCMF needs to anchor the application data channel, the IMS AS invokes the DCMF service to modify the data channel media resources based on the SDP answer for the application DC. To make the IMS AS independent of the DCMF, DC2 is used to modify the data channel media resources. If the enhanced MRF is used, the IMS AS uses the Mr’ / Cr of the enhanced MRF to modify the data channel media resources. 15. The IMS AS notifies the DCSF of the data channel modification, including the user - specific information of Party B (hereinafter referred to as the data of Party B), such as the E.164 number, MSISDN, access type, etc. 16. The DCSF stores the data from Party B, including UE / user / network information. 17. The IMS AS modifies the SDP answer for the application data channel of Party A in the 200OK response and sends the 200OK response to the S - CSCF and P - CSCF. The originating network P - CSCF performs the QoS process for the application data channel media based on the SDP answer information from the 200OK response. The P - CSCF returns the 200OK response to Party A. 18. Party A sends an ACK to the terminating network. 19. The application data channel established between Party A and Party B can be anchored or not anchored on the DCMF / enhanced MRF.

[0131] In an option called Option 1, the IMS DC application server is configured to act as, serve as, or be used as a service - providing entity. Therefore, the IMS DC application server can retrieve the user - specific information of one or both parties, i.e., the data of Party A and / or the data of Party B, from the information storage entity (i.e., the DCSF).

[0132] In this option, the example embodiment of FIG. 12 shows the following steps / operations. 20 - 21. The IMS DC application server retrieves the calling - party data from the DCSF. 22. The IMS DC application can use this data to provide customized services to the user.

[0133] In an option called Option 2, Party A and / or Party B are configured to act as, serve as, or be used as a service - providing entity. Therefore, Party A and / or Party B can retrieve the user - specific information of one or both parties, i.e., the data of Party A and / or the data of Party B, from the information storage entity (i.e., the DCSF).

[0134] In this option, the example embodiment of FIG. 12 shows the following steps / operations. 23 - 26. The IMS DC application in the UE of Party A retrieves the caller data from the DCSF. 27. The IMS DC application in the UE of Party A can use this data to provide customized services to the user. 28 - 29. The IMS DC application in the UE of Party B retrieves the caller data from the DCSF. 30. The IMS DC application in the UE of Party B can use this data to provide customized services to the user.

[0135] In FIG. 12, an example process is shown where the data of Party A and the data of Party B are stored at the DCSF in advance (i.e., before the potential information request), e.g., during / upon establishment of the application data channel. Alternatively, even if not shown, the data of Party A and the data of Party B can be stored at the DCSF as needed (i.e., upon information request), e.g., after establishment of the application data channel. For example, the data of Party A and the data of Party B can be stored at the DCSF between steps / operations 20 and 21 in the case of Option 1 or between steps / operations 24 and 24 and / or steps / operations 28 and 29 in the case of Option 2.

[0136] In FIG. 12, an example process is shown where the data of Party A and the data of Party B retrieved by the service - providing entity are the same as (e.g., the entire range) the data of Party A and the data of Party B stored at the DCAR, such as E.164 number, MSISDN, access type, etc. Alternatively, even if not shown, the data of Party A and the data of Party B retrieved by the service - providing entity may be different from (e.g., a subset of) the data of Party A and the data of Party B stored at the DCAR, such as one of E.164 number, MSISDN, access type, etc. For example, the data retrieved by the service - providing entity can be application - specific and / or service - specific, i.e., the user - specific information retrieved is thus information specific to the IMS DC application and / or the service of the IMS DC application (at the service - providing entity).

[0137] FIG. 13 (composed of Figure 13A and Figure 13B shows a sequence diagram illustrating a process according to at least one example embodiment. In the example embodiment thus shown, the DCMF / Enhanced MRF is configured to act as, serve as, or be used as an information - storage entity (where the information of each party of Party A and Party B is stored), and the IMS AS is configured to act as, serve as, or be used as an information - providing entity. The DCMF / Enhanced MRF represents the DCMF in the case of the IM DC architecture of Figure 6 or represents the Enhanced MRF in the case of the IM DC architecture of Figure 7

[0138] ​For example, the exemplary embodiment of FIG. 13 shows the following steps / operations. 0. An IMS session and a bootstrap data channel have been established. The data channel application has been downloaded to Party A and Party B. 1. Party A sends a SIP pre-INVITE request with updated SDP to the IMS AS via the originating network P-CSCF and S-CSCF. The updated SDP contains the established bootstrap data channel information and the application data channel establishment requirements indicated by the stream ID (dcmap value: greater than or equal to 1000), stream label, etc. 2. The IMS AS verifies the data channel media description information and / or user subscription data to determine whether a DC call request should be triggered to the DCSF. 3. The IMS AS notifies the DCSF of the call event and the request for the data channel. 4. After receiving the DC call request, based on the relevant parameters in the DC call request and / or the operator policy, the DCSF determines the policy for handling the application data channel establishment requirements. 5. The DCSF invokes the IMS AS service to send a data channel control request to the IMS AS using the application data channel establishment policy. If the DCMF or enhanced MRF needs to anchor the application data channel, the policy includes the following indications: - Initiate the establishment of the application data channel, which targets Party B via the originating DCMF or enhanced MRF. If the application data channel is not anchored on the DCMF or enhanced MRF, steps 6 and 13 are skipped. 6. If the DCMF needs to anchor the application data channel, the IMS AS invokes the DCMF service to instruct the DCMF regarding data channel establishment and data channel media resource reservation based on the DC media information received from the DCSF. To make the IMS AS independent of the DCMF, DC2 is used to reserve the data channel media resources. If the enhanced MRF is used, the IMS AS uses Mr’ / Cr of the enhanced MRF to reserve the data channel media resources. The IMS AS provides / notifies the user-specific information of Party A (hereinafter referred to as the data of Party A), including UE / user / network information, such as the E.164 number, MSISDN, access type, etc. 7. The DCMF or enhanced MRF stores the data of Party A, including UE / user / network information, such as the E.164 number, MSISDN, access type, etc. 8-9. The IMS AS notifies the DCSF of the data channel control response to notify the result of the data channel control operation. ​10 - 11. The IMS AS sends a reINVITE to the originating S-CSCF, and then to the remote network side and Party B. If the DCMF or the enhanced MRF needs to anchor the application data channel, the IMS AS includes an updated SDP offer that adds the media information of the DCMF or the enhanced MRF. 12 - 13. Party B and the terminating network return a 200OK response with an SDP answer for the application DC to the originating network. 14. If the DCMF needs to anchor the application data channel, the IMS AS invokes the DCMF service to modify the data channel media resources based on the SDP answer for the application DC. To make the IMS AS independent of the DCMF, DC2 is used to modify the data channel media resources. If the enhanced MRF is used, the IMS AS uses the Mr’ / Cr of the enhanced MRF to modify the data channel media resources. 15. The IMS AS notifies the DCMF or the enhanced MRF of the data channel modification, including the user-specific information of Party B (hereinafter referred to as the data of Party B), including UE / user / network information such as the E.164 number, MSISDN, access type, etc. 16. The DCMF or the enhanced MRF stores the data of Party B, including UE / user / network information such as the E.164 number, MSISDN, access type, etc. 17 - 19. The IMS AS modifies the SDP answer for the application data channel to Party A in the 200OK response and sends the 200OK response to the S-CSCF and the P-CSCF. The originating network P-CSCF performs the QoS process for the application data channel media based on the SDP answer information from the 200OK response. The P-CSCF returns a 200OK response to Party A. 20. Party A sends an ACK to the terminating network. 21. An application data channel is established between Party A and Party B, which can be anchored or not anchored on the DCMF / enhanced MRF.

[0139] In an option called Option 1, the IMS DC application server is configured to act as, serve as, or be used as a service providing entity. Therefore, the IMS DC application server can retrieve the user-specific information of one or both parties, i.e., the data of Party A and / or the data of Party B, from the information storage entity (i.e., the DCMF / enhanced MRF).

[0140] In this option, the example embodiment of Figure 13 shows the following steps / operations. 22 - 23. The IMS DC application server retrieves the caller data from the DCMF / enhanced MRF. 24. The IMS DC application can use this data to provide customized services to users.

[0141] In the option called Option 2, Party A and / or Party B are configured to act as, serve as, or function as service providing entities. Thus, Party A and / or Party B can retrieve user-specific information of one or both parties, i.e., data of Party A and / or data of Party B, from the information storage entity (i.e., DCMF / Enhanced MRF).

[0142] In this option, the example embodiment of FIG. 13 shows the following steps / operations. 25-26. The IMS DC application in the UE of Party A retrieves the caller data from the DCMF / Enhanced MRF. 27. The IMS DC application in the UE of Party A can use this data to provide customized services to users. 28-29. The IMS DC application in the UE of Party B retrieves the caller data from the DCMF / Enhanced MRF. 30. The IMS DC application in the UE of Party B can use this data to provide customized services to users.

[0143] In FIG. 13, an example process is shown where the data of Party A and the data of Party B are stored in advance (i.e., before a potential information request) at the DCMF / Enhanced MRF, e.g., during / upon establishment of the application data channel. Alternatively, even if not shown, the data of Party A and the data of Party B can be stored at the DCMF / Enhanced MRF as needed (i.e., upon information request), e.g., after establishment of the application data channel. For example, the data of Party A and the data of Party B can be stored at the DCMF / Enhanced MRF between steps / operations 22 and 23 in the case of Option 1 or between steps / operations 25 and 26 and / or between steps / operations 28 and 29 in the case of Option 2.

[0144] In FIG. 13, an example process is shown where the data of Party A and the data of Party B retrieved by the service providing entity are the same as (e.g., the entire range of) the data of Party A and the data of Party B stored at the DCAR, such as E.164 number, MSISDN, access type, etc. Alternatively, even if not shown, the data of Party A and the data of Party B retrieved by the service providing entity may be different from (e.g., a subset of) the data of Party A and the data of Party B stored at the DCAR, such as one of E.164 number, MSISDN, access type, etc. For example, the data retrieved by the service providing entity can be application-specific and / or service-specific, i.e., thus the user-specific information retrieved can be information specific to the IMS DC application and / or the service of the IMS DC application (at the service providing entity).

[0145] Figure 14 (composed of Figure 14A and Figure 14B ) shows a sequence diagram illustrating a process according to at least one example embodiment. In the example embodiment thus shown, the IMS AS is configured to act as, serve as, or function as an information storage entity (wherein the information of each party of Party A and Party B is stored), and the IMS AS is configured to act as, serve as, or function as an (internal) information providing entity. DCMF / Enhanced MRF represents DCMF in the case of the IM DC architecture of Figure 6 , or represents an enhanced MRF in the case of the IM DC architecture of Figure 7 .

[0146] For example, the example embodiment of Figure 14 shows the following steps / operations. 0. An IMS session and a bootstrap data channel have been established. The data channel application has been downloaded to Party A and Party B. 1. Party A sends a SIP reINVITE request with updated SDP to the IMS AS via the originating network P-CSCF and S-CSCF. The updated SDP contains the established bootstrap data channel information, as well as the application data channel establishment requirements indicated by the stream ID (dcmap value: greater than or equal to 1000), stream label, etc. 2. The IMS AS verifies the data channel media description information and / or user subscription data to determine whether a DC call request should be triggered to DCSF. The IMS AS stores information including user-specific information of Party A (hereinafter referred to as the data of Party A), such as the E.164 number, MSISDN, access type, etc. 3. The IMS AS notifies DCSF of the call event and the request for the data channel. 4. After receiving the DC call request, based on the relevant parameters in the DC call request and / or the operator policy, DCSF determines the policy for how to handle the application data channel establishment requirements. 5. DCSF invokes the IMS AS service to send a data channel control request to the IMS AS with the application data channel establishment policy. If DCMF or the enhanced MRF needs to anchor the application data channel, the policy includes the following indication: - Initiate the establishment of the application data channel, which targets Party B via the originating DCMF or enhanced MRF. If the application data channel is not anchored on DCMF or the enhanced MRF, steps 6 and 13 are skipped. 6 - 7. If the DCMF needs to anchor the application data channel, the IMS AS invokes the DCMF service to indicate to the DCMF regarding data channel establishment and data channel media resource reservation based on the DC media information received from the DCSF. To make the IMS AS independent of the DCMF, DC2 is used to reserve the data channel media resources. If the enhanced MRF is used, the IMS AS uses the Mr’ / Cr of the enhanced MRF to reserve the data channel media resources. 8 - 9. The IMS AS notifies the DCSF of the data channel control response to inform the result of the data channel control operation. 10 - 11. The IMS AS sends a reINVITE to the originating S - CSCF, and then to the remote network side and Party B. If the DCMF or the enhanced MRF needs to anchor the application data channel, the IMS AS includes an updated SDP offer that adds the media information of the DCMF or the enhanced MRF. 12 - 13. Party B and the terminating network return a 200OK response with an SDP answer for the application DC to the originating network. 14. If the DCMF needs to anchor the application data channel, the IMS AS invokes the DCMF service to modify the data channel media resources based on the SDP answer for the application DC. To make the IMS AS independent of the DCMF, DC2 is used to modify the data channel media resources. If the enhanced MRF is used, the IMS AS uses the Mr’ / Cr of the enhanced MRF to modify the data channel media resources. The IMS AS stores information including user - specific information of Party B (hereinafter referred to as Party B's data), such as the E.164 number, MSISDN, access type, etc. 15. The IMS AS notifies the DCMF or the enhanced MRF of the data channel modification. 16. The DCMF or the enhanced MRF stores Party B's data. 17. The IMS AS modifies the SDP answer for the application data channel to Party A in the 200OK response and sends a 200OK response to the S - CSCF and the P - CSCF. The originating network P - CSCF performs a QoS process for the application data channel media based on the SDP answer information from the 200OK response. The P - CSCF returns a 200OK response to Party A. 18. Party A sends an ACK to the terminating network. 19. An application data channel between Party A and Party B is established, which may or may not be anchored on the DCMF / enhanced MRF.

[0147] In an option called Option 1, the IMS DC application server is configured to act as, serve as, or function as a service providing entity. Thus, the IMS DC application server can retrieve user-specific information of one or both parties, i.e., data of Party A and / or data of Party B, from an information storage entity (i.e., the IMS AS).

[0148] In this option, the example embodiment of FIG. 14 shows the following steps / operations. 20-21. The IMS DC application server retrieves the calling party data from the IMS AS. 22. The IMS DC application can use this data to provide customized services to the user.

[0149] In an option called Option 2, Party A and / or Party B are configured to act as, serve as, or function as a service providing entity. Thus, Party A and / or Party B can retrieve user-specific information of one or both parties, i.e., data of Party A and / or data of Party B, from an information storage entity (i.e., the IMS AS).

[0150] In this option, the example embodiment of FIG. 14 shows the following steps / operations. 23-26. The IMS DC application in the UE of Party A retrieves the calling party data from the IMS AS. 27. The IMS DC application in the UE of Party A can use this data to provide customized services to the user. 28-29. The IMS DC application in the UE of Party B retrieves the calling party data from the IMS AS. 30. The IMS DC application in the UE of Party B can use this data to provide customized services to the user.

[0151] In FIG. 14, an example process is shown where the data of Party A and the data of Party B are stored at the IMS AS in advance (i.e., before a potential information request), e.g., in / during the establishment of the application data channel. Alternatively, even if not shown, the data of Party A and the data of Party B can be stored at the IMS AS as needed (i.e., at the time of information request), e.g., after the establishment of the application data channel. For example, the data of Party A and the data of Party B can be stored at the IMS AS between steps / operations 20 and 21 in the case of Option 1 or between steps / operations 24 and 25 and / or between steps / operations 28 and 29 in the case of Option 2.

[0152] In FIG. 14, an example process is shown where the data of Party A and the data of Party B retrieved by the service - providing entity are the same as the data of Party A and the data of Party B stored at the DCAR (e.g., its entire range), such as E.164 numbers, MSISDNs, access types, etc. Alternatively, even if not shown, the data of Party A and the data of Party B retrieved by the service - providing entity may be different from the data of Party A and the data of Party B stored at the DCAR (e.g., a subset thereof), such as one of E.164 numbers, MSISDNs, access types, etc. For example, the data retrieved by the service - providing entity can be application - specific and / or service - specific, that is, the user - specific information thus retrieved can be information specific to the IMS DC application and / or the service of the IMS DC application (at the service - providing entity).

[0153] Referring to any one of FIGS. 11 to 14, it should be noted that different IMS DC entities can assume different roles. For example, the DCAR or DCSF or DCMF / Enhanced MRF or IMS AS can act as, serve as, or be used as an information - storage entity (from which / at which the IMS DC application on the UE device or (optionally) the IMS DC application server can access information). However, this is merely exemplary and the present disclosure is not limited thereto. That is, the roles of the information - storage entity, the service - providing entity, and / or the information - providing entity can be different, for example, depending on the IMS DC architecture, network or system, underlying or hosting network, etc.

[0154] Referring to any one of FIGS. 11 to 14, it should be noted that the entire process or a part thereof (e.g., the information retrieval of Option 1 or 2) can be invoked by the originating party / side or the terminating party / side. In addition, it should be noted that the information retrieval of Option 1 can be invoked or executed by the IMS DC application on the IMS DC application server or an entity with a corresponding function, while the information retrieval of Option 2 can be invoked or executed by the IMS DC application on an IMS DC entity (e.g., the UE of either party) or an entity with a corresponding function.

[0155] Referring to any one of FIGS. 11 to 14, it should be noted that Party A and / or Party B can be, include, implement, or represent any kind of entity that can be involved (e.g., in IMS sessions / calls and / or application - related communications). For example, either party can be a user UE or terminal, an enterprise UE or terminal, a PSAP UE or terminal, a UE or terminal of the first responder, etc.

[0156] The above-described example embodiments have been described under the assumption of two parties involved (e.g., in an IMS session / call and / or application-related communication), but the present disclosure is not limited thereto. That is, more than two parties may be involved (e.g., in an IMS session / call and / or application-related communication). Thus, referring to FIGS. 11 to 14, when Party A initiates an IMS session / call or an IMS DC or an application data channel establishment, the initiated IMS session / call or IMS DC or application data channel may be established to any party involved, such as Party B and one or more other parties (not shown). Any one of such other parties may operate or behave similarly to the operation or behavior of Party B, as shown in any of FIGS. 11 to 14, and / or similar information of such additional parties may be correspondingly (e.g., additionally or alternatively) processed or addressed.

[0157] The above-described example embodiments have been described in which Party B initiates an IMS session / call or an IMS DC or an application data channel establishment (e.g., by sending a SIP reINVITE request). However, the present disclosure is not limited thereto. That is, an IMS call / session or an IMS DC or an application data channel establishment may be initiated by Party B (e.g., by sending a SIP reINVITE request). When more than two parties are involved, an IMS session / call or an IMS DC or an application data channel establishment may be initiated by any one of the parties involved.

[0158] In the following, example embodiments are described in which user-specific information of both parties (e.g., two parties involved (i.e., Party A and Party B in FIGS. 11 to 14) of an (e.g., IMS session or application-related link / communication)) is processed / addressed, particularly received and stored at / by an information storage entity and / or provided by an information providing entity. This may be advantageous in scenarios where user-specific information is used to support / enhance communication, services, etc. between the two parties. However, the present disclosure is not limited thereto. That is, user-specific information of only one party or a subset of the parties involved (e.g., Party A or Party B in FIGS. 11 to 14) of an (e.g., IMS session or application-related link / communication) may be processed / addressed, particularly received and stored at / by an information storage entity and / or provided by an information providing entity. This may be advantageous in scenarios where user-specific information is used to support / enhance communication, services, etc. towards a single party or a subset of the parties (e.g., between a network such as a network node / entity and a single party, between a single party and another party, etc.).

[0159] Above, example embodiments have been described in the context of assuming a single application (e.g., for communication between parties), but the present disclosure is not limited thereto. That is, two or more applications (e.g., for communication between parties) may be involved, such that, for example, two or more applications (IMS DC applications) may exist and / or run / execute in parallel at the parties, and / or application-related communication based on two or more applications may be implemented in parallel.

[0160] Hereinafter, for the purpose of illustrating the concepts of the present disclosure, various use cases (of the example embodiments) are described in more detail. The details thus described are for illustrative purposes only and do not correspondingly limit the present disclosure.

[0161] According to various example embodiments, the services provided via IMS DC (i.e., in the IMS DC architecture) may have different purposes and / or involve different (types of) applications, i.e., applications running on the UEs of Party A and Party B. Such services, purposes, or applications may be any service, purpose, or application as long as it can be provided via communication between at least two parties on IMS DC, i.e., in the IMS DC architecture. Such communication may involve web pages, JavaScript programming, etc. (data transmission via / through web pages, JavaScript programming, etc.). For example, such services, purposes, or applications may refer to content sharing (e.g., screen sharing, image sharing, file transfer, chat, virtual / augmented reality, etc.), customized enterprise communication (e.g., doctor visit, plumber visit, furniture store, insurance, hotel, etc.), entertainment and / or tourism (e.g., sports events, museums, city guides, language translation, education, etc.), emergency services and public safety (e.g., content sharing in the context, location, and / or map, virtual / augmented reality assistance or aid, language translation, transcription, etc.), rich caller ID (e.g., call intent, verified caller ID, image, etc., interactive menu, call hold, etc.), and so on.

[0162] As a first illustrative but non-limiting example, the use case of an OTT communication application may be adopted.

[0163] So far, OTT communication applications (e.g., WhatsApp, Teams, Zoom, Facetime, iMessage) have significant limitations. That is, all participants in an OTT application session must be subscribers of that OTT application. Therefore, OTT communication applications are all proprietary islands that do not interoperate with each other, and all participants in an OTT communication application session must be subscribers of that OTT application.

[0164] By using the IMS Data Channel (DC) within the IMS DC architecture, a party can select an OTT communication application (e.g., WhatsApp, Teams, Zoom, Facetime, iMessage) from the IMS DC application repository to use with another party during an IMS session such as an IMS VoIP call. After selection, both parties can access the IMS DC OTT communication application from the IMS DC application server (IMS DC application repository web server). Neither party needs to install the OTT communication application on the device, but the IMS DC OTT communication application is (dynamically) downloaded to the parties (UEs).

[0165] Based on various example embodiments, the IMS DC OTT communication application (running on the UE and / or IMS DC application server) is able to obtain (relevant / required) user-specific information, i.e., subscriber information for all parties in the session (as needed), such as E.164 number, MSISDN, location, access type (e.g., WiFi, 4G, 5G, NTN), UE capabilities, and / or any future standard-defined identifiers. Then, the IMS DC OTT communication application (e.g., WhatsApp, Teams, Zoom, Facetime, iMessage) can use the subscriber information to provide existing services, such as the user's OTT friend list, or provide new and / or enhanced services.

[0166] Thus, various example embodiments allow the use of OTT communication applications without requiring that a party must be a subscriber of the application or must download (and install) the application (onto / on your UE). And if a user is already a subscriber of the application, she / he can get the full capabilities of the OTT service as well as potential enhanced services, since the IMS DC OTT communication application has the ability to obtain CSP user and / or network data about the user or subscriber (as needed).

[0167] As a second illustrative but non-limiting example, a use case of an OTT application with built-in communication services can be adopted.

[0168] To date, OTT applications with built-in communication services (e.g., plumber, hotel, doctor applications) have significant limitations. That is, while it is not necessarily required that both parties be subscribers of the application, both parties must install the application or access the application via a URL. Thus, OTT applications with built-in communication services require the user to first download the OTT application or send a link to the user to access the OTT application.

[0169] For example, by using the IMS Data Channel (DC) within the IMS DC architecture, a person at a business / enterprise can select a customized business / enterprise application with built-in communication services (e.g., plumber, hotel, doctor) from the IMS DC application repository to use with a customer in an IMS session such as an IMS VoIP call. After selection, both parties can access the IMS DC OTT business / enterprise application with built-in communication services from the IMS DC application server (IMS DC application repository web server). Neither party needs to install the OTT application on the device, but the IMS DC OTT communication application is (dynamically) downloaded to each party (UE).

[0170] Based on various example embodiments, the IMS DC OTT business / enterprise application (running on the UE and / or IMS DC application server) is able to obtain (relevant / required) user-specific information, i.e., subscriber information, such as the E.164 number, MSISDN, location, access type (e.g., WiFi, 4G, 5G, NTN), UE capabilities, and / or any identifier defined by future standards for all parties in the session (as needed). Then, the IMS DC OTT business / enterprise application with built-in communication services (e.g., plumber, hotel, doctor) can use the subscriber information to provide existing services, e.g., presenting a customer profile with preferences and previous purchases, or provide new and / or enhanced services, e.g., AR-supported directions on a map.

[0171] Thus, various example embodiments allow the use of OTT applications with built-in communication services without requiring that one must be a subscriber of the application or must download (and install) the application (to / on your UE) or use a URL to access the application. If the OTT application is for a specific business, e.g., a hotel, the hotel application can provide customized or improved customer service because the IMS DC OTT application has the ability to obtain CSP user and / or network data about the user or subscriber (as needed).

[0172] As a third illustrative but non-limiting example, a use case of an RCS application / service can be adopted.

[0173] To date, the RCS service of CSPs has the following limitations: all users must have access to the RCS application that must be built-in and / or pre-installed in the user's UE. Thus, for the RCS application / service, all parties in an RCS session have the prerequisite that RCS must be installed in the devices of all parties in the session.

[0174] By using the IMS Data Channel (DC) within the IMS DC architecture, a party can select an RCS application from the IMS DC application repository for use with another party during an IMS session such as an IMS VoIP call. After selection, both parties can access the IMS DC RCS application from the IMS DC application server (IMS DC application repository web server). Neither party needs to install the RCS application on the device, but the IMS DC RCS application is (dynamically) downloaded to each party (UE).

[0175] Based on various example embodiments, the IMS RCS application (running on the UE and / or IMS DC application server) is able to obtain (relevant / required) user-specific information, i.e., subscriber information, such as the E.164 number, MSISDN, location, access type (e.g., WiFi, 4G, 5G, NTN), UE capabilities, and / or any future standard-defined identifiers for all parties in the session (as needed). The IMS DC RCS application can then use the subscriber information (e.g., the subscriber's network user information) to provide existing services, such as the user's RCS buddy list / network address book, or to provide new and / or enhanced services.

[0176] Thus, various example embodiments allow the use of RCS applications without pre-installing the RCS application on the user UE. Instead, the IMS DC RCS application can provide services because it has the ability to obtain CSP user and / or network data (as needed) about the user or subscriber.

[0177] As a fourth illustrative but non-limiting example, a use case for a public safety application can be adopted.

[0178] So far, public safety services may not work between a first responder group (e.g., firefighters) in one area and a first responder group (e.g., firefighters) in another area, or for example, firefighters in one area and police in the same / different areas because they may use different or evolving public safety applications. Thus, public safety services / applications provide limited advanced capabilities to first responders, require the service to be installed on the user device, and do not always work between different groups of first responders.

[0179] By using the IMS Data Channel (DC) within the IMS DC architecture, first responders from a public safety group (e.g., firefighters or police in a region) can select public safety applications from the IMS DC application repository to use on an IMS session such as an IMS VoIP call with another first responder from another public safety group (e.g., firefighters or police in the same or another region). After selection, both parties can access the IMS DC public safety application from the IMS DC application server (IMSDC application repository web server). Neither party needs to install the public safety application on the device, but the IMS DC public safety application is (dynamically) downloaded to each party (UE).

[0180] Based on various example embodiments, the IMS DC public safety application (running on the UE and / or IMS DC application server) is able to obtain (relevant / required) user-specific information, i.e., subscriber information, such as the E.164 number, MSISDN, location, access type (e.g., WiFi, 4G, 5G, NTN), UE capabilities, and / or any identifier defined by future standards for all parties in the session (as needed). Then, the IMS DC public safety application can use the subscriber information (i.e., the user information of the first responder) to provide new and / or enhanced services.

[0181] Thus, various example embodiments allow the use of public safety services without requiring the first responders involved / concerned to use the same public safety application. More specifically, different groups of first responders are allowed to use advanced and / or different public safety applications without requiring the systems of the two groups to have the same available applications, because the IMS DC public safety application has the ability to obtain CSP user and / or network data about the user or subscriber (as needed). The application can be obtained from the system of only one group, and the two groups will be able to use the application together.

[0182] As a fifth illustrative but non-limiting example, a use case of an emergency service application can be adopted.

[0183] So far, the public can communicate with PSAP operators via voice / VoIP, and in some communities, SMS and / or MMS are also available as non-voice emergency services. Thus, emergency services provide limited advanced capabilities for calls between PSAP operators and the public because the parties involved must use the same emergency service application, i.e., the same emergency service application must be installed on their devices.

[0184] By using the IMS Data Channel (DC) within the IMS DC architecture, an emergency services PSAP operator can select an emergency services application from the IMS DC application repository for use with a caller from the public during an IMS session such as an IMS VoIP call. After selection, both parties can access the IMS DC emergency services application from the IMS DC application server (IMS DC application repository web server). Neither party needs to install the emergency services application on the device, but the IMS DC emergency services application is (dynamically) downloaded to both parties (UE).

[0185] Based on various example embodiments, the IMS DC emergency services application (running on the UE and / or IMS DC application server) is capable of obtaining (relevant / required) user-specific information, i.e., subscriber information, such as the E.164 number, MSISDN, location, access type (e.g., WiFi, 4G, 5G, NTN), UE capabilities, and / or any future standard-defined identifier for all parties in the session (as needed). The IMS DC emergency services application can then use the subscriber information of the caller to provide new and / or enhanced services.

[0186] Accordingly, various example embodiments allow the use of emergency services applications without the requirements and / or limitations heretofore. More specifically, PSAP operators are allowed to use advanced emergency services with the public without requiring the public user to pre-install the emergency services application in her / his device, since the IMS DC emergency services application has the ability to obtain CSP user and / or network data about the caller (as needed).

[0187] As a sixth illustrative but non-limiting example, a use case of an enhanced caller ID application can be adopted.

[0188] Heretofore, caller ID services have evolved from providing only the phone number to the name of the caller to verifying the name of the caller to include the logo of the caller—especially if commercial. Currently, the state of caller ID does not include information such as location or other user and / or network information.

[0189] By using the IMS Data Channel (DC) within the IMS DC architecture, a caller can select an enhanced caller ID from the IMS DC application repository for use with the caller during the initiation of an IMS session such as an IMS VoIP call. After selection, both parties can access the IMS DC enhanced caller ID application from the IMS DC application server (IMS DC application repository web server). Neither party needs to install the enhanced caller ID application on the device, but the IMS DC enhanced caller ID application is (dynamically) downloaded to both parties (UE).

[0190] Based on various example embodiments, an IMS DC enhanced caller ID application (running on the UE and / or the IMS DC application server) can obtain (relevant / required) user-specific information, i.e., subscriber information, such as the E.164 number, MSISDN, location, access type (e.g., WiFi, 4G, 5G, NTN), UE capabilities, and / or any future standard-defined identifiers for all parties in a session as needed. Then, the IMS DC enhanced caller ID application can use the caller's user information stored or provided by the network to provide new and / or enhanced services.

[0191] Accordingly, various example embodiments allow the use of enhanced caller ID applications without the requirements and / or limitations heretofore. More specifically, a further evolution of the caller ID service can be provided, which includes caller ID verification, logo, location, call intent, etc., since the IMS DC enhanced caller ID application has the ability to obtain CSP user and / or network data about the caller as needed.

[0192] As described above, various example embodiments provide techniques for (e.g., enabling / implementing) service enhancements for IMS DC in, for example, an IP Multimedia Subsystem (IMS) Data Channel (DC) architecture. That is, measurements / mechanisms (including methods, apparatuses (i.e., devices, entities, elements, instances, and / or functions)) for (e.g., enabling / implementing) service enhancements for IMS DC in an IP Multimedia Subsystem (IMS) Data Channel (DC) architecture are provided.

[0193] As described above, service enhancements can be achieved because the user-specific information of the first party and the user-specific information of the second party are stored at the information storage entity, where the user-specific information of the first party and / or the user-specific information of the second party can be retrieved by the service providing entity. Thereby, the service providing entity can provide / supply customized services based on the user-specific information of the first party and / or the user-specific information of the second party. That is, the service providing entity can obtain user-specific information for service customization (which is available in the underlying / hosted CSP network), even if at least one of the users is not a subscriber of the relevant application, or the user information of at least one user is unavailable to the application for some other reason.

[0194] For example, various example embodiments can effectively provide access to applications (such as OTT applications) that go beyond current limitations (such as membership islands). Doing so gives users greater flexibility who do not want to download and subscribe to every application used by every party (e.g., friends, family, enterprises) with whom they may wish to communicate. Various example embodiments enable applications to utilize UE, user, and / or network information to provide customized service provisioning to users, and / or enable application providers to utilize features or services of the underlying or hosted (e.g., 3GPP) CSP network, such as QoS, security, etc.

[0195] For example, various example embodiments can be used in an IMS data channel solution that includes multiple standardized IMS DC nodes / entities or functions.

[0196] The above functions and their related operations, processes, methods, and procedures can be implemented by corresponding functional elements, entities, modules, units, processors, etc., as described below. These functional elements, entities, modules, units, processors, etc. (i.e., the implementation means of one or more example embodiments) can be implemented in a cloud environment, via SDN, via NFV / NFVI, etc.

[0197] Although various example embodiments are described with reference to operations, processes, methods, and procedures, these example embodiments also cover the corresponding apparatuses, entities, modules, units, network nodes, and / or systems, including their software and / or hardware.

[0198] The corresponding example embodiments are described below, and for the sake of brevity, reference is made to the detailed description of the corresponding configuration / settings, solutions, processes, sequences, methods, and functions, principles, and operations according to Figures 4 to 1 4.

[0199] Figure 15 A schematic block diagram showing the structure of an apparatus according to at least one example embodiment is shown.

[0200] In Figure 15 , these blocks are basically configured to perform the corresponding methods, processes, and / or functions as described above. It should be noted that each block is intended to show the corresponding functional block that separately implements the corresponding function, process, or procedure. Such functional blocks are independent of the implementation means, i.e., they can be implemented separately by any type of hardware or software or a combination thereof.

[0201] According to at least one example embodiment, the apparatus according to at least one example embodiment can represent or implement / embodiment an information storage entity or an element, function, or entity with specific functionality or operability (e.g., a part thereof). Such an information storage entity can be an IMS DC entity, i.e., an entity / its entity in an IMS DC architecture, network, or system.

[0202] Such a device may be shown or implemented as Figure 3 shown. The device or at least one of its processors 320 (e.g., together with instructions stored in at least one of its memories 330) may be configured to receive user-specific information of a first party of an IMS session involving IMS DC, store the user-specific information of the first party, receive user-specific information of a second party of the IMS session, and store the user-specific information of the second party. In addition, the device or at least one of its processors 320 (e.g., together with instructions stored in at least one of its memories 330) may be configured to receive a request for the user-specific information of the first party and / or the user-specific information of the second party from a second IMS DC entity, and send a message to the second IMS DC entity, the message including the user-specific information of the first party and / or the user-specific information of the second party.

[0203] Such a device may be shown or implemented as Figure 15 shown as device 1510. Device 1510 may include one or more units / components / circuits represented (at least) by a receiving portion 1511, which represents any implementation for (or configured to) receive user-specific information of a first party of an IMS session involving IMS DC and / or user-specific information of a second party of the IMS session; and one or more units / components / circuits represented by a storage portion 1512, which represents any implementation for (or configured to) store the user-specific information of the first party and / or the user-specific information of the second party. As shown by the dashed line, device 1510 may include one or more units / components / circuits represented (at least) by a receiving portion 1513, which represents any implementation for (or configured to) receive a request for the user-specific information of the first party and / or the user-specific information of the second party from a second IMS DC entity; and one or more units / components / circuits represented by a sending portion 1514, which represents any implementation for (or configured to) send a message to the second IMS DC entity, the message including the user-specific information of the first party and / or the user-specific information of the second party.

[0204] According to at least one example embodiment, the device according to at least one example embodiment may represent or implement / embodiment a service providing entity or an element, function or entity of a specific function or operability (e.g., a part thereof). Such a service providing entity may be an IMS DC entity, i.e., an entity / its entity in an IMS DC architecture, network or system.

[0205] Such a device may be shown or implemented as Figure 2 or Figure 3shown or implemented. The apparatus or at least one of its processors 220 or 320 (e.g., together with instructions stored in at least one of its memories 230 or 330) may be configured to: receive user-specific information of a first party and / or user-specific information of a second party of an IMS session involving an IMS data channel from an information storage entity, and provide a customized service via the IMS DC based on the user-specific information of the first party and / or the user-specific information of the second party. In addition, the apparatus or at least one of its processors 220 or 320 (e.g., together with instructions stored in at least one of its memories 230 or 330) may be configured to: send a request for user-specific information to the information storage entity, and receive a response including the user-specific information of the first party and / or the user-specific information of the second party from the information storage entity. In addition, the apparatus or at least one of its processors 220 or 320 (e.g., together with instructions stored in at least one of its memories 230 or 330) may be configured to: obtain service-related user information based on the user-specific information of the first party and / or the user-specific information of the second party, and customize the service based on the service-related user information.

[0206] Such an apparatus may be as Figure 15is shown or implemented as device 1520. Device 1520 may include one or more units / components / circuits represented by (at least) receiving part 1521, which represents any implementation for (or configured to) receive user-specific information of a first party and / or user-specific information of a second party of an IMS session related to an IMS data channel from an information storage entity; and one or more units / components / circuits represented by providing part 1522, which represents any implementation for (or configured to) provide a customized service via the IMS DC based on the user-specific information of the first party and / or the user-specific information of the second party. As shown by the dashed line, device 1520 may include one or more units / components / circuits represented by sending part 1523, which represents any implementation for (or configured to) send a request for user-specific information to the information storage entity; and one or more units / components / circuits represented by receiving part 1524, which represents any implementation for (or configured to) receive a response including the user-specific information of the first party and / or the user-specific information of the second party from the information storage entity. As shown by the dashed line, device 1520 may include one or more units / components / circuits represented by obtaining part 1525, which represents any implementation for (or configured to) obtain service-related user information based on the user-specific information of the first party and / or the user-specific information of the second party; and one or more units / components / circuits represented by customizing part 1526, which represents any implementation for (or configured to) customize the service based on the service-related user information.

[0207] According to at least one example embodiment, the device according to at least one example embodiment may represent or implement / embodiment an information providing entity or an element, function or entity of a specific function or operability (e.g., a part thereof). Such an information providing entity may be an IMS DC entity, i.e., an entity in the IMS DC architecture, network or system / its entity.

[0208] Such a device may be as Figure 3 shown or implemented. The device or at least one of its processors 320 (e.g., together with instructions stored in at least one of its memories 330) may be configured to: provide user-specific information of a first party of an IMS session related to an IMS data channel, and provide user-specific information of a second party of the IMS session.

[0209] Such a device may be as Figure 15is shown or implemented as device 1530. Device 1530 may include (at least) one or more units / components / circuits represented by a providing portion 1531, which represents any implementation for (or configured to) provide user-specific information of a first party of an IMS session involving an IMS data channel and / or user-specific information of a second party of the IMS session. As shown by the dashed line, device 1530 may include one or more units / components / circuits represented by a holding portion 1532, which represents any implementation for (or configured to) hold user-specific information of the first party and / or user-specific information of the second party.

[0210] For further details regarding the operability / functionality of the device (or its units / components) according to an example embodiment, reference is respectively made to the descriptions in conjunction with any one of the above Figures 1 to 1 in 4.

[0211] According to an example embodiment, any one of (at least one) processor, (at least one) memory, and (at least one) interface, as well as any one of the illustrated units / components, may be implemented as separate modules, chips, chip sets, circuits, etc., or one or more of them may be respectively implemented as a common module, chip set, circuit, etc.

[0212] As used herein, the term "circuit" may refer to one or more or all of the following: (a) only a hardware circuit implementation (such as an implementation only in analog and / or digital circuits) and (b) a combination of hardware circuits and software, such as (when applicable): (i) a combination of analog and / or digital hardware circuits and software / firmware, and (ii) any part of a hardware processor with software (including a digital signal processor, software, and memory, which work together to enable a device such as a mobile phone or a server to perform various functions), and (c) a hardware circuit and / or a processor, such as a microprocessor or a part of a microprocessor, which requires software (e.g., firmware) to operate, but the software may be absent when it is not required to operate.

[0213] This definition of a circuit applies to all uses of this term included in any claims herein. As another example, as used herein, the term "circuit" also covers an implementation of only a hardware circuit or a processor (or processors) or a part of a hardware circuit or a processor and its (or their) accompanying software and / or firmware. The term "circuit" also covers, for example and if applicable to a specific claim element, a baseband integrated circuit or a processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network devices.

[0214] According to an example embodiment, the system may include any conceivable combination of any of the depicted or described devices and other network elements or functional entities, which are configured to cooperate as described above.

[0215] Generally, it should be noted that corresponding functional blocks or elements according to the various embodiments described herein may be implemented separately in hardware and / or software by any known components if only suitable for performing the described functions of the corresponding parts. The mentioned method steps may be implemented in individual functional blocks or by individual devices, or one or more of the method steps may be implemented in a single functional block or by a single device.

[0216] Generally, the basic system architecture of a (remote) communication network, including a mobile communication system, to which some examples of the example embodiments apply, may include the architecture of one or more communication networks, the one or more communication networks including radio access network sub / systems and possibly a core network. Such an architecture may include one or more communication network control elements or functions, such as access network elements, radio access network elements, access service network gateways or transceiver base stations, such as base stations, access points, NodeB (NB), eNB or gNB, distributed or centralized units, which control the corresponding coverage areas or cells, and one or more communication stations capable of communicating with them via one or more communication beams transmitting several types of data in multiple access domains via one or more channels. The communication stations are, for example, communication elements or functions, such as user equipment or terminal devices, such as UE, or another device with a similar function, such as a modem chipset, chip, module, etc., which may also be part of a station, element, function or application capable of communicating, such as a UE, an element or function usable in a machine-to-machine communication architecture, or attached as a separate element to such an element, function or application capable of communicating, etc. In addition, core network elements or network functions may be included, such as gateway network elements / functions, mobility management entities, mobile switching centers, servers, databases, etc.

[0217] The general functions and interconnections of the described elements and functions, which also depend on the actual network type, are known to those skilled in the art and are described in the corresponding specifications, and thus their detailed description is omitted here. It should be understood that several additional network elements and signaling links may be used for communication to or from elements, functions or applications, such as communication endpoints, communication network control elements (such as servers, gateways, radio network controllers), and other elements of the same or other communication networks other than those described in detail below herein.

[0218] The communication network architecture considered in the example of the example embodiment is also capable of communicating with other networks, such as the public switched telephone network or the Internet, including the Internet of Things. The communication network is also capable of supporting the use of cloud services for virtual network elements or their functions, where it should be noted that the virtual network part of the (remote) communication network can also be provided by non-cloud resources, such as an internal network, etc. It should be understood that the network elements and / or corresponding functions of the access system, core network, etc. can be implemented by using any node, host, server, access node or entity suitable for such use. Generally, network functions can be implemented as network elements on dedicated hardware, software instances running on dedicated hardware, or virtualized functions instantiated on a suitable platform (e.g., cloud infrastructure).

[0219] Any method step is suitable for being implemented as software or hardware without changing the idea or scope of the various example embodiments. Such software can be independent of the software code and can be specified using any known or future-developed programming language, such as Java, C++, C, and assembler, as long as the function defined by the method step is retained. Such hardware can be independent of the hardware type and can be implemented using any known or future-developed hardware technology or any combination of these, such as MOS (metal oxide semiconductor), CMOS (complementary MOS), BiMOS (bipolar MOS), BiCMOS (bipolar CMOS), ECL (emitter-coupled logic), TTL (transistor-transistor logic), etc., using, for example, ASIC (application-specific IC (integrated circuit)) components, FPGA (field-programmable gate array) components, CPLD (complex programmable logic device) components, or DSP (digital signal processor) components. The device / apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module including such a chip or chipset; however, this does not exclude the possibility that the function of the device / apparatus or module (not hardware-implemented) is implemented as software in a (software) module, such as a computer program or a computer program product including an executable software code portion for execution / run on a processor. For example, the device can be regarded as a device / apparatus or a component of more than one device / apparatus, whether functionally cooperating with each other or functionally independent of each other, but in the same device housing.

[0220] The device and / or unit / component or part thereof can be implemented as an individual device, but this does not exclude the possibility that it can be implemented in a distributed manner throughout the system as long as the functionality of the device is retained. These and similar principles are considered to be known to those skilled in the art.

[0221] In the sense of this description, software comprises software code comprising code means or portions or a computer program or computer program product for performing the corresponding functions, as well as software (or computer program or computer program product) embodied on a tangible medium (such as a computer-readable (storage) medium) having the corresponding data structures or code means / portions stored thereon, or potentially embodied in a signal or in a chip during processing thereof.

[0222] The various example embodiments also cover any conceivable combination of the above method steps and operations, and any conceivable combination of the above nodes, apparatuses, modules, or elements, as long as the concepts of the above methods and structural arrangements are applicable.

[0223] In view of the above, measures are provided for enabling / implementing service enhancements for an IP Multimedia Subsystem (IMS) Data Channel (DC), for example, in an IMS DC architecture. Such measures may exemplarily include: an information storage entity receiving and storing user-specific information of a first party and / or user-specific information of a second party of an IMS session involving an IMS DC, and a service providing entity receiving the user-specific information of the first party and / or user-specific information of the second party of an IMS session involving an IMS data channel from the information storage entity, and providing a customized service via the IMS DC based on the user-specific information of the first party and / or the user-specific information of the second party.

[0224] Although various exemplary embodiments have been described above with reference to the accompanying drawings, it should be understood that the various exemplary embodiments are not limited thereto. On the contrary, it is obvious to those skilled in the art that the various exemplary embodiments may be modified in many ways without departing from the intended scope.

Claims

1. A method, comprising: Receiving, by a first IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party of an IMS session involving an IMS DC, Storing, by the first IMS DC entity, the user-specific information of the first party, Receiving, by the first IMS DC entity, user-specific information of a second party of the IMS session, and Storing, by the first IMS DC entity, the user-specific information of the second party.

2. The method according to claim 1, further comprising: Receiving, by the first IMS DC entity, a request for the user-specific information of the first party and / or the user-specific information of the second party from a second IMS DC entity, and Sending a message to the second IMS DC entity, the message including the user-specific information of the first party and / or the user-specific information of the second party.

3. The method according to claim 1 or 2, wherein Receiving, by the first IMSDC entity, user-specific information of the first party and user-specific information of the second party includes: The first IMS DC entity receives an IMS DC request.

4. The method according to claim 1 or 2, wherein In response to a request for user-specific information from a third IMS DC entity, the user-specific information of the first party and / or the user-specific information of the second party is received by the first IMS DC entity.

5. The method according to any one of claims 1 to 4, wherein The user-specific information indicates at least one of the following: Subscriber information associated with a service subscription, User-specific information of a network hosting or supporting an IMS DC architecture, User information, User equipment information, Network information, Telephone number, Mobile Subscriber Integrated Services Digital Network Number (MSISDN), User identifier, User equipment capability information, Location, Access network, Access type.

6. The method according to any one of claims 1 to 5, wherein The first IMS DC entity is, implements, includes, or is constituted by the following: a Data Channel Application Repository (DCAR) or an entity having a corresponding function, and / or The user-specific information of the first party and / or the user-specific information of the second party is received by the first IMS DC entity from an information providing entity, the information providing entity being, implementing, including, or constituted by the following: a Data Channel Signaling Function (DCSF) or an entity having a corresponding function, and / or The user-specific information of the first party and / or the user-specific information of the second party is received by the first IMS DC entity from an information providing entity, the information providing entity being, implementing, including, or constituted by the following: an IMS Application Server (IMS AS) or an entity having a corresponding function.

7. The method according to any one of claims 1 to 5, wherein The first IMS DC entity is, implements, includes, or is constituted by the following: a Data Channel Signaling Function (DCSF) or an entity having a corresponding function, and / or The user-specific information of the first party and / or the user-specific information of the second party is received by the first IMSDC entity from an information providing entity, which is, implements, includes, or consists of: an IMS application server (IMS AS) or an entity with corresponding functions.

8. The method according to any one of claims 1 to 5, wherein The first IMSDC entity is, implements, includes, or consists of: a data channel media function (DCMF) or an entity with corresponding functions, or the first IMSDC entity is, implements, includes, or consists of: an enhanced media resource function (MRF) or any entity with corresponding functions, and / or The user-specific information of the first party and / or the user-specific information of the second party is received by the first IMSDC entity from an information providing entity, which is, implements, includes, or consists of: an IMS application server (IMS AS) or an entity with corresponding functions.

9. The method according to any one of claims 1 to 5, wherein The user-specific information of the first party and / or the user-specific information of the second party is received locally by the first IMSDC entity, where the first IMSDC entity is, implements, includes, or consists of: an IMS application server (IMS AS) or an entity with corresponding functions.

10. The method according to any one of claims 1 to 9, wherein The IMSDC application is or corresponds to at least one of the following: an over-the-top (OTT) application, an over-the-top (OTT) application related to communication services, a rich communication services (RCS) application, a public safety application, an emergency services application, a public safety answering point (PSAP) application, an enhanced caller ID application, an enterprise application, or a communication service provider (CSP) application.

11. The method according to any one of claims 1 to 10, wherein The communication is based on a data channel media type and / or the WebRTC data channel protocol, and / or The IMS session includes at least an IP voice (VoIP) call established or initiated between the first party and the second party, and / or Either the first party or the second party involves a user of the IMSDC and / or a subscriber of a network hosting or supporting the IMSDC architecture, and / or The IMSDC architecture is based on a 3GPP network as a communication service provider network.

12. A method, comprising: Receiving, by an IP multimedia subsystem (IMS) data channel (DC) entity, user-specific information of a first party and / or user-specific information of a second party of an IMS session involving an IMSDC from an information storage entity, and Providing, by the IMSDC entity, a customized service via the IMSDC based on the user-specific information of the first party and / or the user-specific information of the second party.

13. The method according to claim 12, wherein the receiving comprises: The IMSDC entity sends a request for user-specific information to the information storage entity, and The IMSDC entity receives a response from the information storage entity, the response including the user-specific information of the first party and / or the user-specific information of the second party.

14. The method according to claim 12 or 13, wherein providing the customized service includes: The IMSDC entity obtains service-related user information based on the user-specific information of the first party and / or the user-specific information of the second party; The IMSDC entity customizes the service based on the service-related user information.

15. The method according to any one of claims 12 to 14, wherein The user-specific information indicates at least one of the following: Subscriber information associated with a service subscription, Information specific to an IMSDC application and / or the service of an IMSDC application, User-specific information of a network hosting or supporting the IMSDC architecture, User information, User equipment information, Network information, Phone number, Mobile Subscriber Integrated Services Digital Network Number (MSISDN), User identifier, User equipment capability information, Location, Access network, Access type.

16. The method according to any one of claims 12 to 15, wherein The IMSDC entity is, implements, includes, or consists of: an IMSDC application server or an entity with corresponding functions, and / or the method is invoked or executed by an IMSDC application on an IMSDC application server or an entity with corresponding functions.

17. The method according to any one of claims 12 to 15, wherein The IMSDC entity is, implements, includes, or consists of: the user equipment of the first party or the user equipment of the second party or an entity with corresponding functions, and / or the method is invoked or executed by an IMSDC application on the user equipment of the first party or the user equipment of the second party or an entity with corresponding functions.

18. The method according to claim 16 or 17, wherein The information storage entity is, implements, includes, or consists of: a Data Channel Application Repository (DCAR) or an entity with corresponding functions, or The information storage entity is, implements, includes, or consists of: a Data Channel Signaling Function (DCSF) or an entity with corresponding functions, or The information storage entity is, implements, includes, or consists of: a Data Channel Media Function (DCMF) or an entity with corresponding functions, or the information storage entity is, implements, includes, or consists of: an Enhanced Media Resource Function (MRF) or an entity with corresponding functions, or The information storage entity is, implements, includes, or consists of: an IMS Application Server (IMS AS) or an entity with corresponding functions.

19. The method according to any one of claims 12 to 18, wherein The IMSDC application is or corresponds to at least one of the following: an Over-the-Top (OTT) communication application, an Over-the-Top (OTT) application related to communication services, a Rich Communication Services (RCS) application, a public safety application, an emergency services application, a Public Safety Answering Point (PSAP) application, an enhanced caller ID application, an enterprise application, or a Communication Service Provider (CSP) application.

20. The method according to any one of claims 12 to 19, wherein the communication is based on a data channel media type and / or the WebRTC data channel protocol, and / or the IMS session includes an Internet Protocol voice (VoIP) call established or initiated at least between the first party and the second party, and / or either the first party or the second party involves a user of the IMSDC and / or a subscriber of a network hosting or supporting the IMSDC architecture, and / or the IMSDC architecture is based on a 3GPP network as a communication service provider network.

21. A method, comprising: providing, by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, user-specific information of a first party of an IMS session involving the IMSDC, and providing, by the IMSDC entity, user-specific information of a second party of the IMS session.

22. The method according to claim 21, wherein the user-specific information indicates at least one of the following: subscriber information associated with a service subscription, user-specific information of a network hosting or supporting the IMSDC architecture, user information, user equipment information, network information, phone number, Mobile Subscriber Integrated Services Digital Network Number (MSISDN), user identifier, user equipment capability information, location, access network, access type. [[ID= ​ ​ ​ ​ ​ ​ The IMSDC entity is, implements, includes, or consists of: an IMS application server (IMS AS) or an entity with corresponding functions, and / or The user-specific information of the first party and / or the user-specific information of the second party is provided by the IMSDC entity to an information storage entity, which is, implements, includes, or consists of: a data channel media function (DCMF) or an entity with corresponding functions, or the information storage entity is, implements, includes, or consists of: an enhanced media resource function (MRF) or an entity with corresponding functions.

26. The method according to claim 21 or 22, wherein The IMSDC entity is, implements, includes, or consists of: an IMS application server (IMS AS) or an entity with corresponding functions, and / or The user-specific information of the first party and / or the user-specific information of the second party is provided by the IMSDC entity to an IMS application server (IMS AS) or an entity with corresponding functions.

27. The method according to any one of claims 21 to 26, wherein The IMSDC application is or corresponds to at least one of the following: an over-the-top (OTT) communication application, an over-the-top (OTT) application related to communication services, a rich communication service (RCS) application, a public safety application, an emergency service application, a public safety answering point (PSAP) application, an enhanced caller ID application, an enterprise application, or a communication service provider (CSP) application.

28. The method according to any one of claims 21 to 27, wherein The communication is based on a data channel media type and / or the WebRTC data channel protocol, and / or The IMS session includes at least an IP voice (VoIP) call established or initiated between the first party and the second party, and / or Either the first party or the second party involves a user of the IMSDC and / or a subscriber of a network hosting or supporting the IMSDC architecture, and / or The IMSDC architecture is based on a 3GPP network as a communication service provider network.

29. An apparatus, comprising: Components for receiving, by a first IP multimedia subsystem (IMS) data channel (DC) entity, user-specific information of a first party of an IMS session involving IMS DC; Components for storing, by the first IMSDC entity, the user-specific information of the first party; Components for receiving, by the first IMSDC entity, user-specific information of a second party of the IMS session; and Components for storing, by the first IMSDC entity, the user-specific information of the second party.

30. The apparatus according to claim 29, further comprising: Components for receiving, by the first IMSDC entity, a request for the user-specific information of the first party and / or the user-specific information of the second party from a second IMSDC entity; and A component for sending a message to the second IMSDC entity, the message including user-specific information of the first party and / or user-specific information of the second party.

31. The apparatus according to claim 29 or 30, wherein Receiving user - specific information of the first party and user - specific information of the second party by the first IMSDC entity includes: An IMSDC request is received by the first IMSDC entity.

32. The apparatus according to claim 29 or 30, wherein In response to a request for user-specific information from a third IMSDC entity, the user-specific information of the first party and / or the user-specific information of the second party is received by the first IMSDC entity.

33. The apparatus according to any one of claims 29 to 32, wherein The user-specific information indicates at least one of the following: Subscriber information associated with a service subscription, User-specific information of a network hosting or supporting the IMSDC architecture, User information, User equipment information, Network information, Telephone number, Mobile Subscriber Integrated Services Digital Network Number (MSISDN), User identifier, User equipment capability information, Location, Access network, Access type.

34. The apparatus according to any one of claims 29 to 33, wherein The first IMSDC entity is, implements, includes, or consists of: a Data Channel Application Repository (DCAR) or an entity with corresponding functions, and / or The user-specific information of the first party and / or the user-specific information of the second party is received by the first IMSDC entity from an information providing entity, the information providing entity being, implementing, including, or consisting of: a Data Channel Signaling Function (DCSF) or an entity with corresponding functions, and / or The user-specific information of the first party and / or the user-specific information of the second party is received by the first IMSDC entity from an information providing entity, the information providing entity being, implementing, including, or consisting of: an IMS Application Server (IMS AS) or an entity with corresponding functions.

35. The apparatus according to any one of claims 29 to 33, wherein The first IMSDC entity is, implements, includes, or consists of: a Data Channel Signaling Function (DCSF) or an entity with corresponding functions, and / or The user-specific information of the first party and / or the user-specific information of the second party is received by the first IMSDC entity from an information providing entity, the information providing entity being, implementing, including, or consisting of: an IMS Application Server (IMS AS) or an entity with corresponding functions.

36. The apparatus according to any one of claims 29 to 33, wherein The first IMSDC entity is, implements, includes, or consists of: a Data Channel Media Function (DCMF) or an entity with corresponding functions, or the first IMSDC entity is, implements, includes, or consists of: an Enhanced Media Resource Function (MRF) or any entity with corresponding functions, and / or The user-specific information of the first party and / or the user-specific information of the second party is received by the first IMSDC entity from an information providing entity, which is, implements, includes, or consists of the following: an IMS application server (IMS AS) or an entity with corresponding functions.

37. The apparatus according to any one of claims 29 to 33, wherein the user-specific information of the first party and / or the user-specific information of the second party is received locally by the first IMSDC entity, where the first IMSDC entity is, implements, includes, or consists of the following: an IMS application server (IMS AS) or an entity with corresponding functions.

38. The apparatus according to any one of claims 29 to 37, wherein the IMSDC application is or corresponds to at least one of the following: an over-the-top (OTT) application, an over-the-top (OTT) application related to communication services, a rich communication service (RCS) application, a public safety application, an emergency service application, a public safety answering point (PSAP) application, an enhanced caller ID application, an enterprise application, or a communication service provider (CSP) application.

39. The apparatus according to any one of claims 28 to 38, wherein the communication is based on a data channel media type and / or a WebRTC data channel protocol, and / or the IMS session includes at least an IP voice (VoIP) call established or initiated between the first party and the second party, and / or either the first party or the second party involves a user of the IMSDC and / or a subscriber of a network hosting or supporting the IMSDC architecture, and / or the IMSDC architecture is based on a 3GPP network as a communication service provider network.

40. An apparatus, comprising: means for receiving, by an IP multimedia subsystem (IMS) data channel (DC) entity, user-specific information of a first party and / or user-specific information of a second party of an IMS session related to an IMSDC from an information storage entity, and means for providing, by the IMSDC entity, a customized service via the IMSDC based on the user-specific information of the first party and / or the user-specific information of the second party.

41. The apparatus according to claim 40, further comprising: means for sending, by the IMSDC entity, a request for user-specific information to the information storage entity, and means for receiving, by the IMSDC entity, a response from the information storage entity, the response including the user-specific information of the first party and / or the user-specific information of the second party.

42. The apparatus according to claim 40 or 41, further comprising: means for obtaining, by the IMSDC entity, service-related user information based on the user-specific information of the first party and / or the user-specific information of the second party; means for customizing, by the IMSDC entity, a service based on the service-related user information.

43. The apparatus according to any one of claims 40 to 42, wherein the user-specific information indicates at least one of the following: subscriber information associated with a service subscription, information specific to an IMSDC application and / or the service of an IMSDC application, user-specific information of a network hosting or supporting the IMSDC architecture, user information, user equipment information, network information, phone number, Mobile Subscriber Integrated Services Digital Network Number (MSISDN), user identifier, user equipment capability information, location, access network, access type.

44. The apparatus according to any one of claims 40 to 43, wherein the IMSDC entity is, implements, includes, or consists of: an IMSDC application server or an entity having a corresponding function, and / or is invoked or executed by an IMSDC application on an IMSDC application server or an entity having a corresponding function.

45. The apparatus according to any one of claims 40 to 43, wherein the IMSDC entity is, implements, includes, or consists of: the user equipment of the first party or the user equipment of the second party or an entity having a corresponding function, and / or is invoked or executed by an IMS DC application on the user equipment of the first party or the user equipment of the second party or an entity having a corresponding function.

46. The apparatus according to claim 44 or 45, wherein the information storage entity is, implements, includes, or consists of: a Data Channel Application Repository (DCAR) or an entity having a corresponding function, or the information storage entity is, implements, includes, or consists of: a Data Channel Signaling Function (DCSF) or an entity having a corresponding function, or the information storage entity is, implements, includes, or consists of: a Data Channel Media Function (DCMF) or an entity having a corresponding function, or the information storage entity is, implements, includes, or consists of: an Enhanced Media Resource Function (MRF) or an entity having a corresponding function, or the information storage entity is, implements, includes, or consists of: an IMS Application Server (IMS AS) or an entity having a corresponding function.

47. The apparatus according to any one of claims 40 to 46, wherein the IMSDC application is or corresponds to at least one of the following: an Over-the-Top (OTT) communication application, an Over-the-Top (OTT) application related to a communication service, a Rich Communication Services (RCS) application, a public safety application, an emergency service application, a Public Safety Answering Point (PSAP) application, an enhanced caller ID application, an enterprise application, or a Communication Service Provider (CSP) application.

48. The apparatus according to any one of claims 40 to 47, wherein the communication is based on a data channel media type and / or the WebRTC data channel protocol, and / or the IMS session includes at least an IP voice (VoIP) call established or initiated between the first party and the second party, and / or Either the first party or the second party involves a user of the IMSDC and / or a subscriber of a network that hosts or supports the IMSDC architecture, and / or The IMSDC architecture is based on a 3GPP network as a communication service provider network.

49. An apparatus, comprising: means for providing user-specific information of a first party of an IMS session involving the IMSDC by an IP Multimedia Subsystem (IMS) Data Channel (DC) entity, and means for providing user-specific information of a second party of the IMS session by the IMSDC entity.

50. The apparatus according to claim 49, wherein The user-specific information indicates at least one of the following: Subscriber information associated with a service subscription, User-specific information of a network that hosts or supports the IMSDC architecture, User information, User equipment information, Network information, Telephone number, Mobile Subscriber Integrated Services Digital Network Number (MSISDN), User identifier, User equipment capability information, Location, Access network, Access type.

51. The apparatus according to claim 49 or 50, wherein The IMSDC entity is, implements, includes, or consists of: a Data Channel Signaling Function (DCSF) or an entity with a corresponding function, or the IMSDC entity is, implements, includes, or consists of: an IMS Application Server (IMSAS) or an entity with a corresponding function, and / or The user-specific information of the first party and / or the user-specific information of the second party is provided by the IMSDC entity to an information storage entity, which is, implements, includes, or consists of: a Data Channel Application Repository (DCAR) or an entity with a corresponding function.

52. The apparatus according to claim 49 or 50, wherein The IMSDC entity is, implements, includes, or consists of: an IMS Application Server (IMS AS) or an entity with a corresponding function, and / or The user-specific information of the first party and / or the user-specific information of the second party is provided by the IMSDC entity to an information storage entity, which is, implements, includes, or consists of: a Data Channel Signaling Function (DCSF) or an entity with a corresponding function.

53. The apparatus according to claim 49 or 50, wherein The IMSDC entity is, implements, includes, or consists of: an IMS Application Server (IMS AS) or an entity with a corresponding function, and / or The user-specific information of the first party and / or the user-specific information of the second party is provided by the IMSDC entity to an information storage entity, which is, implements, includes, or consists of: a Data Channel Media Function (DCMF) or an entity with a corresponding function, or the information storage entity is, implements, includes, or consists of: an Enhanced Media Resource Function (MRF) or an entity with a corresponding function.

54. The apparatus according to claim 49 or 50, wherein The IMSDC entity is, implements, includes, or consists of the following: an IMS application server (IMS AS) or an entity with corresponding functions, and / or The user-specific information of the first party and / or the user-specific information of the second party is provided by the IMSDC entity to an IMS application server (IMS AS) or an entity with corresponding functions.

55. The apparatus according to any one of claims 49 to 54, wherein The IMSDC application is or corresponds to at least one of the following: an over-the-top (OTT) communication application, an over-the-top (OTT) application related to communication services, a rich communication service (RCS) application, a public safety application, an emergency service application, a public safety answering point (PSAP) application, an enhanced caller ID application, an enterprise application, or a communication service provider (CSP) application.

56. The apparatus according to any one of claims 49 to 55, wherein The communication is based on a data channel media type and / or the WebRTC data channel protocol, and / or The IMS session includes at least an IP voice (VoIP) call established or initiated between the first party and the second party, and / or Either the first party or the second party involves a user of the IMSDC and / or a subscriber of a network that hosts or supports the IMSDC architecture, and / or The IMSDC architecture is based on a 3GPP network as a communication service provider network.

57. A system comprising at least two of the following: The apparatus according to any one of claims 28 to 39, The apparatus according to any one of claims 40 to 48, and The apparatus according to any one of claims 49 to 56.

58. A computer program product comprising computer program code that, when executed on a computer, is configured to cause the computer to perform at least the method according to any one of claims 1 to 11 or 12 to 20 or 21 to 28.

59. A computer-readable medium comprising program instructions for causing an apparatus to perform at least the method according to any one of claims 1 to 11 or 12 to 20 or 21 to 28.

Images