Method and apparatus for acquiring base avatar
The method addresses the challenge of managing avatars across multiple terminals by implementing secure avatar transfer processes and encryption, improving efficiency and security in advanced communication systems.
Patent Information
- Application Number
- PCT/KR2026/096864
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-12
- Filing Date
- 2026-05-12
- Publication Date
- 2026-11-19
AI Technical Summary
Existing communication systems lack efficient methods for acquiring and managing avatars across multiple terminals while ensuring security and performance, particularly in the context of increasing connected devices and advanced communication technologies like 5G and 6G.
A method for obtaining a base avatar through a series of processes including posture capture, animation command generation, scene mapping, rendering, and display, with security measures such as encryption and access control using asymmetric keys to manage avatar sharing and prevent unauthorized access.
Enables secure and efficient transfer of avatars across terminals, reducing transmission time and ensuring authorized access, thereby enhancing user experience and system performance in multi-terminal environments.
Smart Images

Figure KR2026096864_19112026_PF_FP_ABST
Abstract
Description
Method and device for obtaining a base avatar
[0001] The present disclosure relates to a method for acquiring a base avatar during an avatar call in a communication system.
[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 to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; 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 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 present disclosure proposes a method for obtaining a base avatar during an avatar process in a communication system.
[0009] Avatar calling can be implemented in the following steps: converting or generating the user's posture, i.e., pose or facial expression, into an animation command that moves the avatar; converting the avatar into the user's posture or facial expression by the animation command; mapping the changed avatar to a scene description that describes a virtual space dependent on user space; rendering the scene description into a 2D format to display it on a display; and converting the rendered image into video or displaying it directly on a display.
[0010] An avatar call process (or process) may be defined to standardize the above steps so that they can be exchanged between different terminals.
[0011] An avatar call process may be used to move the avatar to match the owner's posture, that is, posture or facial expression. The avatar call process may include a capture process for acquiring the user's posture or facial expression, an animation command generation process for generating commands to move the avatar from the captured information, an avatar animation process for moving the avatar according to the commands to move the avatar, a scene update process for applying the moved avatar to a scene description, a rendering process for converting the scene into an image, an encoding process for generating or compressing the image into a video, and a display process for displaying it on a display device.
[0012] The output of the previous step between each process can be sequentially connected as the input of the next step.
[0013] Avatar calling can be performed by dividing the avatar calling process among avatar calling entities. For example, animation command generation can be performed at a first terminal, the generated animation command can be transmitted to a second terminal, and the process after avatar animation can be performed at the second terminal.
[0014] An avatar may consist of one or more assets. Examples of assets may include the torso, face, clothing, and accessories such as hats. The owner entity of the avatar (e.g., the first terminal) may instruct the avatar user entity (e.g., the second terminal) to use an Avatar ID to specify which of the owner's multiple avatars to use for avatar calls, and to use an Asset ID to specify which assets of that avatar to use. One or more assets may be specified, and each asset may have different levels of detail (LoDs).
[0015] The avatar can operate by receiving and using it from the avatar user entity (e.g., the second terminal) after going through the step of authorizing use from the avatar owner entity (e.g., the first terminal).
[0016] At the call conclusion stage, whether avatar calls are possible between the two entities and whether avatar calls can be received can be determined.
[0017] Entities may select an avatar to be shown to a counterpart and provide information to enable access to it. For example, in order for a second terminal to access and use the avatar of the first terminal, that is, the avatar of the first user, the first terminal provides information such as an identifier and an asset identifier of the avatar to be used by the first user to the second terminal, and the second terminal can receive avatar data based on said information.
[0018] During the performance negotiation phase, it can be determined which avatar call processes to perform and which inputs and outputs to exchange between the two entities or additional entities of the network. For example, capture and animation command generation may be performed at the first terminal, and subsequent processes may be performed at the second terminal.
[0019] When an avatar is transmitted directly from the avatar owner's terminal to the avatar user's terminal, the process may take a significant amount of time as the number of terminals participating in the avatar call increases. To address this, the avatar owner can create the avatar and store it in advance in a network storage provided by the avatar call service. During the avatar reception phase, the avatar user's terminal can receive the avatar from the network storage.
[0020] The method and apparatus according to the embodiment of the present disclosure can efficiently acquire a base avatar from a BAR (Base Avatar Repository).
[0021] The method and apparatus according to the embodiments of the present disclosure can specify a target and an accessible range with security in mind in an avatar process.
[0022] FIG. 1 is a drawing for explaining an avatar process according to an embodiment of the present disclosure.
[0023] FIG. 2 is a flowchart for explaining an avatar data transfer method according to one embodiment of the present disclosure.
[0024] FIG. 3 is a flowchart illustrating an avatar data transfer method according to another embodiment of the present disclosure.
[0025] FIG. 4 is a flowchart for explaining an avatar reception failure response according to an embodiment of the present disclosure.
[0026] FIG. 5 is a flowchart for explaining the operation of entities when the end access time arrives during ASI according to an embodiment of the present disclosure.
[0027] FIG. 6 is a flowchart for explaining the operation of entities when a call termination is requested according to an embodiment of the present disclosure.
[0028] FIGS. 7a and 7b are flowcharts for explaining the operation of entities processing performance information related to an avatar call process according to an embodiment of the present disclosure.
[0029] FIG. 8 is a flowchart for explaining the operation of entities related to an avatar registration request according to an embodiment of the present disclosure.
[0030] FIG. 9 is a block diagram of a terminal according to one embodiment of the present disclosure.
[0031] FIG. 10 is a block diagram of a network node performing network functions according to one embodiment of the present disclosure.
[0032] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0033] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.
[0034] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.
[0035] 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 ensure that the disclosure is 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. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.
[0036] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, such terms may be replaced with terms defined in 3GPP Technical Specifications (TS) where appropriate.
[0037] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, the downlink (DL) refers to the wireless transmission path of a signal transmitted by a base station to a terminal, and the uplink (UL) refers to the wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technology (5G, new radio, NR) and 6th generation mobile communication technology (6G) developed after LTE-A may be included, and the 5G or 6G below may be a concept that includes existing LTE, LTE-A and other similar services. In addition, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications made in the judgment of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.
[0038] Hereinafter, “A or B” as described in the present disclosure may be understood as “A and / or B,” which may be understood to include “A,” or “B,” or “A and B.”
[0039] Additionally, “at least one of A, B, or C” described in the present disclosure may be understood to include “A,” or “B,” or “C,” or “any combination of A, B, and C.”
[0040] Additionally, “A / B” as described in the present disclosure may be understood as “A and / or B,” which may be understood as including “A,” or “B,” or “A and B.”
[0041] Additionally, “A, B” as described in the present disclosure may be understood as “A and / or B,” which may be understood as including “A,” or “B,” or “A and B.”
[0042] Furthermore, the expressions “if” and “in case that” as described in this disclosure or claims may be interpreted, depending on the context, as meaning “when or upon,” “in response to,” “based on,” or “according to,” and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes, provided that they do not impair the technical features of this disclosure.
[0043] Additionally, the expression in the present disclosure or claims that information can be configured from a base station may, depending on the context, mean that a terminal receives said information from a base station through upper-layer signaling, and such expression may be replaced with other terms having the same or substantially similar meaning.
[0044] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.
[0045] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure will be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the circumstances 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 in the singular form, and even if a component is expressed in the singular form, it may be composed in the plural form.
[0046] The drawings or flowcharts described below illustrate exemplary methods that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.
[0047] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each embodiment and may be utilized as a combination of all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope that does not deviate significantly from the scope of the present disclosure, at the judgment of a person skilled in the art.
[0048] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression "A" is used in one embodiment and the expression "B" is used in another embodiment, they may be understood by interchangeably, substituted, or combined.
[0049] At this point, 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 instruction means 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).
[0050] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific 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 example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.
[0051] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes 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 utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.
[0052] As stated above, it should be noted that the blocks of each flowchart and combinations of flowcharts described in this disclosure may be executed by one or more computer programs including instructions. The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.
[0053] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors is a circuitry that performs processing and may include an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry.
[0054] Additionally, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0055] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), and said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed alone or collectively by one or more processors of an electronic device.
[0056] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure.
[0057] Accordingly, various embodiments provide a program comprising code for implementing an apparatus or method according to any one of the claims of the present specification and a non-transient machine-readable storage medium for storing such program.
[0058] The operating principles of the present disclosure will be described in detail below with reference to the attached drawings. In describing the present disclosure below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Furthermore, the terms described below are defined in consideration of their functions in the present disclosure, 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.
[0059] In the present disclosure, an avatar call may be a communication method mediated by an avatar for communication between two or more entities. An entity may be a terminal or a network server. For example, it may be a call between a person who is the owner of one terminal and a person who is the owner of another terminal, or a call between an Artificial Intelligence (AI) agent and another AI agent among processes on a network server.
[0060] Avatar calling can be implemented in the following steps: converting or generating the user's posture, i.e., pose or facial expression, into an animation command that moves the avatar; converting the avatar into the user's posture or facial expression by the animation command; mapping the changed avatar to a scene description that describes a virtual space dependent on user space; rendering the scene description into a 2D format to display it on a display; and converting the rendered image into video or displaying it directly on a display.
[0061] An avatar call process (or process) may be defined to standardize the above steps so that they can be exchanged between different terminals.
[0062] An avatar call process may be used to move the avatar to match the owner's posture, that is, posture or facial expression. The avatar call process may include a capture process for acquiring the user's posture or facial expression, an animation command generation process for generating commands to move the avatar from the captured information, an avatar animation process for moving the avatar according to the commands to move the avatar, a scene update process for applying the moved avatar to a scene description, a rendering process for converting the scene into an image, an encoding process for generating or compressing the image into a video, and a display process for displaying it on a display device.
[0063] The output of the previous step between each process can be sequentially connected as the input of the next step.
[0064] Avatar calling can be performed by dividing the avatar calling process among avatar calling entities. For example, animation command generation can be performed at a first terminal, the generated animation command can be transmitted to a second terminal, and the process after avatar animation can be performed at the second terminal.
[0065] An avatar may consist of one or more assets. Examples of assets may include the torso, face, clothing, and accessories such as hats. The owner entity of the avatar (e.g., the first terminal) may instruct the avatar user entity (e.g., the second terminal) to use an Avatar ID to specify which of the owner's multiple avatars to use for avatar calls, and to use an Asset ID to specify which assets of that avatar to use. One or more assets may be specified, and each asset may have different levels of detail (LoDs).
[0066] The avatar can operate by receiving and using it from the avatar user entity (e.g., the second terminal) after going through the step of authorizing use from the avatar owner entity (e.g., the first terminal).
[0067] At the call conclusion stage, whether avatar calls are possible between the two entities and whether avatar calls can be received can be determined.
[0068] Entities may select an avatar to be shown to a counterpart and provide information to enable access to it. For example, in order for a second terminal to access and use the avatar of the first terminal, that is, the avatar of the first user, the first terminal provides information such as an identifier and an asset identifier of the avatar to be used by the first user to the second terminal, and the second terminal can receive avatar data based on said information.
[0069] During the performance negotiation phase, it can be determined which avatar call processes to perform and which inputs and outputs to exchange between the two entities or additional entities of the network. For example, capture and animation command generation may be performed at the first terminal, and subsequent processes may be performed at the second terminal.
[0070] When an avatar is transmitted directly from the avatar owner's terminal to the avatar user's terminal, the process may take a significant amount of time as the number of terminals participating in the avatar call increases. To address this, the avatar owner can create the avatar and store it in advance in a network storage provided by the avatar call service. During the avatar reception phase, the avatar user's terminal can receive the avatar from the network storage.
[0071] FIG. 1 is a drawing for explaining an avatar process according to an embodiment of the present disclosure.
[0072] Referring to FIG. 1, the communication system may include a first UE (user equipment), an IMS (IP Multimedia Subsystem) network, and a terminating network / second UE (Terminating Network / UE2). The second UE may belong to the terminating network.
[0073] The first UE may include Avatar Storage and Avatar app #1.
[0074] The IMS network may include at least one of CSCF (Call Session Control Function), IMS AS (IP Multimedia Subsystem Application Server), DCSF (Data Channel Service Function), MF (Media Function), DC AS (Data Channel Application Server), and BAR (Base Avatar Repository).
[0075] A second UE belonging to the end network may include Avatar Storage and Avatar app #2.
[0076] Step 1. The first UE can create an avatar prior to avatar currency.
[0077] Step 2. The avatar generated in the first UE can be uploaded to the IMS network.
[0078] Step 3. A call can be established between avatar call entities.
[0079] Step 4. The avatar call process performance of the avatar call entity can be exchanged, and the avatar call processes to be performed in each avatar call entity can be negotiated.
[0080] Step 5. A scene description including the avatars of the call participants can be constructed.
[0081] Step 6. The avatar call entity can receive the avatar instructed by the counterpart entity.
[0082] Step 7. The avatar call entity can execute the negotiated avatar call process.
[0083] An IMS network may be considered as an example of a network providing avatar call services. The IMS network may be composed of an IMS AS that finds and connects call counterpart entities in response to a call request, a DCSF for performing data channel negotiation when the information to be exchanged between call entities is data, a DC AS that provides data channel-based services, an MF responsible for data channel transmission or processing, and a BAR that stores and transmits avatars on the network to support avatar call services.
[0084] Limited sharing instruction method
[0085] A method is proposed for a single entity to restrictively share its avatar with a specific entity, and a method to ensure that such instruction is not misappropriated by another entity. In other words, a method is proposed to prevent the same instruction from being used by another entity against the will of the avatar owner. For example, it is necessary to restrict access so that while a third terminal can read the content that a first terminal has allowed a second terminal to access, the third terminal cannot access the first avatar and the first asset.
[0086] When one entity instructs another entity to use an avatar in a call, the instruction may consist of plaintext and ciphertext. The plaintext portion may be read by other entities without security issues, but the ciphertext portion may provide a verification function to prevent tampering with the plaintext. For example, when the first entity instructs the second entity to use its avatar, the third entity can also read the plaintext; however, if the third entity arbitrarily changes the plaintext content to make it appear as if it has been authorized to the third entity, the ciphertext portion may fail to pass the verification procedure.
[0087] Ciphertext can be generated from plaintext, an encryption key used to encrypt the plaintext, and an encryption algorithm. When an entity uses the same encryption key for both encryption and decryption, it is called symmetric-key based encryption; when the key used for encryption differs from the key used for decryption, it is called asymmetric-key based encryption. When implemented using an asymmetric key method, a terminal can generate two keys to form a pair: a private key (encryption key) and a public key derived from that key. The public key can decrypt content encrypted with the private key, and content encrypted with the public key can be decrypted with the private key. Only one public key can be generated from a private key, but it may be impossible to calculate the private key from a public key. The public key can be transmitted to a recipient authorized to decrypt, but the private key cannot be disclosed to anyone.
[0088] An avatar directive generated by one entity consists of plaintext and ciphertext, the ciphertext is encrypted with the one entity's private key, and the one entity's public key can be transmitted only to a BAR that stores and manages avatars or a DC AS that services avatar calls. An avatar directive can be transmitted from the one entity to a DC AS, and the DC AS may transmit the received avatar directive to a BAR for management, treating it as a currently valid avatar directive. Alternatively, the avatar directive can be transmitted directly from the one entity to other entities that are targets for calls (e.g., a second entity). A second entity that receives an avatar directive may submit it to a BAR or DC AS to receive only the avatar, without attempting to decrypt the plaintext and ciphertext within the avatar directive. BAR can use the avatar directive of the first entity that it has or has received from DC AS to compare with the avatar directive submitted by the second entity, and if they match, it can verify the avatar directive using the public key received from the first entity, and if the directive is verified, it can provide the avatar to the second entity within the directive.
[0089] An entity may transmit avatar directives—that is, directives regarding the avatar to be used in avatar currency—as Avatar Selection Information or Avatar Selection Instruction (ASI). Avatar Selection Information may include an avatar identifier designating the avatar to be used in avatar currency, the scope of sharing for the assets constituting the avatar, and the Level of Details (LoDs) for each asset. Additionally, the start and expiration times of the information may be specified. Furthermore, it may include a hash code capable of verifying all this information, and an encrypted hash code obtained by encrypting that hash code with the user's private key.
[0090] Table 1: ASI (Avatar Selection Information)
[0091] Avatar Selection Information Description Owner ID: Information to identify the owner of the avatar. Target ID: Information to identify the avatar call counterpart. Avatar ID: The avatar owner's avatar identifier or URL. Asset ID: Identifier of the asset belonging to the avatar. A list of multiple Asset IDs may be provided for a single Avatar ID, and each Asset ID may have one or more LoDs IDs. LoDs ID: Identifier of the LoDs specified for the asset. access start time: The start time when the ASI becomes valid. access expiration time: The time when the ASI expires. asiIdentifier: The identifier of the ASI. postCallPolicy: Indicates whether avatar data is retained after the call. deleteAfterCall deletes avatar data upon call termination. remainAfterCall retains avatar data even after the call ends. asiPublishingTime: The time when the ASI is published. Encrypted HASH code: The result of encrypting the HASH code for the remaining ASI information (plaintext), excluding the Encrypted HASH code, using the Owner's private key.
[0092] Except for the Encrypted HASH code, the remaining ASI information can be transmitted in plaintext. Avatar call intermediary entities such as DC AS and MF can verify the ASI content during the negotiation process.
[0093] An encrypted hash code can be generated by encrypting the hash code of plaintext using a private key. A hash code is the result of creating a unique string or numerical form for a given plaintext; if the plaintext is identical, the same value will always be generated, but if the order of the plaintext or even a single space is changed, a different value may be generated. Therefore, plaintext must be read according to the same rules and passed to the hash algorithm so that the recipient (BAR) can verify it. Consistent plaintext rules that can be applied when passing an ASI to a hash algorithm include using the content exactly as written in the ASI, creating combined text separated by special values (e.g., comma-separated text), or writing it according to JSON (JavaScript Object Notation) rules and generating a serialized string using methods such as a JSON dump.
[0094] A second entity that receives an ASI from a first entity transmits the ASI to Avatar Storage within the second entity, and Avatar Storage can request an avatar from BAR via MF. The avatar request may include an ASI. BAR can read the ASI, read the Owner ID, and verify whether the public key of the user identified by the Owner ID is stored in BAR. BAR can decrypt an encrypted hash code using the corresponding user's public key and verify whether the decrypted hash code value matches the hash code generated by BAR for the plaintext.
[0095] If verified, BAR can determine that the ASI is generated by the first entity and grants the second entity access to all or part of the avatar. That is, if the plaintext part is tampered with, such as by being a third entity for the Target ID, the hash code value will not match, and thus tampering with the ASI instructions can be prevented.
[0096] Next, the BAR can determine whether the current time is greater than the access start time and less than the access end time. That is, if the current time is within the range of the access time, it can determine that it is permissible to provide the avatar indicated by the Avatar ID, Asset ID, and LoDs ID to the second entity specified by the Target ID. In other words, even if it is a valid ASI created by the first entity, receiving the avatar again using that ASI after the avatar call may be blocked.
[0097] BAR can encrypt the avatar's access permissions specified in ASI using the second entity's public key and deliver it as a response to an avatar request from the second entity's Avatar Storage. In other words, if an entity other than the second entity, which is the legitimate recipient, intercepts the data, there is no way to decrypt it, so use by other entities can be blocked.
[0098] If the BAR does not have a public key identified by the Owner ID and Target ID, it can request one from the DC AS. The DC AS can receive the entities' public keys before the call or during the call execution phase. The DC AS can encrypt the requested users' public keys using the BAR's public key and transmit them to the BAR, which can store them and decrypt them using its private key for use when necessary.
[0099] FIG. 2 is a flowchart for explaining an avatar data transfer method according to one embodiment of the present disclosure.
[0100] Referring to FIG. 2, the communication system may include a first UE (user equipment), an IMS (IP Multimedia Subsystem) network, and a terminating network / second UE (Terminating Network / UE2). The second UE may belong to the terminating network.
[0101] The first UE may include a first Avatar Storage and a first Avatar app #1.
[0102] The IMS network may include at least one of CSCF (Call Session Control Function), IMS AS (IP Multimedia Subsystem Application Server), DCSF (Digital Content Service Function), MF (Media Function), DC AS (Digital Content Application Server), and BAR (Base Avatar Repository).
[0103] A second UE belonging to an end network may include a second Avatar Storage and a second Avatar app #2. Step 1. In the step of establishing a call from the first terminal (UE1) to the second terminal (UE2), ASI information within the call request may be transmitted. The Avatar app specifies UE2 as the call recipient to the IMS AS via the CSCF, and the IMS AS may transmit the call request to UE2.
[0104] Step 2. Or, after an application data channel is established between the first terminal and the second terminal, ASI information may be transmitted from the first terminal to the second terminal. Messages from the avatar call app may be transmitted to the second terminal via an MF that relays the data channel connection.
[0105] Step 3. The avatar calling app of the second terminal (the second avatar calling app) can load (loadAvatar) the avatar specified by the first terminal (e.g., Avatar ID is Avatar1) into the Avatar Storage of the second terminal (the second avatar storage).
[0106] Step 4. The second avatar store can request the receipt of an avatar from the BAR via MF and DC AS using the DC AS / BAR URL (requestAvatar). The parameters of requestAvatar() may include ASI.
[0107] Step 5. The BAR can verify the received ASI and determine whether it has been tampered with.
[0108] Step 6. After passing the tamper-proof verification, the BAR can verify whether it has expired by comparing the start / end access time within the ASI with the current time.
[0109] Step 7. BAR can find UE2's public key for UE2, which has been determined to be a legitimate recipient, and encrypt the avatar data decrypted with UE1's public key using UE2's public key.
[0110] Step 8. BAR can send avatar data encrypted with the recipient UE2's public key to a second avatar storage as a response to requestAvatar().
[0111] Step 9. The second avatar storage can store the received avatar data.
[0112] Step 10. The second avatar store can respond that the avatar has been saved according to the loadAvatar() message.
[0113] Step 11. The Avatar Calling App of the second terminal (the second Avatar Calling App) may request Avatar data from the Avatar Storage of the second terminal (the second Avatar Storage) to read the Avatar specified by the first terminal (e.g., Avatar ID is Avatar1). The parameters of readAvatar() may include Avatar ID, Asset ID, byte offset / range, as well as ASI, private key, DC AS / BAR URL, etc.
[0114] Step 12. The second avatar storage can check whether the current time is within the access time range for the avatar data request from the second avatar calling app in Step 11.
[0115] Steps 13, 14. The second avatar storage can decrypt the avatar data request from the second avatar calling app using a UE2 private key and then transmit it to the second avatar calling app.
[0116] <How to expire sharing>
[0117] A method is proposed to prevent other entities participating in the call from further accessing the avatar of the unentity once the avatar call of the unentity ends.
[0118] For example, if the first terminal ends the avatar call, the second terminal can no longer configure a screen using the first avatar.
[0119] In order to prevent the reuse of Avatar 1, which is the other party's avatar, after a call is ended on the second terminal, a DRM role is assigned to Avatar Storage, which is the avatar storage of the second terminal.
[0120] An Avatar Calling entity may have an Avatar Calling App and Avatar Storage as components. Avatar Storage may provide functions for the transmission and storage of avatar data, decryption of stored avatar data, and permission management (or Digital Rights Management (DRM)) of stored avatar data. An Avatar Calling App cannot receive avatars directly but can receive them through Avatar Storage. Avatar Storage checks the Avatar Owner's provision policy regarding the Avatar Calling App's request for avatar data and may provide avatar data only if it is confirmed to be consistent with the policy. In other words, even if avatar data has been received by the device, unauthorized access may be blocked if it violates the policy permitted and granted by the avatar owner.
[0121] The Avatar Calling app can request Avatar data from Avatar Storage using a readAvatar() message. If the requested Avatar data has not been received, Avatar Storage can decide to receive it and proceed.
[0122] Table 2: readAvatar()
[0123] readAvatar() ASI: The private key issued by the avatar owner for permission to use the avatar private key: The avatar user's private key DC AS / BAR URL: The BAR where the avatar is stored or the URL of the DC AS to access the BAR avatar ID: The avatar identifier to be accessed by the avatar calling app. list of asset IDs: Asset identifier(s) to be accessed from the avatar list of LoDs: Indicates the identifier of the specified Asset-Specific Quality (LoDs) from the list of asset IDs. byteOffset: The starting position in the asset to read byteRange: The size in bytes to be read from the starting position in the asset
[0124] Table 3: requestAvatar()
[0125] requestAvatar() ASI issued by the avatar owner for permission to use the avatar
[0126] ASI, private key, DC AS / BAR URL, etc., may be omitted after the initial avatar data request from the Avatar Calling App to Avatar Storage following the establishment of an Avatar Call. If this information is destroyed within Avatar Storage or is determined to be no longer valid in communication with BAR / DC AS, Avatar Storage may respond to the Avatar Calling App with an error code indicating that this information is incorrect.
[0127] FIG. 3 is a flowchart illustrating an avatar data transfer method according to another embodiment of the present disclosure.
[0128] Referring to FIG. 3, the communication system may include a first UE (user equipment), an IMS (IP Multimedia Subsystem) network, and a terminating network / second UE (Terminating Network / UE2). The second UE may belong to the terminating network.
[0129] The first UE may include a first Avatar Storage and a first Avatar Call App (Avatar app #1). The IMS network may include at least one of CSCF, IMS AS, DCSF, MF, DC AS, and BAR. The second UE belonging to the end network may include a second Avatar Storage and a second Avatar Call App (Avatar app #2). Step 1. In the step of establishing a call from the first terminal (UE1) to the second terminal (UE2), ASI information within the call request may be transmitted. The Avatar Call App specifies UE2 as the call recipient to the IMS AS via the CSCF, and the IMS AS may transmit the call request to UE2.
[0130] Step 2. After an application data channel is established between the first terminal and the second terminal, ASI information can be transmitted from the first terminal to the second terminal. Messages from the avatar call app can be transmitted to the second terminal via an MF that relays the data channel connection.
[0131] Step 3. The Avatar Calling App of the second terminal (the second Avatar Calling App) may request Avatar data from the Avatar Storage of the second terminal (the second Avatar Storage) to read the Avatar specified by the first terminal (e.g., Avatar ID is Avatar1). The parameters of readAvatar() may include Avatar ID, Asset ID, byte offset / range, as well as ASI, private key, DC AS / BAR URL, etc.
[0132] Step 4. The second avatar storage checks if there is already stored avatar data, and if there is no stored data, steps 5 to 10 may be performed.
[0133] Step 5. The second avatar store can request the reception of an avatar from the BAR via MF and DC AS using the DC AS / BAR URL (requestAvatar). The parameters of requestAvatar() may include ASI.
[0134] Step 6. The BAR can verify the received ASI and determine whether it has been tampered with.
[0135] Step 7. After passing the tamper-proof verification, the BAR can verify whether it has expired by comparing the start / end access time within the ASI with the current time.
[0136] Step 8. BAR can find UE2's public key for UE2, which has been determined to be a legitimate recipient, and encrypt the avatar data decrypted with UE1's public key using UE2's public key.
[0137] Step 9. BAR can send avatar data encrypted with the recipient UE2's public key to a second avatar storage as a response to requestAvatar().
[0138] Step 10. The second avatar storage can store the received avatar data.
[0139] Step 11. The second avatar storage can check whether the current time is within the access time range for the avatar data request from the second avatar calling app in Step 3.
[0140] Steps 12, 13. The second avatar storage can decrypt the avatar data request from the second avatar calling app using a UE2 private key and then transmit it.
[0141] An avatar calling app can explicitly request Avatar Storage to receive avatar data using a loadAvatar() message instead of a readAvatar() message. The avatar's receive instruction may include an address for accessing the DC AS or BAR and an ASI.
[0142] With the Avatar Call Entity having established an application data channel with MF, components of the Avatar Call Entity, such as Avatar Storage and the Avatar Call App, can request messages from DC AS, BAR, and counterpart call entities and receive responses through MF.
[0143] Avatar Storage may send a requestAvatar() message to request the transfer of an avatar to a DC AS or BAR. The requestAvatar() message includes an ASI. For example, it may include an ASI instructing the use of Avatar 1 (Avatar ID = Avatar1) and its asset, Asset 1 (Asset ID = Asset 1), from a first terminal to a first user (Owner ID = 1 User) for an avatar call with a user of a second terminal (Target ID = 2 User).
[0144] BAR can determine whether the ASI received from Avatar Storage is valid by reading the ASI, verifying the encrypted hash code, etc., and verifying whether it is within the permitted usage time.
[0145] BAR can determine the range of data indicated by ASI by verifying the owner ID of the avatar from ASI, verifying the avatar identifier (Avatar ID) from the owner's avatar list, and verifying the asset identifier and quality (LoDs) identifier from the avatar data. The determined range of data can be encrypted using the public key of the allowed sharing target (Target ID) and then returned as a response to requestAvatar. For example, in response to a requestAvatar message received from a second terminal, the first asset specified in ASI can be encrypted with the second user's public key and transmitted to the second terminal.
[0146] Table 4: loadAvatar()
[0147] loadAvatar() ASI The ASI DC AS / BAR URL issued by the avatar owner for permission to use the avatar, or the URL of the DC AS for accessing the BAR where the avatar is stored.
[0148] Avatar Storage can store encrypted avatars received from BAR and provide them to avatar calling apps. The storage of encrypted avatars and their provision to avatar calling apps may be limited to the time range permitted within ASI.
[0149] After the allowed time range (start / end access time) within the ASI, the deletion of Avatar data may follow the postCallPolicy specified within the ASI. If the value of postCallPolicy is deleteAfterCall, Avatar Storage may schedule a delete command for data identified by the Avatar ID as an event triggered at the access expiration time. When the time on the Avatar Call entity's clock is after the access expiration time, the delete command is executed, and all data identified by the Avatar ID may be deleted.
[0150] In order to enable Avatar Storage to provide data only within the allowed time range, Avatar Data Information received from the BAR may be a bundle of Avatar data encrypted with the public key of an authorized user, along with information such as the Avatar owner's identifier (Owner ID), authorized user's identifier (Target ID), Avatar identifier (Avatar ID), a list of bundles of asset and asset LoDs identifiers, usage start time, usage expiration time, and post-call policy.
[0151] Table 5: Avatar Data Information
[0152] Avatar Data Information Description Owner ID: Information to identify the owner of the avatar. Target ID: Information to identify the avatar call partner. Avatar ID: The avatar owner's avatar identifier or URL. Asset ID: Identifier of an asset belonging to the avatar. A list of multiple Asset IDs may be provided for a single Avatar ID, and each Asset ID may have one or more LoDs IDs. LoDs ID: Identifier of the LoDs specified for the asset. access start time: The start time when the ASI becomes valid. access expiration time: The time when the ASI expires. postCallPolicy: Indicates whether avatar data is retained after the call. deleteAfterCall deletes avatar data upon the end of the call. remainAfterCall retains avatar data even after the end of the call. encryptedData: Avatar data encrypted with the avatar call partner's public key.
[0153] Avatar Storage can store Avatar Data Information received from the BAR and retain it within the usage period specified in the ASI.
[0154] The Avatar Calling App can request data from Avatar Storage by instructing it with the Avatar Identifier and Asset Identifier. Avatar Storage checks the allowed access time when the information exists, and if the current time is within the allowed access time, it can decrypt the data using the user's private key and provide the Avatar data to the Avatar Calling App.
[0155] If the current time is after the usage period specified in the ASI, Avatar Storage may refuse to transmit data to the Avatar calling app.
[0156] Avatar Storage may extend the allowed time range (start / end access time) before it expires within ASI. Compared to conventional voice and video calls, the difference in avatar calls is that the avatar, which acts on behalf of the user, is permitted to be used only during the avatar call. Since the exact end time of the call cannot be specified at the time of the request, the call may typically end before the designated end time, or the avatar call may end after the designated end time.
[0157] The entity requesting the avatar call can specify an expected call end time, i.e., end access time, of an appropriate length, such as 1 minute. If, as the call continues, it is expected that the call will continue beyond the initially specified end access time, the entity needs to extend the counterpart entity's avatar access time.
[0158] Accordingly, the entity of the owner of the avatar (e.g., the first terminal) or the entity of the user of the avatar may send a message to extend the end access time at a certain time when the avatar call is in progress and the end access time arrives.
[0159] If the day entity is the avatar owner's entity and extends the call duration, the avatar call app can set a time interval or time-based reporting frequency to maintain the call and notify the DC AS that the call is in progress at fixed time intervals or at fixed frequencies per hour unit.
[0160] A call maintenance report may indicate that a work entity is participating in an avatar call, and updates to the ASIs that the entity has directed other entities to, i.e., new end access times.
[0161] One entity can verify, through a response to a call maintenance report from the DC AS, whether the permission to use Avatar data, that is, data identified by an Avatar identifier, which was granted permission by another entity, is still valid. When another entity terminates a call, the DC AS may include a list of entities whose call was terminated and / or Avatar identifiers and ASI identifiers in the response to the call maintenance report from the one entity, thereby causing the Avatar Storage of the one entity receiving this to expire the data identified by the Avatar identifier and the ASI received from those entities. For example, if the first terminal sends a call maintenance report to the DC AS after the third terminal terminates a call during an Avatar call between the first, second, and third terminals, the DC AS may respond that the third terminal has terminated the call and that the identifier of the ASI granted by the third terminal to the first terminal and the Avatar identifier Avatar3 have expired. The Avatar Storage of the first terminal recognizes the expiration information in the response as an instruction, deletes the Avatar3 stored in the Avatar Storage according to the policy, changes the end access time of the ASI from the identified third terminal to the current time, and can reject the data request for the display of the third terminal's avatar, i.e., Avatar3, from the avatar app of the first terminal.
[0162] A DC AS may notify other entities of the termination of a call by one entity. The notification may be in response to a call maintenance report or may be a notification from the DC AS to entities that participated in the avatar call prior to receiving the call maintenance report.
[0163] DC AS can refer to call persistence reports to determine whether the work entity is in an avatar call while the session has not been explicitly ended.
[0164] If the DC AS determines that an avatar call is in progress, it can manage the avatar call session as being maintained. The DC AS can update the last call maintenance report time (lastPingTimestamp) per call entity to the current time and instruct the BAR to increment the end access time of the corresponding ASI.
[0165] If a DC AS determines that the entity has disconnected or the avatar calling app has terminated abnormally if no call maintenance report is received after the call maintenance report interval from the time the last call maintenance report was received, it may revoke permissions to prevent avatars owned by the entity from being used by other entities.
[0166] When a DC AS revokes authority, the DC AS may instruct the BAR to expire (dismissAvatarCall) the ASI issued by the Avatar Owner. The dismissedTime of dismissAvatarCall() can be the time when the message was sent or the time when the Owner entity last received a report to keep the call.
[0167] The BAR receives the Owner ID from the dismissAvatarCall message, identifies ASIs with matching Owner IDs among the currently active ASIs, classifies those ASIs as deactivated, and can specify the classification time as dismissedTime.
[0168] When a request for access to an avatar is received from Avatar Storage of Avatar User entities with an ASI as a parameter, the BAR may compare it against the active ASIs and refuse to provide the avatar data and return an error code if the ASI's asiPublishingTime is older than dismissedTime—that is, if it has been processed as expired by the DC AS since being issued by the Avatar Owner entity. The error code may include details such as ASI deactivated or Avatar owner departed.
[0169] Avatar Storage for Avatar User entities can specify the access expiration time as the current time or dismissedTime when deleting or retaining avatar data for expired avatars according to the policy in Avatar Data Information.
[0170] Table 6: dismissAvatarCall()
[0171] dismissAvatarCall() Owner ID: The identifier of the avatar owner is entered. dismissedTime: The time when the avatar sharing was expired is entered.
[0172] FIG. 4 is a flowchart for explaining an avatar reception failure response according to an embodiment of the present disclosure.
[0173] Referring to FIG. 4, the communication system may include a first UE, an IMS network, and a terminating network / second UE (Terminating Network / UE2). The second UE may belong to the terminating network.
[0174] The first UE may include a first Avatar Storage and a first Avatar app (Avatar app #1). The IMS network may include at least one of CSCF, IMS AS, DCSF, MF, DC AS, and BAR. A second UE belonging to an end network may include a second Avatar Storage and a second Avatar app (Avatar app #2). Step 1. The first Avatar app may transmit a call hold report to the DC AS when a call is being held.
[0175] Step 2. DC AS can update the last Ping Timestamp of the first terminal to the current time based on a call hold report from the first avatar call app.
[0176] Step 3. At any point, the first avatar call app may terminate abnormally. This may result in the call maintenance report not being sent for a significant amount of time.
[0177] Step 4. DC AS may determine that it is a timeout when no call maintenance report is received from the first avatar call app even after a call maintenance report interval from the time the last call maintenance report was received.
[0178] Step 5. DC AS can pass the Owner ID of the first avatar call app and dismissTime as the timeout classification point as parameters of the dismissAvatarCall() message to reflect the timeout in the BAR.
[0179] Step 175 6. The BAR can look up active ASIs by Owner ID and mark matching ASIs as disabled. The BAR can update asiPublishingTime to dismissedTime for ASIs under management.
[0180] Step 7. The BAR can respond that deactivation is complete.
[0181] Step 8. At any time, the second avatar calling app may receive the first user's avatar from the second avatar storage or request the data.
[0182] Step 9. The second avatar repository may submit an ASI to the BAR to receive avatar data.
[0183] Step 10. The BAR can identify that the ASI requested by the second avatar repository has an earlier time than the ASI disabled by the BAR by comparing asiPublishingTime, and that the disabled ASI is the more up-to-date information.
[0184] Step 11. The BAR may respond with a rejection message containing an error code indicating that the ASI submitted to request avatar data has expired.
[0185] Step 12. The second avatar storage may delete or retain expired avatar data according to the policy, but may not proceed with decryption.
[0186] Step 13. The second avatar storage may respond to the second avatar calling app that avatar reception or data provision failed.
[0187] According to one embodiment, if an entity is an avatar user entity and extends the call time, the avatar call app may request an end access time extension request (requestEndtimeExtension) to the DC AS before the end access time arrives. The timing of the request may be a predetermined time before the end access time (e.g., 5 seconds before). As parameters of requestEndtimeExtension, the ASI or the Owner ID and Avatar ID within the ASI to be updated may be specified.
[0188] When the DC AS receives a call maintenance report from the Avatar Owner entity and the Avatar session is managed as being maintained accordingly, it can request the Avatar Owner entity to issue a new ASI to extend the session (updateAvatarCallSession).
[0189] The Avatar Owner entity may reply by issuing an ASI with an extended end access time as a response.
[0190] DC AS can return a new ASI to the Avatar User entity as a response to requestEndtimeExtension.
[0191] The Avatar Owner entity can issue an ASI with a preset value (e.g., 1 minute from the current time) to avoid too frequent extension requests.
[0192] Table 7: requestEndtimeExtension()
[0193] requestEndTimeExtension() The ASI of the ASI to be updated is entered. Owner The owner ID within IDASI is entered instead. Avatar The Avatar ID within IDASI is entered instead.
[0194] Table 8: updateAvatarCallSession()
[0195] updateAvatarCallSession()ASI The new ASI is recorded.(new) end access time The new end access time to be changed is recorded.(new) asiPublishingTime The time when the new ASI was issued is recorded.
[0196] FIG. 5 is a flowchart for explaining the operation of entities when the end access time arrives during ASI according to an embodiment of the present disclosure.
[0197] Referring to FIG. 5, the communication system may include a first UE, an IMS network, and a terminating network / second UE (Terminating Network / UE2). The second UE may belong to the terminating network.
[0198] The first UE may include a first Avatar Storage and a first Avatar app #1. The IMS network may include at least one of CSCF, IMS AS, DCSF, MF, DC AS, and BAR. The second UE belonging to the end network may include a second Avatar Storage and a second Avatar app #2.
[0199] Step 1. The second avatar calling app can detect ASIs received from call counterpart entities whose end access time is approaching. To do this, it can schedule an event that is triggered a predetermined time (e.g., 5 seconds) before the end access time, and when the event is triggered, it can determine a request for reissuance for the corresponding ASI.
[0200] Step 2. The second avatar calling app can request a session extension (requestEndtimeExtension) from the DC AS.
[0201] Step 3. DC AS can check the last call maintenance report time of the target first avatar call app and identify whether the first avatar call app is in a timeout state.
[0202] Steps 4, 5. If identified as being in a timeout state, the DC AS may reject the request from the second avatar calling app.
[0203] Step 6. If the session is valid and not a timeout, the DC AS may request an ASI from the first avatar calling app to extend the session.
[0204] Step 7. The first avatar call app can extend the end access time of the ASI and re-perform hashing and encryption to issue the extended ASI.
[0205] Step 8. The first avatar call app can transmit a new ASI with an extended end access time to the DC AS.
[0206] Step 9. DC AS can transmit the extended ASI to the second avatar calling app.
[0207] If a day entity is the avatar owner's entity and the call time ends—that is, if the avatar owner logs out of the avatar call—the owner's avatar call app may request the DC AS to end the call. Upon request, the DC AS may revoke avatar usage rights for the entities of avatar users remaining in the avatar call session.
[0208] When a DC AS revokes authority, the DC AS may instruct the BAR to expire (dismissAvatarCall) the ASI issued by the Avatar Owner. The dismissedTime of dismissAvatarCall() can be the time when the message was sent or the time when the Owner entity last received a report to keep the call.
[0209] The BAR receives the Owner ID from the dismissAvatarCall message, identifies ASIs with matching Owner IDs among the currently active ASIs, classifies those ASIs as deactivated, and can specify the classification time as dismissedTime.
[0210] When a request for access to an avatar is received from Avatar Storage of Avatar User entities with an ASI as a parameter, the BAR may compare it against the active ASIs and refuse to provide the avatar data and return an error code if the ASI's asiPublishingTime is older than dismissedTime—that is, if it has been processed as expired by the DC AS since being issued by the Avatar Owner entity. The error code may include details such as ASI deactivated or Avatar owner departed.
[0211] Avatar Storage for Avatar User entities can specify the access expiration time as the current time or dismissedTime when deleting or retaining avatar data for expired avatars according to the policy in Avatar Data Information.
[0212] The DC AS can send dismissAvatarCall to the entity's Avatar Call app for the avatar users remaining in the avatar call session. Upon receiving dismissAvatarCall, the entity's Avatar Call app can disable the ASI with the specified owner ID and remove the avatar matching the owner ID from the avatar call's Scene description.
[0213] FIG. 6 is a flowchart for explaining the operation of entities when a call termination is requested according to an embodiment of the present disclosure.
[0214] Referring to FIG. 6, the communication system may include a first UE, an IMS network, and a terminating network / second UE (Terminating Network / UE2). The second UE may belong to the terminating network.
[0215] The first UE may include a first Avatar Storage and a first Avatar app #1. The IMS network may include at least one of CSCF, IMS AS, DCSF, MF, DC AS, and BAR. The second UE belonging to the end network may include a second Avatar Storage and a second Avatar app #2.
[0216] Step 1. The first avatar call app may send an avatar call termination request to the DC AS before exiting the avatar call.
[0217] Step 2. The DC AS can determine the termination process for the session of UE1 (the first avatar call app) among the call participants of the avatar call session.
[0218] Step 3. DC AS can notify BAR that the avatar with Owner ID UE1 is deactivated.
[0219] Step 4. BAR can look up ASIs and classify ASIs with Owner ID UE1 as disabled.
[0220] Step 5. The BAR can respond to the DC AS that the disable action for the ASI with Owner ID UE1 has been completed.
[0221] Step 6. The DC AS can query entities that are maintaining a connection within the avatar call session. For example, processing can be initiated for UE2 when it remains.
[0222] Step 7. DC AS may notify the second avatar call app of the deactivation of the call status with Owner ID UE1.
[0223] Step 8. The second avatar call app can remove UE1's avatar from the Scene and terminate the avatar call processes running on the second terminal to process UE1's avatar.
[0224] Step 9. The second avatar calling app may instruct the second avatar storage to delete Avatar1, which is UE1's avatar, in accordance with the policy.
[0225] Step 10. The second avatar storage can respond to the second avatar calling app that the deletion of the avatar is complete.
[0226] <Shared Delegation Method>
[0227] The processing capabilities of entities participating in an avatar call can be negotiated, and a network server can intervene to process the avatar call process as another entity; in this case, a method is proposed to delegate the avatar access rights of the entity to handle the processing instead.
[0228] For example, when the performance of the second terminal is insufficient, the network server needs to inherit the access rights of the second terminal in order to receive and render the first avatar instead of the second terminal.
[0229] DC AS can compare the performance of the first terminal and the performance of the second terminal when receiving and concluding an avatar call request from the first terminal to the second terminal. When it is determined that part of the avatar call process cannot be executed at either the first terminal or the second terminal, DC AS can decide to have the network server (MF) handle the processing and have the MF participate between the first terminal and the second terminal.
[0230] Since the first terminal designated the second terminal as the recipient of the avatar call, the Target ID of the ASI can be the identifier of the second terminal.
[0231] If MF is assigned the role of executing part of the avatar processing performed between the first terminal and the second terminal, such as Avatar animation and Rendering, MF must be able to obtain access rights to the avatar of the first terminal. However, avatar data transmitted from BAR to MF is encrypted with the public key of the second terminal designated as the recipient by the first terminal, so it cannot be decrypted by MF.
[0232] To resolve this, the DC AS may instruct the MF to have an identifier, a public key, and a private key at the time it determines the intervention and allocation of the MF. The identifier, public key, and private key may be generated by the MF or issued by a management function on a separate network.
[0233] DC AS can receive an identifier and a public key from MF.
[0234] DC AS can convey to the first terminal (requestAddDelegator) that an ASI targeting MF should be issued in addition to the ASI issued by the first terminal targeting the second terminal.
[0235] Table 9: requestAddDelegator()
[0236] requestAddDelegator original Target ID: Originally specified Avatar User Entity Identifier delegated Target ID: MF's Identifier
[0237] The first terminal receives a request for the issuance of a new ASI from the DC AS, identifies from the parameters that the request for issuance is an inheritance of authority to the MF (delegated Target ID) regarding the access authority granted to the second terminal (original Target ID), and determines that a request has been made to execute some avatar call process by the network server.
[0238] The first terminal can issue a new ASI with the requested identifier and transmit it to the DC AS.
[0239] DC AS passes this to MF, and MF can request an avatar from BAR using the issued ASI.
[0240] BAR verifies the ASI received from MF and can deliver the avatar owned by the first user to MF instead of the second terminal. BAR has received or can receive MF's public key from the DC AS. BAR encrypts the avatar data using MF's public key and delivers it to MF, and MF stores it in the Base Avatar Cache (BAC) process and can then retrieve and use it in the avatar animation process or rendering process.
[0241] BAC can support DRM for avatar data, such as the terminal's Avatar Storage.
[0242] FIGS. 7a and 7b are flowcharts for explaining the operation of entities processing performance information related to an avatar call process according to an embodiment of the present disclosure.
[0243] Referring to FIGS. 7a and 7b, the communication system may include a first UE, an IMS network, and a terminating network / second UE (Terminating Network / UE2). The second UE may belong to the terminating network.
[0244] The first UE may include a first Avatar Storage and a first Avatar app #1. The IMS network may include at least one of CSCF, IMS AS, DCSF, MF, BAC, DC AS, and BAR. The second UE belonging to the end network may include a second Avatar Storage and a second Avatar app #2.
[0245] Referring to FIG. 7a, in steps 1 and 2, the DC AS can request performance information related to the avatar call process from avatar call entities participating in the avatar call.
[0246] In steps 3 and 4, each avatar call app can provide information to the DC AS regarding the avatar call process and available inputs and outputs.
[0247] Step 5. DC AS can allocate avatar call processes through performance comparison between entities and determine whether to use MF's processing capabilities when there are processes that cannot be executed by any entity.
[0248] Steps 6 through 30 illustrate the case where MF is used, and steps 31 through 34 illustrate the case where MF is not used.
[0249] Step 6. The DC AS may request the DCSF (or IMS AS) to allocate an MF for processing. The MF for processing may be the same as or different from the MF for the data channel proxy. The performance required for the data channel proxy may differ from the performance required to execute the avatar call process. However, the same identifier and the same address may be assigned as the MF that supports the avatar call process.
[0250] Step 7. The DCSF (or the DCSF at the request of the IMS AS) may allocate an MF capable of executing the avatar call process.
[0251] Step 8. The DCSF (or IMS AS) may respond with the identifier and address of the MF assigned to the DC AS.
[0252] Steps 9, 10. DC AS can request and receive performance information for the avatar call process from MF.
[0253] Step 11. Performance negotiation for the avatar call process between the first avatar call app, the second avatar call app, and MF can be conducted.
[0254] Step 12. After the performance negotiation is completed, the DC AS can instruct the MF to generate a cryptographic key.
[0255] Step 13. The DC AS may send a message (requestAddDelegator) to the first avatar calling app to enable MF to receive the delegation of avatar access rights granted to UE2 from UE1. The parameters of the message may include the original destination and the destination to be delegated.
[0256] Step 14. The first avatar calling app may create an MF delegated ASI with MF as the new recipient, using the avatar identifier and asset identifier, etc., that were allowed to the second avatar calling app.
[0257] Step 15. The first avatar calling app can transmit the delegated ASI to the DC AS.
[0258] Step 16. DC AS can transmit execution instructions for avatar processes negotiated with MF and MF delegated ASI, etc.
[0259] Referring to FIG. 7b, in step 17, avatar reception can be initiated for each avatar call entity.
[0260] Step 18. Avatar reception between the first avatar calling app and the BAR can be performed.
[0261] Step 19. Avatar reception between the second avatar calling app and the BAR can be performed.
[0262] Step 20. Avatar reception between MF and BAR can be performed.
[0263] Step 21. MF can request the reception of an avatar from the Base Avatar Cache (BAC), which is a temporary avatar storage on the network.
[0264] Step 22. BAC can pass the delegated ASI to BAR and request an avatar.
[0265] Steps 23, 24. BAR can verify ASI with MF's public key, encrypt the avatar with MF's public key, and transmit it to MF.
[0266] Step 25. BAC can respond to MF that data reception is complete.
[0267] Step 26. Part of the avatar call process is carried out in the first avatar call app.
[0268] Step 27. The final result of the process performed in the first avatar call app can be transmitted to MF.
[0269] Step 28. A part of the avatar call process is executed in MF using the outputs of the first avatar call app as inputs.
[0270] Step 29. The final result of the process performed in MF can be transmitted to the second avatar call app.
[0271] Step 30. A part of the avatar call process is performed in the second avatar call app using the outputs of MF as inputs.
[0272] Step 31. In DC AS, avatar call process performance negotiation is conducted between the first avatar call app and the second avatar call app.
[0273] Step 32. Part of the avatar call process is carried out in the first avatar call app.
[0274] Step 33. The final result of the process performed in the first avatar call app can be transmitted to the second avatar call app.
[0275] Step 34. In the second avatar call app, a part of the avatar call process is executed using the outputs of the first avatar call process as inputs.
[0276] <Avatar Storage 네트워크 저장소 동작 방법>
[0277] A method is proposed in which a network Base Avatar Repository (BAR) manages avatars by identifying the owner of an avatar, verifying the owner's instructions to share the avatar with other entities, and providing the avatar so that only the relevant other entities can access it.
[0278] For example, when a first terminal instructs the use of a first avatar in an avatar call with a second terminal, the BAR must be able to verify that the instruction was generated by the first terminal and must be able to provide the avatar so that only the second terminal can use it.
[0279] The Avatar Call Entity can generate avatar data through an internal device or external service. The generated avatar can be registered with the BAR through the Avatar Call Service before performing an avatar call.
[0280] An entity that creates and owns an avatar and registers it for an avatar currency service is called the Avatar Owner entity.
[0281] The Avatar Owner entity can request the DC AS to register an avatar (createAvatar).
[0282] The DC AS can forward a registration request from the Avatar Owner entity to the BAR and receive an Avatar ID for the new avatar from the BAR. The Avatar ID can be an identifier unique to the Avatar Owner entity, unique within the service scope of the DC AS, or unique to all avatars within the BAR. The BAR can generate a separate URL for uploading the avatar and return it along with the Avatar ID.
[0283] The DC AS can pass the received Avatar ID and URL to the Avatar Owner entity.
[0284] The Avatar Owner entity can record the Avatar ID within the avatar data, encrypt the avatar data with a private key, and transmit it to the BAR. (updateAvatar)
[0285] BAR can store received avatar data along with the avatar owner identifier (Owner ID) and public key.
[0286] BAR can provide a URL to access the avatar and a hash code of the received data within the response to the updateAvatar() message.
[0287] In response to avatar data requests from other avatar currency entities, BAR can decrypt the avatar data using the avatar owner's public key, encrypt it using the public key of each requesting avatar currency entity, and transmit it. Each avatar currency entity can decrypt the received avatar data using their own private key and use it.
[0288] Table 10: createAvatar()
[0289] createAvatar() public key The avatar owner's public key is entered. The public key can be exchanged via a channel encrypted by a BAR or DC AS. owner ID The avatar owner identifier is entered to generate an avatar identifier within the BAR of the avatar to be uploaded.
[0290] Table 11: updateAvatar()
[0291] updateAvatar() data: Data of the avatar being uploaded Avatar ID: Identifier of the avatar being uploaded
[0292] FIG. 8 is a flowchart for explaining the operation of entities related to an avatar registration request according to an embodiment of the present disclosure.
[0293] Referring to FIG. 8, the communication system may include a first UE, an IMS network, and a terminating network / second UE (Terminating Network / UE2). The second UE may belong to the terminating network.
[0294] The first UE may include a first Avatar Storage and a first Avatar app #1. The IMS network may include at least one of CSCF, IMS AS, DCSF, MF, BAC, DC AS, and BAR. The second UE belonging to the end network may include a second Avatar Storage and a second Avatar app #2.
[0295] The first avatar calling app may include functions for creating an avatar and registering it to an avatar calling service. The first avatar calling app may be provided and received from a DC AS that is an avatar calling service provider, or may be received in advance by the first UE. The reception of the first avatar calling app may be via a Bootstrap Data Channel. The app and the DC AS are connected via a Bootstrap Data Channel (BDC) or an Application Data Channel (ADC) and can transmit messages and data through it.
[0296] Step 1. An avatar can be created from the first avatar call entity.
[0297] Step 2. The first avatar calling app may forward an avatar registration request to the DC AS. UE1's public key may be forwarded along with it.
[0298] Step 3. DC AS can forward the registration request to BAR.
[0299] Step 4. BAR can generate an Avatar ID for the Owner ID and store the public key.
[0300] Step 5. The BAR can respond with the generated Avatar ID.
[0301] Step 6. The DC AS can respond with the generated Avatar ID.
[0302] Step 7. The first avatar calling app can insert the received Avatar ID into the avatar that created it. The format of the avatar data may provide the ability to store a unique identifier as an ID within the metadata.
[0303] Step 8. The first avatar calling app may instruct the first avatar storage to upload the avatar that has been created and assigned an identifier.
[0304] Step 9. The first avatar store can be encrypted with the UE1 private key and generate a hash code for data verification.
[0305] Step 10. The first avatar repository can upload encrypted avatar data to the URL of BAL.
[0306] Step 11. BAR can manage the received avatar data under Owner ID and verify the received data with a hash code.
[0307] Step 12. BAR can respond with a hash code after the upload of the avatar data is complete.
[0308] Step 13. The first avatar store can verify the hash code.
[0309] Step 14. The first avatar storage can respond to the first avatar calling app whether the upload was successful.
[0310] FIG. 9 is a block diagram of a terminal according to one embodiment of the present disclosure.
[0311] The terminal (900) is an electronic device capable of wireless communication and may include user equipment (UE), mobile phones, smartphones, tablets, Internet of Things devices having various form factors, etc., and can perform wireless communication with a base station through a wireless channel.
[0312] Referring to FIG. 9, the terminal (900) may include at least one transceiver (901) (hereinafter, transceiver), at least one processor (902) (hereinafter, processor), and at least one memory (903) (hereinafter, memory). The transceiver (901), processor (902), and memory (903) of the terminal (900) may operate according to at least one or a combination thereof of the methods corresponding to the above-described embodiments. However, the components of the terminal (900) are not limited to the examples of components shown in FIG. 9. In other embodiments, the terminal (900) may include additional components such as the above-described components or omit some components. Also, in some embodiments, the transceiver (901), processor (902), or memory (903) may be integrated into a single chip.
[0313] The transceiver (901) may be a communication circuit or communication circuitry that enables the terminal (900) to transmit and receive signals to and from a base station via cellular wireless communication. For example, the transceiver (901) may support at least one of various cellular wireless communication technologies including 3G, 4G LTE (long-term evolution), 5G NR (new radio), 6G, etc., and may include all subsequent generations of wireless communication.
[0314] According to one embodiment, the terminal (900) may include a plurality of transceivers, and if it supports EN-DC (E-UTRA-NR Dual Connectivity), it may include a first transceiver that supports 4G LTE wireless communication and a second transceiver that supports 5G NR wireless communication. According to another embodiment, if the terminal (900) supports NR-DC (NR Dual Connectivity), the terminal (900) may include a plurality of transceivers that support 5G NR wireless communication. According to another embodiment, if the terminal (900) supports short-range wireless communication, the terminal (900) may separately include a transceiver that supports at least one of a group of wireless communication protocol standards such as those defined by Bluetooth, wireless LAN, or WLAN networks (including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be).
[0315] According to one embodiment, the transceiver (901) may include various circuit structures used to transmit and receive signals to and from a base station via a wireless channel. The signals may include control information and data. For example, the transceiver (901) may be configured to include 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. The transceiver (901) may output the signal received via the wireless channel to a processor (902) and transmit the signal output from the processor (902) via the wireless channel.
[0316] The processor (902) can control the overall operation of the terminal (900) according to the embodiments of the present disclosure described above. The processor (902) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing operations. The processor (902) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (903) individually, collectively, or in any combination. Additionally, the processor (902) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.
[0317] The processor (902) is electrically, operatively, or communicatively coupled to the transceiver (901) so as to control the transceiver (901).
[0318] The processor (902) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (902) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (902) may be included in one chip, and another part of the processor (902) may be included in a separate chip. Alternatively, at least one processor may be included in other components, e.g., a transceiver (901) or a memory (903).
[0319] The processor (902) may perform, cause, or control the operation of a terminal to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (902) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (902) may control other components of the terminal (900) to perform various operations by executing computer programs, code, or instructions stored in memory (903).
[0320] Memory (903) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (903) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.
[0321] The memory (903) can be electrically, operatively, or communically coupled with the processor (902) and can be accessed by the processor (902).
[0322] A computer program, code, or instruction that can be executed by a processor (902) may be stored in the memory (903). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (902) may be stored in a single memory or separated and distributed across two or more memories. The processor (902) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (903).
[0323] According to an actual embodiment of the present disclosure, the operation of the terminal described below may be performed individually, collectively, or in any combination of at least one processor, a processing circuitry that does not execute instructions, or a component of a processing circuitry that does not execute instructions, through computer programs, codes, or instructions stored in memory (903).
[0324] FIG. 10 is a block diagram of a network node performing network functions according to one embodiment of the present disclosure.
[0325] A network node (1000) may include one or more network functions (NF) that constitute a core network (e.g., 5G core, 5GC) in a communication system, or entities (devices, devices, or servers, etc.) that perform part of the network functions. In this case, multiple NFs may be implemented within a single network node, or a single NF may be distributed and implemented across multiple network nodes. Additionally, when an NF is implemented within a network node, the NF may be implemented in the form of software, and in this case, a program for running the NF may be loaded into the memory of the network node (1000).
[0326] A network node (1000) may include at least one of a Call Session Control Function (CSCF), an IP Multimedia Subsystem Application Server (IMS AS), a Digital Content Service Function (DCSF), a Media Function (MF), a Digital Content Application Server (DC AS), and a Base Avatar Repository (BAR).
[0327] A single NF can be implemented as one or more instances and can operate by being distributed across the same network node or multiple network nodes. Here, the instance is a software unit that logically executes a specific network function and may be separate from physical hardware resources. Additionally, one or more NFs may be implemented as a single network slice to operate in order to satisfy the specifications required by a specific service.
[0328] The above NF may include any one of the Access and Mobility Management Function (AMF), Session Management Function (SMF), Local Session Management Function (L-SMF), User Plane Function (UPF), Local User Plane Function (L-UPF), Policy Control Function (PCF), Unified Data Management (UDM), Unified Data Repository (UDR), Network Exposure Function (NEF), Network Repository Function (NRF), Application Function (AF), Network Slice Selection Function (NSSF), Network Data Analytics Function (NWDAF), Network Slice Admission Control Function (NSACF), Authentication Server Function (AUSF), or Data Network (DN).
[0329] Referring to FIG. 10, a network node (1000) may include at least one network interface (1001), at least one processor (1002) (hereinafter, processor), and at least one memory (1003) (hereinafter, memory). As described above, the NF may be implemented in the form of a physical device such as the network node (1000), or may be implemented and executed in the form of a virtualized instance. When the NF is implemented in the form of an instance, it may not necessarily include physical components as illustrated in FIG. 10. In such cases, the instance may be composed of one or more logical functional units and represented logically.
[0330] According to at least one or a combination thereof of the methods corresponding to the above-described embodiments, the network interface (1001), processor (1002), and memory (1003) of the network node (1000) may be operated. However, the components of the network node (1000) are not limited to the examples of components shown in FIG. 10. In other embodiments, the network node (1000) may include additional components in addition to the above-described components or omit some components. Also, in one embodiment, the network interface (1001), processor (1002), or memory (1003) may be implemented in the form of a single chip.
[0331] The network interface (1001) collectively refers to the transmitting part and the receiving part of a network node and may be a communication circuit for transmitting and receiving signals with a terminal (user equipment, UE), a base station, or another network node. In this case, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for wired communication. For example, the network interface (1001) may include circuits, logic, hardware, etc. configured to exchange control plane messages or user plane messages with a terminal, a base station, or other core network nodes via wireless or wired communication. The network interface (1001) may operate using various protocols (e.g., NAS (Non-Access Stratum) protocol).
[0332] The processor (1002) can control the overall operation of the network node (1000) according to the embodiments of the present disclosure described above. In one embodiment, the processor (1002) may be implemented as one or more IC (integrated circuit or circuitry) chips and may perform various data processing operations. The processor (1002) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (1003) individually, collectively, or in any combination. Additionally, the processor (1002) may include a single-core processor or a multi-core processor, and in a specific implementation method, may be composed of a processor assembly including a plurality of processing circuits. Additionally, it should be noted that the processor (1002) may not necessarily be composed of physical hardware when the network function (1000) is implemented in an instance form according to another embodiment.
[0333] According to one embodiment, the processor (1002) is electrically, operatively, or communicatively coupled to the network interface (1001) so as to control the network interface (1001).
[0334] The processor (1002) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a particular embodiment, at least one part of the processor (1002) may be included in one chip, and another part of the processor (1002) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a network interface (1001) or memory (1003).
[0335] A processor (1002) may perform or control the operation of a network node (1000) to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (1002) may control the operation of a network node (1000) to exchange control plane messages or user plane messages with a terminal, base station, or other core network nodes via wireless or wired communication using various protocols (e.g., NAS protocol). To this end, the processor (1002) may control other components of the network node (1000) to perform various operations by executing computer programs, code, or instructions stored in memory (1003).
[0336] Memory (1003) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (1003) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.
[0337] According to one embodiment, the memory (1003) may be electrically, operatively, or communically coupled with the processor (1002) and may be accessed by the processor (1002).
[0338] A computer program, code, or instruction that can be executed by a processor (1002) may be stored in the memory (1003). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (1002) may be stored in a single memory or separated and distributed across two or more memories. The processor (1002) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (1003).
[0339] 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
In a method of operation of a first UE (user equipment) in a wireless communication system, Step of creating an avatar; A step of transmitting a registration request message requesting the registration of the above avatar to a DC AS (data channel application server) within an IMS (IP multimedia subsystem) network; A step of receiving a response message from the DC AS that includes an avatar ID corresponding to the above avatar; A step of associating the above avatar ID with the above avatar; and A method characterized by including the step of uploading avatar data related to the above avatar to a BAR (base avatar repository) within the above IMS network. In paragraph 1, A method characterized by further including the step of receiving from the BAR information for identifying the owner of the avatar (Owner ID), the identifier of the avatar (Avatar ID), and the identifier of an asset belonging to the avatar (Asset ID). In paragraph 1, A method characterized by further including the step of encrypting the avatar data with the private key of the first UE and generating a hash code for verifying the avatar data. In claim 1, the first UE includes avatar storage and an avatar call application, and A method characterized in that the above-mentioned avatar call application and the above-mentioned DC AS are connected via a bootstrap data channel or an application data channel to transmit data. In paragraph 1, The method further includes the step of transmitting avatar selection information to a second UE within a terminating network, and A method characterized by comprising at least one of the following: information for identifying the owner of the avatar (Owner ID), an identifier of the avatar (Avatar ID), a time at which the avatar selection information is published (asiPublishingTime), an identifier of an asset belonging to the avatar (Asset ID), or an identifier of a LoD (level of details) assigned to the asset (Lode ID). A method according to claim 5, wherein the avatar selection information comprises at least one of information for identifying an avatar call partner (Target ID), a start time when the avatar selection information becomes valid (access start time), an identifier of the avatar selection information (asiIdentifier), or information regarding whether the avatar data is retained after a call (postCallPolicy). In paragraph 5, A step of converting the user's posture or facial expression into an animation command, which is a command to move the avatar; and A method characterized by including the step of transmitting the above animation command to the second UE. In paragraph 1, A step of exchanging avatar call process performance with the second UE and negotiating at least one parameter for the avatar call process; A step of configuring a scene including the above avatar (scene description); and A method characterized by further including the step of executing the second UE and the avatar call processor. In a first UE (user equipment) in a wireless communication system, At least one transceiver; At least one processor connected to communicate with the above at least one transceiver; and It includes at least one memory that is communicably connected to the at least one processor and stores instructions that are executable individually or in combination by the at least one processor. The above command is the above first UE: Create an avatar, and A registration request message requesting the registration of the above avatar is sent to a DC AS (data channel application server) within the IMS (IP multimedia subsystem) network, and Receive a response message from the DC AS including an avatar ID corresponding to the above avatar, and Associate the above avatar ID with the above avatar, and A first UE characterized by uploading avatar data related to the above avatar to a BAR (base avatar repository) within the above IMS network. In paragraph 9, the above command is that the above 1 UE: A first UE characterized by receiving information for identifying the owner of the avatar (Owner ID), an identifier of the avatar (Avatar ID), and an identifier of an asset belonging to the avatar (Asset ID) from the BAR. In paragraph 9, the above command is that the above 1 UE: A first UE characterized by encrypting the avatar data with the private key of the first UE and generating a hash code for verifying the avatar data. In paragraph 9, the first UE includes avatar storage and an avatar call application, and A first UE characterized in that the above-mentioned avatar call application and the above-mentioned DC AS are connected via a bootstrap data channel or an application data channel to transmit data. In paragraph 9, the above command is that the above 1 UE: To transmit avatar selection information to a second UE within a terminating network, and The first UE is characterized by the fact that the above avatar selection information includes at least one of information for identifying the owner of the avatar (Owner ID), an identifier of the avatar (Avatar ID), a time when the above avatar selection information is published (asiPublishingTime), an identifier of an asset belonging to the avatar (Asset ID), or an identifier of a LoD (level of details) assigned to the asset (Lode ID). The first UE according to claim 13, wherein the avatar selection information comprises at least one of information for identifying an avatar call partner (Target ID), a start time when the avatar selection information becomes valid (access start time), an identifier of the avatar selection information (asiIdentifier), or information regarding whether the avatar data is retained after a call (postCallPolicy). In Paragraph 13, the above command is that the above 1 UE: Converts the user's posture or facial expression into an animation command, which is a command to move the avatar, and A first UE characterized by transmitting the above animation command to the second UE.
