KR20240033937A - Method and apparatus of controlling traffic in wireless communication system - Google Patents

Abstract

This specification proposes a method and device for measuring data status in a wireless communication system. That is, we propose a method and device for receiving congestion-related information and measuring at least one of data rate, delay budget, delay difference, jitter, round trip delay, and congestion level based on the received congestion-related information.

Description

{Method and apparatus of controlling traffic in wireless communication system}

This specification relates to the 3GPP 5G NR system.

As more and more communication devices require larger communication traffic with the passage of time, the next-generation 5G system, which is an improved wireless broadband communication system than the existing LTE system, is required. In this next-generation 5G system, called NewRAT, communication scenarios are divided into Enhanced Mobile BroadBand (eMBB)/Ultra-reliability and low-latency communication (URLLC)/Massive Machine-Type Communications (mMTC).

Here, eMBB is a next-generation mobile communication scenario with characteristics such as High Spectrum Efficiency, High User Experienced Data Rate, and High Peak Data Rate, and URLLC is a next-generation mobile communication scenario with characteristics such as Ultra Reliable, Ultra Low Latency, and Ultra High Availability. (e.g., V2X, Emergency Service, Remote Control), mMTC is a next-generation mobile communication scenario with Low Cost, Low Energy, Short Packet, and Massive Connectivity characteristics. (e.g., IoT).

Meanwhile, XR (eXtended Reality) and CG (Cloud Gaming) are various types of augmented, virtual and mixed technologies in human-machine and human-human communication performed with the help of handheld and wearable devices. It is used as a broad term to mean the environment. Extended Reality (XR: eXtended Reality) is used as a broad term encompassing Augmented Reality (AR), Mixed Reality (MR), and Virtual Reality (VR). Cloud gaming represents a use case in which most computations related to gaming are offloaded from the terminal to an edge or remote server. XR applications along with cloud computing/gaming typically require high throughput and low latency.

Many XR and CG use cases require frequent uplink (e.g. pose/control updates) and/or quasi-periodic (with possible jitter) high data rates on the downlink video stream combined with the uplink video stream. ) is characterized by traffic. Both downlink and uplink traffic are characterized by a relatively tight packet delay budget (PDB). Many XR and CG devices have limited battery power. However, the current DRX configuration is not suitable due to the non-integer XR traffic cycle, variable XR data rate, and quasi-periodic XR cycle.

The XR and CG service sets are diverse. Data streams (e.g. video) can change on the fly while the service is running over a wireless network (e.g. NR).

Packets within one frame may have dependencies on each other. The application may require all packets that make up the frame to decode the frame. Loss of one packet can render other correlated packets useless even if they were transmitted successfully. For example, XR applications may impose requirements in terms of Application Data Units (ADUs)/media units rather than single packets/PDUs. Packets from the same video stream, but within different frame types (I/P frames) or Group of Pictures (GoPs) or even in different locations/areas within a video frame, can have different contributions to the user experience. Therefore, layered QoS handling within the video stream can relax requirements and lead to higher efficiency.

If additional information from the upper/application layer can be utilized about the running service/application, it may be useful to facilitate wireless parameter selection. However, there is no specific method provided to effectively recognize and process the characteristics of XR application traffic in the terminal/base station/core network.

To enable media codec/rate adaptation of XR applications, the 5GS system must be able to transmit congestion-related information to the application server/application function/application. However, a specific operation method for this is not provided in a wireless network.

Accordingly, the purpose of the disclosure of this specification is to propose an operating method and device for providing congestion-related information in a wireless network to solve the above-mentioned problems.

This specification proposes a method and device for measuring data status in a wireless communication system. That is, we propose a method and device for receiving congestion-related information and measuring at least one of data rate, delay budget, delay difference, jitter, round trip delay, and congestion level based on the received congestion-related information.

This specification targets the 5G/5G-advanced system defined in 3GPP, but the technology/concept proposed in this specification can be applied to mobile communication systems other than 5G, such as LTE or 6G to be defined in the future.

According to the disclosure of this specification, there is an effect of supporting codec/data rate adaptation of XR/media applications through signaling linked in the wireless network/base station/gNB-DU/gNB-CU in a wireless mobile communication system.

Figure 1 illustrates the structure of a radio frame used in NR.
Figure 2 shows an example of a structure for representing 5G-XR functionality within a 5G system.
Figure 3 shows the overall structure of NG-RAN in the 5G system.
Figure 4 shows a block diagram of a processor on which the disclosure of the present specification is implemented.
Figure 5 shows a wireless communication device according to an embodiment of the present specification.
Figure 6 illustrates a block diagram of a communication device according to an embodiment of the present specification.

Although this specification describes embodiments using an LTE system, an LTE-A system, and an NR system, these embodiments may be applied to any communication system that falls within the above definition.

In addition, in this specification, the name of the base station may be used as a comprehensive term including remote radio head (RRH), eNB, transmission point (TP), reception point (RP), relay, etc.

The 3GPP-based communication standard includes downlink physical channels corresponding to resource elements that carry information originating from the upper layer, and downlink physical channels corresponding to resource elements that are used by the physical layer but do not carry information originating from the upper layer. Physical signals are defined. For example, a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), a physical multicast channel (PMCH), and a physical control format indicator channel (physical control). format indicator channel (PCFICH), physical downlink control channel (PDCCH), and physical hybrid ARQ indicator channel (PHICH) are defined as downlink physical channels, and reference signals and synchronization signals are defined as downlink physical signals. A reference signal (RS), also called a pilot, refers to a signal with a predefined special waveform known to both the gNB and the UE, for example, cell specific RS (cell specific RS), UE- UE-specific RS (UE-RS), positioning RS (PRS), and channel state information RS (CSI-RS) are defined as downlink reference signals. The 3GPP LTE/LTE-A standard corresponds to uplink physical channels corresponding to resource elements carrying information originating from upper layers, and resource elements used by the physical layer but not carrying information originating from upper layers. Uplink physical signals are defined. For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are used as uplink physical channels. A demodulation reference signal (DMRS) for uplink control/data signals and a sounding reference signal (SRS) used for uplink channel measurement are defined.

