WO2022147642A1 - Procédures de transfert intercellulaire vers l'arrière pour mobilité de relais l2 - Google Patents

Procédures de transfert intercellulaire vers l'arrière pour mobilité de relais l2 Download PDF

Info

Publication number
WO2022147642A1
WO2022147642A1 PCT/CN2021/070253 CN2021070253W WO2022147642A1 WO 2022147642 A1 WO2022147642 A1 WO 2022147642A1 CN 2021070253 W CN2021070253 W CN 2021070253W WO 2022147642 A1 WO2022147642 A1 WO 2022147642A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay
base station
paging messages
paging
request
Prior art date
Application number
PCT/CN2021/070253
Other languages
English (en)
Inventor
Peng Cheng
Karthika Paladugu
Hong Cheng
Ozcan Ozturk
Gavin Bernard Horn
Original Assignee
Qualcomm Incorporated
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 Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2021/070253 priority Critical patent/WO2022147642A1/fr
Priority to TW110148269A priority patent/TW202233005A/zh
Publication of WO2022147642A1 publication Critical patent/WO2022147642A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/23—Manipulation of direct-mode connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • the following relates to wireless communication, including backward handover procedures for layer two (L2) relay mobility.
  • L2 layer two
  • 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 fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • UE user equipment
  • Some wireless communications networks may support relayed or sidelink communications to extend coverage and increase reliability between devices in the network.
  • Conventional techniques for establishing and maintaining the sidelink may be deficient.
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support handover procedures (e.g., backward handover procedures) for layer two (L2) relay mobility.
  • a user equipment e.g., a remote UE
  • the base station may select the relay UE from a set of candidate relay UEs to enable the remote UE to communicate with the base station via the relay UE.
  • the base station may additionally identify a connection state of the selected relay UE based on one or more measurement reports received from the remote UE.
  • the base station may identify that the connection state of the relay UE is an idle state or an inactive state.
  • one or more paging message may be transmitted to the relay UE prior to the base station performing a connection establishment procedure or a connection resumption procedure with the relay UE.
  • an access and mobility management function (AMF) or an anchor base station associated with the relay UE may transmit the one or more paging messages to the relay UE prior to the connection establishment procedure or connection resumption procedure.
  • the paging messages sent to the relay UE may trigger the UE to establish or resume a connection with the base station (e.g., based on the relay UE’s connection state) , which may result in a relay link between the remote UE and the base station via the relay UE.
  • a method for wireless communication at a base station may include identifying a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates, identifying a connection state of the relay UE based on a measurement report from the UE, and performing a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE.
  • the apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to identify a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates, identify a connection state of the relay UE based on a measurement report from the UE, and perform a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE.
  • the apparatus may include means for identifying a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates, means for identifying a connection state of the relay UE based on a measurement report from the UE, and means for performing a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE.
  • a non-transitory computer-readable medium storing code for wireless communication at a base station is described.
  • the code may include instructions executable by a processor to identify a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates, identify a connection state of the relay UE based on a measurement report from the UE, and perform a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to a network node, a request to page the relay UE based on the connection state of the relay UE, where the one or more paging messages may be transmitted to the relay UE in response to the request to page the relay UE.
  • identifying the connection state of the relay UE may include operations, features, means, or instructions for identifying that the relay UE may be in an idle state based on the measurement report, where the network node includes an AMF associated with the base station.
  • identifying the connection state of the relay UE may include operations, features, means, or instructions for identifying that the relay UE may be in an inactive state based on the measurement report, where the network node includes an anchor base station associated with the relay UE.
  • the request to page the relay UE indicates a paging cause including a relay path switch.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the relay UE, the one or more paging messages from the network node based on a request to page the relay UE, the one or more paging messages transmitted via core network paging, where the network node includes an AMF associated with the relay UE.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the relay UE, the one or more paging messages from the network node based on a request to page the relay UE, the one or more paging messages transmitted via core network paging, where the network node includes an AMF associated with the base station.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the relay UE, the one or more paging messages based on the connection state of the relay UE, where the one or more paging messages may be transmitted via radio access network (RAN) paging.
  • RAN radio access network
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to an anchor base station associated with the relay UE, a request for context information for the relay UE and receiving, from the anchor base station and in response to the request for the context information, an indication of the context information for the relay UE, where transmitting the one or more paging messages may be based on the context information for the relay UE.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the measurement report from the UE, where the measurement report includes an indication of the connection state of the relay UE, an identifier of the relay UE, a cell identifier of the relay UE, or any combination thereof, where the relay pairing may be based on the measurement report.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for generating a handover command for the UE based on the connection establishment procedure establishing a connection between the relay UE and the base station, configuring a relay bearer mapping associated with the relay pairing based on generating the handover command, and transmitting a reconfiguration message to the relay UE, the reconfiguration message including an indication of the configured relay bearer mapping.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying context information for the relay UE based on the one or more paging messages transmitted to the relay UE, where generating the handover command and configuring the relay bearer mapping may be based on the identified context information for the relay UE.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the UE, a handover command based on the relay pairing between the UE and the relay UE, where the handover command includes a radio link control configuration of a sidelink channel between the UE and the relay UE.
  • a method for wireless communication at a relay UE may include receiving one or more paging messages associated with modifying a relay path to include the relay UE, transmitting, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based on a connection state of the relay UE, where the message is transmitted in response to receiving the one or more paging message, and receiving a reconfiguration message including a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • the apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to receive one or more paging messages associated with modifying a relay path to include the relay UE, transmit, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based on a connection state of the relay UE, where the message is transmitted in response to receiving the one or more paging message, and receive a reconfiguration message including a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • the apparatus may include means for receiving one or more paging messages associated with modifying a relay path to include the relay UE, means for transmitting, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based on a connection state of the relay UE, where the message is transmitted in response to receiving the one or more paging message, and means for receiving a reconfiguration message including a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • a non-transitory computer-readable medium storing code for wireless communication at a relay UE is described.
  • the code may include instructions executable by a processor to receive one or more paging messages associated with modifying a relay path to include the relay UE, transmit, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based on a connection state of the relay UE, where the message is transmitted in response to receiving the one or more paging message, and receive a reconfiguration message including a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • receiving the one or more paging messages may include operations, features, means, or instructions for receiving the one or more paging messages via core network paging, where the one or more paging messages may be from an AMF associated with the relay UE.
  • receiving the one or more paging messages may include operations, features, means, or instructions for receiving the one or more paging messages via core network paging, where the one or more paging messages may be from an AMF associated with the base station.
  • receiving the one or more paging messages may include operations, features, means, or instructions for receiving the one or more paging messages via RAN paging, where the one or more paging messages may be from an anchor base station associated with the relay UE.
  • receiving the one or more paging messages may include operations, features, means, or instructions for receiving the one or more paging messages via RAN paging, where the one or more paging messages may be from the base station, the base station being different from an anchor base station associated with the relay UE.
  • the connection state of the relay UE includes an idle state or an inactive state.
  • a method for wireless communications at a first network node may include receiving, from a second network node, a request to page a relay UE based on modifying a relay path to include the relay UE, where the request to page the relay UE indicates a paging cause including a relay path switch and transmitting, to the relay UE, one or more paging messages in response to the request to page the relay UE.
  • the apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to receive, from a second network node, a request to page a relay UE based on modifying a relay path to include the relay UE, where the request to page the relay UE indicates a paging cause including a relay path switch and transmit, to the relay UE, one or more paging messages in response to the request to page the relay UE.
  • the apparatus may include means for receiving, from a second network node, a request to page a relay UE based on modifying a relay path to include the relay UE, where the request to page the relay UE indicates a paging cause including a relay path switch and means for transmitting, to the relay UE, one or more paging messages in response to the request to page the relay UE.
  • a non-transitory computer-readable medium storing code for wireless communications at a first network node is described.
  • the code may include instructions executable by a processor to receive, from a second network node, a request to page a relay UE based on modifying a relay path to include the relay UE, where the request to page the relay UE indicates a paging cause including a relay path switch and transmit, to the relay UE, one or more paging messages in response to the request to page the relay UE.
  • transmitting the one or more paging messages may include operations, features, means, or instructions for transmitting the one or more paging messages via core network paging, where the first network node includes a first AMF associated with the relay UE, and where the second network node includes second AMF associated with a base station.
  • transmitting the one or more paging messages may include operations, features, means, or instructions for transmitting the one or more paging messages via core network paging, where the first network node includes an AMF associated with a base station, and where the second network node includes the base station.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to a second a second AMF associated with the relay UE, a request for context information for the relay UE, where the request for the context information may be based on receiving the request to page the relay UE and receiving, from the second AMF, the context information for the relay UE based on the request for the context information.
  • transmitting the one or more paging messages may include operations, features, means, or instructions for transmitting the one or more paging messages via core network paging, where the first network node includes an anchor base station associated with the relay UE, and where the second network node includes a base station different from the anchor base station.
  • FIG. 1 illustrates an example of a wireless communications system that supports backward handover procedures for layer two (L2) relay mobility in accordance with aspects of the present disclosure.
  • FIG. 2 illustrates an example of a wireless communications system that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIGs. 3 and 4 illustrate example process flows in a system that support backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example of a process flow that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIGs. 5 and 6 show block diagrams of devices that support backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIG. 7 shows a block diagram of a communications manager that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIG. 8 shows a diagram of a system including a device that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIGs. 9 and 10 show block diagrams of devices that support backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIG. 11 shows a block diagram of a communications manager that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIG. 12 shows a diagram of a system including a device that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIGs. 13 and 14 show block diagrams of devices that support backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIG. 15 shows a block diagram of a communications manager that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIG. 16 shows a diagram of a system including a device that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • FIGs. 17 through 22 show flowcharts illustrating methods that support backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • a user equipment may utilize Device-to-Device (D2D) communications (which may also be referred to as sidelink communications) , where a first UE may transmit data via a direct link or sidelink to a second UE in the network.
  • D2D Device-to-Device
  • sidelink communications may enable one or more remote UEs (for example, UEs that are out-of-coverage of the wireless network) to communicate with the network via a relay UE (for example, a UE that is in-coverage of the wireless network) .
  • relayed communications may efficiently redirect traffic to and from remote UEs in proximity of the network and thus may extend coverage of the wireless network.
  • a base station may identify a relay pairing between the UE and the relay UE (e.g., from a set of relay UE candidates) .
  • the UE may transmit one or more measurement reports to the base station.
  • the remote UE may be mobile and may provide measurement reporting to the base station based on the UE’s mobility (e.g., including measurements of one or more potential relay UEs while the UE is mobile) .
  • the base station may identify the relay pairing.
  • the base station may then configure a radio bearer mapping associated with the relay pairing and transmit a reconfiguration message to the UE indicating the configured relay bearer mapping.
  • the UE may be configured to communicate with the base station via the relay UE.
  • the base station may identify that the relay UE is in an inactive or idle connection state (e.g., based on the measurement report received from the UE) .
  • context information for the relay UE may not be available to the base station, and the base station may therefore be unable to configure the radio bearer mapping associated with the relay UE.
  • one or more paging messages may be transmitted to the relay UE prior to the base station configuring the radio bearer mapping associated with the relay pairing.
  • the one or more paging messages may trigger the relay UE to perform a connection establishment procedure or connection resumption procedure with the base station.
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are then described in the context of process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to backward handover procedures for layer two (L2) relay mobility.
  • L2 layer two
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-A Pro
  • NR New Radio
  • the wireless communications system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.
  • Wireless communications system 100 may support triggering of connection establishment or connection resumption procedures through paging a relay UE that is in an idle or inactive state.
  • the base stations 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may be devices in different forms or having different capabilities.
  • the base stations 105 and the UEs 115 may wirelessly communicate via one or more communication links 125.
  • Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base station 105 may establish one or more communication links 125.
  • the coverage area 110 may be an example of a geographic area over which a base station 105 and a UE 115 may support the communication of signals according to one or more radio access technologies.
  • the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
  • the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115, the base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment) , as shown in FIG. 1.
  • network equipment e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment
  • the base stations 105 may communicate with the core network 130, or with one another, or both.
  • the base stations 105 may interface with the core network 130 through one or more backhaul links 120 (e.g., via an S1, N2, N3, or other interface) .
  • the base stations 105 may communicate with one another over the backhaul links 120 (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations 105) , or indirectly (e.g., via core network 130) , or both.
  • the backhaul links 120 may be or include one or more wireless links.
  • One or more of the base stations 105 described herein may include or may be referred to by a person having ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a Home NodeB, a Home eNodeB, or other suitable terminology.
  • a base transceiver station a radio base station
  • an access point a radio transceiver
  • a NodeB an eNodeB (eNB)
  • eNB eNodeB
  • a next-generation NodeB or a giga-NodeB either of which may be referred to as a gNB
  • gNB giga-NodeB
  • a UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples.
  • a UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the base stations 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • devices such as other UEs 115 that may sometimes act as relays as well as the base stations 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the base stations 105 may wirelessly communicate with one another via one or more communication links 125 over one or more carriers.
  • the term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links 125.
  • a carrier used for a communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • BWP bandwidth part
  • Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling.
  • the wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.
  • a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN) ) and may be positioned according to a channel raster for discovery by the UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • a carrier may be operated in a standalone mode where initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode where a connection is anchored using a different carrier (e.g., of the same or a different radio access technology) .
  • the communication links 125 shown in the wireless communications system 100 may include uplink transmissions from a UE 115 to a base station 105, or downlink transmissions from a base station 105 to a UE 115.
  • Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • a carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a number of determined bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
  • Devices of the wireless communications system 100 e.g., the base stations 105, the UEs 115, or both
  • the wireless communications system 100 may include base stations 105 or UEs 115 that support simultaneous communications via carriers associated with multiple carrier bandwidths.
  • each served UE 115 may be configured for operating over portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
  • Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
  • MCM multi-carrier modulation
  • a resource element may include one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related.
  • the number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) .
  • a wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams) , and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE 115.
  • One or more numerologies for a carrier may be supported, where a numerology may include a subcarrier spacing ( ⁇ ? ) and a cyclic prefix.
  • a carrier may be divided into one or more BWPs having the same or different numerologies.
  • a UE 115 may be configured with multiple BWPs.
  • a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
  • Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) .
  • Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
  • SFN system frame number
  • Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots.
  • each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing.
  • Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
  • a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
  • TTI duration e.g., the number of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
  • Physical channels may be multiplexed on a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • a control region e.g., a control resource set (CORESET)
  • CORESET control resource set
  • a control region for a physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier.
  • One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to a number of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
  • Each base station 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof.
  • the term “cell” may refer to a logical communication entity used for communication with a base station 105 (e.g., over a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) , or others) .
  • a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) over which the logical communication entity operates.
  • Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the base station 105.
  • a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with geographic coverage areas 110, among other examples.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell.
  • a small cell may be associated with a lower-powered base station 105, as compared with a macro cell, and a small cell may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells.
  • Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) .
  • a base station 105 may support one or multiple cells and may also support communications over the one or more cells using one or multiple component carriers.
  • a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
  • protocol types e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB)
  • NB-IoT narrowband IoT
  • eMBB enhanced mobile broadband
  • a base station 105 may be movable and therefore provide communication coverage for a moving geographic coverage area 110.
  • different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105.
  • the overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105.
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.
  • the wireless communications system 100 may support synchronous or asynchronous operation.
  • the base stations 105 may have similar frame timings, and transmissions from different base stations 105 may be approximately aligned in time.
  • the base stations 105 may have different frame timings, and transmissions from different base stations 105 may, in some examples, not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • Some UEs 115 may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station 105 without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that makes use of the information or presents the information to humans interacting with the application program.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception simultaneously) .
  • half-duplex communications may be performed at a reduced peak rate.
  • Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating over a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques.
  • some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
  • the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications.
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions) .
  • Ultra-reliable communications may include private communication or group communication and may be supported by one or more mission critical services such as mission critical push-to-talk (MCPTT) , mission critical video (MCVideo) , or mission critical data (MCData) .
  • MCPTT mission critical push-to-talk
  • MCVideo mission critical video
  • MCData mission critical data
  • Support for mission critical functions may include prioritization of services, and mission critical services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, mission critical, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may also be able to communicate directly with other UEs 115 over a D2D communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol) .
  • P2P peer-to-peer
  • One or more UEs 115 utilizing D2D communications may be within the geographic coverage area 110 of a base station 105.
  • Other UEs 115 in such a group may be outside the geographic coverage area 110 of a base station 105 or be otherwise unable to receive transmissions from a base station 105.
  • groups of the UEs 115 communicating via D2D communications may utilize a one-to-many (1: M) system in which each UE 115 transmits to every other UE 115 in the group.
  • a base station 105 facilitates the scheduling of resources for D2D communications.
  • D2D communications are carried out between the UEs 115 without the involvement of a base station 105.
  • the D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) .
  • vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these.
  • V2X vehicle-to-everything
  • V2V vehicle-to-vehicle
  • a vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system.
  • vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., base stations 105) using vehicle-to-network (V2N) communications, or with both.
  • V2N vehicle-to-network
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the base stations 105 associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to IP services 150 for one or more network operators.
  • the IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • Some of the network devices may include subcomponents such as an access network entity 140, which may be an example of an access node controller (ANC) .
  • Each access network entity 140 may communicate with the UEs 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs) .
  • Each access network transmission entity 145 may include one or more antenna panels.
  • various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station 105) .
  • the wireless communications system 100 may operate using one or more frequency bands, for example, in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors.
  • the transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • the wireless communications system 100 may also operate in a super high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter band, or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band.
  • SHF super high frequency
  • EHF extremely high frequency
  • the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the base stations 105, and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate use of antenna arrays within a device.
  • mmW millimeter wave
  • the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions.
  • the techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
  • the wireless communications system 100 may utilize both licensed and unlicensed radio frequency spectrum bands.
  • the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the base stations 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA) .
  • Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
  • a base station 105 or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
  • the antennas of a base station 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a base station 105 may be located in diverse geographic locations.
  • a base station 105 may have an antenna array with a number of rows and columns of antenna ports that the base station 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.
  • an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port.
  • the base stations 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase the spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) .
  • Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) , where multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , where multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • a base station 105 or a UE 115 may use beam sweeping techniques as part of beam forming operations.
  • a base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115.
  • Some signals e.g., synchronization signals, reference signals, beam selection signals, or other control signals
  • the base station 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission.
  • Transmissions in different beam directions may be used to identify (e.g., by a transmitting device, such as a base station 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the base station 105.
  • a transmitting device such as a base station 105
  • a receiving device such as a UE 115
  • Some signals may be transmitted by a base station 105 in a single beam direction (e.g., a direction associated with the receiving device, such as a UE 115) .
  • the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted in one or more beam directions.
  • a UE 115 may receive one or more of the signals transmitted by the base station 105 in different directions and may report to the base station 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
  • transmissions by a device may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from a base station 105 to a UE 115) .
  • the UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across a system bandwidth or one or more sub-bands.
  • the base station 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded.
  • a reference signal e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS)
  • CRS cell-specific reference signal
  • CSI-RS channel state information reference signal
  • the UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) .
  • PMI precoding matrix indicator
  • codebook-based feedback e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook
  • a UE 115 may employ similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal in a single direction (e.g., for transmitting data to a receiving device) .
  • a receiving device may try multiple receive configurations (e.g., directional listening) when receiving various signals from the base station 105, such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • receive configurations e.g., directional listening
  • a receiving device may try multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions.
  • receive beamforming weight sets e.g., different directional listening weight sets
  • a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) .
  • the single receive configuration may be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
  • SNR signal-to-noise ratio
  • the wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack.
  • communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based.
  • a Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels.
  • RLC Radio Link Control
  • a Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency.
  • the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a base station 105 or a core network 130 supporting radio bearers for user plane data.
  • RRC Radio Resource Control
  • transport channels may be mapped to physical channels.
  • the UEs 115 and the base stations 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly over a communication link 125.
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) .
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions) .
  • a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • a UE 115 may be transferred from a serving base station 105 (known as the source base station) to another base station 105 (known as the target base station) .
  • the UE 115 may be moving into the coverage area of the target base station 105, or the target base station 105 may be capable of providing better service for the UE 115 or relieving the source base station 105 of excess load.
  • the transition may be referred to as a “handover. ”
  • the source base station 105 may configure the UE 115 with procedures for measuring the signal quality of neighboring base stations 105.
  • the UE 115 may then respond with a measurement report.
  • the source base station 105 may use the measurement report to make the handover decision.
  • the decision may also be based on radio resource management (RRM) factors such as network load and interference mitigation.
  • RRM radio resource management
  • the source base station 105 may send a handover request message to the target base station 105, which may include context information to prepare the target base station 105 to serve the UE 115.
  • the target base station 105 may make an admission control decision, for example, to ensure that it can meet the quality of service (QoS) standards of the UE 115.
  • QoS quality of service
  • the target base station 105 may then configure resources for the incoming UE 115, and send a handover request acknowledge message to the source base station 105, which may include RRC information to be passed on to the UE 115.
  • the source base station 105 may then direct the UE 115 to perform the handover, and pass a status transfer message to the target base station with packet data convergence protocol (PDCP) bearer status information.
  • PDCP packet data convergence protocol
  • the UE 115 may attach to the target base station via a random access procedure.
  • a UE 115 may operate in accordance with various states or modes for communicating with a network.
  • a UE 115 may operate in an RRC idle state (e.g., RRC_IDLE) , an RRC inactive state (e.g., RRC_INACTIVE) , and/or an RRC connected state (e.g., RRC_CONNECTED) .
  • the UE 115 may transition between the various states or modes, for example, based on communications traffic for the UE 115.
  • a UE 115 may not be registered to a particular cell, and may accordingly lack an access stratum (AS) context, and the UE 115 may thus not have an active RRC connection established with the network (e.g., via a base station 105) .
  • the UE 115 may wake up periodically to monitor channels for paging or other signaling, and the mobility of the UE 115 may be managed by the UE 115 when performing measurements of one or more cells.
  • the UE 115 may have an established RRC connection (e.g., with a 5GC) where the UE 115 may store an AS context.
  • the UE 115 may belong to a known cell and may be identified using a cell radio network temporary identifier (C-RNTI) assigned to the UE 115.
  • C-RNTI cell radio network temporary identifier
  • the UE 115 may monitor for messages transmitted by the network, which may include monitoring various channels (e.g., paging channels, control channels, or the like) .
  • the RRC inactive state may be used to reduce signaling overhead and may provide an intermediate mode or state (e.g., between idle and connected) , which may also be used to reduced latency when transitioning to another state (e.g., to the connected state) .
  • the UE 115 may periodically wake up while in the inactive state to monitor for paging messages from the network, where the UE 115 may, in some cases, perform a random access procedure to move to the connected mode and communicate with the network.
  • a UE 115 may utilize D2D communications, which may also be referred to as sidelink communications (e.g., communications over a sidelink communication link) , where a first UE 115 may transmit data via a direct link or sidelink to a second UE 115 in the network.
  • sidelink communications may enable one or more remote UEs 115 (for example, UEs 115 that are out-of-coverage of the wireless network) to communicate with the network via a relay UE 115 (for example, a UE 115 that is in-coverage of the wireless network) .
  • relayed communications may efficiently redirect traffic to and from remote UEs 115 in proximity of the network and thus may extend coverage of the wireless network.
  • a base station 105 may identify a relay pairing between the UE 115 and the relay UE 115 (e.g., from a set of relay UE 115 candidates) . For example, the UE 115 may transmit a measurement report to the base station 105 and, based on the measurement report, the base station 105 may identify the relay pairing. Based on identifying the relay pairing, the base station 105 may configure a radio bearer mapping associated with the relay pairing and transmit a reconfiguration message (e.g., and RRC reconfiguration message) to the UE 115 indicating the configured relay bearer mapping. Thus, the UE 115 may be configured to communicate with the base station 105 via the relay UE 115.
  • a reconfiguration message e.g., and RRC reconfiguration message
  • the base station 105 may identify that the relay UE 115 is in an inactive or idle connection state. In these instances, the base station 105 may not store context information for the relay UE 115 and may therefore be unable to configure the radio bearer mapping associated with the relay UE 115.
  • one or more paging messages may be transmitted to the relay UE 115 prior to performing the connection establishment procedure or the connection resumption procedure. In some cases, the one or more paging messages may trigger the relay UE 115 to perform the connection establishment procedure or the connection resumption procedure with the base station 105. After performing the connection establishment procedure or the connection resumption procedure, the base station 105 may store the context information associate with the relay UE 115 and may configure the radio bearer mapping associated with the relay pairing accordingly.
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • wireless communications system 200 may implement aspects of wireless communications system 100.
  • the wireless communications system 200 may include a base station 105-a and UEs 115-a, 115-b, and 115-c, which may be examples of base stations 105 and UEs 115 as described with reference to FIG. 1.
  • Base station 105-a may serve a number of cells or geographic coverage areas (for example, geographic coverage area 110-a) .
  • UEs 115 may utilize D2D communications, where a first UE 115-a may transmit data via a direct link or sidelink to a second UE 115-b in the network coverage area 110-a.
  • sidelink communications may enable remote UEs 115 (e.g., such as a UE 115-a that is out of coverage of the wireless network) to communicate with the network via a relay UE 115 (e.g., such as UE 115-b or 115-c that is in-coverage of the wireless network) .
  • relayed communications may efficiently redirect traffic to and from remote UEs 115 in proximity of the network and may extend coverage of the wireless network.
  • relay selection may be performed in accordance with L2 routing.
  • the relay UE 115-b may relay data below the PDCP layer.
  • the user plane protocol stack 205 associated with the L2 relay includes a protocol data unit (PDU) connected to a PDCP layer which is connected to a sidelink RLC layer. PDUs provided by the RLC layer are directed to a device to network (D2N) MAC entity or a D2D MAC entity.
  • D2D MAC may provide a connection to the base station 105-a via Uu interface, and the D2D MAC connects to relay UE 115-b via a sidelink 225 (e.g., PC5) .
  • sidelink 225 e.g., PC5
  • the relay UE 115-b may forward the PC5 bearer and the Uu bearer using an adaptation layer function.
  • traffic may terminate at the core network which may prevent direct communication between the remote UE 115-a (e.g., data radio bearers of the remote UE 115-a may be controlled by the network) .
  • the network may be aware of the relay configuration between the remote UE 115-a and a number of relay UE candidates 115-b and 115-c, and may select a sidelink relay pairing (e.g., a pairing between remote UE 115-a and relay UE 115-b) based on link strength or quality of the relay link. Such relay selection by the network may increase the quality and reliability of relayed communications and may further extend coverage of the wireless communications system.
  • the remote UE 115-a may include both the PC5 C-plane and the NR Uu C-plane.
  • the PC5 C-plane may be for setting up a unicast link prior to communicating with the base station 105-a via the relay UE 115-b.
  • the remote UE 115-a may support NR Uu access stratum (AS) and non-access stratum (NAS) connections (e.g., above the PC5 RLC layer) .
  • the NG-RAN may control the sidelink 225 (e.g., the PC5 link) via NR RRC.
  • the adaptation layer may support multiplexing traffic associated with multiple UEs 115 on the relay UE 115-b Uu interface.
  • the UE 115-a may be in direct communication with the base station 105-a prior to communicating with the base station 105-a via the relay UE 115-b.
  • the UE 115-a may communicate uplink and downlink communications directly with the base station 105-a.
  • the UE 115-a may transmit a measurement report to the base station 105-a.
  • the UE 115-a may be mobile and may transmit a measurement report to the base station 105-a, where the measurement report may provide information on nearby candidate UEs 115 that may be selected for a relay pairing (e.g., based on the mobility of UE 115-a) .
  • the measurement report may indicate one or more parameters associated with each of the candidate relay UEs 115-b and 115-c.
  • the measurement report may indicate a connection state of the relay UEs 115-b and 115-c, an identifier of each relay UE 115-b and 115-c, and an indication of context information for the relay UEs 115-b and 115-c.
  • the base station 105-a may determine to perform a handover with the UE 115-a to switch from communicating directly with the UE 115-a to communicating with the UE 115-a via the relay UE 115-b. For example, the base station 105-a may identify a relay pairing between the UE 115-a and the relay UE 115-b. In some cases, the base station 105-a may determine to perform the handover based on determining that a signal quality for communications between the UE 115-a and the base station 105-a may be improved by performing the handover.
  • the base station 105-a may configure a radio bearer mapping associated with the relay pairing and transmit a reconfiguration message (e.g., and RRC reconfiguration message) to the UEs 115-a and 115-b indicating the configured relay bearer mapping.
  • a reconfiguration message e.g., and RRC reconfiguration message
  • the UE 115-a may be configured to communicate with the base station 105-a via the relay UE 115-b.
  • the base station 105-a may identify that the relay UE 115-b is in an inactive or idle connection state (e.g., RRC_INACTIVE or RRC_IDLE) .
  • the base station 105-a may identify the connectivity state of the relay UE 115-b based on receiving the measurement report from the UE 115-a, where the UE 115-a may indicate the connectivity state for UE 115-b within a measurement report, among other information.
  • the base station 105-a may not store context information for the relay UE 115-b and may therefore be unable to configure the radio bearer mapping associated with the relay UE 115-b.
  • one or more paging messages may be transmitted to the relay UE 115-b prior to the base station 105-a configuring the radio bearer mapping associated with the relay pairing between the UE 115-a and 115-b. That is, the one or more paging messages may trigger the relay UE 115-b to perform a connection establishment procedure or a connection resumption procedure with the base station 105-a (e.g., to transition out of the idle or inactive connection state) .
  • the base station 105-a may store the context information associate with the relay UE 115-b, thus enabling the base station 105-a to configure the radio bearer mapping associated with the relay pairing.
  • the base station 105-a may transmit, to another network node (e.g., an AMF associated with the base station 105-a) , a request to page the relay UE 115-b after determining to perform the handover (e.g., a Uu to PC5 handover) with the UE 115-a to switch from communicating directly with the UE 115-a to communicating with the UE 115-a via the relay UE 115-b.
  • the AMF associated with the base station may determine the context information associated with the relay UE 115-b based on communicating with an AMF associated with the relay UE 115-b.
  • the AMF associated with the base station 105-a may then transmit (e.g., via the base station 105-a) the one or more paging messages to the relay UE 115-b based on determining the context information associated with the relay UE 115-b.
  • the AMF associated with the base station may communicate the paging request (e.g., received from the base station 105-a) to the AMF associated with the relay UE 115-b.
  • the AMF associated with the relay UE 115-b may transmit (e.g., via the base station 105-a) the one or more paging messages to the relay UE 115-b.
  • the base station 105-a may not be an anchor base station 105 for the relay UE 115-b.
  • the base station 105-a may transmit, to the anchor base station 105 for the relay UE 115-b, a request to page the relay UE 115-b after determining to perform the handover with the UE 115-a to switch from communicating directly with the UE 115-a to communicating with the UE 115-a via the relay UE 115-b.
  • the anchor base station 105 may then transmit the one or more paging messages to the relay UE 115-b.
  • the base station 105-a may retrieve the context information associated with the relay UE 115-b from the anchor base station 105 associated with the relay UE 115-b.
  • the base station 105-a may then transmit the one or more paging messages to the relay UE 115-b based on retrieving the context information from the anchor base station 105 associated with the relay UE 115-b.
  • the handover to switch from communicating directly with the UE 115-a to communicating with the UE 115-a via the relay UE 115-b may additionally include a handover from the source base station 105-a to a different base station 105 (e.g., a target base station 105) .
  • a different base station 105 e.g., a target base station 105
  • the handover between the source and target base station 105 may be based on the mobility of the UE 115-a, based on a relay UE 115-b that is selected for the relay pairing, or for some other reasons. But in some other cases, the source and target base stations 105 may the same base station 105-a.
  • FIG. 3 illustrates an example of a process flow 300 in a system that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the process flow 300 includes UEs 115-d and 115-e and base stations 105-b and 105-c, which may be examples of the corresponding devices described with reference to FIGs. 1–2.
  • the process flow 300 may additionally include AMFs 305-a and 305-b.
  • the AMF 305-a may be associated with the base station 105-b and the AMF 305-b may be associated with the relay UE 115-e.
  • the source base station 105-b and the target base station 105-c may be the same base station 105.
  • Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.
  • the process flow 300 illustrates an example of a backward handover procedure (e.g., initiated by a base station 105) to switch the remote UE 115-d from communicating directly with the base station 105-b to communicating with the base station 105-c via the relay UE 115-e in a case that the relay UE 115-e is in an idle state (e.g., RRC_IDLE) .
  • a backward handover procedure e.g., initiated by a base station 105
  • RRC_IDLE an idle state
  • the remote UE 115-d may communicate directly with the base station 105-b (e.g., a source base station 105-b) .
  • the remote UE 115-d may transmit uplink data to the base station 105-b and the base station 105-b may transmit downlink data to the remote UE 115-d.
  • the remote UE 115-d may transmit a measurement report (e.g., a mobility trigger) to the base station 105-b.
  • the measurement report may include an indication of the connection state of the relay UE 115-e (e.g., an RRC state of the relay UE 115-e) , an identifier of the relay UE 115-e, a cell identifier of the relay UE 115-e, or any combination thereof.
  • the identifier of the relay UE 115-e may include a serving temporary mobile subscriber identity (S-TMSI) , such as a 5G-S-TMSI, or a hashed version of a 5G-S-TMSI, or the like.
  • S-TMSI serving temporary mobile subscriber identity
  • the source base station 105-b and the target base station 105-c may make a handover decision.
  • the base stations 105-b and 105-c may determine to handover the remote UE 115-d from communicating directly with the source base station 105-b to communicating with the target base station 105-c via the relay UE 115-e.
  • the source base station 105-b and the target base station 105-c may be the same.
  • the handover decision may relate to switching the remote UE 115-d from communicating directly with the base station 105 to communicating with the base station 105 via the relay UE 115-e (e.g., a Uu to PC5 handover) .
  • the target base station 105-c may identify a relay pairing between the remote UE 115-d and the relay UE 115-e.
  • the target base station 105-c may transmit a request to page the relay UE 115-e based on the connection state of the relay UE 115-e.
  • the measurement report (e.g., transmitted by the remote UE 115-d at 315) may indicate that the relay UE 115-e is in an idle state.
  • the target base station 105-c may transmit the page request to the AMF 305-a that is associated with the base station 105-c.
  • the page request may indicate a paging cause including a relay path switch (e.g., including the relay UE 115-e) .
  • the AMF 305-a may optionally forward the paging request to the AMF 305-b. That is, if the AMF 305-a is not associated with the relay UE 115-e, the AMF 305-a may forward the paging request to the AMF 305-b that is associated with the relay UE 115-e. In a case that the AMF 305-a is associated with the relay UE 115-e, the AMF 305-a may not forward the paging request to another AMF 305-b and instead proceed to 345.
  • the AMF 305-b may optionally transmit one or more paging messages to the target base station 105-c in response to receiving the forwarded paging request from the AMF 305-a. That is, in a case that the AMF 305-a does not forward the paging request to the AMF 305-b, the AMF 305-b may not transmit the one or more paging messages to the target base station 105-c.
  • the AMF 305-a may optionally receive context information for the relay UE 115-e from the AMF 305-b. That is, in a case that the AMF 305-a is not associated with the relay UE 115-e and the AMF 305-a does not forward the paging request to the AMF 305-b at 330, the AMF 305-b (e.g., associated with the relay UE 115-e) may transfer the context information associated with the relay UE 115-e to the AMF 305-a.
  • the AMF 305-a may transmit one or more paging messages to the target base station 105-c in response to receiving the paging request from the base station 105-c.
  • the target base station 105-c may forward the one or more paging messages to the relay UE 115-e.
  • the target base station 105-c may forward the one or more paging messages received from the AMF 305-a (e.g., at 345) or from the AMF 305-b (e.g., at 335) .
  • the one or more paging messages may be transmitted via core network paging.
  • the relay UE 115-e and the target base station 105-c may perform an RRC establishment procedure (e.g., a connection establishment procedure) based on the relay UE 115-e receiving the one or more paging messages.
  • the relay UE 115-e may enter into a connected state (e.g., from an idle state) based on performing the RRC establishment procedure.
  • the source base station 105-b and the target base station 105-c may prepare for the handover.
  • the source and/or target base stations 105 may generate a handover command for the remote UE 115-d based on the RRC establishment procedure.
  • the source and/or target base stations 105 may configure a relay bearer mapping (e.g., a PC5-to-Uu bearer mapping) associated with the relay pairing based on generating the handover command.
  • the base stations 105 may prepare for the handover prior to performing the RRC establishment procedure with the relay UE 115-e.
  • the target base station 105-c may perform an RRC reconfiguration procedure with the relay UE 115-e based on the target base station 105-c preparing for the handover. For example, the target base station 105-c may transmit an RRC reconfiguration message to the relay UE 115-e including the relay bearer mapping (e.g., configured at 360) .
  • the relay bearer mapping e.g., configured at 360
  • the source base station 105-b may perform an RRC reconfiguration procedure with the remote UE 115-d and indicate the handover command (e.g., generated at 360) .
  • the source base station 105-b may transmit an RRC reconfiguration message to the remote UE 115-d including the Uu signaling radio bearer and dedicated radio bearer.
  • the RRC reconfiguration message may indicate a configuration for the sidelink RLC channel (e.g., the PC5 RLC channel) .
  • the remote UE 115-d and the relay UE 115-e may establish (e.g., setup and configure) the sidelink channel (e.g., the PC5 channel) based on the RRC reconfiguration messages and the handover command.
  • the sidelink channel e.g., the PC5 channel
  • the remote UE 115-d may transmit an RRC reconfiguration complete message to the target base station 105-c using a target configuration provided in the RRC reconfiguration and based on establishing the sidelink channel between the remote UE 115-d and the relay UE 115-e. For example, at 380 the remote UE 115-d may transmit the RRC reconfiguration complete message to the relay UE 115-e and at 385, the relay UE 115-e may forward the RRC reconfiguration complete message to the target base station 105-d.
  • the target base station 105-c may maintain identifiers (e.g., L2 identifiers) for the relay UE 115-e and the remote UE 115-d (e.g., based on receiving the RRC reconfiguration complete message from the remote UE 115-d via the relay UE 115-e) .
  • identifiers e.g., L2 identifiers
  • the remote UE 115-d may optionally communicate with the target base station 105-c via the relay UE 115-e.
  • the remote UE 115-d may transmit uplink data to the target base station 105-c via the relay UE 115-e.
  • the base station 105-c may transmit downlink data to the remote UE 115-d via the relay UE 115-e.
  • FIG. 4 illustrates an example of a process flow 400 in a system that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the process flow 400 includes UEs 115-f and 115-g and base stations 105-d and 105-e, which may be examples of the corresponding devices described with reference to FIGs. 1–2.
  • the process flow 400 may additionally include an anchor base station 405 associated with the relay UE 115-g.
  • the source base station 105-d and the target base station 105-e may be the same base station 105.
  • Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.
  • the process flow 400 may illustrate an example of a backward handover procedure (e.g., initiated by a base station 105) to switch the remote UE 115-f from communicating directly with the base station 105-d to communicating with the base station 105-e via the relay UE 115-g in a case that the relay UE 115-g is in an inactive state (e.g., RRC_INACTIVE) .
  • a backward handover procedure e.g., initiated by a base station 105
  • switch the remote UE 115-f from communicating directly with the base station 105-d to communicating with the base station 105-e via the relay UE 115-g in a case that the relay UE 115-g is in an inactive state (e.g., RRC_INACTIVE) .
  • the remote UE 115-f may communicate directly with the base station 105-d (e.g., a source base station 105-d) .
  • the remote UE 115-f may transmit uplink data to the base station 105-d and the base station 105-d may transmit downlink data to the remote UE 115-f.
  • the remote UE 115-f may transmit a measurement report (e.g., a mobility trigger) to the base station 105-d.
  • the measurement report may include an indication of the connection state of the relay UE 115-g (e.g., an RRC state of the relay UE 115-g) , an identifier of the relay UE 115-g, a cell identifier of the relay UE 115-g, or any combination thereof.
  • the identifier of the relay UE 115-g may include a TMSI, such as a 5G-S-TMSI, or a hashed version of the 5G-S-TMSI, or the like.
  • the source base station 105-d and the target base station 105-e may make a handover decision.
  • the base stations 105-d and 105-e may determine to handover the remote UE 115-f from communicating directly with the source base station 105-d to communicating with the target base station 105-e via the relay UE 115-g.
  • the source base station 105-d and the target base station 105-e may be the same.
  • the handover decision may relate to switching the remote UE 115-f from communicating directly with the base station 105 to communicating with the base station 105 via the relay UE 115-g.
  • the base station 105-e may identify a relay pairing between the remote UE 115-f and the relay UE 115-g.
  • the target base station 105-e may optionally transmit, to the anchor base station 405, a request to page the relay UE 115-g based on the connection state of the relay UE 115-g.
  • the measurement report (e.g., transmitted by the remote UE 115-f at 415) may indicate that the relay UE 115-g is in an inactive state.
  • the target base station 105-e may transmit the page request to the anchor base station 405 that is associated with the relay UE 115-g.
  • the page request may indicate a paging cause including a relay path switch (e.g., including the relay UE 115-g) .
  • the anchor base station 405 may transmit one or more paging messages to the relay UE 115-g in response to receiving the page request.
  • the one or more paging messages may be transmitted via radio access network (RAN) paging.
  • RAN radio access network
  • the base station 105-e may optionally receive context information for the relay UE 115-g from the anchor base station 405 That is, in a case that the base station 105-e is not the anchor base station 405 for the relay UE 115-g, the anchor base station 405 may transfer the context information associated with the relay UE 115-g to the target base station 105-e.
  • the base station 105-e may transmit one or more paging messages to the relay UE 115-g in response to receiving the context information associated with the relay UE 115-g from the anchor base station 405. In some cases, the one or more paging messages may be transmitted via RAN paging.
  • the relay UE 115-g and the target base station 105-e may perform an RRC resumption procedure (e.g., a connection resumption procedure or resuming a previously-established connection) based on the relay UE 115-g receiving the one or more paging messages.
  • the relay UE 115-g may enter into a connected state (e.g., from an inactive state) based on performing the RRC resumption procedure.
  • the source base station 105-d and the target base station 105-e may prepare for the handover.
  • the source and/or target base stations 105 may generate a handover command for the remote UE 115-f based on the RRC resumption procedure.
  • the source and/or target base stations 105 may configure a relay bearer mapping (e.g., a PC5-to-Uu bearer mapping) associated with the relay pairing based on generating the handover command.
  • the base stations 105 may prepare for the handover prior to performing the RRC resumption procedure with the relay UE 115-g.
  • the base stations 105 may prepare for the handover prior to transmitting the one or more paging messages at 440 (e.g., in a case that the base station 105-e receives the context information associated with the relay UE 115-g from the anchor base station 405 at 435) .
  • the target base station 105-e may perform an RRC reconfiguration procedure with the relay UE 115-g based on the target base station 105-e preparing for the handover. For example, the target base station 105-e may transmit an RRC reconfiguration message to the relay UE 115-g including the relay bearer mapping (e.g., configured at 450) .
  • the relay bearer mapping e.g., configured at 450
  • the source base station 105-d may perform an RRC reconfiguration procedure with the remote UE 115-f and indicate the handover command (e.g., generated at 450) .
  • the source base station 105-d may transmit an RRC reconfiguration message to the remote UE 115-f including the Uu signaling radio bearer and dedicated radio bearer.
  • the RRC reconfiguration message may indicate a configuration for the sidelink RLC channel (e.g., the PC5 RLC channel) .
  • the remote UE 115-f and the relay UE 115-g may establish (e.g., setup and configure) the sidelink channel (e.g., the PC5 channel) based on the RRC reconfiguration messages and the handover command.
  • the sidelink channel e.g., the PC5 channel
  • the remote UE 115-f may transmit an RRC reconfiguration complete message to the target base station 105-e using a target configuration provided in the RRC reconfiguration and based on establishing the sidelink channel between the remote UE 115-f and the relay UE 115-g. For example, at 470 the remote UE 115-f may transmit the RRC reconfiguration complete message to the relay UE 115-g and at 475, the relay UE 115-g may forward the RRC reconfiguration complete message to the target base station 105-d.
  • the target base station 105-e may maintain identifiers (e.g., L2 identifiers) for the relay UE 115-g and the remote UE 115-f (e.g., based on receiving the RRC reconfiguration complete message from the remote UE 115-f via the relay UE 115-g) .
  • identifiers e.g., L2 identifiers
  • the remote UE 115-f may optionally communicate with the target base station 105-e via the relay UE 115-g. For example, the remote UE 115-f may transmit uplink data to the target base station 105-e via the relay UE 115-g. Additionally, the base station 105-e may transmit downlink data to the remote UE 115-f via the relay UE 115-g.
  • FIG. 5 shows a block diagram 500 of a device 505 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the device 505 may be an example of aspects of a base station 105 as described herein.
  • the device 505 may include a receiver 510, a transmitter 515, and a communications manager 520.
  • the device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) . Information may be passed on to other components of the device 505.
  • the receiver 510 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 515 may provide a means for transmitting signals generated by other components of the device 505.
  • the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) .
  • the transmitter 515 may be co-located with a receiver 510 in a transceiver module.
  • the transmitter 515 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of backward handover procedures for L2 relay mobility as described herein.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a DSP, an ASIC, a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure)
  • the communications manager 520 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both.
  • the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 520 may support wireless communication at a base station in accordance with examples as disclosed herein.
  • the communications manager 520 may be configured as or otherwise support a means for identifying a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates.
  • the communications manager 520 may be configured as or otherwise support a means for identifying a connection state of the relay UE based on a measurement report from the UE.
  • the communications manager 520 may be configured as or otherwise support a means for performing a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE.
  • the device 505 e.g., a processor controlling or otherwise coupled to the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof
  • the device 505 may support techniques for determining context information associated with a relay UE while maintaining a continuity of service (e.g., to a remote UE) .
  • FIG. 6 shows a block diagram 600 of a device 605 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the device 605 may be an example of aspects of a device 505 or a base station 105 as described herein.
  • the device 605 may include a receiver 610, a transmitter 615, and a communications manager 620.
  • the device 605 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) . Information may be passed on to other components of the device 605.
  • the receiver 610 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 615 may provide a means for transmitting signals generated by other components of the device 605.
  • the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) .
  • the transmitter 615 may be co-located with a receiver 610 in a transceiver module.
  • the transmitter 615 may utilize a single antenna or a set of multiple antennas.
  • the device 605, or various components thereof may be an example of means for performing various aspects of backward handover procedures for L2 relay mobility as described herein.
  • the communications manager 620 may include a relay manager 625, a connection state manager 630, a connection procedure component 635, or any combination thereof.
  • the communications manager 620 may be an example of aspects of a communications manager 520 as described herein.
  • the communications manager 620, or various components thereof may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both.
  • the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 620 may support wireless communication at a base station in accordance with examples as disclosed herein.
  • the relay manager 625 may be configured as or otherwise support a means for identifying a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates.
  • the connection state manager 630 may be configured as or otherwise support a means for identifying a connection state of the relay UE based on a measurement report from the UE.
  • the connection procedure component 635 may be configured as or otherwise support a means for performing a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE.
  • FIG. 7 shows a block diagram 700 of a communications manager 720 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein.
  • the communications manager 720, or various components thereof, may be an example of means for performing various aspects of backward handover procedures for L2 relay mobility as described herein.
  • the communications manager 720 may include a relay manager 725, a connection state manager 730, a connection procedure component 735, a paging manager 740, a handover component 745, a bearer manager 750, a context manager 755, or any combination thereof.
  • Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the communications manager 720 may support wireless communication at a base station in accordance with examples as disclosed herein.
  • the relay manager 725 may be configured as or otherwise support a means for identifying a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates.
  • the connection state manager 730 may be configured as or otherwise support a means for identifying a connection state of the relay UE based on a measurement report from the UE.
  • the connection procedure component 735 may be configured as or otherwise support a means for performing a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE.
  • the paging manager 740 may be configured as or otherwise support a means for transmitting, to a network node, a request to page the relay UE based on the connection state of the relay UE, where the one or more paging messages are transmitted to the relay UE in response to the request to page the relay UE.
  • connection state manager 730 may be configured as or otherwise support a means for identifying that the relay UE is in an idle state based on the measurement report, where the network node includes an AMF associated with the base station.
  • connection state manager 730 may be configured as or otherwise support a means for identifying that the relay UE is in an inactive state based on the measurement report, where the network node includes an anchor base station associated with the relay UE.
  • the request to page the relay UE indicates a paging cause including a relay path switch.
  • the paging manager 740 may be configured as or otherwise support a means for transmitting, to the relay UE, the one or more paging messages from the network node based on a request to page the relay UE, the one or more paging messages transmitted via core network paging, where the network node includes an AMF associated with the relay UE.
  • the paging manager 740 may be configured as or otherwise support a means for transmitting, to the relay UE, the one or more paging messages from the network node based on a request to page the relay UE, the one or more paging messages transmitted via core network paging, where the network node includes an AMF associated with the base station.
  • the paging manager 740 may be configured as or otherwise support a means for transmitting, to the relay UE, the one or more paging messages based on the connection state of the relay UE, where the one or more paging messages are transmitted via RAN paging.
  • the context manager 755 may be configured as or otherwise support a means for transmitting, to an anchor base station associated with the relay UE, a request for context information for the relay UE. In some examples, the context manager 755 may be configured as or otherwise support a means for receiving, from the anchor base station and in response to the request for the context information, an indication of the context information for the relay UE, where transmitting the one or more paging messages is based on the context information for the relay UE.
  • the relay manager 725 may be configured as or otherwise support a means for receiving the measurement report from the UE, where the measurement report includes an indication of the connection state of the relay UE, an identifier of the relay UE, a cell identifier of the relay UE, or any combination thereof, where the relay pairing is based on the measurement report.
  • the handover component 745 may be configured as or otherwise support a means for generating a handover command for the UE based on the connection establishment procedure establishing a connection between the relay UE and the base station.
  • the bearer manager 750 may be configured as or otherwise support a means for configuring a relay bearer mapping associated with the relay pairing based on generating the handover command.
  • the handover component 745 may be configured as or otherwise support a means for transmitting a reconfiguration message to the relay UE, the reconfiguration message including an indication of the configured relay bearer mapping.
  • the context manager 755 may be configured as or otherwise support a means for identifying context information for the relay UE based on the one or more paging messages transmitted to the relay UE, where generating the handover command and configuring the relay bearer mapping is based on the identified context information for the relay UE.
  • the handover component 745 may be configured as or otherwise support a means for transmitting, to the UE, a handover command based on the relay pairing between the UE and the relay UE, where the handover command includes a radio link control configuration of a sidelink channel between the UE and the relay UE.
  • FIG. 8 shows a diagram of a system 800 including a device 805 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the device 805 may be an example of or include the components of a device 505, a device 605, or a base station 105 as described herein.
  • the device 805 may communicate wirelessly with one or more base stations 105, UEs 115, or any combination thereof.
  • the device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, a network communications manager 810, a transceiver 815, an antenna 825, a memory 830, code 835, a processor 840, and an inter-station communications manager 845.
  • These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 850) .
  • the network communications manager 810 may manage communications with a core network 130 (e.g., via one or more wired backhaul links) .
  • the network communications manager 810 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the device 805 may include a single antenna 825. However, in some other cases the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 815 may communicate bi-directionally, via the one or more antennas 825, wired, or wireless links as described herein.
  • the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825.
  • the transceiver 815 may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.
  • the memory 830 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform various functions described herein.
  • the code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 835 may not be directly executable by the processor 840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 830 may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 840 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 840.
  • the processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting backward handover procedures for L2 relay mobility) .
  • the device 805 or a component of the device 805 may include a processor 840 and memory 830 coupled to the processor 840, the processor 840 and memory 830 configured to perform various functions described herein.
  • the inter-station communications manager 845 may manage communications with other base stations 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. For example, the inter-station communications manager 845 may coordinate scheduling for transmissions to UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communications manager 845 may provide an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between base stations 105.
  • the communications manager 820 may support wireless communication at a base station in accordance with examples as disclosed herein.
  • the communications manager 820 may be configured as or otherwise support a means for identifying a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates.
  • the communications manager 820 may be configured as or otherwise support a means for identifying a connection state of the relay UE based on a measurement report from the UE.
  • the communications manager 820 may be configured as or otherwise support a means for performing a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE.
  • the device 805 may support techniques for improved coordination between devices by improving a continuity of service between a base station and a remote UE.
  • the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof.
  • the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the processor 840, the memory 830, the code 835, or any combination thereof.
  • the code 835 may include instructions executable by the processor 840 to cause the device 805 to perform various aspects of backward handover procedures for L2 relay mobility as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.
  • FIG. 9 shows a block diagram 900 of a device 905 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the device 905 may be an example of aspects of a UE 115 as described herein.
  • the device 905 may include a receiver 910, a transmitter 915, and a communications manager 920.
  • the device 905 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 910 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) . Information may be passed on to other components of the device 905.
  • the receiver 910 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 915 may provide a means for transmitting signals generated by other components of the device 905.
  • the transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) .
  • the transmitter 915 may be co-located with a receiver 910 in a transceiver module.
  • the transmitter 915 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of backward handover procedures for L2 relay mobility as described herein.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , an FPGA or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU) , an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU) , an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting
  • the communications manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both.
  • the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 920 may support wireless communication at a relay UE in accordance with examples as disclosed herein.
  • the communications manager 920 may be configured as or otherwise support a means for receiving one or more paging messages associated with modifying a relay path to include the relay UE.
  • the communications manager 920 may be configured as or otherwise support a means for transmitting, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based on a connection state of the relay UE, where the message is transmitted in response to receiving the one or more paging message.
  • the communications manager 920 may be configured as or otherwise support a means for receiving a reconfiguration message including a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • the device 905 e.g., a processor controlling or otherwise coupled to the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof
  • the device 905 may support techniques for maintaining a continuity of service while performing a backward handover procedure.
  • FIG. 10 shows a block diagram 1000 of a device 1005 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the device 1005 may be an example of aspects of a device 905 or a UE 115 as described herein.
  • the device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020.
  • the device 1005 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1010 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) . Information may be passed on to other components of the device 1005.
  • the receiver 1010 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005.
  • the transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) .
  • the transmitter 1015 may be co-located with a receiver 1010 in a transceiver module.
  • the transmitter 1015 may utilize a single antenna or a set of multiple antennas.
  • the device 1005, or various components thereof, may be an example of means for performing various aspects of backward handover procedures for L2 relay mobility as described herein.
  • the communications manager 1020 may include a paging receiver 1025 a connection manager 1030, or any combination thereof.
  • the communications manager 1020 may be an example of aspects of a communications manager 920 as described herein.
  • the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both.
  • the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 1020 may support wireless communication at a relay UE in accordance with examples as disclosed herein.
  • the paging receiver 1025 may be configured as or otherwise support a means for receiving one or more paging messages associated with modifying a relay path to include the relay UE.
  • the connection manager 1030 may be configured as or otherwise support a means for transmitting, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based on a connection state of the relay UE, where the message is transmitted in response to receiving the one or more paging message.
  • the connection manager 1030 may be configured as or otherwise support a means for receiving a reconfiguration message including a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein.
  • the communications manager 1120, or various components thereof may be an example of means for performing various aspects of backward handover procedures for L2 relay mobility as described herein.
  • the communications manager 1120 may include a paging receiver 1125, a connection manager 1130, a CN paging component 1135, a RAN paging component 1140, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the communications manager 1120 may support wireless communication at a relay UE in accordance with examples as disclosed herein.
  • the paging receiver 1125 may be configured as or otherwise support a means for receiving one or more paging messages associated with modifying a relay path to include the relay UE.
  • the connection manager 1130 may be configured as or otherwise support a means for transmitting, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based on a connection state of the relay UE, where the message is transmitted in response to receiving the one or more paging message.
  • the connection manager 1130 may be configured as or otherwise support a means for receiving a reconfiguration message including a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • the CN paging component 1135 may be configured as or otherwise support a means for receiving the one or more paging messages via core network paging, where the one or more paging messages are from an AMF associated with the relay UE.
  • the CN paging component 1135 may be configured as or otherwise support a means for receiving the one or more paging messages via core network paging, where the one or more paging messages are from an AMF associated with the base station.
  • the RAN paging component 1140 may be configured as or otherwise support a means for receiving the one or more paging messages via RAN paging, where the one or more paging messages are from an anchor base station associated with the relay UE.
  • the RAN paging component 1140 may be configured as or otherwise support a means for receiving the one or more paging messages via RAN paging, where the one or more paging messages are from the base station, the base station being different from an anchor base station associated with the relay UE.
  • connection state of the relay UE includes an idle state or an inactive state.
  • FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the device 1205 may be an example of or include the components of a device 905, a device 1005, or a UE 115 as described herein.
  • the device 1205 may communicate wirelessly with one or more base stations 105, UEs 115, or any combination thereof.
  • the device 1205 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1220, an input/output (I/O) controller 1210, a transceiver 1215, an antenna 1225, a memory 1230, code 1235, and a processor 1240.
  • These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245) .
  • the I/O controller 1210 may manage input and output signals for the device 1205.
  • the I/O controller 1210 may also manage peripherals not integrated into the device 1205.
  • the I/O controller 1210 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1210 may utilize an operating system such as or another known operating system.
  • the I/O controller 1210 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1210 may be implemented as part of a processor, such as the processor 1240.
  • a user may interact with the device 1205 via the I/O controller 1210 or via hardware components controlled by the I/O controller 1210.
  • the device 1205 may include a single antenna 1225. However, in some other cases, the device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 1215 may communicate bi-directionally, via the one or more antennas 1225, wired, or wireless links as described herein.
  • the transceiver 1215 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1215 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1225 for transmission, and to demodulate packets received from the one or more antennas 1225.
  • the transceiver 1215 may be an example of a transmitter 915, a transmitter 1015, a receiver 910, a receiver 1010, or any combination thereof or component thereof, as described herein.
  • the memory 1230 may include RAM and ROM.
  • the memory 1230 may store computer-readable, computer-executable code 1235 including instructions that, when executed by the processor 1240, cause the device 1205 to perform various functions described herein.
  • the code 1235 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 1235 may not be directly executable by the processor 1240 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1230 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the processor 1240 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 1240 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1240.
  • the processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1230) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting backward handover procedures for L2 relay mobility) .
  • the device 1205 or a component of the device 1205 may include a processor 1240 and memory 1230 coupled to the processor 1240, the processor 1240 and memory 1230 configured to perform various functions described herein.
  • the communications manager 1220 may support wireless communication at a relay UE in accordance with examples as disclosed herein.
  • the communications manager 1220 may be configured as or otherwise support a means for receiving one or more paging messages associated with modifying a relay path to include the relay UE.
  • the communications manager 1220 may be configured as or otherwise support a means for transmitting, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based on a connection state of the relay UE, where the message is transmitted in response to receiving the one or more paging message.
  • the communications manager 1220 may be configured as or otherwise support a means for receiving a reconfiguration message including a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • the device 1205 may support techniques for improved coordination between devices.
  • the communications manager 1220 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1215, the one or more antennas 1225, or any combination thereof.
  • the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the processor 1240, the memory 1230, the code 1235, or any combination thereof.
  • the code 1235 may include instructions executable by the processor 1240 to cause the device 1205 to perform various aspects of backward handover procedures for L2 relay mobility as described herein, or the processor 1240 and the memory 1230 may be otherwise configured to perform or support such operations.
  • FIG. 13 shows a block diagram 1300 of a device 1305 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the device 1305 may be an example of aspects of a network node as described herein.
  • the device 1305 may be an example of a base station 105, or an AMF (e.g., an AMF associated with a base station, an AMF associated with a relay UE) , or another network node or network entity.
  • the device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320.
  • the device 1305 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1310 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) . Information may be passed on to other components of the device 1305.
  • the receiver 1310 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 1315 may provide a means for transmitting signals generated by other components of the device 1305.
  • the transmitter 1315 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) .
  • the transmitter 1315 may be co-located with a receiver 1310 in a transceiver module.
  • the transmitter 1315 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations thereof or various components thereof may be examples of means for performing various aspects of backward handover procedures for L2 relay mobility as described herein.
  • the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
  • the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure)
  • the communications manager 1320 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 1310, the transmitter 1315, or both.
  • the communications manager 1320 may receive information from the receiver 1310, send information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 1320 may support wireless communications at a first network node in accordance with examples as disclosed herein.
  • the communications manager 1320 may be configured as or otherwise support a means for receiving, from a second network node, a request to page a relay UE based on modifying a relay path to include the relay UE, where the request to page the relay UE indicates a paging cause including a relay path switch.
  • the communications manager 1320 may be configured as or otherwise support a means for transmitting, to the relay UE, one or more paging messages in response to the request to page the relay UE.
  • the device 1305 may support techniques for enabling a base station to determine information associated with a relay UE while maintaining a continuity of service (e.g., to a remote UE) .
  • FIG. 14 shows a block diagram 1400 of a device 1405 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the device 1405 may be an example of aspects of a device 1305 or a network node as described herein.
  • the device 1405 may include a receiver 1410, a transmitter 1415, and a communications manager 1420.
  • the device 1405 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1410 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) . Information may be passed on to other components of the device 1405.
  • the receiver 1410 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 1415 may provide a means for transmitting signals generated by other components of the device 1405.
  • the transmitter 1415 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to backward handover procedures for L2 relay mobility) .
  • the transmitter 1415 may be co-located with a receiver 1410 in a transceiver module.
  • the transmitter 1415 may utilize a single antenna or a set of multiple antennas.
  • the device 1405, or various components thereof may be an example of means for performing various aspects of backward handover procedures for L2 relay mobility as described herein.
  • the communications manager 1420 may include a paging request manager 1425 a paging message component 1430, or any combination thereof.
  • the communications manager 1420 may be an example of aspects of a communications manager 1320 as described herein.
  • the communications manager 1420, or various components thereof may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 1410, the transmitter 1415, or both.
  • the communications manager 1420 may receive information from the receiver 1410, send information to the transmitter 1415, or be integrated in combination with the receiver 1410, the transmitter 1415, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 1420 may support wireless communications at a first network node in accordance with examples as disclosed herein.
  • the paging request manager 1425 may be configured as or otherwise support a means for receiving, from a second network node, a request to page a relay UE based on modifying a relay path to include the relay UE, where the request to page the relay UE indicates a paging cause including a relay path switch.
  • the paging message component 1430 may be configured as or otherwise support a means for transmitting, to the relay UE, one or more paging messages in response to the request to page the relay UE.
  • FIG. 15 shows a block diagram 1500 of a communications manager 1520 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the communications manager 1520 may be an example of aspects of a communications manager 1320, a communications manager 1420, or both, as described herein.
  • the communications manager 1520, or various components thereof may be an example of means for performing various aspects of backward handover procedures for L2 relay mobility as described herein.
  • the communications manager 1520 may include a paging request manager 1525, a paging message component 1530, a context information component 1535, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the communications manager 1520 may support wireless communications at a first network node in accordance with examples as disclosed herein.
  • the paging request manager 1525 may be configured as or otherwise support a means for receiving, from a second network node, a request to page a relay UE based on modifying a relay path to include the relay UE, where the request to page the relay UE indicates a paging cause including a relay path switch.
  • the paging message component 1530 may be configured as or otherwise support a means for transmitting, to the relay UE, one or more paging messages in response to the request to page the relay UE.
  • the paging message component 1530 may be configured as or otherwise support a means for transmitting the one or more paging messages via core network paging, where the first network node includes a first AMF associated with the relay UE, and where the second network node includes second AMF associated with a base station.
  • the paging message component 1530 may be configured as or otherwise support a means for transmitting the one or more paging messages via core network paging, where the first network node includes an AMF associated with a base station, and where the second network node includes the base station.
  • the context information component 1535 may be configured as or otherwise support a means for transmitting, to a second a second AMF associated with the relay UE, a request for context information for the relay UE, where the request for the context information is based on receiving the request to page the relay UE. In some examples, the context information component 1535 may be configured as or otherwise support a means for receiving, from the second AMF, the context information for the relay UE based on the request for the context information.
  • the paging message component 1530 may be configured as or otherwise support a means for transmitting the one or more paging messages via core network paging, where the first network node includes an anchor base station associated with the relay UE, and where the second network node includes a base station different from the anchor base station.
  • FIG. 16 shows a diagram of a system 1600 including a device 1605 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the device 1605 may be an example of or include the components of a device 1305, a device 1405, or a network node as described herein.
  • the device 1605 may be an example of a base station 105, or an AMF (e.g., an AMF associated with a base station, an AMF associated with a relay UE) , or another network node or network entity.
  • AMF e.g., an AMF associated with a base station, an AMF associated with a relay UE
  • the device 1605 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1620, an I/O controller 1610, a transceiver 1625, an antenna 1630, a memory 1635, code 1640, a processor 1645.
  • the device 1605 may further include an inter-station communications manager (such as an inter-station communications manager 845 described with reference to FIG. 8) .
  • the device 1605 may include a network communications manager. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1650) .
  • the I/O controller 1610 may manage input and output signals for the device 1605.
  • the I/O controller 1610 may also manage peripherals not integrated into the device 1605.
  • the I/O controller 1610 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1610 may utilize an operating system such as or another known operating system.
  • the I/O controller 1610 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1610 may be implemented as part of a processor, such as the processor 1645.
  • a user may interact with the device 1605 via the I/O controller 1610 or via hardware components controlled by the I/O controller 1610.
  • the device 1605 may include a single antenna 1630. However, in some other cases, the device 1605 may have more than one antenna 1630, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 1625 may communicate bi-directionally, via the one or more antennas 1630, wired, or wireless links as described herein.
  • the transceiver 1625 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1625 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1630 for transmission, and to demodulate packets received from the one or more antennas 1630.
  • the transceiver 1625 may be an example of a transmitter 1315, a transmitter 1415, a receiver 1310, a receiver 1410, or any combination thereof or component thereof, as described herein.
  • the memory 1635 may include RAM and ROM.
  • the memory 1635 may store computer-readable, computer-executable code 1640 including instructions that, when executed by the processor 1645, cause the device 1605 to perform various functions described herein.
  • the code 1640 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 1640 may not be directly executable by the processor 1645 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1635 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the processor 1645 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 1645 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1645.
  • the processor 1645 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1635) to cause the device 1605 to perform various functions (e.g., functions or tasks supporting backward handover procedures for L2 relay mobility) .
  • the device 1605 or a component of the device 1605 may include a processor 1645 and memory 1635 coupled to the processor 1645, the processor 1645 and memory 1635 configured to perform various functions described herein.
  • the inter-station communications manager may manage communications with other base stations 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. For example, the inter-station communications manager may coordinate scheduling for transmissions to UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communications manager may provide an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between base stations 105. The network communications manager may manage communications with a core network 130 (e.g., via one or more wired backhaul links) . For example, the network communications manager may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the communications manager 1620 may support wireless communications at a first network node in accordance with examples as disclosed herein.
  • the communications manager 1620 may be configured as or otherwise support a means for receiving, from a second network node, a request to page a relay UE based on modifying a relay path to include the relay UE, where the request to page the relay UE indicates a paging cause including a relay path switch.
  • the communications manager 1620 may be configured as or otherwise support a means for transmitting, to the relay UE, one or more paging messages in response to the request to page the relay UE.
  • the device 1605 may support techniques for improved coordination between devices.
  • the communications manager 1620 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1625, the one or more antennas 1630, or any combination thereof.
  • the communications manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1620 may be supported by or performed by the processor 1645, the memory 1635, the code 1640, or any combination thereof.
  • the code 1640 may include instructions executable by the processor 1645 to cause the device 1605 to perform various aspects of backward handover procedures for L2 relay mobility as described herein, or the processor 1645 and the memory 1635 may be otherwise configured to perform or support such operations.
  • FIG. 17 shows a flowchart illustrating a method 1700 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the operations of the method 1700 may be implemented by a base station or its components as described herein.
  • the operations of the method 1700 may be performed by a base station 105 as described with reference to FIGs. 1 through 8.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may perform aspects of the described functions using special-purpose hardware.
  • the method may include identifying a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates.
  • the operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a relay manager 725 as described with reference to FIG. 7.
  • the method may include identifying a connection state of the relay UE based on a measurement report from the UE.
  • the operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a connection state manager 730 as described with reference to FIG. 7.
  • the method may include performing a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE.
  • the operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a connection procedure component 735 as described with reference to FIG. 7.
  • FIG. 18 shows a flowchart illustrating a method 1800 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the operations of the method 1800 may be implemented by a base station or its components as described herein.
  • the operations of the method 1800 may be performed by a base station 105 as described with reference to FIGs. 1 through 8.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may perform aspects of the described functions using special-purpose hardware.
  • the method may include identifying a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates.
  • the operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a relay manager 725 as described with reference to FIG. 7.
  • the method may include identifying a connection state of the relay UE based on a measurement report from the UE.
  • the operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by a connection state manager 730 as described with reference to FIG. 7.
  • the method may include transmitting, to a network node, a request to page the relay UE based on the connection state of the relay UE.
  • the operations of 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a paging manager 740 as described with reference to FIG. 7.
  • the method may include performing a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE, where the one or more paging messages are transmitted to the relay UE in response to the request to page the relay UE.
  • the operations of 1820 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed by a connection procedure component 735 as described with reference to FIG. 7.
  • FIG. 19 shows a flowchart illustrating a method 1900 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the operations of the method 1900 may be implemented by a base station or its components as described herein.
  • the operations of the method 1900 may be performed by a base station 105 as described with reference to FIGs. 1 through 8.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may perform aspects of the described functions using special-purpose hardware.
  • the method may include identifying a relay pairing between a UE and a relay UE, where the relay UE is from a set of one or more relay UE candidates.
  • the operations of 1905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by a relay manager 725 as described with reference to FIG. 7.
  • the method may include identifying a connection state of the relay UE based on a measurement report from the UE.
  • the operations of 1910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by a connection state manager 730 as described with reference to FIG. 7.
  • the method may include transmitting, to a network node, a request to page the relay UE based on the connection state of the relay UE.
  • the operations of 1915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed by a paging manager 740 as described with reference to FIG. 7.
  • the method may include transmitting, to the relay UE, the one or more paging messages from the network node based on the request to page the relay UE, the one or more paging messages transmitted via core network paging, where the network node includes an AMF associated with the relay UE.
  • the one or more paging messages are transmitted to the relay UE in response to the request to page the relay UE.
  • the operations of 1920 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed by a paging manager 740 as described with reference to FIG. 7.
  • the method may include performing a connection establishment procedure or a connection resumption procedure with the relay UE based on one or more paging messages transmitted to the relay UE.
  • the operations of 1925 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1925 may be performed by a connection procedure component 735 as described with reference to FIG. 7.
  • FIG. 20 shows a flowchart illustrating a method 2000 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the operations of the method 2000 may be implemented by a UE or its components as described herein.
  • the operations of the method 2000 may be performed by a UE 115 as described with reference to FIGs. 1 through 4 and 9 through 12.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving one or more paging messages associated with modifying a relay path to include the relay UE.
  • the operations of 2005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed by a paging receiver 1125 as described with reference to FIG. 11.
  • the method may include transmitting, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based on a connection state of the relay UE, where the message is transmitted in response to receiving the one or more paging message.
  • the operations of 2010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by a connection manager 1130 as described with reference to FIG. 11.
  • the method may include receiving a reconfiguration message including a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • the operations of 2015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed by a connection manager 1130 as described with reference to FIG. 11.
  • FIG. 21 shows a flowchart illustrating a method 2100 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the operations of the method 2100 may be implemented by a UE (e.g., a relay UE) or its components as described herein.
  • the operations of the method 2100 may be performed by a UE 115 as described with reference to FIGs. 1 through 4 and 9 through 12.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving one or more paging messages associated with modifying a relay path to include the relay UE.
  • the method may include receiving the one or more paging messages via CN paging, where the one or more paging messages are from an AMF associated with the relay UE.
  • the operations of 2105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed by a paging receiver 1125 as described with reference to FIG. 11.
  • the method may include receiving the one or more paging messages via CN paging, where the one or more paging messages are from an AMF associated with a base station.
  • the operations of 2115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed by a CN paging component 1135 as described with reference to FIG. 11.
  • the method may include transmitting, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based on a connection state of the relay UE, where the message is transmitted in response to receiving the one or more paging message.
  • the operations of 2115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed by a connection manager 1130 as described with reference to FIG. 11.
  • the method may include receiving a reconfiguration message including a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • the operations of 2120 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed by a connection manager 1130 as described with reference to FIG. 11.
  • FIG. 22 shows a flowchart illustrating a method 2200 that supports backward handover procedures for L2 relay mobility in accordance with aspects of the present disclosure.
  • the operations of the method 2200 may be implemented by a network node (e.g., a first network node, such as a base station, an AMF, a network entity, or the like) or its components as described herein.
  • a network node e.g., a first network node, such as a base station, an AMF, a network entity, or the like
  • the operations of the method 2200 may be performed by a network node as described with reference to FIGs. 1 through 4 and 13 through 16.
  • a network node may execute a set of instructions to control the functional elements of the network node to perform the described functions. Additionally or alternatively, the network node may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, from a second network node, a request to page a relay UE based on modifying a relay path to include the relay UE, where the request to page the relay UE indicates a paging cause including a relay path switch.
  • the operations of 2205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2205 may be performed by a paging request manager 1525 as described with reference to FIG. 15.
  • the method may include transmitting, to the relay UE, one or more paging messages in response to the request to page the relay UE.
  • the operations of 2210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2210 may be performed by a paging message component 1530 as described with reference to FIG. 15.
  • a method for wireless communication at a base station comprising: identifying a relay pairing between a UE and a relay UE, wherein the relay UE is from a set of one or more relay UE candidates; identifying a connection state of the relay UE based at least in part on a measurement report from the UE; and performing a connection establishment procedure or a connection resumption procedure with the relay UE based at least in part on one or more paging messages transmitted to the relay UE.
  • Aspect 2 The method of aspect 1, further comprising: transmitting, to a network node, a request to page the relay UE based at least in part on the connection state of the relay UE, wherein the one or more paging messages are transmitted to the relay UE in response to the request to page the relay UE.
  • Aspect 3 The method of aspect 2, wherein identifying the connection state of the relay UE comprises: identifying that the relay UE is in an idle state based at least in part on the measurement report, wherein the network node comprises an AMF associated with the base station.
  • Aspect 4 The method of any of aspects 2 through 3, wherein identifying the connection state of the relay UE comprises: identifying that the relay UE is in an inactive state based at least in part on the measurement report, wherein the network node comprises an anchor base station associated with the relay UE.
  • Aspect 5 The method of any of aspects 2 through 4, wherein the request to page the relay UE indicates a paging cause comprising a relay path switch.
  • Aspect 6 The method of any of aspects 2 through 5, further comprising: transmitting, to the relay UE, the one or more paging messages from the network node based at least in part on a request to page the relay UE, the one or more paging messages transmitted via core network paging, wherein the network node comprises an AMF associated with the relay UE.
  • Aspect 7 The method of any of aspects 2 through 6, further comprising: transmitting, to the relay UE, the one or more paging messages from the network node based at least in part on a request to page the relay UE, the one or more paging messages transmitted via core network paging, wherein the network node comprises an AMF associated with the base station.
  • Aspect 8 The method of any of aspects 1 through 7, further comprising: transmitting, to the relay UE, the one or more paging messages based at least in part on the connection state of the relay UE, wherein the one or more paging messages are transmitted via RAN paging.
  • Aspect 9 The method of aspect 8, further comprising: transmitting, to an anchor base station associated with the relay UE, a request for context information for the relay UE; receiving, from the anchor base station and in response to the request for the context information, an indication of the context information for the relay UE, wherein transmitting the one or more paging messages is based at least in part on the context information for the relay UE.
  • Aspect 10 The method of any of aspects 1 through 9, further comprising: receiving the measurement report from the UE, wherein the measurement report comprises an indication of the connection state of the relay UE, an identifier of the relay UE, a cell identifier of the relay UE, or any combination thereof, wherein the relay pairing is based at least in part on the measurement report.
  • Aspect 11 The method of any of aspects 1 through 10, further comprising: generating a handover command for the UE based at least in part on the connection establishment procedure establishing a connection between the relay UE and the base station; configuring a relay bearer mapping associated with the relay pairing based at least in part on generating the handover command; and transmitting a reconfiguration message to the relay UE, the reconfiguration message comprising an indication of the configured relay bearer mapping.
  • Aspect 12 The method of aspect 11, further comprising: identifying context information for the relay UE based at least in part on the one or more paging messages transmitted to the relay UE, wherein generating the handover command and configuring the relay bearer mapping is based at least in part on the identified context information for the relay UE.
  • Aspect 13 The method of any of aspects 1 through 12, further comprising: transmitting, to the UE, a handover command based at least in part on the relay pairing between the UE and the relay UE, wherein the handover command comprises a radio link control configuration of a sidelink channel between the UE and the relay UE.
  • a method for wireless communication at a relay UE comprising: receiving one or more paging messages associated with modifying a relay path to include the relay UE; transmitting, to a base station, a message for establishing or resuming a connection between the relay UE and the base station based at least in part on a connection state of the relay UE, wherein the message is transmitted in response to receiving the one or more paging message; and receiving a reconfiguration message comprising a relay bearer mapping for a relay pairing between the relay UE and a UE.
  • Aspect 15 The method of aspect 14, wherein receiving the one or more paging messages comprises: receiving the one or more paging messages via core network paging, wherein the one or more paging messages are from an AMF associated with the relay UE.
  • Aspect 16 The method of any of aspects 14 through 15, wherein receiving the one or more paging messages comprises: receiving the one or more paging messages via core network paging, wherein the one or more paging messages are from an AMF associated with the base station.
  • Aspect 17 The method of any of aspects 14 through 16, wherein receiving the one or more paging messages comprises: receiving the one or more paging messages via RAN paging, wherein the one or more paging messages are from an anchor base station associated with the relay UE.
  • Aspect 18 The method of any of aspects 14 through 17, wherein receiving the one or more paging messages comprises: receiving the one or more paging messages via RAN paging, wherein the one or more paging messages are from the base station, the base station being different from an anchor base station associated with the relay UE.
  • Aspect 19 The method of any of aspects 14 through 18, wherein the connection state of the relay UE comprises an idle state or an inactive state.
  • a method for wireless communications at a first network node comprising: receiving, from a second network node, a request to page a relay UE based at least in part on modifying a relay path to include the relay UE, wherein the request to page the relay UE indicates a paging cause comprising a relay path switch; and transmitting, to the relay UE, one or more paging messages in response to the request to page the relay UE.
  • Aspect 21 The method of aspect 20, wherein transmitting the one or more paging messages comprises: transmitting the one or more paging messages via core network paging, wherein the first network node comprises a first AMF associated with the relay UE, and wherein the second network node comprises second AMF associated with a base station.
  • Aspect 22 The method of any of aspects 20 through 21, wherein transmitting the one or more paging messages comprises: transmitting the one or more paging messages via core network paging, wherein the first network node comprises an AMF associated with a base station, and wherein the second network node comprises the base station.
  • Aspect 23 The method of aspect 22, further comprising: transmitting, to a second a second AMF associated with the relay UE, a request for context information for the relay UE, wherein the request for the context information is based at least in part on receiving the request to page the relay UE; and receiving, from the second AMF, the context information for the relay UE based at least in part on the request for the context information.
  • Aspect 24 The method of any of aspects 20 through 23, wherein transmitting the one or more paging messages comprises: transmitting the one or more paging messages via core network paging, wherein the first network node comprises an anchor base station associated with the relay UE, and wherein the second network node comprises a base station different from the anchor base station.
  • Aspect 25 An apparatus for wireless communication at a base station, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 13.
  • Aspect 26 An apparatus for wireless communication at a base station, comprising at least one means for performing a method of any of aspects 1 through 13.
  • Aspect 27 A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 13.
  • Aspect 28 An apparatus for wireless communication at a relay UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 14 through 19.
  • Aspect 29 An apparatus for wireless communication at a relay UE, comprising at least one means for performing a method of any of aspects 14 through 19.
  • Aspect 30 A non-transitory computer-readable medium storing code for wireless communication at a relay UE, the code comprising instructions executable by a processor to perform a method of any of aspects 14 through 19.
  • Aspect 31 An apparatus for wireless communications at a first network node, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 20 through 24.
  • Aspect 32 An apparatus for wireless communications at a first network node, comprising at least one means for performing a method of any of aspects 20 through 24.
  • Aspect 33 A non-transitory computer-readable medium storing code for wireless communications at a first network node, the code comprising instructions executable by a processor to perform a method of any of aspects 20 through 24.
  • LTE, LTE-A, LTE-A Pro, or NR may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

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

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs de communication sans fil. Un équipement d'utilisateur (UE) peut communiquer avec une station de base par le biais d'un UE relais. La station de base peut identifier un appariement de relais entre l'UE et un UE relais en sélectionnant l'UE relais à partir d'un ensemble d'UE relais candidats. La station de base peut en outre identifier un état de connexion de l'UE relais sur la base d'un rapport de mesure reçu de l'UE. Dans le cas où la station de base identifie que l'UE relais se trouve dans un état en attente ou dans un état inactif, un message de radiomessagerie peut être transmis à l'UE relais avant que la station de base n'effectue une procédure d'établissement de connexion ou une procédure de reprise de connexion avec l'UE relais. Par exemple, une fonction de gestion d'accès et de mobilité (AMF) ou une station de base d'ancrage associée à l'UE relais peut transmettre le message de radiomessagerie à l'UE relais.
PCT/CN2021/070253 2021-01-05 2021-01-05 Procédures de transfert intercellulaire vers l'arrière pour mobilité de relais l2 WO2022147642A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/070253 WO2022147642A1 (fr) 2021-01-05 2021-01-05 Procédures de transfert intercellulaire vers l'arrière pour mobilité de relais l2
TW110148269A TW202233005A (zh) 2021-01-05 2021-12-22 用於ｌ２中繼移動性的向後切換過程

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/070253 WO2022147642A1 (fr) 2021-01-05 2021-01-05 Procédures de transfert intercellulaire vers l'arrière pour mobilité de relais l2

