Method and apparatus for low latency media streaming in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method performed by a terminal in a wireless communication system, according to embodiments of the present disclosure, comprises the steps of: transmitting, to a data network (DN) entity, a dynamic policy configuration request for a downlink streaming service on the basis of a policy template; and identifying the result of the dynamic policy configuration request, wherein the policy template can include information about low latency low loss scalable throughput (L4S) support.

Description

Method and device for low-latency media streaming in wireless communication systems

[0001] The present disclosure relates to a wireless communication system, and to a method and apparatus for supporting low-latency media streams.

[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 discloses a method for supporting low-latency media streaming in a wireless communication system.

[0009] A method performed by a terminal of a wireless communication system according to embodiments of the present disclosure for solving the above-described problem includes a step of transmitting a dynamic policy setting request for a downlink streaming service based on a policy template to a data network (DN) entity and a step of identifying a result of the dynamic policy setting request, wherein the policy template may include information on L4S (Low Latency Low Loss Scalable Throughput) support.

[0010] According to embodiments of the present disclosure, a method and apparatus for a low-latency media streaming service supporting L4S in a wireless communication system can be provided.

[0011] FIG. 1 is a conceptual diagram illustrating a 5G system architecture (5G system, 5GS) for a low-latency media streaming service in a wireless communication system according to various embodiments of the present disclosure.

[0012] FIG. 2 is a conceptual diagram illustrating a generalized media delivery architecture for providing media services in a wireless communication system according to various embodiments of the present disclosure.

[0013] FIG. 3 is a conceptual diagram illustrating ECN code points according to various embodiments of the present disclosure.

[0014] FIG. 4 is a conceptual diagram illustrating an L4S structure according to various embodiments of the present disclosure.

[0015] FIG. 5 is a conceptual diagram illustrating a media transmission structure based on a 5G system structure to which L4S is applied according to various embodiments of the present disclosure.

[0016] FIG. 6 is a diagram illustrating an example of a downlink streaming service provision procedure supporting L4S according to various embodiments of the present disclosure.

[0017] FIG. 7 illustrates the structure of a terminal according to various embodiments of the present disclosure.

[0018] FIG. 8 illustrates the structure of a network entity according to various embodiments of the present disclosure.

[0019] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Furthermore, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on their functions in the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of the present disclosure.

[0020] 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 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 solely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the disclosure.

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

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

[0023] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0024] In describing the present disclosure below, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the gist of the present disclosure, the detailed description will be omitted.

[0025] For the same reason, some components in the attached drawings are exaggerated, omitted or schematically illustrated.

[0026] It will be appreciated that each block of the flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, such that the instructions, when executed by the processor of the computer or other programmable data processing equipment, create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to perform the functions in a specific manner, such that the instructions stored in the computer-available or computer-readable memory can produce an article of manufacture that includes instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions can also be installed on a computer or other programmable data processing device, a series of operations are 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 operations for performing the functions described in the flowchart block(s) can also provide operations for performing the functions described in the flowchart block(s).

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

[0028] In the present disclosure, a 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 wireless access unit, a base station controller, or a node on a network. 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 a communication function. Although 5G (NR) or a 5G (NR) system may be described below as an example, embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. In addition, the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

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

[0030] The present disclosure relates to a method and device for supporting low-latency media streaming in a mobile communication system. For example, the present disclosure relates to a method and device for supporting low-latency media streaming, such as XR services, in a mobile communication system supporting L4S (Low Latency, Low Loss, Scalable Throughput) functionality.

[0031] XR refers to a technology that provides interaction between wearable device users and machines using content generated by computing technology in an environment where the real and virtual are combined. XR creates an expanded reality through the individual or combined use of virtual reality (VR) and augmented reality (AR) technologies. XR is expected to be applied to various fields such as education, healthcare, and manufacturing. To realize XR, high-performance computing power and graphics processing performance are crucial for displaying large-capacity, real-time 3D images. Display technology must also advance, and technologies such as 5G mobile communications that efficiently transmit large amounts of data with ultra-low latency are also prerequisites.

[0032] The L4S architecture is a packet processing architecture for application services provided over the Internet, and is characterized by providing low latency, low loss, and scalable throughput control. The main purpose of L4S is to minimize packet latency of devices located along the packet transmission path on the Internet. The L4S architecture can be composed of hosts, networks, and protocols. L4S hosts are characterized by the use of scalable congestion control algorithms, and L4S networks are characterized by managing L4S packets and general Internet packets (classic packets) using separate queues. The L4S protocol uses identifiers that allow hosts and networks to distinguish between L4S packets and classic packets, and is supported by a modified form of Explicit Congestion Notification (ECN).

[0033] L4S hosts that provide media streaming over the general Internet cannot determine whether the L4S network is available before service initiation. Therefore, monitoring and verification procedures must be performed for a certain period of time after service initiation to determine whether media streaming packets are transmitted over the L4S network. This can cause initial performance instability, so a procedure is required before service initiation to verify that the L4S hosts and L4S network that comprise the LS4 architecture support the L4S protocol.

[0034] According to various embodiments of the present disclosure, a low-latency media streaming structure including L4S can be utilized to smoothly provide delay-sensitive services such as XR services.

