Method and device for managing avatar in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, the present disclosure provides a method and a device for managing an avatar in a wireless communication system. A disclosed embodiment provides a device and a method capable of effectively providing a service in a wireless communication system.

Description

Method and device for managing avatars in a wireless communication system

[0001] The present disclosure relates to the field of communications and to the operation of a terminal, a base station, and a core network. In particular, the present disclosure relates to an IMS (IP (Internet Protocol) Multimedia Subsystem) based avatar management method and apparatus.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band of 6G mobile communication technology; metamaterial-based lenses and antennas; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology to improve terahertz band signal coverage; as well as full-duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and Artificial Intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The disclosed embodiments aim to provide an apparatus and method capable of effectively providing services in a wireless communication system.

[0009] A method according to one embodiment of the present disclosure is characterized by comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

[0010] The disclosed embodiments provide an apparatus and a method capable of effectively providing services in a wireless communication system.

[0011] FIG. 1 is a diagram showing the structure of a wireless communication system that provides voice and video calls in a mobile communication network according to one embodiment of the present disclosure.

[0012] FIG. 2 is a diagram showing an example of an avatar processing block and an avatar media processing procedure according to one embodiment of the present disclosure.

[0013] FIG. 3 is a drawing for explaining an avatar storage according to one embodiment of the present disclosure.

[0014] FIG. 4 is a diagram illustrating IMS components based on the service-based architecture of 3GPP SA2 according to one embodiment of the present disclosure.

[0015] FIG. 5 is a diagram illustrating an avatar call procedure according to one embodiment of the present disclosure.

[0016] FIG. 6 is a diagram illustrating an avatar call procedure according to one embodiment of the present disclosure.

[0017] FIG. 7 is a drawing for explaining avatar model identification according to one embodiment of the present disclosure.

[0018] FIG. 8 is a drawing for explaining a procedure for providing an avatar model list according to one embodiment of the present disclosure.

[0019] FIG. 9 is a drawing for explaining an avatar model management method according to one embodiment of the present disclosure.

[0020] FIG. 10 is a drawing for explaining an avatar model management application according to one embodiment of the present disclosure.

[0021] FIG. 11 is a drawing for explaining an avatar call procedure according to one embodiment of the present disclosure.

[0022] FIG. 12 is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0023] FIG. 13 is a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0024] FIG. 14 is a block diagram illustrating the structure of a network entity according to one embodiment of the present disclosure.

[0025] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit the scope of other embodiments. A singular expression may include a plural expression unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as generally understood by those skilled in the art described in this disclosure. Terms used in this disclosure that are defined in a general dictionary may be interpreted as having the same or similar meaning as they have in the context of the relevant technology, and are not to be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure. In some cases, even terms defined in this disclosure are not to be interpreted to exclude the embodiments of this disclosure.

[0026] In the various embodiments of the present disclosure described below, a hardware-based approach is described as an example. However, since the various embodiments of the present disclosure include techniques using both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0027] Various embodiments are described in detail below with reference to the accompanying drawings. Furthermore, in describing the embodiments of this disclosure, specific descriptions of related known functions or configurations are omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the embodiments. Additionally, terms used below are defined considering their functions in the embodiments, and these may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0028] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions.

[0029] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to make the present disclosure complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims.

[0030] At this time, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0031] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For instance, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order according to their corresponding functions.

[0032] In this case, the term “part” as used in various embodiments of the present disclosure refers to a software or hardware component, such as an FPGA or ASIC, and the “part” may perform certain roles. However, the “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or may be configured to run one or more processors. Accordingly, as an example, the “part” may include components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and “parts” may be combined into a smaller number of components and “parts” or further separated into additional components and “parts.” In addition, the components and '~parts' may be implemented to play one or more CPUs within the device or secure multimedia card.

[0033] Preferred embodiments of the present disclosure are described in detail below with reference to the attached drawings. It should be noted that identical components in the attached drawings are indicated by the same reference numerals whenever possible. Furthermore, it should be noted that the drawings of the present invention attached below are provided to aid in understanding the present invention, and that the present invention is not limited to the forms or arrangements illustrated in the drawings. Additionally, detailed descriptions of known functions and configurations that may obscure the essence of the present invention will be omitted. It should be noted that in the following description, only the parts necessary for understanding the operation according to various embodiments of the present invention are described, and descriptions of other parts will be omitted so as not to distract from the essence of the present invention. Furthermore, the present disclosure describes various embodiments using terms used in some communication standards (e.g., 3GPP (3rd Generation Partnership Project)), but this is merely an example for illustrative purposes. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.

[0034] In the present disclosure, each of the phrases such as “A / B”, “A and / or B”, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “at least one of A, B, or C” may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first”, “second”, or “first” or “second” may be used simply to distinguish a component from another component and do not limit the components in any other aspect (e.g., importance or order).

[0035] In this disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and the components included in the network structure of FIG. 1 described below may refer to physical entities, or to software performing individual functions or hardware combined with software. Reference numerals denoted by Nx, such as N1, N2, N3, ... in the drawings, represent known interfaces between NFs in a 5G core network (CN). Based on the discussion above, this disclosure may provide a method and apparatus for effectively managing an avatar model required for an avatar call when performing an avatar call in a mobile communication system. Furthermore, this disclosure provides a method for a terminal to access an avatar model stored in a storage on a network in an IMS-based avatar call.

[0036] FIG. 1 is a diagram showing the structure of a wireless communication system that provides voice and video calls in a mobile communication network according to one embodiment of the present disclosure.

[0037] FIG. 1 illustrates an IMS (Internet Protocol Multimedia Subsystem; IP Multimedia Subsystem) architecture that a first terminal (user equipment 1; UE1) can use for real-time multimedia transmission and reception with a second terminal (UE2), and the functions of the components are described as follows. Of course, the IMS architecture is not limited to the examples below and may include more or fewer components.

[0038] According to one embodiment of the present disclosure, a P-CSCF (Proxy-Call Session Control Function) serves as the first point of contact in an IMS network and can handle communication between a user terminal and an IMS network. The P-CSCF processes SIP (Session Initiation Protocol) requests and responses and can forward a user's request to a S-CSCF (Serving-Call Session Control Function). The P-CSCF also performs authentication and security processing and can route the user terminal's request to an appropriate location in the IMS network. Additionally, the P-CSCF can support roaming functions in the network.

[0039] According to one embodiment of the present disclosure, a Serving-Call Session Control Function (S-CSCF) can manage and control user sessions. The S-CSCF routes SIP messages and can handle user registration and authentication. The S-CSCF can communicate with a Home Subscriber Server (HSS) to query user profiles and establish sessions. Additionally, the S-CSCF can provide interfaces with various application services to control and coordinate services.

[0040] According to one embodiment of the present disclosure, a Home Subscriber Server (HSS) may be a database that stores and manages user information within an IMS network. The HSS may manage user profiles, including user authentication, authorization, and location management. The HSS communicates with an S-CSCF to provide user information and may provide all essential information about the user.

[0041] According to one embodiment of the present disclosure, Unified Data Management (UDM) can provide a function for managing data related to user profiles in a 5G network. UDM is a network function designed according to 3GPP (3rd Generation Partnership Project) standards and can perform roles related to user profile management, session management, authentication and authorization, policy and rule enforcement, and data synchronization and distribution in a 5G core network.

[0042] According to one embodiment of the present disclosure, an IMS AS (Application Server) may be a server that provides various applications and services in an IMS network. The IMS AS supports various SIP-based application services and, through this, can provide various services to users, such as voice, video, and messaging services. It can communicate with an S-CSCF to process service requests and perform various functions necessary for providing services.

