Information forwarding via sidelink relaying

Abstract

This application relates to information forwarding via sidelink relaying. This application relates to devices and components, including apparatus, systems, and methods for information forwarding via sidelink relaying in a wireless network.

Description

Background Technology

[0001] The 3GPP Technical Specifications (TS) define the standards for New Radio (NR) wireless networks. These TSs describe aspects related to the transmission of system information and paging messages in wireless networks. Attached Figure Description

[0002] Figure 1 A network environment according to some implementation schemes is shown.

[0003] Figure 2 The signaling flow is shown according to some implementation schemes.

[0004] Figure 3 Another signaling flow is shown according to some implementation schemes.

[0005] Figure 4 Another signaling flow is shown according to some implementation schemes.

[0006] Figure 5 Another signaling flow is shown according to some implementation schemes.

[0007] Figure 6 Another signaling flow is shown according to some implementation schemes.

[0008] Figure 7 Another signaling flow is shown according to some implementation schemes.

[0009] Figure 8 Another signaling flow is shown according to some implementation schemes.

[0010] Figure 9 The operational flow / algorithm structure according to some implementation schemes is shown.

[0011] Figure 10 Another operational flow / algorithm structure according to some implementation schemes is shown.

[0012] Figure 11 Another operational flow / algorithm structure according to some implementation schemes is shown.

[0013] Figure 12 User equipment according to some implementation schemes is shown. Detailed Implementation

[0014] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, and techniques, are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases “A / B” and “A or B” refer to (A), (B), or (A and B).

[0015] The following is a glossary of terms that may be used in this disclosure.

[0016] As used herein, the term "circuit" refers to a portion of or includes said hardware component configured to provide the described functionality. Hardware components may include electronic circuitry, logic circuitry, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), or digital signal processors (DSPs). In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the said functionality. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functionality (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0017] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0018] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, and network interface cards.

[0019] As used herein, the term "user equipment" or "UE" refers to a device having radio communication capabilities that allow a user to access network resources within a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Furthermore, the term "user equipment" or "UE" can include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0020] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0021] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a particular device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and application or workload units. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualized infrastructure to applications, devices, or systems. The terms "network resource" or "communication resource" can refer to resources accessible by a computer device / system via a communication network. The term "system resource" can refer to any kind of shared entity providing a service and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0022] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0023] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0024] The term "connection" can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0025] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, network hardware, network equipment, network node, or virtualized network function.

[0026] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0027] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include user equipment (UE) 104 and 106 and a base station 108 of a radio access network (RAN). Base station 108 may be a next-generation node B (gNB) to provide one or more 5G New Radio (NR) cells, thereby providing NR user plane and control plane protocol terminals to UE 104 / 106.

[0028] UE 104 can be located within the NR cell provided by base station 108 and can be coupled to base station 108 via the NR Uu interface. UE 104 may also have a sidelink connection to remote UE 106 via a sidelink physical interface (which may also be referred to as the PC5 interface). UE 104 can act as a UE-to-network relay to extend network coverage to remote UE 106. Remote UE 106 may be outside the network coverage area because remote UE 106 is located outside the NR cell, or for example, because remote UE 106 has turned off its Uu modem to save power and is only operating its sidelink modem. By providing a Layer 2 UE-to-NW relay, remote UE 106 can be accessed and controlled by base station 108 via an end-to-end NR Uu interface including the PC5 and NR Uu interfaces. UE 104 (which may also be referred to as relay UE 104) facilitates access and control by base station 108 by forwarding system information and paging messages to remote UE 106.

[0029] In some implementations, base station 108 may transmit downlink control information (DCI) with an indicator to indicate whether specific system information has been updated by the network. For example, the DCI may include a systemInfoModification field, where a bit set to "1" indicates a Broadcast Control Channel (BCCH) modification other than System Information Block (SIB) 6, SIB 7, or SIB 8. BCCH modification may occur in a modification cycle immediately following the modification cycle that transmits the system information modification indication.

[0030] SIB6 / 7 / 8 correspond to Public Warning System (PWS) system information. SIB6 can be used to support primary notifications for Earthquake and Tsunami Warning Systems (ETWS) (e.g., short notifications delivered within four seconds). SIB7 can be used to support secondary notifications for ETWS, which include more details than primary notifications. SIB8 can be used to provide Commercial Mobile Alert Service (CMAS) notifications. CMAS notifications allow service providers to send emergency alerts as text messages to their users.

[0031] For PWS updates, DCI may include ETWS and CMAS indication fields, where one bit, if set to "1", indicates ETWS primary notification and ETWS secondary notification or CMAS notification. For example, updates to SIB6 / 7 / 8.

[0032] The systemInfoModification and etwsAndCmasIndication bits can be set in DCI format 1_0, which scrambles the cyclic redundancy check (CRC) bits using the Paging Radio Network Temporary Identity (P-RNTI).

[0033] For idle or inactive UEs, base station 108 may repeatedly transmit the etwsAndCmasIndication bits because the network may want to warn all incoming UEs that a PWS warning has been received. However, a UE that has already received a warning may not necessarily know whether the warning corresponds to a new PWS message. Therefore, the UE may repeatedly decode the same SIB6 / 7 / 8. If the content of a decoded message has already been received, the UE may not provide the content to its higher layers for display or further action.

[0034] When remote UE 106 is out of coverage (or its Uu mode is off), it may not be able to receive system information directly from base station 108. System information messages (SIB6 / 7 / 8) from PWS can be forwarded to remote UE 106 by relay UE 104 via a side link (which can operate in any RRC state of the remote UE); or pushed to remote UE 106 by the network via dedicated RRC signaling (if / when remote UE 106 enters RRC connection mode).