Publications (1)

Publication Number Publication Date
WO2022147642A1 true WO2022147642A1 (fr) 2022-07-14

Family

ID=82357022

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/070253 WO2022147642A1 (fr) 2021-01-05 2021-01-05 Procédures de transfert intercellulaire vers l'arrière pour mobilité de relais l2

Country Status (1)

Country Link
WO (1) WO2022147642A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4102901A4 (fr) * 2020-03-05 2023-08-02 Huawei Technologies Co., Ltd. Procédé de communication et dispositif associé

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018083381A1 (fr) * 2016-11-04 2018-05-11 Nokia Technologies Oy Amélioration de la mobilité en mode repos pour un équipement utilisateur distant hors couverture
CN111432469A (zh) * 2020-03-05 2020-07-17 华为技术有限公司 一种通信方法及相关装置
WO2020263691A1 (fr) * 2019-06-28 2020-12-30 Qualcomm Incorporated Transition rapide assistée par un équipement utilisateur entre des états rrc

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018083381A1 (fr) * 2016-11-04 2018-05-11 Nokia Technologies Oy Amélioration de la mobilité en mode repos pour un équipement utilisateur distant hors couverture
WO2020263691A1 (fr) * 2019-06-28 2020-12-30 Qualcomm Incorporated Transition rapide assistée par un équipement utilisateur entre des états rrc
CN111432469A (zh) * 2020-03-05 2020-07-17 华为技术有限公司 一种通信方法及相关装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Procedures for remote or relay UE in idle mode", 3GPP DRAFT; R2-167880, vol. RAN WG2, 5 November 2016 (2016-11-05), Reno, Nevada, USA, pages 1 - 7, XP051192853 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4102901A4 (fr) * 2020-03-05 2023-08-02 Huawei Technologies Co., Ltd. Procédé de communication et dispositif associé

