Acquisition of base system information over sidelink remote device

Abstract

Aspects of the present disclosure relate to devices and methods for wireless communication that use sidelink communication to relay base system information to a user equipment that is remote from and outside of a coverage area of a serving network device. The relay communication device continues to relay the base system information to the remote communication device using the sidelink communication even after being released while the remote communication device is in the radio resource control connected state. Release is transmitted by the remote communication device to the relay communication device as a requirement that the remote communication device enters a radio resource control connected state.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly, to wireless communications using sidelink communications for distributing basic system information. Background Art

[0002] A wireless communication system may include one or more network communication devices, including network devices, which may be further referred to as eNodeB (eNB), next generation NodeB (gNB) or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may be further referred to as user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth generation (6G)).

[0003] In addition to traditional cellular scheduling of wireless communications, recent implementations also include communicating in unlicensed spectrum using sidelink communications over the PC5 interface. A UE within the coverage area of ​​a base station or network device (such as an eNB) can act as a relay UE for another UE ("remote UE") inside or outside the coverage area of ​​the network device. In an example, the eNB is an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) as defined by the Third Generation Partnership Project (3GPP) for RG Long Term Evolution (LTE). The relay UE can execute the Evolved ProSe UE to Network Relay Protocol to support connection management, system information (SI) delivery, paging and access control for the remote UE. Summary of the invention

[0004] The present disclosure proposes a method, apparatus and system for supporting wireless communication of basic system information using sidelink communication relayed to a remote user equipment even after the remote user equipment transitions to a radio resource control connected state. By maintaining updated basic system information (such as system information block type 1 (SIB1)), the remote user equipment can acquire and connect to a network device while in a radio resource control connected state.

[0005] Some implementations of the methods and apparatus described herein may include receiving basic system information from a serving network device via a relay communication device at a remote communication device. Some implementations may also include communicating with a relay communication device via a side link communication channel via a transceiver of the remote communication device. In response to the remote communication device transitioning to a radio resource control connected state, the method may also include automatically sending a release of basic system information originating from a serving network device from the remote communication device to the relay communication device, wherein the transmission of the release is a requirement for the device to enter a radio resource control connected state. The method may also include subsequently sending a request for basic system information to the serving network device via the relay device. The relay communication device and the serving network device are configured to ignore the release of the relay basic system information. Therefore, while in the radio resource control connected state, the method may also include receiving a response containing basic system information from the serving network device via the relay device.

[0006] Some implementations of the methods and apparatus described herein may also include relaying basic system information via a side link communication channel by a relay communication device. The method may also include: receiving, via a transceiver of the relay communication device, a release to relay basic system information originating from a serving network device to a remote device, the release being a required communication from a remote device connected to the side link when the remote device is transitioning to a radio resource control connected state. The method may also include: identifying the release as a release that needs to be sent via an RRC connection state protocol but does not control the demand for basic system information by the remote device. The method may also include: subsequently receiving a request for basic system information from the remote device via the transceiver. In response to receiving the request, the method may also include ignoring the release of relaying basic system information and relaying the request to the serving network device. The method may also include receiving basic system information from the serving network device. The method may also include sending basic system information to a remote device in a radio resource control connected state. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 An example of a wireless communication system supporting distribution of basic system information to a remote user equipment in a radio resource control (RRC) connected state using sidelink communication according to aspects of the present disclosure is shown.

[0008] Figure 2 A diagram illustrating message transfer between a remote communication device and a relay communication device with continued relaying of basic system information after receiving a release request from the remote communication device according to aspects of the present disclosure is shown.

[0009] Figure 3A diagram illustrating message delivery between a remote communication device and a relay communication device from communicating basic system information by ignoring a release received from the remote communication device while the remote communication device is in a radio resource control connected state according to aspects of the present disclosure, with continued relaying of basic system information.

[0010] Figure 4 A message passing diagram between a remote communication device, a relay communication device, and a serving network device is shown, the serving network device being enabled to continue sending basic system information while the remote communication device is in a radio resource control connected state, according to aspects of the present disclosure.

[0011] Figure 5 A message passing diagram is shown between a remote communication device, a relay communication device, and a serving network device, all configured to continue to send basic system information while the remote communication device is in a radio resource control connected state, according to aspects of the present disclosure.

[0012] Figure 6 An example of a block diagram of a user equipment utilizing sidelink communication to relay or receive basic system information according to aspects of the present disclosure is shown.

[0013] Figure 7 An example of a block diagram of a serving network device supporting sidelink wireless communications that distributes basic system information according to aspects of the present disclosure is shown.

[0014] Figure 8 A flow chart presenting a wireless communication method at a remote communication device according to aspects of the present disclosure is shown, the remote communication device continuing to receive basic system information using sidelink communication while in a radio resource control connected state.

[0015] Fig. 9 A flow chart presenting a wireless communication method at a relay communication device according to aspects of the present disclosure is shown, the relay communication device continuing to relay basic system information using sidelink communications while a remote communication device is in a radio resource control connected state. DETAILED DESCRIPTION

[0016] A UE within the coverage area of ​​a fifth generation (5G) new radio (NR) base node (gNB) can act as a relay UE for a remote UE within or outside the coverage area. A UE-to-network (U2N) relay UE can forward basic system information (SI) to a U2N remote UE via broadcast, multicast, or dedicated PC5-to-radio resource control (RRC) signaling. An example of basic SI is a system information block type 1 (SIB1), which carries information relevant to evaluating whether a UE is allowed to access a cell and defines the scheduling of other system information. SIB1 also provides radio resource confirmation information and barring information.

[0017] According to a known implementation or a proposed implementation, a U2N remote UE may request that certain system information blocks (SIBs) be forwarded by a U2N relay UE over a PC5-RRC connection. The request is made for a list of required SIBs in the sl-Request-SI-List. The U2N relay UE then obtains the requested SIBs and forwards them to the remote UE. However, when the remote UE is entering the RRC_Connected state, the remote UE releases the request for the relay UE to forward (multiple) SIBs. Upon receiving this release SIB request, the relay UE no longer forwards the SI to the remote UE. Specifically, once the UE enters the RRC_Connected state, the relay UE will not forward updates to the requested SIBs or SIB1. In the RRC_Connected state, the remote UE may use the DEDICATEDSIBREQUEST message to request certain SIBs: sib12, sib13, sib14, sib20-v1700, sib21-v1700, spare3, spare2, and spare1.