[0043] According to one embodiment of the present disclosure, a Data Channel Signaling Function (DCSF) can perform the function of managing signals related to a data channel in an IMS network. The DCSF can be used to initialize and control a data channel through which application data is transmitted. The functions provided by the DCSF may be functions for efficiently supporting real-time data transmission as well as multimedia services, particularly within an IMS network. One of the roles of the DCSF may be to establish a data channel. The establishment of a data channel may involve defining and setting parameters of the data channel using protocols such as the Session Initiation Protocol (SIP) or the Session Description Protocol (SDP). For example, this may include the channel type, bandwidth, transmission format, etc. Of course, it is not limited to the above examples. After establishing the data channel, the DCSF may continuously manage the data channel. This may include functions such as monitoring the channel status, maintaining the session, resetting, and terminating. Additionally, the DCSF may ensure stable data transmission by handling changes that may occur while the session is maintained.

[0044] According to one embodiment of the present disclosure, a DCAR (Data Channel Application Repository; DC Application Repository) may be a component that stores and processes user data in an IMS architecture. The DCAR may create a data channel (data transmission) for a user to use a data communication service, and user data or carrier applications stored in the DCAR may be transmitted to a user terminal via a DCSF and a Media Function (MF).

[0045] According to one embodiment of the present disclosure, a Media Function (MF) may be a functional element responsible for media streaming and processing within an IMS network. The MF processes media such as voice, video, and data, and can manage media streams in cooperation with a Media Gateway. This enables seamless media transmission and processing. The Media Function can process media streams generated from various services, such as calls, video streaming, and video conferencing. This ensures that multimedia data between users is transmitted in high quality and supports users in using the service in the intended manner.

[0046] According to one embodiment of the present disclosure, an IMS-AGW (IMS Access Gateway) may be a gateway that provides an interface between an IMS network and an external network. The IMS-AGW supports interoperability between the external network and the IMS network and converts and transmits SIP signals and media streams. This gateway can ensure seamless communication with the external network.

[0047] According to one embodiment of the present disclosure, a Data Channel Application Server (DCAS) may be a server that transmits various application data over a data channel as part of an IMS architecture. It is designed to efficiently handle data transmission as well as SIP-based multimedia sessions within an IMS network. The DCAS can manage the transmission of data other than media streams. This may include data in various formats, such as text, files, application-related data, and status updates. For example, it may provide functions such as sharing files during video conferences or synchronizing location information in real-time games. The DCAS establishes, maintains, and terminates sessions using SIP. It coordinates the configuration of the data channel through SIP messaging, thereby enabling bidirectional transmission of data. The DCAS supports various types of data formats. This may mean that the DCAS can be used in multiple applications and services. Examples may include real-time data synchronization for business applications, communication with IoT (Internet of Things) devices, or real-time chat applications. As part of the IMS architecture, the DCAS operates in integration with other IMS components. For example, session control can be performed in conjunction with CSCF, and user authentication and authorization management can be handled in conjunction with HSS.

[0048] Based on the aforementioned components, a UE according to one embodiment of the present disclosure may request a connection to a counterpart terminal as follows.

[0049] First, a UE can send a request to the P-CSCF via a Session Initiation Protocol (SIP) Invitation Message to establish a data channel with another UE. The SIP message may include media-related parameters and multiplexing requirements within the Session Description Protocol (SDP). Additionally, to utilize IMS data channel services, the UE may include an SDP offer containing bootstrap information within the SIP Invitation Message, along with an SDP offer for an existing video or audio session connection.

[0050] The P-CSCF can forward received SIP messages to the S-CSCF. The S-CSCF is a key functional element responsible for session control within the IMS network; it manages UE sessions and interacts with the associated application server (IMS AS). The S-CSCF can process messages, verify user authentication and authorization if necessary, and then forward the messages to the IMS AS. Upon receiving a SIP INVITE message containing SDP information, the S-CSCF can forward the contents of the bootstrap-related SDP offer to the IMS AS if the SIP INVITE message includes a bootstrap data channel SDP offer for a data channel service connection request. At this time, the S-CSCF can check whether the terminal or network supports IMS-DC based on the contents of the received bootstrap-related SDP offer. If both parties support the data channel, the S-CSCF may decide to forward information for the bootstrap data channel connection to the IMS AS.

[0051] Upon receiving a bootstrap-related SDP offer message from the S-CSCF, the IMS AS can first check with the HSS (home subscriber server) whether the relevant UE or subscriber can use the data channel service. If the user cannot use the data channel based on the user's user profile, the IMS AS can perform a multimedia telephony (MMTel) session setup operation without a data channel connection through the standard IMS process. Additionally, if the user cannot use the data channel-based service, the IMS AS can update the SIP INVITE message received from the S-CSCF by deleting the data channel (DC) related media information from the message, and then forward the updated SIP INVITE message to the S-CSCF.

[0052] The S-CSCF can forward a UE's data channel request to the IMS AS. The IMS AS is a node that performs various service logic and can initiate interactions with the DCSF and MF based on the data channel setup request. The IMS AS can analyze the request and initiate a signaling procedure to establish the data channel.

[0053] If the service user can utilize a service based on the IMS data channel, the IMS AS can communicate with the DCSF to perform data channel bootstrapping through a data channel call request as part of the signaling process for data channel setup. The IMS AS can select a DCSF by performing discovery and selection of a DCSF instance via the NRF (network repository function) based on the network operator's local configuration or information transmitted from the UE. Through the above process, the IMS AS can deliver a Session Event Control Notification (SessionEventControl_Notify) message containing information such as SessionEstablishmentRequestEvent, Session ID, CallingID, CalledID, SessionCase, Event initiator, MediaInfoList, and DC Stream ID to the DCSF selected. The DCSF is responsible for the setup, management, and control of the data channel and can generate and deliver necessary SIP / SDP (Session Description Protocol) signaling messages. The DCSF can set data channel parameters in accordance with the request from the IMS AS and manage the process to ensure that the data channel is correctly configured on the counterparty terminal side as well. In addition, DCSF can determine MDC1 media information so that the UE can download applications through MF or MRF (Media Resource Function).

[0054] Based on the determined MDC1 media information, the DCSF can send a MediaControl_MediaInstruction message containing information such as SessionID and MediaInstructionSet to the IMS AS. The DCSF can send the MDC1 media endpoint address, DC stream ID, and alternative information for the URL (uniform resource locator) of the application list delivered from the MDC1 interface to the IMS AS by including it in the MediaInstructionSet. Based on this, the DCSF can provide the IMS AS with a policy regarding how the originating and terminating sides can create bootstrap data channels using MF.

[0055] IMS AS can select an MF by using NRF to search for and select an MF instance or enhanced MRF that supports local settings or DC media functions.

[0056] The IMS AS can transmit a list of Media Termination Descriptors to the selected MF via the Nmf_MRM_Create message. The IMS AS may request the creation of two different Media Terminations. One Media Termination information may be related to local bootstrap media, and the other may be related to remote bootstrap media to be provided to a remote UE. Each Media Termination may include information regarding resource allocation requests for the Mb and MDC1 interfaces. The MF may transmit the result of the negotiation of the corresponding data channel media resource information to the IMS AS.

[0057] After completing signal processing of the data channel based on MF information received from the IMS AS, the DCSF can communicate with the Media Function (MF) for processing the media stream. The MF can perform the role of processing the actual media data (e.g., audio, video, etc.) to be transmitted through the data channel. The MF can prepare necessary tasks such as transcoding, mixing, and conversion of the media stream, and can establish the data transmission path. The MF can ensure stable data transmission by performing QoS (quality of service) management and security functions.

[0058] When the DCSF and MF successfully establish a data channel, the IMS AS can send a SIP INVITE message to the S-CSCF containing an updated SDP offer with media information added from the MF or enhanced MRF. The S-CSCF can forward the received SIP INVITE message containing the updated SDP offer to the remote network and UE#2. Once the data channel is established, data transmission between the UE and the counterpart terminal begins. The data channel is connected between the UE, the MF, and the counterpart terminal, and the MF can transmit data in real time while processing media data and performing necessary conversion operations.