[0035] Some implementations describe UE 104 performing a filtering process relative to forwarded PWS system information messages. For example, relay UE 104 may decode the complete set of SIB6 / 7 / 8 and only forward the consistent set to remote UE 106. The consistent set excludes duplicate and out-of-order segments. Relay UE 104 may only need to forward new complete PWS messages to remote UE 106. For example, relay UE 104 may only forward segments if the complete set of segments is received. By performing filtering in relay UE 104, remote UE 106 may not need to receive and discard power to process incomplete or duplicate segments.

[0036] Figure 2 Signaling flow 200 for filtering and forwarding system information messages according to some implementations is illustrated. Relay UE 104 can receive SI broadcast messages 204, which may include SIB6, SIB7, or SIB8, and can transmit information corresponding to the SIB broadcast message 204 in SI container 208. Information forwarded in the SI container may contain or be based on the SIB of SI broadcast 204. SI container 208 can be transmitted to remote UE 106 via PC5 interface.

[0037] Another SI broadcast message 212 may be sent, but the relay UE 104 has not yet received the PWS modification indication, and therefore it may not need to decode the SI broadcast message 212. Therefore, the relay UE 104 may also not forward another SI container at that time.

[0038] At 216, the relay UE 104 can receive paging messages for short messages regarding etwsAndCmasindication. For example, the relay UE 104 can process DCI format 1_0 including CRC scrambled by P-RNTI to determine that etwsAndCmasindication is set to "1".

[0039] Upon receiving a paging message for the short message "etwsAndCMASindication", relay UE 104 can receive and decode SI broadcast 220. At 224, relay UE 104 can determine whether the ETWS / CMAS message transmitted by SI broadcast 220 (SIB6 / 7 / 8) is new and complete. If the ETWS / CMAS message includes information not previously provided to remote UE 106, relay UE 104 can determine that the ETWS / CMAS message is new. If the ETWS / CMAS message includes all segments in their correct order, relay UE 104 can determine that the ETWS / CMAS message is complete. In the case of an incomplete ETWS / CMAS message, relay UE 104 can attempt to obtain additional SI broadcast messages until the ETWS / CMAS message is complete.

[0040] Upon determining that the ETWS / CMAS message is new and complete, relay UE 104 may forward the ETWS / CMAS message to remote UE 106 in SI container (SI) 228. This can be transmitted via the PC5 interface. The SI container used for transmitting ETWS / CMAS messages via the PC5 interface can be a PC5-RRC message; a message transmitted on a sidelink radio bearer designated for SI message forwarding; or a relay discovery message.

[0041] In some implementations, relay UE 104 may filter PWS messages based on the location of remote UE 106. For example, warnings are typically broadcast over a large geographic area (often at the county level in the US) to ensure broad coverage. However, in many cases, such broadcast coverage may be too large because it could include a large number of irrelevant receivers. Additionally, cell tower coverage may overlap in high-density areas, and cell-level broadcasts may not be targeted to specific local areas. Therefore, some implementations describe relay UE 104 utilizing location information about remote UE 106 to facilitate highly localized PWS warnings.

[0042] PWS messages may include information defining a specific alarm area. For example, a PWS message may provide the UE with alarm area coordinates that can be used for geolocation or geofencing. In some implementations, relay UE 104 may include geofencing detection logic that uses the location information and alarm area information of remote UE 106 to trigger the forwarding of geofencing PWS messages to remote UE 106 in a timely and appropriate manner.

[0043] Figure 3 The signaling flow 300 for location-based filtering and forwarding of system information messages is illustrated according to some implementation schemes.

[0044] Signaling flow 300 may include base station 108 periodically transmitting SI broadcasts 304, 308, ... 312, similar to those discussed above.

[0045] At 306, relay UE 104 can acquire location information relative to remote UE 106. In some embodiments, the location information may be based on the nature of the sidelink communication established between relay UE 104 and remote UE 106. For example, relay UE 104 may have some knowledge of the upper limit of the sidelink communication range. It can use this knowledge to determine a rough location of remote UE 106. The upper limit of the sidelink communication range may be based on the technology used for sidelink communication. For example, a wired connection or a short-range wireless connection can ensure that remote UE 106 is relatively close to relay UE 104. In other embodiments, other sidelink positioning or ranging methods may be used. For example, relay UE 104 may derive the relative distance to remote UE 106 based on measurements of sidelink radio quality. Measurements of sidelink radio quality may include, for example, sidelink discovery-reference received signal power (SD-RSRP) or sidelink-reference received signal power (SL-RSRP) measured based on sidelink channel state information. In other implementations, the remote UE 106 may directly provide its location information (e.g., GPS coordinates) to the relay UE 104.

[0046] At 310, the relay UE 104 can receive a paging message for the short message "etwsAndCmasindication". For example, the relay UE 104 can process DCI format 1_0 including CRC scrambled by P-RNTI to determine that "etwsAndCmasindication" is set to "1". After receiving the paging message for the short message "etwsAndCmasindication", the relay UE 104 can receive and decode SI broadcast 312, which may include SIB6, SIB7, or SIB8.

[0047] At 316, relay UE 104 can inspect the ETWS / CMAS segment of SI broadcast 312 and perform a geographic target assessment based on the known location of remote UE 106. For example, the ETWS / CMAS segment may be associated with a specific alarm zone, and relay UE 104 can determine whether remote UE 106 is located within the alarm zone. If remote UE 106 is located within the alarm zone, relay UE 104 can transmit information corresponding to SIB broadcast message 312 in SI container (SI) 320 via the PC5 interface. In some implementations, relay UE 104 may also determine that the ETWS / CMAS message is new and complete before forwarding, similar to the above description relative to... Figure 2 The kind that was discussed.

[0048] In some implementations, when the conditions for geofencing the display of ETWS / CMAS alarms are met, the relay UE 104 can simply forward the alarm to the remote UE 106 as a normal ETWS / CMAS message. The remote UE 106 can then simply display the corresponding alarm without performing further tracing or determining whether the conditions for displaying geofenced ETWS / CMAS alarms are met. This saves power for the remote UE 106.

