Method and device for multimedia call service in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to the present disclosure, a method performed by a terminal in a wireless communication system may be provided. The method may comprise the steps of: determining a list including one or more sub-tasks associated with the terminal from among a plurality of sub-tasks included in a task; transmitting a message including the list to a network entity; receiving a response message from the network entity; performing sub-task processing during a time period; identifying at least one sub-task completed during the time period; and transmitting a message including result information to the network entity on the basis of the at least one sub-task.

Description

Method and device for multimedia call service in wireless communication system

[0001] The present disclosure relates to a wireless communication system. More specifically, it relates to a method and device for effectively providing an inference service for a call transmission and reception service in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in 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 present disclosure can provide a method and device for dynamically performing sub-task processing according to an agreement between a terminal and a network entity in a wireless communication system.

[0009] Figure 1 is a diagram showing the structure of a wireless communication system that provides voice and video calls in a mobile communication network.

[0010] Figure 2 is a diagram showing the relationship between the input / output sub-task identifier, the sub-task input / output media list, and the sub-task identifier of the sub-task.

[0011] FIG. 3 is a diagram illustrating a method for executing an AI model in MF according to one embodiment of the present disclosure.

[0012] Figure 4 illustrates a detailed and improved communication method for a data channel establishment request process between IMS-AS and DCSF for a terminal to be used in a call and a counterpart terminal (UE2).

[0013] FIG. 5 is a diagram illustrating a process of providing task configuration information for each task when one or more tasks are selected according to one embodiment of the present disclosure.

[0014] FIG. 6 is a diagram illustrating a process for providing integrated task configuration information when one or more tasks are selected according to one embodiment of the present disclosure.

[0015] FIG. 7 is a diagram for explaining a detailed communication method between a terminal and DCSF and DCAS according to one embodiment of the present disclosure.

[0016] FIG. 8 is a diagram illustrating a dynamic task configuration according to one embodiment of the present disclosure.

[0017] FIG. 9 is a diagram illustrating a method for performing dynamic task configuration according to one embodiment of the present disclosure.

[0018] FIG. 10 is a diagram showing the configuration of a terminal according to one embodiment of the present disclosure.

[0019] FIG. 11 is a diagram showing the configuration of a base station according to one embodiment of the present disclosure.

[0020] FIG. 12 is a diagram showing the configuration of a network entity according to the present disclosure.

[0021] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0022] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.

[0023] 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. In each drawing, identical or corresponding components are assigned the same or different reference numbers.

[0024] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and these may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.

[0025] In the present disclosure, it will be appreciated that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed based on computer program instructions. These computer program instructions can be selectively installed in at least one processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by any one or any combination of at least one processor of the computer or other programmable data processing equipment create 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 an article of manufacture that includes 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).

[0026] 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 mentioned in the blocks may occur out of order. For example, two blocks (or functions) depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on the corresponding function.

[0027] The term '~ unit' used in the embodiments of the present disclosure means a software or hardware component such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and the '~ unit' performs certain roles. However, terms including '~ unit' are not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~parts' may be implemented to play one or more central processing units (CPUs) within the device or secure multimedia card. Also, in an embodiment, the '~parts' may include one or more processors.

[0028] As described above, it should be noted that the blocks and combinations of flowcharts described in the present disclosure may be implemented by one or more computer programs containing instructions. One or more computer programs may be stored entirely in a single memory device, or one or more computer programs may be divided and stored in different portions across multiple memory devices.

[0029] Additionally, any / any function or operation described in the present disclosure may be processed by a single processor or a combination of processors. The single processor or the combination of processors may include circuitry that performs processing, such as an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on a chip (SoC), an IC, or similar circuitry.

[0030] It should also be noted that the various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0031] Such software may be stored on a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores one or more computer programs (software modules), wherein the one or more computer programs include computer-executable instructions that, when executed alone or collectively by one or more processors of an electronic device, cause the electronic device to perform a method according to the present disclosure.

[0032] The software may be stored in a temporary or non-transitory storage device, for example, in the form of a read-only memory (ROM) (whether erasable or rewritable), a random access memory (RAM), a memory chip, a device, or an integrated circuit (IC). The software may also be stored in an optically or magnetically readable medium, for example, a compact disc (CD), a digital versatile disc (DVD), a magnetic disk, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transitory machine-readable storage media suitable for storing a program for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing a device or method according to any one of the claims of the present specification, and a non-transitory machine-readable storage medium storing such a program.

[0033] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an action corresponding to it, or omitting or dropping an action for a lower priority.

[0034] Hereinafter, 'A or B' described in the present disclosure may be understood as 'A and / or B', which may be understood to include 'A', or 'B', or 'A and B'.

[0035] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0036] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0037] Additionally, 'A / B' described in the present disclosure may be understood as 'A and / or B', which may be understood to include 'A', or 'B', or 'A and B'.

[0038] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood to include 'A', or 'B', or 'A and B'.

[0039] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood to include 'A', or 'B', or 'A and B'.

[0040] In addition, it can be understood that the 'case where conditions A and B are satisfied' described in the present disclosure is not necessarily limited to the case where both conditions A and B are satisfied, but may include the case where each of conditions A or B is satisfied, the case where both conditions A and B are satisfied, or the case where one or more additional conditions are satisfied together.

[0041] Additionally, throughout this specification, ordinal terms such as "first," "second," "third," and the like (and modifiers thereof) are used solely to distinguish between various instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information, as described below. Unless the context clearly requires otherwise, the use of such ordinal terms does not require that the elements, operations, or information distinguished by them be structurally, numerically, or inherently different. For example, "a first signal" and "a second signal" may represent instances of the same signal transmitted at different times, may represent signals containing the same core information albeit with some modifications, or may represent signals having different content or characteristics depending on the specific context. Similarly, "a first value" and "a second value" may represent measurements or applications of the same magnitude in different circumstances, or may represent different magnitudes. Such interpretation should be determined by the specific technical context, functions and relationships described in the relevant portions of the specification and claims.

[0042] Furthermore, although terms such as "first" and "second" described in this disclosure are used to refer to various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood to be used merely to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element.

[0043] Additionally, it may be understood that the terms "first~" and "second~" described in this disclosure may refer to the same or different elements. For example, if the elements are information, the first information and the second information may both be information, and in some cases, they may be the same information or different information.

[0044] In addition, the expressions "if" and "in case that" described in the present disclosure or claims may be interpreted to mean "when or upon," "in response to," or "based on," or "according to," depending on the context, and these expressions may be used interchangeably. In addition, in addition to these expressions, other expressions having substantially the same meaning may be used interchangeably, within the scope that does not impair the technical features of the present disclosure.

[0045] Additionally, the term "not perform" as used in this disclosure or claims may be understood to mean omitting or skipping a step, depending on the context. Such terms may be replaced with other terms having the same or substantially similar meaning.

[0046] Additionally, "transmitting a message including A and B" as described herein may be interpreted to include both (i) cases where A and B are transmitted in a single message, as well as (ii) cases where A and B are transmitted individually via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply when a message including two or more items, such as A, B, and C, is transmitted together or individually.

[0047] Additionally, 'sending a message containing A and sending a message containing B' can also be interpreted as sending a single message containing A and B.

[0048] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure will be expressed in the singular or plural, 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 the plural may be composed of singular elements, or components expressed in the singular may be composed of plural elements.

[0049] The drawings or flowcharts described below illustrate exemplary methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods depicted in the flowcharts of the present disclosure. For example, although depicted as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in different orders, or occur multiple times. In other instances, any step may be omitted or replaced with another step.

[0050] The methods and devices proposed in the embodiments of the present disclosure are not limited to each embodiment, and may be utilized as a combination of one or more embodiments, all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as determined by a person skilled in the art.

