Method and device for granting authority to use avatar expression information on network storage

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to an embodiment of the present disclosure, when an avatar service utilizing avatar expression information is requested in an IMS-DC service, authorization for use of specific avatar expression information stored on a network storage may be granted through an HSS or DC AS (XS AS) on the basis of avatar expression information (Avatar ID) and terminal information (UE ID).

Description

Method and device for granting authorization for using avatar expression information on network storage

[0001] The present disclosure relates to an avatar call session connection service utilizing avatar storage on a network. In addition, the present disclosure relates to a method and device for supporting authorization for use of avatar representation information in avatar storage on a network during a bootstrap data channel setup signaling procedure and / or an application data channel setup signaling procedure for an avatar service connection based on IMS-DC (IP (internet protocol) multimedia subsystem-data channel).

[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 the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

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

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

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The IMS (IP (internet protocol) multimedia subsystem) system is a system for transmitting IP (internet protocol)-based multimedia, and various services such as VoLTE (voice over LTE) and VoNR (voice over NR) are provided through the existing IMS network linked to the LTE or 5G network. The purpose of the IMS data channel service is to provide various additional services such as user location information transmission and screen sharing using separate applications in addition to the existing voice or video-based services by using the data channel linked to IMS, i.e., the IMS-DC service, in addition to the existing RTP (real-time transport protocol)-based voice, video, and text services. In order to use the additional services using the data channel within the IMS data network or the standalone IMS data channel service, the terminal can transmit a signaling message containing a request for a data channel application and related configuration information for a data channel-based service to the network through the bootstrap data channel setup signaling process. The IMS data channel network, upon receiving the above signaling message, may transmit application or application list information to the terminal based on the user or service provider's settings and request information received from the terminal, thereby enabling the terminal to download applications for the data channel service. The terminal may then select an appropriate data channel application based on the terminal's capabilities and user selection based on the application or application list information received from the network, and request the appropriate data channel application. Furthermore, the network may allocate a separate media function entity within the network during the bootstrap data channel setup process to support the download of a specific application requested by the terminal.The media function entity can receive data channel application-related information (Replacement HTTP (Hyper Text Transfer Protocol) Uniform Resource Locator (URL) representing the application list offered via the MDC1 interface) that can be converted into data channel application information through the media resource management service operation during the bootstrap data channel setup process. Afterwards, the media function entity can receive specific data channel application information selected and requested by the terminal through the Mb interface, and then convert the data channel application download request information into HTTP URL information that can be recognized by the IMS data channel network (e.g., DSCF) to perform application download support operation of the terminal. Multiplexed data streams can be supported depending on the type of service. The terminal can receive each data channel application through the bootstrap connection process and simultaneously receive data channel application-related information. Thereafter, the terminal can perform the application data channel setup signaling operation for the data channel connection request of the received data channel application. The application data channel setup signaling message can also transmit application binding information including configuration information for supporting a specific application.Based on the above information received from the terminal, the network can perform at least one application data channel connection operation among three types of application data channel connections: terminal to terminal (P2P Application Data Channel Setup), terminal to application server (P2A Application Data Channel Setup), or terminal to terminal connection via application server (P2A2P Application Data Channel Setup).

[0009] The present disclosure provides a method and device for granting authorization to access service user-related avatar expression information supported by an avatar storage entity on a network when connecting an avatar call session based on an IMS data channel service utilizing avatar storage on a network. Furthermore, to address privacy issues such as when requesting and managing avatar information from a terminal, a method and device for receiving avatar expression data using an avatar ID and managing avatar expression information within a network are provided.

[0010] According to one embodiment of the present disclosure, a method of a DCSF (data channel signaling function) entity in an IMS-DC service comprises the steps of: receiving, by an IMS AS (application server), session establishment request event information for downloading avatar expression information or a list of avatar expression information from a digital asset container or avatar storage storing an application or a list of applications supporting an avatar service and user-related avatar expression information based on a bootstrap channel session connection request message including avatar service-related information including an application ID or a service ID from a UE (user equipment); checking and determining access authority for avatar storage having user-related avatar expression information in a service requested by a terminal based on avatar expression-related information such as an event ID (service ID) and an Application ID and a terminal ID (UE ID); receiving avatar expression information or a list of avatar expression information provided from the avatar storage based on the request information; setting a proxy for transmitting appropriate avatar expression data based on the avatar expression information requested by the terminal (e.g.,A step of generating alternative HTTP URL media resource information for receiving actual avatar expression data as DCSF based on avatar expression information transmitted through an HTTP proxy and an avatar ID, and transmitting the same to an IMS AS; A step of receiving media change request event information for connection of an application data channel of an avatar service-related service generated based on a data channel session connection request message including avatar expression-related information such as an avatar ID, avatar model descriptor, and version ID, and avatar service-related information including an Application ID or Service ID; A step of requesting an HSS (home subscriber server) to confirm authorization information on whether a service user can use avatar expression information related to the service user from the avatar storage based on avatar expression-related information such as an avatar ID transmitted from a terminal, and a step of using the service based on the user's subscription information in the HSS.A step for receiving permission information for allowing access to user-related avatar expression information within a network storage by 228 users; A step for requesting download of avatar expression information directly from a DAC or avatar storage in a DCSF based on the access permission information of the avatar expression information transmitted from an HSS; Or, if avatar expression information can be downloaded through a 3rd party DC AS (data channel application server) depending on the location of the DAC or avatar storage, a step for requesting transmission of avatar expression information by transmitting the access permission information of the avatar expression information transmitted from the HSS to the DC AS; A step for receiving the result of creating and updating media resources related to avatar expression information from an IMS AS to a Local MF (media function) and, if necessary, MDC2 Endpoint information from the DC AS depending on the Application DC type; A step for requesting a connection to the corresponding DC AS and requesting an MDC2 Endpoint if an Application DC connection type utilizing the DC AS, such as a P2A or P2A2P connection, exists; In the case of an Application DC connection type utilizing a DC AS, such as a P2A or P2A2P connection, the method includes: receiving a connection request result and an MDC2 Endpoint of a DC AS from the DC AS; transmitting the information regarding the MDC2 Endpoint for each DC AS received from the DC AS to an IMS AS for transmission to an MF; receiving a result of updating an MDC2-related media resource in the MF from the IMS AS; and transmitting a session connection request event result including avatar expression information or a list of avatar expression information in response to a session connection request event transmitted from the IMS AS to the IMS AS.

[0011] According to one embodiment of the present disclosure, a method of a first terminal for an avatar service in a wireless communication system may include the steps of receiving an avatar identifier (avatar ID) through a bootstrap data channel, receiving avatar expression information from a media function (MF) based on the avatar identifier, performing avatar animation based on the avatar expression information, and transmitting video information converted based on the avatar animation to a second terminal.

[0012] In addition, according to one embodiment of the present disclosure, a method of a second terminal for an avatar service in a wireless communication system may include a step of receiving avatar expression information of a first terminal from an MF (media function), a step of receiving avatar movement information of the first terminal through an application data channel, and a step of performing avatar animation based on the avatar expression information and the avatar movement information.

[0013] In addition, according to one embodiment of the present disclosure, a first terminal for an avatar service in a wireless communication system includes a transceiver and at least one processor, and the at least one processor can control to receive an avatar identifier (avatar ID) through a bootstrap data channel, receive avatar expression information from a media function (MF) based on the avatar identifier, perform avatar animation based on the avatar expression information, and transmit video information converted based on the avatar animation to a second terminal.

[0014] In addition, according to one embodiment of the present disclosure, a second terminal for an avatar service in a wireless communication system includes a transceiver and at least one processor, and the at least one processor receives avatar expression information of a first terminal from an MF (media function), receives avatar movement information of the first terminal through an application data channel, and controls to perform avatar animation based on the avatar expression information and the avatar movement information.

[0015] A method and device according to an embodiment of the present disclosure can receive avatar expression information requested by a service user from an avatar storage function entity based on avatar service-related information (Avatar ID, Avatar Model descriptor, Avatar version, Avatar service Info, etc.) and user-related information (Calling ID, Called ID) transmitted from a DCSF based on requirements of an avatar-based IMS-DC service in a terminal, receive access authority information for receiving avatar expression information, receive authorization information for using avatar expression information to receive user-related avatar expression information from avatar storage, and request transmission of avatar expression information to an avatar storage function entity or DAC based on the avatar expression information use authority information, and perform a download operation of the avatar expression information to a terminal or a network entity (e.g., MF).

[0016] FIG. 1 is a diagram illustrating a network structure and interface of a 5G system according to one embodiment of the present disclosure.

[0017] FIG. 2 is an example of an IMS-DC structure that provides a data channel service based on an IMS service according to one embodiment of the present disclosure.

[0018] FIG. 3 is an example of a reference structure that constitutes an avatar-based service according to one embodiment of the present disclosure.

[0019] FIG. 4 is an example of a structure for explaining an operation for a terminal to request avatar expression information and receive related information through a bootstrap data channel setup signaling process in an avatar service using network avatar storage according to one embodiment of the present disclosure.

[0020] FIG. 5 is a flowchart illustrating a process of performing an operation to create or update the information by using an HSS (home subscriber server) to store avatar service-related profile information including specific user-related avatar information, service information, avatar use restriction information, etc., in terminal subscription information in a service provider server (AF, application function) that manages avatar expression information according to one embodiment of the present disclosure.

[0021] FIG. 6 is a flowchart illustrating an operation of registering a service and granting access rights to grant a service provider that manages avatar expression information according to one embodiment of the present disclosure the right to access network storage that stores avatar expression information in a specific service and / or application.

[0022] FIGS. 7a, 7b, and 7c are flowcharts illustrating an operation of requesting access to network storage storing avatar expression information and receiving avatar expression information or an avatar expression information list based on the request during a data channel signaling process according to one embodiment of the present disclosure.

[0023] FIGS. 8a and 8b are flowcharts for explaining a method and operation for granting usage rights based on an avatar ID and a terminal ID for each service type during an application data channel connection process for using an avatar service in a terminal according to one embodiment of the present disclosure.

[0024] FIGS. 9a and 9b are flowcharts for explaining a method and operation for granting usage rights based on an avatar ID and a terminal ID for each service type during an application data channel connection process for using an avatar service in a terminal according to one embodiment of the present disclosure.

[0025] FIGS. 10a, 10b, and 10c are flowcharts for explaining a method and operation for granting usage rights based on an avatar ID and a terminal ID for each service type during an application data channel connection process for using an avatar service in a terminal according to one embodiment of the present disclosure.

[0026] FIG. 11 is a diagram illustrating a configuration of a network entity performing another network function in one embodiment of the present disclosure.

[0027] FIG. 12 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.

[0028] Hereinafter, one embodiment of the present disclosure will be described in detail with reference to the attached drawings.

[0029] In describing this disclosure, descriptions of technical details that are well-known in the technical field to which this disclosure pertains and are not directly related to this disclosure will be omitted. This is to avoid obscuring the gist of this disclosure by omitting unnecessary explanations and to convey it more clearly. Furthermore, the terms described below are defined based on their functions in this disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0030] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0031] Hereinafter, a base station (BS) is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B (or an xNode B (where x is an alphabet including g or e)), a wireless access unit, a base station controller, a satellite, an airborn, or a node on a network. A user equipment (UE) may include a mobile station (MS), a vehicle, a satellite, an airborn, a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, a downlink (DL) is a wireless transmission path of a signal transmitted from a base station to a terminal, and an uplink (UL) means a wireless transmission path of a signal transmitted from a terminal to an air station. Additionally, a sidelink (SL) may exist, which means a wireless transmission path of a signal transmitted from a terminal to another terminal.