[0035] A wireless communication system according to various embodiments of the present disclosure may be, for example, a 5G system (5GS: 5G System). The 5G system may be composed of a 5G radio access network (NG-RAN: Next Generation Radio Access Network) and a 5G core network (5GC: 5G Core Network). 5GS interworks with existing LTE and may also be connected to non-3GPP wireless access technologies such as Wi-Fi. 5GC is located between the NG-RAN and an external packet data network (PDN: Public Data Network) and may provide various types of data services, including voice, to users. The control plane components of 5GC may be regarded as virtualized network functions (VNFs), and communication between VNFs may be regarded as a RESTful-based API exchange, where one VNF provides a service to other VNFs. The API-based communication interface between VNFs is called a Service Based Interface (SBI).

[0036] FIG. 1 is a conceptual diagram illustrating a 5G system structure (5G system, 5GS) for XR service in a wireless communication system according to various embodiments of the present disclosure.

[0037] Referring to FIG. 1, 5GS may include a user equipment (UE) (101), an NG-RAN (102) including a base station, a user plane function (UPF) device (103), an access and mobility management function (AMF) device (111), a session management function (SMF) device (112), a policy control function (PCF) device (113), a network exposure function (NEF) device (114), an NF repository function (NRF) device (115), an authentication server function (AUSF) device (116), a unified data management (UDM) device (117), a media application function (Media AF) device (121), and a media application server (Media AS) device (122). Of course, 5GS is not limited to the examples and may include fewer or more configurations than those illustrated in FIG. 1. Furthermore, each device may be referred to as a network entity, a network function, or a network function apparatus.

[0038] Referring to Figure 1, each network function (NF) of 5GS will be described as a "network entity" or "network function" itself. However, those skilled in the art will understand that an NF and / or an NF device may be implemented in one or more specific servers, or two or more NFs performing the same operation may be implemented in a single server.

[0039] Furthermore, according to the present disclosure, one NF or two or more NFs may be implemented in the form of a network slice, depending on the situation. A network slice may be created based on a specific purpose. For example, a network slice may be configured for a group of subscribers to provide the same type of service, such as a maximum transmission rate and data usage, or a guaranteed minimum transmission rate, to a specific group of subscribers. In addition, a network slice may be implemented for various other purposes. Since network slices are well known to those skilled in the art, a description thereof will be omitted.

[0040] Referring to Fig. 1, Fig. 1 illustrates interfaces between each node. A Uu interface may be used between a UE (101) and an NG-RAN (102), an N2 interface may be used between an NG-RAN (102) and an AMF (111), an N3 interface may be used between an NG-RAN (102) and an UPF (103), an N4 interface may be used between an SMF (112) and an UPF (103), and an N6 interface may be used between the UPF (103) and a Media AF (121) and a Media AS (122) located in a DN (Data Network). Since the above-described interfaces are defined in the 3GPP standard, their descriptions are omitted. The interfaces between the Media AF (121) and the Media AS (122) and the UE will be described in the media architecture described later.

[0041] FIG. 2 is a conceptual diagram illustrating a generalized media delivery architecture for providing media services in a wireless communication system according to various embodiments of the present disclosure.

[0042] Referring to Figure 2, the main functional elements of the conceptualized media transmission structure are as follows:

[0043] - Media AF (260): Application Function for providing media services

[0044] - Media AS (270): Application Server for media transmission

[0045] - Media Client (210): A UE internal function for media transmission. The following sub-functions may be included as logical functions.

[0046] ■ Media Session Handler (211): Internal function of UE (200) that communicates with Media AF (260) to establish and control media transmission session.

[0047] ■ Media Access Function (212): A function within the UE (200) that communicates with the Media AS (270) to access and transmit media content. The media access function may have detailed functions such as a media transmission protocol, a media codec, and a metadata processor, for example.

[0048] Although FIG. 2 illustrates that the media session handler (211) and the media access function (212) provide APIs to each other through the M11 interface and provide APIs to the media-aware application (220) through the M6 ​​and M7 interfaces, respectively, depending on the implementation selection, the functions of the above-described element functions may be provided by the media-aware application (220) or other components of the UE (200), in which case the M11, M6 and M7 interfaces may not exist.

[0049] - Media-aware Application (220): An application running on a UE (200) that can utilize at least one of the APIs (Application Program Interfaces) provided by a media session handler (211) or a media access function (212) for media transmission.

[0050] Referring to FIG. 2, components of the conceptualized media transmission structure described above can communicate with each other using the following interfaces.

[0051] - M1: Interface between media application provider (280) and Media AF (260), can be used for media transmission service provisioning.

[0052] - M2: An interface between a media application provider (280) and Media AS (270), which can be used to provide media data to or receive media data from Media AS (270).

[0053] - M3: Interface between Media AF (260) and Media AS (270), and can be used for configuration of Media AS (270) or media session processing related to media transmission.

[0054] - M4: An interface between the media access function (212) of the UE and the Media AS (270), and the media access function (212) can be used to receive media data from the Media AS (270) or transmit media data to the Media AS (270).

[0055] - M5: Interface between UE's media session handler (211) and Media AF (260), which can be used for media session processing related to media transmission.

[0056] - M6: An interface between a media-aware application (220) and a media session handler (211), which can be used to set up the media session handler (211).

[0057] - M7: An interface between a media recognition application (220) and a media access function (212), and can be used to control the media access function (212).

[0058] - M8: An interface between the media awareness application (220) of the UE and the media application provider (280), and can be used to control media application service logic.

