Sub-picture level hrd

Abstract

The present disclosure provides a method. The method may comprise the steps of: transmitting a registration request message; transmitting a registration acceptance message; receiving a request message related to sub-picture-level HRD from a network entity related to an application; performing a sub-picture-level HRD operation including two or more of a capturing step, an encoding step, a transmission step, a decoding step, and / or a displaying step; and monitoring the sub-picture-level HRD operation.

Description

Sub-picture level HRD

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR, meeting both urgent market needs and the longer-term requirements outlined by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. NR must also be able to utilize any spectrum band up to at least 100 GHz, ensuring that it remains available for wireless communications well into the future.

[0004] NR aims to be a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra-Reliable and Low Latency Communications (URLLC). NR must be inherently forward-compatible.

[0005] As part of the evolution of 5G and one of the targets of 6G, ultra-low latency services must be supported. However, conventional technology has a problem in that it does not effectively support sub-picture-level HRD (Hypothetical Reference Decoder) operations required to support ultra-low latency services.

[0006] According to one embodiment of the present disclosure, a method is provided. The method may include: transmitting a registration request message; transmitting a registration acceptance message; receiving a request message related to a sub-picture-level HRD from a network entity associated with an application; performing a sub-picture-level HRD operation, the sub-picture-level HRD operation including two or more steps of a capturing step, an encoding step, a transmission step, a decoding step, and / or a displaying step; and performing monitoring of the sub-picture-level HRD operation.

[0007] According to one embodiment, a device implementing the method is provided.

[0008] According to one embodiment of the present disclosure, a method is provided. The method may include the steps of transmitting a request message related to sub-picture-level HRD to a UE; and receiving a result of monitoring the sub-picture-level HRD operation from the UE.

[0009] According to one embodiment, a device implementing the method is provided.

[0010] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0011] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0012] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0013] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0014] Figures 5 and 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0015] Figure 7 shows examples of picture based HRD operation and sub-picture level HRD operation.

[0016] Figure 8 shows an example of a terminal structure and a network structure to which the implementation of this specification is applied.

[0017] Figure 9 illustrates a first example of a procedure supporting sub-picture level HRD operations to which the implementation of the present specification applies.

[0018] Figure 10 illustrates a second example of a procedure supporting sub-picture level HRD operations to which the implementation of the present specification applies.

[0019] Figure 11 shows an example of a procedure to which the implementation of this specification is applied.

[0020] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) Long-Term Evolution (LTE) is part of E-UMTS (Evolved UMTS) that utilizes E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0021] For convenience of explanation, the implementation of this specification is primarily described in relation to a 3GPP-based wireless communication system. However, the technical features of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, but aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

[0022] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0023] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Alternatively, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0024] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0025] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0026] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

[0027] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (e.g., PDCCH)", "PDCCH" may be proposed as an example of "control information."

[0028] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0029] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0030] Hereinafter, the present specification will be described in more detail with reference to the drawings. In the following drawings and / or description, the same reference numbers may refer to the same or corresponding hardware blocks, software blocks, and / or functional blocks, unless otherwise indicated.

[0031] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0032] The 5G usage scenario shown in FIG. 1 is only an example, and the technical features of this specification can be applied to other 5G usage scenarios not shown in FIG. 1.

[0033] The three main requirement categories for 5G are (1) enhanced mobile broadband (eMBB), (2) massive machine type communication (mMTC), and (3) ultra-reliable and low latency communications (URLLC).

[0034] Referring to FIG. 1, a communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of a network of the communication system (1), but the implementation of the present disclosure is not limited to a 5G system and can be applied to future communication systems beyond the 5G system.

[0035] The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices.

[0036] The wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. The wireless devices (100a to 100f) may include, but are not limited to, a robot (100a), a vehicle (100b-1 and 100b-2), an extended reality (XR) device (100c), a portable device (100d), a home appliance (100e), an Internet-of-Things (IoT) device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of HMD (Head-Mounted Device) and HUD (Head-Up Display) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0037] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving function, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

[0038] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). AI technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0039] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and a base station (200) and / or between base stations (200). Here, the wireless communication / connection can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D (Device-To-Device) communication), and base station-to-base station communication (150c) (e.g., relay, IAB (Integrated Access and Backhaul)). Through the wireless communication / connection (150a, 150b, 150c), the wireless devices (100a to 100f) and the base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of this specification, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed.

[0040] NR supports multiple numerologies, or subcarrier spacings (SCS), to support diverse 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0041] The NR frequency band can be defined by two types of frequency ranges (FR1 and FR2). The numerical values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range," and FR2 can mean the "above 6 GHz range," which can be called millimeter wave (mmW).

[0042] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0043] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 2 below. For example, FR1 may include a frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

[0044] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0045] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also Narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (Non-Bandwidth Limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PANs (Personal Area Networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0046] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0047] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use case / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules.

[0048] The first wireless device (100) may include at least one transceiver, such as a transceiver (106), at least one processing chip, such as a processing chip (101), and / or one or more antennas (108).

[0049] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or alternatively, the memory (104) may be located external to the processing chip (101).

[0050] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0051] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

[0052] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). Each transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0053] The second wireless device (200) may include at least one transceiver, such as a transceiver (206), at least one processing chip, such as a processing chip (201), and / or one or more antennas (208).

[0054] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be located external to the processing chip (201).

[0055] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0056] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements code, instructions and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

[0057] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). Each transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with the RF unit. In the present specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0058] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Resource Control (RRC) layer, and a Service Data Adaptation Protocol (SDAP) layer). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs), one or more Service Data Units (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0059] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), and / or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a Memory Control Processor. One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer readable storage media and / or combinations thereof.One or more memories (104, 204) may be located internally and / or externally to one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0060] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0061] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present disclosure, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0062] One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0063] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0064] In the implementation of this specification, a UE can operate as a transmitter in the uplink and as a receiver in the downlink. In the implementation of this specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to the implementation of this specification or to control a transceiver (106) to perform UE operations according to the implementation of this specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of this specification or to control a transceiver (206) to perform base station operations according to the implementation of this specification.

[0065] In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.

[0066] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0067] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0068] The UE (100) includes a processor (102), memory (104), a transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0069] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors.

