Secure (avatar) communication with adaptive language settings in a real-time communication system

Abstract

This invention describes a method and apparatus and computer program for secure Avatar communication with adaptive language settings in a real-time communication system. The invention allows two or communicating devices to securely exchange and agree on an Avatar and common adaptive language settings that can be used to perform adaptive language procedure in either a network centric or device centric manner.

Description

[0001] Secure (Avatar) communication with Adaptive language settings in a real-time communication system

[0002] FIELD OF THE INVENTION

[0003] This invention relates to a method, apparatus, and computer program for secure (Avatar) communication with adaptive language settings in a real-time communication system such as IMS.

[0004] BACKGROUND OF THE INVENTION

[0005] A new trend in voice communication systems is to enable real-time speech recognition and translation of speech (and possibly other media) to a person of another nationality. For example, some mobile phones (e.g. Galaxy S24 Series Live Translate) or an application (e.g. Al Phone) running on the mobile phone can take the speech of a voice call and then translate it to the receiving user. 3GPP is currently investigating the possibility to add automatic translation as a service to the IP Multimedia System (IMS), as mentioned in the use case on Natural Language Processing (NLP) on speech in real-time communication described in clause 4.2.5 of 3GPP TR 26.927. Also some proprietary, non-standardized, extensions to IMS have been investigated by some companies, as described in [1] M. A. TUNDIK, A. HILT, G. BOTA, L. NAGY and K. LUUKKANEN, "Access-independent Cloud-based Real-Time Translation Service for Voice Calls in Mobile Networks," 2018 11th International Symposium on Communication Systems, Networks & Digital Signal Processing (CSNDSP), Budapest, Hungary, 2018, pp. 1-6, doi: 10.1109 / CSNDSP.2018.8471757.

[0006] Additionally, IMS (IP Multimedia Subsystem) systems are introducing the usage of Avatar communication as described in 3GPP TR 22.856 and TR 23.700-77, and this allows for a better interaction between the communicating parties. Avatars enable users to engage in more personalized and expressive communication, enhancing the overall user experience. This innovation in IMS systems leverages advanced graphics and real-time data processing to create dynamic and interactive representations of users during communication sessions, e.g. as described in clause 4.2.2.2 of 3GPP TR 26.927. However, different users may have different language preferences, and it remains a challenge how to facilitate interaction in these cases. Another challenge refers to the Avatar communication itself, e.g., how to retrieve and / or authenticate and authorize the Avatar selected by a user. SUMMARY OF THE INVENTION

[0007] An aim of the invention is to address above problems enabling secure Avatar communication with adaptive language settings in real time communication systems.

[0008] To this end, it is proposed methods, the apparatuses and the computer program product as defined in the appended set of claims.

[0009] In accordance with a first aspect of the invention, it is proposed a method performed by a sending wireless device (e.g. a UE) in an avatar communication session, such as a IP Multimedia Subsystem (IMS) avatar communication session, in a receiving wireless device-centric rendering mode, comprising: selecting an Avatar Identifier (Avatar ID) for an avatar representation associated with the sending UE; generating, by the sending wireless device, an authorization token that includes:

[0010] (i) the Avatar ID,

[0011] (ii) a sending wireless device identifier of the sending wireless device,

[0012] (iii) a receiving wireless device identifier of a receiving wireless device,

[0013] (vi) an expiration time; signing the authorization token, e.g. digitally signing, to obtain a signed authorization token; and transmitting, via a data channel between the sending wireless device and the receiving wireless device, the signed authorization token together with an address, such as a URL, associated with the selected Avatar ID to enable the receiving wireless device to downloading of the avatar representation associated with the sending wireless device.

[0014] Optionally, the data channel is an established application data channel.

[0015] In a variant, the authorization token comprises the address, or part of the address or an indication of the address.

[0016] In accordance with a second aspect of the invention, it is proposed a sending wireless device, such as a UE, comprising one or more processors, a memory storing instructions, and a transceiver, the instructions when executed causing the sending wireless device to: select an Avatar ID for an avatar representation of the sending wireless device; generate an authorization token that includes: the Avatar ID, a wireless device identifier of the sending wireless device, a wireless device identifier of the receiving wireless device, and an expiration time, and sign the authorization token to obtain a signed authorization token; and transmit, via a data channel with a receiving wireless device, the signed authorization token together with an address, such as a URL, associated with the Avatar ID for use in receiving-wireless device-centric rendering.

[0017] Optionally, the authorization token includes the address, or part of the address or an indication of the address.

[0018] In accordance with a third aspect of the invention, it is proposed a method performed by a receiving wireless device (e.g. a UE) in an IMS avatar communication session in receiving-wireless device-centric rendering mode, comprising: receiving, via a data channel between a sending wireless device and the receiving wireless device, a received authorization token and an address associated with an Avatar ID selected by the sending wireless device, or an indication of the address, the token including at least: the Avatar ID, a sending wireless device identifier, a receiving wireless device identifier, and an expiration time; transmitting an avatar representation downloading request that includes the received authorization token to a media function (MF) for delivery to a Base Avatar Repository (BAR); obtaining an avatar representation associated with the sending wireless device in response to a successful verification at the BAR of a signature of the authorization token, the Avatar ID, the sending wireless device identifier, the receiving wireless device identifier; and of a valid expiry time of the authorization token ; and rendering the obtained avatar representation at the receiving wireless device.

[0019] Optionally, the avatar representation downloading request is transmitted directly or through a Distributed Content Application Server, DC AS.

[0020] In another option, the avatar representation is obtained from the MF or from the DC AS.

[0021] In another option, the token includes the address or part of the address or an indication of the address.

[0022] In accordance with a fourth aspect of the invention, it is proposed a receiving wireless device, such as a User Equipment, UE, comprising one or more processors, a memory storing instructions, and a transceiver, the instructions when executed causing the receiving wireless device to: receive, from a sending wireless device via a data channel, a signed authorization token and an address, such as a URL, or an indication of the address, wherein the address is associated with an Avatar ID selected by the sending wireless device, the token including at least: the Avatar ID, a UE identifier of the sending UE, a UE identifier of the receiving wireless device, and an expiration time; transmit an avatar representation downloading request including the token and the Avatar ID to an MF for delivery to a Base Avatar Repository, BAR, directly or through a Distributed Content Application Server, DC AS; receive, from the MF, the avatar representation associated to the sending UE upon successful verification of the authorization token at the BAR as defined by the token checks; and render the avatar representation received.

[0023] Optionally, the token includes the address or part of the address or an indication of the address.

[0024] In accordance with a fifth aspect of the invention, it is proposed a method for adaptive language configuration in a communication system wherein the method comprises: sending, by a first device, a communication request to initiate a communication with at least one second device, the request including an indication (to a network function or the second device) that adaptive language is supported at the first device, receiving, by the first device, a communication confirmation accepting the communication with one or more of the second devices, wherein the communication confirmation includes a configuration element comprising at least one of

[0025] * an indication of first adaptive language settings (e.g. to be applied at the first device),

[0026] * at least an indication of second adaptive language settings of at least the second device, and

[0027] * an adaptive language model or model identifier of an adaptive language model or a confirmation to use an adaptive language model pre-configured at the first device to perform the adaptive language procedures, performing, by the first device, a first adaptive language procedure to an incoming data stream from the one or more of the second devices according to the configuration element; and / or performing, by the first device, a second adaptive language procedure to one or more outgoing data stream to one or more second devices according to the second adaptive language settings and the adaptive language model.

[0028] In accordance with a sixth aspect of the invention it is proposed a method for adaptive language configuration in a communication system, wherein the method comprises: sending, by a first device, a communication request to initiate a communication with at least one second device, the request including an indication to a network function or the second device, wherein the indication comprises a request to perform adaptive language for the first device and / or second device, and wherein the method comprises at least one of: receiving, by the first device, a communication confirmation accepting the communication with one or more of the at least one second device, wherein the communication confirmation includes an indication of available languages to perform adaptive language, and sending, by the first device, the first adaptive language setting including at least an indication of a selected language from the available languages, or receiving, by the first device, a communication confirmation accepting the communication with one or more second devices, wherein the communication confirmation includes an indication of the first adaptive language settings, the first adaptive language setting including at least an indication of a selected language, and receiving, by the first device, at least a data stream whose adaptive language is according to the first adaptive language settings.

[0029] In accordance with a seventh aspect of the invention, it is proposed a method for adaptive language configuration in a communication system, the method comprising: receiving, by a second device, a communication request to initiate a communication with at least one first device, the request including an indication from a network function or the first device wherein the indication comprises a request to perform adaptive language, sending, by the second device, a communication confirmation accepting the communication with one or more of the at least one first devices, wherein the communication confirmation includes at least one of an indication of first adaptive language settings, an indication of second adaptive language settings of the second device, a request to perform adaptive language at the second device and a confirmation / user consent to perform adaptive language at the first device or network function.

[0030] In accordance with an eighth aspect of the invention, it is proposed a method for adaptive language configuration in a communication system, wherein the method comprises: receiving, by a second device, communication request to initiate a communication with at least one first device, the request including an indication from a network function or the first device, wherein the indication comprises an indication to perform adaptive language, sending, by the second device, a communication rejection, wherein the communication rejection indicates that the second devices does not accept the communication with one or more first devices or wherein the communication rejection includes at least one of an indication of a first rejected adaptive language setting, an indication of a second rejected adaptive language setting of the second device or a rejection to perform adaptive language at the first or second device or network function.

[0031] In a first variant, the method further comprises: receiving, by the second device, a further communication confirmation including a confirmation of the first and / or second adaptive language settings of at least the second device, and an adaptive language model or a model identifier of an adaptive language model or a confirmation to use an adaptive language model pre-configured at the second device to perform the adaptive language procedures, performing, by the second device, a second adaptive language procedure to one or more incoming data stream from one or more first devices according to the second adaptive language settings and the adaptive language model; and performing, by the second device, a first adaptive language procedure to one or more outgoing data stream to one or more first devices according to one or more of the first adaptive language settings and the adaptive language model.

[0032] In another variant, the first or second adaptive language settings comprise at least one of: an indication whether or not adaptive language should be activated or not, a preferred language, a preferred language when translating sign language into text, a preferred language complexity when translating, a preferred voice style, a minimum required accuracy level, a timing of the output of the adaptive language in relation to the original input, a volume of the output of the adaptive language in relation to the original input, a composition of the adaptive language and the original input, a list of available languages to perform the adaptive language procedure, translation thresholds when performing the adaptive language procedure, a network-centric rendering or User Equipment-centric rendering when executing the adaptive language procedures, an address, such as a URL, of an Avatar representative of the preferred language. In another variant, the adaptive language model comprises at least one of: a voice input to voice output translation model for an input-output language combination; a sign language to text translation model for the preferred language; a sign language to voice translation model for the preferred language; a voice input to sign language; a voice input to body language.

[0033] In another variant, the method comprises, if the first and / or second device is unable to apply all or some of the preferred adaptive language settings, the first and / or second device defaulting to a set of pre-configured language preferences stored in the first and / or second device and / or communication system.

[0034] In another variant, the method comprises, if the first and / or second device is unable to receive or process the adaptive language settings from the second and / or first device, a fallback mechanism is initiated, said fallback mechanism including the first and / or second device receiving a notification, said notification being indicative of a conflict and / or a default adaptive language setting.

[0035] In another variant, the method comprises the first device or the second device providing feedback for rating a quality of the adaptive language procedures, the quality including one or more of the accuracy of the adaptive language procedure, the effectiveness of the adaptive language procedure, the latency of the adaptive language procedure, the fluidity of a translated signal.

[0036] In another variant, the adaptive language procedure comprises combining the usage of the adaptive language model and of an Avatar representation in an Avatar communication.

[0037] In another variant, the adaptive communication settings of the first and / or second device are stored in and / or retrieved from a data function (e.g., HSS / UDM) in the communication system as part of the user's subscription data.

[0038] In another variant, the communication request or communication confirmation or communication rejection or notification or feedback are communication protocol commands, voice commands or A / V output.

[0039] In accordance with a ninth aspect of the invention, it is proposed a method for operating a communication system, said communication system comprising a device performing the method of any of fifth to eighth aspects and their variants.

[0040] In a variant, the method comprises the first device and / or second device and / or a network function in the communication system learning a user's language preferences over time and automatically updating stored preferences based on previous selections and interactions of the user.

[0041] In another variant, the method comprises, if some adaptive language settings are missing from either the first and / or the second device during the setup of the communication session, the communication system dynamically adjusting the adaptive language based on the context of the ongoing conversation.

[0042] In another variant, the method comprises the communication system storing a log of any missing adaptive language settings and notifying the first and / or second device to update their adaptive language for future communication sessions.

[0043] In another variant, the communication system utilizes Al-based algorithms to predict likely adaptive language settings for future sessions based on historical data and user behavior patterns and sends the predicted adaptive language settings to the first and / or second device.

[0044] In another variant, the method comprising the first and / or second devices synchronizing (optionally periodically) the stored adaptive language settings and / or model with the communication system to ensure up-to-date settings are available for seamless communication.

[0045] In another variant, the method comprises the first device and / or second device overriding a preconfigured or predicted adaptive language settings during a communication session if any of the first and second device prefers to select a different adaptive language setting.

[0046] In another variant, the first device and / or second device and / or network function in the communication system provides feedback to the entity performing the adaptive language procedure wherein the feedback comprises one or more: timing misalignment, request to repeat the adaptive language procedure with the same or different settings, request to adapt the adaptive language settings.

[0047] In another variant, the first device and / or second device and / or network function in the communication system provides feedback to the first or second device about adaptive language processing errors, which may include a request for the user to repeat part of the communication or to slow down the communication.

[0048] In accordance with a tenth aspect of the invention, it is proposed an apparatus for adaptive language settings in a communication system wherein the apparatus comprises a transmitter, a receiver, and a controller; wherein the transmitter is configured to send a communication request to initiate a communication with at least a second device, the request including an indication to a network function or the second device wherein the indication comprises an indication to perform adaptive language at the apparatus, wherein the receiver is configured to receive a communication confirmation accepting the communication with one or more second devices, wherein the communication confirmation includes a configuration element comprising at least one of the first adaptive language settings (e.g. to be applied at the first device), at least an indication of second adaptive language settings of at least the second device and / or an adaptive language model or model identifier of an adaptive language model or a confirmation to use an adaptive language model pre-configured at the first device to perform the adaptive language procedures, wherein the controller is configured to performing at least one of a first adaptive language procedure to an incoming data stream from one or more second devices according to the configuration element; and / or a second adaptive language procedure to one or more outgoing data stream to one or more second devices according to the second adaptive language settings and the adaptive language model.

[0049] In accordance with an eleventh aspect of the invention, it is proposed an apparatus for adaptive language settings in a communication system wherein the apparatus comprises: a transmitter, a receiver, and a controller: wherein the controller causes the transmitter to send a communication request to initiate a communication with at least one second device, the request including an indication to a network function or the second device wherein the indication comprises a request to perform adaptive language for the apparatus and / or second device, wherein the receiver is configured for receiving a communication confirmation accepting the communication with one or more second devices, wherein the communication confirmation includes an indication of available languages to perform adaptive language, and the transmitter sends the first adaptive language setting including at least an indication of a selected language from the available languages, and / or wherein the receiver is configured for receiving the communication confirmation accepting the communication with one or more second devices, wherein the communication confirmation includes an indication of the first adaptive language settings, the first adaptive setting including at least an indication of a selected language, and the receiver is configured for receiving at least a data stream whose adaptive language is according to the first adaptive language settings.