[0018] However, the remote UE cannot use DEDICATEDSIBREQUEST to request basic SI, such as SIB1, in the RRC_Connected state. Therefore, the remote UE has two unsatisfactory options. First, the remote UE that cannot receive SIB1 updates may continue to use the version of SIB1 last received before it transitions to the RRC_Connected state. As a result, the remote UE may be using an outdated / invalid configuration. With an invalid configuration, the remote UE may not be able to monitor the radio conditions of the serving cell, such as using the ServingCellConfigCommonSIB message containing synchronization signal block (SSB) information. Second, the remote UE that cannot maintain a valid version of SIB1 may believe that the remote UE is prohibited from using the serving cell.

[0019] In multiple embodiments, the present disclosure supports maintaining valid basic system information, such as SIB1, at a remote UE that has entered the RRC_Connected state. In one embodiment, the U2N relay UE is configured to continue forwarding SIB1 updates to the U2N remote UE regardless of whether information indicating that the forwarding of SIB1 should be stopped has been received. Specifically, the relay UE continues to forward SIB1 regardless of whether a RemoteUEInformationSidelink message is received, and does not modify the operation based on the content of the message. In another embodiment, the U2N remote UE is configured not to request to terminate the forwarding of basic SI such as SIB1 when entering the RRC_Connected state. Specifically, the remote UE does not set the sl-Requested-SI-List to the value "Release" while transitioning to the RRC_Connected state or after transitioning to the RRC_Connected state. In another embodiment, a service UE, such as a network device or base station, is configured to send SIB1 and its updates to all U2N remote UEs. In another embodiment, the communication system of the UE and the network device is configured to support a DedicatedSIBRequest message, which may include explicit information allowing SIB1 requests from U2N remote UEs. Each of the embodiments enables the remote UE to maintain accurate basic SI and thereby access the serving UE or network device while using a PC5-RRC connection to the relay UE.

[0020] According to aspects of the present disclosure, a method for wireless communication at a remote communication device is provided. The method may include communicating with a relay communication device via a sidelink communication channel via a transceiver of the remote communication device. The method includes sending a first request for at least one system information block originating from a serving network device to the relay communication device. The method includes receiving at least one system information block from the relay communication device. In response to transitioning to a radio resource control (RRC) connected state, the method may include sending a release of basic system information originating from a serving network device to the relay device. The method may include sending a second request for at least one system information block to the serving network device via the relay device. While in the RRC connected state, the method may include receiving a response containing at least one system information from the serving network device via the relay device. In one or more embodiments, the first request for at least one system information block is a radio resource control message. In one or more embodiments, the second request for at least one system information block and the response containing at least one system information block are RRC messages.

[0021] According to another aspect of the present disclosure, a method for wireless communication at a relay communication device is provided. The method may include communicating with a serving network device via a wireless communication channel via a transceiver of the relay communication device. The method may include communicating with a remote device via a side link communication channel via a transceiver of the relay device. The method may include receiving a first request for at least one system information block originating from the serving network device from a relay device. The method may include sending at least one system information block received from the serving network device to a remote device. The method may include receiving a release of basic system information originating from the serving network device from a remote device that has transitioned to a radio resource control connected state. The method may include relaying to the serving network device a second request for at least one system information block received from the remote device. The method may include relaying to the remote device in the radio resource control connected state a response containing at least one system information received from the serving network device.

[0022] Some implementations of the methods and apparatus described herein may include receiving basic system information from a serving network device. Some implementations may also include relaying the basic system information to a remote user device via a sidelink communication channel. Some implementations may also include receiving a release of the relayed basic system information from the remote user device, the remote user device transitioning to a radio resource control connected state. Some implementations may also include, in response to receiving updated basic system information from the serving network device, relaying the updated basic system information to the remote user device via a sidelink communication channel while the remote user device is in a radio resource control connected state.

[0023] Some implementations of the methods and apparatus described herein may further include receiving basic system information originating from a serving network device from a relay user equipment via a sidelink communication channel. Some implementations may further include, in response to transitioning to a radio resource control connected state, the aforementioned release of relay basic system information to the relay user equipment. Some implementations may further include: while in a radio resource control connected state, receiving updated basic system information originating from a serving network device from a relay user equipment via a sidelink communication channel.

[0024] Some implementations of the methods and apparatus described herein may also include: sending basic system information, by the network device, to the intermediate device, the basic system information being addressed to a remote user device communicatively coupled to the intermediate device via a sidelink communication channel. Some implementations of the methods and apparatus described herein may also include, in response to determining that the remote user device has transitioned to a radio resource control connected state, sending updated basic system information to the remote user device via a direct connection corresponding to the radio resource control connected state by the network device.

[0025] In one or more embodiments, some implementations further include determining that the remote user equipment has transitioned to a radio resource control connected state based on receiving a dedicated system information block request from the remote user equipment. In one or more embodiments, some implementations further include determining that the remote user equipment has transitioned to a radio resource control connected state based on receiving a request for required basic system information via a user equipment assistance information message.

[0026] Figure 1 An example of a wireless communication system 100 that supports wireless communication of basic system information using side link communications relayed to a remote user device even after the remote user device transitions to a radio resource control connected state according to aspects of the present disclosure is shown. The wireless communication system 100 may include one or more base stations or network devices 102, one or more UEs 104, a core network 106, and a packet data network 109. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network. The wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0027] One or more network devices 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more network devices 102 described herein may be or include or may be referred to as a base transceiver station, access point, NodeB, eNodeB (eNB), next generation NodeB (gNB) or other suitable terms. The network device 102 and the UE 104 may communicate via a communication link 108, which may be a wireless or wired connection. For example, the network device 102 and the UE 104 may communicate wirelessly via a Uu interface.