[0049] While the above implementation describes the filtered forwarding of PWS messages, similar concepts can be applied to forward other types of system information. For example, if relay UE 104 forwards a systemInfoModification indication to remote UE 106, remote UE 106 may not know which system information has been modified. It might then be necessary to send a pleading message for each system information of interest, which could be wasteful and may not even result in new information being provided to remote UE 106. Therefore, some implementations use relay UE 104 as a gating function to forward selected system information messages to remote UE 106. In some implementations, the relay UE may check for updated system information and voluntarily forward all SIBs that have been updated by the network to remote UE 106. This forwarding may optionally be sent along with the system information modification indication. In other implementations, forwarding may be based on the interest expressed by remote UE 106.

[0050] Figure 4 Signaling flow 400, which describes the selective forwarding of system information messages according to some implementation schemes, is illustrated.

[0051] Signaling procedure 400 may include the base station periodically transmitting SI broadcasts 404, 408, ... 412.

[0052] At 406, a remote UE 106, which may be in RRC idle or inactive mode, may provide an SI forwarding register message (SIBx) to a relay UE 104. The SI forwarding register message registers or subscribes to the system information interests of the remote UE 106 with the relay UE 104. In some embodiments, the message may include a full request that includes a complete list of SIBs that the remote UE 106 is interested in and will be forwarded by the relay UE 104. In other embodiments, the message may include an incremental request in which the remote UE 106 only indicates changes from a previously requested change. This message may include one or more SIBs to be added to the interest list associated with the remote UE 106, or it may include one or more SIBs to be removed from the interest list. The relay UE 104 may maintain an interest list (e.g., an SI bitmap) corresponding to each remote UE connected to it and provide relay functionality.

[0053] At 410, the relay UE 104 can receive a paging message regarding systemInfoModification. For example, the relay UE 104 can process DCI format 1_0, including CRC scrambled by P-RNTI, to determine that the systemInfoModification bit is set to "1". After receiving the paging message regarding systemInfoModification, the relay UE 104 can receive and decode SI broadcast 412.

[0054] At 416, relay UE 104 can obtain system information from SI broadcast 412. At 420, relay UE 104 can determine whether any SIBs of interest to remote UE 104 have been updated. If one or more of the interested SIBs have been updated, relay UE 104 can forward the relevant SIBs (generally denoted as SIBx) in SI container (SI) 424.

[0055] In some implementations, the remote UE 106 can send a deregistration message via a sidelink to stop forwarding operations.

[0056] Figure 5 Signaling flow 500, which describes the selective forwarding of system information messages according to some implementation schemes, is illustrated.

[0057] Signaling procedure 500 may include the base station periodically transmitting SI broadcasts 504, 508, ... 512.

[0058] At 510, the relay UE 104 can receive a paging message regarding systemInfoModification. For example, the relay UE 104 can process DCI format 1_0 including CRC scrambled by P-RNTI to determine that systemInfoModification is set to "1". After receiving the paging message regarding systemInfoModification, the relay UE 104 can receive and decode SI broadcast 512.

[0059] At point 516, relay UE 104 can obtain system information from SI broadcast 512. At point 520, relay UE 104 can determine the SIBs that have been updated. At point 524, relay UE 104 can send an SIB update list (x, y, z) that includes a list of SIBs determined to have been updated. The list can simply include the indices of the changed SIBs. For example, a list indicating (x, y, z) can indicate that SIBx, SIBy, and SIBz have changed without providing the SIBs themselves. In some implementations, the SIB update list...

[0060] It can include a list of indices of all SIBs collected / inspected, and can also include whether the corresponding SIB has been...

[0061] Additional instructions for updates. The SIB update list can be a PC5-RRC message.

[0062] In some implementations, it may be assumed that the relay UE 104 has checked every SIB that may have been updated. In other implementations, the relay UE 104 may not need to check all SIBs. Instead, the relay UE 104 may check only a subset of the possible SIBs and may transmit this information about the subset to the remote UE 106. The subset may include SIBs selected based on the interests of the relay UE 104 or some other criterion. The information about the subset transmitted to the remote UE 106 in the SIB update list at 528 may include which SIBs have been updated and which SIBs have not been updated. The relay UE 104 may not have information about SIBs that are not explicitly listed in the information about the subset.

[0063] At 532, the remote UE 106 can determine whether it is interested in any SIBs included in the update list, and if so, trigger an on-demand request. For example, if the remote UE 106 is interested in an SIB (e.g., SIBx) indicated to be updated by the SIB update list, the remote UE 106 can transmit an SI request for the SIB at 536. The relay UE can then respond at 540 via an SI container that includes the updated SIB.

[0064] If the remote UE 106 is interested in an SIB that the relay UE 104 is unaware of, the remote UE 106 may request the relay UE 104 to obtain information related to that SIB. In this case, the relay UE 104 does not indicate whether the SIB has changed or is not in its signaling. Therefore, the update status of the SIB is ambiguous. However, if the remote UE 106 is indeed interested in this SIB, it will initiate a request for this specific SIB as needed, and the relay UE 104 will then obtain and examine that specific SIB. If the SIB has changed, the relay UE will transmit the changed SIB to the remote UE 106.

[0065] If none of the SIBs of interest to the remote UE 106 are updated, the remote UE 106 may not trigger the on-demand procedure.

[0066] If the remote UE 106 in relay UE 104 is always on, the above procedure can reduce signaling overhead, but may be less effective in reducing power consumption for sidelink communication. To further reduce power consumption, relay UE 104 and remote UE 106 can use a specially designed sidelink discontinuous reception (SL-DRX) configuration to coordinate communication. SL-DRX can be used for remote UEs in idle / inactive mode to reduce wake-up time.

[0067] When operating in SL-DRX mode, the remote UE 106 can enter sleep mode for periods when it does not need to listen to the sidelink channel (e.g., by powering down components of its receive circuitry). SL-DRX configuration may include DRX cycling and on-duration periods. The remote UE 106 can wake up during the on-duration period to monitor the PSCCH. After the on-duration period, assuming no wake-up signal is received, the remote UE 106 can return to sleep. DRX cycling defines the length of time between consecutive on-duration periods.

[0068] In some implementations, relay UE 104 and remote UE 106 may use SL-DRX configurations suitable for paging and SI forwarding. Selecting an SL-DRX configuration for paging / SI forwarding may involve considering trade-offs between power efficiency and latency in the forwarded communication. Various implementations describe SL-DRX configurations specifically tailored for paging (e.g., paging SL-DRX), SL-DRX configurations specifically tailored for system information (e.g., SI SL-DRX), or SL-DRX configurations generally applicable to both paging and system information (e.g., paging / SI SL-DRX).

[0069] Figure 6Signaling diagram 600 illustrating paging SL-DRX is provided according to some implementation schemes. The paging SL-DRX configuration can be a unicast DRX configuration specifying the forwarding of paging messages between a relay UE and a remote UE.

[0070] Paging SL-DRX can be configured between relay UE 104 and remote UE 106 based on the paging timing of remote UE 106. For example, during the paging timing of remote UE 106, base station 108 may transmit a mobile termination (MT) paging message for the remote UE at 604. This paging message may be intercepted by relay UE 104. The paging SL-DRX configuration can be set to provide a periodic SL-DRX on-time duration period at a specific time after the paging timing. The time between the paging timing and the SL-DRX on-time duration period can be considered as a delay caused by SL-DRX. Therefore, the SL-DRX configuration can be configured to provide an SL-DRX on-time duration period as close as possible to the reception during the paging timing (e.g., immediately following the reception during the paging timing).

[0071] The start time of the connection duration period can be exactly after the timing of the paging of the remote UE 106 by the relay UE 104. In some implementations, a small offset from the paging timing to the start of the connection duration period can be provided to account for the relay operation of the relay UE 104.

[0072] During the SL-DRX on-time period, for example at 608, relay UE 104 may forward a paging indication from an MT paging message. The paging indication may be transmitted in a PC5-RRC message.

[0073] The DRX cycle of the paging SL-DRX configuration can be set to be equal to the RAN / core network paging cycle of the remote UE. In this way, the on-time duration period can correspond to each paging opportunity to provide the trunk UE 104 with an opportunity to forward the paging indication upon receiving an MT-paging message.

[0074] In some implementations, the paging SL-DRX configuration can be established based on the DRX configuration provided by base station 108. In this way, base station 108 can understand the paging DRX cycle and provide paging messages in a manner that aligns with the call duration.

[0075] Configuring an SL-DRX for forwarding system information messages can be more complex than configuring one for forwarding paging messages. For example, an SI can be a unicast to a specific remote UE or a broadcast / multicast to multiple remote UEs. Therefore, in some implementations, SI SL-DRX configuration may need to be aligned with multiple UEs.

[0076] In another example, for relay UE 104, obtaining updated system information can take longer than it can forward the system information (e.g., SI x) or an indication of an updated SI index (e.g., SI index = x) to remote UE 106. For example, as discussed above, the SI update can occur in a modification cycle after the modification cycle in which the system information modification indication is transmitted. The modification cycle can be a multiple of the default paging cycle, which can result in significant delays. PWS changes via SIB6 / 7 / 8 do not incur modification cycle delays.

[0077] Figure 7 Signaling diagram 700 illustrating SI SL-DRX according to some implementation schemes is provided. SI SL-DRX can be configured for short messages based on P-RNTI and paging loop. The SI SL-DRX configuration can have a DRX loop that matches a modification period, which can be a multiple of the default paging DRX loop. For example, if the network's idle mode DRX loop length is 1.28 seconds, the SI SL-DRX loop used for SI forwarding can be longer than 1.28 seconds toward the remote UE 106, as long as it is within the delay requirements for delivering the SI message.

[0078] Base station 108 may periodically transmit paging messages with system information modifications at 704 and 708. Relay UE 104 may receive the paging messages for short messages transmitted at 704. Then, relay UE 104 may forward an SI message (which may include the SI or an indication of an updated SI) at 712 during the next SL-DRX on-call duration. The SI message may be forwarded in a PC5-RRC message.

[0079] A long DRX cycle length configured in the SI SL-DRX configuration can result in a relatively long delay between receiving a paging message for a short message at 704 and forwarding the SI at 712. In some cases, this delay can be longer than the paging cycle. The trunk UE 104 can use this delay to obtain the updated SI, and the SI forwarding message can be based on this updated SI. The start time of the on-duration period can be set to the expected time to obtain the updated SIB in each modification period.

[0080] Given that SL-DRX can be statically configured, these implementations may be most useful if the time when the relay UE 104 will receive the updated SI can be predetermined. For example, this could be based on a mechanism used for replaying fixed SIBs.

[0081] In some cases, it may be difficult to predict which SIBs will be changed and when an updated SI will be received. Therefore, some implementations describe a paging / SI SL-DRX configuration with a DRX loop to accommodate paging and SI forwarding. This can be used in sidelink unicast scenarios where the SL-DRX is used by a single remote UE and a trunk UE.

[0082] In some implementations, a shorter DRX cycle for paging and a longer DRX cycle for SI can be combined into a single short DRX cycle. The relay UE 104 can be configured with only one SL-DRX cycle, which has an on-time duration suitable for delivering both paging and SI forwarding to the remote UE 106.