[0070] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

[0071] A transceiver (106) is operably coupled to the processor (102) and transmits and / or receives a radio signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a radio frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a radio signal.

[0072] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0073] The display (143) outputs the results processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0074] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

[0075] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0076] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0077] The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).

[0078] - AUSF (Authentication Server Function)

[0079] -AMF (Access and Mobility Management Function)

[0080] - DN (Data Network), for example, operator services, Internet access, or third-party services.

[0081] - USDF (Unstructured Data Storage Function)

[0082] - NEF (Network Exposure Function)

[0083] - I-NEF (Intermediate NEF)

[0084] - NRF (Network Repository Function)

[0085] - NSSF (Network Slice Selection Function)

[0086] - PCF (Policy Control Function)

[0087] - SMF (Session Management Function)

[0088] - UDM (Unified Data Management)

[0089] - UDR (Unified Data Repository)

[0090] - UPF (User Plane Function)

[0091] - UCMF (UE radio Capability Management Function)

[0092] - AF (Application Function)

[0093] - UE (User Equipment)

[0094] - (R)AN ((Radio) Access Network)

[0095] - 5G-EIR (5G-Equipment Identity Register)

[0096] - NWDAF (Network Data Analytics Function)

[0097] - CHF (CHarging Function)

[0098] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

[0099] - N3IWF (Non-3GPP InterWorking Function)

[0100] - TNGF (Trusted Non-3GPP Gateway Function)

[0101] - W-AGF (Wireline Access Gateway Function)

[0102] Figure 4 illustrates the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0103] For clarity of the point-to-point diagram in Figure 4, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0104] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Fig. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in Fig. 4.

[0105] The 5G system architecture includes the following benchmarks:

[0106] - N1: Reference point between UE and AMF.

[0107] - N2: Reference point between (R)AN and AMF.

[0108] - N3: Reference point between (R)AN and UPF.

[0109] - N4: Reference point between SMF and UPF.

[0110] - N6: Reference point between UPF and data network.

[0111] - N9: Reference point between two UPFs.

[0112] The following benchmarks illustrate the interactions that exist between NF services in NF.

[0113] - N5: Reference point between PCF and AF.

[0114] - N7: Reference point between SMF and PCF.

[0115] - N8: Reference point between UDM and AMF.

[0116] - N10: Reference point between UDM and SMF.

[0117] - N11: Reference point between AMF and SMF.

[0118] - N12: Reference point between AMF and AUSF.

[0119] - N13: Reference point between UDM and AUSF.

[0120] - N14: Reference point between two AMFs.

[0121] - N15: Reference point between PCF and AMF for non-roaming scenarios, and reference point between PCF and AMF of visited network for roaming scenarios.

[0122] - N16: Reference point between two SMFs (in case of roaming, between the SMF of the visited network and the SMF of the home network)

[0123] - N22: Reference point between AMF and NSSF.

[0124] In some cases, two NFs may need to be interconnected to serve a UE.

[0125] Describes the registration procedure. See section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0126] Figures 5 and 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0127] A UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration process using one of the following registration types:

[0128] - Initial registration for 5GS; or

[0129] - mobility registration update; or

[0130] - Periodic registration update; or

[0131] - Emergency registration

[0132] The general registration procedures of Figures 5 and 6 apply to all registration procedures described above, but periodic registration updates do not need to include all parameters used in other registration procedures.

[0133] The general registration procedures of Figures 5 and 6 can also be used to register a UE for a 3GPP connection when it is already registered for a non-3GPP connection, and vice versa. Registering a UE for a 3GPP connection when it is already registered for a non-3GPP connection scenario may require an AMF change.

[0134] First, the procedure of Fig. 5 is described.

[0135] (1) Step 1: The UE transmits a Registration Request message to the (R)AN. The Registration Request message corresponds to an AN message.

[0136] The registration request message may include AN parameters. For NG-RAN, the AN parameters include, for example, the 5G SAE temporary mobile subscriber identity (5G-S-TMSI) or globally unique AMF ID (GUAMI), the selected public land mobile network (PLMN) ID (or PLMN ID and network identifier (NID)), and the requested network slice selection assistance information (NSSAI). The AN parameters also include an establishment cause. The establishment cause provides the reason for requesting establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the access stratum connection establishment NSSAI inclusion mode parameter.

[0137] A registration request message may include a registration type. The registration type indicates whether the UE wants to perform an initial registration (e.g., the UE is in RM-DEREGISTERED state), or a mobility registration update (e.g., the UE is in RM-REGISTERED state and initiates a registration procedure because the UE moves, or the UE wants to update capabilities or protocol parameters, or requests a change in the set of network slices the UE is allowed to use), or a periodic registration update (e.g., the UE is in RM-REGISTERED state and initiates a registration procedure because a periodic registration update timer expires), or an emergency registration (e.g., the UE is in a restricted service state).

[0138] When a UE performs initial registration, the UE indicates its UE ID in the registration request message, listed in decreasing priority order.

[0139] i) If the UE has a valid evolved packet system (EPS) globally unique temporary identifier (GUTI), 5G-GUTI mapped from the EPS GUTI;

[0140] ii) Native 5G-GUTI (if available) allocated by the PLMN in which the UE is attempting to register;

[0141] iii) Native 5G-GUTI allocated by a PLMN equivalent to the PLMN in which the UE is attempting to register;

[0142] iv) Native 5G-GUTI allocated by another PLMN (if available);

[0143] v) Otherwise, the UE includes a subscriber concealed identifier (SUCI) in the registration request message.

[0144] If a UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE also indicates the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE selects a 5G-GUTI from items (ii)-(iv) in decreasing priority order in the list above.

[0145] When the UE performs initial registration with native 5G-GUTI, the UE indicates the relevant GUAMI information in the AN parameters. When the UE performs initial registration with SUCI, the UE does not indicate the GUAMI information in the AN parameters.

[0146] For emergency registration, if the UE does not have a valid 5G-GUTI, the SUCI is included. If the UE does not have a subscriber permanent identifier (SUPI) and does not have a valid 5G-GUTI, the PEI (Permanent Equipment Identifier) ​​is included. Otherwise, the 5G-GUTI is included, indicating the last serving AMF.

