Methods and apparatus for CB-MSG3 transmission and CB-MSG3 response processing
By employing techniques for CB-Msg3 transmission and response processing, such as identifier derivation and interference randomization, the reliability and efficiency of contention-based access procedures are improved in wireless communication systems.
Patent Information
- Application Number
- PCT/CN2026/094244
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-30
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems lack sufficient flexibility and efficiency in handling contention-based uplink transmissions and corresponding network responses, affecting the reliability and efficiency of access procedures.
Implementing techniques for contention-based message 3 (CB-Msg3) transmission and CB-Msg3 response processing, including identifier derivation based on system frame numbers and transmission window parameters, interference randomization, timing adjustment, and configuration parameters to enhance coordination and reliability.
Enhances the efficiency, reliability, and flexibility of contention-based access procedures by streamlining uplink access processes and improving success rates in wireless communication systems.
Smart Images

Figure CN2026094244_12112026_PF_FP_ABST
Abstract
Description
METHODS AND APPARATUS FOR CB-MSG3 TRANSMISSION AND CB-MSG3 RESPONSE PROCESSINGCROSS REFERENCE TO RELATED PATENT APPLICATION (S)
[0001] The present disclosure is part of a non-provisional application claiming the priority benefit of PCT Patent Application No. PCT / CN2025 / 093864, filed 9 May 2025, the contents of which herein being incorporated by reference in its entirety.TECHNICAL FIELD
[0002] The present disclosure is generally related to mobile communications and, more particularly, to methods and apparatus for contention-based message 3 (CB-Msg3) transmission and CB-Msg3 response (CB-Msg4) processing.BACKGROUND
[0003] Unless otherwise indicated herein, approaches described in this section are not prior art to the claims listed below and are not admitted as prior art by inclusion in this section.
[0004] In wireless communication systems, an initial access procedure may be performed to allow a user equipment (UE) to establish uplink communication with a network node. Such procedures may involve a sequence of signaling exchanges between the UE and the network node in order to obtain uplink transmission resources and synchronize communication parameters.
[0005] In some access procedures, the UE may initiate the uplink access process by transmitting a preamble signal. The preamble may allow the network node to detect the UE’s access attempt and provide subsequent information for completing the access procedure, including scheduling information or timing related adjustments.
[0006] In some communication scenarios, however, a timing offset between the UE and the network node may be relatively small or may be estimated in advance. In such situations, it may be possible for the UE to transmit uplink data directly as part of a contention-based access procedure without requiring a separate preamble transmission.
[0007] When uplink transmission is triggered through a contention-based message, additional mechanisms may be involved to manage the transmission process and the corresponding response from the network node. These mechanisms may include procedures for identifying transmissions, coordinating responses, and processing signaling associated with the uplink transmission.
[0008] However, existing mechanisms may not provide sufficient flexibility or efficiency for handling some aspects of contention-based uplink transmissions and the corresponding network responses in some communication scenarios. This limitation may affect the reliability or efficiency of the access procedure and subsequent communication operations.
[0009] Accordingly, there is a need for techniques that improve the handling of contention-based uplink transmissions and associated response processing, thereby enhancing the efficiency and robustness of communication procedures in wireless networks.SUMMARY
[0010] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.
[0011] An objective of the present disclosure is to provide solutions or schemes that improve handling of CB-Msg3 transmission and CB-Msg3 response processing in wireless communication systems, thereby enhancing efficiency, reliability and flexibility of contention-based access procedures.
[0012] In one aspect, a method may involve a user equipment (UE) transmitting a contention-based message 3 (CB-Msg3) in a transmission window using an identifier associated with the CB-Msg3. The method may further involve the UE receiving a CB-Msg3 response (CB-Msg4) associated with the CB-Msg3. The CB-Msg3 and the CB-Msg4 may be associated with at least one configuration parameter related to an identifier derivation and a response processing. The identifier derivation may be based on a system frame number associated with the transmission window and a transmission window parameter.
[0013] In one aspect, a UE may comprise a transceiver configured to communicate with a network node and a processor communicatively coupled to the transceiver. The processor, during operation, may perform operations comprising transmitting, via the transceiver, a contention-based message 3 (CB-Msg3) in a transmission window using an identifier associated with the CB-Msg3. The processor, during operation, may further perform operations comprising receiving, via the transceiver, a CB-Msg3 response (CB-Msg4) associated with the CB-Msg3. The CB-Msg3 and the CB-Msg4 may be associated with at least one configuration parameter related to an identifier derivation and a response processing. The identifier derivation may be based on a system frame number associated with the transmission window and a transmission window parameter.
[0014] In one aspect, a method may involve a network node receiving a contention-based message 3 (CB-Msg3) transmitted by a user equipment (UE) in a transmission window using an identifier associated with the CB-Msg3. The method may further involve the network node transmitting a CB-Msg3 response (CB-Msg4) associated with the CB-Msg3. The CB-Msg3 and the CB-Msg4 may be associated with at least one configuration parameter related to identifier derivation and response processing. The identifier derivation may be based on a system frame number associated with the transmission window and a transmission window parameter.
[0015] It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro, 5th Generation (5G) , New Radio (NR) , Internet-of-Things (IoT) and Narrow Band Internet of Things (NB-IoT) , Industrial Internet of Things (IIoT) , and 6th Generation (6G) , the proposed concepts, schemes and any variation (s) / derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies. Thus, the scope of the present disclosure is not limited to the examples described herein.BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.
[0017] FIG. 1 is a diagram depicting an example scenario under schemes in accordance with implementations of the present disclosure.
[0018] FIG. 2 is a block diagram of an example communication system in accordance with an implementation of the present disclosure.
[0019] FIG. 3 is a flowchart of an example process in accordance with an implementation of the present disclosure.
[0020] FIG. 4 is a flowchart of another example process in accordance with an implementation of the present disclosure. DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS
[0021] Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations. Overview
[0022] The following description is provided to facilitate an understanding of the technical solutions of the present disclosure. In particular, some reference techniques and example scenarios are described below to illustrate contexts in which the embodiments of the present disclosure may be applied.
[0023] Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and / or solutions pertaining to wireless communications, and more particularly to methods and apparatus for contention-based message 3 (CB-Msg3) transmission and CB-Msg3 response (CB-Msg4) processing. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.
[0024] Regarding the present disclosure, in some wireless communication systems, a user equipment (UE) may initiate an uplink access procedure using a contention-based message. In some scenarios, a CB-Msg3 may be transmitted by the UE to trigger an uplink access process without requiring a separate preamble transmission. The UE may transmit the CB-Msg3 in a transmission window using an identifier associated with the CB-Msg3 and may subsequently receive a CB-Msg4 from a network node.
[0025] In some scenarios, the CB-Msg3 and the CB-Msg4 may be associated with one or more configuration parameters related to identifier derivation and response processing. For example, the identifier associated with the CB-Msg3 may be derived based on a system frame number associated with the transmission window and a transmission window parameter. Such mechanisms may facilitate coordination between the UE and the network during contention-based access procedures.
[0026] In one aspect of the present disclosure, techniques for deriving a contention-based radio network temporary identifier (CB-RNTI) may be provided for bandwidth-limited (BL) UEs, UEs in enhanced coverage scenarios, and narrowband Internet of Things (NB-IoT) UEs. In some implementations, the CB-RNTI may be derived based on parameters associated with a transmission window and other related information.
[0027] In another aspect of the present disclosure, techniques for configuring contention-based message transmission may be provided. Such techniques may include configuration of parameters associated with CB-Msg3 transmission and corresponding response processing.
[0028] In another aspect of the present disclosure, techniques for interference randomization of CB-Msg3 responses may be provided. For example, downlink transmissions associated with a CB-Msg3 response may utilize scrambling sequences determined based on an identifier associated with the CB-Msg3.
[0029] In another aspect of the present disclosure, techniques for timing adjustment associated with CB-Msg3 transmission and CB-Msg3 response processing may be provided. For instance, timing advance information may be included in a response message to facilitate uplink timing alignment.
[0030] In another aspect of the present disclosure, techniques for configuring response related information associated with CB-Msg3 responses may be provided. Such techniques may include mechanisms for indicating hybrid automatic repeat request (HARQ) feedback related information and other parameters associated with the response.
[0031] Accordingly, by enabling contention-based message transmission and corresponding response processing using the techniques described herein, uplink access procedures between a UE and a network node may be streamlined while maintaining reliability and communication efficiency in wireless communication systems.
[0032] FIG. 1 illustrates an example scenario 100 under schemes in accordance with implementations of the present disclosure. Scenario 100 involves at least one network node and a UE, which may be a part of a wireless communication network (e.g., an LTE network, a 5G / NR network, an IoT network or a 6G network) . The network side may comprise one or more than one network nodes, including a radio access network and a core network, operating in a wireless communication system. FIG. 1 illustrates an example scenario 100 between a network node and a UE for CB-Msg3 transmission and CB-Msg4 processing.
[0033] FIG. 1 illustrates the example scenario 100 in which a UE performs an uplink access procedure using CB-Msg3 with a network node. In some implementations, the UE transmits a CB-Msg3 in a transmission window using an identifier associated with the CB-Msg3. The identifier may be derived based on a system frame number associated with the transmission window and a transmission window parameter. After transmitting the CB-Msg3, the UE may receive a CB-Msg4 from the network node.
[0034] In some implementations, the CB-Msg3 and the CB-Msg4 may be associated with one or more configuration parameters related to identifier derivation and response processing. Such configuration parameters may support reliable processing of the CB-Msg3 and the CB-Msg4 and facilitate coordination between the UE and the network node during the uplink access procedure.
[0035] In some implementations, the network node may receive the CB-Msg3 transmitted by the UE in the transmission window using the identifier associated with the CB-Msg3. The network node may then transmit the CB-Msg4 to the UE. The CB-Msg3 and the CB-Msg4 may be processed based on configuration parameters related to identifier derivation and response processing.
[0036] According to the present disclosure, techniques are provided for utilizing CB-Msg3 to trigger an uplink access process. By providing mechanisms for identifier derivation and response processing associated with CB-Msg3 and CB-Msg4, the random access procedure may be streamlined. This approach improves reliability and enhances the success rate of uplink access in communication systems.
[0037] More specifically, the present disclosure considers the following proposals related to CB-Msg3 transmission and CB-Msg3 response processing. In some implementations, the proposals described below may be implemented individually or jointly. That is, although the proposals may be described separately, two or more of the proposals may be implemented in combination.
[0038] Proposal #1 provides a CB-RNTI derivation mechanism for bandwidth limited (BL) UEs and UEs operating in enhanced coverage conditions. In some scenarios, the identifier associated with the CB-Msg3 may comprise a contention-based radio network temporary identifier (CB-RNTI) . In some implementations, the CB-RNTI may be derived based on parameters related to a transmission window in which a contention-based physical uplink shared channel (PUSCH) carrying the CB-Msg3 is transmitted. For example, the CB-RNTI may be derived based on a system frame number (SFN) associated with the transmission window and a transmission window parameter.
[0039] In some implementations, the CB-RNTI may be derived based on a start system frame number or an end system frame number of the transmission window. In some scenarios, the CB-RNTI may be determined using a function of the SFN and a minimum transmission window length parameter. For example, the CB-RNTI may be computed as: CB-RNTI = 1 + floor (SFN_id / Wmin) , where the SFN_id may correspond to a start SFN of the transmission window or an end SFN of the transmission window, and Wmin may represent a minimum value of a transmission window length.
[0040] In some implementations, different offset values may be applied when deriving the CB-RNTI. For example, in some scenarios, the CB-RNTI may be computed as: CB-RNTI = 2401 + floor (SFN_id / Wmin) .
[0041] In some implementations, the CB-RNTI may alternatively be computed as: CB-RNTI = 2402 +floor (SFN_id / Wmin) .
[0042] In some scenarios, the parameter Wmin may correspond to a predefined value. For example, the predefined value of Wmin may be selected from a candidate value set including {2, 4, 6, 8, 12, 16, 20, 32, 40, 64} . In some implementations, the value of Wmin may be configured by the network node. For example, Wmin may be configured using one or more bits in system information, such as a system information block (SIB) , and may be updated via system information or radio resource control (RRC) signaling.
[0043] In some scenarios, the CB-RNTI may be derived based on a transmit resource associated with the transmission window used for CB-Msg3 transmission. For example, the transmit resource may include a start timing of the transmission window represented by an SFN and a transmission window length. In some implementations, the CB-RNTI may correspond to an index of a monitoring window within a higher-frame system number (H-FSN) period. The monitoring window index may be obtained by dividing the starting SFN of the transmission window by the window length and rounding down the result. In some scenarios, the minimum window length may be used instead of the actual window length to simplify the calculation.
[0044] In some implementations, different UE types may apply different CB-RNTI derivation parameters. For example, BL UEs or UEs operating in enhanced coverage conditions may apply one set of offset values, while narrowband Internet of Things (NB-IoT) UEs may further consider additional parameters such as a carrier index when deriving the CB-RNTI.
[0045] In some scenarios, the offset value used in the CB-RNTI derivation may be selected to avoid identifier collision with other radio network temporary identifiers. For example, in some implementations, the CB-RNTI may start from an offset value greater than a maximum value of a random access radio network temporary identifier (RA-RNTI) . For example, the RA-RNTI maximum value may be 2400 for enhanced machine-type communication (eMTC) systems and 4096 for NB-IoT systems. Accordingly, an offset value such as 2401 may be used as a starting value for CB-RNTI derivation. Such configuration may limit the available identifier range and prevent identifier collision between CB-RNTI and RA-RNTI.
[0046] In some implementations, the CB-RNTI may be used for CB-Msg4 monitoring and CB-Msg3 scrambling. For example, a network node may transmit a CB-Msg4 that is monitored using the CB-RNTI derived from the transmission window resource associated with the CB-Msg3 transmission. In some scenarios, a single monitoring window and a single CB-RNTI may be adopted for CB-Msg4 monitoring corresponding to a CB-Msg3 transmission window.
[0047] Proposal #2 provides CB-RNTI derivation for narrowband Internet of Things (NB-IoT) UEs. In some implementations, the identifier associated with the CB-Msg3 may comprise a contention-based radio network temporary identifier (CB-RNTI) . In some scenarios, the CB-RNTI may be derived based on parameters related to a transmission window in which a contention-based physical uplink shared channel (PUSCH) carrying the CB-Msg3 is transmitted. For example, the CB-RNTI may be derived based on a system frame number (SFN) associated with the transmission window and a transmission window parameter. In some implementations, the CB-RNTI derivation may further depend on parameters associated with NB-IoT carriers. For example, the CB-RNTI may depend on a carrier index identifying an uplink carrier associated with the specified CB-Msg3 transmission. In some scenarios, the carrier index of an anchor carrier may be set to 0.
[0048] In some implementations, the CB-RNTI associated with the CB-Msg3 in which the contention-based PUSCH is transmitted may be computed as: CB-RNTI = 1 + floor (SFN_id / Wmin) + N × carrier_id, where the SFN_id corresponds to a start system frame number (SFN) or an end SFN of the transmission window, Wmin represents a minimum value of the transmission window length, and carrier_id represents an index of an uplink carrier associated with the CB-Msg3 transmission. In some scenarios, the parameter N may correspond to a maximum value of floor (SFN_id / Wmin) . In some scenarios, the carrier index of an anchor carrier may be set to 0.
[0049] In some implementations, an offset value may be applied to the CB-RNTI derivation to avoid collision with other radio network temporary identifiers. For example, the CB-RNTI may alternatively be computed as: CB-RNTI = 4096 + floor (SFN_id / Wmin) + N × carrier_id, or CB-RNTI = 4097 + floor (SFN_id / Wmin) + N × carrier_id.
[0050] In some scenarios, NB-IoT UEs operating in time division duplex (TDD) mode may utilize additional parameters related to a hyper frame number. For example, the CB-RNTI may be computed as: CB-RNTI = 1 + floor (SFN_id / Wmin) + N × (H-SFN mod 2) , where H-SFN corresponds to an index of a hyper frame associated with the specified CB-Msg3 transmission. In some implementations, the PDCCH transmission and the CB-Msg3 resource may be located on the same carrier.
[0051] In some implementations, offset values may also be applied for TDD scenarios. For example, the CB-RNTI may be computed as: CB-RNTI = 768 + floor (SFN_id / Wmin) + N × (H-SFN mod 2) , or CB-RNTI = 769 + floor (SFN_id / Wmin) + N × (H-SFN mod 2) .
[0052] In some scenarios, the parameter Wmin may correspond to a predefined value selected from a candidate value set including {2, 4, 6, 8, 12, 16, 20, 32, 40, 64} . In some implementations, the value of Wmin may be configured by the network node via system information or radio resource control (RRC) signaling.
[0053] In some implementations, the parameter N may correspond to a predefined value selected from a candidate value set including {512, 256, 170, 128, 85, 64, 51, 32, 25, 16} . In some scenarios, N may also be derived based on a relationship with the transmission window parameter. For example, N may be determined according to: N = floor (1024 / Wmin) .
[0054] In some scenarios, the CB-RNTI may be derived based on a transmit resource associated with the transmission window. For example, the transmission window resource may include a start timing represented by the SFN and a window length parameter.
[0055] In some implementations, the CB-RNTI may correspond to an index of a monitoring window within a higher frame system number (H-FSN) period. The index of the monitoring window may be obtained by dividing the starting SFN of the transmission window by the window length and rounding down the result. In some scenarios, the minimum transmission window length Wmin may be used instead of the actual window length to simplify the computation.
[0056] In some implementations, the CB-RNTI may be used for CB-Msg4 monitoring and CB-Msg3 scrambling. For example, a network node may transmit a CB-Msg4 that is monitored using the CB-RNTI derived from the transmission window resource associated with the CB-Msg3 transmission.
[0057] In some scenarios, a single monitoring window and a single CB-RNTI may be adopted for CB-Msg4 monitoring corresponding to a CB-Msg3 transmission window. For example, according to certain agreements, a CB-RNTI derived from the transmission resource may be used for CB-Msg4 monitoring and CB-Msg3 scrambling.
[0058] In some implementations, the offset value used in CB-RNTI derivation may be selected to avoid identifier collision with random access radio network temporary identifiers (RA-RNTIs) . For example, the RA-RNTI maximum value may be 2400 for enhanced machine-type communication (eMTC) systems and 4096 for NB-IoT systems. Accordingly, the CB-RNTI may start from a value greater than the RA-RNTI maximum value in order to prevent identifier collision. In some scenarios, NB-IoT systems may support multiple non-anchor carriers. For example, the number of non-anchor carriers may be up to a predefined maximum value.
[0059] Proposal #3 provides the CB-Msg3 configuration. In some implementations, configuration parameters associated with CB-Msg3 transmission may be provided to a UE through system information. For instance, one or more CB-Msg3 related parameters may be configured in system information for a carrier, such as a non-anchor carrier. These parameters may define conditions for transmitting CB-Msg3 within a transmission window and for processing a corresponding CB-Msg3 response. In some scenarios, CB-Msg3 related parameters may be configured in System Information Block 22 (SIB22) for a non-anchor carrier. In some implementations, if certain CB-Msg3 related parameters configured in SIB22 for the non-anchor carrier are not present, parameters having the same name configured in System Information Block 2 (SIB2) for an anchor carrier may be used. In some scenarios, if parameters with the same name are not configured in SIB2, parameters having the same name in a first entry of an SIB22 list may be used.
[0060] In some implementations, CB-Msg3 transmission may be restricted to a configured dynamic scheduling access (DSA) transmission window. In some scenarios, CB-Msg3 or physical uplink shared channel (PUSCH) resource occasions located outside the DSA transmission window may not be utilized for CB-Msg3 transmission. In some implementations, the hybrid automatic repeat request (HARQ) process 0 may be used for CB-Msg3 transmissions and retransmissions. In some scenarios, HARQ process 0 may be configured as a default HARQ process for CB-Msg3 transmission. In some implementations, all CB-Msg3 replicas transmitted within the transmission window may use HARQ process 0. In some scenarios, a redundancy version 0 (RV0) may be used for transmitting a first repetition of each CB-Msg3 replica in the transmission window.
[0061] In some implementations, HARQ feedback may not be used for CB-Msg3 transmission. For example, HARQ mode B may not be applied to CB-Msg3 transmissions and retransmissions. In some scenarios, HARQ mode A may be used as a default mode for CB-Msg3 transmissions and retransmissions. In some implementations, additional information elements may be included in CB-Msg3. For example, a data volume and power headroom report (DPR) medium access control (MAC) control element may be included in the CB-Msg3 transmission.
[0062] Proposal #4 provides interference randomization of the CB-Msg3 response (CB-Msg4) . In some implementations, response processing associated with a CB-Msg4 may support interference randomization. In some scenarios, when interference randomization is enabled, a downlink transmission associated with the CB-Msg4 may be decoded using a scrambling sequence determined based on an identifier associated with the CB-Msg3, such as a CB-RNTI. Such a mechanism may improve the robustness of reception under interference conditions.
[0063] In some implementations, interference randomization may be applied to transmissions associated with a CB-Msg3 response carried on a narrowband physical downlink shared channel (NPDSCH) . In some scenarios, for frame structure type 1, interference randomization may be applied according to at least one of the following options. For example, in some implementations, interference randomization may be applied to NPDSCH associated with a CB-RNTI in an NB-IoT anchor carrier or non-anchor carrier when an interferenceRandomisationConfig parameter is configured for the specific carrier. In some scenarios, interference randomization may be applied to NPDSCH associated with a CB-RNTI when interferenceRandomisationConfig is configured for the carrier. In some implementations, interference randomization may alternatively be applied to NPDSCH associated with the CB-RNTI regardless of whether the configuration parameter is explicitly configured.
[0064] For NPDSCH, for frame structure type 1, at least one of the following options is provided.
[0065] Option 1: for NPDSCH associated with CB-RNTI in an NB-IoT anchor carrier or non-anchor carrier when interferenceRandomisationConfig for this specific carrier is configured.
[0066] Option 2: for NPDSCH associated with CB-RNTI when interferenceRandomisationConfig is configured.
[0067] Option 3: for NPDSCH associated with CB-RNTI.
[0068] In some scenarios, for frame structure type 2, interference randomization may be applied to NPDSCH transmissions that do not carry broadcast control channel (BCCH) information. In some implementations, a block of complex-valued symbols mapped to a subframe and radio frame may be multiplied by a phase rotation sequence prior to transmission. In some scenarios, each complex-valued symbol may be multiplied by a corresponding coefficient derived from a scrambling sequence, where the scrambling sequence may be initialized based on parameters including the CB-RNTI, radio frame number, subframe index, and cell identity. Such phase rotation may include values such as 1, -1, j, or -j depending on the values of the scrambling sequence.
[0069] For frame structure type 2, for NPDSCH not carrying the BCCH, some implementations define as the block of complex-valued symbols mapped to subframe number and radio frame number nf. Each complex-valued symbol is multiplied with before its transmission, with where the scrambling sequence is given by some agreements and is initialized at the start of each subframe with
[0070] In some implementations, interference randomization may also be applied to transmissions on a narrowband physical downlink control channel (NPDCCH) associated with the CB-Msg3 response. In some scenarios, for frame structure type 1, interference randomization may be applied to NPDCCH associated with a CB-RNTI when interferenceRandomisationConfig is configured for an NB-IoT anchor carrier or non-anchor carrier. In some implementations, interference randomization may alternatively be applied to NPDCCH associated with the CB-RNTI when the configuration parameter is present, or may be applied regardless of whether the configuration parameter is explicitly configured.
[0071] For NPDCCH, for frame structure type 1, at least one of the following options is provided.
[0072] Option 1: for NPDCCH associated with CB-RNTI in an NB-IoT anchor carrier or non-anchor carrier when interferenceRandomisationConfig for this specific carrier is configured.
[0073] Option 2: for NPDCCH associated with CB-RNTI when interferenceRandomisationConfig for this specific carrier is configured.
[0074] Option 3: for NPDCCH associated with CB-RNTI.
[0075] In some scenarios, for frame structure type 2, each complex-valued symbol mapped to NPDCCH resources may be multiplied by a phase rotation coefficient derived from a scrambling sequence. In some implementations, the scrambling sequence may be initialized at the start of each subframe using parameters including a cell identity and radio frame information.
[0076] For NPDCCH, for frame structure type 2, each complex-valued symbol 1 is multiplied with where:
[0077]
[0078] The scrambling sequence is given by some agreements and is initialized at the start of each subframe with
[0079] In some implementations, interference randomize may be enabled or disabled for CB-Msg3. In some implementations, the enable / disable configuration may be indicated by SIB, like SIB-22. In some implementations, the default configuration of Interference Randomize of CB-Msg3 is enabled. In some implementations, the default configuration of Interference Randomize of CB-Msg3 is disabled.
[0080] In some implementations, the interference randomization functionality may be enabled or disabled for CB-Msg3 related transmissions. In some scenarios, the enable or disable configuration may be indicated by system information, such as a system information block (SIB) , for example, SIB-22. In some implementations, a default configuration may be defined for the interference randomization functionality. For example, in some scenarios, interference randomization for CB-Msg3 related transmissions may be enabled by default, while in other implementations it may be disabled by default.
[0081] In some implementations, interference randomization may be applied to downlink transmissions associated with CB-Msg3 responses. In some scenarios, a CB-RNTI may be used as a scrambling seed for a PDSCH transmission, and the downlink PDSCH may be subject to interference randomization. In some implementations, interference randomization may be enabled for all downlink transmissions that use the CB-RNTI. In some scenarios, interference randomization may be enabled through network configuration. In some implementations, the configuration may be applied separately for anchor carriers and non-anchor carriers. In some scenarios, when interference randomization is enabled, the UE may perform decoding based on a modified scrambling sequence derived according to a predefined formula. In some implementations, the scrambling sequence may differ from a legacy sequence, and the UE may apply a corresponding decoding procedure based on the updated scrambling sequence.
[0082] Proposal #5 provides timing adjustment with CB-Msg3 and CB-Msg3 response (CB-Msg4) . In some implementations, the CB-Msg3 response may further include timing related information for uplink timing adjustment. For instance, a timing advance command may be provided in the CB-Msg3 response to indicate a timing advance value for adjusting uplink transmission timing of the UE. In some scenarios, the timing advance value may be represented using an index value associated with a timing advance command field, and the UE may determine a corresponding timing advance value based on the index value and a predefined mapping rule. In some implementations, the timing advance command included in the CB-Msg3 response may be used to compensate for timing inaccuracies when no physical random access channel (PRACH) procedure is performed. In some scenarios, since CB-Msg3 transmission may not rely on a conventional Msg1 / Msg2 exchange, the UE may initially determine uplink timing independently, which may result in timing misalignment. Accordingly, the network may transmit the timing advance command in the CB-Msg3 response to adjust the uplink timing of the UE.
[0083] In some implementations, transmission of the uplink radio frame number i from the UE may start seconds before the start of the corresponding downlink radio frame at the UE. In some implementations, the timing advance command may indicate the change of the uplink timing relative to the current uplink timing as multiples of 16Ts. The start timing of CB-Msg3 may fulfil where CB-Msg3 should assume NTA=0.
[0084] Alternative 1: In case of CB-Msg4, an 11-bit timing advance command, TA, indicates NTA values by index values of TA = 0, 1, 2, ..., 1536, where an amount of the time alignment is given by Option 1: NTA = TA ×16 or Option 2: NTA = (TA -1023) ×16. In some implementations, a timing advance command may be included in a CB-Msg4 to adjust the uplink timing of the UE. In some scenarios, the timing advance command may be represented using different bit lengths. For example, in some implementations, an 11-bit timing advance command may be used, where index values of the timing advance command range from 0 to 1536.
[0085] Alternative 2: In case of CB-Msg4, a 6-bit timing advance command, TA, indicates NTA values by index values of TA = 0, 1, 2, ..., 63, where an amount of the time alignment is given by Option 1: NTA = TA ×16 or Option 2: NTA = (TA -31) ×16. In some implementations, a shorter timing advance command may be used. For example, in some scenarios, a 6-bit timing advance command may indicate timing advance values using index values from 0 to 63.
[0086] Alternative 3: In case of CB-Msg4, a 7-bit timing advance command, TA, indicates NTA values by index values of TA = 0, 1, 2, ..., 127, where an amount of the time alignment is given by Option 1: NTA = TA ×16 or Option 2: NTA = (TA -63) ×16. In some implementations, a 7-bit timing advance command may also be used, where the index values range from 0 to 127.
[0087] In some implementations, a 6-bit timing advance command may be indicated in CB-Msg4. In some implementations, a 7-bit timing advance command may be indicated in CB-Msg4. In some implementations, an 11-bit timing advance command may be indicated in CB-Msg4.
[0088] In some scenarios, the timing advance command may be included in the CB-Msg3 response transmitted on a downlink channel, such as a CB-Msg4. In some implementations, a 6-bit timing advance command field may be used in the CB-Msg3 response, which may correspond to the timing advance command defined in the specification. In some scenarios, other bit lengths, such as 7 bits or 11 bits, may be supported for extended configurations or future enhancements. In some scenarios, the timing advance command in the CB-Msg3 response may be particularly useful when no physical random access channel (PRACH) is used, and no Msg1 / Msg2 timing advance exchange is performed. In such cases, the UE may initially determine uplink timing independently, which may introduce timing inaccuracies. Therefore, the network may provide a timing advance command in the CB-Msg3 response to adjust uplink timing and achieve proper time alignment.
[0089] Proposal #6 provides the configuration of the CB-Msg3 response (CB-Msg4) . In some implementations, the CB-Msg4 may include configuration information related to hybrid automatic repeat request (HARQ) feedback. For example, the CB-Msg3 response may indicate resources used for HARQ feedback and may include resource information associated with HARQ acknowledgment (ACK) feedback. In some scenarios, HARQ feedback configuration associated with the CB-Msg3 response may depend on parameters such as subcarrier spacing (SCS) , resource indication fields, or configuration parameters included in the response message.
[0090] In some implementations, for narrowband Internet of Things (NB-IoT) systems, the subcarrier spacing used for HARQ feedback associated with the CB-Msg3 response may be the same as the uplink subcarrier spacing used for CB-Msg3 transmission. In some scenarios, the HARQ feedback SCS may correspond to the SCS used by the UE when transmitting the CB-Msg3. For example, in some implementations supporting narrowband communications, the HARQ feedback SCS may be 3.75 kHz or 15 kHz. Such configuration may maintain timing consistency between uplink and downlink transmissions and simplify HARQ feedback processing at the UE.
[0091] For eMTC, the resource for the feedback of HARQ ACK is assigned by at least one of the options.
[0092] Option 1: HARQ ACK resource offset field in DCI and HARQ ACK resource offset for CB-Msg3 Response field in CB-Msg3 response, where the ΔARO is determined from the HARQ-ACK resource offset field in the DCI and HARQ ACK resource offset for CB-Msg3 Response field in CB-Msg3 response.
[0093] Option 2: HARQ ACK resource offset for CB-Msg3 Response field in CB-Msg3 response, where the ΔARO is determined from the HARQ ACK resource offset for CB-Msg3 Response field in CB-Msg3 response.
[0094] In some implementations, for enhanced machine-type communication (eMTC) systems, resources used for HARQ acknowledgment feedback may be assigned using resource indication fields included in control signaling or in the CB-Msg3 response. In some scenarios, the HARQ ACK feedback resource may be determined based on a HARQ ACK resource offset indicated in downlink control information (DCI) , together with a HARQ ACK resource offset field included in the CB-Msg3 response. In some implementations, the HARQ ACK resource may alternatively be determined solely based on a HARQ ACK resource offset field included in the CB-Msg3 response.
[0095] In some implementations, for NB-IoT, SubCarrierSpacing for HARQ feedback of CB-Msg3 response is the same as the one used for CB-Msg3. For NB-IOT, the resource for the feedback of HARQ ACK is assigned by at least one of the options.
[0096] Option 1: HARQ ACK resource field in DCI and HARQ ACK resource for CB-Msg3 Response field in CB-Msg3 response.
[0097] Option 2: HARQ ACK resource for CB-Msg3 Response field in CB-Msg3 response.
[0098] In some implementations, for NB-IoT systems, HARQ feedback resources may also be indicated through signaling fields associated with the CB-Msg3 response. In some scenarios, the HARQ feedback resource may be determined using a HARQ ACK resource field indicated in DCI, together with a HARQ ACK resource field included in the CB-Msg3 response. In some implementations, the HARQ ACK feedback resource may alternatively be determined based only on a HARQ ACK resource field included in the CB-Msg3 response.
[0099] In some implementations, HARQ feedback resource information may be included in the CB-Msg3 response together with a contention resolution identifier that identifies a specific UE. In some scenarios, whether HARQ feedback should be transmitted for a CB-Msg3 response may be controlled by the network. In some implementations, the UE may transmit HARQ acknowledgment feedback when reception is successful, while HARQ negative acknowledgment (NACK) feedback may not be transmitted. In some scenarios, the configuration of HARQ feedback resources and parameters associated with the CB-Msg3 response may provide flexible feedback control and improve the reliability of downlink reception for contention-based transmissions. Illustrative Implementations
[0100] FIG. 2 illustrates an example communication system 200 having an example communication apparatus 210 and an example network apparatus 220 in accordance with an implementation of the present disclosure. The communication apparatus 210 may correspond to a user equipment (UE) , and the network apparatus 220 may correspond to a network entity or a combination of network functions. Each of the communication apparatus 210 and the network apparatus 220 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to CB-Msg3 transmission and CB-Msg4 processing, including the scenarios and schemes described above as well as the example processes 300 and 400 described below with reference to FIG. 3 and FIG. 4.
[0101] Communication apparatus 210 may be a part of an electronic apparatus, which may be a UE such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus. For instance, communication apparatus 210 may be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Communication apparatus 210 may also be a part of a machine type apparatus, which may be an IoT, NB-IoT, or IIoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus. For instance, communication apparatus 210 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. Alternatively, communication apparatus 210 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. Communication apparatus 210 may include at least some of those components shown in FIG. 2 such as a processor 212, for example. Communication apparatus 210 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and / or user interface device) , and, thus, such component (s) of communication apparatus 210 are neither shown in FIG. 2 nor described below in the interest of simplicity and brevity.
[0102] Network apparatus 220 may be a part of a network apparatus, which may be a network node such as a satellite, a base station, a small cell, a router or a gateway. For instance, network apparatus 220 may be implemented in an eNodeB in an LTE network, in a gNB in a 5G / NR, IoT, NB-IoT or IIoT network or in a satellite or base station in a 6G network. Alternatively, network apparatus 220 may be implemented in the form of one or more IC chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network apparatus 220 may include at least some of those components shown in FIG. 2 such as a processor 222, for example. Network apparatus 220 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and / or user interface device) , and, thus, such component (s) of network apparatus 220 are neither shown in FIG. 2 nor described below in the interest of simplicity and brevity.
[0103] In one aspect, each of processor 212 and processor 222 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though a singular term “aprocessor” is used herein to refer to processor 212 and processor 222, each of processor 212 and processor 222 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor 212 and processor 222 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and / or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of processor 212 and processor 222 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks including CB-Msg3 transmission and CB-Msg4 processing in a device (e.g., as represented by communication apparatus 210) and a network (e.g., as represented by network apparatus 220) in accordance with various implementations of the present disclosure.
[0104] In some implementations, communication apparatus 210 may also include a transceiver 216 coupled to processor 212 and capable of wirelessly transmitting and receiving data. In other words, processor 212 may transceive the data such as configuration, message, signal, information, indicator, etc. via transceiver 216. In some implementations, communication apparatus 210 may further include a memory 214 coupled to processor 212 and capable of being accessed by processor 212 and storing data therein. In some implementations, network apparatus 220 may also include a transceiver 226 coupled to processor 222 and capable of wirelessly transmitting and receiving data. In other words, processor 222 may transceive the data such as configuration, message, signal, information, indicator, etc. via transceiver 226. In some implementations, network apparatus 220 may further include a memory 224 coupled to processor 222 and capable of being accessed by processor 222 and storing data therein. Accordingly, communication apparatus 210 and network apparatus 220 may wirelessly communicate with each other via transceiver 216 and transceiver 226, respectively. To aid better understanding, the following description of the operations, functionalities and capabilities of each of communication apparatus 210 and network apparatus 220 is provided in the context of a mobile communication environment in which communication apparatus 210 is implemented in or as a communication apparatus or a UE and network apparatus 220 is implemented in or as a network node of a communication network.
[0105] In some implementations, each of memory 214 and memory 224 may include a type of random-access memory (RAM) such as dynamic RAM (DRAM) , static RAM (SRAM) , thyristor RAM (T-RAM) and / or zero-capacitor RAM (Z-RAM) . Alternatively, or additionally, each of memory 214 and memory 224 may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM) , erasable programmable ROM (EPROM) and / or electrically erasable programmable ROM (EEPROM) . Alternatively, or additionally, each of memory 214 and memory 224 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM) , magnetoresistive RAM (MRAM) and / or phase-change memory. Illustrative Processes
[0106] FIG. 3 illustrates an example process 300 in accordance with an implementation of the present disclosure. Process 300 may be an example implementation of the scenarios and schemes described above, whether partially or completely, with respect to CB-Msg3 transmission and CB-Msg4 processing. Process 300 may represent an aspect of implementation of features of communication apparatus 210. Process 300 may include one or more operations, actions, or functions as illustrated by one or more of blocks 310 to 320. Although illustrated as discrete blocks, various blocks of process 300 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 300 may be executed in the order shown in FIG. 3 or, alternatively, in a different order. Process 300 may be implemented by communication apparatus 210 or any suitable UE. Solely for illustrative purposes and without limitation, process 300 is described below in the context of communication apparatus 210. Process 300 may begin at block 310.
[0107] At block 310, process 300 may involve processor 212 of communication apparatus 210, transmitting, via transceiver 216, a contention-based message 3 (CB-Msg3) in a transmission window using an identifier associated with the CB-Msg3. Process 300 may proceed from block 310 to block 320.
[0108] At block 320, process 300 may involve processor 212 of communication apparatus 210 receiving, via transceiver 216, a CB-Msg3 response (CB-Msg4) associated with the CB-Msg3. The CB-Msg3 and the CB-Msg4 may be associated with at least one configuration parameter related to an identifier derivation and a response processing. The identifier derivation may be based on a system frame number associated with the transmission window and a transmission window parameter.
[0109] In some implementations, the identifier may comprise a contention-based radio network temporary identifier (CB-RNTI) . In some implementations, the CB-RNTI may be derived based on a floor operation of the system frame number divided by the transmission window parameter, an offset value associated with a UE type, and optionally a carrier index identifying an uplink carrier associated with transmission of the CB-Msg3.
[0110] In some implementations, the offset value may comprise 2401 for a bandwidth limited (BL) UE or a UE in enhanced coverage. In some implementations, the offset value may comprise 4097 for a narrowband Internet of Things (NB-IoT) UE. The CB-RNTI may further depend on a value obtained from the carrier index and a scaling factor, and the carrier index of an anchor carrier may be 0.
[0111] In some implementations, the response processing may comprise, in an event that an interference randomization is enabled, decoding, by processor 212 of communication apparatus 210, a narrowband physical downlink shared channel (NPDSCH) transmission associated with the CB-RNTI using a scrambling sequence determined based on the CB-RNTI. In some implementations, the response processing comprises, in an event that an interference randomization is enabled, decoding, by processor 212 of communication apparatus 210, a narrowband physical downlink control channel (NPDCCH) transmission associated with the CB-RNTI using a scrambling sequence determined based on the CB-RNTI.
[0112] In some implementations, the at least one configuration parameter related to identifier derivation and response processing may comprise at least one CB-Msg3 related parameter configured in a System Information Block 22 (SIB22) for a non-anchor carrier. In some implementations, in an event that the at least one CB-Msg3 related parameter configured in SIB22 is not present, at least one parameter having a same name configured in a System Information Block 2 (SIB2) for an anchor carrier is used.
[0113] In some implementations, the response processing may comprise not utilizing at least one CB-Msg3 or physical uplink shared channel (PUSCH) resource occasion outside the transmission window associated with the CB-Msg3. In some implementations, the response processing may comprise using hybrid automatic repeat request (HARQ) process 0 for transmission and retransmission of the CB-Msg3 in the transmission window. In some implementations, the HARQ process 0 may be used to transmit all CB-Msg3 replicas in the transmission window.
[0114] In some implementations, redundancy version 0 (RV0) may be used to transmit a first repetition of each CB-Msg3 replica in the transmission window. In some implementations, the response processing may further comprise receiving, by processor 212 of communication apparatus 210, in the CB-Msg4, a timing advance command for adjusting uplink timing of communication apparatus 210. The timing advance command may indicate a timing advance value in multiples of a time unit. In some implementations, the timing advance command may comprise a 6-bit timing advance command (TAC) field indicating an index value, and the timing advance value may correspond to the index value multiplied by 16.
[0115] In some implementations, for a narrowband Internet of Things (NB-IoT) UE, a subcarrier spacing used for hybrid automatic repeat request (HARQ) feedback of the CB-Msg4 is the same as a subcarrier spacing used for transmission of the CB-Msg3. In some implementations, the CB-Msg4 may further comprise hybrid automatic repeat request (HARQ) feedback resource information together with a contention resolution identity identifying processor 212 of communication apparatus 210.
[0116] In some implementations, a resource for hybrid automatic repeat request (HARQ) feedback of the CB-Msg4 may be determined based on at least one of a HARQ ACK resource offset field included in the CB-Msg4 and a HARQ ACK resource field included in the CB-Msg4.
[0117] FIG. 4 illustrates another example process 400 in accordance with an implementation of the present disclosure. Process 400 may be an example implementation of the scenarios and schemes described above, whether partially or completely, with respect to network-side operations for CB-Msg3 transmission and CB-Msg4 processing. Process 400 may represent an aspect of implementation of features of network apparatus 220. Process 400 may include one or more operations, actions, or functions as illustrated by one or more of blocks 410 and 420. Although illustrated as discrete blocks, various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 400 may be executed in the order shown in FIG. 4 or, alternatively, in a different order. Process 400 may be implemented by network apparatus 220 or any suitable network entity or combination of network functions. Solely for illustrative purposes and without limitation, process 400 is described below in the context of network apparatus 220. Process 400 may begin at block 410.
[0118] At block 410, process 400 may involve processor 222 of network apparatus 220 receiving, via the transceiver 226, a contention-based message 3 (CB-Msg3) transmitted by a user equipment (UE) in a transmission window using an identifier associated with the CB-Msg3. Process 400 may proceed from block 410 to block 420.
[0119] At block 420, process 400 may involve processor 222 of network apparatus 220 transmitting, via the transceiver 226, a CB-Msg3 response (CB-Msg4) associated with the CB-Msg3. The CB-Msg3 and the CB-Msg4 may be associated with at least one configuration parameter related to identifier derivation and response processing. The identifier derivation may be based on a system frame number associated with the transmission window and a transmission window parameter.
[0120] In some implementations, the CB-Msg4 may further comprise hybrid automatic repeat request (HARQ) feedback resource information together with a contention resolution identity identifying the UE, and a resource for HARQ feedback of the CB-Msg4 may be indicated by at least one of a HARQ ACK resource offset field included in the CB-Msg4 and a HARQ ACK resource field included in the CB-Msg4. Additional Notes
[0121] The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected" , or "operably coupled" , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable" , to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.
[0122] Further, with respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.
[0123] Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to, ” the term “having” should be interpreted as “having at least, ” the term “includes” should be interpreted as “includes but is not limited to, ” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an, " e.g., “a” and / or “an” should be interpreted to mean “at least one” or “one or more; ” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two recitations, " without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B. ”
[0124] From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
Claims
1.A method, comprising:transmitting, by a user equipment (UE) , a contention-based message 3 (CB-Msg3) in a transmission window using an identifier associated with the CB-Msg3; andreceiving, by the UE, a CB-Msg3 response (CB-Msg4) associated with the CB-Msg3,wherein the CB-Msg3 and the CB-Msg4 are associated with at least one configuration parameter related to an identifier derivation and a response processing, and wherein the identifier derivation is based on a system frame number associated with the transmission window and a transmission window parameter.2.The method of Claim 1, wherein the identifier comprises a contention-based radio network temporary identifier (CB-RNTI) .3.The method of Claim 2, wherein the CB-RNTI is derived based on:a floor operation of the system frame number divided by the transmission window parameter;an offset value associated with a UE type; andoptionally a carrier index identifying an uplink carrier associated with transmission of the CB-Msg3.4.The method of Claim 3, wherein the offset value comprises 2401 for a bandwidth limited (BL) UE or a UE in enhanced coverage.5.The method of Claim 3, wherein the offset value comprises 4097 for a narrowband Internet of Things (NB-IoT) UE, wherein the CB-RNTI further depends on a value obtained from the carrier index and a scaling factor, and wherein the carrier index of an anchor carrier is 0.6.The method of Claim 2, wherein the response processing comprises, in an event that an interference randomization is enabled, decoding, by the UE, a narrowband physical downlink shared channel (NPDSCH) transmission associated with the CB-RNTI using a scrambling sequence determined based on the CB-RNTI.7.The method of Claim 2, wherein the response processing comprises, in an event that an interference randomization is enabled, decoding, by the UE, a narrowband physical downlink control channel (NPDCCH) transmission associated with the CB-RNTI using a scrambling sequence determined based on the CB-RNTI.8.The method of Claim 1, wherein the at least one configuration parameter related to identifier derivation and response processing comprises at least one CB-Msg3 related parameter configured in a System Information Block 22 (SIB22) for a non-anchor carrier.9.The method of Claim 1, wherein the response processing comprises not utilizing at least one CB-Msg3 or physical uplink shared channel (PUSCH) resource occasion outside the transmission window associated with the CB-Msg3.10.The method of Claim 1, wherein the response processing comprises using hybrid automatic repeat request (HARQ) process 0 for transmission and retransmission of the CB-Msg3 in the transmission window.11.The method of Claim 10, wherein the HARQ process 0 is used to transmit all CB-Msg3 replicas in the transmission window.12.The method of Claim 11, wherein redundancy version 0 (RV0) is used to transmit a first repetition of each CB-Msg3 replica in the transmission window.13.The method of Claim 1, wherein the response processing further comprises:receiving, by the UE, in the CB-Msg4, a timing advance command for adjusting uplink timing of the UE, wherein the timing advance command indicates a timing advance value in multiples of a time unit.14.The method of Claim 13, wherein the timing advance command comprises a 6-bit timing advance command (TAC) field indicating an index value, and wherein the timing advance value corresponds to the index value multiplied by 16.15.The method of Claim 1, wherein for a narrowband Internet of Things (NB-IoT) UE, a subcarrier spacing used for hybrid automatic repeat request (HARQ) feedback of the CB-Msg4 is the same as a subcarrier spacing used for transmission of the CB-Msg3.16.The method of Claim 1, wherein the CB-Msg4 further comprises hybrid automatic repeat request (HARQ) feedback resource information together with a contention resolution identity identifying the UE.17.The method of Claim 1, wherein a resource for hybrid automatic repeat request (HARQ) feedback of the CB-Msg4 is determined based on at least one of:a HARQ ACK resource offset field included in the CB-Msg4; anda HARQ ACK resource field included in the CB-Msg4.18.A user equipment (UE) , comprising:a transceiver which, during operation, wirelessly communicates with a network node; anda processor communicatively coupled to the transceiver such that, during operation, the processor performs operations comprising:transmitting, via the transceiver, a contention-based message 3 (CB-Msg3) in a transmission window using an identifier associated with the CB-Msg3; andreceiving, via the transceiver, a CB-Msg3 response (CB-Msg4) associated with the CB-Msg3,wherein the CB-Msg3 and the CB-Msg4 are associated with at least one configuration parameter related to an identifier derivation and a response processing, and wherein the identifier derivation is based on a system frame number associated with the transmission window and a transmission window parameter.19.A method, comprising:receiving, by a network node, a contention-based message 3 (CB-Msg3) transmitted by a user equipment (UE) in a transmission window using an identifier associated with the CB-Msg3;transmitting, by the network node, a CB-Msg3 response (CB-Msg4) associated with the CB-Msg3,wherein the CB-Msg3 and the CB-Msg4 are associated with at least one configuration parameter related to identifier derivation and response processing, andwherein the identifier derivation is based on a system frame number associated with the transmission window and a transmission window parameter.20.The method of Claim 19, wherein the CB-Msg4 further comprises hybrid automatic repeat request (HARQ) feedback resource information together with a contention resolution identity identifying the UE, and wherein a resource for HARQ feedback of the CB-Msg4 is indicated by at least one of:a HARQ ACK resource offset field included in the CB-Msg4; anda HARQ ACK resource field included in the CB-Msg4.
