TW202041087A - Communicating between a terminal and a wireless network node - Google Patents

Abstract

An apparatus comprising means for: sending an uplink message (MsgA) in a two-step random access procedure; receiving a downlink reply message (MsgB) in the two-step random access procedure, the received downlink reply message comprising an identifier for the apparatus; and sending an uplink acknowledgement message using a PUCCH resource determined by a PUCCH resource index wherein the PUCCH resource index is dependent upon, at least, a PUCCH resource indicator (PRI) and the identifier of the apparatus.

Description

Communication technology between terminal and wireless network node

The embodiment of the disclosure relates to the communication between the terminal and the wireless network node.

A wireless network includes a plurality of network nodes including terminal nodes and access nodes.

The terminal node and the access node communicate with each other wirelessly.

In some cases, it may be desirable to reduce power consumption at the terminal node.

According to various, but not necessarily all, embodiments, examples as claimed in the scope of the appended application are provided.

definition ACK Confirm BWP Bandwidth part CCE Control Channel Elements CS cyclic shift DCI Downlink control information HARQ mixed confirmation request NW Network PRB physical resource block PRACH entity RACH PRI PUCCH resource indicator PUCCH physical uplink control channel RA Random access RA-RNTI random access to radio network temporary identifier RACH Random access channel RAR Random response RO RACH timing UCI Uplink control information UE User Equipment

FIG. 1 shows an example of a network 100, which includes a plurality of network nodes including a terminal node 110, an access node 120, and one or more core nodes 1129. The terminal node 110 and the access node 120 communicate with each other wirelessly. One or more core nodes 129 communicate with the access node 120.

In some examples, one or more core nodes 129 may communicate with each other. In some examples, one or more access nodes 120 may communicate with each other.

The network 100 may be a cellular network, which includes a plurality of cells 122 each served by an access node 120. In this example, the interface defining a cell 122 between the terminal node 110 and an access node 120 is a wireless interface 124.

The access node 120 is a cellular radio transceiver. The terminal node 110 is a cellular radio transceiver.

In the example, the cellular network 100 shown is a third-generation partnership project (3GPP) network, where the terminal node 110 is a user equipment (UE) and the access node 120 is a base station.

In a specific example, the network 100 shown is an evolved universal terrestrial radio access network (E-UTRAN). E-UTRAN is composed of E-UTRAN Node B (eNB) 120, and provides E-UTRA user plane and control plane (RRC) agreed terminals to UE 110. The eNBs 120 are interconnected with each other via an X2 interface 126. The eNB also connects to a mobility management entity (MME) 129 via the S1 interface 128.

In other examples, the network 100 is a next-generation (or New Radio NR) radio access network (NG-RAN). The NG-RAN is composed of gNodeB (gNB) 120 and provides user plane and control plane (RRC) protocol terminals to UE 110. The gNB 120 is interconnected with each other via an X2/Xn interface 126. The gNB is also connected to the access and mobility management function (AMF) via the N2 interface 128.

The current development of radio access networks is focused on supporting a large number of latent time tolerance, low data UE 110. This makes machine type communication (MTC) and cellular Internet of Things (IoT) possible. MTC and IoT devices can only transmit data bursty, and the network must support burst data transmission by a UE 110 when it is in the idle mode 130.

A UE 110 can transmit to the network 100 so that the network can classify the UE 110 according to latency requirements, data bandwidth requirements, and mobility requirements. For example, one of the physical layer enhancements used in the machine type communication (eMTC) protocol can use one of 1.4 MHz to reduce the bandwidth. For example, a narrowband Internet of Things (NB-IoT) protocol uses one of 200 kHz to reduce the bandwidth. The expected mobility of UE 110, one of the NB-IoT protocols, is very low. The NB-IoT protocol is not handed over in the connected mode 132.

UE 110 can operate under different coverage enhancement levels. This means that in the same cell 122, different UEs 110 can use the same logical channel, but between UEs 110 operating at different coverage enhancement levels, the characteristics of the corresponding physical channel (narrowband resources, repetition, etc.) can be very different.

FIG. 2 shows an example of the different modes 130 and 132 of the UE 110 and the transitions 131 and 133 between the modes 130 and 132.

The connected mode 132 is a mode that enables communication between the UE 110 and the network 100 at a higher layer, for example, to enable communication of application data or higher-level signaling.

For example, the random access procedure is used for the transition from the idle mode (or inactive mode) 130 to the connected mode 131, and when the UE 110 is in the connected mode when the UL is not synchronized, or when there is no dedicated row configuration. When requesting resources, it is used to request UL resources or to recover from beam failure. One of the transition 133 from the connected mode 132 to the idle mode 130, for example, can occur when the connection is released or the wireless link fails.

In the NG-RAN network 100, the idle or inactive mode 130 corresponds to RRC_IDLE or RRC_INACTIVE, respectively, and the connected mode corresponds to RRC_CONNECTED. Transition 131 corresponds to, for example, RRC connection establishment, RRC connection reestablishment, RRC connection recovery, or early data transmission (EDT). Transition 133, for example, corresponds to RRC connection release (also a radio link failure).

Hereinafter, a terminal node 110 will be referred to as a terminal 110.

A terminal 110 is a device that terminates the cell side of the radio link. It is a device that allows access to network services. The terminal 110 may be a mobile terminal. The terminal 110 may be user equipment or mobile equipment. User equipment is mobile equipment plus a user identity module (SIM).

