EP3569028A1 - Kontrollierte downlink-paketmarkierung - Google Patents

Kontrollierte downlink-paketmarkierung

Info

Publication number
EP3569028A1
EP3569028A1 EP17891962.7A EP17891962A EP3569028A1 EP 3569028 A1 EP3569028 A1 EP 3569028A1 EP 17891962 A EP17891962 A EP 17891962A EP 3569028 A1 EP3569028 A1 EP 3569028A1
Authority
EP
European Patent Office
Prior art keywords
quality
uplink
service
processor
correctly
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP17891962.7A
Other languages
English (en)
French (fr)
Other versions
EP3569028A4 (de
Inventor
Matti Laitila
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
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
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of EP3569028A1 publication Critical patent/EP3569028A1/de
Publication of EP3569028A4 publication Critical patent/EP3569028A4/de
Withdrawn legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0215Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control

Definitions

  • Embodiments of the invention generally relate to wireless or mobile communications networks, such as, but not limited to, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE- A), LTE-A Pro, and/or 5G radio access technology or new radio access technology (NR).
  • UMTS Universal Mobile Telecommunications System
  • UTRAN Long Term Evolution
  • E-UTRAN Long Term Evolution Evolved UTRAN
  • LTE-A LTE-Advanced
  • NR new radio access technology
  • Some embodiments may generally relate to quality of service (QoS) flow marking in radio access networks (RAN), such as 5G or NR systems.
  • QoS quality of service
  • Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network refers to a communications network including base stations, or Node Bs, and for example radio network controllers (RNC).
  • UTRAN allows for connectivity between the user equipment (UE) and the core network.
  • the RNC provides control functionalities for one or more Node Bs.
  • the RNC and its corresponding Node Bs are called the Radio Network Subsystem (RNS).
  • RNC Radio Network Subsystem
  • E-UTRAN enhanced UTRAN
  • no RNC exists and radio access functionality is provided by an evolved Node B (eNodeB or eNB) or many eNBs. Multiple eNBs are involved for a single UE connection, for example, in case of Coordinated Multipoint Transmission (CoMP) and in dual connectivity.
  • CoMP Coordinated Multipoint Transmission
  • LTE Long Term Evolution
  • E-UTRAN refers to improvements of the UMTS through improved efficiency and services, lower costs, and use of new spectrum opportunities.
  • LTE is a 3GPP standard that provides for uplink peak rates of at least, for example, 75 megabits per second (Mbps) per carrier and downlink peak rates of at least, for example, 300 Mbps per carrier.
  • LTE supports scalable carrier bandwidths from 20 MHz down to 1.4 MHz and supports both Frequency Division Duplexing (FDD) and Time Division Duplexing (TDD).
  • FDD Frequency Division Duplexing
  • TDD Time Division Duplexing
  • LTE may also improve spectral efficiency in networks, allowing carriers to provide more data and voice services over a given bandwidth. Therefore, LTE is designed to fulfill the needs for high-speed data and media transport in addition to high-capacity voice support. Advantages of LTE include, for example, high throughput, low latency, FDD and TDD support in the same platform, an improved end-user experience, and a simple architecture resulting in low operating costs.
  • LTE-A LTE- Advanced
  • LTE-A is directed toward extending and optimizing the 3GPP LTE radio access technologies.
  • a goal of LTE-A is to provide significantly enhanced services by means of higher data rates and lower latency with reduced cost.
  • LTE-A is a more optimized radio system fulfilling the international telecommunication union-radio (ITU-R) requirements for IMT-Advanced while maintaining backward compatibility.
  • ITU-R international telecommunication union-radio
  • 5G refers to the next generation (NG) of radio systems and network architecture.
  • 5G is expected to provide higher bitrates and coverage than the current LTE systems. Some estimate that 5G will provide bitrates one hundred times higher than LTE offers. 5G is also expected to increase network expandability up to hundreds of thousands of connections. The signal technology of 5G is anticipated to be improved for greater coverage as well as spectral and signaling efficiency. 5G is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life.
  • IoT Internet of Things
  • One embodiment is directed to a method that may include determining or verifying, by a core network node, whether a UE has configured UL filters correctly.
  • the core network node verifies that the UE has configured the UL filters correctly, indicating to RAN that a mapping of SDF to QoS flow is correct and/or that RAN does not need to include DL QoS flow IDs for NAS filter configuration.
  • the indicating may include setting reflective QoS bits of following packets to off.
  • the core network node determines that the UE has not configured UL filters correctly, setting a reflective QoS bit of DL packet to on.
  • Another embodiment is directed to an apparatus that may include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code configured, with the at least one processor, to cause the apparatus at least to determine or verify whether a UE has configured UL filters correctly.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to indicate to RAN that a mapping of SDF to QoS flow is correct and/or that RAN does not need to include DL QoS flow IDs for NAS filter configuration.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to indicate to RAN by setting reflective QoS bits of following packets to off.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to set a reflective QoS bit of DL packet to on.
  • Another embodiment is directed to an apparatus that may include deterrnining means for determining or verifying whether a UE has configured UL filters correctly.
  • the apparatus may include indicating means for indicating to RAN that a mapping of SDF to QoS flow is correct and/or that RAN does not need to include DL QoS flow IDs for NAS filter configuration.
  • the indicating means may include setting means for setting reflective QoS bits of following packets to off.
  • the apparatus includes setting means for setting a reflective QoS bit of DL packet to on.
  • Another embodiment is directed to a computer program embodied on a non-transitory computer readable medium.
  • the computer program is configured to control a processor to perform a process including deterrnining or verifying whether a UE has configured UL filters correctly.
  • a process including deterrnining or verifying whether a UE has configured UL filters correctly.
  • the indicating may include setting reflective QoS bits of following packets to off.
  • setting a reflective QoS bit of DL packet to on When it is determined that the UE has not configured UL filters correctly, setting a reflective QoS bit of DL packet to on.
  • Another embodiment is directed to a method that may include inspecting, by a RAN node, QoS flow IDs of the UL traffic received from UL DRBs. For QoS flows that are subject to reflective QoS, the method may include comparing the UL QoS flow ID to DRB binding to the DL mapping table of the QoS flow. If the comparison shows that UL and DL DRB is the same for a QoS flow, the method may include concluding that the UL filters are correctly configured, and stopping including the QoS flow ID in the DL packets for AS filter configuration purposes.
  • Another embodiment is directed to an apparatus that may include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code configured, with the at least one processor, to cause the apparatus at least to inspect QoS flow IDs of the UL traffic received from UL DRBs.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to compare the UL QoS flow ID to DRB binding to the DL mapping table of the QoS flow.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to conclude that the UL filters are correctly configured, and to stop including the QoS flow ID in the DL packets for AS filter configuration purposes.
  • Another embodiment is directed to an apparatus that includes inspecting means for inspecting QoS flow IDs of the UL traffic received from UL DRBs.
  • the apparatus may include comparing means for comparing the UL QoS flow ID to DRB binding to the DL mapping table of the QoS flow. If the comparing means shows that UL and DL DRB is the same for a QoS flow, the apparatus may include concluding means for concluding that the UL filters are correctly configured, and stopping including the QoS flow ID in the DL packets for AS filter configuration purposes.
  • Another embodiment is directed to a computer program embodied on a non-transitory computer readable medium.
  • the computer program is configured to control a processor to perform a process including inspecting QoS flow IDs of the UL traffic received from UL DRBs.
  • the process may include comparing the UL QoS flow ID to DRB binding to the DL mapping table of the QoS flow. If the comparison shows that UL and DL DRB is the same for a QoS flow, the process may include concluding that the UL filters are correctly configured, and stopping including the QoS flow ID in the DL packets for AS filter configuration purposes.
  • FIG. 1 illustrates an example of a DL DRB mapping table of a gNB, according to an embodiment
  • FIG. 2 illustrates an example of a DL SDF mapping table, according to an embodiment
  • FIG. 3a illustrates a block diagram of an apparatus, according to an embodiment
  • FIG. 3b illustrates a block diagram of an apparatus, according to another embodiment
  • FIG. 4a illustrates an example flow diagram of a method, according to an embodiment
  • Fig. 4b illustrates an example flow diagram of a method, according to another embodiment.
  • 3GPP has an ongoing study items for the 5G system architecture in SA2 and radio access network (RAN) protocols in RAN2 and RAN3.
  • QoS Quality of service
  • 3GPP has adopted, for 5G, the so -called "flow based" QoS frame work, where instead of dedicated end to end tunnels (bearers) for each QoS class, the core network (CN) in the downlink (DL) direction and the UE in the uplink (UL) direction map Service Data Flows (SDF) into packet based QoS flows. Every service data flow (SDF) that has the same QoS requirements are mapped to a same QoS flow and marked with the same QoS mark. On a RAN-CN leg, the QoS flows are delivered over a single transport connection (tunnel). For the radio interface, bearer based QoS has been adopted, where Data Radio Bearer (DRB) defines over the air packet treatment in the RAN.
  • DRB Data Radio Bearer
  • the two-level SDF to DRB mapping was agreed to in 3GPP technical report (TR) 23.799 and RAN2.
  • the SDFs are first mapped to the QoS flows and, in the second phase, QoS flows are mapped to the DRBs.
  • the mapping of the SDFs to the QoS flows is based on the "NAS" filters, which are located in a UE for UL traffic and in the core network user plane (CN-UP) for DL traffic.
  • the mapping of QoS flows to the DRBs is based on the "AS filters", which are located in a UE for UL traffic and in a RAN for DL traffic.
  • the two-level mapping means that the RAN has no visibility to user service packets.
  • SA2 has made an interim agreement on the usage of the reflective QoS for flow configuring UL SDF to QoS flow mapping (NAS filter) in a UE, and RAN2 has agreed that the reflective QoS can be used for AS filter configuration.
  • the reflective QoS is based on the fact that the application (and transport) protocols in practice always generate bidirectional flows.
  • the reflective QoS in the context of non-access stratum (NAS) filter configuration means that the UE maps the UL of a certain SDF to the same QoS flow as the DL was mapped to.
  • Reflective QoS in the access stratum (AS) filter configuration means that the UE maps the UL of a certain QoS flow to the same DRB as the DL was using.
  • RAN 2 Since reflective QoS necessitates that the QoS flow id needs to be included in DL packets over the air interface, RAN 2 has made following agreements: DL packets over Uu interface are marked inband with QOS-flow-id for the purposes of reflective QoS; and UL packets over Uu are marked inband with QOS-flow-id for the purposes of marking forwarded packets to the CN.
  • RAN2 has also realized that the inclusion of the QoS flow ID in every packet is a problem from the perspective of increased overhead, so RAN2 has agreed that further study should be made as to whether DL packets can be semi- statically configured to not include the QOS flow ID in some cases.
  • Certain embodiments rely on the fact that the single packet of a QoS flow received by the UE is enough for configuring UL filters on NAS and AS layers. However, it cannot be always guaranteed that the UE receives the (single) packet with the QoS flow ID - for example, in the case of RLC UM or UE for some reason may not able configure filters from the first packet - so the inclusion of QoS flow ID to multiple packets may be needed.
  • One embodiment introduces the CN assisted selective DL QoS flow marking concept in RAN.
  • An embodiment provides that, instead of including the QoS flow ID in every DL radio packet of a QoS flow subject to reflective QoS, the QoS flow ID is included only in the first packet(s) or until the network has verified that the UE has configured UL filters correctly.
  • verification for both NAS and AS filter configuration may be needed before the packets of a QoS flow can be sent without Qos flow IDs towards the UE.
  • the CN when the CN has verified that the UE has configured UL filters correctly, the CN indicates to RAN that the mapping is correct so that RAN can stop attaching the QoS flow IDs to DL packets for the sake of NAS filter configuration.
  • RAN being aware of the DL QoS flow ID to DRB mapping is able to verify the correct AS filter configuration by inspecting the UL traffic. After detecting that the UL DRB mapping made by the UE using reflective QoS is correct, RAN can stop including the QoS flow ID to DL packets for AS filter configuration by reflective manner.
  • RAN is not able to verify NAS level UL mapping by the UE since it has no visibility to the SDFs; thus, according to an embodiment, the CN verifies the correct mapping.
  • the CN after the CN has verified that the UE has configured UL filters correctly, the CN indicates to RAN that the mapping is correct so that RAN can stop attaching the flow IDs to DL packets for the sake of NAS filter configuration.
  • verification for both NAS and AS filter configuration may be needed before the packets of a QoS flow can be sent without Qos flow IDs towards the UE.
  • the RAN maintains a DRB mapping table for DL QoS flow to DRB mapping.
  • Fig. 1 illustrates an example of a DL DRB mapping table of a gNB, according to an embodiment.
  • RAN inspects QoS flow IDs of the UL traffic received from UL DRBs (which it must do anyways for transport QoS mapping).
  • RAN compares the UL QoS flow ID to DRB binding to the DL mapping table of the QoS flow. If UL and DL DRB is the same for a QoS flow, the UL filters can be considered to be correctly configured. Therefore, there is no need to include the QoS flow ID in the DL packets for AS filter configuration purposes anymore.
  • Fig. 2 illustrates an example of a DL SDF mapping table, according to an embodiment.
  • the CN-UP compares the SDF/QoS flow pair of the UL packets to the DL mapping table and verifies if the QoS flow is the same for the SDF in both directions. If they are the same, then the UE has correctly mapped the UL SDF to QoS flows.
  • the CN-UP may inform RAN about the correct UL NAS layer mapping by using the NG3 reflective QoS bit. For example, the CN-UP may set the reflective QoS bit of a DL packet on when the RAN should use the packet for the NAS UL filter configuration. After detecting that the NAS filter for a QoS flow are correctly configured, the CN sets the reflective QoS bits of the following packets off, which indicates to the RAN that the UE has correctly configured UL NAS filter for a QoS flow, and the inclusion of DL QoS flow IDs are no longer needed for NAS filter configuration.
  • Fig. 3a illustrates an example of an apparatus 10 according to an embodiment.
  • apparatus 10 may be a node, host, or server in a communications network or serving such a network.
  • apparatus 10 may be a core network node, such as a policy control function (PCF), access and mobility management function (AMF), session management function (SMF), subscriber data management function (SDM), mobility management entity (MME), subscription server or home subscription server (HSS) associated with a radio access network, such as a LTE network or 5G radio access technology.
  • PCF policy control function
  • AMF access and mobility management function
  • SMF session management function
  • SDM subscriber data management function
  • MME mobility management entity
  • HSS home subscription server
  • apparatus 10 may include components or features not shown in Fig. 3a.
  • apparatus 10 may include a processor 12 for processing information and executing instructions or operations.
  • processor 12 may be any type of general or specific purpose processor. While a single processor 12 is shown in Fig. 3a, multiple processors may be utilized according to other embodiments. In fact, processor 12 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples.
  • DSPs digital signal processors
  • FPGAs field-programmable gate arrays
  • ASICs application-specific integrated circuits
  • Processor 12 may perform functions associated with the operation of apparatus 10 which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.
  • Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12.
  • Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory.
  • memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non-transitory machine or computer readable media.
  • the instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.
  • apparatus 10 may also include or be coupled to one or more antennas 15 for transmitting and receiving signals and/or data to and from apparatus 10.
  • Apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and receive information.
  • the transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 15.
  • the radio interfaces may correspond to a plurality of radio access technologies including one or more of LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), and the like.
  • the radio interface may include components, such as filters, converters (for example, digital- to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink).
  • transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10.
  • transceiver 18 may be capable of transmitting and receiving signals or data directly.
  • memory 14 may store software modules that provide functionality when executed by processor 12.
  • the modules may include, for example, an operating system that provides operating system functionality for apparatus 10.
  • the memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10.
  • the components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.
  • apparatus 10 may be a network node, server, or network function for a core network. According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to perform the functions associated with embodiments described herein. In one embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to determine or verify whether a UE has configured UL filters correctly. When the apparatus 10 verifies that the UE has configured the UL filters correctly, apparatus 10 may be controlled by memory 14 and processor 12 to indicate to RAN that a mapping of SDF to QoS flow is correct and/or that RAN does not need to include DL QoS flow IDs for NAS filter configuration.
  • apparatus 10 may be controlled by memory 14 and processor 12 to indicate to RAN by setting reflective QoS bits of following packets to off.
  • apparatus 10 may be controlled by memory 14 and processor 12 to set a reflective QoS bit of DL packet to on.
  • apparatus 20 may be a server, node, host or element in a communications network or associated with such a network.
  • apparatus 20 may be a RAN node, such as a base station, access point, node B, eNB, gNB, WLAN access point, or the like.
  • apparatus 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, and the like), one or more radio access components (for example, a modem, a transceiver, and the like), and/or a user interface.
  • apparatus 20 may be configured to operate using one or more radio access technologies, such as LTE, LTE-A, 5G, WLAN, WiFi, Bluetooth, NFC, and any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 3b.
  • apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations.
  • processor 22 may be any type of general or specific purpose processor. While a single processor 22 is shown in Fig. 3b, multiple processors may be utilized according to other embodiments. In fact, processor 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application- specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples.
  • DSPs digital signal processors
  • FPGAs field-programmable gate arrays
  • ASICs application-specific integrated circuits
  • Processor 22 may perform functions associated with the operation of apparatus 20 including, without limitation, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.
  • Apparatus 20 may further include or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22.
  • Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory.
  • memory 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non-transitory machine or computer readable media.
  • the instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein.
  • apparatus 20 may also include or be coupled to one or more antennas 25 for receiving a downlink or signal and for transmitting via an uplink from apparatus 20.
  • Apparatus 20 may further include a transceiver 28 configured to transmit and receive information.
  • the transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25.
  • the radio interface may correspond to a plurality of radio access technologies including one or more of LTE, LTE-A, 5G, WLAN, Bluetooth, BT-LE, NFC, RFID, UWB, and the like.
  • the radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.
  • filters for example, digital-to-analog converters and the like
  • symbol demappers for example, digital-to-analog converters and the like
  • signal shaping components for example, an Inverse Fast Fourier Transform (IFFT) module, and the like
  • IFFT Inverse Fast Fourier Transform
  • transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20.
  • transceiver 28 may be capable of transmitting and receiving signals or data directly.
  • Apparatus 20 may further include a user interface, such as a graphical user interface or touchscreen.
  • memory 24 stores software modules that provide functionality when executed by processor 22.
  • the modules may include, for example, an operating system that provides operating system functionality for apparatus 20.
  • the memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20.
  • the components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software.
  • apparatus 20 may be a RAN node, for example. According to certain embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to perform the functions associated with embodiments described herein. In one embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to inspect QoS flow IDs of the UL traffic received from UL DRBs. For QoS flows that are subject to reflective QoS, apparatus 20 may be controlled by memory 24 and processor 22 to compare the UL QoS flow ID to DRB binding to the DL mapping table of the QoS flow.
  • apparatus 20 may conclude that the UL filters are correctly configured, and apparatus 20 may be controlled by memory 24 and processor 22 to stop including the QoS flow ID in the DL packets for AS filter configuration purposes.
  • Fig. 4a illustrates an example flow chart of a method, according to one embodiment.
  • the method of Fig. 4a may be performed by a core network node.
  • the method may include, at 400, determining or verifying whether a UE has configured UL filters correctly.
  • the core network node verifies that the UE has configured the UL filters correctly, indicating, at 410, to RAN that a mapping of SDF to QoS flow is correct and/or that RAN does not need to include DL QoS flow IDs for NAS filter configuration.
  • the indicating may include setting reflective QoS bits of following packets to off.
  • Fig. 4b illustrates an example flow chart of a method, according to one embodiment.
  • the method of Fig. 4b may be performed by a RAN node.
  • the method may include, at 450, inspecting QoS flow IDs of the UL traffic received from UL DRBs.
  • the method may include, at 460, comparing the UL QoS flow ID to DRB binding to the DL mapping table of the QoS flow.
  • the method may include, at 470, concluding that the UL filters are correctly configured, and stopping including the QoS flow ID in the DL packets for AS filter configuration purposes.
  • Embodiments described herein are capable of providing several technical improvements and/or advantages. For example, certain embodiments are able to reduce overhead by preventing the inclusion of QoS flow IDs in multiple packets. Accordingly, the use of embodiments of the invention results in the improved functioning and performance of communications networks and their nodes.
  • any of the methods, processes, signaling diagrams, or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and executed by a processor.
  • an apparatus may be, included or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of it (including an added or updated software routine), executed by at least one operation processor.
  • Programs also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and include program instructions to perform particular tasks.
  • a computer program product may comprise one or more computer- executable components which, when the program is run, are configured to carry out embodiments.
  • the one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of an embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.
  • Software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • the computer readable medium or computer readable storage medium may be a non-transitory medium.
  • the functionality may be performed by hardware, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software.
  • ASIC application specific integrated circuit
  • PGA programmable gate array
  • FPGA field programmable gate array
  • the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.
  • an apparatus such as a node, device, or a corresponding component, may be configured as a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.
  • a microprocessor such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP17891962.7A 2017-01-13 2017-12-27 Kontrollierte downlink-paketmarkierung Withdrawn EP3569028A4 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762445851P 2017-01-13 2017-01-13