[0050] In accordance with a twelfth aspect of the invention , it is proposed an apparatus for adaptive language settings in a communication system wherein the apparatus comprises: a receiver configured for receiving a communication request to initiate a communication with at least one first device, the request including an indication from a network function or the first device wherein the indication comprises a request to perform adaptive language, a transmitter configured for sending a communication confirmation accepting the communication with one or more of the at least one first devices, wherein the communication confirmation includes at least one of an indication of the first adaptive language settings, an indication of the second adaptive language settings of the apparatus, a request to perform adaptive language at the apparatus and a confirmation / user consent to perform adaptive language at the first device or network function.

[0051] In accordance with a thirteenth aspect of the invention, it is proposed an apparatus for adaptive language settings in a communication system wherein the apparatus comprises: a receiver configured for receiving communication request to initiate a communication with at least one first device, the request including an indication from a network function or the first device, wherein the indication comprises an indication to perform adaptive language, a transmitter adapted to send a communication rejection indicating that the apparatus does not accept the communication with one or more first devices or wherein the communication rejection includes at least one of an indication of a first rejected adaptive language setting, an indication of a second rejected adaptive language setting of the apparatus or a rejection to perform adaptive language at the apparatus, the first device or network function.

[0052] In accordance with a fourteenth aspect of the invention , it is proposed a computer program product comprising instructions which, when executed on a device, cause the device to perform the methods of any of the previously introduced aspects and variants.

[0053] It shall be understood that a preferred embodiment of the invention can also be any combination of the dependent claims or above embodiments with the respective independent claim.

[0054] These and other aspects of the invention will be apparent from and elucidated with reference to the embodiments described hereinafter.

[0055] BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 schematically represents the overall cellular system including UEs, RAN, and core network;

[0056] Fig. 2 provides a schematic representation of a UE and its components; and

[0057] Fig. 3 schematically represents different entities involved in a non-terrestrial network; Fig. 4 schematically represents a random-access procedure in a wireless network;

[0058] Fig. 5 schematically represents a signalling procedure by an access device;

[0059] Fig. 6 schematically represents the periodic transmission of SSB bursts;

[0060] Fig. 7 schematically represents the communication flow in a real time communication system involving adaptive language procedures; and

[0061] Fig. 8 schematically represents the communication flow in a communication system using avatar communication.

[0062] DETAILED DESCRIPTION OF EMBODIMENTS

[0063] Embodiments of the present invention are now described based on a cellular communication network environment, such as 5G or 6G. However, the present invention may also be used in connection with other wireless technologies or communication technologies in which language translation services and metaverse / avatar applications are provided or can be introduced.

[0064] Throughout the present disclosure, the abbreviation "gNB" (5G terminology) or "BS" (base station) or the term "access device" is intended to mean a wireless access device such as a cellular base station or a WiFi access point or a ultrawide band (UWB) personal area network (PAN) coordinator. The gNB may consist of a centralized control plane unit (gNB-CU-CP), multiple centralized user plane units (gNB-CU-UPs) and / or multiple distributed units (gNB-DUs). The gNB is part of a radio access network (RAN), which provides an interface to functions in the core network (CN). The RAN is part of a wireless communication network. It implements a radio access technology (RAT). Conceptually, it resides between a communication device such as a mobile phone, a computer, or any remotely controlled machine and provides connection with its CN. The CN is the communication network's core part, which offers numerous services to customers who are interconnected via the RAN. More specifically, it directs communication streams over the communication network and possibly other networks.

[0065] Furthermore, the terms "base station" (BS) and "network" may be used as synonyms in this disclosure. This means for example that when it is written that the "network" performs a certain operation it may be performed by a CN function of a wireless communication network, or by one or more base stations that are part of such a wireless communication network, and vice versa. It can also mean that part of the functionality is performed by a CN function of the wireless communication network and part of the functionality by the base station.

[0066] Furthermore, the term "network function" is used to denote a function or subsystem in a core network or adjacent / related parts of a cellular network deployment, such as IMS system (or subsystem or function thereof or a server hosting a Data Channel applications for deployment in an IMS system).

[0067] Moreover, the term "metaverse" is understood as referring to a shared set of interactable spaces, within which users may interact with one another alongside mutually perceived real-world and virtual features (i.e., augmented reality (AR)) or where those spaces are entirely composed of virtual features (i.e., virtual reality (VR)). VR and AR may generally be referred to as "mixed reality" (MR). In metaverse applications, users are typically represented by their "avatar".

[0068] Additionally, the term "data" is understood as referring to a representation according to a known or agreed format of information to be stored, transferred or otherwise processed. The information may particularly comprise one or more channels of audio, video, image, haptic, motion or other form of multimedia information that may be synchronized. Such multimedia information may be derived from sensors (e.g., microphones, cameras, motion detectors, etc.) or may be partially or wholly synthesized (e.g., live actor in front of a synthetic background). These sensors may be used to control or create expressions to the avatar representation of the user.

[0069] Companies could provide specific video conferencing 'facilities' within a 'location' within the metaverse, where conference calls could take place (to those inside and outside the metaverse), possibly with the cooperation of the metaverse provider. Companies could also provide voice / video-over-IP services, which may offer an identity or a phone number that users can use on various devices for making calls, sending messages, and receiving / sending voicemails. Calling may be performed over the Internet, IP Multimedia System (IMS) or legacy cellular or other wireless communication (e.g. if initial or final leg is needed using a legacy cellular network connection). The app loaded on e.g. a user's mobile phone may be configured to inform dedicated servers about the user's IP location and to forward calls (e.g., on a 5G communications systems to a (assigned) network telephone number) to predetermined destinations for that number. The call may be forwarded to the dedicated servers and these route the call through the Internet, IMS (or other cellular infrastructure) to the receiving devices. In case of metaverse users calling with people outside the metaverse (or another metaverse) and vice versa, networks need to collaborate with metaverse servers and serve them calls and vice versa.

[0070] The IP Multimedia Subsystem (IMS) as specified in 3GPP TS 23.228 is an architectural framework designed to deliver IP-based multimedia services. Originally conceived by the 3rd Generation Partnership Project (3GPP) for mobile networks, IMS has since been adopted across various types of network infrastructures, including fixed-line and cable networks. IMS aims to provide a seamless, integrated experience for users accessing multimedia services, such as voice, video, and data, over an IP network. IMS comprises several key components that work together to facilitate the delivery of multimedia services such as (1) Proxy-CSCF (P-CSCF): The first point of contact for the user equipment (UE). It handles session initiation, termination, and routing of SIP (Session Initiation Protocol) messages; (2) Interrogating-CSCF (l-CSCF): Acts as an entry point to the home network and performs user location queries to route the requests appropriately, and (3) Serving-CSCF (S-CSCF): The central component that maintains session state and interacts with other network entities to manage sessions. Furthermore, the HSS is a centralized database that contains user-related information, such as subscription data, user profiles, and authentication and authorization information. It plays a crucial role in supporting various IMS functions. Application Servers (AS) host and execute the services and applications that utilize the IMS framework. IMS relies on several key protocols to ensure the seamless delivery of multimedia services, including, Session Initiation Protocol (SIP) and Real-Time Protocol (RTP) . SIP is the primary signaling protocol used in IMS for session initiation, modification, and termination. It enables the establishment of multimedia sessions and supports various communication types, such as voice, video, and instant messaging. RTP is employed for the transmission of real-time audio and video data over IP networks. It ensures the timely delivery of media streams and handles synchronization and sequencing.

[0071] The embodiments of this invention may be illustrated in the context of a real time communication system based on IMS that may include components as illustrated in Fig. 7 wherein entities 1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, and 1008 correspond to a first UE (UE_A) and / or user, an avatar / digital asset repository or database, the Media Function / Media Rendering Function (MF / MRF), a Data Channel (DC) Application Server (AS) and / or an extended Reality (XR) / Augmented Reality (AR) AS, the Data Channel Signalling Function (DCSF), an IMS AS, a core network function in charge of identity management (e.g., HSS or UDM / UDR), a third party issuing identities / signatures, and a second UE (UE_B) and / or user, respectively. Other entities such as a Proxy- Call Session Control Function (P-CSCF) or an Interrogating-Call Session Control Function (l-CSCF) or IMS Gateway may be involved as well.

[0072] Step 1009 may include establishing an Audio / Video (which may be audio only) communication session between UE_A and UE_B (which may include a generic session setup similar to the procedure 5.4.6.3 in TS 23.228 and / or an A / V codec negotiation similar to the procedure 5.11.3.1 in TS 23.228) or an initial configuration step of UEs (e.g., with authorization tokens, or policies) or authorization policies for some functions (e.g., authorization or configuration information related to Avatar repository 1001). This step may also include negotiating and establishing a Data Channel (e.g. similar to procedures in Annex AC.7, or e.g. step 1 in Annex AC.9.3.1 and Annex AC.9.3.2 in TS 23.228).

[0073] Step 1010 may comprise an initial A / V and / or AR media rendering negotiation step (e.g., similar to Annex AC.9.3.2 in TS 23.228, step 3) wherein an Avatar model or the use of adaptive language may be negotiated, e.g., for UE_A or where e.g. the use of a MRF for transcoding is negotiated (e.g. similar to 5.14 and Annex P of TS 23.228).

[0074] Step 1011 may refer to media (re-)negotiation between UE_B and IMS network (e.g. similar to Annex AC.9.3.2 in TS 23.228, step 6), e.g. for a given Avatar model.

[0075] Steps 1010 and 1011 may be combined when performed end-to-end between UE A and UE-B, e.g. similar to Annex AC.9.3.1 in TS 23.228, step 2.

[0076] Step 1012 may refer to an internal configuration / authentication / authorization of an Avatar communication and / or adaptive language based on the user / UE identities, Avatar model and / or adaptive language service / application to use, and policies, this may involve configuring an Avatar model and / or adaptive language service / application at the MF / MRF 1002 or at one of the UEs, e.g., UE_A or UE_B.

[0077] Step 1013 may indicate the start of the communication wherein UE_A transmits stream data (audio / video / sensed gestures / ...) to 1002.

[0078] In Step 1014, 1002 may perform the transcoding / rendering based on an Avatar model and / or e.g. an adaptive language service (e.g. real-time translation of one spoken language to another spoken language).

[0079] In Step 1015 the rendered data is sent to UE_B. This procedure is exemplary and may be combined with other aspects, e.g., the transcoding / rendering may be performed at UE_A 1000 or UE_B 1008 requiring the storage of the Avatar model and / or adaptive language service / application and / or related data at UE_A or UE_B and e.g. combining steps 1013 and 1015 through an end-to-end communication whereby step 1014 may be performed in one of the UEs.

[0080] The Media Function / Media Rendering Function (MF / MRF) plays a pivotal role in ensuring smooth communication between devices by supporting media transcoding technologies such as Automatic Speech Recognition (ASR), Text-to-Speech (TTS), Sign Language Recognition (SLR), and Sign Language Synthesis (SSL). ASR technology converts spoken language into written text, enabling seamless interaction between users and machines. By analyzing audio signals and matching them to linguistic units, ASR systems can transcribe speech in real-time. TTS technology synthesizes spoken language from written text, providing a natural-sounding voice output. SLR technology involves the automatic interpretation of sign language gestures into text or spoken language bridging communication gaps between deaf and hearing individuals. SSL technology converts text or spoken language into sign language gestures, enabling communication with sign language users.

[0081] Next multiple embodiments of the invention are provided wherein the first UE may be called UE_A or first device and the second UE may be called UE_B or second device. Although the embodiments are primarily described in the context of IMS, they may also apply to other (real-time) communication systems or (A / V) messaging systems.

[0082] An embodiment of the invention involves adaptive language settings in a communication system. This embodiment may function independently or in conjunction with other embodiments, and it includes the following steps:

[0083] (1) A first User Equipment (UE), referred to as UE_A, may initiate a communication request to establish a connection with a second User Equipment, referred to as UE_B. This request may be a SIP message, and may include an indication to a network function, e.g. IMS function such as the Media Function / Media Rendering Function (MF / MRF), Data Channel Signalling Function (DCSF), or IMS Application Server (IMS AS), or to UE B, specifying the need to perform adaptive language procedures (as defined below) at UE_A. This message may include adaptive language preferences and / or adaptive language capabilities of UE_A, e.g., by including some first adaptive language settings as defined below that may have been provided by the user (e.g. through user interaction with an application / service on a mobile phone).

[0084] (2) UE_A may receive a communication confirmation accepting the communication request from one or more network functions (e.g. IMS system) or UE_B. This confirmation may include, e.g., the first adaptive language settings (as defined below), an indication of the second adaptive language settings for UE_B, and an adaptive language model (as defined below) or model identifier of an adaptive language model (e.g. of a previously downloaded language model) or a confirmation to use an adaptive language model pre-configured at UE A to perform the adaptive language procedures, or a list of adaptive language capabilities (e.g. whether adaptive language is supported or not, available types of adaptive language procedure or available voice styles) offered by one or more network functions and / or UE_B. Additionally or alternatively, this confirmation may also include (reference to) a Data Channel (DC) application and / or metadata thereof (e.g. list of adaptive language capabilities offered by such DC application) that is able to perform adaptive language procedures (e.g. using an adaptive language model for real-time translation) or a list of Data Channel (DC) applications that UE_A can choose from that may include a DC application to perform adaptive language procedures, upon which the selected DC application may be downloaded to UE-A (and possibly also to UE_B). (3) UE_A may perform a first adaptive language procedure (as defined below) on an incoming data stream (typically an A / V stream) from UE_B according to the first adaptive language settings and the adaptive language model.

[0085] (4) Additionally, UE_A may perform a second adaptive language procedure on one or more outgoing data streams (typically one or more A / V streams) to UE_B, based on the second adaptive language settings and the adaptive language model.

[0086] This embodiment is advantageous because it allows UE_A / UE_B to determine / agree language preferences, e.g., when the rendering is performed at the UE side, in this case UE_A side. Similarly, the first and second adaptive language procedures may be performed at the UE_B side. Additionally or alternatively, the first and second adaptive language procedures may be performed by the one or more network functions (e.g. by an IMS Media Function (MF) or DC application).

[0087] In an example, UE_A and UE_B set up a P2P Application Data Channel (e.g. as specified in clause AC.7.2.1 of 3GPP TS 23.228), whereby the data channel between UE_A and UE_B may be used for transmitting a request to invoke / perform adaptive language (possibly instead of sending this request as part of a SIP request), and / or for transmitting messages that may include adaptive language preferences to be applied and / or adaptive language capabilities of UE_A and / or UE_B, and / or messages to request and / or confirm which UEs will perform adaptive language and / or which adaptive language preferences they will apply. UE_A and / or UE_B may set up an A / V session so that in case UE_A and / or UE_B perform adaptive language upon transmitting, they can transmit the adapted A / V stream after applying adaptive language to the other UE. In case only the receiving UE performs adaptive language, UE_A and / or UE_B transmit the original A / V stream to the other UE, upon which the receiving UE performs the adaptive language. Additionally or alternatively, the A / V session is established before the adaptive language is invoked. In such case, UE_A and / or UE_B may establish a P2P Data Channel at a later point to request to invoke / perform adaptive language.