[0028] The network device 102 may provide a geographic coverage area 110 for which the network device 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 110. For example, the network device 102 and the UE 104 may support wireless communications of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more wireless access technologies. In some implementations, the network device 102 may be mobile, such as a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 110 may be associated with different network devices 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0029] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 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 term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In some other implementations, UE 104 may move in the wireless communication system 100.

[0030] One or more UEs 104 may be devices of different forms or with different capabilities. Figure 1 Some examples of UE 104 are shown in FIG. UE 104 can communicate with various types of devices, such as network device 102, other UE 104, or network devices (e.g., core network 106, relay device, integrated access and backhaul (IAB) node, or another network device), such as Figure 1 Additionally, or alternatively, the UE 104 can support communications with other network devices 102 or UEs 104 by acting as a relay UE that relays information between the network devices 102 and other UEs 104 within the wireless communication system 100.

[0031] UE 104 may also support direct wireless communication with other UE 104 via communication link 112. For example, UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations such as vehicle-to-vehicle (V2V) deployment, vehicle-to-everything (V2X) deployment, or cellular-V2X deployment, communication link 112 may be referred to as a side link. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface. In one example, relay UE 104a has a PC5-RRC connection with a remote UE 104b located outside of coverage area 110 on communication link 112a. Relay UE 104a has a PC5-RRC connection with a remote UE 104c located outside of coverage area 110 on communication link 112b. Even when one or both of the remote UEs 104b-104c are in the RRC_Connected state, the network device 102, the relay UE 104a, and one or more of the remote UEs 104b-104c are configured to support sending, relaying, or receiving updated basic SI, respectively. The remote UEs 104b-104c are able to access and connect to the network device 102 using basic SI such as SIB1.

[0032] The network device 102 may support communication with the core network 106 or with another network device 102, or both. For example, the network device 102 may interface with the core network 106 via one or more backhaul links 114 (e.g., via S1, N2, N2 or another network interface). The network devices 102 may communicate with each other via the backhaul links 114 (e.g., via X2, Xn or another network interface). In some implementations, the network devices 102 may communicate directly with each other (e.g., between the network devices 102). In some other implementations, the network devices 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network devices 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmission-reception points (TRPs).

[0033] In some implementations, the network entity or network device 102 may be configured as a decomposed architecture, which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities or network devices 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration initiated by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity or network device 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (Near-RT RIC), a non-real-time RIC (Non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0034] The RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of a network entity or a network device 102 in a decomposed RAN architecture may be co-located, or one or more components of a network entity or a network device 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities or network devices 102 of the decomposed RAN architecture may be implemented as a virtual unit (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0035] The split of functions between CU, DU and RU may be flexible and may support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU or RU. For example, a functional split of the protocol stack may be adopted between the CU and the DU so that the CU may support one or more layers of the protocol stack, while the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU may be connected to one or more DUs or RUs, and one or more DUs or RUs may host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and may each be at least partially controlled by the CU.

[0036] In addition, or alternatively, a functional split of the protocol stack may be employed between the DU and the RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU or between the DU and the RU may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different one of the CU, DU, or RU).

[0037] The CU may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU may be connected to one or more DUs via a mid-range communication link (e.g., F1, F1c, F1u), and the DU may be connected to one or more RUs via a front-haul communication link (e.g., an open front-haul (FH) interface). In some implementations, the mid-range communication link or the front-haul communication link may be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by a corresponding network entity or network device 102 communicating via such a communication link.

[0038] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)) and user plane entities that route or interconnect packets to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of one or more UEs 104 served by one or more network devices 102 associated with the core network 106.

[0039] The core network 106 may communicate with the packet data network 109 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The packet data network 109 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via a network entity or network device 102. The core network 106 may use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118. The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0040] In the wireless communication system 100, the network entity or network device 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the network entity or network device 102 and the UE 104 may support different resource structures. For example, the network entity or network device 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the network entity or network device 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the network entity or network device or network device 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The network entity or network device 102 and the UE 104 may support various frame structures based on one or more parameter sets.

[0041] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a normal cyclic prefix. In some implementations, a first parameter set (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15kHz) may utilize one slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a normal cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a normal cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a normal cyclic prefix.

[0042] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0043] In addition, or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include multiple (e.g., number) time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with the corresponding subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include multiple (e.g., number) symbols (e.g., OFDM symbols). In some implementations, the number of time slots (e.g., number) of a subframe may depend on the parameter set. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60kHz subcarrier spacing), a time slot may include 12 symbols. For normal cyclic prefix and extended cyclic prefix, the relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame may depend on the parameter set. It should be understood that references to a first parameter set (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15kHz) may be used interchangeably between subframes and slots.

[0044] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various classes, bands, channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as the frequency range designations FR1 (410 MHz-7.125 GHz), FR2 (24.25 GHz-52.6 GHz), FR3 (7.125 GHz-24.25 GHz), FR4 (52.6 GHz-114.25 GHz), FR4a or FR4-1 (52.6 GHz-71 GHz), and FR5 (114.25 GHz-300 GHz). In some implementations, the network entity or network device 102 and the UE 104 can perform wireless communications on the one or more operating frequency bands. In some implementations, FR1 can be used by the network entity or network device 102 and the UE 104 and other devices or apparatuses for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by network entities or network devices 102 and UE 104 and other devices or apparatuses for short-range, high data rate capabilities.

[0045] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with a first parameter set (e.g., μ=0) including a 15kHz subcarrier spacing, a second parameter set (e.g., μ=1) including a 30kHz subcarrier spacing, and a third parameter set (e.g., μ=2) including a 60kHz subcarrier spacing. FR2 may be associated with one or more parameter sets (e.g., at least 2 parameter sets). For example, FR2 may be associated with a third parameter set (e.g., μ=2) including a 60kHz subcarrier spacing, and a fourth parameter set (e.g., μ=3) including a 120kHz subcarrier spacing.

[0046] Figure 2 The U2N remote device 202 (such as UE 104b-104c ( Figure 1 )) and a U2N relay device 204 (such as UE 104a ( Figure 1 )) between the U2N relay device 204. In a first aspect, the U2N relay device 204 is configured to relay basic system information to the remote device 202 via sidelink communication even after the remote device 202 releases the relaying of basic system information when the remote device 202 is transitioning to the RRC connected state. SIB1 continues to be forwarded from the relay device 204 to the remote device 202 even if the remote device 202 has "released" the requested SIB(s) (i.e., has set sl-Requested-SI-List to the value Released).

