Packet data processing method and device

By using high-level information to configure wireless resources in the radio network, the problem of traffic feature recognition and processing of XR application is solved, and the effective processing of traffic of XR application is realized, and data transmission efficiency and responsiveness are improved.

CN119072909APending Publication Date: 2024-12-03KT CORP

Patent Information

Application Number
CN202380035695.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-04-07
Filing Date
2023-04-19
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

Existing mobile communication technologies fail to effectively identify and process the characteristics of augmented reality (XR) application traffic, resulting in the inability of terminals, base stations, or core networks to effectively process XR application traffic in radio networks.

Method used

By using information provided by the high-level/application layer in a wireless network, wireless resource configuration information is configured to process application data flow, including sending and receiving wireless resource configuration information between a user equipment (UE) and a base station to distinguish processing application data flow .

Benefits of technology

It realizes effective identification and processing of XR application traffic in radio networks, improves the efficiency and responsiveness of data transmission, and is suitable for high throughput and low latency XR and cloud gaming scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072909A_ABST
    Figure CN119072909A_ABST
Patent Text Reader

Abstract

The present disclosure relates to a technique for processing packet data. An embodiment of the present invention provides a method and an apparatus for processing an application data stream by a user equipment, the method comprising the steps of: receiving a high-level message including radio resource configuration information configured to be used for transmitting or receiving specific application data; configuring wireless resource configuration information in the user equipment; and performing distinguishing processing on user plane data of the application data based on the wireless resource configuration information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a technique for processing packet data. Background Art

[0002] Extended reality (XR) and cloud gaming (CG) are broad terms that refer to various types of augmented, virtual, and hybrid environments in human-machine and human-to-human communications with the help of handheld and wearable terminals. Extended reality (XR) is a broad term that covers augmented reality (AR), mixed reality (MR), and virtual reality (VR). Cloud gaming represents a use case where most of the computations related to gaming are offloaded from the terminal to the edge or remote servers. XR applications and cloud computing / gaming typically require high throughput and low latency.

[0003] Many XR and CG use cases are characterized by quasi-periodic traffic with high data rates (possibly with jitter) in downlink video streams paired with frequent uplinks (e.g., attitude / control updates) and / or uplink video streams. Both downlink and uplink traffic must adhere to relatively tight packet delay budgets (PDBs).

[0004] In addition, many XR and CG terminals have limited battery power. However, due to the non-integer periodic XR traffic, variable XR data rate, and quasi-periodic nature of the XR cycle, the current UE discontinuous reception (DRX) configuration is not suitable.

[0005] The set of XR and CG services is diverse. When the service is run over a radio network (such as NR), the data stream (such as video) may change dynamically.

[0006] Therefore, data packets within the same frame are interdependent. However, existing mobile communication technologies do not provide specific methods for terminals, base stations or core networks to effectively identify and process XR application traffic. Summary of the invention Technical issues

[0007] In the above background, the present disclosure proposes a configuration method and apparatus for providing packet data processing that takes into account application traffic characteristics by utilizing information provided by an upper layer / application layer in a wireless network. Technical Solution

[0008] On the one hand, the present disclosure provides a method for processing an application data stream by a user equipment (UE), which may include: receiving a high-level message containing wireless resource configuration information, wherein the wireless resource configuration information is configured for sending / receiving specific application data; configuring the wireless resource configuration information in the UE; and performing differentiated processing on user plane data of the application data according to the wireless resource configuration information.

[0009] On the other hand, the present disclosure provides a method for processing an application data stream by a base station, which may include: sending a high-layer message including wireless resource configuration information to a UE, wherein the wireless resource configuration information is configured for sending / receiving specific application data; and performing differentiated processing on user plane data of the application data based on the wireless resource configuration information.

[0010] On the other hand, the present disclosure provides a user equipment (UE) for processing an application data stream, which UE may include: a receiver for receiving a high-layer message including wireless resource configuration information, wherein the wireless resource configuration information is configured for sending / receiving specific application data; and a controller for configuring the wireless resource configuration information in the UE and performing differentiated processing on user plane data of the application data based on the wireless resource configuration information.

[0011] On the other hand, the present disclosure provides a base station for processing an application data stream, which may include: a transmitter, which sends a high-layer message including wireless resource configuration information to a UE, wherein the wireless resource configuration information is configured for sending / receiving specific application data; and a controller, which differentiates and processes user plane data of the application data based on the wireless resource configuration information. Effects of the Invention

[0012] According to this embodiment, the following effects are provided: a UE, a base station or a core network entity in a radio network can effectively identify and process XR application traffic. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 Schematic diagram of an NR wireless communication system according to an embodiment of the present disclosure.

[0014] Figure 2 is a diagram schematically showing a frame structure in an NR system according to an embodiment of the present disclosure.

[0015] Figure 3 is a diagram for explaining a resource grid supported by a radio access technology according to an embodiment of the present disclosure.

[0016] Figure 4 2 is a diagram for explaining a bandwidth portion supported by a radio access technology according to an embodiment of the present disclosure.

[0017] Figure 5 is a diagram showing an example of a synchronization signal block in a wireless access technology according to an embodiment of the present disclosure.

[0018] Figure 6 It is a signal diagram for explaining a random access procedure in a wireless access technology according to an embodiment of the present disclosure.

[0019] Figure 7 This is a diagram for explaining CORESET.

[0020] Figure 8 is a diagram showing a structural example for implementing a 5G-XR function in a 5G system.

[0021] Fig. 9 is a flowchart illustrating the operation of a UE according to an embodiment.

[0022] Fig.10 is a flowchart for describing the operation of a base station according to an embodiment.

[0023] Fig.11 is a diagram exemplarily illustrating a PDU session resource establishment request transmission information element according to an embodiment.

[0024] Fig.12 is a diagram exemplarily illustrating a PDU session resource modification request transmission information element according to an embodiment.

[0025] Fig.13 is a diagram exemplarily showing SDAP configuration information elements according to an embodiment.

[0026] Fig.14 is a diagram exemplarily illustrating a PDU session resource establishment request transmission information element according to another embodiment.

[0027] Fig.15 is a diagram exemplarily illustrating a PDU session resource modification request transmission information element according to another embodiment.

[0028] Fig.16 is a diagram exemplarily showing SDAP configuration information elements according to another embodiment.

[0029] Fig.17 is a diagram showing a DL SDAP data PDU format with an SDAP header according to an embodiment.

[0030] Fig.18 is a diagram showing a UL SDAP data PDU format with an SDAP header according to an embodiment.

[0031] Fig.19 is a block diagram showing a UE according to an embodiment.

[0032] Fig. 20 is a block diagram showing a base station according to an embodiment. DETAILED DESCRIPTION

[0033] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to the schematic drawings. When adding reference numerals to the constituent elements of each drawing, the same reference numerals are assigned to the same constituent elements as much as possible, even if they are shown on different drawings. In addition, when describing the embodiments of the present disclosure, when the detailed description of the associated known configurations and functions may make the subject matter of the technical concept of the present disclosure unclear, the detailed description will be omitted. When the expressions "including", "having", "consisting of...", etc. as mentioned in this specification are used, any other parts may be added unless the expression "only" is used. When a constituent element is expressed in the singular, the constituent element may cover the plural case unless there is a clear and special reference to the constituent element.

[0034] In addition, when describing the constituent elements of the present disclosure, terms such as first, second, A, B, (a), (b), etc. may be used herein. These terms are not used to limit the nature, order, sequence or quantity of the corresponding constituent elements, but are only used to distinguish the corresponding constituent elements from other constituent elements.

[0035] When describing the positional relationship between constituent elements, if two or more constituent elements are mentioned as being "connected," "combined," or "accessed" to each other, it should be understood that the two or more constituent elements may be directly "connected," "combined," or "accessed" to each other, and the two or more constituent elements may be "connected," "combined," or "accessed" to each other with another constituent element "interposed" therebetween. In this case, the other constituent element may be included in at least one of the two or more constituent elements that are "connected," "combined," or "accessed" to each other.

[0036] In the description of the temporal relationship related to constituent elements, operating methods or manufacturing methods, for example, when expressions such as "after", "subsequently", "next", "before", etc. are used to describe the time sequence or process sequence, discontinuous situations may also be covered unless "immediately" or "directly" is used otherwise.

[0037] In addition, the numerical values ​​used for constituent elements or information corresponding thereto (e.g., levels, etc.) mentioned in this specification may be interpreted as including error ranges caused by various factors (e.g., process factors, internal or external impacts, noise, etc.), even if not otherwise explicitly stated.

[0038] The wireless communication system in this specification refers to a system that uses wireless resources to provide various communication services (such as voice services and data services), and may include UE, base stations, core networks, etc.

[0039] The embodiments of the present disclosure disclosed below can be applied to wireless communication systems using multiple wireless access technologies. For example, the embodiments can be applied to multiple wireless access technologies, such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), non-orthogonal multiple access (NOMA), etc. In addition, wireless access technology can refer not only to specific access technology, but also to various generations of communication technologies established by various communication organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, ITU, etc. For example, CDMA can be implemented as wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as wireless technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rate for GSM Evolution (EDGE). OFDMA can be implemented into wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802-20, Evolved UTRA (E-UTRA), etc. IEEE802.16m is an evolution of IEEE802.16e, which provides backward compatibility with systems based on IEEE802.16e. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) using Evolved UMTS Terrestrial Radio Access (E-UTRA), using OFDMA for the downlink and SC-FDMA for the uplink. As described above, the embodiments of the present disclosure can be applied to wireless access technologies that have been launched or commercialized, and can also be applied to wireless access technologies that are being developed or will be developed in the future.

[0040] In addition, the terminal used in this specification should be interpreted as indicating a broad meaning of a device including a wireless communication module that communicates with a base station in a wireless communication system, which includes not only user equipment (UE) in WCDMA, LTE, NR, HSPA, IMT-2020 (5G or new wireless), etc., but also mobile stations (MS), user terminals (UT), subscriber stations (SS), wireless devices, etc. in GSM. In addition, the terminal may be a portable user device such as a smart phone, or a vehicle, a device including a wireless communication module in a vehicle, etc. in a V2X communication system, depending on its usage type. In the case of a machine type communication (MTC) system, the terminal may refer to an MTC terminal, an M2M terminal, or a URLLC terminal, etc., which is equipped with a communication module capable of performing machine type communication.

[0041] The base station or cell in this specification refers to an endpoint for communicating with a terminal through a network, covering various coverage areas such as Node-B, evolved Node-B (eNB), gNode-B (gNB), low power node (LPN), sector, site, various types of antennas, base transceiver system (BTS), access point, point (e.g., transmission point, reception point or transmission / reception point), relay node, megacell, macrocell, microcell, picocell, femtocell, remote radio head (RRH), radio unit (RU), small cell, etc. In addition, the cell can be used as a meaning including a bandwidth part (BWP) in the frequency domain. For example, a serving cell can refer to an activated BWP of a terminal.

[0042] The various cells listed above are all equipped with a base station that controls at least one cell, and the base station can be understood in two meanings. The base station can be 1) a device itself for providing a megacell, macrocell, microcell, picocell, femtocell or small cell associated with a wireless area, or the base station can be 2) the wireless area itself. In the description of 1) above, the base station can be a device controlled by the same entity and providing a predetermined wireless area, or it can be all devices that interact with each other and coordinately configure the wireless area. For example, depending on the configuration method of the wireless area, the embodiments of the base station can be a point, a sending / receiving point, a sending point, a receiving point, etc. In the description 2) above, the base station can also refer to the wireless area itself for the terminal or an adjacent base station to send and receive data.

[0043] In this specification, a cell may refer to a coverage of a signal transmitted from a transmission / reception point, a component carrier having coverage of a signal transmitted from a transmission / reception point (or transmission point), or a transmission / reception point itself.

[0044] The uplink (UL) refers to the way data is sent from the UE to the base station, and the downlink (DL) refers to the way data is sent from the base station to the UE. The downlink may represent the communication or communication path from multiple transmission / reception points to the UE, and the uplink may represent the communication or communication path from the UE to the multiple transmission / reception points. In the downlink, the transmission unit may be part of the multiple transmission / reception points, and the receiving unit may be part of the UE. In addition, in the uplink, the transmission unit may be part of the UE, and the receiving unit may be part of the multiple transmission / reception points.

[0045] Uplink and downlink send and receive control information through control channels such as Physical Downlink Control Channel (PDCCH) and Physical Uplink Control Channel (PUCCH). Hereinafter, the situation of sending and receiving signals through channels such as PUCCH, PUSCH, PDCCH, PDSCH, etc. may be expressed as "sending and receiving PUCCH, PUSCH, PDCCH, PDSCH, etc.".

[0046] For clarity, the following description will focus on 3GPP LTE / LTE-A / NR (New Radio) communication systems, but the technical features of the present disclosure are not limited to these communication systems.

[0047] After studying 4G (Fourth Generation) communication technologies, 3GPP has been developing 5G (Fifth Generation) communication technologies to meet the requirements of ITU-R's next-generation radio access technologies. Specifically, 3GPP is developing LTE-A pro, which is an improvement of LTE-Advanced technology according to the requirements of ITU-R, and new NR communication technologies that are completely different from 4G communication technologies, as 5G communication technologies. Both LTE-A pro and NR refer to 5G communication technologies. Hereinafter, unless a specific communication technology is specified, 5G communication technologies will be described based on NR.

[0048] NR defines a variety of operation scenarios in existing 4G LTE scenarios, further considering satellites, automobiles, new vertical fields, etc., to support the enhanced mobile broadband (eMBB) scenario in terms of traffic, the massive machine type communication (mMTC) scenario (where a high density of terminals is distributed over a wide area and requires low data rates and asynchronous connections), and the ultra-reliable low latency (URLLC) scenario (which requires high responsiveness and reliability and supports high-speed mobility).

[0049] To meet such scenarios, NR discloses a wireless communication system that employs new waveform and frame structure technologies, low latency technologies, ultra-high frequency band (mmWave) support technologies, and forward compatibility provision technologies. In particular, the NR system has made various technical changes in terms of flexibility to provide forward compatibility. The main technical features of NR will be described below with reference to the accompanying drawings.

[0050] <Overview of NR System>

[0051] Figure 1 is a schematic structural diagram of an NR wireless communication system to which this embodiment can be applied.

[0052] Reference Figure 1, the NR system is divided into a 5G core network (5GC) and an NG-RAN part. The NG-RAN includes gNBs and ng-eNBs that provide the user plane (SDAP / PDCP / RLC / MAC / PHY) and the control plane (RRC) protocol terminations for user equipment (UE). gNBs are connected to each other or to ng-eNBs via the Xn interface. gNBs and ng-eNBs are connected to the 5GC via the NG interface respectively. The 5GC can be configured to include an access and mobility management function (AMF) for managing the control plane (such as terminal access and mobility control functions, etc.) and a user plane function (UPF) responsible for controlling user data. NR supports frequency bands below 6 GHz (FR1, frequency range 1) and frequency bands above 6 GHz (FR2, frequency range 2).

[0053] gNB refers to a base station that provides the NR user plane and control plane protocol terminations for terminals, and ng-eNB refers to a base station that provides the E-UTRA user plane and control plane protocol terminations for terminals. The base stations described in this specification should be understood to cover gNBs and ng-eNBs, and as needed, the base station can also be used to distinguish and refer to gNBs or ng-eNBs.

[0054] <NR Waveform, Parameter Set, and Frame Structure>

[0055] NR uses the CP-OFDM waveform with a cyclic prefix for downlink transmission and uses CP-OFDM or DFT-s-OFDM for uplink transmission. The OFDM technology has the following advantages: it is very easy to combine with the multiple-input multiple-output (MIMO) scheme and allows the use of low-complexity receiving units with high frequency efficiency.

[0056] In addition, since the above three scenarios have different requirements for data rate, latency rate, coverage range, etc. in NR, it is necessary to efficiently meet the requirements of each scenario through the frequency bands that make up the NR system. For this purpose, a technique for effectively multiplexing radio resources based on multiple different parameter sets has been proposed.

[0057] Specifically, the NR transmission parameter set is determined according to the subcarrier spacing and the cyclic prefix (CP), and as shown in Table 1 below, "μ" is used as the exponential value of 2, so that it changes exponentially based on 15 kHz.

[0058] [Table 1] μ Subcarrier spacing Cyclic prefix Support for data Support for synchronization 0 15 conventional yes yes 1 30 conventional yes yes 2 60 General, Extended yes no 3 120 conventional yes yes 4 240 conventional no yes

[0059] As shown in Table 1 above, NR can have five parameter sets according to the subcarrier spacing. This is different from LTE, one of the 4G communication technologies, in which the subcarrier spacing is fixed to 15kHz. Specifically, in NR, the subcarrier spacing for data transmission is 15, 30, 60 or 120kHz, and the subcarrier spacing for synchronization signal transmission is 15, 30, 120 or 240kHz. In addition, the extended CP is only applied to the subcarrier spacing of 60kHz. A frame with a length of 10ms is defined in the frame structure in NR, which includes 10 subframes, each subframe having the same length of 1ms. A frame can be divided into half frames of 5ms, each half frame including 5 subframes. When the subcarrier spacing is 15kHz, a subframe includes 1 time slot, and each time slot includes 14 OFDM symbols.

[0060] Figure 2 This is a diagram used to illustrate the frame structure in the NR system to which this embodiment can be applied.

[0061] refer to Figure 2 , a time slot includes 14 OFDM symbols in a fixed manner in the case of a conventional CP, but the length of the time slot in the time domain may vary according to the subcarrier spacing. For example, in the case of a parameter set with a subcarrier spacing of 15kHz, the time slot is configured to have a length of 1ms, which is the same as the length of a subframe. In contrast, in the case of a parameter set with a subcarrier spacing of 30kHz, a time slot includes 14 OFDM symbols, but a subframe may include two time slots, each of which has a length of 0.5ms. That is, a subframe as well as a frame may be defined using a fixed time length, and a time slot may be defined as the number of symbols so that its time length varies according to the subcarrier spacing.

[0062] In addition, NR defines the basic unit of scheduling as a time slot, and also introduces micro-time slots (or sub-time slots or non-time slot-based scheduling) to reduce the transmission delay of the wireless part. If a wide subcarrier spacing is used, the length of a time slot is shortened inversely proportional to it, thereby reducing the transmission delay in the wireless part. Micro-time slots (or sub-time slots) are designed to effectively support URLLC scenarios, and micro-time slots can be scheduled in units of 2, 4, or 7 symbols.

[0063] In addition, unlike LTE, NR defines uplink and downlink resource allocation at the symbol level in one slot. In order to reduce HARQ latency, a slot structure that can directly send HARQ ACK / NACK in the transmission slot has been defined, and this slot structure is called a "self-contained structure" for description.

[0064] NR is designed to support a total of 256 slot formats, of which 62 slot formats are used in 3GPP Rel-15. In addition, NR supports a common frame structure that constitutes an FDD or TDD frame through a combination of multiple slots. For example, NR supports a slot structure in which all symbols of the slot are configured for downlink, a slot structure in which all symbols are configured for uplink, and a slot structure in which downlink symbols and uplink symbols are mixed. In addition, NR supports data transmission scheduled and distributed to at least one slot. Therefore, the base station can use the Slot Format Indicator (SFI) to notify the terminal whether the slot is a downlink slot, an uplink slot, or a flexible slot. The base station can notify the slot format by indicating the index of a table configured through terminal-specific RRC signaling using the SFI, and can also dynamically indicate the slot format through Downlink Control Information (DCI), or statically or semi-statically indicate the slot format through RRC signaling.

[0065] <Physical Resources of NR>

[0066] Regarding the physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, bandwidth parts, etc. are considered.

[0067] An antenna port is defined such that the channel carrying the symbol on the antenna port can be inferred from another channel carrying another symbol on the same antenna port. If the large-scale properties of the channel carrying the symbol on one antenna port can be inferred from another channel carrying the symbol on another antenna port, the two antenna ports can have a QC / QCL (Quasi Co-Located) relationship. The large-scale properties include at least one of delay spread, Doppler spread, frequency shift, average received power, and reception timing.

[0068] Figure 3 is a diagram for describing the resource grid supported by the radio access technology to which this embodiment can be applied.

[0069] Reference Figure 3 , since NR supports multiple parameter sets in the same carrier, there can be one resource grid per parameter set. In addition, the resource grid can exist according to antenna ports, subcarrier spacing, or transmission direction.

[0070] A resource block includes 12 subcarriers and is defined only in the frequency domain. In addition, a resource element includes 1 OFDM symbol and 1 subcarrier. Therefore, as Figure 3 shown, the size of one resource block can vary according to the subcarrier spacing. In addition, "Point A" that serves as a common reference point for the resource block grid, as well as common resource blocks and virtual resource blocks, are defined in NR.

[0071] Figure 4 This is a diagram for describing the bandwidth part supported by the radio access technology to which this embodiment can be applied.

[0072] In NR, different from LTE where the carrier bandwidth is fixed at 20 MHz, the maximum carrier bandwidth is set to 50 MHz to 400 MHz according to the subcarrier spacing. Therefore, it is not assumed that all terminals use all these carrier bandwidths. Thus, in NR, as Figure 4 shown, a bandwidth part (BWP) can be specified within the carrier bandwidth and used by the terminal. In addition, the bandwidth part is associated with a parameter set and consists of a subset of consecutive common resource blocks, and the bandwidth part can be dynamically activated over time. For a terminal, up to four bandwidth parts can be configured for each of the uplink and downlink, such that the bandwidth part activated at a given time is used to send / receive data.

[0073] In the case of paired spectrum, the uplink and downlink bandwidth parts are set independently, and in the case of unpaired spectrum, the uplink and downlink bandwidth parts are configured in pairs to share the center frequency, aiming to prevent unnecessary frequency retuning between downlink and uplink operations.

[0074] <NR Initial Access>

[0075] In NR, the UE performs a cell search process and a random access process to access the base station and communicate.

[0076] During the cell search process, the UE uses the synchronization signal block (SSB) sent by the base station to synchronize with the cell of the base station, obtain the physical layer cell ID, and obtain system information.

[0077] Figure 5 This is a schematic diagram of the synchronization signal block in the radio access technology to which this embodiment can be applied.

[0078] Refer to Figure 5 , the SSB is composed of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) that respectively occupy one symbol and 127 subcarriers, and a PBCH that spans three OFDM symbols and 240 subcarriers.

[0079] The UE monitors the SSB in the time domain and frequency domain and receives the SSB.

[0080] SSB can be transmitted up to 64 times within 5ms. Multiple SSBs are transmitted on different transmission beams within 5ms, and the UE performs detection based on the assumption that SSB is transmitted every 20ms period based on one specific beam used for transmission. The number of beams available for SSB transmission within 5ms can increase as the frequency band increases. For example, up to 4 SSB beam transmissions can be performed on frequency bands below 3GHz, up to 8 different beams can be used to transmit SSB on frequency bands from 3 to 6GHz, and up to 64 different beams can be used to transmit SSB on frequency bands of 6GHz or higher.

[0081] One slot includes two SSBs, and the start symbol and the number of repetitions within the slot are determined as follows according to the subcarrier spacing.

[0082] In addition, unlike the existing SS of LTE, SSB is not sent at the center frequency of the carrier bandwidth. In other words, SSB can be sent even at the center of the non-system frequency band, and multiple SSBs can be transmitted in the frequency domain when broadband operation is supported. Accordingly, the UE monitors the SSB through the synchronization grid which is a candidate frequency position for monitoring the SSB. NR newly defines a carrier grid and a synchronization grid as the center frequency position information about the channel used for initial access, and the synchronization grid has a wider frequency interval than the carrier grid, so it can support the UE to perform fast SSB search.

[0083] The UE can obtain the master information block (MIB) through the PBCH of the SSB. The master information block (MIB) includes the minimum information for the UE to receive the remaining system information (e.g., the remaining minimum system information (RMSI)) broadcast by the network. In addition, the PBCH may include information about the position of the first DM-RS symbol in the time domain, information for the UE to monitor SIB1 (e.g., SIB1 parameter set information, information related to SIB1 CORESET, search space information, PDCCH-related parameter set information, etc.), offset information between common resource blocks and SSBs (the absolute position of SSBs within the carrier is transmitted through SIB1), etc. Among them, the SIB1 parameter set information is also applicable to a part of the messages used in the random access process for the UE to access the base station after completing the cell search process. For example, the parameter set information of SIB1 can be applied to at least one of messages 1 to 4 of the random access process.

[0084] The above-mentioned RMSI may be system information block 1 (SIB1), and SIB1 is broadcast periodically (e.g., 160ms) in the cell. SIB1 includes information required for the UE to perform the initial random access procedure, and SIB1 is periodically transmitted through the PDSCH. In order to receive SIB1, the UE needs to receive parameter set information for SIB1 transmission and control resource set (CORESET) information for SIB1 scheduling through the PBCH. The UE uses SI-RNTI in the CORESET to identify the scheduling information for SIB1, and obtains SIB1 on the PDSCH according to the scheduling information. The remaining SIBs except SIB1 may be transmitted periodically or at the request of the UE.

[0085] Figure 6 This is a diagram for describing a random access procedure in a wireless access technology to which this embodiment can be applied.

[0086] refer to Figure 6 , when the cell search is completed, the UE sends a random access preamble for random access to the base station. The random access preamble is transmitted through the PRACH. Specifically, the random access preamble is sent to the base station in a specific time slot that is repeated periodically through the PRACH composed of continuous radio resources. In general, when the 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.

[0087] The UE receives a random access response in response to the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), uplink radio resources (UL grant), a temporary cell radio network temporary identifier (C-RNTI), and a time alignment command (TAC). Since a random access response may include random access response information for at least one UE, a random access preamble identifier may be included to indicate which UE the UL grant, temporary C-RNTI, and TAC included in the random access response are valid for. The random access preamble identifier may be an identifier for a random access preamble received by a base station. 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 (i.e., a random access radio network temporary identifier (RA-RNTI)) on a PDCCH.

[0088] After receiving a valid random access response, the UE processes the information included in the random access response and performs a scheduled transmission to the base station. For example, the UE applies the TAC and stores the temporary C-RNTI. In addition, the UE uses the UL grant to send data stored in the UE's cache or newly generated data to the base station. In this case, it is necessary to include information that can identify the UE.

[0089] Finally, the UE receives a downlink message for contention resolution.

[0090] <NR CORESET>

[0091] In NR, the downlink control channel is transmitted in a control resource set (CORESET) with a length of 1 to 3 symbols, which transmits uplink and downlink scheduling information, slot format index (SFI), transmit power control (TPC) information, etc.

[0092] In this way, NR introduces the concept of CORESET to ensure the flexibility of the system. Control resource set (CORESET) refers to the time-frequency resources used for downlink control signals. The UE can use at least one search space in the CORESET time-frequency resources to decode candidate control channels. A CORESET-specific quasi-co-location (QCL) assumption is configured to notify the simulated beam direction related characteristics in addition to the delay spread, Doppler spread, Doppler shift and average delay that are characteristics assumed by the existing QCL.

[0093] Figure 7 This is a diagram for explaining CORESET.

[0094] refer to Figure 7 ,CORESET can exist in multiple forms in the carrier bandwidth within a time slot, and in the time domain, a CORESET can be composed of up to 3 OFDM symbols. In addition, a CORESET is defined in the frequency domain as a multiple of 6 resource blocks, but not exceeding the carrier bandwidth.

[0095] The first CORESET is indicated as part of the initial bandwidth portion through the MIB, so that additional configuration information and system information can be received from the network. After establishing a connection with the base station, the UE can receive and configure at least one CORESET information through RRC signaling.

[0096] In this specification, frequency, frame, subframe, resource, resource block, area, frequency band, subband, control channel, data channel, synchronization signal, various reference signals, various signals or various messages related to NR (New Radio) may be interpreted as the meaning used now or in the past, or may be interpreted as various meanings to be used in the future.

[0097] The present invention relates to a method and apparatus for processing packet data for specific application services such as XR / media in a mobile communication network. For example, the present disclosure relates to a technique for dividing and processing a group of data packets or a set of protocol data units (PDUs).

[0098] Packets for a particular application service may have interdependent properties. For example, packets within a frame may be dependent on each other. The application may require all packets to decode the corresponding frame. The loss of one packet may render the corresponding packet useless despite the successful transmission of other related packets. For example, requirements may be placed on XR applications for application data units (ADUs) / media units instead of individual packets / PDUs. Even packets in different frame types (I / P frames) or different positions in groups of pictures (GoPs) may contribute differently to the user experience despite being in the same video stream. Therefore, layered QoS processing in the video stream may relax requirements and improve efficiency.

[0099] If the running service / application can utilize additional information from higher layers / application layer, it may help to select radio parameters more easily. However, currently no specific method is provided for the UE, base station or core network to effectively identify and process the characteristics of XR application traffic.

[0100] Therefore, existing mobile communication technologies do not provide a specific method to enable UE, base station or core network to effectively identify and process XR application traffic.

[0101] To address these issues, the present disclosure introduces a configuration method and apparatus for providing packet data processing that takes into account application traffic characteristics using information provided from the higher layers / application layers in a wireless network.

[0102] The present invention discloses a method based on 5GS / NR technology. However, this is for the convenience of description, and the present embodiment can be applied to any system / radio access technology (e.g., LTE, 6G). The embodiments described in the present disclosure include the information elements and operations specified in the NR / 5GS standards (e.g., TS38.321 as a MAC standard, TS38.331 as an NRRRC standard, TS23.501 as a 5G system structure standard, TS23.502 as a 5G system procedure standard, etc.). Although the present invention does not include the details of the UE operation related to the definition of the corresponding information elements, the corresponding contents specified in the standard and belonging to the scope of known technology can be incorporated into the present embodiment.

[0103] Further, in the present disclosure, XR or CG applications are used as examples of the application for description. However, this is only for the convenience of description and easy understanding, and is not limited thereto. The present embodiment can also be applied to data processing at a specific application level.

[0104] Any function described below is defined as an individual UE capability (UE wireless capability or UE core network capability), which can be transmitted by the UE to the base station / core network entity (such as AMF / SMF) through corresponding signaling. Alternatively, any functions can be combined / merged, defined as corresponding UE capabilities, and transmitted by the UE to the base station / core network entity through corresponding signaling.

[0105] The base station may send / indicate information to the UE through an RRC message that allows / supports / configures the corresponding function / function combination for any function or any function combination described below. For example, the UE may be instructed before or at the same time as configuring / applying the corresponding function / function combination. The RRC message may be broadcast through system information. Alternatively, the UE may be instructed through a dedicated RRC message.

[0106] For the convenience of description, units divided by application / application layer, or within an application, units with correlation between data / streams / packets in one application, units with dependency between data / streams / packets in one application, units divided by different traffic characteristics / streams within a flow, units divided by different traffic characteristics / streams within a PDU session, units divided based on any information / fields / metadata included / used / added in the application, or PDUs carrying a unit information payload generated at the application level are represented as PDU sets. This is just for the convenience of description, and the term "PDU set" can be replaced with any other terms, such as application data unit (ADU), application unit, media unit (MU), application packet data unit, group of pictures (GoP) unit, traffic type (e.g., XR viewer posture information unit, tactile information, video, audio, degree of freedom) specific unit, frame type, stream type, etc.

[0107] A PDU set consists of one or more PDUs that carry an information unit generated by the application layer as a payload, and these PDUs have the same importance requirement at the application layer. The application layer requires all PDUs in a PDU set to use the corresponding unit information. (A PDU set consists of one or more PDUs that carry the payload of an information unit generated at the application level (for example, a frame or video slice of an XRM service), and they have the same importance requirement at the application layer. The application layer requires all PDUs in the PDU set to use the corresponding information unit.) For example, a PDU set can be understood as a concept similar to a video slice. A video slice is a spatially divided area in a frame of video and is encoded by separating it from other areas in the same frame.

[0108] The functions described below can be performed individually and independently. The functions described below can be combined or merged arbitrarily, and it is obvious that they are also included in the scope of this embodiment. For example, one or more functions can be applied at the same time.

[0109] Any information about XR applications described below may be traffic characteristic information obtained / calculated / derived by the UE / network through statistics / experience (e.g., any statistical data / statistical quantity, such as expected value / average value, deviation, standard deviation, etc.). Therefore, any information contained herein may indicate one or more average (expected value) / minimum value / maximum value / standard deviation values. For example, if the information 'update rate' is included, it may mean the average (expected value) / minimum value / maximum value / standard deviation update rate. This is for the convenience of description, and all the information in the present disclosure may be used as statistical information. Alternatively, it may be information pre-configured in the UE / network, or information provided by OAM / application server / application function / UDM.

[0110] Figure 8 is an example diagram showing a structure for implementing a 5G-XR function in a 5G system.

[0111] For the convenience of description, the embodiments of the present disclosure are based on Figure 8 Description is made, however, the embodiments are not limited thereto and these embodiments can be applied to any system / radio access technology (such as LTE or 6G).

[0112] See also Figure 8 , 5G-XR AF represents the application function for 5G-XR services. 5G-XR AS represents the application server for 5G-XR services, and 5G-XR client represents the UE internal function for 5G-XR services. In the UE, the XR client can indicate the transceiver of the XR session accessed by the XR application through an API, etc. The XR client can communicate or transmit signaling with the 5G-XRAF to configure / control / support the XR session (or the transmission of the XR session). The XR client can access XR data and communicate with the 5G-XR AS to process the corresponding data. The 5G-XR AF provides various control functions for processing the XR session on the UE. The 5G-XRAF can transmit signaling with the PCF / NEF to achieve QoS control. The 5G-XR AS represents an application server that carries 5G XR media and media functions.

[0113] Fig. 9 is a flowchart illustrating the operation of a UE according to an embodiment.

[0114] Reference Fig. 9In the method for processing an application data flow, the UE may perform a step of receiving a high-layer message including radio resource configuration information, wherein the radio resource configuration information is configured for sending / receiving specific application data (S910).

[0115] According to one embodiment, the wireless resource configuration information may include protocol data unit (PDU) set information, the information including at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information. In addition, the wireless resource configuration information may include at least one of auxiliary information of application traffic characteristics and PDU set information.

[0116] According to one embodiment, the application data stream (or application data) may be a PDU set of specific application data with high correlation between data streams such as XR or CG. The UE may receive radio resource configuration information related to auxiliary information from the base station, and the auxiliary information may help solve the characteristics of the corresponding application traffic. According to another embodiment, the UE may receive radio resource configuration information associated with the PDU set information from the base station. According to yet another embodiment, the UE may receive radio resource configuration information associated with the auxiliary information and the PDU set information from the base station.

[0117] According to one embodiment, the auxiliary information may include at least one of uplink or downlink periodicity information about the application data stream and jitter information associated with the periodicity information. As previously mentioned, the application data stream may cause uplink or downlink with a non-integer period according to the traffic characteristics of the corresponding application. In addition, the application data stream may cause a certain degree of jitter in uplink or downlink transmission / reception. Therefore, the periodicity information can be set to a non-integer value. Alternatively, the periodicity information can be set to an integer value. By using the auxiliary information, the UE can perform effective application traffic processing by applying transmission / reception parameters that take into account the characteristics of the corresponding application data stream.

[0118] According to another embodiment, the PDU set information may include at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information. For example, the PDU set information may include a PDU set sequence number used in the corresponding application. Alternatively, the PDU set information may include indication information indicating the last PDU of the PDU set terminated by the corresponding application. Alternatively, the PDU set information may include importance information applied to the PDU set. A PDU set may be set to have the same importance.

[0119] Meanwhile, the high-layer message may be an RRC message. For example, the high-layer message may include an N1 session management (SM) container including a PDU set QoS parameter. That is, the UE may identify the N1 SM container included in the high-layer message and use the PDU set QoS parameter included in the N1 SM container to apply to the corresponding application data flow processing. Alternatively, the high-layer message may also be a message broadcast by the base station.

[0120] The UE may perform a step of configuring radio resource configuration information (S920).

[0121] According to one embodiment, the UE may store the received radio resource configuration information in the UE, or the UE may store the received radio resource configuration information as a parameter value of the UE and use it later when needed.

[0122] According to an embodiment, the UE may configure a radio link control (RLC) entity based on at least one information included in the PDU set information.

[0123] According to another embodiment, the radio resource configuration information may include one or more of the following: DRX configuration information supporting non-integer values ​​based on auxiliary information, or data radio bearer configuration information associated with one or more logical channel configurations based on PDU set information.

[0124] According to another embodiment, the UE may configure the DRX parameter by storing or applying the DRX configuration information supporting the non-integer value included in the radio resource configuration information to the UE. Thus, a UE DRX operation suitable for the application data stream sent and received with a period set to the non-integer value may be performed.

[0125] According to another embodiment, the UE may configure the DRB of the UE using the DRB configuration information associated with the logical channel configuration included in the radio resource configuration information. Based on configuring the corresponding logical channel configuration based on the PDU set information, a logical channel and DRB suitable for the application data flow may be configured in the UE.

[0126] The UE may perform a step of distinguishing user plane data of application data based on the radio resource configuration information ( S930 ).

[0127] According to an embodiment, the UE may apply the radio resource configuration information and send and receive user plane data generated at the corresponding application layer. At this time, the UE may distinguish and process the user plane data of the corresponding application data from other normal data according to the radio resource configuration information.

[0128] For example, the UE may process the user plane data generated by the corresponding application layer using the data radio bearer configured by the radio resource configuration information. As another example, the UE may control the DRX operation of the UE according to the uplink or downlink key period generated as a non-integer value by applying the DRX parameter configured using the radio resource configuration information to the UE.

[0129] At the same time, the above-mentioned protocol data unit (PDU) of user plane data for a specific application can be configured to include one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information. For example, one of the PDU set sequence number, the PDU set end PDU indication information, and the PDU set importance information can be included in the service data adaptation protocol (SDAP) header or the packet data convergence protocol (PDCP) header of the PDU. In other words, the SDAP header may include one or more information constituting the corresponding PDU set information. And / or, the PDCP header may include one or more information constituting the corresponding PDU set information. Therefore, the corresponding PDU set information can be processed differently.

[0130] For example, the UE may discard all protocol data units (PDUs) or service data units (SDUs) associated with at least one information included in the PDU set information in the packet data convergence protocol (PDCP) entity or the radio link control (RLC) entity. In other words, all related PDU sets may be discarded.

[0131] The timer configured to discard the protocol data unit (PDU) or the service data unit (SDU) can be distinguished according to each PDU set information. The corresponding timer can be included in the radio resource configuration information and configured in the UE. In addition, the corresponding timer can be configured and operated separately for each PDU set. At the same time, if the timer expires, the UE can instruct the lower layer to discard the protocol data unit (PDU) or the service data unit (SDU). For example, if the timer expires, the PDCP entity can instruct the RLC entity to discard the PDU or SDU associated with the corresponding timer.

[0132] Through the above operation, the UE can enhance the dynamic processing performance for various transmission / reception data generated in a specific application. In addition, the UE can handle services requiring high accuracy and responsiveness, such as XR or CG, without any problem.

[0133] More specific processes and related information will be described in detail later for each embodiment.

[0134] Fig.10 is a flowchart for describing the operation of a base station according to an embodiment.

[0135] See also Fig.10 In the method for processing an application data stream, the base station according to this embodiment may execute the step of sending a high-layer message including wireless resource configuration information to the UE, where the wireless resource configuration information is configured for sending / receiving specific application data (S1010).

[0136] According to one embodiment, the wireless resource configuration information may include protocol data unit (PDU) set information, the information including at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information. In addition, the wireless resource configuration information may include at least one of auxiliary information of application traffic characteristics and PDU set information. For example, an application data stream (or application data) may be a PDU set of specific application data with a high correlation between data streams such as XR or CG. The UE may receive wireless resource configuration information related to the auxiliary information from the base station, and the auxiliary information may help solve the characteristics of the corresponding application traffic. Alternatively, the UE may receive wireless resource configuration information associated with the PDU set information from the base station. In another case, the UE may receive the wireless resource configuration information and the PDU set information associated with the auxiliary information from the base station.

[0137] According to one embodiment, the auxiliary information may include at least one of uplink or downlink periodicity information about the application data stream and jitter information associated with the periodicity information. As mentioned above, the application data stream may cause uplink or downlink transmission with a non-integer period according to the traffic characteristics of the corresponding application. In addition, the application data stream may cause a certain degree of jitter in uplink or downlink transmission / reception. Therefore, the periodicity information can be set to a non-integer value. Alternatively, the periodicity information can also be set to an integer value. By using the auxiliary information, the UE can perform effective application traffic processing by applying sending / receiving parameters that take into account the characteristics of the corresponding application data stream.

[0138] According to another embodiment, the PDU set information may include at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information. For example, the PDU set information may include a PDU set sequence number used in the corresponding application. Alternatively, the PDU set information may include indication information indicating the last PDU of the PDU set terminated by the corresponding application. Alternatively, the PDU set information may include importance information applied to the PDU set. A PDU set may be set to have the same importance.

[0139] The high-layer message may be an RRC message. For example, the high-layer message may include an N1 session management (SM) container including a PDU set QoS parameter. Alternatively, the high-layer message may also be a message broadcast by the base station.

[0140] The base station may perform a step of distinguishing user plane data of application data based on the radio resource configuration information (S1020).

[0141] In order to distinguish the user plane data for processing the specific application data, it is necessary to identify the protocol data unit (PDU) of the corresponding user plane data.

[0142] To this end, the PDU of user plane data for a specific application can be configured to include one or more information of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information. For example, one or more information of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance can be included in a service data adaptation protocol (SDAP) header or a packet data convergence protocol (PDCP) header of the PDU. In other words, the SDAP header may include one or more information constituting the corresponding PDU set information. And / or, the PDCP header may include one or more information constituting the corresponding PDU set information. Therefore, the corresponding PDU set information can be processed differently.

[0143] The protocol data unit (PDU) or the service data unit (SDU) can be discarded according to the timer configured to distinguish each PDU set information. The corresponding timer may be included in the radio resource configuration information. Further, the corresponding timer may be configured and operated in association with each PDU set. At the same time, if the timer expires, the lower layer may be instructed to discard the protocol data unit (PDU) or the service data unit (SDU). For example, if the timer expires, the PDCP entity may instruct the RLC entity to discard the PDU or SDU associated with the corresponding timer.

[0144] Through the above operation, the base station can enhance the dynamic processing performance for various transmission / reception data generated in specific applications. In addition, the base station can handle services requiring high accuracy and responsiveness, such as XR or CG, without any problems.

[0145] More specific processes and related information will be described in detail below for each embodiment. The individual embodiments described below may be performed in combination in whole or in part. In the following description, XR / media application services are used as examples of specific application services. This is for ease of description, and the embodiments are not limited to this.

[0146] Define the relationship between PDU session and PDU set

[0147] A PDU session indicates the association between the UE and a data network that provides a PDU connection service. For one UE (or each UE), one XR / media service may use a single PDU session.

[0148] For example, the UE may share an XR / media application service that supports / provides a PDU set (or PDU set capability) and another application service that does not support / provide a PDU set through a PDU session. It is best to transmit tactile and / or multimodal data related to an application (e.g., audio, video, tactile data related to a specific time) to the user / UE at similar times by adjusting the processing. The mobile communication system (e.g., UE, base station or 5GS (e.g., SMF or UPF)) can group and distinguish the XR / media application service data streams that support / provide the PDU set (or PDU set capability) of the corresponding PDU session. For example, it can be distinguished by information identifying the corresponding XR / media application service data stream (QoS-stream / PDU-set) group. Alternatively, for XR / media application service data streams that support / provide PDU sets (or PDU set capabilities), they can be distinguished by information identifying the corresponding PDU set (e.g., PDU-set-ID).