[0147] The registration request message may also include security parameters, PDU session status, etc. Security parameters are used for authentication and integrity protection. The PDU session status indicates a previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the PDU session status indicates the PDU session currently established in the PLMN in the UE.

[0148] (2) Step 2: (R)AN selects AMF.

[0149] If 5G-S-TMSI or GUAMI is not included, or if 5G-S-TMSI or GUAMI does not indicate a valid AMF, the (R)AN selects an AMF based on the (R)AT and the requested NSSAI, if available.

[0150] When the UE is in CM-CONNECTED state, (R)AN can forward a registration request message to AMF based on the N2 connection of the UE.

[0151] If the (R)AN cannot select an appropriate AMF, the (R)AN performs AMF selection by forwarding a registration request message to the AMF configured in the (R)AN.

[0152] (3) Step 3: (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message.

[0153] The registration request message may contain all of the information and / or part of the information contained in the registration request message received from the UE described in step 1.

[0154] The registration request message may include an N2 parameter. When NG-RAN is used, the N2 parameter includes the selected PLMN ID (or PLMN ID and NID), location information and cell ID related to the cell where the UE is camping, and a UE context request indicating that a UE context including security information should be established in the NG-RAN. When NG-RAN is used, the N2 parameter also includes an establishment cause.

[0155] If the registration type indicated by the UE is periodic registration update, steps 4-19 described below may be omitted.

[0156] (4) Step 4: If the UE's 5G-GUTI is included in the registration request message and the serving AMF has changed since the last registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service operation to the previous AMF, including the full registration request non-access stratum (NAS) message to request the UE's SUPI and UE context.

[0157] (5) Step 5: The old AMF can respond to the new AMF for the Namf_Communication_UEContextTransfer call including the UE's SUPI and UE context.

[0158] (6) Step 6: If SUCI is not provided by the UE or not retrieved from the previous AMF, the new AMF may initiate an ID request procedure by sending an Identity Request message to request SUCI from the UE.

[0159] (7) Step 7: The UE may respond with an Identity Response message including the SUCI. The UE derives the SUCI using the provided public key of the home PLMN (HPLMN).

[0160] (8) Step 8: The new AMF may decide to initiate UE authentication by calling the AUSF. In this case, the new AMF selects the AUSF based on SUPI or SUCI.

[0161] (9) Step 9: Authentication / security can be established by UE, new AMF, AUSF and / or UDM.

[0162] (10) Step 10: If the AMF has changed, the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to notify the old AMF that the UE registration with the new AMF is complete. If the authentication / security procedure fails, the registration is rejected and the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code to the old AMF. The old AMF may continue as if the UE context transfer service operation was not received.

[0163] (11) Step 11: If the PEI was not provided by the UE or was not retrieved from the previous AMF, the new AMF may initiate the ID request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted encrypted, except when the UE performs emergency registration and cannot be authenticated.

[0164] (12) Step 12: Optionally, the new AMF can initiate ME ID checking by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

[0165] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is described.

[0166] (13) Step 13: When step 14 below is performed, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

[0167] (14) Step 14: New AMFs can be registered with UDM.

[0168] (15) Step 15: New AMF can select PCF.

[0169] (16) Step 16: The new AMF may optionally perform AM policy association establishment / modification.

[0170] (17) Step 17: The new AMF can send update / release SM context messages (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to the SMF.

[0171] (18) Step 18: If the new AMF and the old AMF are in the same PLMN, the new AMF may send a UE context modification request to the N3IWF / TNGF / W-AGF.

[0172] (19) Step 19: N3IWF / TNGF / W-AGF may send a UE context modification response to the new AMF.

[0173] (20) Step 20: After the new AMF receives the response message from N3IWF / TNGF / W-AGF in step 19, the new AMF can register with UDM.

[0174] (21) Step 21: The new AMF sends a Registration Accept message to the UE.

[0175] The new AMF sends the UE a Registration Accept message indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, it includes the 5G-GUTI. If the UE is already in the RM-REGISTERED state through another connection to the same PLMN, the UE uses the 5G-GUTI received in the Registration Accept message for both registrations. If the Registration Accept message does not include a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration. If the new AMF allocates a new registration area, it sends the registration area to the UE in the Registration Accept message. If the Registration Accept message does not include a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included if mobility restrictions apply to the UE and the registration type is not emergency registration. The new AMF indicates the PDU sessions established for the UE in the PDU Session State. The UE locally removes internal resources associated with PDU sessions that are not marked as established in the received PDU Session State. When a UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with PDU sessions in the current PLMN that are not marked as established in the received PDU session status. If PDU session status information is present in the Registration Accept message, the new AMF indicates the PDU session status to the UE.

[0176] The Allowed NSSAI provided in the Registration Accept message is valid for the registration area and applies to all PLMNs that have a tracking area included in the registration area. The Mapping of Allowed NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Allowed NSSAIs. The Mapping of Configured NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Configured NSSAI for the serving PLMN.

[0177] Additionally, optionally, the new AMF performs UE policy association establishment.

[0178] (22) Step 22: If the UE successfully updates itself, it can send a Registration Complete message to the new AMF.

[0179] The UE may send a registration complete message to the new AMF to confirm that a new 5G-GUTI has been allocated.

[0180] (23) Step 23: In case of registration via 3GPP connection, if the new AMF does not release the signaling connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN. In case of registration via non-3GPP connection, if the UE is in CM-CONTENED state on the 3GPP connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN.

[0181] (24) Step 24: AMF can perform information updates on UDM.

[0182] (25) Step 25: The UE may execute a network slice-specific authentication and authorization (NSSAA) procedure.

[0183] During the transmission and decoding of video content, the Hypothetical Reference Decoder (HRD) model is used to reliably manage the decoder's buffer status. HRD defines the rules that must be observed during stream generation to ensure stable decoding and playback without buffer overflow or underflow when a bitstream is input to the decoder.

[0184] Sub-picture-level (Hypothetical Reference Decoder) HRD operations are being discussed for ultra-low delay support. For example, with the recent increase in applications requiring real-time performance, such as ultra-low latency communications, streaming services, AR, and VR, existing picture-based HRD operations have limitations. To address these needs, sub-picture-level HRD operations are being discussed.

[0185] For example, H.265 (HEVC) specifies sub-picture-level High Resolution Display (HRD) operation to support ultra-low latency. This mechanism specifies a standard-compliant way to enable latency reductions of less than one picture interval. Sub-picture-level coded picture buffer (CPB) and DPB parameters can be signaled, and a method is specified to derive CPB timing (where CPB removal time corresponds to decoding time) and DPB output timing (display time) using this information. A decoder can also operate HRD at the traditional access unit level, even if sub-pixel-level HRD parameters are present.

[0186] Hereinafter, examples of conventional picture-based HRD operation and sub-picture level HRD operation are described with reference to FIG. 7.

[0187] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0188] Figure 7 shows examples of picture based HRD operation and sub-picture level HRD operation.

[0189] Existing HRD models primarily follow picture-based HRD operations. As illustrated in Figure 7 (A), in picture-based HRD, entire frames (pictures) are captured, encoded, and then transmitted and input to a decoder. The decoder performs decoding and display on a per-picture basis. At this time, the time required from capturing to displaying the entire picture is managed as a constant cycle (t). However, because transmission and decoding are performed on a per-picture basis, there is a problem in that the delay time required for decoding and playback becomes relatively long.

[0190] Sub-picture-level HRD is a method that divides a picture into multiple sub-picture units and independently controls buffer management and decoding schedule for each sub-picture. As illustrated in (B) of Fig. 7, in sub-picture-based HRD, a picture is divided into multiple sub-pictures, and each sub-picture is individually captured, encoded, transmitted, decoded, and displayed. The processing time of each sub-picture is represented by dt, which is the total cycle t divided by the number of decoding units N (dt = t / N). Since the data flow is segmented into sub-picture units in this way, partial decoding and display are possible without waiting for the entire frame, which significantly reduces decoding delay. For example, as illustrated in Fig. 7, in sub-picture-level HRD operation, display can begin after capture begins within a time smaller than the capture time t in conventional picture-based HRD operation.

[0191] However, according to the prior art, the subpicture-based HRD model has limited implementation efficiency and stability in implementing subpicture HRD operations because a specific implementation method has not been defined. In addition, there has been no method for the terminal to effectively support subpicture-level HRD functions. For example, for the terminal to support and effectively perform subpicture-level HRD functions, monitoring the results of the terminal's execution of the subpicture-level HRD function may be necessary. However, the problem with the prior art is that there is a lack of research on the exposure API that reports monitoring of the specific execution results of the terminal.

[0192] In some implementations, the disclosure of this specification proposes examples of ways to efficiently support sub-picture-level HRD operations.

[0193] In some implementations, the disclosure of this specification may describe network support technologies and terminal data collection / exposure required for providing 6G media services such as XR / immersive services.

[0194] In some implementations, the various examples described in the disclosure of this specification illustrate examples of terminals directly collecting encoding / deciding-related data in an environment where a group of various devices / drones / robots, etc., collaborate to provide services. Furthermore, the various examples described in the disclosure of this specification illustrate examples of technologies that can expose this information to the terminal's application service layer or network. Furthermore, terminals can more effectively provide 6G services based on AI and distributed processing by exchanging information related to sub-picture-level HRD with other terminals in a cooperative relationship. Examples of system support functions and procedures that implement these operations are described.

[0195] For reference, in the disclosure of this specification, the terms network node and network entity may be used as terms with the same meaning.

[0196] For reference, in the disclosure of this specification, AF and application server may be used as terms with the same meaning.

[0197] For reference, in the disclosure of this specification, UE and terminal may be used as terms having the same meaning.

[0198] The collaborative robot scenario disclosed in this specification does not solely refer to physical mechanical robots, but can also encompass scenarios in which various terminals / devices, such as automobiles, drones, IoT devices, and wearable devices, collaborate to perform services. For example, the term "terminal" is not limited to robots, but can encompass a comprehensive range of devices.

[0199] As illustrated in the example of Figure 7, picture-level HRD operations can be performed in the following order. For example, capturing -> encoding -> transmission -> decoding -> displaying can be performed sequentially. Unlike picture-level HRD, where each step is performed without overlapping, sub-picture-level HRD can perform each step with some overlap.

[0200] In various examples disclosed herein, a communication system may selectively utilize picture-level HRD and sub-picture-level HRD. For example, examples of using sub-picture-level HRD operations and / or examples of applying flexible control, such as when a network or UE requests monitoring related to sub-picture-level HRD operations, are described.

[0201] For example, monitoring related to sub-picture-level HRD operations can be performed by the terminal. The terminal may perform monitoring related to sub-picture-level HRD operations based on a combination of one or more of the following examples:

[0202] - When sub-picture-level HRD operations are used, the start times of each of the five monitored steps (e.g., capturing / encoding / transmission / decoding / displaying);

[0203] - Time intervals between the start of each of the five steps (e.g., capturing / encoding / transmission / decoding / displaying). For example, the time interval between capturing and encoding; and / or

[0204] - In the displaying phase of the sub-picture-level HRD operation, parameters related to user QoE displayed on the terminal (e.g., buffering status, average packet delay time, average packet loss rate, etc.).

[0205] For example, as a result of monitoring, the terminal may derive analysis information (e.g., including statistical values ​​and / or predicted values), such as the following examples:

[0206] - Example (a) Whether the user's QoE set on the terminal is maintained while the sub-picture-level HRD operation is performed.

[0207] - Example (b) Possible / effective overlap time between some steps of Sub-picture-level HRD operation while maintaining the user QoE set on the terminal; and / or

[0208] - Example (c) Referring to Example 8, the processing time for each step required to perform a sub-picture-level HRD operation while maintaining the user's QoE set on the terminal is also shown as an example of the terminal structure and network structure when monitoring related to the sub-picture-level HRD operation is performed.

[0209] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0210] Figure 8 shows an example of a terminal structure and a network structure to which the implementation of this specification is applied.

