[go: up one dir, main page]

WO2019195445A1 - Procédés destinés à la gestion d'une partie de largeur de bande dans des systèmes sans fil - Google Patents

Procédés destinés à la gestion d'une partie de largeur de bande dans des systèmes sans fil Download PDF

Info

Publication number
WO2019195445A1
WO2019195445A1 PCT/US2019/025611 US2019025611W WO2019195445A1 WO 2019195445 A1 WO2019195445 A1 WO 2019195445A1 US 2019025611 W US2019025611 W US 2019025611W WO 2019195445 A1 WO2019195445 A1 WO 2019195445A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
wtru
resources
random access
bwps
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.)
Ceased
Application number
PCT/US2019/025611
Other languages
English (en)
Inventor
Mouna HAJIR
Ghyslain Pelletier
Faris ALFARHAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
IDAC Holdings Inc
Original Assignee
IDAC Holdings 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 IDAC Holdings Inc filed Critical IDAC Holdings Inc
Publication of WO2019195445A1 publication Critical patent/WO2019195445A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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
    • 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
    • H04W74/0838—Random access procedures, e.g. with 4-step access using contention-free random access [CFRA]

Definitions

  • a wireless transmit/receive unit can be scheduled for uplink transmission if its uplink transmission timing is synchronized.
  • the random access channel plays an important role as an interface between non-synchronized WTRUs and the transmission scheme of the WTRU uplink radio access. For example, RACH is used to achieve uplink time synchronization for a WTRU which has not yet acquired or has lost its uplink synchronization.
  • a base station BS may schedule an uplink transmission resource for the WTRU.
  • a WTRU may transmit a random access preamble to a BS, allowing the BS to estimate the transmission timing of the device.
  • the BS may transmit a random access response (RAR) on the downlink shared channel (DL-SCH), containing a timing adjustment, a cell-radio network temporary identifier (C-RNTI), and an uplink grant for L2/L3 messages.
  • RAR random access response
  • DL-SCH downlink shared channel
  • C-RNTI cell-radio network temporary identifier
  • a WTRU may be configured with one or more bandwidth part(s) (BWP) for random access procedures. For example, a WTRU may transmit, via the RACH, a random access preamble in an uplink bandwidth part (UL BWP). The WTRU may also receive, via the DL-SCH, the RAR in a downlink bandwidth part (DL BWP).
  • DL BWP downlink bandwidth part
  • the BS may need to transmit a very large number of RARs.
  • a wireless transmit/receive unit may transmit, via an active uplink (UL) bandwidth part (BWP) in a random access channel, a random access request.
  • the WTRU may then determine an association between the UL BWP and one or more downlink (DL)
  • the WTRU may further determine from the association between the UL BWP and the one or more DL BWPs, an active DL BWP over which to receive a random access response (RAR). The WTRU may then receive the RAR over the active DL BWP.
  • RAR random access response
  • FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment;
  • WTRU wireless transmit/receive unit
  • FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
  • RAN radio access network
  • CN core network
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A according to an embodiment
  • FIG. 2 is a diagram illustrating an example one-to-one mapping with a static bandwidth part (BWP) center frequency and bandwidth;
  • BWP static bandwidth part
  • FIG. 3 is a flowchart illustrating procedures to be performed by a WTRU upon linking of uplink (UL) BWPs and downlink (DL) BWPs;
  • FIG. 4 is a diagram illustrating an example one-to-one mapping from the system perspective with the same BWP center frequency but different bandwidths
  • FIG. 5 is a diagram illustrating an example one-to-one mapping from system perspective with different BWP center frequencies and bandwidth of WTRUs;
  • FIG. 6 is a diagram of UL BWP and DL BWP mapping according to one embodiment.
  • FIG. 7 is an illustration of an embodiment where an UL BWP configured with RACH resources associated with a mix of SSB and CSI-RS is linked to two DL BWPs.
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT-UW-DFT-S-OFDM zero-tail unique-word discrete Fourier transform Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (ON) 106, a public switched telephone network (PSTN) 108, the Internet 1 10, and other networks 1 12, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • the communications systems 100 may also include a base station 114a and/or a base station 1 14b.
  • Each of the base stations 1 14a, 1 14b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 1 10, and/or the other networks 112.
  • the base stations 1 14a, 1 14b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Flome Node B, a Flome eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 1 14a, 1 14b are each depicted as a single element, it will be appreciated that the base stations 1 14a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, and the like.
  • the base station 1 14a and/or the base station 1 14b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 1 14a may be divided into three sectors.
  • the base station 1 14a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 1 14a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 1 14a, 1 14b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 1 16, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 1 16 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 1 14a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (FISPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (FISDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA).
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 1 16 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 1 16 using NR.
  • a radio technology such as NR Radio Access
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 1 14b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.1 1 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 1 14b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 1 14b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 1 14b may have a direct connection to the Internet 1 10.
  • the base station 1 14b may not be required to access the Internet 1 10 via the CN 106.
  • the RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106 may provide call control, billing services, mobile location- based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high- level security functions, such as user authentication.
  • the RAN 104 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
  • the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 1 12.
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 1 10 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 1 12 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 1 12 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 1 14b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
  • GPS global positioning system
  • the processor 1 18 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (1C), a state machine, and the like.
  • the processor 1 18 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 1 18 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1 B depicts the processor 1 18 and the transceiver 120 as separate components, it will be appreciated that the processor 1 18 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 1 14a) over the air interface 1 16.
  • a base station e.g., the base station 1 14a
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 1 16.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.1 1 , for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the display/touchpad 128 e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the processor 1 18 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 1 18 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), read- only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 1 18 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 1 18 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 1 16 from a base station (e.g., base stations 1 14a, 1 14b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors.
  • the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit to reduce and or substantially eliminate selfinterference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 1 18).
  • the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 1 16.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 1 10, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 1 10
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional landline communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 1 12 may be a WLAN.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.1 1 e DLS or an 802.11 z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an“ad-hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA (e.g., only one station) may transmit at any given time in a given BSS.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • V HT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.1 1 af and 802.1 1 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.1 1 ah relative to those used in 802.1 1 h, and 802.1 1 ac.
  • 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.1 1 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.1 1 ah may support Meter Type Control/Machine-Type Communications (MTC), such as MTC devices in a macro coverage area.
  • MTC Meter Type Control/Machine-Type Communications
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.1 1 h, 802.1 1 ac, 802.1 1 af, and 802.1 1 ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.1 1 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 1 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 1 16.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 1 16.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 106 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one
  • UPF 184a, 184b at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • DN Data Network
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like.
  • PDU protocol data unit
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • different network slices may be established for different use cases such as services relying on ultrareliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like.
  • URLLC ultrareliable low latency
  • eMBB enhanced massive mobile broadband
  • the AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N1 1 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like.
  • a PDU session type may be IP- based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 1 10, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 1 12, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 1 14a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment.
  • Direct RF coupling and/or wireless communications via RF circuitry e.g., which may include one or more antennas
  • the 5G air interface will at least enable the following use cases: (1 ) improved broadband performance (IBB); (2) industrial control and communications (ICC) and vehicular applications (V2X); and (3) massive machine-type communications (mMTC).
  • IBB improved broadband performance
  • ICC industrial control and communications
  • V2X vehicular applications
  • mMTC massive machine-type communications
  • LLC ultra-low transmission latency
  • RTT round trip time
  • TTI transmission time intervals
  • ICC and V2X may require end-to-end (e2e) latency of less than 10 ms.
  • URC ultra-reliable communications
  • One key design consideration includes transmission reliability that is much better than what is possible with legacy LTE systems. For example, a possible target may be close to 99.999% transmission success and service availability. Another consideration may be support for mobility for speed in the range of 0- 500 km/h.
  • ICC and V2X may require a Packet Loss Ratio of less than 10e- 6 .
  • the air interface may efficiently support narrowband operation (e.g., using less than 200 KHz), extended battery life (e.g., up to 15 years of autonomy), and minimal communication overhead for small and infrequent data transmissions (e.g., low data rate in the range of 1 -100 kbps with access latency of seconds to hours).
  • narrowband operation e.g., using less than 200 KHz
  • extended battery life e.g., up to 15 years of autonomy
  • minimal communication overhead for small and infrequent data transmissions e.g., low data rate in the range of 1 -100 kbps with access latency of seconds to hours.
  • Orthogonal Frequency Division Multiplexing may be used as the basic signal format for data transmissions in both LTE and in IEEE 802.1 1.
  • OFDM efficiently divides the spectrum into multiple parallel orthogonal sub-bands.
  • Each subcarrier may be shaped using a rectangular window in the time domain leading to sine-shaped subcarriers in the frequency domain.
  • Orthogonal Frequency Division Multiple Access OFDMA
  • OFDMA Orthogonal Frequency Division Multiple Access
  • OFDMA may thus require perfect frequency synchronization and tight management of uplink timing alignment within the duration of the cyclic prefix to maintain orthogonality between signals and to minimize inter-carrier interference.
  • Such tight synchronization may not be well-suited to a system in which a WTRU is connected to multiple access points simultaneously.
  • Additional power reduction may typically be applied to uplink transmissions to comply with spectral emission requirements to adjacent bands, in particular in the presence of aggregation of fragmented spectrum for the WTRU’s transmission.
  • CP-OFDM cyclic prefix OFDM
  • a CP-based OFDM transmission scheme may also lead to a downlink physical layer for 5G similar to that of legacy systems (e.g., mainly modifications to pilot signal density and location).
  • the 5G flexible radio access technology (5gFLEX) design may consider other waveform candidates, although conventional CP-OFDM remains a possible candidate for 5G systems at least for the downlink transmission scheme.
  • the 5gFLEX radio access design may be characterized by a very high degree of spectrum flexibility that enables deployment in different frequency bands with different characteristics, including different duplex arrangements, different and/or variable sizes of the available spectrum including contiguous and non-contiguous spectrum allocations in the same or different bands. It may also support variable timing aspects such as multiple TTI lengths and asynchronous transmissions.
  • TDD time division duplexing
  • FDD frequency division duplexing
  • supplemental downlink operation may be supported using spectrum aggregation.
  • the FDD operation may support both full-duplex FDD and half-duplex FDD operation.
  • the WTRU may be configured with downlink control channel resources for each cell of the WTRU’s configuration.
  • the configuration may include, but is not limited to, one or more search space configurations and/or one or more CORESET configurations for each cell of the WTRU’s configuration.
  • the WTRU may be configured with uplink control channel resources for each cell of the WTRU’s configuration.
  • the configuration may include, but is not limited to, one or more PUCCH configurations for each cell of the WTRU’s configuration.
  • the WTRU may be configured with physical random access channel resources for each cell of the WTRU’s configuration.
  • the configuration may include, but is not limited to, one or more PRACH configuration for each cell of the WTRU’s configuration.
  • the WTRU may use the PRACH resources to perform random access procedures and/or for beamforming management (e.g., for establishment of beams and/or recovery from beam failure event).
  • the WTRU may be configured with one or more cells (e.g., a primary cell (PCell) and zero or more secondary cells (SCell)).
  • the WTRU may be configured with one or more groups of cells (cell group (CG)).
  • the WTRU may be configured with one special cell (SCell) or primary special cell (PSCell) for a CG.
  • the primary CG (MCG) may include at least one PCell.
  • the WTRU may be configured with carrier aggregation, in which at least one PCell may be configured for a CG.
  • a WTRU may be configured with one or more bandwidth parts (BWPs) for a given cell and/or carrier.
  • BWP bandwidth parts
  • a BWP may be characterized by at least one of subcarrier spacing, a cyclic prefix, or a number of contiguous physical resource blocks (PRBs).
  • PRBs physical resource blocks
  • a BWP may be further characterized by a frequency location (e.g., a center frequency).
  • RRC radio resrouce control
  • a WTRU may be configured with up to 4 dedicated BWPs.
  • An UL BWP with PRACH resources may always be linked to a DL BWP with random access CORESET and common search space (ra-coreset and ra-css).
  • a WTRU may be configured with an initial BWP.
  • the WTRU may be configured with an initial BWP included in the system information broadcast from a gNB and received by the WTRU.
  • the WTRU may be configured to access the system using the initial BWP for a given cell and/or carrier.
  • Such access may be an initial access (e.g., when the WTRU is in IDLE and/or determines that it should establish a RRC connection to the system).
  • the configuration of such an initial BWP may include configuration parameters for use in the random access procedure.
  • a WTRU (e.g., in CONNECTED mode) may be further configured with a default BWP.
  • the default BWP may be similar to the initial BWP, or it may be different.
  • the WTRU may revert to the default BWP at the expiration of a timer (e.g., after a period of scheduling inactivity).
  • the WTRU may be configured with the default BWP in the system information received from a gNB, or it may be configured with the default BWP via direct signalling, or in some other manner.
  • a WTRU may be further configured with additional BWPs.
  • the WTRU may be configured with a BWP for a specific type of data transfer (e.g., for URLLC transmissions).
  • These additional BWPs may be configured via system information broadcast from a gNB, or via direct signaling.
  • Uplink BWPs may be logically linked to downlink BWPs. It may be assumed that a 5G system configures a one-to-one mapping table of UL (regular uplink (RUL) or supplemental uplink (SUL)) and DL BWPs, where UL BWP i is linked to DL BWP j.
  • FIG. 2 illustrates an example one-to- one mapping with static BWP center frequency and bandwidth where i equals j.
  • NW network
  • WTRUs in the same cell may or may not be configured with the same BWP center frequency and bandwidth as the mapped one, but certain association rules may remain so that the NW knows where to transmit the RAR, as discussed below.
  • Other use cases may include any procedures involving DL and UL pairing, such as BWP switching in connected mode.
  • a WTRU 200 may be configured with the same center frequency and bandwidth as the one of the system mapping.
  • UL BWPs 210, 220, 230, and 240 correspond respectively to DL BWPs 21 1 , 221 , 231 , and 241 ; both in turn correspond to UL/DL BWPs 1 , 3, 5, and 7.
  • the NW knows that it corresponds to UL BWP5 in its mapping table.
  • the UL BWP5 is linked to DL BWP5 from the system’s perspective, which is the same as DL BWP 231 from WTRU perspective.
  • the NW i.e. gNB, can transmit a RAR message to the WTRU 200 using DL BWP 231.
  • FIG. 3 is a method flow diagram of a procedure to be performed by a WTRU to link UL BWPs and DL BWPs.
  • the MAC entity of the WTRU may evaluate whether PRACH occasions are configured for the active UL BWP. If not, the WTRU may switch to the configured initial DL BWP and UL BWP, at step 303A. If PRACH occasions are configured for the active UL BWP, at step 303B the WTRU may further determine if the active DL BWP has the same BWP-ID as the active UL BWP.
  • the WTRU may switch the active DL BWP to the DL BWP with the same BWP-ID as the active UL BWP. If the active DL BWP does have the same BWP-ID as the active UL BWP, at step 304B, the WTRU may then perform the Random Access procedure by sending a preamble on the active UL BWP and monitoring the active DL BWP for a RAR message from the NW.
  • BWP linkage in a Contention Based Random Access Channel (CBRA) context.
  • Multiple WTRUs in a wideband carrier may be configured with the same or overlapping UL BWPs.
  • the NW may not know which WTRU has transmitted it.
  • the NW may refrain from determining where to send the RAR, and simply ignore the received preamble.
  • the NW may need to transmit a very large number of RARs if no enhancement is proposed to the current specifications.
  • a WTRU may be configured with an UL BWP and a mapped DL BWP at any time in order for the NW to transmit one RAR when the WTRU transmits a preamble in the corresponding UL BWP.
  • a BWP indexation may be used so that at any time, the active DL BWP of the WTRU does not have the same index as the UL BWP in which the WTRU has sent the preamble.
  • the WTRU may switch its active DL BWP to the one with the same index.
  • one-to-one mapping may be simple and may permit limiting of the number of RARs to a minimum (e.g., one), one-to-one mapping may introduce some restrictions in terms of BWP configuration (e.g., center frequency, subcarrier spacing (SCS), bandwidth) for WTRUs in the same cell, since the configurations of the BWPs themselves (e.g., center frequency, SCS and bandwidth) may need to be static and require the UL-DL pairing to remain identical throughout the cell.
  • BWP configuration e.g., center frequency, subcarrier spacing (SCS), bandwidth
  • a WTRU may be configured with independent configurations for beam failure recovery for each BWP, which may include a list of candidate beams and CFRA resources to indicate selected beams.
  • the WTRU may initiate a random access procedure to re-establish beam pairing, by indicating, for example, a beam from the candidate beam list to the network according to measurements on the channel-state-information reference signals (CSI-RS) pertaining to the applicable candidate beam list.
  • CSI-RS channel-state-information reference signals
  • a random access procedure of this type is a mixed CBRA-CFRA procedure.
  • NR there may be a linkage configured between UL and DL BWPs for CBRA with the aim of aiding the network in reducing the number of RARs transmitted, as described herein. If the WTRU’s UL BWP index does not match the DL BWP index, the WTRU switches its DL BWP to the one that has the same index as its active UL BWP, as described herein.
  • the WTRU might detect beam failure on a DL BWP that is not linked to the active UL BWP. Therefore, upon beam failure detection on a given DL BWP, the WTRU may switch to another DL BWP. This may not be desired in situations where there is high frequency selective fading variations between DL BWPs -especially in wide-bandwidth carriers, or when the downlink candidate beam lists differ between BWPs.
  • the WTRU may determine an association between two (or more) BWPs (UL BWPs and/or DL BWPs) from a characteristic of one or more concerned BWPs. Such characteristics may include, but are not limited to, an identity of the BWP, a frequency characteristic, a state of the BWP, a type of BWP, the type of the cell that corresponds to the BWP, and any combination thereof.
  • Examples of the frequency characteristic may include, but are not limited to, a center frequency of the BWP, a bandwidth of the BWP and/or an overlap with another BWP of the same cell.
  • a WTRU may determine that a first (e.g., uplink) BWP is associated with a second (e.g., downlink) BWP corresponding to the center frequency of the cell of the concerned BWPs. This may be useful, for example, for the WTRU to associate any UL BWP with the default DL BWP.
  • the state of the BWP may indicate whether a BWP is active or not.
  • a WTRU may consider a BWP to be active when it determines an association.
  • the WTRU may determine that it has received a downlink transmission on a PDSCFI on a DL BWP and determine that an associated uplink BWP should be used for the transmission of Uplink Control Information (UCI). Accordingly, the corresponding UL BWP would be determined in this scenario to be an active BWP.
  • UCI Uplink Control Information
  • a WTRU may determine that an uplink BWP configured with PRACH resources is associated with a specific search space (e.g., based on an identity, such as a CORESET ID or a PRACH ID).
  • the specific search space may be associated with the search space of the same cell if the UL BWP corresponds to resources of a PCell for a MCG, or to resources of the PSCell for a SCG.
  • the WTRU may determine that the UL BWP is associated with the specific search space of another cell of the same CG otherwise.
  • the WTRU may determine that the concerned search space corresponds to a search space of the PCell for a MCG or a search space of the PSCell for a SCG.
  • the WTRU may perform such logic only if there is no search space configured with a common search space for any DL BWP of the same cell of the concerned UL BWP. It is also possible that the WTRU may perform such logic only if there is no such DL BWP with such search space in the active state for such cell.
  • the WTRU may determine that a downlink BWP is associated with an uplink BWP configured with PUCCH resources of the same cell if the UL BWP corresponds to resources of a PCell for a MCG, or to resources of the PSCell for a SCG, while the WTRU may determine that the DL BWP is associated with the PUCCH of another cell of the same CG otherwise.
  • the WTRU may determine that the PUCCH corresponds to a PUCCH of the PCell for a MCG or a search space of the PSCell for a SCG.
  • the WTRU may perform such logic only if there are no PUCCH resources configured for any UL BWP of the same cell of the associated DL BWP. It is also possible that the WTRU may perform such logic only if there is no such UL BWP with PUCCH resources in the active state for such cell.
  • the WTRU may similarly determine an association to a control resource set (CORESET).
  • CORESET control resource set
  • teh WTRU may associate a CORESET identifier (ID) to a DL BWP ID, or to an UL BWP, or to both.
  • ID CORESET identifier
  • embodiments of the following one-to-one associations (or mappings) may be possible: (1 ) UL BWP center frequency to DL BWP center frequency; (2) UL BWP center frequency to DL BWP CORESET; (3)
  • UL PRACH resource to DL BWP CORESET; and/or (4) UL multiple WTRUs overlapping BWP portion (i.e. bandwidth and center frequency of the overlapping zone) to DL multiple WTRUs overlapping BWP portion (i.e. bandwidth and center frequency of the overlapping zone).
  • the association of UL and DL BWPs is not based on the BWPs themselves, but may instead be based on one or more specific characteristics of the BWP, such as center frequency and CORESET.
  • Center frequencies of UL BWPs may be associated to center frequencies of DL BWPs where the CORESET may be located.
  • the CORESET may be located in a bandwidth portion of the DL BWP and has a configurable bandwidth in terms of number of PRBs.
  • the minimum size of this CORESET bandwidth portion may be the size of the physical downlink control channel (PDCCH).
  • This association may be used for the WTRU to receive a in response to a transmitted preamble and the NW does not know which WTRU has sent the preamble and in which DL BWP to respond.
  • FIG. 4 illustrates an example one-to-one mapping from the system perspective with BWPs configured for WTRUs 410, 420, and 430.
  • the UL BWPs 41 1 , 422, and 432 may have the same BWP center frequency 451 as their corresponding DL BWPs 412, 424, and 434, but different bandwidths.
  • UL BWPs 421 and 431 may have the same respective center frequencies 452 and 453 as their corresponding DL BWPS 423 and 433.
  • the center frequency of BWPs among multiple WTRUs may be the same, but the bandwidth may be different (e.g., larger or smaller).
  • the NW may take into account the center frequency 450 of the BWP.
  • the WTRU may be configured with a DL BWP at least containing the DL BWP mapped to this UL BWP. For example, if the WTRU 410 transmits a preamble in its UL BWP 411 , since the UL BWP 41 1 corresponds to UL BWP6 in terms of center frequency (from the system perspective), the WTRU may receive the RAR in the DL BWP6 (from the system perspective).
  • any WTRU that is configured with an UL BWP that has the same center frequency as the one mapped in the system it may be configured with a paired DL BWP that has the same center frequency as the corresponding DL BWP in the system mapping.
  • FIG. 5 illustrates another example one-to-one mapping from the system perspective with BWPs configured for WTRUs 510, 520, and 530.
  • center frequencies are the same for corresponding UL BWP 511 and DL BWP 512, but different center frequencies and bandwidths are configured for corresponding UL BWPs 521 , 522, 531 and 532, and DL BWPs 523, 524, 533 and 534.
  • the association of UL and DL BWPs may not be based on the BWP itself but on the center frequency and bandwidth of overlapping BWP portions. As illustrated in FIG.
  • the BWPs configured at the WTRU may have different center frequencies and bandwidth than those mapped in the system, but may still overlap. If these WTRUs’ PRACH resources overlap as well, the WTRU may be configured with a different DL BWP (i.e. center frequency and bandwidth) as long as a portion of the DL BWP overlaps with the one mapped in the system.
  • This portion can be configurable in terms of a number of PRBs. For example, the portion may be defined over a range from x to y PRBs, where x may be the minimum bandwidth of the CORESET and y may be the number of contiguous PRBs received in the upper-layer configuration as the bandwidth of the BWP.
  • This portion of the BWP may contain the CORESET, and these WTRUs may be configured with the same common search spaces.
  • the dotted areas 553 and 555 may represent the common DL BWP portion among all WTRUs configured with overlapping UL BWPs that may contain the CORESET.
  • the NW may simply transmit the RAR in bandwidth associate with the dotted areas 553 and 555 since the NW does not know which one of the WTRUs has transmitted the preamble in the common UL BWP PRACH resources (i.e. hatched regions 551 , 552, and 554) among WTRUs 510, 520, and 530.
  • one UL BWP may be linked to multiple DL BWPs from the system perspective.
  • Different WTRUs that share the same UL BWP may be configured with orthogonal PRACH resources. Since the NW allocasted the PRACH resources according to an RRC configuration, the NW may know which WTRU has transmitted the preamble. Since the NW knows the configured BWPs, the NW may transmit a single RAR in the RRC paired DL BWP associated with the WTRU.
  • the NW may limit this case to x number of WTRUs, and hence may transmit x RARs in the different DL BWPs. If multiple WTRUs are configured with the same UL BWP or overlapping UL BWPs, they may be configured with any DL BWP. The RAR may be sent to each of the DL BWPs paired to these UL BWPs.
  • the RAR may be transmitted to DL BWP 512 (of WTRU 510), DL BWP 554 (of WTRU 520) and DL BWP 534 of WTRU 530.
  • DL BWP 512 of WTRU 510
  • DL BWP 554 of WTRU 520
  • DL BWP 534 of WTRU 530.
  • FIG. 6 illustrates an embodiment in which UL BWP PRACH resources are associated with DL BWP CORESET identifiers.
  • a WTRU may be configured with multiple UL BWPs 601 , 602, and 603 and multiple DL BWPs 61 1 , 612, and 613.
  • the WTRU may be initially configured with an active UL BWP 601 and an active DL BWP 61 1.
  • Each UL BWP may have one or more PRACH sets 621 , 622, 623, 624, or 625, and each PRACH set may be associated with a CORESET 631 , 632, 633, 634, or 635 within multiple DL BWPs.
  • the WTRU may transmit a preamble to a gNB in the NW over the WTRU’s active UL BWP using PRACH resources— shown in FIG. 6, for example, as UL BWP 601 and PRACH set 622.
  • the WTRU may then determine the set of DL BWPs having CORESET identifiers corresponding to the PRACH set used for preamble transmission. For instance, as shown in FIG. 6, PRACH set 622 corresponds to CORESET 633, located within DL BWP 612.
  • the WTRU may determine that the corresponding CORESET is not within the active DL BWP 611 , and thus switch the active DL BWP to DL BWP 612 to receive a RAR from the NW over the new active DL BWP 612.
  • one bit of information may indicate to the WTRU that its configured UL BWP is the same or overlapping with other WTRUs’ UL BWPs in the cell.
  • This indication may allow the WTRU to switch its active BWP to the initial/default BWP when it transmits a preamble in a PRACH resource in an UL BWP flagged with a non-zero value (e.g., value of 1). Otherwise, if the bit-information is zero, no other UL BWP in the cell is overlapping with the UL BWP where the WTRU is transmitting the PRACH resource. Thus, the WTRU may receive the RAR in its active DL BWP. Again, this reduces the number of RAR messages the NW may have to transmit.
  • a WTRU may detect beam failure on a certain DL BWP that is not linked to the active UL BWP. To be able to monitor the DL link quality of the configured candidate beam and transmit a preamble in an UL BWP the WTRU may apply one or more methods as described below.
  • the WTRU may switch its UL BWP to the UL BWP linked with the DL BWP on which beam failure is detected.
  • the WTRU may further condition such action on whether the UL BWP linked to the active DL BWP has CFRA and/or CBRA PRACH resources configured.
  • the WTRU may switch UL and DL BWPs to the initial UL BWP and DL BWP, or the initial UL BWP and the default DL BWP.
  • the WTRU may ignore the configured BWP linkage, and not switch its active DL BWP.
  • the WTRU may further condition such action on whether the WTRU is configured with CFRA preambles corresponding to the candidate beam list in the active DL BWP.
  • the WTRU may be configured with a beam failure specific BWP linkage and may ignore any other configured BWP linkage.
  • the WTRU detects a beam failure in its active DL BWP, the WTRU switches to the UL BWP linked to the active DL BWP.
  • the linked UL BWP is configured with PRACH resources associated with a list of reference signals identifying the candidate beams for recovery (CSI-RS and/or Synchronization Signal Block (SSB)) that the WTRU is able to monitor in the linked DL BWP (e.g. DL BWP contains the frequency location of these reference signals).
  • CSI-RS and/or Synchronization Signal Block
  • the WTRU may monitor
  • the WTRU may provide a BFI to the MAC layer when RSRP is less than a threshold for all monitored DL BWPs, for example.
  • the WTRU may also adjust its beam failure instance counter and beam failure detection timer.
  • a WTRU may be configured with its active UL BWP with CFRA associated to a mix of
  • CSI-RS and/or SSBs and/or CBRA resources associated to SSBs may be separated in frequency.
  • the WTRU may monitor both types of configured reference signals and transmit a preamble in the UL BWP configured with the mix of CSI- RS and SSB RACH resources.
  • this UL BWP is linked to a DL BWP spanning the whole bandwidth containing both types of resources.
  • the WTRU may be configured with an UL BWP configured with RACH resources associated with a mix of SSB and CSI-RS, that is linked to two DL BWPs.
  • the WTRU may be configured with multiple UL BWPs 700, 701 , and 702, and multiple DL BWPs 710, 71 1 , and 712.
  • UL BWP 702 is associated with both SSB resources 730 and CSI-RS resources 731
  • UL BWP 700 is associated only with SSB resources 730.
  • the SSB resources 730 may be associated with CFRA or CBRA, while the CSI-RS resources are associated with CFRA.
  • the WTRU may apply a priority to CFRA resources associated with CSI-RS resources when determining the DL BWP over which to perform the random access procedure.
  • the WTRU may first switche its active DL BWP to the DL BWP 71 1 containing the CSI-RS resource frequencies if the DL BWP 711 containing the CSI-RS is not already the active DL BWP.
  • the WTRU may monitor the CSI-RS signal in this active DL BWP 71 1 and perform a random access procedure, if necessary.
  • the WTRU may switch to the DL BWP 710 containing the cell associated SSB resource frequency to perform either CFRA or, for example, in the event CFRA is unsuccessful, to fall back to CBRA.