PCT/FI2017/050938 WO2018130741A1 (en) 2017-01-13 2017-12-27 Controlled downlink packet marking

Publications (2)

Publication Number Publication Date
EP3569028A1 true EP3569028A1 (de) 2019-11-20
EP3569028A4 EP3569028A4 (de) 2020-11-25

Family

ID=62839777

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17891962.7A Withdrawn EP3569028A4 (de) 2017-01-13 2017-12-27 Kontrollierte downlink-paketmarkierung

Country Status (2)

Country Link
EP (1) EP3569028A4 (de)
WO (1) WO2018130741A1 (de)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112567699A (zh) 2018-08-13 2021-03-26 苹果公司 用于反射服务质量的分组过滤器的灵活范围
CN110062426B (zh) * 2019-04-02 2021-08-24 腾讯科技(深圳)有限公司 通信方法、装置、计算机可读介质及电子设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140233380A1 (en) * 2011-10-27 2014-08-21 Lg Electronics Inc. Method and apparatus for managing quality of service of uplink in wireless communication system
CN102612096B (zh) * 2012-03-06 2014-10-29 电信科学技术研究院 一种ip数据包的传输方法和设备
US9521679B2 (en) * 2014-03-06 2016-12-13 Cisco Technology, Inc. Systems and methods for implementing reflective EPS bearers to ensure uplink quality of service