An access node 120 is a network component in the radio access network responsible for radio transmission to or reception from the terminal 110 in one or more cells 122. The access node 120 is the network terminal of the radio link. The access node 120 operates as NodeB, eNodeB, and gNodeB.

FIG. 3 shows an example of a random access procedure 200 based on a 4-step competition. Section 10.1.5 of 3GPP TS 36.300 (2018 version 15) describes an example of a competition-based random access procedure.

The random access procedure based on competition is a common procedure for frequency division duplex (FDD) and time division duplex (TDD). For example, the random access procedure based on competition can be used for the initial access from RRC_IDLE. This can be done for RRC connection establishment, RRC connection reestablishment or early data transmission (EDT) or other reasons.

In the first step, when a terminal node 110 sends an uplink initiation message (Msg1) 202 to an access node 120, the 4-step contention-based random access procedure 200 is started. This is the random access preamble code in Section 10.1.5 of 3GPP TS 36.300 (2018 version 15). Msg1 202 is sent in the logical random access channel (RACH), and physically sent in the physical random access channel (PRACH). The terminal node 110 selects a random access resource based on the conditions broadcast on the test system information at the terminal node 110 and randomly selects a preamble code, for example, including random access timing (RO) and preamble code in the selected RO Group. For example, such conditions may include a signal level of a beam (such as RSRP, RSRQ, SINR).

Secondly, in the second step, the access node 120 responds to receiving an uplink initiation message (Msg1) 202 by sending a downlink response (Msg2) 204 from the access node 120 to the terminal node 110. The downlink response 204 includes an initial uplink grant. The downlink response 204 is a random access response in section 10.1.5 of 3GPP TS 36.300 (version 15 in 2018). The random access response additionally includes timing alignment information for determining timing advance. It is addressed to RA-RNTI on PDCCH. The random access RNTI (RA-RNTI) clearly identifies which time-frequency resource the terminal node 110 uses to transmit the random access preamble 202 within a configured time window (random access response time window).

The terminal node 110 uses timing advance to advance/delay its transmission timing to the access node 120 in order to compensate for the propagation delay between the terminal node 110 and the access node 120.

Secondly, in the third step, the terminal node 110 responds to the downlink response (Msg2) received from the access node 120 by sending an uplink connection request (Msg3) 206 from the terminal node 110 to the access node 120 ) 204. The uplink connection request 206 may include an identifier of the terminal node 110. The uplink connection request 206 is a scheduled transmission in section 10.1.5 of 3GPP TS 36.300 (Release 15, 2018). The identifier of the terminal node 110 is the UE identifier. The scheduled transmission 206 is sent according to the initial uplink grant provided in the random access response 204. The scheduled transmission may include an RRC connection request, an RRC connection reestablishment request, an RRC connection reply request, or, if early data transmission (EDT) is enabled, an RRC EarlyDataRequest, or in one possibility, it does not include RRC messages , But includes C-RNTI MAC CE (Media Access Control Control Element) for connected mode terminal nodes.

Second, in the fourth step, the access node 120 responds to receiving the uplink connection request 206 by sending a downlink response (Msg4) 208 from the access node 120 to the terminal node 110. The downlink response 208 to the uplink connection request 206 includes an identifier of the terminal node 110 received in the uplink connection request 206. The downlink response 208 to the uplink connection request 206 is a contention resolution in section 10.1.5 of 3GPP TS 36.300 (Release 15, 2018).

If the access node 120 can decode the Msg3 206, in the fourth step, by including the contention resolution ID of the terminal node in the contention resolution MAC PDU (IDLE/INACTIVE mode terminal node), or by directly communicating with the terminal node C-RNTI (Connected Mode Terminal Node) performs scheduling and contention resolution occurs.

Focusing only on the IDLE/INACTIVE mode terminal node, the terminal node 110 that decodes its contention resolution ID from the MAC PDU then sends a HARQ ACK to the access node 120 (NACK is not transmitted, because the terminal node 110 obviously does not know whether the contention resolution is It happens).

PRB之一初始上行鏈路BWP中傳輸有關PUCCH之HARQ-ACK資訊。Therefore, in the 4-step random access procedure 200, a terminal node 110 transmits HARQ ACK/NACK feedback to the Msg4 208. A PUCCH resource set is provided by pucch-ResourceCommon that transmits signaling in RMSI through an index in a column of Table 9.2.1-1 in 3GPP TS 38.213 (2018 version 15).

The HARQ-ACK information related to PUCCH is transmitted in the initial uplink BWP of one of the PRBs.

，以及 用於一PUCCH傳輸之一循環移位索引集。The PUCCH resource set includes sixteen resources (16 index values), and each resource corresponds to: a PUCCH format, a first symbol, a duration, and a PRB offset

, And a cyclic shift index set for a PUCCH transmission.

The terminal node 110 uses frequency hopping to transmit a PUCCH. In Table 9.2.1-1, an orthogonal orthogonal cover code with an index of 0 is used for a PUCCH resource with a PUCCH format of 1.

，

，確定為

，其中

係一PDCCH接收之一CORESET中之若干CCE，

係用於PDCCH接收之一第一CCE之索引，並且

係DCI中PUCCH資源指示符欄位之一值。 若

- 終端節點110將第一跳躍中PUCCH傳輸之PRB索引確定為

，並且將第二跳躍中PUCCH傳輸之PRB索引確定為

