Communication system and method

Abstract

A communication system and method includes receiving a call at a first user equipment (UE), where the call originates from a second UE. A selection of an avatar is received at the first UE. The first UE sends an avatar identifier of the selected avatar to a data channel (DC) application server. The DC application server sends the avatar identifier to an avatar storage location as part of a request for avatar definition data. The avatar storage location retrieves the avatar definition data based on the avatar identifier. The avatar storage location sends the avatar definition data to the DC application server. The DC application server sends the avatar definition data to a media function (MF). The MF generates avatar stream data based on the avatar definition data. The MF sends the avatar stream data to the second UE.

Description

Technical Field

[0001] This invention relates to a system and method for generating, registering, and using user agents or avatars, particularly for calls within a mobile network. Background Technology

[0002] In the world of digital communication and virtual environments, avatars are steadily gaining greater relevance as an indispensable tool for personal representation and interaction. When a user is unavailable, an avatar can act as a proxy for the user or enhance privacy. For example, avatars can be used in multi-user online games.

[0003] In general use, avatars are defined as things that appear and hear according to a user's preferences. Identifying a user based on the avatar they are using can be difficult or impossible because an avatar's appearance may not closely match or may be completely different from the person they represent. This can pose security or protection risks when avatars communicate with other users, for example, in computer games or virtual worlds, especially for vulnerable users. This can also be important in preventing fraud or misrepresentation.

[0004] Therefore, there is a need for improved methods and systems for the security, control, and management of incarnations, their creation, and use. Summary of the Invention

[0005] When a user is busy or unable to answer calls, it is useful for an agent to handle calls and other external interactions on the user's mobile device. Such an agent can take the form of an avatar, which can be a visual representation of the user or a digital personification of a person. However, an avatar can take any form. Data or metadata can be used to generate avatars, and different users can have different avatars. A single user can have multiple avatars for different occasions or situations. For example, a user might have an avatar for professional or work interactions and different avatars for social interactions. For other purposes or simply for variety, a user can have different avatars to choose from.

[0006] Users can generate data to define each avatar so that they can have different characteristics. Users can use a mobile application to generate avatar definition data.

[0007] Different avatars have different avatar identifiers (preferably unique identifiers). This allows different avatars to be instantiated when requested. Users operating mobile devices or any user equipment (UE) also have their own subscriber identifiers, which are used to access the mobile network. To use an avatar on the mobile network (e.g., within a call), avatar definition data and avatar identifiers need to be securely generated and registered to prevent impersonation and restrict the use of the avatar to what the mobile network allows for that particular user. It is possible that some users do not have permission to generate and use avatars (e.g., children), or that avatars may only be available for limited use or only for a limited time. This method and system allow for such security and control.

[0008] A user uses a mobile device or UE to send a request to register a (new) avatar. This request includes the user's subscriber information, such as their Subscription Permanent Identifier (SUPI), General Public Subscription Identifier (GPSI), or other subscription or device identifiers (e.g., International Mobile Subscriber Identity—IMSI, International Device Identifier—IMEI, or Permanent Device Identifier—PEI). This can be sent by a mobile application on the UE or as part of another action or component, such as a local application for making and receiving calls. An application server (e.g., within the mobile network) receives and verifies the request. For example, the application server can determine whether the user has permission to register an avatar or whether they have reached the limit on the number of avatars they can generate and register.

[0009] The application server verifies the request by sending it to the Data Channel Signalling Function (DCSF). The DCSF needs to obtain subscriber information based on the subscription identifier (e.g., SUIP / GPSI) included in the request. The DCSF accomplishes this by querying components of the user's home network, such as the Home Subscriber System (HSS), Unified Data Management (UDM), and / or Unified Data Warehouse (UDR). The home network components provide subscriber information based on the supplied subscriber identifier. Subscriber information may include access information, UE registration details, and / or communication session information, such as the UE's Subscriber Access and Mobility Management Function (AMF), Session Management Function (SMF), and / or Authentication Server Function (AUSF). This enables the UE to be verified and authenticated for avatar services. Subscriber information may also include a list of previously registered avatars for a specific subscriber.