[0032] In addition, although LTE, LTE-A, or 5G systems may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, this may include 5G-Advance or NR-Advance, or 6th generation mobile communication technology (6G) developed after 5G mobile communication technology (or new radio, NR), and the 5G described below may also include existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly deviate from the scope of the present disclosure, as determined by a person having skilled technical knowledge.

[0033] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0034] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0035] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0036] 3GPP, responsible for cellular mobile communications standards, is standardizing a new core network architecture called 5G Core (5GC) to facilitate the evolution of 4G LTE systems to 5G systems. Compared to the Evolved Packet Core (EPC), the network core for 4G, 5GC supports the following differentiated features:

[0037] 5GC introduces the Network Slice feature. As a requirement of 5G, 5GC must support a variety of terminal types and services, such as enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine Type Communications (mMTC). These terminals and services each have different requirements for the core network. For example, eMBB services may require high data rates, while URLLC services may require high reliability and low latency. To meet these diverse service requirements, Network Slice technology has been proposed.

[0038] Network slicing can refer to a method of virtualizing a single physical network to create multiple logical networks (e.g., network slices). An activated network slice can be called a network slice instance, and each network slice instance (NSI) can have different characteristics. By configuring a network function (NF) for each NSI according to its characteristics, mobile carriers can satisfy various service requirements according to terminals / services. For example, mobile carriers can efficiently support various 5G services (e.g., eMBB, URLLC, or mMTC) by allocating an NSI that matches the characteristics of the service required for each terminal.

[0039] 5GC can easily support the network virtualization paradigm by separating the mobility management function from the session management function. In 4G LTE, all terminals can receive services from the network through signaling exchanges with a single core entity called the mobility management entity (MME), which is responsible for registration, authentication, mobility management, and session management. In 5G, the number of terminals (including MTC terminals) will explode, and the mobility and traffic / session characteristics that must be supported depending on the terminal type will become more specialized. Therefore, supporting all functions from a single entity (such as the MME) will inevitably reduce scalability by adding entities for each required function. Therefore, various functions are being developed based on a structure that separates the mobility management function from the session management function to improve scalability in terms of the functional / implementation complexity and signaling load of the core entity responsible for the control plane.

[0040] FIG. 1 is a diagram illustrating a network structure and interface of a 5G system according to one embodiment of the present disclosure.

[0041] A network entity included in the network structure of the 5G system of Fig. 1 may include a network function (NF) depending on the system implementation.

[0042] Referring to FIG. 1, the network structure of a 5G system may include various network entities. For example, the 5G system may include an authentication server function (AUSF) entity (108), an access and mobility management function (AMF) entity (103), a session management function (SMF) entity (105), a policy control function (PCF) entity (106), an application function (AF) entity (107), a unified data management (UDM) entity (109), a data network (DN) entity (110), a network exposure function (NEF) entity (111), a network slicing selection function (NSSF) entity (114), a network repository function (NRF) entity (115), a network data analytics function (NWDAF), and an edge application service domain repository. It may include a domain repository (EDR), an edge application server (EAS), an EAS discovery function (EASDF), a user plane function (UPF) entity (104), a (radio) access network ((R)AN) (102), and a terminal, for example, a user equipment (UE) (101).

[0043] Each NF entity of the 5G system (100) supports the following functions.

[0044] AUSF (108) processes and stores data for authentication of UE (101).

[0045] AMF (103) provides functions for access and mobility management per UE, and one UE can basically be connected to one AMF. Specifically, the AMF (103) provides signaling between CN nodes for mobility between 3GPP access networks, termination of a radio access network (RAN) CP interface (i.e., N2 interface), termination of non-access stratum (NAS) signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE reachability (including control and performance of paging retransmission), mobility management control (subscription and policy), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (for AMF events and interfaces to the LI system), provision of forwarding of session management (SM) messages between UE and SMF, transparent proxy for SM message routing, access authentication, access authorization including roaming authorization check. It supports functions such as authorization, provision of SMS message transmission between UE and SMSF, security anchor function (SAF) and / or security context management (SCM). Some or all of the functions of an AMF entity (103) may be supported within a single instance of an AMF entity.

[0046] DN (110) refers to, for example, an operator service, Internet access, or a third-party service. DN (110) transmits a downlink protocol data unit (PDU) to the UPF entity (104) or receives a PDU transmitted from the UE (101) from the UPF entity (104).

[0047] The PCF entity (106) receives information about packet flows from the application server and provides a function to determine policies such as mobility management and session management. Specifically, the PCF entity (106) supports functions such as supporting a unified policy framework for controlling network operations, providing policy rules so that control plane function entity(ies) (e.g., AMF entity, SMF entity, etc.) can enforce the policy rules, and implementing a front end for accessing related subscription information for policy determination within a user data repository (UDR).

[0048] The SMF entity (105) provides a session management function, and when the UE (101) has multiple sessions, each session can be managed by a different SMF entity. Specifically, the SMF entity (105) is responsible for session management (e.g., session establishment, modification, and termination, including tunnel maintenance between the UPF entity (104) and the (R)AN (102) node), UE IP address allocation and management (optionally including authentication), selection and control of UP functions, setting up traffic steering to route traffic from the UPF entity (104) to the appropriate destination, termination of the interface to policy control functions, enforcement of the control portion of policy and quality of service (QoS), lawful intercept (for SM events and interfaces to the LI system), termination of the session management (SM) portion of NAS messages, downlink data notification, initiation of AN (access network) specific SM information (delivered to the (R)AN (102) via N2 via the AMF entity (103)), determination of the session and service continuity (SSC) mode of the session, and roaming. Supports functions such as functions, etc. Some or all functions of an SMF entity (105) can be supported within a single instance of an SMF entity.

[0049] The UDM entity (109) stores user subscription data, policy data, etc. The UDM entity (109) includes two parts: an application front end (FE) and a user data repository (UDR).

[0050] The FE (front end) includes the UDM FE, which is responsible for location management, subscription management, and credential processing, and the PCF entity, which is responsible for policy control. The UDR stores the data required for the functions provided by the UDM-FE and the policy profiles required by the PCF entity. The data stored in the UDR includes user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data. The UDM-FE accesses the subscription information stored in the UDR and supports functions such as authentication credential processing, user identification handling, access authentication, registration / mobility management, subscription management, and SMS management.

[0051] The UPF entity (104) forwards the downlink PDU received from the DN (110) to the UE (101) via the (R)AN (102), and forwards the uplink PDU received from the UE (101) via the (R)AN (102) to the DN (110). Specifically, the UPF entity (104) supports functions such as an anchor point for intra / inter RAT mobility, an external PDU session point for interconnection to the Data Network, a user plane part of packet routing and forwarding, packet inspection and policy rule enforcement, an uplink classifier to support lawful intercept, traffic usage reporting, routing of traffic flows to the Data Network, a branching point to support multi-homed PDU sessions, QoS handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement), uplink traffic validation (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering. Some or all of the functions of a UPF entity (104) may be supported within a single instance of a UPF.

[0052] The AF entity (107) interacts with the 3GPP core network to provide services (e.g., supporting functions such as application impact on traffic routing, access to network capability exposure, and interaction with the policy framework for policy control).

[0053] (R)AN(102) is a general term for a new radio access network that supports both evolved E-UTRA, an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB).

[0054] The gNB provides functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to the UE in uplink / downlink (i.e., scheduling), IP (internet protocol) header compression, encryption and integrity protection of user data streams, selection of an AMF upon attachment of the UE if routing to the AMF is not determined from the information provided to the UE, routing of user plane data to UPF(s), routing of control plane information to the AMF, connection setup and teardown, scheduling and transmission of paging messages (originating from the AMF), scheduling and transmission of system broadcast information (originating from the AMF or operating and maintenance (O&M)), measurement and measurement reporting setup for mobility and scheduling, transport level packet marking in uplink, session management, support for network slicing, and QoS flows. It supports features such as mapping to management and data radio bearers, support for UEs in inactive mode, distribution of NAS messages, NAS node selection, radio access network sharing, dual connectivity, and tight interworking between NR and E-UTRA.

[0055] UE (101) refers to a user equipment. The user equipment may be referred to by terms such as terminal, mobile equipment (ME), or mobile station (MS). Furthermore, the user equipment may be a portable device such as a laptop, mobile phone, personal digital assistant (PDA), smartphone, or multimedia device, or may be a non-portable device such as a personal computer (PC) or vehicle-mounted device.

[0056] The NEF (111) provides a means to securely expose services and capabilities provided by 3GPP network functions, for example, for third parties, internal exposure / re-exposure, application functions, and edge computing. The NEF (111) receives information from other NF (s) (based on the exposed capability(s) of other NF (s)). The NEF (111) can store the received information as structured data using a standardized interface to a data storage network function. The stored information can be re-exposed to other NF entity(s) and AF entity(s) by the NEF entity (111) and used for other purposes, such as analysis.

[0057] EASDF is an NF that can add an ECS (EDNS (extension mechanisms for DNS) client subnet) option that can be expressed as the address of a DNS server to which a DNS (domain name system) request of a terminal is forwarded, and an IP subnet address to be added when forwarding a DNS request of a terminal, for each FQDN (fully qualified domain name). EASDF receives EAS (exchange active sync) domain configuration information from EDR, and processes a DNS request message received from a terminal according to the received information. In addition, EASDF is an NF that receives a terminal IP address, location information of the terminal within 3GPP, DNS message processing rules, and DNS message reporting rules from an SMF (105), processes a DNS Query message received from a terminal, a DNS response message received from a DNS server, and transmits information in a DNS message and statistical information processed therefrom to the SMF (105) according to the DNS message reporting rules.

[0058] NRF (115) supports service discovery. It receives NF discovery requests from NF instances and provides information about discovered NF instances to the NF instances. It also maintains available NF instances and the services they support.

[0059] Meanwhile, for convenience of explanation, FIG. 1 illustrates a reference model for a case where a UE (101) accesses one DN (110) using one PDU session, but the present disclosure is not limited thereto.

[0060] A UE (101) can access two (i.e., local and central) data networks simultaneously using multiple PDU sessions. In this case, two SMFs can be selected for different PDU sessions. However, each SMF can have the ability to control both the local UPF and the central UPF within the PDU session.

[0061] Additionally, the UE (101) may simultaneously access two (i.e., local and central) data networks provided within a single PDU session.

[0062] In the 3GPP system, a conceptual link connecting NFs within a 5G system is defined as a reference point. For example, the reference point(s) included in the 5G system (100) of FIG. 1 are as follows.