[0211] Figure 8 is an example of the structure of a terminal to which the implementation of this specification is applied and the structure of a network.

[0212] However, the structure of FIG. 8 is merely an example of the structure of the UE and the structure of the network (e.g., data network) when monitoring related to sub-picture-level HRD operations is performed. The scope of the disclosure of the present specification is not limited by the structure of FIG. 8. For example, each component included in the UE may be merely a logical component that performs the operation of the UE, and thus each component may be a unit describing a functional operation performed by the processor of the UE. In addition, each component included in the data network in the example of FIG. 8 may also be a unit describing a functional operation performed by one application server (or Application Function (AF)).

[0213] A terminal (e.g., UE) may include one or more of the following components:

[0214] - Vertical application specific client: This may be a function in charge of the application service of the terminal. For example, the vertical application specific client may have functions for different application services depending on the vertical. When different functions within the terminal (HRD performing client or UE analytic function) transmit HRD-related information (e.g., terminal experience information recognized or collected / analyzed by each internal function of the terminal) to the vertical application specific client, the vertical application specific client may transmit HRD-related information (e.g., terminal experience information) to the network (e.g., media-related entities of the edge / cloud, application servers, core networks, and / or network function nodes of base stations, etc.) and / or other terminals. Here, the experience information may include one or more of the following information: a specific time during which the HRD operation is performed, a step-by-step processing time of the HRD operation during the HRD operation cycle, a step-by-step success / failure rate of the HRD operation (additionally, a reprocessing rate), a terminal / user QoE level during the HRD operation, etc.