， 其中

係初始循環移位索引集合中初始循環移位索引之總數， - 終端節點110將初始循環移位索引集合中之初始循環移位索引確定為

。 若

- 終端節點110將第一跳躍中PUCCH傳輸之PRB索引確定為

，並且將第二跳躍中PUCCH傳輸之PRB索引確定為

， - 終端節點110將初始循環移位索引集合中之初始循環移位索引確定為

。The terminal node 110 indexes the PUCCH resource

,

, Determined as

,among them

A PDCCH receives a number of CCEs in a CORESET,

Is the index of the first CCE used for PDCCH reception, and

It is a value of the PUCCH resource indicator field in DCI. If

-The terminal node 110 determines the PRB index of the PUCCH transmission in the first hop as

, And determine the PRB index of PUCCH transmission in the second hop as

, among them

Is the total number of initial cyclic shift indexes in the initial cyclic shift index set,-the terminal node 110 determines the initial cyclic shift index in the initial cyclic shift index set as

. If

-The terminal node 110 determines the PRB index of the PUCCH transmission in the first hop as

, And determine the PRB index of PUCCH transmission in the second hop as

,-The terminal node 110 determines the initial cyclic shift index in the initial cyclic shift index set as

.

In addition to the above PUCCH resource determination, PDSCH PDCCH scheduling provides a time domain allocation (PDSCH-to-HARQ_feedback timing indicator) in DCI. This determines a time slot for the determined PUCCH resource. The PDSCH-to-HARQ-timing-indicator field value is mapped to {1, 2, 3, 4, 5, 6, 7, 8}.

In the 15th version of 3GPP, after conflict resolution, HARQ ACK/NACK feedback is transmitted for Msg4 208 PDSCH, that is, only one terminal node 110 that decodes its contention resolution ID transmits HARQ ACK.

FIG. 4 shows an example of a random access procedure 300 based on a 2-step competition. In addition to the 4-step random access procedure 200, support can also be provided for this.

In the first step, when the terminal node 110 sends an uplink initiation message (MsgA) 302, which is one of the 2-step random access procedures, to the access node 120, the 2-step contention-based random access procedure 300 starts. MsgA can include random selection of the PRACH preamble code through one of the PRACH and PUSCH data transmission through the PUSCH, that is, it can be one or two transmissions, but it is regarded as one step.

Next, in the second step, the access node 120 responds to the uplink initiation message, one of the receiving 2-step random access procedures, by sending a downlink response message (MsgB) 304 from the access node 120 to the terminal node 110 (MsgA) 302.

The random access procedure 200 based on the 2-step competition is different from the random access procedure 200 based on the 4-step competition. The reason is that the response to the random access request realizes the contention resolution without further transmission. Contention resolution provides an uplink grant.

The MsgA 302 is used to detect the signal of the terminal node 110 and provide a Msg3 payload, while the MsgB 304 is used for contention resolution for contention-based random access (CBRA) with a possible payload. The MsgA 302 will at least include the equivalent information sent in the Msg3 for the random access procedure 200 based on the 4-step competition. All triggers used for the random access procedure 200 based on the 4-step competition are also applicable to the random access procedure 300 based on the 2-step competition.

The contention resolution in the step 2 procedure 300 will be performed by including a terminal node identifier 310 (UE identifier) in the first message MsgA 302 returned in the second message MsgB 304. For example, the type of terminal node identifier 310 may be RRC connection setup message/RRC connection reply message/reestablishment request message, which contains the UE ID or the least/most significant number of RRC messages sent to it ( Such as 48 MSB or LSB), or C-RNTI MAC CE. A UE contention can be used to resolve the MAC CE returning the terminal node identifier(s) 310 in the second message MsbG 304.

For the random access procedure 300 based on the 2-step competition, the MsgB 304 may include responses to multiple terminal nodes 110 (similar to the Msg2 204 in the 4-step procedure 200). Whenever multiple terminal nodes 110 transmit the MsgA 302 preamble part on the same or different PRACH resources, the payload on the PUSCH resource may be different. Therefore, the MsgB 304 may include a contention resolution ID (returned terminal node identifier 310) for the multiple terminal nodes 110 that follow in the MsgA 302 transmission.

Since a single MsgB 304 may include the contention resolution ID 310 of several terminal nodes 110, the resources used for the confirmation of all terminal nodes 110 (confirm the HARQ ACK of the contention resolution message MsgB 304) are for each terminal node 110 that sends an acknowledgment. Both should be unique, so that the access node 120 can determine which terminal nodes 110 receive the message MsgB304. For transmission confirmation, a PUCCH resource set is provided, for example, provided by pucch-ResourceCommon or some other information element such as signaling in RMSI. The terminal node 110 may use the PUCCH resource set, or in some examples, from outside the PUCCH resource set but use the PUCCH format, first symbol, duration, PRB offset, and a cyclic shift index set indicated for the PUCCH resource set , Determine the PUCCH resource for confirmation.

In the following example, the terminal node 110 determines the PUCCH resource for HARQ ACK transmission (confirmation 306 carries the PDSCH of MsgB 304). In this situation, the access node 120 does or can target multiple terminal nodes 110 in a single MsgB In 304, multiple contention resolution IDs 310 are transmitted.

The terminal node 110 determines the PUCCH transmission time and resources for HARQ ACK based on the information provided in the DCI schedule MsgB 304 and in the MsgB 304.