Landscapes

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

Abstract

La présente invention concerne des procédés et des appareils destinés à la gestion d'une partie de largeur de bande (BWP) dans des systèmes sans fil. Par exemple, une unité d'émission/réception sans fil (WTRU) peut transmettre un accès aléatoire par l'intermédiaire d'une partie de largeur de bande (BWP) de liaison montante (UL) active dans un canal d'accès aléatoire. La WTRU peut ensuite déterminer une association entre la BWP d'UL et une ou plusieurs BWP de liaison descendante (DL) dans un canal partagé. La WTRU peut en outre déterminer à partir de l'association entre la BWP d'UL et la ou les BWP de DL, une BWP de DL active sur laquelle recevoir une réponse d'accès aléatoire (RAR). La WTRU peut ensuite recevoir la RAR sur la BWP de DL active.
PCT/US2019/025611 2018-04-03 2019-04-03 Procédés destinés à la gestion d'une partie de largeur de bande dans des systèmes sans fil Ceased WO2019195445A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201862652131P 2018-04-03 2018-04-03
US62/652,131 2018-04-03
US201862687009P 2018-06-19 2018-06-19
US62/687,009 2018-06-19

Publications (1)

Publication Number Publication Date
WO2019195445A1 true WO2019195445A1 (fr) 2019-10-10