[0059] The following is a description of the general 3GPP SA2 architecture.

[0060] NF (Network Function) refers to a network function and may refer to a logical entity that performs a series of functions necessary to provide a specific network service. In this disclosure, NF may be used interchangeably with network entity. NFs form part of network infrastructure and can often be virtualized and run in a cloud environment.

[0061] The Network Repository Function (NRF) refers to the network repository function, which is responsible for storing and managing information about all NF instances within a network. The NRF can determine how NFs are deployed and connected within the network.

[0062] When an NF is generated, it must be registered with the NRF, and the registration process usually follows the order below. Of course, the following examples are not limited, and the order of the registration process may change.

[0063] - The newly created NF sends a registration request to the NRF.

[0064] - The NRF checks the information of the corresponding NF and requests additional information if necessary.

[0065] - The information that NF provides to NRF includes the type of NF, the services provided, the required resources, etc.

[0066] - An NRF stores information about an NF and provides connection information with other NFs that require that NF.

[0067] When registration is complete, the NRF sends a registration completion message to the NF, and the NF is now ready to operate within the network.

[0068] IMPU (IMS Public Identity) is a public identifier used in the IP Multimedia Subsystem (IMS). The IMS is a system that provides various IP-based multimedia services, such as voice, video, and messaging, and the IMPU can be used to distinguish users utilizing these services.

[0069] IMPUs typically use the 'tel:' URI scheme and often follow a phone number format. For example, an IMPU of the form '+821012345678' represents the Korean country code 82 and the mobile phone number 1012345678.

[0070] However, IMPU does not refer solely to a phone number. IMS supports various types of devices, and each of them can have a unique IMPU. For example, not only smartphones but also tablets, laptops, and desktop computers can utilize multimedia services through IMS, and each device acquires its own IMPU.

[0071] However, just because the IMPU is similar to the phone number format, existing phone numbers are not used as is. IMS is an IP-based system that uses a network separate from the existing telephone network. Therefore, a separate IMPU must be allocated from the existing phone numbers.

[0072] In summary, IMPU is a public identifier that identifies users on IMS and can take various forms in addition to the phone number format. However, even though IMPU has a form similar to a phone number, it is assigned separately from existing phone numbers and can only be used on an IP-based network called IMS.

[0073] PSI (Public Service Identifier) ​​can be used to distinguish instances of the Media Function of 3GPP SA2.

[0074] A PSI can typically be allocated during the creation or initialization phase of an MF instance. The allocated PSI can be stored as part of the MF instance and used to communicate with external systems as needed. For example, if an MF wants to interact with the IP Multimedia Subsystem (IMS), the MF passes its PSI to the IMS, and the IMS can use it to identify and manage the MF.

[0075] Bootstrap Data Channel: A data channel established within an IMS session between the UE and the network, capable of transmitting a graphical user interface that may include a list of data channel applications.

[0076] Data Channel Application: An HTML page containing JavaScript and optionally images and style sheets. It can be downloaded from the network to the UE via the Bootstrap data channel.

[0077] FIG. 2 is a diagram showing an example of an avatar processing block and an avatar media processing procedure according to one embodiment of the present disclosure.

[0078] Referring to FIG. 2, avatar processing blocks that can be considered to represent a user's facial expressions or gestures as an avatar are indicated by gray blocks, and the processing procedures between the avatar processing blocks and the avatar media, which are the main inputs and outputs, are indicated by white blocks. Each process can be executed in a UE, a network, or a remote UE, and the execution location of each process can be determined as a result of a separate judgment and negotiation process. For example, when executed in a network, it may be executed in a media function (MF) within the network, but is not limited thereto.

[0079] According to one embodiment of the present disclosure, an avatar model (Base Avatar) is information for representing a user, and the user can express their facial expressions, posture, etc. by selecting at least one of one or more avatar models in an avatar call.

[0080] According to one embodiment of the present disclosure, a reference avatar model is a basic model representing a human, and the characteristics of the user can be described as differences based on the reference avatar model.

[0081] According to one embodiment of the present disclosure, captured data may refer to information such as video, audio, or motion sensor data based on the acquired facial expression and / or posture of a user. For example, if User A causes an avatar mimicking their facial expression and posture to be displayed on a Remote UE, User A's terminal may acquire User A's facial expression and posture to generate captured data.

[0082] If a pre-generated Base Avatar is not available, the user can record key facial expressions, dialogue, etc., following the guides in the Avatar app. The captured data of the recorded actions can be fed into the Base Avatar Generation unit to be generated as a Base Avatar. Since the Base Avatar has various options depending on the solution and quality, ranging from real-time processing to post-processing that takes several hours, it is common for it to be generated and stored in advance before an avatar call. Of course, the method of generating the Base Avatar is not limited to the above examples.

[0083] According to one embodiment of the present disclosure, an Avatar Storage (Base Avatar Repository) serves to store a Base Avatar and provide it upon request. For example, when users A and B make an Avatar call, the Avatar Storage may be the local storage of user A's terminal (UE), a storage on a mobile communication network (IMS) that mediates the Avatar call, a storage of an OTT (over the top) operator that mediates an OTT Avatar call using the mobile communication network, or the local storage of user B's terminal (Remote UE) that has previously made an Avatar call with user A.

[0084] According to one embodiment of the present disclosure, animation data is generated from captured data and may be information or commands for moving the Base Avatar in accordance with the user's movements. Depending on the technology applied to the Base Avatar, the technology applied to the animation data may vary. For example, if the Base Avatar is a generative AI model, the animation data may be a long text description (prompt) that the AI ​​model allows. As another example, if the Base Avatar is a 3D graphic model, the animation data may be a sequence of XYZ coordinate movement information for moving each point of a graphic object. Of course, the above examples are not limited.

[0085] Therefore, the Animation Data Generation unit that generates Animation Data can communicate with Avatar Animation and Avatar Storage to determine whether the technology applied to the Base Avatar and the Avatar Animation can support the corresponding technology (technology applied to the Base Avatar).

[0086] According to one embodiment of the present disclosure, an Animated Avatar is a Base Avatar modified according to the instructions of Animation Data. As a result of the modification, User A's Animated Avatar may mimic User A's posture and facial expressions. The Animated Avatar may belong to a Scene containing objects representing virtual or real space, along with Users A and B, or other users. According to one embodiment of the present disclosure, a Renderer may generate a Rendered Scene such that a projection plane at a position determined by considering the location of a specific user, for example, the relative position of User B and the Remote UE with respect to the Scene, constitutes all or part of the Remote UE's Display.

[0087] Captured data, Base Avatar, Animation data, Animated Avatar, Scene, and Rendered Scene applied to and generated from the processing blocks described above are collectively referred to as Avatar Media in this disclosure. In the description of various embodiments of this disclosure, Avatar Media may include at least one of Captured data, Base Avatar, Animation data, Animated Avatar, Scene, and Rendered Scene. Unless specifically stated otherwise, in the description of various embodiments of this disclosure, Media may be Avatar Media.

[0088] FIG. 3 is a drawing for explaining an avatar storage according to one embodiment of the present disclosure.

[0089] According to one embodiment, the Base Avatar Repository (BAR) may be connected to DCSF, which is one of the components of the IMS architecture as shown in FIG. 3, or to DCAS, or to a third IMS architecture component.

[0090] According to one embodiment of the present disclosure, if the entity requesting the avatar repository is an MNO service component excluding DCAS among the components within the IMS architecture, the avatar repository can be created in the DCSF and placed under the DCSF or a third component.

[0091] If the entity requesting the avatar repository is DCAS, DCAS can create the avatar repository and place it under DCAS or a third component.

[0092] Additionally, according to one embodiment of the present disclosure, the avatar storage may communicate directly with any component, but if configured to be connected to a DCSF, it may be created or deleted through the DCSF. Additionally, if the avatar storage is configured to be connected to a DCAS, it may be created or deleted through the DCAS.