[0047] At 210, the U2N relay device 204 may provide SIB1 and its updates to the U2N remote device 202. At 211, the remote device 202 explicitly requests additional SIB(s). In the example, the request is in the form of RemoteUEInformationSidelink(sl-Requested-SI-List). After receiving the SIB request, the U2N relay device 204 will obtain the requested SIB(s). At 212, the relay device 204 then forwards these requested SIB(s) to the remote device 202. At 213, the relay device 204 may relay the updated SIB1. At 214, the remote device 202 enters the RRC_Connected state. At 215, in response to the RRC_Connected state, the remote device 202 notifies the relay device 204 that it is no longer requesting SIB(s) by sending a RemoteUEInformationSidelink message and setting the included sl-Requested-SI-List to the value "Release". At 216 , as part of the present embodiment, U2N relay device 204 is configured to keep forwarding the SIB1 update to remote device 202 even after having received the message at 215 .

[0048] Figure 3 The U2N remote device 302 (such as UE 104b-104c ( Figure 1 )) and a U2N relay device 304 (such as UE 104a ( Figure 1 )) between the messaging diagram 300. In a second aspect, the U2N remote device 302 is configured to not release the U2N relay device 304 relaying basic system information to the remote device 302 via sidelink communication when transitioning to the RRC connected state.

[0049] At 310, the U2N relay device 304 may provide SIB1 and its updates to the U2N remote device 302. At 311, the remote device 302 explicitly requests additional SIB(s). In the example, the request is in the form of RemoteUEInformationSidelink(sl-Requested-SI-List). After receiving the SIB request, the U2N relay device 304 will obtain the requested SIB(s). At 312, the relay device 304 then forwards these requested SIB(s) to the remote device 302. At 313, the relay device 304 may relay the updated SIB1. At 314, the remote device 302 enters the RRC_Connected state. At 315, the remote device 202 is configured to no longer notify the relay device 304 that the SIB(s) are no longer requested. The remote device 302 does not send a RemoteUEInformationSidelink message with the included sl-Requested-SI-List set to the value "Release". Instead, at 316, the remote device 302 may send a RemoteUEInformationSidelink message (sl-Requested-SI-List) requesting only the SIB(s) that the remote device 302 may need in the RRC Connected state from the relay device 304. At 317, the U2N relay device 304 relays the requested SIB(s). At 318, the U2N relay device 204 relays the SIB1 update. Depending on the availability of the SIB1 update, the U2N relay device 204 may relay the SIB1 update before or after the requested SIB(s).

[0050] Figure 4 4. In the U2N remote device 402 (such as UE 104b-104c ( Figure 1 )), U2N relay device 404 (such as UE 104a ( Figure 1 )) and service device 406 (such as network device 102 ( Figure 1 )) messaging diagram 400. In a third aspect, the serving device 406 is configured to distribute basic system information such as SIB1 to the U2N remote device 402 even when the U2N remote device 402 transitions to the RRC connected state.

[0051] At 410, the U2N relay device 404 may provide SIB1 and its updates to the U2N remote device 402. At 411, the remote device 402 explicitly requests additional SIB(s). In an example, the request is in the form of RemoteUEInformationSidelink(sl-Requested-SI-List). After receiving the SIB request, the U2N relay device 404 will obtain the requested SIB(s). At 412, the relay device 404 then forwards these requested SIB(s) to the remote device 402. At 413, the relay device 404 may relay the updated SIB1. At 414, the remote device 402 enters the RRC_Connected state. The serving device 406 sends the updated master information block (MIB) / SIB1 to the remote device 402 in the RRC connected state. At 415, in response to the RRC_Connected state, the remote device 402 notifies the relay device 404 that it is no longer requesting (multiple) SIBs by sending a RemoteUEInformationSidelink message and setting the included sl-Requested-SI-List to the value "Release". Regardless of the release, the service device 406 is configured to identify that a certain UE is a U2N remote device 402 because the remote device 402 is connecting via the U2N relay device 404. In an example, the service device 406 identifies this state based on the presence of a Sidelink Relay Adaptation Protocol (SRAP) header. In response, at 416, the service device 406 ignores the release and forwards the SIB1 update to the U2N remote device 402.

[0052] Figure 5 The U2N remote device 502 (such as UE 104b-104c ( Figure 1 )), U2N relay device 504 (such as UE 104a ( Figure 1 )) and service device 506 (such as network device 102 ( Figure 1 )) between the message passing diagram 500. In the fourth aspect, the U2N remote device 502, the U2N relay device 504 and the serving device 506 are also configured to support messaging to distribute basic system information such as SIB1 even when the U2N remote device 502 transitions to the RRC connected state.

[0053] At 510, the U2N relay device 504 may provide SIB1 and its updates to the U2N remote device 502. At 511, the remote device 502 explicitly requests other SIB(s). In an example, the request is in the form of RemoteUEInformationSidelink(sl-Requested-SI-List). After receiving the SIB request, the U2N relay device 504 will obtain the requested SIB(s). At 512, the relay device 504 then forwards these requested SIB(s) to the remote device 502. At 513, the relay device 504 may relay the updated SIB1. At 514, the remote device 502 enters the RRC_Connected state. The serving device 506 sends the updated master information block (MIB) / SIB1 to the remote device 502 in the RRC connected state. At 515, in response to the RRC_Connected state, the remote device 502 notifies the relay device 504 that it is no longer requesting SIB(s) by sending a RemoteUEInformationSidelink message and setting the included sl-Requested-SI-List to a value of "Release".

[0054] Regardless of the release, the serving device 506 is configured to identify that a certain UE is a U2N remote device 502 because the remote device 502 is connecting via the U2N relay device 504. In an example, the serving device 506 identifies this state based on the presence of a Sidelink Relay Adaptation Protocol (SRAP) header. At 516, the remote device 502 sends a SIB-ReqInfo in a DEDICATEDSIBREQUEST message containing an indication of SIB1 or basic system information (MIB and SIB1). At 517, upon receiving the SIB1 request in an uplink RRC message (inside the DedicatedSIBRequest message), the serving device 506 can provide SIB1 and its updates (when and when these are available) in a downlink RRC message.