Family

ID=66175568

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/025611 Ceased WO2019195445A1 (fr) 2018-04-03 2019-04-03 Procédés destinés à la gestion d'une partie de largeur de bande dans des systèmes sans fil

Country Status (1)

Country Link
WO (1) WO2019195445A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210168815A1 (en) * 2018-08-10 2021-06-03 Lg Electronics Inc. Method for configuring bandwidth part in wireless communication system and device for supporting same
WO2021172937A1 (fr) * 2020-02-28 2021-09-02 Samsung Electronics Co., Ltd. Procédé et appareil pour procédure d'accès aléatoire
WO2021223091A1 (fr) * 2020-05-06 2021-11-11 Qualcomm Incorporated Sélection de ressources de procédure d'accès aléatoire
CN115280882A (zh) * 2020-03-12 2022-11-01 诺基亚技术有限公司 启用能力降低的新无线电（nr）设备的接入
US20220377636A1 (en) * 2018-05-11 2022-11-24 Vivo Mobile Communication Co.,Ltd. Resource processing method, apparatus, and system
CN115486177A (zh) * 2020-05-08 2022-12-16 高通股份有限公司 用于全双工通信的频域资源分配技术
WO2024016278A1 (fr) * 2022-07-21 2024-01-25 Zte Corporation Procédés et dispositifs d'accès aléatoire en duplex intégral de sous-bande

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "BWP Inactivity Timer and DRX", vol. RAN WG2, no. Reno, Nevada, USA; 20171127 - 20171201, 21 November 2017 (2017-11-21), XP051372597, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F100/Docs/> [retrieved on 20171121] *
HUAWEI ET AL: "BWP issues for SA", vol. RAN WG2, no. Athens, Greece; 20180226 - 20180302, 16 February 2018 (2018-02-16), XP051400054, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F101/Docs/> [retrieved on 20180216] *
LG ELECTRONICS: "Remaining issues on bandwidth parts", vol. RAN WG1, no. Reno, USA; 20171127 - 20171201, 18 November 2017 (2017-11-18), XP051369648, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F91/Docs/> [retrieved on 20171118] *
NOKIA ET AL: "BWP switch interaction with contention free BFR preamble", vol. RAN WG2, no. Athens, Greece; 20180226 - 20180302, 16 February 2018 (2018-02-16), XP051400430, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F101/Docs/> [retrieved on 20180216] *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12137382B2 (en) 2018-05-11 2024-11-05 Vivo Mobile Communication Co., Ltd. Method for processing CSI processing unit, apparatus, and system
US20220377636A1 (en) * 2018-05-11 2022-11-24 Vivo Mobile Communication Co.,Ltd. Resource processing method, apparatus, and system
US11825363B2 (en) * 2018-05-11 2023-11-21 Vivo Mobile Communication Co., Ltd. Resource processing method, apparatus, and system
US20210168815A1 (en) * 2018-08-10 2021-06-03 Lg Electronics Inc. Method for configuring bandwidth part in wireless communication system and device for supporting same
US11570784B2 (en) * 2018-08-10 2023-01-31 Lg Electronics Inc. Method for configuring bandwidth part in wireless communication system and device for supporting same
US11659600B2 (en) 2020-02-28 2023-05-23 Samsung Electronics Co., Ltd. Method and apparatus for random access procedure
WO2021172937A1 (fr) * 2020-02-28 2021-09-02 Samsung Electronics Co., Ltd. Procédé et appareil pour procédure d'accès aléatoire
CN115280882A (zh) * 2020-03-12 2022-11-01 诺基亚技术有限公司 启用能力降低的新无线电（nr）设备的接入
EP4118917A4 (fr) * 2020-03-12 2024-03-13 Nokia Technologies Oy Autorisation d'accès pour un dispositif nouvelle radio (nr) à capacité réduite
WO2021223091A1 (fr) * 2020-05-06 2021-11-11 Qualcomm Incorporated Sélection de ressources de procédure d'accès aléatoire
CN115486177A (zh) * 2020-05-08 2022-12-16 高通股份有限公司 用于全双工通信的频域资源分配技术
CN115486177B (zh) * 2020-05-08 2025-03-04 高通股份有限公司 用户设备和基站处的无线通信方法和用于无线通信的装置
WO2024016278A1 (fr) * 2022-07-21 2024-01-25 Zte Corporation Procédés et dispositifs d'accès aléatoire en duplex intégral de sous-bande