[0059] - M9: Interface between the first and second instances of Media AF (260), and can be used for linking between Media AF instances.

[0060] - M10: Interface between the first and second instances of Media AS (270), which can be used for media relay and processing between Media AS instances.

[0061] - M11: An interface between a media session handler (211) and a media access function (212), and can be used to set up a media session handler (211) or a media access function (212).

[0062] Referring to FIG. 2, the above-described Media AF (260) and Media AS (270) are functions located in the data network (250), and the Media AF (260) and Media AS (270) can communicate with the UE (200) through the N6 interface defined in 5GS. A function located in an operator's external network (External DN) (for example, Media AF (260)) can communicate with a 5G network function through the NEF (114) using the N33 interface, and a function located in an operator's trusted network (Trusted DN) (for example, Media AF (260)) can directly communicate with a 5G network function. Referring to FIG. 2, the Media AF (260) located in the operator's trusted network can communicate with the PCF (113) using the N5 interface. The communication between the Media AF (260) and the NEF (114) or the PCF (113) may be a network service consumption process using an API provided by the NEF (114) or the PCF (113). For example, the Media AF (260) may request traffic processing policy settings, including QoS (Quality of Service) parameters, for a media transmission session between the media access function (212) of the UE (200) and the Media AS (270), using the Nnef_AFSessionWithQoS service provided by the NEF (114) or the Npcf_PolicyAuthoriztion service provided by the PCF (113). As another example, the Media AF (260) may subscribe to a network event notification service and be notified when a related situation occurs in the network.The above event notification may be delivered directly to the Media AF (260) from a network function associated with the event (e.g., PCF (113) or UPF (103)) or via the NEF (114).

[0063] Media services according to various embodiments of the present disclosure may include the following two main scenarios.

[0064] - Downlink Streaming: The network provides media and the UE plays the role of consuming the media.

[0065] - Uplink Streaming: The UE provides media and the network consumes the media.

[0066] The functions and interfaces of the conceptualized media transmission architecture illustrated in FIG. 2 may provide different functions for downlink streaming and uplink streaming. For convenience of explanation, the functions and interfaces for downlink streaming are denoted by the suffix “d,” and the functions and interfaces for uplink streaming are denoted by the suffix “u.”

[0067] According to various embodiments of the present disclosure, the L4S architecture is a packet processing architecture for application services provided through the Internet, and is characterized by providing low latency, low loss, and scalable throughput control. The L4S architecture may include a protocol, a network, and a host. The L4S host is characterized by using a scalable congestion control algorithm, and the L4S network is characterized by managing L4S packets and general Internet packets (classic packets) using separate queues. The L4S protocol uses an identifier that allows the L4S host and the L4S network to distinguish between L4S packets and classic packets, and the L4S protocol is supported in the form of a modified form of Explicit Congestion Notification (ECN).

[0068] FIG. 3 is a conceptual diagram illustrating ECN code points according to various embodiments of the present disclosure.

[0069] Referring to FIG. 3, the last two bits of the traffic class field (310) included in the IP packet header (300) can be used as an ECN field (320). More specifically, the ECN code points, which are candidate values ​​that the ECN field can have, can be defined as follows.

[0070] - 00: Not ECN-Capable Transport, Not-ECT

[0071] - 01: ECN Capable Transport(1), ECT(1)

[0072] - 10: ECN Capable Transport(0), ECT(0)

[0073] - 11: Congestion Experienced, CE

[0074] When both the transmitting host and the receiving host participating in the communication support ECN, the transmitting host transmits an IP packet by setting the ECN field of the IP packet header to ECT(0) ('10') or ECT(1) ('01'). When the network located between the transmitting host and the receiving host supports ECN, the network equipment changes (marks) the ECN field of the IP packet header (300) to CE ('11') and transmits the packet instead of dropping it when congestion occurs. The receiving host that receives the packet in which the ECN field is set to CE ('11') can recognize that congestion has occurred in the network and can notify the transmitting host that congestion has occurred in the network. The difference between the L4S protocol according to the present disclosure and the conventional ECN protocol can be expressed as an example in the following [Table 1].

[0075] Setting the ECN field of the sending host Setting the CE field of the network Criteria for setting the ECN field of the network Congestion control technique of the sending host Conventional ECN ECT (0) Network congestion situation equivalent to a drop Congestion control by considering CE packets as drops L4SECT (1) Light network congestion situation Preemptive congestion control considering the frequency / probability of CE packets

[0076] FIG. 4 is a conceptual diagram illustrating an L4S structure according to various embodiments of the present disclosure.