[0051] In this case, even if any wording is mentioned in different embodiments, if the concepts correspond, they may be used interchangeably, combined, or substituted. For example, for identical or corresponding concepts, even if one embodiment uses the expression "A" and another embodiment uses the expression "B," these may be understood interchangeably, substituted, or combined.

[0052] In the following description, terms used to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. In addition, the terms may be replaced with terms defined in the 3rd generation partnership project (3GPP) Technical Specifications (TS), if appropriate.

[0053] Hereinafter, the base station 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, a BS (base station), a radio access unit, a base station controller, or a node on a network. In addition, the base station of the present disclosure may include a structure that is split into a central unit (CU) and a distributed unit (DU). In this structure, the CU is responsible for the upper layers of the control and user planes, and the DU is responsible for radio resource processing of the lower layers. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are separated into the CU and DU.

[0054] The terminal may include a UE (user equipment), an MS (mobile station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions.

[0055] In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station.

[0056] In addition, although the fifth generation mobile communication system (5G, new radio, NR) and the sixth generation mobile communication system (6G) may be described below as examples, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. For example, this may include new and evolved mobile communication systems developed after 5G and 6G. Furthermore, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as determined by a person having skilled technical knowledge.

[0057] In the following description, the terms "physical channel" and "signal" may be used interchangeably with data or control signals. For example, while PDSCH (physical downlink shared channel) refers to a physical channel through which data is transmitted, PDSCH may also be used to refer to data. That is, in the present disclosure, the expression "transmitting a physical channel" may be interpreted equivalently to the expression "transmitting data or a signal through a physical channel."

[0058] In the following description of the present disclosure, upper layer signaling may be signaling corresponding to at least one or a combination of one or more of MIB (master information block), SIB (system information block), SIB M (M=1, 2, …), RRC (radio resource control), MAC (medium access control) CE (control element), NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).

[0059] In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using a physical layer channel or signaling of PDCCH (physical downlink control channel), DCI (downlink control information), UE-specific DCI, group common DCI, common DCI, scheduling DCI (e.g., DCI used for the purpose of scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not for the purpose of scheduling downlink or uplink data), physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling may also be referred to as physical layer signaling.

[0060] Hereinafter, the expression that information can be configured from a base station in the present disclosure or claims may mean that a terminal receives the information from the base station through physical layer signaling or upper layer signaling, depending on the context, and such expression may be replaced with other terms having the same or substantially similar meaning.

[0061] The operating principle of the present disclosure is described in detail with reference to the attached drawings below.

[0062] Figure 1 is a diagram showing the structure of a wireless communication system that provides voice and video calls in a mobile communication network.

[0063] FIG. 1 illustrates an IMS (internet protocol Multimedia Subsystem; IP Multimedia Subsystem) architecture that a first terminal (user equipment 1; UE1) can use for real-time multimedia transmission and reception with a second terminal (UE2), and the functions of the components are described as follows.

[0064] The Proxy-Call Session Control Function (P-CSCF) is the first point of contact in the IMS network and is responsible for communication between user equipment (UEs) and the IMS network. This functional element processes Session Initiation Protocol (SIP) requests and responses and forwards user requests to the Serving-Call Session Control Function (S-CSCF). The P-CSCF also performs authentication and security processing and routes UE requests to the appropriate location within the IMS network. Additionally, the P-CSCF supports roaming within the network.

[0065] The Serving-Call Session Control Function (S-CSCF) is a core element of the IMS network, managing and controlling user sessions. This functional element routes SIP messages and handles user registration and authentication. The S-CSCF communicates with the Home Subscriber Server (HSS) to retrieve user profiles and establish sessions. Additionally, the S-CSCF provides interfaces with various application services to control and coordinate them.

[0066] The Home Subscriber Server (HSS) is a database that stores and manages user information within the IMS network. The HSS manages user profiles, including user authentication, authorization, and location management. The HSS communicates with the S-CSCF to provide user information, providing all essential information about the user.

[0067] Unified Data Management (UDM) provides the ability to manage data related to user profiles in 5G networks. Designed according to the 3rd Generation Partnership Project (3GPP) standard, UDM is a network function responsible for user profile management, session management, authentication and authorization, policy and rule enforcement, and data synchronization and distribution in 5G core networks.

[0068] The IMS Application Server (AS) is a server that provides various applications and services in the IMS network. The IMS AS supports a variety of SIP-based application services, providing users with a variety of services, including voice, video, and messaging. It communicates with the S-CSCF to process service requests and performs various functions required for service provision.

[0069] The Data Channel Signaling Function (DCSF) manages signals related to data channels in IMS networks. DCSF is used to initialize and control the data channels through which application data is transmitted. This function is essential for efficiently supporting real-time data transmission, as well as multimedia services, within IMS networks. One of DCSF's primary roles is to establish data channels. This defines and configures data channel parameters using protocols such as the Session Initiation Protocol (SIP) or Session Description Protocol (SDP). These parameters include channel type, bandwidth, and transmission format. After establishing a data channel, DCSF continuously manages the channel. This includes functions such as monitoring channel status, maintaining, re-establishing, and terminating sessions. Furthermore, DCSF handles changes that may occur during the session, ensuring stable data transmission.

[0070] DCAR (Data Channel Application Repository; DC Application Repository) is a component in the IMS architecture responsible for storing and processing user data. DCAR allows users to create data channels (data transmission) for data communication services. User data or operator applications stored within DCAR can then be transmitted to user terminals via the DCSF and MF (Media Function).

[0071] The Media Function (MF) is a functional element responsible for media streaming and processing within an IMS network. The MF processes media such as voice, video, and data and collaborates with the Media Gateway to manage media streams. This facilitates seamless media transmission and processing. The Media Function processes media streams generated from various services, such as calls, video streaming, and video conferencing. This ensures high-quality delivery of multimedia data between users and enables users to utilize services in their intended manner.

[0072] IMS-AGW (IMS Access Gateway) is a gateway that provides an interface between the IMS network and external networks. IMS-AGW supports interoperability between external networks and IMS networks, converting and forwarding SIP signals and media streams. This gateway ensures seamless communication with external networks.

[0073] The Data Channel Application Server (DCAS) is part of the IMS architecture and is a server that transmits various application data over data channels. It is designed to efficiently handle SIP-based multimedia sessions as well as data transmission within the IMS network. DCAS manages the transmission of data, not media streams. This can include various data formats, such as text, files, application-related data, and status updates. For example, it provides functions such as file sharing during video conferencing or location synchronization in real-time games. DCAS uses SIP to establish, maintain, and terminate sessions. It coordinates data channel settings through SIP messaging, enabling bidirectional data transmission. DCAS supports a variety of data formats. This means it can be used in a variety of applications and services. Examples include real-time data synchronization for business applications, communication with Internet of Things (IoT) devices, and real-time chat applications. DCAS is part of the IMS architecture and operates in integration with other IMS components. For example, it works with the CSCF to perform session control and with the HSS to handle user authentication and authorization management.

[0074] Based on the aforementioned components, the UE can request a connection to the counterpart terminal as follows.

[0075] First, the UE sends a request to the P-CSCF via a Session Initiation Protocol (SIP) INVITE message to establish a data channel with the other terminal. This SIP message includes media-related parameters and multiplexing-related requirements within the Session Description Protocol (SDP). Furthermore, the UE can include an SDP offer containing bootstrap information, along with an SDP offer for connecting an existing video or audio session, within the SIP INVITE message to utilize the IMS data channel service.

[0076] The P-CSCF forwards the received SIP message to the S-CSCF. The S-CSCF is the main functional element responsible for session control within the IMS network, manages the UE's session, and interacts with the related application server (IMS AS). The S-CSCF processes the message, verifies user authentication and authorization if necessary, and then forwards the message to the IMS AS. Upon receiving the SIP INVITE message including the above SDP information, the S-CSCF can forward the contents of the bootstrap data channel SDP offer to the IMS AS if the SIP INVITE message includes a bootstrap data channel SDP offer for a data channel service connection request. At this time, the S-CSCF can check whether the terminal or network supports IMS-DC based on the contents of the received bootstrap 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.

