Hybrid automatic repeat request (HARQ) process for sidelink operating in unlicensed band
By introducing multiple PSFCH transmission opportunities and autonomous PSFCH transmission in the NR-U system, combined with the new PSFCH format, the transmission delay and low channel occupation efficiency of the NR-U SL communication system in the non-licensed frequency band are solved, and the further improvement is achieved Efficient SL data transmission and meeting regulatory requirements.
Patent Information
- Application Number
- CN202380028244.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-09-16
- Filing Date
- 2023-04-21
- Publication Date
- 2024-12-03
AI Technical Summary
NR-U SL communication systems operating in unlicensed frequency bands face challenges, including transmission delays in frequency range-1 and low channel occupancy efficiency, and prior art is difficult to meet regulatory requirements and improve SL data rates in different regions.
By introducing multiple PSFCH transmission opportunities and autonomous PSFCH transmission in NR-U, 1-to-many mapping of PSFCH with PSCCH/PSSCH resources is allowed, the HARQ process is enhanced to improve spectral efficiency and channel utilization, and a new PSFCH format is defined to carry Multiple TB of HARQ-ACK information.
It realizes more efficient SL transmission in the non-licensed frequency band, improves channel occupancy efficiency and data rate, meets the regulatory requirements of different regions, and supports HARQ-ACK feedback for multi-slot and multi-TB transmission.
Smart Images