[0077] Referring to FIG. 4, the L4S transmitter (410) transmits an IP packet to the L4S receiver (430) via the L4S network (420). The ECN field of the IP packet transmitted by the L4S transmitter (410) may be set to ECT (1). At this time, the classic transmitter (411) may also transmit an IP packet to the classic receiver (not shown) via the L4S network (420), and the ECN field of the IP packet transmitted by the classic transmitter (411) may be set to ECT (0) or Not-ECT. The L4S network (420) that receives the packet transmitted by the L4S transmitter (410) or the classic transmitter (411) may change the ECN field to CE (Congestion Experienced) depending on the network congestion level to mark network congestion or drop a specific packet. The above L4S network (420) can operate separate processing pipelines for L4S traffic and classic traffic. For example, referring to FIG. 4, the L4S network (420) can classify L4S traffic (ECT(1)) and classic traffic (ECT(0) or Not-ECT) based on the ECN field value using an IP-ECN classifier (421). L4S packets classified based on the ECN field value are assigned to an L4S traffic queue (422), and the L4S network (420) performs marking (423) to change the ECN field value to CE based on the occupancy rate of the L4S traffic queue (422). Except for L4S packets, the remaining classic traffic is allocated to a separate classic traffic queue (424), and the L4S network (420) performs marking (in the case of ECT(0)) or dropping (ECT(0) or Not-ECT) by changing the ECN field value to CE according to the occupancy rate of the classic traffic queue (424) (425). Thereafter, non-dropped packets are delivered to the scheduler (426) and ultimately transmitted to the L4S receiving device (430).

[0078] The L4S receiving device (430) can check the ECN field value of the received IP packet, and if the ECN field value is set to CE, it can recognize that the network is congested. In addition, the L4S receiving device (430) can transmit information about the network congestion situation to the L4S transmitting device (410) using L4S feedback. The L4S transmitting device (410) that obtains information about the network congestion situation from the L4S receiving device (430) can operate a congestion control algorithm based on the information about the network congestion situation. The L4S feedback may vary depending on the type of transmission protocol that transmits the media content. For example, when the TCP protocol is used, an Ack frame can be used as L4S feedback, when the RTP protocol is used, an RTCP feedback message can be used as L4S feedback, and when the QUIC protocol is used, an ECN count block of the Ack frame can be used as L4S feedback.

[0079] FIG. 5 is a conceptual diagram illustrating a media transmission structure based on a 5G system architecture to which L4S is applied according to various embodiments of the present disclosure. Referring to FIG. 5 , a 5G-L4S network (500) performs the role of the L4S network (420) of FIG. 4 and can notify the Media AF (260) of L4S network-related information. For example, the 5G-L4S network can perform at least one of the following functions:

[0080] - Perform network congestion marking in NG-RAN (102) or UPF (103).

[0081] - When setting media session parameters according to the request of Media AF (260), specify whether L4S is supported.

[0082] - When L4S support changes due to changes in network nodes such as NG-RAN (102) or UPF (103), the change in L4S support is notified to Media AF (260).

[0083] - Provides L4S-related parameters such as the rate of congested packets to Media AF (260).

[0084] Referring to FIG. 5, the UE (200) (or media client (210)) and the Media AS (270) can each perform the role of an L4S transmitter (430) or an L4S receiver (410). For example, in the case of a downlink streaming service, the Media AS (270) can perform the role of an L4S transmitter (410), and the UE (200) (or media client (210)) can perform the role of an L4S receiver (430). As another example, in the case of an uplink streaming service, the Media AS (270) can perform the role of an L4S receiver (430), and the UE (200) (or media client (210)) can perform the role of an L4S transmitter (410).

[0085] Referring to FIG. 5, Media AF (260) receives media transmission service configuration information including L4S related parameters from a media application provider (280) through an M1 interface, and can configure at least one of a media client (210) and a Media AS (270) based on the media transmission service configuration information, and can request a PCF (113) or NEF (114) to configure a traffic processing policy including L4S related parameters for a media transmission session between the media client (210) and the Media AS (270).

[0086] FIG. 6 is a diagram illustrating an example of a procedure for providing a downlink streaming service supporting L4S according to various embodiments of the present disclosure. Referring to FIG. 6, a downlink streaming service supporting L4S can be provided to a user through the following procedure.

[0087] 1. Service Provisioning: The 5GMSd application provider (280) can establish a provisioning session with the 5GMSd AF (260) and configure 5GMSd functions for downlink streaming services. The 5GMSd functions may include dynamic policy invocation, and the provisioning information for configuring the dynamic policy invocation function may include L4S provisioning information.

[0088] 2. AS configuration: 5GMSd AF (260) can set up 5GMSd AS (270) based on provisioning information. L4S AS setting information can be provided when setting up the 5GMSd AS (270).

[0089] 3. 5GMS Ingest: The 5GMSd application provider (280) can supply / transmit content for a downlink streaming service to the 5GMSd AS (270). The connection information and media transmission protocol setting information of the 5GMSd AS (270) for the content supply / transmission can be provided to the 5GMSd application provider (280) by the 5GMSd AF (260) as a result of provisioning.

[0090] 4. Service Announcement: The 5GMSd application provider (280) can transmit service announcement information to the 5GMSd aware application (220) running on the user equipment (UE). The service announcement information can include service access information or a path through which the 5GMSd client (210) running on the user equipment can obtain service access information. The service access information can include a provisioning session identifier associated with the 5GMSd aware application (220) and configuration information for a dynamic policy request.

[0091] 5. Start Media Playback: The 5GMSd cognitive application (220) can request the 5GMSd client (210) to acquire and play content selected by the user. At this time, service access information or a path through which the 5GMSd client (210) can acquire service access information can be transmitted.

[0092] 6. Media Session Configuration: If the 5GMSd client (210) knows the path through which service access information can be obtained, the 5GMSd client (210) obtains service access information using the path through which service access information can be obtained.

[0093] 7. Establish Transport Session: A media transport session can be established for acquiring media content. At this time, negotiations regarding whether to use L4S can take place between the 5GMSd AS (270) and the 5GMSd client (210) according to the media transport protocol.