[0149] For another example, the UE can configure a PDU session supporting an XR / media application service through a PDU session, the XR / media application service supports and provides a PDU set (or PDU set capability), and provide a PDU session supporting another application service, the application service does not support a PDU set. The service can be provided through a dedicated PDU session for an XR / media application service. In this case, since the QoS flow / service data flow of another application service is not shared, even if the information of the QoS flow / PDU set grouping for the corresponding XR / media application service is not included separately, processing considering PDU set level parameters can be provided / supported for all QoS flows / service data flows included in the corresponding PDU session. In the corresponding process / signaling (for example, the PDU session establishment / modification process between the UE and the core network node (for example, AMF / SMF)), the corresponding PDU session can be distinguished by indication information, which is used to distinguish / identify / indicate the PDU session that supports / provides the PDU-set.

[0150] PDU set differentiation processing in NAS

[0151] For the downlink, the UPF (for the uplink, the UE) may use one or more pieces of information contained in any header of the data packet / payload / PDU (e.g., payload / RTP / SRTP / RTCP / TCP / UDP / IP header) that encapsulates the corresponding data packet / payload / application PDU to identify the PDU-set. For example, the RTP header may include information such as a sequence number, a timestamp, a mark (M) bit, and the corresponding information may be used to identify data packets belonging to a PDU-set. As another example, the RTP extension header may include information about the payload data type (e.g., the RTP payload network application layer unit type field), and the corresponding information may be used to determine the importance of the corresponding data packet. Alternatively, the UPF may use metadata generated by the AS to identify the PDU-set. Packet filtering information for identifying PDU-sets (e.g., PDU-set description information via one or more pieces of information contained in any header) may be transmitted by the application function AF (or via the network exposure function (NEF) if one exists) to the corresponding entity / node (e.g., PCF / SMF / PFDF / UDM).

[0152] For the downlink case, the UPF (for the uplink case, the UE) can add PDU-set-related information to the corresponding PDU and send it to the base station (RAN). The base station can use the received corresponding information to allocate radio resources. The base station can identify the corresponding PDU-set and use the received corresponding information to transmit data to the UPF. The PDU-set-related information sent by the UPF / UE to the base station may include one or more of the following information.

[0153] -PDU set identifier: information used to identify a PDU set

[0154] -PDU-Set Sequence Number / Tag

[0155] -PDU set size: information used to identify / indicate the last SDU / PDU of a PDU set

[0156] - Information indicating that it is the last PDU in a PDU set

[0157] -PDU-set importance / priority indication information: information used to indicate the importance / priority value of the corresponding PDU-set

[0158] The above one or more information (PDU-set-related information) may be included only in the first PDU of the corresponding PDU-set. And / or, the above one or more information may be included in the last PDU of the corresponding PDU-set. Alternatively, the above one or more information may be included in all PDUs of the corresponding PDU-set. For example, a PDU-set can be identified by setting / adding the same PDU sequence number for all the data packets belonging to the corresponding PDU-set. For another example, a PDU-set can be identified by setting / adding information, which is used to indicate that the last data packet belonging to the corresponding PDU-set is the last PDU in the corresponding PDU-set.

[0159] The above-mentioned one or more pieces of information (PDU-set-related information) can be identified by any field tag on the GTP-U extension header in the base station / UPF.

[0160] One or more PDU-set-related information (e.g., PDU-set sequence number) may have an n-bit value (where n is a natural number greater than 2, such as 2, 3, 4, ...). The corresponding value may start from 0 (or 1), increment by 1, and reach the maximum value after modulo / remainder operation, and then be set to cycle. For example, when the corresponding n has 2 bits, there may be 4 values ​​of 0, 1, 2, 3, which can be cycled to 0, 1, 2, 3, 0, 1, 2, 3, 0, 1, 2, 3, ... through modulo 4 operation.

[0161] The UE with PDU-set processing capability may request to use the corresponding function during a NAS process (e.g., an attachment process, a service request process, a PDU session establishment / modification) and may receive authorization / permission for the function. Alternatively, the corresponding UE may receive PDU-set processing rules / policies for a PDU session supporting PDU-set processing during a PDU session establishment / modification process. For example, the UE may include rules / policies for DU-set processing in an N1 session management (SM) container and receive the rules / policies. The rules / policies may include QoS rules for PDU sets and QoS flow / PDU set level QoS parameters of the QoS flow / PDU set associated with the corresponding QoS rules.

[0162] The UE may process uplink data using the QoS rules and the PDU-set level QoS parameters for the received PDU-set. The PDU-set level QoS parameters may include PDU-set level QoS characteristics (one or more of PDU-set level resource types (non-GBR, GBR, delay critical GBR)), PDU-set level priority / importance, PDU-set level packet delay budget, PDU-set level packet error rate, PDU-set level average window, PDU-set level maximum data burst, PDU-set discard time). Alternatively, the PDU-set level QoS parameters may be a scalar value (e.g., 5QI or QCI) for reference to PDU-set level QoS characteristics. The base station may receive the QoS rules and the PDU-set level QoS parameters for the corresponding PDU-set from a core network node (e.g., AMF / SMF) on a related NAS processor.

[0163] DRB mapping of QoS flows and PDU sets in the SDAP sublayer

[0164] In the related art, the Service Data Adaptation Protocol (SDAP) layer / sublayer provides the function of mapping QoS flows to DRBs. For example, both the uplink and the downlink support the mapping between a QoS flow and a DRB. Both the uplink and the downlink mark the QoS flow ID in the SDAP header. (QFI).

[0165] To support PDU-set level QoS processing for (XR / media) applications, SDAP may need to be enhanced (or PDCP higher adaptation protocol) function.

[0166] For example, a PDU-set may be mapped to a DRB and processed. Information for identifying the PDU-set (e.g., PDU-set-ID) may be marked / included in the SDAP header in the uplink and downlink. The base station may transmit the corresponding PDU-session identification information and the PDU-set information to be added / released on the SDAP configuration information (sdap-config) through the RRC message.

[0167] Fig.11 is a diagram exemplarily illustrating a PDU session resource establishment request transmission information element according to an embodiment. Fig.12 is a diagram exemplarily illustrating a PDU session resource modification request transmission information element according to an embodiment.

[0168] Reference Fig.11 and Fig.12 , the PDU-set establishment / addition / modification information contained in the PDU session resource establishment / addition / modification request message contained in the NGAP interface between the core network node (e.g., AMF / SMF) and the base station can be used independently of the QoS flow establishment / addition / modification information. Alternatively, the PDU-set setting / addition / modification information contained in the PDU session resource setting / addition / modification request message contained in the NGAP interface between the core network node (e.g., AMF / SMF) and the base station can be used as a parameter at the same level as the QoS flow setting / addition / modification information, such as Fig.11 and Fig.12 shown.

[0169] Fig.13 is a diagram exemplarily illustrating SDAP configuration information elements according to an embodiment.

[0170] See also Fig.13 As another example, the SDAP configuration information (sdap-config) included in the RRC message may indicate the information of the QFI list of the uplink QoS flow for indicating the PDU session that needs to be additionally mapped to the DRB, which is independent of the information of the PDU-set-ID list of the uplink PDU-set for indicating the PDU session that needs to be additionally mapped to the DRB. Alternatively, the SDAP configuration information (sdap-config) included in the RRC message may be as follows: Fig.13As shown, the information of the QFIs list of the uplink QoS flow indicating the PDU session that needs to be additionally mapped to the corresponding DRB is indicated as a parameter of the same level as the information of the PDU-set-IDs list of the uplink PDU-set indicating the PDU session that needs to be additionally mapped to the DRB. The corresponding DRB can be mapped / associated through a shared QoS flow and / or PDU set. Alternatively, the corresponding DRB can be specifically mapped / associated to a QoS flow or PDU set. The corresponding uplink / downlink SDAP header can be applied, including a QoS flow ID and / or PDU set ID according to the QoS flow and / or the PDU set.

[0171] Fig.14 is a diagram exemplarily illustrating a PDU session resource establishment request transmission information element according to another embodiment. Fig.15 is a diagram exemplarily illustrating a PDU session resource modification request transmission information element according to another embodiment.

[0172] refer to Fig.14 and Fig.15 As another example, the PDU-set setting / addition / modification information contained in the PDU session resource setting / addition / modification request message contained in the NGAP interface between the core network node (e.g., AMF / SMF) and the base station can serve as a subordinate parameter of the QoS flow setting / addition / modification information.

[0173] Fig.16 is a diagram exemplarily illustrating SDAP-Configuration information elements according to another embodiment.

[0174] See also Fig.16 As another example, in the SDAP configuration information (sdap-config) included in the RRC message, the PDU-set-ID of the uplink PDU-set of the PDU session that needs to be additionally mapped to the corresponding DRB may be indicated as a lower parameter of the information for indicating the QFI of the uplink QoS-Flow of the PDU session that needs to be additionally mapped to the DRB. The corresponding uplink / downlink SDAP header may be applied, including a QoS flow ID and / or a PDU set ID according to the QoS flow and / or the PDU set.

[0175] For another example, if no PDU set to DRB mapping rule is indicated / configured / stored for the corresponding PDU set, the corresponding PDU set may be mapped to the default DRB. Otherwise, the PDU / SDAP-SDU belonging to the PDU set may be mapped to the corresponding DRB according to the PDU set to DRB mapping rule for mapping the indicated / configured / stored PDU set to the DRB.

[0176] For another example, for the PDU-set, the corresponding SDAP SDU may not be mapped to the default DRB. The PDU / SDAP-SDU belonging to the PDU-set may be mapped to the corresponding DRB according to the PDU set to DRB mapping rule, which always maps the indicated / configured / stored PDU-set to the DRB.

[0177] For another example, if the DRB mapping rule of the corresponding PDU-set is not indicated / configured / stored,

[0178] >>If the QoS flow to DRB mapping rule of the corresponding PDU-set is indicated / configured / stored for the QoS flow to which the corresponding PDU-set belongs, the PDU / SDAP-SDU belonging to the corresponding PDU-set can be mapped to the corresponding DRB according to the mapping rule of mapping the indicated / configured / stored QoS flow to the PDU set to the DRB.

[0179] >> Otherwise (or if no QoS flow to DRB mapping rule is indicated / configured / stored for the QoS flow to which the corresponding PDU-set belongs for the corresponding PDU-set)

[0180] >>>The corresponding PDU-set (PDU / SDAP-SDU(s) belonging to the corresponding PDU-set) may be mapped to the default DRB.

[0181] >>>This may be indicated by a higher layer (e.g., RRC / NAS). The higher layer of the UE may indicate this to the base station / core network node (e.g., AMF / SMF) via signaling (RRC / NAS signaling).

[0182] For another example, the default DRB indication information (defaultDRB) indicates information for indicating whether it is the default DRB for the PDU session in all the configured SDAP instances having the same value (e.g., PDU-session ID) as the corresponding PDU-session. If the corresponding DRB is only mapped to a (specific) PDU-set (configured by SDAP-), the corresponding DRB may not be configured as the default DRB. Therefore, the DRB configured / indicated for the (specific) PDU set (one or more) cannot be used as the default DRB. For another example, the default DRB can be used in a DRB mapped to a QoS-flow (mapping to a QoS-flow).

[0183] For another example, the base station may add information for indicating the default DRB of the PDU-set to the RRC message and indicate it to the UE. The corresponding information may be defined and indicated as information distinguished from the default DRB indication information (default DRB) described above.

[0184] SDAP sublayer distinguishes and processes PDU sets