Similar Documents

Publication Publication Date Title
WO2021041601A1 (fr) Distribution de services de diffusion à l'aide de différents modes de support de radiodiffusion/multidiffusion
US20210067997A1 (en) Sounding reference signal channel measurement for sidelink communication
WO2022094903A1 (fr) Sélection de relais basée sur une mesure précoce dans un relais l2
WO2021253456A1 (fr) Alignement de durées pour répétitions d'un canal physique partagé lors de transmissions à panneaux multiples
WO2022147642A1 (fr) Procédures de transfert intercellulaire vers l'arrière pour mobilité de relais l2
WO2022041115A1 (fr) Procédé de partage de piles de protocoles en double connectivité
WO2021223204A1 (fr) Resélection de cellule de type véhicule à tout
WO2022000484A1 (fr) Conception de signal de réveil pour de multiples sessions de multidiffusion
WO2021253258A1 (fr) Alignement de signal de référence de suivi de phase pour canal partagé physique
EP4133823A1 (fr) Capacité de transmission et de réception de dispositif sans fil dans des informations de commande de liaison latérale
WO2021046933A1 (fr) Signalisation internodale de configuration de mesure
WO2022147646A1 (fr) Procédures de transfert intercellulaire direct pour mobilité de relais l2
WO2023044600A1 (fr) Techniques de gestion d'identifiant d'équipement d'utilisateur distant local
US11758592B2 (en) Implicit beam indication
WO2022170556A1 (fr) Identifiant d'équipement utilisateur supplémentaire pour réponse de radiomessagerie
WO2022011612A1 (fr) Mise à jour de signal de référence d'affaiblissement de trajet pour de multiples faisceaux
WO2023070359A1 (fr) Mécanisme d'ue amélioré pour augmenter la chance d'une redirection irat
US20240073994A1 (en) A rapid signaling release solution after paging response
WO2021195911A1 (fr) Connexion à un service à multiples technologies d'accès radio en un mode non autonome
WO2022151146A1 (fr) Techniques de transfert intercellulaire d'équipement d'utilisateur distant en raison de la mobilité d'un équipement d'utilisateur relais
US20210352674A1 (en) Group common control for coverage enhancement for uplink control channel
WO2021212298A1 (fr) Reprise rapide de service réseau en cas de conflit de ressources radio
WO2021232408A1 (fr) Récupération de connexion dans un service d'abonné double
US20220225305A1 (en) Techniques for signaling a panel switching capability of a user equipment
WO2021223056A1 (fr) Récupération après un blocage de données dans des systèmes de communication sans fil

Legal Events

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

Ref document number: 21916700

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

Country of ref document: EP

Kind code of ref document: A1