Also Published As

Publication number Publication date
EP3569028A4 (de) 2020-11-25
WO2018130741A1 (en) 2018-07-19

Similar Documents

Publication Publication Date Title
US20210267015A1 (en) Uu interface enhancement for nr v2x
US12022503B2 (en) Sidelink bearer mode selection
US20220039140A1 (en) Control Channel Repetition Using Multiple Coresets
US20220046661A1 (en) Resource Configuration for Non-Connected State
EP3516819B1 (de) Schlüsselsatzidentifikator der nächsten generation
US20180049046A1 (en) Apparatus and method of signalling support for reduced latency operation
US11558159B2 (en) Configurable set of overloaded downlink control information fields used for demodulation reference signal bundling
US11622323B2 (en) Slice allocation and interface to applications
US10511993B2 (en) Buffer status reporting and new quality of service flows on default bearer in next generation radio access networks
US11218891B2 (en) Enhanced radio link monitoring for user equipment
KR20230050324A (ko) 사이드링크 캐리어 어그리게이션 셋업, 활성화 및 비활성화
EP4270851A2 (de) Automatische verstärkungsregelung für sidelink-kommunikationen
US10581495B2 (en) Physical layer configuration continuity during radio resource control restoration
WO2018202941A1 (en) Providing security information
US11576163B2 (en) Parameter overwriting rules for multiple SPS/CG configurations
CN114270884A (zh) 5g广播/多播安全性密钥刷新
KR20220167372A (ko) 시간 영역 리소스 할당-기반 harq-ack 피드백 생성
EP3569028A1 (de) Kontrollierte downlink-paketmarkierung
JP2022536534A (ja) 切捨て識別インジケータ
CA3194633A1 (en) Listen-before-talk result indication in wireless communications
WO2018029596A1 (en) Control plane architecture for lte-nr tight interworking
US20230354374A1 (en) Sidelink Control Information Communication
US20240155656A1 (en) Channel Access Priority Class for Multi-Consecutive Slots Sidelink Transmissions
US11363487B2 (en) Methods and apparatuses for quality of service flow relocation handling

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20190813

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20201027

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 28/02 20090101ALI20201021BHEP

Ipc: H04L 12/24 20060101ALI20201021BHEP

Ipc: H04W 72/12 20090101AFI20201021BHEP

Ipc: H04W 28/24 20090101ALI20201021BHEP

Ipc: H04W 76/12 20180101ALI20201021BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20210526