[0055] The ASN.1 message structure of the DedicatedSIBRequest message can be constructed as follows:

[0056]

[0057]

[0058] In the fifth aspect, the UE requests the required basic system information (MIB, SIB1) from the gNB using UAI (UEAssistanceInformation). This embodiment is the same as the previous embodiment, except that in this embodiment, the SIB1 request is made using UEAssistanceInformation instead of DedicatedSIBRequest message.

[0059] Figure 6 An example of a block diagram 600 of a user equipment 602 that utilizes sidelink communication to relay or receive basic system information (such as SIB1) according to aspects of the present disclosure is shown. When operating as a relay communication device, the user equipment 602 can relay basic system information to a remote UE in an RRC connected state. When operating as a remote communication device, according to aspects of the present disclosure, the user equipment 602 can receive basic system information from the relay UE even while the user equipment 602 is in a radio resource control (RRC) connected state. The user equipment 602 can be an example of a UE 104 as described herein. The user equipment 602 can support wireless communication with one or more network devices 102, UE 104, or any combination thereof. The user equipment 602 can include components for two-way communication, including components for sending and receiving communications, such as a communication manager 604, a processing subsystem 606, a memory 608, a receiver 610, a transmitter 612, and an I / O controller 614. These components may be in electronic communication or otherwise coupled (eg, operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (eg, buses). Receiver 610 and transmitter 612 may exist on the same chip and are collectively referred to as transceiver 615 .

[0060] The communication manager 604, the receiver 610, the transmitter 612, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure as described herein. For example, the communication manager 604, the processing subsystem 606, the receiver 610, the transmitter 612, or various combinations or components thereof, may support methods for performing one or more functions described herein.

[0061] In some implementations, the communication manager 604, the receiver 610, the transmitter 612, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a data processor 616, a digital signal processor (DSP) 617, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports a device for performing the functions described in the present disclosure. In some implementations, the processing subsystem 606 and the memory 608 coupled to the processing subsystem 606 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 608 by the processing subsystem 606). In an example, an executable sidelink relay module 618 stored in the memory 608 and executed by the processing subsystem 606 configures the user equipment 602 to relay or receive basic system information while transitioning to and being in a radio resource control (RRC) connected state.

[0062] Additionally, or alternatively, in some implementations, the communication manager 604, receiver 610, transmitter 612, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by the processing subsystem 606. If implemented in code executed by the processing subsystem 606, the functionality of the communication manager 604, receiver 610, transmitter 612, or various combinations or components thereof may be performed by a general purpose processor, DSP, central processing unit (CPU), ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., devices configured or otherwise supported for performing the functions described in the present disclosure).

[0063] In some implementations, the communication manager 604 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 610, the transmitter 612, or both. For example, the communication manager 604 may receive information from the receiver 610, send information to the transmitter 612, or be integrated with the receiver 610, the transmitter 612, or both to receive information, send information, or perform various other operations as described herein. Although the communication manager 604 is shown as a separate component, in some implementations, one or more functions described with reference to the communication manager 604 may be supported or performed by the processing subsystem 606, the memory 608, or any combination thereof. For example, the memory 608 may store code that may include instructions executable by the processing subsystem 606 to cause the user device 602 to perform various aspects of the present disclosure as described herein, or the processing subsystem 606 and the memory 608 may be otherwise configured to perform or support such operations.

[0064] For example, the communication manager 604 can support wireless communication at a first device (e.g., user device 602) according to examples as disclosed herein. The communication manager 604 can be configured to or otherwise support wireless communication using sidelink communication in an unlicensed spectrum. Specifically, the processing subsystem 606 configures the communication manager 604 and the transceiver 615 to support sidelink wireless communication relay or receive basic system information from a serving network device, where the device 602 acts as a relay device or a remote device.

[0065] The processing subsystem 606 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). In some implementations, the processing subsystem 606 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processing subsystem 606. The processing subsystem 606 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 608) to enable / configure the user device 602 to perform various functions of the present disclosure.

[0066] Memory 608 may include random access memory (RAM) and read-only memory (ROM). Memory 608 may store computer-readable, computer-executable code, which includes instructions that, when executed by processing subsystem 606, cause user device 602 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some embodiments, the code may not be directly executed by processing subsystem 606, but may cause / configure a computer (e.g., when the code is compiled and executed) to perform the functions described herein. In some implementations, memory 608 may include, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0067] The I / O controller 614 can manage input and output signals for the user device 602. The I / O controller 614 can also manage peripheral devices that are not integrated into the user device 602. In some implementations, the I / O controller 614 can represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 614 can utilize an operating system, such as

[0068] Or another known operating system. In some implementations, I / O controller 614 can be implemented as part of a processor, such as processing subsystem 606. In some implementations, a user can interact with user device 602 via I / O controller 614 or via hardware components controlled by I / O controller 614.

[0069] In some implementations, the user equipment 602 may include a single antenna 620. However, in some other implementations, the user equipment 602 may have more than one antenna 620, which may be able to simultaneously send or receive multiple wireless transmissions. The receiver 610 and the transmitter 612 may communicate bidirectionally via one or more antennas 620, wired or wireless links as described herein. For example, the receiver 610 and the transmitter 612 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem for modulating packets, providing the modulated packets to one or more antennas 620 for transmission, and demodulating packets received from one or more antennas 620.

[0070] In one or more embodiments, user device 602 is a remote user device (such as Figure 1 104a) performs wireless communication with a relay device or an intermediate device (such as UE 104a) of UE 104b-104c. UE 104a-104c may be incorporated into user equipment 602 ( Figure 6 ) components and functions. User equipment 602 receives basic system information from a serving network device. User equipment 602 relays the basic system information to a remote user equipment via a sidelink communication channel. After / when the remote user equipment transitions to a radio resource control connected state, user equipment 602 receives a release to relay basic system information from the remote user equipment. In response to receiving updated basic system information from the serving network device, user equipment 602 relays the updated basic system information to the remote user equipment via a sidelink communication channel while the remote user equipment is in a radio resource control connected state.