[0093] According to one embodiment of the present disclosure, a Base Avatar Cache (BAC) can store information stored in a BAR. For example, a Base Avatar Cache may be used to temporarily copy an avatar model and then allow it to be accessed by an MF or terminal. MFs related to avatar calls include Base Avatar generation, Animation Data generation, Avatar animation, Scene management, etc. If MFs related to avatar calls access the BAC without passing through DCSF, DCAS, etc. every time, only the avatar model related to the avatar call can be exposed. In addition, the BAC and BAR can be operated separately by providing a decision step to determine whether to apply a series of modifications to the avatar model that may occur during a call to the avatar model stored in the BAR, based on whether the modifications are limited to the current call or will also be applied to future calls.

[0094] FIG. 4 is a diagram illustrating IMS components based on the service-based architecture of 3GPP SA2 according to one embodiment of the present disclosure.

[0095] According to one embodiment, an avatar repository can be created as a Network Function (NF) and then registered in an NRF. An NF or MF that wishes to use the avatar repository, i.e., an avatar repository consumer, may request the NRF to search for the avatar repository or a corresponding data channel application repository and receive information about the avatar repository in response.

[0096] According to one embodiment of the present disclosure, an avatar repository may register to the NRF during the creation process as an NF that it can serve as an avatar repository or a data repository for a data channel application. The avatar repository and the data channel application data repository may be managed and identified as different attributes.

[0097] Additionally, according to one embodiment of the present disclosure, an avatar repository may also be registered with the NRF by the entity that commissioned its creation. For example, if the DCSF creates it, the DCSF may register it. If the DCAS creates it, the DCAS may transmit the creation and registration results of the avatar repository connected to the DCAS to the NRF and the DCSF.

[0098] According to one embodiment of the present disclosure, when an avatar repository can be accessed only through a DCSF or DCAS, the DCSF or DCAS may be registered in an NRF as having the function of an avatar repository. That is, in this case, the NF received as a search result from the NRF by searching for the avatar repository may actually be a DCSF or DCAS. Thus, the DCSF or DCAS may have the attributes of an avatar repository or a data channel application data repository.

[0099] Additionally, according to one embodiment of the present disclosure, an avatar storage consumer may also request the DCSF to retrieve an avatar storage or a corresponding data channel application storage.

[0100] FIG. 5 is a diagram illustrating an avatar call procedure according to one embodiment of the present disclosure.

[0101] According to one embodiment, the terminal can request an avatar call from the IMS AS by specifying the avatar model to be used for the avatar call.

[0102] In Step 1, the terminal creates a call request called SIP and sends it to the CSCF of the IMS architecture, and the CSCF can send the call request to the IMS AS.

[0103] In Step 2, the IMS AS may inquire with the DCSF whether the avatar model of the identifier is stored in the avatar store when the identifier of the avatar model is specified in a call request identified as an avatar call. The inquiry may include identifying information such as the identifier of the avatar model.

[0104] In step 3, the DCSF receives identification information of the avatar model that the terminal and the user intend to use in an avatar call, and can search the avatar storage where the avatar model of the identification information is stored.

[0105] In step 4, the DCSF can search all avatar repositories connected to the DCSF, avatar repositories connected to the DCAS, or avatar repositories connected to a third component to determine whether an avatar model is stored. The search may be performed by transmitting identification information of the avatar model and receiving a list of whether it is held or access paths.

[0106] In step 5, the Avatar Repository may respond to a request from the DCSF using the Avatar identifier to be searched by simply in the form of True / False, or return a path to access the Avatar model such that it is displayed as an internal path within the Avatar Repository or an external path including the Avatar Repository.

[0107] In step 6, depending on the case, when there are multiple avatar models with the same avatar identifier (e.g., different versions), the response from the avatar repository may be returned as a list of internal or external paths to the avatar repository containing version information.

[0108] In step 7, DCSF can request a list of avatar models from the avatar repository and, after receiving the list from the avatar repository, search to see if the avatar model to be found is included.

[0109] In step 8, DCSF can respond to an inquiry from IMS AS regarding whether the avatar model received as a result of the search or from the list is saved.

[0110] In step 9, when the response from the avatar repository is a path within the avatar repository, the DCSF may append additional paths based on the location of the avatar repository. For example, when the first avatar repository is connected to the DCSF and the second avatar repository is connected to the DCAS, the DCSF may append additional paths that identify the avatar repository, such as / DCSF / BAR1 / AVATAR_CALL / User_000000 / Model_abcd1111, to the path of the avatar model received from the first avatar repository, / AVATAR_CALL / User_000000 / Model_abcd1111, thereby creating and managing a path such as / DCSF / BAR1 / AVATAR_CALL / User_000000 / Model_abcd1111. Similarly, when the second avatar repository is connected to DCAS, DCSF can create and manage paths for avatar models received from the second avatar repository, such as / DCAS / BAR2 / AVATAR_CALL / User_000000 / Model_abcd1111.

[0111] In step 10, if the avatar store has a unique path and the connection to DCSF or DCAS is not specified, / DCSF, / DCAS, etc. may be omitted from the path.

[0112] FIG. 6 is a diagram illustrating an avatar call procedure according to one embodiment of the present disclosure.

[0113] According to one embodiment, the terminal may request an avatar call without specifying the avatar model to be used.

[0114] In Step 1, the terminal creates a call request called SIP and sends it to the CSCF of the IMS architecture, and the CSCF can send the call request to the IMS AS.

[0115] In Step 2, when the identifier of an avatar model is not listed in a call request identified as an avatar call, the IMS AS may inquire with the DCSF for a list of avatar models allowed to the user or the user’s IMPU.

[0116] In step 3, the DCSF can query the avatar repository for a list of avatar models allowed to the terminal and user.

[0117] In Step 4, within the avatar repository, avatar models may exist under specific user or public user folders. For example, if there is a specific user with identifier 000000, that user's avatar model may exist under a folder such as User_000000. Additionally, avatar models for public users may exist under the common folder.

[0118] In step 5, the avatar models stored under the user folder can be provided as a list of avatar models that the user can use.

[0119] In step 6, the avatar models stored under the common folder can be provided as a list of avatar models available for use by all users.

[0120] In Step 7, a specific user folder may exist under a folder for a specific service, provided that the user is subscribed to that service. For example, assuming there is a specific service with the identifier service_001, a user folder named User_000000 may exist under a folder named service_001.

[0121] In Step 8, a specific service may have a folder provided to all service users. For example, if there is a common folder under the service identifier, that is, avatar models stored under a folder named service_001 / common may be provided as a list of avatar models that all service users can use.

[0122] In step 9, the DCSF may use a data channel application to generate a list of avatar models available to the user from the aforementioned folders and to allow the user to select one.

[0123] In step 10, DCSF may respond to IMS AS that it can provide a list of one or more avatar models that the user can select.

[0124] In step 11, the IMS AS may instruct the terminal to request a call request that includes the establishment of a bootstrap data channel.

[0125] In step 12, the terminal transmits a call request to the IMS AS requesting the establishment of a bootstrap data channel, and the IMS AS may request the DCSF to create or retrieve an MF for transmitting a bootstrap application.

[0126] In step 13, the DCSF can transmit access information of the generated or retrieved MF to the terminal via the IMS AS.

[0127] In step 14, the terminal can establish a bootstrap data channel with MF.

[0128] In step 15, the bootstrap application can be transmitted from the DCSF to the terminal via the MF.

[0129] In step 16, the terminal can run a bootstrap application to receive a list of avatar models.

[0130] In step 17, the terminal's bootstrap application can select an avatar model and request to use the call.

[0131] In step 18, MF can receive the selected avatar model from the avatar repository and transmit it to the counterpart terminal or configure it for use in avatar processes (animation data generation, animated avatar generation, scene generation, etc.) within the avatar reference architecture.