The information for identifying PUCCH resources among the terminal nodes 110 is contained in MsgB 304, and can be explicit and/or implicit information, such as the index position of the terminal node identifier 310 (contention resolution ID) that has been returned in MsgB 304 .

In the 2-step procedure 300, the confirmation 306 can be transmitted by multiple terminal nodes 110 using orthogonal resources to confirm the success of individual contention resolution.

To achieve this, in addition to sending an uplink message (MsgA) 302 in a two-step random access procedure 300 and receiving a downlink reply message (MsgB) 304 in the two-step random access procedure 300, The method 300 further includes: sending an uplink confirmation message 306 using a PUCCH resource determined by a PUCCH resource index, where the PUCCH resource index depends on at least a PUCCH resource indicator (PRI) and responding to the message on the downlink (MsgB) An identifier 310 of the device 110 received in 304.

The PUCCH resource indicator (PRI) is received from the downlink control information (DCI) and/or from the downlink response message (MsgB 304). Alternatively/in addition, if the first PUCCH resource indicator (PRI) is provided by DCI and if more resources are needed, for example, in the resource domain, MsgB 304 provides these resources, a hybrid method can be provided.

In some but not necessarily all examples, the terminal node 110 determines the effective PUCCH resource for the transmission confirmation 306 based on the PUCCH resource indicator (PRI) and the index position of the contention resolution ID 310 of the terminal node in the MsgB 304.

The time slot for the transmission confirmation 306 is determined based on the PDSCH-to-HARQ_feedback timing indicator in the received scheduled DCI, or alternatively is provided in the MsgB 304.

In some but not necessarily all examples, the PUCCH resource index depends on at least one of the PUCCH resource indexes applicable to the four-step random access procedure 200 and the identifier 310 of the terminal node 110. The PUCCH resource index applicable to the four-step random access procedure 200 depends on the PUCCH resource indicator (PRI):

In some but not necessarily all examples, the PUCCH resource index depends on the identifier 310 of the terminal node 110, because it depends on one of the indexes of the identifier 310 of the terminal node 110 in the received downlink reply message (MsgB) 304 position.

In some but not necessarily all examples, the PUCCH resource index depends on the identifier 310 of the terminal node 110 because it depends on an offset associated with the identifier 310 of the terminal node 110. The offset is received from the received downlink response message (MsgB) 304 or from the downlink control information (DCI).

In some but not necessarily all examples, the PUCCH resources available for the uplink confirmation message 306 are reserved via the received downlink control information (DCI).

In some but not necessarily all examples, the PUCCH resource index depends on a first index value, the first index value depends on the PUCCH resource indicator (PRI), the PUCCH resource indicator (PRI) depends on the terminal A second value of the identifier 310 of the node 110 is offset.

In some but not necessarily all examples, when the PUCCH resource index exceeds a maximum allowable value, an additional process is performed to determine one of the PUCCH resources for sending the uplink confirmation message 306.

In some but not necessarily all instances, the determined resource is determined by receiving a seed from the received downlink reply message (MsgB) 304, or the determined resource is determined by applying a modulus 16 operation to the PUCCH resource index to make sure.

In some, but not necessarily all, examples, the method 300 includes receiving a downlink response message 304 specifying a new PUCCH resource indicator (PRI) and/or a new time slot for the uplink confirmation message 306.

In some but not necessarily all instances, when the PUCCH resource index exceeds a maximum allowable value, it is reset to a minimum allowable value.

In some but not necessarily all instances, the uplink confirmation message is sent in a time slot determined by receiving an indicator via downlink control information (DCI) or in the received downlink reply message 304 306.

The method 300 can be implemented in various different ways, such as a way that will be better understood from the following examples.

In some but not necessarily all instances, the PUCCH resource index depends on a first index value, the first index value depends on the PUCCH resource indicator (PRI), the PUCCH resource indicator (PRI) depends on the terminal A second value of the identifier 310 of the node 110 is offset.