In this specification, PDCCH (Physical Downlink Control CHannel) / PCFICH (Physical Control Format Indicator CHannel) / PHICH ((Physical Hybrid automatic retransmit request Indicator CHannel) / PDSCH (Physical Downlink Shared CHannel) are respectively DCI (Downlink Control Information) / CFI ( Control Format Indicator)/Downlink ACK/NACK (ACKnowlegement/Negative ACK)/Refers to a set of time-frequency resources or a set of resource elements carrying downlink data. Also, PUCCH (Physical Uplink Control CHannel)/PUSCH (Physical Uplink Shared CHannel)/PRACH (Physical Random Access CHannel) refers to a set of time-frequency resources or a set of resource elements that carry UCI (Uplink Control Information)/uplink data/random access signal, respectively.

Below, a control method based on 5GS/NR technology is described. However, this is for convenience of explanation and the present invention can be applied to any system/wireless access technology (e.g. LTE, 6G). The embodiment described in the present invention includes the information elements and operations specified in the NR/5GS standard (e.g. TS 38.321, a MAC standard, TS 38.331, a NR RRC standard, TS 23.501, a system architecture standard, etc.). Even if the definition of the corresponding information element and the related terminal operation content are not included in this specification, the corresponding content specified in the standard specification, which is a known technology, may be included in the present invention.

Any function described below is defined as an individual terminal capability (UE radio capability or UE Core network capability) and can be transmitted by the terminal to the base station/core network entity (e.g. AMF/SMF) through corresponding signaling. . Alternatively, arbitrary functions may be combined/combined, defined as the terminal capability, and transmitted by the terminal to the base station/core network entity through corresponding signaling.

The base station may transmit/instruct to the terminal through an RRC message information indicating permission/support/configuration of the function/function combination for any function or combination of functions described below. For example, this can be instructed to the terminal before or after configuration/application of the function/function combination, or simultaneously with configuration/application of the function/function combination. The RRC message can be broadcast through system information. Alternatively, it may be indicated to the terminal through a dedicated RRC message.

For convenience of explanation, units divided by application/application layer, or units divided within an application, or units with correlation between data/streams/packets within one application, or within one application. Units with dependencies between data/streams/packets, units distinguished with different traffic characteristics/streams within one flow, units distinguished with different traffic characteristics/streams within one PDU session, included in the application/ Units classified based on arbitrary information/fields/metadata used/added, and PDUs carrying the payload of one unit of information generated at the application level are denoted as PDU Set. This is only for convenience of explanation, and includes ADU (Application Data Unit), MU (media unit), Application packet data unit, GoP (Group of Picture) unit, traffic type (e.g. XR viewer pose information unit, tactile information, video, audio, degree of freedom) can be replaced with any other term such as specific unit, frame type, stream type, a group of packets, PDU group, etc.

One PDU Set consists of one or more PDUs that carry one unit of information generated at the application level as a payload, and the PDUs have the same importance requirements at the application layer. All PDUs in one PDU Set may or may not be required to use the corresponding unit information by the application layer. (A PDU Set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice for XRM Services) In some implementations all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover parts or all of the information unit, when some PDUs are missing) Information to indicate presence may be transmitted from the application layer/application server/application function/terminal to the base station. For example, it can be transmitted from the application server/application function to the base station through the core network through control plane signaling. Or, when transmitted from the application server to the UPF on the user plane and from the UPF to the base station, it will be included and transmitted in any header (e.g. GTP-U header, header containing PDU-Set related information) carrying the data. You can. The base station can instruct the terminal to classify the relevant data and transmit it to the base station by instructing the terminal to provide relevant information or data. Alternatively, the terminal may transmit related information to the base station through RRC signaling.

The functions described below can be performed individually and independently. It is obvious that the functions described below can be implemented in any combination/combination and that this is also included in the scope of the present invention. For example, more than one function may be applied simultaneously.

Random information on XR applications described below includes traffic characteristic information statistically/empirically obtained/calculated/derived from the terminal/network (e.g. random statistics/average, deviation, standard deviation, minimum, maximum, etc.) It can be a statistic). Accordingly, any information included in this specification may represent one or more of the following values: average (expected value)/minimum/maximum/standard deviation value. For example, if update rate information is included, this may mean the average (expected)/minimum/maximum/standard deviation values of the update rate. This is for convenience of explanation, and all information in this specification may be used as statistical information. Alternatively, it may be information pre-configured in the terminal/network or provisioned through OAM/application server/application function/UDM.

Figure 1 illustrates the structure of a radio frame used in NR.

In NR, uplink and downlink transmission consists of frames. A wireless frame is 10ms long and is defined as two 5ms half-frames (HF). A half-frame is defined as five 1ms subframes (Subframe, SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on SCS (Subcarrier Spacing). Each slot contains 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP). Normally when CP is used, each slot contains 14 symbols. When extended CP is used, each slot contains 12 symbols. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol) and an SC-FDMA symbol (or DFT-s-OFDM symbol).

Table 1 illustrates that when a normal CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

SCS(15* ^2u ) N- ^slot _symbol N ^{frame, u} _slot N ^{subframe, u} _slot 15 KHz (u = 0) 14 10 One 30 KHz (u = 1) 14 20 2 60 KHz (u = 2) 14 40 4 120 KHz (u =3) 14 80 8 240 KHz (u =4) 14 160 16

N ^slot _symb : Number of symbols in slot

N ^frame,u _slot : Number of slots in the frame

N ^subframe,u _slot : Number of slots in the subframe

Table 2 illustrates that when an extended CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

SCS (15* ^2u ) N- ^slot _symbol N ^{frame, u} _slot N ^subframe,u _slot 60KHz (u=2) 12 40 4

In the NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells merged into one UE. Accordingly, the (absolute time) interval of time resources (e.g., SF, slot, or TTI) (for convenience, collectively referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between merged cells.

Figure 2 shows an example of a structure for representing 5G-XR functionality within a 5G system.

Referring to Figure 2, 5G-XR AF represents an application function for 5G-XR service. 5G-XR AS represents an application server for 5G-XR services. 5G-XR Client represents terminal internal functions for 5G-XR service. Within the terminal, the XR client can represent the transceiver of the XR session accessed through APIs, etc. by the XR application. The XR client may perform communication/signaling with 5G-XR AF to establish/control/support an XR session (or delivery of an XR session). XR clients can access XR data and communicate with the 5G-XR AS to process that data. 5G-XR AF provides various control functions for processing XR sessions on the terminal, and can perform PCF/NEF and signaling for QoS control, etc. 5G-XR AS represents an application server that hosts 5G XR media and media functions.

Meanwhile, the XR application server/application function/application can adapt the media codec/traffic rate to adapt to network conditions and ensure the required experience for users. To enable media codec/rate adaptation of the application, the 5GS system may consider transmitting the information to the application server/application function. However, currently, no specific method for this is provided.

Figure 3 shows the overall structure of NG-RAN in the 5G system.

High layer functional split/base station split structure

To support efficient network construction, NR divides the base station (gNB) into centralized nodes (hereinafter referred to as gNB-CU/CU for convenience of explanation) and distributed nodes (hereinafter referred to as gNB-DU/DU for convenience). Provides a base station separation structure that separates the base station. Referring to Figure 3, the next-generation wireless network consists of one set of base stations connected to 5GC (5G Core network) through an NG interface. Base stations are interconnected through the Xn interface. One base station may consist of one gNB-CU and one or more gNB-DU. gNB-CU and gNB-DU are connected through the F1 interface. One gNB-DU can be connected to only one gNB-CU. The NG interface and Xn-C interface for one base station consisting of gNB-CU and gNB-DU are terminated at gNB-CU. gNB-DUs connected to gNB-CU are seen as only one base station to other base stations and 5GC. The gNB-CU is a logical node that hosts the base station's RRC, SDAP, and PDCP protocols. The gNB-DU is a logical node that hosts the RLC, MAC, and PHY layers of the base station. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU.

Below, a control method based on 5GS/NR technology is described. However, this is for convenience of explanation and the present invention can be applied to any system/wireless access technology (e.g. LTE, 6G). The embodiment described in the present invention includes information elements and operations specified in the NR/5GS standard (e.g. TS 38.321, a MAC standard, TS 38.331, a NR RRC standard, TS 38.401, a wireless network architecture standard, TS 23.501, a system architecture standard, etc.) Includes the contents of Even if the definition of the corresponding information element and the related terminal operation content are not included in this specification, the corresponding content specified in the standard specification, which is a known technology, may be included in the present invention.

Any function described below is defined as an individual terminal capability (UE radio capability or UE Core network capability) and can be transmitted by the terminal to the base station/core network entity (e.g. AMF/SMF) through corresponding signaling. . Alternatively, arbitrary functions may be combined/combined, defined as the terminal capability, and transmitted by the terminal to the base station/core network entity through corresponding signaling.

The base station may transmit/instruct to the terminal through an RRC message information indicating permission/support/configuration of the function/function combination for any function or combination of functions described below. For example, this can be instructed to the terminal before or after configuration/application of the function/function combination, or simultaneously with configuration/application of the function/function combination. The RRC message can be broadcast through system information. Alternatively, it may be indicated to the terminal through a dedicated RRC message.

For convenience of explanation, units divided by application/application layer, or units divided within an application, or units with correlation between data/streams/packets within one application, or within one application. Units with dependencies between data/streams/packets, units distinguished with different traffic characteristics/streams within one flow, units distinguished with different traffic characteristics/streams within one PDU session, included in the application/ Units classified based on arbitrary information/fields/metadata used/added, and PDUs carrying the payload of one unit of information generated at the application level are denoted as PDU Set. This is only for convenience of explanation, and includes ADU (Application Data Unit), MU (media unit), Application packet data unit, GoP (Group of Picture) unit, traffic type (e.g. XR viewer pose information unit, tactile information, video, audio, degree of freedom) can be replaced with any other term such as specific unit, frame type, stream type, a group of packets, PDU group, etc.

One PDU Set consists of one or more PDUs that carry one unit of information generated at the application level as a payload, and the PDUs have the same importance requirements at the application layer. All PDUs in one PDU Set may or may not be required to use the corresponding unit information by the application layer. (A PDU Set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice for XRM Services) In some implementations all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover parts or all of the information unit, when some PDUs are missing) Information to indicate presence may be transmitted from the application layer/application server/application function/terminal to the base station. For example, it can be transmitted from the application server/application function to the base station through the core network through control plane signaling. Or, when transmitted from the application server to the UPF on the user plane and from the UPF to the base station, it may be transmitted and included in any header (e.g. GTP-U header, header containing PDU-Set related information) carrying the data. You can. The base station can instruct the terminal to classify the relevant data and transmit it to the base station by instructing the terminal to provide relevant information or data. Alternatively, the terminal may provide assistance/related information (e.g. preferred bit rate, preferred frame rate, preferred delay, preferred) to receive the configuration through RRC/MAC signaling (e.g. UE assistance information, random UL information, capability signaling, MAC CE). jitter, preferred PDU-Set delay, preferred PDU-Set error rate) can be transmitted to the base station. The terminal can receive the configuration from the base station and apply it. The terminal includes PDU-Set related information (or information to distinguish PDU-Set) on one or more L2 headers (e.g. MAC (e.g. LCID), RLC (LCID), PDCP, SDAP) for the data and sends it to the base station. It can be sent to .