[0132] FIG. 7 is a drawing for explaining avatar model identification according to one embodiment of the present disclosure.

[0133] According to one embodiment, differences between avatar models that cannot be identified solely by the avatar model identifier can be distinguished and identified.

[0134] According to one embodiment of the present disclosure, the avatar model previously received by the terminal and the avatar model stored in the avatar repository may have been changed in whole or in part. For example, the terminal may have improved the user's own avatar model, or the network may have upgraded the reference avatar model for the avatar models. Therefore, it is not possible to determine whether the avatar model that the user intends to use matches or does not match the avatar model in the avatar repository based solely on the identifier of the avatar model.

[0135] To improve this, the avatar model may contain additional information as metadata in addition to its identifier. The metadata may include the avatar model's version information, profile, MD5, total file size, and update and access date information. Of course, it is not limited to the examples above. Additionally, the metadata may include the structure and list of sub-data constituting the avatar model. Each sub-data may include the sub-data's version information, identifier, MD5, size, and update and access date information. Of course, it is not limited to the examples above.

[0136] According to one embodiment of the present disclosure, a terminal may describe and display the terminal's performance in relation to avatar calls as a profile. For example, performance information such as AR glasses, whether 3D stereoscopic images can be acquired, and 3D stereoscopic image formats may be defined as a profile. Since the avatar model may or may not operate depending on the profile, the available terminal profiles may be described within the metadata of the avatar model.

[0137] In addition, according to one embodiment, when sub-data constituting an avatar model is changed, it is a principle that not only the version information of the sub-data but also the version information of the avatar model is changed. That is, it is possible to determine whether two avatar models are identical or not solely by the identifier and version information of the avatar model. When they are not identical, the version information of the sub-data within the metadata may be referenced to determine which sub-data is not identical. When the versions of the avatar models are not identical, the version information of at least one sub-data may not be identical. Through this, between the terminal and the avatar storage, it is possible to identify one or more sub-data that must be updated to make two different avatar models, identified as having the same identifier but different versions, into avatar models having the same identifier and the same version information, and to identify sub-data that is identical even if not updated.

[0138] According to one embodiment, version information may be added to an access path for an avatar repository having one or more versions of an avatar model. For example, it may be added as avatar_path / avatar_model_identifier / version_information. Accordingly, a path to a specific version of the avatar model that the user and terminal intend to use may be responded to the terminal or avatar model consumer from the DCSF.

[0139] Additionally, according to one embodiment, metadata may be added to the access path to identify sub-data. For example, a path may be added such as Avatar_Path / Avatar_Model_Identifier / Version_Information / Metadata. Accordingly, when the terminal receives one or more version information and a corresponding path list for a requested Avatar Model Identifier, it may receive a list of sub-data constituting the version and the identifier and version information of each sub-data. The terminal may decide to update only all or part of the sub-data to configure the same version in the terminal or the Avatar Storage and may perform the update.

[0140] For example, if some sub-data is changed due to an update within the terminal, the version of the sub-data and the version of the avatar model can be updated, and only the changed sub-data can be transferred to the avatar storage to ensure they are the same version.

[0141] Subordinate data may be added to the access path to access only the subordinate data. Since subordinate data can also have identifiers and version information, it may be added as follows: Avatar_Path / Avatar_Model_Identifier / Version_Information / Subordinate_Data_Identifier / Subordinate_Data_Version_Information. Accordingly, when the version information changes, the terminal can configure an access path to receive the changed data among the subordinate data and make a request.

[0142] A data channel can be established and connected for the exchange of avatar lists and data between the above terminal and the avatar storage.

[0143] The terminal may specify Avatar Call as the call service type. In this case, a related bootstrap application may be provided to or downloaded to the terminal based on conditions derived from the contents specified in the Avatar Call request or according to an explicit request.

[0144] FIG. 8 is a drawing for explaining a procedure for providing an avatar model list according to one embodiment of the present disclosure.

[0145] According to one embodiment, an application that provides a list of avatar models available for use on a terminal may be provided.

[0146] In Step 1, when no avatar model is specified in the avatar call request transmitted from the terminal, the DCSF may aggregate and provide a list of avatar models stored in the user's avatar storage and service-common avatar models to be used in the avatar call.

[0147] In step 2, even if an avatar model is specified in the avatar call request transmitted from the terminal, if one or more avatar models are found or if the specified avatar model is not found, a bootstrap application may be provided to and downloaded to the terminal.

[0148] In step 3, an avatar model list request may be included in the avatar call request transmitted from the terminal. If avatar call is specified as the call service type and avatar_model_list_request is specified as an additional attribute or a bootstrap data channel is requested, an application for providing a list of avatar models may be provided to and downloaded to the terminal.

[0149] In step 4, a data channel may be established for transmitting a list of avatar models and selecting an avatar model between the terminal and the IMS architecture. The data channel may be a bootstrap channel or an application channel.

[0150] In Step 5, when a bootstrap channel is established, an avatar list management application is downloaded and executed from the DCSF to the terminal via the MF, and the application on the terminal communicates with the MF, which has been delegated the list information of avatar models from the DCSF, to exchange lists and receive selection results from the terminal. The selected results are transmitted to the DCSF and IMS AS and can be used for session negotiation and transmission of avatar models to the counterparty terminal.

[0151] In Step 6, when the application channel is established, message exchange communication is initiated between the MF, which has been delegated the list information of avatar models from the DCSF, and the terminal. The terminal and the MF can transmit, receive, and select a list of available avatar models through the following messages.

[0152] A request message can be sent from an entity that wants to receive a list of avatars (e.g., a terminal) to an entity that can provide a list of avatars (e.g., an MF). Of course, it is not limited to the following examples.

[0153] message_type = avatar_model_list_request Indicates that the message is a request for a list of avatar models. ownership = 0 for subscriber only, 1 for common only, 2 for all available Indicates that 0 is for those owned by the service subscriber, 1 is a list of service-common avatars, and 2 is a list of all available avatars. profile If specified, only the list of avatars corresponding to that profile can be requested.

[0154] A response message may be sent from an entity capable of providing a list of avatars to the requesting entity. The message may contain the following information. Of course, it is not limited to the examples below.

[0155] message_type = avatar_model_list Indicates that the message is a list of avatar models number_of_avatar_model_for_subscriber Number of avatar models for the user number_of_avatar_model_for_common Number of avatar models for common users avatar_model Avatar model details - identifier Avatar model identifier - description Description provided by the user or service - version Version of the avatar model - owner Owner of the avatar model. The subscriber's identifier may be entered. - BAR_path Path to the avatar repository - BAC_path Path to the temporary avatar repository - Hero_image_path Path to the representative image or video. A data format that allows the form to be inferred before receiving the entire avatar model may be entered. - metadata_path Path to the metadata

[0156] A selection message can be used to determine and convey which avatar to select from the list of provided avatar models. The message may contain the following information. Of course, it is not limited to the examples below.

[0157] message_type = selected_avatar_model Indicates that the message is the result of selecting an avatar model. avatar_model_identifier Identifier of the selected avatar model avatar_model_version Version of the selected avatar model BAC_request Request to use BAC, the temporary avatar storage. May be requested if BAC_path is not provided.

[0158] The selection response message can be used as an acknowledgment for the avatar model's selection. The message may contain the following information. Of course, it is not limited to the examples below.

[0159] message_type = selection_acknowledged Indicates that the selection has been acknowledged. BAC_path A temporary avatar storage is provided if requested. error_code Used to indicate the status of the avatar model selection. OK indicates no issues, ERROR_BAC_FAILED indicates an error in saving the BAC, and WARNING_BAC_WAITING indicates that you must wait a moment before using BAC_path because it is being saved to the BAC.

[0160] FIG. 9 is a drawing for explaining an avatar model management method according to one embodiment of the present disclosure.

[0161] According to one embodiment, to manage an avatar model at a terminal, a CRUD (Create, Read, Update and Delete) application or an Echo play application, which is an avatar management application, may be provided.