[0088] In another example, UE_A and UE_B set up a Person-to-Application and Application-to-Person (P2A2P) Procedure (e.g. as specified in clause AC.7.2.3 of 3GPP TS 23.228), whereby the data channel between UE_A, UE_B and a Network Function (e.g. MF / MRF) may be used for transmitting a request to invoke / perform adaptive language (possibly instead of sending this request as part of a SIP request), and / or for transmitting messages that may include adaptive language preferences to be applied and / or adaptive language capabilities of UE_A and / or UE_B and / or the Network Function, and / or messages to request and / or confirm which UEs and / or Network Function will perform adaptive language and / or which adaptive language preferences they will apply. UE_A and / or UE_B may set up an A / V session with the Network Function so that in case the Network Function performs adaptive language upon transmitting, they can transmit the original A / V stream to the Network Function, upon which the Network Function performs the adaptive language and transmits the adapted A / V stream to the receiving UE(s). Additionally or alternatively, the A / V session is established before the adaptive language is invoked. In such case, UE_A and / or UE_B and Network Function may establish a P2PAP Data Channel at a later point to request to invoke / perform adaptive language.

[0089] In another example, UE_A and UE_B set up a multimedia telephony (MMTEL) session (e.g. as specified in clause 4.16, 5.4 of 3GPP TS 23.228) and / or a WebRTC session (e.g. as specified in clause U of TS 23.228) directly between each other or indirectly via a Network Function (e.g. Call Session Control Function (CSCF), Media Gateway Function (MGW), IMS, IMS Access Gateway or elMS-AGW), whereby SIP messages may be used between UE_A and / or UE_B and / or a Network Function for transmitting a request to invoke / perform adaptive language (e.g. as part of SDP description having some new / additional fields for this purpose, or new SIP message or new field in SIP message, e.g. to indicate a preferred language and / or an available source-target language translation pair), and / or for transmitting messages that may include adaptive language preferences to be applied and / or adaptive language capabilities of UE_A and / or UE_B and / or network function, and / or messages to request and / or confirm which UEs and / or network function will perform adaptive language and / or which adaptive language preferences they will apply. Based on the exchange of such SIP messages UE_A and / or UE_B and / or a network function may be involved in performing adaptive language. In case the two UEs set up an A / V session whereby UE_A and / or UE_B perform adaptive language upon transmitting, they can transmit the adapted A / V stream after applying adaptive language to the other UE. In case only the receiving UE performs adaptive language, UE_A and / or UE_B transmit the original A / V stream to the other UE, upon which the receiving UE performs the adaptive language. Additionally or alternatively, the SIP message may include an Accept-Contact field (e.g. as specified in IETF RFC 3841) which may be extended to include an indication of an adaptive language service to be invoked / applied and / or a set of adaptive language preferences to be applied. This may be used to indicate a request for UE_A to apply adaptive language e.g. by UE_B, during a communication session between UE_A and UE_B. If adaptive language is not available or will not be performed (e.g. because UE_A or UE_B not authorized to invoke adaptive language service), a 480 return code may be provided to UE_A and / or UE_B. Additionally or alternatively, a Network Function may be involved in performing adaptive language. To this end, the SIP messages may include an IMS communication service identifier that indicates a Network Function (e.g. address of an (application) server) to be invoked that performs adaptive language, e.g. in the REGISTER and INVITE request (e.g. as specified in clause 4.13 of TS 23.228). The Network Function that perform the adaptive language may be deployed as a supplementary services, in which case the requested service may be activated using REGISTER / FACILITY message, using similar mechanism as in 3GPP TS 24.010, extended for invoking a supplementary service for adaptive language and / or for applying a set of adaptive language preferences and / or for exchange of capability information related to the adaptive language service. Note that such adaptive language service may be configured with a (new) set of adaptive language preferences using e.g. a) XCAP as enabling protocol over Ut as described in 3GPP TS 24.623, extended for this purpose; or b) use SIP based user configuration as described in 3GPP TS 24.238, extended for this purpose.

[0090] Additionally or alternatively, the A / V session is established before the adaptive language is invoked. In such case, UE_A and / or UE_B and / or Network Function may establish a new A / V session at a later point to request to invoke / perform adaptive language (e.g. using FACILITY message, or sending a new SIP message extended for the purpose of requesting adaptive language).

[0091] In general terms, an adaptive language procedure (also known as "adaptive language" in this document) can be defined as a process that considers the input audio / visual signal and utilizes the adaptive language settings and the adaptive language model to generate an output audio / visual signal that translates the input data stream into an output data stream (possibly in real-time or after a delay). The adaptive language procedure may be performed with support of the network (network rendering) or at the end sides (by means of UE rendering). This approach ensures that the communication is tailored to the linguistic preferences and needs of the users, providing a more inclusive and effective interaction.

[0092] In an embodiment of the invention for adaptive language settings in a communication system which may be combined with other embodiments or used independently, the adaptive language settings may comprise at least one of the following settings determining how the "translation between languages" is or should be performed. Some preferences / settings may be determined by the UEs while some settings / preferences may be determined by one or more network functions, e.g., IMS system, and may be based on the adaptive language capabilities of the UEs and / or the one or more network functions:

[0093] Indication of whether or not adaptive language should be activated or not, which could be different for text, voice, or sign language.

[0094] Preferred language: The primary language selected by the user for communication, which could be different for text, voice, or sign language.

[0095] Preferred language when translating sign language into text: The language output when converting sign language gestures into written text, ensuring that the translation aligns with the user's linguistic preferences. Preferred language complexity when translating: The chosen complexity level of language for translation, which could range from basic to advanced, depending on the user's proficiency and comprehension abilities.

[0096] Preferred voice style: The specific characteristics of the voice output, such as tone, pitch, speed, and accent, tailored to match user preferences for a more personalized experience.

[0097] Minimum required accuracy level: The threshold for the accuracy of translations, ensuring that the adaptive language model meets or exceeds this level to provide reliable communication.

[0098] Timing of the output of the adaptive language in relation to the original input: The synchronization of the translated output with the original input, which can be adjusted for real-time or delayed responses as needed by the user.

[0099] Volume of the output of the adaptive language in relation to the original input: The relative loudness of the translated output compared to the original input, which can be customized based on user preferences or environmental conditions.

[0100] Composition of the adaptive language and the original input: Detailed guidelines on how integrated or distinct the adaptive language output should be in comparison to the original input, such as fully replacing the original or providing side-by-side A / V renderings of the original and the translations.

[0101] Available languages to perform the adaptive language procedure: A list of all supported languages that the adaptive language model can utilize for translation, voice, and sign language outputs, ensuring comprehensive linguistic coverage.

[0102] The preferred type of adaptive language procedure (e.g., voice to voice, voice to text, voice to sign, text to voice, or text to sign).

[0103] Translation thresholds when performing the adaptive language procedure, wherein translation thresholds indicate how much certain language should be translated / allowed. For instance, a threshold may refer to avoid any obscene terms when performing the adaptive language procedure. For instance, adaptive language procedure may "translate" body language into certain expressions, e.g., when an Italian uses expressive hand movements, that body language may be used to enhance (or not enhanced) the spoken language when performing the adaptive language procedure.

[0104] Network-centric rendering or UE-centric rendering when executing the adaptive language procedures, i.e., executed in an entity such as the MF / MRF and / or executed by UE_A and / or UE_B.

[0105] In an embodiment of the invention for adaptive language settings in a communication system which may be combined with other embodiments or used independently, the adaptive language model may comprise various translation models used to perform the translation tasks, such as:

[0106] - A voice input to voice output translation model for an input-output language combination. This model may include advanced speech recognition and synthesis algorithms to ensure accurate and natural-sounding translations, which may be manipulated by the MF / MRF to maintain synchronization and context.

[0107] - A sign language to text translation model for the preferred language. This model may involve the use of sophisticated computer vision techniques to accurately interpret sign language gestures and convert them into written text. The DCSF may integrate these translations seamlessly into the communication stream for a more comprehensive user experience.

[0108] - A sign language to voice translation model for the preferred language. Utilizing deep learning algorithms, this model can interpret sign language gestures and convert them into spoken words. The IMS AS or network function (e.g. part of the IMS system) may enhance the voice output with appropriate intonation and emotion to reflect the original intent and nuances of the sign language input.

[0109] - A voice input to sign language translation model. This model may involve real-time speech recognition and avatar technology to translate spoken words into sign language, displayed through a visual representation on the screen. The MF / MRF may ensure that the avatar's gestures are synchronized with the spoken input, providing an intuitive and accessible communication experience for users relying on sign language.

[0110] - A voice input to body language translation model, which may involve an AI / ML model extracting the semantic meaning of the voice input and translating it into corresponding body language. The video stream may be manipulated by the M F / M RF to render body language that fits the semantic meaning of the voice input.

[0111] The quality of the translation is highly dependent on the translation model that is used, which may differ per operator or application provider. This may lead to interpretation issues. The originating user, but also the receiving user may wish to know how well the translation is expected to work before choosing a particular output language, since the user may want to choose another language if the quality is not sufficient. Otherwise, it may affect a user's ability to express him / herself if the translation is poor quality and may lead to misunderstandings. All this requires a dynamic negotiation mechanism.

[0112] Therefore, in an embodiment that may be combined with other embodiments or used independently for adaptive language settings in a communication system, UE_A may initiate communication with UE_B by sending a request, which may include an indication to a network function or UE B to perform adaptive language for UE A and / or UE B. Upon receiving this request, the network function or UE_B may respond with a communication confirmation indicating acceptance and may include details of the available languages for performing adaptive language and may include (reference to) a DC application (and / or metadata thereof) to download. The included details in the response message or in the metadata related to the DC application may e.g. be in the form of sourcetarget language translation pairs, possibly augmented with metadata about the translation, such as a translation score or an (achievable) accuracy level and / or information about the translation provider / application provider and / or Al model that is being used. UE_A may then select a language from the available options and send the selected language as its first adaptive language setting. Alternatively, the communication confirmation from the network function or UE_B may include the first adaptive language settings, which may include a selected language, in which case UE_A may simply accept those settings. Subsequently, UE_A may receive data streams where the adaptive language has been applied according to the first adaptive language settings. The IMS functions such as the MF / MRF or DCSF, or IMS AS, may facilitate these processes, e.g., when there is a mismatch between the adaptive language settings of UE_A and UE_B, ensuring that the adaptive language settings are correctly applied for seamless communication between UE_A and UE_B. This may require signalling / requesting / adapting the adaptive language settings upon communication with UE_A and / or UE_B.

[0113] An issue with current systems is that the originating user has no control over whether he / she wants his / her speech (or other input) to be processed in this manner. Since the speech will be processed and listened to by an Al system, it may it lead to privacy issues (e.g. contents of what is discussed in the call may need to remain secret) and hence the user may not trust certain systems, whereas it may trust other systems. Therefore, some authorization and consent management is required. Consent or at least a confirmation is also needed on whether to allow the original or translated communication to be used for improving the language / translation model.

[0114] Therefore, in an embodiment of the invention for adaptive language settings in a communication system that may be combined with other embodiments or used independently, the process may involve UE_B receiving a communication request from UE_A or a network function. This request may include an indication to perform adaptive language and may include a confirmation / user consent to perform adaptive language at UE_B or a network function. Upon receiving this request, UE_B may send a communication confirmation accepting the communication with one or more first devices. The communication confirmation may include at least one of the following: (1) an indication of the first adaptive language settings, (2) an indication of the second adaptive language settings of UE_B, (3) a request to perform adaptive language at UE_B or the network function, and (4) a confirmation / user consent to perform adaptive language at UE_A or the network function. Additionally, UE_B may receive further communication confirmation that includes the confirmation of (that may include user consent for the use of) the first and / or second adaptive language settings of at least UE_B and an adaptive language model or a model identifier to perform the adaptive language procedures. UE_B may then perform a second adaptive language procedure on one or more incoming data streams from one or more first devices according to the second adaptive language settings and the adaptive language model. Also, UE_B may perform a first adaptive language procedure on one or more outgoing data streams to one or more first devices according to one or more first adaptive language settings and the adaptive language model.

[0115] Additionally or alternatively, UE_A may request UE_B to confirm / give consent to perform adaptive language at UE_A or a network function, or vice versa UE_B may request UE_A to confirm / give consent to perform adaptive language at UE_A or a network function. Additionally or alternatively, the network function (e.g. after receiving a request for performing adaptive language procedures at either the network function or one of the UEs) may request UE_A and / or UE_B to confirm / give consent to perform adaptive language, upon which UE_A and / or UE_B may send a conformation message that includes an indication of consent to perform adaptive language. Note that consent can also be partial consent, e.g. only consent for using a subset of languages or subset of adaptive language settings.

[0116] In an embodiment of the invention that may be combined with other embodiments or used independently, the adaptive language settings in a communication system may involve UE_B receiving a communication request to initiate / re-initiate communication with at least UE_A. This request may include an indication from a network function (e.g. an IMS function part of the IMS system) or UE_A to perform adaptive language procedures. UE_B may optionally send a communication rejection if it does not accept the communication / adaptive language procedure with one or more first devices. This communication rejection may include : an indication of a first rejected adaptive language setting, an indication of a second rejected adaptive language setting of UE_B, or a rejection to perform adaptive language at UE_A or UE_B or a network function.

[0117] In an embodiment that may be combined with other embodiments or used independently, if the first or second device is unable to apply all preferred adaptive language settings due to technical constraints or lack of available data, the device defaults to a set of pre-configured language preferences stored in the device or network function. These default settings may include commonly used languages such as English, Spanish, or Mandarin, as well as basic translation features that do not rely on advanced algorithms or extensive data resources. Additionally or alternatively, the default settings may depend on the (requested) adaptive language settings of the first device (UE_A) and / or the second device (UE_B). The agreed default settings may be determined by a network function, e.g., XR AS. Several conditions may prevent the devices from applying all preferred adaptive language settings:

[0118] (1) Technical Constraints: Limitations in hardware or software capabilities may hinder the application of certain adaptive language settings. For instance, older devices may not support advanced speech recognition or deep learning algorithms required for accurate translations.

[0119] (2) Network Issues: Poor connectivity or low bandwidth can impact the ability to download or update language models in real-time, leading to reliance on pre-stored default settings.

[0120] (3) Data Availability: Insufficient linguistic data for less common languages or dialects may make it impossible to provide accurate translations, necessitating the use of more general language models.

[0121] (4) Processing Power: High computational demands of some translation models may exceed the processing capabilities of the device, especially in real-time scenarios, causing a fallback to simpler models.

[0122] (5) User Preferences: Users may have personalized settings that conflict with the adaptive language preferences, leading the system to prioritize user-defined configurations.

[0123] (6) Software Updates: Incomplete or pending software updates can restrict the functionality of adaptive language settings until the updates are fully installed and integrated.