[0185] When one or more PDU-sets are mapped to a DRB and processed, a method for differentiated processing thereof on SDAP may be provided to support differentiated processing of each PDU-set (e.g., each PDU-set-ID, each PDU-set sequence number having the same PDU-set-ID, or each PDU-set importance / priority having the same PDU-set-ID) in any L2 sublayer (e.g., SDAP / PDCP / RLC / MAC).

[0186] For the convenience of description, the method for distinguishing and processing the PDU-set in the SDAP sublayer is described below. However, this is only for the convenience of description, and it is obvious that the application of the same method as the SDAP sublayer in the PDCP / RLC / MAC sublayer is also included in the scope of the present invention.

[0187] Fig.17 is a diagram showing a DL SDAP data PDU format with an SDAP header according to an embodiment. Fig.18 is a diagram showing a UL SDAP data PDU format with an SDAP header according to an embodiment.

[0188] Fig.17 and Fig.18 The SDAP data PDU format in the related art is shown.

[0189] For example, the uplink / downlink SDAP data PDU can be constructed by including the above-mentioned PDU-set-related information in the SDAP header (for example, the PDU-set identifier, the PDU-set sequence number, the PDU-set size, information for identifying the last PDU of the PDU-set, information for indicating that it is the last PDU in the PDU-set, and one or more of the PDU-set importance / priority indication information).

[0190] For example, in order to use the SDAP header including one or more pieces of information in the PDU set related information identified from the prior art, the base station may include information indicating the use / application / existence of the uplink / downlink SDAP header supporting the PDU-set through RRC signaling (in the SDAP configuration information), and indicate it to the UE. The corresponding information may indicate the use of the corresponding SDAP header by information that is distinguished from the information of the SDAP header (sdap-HeaderUL / sdap-HeaderDL) indicating whether there is uplink / downlink data on the DRB in the prior art.

[0191] As another example, the use of the SDAP header supporting the PDU-set may be indicated by information indicating a dedicated PDU session or dedicated SDAP configuration supporting the PDU set. The use of the corresponding SDAP header may be indicated by information on whether there is an SDAP header (sdap-HeaderUL / sdap-HeaderDL) for uplink / downlink data on the DRB in accordance with the prior art. Alternatively, the use of the corresponding SDAP header may also be indicated by information discerned from information on whether there is an SDAP header (sdap-HeaderUL / sdap-HeaderDL) for uplink / downlink data on the corresponding DRB in the prior art.

[0192] As another example, an SDAP entity of a PDU session supporting a PDU-set may be further configured / set. For example, the SDAP entity of the QoS flow included in the corresponding PDU session and the SDAP entity of the PDU-set included in the corresponding PDU session may be configured / set separately. Alternatively, a dedicated SDAP entity of the PDU-set included in the corresponding PDU session may be configured / set.

[0193] For another example, for the UE that supports the PDU-set and / or when the base station receives the PDU-set processing request from the UE / core network node (e.g., AMF / SMF), the base station can use the above-mentioned PDU-set-related information (e.g., the PDU-set identifier, the PDU-set sequence number, the PDU-set size, information for identifying that it is the last PDU of the PDU-set, information for indicating that it is the last PDU in the PDU-set, and one or more of the PDU-set importance / priority indication information) to notify the UE.

[0194] For another example, the PDU-set can be processed differently through the SDAP control PDU.

[0195] For example, in order to indicate / notify the use / termination of use / switching / presence / non-existence of the SDAP header including one or more information in the PDU-set-related information in the prior art, the base station may send SDAP control PDU signaling to the UE. For another example, in order to indicate / notify the use / termination of use / switching / presence / non-existence of any L2 (PDCP / RLC / MAC) header including one or more information in the PDU-set-related information identified from the prior art, the base station may send the corresponding L2-control-PDU / MAC-CE signaling to the UE. The control PDU / MAC-CE may include one or more information in the above-mentioned PDU-set-related information. The control PDU / MAC-CE may include indication information for identifying one or more information in the use / start of use / termination of use / switching / presence / non-existence of the header.

[0196] For another example, the PDU-set may control the PDU mapping to the DRB through an end marker. When the RRC configures a rule for mapping the uplink PDU-set to the DRB, the SDAP entity may perform the following operations.

[0197] >If one or more of the following conditions are met, you can perform one or more of the following operations.

[0198] Relevant conditions: SDAP is configured, there is no rule mapping the PDU-set stored for the corresponding PDU-set to the DRB, the default DRB for the corresponding PDU-set or the default DRB for the QoS flow belonging to the corresponding PDU-set is configured, and the last PDU / SDAP-SDU identified / detected in the corresponding PDU-set.

[0199] According to the prior art (TS.37.324 6.2.3), the above-mentioned control PDU or end marker control PDU is constructed for the corresponding PDU set.

[0200] >>Map the corresponding end marker control PDU or the control PDU described above to the default DRB of the corresponding PDU-set or the default DRB of the QoS-flow belonging to the corresponding PDU-set.

[0201] >>Submit the corresponding end marker control PDU or the control PDU described above to the lower layer.

[0203] >If one or more of the following conditions are met, you can perform one or more of the following operations.

[0204] Related conditions: The rule for mapping the PDU-set to the DRB stored for the corresponding PDU-set is different from the rule for mapping the PDU-set to the DRB configured for the corresponding PDU-set, the rule for mapping the PDU-set to the DRB stored for the corresponding PDU-set is configured by the RRC, and the last PDU / SDAP-SDU is identified / detected in the corresponding PDU-set.

[0205] >>According to the prior art (TS.37.324 6.2.3), the above control PDU or end marker control PDU is constructed for the corresponding PDU set.

[0206] >> According to the rule of mapping the stored PDU set of the corresponding PDU set to the DRB, map the corresponding end marker control PDU or the control PDU described above to the DRB.

[0207] >>Submit the corresponding end marker control PDU or the control PDU described above to the lower layer.

[0208] For another example, the SDAP SDU mapping of the PDU-set indicated by the PDU-set ID included in the end marker control PDU on the DRB to which the corresponding end marker control PDU is transmitted can be indicated by including the PDU-set ID in the QFI / field on the end marker control PDU.

[0209] For another example, the PDU-set ID can be included in the QFI / field on the end marker control PDU to indicate that the SDAP SDU mapping of the QoS flow containing the corresponding PDU-set can be stopped using the PDU-set ID included in the corresponding end marker control PDU on the DRB that transmits the corresponding end marker control PDU.

[0210] Differentiated processing of PDU sets in the PDCP sublayer

[0211] When one or more PDU-sets are mapped to a DRB and processed, a method for differentiated processing them at PDCP can be provided to support different processing of each PDU-set (e.g., each PDU-set-ID, each PDU-set sequence number with the same PDU-set-ID, or each PDU-set importance / priority with the same PDU-set-ID) in any L2 sublayer (e.g., SDAP / PDCP / RLC / MAC).

[0212] For example, the PDCP entity may discard all / remaining PDCP SDUs (or PDUs) contained in the corresponding PDU set at the PDU set level.

[0213] For example, the base station may configure a discard timer for a specific PDU set in the UE through RRC signaling. The corresponding discard timer may be based on a discardTimer for discarding a PDCP SDU according to the prior art (TS 38.323 5.3).

[0214] As another example, when the discard timer for a PDCP SDU according to the prior art or the discard timer for a PDU set mentioned above expires, the transmitting PDCP entity may discard the PDCP SDU together with the corresponding PDCP data PDU. The transmitting PDCP entity may discard the PDCP SDU together with all / remaining / all non-discarded / remaining non-discarded PDCP data PDUs contained in the PDU set associated / mapped / included by the corresponding PDCP SDU. The PDCP SDU may be a PDCP-data-PDU / PDCP-SDU that is equal in one or more of the PDU set related information (e.g., PDU set ID, PDU set sequence number, PDU set importance / priority), as well as all / remaining / all non-discarded / remaining non-discarded PDCP data PDUs contained in the above-mentioned PDU set.

[0215] As another example, if the discard timer for a PDCP SDU according to the prior art or the discard timer for a PDU set described above expires, the transmitting PDCP entity may indicate this to the lower layer. The RLC entity that receives the corresponding information (by any method) may reconfigure the corresponding RLC entity. Alternatively, the corresponding RLC entity may discard all / remaining / all non-discarded / remaining non-discarded RLC SDUs, RLC SDU segments, and RLC PDUs. (Included in the PDU-set associated / mapped / contained in the corresponding PDCP / RLC SDU).

[0216] For another example, when the corresponding PDUP SDU or PDU-set is identified to have been successfully transmitted according to the PDCP status report of the prior art or by identifying the status report of the PDU-set, the sending PDCP entity may discard the PDCP SDU together with the corresponding PDCP data PDU. The sending PDCP entity may discard the PDCP SDU together with all / remaining / all non-discarded / remaining non-discarded PDCP data PDUs contained in the PDU set associated / mapped / included with the corresponding PDCP SDU. The PDCP SDU may be a PDCP-data-PDU / PDCP-SDU that is equal in one or more PDU set related information (e.g., PDU set ID, PDU set sequence number, PDU set importance / priority), as well as all / remaining / all non-discarded / remaining non-discarded PDCP data PDUs contained in the above-mentioned PDU set.

[0217] For another example, the base station may receive auxiliary information for configuring wireless parameters for PDU-set processing from the UE via RRC signaling, or receive auxiliary information for configuring wireless parameters for PDU-set processing from a core network node (e.g., AMF / SMF) via NGAP signaling on a related NAS processor. For example, the base station may receive one of the above-mentioned PDU set-level QoS parameters (e.g., PDU set-level delay budget, PDU set discard time, and (expected) time indicating the upper / lower limit / limit required before all the PDUs included in the corresponding PDU set are discarded). The base station may set a PDU-set discard timer (based on) the corresponding value and configure it in the UE.

[0218] PDCP status report containing PDU-set-related information

[0219] A status report may be defined and provided on any L2 sublayer to report the status of information related to a PDU set. Below, for the convenience of description, a method for defining and using a status report of PDCP is described. However, this is only for the convenience of description, and it is obvious that providing corresponding functions on any sublayer of SDAP / PDCP / RLC / MAC is also within the scope of the present invention.

[0220] For the DRB mapped to the PDU-set configured by the higher layer (RRC), in order to be able to send the PDCP status report to the uplink, the PDCP entity may trigger the PDCP status report containing PDU-set-related information in one or more of the following situations.

[0221] For example, when the higher layer (e.g., RRC) requests reconfiguration of the PDCP entity, when the higher layer requests PDCP data recovery, when the higher layer requests uplink data switching, and when the higher layer instructs the DRB / PDCP entity to reconfigure to map a PDU-set (e.g., reconfiguration for indicating PDU-set remapping), the PDCP status report including PDU-set-related information may be triggered.

[0222] As another example, the corresponding status report may be applicable to an AM DRB and / or a UM DRB.

[0223] If the PDCP status report is triggered, the receiving PDCP entity may compile the PDCP status report.

