KR20230116706A - Method and apparatus for controlling traffic - Google Patents

Abstract

The present disclosure relates to a technology for controlling XR and media service traffic in a mobile communication network. In one aspect, the present embodiments are a method for controlling data traffic by a core network control plane node, from application function control entities to help information on application traffic characteristics, PDU-Set QoS parameters, and multimodal applications. During the information receiving step of receiving at least one of an identifier for grouping flows and a synchronization threshold, and during a PDU session setup or modification procedure, help information on application traffic characteristics, PDU Set QoS parameters, and flows belonging to multimodal applications are sent to the base station. It is possible to provide a method and apparatus including an information transmission step of transmitting at least one of an identifier for grouping and a synchronization threshold, and a control step of instructing transmission of a user packet including PDU-Set information to a core network user plane node. .

Description

Traffic control method and apparatus {METHOD AND APPARATUS FOR CONTROLLING TRAFFIC}

The present disclosure relates to a technology for controlling XR and media service traffic in a mobile communication network.

XR(eXtended Reality) and CG(Cloud Gaming) are various types of augmented, virtual and mixed environments in human-machine and human-human communication performed with the help of handheld and wearable terminals. It is used as a broad term meaning Extended Reality (XR) 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 of the calculations related to gaming are offloaded from the terminal to the edge or remote server. Along with cloud computing/gaming, XR applications typically require high throughput and low latency.

Many XR and CG use cases involve frequent uplink (e.g. pose/control updates) and/or quasi-periodic (possibly jitter) high data rates in the downlink video stream combined with the uplink video stream. ) characterized by traffic. Both downlink and uplink traffic is characterized by a relatively tight packet delay budget (PDB).

Many XR and CG terminals have limited battery power. However, the current DRX configuration is not suitable due to non-integer XR traffic cycles, variable XR data rates, and quasi-periodic XR cycles.

Also, the set of expected XR and CG services has a certain diversity. While the corresponding service is running through a wireless network (e.g. NR), the data stream (e.g. video) may change on the fly.

Packets within one frame may have dependencies on each other. The application may need all of the packets to decode the frame. The loss of one packet can render other correlated packets useless even if they have been successfully transmitted. For example, XR applications may impose requirements in terms of Application Data Units (ADUs)/Media Units rather than single packets/PDUs.

Packets in the same video stream but in different frame types (I/P frames) or even different locations within a Group of Picture (GoP) can have different contributions to the user experience. Thus, layered QoS handling within the video stream can loosen the requirements and lead to higher efficiencies.

It may be useful to facilitate radio parameter selection if additional information is available on the running service/application from higher layers. To this end, a technology that allows the communication network to effectively recognize and process XR application traffic is required.

The present disclosure intends to provide a specific method and apparatus through which communication network nodes can effectively recognize and process XR application traffic.

In one aspect, the present embodiments are a method for controlling data traffic by a core network control plane node, from application function control entities to help information on application traffic characteristics, PDU-Set QoS parameters, and multimodal applications. During the information receiving step of receiving at least one of an identifier for grouping flows and a synchronization threshold, and during a PDU session setup or modification procedure, help information on application traffic characteristics, PDU Set QoS parameters, and flows belonging to multimodal applications are sent to the base station. It is possible to provide a method including an information transmission step of transmitting at least one of an identifier for grouping and a synchronization threshold, and a control step of instructing transmission of a user packet including PDU-Set information to a core network user plane node.

In another aspect, the present embodiments are a method for controlling data traffic by a base station, using help information for application traffic characteristics from a core network control plane node, PDU-Set QoS parameters, identifiers for grouping flows belonging to multimodal applications , information receiving step of receiving one or more of the synchronization thresholds, constructing a radio bearer for application traffic using the information received from the core network control plane node, and receiving PDU-set information from the core network user plane node. A method comprising steps may be provided.

In another aspect, the present embodiments provide help information on application traffic characteristics, PDU-Set QoS parameters, and belonging to multimodal applications from an application function control entity in a core network control plane node that controls data traffic. An identifier for grouping flows, a synchronization threshold, and help information on application traffic characteristics to a base station during a PDU session setup or modification procedure, PDU Set QoS parameter, and grouping flows belonging to multimodal applications It is possible to provide a core network control plane node apparatus including a transmitter for transmitting at least one of an identifier and a synchronization threshold and a control unit for controlling transmission of user packets including PDU-Set information to a core network user plane node.

In another aspect, the present embodiments provide, in a base station controlling data traffic, help information for application traffic characteristics from a core network control plane node, a PDU-Set QoS parameter, an identifier for grouping flows belonging to a multimodal application, A receiver for receiving at least one information of the synchronization threshold and a control unit for configuring a radio bearer for application traffic using information received from a core network control plane node, wherein the receiver receives PDU-set information from a core network user plane node. It is possible to provide a base station device further comprising the step of receiving.

The present disclosure provides an effect of providing a specific method and apparatus for communication network nodes to effectively recognize and process XR application traffic.

1 is a diagram schematically illustrating the structure of an NR wireless communication system to which this embodiment can be applied.
2 is a diagram for explaining a frame structure in an NR system to which this embodiment can be applied.
3 is a diagram for explaining a resource grid supported by a radio access technology to which this embodiment can be applied.
4 is a diagram for explaining a bandwidth part supported by a radio access technology to which this embodiment can be applied.
5 is a diagram exemplarily illustrating a synchronization signal block in a radio access technology to which this embodiment can be applied.
6 is a diagram for explaining a random access procedure in a radio access technology to which this embodiment can be applied.
7 is a diagram for explaining CORESET.
8 is a diagram for explaining an example of a structure for representing a 5G-XR function in a 5G system.
9 is a diagram for explaining an operation of a core network control plane node according to an embodiment.
10 is a diagram for explaining an operation of a base station according to an embodiment.
11 is a diagram showing the configuration of a core network control plane node according to another embodiment.
12 is a diagram showing the configuration of a base station according to another embodiment.

DETAILED DESCRIPTION Some embodiments of the present disclosure are described in detail below with reference to exemplary drawings. In adding reference numerals to components of each drawing, the same components may have the same numerals as much as possible even if they are displayed on different drawings. In addition, in describing the present embodiments, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present technical idea, the detailed description may be omitted. When "comprises", "has", "consists of", etc. mentioned in this specification is used, other parts may be added unless "only" is used. In the case where a component is expressed in the singular, it may include the case of including the plural unless otherwise explicitly stated.

Also, terms such as first, second, A, B, (a), and (b) may be used in describing the components of the present disclosure. These terms are only used to distinguish the component from other components, and the nature, sequence, order, or number of the corresponding component is not limited by the term.

In the description of the positional relationship of components, when it is described that two or more components are "connected", "coupled" or "connected", the two or more components are directly "connected", "coupled" or "connected". ", but it will be understood that two or more components and other components may be further "interposed" and "connected", "coupled" or "connected". Here, other components may be included in one or more of two or more components that are “connected”, “coupled” or “connected” to each other.

In the description of the temporal flow relationship related to components, operation methods, production methods, etc., for example, "after", "continued to", "after", "before", etc. Alternatively, when a flow sequence relationship is described, it may also include non-continuous cases unless “immediately” or “directly” is used.

On the other hand, when a numerical value or corresponding information (eg, level, etc.) for a component is mentioned, even if there is no separate explicit description, the numerical value or its corresponding information is not indicated by various factors (eg, process factors, internal or external shocks, noise, etc.) may be interpreted as including an error range that may occur.

A wireless communication system in the present specification refers to a system for providing various communication services such as voice and data packets using radio resources, and may include a terminal, a base station, or a core network.

The present embodiments disclosed below may be applied to wireless communication systems using various wireless access technologies. For example, the present embodiments include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and singlecarrier frequency division multiple access (SC-FDMA). Alternatively, it may be applied to various radio access technologies such as non-orthogonal multiple access (NOMA). In addition, the wireless access technology may mean not only a specific access technology, but also a communication technology for each generation established by various communication consultative organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, and ITU. For example, CDMA may be implemented as a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented with a radio technology such as global system for mobile communications (GSM)/general packet radio service (GPRS)/enhanced datarates for GSM evolution (EDGE). OFDMA may be implemented with a wireless technology such as institute of electrical and electronic engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), and the like. IEEE 802.16m is an evolution of IEEE 802.16e, and provides backward compatibility with a system based on IEEE 802.16e. UTRA is part of the universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) that uses evolved-UMTSterrestrial radio access (E-UTRA). Adopt FDMA. As such, the present embodiments may be applied to currently disclosed or commercialized radio access technologies, and may also be applied to radio access technologies currently under development or to be developed in the future.

Meanwhile, a terminal in the present specification is a comprehensive concept meaning a device including a wireless communication module that communicates with a base station in a wireless communication system, and in WCDMA, LTE, NR, HSPA, and IMT-2020 (5G or New Radio) It should be interpreted as a concept that includes not only User Equipment (UE), but also Mobile Station (MS), User Terminal (UT), Subscriber Station (SS), and wireless device in GSM. In addition, the terminal may be a user portable device such as a smart phone depending on the type of use, or may mean a vehicle or a device including a wireless communication module in the vehicle in the V2X communication system. In addition, in the case of a machine type communication system, it may mean an MTC terminal, an M2M terminal, a URLLC terminal, etc. equipped with a communication module to perform machine type communication.

A base station or cell in this specification refers to an end that communicates with a terminal in terms of a network, and includes Node-B (Node-B), eNB (evolved Node-B), gNB (gNode-B), LPN (Low Power Node), Sector, site, various types of antennas, base transceiver system (BTS), access point, point (e.g. transmission point, reception point, transmission/reception point), relay node ), mega cell, macro cell, micro cell, pico cell, femto cell, remote radio head (RRH), radio unit (RU), and small cell. Also, a cell may mean including a bandwidth part (BWP) in the frequency domain. For example, the serving cell may mean the activation BWP of the terminal.