[0071] In one or more embodiments, the user device 602 is used as a relay device by an intermediate device or relay device (such as Figure 1 UE104a) supports remote devices (such as Figure 1 UE 104b-104c) performs wireless communication. User equipment 602 receives basic system information originating from the serving network device from the relay user equipment via the side link communication channel. In one or more embodiments, in response to transitioning to the radio resource control connected state, the user equipment 602 sends a release of the relay basic system information to the relay user equipment. While in the radio resource control connected state, the user equipment 602 receives updated basic system information originating from the serving network device from the relay user equipment via the side link communication channel.

[0072] Figure 7 An example of a block diagram 700 of a network device 702 supporting sidelink wireless communication for distributing basic system information (such as SIB1) according to aspects of the present disclosure is shown. The network device 702 can send the basic system information to a remote UE via a relay UE before and after transitioning to a radio resource control (RRC) connected state. The network device 702 can be an example of a network device 102 or a base node as described herein. The network device 702 can support communication with a remote UE such as a base node 102 or a relay UE. Figure 1 106, UE 104, or any combination thereof. The network device 702 may include components for bidirectional communication, including components for sending and receiving communications, such as a scheduler 704, a processing subsystem 706, a memory 708, a receiver 710, a transmitter 712, and an I / O controller 714. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus). The receiver 710 and the transmitter 712 may be located on a single chip and are collectively referred to as a transceiver 715.

[0073] The scheduler 704, the receiver 710, the transmitter 712, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure as described herein. For example, the scheduler 704, the receiver 710, the transmitter 712, or various combinations or components thereof, may support methods for performing one or more functions described herein.

[0074] In some implementations, the scheduler 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor 716, a digital signal processor (DSP) 717, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured as or otherwise supports a device for performing the functions described in the present disclosure. In some implementations, the processing subsystem 706 and a memory 708 coupled to the processing subsystem 706 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 708 by the processing subsystem 706).

[0075] Additionally, or alternatively, in some implementations, the scheduler 704, receiver 710, transmitter 712, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by the processing subsystem 706. If implemented in code executed by the processing subsystem 706, the functions of the scheduler 704, receiver 710, transmitter 712, or various combinations or components thereof may be performed by a general purpose processor, DSP, central processing unit (CPU), ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., a device configured or otherwise supported for performing the functions described in the present disclosure).

[0076] In some implementations, the scheduler 704 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 710, the transmitter 712, or both. For example, the scheduler 704 may receive information from the receiver 710, send information to the transmitter 712, or be integrated with the receiver 710, the transmitter 712, or both—to receive information, send information, or perform various other operations as described herein. Although the scheduler 704 is shown as a separate component, in some implementations, one or more functions described with reference to the scheduler 704 may be supported or performed by the processing subsystem 706, the memory 708, or any combination thereof. For example, the memory 708 may store code that may include instructions that may be executed by the processing subsystem 706 to cause / configure the network device 702 to perform various aspects of the present disclosure as described herein, or the processing subsystem 706 and the memory 708 may be otherwise configured to perform or support such operations.

[0077] For example, the scheduler 704 may support wireless communication at a first network device (e.g., network device 702) according to examples as disclosed herein. The scheduler 704 may be configured to support wireless communication of basic system information with a relay communication device relayed via a side link communication channel. Specifically, the processing subsystem 706 configures the scheduler 704 and the transceiver 715 to perform wireless communication.

[0078] The processing subsystem 706 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). In some implementations, the processing subsystem 706 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processing subsystem 706. The processing subsystem 706 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 708) to cause the network device 702 to perform various functions of the present disclosure.

[0079] The memory 708 may include a random access memory (RAM) and a read-only memory (ROM). The memory 708 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processing subsystem 706, cause the network device 702 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some implementations, the code may not be directly executed by the processing subsystem 706, but may enable / configure the computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 708 may include, in particular, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interactions with peripheral components or devices. The network device 702 may store an executable sidelink relay module 718, which, when executed, configures the network device 702 to send basic system information to a relay UE, which is relayed to a remote UE in a radio resource control (RRC) connected state via a sidelink communication.

[0080] I / O controller 714 can manage input and output signals of network device 702. I / O controller 714 can also manage peripheral devices that are not integrated into network device 702. In some implementations, I / O controller 714 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 714 can utilize an operating system, such as

[0081] Or another known operating system. In some implementations, I / O controller 714 can be implemented as part of a processor, such as processing subsystem 706. In some implementations, a user can interact with network device 702 via I / O controller 714 or via hardware components controlled by I / O controller 714.

[0082] In some implementations, the network device 702 may include a single antenna 720. However, in some other implementations, the network device 702 may have multiple antennas 720, which may be able to simultaneously send or receive multiple wireless transmissions. The receiver 710 and the transmitter 712 may communicate bidirectionally via one or more antennas 720, wired or wireless links as described herein. For example, the receiver 710 and the transmitter 712 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem for modulating packets, providing the modulated packets to one or more antennas 720 for transmission, and demodulating packets received from one or more antennas 720.