[0063] - N1: Reference point between UE (101) and AMF (103)

[0064] - N2: Reference point between (R)AN(102) and AMF(103)

[0065] - N3: Reference point between (R)AN(102) and UPF(104)

[0066] - N4: Reference point between SMF (105) and UPF (104)

[0067] - N5: Reference point between PCF (106) and AF (107)

[0068] - N6: Reference point between UPF (104) and DN (110)

[0069] - N7: Reference point between SMF (105) and PCF (106)

[0070] - N8: Reference point between UDM (109) and AMF (103)

[0071] - N10: Reference point between UDM (109) and SMF (105)

[0072] - N11: Reference point between AMF (103) and SMF (105)

[0073] - N12: Reference point between AMF (103) and AUSF (108)

[0074] - N13: Reference point between UDM (109) and AUSF (108)

[0075] - N14: Reference point between two AMFs (103)

[0076] - N15: Reference point between PCF and AMF in non-roaming scenario, reference point between PCF and AMF in visited network in roaming scenario.

[0077] - Nx: Reference point between SMF(105) and EASDF

[0078] - Ny: Reference point between NEF (EDF) (111) and EASDF

[0079] FIG. 2 is an example of an IMS-DC structure that provides a data channel service based on an IMS service according to one embodiment of the present disclosure.

[0080] In the above structure, the terminal can transmit a SIP (session initiation protocol) INVITE message to an existing CSCF, such as a P-CSCF (proxy - call session control function) and an S-SCSF (serving - call session control function), to request a call session connection. The SIP INVITE message can include media-related parameters and multiplexing-related requirement information in the SDP (Session Description Protocol) and transmit them together to the network. In addition, the terminal can transmit an SDP offer including bootstrap information together with an SDP offer for connecting an existing video or audio session, in the SIP INVITE message, in order to use an IMS data channel service.

[0081] The S-CSCF, which has received the SIP INVITE including the above SDP information, can forward the contents of the bootstrap data channel SDP offer for a data channel service connection request to the IMS AS (application server) if the SIP INVITE contains a bootstrap data channel SDP offer. At this time, the S-CSCF checks whether the terminal or network supports IMS-DC based on the contents of the received bootstrap-related SDP offer. If both sides support the data channel, the S-CSCF can decide to forward the information for the bootstrap data channel connection for the data channel connection to the IMS AS. The IMS AS, which has received the bootstrap-related SDP offer message from the S-CSCF, can first check with the HSS (home subscriber server) whether the UE or subscriber can use the data channel service. If the user cannot use the data channel based on the user profile of the user, the MMTel (multimedia telephony) session setup operation can be performed without connecting the data channel through the general IMS process. Additionally, if the user cannot use a data channel-based service, the IMS AS can update the SIP INVITE message received from the S-CSCF by deleting the DC (data channel)-related media information in the SIP INVITE message, and then forward the updated SIP INVITE message to the S-CSCF.

[0082] If the service user can use the service based on the IMS data channel, data channel bootstrapping can be performed through a data channel call request with the data channel signaling function (DCSF). The IMS AS can select a DCSF by performing discovery and selection of a DCSF instance from the NRF based on the local configuration of the network operator or information transmitted from the UE. The IMS AS can transmit a session event control notification (SessionEventControl_Notify) message containing information such as SessionEstablishmentRequestEvent, Session ID, CallingID, CalledID, SessionCase, Event initiator, MediaInfoList, and DC Stream ID to the DCSF selected through the above process.

[0083] Upon receiving a DC control request from an IMS AS, the DCSF can make policy decisions on how to create a bootstrap data channel based on the relevant parameters in the DC control request message. Furthermore, the DCSF can determine MDC1 media information to enable the UE to download applications via the MF or MRF.

[0084] Based on the above decision information, DCSF can forward a MediaControl_MediaInstruction message containing information such as SessionID and MediaInstructionSet to the IMS AS. DCSF can also forward the MediaInstructionSet to the IMS AS, including the MDC1 media endpoint address, DC stream ID, and alternative information such as the URL of the application list transmitted on the MDC1 interface. Based on this, DCSF can provide the IMS AS with a policy on how to create a bootstrap data channel using MF on the originating and terminating sides.

[0085] IMS AS can select MF through a process of searching and selecting MF instance or enhanced MRF supporting local configuration or DC media capabilities using NRF.

[0086] The IMS AS can forward a list of Media Termination Descriptors to the MF selected in the above process via the Nmf_MRM_Create message. The IMS AS can request the creation of two different Media Terminations. One Media Termination may represent local bootstrap media-related information, and the other may represent remote bootstrap media-related information to be provided to a remote UE. Each Media Termination may include resource allocation request information for the Mb and MDC1 interfaces. The MF may forward the results of the negotiation of the corresponding data channel media resource information to the IMS AS.

[0087] An IMS AS may send a response to a MediaInstruction request from the DCSF. The response message may include information regarding the result of the above operation and information regarding the MDC1 data channel media resource information negotiation.

[0088] DCSF can store media resource information in a response message to a MediaInstruction request received from an IMS AS and forward a response message related to a data channel connection notification (SessionEventControl_Notify) request from the IMS AS to the IMS AS.

[0089] The IMS AS can forward a SIP INVITE message containing an updated SDP offer with media information from the MF or enhanced MRF to the S-CSCF. The S-CSCF can forward the SIP INVITE message containing the received updated SDP offer to the remote network and UE#2.

[0090] UE#2 and the terminating network can forward the SDP response related to the bootstrap data channel to the originating network in an 18X response message. Based on the received SDP response message, the MF or enhanced MRF can update the data channel media resource information of UE#2. Afterwards, UE#2 and the terminating network can send a 200 OK response message indicating the successful completion of the request.

[0091] The IMS AS can notify the DCSF of successful session connection-related event information by sending a SessionEventControl Notify message containing SessionEstablishmentSuccessEvent, SessionID, and MediaInfoList. After receiving a response message for the successful session connection event notification from the DCSF, the IMS AS can send a 200 OK message to UE#1, indicating that the bootstrap data channel has been connected. This allows the bootstrap data channel connection to be established between UE#1, UE#2, and the originating MF or enhanced MRF. Afterwards, UE#1 and UE#2 can request data channel applications by sending an application request message to the MF or enhanced MRF. If the multi-DC application supports it, the application list can be requested. The MF or MRF can change the root URL to application-related URL information based on the replacement URL information received from the DCSF. Afterwards, the MF can forward the application request message received from the UE to the DCSF. DCSF can provide a list of applications or appropriate data applications to UE#1 and UE#2, depending on the UE's data channel processing capabilities and selection. Depending on the MF's location, if terminating MF or MRF is used, the above process can be performed through terminating DCSF, and the appropriate data channel application can be downloaded.

[0092] After the IMS session and bootstrap data channel connection and data channel application are downloaded to UE#1 and UE#2, UE#1 can send a SIP reINVITE message containing the updated SDP to the IMS AS. The updated SDP may include not only bootstrap data channel information, but also application data channel request and related DC application binding information.

[0093] Based on user subscription data information, the IMS AS can determine whether to notify the DCSF of a media change request event. Once the IMS AS has decided to notify the DCSF of the event, it can forward the SessionEventControl_Notify message to the DCSF, containing the MediaChangeRequest Event, Session ID, Event Direction, Event Initiator, and Media Info List.

[0094] After receiving the session event notification message, the DCSF can determine the policy on how to handle the application data channel connection request based on the relevant parameters conveyed in the notification message and the network operator's policy. If UE#2 is the target endpoint and does not require an anchor of the local MF or enhanced MRF, the DCSF can decide to add the application data channel media descriptor to the SDP offer. If the MF or enhanced MRF is required as the anchor of the application data channel, the DCSF can forward the Nimsas_MediaControl message to the IMS AS to instruct the IMS AS to perform the allocation of data channel media resources of the MF or enhanced MRF.

[0095] DCSF can forward a response to the Session Event Notification message to the IMS AS. The IMS AS can then forward a SIP reINVITE message to the originating S-CSCF, which can then forward it to the terminating network and UE#2.

[0096] The 200 OK response can be included in the SDP response related to the application data channel from UE#2 and the terminating network and forwarded to the originating network. Afterwards, the IMS AS, which receives the SDP offer response message including the 200 OK response from the terminating network, can notify the DCSF of the successful data channel change. The DCSF can send a response to the notification to the IMS AS, and the IMS AS can then forward the 200 OK response to UE#1 through the originating S-CSCF and P-CSCF. At this time, the P-CSCF of the originating network can perform the QoS procedure of the application data channel media based on the SDP response information including the 200 OK response. UE#1 can send an ACK to the terminating network. Through the above process, the application data channel connection operation between UE#1 and UE#2 can be performed.

[0097] FIG. 3 is an example of a reference structure that constitutes an avatar-based service according to one embodiment of the present disclosure.

[0098] In Fig. 3, the location where each functional entity within the reference structure operates may vary depending on the performance and scenario of the terminal requesting the avatar service and the network transmitting it.

[0099] For example, if avatar creation is supported on the terminal, a base avatar generation functional entity and an avatar animation data generation functional entity can be located on the terminal based on data captured from the camera. In addition, if the terminal can directly receive or know information about the space where the avatar will be located, provided by the other terminal or application server, through feedback, etc., a scene management functional entity can be located on the terminal.

[0100] If the terminal only supports base avatar creation and the avatar animation data creation function is provided by the network, the terminal may have a base avatar creation function entity that supports creation of captured data or pre-created base avatar data. Afterwards, depending on the camera method supported by the terminal (e.g., Video or depth), video or feature-based data is transmitted to the avatar animation data creation function entity within the network, so that avatar animation data expressing the avatar's movements can be generated based on the data transmitted from the terminal. As described above, each function entity can be set by the terminal selecting an appropriate data channel application during the bootstrap data channel setup signaling process depending on the performance of the terminal or network, or by the terminal transmitting an appropriate function entity and related information to the network during the application data channel setup signaling process after selecting a basic data channel application.

[0101] In an embodiment of the present disclosure, depending on the settings of the service provider, base avatar information can be stored directly in the terminal, and when an avatar-related call session is established, data can be directly transmitted to the network or the counterpart terminal, or avatar expression information can be transmitted to the network or the counterpart terminal through avatar storage within the network.

[0102] FIG. 4 is an example of a structure for explaining an operation for a terminal to request avatar expression information and receive related information through a bootstrap data channel setup signaling process in an avatar service using network avatar storage according to one embodiment of the present disclosure.

[0103] In FIG. 4, the terminal can receive both data channel application information and avatar expression information from the DCSF through the bootstrap data channel setup signaling process. To this end, the terminal can basically include a bootstrap DC stream ID, a Calling ID, a Called ID, and Media info including data channel application-related information in the SIP INVITE message transmitted when requesting a bootstrap data channel connection. Additionally, if the service is an avatar-based service, the SIP INVITE message can additionally include avatar expression-related information. In an embodiment of the present disclosure, the avatar expression-related information can include an Avatar ID, an Avatar Model descriptor, a Version, and the like.

