US11856603B2 - Sharing channel occupancy time across nodes of an integrated access backhaul network - Google Patents
Sharing channel occupancy time across nodes of an integrated access backhaul network Download PDFInfo
- Publication number
- US11856603B2 US11856603B2 US17/081,880 US202017081880A US11856603B2 US 11856603 B2 US11856603 B2 US 11856603B2 US 202017081880 A US202017081880 A US 202017081880A US 11856603 B2 US11856603 B2 US 11856603B2
- Authority
- US
- United States
- Prior art keywords
- iab node
- cot
- iab
- node
- channel
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
- 238000004891 communication Methods 0.000 claims abstract description 216
- 238000000034 method Methods 0.000 claims abstract description 163
- 238000001228 spectrum Methods 0.000 claims abstract description 34
- 230000005540 biological transmission Effects 0.000 claims description 199
- 230000008054 signal transmission Effects 0.000 claims description 37
- 238000011144 upstream manufacturing Methods 0.000 claims description 15
- 230000006870 function Effects 0.000 description 27
- 238000005259 measurement Methods 0.000 description 18
- 238000005516 engineering process Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 10
- 238000013459 approach Methods 0.000 description 9
- 238000001514 detection method Methods 0.000 description 8
- 241000700159 Rattus Species 0.000 description 6
- 239000013307 optical fiber Substances 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000006243 chemical reaction Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 4
- 230000000977 initiatory effect Effects 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 230000007774 longterm Effects 0.000 description 3
- 235000008694 Humulus lupulus Nutrition 0.000 description 2
- 101150096310 SIB1 gene Proteins 0.000 description 2
- 101150039363 SIB2 gene Proteins 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 239000002245 particle Substances 0.000 description 2
- 238000005192 partition Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000000926 separation method Methods 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 1
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000008014 freezing Effects 0.000 description 1
- 238000007710 freezing Methods 0.000 description 1
- 230000003116 impacting effect Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000003595 spectral effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 208000037918 transfusion-transmitted disease Diseases 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/14—Spectrum sharing arrangements between different networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
- H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/20—Hop count for routing purposes, e.g. TTL
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/27—Control channels or signalling for resource management between access points
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/14—Backbone network devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0833—Random access procedures, e.g. with 4-step access
Definitions
- This application generally relates to wireless communication systems, and more particularly to methods and systems configured to facilitate the sharing of channel occupancy time (COT) for a channel in an unlicensed 5G spectrum across nodes of an integrated access backhaul (IAB) network.
- COT channel occupancy time
- IAB integrated access backhaul
- Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power).
- Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, and orthogonal frequency division multiple access (OFDMA) systems, (e.g., a Long Term Evolution (LTE) system).
- CDMA code division multiple access
- TDMA time division multiple access
- FDMA frequency division multiple access
- OFDMA orthogonal frequency division multiple access
- a wireless multiple-access communications system may include a number of base stations (BSs), each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE).
- BSs base stations
- UE user equipment
- 5G NR fifth generation new radio
- 5G NR may provision for access traffic and backhaul traffic at gigabit-level throughput.
- Access traffic refers to traffic between an access node (e.g., a base station) and a UE.
- Backhaul traffic refers to traffic among access nodes and a core network.
- an IAB node of the IAB network may perform a channel access procedure to acquire or initiate the COT and share the COT with a parent IAB node and/or a child IAB node for the parent IAB node and/or child IAB node to use the COT for communication with, or in turn share the COT (or what remains thereof) with, another IAB node that is different from the COT-initiating node.
- the sharing of a COT with IAB nodes that are not directly linked to a COT-initiating IAB node can promote the efficient use of IAB network resources.
- a method of wireless communication performed by a first integrated access backhaul (IAB) node comprises receiving, from a second IAB node and for signal transmission by the first IAB node, a first communication signal allowing the first IAB node to access a channel in an unlicensed 5G spectrum during a channel occupancy time (COT).
- the COT can be acquired by the second IAB node.
- the method further comprises communicating a second communication signal with a third IAB node different from the first IAB node to allow the third IAB node to access the channel for signal transmission by the third IAB node during the COT.
- a non-transitory computer-readable medium having program code recorded thereon.
- the program code comprises code for causing a first integrated access backhaul (IAB) node to receive, from a second IAB node and for signal transmission by the first IAB node, a first communication signal allowing the first IAB node to access a channel in an unlicensed 5G spectrum during a channel occupancy time (COT), the COT acquired by the second IAB node.
- the program code comprises code for causing the first IAB node communicate a second communication signal with a third IAB node different from the first IAB node to allow the third IAB node to access the channel for signal transmission by the third IAB node during the COT.
- FIG. 1 illustrates a wireless communication network according to aspects of the present disclosure.
- FIG. 3 illustrates an IAB network according to aspects of the present disclosure.
- FIGS. 6 A- 6 C illustrate operations of an IAB node based on the resource types of the IAB node according to aspects of the present disclosure.
- FIGS. 8 A- 8 D illustrate channel occupancy time (COT) sharing between a next generation NodeB (gNB) and a user equipment (UE) according to aspects of the present disclosure.
- COT channel occupancy time
- FIG. 10 illustrates example COT sharing across IAB nodes of an IAB network according to aspects of the present disclosure.
- FIG. 11 is a block diagram of an example UE according to aspects of the present disclosure.
- An OFDMA network may implement a radio technology such as evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM and the like.
- E-UTRA evolved UTRA
- IEEE Institute of Electrical and Electronics Engineers
- GSM Global System for Mobile communications
- LTE long term evolution
- UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided from an organization named “3rd Generation Partnership Project” (3GPP), and cdma2000 is described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2).
- 3GPP 3rd Generation Partnership Project
- 3GPP long term evolution LTE
- LTE long term evolution
- the 3GPP may define specifications for the next generation of mobile networks, mobile systems, and mobile devices.
- the present disclosure is concerned with the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond with shared access to wireless spectrum between networks using a collection of new and different radio access technologies or radio air interfaces.
- the 5G NR will be capable of scaling to provide coverage (1) to a massive Internet of things (IoTs) with an Ultra-high density (e.g., ⁇ 1 M nodes/km), ultra-low complexity (e.g., ⁇ 10 s of bits/sec), ultra-low energy (e.g., ⁇ 10+ years of battery life), and deep coverage with the capability to reach challenging locations; (2) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (e.g., ⁇ 99.9999% reliability), ultra-low latency (e.g., ⁇ 1 ms), and users with wide ranges of mobility or lack thereof; and (3) with enhanced mobile broadband including extreme high capacity (e.g., ⁇ 10 Tbps/km 2 ), extreme data rates (e.g., multi-Gbps rate, 100+ Mbps user experienced rates), and deep awareness with advanced discovery and optimizations.
- IoTs Internet of things
- ultra-high density e.g., ⁇ 1 M nodes/km
- the 5G NR may be implemented to use optimized OFDM-based waveforms with scalable numerology and transmission time interval (TTI); having a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD)/frequency division duplex (FDD) design; and with advanced wireless technologies, such as massive multiple input, multiple output (MIMO), robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility.
- TTI numerology and transmission time interval
- SCS may occur with 15 kHz, for example over 5, 10, 20 MHz, and the like bandwidth (BW).
- BW bandwidth
- SCS may occur with 30 kHz over 80/100 MHz BW.
- the SCS may occur with 60 kHz over a 160 MHz BW.
- the SCS may occur with 120 kHz over a 500 MHz BW.
- the scalable numerology of the 5G NR facilitates scalable TTI for diverse latency and quality of service (QoS) requirements. For example, shorter TTI may be used for low latency and high reliability, while longer TTI may be used for higher spectral efficiency.
- QoS quality of service
- 5G NR also contemplates a self-contained integrated subframe design with uplink (UL)/downlink (DL) scheduling information, data, and acknowledgement in the same subframe.
- the self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive UL/downlink that may be flexibly configured on a per-cell basis to dynamically switch between UL and downlink to meet the current traffic needs.
- COT-sharing across IAB nodes of an IAB network improves the efficient use of IAB network resources. This is because a COT acquired by a first IAB node (but not used entirely by the first IAB node for a DL or UL transmission) can be shared by the first IAB node with its parent IAB node or child IAB node, and the parent IAB node or child IAB node may use the COT for communication with, or in turn share the remaining COT with, additional IAB nodes that are different from the COT-initiating IAB node, thereby allowing the complete or nearly complete use of the COT.
- COT-sharing across IAB nodes of an IAB network allows the IAB network to have low latency, as the IAB nodes can use already acquired COT for communication with other IAB nodes after performing a type2 channel access procedure rather than performing a type1 channel access procedure, wherein normally a type2 procedure is much simpler and quicker procedure for evaluating the idleness of channel for next transmission.
- a channel access procedure can refer to a procedure based on sensing that evaluates the availability of a channel for performing transmissions, as discussed in the 3GPP standard document technical specification “3GPP TS 37.213 (Release 16)”, which is incorporated herein by reference in its entirety.
- the COT-sharing may improve the capabilities of IAB networks to provide extremely high data rates to network users.
- FIG. 1 illustrates a wireless communication network 100 according to aspects of the present disclosure.
- the network 100 includes a plurality of BSs 105 , a plurality of UEs 115 , and a core network 130 .
- the network 100 may be a LTE network, a LTE-A network, a millimeter wave (mmW) network, a new radio (NR) network, a 5G network, or any other successor network to LTE.
- mmW millimeter wave
- NR new radio
- the BSs 105 may wirelessly communicate with the UEs 115 via one or more BS antennas. Each BS 105 may provide communication coverage for a respective geographic coverage area 110 .
- the term “cell” can refer to this particular geographic coverage area of a BS and/or a BS subsystem serving the coverage area, depending on the context in which the term is used.
- the BSs 105 a , 105 b , 105 c , 105 d , and 105 e are examples of macro BSs for the coverage areas 110 a , 110 b , 110 c , 110 d , and 110 e , respectively.
- Communication links 125 shown in the network 100 may include uplink (UL) transmissions from a UE 115 to a BS 105 , or downlink (DL) transmissions, from a BS 105 to a UE 115 .
- the communication links 125 are referred to as wireless access links.
- the UEs 115 may be dispersed throughout the network 100 , and each UE 115 may be stationary or mobile.
- a UE 115 may also be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
- a UE 115 may also be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a personal electronic device, a handheld device, a personal computer, a wireless local loop (WLL) station, an Internet of things (IoT) device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, an appliance, an automobile, or the like.
- PDA personal digital assistant
- WLL wireless local loop
- IoT Internet of things
- IoE Internet of Everything
- MTC machine type communication
- the BSs 105 may communicate with the core network 130 and with one another via optical fiber links 134 .
- the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
- IP Internet Protocol
- At least some of the BSs 105 (e.g., which may be an example of an evolved NodeB (eNB), a next generation NodeB (gNB), or an access node controller (ANC)) may interface with the core network 130 through the backhaul links 134 (e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communication with the UEs 115 .
- the BSs 105 may communicate, either directly or indirectly (e.g., through core network 130 ), with each other over the backhaul links 134 (e.g., X1, X2, etc.).
- the BSs 105 can assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks) for DL and UL transmissions in the network 100 .
- DL refers to the transmission direction from a BS 105 to a UE 115
- UL refers to the transmission direction from a UE 115 to a BS 105 .
- the communication can be in the form of radio frames.
- a radio frame may be divided into a plurality of subframes, for example, about 10.
- Each subframe can be divided into slots, for example, about 2.
- FDD frequency-division duplexing
- each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band.
- TDD time-division duplexing
- UL and DL transmissions occur at different time periods using the same frequency band.
- a subset of the subframes (e.g., DL subframes) in a radio frame may be used for DL transmissions and another subset of the subframes (e.g., UL subframes) in the radio frame may be used for UL transmissions.
- each DL or UL subframe may have pre-defined regions for transmissions of reference signals, control information, and data.
- Reference signals are predetermined signals that facilitate the communications between the BSs 105 and the UEs 115 .
- a reference signal can have a particular pilot pattern or structure, where pilot tones may span across an operational bandwidth or frequency band, each positioned at a pre-defined time and a pre-defined frequency.
- a BS 105 may transmit cell-specific reference signals (CRSs) and/or channel state information-reference signals (CSI-RSs) to enable a UE 115 to estimate a DL channel.
- CRSs cell-specific reference signals
- CSI-RSs channel state information-reference signals
- a UE 115 may transmit sounding reference signals (SRSs) to enable a BS 105 to estimate a UL channel.
- Control information may include resource assignments and protocol controls.
- Data may include protocol data and/or operational data.
- the BSs 105 and the UEs 115 may communicate using self-contained subframes.
- a self-contained subframe may include a portion for DL communication and a portion for UL communication.
- a self-contained subframe can be DL-centric or UL-centric.
- a DL-centric subframe may include a longer duration for DL communication.
- a UL-centric subframe may include a longer duration for UL communication.
- a UE 115 attempting to access the network 100 may perform an initial cell search by detecting a primary synchronization signal (PSS) from a BS 105 .
- PSS primary synchronization signal
- the UE 115 may then receive a secondary synchronization signal (SSS).
- SSS may enable radio frame synchronization, and may provide a cell identity value, which may be combined with the physical layer identity value to identify the cell.
- the SSS may also enable detection of a duplexing mode and a cyclic prefix length.
- Some systems, such as TDD systems may transmit an SSS but not a PSS. Both the PSS and the SSS may be located in a central portion of a carrier, respectively.
- the UE 115 may receive a master information block (MIB), which may be transmitted in the physical broadcast channel (PBCH).
- the MIB may contain system bandwidth information, a system frame number (SFN), and a Physical Hybrid-ARQ Indicator Channel (PHICH) configuration.
- SIBs system information blocks
- SIB1 may contain cell access parameters and scheduling information for other SIBs. Decoding SIB1 may enable the UE 115 to receive SIB2.
- FIG. 3 illustrates an IAB network 300 according to aspects of the present disclosure.
- the network 300 is similar to the network 200 and illustrates the use of millimeter wave (mmWave) frequency band for communications.
- a single BS e.g., the BS 105 c
- the other BSs 105 a , 105 b , 105 d , and 105 e communicate with each other and with the BS 105 c using directional beams 334 , for example, over the wireless links 234 .
- the BSs 105 may also communicate with the UEs 115 using narrow directional beams 325 , for example, over the wireless links 125 .
- the anchor 410 may also be known as an IAB donor and may include the function of controlling the IAB network topology 400 through configurations as well as the function of scheduling the communications of child IAB nodes or UEs (i.e., the IAB nodes or UEs directly linked to it via links 404 ).
- the anchor or IAB donor 410 includes a central unit (CU) that performs the former functions and a distributed unit (DU) that performs the latter functions.
- CU central unit
- DU distributed unit
- the CU can be a logical node hosting radio resource control (RRC), service data adaptation protocol (SDAP) and packet data convergence protocol (PDCP) of the anchor or IAB donor while the DU can be a logical node hosting radio link control (RLC), medium access control (MAC) and physical (PHY) layers of the anchor or IAB donor 410 .
- the CU and the DU may be connected via an F1 interface, the application protocol (F1-AP) of which can be used for conveying the lower-layer configuration information of the radio bearers between the CU and DU, as well as for setting up of a General Packet Radio Services (GPRS) tunneling protocol (GTP) tunnel between the DU and CU for each radio bearer.
- GPRS General Packet Radio Services
- the topology 400 includes a plurality of logical levels 402 .
- the topology 400 includes three levels 402 , shown as 402 a , 402 b , and 402 c .
- the topology 400 can include any suitable number of levels 402 (e.g., two, three, four, five, or six).
- Each level 402 may include a combination of UEs 115 and BSs 105 interconnected by logical links 404 , shown as 404 a , 404 b , and 404 c .
- a logical link 404 between a BS 105 and a UE 115 may correspond to a wireless access link 125
- a logical link 404 between two BSs 105 may correspond to a wireless backhaul link 234
- the BSs 105 and the UEs 115 may be referred to as relay nodes in the topology 400 .
- a BS 105 may implement both ACF and UEF and may function as an ACF-node and an UEF-node depending on which node the BS is communicating with.
- a BS 105 in the level 402 b may function as an access node when communicating with a BS 105 or a UE 115 in the level 402 c .
- the BS 105 may function as a UE when communicating with a BS 105 in the level 402 a .
- the communication is referred to as a UL communication.
- the communication is referred to as a DL communication.
- the anchor 410 may allocate resources for the links 404 .
- FIG. 4 B shows an example IAB network with a network core 495 linked via a wireline fiber 485 to an IAB donor 455 including a CU 415 and a DU 425 and IAB donor 455 linked via link 472 to an IAB node 465 .
- the entity or node of an IAB node 465 that functions as the ACF-node of the IAB node may be referred to as the DU 445 of the IAB node 465 and the entity or node of an IAB node 465 that functions as the UEF-node of the IAB node may be referred as the mobile termination (MT) 435 of the IAB node 465 .
- MT mobile termination
- the MT 435 of an IAB node 465 can be a scheduled node (e.g., similar to a UE) with its communications scheduled by the parent IAB-node 455 (i.e., the communications of MT 435 can be scheduled by its parent DU 425 of its parent IAB 455 ) or the IAB-donor (i.e., the anchor 410 ) and the DU 425 of an IAB node 455 can be a scheduling node that schedules the communications of child IAB node 465 (e.g., schedule its child MT 435 of the child IAB node 465 ) of that IAB node 465 .
- a DU 445 of a IAB node 465 may also schedule or control a UE 475 .
- the DU of an IAB node e.g., BS
- the CU of the IAB donor e.g., BS
- the logical node of the hosting RRC, SDAP and PDCP may function as the logical node of the hosting RRC, SDAP and PDCP.
- FIGS. 5 A- 5 C illustrate duplex capabilities of an IAB node according to aspects of the present disclosure.
- IAB nodes e.g., such as IAB nodes 105 or 465
- IAB nodes 105 or 465 can support duplex capabilities, i.e., the radio or communication resources of an IAB node may be orthogonally partitioned between the access links and the backhaul links of the IAB node according to the multiplex capabilities of the IAB node, which include partitioning the radio or communication resources of the node in time (i.e., time division multiplexing (TDM) capabilities), in frequency (i.e., frequency division multiplexing (FDM) capabilities), and in space (i.e., space division multiplexing (SDM) capabilities).
- TDM time division multiplexing
- FDM frequency division multiplexing
- SDM space division multiplexing
- FIG. 5 A shows an example schematic illustration of a IAB node 502 where the resources of the IAB node 502 are partitioned in time (i.e., using TDM capabilities of the IAB node) between the IAB node's backhaul links 504 and the access or child links 506 .
- the access or child links between the DU of the IAB node 502 and the child MT (i.e., the MT of its child IAB node 514 ) or a UE 516 may be inactive ( 508 ) or inactive ( 506 ), respectively.
- the radio resources of the IAB node may be partitioned in time between the backhaul links ( 504 or 510 ) and the access links ( 506 or 508 ) during in-band operations of the IAB node 502 .
- FIG. 5 B shows an example schematic illustration of a IAB node 518 where the resources of the IAB node 518 are partitioned in space (i.e., using SDM capabilities of the IAB node) and the IAB node's backhaul links and access or child links are engaged simultaneously in signal reception RX (e.g., 520 and 522 ) or signal transmission TX (e.g., 524 and 526 ).
- RX reception RX
- TX signal transmission
- FIGS. 6 A- 6 C illustrate operations of an IAB node based on the resource types of the IAB node according to aspects of the present disclosure.
- TDM of the resources of the IAB nodes may be employed to facilitate communication between neighboring IABs.
- the DU and/or MT time-domain resources of a IAB node can be configured as uplink (UL), downlink (DL) and flexible (F) to indicate the allowed transmission directions for that resource type (DU or MT).
- a MT resource's configuration may not necessarily indicate that the MT is available in the configured transmission direction, since the availability of a MT resource can depend on the configuration of the corresponding DU resource.
- the availabilities of the DU and MT resources can be coordinated by configuring the DU resources as hard (H), soft (S) and not available (NA), as discussed in the 3GPP standard document technical specification (TS) 38.873, titled “Study on Integrated Access and Backhaul (3GPP TS 38.873)”, which is incorporated herein by reference in its entirety.
- resources may be configured as downlink-only, uplink-only, flexible, or not available (e.g., unavailable).
- a resource is configured as downlink-only for an IAB node, that time resource may be available for only downlink communications of the IAB node, and not uplink communications.
- a time resource is configured as uplink-only for an IAB node, that resource may be available for only uplink communications of the IAB node, and not downlink communications.
- a resource is configured as flexible for an IAB node, that resource may be available for both downlink communications and uplink communications of the IAB node.
- the resource When a resource is configured as not available for an IAB node DU, the resource may not be used for any communications by the IAB node DU with its child IAB node. It should be noted that the techniques and apparatuses described herein for time resources can be applied for any type of resource (e.g., frequency resource, spatial resource, code resource, and/or the like).
- resources in an IAB network that are configured as downlink-only, uplink-only, or flexible may be further configured as hard resources or soft resources.
- a resource is configured as a hard resource for an IAB node DU
- the resource can be always available for communications by the IAB node DU with its child IAB node.
- a hard downlink-only resource can always be available for only downlink communications of the IAB node DU
- a hard uplink-only resource can always be available for only uplink communications of the IAB node DU
- a hard flexible resource can always be available for uplink and downlink communications of the IAB node DU.
- a hard DU configuration indicates that the DU resource is available for the DU in the configured transmission direction without the IAB node that includes the DU having to consider the impact of the availability on the resources of the corresponding MT (i.e., MT of the same IAB). That is, hard DU resources can indicate that the DU resources are available for transmission/reception (TX/RX) by the DU while the MT resources are unavailable regardless of the configurations of the MT resource. That is, when DU resources are configured as hard, it cannot be guaranteed that the MT can properly transmit or receive on these resources while the DU can use these resources regardless of the MT resource configurations.
- TX/RX transmission/reception
- FIG. 6 B shows a schematic illustration of hard DU resources configured for downlink (DL) 606 , uplink (UL) 608 and flexible (F) 604 transmission by a DU of a IAB node may be available regardless of the configurations of the MT (e.g., 602 ) of the same IAB.
- a Not Available DU configuration such as the example illustration shown in FIG. 6 A , indicates that the N/A DU resource 610 may not be available for the DU, and as such, the DU cannot assume or expect the resource to be available for its TX/RX.
- a MT's or UE's resource configuration for TX/RX may be scheduled by a parent IAB node or via an radio resource control (RRC) configuration message from the control unit (CU) of the IAB-donor (of the IAB network of which the IAB is a part).
- RRC radio resource control
- a soft resource When a resource is configured as a soft resource for an IAB node DU, the availability of that resource can be controlled by a parent node of the IAB node. For example, the parent node may indicate (e.g., explicitly or implicitly) whether a soft resource is available for communications of the IAB node DU.
- a soft resource may be in one of two states: an available state (e.g., when the soft resource can be available for scheduling and/or communications of the IAB node DU) and a non-available state (e.g., when the soft resource may not be available for scheduling and may not be available for communications of the IAB node DU).
- a soft DU configuration can come in two states, an available state and a non-available state.
- An available state is where the IAB node has indication from its parent IAB node that the DU resource configured as available has been indicated, explicitly or implicitly, as available.
- a parent IAB node may indicate, via a downlink control information (DCI) transmission (e.g., such as DCI2_5 message), that the DU resource is available for transmission by the DU.
- DCI downlink control information
- a non-available state is where the IAB node has no indication from its parent IAB node that the DU resource configured as non-available has been indicated, explicitly or implicitly, as available.
- an available DU resource may be considered as a hard DU resource, and a non-available resource may be considered as a N/A DU resource.
- a soft DU resource may indicate that the soft DU resource can be used by the DU if that does not impact the MT's ability to transmit and/or receive according to the MT's configuration and scheduling.
- a DU resource may be configured as soft DU.
- the DU can use the soft DU resource for TX/RX.
- a DU can use a soft DU configured resource provided the DU's use is not impacting the MT's TX/RX.
- a IAB network includes multiple IAB nodes (e.g., BSs) communicating with each other, either directly or indirectly (e.g., through the core network of the IAB network), over backhaul links and UEs communicating with the IAB nodes via access links (e.g., wireless access links).
- IAB nodes e.g., BSs
- backhaul links e.g., wireless access links
- UEs communicating with the IAB nodes via access links (e.g., wireless access links).
- NR-U The operations or deployments of NR in an unlicensed spectrum is referred to as NR-U.
- One approach to avoiding collisions when communicating in a shared spectrum or an unlicensed spectrum is to use a listen-before-talk (LBT) channel access procedure to ensure that the shared channel is clear before transmitting a signal in the shared channel.
- LBT listen-before-talk
- FIGS. 7 A- 7 D illustrate such channel access procedures for NR-U according to aspects of the present disclosure
- the device can proceed to the backoff stage.
- the device can select a random whole number N in ⁇ 0, . . . , CW ⁇ , where CW is the contention window.
- CCA may then be performed for each observation slot and can result either in decrementing N by 1 (e.g., 708 ) or freezing the backoff procedure.
- N a transmission 710 may commence.
- the length of the transmission 710 i.e., the channel occupancy time (COT) for the device, can be upper bounded by a maximum channel occupancy time (MCOT T mcot ) (e.g., no greater than 10 ms) which can vary based on the priority class of the transmission.
- MCOT T mcot maximum channel occupancy time
- a transmission with a lower or higher priority class number may have a higher or lower chance of acquiring a channel because the contention window (CW) has shorter or longer duration, respectively.
- the responding device may send an immediate acknowledgement (e.g., without a CCA) and reset CW to the minimum value of CW, CW min .
- FIGS. 7 C- 7 D show example schematic illustrations of type 2 LBT channel access procedures according to some aspects of the present disclosure.
- Type 2 channel access procedures refer to LBT with no random back-off but rather deterministic CCA or channel sensing period.
- FIG. 7 C shows example schematic illustration of type 2A LBT channel access procedure according to some aspects of the present disclosure.
- Type 2A refers to a channel access procedure with a deterministic channel sensing period of 25 ⁇ s for when the gap between a UL physical uplink shared channel (PUSCH) transmission grant being transmitted in a DL direction and the UL PUSCH transmission start time may be 25 ⁇ s or more (e.g., can be as long as several ms).
- PUSCH physical uplink shared channel
- the channel sensing period is 25 ⁇ s when the gap between an UL transmission and a DL transmission is exactly 25 ⁇ s, and in some respects, the channel access procedure is a type 2A channel access procedure only when the transmission gap is exactly equal to 25 microseconds.
- Channel sensing 712 may occur for at least 4 ⁇ s within a 9 ⁇ s period 714 of the gap.
- Type 2B channel access procedure refers to a channel access procedure with a deterministic channel sensing period of 16 ⁇ s, i.e., a 16 ⁇ s sensing period is required before a transmission can commence, and can be applicable for when the gap between an UL transmission and a DL transmission, between an UL transmission and an UL transmission, between a DL transmission and an UL transmission, or between a DL transmission and a DL transmission is equal to 16 ⁇ s.
- Channel sensing 716 may occur for at least 4 ⁇ s within a 9 ⁇ s period 718 of the gap.
- An example illustration of a listen-before-talk (LBT) channel access procedure is shown in FIG. 7 E .
- FIG. 7 E shows a timing diagram illustrating a listen-before-talk (LBT) channel access procedure according to some aspects of the present disclosure.
- the scheme 750 may be employed by a BS such as the BSs 105 and a UE such as the UEs 115 in a network such as the network 100 .
- a BS or a UE may employ scheme 750 to determine measurement periods within a link switch duration for LBT measurements.
- the x-axis represents time in some constant units.
- a wireless communication device receives a communication signal 760 (shown as Rx signal) and completes the reception at time T 0 in a certain link direction (e.g., UL or DL). After receiving the communication signal 760 , the wireless communication device switches to another link direction (e.g., UL-to-DL or DL-to-UL) and transmits a communication signal 770 (shown as Tx signal) starting at time T 1 .
- a communication signal 760 shown as Rx signal
- the wireless communication device switches to another link direction (e.g., UL-to-DL or DL-to-UL) and transmits a communication signal 770 (shown as Tx signal) starting at time T 1 .
- the wireless communication device corresponds to a BS
- the communication signal 760 is an UL communication signal (e.g., including PUSCH data and/or physical uplink control channel (PUCCH) control information transmitted by a UE)
- the communication signal 770 corresponds to a discovery reference signal (DRS) (e.g., including synchronization signal blocks (SSBs)) or any DL communication signal including Physical Downlink Shared Channel (PDSCH) data and/or Physical downlink Control Channel (PDCCH) control information.
- DRS discovery reference signal
- SSBs synchronization signal blocks
- PDSCH Physical Downlink Shared Channel
- PDCCH Physical downlink Control Channel
- the wireless communication device corresponds to a UE
- the communication signal 760 is a DL communication signal (e.g., including PDSCH data and/or PDCCH control information transmitted by a BS)
- the communication signal 770 corresponds to a scheduled UL transmission (e.g., including PUSCH data and/or PUCCH control information) in a COT acquired or reserved by the BS.
- the wireless communication device may perform a LBT channel access procedure (e.g., a type 2 LBT) prior to transmitting the communication signal 770 .
- the switching gap can be longer than the duration of the measurement period considered for LBT.
- the time or gap between a UL PUSCH transmission grant being transmitted in a DL direction and the UL PUSCH transmission start time may be as long as several ms, but the LBT may be performed for just a fixed duration (e.g., about 25 ⁇ s) prior to the PUSCH transmission.
- a fixed duration LBT channel access procedures type 2 LBT
- a BS may use a fixed duration (e.g., about 25 ⁇ s) LBT just prior to the DRS transmission.
- the scheme 750 time-partitions a link switch gap duration 752 between the received communication signal 760 and the scheduled or upcoming transmit communication signal 770 or more generally the type 2 LBT duration into about three slots 754 (shown as 754 S(1) , 754 S(2) , and 754 S(3) ).
- the link switch gap duration 752 may be about 25 ⁇ s
- the slot 754 S(1) may have a duration of about 9 ⁇ s
- the slot 754 S(2) may have a duration of about 7 ⁇ s
- the slot 754 S(3) may have a duration of about 9 ⁇ s.
- the scheme 750 allows LBT measurements during the slots 754 S(1) and 754 S(3) , but not during the slot 754 S(2) . Additionally, the scheme 750 requires an LBT measurement duration of at least 4 ⁇ s. LBT measurements may refer to energy detection or measurements.
- the wireless communication device may determine whether the channel is available by performing energy detection during a measurement period 756 a within the slot 754 S(1) and during a measurement period 756 b within the slot 754 S(3) .
- the wireless communication device measures channel energy for a duration of at least 4 ⁇ s to determine a channel status (e.g., idle or occupied).
- a channel status e.g., idle or occupied.
- each of the measurement periods 756 a and 756 b may have a duration of at least 4 ⁇ s.
- the wireless communication device may select any 4 ⁇ s within the slots 754 S(1) and 754 S(3) for channel energy measurements and refrain from performing energy detection during the slot 754 S(2) .
- the wireless communication device may perform energy detection in a beginning portion of the slot 754 S(1) or the slot 754 S(3) and use the remaining time of the corresponding slots 754 for processing the energy measurement.
- An LBT channel access procedure is a pass when the measurements in the measurement periods 756 a and 756 b are below a certain energy detection threshold. Conversely, an LBT channel access procedure fails when the measurement in the measurement period 756 a or the measurement in the measurement period 756 b is equal to or greater than the energy detection threshold.
- a device such as a BS may perform a channel access procedure (e.g., type 1 LBT channel access procedure) to acquire or reserve a COT for a channel in an unlicensed 5G spectrum for signal transmission to a UE.
- a channel access procedure e.g., type 1 LBT channel access procedure
- the COT may be longer than what is needed for transmission by the BS and the BS may share the COT with the UE so that the UE may use part of the COT for signal transmission back to the BS.
- the BS may explicitly indicate, via an UL scheduling grant, what kind of channel access procedure the UE must perform to be able to access the channel and use the COT for an UL transmission to the BS.
- the BS may indicate to the UE, via the UL scheduling grant, the type of channel access procedure the UE may perform to access the channel within the COT depending on the gap between the DL transmission from the BS and the UL transmission by the UE, i.e., depending on which condition of the type 1 or type 2 channel access procedures that the gap meets.
- the BS may indicate to the UE to perform type 2A, type 2B or type 2C channel access procedure if the gap is 25 ⁇ s, 16 ⁇ s or less than or equal to 16 ⁇ s, respectively.
- a BS 802 may perform a type 1 channel access procedure 804 to acquire a COT 806 that is no greater in duration than the sum of MCOT (T mcot ) and T g , and the BS 802 may use some of the COT 806 for a DL transmission 808 to the UE 810 .
- T g can be the total duration of all gaps of duration greater than 25 ⁇ s that can occur between the DL transmission of the BS and UL transmissions scheduled by the BS, and between any two UL transmissions scheduled by the BS starting from t o , where t o is the time instance where BS has started transmission.
- the BS 802 may perform type 2 channel access procedure 818 to access this available COT for additional DL transmission 820 .
- the x-axis represents time in some arbitrary units.
- FIG. 8 B is a timing diagram illustrating the sharing of a BS initiated COT between the BS and a UE according to some aspects of the present disclosure.
- the COT sharing may be initiated by BSs such as the BSs 105 for COT sharing with UEs such as the UEs 115 in a network such as the network 100 .
- the x-axis represents time in some arbitrary units.
- the UE Upon receiving the UL scheduling grant 826 , the UE performs a type 2 procedure 828 prior to the scheduled time T 0 .
- a type 2 procedure may be referred to as channel access procedure without a random backoff.
- a type 2 procedure may also be referred to as a one-shot LBT.
- the UE transmits a UL communication signal 830 based on the UL scheduling grant 826 .
- the UL communication signal 830 can include UL data and/or UL control information.
- the UL data may be carried in a PUSCH and the UL control information may be carried in a PUCCH.
- the UL control information may include scheduling request, channel information (e.g., CSI reports), and/or hybrid automatic repeat request (HARQ) acknowledgement/negative-acknowledgement (ACK/NACK) feedbacks.
- HARQ hybrid automatic repeat request
- the COT may initially be initiated or acquired by the UE as part of a UL transmission to the BS and may be shared with the BS for a DL transmission by the BS to the UE.
- the UE may initiate a COT in a channel of an unlicensed 5G spectrum by performing a type 1 channel access procedure and use some of the COT for an UL transmission, and share the remaining COT with the BS for an UL transmission by the BS to the UE.
- the BS may autonomously determine what type of channel access procedure to perform to access the COT. This is because, since DL/UL communications between the BS and the UE are controlled by the BS, the BS may have information about remaining COT.
- the channel access priority class can be pre-defined (e.g., in a specification).
- FIG. 8 C shows an example schematic illustration of a COT initiated by a UE and shared with a BS.
- the UE 852 may perform a type 1 channel access procedure 856 to acquire a COT 806 that is no greater in duration than the MCOT (T mcot ), and the UE 852 may use some of the COT 858 for a UL transmission 860 to the BS 850 .
- the UL transmission 860 may also include a GC-UCI 862 indicating the COT remaining after the UL transmission 860 by the UE 852 .
- the BS 850 may perform a type 2 channel access procedure 864 for an DL transmission 866 to the UE 852 .
- the x-axis represents time in some arbitrary units.
- the UE may share the COT 876 with the BS for DL communication.
- the UE includes COT sharing information 880 in the UL communication signal 878 .
- the COT sharing information 880 may indicate that the BS is allowed to share the UE's COT 876 for communication.
- the COT sharing information 880 may indicate a sharable portion of the UE's COT 876 starting at a time 882 (e.g., at time T 1 ) with a duration 884 as shown by the dashed-dotted box.
- a BS may be allowed to use a COT the BS initiated or acquired for DL/UL communications with a UE for other DL/UL communications related to the BS (e.g., for DL/UL communications with another UE that the BS is connected to). For instance, if the COT is initiated by BS for communication with a first UE, the BS can use the COT for communication with a second UE as long as the gap between the DL transmissions to the first UE and the second UE is no greater than 16 ⁇ s.
- the IAB network 450 includes an IAB node 465 linked to another IAB node 466 via a backhaul link 468 and to a UE 475 via an access link 476 .
- each IAB node may include a DU and an MT where the DU may serve as a parent DU node to a child MT of a child IAB node and the MT may serve as a child node to a parent DU of a parent IAB node.
- IAB node 465 may include a DU 445 that functions as a parent DU node to the child MT 478 of the child IAB node 466 as well as a child MT node 435 that is a child MT to a parent DU node 425 .
- an IAB node may or may not be available for communication based on its resource type.
- FIGS. 9 A- 9 B illustrate example COT sharing of COT initiated for communications by a DU and a MT, respectively, of an IAB node across IAB nodes of an IAB network, according to aspects of the present disclosure.
- the DU of the IAB node 908 may then transmit a DL transmission 922 to a UE or a third IAB node 910 that is different from the COT-initiating node 902 and can be along downstream signal path (i.e., away from the IAB donor of the IAB network).
- the DL transmission 922 may include a DCI transmission 924 (e.g., DCI2_0 message, DCI2_5 message) including information about the COT 914 remaining after the DL transmission 922 and about a type of channel access procedure the IAB node or UE 910 may perform to access this remaining COT.
- the MT of the IAB node 904 may perform a type 2 channel access procedure 934 (e.g., type 2A) to access the remaining COT despite the indication from the UL signal 932 about performing type 1 channel access procedure, provided the conditions for the type 2 procedure are fulfilled by the shared (i.e., remaining) COT.
- the MT of the IAB node 904 may then transmit an UL transmission 936 to a third IAB node 906 that is different from the COT-initiating node 902 and can be along upstream signal path (i.e., towards the IAB donor of the IAB network).
- the UL transmission 936 may also include a UL signal 938 that includes information about the COT 914 remaining after the UL transmission 930 and about a type of channel access procedure the IAB node 906 may perform to access this remaining COT for further transmission.
- FIG. 9 B illustrates example COT sharing, across IAB nodes of an IAB network, of COT initiated for communications by a MT of an IAB node, according to aspects of the present disclosure.
- the MT of the IAB node 952 may acquire a COT 964 for a channel in a unlicensed 5G spectrum by performing a type 1 channel access procedure 962 , which the MT, after transmitting an UL transmission 966 , shares with the parent IAB node 954 for the parent IAB node's further transmission (e.g., UL transmission 972 ) to a third IAB node 956 positioned along an upstream signal path towards from the IAB donor of the IAB network.
- a type 1 channel access procedure 962 which the MT, after transmitting an UL transmission 966 , shares with the parent IAB node 954 for the parent IAB node's further transmission (e.g., UL transmission 972 ) to a third IAB node 956 positioned along an upstream signal path
- the COT 964 may have an associated maximum COT.
- the child IAB node's UL transmission 972 may be to a third IAB node positioned along an upstream signal path towards an IAB donor of the IAB network.
- the UL transmission 966 from the MT of the IAB node 952 may include an UL signal 968 having information about the type of channel access procedure performed by the MT prior to the UL transmission 966 .
- the UL signal 968 may also include information related to COT sharing, for example, the amount of COT remaining after the transmission by the MT.
- the parent DU may share the COT with the co-located MT of the same IAB node 954 , which allows the co-located MT to access the COT by performing a type 2 channel access procedure 970 .
- the UL transmission 966 may include an UL signal 968 for the parent DU having COT sharing information (e.g., remaining COT available for sharing after UL transmission 966 ). Such information may be used in determining whether it can perform type 2 channel access procedure to access the COT.
- the parent DU may not have this information otherwise (i.e., without receiving it via the UL signal 932 because the parent DU may not control the DU of the IAB node 902 ).
- the MT of the IAB node 954 may then transmit an UL transmission 972 to a third IAB node 956 that is different from the COT-initiating node 952 and can be along upstream signal path (i.e., towards the IAB donor of the IAB network).
- the UL transmission 972 may include an UL signal 974 including information about the COT 964 remaining after the UL transmission 972 and about a type of channel access procedure the IAB node 956 may perform to access this remaining COT.
- the DU of COT-initiating IAB node 952 may transmit a DL transmission 976 that includes a DCI transmission 978 (e.g., DCI2_0 message, DCI2_5 message) indicating to the IAB node 958 the type of channel access procedure (e.g., type 1 channel access procedure) to be performed to access the shared COT.
- the DCI transmission 978 may also include COT-related information, such as the COT remaining after the DL transmission 976 by the DU of the IAB node 952 .
- the child MT of the IAB node 958 may share the COT with the co-located DU of the same IAB node 958 , which allows the co-located DU to access the COT by performing a type 2 channel access procedure 980 .
- the co-located DU of the IAB node 958 may then perform a type 2 channel access procedure 920 (e.g., type 2A) to access the remaining COT 954 despite the indication from the DCI transmission 918 about performing type 1 channel access procedure, provided the conditions for the type 2 procedure are fulfilled by the shared (i.e., remaining) COT.
- a type 2 channel access procedure 920 e.g., type 2A
- the DU of the IAB node 908 may then transmit a DL transmission 982 to a UE or a third IAB node 960 that is different from the COT-initiating node 952 and can be positioned along downstream signal path (i.e., away from the IAB donor of the IAB network).
- the DL transmission 982 may include a DCI transmission 984 (e.g., DCI2_0 message, DCI2_5 message) including information about the COT 964 remaining after the DL transmission 982 and about a type of channel access procedure the IAB node or UE 960 may perform to access this remaining COT.
- the example COT-sharing illustrated in FIG. 9 B allows for a COT initiated for transmission by a MT of an IAB node 952 to be used for communication with, or to be shared with, IAB nodes (e.g., IAB nodes 956 and 960 ) that are not directly linked to the COT-initiating IAB node 952 . That is, with the COT-sharing approach illustrated in FIG. 9 B , a COT may be used by a neighboring IAB node (e.g., IAB nodes 954 and 958 ) to communicate with IAB nodes that are further away from, and not directly linked to, the COT-initiating IAB node 952 .
- a neighboring IAB node e.g., IAB nodes 954 and 958
- the COT-sharing approach allows the COT to be shared with IAB nodes (e.g., IAB nodes 956 and 960 ) that are more than one backhaul or access links away from the COT-initiating IAB 902 .
- IAB nodes e.g., IAB nodes 956 and 960
- COT-sharing approach improves efficiency of the use of IAB network resources.
- an IAB node that received a COT from a COT-initiating IAB node may share the COT with a third IAB node that may be positioned along the same upstream or downstream signal path from the IAB donor of the IAB network that includes the IAB nodes and the IAB donor.
- IAB node 904 after receiving a COT from COT-initiating IAB node 902 , shares the COT with IAB node 906 , which is positioned along the same signal path from or away the IAB donor as the COT-receiving IAB node 904 .
- the COT-receiving IAB node may be positioned along the opposite signal path with respect to the IAB donor.
- FIG. 10 shows a COT-initiating IAB node 1002 initiating or acquiring a COT 1022 for a DL transmission 1010 to child IAB node 1004 by performing a type 1 channel access procedure 1008 (e.g., substantially similar to IAB node 902 acquiring COT 914 ).
- the COT-initiating IAB node 1002 may share the COT 1022 with IAB node 1004 , which the MT of the latter accesses by performing a type 2 channel access procedure 1012 .
- the MT of the IAB node 1004 may transmit an UL signal 1014 to share the COT with a different parent IAB node 1006 that is different from the parent IAB node from which IAB node 1004 initially received the COT 1022 .
- the child IAB node 1004 may share the COT 1022 with an IAB node 1006 that is positioned, with respect to the child IAB node 1004 , along a signal path (e.g., upstream towards or downstream away from the IAB donor of the IAB network) that is opposite to the signal path of the child IAB node with respect to the COT-initiating IAB node 1002 .
- the UL signal 1014 may include a request from the MT of IAB node 1004 to the parent DU (i.e., DU of the parent IAB node 1006 ) for the parent DU to perform a specific type of channel access procedure in transmission a DL transmission to the MT.
- the IAB node 1006 may then perform, for example based on the request in the UL signal 1014 , a type 2 channel access procedure 1016 to access the COT 1022 for further transmission (e.g., such as DL transmission 1018 back to IAB node 1004 or another IAB node linked to it by a backhaul or access link).
- the sharing of COT across IAB nodes of an IAB network as discussed, for example, with respect to FIGS. 9 A- 9 B and FIG. 10 may have associated constraints.
- the sharing may be restricted to IAB nodes (or UEs) that are no farther than a given number of backhaul or access links from the COT-initiating IAB node.
- the max hop count can be 1, 2, 3, 4, 5, etc.
- the COT-sharing may be permitted along one signal path direction but not along the opposite direction. For instance, COT-sharing may be allowed if the COT-receiving IAB node is positioned along an upstream or downstream signal path towards the IAB donor of the IAB network but not if the COT-receiving IAB node is positioned along the downstream or upstream signal path, respectively.
- the COT-sharing along a particular signal path direction (e.g., upstream or downstream) may be allowed if the COT is initiated for transmission by the DU of the COT-initiating IAB node, but not if the COT is initiated for transmission by the MT of the COT-initiating IAB node, or vice versa.
- COT sharing by a first IAB node with a second IAB node of an IAB network may depend on the transmission power and/or transmission beam direction of the second IAB node. That is, the sharing of COT between two IAB nodes of an IAB network may be constrained by the transmission power and/or transmission beam direction of the IAB node that is receiving the COT.
- the first IAB node may share COT with the second IAB node when (e.g., in some cases, only when) the second IAB node has a transmission power that is no greater than a threshold transmission power.
- the constraint may be that the first IAB node, i.e., the sharer of the COT, may share the COT with the second IAB node when (e.g., in some cases, only when) the transmission beam used by the second IAB node is selected from a specific subset of beams, or within a specific angular range of the beam used by the first IAB node.
- constraints may be indicated (e.g., to the second IAB node) by the first IAB node using MAC-CE messages and/or DL/UL control indications.
- a parent IAB node or the CU of an IAB donor may control the afore-mentioned constraints of COT-sharing across IAB nodes of the IAB network.
- the control unit (CU) of the IAB may configure (e.g., semi-statically) the COT-sharing by using F1 application protocol (AP) messages via F1 interface connecting the CU to the DU of the same IAB donor.
- AP application protocol
- the CU may communicate with the IAB nodes via the DU to configure the IAB nodes with the constraints on sharing COT.
- no UL signal may be needed to carry COT-sharing information for access network, because in this case the UL transmission may be scheduled/controlled by the BS, which may already possess the COT-sharing information.
- COT sharing between across an IAB-network may be different, because the COT may be initiated by an IAB-node DU and then be shared to a parent node DU via an IAB-node MT, and in this case the COT sharing information may be unknown to parent DU for dynamic scheduled UL transmission because parent DU may not control IAB-node DU's activity.
- the COT sharing information may need to be supported by an UL signal even for dynamic scheduled UL transmission.
- the UL signals (such as UL signals 932 , 938 , 962 , 974 and 1014 , etc.) from the child MT of a child IAB node to a parent DU of a parent IAB node may include information related to the COT, such as but not limited to amount of remaining COT.
- the child IAB node may have initiated the COT, and in other cases, the child IAB node may have received the COT from another IAB node (or from the COT-initiating IAB node).
- the instructions 1106 may include instructions that, when executed by the processor 1102 , cause the processor 1102 to perform the operations described herein with reference to the UEs 115 in connection with aspects of the present disclosure, for example, aspects of FIGS. 1 - 10 and 13 . Instructions 1106 may also be referred to as program code. The program code may be for causing a wireless communication device to perform these operations, for example by causing one or more processors (such as processor 1102 ) to control or command the wireless communication device to do so.
- the terms “instructions” and “code” should be interpreted broadly to include any type of computer-readable statement(s).
- instructions and code may refer to one or more programs, routines, sub-routines, functions, procedures, etc. “Instructions” and “code” may include a single computer-readable statement or many computer-readable statements.
- the COT sharing module 1108 may be implemented via hardware, software, or combinations thereof.
- the COT sharing module 1108 may be implemented as a processor, circuit, and/or instructions 1106 stored in the memory 1104 and executed by the processor 1102 .
- the COT sharing module 1108 may be used for various aspects of the present disclosure, including aspects of FIGS. 1 - 10 and 13 .
- the COT sharing module 1108 is configured to perform channel access procedures (e.g., as discussed with reference to FIGS. 7 A- 7 E ) to allow the UE 1100 to access COT shared by its parent IAB node, as discussed in the aspects of FIGS. 1 - 10 and 13 .
- the RF unit 1114 may be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.) modulated/encoded data from the modem subsystem 1112 (on outbound transmissions) or of transmissions originating from another source such as a UE 115 or a BS 105 .
- the RF unit 1114 may be further configured to perform analog beamforming in conjunction with the digital beamforming.
- the modem subsystem 1112 and the RF unit 1114 may be separate devices that are coupled together at the UE 115 to enable the UE 115 to communicate with other devices.
- the RF unit 1114 may provide the modulated and/or processed data, e.g. data packets (or, more generally, data messages that may contain one or more data packets and other information), to the antennas 1316 for transmission to one or more other devices.
- the antennas 1116 may further receive data messages transmitted from other devices.
- the antennas 1116 may provide the received data messages for processing and/or demodulation at the transceiver 1110 .
- the antennas 1116 may include multiple antennas of similar or different designs in order to sustain multiple transmission links.
- the RF unit 1114 may configure the antennas 1116 .
- the UE 1100 can include multiple transceivers 1110 implementing different RATs (e.g., NR and LTE). In an aspect, the UE 1100 can include a single transceiver 1110 implementing multiple RATs (e.g., NR and LTE). In an aspect, the transceiver 1110 can include various components, where different combinations of components can implement RATs.
- RATs e.g., NR and LTE
- the transceiver 1110 can include various components, where different combinations of components can implement RATs.
- FIG. 12 is a block diagram of an exemplary BS 1400 according to aspects of the present disclosure.
- the BS 1200 may be a BS 105 in the networks 100 , 200 , 300 or 400 as discussed above in FIG. 1 , 2 3 , or 4 A, respectively.
- the BS 1200 can be the IAB donor 410 or the IAB node 105 of the IAB network 400 of FIG. 4 A .
- the BS 1200 can also be the IAB donor 455 or the IAB nodes 465 or 466 of the IAB network 450 of FIG. 4 B .
- the BS 1200 may include a processor 1202 , a memory 1204 , a COT sharing module 1208 , a transceiver 1210 including a modem subsystem 1212 and a RF unit 1214 , and one or more antennas 1216 . These elements may be in direct or indirect communication with each other, for example via one or more buses.
- the memory 1204 may include a cache memory (e.g., a cache memory of the processor 1202 ), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, a solid state memory device, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory.
- the memory 1204 may include a non-transitory computer-readable medium.
- the memory 1404 may store instructions 1206 .
- the instructions 1206 may include instructions that, when executed by the processor 1202 , cause the processor 1202 to perform operations described herein, for example, aspects of FIGS. 1 - 10 and 13 . Instructions 1206 may also be referred to as code, which may be interpreted broadly to include any type of computer-readable statement(s) as discussed above with respect to FIG. 11 .
- the DL communication signal is a DL transmission scheduled via a downlink control information (DCI) grant.
- the DL communication signal is transmitted as medium access control (MAC) control element (CE) message.
- MAC medium access control
- CE control element
- a number of backhaul links between the second IAB node and the third IAB nodes is no greater than a maximum hop count constraint on sharing COT in the IAB network.
- the RF unit 1214 may be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.) modulated/encoded data from the modem subsystem 1212 (on outbound transmissions) or of transmissions originating from another source such as a UE 115 .
- the RF unit 1214 may be further configured to perform analog beamforming in conjunction with the digital beamforming.
- the modem subsystem 1212 and/or the RF unit 1214 may be separate devices that are coupled together at the BS 105 to enable the BS 105 to communicate with other devices.
- the transceiver 1210 may be configured to communicate a second communication signal with a third IAB node different from the first IAB node to allow the third IAB node to access the channel for signal transmission by the third IAB node during the COT.
- the first IAB node may utilize one or more components, such as the processor 1302 , the memory 1304 , the COT sharing module 1308 , the transceiver 1310 , the modem 1312 , and/or the one or more antennas 1316 , to communicating a second communication signal with a third IAB node different from the first IAB node to allow the third IAB node to access the channel for signal transmission by the third IAB node during the COT.
- “or” as used in a list of items indicates an inclusive list such that, for example, a list of [at least one of A, B, or C] means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (26)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/081,880 US11856603B2 (en) | 2020-05-26 | 2020-10-27 | Sharing channel occupancy time across nodes of an integrated access backhaul network |
PCT/US2021/029196 WO2021242460A1 (en) | 2020-05-26 | 2021-04-26 | Sharing channel occupancy time across nodes of an integrated access backhaul network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202063030194P | 2020-05-26 | 2020-05-26 | |
US17/081,880 US11856603B2 (en) | 2020-05-26 | 2020-10-27 | Sharing channel occupancy time across nodes of an integrated access backhaul network |
Publications (2)
Publication Number | Publication Date |
---|---|
US20210378011A1 US20210378011A1 (en) | 2021-12-02 |
US11856603B2 true US11856603B2 (en) | 2023-12-26 |
Family
ID=78704582
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/081,880 Active 2041-02-10 US11856603B2 (en) | 2020-05-26 | 2020-10-27 | Sharing channel occupancy time across nodes of an integrated access backhaul network |
Country Status (2)
Country | Link |
---|---|
US (1) | US11856603B2 (en) |
WO (1) | WO2021242460A1 (en) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11470642B2 (en) * | 2020-03-27 | 2022-10-11 | Qualcomm Incorporated | Channel access with variable energy detection thresholds |
US11627606B2 (en) * | 2020-10-16 | 2023-04-11 | Samsung Electronics Co., Ltd | Receiver-assisted listen before talk for new radio unlicensed spectrum |
WO2023223158A1 (en) * | 2022-05-19 | 2023-11-23 | Lenovo (Singapore) Pte. Ltd. | Channel access by network-controlled repeaters |
WO2023223159A1 (en) * | 2022-05-19 | 2023-11-23 | Lenovo (Singapore) Pte. Ltd. | Repeater-assisted channel access with network-controlled repeaters |
CN115553024A (en) * | 2022-08-02 | 2022-12-30 | 北京小米移动软件有限公司 | Method and device for sharing channel occupation time COT |
Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200053798A1 (en) * | 2018-08-10 | 2020-02-13 | Mediatek Inc. | Methods for mitigating impact of listen-before-talk in unlicensed spectrum |
US20200145967A1 (en) * | 2018-11-01 | 2020-05-07 | Comcast Cable Communications, Llc | Radio Resource Allocation for Access Link |
WO2020146833A1 (en) * | 2019-01-11 | 2020-07-16 | Apple Inc. | Cot sharing procedure for configured grants in nr systems operating on unlicensed spectrum |
US20200322982A1 (en) * | 2019-01-18 | 2020-10-08 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method and device for wireless communication on an unlicensed spectrum |
US20210007149A1 (en) * | 2019-09-19 | 2021-01-07 | Intel Corporation | Grant based pusch transmission and configured grant based pusch transmission in nr systems operating on unlicensed spectrum |
US20210050933A1 (en) * | 2019-08-15 | 2021-02-18 | Lg Electronics Inc. | Method and apparatus for transmitting and receiving signal in wireless communication system |
US20210068154A1 (en) * | 2018-05-18 | 2021-03-04 | Huawei Technologies Co., Ltd. | Channel sensing method, related device, and system |
US20210136676A1 (en) * | 2018-08-03 | 2021-05-06 | Fujitsu Limited | Method of securing wireless backhaul, a child base station, a parent base station and methods in the child and parent base stations |
US20210204322A1 (en) * | 2018-08-08 | 2021-07-01 | Idac Holdings, Inc. | Receiver assisted transmissions in nru |
US20220015143A1 (en) * | 2018-12-20 | 2022-01-13 | Nokia Technologies Oy | Relay operations in a communication system |
US20220078781A1 (en) * | 2019-11-04 | 2022-03-10 | Ofinno, Llc | Uplink transmission in new radio unlicensed band |
US20220167423A1 (en) * | 2019-06-19 | 2022-05-26 | Apple Inc. | Channel sensing for physical random access channel (prach) signals in new radio (nr) systems operating in the unlicensed spectrum |
US20220232392A1 (en) * | 2018-05-10 | 2022-07-21 | Sony Group Corporation | Electronic apparatus, wireless communication method and computer-readable medium for defining an acquisition manner of an unlicensed band resource |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111491392B (en) * | 2019-01-29 | 2022-05-24 | 华为技术有限公司 | Communication method, terminal equipment and access network equipment |
EP3955620A1 (en) * | 2019-04-10 | 2022-02-16 | Ntt Docomo, Inc. | User terminal, wireless communication method, and base station |
-
2020
- 2020-10-27 US US17/081,880 patent/US11856603B2/en active Active
-
2021
- 2021-04-26 WO PCT/US2021/029196 patent/WO2021242460A1/en active Application Filing
Patent Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220232392A1 (en) * | 2018-05-10 | 2022-07-21 | Sony Group Corporation | Electronic apparatus, wireless communication method and computer-readable medium for defining an acquisition manner of an unlicensed band resource |
US20210068154A1 (en) * | 2018-05-18 | 2021-03-04 | Huawei Technologies Co., Ltd. | Channel sensing method, related device, and system |
US20210136676A1 (en) * | 2018-08-03 | 2021-05-06 | Fujitsu Limited | Method of securing wireless backhaul, a child base station, a parent base station and methods in the child and parent base stations |
US20210204322A1 (en) * | 2018-08-08 | 2021-07-01 | Idac Holdings, Inc. | Receiver assisted transmissions in nru |
US20200053798A1 (en) * | 2018-08-10 | 2020-02-13 | Mediatek Inc. | Methods for mitigating impact of listen-before-talk in unlicensed spectrum |
US20200145967A1 (en) * | 2018-11-01 | 2020-05-07 | Comcast Cable Communications, Llc | Radio Resource Allocation for Access Link |
US20220015143A1 (en) * | 2018-12-20 | 2022-01-13 | Nokia Technologies Oy | Relay operations in a communication system |
WO2020146833A1 (en) * | 2019-01-11 | 2020-07-16 | Apple Inc. | Cot sharing procedure for configured grants in nr systems operating on unlicensed spectrum |
US20200322982A1 (en) * | 2019-01-18 | 2020-10-08 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method and device for wireless communication on an unlicensed spectrum |
US20220167423A1 (en) * | 2019-06-19 | 2022-05-26 | Apple Inc. | Channel sensing for physical random access channel (prach) signals in new radio (nr) systems operating in the unlicensed spectrum |
US20210050933A1 (en) * | 2019-08-15 | 2021-02-18 | Lg Electronics Inc. | Method and apparatus for transmitting and receiving signal in wireless communication system |
US20210007149A1 (en) * | 2019-09-19 | 2021-01-07 | Intel Corporation | Grant based pusch transmission and configured grant based pusch transmission in nr systems operating on unlicensed spectrum |
US20220078781A1 (en) * | 2019-11-04 | 2022-03-10 | Ofinno, Llc | Uplink transmission in new radio unlicensed band |
Non-Patent Citations (3)
Title |
---|
"3rd Generation Partnership Project, Technical Specification Group Radio Access Network, Physical Layer Procedures for Shared Spectrum Channel Access (Release 16)", 3GPP Standard, Technical Specification, 3GPP TS 37.213, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre 650, Route Des Lucioles, F-06921 Sophia-Antipolis Cedex, France, vol. RAN WG1, No. V16.1.0 Apr. 3, 2020 (Apr. 4, 2020), XP051893817, pp. 1-25, Retrieved from the Internet: URL:ftp://ftp.3gpp.org/Specs/archive/37_series/37.213/37213-g10.zip 37213-g10.doc. |
ANONYMOUS: "3rd Generation Partnership Project, Technical Specification Group Radio Access Network, NR, Study on Integrated Access and Backhaul, (Release 16)", 3GPP Standard Technical Report, 3GPP, TR 38.874, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-Antipolis Cedex, France, No. V16.0.0, Jan. 10, 2019 (Jan. 18, 2019), Dec. 31, 2018 (Dec. 31, 2018), pp. 1-111, XP051591643, Sections 8.3.5 and 9.3, p. 21-p. 23. |
International Search Report and Written Opinion—PCT/US2021/029196—ISA/EPO—Jul. 15, 2021. |
Also Published As
Publication number | Publication date |
---|---|
WO2021242460A1 (en) | 2021-12-02 |
US20210378011A1 (en) | 2021-12-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11864231B2 (en) | Listen-before-talk (LBT) aware autonomous sensing for sidelink | |
US20230146161A1 (en) | Cyclic prefix (cp) extension in channel occupancy time (cot) sharing for sidelink communication | |
US20210195649A1 (en) | Autonomous sidelink over unlicensed band | |
US10912012B2 (en) | Initial network access for downlink unlicensed deployment | |
US11711849B2 (en) | Network controlled sidelink off-loading over unlicensed carrier | |
US11743911B2 (en) | Starting offset for new radio-unlicensed (NR-U) uplink transmission | |
US11425691B2 (en) | Physical sidelink feedback channel (PSFCH) negotiation | |
US11856603B2 (en) | Sharing channel occupancy time across nodes of an integrated access backhaul network | |
US20230389070A1 (en) | Category-2 listen-before-talk (lbt) options for new radio-unlicensed (nr-u) | |
US20220103232A1 (en) | Transmission reception point (trp)-specific beam failure detection (bfd) reference signal (rs) determination | |
US20190349969A1 (en) | Efficient operation with unlicensed downlink (dl) and licensed uplink (ul) by transmission of selective dl messages using licensed ul | |
US20200100116A1 (en) | Licensed supplemental uplink as fallback with unlicensed uplink and downlink | |
US11304229B2 (en) | Constraints on no listen-before-talk (LBT) transmission during uplink/downlink (UL/DL) switches | |
US11895699B2 (en) | Listen-before-talk (LBT) type and gap signaling for back-to-back grants and multi-transmission time interval (multi-TTI) grants | |
US11589388B2 (en) | Sharing channel occupancy time of a node in an integrated access backhaul network | |
US11632786B2 (en) | Channel access contention management for ultra-reliable low-latency communication (URLLC) | |
US20210195638A1 (en) | Uplink (ul) to downlink (dl) channel occupancy time (cot) sharing with scheduled ul in new radio-unlicensed (nr-u) | |
US20220104036A1 (en) | Beam group specific medium access control-control element (mac-ce) based beam failure recovery (bfr) requests | |
WO2021217484A1 (en) | Sidelink slot structure for sidelink communication in a wireless communications network | |
US11528742B2 (en) | Systems and methods for autonomous transmission of deprioritized protocol data units | |
US20210112603A1 (en) | Systems and methods for physical uplink shared channel (pusch) occasion validation for 2-step random access channel (rach) | |
US11516838B2 (en) | Systems and methods for physical uplink shared channel repetition adaptation | |
US11395334B2 (en) | Multiple grant scheduling for hybrid automatic repeat request (HARQ) and random access | |
US20230084692A1 (en) | Coordinated clear channel assessment (cca) for wireless repeaters | |
US20230269772A1 (en) | Channel occupancy time sharing for frame-based equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: QUALCOMM INCORPORATED, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LUO, JIANGHONG;ZHANG, XIAOXIA;SUN, JING;AND OTHERS;SIGNING DATES FROM 20210115 TO 20210120;REEL/FRAME:055022/0694 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION COUNTED, NOT YET MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |