WO2020159178A1 - Gestion de défaillance de vérification d'intégrité - Google Patents

Gestion de défaillance de vérification d'intégrité Download PDF

Info

Publication number
WO2020159178A1
WO2020159178A1 PCT/KR2020/001257 KR2020001257W WO2020159178A1 WO 2020159178 A1 WO2020159178 A1 WO 2020159178A1 KR 2020001257 W KR2020001257 W KR 2020001257W WO 2020159178 A1 WO2020159178 A1 WO 2020159178A1
Authority
WO
WIPO (PCT)
Prior art keywords
data unit
integrity verification
receiving side
rlc
entity
Prior art date
Application number
PCT/KR2020/001257
Other languages
English (en)
Inventor
Taehun Kim
Bokyung BYUN
Geumsan JO
Original Assignee
Lg Electronics 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
Application filed by Lg Electronics Inc. filed Critical Lg Electronics Inc.
Publication of WO2020159178A1 publication Critical patent/WO2020159178A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present disclosure relates to handling integrity verification failure.
  • 3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communications.
  • 3GPP 3rd generation partnership project
  • LTE long-term evolution
  • Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity.
  • the 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.
  • ITU international telecommunication union
  • NR new radio
  • 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU radio communication sector (ITU-R) international mobile telecommunications (IMT)-2020 process.
  • ITU-R ITU radio communication sector
  • IMT international mobile telecommunications
  • the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.
  • the NR targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), etc.
  • eMBB enhanced mobile broadband
  • mMTC massive machine-type-communications
  • URLLC ultra-reliable and low latency communications
  • the NR shall be inherently forward compatible.
  • Integrity protection ensures that the intruder cannot replay or modify signaling messages that the mobile and network exchange. It protects the system against problems such as man-in-middle attacks, in which an intruder intercepts a sequence of signaling messages and modifies and re-transmits them, in an attempt to take control of the mobile.
  • integrity protection is only applied to signaling radio bearer (SRB).
  • integrity protection can also be applied to data radio bearer (DRB) as well as signaling radio bearer (SRB). Since the DRB has less importance than the SRB, the DRB for which integrity protection fails can be simply discarded. This mechanism can also be applied for the SRB, but some issues should be addressed.
  • a method for a receiving side in a wireless communication system includes receiving, from a transmitting side, a first data unit with a specific indication, perform integrity verification on a second data unit which is based on the first data unit with the specific indication, and transmitting, to the transmitting side, a positive acknowledgement as a response to the first data unit based on a successful integrity verification on the second data unit.
  • an apparatus for implementing the above method is provided.
  • the present disclosure can have various advantageous effects.
  • efficient signaling procedure can be provided for packets required for more than functional verification of more than two layers.
  • FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.
  • FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.
  • FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.
  • FIG. 4 shows another example of wireless devices to which implementations of the present disclosure is applied.
  • FIG. 5 shows an example of UE to which implementations of the present disclosure is applied.
  • FIGs. 6 and 7 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.
  • FIG. 8 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.
  • FIG. 9 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.
  • FIG. 10 shows an example of PDSCH time domain resource allocation by PDCCH to which implementations of the present disclosure is applied.
  • FIG. 11 shows an example of PUSCH time resource allocation by PDCCH to which implementations of the present disclosure is applied.
  • FIG. 12 shows an example of physical layer processing at a transmitting side to which implementations of the present disclosure is applied.
  • FIG. 13 shows an example of physical layer processing at a receiving side to which implementations of the present disclosure is applied.
  • FIG. 14 shows an example of a method for performing an integrity protection verification according to implementations of the present disclosure.
  • FIG. 15 shows an example of a method for a transmitting side according to implementations of the present disclosure.
  • FIG. 16 shows an example of a method for a receiving side according to implementations of the present disclosure.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • MC-FDMA multicarrier frequency division multiple access
  • CDMA may be embodied through radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
  • TDMA may be embodied through radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE).
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • EDGE enhanced data rates for GSM evolution
  • OFDMA may be embodied through radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA).
  • IEEE institute of electrical and electronics engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • E-UTRA evolved UTRA
  • UTRA is a part of a universal mobile telecommunications system (UMTS).
  • 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA.
  • 3GPP LTE employs OFDMA in DL and SC-FDMA in UL.
  • LTE-advanced (LTE-A) is an evolved version of 3GPP LTE.
  • implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system.
  • the technical features of the present disclosure are not limited thereto.
  • the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.
  • a or B may mean “only A”, “only B”, or “both A and B”.
  • a or B in the present disclosure may be interpreted as “A and/or B”.
  • A, B or C in the present disclosure may mean “only A”, “only B”, “only C”, or "any combination of A, B and C”.
  • slash (/) or comma (,) may mean “and/or”.
  • A/B may mean “A and/or B”.
  • A/B may mean "only A”, “only B”, or “both A and B”.
  • A, B, C may mean "A, B or C”.
  • At least one of A and B may mean “only A”, “only B” or “both A and B”.
  • the expression “at least one of A or B” or “at least one of A and/or B” in the present disclosure may be interpreted as same as “at least one of A and B”.
  • At least one of A, B and C may mean “only A”, “only B”, “only C”, or “any combination of A, B and C”.
  • at least one of A, B or C or “at least one of A, B and/or C” may mean “at least one of A, B and C”.
  • parentheses used in the present disclosure may mean “for example”.
  • control information PDCCH
  • PDCCH PDCCH
  • PDCCH PDCCH
  • FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.
  • the 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1.
  • Three main requirement categories for 5G include (1) a category of enhanced mobile broadband (eMBB), (2) a category of massive machine type communication (mMTC), and (3) a category of ultra-reliable and low latency communications (URLLC).
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC ultra-reliable and low latency communications
  • Partial use cases may require a plurality of categories for optimization and other use cases may focus only upon one key performance indicator (KPI).
  • KPI key performance indicator
  • eMBB far surpasses basic mobile Internet access and covers abundant bidirectional work and media and entertainment applications in cloud and augmented reality.
  • Data is one of 5G core motive forces and, in a 5G era, a dedicated voice service may not be provided for the first time.
  • voice will be simply processed as an application program using data connection provided by a communication system.
  • Main causes for increased traffic volume are due to an increase in the size of content and an increase in the number of applications requiring high data transmission rate.
  • a streaming service (of audio and video), conversational video, and mobile Internet access will be more widely used as more devices are connected to the Internet.
  • Cloud storage and applications are rapidly increasing in a mobile communication platform and may be applied to both work and entertainment.
  • the cloud storage is a special use case which accelerates growth of uplink data transmission rate.
  • 5G is also used for remote work of cloud. When a tactile interface is used, 5G demands much lower end-to-end latency to maintain user good experience.
  • Entertainment for example, cloud gaming and video streaming, is another core element which increases demand for mobile broadband capability. Entertainment is essential for a smartphone and a tablet in any place including high mobility environments such as a train, a vehicle, and an airplane.
  • Other use cases are augmented reality for entertainment and information search. In this case, the augmented reality requires very low latency and instantaneous data volume.
  • one of the most expected 5G use cases relates a function capable of smoothly connecting embedded sensors in all fields, i.e., mMTC. It is expected that the number of potential Internet-of-things (IoT) devices will reach 204 hundred million up to the year of 2020.
  • An industrial IoT is one of categories of performing a main role enabling a smart city, asset tracking, smart utility, agriculture, and security infrastructure through 5G.
  • URLLC includes a new service that will change industry through remote control of main infrastructure and an ultra-reliable/available low-latency link such as a self-driving vehicle.
  • a level of reliability and latency is essential to control a smart grid, automatize industry, achieve robotics, and control and adjust a drone.
  • 5G is a means of providing streaming evaluated as a few hundred megabits per second to gigabits per second and may complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such fast speed is needed to deliver TV in resolution of 4K or more (6K, 8K, and more), as well as virtual reality and augmented reality.
  • Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games.
  • a specific application program may require a special network configuration. For example, for VR games, gaming companies need to incorporate a core server into an edge network server of a network operator in order to minimize latency.
  • Automotive is expected to be a new important motivated force in 5G together with many use cases for mobile communication for vehicles. For example, entertainment for passengers requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect connection of high quality regardless of their locations and speeds.
  • Another use case of an automotive field is an AR dashboard.
  • the AR dashboard causes a driver to identify an object in the dark in addition to an object seen from a front window and displays a distance from the object and a movement of the object by overlapping information talking to the driver.
  • a wireless module enables communication between vehicles, information exchange between a vehicle and supporting infrastructure, and information exchange between a vehicle and other connected devices (e.g., devices accompanied by a pedestrian).
  • a safety system guides alternative courses of a behavior so that a driver may drive more safely drive, thereby lowering the danger of an accident.
  • the next stage will be a remotely controlled or self-driven vehicle. This requires very high reliability and very fast communication between different self-driven vehicles and between a vehicle and infrastructure. In the future, a self-driven vehicle will perform all driving activities and a driver will focus only upon abnormal traffic that the vehicle cannot identify.
  • Technical requirements of a self-driven vehicle demand ultra-low latency and ultra-high reliability so that traffic safety is increased to a level that cannot be achieved by human being.
  • a smart city and a smart home/building mentioned as a smart society will be embedded in a high-density wireless sensor network.
  • a distributed network of an intelligent sensor will identify conditions for costs and energy-efficient maintenance of a city or a home. Similar configurations may be performed for respective households. All of temperature sensors, window and heating controllers, burglar alarms, and home appliances are wirelessly connected. Many of these sensors are typically low in data transmission rate, power, and cost. However, real-time HD video may be demanded by a specific type of device to perform monitoring.
  • the smart grid collects information and connects the sensors to each other using digital information and communication technology so as to act according to the collected information. Since this information may include behaviors of a supply company and a consumer, the smart grid may improve distribution of fuels such as electricity by a method having efficiency, reliability, economic feasibility, production sustainability, and automation.
  • the smart grid may also be regarded as another sensor network having low latency.
  • Mission critical application is one of 5G use scenarios.
  • a health part contains many application programs capable of enjoying benefit of mobile communication.
  • a communication system may support remote treatment that provides clinical treatment in a faraway place. Remote treatment may aid in reducing a barrier against distance and improve access to medical services that cannot be continuously available in a faraway rural area. Remote treatment is also used to perform important treatment and save lives in an emergency situation.
  • the wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.
  • Wireless and mobile communication gradually becomes important in the field of an industrial application.
  • Wiring is high in installation and maintenance cost. Therefore, a possibility of replacing a cable with reconstructible wireless links is an attractive opportunity in many industrial fields.
  • it is necessary for wireless connection to be established with latency, reliability, and capacity similar to those of the cable and management of wireless connection needs to be simplified. Low latency and a very low error probability are new requirements when connection to 5G is needed.
  • Logistics and freight tracking are important use cases for mobile communication that enables inventory and package tracking anywhere using a location-based information system.
  • the use cases of logistics and freight typically demand low data rate but require location information with a wide range and reliability.
  • the communication system 1 includes wireless devices 100a to 100f, base stations (BSs) 200, and a network 300.
  • FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.
  • the BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS/network node with respect to other wireless devices.
  • the wireless devices 100a to 100f represent devices performing communication using radio access technology (RAT) (e.g., 5G new RAT (NR)) or LTE) and may be referred to as communication/radio/5G devices.
  • RAT radio access technology
  • the wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device/server 400.
  • the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles.
  • the vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone).
  • UAV unmanned aerial vehicle
  • the XR device may include an AR/VR/Mixed Reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc.
  • the hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook).
  • the home appliance may include a TV, a refrigerator, and a washing machine.
  • the IoT device may include a sensor and a smartmeter.
  • the wireless devices 100a to 100f may be called user equipments (UEs).
  • a UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather/environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.
  • PDA personal digital assistant
  • PMP portable multimedia player
  • PC slate personal computer
  • tablet PC a tablet PC
  • ultrabook a vehicle, a vehicle having an autonomous
  • the UAV may be, for example, an aircraft aviated by a wireless control signal without a human being onboard.
  • the VR device may include, for example, a device for implementing an object or a background of the virtual world.
  • the AR device may include, for example, a device implemented by connecting an object or a background of the virtual world to an object or a background of the real world.
  • the MR device may include, for example, a device implemented by merging an object or a background of the virtual world into an object or a background of the real world.
  • the hologram device may include, for example, a device for implementing a stereoscopic image of 360 degrees by recording and reproducing stereoscopic information, using an interference phenomenon of light generated when two laser lights called holography meet.
  • the public safety device may include, for example, an image relay device or an image device that is wearable on the body of a user.
  • the MTC device and the IoT device may be, for example, devices that do not require direct human intervention or manipulation.
  • the MTC device and the IoT device may include smartmeters, vending machines, thermometers, smartbulbs, door locks, or various sensors.
  • the medical device may be, for example, a device used for the purpose of diagnosing, treating, relieving, curing, or preventing disease.
  • the medical device may be a device used for the purpose of diagnosing, treating, relieving, or correcting injury or impairment.
  • the medical device may be a device used for the purpose of inspecting, replacing, or modifying a structure or a function.
  • the medical device may be a device used for the purpose of adjusting pregnancy.
  • the medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for procedure.
  • the security device may be, for example, a device installed to prevent a danger that may arise and to maintain safety.
  • the security device may be a camera, a closed-circuit TV (CCTV), a recorder, or a black box.
  • CCTV closed-circuit TV
  • the FinTech device may be, for example, a device capable of providing a financial service such as mobile payment.
  • the FinTech device may include a payment device or a point of sales (POS) system.
  • POS point of sales
  • the weather/environment device may include, for example, a device for monitoring or predicting a weather/environment.
  • the wireless devices 100a to 100f may be connected to the network 300 via the BSs 200.
  • An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300.
  • the network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network.
  • the wireless devices 100a to 100f may communicate with each other through the BSs 200/network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200/network 300.
  • the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication).
  • the IoT device e.g., a sensor
  • the IoT device may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.
  • Wireless communication/connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and/or between wireless device 100a to 100f and BS 200 and/or between BSs 200.
  • the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc.
  • the wireless devices 100a to 100f and the BSs 200/the wireless devices 100a to 100f may transmit/receive radio signals to/from each other through the wireless communication/connections 150a, 150b and 150c.
  • the wireless communication/connections 150a, 150b and 150c may transmit/receive signals through various physical channels.
  • various configuration information configuring processes e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/de-mapping
  • resource allocating processes for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.
  • FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.
  • a first wireless device 100 and a second wireless device 200 may transmit/receive radio signals to/from an external device through a variety of RATs (e.g., LTE and NR).
  • RATs e.g., LTE and NR
  • ⁇ the first wireless device 100 and the second wireless device 200 ⁇ may correspond to at least one of ⁇ the wireless device 100a to 100f and the BS 200 ⁇ , ⁇ the wireless device 100a to 100f and the wireless device 100a to 100f ⁇ and/or ⁇ the BS 200 and the BS 200 ⁇ of FIG. 1.
  • the first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108.
  • the processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure.
  • the processor(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106.
  • the processor(s) 102 may receive radio signals including second information/signals through the transceiver(s) 106 and then store information obtained by processing the second information/signals in the memory(s) 104.
  • the memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102.
  • the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure.
  • the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR).
  • the transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive radio signals through one or more antennas 108.
  • Each of the transceiver(s) 106 may include a transmitter and/or a receiver.
  • the transceiver(s) 106 may be interchangeably used with radio frequency (RF) unit(s).
  • the first wireless device 100 may represent a communication modem/circuit/chip.
  • the second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and/or one or more antennas 208.
  • the processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure.
  • the processor(s) 202 may process information within the memory(s) 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) 206.
  • the processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204.
  • the memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202.
  • the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure.
  • the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR).
  • the transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208.
  • Each of the transceiver(s) 206 may include a transmitter and/or a receiver.
  • the transceiver(s) 206 may be interchangeably used with RF unit(s).
  • the second wireless device 200 may represent a communication modem/circuit/chip.
  • One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202.
  • the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer).
  • layers e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer).
  • PHY physical
  • MAC media access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • the one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and/or one or more service data unit (SDUs) according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206.
  • the one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers.
  • the one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • firmware or software may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions.
  • Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202.
  • the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and/or a set of commands.
  • the one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands.
  • the one or more memories 104 and 204 may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof.
  • the one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202.
  • the one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.
  • the one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, to one or more other devices.
  • the one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, from one or more other devices.
  • the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals.
  • the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices.
  • the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.
  • the one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208.
  • the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).
  • the one or more transceivers 106 and 206 may convert received radio signals/channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc., using the one or more processors 102 and 202.
  • the one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals.
  • the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters.
  • the transceivers 106 and 206 can up-convert OFDM baseband signals to a carrier frequency by their (analog) oscillators and/or filters under the control of the processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency.
  • the transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and/or filters under the control of the transceivers 102 and 202.
  • a UE may operate as a transmitting device in uplink (UL) and as a receiving device in downlink (DL).
  • a BS may operate as a receiving device in UL and as a transmitting device in DL.
  • the first wireless device 100 acts as the UE
  • the second wireless device 200 acts as the BS.
  • the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be configured to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure.
  • the processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be configured to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.
  • a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.
  • NB node B
  • eNB eNode B
  • gNB gNode B
  • FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.
  • the wireless device may be implemented in various forms according to a use-case/service (refer to FIG. 1).
  • wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules.
  • each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140.
  • the communication unit 110 may include a communication circuit 112 and transceiver(s) 114.
  • the communication circuit 112 may include the one or more processors 102 and 202 of FIG. 2 and/or the one or more memories 104 and 204 of FIG. 2.
  • the transceiver(s) 114 may include the one or more transceivers 106 and 206 of FIG.
  • the control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140 and controls overall operation of each of the wireless devices 100 and 200. For example, the control unit 120 may control an electric/mechanical operation of each of the wireless devices 100 and 200 based on programs/code/commands/information stored in the memory unit 130.
  • the control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit 110.
  • the additional components 140 may be variously configured according to types of the wireless devices 100 and 200.
  • the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit (e.g., audio I/O port, video I/O port), a driving unit, and a computing unit.
  • I/O input/output
  • the wireless devices 100 and 200 may be implemented in the form of, without being limited to, the robot (100a of FIG. 1), the vehicles (100b-1 and 100b-2 of FIG. 1), the XR device (100c of FIG. 1), the hand-held device (100d of FIG. 1), the home appliance (100e of FIG. 1), the IoT device (100f of FIG.
  • the wireless devices 100 and 200 may be used in a mobile or fixed place according to a use-example/service.
  • the entirety of the various elements, components, units/portions, and/or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110.
  • the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110.
  • Each element, component, unit/portion, and/or module within the wireless devices 100 and 200 may further include one or more elements.
  • the control unit 120 may be configured by a set of one or more processors.
  • control unit 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor.
  • the memory 130 may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.
  • FIG. 4 shows another example of wireless devices to which implementations of the present disclosure is applied.
  • wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules.
  • the first wireless device 100 may include at least one transceiver, such as a transceiver 106, and at least one processing chip, such as a processing chip 101.
  • the processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104.
  • the memory 104 may be operably connectable to the processor 102.
  • the memory 104 may store various types of information and/or instructions.
  • the memory 104 may store a software code 105 which implements instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the software code 105 may control the processor 102 to perform one or more protocols.
  • the software code 105 may control the processor 102 may perform one or more layers of the radio interface protocol.
  • the second wireless device 200 may include at least one transceiver, such as a transceiver 206, and at least one processing chip, such as a processing chip 201.
  • the processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204.
  • the memory 204 may be operably connectable to the processor 202.
  • the memory 204 may store various types of information and/or instructions.
  • the memory 204 may store a software code 205 which implements instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the software code 205 may control the processor 202 to perform one or more protocols.
  • the software code 205 may control the processor 202 may perform one or more layers of the radio interface protocol.
  • FIG. 5 shows an example of UE to which implementations of the present disclosure is applied.
  • a UE 100 may correspond to the first wireless device 100 of FIG. 2 and/or the first wireless device 100 of FIG. 4.
  • a UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 110, a battery 1112, a display 114, a keypad 116, a subscriber identification module (SIM) card 118, a speaker 120, and a microphone 122.
  • SIM subscriber identification module
  • the processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the processor 102 may be configured to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • Layers of the radio interface protocol may be implemented in the processor 102.
  • the processor 102 may include ASIC, other chipset, logic circuit and/or data processing device.
  • the processor 102 may be an application processor.
  • the processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator).
  • DSP digital signal processor
  • CPU central processing unit
  • GPU graphics processing unit
  • modem modulator and demodulator
  • processor 102 may be found in SNAPDRAGON TM series of processors made by Qualcomm ® , EXYNOS TM series of processors made by Samsung ® , A series of processors made by Apple ® , HELIO TM series of processors made by MediaTek ® , ATOM TM series of processors made by Intel ® or a corresponding next generation processor.
  • the memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102.
  • the memory 104 may include ROM, RAM, flash memory, memory card, storage medium and/or other storage device.
  • modules e.g., procedures, functions, etc.
  • the modules can be stored in the memory 104 and executed by the processor 102.
  • the memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.
  • the transceiver 106 is operatively coupled with the processor 102, and transmits and/or receives a radio signal.
  • the transceiver 106 includes a transmitter and a receiver.
  • the transceiver 106 may include baseband circuitry to process radio frequency signals.
  • the transceiver 106 controls the one or more antennas 108 to transmit and/or receive a radio signal.
  • the power management module 110 manages power for the processor 102 and/or the transceiver 106.
  • the battery 112 supplies power to the power management module 110.
  • the display 114 outputs results processed by the processor 102.
  • the keypad 116 receives inputs to be used by the processor 102.
  • the keypad 16 may be shown on the display 114.
  • the SIM card 118 is an integrated circuit that is intended to securely store the international mobile subscriber identity (IMSI) number and its related key, which are used to identify and authenticate subscribers on mobile telephony devices (such as mobile phones and computers). It is also possible to store contact information on many SIM cards.
  • IMSI international mobile subscriber identity
  • the speaker 120 outputs sound-related results processed by the processor 102.
  • the microphone 122 receives sound-related inputs to be used by the processor 102.
  • FIGs. 6 and 7 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.
  • FIG. 6 illustrates an example of a radio interface user plane protocol stack between a UE and a BS
  • FIG. 7 illustrates an example of a radio interface control plane protocol stack between a UE and a BS.
  • the control plane refers to a path through which control messages used to manage call by a UE and a network are transported.
  • the user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported.
  • the user plane protocol stack may be divided into Layer 1 (i.e., a PHY layer) and Layer 2.
  • the control plane protocol stack may be divided into Layer 1 (i.e., a PHY layer), Layer 2, Layer 3 (e.g., an RRC layer), and a non-access stratum (NAS) layer.
  • Layer 1 i.e., a PHY layer
  • Layer 2 e.g., an RRC layer
  • NAS non-access stratum
  • Layer 1 Layer 2 and Layer 3 are referred to as an access stratum (AS).
  • the Layer 2 is split into the following sublayers: MAC, RLC, and PDCP.
  • the Layer 2 is split into the following sublayers: MAC, RLC, PDCP and SDAP.
  • the PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers.
  • the SDAP sublayer offers to 5G core network quality of service (QoS) flows.
  • QoS quality of service
  • the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing/de-multiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels; scheduling information reporting; error correction through hybrid automatic repeat request (HARQ) (one HARQ entity per cell in case of carrier aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding.
  • HARQ hybrid automatic repeat request
  • a single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use.
  • MAC Different kinds of data transfer services are offered by MAC.
  • multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information.
  • Each logical channel type is defined by what type of information is transferred.
  • Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only.
  • Broadcast control channel is a downlink logical channel for broadcasting system control information
  • PCCH paging control channel
  • PCCH is a downlink logical channel that transfers paging information
  • common control channel CCCH
  • DCCH dedicated control channel
  • DTCH Dedicated traffic channel
  • a DTCH can exist in both uplink and downlink.
  • BCCH can be mapped to broadcast channel (BCH); BCCH can be mapped to downlink shared channel (DL-SCH); PCCH can be mapped to paging channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH.
  • PCCH downlink shared channel
  • CCCH can be mapped to DL-SCH
  • DCCH can be mapped to DL-SCH
  • DTCH can be mapped to DL-SCH.
  • the RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged node (AM).
  • the RLC configuration is per logical channel with no dependency on numerologies and/or transmission durations.
  • the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).
  • the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using robust header compression (ROHC); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers.
  • ROIHC robust header compression
  • the main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers.
  • the main services and functions of SDAP include: mapping between a QoS flow and a data radio bearer; marking QoS flow ID (QFI) in both DL and UL packets.
  • QFI QoS flow ID
  • a single protocol entity of SDAP is configured for each individual PDU session.
  • the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to/from NAS from/to UE.
  • SRBs signaling radio bearers
  • DRBs data radio bearers
  • mobility functions including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility
  • QoS management functions UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS
  • FIG. 8 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.
  • OFDM numerologies e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration
  • SCCS subcarrier spacing
  • TTI transmission time interval
  • symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).
  • Each frame is divided into two half-frames, where each of the half-frames has 5ms duration.
  • Each half-frame consists of 5 subframes, where the duration T sf per subframe is 1ms.
  • Each subframe is divided into slots and the number of slots in a subframe depends on a subcarrier spacing.
  • Each slot includes 14 or 12 OFDM symbols based on a cyclic prefix (CP). In a normal CP, each slot includes 14 OFDM symbols and, in an extended CP, each slot includes 12 OFDM symbols.
  • a slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain.
  • a resource grid of N size,u grid,x * N RB sc subcarriers and N subframe,u symb OFDM symbols is defined, starting at common resource block (CRB) N start,u grid indicated by higher-layer signaling (e.g., RRC signaling), where N size,u grid,x is the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink.
  • N RB sc is the number of subcarriers per RB. In the 3GPP based wireless communication system, N RB sc is 12 generally.
  • Each element in the resource grid for the antenna port p and the subcarrier spacing configuration u is referred to as a resource element (RE) and one complex symbol may be mapped to each RE.
  • Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l representing a symbol location relative to a reference point in the time domain.
  • an RB is defined by 12 consecutive subcarriers in the frequency domain.
  • RBs are classified into CRBs and physical resource blocks (PRBs).
  • CRBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configuration u .
  • the center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides with 'point A' which serves as a common reference point for resource block grids.
  • PRBs are defined within a bandwidth part (BWP) and numbered from 0 to N size BWP,i -1, where i is the number of the bandwidth part.
  • BWP bandwidth part
  • n PRB n CRB + N size BWP,i , where N size BWP,i is the common resource block where bandwidth part starts relative to CRB 0.
  • the BWP includes a plurality of consecutive RBs.
  • a carrier may include a maximum of N (e.g., 5) BWPs.
  • a UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.
  • the NR frequency band may be defined as two types of frequency range, i.e., FR1 and FR2.
  • the numerical value of the frequency range may be changed.
  • the frequency ranges of the two types may be as shown in Table 3 below.
  • FR1 may mean "sub 6 GHz range”
  • FR2 may mean “above 6 GHz range”
  • mmW millimeter wave
  • FR1 may include a frequency band of 410MHz to 7125MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).
  • the term "cell” may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources.
  • a “cell” as a geographic area may be understood as coverage within which a node can provide service using a carrier and a "cell” as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier.
  • the "cell” associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL component carrier (CC) and a UL CC.
  • the cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources.
  • the coverage of the node may be associated with coverage of the "cell" of radio resources used by the node. Accordingly, the term "cell" may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.
  • CA two or more CCs are aggregated.
  • a UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities.
  • CA is supported for both contiguous and non-contiguous CCs.
  • the UE When CA is configured, the UE only has one RRC connection with the network.
  • one serving cell At RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment/handover, one serving cell provides the security input.
  • This cell is referred to as the primary cell (PCell).
  • the PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
  • secondary cells can be configured to form together with the PCell a set of serving cells.
  • An SCell is a cell providing additional radio resources on top of special cell (SpCell).
  • the configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells.
  • the term SpCell refers to the PCell of the master cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG).
  • MCG master cell group
  • PSCell primary SCell
  • SCG secondary cell group
  • An SpCell supports PUCCH transmission and contention-based random access, and is always activated.
  • the MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells.
  • the SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC.
  • a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprised of the PCell.
  • serving cells is used to denote the set of cells comprised of the SpCell(s) and all SCells.
  • two MAC entities are configured in a UE: one for the MCG and one for the SCG.
  • FIG. 9 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.
  • Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data.
  • the MAC PDU is transmitted/received using radio resources through the PHY layer to/from an external device.
  • the MAC PDU arrives to the PHY layer in the form of a transport block.
  • the uplink transport channels UL-SCH and RACH are mapped to their physical channels PUSCH and PRACH, respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to PDSCH, PBCH and PDSCH, respectively.
  • uplink control information (UCI) is mapped to PUCCH
  • downlink control information (DCI) is mapped to PDCCH.
  • a MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant
  • a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.
  • a UE In order to transmit data unit(s) of the present disclosure on UL-SCH, a UE shall have uplink resources available to the UE. In order to receive data unit(s) of the present disclosure on DL-SCH, a UE shall have downlink resources available to the UE.
  • the resource allocation includes time domain resource allocation and frequency domain resource allocation.
  • uplink resource allocation is also referred to as uplink grant, and downlink resource allocation is also referred to as downlink assignment.
  • An uplink grant is either received by the UE dynamically on PDCCH, in a random access response, or configured to the UE semi-persistently by RRC.
  • Downlink assignment is either received by the UE dynamically on the PDCCH, or configured to the UE semi-persistently by RRC signaling from the BS.
  • the BS can dynamically allocate resources to UEs via the cell radio network temporary identifier (C-RNTI) on PDCCH(s).
  • C-RNTI cell radio network temporary identifier
  • a UE always monitors the PDCCH(s) in order to find possible grants for uplink transmission when its downlink reception is enabled (activity governed by discontinuous reception (DRX) when configured).
  • DRX discontinuous reception
  • the BS can allocate uplink resources for the initial HARQ transmissions to UEs.
  • Two types of configured uplink grants are defined: Type 1 and Type 2. With Type 1, RRC directly provides the configured uplink grant (including the periodicity).
  • RRC defines the periodicity of the configured uplink grant while PDCCH addressed to configured scheduling RNTI (CS-RNTI) can either signal and activate the configured uplink grant, or deactivate it. That is, a PDCCH addressed to CS-RNTI indicates that the uplink grant can be implicitly reused according to the periodicity defined by RRC, until deactivated.
  • the BS can dynamically allocate resources to UEs via the C-RNTI on PDCCH(s).
  • a UE always monitors the PDCCH(s) in order to find possible assignments when its downlink reception is enabled (activity governed by DRX when configured).
  • SPS semi-persistent Scheduling
  • the BS can allocate downlink resources for the initial HARQ transmissions to UEs.
  • RRC defines the periodicity of the configured downlink assignments while PDCCH addressed to CS-RNTI can either signal and activate the configured downlink assignment, or deactivate it.
  • a PDCCH addressed to CS-RNTI indicates that the downlink assignment can be implicitly reused according to the periodicity defined by RRC, until deactivated.
  • PDCCH For resource allocation by PDCCH (i.e., resource allocation by DCI), PDCCH can be used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH, where the DCI on PDCCH includes: downlink assignments containing at least modulation and coding format (e.g., modulation and coding scheme (MCS) index I MCS ), resource allocation, and hybrid-ARQ information related to DL-SCH; or uplink scheduling grants containing at least modulation and coding format, resource allocation, and hybrid-ARQ information related to UL-SCH.
  • MCS modulation and coding scheme
  • the size and usage of the DCI carried by one PDCCH are varied depending on DCI formats.
  • DCI format 0_0 or DCI format 0_1 is used for scheduling of PUSCH in one cell
  • DCI format 1_0 or DCI format 1_1 is used for scheduling of PDSCH in one cell.
  • FIG. 10 shows an example of PDSCH time domain resource allocation by PDCCH to which implementations of the present disclosure is applied.
  • FIG. 11 shows an example of PUSCH time resource allocation by PDCCH to which implementations of the present disclosure is applied.
  • DCI carried by a PDCCH for scheduling PDSCH or PUSCH includes a value m for a row index m +1 to an allocation table for PDSCH or PUSCH.
  • Either a predefined default PDSCH time domain allocation A, B or C is applied as the allocation table for PDSCH, or RRC configured pdsch - TimeDomainAllocationList is applied as the allocation table for PDSCH.
  • Either a predefined default PUSCH time domain allocation A is applied as the allocation table for PUSCH, or the RRC configured pusch - TimeDomainAllocationList is applied as the allocation table for PUSCH.
  • Which PDSCH time domain resource allocation configuration to apply and which PUSCH time domain resource allocation table to apply are determined according to a fixed/predefined rule.
  • Each indexed row in PDSCH time domain allocation configurations defines the slot offset K 0 , the start and length indicator SLIV , or directly the start symbol S and the allocation length L , and the PDSCH mapping type to be assumed in the PDSCH reception.
  • Each indexed row in PUSCH time domain allocation configurations defines the slot offset K 2 , the start and length indicator SLIV , or directly the start symbol S and the allocation length L , and the PUSCH mapping type to be assumed in the PUSCH reception.
  • K 0 for PDSCH, or K 2 for PUSCH is the timing difference between a slot with a PDCCH and a slot with PDSCH or PUSCH corresponding to the PDCCH.
  • SLIV is a joint indication of starting symbol S relative to the start of the slot with PDSCH or PUSCH, and the number L of consecutive symbols counting from the symbol S .
  • mapping Type A where demodulation reference signal (DMRS) is positioned in 3 rd or 4 th symbol of a slot depending on the RRC signaling
  • Mapping Type B where DMRS is positioned in the first allocated symbol.
  • the scheduling DCI includes the Frequency domain resource assignment field which provides assignment information on resource blocks used for PDSCH or PUSCH.
  • the Frequency domain resource assignment field may provide a UE with information on a cell for PDSCH or PUSCH transmission, information on a bandwidth part for PDSCH or PUSCH transmission, information on resource blocks for PDSCH or PUSCH transmission.
  • Type 1 where an uplink grant is provided by RRC, and stored as configured grant
  • configured grant Type 2 where an uplink grant is provided by PDCCH, and stored or cleared as configured uplink grant based on L1 signaling indicating configured uplink grant activation or deactivation.
  • Type 1 and Type 2 are configured by RRC per serving cell and per BWP. Multiple configurations can be active simultaneously only on different serving cells. For Type 2, activation and deactivation are independent among the serving cells. For the same serving cell, the MAC entity is configured with either Type 1 or Type 2.
  • a UE is provided with at least the following parameters via RRC signaling from a BS when the configured grant type 1 is configured:
  • timeDomainAllocation value m which provides a row index m+1 pointing to an allocation table, indicating a combination of a start symbol S and length L and PUSCH mapping type
  • the UE Upon configuration of a configured grant Type 1 for a serving cell by RRC, the UE stores the uplink grant provided by RRC as a configured uplink grant for the indicated serving cell, and initialize or re-initialise the configured uplink grant to start in the symbol according to timeDomainOffset and S (derived from SLIV ), and to reoccur with periodicity .
  • a UE is provided with at least the following parameters via RRC signaling from a BS when the configured gran Type 2 is configured:
  • the actual uplink grant is provided to the UE by the PDCCH (addressed to CS-RNTI).
  • a UE may be configured with SPS per serving cell and per BWP by RRC signaling from a BS. Multiple configurations can be active simultaneously only on different serving cells. Activation and deactivation of the DL SPS are independent among the serving cells.
  • a DL assignment is provided to the UE by PDCCH, and stored or cleared based on L1 signaling indicating SPS activation or deactivation.
  • a UE is provided with the following parameters via RRC signaling from a BS when SPS is configured:
  • - cs- RNTI which is CS-RNTI for activation, deactivation, and retransmission
  • a UE validates, for scheduling activation or scheduling release, a DL SPS assignment PDCCH or configured UL grant type 2 PDCCH if the cyclic redundancy check (CRC) of a corresponding DCI format is scrambled with CS-RNTI provided by the RRC parameter cs- RNTI and the new data indicator field for the enabled transport block is set to 0.
  • CRC cyclic redundancy check
  • Validation of the DCI format is achieved if all fields for the DCI format are set according to Table 5 or Table 6 below.
  • Table 5 shows special fields for DL SPS and UL grant Type 2 scheduling activation PDCCH validation
  • Table 6 shows special fields for DL SPS and UL grant Type 2 scheduling release PDCCH validation.
  • DCI format 0_0/0_1 DCI format 1_0
  • DCI format 1_1 HARQ process number set to all '0's set to all '0's set to all '0's Redundancy version set to '00' set to '00'
  • DCI format 0_0 DCI format 1_0 HARQ process number set to all '0's set to all '0's Redundancy version set to '00' set to '00' Modulation and coding scheme set to all '1's set to all '1's Resource block assignment set to all '1's set to all '1's
  • the resource assignment fields e.g., time domain resource assignment field which provides Time domain resource assignment value m , frequency domain resource assignment field which provides the frequency resource block allocation, modulation and coding scheme field
  • the UE considers the information in the DCI format as valid activation or valid release of DL SPS or configured UL grant Type 2.
  • the data unit(s) of the present disclosure is(are) subject to the physical layer processing at a transmitting side before transmission via radio interface, and the radio signals carrying the data unit(s) of the present disclosure are subject to the physical layer processing at a receiving side.
  • FIG. 12 shows an example of physical layer processing at a transmitting side to which implementations of the present disclosure is applied.
  • Table 7 specifies the mapping of the uplink transport channels to their corresponding physical channels
  • Table 8 specifies the mapping of the uplink control channel information to its corresponding physical channel
  • Table 9 specifies the mapping of the downlink transport channels to their corresponding physical channels
  • Table 10 specifies the mapping of the downlink control channel information to its corresponding physical channel.
  • Data and control streams from/to MAC layer are encoded to offer transport and control services over the radio transmission link in the PHY layer.
  • a transport block from MAC layer is encoded into a codeword at a transmitting side.
  • Channel coding scheme is a combination of error detection, error correcting, rate matching, interleaving and transport channel or control information mapping onto/splitting from physical channels.
  • Table 11 specifies the mapping of transport channels to respective coding scheme.
  • Table 12 specifies the mapping of control information to respective coding scheme.
  • Transport Channel Coding scheme UL-SCH Low density parity check (LDPC) code
  • LDPC Low density parity check
  • a transport block CRC sequence is attached to provide error detection for a receiving side.
  • the communication device uses LDPC codes in encoding/decoding UL-SCH and DL-SCH.
  • the 3GPP NR system supports two LDPC base graphs (i.e., two LDPC base matrixes): LDPC base graph 1 optimized for small transport blocks and LDPC base graph 2 for larger transport blocks. Either LDPC base graph 1 or 2 is selected based on the size of the transport block and coding rate R .
  • the coding rate R is indicated by the MCS index I MCS .
  • the MCS index is dynamically provided to a UE by PDCCH scheduling PUSCH or PDSCH, provided to a UE by PDCCH activating or (re-)initializing the UL configured grant 2 or DL SPS, or provided to a UE by RRC signaling related to the UL configured grant Type 1. If the CRC attached transport block is larger than the maximum code block size for the selected LDPC base graph, the CRC attached transport block may be segmented into code blocks, and an additional CRC sequence is attached to each code block.
  • the maximum code block sizes for the LDPC base graph 1 and the LDPC base graph 2 are 8448 bits and 3480 bits, respectively.
  • the CRC attached transport block is encoded with the selected LDPC base graph.
  • Each code block of the transport block is encoded with the selected LDPC base graph.
  • the LDPC coded blocks are then individually rat matched. Code block concatenation is performed to create a codeword for transmission on PDSCH or PUSCH.
  • up to 2 codewords i.e., up to 2 transport blocks
  • PUSCH can be used for transmission of UL-SCH data and layer 1/2 control information.
  • the layer 1/2 control information may be multiplexed with the codeword for UL-SCH data.
  • the bits of the codeword are scrambled and modulated to generate a block of complex-valued modulation symbols.
  • the complex-valued modulation symbols of the codeword are mapped to one or more multiple input multiple output (MIMO) layers.
  • a codeword can be mapped to up to 4 layers.
  • a PDSCH can carry two codewords, and thus a PDSCH can support up to 8-layer transmission.
  • a PUSCH supports a single codeword, and thus a PUSCH can support up to 4-layer transmission.
  • the DL transmission waveform is conventional OFDM using a cyclic prefix (CP).
  • CP cyclic prefix
  • transform precoding in other words, DFT
  • the UL transmission waveform is conventional OFDM using a CP with a transform precoding function performing DFT spreading that can be disabled or enabled.
  • the transform precoding can be optionally applied if enabled.
  • the transform precoding is to spread UL data in a special way to reduce peak-to-average power ratio (PAPR) of the waveform.
  • the transform precoding is a form of DFT.
  • the 3GPP NR system supports two options for UL waveform: one is CP-OFDM (same as DL waveform) and the other one is DFT-s-OFDM. Whether a UE has to use CP-OFDM or DFT-s-OFDM is determined by a BS via RRC parameters.
  • the layers are mapped to antenna ports.
  • DL for the layers to antenna ports mapping, a transparent manner (non-codebook based) mapping is supported and how beamforming or MIMO precoding is performed is transparent to the UE.
  • UL for the layers to antenna ports mapping, both the non-codebook based mapping and a codebook based mapping are supported.
  • the complex-valued modulation symbols are mapped to subcarriers in resource blocks allocated to the physical channel.
  • the communication device at the transmitting side generates a time-continuous OFDM baseband signal on antenna port p and subcarrier spacing configuration u for OFDM symbol l in a TTI for a physical channel by adding a CP and performing inverse fast Fourier transform (IFFT). For example, for each OFDM symbol, the communication device at the transmitting side may perform IFFT on the complex-valued modulation symbols mapped to resource blocks in the corresponding OFDM symbol and add a CP to the IFFT-ed signal to generate the OFDM baseband signal.
  • IFFT inverse fast Fourier transform
  • the communication device at the transmitting side up-convers the OFDM baseband signal for antenna port p , subcarrier spacing configuration u and OFDM symbol l to a carrier frequency f 0 of a cell to which the physical channel is assigned.
  • the processor 102, 202 in FIG. 2, the processor included in the communication unit 112 and/or the control unit 120 in FIG. 3, the processor 102, 202 in FIG. 4 and/or the processor 102 in FIG. 5 may be configured to perform encoding, schrambling, modulation, layer mapping, transform precoding (for UL), subcarrier mapping, and OFDM modulation.
  • the processor 102, 202 in FIG. 2, the processor included in the communication unit 112 and/or the control unit 120 in FIG. 3, the processor 102, 202 in FIG. 4 and/or the processor 102 in FIG. 5 may control the transceiver 106, 206 in FIG. 2, the transceiver 114 in FIG. 3, the transceiver 106, 206 in FIG. 4 and/or the transceiver 106 in FIG. 5 to up-convert the OFDM baseband signal onto the carrier frequency to generate radio frequency (RF) signals.
  • RF radio frequency
  • FIG. 13 shows an example of physical layer processing at a receiving side to which implementations of the present disclosure is applied.
  • the physical layer processing at the receiving side is basically the inverse processing of the physical layer processing at the transmitting side. Each step of FIG. 13 is described below in detail.
  • the communication device at a receiving side receives RF signals at a carrier frequency through antennas.
  • the transceiver 106, 206 in FIG. 2, the transceiver 114 in FIG. 3, the transceiver 106, 206 in FIG. 4 and/or the transceiver 106 in FIG. 5receiving the RF signals at the carrier frequency down-converts the carrier frequency of the RF signals into the baseband in order to obtain OFDM baseband signals.
  • the communication device at the receiving side obtains complex-valued modulation symbols via CP detachment and FFT. For example, for each OFDM symbol, the communication device at the receiving side removes a CP from the OFDM baseband signals and performs FFT on the CP-removed OFDM baseband signals to obtain complex-valued modulation symbols for antenna port p , subcarrier spacing u and OFDM symbol l .
  • the subcarrier de-mapping is performed on the complex-valued modulation symbols to obtain complex-valued modulation symbols of a corresponding physical channel.
  • the UE processor may obtain complex-valued modulation symbols mapped to subcarriers belong to PDSCH from among complex-valued modulation symbols received in a bandwidth part.
  • Transform de-precoding e.g., inverse DFT (IDFT)
  • IDFT inverse DFT
  • the transform de-precoding is not performed.
  • the complex-valued modulation symbols are de-mapped into one or two codewords.
  • the complex-valued modulation symbols of a codeword are demodulated and descrambled into bits of the codeword.
  • the codeword is decoded into a transport block.
  • either LDPC base graph 1 or 2 is selected based on the size of the transport block and coding rate R .
  • the codeword may include one or multiple coded blocks.
  • Each coded block is decoded with the selected LDPC base graph into a CRC-attached code block or CRC-attached transport block. If code block segmentation was performed on a CRC-attached transport block at the transmitting side, a CRC sequence is removed from each of CRC-attached code blocks, whereby code blocks are obtained.
  • the code blocks are concatenated into a CRC-attached transport block.
  • the transport block CRC sequence is removed from the CRC-attached transport block, whereby the transport block is obtained.
  • the transport block is delivered to the MAC layer.
  • the time and frequency domain resources e.g., OFDM symbol, subcarriers, carrier frequency
  • OFDM modulation and frequency up/down conversion can be determined based on the resource allocation (e.g., UL grant, DL assignment).
  • the integrity protection (IP) function includes both integrity protection and integrity verification and is performed in PDCP, if configured.
  • the data unit that is integrity protected is the PDU header and the data part of the PDU before ciphering.
  • the integrity protection algorithm and key to be used by the PDCP entity are configured by upper layers.
  • the integrity protection function is activated/suspended/resumed by upper layers. When security is activated and not suspended, the integrity protection function shall be applied to all PDUs including and subsequent to the PDU indicated by upper layers for the downlink and the uplink, respectively.
  • the parameters that are required by PDCP for integrity protection are defined and are input to the integrity protection algorithm.
  • the required inputs to the integrity protection function include the COUNT value, and DIRECTION (direction of the transmission).
  • the parameters required by PDCP which are provided by upper layers are listed below:
  • the UE computes the value of the MAC-I field and at reception it verifies the integrity of the PDCP data PDU by calculating the X-MAC based on the input parameters as specified above. If the calculated X-MAC corresponds to the received MAC-I, integrity protection is verified successfully.
  • the receiver PDCP entity shall indicate the integrity verification failure to upper layer, and discard the PDCP data PDU.
  • integrity protection and integrity verification is only applicable for SRB. If integrity verification is failed on SRB, the UE performs RRC connection re-establishment procedure to resolve IP problem and remove risk by an attacker, e.g., man in the middle attack.
  • integrity protection can also be configured to DRB as well as SRB.
  • the integrity protection is always applied to PDCP data PDUs of SRBs.
  • the integrity protection is applied to PDCP data PDUs of DRBs for which integrity protection is configured.
  • the integrity protection is not applicable to PDCP control PDUs.
  • RRC connection re-establishment after integrity verification failure is kept for SRB.
  • SRBs have higher priority than DRBs since these carry important signaling information to maintain and change UE connection to the radio network. So, it might seem that initiating an RRC connection re-establishment procedure upon integrity verification failure of SRB is justified.
  • problem scenarios may be as follows:
  • the network i.e., gNB or eNB transmits one way (or, unsolicited) message (i.e., without response message from the UE).
  • examples of the one way message may include RRC connection release message or MSG4 in early data transmission (i.e., EarlyDataComplete message or resume message).
  • examples of the one way message may include data packet.
  • RLC layer of the UE Upon successfully receiving RLC SDU from lower layers, RLC layer of the UE delivers RLC PDU to upper layer (i.e., PDCP layer) and sends a positive acknowledgement for the one way message to the network.
  • RLC PDU i.e., PDCP layer
  • PDCP layer of the UE Upon receiving the RLC PDU from lower layers, PDCP layer of the UE checks integrity verification, but integrity verification may fail. Then, the PDCP layer of the UE discards the RLC PDUs for which integrity verification has failed. However, upon receiving the positive acknowledgement from the RLC layer of the UE, the network considers the one way message successfully delivered to the UE. If the one way message corresponds to SRB mentioned above, e.g., RRC connection release message or MSG4 in EDT, the network makes the UE enter RRC_IDLE by removing UE contexts.
  • SRB e.g., RRC connection release message or MSG4 in EDT
  • Integrity verification fails in the UE side, but the network cannot acknowledge integrity verification failure upon receiving positive acknowledgement from the RLC layer of the UE. Additional reporting may be considered, but it may cause additional signaling and may be difficult to apply in some cases.
  • FIG. 14 shows an example of a method for performing an integrity protection verification according to implementations of the present disclosure.
  • the receiving side of the RLC entity waits to send feedback (e.g., a positive acknowledgement) until a receiving side of a PDCP entity completes to perform integrity verification even if the special RLC SDU meets the condition to send the positive acknowledgement to the a transmitting side of the RLC entity. If integrity verification is successfully completed in the receiving side of the PDCP entity, the receiving side of the RLC entity sends the waited positive acknowledgement to the transmitting side of the RLC entity. Otherwise, the receiving side of the RLC entity may send a negative acknowledgement to the transmitting side of the RLC entity to trigger retransmission of the packets (including the special RLC SDU) from the transmitting side.
  • feedback e.g., a positive acknowledgement
  • the receiving side may correspond to a wireless device.
  • the wireless device may be in communication with at least one of a mobile device, a network, and/or autonomous vehicles other than the wireless device.
  • step S1400 the receiving side receives, from a transmitting side, a first data unit with a specific indication.
  • the first data unit with the specific indication may be received from the transmitting side at the receiving side of the RLC entity via lower layers of the receiving side.
  • the first data unit may include an RLC PDU and/or an RLC SDU.
  • the specific indication includes a specific logical channel identifier (LCID).
  • LCID logical channel identifier
  • the first data unit may include a one-way radio resource control (RRC) message which does not require a response message.
  • RRC radio resource control
  • the one-way RRC message may include an RRC connection release message, an RRC release message, an RRC resume message for EDT.
  • step S1410 the receiving side performs integrity verification on a second data unit which is based on the first data unit with the specific indication.
  • the integrity verification on the second data unit may be performed at the receiving side of the PDCP entity.
  • the second data unit includes a PDCP PDU.
  • the receiving side of the RLC entity may request a feedback of the integrity verification from the receiving side the PDCP entity.
  • the receiving side of the RLC entity may postpone to transmit, to the transmitting side, a positive acknowledgement as a response to the first data unit until the feedback of the integrity verification is received from the receiving side of the PDCP entity.
  • the feedback of the integrity verification may be requested upon delivering the first data unit from the receiving side of the RLC entity to the receiving side of the PDCP entity.
  • step S1420 the receiving side transmits, to the transmitting side, the positive acknowledgement as a response to the first data unit based on a successful integrity verification on the second data unit.
  • the feedback of the integrity verification may correspond to the successful integrity verification on the second data unit.
  • FIG. 15 shows an example of a method for a transmitting side according to implementations of the present disclosure.
  • step S1500 the transmitting side of AM RLC entity receives special RLC SDUs from the upper layer.
  • the transmitting side of AM RLC entity may identify the special RLC SDUs based on (pre-)configuration and/or additional indication from the upper layer to represent the special RLC SDUs.
  • the special RLC SDUs may be determined by a particular LCID.
  • the particular LCID may be (pre)-configured and/or (pre)-determined.
  • the special RLC SDUs may have an indication which requires confirmation of the receiving side of PDCP entity before sending positive acknowledgement to the transmitting side of AM RLC entity.
  • the special RLC SDUs may be integrity protected by the transmitting side of PDCP entity.
  • the special RLC SDU may correspond to RRC message.
  • the RRC message may be one-way RRC message where there is no response RRC message for the RRC message.
  • the RRC message may include at least one of RRC connection release message in LTE, RRC release message in NR and/or RRC resume message in LTE for EDT.
  • step S1510 the transmitting side of AM RLC entity generates RLC PDUs.
  • the transmitting side of AM RLC entity may add additional indication in the RLC PDUs to represent the special RLC PDU in the RLC PDUs. Then, the transmitting side of AM RLC entity submits the RLC PDUs to lower layers.
  • FIG. 16 shows an example of a method for a receiving side according to implementations of the present disclosure.
  • step S1600 the receiving side of AM RLC entity receives RLC PDUs from lower layers and identifies a special RLC PDU in the RLC PDUs.
  • the receiving side of AM RLC entity may identify the special RLC PDU in the RLC PDUs based on (pre-)configurations and/or an indication in the RLC PDUs, as specified in behaviors of the receiving side of AM RLC entity.
  • step S1610 if the receiving side of AM RLC entity needs to send an acknowledgement for the special RLC PDU, the receiving side of AM RLC entity requests feedback of a function operation for the special RLC SDU from upper layers (e.g., PDCP layer) and postpones to send the acknowledgement until the feedback is received from the upper layers.
  • upper layers e.g., PDCP layer
  • the receiving side of AM RLC entity may inform the upper layers of the request of the feedback of the function operation for the special RLC SDU when delivering the RLC SDUs to the upper layers (e.g., PDCP layer). Otherwise, the receiving side of AM RLC entity may perform the legacy behavior.
  • the feedback of the function operation for the special RLC SDU may be requested to the receiving side of PDCP entity with additional indication provided by the receiving side of AM RLC entity and/or new information element (IE) in PDCP PDUs generated by the transmitting side of PDCP entity.
  • IE new information element
  • the function operation may include functions performed in PDCP entity, e.g., integrity verification for control plane data and/or user plane data.
  • step S1620 upon receiving the feedback from the upper layers, the receiving side of AM RLC entity sends the acknowledgement in response to the RLC PDU to a transmitting side.
  • step S1620 may be performed in detail according to one of the following two options.
  • Option 1 for the case PDCP entity manages counter for failure
  • PDCP entity may increment a counter for failure based on failure of the requested function operation on the PDCP PDUs. That is, if PDCP entity fails to perform the requested function operation on the PDCP PDUs received from lower layers, PDCP entity may increment a counter for failure.
  • the counter for failure may be associated to corresponding receiving side of AM RLC entity.
  • the counter for failure may be set to 0 at beginning (i.e., when the AM RLC entity is configured).
  • the counter for failure may be reset to zero when one of the followings occur:
  • PDCP entity may submit the results of requested function operation to lower layers (e.g., AM RLC entity) based on that the counter for failure has not reached a failure threshold. That is, if the counter for failure is less than N which is the failure threshold, PDCP entity may submit the results of requested function operation to lower layers (e.g., AM RLC entity). PDCP entity may not additionally perform legacy behaviors for upper layer (e.g., RRC layer).
  • lower layers e.g., AM RLC entity
  • PDCP entity may not additionally perform legacy behaviors for upper layer (e.g., RRC layer).
  • PDCP entity may indicate the results to upper layers (e.g., RRC layer) based on that the counter for failure has reached a failure threshold. That is, if the counter for failure reaches to N, PDCP entity may indicate the results to upper layers (e.g., RRC layer).
  • RRC layer e.g., RRC layer
  • the legacy behaviors for upper layer may include indicating the integrity verification failure to upper layers if the function operation is integrity verification.
  • N may be (pre-)configured. N may be provided per a packet (e.g., SDU or PDU), or per DRB or per SRB.
  • the receiving side of AM RLC entity Upon receiving the results of the requested function operation from upper layers, the receiving side of AM RLC entity performs the postponed status reporting procedure. That is, upon receiving feedback from the upper layer, the receiving side of AM RLC entity sends the acknowledgement to the transmitting side.
  • the receiving side of AM RLC entity may send the pending positive acknowledgement to the transmitting side based on success of the requested function operation. That is, if the receiving side of AM RLC entity receives the results of the requested function operation which is success, the receiving side of AM RLC entity may send the pending positive acknowledgement to the transmitting side.
  • the receiving side of AM RLC entity may cancel the pending positive acknowledgement and instead send a negative acknowledgement to the transmitting side based on failure of the requested function operation. That is, if the receiving side of AM RLC entity receives the results of the requested function operation which is failure, the receiving side of AM RLC entity may cancel the pending positive acknowledgement and instead send a negative acknowledgement to the transmitting side.
  • PDCP entity may submit the results of requested function operation to lower layers (i.e., AM RLC entity).
  • the PDCP entity may not additionally perform legacy behaviors for upper layer (e.g., RRC layer).
  • the legacy behaviors for upper layer may include indicating the integrity verification failure to upper layers if the function operation is integrity verification.
  • the receiving side of AM RLC entity upon receiving the results of the requested function operation from upper layers, performs the postponed status reporting procedure.
  • the receiving side of AM RLC entity may send the pending positive acknowledgement to the transmitting side based on success of the requested function operation. That is, if the receiving side of AM RLC entity receives the results of the requested function operation which is success, the receiving side of AM RLC entity may send the pending positive acknowledgement to the transmitting side.
  • the receiving side of AM RLC entity may cancel the pending positive acknowledgement and instead send a negative acknowledgement to the transmitting side.
  • the receiving side of AM RLC entity may inform upper layer of the failure. Then, upon receiving the information on the failure, PDCP entity may perform legacy behaviors for upper layer.
  • the wireless device may perform the following actions.
  • the wireless device may enter RRC idle mode.
  • the wireless device may enter RRC idle mode.
  • the wireless device may perform RRC connection re-establishment procedure.
  • the AM RLC entity in Tx side transmits special RLC SDUs to the AM RLC entity in Rx side.
  • the AM RLC entity in Rx side receives the special SDUs.
  • the AM RLC entity in Rx side needs to trigger status reporting to send a positive acknowledgement.
  • the AM RLC entity in RX side postpones the status reporting and requests for feedback of integrity verification to the PDCP entity in Rx side.
  • the PDCP entity in Rx side is configured with N of failure threshold. It is assumed that the N of failure threshold is configured to 2 by the network.
  • the PDCP entity in Rx side receives PDCP SDUs with the request for feedback of integrity verification by the AM RLC entity in Rx side.
  • the PDCP entity in Rx side compares the counter (i.e., 1) to the N of failure threshold (i.e., 2).
  • the PDCP entity in Rx side submits the results for integrity verification (i.e., fail) to the AM RLC entity in Rx side and doesn't indicate the integrity verification failure to upper layers.
  • the AM RLC entity in Rx side cancels the pending positive acknowledgement and instead sends negative acknowledgement to the network
  • the AM RLC entity in Tx side Upon receiving the negative acknowledgement, the AM RLC entity in Tx side performs retransmission of the special RLC PDUs to the AM RLC entity in Rx side.
  • the AM RLC entity in Rx side receives the special SDUs.
  • the AM RLC entity in Rx side needs to trigger status reporting to send a positive acknowledgement.
  • the AM RLC entity in Rx side postpones the status reporting and requests for feedback of integrity verification to the PDCP entity in Rx side.
  • the PDCP entity in Rx side receives PDCP SDUs with the request for feedback of integrity verification by the AM RLC entity in Rx side.
  • the PDCP entity in Rx side compares the counter (i.e., 2) to the N of failure threshold (i.e., 2).
  • the PDCP entity in Rx side indicates the integrity verification failure to upper layers.
  • the UE-RRC layer in RRC connected mode receives integrity verification failure from lower layers.
  • the UE-RRC layer performs re-establishment procedure. Otherwise, the UE-RRC layer enters RRC idle mode.
  • the AM RLC entity in Tx side transmits special RLC SDUs to the AM RLC entity in Rx side.
  • the AM RLC entity in Rx side receives the special SDUs.
  • the AM RLC entity in Rx side needs to trigger status reporting to send a positive acknowledgement.
  • the AM RLC entity in RX side postpones the status reporting and requests for feedback of integrity verification to the PDCP entity in Rx side.
  • the PDCP entity in Rx side is configured with N of failure threshold. It is assumed that the N of failure threshold is configured to 2 by the network.
  • the PDCP entity in Rx side receives PDCP SDUs with the request for feedback of integrity verification by the AM RLC entity in Rx side.
  • the PDCP entity in Rx side compares the counter (i.e., 1) to the N of failure threshold (i.e., 2).
  • the PDCP entity in Rx side submits the results for integrity verification (i.e., fail) to the AM RLC entity in Rx side and doesn't indicate the integrity verification failure to upper layers.
  • the RLC entity in Rx side cancels the pending positive acknowledgement and instead sends negative acknowledgement to the network.
  • the AM RLC entity in Tx side Upon receiving the negative acknowledgement, the AM RLC entity in Tx side performs retransmission of the special RLC PDUs to the AM RLC entity in RX side.
  • the AM RLC entity in Rx side receives the special SDUs.
  • the AM RLC entity in Rx side needs to trigger status reporting to send a positive acknowledgement.
  • the AM RLC entity in Rx side postpones the status reporting and requests for feedback of integrity verification to the PDCP entity in Rx side.
  • the PDCP entity in Rx side receives PDCP SDUs with the request for feedback of integrity protection by the AM RLC entity in Rx side.
  • the PDCP entity in Rx side submits the results for integrity verification (i.e., success) to the AM RLC entity in Rx side.
  • the RLC entity in Rx side sends the pending positive acknowledgement to the network.
  • the AM RLC entity in Tx side Upon receiving the positive acknowledgement, the AM RLC entity in Tx side considers transmission the special RLC PDUs succeeds.
  • the AM RLC entity in Tx side transmits special RLC SDUs to the AM RLC entity in Rx side.
  • the AM RLC entity in Rx side receives the special SDUs.
  • the AM RLC entity in Rx side needs to trigger status reporting to send a positive acknowledgement.
  • the AM RLC entity in Rx side postpones the status reporting and requests for feedback of integrity verification to the PDCP entity in Rx side.
  • the PDCP entity in Rx side receives PDCP SDUs with the request for feedback of integrity verification by the AM RLC entity in Rx side, performs integrity verification and submits the feedback to the AM RLC entity in Rx side.
  • the PDCP entity in Rx side doesn't indicate the integrity verification failure to upper layers even if the integrity verification fails.
  • the AM RLC entity in Rx side is configured with N of failure threshold. It is assumed that the N of failure threshold is configured to 2 by the network.
  • the AM RLC entity in Rx side compares the counter (i.e., 1) to the N of failure threshold (i.e., 2).
  • the AM RLC entity in Rx side cancels the pending positive acknowledgement and instead sends negative acknowledgement to the network.
  • the AM RLC entity in Tx side Upon receiving the negative acknowledgement, the AM RLC entity in Tx side performs retransmission of the special RLC PDUs to the AM RLC entity in RX side.
  • the AM RLC entity in Rx side receives the special SDUs.
  • the AM RLC entity in Rx side needs to trigger status reporting to send a positive acknowledgement.
  • the AM RLC entity in Rx side postpones the status reporting and requests for feedback of integrity verification to the PDCP entity in Rx side.
  • the PDCP entity in Rx side receives PDCP SDUs with the request for feedback of integrity verification by the AM RLC entity in Rx side, performs integrity verification and submits the feedback to the AM RLC entity in Rx side.
  • the PDCP entity in Rx side doesn't indicate the integrity verification failure to upper layers even if the integrity verification fails.
  • the AM RLC entity in Rx side compares the counter (i.e., 2) to the N of failure threshold (i.e., 2).
  • the AM RLC entity in Rx side informs upper layer of the integrity verification failure. Then, upon receiving information on the integrity verification failure, the PDCP entity in Rx side indicates the integrity verification failure to upper layers.
  • the UE-RRC layer in RRC connected mode receives integrity verification failure from lower layers.
  • the UE-RRC layer performs re-establishment procedure. Otherwise, the UE-RRC layer enters RRC idle mode.
  • the AM RLC entity in Tx side transmits special RLC SDUs to the AM RLC entity in Rx side.
  • the AM RLC entity in Rx side receives the special SDUs.
  • the AM RLC entity in Rx side needs to trigger status reporting to send a positive acknowledgement.
  • the AM RLC entity in Rx side postpones the status reporting and requests for feedback of integrity verification to the PDCP entity in Rx side.
  • the PDCP entity in Rx side receives PDCP SDUs with the request for feedback of integrity protection by the AM RLC entity in Rx side, performs integrity verification and submits the feedback to RLC entity.
  • the PDCP entity in Rx side doesn't indicate the integrity verification failure to upper layers even if the integrity verification fails.
  • the AM RLC entity in Rx side is configured with N of failure threshold. It is assumed that the N of failure threshold is configured to 2 by the network.
  • the AM RLC entity in Rx side compares the counter (i.e., 1) to the N of failure threshold (i.e., 2).
  • the AM RLC entity in Rx side cancels the pending positive acknowledgement and instead sends negative acknowledgement to the network.
  • the AM RLC entity in Tx side perform retransmission the special RLC PDUs
  • the AM RLC entity in Rx side receives the special SDUs.
  • the AM RLC entity in Rx side needs to trigger status reporting to send a negative acknowledgement.
  • the AM RLC entity in Rx side sends the negative acknowledgement to the network.
  • the present disclosure can be applied to some cases/packets acknowledgment is required regardless of mode such as UM and TM.
  • the present disclosure can be applied to LTE as well as NR.
  • the present disclosure can be applied to SRBs as well as DRBs.
  • the present disclosure can have various advantageous effects.
  • efficient signaling procedure can be provided for packets required for more than functional verification of more than two layers.

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil permettant de gérer une défaillance d'une vérification d'intégrité. Un côté de réception reçoit, à partir d'un côté de transmission, une première unité de données contenant une indication spécifique, et effectue une vérification d'intégrité sur une seconde unité de données fondée sur la première unité de données contenant l'indication spécifique. En fonction d'une vérification d'intégrité réussie sur la seconde unité de données, par exemple lorsque la vérification d'intégrité sur la seconde unité de données a réussi, le côté de réception transmet, au côté de transmission, un accusé de réception positif en réponse à la première unité de données.
PCT/KR2020/001257 2019-01-30 2020-01-28 Gestion de défaillance de vérification d'intégrité WO2020159178A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20190012282 2019-01-30
KR10-2019-0012282 2019-01-30

