WO2018202205A1 - Utilisation d'en-tête sdap pour la gestion de qos réflective as/nas et pour garantir une distribution dans l'ordre de paquets pendant la réaffectation dans des systèmes de communication 5g - Google Patents

Utilisation d'en-tête sdap pour la gestion de qos réflective as/nas et pour garantir une distribution dans l'ordre de paquets pendant la réaffectation dans des systèmes de communication 5g Download PDF

Info

Publication number
WO2018202205A1
WO2018202205A1 PCT/CN2018/085893 CN2018085893W WO2018202205A1 WO 2018202205 A1 WO2018202205 A1 WO 2018202205A1 CN 2018085893 W CN2018085893 W CN 2018085893W WO 2018202205 A1 WO2018202205 A1 WO 2018202205A1
Authority
WO
WIPO (PCT)
Prior art keywords
drb
qos
qos flow
flow
data packet
Prior art date
Application number
PCT/CN2018/085893
Other languages
English (en)
Inventor
Yu-Syuan Jheng
Pavan Santhana Krishna Nuggehalli
Chia-Chun Hsu
Original Assignee
Mediatek Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US15/971,093 external-priority patent/US20180324631A1/en
Application filed by Mediatek Inc. filed Critical Mediatek Inc.
Priority to EP18793837.8A priority Critical patent/EP3613225A4/fr
Priority to CN201880004369.6A priority patent/CN109952773A/zh
Publication of WO2018202205A1 publication Critical patent/WO2018202205A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers

Definitions

  • the present disclosure relates generally to mobile communication systems, and more particularly, to user equipment (UE) that supports utilization of Service Data Adaptation Protocol (SDAP) headers for handling Application Service (AS) /Non-Access Stratum (NAS) reflective Quality of Service (QoS) and to ensure in-sequence packet delivery during remapping in 5G communication systems.
  • SDAP Service Data Adaptation Protocol
  • AS Application Service
  • NAS Non-Access Stratum
  • QoS Quality of Service
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • 5G New Radio is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements.
  • 3GPP Third Generation Partnership Project
  • Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard.
  • LTE Long Term Evolution
  • the apparatus may be a UE.
  • the UE receives a downlink data packet and determines a service data flow associated with the downlink data packet.
  • the UE extracts, from the downlink data packet, a Non-Access Stratum (NAS) Reflective QoS Indication (RQI) indicator that instructs the UE to map a service data flow to the QoS flow.
  • the UE also extracts, from the downlink data packet, a Quality of Service (QoS) flow identifier identifying a QoS flow.
  • QoS Quality of Service
  • the UE generates a first NAS mapping that maps the service data flow to the QoS flow, in response to a determination that the service data flow is not mapped to the QoS flow at the UE.
  • the UE further transmits, in accordance with the first NAS mapping, an uplink data packet associated with the service data flow through the QoS flow.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.
  • FIGs. 2A, 2B, 2C, and 2D are diagrams illustrating examples of a DL frame structure, DL channels within the DL frame structure, an UL frame structure, and UL channels within the UL frame structure, respectively.
  • FIG. 3 is a diagram illustrating a base station in communication with a UE in an access network.
  • FIG. 4 illustrates an example logical architecture of a distributed access network.
  • FIG. 5 illustrates an example physical architecture of a distributed access network.
  • FIG. 6 is a diagram showing an example of a DL-centric subframe.
  • FIG. 7 is a diagram showing an example of an UL-centric subframe.
  • FIG. 8 illustrates a protocol stack for QoS flow-based 5G communication systems.
  • FIGs. 9A and 9B illustrate mappings of QoS flows for both downlink and uplink IP data flows.
  • FIG. 10 illustrates NAS level mappings of IP flows to QoS flows and AS level mappings of QoS flows to data bearers.
  • FIG. 11 is a sequence diagram illustrating NAS reflective QoS functionality.
  • FIG. 12 is a sequence diagram illustrating AS reflective QoS functionality.
  • FIG. 13 is a diagram showing an example of a SDAP header that may be utilized to enable NAS/AS reflective QoS functionality.
  • FIGs. 14A-14B are diagrams illustrating utilization and processing of an example SDAP header to enable reflective QoS flow mappings.
  • FIGs. 15A-15B, 16 and 17 are diagrams illustrating utilization of an example SDAP header to guarantee in-sequence delivery of packets during QoS flow relocations.
  • FIGs. 18A-18B are diagrams showing examples of SDAP headers that may be utilized to guarantee in-sequence delivery of packets during QoS flow relocations.
  • FIG. 19 is a flow chart 1900 of a method (process) for enabling NAS level mappings of IP flows to QoS flows.
  • FIG. 20 is a flow chart 2000 of a method (process) for enabling AS level mappings of QoS flows to data bearers.
  • FIGs. 21A-21B are flow charts 2100 and 2120, respectively, of a method (process) performed by a UE to guarantee in-sequence delivery of packets during QoS flow relocations.
  • FIGs. 22A-22C are flow charts 2200, 2220 and 2230, respectively, of a method (process) performed by a base station to guarantee in-sequence delivery of packets during QoS flow relocations.
  • FIG. 23 is a conceptual data flow diagram illustrating the data flow between different components/means in an exemplary apparatus.
  • FIG. 24 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.
  • processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • processors in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer.
  • such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • optical disk storage magnetic disk storage
  • magnetic disk storage other magnetic storage devices
  • combinations of the aforementioned types of computer-readable media or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100.
  • the wireless communications system also referred to as a wireless wide area network (WWAN)
  • WWAN wireless wide area network
  • the base stations 102 may include macro cells (high power cellular base station) and/or small cells (low power cellular base station) .
  • the macro cells include base stations.
  • the small cells include femtocells, picocells, and microcells.
  • the base stations 102 (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) interface with the EPC 160 through backhaul links 132 (e.g., S1 interface) .
  • UMTS Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network
  • the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages.
  • the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160) with each other over backhaul links 134 (e.g., X2 interface) .
  • the backhaul links 134 may be wired or wireless.
  • the base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102’may have a coverage area 110’that overlaps the coverage area 110 of one or more macro base stations 102.
  • a network that includes both small cell and macro cells may be known as a heterogeneous network.
  • a heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) .
  • eNBs Home Evolved Node Bs
  • HeNBs Home Evolved Node Bs
  • CSG closed subscriber group
  • the communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104.
  • UL uplink
  • DL downlink
  • the communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
  • MIMO multiple-input and multiple-output
  • the communication links may be through one or more carriers.
  • the base stations 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100 MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction.
  • the carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL) .
  • the component carriers may include a primary component carrier and one or more secondary component carriers.
  • a primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
  • PCell primary cell
  • SCell secondary cell
  • the wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum.
  • AP Wi-Fi access point
  • STAs Wi-Fi stations
  • communication links 154 in a 5 GHz unlicensed frequency spectrum.
  • the STAs 152 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • the small cell 102’ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102’may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102’, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
  • the gNodeB (gNB) 180 may operate in millimeter wave (mmW) frequencies and/or near mmW frequencies in communication with the UE 104.
  • mmW millimeter wave
  • the gNB 180 may be referred to as an mmW base station.
  • Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave.
  • Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters.
  • the super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW /near mmW radio frequency band has extremely high path loss and a short range.
  • the mmW base station 180 may utilize beamforming 184 with the UE 104 to compensate for the extremely high path loss and short range.
  • the EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172.
  • MME Mobility Management Entity
  • MBMS Multimedia Broadcast Multicast Service
  • BM-SC Broadcast Multicast Service Center
  • PDN Packet Data Network
  • the MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
  • HSS Home Subscriber Server
  • the MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160.
  • the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172.
  • IP Internet protocol
  • the PDN Gateway 172 provides UE IP address allocation as well as other functions.
  • the PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176.
  • the IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service (PSS) , and/or other IP services.
  • the BM-SC 170 may provide functions for MBMS user service provisioning and delivery.
  • the BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions.
  • PLMN public land mobile network
  • the MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.
  • MMSFN Multicast Broadcast Single Frequency Network
  • the base station may also be referred to as a gNB, Node B, evolved Node B (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , or some other suitable terminology.
  • the base station 102 provides an access point to the EPC 160 for a UE 104.
  • Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a toaster, or any other similar functioning device.
  • Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, etc. ) .
  • the UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • FIG. 2A is a diagram 200 illustrating an example of a DL frame structure.
  • FIG. 2B is a diagram 230 illustrating an example of channels within the DL frame structure.
  • FIG. 2C is a diagram 250 illustrating an example of an UL frame structure.
  • FIG. 2D is a diagram 280 illustrating an example of channels within the UL frame structure.
  • Other wireless communication technologies may have a different frame structure and/or different channels.
  • a frame (10 ms) may be divided into 10 equally sized subframes. Each subframe may include two consecutive time slots.
  • a resource grid may be used to represent the two time slots, each time slot including one or more time concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs) ) .
  • RBs time concurrent resource blocks
  • the resource grid is divided into multiple resource elements (REs) .
  • REs resource elements
  • an RB For a normal cyclic prefix, an RB contains 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols (for DL, OFDM symbols; for UL, SC-FDMA symbols) in the time domain, for a total of 84 REs.
  • an RB For an extended cyclic prefix, an RB contains 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs.
  • the number of bits carried by each RE depends on the modulation scheme.
  • the DL-RS may include cell-specific reference signals (CRS) (also sometimes called common RS) , UE-specific reference signals (UE-RS) , and channel state information reference signals (CSI-RS) .
  • CRS cell-specific reference signals
  • UE-RS UE-specific reference signals
  • CSI-RS channel state information reference signals
  • FIG. 2A illustrates CRS for antenna ports 0, 1, 2, and 3 (indicated as R0, R1, R2, and R3, respectively) , UE-RS for antenna port 5 (indicated as R5) , and CSI-RS for antenna port 15 (indicated as R) .
  • FIG. 2B illustrates an example of various channels within a DL subframe of a frame.
  • the physical control format indicator channel (PCFICH) is within symbol 0 of slot 0, and carries a control format indicator (CFI) that indicates whether the physical downlink control channel (PDCCH) occupies 1, 2, or 3 symbols (FIG. 2B illustrates a PDCCH that occupies 3 symbols) .
  • the PDCCH carries downlink control information (DCI) within one or more control channel elements (CCEs) , each CCE including nine RE groups (REGs) , each REG including four consecutive REs in an OFDM symbol.
  • DCI downlink control information
  • CCEs control channel elements
  • each CCE including nine RE groups (REGs) , each REG including four consecutive REs in an OFDM symbol.
  • a UE may be configured with a UE-specific enhanced PDCCH (ePDCCH) that also carries DCI.
  • the ePDCCH may have 2, 4, or 8 RB pairs (FIG.
  • the physical hybrid automatic repeat request (ARQ) (HARQ) indicator channel (PHICH) is also within symbol 0 of slot 0 and carries the HARQ indicator (HI) that indicates HARQ acknowledgement (ACK) /negative ACK (NACK) feedback based on the physical uplink shared channel (PUSCH) .
  • the primary synchronization channel (PSCH) may be within symbol 6 of slot 0 within subframes 0 and 5 of a frame.
  • the PSCH carries a primary synchronization signal (PSS) that is used by a UE to determine subframe/symbol timing and a physical layer identity.
  • PSS primary synchronization signal
  • the secondary synchronization channel may be within symbol 5 of slot 0 within subframes 0 and 5 of a frame.
  • the SSCH carries a secondary synchronization signal (SSS) that is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DL-RS.
  • the physical broadcast channel (PBCH) which carries a master information block (MIB) , may be logically grouped with the PSCH and SSCH to form a synchronization signal (SS) block.
  • MIB master information block
  • the MIB provides a number of RBs in the DL system bandwidth, a PHICH configuration, and a system frame number (SFN) .
  • the physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.
  • SIBs system information blocks
  • some of the REs carry demodulation reference signals (DM-RS) for channel estimation at the base station.
  • the UE may additionally transmit sounding reference signals (SRS) in the last symbol of a subframe.
  • SRS sounding reference signals
  • the SRS may have a comb structure, and a UE may transmit SRS on one of the combs.
  • the SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
  • FIG. 2D illustrates an example of various channels within an UL subframe of a frame.
  • a physical random access channel (PRACH) may be within one or more subframes within a frame based on the PRACH configuration.
  • the PRACH may include six consecutive RB pairs within a subframe.
  • PRACH physical random access channel
  • the PRACH allows the UE to perform initial system access and achieve UL synchronization.
  • a physical uplink control channel may be located on edges of the UL system bandwidth.
  • the PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and HARQ ACK/NACK feedback.
  • UCI uplink control information
  • the PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.
  • BSR buffer status report
  • PHR power headroom report
  • FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network.
  • IP packets from the EPC 160 may be provided to a controller/processor 375.
  • the controller/processor 375 implements layer 3 and layer 2 functionality.
  • Layer 3 includes a radio resource control (RRC) layer
  • layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • the controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression /decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDU
  • the transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions.
  • Layer 1 which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing.
  • the TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M- QAM) ) .
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M- QAM M-quadrature amplitude modulation
  • the coded and modulated symbols may then be split into parallel streams.
  • Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.
  • IFFT Inverse Fast Fourier Transform
  • the OFDM stream is spatially precoded to produce multiple spatial streams.
  • Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing.
  • the channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350.
  • Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX.
  • Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.
  • each receiver 354RX receives a signal through its respective antenna 352.
  • Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356.
  • the TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions.
  • the RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream.
  • the RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) .
  • FFT Fast Fourier Transform
  • the frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal.
  • the symbols on each subcarrier, and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358.
  • the soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel.
  • the data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
  • the controller/processor 359 can be associated with a memory 360 that stores program codes and data.
  • the memory 360 may be referred to as a computer-readable medium.
  • the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160.
  • the controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
  • RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting
  • PDCP layer functionality associated with
  • Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
  • the spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.
  • the UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350.
  • Each receiver 318RX receives a signal through its respective antenna 320.
  • Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
  • the controller/processor 375 can be associated with a memory 376 that stores program codes and data.
  • the memory 376 may be referred to as a computer-readable medium.
  • the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160.
  • the controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • New radio may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA) -based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP) ) .
  • NR may utilize OFDM with a cyclic prefix (CP) on the uplink and downlink and may include support for half-duplex operation using time division duplexing (TDD) .
  • NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond) , millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz) , massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC) service.
  • eMBB Enhanced Mobile Broadband
  • mmW millimeter wave
  • mMTC massive MTC
  • URLLC ultra-reliable low latency communications
  • NR resource blocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1 ms duration or a bandwidth of 15 kHz over a 1 ms duration.
  • Each radio frame may consist of 10 or 50 subframes with a length of 10 ms.
  • Each subframe may have a length of 0.2 ms.
  • Each subframe may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched.
  • Each subframe may include DL/UL data as well as DL/UL control data.
  • UL and DL subframes for NR may be as described in more detail below with respect to FIGs. 6 and 7.
  • Beamforming may be supported and beam direction may be dynamically configured.
  • MIMO transmissions with precoding may also be supported.
  • MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE.
  • Multi-layer transmissions with up to 2 streams per UE may be supported.
  • Aggregation of multiple cells may be supported with up to 8 serving cells.
  • NR may support a different air interface, other than an OFDM-based interface.
  • the NR RAN may include a central unit (CU) and distributed units (DUs) .
  • a NR BS e.g., gNB, 5G Node B, Node B, transmission reception point (TRP) , access point (AP)
  • NR cells can be configured as access cells (ACells) or data only cells (DCells) .
  • the RAN e.g., a central unit or distributed unit
  • DCells may be cells used for carrier aggregation or dual connectivity and may not be used for initial access, cell selection/reselection, or handover.
  • DCells may not transmit synchronization signals (SS) in some cases DCells may transmit SS.
  • SS synchronization signals
  • NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.
  • FIG. 4 illustrates an example logical architecture 400 of a distributed RAN, according to aspects of the present disclosure.
  • a 5G access node 406 may include an access node controller (ANC) 402.
  • the ANC may be a central unit (CU) of the distributed RAN 400.
  • the backhaul interface to the next generation core network (NG-CN) 404 may terminate at the ANC.
  • the backhaul interface to neighboring next generation access nodes (NG-ANs) may terminate at the ANC.
  • the ANC may include one or more TRPs 408 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term) .
  • TRPs 408 which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term.
  • TRP may be used interchangeably with “cell. ” .
  • the TRPs 408 may be a distributed unit (DU) .
  • the TRPs may be connected to one ANC (ANC 402) or more than one ANC (not illustrated) .
  • ANC ANC
  • RaaS radio as a service
  • a TRP may include one or more antenna ports.
  • the TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.
  • the local architecture of the distributed RAN 400 may be used to illustrate fronthaul definition.
  • the architecture may be defined that support fronthauling solutions across different deployment types.
  • the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter) .
  • the architecture may share features and/or components with LTE.
  • the next generation AN (NG-AN) 410 may support dual connectivity with NR.
  • the NG-AN may share a common fronthaul for LTE and NR.
  • the architecture may enable cooperation between and among TRPs 408. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC 402. According to aspects, no inter-TRP interface may be needed/present.
  • a dynamic configuration of split logical functions may be present within the architecture of the distributed RAN 400.
  • the PDCP, RLC, MAC protocol may be adaptably placed at the ANC or TRP.
  • FIG. 5 illustrates an example physical architecture of a distributed RAN 500, according to aspects of the present disclosure.
  • a centralized core network unit (C-CU) 502 may host core network functions.
  • the C-CU may be centrally deployed.
  • C-CU functionality may be offloaded (e.g., to advanced wireless services (AWS) ) , in an effort to handle peak capacity.
  • a centralized RAN unit (C-RU) 504 may host one or more ANC functions.
  • the C-RU may host core network functions locally.
  • the C-RU may have distributed deployment.
  • the C-RU may be closer to the network edge.
  • a distributed unit (DU) 506 may host one or more TRPs.
  • the DU may be located at edges of the network with radio frequency (RF) functionality.
  • RF radio frequency
  • FIG. 6 is a diagram 600 showing an example of a DL-centric subframe.
  • the DL-centric subframe may include a control portion 602.
  • the control portion 602 may exist in the initial or beginning portion of the DL-centric subframe.
  • the control portion 602 may include various scheduling information and/or control information corresponding to various portions of the DL-centric subframe.
  • the control portion 602 may be a physical DL control channel (PDCCH) , as indicated in FIG. 6.
  • the DL-centric subframe may also include a DL data portion 604.
  • the DL data portion 604 may sometimes be referred to as the payload of the DL-centric subframe.
  • the DL data portion 604 may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE) .
  • the DL data portion 604 may be a physical DL shared channel (PDSCH) .
  • PDSCH physical DL shared channel
  • the DL-centric subframe may also include a common UL portion 606.
  • the common UL portion 606 may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms.
  • the common UL portion 606 may include feedback information corresponding to various other portions of the DL-centric subframe.
  • the common UL portion 606 may include feedback information corresponding to the control portion 602.
  • Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information.
  • the common UL portion 606 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs) , and various other suitable types of information.
  • RACH random access channel
  • SRs scheduling requests
  • the end of the DL data portion 604 may be separated in time from the beginning of the common UL portion 606.
  • This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms.
  • This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE) ) to UL communication (e.g., transmission by the subordinate entity (e.g., UE) ) .
  • DL communication e.g., reception operation by the subordinate entity (e.g., UE)
  • UL communication e.g., transmission by the subordinate entity (e.g., UE)
  • FIG. 7 is a diagram 700 showing an example of an UL-centric subframe.
  • the UL-centric subframe may include a control portion 702.
  • the control portion 702 may exist in the initial or beginning portion of the UL-centric subframe.
  • the control portion 702 in FIG. 7 may be similar to the control portion 602 described above with reference to FIG. 6.
  • the UL-centric subframe may also include an UL data portion 704.
  • the UL data portion 704 may sometimes be referred to as the pay load of the UL-centric subframe.
  • the UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS) .
  • the control portion 702 may be a physical DL control channel (PDCCH) .
  • PDCCH physical DL control channel
  • the end of the control portion 702 may be separated in time from the beginning of the UL data portion 704. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity) .
  • the UL-centric subframe may also include a common UL portion 706.
  • the common UL portion 706 in FIG. 7 may be similar to the common UL portion 706 described above with reference to FIG. 7.
  • the common UL portion 706 may additionally or alternatively include information pertaining to channel quality indicator (CQI) , sounding reference signals (SRSs) , and various other suitable types of information.
  • CQI channel quality indicator
  • SRSs sounding reference signals
  • two or more subordinate entities may communicate with each other using sidelink signals.
  • Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications.
  • a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS) , even though the scheduling entity may be utilized for scheduling and/or control purposes.
  • the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum) .
  • Embodiments are disclosed below of a quality of service (QoS) model that supports a QoS flow based framework.
  • Networks use QoS parameters to ensure that certain traffic types are handled in a certain way to provide a certain, threshold amount of QoS.
  • a given traffic flow may be classified by certain, generally static QoS parameters, such as guaranteed bit rate (GBR) , non-guaranteed bit rate (non-GBR) , priority handling, packet delay budget, packet error loss rate, and/or other parameters.
  • GRR guaranteed bit rate
  • non-GBR non-guaranteed bit rate
  • priority handling packet delay budget
  • packet error loss rate packet error loss rate
  • a traffic flow may for example be forwarded via a radio bearer that can carry traffic according to the QoS parameter.
  • the EPS bearer handles all the user packets mapped to the EPS bearer with the same QoS. Within the EPS bearer, there is no further differentiated handling of the user plane packets. For improvement, the packets mapped to the different QoS flows belonging to the UE traffic can be handled differently. For example, multiple EPS bearers with different QoS parameters need to be created.
  • a QoS Flow ID may be used to identify a QoS flow in the present disclosure.
  • UP traffic with the same QFI within a PDU session receives the same traffic forwarding treatment (e.g. scheduling, admission threshold) . It can be applied to PDUs with different types of payload, i.e. IP packets, non-IP PDUs and Ethernet frames.
  • the QFI should be unique within a PDU session.
  • Each QoS flow may be associated with QoS parameters, such as a 5G QoS Indicator (5QI) .
  • a 5QI is a scalar that is used as a reference to 5G QoS characteristics, i.e., to access node-specific parameters that control QoS forwarding treatment for the QoS flow (e.g., scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc. ) .
  • QoS flows provide finest granularity for QoS differentiation of packets within a PDU session.
  • FIG. 8 illustrates a protocol stack for QoS flow-based communication systems.
  • the protocol stack shown in FIG. 8 includes a plurality of layers: an IP layer 802, SDAP layer 804, PDCP layer 806, RLC layer 808, MAC layer 810 and L1 layer 812.
  • the IP layer 802 is the network layer of the IP protocol suite, and provides a common packet format and addressing scheme capable of transporting data over multiple subnetwork technologies (e.g., Ethernet, ATM, and the like) .
  • Functionality of the PDCP layer 806, the RLC layer 808 and the MAC layer 810 is described above in conjunction with FIG. 3.
  • the L1 layer 812 is a physical layer.
  • the present system has retained the DRB concept for user plane handling. This requires that the one or more QoS flows belonging to the PDU session of the UE is mapped to the DRB depending on the QoS requirement.
  • the mapping of the QoS flow to the DRB is done within the new user plane protocol layer called Service Data Adaptation Protocol (SDAP) layer 804 which is placed above the PDCP layer 806 and below the IP layer 802.
  • SDAP entities are located in the SDAP layer 804.
  • Several SDAP entities may be defined for a UE. There is the SDAP entity configured per cell group for each individual PDU session.
  • the SDAP entity in the SDAP layer 804 performs mapping between the QoS flow and the data radio bearer for both the DL and the UL traffic.
  • QFI is used to identify the QoS flow.
  • User plane traffic with the same session PDU QFI receives the same traffic transmission process (e.g., scheduling, and approval threshold (admission threshold) ) .
  • QFI may be applied to each of the different types of payload PDU 814 (i.e., IP packets, unstructured packets, Ethernet frames, etc. ) .
  • FIG. 9A illustrates mappings of QoS flows for downlink IP data flows. More specifically, FIG. 9A illustrates communication between User Plane Function (UPF) device/entity/function 912 and the UE 926.
  • the UPF 912 may perform the same functions as the base station for modifying the QoS treatment of packets based on a request from the device; however the UPF 912 may not change the scheduling priority over the radio, but instead may change the QoS packet marking to match the modified QoS treatment when forwarding the packets to the base station (which causes the base station to modify the scheduling priority) .
  • the UPF 912 is able to map one or more IP flows 906a-906n from an application or service layer 902 to one or more QoS flows. For example, IP packets sourced from the same application or service may be considered as being associated with the same IP flow. Similarly, IP packets destined to the same application or service may be considered as being associated with the same IP flow.
  • both the UPF 912 and the UE 926 also define packet filters 911 that allow the NAS level 908 at the UE 926 and the UPF 912 to decide which IP flow to map onto which QoS flow 916.
  • This filtering may be performed based on source and destination IP address and port number. It is therefore flexible so that the network can map packets of different kinds of applications to different QoS flows 916.
  • the UPF 912 assigns a QFI 914 and adds it to a header of each payload packet 910 for every QoS flow 916 and transmits all QoS flows 916 of one or more PDU sessions 918 to a base station 920. For each PDU session, a single tunnel may be established between the UPF 912 and the base station 920 for exchanging the packets associated with different QoS flows 916 of the PDU session 918.
  • the base station 920 is configured to receive a plurality of packets of at least one QoS flow 916 from the UPF 912.
  • the QFI 914 associated with the at least one QoS flow 916 is received in the header of each payload packet. Further, the base station 920 is configured to map each received packet of each QoS flow 916 to one of the DRBs 922, 924.
  • the QoS flows 916 are mapped to the DRBs 922, 924 based on the QFI 914 associated with the QoS flows 916 according to certain rules described below. This mapping of QoS flows 916 to DRBs 922, 924 is performed at an AS level 909.
  • the QoS parameters of the QoS flow are also provided to the base station 920 as the QoS profile when the PDU session 918 is established or the new QoS flow 916 is established or when the radio connection is established.
  • the QoS parameters may also be pre-configured in the base station 920.
  • the DRB 922, 924 defines the packet treatment on the radio interface (i.e., Uu) .
  • the DRB 922, 924 serves the packets with the same packet forwarding treatment. Separate DRBs 922, 924 may be established for the QoS flows 916 requiring different packet forwarding treatment.
  • the base station 920 knows the mapping between each QoS flow 916 and associated QoS parameters (or QoS profile) and accordingly decides the radio configuration for corresponding data radio bearer 922, 924.
  • the base station 920 maps the QoS flows 916 to the DRBs 922, 924 based on the packet marking (i.e. QFI 914) and the associated QoS profiles.
  • One DRB such as a first DRB 922, can be mapped to multiple QoS flows.
  • the base station 920 provides the list of one or more QFIs 914 and PDU session 918 identifier.
  • the QoS parameters e.g. packet error rate, latency, data rate, etc.
  • QFI 914 is carried in an SDAP header, as described below.
  • FIG. 9B illustrates mappings of QoS flows for uplink IP data flows.
  • the UE 926 maps the QoS flows 916 to the DRBs 922, 924 based on mapping received from the base station 920. Further, the UE 926 receives uplink user plane packets included in IP flows 904a-904n from a higher layer, such as Application/Service layer 902. Further, the UE 926 maps each packet first to a corresponding QoS flow 916 at the NAS level using corresponding packet filters 911. Next, the UE 926 maps each QoS flow 916 to corresponding DRBs 922, 924 based on the received QFI 914 at the AS level 909.
  • the UE 926 maps the packet to the default DRB (not shown in FIG. 9) of the PDU session. Further, the UE 926 also adds the QFI 914 in a header (e.g., SDAP header) of the packet sent on each DRB, including the default DRB. Further, the UE 926 transmits all uplink packets along with corresponding packet headers to the base station 920 via corresponding DRBs 922, 924 associated with particular QoS flows 916.
  • a header e.g., SDAP header
  • each QoS flow 916 may be associated with QoS parameters using a special indicator, such as 5QI.
  • the 5QI is a scalar that is used as a reference to 5G QoS characteristics.
  • Each 5QI represents one combination of 5G QoS characteristics (certain QoS parameters, e.g., the scheduling weight, approval thresholds, queue management thresholds, etc. ) .
  • 5QI may represent the following 5G QoS characteristics: resource type (GBR or Non-GBR) , flow priority level, packet delay budget and packet error rate.
  • Flow priority level is a parameter indicating the relative priority of fulfilling the required bit rate and delivery characteristics (packet delay budget, packet error rate) . It impacts the PDU flow admission to resources in the network as well as the distribution of resources for packet forwarding treatment, allowing consistency in admission and resource distribution to fulfil the service requirements.
  • a Packet Delay Budget is a QoS characteristic that describes one aspect of a packet forwarding treatment that a QoS flow receives edge-to-edge between the UE 926 and the UPF 912.
  • the PDB defines an upper bound for the time that a packet may be delayed between the UE 926 and the UPF 912. For a certain 5QI the value of the PDB is the same in the UL and DL.
  • the PDB is used to support the configuration of scheduling and link layer functions (e.g. the setting of scheduling priority weights and HARQ target operating points) .
  • the PDB denotes an end-to-end “soft upper bound” .
  • PDUs may be stored in a packet buffer if a data rate, such as the short-term bit rate, is higher than the maximum bit rate associate with the PDU data flow. If packets are dropped, the number of dropped packets may be recorded. The long-term overall packet drop rate (or packet loss rate) may be limited to the packet error rate requirement.
  • Non-standardized 5QIs may be used by mobile network operators to associate different QoS characteristics with standardized 5QI type according to their own needs.
  • QoS profile of the standardized 5QI is typically better for internetworking with EPC-based networks. It should be noted that UE’s 926 behavior typically does not depend on a type of used 5QI scalars.
  • a first option is to use non-GBR QoS flows in combination with the standardized 5QI values.
  • standardized 5QI is used as QFI.
  • a second option applies to both non-GBR and GBR QoS flows, where 5QI values are not used.
  • the UE 926 needs to signal (transmit) QFI 914 to the base station 920 and to the UPF 912 over N2 and N7 interfaces, respectively.
  • additional signaling of QoS parameters is required.
  • FIG. 10 illustrates NAS level mappings of IP flows to QoS flows and AS level mappings of QoS flows to data bearers based on corresponding mapping tables, which may be performed by an apparatus 1000.
  • the apparatus 1000 may be either a UE (e.g. UE 926) or a base station (e.g., base station 920) .
  • the apparatus 1000 receives a plurality of packets belonging to one or more IP flows, which in turn belong to one or more PDU sessions (e.g., a first PDU session 1004) .
  • the apparatus 1000 performs the classification and marking of DL/UL traffic, i.e.
  • a QoS rule may include a QoS rule identifier, the QFI of the QoS flow, and a QoS flow template (i.e. the set of packet filters 1006 and corresponding precedence values associated with the QoS flow 1008) .
  • One QoS flow can have one or more QoS rules.
  • QoS rule ID Precedence Packet Filter QFI 1 1 (UE IP, *, RTP, *, UDP) 5 2 0 (UE IP, *, 73, 73, *) 65 3 2 (UE IP, *, Game *, *) 103 4 5 9
  • each PDU session 1004 is required to have a default QoS rule.
  • the last QoS rule having QoS rule Id equal to 4 is the default QoS rule.
  • the default QoS rule is the only QoS rule associated with a particular PDU session that may contain no packet filter (as shown in Table 2) .
  • the apparatus 1000 Upon completing the mappings between IP flows and QoS flows 1008, at AS level 1010, the apparatus 1000 performs the association of QoS flows 1008 to DRBs 1012, based on corresponding mapping table.
  • the exemplary AS level mappings of QoS flows 1008 to DRBs 1012 are specified in Table 3 below:
  • Last row of Table 3 indicates that all unknown QFIs will be mapped to a default third DRB (not shown in FIG. 10) .
  • each of a first DRB 1012a and second a DRB 1012b sends corresponding QoS flow packets to the corresponding dedicated logical traffic channel 1014a and 1014b with encryption and Robust Header Compression (ROHC) 1016a and 1016b, respectively.
  • ROHC Robust Header Compression
  • NAS reflective QoS is an optional feature used in the communication systems of the present disclosure to control UE derived QoS rules by downlink traffic implicitly. More specifically, network decides which QoS rules to apply on DL traffic, and UE reflects the DL QoS rules to the associated UL traffic. When UE receives a DL packet for which reflective QoS should be applied, the UE creates a new derived QoS rule, if needed. The packet filter in the derived QoS rule is derived from the DL packet. It is possible to apply both reflective QoS and non-reflective QoS on the same PDU session. Further, AS reflective QoS is an optional feature used by base stations in the communication systems of the present disclosure to configure QoS flow to DRB mapping by downlink traffic implicitly.
  • FIG. 11 is a sequence diagram illustrating NAS reflective QoS functionality.
  • the communications system 1100 comprises a Data Network (DN) 1102 (e.g., operator services, Internet access or 3rd party services) , Session Management Function (SMF) 1104, UPF 1106, base station 1108, and UE 1110.
  • DN Data Network
  • SMF Session Management Function
  • UPF User Plane Function
  • UE 1110 packets of the PDU session in the DL direction traverse from the DN 1102 to the UPF 1106 over a N6 interface 1112, from the UPF 1106 to the base station 1108 over a N3 interface 1118 and from the base station 1108 to the UE 1110 over a radio interface 1120.
  • the SMF 1104 is configured to control: session management (e.g., by session establishment, modifications and release) , UE IP address allocation and management, routing traffic from the UPF 1106 with the appropriate destination steering (traffic steering) setting, policy control enforcement, and QoS interface, among other functionalities.
  • the SMF 1104 communicates with the UPF 1106 over a N4 interface 1114.
  • the SMF 1104 sends a reflective QoS rule associated with the downlink packet sent over the N6 interface 1112 to the UPF 1106.
  • the reflective QoS rule is sent by the SMF 1104 via N4 interface 1114.
  • the reflective QoS rule indicates to the UPF 1106 that NAS reflective QoS should be activated.
  • the UPF 1106 receives a DL packet matching the QoS rule that contains an indication to activate reflective QoS, the UPF 1106 includes a Reflective QoS Indicator (RQI) along with the QFI of the QoS flow in the header of the packet transmitted over the N3 interface 1118.
  • RQI Reflective QoS Indicator
  • the base station 1108 also adds a header (e.g., SDAP header) to a DL radio packet transmitted over the radio interface 1120.
  • the UE 1110 when the UE 1110 receives the DL packet for which reflective QoS should be applied (packet having a set RQI indicator within the header) , the UE 1110 creates a new derived QoS rule.
  • the packet filter in the derived QoS rule is derived from the received DL packet.
  • the UE 1110 also adds 1122 the derived packet filter to the plurality of NAS level packet filters 1006.
  • the UE 1110 performs the classification and marking of UL traffic using the newly created NAS level packet filter and using the derived QoS rule.
  • the RQI is sent for downlink user plane traffic only.
  • packets of the PDU session in the uplink (UL) direction traverses from the UE 1110 to the base station 1108 over the radio interface 1120, from the base station 1108 to the UPF 1106 over the N3 interface 1118 and from the UPF 1106 to the DN 1102 over the N6 interface 1112.
  • the RQI is sent for downlink user plane traffic only, but the uplink traffic traversing from the UE 1110 to the UPF 1106 carries the QFI of the corresponding QoS flow in AS protocol (i.e., SDAP) header.
  • FIG. 12 is a sequence diagram 1200 illustrating AS reflective QoS functionality.
  • the base station 1204 configures QoS flow to DRB mapping using one of two mechanisms.
  • the UE 1202 receives mapping of the QoS flow identifiers to the DRBs for each established PDU session from the base station 1204 in a signaling message (e.g., RRC signaling message) .
  • the AS reflective QoS functionality may be activated implicitly through the DL packet using Reflective QoS flow to DRB mapping Indication (RDI) . As shown in FIG.
  • RDI Reflective QoS flow to DRB mapping Indication
  • the RDI is sent for downlink user plane traffic only and is contained within the AS protocol header 1206 along with the QFI of the downlink packet transmitted via a particular DRB 1210.
  • the RDI bit indicates whether QoS flow to DRB mapping rule should be updated.
  • the UE 1202 Based on the received RDI bit, the UE 1202 selectively updates corresponding QoS flow to DRB mapping rule and sends the UP packets 1208 associated with the same QoS flow using the same DRB 1210.
  • FIG. 13 is a diagram showing an example of a SDAP header that may be utilized to enable NAS/AS reflective QoS functionality. It should be noted that in some configurations the SDAP header 1300 may not be present and may be configured per DRB. If configured, size of the SDAP header 1300 for a DRB is static (e.g., 1 byte) . Presence of the SDAP header 1300 in DL traffic and UL traffic can be separately configured through corresponding RRC signaling procedures.
  • the SDAP header 1300 may include two additional indicators along with the QFI 1306.
  • the RQI indicator 1302 is utilized to configure NAS reflective QoS by indicating an update of NAS level mapping rule (s) .
  • the RDI indicator 1304 is used to configure AS reflective QoS by indicating whether AS level mapping rule (QoS flow to DRB mapping rule) should be updated.
  • both the RDI 1302 and the RDI 1304 are one bit long.
  • the RQI 1302 and the RDI 1304 may be sent separately depending on a utilized base station policy.
  • FIGS. 14A is a diagram illustrating utilization and processing of an example SDAP header to enable NAS reflective QoS flow mappings.
  • the DL packet transmitted from the base station 1404 to the UE 1402 may include the SDAP header 1406 (if configured to be present) .
  • the SDAP header 1406 includes the RQI and QFI indicators.
  • the UE 1402 performs SDAP header processing.
  • SDAP header processing 1408 involves extracting both the RQI and QFI from the header.
  • the UE 1402 extracts the RQI indicator first, determines whether the RQI indicator is set to 1 and extracts the QFI from the header only in response to determining that the RQI indicator is set.
  • the UE 1402 informs the upper (NAS) layer of the RQI and QFI.
  • the SDAP processing operation 1408 involves adding the identical QFI (received from the NAS level) to the SDAP header 1412 of the UL packet if the SDAP header 1412 is configured to be present for the UL traffic.
  • the UE 1402 performs NAS processing to enable NAS reflective QoS if configured. More specifically, at operation 1410, the UE 1402 extracts the packet filter from the DL packet. In some configurations, the UE 1402 derives the NAS level packet filter from a corresponding IP header of the DL packet. The IP header includes a 5-tuple consisting of source IP address, destination IP address, source port number, destination port number, and network protocol ID.
  • the operation 1410 also involves performing a reflective processing on the derived NAS level packet filter for the UL traffic. In some configurations, this reflective processing comprises reversing source and destination IP addresses and port numbers for the NAS level packet filter for a corresponding UL traffic.
  • the reflective processing involves creating a mirror packet header and mirror the QoS in a different flow direction (UL) .
  • the UE 1402 also determines whether there is an existing QoS rule (NAS level mapping) that maps the IP flow of the received DL packet to a corresponding QoS flow. If such NAS level mapping does not exist, the UE 1402 adds the newly derived QoS rule to the current NAS level mappings table and potentially removes the old QoS rule, if needed.
  • operation 1410 involves sending the QFI to the SDAP layer.
  • FIGS. 14B is a diagram illustrating utilization and processing of an example SDAP header to enable AS reflective QoS flow mappings.
  • the SDAP header 1422 (if configured to be present) includes the RDI and QFI indicators.
  • the UE 1402 performs SDAP header processing.
  • SDAP header processing 1408 involves extracting both the RDI and QFI from the header.
  • the UE 1402 extracts the RDI indicator first, determines whether the RDI indicator is set to 1 and extracts the QFI from the header only in response to determining that the RDI indicator is set. Further, if the RDI is set, the UE 1402 informs the AS level of the RDI and QFI.
  • the SDAP processing operation 1408 involves adding the identical QFI (received from the AS level) to the SDAP header 1424 of the UL packet if the SDAP header 1424 is configured to be present for the UL traffic.
  • the UE 1402 performs AS processing to enable AS reflective QoS if configured. More specifically, at operation 1411, the UE 1402 determines the identifier of the DRB over which the DL packet was received. The UE 1402 also determines whether there is an existing AS level mapping (QoS flow to DRB mapping) that maps the QoS flow of the received DL packet to the identified DRB. If such AS level mapping does not exist, the UE 1402 adds the newly derived QoS flow to DRB mapping to the current AS level mappings table and potentially removes the old mapping, if needed. In some configurations, the AS processing 1411 for the UL packet involves identifying the QoS flow associated with the QFI to determine which DRB should be used to send the UL packet.
  • AS level mapping QoS flow to DRB mapping
  • SDAP headers may also be utilized to address in-sequence delivery of packets (e.g. PDCP PDUs) during QoS flow relocation also known as QoS flow to DRB remapping.
  • QoS flow to DRB remapping is defined as the operation that changes the mapping relation between a QoS flow and a DRB, i.e., a QoS flow is reconfigured to be carried on a different DRB.
  • the remapping may take place when the base station wants to move a QoS flow in the default DRB to a dedicated DRB.
  • the present DRB for a QoS flow may become unavailable due to the change of radio environment including Handover (HO) .
  • the base station may adjust DRB allocation to better cope with the current traffic mix.
  • QoS flow relocation also means that data is moved from a first PDCP entity (source PDCP entity) to a second PDCP entity (target PDCP entity) .
  • source PDCP entity source PDCP entity
  • target PDCP entity target PDCP entity
  • one QoS flow is remapped to a more suitable DRB, which means that the latency of the target DRB may be shorter than that of the source DRB.
  • a packet sent over the target DRB may arrive earlier than a previous one sent over the source DRB. Therefore it is possible at the receiving side that one QoS flow is carried on more than one DRB at the same time.
  • the UE 1502 originally send UL packets associated with a particular QoS flow to the base station 1504 through the first DRB 1508.
  • the base station 1504 decides to relocate this QoS flow to the second DRB 1512.
  • the UE 1502 finds out about the remapping when it receives a DL packet having SDAP header 1510 through the second DRB 1512.
  • the SDAP header 1510 includes both the QFI associated with the relocated QoS flow and the RDI indicator discussed above.
  • the UE 1502 starts sending UL packets with the corresponding SDAP header 1514 through the second DRB 1512.
  • FIG. 15B is a diagram 1520 illustrating additional details related to QoS flow relocation. More specifically, packets 1522 represent UL packets associated with the first QoS flow 1516 that were sent by the UE 1502 through the first DRB 1508. Packets 1524 represent UL packets associated with the second QoS flow 1518 that were sent by the UE 1502 through the second DRB 1512. Further, packets 1526 represent UL packets associated with the first QoS flow 1516 that were sent by the UE 1502 through the second DRB 1512 after the QoS flow relocation.
  • FIG. 16 illustrates one solution to in-sequence packet delivery problem during QoS flow relocation. More specifically, the UE 1502 (not shown in FIG. 16) adds a one bit indicator in the SDAP header of a corresponding UL packet when changing transmit PDCP entity. Packets 1608 represent packets sent by the UE through the first DRB 1602 prior to relocation of the QoS flow 1606. SDAP headers 1610 of the first two packets 1608 include only the QFI indicator.
  • the UE 1502 Before transmitting through the first DRB 1602 the last UL packet associated with the QoS flow 1606, the UE 1502 adds a special so called “end-marker” to the header 1612 of that last packet. After the QoS flow relocation takes place, the UE 1502 starts sending UL packets through the second DRB 1604. It should be noted that the SDAP headers 1614 of these UL packets no longer include any special markers (e.g., end markers) .
  • the SDAP receiver on the other side of the DRB (e.g., SDAP receiver of the base station 1504) knows that the transmission of the QoS flow 1606 is going to end in this first DRB 1602. If the SDAP receiver of the base station 1504 subsequently receives packets of the same QoS flow 1606 in the second DRB 1604, the SDAP receiver of the base station 1504 knows that all packets were received in a proper order and can seamlessly pass all received UL packets to upper layers.
  • the SDAP receiver of the base station 1504 receives packets of the same flow in the second DRB 1604 without receiving a packet with the SDAP header having an end marker in the first DRB 1602, the SDAP receiver of the base station 1504 knows that out-of-order delivery has occurred and holds the new packet (s) until the packet containing an end marker in the header is received.
  • the SDAP receiver of the base station 1504 holds the packets having headers 1614 having the same QFI in a special buffer until the arrival of packet having headers 1612, so that all packets can be delivered in order to upper layers on the base station side.
  • FIG. 17 illustrates alternative solution to in-sequence packet delivery problem during QoS flow relocation. More specifically, the UE 1502 (not shown in FIG. 17) adds a one bit indicator in the SDAP header of a corresponding UL packet when changing transmit PDCP entity. Packets 1708 represent packets sent by the UE through the first DRB 1702 prior to relocation of the QoS flow 1706. SDAP headers of the first UL packets 1708 include only the QFI indicator.
  • the SDAP transmitter of the UE 1502 adds a special, so called start-marker to the header 1712 of the first UL packet transmitted through the second DRB 1704 to indicate the start of transmission of the QoS flow 1706 through the second DRB 1704.
  • the SDAP layer of the base station 1504 can directly pass all received packets 1708, 1710 to upper layers without waiting, since it knows that all packets were received in proper order.
  • FIG. 18A and 18B are diagrams showing examples of SDAP headers 1800 that may be utilized to guarantee in-sequence delivery of packets during QoS flow relocations.
  • either an end-marker 1804 or a start-marker 1808 described below can be represented by a single bit along with the QFI 1806 within the SDAP header 1800 during QoS flow relocation/remapping procedure.
  • the SDAP transmitter of the UE always uses either the end-marker 1804 or the start-marker 1808 depending on if there are any additional packet transmissions pending through the original DRB (e.g., the first DRB 1702 in FIG. 17) .
  • the SDAP transmitter of the UE may use acknowledgments sent by the RLC layer to determine whether any particular packet was successfully sent. In one configuration, if all transmitted packets are successfully acknowledged or if the SDAP transmitter no longer has any additional packets to send or if the original DRB is released, the SDAP transmitter of the UE can use the start-marker 1808 to shorten the latency, otherwise the end-marker 1804 is used. On the receiver side (e.g., base station side) the SDAP receiver waits for either the end-marker 1804 from the first DRB or waits for the start-marker 1808 from the second DRB. It should be noted that this functionality works the same in both directions. In other words, the SDAP transmitter of the UE is capable of adding start-markers 1808/end-markers 1804 to the corresponding UL packets, while the SDAP receiver of the UE is capable of properly interpreting these markers.
  • FIG. 19 is a flow chart 1900 of a method (process) for enabling NAS reflective QoS functionality.
  • the method may be performed by a UE (e.g., the NAS reflective QoS component 192 of thr UE 104, the UE 350, the UE 1110, the UE 1402, the apparatus 2302/2302’) .
  • the UE receives a DL data packet and determines a service data flow associated with the DL data packet.
  • the UE extracts from the DL data packet a NAS RQI indicator that instructs the UE to map the service protocol flow to the QoS flow.
  • the UE extracts from the DL data packet a QFI identifying a QoS flow associated with the received DL data packet.
  • the UE determines whether the service data flow is mapped to the QoS flow at the UE.
  • the UE generates a new NAS mapping that maps the service data flow to the QoS flow, in response to a determination that the service data flow is not mapped to the QoS flow at the UE.
  • the UE maintains an old NAS mapping, in response to a determination that the service data flow is mapped to the QoS flow at the UE.
  • the UE removes an old NAS mapping that maps the service data flow to a different QoS flow, in response to a determination that the service data flow is not mapped to the QoS flow at the UE.
  • the UE transmits, in accordance with the new NAS mapping, an UL data packet associated with the service data flow through the QoS flow.
  • the NAS RQI indicator is extracted from a SDAP header of the DL data packet.
  • FIG. 20 is a flow chart 2000 of a method (process) for enabling AS reflective QoS functionality.
  • the method may be performed by a UE (e.g., the AS reflective QoS component 194 of the UE 104, the UE 350, the UE 1110, the UE 1402, the apparatus 2302/2302’) .
  • the UE receives a DL data packet and determines a service data flow associated with the DL data packet.
  • the UE extracts from the DL data packet an AS RDI indicator that instructs the UE to map the QoS flow to the DRB.
  • the UE extracts from the DL data packet a QFI identifying a QoS flow associated with the received DL data packet.
  • the UE determines a DRB through which the DL data packet was received.
  • the UE determines whether the QoS flow is mapped to the determined DRB at the UE.
  • the UE generates a new AS mapping that maps the QoS flow to the DRB, in response to a determination that the QoS flow is not mapped to the DRB at the UE.
  • the UE maintains an old AS mapping, in response to a determination that the QoS flow is mapped to the DRB at the UE.
  • the UE removes an old AS mapping that maps the QoS flow to a different DRB, in response to a determination that the QoS flow is not mapped to the DRB at the UE.
  • the UE transmits, in accordance with the new AS mapping, an UL data packet associated with the service data flow through the DRB.
  • the AS RDI indicator is extracted from a SDAP header of the DL data packet.
  • the QFI indicator is extracted from the SDAP header of the DL data packet.
  • FIG. 21A-B are flow charts 2100 and 2120, respectively, of a method (process) performed by a QoS Flow Relocation component 196 of the UE 104, the UE 350, the UE 1110, the UE 1402, the apparatus 2302/2302’to guarantee in-sequence delivery of packets during QoS flow relocations.
  • the method may be performed by a UE (e.g., the UE 104, the UE 350, the UE 1110, the UE 1402, the apparatus 2302/2302’) .
  • the UE determines whether a QoS flow is remapped from a first DRB to a second DRB.
  • the UE sets, in a last data packet of the one or more data packets, an end marker indicating an end of packets associated with the QoS flow scheduled to be transmitted through the first DRB, in response to a determination that the one or more data packets remain to be transmitted through the first DRB.
  • the UE transmits the last data packet through the first DRB.
  • the UE determines whether a QoS flow is remapped from a first DRB to a second DRB.
  • the UE sets a start marker indicating a start of packets associated with the QoS flow scheduled to be transmitted through the second DRB in a first data packet associated with the QoS flow scheduled to be transmitted through the second DRB, in response to a determination that no more data packets associated with the QoS flow remain to be transmitted through the first DRB, or if the first DRB was released.
  • the UE transmits the first data packet through the second DRB.
  • the end marker is included in the SDAP header of the last data packet.
  • the start marker is included in the SDAP header of the last data packet.
  • the determination whether the QoS flow is remapped is made by receiving the QFI and AS RDI in the DL packets and by detecting that the DRB associated with the QoS flow has changed.
  • the determination whether the QoS flow is remapped is made by receiving a RRC message of Radio Bearer Configuration and by detecting that the DRB mapping provided in the RRC message is different from previous DRB mapping.
  • the UE receives a RRC message indicating the configuration of a radio bearer, the UE determines whether the QoS flow associated with the QoS flow associated with the DRB requires in-sequence delivery. The UE enables end marker mechanism if in-sequence delivery is required and disables the end marker mechanism otherwise.
  • FIGS. 22A-C are flow charts 2200, 2220 and 2230, respectively of a method (process) performed by a base station to guarantee in-sequence delivery of packets during QoS flow relocations.
  • the method may be performed by a base station (e.g., base station 102, base station 310, etc. ) .
  • the base station receives a first one or more data packets associated with a QoS flow through a first DRB.
  • the base station determines whether at least one of the first one or more data packets includes a data packet having an end marker indicating an end of packets associated with the QoS flow scheduled to be transmitted through the first DRB.
  • the base station sends the first one or more data packets to an upper layer.
  • the base station determines whether in-sequence delivery is required for a QoS flow.
  • the base station receives a first one or more data packets associated with a QoS flow through a first DRB and receives a second one or more data packets associated with the QoS flow through a second DRB.
  • the base station determines whether at least one of the first one or more data packets includes a data packet having an end marker indicating an end of packets associated with the QoS flow scheduled to be transmitted through the first DRB.
  • the base station sends the second one or more data packets to an upper layer subsequent to the first one or more data packets being sent to the upper layer, in response to a determination that at least one of the first one or more data packets includes the data packet having the end marker.
  • the base station refrains from sending the second one or more data packets to the upper layer, in response to a determination that none of the first one or more data packets includes the data packet having the end marker.
  • the base station determines whether in-sequence delivery is required for a QoS flow.
  • the base station receives a first one or more data packets associated with a QoS flow through a first DRB and receives a second one or more data packets associated with the QoS flow through a second DRB.
  • the base station determines whether at least one of the first one or more data packets includes a data packet having an end marker indicating an end of packets associated with the QoS flow scheduled to be transmitted through the first DRB.
  • the base station sends the second one or more data packets to an upper layer subsequent to the first one or more data packets being sent to the upper layer, in response to a determination that at least one of the first one or more data packets includes the data packet having the end marker.
  • the base station refrains from sending the second one or more data packets to the upper layer, in response to a determination that none of the first one or more data packets includes the data packet having the end marker.
  • the base station determines whether at least one of the second one or more data packets includes a data packet having a start marker indicating a start of packets associated with the QoS flow scheduled to be transmitted through the second DRB, in response to a determination that none of the first one or more data packets includes the data packet having the end marker.
  • the base station stops the refraining and sends the second one or more data packets to the upper layer subsequent to the first one or more data packets being sent to the upper layer, in response to a determination that at least one of the second one or more data packets includes the data packet having the start marker.
  • the determination whether the at least one of the second one or more data packets includes a data packet having the start marker includes detecting the start marker in a SDAP header of the at least one of the second one or more data packets.
  • the determination whether the at least one of the first one or more data packets includes a data packet having the end marker includes detecting the end marker in the SDAP header of the at least one of the first one or more data packets
  • FIG. 23 is a conceptual data flow diagram 2300 illustrating the data flow between different components/means in an exemplary apparatus 2302.
  • the apparatus 2302 may be either a UE.
  • the apparatus 2302 includes a reception component 2304, a NAS Reflective QoS component 2306, an AS Reflective QoS component 2312, a QoS flow relocation component 2308 and a transmission component 2310.
  • the reception component 2304 may receive signals 2362 from a base station 2350 and the transmission component 2310 may send signals 2364 to the base station 2350.
  • the NAS reflective QoS component 2306 is pre-configured to enable NAS reflective QoS functionality. In other words, the NAS reflective QoS component 2306 is pre-configured to determine which QoS rules to apply on DL traffic, and configured to reflect the DL QoS rules to the associated UL traffic.
  • the NAS reflective QoS component 2306 receives a DL data packet 2322 and determines a service data flow associated with the DL data packet 2322.
  • the DL data packet 2322 includes the QFI and may include a NAS RQI indicator.
  • the NAS reflective QoS component 2306 extracts from the DL data packet 2322 a QFI and extracts a NAS RQI indicator (if present) that instructs the NAS reflective QoS component 2306 to map the service protocol flow to the QoS flow.
  • the NAS reflective QoS component 2306 determines whether the service data flow is mapped to the QoS flow.
  • the NAS reflective QoS component 2306 generates a new NAS mapping that maps the service data flow to the QoS flow, in response to a determination that the service data flow is not mapped to the QoS flow at the UE.
  • the NAS reflective QoS component 2306 maintains an old NAS mapping, in response to a determination that the service data flow is mapped to the QoS flow at the UE.
  • the NAS reflective QoS component 2306 removes an old NAS mapping that maps the service data flow to a different QoS flow, in response to a determination that the service data flow is not mapped to the QoS flow at the UE.
  • the NAS reflective QoS component 2306 sends to the transmission component 2310 an UL data packet 2324 associated with the QoS flow in accordance with the new NAS mapping.
  • QoS rules of the UL data packet is identical to the QoS rules of the corresponding DL data packet 2322, if the DL data packet 2322 included a set NAS RQI indicator.
  • the NAS RQI indicator may be included in a SDAP header of the DL data packet 2322.
  • the AS Reflective QoS component 2312 is pre-configured to enable AS reflective QoS functionality. In other words, the AS Reflective QoS component 2312 is pre-configured to control QoS flow to DRB mapping by downlink traffic implicitly.
  • the AS reflective QoS component 2312 receives a DL data packet 2322 and determines a service data flow associated with the DL data packet 2322.
  • the AS Reflective QoS component 2312 extracts from the DL data packet 2322 a QFI and an AS RDI indicator (if present) that instructs the AS Reflective QoS component 2312 to map the QoS flow to the DRB.
  • the AS Reflective QoS component 2312 determines a DRB through which the DL data packet 2322 was received.
  • the AS Reflective QoS component 2312 determines whether the QoS flow is mapped to the determined DRB at the UE.
  • the AS Reflective QoS component 2312 generates a new AS mapping that maps the QoS flow to the DRB, in response to a determination that the QoS flow is not mapped to the DRB at the UE.
  • the AS Reflective QoS component 2312 maintains an old AS mapping, in response to a determination that the QoS flow is mapped to the DRB at the UE.
  • the AS Reflective QoS component 2312 removes an old AS mapping that maps the QoS flow to a different DRB, in response to a determination that the QoS flow is not mapped to the DRB at the UE.
  • the AS Reflective QoS component 2312 sends to the transmission component 2310 an UL data packet 2324 associated with the QoS flow in accordance with the new AS mapping.
  • the AS Reflective QoS component 2312 indicates to the transmission component which DRB to use to transmit the UL data packet 2324, if the DL data packet 2322 included a set AS RDI indicator.
  • the QFI and the AS RDI indicator are extracted from a SDAP header of the DL data packet 2322.
  • the QoS Flow Relocation component 2308 is pre-configured to guarantee in-sequence delivery of packets during QoS flow relocations.
  • the QoS Flow Relocation component 2308 determines whether a QoS flow is remapped from a first DRB to a second DRB.
  • the AS Reflective QoS component 2312 indicates to the QoS Flow Relocation Component 2308 that QoS flow relocation occurred when the AS Reflective QoS component 2312 receives the QFI and AS RDI in the DL packets 2322 and when the AS Reflective QoS component 2312 detects that the DRB associated with the QoS flow has changed.
  • the determination whether the QoS flow is remapped is made by the QoS Flow Relocation Component 2308 when it receives a RRC message 2326 and detects that the DRB mapping provided in the RRC message 2326 is different from previous DRB mapping.
  • the QoS Flow Relocation Component 2308 determines whether one or more UL data packets 2324 associated with the QoS flow remain to be transmitted through the first DRB, in response to a determination that the QoS flow is remapped from the first DRB to the second DRB.
  • the QoS Flow Relocation Component 2308 sets, in a last data packet of the one or more UL data packets 2324, an end marker indicating an end of packets associated with the QoS flow scheduled to be transmitted through the first DRB, in response to a determination that the one or more data packets remain to be transmitted through the first DRB.
  • the QoS Flow Relocation Component 2308 indicates to the transmission component 2310 to transmit the last UL data packet 2324 through the first DRB.
  • the QoS Flow Relocation Component 2308 sets a start marker indicating a start of packets associated with the QoS flow scheduled to be transmitted through the second DRB in a first data packet associated with the QoS flow scheduled to be transmitted through the second DRB, in response to a determination that no more data packets associated with the QoS flow remain to be transmitted through the first DRB, or if the first DRB was released.
  • the QoS Flow Relocation Component 2308 indicates to the transmission component 2310 to transmit the first UL data packet 2324 through the second DRB.
  • the end marker and the start marker are included in the SDAP header of the last/first data packet associated with corresponding DRBs.
  • FIG. 24 is a diagram 2400 illustrating an example of a hardware implementation for an apparatus 2302’employing a processing system 2414.
  • the apparatus 2302’ may be a UE.
  • the processing system 2414 may be implemented with a bus architecture, represented generally by a bus 2424.
  • the bus 2424 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 2414 and the overall design constraints.
  • the bus 2424 links together various circuits including one or more processors and/or hardware components, represented by one or more processors 2404, the reception component 2304, the NAS Reflective QoS component 2306, the AS Reflective QoS component 2312, the QoS flow relocation component 2308, the transmission component 2310, and a computer-readable medium /memory 2406.
  • the bus 2424 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, etc.
  • the processing system 2414 may be coupled to a transceiver 2410, which may be one or more of the transceivers 354.
  • the transceiver 2410 is coupled to one or more antennas 2420, which may be the communication antennas 352.
  • the transceiver 2410 provides a means for communicating with various other apparatus over a transmission medium.
  • the transceiver 2410 receives a signal from the one or more antennas 2420, extracts information from the received signal, and provides the extracted information to the processing system 2414, specifically the reception component 2304.
  • the transceiver 2410 receives information from the processing system 2414, specifically the transmission component 2310, and based on the received information, generates a signal to be applied to the one or more antennas 2420.
  • the processing system 2414 includes one or more processors 2404 coupled to a computer-readable medium /memory 2406.
  • the one or more processors 2404 are responsible for general processing, including the execution of software stored on the computer-readable medium /memory 2406.
  • the software when executed by the one or more processors 2404, causes the processing system 2414 to perform the various functions described supra for any particular apparatus.
  • the computer-readable medium /memory 2406 may also be used for storing data that is manipulated by the one or more processors 2404 when executing software.
  • the processing system 2414 further includes at least one of the reception component 2304, the NAS Reflective QoS component 2306, the AS Reflective QoS component 2312, the QoS flow relocation component 2308 and the transmission component 2310.
  • the components may be software components running in the one or more processors 2404, resident/stored in the computer readable medium /memory 2406, one or more hardware components coupled to the one or more processors 2404, or some combination thereof.
  • the processing system 2414 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the communication processor 359.
  • the apparatus 2302/apparatus 2302’for wireless communication includes means for performing each of the operations of FIGS. 19-22.
  • the aforementioned means may be one or more of the aforementioned components of the apparatus 2302 and/or the processing system 2414 of the apparatus 2302’configured to perform the functions recited by the aforementioned means.
  • the processing system 2314 may include the TX Processor 368, the RX Processor 356, and the communication processor 359.
  • the aforementioned means may be the TX Processor 368, the RX Processor 356, and the communication processor 359 configured to perform the functions recited by the aforementioned means.
  • the specific order or hierarchy of blocks in the processes /flowcharts disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes /flowcharts may be rearranged. Further, some blocks may be combined or omitted.
  • the accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
  • Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C.
  • combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un aspect de l'invention concerne un appareil. L'appareil reçoit un paquet de données de liaison descendante et détermine un flux de données de service associé au paquet de données de liaison descendante. L'appareil extrait, du paquet de données de liaison descendante, un indicateur d'indication de QoS réflective (RQI) hors strate d'accès (NAS) qui donne pour instruction à l'UE d'associer un flux de données de service au flux de QoS. L'appareil extrait en outre, du paquet de données de liaison descendante, un identifiant de flux de qualité de service (QoS) identifiant un flux de QoS. L'appareil génère un premier mappage de NAS qui associe le flux de données de service au flux de QoS, en réaction à une détermination selon laquelle le flux de données de service n'est pas associé au flux de QoS au niveau de l'appareil. L'appareil émet en outre, selon le premier mappage de NAS, un paquet de données de liaison montante associé au flux de données de service par l'intermédiaire du flux de QoS.