[0083] In one or more embodiments, network device 702 acts as an intermediate device (such as Figure 1 UE 104a) and remote user equipment (such as Figure 1 UE 104a-104c may include user equipment 602 ( Figure 6 ) components and functions. Network device 702 sends basic system information to the intermediate device, the basic system information being addressed to a remote user device communicatively coupled to the intermediate device via a sidelink communication channel. In response to determining that the remote user device has transitioned to a radio resource control connected state, network device 702 sends updated basic system information to the remote user device via a direct connection corresponding to the radio resource control connected state.

[0084] In one or more specific embodiments, the network device 702 determines that the remote user equipment has transitioned to the radio resource control connected state based on receiving a dedicated system information block request from the remote user equipment. In one or more specific embodiments, the network device 702 determines that the remote user equipment has transitioned to the radio resource control connected state based on receiving a request for required basic system information via a user equipment assistance information message.

[0085] According to aspects of the present disclosure, SIB1 is obtained by an RRC_Connected U2N remote UE in the following manner: (a) by continuing to forward SIB1 updates to the U2N remote UE via the U2N relay, regardless of whether RemoteUEInformationSidelink is received and regardless of its content; (b) by the U2N remote UE not setting sl-Requested-SI-List to the value "release" when / after transitioning to RRC_Connected; (c) by the relay UE ensuring that SIB1 and its updates are sent to all U2N remote UEs; or (d) by using a DedicatedSIBRequest and including explicit information within it to allow SIB1 requests.

[0086] In one or more embodiments, the present disclosure provides a method in a remote UE. The method includes initiating a transition from the remote UE to an RRC_connected state. The method includes sending a release of requested system information to a relay UE. The method includes sending a dedicated SIB request to a serving network node and including explicit information for a SIB1 request within the dedicated SIB request.

[0087] In one or more embodiments, the present disclosure provides a method in a network node. The method includes receiving a dedicated SIB request and determining whether a U2N remote UE makes an explicit request for SIB1. The method includes sending SIB1 to an RRC-connected U2N remote UE.

[0088] In one or more embodiments, the present disclosure provides a method in a network node. The method includes determining whether an RRC-connected UE is a U2N remote UE. The method includes sending SIB1 to the RRC-connected U2N remote UE.

[0089] The present disclosure addresses the situation where a relay UE will not provide SIB1 to a remote UE once the remote UE has released a request to forward (multiple) SIBs when entering the RRC_connected state. Otherwise, the remote UE will continue to use a potentially outdated version of SIB1 when it is unable to receive SIB1 updates, indicating an invalid configuration. In the example, the remote UE requires the ServingCellConfigCommonSIB containing SSB information to monitor the radio conditions of the serving cell. In the RRC_connected state, the present disclosure allows the remote UE to request SIB1. As a result, the U2N remote UE is able to maintain a valid version of SIB1 after having transitioned to the RRC_connected state. In one or more embodiments, the present disclosure provides a new relay UE behavior in which the U2N relay device continues to forward SIB1 updates to the U2N remote UE regardless of whether the RemoteUEInformationSidelink is received and regardless of the content of the RemoteUEInformationSidelink. In one embodiment, even if the remote device has "released" the requested SIB(s) (i.e., has set sl-Requested-SI-List to the value Released), SIB1 continues to be forwarded from the relay UE to the remote UE. In another embodiment, the serving gNB sends the updated MIB / SIB1 to the RRC_connected remote UE.

[0090] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Furthermore, aspects of two or more of the methods may be combined.

[0091] Figure 8 A flow chart of a method 800 of supporting wireless communication at a remote communication device according to aspects of the present disclosure is shown, the remote communication device continuing to receive basic system information using sidelink communication while in a radio resource control connected state. The operations of the method 800 may be implemented by a device or components thereof as described herein. For example, the operations of the method 800 may be implemented by a user equipment (such as UE 104 ( Figure 1 ) or as reference Figure 6In some implementations, the user device may execute a set of instructions to control the functional elements of the network device to perform the described functions. In addition, or alternatively, the user device may use dedicated hardware to perform aspects of the described functions.

[0092] At 805, method 800 may include communicating with a relay communication device via a side link communication channel via a transceiver of the communication device. The operations of 805 may be performed according to examples as described herein. In some implementations, aspects of the operations of 805 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0093] At 810, method 800 may also include, in response to the communication device transitioning to the radio resource control connected state, automatically sending a release of basic system information originating from the serving network device to the relay communication device from the communication device, the transmission of the release being a requirement for the device to enter the radio resource control connected state. The operations of 810 may be performed according to examples as described herein. In some implementations, aspects of the operations of 810 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0094] At 815, method 800 may also include subsequently sending a request for basic system information to the serving network device via the relay communication device. The operations of 815 may be performed according to examples as described herein. In some implementations, aspects of the operations of 815 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0095] At 820, the method 800 may also include, while in the radio resource control connected state, receiving a response including system basic information from the serving network device via the relay communication device, wherein the relay communication device and the serving network node are configured to ignore the release of the relay basic system information. The operation of 820 may be performed according to the examples described herein. In some implementations, aspects of the operation of 820 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0096] According to one or more embodiments, method 800 may further include sending a first request for system basic information originating from a serving network device to a relay communication device via a transceiver before the device enters a radio resource control connected state. The request is a second request after the first request. Method 800 may include receiving system basic information from a relay communication device in response to the first request.

[0097] In one or more embodiments, the system basic information includes at least one system information block. In one or more embodiments, the first request for at least one system information block includes a radio resource control message. In one or more embodiments, the second request for at least one system information block and the response including at least one system information block include a radio resource control message.

[0098] Fig. 9 A flow chart of a method 900 of supporting wireless communication at a relay communication device according to aspects of the present disclosure is shown, wherein the relay communication device continues to relay basic system information using sidelink communication while a remote communication device is in a radio resource control connected state. The operations of the method 900 may be implemented by a device or components thereof as described herein. For example, the operations of the method 900 may be implemented by a user equipment (such as UE 104 ( Figure 1 ) or as reference Figure 6 In some implementations, the user device may execute a set of instructions to control the functional elements of the network device to perform the described functions. In addition, or alternatively, the user device may use dedicated hardware to perform aspects of the described functions.

[0099] At 905, method 900 may include communicating with a serving network device via a communication channel via a transceiver of a relay communication device. The operations of 905 may be performed according to examples as described herein. In some implementations, aspects of the operations of 905 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0100] At 910, method 900 may also include communicating with a remote communication device via a side link communication channel via the transceiver. The operations of 910 may be performed according to examples as described herein. In some implementations, aspects of the operations of 910 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0101] At 915, method 900 may also include receiving, via the transceiver, a release to relay basic system information originating from the serving network device to the remote communication device. The release is a required communication from the remote communication device of the sidelink connection when the remote communication device is transitioning to a radio resource control connected state. The operations of 915 may be performed according to examples as described herein. In some implementations, aspects of the operations of 915 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0102] At 920, the method 900 may also include identifying a release as a release that requires transmission via the RRC connection state protocol but does not control the need for basic system information by the remote communication device. The operations of 920 may be performed according to examples as described herein. In some implementations, aspects of the operations of 920 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0103] At 925, method 900 may also include subsequently receiving a request for basic system information from a remote communication device via the transceiver. The operations of 925 may be performed according to examples as described herein. In some implementations, aspects of the operations of 925 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0104] At 930, method 900 may also include, in response to receiving the request, ignoring the release of the relay basic system information. The operations of 930 may be performed according to the examples described herein. In some implementations, aspects of the operations of 930 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0105] At 935, method 900 may also include relaying the request to a serving network device. The operations of 935 may be performed according to examples as described herein. In some implementations, aspects of the operations of 935 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0106] At 940, method 900 may also include receiving basic system information from a serving network device. The operations of 940 may be performed according to examples as described herein. In some implementations, aspects of the operations of 940 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0107] At 945, method 900 may also include sending basic system information to the remote communication device in the radio resource control connected state. The operations of 945 may be performed according to the examples described herein. In some implementations, aspects of the operations of 945 may be performed as described in reference to Figure 1 or Figure 6 The described device is used to perform