Publications (1)

Publication Number Publication Date
WO2020159178A1 true WO2020159178A1 (fr) 2020-08-06

Family

ID=71840568

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2020/001257 WO2020159178A1 (fr) 2019-01-30 2020-01-28 Gestion de défaillance de vérification d'intégrité

Country Status (1)

Country Link
WO (1) WO2020159178A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100042660A (ko) * 2007-08-14 2010-04-26 콸콤 인코포레이티드 Ｍａｃ프레임들 내부의 ｐｄｃｐ 제어 ｐｄｕ들의 전달
US20130235803A1 (en) * 2010-02-02 2013-09-12 Lg Electronics Inc. Method of selectively applying a pdcp function in wireless communication system
US20160302075A1 (en) * 2013-11-11 2016-10-13 Telefonaktiebolaget L M Ericsson (Publ) Discarding a duplicate protocol data unit associated with a data transmission via a first signaling radio bearer or a second signaling radio bearer
US20180368196A1 (en) * 2017-06-16 2018-12-20 Huawei Technologies Co., Ltd. Downlink transmission in a ran inactive mode

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100042660A (ko) * 2007-08-14 2010-04-26 콸콤 인코포레이티드 Ｍａｃ프레임들 내부의 ｐｄｃｐ 제어 ｐｄｕ들의 전달
US20130235803A1 (en) * 2010-02-02 2013-09-12 Lg Electronics Inc. Method of selectively applying a pdcp function in wireless communication system
US20160302075A1 (en) * 2013-11-11 2016-10-13 Telefonaktiebolaget L M Ericsson (Publ) Discarding a duplicate protocol data unit associated with a data transmission via a first signaling radio bearer or a second signaling radio bearer
US20180368196A1 (en) * 2017-06-16 2018-12-20 Huawei Technologies Co., Ltd. Downlink transmission in a ran inactive mode

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP; TSGRAN; E-UTRA and EPC; UE conformance specification; Part 1: Protocol conformance specification (Release 15), 3GPP TS 36.523-1 V15.4.0, 19 December 2018 pages 1542-1546, 1608-1609 *