Since there is a base station controlling one or more cells in the various cells listed above, the base station can be interpreted in two meanings. 1) In relation to the radio area, it may be a device itself that provides a mega cell, macro cell, micro cell, pico cell, femto cell, or small cell, or 2) it may indicate the radio area itself. In 1), all devices providing a predetermined radio area are controlled by the same entity or all devices interacting to form a radio area cooperatively are directed to the base station. Points, transmission/reception points, transmission points, reception points, etc., according to the configuration method of the radio area, become an example of a base station. In 2), the radio area itself in which signals are received or transmitted may be indicated to the base station from the viewpoint of the user terminal or the neighboring base station.

In this specification, a cell refers to a component carrier having coverage of a signal transmitted from a transmission/reception point or a coverage of a signal transmitted from a transmission/reception point (transmission point or transmission/reception point), and the transmission/reception point itself. can

Uplink (UL, or uplink) means a method of transmitting and receiving data from a terminal to a base station, and downlink (DL, or downlink) means a method of transmitting and receiving data from a base station to a terminal do. Downlink may mean communication or a communication path from multiple transmission/reception points to a terminal, and uplink may mean communication or communication path from a terminal to multiple transmission/reception points. In this case, in the downlink, the transmitter may be a part of a multi-transmission/reception point, and the receiver may be a part of a terminal. Also, in uplink, a transmitter may be a part of a terminal, and a receiver may be a part of a multi-transmission/reception point.

In uplink and downlink, control information is transmitted and received through control channels such as a physical downlink control channel (PDCCH) and a physical uplink control channel (PUCCH), and a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH). Data is transmitted and received by configuring the same data channel. Hereinafter, the situation in which signals are transmitted and received through channels such as PUCCH, PUSCH, PDCCH, and PDSCH is expressed in the form of 'transmitting and receiving PUCCH, PUSCH, PDCCH, and PDSCH'. do.

For clarity of explanation, 3GPP LTE/LTE-A/NR (New RAT) communication system is mainly described in the following technical idea, but the technical features are not limited to the corresponding communication system.

3GPP develops 5G (5th-Generation) communication technology to meet the requirements of ITU-R's next-generation wireless access technology after research on 4G (4th-Generation) communication technology. Specifically, 3GPP develops new NR communication technology separate from LTE-A pro and 4G communication technology, which has improved LTE-Advanced technology to meet the requirements of ITU-R as 5G communication technology. Both LTE-A pro and NR refer to 5G communication technology. Hereinafter, 5G communication technology will be described focusing on NR when a specific communication technology is not specified.

Operating scenarios in NR defined various operating scenarios by adding consideration to satellites, automobiles, and new verticals in the existing 4G LTE scenarios. It is deployed in the range to support mMTC (Massive Machine Communication) scenarios that require low data rates and asynchronous access, and URLLC (Ultra Reliability and Low Latency) scenarios that require high responsiveness and reliability and can support high-speed mobility. .

In order to satisfy this scenario, NR discloses a wireless communication system to which a new waveform and frame structure technology, low latency technology, mmWave support technology, and forward compatible technology are applied. In particular, the NR system proposes various technical changes in terms of flexibility in order to provide forward compatibility. The main technical features of NR are described below with reference to the drawings.

<NR System General>

1 is a diagram schematically showing the structure of an NR system to which this embodiment can be applied.

Referring to FIG. 1, the NR system is divided into 5GC (5G Core Network) and NR-RAN parts, and NG-RAN controls the user plane (SDAP / PDCP / RLC / MAC / PHY) and UE (User Equipment) It consists of gNB and ng-eNB providing plane (RRC) protocol termination. The gNB mutual or the gNB and ng-eNB are interconnected through the Xn interface. gNB and ng-eNB are each connected to 5GC through NG interface. 5GC may include an Access and Mobility Management Function (AMF) in charge of a control plane such as terminal access and mobility control functions, and a User Plane Function (UPF) in charge of a control function for user data. NR includes support for both frequency bands below 6 GHz (FR1, Frequency Range 1) and above 6 GHz frequency band (FR2, Frequency Range 2).

gNB means a base station that provides NR user plane and control plane protocol termination to a terminal, and ng-eNB means a base station that provides E-UTRA user plane and control plane protocol termination to a terminal. The base station described in this specification should be understood as encompassing gNB and ng-eNB, and may be used to refer to gNB or ng-eNB separately as needed.

<NR wave form, numerology and frame structure>

In NR, a CP-OFDM waveform using a cyclic prefix is used for downlink transmission, and CP-OFDM or DFT-s-OFDM is used for uplink transmission. OFDM technology is easy to combine with multiple input multiple output (MIMO) and has the advantage of using a low-complexity receiver with high frequency efficiency.

On the other hand, in NR, since the requirements for data rate, latency, coverage, etc. are different for each of the three scenarios described above, it is necessary to efficiently satisfy the requirements for each scenario through a frequency band constituting an arbitrary NR system. . To this end, a technique for efficiently multiplexing radio resources based on a plurality of different numerologies has been proposed.

Specifically, the NR transmission numerology is determined based on the sub-carrier spacing and CP (Cyclic prefix), and as shown in Table 1 below, the μ value is used as an exponential value of 2 based on 15 kHz, resulting in an exponential is changed to

μ subcarrier spacing Cyclic prefix Supported for data Supported for synch 0 15 Normal Yes Yes One 30 Normal Yes Yes 2 60 Normal, Extended Yes No 3 120 Normal Yes Yes 4 240 Normal No Yes

As shown in Table 1 above, the numerology of NR can be classified into five types according to the subcarrier spacing. This is different from the fact that the subcarrier interval of LTE, which is one of the 4G communication technologies, is fixed at 15 kHz. Specifically, in NR, subcarrier intervals used for data transmission are 15, 30, 60, and 120 kHz, and subcarrier intervals used for synchronization signal transmission are 15, 30, 120, and 240 kHz. In addition, the extended CP is applied only to a 60 kHz subcarrier interval. Meanwhile, a frame structure in NR is defined as a frame having a length of 10 ms composed of 10 subframes having the same length of 1 ms. One frame may be divided into half frames of 5 ms, and each half frame includes 5 subframes. In the case of a 15 kHz subcarrier interval, one subframe consists of one slot, and each slot consists of 14 OFDM symbols.

2 is a diagram for explaining a frame structure in an NR system to which this embodiment can be applied.

Referring to FIG. 2, a slot is fixedly composed of 14 OFDM symbols in the case of a normal CP, but the length of the slot in the time domain may vary according to the subcarrier interval. For example, in the case of a numerology having a 15 kHz subcarrier interval, a slot is 1 ms long and has the same length as a subframe. In contrast, in the case of numerology having a subcarrier interval of 30 kHz, a slot consists of 14 OFDM symbols, but two slots may be included in one subframe with a length of 0.5 ms. That is, subframes and frames are defined with a fixed time length, and slots are defined by the number of symbols, and the time length may vary according to subcarrier intervals.

Meanwhile, NR defines a basic unit of scheduling as a slot, and introduces a mini-slot (or sub-slot or non-slot based schedule) to reduce transmission delay in a radio section. When a wide subcarrier interval is used, the length of one slot is shortened in inverse proportion to a transmission delay in a radio section. Mini-slots (or sub-slots) are for efficient support of URLLC scenarios and can be scheduled in units of 2, 4, or 7 symbols.

Also, unlike LTE, NR defines uplink and downlink resource allocation at the symbol level within one slot. In order to reduce HARQ delay, a slot structure capable of directly transmitting HARQ ACK/NACK within a transmission slot has been defined, and this slot structure is named and described as a self-contained structure.

NR is designed to support a total of 256 slot formats, of which 62 slot formats are used in 3GPP Rel-15. In addition, a common frame structure constituting an FDD or TDD frame is supported through a combination of various slots. For example, a slot structure in which all symbols of a slot are set to downlink, a slot structure in which all symbols of a slot are set to uplink, and a slot structure in which downlink symbols and uplink symbols are combined are supported. NR also supports that data transmissions are distributed and scheduled over one or more slots. Therefore, the base station can inform the terminal whether the slot is a downlink slot, an uplink slot, or a flexible slot using a slot format indicator (SFI). The base station may indicate the slot format by indicating the index of the table configured through UE-specific RRC signaling using SFI, dynamically indicating through DCI (Downlink Control Information), or static or static through RRC. It can also be given quasi-statically.

<NR physical resources>

Regarding physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, bandwidth parts, etc. are considered do.

An antenna port is defined such that the channel on which a symbol on an antenna port is carried can be inferred from the channel on which other symbols on the same antenna port are carried. Two antenna ports are quasi co-located or QC/QCL (quasi co-located or quasi co-location). Here, the wide range characteristics include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

3 is a diagram for explaining a resource grid supported by a radio access technology to which this embodiment can be applied.

Referring to FIG. 3 , since NR supports a plurality of numerologies in the same carrier, a resource grid may exist according to each numerology. Also, resource grids may exist according to antenna ports, subcarrier intervals, and transmission directions.

A resource block consists of 12 subcarriers and is defined only in the frequency domain. Also, a resource element is composed of one OFDM symbol and one subcarrier. Accordingly, as shown in FIG. 3, the size of one resource block may vary according to the subcarrier interval. In addition, in NR, “Point A”, which serves as a common reference point for the resource block grid, and common resource blocks and virtual resource blocks are defined.

4 is a diagram for explaining a bandwidth part supported by a radio access technology to which this embodiment can be applied.