[0094] 8. Dynamic policy invocation: The 5GMSd client (210) may request the 5GMSd AF (260) to set a dynamic policy to be applied to a media transmission session. The dynamic policy setting request may include a provisioning session identifier, a service data flow description, and a policy template identifier. L4S dynamic policy information may be included in at least one of the service data flow description and the policy template.

[0095] 9. Media traffic policy request: 5GMSd AF (260) can request a media transmission traffic processing policy from PCF (113) or NEF (114). The media transmission traffic processing policy can include at least one of L4S support and L4S-related event notification service subscription.

[0096] 10. Query Stats: The 5GMSd client (210) can check the dynamic policy setting results by inquiring with the 5GMSd AF (260). The response of the 5GMSd AF (260) to the inquiry of the 5GMSd client (210) may include information on the dynamic policy setting status (e.g., Accepted, Rejected, etc.) and instructions for the dynamic policy (e.g., bit rate, L4S support, etc.).

[0097] 11. Request Media Contents: The 5GMSd client (210) can reset the internal parameters of the 5GMSd client according to the response of the 5GMSd AF (260) and request transmission of media contents to the 5GMSd AS (270).

[0098] 12. Media Contents / L4S Feedback: The 5GMSd AS (260) can transmit media data requested by the 5GMSd client (210) to the 5GMSd client (210) using a media transfer protocol. The 5GMSd client (210) that receives the media data can inspect the ECN field of the received IP packet and transmit the inspection result of the ECN field of the IP packet to the 5GMSd AS (260) as L4S feedback. For example, the L4S feedback can mean the ratio of packets marked as CE (congestion experienced) among the IP packets received within a specific time or packet sequence number range. The specific format of the L4S feedback can vary depending on the media transfer protocol used. The 5GMSd AS (260) can operate a congestion control algorithm for media data transmission according to the contents of the received L4S feedback.

[0099] If the 5GMSd application provider (280) uses a media server that it operates on its own rather than a media server operated by the 5GMSd AS (270), the above-described operations 2. and 3. may be performed as internal operations of the 5GMSd application provider (280). The above-described operation 10. Query Status may be performed as a response or subsequent operation of operation 8. Dynamic policy invocation operation rather than as a separate operation depending on the API between the 5GMSd client (210) and the 5GMSd AF (260).

[0100] Although the above-described embodiment describes that the 5GMSd client (210) requests dynamic policy setting from the 5GMSd AF (260), the 5GMSd AS (270) may also request dynamic policy setting based on the policy of the mobile communication service provider or the request of the 5GMSd application provider (280). In addition, the 5GMSd AS (270) may request L4S application from the 5GMSd AF (260) separately from the dynamic policy request, and the result may be notified to the 5GMSd client.

[0101] The provisioning procedure for a media streaming service according to various embodiments of the present disclosure may include creating, acquiring, and updating a Provision Session resource using a Rest API or the like. [Table 2] below is an example of a Provisioning Session resource according to an embodiment of the present disclosure.

[0102] Property name Type CardinalityDescription provisioningSessionId ResourceId 1..1 Unique identifier assigned to the provisioning session provisioningSessionType ProvisioningSessionType 1..1 Type of provisioning session, which can indicate downlink streaming or uplink streaming externalServiceId String 1..1 Identifier representing the service associated with the provisioning session aspid AspId 0..1 Identifier representing the application service provider associated with the provisioning session appId ApplicationId 1..1 Identifier representing the application associated with the provisioning session policyTemplateId sarrya{ResourceId} 0..1 Policy template identifiers associated with the provisioning session edgeResourceConfigurationId sarray{ResourceId} Edge server configuration identifiers associated with the provisioning session protocolDescription ProtocolDescription 0..1 Protocol-related information associated with the provisioning session...

[0103] A Provisioning Session Resource according to various embodiments of the present disclosure may include L4S provisioning information. The L4S provisioning information may be included in the protocolDescription property and applied to the entire provisioning session, or may be included in a resource referenced by the Provisioning Session Resource and applied only to specific settings. For example, the L4S provisioning information may be configured for each policy template or for each edge server configuration.

[0104] [Table 3] below is an example of a policy template resource according to various embodiments of the present disclosure.

[0105] Property nameTypeCardinalityDescriptionpolicyTemplateIdResourceId1..1Identifier of the policy template. It has a unique value within the provisioning session.statestring1..1A property that indicates the processing status of the policy template. For example, it can have values ​​such as READY or PENDDING.stateReasonProblemDetails1..1Detailed information about the processing status of the policy templateexternalReferencestringAn additional identifier of the policy template. It has a unique value within the provisioning session. It can be referenced in metadata related to media transmission. (For example, HD_Premium, L4S)applicationSessionContextarray(object)0..1Information about the context of the application session, which can include a network slice identifier or a data network identifier.qoSSpecificationQoSSpecification0..1QoS information to be applied to the media transmission session associated with this policy template. May contain information such as bit rate or packet loss rate. chargingSpecificationCharginSpecification0..1Charging information to be applied to the media transfer session associated with this policy template. protocolDescriptionProtocolDescription0..1Information about the protocol associated with the provisioning session...

[0106] The qoSSpecification attribute or protocolDescription attribute of the Policy Template resource according to various embodiments of the present disclosure may include L4S provisioning information.

