Resource selection, listen before talk procedure, and mapping of priority and quality of service information for sidelink communications
By combining LBT programs and sensing resource selection in unlicensed spectrum, combined with the mapping of CAPC and PPPP, the spectrum usage and channel access optimization problems of side link communication systems in commercial use cases are solved, and efficient side chains are achieved Road communication expansion and spectrum utilization.
Patent Information
- Application Number
- CN202380028266.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-18
- Filing Date
- 2023-04-17
- Publication Date
- 2024-11-05
AI Technical Summary
In unlicensed spectrum, side link communication systems are difficult to achieve fair spectrum usage and fair coexistence between different technologies, and prior art is difficult to effectively extend side link operations to commercial use cases, such as between highly driving automated vehicles. Sensor information sharing, especially in terms of spectrum usage and channel access priority mapping.
By introducing a combination of listen first and speak (LBT) programs and sensing and resource selection programs in the unauthorized spectrum, combining mapping between channel access priority category (CAPC) and per packet ProSe priority (PPPP), Optimize resource selection and transmission processes to ensure fair use of spectrum and effective access to channels.
The effective expansion of side link communication in unlicensed spectrum is achieved, data rate and spectrum utilization is improved, new carrier frequency operation is supported, and fair coexistence between different technologies and fair use of spectrum is ensured.
Smart Images