[0224] The corresponding information may include the uplink PDCP SN / COUNT transmitter status and the downlink PDCPSN / COUNT receiver status of the DRB mapped to the PDU-set. Alternatively, it may include the uplink PDU-set-related information transmitter status and the downlink PDU-set-related information receiver status of the SDAP-SDU / PDU mapped to the PDU-set. Further, the source base station may also include the uplink PDU-set SN transmitter status and the downlink PDU-set SN receiver status of the DRB mapped to the PDU-set. In addition, it may also include the transmitter status of one or more pieces of information in the uplink PDU-set-related information of the DRB mapped to the PDU-set, and the receiver status of one or more pieces of information in the downlink PDU-set-related information. As another example, the uplink PDU-set-related information (e.g., one or more information in any PDU-set-related information such as PDU-set SN) transmitter status may include PDU-set information of the first lost uplink PDU-set (e.g., one or more information in any PDU-set-related information such as PDU-set SN). As another example, the downlink PDU-set-related information (e.g., one or more information in any PDU-set-related information such as PDU-set SN) receiver status may include the next PDU-set-related information (e.g., one or more information in any PDU-set-related information such as PDU-set SN) for the PDU-set that does not have the PDU-set SN. For another example, the downlink PDU-set-related information (e.g., one or more information in any PDU-set-related information such as PDU-set SN) receiver status may include the minimum PDU-set SN that the UE has not yet received. For another example, the receiver status of the downlink PDU-set-related information (for example, one or more information in any PDU-set-related information such as the PDU-set SN) may include a minimum PDU-set SN, wherein all the data packets / PDUs belonging to the corresponding PDU-set have not been received by the UE. As another example, the bitmap field may be configured to not include the first lost PDU-set (or a PDU with PDU-set-related information, or a PDU-set SN, or a PDU-set including a lost PDCP-SDU / SDAP-SDU), but include the PDU-set PDU at the end (or a PDU with the PDU-set-related information, or a PDU-set SN, or a PDU-set including the lost PDCP-SDU / SDAP-SDU). As another example, the bitmap field may be configured to include the first lost PDU-set PDU, but not include the last sequential PDU-set PDU.

[0225] Differentiated processing of PDU sets in L2 sublayer

[0226] When one or more PDU-sets are mapped to a DRB and processed, a method for differentiated processing thereof in the corresponding L2 sublayer may be provided to support differentiated processing of each PDU-set (e.g., each PDU-set-ID, each PDU-set sequence number with the same PDU-set-ID, or each PDU-set importance / priority with the same PDU-set-ID) in any L2 sublayer (e.g., SDAP / PDCP / RLC / MAC).

[0227] For example, one or more RLC entities may be associated with the PDU-set-related information described above to provide differentiated processing for each PDU set.

[0228] For example, for the data radio bearer mapped to a PDU set, each PDCP entity may be associated with one or more UM RLC entities (for the same direction). (e.g., 1xN UM RLC entity, where N is 1, 2, 3, ...)

[0229] As another example, for the data radio bearer mapped to the PDU set, each PDCP entity may be associated with one or more AM RLC entities (e.g., 1xN AMR LC entities, where N is 1, 2, 3, ...)

[0230] As another example, the number (N) of the corresponding UM / AM RLC entities can be associated with the PDU set identifier and / or PDU set sequence number described above. For example, when the PDU-set identifier and / or PDU-set sequence number has n bits (where n is a natural number, such as 1, 2, 3, 4, ...), it can be N = 2*n. For example, when the corresponding information has 2 bits, there can be 4 RLC entities. The base station can indicate to the UE through RRC signaling the information associating the PDU-set identifier or PDU-set sequence number with the corresponding RLC entity. Alternatively, the PDU-set SDU / PDU associated with the corresponding PDU-set identifier or PDU-set sequence number can be associated with the corresponding RLC entity through a modulo operation. The sending PDCP entity can submit the PDCP PDU belonging to the corresponding PDU set to the associated RLC entity.

[0231] As another example, the number (N) of the corresponding UM / AM RLC entities may be associated with the number of PDU sets having different PDU set importance / priority values, the PDU sets being associated with the PDU set to be transmitted via the corresponding radio bearer. For example, if the PDU set SDU / PDU having two PDU set importances / priorities is transmitted via the corresponding radio bearer, the number of the corresponding radio bearers may be 2. The base station may indicate information associating the PDU-set-importance / priority with the corresponding RLC entity to the UE via RRC signaling. The transmitting PDCP entity may submit the PDCP PDU belonging to the corresponding PDU set to the associated RLC entity.

[0232] As another example, the configuration of the logical channel carried by the RLC through the corresponding RLC entity may include parameters associated with one or more pieces of information in the above-mentioned PDU set related information. For example, it may include parameters related to PDU-set-importance / priority. Through this, the MAC layer can use the corresponding information in the logical channel priority processor to process data or data transmission / retransmission.

[0233] For another example, an RLC entity may include one or more of the above PDU set related information in the RLC header and provide differentiated processing for each PDU set. This can be achieved by exchanging SDAP with RLC in the previous embodiment.

[0234] As another example, the configuration of the logical channel carried by the RLC entity may include parameters associated with the one or more PDU set related information. For example, it may include parameters related to PDU-set-importance / priority. Through this, the MAC layer may use the corresponding information in the logical channel priority processor to process data or data transmission / retransmission.

[0235] Activation / deactivation / switching / fallback of PDU set processing

[0236] In order for the UE and the base station to map and process one or more PDU-sets to one DRB, various functions need to be operated to support differentiated processing of each PDU-set (e.g., each PDU-set-ID, each PDU-set sequence number with the same PDU-set-ID, or each PDU-set importance / priority with the same PDU-set-ID) in the L2 sublayer (e.g., SDAP / PDCP / RLC / MAC). This may be a load / burden on each sublayer. Therefore, the UE or the base station may need to operate by defining L2 signaling to indicate activation / deactivation of the corresponding function. For example, one or more of the SDAP control PDU, the PDCP control PDU, the RLC control PDU, and the MAC control unit may be used to indicate activation / deactivation / switching / fallback of the PDU set processing of the corresponding radio bearer on each sublayer. The sublayer that receives the corresponding signaling may transmit the corresponding information to another sublayer (a higher sublayer or a lower sublayer) where the corresponding function operates. The corresponding sublayer may perform the corresponding operation.

[0237] According to the above embodiments, the information / field unit generated in the service / application running in the higher layer can be used to effectively process the packet data based on the traffic characteristics in the wireless network. The UE and the base station capable of executing the above embodiments will be briefly described below. The embodiments not described below can also be executed by the UE and the base station based on the above operations.

[0238] Fig.19 is a block diagram showing a UE according to an embodiment.

[0239] Reference Fig.19 , a UE 1900 for processing an application data stream may include: a receiver 1930 for receiving a high-level message including wireless resource configuration information, wherein the wireless resource configuration information is configured for sending / receiving specific application data; and a controller 1910 for configuring the wireless resource configuration information in the UE and performing differentiated processing on user plane data of the application data based on the wireless resource configuration information.

[0240] According to one embodiment, the wireless resource configuration information may include protocol data unit (PDU) set information, the information including at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information. Alternatively, the wireless resource configuration information may include at least one of auxiliary information of application traffic characteristics and PDU set information.

[0241] According to one embodiment, the application data stream (or application data) may be a PDU set of specific application data with high correlation between data streams such as XR or CG. The receiver 1930 may receive from the base station the radio resource configuration information associated with the auxiliary information that may help resolve the characteristics of the corresponding application traffic. Alternatively, the receiver 1930 may receive from the base station the radio resource configuration information associated with the PDU set information. In addition, the receiver 1930 may receive from the base station the radio resource configuration information associated with the auxiliary information and the PDU set information.

[0242] According to one embodiment, the auxiliary information may include at least one of uplink or downlink periodicity information about the application data stream and jitter information associated with the periodicity information. As mentioned above, the application data stream may cause uplink or downlink with a non-integer period according to the traffic characteristics of the corresponding application. In addition, the application data stream may cause a certain degree of jitter in uplink or downlink transmission / reception. Therefore, the periodicity information can be set to a non-integer value, or the periodicity information can be set to an integer value. By using the auxiliary information, the UE can perform effective application traffic processing by applying send / receive parameters that take into account the characteristics of the corresponding application data stream.

[0243] According to another embodiment, the PDU set information may include at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information. For example, the PDU set information may include a PDU set sequence number used in the corresponding application. Alternatively, the PDU set information may include indication information indicating the last PDU of the PDU set terminated by the corresponding application. Alternatively, the PDU set information may include importance information applied to the PDU set. A PDU set may be set to have the same importance.

[0244] Meanwhile, the high-layer message may be an RRC message. For example, the high-layer message may include an N1 session management (SM) container including a PDU set QoS parameter. That is, the UE may identify the N1 SM container included in the high-layer message and use the PDU set QoS parameter included in the N1 SM container to apply to the corresponding application data flow processing. Alternatively, the high-layer message may also be a message broadcast by the base station.

[0245] The controller 1910 may store the received radio resource configuration information in the UE, or the controller 1910 may store the radio resource configuration information as a parameter value of the UE and use it later when needed.

[0246] According to an embodiment, the controller 1910 may configure a radio link control (RLC) entity in association with at least one information included in the PDU set information.

[0247] According to another embodiment, the radio resource configuration information may include one or more DRX configuration information supporting non-integer values ​​based on auxiliary information, and data radio bearer configuration information associated with one or more logical channel configurations based on PDU set information.

[0248] According to another embodiment, the controller 1910 may configure the DRX parameter by storing or applying the DRX configuration information supporting non-integer values ​​included in the radio resource configuration information to the UE. Thus, a UE DRX operation suitable for the application data stream sent and received with a period set to a non-integer value may be performed.

[0249] According to another embodiment, the controller 1910 may configure the DRB of the UE using the DRB configuration information associated with the logical channel configuration included in the radio resource configuration information. The corresponding logical channel configuration is configured based on the PDU set information, and a logical channel and DRB suitable for the application data flow may be configured in the UE.

[0250] In addition, the UE 1900 may apply the radio resource configuration information to the UE and transmit and receive user plane data generated in the corresponding application layer. In this case, the controller 1910 may distinguish the user plane data of the corresponding application data from other normal data based on the radio resource configuration information.

[0251] For example, the controller 1910 may process the user plane data generated in the corresponding application layer using the data radio bearer configured using the radio resource configuration information. As another example, the controller 1910 may control the DRX operation of the UE according to the uplink or downlink key period generated as a non-integer value by applying the DRX parameter configured using the radio resource configuration information to the UE.

[0252] At the same time, the above-mentioned protocol data unit (PDU) of user plane data for a specific application can be configured to include one or more information of the PDU set sequence number, PDU set end PDU indication information and PDU set importance. For example, one or more information of the PDU set sequence number, PDU set end PDU indication information and PDU set importance can be included in the service data adaptation protocol (SDAP) header or the packet data convergence protocol (PDCP) header of the PDU. In other words, the SDAP header may include one or more information constituting the corresponding PDU set information. And / or, the PDCP header may include one or more information constituting the corresponding PDU set information. In this way, the corresponding PDU set information can be distinguished and processed.

[0253] For example, the controller 1910 may discard all protocol data units (PDUs) or service data units (SDUs) associated with at least one information included in the PDU set information in the packet data convergence protocol (PDCP) entity or the radio link control (RLC) entity. In other words, all related PDU sets may be discarded.