[0107] L4S provisioning information according to various embodiments of the present disclosure may include at least one of the following information:

[0108] - l4sSupport: Whether L4S is supported. When included in the protocolDescription property, it can indicate whether all media traffic associated with the provisioning session is supported. When included in a resource referenced by the Provisioning Session Resource, it can indicate whether media traffic associated with that resource is supported.

[0109] - fallbackPolicy: Policy for cases where L4S is not supported. It can have values ​​such as mandatory support, optional support, etc. If the fallbackPolicy included in the protocolDescription attribute has a value of mandatory support, Media AF must establish a traffic transmission path to an NF (e.g., UPF, RAN) that supports L4S. If this is not satisfied (i.e., if the traffic transmission path to an NF (e.g., UPF, RAN) that supports L4S is not established), Media AF may not provide the service. The value of the fallbackPolicy attribute included in the resource referenced by the Provisioning Session Resource can be used as a criterion for selecting a specific policy template or configuration information.

[0110] - transportProtocol: Identifier(s) of the media transport protocol supporting L4S. Examples include TCP, RTP over UDP, QUIC, and SCTP. Additional attributes for L4S feedback may be included depending on the transport protocol. For example, when RTP over UDP is used, the identifier of the RTCP feedback message containing L4S feedback may be included.

[0111] - congestionCtrlScheme: Identifier of the congestion control algorithm to be used by the L4S transmitter. For example, Prague.

[0112] - congestionInfoRequired: Whether to subscribe to congestion information provided by 5G NF such as UPF.

[0113] Media AF according to various embodiments of the present disclosure can configure Media AS based on provisioning information including L4S provisioning information. The Media AS configuration procedure can include the process of creating, obtaining, and updating an AsResouceConfiguration resource using Rest-API, etc. The AsResouceConfiguration resource can include L4S AS configuration information including at least one of the following information:

[0114] - l4sSupport: Whether L4S is supported.

[0115] - fallbackPolicy: Policy for when L4S is not supported. It can have values ​​such as required support, optional support, etc. When L4S support is required, the value of the fallbackPolicy attribute can be used as a criterion for selecting a specific Media AS.

[0116] - transportProtocol: Identifier(s) of the media transport protocol supporting L4S. Examples include TCP, RTP over UDP, QUIC, and SCTP. Additional attributes for L4S feedback may be included depending on the transport protocol. For example, if RTP over UDP is used, the identifier of the RTCP feedback message containing L4S feedback may be included.

[0117] congestionCtrlScheme: Identifier of the congestion control algorithm to be used by the L4S transmitter. For example, Prague.

[0118] congestionInfoRequired: Whether to subscribe to congestion information provided by 5G NFs such as UPF.

[0119] The L4S dynamic policy request procedure of a media streaming service according to various embodiments of the present disclosure may include a process of creating, obtaining, and updating a Dynamic Policy resource using Rest-API, etc. [Table 4] below is an example of a Dynamic Policy resource according to an embodiment of the present disclosure.

[0120] Property nameTypeCardinalityDescriptiondynamicPolicyIdResourceId1..1 Unique identifier of this dynamic policyprovisioningSessionIdResourceId1..1 Unique identifier of the associated provisioning sessionsessionIdMediaDeliverySessionId1..1 Unique identifier of the associated media delivery sessionpolicyTemplateIdResourceId1..1 Identifier of the policy template to be applied to the application data flowserviceDataFlowDescriptionsarray{ServiceDataFlow Description}1..1 Information about the Service Data Flow to which this dynamic policy will be appliedmediaTypeMediaType0..1 The media format transported by the application flow described in serviceDataFlowDescriptionsqoSSpecificationM5QoSSpecification0..1 The QoS requirements of this dynamic policy. It may include information such as bit rate, packet delay time, and packet loss rate. qoSEnforcementboolean0..1An indicator indicating whether the QoS requirements described in qoSSpecification are satisfied in the 5G system. protocolDescriptionProtocolDescription0..1Protocol-related information of the application flow described in serviceDataFlowDescriptions...

[0121] A Dynamic Policy resource according to various embodiments of the present disclosure may directly include L4S dynamic policy information, or may include information (e.g., a resource identifier) ​​on another resource including L4S dynamic policy information. A Dynamic Policy resource according to one embodiment of the present disclosure may include an identifier of a policy template resource including L4S provisioning information as a policyTemplateId attribute, wherein the L4S provisioning information may be regarded as L4S dynamic policy information. A Dynamic Policy resource according to one embodiment of the present disclosure may include L4S dynamic information as its attribute, wherein the L4S dynamic policy information may be included as a sub-attribute of at least one of a serviceDataFlowDescriptions attribute, a qoSSpecification attribute, and a protocolDescription attribute. A Dynamic Policy resource according to one embodiment of the present disclosure may include both one or more attributes including L4S dynamic policy information and information (e.g., a resource identifier) ​​on another resource including L4S dynamic policy information.

[0122] L4S dynamic policy information according to the present disclosure may include at least one of the following information as its components:

[0123] - l4sSupport: Whether L4S is supported. When included in the qoSSpecification or protocolDescription property, it can indicate whether all application flows described in the serviceDataFlowDescriptions property are supported. When included in an individual ServiceDataFlowDescription of the serviceDataFlowDescriptions property, it can indicate whether the service data flow described in the ServiceDataFlowDescription is supported.