PCT/CN2018/085893 2017-05-05 2018-05-07 Utilisation d'en-tête sdap pour la gestion de qos réflective as/nas et pour garantir une distribution dans l'ordre de paquets pendant la réaffectation dans des systèmes de communication 5g WO2018202205A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18793837.8A EP3613225A4 (fr) 2017-05-05 2018-05-07 Utilisation d'en-tête sdap pour la gestion de qos réflective as/nas et pour garantir une distribution dans l'ordre de paquets pendant la réaffectation dans des systèmes de communication 5g
CN201880004369.6A CN109952773A (zh) 2017-05-05 2018-05-07 使用sdap报头处理as/nas反射qos并确保在5g通信系统中重映射期间顺序传送分组

Applications Claiming Priority (14)

Application Number Priority Date Filing Date Title
US201762501917P 2017-05-05 2017-05-05
US62/501,917 2017-05-05
US201762544107P 2017-08-11 2017-08-11
US62/544,107 2017-08-11
US201762564383P 2017-09-28 2017-09-28
US201762564388P 2017-09-28 2017-09-28
US62/564,388 2017-09-28
US62/564,383 2017-09-28
US201762565232P 2017-09-29 2017-09-29
US201762565234P 2017-09-29 2017-09-29
US62/565,232 2017-09-29
US62/565,234 2017-09-29
US15/971,093 2018-05-04
US15/971,093 US20180324631A1 (en) 2017-05-05 2018-05-04 Using sdap headers for handling of as/nas reflective qos and to ensure in-sequence packet delivery during remapping in 5g communication systems