Figure CN118901272A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 332,094, filed on April 18, 2022; and priority to U.S. Provisional Patent Application No. 63 / 332,084, filed on April 18, 2022. Technical Field
[0003] Various embodiments may generally relate to the field of wireless communications.For example, some embodiments may relate to techniques for sidelink communications, such as in an unlicensed spectrum. Background Art
[0004] Mobile communications have evolved significantly from early voice systems to today's highly complex integrated communications platforms. The next generation of wireless communications systems, the fifth generation (5G) (which may additionally or alternatively be referred to as new radio (NR)) can provide access to information and data sharing anytime, anywhere by a variety of users and applications. NR can be a unified network / system with the goal of meeting very different and sometimes conflicting performance dimensions and services. Such diverse multi-dimensional requirements may be driven by different services and applications.
[0005] For example, in the 3rd Generation Partnership Project (3GPP) Release 16 (Rel. 16) specification, sidelink (SL) communications were developed in the radio access network (RAN) to support advanced vehicle-to-everything (V2X) applications. In Release 17 (Rel. 17), SA2 studied and standardized proximity-based services, including public safety and business-related services, and as part of Rel. 17, power saving solutions (e.g., partial sensing, discontinuous reception (DRX), etc.) and coordination between user equipment (UE) have been developed to improve power consumption and reliability of SL transmission for battery-constrained terminals. Although NR SL was originally 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 (e.g., video) between vehicles with a high degree of driving automation. For commercial SL applications, the desired features may include increased SL data rates and new carrier frequencies to support SL. To achieve these elements, one of the goals in Release 18 (Rel. 18) is to extend SL operations in unlicensed spectrum (e.g., referred to as NR-U SL). BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The embodiments will be easily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, similar reference numerals represent similar structural elements. The embodiments are shown in the figures of the accompanying drawings by way of example and not by way of limitation.
[0007] Figure 1A New Radio - Unlicensed (NR-U) Side Link (SL) communication mode is schematically illustrated.
[0008] Figure 2 The Version 16 sensing and resource selection scheme is schematically shown.
[0009] Figure 3 An example procedure of combining the LBT procedure with the SL sensing and resource selection procedure according to various embodiments is shown.
[0010] Figure 4 An example of an LBT procedure for determining and transmitting on reserved but unutilized or unoccupied resources according to various embodiments is shown, where a user equipment (UE) transmits just prior to the reserved resources.
[0011] Figure 5 An example of an LBT procedure for determining and transmitting on reserved but unutilized or unoccupied resources according to various embodiments is shown, wherein the UE performs the LBT procedure on the reserved resources.
[0012] Figure 6 An example of mapping of channel access priority class (CAPC) and / or per-packet ProSe priority (PPPP) to SL transmission priority for SL communication in an unlicensed spectrum according to various embodiments is shown.
[0013] Figure 7 An example is shown of a first UE (UE#1) indicating a request to obtain a channel occupancy time (COT) prior to a subsequent transmission, in this case the request being for the COT of a second UE (UE#2), where UE#2 initiates the COT after receiving an indication from UE#1 that UE#1's COT has been published, according to various embodiments.
[0014] Figure 8 A wireless network according to various embodiments is schematically illustrated.
[0015] Fig. 9 Components of a wireless network according to various embodiments are schematically illustrated.
[0016] Fig.10 is a block diagram illustrating components that are 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 in the present disclosure, according to some example embodiments.
[0017] Fig.11 , Fig.12 and Fig.13 Example procedures for practicing various embodiments in the present disclosure are shown. DETAILED DESCRIPTION
[0018] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are described for the purpose of explanation rather than limitation, so as to provide a thorough understanding of various aspects of various embodiments. However, those skilled in the art will appreciate that various aspects of various embodiments can be implemented in other examples that deviate from these specific details after benefiting from this disclosure. In some cases, descriptions of well-known devices, circuits, and methods are omitted to avoid confusing the descriptions of various embodiments with unnecessary details. For the purposes of this disclosure, the phrase "A or B" refers to (A), (B), or (A and B).
[0019] Various embodiments in the present disclosure provide techniques for sidelink communications on unlicensed spectrum. For example, embodiments include sensing and resource selection (or reselection) procedures to select resources on which to perform sidelink transmissions. Prior to transmission, a listen-before-talk (LBT) procedure may be performed on the selected resources. Embodiments further include techniques for handling LBT failures. In addition, embodiments provide techniques for mapping between channel access priority classes (CAPCs) and per-packet ProSe priorities (PPPPs) and / or PC5 quality of service (QoS) indicators (PQIs).
[0020] As discussed above, one of the key goals in Rel.18 is to extend SL operation in unlicensed spectrum (NR-U SL). Note, however, that in order to allow fair use of spectrum and fair coexistence between different technologies, there are different regional regulatory requirements around the world. Therefore, it may be sufficient to enable a solution that complies with the most stringent regulations from ETSI BRAN published in EN 301 893 for all regions. In order to develop NR-U during Rel.16, a 3GPP NR-based system was developed that complies with these regulations.
[0021] In this context, given that the goal is to enable SL communication systems in unlicensed bands, considerations for SL communication systems need to be combined with regulatory requirements required for operation in unlicensed bands. In particular, note that NR SL can operate in two modes of operation: 1) Mode 1, where the gNB schedules (multiple) SL transmission resources to be used by the UE and Uu operation is limited to licensed spectrum; 2) Mode 2, where the UE determines (e.g., the gNB does not schedule) (multiple) SL transmission resources within the SL resources configured or pre-configured by the gNB / network. Figure 1 Two modes of operation are shown.
[0022] In this scenario, there are several specific challenges in enabling NR-U SL. In particular, one of the challenges is that when operating in the FR-1 unlicensed band, a listen-before-talk (LBT) procedure needs to be performed to acquire the medium before transmission can occur.
[0023] Sensing and resource selection
[0024] In Rel.16SL, when operating in Mode 2, some specific principles have been defined to allow appropriate selection of resources used by the UE, and in particular, a sensing procedure has been established such that the medium is scanned within a given window to pre-establish a set of candidate resources that are suitable for use or can be used within a given pool. The UE performs RSRP measurements and compares such measurements with specific thresholds depending on the SL priority to determine whether, if a specific resource is used, it will not cause congestion or interfere with another SL UE. Figure 2 A high-level schematic diagram of the sensing and resource selection procedures is provided in .
[0025] Moving on to Rel. 18, as described above, when the SL system operates in an unlicensed spectrum, LBT is required to acquire the COT based on the gaps between SL transmission bursts within the COT, or even within the COT if sharing of the COT is allowed. According to various embodiments in the present disclosure, given that LBT performs instantaneous measurements of the medium and can be used as a method to determine whether a transmission or resource can be used for transmission, the sensing and resource selection scheme can be modified to include the LBT procedure therein. The present disclosure describes various options for such a procedure according to various embodiments. For example, multiple options are provided on how to relate the LBT procedure to the SL sensing and resource selection procedure. In addition, the embodiments provide enhancements within the SL sensing and resource selection procedure.
[0026] Relationship of LBT to SL sensing and resource selection procedures
[0027] In one embodiment, for NR SL communications in unlicensed spectrum, one or more of the following options may be used according to various embodiments:
[0028] Option 1 - LBT-centric design:
[0029] ○ This option relies only on LBT operation and does not utilize components from the SL sensing and resource selection procedure. In this case, the UE can autonomously select the resource to be utilized from the configured resource pool and perform the LBT procedure just before performing a transmission on that resource. In this case,
[0030] ■ In one sub-option, to assess whether resources can be used, the energy measurements performed during LBT are compared with the EDT, which is set to the corresponding value of the RSRP threshold indicated by the i-th field in sl-Thres-RSRP-List, where i = p i +(p j -l)*8, and p i It is sl priority i.
[0031] ■ In one sub-option, in order to assess whether resources can be used, the energy measurements performed during LBT are compared with EDT as defined in 3GPP TS 37.213.
[0032] Option 2 - Combination of LBT design w / SL sensing and resource selection design:
[0033] ○ In this option, the LBT procedure may run independently, for example, on top of the NR SL sensing and resource selection procedure. For example, although the NR SL sensing and resource selection procedure may be reused, once a specific resource for its use is selected, the UE will perform the LBT procedure before transmission may occur.
[0034] Option 3 - Use LBT Energy Detection Threshold for Sensing (Resource Exclusion) Operation:
[0035] ○ In this option, the SL sensing and resource selection design is reused as a baseline, and the SL-RSRP threshold for resource exclusion (which can be converted to an energy detection (ED) threshold) is paired with the ED threshold for unlicensed operation defined in NR-U and described in TS 37.213. In this case, the channel access threshold may induce similar behavior in terms of channel access.
[0036] Option 4 - Threshold Alignment + LBT
[0037] ○ In this option, the SL sensing and resource selection design is reused as a baseline, and the SL-RSRP threshold for resource exclusion (which can be converted to an energy detection (ED) threshold) is paired with the ED threshold for unlicensed operation defined in NR-U and described in TS 37.213. In addition, LBT is performed before the actual transmission on the selected resources (e.g., within a given resource or at a CP extension interval).
[0038] Figure 3 An example procedure is shown that combines the LBT procedure with the SL sensing and resource selection procedure, for example, according to options 2, 3 and 4 above.
[0039] In one embodiment, option 1 may be supported by authorization, and in addition, one or more other options (eg, option 2 or 3 or 4) may be supported based on higher layer signaling configuration or UE capabilities.
[0040] LBT and resource selection enhancements
[0041] In one embodiment, one or more of the following options may be used to enhance the resource (re)selection procedure for SL transmission:
[0042] Option 1 - Back-to-Back Resource Selection + LBT:
[0043] ○ In this option, resource selection of continuous time slots is supported.
[0044] In one embodiment of this option, this may be enabled for all SL transports (e.g., by pre-configuration), or only if certain conditions are met (which may be controlled by pre-configuration):
[0045] ○ The packet delay budget (PDB) is less than the pre-configured value;
[0046] ○The remaining PDB is less than the pre-configured value;
[0047] ○The channel busy ratio (CBR) value is less than the pre-configured value;
[0048] ○ Priority and / or CAPC conditions:
[0049] ■ The TX UE is aware that there are no reserved resources associated with higher or lower SL priority and / or CAPC in the selected back-to-back resources.
[0050] ◆In one embodiment of this option, it is assumed that all UEs in the system additionally perform an LBT procedure before SL transmission, and therefore other UEs cannot access the channel due to energy detection, which can be considered in combination with the existing NR SL sensing and resource selection procedures.
[0051] Option 2 - Select time-first resources from the candidate resource set + LBT
[0052] o Resources are selected from the candidate resource set in a back-to-back and time-first manner. For example, the earliest resource in time from the candidate resource set formed by the sensing and resource selection procedure is prioritized for selection, and LBT is performed before the resource can be used for SL transmission.
[0053] Option 3 - Select resources from the candidate resource set + LBT
[0054] o In this option, the sensing and resource selection procedures are supplemented by an additional LBT procedure performed during resource selection, which can be applied to decide whether the channel can be accessed for SL transmission on the identified candidate resources. In this case, once the set of candidate resources is formed and the UE is associated with a specific resource, the UE can either transmit directly or can be authorized to perform additional LBT before performing SL transmission on that resource.
[0055] Transmission on reserved unused resources
[0056] In one embodiment, the LBT procedure may be used to check whether previously reserved SL resources are actually not occupied / utilized (e.g., due to received ACK feedback or any other reason), and therefore such resources may be considered as candidates for UE SL transmission and channel access. This mechanism may be used for configured grant transmissions, and in one embodiment, one or more of the following options may be used:
[0057] Option 1 - Transmission just before the reserved resources:
[0058] o A UE intending to transmit on the reserved resources (eg, received NACK) is expected to start transmission earlier (eg, applying CP extension) so that its transmission can be detected by a UE performing LBT measurements just before the reserved resources. Figure 4 An example of this procedure is shown.
[0059] ◆If a UE intending to transmit on the reserved resources detects a PSCCH / PSSCH in the previous slot indicating an extension or requesting a CP extension and only Type 2C LBT procedure can be applied, the UE does not need to perform LBT.
[0060] ◆If a UE intending to transmit on the reserved resources does not detect a PSCCH / PSSCH in the previous slot indicating an extension or requesting an extension to apply only the Type 2C LBT procedure, the UE needs to perform LBT. If there is no LBT failure, the UE transmits on the reserved resources.
[0061] Option 2 - LBT window within reserved resources:
[0062] o The UE performs LBT within the reserved resources and accesses the channel if LBT is successful (eg, no transmission detected on the reserved resources / energy is below a pre-configured threshold, eg, energy measured on the reserved resources or broadband). Figure 5 An example of this process is shown.
[0063] LBT failure detection and reporting
[0064] When the system operates in unlicensed spectrum, from the receiver's perspective, whether a particular transmission is not received due to poor channel conditions or due to LBT failure at the transmitter are completely equivalent, and it is impossible to discern between the two events unless clear procedures / indications are established / provided.
[0065] This can be applied to SL systems, especially unicast transmissions, where feedback information is expected from another UE. In this case, unless the physical sidelink feedback channel (PSFCH) is defined as short control signaling and no LBT is applied to it at the time of transmission, the transmission of the PSFCH will be conditional on the success of the LBT procedure and the UE can evaluate whether the channel is clear. In this sense, from the UE's perspective, if the PSFCH related to the previous transmission is not received, it can be interpreted as either the transmission was never received or the receiving UE could not transmit the PSFCH due to LBT failure. However, it cannot know exactly which one occurred, so performing a retransmission is a straightforward behavior. Although in order to alleviate the problem of not being able to transmit the PSFCH due to LBT failure, a retransmission can be triggered after a specific time defined by a timer to allow the receiving UE to attempt LBT multiple times. However, if a consistent LBT failure occurs at the receiving UE, this may not solve the problem and the transmitting UE will be forced to continue to perform retransmissions while the receiving UE has indeed received the intended transmission.
[0066] Embodiments in the present disclosure provide techniques for handling consistent LBT failures in SL, e.g., for both Mode 1 and Mode 2 SL operations. For example, when an LBT failure occurs at a UE for an intended SL transmission, the UE reports the event to upper layers of the UE. The UE may count the LBT failures that occur within a specific time, and if the number of LBT failures exceeds a threshold, send a report of consistent LBT failures. The report may be sent, for example, to a gNB or another UE. The receiving device may attempt to mitigate the problem, for example, through appropriate resource management.
[0067] Another important aspect when enabling SL design in unlicensed spectrum is that when operating in dynamic channel access mode, Type 1 LBT needs to be performed at the UE to initiate the channel occupation time (COT). However, as detailed in Table I, the maximum COT that can be obtained using this LBT channel access type and some of the details of this type of LBT depend on the channel access priority class (CAPC), which is configured by the network based on the type of services that the device can support and the quality of service (QoS) requirements that should be met.
[0068] Table I - Relationship between Channel Access Priority Class (CAPC) and MCOT
[0069]
[0070] Regarding the relationship between CAPC and QoS Control Indicator (QCI), Table II summarizes this, while Table III provides details in terms of priority class, packet delay budget, and packet error rate for each QCI.
[0071] Table II - Mapping between CAPC and QCI
[0072] Channel access priority class QCI 1 1 3 5 65 66 69 70 2 2 7 3 4 6 8 9 4 -
[0073] Table III - QCI to QoS characteristics mapping
[0074]
[0075]
[0076] However, it is to be noted that for SL, different QoS requirements have been defined which are mapped to specific PC5 5GNR standardized QoS identifiers (PQIs) as summarized in Table IV and indicated in the physical layer via the associated PQI via the per-packet SL ProSe Priority 5 (PPPP) indication provided within the SL Control Information (SCI).
[0077] Table IV: PQI to QoS characteristics mapping
[0078]
[0079]
[0080] Various embodiments in the present disclosure provide techniques for mapping between CAPC and PPPP. Considering that information related to CAPC is necessary for unlicensed operation, but CAPC will refer to and will be configured based on different QoS, some mapping between CAPC and PPPP may be required.
[0081] Another aspect described in the present disclosure is to allow SL systems operating in unlicensed spectrum to provide a further degree of coordination in terms of COT sharing, thereby allowing better spectrum utilization. Coordination can be used to allow a UE to request another device to initiate a COT and share its COT so that the UE's transmissions can fall within the COT of that device and can operate as a responding device. A variety of such schemes for both Mode 1 and Mode 2 SL operation are described in the present disclosure.
[0082] Report of SL COT sharing failure
[0083] As described above, when the system is operating in unlicensed spectrum, from the receiver's perspective, whether a particular transmission was not received due to poor channel conditions or due to LBT failure at the transmitter is completely equivalent, and it is impossible to discern between the two events unless clear routines / indications are established / provided. For example, in SL, the transmission of the PSFCH will be conditional on the success of the LBT procedure and the UE's assessment that the channel is clear. Therefore, from the UE's perspective, if the PSFCH associated with a previous transmission is not received, it can be interpreted as either the transmission was never received or the receiving UE could not transmit the PSFCH due to LBT failure, but it is not known exactly which one occurred, and therefore the direct behavior will be to perform a retransmission. Although in order to alleviate the problem of not being able to transmit the PSFCH due to LBT failure, a retransmission can be triggered after a specific time defined by a timer to allow the receiving UE to attempt LBT multiple times. However, if a consistent LBT failure occurs at the receiving UE, this may not solve the problem, and the transmitting UE will be forced to continue to perform retransmissions while the receiving UE has indeed received the intended transmission. Therefore, a method to signal consistent LBT failure to either the network or other UEs is advantageous so that different scheduling or behavior can be taken in this situation.
[0084] In one embodiment, when the SL system operates in Mode 1, one of the following options may be employed:
[0085] • Option 1: If the UE fails to access the channel(s) prior to the intended SL transmission, the UE does not need to take any action.
[0086] ● Option 2: If the UE fails to access the channel(s) before the expected SL transmission, then Layer 1 notifies higher layers of the channel access failure. In this regard, within higher layers, the device may count the LBT failures that occur within a specific time window. If the count within a given time window is greater than a given threshold, then this indicates that consistent LBT failures are occurring, and the device may report such indication back to the network if possible, so that the network can potentially make appropriate scheduling decisions to mitigate the problem.
[0087] o In one embodiment, this option may be applied if the SL transmission may carry one or more of the following SL physical channels:
[0088] ■Physical Sidelink Control Channel (PSCCH)
[0089] ■Physical Sidelink Shared Channel (PSSCH)
[0090] ■Physical Sidelink Feedback Channel (PSFCH)
[0091] ■Physical Sidelink Broadcast Channel (PSBCH)
[0092] ■Sidelink Synchronization Signal Block (S-SSB)
[0093] In one embodiment, when the SL system operates in Mode 2, one of the following options may be employed:
[0094] • Option 1: If the UE fails to access the channel(s) prior to the intended SL transmission, the UE does not need to take any action.
[0095] • Option 2: If the UE fails to access the channel(s) prior to the intended SL UL transmission, Layer 1 notifies higher layers of the channel access failure.
[0096] o In one embodiment, this option may be applied if the SL transmission may carry one or more of the following SL physical channels:
[0097] PSCCH
[0098] ■PSSCH
[0099] ■PSFCH
[0100] ■PSBCH
[0101] ■S-SSB
[0102] ○ In one embodiment, higher layers perform counting of LBT failures per link (e.g., one counter per UE with which the TX UE communicates), or per UE (e.g., a single counter is maintained per UE), or per UE group. If the counter within a given time window is greater than a given threshold, this indicates that a consistent LBT failure is occurring, and the device may report such indication in a subsequent transmission in a dedicated field in the SCI (either Phase 1 or Phase 2 or both) to the specific UE for which the relevant counter has triggered a consistent LBT failure, or to the group of UEs for which the relevant counter has triggered a consistent LBT failure, or to any UE (if the counter is maintained per UE).
[0103] ●Option 3: If the UE fails to access the channel(s) prior to the intended SL UL transmission, the UE may report such event back to the other UE or UEs intended to transmit to it by indicating this in a dedicated field in the SCI (either Phase 1 or Phase 2 or both) in subsequent transmissions to the other UE or UEs intended to transmit to it.
[0104] o In one embodiment, this option may be applied if the SL transmission may carry one or more of the following SL physical channels:
[0105] PSCCH
[0106] ■PSSCH
[0107] ■PSFCH
[0108] ■PSBCH
[0109] ■S-SSB
[0110] Relationship between SL priority and CAPC
[0111] For NR SL communications, PPPP is defined and mapped to the SL transmission priority at the radio layer, and as mentioned above, this is related to the specific QoS requirements that the transmission must meet. However, for NR-U operation, the concept of CAPC is defined. Based on the network configured / assigned CAPC, the device is allowed to transmit to different MCOTs after a Type 1 LBT with appropriate LBT measurement details specific to the CAPC used, as indicated in Table I. For NR-U, the selection of CAPC is determined by the network based on the QoS that should be met, and as indicated in Tables II and III, there is a relationship between the CAPC and the QoS characteristics that the transmission should ensure.
[0112] From a physical layer perspective, it is desirable to indicate a parameter that can determine the channel access behavior of the UE in terms of resource allocation, but also has a relationship with QoS characteristics that must be met. According to various embodiments in the present disclosure, one of the following options may be adopted. Figure 6 The mapping of CAPC and / or PPPP to SL transport priorities is shown for the following options.
[0113] Option 1: Only PPPP-based SL priority is used for SL communications in unlicensed spectrum.
[0114] Option 2: Only CAPC is used for SL communications in unlicensed spectrum.
[0115] o In this case, CAPC is used for either 1) UE LBT based channel access, or 2) SL sensing and resource selection procedures, or both.
[0116] o In one sub-option, the bits used by the field in the SCI that carries the PPPP information are either ignored or not used, and two additional bits are included in the SCI to indicate the CAPC used. In another sub-option, the bits used by the field in the SCI that carries the PPPP information are partially flushed to carry a 2-bit indication for the CAPC, and the remaining bits are either removed from the SCI payload or ignored.
[0117] Option 3: Redefine SL priority (or CAPC) based on PPPP and CAPC parameters (or introduce new parameters).
[0118] o In this case, CAPC is used for either 1) UE LBT based channel access, or 2) SL sensing and resource selection procedures, or both.
[0119] ■ Option 3A: CAPC is used for SL communications in unlicensed spectrum, and the mapping between CAPC and QCI is enhanced to include PQI for SL (e.g., 21, 22, 23, 55, 56, 57, 58, 59, 90, and 91).
[0120] As an example, the new mapping may be as shown in Table V.
[0121] Table V - Mapping between CAPC and QCI / PQI
[0122] Channel access priority class QCI / PQI 1 1,3,5,65,66,69,70,21,22,55,56,57,90, 2 2,7,23,58 3 4,6,8,9,59 4 --
[0123] o In one option, the bits used by the field in the SCI that carries PPPP information are either ignored or unused, and two additional bits are included in the SCI to indicate the CAPC used.
[0124] o In a different option, the bits used by the field in the SCI that carries the PPPP information are partially flushed to carry the 2-bit indication for CAPC, while the remaining bits are either removed from the SCI payload or ignored.
[0125] ■ Option 3B: CAPC is used for SL communication in unlicensed spectrum, and a mapping between CAPC and PQI for SL is formed (e.g., 21, 22, 23, 55, 56, 57, 58, 59, 90, and 91).
[0126] As an example, the new mapping can be shown in Table VI
[0127] Table VI - Mapping between CAPC and PQI
[0128] Channel access priority class OCI / PQI 1 21,22,55,56,57,90,91 2 23,58 3 59 4 -
[0129] o In one option, the bits used by the field in the SCI that carries PPPP information are either ignored or unused, and two additional bits are included in the SCI to indicate the CAPC used.
[0130] o In a different option, the bits used by the field in the SCI that carries the PPPP information are partially flushed to carry the 2-bit indication for CAPC, while the remaining bits are either removed from the SCI payload or ignored.
[0131] ■ Option 3C: A PQI is assigned to a specific CAPC or vice versa (eg, using the mapping provided in Table V or Table VI), and the PPPP field in the SCI jointly indicates the corresponding PQI and CAPC.
[0132] ■ Option 3D: A new parameter is defined which indicates PPPP and CAPC together.
[0133] o In one option, the bits used by the field in the SCI that carries PPPP information are either ignored or unused, and an additional bit is included in the SCI to indicate the new parameter.
[0134] o In a different option, the bits used by the field in the SCI that carries the PPPP information are refreshed to carry bits indicating the new parameters.
[0135] Option 4: Use both CAPC and SL transmission priorities, where SL transmission priority is a function of PPPP
[0136] o In this option, CAPC can be used to determine the LBT-based sidelink channel access procedure, while the sidelink transmission priority can be reused for the sidelink sensing and resource selection procedure.
[0137] o In one option, the SCI payload (Phase 1 or Phase 2 or both) may be extended to additionally contain an additional 2 bits to indicate CAPC. In a different option, some of the unused bits within the SCI payload (Phase 1 or Phase 2 or both) may be repurposed and used to carry a 2-bit indication for CAPC.
[0138] Method to request to initiate SL COT
[0139] As discussed above, when the SL operates in Mode 1, for example, with deployments where decoding / sensing from the gNB is allowed / possible, another possible enhancement that may be applied is to enable further coordination between devices by allowing the UE to request another device to initiate a COT and share its COT so that the UE's transmissions can fall within the COT of that device and can operate as a responding device. This may be particularly useful for Configuration Grant (CG) transmissions, where resources are pre-configured and dynamic allocation is not possible, and the allocated resources cannot be changed based on the UE's current buffer occupancy. Furthermore, this may be even more useful for CG transmissions with cg-RetransmissionTimer enabled, as the UE can operate in an autonomous manner and in principle can compete for resources with either the gNB or other UEs, while the gNB may not be aware of the UE's current buffer occupancy.
[0140] In one embodiment, the SCI (either Stage 1 or Stage 2 or both) may be enhanced to include one or more of the following information that may be used to achieve the above objectives:
[0141] ○ An indication of the UE's intent to request COT, which may be interpreted as follows:
[0142] ○Alternative 1: The UE periodically requests the intent of COT from other devices from one or more of the following.
[0143] o Alternative 2: The UE requests the intent of COT from other devices from a specific start time, which is indicated separately.
[0144] o The start of the requested time domain resources (either in slot or symbol granularity) where the UE is requesting some other device to acquire the COT.
[0145] ○ The amount of time to request a COT from another device, which may indicate one of the following alternatives:
[0146] ○Alternative 1: Number of consecutive cycles.
[0147] o Alternative 2: The number of symbols or time slots starting from the requested time domain resource, which may be indicated separately.
[0148] When the SL system is operating in Mode 2, a UE requesting another UE to initiate sidelink COT sharing may be particularly beneficial in the case of unicast or multicast communications, and one of the possible use cases may be that the UE as the actual initiating device wants to publish its COT and allow another device to operate as the initiating device even if the MCOT of that device has not yet terminated, in order to ensure that the device can transmit later when its own MCOT may have terminated. This is in Figure 7 Shown in.
[0149] In one embodiment, when the SL system operates in Mode 2, one of the following options may be employed:
[0150] ● Option 1: An additional field may be carried in the SCI (either Phase 1 or Phase 2, or both), indicating that UE#1 wants to publish its COT if the transmission still falls within its initial COT, or that UE#1 wants to operate as a responding device regardless of who is the current initiating device.
[0151] ● Option 2: Field indicating whether the device is operating as an initiating or responding device and / or whether the remaining COT information is for issuing COT:
[0152] o The initiating device may later indicate within its COT that the remaining COT is 0, which may be interpreted by other devices as the COT for this UE having terminated.
[0153] o The initiating device may later indicate within its COT that it is operating as a responding device, and collectively indicate that the remaining COT is 0: this may again be interpreted by other devices as the COT for this UE having terminated, and that this UE is requesting.
[0154] System and implementation
[0155] Figures 8 to 10 Various systems, devices, and components are shown that can implement aspects of the disclosed embodiments.
[0156] Figure 8 A network 800 according to various embodiments is shown. The network 800 may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this regard, and the described embodiments may be applied to other networks that benefit from the principles described in the present disclosure, such as future 3GPP systems, etc.
[0157] The network 800 may include a UE 802, which may include any mobile or non-mobile computing device designed to communicate with the RAN 804 via an over-the-air connection. The UE 802 may be communicatively coupled to the RAN 804 via a Uu interface. The UE 802 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, a dashboard, a head-up display device, an on-board diagnostic device, a dash cam 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 device, a machine type communication device, an M2M or D2D device, an IoT device, etc.
[0158] In some embodiments, the network 800 may include multiple UEs directly coupled to each other via a sidelink interface. The UE may be an M2M / D2D device that communicates using a physical sidelink channel such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
[0159] In some embodiments, UE 802 may additionally communicate with AP 806 via an over-the-air connection. AP 806 may manage a WLAN connection that may be used to offload some / all network traffic from RAN 804. The connection between UE 802 and AP 806 may be consistent with any IEEE 802.11 protocol, where AP 806 may be a Wireless Fidelity Router. In some embodiments, UE 802, RAN 804, and AP 806 may utilize cellular WLAN aggregation (eg, LWA / LWIP). Cellular WLAN aggregation may involve configuring UE 802 by RAN 804 to utilize both cellular radio resources and WLAN resources.
[0160] RAN 804 may include one or more access nodes, such as access node (AN) 808. AN 808 may terminate the air interface protocol of UE 802 by providing access layer protocols including RRC, PDCP, RLC, MAC and L1 protocols. In this way, AN 808 may implement data / voice connection between CN 820 and UE 802. In some embodiments, AN 808 may be implemented in a discrete device or as one or more software entities running on a server computer as part of a virtual network, such as a CRAN or a virtual baseband unit pool. AN 808 is referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 808 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.
[0161] In an embodiment where the RAN 804 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 804 is an LTE RAN) or an Xn interface (if the RAN 804 is a 5G RAN). In some embodiments, the X2 / Xn interface, which may be separated into a control / user plane interface, may allow the AN to transmit information related to handover, data / context transfer, mobility, load management, interference coordination, etc.
[0162] The ANs of the RAN 804 may each manage one or more cells, cell groups, component carriers, etc. to provide an air interface for network access to the UE 802. The UE 802 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 804. For example, the UE 802 and the RAN 804 may use carrier aggregation to allow the UE 802 to connect to multiple component carriers, each corresponding to a Pcell or an 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.
[0163] RAN 804 can provide an air interface through a licensed spectrum or an unlicensed spectrum. In order to operate in an unlicensed spectrum, a node can use LAA, eLAA and / or feLAA mechanisms based on CA technology with PCell / Scell. Before accessing an unlicensed spectrum, a node can perform a medium / carrier sensing operation based on, for example, a listen-before-talk (LBT) protocol.
[0164] In the V2X scenario, the UE 802 or AN 808 may be or act as an RSU, which may refer to any transportation infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable An or a stationary (or relatively stationary) 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, the RSU is a computing device coupled to a radio frequency circuit system located on the roadside that provides connection support for passing vehicle UEs. The RSU may also include an internal data storage circuit system to store intersection map geometry, traffic statistics and media, and applications / software to sense and control ongoing vehicle and pedestrian traffic. The RSU may provide very low latency communications required for high-speed events such as collision avoidance, traffic warnings, etc. 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 (e.g., Ethernet) to a traffic signal controller or backhaul network.
[0165] In some embodiments, the RAN 804 may be an LTE RAN 810 with an eNB (e.g., eNB 812). The LTE RAN 810 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 codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and 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.
[0166] In some embodiments, the RAN 804 may be a NG-RAN 814 having a gNB (e.g., gNB 816) or an ng-eNB (e.g., ng-eNB 818). The gNB 816 may be connected to a 5G-enabled UE using a 5G NR interface. The gNB 816 may be connected to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 818 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 816 and the ng-eNB 818 may be connected to each other via an Xn interface.
[0167] In some embodiments, the NG interface can be divided into two parts, an NG user plane (NG-U) interface (e.g., N3 interface) that carries service data between the nodes of the NG-RAN 814 and the UPF 848, and an NG control plane (NG-C) interface, which is a signaling interface (e.g., N2 interface) between the nodes of the NG-RAN 814 and the AMF 844.
[0168] NG-RAN 814 may provide a 5G-NR air interface with the following features: variable SCS; CP-OFDM, CP-OFDM for DL, and DFT-s-OFDM for UL; polarity, repetition, simplex, and Reed-Muller codes for control, and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS. 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 a FR1 band including bands below 6 GHz, or on a FR2 band including bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB, which is an area of a downlink resource grid including PSS / SSS / PBCH.
[0169] In some embodiments, the 5G-NR air interface may use BWP for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, UE 802 may be configured with multiple BWPs, each of which is configured with a different SCS. When a BWP change is indicated to UE 802, the SCS of the transmission is also changed. Another use case example of BWP is related to power saving. In particular, multiple BWPs with different amounts of frequency resources (e.g., PRBs) may be configured for UE 802 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 saving at UE 802 and in some cases at gNB 816. A BWP containing a large number of PRBs may be used in scenarios with higher traffic loads.
[0170] RAN 804 is communicatively coupled to CN 820, which includes network elements that provide various functions to support data and telecommunication services to customers / subscribers (e.g., users of UE 802). Components of CN 820 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be used to virtualize any or all functions provided by the network elements of CN 820 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of CN 820 may be referred to as a network slice, and a logical instantiation of a portion of CN 820 may be referred to as a network sub-slice.
[0171] In some embodiments, CN 820 may be LTE CN 822, which may also be referred to as EPC. LTE CN 822 may include MME 824, SGW 826, SGSN 828, HSS 830, PGW 832, and PCRF 834 coupled to each other via interfaces (or "reference points"), as shown. The functions of the elements of LTE CN 822 may be briefly described as follows.
[0172] The MME 824 may implement mobility management functions to track the current location of the UE 802 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.
[0173] The SGW 826 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 822. The SGW 826 may be the local mobility anchor 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.
[0174] SGSN 828 may track the location of UE 802 and perform security functions and access control. In addition, SGSN 828 may perform inter-EPC node signaling for mobility between different RAT networks; perform PDN and S-GW selection as specified by MME 824; perform MME handover selection; etc. The S3 reference point between MME 824 and SGSN 828 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active states.
[0175] The HSS 830 may include a database for network users that includes subscription-related information to support network entities' handling of communication sessions. The HSS 830 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. The S6a reference point between the HSS 830 and the MME 824 may enable the transfer of subscription and authentication data for authenticating / authorizing users to access the LTE CN 820.
[0176] The PGW 832 may terminate the SGi interface pointing to a data network (DN) 836, which may include an application / content server 838. The PGW 832 may route data packets between the LTE CN 822 and the data network 836. The PGW 832 may be coupled to the SGW 826 via an S5 reference point to facilitate user plane tunnels and tunnel management. The PGW 832 may also include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 832 and the data network 836 may be an operator external public, private PDN, or an operator internal packet data network, for example, for providing IMS services. The PGW 832 may be coupled to the PCRF 834 via a Gx reference point.
[0177] PCRF 834 is the policy and charging control element of LTE CN 822. PCRF 834 may be communicatively coupled to application / content server 838 to determine appropriate QoS and charging parameters for service flows. PCRF 834 may provide the associated rules to PCEF (via Gx reference point) with the appropriate TFT and QCI.
[0178] In some embodiments, CN 820 may be 5GC 840. 5GC 840 may include AUSF 842, AMF 844, SMF 846, UPF 848, NSSF 850, NEF 852, NRF 854, PCF 856, UDM 858, and AF 860 coupled to each other via interfaces (or "reference points"), as shown. The functions of the elements of 5GC 840 may be briefly described as follows.
[0179] AUSF 842 can store data for authentication of UE 802 and handle authentication-related functions. AUSF 842 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 840 through reference points as shown, AUSF 842 can also expose interfaces based on Nausf services.
[0180] AMF 844 may allow other functions of 5GC 840 to communicate with UE 802 and RAN 804, and subscribe to notifications about mobility events related to UE 802. AMF 844 may be responsible for registration management (e.g., for registering UE 802), connection management, reachability management, mobility management, legal interception of AMF-related events, and access authentication and authorization. AMF 844 may provide transport for SM messages between UE 802 and SMF 846, and act as a transparent proxy for routing SM messages. AMF 844 may also provide transport for SMS messages between UE 802 and SMSF. AMF 844 may interact with AUSF 842 and UE 802 to perform various security anchor and context management functions. In addition, AMF 844 may be a termination point for the RAN CP interface, which may include or may be an N2 reference point between RAN 804 and AMF 844; and AMF 844 may be a termination point for NAS (N1) signaling, and performs NAS encryption and integrity protection. AMF 844 may also support NAS signaling with UE 802 over the N3 IWF interface.
[0181] SMF 846 may be responsible for SM (e.g., session establishment, tunnel management between UPF 848 and AN 808); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering at UPF 848 to route traffic to the appropriate destination; terminating interfaces toward policy control functions; controlling policy enforcement, charging, and some of QoS; lawful interception (for SM events and LI system interfaces); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN 808 via AMF 844 over N2; and determining the SSC mode for the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between UE 802 and data network 836.
[0182] The UPF 848 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected to the data network 836, and a branch point for supporting multi-homed PDU sessions. The UPF 848 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 service usage reporting, perform QoS handling of the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink service verification (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 848 may include an uplink classifier to support routing of service flows to the data network.
[0183] NSSF 850 may select a set of network slice instances to serve UE 802. If necessary, NSSF 850 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI. NSSF 850 may also determine the AMF group or the list of candidate AMFs to be used to serve UE 802 based on appropriate configuration and possibly by querying NRF 854. The selection of a set of network slice instances for UE 802 may be triggered by AMF 844, with which UE 802 registers by interacting with NSSF 850, which may cause a change in AMF. NSSF 850 may interact with AMF 844 via the N22 reference point; and may communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, NSSF 850 may expose an interface based on Nnssf services.
[0184] NEF 852 can securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AF (e.g., AF 860), edge computing or fog computing systems, etc. In such embodiments, NEF 852 can authenticate, authorize or restrict AF. NEF 852 can also translate information exchanged with AF 860 and information exchanged with internal network functions. For example, NEF 852 can translate between AF service identifiers and internal 5GC information. NEF 852 can also receive information from other NFs based on the exposure capabilities of other NFs. The information can be stored at NEF 852 as structured data, or stored at a data storage NF using a standardized interface. The stored information can then be re-exposed to other NFs and AFs by NEF 852, or used for other purposes such as analysis. In addition, NEF 852 can display interfaces based on Nnef services.
[0185] NRF 854 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 854 also maintains information about available NF instances and the services they support. As used in this disclosure, the terms "instantiate," "instantiation," and the like may refer to the creation of an object, and "instance" may refer to a specific occurrence of an object, such as may occur during the execution of program code. In addition, NRF 854 may expose an interface based on Nnrf services.
[0186] PCF 856 can provide policy rules to control plane functions to enforce them, and can also support a unified policy framework to manage network behavior. PCF 856 can also implement a front end to access subscription information related to policy decisions in the UDR of UDM 858. In addition to communicating with functions through reference points as shown in the figure, PCF 856 also exposes an interface based on Npcf services.
[0187] The UDM 858 may handle subscription-related information to support the handling of communication sessions by network entities, and may store subscription data for the UE 802. For example, the subscription data may be transmitted via the N8 reference point between the UDM 858 and the AMF 844. The UDM 858 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 858 and the PCF 856, and / or structured data for exposure and application data for the NEF 852 (including PFD for application detection and application request information for multiple UEs 802). Nudr service-based interfaces may be displayed by the UDR221 to allow the UDM 858, PCF 856, and NEF 852 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of changes to related data in the UDR. The UDM may include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 858 can also expose Nudm service-based interfaces.
[0188] AF 860 may provide application influence on service routing, provide access to NEF, and interact with the policy framework for policy control.
[0189] In some embodiments, 5GC 840 can implement edge computing by selecting an operator / third-party service geographically close to the point where UE 802 attaches to the network. This can reduce latency and load on the network. In order to provide an edge computing implementation, 5GC 840 can select a UPF 848 close to UE 802 and perform service guidance from UPF 848 to data network 836 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 860. In this way, AF 860 can affect UPF (re)selection and service routing. Based on operator deployment, when AF 860 is considered a trusted entity, the network operator can allow AF 860 to interact directly with related NFs. In addition, AF 860 can expose an interface based on Naf services.
[0190] The data network 836 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers (including, for example, an application / content server 838).
[0191] Fig. 9 A wireless network 900 is schematically illustrated in accordance with various embodiments. The wireless network 900 may include a UE 902 in wireless communication with an AN 904. The UE 902 and AN 904 may be similar to, and substantially interchangeable with, similarly named components described elsewhere in this disclosure.
[0192] UE 902 may be communicatively coupled with AN 904 via connection 906. Connection 906 is shown as an air interface to implement the communicative coupling and may be consistent with a cellular communication protocol operating at mmWave or sub-6 GHz frequencies, such as an LTE protocol or a 5G NR protocol.
[0193] UE 902 may include a host platform 908 coupled to a modem platform 910. Host platform 908 may include application processing circuitry 912, which may be coupled to protocol processing circuitry 914 of modem platform 910. Application processing circuitry 912 may run various applications that source / aggregate application data for UE 902. Application processing circuitry 912 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.
[0194] Protocol processing circuitry 914 may implement one or more layer operations to facilitate transmission or reception of data over connection 906. The layer operations implemented by protocol processing circuitry 914 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.
[0195] The modem platform 910 may further include a digital baseband circuit system 916, which may implement one or more layer operations, which are "lower" layer operations in the network protocol stack performed by the protocol processing circuit system 914. For example, these operations may include PHY operations, which include one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multiple 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.
[0196] The modem platform 910 may further include a transmit circuit system 918, a receive circuit system 920, an RF circuit system 922, and an RF front end (RFFE) 924, which may include or be connected to one or more antenna panels 926. In brief, the transmit circuit system 918 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receive circuit system 920 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit system 922 may include a low noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 924 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 system 918, the receive circuit system 920, the RF circuit system 922, the RFFE 924, and the antenna panel 926 (collectively referred to as the "transmit / receive component") may be specific to the details of a particular implementation, such as, for example, whether the communication is TDM or FDM, millimeter wave or sub-6 GHz frequency, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be provided in the same or different chips / modules, and so on.
[0197] In some embodiments, protocol processing circuitry 914 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.
[0198] UE reception may be established by and via antenna panel 926, RFFE 924, RF circuitry 922, receive circuitry 920, digital baseband circuitry 916, and protocol processing circuitry 914. In some embodiments, antenna panel 926 may receive transmissions from AN 904 via receive beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 926.
[0199] UE transmissions may be established by and via protocol processing circuitry 914, digital baseband circuitry 916, transmit circuitry 918, RF circuitry 922, RFFE 924, and antenna panel 926. In some embodiments, the transmit component of UE 902 may apply spatial filtering to the data to be transmitted to form transmit beams emitted by the antenna elements of antenna panel 926.
[0200] Similar to UE 902, AN 904 may include a host platform 928 coupled to a modem platform 930. The host platform 928 may include an application processing circuit system 932 coupled to a protocol processing circuit system 934 of the modem platform 930. The modem platform may further include a digital baseband circuit system 936, a transmit circuit system 938, a receive circuit system 940, an RF circuit system 942, an RFFE circuit system 944, and an antenna panel 946. The components of AN 904 may be similar to the similarly named components of UE 902 and may be substantially interchangeable. In addition to performing data transmission / reception as described above, the components of AN 904 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.
[0201] Fig.10 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed in the present disclosure according to some example embodiments. Specifically, Fig.10 A diagram of hardware resources 1000 is shown, which includes one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which can be communicatively coupled via a bus 1040 or other interface circuitry. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1002 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1000.
[0202] The one or more processors 1010 may include, for example, a processor 1012 and a processor 1014. The processor 1010 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing processor (CISC), 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 the processors discussed in the present disclosure), or any suitable combination thereof.
[0203] The memory / storage device 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1020 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 variable memory read-only memory (EPROM), electrically erasable variable memory read-only memory (EEPROM), flash memory, solid-state storage, etc.
[0204] The communication resources 1030 may include an interconnect or network interface controller, component, or other suitable means to communicate with one or more peripheral devices 1004 or one or more databases 1006 or other network elements via the network 1008. For example, the communication resources 1030 may include a wired communication component (e.g., for coupling via USB, Ethernet, etc.), a cellular communication component, an NFC component, (or Low energy) components, components and other communication components.
[0205] The instructions 1050 may include software, programs, applications, applet, applications, or other executable code for causing at least one of the processors 1010 to perform at least one or more of the methods discussed in the present disclosure. The instructions 1050 may reside in whole or in part in at least one of the processor 1010 (e.g., in a cache memory of the processor), the memory / storage device 1020, or any suitable combination thereof. In addition, any portion of the instructions 1050 may be passed to the hardware resources 1000 from any combination of the peripheral device 1004 or the database 1006. Therefore, the memory of the processor 1010, the memory / storage device 1020, the peripheral device 1004, and the database 1006 are examples of computer-readable and machine-readable media.
[0206] Sample Program
[0207] In some embodiments, Figures 8 to 10 The electronic device(s), network(s), system(s), chip(s) or component(s) or parts or implementations of some other figures in the present disclosure may be configured to perform one or more processes, techniques or methods described in the present disclosure or parts thereof. Such a process 1100 Fig.11. Process 1100 may be performed by a user equipment (UE), one or more elements of a UE, or an electronic device including a UE. At 1102, process 1100 may include receiving sidelink control information (SCI) including an indication of a channel access priority category (CAPC) for a sidelink transmission. At 1104, process 1100 may further include determining a first PC5 quality of service (QoS) identifier (PQI) for the sidelink transmission from one or more PQIs associated with the CAPC. At 1106, process 1100 may further include performing a sidelink transmission based on the CAPC and the first PQI.
[0208] Fig.12 Another example process 1200 is shown in accordance with various embodiments. The process 1200 may be performed by a UE, one or more elements of a UE, or an electronic device including a UE. At 1202, the process 1200 may include determining that a number of listen-before-talk (LBT) failures on a sidelink channel over a period of time exceeds a threshold. At 1204, the process 1200 may further include sending a report to indicate consistent LBT failures based on the determination.
[0209] Fig.13 Another example process 1300 is shown according to various embodiments. The process 1300 may be performed by a UE, one or more elements of a UE, or an electronic device including a UE. At 1302, the process 1300 may include performing a sidelink sensing and resource selection procedure to select a sidelink resource for a sidelink transmission. At 1304, the process 1300 may further include performing a listen-before-talk (LBT) procedure on the selected sidelink resource. At 1306, the process 1300 may further include, if the LBT procedure is successful, performing a sidelink transmission in the selected sidelink resource.
[0210] 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 Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, the circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below in the Examples section.
[0211] Example
[0212] Example A1 may include one or more non-transitory computer readable media (NTCRMs) having instructions stored thereon that, when executed by one or more processors of a user equipment (UE), configure the UE to:
[0213] receiving sidelink control information (SCI) including an indication of a channel access priority class (CAPC) for a sidelink transmission,
[0214] determining a first PC5 quality of service (QoS) identifier (PQI) for the sidelink transmission from one or more PQIs associated with the CAPC; and
[0215] The sidelink transmission is performed based on the CAPC and the first PQI.
[0216] Example A2 may include one or more non-transitory computer-readable media (NTCRM) of Example A1, wherein the instructions, when executed, further configure the UE to:
[0217] determining a maximum channel occupancy time for the sidelink transmission based on the CAPC; and
[0218] One or more QoS characteristics for the sidelink transmission are determined based on the first PQI.
[0219] Example A3 may include the one or more non-transitory computer-readable media (NTCRM) of Example A1, wherein the first PQI is determined according to the following table based on an association between the PQI and the corresponding CAPC:
[0220] Channel access priority class() <![CDATA[ p QoS Control Indicator (QCI) / PQI]]> 1 1,3,5,65,66,69,70,21,22,55,56,57,90,91 2 2,7,23,58 3 4,6,8,9,59 4 -- .
[0221] Example A4 may include the one or more non-transitory computer-readable media (NTCRM) of any one of Examples A1 to A3, wherein the SCI further includes an indication of a per-packet ProSe priority (PPPP) for the sidelink transmission, wherein the sidelink transmission is further performed based on the PPPP.
[0222] Example A5 may include the one or more non-transitory computer-readable media (NTCRM) of Example A4, wherein the instructions, when executed, further configure the UE to:
[0223] determining a sidelink transmission priority for the sidelink transmission based on the PPPP; and
[0224] A sidelink sensing and resource selection procedure for the sidelink transmission is performed based on the sidelink transmission priority.
[0225] Example A6 may include the one or more non-transitory computer-readable media (NTCRM) of Example A5, wherein the instructions, when executed, further configure the UE to determine a listen-before-talk (LBT)-based sidelink channel access procedure for the sidelink transmission based on the CAPC.
[0226] Example A7 may include the one or more non-transitory computer-readable media (NTCRM) of any one of Examples A1 to A3, wherein the SCI does not indicate a per-packet ProSe priority (PPPP) for the sidelink transmission, or the PPPP indicated by the SCI is ignored for the sidelink transmission.
[0227] Example A8 may include one or more non-transitory computer readable media (NTCRMs) having instructions stored thereon, the instructions, when executed by one or more processors of a user equipment (UE), configuring the UE to:
[0228] determining that a number of listen-before-talk (LBT) failures on the sidelink channel exceeds a threshold over a period of time, and
[0229] A report is sent based on the determination to indicate a consistent LBT failure.
[0230] Example A9 may include the one or more non-transitory computer-readable media (NTCRM) of Example A8, wherein the UE is in sidelink mode 1.
[0231] Example A10 may include the one or more non-transitory computer-readable media (NTCRM) of Example A8, wherein the UE is in sidelink mode 2.
[0232] Example A11 may include the one or more non-transitory computer-readable media (NTCRM) of Example A8, wherein the report is sent to the gNB.
[0233] Example A12 may include the one or more non-transitory computer-readable media (NTCRM) of any of Examples A8 to A11, wherein the determination is associated with the UE attempting to transmit a physical sidelink feedback channel (PSFCH).
[0234] Example A13 may include one or more non-transitory computer readable media (NTCRMs) having instructions stored thereon, which when executed by one or more processors of a user equipment (UE) configure the UE to:
[0235] performing a sidelink sensing and resource selection procedure to select a sidelink resource for sidelink transmission;
[0236] performing a listen-before-talk (LBT) procedure on the selected sidelink resource; and
[0237] If the LBT procedure is successful, the sidelink transmission is performed in the selected sidelink resource.
[0238] Example A14 may include the one or more non-transitory computer-readable media (NTCRM) of Example A13, wherein the side link sensing and resource selection procedure is performed based on an energy detection threshold of the LBT procedure.
[0239] Example A15 may include the one or more non-transitory computer-readable media (NTCRM) of Example A13, wherein the sidelink sensing and resource selection procedure includes sensing activity on resources of a channel and excluding one or more of the resources from a candidate resource set based on the sensed activity, wherein the sidelink resources are selected from the candidate resource set for the sidelink transmission.
[0240] Example A16 may include the one or more non-transitory computer-readable media (NTCRM) of Example A13, wherein the LBT procedure is performed within a cyclic prefix extension prior to the selected side link resource.
[0241] Example A17 may include the one or more non-transitory computer-readable media (NTCRMs) of Example A13, wherein the selected side link resources include continuous time slots.
[0242] Example A18 may include the one or more non-transitory computer-readable media (NTCRM) of Example A17, wherein the instructions, when executed, further configure the UE to determine support for selection of the continuous time slots based on one or more conditions.
[0243] Example A19 may include the one or more non-transitory computer-readable media (NTCRM) of Example A18, wherein the one or more conditions include one or more of the following:
[0244] a packet delay budget less than a first predetermined value;
[0245] a remaining packet delay budget less than a second predetermined value;
[0246] A channel busy ratio (CBR) less than a third predetermined value; or
[0247] A condition based on the priority of the sidelink transmission or a channel access priority condition (CAPC).
[0248] Example A20 may include the one or more non-transitory computer-readable media (NTCRM) of any of Examples A13 to A19, wherein the sidelink sensing and resource selection procedure prioritizes the earliest resources in time.
[0249] Example B1 may include a method for enabling a SL system to operate in an unlicensed spectrum.
[0250] Example B2 may include the method of Example B1 or some other examples in the present disclosure, further including LBT and sensing and resource (re)selection procedures in a SL system operating in an unlicensed spectrum.
[0251] Example B3 may include the method of Example B1 or some other examples in the present disclosure, further including an enhancement to the resource (re)selection procedure in a SL system operating in an unlicensed spectrum.
[0252] Example B4 may include the method of Example B1 or some other examples in the present disclosure, further including a method for enabling resource selection of back-to-back resources in a SL system operating in an unlicensed spectrum.
[0253] Example B5 may include the method of Example B1 or some other examples in the present disclosure, further including a method for allowing transmission on reserved unutilized resources in a SL system operating in an unlicensed spectrum.
[0254] Example B6 may include a method of a UE, comprising: performing a side link sensing and resource selection procedure to select a side link resource for transmission based on a listen-before-talk (LBT) threshold of the LBT procedure; and performing the transmission in the selected side link resource.
[0255] Example B7 may include the method of Example B6 or some other examples in the present disclosure, wherein the LBT procedure is performed on the selected side link resource prior to the transmission.
[0256] Example Cl may include a method for handling LBT failure in a SL system operating in mode 1 in an unlicensed band.
[0257] Example C2 may include a method for handling LBT failures in a SL system operating in Mode 2 in an unlicensed band.
[0258] Example C3 may include a method of requesting another UE to initiate and share a SL COT interval in a SL system operating in mode 1 in an unlicensed band.
[0259] Example C4 may include a method of requesting another UE to initiate and share a SL COT interval in a SL system operating in mode 2 in an unlicensed band.
[0260] Example C5 may include a method of mapping and associating SL priorities and CAPCs within a SL system operating in an unlicensed band.
[0261] Example C6 may include a method of a UE, the method comprising: determining that a number of listen-before-talk (LBT) failures on a sidelink channel exceeds a threshold; and sending a report to indicate consistent LBT failures based on the determination.
[0262] Example C7 may include the method of Example C6 or some other examples in the present disclosure, wherein the UE is in sidelink mode 1.
[0263] Example C8 may include the method of Example C6 or some other examples in the present disclosure, wherein the UE is in sidelink mode 2.
[0264] Example C9 may include the method of Examples C6 to C8 or some other examples in the present disclosure, wherein the report is sent to the gNB.
[0265] Example C10 may include the method of Examples C6 to C9 or some other examples in the present disclosure, wherein the determination is associated with the UE attempting to transmit a sidelink message.
[0266] Example C11 may include the method of Example C10 or some other examples in the present disclosure, wherein the sidelink message is PSCCH, PSSCH, PSFCH, PSBCH and / or S-SSB.
[0267] Example Z01 may include a device comprising measures for performing one or more elements of a method described in or related to any of Examples A1 to A20, B1 to B7, C1 to C11, or any other method or process described in the present disclosure.
[0268] Example Z02 may include one or more non-transitory computer-readable media, which include instructions that cause an electronic device to perform one or more elements of a method described in or related to any of Examples A1 to A20, B1 to B7, C1 to C11, or any other method or process described in the present disclosure when the instructions are executed by one or more processors of the electronic device.
[0269] Example Z03 may include a device comprising logic, modules, or circuit systems to perform one or more elements of a method described in or related to any of Examples A1 to A20, B1 to B7, C1 to C11, or any other method or process described in the present disclosure.
[0270] Example Z04 may include methods, techniques, or processes as described in or related to any of Examples A1 to A20, B1 to B7, C1 to C11, or portions or parts thereof.
[0271] Example Z05 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform methods, techniques, or processes described in or related to any one of Examples A1 to A20, B1 to B7, C1 to C11, or portions thereof.
[0272] Example Z06 may include signals as described in or related to any of Examples A1 to A20, B1 to B7, C1 to C11, or portions or parts thereof.
[0273] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described or related in Examples A1 to A20, B1 to B7, C1 to C11, or portions or parts thereof, or otherwise described in the present disclosure.
[0274] Example Z08 may include a signal encoded with data as described in or related to Examples A1 to A20, B1 to B7, C1 to C11, or portions or parts thereof, or otherwise described in this disclosure.
[0275] Example Z09 may include a signal encoded in a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to Examples A1 to A20, B1 to B7, C1 to C11, or portions or parts thereof, or otherwise described in the present disclosure.
[0276] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein the computer-readable instructions are executed by one or more processors to cause the one or more processors to perform a method, technique, or process as described in or related to any one of Examples A1 to A20, B1 to B7, C1 to C11, or a portion thereof.
[0277] 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 as described in or related to any one of Examples A1 to A20, B1 to B7, C1 to C11, or a portion thereof.
[0278] Example Z12 may include a signal in a wireless network as shown and described in this disclosure.
[0279] Example Z13 may include a method of communicating in a wireless network as shown and described in this disclosure.
[0280] Example Z14 may include a system for providing wireless communications as shown and described in this disclosure.
[0281] Example Z15 may include an apparatus for providing wireless communications as shown and described in this disclosure.
[0282] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be obtained from the practice of the various embodiments.
[0283] abbreviation
[0284] Unless used differently in this disclosure, the terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR21.905v16.0.0 (2019-06). For the purposes of this disclosure, the following abbreviations may be applied to the examples and embodiments discussed in this disclosure.
[0285] 3GPP Third Generation Partnership Project
[0286] 4G Fourth Generation
[0287] 5G Fifth Generation
[0288] 5GC 5G Core Network
[0289] AC Application Customers
[0290] ACR Application Context Relocation
[0291] ACK
[0292] ACID Application Client Identity
[0293] AF Application Function
[0294] AM Confirmation Mode
[0295] AMBR Aggregate Maximum Bit Rate
[0296] AMF Access and Mobility Management Function
[0297] AN Access Network
[0298] ANR Automatic Neighbor Relation
[0299] AOA Angle of Arrival
[0300] AP application protocol, antenna port, access point
[0301] API Application Programming Interface
[0302] APN Access Point Name
[0303] ARP Allocation and Reservation Priority
[0304] ARQ Automatic Repeat Request
[0305] AS Access Layer
[0306] ASP Application Service Provider
[0307] ASN.l Abstract Syntax Notation One
[0308] AUSF authentication server function
[0309] AWGN Additive White Gaussian Noise
[0310] BAP Backhaul Adaptation Protocol
[0311] BCH Broadcast Channel
[0312] BER Bit Error Rate
[0313] BFD beam failure detection
[0314] BLER Block Error Rate
[0315] BPSK Binary Phase Shift Keying
[0316] BRAS Broadband Remote Access Server
[0317] BSS Business Support System
[0318] BS Base Station
[0319] BSR Buffer Status Report
[0320] BW Bandwidth
[0321] BWP Bandwidth Part
[0322] C-RNTI Cell Radio Network Temporary Identifier
[0323] CA operator aggregation, certificate authority
[0324] CAPEX Capital Expenditure
[0325] CBRA Contention Based Access
[0326] CC component carrier, country code, cryptographic checksum
[0327] CCA Clear Channel Assessment
[0328] CCE Control Channel Element
[0329] CCCH Common Control Channel
[0330] CE Coverage Enhancement
[0331] CDM Content Delivery Network
[0332] CDMA Code Division Multiple Access
[0333] CDR Charging Data Request
[0334] CDR charging data response
[0335] CFRA Contention-free random access
[0336] CG Cell Group
[0337] CGF Billing Gateway Function
[0338] CHF billing function
[0339] Cl cell identifier
[0340] CID Cell ID (e.g. positioning method)
[0341] CIM Common Information Model
[0342] CIR Carrier to Interference Ratio
[0343] CK Cryptographic Key
[0344] CM connection management, conditional enforcement
[0345] CM AS Commercial Mobile Alert Service
[0346] CMD command
[0347] CMS Cloud Management System
[0348] CO conditionally optional
[0349] CoMP Coordinated Multipoint
[0350] CORESET Control Resource Set
[0351] COTS Commercial Off-the-Shelf
[0352] CP Control Plane, Cyclic Prefix, Attachment Point
[0353] CPD Connection Point Descriptor
[0354] CPE Customer Premise Equipment
[0355] CPICH Common Pilot Channel
[0356] CQI Channel Quality Indicator
[0357] CPU CSI processing unit, central processing unit
[0358] C / R Command / Response field bit
[0359] CRAN Cloud Radio Access Network, Cloud RAN
[0360] CRB Common Resource Block
[0361] CRC Cyclic Redundancy Check
[0362] CRI Channel State Information Resource Indicator, CSI-RS Resource Indicator
[0363] C-RNTI Cell RNTI
[0364] CS Circuit Switched
[0365] CSCF Call Session Control Function
[0366] CSAR Cloud Service Archives
[0367] CSI Channel State Information
[0368] CSI-IM CSI Interference Measurement
[0369] CSI-RS CSI Reference Signal
[0370] CSI-RSRP CSI reference signal received power
[0371] CSI-RSRQ CSI reference signal reception quality
[0372] CSI-SINR CSI signal-to-noise ratio and interference ratio
[0373] CSMA Carrier Sense Multiple Access
[0374] CSMA / CA CSMA Carrier Sense Multiple Access with Collision Avoidance
[0375] CSS Common Search Space, Cell-Specific Search Space
[0376] CTF Billing Trigger Function
[0377] CTS Clear to Send
[0378] CW codeword
[0379] CWS Contention Window Size
[0380] D2D Device to Device
[0381] DC dual connection, direct current
[0382] DCI Downlink Control Information
[0383] DF deployment style
[0384] DL Downlink
[0385] DMTF Distributed Management Task Force
[0386] DPDK Data Plane Development Kit
[0387] DM-RS, DMRS demodulation reference signal
[0388] DN Data Network
[0389] DNN data network name
[0390] DNAI Data Network Access Identifier
[0391] DRB Data Radio Bearer
[0392] DRS Discovery Reference Signal
[0393] DRX Discontinuous Reception
[0394] DSL Domain Specific Language, Digital Subscriber Line
[0395] DSLAM DSL Access Multiplexer
[0396] DwPTS Downlink Pilot Time Slot
[0397] E-LAN Ethernet Local Area Network
[0398] E2E End to End
[0399] EAS Edge Application Server
[0400] ECCA Extended Clear Channel Assessment, Extended CCA
[0401] ECCE Enhanced Control Channel Element, Enhanced CCE
[0402] ED Energy Detection
[0403] EDGE GSM GSM Enhanced Data Rates Evolution (GSM Evolution)
[0404] EAS Edge Application Server
[0405] EASID Edge Application Server Identifier
[0406] ECS Edge Configuration Server
[0407] ECSP Edge Computing Service Provider
[0408] EDN Edge Data Network
[0409] EEC Edge Enabler Client
[0410] EECID Edge Enabler Client Identifier
[0411] EES Edge Enabler Server
[0412] EESID Edge Enabler Server ID
[0413] EHE Edge Hosting Environment
[0414] EGMF Risk Governance Management Functions
[0415] EGPRS Enhanced GPRS
[0416] EIR Equipment Identification Register
[0417] eLAA Enhanced License Assisted Access, enhanced LAA
[0418] EM Element Manager
[0419] eMBB Enhanced Mobile Broadband
[0420] EMS Element Management System
[0421] eNB Evolved Node B, E-UTRAN Node B
[0422] EN-DC E-UTRA-NR Dual Connectivity
[0423] EPC Evolved Packet Core
[0424] EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel
[0425] EPRE Energy per resource element
[0426] EPS Evolved Packet System
[0427] EREG Enhanced REG, Enhanced Resource Element Group
[0428] ETSI European Telecommunications Standards Institute
[0429] ETWS Earthquake and Tsunami Early Warning System
[0430] eUICC embedded UICC, embedded universal integrated circuit card
[0431] E-UTRA Evolved UTRA
[0432] E-UTRAN Evolved UTRAN
[0433] EV2X Enhanced V2X
[0434] F1AP F1 Application Protocol
[0435] Fl-C F1 Control plane interface
[0436] F1-U F1 User Plane Interface
[0437] FACCH Fast Associated Control Channel
[0438] FACCH / F Fast Associated Control Channel / Full Rate
[0439] FACCH / H Fast Associated Control Channel / Half Rate
[0440] FACH Forward Access Channel
[0441] FAUSCH Fast Uplink Signalling Channel
[0442] FB Function Block
[0443] FBI Feedback
[0444] FCC Federal Communications Commission
[0445] FCCH Frequency Correction Channel
[0446] FDD Frequency Division Duplex
[0447] FDM Frequency Division Multiplexing
[0448] FDMA Frequency Division Multiple Access
[0449] FE Front End
[0450] FEC Forward Error Correction
[0451] FFS for further study
[0452] FFT Fast Fourier Transform
[0453] feLAA Further Enhanced License Assisted Access, Further Enhanced LAA
[0454] FN Frame Number
[0455] FPGA Field Programmable Gate Array
[0456] FR Frequency Range
[0457] FQDN Fully Qualified Domain Name
[0458] G-RNTI GERAN Radio Network Temporary Identity
[0459] GGERAN GSM EDGE RAN, GEM EDGE Radio Access Network
[0460] GGSN Gateway GPRS Support Node
[0461] GLONASS Global Navigation Satellite System
[0462] gNB Next Generation NodeB
[0463] gNB-CU gNB-centralized unit, next generation NodeB centralized unit
[0464] gNB-DU gNB-distributed unit, next generation NodeB distributed unit
[0465] GNSS Global Navigation Satellite System
[0466] GPRS General Packet Radio Service
[0467] GPSI General Public Subscription Identifier
[0468] GSM Global System for Mobile Communications, Mobile Task Force
[0469] GTP GPRS Tunneling Protocol
[0470] GTP-U GPRS Tunneling Protocol for the User Plane
[0471] GTS enters sleep signal (related to WUS)
[0472] GUMMEI Globally Unique MME Identifier
[0473] GUTI Globally Unique Temporary UE Identifier
[0474] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request
[0475] HANDO Switch HFN, HyperFrame number
[0476] HHO Hard Handover
[0477] HLR Home Location Register
[0478] HN Home Network
[0479] HO Switchover
[0480] HPLMN Home Public Land Mobile Network
[0481] HSDPA High Speed Downlink Packet Access
[0482] HSN Hopping Sequence Number
[0483] HSPA High Speed Packet Access
[0484] HSS Home Subscriber Server
[0485] HSUPA High Speed Uplink Packet Access
[0486] HTTP Hypertext Transfer Protocol
[0487] HTTPS Hypertext Transfer Protocol Secure (http is http / 1.1 over SSL, i.e. port 443)
[0488] I-Block Information Block
[0489] ICCID Integrated Circuit Card Identification
[0490] IAB Integrated Access and Backhaul
[0491] ICIC Inter-cell Interference Cooperation
[0492] ID, identifier
[0493] IDFT Inverse Discrete Fourier Transform
[0494] IE Information Elements
[0495] IBE In-Band Emission
[0496] IEEE Institute of Electrical and Electronics Engineers
[0497] IEI Information Element Identifier
[0498] IEIDL Information Element Identifier Data Length
[0499] IETF Internet Engineering Task Force
[0500] IF Infrastructure
[0501] IIOT Industrial Internet of Things
[0502] IM Interference Measurement, Intermodulation, IP Multimedia
[0503] IMC IMS Certificate
[0504] IMEI International Mobile Equipment Identity
[0505] IMGI International Mobile Group Identity
[0506] IMPI IP Multimedia Special Identifier
[0507] IMPU IP Multimedia Public Identity
[0508] IMS IP Multimedia Subsystem
[0509] IMSI International Mobile Subscriber Identity
[0510] IoTa Internet of Things
[0511] IP Internet Protocol
[0512] Ipsec IP security, Internet Protocol security
[0513] IP-CAN IP-Connection Access Network
[0514] IP-M IP Multicast
[0515] IPv4 Internet Protocol version 4
[0516] IPv6 Internet Protocol Version 6
[0517] IR
[0518] IS Synchronization
[0519] IRP Integration Reference Point
[0520] ISDN Integrated Services Digital Network
[0521] ISIM IM Service Identity Module
[0522] ISO International Organization for Standardization
[0523] ISP Internet Service Provider
[0524] IWF interworking function
[0525] I-WLAN Intercommunication WLAN
[0526] Constraint length of convolutional code, USIM
[0527] Separate key
[0528] kB kilobyte (1000 bytes)
[0529] kbps kilobits per second
[0530] Kc encryption key
[0531] Ki Individual subscriber authentication key
[0532] KPI Key Performance Indicator
[0533] KQI Key Quality Indicator
[0534] KSI Key Setting Identifier
[0535] ksps kilosymbols per second
[0536] KVM Kernel Virtual Machine
[0537] L1 Layer 1 (physical layer)
[0538] Ll-RSRP Layer 1 reference signal received power
[0539] L2 Layer 2 (Data Link Layer)
[0540] L3 Layer 3 (Network Layer)
[0541] LAA Licensed Assisted Access
[0542] LAN Local Area Network
[0543] LADN Local Area Data Network
[0544] LBT Listen before you speak
[0545] LCM Life Cycle Management
[0546] LCR Low Chip Rate
[0547] LCS Location Services
[0548] LCID Logical Channel ID
[0549] LI layer indicator
[0550] LLC Logical Link Control, Low Layer Compatibility
[0551] LMF Location Management Function
[0552] LOS Line of Sight
[0553] LPLMN Local PLMN
[0554] LPP LTE Positioning Protocol
[0555] LSB Least Significant Bit
[0556] LTE Long Term Evolution
[0557] LWA LTE-WLAN Aggregation
[0558] LWIP integrated with IPsec tunnel at LTE / WLAN radio level
[0559] LTE Long Term Evolution
[0560] M2M Machine to Machine
[0561] MAC Media Access Control (Protocol Layer Context)
[0562] MAC Message Authentication Code (Security / Cryptography Context)
[0563] MAC-A MAC for authentication and key protocols (TSG TWG3 context) and MAC-IMAC for data integrity of signaling messages (TSG TWG3 context)
[0564] MANO Management and Orchestration
[0565] MBMS Multimedia Broadcast and Multicast Service
[0566] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
[0567] MCC Mobile Country Code
[0568] MCG Master Unit Group
[0569] MCOT Maximum Channel Occupancy Time
[0570] MCS Modulation and Coding Scheme
[0571] MDAF Management Data Analysis Function
[0572] MDAS Management Data Analysis Service
[0573] MDT Minimized Drive Testing ME Mobile Device
[0574] MeNB master eNB MER message error rate
[0575] MGL Measurement Gap Length
[0576] MGRP Measurement Gap Repetition Period
[0577] MIB Master Information Block, Management Information Base
[0578] MIMO Multiple Input Multiple Output
[0579] MLC Mobile Location Center
[0580] MM Mobility Management
[0581] MME Mobility Management Entity
[0582] MN Master Node
[0583] MNO Mobile Network Operator
[0584] MO measurement object, mobile origination
[0585] MPBCH MTC Physical Broadcast Channel
[0586] MPDCCH MTC Physical Downlink Control Channel
[0587] MPDSCH MTC Physical Downlink Shared Channel
[0588] MPRACH MTC Physical Random Access Channel
[0589] MPUSCH MTC Physical Uplink Shared Channel
[0590] MPLS Multiprotocol Label Switching
[0591] MS Mobile Station
[0592] MSB Most Significant Bit
[0593] MSC Mobile Switching Center
[0594] MSI minimum system information, MCH scheduling information
[0595] MSID Mobile Station Identifier
[0596] MSIN Mobile Station Identification Number
[0597] MSISDN Mobile Subscriber ISDN Number
[0598] MT Mobile Terminated, Mobile Terminated
[0599] MTC Machine Type Communication
[0600] mMTC Massive MTC, Massive Machine Type Communication
[0601] MU-MIMO Multi-User MIMO
[0602] MWUS MTC wake-up signal, MTC WUS
[0603] NACK Negative Acknowledgement
[0604] NAI Network Access Identifier
[0605] NAS non-access layer (layer), non-access layer (stratum layer)
[0606] NCT Network Connection Topology
[0607] NC-JT Non-coherent joint transmission
[0608] NEC network capabilities exposed
[0609] NE-DC NR-E-UTRA dual connectivity
[0610] NEF Network Exposure Function
[0611] NF Network Function
[0612] NFP Network Forwarding Path
[0613] NFPD Network Forwarding Path Descriptor
[0614] NFV Network Function Virtualization
[0615] NFVI NFV Infrastructure
[0616] NFVO NFV Orchestrator
[0617] NG Next Generation, Next Gen
[0618] NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity
[0619] NM Network Manager
[0620] NMS Network Management System
[0621] N-PoP Network Point of Presence
[0622] NMIB, N-MIB Narrowband MIB
[0623] NPBCH Narrowband Physical Broadcast Channel
[0624] NPDCCH Narrowband Physical Downlink Control Channel
[0625] NPDSCH Narrowband Physical Downlink Shared Channel
[0626] NPRACH Narrowband Physical Random Access Channel
[0627] NPUSCH Narrowband Physical Uplink Shared Channel
[0628] NPSS Narrowband Primary Synchronization Signal
[0629] NSSS Narrowband Secondary Synchronization Signal
[0630] NR New Radio, Neighbor Relations
[0631] NRF NF Repository Capabilities
[0632] NRS Narrowband Reference Signal
[0633] NS Network Services
[0634] NSA Non-standalone operation mode
[0635] NSD Network Service Descriptor
[0636] NSR Network Service Record
[0637] NSSAI Network Slice Selection Assistance Information
[0638] S-NNSAI Single NSSAI
[0639] NSSF network slice selection function
[0640] NW Network
[0641] NWUS Narrowband wake-up signal, narrowband WUS
[0642] NZP Non Zero Power
[0643] O&M Operation and Maintenance
[0644] ODU2 Optical Channel Data Unit - Type 2
[0645] OFDM Orthogonal Frequency Division Multiplexing
[0646] OFDMA Orthogonal Frequency Division Multiple Access
[0647] OOB Out of Band
[0648] OOS Out of Sync
[0649] OPEX Operating Expenses
[0650] OSI Other System Information
[0651] OSS Operation Support System
[0652] OTA
[0653] PAPR Peak to Average Power Ratio
[0654] PAR Peak to Average Ratio
[0655] PBCH Physical Broadcast Channel
[0656] PC Power Control, Personal Computer
[0657] PCC Primary Component Carrier, Primary CC
[0658] P-CSCF Proxy CSCF
[0659] Pcell Primary cell
[0660] PCI Physical Cell ID, Physical Cell Identifier
[0661] PCEF Policy and Charging Enforcement Function
[0662] PCF Policy Control Function
[0663] PCRF Policy Control and Charging Rules Function
[0664] PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer
[0665] PDCCH Physical Downlink Control Channel
[0666] PDCP Packet Data Convergence Protocol
[0667] PDN Packet Data Network, Public Data Network
[0668] PDSCH Physical Downlink Shared Channel
[0669] PDU Protocol Data Unit
[0670] PEI Persistent Equipment Identifier
[0671] PFD Packet Flow Description
[0672] P-GW PDN Gateway
[0673] PHICH Physical Hybrid ARQ Indicator Channel
[0674] PHY Physical Layer
[0675] PLMN Public Land Mobile Network
[0676] PIN Personal Identification Number
[0677] PM performance measurement
[0678] PMI Precoding matrix indicator
[0679] PNF Physical Network Function
[0680] PNFD Physical Network Functional Descriptor
[0681] PNFR Physical Network Function Record
[0682] PTT over POC cellular network
[0683] PP, PTP point to point
[0684] PPP Point-to-Point Protocol
[0685] PRACH Physical RACH
[0686] PRB Physical Resource Block
[0687] PRG Physical Resource Group
[0688] ProSe proximity services, proximity-based services
[0689] PRS Positioning Reference Signal
[0690] PRR Packet Receive Radio
[0691] PS Packet Service
[0692] PSBCH Physical Sidelink Broadcast Channel
[0693] PSDCH Physical Sidelink Downlink Channel
[0694] PSCCH Physical Sidelink Control Channel
[0695] PSSCH Physical Sidelink Shared Channel
[0696] PSFCH Physical Sidelink Feedback Channel
[0697] PSCell Primary SCell
[0698] PSS Primary Synchronization Signal
[0699] PSTN Public Switched Telephone Network
[0700] PT-RS Phase Tracking Reference Signal
[0701] PTT Push to Talk
[0702] PUCCH Physical Uplink Control Channel
[0703] PUSCH Physical Uplink Shared Channel
[0704] QAM Quadrature Amplitude Modulation
[0705] QCI QoS Class Identifier
[0706] QCL Quasi-Co-sited
[0707] QFI QoS flow ID, QoS flow identifier
[0708] QoS Quality of Service
[0709] QPSK Quadrature (Quaternary) Phase Shift Keying
[0710] QZSS Quasi-Zenith Satellite System
[0711] RA-RNTI Random Access RNTI
[0712] RAB Radio Access Bearer, Random Access Burst
[0713] RACH Random Access Channel
[0714] RADIUS Remote Authentication Dial-In User Service
[0715] RAN Radio Access Network
[0716] RAND Random number (for authentication)
[0717] RAR Random Access Response
[0718] RAT Radio Access Technology
[0719] RAU Routing Area Update
[0720] RB Resource Block, Radio Bearer
[0721] RBG Resource Block Group
[0722] REG Resource Element Group
[0723] Rel release version
[0724] REQ REQuest
[0725] RF
[0726] RI Rank Indicator
[0727] RIV Resource Indicator Value
[0728] RL Radio Link
[0729] RLC Radio Link Control, Radio Link Control Layer
[0730] RLC AM RLC Acknowledgement Mode
[0731] RLC UM RLC Unacknowledged Mode
[0732] RLF Radio Link Failure
[0733] RLM Radio Link Monitoring
[0734] RLM-RS Reference signal for RLM
[0735] RM Registration Management
[0736] RMC Reference Measurement Channel
[0737] RMSI Remaining MSI, Remaining Minimum System Information
[0738] RN Relay Node
[0739] RNC Radio Network Controller
[0740] RNL Radio Network Layer
[0741] RNTI Radio Network Temporary Identifier
[0742] ROHC Robust Header Compression
[0743] RRC Radio Resource Control, Radio Resource Control Layer
[0744] RRM Radio Resource Management
[0745] RS reference signal
[0746] RSRP Reference Signal Received Power
[0747] RSRQ Reference Signal Received Quality
[0748] RSSI Received Signal Strength Indicator
[0749] RSU Roadside Unit
[0750] RSTD Reference Signal Time Difference
[0751] RTP Real Time Protocol
[0752] RTS Ready to send
[0753] RTT Round Trip Time
[0754] Rx receiving, receiving, receiver
[0755] S1AP S1 Application Protocol
[0756] S1-MME is used for control plane
[0757] S1-U S1 for user plane
[0758] S-CSCF Serving CSCF
[0759] S-GW Service Gateway
[0760] S-RNTI SRNC Radio Network Temporary Identifier
[0761] S-TMSI SAE Temporary Mobile Site Identifier
[0762] SA Standalone Operation Mode
[0763] SAE system architecture evolution
[0764] SAP Service Access Point
[0765] SAPD Service Access Point Descriptor
[0766] SAPI Service Access Point Identifier
[0767] SCC Secondary Component Carrier, Secondary CC
[0768] Scell
[0769] SCEF Service Capability Exposure Function
[0770] SC-FDMA Single Carrier Frequency Division Multiple Access
[0771] SCG Secondary Cell Group
[0772] SCM Security Context Management
[0773] SCS subcarrier spacing
[0774] SCTP Stream Control Transmission Protocol
[0775] SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer
[0776] SDL Supplemental Downlink
[0777] SDNF Structured Data Storage Network Function
[0778] SDP Session Description Protocol
[0779] SDSF structured data storage function
[0780] SDT Small Data Transfer
[0781] SDU Service Data Unit
[0782] SEAF safety anchor function
[0783] SeNB Secondary eNB
[0784] SEPP Security Edge Protection Proxy
[0785] SFI Slot Format Indicator
[0786] SFTD Space Frequency Time Diversity, SFN and Frame Timing Difference
[0787] SFN System Frame Number
[0788] SgNB Secondary gNB
[0789] SGSN Serving GPRS Support Node
[0790] S-GW Service Gateway
[0791] SI System Information
[0792] SI-RNTI System Information RNTI
[0793] SIB System Information Block
[0794] SIM Subscriber Identity Module
[0795] SIP Session Initiation Protocol
[0796] System in a SiP Group
[0797] SL Side Link
[0798] SLA Service Level Agreement
[0799] SM Session Management
[0800] SMF session management functions
[0801] SMS Short Message Service
[0802] SMSF SMS Function
[0803] SMTC SSB-based measurement timing configuration
[0804] SN Secondary node, serial number
[0805] SoC System on Chip
[0806] SON Self-Organizing Network
[0807] SpCell Dedicated Cell
[0808] SP-CSI-RNTI Semi-Permanent CSI-RNTI
[0809] SPS Semi-Permanent Scheduling
[0810] SQN Serial Number
[0811] SR Scheduling Request
[0812] SRB Signalling Radio Bearer
[0813] SRS Sounding Reference Signal
[0814] SS Sync Signal
[0815] SSB Synchronous Signal Block
[0816] SSID Service Set Identifier
[0817] SS / PBCH block SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator
[0818] SSC Session and Service Continuity
[0819] SS-RSRP Synchronization signal based on reference signal received power
[0820] SS-RSRQ Synchronization signal based on reference signal reception quality
[0821] SS-SINR Signal-to-Noise and Interference Ratio based on synchronization signal
[0822] SSS Secondary sync signal
[0823] SSSG Search Space Group
[0824] SSSIF Search Space Set Indicator
[0825] SST Slice / Service Type
[0826] SU-MIMO Single User MIMO
[0827] SUL Supplementary Uplink
[0828] TA Timing Advance, Tracking Area
[0829] TAC Tracking Area Code
[0830] TAG Timing Advance Group
[0831] TAI Tracking Area Identifier
[0832] TAU Tracking Area Updates
[0833] TB Transfer Block
[0834] TBS Transport Block Size
[0835] TBD
[0836] TCI Transmission Configuration Indicator
[0837] TCP transport communication protocol
[0838] TDD Time Division Duplex
[0839] TDM Time Division Multiplexing
[0840] TDMA Time Division Multiple Access
[0841] TE Terminal Equipment
[0842] TEID Tunnel Endpoint Identifier
[0843] TFT Business Flow Template
[0844] TMSI Temporary Mobile Subscriber Identity
[0845] TNL Transport Network Layer
[0846] TPC Transmit Power Control
[0847] TPMI transmitted precoding matrix indicator
[0848] TR Technical Report
[0849] TRP, TRxP Transmission Receive Point
[0850] TRS Tracking Reference Signal
[0851] TRx Transceiver
[0852] TS Technical Specifications, Technical Standards
[0853] TTI Transmission Time Interval
[0854] Tx Transmitting, Transmitting, Transmitter
[0855] U-RNTI UTRAN Radio Network Temporary Identity
[0856] UART Universal Asynchronous Receiver and Transmitter
[0857] UCI Uplink Control Information
[0858] UE User Equipment
[0859] UDM Unified Data Management
[0860] UDP User Datagram Protocol
[0861] UDSF Unstructured Data Storage Network Function
[0862] UICC Universal Integrated Circuit Card
[0863] UL Uplink
[0864] UM Unconfirmed Mode
[0865] UML Unified Modeling Language
[0866] UMTS Universal Mobile Telecommunications System
[0867] UP User Plane
[0868] UPF User Plane Function
[0869] URI Uniform Resource Identifier
[0870] URL Uniform Resource Locator
[0871] URLLC Ultra-Reliable Low Latency
[0872] USB Universal Serial Bus
[0873] USIM Universal Subscriber Identity Module
[0874] USS UE specific search space
[0875] UTRA UMTS Terrestrial Radio Access
[0876] UTRAN Universal Terrestrial Radio Access Network
[0877] UwPTS Uplink Pilot Time Slot
[0878] V2I Vehicle to Infrastructure
[0879] V2P Vehicle to Pedestrian
[0880] V2V Vehicle to Vehicle
[0881] V2X Vehicle to Everything
[0882] VIM Virtualization Infrastructure Manager
[0883] VL Virtual Link
[0884] VLAN Virtual LAN, Virtual Local Area Network
[0885] VM Virtual Machine
[0886] VNF Virtualized Network Function
[0887] VNFFG VNF forwarding graph
[0888] VNFFGD VNF Forwarding Graph Descriptor
[0889] VNFM VNF Manager
[0890] VoIP Voice over IP, Voice over Internet Protocol
[0891] VPLMN Visited Public Land Mobile Network
[0892] VPN Virtual Private Network
[0893] VRB Virtual Resource Block
[0894] WiMAX Worldwide Interoperability for Microwave Access
[0895] WLAN Wireless Local Area Network
[0896] WMAN Wireless Metropolitan Area Network
[0897] WPAN Wireless Personal Area Network
[0898] X2-C X2 control plane
[0899] X2-U X2 User plane
[0900] XML Extensible Markup Language
[0901] XRES Expected User Response
[0902] XOR
[0903] ZC Zadov-First
[0904] ZP Zero Power
[0905] the term
[0906] For purposes of this disclosure, the following terms and definitions apply to the examples and embodiments discussed in this disclosure.
[0907] The term "circuitry" as used in this disclosure refers to, is part of, or includes a hardware component, such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or a memory (shared, dedicated, or group), 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., which is configured to provide the described functions. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuitry" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and a program code for executing the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a special type of circuitry.
[0908] The term "processor circuit system" used in this disclosure refers to a circuit system that can sequentially and automatically perform a series of arithmetic or logical operations, or record, store and / or transmit digital data, is a part of the circuit system or includes the circuit system. The processing circuit system may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuit system" 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, and / or functional processes. The processing circuit system may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuit system" and / or "baseband circuit system" may be considered synonymous with "processor circuit system" and may be referred to as "processor circuit system".
[0909] The term "interface circuitry" as used in this disclosure refers to, is a part of, or includes circuitry that enables information to be exchanged between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.
[0910] The term "user equipment" or "UE" as used in this disclosure 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: a client, a mobile device, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, a radio device, a reconfigurable radio device, a 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.
[0911] The term "network element" as used in this disclosure 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: a networked computer, networking hardware, a network device, a network node, a router, a switch, a hub, a bridge, a radio network controller, a RAN device, a RAN node, a gateway, a server, a virtualized VNF, a NFVI, etc.
[0912] The term "computer system" as used in this disclosure refers to any type of interconnected electronic devices, computer devices, or components thereof. In addition, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. In addition, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.
[0913] The terms "facility", "computer facility", etc., as used in this disclosure, refer to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide specific computing resources. A "virtual device" is a virtual machine image implemented by a device equipped with a hypervisor that virtualizes or emulates a computer facility or is otherwise dedicated to providing specific computing resources.
[0914] The term "resource" used in this disclosure refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical / 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, an electrical power, an input / output operation, a port or a network socket, a channel / link allocation, a throughput, a memory usage, a storage, a network, a database and an application, a workload unit, etc. "Hardware resources" may refer to computing, storage and / or network resources provided by (multiple) physical hardware elements. "Virtualized resources" may refer to computing, storage and / or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access 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 to be a set of coherent functions, network data objects, or services that can be accessed through a server, where such system resources are located on a single host or multiple hosts and are clearly identifiable.
[0915] The term "channel" as used in the present disclosure refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent to the following terms: "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 path or medium through which data is transmitted. In addition, the term "link" as used in the present disclosure refers to a connection between two devices over a RAT for transmitting and receiving information.
[0916] The terms "instantiate", "instantiation" and the like used in this disclosure refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, such as that which may occur during the execution of program code.
[0917] The terms "coupled", "communicatively coupled" and their derivatives are used in this disclosure. The term "coupled" may refer to two or more elements being in direct physical or electrical contact with each other, may refer to two or more elements being in indirect contact with each other, but still cooperating or interacting with each other, and / or may refer to one or more other elements being coupled or connected between elements referred to as being coupled to each other. The term "directly coupled" may refer to two or more elements being in direct contact with each other. The term "communicatively coupled" may refer to two or more elements being in contact with each other by means of communication, including by wired or other interconnect connections, by wireless communication channels or links, etc.
[0918] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element or a data element that contains content.
[0919] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConformation.
[0920] The term "SSB" refers to SS / PBCH block.
[0921] The term "primary cell" refers to an MCG cell operating on a primary frequency, where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.
[0922] The term "primary SCG cell" refers to an SCG cell to which a UE performs random access when performing reconfiguration with a synchronization procedure for DC operation.
[0923] The term "secondary cell" refers to a cell that provides additional radio resources on top of a dedicated cell for a UE configured with CA.
[0924] The term "secondary cell group" refers to a subset of serving cells, which includes a PSCell and zero or more secondary cells for a UE configured with DC.
[0925] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and has only one serving cell consisting of the primary cell.
[0926] The term "serving cell" or "cells" refers to a group of cells including the dedicated cell(s) and all secondary cells for a UE in RRC-CONNECTED configured with CA / .
[0927] The term "dedicated cell" refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term "dedicated cell" refers to the Pcell.
Claims
1. One or more non-transitory computer readable media (NTCRM) having instructions stored thereon, which when executed by one or more processors of a user equipment (UE), configure the UE to: receiving sidelink control information (SCI) including an indication of a channel access priority class (CAPC) for a sidelink transmission, determining a first PC5 quality of service (QoS) identifier (PQI) for the sidelink transmission from one or more PQIs associated with the CAPC; and The sidelink transmission is performed based on the CAPC and the first PQI.
2. The one or more non-transitory computer readable media (NTCRM) of claim 1, wherein the instructions, when executed, further configure the UE to: determining a maximum channel occupancy time for the sidelink transmission based on the CAPC; and One or more QoS characteristics for the sidelink transmission are determined based on the first PQI.
3. The one or more non-transitory computer readable media (NTCRM) of claim 1, wherein the first PQI is determined based on an association between a PQI and a corresponding CAPC according to the following table: .
4. One or more non-transitory computer-readable media (NTCRM) according to any one of claims 1 to 3, wherein the SCI further includes an indication of a per-packet ProSe priority (PPPP) for the sidelink transmission, wherein the sidelink transmission is further performed based on the PPPP.
5. The one or more non-transitory computer readable media (NTCRM) of claim 4, wherein the instructions, when executed, further configure the UE to: determining a sidelink transmission priority for the sidelink transmission based on the PPPP; and A sidelink sensing and resource selection procedure for the sidelink transmission is performed based on the sidelink transmission priority.
6. One or more non-transitory computer-readable media (NTCRM) according to claim 5, wherein the instructions, when executed, further configure the UE to determine a listen-before-talk (LBT) based sidelink channel access procedure for the sidelink transmission based on the CAPC.
7. One or more non-transitory computer-readable media (NTCRM) according to any one of claims 1 to 3, wherein the SCI does not indicate a per-packet ProSe priority (PPPP) for the sidelink transmission, or the PPPP indicated by the SCI is ignored for the sidelink transmission.
8. One or more non-transitory computer readable media (NTCRM) having instructions stored thereon, the instructions, when executed by one or more processors of a user equipment (UE), configuring the UE to: determining that a number of listen-before-talk (LBT) failures on the sidelink channel exceeds a threshold over a period of time, and A report is sent based on the determination to indicate a consistent LBT failure.
9. One or more non-transitory computer readable media (NTCRM) according to claim 8, wherein the UE is in sidelink mode 1.
10. The one or more non-transitory computer readable media (NTCRM) of claim 8, wherein the UE is in sidelink mode 2.
11. The one or more non-transitory computer readable media (NTCRM) of claim 8, wherein the report is sent to a gNB.
12. One or more non-transitory computer readable media (NTCRM) according to any one of claims 8 to 11, wherein the determination is associated with the UE attempting to transmit a physical sidelink feedback channel (PSFCH).
13. One or more non-transitory computer readable media (NTCRM) having instructions stored thereon, which when executed by one or more processors of a user equipment (UE), configure the UE to: performing a sidelink sensing and resource selection procedure to select a sidelink resource for sidelink transmission; performing a listen-before-talk (LBT) procedure on the selected sidelink resource; and If the LBT procedure is successful, the sidelink transmission is performed in the selected sidelink resource.
14. One or more non-transitory computer readable media (NTCRM) according to claim 13, wherein the sidelink sensing and resource selection procedure is performed based on an energy detection threshold of the LBT procedure.
15. One or more non-transitory computer-readable media (NTCRM) according to claim 13, wherein the sidelink sensing and resource selection procedure includes sensing activity on resources of a channel and excluding one or more of the resources from a candidate resource set based on the sensed activity, wherein the sidelink resource is selected from the candidate resource set for the sidelink transmission.
16. One or more non-transitory computer readable media (NTCRM) according to claim 13, wherein the LBT procedure is performed within a cyclic prefix extension prior to the selected side link resource.
17. The one or more non-transitory computer readable media (NTCRM) of claim 13, wherein the selected side link resources comprise consecutive time slots.
18. The one or more non-transitory computer readable media (NTCRM) of claim 17, wherein the instructions, when executed, further configure the UE to determine support for selection of the consecutive time slots based on one or more conditions.
19. The one or more non-transitory computer readable media (NTCRM) of claim 18, wherein the one or more conditions include one or more of the following: a packet delay budget less than a first predetermined value; a remaining packet delay budget less than a second predetermined value; A channel busy ratio (CBR) less than a third predetermined value; or A condition based on the priority of the sidelink transmission or a channel access priority condition (CAPC).
20. One or more non-transitory computer readable media (NTCRM) according to any one of claims 13 to 19, wherein the sidelink sensing and resource selection procedure is to prioritize the earliest resources in time.