Similar Documents

Publication Publication Date Title
WO2020122617A1 (fr) Procédé de transmission de signaux de liaison montante et dispositif associé
WO2020209669A1 (fr) Procédé de réalisation d'une procédure d'accès aléatoire, et dispositif de transmission, appareil et support de stockage associés
WO2020235956A1 (fr) Procédé de réalisation d'une procédure d'accès aléatoire (ra), et dispositif de transmission, appareil et support de stockage associés, et procédé et appareil pour transmettre une pdu mac d'une procédure de ra
WO2020166859A1 (fr) Procédé et appareil permettant de transmettre un rapport d'état de mémoire tampon au moyen d'un nœud iab dans un système de communication sans fil
WO2020159134A1 (fr) Reconstruction d'unité de données
WO2020116820A1 (fr) Procédé et appareil de transmission de rapport d'état de mémoire tampon par nœud sans fil dans un système de communication sans fil
WO2020180172A1 (fr) Procédé de réalisation d'une procédure d'accès aléatoire, et dispositif de transmission, appareil et support de stockage associés
WO2022025425A1 (fr) Procédé et appareil de transmission de données en liaison montante à base de multiples attributions configurées dans un système de communication sans fil
WO2020138777A1 (fr) Procédé d'émission/réception d'unité de données, et dispositif associé
WO2020222474A1 (fr) Procédure d'accès aléatoire basée sur la qualité de faisceau
WO2020235965A1 (fr) Procédé de réalisation d'une procédure d'accès aléatoire (ra), et dispositif de transmission, appareil et support de stockage associés, et procédé et appareil de transmission de pdu mac de procédure ra
WO2020222520A1 (fr) Appareil et procédé de combinaison de procédure mo edt avec une procédure mt edt dans un système de communication sans fil
WO2020159327A1 (fr) Procédé d'émission/réception d'unité de données et dispositif et support de stockage associés
WO2020122544A1 (fr) Procédé de transmission de rapport de réserve de puissance, et dispositif associé
WO2020222473A1 (fr) Attribution de bande de fréquence pour transmission faisant appel à la radiomessagerie
WO2020159179A1 (fr) Désactivation d'autorisation configurée sur la base du nombre de retransmissions
WO2020166990A1 (fr) Procédé et appareil pour accès initial sur la base d'une classe de priorité d'accès au canal dans un système de communication sans fil
WO2020222545A1 (fr) Activation rapide de groupe de cellules sur la base d'une mesure de cellule unique
WO2020138721A1 (fr) Procédé et appareil pour la transmission d'un rapport de taille de tampon contenant des informations de double bitmap par un nœud sans fil dans un système de communication sans fil
WO2022139152A1 (fr) Procédé et appareil de transmission d'informations de taille de mémoire tampon pour des données volontaires dans un système de communication sans fil
WO2020197237A1 (fr) Activation et transmission de liaison supplémentaire conditionnelle
WO2022030780A1 (fr) Procédé et appareil pour effectuer une procédure de reprise sur défaillance de faisceau dans un système de communication sans fil
WO2020197162A1 (fr) Procédé et appareil permettant de gérer une défaillance de liaison radio sur une fréquence sans licence dans un système de communication sans fil
WO2020159178A1 (fr) Gestion de défaillance de vérification d'intégrité
WO2023058936A1 (fr) Procédé et appareil pour transmettre un rapport de réserve de puissance associé à une cellule de non-desserte dans un système de communication sans fil

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: 20749009

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20749009

Country of ref document: EP

Kind code of ref document: A1