[0077] An IMS AS that receives a bootstrap-related SDP offer message from an S-CSCF can first check with an 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, the IMS AS can perform an MMTel (multimedia telephony) session setup operation without connecting the data channel through a general IMS process. In addition, if the user cannot use the data channel-based service, the IMS AS can delete the DC (data channel)-related media information in the SIP INVITE message received from the S-CSCF, update the SIP INVITE message, and then forward the updated SIP INVITE message to the S-CSCF.

[0078] The S-CSCF forwards the UE's data channel request to the IMS AS. The IMS AS, a node that performs various service logic, initiates interactions with the DCSF and MF in response to the data channel establishment request. The IMS AS analyzes the request and initiates signaling procedures to establish the data channel.

[0079] If the service user can use the IMS data channel-based service, the IMS AS can communicate with the DCSF to perform data channel bootstrapping through a data channel call request as one of the signaling processes for data channel establishment. The IMS AS can select a DCSF by performing discovery and selection of a DCSF instance from the NRF (network repository function) based on the network operator's local settings 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. The DCSF is responsible for establishing, managing, and controlling the data channel, and generates and transmits the necessary SIP / SDP (Session Description Protocol) signaling messages. The DCSF configures the data channel parameters according to the request of the IMS AS, and also manages the data channel to be properly established on the other terminal side. Additionally, DCSF can determine MDC1 media information to enable UE to download applications via MF or MRF (Media Resource Function).