[0083] The SL-DRX cycle can monitor the paging and SI frequencies based on the frequency used by the relay UE 104. The paging frequency can be derived from the idle mode DRX cycle used by the relay UE 104 to intercept paging from the remote UE 106. The SI frequency can be derived from a modified cycle corresponding to a frequency that may change in SI. The SL-DRX configured uptime period can be based on the paging timing of the remote UE 106. For example, the uptime period can be set immediately (or shortly after) after the paging timing to deliver paging to the remote UE 106 with almost no delay.

[0084] When relay UE 104 receives a paging message, ETWS / CMAS message, or an SIB message associated with remote UE 106, relay UE 104 may deliver the information during the next available connection duration. The SL-DRX cycle can be configured to ensure that the SI message is still delivered in a timely manner. For example, CMAS messages may be delivered within four seconds according to government regulations, but the SL-DRX cycle can be configured to be much shorter. For example, the SL-DRX cycle can be configured to match Uu paging cycles of, for example, 320ms, 640ms, 1.28s, or 2.56s. As long as the SL-DRX cycle is less than 4 seconds, further optimization for ETWS / CMAS delivery delays may not be necessary.

[0085] Some implementations may offer additional measures to ensure more timely delivery of system information rather than waiting for the next call duration cycle, while still considering the trade-off between latency and power consumption. Some implementations can provide timely SI forwarding by utilizing an additional one-time wake-up cycle (active time), which can be indicated during the call duration cycle of a normal paging / SI DRX cycle. The active time for SI forwarding can be based on a predicted time, where relay UE 104 can retrieve the latest ETWS / CMAS or modified SIB registered by remote UE 106 (assuming at least one of those SIBs will be delivered to remote UE 106).

[0086] Figure 8 Signaling diagram 800 is provided, illustrating the use of SL-DRX for SI forwarding based on some implementation schemes.

[0087] At position 804, remote UE 106 can transmit SI forwarding register messages to relay UE 104. SI forwarding register messages can be similar to those described above relative to... Figure 4 The SI forwarding register message 406 is described.

[0088] At 808, relay UE 104 can receive paging messages with system information modification instructions for short messages.

[0089] Then, the relay UE 104 may generate an SL configuration message 812 during the SL-DRX on-time and transmit it to the remote UE 106. The SL configuration message 812 can configure the active time for SI forwarding. In some implementations, this active time for SI forwarding can be dynamically configured by the relay UE 104 as needed. For example, the relay UE 104 may only enable this if ETWS / CMAS is detected in a short message and may not enable it if PWS broadcasting stops.

[0090] Signaling diagram 800 may also include relay UE 104 receiving SI broadcast message 816 from base station 108. At 820, relay UE 104 obtains the SI that has been updated in the next modification cycle. Relay UE 104 may check the updated SIBs to determine at 824 whether remote UE 106 is interested in any of them. If the remote UE is interested in one or more updated SIBs (e.g., SIBx), relay UE 104 may forward them to remote UE 106 in SI container 828 during the active time for SI forwarding.

[0091] If relay UE 104 does not detect any updated SIB of interest at 824, it may not deliver anything to remote UE 106 during the active time period used for SI forwarding.

[0092] The mechanism for an active time can be triggered again if a message has not been successfully delivered due to any failure in SI retrieval in the Uu interface or SI forwarding via the PC5 interface. In this case, for example, if the SI is not ready to be forwarded on the PC5 interface during the first active time, the second active time in the PC5 interface is scheduled based on the latest estimated time of the relay UE used to enable the relay UE to forward the SIB to the remote UE.

[0093] Figure 9An operation flow / algorithm structure 900 is provided according to some implementation schemes. The operation flow / algorithm structure 900 can be executed / implemented by a UE (such as, for example, relay UE 104, UE 1200) or its components (such as processor 1204).

[0094] The operation flow / algorithm structure 900 may include, at 904, decoding of the PWS message based on the PWS indication. The PWS indication may be received in DCI format 1_0 with its CRC scrambled via P-RNTI. The PWS indication may indicate a change relative to the ETWS primary notification transmitted in SIB6, the ETWS secondary notification transmitted in SIB7, or the CMAS notification transmitted in SIB8. The PWS message may be an SI message including SIB6 / 7 / 8. In some embodiments, the PWS message may be received as multiple segments.

[0095] The operation flow / algorithm structure 900 may also include generating a filtered PWS message at 908. In some implementations, a filtered PWS message can be generated by examining segments of the PWS message received at 904. A filtered BWS message can then be generated from the complete set of segments of the PWS message, where duplicate and out-of-order segments have been removed.

[0096] In some implementations, PWS message filtering can be further based on the location of the remote UE. For example, PWS messages associated with alarm areas that do not include the location of the remote UE can be filtered out and not forwarded to the remote UE.

[0097] The operation flow / algorithm structure 900 may also include, at 912, forwarding filtered PWS messages to the remote UE via the side link interface. In some implementations, filtered PWS messages may be transmitted in an SI container that includes PC5-RRC messages, relay discovery messages, or messages transmitted on an SLRB dedicated to SI message forwarding.

[0098] Figure 10 An operation flow / algorithm structure 1000 is provided according to some implementation schemes. The operation flow / algorithm structure 1000 can be executed / implemented by a UE (such as, for example, relay UE 104, UE 1200) or its components (such as processor 1204).

[0099] The operation flow / algorithm structure 1000 may include, at 1004, receiving an SI modification instruction. The SI modification instruction may be received in DCI format 1_0 with its CRC scrambled via P-RNTI. The SI modification instruction may indicate changes to the BCCH content other than SIB6 / 7 / 8.

[0100] The operation flow / algorithm structure 1000 may also include, at 1008, identifying one or more SIBs that have been updated. To identify updated SIBs, the relay UE can acquire and examine the set of SIBs to determine whether they have been updated.