[0215] - HRD Control function: The HRD Control function can be responsible for controlling HRD. The HRD Control function can receive HRD policy and configuration information, such as encoding / decoding, from the network AF and perform the necessary controls for HRD operation.

[0216] - HRD performing client: Based on requests and / or instructions received from the network, the HRD performing client can perform HRD operations such as encoding / decoding under the control of the HRD control function within the terminal and transmit media to the network and / or other terminals. The HRD performing client can record and / or store the results of the HRD operations and transmit them to the HRD control function and / or the application layer. If there is a UE analytic function within the terminal, the HRD performing client can transmit HRD-related information (e.g., terminal experience information) to the UE analytic function for statistical and predictive value analysis of HRD-related information (e.g., terminal experience information).

[0217] - UE analytic function: The UE analytic function can collect information related to HRD operations such as encoding / decoding, and analyze statistical values ​​and / or predicted values ​​of terminal experience information related to HRD. The UE analytic function can transmit the analysis information (e.g., including statistical values ​​and / or predicted values) to the network and / or terminal application layer.

[0218] A network (e.g., a data network) may contain one or more of the following components. The three components below are examples only; a single application server may perform some or all of the following:

[0219] - Media AF: Media AF can transmit support / monitoring request messages to terminals to perform application services or to network control nodes. Media AF can also transmit policy and configuration information related to HRD control to terminals.

[0220] - HRD performing server: The HRD performing server can be a peer of the terminal's HRD performing client. The HRD performing server can perform HRD-related operations, such as encoding / decoding, as needed.

[0221] - Application provider: An application provider can provide application services. For example, an application provider may include functionality to provide vertically specialized application services.

[0222] Referring to the example of FIG. 9, an example of a sub-picture level HRD operation according to one embodiment of the disclosure of the present specification is described.

[0223] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0224] Figure 9 illustrates a first example of a procedure supporting sub-picture level HRD operations to which the implementation of the present specification applies.

[0225] 1. The application server can send a request message to the UE.

[0226] For example, a request message may contain information requesting that a sub-picture-level HRD operation be performed.

[0227] For example, the request message may also contain information requesting monitoring of sub-picture-level HRD operations.

[0228] Note that step 1 may be omitted. The UE may perform sub-picture-level HRD operations for specific application execution based on pre-configured information, without an explicit request from the application server.

[0229] 2. The UE can perform sub-picture level HRD operations.

[0230] As illustrated in the example of FIG. 9, a UE can perform sub-picture level HRD operations with other UEs and / or network nodes. For example, in the example of FIG. 7, the UE can perform Capturing, Encoding, and Transmission, while other UEs and / or network nodes can perform Decoding and Displaying.

[0231] 3. The UE can perform monitoring and / or analysis of sub-picture level HRD operations.

[0232] For example, a UE may monitor sub-picture level HRD operations it performs and / or sub-picture level HRD operations performed by other network nodes.

[0233] For example, the UE may perform analysis on the results of monitoring sub-picture level HRD operations. The UE may derive analysis information (e.g., including predictions and / or statistics).

[0234] 4. The UE may transmit UE data related to sub-picture level HRD operations to applications, other UEs, and / or network nodes.

[0235] UE data related to sub-picture level HRD operations may include information related to the results of monitoring sub-picture level HRD operations and / or analysis information regarding the results of monitoring sub-picture level HRD operations. For example, by transmitting UE data related to sub-picture level HRD operations, the UE, other UEs, network nodes, and application servers may provide the UE with information that supports more efficient performance of sub-picture level HRD operations.

[0236] Hereinafter, with reference to the example of FIG. 10, an example in which a different operation from the example of FIG. 9 is specifically performed will be described. The operations according to the example of FIG. 9 and the operations according to the example of FIG. 10 may be combined with each other.

[0237] The disclosure of this specification encompasses collaborative robot scenarios, and thus encompasses scenarios where information collected and predicted by a single terminal is transmitted to other network nodes, servers, and / or other terminals. However, this does not exclude scenarios where a single terminal is used. For example, even when a single terminal provides a service independently, the functions / control procedures described herein can be utilized.

[0238] Referring to the example of FIG. 10, a second example of a procedure supporting sub-picture level HRD operations to which the implementation of the present specification applies is described. The example of FIG. 10 may be an example in which the terminal structure and network structure of the example of FIG. 8 are applied to the operation of the example of FIG. 9.

[0239] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0240] Figure 10 illustrates a second example of a procedure supporting sub-picture level HRD operations to which the implementation of the present specification applies.

[0241] The example in FIG. 10 is an example of a control procedure to which the functions described in the disclosure of this specification are applied.

[0242] The UE application, UE control function, UE analysis function, and UE HRD performing included in the UE are merely examples for explaining the operation of the UE, and the operations performed by each of the UE application, UE control function, UE analysis function, and UE HRD performing may all be operations performed by the UE.

[0243] For reference, before performing the operation according to the example of FIG. 10, the terminal may perform the registration procedure described with reference to FIGS. 5 and 6. For example, the terminal may transmit a registration request message to the AMF. For example, the registration request message may include capability information related to the terminal supporting sub-picture-level HRD operations. Alternatively, the terminal may transmit capability information related to supporting sub-picture-level HRD operations to the Media AF and / or application server via an application layer message.