The functions described below can be performed individually and independently. It is obvious that the functions described below can be implemented in any combination/combination and that this is also included in the scope of the present invention. For example, more than one function may be applied simultaneously.

Random information on XR applications described below includes traffic characteristic information statistically/empirically obtained/calculated/derived from the terminal/network (e.g. random statistics/average, deviation, standard deviation, minimum, maximum, etc.) It can be a statistic). Accordingly, any information included in this specification may represent one or more of the following values: average (expected value)/minimum/maximum/standard deviation value. For example, if update rate information is included, this may mean the average (expected)/minimum/maximum/standard deviation values of the update rate. This is for convenience of explanation, and any information in this specification may be used as statistical information. Alternatively, it may be information pre-configured in the terminal/network or provisioned through OAM/application server/application function/UDM.

To enable media codec/rate adaptation/adjustment of XR applications, the 5GS system can transmit congestion-related information to the application server/application function/terminal. For example, congestion-related information can be provided using ECN (Explicit Congestion Notification) marking based on L4S (Low Latency, Low Loss, Scalable Throughput) for uplink and downlink. Alternatively, the 5G system can externally link congestion-related information to AF based on API. Alternatively, the 5G system can mark this in the header on any/random layer used for the payload on the user plane and transmit it to the application server/terminal.

5G systems can use Explicit Congestion Notification (ECN) marking for uplink and/or downlink QoS flows through one of the following methods:

As an example, to support L4S, a base station (NG-RAN) may perform ECN marking on the uplink/downlink at the IP layer of the received packet.

As another example, the PDU Session Anchor (PSA) UPF performs ECN marking on the uplink/downlink based on the current congestion level information reported through the GTP-U header from the base station (or any relevant indication received from the base station). can do.

The 5G system can support exposure of API-based congestion level information as an application function. Information exposed may include the following information.

- QoS Notification Control/Monitoring/Measurement/Reporting for GBR QoS flow where data rate cannot be guaranteed

- (for non-GBR QoS-flow/QoS-sub-flow/PDU-Set and/or GBR QoS flow/QoS-sub-flow/PDU-Set, or directed/specific QoS-flow/QoS-sub- QoS notification control/monitoring/measurement/reporting for QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s) whose QoS profile/parameters cannot be fulfilled (for flow/PDU-Set)

- Application functions can subscribe to receive information on exposure to NEF/PCF.

- Exposure path of RAN/UPF reporting congestion level information via SMF/PCF/NEF

In any of the above-mentioned methods, information transmitted from the base station to the UPF/terminal/application or information exposed/transmitted from the base station to the application server/application function/application through the core network (e.g. via SMF, PCF, NEF) may include one or more information of data rate, delay budget, delay difference, jitter, round trip delay, and congestion level monitored/measured/calculated/generated at the base station.

QoS Notification Control/Monitoring/Measurement/Reporting Instruction/Request/Configuration for media codec/data rate adaptation from CU to DU

During the PDU session setup/modification procedure, the SMF may indicate QoS notification control/monitoring/measurement/reporting parameters to the base station (gNB-CU). For example, it can be transmitted by including it as part of the corresponding QoS profile/parameters/characteristics. The corresponding QoS notification control/monitoring/measurement/reporting parameters can be indicated in connection with the flow/sub-flow/PDU-Set of the XR/media application. The corresponding QoS notification control/monitoring/measurement/reporting parameters may include PDU-Set QoS profile/parameters/characteristics. The QoS notification control/monitoring/measurement/reporting parameters may include information to be notified/monitored/measured/reported by the base station (e.g. data rate, delay budget, delay difference, jitter, round trip delay, congestion level). The corresponding QoS notification control/monitoring/measurement/reporting parameters may include information for calculating information to be notified/monitored/measured by the base station. The corresponding QoS notification control/monitoring/measurement/reporting parameter may include information for instructing the corresponding QoS notification control/monitoring/measurement/reporting. The corresponding QoS notification control/monitoring/measurement/reporting parameters are the requested (alternative) QoS profile/parameter/characteristic set (e.g. PDU-Set delay budget, PDU-Set error rate, PDU-Set priority/importance, 5QI, ARP, data rate, flow/sub-flow/PDU-Set bit rates (maximum flow/sub-flow/PDU-Set bit rate, guaranteed flow/sub-flow/PDU-Set bit rate), aggregate bit rates (corresponding PUD-Session/ QoS-flows/QoS-subflows/PDU-Sets aggregate maximum bit rate), averaging time window, frame rate of XR/media, data burst generation cycle, data burst size, etc.) and/or to identify them. It may include information and/or a bitmap to indicate it. The QoS notification control/monitoring/measurement/reporting parameters may include information to indicate ECN bit marking for the corresponding QoS-flow/QoS-sub-flow/QoS-PDU-Set (at the base station). This information includes specific QoS profiles/parameters/characteristics (e.g. PDU-Set delay budget, PDU-Set error rate, PDU-Set priority/importance, 5QI, ARP, data rate, flow/sub-flow/PDU-Set bit rates ( maximum flow/sub-flow/PDU-Set bit rate, guaranteed flow/sub-flow/PDU-Set bit rate), aggregate bit rates (corresponding PUD-Session/QoS-flows/QoS-subflows/PDU-Sets aggregate maximum bit rate), averaging time window, frame rate of XR/media, data burst generation period, and data burst size) may be indicated using predefined/specified values. Alternatively, the information may be indicated by defining explicit instruction information.