[0101] The operation flow / algorithm structure 1000 may further include, at 1012, transmitting an indication of one or more SIBs to the remote UE. In some embodiments, the indication may be a list identifying SIBs that have been updated. In some embodiments, the indication may also include a list identifying SIBs that have not yet been updated. The updated list and the unupdated list may correspond to the set of SIBs acquired and checked at 1008.

[0102] After transmitting the list of identified updated SIBs, the relay UE can receive a request for one or more updated SIBs from the remote UE. The relay UE can then respond with the requested information.

[0103] Figure 11 An operation flow / algorithm structure 1100 is provided according to some implementation schemes. The operation flow / algorithm structure 1100 can be executed / implemented by a UE (such as, for example, relay UE 104, UE 1200) or its components (such as processor 1204).

[0104] The operational flow / algorithm structure 1100 may include, at 1104, configuring the SL-DRX for paging or SI forwarding. The SL-DRX configuration may be based on the periodicity of paging or SI update messages from the network. In some implementations, the SL-DRX may be specifically configured for paging, specifically configured for SI forwarding, or configured to accommodate both paging and SI forwarding.

[0105] The operation procedure / algorithm structure 1100 may also include receiving a message from the base station at 1108. The message may be a paging message including a paging indication or an SI message including updated SI content.

[0106] The operation flow / algorithm structure 1100 may also include, at 1112, transmitting information to the remote UE during the SL-DRX's on-time duration. The information may be based on a message received from the base station at 1108. For example, the information may be a paging indication, an updated SIB, or an indication that one or more SIBs have been updated.

[0107] Figure 12 UE 1200 is shown according to some implementation schemes. UE 1200 may be similar to or interchangeable with relay UE 104 or remote UE 106.

[0108] The UE 1200 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, stock sensor, voltmeter / ammeter, or actuator), video surveillance / monitoring device (e.g., camera or camcorder), wearable device (e.g., smartwatch), or Internet of Things device.

[0109] UE 1200 may include a processor 1204, RF interface circuitry 1208, memory / storage device 1212, user interface 1216, sensor 1220, drive circuitry 1222, power management integrated circuit (PMIC) 1224, antenna structure 1226, and battery 1228. Components of UE 1200 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 12 The block diagram is intended to show a high-level view of some of the components of the UE 1200. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0110] Components of UE 1200 can be coupled to various other components via one or more interconnects 1232, which can represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, or optical connector, allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0111] Processor 1204 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 1204A, central processing unit circuitry (CPU) 1204B, and graphics processing unit circuitry (GPU) 1204C. Processor 1204 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 1212) to cause UE 1200 to perform the operations described herein.

[0112] In some implementations, the baseband processor circuit 1204A can access the communication protocol stack 1236 in the memory / storage device 1212 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1204A can access the communication protocol stack 1236 to perform the following operations: user plane functions at the PHY, MAC, RLC, PDCP, and SDAP layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and NAS layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 1208.

[0113] The baseband processor circuit 1204A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0114] Memory / storage device 1212 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 1236) that can be executed by one or more processors in processor 1204 to cause UE 1200 to perform the various operations described herein. Memory / storage device 1212 includes any type of volatile or non-volatile memory that can be distributed throughout UE 1200. In some embodiments, some memory / storage devices in memory / storage device 1212 may be located on processor 1204 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 1212 may be located external to processor 1204 but accessible via a memory interface. Memory / storage device 1212 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0115] RF interface circuitry 1208 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows UE 1200 to communicate with other devices via a radio access network. RF interface circuitry 1208 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0116] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 1226 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 1204.

[0117] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 1226.

[0118] In various implementations, the RF interface circuit 1208 can be configured to transmit / receive signals in a manner compatible with NR and sidelink access technologies.

[0119] Antenna 1226 may include antenna elements to convert electrical signals into radio waves for propagation through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 1226 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 1226 may include: a microstrip antenna; a printed antenna fabricated on the surface of one or more printed circuit boards; a patch antenna; or a phased array antenna. Antenna 1226 may have one or more panels designed for a specific frequency band, including the frequency bands in FR1 or FR2.

[0120] User interface circuitry 1216 includes various input / output (I / O) devices designed to enable users to interact with UE 1200. User interface 1216 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 1200.

[0121] Sensor 1220 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, or subsystems. Examples of such sensors include: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other similar audio capture devices.

[0122] The driving circuit 1222 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1200. The driving circuit 1222 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 1200. For example, the driving circuit 1222 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for obtaining sensor readings from the sensor circuit 1220 and controlling and allowing access to the sensor circuit 1220; a driver for obtaining actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0123] The PMIC 1224 manages the power supplied to various components of the UE 1200. In particular, relative to the processor 1204, the PMIC 1224 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0124] Battery 1228 can power UE 1200, but in some examples, UE 1200 may be mounted in a fixed location and may have a power source coupled to the mains. Battery 1228 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 1228 may be a typical lead-acid automotive battery.

[0125] Figure 10 A base station 1000 according to some embodiments is shown. Base station 1000 may be similar to base station 108 and is substantially interchangeable with it.

[0126] Base station 1000 may include processor 1004, RF interface circuit 1008 (if implemented as a base station), core network (CN) interface circuit 1012, memory / storage device circuit 1016 and antenna structure 1026 (if implemented as a base station).

[0127] The components of base station 1000 can be coupled to various other components via one or more interconnects 1028.

[0128] The processor 1004, RF interface circuit 1008, memory / storage device circuit 1016 (including communication protocol stack 1010), antenna structure 1026, and interconnect 1028 can be similar to those described above. Figure 8 Similar named elements are shown and described.