[0124] In an embodiment that may be combined with other embodiments or used independently, if UE_A or UE_B is unable to receive or process the adaptive language settings from the other device, the communication system (e.g. UE_A and / or UE_B and / or network function) initiates a fallback mechanism. This mechanism includes sending a notification to both UE_A and UE_B about the conflict and / or indicating the default adaptive language setting. Detection of the inability to receive or process the adaptive language settings may involve several techniques, including but not limited to:

[0125] (1) Error Codes: If UE_A or UE_B encounters an error while applying the settings, an error code is generated and sent to the system.

[0126] (2) Timeouts: If there is no acknowledgment within a specified time frame after the adaptive language settings are sent, the system assumes failure.

[0127] (3) Communication Logs: Analyzing logs for unsuccessful attempts to apply settings can indicate issues.

[0128] (4) Health Checks: Periodic health checks of UE_A and UE_B to ensure they can process adaptive language settings. (5) User Feedback: Feedback from users indicating issues with adaptive language settings can trigger the fallback mechanism.

[0129] In one embodiment that may be used independently or combined with other embodiments, the first device and / or second device and / or a network system learns the user's language preferences over time and automatically update the stored preferences based on the user's previous selections and interactions. The preferences (e.g., adaptive language settings may be stored locally in the first and / or second device, or indicated / transmitted to a network system (e.g., HSS / UDM and / or XR AS). This learning can be conducted through several mechanisms, including:

[0130] (1) Usage Patterns: Monitoring the frequency and context in which specific languages are utilized during communication sessions.

[0131] (2) Interaction History: Analyzing past interactions to identify preferred language settings during different types of conversations or with different contacts.

[0132] (3) Al Algorithms: Employing advanced Al-based algorithms that predict language preferences based on historical data and user behavior patterns.

[0133] (4) User Feedback: Collecting and incorporating direct feedback from users regarding their language preferences and any issues they encounter.

[0134] (5) Contextual Analysis: Assessing the context of ongoing conversations to dynamically adjust language settings in real-time, ensuring seamless communication.

[0135] Aspects that can be learned include one or more of:

[0136] (1) Preferred Languages: The primary and secondary languages users prefer for different types of communication (e.g., work, personal, formal, informal).

[0137] (2) Preferred Language Styles: Formality level, dialects, and any specific terminology or jargon commonly used by the user.

[0138] (3) Device-Specific Settings: Adjusting settings based on the device being used, such as a smartphone, tablet, or computer, to optimize performance.

[0139] (4) Time-Sensitive Preferences: Learning if certain languages are preferred at different times of the day or for particular events or meetings.

[0140] (5) Contact-Specific Preferences: Identifying if the user prefers different languages when communicating with specific contacts or groups.

[0141] This approach is advantageous because it can allow reducing signalling and improve user experience.

[0142] In an embodiment that may be combined with other embodiments, it is preferred to perform the adaptive language procedure at the receiving device (e.g. using a pre-installed application / adaptive language model or a downloaded DC application with an adaptive language model). For instance, UE_B performs the adaptive language procedure for the data stream received from UE_A, and UE_A performs the adaptive language procedure for the data stream received from UE_B. This approach is advantageous because the receiving device can adapt settings faster, ensuring a more immediate and responsive adjustment to the ongoing conversation. The adaptive language procedure at the receiving device allows for real-time modifications based on the incoming data stream's content and context. By analyzing the received communication, the receiving device can dynamically adjust language settings to match the preferred languages, dialects, and formality levels of the user. This ensures that the communication remains coherent and aligned with user preferences without significant delays. This allows users to maintain control over their language preferences while benefiting from the system's adaptive language capabilities.

[0143] In an embodiment that may be combined with other embodiments, the communication system may adapt dynamically to any missing adaptive language settings during the setup of a communication session. If either the first device or the second device encounters missing settings, the communication system (e.g. the first device and / or second device and / or network function) may assess the context of the ongoing conversation. The system may employ Al-based algorithms to predict and fill in the missing adaptive language settings. This dynamic adjustment ensures that the communication remains seamless and coherent. The system may leverage historical data and user behavior patterns to make real-time predictions. For instance, if a user typically prefers formal language during work hours, the system may automatically adjust the language settings to align with this preference when a communication session is initiated during that time. Similarly, if a user prefers a specific dialect when speaking to certain contacts, the system may detect the contact and adjust the settings accordingly. Furthermore, the system may continuously monitor the conversation for context cues and user interactions that might necessitate a change in settings. If the conversation shifts from a formal to an informal tone, the system may promptly adapt the language settings to reflect this change. Any adjustments made by the system may be communicated to the first and / or second device in real-time, ensuring both parties are aware of the changes and can continue the conversation without interruption. The system may also provide an option for the first and / or second device to override the dynamically adjusted settings if they prefer to select a different adaptive language setting during the communication session. This flexibility allows users to maintain control over their language preferences while benefiting from the system's adaptive language capabilities.

[0144] In an embodiment that may be combined with other embodiments or used independently, the communication system stores a log of any missing adaptive language settings and notifies the first and / or second device to update their adaptive language for future communication sessions. The log of missing adaptive language settings contains detailed records of any gaps encountered during communication sessions. These records may include one or more of: (1) a timestamp: The exact date and time when the missing settings were detected.

[0145] (2) a device Information: Details about the first and / or second device involved, such as device type, model, and operating system.

[0146] (3) a session Context: Information about the context of the communication session, including the type of conversation (e.g., work, personal), the formality level, and any specific topics discussed.

[0147] (4) user Preferences: The preferred languages, dialects, and formality levels that were not initially set up or detected.

[0148] (5) Predicted Settings: Al-based predictions made to fill in the missing adaptive language settings, including the rationale behind these predictions based on historical data and behavior patterns.

[0149] (6) Adjustments Made: Any adjustments dynamically applied by the system during the session to ensure seamless communication, along with notifications sent to the devices.

[0150] (7) User Feedback: Feedback provided by the first and / or second device regarding the accuracy and effectiveness of the adaptive language settings.

[0151] This log helps the system to continuously improve its adaptive language model and ensures that future communication sessions are more aligned with user preferences. This log may be stored locally at the UEs or in a network function.

[0152] In an embodiment that may be combined with other embodiments or used independently, the communication system utilizes advanced AI / ML algorithms to predict likely adaptive language settings for future sessions based on historical data and user behavior patterns. These predictions are then communicated to the first and / or second device to ensure seamless and effective communication. Examples of AI / ML algorithms that can be employed include:

[0153] (1) Natural Language Processing (NLP) Algorithms: These algorithms can analyze the context, tone, and formality of previous communications to predict the most suitable language settings.

[0154] (2) Reinforcement Learning: This algorithm can continuously learn from user interactions and feedback to improve the accuracy of the adaptive language settings over time.

[0155] (3) Collaborative Filtering: Often used in recommendation systems, this algorithm can predict user preferences by analyzing patterns across different users with similar behavior.

[0156] (4) Decision Trees: These can be used to create a model that predicts adaptive language settings based on input features such as device type, session context, and user preferences.

[0157] (5) Neural Networks: Deep learning models can be trained on vast datasets of communication patterns to identify subtle cues and make highly accurate predictions.

[0158] The system dynamically applies these predictions during communication sessions, ensuring that language settings are always aligned with user preferences and context. This continual adaptation is supported by regular feedback from the devices involved, which helps enhance the language model and further refine the predictions. The system provides an option for the first and / or second device to override the pre-configured or predicted adaptive language settings during any communication session if they prefer to select a different setting.

[0159] In an embodiment that may be combined with other embodiments or used independently, the communication system includes signaling procedures for synchronization between the first and second devices, UE_A and UE_B, and the network function. These devices may periodically synchronize the stored adaptive language settings and / or models to ensure up-to-date configurations for seamless communication. During the initialization phase, UE_A and UE_B may send a synchronization request signal to the network function. This request may include the device identification, current adaptive language settings, and a timestamp marking the last synchronization event. Upon receiving the synchronization request, the network function may perform an authentication and verification process. This process ensures that the devices are authorized to access and update the adaptive language settings. The system may verify the device identification and check the timestamp to determine if synchronization is necessary. If synchronization is required, the system may transmit the latest adaptive language settings and model updates to the devices. This data transmission may be securely encrypted to protect the integrity and confidentiality of the settings. UE_A and UE_B may receive and store these updates, ensuring that they utilize the most current configurations for subsequent communication sessions. After successfully updating the adaptive language settings, the devices may send a confirmation signal back to the network function. This confirmation may include details on the successful update and any discrepancies or errors encountered during the synchronization process. Additionally, the devices may provide feedback on the effectiveness and accuracy of the new settings, which the system may use to refine future updates. The devices may periodically repeat this synchronization process, either at predefined intervals or triggered by specific events such as network reconnections or firmware updates. This periodic synchronization ensures that the adaptive language settings remain aligned with the latest user preferences and contextual requirements. The method may also include an option for the devices to override the pre-configured or predicted adaptive language settings during any communication session. This is signaled by sending an override request to the network function, along with the desired settings. The system may acknowledge this request and temporarily adjust the settings for the ongoing session.

[0160] In an embodiment that may be combined with other embodiments or used independently, the communication system may provide an option for UE_A and / or UE_B to override the pre-configured or predicted adaptive language settings during any communication session if either of them prefers to select a different adaptive language setting. This overriding process may be signaled by sending an override request from UE_A or UE_B to the communication system. The request may include the desired adaptive language settings along with relevant session information. Upon receiving this request, the system may acknowledge it and temporarily adjust the language settings for the ongoing session. Furthermore, the devices may offer a user interface allowing users to manually select or adjust the language settings before or during a session (e.g. as part of a call-setup screen or screen displayed during a call). This interface may provide options such as a dropdown menu or toggle buttons to facilitate easy selection of the preferred language settings (e.g. subset of the adaptive language settings). Once the override request is processed, the system may send a confirmation signal back to the requesting device, indicating that the new settings have been applied. The system may also log this override action to refine future predictions and ensure continuous improvement of the adaptive language model. The network function and / or UE_A or UE_B may store the updated adaptive language settings and / or a preferred set of adaptive language settings and / or adjustments thereof so that these can be applied to subsequent calls. The network function and / or UE_A and / or UE_B may signal (to each other) the availability of (updated) language settings so that they language settings do not need to be (re-)negotiated in another (e.g., a subsequent) communication session.

[0161] In an embodiment that may be combined with other embodiments or used independently, the first device, referred to as UE_A, and / or the second device, referred to as UE_B, and / or a network function in the communication system may provide feedback to the entity performing the adaptive language procedure (e.g., UE_A may provide feedback to the UE_A itself, a network function such as MF / MRF or the remote UE UE_B). This feedback that may be performed by sending a message such as a message request / update may include one or more of the following:

[0162] (1) Timing misalignment: Feedback may indicate instances where there were discrepancies in the synchronization of adaptive language settings, leading to potential communication lags or mismatches in language preferences during sessions.

[0163] (2) Request to repeat the adaptive language procedure with the same or different settings: Such a request may arise if the initial procedure did not yield satisfactory results, prompting a need for re-evaluation using either the same parameters to confirm consistency or altered settings to explore alternative outcomes.

[0164] (3) Request to adapt the adaptive language settings: Devices may request modifications to the current language settings based on evolving user preferences, contextual changes, or feedback indicating that the existing settings are not optimal for effective communication. In an embodiment that may be combined with other embodiments or used independently, the method may involve signaling procedures to gather feedback from the first device, referred to as UE_A, and the second device, referred to as UE_B. The steps may include:

[0165] (1) Initiation of Feedback Request: UE_A and / or UE_B may send a feedback request signal to the communication system. Alternatively, the communication system may initiate the feedback request signal to UE_A and / or UE_B. This request may include details on the recent adaptive language settings used, the session context, and any observed issues or discrepancies.

[0166] (2) Authentication and Verification: Upon receiving the feedback request, the communication system may perform an authentication and verification process to ensure that the devices are authorized to provide feedback.

[0167] (3) Transmission of Feedback Data: UE_A and / or UE_B may transmit the feedback data to the r communication system. This data may cover aspects such as timing misalignment, effectiveness of adaptive language settings, and any requests for adjustments or repetitions of the adaptive language procedure. Conversely, the communication system may send a request to UE_A and / or UE_B to provide specific feedback.

[0168] (4) Analysis and Processing: The communication system may analyze the received feedback to identify any patterns or common issues. This analysis may involve comparing the feedback from multiple sessions and devices to refine the adaptive language model.

[0169] (5) Update and Refinement: Based on the analysis of the feedback, the communication system may update the adaptive language settings and models to enhance future communication sessions. These updates may be securely transmitted back to UE_A and UE_B.

[0170] (6) Confirmation and Logging: After successfully processing the feedback, the communication system may send a confirmation signal back to UE_A and / or UE_B, indicating that the feedback has been received and processed. Alternatively, UE_A and / or UE_B may send a confirmation signal to the communication system. The system may also log the feedback and the actions taken to ensure continuous improvement.

[0171] These signaling steps may be repeated periodically or triggered by specific events such as network reconnections or firmware updates, ensuring that the adaptive language settings remain aligned with user preferences and contextual requirements.

[0172] In an embodiment that may be combined with other embodiments or used independently, the communication request, communication confirmation, communication rejection, notification, or feedback may be given as communication protocol commands, voice commands, or A / V output. The voice commands may include instructions such as "Send feedback," "Confirm communication," "Reject request," or "Notify issue." Additionally, these voice commands may be extracted from the conversation itself. For instance, if a user tells another user, "I do not get it, it is difficult to understand," the system may determine that the content needs to be rephrased or retranslated. The A / V output may involve audio alerts, visual notifications on the device screen, or a combination of both to indicate the status of the communication process or to prompt the user for further actions.

[0173] In one embodiment, the first device, UE_A, and / or the second device, UE_B, within a communication system (e.g. IMS (IP Multimedia Subsystem)), may provide feedback regarding adaptive language processing errors. This feedback protocol may encompass the following:

[0174] (1) Request to Slow Down: Users may request the system to slow down the communication / translation speed, ensuring the conveyed information is comprehensible.

[0175] (2) Request to Repeat: Users may ask for certain parts of the communication to be repeated for better understanding.

[0176] (3) Request to Rephrase: The system may rephrase the content if a user finds it difficult to understand the original phrasing.

[0177] (4) Request for Clarification: Users may seek further clarification on specific points or terms used during communication.

[0178] (5) Adjust Volume or Tone: The system may adjust the volume or tone to suit the user's preferences or hearing capabilities.

[0179] By incorporating these specific feedback requests, the communication system ensures that the adaptive language settings remain aligned with user preferences and contextual requirements, enhancing the overall communication experience.

[0180] In an embodiment that may be combined with other embodiments or used independently, the entity performing the adaptive language procedure may perform multiple procedures including multiple versions of the adaptive language translation in the communication stream so that the receiving device can choose the most suitable one according to its adaptive language settings. This approach offers several advantages, as it allows users to select the most suitable translation according to their needs and it may allow addressing multiple receiving users / UEs / devices. For example, a translation may be provided in advanced Dutch for native speakers and in simplified Dutch for foreigners. The system can signal and negotiate the capability to include multiple versions of the adaptive language translation. Initially, multiple versions of the translation may be computed and communicated to enhance the user experience so that as soon as the data stream is received, the receiving UE can select the preferred one according to his / her adaptive language settings. Once the user on the receiving end (UE) has selected the most appropriate translation, the entity performing the translation can limit future translations to that choice. This ensures that the communication remains efficient and tailored to the user's preferences, further enhancing the effectiveness of the adaptive language model in providing contextually appropriate and personalized interactions.

[0181] In an embodiment that may be combined with other embodiments or used independently, the adaptive language procedure may include the use of an Avatar communication system within a communication system, such as an IMS (IP Multimedia Subsystem) framework as illustrated in Fig. 7. Avatar communication involves the utilization of a virtual representation or avatar that mirrors the user's actions and speech. This system combines the adaptive language model with the avatar to enhance user interaction. The avatar can convey expressions, gestures, and emotions, providing a more immersive and engaging communication experience. The adaptive language model ensures that the avatar's responses are contextually appropriate and personalized to the user's preferences, making the interaction seamless and effective.

[0182] In an embodiment that may be combined with other embodiments or used independently, the adaptive language settings of UE_A and / or UE_B and / or a preferred / adjusted set of adaptive language settings and / or an indication to enable / disable language translation may be stored in and / or retrieved from a data function, such as the Home Subscriber Server (HSS) or the User Data Management (UDM) system (e.g.as part of the user's subscription data), when the communication system refers to the IMS (IP Multimedia Subsystem) and / or a 5G cellular system. This ensures that the settings are synchronized and available regardless of the device or network in use, facilitating real-time adjustments and optimizations based on the user's communication preferences.

[0183] Section: Example procedure for adaptive language

[0184] Next, an exemplary procedure according to some embodiments of the invention invention is presented. This procedure may be illustrated by means of Fig. 7. In this procedure, certain steps and entities are involved, although steps may be performed at different stages, additional steps based on some embodiments in the invention may be introduced. In this exemplary procedure, a data channel may have been established initially between UE_A and UE_B. UE_A may send an initial message requesting adaptive language procedures in a message, e.g., SIP INVITE or re-INVITE or in a reconfiguration message. This message may include an Avatar ID that may contain or specific adaptive language settings. For instance, the Avatar ID may contain metadata including the adaptive language settings so that the requested Avatar uses a specific language. The request may also include whether the procedures should preferably be executed on UE_A and / or network and / or UE_B. This message may be sent to the l / S-CSCF that may send it to IMS / DCSF / XR AS / HSS. This message may include an indication of the adaptive language settings of UE_A. It may also trigger the retrieval of such adaptive language settings, e.g., from the HSS. A function such as XR AS may send a request to the DCSF to request the IMS AS to start an Avatar call with adaptive language support. This may also indicate where such adaptive language procedures should be executed (UE_A and / or network and / or UE_B). A suitable MF / MRF may be selected (e.g., by IMS AS) that may allocated sufficient resources. IMS may notify the DCSF about the successful / failed configuration that may confirm to the XR AS. At this stage, the XR AS may go on with the communication setup, and the IMS AS may send the request message to the remote IMS network where UE_B is located. This request may be sent through the S-CSCF. This message may include, e.g., information about the adaptive language settings of UE_A, the adaptive language settings that are configured in the MR / MRF, where the adaptive language procedures are requested / preferred to be executed, etc. This request message may be, e.g., a re-INVITE message. UE_B and / or the terminating IMS network may return a 200 OK response. This message may include adaptive language settings of UE_B, or a request to retrieve them, e.g., from the HSS. UE_B may have done it directly, or an entity such as IMS AS or DCSF may retrieve them. The network may determine whether inconsistencies between the adaptive language settings are present or with the current configuration of MF / MRF and or UE_A / UE_B to perform the adaptive language procedures. If inconsistencies appear, additional signalling may be required to resolve them, e.g., according to embodiments in the invention. The MR / MRF may be configured with additional adaptive language models (e.g., required by UE_B )or the URL to retrieve them. Additionally or alternatively, the models / URL to perform the adaptive language procedures and / or adaptive language models may be retrieved / distributed / provided to UE_A and / or UE_B. The application data channels between UEs and MR / MRF may be established. The XR AS may send a service media control request to MF / MRF, e.g., through DCSF. This control request may determine control parameters for the adaptive language procedure to be executed in the MR / MRF and / or at the end UEs, UE_A and / or UE_B. In case of network centric rendering, UE_A / UE_B may send metadata through the data channel / audio / video via RTP to the MF / MRF. MF / MRF may perform the adaptive language procedures in combination with the Avatar rendering, and the MF / MRF may send the avatar video stream and / or generated metadata after application of the adaptive language procedure to UE_A and / or UE_B.

[0185] In another exemplary embodiment, the procedure in Fig. 8 (taken from clause 6.25.2.1 of 3GPP TR 23.700-77) is extended with sending, confirming and / or performing adaptive language operation. Sending the language / translation preference could be part of the steps 0 / 1 / 8 / 9 / 11 / 12 / 16 in Fig. 8. The message that includes the list of available adaptive language settings and / or to confirm adaptive language settings / procedure could be part of messages 8, and 9, or 12 to / from UE#2 or step 1, 11, 12 or 16 to / from UE#1, but could also be an additional message exchange between the l / S-CSCF and UE#1 before step 18 (or perhaps a NAS message during registration). The adaptive language procedure could be done as part of step 18 by the MF / MRF, which could operate an adaptive language model which it may fetch / receive from a database or application server (e.g. XR AS) (whereby fetching adaptive language model or settings by the MF / MRF may be combined with step 15), or could be performed by UE#1 or UE#2 whereby steps 15 and / or 18 would not be performed by the MF / MRF but by the UE#1 or UE#2 and steps 16 and 17, as well as steps 19 and 20 would be done directly between the two UEs. Additionally or alternatively, the adaptive language procedure may be performed by an application server (e.g. XR AS), whereby the output of the adaptive language procedure may be aggregated / mixed with A / V media that is being streamed over the data channel (or used instead of the A / V media that is being streamed over the data channel).

[0186] To summarize, it is proposed a method for adaptive language in a communication system wherein the method comprises: sending, by a first device, communication request to initiate a communication with at least a second device, the request including an indication to a network function or the second device wherein the indication comprises an indication to perform adaptive language at the first device, receiving, by the first device, a communication confirmation accepting the communication with one or more second devices, wherein the communication confirmation includes an indication of the first adaptive language settings, at least an indication of the second adaptive language settings of at least the second device and an adaptive language model or model identifier of an adaptive language model or a confirmation to use an adaptive language model pre-configured at the second device to perform the adaptive language procedures, performing, by the first device, a first adaptive language procedure to an incoming data stream from one or more second devices according to the first adaptive language settings and the adaptive language model; and performing, by the first device, a second adaptive language procedure to one or more outgoing data stream to one or more second devices according to the second adaptive language settings and the adaptive language model.

[0187] Section: Authorization in Receiving UE centric IMS Avatar communication

[0188] In IMS-based avatar communication, specifically in a scenario where the rendering is performed by a receiving UE (e.g., UE2), also known as receiving UE-centric rendering mode, specified in AC.11.3.2.2 of TS 23.228 (vl9.2.0), the authorization process for UE2 to access / retrieve / download and utilize the sending UE's (e.g., UE1) avatar representation may introduce critical inefficiencies and / or security issues (e.g., related to UE2 authorization). The multi-entity dependency involving the DC AS, BAR, and MF introduces potential coordination failures, particularly during the authorization validation of UE2's request to download the avatar representation of UE1, which may lead to unauthorized access, denial of legitimate requests, or delays in avatar animation rendering. Such inefficiencies do not only degrade the real-time communication experience but also impact system scalability and performance by increasing signalling overhead and processing delays. Addressing these authorization challenges is essential to ensure secure, efficient, and seamless avatar interaction in multi-user avatar communication scenarios. To that end, it is described the following embodiments which may be combined with the other embodiments or used independently:

[0189] In certain scenarios, a token-based authorization mechanism may be used to:

[0190] • ensure that the avatar representation being requested for download belongs to the sending UE (e.g., UE1) e.g., by verifying the Avatar ID is present in the list of Avatar IDs associated with the sending UE identifier (e.g., IMPU), e.g., by including the UE1 ID and the Avatar ID in the token, or

[0191] • ensure that the network / functional entity requesting the avatar representation (e.g., DC AS or MF) identifier is authorized to do so, e.g., by including its identifier in the token, or

[0192] • ensure that the repository (e.g., BAR) where the Avatar representation is stored is authorized to provide the Avatar representation e.g., by including the identifier of the repository in the token, or

[0193] • ensure that the authorization to access / retrieve / fetch the Avatar representation is timebound e.g., by including an expiration time in the token, or

[0194] • ensure the receiving UE (i.e., UE2) is authorized to request / fetch / retrieve the Avatar representation of UE1 e.g., by including the UE2 identifier (e.g, IMPU) in the token, where the token is signed by UE1 and provided to a functional / network entity and the verification of the token is meant to guarantee the above.

[0195] Still, the above may not be sufficient to provide the required guarantees. For instance, as described in step 2 of clause AC.11.3.2.2 in TS 23.228 (vl9.2.0) and NOTE1 right below, the P2A2P application data channel is established between UE1 / UE2 and DC AS, and UE1 fetches the URL (e.g., from DC AS) associated with the Avatar representation indicated by the requested Avatar ID, and according to step 5 in the same clause, UE2 requests downloading the avatar representation from BAR (e.g., directly through MF, or through MF via DC AS) using the URL (associated with the Avatar representation received from UE1) received from UE1 through the established application channel in step 2, yet it is not clear when the URL associated with the avatar representation and its corresponding avatar ID is provided to UE2, thus, it is an aim of this invention to provide enhanced authorization means in IMS-based avatar communication by means of one or more of the following embodiments: In an embodiment that may be combined with other embodiments or used independently, the associated URL is provided to UE2 by UE1, e.g., in Step 3 when UE1 requests UE2 to perform the avatar animation.

[0196] Additionally or alternatively, the URL is provided to UE2, e.g., in step 4 where UE1 performs avatar animation negotiation with DC AS and UE2, such that the negotiation includes usages of the URL and / or the context in which the URL can be used for the retrieval of an Avatar in addition to the avatar ID, thereby allowing DC AS to associate UE1, UE2, Avatar ID and avatar URL, thereby ensuring DC AS (or another functional entity e.g., MF or BAR) has the mapping between the UE identifiers and avatar ID and avatar URL for subsequent verifications e.g., during avatar download request, so that authorization can be performed.

[0197] In another embodiment that may be combined with other embodiments or used independently, the token to be used to provide the guarantees described in the scenario above, may further include the URL (complete or a fingerprint of it) associated with the avatar representation of UE1, which may also be linked to the avatar ID. This provides stronger guarantees for the URL to not be misused to fetch avatar representation(s) of a UE.

[0198] In another embodiment that may be combined with other embodiments or used independently, the URL allowing the download of the Avatar representation may implicitly be associated with the Avatar ID that identifies the Avatar representation selected by the sending UE . For instance, the URL may be of the format URL / AvatarJD, or include a parameter e.g., a GET parameter, including the Avatar ID e.g., URL?&AvatarlD=Avatar_ID, or the like (e.g., POST parameter), thereby allowing a network entity (e.g., MF, DC AS, and / or BAR) to verify the association between the received Avatar ID and URL.

[0199] In another embodiment that may be combined with other embodiments or used independently, the URL may provide access to different versions of an Avatar ID depending on the authorization level of a UE. This can be useful, e.g., in multi-user / multi-UE Avatar communication wherein a single token may be available (Avatar ID and UE1), a functional entity (e.g., MF or BAR) may know the different authorization levels of different receiving UEs, and a single URL may be preferred. Different receiving UEs may provide the same URL, but depending on the determined authorization level, a different Avatar version may be determined and / or provided. For instance, if 3 different levels of authorization / a, / b, and / c are feasible, the URLs of the Avatar that is authorized to be retrieved may be:

[0200] URL / a

[0201] URL / b URL / c

[0202] In other words, the final URL may be obtained as a function (e.g., concatenation) of a base URL and the authorization level.

[0203] In another embodiment that may be combined with other embodiments or used independently, the token which may include the URL of the avatar representation of UE1, the Avatar ID associated with the avatar representation referenced by the URL, UE1 ID, and UE2 ID, may be provided by UE1 to UE2 in, e.g., step 3, or step 4, as described in previous embodiments.

[0204] In another embodiment that may be combined with other embodiments or used independently, when fetching the URL from DC AS, the UE1 may indicate to DC AS conditions associated with invalidation of the URL e.g., number of times said URL may be used, e.g., once or X number of times, indicate the identifier of the receiving UE (or UEs) allowed to use said URL, duration of time for which the URL may remain valid, etc.

[0205] Additionally or alternatively, the URL and / or token may be cross invalidated, e.g., if URL is to be used only one time, once it is used, it is invalidated together with the token with which it is associated, e.g., if the token is invalidated due to time expiry, URL is also invalidated at the same time.

[0206] In another embodiment that may be combined with other embodiments or used independently, in step 2 of the aforementioned procedure, where the DCSF instructs the MF to establish a connection to BAR or DC AS, the DCSF may indicate to the UE whether the connection link between MF and BAR is direct, or indirect (e.g., through DC AS), such that UE1 may determine whether to include the UE2 ID in the token, e.g., when MF has a direct link to BAR, and upon receiving the Avatar download request from UE2, which includes UE2 ID, MF or BAR perform the token signature verification, and if successful, and UE2 in the token matches the UE2 ID in the token, it can be ensured that UE2 is authorized to download the avatar ID. Whereas, if the connection link between MF and BAR is through DC AS, UE1 may not necessarily add UE2 ID in the token, as DC AS already knows the Application data channel is established between UE1 and UE2 and UE2 was provided with URL and Avatar ID by UE1, thereby implicitly authorizing it to retrieve its avatar representation associated with the URL / Avatar ID shared with it.

[0207] Additionally or alternatively, and to provide stronger guarantees for UE2 authorization by UE1 to retrieve the Avatar representation, UE2 ID in the Avatar representation download request may be cross-checked with the UE2 ID in the token by the DC AS upon receiving the token from UE2, whereas BAR provides assurance of UE2 ID validity solely by verifying the token signature. In another embodiment that may be combined with other embodiments or used independently, in a multi-user / UE avatar communication session, the token may include a list of receiving UE identifiers, which may be used to ensure that UE1 avatar representation is authorized for retrieval only from the receiving UEs in said list.

[0208] Additionally or alternatively, a single URL may be used in the token, and shared with the different receiving UEs to use for avatar representation retrieval.

[0209] Additionally or alternatively, the number of receiving UEs, may be the threshold for URL usage, such that the URL and / or token are invalidated once the URL is used N times, where the list of receiving UE IDs includes N UE identifiers.

[0210] Additionally or alternatively, a network entity (e.g., BAR, DC AS,...) may be aware of the UE identities involved in the multi-user / UE avatar communication and may be aware about which users / UEs allow disclosing which Avatar IDs to which users / UEs. A receiving UE may present the authorization token including the sending UE ID and avatar ID, and the network entity may grant / allow access to the Avatar if the receiving UE is authorized.

[0211] In general, it is proposed a method that can be implemented in a sending User Equipment (UE) for authorizing the retrieval of an avatar representation by a receiving UE in an IP Multimedia Subsystem (IMS)-based communication session, the method comprising one or more of: generating a token that includes for example one or more of: an identifier of the sending UE, an identifier of the receiving UE, an identifier of the avatar representation, a URL associated with the avatar representation, a validity condition for the token, the validity condition may include in some variants at least one of a time constraint, a usage limit, or a list of authorized receiving UE identifiers; signing the token to ensure its authenticity and integrity; transmitting the token to a designated functional entity, wherein the functional entity is one of a Distributed Content Application Server (DC AS), a Media Function (MF), or a Base Avatar Repository (BAR); providing the receiving UE with the URL associated with the avatar representation, wherein the URL is provided during one of: a request by the sending UE for the receiving UE to perform avatar animation, or an avatar animation negotiation involving the sending UE, the receiving UE, and the

[0212] DC AS; indicating to the DC AS conditions for invalidating the URL, the conditions including for example at least one of: a maximum number of URL usages, a validity duration, or identifiers of receiving UEs authorized to use the URL; and ensuring that the URL and the token are cross-invalidated based on the satisfaction of the validity condition.

[0213] In general, it is proposed a method in a receiving User Equipment (UE) for retrieving an avatar representation of a sending UE in an IP Multimedia Subsystem (IMS)-based communication session, the method comprising one or more of: receiving, from the sending UE, a token that includes one or more of: an identifier of the sending UE, an identifier of the receiving UE, an identifier of the avatar representation, a URL associated with the avatar representation, a validity condition for the token, the validity condition including at least one of a time constraint, a usage limit, or a list of authorized receiving UE identifiers; receiving, from the sending UE, the URL associated with the avatar representation; transmitting a request to a functional entity, wherein the request includes the token and the URL, the functional entity being one of a DC AS, a Media Function (MF), or a BAR; ensuring that the token is verified by the functional entity by: validating the token signature, verifying the identifier of the receiving UE in the token matches the identifier of the requesting UE, and confirming that the token validity condition is satisfied; retrieving the avatar representation from the functional entity using the URL upon successful token verification; and rendering the avatar representation locally on the receiving UE for avatar animation.

[0214] Wireless local area network technologies 2024P00529WQ

[0215] Wi-Fi is a wireless technology that allows devices to connect to the Internet or to each other without using cables. Wi-Fi is based on radio waves that are transmitted and received by a device called a wireless access point (AP). The AP acts as a hub that connects Wi-Fi enabled devices, such as laptops, smartphones, tablets, smart TVs, etc., to a wired network, such as a local area network (LAN) or the Internet.

[0216] The term Wi-Fi is a trademark of the Wi-Fi Alliance, an industry association that certifies products that comply with the IEEE 802.11 standards for wireless local area networks (WLANs). These standards define the physical and data link layers of the communication protocol, such as the frequency bands, modulation schemes, encryption methods, authentication mechanisms, and data rates used by Wi-Fi devices. The most common Wi-Fi standards are 802.11a, 802.11b, 802.11g, 802. lln, 802.11ac, and 802.11ax, which operate in different frequency bands (2.4 GHz, 5 GHz, or both) and offer different levels of performance and compatibility.

[0217] To use Wi-Fi, a device needs to have a wireless network interface card (NIC) that can send and receive radio signals. The NIC scans the available wireless channels and detects the presence of nearby APs. The device then selects an AP to connect to, based on factors such as signal strength, security settings, and network name (SSID). The device and the AP exchange information, such as the MAC address, IP address, encryption key, and password, to establish a connection. This process is called association. After the connection is established, the device can communicate with the AP and other devices on the same network, or access the Internet through the AP.

[0218] IEEE 802. lln (Wi-Fi 4) provided new features such as MIMO and frame aggregation to increase throughput. IEEE 802.11ac (Wi-Fi 5) introduced wider bandwidth and MU-MIMO. IEEE 802.11 ax (WIFI-6) included OFDMA and BSS color or spatial reuse to use spectrum resources more efficiently. IEEE 802.11 ah introduced target wake time (TWT) to support low power loT applications by allowing STAs to go into sleep when not in a wake period after negotiation with AP. IEEE 802.11be (Wi-Fi 7) aims at improving throughput and latency operating in unlicensed bands between 1GHz and 7.125 GHz. Wi-Fi 7. Increases bandwidths up to 320 MHz, 4096 QAM modulation, and supporting up to 16 spatial streams in MU-MIMO with an improved sounding procedure. Wi-FI 7 also enables multiple resource units to be assigned to a single device. Furthermore, it includes an enhanced preamble with a universal SIG filed indicating the PHY version. It also extends the negotiated ack buffer size to 1024 bits.lt also enables multilink operation (MLO) enabling multiple links between a station and an access point, for instance an AP can have two radios 2.4 and 5 GHz and use both of them for simultaneous transmission and / or reception with a multi-link capable device (MLD) capable station. Wi-Fi 7 also includes a restricted TWT providing predictable latency by assigning STAs to different rTWT types and making sure that other STAs do not transmit if they do not belong to a given rTWT type. Wi-Fi 7 also include multi-AP coordination performing, e.g., coordinated transmission, beamforming, or joint transmission.

[0219] For instance, in references to Fig. 1, devices 100, 101 and 102 can be Wi-FI access points and device 106 can be a wireless station. Station 106 and access point 101 are MLD and communicate with two links 126. Device 102 is a cellular capable residential gateway.

[0220] Cellular technologies

[0221] A cellular system is a wireless communication system that consists of three main components: user equipment (UE), radio access network (RAN), and core network (CN). These components work together to provide voice and data services to mobile users over a large geographic area.

[0222] User equipment (UE) is the device that a user uses to access the cellular system, such as a smartphone, a tablet, a laptop, loT device, or a wearable device. A UE typically may contain the following components:

[0223] - A universal integrated circuit card (UICC), which stores the user's identification and authentication information, such as the subscription permanent identifier (SUPI) or credentials.

[0224] - A transceiver, which converts the digital signals from the processor into analog signals for transmission and reception over the air interface. The transceiver also performs modulation, demodulation, coding, decoding, and other signal processing functions.

[0225] - A processor, which controls the operation of the UE and executes the applications and services that the user requests. The processor also communicates with the RAN and the CN using various protocols.

[0226] - A display, which shows the user the information and feedback from the UE, such as the signal strength, the battery level, the call status, the messages, the contacts, the menu, etc.

[0227] - A microphone and a speaker, which enable the user to make and receive voice calls, as well as use other audio features, such as voice mail, voice recognition, etc.

[0228] - A keyboard and / or a touch screen, which allow the user to enter and select commands, text, numbers, etc.

[0229] - A camera and / or a video recorder, which enable the user to capture and send images and videos, as well as use other multimedia features, such as video calling, video streaming, etc.

[0230] - A memory, which stores the data and programs that the user needs, such as the phone book, the messages, the photos, the videos, the applications, etc as well as a computer program to perform the operations of the RAN and CN protocols.

[0231] - A battery, which provides the power supply for the UE. Fig. 2 provides a schematic representation of a UE and its components, e.g., UICC (201), processor (202), transceiver (203), memory (204), input devices (205) such as camera, microphone, etc and output devices (206) such as display, speaker, etc.

[0232] A UE access the cellular network via the radio access network, as described below. Certain UEs may communicate with each other by using device-to-device communication, also known as sidelink communication using the PC5 interface that may rely on physical sidelink (PS) broadcast channel, PS shared channel, PS control, etc.

[0233] A UE may receive a configuration by means of different procedures:

[0234] Downlink control information (DCI) is a type of control information that is sent from the BS to the UE on the physical downlink control channel (PDCCH). DCI contains various parameters that instruct the UE how / when to decode and transmit data on the physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH), such as the resource allocation, the modulation and coding scheme. The UE needs to monitor the PDCCH in each subframe to detect and decode the DCI that is addressed to it.

[0235] Uplink control information (UCI) is a type of control information that is sent from the UE to the BS on the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). UCI contains various feedback signals that inform the BS about the status and quality of the downlink transmission, such as the HARQ. acknowledgments (ACKs), the channel state information (CSI), and the scheduling requests (SRs). The UE needs to encode and transmit the UCI according to the configuration and timing indicated by the BS.