[0108] According to aspects of the present disclosure, the request is a second request after the first request. The method 900 may also include receiving a first request for system basic information originating from a serving network device via a transceiver from a remote communication device. The first request is sent before the remote communication device enters a radio resource control connected state. The method 900 may also include relaying the first request to the serving network device. The method 900 may also include receiving basic system information from the serving network device. The method 900 may also include sending the system basic information to the remote communication device in response to the first request.

[0109] In one or more embodiments, the system basic information includes at least one system information block. In one or more embodiments, the first request for at least one system information block includes a radio resource control message. In one or more embodiments, the second request for at least one system information block and the response including at least one system information block include a radio resource control message. In one or more embodiments, the controller records the release.

[0110] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. 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, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0111] 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 sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these. Features that implement the functions may also be physically located at various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0112] Computer-readable media include both non-transient computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Non-transient storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. As an example and not limitation, non-transient computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or can be used to carry or store the required program code device in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Any other non-transient medium.

[0113] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent 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 all included in the definition of computer-readable media. Disks and optical disks as used herein include CDs, laser optical disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, wherein disks are typically used to reproduce data magnetically, and optical disks utilize lasers to reproduce data optically. The above combinations are also included in the scope of computer-readable media.

[0114] As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". In addition, as used herein, including in the claims, a "set" may include one or more elements.

[0115] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that can be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "in favor of other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0116] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A device for wireless communication, the device comprising: a transceiver that enables the device to communicate with a relay device via a sidelink communication channel; as well as a controller communicatively coupled to the transceiver, and the controller: in response to transitioning to a radio resource control connected state, automatically sending to the relay device a release of basic system information that relays originating from a serving network device, the transmission of the release being a requirement for the device to enter the radio resource control connected state; Then sending a request for basic system information to the serving network device via the relay device; as well as While in the radio resource control connected state, receiving a response including the system basic information from the serving network device via the relay device, wherein the relay device and the serving network device are configured to ignore the release of the relay basic system information.

2. The apparatus of claim 1 , wherein the request comprises a second request subsequent to the first request, and the controller: before the device enters the radio resource control connected state, sending the first request for basic system information originating from a serving network device to the relay device via the transceiver; and The system basic information is received from the relay device in response to the first request. The apparatus according to claim 2 , wherein the system basic information comprises at least one system information block. 4 . The apparatus of claim 3 , wherein the first request for the at least one system information block comprises a radio resource control message.

5. The apparatus of claim 3, wherein the second request for the at least one system information block, and the response including the at least one system information block comprises: Radio Resource Control Message.

6. A method for wireless communication at a communication device, the method comprising: communicating with a relay device via a sidelink communication channel via a transceiver of the communication device; in response to the communication device transitioning to a radio resource control connected state, automatically sending from the communication device to the relay device a release of basic system information that relays originating from a serving network device, the transmission of the release being a requirement for the device to enter the radio resource control connected state; Then sending a request for basic system information to the serving network device via the relay device; as well as While in the radio resource control connected state, receiving a response including the system basic information from the serving network device via the relay device, wherein the relay device and the serving network device are configured to ignore the release of the relay basic system information.

7. The method according to claim 6, further comprising: Before the device enters the radio resource control connected state, further sending a first request for basic system information originating from a serving network device to the relay device via the transceiver, the request including a second request after the first request; and The system basic information is received from the relay device in response to the first request. The method according to claim 7 , wherein the system basic information comprises at least one system information block.

9. The method of claim 8, wherein the first request for the at least one system information block comprises a radio resource control message.

10. The method of claim 8, wherein the second request for the at least one system information block, and the response including the at least one system information block comprises: Radio Resource Control Message.

11. A device for wireless communication, the device comprising: a transceiver that enables the device to communicate with a serving network device via a communication channel and with a remote device via a sidelink communication channel; as well as a controller communicatively coupled to the transceiver, and the controller: receiving, via the transceiver, a release to relay basic system information originating from the serving network device to the remote device, the release being a required communication from the remote device of the sidelink connection when the remote device is transitioning to a radio resource control connected state; identifying the release as a release that needs to be sent via an RRC connection state protocol but does not control a need for basic system information by the remote device; then receiving, via the transceiver, a request for basic system information from the remote device; as well as In response to receiving the request: Ignoring said release of relay basic system information; relaying the request to the serving network device; Receiving the basic system information from the serving network device; as well as The basic system information is sent to the remote device in the radio resource control connected state.

12. The apparatus of claim 11, wherein the request comprises a second request subsequent to the first request, and the controller: receiving, via the transceiver, from the remote device the first request for system basic information originating from a serving network device, the first request being sent before the remote device enters the radio resource control connected state; relaying the first request to the serving network device; Receiving the basic system information from the serving network device; as well as The basic system information is sent to the remote device in response to the first request.

13. The apparatus according to claim 12, wherein the system basic information comprises at least one system information block.

14. The apparatus of claim 13, wherein the first request for the at least one system information block comprises a radio resource control message.

15. The apparatus of claim 13, wherein the second request for the at least one system information block, and the response including the at least one system information block comprises: Radio Resource Control Message.

16. The apparatus of claim 11, wherein the controller records the release.

Images