[0244] 1. Media AF can transmit settings and policies for HRD-related services to the terminal.

[0245] For example, a network node Media AF can provision information related to policies, such as parameters and billing required for performing HRD, for services related to HRD, services requiring HRD application, and / or services requiring Ultralow delay, to terminals.

[0246] For reference, step 1 may be performed based on receiving capability information from the AMF or from the UE regarding whether the Media AF supports sub-picture-level HRD operations.

[0247] 2. The terminal (e.g., the terminal's control function) can update the configuration and policy, and apply the policy when necessary. The configuration and / or policy may include parameters (e.g., default time value, reporting cycle, etc.) required when the terminal performs a sub-picture-level HRD operation and monitoring related to the sub-picture-level HRD, conditions under which the sub-picture-level HRD is performed (e.g., validity time / location, etc.), monitoring performance and reporting conditions, etc. For example, at this stage, parameters (e.g., default time value, reporting cycle, etc.) required when the terminal performs a sub-picture-level HRD operation and monitoring related to the sub-picture-level HRD, conditions under which the sub-picture-level HRD is performed (e.g., validity time / location, etc.), monitoring performance and reporting conditions, etc. may be set or updated.

[0248] 3. The application server may transmit a request message to the UE to request sub-picture-level HRD execution and / or to request monitoring related to sub-picture-level HRD. The application server may transmit the request message to the UE via Media AF, or the application server may transmit the request message directly to the UE.

[0249] Note that in various examples disclosed in this specification, the application server and media AF may be described as separate entities, but this is merely an example. For example, the application server and media AF may be the same device.

[0250] For example, the Application server or AF may request or instruct the terminal and / or the network (e.g., NW HRD performing in FIG. 10) to perform Sub-picture-level HRD. Alternatively, the Application server or AF may implicitly request or instruct the terminal and / or the network to perform Ultralow delay service, thereby requesting or instructing the terminal to perform Sub-picture-level HRD. Alternatively, the terminal may perform Sub-picture-level HRD operation for performing a specific application, even without an explicit request or instruct from the network, according to information configured in advance. For example, the application layer of the terminal may instruct the performing function module (e.g., UE HRD performing) to perform Sub-picture-level HRD.

[0251] In some implementations, when the application server transmits a request message to the UE to request execution of sub-picture-level HRD, it may also transmit information for requesting monitoring related to sub-picture-level HRD to the UE. Alternatively, the application server may separately transmit a request message for requesting monitoring related to sub-picture-level HRD to the UE. Alternatively, even if the application server does not transmit information for requesting monitoring related to sub-picture-level HRD to the UE, the UE may receive a request message for requesting execution of sub-picture-level HRD or perform monitoring related to sub-picture-level HRD based on preset information.

[0252] Note that step 3 may be performed based on the capability information received from the AMF or the UE regarding whether the Application server or AF supports sub-picture-level HRD operations.

[0253] 4. The terminal, other terminals, and / or the network can perform sub-picture-level HRD.

[0254] For example, after a terminal performs capturing and encoding, it can transmit data to another terminal (e.g., another UE in the example of FIG. 10) and / or a network node (e.g., a NW HRD performing in the example of FIG. 10). Then, the network node and / or another terminal can perform decoding and displaying operations. Since sub-picture-level HRD is requested, some or all of the five steps (e.g., capturing, encoding, transmission, decoding, displaying) can be performed overlapping with other steps, and ultra-low delay can be supported.

[0255] Additionally, the terminal can monitor sub-picture-level HRD. For example, the terminal can collect information related to sub-picture-level HRD performed by itself, information related to sub-picture-level HRD performed by other terminals, and / or information related to sub-picture-level HRD performed by network nodes.

[0256] For example, information related to Sub-picture-level HRD collected by the terminal may include the start time of some or all of the five steps of Sub-picture-level HRD (e.g., capturing, encoding, transmission, decoding, displaying), the time interval between steps for some or all of the five steps, and / or information related to user QoE.

[0257] 5. The terminal may transmit the monitoring results (e.g., information related to Sub-picture-level HRD collected by the terminal) to a functional module within the terminal (e.g., UE analysis function and / or UE control function) and / or a UE application.

[0258] For example, information related to Sub-picture-level HRD performed internally in the terminal (e.g., start time of some or all of the five steps of Sub-picture-level HRD (e.g., capturing, encoding, transmission, decoding, displaying), time intervals between steps for some or all of the five steps, and / or information related to user QoE, etc.) can be monitored. The monitoring result can be transmitted to a functional module or application layer within the terminal.

[0259] 6. The terminal can perform analysis on the monitoring results. For example, the terminal can generate analysis information (e.g., statistical values ​​and predicted values) on the monitoring results.

[0260] The terminal may also support analysis of monitoring information. For example, the terminal may include a functional module responsible for analytics. The terminal may generate statistics and / or predictions for the monitoring results, as in the following examples:

[0261] - Example (a) Whether the user's QoE set on the terminal is maintained while the sub-picture-level HRD operation is performed.

[0262] - Example (b) Possible / effective overlap time between some steps of Sub-picture-level HRD operation while maintaining the user QoE set on the terminal; and / or

[0263] - Example (c) Processing time for each step required to perform Sub-picture-level HRD operation while maintaining the user's QoE set in the terminal, etc. 7. Analysis information generated within the terminal (e.g., statistical values ​​and predicted values, etc.) can be transmitted to the function module or application layer within the terminal.

[0264] 8. The terminal may transmit UE data related to sub-picture-level HRD to other terminals and / or network nodes. For example, UE data related to sub-picture-level HRD may include monitoring results for sub-picture-level HRD, analysis information related to monitoring results for sub-picture-level HRD, information based on monitoring results, and / or information based on analysis information.

[0265] For example, information collected through various functional nodes within the terminal and / or information processed from the collected information may be exposed to other terminals and control nodes of the network, application servers, etc. in a cooperative relationship. For example, the collected information may include the monitoring results collected by the terminal itself (e.g., start time / end time of each HRD step, etc.). For example, the processed information from the collected information may include analysis information generated by the terminal based on the monitoring results (e.g., statistical values ​​and / or predicted values ​​for the monitoring results, such as the overlapping time of each step of the expected HRD operation, etc.). The terminal may transmit the collected information (e.g., monitoring results) and the processed information (e.g., analysis information for the monitoring results and / or data based on the analysis information) to other UEs and / or network nodes.

[0266] For reference, in the example of FIG. 10, another UE receiving UE data related to sub-picture-level HRD transmitted by the terminal in step 8 is depicted as being identical to another UE performing step 4, but this is merely an example. For example, the terminal may transmit UE data related to sub-picture-level HRD to another UE performing step 4 as depicted in FIG. 10 and / or to another UE that did not perform step 4.

[0267] For reference, the network node receiving the UE data related to the sub-picture-level HRD transmitted by the terminal in step 8 of FIG. 10 is depicted differently from the NW HRD performing step 4, but this is merely an example. For example, the terminal performing the NW HRD performing step 4 illustrated in FIG. 10 may be the same as the network node in step 8.

[0268] UE data related to sub-picture-level HRD transmitted by the terminal can be used / utilized as follows:

[0269] - The network's application server and / or media server can determine whether HRD-related configuration and policy update is necessary based on UE data related to sub-picture-level HRD. For example, the application server and / or media server can configure thresholds or requirements for time intervals of major steps (e.g., time intervals between capturing and encoding). The application server and / or media server can determine whether the configured threshold or requirement is appropriate based on UE data related to sub-picture-level HRD transmitted by the terminal, and can change the configured threshold or requirement. If the network's application server and / or media server updates the configuration and / or policy, the updated description and / or policy can be transmitted to the terminal, as in step 1.

[0270] - Based on the UE data related to the sub-picture-level HRD transmitted by the terminal, the network node of the core network (e.g., SMF, UPF) can determine whether the transmission time of the terminal needs to be adjusted. The network node of the core network can appropriately adjust the delay, etc. for the media flow that provides the service related to the sub-picture-level HRD, so that the sub-picture-level HRD operation can be performed effectively. The network node of the core network can also change the QoS parameter / operate QoS control.

[0271] For 6G services based on AI and distributed processing, each media service processing module (e.g., rendering for XR services) may be processed on a different terminal. In this case, based on UE data related to the sub-picture-level HRD transmitted by the terminal, the other terminal can change the configuration related to the sub-picture-level HRD or apply the changed policy.

[0272] In some implementations, a terminal may receive a request related to an Ultralow Delay service (or a request related to sub-picture level HRD) from the network. Based on the request, the terminal may perform a sub-picture level HRD operation. For example, the terminal may monitor the start time, time interval, and / or user QoE information for each step of the sub-picture level HRD operation. For example, the information collected and processed through various functional nodes within the terminal may be exposed to other terminals in a cooperative relationship, the network control node, and / or the application server.

[0273] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0274] Figure 11 illustrates an example of a procedure to which the implementation of this specification is applied.