Publications (1)

Publication Number Publication Date
WO2018202205A1 true WO2018202205A1 (fr) 2018-11-08

Family

ID=64015839

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085893 WO2018202205A1 (fr) 2017-05-05 2018-05-07 Utilisation d'en-tête sdap pour la gestion de qos réflective as/nas et pour garantir une distribution dans l'ordre de paquets pendant la réaffectation dans des systèmes de communication 5g

Country Status (3)

Country Link
EP (1) EP3613225A4 (fr)
CN (1) CN109952773A (fr)
WO (1) WO2018202205A1 (fr)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20180123345A (ko) * 2017-05-08 2018-11-16 삼성전자주식회사 이동 통신 시스템에서의 QoS(Quality Of Service) Flow의 설정 방법 및 장치
CN110267286A (zh) * 2019-07-01 2019-09-20 京信通信系统（中国）有限公司 数据传输方法、装置、接入网设备和存储介质
CN110475286A (zh) * 2018-05-09 2019-11-19 电信科学技术研究院有限公司 一种数据包丢弃管理方法、设备及装置、介质
WO2019246420A1 (fr) * 2018-06-21 2019-12-26 Qualcomm Incorporated Remappage de flux de qualité de service parmi des porteuses radio de données
EP3668259A1 (fr) * 2018-12-12 2020-06-17 Samsung Electronics Co., Ltd. Appareil et procédé pour fournir un réseau de service dans un système de communication sans fil
WO2020148159A1 (fr) * 2019-01-15 2020-07-23 Sony Corporation Équipement d'infrastructure, réseaux de communications sans fil et procédés
CN112188555A (zh) * 2019-07-02 2021-01-05 大唐移动通信设备有限公司 一种业务数据适配层实体的管理方法、发送端及接收端
US11025520B2 (en) * 2019-06-28 2021-06-01 Intel Corporation Quality-of-service in cellular information centric network
WO2022143399A1 (fr) * 2020-12-31 2022-07-07 Telefonaktiebolaget Lm Ericsson (Publ) Dispositif terminal, nœud de réseau et procédés destinés à y être effectués permettant la dérivation de la règle qos
WO2022180104A1 (fr) * 2021-02-25 2022-09-01 Telefonaktiebolaget Lm Ericsson (Publ) Gestion adaptative de transfert de paquets de données
WO2023096724A1 (fr) * 2021-11-24 2023-06-01 Apple Inc. Tramage de paquets pour transmission d'unité de données d'application
WO2023192303A1 (fr) * 2022-03-28 2023-10-05 Interdigital Patent Holdings, Inc. Système et procédés pour prendre en charge un flux et un profil de qos auto-adaptatifs
WO2023231499A1 (fr) * 2022-05-31 2023-12-07 华为技术有限公司 Procédé de qualité de service réfléchissant, et appareil
WO2024061475A1 (fr) * 2022-09-20 2024-03-28 Lenovo (Singapore) Pte. Ltd Qualité de service de supports de réalité étendue sur un réseau de communication sans fil

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536263A (zh) * 2019-07-11 2019-12-03 中兴通讯股份有限公司 一种数据传输方法、装置、第一通信节点及第二通信节点
CN112243270A (zh) * 2019-07-19 2021-01-19 中国移动通信有限公司研究院 一种数据包的传输方法、装置和计算机可读存储介质
CN110677889B (zh) * 2019-09-24 2021-11-23 京信网络系统股份有限公司 数据传输方法、装置、接入网设备和可读存储介质
CN112584334B (zh) * 2019-09-27 2022-04-12 维沃移动通信有限公司 一种乱序递交功能指示方法、控制方法及相关设备
CN111163017B (zh) * 2019-12-30 2023-10-24 京信网络系统股份有限公司 数据传输方法、装置、基站设备和计算机可读存储介质
CN115066975B (zh) * 2020-01-28 2023-10-31 哲库科技(上海)有限公司 使用集成电路的层2下行数据在线处理
WO2021159229A1 (fr) * 2020-02-10 2021-08-19 Mediatek Singapore Pte. Ltd. Procédés et appareil d'établissement d'une porteuse radio de multidiffusion pour services de diffusion et de multidiffusion nr
CN113630726B (zh) * 2020-05-07 2022-07-29 大唐移动通信设备有限公司 Mbms业务处理方法、基站、用户终端及存储介质
CN115696631A (zh) * 2021-07-30 2023-02-03 华为技术有限公司 通信方法及相关装置
CN115701727A (zh) * 2021-08-02 2023-02-10 华为技术有限公司 数据传输方法、电子设备、芯片和存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015028924A2 (fr) * 2013-08-29 2015-03-05 Telefonaktiebolaget L M Ericsson (Publ) Prise en charge de modèle qos basé sur une porteuse 3gpp, sur un réseau wifi
CN104683956A (zh) * 2013-11-27 2015-06-03 普天信息技术研究院有限公司 QoS控制方法和系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015028924A2 (fr) * 2013-08-29 2015-03-05 Telefonaktiebolaget L M Ericsson (Publ) Prise en charge de modèle qos basé sur une porteuse 3gpp, sur un réseau wifi
CN104683956A (zh) * 2013-11-27 2015-06-03 普天信息技术研究院有限公司 QoS控制方法和系统

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
3GPP S2-170802
HUAWEI ET AL.: "QoS Flow to DRB Mapping", 3GPP TSG-RAN2 MEETING # 97, R2-1701205, REVISION OF R2-1700088, 17 February 2017 (2017-02-17), pages 3 - 5, XP051223422 *
INTEL CORPORATION: "Considerations on RAN3 impacts from QoS flow framework", 3GPP TSG RAN WG3 MEETING #95BIS, R3-171070, 7 April 2017 (2017-04-07), pages 1 - 3, XP051255147 *
See also references of EP3613225A4 *

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20180123345A (ko) * 2017-05-08 2018-11-16 삼성전자주식회사 이동 통신 시스템에서의 QoS(Quality Of Service) Flow의 설정 방법 및 장치
EP3603170A4 (fr) * 2017-05-08 2020-04-15 Samsung Electronics Co., Ltd. Procédé et appareil de configuration de flux de qualité de service (qos) dans un système de communication sans fil
KR102355678B1 (ko) 2017-05-08 2022-01-26 삼성전자 주식회사 이동 통신 시스템에서의 QoS(Quality Of Service) Flow의 설정 방법 및 장치
US11218902B2 (en) 2017-05-08 2022-01-04 Samsung Electronics Co., Ltd Method and apparatus for configuring QoS flow in wireless communication system
CN110475286A (zh) * 2018-05-09 2019-11-19 电信科学技术研究院有限公司 一种数据包丢弃管理方法、设备及装置、介质
EP4340531A3 (fr) * 2018-06-21 2024-03-27 QUALCOMM Incorporated Remappage de flux de qualité de service parmi des porteuses radio de données
WO2019246420A1 (fr) * 2018-06-21 2019-12-26 Qualcomm Incorporated Remappage de flux de qualité de service parmi des porteuses radio de données
US10904795B2 (en) 2018-06-21 2021-01-26 Qualcomm Incorporated Remapping quality of service flows among data radio bearers
EP3668259A1 (fr) * 2018-12-12 2020-06-17 Samsung Electronics Co., Ltd. Appareil et procédé pour fournir un réseau de service dans un système de communication sans fil
CN111314956A (zh) * 2018-12-12 2020-06-19 三星电子株式会社 用于在无线通信系统中提供服务网络的装置和方法
US11006313B2 (en) 2018-12-12 2021-05-11 Samsung Electronics Co., Ltd. Apparatus and method for providing service network in wireless communication system
CN113273242A (zh) * 2019-01-15 2021-08-17 索尼集团公司 基础设施设备、无线通信网络和方法
WO2020148159A1 (fr) * 2019-01-15 2020-07-23 Sony Corporation Équipement d'infrastructure, réseaux de communications sans fil et procédés
US11025520B2 (en) * 2019-06-28 2021-06-01 Intel Corporation Quality-of-service in cellular information centric network
US11570079B2 (en) 2019-06-28 2023-01-31 Intel Corporation Quality-of-service in cellular information centric network
CN110267286B (zh) * 2019-07-01 2023-06-23 京信网络系统股份有限公司 数据传输方法、装置、接入网设备和存储介质
CN110267286A (zh) * 2019-07-01 2019-09-20 京信通信系统（中国）有限公司 数据传输方法、装置、接入网设备和存储介质
CN112188555A (zh) * 2019-07-02 2021-01-05 大唐移动通信设备有限公司 一种业务数据适配层实体的管理方法、发送端及接收端
WO2022143399A1 (fr) * 2020-12-31 2022-07-07 Telefonaktiebolaget Lm Ericsson (Publ) Dispositif terminal, nœud de réseau et procédés destinés à y être effectués permettant la dérivation de la règle qos
WO2022180104A1 (fr) * 2021-02-25 2022-09-01 Telefonaktiebolaget Lm Ericsson (Publ) Gestion adaptative de transfert de paquets de données
WO2023096724A1 (fr) * 2021-11-24 2023-06-01 Apple Inc. Tramage de paquets pour transmission d'unité de données d'application
WO2023192303A1 (fr) * 2022-03-28 2023-10-05 Interdigital Patent Holdings, Inc. Système et procédés pour prendre en charge un flux et un profil de qos auto-adaptatifs
WO2023231499A1 (fr) * 2022-05-31 2023-12-07 华为技术有限公司 Procédé de qualité de service réfléchissant, et appareil
WO2024061475A1 (fr) * 2022-09-20 2024-03-28 Lenovo (Singapore) Pte. Ltd Qualité de service de supports de réalité étendue sur un réseau de communication sans fil