In NR, unlike LTE where the carrier bandwidth is fixed at 20Mhz, the maximum carrier bandwidth is set from 50Mhz to 400Mhz for each subcarrier interval. Therefore, it is not assumed that all terminals use all of these carrier bandwidths. Accordingly, in NR, as shown in FIG. 4, a bandwidth part (BWP) can be designated and used by a UE within a carrier bandwidth. In addition, the bandwidth part is associated with one numerology, is composed of a subset of consecutive common resource blocks, and can be dynamically activated according to time. Up to four bandwidth parts each of uplink and downlink are configured in the terminal, and data is transmitted and received using the active bandwidth part at a given time.

In the case of paired spectrum, the uplink and downlink bandwidth parts are set independently, and in the case of unpaired spectrum, to prevent unnecessary frequency re-tuning between downlink and uplink operations. For this purpose, the bandwidth parts of downlink and uplink are paired to share a center frequency.

<NR initial connection>

In NR, a UE accesses a base station and performs a cell search and random access procedure to perform communication.

Cell search is a procedure in which a UE synchronizes with a cell of a corresponding base station using a synchronization signal block (SSB) transmitted by the base station, acquires a physical layer cell ID, and obtains system information.

5 is a diagram exemplarily illustrating a synchronization signal block in a radio access technology to which this embodiment can be applied.

Referring to FIG. 5, the SSB consists of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) occupying 1 symbol and 127 subcarriers, and a PBCH spanning 3 OFDM symbols and 240 subcarriers.

The UE receives the SSB by monitoring the SSB in the time and frequency domains.

SSB can be transmitted up to 64 times in 5 ms. A plurality of SSBs are transmitted in different transmission beams within 5 ms, and the UE performs detection assuming that SSBs are transmitted every 20 ms period based on one specific beam used for transmission. The number of beams usable for SSB transmission within 5ms may increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted below 3 GHz, SSBs can be transmitted using up to 8 different beams in a frequency band of 3 to 6 GHz, and up to 64 different beams in a frequency band of 6 GHz or higher.

Two SSBs are included in one slot, and the start symbol and the number of repetitions within the slot are determined according to the subcarrier interval as follows.

On the other hand, SSB is not transmitted at the center frequency of the carrier bandwidth, unlike SS of conventional LTE. That is, the SSB can be transmitted even in a place other than the center of the system band, and a plurality of SSBs can be transmitted in the frequency domain when wideband operation is supported. Accordingly, the UE monitors the SSB using a synchronization raster, which is a candidate frequency location for monitoring the SSB. The carrier raster and synchronization raster, which are the center frequency location information of the channel for initial access, are newly defined in NR, and the synchronization raster has a wider frequency interval than the carrier raster, so it can support fast SSB search of the terminal. can

The UE may acquire the MIB through the PBCH of the SSB. MIB (Master Information Block) includes minimum information for the terminal to receive the remaining system information (RMSI, Remaining Minimum System Information) broadcast by the network. In addition, the PBCH includes information about the position of the first DM-RS symbol in the time domain, information for monitoring SIB1 by the UE (eg, SIB1 numerology information, information related to SIB1 CORESET, search space information, PDCCH related parameter information, etc.), offset information between the common resource block and the SSB (the location of the absolute SSB within the carrier is transmitted through SIB1), and the like. Here, the SIB1 numerology information is equally applied to some messages used in the random access procedure for accessing the base station after the UE completes the cell search procedure. For example, the numerical information of SIB1 may be applied to at least one of messages 1 to 4 for a random access procedure.

The aforementioned RMSI may mean System Information Block 1 (SIB1), and SIB1 is periodically (eg, 160 ms) broadcast in a cell. SIB1 includes information necessary for the terminal to perform an initial random access procedure, and is periodically transmitted through the PDSCH. In order for the terminal to receive SIB1, it needs to receive numerology information used for SIB1 transmission and CORESET (Control Resource Set) information used for SIB1 scheduling through the PBCH. The UE checks scheduling information for SIB1 using the SI-RNTI in CORESET, and acquires SIB1 on PDSCH according to the scheduling information. The remaining SIBs except for SIB1 may be transmitted periodically or may be transmitted according to the request of the terminal.

6 is a diagram for explaining a random access procedure in a radio access technology to which this embodiment can be applied.

Referring to FIG. 6, when cell search is completed, the terminal transmits a random access preamble for random access to the base station. The random access preamble is transmitted through PRACH. Specifically, the random access preamble is transmitted to the base station through a PRACH composed of contiguous radio resources in a periodically repeated specific slot. In general, when a UE initially accesses a cell, a contention-based random access procedure is performed, and when random access is performed for beam failure recovery (BFR), a non-contention-based random access procedure is performed.

The terminal receives a random access response to the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), UL Grant (uplink radio resource), temporary C-RNTI (Temporary Cell-Radio Network Temporary Identifier), and TAC (Time Alignment Command). Since one random access response may include random access response information for one or more terminals, the random access preamble identifier may be included to indicate to which terminal the included UL Grant, temporary C-RNTI, and TAC are valid. The random access preamble identifier may be an identifier for the random access preamble received by the base station. The TAC may be included as information for the UE to adjust uplink synchronization. The random access response may be indicated by a random access identifier on the PDCCH, that is, a random access-radio network temporary identifier (RA-RNTI).

Upon receiving a valid random access response, the terminal processes information included in the random access response and performs scheduled transmission to the base station. For example, the UE applies TAC and stores the temporary C-RNTI. In addition, data stored in the buffer of the terminal or newly generated data is transmitted to the base station using the UL grant. In this case, information capable of identifying the terminal must be included.

Finally, the terminal receives a downlink message for contention resolution.

<NR CORESET>

The downlink control channel in NR is transmitted in a CORESET (Control Resource Set) having a length of 1 to 3 symbols, and transmits up/down scheduling information, SFI (Slot Format Index), TPC (Transmit Power Control) information, etc. .

In this way, NR introduced the concept of CORESET to secure the flexibility of the system. A control resource set (CORESET) means a time-frequency resource for a downlink control signal. The UE may decode the control channel candidate using one or more search spaces in the CORESET time-frequency resource. A Quasi CoLocation (QCL) assumption for each CORESET is set, which is used for the purpose of notifying the characteristics of the analog beam direction in addition to the delay spread, Doppler spread, Doppler shift, and average delay, which are characteristics assumed by the conventional QCL.

7 is a diagram for explaining CORESET.

Referring to FIG. 7 , a CORESET may exist in various forms within a carrier bandwidth within one slot, and a CORESET may consist of up to three OFDM symbols in the time domain. In addition, CORESET is defined as a multiple of 6 resource blocks up to the carrier bandwidth in the frequency domain.

The first CORESET is indicated through the MIB as part of the initial bandwidth part configuration to allow additional configuration and system information to be received from the network. After establishing a connection with the base station, the terminal may receive and configure one or more CORESET information through RRC signaling.

In this specification, a frequency, frame, subframe, resource, resource block, region, band, subband, control channel, data channel, synchronization signal, various reference signals, various signals, or various messages related to NR (New Radio) can be interpreted in various meanings used in the past or currently used or in the future.

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

Many XR and CG use cases involve frequent uplink (e.g. pose/control updates) and/or quasi-periodic (possibly jitter) high data rates in the downlink video stream combined with the uplink video stream. ) characterized by traffic. Both downlink and uplink traffic is characterized by a relatively tight packet delay budget (PDB).

Many XR and CG terminals have limited battery power. However, the current DRX configuration is not suitable due to non-integer XR traffic cycles, variable XR data rates, and quasi-periodic XR cycles.

The set of expected XR and CG services has a certain diversity. While the corresponding service is running through a wireless network (e.g. NR), the data stream (e.g. video) may change on the fly.

Packets within one frame may have dependencies on each other. The application may need all of the packets to decode the frame. The loss of one packet can render other correlated packets useless even if they have been successfully transmitted. For example, XR applications may impose requirements in terms of application data units (ADUs)/media units rather than single packets/PDUs.

Packets in the same video stream but in different frame types (I/P frames) or even different locations within a Group of Picture (GoP) can have different contributions to the user experience. Thus, layered QoS handling within the video stream can loosen the requirements and lead to higher efficiencies.

It may be useful to facilitate radio parameter selection if additional information is available on the running service/application from higher layers.

However, in the conventional mobile communication technology, a specific method for enabling a terminal/base station/core network to effectively recognize and process XR application traffic has not been provided.

The present embodiment, devised to solve this problem, provides a technique for enabling QoS processing considering corresponding traffic characteristics by additionally utilizing information/fields used for services/applications.

Hereinafter, a control technology based on 5GS/NR technology will be described. However, this is for convenience of description and may be applied to the present embodiments for any system/radio access technology (e.g. LTE, 6G). The embodiments described in this disclosure include information elements and operation contents specified in the NR/5GS standards (e.g. MAC standard TS 38.321, NR RRC standard TS 38.331, system architecture standard TS 23.501). Even if the terminal operation content related to the definition of the corresponding information element is not included in this specification, the corresponding content specified in the standard specification, which is a known technology, may be included in this embodiment.

Any function described below may be defined as an individual terminal capability and transmitted by a terminal to a base station/core network entity (eg AMF/SMF). Alternatively, arbitrary functions may be combined/combined, defined as the corresponding terminal capability, and transmitted by the terminal to the base station/core network entity.

For convenience of explanation, one or more PDUs that deliver the payload of unit information generated by the application/application layer, a unit classified by application/application layer, or a unit classified within an application, or data/stream/ A unit having correlation between packets, or a unit having dependence between data/stream/packet, or a unit having different traffic characteristics/streams within one flow, and different traffic characteristics/streams within one PDU session. A unit that is classified based on information/field/metadata included/used/added in an application is marked as ADU (Application Data Unit) or PDU-set. This is only for convenience of description, 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) specific unit , frame type, stream type, etc. can be replaced with any other terms.

An application data unit (ADU) or PDU-set may consist of one or more PDUs carrying the payload of a unit of information generated at the application level (e.g. frames or video slices for XRM services as used in TR 26.926). there is. All PDUs in a PDU set are required by the application layer to use that information unit. Alternatively, the application layer may still recover all or part of the information units if some PDUs are missing.