[0129] The CN interface circuit 1012 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol (such as Carrier Ethernet) or some other suitable protocol). Network connectivity can be provided to / from base station 1000 via fiber optic or wireless backhaul. The CN interface circuit 1012 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN controller circuit 1012 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0130] In some implementations, base station 1000 may be coupled to transmit-receive point (TRP) using antenna structure 1026, CN interface circuitry or other interface circuitry.

[0131] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0132] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, or network element described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0133] Example

[0134] Further exemplary implementations are provided in the following sections.

[0135] Example 1 includes a method for operating a relay user equipment (UE), the method comprising: establishing sidelink communication with a remote UE; receiving a common warning system (PWS) indication in downlink control information (DCI); decoding a common warning system (PWS) message based on the PWS indication; generating a filtered PWS message based on the PWS message; and forwarding the filtered PWS message to the remote UE.

[0136] Example 2 includes the method according to Example 1 or some other embodiments herein, wherein the PWS message includes system information having a System Information Block (SIB) 6, SIB 7 or SIB 8.

[0137] Example 3 includes the method according to Example 1 or some other embodiments herein, wherein generating the filtered PWS message includes: removing content previously forwarded to the remote UE from the PWS message.

[0138] Example 4 includes the method according to Example 1 or some other embodiments herein, further comprising: decoding the PWS message to obtain a first plurality of segments; and generating the filtered PWS message by generating a second plurality of segments through removing duplicate and out-of-order segments from the first plurality of segments.

[0139] Example 5 includes the method described according to Example 4 or some other embodiments herein, further comprising: forwarding the filtered PWS message based on determining that the second plurality of segments includes a complete set of segments.

[0140] Example 6 includes the method according to Example 1 or some other embodiments herein, wherein forwarding the filtered PWS message includes: generating a system information (SI) container including the filtered PWS message; and transmitting the SI container to the remote UE via a sidelink channel.

[0141] Example 7 includes the method according to Example 6 or some other embodiments herein, wherein the SI container includes PC5 radio resource control messages; relay discovery messages; or messages transmitted on a sidelink radio bearer (SLRB) dedicated to SI message forwarding.

[0142] Example 8 includes the method according to Example 1 or some other embodiments herein, wherein the PWS message includes information for defining an alarm region and the method further includes: determining the location of the remote UE within the alarm region; and generating a filtered PWS message without the information for defining the alarm region.

[0143] Example 9 includes the method according to Example 8 or some other embodiments herein, wherein determining the location of the remote UE includes: determining an upper limit of the range of the sidelink communication; or determining the proximity of the remote UE based on sidelink radio quality measurements.

[0144] Example 10 includes a method for operating a relay user equipment (UE), the method comprising: establishing sidelink communication with a remote UE; receiving a system information (SI) modification indication in downlink control information (DCI); identifying one or more system information blocks (SIBs) that have been updated; and transmitting an indication of the one or more SIBs to the remote UE.

[0145] Example 11 includes the method according to Example 10 or some other embodiments herein, wherein identifying the one or more SIBs that have been changed includes: acquiring and inspecting a set of SIBs based on the SIB modification indication; and identifying the one or more SIBs that have been updated based on the acquired and inspected set of SIBs.

[0146] Example 12 includes the method according to Example 10 or some other embodiments herein, wherein transmitting the instruction includes transmitting a list of indexes of the one or more SIBs that have been updated.

[0147] Example 13 includes the method according to Example 10 or some other embodiments herein, further comprising: receiving from the remote UE a request for an updated SIB selected from the one or more SIBs; and transmitting the updated SIB to the remote UE based on the request.

[0148] Example 14 includes the method according to Example 10 or some other embodiments herein, further comprising: transmitting to the remote UE an index list of SIBs for update checking based on the SI modification indication and an additional indication as to whether each of the SIBs has been updated.

[0149] Example 15 includes the method according to Example 14 or some other embodiments herein, further comprising: receiving from the remote UE an indication of interest not included in the SIBs in the list; checking the SIB to determine whether it has been updated; and transmitting to the remote UE a message resulting in the checking of the SIB.

[0150] Example 16 includes a method for operating a relay user equipment (UE), the method comprising: establishing sidelink communication with a remote UE; establishing a sidelink discontinuous reception (SL-DRX) configuration for communicating with the remote UE based on a paging timing used by the network to paging the remote UE; receiving a paging message for the remote UE from a base station; and transmitting a paging indication to the remote UE based on the paging message during the on-duty period of the SL-DRX configuration.

[0151] Example 17 includes the method described according to Example 16 or some other embodiments herein, wherein the SL-DRX configuration is established based on the DRX configuration provided by the base station.

[0152] Example 17 includes the method described according to Example 16 or some other embodiments herein, wherein the SL-DRX configuration includes a DRX cycle equal to the paging cycle of the base station.

[0153] Example 18 includes the method according to Example 16 or some other embodiments herein, wherein the SL-DRX is a paging SL-DRX configuration and the method further includes: determining a system information (SI) SL-DRX configuration; receiving an SI update from the network during a modification period; and transmitting an SI update message to the remote UE during an on-duration period of the SI SL-DRX configuration.

[0154] Example 19 includes the method according to Example 18 or some other embodiments herein, wherein transmitting the SI update message further includes: transmitting the SI update message to multiple remote UEs as a multicast or broadcast message.

[0155] Example 20 includes the method according to Example 18 or some other embodiments herein, wherein the SI SL-DRX configuration includes a DRX cycle corresponding to the modification period.

[0156] Example 21 includes a method for operating a relay user equipment (UE), the method comprising: establishing sidelink communication with a remote UE; establishing a sidelink discontinuous reception (SL-DRX) configuration for communicating with the remote UE based on periodic paging or system information (SI) update messages from the network; receiving paging or SI update messages; and transmitting information to the remote UE based on the paging or SI update messages during the on-duty period of the SL-DRX configuration.