[0080] Based on the above decision information, DCSF can forward a MediaControl_MediaInstruction message containing information such as SessionID, MediaInstructionSet, etc. to the IMS AS. DCSF can also forward the MediaInstructionSet to the IMS AS, including the MDC1 media endpoint address, DC stream ID, and replacement information for the uniform resource locator (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.

[0081] 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.

[0082] 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.

[0083] After completing signal processing of the data channel based on the MF information received from the IMS AS, the DCSF communicates with the Media Function (MF) to process the media stream. The MF processes the actual media data (e.g., audio, video, etc.) to be transmitted over the data channel. The MF prepares necessary tasks, such as transcoding, mixing, and converting the media stream, and establishes the data transmission path. During this process, the MF performs quality of service (QoS) management and security functions to ensure stable data transmission.

[0084] Once the DCSF and MF successfully establish a data channel, the IMS AS can send 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. Once the data channel is established, data transmission between the UE and the remote terminal begins. This data channel is connected between the UE, the MF, and the remote terminal, and the MF processes the media data and performs necessary conversion tasks, transmitting the data in real time.

[0085] Multimedia calling based on the IMS architecture can be extended to include the following three elements to provide AI learning or inference services as intended in the present disclosure.

[0086] 1. AI Model Configuration and Selection Method: Service providers and users may be provided with guidance on how to select and configure an appropriate AI model for AI learning or inference. AI models may be provided not only by service providers but also by third-party operators. The guidance may include functions for assessing the characteristics, strengths, and weaknesses of various AI models, as well as their compatibility with the collected data of the terminals / subscribers participating in the call, as well as the terminal execution environment and performance.

[0087] 2. Method for determining eligibility for AI processing and service use through MF of call participants: A procedure may be provided to determine eligibility for use of AI processing functions by terminals / subscribers participating in a call. If AI processing is partially or fully executed on a network server, a procedure may be defined for determining eligibility for use of AI processing functions through MF, a network server in the IMS architecture. If a service provider distinguishes available AI processing functions by subscriber, a procedure may be provided to provide a list of AI processing functions appropriate for the terminal / subscriber's subscription history.

[0088] 3. Method for adjusting the real-time MF processing scope according to the status of each terminal: After the AI ​​processing function begins, a method can be provided to optimize the integration of AI processing between the terminal and the MF based on the dynamically changing terminal performance indicators of each terminal. By dynamically adjusting the processing of the terminal and the MF according to various background app execution situations, the mobility of the terminal / subscriber, and the network connection status, a seamless service experience and efficiency can be achieved.

[0089] According to the present disclosure, a method for providing an AI learning or inference service to a real-time multimedia call transmission and reception service between IMS endpoints (hereinafter referred to as endpoints) based on the aforementioned IMS multimedia call service architecture can be provided.

[0090] Endpoints are components capable of transmitting and receiving multimedia over an IMS network, and may include, for example, terminals and servers. Accordingly, real-time multimedia calls may be between terminals, between terminals and servers, or between terminals, servers, and terminals.

[0091] The multimedia transmitted / received between endpoints may be generated in real time at the terminal or server, or may be a combination of real-time generation and non-real-time generation in advance.

[0092] In the present disclosure, multimedia refers to various information to be transmitted and received between endpoints, such as video, audio, 3D graphics, spatial information, metadata, sensor measurement values, and intermediate data of AI models, and is not limited to the examples described above.

[0093] A service provider according to the present disclosure may provide a task to a terminal / subscriber. The task may comprise a series of processing steps that input multimedia transmitted from an endpoint, such as a terminal or server, and provide output as multimedia received by the other terminal or server.

[0094] In the present disclosure, a task may include a series of process groups that receive input data, such as multimedia, and generate output data. The task may be performed on any type of computing device, and computing devices may include a transmitting terminal, a receiving terminal, a network edge computing server (Edge Application Server), and a cloud computing server. Examples of tasks may include 2D rendering of a 3D graphic model, AI learning or inference, such as voice translation or object recognition in an image. A user of the service, acting as a sender or receiver of multimedia, may select and apply a desired task from among the tasks provided by the service provider for the multimedia being transmitted and received.

[0095] A task may have a user-identifiable description (e.g., "Display audio captions") and an identifier that allows terminals and service providers to uniquely identify the task within the service. More specifically, a task may be composed of one or more subtasks. Accordingly, a task may be linked (mapped) to a task configuration, which is information describing a list of subtasks included in the task, information about each subtask, and their respective connection relationships, via a task configuration identifier.

[0096] Additionally, tasks may have classification symbols assigned based on the service provider's subscriber identification policy. For example, there may be AI models that are not available to free users. For example, the accuracy and performance specifications of an AI model for a low-cost subscription plan may differ from those for a high-cost subscription plan. Therefore, tasks may include classification symbols that distinguish between free and paid users, classification symbols that distinguish by country, classification symbols that distinguish by the type of media to which the task applies (e.g., video, audio, sensor, etc.), and classification symbol information based on the service provider's separate policies. If tasks are provided differently for each user, for example, purchase information for individual tasks may be recorded in the subscriber subscription database managed by the service provider. Tasks that are only available to users who have purchased a task may be included in the task list only if they are included in the purchase history managed by the service provider after a query based on the terminal identifier when the terminal requests the task list.

[0097] In this disclosure, subscriber subscription data may include a list of service functions (e.g., tasks) or network resources (e.g., AI model repository, AI model) available to terminals and apps based on a user's service subscription. User subscription data is managed by a service provider and is retrieved upon terminal request. Terminal requests may be provided or rejected after confirming the user's subscription to the service function or network resource. Service providers may include mobile network operators (MNOs) and over-the-top (OTT) service providers.

[0098] In the present disclosure, resources may include network functions, edge computing servers, user data repositories, content, AI models, etc. of a network. Network functions (e.g., DCSF, DCMF) capable of processing specific protocols (e.g., data channels), edge computing servers (EAS) for executing programs on the network, user data repositories capable of storing user data on the network, etc. may be provided to specific users rather than all users after an identifier search, and in some cases, may be provided with separate charges based on the time of resource usage or data size.

[0099] The information included in the task is as shown in Table 1 below:

[0100] [Table 1]

[0101]

[0102] A service provider according to the present disclosure may have one or more tasks and may deliver a list of tasks that are available to and usable by an endpoint.

[0103] An endpoint according to the present disclosure may select one or more tasks for multimedia to be transmitted and received and generate output multimedia by applying the tasks to the input multimedia.

[0104] A service provider according to the present disclosure can check the subscription information of an endpoint requesting a service and a counterpart endpoint with which the endpoint wishes to make a call, determine whether the endpoint is eligible to use the MF of the IMS architecture, determine the subscription history within the service provider's service, and provide the endpoint with a list of only tasks that are determined to be appropriate based on the level or qualification of the subscribed service history.

[0105] The task list is a list of tasks provided by the service provider, and can list all tasks that can be used on the terminal.

[0106] The information included in the task list is as shown in Table 2 below:

[0107] [Table 2]

[0108]

[0109] A task according to the present disclosure is composed of one or more subtasks, and a subtask may be a group of processes of a task that can be divided and executed at two or more endpoints.

[0110] For example, subtasks can be organized into units that can be divided and executed between different terminals or between a terminal and a server.

[0111] A task according to the present disclosure may have a task configuration (hereinafter referred to as a task configuration), which is information describing information on sub-tasks that constitute the task and performance requirements required for each sub-task to be executed on a computing device (terminal or server).

[0112] A task configuration consists of a list of subtasks within a task and the information required to execute each subtask. Using the task configuration, a terminal or server can determine the internal and external conditions required to execute a task, at the subtask level.

[0113] A task configuration has a configuration identifier, configuration version information, and an identifier of the task being described, and can have a list of subtasks, which is a list of information about subtasks belonging to the task.

[0114] A subtask can be identified as a unit whose execution subject can be separated. For example, in a task having n subtasks, when 0 < k < n, a total of n server tasks can be executed on one or more terminals by executing any k subtasks on a first terminal and nk subtasks on a second terminal. k can be determined based on the performance that the first terminal can execute up to the kth subtask. When the first terminal transmits the output of the kth subtask as a result of executing the k subtasks to the second terminal, the second terminal receives this, applies the output of the kth subtask as input to the (k+1)th subtask, executes up to the nth subtask, and the output of the last nth subtask can be considered to be the same as the output of the task.

[0115] The information included in the task configuration is as shown in Table 3 below:

[0116] [Table 3]

[0117]

[0118] Figure 2 is a diagram showing the relationship between the input / output sub-task identifier, the sub-task input / output media list, and the sub-task identifier of the sub-task.

[0119] In Fig. 2, subtasks i, j, k, and m can each be identifiers of four different subtasks. In Fig. 2, which is centered around subtask k, subtask k receives the output media of subtasks i and j as input media. The output media of subtask k becomes the input media of subtask m, which is a subsequent subtask. Therefore, the input subtask identifiers for subtask k are i and j, and the output subtask identifier is m. Subtask i can output x multimedia to its output media list, and subtask j can output y multimedia to its output media list. The subtask input media list of subtask k can receive x+y multimedia as input.

[0120] A service provider according to the present disclosure may have tasks, a list of tasks, and a task configuration for each task.

[0121] A service provider according to the present disclosure can provide a list of the provided tasks to an endpoint, and the endpoint can receive a task configuration from the service provider when selecting one of the tasks to execute from the list of received tasks.

[0122] The DCAS according to the present disclosure may be provided with a task, which is a service to be provided to a user as a component that provides a service, a list of tasks, and a task configuration, which is information for setting each task.

[0123] DCAS may have a task list and a task service subscriber database.

[0124] To initiate a service, the DCAS can transmit a list of tasks and a task configuration list for each task to the DCSF. DCSF can transmit the task list in response to a task request from a terminal via the IMS AS and receive the identifier of the task selected by the user from the terminal.

[0125] An endpoint according to the present disclosure can obtain a task configuration of a task to be selected, determine that the task is composed of subtasks, and determine the range of subtasks that can be performed at the endpoint from the performance requirement specifications of each subtask.

[0126] An endpoint according to the present disclosure can determine whether to select a task and the scope of sub-tasks to be performed and transmit this to a service provider or a counterpart endpoint.

[0127] A service provider or counterpart endpoint according to the present disclosure can receive task information and sub-task execution range information determined by a terminal, and determine whether to execute the remaining sub-tasks constituting the task accordingly.

[0128] An endpoint according to the present disclosure can achieve a seamless service experience and efficiency by dynamically adjusting the sub-task execution range between the endpoint and the counterpart endpoint based on various variables such as the execution status of various background apps of the endpoint, the status of available resources such as CPU / GPU / memory, the availability of MF within a cell based on the mobility of the terminal / subscriber, and changes in transmission bandwidth based on the network connection status.

[0129] The relative endpoint according to the present disclosure can execute a changed sub-task execution range according to the dynamically adjusted sub-task execution range of the one endpoint and generate a result thereof.

[0130] As an example of a task to help understand the invention, we can assume a task that inputs video and audio of a video call as multimedia and outputs video, audio, and translated subtitles as multimedia.

[0131] This example consists of a first endpoint, Terminal 1, and a second endpoint, Terminal 2. The third endpoint, MF, only handles data mediation and does not handle any processing. The MF's omission of processing is intended to reduce the complexity of the example, but it is self-evident that the MF could handle processing in other examples.

[0132] In this example, a user on Terminal 1 can select a task to translate their conversation into the language of a foreigner while video calling. This allows the user on Terminal 2 to listen to the user on Terminal 1's voice and view subtitles created from text extracted from the voice alongside the user's video.

[0133] In this example, the task may be provided as a unit of a task provided by a service provider with a task name such as 'display voice subtitles', including a first AI model subtask that extracts a human voice band from audio, which is one of the multimedia transmitted from the first terminal, a second AI model subtask that converts the extracted voice into text, a third subtask that visualizes the resulting text as text, and a fourth subtask that combines the text with an image. Each of the above-described steps may be configured as a subtask, and since a typical AI model is configured with multiple layers, the first or second AI model subtask may also be configured as a set of multiple subtasks.

[0134] In this example, the user of the first terminal receives a task configuration, which is information for determining whether the execution of a task can be completely processed within the first terminal, from the service provider, and based on performance information of the sub-tasks included in the task configuration, determines how many sub-tasks to process within the first terminal and requests that the remaining sub-tasks be processed within the second terminal, and transmits the determination result to the second terminal to request that the second terminal perform the remainder of the task.

[0135] In this example, the first terminal informs the second terminal that it will deliver the results of executing up to the kth subtask for a task consisting of, for example, n subtasks, and the second terminal can secure the terminal resources necessary for executing from the k+1th subtask to the nth subtask and then send an OK response.

[0136] In another example, for dynamic configuration, the first terminal may inform the second terminal that it will deliver three different ranges of execution results, i.e., the i-th, j-th, and k-th, for a task consisting of, for example, n subtasks, and the second terminal may secure terminal resources capable of responding to all three cases in executing the i+1-th, j+1-th, and k+1-th subtasks to the n-th subtask and then send an OK response.

[0137] The first terminal may be able to perform up to the kth task within the target time for some multimedia input frames, or may be able to perform only up to the ith task for some multimedia input frames within the target time, depending on the terminal's own processing performance or internal / external situational changes. Considering these situational changes, three sub-task ranges (i, j, and k) are designated, so that the second terminal can identify the sub-task range in which the multimedia input frame received from the first terminal was performed, and execute the subsequent sub-task range.

[0138] The first terminal may include or separately transmit a sub-task identifier in the output frame for each input frame to enable the second terminal to convey the scope of the sub-task it has performed. The second terminal may identify the scope of the sub-task performed by the first terminal from signal information received within the received multimedia input frame or separately.

[0139] FIG. 3 is a diagram illustrating a method for executing an AI model in MF according to one embodiment of the present disclosure.

[0140] In step 1, the UE (terminal) can register with the CSCF (including P-CSCF, S-CSCF, etc.) and transmit a SIP message including information requesting settings for AI / ML media processing. The UE can request registration with the IMS network via a SIP REGISTER message. The SIP REGISTER message can include information indicating that the UE can support task-based AI / ML media processing functions. The P-CSCF can receive the SIP REGISTER message and forward it to the S-CSCF to complete the registration procedure of the UE. The S-CSCF can check the registration status of the UE and record related information.

[0141] In step 2, the UE can invite UE2 as a counterpart terminal for a conversation. The UE can establish a call session with UE2 by sending a SIP INVITE message to the CSCF. The SIP INVITE message can be forwarded to the IMS AS via the CSCF. The IMS AS can receive the request to establish a call session with UE2 and initiate the session establishment procedure with UE2. The IMS AS can prepare the resource allocation and data channel configuration required for the step of establishing a call session between the UE and UE2.

[0142] In Step 3, the IMS AS can confirm the data channel usage request within the SIP message and forward information about the data channel usage request to the DCSF. The IMS AS can then communicate with the DCSF to allocate the necessary data channel resources for the session. The DCSF is responsible for setting up and managing the data channel and can allocate the necessary resources to the MF.

[0143] In this disclosure, the data channel for receiving a task list, etc. from a service provider is illustrated as a bootstrap data channel (step 6), and the data channel for negotiating task configuration between a terminal and an MF is illustrated as an application data channel (step 11).

[0144] A bootstrap data channel can enable MNO applications to be downloaded from the Data Channel Application Repository (DCAR) via the DCSF and MF to endpoints such as terminals. Applications stored within the DCAR may include prerequisite information for service access (service discovery URL, pass key, etc.). However, applications can also be downloaded from the DCAS repository via the MF to endpoints such as terminals. Therefore, establishing a bootstrap data channel for service provider access is only one example; access to application data channels is also possible.

[0145] Therefore, DCSF can instruct DCAS to establish a bootstrap data channel in step 6 if it has a bootstrap application within DCAR for the service task list and task configuration during the service provisioning phase, and to establish an application data channel within DCAS.

[0146] In Step 4, a multimedia call session can be established. Audio and video sessions between UE and UE2 can be successfully established. This enables a basic multimedia call, allowing both parties to exchange data in real time.

[0147] Step 5 is a setup procedure for AI / ML media processing, and may include steps 6 to 12.

[0148] In step 6, a bootstrap data channel can be established between the UE and the MF. By establishing a bootstrap data channel with the MF, the UE can establish an environment for transmitting the initial data required for AI / ML media processing. This channel can provide a foundation for information exchange required for subsequent AI / ML tasks.

[0149] In step 7, a media processing task list download procedure may be performed between the UE and the MF and DCSF. The UE may communicate with the MF and DCSF to download a list of available AI / ML media processing tasks. This list may include various AI / ML-based media processing options.

[0150] In step 8, the UE may provide the user with a list of AI / ML media processing tasks. The UE may present the user with a list of downloaded AI / ML media processing tasks. The user may select a desired task from this list.

[0151] In step 9, an AI / ML task configuration application download procedure may be performed between the UE, MF, and DCSF. The UE, in collaboration with the MF and DCSF, may download a configuration application for the AI / ML media processing task selected by the user. This application may be used to perform detailed task configuration.

[0152] In step 10, the UE may provide configuration options to the user. Based on the downloaded configuration application, the UE may present task configuration options to the user. These options allow the user to adjust the details of the AI / ML media processing task.

[0153] In step 11, application data channel setup and configuration information transmission between the UE and the MF may be performed. The UE may establish an application data channel with the MF and transmit configuration information selected by the user to the MF.

[0154] In step 12, the MF can set up an AI / ML media processing task. The MF can set up an AI / ML media processing task based on the received configuration information. This task can optimize the MF's resources to process media data in real time.

[0155] In step 13, the UE may transmit a media stream to the MF. The UE may transmit audio and video streams to the MF. These streams may be received by the MF for AI / ML-based processing tasks, and any necessary conversion and processing may be performed.

[0156] In Step 14, MF can process media streams according to the configuration. MF can process media streams according to pre-configured AI / ML task settings. This processing occurs in real time and can apply AI / ML technologies such as voice recognition, noise removal, and image enhancement.

[0157] In step 15, the MF may transmit the processed media stream to UE2. The MF may transmit the processed media stream to UE2. UE2 may receive this stream and deliver it to the user, ultimately providing high-quality media content.

[0158] In step 16, the UE may transmit a task configuration update to the MF. If the user changes the task settings, the UE may transmit these changes to the MF via the application data channel.

[0159] In step 17, the MF can apply a task configuration update. Based on the received configuration information, the MF can set up an AI / ML media processing task. This task can optimize the MF's resources to process media data in real time. This allows the user to adjust the details of the AI / ML task even during a call.

[0160] In addition to the above-described method of operation, the following changes may be considered in the communication between the service provider and the endpoints according to the present disclosure.

[0161] Before step 1 of the aforementioned drawing 3 begins, a service provisioning step by the service provider may be initiated.

[0162] A service provider can be represented as a DCAS within the IMS architecture, and the DCAS can delegate service operations to the DCSF by transmitting basic information and service settings related to the service during the service preparation phase.

[0163] The service according to the present disclosure is characterized by task-based real-time multimedia processing, and basic information related to the service may include information such as tasks, a list of tasks, and task configurations. Information related to service settings may include a service identifier, a channel type for task list discovery, a channel type for task configuration negotiation, a channel type for transmitting and receiving multimedia other than existing IMS media (e.g., 3D graphics, binary data, intermediate data, etc.), a path / stream ID of a service application repository, and an extended protocol identifier for dynamic task configuration negotiation.

[0164] DCSF can allocate and provide data channels, stream IDs, MF instances, etc. according to the provisioned settings for requests from endpoints that wish to access the service.

[0165] In step 1 or step 6 of the aforementioned FIG. 3, the following may be considered as information indicating that the UE can support task-based AI / ML media processing functions:

[0166] - IMS call type or IMS service identifier: A service identifier that includes the profile and data channel requirements of the multimedia being transmitted and received, such as a voice call, video call, or avatar call. A service provider can identify that it can support the task-based media processing function according to the present disclosure for access from an App with an identifiable identifier (e.g., a task-based media call, etc.).

[0167] - Supported DC App Identifier or Bootstrap DC App identifier: An identifier of a Data Channel Application installed or to be installed on a terminal to receive a service from a service provider. The service provider can identify an App with an identifiable identifier as being capable of supporting the task-based media processing function according to the present disclosure.

[0168] - DC application profile or DC application attribute and binding information included therein: Based on the above information transmitted from the service provider's App or 3rd party App, the service provider can identify that the terminal can support the task-based media processing function according to the present disclosure.

[0169] - bootstrap data channel SDP with Stream ID: When the Stream ID value specified in the SDP is a specific value, the service provider can identify that the terminal can support the task-based media processing function according to the present disclosure.

[0170] Step 3 of Figure 3 illustrates a process for requesting a data channel connection between IMS-AS and DCSF for a terminal to be used in a call and a counterpart terminal (UE2).

[0171] Figure 4 illustrates a detailed and improved communication method for a data channel establishment request process between IMS-AS and DCSF for a terminal to be used in a call and a counterpart terminal (UE2).

[0172] Figure 4 illustrates a more detailed and improved communication method for step 3 of Figure 3. After a data channel establishment is requested from IMS-AS to DCSF in step 3 of Figure 4, the eligibility of UE and UE2 to participate in the call must be reviewed from two aspects.

[0173] The first aspect is based on the MF usage rights of the user's subscription plan. For a terminal to request work from a network server and receive results, appropriate subscription and billing settings are required. Accordingly, the DCSF must determine, through the CSCF, whether the UE participating in the call and UE2 have subscription details and permissions for MF usage from the HSS or UDM. If UE2 is subscribed to a Remote IMS (i.e., another communications network), whether UE2 is billed and how it is billed when the MF within the UE's network performs processing can be determined based on the Service Level Agreement (SLA).

[0174] The second aspect is based on the service provider's service subscription information. The terminal / subscriber may not have secured the right to use all tasks of the task service provider. For example, AI models require high performance and power, so there may be differences in functionality and accuracy between the free and paid versions. Accordingly, the DCSF can contact the DCAS to request a list of appropriate tasks that the UE and UE2 participating in the call can receive. The DCSF may have received a list of all tasks (including free and paid) that DCAS can provide in advance from the DCAS, but the list specific to the UE and UE2 can be managed and continuously updated by the DCAS. In response to the DCSF's request, the DCAS can generate and transmit a list of tasks that only the UE and UE2 can receive. This list may include a first list that the UE can receive, a second list that UE2 can receive, and a third list that is a common list that both the UE and UE2 can receive.

[0175] In Step 4, the DCSF can verify the subscription information of the UE and UE2 from the HSS or UDM via the S-CSCF. If both are capable of using the MF, it can be determined that the DC connection and AI services are provided.

[0176] HSS or UDM may include detailed information about the terminal's subscription, such as whether network media processing is permitted, charging information for MF use, the scope and limits of MF resources that the terminal can use, and profile information indicating this.

[0177] HSS or UDM may respond to DCSF's MF eligibility inquiry with either permission to use MF or more detailed billing information, scope / limits of MF resources, or profile information.

[0178] In step 5, the DCSF may forward the terminal's call request to the DCAS. The information transmitted may include the terminal's identifier and details related to MF usage. If information related to terminal performance (e.g., OS, CPU / GPU / memory, etc.) is received from the terminal, this information may be included.

[0179] In step 6, DCAS can transmit a task list to DCSF based on the terminal's service qualifications. DCAS can transmit a first list of tasks available to a single terminal, a second list available to the other terminal, and a third list available to all terminals, based on the terminal's qualifications among the entire list of serviceable tasks. The first, second, and third lists can be further filtered based on the resources and profile information allowed to the MF. That is, tasks that do not meet the conditions can be removed from the list.

[0180] In step 7, DCAS can transmit task configuration information for each task to DCSF, along with a list of tasks it has transmitted. DCSF can prepare task configuration information along with a task list for each terminal participating in the call, and provide task configuration information when the terminal selects a task.

[0181] In step 8, the DCSF may return the DC resource allocated to the Data channel allocation requested by the IMS AS in step 3. The resource may include Bootstrap Data channel information.

[0182] In step 9, the IMS AS can request session establishment (INVITE) to UE-2 using the received Bootstrap Data channel information.

[0183] Step 10 may correspond to step 4 of FIG. 3.

[0184] FIG. 5 is a diagram illustrating a process of providing task configuration information for each task when one or more tasks are selected according to one embodiment of the present disclosure.

[0185] FIG. 6 is a diagram illustrating a process for providing integrated task configuration information when one or more tasks are selected according to one embodiment of the present disclosure.

[0186] The terminal can select a task from a list of received tasks and receive task configuration information for configuring the task from the DCSF. If more than one task is selected, this can be the reception of task configurations for each task or an integrated task configuration.

[0187] For example, in another example, when a user requests a multi-modal service that generates subtitles and sign language by selecting the first task, 'Voice subtitle generation', and the second task, 'Sign language video generation', which take the transmission and reception of a multimedia video call as input, as shown in FIG. 5, a subtask within the first task can generate text based on the voice, and then a subtask within the second task can generate a sign language video that matches the language of the text. To this end, a subtask that is distinct from the subtasks shared within the first and second tasks can be configured, as shown in FIG. 6, and thus it is necessary to configure this as an integrated task and provide integrated task configuration information for this.

[0188] For this purpose, when multiple tasks are selected from a terminal, DCSF can notify DCAS and request a decision from DCAS on whether to provide multiple task configurations or an integrated task configuration. If an integrated task is provided, DCAS can create an integrated task configuration and pass it to DCSF.

[0189] FIG. 7 is a diagram for explaining a detailed communication method between a terminal and DCSF and DCAS according to one embodiment of the present disclosure.

[0190] Figure 7 illustrates a detailed communication method between the terminal and the DCSF and DCAS between step 7 (step 12 of Figure 7) and step 9 (step 21 of Figure 7) of Figure 3.

[0191] In step 13, the terminal can create and provide a list from which the user can select from the received task list.

[0192] In step 14, in the service and terminal according to the present disclosure, the user can select one or more tasks.

[0193] In steps 15 and 16, identifiers of the selected tasks can be passed from the UE to the DCSF via the MF.

[0194] In step 17, DCSF may transmit identifiers of selected tasks and identifiers and version information of task configurations held by DCSF to DCAS for the purpose of sharing service request status with service providers or checking new task configuration information.

[0195] In step 18, DCAS can create a new integrated task configuration if necessary. For example, if a new multimodal service configuration is required, DCAS can create multimodal service configuration information.

[0196] In step 19, DCAS may respond with an OK to DCSF to use the existing task configuration or may transmit an integrated task configuration for the tasks. For example, if multimodal service configuration information was generated in step 18, DCAS may transmit the multimodal service configuration information to DCSF.

[0197] At step 20, DCSF may decide to forward the task configuration it has or receives a new one, based on the response from DCAS.

[0198] In step 21, the terminal can download a task configuration application for task configuration from the DCSF through the MF. The task configuration application can have task configuration information for a task selected by the user, and information and methods for determining whether the terminal can perform all or part of the subtasks among the tasks. For example, operations such as determining whether hardware supports a specific video codec or collecting a profile of multimedia that can be acquired / generated by the terminal can be performed. The task configuration information includes an index to be determined by the task configuration application (e.g., a type of video codec that can be supported by hardware) and a target value (H.264, H.265, AV1, VVC, etc.), and can be reported by the task configuration application in the form of a support value of the terminal for the index (e.g., HW supported: [H.264, H.265]).

[0199] Subtask information within a task configuration may include code or links for executing the subtask. Types of executable code include, but are not limited to, scripts, binary executables, and AI models.

[0200] Considering the case where the terminal does not execute the subtask but delegates it to the MF, the subtask information may include a link rather than an executable code, and may be downloaded during the terminal selection process.

[0201] For example, in the case of an AI model, the AI ​​model may be enclosed in subtask information, or information for receiving the AI ​​model, such as a URL, may be included.

[0202] The task configuration application may receive a code for executing a subtask from a subtask link during the process of checking the performance indicators of the terminal, or may receive a separate code only for checking the indicators.

[0203] FIG. 8 is a diagram illustrating a dynamic task configuration according to one embodiment of the present disclosure.

[0204] In cases where the task configuration needs to be changed due to reasons such as terminal performance, if steps 16 and 17 of Fig. 3 are performed, the MF reset process may take time, and in most cases, it may be difficult to guarantee processing of multimedia input frames generated during the reset time. Accordingly, the terminal may determine a dynamic task configuration in the task configuration step and transmit multiple sub-task candidates for this purpose. The candidates may be from a sub-task after the first sub-task to be executed on the terminal to a final sub-task that is satisfactory based on the current terminal performance. Fig. 8 illustrates sub-tasks within a task as 1, 2, 3, 4, 5, and 6.

[0205] As illustrated in a) of FIG. 8, the terminal may specify a max UE delay time, which is the time required for processing per frame, and report to the MF that it can perform the first to fourth subtasks based on the subtasks that can be completed within the max UE delay considering the current performance. The MF may secure sufficient resources to perform the second to sixth, third to sixth, fourth to sixth, or fifth to sixth subtasks and transmit a task configuration ok response to the terminal.