[0010] The DCSF sends the subscriber information (retrieved from the UE's home network) to a storage facility or data storage device used to store avatar data. This could be referred to as the Basic Avatar Repository (BAR). The BAR generates a new avatar identifier (ID) and stores the avatar ID along with the subscriber identifier. The BAR also sends the avatar ID back to the DCSF, which then sends the newly generated avatar ID to the components and application servers of the home network.

[0011] The application server sends the avatar ID to the UE and another application server (e.g., the data channel application server). The data channel application provides avatars and other extended reality (XR) or virtual reality (VR) services. Simultaneously (before or after other steps), the UE generates definition data or metadata to define the characteristics of the avatar. This may include, for example, the avatar's appearance, voice, and other characteristics. The UE sends the avatar definition data to the BAR, which stores the avatar definition data along with the avatar ID, so that the avatar definition data can be retrieved if and when the avatar ID is provided (e.g., as part of a separation process).

[0012] Once an avatar is registered, it can be used for various applications. One such application is to act as an agent for the user of the UE during a call. For example, a user can receive calls from a second UE or mobile device at their (first) UE. The call ringing screen can indicate the options for incoming calls and for the avatar to answer the call. There may be several available and registered avatars, and the user can choose one of them. For example, one avatar may be more suitable for work or formal calls, while another avatar may be more suitable for social or family calls. Optionally, an avatar generation and registration process can be performed (e.g., if the user does not have any current, active, or available avatars).

[0013] After an avatar is selected, the UE sends or transmits the corresponding avatar identifier (e.g., an identifier registered during the method described above) to the DC application server. This forms a request for the corresponding avatar definition data. The DC application server sends the avatar identifier to the avatar storage location or BAR, which retrieves the avatar definition data based on the avatar identifier provided in the request.

[0014] The avatar storage location sends avatar definition data to the DC application server, which then sends the data to the Media Function (MF) or Media Execution Server. The MF uses the avatar definition data to generate avatar streaming data (e.g., by executing software code using the avatar definition data). The avatar streaming data is then directly transmitted to a second UE (e.g., via a mobile network), allowing the second UE to view the avatar within a call with the first UE. This simplifies the process and reduces network traffic.

[0015] Data can be sent to and from the second UE and MF, enabling the creation of responses by the avatar using call responses, voice, video (if it is a video call), and other components. For example, avatar streaming data can generate video and voice of the avatar, which can ask questions. Responses to these questions (e.g., voice or text commands from the user of the second UE) can also be sent from the second UE to the MF and interpreted (e.g., using a speech-to-text translator). The MF can process this data in real time, providing real-time responses in the form of a dialogue without human intervention.

[0016] The user of the first UE can be informed of the progress or content of the avatar call. This could take the form of a speech-to-text converter that provides a real-time written transcript. Alternatively or additionally, a text transcript or summary could be provided at the end of the call. For example, at any time, the user of the first UE can intervene in the call and suspend the avatar.

[0017] According to the first aspect, a communication method is provided, comprising: A call is received at a first user equipment (UE), wherein the call originates from a second UE; Receive the choice of avatar at the first UE; The first UE sends the avatar identifier of the selected avatar to the data channel DC application server; The DC application server sends the avatar identifier as part of the request for avatar definition data to the avatar storage location; The avatar storage location retrieves avatar definition data based on the avatar identifier; The avatar storage location sends avatar definition data to the DC application server; The DC application server sends avatar definition data to the media function MF; MF generates avatar stream data based on avatar definition data; and The MF sends avatar stream data to the first UE. Therefore, the agent or avatar can answer calls more conveniently and securely. For example, the call could be a video call using a mobile network.

[0018] Optionally, the method may also include registering the avatar before receiving a call. Registration can be made by any suitable method, but is preferably the registration process described in detail herein.

[0019] Optionally, during a call with the second UE, avatar stream data can be rendered to generate interactions between the avatar and the second UE. This rendering can occur on the UE or at another location (e.g., within a part or component of a mobile network).

[0020] Optionally, the interaction may include a response to a query within a call from the second UE. This query may appear in the avatar (e.g., "Who is calling?"). "What is the subject of the call?" (etc.) or from the caller (e.g., "When is the first user available to speak?"). (”).

[0021] Optionally, the interaction may include a request to obtain the reason for the call.

[0022] Optionally, the interaction may include an offer to call back to the second UE. This offer or inquiry may originate from an avatar (e.g., "The person you are calling is currently unavailable. Would you like them to call you back?"). (”).

[0023] Optionally, the method may also include consulting the user's calendar for the first UE to determine the available time and date for a callback. The calendar may be an application on the first UE, or it may be data stored elsewhere (e.g., on a separate server or at a virtual server or service location). For example, the calendar may be accessed via an application programming interface (API).

[0024] Optionally, the rendered avatar may present a proposal of the determined available time and date of the callback to the user of the second UE during the call. For example, one or more alternative callback times and dates may be provided.

[0025] Optionally, when the rendered avatar receives an indication from the user of the second UE during a call to reject the proposed callback time and date, the avatar's rendering proposes an alternative time and date to the user of the second UE during the call. This process, or a series of interactions, may be repeated until a suitable (approved) date and time are presented and accepted.

[0026] Optionally, the method may further include the rendered avatar receiving an indication from the user of the second UE during the call to accept the proposed callback time and date, and in response, saving the callback appointment at the accepted time and date in the calendar of the user of the first UE. For example, the appointment or reminder may have an advance reminder time (e.g., sending a notification or reminder in advance of the appointment).

[0027] Optionally, the method may also include providing a written description of the interaction and / or a summary of the call outcome. This could be text displayed on the first UE's display, stored in the UE's memory, sent (e.g., via email) to the user of the first UE, or otherwise provided. For example, the text could be generated at a media function (MF) and transmitted over a network.

[0028] Optionally, a written description may be provided in real time during the interaction and / or at the end of the call. For example, as the call progresses, a real-time display may show a scrolling or continuous stream of text on the screen.

[0029] Optionally, the method may further include receiving a request for intervention in the call from a user of the first UE, and in response to the request, pausing or stopping the merging of avatar stream data during the call. For example, this could be done by the user pressing a button or selectable icon on the first UE's display. This would pause or stop the rendering of the avatar (and the streaming of avatar stream data from the MF) and provide the user with an interface to continue the call (e.g., activating the microphone, camera, displaying a second user on the screen, etc.).

[0030] According to the second aspect, a user equipment (UE) is provided, comprising: One or more processors; and One or more memories store computer-executable instructions that, when executed by a processor, cause the UE to: A call is received at the UE, which is a first UE, wherein the call originates from a second UE; Receive the choice of incarnation; and The selected avatar's identifier is sent to the data channel DC application server. Multiple UEs may exist in the mobile network. Each UE can act as either the first UE (receiving calls) or the second UE (initiating and making calls).

[0031] According to the third aspect, a system is provided, comprising: One or more UEs, as described above; Data channel DC application server; Incarnation storage location; and Media Functions (MF) The DC application server is configured to send the avatar identifier as part of a request for avatar definition data to the avatar storage location. The avatar storage location is configured as follows: Retrieving avatar definition data based on avatar identifier, and Send the avatar definition data to the DC application server. The DC application server is also configured to send the avatar definition data to the MF, and The MF is configured as follows: Generate avatar stream data based on avatar definition data, and The avatar stream data is sent to the second UE. For example, there may be multiple entities or devices, each operating in a communication network. The second UE (caller) is the UE that initiated the call to the first UE (call receiver).

[0032] According to another aspect, a method for registering an avatar is provided, the method comprising: The user equipment (UE) sends a request to register an avatar, which includes the UE's subscriber identifier; The application server receives requests from the UE; The application server sends a request to the Data Channel Signalling Function (DCSF), and in response, the DCSF requests subscriber information from the UE subscriber's home network components based on the subscriber identifier. Components of a home network that provide subscriber information to the DCSF; DCSF sends subscriber information to the avatar storage location; The avatar storage location generates the avatar identifier; The avatar storage location stores the avatar identifier along with the subscriber identifier; The avatar storage location sends the avatar identifier to the DCSF; DCSF sends avatar identifiers to components and application servers in the home network; The application server sends avatar identifiers to the UE and the data channel application server; The UE generates avatar definition data; The UE sends the avatar definition data to the avatar storage location; and The avatar storage location stores the avatar definition data along with the avatar identifier. Therefore, avatars can be registered reliably and securely.

[0033] Preferably, the application server can be an IP Multimedia Subsystem (IMS) application server. Other application servers can be used, but an IMS application server is particularly suitable for avatar use.

[0034] Optionally, the subscriber identifier may include the UE subscriber's Subscription Permanent Identifier (SUPI) and / or General Public Subscription Identifier (GPSI). Other subscription or device identifiers may be used, such as International Mobile Subscriber Identity (IMSI), Permanent Device Identifier (PEI), or International Mobile Equipment Identifier (IMEI).

[0035] Optionally, the method may also include a component of the home network that stores an avatar identifier associated with subscriber information. Thus, the home network can recognize avatars generated by a specific subscriber.

[0036] Optionally, the home network can store the avatar identifier along with previously generated avatar identifiers of the UE's subscribers. Therefore, the home network can maintain a list of avatars for a specific subscriber.

[0037] Alternatively, components of the home network can be Unified Data Management (UDM) and / or Unified Data Warehouse (UDR). For example, other components of the home network, such as HSS or HLR, can be used.

[0038] Preferably, the avatar definition data may include any one or more of the following: voice, images, and video. Other descriptive data, such as color and shape, may also be included.

[0039] Optionally, the method may also include the application server verifying the request by receiving an avatar identifier from the DCSF to determine if the UE's subscriber has permission to generate an avatar. Security, verification, and authentication may also be performed. Thus, by receiving the avatar identifier (after a successful or earlier step), the application server can be confident that the subscriber has permission to generate, register, and use avatars (e.g., within a call).

[0040] Optionally, the method may further include: A call is received at a UE, wherein the UE is a first UE and the call originates from a second UE; The first UE receives the selection of the avatar corresponding to the avatar identifier; The first UE sends an avatar identifier to the DC application server; The DC application server sends the avatar identifier as part of the request for avatar definition data to the avatar storage location; The avatar storage location retrieves avatar definition data based on the avatar identifier; The avatar storage location sends avatar definition data to the DC application server; The DC application server sends avatar definition data to the media function (MF) or media execution server; MF generates avatar stream data based on avatar definition data; and The MF sends avatar stream data to the first UE. For example, the avatar can be used for purposes other than calling, such as within games or social media applications. The MF then sends the avatar stream data directly to the second (calling) UE.

[0041] Alternatively, communication between the data channel application server and the avatar storage location can be conducted via a dedicated interface. This can be a separate interface from those used in other signaling and messaging within the method and system.

[0042] According to another aspect, a user equipment (UE) is provided, comprising: One or more processors; and One or more memories store computer-executable instructions that, when executed by a processor, cause the UE to: Send a request to register an avatar, wherein the request includes the subscriber's identifier for the UE; Receive the avatar identifier from the application server; Generate avatar definition data; and Send the avatar definition data to the avatar storage location.

[0043] Preferably, the avatar definition data can be generated by the mobile application. For example, the avatar definition data can also be generated outside the UE (e.g., downloaded from an external source).

[0044] Alternatively, the application can be downloaded from a data channel application repository located within the core network. Other application storage devices can be used to provision the application.

[0045] According to another aspect, a system is provided, comprising: One or more UEs as previously described; Application server; Data channel signaling function, DCSF; Components of a home network; Incarnation storage location; and Data channel application server, wherein the application server is configured to: Receive requests from the UE, and Send the request to the DCSF; and wherein the DCSF is configured to: In response to a request from the application server, subscriber information is requested from components of the home network based on the subscriber identifier; and whereby... Components of the home network provide subscriber information to the DCSF; and among them The avatar storage location is configured as follows: Generate avatar identifiers, Store the avatar identifier together with the subscriber identifier, and Send avatar identifiers to components and application servers of the home network; and among them The application server is also configured as follows: Send avatar identifiers to the UE and the data channel application server; and among them The avatar storage location is also configured as follows: Store the avatar definition data together with the avatar identifier.

[0046] Preferably, the avatar storage location can be located within the (mobile operator's) core network.

[0047] It should be noted that individual methods can be combined and used in any combination. For example, a method for registering an avatar can be combined with and follow a communication method. However, these methods can be implemented separately. Furthermore, the UE and the system can each include all the functions and components for registering and using the avatar (e.g., by implementing the communication method).

[0048] The methods described above can be implemented as computer programs that include program instructions for operating a computer. Computer programs can be stored on computer-readable media, including non-transitory computer-readable media.

[0049] A computer system may include one or more processors (e.g., local, virtual, or cloud-based), such as a central processing unit (CPU), and / or a single graphics processing unit (GPU) or a collection of GPUs. The processors may execute logic in the form of a software program. The computer system may include memory, comprising volatile and non-volatile storage media. Computer-readable media (CRMs) may be included to store logic or program instructions. For example, embodiments may include a non-transitory computer-readable medium (CRM) storing software including instructions executable by one or more computers, which, upon such execution, cause the one or more computers to perform disclosed methods. A non-transitory CRM may refer to a CRM that stores data for a short period or in the presence of power, such as a memory device or random access memory (RAM). For example, a non-transitory computer-readable medium may include storage components such as a hard disk (e.g., a magnetic disk, optical disk, magneto-optical disk, and / or solid-state disk), an optical disk (CD), a digital versatile disk (DVD), a floppy disk, a magnetic tape cassette, and / or a magnetic tape. Different parts of the system may be connected using a network (e.g., a wireless network and a wired network). The computer system may include one or more interfaces. For example, a computer system may contain a suitable operating system, such as UNIX (RTM), Windows (RTM), or Linux (RTM).

[0050] It should be noted that any of the features described above may be used with any particular aspect or embodiment of the invention. Attached Figure Description

[0051] This invention can be practiced in several ways, and embodiments will now be described by way of example only and with reference to the accompanying drawings, wherein: Figure 1 A flowchart of the method for registering an avatar is shown; Figure 2 It shows the use of Figure 1 A flowchart of the communication method of the embodiment; Figure 3 The following diagram illustrates the implementation. Figure 1 and 2 A schematic diagram of the computer system for the method; Figure 4 The following diagram illustrates the implementation. Figure 1 and 2 A schematic diagram of the communication system using this method; Figure 5 The following diagram illustrates the implementation. Figure 1 and 2 Another schematic diagram of the communication system using this method; Figure 6 The following diagram illustrates the implementation. Figure 1 and 2 A schematic diagram of a part of the communication system of the method; Figure 7 The diagram illustrates the process of registration. Figure 1 Another aspect of the sequence diagram of the method of incarnation; Figure 8 The diagram shows... Figure 2 Sequence diagrams of other aspects of the communication methods; and Figure 9 A schematic diagram is shown of the process for interpreting speech during a call that includes an avatar.

[0052] It should be noted that the accompanying drawings are provided for simplicity and are not necessarily drawn to scale. Similar features are provided with the same reference numerals. Detailed Implementation

[0053] An avatar refers to a digital representation, agent, or characteristic of a user in a virtual environment such as virtual reality (VR), augmented reality (AR), or extended reality (XR). These avatars range from 2D representations to highly detailed, realistic 3D models that mimic a user's appearance or behavior in real time.

[0054] Currently, at some point, 3GPP standardization is focused on XR-related concepts. This disclosure presents the role of these avatars, including their integration with existing communication services and their technical support for immersive virtual environments, thereby enhancing the user experience.

[0055] Figure 1A flowchart of method 10 for registering an avatar or proxy for a user is shown. At step 15, the mobile device or user equipment (UE) initiates method 10 by requesting registration or a new avatar identifier. This request can be initiated at any time, including but not limited to when the user receives a call. The request includes the UE's identifier. The UE's identifier can be a Subscription Permanent Identifier (SUPI), a General Public Subscription Identifier (GPSI), or other identifiers (e.g., International Mobile Subscriber Identity—IMEI, International Device Identifier—IMEI, or Permanent Device Identifier—PEI). At step 20, an application server, such as an IP Multimedia Subsystem (IMS), receives the request from the UE.

[0056] The application server verifies the request by confirming that the requesting UE has permission to create an avatar. At step 25, the application server completes this by sending a request to the Data Channel Signalling Function (DCSF). In response, the DCSF requests subscriber information by sending the UE identifier included in the request to a component of the UE subscriber's home network (step 30). This component could be, for example, a Home Location Register (HLR), a Home Subscriber Server (HSS), a Unified Data Management (UDM), and / or a Unified Data Warehouse (UDR).

[0057] At step 35, a component of the home network provides subscriber information to the DCSF, and at step 40, the DCSF sends the subscriber information to the avatar storage location (e.g., the Basic Avatar Repository—BAR). Optionally, one or more identifiers of the UE may also be sent along with the subscriber information. This triggers the BAR to generate a new avatar or proxy identifier (step 45) and store the avatar identifier along with the subscriber identifier, so that the avatar identifier can be retrieved when the subscriber identifier is provided (step 50). At step 55, the BAR sends the generated avatar identifier to the DCSF (in response to the DCSF sending the UE subscriber information to the BAR).

[0058] At step 60, the DCSF now sends the avatar identifier to the home network component (UDM / UDR) and to the application server. At step 65, the application server sends the avatar identifier to the UE and the data channel (DC) application server (e.g., an extended reality (XR) or virtual reality (VR) application server). The UE can now generate (or has already generated) data defining the avatar (step 70). This data may include metadata and any other information necessary for rendering the avatar. At step 75, this data definition data is sent to the BAR, and at step 80, the BAR stores the avatar definition data along with the avatar identifier. The BAR may have a database 272 for storing this data.

[0059] Once at least one avatar has been created and registered for a UE user, that avatar can be used. Figure 2 A flowchart is shown for a method 100 for incorporating an avatar into a call made by a second UE or a mobile device to a first UE.

[0060] At step 115, the first UE receives a call. The user of the first UE decides not to answer the call, but instead selects an avatar (if they have more than one avatar to choose from) to answer the call on their behalf (step 120). At step 125, the first user sends the avatar identifier of the selected avatar to the DC application server. The DC application server can verify the request to determine if the avatar identifier is valid (e.g., it can optionally expire after a period of time). At step 130 (e.g., after successful verification), the DC application server creates a request for avatar definition data, including the avatar identifier, and sends the request to the avatar storage location or BAR.

[0061] At step 135, the BAR uses the avatar identifier as a reference to retrieve avatar definition data from a database or data storage device. The avatar definition data may have been created on the first UE or elsewhere. If no saved avatar definition data is available for a particular requested avatar identifier, the BAR may return an error or simply fail to respond. When the saved avatar definition data is available and can be retrieved, at step 140, this data is sent by the BAR to the DC application server.

[0062] Avatar definition data is data or metadata generated by appropriate executable content or functionality to produce visual, video, and / or audio data representing the avatar. This processing is performed by a Media Function (MF) or a media generation server. At step 145, the DC application server sends the avatar definition data to the MF, and at step 150, the MF generates avatar streaming data based on the avatar definition data. At step 155, the MF streams the data to a second UE (e.g., the avatar's video and audio). This could take the form of the first UE accepting a call, but instead, the first UE's microphone (and camera) is used to capture the first user's voice (and image), and the avatar representation is incorporated into the call stream, which is sent directly to the second UE. At step 160, a response from the user of the second UE is obtained and sent to the MF. This processing can include natural language processing and artificial intelligence (AI) and machine learning (ML) techniques. This processing can include, for example, AI-ML-based speech recognition, intent recognition, entity recognition, data access, natural language generation, and follow-up responses.

[0063] Once an avatar call is initiated, it can continue without user input. However, the user can be updated on the call's progress in real time or after the call is completed. For example, a transcript of the ongoing call (both the avatar's voice text and the caller's voice text) can be captured and presented to the user of the first UE. This text can be displayed on the screen or sent or stored as a file after the call is completed. In some example implementations, the user of the first UE (who receives the call and initiates the avatar) can intervene in the call and suspend or stop the avatar from participating in the call. For example, there might be some switching action, such as the avatar announcing that the user will soon enter the call.

[0064] An avatar can interact with a call in various ways. For example, the avatar can ask the caller to describe the purpose of the call, and this can be transmitted to the call recipient (the user of the first UE). The avatar can additionally or alternatively provide the caller with the option for the call recipient to call back the caller. If the caller accepts such an option, the systems and methods operating on the first UE can query or consult the call recipient's calendar (either within the UE or by accessing a remote calendar). The purpose of this calendar consultation is to find a suitable and flexible time for the call recipient to call back the caller. For example, this could be indicated in the calendar as part of a regular workday (if a formal or work avatar is selected), or as a flexible time slot in the evening or on a weekend if a social avatar (family avatar) is selected. There may be advance rules set by the call recipient to determine whether, how, and when a call back can be scheduled.

[0065] Once a suitable callback time and date are determined, this information can be presented to the caller by the avatar during the call. If the caller accepts the callback time and date (e.g., by saying "yes" or nodding during a video call), the system and method can add a calendar entry (with or without a reminder) at that time. If the caller indicates that they cannot accept the time and date (e.g., by saying "no" or shaking their head during a video call), the calendar can be consulted again to find alternative free times and dates that also meet the caller's criteria. This process can be looped or continued until an acceptable callback time and date is provided and approved by the caller. For example, interaction with the calendar can be done via an application programming interface (API).

[0066] Refer to each Figure 1 and Figure 2 Both methods 10 and 100 described can be performed by computer system 200. For example, computer system 200 may include one or more separate machines or nodes.

[0067] like Figure 3As shown, the computer system 200 includes several components, including a communication interface 220, system circuitry 230, input / output (I / O) circuitry 240, display circuitry and interface 250, and data storage device 270. System circuitry 220 may include one or more processors or CPUs 280 and memory 290. System circuitry 230 may include any combination of hardware, software, firmware, and / or other circuitry. System circuitry 230 may be implemented using one or more system-on-chip (SoC), application-specific integrated circuit (ASIC), microprocessor, and / or analog and digital circuitry.

[0068] The display circuitry can provide one or more graphical user interfaces (GUIs) 260, and the I / O interface circuitry 240 can include touch-sensitive or non-touch displays, sound, voice, or other recognition inputs, buttons, switches, speakers, audio, and other user interface elements. The I / O interface circuitry 240 can include microphones, cameras, headphones, and microphone input / output connectors, a Universal Serial Bus (USB) connector, and SD or other memory card slots. The I / O interface circuitry 240 may also include data media interfaces (e.g., CD-ROM or DVD drives) and other bus and display interfaces.

[0069] Memory 290 may include volatile (RAM) or non-volatile memory (e.g., ROM or flash memory). The memory may store the operating system 292, applications or software 294, dynamic data 296, and / or static data 298 of the computer system 200. For example, data storage device or data source 270 may include one or more databases 272, 274, and / or file storage or file system. Database 272 may form part of a BAR.

[0070] Figure 4 A schematic diagram of a system 300 for implementing methods 10 and 100 is shown. System 300 includes different components of a communication network and multiple interfaces for transmitting data and signaling between these components. Figure 4 The diagram illustrates the use of the IP Multimedia Subsystem (IMS) architecture in System 300. This architecture is integrated with other functions and is empowered by data channels (DCs). Connecting nodes and network functions are referenced to their corresponding interfaces (DC1, DC2, DC3, DC4, DC5, and DC6), and key connections for this example implementation are highlighted in the diagram. In this example, System 300 is approximately based on a 5GC architecture.

[0071] exist Figure 4The diagram illustrates a single UE 310. However, in the implemented system, more than one UE 310 can be operational. UE 310 sends requests for its registration avatar via the IMS proxy and service call session control functions, which handle routine IMS registration. The application server in this example implementation is an IMS application server (IMS AS) 320. The interface between IMS AS 320 and DCSF 330 is illustrated in the diagram. The home network component is a UDM / UDR 340. The interface (DC1) between IMS AS 320 and DCSF 330 is also shown.

[0072] exist Figure 4 In this diagram, the avatar storage location or repository is shown as the base avatar repository BAR 350. BAR 350 communicates with the DC application server 360 via interface DC6. The DC application server includes functionality to provide extended reality (XR) and augmented reality (AR) services. The DC application server communicates with the DCSF 330 via interface DC4. A mobile application is used on the UE 310 to generate avatar definition data. The mobile application is provided by the DC application repository 380.

[0073] As previously described, once an avatar is registered, the MF 370 receives avatar definition data from the DC application server 360 and streams the data to the UE 310 through various components of the system 300.

[0074] Figure 5 The diagram shows... Figure 4 The components shown are illustrated, but another schematic diagram of system 300 is shown illustrating various interfaces and different communication planes for data. This diagram illustrates where avatar data 410 is defined (within application 420 of UE 310) and generated (within MF 370). Media plane 430 provides streaming services for this data. Mobile network communication 440 is illustrated to show cellular messaging. IMS service 450 is illustrated within the mobile network.

[0075] In avatar communication and avatar calling scenarios, it is crucial to identify, authenticate, and authorize avatars within the communication network and map them to registered or subscribed UEs. The mobile application used to generate avatar definition data is the avatar creation application. Avatar creation applications can belong to the MNO network, third parties, or AR / XR-enabled devices, and, depending on the described methods and systems, support authentication and registration using a BAR (Basic Avatar Storage) / UDM (Unified Data Management) / UDR (Unified Data Warehouse) repository. Avatar creation applications can communicate with the core network to store avatars in the BAR (Basic Avatar Repository) within the operator network.

[0076] The creation and storage of avatars require the identification and authentication of the avatar. This, in turn, requires the secure assignment of an avatar identifier to the avatar, which is then mapped to a subscriber within the network. Mapping the avatar identifier to a specific user, and optionally also to a user equipment having a user and (optionally) a device identifier known to the network operator (e.g., Subscription Permanent Identifier (SUPI), General Public Subscription Identifier (GPSI), International Mobile Subscriber Identity (IMSI), Permanent Device Identifier (PEI), and / or International Mobile Equipment Identifier (IMEI)), is a critical step in the process because it ensures that the entity (avatar) can be trusted by other users, properly authenticated, authorized, and securely stored.

[0077] Before avatars can be created using the avatar creation app on UE 310, the app must be downloaded and installed after the subscriber is authenticated. However, the avatar creation app itself can be verified and authenticated to enhance security. Figure 6 This diagram illustrates the relationship between avatar creation applications and the Network Exposure Function (NEF) that performs such authentication and verification. This prevents malicious applications from being downloaded and installed. The process can be based on third-party application authentication as defined in 3GPP.

[0078] Once the verified avatar creation application is installed on UE 310, the first (and any other) avatar can be created and registered according to method 10. Figure 7 The sequence diagram shown illustrates another aspect of method 10. This results in avatars being identified and mapped to specific UEs and / or subscribers.

[0079] When an avatar is generated in the avatar creation application, it is submitted to the network to be stored in BAR 350 (and assigned to the UE's profile).

[0080] 1. The avatar registration request is sent from UE 310 and the application repository (within UE 310) to IMS AS 320.

[0081] 2. The IMS application server (AS) 320 sends a user information request to the DCSF 330. The DCSF 330 queries the subscription information from the UDM / UDR 340. The response from the UDM / UDR 340 includes the UE's SUPI / GPSI, optionally IMEI / PEI, and a list of avatar identifiers (if a previous avatar has been created and registered).

[0082] 3. After receiving information from UDR / UDM 340, DCSF 330 sends an avatar registration request to BAR 350 via XR AS 320. This request contains UE subscription information and a list of avatar IDs. The request prompts BAR 350 to send a new avatar identifier.

[0083] Note 1: The new signaling interface (DC6) is used for communication between XR (DC / AR) AS 360 and BAR 350.

[0084] 4. BAR 350 checks the UE's profile and avatar ID list, and generates a new avatar identifier. The new avatar identifier is sent back to DCSF 330.

[0085] 5. DCSF 330 provides an avatar identifier as a response to an IMS AS 320 registration request.

[0086] 6. IMS AS 320 updates the avatar identifier list in UDR / UDM 340 and XR (DC / AR) AS 360. Communication to XR (DC / AR) AS 360 is performed using the DC1 and DC4 interfaces. These interfaces have been modified to update information about the avatar list for a specific UE 310. DC4 contains GPSI information identifying the UE 310.

[0087] Note 2: The XR AS 320 includes data channel (DC) and / or AR AS capabilities and supports all next-generation real-time communications. The DC AS 360 is currently supported for IMS network tasks based on the data channel. The AR AS 320 currently supports IMS-based AR communication services.

[0088] 7. IMS AS 320 uses BAR 350 to confirm the avatar identifier and sends the new avatar identifier to UE310.

[0089] 8. UE 310 stores the new avatar together with the corresponding avatar identifier in BAR 350.

[0090] Figure 7 A more detailed diagram illustrates the sequence of method 100 for initiating an avatar call using an avatar, where the avatar is generated and registered using method 10. When a user needs to use an avatar, a list of avatar identifiers is downloaded to UE 310 via DCSF 330 using a bootstrap data channel. DCSF 330 verifies whether UE 310 is permitted to use an avatar representation.

[0091] Note 3: UE 310 may have a default avatar and several options to select any other saved avatar from the avatar list on the UE screen. These alternative avatars may be specific to a situation or selected based on the user's current preferences.

[0092] The method can begin once the following required components have been installed or are available on UE 310: IMS-Aware Avatar Application: For example, the application can be embedded in the UE 310, or it can be downloaded from the AR / XR / DC AS360 or DC application repository 380. The avatar application can be used to create avatars.

[0093] The IMS stack includes DC(AR)MTSI: DC(AR)MTSI support is provided in a chipset that has an IMS stack. This enables the device to communicate with an IMS network that supports data channels. Split Render Client (SRC) and Split Render Server (SRS) are split rendering components on the client and device, respectively. These can be used individually or in combination based on specific use cases and device capabilities.

[0094] The following components are available in the mobile IMS network: - MF MRF (Media Functions Media Repository Functions): MF 370 or Enhanced MRF includes additional media functions to support new services such as data channels, split rendering, avatar-related media functions, and AI-related media functions.

[0095] - BAR (Basic Avatar Repository): BAR 350 is used to store and retrieve avatar models according to 5GC.

[0096] Note 4: The avatar identifier stored in BAR 350 is assigned to each avatar and user identifier.

[0097] - DC Application Library: This is a storage system used to store applications, content, or services related to the data channel.

[0098] - AR / XR / DC AS 360: It manages and delivers immersive experiences by handling data communication, user sessions, and content delivery for AR / XR applications.

[0099] The following describes example usage of the avatar once it has been registered: UE 2 turns on the dialer and calls UE 1.

[0100] UE 1 receives a call (ringing).

[0101] The ringing answer option is downloaded from DC application server 360 (to UE 1).

[0102] UE 1 has stored two (but may have more) avatars in the BAR350 within the network. These avatars (their identifiers) are mapped, identified and associated with their subscriber identifiers (e.g., SUPI / GPSI), and optionally also associated with their device (IMEI / PEI).

[0103] UE 1 can create an avatar from a third-party provider or by using an avatar application on the device (part of the device or a downloaded application) and save the avatar to the network. In an alternative implementation, the IMS data channel on the dial screen may have the option to select content downloaded from the DC (XR / AR) AS 360 via the bootstrap data channel through the DCSF 330, and to create or edit the avatar on the screen (e.g., using JavaScript).

[0104] UE 1 saves the newly created avatar (in this example, the user of UE 1 wants to use the avatar to answer a call), and the avatar is mapped side by side to the identities of other pre-created avatars.

[0105] UE 1 receives a call and presents on their device screen the option to choose an avatar from pre-created avatars available to them. The name or icon is displayed on the telephone dialing screen.

[0106] Note: This utilizes the capabilities of a next-generation RTC employing the IMS data channel concept. When establishing a bootstrap data channel, options can be downloaded from the DC (AR / XR) AS 360 to the dialer on the JavaScript screen.

[0107] Therefore, instead of answering calls directly, UE 1 users select their avatars to do so.

[0108] When a call is established, an avatar of UE 1 appears on the screen of UE 2 (the caller or dialer). In an example implementation, the avatar asks the user of UE 2 about the reason for the call, whether UE 2 wants to leave a message, and / or whether the caller prefers a callback at a specific date and time.

[0109] In an example implementation, artificial intelligence (AI) can be used to enhance the operation and control of the avatar during a call, allowing the call to leave voice or text messages while talking to the avatar.

[0110] Note that AI can perform text-to-speech, speech-to-text, text-to-text, and speech-to-speech conversions, generate communications, and display the results on the screen of either or both parties.

[0111] UE 1 can receive a copy of the communication between the avatar and the caller of UE 2 on their screen.

[0112] If the user of UE 1 wishes to or leaves the call entirely to the avatar, the user of UE 1 can intervene at any point.

[0113] When communication between the avatar and the caller (UE 2) is complete, the call ends, and the network delivers the caller's (UE 2) message and / or copy to the recipient's (UE 1's) inbox.

[0114] In an example implementation, an avatar (e.g., an AI-controlled avatar) can set or schedule callback times and dates. For example, an application programming interface (API) call to the recipient's calendar can allow the avatar to check, verify, and update the call recipient's availability. Different time slots can be suggested to the caller, or the caller can suggest their preferred callback time and date. If the requested time slot is available, a callback can be scheduled (using the API). Otherwise, another date and / or time can be suggested. This can continue until a suitable time and date are found.

[0115] Figure 8 A more detailed map illustrating the sequence of method 100 is shown. Identical components and features have the same reference numerals. Both the subscriber (caller) of UE1 and the subscriber (caller) of UE2 are licensed to use the avatar calling function. These licenses are recorded in the home network component (UDR / UDM) with reference to each subscriber identifier.

[0116] System 300 can generate a response to the voice of a caller who is the avatar caller. MF 370 can generate streaming avatar data, which presents these responses in the form of generated avatars. This is achieved using natural language processing and artificial intelligence / machine learning (AI / ML) technologies. Figure 9 The diagram illustrates the process of a voice response from UE2 (the caller), which uses AI / ML for decoding and processing to provide the caller with follow-up responses, as delivered by the avatar.

[0117] This method and system can be implemented using hardware, software, or a combination of both. It can be implemented as a server comprising a single computer system, or as a distributed network of servers spanning a network connection. Any type of computer system or other electronic device can be adapted to perform the described method.

[0118] As used throughout this document, including in the claims, unless the context otherwise indicates, the singular form of a term herein shall be construed as including the plural form, and vice versa. For example, unless the context otherwise indicates, singular references included in the claims, such as “a” or “an,” mean “one or more.” Throughout the description and claims of this disclosure, the words “comprising,” “including,” “having,” and “containing,” as well as variations of these words, such as “including” and “comprising,” or similar expressions, mean “including, but not limited to,” and are not intended to (and will not) exclude other components. Furthermore, the use of “or” is inclusive, such that the phrase “A or B” is true when “A” is true and “B” is true, or when both “A” and “B” are true.

[0119] The use of any and all examples or exemplary language (“for example,” “such as,” “e.g.,” and similar language) provided herein is intended merely to better illustrate this disclosure and, unless otherwise claimed, does not indicate a limitation on the scope of this disclosure. Nothing in this specification should be construed as indicating that any unclaimed element is necessary for the practice of this disclosure.

[0120] The terms "first" and "second" may be reversed without altering the scope of this disclosure. That is, an element referred to as a "first" element may be referred to as a "second" element, and an element referred to as a "second" element may be considered as a "first" element.

[0121] Any steps described in this specification may be performed in any order or simultaneously unless otherwise stated or required by the context. Furthermore, the fact that a step is described as being performed after another step does not preclude the execution of intermediate steps.

[0122] It should also be understood that, for any given component or embodiment described herein, any of the possible candidates or alternatives listed for that component may generally be used alone or in combination with each other, unless implicitly or explicitly understood or otherwise stated. It will be understood that any such list of candidates or alternatives is merely illustrative and not restrictive, unless implicitly or explicitly understood or otherwise stated.

[0123] Unless otherwise described, all technical and scientific terms used throughout this document have the meanings commonly understood by one of ordinary skill in the art to which the various embodiments described herein pertain.

[0124] As will be appreciated by those skilled in the art, the details of the above embodiments may vary without departing from the scope of the invention as defined by the appended claims.

[0125] For example, although only one or two devices (UEs) are shown and described, any number of devices may exist in a communication system with similar functions.

[0126] Furthermore, any network component and server can be replicated to provide load balancing or redundancy. Avatars can take any form and are not limited to human appearance. For example, different (or identical) avatars can speak different languages.

[0127] Many combinations, modifications, or variations of the features of the above embodiments will be apparent to those skilled in the art and are intended to form part of this invention. Any feature described specifically relating to one embodiment or example may be used in any other embodiment by making appropriate changes.

Claims

1. A communication method, comprising: A call is received at a first user equipment (UE), wherein the call originates from a second UE; Receive the choice of avatar at the first UE; The first UE sends the avatar identifier of the selected avatar to the data channel DC application server; The DC application server sends the avatar identifier as part of a request for avatar definition data to the avatar storage location; The avatar storage location retrieves the avatar definition data based on the avatar identifier; The avatar storage location sends the avatar definition data to the DC application server; The DC application server sends the avatar definition data to the media function MF. The MF generates avatar stream data based on the avatar definition data; as well as The MF sends the avatar stream data to the second UE.

2. The method of claim 1, further comprising registering the avatar before receiving the call.

3. The method of claim 1 or 2, wherein during the call with the second UE, the avatar stream data is rendered to generate the interaction between the avatar and the second UE.

4. The method of claim 3, wherein the interaction includes a response to a query within the call of the second UE.

5. The method of claim 3 or 4, wherein the interaction includes a request to obtain the reason for the call.

6. The method according to any one of claims 3 to 5, wherein the interaction includes a proposal to call back the second UE.

7. The method of claim 6 further includes consulting the calendar of the user of the first UE to determine the available time and date of the callback.

8. The method of claim 7, wherein the rendered avatar presents to the user of the second UE during the call a proposal of the determined available time and date of the callback.

9. The method of claim 8, wherein when the rendered avatar receives an indication from the user of the second UE during a call to reject the proposed time and date of the callback, the rendering of the avatar proposes an alternative time and date to the user of the second UE during the call.

10. The method of claim 8 or 9, further comprising the rendered avatar receiving, during the call, an indication from the user of the second UE to accept the proposed call-back time and date, and in response, saving the call-back appointment at the accepted time and date in the user's calendar of the first UE.

11. The method according to any one of claims 3 to 10, further comprising providing a written description of the interaction and / or a summary of the outcome of the call.

12. The method of claim 11, wherein the written description is provided in real time during the interaction and / or at the end of the call.

13. The method according to any of the preceding claims further comprises receiving a request from a user of the first UE to intervene in the call, and in response to the request, suspending or stopping the merging of the avatar stream data in the call.

14. A user equipment (UE), comprising: One or more processors; as well as One or more memories storing computer-executable instructions that, when executed by the processor, cause the UE to: A call is received at the UE, which is a first UE, wherein the call originates from a second UE; Receive the choice of incarnation; and Send the avatar identifier of the selected avatar to the data channel DC application server.

15. A system comprising: One or more UEs according to claim 14; Data channel DC application server; Transform into a storage location; as well as Media Functions (MF) The DC application server is configured to send the avatar identifier as part of a request for avatar definition data to the avatar storage location. The avatar storage location is configured as follows: Based on the avatar identifier, the avatar definition data is retrieved, and The avatar definition data is sent to the DC application server. The DC application server is also configured to send the avatar definition data to the MF, and The MF is configured as follows: Based on the avatar definition data, avatar stream data is generated, and The avatar stream data is sent to the second UE.

Images