Figure CN119072874A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to the following applications: U.S. Provisional Patent Application No. 63 / 333,989 filed on April 22, 2022; U.S. Provisional Patent Application No. 63 / 352,856 filed on June 16, 2022; and U.S. Provisional Patent Application No. 63 / 407,384 filed on September 16, 2022. Technical Field
[0003] Various embodiments may generally relate to the field of wireless communications. For example, some embodiments may relate to sidelink (SL) operations in unlicensed bands. Background Art
[0004] Various embodiments may generally relate to the field of wireless communications. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] The embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To aid this description, similar reference numerals designate similar structural elements. The embodiments are illustrated in the accompanying drawings by way of example and not by way of limitation.
[0006] Figure 1 An example of a SL mode of operation in an unlicensed spectrum is illustrated according to various embodiments.
[0007] Figure 2 Illustrated are examples of (one or more) one-to-many mappings between Physical SL Control Channel (PSCCH) / Physical SL Shared Channel (PSSCH) resources and Physical SL Feedback Channel (PSFCH) resource opportunities according to various embodiments.
[0008] Figure 3 An example of a one-to-many mapping (one or more) from PSCCH / PSSCH slots to PSFCH opportunities is illustrated according to various embodiments.
[0009] Figure 4 An example of PSFCH resource determination for multiple transport block (TB) scheduling according to various embodiments is illustrated.
[0010] Figure 5 A wireless network according to various embodiments is schematically illustrated.
[0011] Figure 6 Components of a wireless network according to various embodiments are schematically illustrated.
[0012] Figure 7The block diagram illustrates components capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein according to some example embodiments.
[0013] Figure 8 A network according to various embodiments is illustrated.
[0014] Fig. 9 Depicted are example procedures for implementing the various embodiments discussed herein.
[0015] Fig.10 Another example process for implementing the various embodiments discussed herein is depicted. DETAILED DESCRIPTION
[0016] The following detailed description refers 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 specific structures, architectures, interfaces, technologies, etc. are recorded for illustration rather than limitation to provide a thorough understanding of various aspects of various embodiments. However, it will be clear to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments may be implemented in other examples that are separated from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted to avoid blurring the descriptions of various embodiments with unnecessary details. For this document, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).
[0017] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated integrated communications platforms. The next generation of wireless communications systems, which may be referred to as fifth generation (5G) and / or new radio (NR), may provide access to information and sharing of data by a variety of users and applications anywhere, at any time. NR may be viewed as a unified network / system that can meet very different and sometimes conflicting performance dimensions and services. This diverse multi-dimensional requirement may be driven by factors such as different services and applications.
[0018] For example, in the third generation partnership project (3GPP) Release 16 (which may be referred to as Rel. 16, Rel 16, Rel-16, etc.) specifications, SL communications are developed at least in part to support advanced vehicle-to-anything (V2X) applications. In the 3GPP Release 17 (which may be referred to as Rel. 17, Rel 17, Rel-17, etc. in this article), 3GPP studies and standardizes proximity-based services, including public safety and business-related services. In addition, as part of Rel. 17, power saving solutions (e.g., partial sensing, discontinuous reception (DRX), etc.) and inter-UE coordination are developed to at least partially improve the power consumption of battery-limited terminals and the reliability of SL transmissions. Although NR SL may have been initially developed for V2X applications, the industry is increasingly interested in extending the applicability of NR SL to commercial use cases such as sharing of sensor information (video) between vehicles with high levels of driving automation. For a commercial SL application, two example requirements might be as follows:
[0019] - Increase SL data rate
[0020] -Support new carrier frequencies for SL.
[0021] To achieve these requirements, one goal of the 3GPP Release 18 (referred to herein as Rel. 18, Rel-18, Rel18, etc.) specification is to extend SL operation in unlicensed spectrum, which may be referred to as NR-U SL in the remainder of this disclosure. However, in order to allow fair use of spectrum and fair coexistence between different technologies, different regional regulatory requirements are imposed around the world. Thus, in order to be able to implement a solution that is applicable to all regions, it may be sufficient to comply with the most stringent regulations from the European Telecommunications Standards Institute (ETSI) Broadband Radio Access Network (BRAN) Committee, for example as published in European Standard (EN) 301 893. In fact, for the development of NR-U during Rel. 16, a 3GPP NR-based system that complies with these regulations has been developed.
[0022] However, given that one goal may be to enable SL communication systems in unlicensed bands, it may be necessary to combine considerations for SL communication systems with regulatory requirements necessary for operation in unlicensed bands. For example, NR SL may be operated in two operating modes: 1) Mode 1, in which a base station (e.g., gNodeB (gNB)) schedules (one or more) SL transmission resources for use by UEs, and Uu operations are limited to licensed spectrum; and / or 2) Mode 2, in which the user equipment (UE) determines (i.e., the gNB does not schedule) (one or more) SL transmission resources within the SL resources configured or pre-configured by the gNB / network. Figure 1 Examples of two modes of operation are illustrated.
[0023] In this scenario, there are several specific challenges in enabling NR-U SL. Specifically, one of the challenges is that when operating in an unlicensed band in frequency range-1 (FR-1, which may refer to frequencies equal to or below about 7 gigahertz (GHz), or in some embodiments, frequencies equal to or below about 6 GHz), a listen before talk (LBT) process may need to be performed to acquire the medium before transmission can occur, which may be performed at any time to significantly improve overall system performance, and also requires that SL transmission be started soon thereafter so that the channel can be immediately seized.
[0024] Another feature when operating in unlicensed spectrum is that the channel acquired by the device can be shared with other devices (e.g., between user equipment (UE) and base stations such as gNodeB (gNB)) to allow more efficient use of channel occupancy time (COT). In addition, ETSI BRAN also specifies that at least 80% of the nominal channel bandwidth should be occupied at all times, as explained by the following text:
[0025]
[0026] To meet these requirements, NR-U, licensed assisted access (LAA) and MulteFire adopt interleaved physical resource block (PRB) mapping, called interleaved mapping, which can be applied to physical uplink control channel (PUCCH) and / or physical uplink shared channel (PUSCH). More importantly, for synchronization signals, the concept of Discovery Reference Signal (DRS) can be used, which can include synchronization signal (SS) / physical broadcast channel (PBCH) transmission and optionally non-zero power (NZP) channel state information (CSI)-reference signal (RS), physical downlink shared channel (PDSCH) transmission related to system information block 1 (SIB1), and / or associated physical downlink control channel (PDCCH) transmission.
[0027] In addition, ETSI BRAN may also define a specific class of signals, called short control signaling, which can be transmitted without any LBT or under specific LBT exceptions. As described in the following text, a short control signal can be a signal that is transmitted no more than 50 times in any observation window of 50 milliseconds (ms), and its aggregate transmission cannot exceed 2.5ms in any observation window:
[0028]
[0029] In this sense, in NR-U, the demodulation reference signal (DRS) may be the only signal that qualifies as short control signaling, and in this sense, base stations such as gNBs may be allowed to transmit this type of signal by acquiring the channel using Type 2A channel access instead of using Type 1 LBT.
[0030] In Rel.16NR SL, different hybrid automatic repeat request (HARQ) processes for unicast / multicast and broadcast operations may be defined, and these processes may rely on a physical SL feedback channel (PSFCH), which may be reliably sent and received. However, when operating in unlicensed spectrum, the transmission of the PSFCH may be conditional on the success of the associated LBT process. In addition, when operating in unlicensed spectrum, in order to improve spectral efficiency and utilization of the COT, the UE may be allowed to transmit long SL transmissions, which may far exceed a single SL slot in Rel.16SL. In view of this, it may be necessary to enhance the Rel.16SL HARQ process, and various design considerations and options may be described in this article.
[0031] The time relationship between PSFCH and triggering PSCCH / PSSCH
[0032] Due to potential LBT failures, fixing the timing relationship between the triggered PSCCH / PSSCH and the corresponding PSFCH as in the Rel.16SL design, which is intended to operate in licensed spectrum, may not be efficient. Specifically, for SL systems operating in unlicensed spectrum, it may be very beneficial to consider a process that allows multiple PSFCH transmission opportunities and / or self-sufficient / autonomous PSFCH transmissions that do not require 1:1 mapping with the triggered PSCCH / PSSCH resources. In this matter, multiple embodiments are provided below in the present disclosure.
[0033] In one embodiment, Figure 2 As shown in , multiple PSFCH transmission opportunities are configured, are fixed, or can be (pre)configured in the resource pool configuration. Figure 2 As shown, for a given PSCCH / PSSCH, the UE has four opportunities to perform LBT and transmit the corresponding PSFCH. Note that in one embodiment, this may only apply to unicast communications, only apply to multicast communications, or in the case of both, as another different option, it may also additionally include broadcast communications.
[0034] In this alternative, it is assumed that the PSCCH / PSSCH transmission resources have a one-to-many mapping with the PSFCH resources in the time domain. Multiple PSFCH transmission occasions may be in different time slots, or in different symbols of the same time slot, or a combination of the two schemes. In one embodiment, sl-PSFCH-Period-r16 or periodPSFCHresource may indicate the rhythm of the PSFCH occasion relative to the PSCCH / PSSCH resource, while another parameter indicates the number of PSFCH opportunities based on each PSCCH / PSSCH resource. In this case, it can also be ensured that the resources of each PSFCH transmission opportunity in the one-to-many mapping are orthogonal to the one-to-many mapping of any other transmission. This can be ensured by (pre)configuring different resources depending on whether it is the nth transmission opportunity.
[0035] The redundancy order of R can be used to control overhead, where R=1 means a single PSFCH opportunity and R>1 means multiple PSFCH opportunities. R can be fixed or (pre)configurable for each resource pool. In addition, in one option, multiple PSFCH transmission opportunities may only be located within a shared COT, or may be allowed to span different COTs. In addition, transport block (TB) bundling of order L can be used to further control overhead, where L=1 means that each PSFCH refers to the HARQ feedback of a single TB, and L>1 means that the hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback of multiple TBs is bundled in a single PSFCH indication, where L can be fixed or (pre)configurable per resource pool. In one option, bundling is applied in such a way that if all TBs are received, ACK is reported in the PSFCH, and if at least one TB is not received, NACK (which can be a non-acknowledgement or a negative acknowledgment) is reported. In a different option, bundling is applied in such a way that an ACK is reported in the PSFCH if at least one TB is received, and a NACK is reported if not all TBs are received.
[0036] Additionally, in one option, multiple PSFCH transmission opportunities may be located only within a shared COT, or may be allowed to span different COTs.
[0037] A given PSFCH opportunity may correspond to >1 transport block. In this case, in one embodiment, the same parallel PSFCH transmission scheme may be used, or alternatively, a new multi-bit HARQ codebook design may be used, where PSFCH may carry HARQ-ACK information for multiple TBs for the same UE or different UEs.
[0038] Figure 3 A comparison example is provided between the traditional Rel.16SL HARQ process (which is based on a 1:1 mapping between triggered PSCCH / PSSCH transmissions and the corresponding PSFCH) and the new HARQ scheme defined for SL operating in unlicensed spectrum (which is based on a one-to-many mapping between PSCCH / PSSCH time slots and PSFCH opportunities).
[0039] In one embodiment, one or more PSFCH opportunities are (pre)configured or fixed. In another option, one or more PSFCH opportunities associated with a particular PSSCH are dynamically indicated in SL control information (SCI) (e.g., Phase 1 or Phase 2 or both) with respect to the time interval between the time of transmission of the corresponding PSSCH and the time slot in which the relevant PSFCH opportunity may occur, where the granularity may be symbol level or time slot level. In another option, the indication of one or more PSFCH opportunities may be a combination of higher layer (pre)configuration and SCI indication.
[0040] In one embodiment, if the PSFCH resource cannot be transmitted within the same COT as the corresponding PSSCH, the PSFCH is discarded. In this case, the UE can then obtain a new COT and trigger a retransmission in the next available COT.
[0041] In one embodiment, if the PSFCH resource cannot be transmitted due to LBT failure, the HARQ-ACK information is transmitted on the subsequent PSSCH via the medium access control (MAC)-control element (CE). In this case, the currently reserved eight-bit byte can be used to carry one or more HARQ-ACK bits: in one option, N bits are transmitted, corresponding to the available N HARQ identifiers (IDs), and for (one or more) HARQ-IDs not configured for the UE, the UE can indicate ACK or NACK.
[0042] In one embodiment, a new PSFCH format may be defined, such as PSFCH format 1, which may be used to carry HARQ-ACK information for multiple TBs for the same UE or different UEs. In one option, the use of this format is based on pre-configuration or based on an indication within the SCI of the UE performing the transmission, which may indicate that a multi-TB transmission may be performed and that format 1 may need to be used.
[0043] In one embodiment, when a new PSFCH format is introduced, a PSFCH transmission carrying multiple HARQ feedbacks may need to be always transmitted within the COT, or alternatively, may be always transmitted at the end of the COT. In one option, if the HARQ feedback cannot be transmitted within the COT, the UE may subsequently acquire a new COT and trigger a retransmission in the next available COT for the TBs for which HARQ cannot be transmitted.
[0044] In one embodiment, NACK-based feedback is not supported when operating in unlicensed spectrum for dynamic channel access mode or when cg-RetransmissionTimer is enabled for semi-static channel access mode. In one embodiment, NACK-based feedback is supported when operating in unlicensed spectrum and when cg-RetransmissionTimer is not enabled for semi-static channel access mode.
[0045] In one embodiment, for multicast with known communication range requirements, when operating in unlicensed spectrum, ACK-based feedback is supported instead of NACK-only-based feedback, whether operating in semi-static or dynamic channel access mode, without requiring the establishment of a multicast context. In one embodiment, neither ACK-based feedback nor NACK-only-based feedback is supported when operating in unlicensed spectrum for dynamic channel access mode or when cg-RetransmissionTimer is enabled for semi-static channel access mode. In one embodiment, when operating in unlicensed spectrum and for semi-static channel access mode when cg-RetransmissionTimer is not enabled, ACK-based feedback is supported only for multicast communications.
[0046] In another embodiment, autonomous PSFCH transmissions are configured. In this case, the PSFCH transmissions may be autonomous or self-sufficient. That is, there is no one-to-one or one-to-many mapping between PSCCH / PSSCH resources and (one or more) PSFCH resources, and the PSFCH is continuously monitored in a window and carries a payload that identifies the source and destination of the SL transmission and the corresponding HARQ-ACK bits. Note that this process can be directly extended for multi-TB transmissions from one or more UEs, and in this case, the PSFCH may need to carry information about the source and destination for each TB or each group of TBs, and indicate the corresponding HARQ-ACK information for each TB. In one embodiment, the window is fixed or preconfigured, or may be related to the COT length within which (one or more) transmissions may have been performed.
[0047] In one embodiment, a retransmission timer concept may be introduced. The retransmission timer starts when the last symbol of the PSCCH / PSSCH with a feedback request is received, or from the first symbol when such a transmission is made. The retransmission timer expires after a configured / predefined number of slots or ms or symbols have been accounted for. When the retransmission timer expires, the UE discards (one or more) HARQ-ACK bits or PSFCH and does not further attempt to retransmit it, or in an alternative, when the retransmission timer expires, the UE may assume a NACK and may retransmit.
[0048] In one embodiment, if a new PSFCH format is defined, the payload of this PSFCH format may include at least one or more of the following information:
[0049] ■Layer 1 (L1) source ID
[0050] ■(One or more) L1 destination IDs, which can be a scalar or vector
[0051] ■HARQ-ACK bits corresponding to a group or all HARQ process IDs
[0052] ■New data indicator (NDI) bit
[0053] ■Cyclic redundancy check (CRC)
[0054] ■COT sharing information when the UE transmitting PSFCH may be an initiator or a responder:
[0055] ○ Whether the COT is shared, and how long the remaining COT may be
[0056] ○ Remaining COT information
[0057] ○Indication of whether the current device is operating as an initiator or responder
[0058] ○Channel access priority level
[0059] ○ Periodicity and / or offset of semi-static channel access pattern
[0060] In another embodiment, the HARQ feedback is provided in the form of SCI piggybacked on the PSSCH. Assuming that a unicast / multicast connection is established, the relevant HARQ feedback may be transmitted as control information piggybacked on the PSSCH. In this case, the payload of the SCI may include at least one or more of the following information:
[0061] L1 Source ID
[0062] ■L1 destination ID, which can be a scalar or vector
[0063] ■HARQ-ACK bits corresponding to a set of HARQ process IDs
[0064] NDI Bit
[0065] ■CRC
[0066] ■COT sharing information when the UE transmitting PSFCH may be an initiator or a responder:
[0067] ○ Whether the COT is shared, and how long the remaining COT may be
[0068] ○ Remaining COT information
[0069] ○Indication of whether the current device is operating as an initiator or responder
[0070] ○Channel access priority level
[0071] ○ Periodicity and / or offset of semi-static channel access pattern
[0072] It will be understood that the embodiments listed here may not be mutually exclusive, and one or more of them may be applicable together.
[0073] Sidelink HARQ-ACK for multi-slot and multi-TB transmissions
[0074] Assuming that multi-slot transmission is introduced in SL to cope with LBT failure, and more importantly, to better utilize COT, the traditional SL HARQ process may need to be revised accordingly.
[0075] For the case of single TB transmission over multiple slots, the process of one-to-one resource mapping between PSCCH / PSSCH and PSFCH slots may require modification in that the slot used for calculation of PSFCH opportunity is derived from the last slot in the multi-slot bundle instead of the initial slot. In this case, the UE has the time budget to process all repetitions of the TB or all TB transmissions and prepare the PSFCH with feedback.
[0076] In one embodiment, when a multi-slot transmission includes multiple repeated bursts of the same TP, the PSFCH resource determination process of Rel.16 will be used again, where the PSFCH resource for a given TB is calculated based on the slot index of the TB. This will result in separate 1-bit PSFCH transmissions for different TBs.
[0077] In one embodiment, group TB bundling may additionally be applied. In this regard, TB bundling of order L may be used to further control overhead, where L=1 means that each PSFCH set refers to the HARQ feedback of a single TB, and L>1 means that the HARQ-ACK feedback of multiple TBs is bundled in a single PSFCH set indication, where L may be fixed or (pre)configured per resource pool. In one option, bundling is applied such that ACK is reported in the PSFCH if all TBs are received, and NACK is reported if there are TBs that are not received. In another different option, bundling is applied such that ACK is reported in the PSFCH if at least one TB is received, and NACK is reported if all TBs are not received.
[0078] As described above, in order to carry HARQ-ACK information for multiple TBs and some information in the previous embodiment, a new PSFCH format may be defined instead, which may still span orthogonal frequency division multiplexed (OFDM) symbols but may carry two or more bits. In this sense, in one embodiment, this new PSFCH may carry M bit ,b(0),…,b(M bit -1) as physical uplink control channel (PUCCH) format 2. Specifically, the pseudo code provided in Section 6.3.2.5.1 of the third generation partnership project (3GPP) technical specification (TS) 38.211 may be used to implement M bit The bits are scrambled and modulated using quadrature phase shift keying (QPSK) as described in Section 6.3.2.5.2 of TS 38.211. Although the process from PUCCH format 2 can be reused for this new PSFCH format, a new radio resource control (RRC) dataScramblingIdentityPSFCH is additionally defined, which can be used to appropriately set the n used in the scrambling process. ID The value of .
[0079] In one embodiment, spreading may be additionally applied to the complex modulation symbols as described in Section 6.3.2.5.2.A of TS 38.211 using the same orthogonal cover code (OCC) defined in Rel.16NR-U. In another embodiment, no spreading is applied to the complex modulation symbols since they are mapped to a specific interlace.
[0080] Uu side link HARQ-ACK caused by channel access failure
[0081] In one embodiment, when a transmitting (TX) UE may be unable to transmit a scheduled PSSCH transmission whose resources are indicated by downlink control information (DCI) due to LBT failure (e.g., failure to acquire COT, or failure to access a channel within a shared COT), the UE may report / generate a NACK to the associated gNB.
[0082] In another embodiment, when a TX UE may be unable to transmit a PSSCH transmission for which resources were provided via a configuration grant due to LBT failure (e.g., failure to acquire a COT, or failure to access a channel within a shared COT), the UE may report / generate a NACK to the associated gNB.
[0083] In another embodiment, if the TX UE does not receive the PSFCH due to LBT failure in any PSFCH reception opportunity associated with PSSSCH transmission in the resources provided by the DCI, the UE may report / generate a NACK to the associated gNB.
[0084] In another embodiment, if the TX UE does not receive the PSFCH due to LBT failure in any PSFCH reception opportunity associated with a PSSSCH transmission for which resources are provided via a configuration grant, the UE may report / generate a NACK to the associated gNB.
[0085] It will be understood that the embodiments listed here are not mutually exclusive and one or more of them may be applicable together.
[0086] System and implementation
[0087] Figure 5-Figure 8 Various systems, devices, and components are illustrated in which aspects of the disclosed embodiments may be implemented.
[0088] Figure 5A network 500 according to various embodiments is illustrated. The network 500 may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited thereto, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.
[0089] The network 500 may include a UE 502, which may include any mobile or non-mobile computing device designed to communicate with the RAN 504 via an over-the-air connection. The UE 502 may be communicatively coupled to the RAN 504 via a Uu interface. The UE 502 may be, but is not limited to, a smartphone, a tablet computer, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, a dashboard, a head-up display device, an onboard diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, and the like.
[0090] In some embodiments, the network 500 may include multiple UEs that are directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels, such as but not limited to PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
[0091] In some embodiments, UE 502 may also communicate with AP 506 via an over-the-air connection. AP 506 may manage a WLAN connection that may be used to offload some / all network traffic from RAN 504. The connection between UE 502 and AP 306 may conform to any IEEE 802.11 protocol, where AP 506 may be a Wireless Fidelity (Wi-Fi) ) router. In some embodiments, UE 502, RAN 504 and AP 506 can utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve UE 502 being configured by RAN 504 to utilize both cellular radio resources and WLAN resources.
[0092] RAN 504 may include one or more access nodes, such as AN 508. AN 508 may terminate air interface protocols for UE 502 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 508 may enable data / voice connectivity between CN 520 and UE 502. In some embodiments, AN 508 may be implemented in a separate device, or as one or more software entities running on a server computer, as part of a virtual network, such as CRAN or a virtual baseband unit pool. AN 508 is referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 508 may be a macro cell base station, or a low power base station for providing a femto cell, pico cell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth than a macro cell.
[0093] In an embodiment where the RAN 504 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 504 is an LTE RAN) or an Xn interface (if the RAN 504 is a 5G RAN). The X2 / Xn interface (which may be separated into a control / user plane interface in some embodiments) may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, and the like.
[0094] The ANs of the RAN 504 may each manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to the UE 502. The UE 502 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 504. For example, the UE 502 and the RAN 504 may use carrier aggregation to allow the UE 502 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual connectivity scenario, the first AN may be a primary node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second AN may be any combination of eNBs, gNBs, ng-eNBs, etc.
[0095] RAN 504 may provide an air interface via a licensed spectrum or an unlicensed spectrum. In order to operate in an unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology and PCell / Scell. Before accessing an unlicensed spectrum, a node may perform a medium / carrier sensing operation based on, for example, a listen-before-talk (LBT) protocol.
[0096] In the V2X scenario, the UE 502 or AN 508 may be or act as an RSU, which may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by an appropriate AN or a fixed (or relatively fixed) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU"; an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU"; and so on. In one example, an RSU is a computing device coupled to a roadside RF circuit that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuits to store intersection map geometry, traffic flow statistics, media, and applications / software to sense and control ongoing vehicle and pedestrian traffic flow. The RSU may provide extremely low latency communications required for high-speed events such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The components of the RSU may be housed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (eg, Ethernet) to a traffic signal controller or backhaul network.
[0097] In some embodiments, the RAN 504 may be an LTE RAN 510 with an eNB, such as, for example, the eNB 512. The LTE RAN 510 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo coding for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; rely on PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and rely on CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on frequency bands below 6 GHz.
[0098] In some embodiments, the RAN 504 may be a NG-RAN 514 with a gNB, such as a gNB 516, or a NG-RAN 514 with a ng-eNB, such as a ng-eNB 518. The gNB 516 may be connected to a 5G-enabled UE using a 5G NR interface. The gNB 516 may be connected to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 518 may also be connected to the 5G core via an NG interface, but may be connected to the UE via an LTE air interface. The gNB 516 and the ng-eNB 518 may be connected to each other via an Xn interface.
[0099] In some embodiments, the NG interface can be divided into two parts, one is the NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 514 and the UPF 548 (e.g., the N3 interface), and the other is the NG control plane (NG-C) interface, which is the signaling interface between the nodes of the NG-RAN 514 and the AMF 544 (e.g., the N2 interface).
[0100] The NG-RAN 514 may provide a 5G-NR air interface with the following features: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking of PDSCH; and tracking reference signals for time tracking. The 5G-NR air interface may operate on FR1 bands including bands below 6 GHz or FR2 bands including bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB, which is a region of a downlink resource grid including PSS / SSS / PBCH.
[0101] In some embodiments, the 5G-NR air interface may utilize BWP for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, UE 502 may be configured with multiple BWPs, each of which is configured with a different SCS. When a BWP change is indicated to UE 502, the SCS of the transmission may also be changed. Another use case example of BWP is related to power saving. Specifically, UE 502 may be configured with multiple BWPs with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs may be used for data transmission with a small traffic load, while allowing power savings at UE 502 and in some cases at gNB 516. A BWP containing a larger number of PRBs may be used for scenarios with higher traffic loads.
[0102] RAN 504 is communicatively coupled to CN 520, which includes network elements to provide various functions to support data and telecommunication services to customers / subscribers (e.g., users of UE 502). The components of CN 520 may be implemented in one physical node or in separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all functions provided by the network elements of CN 520 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of CN 520 may be referred to as a network slice, and a logical instantiation of a portion of CN 520 may be referred to as a network sub-slice.
[0103] In some embodiments, CN 520 may be an LTE CN 522, which may also be referred to as an EPC. LTE CN 522 may include MME 524, SGW 526, SGSN 528, HSS 530, PGW 532, and PCRF 534, which are coupled to each other via interfaces (or "reference points"), as shown. The functions of the elements of LTE CN 522 may be briefly described as follows.
[0104] The MME 524 may implement mobility management functions to track the current location of the UE 502 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and the like.
[0105] The SGW 526 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 522. The S-GW 526 may be the local mobility anchor point for handovers between RAN nodes and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.
[0106] SGSN 528 may track the location of UE 502 and perform security functions and access control. In addition, SGSN 528 may perform inter-EPC node signaling for mobility between different RAT networks; select PDN and S-GW as specified by MME 524; select MME for handover; etc. The S3 reference point between MME 524 and SGSN 528 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active states.
[0107] The HSS 530 may include a database for network users, including subscription related information, to support the handling of communication sessions by network entities. The HSS 530 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. The S6a reference point between the HSS 530 and the MME 524 may enable the transfer of subscription and authentication data to authenticate / authorize user access to the LTE CN 520.
[0108] The PGW 532 may terminate the SGi interface towards a data network (DN) 536, which may include an application / content server 538. The PGW 532 may route data packets between the LTE CN 522 and the data network 536. The PGW 532 may be coupled to the SGW 526 via an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 532 may also include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 532 and the data network 536 may be an operator external public, private PDN, or an intra-operator packet data network, such as for the provisioning of IMS services. The PGW 532 may be coupled to the PCRF 534 via a Gx reference point.
[0109] PCRF 534 is the policy and charging control element of LTE CN 522. PCRF 534 may be communicatively coupled with application / content server 538 to determine appropriate QoS and charging parameters for service flows. PCRF 532 may provision the associated rules into PCEF (via Gx reference point) with the appropriate TFT and QCI.
[0110] In some embodiments, CN 520 may be 5GC 540. 5GC 540 may include AUSF 542, AMF 544, SMF 546, UPF 548, NSSF 550, NEF 552, NRF 554, PCF 556, UDM 558, and AF 560, which are coupled to each other through interfaces (or "reference points") as shown. The functions of the elements of 5GC 540 may be briefly described as follows.
[0111] AUSF 542 can store data for authentication of UE 502 and handle authentication related functions. AUSF 542 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 540 through reference points as shown, AUSF 542 can also expose a Nausf service-based interface.
[0112] AMF 544 may allow other functions of 5GC 540 to communicate with UE 502 and RAN 504, and subscribe to notifications about mobility events for UE 502. AMF 544 may be responsible for registration management (e.g., for registering UE 502), connection management, reachability management, mobility management, legal interception of AMF-related events, and access authentication and authorization. AMF 544 may provide transport for SM messages between UE 502 and SMF 546, and act as a transparent proxy for routing SM messages. AMF 544 may also provide transport for SMS messages between UE 502 and SMSF. AMF 544 may interact with AUSF 542 and UE 502 to perform various security anchoring and context management functions. In addition, AMF 544 can be a termination point for the RAN CP interface, which can include or can be an N2 reference point between RAN 504 and AMF 544; and AMF 544 can be a termination point for NAS (N1) signaling and perform NAS encryption and integrity protection. AMF 544 can also support NAS signaling with UE 502 through the N3 IWF interface.
[0113] SMF 546 may be responsible for SM (e.g., session establishment, tunnel management between UPF 548 and AN 508); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering at UPF 548 to route traffic to the appropriate destination; termination of interfaces to policy control functions; control portions of policy enforcement, charging, and QoS; lawful interception (for SM events and interfaces to LI systems); termination of the SM portion of NAS messages; downlink data notification; initiation of AN-specific SM information sent to AN 508 via AMF 544 over N2; and determination of the SSC mode for a session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between UE 502 and data network 536.
[0114] The UPF 548 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 536, and a branch point to support multi-homed PDU sessions. The UPF 548 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS handling for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 548 may include an uplink classifier to support routing of traffic flows to the data network.
[0115] The NSSF 550 may select a set of network slice instances to serve the UE 502. If necessary, the NSSF 550 may also determine the allowed NSSAIs and the mapping to the subscribed S-NSSAIs. The NSSF 550 may also determine the set of AMFs to be used to serve the UE 502, or a list of candidate AMFs, based on appropriate configuration and possibly by querying the NRF 554. The selection of a set of network slice instances for the UE 502 may be triggered by the AMF 544 with which the UE 502 is registered by interacting with the NSSF 550, which may result in a change of the AMF. The NSSF 550 may interact with the AMF 544 via the N22 reference point; and may communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, the NSSF 550 may present an Nnssf service-based interface.
[0116] NEF 552 can safely expose services and capabilities provided by 3GPP network functions, internal exposure / re-exposure, AF (e.g., AF 560), edge computing or fog computing systems, etc. to third parties. In this embodiment, NEF 552 can authenticate, authorize or throttle AF. NEF 552 can also convert information exchanged with AF 560 and information exchanged with internal network functions. For example, NEF 552 can translate between AF service identifiers and internal 5GC information. NEF 552 can also receive information from other NFs based on the exposed capabilities of other NFs. This information can be stored at NEF 552 as structured data, or stored at a data storage NF using a standardized interface. The stored information can then be exposed to other NFs and AFs by NEF 552, or used for other purposes, such as parsing. In addition, NEF 552 can present Nnef service-based interfaces.
[0117] NRF 554 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information about discovered NF instances to NF instances. NRF 554 also maintains information about available NF instances and the services they support. As used herein, the term "instantiation" or the like may refer to the creation of an instance, while "instance" may refer to the specific occurrence of an object, which may occur during the execution of program code, for example. In addition, NRF 554 may present an Nnrf service-based interface.
[0118] PCF 556 can provide policy rules to control plane functions to enforce them, and can also support a unified policy framework to constrain network behavior. PCF 556 can also implement a front end to access subscription information related to policy decisions in the UDR of UDM 558. In addition to communicating with functions through reference points as shown, PCF 556 can also expose Npcf service-based interfaces.
[0119] UDM 558 can handle subscription-related information to support the handling of communication sessions by network entities, and can store subscription data for UE502. For example, subscription data can be communicated via the N8 reference point between UDM 558 and AMF 544. UDM558 may include two parts, an application front end and a UDR. UDR may store subscription data and policy data for UDM 558 and PCF 556, and / or store structured data and application data for exposure (including PFD for application detection, application request information for multiple UEs 502) for NEF 552. Nudr service-based interfaces may be presented by UDR 221 to allow UDM 558, PCF 556, and NEF 552 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of changes in related data in the UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, and the like. Several different front ends may serve the same user in different transactions. UDM-FE accesses subscription information stored in UDR and performs authentication credential processing, user identity handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, UDM 558 can also expose Nudm service-based interfaces.
[0120] The AF 560 may provide application influence on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.
[0121] In some embodiments, 5GC 540 can implement edge computing by selecting an operator / third-party service to be geographically close to the point where UE502 is attached to the network. This can reduce latency and load on the network. In order to provide edge computing implementation, 5GC 540 can select a UPF 548 close to UE 502 and perform traffic manipulation from UPF 548 to data network 536 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 560. In this way, AF 560 can affect UPF (re)selection and traffic routing. Based on operator deployment, when AF 560 is considered a trusted entity, the network operator can allow AF 560 to interact directly with related NFs. In addition, AF 560 can present a Naf service-based interface.
[0122] The data network 536 may represent various network operator services, Internet access, or third-party services, which may be provided by one or more servers, including, for example, an application / content server 538 .
[0123] Figure 6 Schematically illustrated is a wireless network 600 in accordance with various embodiments. The wireless network 600 may include a UE 602 in wireless communication with an AN 604. The UE 602 and AN 604 may be similar to, and substantially interchangeable with, similarly named components described elsewhere herein.
[0124] UE 602 may be communicatively coupled with AN 604 via connection 606. Connection 606 is illustrated as an air interface to enable the communicative coupling and may conform to a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.
[0125] UE 602 may include a host platform 608 coupled to a modem platform 610. Host platform 608 may include application processing circuitry 612, which may be coupled to protocol processing circuitry 614 of modem platform 610. Application processing circuitry 612 may run various applications that source / sink application data for UE 602. Application processing circuitry 612 may further implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.
[0126] Protocol processing circuitry 614 may implement one or more layer operations to facilitate sending or receiving data over connection 606. The layer operations implemented by protocol processing circuitry 614 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.
[0127] The modem platform 610 may also include digital baseband circuitry 616, which may implement one or more layer operations in the network protocol stack "below" the layer operations performed by the protocol processing circuitry 614. These operations may include, for example, PHY operations, including one or more of the following: HARQ-ACK functionality, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time, space-frequency, or space coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.
[0128] The modem platform 610 may also include a transmit circuit 618, a receive circuit 620, an RF circuit 622, and an RF front end (RFFE) 624, which may include or be connected to one or more antenna panels 626. In brief, the transmit circuit 618 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receive circuit 620 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 622 may include a low noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 624 may include a filter (e.g., a surface / bulk acoustic wave filter), a switch, an antenna tuner, a beamforming component (e.g., a phased array antenna component), etc. The selection and arrangement of the components of the transmit circuit 618, the receive circuit 620, the RF circuit 622, the RFFE 624, and the antenna panel 626 (generally referred to as "transmit / receive components") may depend on the details of the specific implementation, such as whether the communication is TDM or FDM, at mmWave or sub-6gHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be disposed in the same or different chips / modules, and so on.
[0129] In some embodiments, the protocol processing circuit 614 may include one or more instances of control circuitry (not shown) to provide control functionality for the transmit / receive components.
[0130] UE reception may be established by and via antenna panel 626, RFFE 624, RF circuitry 622, receive circuitry 620, digital baseband circuitry 616, and protocol processing circuitry 614. In some embodiments, antenna panel 626 may receive transmissions from AN 604 via receive beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 626.
[0131] UE transmission may be established by and via protocol processing circuitry 614, digital baseband circuitry 616, transmit circuitry 618, RF circuitry 622, RFFE 624, and antenna panel 626. In some embodiments, the transmit component of UE 604 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of antenna panel 626.
[0132] Similar to UE 602, AN 604 may include a host platform 628 coupled to a modem platform 630. Host platform 628 may include application processing circuitry 632 coupled to protocol processing circuitry 634 of modem platform 630. The modem platform may also include digital baseband circuitry 636, transmit circuitry 638, receive circuitry 640, RF circuitry 642, RFFE circuitry 644, and antenna panel 646. The components of AN 604 may be similar to the like-named components of UE 602 and are substantially interchangeable. In addition to performing data transmission / reception as described above, the components of AN 608 may also perform various logical functions including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
[0133] Figure 7 The block diagram of illustrates components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing any one or more of the methods discussed herein according to some example embodiments. Specifically, Figure 7 A diagrammatic representation of hardware resources 700 is shown, including one or more processors (or processor cores) 710, one or more memory / storage devices 720, and one or more communication resources 730, each of which may be communicatively coupled via a bus 740 or other interface circuitry. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 702 may be executed to provide an execution environment for one or more network slices / subslices utilizing the hardware resources 700.
[0134] Processor 710 may include, for example, processor 712 and processor 714. Processor 710 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination of these.
[0135] The memory / storage device 720 may include main memory, disk storage, or any suitable combination of these. The memory / storage device 720 may include, but is not limited to, any type of volatile, non-volatile, or semi-volatile memory, such as 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 storage, and the like.
[0136] The communication resources 730 may include an interconnect or network interface controller, component, or other appropriate device to communicate with one or more peripheral devices 704 or one or more databases 706 or other network elements via the network 708. For example, the communication resources 730 may include a wired communication component (e.g., for coupling via USB, Ethernet, etc.), a cellular communication component, an NFC component, (or low energy consumption ) components, Wi- components, and other communication components.
[0137] The instructions 750 may include software, programs, applications, applet programs, apps, or other executable code for causing at least any one of the processors 710 to perform any one or more of the methods discussed herein. The instructions 750 may reside in whole or in part within at least one of the processors 710 (e.g., within a cache memory of the processor), within the memory / storage device 720, or any suitable combination of these. In addition, any portion of the instructions 750 may be transferred to the hardware resources 700 from any combination of the peripheral device 704 or the database 706. Thus, the memory of the processor 710, the memory / storage device 720, the peripheral device 704, and the database 706 are examples of computer-readable and machine-readable media.
[0138] Figure 8 The network 800 according to various embodiments is illustrated. The network 800 may operate in a manner that complies with the 3GPP technical specifications or technical reports of the 6G system. In some embodiments, the network 800 may operate simultaneously with the network 500. For example, in some embodiments, the network 800 may share one or more frequency or bandwidth resources with the network 500. As a specific example, a UE (e.g., UE 802) may be configured to operate in the network 800 and the network 500. This configuration may be based on the UE including a circuit configured to communicate with the frequency and bandwidth resources of both the network 500 and the network 800. In general, several elements of the network 800 may share one or more characteristics with elements of the network 500. For the sake of brevity and clarity, these elements may not be repeated in the description of the network 800.
[0139] The network 800 may include a UE 802, which may include any mobile or non-mobile computing device designed to communicate with the RAN 808 via an over-the-air connection. The UE 802 may be similar to, for example, the UE 502. The UE 802 may be, but is not limited to, a smartphone, a tablet computer, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, a dashboard, a head-up display device, an onboard diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, and the like.
[0140] Although in Figure 8 Although not specifically shown in FIG. 8 , in some embodiments, the network 800 may include multiple UEs that are directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels, such as but not limited to PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although in Figure 8 Although not specifically shown, UE 802 can communicate with AP (e.g., Figure 5 AP 506) described above is communicatively coupled. Figure 8 Although not specifically shown in the figure, in some embodiments, the RAN 808 may include one or more ANs, such as Figure 5 AN 508 is described. The RAN 808 and / or the AN of the RAN 808 may be referred to as a base station (BS), a RAN node, or by some other terminology or name.
[0141] The UE 802 and the RAN 808 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features, such as communication in terahertz (THz) or sub-THz bandwidths, or joint communication and sensing. As used herein, the term "joint communication and sensing" may refer to a system that implements wireless communication and radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidth may refer to communications in a frequency range of 80 GHz and above. This frequency range may be additionally or alternatively referred to as a "millimeter wave" or "mmWave" frequency range.
[0142] The RAN 808 may allow communication between the UE 802 and the 6G core network (CN) 810. Specifically, the RAN 808 may facilitate the transmission and reception of data between the UE 802 and the 6G CN 810. The 6G CN 810 may include various functions, such as NSSF 550, NEF 552, NRF 554, PCF 556, UDM 558, AF 560, SMF 546, and AUSF 542. Figure 8 As shown, 6G CN810 may also include UPF 548 and DN 536.
[0143] In addition, the RAN 808 may include various additional functions that are in addition to or in place of the functions of a traditional cellular network (e.g., a 4G or 5G network). Two such functions may include a computing control function (computing CF) 824 and a computing service function (computing SF) 836. The computing CF 824 and the computing SF 836 may be parts or functions of a computing service plane. The computing CF 824 may be a control plane function that provides functions such as: management of the computing SF 836, computing task context generation and management (e.g., create, read, modify, delete), interacting with the underlying computing infrastructure for computing resource management, and the like. The computing SF 836 may be a user plane function that acts as an interface gateway for computing service users (e.g., UE 802) and computing nodes behind the computing SF instance. Some functions of the computing SF 836 may include: parsing computing service data received from users to calculate tasks that can be performed by computing nodes; maintaining a service mesh entry gateway or service API gateway; service and billing policy enforcement; performance monitoring and telemetry collection, and the like. In some embodiments, a compute SF 836 instance may serve as a user plane gateway for a cluster of compute nodes. A compute CF 824 instance may control one or more compute SF 836 instances.
[0144] Two other such functions may include a communication control function (communication CF) 828 and a communication service function (communication SF) 838, which may be part of the communication service plane. The communication CF 828 may be a control plane function for managing the communication SF 838, communication session creation / configuration / release, and managing communication session contexts. The communication SF 838 may be a user plane function for data transmission. The communication CF 828 and the communication SF 838 may be considered as upgrades to the SMF 546 and UPF 548, both of which have been referenced. Figure 5 The 5G system in FIG. 8 is described. The upgrade provided by the communication CF 828 and the communication SF 838 enables service-aware transmission. For traditional (e.g., 4G or 5G) data transmission, the SMF 546 and UPF 548 can still be used.
[0145] Two other such functions may include a data control function (data CF) 822 and a data service function (data SF) 832, which may be part of the data service plane. The data CF 822 may be a control plane function and provide functions such as data SF 832 management, data service creation / configuration / release, data service context management, etc. The data SF 832 may be a user plane function and act as a gateway between data service users (e.g., various functions of UE 802 and 6G CN 810) and data service endpoints behind the gateway. Specific functions may include: parsing data service user data and forwarding to corresponding data service endpoints, generating billing data, reporting data service status.
[0146] Another such function may be a service orchestration and chaining function (SOCF) 820, which may discover, orchestrate, and chain communication / computing / data services provided by functions in the network. Upon receiving a service request from a user, SOCF 820 may interact with one or more of the computing CF 824, the communication CF 828, and the data CF 822 to identify computing SF 836, communication SF 838, and data SF 832 instances, configure service resources, and generate a service chain, which may include multiple computing SF 836, communication SF 838, and data SF 832 instances and their associated computing endpoints. Workload processing and data movement may then be performed within the generated service chain. SOCF 820 may also be responsible for maintaining, updating, and releasing the created service chain.
[0147] Another such function may be a service registration function (SRF) 814, which may act as a registration center for system services provided in the user plane, such as services provided by service endpoints behind the compute SF 836 and data SF 832 gateways and services provided by the UE 802. The SRF 814 may be viewed as a counterpart to the NRF 554, which may act as a registration center for network functions.
[0148] Other such functions may include an evolved service communication proxy (eSCP) and a service infrastructure control function (SICF) 826, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G, with the addition of user plane service communication proxy capabilities. The eSCP is thus expressed in two parts: eCSP-C 812 and eSCP-U 834, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 826 may control and configure the eCSP instance in terms of service traffic routing policies, access rules, load balancing configuration, performance monitoring, and the like.
[0149] Another such function is AMF 844. AMF 844 may be similar to 544, but with additional functionality. Specifically, AMF 844 may include potential functional re-division, such as moving message forwarding functionality from AMF 844 to RAN 808.
[0150] Another such function is a service orchestration exposure function (SOEF) 818. SOEF may be configured to expose service orchestration and chaining services to external users (eg, applications).
[0151] The UE 802 may include an additional function called a compute client service function (compute CSF) 804. The compute CSF 804 may have both control plane functions and user plane functions, and may interact with corresponding network-side functions (e.g., SOCF 820, compute CF 824, compute SF 836, data CF 822, and / or data SF 832) to implement service discovery, request / response, computing task workload exchange, etc. The compute CSF 804 may also cooperate with network-side functions to decide whether computing tasks should be run on elements of the UE 802, RAN 808, and / or 6G CN 810.
[0152] UE 802 and / or computing CSF 804 may include a service mesh proxy 806. The service mesh proxy 806 may act as a proxy for service-to-service communications in the user plane. The functions of the service mesh proxy 806 may include one or more of addressing, security, load balancing, and the like.
[0153] Example Process
[0154] In some embodiments, Figure 5-Figure 7 Or (one or more) electronic devices, (one or more) networks, (one or more) systems, (one or more) chips or (one or more) components or some parts or implementations thereof of some other figures herein may be configured to perform one or more processes, techniques or methods or some parts thereof as described herein.
[0155] One such process is Fig. 9 Depicted in. Fig. 9 The process may include or involve a method to be performed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices including and / or implementing the UE. The process may include: at 901, performing a listen-before-talk (LBT) process related to a new radio (NR) side link (SL) transmission in a first time slot of a plurality of time slots; at 902, identifying a subset of the plurality of time slots having two or more candidate time slots for transmitting a hybrid automatic repeat request (HARQ) message related to the LBT process; and at 903, transmitting the HARQ message in a candidate time slot of the two or more candidate time slots.
[0156] Another such process is Fig.10 Depicted in. Fig.10 The process may include or involve a method to be performed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices including and / or implementing the UE. The process may include: at 1001, transmitting a new radio (NR) sidelink (SL) transmission; and at 1002, in a time slot of a subset of a plurality of time slots having two or more candidate time slots, based on a listen-before-talk (LBT) process performed in a first time slot of the plurality of time slots, identifying a hybrid automatic repeat request (HARQ) message, wherein the LBT process is related to the NR SL transmission.
[0157] For one or more embodiments, at least one of the components described in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the example section below. For example, the baseband circuit described above in connection with one or more of the foregoing figures may be configured to operate according to one or more examples described below. For another example, the circuits associated with UE, base station, network element, etc. described above in connection with one or more of the foregoing figures may be configured to operate according to one or more examples described below in the example section.
[0158] Example
[0159] Example 1 may include a process for enabling unicast HARQ feedback for SL operation in unlicensed spectrum;
[0160] Example 2 may include a process for enabling multicast HARQ feedback for SL operation in unlicensed spectrum;
[0161] Example 3 may include a process for enabling broadcast HARQ feedback for SL operation in unlicensed spectrum;
[0162] Example 4 may include a process for supporting HARQ feedback for multi-slot transmissions;
[0163] Example 5 may include defining a new PSFCH format to carry HARQ-ACK information for multiple TBs and some information to allow COT sharing and feedback of HARQ information to different UEs.
[0164] Example 6 includes a method to be performed by a user equipment (UE), one or more elements of the UE and / or an electronic device including the UE, wherein the method includes: identifying a physical sidelink shared information (PSSCH) transmission; and based on the PSSCH transmission, transmitting a hybrid automatic repeat request acknowledgment (HARQ-ACK) in a physical sidelink feedback channel (PSFCH) transmission; wherein one or both of the PSSCH transmission and the PSFCH transmission are in an unlicensed frequency band.
[0165] Example 7 includes a method to be performed by an electronic device, wherein the method includes: transmitting a physical sidelink shared information (PSSCH) transmission; and based on the PSSCH transmission, identifying a hybrid automatic repeat request acknowledgment (HARQ-ACK) in a physical sidelink feedback channel (PSFCH) transmission; wherein one or both of the PSSCH transmission and the PSFCH transmission are in an unlicensed frequency band.
[0166] Example 8 includes the method of Example 7 and / or some other example herein, wherein the electronic device is a user equipment (UE), one or more elements of a UE, or an electronic device including a UE,
[0167] Example 9 includes the method of Example 7 and / or any other example herein, wherein the electronic device is a base station, one or more elements of a base station, or an electronic device including a base station,
[0168] Example 10 may include a method as described in any of Examples 7-9 and / or some other example herein, wherein the electronic device is a UE, and the method further includes generating / sending a NACK to a gNB if the transmission of the PSSCH fails or the UE does not receive the PSFCH transmission.
[0169] Example 11 may include a method as described in any of Examples 7-10 and / or some other example herein, wherein the timing of transmission of the PSFCH is preconfigured or fixed.
[0170] Example 12 may include a method to be performed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices including and / or implementing the UE, wherein the method includes: performing a listen-before-talk (LBT) process associated with a new radio (NR) side link (SL) transmission in a first time slot of a plurality of time slots; identifying a subset of the plurality of time slots having two or more candidate time slots for transmission of a hybrid automatic repeat request (HARQ) message associated with the LBT process; and transmitting the HARQ message in a candidate time slot of the two or more candidate time slots.
[0171] Example 13 may include a method as described in Example 12 and / or some other example herein, wherein the subset of two or more candidate time slots includes four candidate time slots.
[0172] Example 14 may include a method as described in any of Examples 12-13 and / or some other example herein, wherein the transmission of the HARQ message includes transmission of the HARQ message in a physical SL feedback channel (PSFCH) transmission.
[0173] Example 15 may include a method as described in any of Examples 12-14 and / or some other example herein, wherein transmitting the HARQ message is performed via unicast transmission.
[0174] Example 16 may include a method as described in any of Examples 12-14 and / or some other example herein, wherein transmitting the HARQ message is performed via a multicast transmission.
[0175] Example 17 may include a method as described in any of Examples 12-14 and / or some other example herein, wherein transmitting the HARQ message is performed via a broadcast transmission.
[0176] Example 18 may include a method as in any of Examples 12-17 and / or some other example herein, wherein there are non-candidate time slots between respective time slots of the two or more candidate time slots in the plurality of time slots.
[0177] Example 19 may include a method as described in any of Examples 12-18 and / or some other example herein, wherein the NR SL transmission is a physical SL control channel (PSCCH) transmission or a physical SL shared channel (PSSCH) transmission.
[0178] Example 20 may include a method to be performed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices including and / or implementing the UE, wherein the method includes: transmitting a new radio (NR) side link (SL) transmission; and in a time slot of a subset of a plurality of time slots having two or more candidate time slots, identifying a hybrid automatic repeat request (HARQ) message based on a listen-before-talk (LBT) process performed in a first time slot of the plurality of time slots, wherein the LBT process is related to the NR SL transmission.
[0179] Example 21 may include a method as described in Example 20 and / or some other example herein, wherein the subset of two or more candidate time slots includes four candidate time slots.
[0180] Example 22 may include a method as described in any of Examples 20-21 and / or some other example herein, wherein the identification of the HARQ message includes identification of the HARQ message in a physical SL feedback channel (PSFCH) transmission.
[0181] Example 23 may include a method as described in any of Examples 20-22, wherein the HARQ message is transmitted via a unicast transmission.
[0182] Example 24 may include a method as described in any of Examples 20-22, wherein the HARQ message is transmitted via a multicast transmission.
[0183] Example 25 may include a method as described in any of Examples 20-22, wherein the HARQ message is transmitted via a broadcast transmission.
[0184] Example 26 may include a method as described in any of Examples 20-25 and / or some other example herein, wherein there are non-candidate time slots between each of the two or more candidate time slots in the plurality of time slots.
[0185] Example 27 may include a method as described in any of Examples 20-26 and / or some other example herein, wherein the NR SL transmission is a physical SL control channel (PSCCH) transmission or a physical SL shared channel (PSSCH) transmission.
[0186] Example Z01 may include an apparatus comprising means for performing one or more elements of a method described in or related to any of Examples 1-27, or any other method or process described herein.
[0187] Example Z02 may include 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 a method described in or related to any of Examples 1-27 or any other method or process described herein.
[0188] Example Z03 may include an apparatus comprising logic, modules, or circuits for performing one or more elements of a method described in or related to any of Examples 1-27, or any other method or process described herein.
[0189] Example Z04 may include a method, technique, or process as described in or related to any of Examples 1-27, or portions thereof.
[0190] Example Z05 may include a device comprising: one or more processors and one or more computer-readable media comprising instructions, which, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portions thereof, as described in or related to any of Examples 1-27.
[0191] Example Z06 may include signals as described in or associated with any of Examples 1-27, or portions thereof.
[0192] Example Z07 may include a datagram, packet, frame, fragment, protocol data unit (PDU) or message as described in or related to any of Examples 1-27, or some portion thereof, or a datagram, packet, frame, fragment, protocol data unit (PDU) or message otherwise described in the present disclosure.
[0193] Example Z08 may include a signal encoding data as described in or associated with any of Examples 1-27, or portions thereof, or data otherwise described in this disclosure.
[0194] Example Z09 may include a signal encoding a datagram, packet, frame, fragment, protocol data unit (PDU) or message as described in or related to any of Examples 1-27, or some portion thereof, or a datagram, packet, frame, fragment, protocol data unit (PDU) or message otherwise described in the present disclosure.
[0195] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process, or portions thereof, as described in or related to any of Examples 1-27.
[0196] Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or portions thereof, as described in or related to any of Examples 1-27.
[0197] Example Z12 may include a signal in a wireless network as shown and described herein.
[0198] Example Z13 may include a method of communicating in a wireless network as shown and described herein.
[0199] Example Z14 may include a system for providing wireless communications as shown and described herein.
[0200] Example Z15 may include an apparatus for providing wireless communications as shown and described herein.
[0201] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The above description of one or more implementations provides illustrations and descriptions, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be obtained by implementing the various embodiments.
[0202] abbreviation
[0203] Unless used differently herein, the terms, definitions and abbreviations may be consistent with those defined in 3GPP TR21.905v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein.
[0204]
[0205]
[0206]
[0207]
[0208]
[0209]
[0210]
[0211]
[0212]
[0213]
[0214]
[0215]
[0216]
[0217]
[0218]
[0219]
[0220]
[0221]
[0222]
[0223]
[0224]
[0225] the term
[0226] For purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein.
[0227] The term "application" may refer to a complete, deployable, packaged environment that implements a certain functionality in an operating environment. The term "AI / ML application" or similar terms may refer to an application that contains some AI / ML models and application-level descriptions.
[0228] The term "circuit" as used herein refers to a hardware component such as, a part of, or including an electronic circuit, a logic circuit, a processor (shared, dedicated, or grouped) and / or a memory (shared, dedicated, or grouped), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the functions described. The term "circuit" may also refer to a combination of one or more hardware elements (or circuits used in electrical or electronic systems) and program code to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.
[0229] The term "processor circuit" used herein refers to a circuit that is part of or includes a circuit that can sequentially and automatically perform a sequence of operations or logical operations, or record, store and / or transmit digital data. The processing circuit may include one or more processing cores to execute instructions, and one or more memory structures to store program and data information. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer executable instructions such as program code, software modules and / or functional processes. The processing circuit may include more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may be referred to as "processor circuit".
[0230] As used herein, the term "interface circuit" refers to, is a part of, or includes a circuit that enables information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and the like.
[0231] The term "user equipment" or "UE" as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as the following terms: 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 device, reconfigurable radio device, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.
[0232] The term "network element" as used herein refers to a physical or virtualized device and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as the following terms: networked computer, networking hardware, network device, network node, router, switch, hub, bridge, radio network controller, RAN equipment, RAN node, gateway, server, virtualized VNF, NFVI, etc.
[0233] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to components of a computer that are communicatively coupled to one another. Additionally, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.
[0234] As used herein, the terms "appliance", "computer appliance" and the like refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.
[0235] The term "resource" as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, a throughput, a memory usage, a storage device, a network, a database and an application, a workload unit, and the like. "Hardware resources" may refer to computing, storage and / or network resources provided by (one or more) physical hardware elements. "Virtualized resources" may refer to computing, storage and / or network resources provided by a virtualized infrastructure to applications, devices, systems, and the like. The term "network resources" or "communication resources" may refer to resources accessible by a computer device / system via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing and / or network resources. System resources may be considered as a collection of coherent 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.
[0236] The term "channel" as used herein refers to any transmission medium, whether tangible or intangible, for communicating data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" and / or any other similar terms representing a passage or medium through which data is communicated. In addition, the term "link" as used herein refers to a connection that occurs between two devices over a RAT in order to send and receive information.
[0237] As used herein, the term "instantiation" or the like refers 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.
[0238] The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other, but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements allegedly coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements are in contact with each other by means of communication, including by wires or other interconnections, by wireless communication channels or links, and the like.
[0239] 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 a data element that contains content.
[0240] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.
[0241] The term "SSB" refers to a SS / PBCH block.
[0242] The term "primary cell" refers to an MCG cell operating on a primary frequency, in which the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.
[0243] The term "primary SCG cell" refers to an SCG cell in which a UE performs random access when performing a reconfiguration procedure with synchronization for DC operation.
[0244] The term "secondary cell" refers to a cell that provides additional radio resources for UEs configured with CA over a special cell.
[0245] The term "secondary cell group" refers to a subset of serving cells including a PSCell and zero or more secondary cells for a UE configured with DC.
[0246] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and there is only one serving cell consisting of the primary cell.
[0247] The term "serving cell" refers to a set of cells including special cell(s) and all secondary cells for a UE configured with CA / in RRC_CONNECTED.
[0248] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term "special cell" refers to the Pcell.
[0249] The term "machine learning" or "ML" refers to the use of a computer system that implements an algorithm and / or statistical model to perform (one or more) specific tasks without the use of explicit instructions, but instead relying on patterns and reasoning. ML algorithms build or estimate (one or more) mathematical models (referred to as "ML models" and the like) based on sample data (referred to as "training data", "model training information", and the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks. In general, an ML algorithm is a computer program that learns from experience and some performance metric about a certain task, and an ML model can be an object or data structure created after training an ML algorithm with one or more training data sets. After training, the ML model can be used to make predictions on new data sets. Although the term "ML algorithm" refers to a different concept than the term "ML model", these terms as described herein can be used interchangeably for the purposes of the present disclosure.
[0250] The terms "machine learning model", "ML model" or similar terms may also refer to the ML methods and concepts used by ML-assisted solutions. "ML-assisted solutions" are solutions that use ML algorithms to solve specific use cases during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithm, support machine vector, Bayesian algorithm, lumping algorithm, etc.), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, etc. Depending on the implementation, a specific ML model may have many sub-models as components, and the ML model may train all sub-models together. During inference, separately trained ML models may also be chained together in an ML pipeline. "ML pipeline" is a set of functions, functions, or functional entities that depend on an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and actors. An "actor" is an entity that uses the output of ML model inference to host an ML-assisted solution. The term "ML training host" refers to an entity, such as a network function, that hosts the training of a model. The term "ML inference host" refers to an entity, such as a network function, that hosts a model during inference mode (this includes both model execution and any online learning, if applicable). The ML host informs the actor of the output of the ML algorithm, and the actor makes decisions for actions (an "action" is performed by the actor as a result of the output of the ML-assisted solution). The term "model inference information" refers to information used as input to an ML model in order to determine (one or more) inferences; the data used to train an ML model and the data used to determine inferences may overlap, however, "training data" and "inference data" refer to different concepts.
Claims
1. A user equipment (UE), comprising: one or more processors; as well as One or more non-transitory computer-readable media, the one or more non-transitory computer-readable media comprising instructions, which when executed by the one or more processors, cause the UE to: performing a listen before talk (LBT) procedure related to a New Radio (NR) sidelink (SL) transmission in a first time slot of a plurality of time slots; identifying a subset of the plurality of time slots having two or more candidate time slots for transmitting a hybrid automatic repeat request (HARQ) message related to the LBT process; and The HARQ message is transmitted in a candidate time slot of the two or more candidate time slots.
2. The UE according to claim 1, wherein: The subset of two or more candidate time slots includes four candidate time slots.
3. The UE according to claim 1, wherein: Transmitting the HARQ message includes transmitting the HARQ message in a physical SL feedback channel (PSFCH) transmission.
4. The UE according to any one of claims 1 to 3, wherein: Transmitting the HARQ message is performed via unicast transmission.
5. The UE according to any one of claims 1 to 3, wherein: Transmitting the HARQ message is performed via multicast transmission.
6. The UE according to any one of claims 1 to 3, wherein: Transmitting the HARQ message is performed via broadcast transmission.
7. The method according to any one of claims 1 to 3, wherein: There are non-candidate time slots between corresponding time slots of the two or more candidate time slots of the plurality of time slots.
8. The UE according to any one of claims 1 to 3, wherein: The NR SL transmission is a physical SL control channel (PSCCH) transmission or a physical SL shared channel (PSSCH) transmission.
9. An apparatus for use in a user equipment (UE), wherein the apparatus comprises: Radio frequency (RF) circuitry for transmitting or receiving one or more new radio (NR) side link (SL) transmissions; and a baseband circuit communicatively coupled to the RF circuit, wherein the baseband circuit is configured to: Transmit NR SL transmission; and In a time slot of a subset of two or more candidate time slots of a plurality of time slots, a hybrid automatic repeat request (HARQ) message is identified based on a listen-before-talk (LBT) process performed in a first time slot of the plurality of time slots, wherein the LBT process is related to the NR SL transmission.
10. The device of claim 9, wherein: The subset of two or more candidate time slots includes four candidate time slots.
11. The device of claim 9, wherein: Identifying the HARQ message includes identifying the HARQ message in a physical SL feedback channel (PSFCH) transmission.
12. The device according to any one of claims 9 to 11, wherein: The HARQ message is transmitted via unicast transmission.
13. The device according to any one of claims 9 to 11, wherein: The HARQ message is transmitted via multicast transmission.
14. The device according to any one of claims 9 to 11, wherein: The HARQ message is transmitted via broadcast transmission.
15. The device according to any one of claims 9 to 11, wherein: There are non-candidate time slots between corresponding time slots of the two or more candidate time slots of the plurality of time slots.
16. The device according to any one of claims 9 to 11, wherein: The NR SL transmission is a physical SL control channel (PSCCH) transmission or a physical SL shared channel (PSSCH) transmission.
17. One or more non-transitory computer readable media (NTCRMs), the one or more NTCRMs comprising instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: performing a listen before talk (LBT) procedure related to a New Radio (NR) sidelink (SL) transmission in a first time slot of a plurality of time slots; identifying a subset of the plurality of time slots having two or more candidate time slots for transmitting a hybrid automatic repeat request (HARQ) message related to the LBT process; and The HARQ message is transmitted in a candidate time slot of the two or more candidate time slots.
18. One or more NTCRMs as claimed in claim 17, wherein: The subset of two or more candidate time slots includes four candidate time slots.
19. The one or more NTCRMs of claim 17, wherein: Transmitting the HARQ message includes transmitting the HARQ message in a physical SL feedback channel (PSFCH) transmission.
20. One or more NTCRMs as claimed in any one of claims 17 to 20, wherein: There are non-candidate time slots between corresponding time slots of the two or more candidate time slots of the plurality of time slots.