In addition, a function in this specification may be described as including a protocol, entity, or node for providing a corresponding function in a core network. For example, AMF (Access and Mobility Management function) serves as a channel for non-access stratum (NAS) messages for UE access to the network, authentication procedure of UE, and gateway for UE to communicate with Core Network such as mobility management. do Accordingly, AMF is used in the sense of including function, protocol, procedure, entity or node. Also, a node in the present disclosure may mean an entity.

Meanwhile, the functions described below may be individually and independently performed. The functions described below may be implemented in any combination/combination, and it is obvious that this is also included in the scope of the present embodiment.

Arbitrary information about XR applications described below is statistically/empirically obtained/calculated/derived traffic characteristic information (e.g. expected value/average, deviation, standard deviation minimum, maximum, etc. ) can be Accordingly, any information contained herein may represent one or more of average (expected value)/minimum/maximum/standard deviation values. For example, if information called an update rate is described, this may mean an average (expected value)/minimum/maximum/standard deviation update rate. This is for convenience of description, and all information in this specification may be used as statistical information. Alternatively, it may be information preconfigured in the terminal/network or provisioned through OAM/application server/application function/UDM.

8 is a diagram for explaining an example of a structure for representing a 5G-XR function in a 5G system. For convenience of description, this specification is described based on FIG. 8, but as described above, this embodiment can be equally applied to any system/radio access technology (eg LTE, 6G).

Referring to FIG. 8 , 5G-XR AF represents an application function for 5G-XR service. 5G-XR AS represents an application server for 5G-XR service. 5G-XR Client represents internal terminal functions for 5G-XR service. Within a terminal, an XR client may represent a transceiver of an XR session accessed via APIs or the like by an XR application. The XR client can communicate/signal with the 5G-XR AF to establish/control/support the XR session (or delivery of the 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 signaling with PCF/NEF for QoS control. 5G-XR AS represents an application server that hosts 5G XR media and media functions.

Hereinafter, operations of a core network control plane node and a base station for effectively controlling XR application data traffic according to the present disclosure will be described.

9 is a diagram for explaining an operation of a core network control plane node according to an embodiment.

Referring to FIG. 9, in a method for controlling data traffic, a core network control plane node provides help information on application traffic characteristics from an application function control entity, PDU-Set QoS parameters, and flows belonging to multimodal applications. An information receiving step of receiving one or more information of an identifier for grouping s and a synchronization threshold may be performed (S910).

Here, the application traffic may mean specific data traffic such as XR.

For example, the help information on application traffic characteristics may include at least one of period information on uplink or downlink traffic of a QoS flow and jitter range information associated with the period information. That is, information on a period in which uplink or downlink of corresponding data traffic occurs or jitter range information interlocked with corresponding period information may be included in the help information for application traffic characteristics.

Period information for uplink or downlink traffic may support non-integer values. For example, period information for uplink or downlink traffic may be set as an integer value as well as a non-integer value. For example, period information may be set to support up to a decimal point, such as 0.XXXms.

As another example, the PDU-Set QoS parameter may include a parameter indicating a quality of service set in association with the PDU-Set.

As another example, an identifier for grouping flows belonging to a multimodal application may group one or more data flows belonging to an application configured to exchange information through various interfaces. In this case, corresponding grouping may be performed through an identifier for grouping flows belonging to a multimodal application. Alternatively, corresponding groups may be identified through an identifier for grouping flows belonging to a multimodal application.

As another example, the synchronization threshold may include threshold information about a delay time difference between flows associated with a multimodal application having one group identifier. Also, the synchronization threshold may be set in association with an identifier for grouping flows belonging to a multimodal application.

The aforementioned help information may be received from an application function or may be generated by a core network control plane node. When a core network control plane node generates help information, the help information may be generated by an application function.

On the other hand, the core network control plane node transmits one or more of help information on application traffic characteristics, PDU Set QoS parameters, identifiers for grouping flows belonging to multimodal applications, and synchronization thresholds to the base station during a PDU session establishment or modification procedure. An information transmission step may be performed (S920).

When the core network control plane node receives information from the application function control entity in step S910, it can deliver the information to the base station. To this end, the core network control plane entity may use an interface between the core network and the base station.

Alternatively, the core network control plane node may include the above-described information in a message used in a PDU session establishment or modification procedure and transmit it to the base station. For example, the aforementioned information may be included in a message defined within a corresponding procedure, such as a PDU session establishment/modification request message, a PDU session establishment/modification response message, and a PDU session establishment/modification completion message. As another example, the aforementioned information may be included in a PDU SESSION RESOURCE SETUP REQUEST message or a PDU SESSION RESOURCE MODIFY REQUEST message.

In addition, the core network control plane node may perform a control step to instruct transmission of user packets including PDU-Set information to the core network user plane node (S930).

The core network control plane node can control transmission of PDU-Set information for application data traffic to the core network user plane node. For example, a core network user plane node may be a User Plane Function (UPF).

The core network user plane node may transmit user plane information to the base station using the received PDU-Set information.

For example, the PDU-set information may include at least one of a PDU-Set sequence number, a PDU-Set end PDU, and a PDU-Set importance.

In addition, the core network user plane node may forward the received PDU-Set information to the base station.

Meanwhile, the order of steps S920 and S930 described above may be changed. That is, the core network control plane node may first transmit PDU-Set information to the core network user plane node, and then transmit the above-described application traffic related information to the base station. Alternatively, the core network control plane node may simultaneously transmit PDU-Set information and application traffic related information.

In addition to this, core network control plane nodes can transmit and receive various information with base stations and core network user plane nodes in order to effectively control application data traffic such as XR. Specific procedures and embodiments are described in more detail below.

10 is a diagram for explaining an operation of a base station according to an embodiment.

Referring to FIG. 10, in a method for controlling data traffic, a base station receives help information on application traffic characteristics from a core network control plane node, a PDU-Set QoS parameter, an identifier for grouping flows belonging to a multimodal application, and synchronization An information receiving step of receiving one or more of the threshold values may be performed (S1010).

For example, the help information on application traffic characteristics may include at least one of period information on uplink or downlink traffic of a QoS flow and jitter range information associated with the period information. That is, information on a period in which uplink or downlink of corresponding data traffic occurs or jitter range information interlocked with corresponding period information may be included in the help information for application traffic characteristics.

Period information for uplink or downlink traffic may support non-integer values. For example, period information for uplink or downlink traffic may be set as an integer value as well as a non-integer value. For example, period information may be set to support up to a decimal point, such as 0.XXXms.

As another example, the PDU-Set QoS parameter may include a parameter indicating a quality of service set in association with the PDU-Set.

As another example, an identifier for grouping flows belonging to a multimodal application may group one or more data flows belonging to an application configured to exchange information through various interfaces. In this case, corresponding grouping may be performed through an identifier for grouping flows belonging to a multimodal application. Alternatively, corresponding groups may be identified through an identifier for grouping flows belonging to a multimodal application.

As another example, the synchronization threshold may include threshold information about a delay time difference between flows associated with a multimodal application having one group identifier. Also, the synchronization threshold may be set in association with an identifier for grouping flows belonging to a multimodal application.

The aforementioned application functions or core network control plane nodes may also create them.

The base station may receive the above-described information through an interface between the core network and the base station. For example, the base station may receive the above information from the core network control plane node through a message used in a PDU session establishment or modification procedure. For example, the aforementioned information may be included in a message defined within a corresponding procedure, such as a PDU session establishment/modification request message, a PDU session establishment/modification response message, and a PDU session establishment/modification completion message. As another example, the aforementioned information may be included in a PDU SESSION RESOURCE SETUP REQUEST message or a PDU SESSION RESOURCE MODIFY REQUEST message.

The base station may perform a step of configuring a radio bearer for application traffic using the information received from the core network control plane node (S1020).

The base station may configure a radio bearer for application data traffic using the received information. The corresponding radio bearer may be set to match the characteristic information of application data traffic, and may be set to transmit and receive data according to a period set as a non-integer value.

Meanwhile, the base station may perform a step of receiving PDU-set information from the core network user plane node (S1030).

For example, the PDU-set information may include at least one of a PDU-Set sequence number, a PDU-Set end PDU, and a PDU-Set importance.

In addition, the core network user plane node may transmit PDU-Set information received from the core network control plane node to the base station.

Meanwhile, the order of steps S1020 and S1030 described above may be changed. That is, the base station may configure a radio bearer after receiving PDU-Set information, or may configure a radio bearer using application traffic related information received from a core network control plane node. If the base station configures the radio bearer after receiving the PDU-Set information, the radio bearer can be configured using the PDU-Set information and the aforementioned application traffic related information.

In addition to this, the base station can transmit and receive various information with the core network control plane node and the core network user plane node in order to effectively control application data traffic such as XR. Specific procedures and embodiments are described in more detail below.

Below, various embodiments for effectively processing specific application data traffic, such as XR, will be described in detail. Each of the embodiments described below may be applied individually or in combination with each other in any combination.

Additional examples of QoS characteristics for XR applications

In the conventional 5GS/NR technology, 5G QoS characteristics linked to 5QI are as follows.

One Resource type (Non-GBR, GBR, Delay-critical GBR);

2 Priority Level;

3 Packet Delay Budget (including Core Network Packet Delay Budget);

4 Packet Error Rate;

5 Averaging window (for GBR and Delay-critical GBR resource type only);

6 Maximum Data Burst Volume (for Delay-critical GBR resource type only).

5G QoS characteristic information can be used as a guideline for setting node-specific parameters for each QoS flow. Standardized or preconfigured 5G QoS characteristic information for XR (specific data traffic) may be defined and indicated through a 5QI value. Alternatively, the 5QI value may be indicated together with additional identification information and/or additional QoS characteristic information. For example, additional identification information and/or additional QoS characteristic information may be linked and indicated for a unit classified within an application or for a unit having correlation/dependency.

Signaled 5G QoS characteristic information may be provided as part of a QoS profile. For XR media delivery, it is typically offered on a download and adaptive streaming basis. Therefore, there is a part that can be adjusted through bit rate. However, QoS characteristic information may be added to effectively support QoS for various XR data streams such as viewpoint-dependent streaming.

For example, the XR terminal uses tracking information. Current pose information/tracking information may be transmitted to XR AF (Application Function)/AS (Application Server) in order to use pose information/tracking information in an adaptive media processing request. Pose information/tracking information may be shared/updated in order to access related information considering the current viewpoint. Tracking/sensor data within the XR device may be processed for XR rendering. Media can be sent/requested adaptively based on the viewpoint. Therefore, whether there is a unit/information that requires adaptive or differentiated request/response/processing/control within one flow, such as pause information/tracking information, and the unit/information that requires dependent processing/control within one flow At least one of existence, pause information/tracking/control information, information for identifying the corresponding information, information for linking the corresponding information, and QoS characteristic information of the corresponding information may be added/defined and signaled.

The pose information may represent a position and orientation in a space relative to the XR space.

- The position in the XR space is a 3D-vector representing the position within a space and relative to the origin defined by the (x,y,z) coordinates.

- The orientation in the XR space is a quaternion representing the orientation within a space and defined by a four-dimensional or homogeneous vector with (x,y,z,w) coordinates, with w being the real part of the quarternion and x, y and z the imaginary parts.

Tracking information includes pose information, position (of a specific node), orientation, rotation, corresponding node identifier being tracked, available tracking status provision status, current location of XR terminal (e.g. Head Mount Device) and one or more information of a center tracking an orientation, a direction, and a direction change.

For another example, QoS characteristic information considering periodic variable characteristics of the video stream may be added. For example, XR traffic can occur with a specific period and within +/- jitter. For example, the level/range of jitter occurring at a certain (arrival) period can be considered. And/or XR traffic may occur with a specific period and another specific range of sizes. For example, the maximum/minimum burst size/range of data occurring in a certain (arrival) period may be considered. For another example, QoS characteristic information considering the non-integer cycle (e.g. 30fps: 33.33ms, 60fps: 16.67ms, 90fps: 11.11ms, 120fps: 8.33ms) characteristics of XR (video) traffic may be added. Information for indicating this may be used for signaling.

For another example, one or more of information such as an update rate of a video stream for supporting XR applications, an update request/response, a packet size, a frame rate per second, and a roundtrip interaction delay tolerance may be added as QoS characteristic information. .

For another example, PDU-Set/MU specific QoS characteristic information may be added. For example, information for processing may be added in consideration of whether PDU-Set/MU units are requested for classification processing. Alternatively, information for linking and processing detailed flows/streams classified in PDU-Set/MU units within one QoS flow may be added. Alternatively, information (e.g. grouping identifier) for linking/grouping and processing detailed flows/streams classified in PDU-Set/MU units having dependencies (within one QoS flow) may be added. Alternatively, information for linking and processing detailed flows/streams classified in PDU-Set/MU units within one PDU session may be added. Alternatively, information for connection processing by classifying application traffic indicated by application/application layer/application server/PCF in units of PDU-Set/MU may be added.

For another example, the corresponding QoS characteristic information may be defined and applied as a QoS profile (or a QoS parameter included in the QoS profile). Corresponding QoS characteristic information may be indicated in association with 5QI. Alternatively, the corresponding QoS characteristic information may be indicated by defining an additional/linked QoS-flow/PDU-Set level sub-indicator/identification information for 5QI. For example, a 5QI value associated with PDU-Set level QoS characteristic information may be defined. This may be defined separately from the 5QI value associated with packet level QoS characteristic information. A 5QI mapping table associated with PDU-Set level QoS characteristic information, which is distinguished from a 5QI mapping table associated with packet level QoS characteristic information, may be defined. Alternatively, it may be defined by designating an unassigned 5QI value in a 5QI mapping table linked to packet level QoS characteristic information. For another example, information for distinguishing 5QI linked to a PDU-Set level QoS parameter may be defined and indicated.

A core network control plane node/entity (e.g. SMF/AMF) sends a message to the base station during the PDU session setup/modification procedure (via PDU SESSION RESOURCE SETUP REQUEST message or PDU SESSION RESOURCE MODIFY REQUEST message, or PDU Session Resource Setup Request in that message). Through Transfer IE or PDU Session Resource Modify Request Transfer IE), it may be indicated by including the corresponding 5QI/QoS characteristic information or the corresponding sub-indicator.