[0206] In a typical case, as shown in a) of Fig. 8, when up to the 4th subtask is executed on the terminal, the result is transmitted to the MF and executed from the 5th subtask to the end.

[0207] However, if it takes more time to execute subtasks 2 and 4 as shown in b) of FIG. 8 due to changes in the internal / external environment of the terminal, the terminal may detect that subtask 4 is not completed until the max UE delay time. In this case, the terminal according to the present disclosure may immediately stop the fourth subtask at the max UE delay time, decide to transmit the result of the third subtask, which is an already completed subtask, to the MF, and transmit the identifier of the third subtask to the MF together with the result data or through a separate channel. The terminal may also transmit the start time of the current input frame and the target end-to-end delay time or target completion time information to the MF.

[0208] MF recognizes that the data received from the third sub-task result and the notified third sub-task identifier are results of the third sub-task and that execution from the fourth sub-task is required, and can generate results by completing all remaining sub-tasks from the fourth sub-task.

[0209] FIG. 9 is a diagram illustrating a method for performing dynamic task configuration according to one embodiment of the present disclosure.

[0210] Figure 9 illustrates a dynamic task configuration method in addition to the static task configuration illustrated in steps 13-17 of Figure 3.

[0211] The description of Fig. 9 is as follows.

[0212] In step 22, the task configuration application can generate a list of user-selectable task configurations from one or more support values ​​of the satisfied indicators. The task configuration application is intended to configure a specific task, but can also provide task configurations for other alternative or complementary tasks (e.g., a high-accuracy model, a mid-accuracy model, or a low-accuracy model of a large language model (LLM) model), and can generate a list of task configurations for possible tasks based on the capabilities of the terminal.