The information to be controlled/monitored/measured/reported by the base station is the Qos-flow-identifier for the PDU session and/or the QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s). /QoS-sub-flow-identifier/PDU-Set-identifier, notification cause (e.g. fulfilled, not fulfilled), not fulfilled QoS profile/parameter/characteristic, current QoS parameters set index, congestion level. there is. The information to be notified/monitored/measured/reported by the base station is the QoS-flow-id/QoS-sub-flow-id/PDU-Set-id list and the corresponding QoS-flow/QoS-sub-flow/ for measuring the delay difference. PDU-Set may include information to identify the group/set to identify/classify the group/set.

The information to be notified/monitored/measured/reported by the base station is the uplink/downlink data rate (or available/measured) for the corresponding QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s) measured/observed wireless network transmission rate), uplink/downlink delay budget (or available/measured/observed wireless network delay budget), multiple (or two) QoS-flow(s)/QoS-sub -Uplink/downlink/round-trip delay difference (or available/measured/observed radio network delay difference) for flow(s)/PDU-Set(s), uplink/downlink jitter (or available /measured/observed wireless network jitter), round trip delay (or available/measured/observed wireless network round trip delay), timestamp/absolute time/UTC time/local time (of the node in question). May contain information. QoS-sub-flow(s)/PDU-Set(s) will be described later.

The parameters for calculating information to be notified/monitored/measured/reported by the base station are the number of steps and step size/range/level for the corresponding codec rate and/or associated data rate for the corresponding XR application/media codec/data rate adaptation. Information, information to classify/identify the step number and step size/range/level by coding, time window/duration/unit time/period information to calculate the corresponding data rate, notification cycle, notification event, notification threshold , It may include one or more information among the threshold value for the notification QoS profile/parameter/characteristic set, information for classifying/identifying the threshold value by coding it, and the number of congestion level steps.

For QoS notification control/monitoring/measurement/reporting at the base station, the gNB-CU may indicate/configure/modify/request/response/confirm one or more of the above-described information to the gNB-DU. The gNB-DU may indicate/configure/modify/request/response/confirm one or more of the above-described information to the gNB-CU. For example, the gNB-CU may include one or more of the above-described information in a UE context setup request/modification message and transmit it to the gNB-DU.

The gNB-CU may include one or more of the above-described information in a UE context setup request/modification message and transmit it to the gNB-DU.

As an example, the gNB-CU may include (corresponding DRB (e.g. DRB ID)) the DRB list information to be set up/modified (DRB to Be Setup List IE / DRB to Be Modified List IE) included in the terminal context setup request/modification message. If the information (Notification Control IE) for instructing notification control (linked to The gNB-CU can be notified/reported. This can be applied to GBR bearers and/or non-GBR bearers. For example, it can be applied to GBR bearers and/or non-GBR bearers mapped/linked to flow/sub-flow/PDU-Set of XR/media application.

As another example, the gNB-CU may include (corresponding DRB (e.g. DRB ID)) the DRB list information to be set up/modified (DRB to Be Setup List IE / DRB to Be Modified List IE) included in the terminal context setup request/modification message. If information to instruct/request QoS notification control/monitoring/measurement/reporting (linked to Whether the profile/parameter/characteristic can no longer be implemented or whether the corresponding QoS profile/parameter/characteristic can be implemented again, the corresponding QoS profile/parameter/characteristic measurement results, the corresponding data rate, delay difference, jitter, round trip delay One or more information can be notified/reported to the gNB-CU. This can be applied to GBR bearers and/or non-GBR bearers. For example, it can be applied to GBR bearers and/or non-GBR bearers mapped/linked to flow/sub-flow/PDU-Set of XR/media application.

As another example, the gNB-CU may include (corresponding DRB (e.g. DRB ID)) the DRB list information to be set up/modified (DRB to Be Setup List IE / DRB to Be Modified List IE) included in the terminal context setup request/modification message. (each) QoS-flow-id/QoS-sub-flow-id/PDU-Set- for (each) QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s) linked to id, and may include QoS profile/parameter/characteristic information for the corresponding QoS-flow-id/QoS-sub-flow-id/PDU-Set-id.

As another example, the gNB-CU may include (corresponding DRB (e.g. DRB ID)) the DRB list information to be set up/modified (DRB to Be Setup List IE / DRB to Be Modified List IE) included in the terminal context setup request/modification message. It may include traffic characteristic information about QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s) (linked to). For example, the direction (uplink/downlink/bidirectional), cycle, size, Arrival time, jitter, (preferred terminal) frame rate/data rate, preferred frame rate/data rate received by subscription information or from AF, corresponding QoS-flows/QoS-sub (grouped in association with multimodal) -Delay differences between flows/PDU-Sets, and/or thresholds for any of the aforementioned parameters, corresponding QoS-flow(s)/QoS-sub-flow(s)/PDU- measured/directed at the gNB-CU Direction (uplink/downlink/bidirectional), period, size, arrival time, jitter, (preferred terminal) frame rate/data rate for Set(s), preferred frame rate received by subscription information or from AF. /data rate, delay difference between corresponding QoS-flows/QoS-sub-flows/PDU-Sets (grouped in association with multimodal), and/or thresholds for any of the foregoing parameters. You can.

As another example, the gNB-CU may include (corresponding DRB (e.g. DRB ID)) the DRB list information to be set up/modified (DRB to Be Setup List IE / DRB to Be Modified List IE) included in the terminal context setup request/modification message. (linked to) Set the information to instruct/request QoS notification control/monitoring/measurement/reporting for QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s) to the corresponding value. If included, gNB-DU monitors/measures the QoS profile/parameters/characteristics of the corresponding QoS-flow/QoS-sub-flow/PDU-Set, and determines the QoS of the corresponding QoS-flow/QoS-sub-flow/PDU-Set. Whether the profile/parameters/characteristics of the corresponding QoS-flow/QoS-sub-flow/PDU-Set can no longer be fulfilled or the QoS profile/parameters/characteristics of the corresponding QoS-flow/QoS-sub-flow/PDU-Set can be fulfilled again. QoS profile/parameter/characteristic measurement results of flow/PDU-Set, data rate of corresponding QoS-flow/QoS-sub-flow/PDU-Set, corresponding QoS-flows/QoS-sub (grouped in connection with multimodal) - Information on one or more of the following: delay difference between flows/PDU-Sets, jitter of the corresponding QoS-flow/QoS-sub-flow/PDU-Set, round trip delay of the corresponding QoS-flow/QoS-sub-flow/PDU-Set Can notify/report to gNB-CU. This may apply to GBR bearers and/or non-GBR bearers. For example, it can be applied to GBR bearers and/or non-GBR bearers mapped/linked to flow/sub-flow/PDU-Set of XR/media application.

Delivery of QoS notification control/monitoring/measurement results/reporting for media codec/data rate adaptation/adjustment from DU to CU