[0157] Example 22 includes the method according to Example 20 or some other embodiments herein, further comprising: generating a sidelink configuration message to enable an active time for SI forwarding; transmitting the sidelink configuration message during a third on-time of the SL-DRX configuration; detecting an update of a system information block of interest to the remote UE; and transmitting the system information block during the active time for SI forwarding.

[0158] Example 23 includes a method of operating a remote user equipment (UE), the method comprising: receiving from a relay UE a list of updated system information blocks (SIBs); transmitting a system information (SI) request to the relay UE to request SIBs selected from the list of updated SIBs; and receiving the SIBs from the relay UE.

[0159] Example 24 includes the method according to Example 23 or some other embodiments herein, wherein the SIB is a first SIB and the method further includes: receiving additional information from the relay UE to determine that a second SIB of interest to the remote UE has an ambiguous update status; transmitting a request to the relay UE to obtain and inspect the second SIB; and if the second SIB is updated, receiving the second SIB from the relay UE.

[0160] Example 25 may include an apparatus comprising means for performing one or more elements of the method described or associated with any of Examples 1 to 24 or any other method or process described herein.

[0161] Example 26 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein, as described or associated with any of Examples 1 to 24.

[0162] Example 27 may include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of the method described or associated with any of Examples 1 to 24 or any other method or process described herein.

[0163] Example 28 may include the methods, techniques, or processes described or associated with any of Examples 1 to 24, or parts or components thereof.

[0164] Example 29 may include an apparatus comprising one or more processors and one or more computer-readable media, the instructions of which, when executed by the one or more processors, cause the one or more processors to perform the methods, techniques or processes or portions thereof described or associated with any of Examples 1 to 24.

[0165] Example 30 may include the signal described or associated with any of Examples 1 to 24, or a portion or component thereof.

[0166] Example 31 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or otherwise in this disclosure, according to any of Examples 1 to 24.

[0167] Example 32 may include a signal encoded with data, or a portion or component thereof, as described or associated with any of Examples 1 to 24, or otherwise described in this disclosure.

[0168] Example 33 may include a signal, or a portion or component thereof, encoded as a datagram, IE, packet, frame, segment, PDU, or message, as described or associated with any of Examples 1 to 24, or otherwise described in this disclosure.

[0169] Example 34 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1 to 24.

[0170] Embodiment 35 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process, or a portion thereof, as described or associated with any of Embodiments 1 to 24.

[0171] Example 36 may include signals in a wireless network as shown and described herein.

[0172] Example 37 may include methods for communicating in a wireless network as shown and described herein.

[0173] Example 38 may include a system for providing wireless communication as shown and described herein.

[0174] Example 39 may include a device for providing wireless communication as shown and described herein.

[0175] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0176] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. One or more computer-readable media, said one or more computer-readable media having instructions that, when executed, cause a relay user equipment (UE) to perform the following operations: Receives a message from a remote UE including a list of interests for one or more System Information Blocks (SIBs) requesting updates, wherein the remote UE is in Radio Resource Control (RRC) idle or inactive mode; Obtain the SIB from the one or more SIBs from the base station; Forward the SIB to the remote UE; Receive a deregistration message from the remote UE; as well as The forwarding of SIBs in the interest list is stopped based on the cancellation message.

2. The computer-readable medium of claim 1, wherein the interest list is a first interest list, and wherein the instructions, when executed, further cause the relay UE to: Add one or more SIBs from the first interest list to the second interest list of SIBs stored at the relay UE; and Monitor updates to the second list of interests for SIB.

3. The computer-readable medium of claim 1, wherein the list of interests corresponds to an incremental request that includes changes to one or more previous requests.

4. The computer-readable medium of claim 1, wherein the instructions, when executed, further cause the relay UE to: It has been determined that the SIB has been updated; and Based on the determination that the SIB has been updated, the SIB is transmitted to the remote UE.

5. The computer-readable medium of claim 4, wherein the instructions, when executed, further cause the relay UE to: Receive system information (SI) modification instructions in the downlink control information (DCI); and The SI modification instruction determines that the SIB has been updated.

6. An apparatus to be implemented in a remote user equipment (UE), the apparatus comprising circuitry configured to: Identify multiple System Information Blocks (SIBs) for which requests were not previously sent to the relay UE; Generate a message to be transmitted to the relay UE, including a list of the plurality of SIBs requesting updates; The message is transmitted to the relay UE; Receive the SIB from the one or more SIBs from the relay UE; as well as A deregistration message is generated to be sent to the relay UE, the deregistration message causing the relay UE to stop forwarding the SIBs in the list to the remote UE.

7. The apparatus of claim 6, wherein the circuitry is configured to transmit the message to the relay UE when the remote UE is in a Radio Resource Control (RRC) idle or inactive state.

8. A method for operating a relay device, the method comprising: Receives a message from a remote user equipment (UE) including a list of interests for one or more System Information Blocks (SIBs) requested for updating, wherein the remote UE is in Radio Resource Control (RRC) idle or inactive mode; Receive one or more SIBs from the base station; Forward the SIB to the remote UE; Receive a deregistration message from the remote UE; as well as The forwarding of SIBs in the interest list is stopped based on the cancellation message.

9. The method of claim 8, wherein the interest list is a first interest list and the method further comprises: Add one or more SIBs from the first interest list to the second interest list of SIBs stored at the relay device; as well as Monitor updates to the second list of interests for SIB.

10. The method of claim 9, wherein the first interest list corresponds to an incremental request that includes changes to one or more previous requests.

11. The method of claim 8, further comprising: It has been determined that the SIB has been updated; as well as Based on the determination that the SIB has been updated, the SIB is transmitted to the remote UE.

12. The method of claim 11, further comprising: Receive system information (SI) modification instructions in the downlink control information (DCI); as well as The SI modification instruction determines that the SIB has been updated.

Images