[0213] An example of a user-selectable task configuration list might be which of the video codecs supported by the terminal's hardware to use.

[0214] Another example is that the subtask execution ranges selectable on a terminal can be listed based on the execution time required when executing a subtask within a task on the terminal. To achieve this, the task configuration can present an end-to-end delay value that ensures normal service use and a max UE delay time, which is the maximum delay time on the terminal. The task configuration application can measure how many times a subtask can be executed within the max UE delay time and then include it in the selections requested from the user.

[0215] The selection may be made automatically (=without asking the user) based on the user's previous execution history, the user's preference settings, or the task configuration application's recommendation based on the terminal's performance and network status.

[0216] In the present disclosure, the user's selection of a subtask may be one or more.

[0217] In step 23, the UE can establish an application data channel with the MF and perform dynamic task configuration. The UE can predict the range of subtasks that can be performed within the max UE delay time based on the performance requirements of the subtasks and transmit a list of subtasks that can be processed within the given delay time, from the minimum to the maximum.

[0218] In step 24, the MF determines the number of cases of subtasks to be processed by the MF based on the list of received subtasks among all subtasks within the task, and allocates resources so as to satisfy the highest resource requirement among them.

[0219] In step 25, once resource allocation is complete, the MF can send an OK response to the terminal. If only some of the selected subtask cases can be satisfied, only the number of cases that can be satisfied can be responded to with a code indicating that it is partially OK in step 25. Upon receiving this code, the terminal can repeat steps 23-25 ​​to select and send only the cases that the MF can support, and after receiving an OK response, proceed to step 26.