gNB-DU is connected to (already) set DRB linked to QoS notification control/monitoring/measurement/reporting (or QoS-flow(s)/QoS-sub-flow(s)/PDU-Set( s), whether the QoS profile/parameters/characteristics are no longer implemented or whether they are implemented again, the QoS profile/parameters/characteristics measurement results of the corresponding QoS-flow/QoS-sub-flow/PDU-Set, the corresponding QoS-flow The data rate of the QoS-sub-flow/PDU-Set, the delay difference between the corresponding QoS-flows/QoS-sub-flows/PDU-Sets, the jitter of the corresponding QoS-flow/QoS-sub-flow/PDU-Set, the corresponding A message for notifying/reporting one or more information among the round trip delays of QoS-flow/QoS-sub-flow/PDU-Set can be transmitted to the gNB-CU. The gNB-DU hosts MAC and RLC. Therefore, MAC Measure/calculate the data rate based on the data burst processed at the RLC layer through scheduling, measure/calculate the delay of the wireless interface/wireless network between the terminal and the base station/gNB-DU/gNB-CU, and detect wireless congestion status. It can be performed and notified/reported.

As an example, the gNB-DU is no longer guaranteed a guaranteed flow bit rate (GFBR) for the corresponding PDU session and/or the corresponding QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s). When not, the corresponding notification/reporting information can be transmitted to the gNB-DU when GFBR is guaranteed again.

As another example, the gNB-DU provides available/measured/observed/indicated data for the corresponding PDU session and/or the corresponding QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s). When the rate/frame rate is no longer provided/available, the corresponding notification/reporting information is sent to the gNB-DU when the available/measured/observed/indicated data rate/frame rate becomes available/available again. It can be sent to .

As another example, the gNB-DU may determine the available/measured/observed/indicated QoS for the corresponding PDU session and/or the corresponding QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s). Profile/parameters/characteristics (e.g. PDU-Set delay budget, PDU-Set error rate, PDU-Set jitter, delay difference between corresponding QoS-flows/QoS-sub-flows/PDU-Sets, corresponding QoS-flow/QoS-sub When the jitter of a -flow/PDU-Set, one or more of the round trip delays of the corresponding QoS-flow/QoS-sub-flow/PDU-Set) is no longer provided/guaranteed/available (or when the corresponding threshold is changed) exceeds), or when it becomes available/guaranteed/available again (or within the corresponding threshold), the corresponding notification/reporting information may be transmitted to the gNB-DU.

As another example, the gNB-DU may implement a PDU-Set QoS/Profile that it can implement for that PDU session and/or that QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s). /parameters/characteristics (e.g. PDU-Set delay budget, PDU-Set error rate, PDU-Set jitter. Delay difference between corresponding QoS-flows/QoS-sub-flows/PDU-Sets, corresponding QoS-flow/QoS-sub- jitter of the flow/PDU-Set, round trip delay of the corresponding QoS-flow/QoS-sub-flow/PDU-Set, etc.) are indicated/replaced/added taking into account the (priority) order. You can check whether it matches at least one of the QoS profiles/parameters/characteristics. If there is a match between one of the corresponding QoS profiles/parameters/characteristics and the QoS-flow/QoS-sub-flow/PDU-Set QoS profile/parameters/characteristics that the gNB-DU can implement, the gNB-DU is flow(s)/QoS-sub-flow(s)/PDU-Set(s) can be accepted. And the reference/index for the corresponding QoS profile/parameter/characteristic can be indicated to the gNB-CU (or to the SMF through the gNB-CU). If there is no match, the gNB-DU may reject the corresponding QoS-flow(s)/QoS-sub-flow(s)/PDU-Set(s) setting/modification.

Delivery of QoS notification control/monitoring/measurement results/reporting for media codec/data rate adaptation/adjustment from CU to core network (e.g. SMF/PCF/NEF, UPF)

When delivery of the corresponding notification/reporting information is triggered in the wireless network (e.g. congestion detection, QoS profile/parameter/characteristic transition detection, indicated event detection, cycle arrival, gNB-CU receives corresponding notification/reporting information from gNB-DU), The gNB-CU/base station can transmit the information to the application function/application server/application through SMF/PCF/NEF using a message for transmitting/notifying/reporting the information. The message for the gNB-CU/base station to transmit/notify/report the information may include any information transmitted by the above-described gNB-DU to the gNB-CU.

As another example, the gNB-CU/base station can transmit UPF by including the corresponding information on the corresponding uplink data header (e.g. GTP-U header, IP header). UPF can transmit the information to the application function/application server/application. The information may include arbitrary information transmitted from the above-described gNB-DU to the gNB-CU. During PDU session setup/modification, information to indicate this may be transmitted to the UPF by the SMF.

As another example, the base station/gNB-CU may mark the ECN bit in the IP layer for uplink/downlink data (e.g. IP packet) based on information received from SMF/UPF/gNB-DU. Alternatively, the base station/gNB-CU may send congestion information (or the aforementioned QoS notification control/monitoring/measurement result) on the GTP-U header of the uplink data (e.g. IP packet) based on the information received from the SMF/UPF/gNB-DU. /Information to link/instruct arbitrary information for reporting) can be included/marked and transmitted to UPF. UPF can mark the ECN bit at the IP layer for the corresponding uplink data (e.g. IP packet). Alternatively, the base station/gNB-CU may mark the ECN bit on the outer IP header including the GTP-U header of the uplink data (e.g. IP packet) based on the information received from the SMF/UPF/gNB-DU. You can. UPF can mark the ECN bit at the IP layer for the corresponding uplink data (e.g. IP packet). Alternatively, the base station/gNB-CU may mark the ECN bit in the IP layer for downlink data (e.g. IP packet) based on information received from SMF/UPF/gNB-DU. The base station/gNB-CU provides the aforementioned QoS notification within the sub-L2 layer (e.g. SDAP/PDCP/RLC/MAC) header that encapsulates downlink data (e.g. IP packet) based on the information received from SMF/UPF/gNB-DU. Information to link/instruct arbitrary information for control/monitoring/measurement results/reporting can be marked.

The application layer of a terminal that supports L4S can provide feedback based on the ECN mark received for L4S. An application server/application function/application that supports L4S can perform codec adaptation.

QoS notification control/monitoring/measurement/reporting related operations

The base station/gNB-CU can perform QoS notification control/monitoring/measurement/reporting for QoS-flow/QoS-sub-flow/PDU-Set based on information received from SMF/UPF/gNB-DU/UE. there is. The base station/gNB-DU can perform QoS notification control/monitoring/measurement/reporting for QoS-flow/QoS-sub-flow/PDU-Set based on information received from SMF/UPF/gNB-CU/UE. there is.

As an example, the base station/gNB-CU/gNB-DU uses uplink/downlink for QoS-flow/QoS-sub-flow/PDU-Set based on information received from SMF/UPF/gNB-DU/gNB-CU. Packet/PDU-Set delay can be measured.

As another example, the base station/gNB-CU/gNB-DU configures two (or multiple) QoS-flows/QoS for multimodal XR/media applications based on information received from SMF/UPF/gNB-DU/gNB-CU. -Uplink/downlink delay difference for sub-flows/PDU-Sets can be measured. For this purpose, the QoS-flow-id/QoS-sub-flow-id/PDU-Set-id list included in the group/set for measuring the delay difference and the corresponding QoS-flow/QoS-sub-flow/PDU-Set group A group/set identifier for identifying/distinguishing a set may be indicated from the SMF to the base station/gNB-CU/gNB-DU.

As another example, when the base station/gNB-CU/gNB-DU receives arbitrary information to indicate QoS notification control/monitoring/measurement result/reporting for the corresponding QoS-flow/QoS-sub-flow/PDU-Set, You can save it. And operations for QoS notification control/monitoring/measurement results/reporting can be performed.