[0124] - fallbackPolicy: Policy for cases where L4S is not supported. Can have values ​​such as required support and optional support.

[0125] - transportProtocol: Identifier(s) of the media transport protocol supporting L4S. Examples include TCP, RTP over UDP, QUIC, and SCTP. Additional attributes for L4S feedback may be included depending on the transport protocol. For example, if RTP over UDP is used, the identifier of the RTCP feedback message containing L4S feedback may be included.

[0126] - congestionCtrlScheme: Identifier of the congestion control algorithm to be used by the L4S transmitter. For example, Prague.

[0127] - congestionInfoRequired: Whether to subscribe to congestion information provided by 5G NF such as UPF.

[0128] Components of L4S dynamic policy information may be distributed and provided in the attribute(s) of the Dynamic Policy resource containing the L4S dynamic policy information and the attributes of other resources identified by the resource identifier. The Dynamic Policy resource according to the embodiment of the present disclosure may include or reference the same components of the L4S dynamic policy information in duplicate, and in this case, the priority of the duplicated component values ​​may be determined according to the policy of the network service provider or application provider.

[0129] FIG. 7 illustrates the structure of a terminal according to various embodiments of the present disclosure.

[0130] Referring to FIG. 7, a terminal according to one embodiment may include a transceiver (710), a memory (720), and a processor (730). The transceiver (710), the memory (720), and the processor (730) of the UE may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited thereto. For example, the terminal may include more or fewer components than the components described above. In addition, the processor (730), the transceiver (710), and the memory (720) may be implemented as a single chip. In addition, the processor (730) may include at least one processor. In addition, the terminal of FIG. 7 may correspond to the terminals described in FIGS. 1, 2, 5, and 6.

[0131] The transceiver (710) collectively refers to the UE receiver and the UE transmitter, and can transmit and receive signals with a base station or network entity. The signals transmitted and received with the base station or network entity may include control information and data. The transceiver (710) may include an RF transmitter for up-converting and amplifying the frequency of a transmission signal, and an RF receiver for low-noise amplification and down-converting the frequency of a reception signal. However, this is only an example of the transceiver (710), and the components of the transceiver (710) are not limited to the RF transmitter and RF receiver.

[0132] In addition, the transceiver (710) can receive a signal through a wireless channel and output it to the processor (730), and transmit the signal output from the processor (730) through the wireless channel. The memory (720) can store programs and data necessary for the operation of the UE. In addition, the memory (720) can store control information or data included in a signal acquired by the UE. The memory (720) can be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0133] The processor (730) can control a series of processes to enable the terminal to operate. For example, the transceiver (710) can receive a data signal including a control signal transmitted by a base station or a network entity, and the processor (730) can determine the result of receiving the control signal and data signal transmitted by the base station or the network entity.

[0134] FIG. 8 illustrates the structure of a network entity according to various embodiments of the present disclosure.

[0135] Referring to FIG. 8, a network entity according to one embodiment may include a transceiver (810), a memory (820), and a processor (830). The transceiver (810), the memory (820), and the processor (830) 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 thereto. For example, the network entity may include more or fewer components than the components described above. In addition, the processor (830), the transceiver (810), and the memory (820) may be implemented as a single chip. In addition, the processor (830) may include at least one processor. In addition, the network entity of FIG. 8 may correspond to the network entities described in FIGS. 1, 2, 5, and 6.

[0136] The transceiver (810) collectively refers to a network entity receiver and a network entity transmitter, and can transmit and receive signals with a terminal (UE), a base station, or other network entities. The signals transmitted and received with the terminal or network entities may include control information and data. The transceiver (810) may include an RF transmitter for up-converting and amplifying the frequency of a transmission signal and an RF receiver for low-noise amplifying and down-converting the frequency of a reception signal. However, this is only an example of the transceiver (810), and the components of the transceiver (810) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (810) may receive a signal through a wireless channel and output it to the processor (830), and transmit a signal output from the processor (830) through the wireless channel.

[0137] The memory (820) can store programs and data necessary for the operation of the network entity. In addition, the memory (820) can store control information or data included in signals acquired by the network entity. The memory (820) can be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, a DVD, or a combination of storage media. The processor (830) can control a series of processes so that the network entity operates as described above. For example, the transceiver (810) can receive a data signal including a control signal transmitted by a terminal or a base station, and the processor (830) can determine the result of receiving the control signal and the data signal transmitted by the terminal or the base station. The network entity of FIG. 8 can include a base station.

[0138] According to one embodiment of the present disclosure, a method of a service control device for supporting low-latency media streaming in a wireless communication system may include a step of receiving low-latency media streaming service configuration information from an application service provider, a step of setting a low-latency media streaming server, a step of receiving detailed information of a packet flow for a low-latency media streaming service from a user terminal or a low-latency media streaming server, and a step of providing network configuration information for the low-latency media streaming service to a network.

[0139] In addition, according to one embodiment of the present disclosure, a method of a service control device for supporting low-latency media streaming in a wireless communication system may include a step of receiving QoS and protocol information of a packet flow for a low-latency media streaming service from a user terminal or a low-latency media streaming server, and a step of requesting QoS and protocol settings to a network based on the QoS and protocol information.

[0140] Additionally, according to one embodiment of the present disclosure, the method may include a step of receiving information for QoS and protocol settings that may be requested by a user terminal or a low-latency media streaming server from a media application provider.