[0162] According to one embodiment of the present disclosure, management such as creating an avatar model on a terminal, modifying an avatar model that has already been created, downloading an avatar model within the terminal, or deleting a created avatar model can be performed by a CRUD application.

[0163] Additionally, if you want to modify the avatar model on the device or test a new avatar model, you can use the Echo play application to make a call without a caller and check how the new avatar model behaves according to the user's gestures or facial expressions.

[0164] Since avatar calling is an enhanced form of voice or video calling in the IMS architecture, access to the IMS architecture is only possible after a session is established by making a call; however, because the aforementioned management applications may not have a counterparty, a method for making a call without a counterparty needs to be considered.

[0165] In one embodiment, the terminal may specify that the service type is an avatar call, in addition to being a solo call, as an additional attribute. The IMS AS is equipped with various bootstrap applications that can be provided to the terminal when the service type is an avatar call and the additional attribute is a solo call, and can transmit these to the terminal through a bootstrap data channel.

[0166] In addition, in one embodiment, the terminal may, in addition to the service type being avatar call, register the counterparty's IMPU as its own IMPU (IMS Public User Identity). That is, if a call request is registered as making an avatar call to itself and transmitted to the IMS AS, the IMS AS may provide various bootstrap applications that can be provided to the terminal when the service type is avatar call and the recipient is the same as the sender, and transmit these to the terminal through a bootstrap data channel.

[0167] In addition, in one embodiment, the terminal may, in addition to the service type being Avatar Call, list a Management Service Specific IMPU in the counterparty's IMPU. The Management Service Specific IMPU is an IMPU arbitrarily determined by the service for the purpose of managing the Avatar Model, and may be provided as one of the detailed items of communication service information that can be announced by the service during the terminal registration process. If the terminal supports Avatar Call, Avatar Call is listed as one of the available call types of the terminal and transmitted to the mobile communication service during the terminal registration process, and the mobile communication service may specify and transmit the Management Service Specific IMPU during the service information transmission process to the terminal. Alternatively, the mobile communication service may specify and transmit the Management Service Specific IMPU during the service information transmission process to the terminal without verifying the available call types of the terminal. The terminal attempts an Avatar Call by designating the Management Service Specific IMPU as the recipient, and the IMS AS recognizes this as a call for management purposes and can transmit various bootstrap applications to the terminal through the bootstrap data channel.

[0168] In one embodiment, a mobile communication service may generate an MF for management purposes in advance during the service provisioning stage. A Public Service Identifier (PSI) is assigned during the generation process as information for accessing the generated MF, and the PSI can be managed as a service-specific PSI.

[0169] In Step 1, the avatar call operator provides avatar call services through DCAS and may request DCSF to create an MF to provide management services during the service provision phase.

[0170] In step 2, DCSF can forward the request from DCAS to MF to create an avatar-managed MF and forward the PSI of the created MF to DCAS as a response.

[0171] In step 3, DCAS can store the received PSI as access information for the Avatar Management MF and transmit it as service information to the Avatar Call App of the terminal that intends to receive the Avatar Call Service.

[0172] In step 4, when the terminal requests avatar calling and management (where the caller and receiver are the same IMPU or explicitly request a solo call), the IMS AS requests the DCSF to establish a data channel, and the DCSF can check with the DCAS whether an MF for the corresponding service has already been created. The DCAS transmits the management PSI to the DCSF, and when the DCSF transmits the MF's PSI to the terminal via the IMS AS, the terminal can establish a data channel with the MF using the PSI.

[0173] In Step 5, when the terminal requests avatar call and management, the terminal may request by specifying a PSI. The IMS AS requests the DCSF to establish a data channel using the specified PSI, and the DCSF can check whether an MF corresponding to the PSI has already been created. After the IMS AS receives confirmation of the PSI from the DCSF, it instructs the terminal to establish a data channel, and the terminal can establish a data channel with the MF using the PSI.

[0174] Applications and MF can perform avatar model management using the following messages. Of course, they are not limited to the examples below.

[0175] message_type = avatar_model_create_request: This can be used by a terminal to request the creation of an avatar model from MF, which is a server on the network. Since the creation of an avatar model may require large-scale processing, the terminal acquires data for the creation of the avatar model, and MF can select from the data formats that the terminal can generate that are suitable for creating the avatar model. UE_device_profile: A performance profile of the terminal related to the avatar. For example, performance information such as AR glasses, the ability to acquire 3D stereoscopic images, and 3D stereoscopic image formats can be defined as a profile. The avatar model creation unit of MF identifies the data types that the terminal can generate based on the terminal's performance and, accordingly, can instruct the terminal to transmit data to MF. UE_resource_list: A list of data types that the terminal can generate.

[0176] message_type = avatar_model_create_responseMF can determine a reference avatar based on the avatar model creation request from the terminal and the data format that can be generated for the avatar model, and specify the corresponding data input format. reference_avatar_identifier The identifier of the reference avatar to be referenced when creating the avatar model. An individual's facial and physical characteristics may be listed in the form of differences from the reference avatar. reference_avatar_version The version of the reference avatar to be referenced when creating the avatar model. individual_templates_list Personalized templates. Types of data to be acquired to identify an individual's facial and physical characteristics. PSIMF access information. May be listed if it differs from the MF for CRUD.

[0177] message_type = avatar_model_create_data The terminal can acquire and store data acquired according to the instructions of the template, such as voice data recorded by reading short texts in which voice characteristics can be identified, image data of facial expressions acquired from various angles, image data of body degrees of freedom and joint characteristics acquired from various angles, etc., as instructed by the template. template_identifier Template identifier template_version Template version acquired_data Voice or image data acquired according to the instructions of the template

[0178] message_type = avatar_model_create_resultMF can create an avatar model based on input template data and notify the terminal of the creation result. avatar_model_identifier Identifier of the created avatar model avatar_model_version Version of the created avatar model avatar_model_path Access path of the avatar model stored in the avatar storage or temporary avatar storage avatar_model_metadata_path Access path of the metadata of the avatar model stored in the avatar storage or temporary avatar storage avatar_model_available_time Validity period of the avatar model path. The avatar model path may be invalidated after a certain period of time.

[0179] message_type = avatar_model_read_info_request The terminal can request information to access an avatar model based on the identifier and version information of a specific avatar model. avatar_model_identifier Avatar model identifier avatar_model_version Avatar model version

[0180] message_type = avatar_model_read_info_responseMF allows providing path information for accessing the avatar model and path information for accessing only the avatar model's metadata. avatar_model_path Storage path of the avatar model avatar_model_metadata_path Storage path of the avatar model's metadata

[0181] message_type = avatar_model_read_request A request can be made to receive an avatar model from the terminal. path avatar_model_path or avatar_model_metadata_path may be specified. requested_range Data is requested within the range (start position, size). Less data may be received than the requested size.

[0182] message_type = avatar_model_read_response The requested data for the avatar model avatar_model_data from DCSF is transmitted from the avatar repository or BAC.

[0183] message_type = avatar_model_update_request Used to update a part of the avatar model on the terminal. Avatar model updates can be requested and applied at the sub-data level. MD5 is provided to transmit a validation value for the data prior to upload, allowing the receiving side to confirm that there are no issues with the received data. avatar_model_identifier Identifier of the target avatar model to be updated avatar_model_version Version of the target avatar model to be updated avatar_model_md5 MD5 validation result of the target avatar model to be updated avatar_model_data_identifier Identifier of the sub-data of the target avatar model to be updated avatar_model_data_version Version of the sub-data of the target avatar model to be updated avatar_model_data_md5 MD5 validation result of the sub-data of the target avatar model to be updated avatar_model_data_source Location of the sub-data of the original avatar model to be updated avatar_model_data_target Location of the sub-data of the target avatar model to be updated. It is copied from the location of the original avatar sub-data to the location of the target avatar sub-data.