Similar Documents

Publication Publication Date Title
US12376129B2 (en) Supplementary uplink transmissions in wireless systems
JP7729798B2 (ja) ワイヤレスシステムにおけるサプリメンタリィアップリンクアクセスのための方法
WO2019195445A1 (fr) Procédés destinés à la gestion d&#39;une partie de largeur de bande dans des systèmes sans fil
WO2020033562A1 (fr) Procédés et appareils de synchronisation dans un système sans fil
WO2018204351A1 (fr) Multiplexage et mappage de signaux de synchronisation en nr
US20240407016A1 (en) Robust bwp approaches to mitigate the impact of high power narrow-band interferer
WO2025034872A1 (fr) Coordination inter-wtru pour sélection de porteuse
EP4500946A1 (fr) Système et procédés pour prendre en charge un flux et un profil de qos auto-adaptatifs
US20250374111A1 (en) System and methods for supporting self-adaptive qos flow and profile
WO2024211426A1 (fr) Procédés et appareils pour une wtru d&#39;émission pour identifier une wtru de synchronisation et demander une émission s-ssb sur un ou plusieurs ensembles de rb
WO2024211428A1 (fr) Procédés et appareils pour une wtru de synchronisation pour indiquer des ensembles rb utilisés aux fins d&#39;une transmission ssb
WO2024211424A1 (fr) Procédés et appareils pour utiliser des ressources réservées de liaison latérale pour déterminer un ou plusieurs ensembles de rb pour une transmission ssb
WO2025034869A1 (fr) Détermination d&#39;une porteuse pour transmettre un psfch à un pscch/pssch de rétroaction
WO2024173566A1 (fr) Procédé et appareil de transmission d&#39;une demande de planification sur la base d&#39;une condition
WO2025034861A1 (fr) Resélection de ressources de préemption
WO2025240743A1 (fr) Saut de fréquence s_ssb pour liaison latérale robuste dans des environnements contestés et congestionnés
WO2025034325A1 (fr) Sélection de ressources pour de multiples porteuses avec porteuses sous licence et sans licence
WO2025034873A1 (fr) Procédure de synchronisation
WO2025034866A1 (fr) Sélection de porteuse
WO2024173455A1 (fr) Procédés et appareils de rapport de retransmissions autonomes
WO2025212596A1 (fr) Procédés de planification d&#39;améliorations pour un canal physique à travers des symboles sbfd et non sbfd
WO2024173454A1 (fr) Procédés et appareils pour la priorisation de retour d&#39;informations de demande de répétition automatique hybride pour autorisation configurée de liaison latérale
WO2025019348A1 (fr) Détermination de seuil de support divisé pour trajets multiples avec de multiples trajets indirects
WO2024173315A1 (fr) Détermination de données de bloc de transport
WO2024168262A1 (fr) Contrôle d&#39;accès d&#39;une wtru à un relais de réseau relatif à un service ai/ml

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

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

Country of ref document: EP

Kind code of ref document: A1