[0220] In step 26, the terminal can determine a time corresponding to the max UE delay time from the start time of each multimedia input.

[0221] At step 27, the terminal can initiate processing for a subtask from the multimedia input.

[0222] In step 28, the terminal immediately transmits to the MF if all terminal subtasks set in the dynamic task are completed before the max UE delay time, and if the max UE delay arrives but the subtasks are not completed, the results of the subtasks completed so far can be transmitted to the MF.

[0223] In step 29, the terminal may signal key timing information to the MF along with the completed subtask identifier. Key timing information may include a frame start time, a completion target time, an E2E (UE to UE2) delay target time, and a terminal time required for the delayed completed subtask.

[0224] In step 30, the MF can identify and execute the subtask to be executed next from the subtask result of the received terminal and the notified subtask identifier, and can also complete the remaining subtasks to generate the result.

[0225] According to one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system may be provided. The method may include: determining a list including one or more subtasks associated with the terminal from among a plurality of subtasks included in a task; transmitting a message including the list to a network entity; receiving a response message from the network entity; performing subtask processing during a time interval; identifying at least one subtask completed during the time interval; and transmitting a message including result information to the network entity based on the at least one subtask.

[0226] According to one embodiment, the one or more sub-tasks may be determined based on the performance of the terminal and the time interval.

[0227] According to one embodiment, the method further comprises the step of determining a maximum terminal delay time, wherein the time interval may be an interval from a frame start time to a time at which the maximum terminal delay time arrives.

[0228] According to one embodiment, the response message may be received when allocation of resources associated with the network entity is completed.

[0229] According to one embodiment, the one or more sub-tasks include a first sub-task and a second sub-task, and when only the first sub-task is completed during the time interval, the result information may include execution result information for the first sub-task and identifier information for the first sub-task.

[0230] According to one embodiment, the one or more subtasks include a first subtask and a second subtask, and when both the first subtask and the second subtask are completed during the time interval, the result information may include execution result information for the first subtask and the second subtask and identifier information for the second subtask.

[0231] According to one embodiment, the message including the list further includes information about the task, and the message including the result information further includes time information, wherein the time information may include a frame start time and a completion target time.

[0232] According to one embodiment of the present disclosure, a method performed by a network entity in a wireless communication system may be provided. The method may include: receiving a message from a terminal, the message including a list including one or more subtasks associated with the terminal among a plurality of subtasks included in a task; allocating a resource based on the list; transmitting a response message to the terminal when the allocation of the resource is completed; receiving a message including result information from the terminal; and performing subtask processing based on the result information.

[0233] According to one embodiment, the one or more subtasks may include a first subtask and a second subtask, and the result information may include execution result information for the first subtask and identifier information for the first subtask.

[0234] According to one embodiment, the step of performing the sub-task processing may include the step of performing processing on at least one sub-task after the first sub-task among the plurality of sub-tasks based on the execution result information and the identifier information.

[0235] According to one embodiment, the one or more subtasks may include a first subtask and a second subtask, and the result information may include execution result information for the first subtask and the second subtask and identifier information for the second subtask.

[0236] According to one embodiment, the step of performing the sub-task processing may include the step of performing processing on at least one sub-task after the second sub-task among the plurality of sub-tasks based on the execution result information and the identifier information.

[0237] According to one embodiment, the message including the list further includes information about the task, and the message including the result information further includes time information, wherein the time information may include a frame start time and a completion target time.

[0238] According to one embodiment, the one or more subtasks are associated with the performance and time interval of the terminal, and the time interval may be an interval from the start of a frame to the time when the maximum terminal delay time arrives.

[0239] According to one embodiment of the present disclosure, a terminal may be provided in a wireless communication system. The terminal may include at least one transceiver; at least one processor communicatively coupled to the at least one transceiver; and at least one memory communicatively coupled to the at least one processor and storing instructions executable by the at least one processor, wherein the instructions may cause the terminal to determine a list including one or more subtasks associated with the terminal from among a plurality of subtasks included in a task, transmit a message including the list to a network entity, receive a response message from the network entity, perform subtask processing during a time interval, identify at least one subtask completed during the time interval, and transmit a message including result information to the network entity based on the at least one subtask.

[0240] FIG. 10 is a diagram showing the configuration of a terminal according to one embodiment of the present disclosure.

[0241] As illustrated in FIG. 10, the terminal of the present disclosure may include a transceiver (1010), a memory (1020), and a processor (1030). The processor (1030), the transceiver (1010), and the memory (1020) of the terminal 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. In addition, the processor (1030), the transceiver (1010), and the memory (1020) may be implemented in the form of a single chip.

[0242] The transceiver (1010) is a general term for the terminal's receiver and transmitter, and can transmit and receive signals with a base station or network entity. The signals transmitted and received with the base station may include control information and data. To this end, the transceiver (1010) 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 down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver (1010), and the components of the transceiver (1010) are not limited to the RF transmitter and RF receiver.

[0243] Additionally, the transceiver (1010) may include a wired or wireless transceiver and may include various configurations for transmitting and receiving signals.

[0244] In addition, the transceiver (1010) can receive a signal through a wired or wireless channel and output it to the processor (1030), and transmit the signal output from the processor (1030) through the wired or wireless channel.

[0245] Additionally, the transceiver (1010) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a network entity via a wired or wireless network.

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

[0247] The processor (1030) can control a series of processes so that the terminal can operate according to the embodiments of the present disclosure described above. The processor (1030) may include at least one processor. For example, the processor (1030) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.

[0248] FIG. 11 is a diagram showing the configuration of a base station according to one embodiment of the present disclosure.

[0249] As illustrated in FIG. 11, the base station of the present disclosure may include a transceiver (1110), a memory (1120), and a processor (1130). The processor (1130), the transceiver (1110), and the memory (1120) of the base station may operate according to the communication method of the base station described above. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the processor (1130), the transceiver (1110), and the memory (1120) may be implemented in the form of a single chip.

[0250] The transceiver (1110) is a general term for the receiving unit and the transmitting unit of the base station, and can transmit and receive signals with a terminal or another base station. At this time, the transmitted and received signals may include control information and data. To this end, the transceiver (1110) 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 (1110), and the components of the transceiver (1110) are not limited to the RF transmitter and RF receiver. The transceiver (1110) may include wired and wireless transceivers, and may include various configurations for transmitting and receiving signals.

[0251] Additionally, the transceiver (1110) can receive a signal through a communication channel (e.g., a wireless channel) and output the signal to the processor (1130), and transmit the signal output from the processor (1130) through the communication channel.

[0252] In addition, the transceiver (1110) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a terminal or network entity via a wired or wireless network.

[0253] The memory (1120) can store programs and data required for the operation of the base station. In addition, the memory (1120) can store control information or data included in signals acquired from the base station. The memory (1120) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD.

[0254] The processor (1130) may control a series of processes so that the base station can operate according to the embodiments of the present disclosure described above. The processor (1130) may include at least one processor. 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.

[0255] Figure 12 is a diagram illustrating the configuration of a network entity according to the present disclosure. The network entity of the present invention is a concept that includes a network function depending on the system implementation.

[0256] As illustrated in FIG. 12, the network entity of the present disclosure may include a transceiver (1200), a memory (1210), and a processor (1220). The processor (1220), the transceiver (1200), and the memory (1210) of the network entity may operate according to the communication method of the network entity described above. However, the components of the network entity are not limited to the examples described above. For example, the network entity may include more or fewer components than the components described above. In addition, the processor (1220), the transceiver (1200), and the memory (1210) may be implemented in the form of a single chip. In addition, the processor (920) may include at least one processor.

[0257] The transceiver (1200) is a general term for the receiving unit and transmitting unit of a network entity, and can transmit and receive signals with a base station. The signals transmitted and received with the base station may include control information and data. To this end, the transceiver (1200) 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-converts the received signal. However, this is only one embodiment of the transceiver (1200), and the components of the transceiver (1200) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1200) may transmit and receive signals with other network entities.

[0258] In addition, the transceiver (1200) can receive a signal through a wireless channel and output it to the processor (1220), and transmit the signal output from the processor (1220) through the wireless channel.

[0259] The memory (1210) can store programs and data required for the operation of the network entity. In addition, the memory (1210) can store control information or data included in signals acquired from the network entity. The memory (1210) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD.

[0260] The processor (1220) may control a series of processes so that a network entity can operate according to the embodiments of the present disclosure described above. For example, the processor (1220) may receive control signals and data signals through the transceiver (1200) and process the received control signals and data signals. Furthermore, the processor (1220) may transmit the processed control signals and data signals through the transceiver (1200).

[0261] Additionally, the transceiver (1200), memory (1210), and processor (1220) may be electrically connected. Furthermore, the operations of a network entity may be realized by providing a memory device storing the corresponding program code in any component within the network entity.

[0262] 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.

[0263] 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 the embodiments described in the claims or specification of the present disclosure.

[0264] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they 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.

[0265] Additionally, the program may be stored in 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 performing 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 performing an embodiment of the present disclosure.

[0266] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural form, 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 the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0267] While the detailed description of the present disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the claims described below but also by equivalents thereof. In other words, it will be apparent to those skilled in the art to which the present disclosure pertains that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the respective embodiments may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate a base station and a terminal. In addition, although the above embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above embodiments may be implemented in other systems such as LTE, LTE-A, and LTE-A-Pro systems.

Claims

1. In a method performed by a terminal in a wireless communication system, A step of determining a list including one or more subtasks associated with the terminal among a plurality of subtasks included in a task; A step of transmitting a message including the above list to a network entity; A step of receiving a response message from the above network entity; A step of performing subtask processing during a time interval; identifying at least one subtask completed during the above time interval; and A method comprising the step of transmitting a message including result information to the network entity based on at least one of the subtasks.

2. A method according to claim 1, wherein the one or more sub-tasks are determined based on the performance of the terminal and the time period.

3. In the first paragraph, further comprising a step of determining the maximum terminal delay time, The above time interval is a method in which the above time interval is an interval from the start of the frame to the time when the above maximum terminal delay time arrives.

4. A method according to claim 1, wherein the response message is received when allocation of resources associated with the network entity is completed.

5. In the first paragraph, the one or more subtasks include a first subtask and a second subtask, A method in which, if only the first sub-task is completed during the time interval, the result information includes execution result information for the first sub-task and identifier information for the first sub-task.

6. In the first paragraph, the one or more subtasks include a first subtask and a second subtask, A method wherein, when both the first subtask and the second subtask are completed during the time interval, the result information includes execution result information for the first subtask and the second subtask and identifier information for the second subtask.

7. In the first paragraph, the message including the list further includes information about the task, A method wherein the message including the result information further includes time information, wherein the time information includes a frame start time and a completion target time.

8. In a method performed by a network entity in a wireless communication system, A step of receiving a message from a terminal, the message including a list including one or more subtasks associated with the terminal among a plurality of subtasks included in the task; A step of allocating resources based on the above list; When the allocation of the above resources is completed, a step of transmitting a response message to the terminal; A step of receiving a message including result information from the terminal; and A method comprising a step of performing sub-task processing based on the above result information, 9. In the 8th paragraph, the one or more subtasks include a first subtask and a second subtask, A method wherein the above result information includes execution result information for the first subtask and identifier information for the first subtask.

10. In the 9th paragraph, the step of performing the subtask processing is A method comprising a step of performing processing on at least one sub-task after the first sub-task among the plurality of sub-tasks based on the execution result information and the identifier information.

11. In the 8th paragraph, the one or more subtasks include a first subtask and a second subtask, A method wherein the result information includes execution result information for the first subtask and the second subtask and identifier information for the second subtask.

12. In the 11th paragraph, the step of performing the subtask processing is A method comprising a step of performing processing on at least one sub-task after the second sub-task among the plurality of sub-tasks based on the execution result information and the identifier information.

13. In the 8th paragraph, the message including the list further includes information about the task, A method wherein the message including the result information further includes time information, wherein the time information includes a frame start time and a completion target time.

14. In the 8th paragraph, the one or more sub-tasks are associated with the performance and time interval of the terminal, The above time interval is a method in which the interval is from the start of the frame to the time when the maximum terminal delay time arrives.

15. In a wireless communication system, at a terminal, At least one transmitter / receiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory coupled to the at least one processor so as to be communicatively connected and storing instructions executable by the at least one processor, The above commands are used by the terminal Determine a list including one or more subtasks associated with the terminal among multiple subtasks included in the task, Send a message containing the above list to the network entity, Receive a response message from the above network entity, Perform subtask processing during a time interval, Identify at least one subtask that was completed during the above time interval, A terminal configured to transmit a message including result information to the network entity based on at least one of the sub-tasks.

Images