[0184] message_type = avatar_model_update_responseMF is used to receive the avatar model and notify the result of the reception. error_codeOK indicates that there is no problem with receiving the data. ERROR_AVATAR_MODEL: indicates that an error occurred in the avatar model operation due to the received data. ERROR_MD5 indicates that the value of the MD5 validation code for the received data is inconsistent. ERROR_NOT_ALLOWED indicates that there is no access permission to modify the received data.

[0185] message_type = avatar_model_delete_request avatar_model_identifier: Identifier of the avatar model to be deleted avatar_model_version: Version of the avatar model to be deleted

[0186] message_type = avatar_model_delete_responseerror_codeOK indicates that the avatar model deletion was successful. ERROR_OCCUPIED indicates that there is another user using the avatar model. ERROR_NOT_ALLOWED indicates that there is no deletion access permission for the received data.

[0187] FIG. 10 is a drawing for explaining an avatar model management application according to one embodiment of the present disclosure.

[0188] In one embodiment, the application and MF can perform avatar calls using an avatar repository between the media layer architecture and the IMS architecture. Of course, the network of FIG. 10 including the application and MF is not limited to the illustrated example.

[0189] FIG. 11 is a drawing for explaining an avatar call procedure according to one embodiment of the present disclosure.

[0190] In Step 1, the terminal may specify an avatar call as the call service type. The terminal may specify an avatar model to be used in the avatar call, and the specification of the avatar model may be achieved by writing identification information including an identifier and a version. The terminal's avatar call request may include a request to open a data channel.

[0191] In Step 2, IMS AS can inquire with and determine whether the terminal and the terminal user have access to the data channel in response to an avatar call request and a data channel opening request from the terminal.

[0192] In step 3, if the data channel is available and the identifier and version of the avatar model are specified, the DCSF can search for whether there is an avatar model of that identifier within the IMS architecture.

[0193] In step 4, DCSF can reply with the requested avatar model as a path list if it exists.

[0194] In step 5, or the DCSF may decide to create a Base Avatar Cache (BAC) for the purpose of supporting avatar calls to the MF, and configure the created BAC to read data from the avatar cache path and cache avatar models. The BAC may be used to offset the security risks associated with original access and the risk of accidental deletion of the original, and to make it difficult to access other avatar models accessible along the path. In this case, the DCSF returns the BAC path, rather than the avatar cache path, to the terminal. The BAC path may be randomized to make it difficult for other users to infer.

[0195] In step 6, MF can generate a BAC and instruct it to receive an avatar model of a specified path. The path of the avatar model to be cached can be generated by randomizing.

[0196] In step 7, the BAC can cache the specified avatar model after it is created.

[0197] In step 8, MF can pass the generated BAC and the path of the avatar model in the BAC to DCSF as a response.

[0198] In Step 9, DCSF can reply to IMS AS with the avatar path within BAC.

[0199] In step 10, the IMS AS may return to the terminal access information for establishing a data channel with the MF and / or BAC, and the avatar model path in the MF or BAC of the avatar model, and instruct the establishment of a data channel.

[0200] In step 11, the terminal establishes a data channel with the MF and the BAC. The data channel between the BAC and the terminal can be direct or via the MF.

[0201] In step 12, if BAC is not created, the transmission of the avatar model can be done via MF from BAR.

[0202] In step 13, the counterparty terminal, having received information about the avatar model to be used for the data channel and call from the IMS AS, can open a data channel to receive this from the BAR.

[0203] In step 14, the avatar model can be transmitted to the counterparty terminal.

[0204] In step 15, if a BAC is created, the avatar model can be transmitted from the BAC. If not all data is cached in the BAC, the data can be transmitted from the BAR to the BAC and then from the BAC to the terminal.

[0205] In step 16, the counterparty terminal, having received information from the IMS AS regarding the data channel and the avatar model to be used for the call, can open a data channel to receive this from the BAC.

[0206] In step 17, the avatar model can be transmitted to the counterparty terminal.

[0207] In Step 18, if an avatar model in the BAC is modified by a call management application or a call application, etc., the owner of the avatar model may use avatar_model_update_request to instruct the avatar model in the BAC to reflect the modifications in the avatar model in the BAR. The location of avatar_model_data_source can be a path in the BAC and the location of avatar_model_data_target can be a path in the BAR.

[0208] In Step 19, the avatar model can be updated from BAC to BAR.

[0209] In step 20, the avatar call may be terminated by the terminal or the other party's terminal.

[0210] In step 21, the IMS AS notifies the DCSF of the end of the call, and the DCSF may instruct the BAC to delete the avatar model used in the call or release the avatar call session identifier to instruct the BAC to delete the avatar model corresponding to the avatar call session.

[0211] In step 22, BAC can delete the avatar model.

[0212] FIG. 12 is a block diagram illustrating the structure of a terminal (User Equipment, UE) according to one embodiment of the present disclosure.

[0213] As illustrated in FIG. 12, the terminal of the present disclosure may include a processor (1220), a transceiver (1200), and a memory (1210). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. In addition, the processor (1220), the transceiver (1200), and the memory (1210) may be implemented in the form of a single chip.

[0214] According to one embodiment of the present disclosure, a processor (1220) can control a series of processes that allow a terminal to operate according to the above-described embodiment of the present disclosure. For example, the processor (1220) can control the components of the terminal to perform a method for managing the above-described avatar according to the above-described embodiments. The processor (1220) can control the components of the terminal so that the above-described embodiments of the present disclosure are performed by executing a program stored in memory (1210). Additionally, the processor (1220) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0215] According to one embodiment of the present disclosure, the transceiver (1200) may transmit and receive signals with a network entity, another terminal, or a base station. The signals transmitted and received with the network entity, another terminal, or a base station may include control information and data. The transceiver (1200) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (1200), and the components of the transceiver (1200) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1200) may receive a signal through a wireless channel and output it to a processor (1220), and transmit the signal output from the processor (1220) through a wireless channel.

[0216] According to one embodiment of the present disclosure, the memory (1210) may store programs and data necessary for the operation of the terminal. Additionally, the memory (1210) may store control information or data included in signals transmitted and received by the terminal. The memory (1210) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memory (1210). Additionally, according to one embodiment, the memory (1210) may store a program for performing a method for managing the aforementioned avatar.

[0217] FIG. 13 is a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0218] As illustrated in FIG. 13, the base station of the present disclosure may include a processor (1320), a transceiver (1300), and a memory (1310). However, the components of the base station are not limited to the examples described above. For example, the base station may include more components or fewer components than the components described above. In addition, the processor (1320), the transceiver (1300), and the memory (1310) may be implemented in the form of a single chip.

[0219] According to one embodiment of the present disclosure, a processor (1320) can control a series of processes that enable a base station to operate according to the above-described embodiment of the present disclosure. For example, the processor (1320) can control the components of the base station to perform a method for managing the above-described avatar according to the above-described embodiments. The processor (1320) can control the components of the base station so that the above-described embodiments of the present disclosure are performed by executing a program stored in memory (1310). Additionally, the processor (1320) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0220] According to one embodiment of the present disclosure, the transceiver (1300) can transmit and receive signals with a network entity, another base station, or a terminal. The signals transmitted and received with the network entity, another base station, or a terminal may include control information and data. The transceiver (1300) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (1300), and the components of the transceiver (1300) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1300) may receive a signal through a wireless channel and output it to a processor (1320), and transmit the signal output from the processor (1320) through a wireless channel.

[0221] According to one embodiment of the present disclosure, the memory (1310) may store programs and data necessary for the operation of the terminal. Additionally, the memory (1310) may store control information or data included in signals transmitted and received by the base station. The memory (1310) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, the memory (1310) may be a plurality of. Additionally, according to one embodiment, the memory (1310) may store a program for performing a method for managing the aforementioned avatar.