The base station can configure an SRB/DRB linked to the corresponding 5QI/QoS characteristic information/sub-indicator (consisting of the 5QI/QoS characteristic information/sub-indicator) in order to support scheduling considering the corresponding 5QI/QoS characteristic information. there is. The base station may include information for indicating this in the corresponding SRB / DRB configuration information through RRC signaling (e.g. RRC reconfiguration message) and transmit it to the terminal. Alternatively, the base station may link and configure a configuration necessary for transmitting the corresponding user plane data in consideration of the corresponding traffic characteristic information with the corresponding DRB configuration information through RRC signaling (e.g. RRC reconfiguration message). For example, one or more of configured grants, semi-persistent scheduling, and DRX configuration that considers/supports non-integerity of XR traffic can be configured in association with the corresponding DRB. Alternatively, one or more of the CQI tables for LCP restrictions, packet duplication, and a specific target block error rate (e.g. minus five powers of 10) may be configured for priority processing of a logical channel associated with the corresponding DRB. For example, it can be configured by mapping the corresponding logical channel to the configured grant configuration through RRC. Alternatively, the base station may allow the corresponding logical channel to use a dynamic grant indicating a specific physical priority level. Alternatively, for linking and processing detailed flows/streams having dependencies, the base station may include information for indicating linkage between corresponding DRBs for a DRB linked to the corresponding detailed flow/stream. Alternatively, for linking and processing detailed flows/streams, the base station may include information for indicating linkage between corresponding logical channels for a logical channel configuration associated with a DRB associated with a corresponding detailed flow/stream.

ADU (PDU-Set) / MU-based packet filter additional embodiment

In order to support effective delivery/transmission of corresponding XR data in a mobile communication network, an application/application layer may add and provide additional arbitrary metadata/control fields for each packet. For example, a field/information/indicator for distinguishing a specific data traffic/flow/stream/unit of a corresponding application may be included on the application header. Through corresponding fields/information/indicators, corresponding application streams/data/flows can be divided into detailed streams/data units/detailed flows/frames having different characteristics.

However, it may be difficult to utilize corresponding information/parameters on the application layer in all nodes of the mobile communication network. For example, (deep) packet inspection may be required to utilize that information. It may be desirable to perform this at an end-to-end node (e.g. UE, UPF) of a mobile communication network rather than at every node (e.g. UE, base station, UPF) that processes user plane data. Corresponding information may include any information generated on XR media processing (e.g. signaling, transmission, codec, format).

In the downlink, incoming data packets can be prioritized based on a packet filter set of downlink Packet Detection Rules (PDRs). UPF can carry user plane traffic classification belonging to one QoS flow through N3 User Plane marking using QFI. Alternatively, different user plane traffic (e.g. detail stream / data unit / detail flow / frame) belonging to one QoS flow is further classified using an identifier included in the present disclosure and / or a packet filter set described below. It can be carried through the corresponding N3 User Plane marking.

For that PDU session in the uplink, the UE evaluates the uplink packet against 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. )can do. The terminal may bind the uplink packet to the QoS flow using a QoS Flow Identifier (QFI) matching the corresponding QoS rule. Alternatively, the terminal additionally classifies different user plane traffic (e.g. detail stream/data unit/detail flow/frame) belonging to one QoS flow using a packet filter set described below and uses the identifier and/or Alternatively, the uplink packet may be bound to the corresponding detailed QoS flow using the corresponding additional indication information.

A core network entity (e.g. UPF) linked to a data network (DN) including an XR application or XR application server in a device or the server uses the information to transfer the corresponding application stream/flow/QoS-flow to different detailed streams/ It can be separated into data unit/detailed flow/frame. For example, a core network entity may classify a corresponding detail stream/data unit/detail flow/frame and add/mark the QFI to be mapped to different QoS flows. For another example, a core network entity can classify a corresponding application/QoS-flow within one application/QoS-flow and separate it into different detail streams/data units/detail flows/frames. In order to identify / distinguish them, detailed / additional identifiers associated with QFI / 5QI may be defined and marked. and/or detailed/additional identifiers (e.g. QFI/5QI/detailed indicators of dependent objects and/or groups having dependencies) to process by linking/grouping detailed streams/data units/detailed flows/frames with dependencies. group identifier) may be defined and marked.

A core network entity may associate a corresponding application stream/flow/QoS-flow with a detailed stream/data unit/detail flow/frame. Alternatively, an identifier that can be used in place of QFI/5QI may be defined and marked. Alternatively, the corresponding identifier may be signaled by applying 5QI dynamically allocated (defined by the operator). For example, the corresponding QoS characteristic information (e.g. dynamic 5QI descriptor IE) as part of the corresponding QoS profile with a non-standardized or non-preconfigured 5QI value may be signaled from the core network control plane entity to the base station.

For another example, there may be QoS flows that require linked QoS processing within a corresponding application. Information for grouping QoS flows requiring associated QoS flow processing may be defined. Information for identifying a group for QoS flows requiring QoS flow processing associated with the UE or UPF may be additionally marked. For another example, the representative/default QFI/5QI for one QoS-flow of the application and the QFI/5QI for the detailed stream/data unit/detail flow/frame linked to the corresponding QoS-flow may be linked/simultaneously provided. can

