Method and apparatus for controlling packet data processing
By using application layer information to configure and process XR application traffic characteristics in radio networks, the problems of delay and jitter in XR and CG scenarios are solved, and the sequential delivery and seamless handover of data flows between base stations are realized, thereby improving the efficiency of mobile communications and performance.
Patent Information
- Application Number
- CN202380035788.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-04-17
- Filing Date
- 2023-04-19
- Publication Date
- 2024-12-03
AI Technical Summary
Existing mobile communication technologies are difficult to effectively identify and process the characteristics of information traffic of augmented reality (XR) applications, resulting in jitter and delay problems in downlink video streams in XR and cloud gaming (CG) scenarios, and the current UE is not continuous The reception configuration is not suitable for non-integer periods and variable data rates of XR information traffic.
By configuring and processing application information traffic characteristics using information acquired from higher layers/application layers in a radio network, a method and device are provided to control the handover of application data flows between UEs, including transmitting a PDU set to a target base station QoS parameters and generate radio bearer configuration information to ensure sequential delivery of data and seamless service.
Effectively identify and process XR application information traffic, reduce latency and jitter, improve the performance of XR and CG services, and ensure sequential delivery and seamlessness in data forwarding and receiving between base stations.
Smart Images

Figure CN119072910A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a technique for controlling packet data processing. 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-human communications performed with the help of handheld and wearable terminals. Extended reality (XR) is used as 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 the game 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 information traffic with high data rates (with possible jitter) in downlink video streams. Often paired with frequent uplink (e.g. gesture / control updates) and / or uplink video streams. Both downlink and uplink information traffic must adhere to relatively tight packet delay budgets (PDBs).
[0004] Furthermore, many XR and CG terminals have limited battery power. However, current UE discontinuous reception (DRX) configurations are not suitable due to the non-integer periodicity of XR information traffic, variable XR data rates, and the quasi-periodic nature of the XR period.
[0005] The set of XR and CG services is diverse. The data stream (e.g., video) can change dynamically while the service is running over the radio network (e.g., NR).
[0006] Therefore, the packets within a frame are interdependent. However, typical mobile communication technologies do not provide a specific method for enabling terminals / base stations / core networks to effectively identify and process XR application information traffic. Summary of the invention
[0007] Technical issues
[0008]
[0013] With the foregoing background in mind, the present disclosure introduces a configuration method and apparatus for providing packet data processing that takes into account application information traffic characteristics using information provided from higher layers / application layers in a wireless network.
[0009] Technical Solutions
[0010] In one aspect, the present disclosure may provide a method for controlling the handover of a UE transmitting / receiving an application data flow by a source base station. The method may include: transmitting a handover request message including QoS parameters of a protocol data unit (PDU) set of application data to a target base station; receiving a handover response message including radio bearer configuration information generated based on the QoS parameters of the PDU set from the target base station; and controlling the forwarding data of the UE's application data (e.g., in, between, or from) to be delivered to the target base station.
[0011] In another aspect, the present disclosure may provide a method for controlling the handover of a UE transmitting / receiving an application data flow by a target base station. The method may include: receiving a handover request message including QoS parameters of a protocol data unit (PDU) set of application data from a source base station; generating radio bearer configuration information of the application data based on the QoS parameters of the PDU set; transmitting a handover response message including the radio bearer configuration information to the source base station; and receiving forwarding data of the application data of the UE from the source base station.
[0012] In still another aspect, the present disclosure may provide a source base station for controlling handover of a UE transmitting / receiving an application data stream. The source base station may include: a transmitter that transmits a handover request message including QoS parameters of a protocol data unit (PDU) set of application data to a target base station; a receiver that receives a handover response message including radio bearer configuration information generated based on the QoS parameters of the PDU set from the target base station; and a controller that controls forwarding data of the UE's application data to the target base station.
[0013] In yet another aspect, the present disclosure may provide a target base station for controlling handover of a UE transmitting / receiving an application data stream. The target base station may include a receiver that receives a handover request message including QoS parameters of a protocol data unit (PDU) set of application data from a source base station; a controller that generates radio bearer configuration information of the application data based on the QoS parameters of the PDU set; and a transmitter that transmits a handover response message including the radio bearer configuration information to the source base station, wherein the receiver also receives forwarding data of the application data of the UE from the source base station.
[0014] Beneficial Effects
[0015] According to an embodiment, a UE, a base station, or a core network entity in a radio network may effectively identify and process XR application information traffic. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Figure 1 is a diagram schematically illustrating an NR wireless communication system according to an embodiment of the present disclosure;
[0017] Figure 2 is a view schematically showing a frame structure in an NR system according to an embodiment of the present disclosure;
[0018] Figure 3 is a view for explaining a resource grid supported by a radio access technology according to an embodiment of the present disclosure;
[0019] Figure 4 is a view for explaining a bandwidth portion supported by a radio access technology according to an embodiment of the present disclosure;
[0020] Figure 5 is a view showing an example of a synchronization signal block in a radio access technology according to an embodiment of the present disclosure;
[0021] Figure 6 is a signal diagram for explaining a random access procedure in a radio access technology according to an embodiment of the present disclosure;
[0022] Figure 7 It is a view used to explain CORESET;
[0023] Figure 8 is a diagram showing an example of a structure for implementing a 5G-XR function in a 5G system;
[0024] Fig. 9 is a flowchart for describing the operation of a source base station according to an embodiment;
[0025] Fig.10 is a flowchart for describing the operation of a target base station according to an embodiment;
[0026] Fig.11 is a diagram exemplarily illustrating a PDU session resource setting request delivery information element according to an embodiment;
[0027] Fig.12 is a diagram exemplarily illustrating a PDU session resource modification request delivery information element according to an embodiment;
[0028] Fig.13 is a view exemplarily showing SDAP configuration information elements according to an embodiment;
[0029] Fig.14 is a diagram exemplarily illustrating a PDU session resource setting request delivery information element according to another embodiment;
[0030] Fig.15 is a diagram exemplarily illustrating a PDU session resource modification request transmission information element according to another embodiment;
[0031] Fig.16is a view exemplarily showing SDAP configuration information elements according to another embodiment;
[0032] Fig.17 is a diagram showing a DL SDAP data PDU format with an SDAP header according to an embodiment;
[0033] Fig.18 is a diagram showing a UL SDAP data PDU format with an SDAP header according to an embodiment;
[0034] Fig.19 is a block diagram showing a configuration of a source base station according to an embodiment; and
[0035] Fig. 20 is a block diagram showing a configuration of a target base station according to an embodiment. DETAILED DESCRIPTION
[0036] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to the attached illustrative figures. In the accompanying drawings, similar reference numerals are used to represent similar elements throughout the accompanying drawings, even if they are shown on different drawings. In addition, in the following description of the present disclosure, when it may make the subject matter of the present disclosure quite unclear, the detailed description of the known functions and configurations contained herein will be omitted. When using the expressions "including", "having", "including" or similar expressions as mentioned herein, any other part can be added, unless the expression "only" is used. When an element is expressed in the singular, the element can cover the plural form, unless the special mention of the element is clearly made.
[0037] In addition, when describing the components of the present disclosure, terms such as first, second, A, B, (A), (B) or the like may be used herein. Each of these terms is not used to define the nature, order or sequence of the corresponding components, but is only used to distinguish the corresponding component from (a plurality of) other components.
[0038] When describing the positional relationship between components, if two or more components are described as being “connected,” “combined,” or “coupled” to each other, it should be understood that the two or more components may be directly “connected,” “combined,” or “coupled” to each other, and the two or more components may be “connected,” “combined,” or “coupled” to each other by another component “interposed” therebetween. In this case, the other component may be included in at least one of the two or more components that are “connected,” “combined,” or “coupled” to each other.
[0039] For example, in the description of a series of operating methods or manufacturing methods, expressions using "after", "after...", "next", "before" and the like may also cover the situation where the operations or processes are not performed continuously, unless "immediately" or "directly" is used in the expression.
[0040] Numerical values of components or information corresponding thereto (e.g., levels or the like) mentioned herein may be construed as including error ranges caused by various factors (e.g., process factors, internal or external influences, noise, etc.) even if no explicit description thereof is provided.
[0041] A wireless communication system in this specification refers to a system for providing various communication services (such as voice services and data services) using radio resources. A wireless communication system may include user equipment (UE), a base station, a core network, and the like.
[0042] The embodiments disclosed below can be applied to wireless communication systems using various radio access technologies. For example, the embodiments can be applied to various radio 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) or the like. In addition, radio access technology can refer to various generations of communication technologies established by various communication organizations (such as 3GPP, 3GPP2, Wi-Fi, Bluetooth, IEEE, ITU or the like), as well as specific access technologies. For example, CDMA can be implemented as a wireless technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as a wireless technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rate for GSM Evolution (EDGE). OFDMA can be implemented as wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802-20, Evolved UTRA (E-UTRA), and the like. IEEE 802.16m is an evolution of IEEE 802.16e, which provides backward compatibility with systems based on IEEE 802.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), which adopts OFDMA in the downlink and SC-FDMA in the uplink. As described above, the embodiments can be applied to radio access technologies that have been launched or commercialized, and can be applied to radio access technologies that are being developed or will be developed in the future.
[0043] The UE used in the specification must be interpreted in a broad sense, indicating a device including a wireless communication module that communicates with a base station in a wireless communication system. For example, UE includes user equipment (UE) in WCDMA, LTE, NR, HSPA, IMT-2020 (5G or New Radio) and the like, a mobile station in GSM, a user terminal (UT), a subscriber station (SS), a wireless device, and the like. In addition, the UE may be a portable user device such as a smartphone, or, depending on its type of use, a vehicle in a V2X communication system, a device including a wireless communication module in a vehicle, and the like. In the case of a machine-type communication (MTC) system, the UE may refer to an MTC terminal, an M2M terminal, or a URLLC terminal, which employs a communication module capable of performing machine-type communication.
[0044] A base station or cell in this specification refers to an end that communicates with a UE through a network, and covers various coverage areas, such as Node-B, evolved Node-B (eNB), gNode-B, 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, and the like. In addition, a cell may be used as a meaning including a bandwidth part (BWP) in the frequency domain. For example, a serving cell may refer to an active BWP of a UE.
[0045] The various cells listed above are provided with a base station that controls one or more cells, and the base station can be interpreted in two meanings. The base station can be 1) a device for providing a megacell, macrocell, microcell, picocell, femtocell or small cell connected to a wireless area, or the base station can be 2) the wireless area itself. In the above description 1), the base station can be a device controlled by the same entity and providing a predetermined wireless area, or all devices that interact with each other and cooperate to configure the wireless area. For example, depending on the configuration method of the wireless area, the base station can be a point, a transmission / reception point, a transmission point, a reception point, and the like. In the above description 2), the base station can be a wireless area in which a user equipment (UE) can be enabled to transmit data to other UEs or adjacent base stations and receive data from other UEs or adjacent base stations.
[0046] In this specification, a cell may refer to 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.
[0047] Uplink (UL) refers to a scheme for transmitting data from a UE to a base station, and downlink (DL) refers to a scheme for transmitting data from a base station to a UE. Downlink may mean communication or a communication path from multiple transmission / reception points to a UE, and uplink may mean communication or a communication path from a UE to multiple transmission / reception points. In the downlink, a transmitter may be part of multiple transmission / reception points, and a receiver may be part of a UE. In addition, in the uplink, a transmitter may be part of a UE, and a receiver may be part of multiple transmission / reception points.
[0048] The uplink and downlink transmit and receive control information on control channels such as the physical downlink control channel (PDCCH) and the physical uplink control channel (PUCCH). The uplink and downlink transmit and receive data on data channels such as the physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH). In the following, the transmission and reception of signals on channels such as PUCCH, PUSCH, PDCCH, PDSCH or the like may be expressed as "transmission and reception of PUCCH, PUSCH, PDCCH, PDSCH or the like".
[0049] For clarity, the following description will focus on a 3GPP LTE / LTE-A / NR (New Radio) communication system, but the technical features of the present disclosure are not limited to the corresponding communication system.
[0050] After studying 4G (fourth generation) communication technology, 3GPP has been developing 5G (fifth generation) communication technology in order to meet the requirements of ITU-R for next-generation radio access technology. Specifically, 3GPP is developing LTE-Apro as 5G communication technology by improving LTE-Advanced technology to meet the requirements of ITU-R, as well as new NR communication technology that is completely different from 4G communication technology. Both LTE-Apro and NR refer to 5G communication technology. In the following, unless a specific communication technology is specified, 5G communication technology will be described based on NR.
[0051] Considering satellites, automobiles, new vertical industries, and the like in typical 4G LTE scenarios, various operation scenarios are defined in NR to support enhanced mobile broadband (eMBB) scenarios on the service side, massive machine-type communication (mMTC) scenarios where UEs are distributed with a high UE density over a vast area, thus requiring low data rates and asynchronous connections, and ultra-reliability and low-latency (URLLC) scenarios that require high responsiveness and reliability and support high-speed mobility.
[0052] To meet these scenarios, NR introduces a wireless communication system that employs new waveform and frame structure technologies, low-latency technologies, ultra-high frequency band (mmWave) support technologies, and forward-compatible provisioning technologies. In particular, the NR system has 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 drawings.
[0053] <Overview of the NR System>
[0054] Figure 1 It is a view schematically showing the NR system to which this embodiment is applicable.
[0055] Refer to 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, which provide user plane (SDAP / PDCP / RLC / MAC / PHY) and user equipment (UE) control plane (RRC) protocol terminations. Multiple gNBs or one gNB and an ng-eNB are connected to each other through the Xn interface. The gNBs and ng-eNBs are connected to the 5GC through 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 UE connection and mobility control functions, and a user plane function (UPF) for controlling user data. NR supports frequency bands below 6 GHz (Frequency Range 1, FR1) and frequency bands equal to or greater than 6 GHz (Frequency Range 2, FR2).
[0056] A gNB represents a base station that provides NR user plane and control plane protocol terminations to a UE. An ng-eNB represents a base station that provides E-UTRA user plane and control plane protocol terminations to a UE. The base stations described in this specification should be understood to cover both gNBs and ng-eNBs. However, as needed, a base station may also be used to separately refer to a gNB or an ng-eNB.
[0057] <NR Waveforms, Numerologies, and Frame Structures>
[0058] NR uses the CP-OFDM waveform (with a cyclic prefix) for downlink transmission and uses CP-OFDM or DFT-s-OFDM for uplink transmission. OFDM technology is easily combinable with multiple-input multiple-output (MIMO) schemes and allows for high-frequency efficiency with a low-complexity receiver.
[0059] Since the above three scenarios have different requirements for data rate, latency rate, coverage, and the like in NR, it is necessary to effectively meet the requirements of each scenario on the frequency bands constituting the NR system. To this end, techniques for effectively multiplexing radio resources based on multiple different numerologies have been proposed.
[0060] Specifically, the NR transmission numerology is determined based on the subcarrier spacing and the cyclic prefix (CP). As shown in Table 1 below, "μ" is used as an exponent of 2 to change exponentially based on 15 kHz.
[0061] [Table 1]
[0062] μ Subcarrier spacing Cyclic prefix Supporting Data Support 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
[0063] As shown in Table 1 above, NR can have five types of numerologies according to the subcarrier spacing. This is different from LTE, which is one of the 4G communication technologies where the subcarrier spacing is fixed at 15 kHz. Specifically, in NR, the subcarrier spacing for data transmission is 15 kHz, 30 kHz, 60 kHz, or 120 kHz, and the subcarrier spacing for synchronization signal transmission is 15 kHz, 30 kHz, 120 kHz, or 240 kHz. Additionally, the extended CP is only applied to the 60 kHz subcarrier spacing. In the frame structure of NR, a frame including 10 subframes (each subframe having the same length of 1 ms) and having a length of 10 ms is defined. A frame can be divided into two half-frames of 5 ms, and each half-frame includes 5 subframes. In the case of a subcarrier spacing of 15 kHz, one subframe includes one time slot, and each time slot includes 14 OFDM symbols.
[0064] Figure 2It is a view used to explain the frame structure in the NR system to which the present embodiment can be applied.
[0065] refer to Figure 2 , a time slot includes 14 OFDM symbols, which are fixed in the case of a conventional CP, but the length of the time slot in the time domain may vary depending on the subcarrier spacing. For example, in the case of a value with a 15kHz subcarrier spacing, the time slot is configured to have the same length of 1ms as the subframe. On the other hand, in the case of a value with a 30kHz subcarrier spacing, the time slot includes 14 OFDM symbols, but one subframe may include two time slots, each having a length of 0.5ms. That is, subframes and frames 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 depending on the subcarrier spacing.
[0066] NR defines the basic unit of scheduling as a slot, and also introduces mini slots (or sub slots or non-slot-based scheduling) to reduce the transmission delay in the radio part. If a wide subcarrier spacing is used, the length of a slot is shortened inversely proportional to it, thereby reducing the transmission delay in the radio part. Mini slots (or sub slots) are designed to effectively support URLLC scenarios, and mini slots can be scheduled in 2, 4 or 7 symbol units.
[0067] 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 has been defined that enables HARQ ACK / NACK to be transmitted directly in the transmission slot. This slot structure is called a "self-contained structure" and will be described.
[0068] NR is designed to support a total of 256 slot formats, and 62 of its slot formats are used in 3GPP Rel-15. Additionally, NR supports a common frame structure for constructing FDD or TDD frames through various combinations of time slots. For example, NR supports i) a slot structure in which all symbols of a time slot are configured for downlink, ii) a slot structure in which all symbols are configured for uplink, and iii) a slot structure in which downlink symbols and uplink symbols are mixed. Additionally, NR supports data transmission scheduled to be distributed over one or more time slots. Thus, the base station can use a slot format indicator (SFI) to inform the UE whether the time slot is a downlink time slot, an uplink time slot, or a flexible time slot. The base station can notify the slot format by indicating the index of a table configured through specific RRC signaling to the UE using the SFI. In addition, the base station can dynamically inform the slot format through downlink control information (DCI), or can statically or quasi-statically inform the slot format through RRC signaling.
[0069] <Physical Resources of NR>
[0070] Regarding the physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, bandwidth parts, and the like are considered.
[0071] An antenna port is defined as a channel carrying a symbol on an antenna port being inferred from another channel carrying a symbol on the same antenna port. If the large-scale attributes of the channel carrying the symbol on an antenna port can be inferred from another channel carrying a symbol on another antenna port, these two antenna ports may have a quasi-co-location or quasi-co-located (QC / QCL) relationship. The large-scale attributes include at least one of delay spread, Doppler spread, frequency shift, average received power, and reception timing.
[0072] Figure 3 A resource grid supported by a radio access technology according to an embodiment of the present disclosure is shown.
[0073] Reference Figure 3 , since NR supports multiple values in the same carrier, the resource grid can exist according to the corresponding values. Additionally, the resource grid can exist depending on the antenna port, subcarrier spacing, and transmission direction.
[0074] A resource block includes 12 subcarriers and is defined only in the frequency domain. Additionally, a resource element includes one OFDM symbol and one subcarrier. Thus, as Figure 3As shown, the size of a resource block can vary according to the subcarrier spacing. In addition, "Point A", common resource blocks, and virtual resource blocks, which serve as common reference points for the resource block grid, are defined in NR.
[0075] Figure 4 Shows a bandwidth part supported by a radio access technology according to an embodiment of the present disclosure.
[0076] Unlike LTE where the carrier bandwidth is fixed at 20 MHz, the maximum carrier bandwidth depends on the subcarrier spacing in NR and is configured to be 50 MHz to 400 MHz. Therefore, it is not assumed that all UEs use the entire carrier bandwidth. Thus, as Figure 4 shown, a bandwidth part (BWP) can be specified within the carrier bandwidth in NR such that a UE can use the bandwidth part. Additionally, the bandwidth part can be associated with a numerical value, can include a subset of consecutive common resource blocks, and can be dynamically activated over time. A UE can have up to four bandwidth parts in each of the uplink and downlink. The UE transmits and receives data using the activated bandwidth part during a given time period.
[0077] In the case of paired spectrum, the uplink and downlink bandwidth parts are configured independently. In the case of unpaired spectrum, to prevent unnecessary frequency retuning between downlink operation and uplink operation, the downlink bandwidth part and the uplink bandwidth part are paired and configured to share the center frequency.
[0078] <Initial Access in NR>
[0079] In NR, a UE performs a cell search and a random access procedure to access a base station and communicate with the base station.
[0080] Cell search is a process by which a UE synchronizes with the cell of a corresponding base station using synchronization signal blocks (SSBs) transmitted from the base station and obtains the physical layer cell ID and system information.
[0081] Figure 5 Shows an example of a synchronization signal block in a radio access technology according to an embodiment of the present disclosure.
[0082] Refer to Figure 5 , the SSB includes a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), which occupy one symbol and 127 subcarriers, and the PBCH spans three OFDM symbols and 240 subcarriers.
[0083] The UE monitors the SSB in the time domain and the frequency domain, thereby receiving the SSB.
[0084] SSB can be transmitted up to 64 times within 5ms. Multiple SSBs are transmitted through different transmission beams within 5ms, and the UE performs detection on the assumption that the SSB is transmitted every 20ms based on the specific beam used for transmission. The number of beams that can be used for SSB transmission within 5ms can increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted on a frequency band of 3GHz or lower, and up to 8 SSB beams can be transmitted on a frequency band of 3GHz to 6GHz. In addition, SSB can be transmitted using up to 64 different beams on a frequency band of 6GHz or higher.
[0085] One slot includes two SSBs, and the start symbol and the number of repetitions in the slot are determined according to the subcarrier spacing as follows.
[0086] Unlike SS in a typical LTE system, SSB is not transmitted at the center frequency of the carrier bandwidth. That is, SSB can also be transmitted at a frequency other than the center of the system band, and in the case of supporting wideband operation, multiple SSBs can be transmitted in the frequency domain. Therefore, the UE monitors SSB using a synchronization grid, which is a candidate frequency position for monitoring SSB. The carrier raster and synchronization raster, which are the center frequency position information of the channel for initial connection, are newly defined in NR, and the synchronization raster can support the UE's fast SSB search because its frequency interval is configured to be wider than the frequency interval of the carrier raster.
[0087] The UE can obtain the MIB on the PBCH of the SSB. The MIB (Master Information Block) includes the minimum information for the UE to receive 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 value information, information related to SIB1 CORESET, search space information, PDCCH-related parameter information, etc.), offset information between common resource blocks and SSBs (the position of the absolute SSB in the carrier transmitted via SIB1), and similar information. The SIB1 value information is also applied to some messages used in the random access process so that the UE can access the base station after completing the cell search process. For example, the value information of SIB1 can be applied to at least one of messages 1 to 4 used for the random access process.
[0088] The RMSI mentioned above may mean SIB1 (System Information Block 1), and SIB1 is broadcast periodically (e.g., 160ms) in the cell. SIB1 includes information required for the UE to perform the initial random access process, and SIB1 is periodically transmitted through the PDSCH. In order to receive SIB1, the UE must receive numerical information for SIB1 transmission and CORESET (Control Resource Set) information for scheduling SIB1 through the PBCH. The UE uses the SI-RNTI in the CORESET to identify the scheduling information of SIB1. The UE acquires SIB1 on the PDSCH according to the scheduling information. The remaining SIBs except SIB1 may be transmitted periodically, or the remaining SIBs may be transmitted according to the request of the UE.
[0089] Figure 6 It is a view for explaining a random access procedure in a radio access technology to which the present embodiment is applicable.
[0090] refer to Figure 6 , if the cell search is completed, the UE transmits a random access preamble for random access to the base station. The random access preamble is transmitted via PRACH. Specifically, the random access preamble is periodically transmitted to the base station via PRACH, which includes continuous radio resources in repeated specific time slots. Typically, when the UE makes initial access to a cell, a contention-based random access procedure is performed, and when the UE performs random access for beam failure recovery (BFR), a non-contention-based random access procedure is performed.
[0091] The UE receives a random access response to the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), an UL grant (uplink radio resources), a temporary C-RNTI (temporary cell radio network temporary identifier), and a TAC (time alignment command). Since a random access response may include random access response information for one or more UEs, a random access preamble identifier may be included to indicate the UE for which the included UL grant, temporary C-RNTI, and TAC are valid. The random access preamble identifier may be an identifier of 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 on the PDCCH, i.e., a random access radio network temporary identifier (RA-RNTI).
[0092] Upon receiving a valid random access response, the UE processes the information included in the random access response and performs scheduled transmission to the base station. For example, the UE applies the TAC and stores the temporary C-RNTI. In addition, the UE transmits data stored in the UE's buffer or newly generated data to the base station using the UL grant. In this case, information for identifying the UE must be included in the data.
[0093] Finally, the UE receives a downlink message to resolve the contention.
[0094] <NR CORESET>
[0095] The downlink control channel in NR is transmitted in a CORESET (Control Resource Set) having a length of 1 to 3 symbols, and the downlink control channel transmits uplink / downlink scheduling information, SFI (Slot Format Index), TPC (Transmission Power Control) information, and similar information.
[0096] As mentioned above, NR introduces the concept of CORESET to ensure the flexibility of the system. CORESET (Control Resource Set) refers to the time-frequency resources used for downlink control signals. The UE can use one or more search spaces in the CORESET time-frequency resources to decode control channel candidates. For the purpose of providing information about the characteristics of the simulated beam direction, as well as delay spread, Doppler spread, Doppler shift and average delay (which are characteristics assumed by the existing QCL), the CORESET-specific QCL (quasi-co-location) assumption is configured and used.
[0097] Figure 7 A CORESET is shown.
[0098] refer to Figure 7 , a CORESET can exist in various forms within the carrier bandwidth in a single time slot, and a CORESET can include up to 3 OFDM symbols in the time domain. In addition, in the frequency domain, a CORESET is defined as a multiple of six resource blocks up to the carrier bandwidth.
[0099] The first CORESET, as part of the initial bandwidth portion, is designated (eg, informed, assigned) through the MIB to receive additional configuration information and system information from the network. After establishing a connection with the base station, the UE may receive and configure one or more CORESET information through RRC signaling.
[0100] In this specification, frequency, frame, subframe, resource, resource block, area, 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 meanings used currently or in the past, or may be interpreted as various meanings to be used in the future.
[0101] The present disclosure relates to a method and apparatus for processing packet data for a specific application service such as XR / media in a mobile communication network. For example, the present disclosure introduces a specific technique for dividing and processing a group of packets or packet data units (PDU) sets. In addition, the present disclosure introduces a handover control technique for controlling handover according to the movement of a UE transmitting / receiving packet data for a specific application service.
[0102] Packets for a specific application service may have interdependent properties. For example, packets within a frame may be dependent on each other. An application may require all packets to decode the corresponding frame. The loss of one packet can render the corresponding packet useless despite the successful transmission of other related packets. For example, requirements may be imposed on XR applications in terms of application data units (ADU) / media units instead of individual packets / PDUs. Even packets at different positions of different frame types (I / P frames) or group of pictures (GoP), although they are in the same video stream, may contribute differently to the user experience. Therefore, layered QoS processing in video streams can relax the requirements and lead to higher efficiency.
[0103] If additional information from higher layers / application layers can be utilized by the running services / applications, it would be useful to make it easier to select radio parameters. However, no specific method is provided for UE / base station / core network to effectively identify and handle XR application information traffic characteristics.
[0104] To solve this problem, the present disclosure introduces a configuration method and apparatus for providing packet data processing that considers application information traffic characteristics using information provided from a higher layer / application layer in a wireless network. In addition, the present disclosure also introduces a handover operation for corresponding packet data processing.
[0105] In the present disclosure, the method is described based on 5GS / NR technology. However, the embodiment is not limited to this. 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 information elements and operation contents specified in the NR / 5GS standard (e.g., TS 38.321 as a MAC standard, TS 38.331 as an NR RRC standard, TS23.501 as a 5G system structure standard, TS23.502 as a 5G system process standard, etc.). Although the present disclosure does not include details of UE operations related to the definition of corresponding information elements, the corresponding contents set forth in the standards for known technologies can be incorporated into the present embodiment.
[0106] In addition, in the present disclosure, XR or CG applications are described as examples of applications. However, this is for convenience of description and easy understanding, and there is no limitation, and the present embodiment can be applied to data processing at a specific application level.
[0107] Any function described below is defined as a single UE capability (UE radio capability or UE core network capability), and can be transmitted by the UE to the base station / core network entity (e.g. AMF / SMF) through corresponding signaling. Alternatively, any functions can be combined / merged to be defined as corresponding UE capabilities and transmitted by the UE to the base station / core network entity through corresponding signaling.
[0108] The base station may transmit / indicate information to the UE via an RRC message, the information indicating that the corresponding function / function combination for any function or any function combination described below is allowed / supported / configured. For example, it may be indicated to the UE before or simultaneously with the configuration / application of the corresponding function / function combination. The RRC message may be broadcast via system information. Alternatively, it may be indicated to the UE via a dedicated RRC message.
[0109] For the convenience of description, a unit divided by application / application layer, a unit divided within an application, a unit with correlation between data / streams / packets in one application, a unit with dependency between data / streams / packets in one application, or a unit divided with different information flow characteristics / flows in one flow, a unit divided with different information flow characteristics / flows in one PDU session, a unit divided based on any information / field / metadata included / used / added in the application, or a PDU carrying a payload of a unit information generated at the application level is represented as a PDU set. This is just for the convenience of description. The term 'PDU set' can be replaced with any other term (such as application data unit (ADU), application unit, media unit (MU), application packet data unit, group of pictures (GoP) unit, information flow type (e.g., XR audience gesture information unit, tactile information, video, audio, degree of freedom) specific unit, frame type, stream type, or the like).
[0110] In one aspect, the present disclosure may provide a method for processing an application data stream by a user equipment (UE). The method may include: receiving a higher layer message including radio resource configuration information associated with at least one of auxiliary information and PDU set information for application information traffic characteristics; applying the radio resource configuration information to the UE; and transmitting / receiving user plane data generated in the application layer using the radio resource configuration information. All PDUs in a PDU set are required by the application layer to use 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 (e.g., a frame or video slice of an XRM service), and these PDUs have the same importance requirements 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 region that is spatially divided in a video frame and is encoded by being separated from other regions in the same frame.
[0111] The functions described below can be performed individually and independently. The functions described below can be combined / 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.
[0112] Any information about XR applications described below may be information traffic characteristic information obtained / calculated / derived by UE / network statistics / experience (e.g., any statistics / statistics such as expected value / average value, deviation, standard deviation, etc.). Therefore, any information included in this document may indicate one or more of the average value (expected value) / minimum value / maximum value / standard deviation value. For example, if the information 'update rate' is included, it may mean the average value (expected value) / minimum value / maximum value / standard deviation update rate. This is for convenience of description, and all information in this 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.
[0113] Figure 8 is a view showing an example of a structure for implementing a 5G-XR function in a 5G system.
[0114] For the convenience of description, the embodiments in this disclosure are based on Figure 8 However, the embodiment is not limited thereto. This embodiment can be applied to any system / radio access technology (such as LTE or 6G).
[0115] refer to Figure 8, 5G-XR AF indicates the application function of the 5G-XR service. 5G-XR AS indicates the application server of the 5G-XR service. 5G-XR client indicates the internal function of the UE for the 5G-XR service. In the UE, the XR client may indicate the transceiver of the XR session accessed by the XR application through an API or the like. The XR client may perform communication / signaling with the 5G-XR AF to configure / control / support the XR session (or the delivery of the XR session). The XR client may access the XR data and communicate with the 5G-XR AS to process the corresponding data. 5G-XR AF provides various control functions for processing the XR session on the UE. 5G-XR AF may perform signaling with the PCF / NEF for QoS control. 5G-XR AS indicates the application server that hosts the 5G XR media and media functions.
[0116] Fig. 9 is a flowchart for describing the operation of a source base station according to an embodiment;
[0117] refer to Fig. 9 In a method for controlling handover of a UE transmitting / receiving an application data flow, a source base station may perform a step (S910) of transmitting a handover request message including QoS parameters of a protocol data unit (PDU) set of application data to a target base station.
[0118] A UE transmitting / receiving application data having high dependency between data packets needs to switch base stations according to its movement. Therefore, the source base station determines whether handover of the UE is required.
[0119] When determining that handover of the UE is required, the source base station may transmit a handover request message to the target base station. The handover request message may include QoS parameters of a PDU set of application data transmitted / received by the UE. As an example, the source base station may transmit the QoS parameters of the PDU set to the target base station during the handover preparation step. As another example, the source base station may also transmit the QoS parameters of the PDU set to the target base station in the handover proceeding step.
[0120] In addition, the source base station may transmit PDU set information or DRB information supporting PDU set processing to the target base station, thereby ensuring seamless service during handover of the UE.
[0121] The source base station may perform a step of receiving a handover response message including radio bearer configuration information generated based on the QoS parameters of the PDU set from the target base station ( S920 ).
[0122] For example, the target base station may identify the QoS flow / PDU set and generate radio bearer configuration information satisfying the QoS parameters.
[0123] In addition, the handover response message may also include data forwarding identification information for distinguishing PDU sets. This ensures data forwarding and sequential delivery during the handover.
[0124] The source base station may deliver the received radio bearer configuration information to the UE.
[0125] For example, the radio bearer generated by the target base station may be a DRB configuration mapped to a PDU set.The radio bearer may be transmitted to the UE through the source base station using an RRC container.
[0126] Alternatively, when the target base station is a base station that does not support PDU set processing, the target base station may set up a PDU set resource including the corresponding PDU set or a PDU set resource mapped / associated to the corresponding PDU set. The target base station may transmit a radio resource configuration supporting the PDU set to the source base station via radio bearer configuration information.
[0127] Alternatively, if the target base station is mapped to a DRB other than the DRB mapped to the PDU set of the source base station during handover, the previous DRB (DRB mapped to the PDU set of the source base station) can be configured in the target base station to minimize the loss.
[0128] The source base station may perform a step of controlling forwarding (eg, transferring) forwarding data of (eg, in, between, from) the application data of the UE to the target base station (S930).
[0129] For example, the forwarding data may include PDU set information, where the PDU set information includes at least one of PDU set identification information, a PDU set sequence number, and PDU set importance information.
[0130] The PDU set information may be included in a GPRS tunneling protocol (GTP)-U extension header provided by a protocol for user plane data transmission on an interface between base stations.
[0131] The target base station can also use the PDU set information included in the forwarded data to effectively manage the UE's application data flow for the corresponding PDU set. This is similar to the control operation in which the source base station manages the application data flow, and can also include PDU set related information required for forwarding and managing the application data flow.
[0132] At the same time, if necessary, the target base station can indicate the PDU set support information to the core network control plane node through a path switch request message or a handover request confirmation message. Therefore, the target base station can establish a PDU session for PDU set processing. Alternatively, the target base station can set a configuration for processing forwarded data.
[0133] In addition, the source base station may perform all or some of the various operations described below.
[0134] Fig.10 is a flowchart for describing the operation of a target base station according to an embodiment.
[0135] refer to Fig.10 In a method for controlling handover of a UE transmitting / receiving an application data flow, a target base station may perform a step of receiving a handover request message from a source base station, the handover request message including a QoS parameter of a protocol data unit (PDU) set of application data (S1010).
[0136] A UE transmitting / receiving application data having high dependency between data packets needs to switch base stations according to its movement. Therefore, the source base station determines whether handover of the UE is required.
[0137] When determining that handover of the UE is required, the source base station may transmit a handover request message to the target base station, the handover request message including the QoS parameters of the PDU set of the application data transmitted / received by the UE. As an example, the target base station may receive the QoS parameters of the PDU set to the target base station during the handover preparation step. As another example, the target base station may also receive the QoS parameters of the PDU set from the source base station in the handover proceeding step.
[0138] In addition, the target base station may receive PDU set information or DRB information supporting PDU set processing from the source base station, thereby ensuring seamless service during handover of the UE.
[0139] The target base station may perform a step of generating radio bearer configuration information of the application data based on the QoS parameters of the PDU set ( S1020 ).
[0140] For example, the target base station may identify the QoS flow / PDU set and generate radio bearer configuration information that may satisfy the QoS parameters.
[0141] Alternatively, when the target base station is a base station that does not support PDU set processing, the target base station may set up a PDU set resource including a corresponding PDU set or a PDU set resource mapped / associated to the corresponding PDU set. The target base station may generate radio bearer configuration information for supporting radio resource configuration of the PDU set.
[0142] Alternatively, if the target base station is mapped to a DRB other than the DRB mapped to the PDU set of the source base station during handover, the previous DRB (DRB mapped to the PDU set of the source base station) can be configured in the target base station to minimize the loss.
[0143] The target base station may perform a step of transmitting a handover response message including radio bearer configuration information to the source base station (S1030).
[0144] In addition, the handover response message may also include data forwarding identification information for distinguishing PDU sets. This ensures data forwarding and sequential delivery during the handover. The source base station may deliver the received radio bearer configuration information to the UE.
[0145] For example, the radio bearer generated by the target base station may be a DRB configuration mapped to a PDU set.The radio bearer may be transmitted to the UE through the source base station using an RRC container.
[0146] Alternatively, when the target base station is a base station that does not support PDU set processing, the target base station may set up a PDU set resource including the corresponding PDU set or a PDU set resource mapped / associated to the corresponding PDU set. The target base station may transmit a radio resource configuration supporting the PDU set to the source base station via radio bearer configuration information.
[0147] Alternatively, if the target base station is mapped to a DRB other than the DRB mapped to the PDU set of the source base station during the handover, the previous DRB (the DRB mapped to the PDU set of the source base station) can be configured in the target base station to minimize the loss. Even in this case, the corresponding DRB configuration information can be delivered to the source base station through the handover response message.
[0148] The target base station may perform a step of receiving (eg, in, between, or from) forwarding data of application data of the UE from the source base station (S1040).
[0149] For example, the forwarding data may include PDU set information, where the PDU set information includes at least one of PDU set identification information, a PDU set sequence number, and PDU set importance information.
[0150] The PDU set information may be included in a GPRS Tunneling Protocol (GTP)-U extension header provided by a protocol for user plane data transmission on an interface between base stations.
[0151] The target base station can also use the PDU set information included in the forwarded data to effectively manage the UE's application data flow for the corresponding PDU set. This is similar to the control operation in which the source base station manages the application data flow, and can also include PDU set related information required for forwarding and managing the application data flow.
[0152] At the same time, if necessary, the target base station may indicate the PDU set support information to the core network control plane node through a path switching request message or a handover request confirmation message. After receiving the handover request message, the corresponding indication operation may be performed. For example, the corresponding indication operation may be performed before transmitting the handover response message. Alternatively, the corresponding indication operation may be performed before receiving the forwarded data. Alternatively, the corresponding indication operation may be performed after receiving the forwarded data and before the handover is completed. Alternatively, the corresponding indication operation may be performed before receiving the handover request message. Therefore, the target base station may establish a PDU session for PDU set processing. Alternatively, the target base station may set a configuration for processing forwarded data. Alternatively, the core network entity may identify whether the target base station supports the corresponding PDU set processing.
[0153] In addition, the target base station may perform all or some of the various operations described below.
[0154] Through the above operations, the base station can enhance the dynamic processing performance of various transmission / reception data generated in specific applications. In addition, the base station can handle services such as XR or CG that require accuracy and responsiveness without any problems, and the UE can seamlessly maintain specific application data services even during the handover process.
[0155] In the following, more specific processes and related information will be described in detail for each detailed embodiment. The various embodiments described below may be performed in any combination of all or some of them. In the following description, XR / media application services are presented as examples of specific application services. This is only for the convenience of description, and the embodiments are not limited thereto.
[0156] Supports handover between cells / base stations with PDU set processing
[0157] During the handover preparation step, the source base station may include PDU set related information (e.g., one or more of PDU set ID, PDU set sequence number, PDU set importance / priority, PDU set level 5QI / QCI, and PDU set level QoS parameters / characteristics) in the UE contact and transmit the PDU set related information to the target base station.
[0158] During the handover preparation step, the source base station can ensure data forwarding of data radio bearers supporting PDU set processing.When the target base station uses the same DRB configuration as the source base station, data forwarding and in-order delivery can be guaranteed in the handover.
[0159] If the target base station is mapped to a DRB different from the DRB mapped to the PDU set of the source base station in the handover, the previous DRB (the DRB mapped to the PDU set of the source base station) can be configured in the target cell / base station to minimize the loss. For sequential delivery in the downlink, the target base station can transmit the PDCP-SDU (or SDAP-SDU, referred to as PDCP SDU hereinafter for the convenience of description) forwarded on the previous DRB before delivering the new data from the 5GC on the new DRB. In the uplink, the target base station can avoid transmitting data to the 5GC from the corresponding PDU set on the new DRB until an end marker is received from the UE on the previous DRB.
[0160] During handover execution, the DRB configuration mapped to the PDU set, as determined by the target base station, may be transmitted to the UE via the source base station using an RRC container. When the UE is connected to the target base station, the target base station may inform the SMF that the UE supports PDU set processing. For example, in the case of an Xn handover, this information may be indicated in the Path Switch Request message. As another example, in the case of an NG handover, the corresponding information may be indicated in the Handover Request Confirmation message.
[0161] Handover between a cell / base station that supports PDU set processing and a cell / base station that does not support PDU set processing
[0162] For example, for a PDU session including a PDU set or a PDU session associated with a PDU set, a handover from a base station that supports the PDU set to a base station that does not support the PDU set may be required. In this case, the target base station may set up a PDU session resource including the corresponding PDU set or a PDU session resource mapped / associated to the corresponding PDU set. The target base station may indicate to the UE through the source base station the radio resource configuration that supports the PDU set.
[0163] A PDU session including a PDU set or a PDU session mapped / associated to a PDU set may indicate a PDU session including application / service data information traffic or (multiple) QoS flows supported by the PDU set processing requested by the UE / AF / PCF / SMF. Alternatively, a PDU session including a PDU set or a PDU session mapped / associated to a PDU set may indicate a PDU session for sending signaling to support the PDU set processing requested by the UE / AF / PCF / SMF. Alternatively, a PDU session including a PDU set or a PDU session mapped / associated to a PDU set may indicate a PDU session including information (e.g., (associated) QoS flow identifier, (associated) QoS flow level QoS parameters / features) for providing QoS flow level QoS processing based on a QoS flow (e.g., QFI / 5QI / QCI) QoS flow (supporting (multiple) QoS flows or application / service data information traffic supported by the PDU set processing requested by the UE / AF / PCF / SMF). The corresponding PDU session may include at least one QoS flow, and the at least one QoS flow includes one or more PDU sets.
[0164] Since the above indication information from the target base station lacks PDU set processing support information, according to the relevant technology, the 5G core network can infer that the corresponding application or service data packet delivery should be switched to QoS flow-based information flow delivery or QFI-based tunnel between UPF and base station. For example, the 5G core network can be AMF, SMF or UPF, and the QoS flow can be QFI, 5QI, QoS flow level QoS parameters / characteristics. The indication information can be information used to indicate PDU set processing support on the path switching request message in the case of Xn handover or information used to indicate PDU set processing support on the handover request confirmation message in the case of NG handover. For example, the information used to indicate PDU set processing support can be the above-mentioned PDU set support information.
[0165] If data forwarding is applied, the source base station may infer from the handover (prepare) response message that the target base station does not support the PDU set. For example, the source base station may perform data forwarding using the QFI mapped / associated to the QoS flow of the corresponding PDU set or the QFI of the QoS flow including the corresponding PDU set. In addition, the target base station may configure radio resources for the UE using the corresponding QoS parameters mapped / associated to the QFI of the QoS flow of the corresponding PDU set or the QFI of the QoS flow including the corresponding PDU set in the forwarding packet. As another example, the source base station may have identified that the target base station does not support the PDU set before preparing for the handover.
[0166] After the handover (or during the handover process), the SMF may trigger a switch from information traffic delivery based on PDU sets (e.g., PDU set ID, PDU set level 5QI / QCI, PDU set level QoS parameters / features) (or a tunnel between the UPF and the base station based on PDU set related information) to information traffic delivery based on QoS flows (e.g., QFI, 5QI, QoS flow level QoS parameters / features) (or a tunnel between the UPF and the base station based on QFI / 5QI) through a PDU session modification / establishment process. For example, the SMF may transmit an N4 session modification / establishment request message to the UPF / PSA (PDU session anchor). The SMF may transmit information about the tunnel between the UPF and the base station, the QFI of the QoS flow mapped / associated to the PDU set, or the QFI of the QoS flow including the corresponding PDU set to the UPF. For example, the SMF may include and transmit corresponding downlink forwarding user plane TNL information (e.g., transport layer address, GTP-TEID, and QoS mapping information (DSCP, flow label).
[0167] After packet processing for the corresponding PDU session switch (e.g., QoS flow level), the UPF / PSA may transmit an N4 session modification / establishment response message to the SMF. A PDU session management contact creation response (e.g., Nsmf_PDUSession_CreateSMContext Response) message includes updated core network parameters (e.g., one or more of QoS flow level QoS parameters and uplink core network tunnel information) in the QoS parameters of the accepted (multiple) QoS flows, which is passed to the AMF. The AMF may transmit an N2 path switch request confirmation / response message to the base station.
[0168] As another example, for a PDU session including a PDU set or a PDU session associated with a PDU set, a handover from a base station that does not support PDU sets to a base station that supports PDU sets may be required. In this case, the 5G core network may transmit the corresponding application / service data packet based on the QoS flow (e.g., QFI, 5QI, QoS flow level QoS parameters / characteristics) from the presence of PDU set processing support information from the above-mentioned target base station (e.g., information for indicating PDU set processing support on a path switch request message in the case of Xn handover, or information for indicating PDU set processing support on a handover request confirmation message in the case of NG handover) to the corresponding application / service data packet based on the QoS flow (e.g., QFI, 5QI, QoS flow level QoS parameters / characteristics) (or based on QFI / 5QI). It can be inferred that the tunnel between the UPF and the base station should be switched to information traffic delivery based on PDU sets (e.g., PDU set ID, PDU set level 5QI / QCI, PDU set level QoS parameters / characteristics) (or the tunnel between the base station and the UPF based on PDU set related information).
[0169] After the handover (or during the handover process), the SMF may trigger a switch from information traffic delivery based on QoS flows (e.g., QFI, 5QI, QoS flow-level QoS parameters / features) (or a tunnel between the UPF and the base station based on QFI / 5QI according to conventional techniques) to information traffic delivery based on PDU sets (e.g., PDU set ID, PDU set-level 5QI / QCI, PDU set-level QoS parameters / features) (or a tunnel between the UPF and the base station based on PDU set-related information) through a PDU session modification / establishment process. For example, the SMF may transmit an N4 session modification / establishment request message to the UPF / PSA (PDU Session Anchor). The SMF may transmit information about the tunnel between the UPF and the base station and PDU set-related information to the UPF. For example, it may include corresponding downlink forwarding user plane TNL information (e.g., transport layer address, GTP-TEID, and QoS mapping information (DSCP, flow label). As another example, the PDU set related information may include one or more of a PDU set ID, a PDU set sequence number, a PDU set importance / priority, a PDU set level 5QI / QCI, a PDU set level QoS parameters / characteristics, and a PDU set level packet detection / execution / reporting rule to be applied to the UPF of the corresponding PDU session. As another example, the PDU set related information may be mapped / associated to the QoS mapping information and indicated.
[0170] After switching packet processing for the corresponding PDU session (e.g., PDU set level), the UPF / PSA may transmit an N4 session modification / establishment response message to the SMF. A PDU session management contact creation response (e.g., Nsmf_PDUSession_CreateSMContext Response) message includes updated core network parameters (e.g., one or more of the PDU set level QoS parameters and uplink core network tunnel information) in the QoS parameters of the accepted (multiple) PDU sets, which are passed to the AMF. The AMF may transmit an N2 path switch request confirmation / response message to the base station.
[0171] As another example, for a PDU session that includes a PDU set or for a PDU session associated with a PDU set, mobility from a base station that supports PDU sets to a base station that does not support PDU sets can be provided by switching the DRB mapped to the PDU set (PDU set ID) to the DRB mapped to the QoS flow (QFI) before handover from the source base station, and (thereafter) configuring (multiple) QoS flow (QFI)-based DRBs through a general handover.
[0172] As another example, a UE may be handed over from a source base station to a target base station that does not support PDU sets without prior / previous reconfiguration from DRBs mapped to PDU sets (PDU set IDs) to DRBs mapped to QoS flows (QFIs). In this case, the access stratum (AS) configuration may not be understood by the target base station. This may result in a full configuration of the target base station. For example, the target base station may inform the UE to configure the radio resources through the source base station for full configuration. Full configuration refers to the configuration provided by 5.3.5.11 of 3GPP TS 38.331.
[0173] As another example, if the target base station is mapped to a DRB different from the DRB mapped to the PDU set of the source base station in the handover, the previous DRB (the DRB mapped to the PDU set of the source base station) can be configured in the target cell / base station to minimize the loss. For sequential delivery in the downlink, the target base station can transmit the PDCP-SDU (or SDAP-SDU, referred to as PDCP SDU hereinafter for convenience of description) forwarded on the previous DRB before delivering the new data delivered from the 5GC on the new DRB. In the uplink, the target base station can avoid transmitting data to the 5GC from the corresponding PDU set on the new DRB until it receives an end marker from the UE on the previous DRB.
[0174] Coordination and data forwarding between base stations through the base station interface Xn or the core network interface NG
[0175] Hereinafter, coordination will be described as coordination between base stations via an inter-base station interface Xn. However, this is only for convenience of description. Obviously, coordination between base stations via an NG interface is also included in the scope of the embodiments of the present disclosure.
[0176] For example, the source base station may send an SN STATUS TRANSFER message to the target base station to carry the uplink PDU set SN receiver status and the downlink PDU set SN transmitter status of the DRB mapped to the PDU set.
[0177] As another example, the source base station may send an SN STATUS TRANSFER message to the target base station to carry a receiver status of one or more pieces of information included in uplink PDU set related information about a DRB mapped to the PDU set, and a transmitter status of one or more pieces of information included in downlink PDU set related information. A PDU session information list including a PDU set or a PDU session information list associated with a PDU set may include one or more of information for PDU set level QoS processing (e.g., (multiple) PDU set IDs, PDU set 5QI / QCI, PDU set level QoS parameters / features) and information for providing QoS flow level QoS processing (e.g., (associated) QoS flow identifier, 5QI / QCI, (associated) QoS flow level QoS parameters / features).
[0178] The source base station and the target base station can effectively support PDU set grouping processing by exchanging PDU set related information. As an example, the source base station can transmit the maximum PDCP SN of the packet that has been transmitted to the UE to the target base station. As another example, the base station can include the maximum PDU set SN of the packet / PDU set that has been transmitted to the UE. As another example, the source base station can include the maximum PDU set SN of the PDU set of all packets / PDUs included in the corresponding PDU set that has been transmitted to the UE. As another example, the source base station can transmit one or more PDU set related information of the PDU set of all packets / PDUs included in the corresponding PDU set that has been transmitted to the UE. As another example, the source base station can include information indicating PDU set processing resources in the handover request message and transmit the information to the target base station. As another example, the target base station can include information indicating PDU set processing support in the handover request confirmation message and transmit the information.
[0179] If the HANDOVER REQUEST ACKNOWLEDGE message includes forwarding response information for distinguishing PDU set data, the source base station can be used to forward the corresponding information traffic / data to the target base station using the information. The forwarding response information for distinguishing PDU set data may include transport layer information (TNL) information for establishing a data forwarding tunnel (for distinguishing the PDU set to the target base station). For example, the transport layer information (TNL) for establishing the forwarding tunnel may include the corresponding DRB ID of the corresponding DRB in the target base station (e.g., the DRB ID mapped to the PDU set), downlink forwarding user plane TNL information (e.g., one or more of the transport layer address, GTP-TEID, QoS mapping information (DSCP, flow label), and the oldest PDU set SN / PDCP-SN information. As another example, PDU set related information may be mapped / associated to the QoS mapping information and indicated.
[0180] The source base station may send an SN STATUS TRANSFER message to the target base station to carry the uplink PDCP SN receiver status and downlink PDCP SN transmitter status of the DRB mapped to the PDU set. As another example, the base station may send an SN STATUS TRANSFER message to the target base station to carry the uplink PDU set related information receiver status and the downlink PDU set related information transmitter status of (multiple) SDAP-SDU / PDU mapped to the PDU set. As another example, the source base station may send an SN STATUS TRANSFER message to the target base station to carry the uplink PDU set SN receiver status and downlink PDU set SN transmitter status of the DRB mapped to the PDU set. As another example, the source base station may send an SN STATUS TRANSFER message to the target base station to convey the receiver status of one or more pieces of information included in the uplink PDU set related information of the DRB mapped to the PDU set, and the transmitter status of one or more pieces of information included in the downlink PDU set related information. As another example, the uplink PDU set related information (e.g., one or more pieces of information in any PDU set related information such as PDU set SN) receiver state may include PDU set information of the first lost uplink PDU set (e.g., one or more pieces of 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 pieces of information in any PDU set related information such as PDU set SN) transmitter state may include next PDU set related information (e.g., one or more pieces of information in any PDU set related information such as PDU set SN) of a new PDU set to be allocated by a target base station without a PDU set SN. As another example, the downlink PDU set related information (e.g., one or more pieces of information in any PDU set related information such as PDU set SN) transmitter state may include the minimum PDU set SN that has not yet been transmitted to the UE. As another example, the downlink PDU set related information (e.g., PDU set SN) transmitter state may include the minimum PDU set SN where the UE has not yet transmitted all packets / PDUs belonging to the corresponding PDU set. Therefore, a corresponding SN STAUSTRANSFER message including the status of the PDU set related information may be transmitted.The above functionality may be provided for RLC AM mode or RLC-UM mode supporting PDU set handling.
[0181] The source base station may propose downlink data forwarding for each PDU set configured for a PDU session. In addition, the source base station may provide (multiple) DRB information mapped to (multiple) PDU sets. As another example, the source base station may propose downlink data forwarding for each PDU set configured for a QoS flow of a PDU session. In addition, the source base station may provide information that (multiple) PDU sets are mapped to (multiple) DRBs. As another example, the source base station may propose (downlink) data forwarding to distinguish PDU sets of a PDU session. As another example, the target base station may determine data forwarding for each PDU set configured for a PDU session. As another example, the target base station may determine data forwarding for each PDU set configured for the corresponding QoS flow of the PDU session. As another example, the corresponding information may include information for indicating the proposed downlink forwarding and information for indicating the proposed uplink forwarding for each PDU set ID. As another example, the target base station may determine data forwarding for distinguishing PDU sets. As another example, the target base station may determine to establish a data forwarding tunnel for each PDU session. The target base station can provide information on which QoS flow data forwarding has been accepted and / or which PDU set data forwarding has been accepted, as well as corresponding user plane TNL information, for the data forwarding tunnel established between the source base station and the target base station, and provide the corresponding DRB ID mapped to the PDU set (to the source base station).
[0182] If the PDU set is remapped in the source base station, and / or before preparing for handover, the user packet after the previous source mapping is still being processed, and / or when the source base station provides the data transmission status (e.g., PDCP SN status or PDU set SN status) to the target base station, it has not received the SDAP end marker control PDU of some PDU sets, then the source base station can provide the target base station with the QoS mapping information of the previous side uplink PDU set when the SDAP end marker control PDU is not received. When the UE completes the uplink user data transmission according to the previous source side mapping, the target base station can receive the end marker of such PDU set.
[0183] Before the handover, remapping occurs between PDU sets, or remapping of PDU sets to QoS flows occurs, and / or the SDAP SDU of the corresponding QoS flow / PDU set is transmitted for user data received by the source base station through the remapped DRB QoS flow / PDU set, and / or the source base station may propose an uplink forwarding establishment of a PDU session if the corresponding SDAP end marker control PDU has not been received. As another example, the end marker control PDU of the DRM mapped to the PDU set may be newly defined and indicated.
[0184] If accepted, the target base station may provide corresponding user plane TNL information for the data forwarding tunnel (to the source base station) established between the source base station and the target base station.
[0185] For a DRB downlink forwarding tunnel established for a DRB mapped to a mapped PDU set in the source base station and / or for any PDU set where data forwarding is accepted by the target base station, any new packet of the PDU set may be forwarded to the PDCP SDU via the mapped DRB downlink forwarding tunnel.
[0186] For any PDU set where data forwarding is accepted by the target base station (where a downlink PDU session forwarding tunnel is established), the source base station may forward SDAP SDUs received on the NG-U via the UPF.
[0187] PDU set related information may be added and used on a protocol (e.g., PDU session user plane protocol, NR-U protocol, GTP-U protocol) used to transmit user plane data on an interface between base stations or an interface between a base station and a UPF to support PDU set processing. For example, PDU set related information may be added and used on a GTP-U extension header. As another example, PDU set related information may be added and used on a PDU session container in a GTP-U extension header. As another example, PDU set related information may be added and used on an NR RAN container in a GTP-U extension header. As another example, a PDU type used to indicate DL / UL PDU session information to distinguish a PDU set may be defined differently from a typical downlink PDU type = 0, a typical uplink PDU type = 1 (e.g., downlink PDU type = 2, uplink PDU type = 3). The corresponding PDU type may include one or more pieces of information included in the PDU set related information.
[0188] PDCP status report containing information about the PDU set
[0189] A status report may be defined and provided on any L2 sublayer for status reporting of PDU set related information. In the following, the definition method will be described as defining and using status reporting on PDCP. 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 included in the scope of the embodiments of the present disclosure.
[0190] For a DRB mapped to a PDU set configured by a higher layer (RRC), in order to transmit a PDCP status report to the uplink, the PDCP entity may trigger a PDCP status report including PDU set related information in one or more of the following situations.
[0191] For example, when a higher layer (e.g., RRC) requests reconfiguration of a PDCP entity, when a higher layer requests PDCP data recovery, when a higher layer requests uplink data switching, or when a higher layer indicates a DRB / PDCP entity reconfiguration for mapping a PDU set (e.g., a reconfiguration for indicating PDU set remapping), a PDCP status report including information related to a PDU set may be triggered.
[0192] As another example, corresponding status reports may be applied to AM DRBs and / or UM DRBs.
[0193] If a PDCP status report is triggered, the receiving PDCP entity may compile a PDCP status report.
[0194] The corresponding information may include an uplink PDCP SN / COUNT transmitter state and a downlink PDCP SN / COUNT receiver state of the DRB mapped to the PDU set. As another example, the uplink PDU set related information transmitter state and the downlink PDU set related information receiver state of (multiple) SDAP-SDU / PDU mapped to the PDU set may be included. As another example, the source base station may include an uplink PDU set SN transmitter state and a downlink PDU set SN receiver state mapped to the DRB of the PDU set. As another example, the transmitter state 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 state of one or more pieces of information in the downlink PDU set related information may be included. As another example, the uplink PDU set related information (e.g., one or more pieces of information in any PDU set related information such as the PDU set SN) transmitter state may include the PDU set information of the first lost uplink PDU set (e.g., one or more pieces of information in any PDU set related information such as the PDU set SN). As another example, the downlink PDU set related information (e.g., one or more pieces of information in any PDU set related information such as a PDU set SN) receiver status may include the next PDU set related information (e.g., one or more pieces of information in any PDU set related information such as a PDU set SN) of a PDU set without a PDU set SN. As another example, the downlink PDU set related information (e.g., one or more pieces of information in any PDU set related information such as a PDU set SN) receiver status may include the minimum PDU set SN that the UE has not yet received. As another example, the downlink PDU set related information (e.g., one or more pieces of information in any PDU set related information such as a PDU set SN) receiver status may include the minimum PDU set SN in which the UE has not yet received all packets / PDUs belonging to the corresponding PDU set. As another example, the bitmap field may be configured to not include the first lost PDU set (or PDUs with PDU set related information, or PDU set SN, or PDU set including lost PDCP-SDU / SDAP-SDU), but include the last out-of-sequence PDU set PDU (or PDUs with PDU set related information, or PDU set SN, or PDU set including 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 out-of-sequence PDU set PDU.
[0195] Additional embodiments will be described in various forms below.
[0196] If the base station does not support application session / PDU set processing (e.g., PDU set integrated packet processing), or if the corresponding function is desired to be disabled / deactivated due to base station load, the UE does not need to send unnecessary signaling when the application session / PDU set processing is desired when the UE is within the coverage of the base station. For convenience of description, any function for supporting post-3GPP Rel-18 XR / media services (or any function for differentiated processing of XR applications or any function provided in the present disclosure) is expressed as application session / PDU set processing. This is just for convenience of description and can be replaced by any other terminology.
[0197] For example, the base station may broadcast information indicating whether application session / PDU set processing is supported / possible / enabled / activated through system information. Alternatively, the base station may indicate the corresponding information to the UE through an RRC dedicated message (e.g., RRC reconfiguration). The UE receiving the corresponding information may pass the corresponding information to a higher layer (NAS / application layer). The higher layer may use the corresponding information to perform efficient data processing (e.g., NAS signaling, codec adaptation).
[0198] As another example, a base station that does not support the corresponding function can transmit and receive the corresponding application data by mapping / associating to the QoS parameters (for general PDU sessions) of (multiple) corresponding application sessions / PDU sets. If the base station supports application session / PDU set processing, the base station can use the identifier of (multiple) corresponding application session / PDU sets and / or the QoS parameters of (multiple) corresponding application session / PDU sets to provide the corresponding function (e.g., PDU set integrated packet processing). The base station can use the identification information of (multiple) application session / PDU sets to determine the PDU session associated with the indicated (multiple) application session / PDU set. If the base station supports application session / PDU set processing, the QoS parameters (for general PDU sessions) mapped / linked to (multiple) application sessions / PDU sets may not be used to allocate radio resources. Alternatively, even when the base station supports application session / PDU set processing, the QoS parameters (for general PDU sessions) mapped / associated to (multiple) corresponding application sessions / PDU sets can also be used to allocate radio resources according to the base station state. If the base station does not support application session / PDU set processing, the QoS parameters (for general PDU sessions) mapped / associated to the corresponding application session / PDU set(s) may be used. Alternatively, if the base station does not support application session / PDU set processing, the QoS parameters of the specific QoS flow included in the corresponding PDU session may be used for the corresponding application session / PDU set(s). The corresponding information may be transmitted from the SMF / AMF to the base station.
[0199] The base station may indicate to the UE radio network signaling (e.g., RRC signaling) for (indicating / adding / modifying) radio resource configuration of (multiple) corresponding application sessions / PDU sets. If the base station does not support application session / PDU set processing, the corresponding radio resources may indicate the radio resource configuration to the UE using PDU session resource setting / modification request information (e.g., QFI, QoS flow level QoS parameters) mapped / associated to (multiple) corresponding application sessions / PDU sets.
[0200] As another example, when the base station supports application session / PDU set processing, dedicated QoS flow / QoS parameters (PDU set level PDU set ID, PDU set level QoS parameters) can be provided for the application session / PDU set, which is separate / divided from the PDU set resource setting / modification request information (e.g., QFI, QoS flow level QoS parameters) mapped / associated to (multiple) corresponding application sessions / PDU sets. If the base station supports application session / PDU set processing, dedicated QoS parameters of (multiple) corresponding application sessions / PDU sets can be used to allocate radio resources. If the base station does not support application session / PDU set processing, QoS parameters (for general PDU sessions distinguished from dedicated QoS parameters) mapped / linked to (multiple) corresponding application sessions / PDU sets can be used.
[0201] As another example, a base station supporting application session / PDU set processing may indicate to a core network entity / node (e.g., AMF / SMF) information indicating whether application session / PDU set processing is supported / possible / enabled / activated. The base station may transmit an N2 PDU session response / PDU session modification response to the AMF. If the base station does not support application session / PDU set processing, the corresponding message (e.g., N2 SM response container) may include an acceptance / rejection QoS flow (e.g., (multiple) QFIs) mapped / associated to (multiple) corresponding application sessions / PDU sets. If the base station supports application session / PDU set processing, the corresponding message (e.g., N2SM response container) may include information indicating whether the base station supports / is able to / enable / activate the corresponding application session / PDU set processing. And / or the corresponding message may include acceptance / rejection QoS flows / PDU sets of (multiple) corresponding application sessions / PDU sets. The core network entity / node (e.g., AMF / SMF / dedicated SMF) may be able to distinguish and process them.
[0202] As another example, the source / target base station supporting application session / PDU set processing may indicate information indicating whether application session / PDU set processing is supported / capable / enabled / activated to the target / source base station as a peer and / or to the core network entity / node (e.g., AMF / SMF). For example, it may be included in one or more messages of HANDOVER REQUIRED, HANDOVER REQUEST ACKNOWLEDGE, HANDOVER NOTIFY, PATH SWITCHREQUEST, and PATH SWITCH REQUEST ACKNOWLEDGE transmitted from the base station to the core network entity / node.
[0203] Define the relationship between PDU sessions and PDU sets
[0204] A PDU Session indicates an association between a UE and a data network that provides a PDU connection service. For one UE (or for each UE), one XR / media service may use a single PDU Session.
[0205] For example, a 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 one PDU session. It may be preferred that tactile and / or multimodal data (e.g., audio, video, tactile data associated with a specific time) associated with an application is delivered to the user / UE at a similar time through adjusted processing. A mobile communication system (e.g., UE, base station, or 5GS (e.g., SMF or UPF)) may group and distinguish XR / media application service data flows that support / provide a PDU set (or PDU set capability) for a corresponding PDU session. For example, it may be distinguished by information identifying a corresponding XR / media application service data flow (QoS flow / PDU set) group. Alternatively, for an XR / media application service data flow that supports / provides a PDU set (or PDU set capability), it may be distinguished by information identifying a corresponding PDU set (e.g., a PDU set ID).
[0206] As another example, the UE may configure differently through one PDU session a PDU session that supports an XR / media application service (which supports and provides PDU sets (or PDU set capabilities)) and a PDU session that provides another application service that does not support and provides PDU sets. The service may 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 information for the QoS / flow / PDU set grouping of the corresponding XR / media application service is not separately included, processing that considers PDU set level parameters may be provided / supported for all QoS flows / service data flows included in the corresponding PDU session. In the corresponding process / signaling (e.g., a PDU session setup / modification process between the UE and a core network node (e.g., AMF / SMF)), the corresponding PDU session may be identified through indication information for identifying / identifying / indicating a PDU session that supports / provides a PDU set.
[0207] Different processing of PDU sets in NAS
[0208] In the case of downlink, the UPF (in the case of uplink, the UE) can use one or more pieces of information included in any header (e.g., payload / RTP / SRTP / RTCP / TCP / UDP / IP header) of a corresponding packet / payload / PDU that encapsulates a data packet / payload / application PDU to identify a PDU set. For example, the RTP header may include information such as a sequence number, a timestamp, a marker (M) bit, and the like, and the corresponding information may be used to identify 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 packet. Alternatively, the UPF may use metadata generated by the AS to identify a PDU set. Packet filter information for identifying PDU sets (e.g., PDU set description information through one or more pieces of information included in any header) may be passed by the application function AF (or through the Network Exposure Function (NEF) if one exists) to the corresponding entity / node (e.g., PCF / SMF / PFDF / UDM).
[0209] In the case of downlink, the UPF (in the case of uplink, the UE) can add PDU set related information to the corresponding PDU and transmit 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 transmit data to the UPF using the received corresponding information. The PDU set related information transmitted by the UPF / UE to the base station may include one or more of the following information.
[0210] -PDU set identifier: information used to identify a PDU set
[0211] -PDU set sequence number / tag
[0212] -PDU set size: information used to identify / indicate the last SDU / PDU of a PDU set
[0213] - Information used to indicate that it is the last PDU in a PDU set
[0214] -PDU set importance / priority indication information: information used to indicate the importance / priority value of the corresponding PDU set
[0215] The above one or more pieces of 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 pieces of information may be included in the last PDU of the corresponding PDU set. Alternatively, the above one or more pieces of information may be included in all PDUs of the corresponding PDU set. As an example, a PDU set can be identified by setting / adding the same PDU sequence number to all packets belonging to the corresponding PDU set. As another example, a PDU set can be identified by setting / adding information indicating that the last packet belonging to the corresponding PDU set is the last PDU in the corresponding PDU set.
[0216] The above one or more pieces of information (PDU set related information) can be identified by marking any field on the GTP-U extended header in the base station / UPF.
[0217] 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) and increase by 1, and if the maximum value is reached by modulo / modulo operation, it may be set to cycle. For example, when the corresponding n has 2 bits, it may have 4 values 0, 1, 2, and 3, and may be cycled to 0, 1, 2, 3, 0, 1, 2, 3, 0, 1, 2, 3, ... by modulo 4 operation.
[0218] A UE capable of PDU set processing 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 it. Alternatively, the corresponding UE may receive rules / policies for PDU set processing for a PDU session supporting PDU set processing during a PDU session setup / 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 for a QoS flow / PDU set associated with the corresponding QoS rules.
[0219] The UE may process uplink data using the received QoS rules and PDU set level QoS parameters of the PDU set. The PDU set level QoS parameters may include QoS features at the PDU set level (one or more of PDU set level resource type (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 the PDU set level QoS characteristics. The base station may receive QoS rules and PDU set level QoS parameters for the corresponding PDU set from a core network node (e.g., AMF / SMF) on a related NAS processor.
[0220] DRB mapping of QoS flows and PDU sets in the SDAP sublayer
[0221] 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 downlink support the mapping between a QoS flow and a DRB. The QoS flow ID (QFI) is marked on the SDAP header of the uplink and downlink.
[0222] In order to support PDU set level QoS processing for (XR / media) applications, enhancements to SDAP (or PDCP Higher Adaptation Protocol) functionality may be required.
[0223] For example, a PDU set may be mapped to a DRB and processed. Information for identifying a PDU set (e.g., a PDU set ID) may be marked / included in the SDAP header for uplink and downlink. The base station may transmit the corresponding PDU session identification information and (multiple) PDU set information to be added / released on the SDAP configuration information (sdap-config) via an RRC message.
[0224] Fig.11 2 is a view exemplarily showing a PDU session resource setting request transfer information element according to an embodiment. Fig.12 : is a view exemplarily showing a PDU session resource modification request delivery information element according to an embodiment.
[0225] refer to Fig.11 and Fig.12 , the PDU set setting / addition / modification information included in the PDU session resource setting / modification request message included in the NGAP interface between the core network node (e.g., AMF / SMF) and the base station may be used independently of the QoS flow setting / addition / modification information. Fig.11 and Fig.12 As shown, the PDU set setting / addition / modification information included in the PDU session resource setting / modification request message included 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.
[0226] Fig.13 is a view exemplarily showing SDAP configuration information elements according to an embodiment.
[0227] refer to Fig.13 As another example, the SDAP configuration information (sdap-config) included in the RRC message may indicate information of a QFI list for uplink QoS flows indicating a PDU session to be additionally mapped to a DRB, independent of information of a PDU set ID list for uplink PDU sets indicating a PDU session to be additionally mapped to a DRB. Alternatively, as Fig.13As shown, the SDAP configuration information (sdap-config) included in the RRC message may indicate information of a QFI list for an uplink QoS flow indicating a PDU session to be additionally mapped to the corresponding DRB, as a parameter of a level equal to information of a PDU set ID list for an uplink PDU set indicating a PDU session to be additionally mapped to the DRB. The corresponding DRB may be mapped / associated by sharing (multiple) QoS flows and / or (multiple) PDU sets. Alternatively, the corresponding DRB may be specifically mapped / associated to (multiple) QoS flows or (multiple) PDU sets. According to (multiple) QoS flows and / or (multiple) PDU sets, a corresponding uplink / downlink SDAP header may be applied, including a QoS flow ID and / or a PDU set ID.
[0228] Fig.14 2 is a diagram exemplarily illustrating a PDU session resource setting request delivery information element according to another embodiment. Fig.15 Schematic diagram of a PDU session resource modification request transmission information element according to another embodiment.
[0229] refer to Fig.14 and Fig.15 , the PDU set setting / addition / modification information included in the PDU session resource setting / modification request message included in the NGAP interface between the core network node (e.g., AMF / SMF) and the base station can be used as a lower level parameter of the QoS flow setting / addition / modification information.
[0230] Fig.16 is a view exemplarily showing SDAP configuration information elements according to another embodiment.
[0231] refer to 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 to be additionally mapped to the PDU session of the corresponding DRB may be indicated as a lower-level parameter to the information indicating the QFI of the uplink QoS flow of the PDU session to be additionally mapped to the DRB. Depending on (multiple) QoS flows and / or (multiple) PDU sets, the corresponding uplink / downlink SDAP header may be applied, including the QoS flow ID and / or the PDU set ID.
[0232] As 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 a default DRB. Otherwise, the (multiple) PDUs / SDAP-SDUs 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.
[0233] As another example, for a PDU set, the corresponding SDAP SDU may not be mapped to a default DRB. The (multiple) PDUs / SDAP-SDUs belonging to a PDU set may be mapped to corresponding DRBs according to a PDU set to DRB mapping rule that always maps the indicated / configured / stored PDU set to a DRB.
[0234] As another example, if there is no indicated / configured / stored DRB mapping rule for the corresponding PDU set,
[0235] >>If there is a QoS flow to DRB mapping rule indicated / configured / stored for the QoS flow to which the corresponding PDU set belongs, then the (multiple) PDUs / SDAP-SDUs belonging to the corresponding PDU set can be mapped to the corresponding DRB according to the PDU set to DRB mapping rule that maps the indicated / configured / stored QoS flow to DRB.
[0236] >> Otherwise (or if there is no QoS flow to DRB mapping rule indicated / configured / stored for the QoS flow to which the corresponding PDU set belongs)
[0237] >>>The corresponding PDU set (PDU(s) / SDAP-SDU(s) belonging to the corresponding PDU set) may be mapped to a default DRB.
[0238] >>>This may be indicated by higher layers (e.g., RRC / NAS). The higher layers of the UE may indicate this to the base station / core network node (e.g., AMF / SMF) via signaling (RRC / NAS signaling).
[0239] As another example, the default DRB indication information (defaultDRB) indicates information used to indicate whether it is the default DRB for the PDU session in all configuration instances of SDAP having the same value (e.g., PDU-SessionID) 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 a default DRB. Therefore, a DRB configured / indicated for a (specific) (multiple) PDU set may not be used as a default DRB. As another example, a default DRB may be used in a DRB mapped to a QoS flow (mapping to a QoS flow).
[0240] As 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 above-mentioned default DRB indication information (defaultDRB).
[0241] Different processing of PDU sets in SDAP sublayer
[0242] When one or more PDU sets are mapped to a DRB and processed, a method for processing them differently on SDAP can be provided to support different processing for each PDU set (e.g., for each PDU set ID, for each PDU set sequence number with the same PDU set ID, or for each PDU set importance / priority with the same PDU set ID) in any L2 sublayer (e.g., SDAP / PDCP / RLC / MAC).
[0243] For the convenience of description, the following describes a method for processing PDU sets differently in the SDAP sublayer. However, this is only for the convenience of description, and it is obvious that applying the same method as the SDAP sublayer in the PDCP / RLC / MAC sublayer is also included in the scope of the present invention.
[0244] Fig.17 is a view showing a DL SDAP data PDU format with an SDAP header according to an embodiment. Fig.18 is a view showing a UL SDAP data PDU format with an SDAP header according to an embodiment.
[0245] Fig.17 and Fig.18 The SDAP data PDU format in the related art is shown.
[0246] For example, an uplink / downlink SDAP data PDU can be constructed by including the above-mentioned PDU set related information (e.g., a PDU set identifier, a PDU set sequence number, a 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) in the SDAP header.
[0247] For example, in order to use an 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 (in the SDAP configuration information) indicating the use / application / existence of the uplink / downlink SDAP header supporting the PDU set through RRC signaling, and indicate it to the UE. According to the prior art, the corresponding information can indicate the use of the corresponding SDAP header by identifying the information used to indicate whether there is an SDAP header (sdap-HeaderUL / sdap-HeaderDL) for uplink / downlink data on the DRB.
[0248] As another example, the use of an SDAP header supporting a PDU set may be indicated by information indicating a dedicated PDU session or a dedicated SDAP-ConFIG that supports the PDU set. According to the related art, the use of the corresponding SDAP header may be indicated by information indicating whether there is an SDAP header (sdap-HeaderUL / sdap-HeaderDL) for uplink / downlink data on the DRB. Alternatively, according to the prior art, the use of the corresponding SDAP header may be indicated by information discerned from information indicating whether there is an SDAP header (sdap-HeaderUL / sdap-HeaderDL) for uplink or downlink data on the corresponding DRB.
[0249] As another example, an SDAP entity for a PDU session supporting a PDU set may be further configured / set. For example, an SDAP entity for a (multiple) QoS flow included in a corresponding PDU session and an SDAP entity for a (multiple) PDU set included in a corresponding PDU session may be configured / set differently. Alternatively, a dedicated SDAP entity for a PDU set included in a corresponding PDU session may be configured / set.
[0250] As another example, for a UE that supports PDU sets and / or when the base station receives a PDU set processing request from a UE / core network node (e.g., AMF / SMF), the base station may use the above-mentioned PDU set related information (e.g., a PDU set identifier, a PDU set sequence number, a PDU set size, information for identifying that it is the last PDU in 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.
[0251] As another example, sets of PDUs may be handled differently by SDAP Control PDUs.
[0252] For example, in order to indicate / notify the use / termination of use / switching / presence / non-existence of an SDAP header including one or more pieces of information in the PDU set related information from the related technology, the base station may send SDAP control PDU signaling to the UE. As 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 pieces of information in the PDU set related information identified from the related technology, the base station may send corresponding L2 control PDU / MAC-CE signaling to the UE. The control PDU / MAC-CE may include one or more pieces of information in the above-mentioned PDU set related information. The control PDU / MAC-CE may include indication information for identifying one or more pieces of information in the header use / start of use / termination of use / switching / presence / non-existence.
[0253] As another example, a PDU set may be mapped to a DRB and used by controlling the PDU through an end marker. When the RRC configures a rule for mapping an uplink PDU set to a DRB, the SDAP entity may operate as follows.
[0254] >If one or more of the following conditions are met, one or more of the following operations can be performed.
[0255] Relevant conditions: SDAP is configured, there is no rule mapping the PDU set stored for the corresponding PDU set to a DRB, the default DRB for the corresponding PDU set or the default DRB for a QoS flow belonging to the configured corresponding PDU set, and the last PDU / SDAP-SDU identified / detected in the corresponding PDU set.
[0256] >>According to the prior art (TS.37.324 6.2.3), construct the above control PDU or end marker control PDU for the corresponding PDU set.
[0257] >>Map the corresponding end marker control PDU or the above control PDU to the default DRB of the corresponding PDU set or the default DRB of the QoS flow belonging to the corresponding PDU set.
[0258] >>Submit the corresponding end marker control PDU or the above control PDU to the lower layer.
[0259] >If one or more of the following conditions are met, one or more of the following operations can be performed.
[0260] Relevant conditions: The rule for mapping the PDU set stored for the corresponding PDU set to the DRB is different from the rule for mapping the PDU set configured for the corresponding PDU set to the DRB, the rule for mapping the PDU set stored for the corresponding PDU set to the DR is configured by RRC, and the last PDU / SDAP-SDU is identified / detected in the corresponding PDU set.
[0261] >>According to the prior art (TS.37.324 6.2.3), construct the above control PDU or end marker control PDU for the corresponding PDU set.
[0262] >> According to the rules for mapping the stored PDU set of the corresponding PDU set to the DRB, the corresponding end marker control PDU or the above control PDU is mapped to the DRB.
[0263] >>Submit the corresponding end marker control PDU or the above control PDU to the lower layer.
[0264] As another example, by including a PDU set ID in the QFI / field on the end marker control PDU, it can be indicated to stop 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.
[0265] As another example, by including a PDU set ID in the QFI / field on the end marker control PDU, it can be indicated to stop SDAP SDU mapping of the QoS flow including the corresponding PDU set using the PDU set ID included in the corresponding end marker control PDU on the DRB (where the corresponding end marker control PDU is transmitted).
[0266] Different processing of PDU sets in the PDCP sublayer
[0267] When one or more PDU sets are mapped to a DRB and processed, a method for processing them differently 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).
[0268] For example, the PDCP entity may discard all / remaining PDCP SDUs (or PDUs) included in the corresponding PDU set at the PDU set level.
[0269] For example, the base station may configure a discard timer for a specific PDU set in the UE through RRC signaling. According to the related art (TS 38.323 5.3), the corresponding discard timer may be based on the discardTimer used to discard a PDCP SDU.
[0270] As another example, when the discard timer of a PDCP SDU according to the related art or the discard timer of the above-mentioned PDU set expires, the transmitting PDCP entity may discard the PDCP SDU together with the corresponding PDCP data PDU. The transmitting PDCP entity may discard (multiple) PDCP SDUs together with (multiple) all / remaining / all non-discarded / remaining non-discarded PDCP data PDUs included in the PDU set (in which the corresponding PDCP SDU is associated / mapped / included). The (multiple) PDCP SDUs may be (multiple) PDCP data PDUs / PDCP-SDUs, which together with (multiple) all / remaining / all non-discarded / remaining non-discarded PDCP data PDUs included in the above-mentioned PDU set are equal in terms of one or more PDU set related information (e.g., PDU set ID, PDU set sequence number, PDU set importance / priority).
[0271] As another example, if the discard timer of one PDCP SDU according to the related art or the discard timer of one PDU set described above expires, the transmitting PDCP entity may indicate the expiration of the discard timer to the lower layer. The RLC entity receiving 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 (which are included in the PDU set in which the corresponding PDCP / RLC SDU is associated / mapped / included).
[0272] As another example, when successful delivery of a corresponding PDUP SDU or PDU set is identified through a PDCP status report according to the related art or through a status report that discriminates a PDU set, the transmitting PDCP entity may discard the PDCP SDU together with the corresponding PDCP data PDU. The transmitting PDCP entity may discard (multiple) PDCP SDUs together with (multiple) all / remaining / all non-discarded / remaining non-discarded PDCP data PDUs included in the PDU set (in which the corresponding PDCP SDU is associated / mapped / included). The (multiple) PDCP SDUs may be (multiple) PDCP data PDUs / PDCP-SDUs that are equal to (multiple) all / remaining / all non-discarded / remaining non-discarded PDCP data PDUs included in the above-mentioned PDU set in terms of one or more PDU set related information (e.g., PDU set ID, PDU set sequence number, PDU set importance / priority).
[0273] As another example, the base station may receive auxiliary information for configuring radio parameters for PDU set processing from the UE via RRC signaling or from a core network node (e.g., AMF / SMF) on a related NAS processor via NGAP signaling. 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 for indicating the upper / lower limit / constraint required until all 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 the discard timer in the UE.
[0274] Different processing of PDU sets in L2 sublayer
[0275] When one or more PDU sets are mapped to a DRB and processed, a method for processing them differently in the corresponding L2 sublayer 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).
[0276] For example, one or more RLC entities may be associated with the above PDU set related information to provide different processing for each PDU set.
[0277] For example, for a 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 entities, where N is 1, 2, 3, ...)
[0278] As another example, for a data radio bearer mapped to a PDU set, each PDCP entity may be associated with one or more AM RLC entities. (e.g., 1xN AM RLC entities, where N is 1, 2, 3, ...)
[0279] As another example, the number (N) of corresponding UM / AM RLC entities may be associated with the above-mentioned PDU set identifier and / or PDU set sequence number. 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 may be N=2*n. For example, when the corresponding information has 2 bits, there may be 4 RLC entities. The base station may indicate to the UE, through RRC signaling, information for associating the PDU set identifier or PDU set sequence number to the corresponding RLC entity. Alternatively, the (multiple) PDU set SDU / PDUs associated with the corresponding PDU set identifier or PDU set sequence number may be associated with the corresponding RLC entity through a modulo operation. The transmitting PDCP entity may submit the PDCP PDU belonging to the corresponding PDU set to the associated RLC entity.
[0280] As another example, the number (N) of corresponding UM / AM RLC entities may be associated with the number of (multiple) PDU sets having different PDU set importance / priority values, which are associated with (multiple) PDU sets to be transmitted via the corresponding radio bearer. For example, if (multiple) PDU set SDUs / PDUs having two PDU set importances / priorities are transmitted via the corresponding radio bearer, the number of corresponding radio bearers may be 2. The base station may indicate information for associating the PDU set importance / priority to the corresponding RLC entity to the UE via RRC signaling. The transmitting PDCP entity may submit the PDCP PDUs belonging to the corresponding PDU set to the associated RLC entity.
[0281] As another example, the configuration of the logical channel carried by the RLC of 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, a parameter associated with the importance / priority of the PDU set may be included. Through this, the MAC layer can use the corresponding information in the logical channel priority handler or data transmission / retransmission to process the data.
[0282] As another example, an RLC entity may include one or more of the above PDU set related information in the RLC header and provide different processing for each PDU set. This can be applied by exchanging SDAP with RLC in the previous embodiment.
[0283] As another example, the configuration of the logical channel carried by the RLC of the RLC entity may include parameters associated with one or more of the above-mentioned PDU set related information. For example, a parameter associated with the importance / priority of the PDU set may be included. Through this, the MAC layer can use the corresponding information in the logical channel priority processor or data transmission / retransmission to process the data.
[0284] Activation / deactivation / switching / fallback of PDU set processing
[0285] 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 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 the L2 sublayer (e.g., SDAP / PDCP / RLC / MAC). This may be a load / burden on each sublayer. Therefore, the UE or base station may need to operate by defining L2 signaling for informing activation / deactivation of corresponding functions. For example, one or more of the SDAP control PDU, PDCP control PDU, RLC control PDU, and MAC control elements can be used to inform the activation / deactivation / switching / fallback of the PDU set processing of the corresponding radio bearer on each sublayer. The sublayer receiving the corresponding signaling can pass the corresponding information to another sublayer (a higher sublayer or a lower sublayer), where the corresponding function operates. The corresponding sublayer can perform the corresponding operation.
[0286] According to the above-described embodiments, by utilizing the unit of information / field generated in the service / application operated from a higher layer, packet data can be effectively processed based on information traffic characteristics in a wireless network. Hereinafter, a UE and a base station capable of executing the above-described embodiments will be briefly described. Embodiments not described below may also be executed by the UE and the base station based on the above-described operations.
[0287] Fig.19 is a block diagram illustrating a source base station according to another embodiment.
[0288] refer to Fig.19, a source base station for controlling the handover of a UE that transmits and receives an application data stream may include a transmitter 1920 for transmitting a handover request message including QoS parameters of a protocol data unit (PDU) set of application data to a target base station; a receiver 1930 for receiving a handover response message including radio bearer configuration information generated based on the QoS parameters of the PDU set from the target base station, and a controller 1910 for controlling forwarding data of the UE's application data to the target base station (for example, controlling the delivery of forwarding data in the UE's application data to the target base station, or controlling the forwarding of data to be forwarded from the UE's application data or among the UE's application data to the target base station).
[0289] A UE transmitting / receiving application data having high dependency between data packets needs to switch base stations according to its movement. Therefore, the controller 1910 determines whether handover of the UE is required.
[0290] When determining that the handover of the UE is required, the transmitter 1920 may transmit a handover request message to the target base station. The handover request message may include QoS parameters of a PDU set of application data transmitted / received by the UE. For example, the transmitter 1920 may transmit the QoS parameters of the PDU set to the target base station during the handover preparation step. As another example, the transmitter 1920 may also transmit the QoS parameters of the PDU set to the target base station in the handover proceeding step.
[0291] In addition, the source base station may transmit PDU set information or DRB information supporting PDU set processing to the target base station, thereby supporting seamless service during handover of the UE.
[0292] At the same time, the target base station can identify the QoS flow / PDU set and generate radio bearer configuration information that meets the QoS parameters.
[0293] In addition, the handover response message may also include data forwarding identification information for identifying a PDU set. This ensures data forwarding and sequential delivery during the handover.
[0294] The transmitter 1920 may deliver the received radio bearer configuration information to the UE.
[0295] For example, the radio bearer generated by the target base station may be a DRB configuration mapped to a PDU set. The generated radio bearer may be transmitted to the UE through the source base station using an RRC container.
[0296] Alternatively, when the target base station is a base station that does not support PDU set processing, the target base station may set up a PDU set resource including the corresponding PDU set or a PDU set resource mapped / associated to the corresponding PDU set. The target base station may transmit a radio resource configuration supporting the PDU set to the source base station via radio bearer configuration information.
[0297] Alternatively, if the target base station is mapped to a DRB other than the DRB mapped to the PDU set of the source base station during handover, the previous DRB (DRB mapped to the PDU set of the source base station) can be configured in the target base station to minimize the loss.
[0298] Meanwhile, the forwarding data may include PDU set information, where the PDU set information includes at least one of PDU set identification information, a PDU set sequence number, and PDU set importance information.
[0299] The PDU set information may be included in a GPRS Tunneling Protocol (GTP)-U extension header provided by a protocol for user plane data transmission on an interface between base stations.
[0300] The target base station can also use the PDU set information included in the forwarded data to effectively manage the UE's application data flow for the corresponding PDU set. This is similar to the control operation in which the source base station manages the application data flow, and can also include PDU set related information required for forwarding and managing the application data flow.
[0301] At the same time, if necessary, the target base station can indicate the PDU set support information to the core network control plane node through a path switch request message or a handover request confirmation message. Therefore, the target base station can establish a PDU session for PDU set processing. Alternatively, the target base station can set a configuration for processing forwarded data.
[0302] In addition, the controller 1910 controls the overall operation of the source base station 1900 according to control for providing packet processing based on information generated in an application layer required to perform the above disclosure.
[0303] The transmitter 1920 and the receiver 1930 are used to transmit or receive signals, messages or data required to perform the above disclosure with the UE, the target base station or the core network entity.
[0304] Fig. 20 is a block diagram illustrating a target base station according to an embodiment.
[0305] refer to Fig. 20, a target base station 2000 for controlling the handover of a UE that receives and transmits an application data stream may include a receiver 2030 that receives a handover request message including QoS parameters of a protocol data unit (PDU) set of application data from a source base station; a controller 2010 that generates radio bearer configuration information of the application data based on the QoS parameters of the PDU set and a transmitter 2020 that transmits a handover response message including the radio bearer configuration message to the source base station, wherein the receiver 2030 also receives forwarding data of the UE's application data (e.g., data among or forwarded from the UE's application data) from the source base station.
[0306] A UE transmitting / receiving application data having high dependency between data packets needs to switch base stations according to its movement. Therefore, the source base station determines whether handover of the UE is required.
[0307] When determining that the handover of the UE is required, the source base station may transmit a handover request message to the target base station. The handover request message may include QoS parameters of a PDU set of application data transmitted / received by the UE. As an example, the receiver 2030 may receive QoS parameters of a PDU set to the target base station during the handover preparation step. As another example, the receiver 2030 may also receive QoS parameters of a PDU set from the source base station in the handover proceeding step.
[0308] In addition, the receiver 2030 may receive PDU set information or DRB information supporting PDU set processing from the source base station, thereby supporting seamless service during handover of the UE.
[0309] The controller 2010 may identify a QoS flow / PDU set and generate radio bearer configuration information that may satisfy the QoS parameters.
[0310] Alternatively, when the target base station is a base station that does not support PDU set processing, the controller 2010 may set up a PDU set resource including a corresponding PDU set or a PDU set resource mapped / associated to a corresponding PDU set. The controller 2010 may generate radio bearer configuration information for supporting radio resource configuration of a PDU set.
[0311] Alternatively, if the target base station is mapped to a DRB other than the DRB mapped to the PDU set of the source base station during handover, the previous DRB (DRB mapped to the PDU set of the source base station) can be configured in the target base station to minimize the loss.
[0312] In addition, the handover response message may also include data forwarding identification information for identifying a PDU set. This can ensure data forwarding and sequential delivery during the handover. The source base station may deliver the received radio bearer configuration information to the UE.
[0313] For example, the radio bearer generated by the target base station may be a DRB configuration mapped to a PDU set, and it may be transmitted to the UE through the source base station using an RRC container.
[0314] Alternatively, when the target base station is a base station that does not support PDU set processing, the control 2010 can set up a PDU set resource including a corresponding PDU set or a PDU set resource mapped / associated to a corresponding PDU set. The transmitter 2020 can transmit a radio resource configuration supporting a PDU set to the source base station through radio bearer configuration information.
[0315] Alternatively, if the target base station is mapped to a DRB other than the DRB mapped to the PDU set of the source base station during the handover, the previous DRB (the DRB mapped to the PDU set of the source base station) can be configured in the target base station to minimize the loss. Even in this case, the corresponding DRB configuration information can be delivered to the source base station through the handover response message.
[0316] For example, the forwarded data may include PDU set information, the PDU set information including at least one of PDU set identification information, PDU set sequence number, and PDU set importance information. The PDU set information may be included in a GPRS Tunneling Protocol (GTP)-U extension header provided by a protocol for user plane data transmission on an interface between base stations.
[0317] The target base station can also use the PDU set information included in the forwarded data to effectively manage the UE's application data flow for the corresponding PDU set. This is similar to the control operation in which the source base station manages the application data flow, and can also include PDU set related information required for forwarding and managing the application data flow.
[0318] At the same time, if necessary, the transmitter 2020 may indicate the PDU set support information to the core network control plane node through a path switching request message or a handover request confirmation message. After receiving the handover request message, the corresponding indication operation may be performed. For example, the corresponding indication operation may be performed before transmitting the handover response message. Alternatively, the corresponding indication operation may be performed before receiving the forwarded data. Alternatively, the corresponding indication operation may be performed after receiving the forwarded data and before the handover is completed. Alternatively, the corresponding indication operation may be performed before receiving the handover request message. Therefore, the controller 2010 may establish a PDU session for PDU set processing. Alternatively, the controller 2010 may set a configuration for processing forwarded data. Alternatively, the core network entity may identify whether the target base station supports the corresponding PDU set processing.
[0319] In addition, the controller 2010 controls the overall operation of the target base station 2000 according to control for providing packet processing based on information generated in an application layer required to perform the above disclosure.
[0320] The transmitter 2020 and the receiver 2030 are used to transmit or receive signals, messages or data required to perform the above disclosure with the UE, the source base station or the core network entity.
[0321] The above-mentioned embodiment may be supported by a standard document disclosed in at least one of the radio access systems such as IEEE 802, 3GPP and 3GPP2. That is, the steps, configurations and parts not described in the present embodiment may be supported by the standard documents mentioned above to clarify the technical concept of the present disclosure. In addition, all terms disclosed herein may be described by the standard documents set forth above.
[0322] The above embodiments may be implemented in any of various ways. For example, the embodiments may be implemented as hardware, firmware, software or a combination thereof.
[0323] In the case of hardware implementation, the method according to the present embodiment may 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.
[0324] In the case of implementation by firmware or software, the method according to the present embodiment can be implemented in the form of a device, process or function for performing the above-mentioned 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 any of various well-known ways.
[0325] In addition, the terms "system", "processor", "controller", "component", "module", "interface", "model", "unit" and the like may generally refer to computer-related entity hardware, a combination of hardware and software, software, or running software. For example, the above-mentioned components may be, but are not limited to, processes driven by a processor, processors, controllers, control processors, entities, execution threads, programs and / or computers. For example, both an application running in a controller or processor and the controller or processor may be a component. One or more components may be provided in a process and / or execution thread, and a component may be provided in a single device (e.g., a system, a computing device, etc.), or may be distributed across two or more devices.
[0326] The above-mentioned embodiments of the present disclosure are described only for illustrative purposes, and those skilled in the art will understand that various modifications and changes may be made thereto without departing from the scope and spirit of the present disclosure. In addition, the embodiments of the present disclosure are not intended to be limiting, but are intended to illustrate the technical ideas of the present disclosure, and therefore the scope of the technical ideas of the present disclosure is not limited by these embodiments. The scope of the present disclosure should be interpreted on the basis of the attached claims in such a manner that all technical ideas included in the scope equivalent to the claims belong to the present disclosure.
[0327] CROSS-REFERENCE TO RELATED APPLICATIONS
[0328] This application claims priority under Section 119(a) of the United States Patent Act (35 U.S.C. 119(a)) to U.S. Patent Application No. 10-2022-0053098, filed on April 28, 2022, and U.S. Patent Application No. 10-2023-0050138, filed on April 17, 2023, which are hereby incorporated by reference. This application also claims priority in other countries outside the United States for the same reasons as above, and the disclosures thereof are incorporated herein by reference in their entirety.
Claims
1. A method for controlling, by a source base station, handover of a UE transmitting / receiving an application data flow, the method comprising: transmitting a handover request message including QoS parameters of a set of protocol data units (PDUs) of application data to a target base station; receiving, from the target base station, a handover response message including radio bearer configuration information generated based on the QoS parameters of the PDU set; and Control to forward the forwarding data of the application data of the UE to the target base station.
2. The method according to claim 1, wherein: The handover response message also includes data forwarding indication information used to distinguish the PDU sets.
3. The method according to claim 1, wherein: The forwarding data includes PDU set information, and the PDU set information includes at least one of PDU set identification information, a PDU set sequence number, and PDU set importance information.
4. The method according to claim 3, wherein: The PDU set information is included in a GPRS Tunneling Protocol (GTP)-U extension header provided by a protocol for user plane data transmission on an interface between base stations.
5. The method according to claim 1, wherein: The target base station indicates the PDU set support information to the core network control plane node through a path switch request message or a handover request confirmation message.
6. A method for controlling, by a target base station, handover of a UE transmitting / receiving an application data flow, the method comprising: receiving a handover request message including QoS parameters of a set of protocol data units (PDUs) of application data from a source base station; generating radio bearer configuration information for the application data based on the QoS parameters of the PDU set; transmitting a handover response message including the radio bearer configuration information to the source base station; and Receive forwarding data of application data of the UE from the source base station.
7. The method according to claim 6, wherein: The handover response message also includes data forwarding indication information used to distinguish the PDU sets.
8. The method according to claim 6, wherein: The forwarding data includes PDU set information, and the PDU set information includes at least one of PDU set identification information, a PDU set sequence number, and PDU set importance information.
9. The method according to claim 8, wherein: The PDU set information is included in a GPRS Tunneling Protocol (GTP)-U extension header provided by a protocol for user plane data transmission on an interface between base stations.
10. The method according to claim 6, further comprising: After receiving the handover request message, the PDU set support information is indicated to the core network control plane node through a path switch request message or a handover request confirmation message.
11. A source base station for controlling handover of a UE transmitting / receiving an application data flow, comprising: a transmitter that transmits a handover request message including QoS parameters of a set of protocol data units (PDUs) of application data to a target base station; a receiver, the receiver receiving, from the target base station, a handover response message including radio bearer configuration information generated based on the QoS parameters of the PDU set; as well as A controller controls forwarding data of application data of the UE to the target base station.
12. The source base station according to claim 11, wherein: The handover response message also includes data forwarding indication information used to distinguish the PDU sets.
13. The source base station according to claim 11, wherein: The forwarding data includes PDU set information, and the PDU set information includes at least one of PDU set identification information, a PDU set sequence number, and PDU set importance information.
14. The source base station according to claim 13, wherein: The PDU set information is included in a GPRS Tunneling Protocol (GTP)-U extension header provided by a protocol for user plane data transmission on an interface between base stations.
15. The source base station according to claim 11, wherein: The target base station indicates the PDU set support information to the core network control plane node through a path switch request message or a handover request confirmation message.