As another example, the base station/gNB-CU/gNB-DU and UPF have a PDU-Set delay budget for the corresponding PDU-Set (e.g. an upper bound for the time that a PDU-Set may be delayed between the UE and the N6 termination point at the UPF), PDU-Set jitter (e.g. delay difference between two PDU-Sets with consecutive sequence numbers with one PDU-Set identifier, or two PDU-Sets with consecutive sequence numbers with one PDU-Set identifier). For a Set, the difference between the delay between the first/last PDU of the preceding sequence number PDU-Set and the first/last PDU of the succeeding sequence number PDU-Set, or two PDU-Sets with consecutive sequence numbers having one PDU-Set identifier. (difference between the delay between the last PDU of the preceding sequence number PDU-Set and the first PDU of the subsequent sequence number PDU-Set), round trip time for that PDU-Set (e.g. having one PDU-Set identifier, or associated For an uplink PDU-Set that has a PDU-Set identifier, or that follows a downlink PDU-Set, the delay time between the terminal and the N6 endpoint in the UPF for the downlink PDU-Set and the terminal and the UPF for the uplink PDU-Set The upper limit on the delay time between the UPF and N6 endpoints, or double the upper limit on the delay time between the terminal and the UPF and N6 endpoints for a downlink PDU-Set, or the upper limit on the delay time between the terminal and the UPF and N6 endpoints for an uplink PDU-Set. can be measured/calculated (double the upper limit for the delay time between endpoints).

As another example, when UPF (or PSA UPF) receives the first packet of the corresponding PDU-Set or transmits (to the base station) the first downlink packet/PDU/monitoring packet of the corresponding PDU-Set, the corresponding QFI/sub-QFI/PDU-Set-ID, information to indicate QoS monitoring (or information to indicate UL/DL packet delay or round-trip time measurement, information to indicate congestion control, QoS Notification) It can be encapsulated with one or more of information for (or arbitrary information for the above-mentioned QoS notification control/monitoring/measurement results/reporting) and local time T1.

The base station can record the local time T1 received within the GTP-U header and the local time T2 when receiving the corresponding packet/PDU/monitoring packet.

When the UPF (or PSA UPF) receives the last packet of the corresponding PDU-Set or transmits (to the base station) the last downlink packet/PDU/monitoring packet of the corresponding PDU-Set, the corresponding QFI/ sub-QFI/PDU-Set-ID, information for directing QoS monitoring (or information for directing UL/DL packet delay or round trip time measurement, information for directing congestion control, QoS Notification) Information, or arbitrary information for the aforementioned QoS notification control/monitoring/measurement results/reporting), and local time T21 may be encapsulated with one or more information.

The base station can record the local time T21 received within the GTP-U header and the local time T22 when receiving the corresponding packet/PDU/monitoring packet.

The base station receives uplink confirmation information (e.g. HARQ Ack/Nak, RLC Ack/NaK)/packet/PDU/monitoring packet (or uplink linked to the downlink QFI/sub-QFI/PDU-Set-ID) from the terminal. When receiving an uplink packet/PDU/monitoring packet for QFI/sub-QFI/PDU-Set-ID), the uplink packet/PDU/monitoring packet that the base station transmits to the UPF through the N3 interface is the GTP-U header. QFI/sub-QFI/PDU-Set-ID, information for instructing QoS monitoring (response/notification) (or information for instructing UL/DL packet delay or round-trip time measurement (response/notification), Information for instructing congestion control (response/notification), information for instructing QoS Notification, or arbitrary information for the aforementioned QoS notification control/monitoring/measurement results/reporting), wireless network round trip time, wireless network up Link/downlink packet delay results, local time T1, local time T2, local time T21, local time T22, local time T3, when the base station transmits the uplink packet/PDU/monitoring packet to UPF through N3 interface, the base station corresponds to When receiving the last packet of the PDU-Set, receiving the corresponding uplink packet/PDU/monitoring packet from the terminal, and transmitting the uplink packet/PDU/monitoring packet to the UPF through the N3 interface, one or more information among local time T23 It can be encapsulated with .

When the UPF (or PSA UPF) receives an uplink packet/PDU/monitoring packet associated with the corresponding PDU-Set, it can record the local time T4 and calculate the round-trip time or uplink/downlink packet delay. .

The UPF (or PSA UPF) can record the local time T24 when receiving the uplink packet/PDU/monitoring packet associated with the corresponding PDU-Set and the PDU-Set round trip time or PDU-Set uplink/downlink. Packet delay can be calculated.

Below, PDU-Set related information/parameters (e.g. PDU-Set parameters) and QoS-sub-flow(s)/PDU-Set(s) for distinguishing PDU-Sets are described.