As described above, detailed streams/data units/detailed flows/frames can be distinguished through arbitrary fields/information included in the corresponding application header and information capable of distinguishing units within an application. Corresponding information can be received from the PCF to the core network entity (e.g. AMF/SMF/UPF) or from the XR application server/application function to the core network entity (eg AMF/SMF/UPF). and/or corresponding information may be set by local configuration.

The XR application in the terminal or the XR application server may separate the corresponding application stream into different sub-streams/data units/sub-flows/frames using the corresponding information. Separated application detail streams/data units/detail flows/frames may be distinguished by using one or more pieces of information from the following packet filters.

(For IP PDU session types) The packet filter set MUST support packet filters based on at least any combination of the following:

-ADU-type

- Fame-type: P-frame, I-frame, B-frame

- Traffic-type: voice, video, haptic, pose information, tracking information

- Media Units (MUs)-type: haptic information, updated pose information, tracking information video, voice,

- Priority/Importance indication

- Source/destination IP address or IPv6 prefix.

- Source / destination port number.

- Protocol ID of the protocol above IP/Next header type.

- Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask.

- Flow Label (IPv6).

- Security parameter index.

- Packet Filter direction.

- Application Identifier: Index for identifying the application detection rule set configured in UPF

- Application Identifier: Information to identify the (XR) application

- Information for identifying the corresponding packet filter set

For example, a UE or UPF may filter packets by PDU-Set/frame/Traffic/MU type within an arbitrary application. Signaling to indicate this may be provided. As an example, a core network control plane entity (e.g. SMF/AMF) can configure its packet filtering for that XR application (or for that application's QoS flow(s)) during the PDU session setup/modification procedure. there is. Alternatively, the core network control plane entity (e.g. SMF/AMF) may enable/disable corresponding packet filtering for the corresponding XR application (or for the QoS flow(s) of the corresponding application) during the PDU session establishment/modification procedure. . Alternatively, when the PCC rule is activated/deactivated by the PCF, the core network control plane entity (e.g. SMF/AMF) activates/deactivates/enforces the rule based on the corresponding packet filter within the UPF/terminal. One or more pieces of information included in one packet filter set and information for instructing activation/deactivation may be included and transmitted. For example, packet filtering in units of detailed stream/data unit/detail flow/frame may be activated/deactivated and effectively controlled.

The core network control plane entity may transmit information for instructing the UPF to request/activation/deactivation of filtering through a corresponding packet filter set. The core network control plane entity may transmit information for instructing the terminal to request/activation/deactivation of filtering through a corresponding packet filter set. Information for instructing packet filtering request/activation/deactivation may include the aforementioned information for corresponding packet filtering. Corresponding information may be received from the PCF or from the XR application server/application function. and/or corresponding information may be set by local configuration.

For another example, a core network control plane entity (e.g. SMF/AMF) may bind a policy and charging control (PCC) rule to a corresponding QoS flow/detail stream/data unit/detail flow/frame. SMF is one or more information included in QFI/5QI/dynamic-5QI-descriptor in one QoS flow/detail stream/data unit/detail flow/frame/information for identifying the corresponding detail stream/detail flow/the aforementioned QoS characteristics Allocate information and determine/derive a QoS profile. For example, the SMF may determine/derive the traffic jitter range associated with the uplink/downlink traffic period of the corresponding QoS flow. During the PDU session establishment/modification procedure, the SMF instructs the UPF to calculate/derive the traffic jitter range associated with the uplink/downlink traffic cycle of the QoS flow, and the UPF determines the uplink/downlink traffic cycle of the QoS flow. An associated traffic jitter range can be derived and transmitted to the SMF. Corresponding UPF instructions and QoS rules from PCC rules can be bound to corresponding QoS flows/detailstreams/dataunits/detailflows/frames provided by the PCF. For each PCC rule bound to the corresponding QoS flow/detail stream/data unit/detail flow/frame, the SMF is included in this specification to enable classification, bandwidth enforcement, and marking of user plane traffic. One or more pieces of arbitrary information (e.g. QoS characteristic information, packet marking information, packet filter set information, 5QI/QFI/subindicator) may be provided to the UPF.

UPF is additional information (e.g. any information included in this specification (e.g. QoS characteristic information, packet marking information, packet filter set information, 5QI / QFI / subindicator) in the GTP-U header having 5QI / QFI) ) can be encapsulated (encapsulate). Alternatively, UPF may encapsulate by including additional information in the GTP-U header associated with 5QI/QFI. Alternatively, additional information may be included in DL PDU session information included in the PDU session user plane protocol. Alternatively, UPF may include additional information when corresponding indication information is received/configured/applied/set (from another core network entity).

For another example, the base station may include and encapsulate additional information in the GTP-U header having 5QI/QFI. Alternatively, the UPF may encapsulate by including additional information in the GTP-U header associated with 5QI/QFI. Alternatively, additional information may be included in UL PDU session information included in the PDU session user plane protocol. Alternatively, the base station may include additional information when the corresponding indication information is received/configured/applied/set (from another core network entity).

For another example, the terminal performs classification and marking of uplink user plane traffic. QoS rules for this may be explicitly provided to the terminal. For example, a corresponding QoS rule may be signaled from a core network entity (AMF/SMF) to a terminal through a message within a procedure using a PDU session establishment/modification procedure. Alternatively, corresponding QoS rules may be pre-configured in the terminal.

The terminal additionally classifies different user plane traffic (e.g. detail stream / data unit / detail flow / frame) belonging to one QoS flow using the packet filter set described below, and the identifier and / or An uplink packet may be bound to a corresponding detailed QoS flow using the corresponding additional indication information.

The base station may instruct the terminal with configuration information for linking/mapping the corresponding QoS flow/detail stream/data unit/detail flow/frame to the DRB through RRC signaling (e.g. RRC reconfiguration message).

For example, the SDAP configuration includes one or more information included in the QFI, 5QI, and dynamic-5QI-descriptor for the QoS flow/detail stream/data unit/detail flow/frame to be mapped, the corresponding detail stream/data unit/detail flow/ It may include one or more of information for identifying a frame and the aforementioned QoS characteristic information.

For another example, the corresponding SDAP may be defined and used to have a header of a format different from that of the SDAP header for the DL Data PDU having the RDI, RQI, and QFI fields. For example, the corresponding header includes one or more information included in QFI, 5QI, and dynamic-5QI-descriptor for QoS flow/detail stream/data unit/detail flow/frame without RDI and RQI fields, corresponding detail stream/data unit/detail flow / It may be configured by including/adding one or more information/fields among information for identifying a frame, the aforementioned QoS characteristic information, and header version information. As another example, the corresponding header identifies one or more information included in the QFI, 5QI, and dynamic-5QI-descriptor for the QoS flow/detail stream/data unit/detail flow/frame, and identifies the corresponding detail stream/data unit/detail flow/frame. It may be configured by including/adding one or more information/fields among information for the above-described QoS characteristics, and header version information.

For another example, the corresponding SDAP may be defined and used to have a header of a different format from the SDAP header for the UL Data PDU having the D/C, R, and QFI fields. For example, the header is one or more pieces of information included in QFI, 5QI, and dynamic-5QI-descriptor for QoS flow/detail stream/data unit/detail flow/frame, to identify the corresponding detail stream/data unit/detail flow/frame It may be configured by including/adding one or more information/fields among information for the above-described QoS characteristics, and header version information.

Information included in the aforementioned arbitrary signaling / terminal operation / core network entity (AMF / SMF / PCF / UPF / NEF / AF) operation / base station operation is information for distinguishing units within applications, header information within applications, ( PDU-Set-type/frame-type/traffic-type/MU-type identified through information for identifying units within the application, or identifier/index information for identifying them, and detailed streams that require associated QoS flow processing /Data unit/subflow/information for identifying groups for frames, QFI, PDU-Set linked to QFI/frame/MU/traffic/substream/subindicator/identifier/index information for identifying subflow , sequence number in PDU-Set-type/frame-type/traffic-type/MU-type, PDU-Set-type/frame-type/traffic-type/MU-type in detail stream/data unit/detail flow/frame endpoint (e.g. Indicates if this is the last packet in the unit, information indicating the end/last PDU of the corresponding PDU Set), data/traffic/service type (The data type of the unit, PDU-Set/frame /Traffic/MU type), importance/priority (assigned relative Priority/importance information in the same flow), corresponding unit/packet creation/transmission timestamp/local time, corresponding unit/packet reception timestamp/local time, downlink /uplink jitter (e.g. the sum of the jitter incurred in NG-RAN (including the jitter at gNB-CU-UP, on F1-U and on gNB-DU) and the jitter over Uu interface, or arrival/receive/transmit of actual units at specific/instructed/preconfigured time points for the corresponding PDU-Set/frame/MU/traffic/substream/subflow difference between points), corresponding downlink/uplink jitter indication information (e.g. 1-bit information to indicate the existence of the corresponding information), downlink/uplink delay (e.g. the sum of the delay incurred in NG-RAN for the corresponding PDU-Set/frame/MU/traffic/substream/subflow including the delay at gNB-CU-UP, on F1-U and on gNB-DU) and the delay over Uu interface), corresponding downlink/uplink delay indication information (e.g. 1-bit information to indicate the existence of the corresponding information) ), and one or more pieces of arbitrary information for distinguishing units through fields/information included by the application header.

Example of ordering XR-related information through core network help information/device help information/NAS signaling

The core network entity may provide help information for supporting effective scheduling of XR data to the base station. Alternatively, the terminal may provide help information for supporting effective scheduling of XR data to the base station/core network entity.