Also Published As

Publication number Publication date
CN109952773A (zh) 2019-06-28
EP3613225A1 (fr) 2020-02-26
EP3613225A4 (fr) 2020-06-24

Similar Documents

Publication Publication Date Title
TWI713378B (zh) 一種使用者設備的無線通訊方法及用於無線通訊的裝置
WO2018202205A1 (fr) Utilisation d'en-tête sdap pour la gestion de qos réflective as/nas et pour garantir une distribution dans l'ordre de paquets pendant la réaffectation dans des systèmes de communication 5g
US11611461B2 (en) On PDCCH DMRS mapping and coreset resource allocation
EP3620031B1 (fr) Relais dans un système de communication de dispositif à dispositif
AU2017310952B2 (en) Congestion control for LTE-V2V with decode-based channel busy ratio determination
EP3498021B1 (fr) Ordonnancement inter-porteuses pour communication v2x
US10779308B2 (en) Priority based resource selection in a device-to-device communication system
EP3406035B1 (fr) Commande de débit de communication relais de dispositif à dispositif
EP3363252B1 (fr) Système et procédé de communication dispositif à dispositif utilisant une communication de type machine évoluée
US20190124647A1 (en) Configuration and selection of pucch resource set
US20180317207A1 (en) Method of efficient downlink control information transmission
EP3571874B1 (fr) Procédés et appareil liés au suivi temporel dans des systèmes à porteuses multiples
EP3317993B1 (fr) Optimisation d'attribution d'ordonnancement pour des communications dispositif à dispositif
US20180227942A1 (en) Techniques of dci messages aggregation
US10469218B2 (en) Inter-cell interference mitigation for traffic according to priority
US20180270835A1 (en) Techniques of cross-link interference mitigation in flexible duplex
US11689267B2 (en) Aperiodic CSI triggering in scenarios with multiple PDCCHs
US10880886B2 (en) Determination of TA adjustment timing
US20180324688A1 (en) Resource sharing between pdcch and pdsch
US10873347B2 (en) Channel bit interleaver design for polar coding chain
CN116349212A (zh) 与拓扑标识符相关联的bap配置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18793837

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018793837

Country of ref document: EP

Effective date: 20191119