[0104] In an embodiment of the present disclosure, if there is avatar expression related information in the data channel service related request information transmitted from the terminal, the IMS AS can separately select a connection to a DCSF that supports the avatar storage function entity. Whether the DSCF supports the avatar storage function entity can be determined based on the service that is registered or requested to be subscribed by transmitting information related to services that the DCSF can support together when subscribing to data channel related information to the IMS AS. In addition, the DCSF can register information on services that the DSCF can support when registering with the NRF, and the IMS AS can select a DCSF that supports the required service based on information in the SIP INVITE message transmitted by the terminal and perform a connection operation for using the data channel service.

[0105] In an embodiment of the present disclosure, the DCSF may perform an operation of requesting and receiving avatar expression information or an avatar expression information list from an avatar storage function entity or an avatar storage repository based on avatar expression-related information transmitted from a terminal.

[0106] In an embodiment of the present disclosure, the DCSF may perform an operation of generating a media resource instruction to be transmitted to the MF (media function). At this time, in order to support an operation for downloading a data channel application of a terminal, the DCSF may generate mapping information, such as a data channel application for an actual data channel application transmission request transmitted from the terminal to the MF through the Mb interface and a replacement HTTP URL, and may transmit this to the MF by including it in a media resource instruction. Additionally, in order to support an avatar service using avatar storage within the network, a replacement HTTP URL mapped to avatar representation-related information requested by the terminal may be transmitted to the MF in order to support the download of avatar representation data requested by the terminal.

[0107] In an embodiment of the present disclosure, the DCSF may update SDP offer information based on avatar representation information (or a list of avatar representation information of originating UEs) supported by an avatar storage function entity or an avatar storage repository, and transmit the updated SDP offer information to the terminating UE via a SIP INVITE. In various embodiments of the present disclosure, the originating UE may be referred to as a first terminal, and the terminating UE may be referred to as a second terminal.