During the PDU session establishment/modification procedure or during handover, the base station may receive assistance information from the core network control plane entity. A core network control plane entity (e.g. SMF/AMF) sends a message to the base station during the PDU session setup/modification procedure (via PDU SESSION RESOURCE SETUP REQUEST message or PDU SESSION RESOURCE MODIFY REQUEST message, or PDU Session Resource Setup Request Transfer IE in that message). Alternatively, the corresponding help information can be transmitted through PDU Session Resource Modify Request Transfer IE. The help information received from the corresponding core network control plane entity may include information about the corresponding XR traffic flow. For example, help information may include corresponding traffic characteristic information. burst arrival time, periodicity, flow/detailstream/dataunit/detailflow/frame direction, level/range of jitter occurring in a specific arrival period, maximum/minimum burst size/range of data occurring in a specific arrival period, XR application To support (pause information/tracking information/control information) update/change/sampling rate/period/duration, packet size, frame rate per second, roundtrip interaction delay tolerance, multi-modal synchronization threshold, multi-detail stream/data unit One or more information of /detailflow/inter-frame synchronization threshold, multi-modal detailstream/data unit/detailflow/frame association/grouping information may be added as QoS characteristic information. Alternatively, one or more of the QoS characteristics information for the aforementioned XR application may be included. Alternatively, one or more pieces of information included in the aforementioned packet filter set may be included. Alternatively, one or more pieces of information included in the aforementioned arbitrary signaling/terminal operation/core network entity (AMF/SMF/PCF/UPF/NEF/AF) operation/base station operation may be included.

The aforementioned help information may be defined as a core network entity (e.g. AMF/SMF) linkage parameter and transmitted to the base station. For example, AMF/SMF can induce corresponding help information. For example, through PDU session setup/modification/release procedures and corresponding QoS characteristic information provided through NAS signaling, a core network entity can derive corresponding information based on statistics/patterns for a corresponding application. there is. For example, the aforementioned help information may be statistical/empirically obtained/calculated/derived traffic/QoS characteristic information (e.g. expected value/average, deviation, standard deviation, minimum, maximum, etc. arbitrary statistics/statistics). If the corresponding parameter value is changed, a PDU session modification procedure may be applied. The core network entity (e.g. AMF/SMF) can store the corresponding parameter in the PDU session context. Corresponding parameters may be linked to detail stream/data unit/detail flow/frame.

The terminal/application server/application function can provide the policy for the flow/detail stream/data unit/detail flow/frame linked to the application as a core network entity (eg AMF/SMF/PCF). The corresponding policy may include one or more information of a terminal and a data flow set, a triggering event associated with expected QoS handling, and coordination information. The corresponding policy may be transmitted to AMF/SMF through Network Exposure Function (NEF). For example, corresponding information may be transmitted when a corresponding application session is established/modified or when a corresponding parameter value is changed. The corresponding information is a data flow set associated with an application and may include tactile and/or multi-modal data. Multi-modal data is defined as describing input data from different types of devices/sensors or output data to different destinations (e.g. one or more UEs) required for the same task or application. Multimodal data consists of more than one single modal data. And each single modal data has a strong dependency on each other. Single modal data can be viewed as one type of data. By combining inputs from more than one source and/or outputs from more than one destination, smoother and more natural communication may be possible.

Multi-modal synchronization thresholds may be defined. It can be defined as the temporal separation of the onset of the two maximally tolerable stimuli (e.g. one sensation and another). In this way, the accompanying sensory objects can be perceived as synchronized. For example, voice and touch should have synchronization thresholds within at least +/- 40 ms accuracy.

Video/audio media for that application, information perceived from sensors about the environment (e.g. brightness, temperature, humidity, etc.), haptic data (feel when touching a surface (e.g., pressure, texture, vibration, temperature), or kinesthetic senses (e.g. gravity, pull forces, sense of position awareness). For example, the sampling rate of a haptic device for teleoperation can reach 1000 times per second.

The terminal/application function/application server may provide information including application traffic characteristics and/or service/QoS requirements to the base station/core network entity (AMF/SMF/PCF). For example, the packet size for haptic data is related to DOF (Degrees Of Freedom) supported by the haptic device, and the packet size for one DOF is 2-8 Bytes, and the haptic device can generate and transmit 500 haptic packets per second. . The application server can transmit audio/video data and haptic data with different cycles. For example, if a video associated with one session is transmitted at 60 frames per second and the sampling rate for haptic information associated with the session is 500 times per second, the application transmits packets related to the video frame every 16.7 ms. and transmit packets including the corresponding haptic information every 2 ms. Video data and haptic data may be delivered through two separate service data flows of one single session. Alternatively, video data and haptic data may be transferred through separate service data flows of two sessions.

For another example, corresponding help information may be provisioned/provided to AMF/SMF/PCF through NEF in the application server OAM (Operations, Administration and Maintenance). Alternatively, the corresponding help information may be provisioned/provided from AF to AMF/SMF/PCF. Alternatively, the corresponding help information may be determined by a node providing a specific function for the corresponding XR application (for convenience of explanation, it is referred to as XRF (XR Function)) and provisioned/provided as AMF/SMF/PCF.

For another example, corresponding help information may be transmitted to a core network entity through NAS signaling. For example, a terminal may transmit control stream/data/information to a core network entity/application function/application server through NAS signaling for effective control of a corresponding application. For another example, the terminal may transmit pose information (or updated pose information) to a core network entity (e.g. AMF, SMF)/application function/application server through NAS signaling for an adaptive media control request. For another example, the terminal may transmit desired/expected traffic characteristic information or QoS characteristic information to the core network entity (e.g. AMF, SMF)/application function/application server through NAS signaling for corresponding application control. there is.

For another example, the corresponding assistance information may be transmitted to the base station through a UE assistance information RRC message (or any uplink RRC message). The terminal may configure an inhibit timer for limiting the transmission of the corresponding help information in the terminal. When the terminal initiates transmission of the terminal help information message including the corresponding information, it may start by setting the inhibit timer associated with the corresponding information to the timer value received from the base station. If the terminal has not provided the terminal's help information since it was configured to provide the corresponding information, if the current terminal's help information is different from that indicated in the last transmission of the terminal's help information message including the terminal's help information, and the corresponding inhibit timer operates. If not, the terminal may start a timer set to a timer value indicated by the base station. The terminal may initiate transmission of the terminal help information message to the base station.

For another example, the corresponding help information may be transmitted to the base station through MAC CE. The MAC entity may configure a bar timer for limiting the transmission of the corresponding help information in the terminal. If the corresponding inhibit timer is not in operation, the terminal may generate and transmit a MAC CE to the base station. The terminal may start the corresponding inhibit timer. The base station may instruct the terminal with information for indicating that the transmission/function of the corresponding MAC CE is supported/allowed/requested. For example, it may be instructed to the terminal through system information. Alternatively, it may be instructed to the terminal through an RRC reconfiguration message. Alternatively, it may be indicated through the downlink MAC CE.

As described above, the present embodiments additionally utilize information/fields used on services/applications being executed from upper layers to link detailed QoS flows, fame-level QoS, ADU-based QoS, XR specific It has the effect of supporting QoS.

Below, the configuration of the aforementioned core network control plane entity and base station will be described once again.

11 is a diagram showing the configuration of a core network control plane node according to another embodiment.

Referring to FIG. 11, the core network control plane node 1100 controlling data traffic provides help information on application traffic characteristics, PDU-Set QoS parameters, flows belonging to multimodal applications from an application function control entity. Grouping flows belonging to multimodal applications, PDU Set QoS parameters, and help information on application traffic characteristics to the base station during a PDU session setup or modification procedure with the receiving unit 1130 receiving one or more information of an identifier for grouping PDUs and a synchronization threshold. It may include a transmitter 1120 for transmitting at least one of an identifier and a synchronization threshold to transmit, and a control unit 1110 for instructing transmission of a user packet including PDU-Set information to a core network user plane node.

For example, the help information on application traffic characteristics may include at least one of period information on uplink or downlink traffic of a QoS flow and jitter range information associated with the period information. That is, information on a period in which uplink or downlink of corresponding data traffic occurs or jitter range information interlocked with corresponding period information may be included in the help information for application traffic characteristics.

Period information for uplink or downlink traffic may support non-integer values. For example, period information for uplink or downlink traffic may be set as an integer value as well as a non-integer value.

As another example, the PDU-Set QoS parameter may include a parameter indicating a quality of service set in association with the PDU-Set.

As another example, an identifier for grouping flows belonging to a multimodal application may group one or more data flows belonging to an application configured to exchange information through various interfaces. In this case, corresponding grouping may be performed through an identifier for grouping flows belonging to a multimodal application. Alternatively, corresponding groups may be identified through an identifier for grouping flows belonging to a multimodal application.

As another example, the synchronization threshold may include threshold information about a delay time difference between flows associated with a multimodal application having one group identifier. Also, the synchronization threshold may be set in association with an identifier for grouping flows belonging to a multimodal application.

The aforementioned help information may be received from an application function or may be generated by a core network control plane node. When a core network control plane node generates help information, the help information may be generated by an application function.

When receiving information from the application function control entity, the transmitter 1120 may transmit the corresponding information to the base station. To this end, the transmitter 1120 may use an interface between the core network and the base station.

Alternatively, the transmitter 1120 may include the above-described information in a message used in a PDU session establishment or modification procedure and transmit it to the base station. For example, the aforementioned information may be included in a message defined within a corresponding procedure, such as a PDU session establishment/modification request message, a PDU session establishment/modification response message, and a PDU session establishment/modification completion message. As another example, the aforementioned information may be included in a PDU SESSION RESOURCE SETUP REQUEST message or a PDU SESSION RESOURCE MODIFY REQUEST message.

The controller 1110 may control PDU-Set information for application data traffic to be transmitted to the core network user plane node. For example, a core network user plane node may be a User Plane Function (UPF). The core network user plane node may transmit user plane information to the base station using the received PDU-Set information.

For example, the PDU-set information may include at least one of a PDU-Set sequence number, a PDU-Set end PDU, and a PDU-Set importance. In addition, the core network user plane node may forward the received PDU-Set information to the base station.

In addition to this, the control unit 1110 controls traffic based on traffic characteristics identified based on information/fields used on services/applications running from upper layers in the traffic control method necessary to perform the present disclosure described above. The operation of the overall core network control plane node 1100 according to the method is controlled.

The transmission unit 1120 and the reception unit 1130 are used to transmit and receive signals, messages, and data required to perform the present embodiment described above to a base station and other core network entities.

12 is a diagram showing the configuration of a base station according to another embodiment.

Referring to FIG. 12, a base station 1200 controlling data traffic receives help information on application traffic characteristics from a core network control plane node, a PDU-Set QoS parameter, an identifier for grouping flows belonging to a multimodal application, and synchronization It includes a receiving unit 1230 that receives information on one or more of the threshold values and a control unit 1210 that configures a radio bearer for application traffic using information received from a core network control plane node. The receiver 1230 may further receive PDU-set information from the core network user plane node.

For example, the help information on application traffic characteristics may include at least one of period information on uplink or downlink traffic of a QoS flow and jitter range information associated with the period information. That is, information on a period in which uplink or downlink of corresponding data traffic occurs or jitter range information interlocked with corresponding period information may be included in the help information for application traffic characteristics.

Period information for uplink or downlink traffic may support non-integer values. For example, period information for uplink or downlink traffic may be set as an integer value as well as a non-integer value. For example, period information may be set to support up to a decimal point, such as 0.XXXms.

As another example, the PDU-Set QoS parameter may include a parameter indicating a quality of service set in association with the PDU-Set.

As another example, an identifier for grouping flows belonging to a multimodal application may group one or more data flows belonging to an application configured to exchange information through various interfaces. In this case, corresponding grouping may be performed through an identifier for grouping flows belonging to a multimodal application. Alternatively, corresponding groups may be identified through an identifier for grouping flows belonging to a multimodal application.

As another example, the synchronization threshold may include threshold information about a delay time difference between flows associated with a multimodal application having one group identifier. Also, the synchronization threshold may be set in association with an identifier for grouping flows belonging to a multimodal application. The aforementioned information may be generated by an application function or a core network control plane node.

The receiving unit 1230 may receive the aforementioned information through an interface between the core network and the base station. For example, the base station may receive the above information from the core network control plane node through a message used in a PDU session establishment or modification procedure. For example, the aforementioned information may be included in a message defined within a corresponding procedure, such as a PDU session establishment/modification request message, a PDU session establishment/modification response message, and a PDU session establishment/modification completion message. As another example, the aforementioned information may be included in a PDU SESSION RESOURCE SETUP REQUEST message or a PDU SESSION RESOURCE MODIFY REQUEST message.

The controller 1210 may configure a radio bearer for application data traffic using the received information. The corresponding radio bearer may be set to match the characteristic information of application data traffic, and may be set to transmit and receive data according to a period set as a non-integer value.

Meanwhile, the PDU-set information may include at least one of a PDU-Set sequence number, a PDU-Set end PDU, and a PDU-Set importance.

In addition, the core network user plane node may transmit PDU-Set information received from the core network control plane node to the base station.

In addition to this, the control unit 1210 controls traffic based on traffic characteristics identified based on information/fields used for services/applications running from upper layers in the traffic control method necessary to perform the present disclosure described above. The overall operation of the base station 1200 according to the method is controlled.

The transmission unit 1220 and the reception unit 1230 are used to transmit and receive signals, messages, and data required to perform the present embodiment described above to terminals and core network entities.

The above-described embodiments may be supported by standard documents disclosed in at least one of IEEE 802, 3GPP, and 3GPP2, which are wireless access systems. That is, among the present embodiments, steps, configurations, and parts not described to clearly reveal the present technical idea may be supported by the above-mentioned standard documents. In addition, all terms disclosed in this specification can be explained by the standard documents disclosed above.

The present embodiments described above may be implemented through various means. For example, the present embodiments may be implemented by hardware, firmware, software, or a combination thereof.

In the case of hardware implementation, the method according to the present embodiments includes one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), processors, controllers, microcontrollers, or microprocessors.