[0236] Sidelink control information (SCI) is a type of control information that is sent from the UE to another UE on the physical sidelink control channel (PSCCH) in device-to-device (D2D) communication scenarios. The main functions of SCI include resource allocation, synchronization, channel quality reporting, .

[0237] Medium access control (MAC) control element (MAC CE) is a type of control information that is sent from the BS to the UE or vice versa on the MAC layer. MAC CE contains various commands or indications that regulate the MAC layer functions, such as the buffer status report (BSR), the timing advance command (TAC), the discontinuous reception (DRX) command, etc. The UE needs to process the MAC CE according to the MAC protocol and the configuration provided by the BS.

[0238] Radio resource control (RRC) command is a type of control information that is exchanged between the BS and the UE on the RRC layer. RRC Command contains various messages that modify / configure RRC parameters and / or initiate, modify, or release the RRC connection or the radio bearers between the UE and the BS, such as the RRC connection setup, the RRC connection reconfiguration, the RRC connection release, the security mode command, the mobility from E-UTRA command, the handover from E-UTRA preparation request, etc. The UE needs to respond to the RRC Command according to the RRC protocol and the configuration provided by the BS.

[0239] Non-access stratum (NAS) messages are used for signalling between UE and core network (CN) on the non-access stratum (NAS) layer. NAS messages enable functionality such as registration, session establishment, security, and mobility management. The UE needs to respond to the NAS Command according to the NAS protocol and the configuration provided by the CN.