[0108] In an embodiment of the present disclosure, the terminating UE may select appropriate avatar representation information of the originating UE based on avatar representation information related to the originating UE (or a list of originating UE's avatar representation information), taking into consideration the terminal performance and supportable codec information of the terminating UE. In addition, the terminating UE may transmit the avatar representation-related information of the terminating UE together with the response information (SDP answer) to the SDP offer transmitted from the originating UE, and transmit the avatar representation information of the terminating UE provided through the avatar storage function entity or the avatar storage repository to the originating UE and the network.

[0109] In an embodiment of the present disclosure, the Originating Network (S-SCSF) that has received SDP answer information including avatar expression-related information of the terminating UE can transmit the avatar expression-related information of the terminating UE to the DCSF via the IMS AS. Based on the received avatar expression-related information of the terminating UE, the DCSF can request transmission of the avatar expression information of the terminating UE that can be provided from the avatar storage function entity or the avatar storage repository. The avatar storage function entity or the avatar storage repository can determine the avatar expression information of the terminating UE that can be provided based on the avatar expression-related information and service information of the terminating UE and transmit the same to the DCSF.

[0110] In an embodiment of the present disclosure, the DCSF, which has received the avatar expression information of the terminating UE from the avatar storage function entity or the avatar storage repository, may determine to generate replacement URL information that is mapped to the avatar expression information of the terminating UE within the MF. Thereafter, the DCSF may generate media instruction information including the replacement URL information that is mapped to the avatar expression information of the terminating UE within the MF and transmit the information to the MF through a media resource management update operation.

[0111] In an embodiment of the present disclosure, response information including avatar expression information of the Originating UE and the Terminating UE may be transmitted to the Originating UE through the IMS AS. At this time, the Originating UE may determine whether to update avatar expression information related to the Originating UE in the avatar storage function entity or avatar storage repository based on the transmitted avatar expression information of the Originating UE. The determination and operation of the avatar expression information update may be performed not only by the Originating UE but also by the Terminating UE that has received the avatar expression information of the Terminating UE provided from the avatar storage function entity or avatar storage repository through an ACK message.

[0112] In an embodiment of the present disclosure, if the Originating UE or the Terminating UE decides to update the avatar expression information of the user in the avatar storage function entity or the avatar storage repository, the avatar expression information update operation can be performed and the corresponding result information can be transmitted through a separate channel (e.g., HTTP POST).

[0113] In an embodiment of the present disclosure, after the Originating UE or the Terminating UE completes updating the avatar expression information of the user in the avatar storage function entity or the avatar storage repository, a SIP re-INVITE message for updating the avatar expression information of the Originating UE or the Terminating UE available in the service can be transmitted to the network and the counterpart UE.

[0114] In an embodiment of the present disclosure, in addition to avatar representation-related information in the SIP re-INVITE information transmitted by the terminal, the user's preferred avatar representation information (Preferred Avatar representation Info) may be transmitted together. For example, if the user's avatar representation information in the avatar storage function entity or avatar storage repository has been updated and a service based on the latest avatar is to be used or provided to the counterpart terminal, the preferred avatar representation information may be transmitted to the counterpart network and terminal by including relevant information to use the latest version of the avatar representation information.

[0115] In an embodiment of the present disclosure, when rendering avatar expression information is performed on each terminal, the avatar expression information can be downloaded during the bootstrap data channel setup signaling operation process. At this time, the terminal can receive the avatar expression information from the DCSF by transmitting the Avatar ID to the MF in order to download the avatar expression information of the other terminal user that can be used in the avatar service. The MF that has received the Avatar ID from the terminal can convert it into an alternative HTTP URL that is mapped to the corresponding avatar ID and transmit the avatar expression information request from the DCSF through the MDC1. The DCSF that has received the request information can receive the avatar expression information requested by the user from the avatar storage connected to the DCSF and transmit it to the terminal through the MF.

[0116] In an embodiment of the present disclosure, when rendering avatar expression information over a network, an Avatar ID may be transmitted as application binding media information within application data channel setup signaling. The DCSF, which receives application binding information including an Avatar ID from a terminal, may include the Avatar ID information in a media instruction within the MF. Thereafter, the DCSF may transmit the media instruction information including the Avatar ID information to the MF to allocate media functions within the MF for performing avatar-related operations. The MF, which has been assigned the Avatar ID and temporary Avatar storage function, may request and receive avatar expression information from the DCSF by converting the Avatar ID into an alternative HTTP URL stored within the MF when the response message transmitted from the Termination UE is 200 OK and accepts the avatar-related configuration operation (network-based rendering) within the MF. At this time, depending on the settings of the DCSF or the network operator, the avatar expression information to be utilized in the avatar storage within the MF may be transmitted in the form of alternative HTTP URL information mapped to the Avatar ID instead of the Avatar ID.

[0117] In embodiments of the present disclosure, an avatar storage function entity or avatar storage repository may be associated with a DCSF and / or a DC AS.

[0118] FIG. 5 is a flowchart illustrating a process of performing an operation to create or update the corresponding information by using an HSS to store avatar service-related profile information including specific user-related avatar information, service information, avatar use restriction information, etc. in terminal subscription information in a service operator server (or AF (application server)) that manages avatar expression information according to one embodiment of the present disclosure.

[0119] In step 0a, if a specific terminal user has registered with an IMS network, the HSS may transmit (send, transmit) a first message to the NRF to request NF registration including relevant profile information. For example, the first message may be an NF registration request message and may be an Nnrf_NFManagement_NFRegister message. In step 0b, the NRF may store HSS profile information including specific terminal user information within the NRF. In step 0c, the NRF may transmit a second message to the HSS in response to the first message. The second message may be an NF registration response message and may be an Nnrf_NFManagement_NFRegister Response message.

[0120] In step 1, a service provider server (AF) managing avatar expression information may determine to generate an AF request message to store avatar service-related profile information including at least one of information such as specific user-related avatar information (UE id and Avatar id) and service information (service id), avatar usage restriction information (Avatar usage restriction), and storage information (DAC id) storing avatar expression information in the terminal subscription information. The avatar usage restriction information may additionally provide information for restricting the use of specific avatars in avatar services, such as restricting the use of the avatar expression information only in network-based avatar services (Network-based rendering only or Avatar representation download not allowed) or restricting downloads to other counterpart service users who are not the avatar owner (Avatar representation owner download only), according to the policy of the service provider managing the avatar expression information. For example, if a service provider managing avatar expression information has set avatar use restriction information that allows avatar use only in network-based avatar services, and if a service user requests an avatar service that downloads avatar expression information to a terminal and provides the service according to his / her choice when connecting to an application data channel, the avatar service connection request through the avatar expression information may be rejected.

[0121] In step 2, the AF may transmit a third message to the NEF, which includes avatar service-related profile information, including at least one of the following information: specific user-related avatar information (UE id and Avatar id) generated in step 1, service information (service id), avatar usage restriction information, storage information (DAC id) storing avatar expression information, etc. The third message may be related to creating, updating, or deleting avatar profile information. The third message may be, for example, a Nnef_ServiceParameter_Create request message, a Nnef_ServiceParameter_Update request message, or a Nnef_ServiceParameter_Delete request message.

[0122] In step 3, NEF may send a fourth message to NRF, including subscriber (IMPU) or group of subscribers (IMPUs), to request information about an HSS server that manages specific user-related subscription information. For example, the fourth message may be an Nnrf_NFDiscovery_Request message.

[0123] In step 4, NRF may forward a fifth message to NEF, which includes HSS information for managing specific user-related subscription information, based on the fourth message. The fifth message may be an Nnrf_NFDiscovery_Response message. NEF may receive HSS server information for managing specific user-related subscription information from NRF.

[0124] In step 5, the NEF may transmit a sixth message to the HSS, which includes avatar service-related profile information including at least one of user-related avatar information (UE id and Avatar id) and service information (service id), avatar usage restriction information, and storage information (DAC id) storing avatar expression information, which are transmitted from the AF. The sixth message may be an Nhss_ImsSDM_Update request message. The NEF may transmit the sixth message based on the HSS server information obtained through the fifth message.

[0125] In step 6, the HSS may store the profile information related to a specific user-related avatar service received from the NEF in the subscription data or perform an action to update or delete existing subscription data.

[0126] In step 7, the HSS may send a seventh message to the NEF in response to the sixth message. The seventh message may be an Nhss_ImsSDM_Update response message. The HSS may use the seventh message to inform the NEF that the specific user-related avatar service profile information has been successfully included in the subscription and processed (stored) in the HSS. The processing related to the avatar service profile may refer to processing for storing, updating, or deleting the new profile information indicated in the sixth message.

[0127] In step 8, the NEF may send an eighth message to the AF in response to the third message. The eighth message may be a Nnef_ServiceParameter_Create response message, a Nnef_ServiceParameter_Update response message, or a Nnef_ServiceParameter_Delete response message. The NEF may use the eighth message to inform the AF that the profile information related to the specific user-related avatar service requested by the AF has been successfully delivered to the HSS based on the update request response information received from the HSS.

[0128] FIG. 6 is a flowchart illustrating an operation of registering a service and granting access rights to grant a service provider that manages avatar expression information according to one embodiment of the present disclosure the right to access network storage that stores avatar expression information in a specific service and / or application.

[0129] In step 0, a service provider (e.g., NF service producer (e.g., DAC)) that manages avatar expression information can store an NF provider (producer) profile to request a network storage access authentication service from the NRF in order to provide a service for authenticating access to network storage that stores avatar expression information in a specific service or application. For example, the service provider can transmit a first message to the NRF in step 0a. The first message can be an Nnrf_NFManagement_NFRegister Request message. In step 0b, the NRF can store an NF producer profile based on the first message. In step 0c, the NRF can transmit a second message to the service provider in response to the first message. The second message can include a processing result according to the request of the first message, and the NRF can inform the service provider of information about the successful storage of the NF producer profile through the second message.

[0130] In step 1, NRF may receive a request for authentication information from DSCF to access network storage (e.g., DAC or ASF) that stores avatar expression information during the bootstrap data channel process. The request for authentication information may be received via a third message, and the third message may be an Nnrf_AccessToken_Get Request message. The information transmitted via the third message to request authorization for access to network storage from DCSF may include at least one of a Service ID and an Application ID related to the avatar service.

[0131] In step 2, the NRF can generate token information that allows access to the network storage (e.g. DAC or ASF) of the NF (e.g. DSCF) based on authorization information for accessing the network storage (e.g. DAC or ASF) including at least one of the Service ID and Application ID information received from the DSCF.

[0132] In step 3, NRF may transmit a fourth message to DCSF in response to the third message. NRF may transmit the fourth message to DCSF, including at least one of token information and expiration information (expire_in) that authorizes access to network storage (e.g., DAC or ASF) that stores avatar expression information of DSCF.

[0133] In step 4, DCSF may transmit a fifth message for service request to a network storage (e.g., DAC or ASF) based on the fourth message in step 3. The fifth message may be an NF service request message. DCSF may forward the NF Service request message, which includes information for requesting avatar expression information, including the access_token_DAC received in step 3 and at least one of UE id, Service id, and Application id, to the network storage (e.g., DAC or ASF) storing the avatar expression information.

[0134] In step 5, the network storage (e.g., DAC or ASF) can verify the token and execute the requested service based on the data request information received from the DSCF through the fifth message. In step 6, the network storage can send a sixth message to the DCSF in response to the fifth message. The sixth message can be an NF service response message. The sixth message can include appropriate avatar representation data (e.g., avatar id) or a list of avatar representation data (list of avatar ids) based on the UE id, Service id, and Application id information.

[0135] FIGS. 7a, 7b, and 7c are flowcharts illustrating an operation of requesting access to network storage storing avatar expression information and receiving avatar expression information or an avatar expression information list based on the request during a data channel signaling process according to one embodiment of the present disclosure. FIGS. 7a, 7b, and 7c are hereinafter referred to as FIG. 7.

[0136] In Fig. 7, the Originating UE (UE#1) can request a data channel application and avatar expression information for using an avatar-based IMS data channel service from the network through a bootstrap data channel setup signaling process. In addition, if the application data channel connection type is P2P, the SIP INVITE message containing the data channel application requested by UE#1 and information related to avatar expression can be transmitted to the Terminating UE (UE#2).

[0137] In an embodiment of the present disclosure, the DCSF may generate alternative HTTP URL information related to the data channel application and avatar expression information in the corresponding bootstrap DC session based on the data channel application and avatar expression information, and may support this through the Local MF, and may include the related HTTP Proxy operation in the media resource instruction and transmit it to the MF.

[0138] In step 0, a network storage service provider providing avatar expression information, such as the embodiment of FIG. 5, may store an avatar service-related profile related to a specific service user within the HSS. The avatar service-related profile may include at least one piece of information from among avatar information related to a specific user (UE id and Avatar id), service information (service id), avatar usage restriction information, and storage information (DAC id) storing the avatar expression information.

[0139] In step 1, a terminal (UE#1) may transmit a first message (e.g., a SIP INVITE message) including an SDP offer for requesting audio, video, and bootstrap data channel connection to an IMS AS. If the service for which the terminal requests connection is an avatar-based service, the bootstrap data channel session connection request information may include avatar representation-related information for receiving avatar representation information of a terminal user supported by an avatar storage within the network. The avatar representation-related information may include at least one of service information (service id and / or application id) using avatar representation information, and user information (UE id) such as IMSI.

[0140] In step 2, the IMS AS that receives the SIP INVITE including the SDP offer including the avatar service information can perform an operation to select a DCSF that supports the avatar storage function entity. If there is avatar expression related information in the data channel service related request information transmitted from the terminal (UE#1), the IMS AS can separately select a connection to the DCSF that supports the avatar storage function entity. Whether the DSCF supports the avatar storage function entity can be determined based on the service that is registered or the subscription request by transmitting information related to services that the DCSF can support together when subscribing to the data channel related information to the IMS AS. In addition, the DCSF can register information on services that the DSCF can support when registering with the NRF, and the IMS AS can select a DCSF that supports the required service based on the information in the SIP INVITE message transmitted by the terminal (UE#1) and perform a connection operation for using the data channel service.

[0141] In step 3, IMS-AS may forward a second message (e.g., a SessionEventControl_Notify message) containing at least one of the following information for requesting a bootstrap data channel connection to DCSF: SessionEstablishmentRequestEvent, Session ID, Calling ID, Called ID, Session Case, Event initiator, Media InfoList, DC Stream ID, and Avatar representation related information.

[0142] In step 4, the SCSF, upon receiving the second message, performs an action based on the second message. For example, the DCSF, upon receiving the second message including the media change request event, may perform a data channel control policy update to support the download of data channel applications and avatar expression information.

[0143] In step 5, the DCSF may perform media resource creation operations of Originating UE and Terminating UE to transfer and set related information to support downloading of data channel applications within the MF, such as data channel application-related conversion or mapping information (Replacement URL for DC application) to transfer data channel application information requested from a terminal (UE#1) into the DCSF based on appropriate data channel application information received from the IMS AS and information to support avatar-related services through avatar storage, and MDC1 endpoint allocation information to receive the data channel application through MDC1 between the DCSF and the MF.

[0144] In step 6, the DCSF may request the transmission of avatar IDs or avatar ID list information related to a specific service user that can be provided in the avatar storage from an Avatar Storage Function (ASF) or a Digital Asset Container (DAC) connected to the DCSF based on the avatar expression-related information received from the IMS AS. In this process, the DCSF may transmit a request message to the storage function entities and receive a response message from the storage function entities to obtain the necessary information. For example, as in the embodiment of FIG. 6, the DCSF may receive authorization information for accessing a network storage that supports avatar expression information through the NRF according to a service provider policy, etc. The DCSF may transmit authorization information (Access_token) and service ID, application ID, UE ID, etc. received from the NRF to the network storage (e.g., ASF or DAC) to receive avatar IDs or avatar ID list information.

[0145] ASF can determine whether to provide avatar expression information according to the request of the service and service user based on service-related information such as Service ID and Called ID received from DCSF. If ASF can provide the avatar expression information desired by the service user in the avatar-related service requested by the service user at the request of the service user, ASF can transmit the avatar expression information or the avatar expression information list of the service user (e.g. UE#1) that ASF can provide to DCSF. DCSF, which receives avatar expression information or the avatar expression information list from ASF at the request of the service user, can generate information to support downloading the avatar expression information to the terminal or MF through avatar storage on the network. For example, the terminal can request DCSF through MF to transmit the avatar expression information to the terminal or MF according to the application data channel connection type based on the avatar expression-related information (e.g., avatar representation ID). The MF, which receives the request information, can convert it based on the conversion or mapping information (replacement URL for avatar representation information) of the terminal's avatar expression-related information (e.g., avatar representation ID) and then transmit it to DCSF. DCSF can perform media resource creation operations to support transmission of avatar representation information on the Originating UE and Terminating UE sides to transmit and set up within the MF information such as conversion or mapping information (replacement URL for avatar representation information) of terminal avatar representation-related information (e.g., avatar representation ID) and MDC1 endpoint allocation information.

[0146] In step 7, the DCSF may transmit media resource information (a third message) to the IMS AS to support the download of data channel applications and avatar presentation information to be delivered to the MF entity. The third message may be a Nimsas MediaControl_MediaInstruction message. Based on the media resource information received from the DCSF, the IMS AS may perform actions to select an appropriate MF via the NRF.

[0147] In step 8, IMS-AS, which has received media resource information of the MF entity from DCSF, may forward it to MF to perform media resource allocation operations to support downloading of data channel applications and avatar expression information within MF. In addition, enMRF discovery operations may be performed.

[0148] In step 9, the MF or enMRF may forward a media resource management create action response message (Nmf_MRM_Create Response) to the IMS AS, including the result of the request for allocation of media resources to support download of data channel application and avatar expression information within the MF received from the IMS AS and the MF's MDC 1 Endpoint resource allocation information.

[0149] In step 10, the IMS AS may transmit a fourth message to the DCSF, including the result of the allocation request for media resources within the MF received from the MF or MRF and the MDC 1 Endpoint resource allocation information. The fourth message may be a Nimsas_MediaControl_MediaInstruction response message. This may be a response message to the fourth third message.

[0150] In step 11, DCSF may transmit a response message (the fifth message) to the session establishment request event, including data channel application-related information and avatar expression information or an avatar expression list of UE#1, to the IMS AS at the request of UE#1. The fifth message may be a Nimsas_SessionEventControl_Notify response message. The fifth message may be a response message to the second message.

[0151] In step 12, the IMS AS on the local network side can transmit updated SDP offer information based on the data channel application-related information for supporting the avatar service using the avatar storage from the DCSF and the avatar expression information or avatar expression list of UE#1 to the remote network and UE side, and transmit a SIP INVITE message (6th message) to the S-SCSF to request a bootstrap data channel session connection.

[0152] In step 13, the S-CSCF on the Local Network side can forward a SIP INVITE message (message 7) containing a modified SDP offer received from the IMS AS to the remote network and UE side to request a bootstrap data channel session connection to the remote network and UE side.

[0153] In step 14, the Remote UE (hereinafter referred to as UE #2) may determine whether to accept the bootstrap data channel connection request based on the data channel application-related information in the SIP INVITE message received via the S-CSCF. Subsequently, the operation of step 15 may be performed.

[0154] In step 16, the remote S-CSCF, which has received a response message (8th message, 200 OK) related to the bootstrap data channel connection request message from UE #2, can forward it to the local S-CSCF.

[0155] In step 17, the Local S-CSCF, which has received a response message (200 OK) related to a bootstrap data channel connection request message from the Remote network and the UE, may forward it to the Local IMS-AS to request the DCSF to forward information for bootstrap data channel connection.

[0156] In step 17, the S-CSCF may receive related information for bootstrap data channel connection of the remote network and the UE based on the response message transmitted from the remote network and the UE. At this time, the response message transmitted from the remote network or the UE may be 200 OK or 183 session progress. In the embodiment of the present disclosure, it is assumed that the response information related to the remote UE (UE#2) is transmitted via 200 OK. If a bootstrap data channel related response message (SDP answer) exists in the 200 OK response message, the S-CSCF may forward it to the IMS AS.

[0157] In step 18, the IMS AS may transmit media change request event information for performing media resource update related to UE #2 based on the remote network and UE-related bootstrap data channel response message to the DCSF through a SessionEventControl_Notify message (message 9) including information such as MediaChangeRequest Event, Session ID, Event Direction, Event initiator, and Media Info List. At this time, the SessionEventControl_Notify transmitted to the DCSF may also include at least one of information such as Service ID, Application Type, and Avatar representation related information from UE #2.

[0158] In step 19, the DCSF may update media resource information related to the media stream transmitted to UE #2 in the MF based on the 9th message and the information included therein, and at the same time, determine how to process the avatar representation-related information transmitted from UE #2. The DCSF may transmit the avatar representation-related information related to UE #2 to the ASF to receive avatar representation information or a list of avatar representation information of UE #2 available in the corresponding avatar service. The DCSF may generate media resource information related to avatar-related mapping information (Replacement URL for UE #2 Avatar representation information) of UE #2 in the MF and update the IMS DC policy based on the avatar representation information or the list of representation information related to UE #2 received from the ASF. DCSF may include updated media resource-related information, such as avatar representation information-related mapping information (Replacement URL for UE #2 Avatar representation information) of UE #2, to support downloading of avatar service-related data channel applications between MF entities and UE #2 and downloading and managing avatar representation information related to UE #2, in the data channel media resource information, and forward a media-related instruction (MediaInstruction) message for media resource control within the MF to IMS-AS. IMS AS may forward a media resource management request (Nmf_MRM_Create Request) message, which includes the media resource-related information created or updated within the MF and avatar representation information-related mapping information (Replacement URL for UE #2 Avatar representation information) of UE #2, to MF or enMRF, received from DCSF.MF (or enMRF) can forward the media resource update result information to IMS AS through a media resource management request response (Nmf_MRM_Create Request Response) message to support downloading and managing avatar representation information of UE#2 in Local MF based on the avatar representation information-related mapping information of UE#2 (Replacement URL for UE#2 Avatar representation information). IMS AS can forward the media resource update result and related information within the MF entity received from MF or enMRF to DCSF.

[0159] In step 20, DCSF may transmit result information for a media change request event including avatar expression information or a list of avatar expression information of UE #2 supported by the avatar storage function entity based on the avatar expression-related information and service information of UE #2 in the response message received for UE #2 to IMS AS through a session event control notification response message (message 9, Nimsas_SessionEventControl_Notify response message).

[0160] In step 21, the IMS AS may forward an updated or modified SDP answer to the S-CSCF in a 200 OK message based on the data channel application or list of data channel applications that support the avatar service requested by UE #1 and the avatar presentation information or list of avatar presentation information related to each terminal (UE #1 and UE #2) that uses the service. The S-CSCF, which receives the 200 OK message including the updated or modified SDP answer, may forward it to UE #1.

[0161] In step 22 (steps 22-1, 22-2, 22-3) and step 23 (steps 23-1, 23-2, 23-3), UE #1 and UE #2 may receive a list of applications providing avatar services through the Mb interface and select and download appropriate applications by considering the status information of each UE. In addition, in order to provide avatar services, UE #1 and UE #2 may download an avatar ID or a list of avatar IDs related to each UE and select appropriate avatar expression information by considering the status information of each UE. In step 24, additional necessary operations may be performed.

[0162] FIGS. 8a and 8b are flowcharts illustrating a method and operation for granting usage rights based on an avatar ID and a terminal ID for each service type during an application data channel connection process for using an avatar service on a terminal according to one embodiment of the present disclosure. Hereinafter, FIGS. 8a and 8b will be referred to as FIG. 8.

[0163] In step 0, a network storage service provider providing avatar expression information, such as the embodiment of FIG. 5, may store an avatar service-related profile related to a specific service user within the HSS. The avatar service-related profile may include at least one piece of information from among avatar information related to a specific user (UE id and Avatar id), service information (service id), avatar usage restriction information, and storage information (DAC id) storing the avatar expression information.

[0164] In step 1, through the audio video session connection and bootstrap data channel connection process between UE-A and UE-B, each UE (UE-A, UE-B) can receive data channel application supporting avatar service and avatar expression information (avatar id).

[0165] In step 2, UE-A can decide to request a network-based avatar service based on the status of the UE and the status information of the network.

[0166] In step 3, UE-A may perform XR media rendering negotiation with an XR Application Server (DC AS). The avatar id of UE-A may be used for media rendering negotiation.

[0167] In step 4a, the terminal (UE-A) may request a session connection of a data channel application to configure a network rendering type avatar service. The terminal (UE-A) may transmit an application data channel-related SDP offer to the IMS AS via a SIP re-INVITE message (the first message). The application data channel-related SDP offer may include the UE-A's avatar representation ID (Avatar Representation ID for UE-A).

[0168] In step 4b, the IMS AS can determine whether to perform an application data channel session connection supporting a Local DCS-based avatar service or an application data channel session connection supporting a Remote DCS-based avatar service based on the Bootstrap ID in the SDP offer related to the application data channel or the DC Stream ID in the SDP offer related to the bootstrap data channel. After performing a DCSF selection operation, the IMS AS can transmit a SessionEventControl_Notify message (second message) containing information such as a MediaChangeRequest Event, Session ID, Event Direction, Event initiator, Media Info List, etc. for an application data channel connection request, and avatar-related information such as the Avatar ID of UE-A, to the selected DCSF. The DCSF, which has received the message including the media change request event, can perform a data channel control policy update for application data channel connection supporting avatar expression information through avatar storage and avatar service. The DCSF can generate media information on the Originating and Terminating sides in the MF for application data channel connection to support avatar service.

[0169] In step 4c, the DCSF may request authorization information for use of avatar expression information in the network storage of the service provider providing avatar expression information (e.g., DAC) to the HSS in order to access the network storage. The HSS may authorize use of the Avatar ID of UE A, which the service user (UE-A) has requested to use for the avatar service, based on the UE ID and Avatar ID of UE-A. In step 4d, the HSS may transmit authorization information related to use of the Avatar ID of the corresponding UE A to the DSCF. If the service provider providing avatar expression information does not store or provide avatar service-related profile information for providing authorization information related to use of the Avatar ID of a specific user in the HSS, steps 4c and 4d may be omitted.

[0170] In step 4e, the DCSF may forward the P2A connection establishment (MDC3 / MDC4) request information and the Avatar representation data and avatar meta data request information, which include at least one of the Avatar-id of UE-A and the UE identity and / or Avatar data usage authorization information from the HSS, to the DC AS (XR Application Server). If the authorization information related to the use of the Avatar ID of a specific user is not provided through the HSS, the DC AS may request an authorization operation for the use of the avatar expression information of UE A within the Avatar representation data and avatar meta data request information.

[0171] In step 4f, if the DC AS (XR application server) does not receive authorization information related to the use of the Avatar ID from the DCSF, the DC AS can perform an authorization operation for the use of UE-A's avatar expression information based on the Avatar-id of UE-A and UE identity information.

[0172] In step 4g, the DC AS, which has been requested to transmit avatar meta data information to support network rendering from the DCSF, may transmit authorization information for use of UE-A avatar expression information and Avatar-id of UE-A and UE identity information to the DAC, and receive avatar meta data from the DAC.

[0173] In step 4h, the DC AS, which has received avatar metadata information from the DAC, can transmit a response message to the P2A connection connection request including avatar metadata information and MDC2 media resources to the DCSF. In step 4e, if the DCSF requests authorization for UE A's avatar usage, the corresponding result information can be transmitted to the DCSF as well. The DCSF can request the IMS AS to transmit updated media instruction information based on the avatar metadata information received from the DCAS to the MF. The IMS AS, which has received the updated media instruction information based on the avatar metadata information from the DCSF, can transmit it to the MF to perform media resource allocation operations within the MF for application data channel connection. The IMS AS can transmit the result of the media resource allocation request to the IMS AS through a Nimsas_MediaControl_MediaInstructionResponse message. DCSF may forward the results of a media change request event, including media resource information within the Local MF, to the IMS AS in relation to the IMS DC service media change request event requested by the IMS AS in step 4b.

[0174] In step 5, the IMS AS may optionally perform media renegotiation with UE-A via the application DC to connect the audio / video media streams of UE-A to the MF / MRF.

[0175] In step 6, the IMS AS may perform media renegotiation with UE-B to connect the audio / video media stream of UE-B to the MF / MRF. After the renegotiation process is performed, the DCSF may notify UE-A that the application data channel connection for configuring a network-based avatar service has been successfully performed. At the same time, if a reporting request for the corresponding event information has been performed from the DC AS to the DCSF when the application data channel connection for configuring a network-based avatar service has been successfully performed according to the policy of the DC AS, etc., the DCSF may transmit a message to UE-A notifying that the application data channel connection has been successfully performed, and at the same time, perform an event reporting operation to the DC AS.

[0176] In step 7, the DC AS, which has received an event reporting from the DCSF indicating that the application data channel connection has been successfully established, can transmit a request for transmission of avatar expression information to the DAC.

[0177] In step 8, the DAC may transmit the UE-A related avatar expression information requested by the DCAS to the DCAS through a response message of the request for transmission of the corresponding avatar expression information or through a separate channel.

[0178] At step 9, the DC AS can begin controlling XR media rendering.

[0179] In step 10, the DC AS can transmit the UE-A related avatar expression information received from the DAC to the MF via the MDC 2 interface.

[0180] In step 11, UE-A can transmit avatar movement information to MF. UE-A can extract avatar movement information and transmit it to MF through application data channel or transmit it to MF through existing RTP session in video format.

[0181] In step 12, the MF that has received the movement information of UE-A can generate avatar expression information in the form of animation by combining the avatar movement information of UE-A with the avatar expression information of UE-A received from the DC AS.

[0182] In step 13, the MF can transmit the avatar media of UE-A, which is converted into video in the form of animation avatar expression information of UE-A, to UE-B via an RTP session. If UE-B is a terminal that supports data channel services rather than a conventional terminal such as an MTSI UE, the avatar media of UE-A, which is converted into video, can be transmitted to UE-B via an application data channel.

[0183] In step 14, MF can transmit the avatar media of UE-A converted to video to UE-A via an RTP session or application data channel. UE-A can check the rendering result of the network through the avatar media of UE-A converted to video.

[0184] FIGS. 9a and 9b are flowcharts illustrating a method and operation for granting usage rights based on an avatar ID and a terminal ID for each service type during an application data channel connection process for using an avatar service on a terminal according to one embodiment of the present disclosure. Hereinafter, FIGS. 9a and 9b will be referred to as FIG. 9.

[0185] In step 0, a network storage service provider providing avatar expression information, such as the embodiment of FIG. 5, may store an avatar service-related profile related to a specific service user within the HSS. The avatar service-related profile may include at least one piece of information from among avatar information related to a specific user (UE id and Avatar id), service information (service id), avatar usage restriction information, and storage information (DAC id) storing the avatar expression information.

[0186] In step 1, through the audio video session connection and bootstrap data channel connection process between UE-A and UE-B, each UE (UE-A, UE-B) can receive data channel application supporting avatar service and avatar expression information (avatar id).

[0187] In step 2, UE-A can decide to use the avatar service using the avatar rendering operation of UE-A at the terminal of UE-A based on the status of the UE and the status information of the network.

[0188] In step 3, UE-A can perform an XR media rendering negotiation operation with the XR Application Server (DC AS). The avatar id of UE-A can be used for the media rendering negotiation. If avatar service-related information is stored in the DAC of the XR AS, avatar usage restriction information may be set according to the policy of the DAC service provider or the request of a specific avatar creator. For example, if avatar usage restriction information that does not allow downloading of specific avatar expression information to the terminal is set, the XR AS may reject a request to use the avatar service using the avatar rendering operation on the terminal of UE-A.

[0189] In step 4a, the terminal (UE-A) may request a session connection of a data channel application to configure a network rendering type avatar service. The terminal (UE-A) may transmit an application data channel-related SDP offer to the IMS AS via a SIP re-INVITE message (the first message). The application data channel-related SDP offer may include the UE-A's avatar representation ID (Avatar Representation ID for UE-A).

[0190] In step 4b, the IMS AS can determine whether to perform an application data channel session connection supporting a Local DCS-based avatar service or an application data channel session connection supporting a Remote DCS-based avatar service based on the Bootstrap ID in the SDP offer related to the application data channel or the DC Stream ID in the SDP offer related to the bootstrap data channel. After performing a DCSF selection operation, the IMS AS can transmit a SessionEventControl_Notify message (second message) containing information such as a MediaChangeRequest Event, Session ID, Event Direction, Event initiator, Media Info List, etc. for an application data channel connection request, and avatar-related information such as the Avatar ID of UE-A, to the selected DCSF. The DCSF, which has received the message including the media change request event, can perform a data channel control policy update for application data channel connection supporting avatar expression information through avatar storage and avatar service. The DCSF can generate media information on the Originating and Terminating sides in the MF for application data channel connection to support avatar service.

[0191] In step 4c, the DCSF may request authorization information for use of avatar expression information in the network storage of the service provider providing avatar expression information (e.g., DAC) to the HSS in order to access the network storage. The HSS may authorize use of the Avatar ID of UE A, which the service user (UE-A) has requested to use for the avatar service, based on the UE ID and Avatar ID of UE-A. In step 4d, the HSS may transmit authorization information related to use of the Avatar ID of the corresponding UE A to the DSCF. If the service provider providing avatar expression information does not store or provide avatar service-related profile information for providing authorization information related to use of the Avatar ID of a specific user in the HSS, steps 4c and 4d may be omitted.

[0192] In step 4e, the DCSF may forward the P2A connection establishment (MDC3 / MDC4) request information and the Avatar representation data and avatar meta data request information, which include at least one of the Avatar-id of UE-A and the UE identity and / or Avatar data usage authorization information from the HSS, to the DC AS (XR Application Server). If the authorization information related to the use of the Avatar ID of a specific user is not provided through the HSS, the DC AS may request an authorization operation for the use of the avatar expression information of UE A within the Avatar representation data and avatar meta data request information.

[0193] In step 4f, if the DC AS does not receive authorization information related to the use of the Avatar ID from the DCSF, the DC AS may perform an authorization operation for the use of UE-A's avatar expression information based on the Avatar-id of UE-A and UE identity information.

[0194] In step 4g, the DC AS, which has been requested to transmit avatar meta data information to support network rendering from the DCSF, may transmit authorization information for use of UE-A avatar expression information and Avatar-id of UE-A and UE identity information to the DAC, and receive avatar meta data from the DAC.

[0195] In step 4h, the DC AS, which has received avatar meta data information from the DAC, can forward a response message to the P2A connection connection request, which includes avatar meta data information and MDC2 media resources, to the DCSF. In step 4e, if the DCSF requests authorization for UE A's avatar usage, the corresponding result information can be forwarded to the DCSF as well.

[0196] In step 4i, the DCSF may request the IMS AS to forward the updated media instruction information based on the avatar metadata information received from the DCAS to the MF. The IMS-AS, which has received the updated media instruction information based on the avatar metadata information from the DCSF, may forward it to the MF to perform media resource allocation operations within the MF for application data channel connection. The IMS AS may forward the results of the media resource allocation request to the IMS AS via the Nimsas_MediaControl_MediaInstructionResponse message. The DCSF may forward the results of the media change request event, including media resource information within the Local MF, related to the IMS DC service media change request event requested by the IMS AS in step 4b, to the IMS AS.

[0197] In step 5, the IMS AS may optionally perform media renegotiation with UE-A via the application DC to connect the audio / video media streams of UE-A to the MF / MRF.

[0198] In step 6, the IMS AS may perform media renegotiation with UE-B to connect the audio / video media stream of UE-B to the MF / MRF. After the renegotiation process is performed, the DCSF may notify UE-A that the application data channel connection for configuring a network-based avatar service has been successfully performed. At the same time, if a reporting request for the corresponding event information has been performed from the DC AS to the DCSF when the application data channel connection for configuring a network-based avatar service has been successfully performed according to the policy of the DC AS, etc., the DCSF may transmit a message to UE-A notifying that the application data channel connection has been successfully performed, and at the same time, perform an event reporting operation to the DC AS.

[0199] In step 7, the DC AS, which has received an event reporting from the DCSF indicating that the application data channel connection has been successfully established, can transmit a request for transmission of avatar expression information to the DAC.

[0200] In step 8, the DAC may transmit the UE-A related avatar expression information requested by the DCAS to the DCAS through a response message of the request for transmission of the corresponding avatar expression information or through a separate channel.

[0201] In step 9, the DC AS can transmit the UE-A related avatar expression information received from the DAC to the MF via the MDC 2 interface and then transmit it to the UE-A again using the Mb interface.

[0202] In step 10, UE-A can generate movement information of the UE-A terminal user. UE-A can extract the movement information of the UE-A terminal user and combine it with the avatar expression information of UE-A received from step 9 to generate avatar expression information in the form of animation.

[0203] In steps 11 and 12, UE-A directly transmits the avatar media of UE-A, which is the avatar expression information in the form of animation generated in step 10, to UE-B via an RTP session, or, if an application data channel connection for transmitting avatar media via MF anchoring is established, UE-A can transmit the avatar media of UE-A, which is the avatar media converted into a video, to MF via an RTP session or an application data channel, and then transmit the avatar media of UE-A, which is the avatar media converted into a video, to UE-B via the MF. If UE-B is a terminal that supports a data channel service rather than a conventional terminal such as an MTSI UE, the avatar media of UE-A, which is the avatar media converted into a video, can be transmitted to UE-B via an application data channel.

[0204] FIGS. 10a, 10b, and 10c are flowcharts illustrating a method and operation for granting usage rights based on an avatar ID and a terminal ID for each service type during an application data channel connection process for using an avatar service on a terminal according to one embodiment of the present disclosure. Hereinafter, FIGS. 10a, 10b, and 10c will be referred to as FIG. 10.

[0205] In step 0, a network storage service provider providing avatar expression information, such as the embodiment of FIG. 5, may store an avatar service-related profile related to a specific service user within the HSS. The avatar service-related profile may include at least one piece of information from among avatar information related to a specific user (UE id and Avatar id), service information (service id), avatar usage restriction information, and storage information (DAC id) storing the avatar expression information.

[0206] In step 1, through the audio video session connection and bootstrap data channel connection process between UE-A and UE-B, each UE (UE-A, UE-B) can receive data channel application supporting avatar service and avatar expression information (avatar id).

[0207] In step 2, UE-A can decide to use the avatar service using the avatar rendering operation of UE-A at the terminal of UE-B based on the status of the UE and the status information of the network.

[0208] In step 3a, UE-A can perform an XR media rendering negotiation operation with the XR Application Server. If avatar service-related information is stored in the DAC of the XR AS, avatar usage restrictions may be set according to the policy of the DAC service provider or the request of a specific avatar creator. For example, if the XR AS has avatar usage restrictions that do not allow downloading of specific avatar expression information to the terminal, it may reject a request to use the avatar service using the avatar rendering operation on the terminal of UE-A. Additionally, if UE-A's UE ID and Avatar ID are stored as an avatar-related service profile in the HSS and the HSS provides UE-A's Avatar ID usage authorization information in the DAC based on UE-A's UE ID and Avatar ID, UE-A can transmit information including UE-B's Avatar representation usage allowed indication for accepting a request for UE-A-related avatar representation information, when UE-A avatar usage authorization information generated based on UE-A's information is transmitted together with UE-B ID, to the DC AS (XR AS). In addition, UE-A can transmit Allowed Session ID or Allowed Service ID information together with UE-B's Avatar representation usage allowed indication to the DC AS (XR AS) in order to allow only UE-B's request for downloading UE-A-related avatar representation information associated with a specific Session ID or Service ID.

[0209] In step 3b, UE-A can perform an XR media rendering negotiation operation with UE-B. Through this XR media rendering negotiation operation, UE-A and UE-B can transfer the IDs of their respective terminals, and UE-A can additionally transfer to UE-B the Avatar ID information of UE-A to be used for the avatar service based on UE-A's avatar media rendering using UE-B's terminal.

[0210] In step 4a, the terminal (UE-B) may request a session connection of a data channel application for configuring a network rendering type avatar service. The terminal (UE-B) may transmit an application data channel-related SDP offer to the IMS AS via a SIP re-INVITE message (the first message). The application data channel-related SDP offer may include the avatar representation ID for UE-A and the ID of UE-A.

[0211] In step 4b, the IMS AS can determine whether to perform an application data channel session connection supporting a Local DCS-based avatar service or an application data channel session connection supporting a Remote DCS-based avatar service based on the Bootstrap ID in the SDP offer related to the application data channel or the DC Stream ID in the SDP offer related to the bootstrap data channel. After performing a DCSF selection operation, the IMS AS can transmit a SessionEventControl_Notify message (second message) containing information such as a MediaChangeRequest Event, Session ID, Event Direction, Event initiator, Media Info List, etc. for an application data channel connection request, and avatar-related information such as the Avatar ID of UE-A, to the selected DCSF. The DCSF, which has received the message including the media change request event, can perform a data channel control policy update for application data channel connection supporting avatar expression information through avatar storage and avatar service. The DCSF can generate media information on the Originating and Terminating sides in the MF for application data channel connection to support avatar service.

[0212] In step 4c, the DCSF may request authorization information for the use of avatar expression information in the network storage of the service provider (e.g., DAC) that provides avatar expression information from the HSS to access the network storage. The DCSF may request authorization information using a third message (Nhss_ImsSDM_Get request message). Based on the UE ID and Avatar ID of UE-A, the HSS may authorize the use of the Avatar ID of UE A that the service user (UE-A) has requested to use for the avatar service.

[0213] In step 4d, the HSS can forward authorization information related to the use of the Avatar ID of the corresponding UE A to the DSCF. The HSS can forward the authorization information to the DSCF using the fourth message (Nhss_ImsSDM_Get response message). If the service provider providing the avatar expression information does not store or provide the avatar service-related profile information for providing authorization information related to the use of the Avatar ID of a specific user within the HSS, steps 4c and 4d can be omitted.

[0214] In step 4e, the DCSF may forward the Avatar representation data and avatar meta data request information, which include P2A connection establishment (MDC3 / MDC4) request information and at least one of the Avatar-id of UE-A and UE identity and / or Avatar data usage authorization information from HSS, to the DC AS (XR Application Server). The DSCF may utilize the fifth message, and the fifth message may be a P2A connection establishment request message. If authorization information related to the use of the Avatar ID of a specific user is not provided through the HSS, the DCSF may request the DC AS to perform an authorization operation for the use of the avatar representation information of UE A within the Avatar representation data and avatar meta data request information. In step 3a, the DC AS receives information from UE-A that the download operation of UE-A's avatar expression information is permitted based on UE-A's avatar use authorization information in a specific avatar service or session at the request of UE-B. Therefore, based on the ID of UE-B and the specific Session ID or Service ID transmitted through step 4e and the UE-A's avatar expression information use authorization information transmitted, the DC AS can decide to provide UE-A's avatar expression information and avatar metadata information.

[0215] In step 4f, if the DC AS does not receive authorization information related to the use of the Avatar ID from the DCSF, the DC AS may perform authorization for UE-B's use of UE-A's avatar usage based on information that allows UE-B's download operation of UE-A's avatar expression information received from UE-A in step 3a, based on at least one of UE-A's Avatar-id and UE identity information, UE-B ID, Session ID, and Service ID.

[0216] In step 4g, the DC AS, which has been requested to transmit avatar meta data information to support network rendering from the DCSF, may transmit authorization information for use of UE-A avatar expression information and Avatar-id of UE-A and UE identity information to the DAC, and receive avatar meta data from the DAC.

[0217] In step 4h, the DC AS, which has received avatar meta data information from the DAC, can forward a response message to the P2A connection connection request, which includes avatar meta data information and MDC2 media resources, to the DCSF. In step 4e, if the DCSF requests authorization for UE A's avatar usage, the corresponding result information can be forwarded to the DCSF as well.

[0218] In step 4i, the DCSF may request the IMS AS to forward the updated media instruction information based on the avatar metadata information received from the DCAS to the MF. The IMS-AS, which has received the updated media instruction information based on the avatar metadata information from the DCSF, may forward it to the MF to perform media resource allocation operations within the MF for application data channel connection. The IMS AS may forward the results of the media resource allocation request to the IMS AS via the Nimsas_MediaControl_MediaInstructionResponse message. The DCSF may forward the results of the media change request event, including media resource information within the Local MF, related to the IMS DC service media change request event requested by the IMS AS in step 4b, to the IMS AS.

[0219] In step 5, the IMS AS may optionally perform media renegotiation with UE-A via the application DC to connect the audio / video media streams of UE-A to the MF / MRF.

[0220] In step 6, the IMS AS may perform media renegotiation with UE-B to connect the audio / video media stream of UE-B to the MF / MRF. After the renegotiation process is performed, the DCSF may notify UE-A that the application data channel connection for configuring a network-based avatar service has been successfully performed. At the same time, if a reporting request for the corresponding event information has been performed from the DC AS to the DCSF when the application data channel connection for configuring a network-based avatar service has been successfully performed according to the policy of the DC AS, etc., the DCSF may transmit a message to UE-A notifying that the application data channel connection has been successfully performed, and at the same time, perform an event reporting operation to the DC AS.

[0221] In step 7, the DC AS, which has received an event reporting from the DCSF indicating that the application data channel connection has been successfully established, can transmit a request for transmission of avatar expression information to the DAC.

[0222] In step 8, the DAC may transmit the UE-A related avatar expression information requested by the DCAS to the DCAS through a response message of the request for transmission of the corresponding avatar expression information or through a separate channel.

[0223] In step 9a, the DC AS transmits the UE-A related avatar expression information received from the DAC to the MF via the MDC 2 interface, and in step 9b, the MF can transmit this again to UE-B using the Mb interface.

[0224] In step 10, UE-A can extract movement information of UE-A terminal user and generate avatar movement information (e.g., FACS) of UE-A. UE-A can transmit the generated avatar movement information of UE-A to UE-B through an application data channel.

[0225] In step 11, UE-B can generate avatar expression information in the form of animation based on the avatar movement information received from UE-A through step 10 and the avatar expression information of UE-A received from DCAS through step 9.

[0226] In step 12, UE-B can convert the avatar expression information in the form of animation of UE-A generated in UE-B into a video form and transmit it to UE-A through an RTP session or application data channel.

[0227] FIG. 11 is a diagram illustrating a configuration of a network entity performing another network function in one embodiment of the present disclosure.

[0228] The network function may be at least one of the NFs such as RAN, AMF, SMF, UPF, PCF, UDM, NSSF, NWDAF, DN, NSACF, HSS, DAC, IMS AS, DSCF, MF, MRF, IMS core, XR application server, AF, etc., as described above through embodiments of the present disclosure.

[0229] Referring to FIG. 11, a network entity performing a network function may include a transceiver (1110), a control unit (1120), and a storage unit (1130). In the present disclosure, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0230] The transceiver (1110) can transmit and receive signals with other network entities. For example, the transceiver (1110) can transmit and receive signals or messages with the AMF, a network entity that manages access and mobility of a terminal to an access network.

[0231] The control unit (1120) can control the overall operation of a network entity performing network functions according to the embodiments proposed in this disclosure. For example, the control unit (1120) can control the signal flow between each block to perform operations according to the flowchart described above.

[0232] The storage unit (1130) can store at least one of the information transmitted and received through the transmission and reception unit (1110) and the information generated through the control unit (1120).

[0233] FIG. 12 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.

[0234] Referring to FIG. 12, the terminal may include a transceiver (1210), a control unit (1220), and a storage unit (1230). The transceiver (1210), the control unit (1220), and the storage unit (1230) may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. For example, the terminal may include a transceiver (1210) and a control unit (1220). In addition, the transceiver (1210), the control unit (1220), and the storage unit (1230) may be implemented in the form of a single chip.

[0235] The transceiver (1210) is a general term for the receiver and transmitter of a terminal, and can transmit and receive signals with a base station, another terminal, or a network entity. The signals transmitted and received with the base station may include control information and data. The transceiver (1210) may, for example, receive system information from the base station and receive a synchronization signal or a reference signal. To this end, the transceiver (1210) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts the received signal. However, this is only one embodiment of the transceiver (1210), and the components of the transceiver (1210) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1210) may include wired and wireless transceivers, and may include various configurations for transmitting and receiving signals. In addition, the transceiver (1210) can receive a signal through a wireless channel and output it to the control unit (1220), and transmit the signal output from the control unit (1220) through the wireless channel. In addition, the transceiver (1210) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a network entity through a wired or wireless network.

[0236] The storage unit (1230) can store programs and data necessary for the operation of the terminal. Furthermore, the memory can store control information or data included in signals acquired from the terminal. The storage unit (1230) can be configured as a storage medium, such as a ROM, RAM, hard disk, CD-ROM, or DVD, or a combination of storage media.

[0237] In the present invention, the control unit (1220) may be defined as a circuit, an application-specific integrated circuit, or at least one processor. The processor may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The control unit (1220) may control the overall operation of the terminal according to the embodiment proposed in the present disclosure. For example, the control unit (1220) may control the signal flow between each block to perform operations according to the flowchart described above.

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

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

[0240] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0241] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0242] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0243] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. In a method of a first terminal for an avatar service in a wireless communication system, A step of receiving an avatar identifier (avatar ID) via a bootstrap data channel; A step of receiving avatar expression information from MF (media function) based on the above avatar identifier; A step of performing avatar animation based on the above avatar expression information; and A method comprising the step of transmitting converted video information based on the above avatar animation to a second terminal.

2. In paragraph 1, A method in which the first terminal performs negotiation for the avatar animation with a DC AS (data channel application server) based on the avatar identifier.

3. In paragraph 1, A method in which an avatar rendering operation for the above avatar service is performed in the first terminal.

4. In paragraph 1, A method characterized in that the above avatar expression information is transmitted from the DC AS to the MF through the MDC2 interface.

5. In paragraph 1, If avatar usage restriction information is set according to the policy of the service provider and the request of a specific avatar creator, the method of not allowing the reception of the above avatar expression information.

6. In a method of a second terminal for avatar service in a wireless communication system, A step of receiving avatar expression information of a first terminal from MF (media function); A step of receiving avatar movement information of the first terminal through an application data channel; and A method comprising a step of performing avatar animation based on the above avatar expression information and the above avatar movement information.

7. In paragraph 6, The second terminal performs negotiation for the avatar animation with the first terminal, The negotiation for the above avatar animation is a method for obtaining access rights to the avatar expression information of the first terminal from the DC AS (data channel application server) in order for the second terminal to download the avatar expression information of the first terminal.

8. In paragraph 6, The avatar rendering operation for the above avatar service is performed on the second terminal, The above avatar expression information is transmitted from the DC AS (data channel application server) to the MF through the MDC2 interface, and If avatar usage restriction information is set according to the policy of the service provider and the request of a specific avatar creator, the method of not allowing the reception of the above avatar expression information.

9. In the first terminal for avatar service in a wireless communication system, Transmitter and receiver; and Contains at least one processor, At least one processor, Receives an avatar identifier (avatar ID) via the bootstrap data channel, Receive avatar expression information from MF (media function) based on the above avatar identifier, Performs avatar animation based on the above avatar expression information, and A first terminal that transmits converted video information based on the above avatar animation to a second terminal.

10. In paragraph 9, The first terminal is a first terminal that performs negotiation for the avatar animation with a DC AS (data channel application server) based on the avatar identifier.

11. In paragraph 9, The avatar rendering operation for the above avatar service is performed in the first terminal, A first terminal, characterized in that the above avatar expression information is transmitted from the DC AS to the MF through the MDC2 interface.

12. In paragraph 9, If avatar use restriction information is set according to the service provider's policy and the request of a specific avatar creator, the first terminal is not permitted to receive the avatar expression information.

13. In a second terminal for avatar service in a wireless communication system, Transmitter and receiver; and Contains at least one processor, At least one processor, Receive avatar expression information of the first terminal from MF (media function), Receives avatar movement information of the first terminal through the application data channel, and A second terminal that performs avatar animation based on the above avatar expression information and the above avatar movement information.

14. In paragraph 13, The second terminal performs negotiation for the avatar animation with the first terminal, The negotiation for the above avatar animation is a second terminal obtaining access rights to the avatar expression information of the first terminal from the DC AS (data channel application server) in order for the second terminal to download the avatar expression information of the first terminal.

15. In paragraph 13, The avatar rendering operation for the above avatar service is performed on the second terminal, The above avatar expression information is transmitted from the DC AS (data channel application server) to the MF through the MDC2 interface, and If avatar use restriction information is set according to the service provider's policy and the request of a specific avatar creator, a second terminal that is not permitted to receive the avatar expression information.

Images