[0141] It should be noted that the configuration diagrams, exemplary diagrams of control / data signal transmission / reception methods, and exemplary diagrams of operating procedures illustrated in FIGS. 1 to 6 are not intended to limit the scope of the embodiments of the present disclosure. That is, not all components, entities, or operational steps described in FIGS. 1 to 6 should be construed as essential components for the implementation of the disclosure, and implementation may be performed within a scope that does not detract from the essence of the disclosure even if only some components are included.

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

[0143] The various components and modules of the entity or terminal device described in the present disclosure may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software, and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.

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

[0145] 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 claims or embodiments of the present disclosure.

[0146] 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 devices, compact disc-ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

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

[0148] In the specific embodiments of the present disclosure described above, components included in the present 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.

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

[0150] Electronic devices that implement, operate, and perform various embodiments of the present disclosure may take various forms. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of the present disclosure are not limited to the aforementioned devices.

[0151] The various embodiments of the present disclosure and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more items, unless the relevant context clearly indicates otherwise. In the present disclosure, each of the phrases "A or B," "at least one of A and B," "at least one of A or B," "A, B, or C," "at least one of A, B, and C," and "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among the phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0152] The term "module" used in various embodiments of the present disclosure may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be an integrally formed component or a minimum unit or part of a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0153] Various embodiments of the present disclosure may be implemented as software (e.g., a program) including one or more instructions stored in a storage medium (e.g., built-in memory or external memory) readable by a machine (e.g., an electronic device). For example, a processor (e.g., a processor) of the machine (e.g., an electronic device) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, "non-transitory" only means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily in the storage medium.

[0154] According to one embodiment, the method according to various embodiments of the present disclosure may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0155] According to various embodiments, each component (e.g., a module or a program) of the described components may include one or more entities, and some of the entities may be separated and placed in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. In a method performed by a terminal of a wireless communication system, A step of sending a dynamic policy setting request for a downlink streaming service based on a policy template to a Data Network (DN) entity; and comprising a step of identifying a result for the above dynamic policy setting request, The above policy template is a method including information on L4S (Low Latency Low Loss Scalable Throughput) support.

2. In paragraph 1, A step of establishing a media transmission session for the above data network entity and media content; and A method further comprising the step of transmitting a request for transmission of the media content to the data network entity.

3. In paragraph 2, A step of receiving the media content from the data network entity; and A method comprising the step of transmitting, to the data network entity, the results of an inspection of the ECN (Explicit Congestion Notification) field of the IP packet associated with the media content.

4. In paragraph 1, Information about the above L4S support is included in either the qoSSpecification attribute or the protocolDescription attribute of the above policy template.

5. A method performed by a data network entity of a wireless communication system, A step of receiving a policy template including information on L4S (Low Latency Low Loss Scalable Throughput) support; and A method comprising the step of receiving, from a terminal, a dynamic policy setting request for a downlink streaming service based on the policy template.

6. In paragraph 5, A step of requesting a media transmission traffic processing policy to a PCF (Policy Control Function) entity or a NEF (Network Exposure Function) entity; A step of establishing a media transmission session for the terminal and media content; and A method further comprising the step of receiving a request for transmission of the media content from the terminal.

7. In paragraph 6, A step of transmitting the media content to the terminal; and A method comprising the step of receiving, from the terminal, an inspection result for an ECN (Explicit Congestion Notification) field of an IP packet associated with the media content.

8. In paragraph 5, Information about the above L4S support is included in either the qoSSpecification attribute or the protocolDescription attribute of the above policy template.

9. In the terminal of a wireless communication system, Transmitter and receiver; and Includes a control unit connected to the above transmitter and receiver, The above control unit: Sends a dynamic policy setting request for downlink streaming service based on a policy template to a Data Network (DN) entity, is set to identify the result of the above dynamic policy setting request, The above policy template is a terminal that includes information on L4S (Low Latency Low Loss Scalable Throughput) support.

10. In paragraph 9, the control unit: Establishing a media transmission session for the above data network entity and media content, and A terminal configured to transmit a request for transmission of the media content to the data network entity.

11. In the 10th paragraph, in the control unit, Receiving the media content from the above data network entity, and A terminal configured to transmit, to the data network entity, the inspection result for the ECN (Explicit Congestion Notification) field of the IP packet associated with the media content.

12. In paragraph 9, Information about the above L4S support is included in either the qoSSpecification attribute or the protocolDescription attribute of the above policy template.

13. In a base station of a wireless communication system, Transmitter and receiver; and Includes a control unit connected to the above transmitter and receiver, The above control unit: Receive a policy template containing information about L4S (Low Latency Low Loss Scalable Throughput) support, and A base station configured to receive a dynamic policy setting request for a downlink streaming service based on the policy template from a terminal.

14. In paragraph 13, Request a policy for handling media transmission traffic from a PCF (Policy Control Function) entity or a NEF (Network Exposure Function) entity, Establish a media transmission session for the above terminal and media content, Receive a request for transmission of the media content from the terminal, Transmitting the media content to the terminal, and A base station configured to transmit, from the terminal, an inspection result for an ECN (Explicit Congestion Notification) field of an IP packet associated with the media content.

15. In paragraph 13, the control unit: Information about the above L4S support is included in either the qoSSpecification attribute or the protocolDescription attribute of the above policy template.

Images