[0222] FIG. 14 is a block diagram illustrating the structure of a network entity according to one embodiment of the present disclosure.

[0223] As illustrated in FIG. 14, the network entity of the present disclosure may include a processor (1420), a transceiver (1400), and a memory (1410). However, the components of the network entity are not limited to the examples described above. For example, the network entity may include more components or fewer components than the components described above. Furthermore, the processor (1420), the transceiver (1400), and the memory (1410) may be implemented in the form of a single chip. Additionally, according to one embodiment of the present disclosure, the network entity may refer to a network function (NF), and the NF may include all the entities described above.

[0224] According to one embodiment of the present disclosure, a processor (1420) can control a series of processes that allow the NF to operate according to the above-described embodiment of the present disclosure. For example, the processor (1420) can control the components of a network entity to perform a method for managing the above-described avatar according to the above-described embodiments. The processor (1420) can control the components of a terminal to perform the above-described embodiments of the present disclosure by executing a program stored in memory (1410). Additionally, the processor (1420) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0225] According to one embodiment of the present disclosure, the transceiver (1400) may transmit and receive signals with another network entity, base station, or terminal. The signals transmitted and received with another network entity or terminal may include control information and data. The transceiver (1400) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (1400), and the components of the transceiver (1400) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1400) may receive a signal through a wireless channel and output it to a processor (1420), and transmit the signal output from the processor (1420) through a wireless channel.

[0226] According to one embodiment of the present disclosure, the memory (1410) may store programs and data necessary for the operation of a network entity. Additionally, the memory (1410) may store control information or data included in signals transmitted and received by the network entity. The memory (1410) may be composed of a storage medium or a combination of storage media such as ROM, RAM, a hard disk, a CD-ROM, and a DVD. Additionally, there may be multiple memory (1410). Additionally, according to one embodiment, the memory (1410) may store a program for performing a method for managing the aforementioned avatar.

[0227] It should be noted that the configuration diagrams, exemplary diagrams of control / data signal transmission and reception methods, and exemplary diagrams of operation procedures illustrated in FIGS. 1 to 14 are not intended to limit the scope of the embodiments of the present disclosure. That is, all components, entities, or steps of operation described in FIGS. 1 to 14 should not be interpreted as essential components for implementing the disclosure, and may be implemented to the extent that the essence of the disclosure is not compromised even if only some components are included.

[0228] The operations of the embodiments described above can be realized by providing a memory device storing the corresponding program code in any component within the device. That is, the control unit within the device can execute the operations described above by reading the program code stored in the memory device by a processor or a CPU (Central Processing Unit) and executing it.

[0229] The entities or various components of terminal devices and modules described in this disclosure may be operated using hardware circuits, such as, for example, complementary metal oxide semiconductor-based logic circuits, firmware, software, and / or a combination of hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.

[0230] Methods according to the claims or embodiments described in the specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0231] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the claims or embodiments described in the specification of this disclosure.

[0232] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in a memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0233] Additionally, the program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, LAN (local area network), WAN (wide area network), or SAN (storage area network), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0234] In the specific embodiments of the present disclosure described above, the components included in the disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0235] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. A method performed by a DCSF (data channel signaling function) entity in a wireless communication system, A step of receiving an avatar model request message requesting an avatar model from an IMS (IP (internet protocol) multimedia subsystem) AS (application server) entity; A step of requesting a list of avatar models from a first avatar repository connected to the above DSCF entity and a second avatar repository connected to the DCAS (data channel application server) entity; A step of receiving a first avatar model list for avatar models stored in the first avatar storage from the first avatar storage; A step of receiving a list of second avatar models for avatar models stored in the second avatar storage from the second avatar storage; A step of generating the avatar model list based on the first avatar model list and the second avatar model list; and A method comprising the step of transmitting the generated avatar model list to the above IMS AS entity.

2. In Claim 1, The above avatar model request message includes request information for an avatar model allowed for the user of the terminal or the identifier of the user of the terminal, and The avatar model's identifier is not included in the request information of the above avatar model, and The above-mentioned generated avatar model list is associated with the avatar models allowed for the user of the terminal or the identifier of the user of the terminal, and A method in which the identifier of the user of the above terminal includes IMPU (IMS public identity).

3. In Claim 1, The first avatar repository or the second avatar repository includes a specific user folder and a common user folder, and A method in which the first avatar model list or the second avatar model list includes an avatar model list available for use by a specific user and an avatar model list available for use by a public user.

4. In claim 1, the method is, A step of creating a bootstrap application associated with the above-mentioned list of generated avatar models; A step of receiving search request and creation request messages for a media function (MF) entity for transmitting the bootstrap application from the IMS AS entity; A step of transmitting MF access information for the MF entity to the IMS AS entity; and A method comprising the step of transmitting the bootstrap application to a terminal through the above MF entity.

5. In Claim 4, The above bootstrap application represents an application exchanged between the terminal and the IMS network entity through a bootstrap data channel, and A method in which the bootstrap data channel represents a data channel established between the terminal and the IMS network entity within an IMS session.

6. In Claim 1, The above avatar model request message includes an identifier of the avatar model, a method.

7. In claim 6, the method is, A step of searching whether an avatar model corresponding to an identifier of the avatar model is stored in the first avatar storage and the second avatar storage; and The method includes the step of receiving a response indicating whether an avatar model corresponding to an identifier of the avatar model is stored from the first avatar storage and the second avatar storage. A method in which the avatar model list is requested from the first avatar repository and the second avatar repository based on the above response.

8. In a data channel signaling function (DCSF) entity in a wireless communication system, At least one processor; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the DCSF entity: Receives an avatar model request message requesting an avatar model from an IMS (IP (Internet Protocol) Multimedia Subsystem) AS (Application Server) entity, and Requesting a list of avatar models from the first avatar repository connected to the above DSCF entity and the second avatar repository connected to the DCAS (data channel application server) entity, and Receive a first avatar model list for avatar models stored in the first avatar storage from the first avatar storage, and Receives a list of second avatar models for avatar models stored in the second avatar storage from the second avatar storage, and Generate the avatar model list based on the first avatar model list and the second avatar model list, and A DCSF entity that causes the IMS AS entity to transmit the generated avatar model list.

9. In Claim 8, The above avatar model request message includes request information for an avatar model allowed for the user of the terminal or the identifier of the user of the terminal, and The avatar model's identifier is not included in the request information of the above avatar model, and The above-mentioned generated avatar model list is associated with the avatar models allowed for the user of the terminal or the identifier of the user of the terminal, and The identifier of the user of the above terminal is a DCSF entity including IMPU (IMS public identity).

10. In Claim 8, The first avatar repository or the second avatar repository includes a specific user folder and a common user folder, and The above first avatar model list or the above second avatar model list is a DCSF entity comprising an avatar model list available to specific users and an avatar model list available to public users.

11. In claim 9, the above instructions are such that the network entity: Create a bootstrap application associated with the above-mentioned list of generated avatar models, and Receiving search request and creation request messages for an MF (media function) entity for transmitting the bootstrap application from the above IMS AS entity, Transmit MF access information for the MF entity to the IMS AS entity, and A DCSF entity that transmits the bootstrap application to the terminal through the above MF entity.

12. In Claim 11, The above bootstrap application represents an application exchanged between the terminal and the IMS network entity through a bootstrap data channel, and The above bootstrap data channel is a DCSF entity representing a data channel established between the terminal and the IMS network entity within an IMS session.

13. In claim 8, The above avatar model request message is a DCSF entity containing an identifier of the avatar model.

14. In claim 13, the above instructions are such that the network entity: Searching whether an avatar model corresponding to the identifier of the avatar model is stored in the first avatar storage and the second avatar storage, and Receiving a response from the first avatar storage and the second avatar storage indicating whether an avatar model corresponding to the identifier of the avatar model is stored, and A DCSF entity in which the avatar model list is requested from the first avatar repository and the second avatar repository based on the above response.

Images