In the case of downlink, UPF (UE in case of uplink) is one data packet/payload/application PDU with an arbitrary header (e.g. payload/RTP/SRTP/RTCP/TCP/ A PDU-Set can be distinguished using one or more pieces of information included in the UDP/IP header. For example, the RTP header includes information such as a sequence number, timestamp, and M (Marker) bit, and the information can be used to identify packets belonging to one PDU-Set. For another example, the RTP extension header contains information about the type of payload data (e.g., RTP payload Network Adaptation Layer Unit Type field), and this information can be used to determine the importance of the packet. Alternatively, UPF can distinguish PDU-Sets using metadata generated by AS/application. Packet filter information to distinguish the PDU-Set (e.g. PDU-Set description information through one or more information included in an arbitrary header) is provided by the application function (AF) (if a NEF (Network Exposure Function) exists, NEF via) can be delivered to the corresponding entity/node (e.g. PCF/SMF/PFDF/UDM).

In the case of downlink, the UPF (UE in the case of uplink) can add PDU-Set related information to the corresponding PDUs and transmit it to the base station (RAN). The base station can use the received information to allocate radio resources. The base station can use the received information to classify the PDU-Set using UPF and transmit data. PDU-Set related information transmitted from the UPF/UE to the base station may include one or more of the following information.

- PDU-Set Identifier: Information to identify the PDU-Set

- PDU-Set sequence number (sequence number/mark)

- PDU-Set Size: Information to identify/indicate the last SDU/PDU of one PDU-Set

- Information to indicate the starting/last PDU in the PDU-Set

- PDU-Set importance/priority indication information: Information to indicate the importance/priority value of the relevant PDU-Set

One or more of the above-mentioned information may be included only in the first PDU of the corresponding PDU-Set. And/or one or more of the above-mentioned information may be included in the last PDU of the corresponding PDU-Set. Alternatively, one or more of the above-described information may be included in all PDUs of the corresponding PDU-Set. As an example, one PDU-Set can be distinguished by setting/adding the same PDU sequence number to all packets belonging to the PDU-Set. As another example, one PDU-Set can be distinguished by setting/adding information to indicate that the last packet belonging to the PDU-Set is the last PDU in the PDU-Set.

One or more of the above-mentioned information may be marked and distinguished through arbitrary fields on the GTP-U extension header at the base station/UPF.

A terminal capable of PDU-Set processing can request use of the function and receive authorization/permission during the NAS procedure (e.g. attach procedure, service request procedure, PDU session establish/modify). And/or, the terminal may receive a rule/policy for PDU-Set processing for a PDU session that supports PDU-Set processing during the PDU Session setup/modification procedure. For example, it can be received by including it in the N1 SM (Session Management) container. The rule/policy is the QoS rule for the PDU-Set, the QoS-flow/Sub-QoS-flow/PDU-Set level QoS parameters linked to the QoS rule. may include. The terminal can process uplink data using QoS rules for the received PDU-Set and Sub-QoS-flow/PDU-Set level QoS parameters. PDU-Set level QoS parameters include PDU-Set level QoS characteristics (PDU-Set level Resource type (Non-GBR, GBR, Delay-critical GBR), PDU-Set level Priority/importance, PDU-Set level Packet Delay Budget, PDU -It may include one or more of Set level Packet Error Rate, PDU-Set level Averaging window, PDU-Set level Maximum Data Burst Volume, and PDU-Set discard time. Or, it may be a scalar value (e.g. 5QI, QCI) used to reference PDU-Set level QoS characteristics. The base station can receive QoS rules and PDU-Set level QoS parameters for the PDU-Set from the core network node (e.g. AMF/SMF) on the related NAS procedure.

The corresponding QoS characteristic information may be indicated in connection with 5QI. Alternatively, the QoS characteristic information may be indicated by defining additional/linked QoS-flow/Sub-QoS-flow/PDU-Set level sub-indicator/identification information for 5QI.

The core network control plane entity (e.g. SMF/AMF) is sent to the base station during the PDU session setup/modification procedure (via the PDU SESSION RESOURCE SETUP REQUEST message or PDU SESSION RESOURCE MODIFY REQUEST message, or the PDU Session Resource Setup Request Transfer IE of the message) Alternatively, it can be indicated including the corresponding 5QI/QoS characteristic information and the corresponding sub-indicator/identification information (via PDU Session Resource Modify Request Transfer IE).

In order to support scheduling considering the information, the base station provides QoS-flow/Sub-QoS-flow/PDU-Set, QoS-flow/Sub-QoS-flow/PDU-Set level 5QI/QoS characteristic information, QoS-flow /Sub-QoS-flow/PDU-Set level You can configure SRB/DRB or SRB(s)/DRB(s) group linked to sub-indicator/identification information (configured with that information). The base station can configure the SRB/DRB configuration information to include information to indicate this through RRC signaling (e.g. RRC reconfiguration message). Alternatively, the base station may link and include the configuration necessary to transmit the user plane data in consideration of the information(s) in the DRB configuration information through RRC signaling (e.g. RRC reconfiguration message).

In the downlink, incoming data packets can be classified based on a packet filter set of downlink PDR (Packet Detection Rule). UPF/Dedicated UPF can carry user plane traffic classification belonging to one QoS flow through N3 User Plane marking using QFI. UPF/Dedicated UPF can distinguish one or more QoS flow(s) belonging to one PDU session into different QoS-flows/Sub-QoS-flow/PDU-Sets. Classification of user plane traffic belonging to one PDU-Set is further classified using any information included in the present invention (e.g. PDU-Set related information) and/or a packet filter set described below and classified into the corresponding N3 User Plane. It can be transported through marking.

QoS-flows/PDU-Sets with correlation/dependency can be grouped into one group-QoS-flow/group-PDU-Set. UPF/Dedicated UPF classifies user plane traffic belonging to one group-QoS-flow/group-PDU-Set further using any information included in the present invention and/or a packet filter set described below. It can be transported through the corresponding N3 User Plane marking.

For the corresponding PDU session/application session in the uplink, the terminal evaluates uplink packets for the uplink packet filter in the packet filter set in the QoS rule in ascending order based on the priority of the QoS rule until a matching QoS rule is found. (evaluate) can be done. The terminal can bind an uplink packet to a QoS flow using a QFI that matches the corresponding QoS rule. The terminal classifies different user plane traffic (PDU Set) belonging to one or more QoS flow(s)/PDU-Set(s) using any information included in the present invention and/or the packet filter set described below. You can use to further classify and bind the corresponding uplink packet to the corresponding QoS-flow/Sub-QoS-flow/PDU-Set.

The core network entity (e.g. UPF/dedicated UPF) linked to the XR application or XR application server within the terminal or the data network (DN) including the server uses the relevant information to divide QoS flows for the application into different application sessions/ It can be separated into QoS-flows/Sub-QoS-flows/PDU-Sets. The core network entity (e.g. UPF/dedicated UPF) linked to the XR application or XR application server within the terminal or the data network (DN) including the server uses the information to group QoS flows for the application into different groups. Can be separated into -flow/group-PDU-Set.

For example, the application session/QoS-flow/Sub-QoS-flow/PDU-Set can be distinguished and QFIs added/marked to be mapped to different QoS flows. The QFI added/marked to the application session/QoS-flow/Sub-QoS-flow/PDU-Set is used to set/modify the PDU session to which the application session/QoS-flow/Sub-QoS-flow/PDU-Set belongs. It may be an additional QFI that is distinct from the QFI for identifying QoS flow. For convenience of explanation, within the corresponding QoS flow (or associated with the corresponding QoS flow), which is distinguished from QFI/5QI used as identification information/QoS identification information for one QoS-flow belonging to one PDU session. Application Session/Sub-QoS-flow/PDU-Set identification information classified by PDU-Set or Application Session/Sub-QoS-flow/PDU-Set QoS identification information is divided into Application Session/Sub-QoS-flow/PDU-Set QFI It is written as /5QI. This is for convenience of explanation and can be replaced with any other term such as PDU-Set level QFI/5QI, Secondary QFI/5QI, PDU-Set-identifier/PDU-Set-5QI, and sub QFI/5QI.

For another example, for one application, the application session/QoS-flow(s)/Sub-QoS-flow belonging to the application can be distinguished and separated into different PDU-Sets. In order to identify/distinguish the PDU Set, detailed/additional identification information linked to the QFI/5QI for the QoS flows of the application belonging to the PDU session may be defined and marked. For example, detailed/additional identification information may be the above-described Application Session/Sub-QoS-flow/PDU-Set QFI/5QI. As another example, detailed/additional identification information can be used to link/group and process PDU-Sets that are dependent on (or belonging to) the application. For example, a group identifier to distinguish the dependent PDU Set group to which the PDU Set belongs, priority/importance of the PDU Set among grouped PDU Sets, other application sessions/QoS flow/Sub-QoS-flow/ within the group. One or more of the following information for identifying the relative priority of the PDU-Set, other PDU-Set(s) with correlation/dependency, and other PDU-Set(s) with correlation/dependency may be defined and marked. there is.

For another example, for one or more single modal data/flows that are correlated for one application, each single modal data/flow/media element can be linked to a PDU Set, and the corresponding PDU Sets can be grouped. A PDU Set group may include a PDU Set list/list for PDU Sets belonging to the group. Each PDU Set has one of the PDU Set identifier, QFI/5QI for the QoS flow/Sub-QoS-flow to which the PDU Set belongs, and Application Session/PDU-Set/Sub-QoS-flow QFI/5QI for the PDU Set. It can be distinguished through connection with the above. PDU Set groups can be distinguished through an identifier/index to identify the PDU Set group.

For another example, an identifier that can be used instead of/instead of QFI/5QI for a PDU-Set may be defined and marked. And/or the identifier may be assigned dynamically (defined by the operator). For example, the identifier can be signaled in the same way as other QoS profiles/QoS parameters by applying dynamically assigned QFI/5QI (as defined by the operator), similar to the dynamically assigned 5QI method. For example, with a non-standardized or non-preconfigured 5QI value, the corresponding QoS characteristic information (e.g. dynamic 5QI descriptor IE) may be signaled from the core network control plane entity to the base station as part of the corresponding QoS profile. As an example, the corresponding QFI/5QI/QoS profile/QoS parameters/characteristics may be included in subscription data and provided from UDM to SMF/PCF/AF. As another example, the SMF can retrieve/receive the corresponding QFI/5QI/QoS profile/QoS parameters from NEF/AF/PCF (or a dedicated SMF that supports PDU Set integrated packet processing). SMF determines the creation/modification of the corresponding application session/QoS-flows/Sub-QoS-flow/PDU-Set based on the policy rules received from NEF/AF/PCF. As another example, one or more of the above operations may be triggered by a terminal request.

<General devices to which this specification can be applied>

Below, the device to which this specification can be applied will be described.

Figure 4 shows a block diagram of a processor on which the disclosure of the present specification is implemented.

As can be seen with reference to Figure 4, the processor 1020 in which the disclosure of this specification is implemented implements the proposed functions, procedures and/or methods described in this specification. To include multiple circuits can do. For example, the processor 1020 may include a first circuit 1020-1, a second circuit 1020-2, and a third circuit 1020-3.

Additionally, although not shown, the processor 1020 may include more circuitry. Each circuit may include a plurality of transistors.

The processor 1020 may be called an application-specific integrated circuit (ASIC) or an application processor (AP), and includes at least one of a digital signal processor (DSP), a central processing unit (CPU), and a graphics processing unit (GPU). can do.

Figure 5 shows a wireless communication device according to an embodiment of the present specification.

Referring to Figure 5, the wireless communication system may include a first device 100a and a second device 100b.

The first device 100a includes a base station, a network node, a transmission terminal, a reception terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, and a connected car (Conn. ected Car),Drone(Unmanned Aerial Vehicle, UAV), AI (Artificial Intelligence) module, robot, AR (Augmented Reality) device, VR (Virtual Reality) device, MR (Mixed Reality) device, hologram device, public safety device, MTC device, IoT device, medical device, pin. It may be a tech device (or financial device), a security device, a climate/environment device, a device related to 5G services, or a device related to the 4th industrial revolution field other than that.

The second device (100b) includes a base station, a network node, a transmission terminal, a reception terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, and a connected car (Conn. ected Car),Drone(Unmanned Aerial Vehicle, UAV), AI (Artificial Intelligence) module, robot, AR (Augmented Reality) device, VR (Virtual Reality) device, MR (Mixed Reality) device, hologram device, public safety device, MTC device, IoT device, medical device, pin. It may be a tech device (or financial device), a security device, a climate/environment device, a device related to 5G services, or a device related to the 4th industrial revolution field other than that.

The first device 100a includes at least one processor, such as the processor 1020a, at least one memory, such as the memory 1010a, and the transceiver 1031a. It may include at least one transceiver. The processor 1020a may perform the above-described functions, procedures, and/or methods. The processor 1020a is capable of performing one or more protocols. For example, the processor 1020a may perform one or more layers of a wireless interface protocol. The memory 1010a is connected to the processor 1020a and can store information and/or instructions in various forms. The transceiver 1031a is connected to the processor 1020a and can be controlled to transmit and receive wireless signals.

The second device 100b includes at least one processor such as the processor 1020b, at least one memory device such as the memory 1010b, and a transceiver 1031b. It may include at least one transceiver. The processor 1020b may perform the above-described functions, procedures, and/or methods. The processor 1020b may implement one or more protocols. For example, the processor 1020b may implement one or more layers of a wireless interface protocol. The memory 1010b is connected to the processor 1020b and can store information and/or instructions in various forms. The transceiver (1031b) is connected to the processor (1020b) and can be controlled to transmit and receive wireless signals.

The memory 1010a and/or the memory 1010b may be connected, respectively, inside or outside the processor 1020a and/or the processor 1020b, and may be connected by wire. or other processors through various technologies, such as wireless connections. It may be connected to.

The first device 100a and/or the second device 100b may have one or more antennas. For example, antenna 1036a and/or antenna 1036b may be configured to transmit and receive wireless signals.

Figure 6 illustrates a block diagram of a communication device according to an embodiment of the present specification.

In particular, Figure 6 is a diagram illustrating the terminal of Figure 5 in more detail.

The terminal includes a memory 1010, a processor 1020, a transceiver 1031, a power management module 1091, a battery 1092, a display 1041, an input unit 1053, a speaker 1042, and a microphone 1052, Includes a subscriber identification module (SIM) card and one or more antennas.

Processor 1020 may be configured to implement the suggested functions, procedures and/or methods described herein. Layers of the air interface protocol may be implemented in processor 1020. Processor 1020 may include an application-specific integrated circuit (ASIC), other chipset, logic circuit, and/or data processing device. The processor 1020 may be an application processor (AP). The processor 1020 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of processors 1020 include SNAPDRAGONTM series processors manufactured by Qualcomm®, EXYNOSTM series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIOTM series processors manufactured by MediaTek®, INTEL® It may be an ATOMTM series processor manufactured by or a corresponding next-generation processor.

The power management module 1091 manages power for the processor 1020 and/or the transceiver 1031. Battery 1092 supplies power to power management module 1091. The display 1041 outputs the results processed by the processor 1020. Input unit 1053 receives input to be used by processor 1020. The input unit 1053 may be displayed on the display 1041. A SIM card is an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and its associated keys, which are used to identify and authenticate subscribers in mobile phone devices such as mobile phones and computers. You can also store contact information on many SIM cards.

The memory 1010 is operably coupled to the processor 1020 and stores various information for operating the processor 610. Memory 1010 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. When an embodiment is implemented as software, the techniques described herein may be implemented as modules (eg, procedures, functions, etc.) that perform the functions described herein. Modules may be stored in memory 1010 and executed by processor 1020. The memory 1010 may be implemented inside the processor 1020. Alternatively, the memory 1010 may be implemented external to the processor 1020 and may be communicatively connected to the processor 1020 through various means known in the art.

The transceiver 1031 is operably coupled to the processor 1020 and transmits and/or receives wireless signals. The transceiver unit 1031 includes a transmitter and a receiver. The transceiver 1031 may include a baseband circuit for processing radio frequency signals. The transceiver controls one or more antennas to transmit and/or receive wireless signals. The processor 1020 transmits command information to the transceiver 1031 to initiate communication, for example, to transmit a wireless signal constituting voice communication data. The antenna functions to transmit and receive wireless signals. When receiving a wireless signal, the transceiver 1031 may transfer the signal and convert the signal to baseband for processing by the processor 1020. The processed signal may be converted into audible or readable information output through the speaker 1042.

The speaker 1042 outputs sound-related results processed by the processor 1020. Microphone 1052 receives sound-related input to be used by processor 1020.

The user inputs command information such as a phone number, for example, by pressing (or touching) a button on the input unit 1053 or by voice activation using the microphone 1052.

The processor 1020 receives this command information and processes it to perform appropriate functions, such as calling a phone number. Operational data can be extracted from the SIM card or memory 1010.

Additionally, the processor 1020 may display command information or driving information on the display 1041 for the user's recognition and convenience.

The examples of the present disclosure posted in the specification and drawings are merely provided as specific examples to easily explain the technical content of the present disclosure and aid understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In addition to the examples posted here, it is obvious to those skilled in the art that other modifications based on the technical idea of the invention can be implemented.

Claims (1)

In a method of measuring data status in a wireless communication system,
Receiving congestion-related information; and
A method comprising measuring at least one of data rate, delay budget, delay difference, jitter, round trip delay, and congestion level based on the received congestion-related information.