In the case of implementation by firmware or software, the method according to the present embodiments may be implemented in the form of a device, procedure, or function that performs the functions or operations described above. The software codes may be stored in a memory unit and driven by a processor. The memory unit may be located inside or outside the processor and exchange data with the processor by various means known in the art.

Also, the terms "system", "processor", "controller", "component", "module", "interface", "model", or "unit" as described above generally refer to computer-related entities hardware, hardware and software. can mean a combination of, software or running software. For example, but is not limited to, a process driven by a processor, a processor, a controller, a control processor, an object, a thread of execution, a program, and/or a computer. For example, a component can be both an application running on a controller or processor and a controller or processor. One or more components may reside within a process and/or thread of execution, and components may reside on one device (eg, system, computing device, etc.) or may be distributed across two or more devices.

The above description is merely illustrative of the technical idea of the present disclosure, and various modifications and variations can be made to those skilled in the art without departing from the essential characteristics of the technical idea. In addition, since the present embodiments are not intended to limit the technical idea of the present disclosure, but to explain, the scope of the present technical idea is not limited by these embodiments. The scope of protection of the present disclosure should be construed by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of rights of the present disclosure.

Claims (20)

In the method for a core network control plane node to control data traffic,
An information receiving step of receiving one or more of information from an application function control entity of help information on application traffic characteristics, a PDU-Set QoS parameter, an identifier for grouping flows belonging to a multimodal application, and a synchronization threshold;
An information transmission step of transmitting one or more of help information for the application traffic characteristics, the PDU Set QoS parameter, an identifier for grouping flows belonging to the multimodal application, and the synchronization threshold to a base station during a PDU session establishment or modification procedure; and
A method comprising controlling a core network user plane node to instruct transmission of a user packet including PDU-Set information. According to claim 1,
The help information for the application traffic characteristics,
A method comprising at least one of period information for uplink or downlink traffic of a QoS flow and jitter range information associated with the period information. According to claim 2,
Period information for the uplink or downlink traffic,
A method characterized by supporting non-integer values. According to claim 1,
The synchronization threshold is,
Includes threshold information on a delay time difference between flows associated with a multimodal application having one group identifier,
characterized in that it is set in association with an identifier for grouping flows belonging to the multimodal application. According to claim 1,
The PDU-set information,
Includes at least one information of a PDU-Set sequence number, a PDU-Set end PDU, and a PDU-Set importance;
characterized in that it is transmitted to the base station by the core network user plane node. A method for controlling data traffic by a base station,
an information receiving step of receiving one or more of information from a core network control plane node of help information on application traffic characteristics, a PDU-Set QoS parameter, an identifier for grouping flows belonging to a multimodal application, and a synchronization threshold;
configuring a radio bearer for application traffic using information received from the core network control plane node; and
A method comprising receiving PDU-set information from a core network user plane node. According to claim 6,
The help information for the application traffic characteristics,
A method comprising at least one of period information for uplink or downlink traffic of a QoS flow and jitter range information associated with the period information. According to claim 7,
Period information for the uplink or downlink traffic,
A method characterized by supporting non-integer values. According to claim 6,
The synchronization threshold is,
Includes threshold information on a delay time difference between flows associated with a multimodal application having one group identifier,
characterized in that it is set in association with an identifier for grouping flows belonging to the multimodal application. According to claim 6,
The PDU-set information,
A method of including at least one information of a PDU-Set sequence number, a PDU-Set end PDU, and a PDU-Set importance. In the core network control plane node for controlling data traffic,
A receiving unit that receives at least one of information about application traffic characteristics, PDU-Set QoS parameters, an identifier for grouping flows belonging to a multimodal application, and a synchronization threshold from an application function control entity;
a transmitter for transmitting at least one of help information on the application traffic characteristics, the PDU Set QoS parameter, an identifier for grouping flows belonging to the multimodal application, and the synchronization threshold to a base station during a PDU session establishment or modification procedure; and
A core network control plane node including a control unit that controls transmission of user packets including PDU-Set information to core network user plane nodes. According to claim 11,
The help information for the application traffic characteristics,
A core network control plane node comprising at least one of period information on uplink or downlink traffic of a QoS flow and jitter range information associated with the period information. According to claim 12,
Period information for the uplink or downlink traffic,
A core network control plane node, characterized in that it supports non-integer values. According to claim 11,
The synchronization threshold is,
Includes threshold information on a delay time difference between flows associated with a multimodal application having one group identifier,
A core network control plane node, characterized in that it is set in association with an identifier for grouping flows belonging to the multimodal application. According to claim 11,
The PDU-set information,
Includes at least one information of a PDU-Set sequence number, a PDU-Set end PDU, and a PDU-Set importance;
The core network control plane node, characterized in that transmitted to the base station by the core network user plane node. In the base station for controlling data traffic,
a receiver receiving one or more of information from a core network control plane node of help information on application traffic characteristics, a PDU-Set QoS parameter, an identifier for grouping flows belonging to a multimodal application, and a synchronization threshold; and
A control unit configuring a radio bearer for application traffic using information received from the core network control plane node;
The base station comprising the receiving unit further receiving PDU-set information from a core network user plane node. 17. The method of claim 16,
The help information for the application traffic characteristics,
A base station including at least one of period information for uplink or downlink traffic of a QoS flow and jitter range information associated with the period information. 18. The method of claim 17,
Period information for the uplink or downlink traffic,
A base station characterized in that it supports non-integer values. 17. The method of claim 16,
The synchronization threshold is,
Includes threshold information on a delay time difference between flows associated with a multimodal application having one group identifier,
A base station characterized in that it is set in association with an identifier for grouping flows belonging to the multimodal application. 17. The method of claim 16,
The PDU-set information,
A base station including at least one information of a PDU-Set sequence number, a PDU-Set end PDU, and a PDU-Set importance.

Images