[0275] For reference, the procedure illustrated in FIG. 11 is merely an example, and the scope of the disclosure of this specification is not limited by the example in FIG. 11.

[0276] For example, with respect to the example of FIG. 11, the operations described in the examples of FIGS. 1 to 10 may also be applied. For example, even if operations, contents, etc. are not directly described in the example of FIG. 11, operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0277] The first network entity may be a network entity related to mobility (e.g., AMF).

[0278] The second network entity may be an application-related network entity (e.g., AS AF, media AF, etc.).

[0279] In step (S1101), the UE may transmit a registration request message to the first network entity.

[0280] In some implementations, the registration request message may include capability information related to the UE's support for sub-picture-level HRD.

[0281] In step (S1102), the first network entity may send a registration acceptance message to the UE.

[0282] Before step (S1103) is performed, the UE may acquire settings and / or policies related to HRD operations. For example, based on the settings and / or policies related to HRD operations, the sub-picture-level HRD operation of step (S1104) may be performed.

[0283] In step (S1103), the second network entity may transmit a request message to the UE.

[0284] For example, the request message may be a request message related to sub-picture-level HRD. The UE may perform a sub-picture-level HRD operation based on the received request message.

[0285] In some implementations, the request message may include request information related to the execution of the sub-picture-level HRD and / or monitoring request information related to the sub-picture-level HRD.

[0286] In some implementations, the request message may not include monitoring request information related to the sub-picture-level HRD. The UE may perform step (S1105) based on performing the sub-picture-level HRD operation even if monitoring request information related to the sub-picture-level HRD is not received.

[0287] Alternatively, step (S1103) may be omitted. The UE may perform a sub-picture-level HRD operation for executing a specific application according to preset information even if a request message is not received.

[0288] In step (S1104), the UE can perform sub-picture-level HRD operations.

[0289] A sub-picture-level HRD operation may include two or more of the following steps: a capturing step, an encoding step, a transmission step, a decoding step, and / or a displaying step.

[0290] For example, the steps for performing sub-picture-level HRD operations may include a capturing step and an encoding step; and a transmission step for transmitting data to another UE and / or a network entity during or after performing the capturing step and the encoding step. The decoding step and the displaying step may be performed by another UE and / or another network entity.

[0291] At step (S1105), the UE can monitor sub-picture-level HRD operations.

[0292] For example, the results of monitoring may include one or more of the following: start times of some or all of the steps included in the Sub-picture-level HRD operation, time intervals between the steps included in the Sub-picture-level HRD operation, and / or information related to the user's Quality of Experience (QoE).

[0293] In some implementations, the UE may transmit the results of the monitoring to one or more of another UE, a network entity, and / or a second network entity.

[0294] In some implementations, the UE may also generate analysis information regarding the monitoring results. For example, the analysis information may include predictions and / or statistics regarding the monitoring results.

[0295] For example, the UE may transmit analysis information and / or monitoring results to one or more of another UE, a network entity, and / or a second network entity.

[0296] A method further comprising a step of determining whether to update settings and / or policies related to the HRD operation based on the results of the monitoring.

[0297] For example, a second network entity may decide, based on the results of the monitoring, whether to update settings and / or policies related to HRD operations.

[0298] For example, a second network entity may update settings and / or policies related to the HRD operation based on the results of the monitoring.