[0240] UE parameter update (UPU) is a procedure between the UE and the home network that enables the home network to update configuration parameters in mobile phones and / or USIM using tthe UDM control plane procedure (TS 23.502). The UE can receive Parameters Update Data from the UDM after the UE has registered in the 5G network.

[0241] Steering of Roaming (SoR) enables the home network to guide the user equipment (UE) when registering on a visited network. For detailed information about the interfaces and registration in the 5G System, refer to 3GPP TS.23.501 and 3GPP TS 24.501. The 5G CP-SOR is activated during or after registration to update the UE's "Operator Controlled PLMN Selector with Access Technology" list via secure NAS messages, as directed by the home PLMN based on specific operator policies, such as preferred networks or UE location.

[0242] UE configuration update (UCU) is used to update configuration parameters as per TS 23.502 that may include Access and Mobility Management related parameters decided and provided by the AMF, UE Policy provided by the PCF. When AMF wants to change the UE configuration for access and mobility management related parameters the AMF initiates the procedure defined in clause 4.2.4.2. When the PCF wants to change or provide new UE Policies in the UE, the PCF initiates the procedure defined in clause 4.2.4.3. If the UE Configuration Update procedure requires the UE to initiate a Registration procedure, the AMF indicates this to the UE explicitly. The procedure in clause 4.2.4.2 may be triggered also when the AAA Server that performed Network Slice-Specific Authentication and Authorization for an S-NSSAI revokes the authorization.

[0243] Radio access network (RAN) is the part of the cellular system that connects the UEs to the CN via the air interface. The RAN consists of base stations (BSs). A base station (BS) is a fixed or mobile transceiver that covers a certain geographic area, called a cell. In 5G, a BS is also called a gNB (next generation node B). A BS can serve multiple UEs simultaneously within its cell, by using different frequencies, time slots, codes, or beams. A BS also performs functions such as power control, handover control, channel allocation, interference management, etc. A base station can be divided into two units: a central unit (CU) and a distributed unit (DU). The CU performs the higher layer functions, such as RLC, PDCP, RRC, etc. The DU performs the lower layer functions, such as PHY and MAC. The CU and the DU can be co-located or separated, depending on the network architecture and deployment. In cellular systems, a base station may be denoted, based on context, as a cell, or gNB.

[0244] The cell may also refer to the coverage area of a base station. A BS may have different coverage areas such as a macro cell (e.g. several kilometres wide), a pico cell (e.g., for a given location such as a stadium) or a femto cell for a small location (e.g., a home or part of it).