[0254] The protocol data unit (PDU) or the service data unit (SDU) can be discarded according to the timer configured to distinguish each PDU set information. The corresponding timer can be included in the radio resource configuration information and configured in the UE. Further, the corresponding timer can be configured and operated in association with each PDU set. At the same time, if the timer expires, the controller 1910 can instruct the lower layer to discard the protocol data unit (PDU) or the service data unit (SDU). For example, if the timer expires, the PDCP entity can instruct the RLC entity to discard the PDU or SDU associated with the corresponding timer.

[0255] In addition, the controller 1910 controls the overall operation of the UE 1900 according to session / QoS / policy control to provide packet data processing based on information generated in the application layer required to perform the above disclosure.

[0256] The transmitter 1920 and the receiver 1930 are used to send or receive signals, messages or data required to execute the above disclosure with the base station or core network entity.

[0257] Fig. 20 is a block diagram showing a base station according to an embodiment.

[0258] Reference Fig. 20The base station 2000 for processing the application data flow may include: a transmitter 2020, used to send a high-level message including wireless resource configuration information to the UE, where the wireless resource configuration information is configured to send / receive specific application data to the UE; and a controller 2010, used to differentiate and process user plane data of the application data based on the wireless resource configuration information.

[0259] According to one embodiment, the wireless resource configuration information may include protocol data unit (PDU) set information, the information including at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information. Alternatively, the wireless resource configuration information may include at least one of auxiliary information of application traffic characteristics and PDU set information. For example, an application data stream (or application data) may be a PDU set of specific application data with a high correlation between data streams such as XR or CG. The transmitter 2020 may send wireless resource configuration information associated with the auxiliary information that may help resolve the characteristics of the corresponding application traffic to the UE. Alternatively, the transmitter 2020 may send wireless resource configuration information associated with the PDU set information to the UE. Alternatively, the transmitter 2020 may send the wireless resource configuration information associated with the auxiliary information and the PDU set information to the UE.

[0260] According to one embodiment, the auxiliary information may include at least one of uplink or downlink periodicity information about the application data stream and jitter information associated with the periodicity information. As described above, the application data stream may cause uplink or downlink with a non-integer period according to the traffic characteristics of the corresponding application. In addition, the application data stream may cause a certain degree of jitter in uplink or downlink transmission / reception. Therefore, the periodicity information may be set to a non-integer value, or the periodicity information may be set to an integer value. By using the auxiliary information, the UE can effectively process application traffic by applying send / receive parameters according to the characteristics of the corresponding application data stream.

[0261] According to another embodiment, the PDU set information may include at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information. For example, the PDU set information may include a PDU set sequence number used in the corresponding application. Alternatively, the PDU set information may include indication information indicating the last PDU of the PDU set terminated by the corresponding application. Alternatively, the PDU set information may include importance information applied to the PDU set. A PDU set may be set to have the same importance.

[0262] The high-layer message may be an RRC message. For example, the high-layer message may include an N1 session management (SM) container including a PDU set QoS parameter. Alternatively, the high-layer message may also be a message broadcast by the base station.

[0263] Meanwhile, in order to distinguish and process the user plane data of the specific application data, it is necessary to identify the protocol data unit (PDU) of the corresponding user plane data.

[0264] To this end, the PDU of the user plane data for a specific application can be configured to include one or more of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance. For example, one or more of the PDU set sequence number, the PDU set end PDU indication information, and the PDU set importance can be included in the Service Data Adaptation Protocol (SDAP) header or the Packet Data Convergence Protocol (PDCP) header of the PDU. In other words, the SDAP header may include one or more information constituting the corresponding PDU set information. And / or, the PDCP header may include one or more information constituting the corresponding PDU set information. In this way, the corresponding PDU set information can be differentiated and processed.

[0265] The protocol data unit (PDU) or the service data unit (SDU) can be discarded according to the timer configured to distinguish each PDU set information. The corresponding timer may be included in the radio resource configuration information. Further, the corresponding timer can be configured and operated in association with each PDU set. At the same time, if the timer expires, the lower layer can be instructed to discard the protocol data unit (PDU) or the service data unit (SDU). For example, if the timer expires, the PDCP entity can instruct the RLC entity to discard the PDU or SDU associated with the corresponding timer.

[0266] In addition, the controller 2010 controls the overall operation of the base station 2000 according to session / QoS / policy control to provide packet data processing based on information generated in the application layer required to perform the above disclosure.

[0267] The transmitter 2020 and the receiver 2030 are used to send or receive signals, messages or data required to execute the above-mentioned disclosed content with the UE or core network entity.

[0268] The above embodiments may be supported by standard documents disclosed in at least one of wireless access systems such as IEEE 802, 3GPP and 3GPP2. That is, the steps, configurations and components not described in this embodiment may be supported by the above standard documents to clarify the technical concepts of the present disclosure. In addition, all terms disclosed herein may be described by the above standard documents.

[0269] The above embodiment can be implemented in various ways. For example, the present embodiment can be implemented as hardware, firmware, software or a combination thereof.

[0270] When implemented by hardware, the method according to the present embodiment can be implemented as at least one of an application specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a processor, a controller, a microcontroller or a microprocessor.

[0271] In the case of firmware or software implementation, the method of this embodiment can be implemented in the form of a device, process or function for performing the above functions or operations. The software code can be stored in a memory unit and can be driven by a processor. The memory unit can be arranged inside or outside the processor and can exchange data with the processor in various well-known ways.

[0272] In addition, the terms "system", "processor", "controller", "component", "module", "interface", "model", "unit", etc. can generally represent computer-related entity hardware, a combination of hardware and software, software, or running software. For example, the above-mentioned components can be but are not limited to processes driven by a processor, processors, controllers, control processors, entities, execution threads, programs and / or computers. For example, an application running in a controller or processor and the controller or processor can both be components. One or more components can be provided in a process and / or execution thread, and the components can be provided in a single device (e.g., a system, a computing device, etc.), or can be distributed across two or more devices.

[0273] The above description is merely an exemplary description of the technical idea of ​​the present disclosure, and those skilled in the art will be able to make various modifications and variations without departing from the essential features of the present disclosure. In addition, the present embodiment is not intended to limit the technical idea of ​​the present disclosure, but to illustrate it, so the scope of the present technical idea is not limited by these embodiments. The scope of protection of the present disclosure should be interpreted according to the attached claims, and all technical ideas within the equivalent scope should be interpreted as included in the scope of rights of the present disclosure.

[0275] CROSS-REFERENCE TO RELATED APPLICATIONS

[0276] This patent application claims the priority of Korean Patent Application Nos. 10-2022-0053088 (filed on April 28, 2022) and 10-2023-0045834 (filed on April 7, 2023) filed in the Korean Intellectual Property Office under Section 119(a) of the United States Patent Act (35 U.S.C. §119(a)), the disclosures of which are incorporated herein by reference in their entirety. In addition, if this patent application claims priority in a country other than the United States for the same reasons as above, its entirety will be incorporated into this patent application by reference.

Claims

1. A method for processing an application data flow by a user equipment (UE), the method comprising the following steps: receiving a high-layer message including radio resource configuration information, wherein the radio resource configuration information is configured for sending / receiving specific application data; configuring the radio resource configuration information in the UE; as well as The user plane data of the application data is differentiated and processed according to the wireless resource configuration information.

2. The method according to claim 1, wherein: The wireless resource configuration information includes protocol data unit (PDU) set information, and the PDU set information includes at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information.

3. The method according to claim 2, wherein: In the step of configuring the radio resource configuration information in the UE, a radio link control (RLC) entity is configured in association with at least one information included in the PDU set information.

4. The method according to claim 1, wherein: The protocol data unit (PDU) of the user plane data includes one or more information of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information, and Among them, one or more information of the PDU set sequence number, the PDU set end PDU indication information, and the PDU set importance is included in a Service Data Adaptation Protocol (SDAP) header or a Packet Data Convergence Protocol (PDCP) header of the PDU.

5. The method according to claim 1, wherein: In the step of performing differentiation processing, all protocol data units (PDUs) or service data units (SDUs) associated with at least one information included in the PDU set information in the packet data convergence protocol (PDCP) entity or the radio link control (RLC) entity are discarded.

6. The method according to claim 5, wherein: The protocol data unit (PDU) or the service data unit (SDU) is discarded according to a timer configured for each of the PDU set information.

7. The method according to claim 5, wherein: In the step of performing a differentiation process, when the timer expires, the differentiation process instructs a lower layer to discard the protocol data unit (PDU) or the service data unit (SDU).

8. A method for processing an application data stream by a base station, the method comprising the following steps: Sending a high-layer message including radio resource configuration information to the UE, where the radio resource configuration information is configured for sending / receiving specific application data; as well as The user plane data of the application data is differentiated and processed according to the wireless resource configuration information.

9. The method according to claim 8, wherein: The wireless resource configuration information includes protocol data unit (PDU) set information, and the PDU set information includes at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information.

10. The method according to claim 8, wherein: The protocol data unit (PDU) of the user plane data includes one or more information of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information, and Among them, one or more information of the PDU set sequence number, the PDU set end PDU indication information, and the PDU set importance is included in a Service Data Adaptation Protocol (SDAP) header or a Packet Data Convergence Protocol (PDCP) header of the PDU.

11. A UE for processing an application data flow, the UE comprising: a receiver, the receiver being configured to receive a high-layer message including radio resource configuration information, the radio resource configuration information being configured to be used for sending / receiving specific application data; as well as A controller is used to configure the wireless resource configuration information in the UE and perform differentiated processing on the user plane data of the application data according to the wireless resource configuration information.

12. The UE according to claim 11, wherein: The wireless resource configuration information includes protocol data unit (PDU) set information, and the PDU set information includes at least one of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information.

13. The UE according to claim 12, wherein: The controller configures a radio link control (RLC) entity in association with at least one information included in the PDU set information.

14. The UE according to claim 11, wherein: The protocol data unit (PDU) of the user plane data includes one or more information of a PDU set sequence number, a PDU set end PDU indication information, and a PDU set importance information, and Among them, one or more information of the PDU set sequence number, the PDU set end PDU indication information, and the PDU set importance is included in a Service Data Adaptation Protocol (SDAP) header or a Packet Data Convergence Protocol (PDCP) header of the PDU.

15. The UE according to claim 11, wherein: The controller discards all protocol data units (PDUs) or service data units (SDUs) associated with at least one information included in PDU set information in a packet data convergence protocol (PDCP) entity or a radio link control (RLC) entity.

16. The UE according to claim 15, wherein: The protocol data unit (PDU) or the service data unit (SDU) is discarded according to a timer configured for each of the PDU set information.

17. The UE according to claim 15, wherein: When the timer expires, the controller instructs a lower layer to discard the protocol data unit (PDU) or the service data unit (SDU).

Citation Information

Patent Citations

  • Apparatus and method for displaying vehicle information

    KR1020220053088A

  • Sulfur-containing polymer, manufacturing method thereof, and heat-resistant and infrared-transmissive polymer film comprising the same

    KR1020230045834A

Cited By

  • Communication method, electronic equipment and related device

    CN121568160A

  • Communication method, electronic device, and related apparatus

    CN121568160B