(藉由PRI及第一CCE之索引來確定)。The first index value depends at least on the PUCCH resource index, which is one of the four-step random access procedures 200, and the identifier 310 of the terminal node 110. The PUCCH resource index applicable to the four-step random access procedure 200 depends on the PUCCH resource indicator (PRI). For example, the index position of the contention resolution ID of the terminal node (for example: #0, #1, #2, etc.) can be added to the PUCCH resource index

(Determined by the index of PRI and the first CCE).

When the PUCCH resource index exceeds a maximum allowable value, an additional process is performed to determine a PUCCH resource for sending the uplink confirmation message 306, such as receiving a new PUCCH resource indicator designated for the uplink confirmation message 306 and/ Or the downlink reply message 304 in a new time slot. In one example, whenever the sum of the PUCCH resource index and the index position of the terminal node reaches the maximum value of the PUCCH resource index (15), the network 100 should use the PUCCH resource indicator and PDSCH- which point to different UL slots. to-HARQ_feedback timing indicator Schedule another MsgB 304. This makes it possible for the network 100 to reserve some PUCCH resources for other downlink transmissions.

The DCI schedule of the MsgB or the MsgB itself may include the same RO (for example, the same RA-RNTI in the same RAR time window), which indicates that there will be another MsgB transmission. If the first detected MsgB 304 does not include the contention resolution ID of the terminal node, this will allow the terminal node 110 to potentially ignore other MsgB 304 for the same RO.

In some but not necessarily all examples, the determined resource is determined by applying a modulus 16 operation to the PUCCH resource index. For example, after exhausting the PUCCH resource index space (reaching 15), the next terminal node 110 starts from PUCCH resource index r _PUCCH =0, and continues until the first PUCCH resource index −1 value is reached.

In some but not necessarily all instances, the PUCCH resource index depends on a first index value, the first index value depends on the PUCCH resource indicator (PRI), the PUCCH resource indicator (PRI) depends on the terminal A second value of the identifier 310 of the node 110 is offset. For example, each index position of the contention resolution ID 310 provides its own resource offset value, and then the resource offset value is used together with the PUCCH resource indicator (PRI) given in the DCI (for example, the resource offset is The shift value is added to the PUCCH resource indicator (PRI) in the PDCCH and a base 16 modulus operation is applied). This approach will provide high flexibility at the expense of increased MsgB 304 payload.

In some but not necessarily all instances, the PUCCH resource index depends on a first index value, the first index value depends on the PUCCH resource indicator (PRI), the PUCCH resource indicator (PRI) depends on the terminal A second value of the identifier 310 of the node 110 is offset. For example, the scheduled DCI has a set mapped to each index position of the contention resolution ID 310, where the bit set is used as a relative value to be applied to the common PUCCH resource indicator in the DCI. For example, there can be 3 sets at most, and 2 bits can be allocated to each set. Therefore, in addition to the first PUCCH resource indicated by the PRI in the scheduled DCI, in order to provide up to three PUCCH resources (and up to three terminal nodes 110), a total of 6 bits will be required in the DCI.

In some but not necessarily all examples, the PUCCH resources available for the uplink confirmation message 306 are reserved via the received downlink control information (DCI). For example, the network 100 configures the maximum value of the PUCCH resource index, and the terminal node 110 that sends HARQ ACK can use the maximum value for the contention resolution message of the terminal node 110; the lower limit for the PUCCH resource index is through the PUCCH resource The indicator and the first CCE of the scheduled DCI to transmit signaling. This makes it possible to reserve PUCCH resources, such as the PUCCH resources indicated by index 3-10 for contention resolution purposes, and other PUCCH resources can be used for any other purpose.

In some but not necessarily all examples, the PUCCH resource index depends on a first index value, the first index value depends on the PUCCH resource indicator (PRI), the PUCCH resource indicator (PRI) depends on the terminal A second value of the identifier 310 of the node 110 is offset.

之一步階大小(由PRI及第一CCE之索引所確定)。舉例而言，DCI指出步階大小等於二，則索引位置為為#1之終端節點110將加上二，並且索引位置為#2之終端節點110將加上四。這將在DCI中需要例如2個位元才能為gNB提供靈活性(步階大小為1、2、3、4)。步階大小也可予以傳送信令作為MsgB 304內容之部分。For example, DCI can also include summing to PUCCH resource index for each index position

A step size (determined by the index of PRI and the first CCE). For example, if the DCI indicates that the step size is equal to two, the terminal node 110 whose index position is #1 will add two, and the terminal node 110 whose index position is #2 will add four. This will require, for example, 2 bits in DCI to provide flexibility for gNB (step sizes of 1, 2, 3, 4). The step size can also be signaled as part of the MsgB 304 content.

In some but not necessarily all instances, the PUCCH resource index depends on a first index value, the first index value depends on the PUCCH resource indicator (PRI), the PUCCH resource indicator (PRI) depends on the terminal A second value of the identifier 310 of the node 110 is offset. When the PUCCH resource index exceeds a maximum allowable value, an additional process is performed to determine one of the PUCCH resources for sending the uplink confirmation message 306. The determined resource is determined by receiving a seed from the received downlink response message (MsgB) 304. For example, once an uplink time slot runs out of PUCCH resources, MsgB 304 can indicate a new “seed” for further contention resolution information included in the same MsgB 304. This may include providing the first CCE index, the first PUCCH resource indicator (PIR) and alternatively a new PDSCH-to-HARQ-timing-indicator or PUCCH used by the terminal node 110 under the index in the MsgB 304 The resource index is offset, and the terminal node 110 uses the above method after that. The PUCCH resource offset r _{offset is} added to the PUCCH resource index r _offset determined by the above method to obtain the actual PUCCH resource index.

In some but not necessarily all examples, the PUCCH resource index depends on a first index value, the first index value depends on the PUCCH resource indicator (PRI), the PUCCH resource indicator (PRI) depends on the terminal A second value of the identifier of the node 110 is offset. When the PUCCH resource index exceeds a maximum allowable value, an additional process is performed to determine one of the PUCCH resources for sending the uplink confirmation message 306. The determined resource is determined by applying a modulus 16 operation to the PUCCH resource index. For example, after the initial PUCCH resource set exhausts the PUCCH resource index space (reaching 15), the next terminal node 110 starts with PUCCH resource index r _PUCCH =16. Next, for each subsequent terminal node 110 indexed in MsgB 304, the PUCCH resource index is incremented by one.

- 終端節點110將第一跳躍中PUCCH傳輸之PRB索引確定為

，並且將第二跳躍中PUCCH傳輸之PRB索引確定為

，其中

係初始循環移位索引集合中初始循環移位索引之總數量 - 終端節點110將初始循環移位索引集合中之初始循環移位索引確定為

如果

- 終端節點110將第一跳躍中PUCCH傳輸之PRB索引確定為

，並且將第二跳躍中PUCCH傳輸之PRB索引確定為

- 終端節點110將初始循環移位索引集合中之初始循環移位索引確定為

When the PUCCH resource index increases beyond the space of the PUCCH resource set, the PRB index needs to be modified to ensure the non-segment use of UL PRB. For example, the PRB index can be determined by the following formula for r _PUCCH > 15: If

-The terminal node 110 determines the PRB index of the PUCCH transmission in the first hop as

, And determine the PRB index of PUCCH transmission in the second hop as

,among them

Is the total number of initial cyclic shift indexes in the initial cyclic shift index set-the terminal node 110 determines the initial cyclic shift index in the initial cyclic shift index set as

in case

-The terminal node 110 determines the PRB index of the PUCCH transmission in the first hop as

, And determine the PRB index of PUCCH transmission in the second hop as

-The terminal node 110 determines the initial cyclic shift index in the initial cyclic shift index set as

FIG. 5A shows an example of a controller 500. A controller 500 can be implemented as a controller circuit system. The controller 500 can be implemented as hardware alone, has certain aspects in software that separately includes firmware, or can be a combination of hardware and software (including firmware).

As shown in FIG. 5A, the controller 500 can be implemented using instructions that enable hardware functions. For example, by using a general-purpose or special-purpose processor 502 that can be stored in a computer-readable storage medium (disk, The memory, etc.) are implemented by the executable instructions of a computer program 506 executed by the processor 502.

The processor 502 is configured to read from and write to the memory 504. The processor 502 may also include an output interface through which data and/or commands are output by the processor 502, and an input interface through which data and/or commands are input to the processor 502.

The memory 504 stores a computer program 506 including computer program instructions (computer program code). When loaded into the processor 502, the computer program 506 controls the operations of the devices 110 and 120. The computer program instructions of the computer program 506 provide logic and routines that enable the device to perform the methods shown in FIGS. 3 and 4. The processor 502 can load and execute the computer program 506 by reading the memory 504.

Therefore, the device 110 includes: At least one processor 502; and At least one memory 504, which includes computer code At least one memory 504 and the computer program code are configured to cooperate with at least one processor 502 to make the device 110 perform at least the following steps: Send an uplink message (MsgA) in a two-step random access procedure; Receive a downlink response message (MsgB) in the two-step random access procedure, the received MsgB includes an identifier for the device; and An uplink confirmation message is sent using a PUCCH resource determined by a PUCCH resource index, where the PUCCH resource index depends at least on a PUCCH resource indicator (PRI) and the identifier of the device.

Therefore, the device 110 includes: At least one processor 502; and At least one memory 504, which includes computer code At least one memory 504 and the computer program code are configured to cooperate with at least one processor 502 to make the device 110 perform at least the following steps: After a two-step random access procedure, a PUCCH resource determined by a PUCCH resource index is used to send an uplink confirmation message, wherein the PUCCH resource index depends on at least a PUCCH resource indicator (PRI) and the The identifier of the device.

As shown in FIG. 5B, the computer program 506 can reach the devices 110, 120 via any suitable delivery mechanism 510. For example, the delivery mechanism 510 may be a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, such as a compact disc-readable memory (CD -ROM) or a digital diversified disc (DVD) or a solid-state storage, a memory medium, a product that contains or tangibly realizes a computer program 506. The delivery mechanism may be configured to reliably deliver a signal of the computer program 506. The devices 110, 120 can broadcast or transmit the computer program 506 as a computer data signal.

A computer program instruction used to make a device 110 perform at least the following steps or perform at least the following steps: Send an uplink message (MsgA) in a two-step random access procedure; Receive a downlink response message (MsgB) in the two-step random access procedure, the received MsgB includes an identifier for the device; and An uplink confirmation message is sent using a PUCCH resource determined by a PUCCH resource index, where the PUCCH resource index depends at least on a PUCCH resource indicator (PRI) and the identifier of the device.

The computer program instructions can be included in a computer program, a non-transitory computer readable medium, a computer program product, and a machine readable medium. In some but not necessarily all instances, the computer program instructions may be distributed in more than one computer program.

Although the memory 504 is shown as a single component/circuit system, it can still be implemented as one or more, some or all of which can be integrated/removable and/or can provide permanent/semi-permanent/dynamic/cache storage The individual components/circuit systems.

Although the processor 502 is shown as a single component/circuit system, it can still be implemented as one or more individual components/circuits, some or all of which can be integrated/removable. The processor 502 may be a single-core or multi-core processor.

References to “computer-readable storage media”, “computer program products”, “computer programs tangibly realized”, etc., or a “controller”, “computer”, “processor”, etc. should be understood as not only Including computers with different architectures such as single/multi-processor architecture and sequential (Von Neumann)/parallel architecture. It also includes computers such as field programmable gate array (FPGA), application-specific circuit (ASIC), signal processing Dedicated circuits such as devices and other processing circuit systems. References to computer programs, instructions, codes, etc. should be understood to include software for a programmable processor or firmware, such as the programmable content of a hardware device, or instructions for a processor, Or used for the configuration settings of a fixed function device, gate array or programmable logic device.

When used in this application, "circuit system" can mean one or more or all of the following: (a) The implementation of hardware-only circuit systems (such as the implementation of analog-only and/or digital circuit systems), and (b) The combination of hardware circuit and software, such as (if applicable): (i) The combination of (various) analog and/or digital hardware circuits and software/firmware, and (ii) Any part of hardware processor(s) (including digital signal processor(s)), software, and memory(s) with software, which work together to make a device such as a mobile phone or server Perform various functions, and (c) Hardware circuit(s) and/or processor(s) such as a microprocessor(s) or part of a microprocessor(s) that require software (such as firmware) to operate, but the software is in It does not exist when it can be operated without it.

The definition of "circuit system" applies to all uses of the term in this application, including all uses of the term in any claim in the scope of the patent application. To give a further example, when the term circuit system is used in this application, it also covers only one hardware circuit or processor, and its accompanying software and/or firmware. The term circuit system, for example, and if applicable to a specific demand component, also covers a baseband integrated circuit used in a mobile device, or a server, a cellular network device, or other computing or network devices One of them is similar to an integrated circuit.

The stages shown in FIG. 4 may represent steps in a code section in a method and/or computer program 506. The illustration of a specific order of the blocks does not necessarily imply that the blocks have a required or preferred order, and the order and arrangement structure of the blocks can be changed. Furthermore, it is possible to omit some blocks.

If a structural feature has been described, it can be replaced with a component for performing one or more functions of the structural feature, regardless of whether the function or those functions are described explicitly or implicitly.

From the foregoing, it will be understood that, in some instances, a system is provided that includes: A device containing components used to: Send an uplink message (MsgA) in a two-step random access procedure; Receive a downlink response message (MsgB) in the two-step random access procedure, the received MsgB contains an identifier for the device; and Sending an uplink confirmation message using a PUCCH resource determined by a PUCCH resource index, where the PUCCH resource index depends at least on a PUCCH resource indicator (PRI) and the identifier of the device; and An access node that contains a component used to: Receive the uplink message (MsgA) in the two-step random access procedure; Send the downlink reply message (MsgB) in the two-step random access procedure, and the received MsgB includes the identifier for the device; and Receive the upstream confirmation message.

In some but not necessarily all instances, the device 110 is configured to transfer data from the device 110 with or without storing the data locally in a memory 504 at the device 110, and with or without using Circuit system or processor to process the data locally.

Data can be stored remotely in processed or unprocessed formats on one or more devices. Data can be stored in the cloud.

Data can be processed remotely at one or more devices. Data can be partially processed locally and partially remotely processed at one or more devices.

Data can be transmitted wirelessly to remote devices via short-range radio communications such as Wi-Fi or Bluetooth, for example, or through long-range cellular radio links. The device may include a communication interface, such as a radio transceiver for data communication.

The device 110 may be part of the Internet of Things that forms part of a larger distributed network.

Whether it is local or remote, data can be processed for health monitoring, data collection, patient monitoring, vital signs monitoring, or other purposes.

Whether it is local or remote, data processing can involve artificial intelligence or machine learning algorithms. For example, the data can be used as a learning input for training a machine learning network, or can be used as a query input for a machine learning network, which provides a response. For example, the machine learning network can use linear regression, mathematical logistic regression, vector support machine, or an acyclic machine learning network, such as a single or multiple hidden layer neural network.

Whether it is local or remote, data processing can produce an output. The output can be transmitted to the device 110, which can generate an output such as an audio output, visual output, or tactile output that can be sensed by the subject.

The above examples found applications that enable the following components: Automotive systems; telecommunications systems; electronic systems including consumer electronics; distributed computing systems; used to generate or present audio, visual, and audiovisual content and hybrid, relay, virtual, and/or augmented reality Media systems for media content; personal systems including personal health systems or personal fitness systems; navigation systems; user interfaces also known as human-machine interfaces; including cellular, non-cellular, and optical networks Network; Prompt operation network; Internet; Internet of Things; virtualized network; and related software and services.

The word "contains" is used in this document in a compatible meaning rather than an exclusive meaning. That is, any reference to X containing Y indicates that X may contain only one Y or may contain more than one Y. If it is intended to use "including" which has an exclusive meaning, it will be explained clearly in the context by meaning "including only one" or by using "consisting of".

In this description, various examples have been referred to. The description of features or functions related to an example indicates that those features or functions exist in the example. Regardless of whether there is a clear statement, the use of the word "example" or "for example" or "may" or "may" in the text means that at least such features or functions exist in the example, whether or not it is described as an example, It also means that these features or functions can, but do not necessarily exist in some or all other instances. Therefore, "example", "for example," "may" or "may" mean a specific example in a class of examples. An attribute of the example may be only an attribute of the example, or an attribute of the category, or an attribute of a subcategory of the category, which includes some but not all examples of the category. Therefore, it is implicitly disclosed that a feature described with reference to one example rather than another example can be used as part of an operating combination in the other example if possible, but it does not necessarily have to be used in the other example .

Although the embodiments have been described with reference to various examples in the preceding paragraphs, it should be understood that the examples given can still be modified without departing from the scope of the patent application.

The features described in the previous description can be used in combinations other than those specifically described above.

Although functions have been described with reference to certain features, those functions can still be performed by other features, regardless of whether they are described or not.

Although the features have been described with reference to certain embodiments, those features can still exist in other embodiments, regardless of whether they are described or not.

The term "一" or "the" is used in this document with a compatible meaning rather than an exclusive meaning. That is, any reference to X that contains one/the Y indicates that X may contain only one Y or may contain more than one Y, unless the context clearly indicates the contrary proposition. If you intend to use "one" or "the" with an exclusive meaning, it will be explained clearly in the context. In some cases, the use of "at least one" or "one or more" can be used to emphasize a compatible meaning, but the absence of these terms should not be used for inference and exclusive meaning.

The existence of a feature (or feature combination) in a claim is a reference to the feature or (feature combination) itself, and is also a reference to a feature (equivalent feature) that achieves substantially the same technical effect. Equivalent features include, for example, features that are variants and achieve substantially the same results in substantially the same way. For example, equivalent features include features that perform substantially the same function in substantially the same manner to achieve substantially the same result.

In this description, various examples have used adjectives or adjective words to illustrate the characteristics of these examples for reference. This description of a characteristic related to an example indicates that the characteristic exists in some examples that are indeed as described, and exists in other examples whose substance is as described.

Although I have tried my best to point out those features that are believed to be important in the foregoing specification, it should be understood that the applicant in this case can still address any patentable features or combinations of features referred to and/or shown in the drawings. , Seek protection through the scope of patent application, regardless of whether the feature or combination of features has been emphasized.

100: Internet 110: terminal node 120: Access node 122: Cellular 124: wireless interface 126: X2 interface 128: S1 interface 129: Core Node 130: idle mode 131,133: Transformation 132: connected mode 200: 4-step competition-based random access procedure 202,302: Uplink initiation message 204, 208: Downlink response 206: Uplink connection request 300: 2-step competition-based random access procedure 304: Downlink reply message 306: confirmation 310: Identifier 500: Controller 502: processor 504: Memory 506: computer program 510: delivery mechanism

Some exemplary embodiments will now be described with reference to the drawings, in which: Figure 1 shows an exemplary embodiment of the subject matter described herein; Figure 2 shows another exemplary embodiment of the subject matter described herein; Figure 3 shows another exemplary embodiment of the subject matter described herein; Figure 4 shows another exemplary embodiment of the subject matter described herein; Figure 5A shows another exemplary embodiment of the subject matter described herein; Figure 5B shows another exemplary embodiment of the subject matter described herein;

110: terminal node

120: Access node

300: 2-step competition-based random access procedure

302: Uplink initiation message

304: Downlink reply message

306: confirmation

310: Identifier

Claims (15)

A device containing components used to: Send an uplink message in a two-step random access procedure; Receive a downlink response message in the two-step random access procedure, and the received downlink response message includes an identifier for the device; and An uplink confirmation message is sent using a PUCCH resource determined by a PUCCH resource index, where the PUCCH resource index depends at least on a PUCCH resource indicator and the identifier of the device. Such as the equipment of request 1, wherein the PUCCH resource indicator (PRI) is received from downlink control information (DCI) and/or from the downlink response message (MsgB). For example, the device of request item 1 or 2, wherein the PUCCH resource index depends on at least one of the PUCCH resource indexes applicable to four-step random access and the identifier of the device, which is applicable to the PUCCH resource of four-step random access The index system depends on the PUCCH resource indicator. The device of any one of the aforementioned request items, wherein the PUCCH resource index depends on the identifier of the device, because it depends on an index of the identifier of the device in the received downlink reply message position. Such as the device of any one of claims 1 to 3, wherein the PUCCH resource index depends on the identifier of the device because it depends on an offset associated with the identifier of the device. Such as the device of claim 5, wherein the offset is received from the received downlink response message or from downlink control information (DCI). A device as in any one of the aforementioned request items, wherein the PUCCH resources available for the uplink confirmation message are indicated by the received downlink control information (DCI). A device as in any one of the foregoing requests, wherein the PUCCH resource index depends on a first index value, the first index value depends on the PUCCH resource indicator (PRI), the PUCCH resource indicator (PRI) It is offset by a second value that depends on the identifier of the device. For example, the device of claim 8, which includes means for performing an additional process when the PUCCH resource index exceeds a maximum allowable value to determine a PUCCH resource for sending the uplink confirmation message. Such as the device of claim 9, wherein the determined resource is determined from receiving a seed in the received downlink reply message, or The determined resource is determined by applying a modulo operation to the PUCCH resource index. Such as the device of any one of the aforementioned request items, which includes a member for receiving a downlink response message that specifies a new PUCCH resource indicator and/or uplink confirmation message A new time slot. A device as in any one of the foregoing requirements, wherein when the PUCCH resource index exceeds a maximum allowable value, it is reset to a minimum allowable value. The device of any one of the foregoing request items, wherein the uplink is sent in a time slot determined by receiving an indicator via downlink control information or in the received downlink reply message Confirm message. A computer program instruction used to cause a device to perform at least the following steps or to perform at least the following steps: Send an uplink message in a two-step random access procedure; Receive a downlink response message in the two-step random access procedure, and the received downlink response message includes an identifier for the device; and An uplink confirmation message is sent using a PUCCH resource determined by a PUCCH resource index, where the PUCCH resource index depends on at least a PUCCH resource indicator and the identifier of the device. A method that includes: Send an uplink message in a two-step random access procedure; Receive a downlink response message in the two-step random access procedure, and the received downlink response message includes an identifier for the device; and An uplink confirmation message is sent using a PUCCH resource determined by a PUCCH resource index, where the PUCCH resource index depends at least on a PUCCH resource indicator and the identifier of the device.

Images