[0245] A base station may communicate with the core network. Since there can be base stations for different cellular systems, different interfaces are required. For instance, a base station, eNB, in a 4G Long Term Evolution (LTE) system (also known as Evolved Universal Mobile Telecommunications Systems (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the 4G CN known as EPC through the corresponding interface. For instance, a base station, gNB, in a 5G system (i.e., 5G New Radio or Next Generation RAN) may communicate with the 5GC through a different interface. 4G and 5G base stations may communicate with each other directly or through their corresponding core networks.

[0246] The main protocols used between the UEs and the RAN are:

[0247] - The physical layer (PHY), which defines the characteristics of the air interface, such as the frequency bands, the modulation schemes, the coding rates, the frame structure, the synchronization, etc.

[0248] - The medium access control (MAC) layer, which regulates the access of the UEs to the shared radio channel, by using techniques such as orthogonal frequency division multiple access (OFDMA), time division duplex (TDD), frequency division duplex (FDD), etc.

[0249] - The radio link control (RLC) layer, which provides reliable data transmission over the radio channel, by using techniques such as segmentation, reassembly, error detection, error correction, retransmission, etc.

[0250] - The packet data convergence protocol (PDCP) layer, which compresses and decompresses the headers of the data packets, encrypts and decrypts the data, and performs data integrity protection.

[0251] - The radio resource control (RRC) layer, which establishes, maintains, and releases the radio bearers between the UEs and the RAN, as well as exchanges the signaling messages for functions such as connection setup, handover, measurement reporting, security activation, etc.

[0252] A transmission / reception communication unit or transceiver may be used by BS and UE to transmit / receive data. Control data may be required for a physical broadcast channel, physical downlink control channel, etc. Data may be for the physical downlink shared channel. 2024P00529WQ

[0253] Data may be encoded by the UE and / or BS to obtain data symbols and / or control symbols that may be exchanged over the wireless interface. The conversion from digital data into analog symbols may be done by the transmission / reception communication unit

[0254] A medium access control control-element (MAC-CE) is a MAC layer communication element that is used to control the communication between wireless devices. A MAC-CE may be exchanged in a shared channel, e.g., the physical downlink / uplink / sidelink shared channel.

[0255] The communication between a UE and a base station or the communication between UEs (when sidelink is used) may involve the exchange of reference signals. Reference signals may include primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS). Core network (CN) is the part of the cellular system that connects the RAN to other networks, such as the Internet, or other cellular systems. The CN consists of two main (control / user) domains. The control domain is responsible for providing signalling and control functions for the UEs, such as authentication, authorization, mobility management, session management, etc. The control plane consists of several network functions (NFs), such as the access and mobility management function (AMF), the session management function (SMF), the unified data management (UDM), the policy control function (PCF), the network exposure function (NEF), and the authentication server function (AUSF). The access and mobility management function (AMF) is a NF that handles the registration, deregistration, connection management, and mobility management for the UEs. The session management function (SMF) is a NF that handles the establishment, modification, and release of the sessions for the UEs. The SMF also communicates with the user plane devices to perform functions such as IP address allocation, tunneling, QoS, etc. The unified data management (UDM) is a NF that stores and manages the user data, such as the SUPI, the service profile, the subscription status, etc. The policy control function (PCF) is a NF that provides the policy rules and charging information for the UEs, such as the access type, the service level, the data rate, the quota, etc. The network exposure function (NEF) is a NF that exposes the network capabilities and services to external applications and devices, such as the IMS, the Internet of Things (loT), etc. The authentication server function (AUSF) is a NF that performs the primary authentication with the by using credentials and the SUPI. The user domain is responsible for providing data and multimedia services to the UEs, by using packets and IP addresses. The user plane consists of two main functions: the user plane function (UPF) and the data network (DN). The user plane function (UPF) is a device that forwards the data packets between the UEs and the DNs, as well as performs functions such as tunneling, firewall, QoS, charging, etc. The data network (DN) is a network that provides access to the services and applications that the UEs request, such as the Internet, the IMS, etc. 2024P00529WQ

[0256] A residential gateway (RG) is a device that connects a home network to an external network, such as the Internet or a cellular system. An RG typically provides functions such as routing, switching, firewall, NAT, DHCP, DNS, VPN, etc. An RG can also support various types of interfaces, such as Ethernet, Wi-Fi, Bluetooth, USB, etc. A cellular-capable RG is an RG that has a cellular interface, such as a UICC slot, a cellular modem, or an antenna, that enables it to access the cellular system as a backup or an alternative to the wired or wireless broadband connection. A cellular-capable RG can provide benefits such as: (1) Enhanced reliability, by switching to the cellular connection in case of a failure or a degradation of the broadband connection; (2) Increased bandwidth, by aggregating the cellular connection and the broadband connection to achieve higher data rates or QoS.

[0257] A multi-SIM subscription is a subscription that allows a user to have multiple SIMs (or eSIMs) that are linked to the same account and service profile. A user can use the multi-SIM subscription to access the cellular system from different devices, such as a smartphone, a tablet, a laptop, or a wearable device, without having to switch the SIM card or the device.

[0258] In reference to Fig. 1, devices 100, 102, and 128 can play the role of UEs. Device 102 is part of a cellular-capable RG providing connectivity to a home network 129 e.g., by means of a local area network and / or wireless local area network. Device 102 is served by base station 104.

[0259] The RAN 127 comprises base station 103 and serves UE 128. UE 128 may also be a UE to Network relay given access to remote UE 136 that is out of coverage of base station 103. UEs 134 and 136 also communicate with each other via a UE-to-UE relay 135. Within the RAN, the range of base station 103 is extended via smart repeater 137 and reflective intelligent surface (RIS) 138. Smart repeater 137 and RIS 138 give access to UE 142.

[0260] The RAN 143 includes base station 104 tand serves as wireless access infrastructure for the home network. Base station 104 also serves a mobile access device and / or UE as a UAV 139. UAV 139 may provide connectivity to remote UE 136.

[0261] Furthermore, a satellite gateway 141 is shown that connects to satellite 140 and may provide connectivity services to remote UE 136 or UE 100.

[0262] In Fig. 1, the 5G core network 133 may include one or more an AMF 121, SMF 123, UPF 122, AUSF 124, UDM 125, PCF 131, NEF 132 and allows the connection to a data network 130.

[0263] In Fig. 1, a second core network 142, e.g., a legacy core network as a 4G core network, is also shown that may interface with the 5G core network 133, interface with base stations denoted eNB in 4G, and provide a connection to the data network 130. The legacy 4G core network is denoted EPC and may include one or more mobility management entities (MME), a serving gateway, a multimedia broadcast multicast service gateway, a broadcast multicast service center, a packet data network gateway, etc. The mobility management entity may handle the signalling between UE and the 4G CN and may interact with the home subscriber server (HSS) in charge of the storage and management of subscriber data and secrets. The MME may provide connection management, similar to the AMF in 5G. The serving gateway may be used to exchange user internet protocol messages whereby the serving gateway may interact with the packet data network gateway that is connected to IP services. Multiple protocols in 4G and 5G have similar features. For example, the 5G network registration and 4G attach registration message are initially sent by the UE to establish a connection between the UE and the CN, which involves sending an initial request from the UE with its identity and capabilities, receiving an authentication request from the CN with a challenge, sending an authentication response from the UE with a response, receiving an authentication result from the CN with an indication of success or failure, and sending a security mode command from the CN with the selected security algorithms. As a result of this connection establishment procedure, NAS and AS keys are derived from the K_AMF (5G) and K_ASME (4G) where K_AMF is managed by the AMF and K_ASME is managed by the MME. A UE may connect to a serving network or serving Public Land Mobile Network (PLMN). A UE may have a subscription with a home PLMN, and during the registration procedure, the (AMF of the) serving PLMN may forward the registration request to the (AUSF of the) home PLMN that may perform an initial authentication procedure between home PLMN and UE. If the authentication procedure is successful, keys are derived and the home PLMN may share derived credentials with the serving PLMN, including K_SEAF, that may be used to derive K_AMF, from which NAS keys and AS keys are derived. The registration request sent by the UE includes an identifier that can be used by the home PLMN to identify the UE. To prevent privacy vulnerabilities, the long-term subscriber's identifier known as Subscriber Permanent Identifier (SUPI) may not be exchanged in the clear, but instead, either a Subscription Concealed Identifier (SUCI) or a pseudonym known as GUTI are exchanged with the AMF of the serving PLMN. The AMF of the PLMN may then forward the SUCI to the home PLMN so that the home PLMN decrypts / verifies it.

[0264] Fig. 1 depicts satellite 140 providing access to one or more UEs. Satellite access can be performed by means of non-terrestrial devices at different altitudes such as Low Earth Orbit (LEO), Medium Earth Orbit (MEO) or Geosynchronous Equatorial Orbit (GEO) satellites. Other types of nonterrestrial devices may include high-altitude platform station (HAPS) or unmanned aerial vehicle (UAVs) that may comprise a base station. Fig. 3 illustrates different elements including a GEO satellite 302, a MEO satellite 303, a LEO satellites 304 and 304', a UAV 305, all of them potential non-terrestrial mobile access devices giving coverage to wireless device (e.g., a UE) 301. GEO satellite 302 remains static over a given earth position while MEO and LEO satellites move. MEO satellites 303 have a slower moving vector 306 in relation to the earth compared with LEO satellites 304 / 304' that have a faster moving vector 307 / 307'. A non-terrestrial gateway 308 is included that provides connectivity to the 2024P00529WQ mobile access device via a feeder link 310. A mobile access device provides service to the wireless device via a service link 311. Two mobile access devices in the same orbit may communicate with each other via an intra-orbit-satellite link 312 while two mobile access devices in different orbits may communicate with each other via an inter-orbit-satellite link 313. Fig. 3 finally also includes a terrestrial access device 309 that may also provide connectivity to wireless device 301. The terrestrial access device 309, the wireless device 301, and non-terrestrial gateway are on the earth surface 314.

[0265] A UE in a cellular system performs an initial random-access procedure to connect an access device. The 5G random access procedure is illustrated by means of Fig. 4 wherein 401 represents a user equipment and 402 represents an access device. The access device distributes signals 402. Signals 402 can be distributed periodically or on demand. Signals 402 may comprise the

[0266] Master Information Block (MIB) transmitted together with / in the physical broadcast channel (PBCH) and the synchronization signals. The MIB comprises:

[0267] MIB ::= SEQUENCE { system FrameNumber BIT STRING (SIZE (6)), subCarrierSpacingCommon ENUMERATED {scsl5or60, scs30orl20}, ssb-SubcarrierOffset INTEGER (0..15), dmrs-TypeA-Position ENUMERATED {pos2, pos3}, pdcch-ConfigSIBl INTEGER (0..255), cellBarred ENUMERATED {barred, notBarred}, intra Freq Reselection ENUMERATED {allowed, notAllowed}, spare BIT STRING (SIZE (1))

[0268] MIB and PBCH are transmitted as part of a Synchronization Signal Block, and the access device may transmit multiple SSBs through different beams, allowing the user equipment to determine the preferred beam, and once the preferred beam is obtained, retrieve the MIB, and use the information in the MIB to attempt to retrieve System Information Block 1 (SIB1) that may also be distributed periodically. The UE can the use the information in SIB1 to perform the random-access procedure selecting a preamble to indicate its intention to access the cell by means of message 404, e.g., preamble transmission. This message may use a random-access radio network temporary identifier (RA-RNTI). Upon reception of message 404, access device 402 replies with message 405, e.g., a random access response. This message may include a time advance field to adapt the transmission timing, a value matching the preamble used by wireless device 401, and a grant (communication resources) for the wireless device. The access device also assigns a temporary cell radio network temporary identifier (TC-RNTI). Prior to this message 405, the access device may send a PDCCH DCI message assigning 2024P00529WQ resources (a communication grant). This message may be addressed using the RA-RNTL Upon reception of message 405, wireless device uses the initial grant received in the previous message and the RA-RNTI to transmit a subsequent message 406, e.g, an RRCSetupRequest or PHY layer. This message may include a Contention Resolution Identifier (CRI). This message may be sent in the PUSCH. As a response, access device replies with message 407, e.g., RRCSetup, that includes / repeats the received CRI confirming that the access device has identified the access device. This message includes a Cell RNTI (C-RNTI). Next, wireless device replies with message 408, e.g., an RRCSetupComplete that includes the RegistrationRequest message, and UE capabilities. TODO

[0269] MIB and PBCH are transmitted as part of a Synchronization Signal Block, and the access device may transmit multiple SSBs through different beams. Multiple SSBs transmitted through multiple beams form an SSB burst. The multiple SSBs in an SSB burst are transmitted sequentially in the first part of a frame. SSB bursts are transmitted periodically, typically every 20 ms, or more.

[0270] Fig. 5 schematically illustrates an access device 500 transmitting four beams, each of them transmitting an SSB, namely 501, 502, 503, and 504. A wireless device 505 can measure the signal strength, i.e., RSRP (Reference Signal Received Power), of the beams. This is illustrated by means of the graph in Fig. 5 where 501', 502', 503', and 504' represent the RSRP of beams 501, 502, 503, and 504, respectively, as measured by wireless device 505. Wireless device 505 can use this information to determine which one of the beams is the preferred beam for further communication, e.g., to perform the random access procedure.

[0271] Fig. 6 further schematically illustrates SSB bursts transmitted periodically. In this case, each SSB burst comprises four SSBs transmitted in the first part / half of every second frame. In this figure, frames are denoted as f, f+1, f+2, f+3,...A frame has a typical duration of 10 ms.

[0272] A wireless system may be used to transport data belonging to different types of applications such as Machine Type Communication (MTC), Critical Machine Type Communication (CMTC), Enhanced Mobile Broadband (EMB), or Fixed Wireless Access (FWA). MTC (e.g., smart meters, tracking,...) requires low bandwidth and non-latency critical, CMTC (e.g., industrial applications) has strict throughput, latency, and availability needs, EMB (VR / AR, 4K UDH, ...) and FWA (e.g., in the home) require high data rate, with low latency, and low end-to-end response time. In wireless network such as 5G the Quality of Service has to accommodate different applications such as EMB, MTC, ultrareliable low latency communications. QoS is influenced by the entities involved in the communication, UE, RAN, UPF, and DN. Data exchanges between UE and DN are mapped to QoS flows, and each QoS flow is mapped to a 5G QoS Identifier (5QI) in TS 23.501 (Table 5.7.4-1) that describes resource types, 2024P00529WQ priority, packet delay budget, packet error rate, maximum data burst volume. Network is configured to configure RAN and core network interfaces to achieve the requirements of a 5QL QoS is applied to a data stream from the wireless physical layer to the core network. Between RAN and UPF, QoS is applied in terms of a QoS flow. QoS in the RAN is managed by means of Data Radio Bearers (DRB). A QoS flow on core network side is created by means of a PDU session establishment accept. The mapping between a QoS flow and a DRM is done by means of SDAP configuration in an RRC message (RRCSetup or RRCReconfiguration) The indication or identifier that connects the whole QoS pipe is called QoS flow identifier. Downlink traffic requires mapping IP messages and the QoS pipe, and this is done by the UPF. For each IP message or packet, the UPF checks (by means of a packet QoS assignment / detection rule) the packet information (source / destination / protocol / type of service / ...) and directs the IP packet to a QoS flow. The packet QoS assignment / detection rule is provided by SMF interacting with PCF. In the uplink, the UE performs a similar task by applying QoS rules provided in NAS messages (e.g., PDU session establishment) by the SMF or are pre-configured / derived by the UE.

[0273] Discontinuous reception (DRX) in cellular networks such as 5G is in two types, Idle mode DRX and Connected mode DRX. In Idle mode DRX, the UE wakes up to monitor for paging messages. If no paging message is detected, it sleeps further. In Connected DRX mode, the UE enters in sleep mode periodically and during the sleep period the UE is not required to monitor the Physical Download Control Channel. The access device configures the UE device with C-DRX parameters. Connected DRX approach reduces energy consumption of the device because it does not require monitoring the PDCCH periodically and it also reduces the transmissions of CSI or SRS signals, that also has a positive effect in the network / access devices load. There are two types of DRX cycles, long and short. A long DRX cycle consists of an on period and an off period. The on duration is in terms of milliseconds. The long DRC cycle may be configured or the long DRX cycle and short DRX cycles may be configured. The access device can configure the time (drx-onDurationTimer) during which the UE is awake and goes back to sleep if there is no PDCCH received. The access device can also configure a given drx-LongCycleStartOffiset to start to awake period at a subframe boundary and / or drx-SlotOffset relative to the subframe boundary. If there is activity in an awake period, the UE may remain awake some more time determined by the drx-lnactivityTimer. Furthermore, the access device can configure long DRX cycle together with additional DRX cycle which is shorter than long DRX cycle. Configurable parameters include the drx-ShortCycle (duration of the short cycle) and drx-ShortCycleTImer that determines how many short cycles before the device should apply.

[0274] Data scheduling in a cellular network such as a 5G cellular network may be performed by means of a scheduler wherein the scheduler takes as input information such as measurements of 2024P00529WQ

[0275] UE / network, buffer status report, QoS requirements, associated radio bearers, or a scheduling request. In the downlink, data scheduling may be performed by means of dynamic scheduling and semi persistent scheduling (SPS). In dynamic scheduling, every data exchange in the Physical Downlink Shared Channel (PDSCH) is scheduled by means of a downlink control information (DCI) message in the Physical Downlink Control Channel (PDCCH). In SPS, the scheduling is done by means of an RRC message. In the uplink, scheduling can be performed by means of dynamic scheduling and configured scheduling (CS). In dynamic scheduling each Physical Uplink Shared Channel (PUSCH) is scheduled over DCI. In CS, the PUSCH transmission is scheduled via RRC message. Furthermore, a Scheduling Request message may be sent over the PUCCH (Physical Uplink Control Channel) or in an Uplink Control Information (UCI) in the PUSCH (Physical Uplink Shared Channel). An SR may be sent by a UE device when it has data to transmit. Upon reception, the access device can allocate resources (Uplink Grant by means of the Physical Downlink Control Channel. Upon resource allocation, the UE device can transmit data in the Physical Uplink Shared Channel.

[0276] Furthermore, this invention can be applied to various types of UEs or terminal devices, such as mobile phone, vital signs monitoring / telemetry devices, smartwatches, detectors, vehicles (for vehicle-to-vehicle (V2V) communication or more general vehicle-to-everything (V2X) communication), V2X devices, Internet of Things (loT) hubs, loT devices, including low-power medical sensors for health monitoring, medical (emergency) diagnosis and treatment devices, for hospital use or first-responder use, virtual reality (VR) headsets, etc.

[0277] Other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the disclosure and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude a plurality. A single processor or other unit may fulfil the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. The foregoing de-scription details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in the text, the invention may be practiced in many ways, and is therefore not limited to the embodiments disclosed. It should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to include any specific characteristics of the features or aspects of the invention with which that terminology is associated. Additionally, the expression "at least one of A, B, and C" is to be understood as disjunctive, i.e., as "A and / or B and / or C". The same applies to the expressions "A or B" and "at least one of A or B", i.e., they may indicate all possible combinations of the listed items.

[0278] A single unit or device may fulfil the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

[0279] The described operations like those indicated in the above embodiments may be implemented as program code means of a computer program and / or as dedicated hardware of the related network device or function, respectively. The computer program may be stored and / or distributed on a suitable medium, such as an optical storage medium or a solid-state medium, supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems.

Claims

522024P00529WOClaims1. A method performed by a sending wireless device (e.g. a UE) in an avatar communication session, such as a IP Multimedia Subsystem (IMS) avatar communication session, in a receiving wireless devicecentric rendering mode, comprising: selecting an Avatar Identifier (Avatar ID) for an avatar representation associated with the sending UE; generating, by the sending wireless device, an authorization token that includes:(i) the Avatar ID,(ii) a sending wireless device identifier of the sending wireless device,(iii) a receiving wireless device identifier of a receiving wireless device,(vi) an expiration time; signing the authorization token, e.g. digitally signing, to obtain a signed authorization token; and transmitting, via a data channel between the sending wireless device and the receiving wireless device, the signed authorization token together with an address, such as a URL, associated with the selected Avatar ID to enable the receiving wireless device to downloading of the avatar representation associated with the sending wireless device.

2. The method of claim 1, wherein the data channel is an established application data channel.

3. The method of claim 1, wherein the authorization token comprises the address, or part of the address or an indication of the address.

4. A sending wireless device, such as a UE, comprising one or more processors, a memory storing instructions, and a transceiver, the instructions when executed causing the sending wireless device to: select an Avatar ID for an avatar representation of the sending wireless device; generate an authorization token that includes: the Avatar ID, a wireless device identifier of the sending wireless device, a wireless device identifier of the receiving wireless device, and an expiration time, and sign the authorization token to obtain a signed authorization token; and transmit, via a data channel with a receiving wireless device, the signed authorization token together with an address, such as a URL, associated with the Avatar ID for use in receiving-wireless device-centric rendering.532024P00529WO5. The wireless device of claim 4, wherein the authorization token includes the address, or part of the address or an indication of the address.

6. A method performed by a receiving wireless device (e.g. a UE) in an IMS avatar communication session in receiving-wireless device-centric rendering mode, comprising: receiving, via a data channel between a sending wireless device and the receiving wireless device, a received authorization token and an address associated with an Avatar ID selected by the sending wireless device, or an indication of the address, the token including at least: the Avatar ID, a sending wireless device identifier, a receiving wireless device identifier, and an expiration time; transmitting an avatar representation downloading request that includes the received authorization token to a media function (MF) for delivery to a Base Avatar Repository (BAR); obtaining an avatar representation associated with the sending wireless device in response to a successful verification at the BAR of a signature of the authorization token, the Avatar ID, the sending wireless device identifier, the receiving wireless device identifier; and of a valid expiry time of the authorization token ; and rendering the obtained avatar representation at the receiving wireless device.

7. The method of claim 6, wherein the avatar representation downloading request is transmitted directly or through a Distributed Content Application Server, DC AS.

8. The method of claim 6 or 7, wherein the avatar representation is obtained from the MF or from the DC AS.

9. The method of any of claims 6-8, wherein the token includes the address or part of the address or an indication of the address.

10. A receiving wireless device, such as a User Equipment, UE, comprising one or more processors, a memory storing instructions, and a transceiver, the instructions when executed causing the receiving wireless device to: receive, from a sending wireless device via a data channel, a signed authorization token and an address, such as a URL, or an indication of the address, wherein the address is associated with an Avatar ID selected by the sending wireless device, the token including at least: the Avatar ID, a UE identifier of the sending UE, a UE identifier of the receiving wireless device, and an expiration time;542024P00529WO transmit an avatar representation downloading request including the token and the Avatar ID to an MF for delivery to a Base Avatar Repository, BAR, directly or through a Distributed Content Application Server, DC AS; receive, from the MF, the avatar representation associated to the sending UE upon successful verification of the authorization token at the BAR as defined by the token checks; and render the avatar representation received.

11. The wireless device of claim 10, wherein the token includes the address or part of the address or an indication of the address.

12. A method for adaptive language configuration in a communication system wherein the method comprises: sending, by a first device, a communication request to initiate a communication with at least one second device, the request including an indication (to a network function or the second device) that adaptive language is supported at the first device, receiving, by the first device, a communication confirmation accepting the communication with one or more of the second devices, wherein the communication confirmation includes a configuration element comprising at least one of* an indication of first adaptive language settings (e.g. to be applied at the first device),* at least an indication of second adaptive language settings of at least the second device, and* an adaptive language model or model identifier of an adaptive language model or a confirmation to use an adaptive language model pre-configured at the first device to perform the adaptive language procedures, performing, by the first device, a first adaptive language procedure to an incoming data stream from the one or more of the second devices according to the configuration element; and / or performing, by the first device, a second adaptive language procedure to one or more outgoing data stream to one or more second devices according to the second adaptive language settings and the adaptive language model.552024P00529WO13. A method for adaptive language configuration in a communication system, wherein the method comprises: sending, by a first device, a communication request to initiate a communication with at least one second device, the request including an indication to a network function or the second device, wherein the indication comprises a request to perform adaptive language for the first device and / or second device, and wherein the method comprises at least one of: receiving, by the first device, a communication confirmation accepting the communication with one or more of the at least one second device, wherein the communication confirmation includes an indication of available languages to perform adaptive language, and sending, by the first device, the first adaptive language setting including at least an indication of a selected language from the available languages, or receiving, by the first device, a communication confirmation accepting the communication with one or more second devices, wherein the communication confirmation includes an indication of the first adaptive language settings, the first adaptive language setting including at least an indication of a selected language, and receiving, by the first device, at least a data stream whose adaptive language is according to the first adaptive language settings.

14. A method for adaptive language configuration in a communication system, the method comprising: receiving, by a second device, a communication request to initiate a communication with at least one first device, the request including an indication from a network function or the first device wherein the indication comprises a request to perform adaptive language, sending, by the second device, a communication confirmation accepting the communication with one or more of the at least one first devices, wherein the communication confirmation includes at least one of an indication of first adaptive language settings, an indication of second adaptive language settings of the second device, a request to perform adaptive language at the second device anda confirmation / user consent to perform adaptive language at the first device or network function.

15. A method for adaptive language configuration in a communication system, wherein the method comprises: receiving, by a second device, communication request to initiate a communication with at least one first device, the request including an indication from a network function or the first device, wherein the indication comprises an indication to perform adaptive language, sending, by the second device, a communication rejection, wherein the communication rejection indicates that the second devices does not accept the communication with one or more first devices or wherein the communication rejection includes at least one of an indication of a first rejected adaptive language setting, an indication of a second rejected adaptive language setting of the second device or a rejection to perform adaptive language at the first or second device or network function.

16. The method of claim 14 or 15, wherein the method further comprises: receiving, by the second device, a further communication confirmation including a confirmation of the first and / or second adaptive language settings of at least the second device, and an adaptive language model or a model identifier of an adaptive language model or a confirmation to use an adaptive language model pre-configured at the second device to perform the adaptive language procedures, performing, by the second device, a second adaptive language procedure to one or more incoming data stream from one or more first devices according to the second adaptive language settings and the adaptive language model; and performing, by the second device, a first adaptive language procedure to one or more outgoing data stream to one or more first devices according to one or more of the first adaptive language settings and the adaptive language model.

17. The methods of any of the claims 12-16, wherein the first or second adaptive language settings comprise at least one of: an indication whether or not adaptive language should be activated or not, a preferred language,a preferred language when translating sign language into text, a preferred language complexity when translating, a preferred voice style, a minimum required accuracy level, a timing of the output of the adaptive language in relation to the original input, a volume of the output of the adaptive language in relation to the original input, a composition of the adaptive language and the original input, a list of available languages to perform the adaptive language procedure, translation thresholds when performing the adaptive language procedure, a network-centric rendering or User Equipment-centric rendering when executing the adaptive language procedures, an address, such as a URL, of an Avatar representative of the preferred language.

18. The method of any of the claims 12-17, wherein the adaptive language model comprises at least one of: a voice input to voice output translation model for an input-output language combination; a sign language to text translation model for the preferred language; a sign language to voice translation model for the preferred language; a voice input to sign language; a voice input to body language.

19. The method of any of claims 12 - 18, comprising, if the first and / or second device is unable to apply all or some of the preferred adaptive language settings, the first and / or second device defaulting to a set of pre-configured language preferences stored in the first and / or second device and / or communication system.

20. The method of any of claims 12-19, comprising, if the first and / or second device is unable to receive or process the adaptive language settings from the second and / or first device, a fallback mechanism is initiated, said fallback mechanism including the first and / or second device receiving a notification, said notification being indicative of a conflict and / or a default adaptive language setting.582024P00529WO21. The method of any of claims 12-20, comprising the first device or the second device providing feedback for rating a quality of the adaptive language procedures, the quality including one or more of the accuracy of the adaptive language procedure, the effectiveness of the adaptive language procedure, the latency of the adaptive language procedure, the fluidity of a translated signal.

22. The method of any of claims 12-21, wherein the adaptive language procedure comprises combining the usage of the adaptive language model and of an Avatar representation in an Avatar communication.

23. The method of any of claims 12-22, wherein the adaptive communication settings of the first and / or second device are stored in and / or retrieved from a data function (e.g., HSS / UDM) in the communication system as part of the user's subscription data.

24. The method of any of claims 12-23, wherein the communication request or communication confirmation or communication rejection or notification or feedback are communication protocol commands, voice commands or A / V output.

25. A method for operating a communication system, said communication system comprising a device performing the method of any of claims 12-24 .

26. The method of claim 25, comprising the first device and / or second device and / or a network function in the communication system learning a user's language preferences over time and automatically updating stored preferences based on previous selections and interactions of the user.

27. The method of claim 25 or 26, the method comprising, if some adaptive language settings are missing from either the first and / or the second device during the setup of the communication session, the communication system dynamically adjusting the adaptive language based on the context of the ongoing conversation.592024P00529WO28. The method of any of claims 25-27 , comprising the communication system storing a log of any missing adaptive language settings and notifying the first and / or second device to update their adaptive language for future communication sessions.

29. The method of any of claims 25-28, wherein the communication system utilizes Al-based algorithms to predict likely adaptive language settings for future sessions based on historical data and user behavior patterns and sends the predicted adaptive language settings to the first and / or second device.

30. The method of any of claims 25-29, comprising the first and / or second devices synchronizing (optionally periodically) the stored adaptive language settings and / or model with the communication system to ensure up-to-date settings are available for seamless communication.

31. The method of any of claims 25-30, comprising the first device and / or second device overriding a pre-configured or predicted adaptive language settings during a communication session if any of the first and second device prefers to select a different adaptive language setting.

32. The method of any of claims 25-31, wherein the first device and / or second device and / or network function in the communication system provides feedback to the entity performing the adaptive language procedure wherein the feedback comprises one or more: timing misalignment, request to repeat the adaptive language procedure with the same or different settings, request to adapt the adaptive language settings.

33. The method of any of claims 25-32, wherein the first device and / or second device and / or network function in the communication system provides feedback to the first or second device about adaptive language processing errors, which may include a request for the user to repeat part of the communication or to slow down the communication.

34. An apparatus for adaptive language settings in a communication system wherein the apparatus comprises a transmitter, a receiver, and a controller;602024P00529WO wherein the transmitter is configured to send a communication request to initiate a communication with at least a second device, the request including an indication to a network function or the second device wherein the indication comprises an indication to perform adaptive language at the apparatus, wherein the receiver is configured to receive a communication confirmation accepting the communication with one or more second devices, wherein the communication confirmation includes a configuration element comprising at least one of the first adaptive language settings (e.g. to be applied at the first device), at least an indication of second adaptive language settings of at least the second device and / or an adaptive language model or model identifier of an adaptive language model or a confirmation to use an adaptive language model pre-configured at the first device to perform the adaptive language procedures, wherein the controller is configured to performing at least one of a first adaptive language procedure to an incoming data stream from one or more second devices according to the configuration element; and / or a second adaptive language procedure to one or more outgoing data stream to one or more second devices according to the second adaptive language settings and the adaptive language model.

35. An apparatus for adaptive language settings in a communication system wherein the apparatus comprises: a transmitter, a receiver, and a controller: wherein the controller causes the transmitter to send a communication request to initiate a communication with at least one second device, the request including an indication to a network function or the second device wherein the indication comprises a request to perform adaptive language for the apparatus and / or second device, wherein the receiver is configured for receiving a communication confirmation accepting the communication with one or more second devices, wherein the communication confirmation includes an indication of available languages to perform adaptive language, and the transmitter sends the first adaptive language setting including at least an indication of a selected language from the available languages, and / or wherein the receiver is configured for receiving the communication confirmation accepting the communication with one or more second devices, wherein the communication confirmation includes an indication of the first adaptive language settings, the first adaptive setting including at612024P00529WO least an indication of a selected language, and the receiver is configured for receiving at least a data stream whose adaptive language is according to the first adaptive language settings.

36. An apparatus for adaptive language settings in a communication system wherein the apparatus comprises: a receiver configured for receiving a communication request to initiate a communication with at least one first device, the request including an indication from a network function or the first device wherein the indication comprises a request to perform adaptive language, a transmitter configured for sending a communication confirmation accepting the communication with one or more of the at least one first devices, wherein the communication confirmation includes at least one of an indication of the first adaptive language settings, an indication of the second adaptive language settings of the apparatus, a request to perform adaptive language at the apparatus and a confirmation / user consent to perform adaptive language at the first device or network function.

37. An apparatus for adaptive language settings in a communication system wherein the apparatus comprises: a receiver configured for receiving communication request to initiate a communication with at least one first device, the request including an indication from a network function or the first device, wherein the indication comprises an indication to perform adaptive language, a transmitter adapted to send a communication rejection indicating that the apparatus does not accept the communication with one or more first devices or wherein the communication rejection includes at least one of an indication of a first rejected adaptive language setting, an indication of a second rejected adaptive language setting of the apparatus or a rejection to perform adaptive language at the apparatus, the first device or network function.

38. A computer program for adaptive language settings in a real time communication system, wherein the program comprises instructions for performing the methods of any of the claims 1- 3, 6-9, or 12-33.

Images