Schemes for contention-based MSG3
The use of contention-based Msg3 methods for initial access in communication systems addresses inefficiencies in uplink access by optimizing CB-RNTI computation, configuration, and interference randomization, improving reliability and success rates.
Patent Information
- Application Number
- PCT/CN2025/093864
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
In communication systems, the initial access process is inefficient when timing offset is minimal or can be accurately pre-compensated, requiring a preamble for uplink access, which can be streamlined using contention-based Msg3 to enhance reliability and success rate.
Proposes methods for utilizing contention-based Msg3 for uplink access, including CB-RNTI computation, CB-Msg3 configuration, interference randomization, timing adjustment, and MAC PDU content configuration for BL UEs, UEs in enhanced coverage, and NB-IoT UEs, ensuring reliability and high success rate.
Enhances the reliability and success rate of the random access process by eliminating the need for a preamble and optimizing contention-based Msg3 procedures.
Smart Images

Figure CN2025093864_12112026_PF_FP_ABST
Abstract
Description
SCHEMES FOR CONTENTION-BASED MSG3FIELD
[0001] The invention discussed below relates generally to wireless communication, and more particularly, to methods for initial access.BACKGROUND
[0002] In communication systems, the initial access process is critically important. Traditionally, the initial access process requires the UE (User Equipment) to first send a preamble to initiate the uplink access trigger. However, in scenarios where the timing offset is minimal or can be accurately pre-compensated, uplink access can be triggered through contention-based Msg3, eliminating the need for a preamble during the uplink trigger process. This proposal introduces the necessary information and methods for utilizing contention-based Msg3 to trigger the uplink access process. By leveraging contention-based Msg3, the random access procedure can be streamlined, ensuring reliability and a high success rate.SUMMARY
[0003] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a preclude to the more detailed description that is presented later.
[0004] In one aspect of the disclosure, the method of CB-RNTI for BL UEs and UEs in enhanced coverage and NB-IoT UEs is proposed.
[0005] In another aspect of the disclosure, the method of CB-Msg3 configuration is proposed.
[0006] In another aspect of the disclosure, the Interference Randomization of CB-Msg3 Response is proposed.
[0007] In another aspect of the disclosure, the method of Timing adjustment with CB-Msg3 and CB-Msg3 Response is proposed.
[0008] In another aspect of the disclosure, the method of Configuration of CB-Msg3 Response is proposed.
[0009] In another aspect of the disclosure, the Content of MAC PDU of CB-Msg3 Response is proposed.
[0010] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed figures set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.BRIEF DESCRIPTION OF THE DRAWINGS
[0011] FIG. 1 illustrates an exemplary diagram of MAC PDU of CB-Msg3 Response.
[0012] FIG. 2 illustrates an exemplary diagram of CB-Msg3 BI subheader.
[0013] FIG. 3 illustrates an exemplary diagram of CBR subheader.
[0014] FIG. 4 illustrates an exemplary diagram of CB-Msg3 MAC SDU subheader.
[0015] FIG. 5 illustrates an exemplary diagram of Content of CB-Msg3 MAC CE / CBR of NB-IoT.
[0016] FIG. 6 illustrates an exemplary diagram of Content of CB-Msg3 MAC CE / CBR of EMTC.DETAILED DESCRIPTION
[0017] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
[0018] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
[0019] In communication systems, the initial access process is crucial. Traditionally, UE (User Equipment) needs to send a preamble to initiate uplink access. However, in scenarios with minimal timing offset or where timing can be accurately pre-compensated, uplink access can be triggered using contention-based Msg3, eliminating the need for a preamble. This patent introduces the necessary information and methods for using contention-based Msg3 to trigger uplink access. It outlines the essential information required and strategies to ensure the reliability and high success rate of the random access process using contention-based Msg3.
[0020] More specifically, we propose to consider the following proposal:
[0021] Proposal #1: CB-RNTI for BL UEs and UEs in enhanced coverage
[0022] 1. Option 1: For BL UEs and UEs in enhanced coverage, CB-RNTI associated with the CB-Msg3 in which the Contention-based PUSCH is transmitted, is computed as:
[0023] CB-RNTI = 1 + floor (SFN_id / Wmin)
[0024] where the SFN_id is the start SFN of the transmission window and the Wmin is the minimum value of transmission window length or where the SFN_id is the end SFN of the transmission window and the Wmin is the minimum value of transmission window length.
[0025] 2. Option 2: For BL UEs and UEs in enhanced coverage, CB-RNTI associated with the CB-Msg3 in which the Contention-based PUSCH is transmitted, is computed as:
[0026] CB-RNTI = 2401 + floor (SFN_id / Wmin)
[0027] where the SFN_id is the start SFN of the transmission window and the Wmin is the minimum value of transmission window length or where the SFN_id is the end SFN of the transmission window and the Wmin is the minimum value of transmission window length.
[0028] 3. Option 3: For BL UEs and UEs in enhanced coverage, CB-RNTI associated with the CB-Msg3 in which the Contention-based PUSCH is transmitted, is computed as:
[0029] CB-RNTI = 2402 + floor (SFN_id / Wmin)
[0030] where the SFN_id is the start SFN of the transmission window and the Wmin is the minimum value of transmission window length or where the SFN_id is the end SFN of the transmission window and the Wmin is the minimum value of transmission window length.
[0031] NOTE:
[0032] · Wmin can be predefined value where at lease the value is one of {2, 4, 6, 8, 12, 16, 20, 32, 40, 64} .
[0033] · Wmin can be configured value, where Wmin can be configured via 1 / 2 / 3 bits in SIB and updated by SIB / RRC with candidate value set from values of {2, 4, 6, 8, 12, 16, 20, 32, 40, 64} .
[0034] Proposal #2: CB-RNTI for NB-IoT UEs
[0035] 1. Option 1: For NB-IoT UEs, CB-RNTI associated with the CB-Msg3 in which the Contention-based PUSCH is transmitted, is computed as:
[0036] CB-RNTI = 1 + + floor (SFN_id / Wmin) + N*carrier_id
[0037] where the SFN_id is the start SFN of the transmission window and the Wmin is the minimum value of transmission window length or where the SFN_id is the end SFN of the transmission window and the Wmin is the minimum value of transmission window length and the carrier_id is the index of UL carrier associated with the specified CB-Msg3 and the N can be the maximum value of floor (SFN_id / Wmin) . The carrier_id of the anchor carrier is 0.
[0038] 2. Option 2: For NB-IoT UEs, CB-RNTI associated with the CB-Msg3 in which the Contention-based PUSCH is transmitted, is computed as:
[0039] CB-RNTI = 4096 + floor (SFN_id / Wmin) + N*carrier_id
[0040] where the SFN_id is the start SFN of the transmission window and the Wmin is the minimum value of transmission window length or where the SFN_id is the end SFN of the transmission window and the Wmin is the minimum value of transmission window length and the carrier_id is the index of UL carrier associated with the specified CB-Msg3 and the N can be the maximum value of floor (SFN_id / Wmin) . The carrier_id of the anchor carrier is 0.
[0041] 3. Option 3: For NB-IoT UEs, CB-RNTI associated with the CB-Msg3 in which the Contention-based PUSCH is transmitted, is computed as:
[0042] CB-RNTI = 4097 + floor (SFN_id / Wmin) + N*carrier_id
[0043] where the SFN_id is the start SFN of the transmission window and the Wmin is the minimum value of transmission window length or where the SFN_id is the end SFN of the transmission window and the Wmin is the minimum value of transmission window length and the carrier_id is the index of UL carrier associated with the specified CB-Msg3 and the N can be the maximum value of floor (SFN_id / Wmin) . The carrier_id of the anchor carrier is 0.
[0044] 4. Option 4: For NB-IoT UEs operating in TDD mode, CB-RNTI associated with the CB-Msg3 in which the Contention-based PUSCH is transmitted, is computed as:
[0045] CB-RNTI = 1 + floor (SFN_id / Wmin) + N* (H-SFN mod 2)
[0046] where the SFN_id is the start SFN of the transmission window and the Wmin is the minimum value of transmission window length or where the SFN_id is the end SFN of the transmission window and the Wmin is the minimum value of transmission window. H-SFN is the index of the first hyper frame of the specified CB-Msg3. The PDCCH transmission and the CB-Msg3 resource are on the same carrier.
[0047] 5. Option 5: For NB-IoT UEs operating in TDD mode, CB-RNTI associated with the CB-Msg3 in which the Contention-based PUSCH is transmitted, is computed as:
[0048] CB-RNTI = 768 + floor (SFN_id / Wmin) + N* (H-SFN mod 2)
[0049] where the SFN_id is the start SFN of the transmission window and the Wmin is the minimum value of transmission window length or where the SFN_id is the end SFN of the transmission window and the Wmin is the minimum value of transmission window. H-SFN is the index of the first hyper frame of the specified CB-Msg3. The PDCCH transmission and the CB-Msg3 resource are on the same carrier.
[0050] 6. Option 5: For NB-IoT UEs operating in TDD mode, CB-RNTI associated with the CB-Msg3 in which the Contention-based PUSCH is transmitted, is computed as:
[0051] CB-RNTI = 769 + floor (SFN_id / Wmin) + N* (H-SFN mod 2)
[0052] where the SFN_id is the start SFN of the transmission window and the Wmin is the minimum value of transmission window length or where the SFN_id is the end SFN of the transmission window and the Wmin is the minimum value of transmission window. H-SFN is the index of the first hyper frame of the specified CB-Msg3. The PDCCH transmission and the CB-Msg3 resource are on the same carrier.
[0053] NOTE:
[0054] · Wmin can be predefined value where at lease the value is one of {2, 4, 6, 8, 12, 16, 20, 32, 40, 64} .
[0055] · Wmin can be configured value, where Wmin can be configured via 1 / 2 / 3 bits in SIB and updated by SIB / RRC with candidate value set from values of {2, 4, 6, 8, 12, 16, 20, 32, 40, 64} .
[0056] · N can be predefined value where at lease the value is one of {512, 256, 170, 128, 85, 64, 51, 32, 25, 16} .
[0057] · N can be configured value, where N can be configured via 1 / 2 / 3 bits in SIB and updated by SIB / RRC with candidate value set from values of {512, 256, 170, 128, 85, 64, 51, 32, 25, 16} .
[0058] · N can be configured value, where N can be derived via N= floor (1024 / Wmin) .
[0059] Proposal #3: CB-Msg3 configuration
[0060] · CB-MSG3 related parameters that configured in SIB22 for non anchor carrier. If some CB-MSG3 related parameters configured in SIB22 for a non anchor carrier is not present, the parameters with the same name configured in SIB2 for anchor carrier can be used. If there is no parameter with the same name configured in SIB2, then the parameters with the same name in the first entity of the SIB22 list can be used.
[0061] · For CB-MSG3, the CB-MSG3 or PUSCH resource occasions that are outside the DSA transmission window shall not be utilized.
[0062] · HARQ process 0 is used or default for CB-Msg3 transmissions and retransmissions.
[0063] · HARQ mode B is not used for CB-Msg3 transmissions and retransmissions. Or HARQ mode A is default for CB-Msg3 transmissions and retransmissions.
[0064] · Data Volume and Power Headroom Report MAC Control Element can be included in CB-Msg3
[0065] Proposal #4: Interference Randomization of CB-Msg3 Response
[0066] · For NPDSCH:
[0067] For frame structure type 1,
[0068] - 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, or
[0069] - Option 2: for NPDSCH associated with CB-RNTI when interferenceRandomisationConfig is configured, or
[0070] - Option 3: for NPDSCH associated with CB-RNTI, or
[0071] for frame structure type 2,
[0072] -for NPDSCH not carrying the BCCH,
[0073] define as the block of complex-valued symbols mapped to subframe number and radio frame number nf. Each complex-valued symbol shall be multiplied with before its transmission, with
[0074] where the scrambling sequence given by clause 7.2 and shall be initialized at the start of each subframe with
[0075] · For NPDCCH:
[0076] For frame structure type 1,
[0077] - 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, or
[0078] - Option 2: for NPDCCH associated with CB-RNTI when interferenceRandomisationConfig for this specific carrier is configured, or
[0079] - Option 3: for NPDCCH associated with CB-RNTI, or
[0080] for frame structure type 2,
[0081] each complex-valued symbol shall be multiplied with where
[0082] where the scrambling sequence is given by clause 7.2 and shall be initialized at the start of each subframe with
[0083] Note:
[0084] · Interference Randomize can be enabled or disabled for CB-Msg3.
[0085] · The enable / disable configuration can be indicated by SIB, like SIB-22.
[0086] · The default configuration of Interference Randomize of CB-Msg3 is enabled. Or The default configuration of Interference Randomize of CB-Msg3 is disabled.
[0087] Proposal #5: Timing adjustment with CB-Msg3 and CB-Msg3 Response
[0088] Transmission of the uplink radio frame number i from the UE shall start seconds before the start of the corresponding downlink radio frame at the UE.
[0089] · The timing advance command indicates the change of the uplink timing relative to the current uplink timing as multiples of 16Ts. The start timing of CB-Msg3 shall fulfil where CB-Msg3 should assume NTA =0.
[0090] · Alternative 1: In case of CB-Msg3 Response, 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
[0091] Option 1: NTA = TA ×16.
[0092] Option 2: NTA = (TA -1023) ×16.
[0093] · Alternative 2: In case of CB-Msg3 Response, an 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
[0094] Option 1: NTA = TA ×16.
[0095] Option 2: NTA = (TA -31) ×16.
[0096] · Alternative 3: In case of CB-Msg3 Response, an 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
[0097] Option 1: NTA = TA ×16.
[0098] Option 2: NTA = (TA -63) ×16.
[0099] Note:
[0100] · 6-bit timing advance command can be indicated in CB-Msg3 Response.
[0101] · 7-bit timing advance command can be indicated in CB-Msg3 Response.
[0102] · 11-bit timing advance command can be indicated in CB-Msg3 Response
[0103] Proposal #6: Configuration of CB-Msg3 Response
[0104] · For NB-IoT, SubCarrierSpacing for HARQ feedback of CB-Msg3 response is same as the one used for CB-Msg3
[0105] · For eMTC, the resource for the feedback of HARQ ACK is assigned by
[0106] – 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.
[0107] – 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.
[0108] · For NB-IOT, the resource for the feedback of HARQ ACK is assigned by
[0109] – Option 1: “HARQ ACK resource” field in DCI and “HARQ ACK resource for CB-Msg3 Response” field in CB-Msg3 response.
[0110] – Option 2: “HARQ ACK resource for CB-Msg3 Response” field in CB-Msg3 response
[0111] Proposal #7: Content of MAC PDU of CB-Msg3 Response
[0112] · MAC PDU of CB-Msg3 Response is a bit string that is byte aligned (i.e. multiple of 8 bits) in length
[0113] · In the figure 1, bit strings are represented by tables in which the most significant bit is the leftmost bit of the first line of the table, the least significant bit is the rightmost bit on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines. The bit order of each parameter field within a MAC PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit.
[0114] · A MAC PDU header of CB-Msg3 Response consists of one or more MAC PDU subheaders of CB-Msg3 Response;
[0115] · The types of subheader have at least one of the following:
[0116] · CB-Msg3 BI subheader
[0117] · CBR subheader
[0118] · CB-Msg3 MAC SDU subheader
[0119] · Each CBR subheader corresponds to different UEs. The CB-Msg3 MAC SDU subheader belongs to the UE corresponding to the previous MAC CBR subheader.
[0120] · MAC PDU of CB-Msg3 Response have at least one of the following:
[0121] · MAC header
[0122] · MAC CB-Msg3 Response (CBR)
[0123] · MAC SDU
[0124] · Optionally Padding
[0125] Proposal #8: CB-Msg3 BI subheader
[0126] · Subheader Type 1 CB-Msg3 BI subheader : CB-Msg3 MAC subheader with 1 byte or 8 bits has the same order as depicted in Fig 2. A MAC PDU subheader of CB-Msg3 consists of at least one of:
[0127] the header field E for subheader / payload indication
[0128] the header field T for subheader type indication
[0129] the header field R for reserved bits
[0130] the header field BI for backoff indication
[0131] Proposal #9: CBR subheader
[0132] · Subheader type 2 CBR subheader : CB-Msg3 MAC subheader with 1 byte or 8 bits has the same order as depicted in Fig 3. A MAC PDU subheader of CB-Msg3 consists of at least one of:
[0133] the header field E for subheader / payload indication
[0134] the header field T for subheader type indication
[0135] the header field T2 for HARQ ACK resource present or not indication, to indicate whether there is HARQ ACK resource in the MAC CBR
[0136] the header field T3 for Timing Advance Command (TAC) present or not indication, to indicate whether there is TAC in the MAC CBR
[0137] the header field R for reserved bits
[0138] the header field T4 for C-RNTI present or not indication, to indicate whether there is C-RNTI in the MAC CBR
[0139] Proposal #10: CB-Msg3 MAC SDU subheader
[0140] · Subheader type 3 CB-Msg3 MAC SDU subheader: CB-Msg3 MAC SDU subheader with 1 or 2 bytes has the same order as depicted in Fig 4. A MAC SDU subheader of CB-Msg3 consists of at least one of:
[0141] the header field E for subheader / payload indication
[0142] the header field T for subheader type indication
[0143] the header field LCID for identifiing the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC control element or CB-Msg3 MAC CBR or padding
[0144] the header field F for the size of the Length field. If the F field is included; if the length of MAC SDU or the MAC control element is less than 128 bytes, the value of the F field is set to 0, otherwise it is set to 1;
[0145] the header field L for the length of the corresponding MAC SDU or the corresponding MAC control element
[0146] the header field R for reserved bits
[0147] Proposal #11: Content of CB-Msg3 MAC CE / CBR
[0148] The CB-Msg3 MAC CBR as depicted in Figure 5 and Figure 6 is of flexible size with 6 or 7 or 8 or 9 or 10 bytes and consists of at least one of the following fields:
[0149] · R: Reserved bit, set to "0" .
[0150] · Timing Advance Command: The Timing Advance Command field indicates the index value TA used to control the amount of timing adjustment that the MAC entity has to apply. The size of the Timing Advance Command field is 11 bits or 6 bits or 7 bits;
[0151] · UE Contention Resolution Identity: 48-bit size.
[0152] · HARQ ACK resource for CB-Msg3 Response: the resource for the feedback of HARQ ACK in NB-IOT
[0153] · HARQ ACK resource offset for CB-Msg3 Response: the resource for the feedback of HARQ ACK in eMTC
[0154] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “UE, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”
[0155] While aspects of the present disclosure have been described in conjunction with the specific embodiments thereof that are proposed as examples, alternatives, modifications, and variations to the examples may be made. Accordingly, embodiments as set forth herein are intended to be illustrative and not limiting. There are changes that may be made without departing from the scope of the claims set forth below.
Claims
1.A method of schemes for Contention-based Msg3 related issues.2.The method of claim 1, wherein CB-RNTI for BL UEs and UEs in enhanced coverage can be calculated as:a. CB-RNTI = 1 + floor (SFN_id / Wmin) ;b. or CB-RNTI = 2401 + floor (SFN_id / Wmin) ;c. or CB-RNTI = 2402 + floor (SFN_id / Wmin) .3.The method of claim 1, wherein CB-RNTI for NB-IoT can be calculated as:a. CB-RNTI = 1+ floor (SFN_id / Wmin) + N*carrier_id;b. or CB-RNTI = 4096+ floor (SFN_id / Wmin) + N*carrier_id;c. or CB-RNTI = 4097+ floor (SFN_id / Wmin) + N*carrier_id;d. or CB-RNTI = 1 + floor (SFN_id / Wmin) + N* (H-SFN mod 2) ;e. or CB-RNTI = 768 + floor (SFN_id / Wmin) + N* (H-SFN mod 2) ;f. or CB-RNTI = 769 + floor (SFN_id / Wmin) + N* (H-SFN mod 2) .4.The method of claim 2 or 3, wherein Wmin can be predefined value where at lease the value is one of {2, 4, 6, 8, 12, 16, 20, 32, 40, 64} , or Wmin can be configured value, where Wmin can be configured via 1 / 2 / 3 bits in SIB and updated by SIB / RRC with candidate value set from values of {2, 4, 6, 8, 12, 16, 20, 32, 40, 64} .5.The method of claim 3, wherein N can be predefined value where at lease the value is one of {512, 256, 170, 128, 85, 64, 51, 32, 25, 16} ; or N can be configured value, where N can be configured via 1 / 2 / 3 bits in SIB and updated by SIB / RRC with candidate value set from values of {512, 256, 170, 128, 85, 64, 51, 32, 25, 16} ; or N can be configured value, where N can be derived via N= floor (1024 / Wmin) .6.The method of claim 1, wherein CB-MSG3 related parameters that configured in SIB22 for non anchor carrier, if some CB-MSG3 related parameters configured in SIB22 for a non anchor carrier is not present, the parameters with the same name configured in SIB2 for anchor carrier can be used; if there is no parameter with the same name configured in SIB2, then the parameters with the same name in the first entity of the SIB22 list can be used.7.The method of claim 1, wherein for CB-MSG3, the CB-MSG3 or PUSCH resource occasions that are outside the DSA transmission window shall not be utilized.8.The method of claim 1, wherein HARQ process 0 is used or default for CB-Msg3 transmissions and retransmissions.9.The method of claim 1, wherein HARQ mode B is not used for CB-Msg3 transmissions and retransmissions, or HARQ mode A is default for CB-Msg3 transmissions and retransmissions.10.The method of claim 1, wherein Data Volume and Power Headroom Report MAC Control Element can be included in CB-Msg3.11.The method of claim 1, wherein Interference Randomization of CB-Msg3 Response can be applied.12.The method of claim 1, wherein Timing adjustment with CB-Msg3 and CB-Msg3 Response can be calculated as:a. NTA = TA ×16;b. NTA = (TA -1023) ×16;c. NTA = (TA -31) ×16;d. NTA = (TA -63) ×16.13.The method of claim 1, wherein for NB-IoT, SubCarrierSpacing for HARQ feedback of CB-Msg3 response is same as the one used for CB-Msg3.14.The method of claim 1, wherein the resource for the feedback of HARQ ACK is assigned by DCI and / or CB-Msg3 response.15.The method of claim 1, wherein MAC PDU of CB-Msg3 Response have at least one of the following:a. MAC header;b. MAC CB-Msg3 Response (CBR) ;c. MAC SDU;d. Optionally Padding.16.The method of claim 1, wherein A MAC PDU header of CB-Msg3 Response consists of one or more MAC PDU subheaders of CB-Msg3 Response.17.The method of claim 1, wherein he types of subheader of CB-Msg3 Response have at least one of the following:a. CB-Msg3 BI subheader;b. CBR subheader;c. CB-Msg3 MAC SDU subheader.18.The method of claim 1, wherein the CB-Msg3 MAC CBR is of flexible size with 6 or 7 or 8 or 9 or 10 bytes and consists of at least one of the following fields:a. R: Reserved bit, set to "0" ;b. Timing Advance Command: the Timing Advance Command field indicates the index value TA used to control the amount of timing adjustment that the MAC entity has to apply, the size of the Timing Advance Command field is 11 bits or 6 bits or 7 bits;c. UE Contention Resolution Identity: 48-bit size;d. HARQ ACK resource for CB-Msg3 Response: the resource for the feedback of HARQ ACK in NB-IOT;e. HARQ ACK resource offset for CB-Msg3 Response: the resource for the feedback of HARQ ACK in eMTC.