[0299] In some implementations, the UE may receive settings and / or policies related to updated HRD behavior from a second network entity based on the results of the monitoring.

[0300] For example, the second network entity may transmit updated settings and / or updated policies related to HRD operations to the UE.

[0301] For example, updated settings and / or updated policies related to an HRD operation may include thresholds and / or requirements related to time intervals between steps included in the HRD operation.

[0302] This specification may have various effects.

[0303] For example, sub-picture-level HRD operations can be effectively supported by having the terminal perform monitoring for sub-picture-level HRD operations.

[0304] For example, a terminal can collect data related to sub-picture-level HRD operations (e.g., various stages such as encoding / deciding). The terminal can then expose the collected information to its application service layer or the network. This can more effectively provide 6G services based on AI and distributed processing.

[0305] For example, in an environment where various devices / drones / robots collaborate to provide services, sub-picture-level HRD operations can be effectively supported. Technology can be supported that allows terminals to directly collect data related to sub-picture-level HRD operations (e.g., various stages such as encoding / deciding) and expose the collected information to the terminal's application service layer or network. Furthermore, terminals can more effectively provide 6G services based on AI and distributed processing by exchanging the collected information with other terminals and / or network nodes in a cooperative relationship.

[0306] The effects that can be achieved through the specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0307] For reference, the operation of the terminal (e.g., UE) described in this specification may be implemented by the devices of FIGS. 1 to 3 described above. For example, the terminal may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). The one or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (105 or 206), and execute the instructions / programs stored in one or more memories (104 or 204) to perform the operation of the terminal (e.g., UE) described in the disclosure of this specification.

[0308] Additionally, the commands for performing the operations of the terminal described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). In addition, the commands recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the terminal described in the disclosure of this specification.

[0309] For reference, the operation of a network node (e.g., OAM, AMF, SMF, PCF, UDM, NWDAF, UDM / UDR, AF, NEF, UPF, media AF, application server, etc.) or a base station (e.g., NG-RAN, gNB, RAN, eNB, (R)AN, etc.) described in this specification may be implemented by the devices of FIGS. 1 to 3 described below. For example, the network node or the base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the network node or the base station described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a network node or base station as described in the disclosure of this specification.

[0310] Additionally, the instructions for performing the operations of the network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium having the instructions recorded thereon. The storage medium may be included in one or more memories (104 or 204). In addition, the instructions recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the network node or base station described in the disclosure of this specification.

[0311] Although the preferred embodiments have been described above by way of example, the disclosure of this specification is not limited to these specific embodiments, and may be modified, changed, or improved in various forms within the scope of the spirit and claims of this specification.

[0312] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0313] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.

Claims

1. Step of sending a registration request message; Step for sending a registration acceptance message; A step of receiving a request message related to a sub-picture-level Hypothetical Reference Decoder (HRD) from a network entity related to the application; A step of performing a sub-picture-level HRD operation including two or more steps among a capturing step, an encoding step, a transmission step, a decoding step, and / or a displaying step; and A method comprising the step of performing monitoring for the above sub-picture-level HRD operation.

2. In paragraph 1, Further comprising a step of obtaining settings and / or policies related to HRD operations, A method in which the sub-picture-level HRD operation is performed based on settings and / or policies related to the HRD operation.

3. In paragraph 1 or 2, The steps for performing the above sub-picture-level HRD operation are: the above capturing step, and the above encoding step; and Including the transmission step for transmitting data to another User Equipment (UE) and / or network entity during or after performing the capturing step and the encoding step, A method wherein the decoding step and the displaying step are performed by the other UE and / or the network entity.

4. In any one of paragraphs 1 to 3, A method wherein the request message includes request information related to the performance of the sub-picture-level HRD and / or monitoring request information related to the sub-picture-level HRD.

5. In any one of paragraphs 1 to 4, The results of the above monitoring are: A method comprising one or more of the following: a start time of some or all of the steps included in the Sub-picture-level HRD operation, a time interval between the steps included in the Sub-picture-level HRD operation, and / or information related to the Quality of Experience (QoE) of the user.

6. In any one of paragraphs 1 to 5, A method further comprising the step of transmitting the results of said monitoring to one or more of another UE, a network entity, and / or a network entity related to said application.

7. In paragraph 6, A method further comprising the step of receiving settings and / or policies related to updated HRD operations from a network entity related to the application based on the results of the above monitoring.

8. In any one of paragraphs 1 to 7, A step of generating analysis information on the results of the above monitoring; and A method further comprising the step of transmitting the analysis information and / or the monitoring results to one or more of another UE, a network entity, and / or a network entity related to the application.

9. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A method wherein said one or more processors are adapted to perform a method according to any one of claims 1 to 8.

10. At least one processor; and At least one memory storing instructions and being operably electrically connected to the at least one processor, An operation performed based on the command being executed by the at least one processor: An apparatus comprising a method according to any one of claims 1 to 8.

11. A non-transitory computer readable medium (CRM) that records commands, A CRM comprising the steps of: said instructions, when executed by one or more processors, causing said one or more processors to perform a method according to any one of claims 1 to 8.

12. A step of transmitting a request message related to the sub-picture-level Hypothetical Reference Decoder (HRD) to the User Equipment (UE). The above request message is used to perform a sub-picture-level HRD operation including two or more steps among a capturing step, an encoding step, a transmission step, a decoding step, and / or a displaying step; and A method comprising the step of receiving the results of monitoring for the sub-picture-level HRD operation from the UE.

13. In paragraph 12, A method further comprising the step of transmitting settings and / or policies related to the HRD operation to the UE.

14. In paragraph 12 or 13, A method further comprising a step of determining whether to update settings and / or policies related to the HRD operation based on the results of the monitoring.

15. In any one of paragraphs 12 to 14, A method further comprising a step of updating settings and / or policies related to the HRD operation based on the results of the monitoring.

16. In paragraph 15, A method further comprising the step of transmitting updated settings and / or updated policies related to the HRD operation to the UE.

17. In paragraph 16, A method wherein the updated settings and / or updated policies related to the HRD operation include thresholds and / or requirements related to time intervals between steps included in the HRD operation.

18. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A method wherein said one or more processors are adapted to perform a method according to any one of claims 12 to 17.

Images