Determining contention solutions

Abstract

Embodiments of the present disclosure relate to determining a contention solution. In an aspect, a terminal device, as part of a random access (RA) procedure, and after a message 3 (Msg3) transmission or a message A (MSGA) transmission, receives a physical downlink control channel (PDCCH) transmission in a serving cell, where the PDCCH transmission is addressed to an identifier of the terminal device and includes an uplink (UL) grant for a new transmission, where the uplink (UL) grant is not addressed to the terminal device. And the serving cell is configured with a plurality of timing advance groups (TAGs). The terminal device determines the RA procedure or a contention solution of the RA procedure as successful or unsuccessful based on an association between the UL grant and a TAG among the plurality of TAGs. Embodiments of the present disclosure may allow a contention solution to be determined without knowing which TAG or transmission and reception point (TRP) a physical random access channel (PRACH) preamble transmission applies to.

Description

Technical Field

[0001] Various example embodiments generally relate to the field of communications, and more specifically to terminal devices, methods, apparatuses, and computer-readable storage media for determining contention solutions. Background Technology

[0002] In New Radio (NR) systems, the concept and function of NR Timing Advance (TA) are essentially the same as those of Long Term Evolution (LTE) Timing Advance. In short, TA is a special command (e.g., notification) from network equipment to terminal equipment that enables the terminal equipment to adjust its uplink transmission. This type of uplink adjustment can be applied to the Physical Uplink Shared Channel (PUSCH), Physical Downlink Control Channel (PDCCH), Sounding Reference Signal (SRS), etc.

[0003] In 3GPP Release 18, support for dual TA enhancements to uplink (UL) multiple downlink control information (DCI) for multiple transmit and receive points (TRP) operations was agreed upon. However, solutions for multiple TAs require further investigation. Summary of the Invention

[0004] In general, exemplary embodiments of this disclosure provide terminal devices, methods, apparatuses, and computer-readable storage media for determining contention solutions. For example, the solutions provided by exemplary embodiments of this disclosure can allow contention solutions to be determined without knowing which timing advance group (TAG) or TRP the Physical Random Access Channel (PRACH) preamble transmission is applied to.

[0005] In a first aspect, a terminal device is provided. The terminal device may include at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: receive a PDCCH transmission in a serving cell as part of a random access (RA) procedure and after a message 3 (Msg3) transmission or a message A (MSGA) transmission, wherein the PDCCH transmission is addressed to an identifier of the terminal device and contains a UL grant for the transmission, and the serving cell is configured with a plurality of TAGs; and determine the RA procedure or a contention resolution of the RA procedure as successful based on the association between the UL grant and a TAG among the plurality of TAGs.

[0006] In a second aspect, a terminal device is provided. The terminal device may include at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: receive a PDCCH transmission in a serving cell as part of a random access (RA) procedure and after a Msg3 or MSGA transmission, wherein the PDCCH transmission is addressed to an identifier of the terminal device, the serving cell is configured with multiple TAGs, and a time alignment timer (TAT) among multiple TATs for the multiple TAGs is not running; and determine the RA procedure or a contention resolution of the RA procedure as successful based on (i) the successful decoding of a received transport block (TB) and (ii) the Media Access Control (MAC) Protocol Data Unit (PDU) corresponding to the TB containing a predetermined MAC control element (CE).

[0007] In a third aspect, a method is provided. The method may include: as part of a random access (RA) procedure and after a Msg3 or MSGA transmission, at the terminal device, receiving a PDCCH transmission from a network device in the serving cell, wherein the PDCCH transmission is addressed to an identifier of the terminal device, does not contain a UL grant for the new transmission, and the serving cell is configured with multiple TAGs; and at the terminal device, determining whether the RA procedure or a contention resolution of the RA procedure is successful or unsuccessful based on the association between the UL grant and one of the multiple TAGs.

[0008] In a fourth aspect, a method is provided. The method may include: as part of a random access (RA) procedure and after a Msg3 or MSGA transmission, at the terminal device, receiving a PDCCH transmission from a network device in a serving cell, wherein the PDCCH transmission is addressed to an identifier of the terminal device, the serving cell is configured with multiple TAGs, and one of the multiple TATs for the multiple TAGs is not in operation; and at the terminal device, determining the RA procedure or a contention resolution of the RA procedure as successful based on (i) the received TB being successfully decoded and (ii) the Media Access Control (MAC) PDU corresponding to the TB containing a predetermined MAC CE.

[0009] In a fifth aspect, an apparatus is provided. The apparatus may include: a component for receiving, as part of a random access (RA) procedure and after a Msg3 or MSGA transmission, a PDCCH transmission in a serving cell at a terminal device, wherein the PDCCH transmission is addressed to an identifier of the terminal device and contains a UL authorization for the new transmission, and the serving cell is configured with a plurality of TAGs; and a component for determining whether the RA procedure or a contention resolution of the RA procedure is successful or unsuccessful based on the association between the UL authorization and the TAGs among the plurality of TAGs.

[0010] In a sixth aspect, an apparatus is provided. The apparatus may include: components for receiving, as part of a random access (RA) procedure and after a Msg3 or MSGA transmission, a PDCCH transmission in a serving cell at a terminal device, wherein the PDCCH transmission is addressed to an identifier of the terminal device, the serving cell is configured with multiple TAGs, and one of the multiple TATs for the multiple TAGs is not operational; and components for determining the RA procedure or a contention resolution of the RA procedure as successful based on (i) the successful decoding of a received TB and (ii) the media access control (MAC) PDU corresponding to the TB containing a predetermined MAC CE.

[0011] In a seventh aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing a device to perform at least the method according to a third or fourth aspect.

[0012] In an eighth aspect, a computer program including instructions, when executed by a device, causes the device to at least: receive a PDCCH transmission in a serving cell as part of a random access (RA) procedure and after a Msg3 or MSGA transmission, wherein the PDCCH transmission is addressed to an identifier of a terminal device and contains a UL authorization for the new transmission, and the serving cell is configured with a plurality of TAGs; and determine the RA procedure or a contention resolution of the RA procedure as successful or unsuccessful based on the association between the UL authorization and a TAG among the plurality of TAGs.

[0013] In a ninth aspect, a computer program including instructions is provided that, when executed by an apparatus, causes the apparatus to at least: receive a PDCCH transmission in a serving cell as part of a random access (RA) procedure and after a Msg3 or MSGA transmission, wherein the PDCCH transmission is addressed to an identifier of a terminal device, the serving cell is configured with a plurality of TAGs, and one of the plurality of TATs for the plurality of TAGs is not in operation; and determine the RA procedure or a contention resolution of the RA procedure as successful based on (i) the received TB being successfully decoded and (ii) the MAC PDU corresponding to the TB containing a predetermined MAC CE.

[0014] In a tenth aspect, a terminal device is provided. The terminal device may include a receiving circuit system configured to receive a PDCCH transmission in a serving cell as part of a random access (RA) procedure and after a Msg3 or MSGA transmission, wherein the PDCCH transmission is addressed to an identifier of the terminal device and contains a UL grant for the new transmission, and the serving cell is configured with a plurality of TAGs; and a determining circuit system configured to determine whether the RA procedure or a contention resolution of the RA procedure is successful or unsuccessful based on the association between the UL grant and a TAG among the plurality of TAGs.

[0015] In an eleventh aspect, a terminal device is provided. The terminal device may include a receiving circuit system configured to receive a PDCCH transmission in a serving cell as part of a random access (RA) procedure and after a Msg3 or MSGA transmission, wherein the PDCCH transmission is addressed to an identifier of the terminal device, the serving cell is configured with multiple TAGs, and one of the multiple TATs for the multiple TAGs is not running; and a determining transmission circuit system configured to determine the RA procedure or the contention resolution of the RA procedure as successful based on (i) the received TB being successfully decoded and (ii) the MAC PDU corresponding to the TB containing a predetermined MAC CE.

[0016] It should be understood that the overview section is not intended to represent key or essential features of the embodiments of this disclosure, nor is it intended to be used to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0017] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:

[0018] Figure 1 The illustration shows an example network environment in which embodiments of the present disclosure can be implemented;

[0019] Figure 2 The illustration shows an example signaling process for determining a contention solution according to some example embodiments of the present disclosure;

[0020] Figure 3 The illustration shows another example signaling process for determining a contention solution according to some example embodiments of the present disclosure;

[0021] Figure 4 The illustration shows an example flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure;

[0022] Figure 5The illustration shows an example flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure;

[0023] Figure 6 The illustration shows an example simplified block diagram of a device suitable for implementing embodiments of the present disclosure; and

[0024] Figure 7 An example block diagram of an example computer-readable medium according to some embodiments of the present disclosure is illustrated.

[0025] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0026] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure.

[0027] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0028] The embodiments described in this disclosure using references to "an embodiment," "an embodiment," "an example embodiment," etc., may include specific features, structures, or characteristics, but not every embodiment necessarily includes a specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, it is within the knowledge of those skilled in the art to consider that in conjunction with other embodiments (whether clearly and explicitly described) it may affect that feature, structure, or characteristic.

[0029] It is understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0030] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising,” “including,” “having,” “having,” “including,” and / or “containing” are used herein, the presence of the stated features, elements, and / or components, etc., is specified, but the presence or addition of one or more other features, elements, components, and / or combinations thereof is not excluded. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements is connected by “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0031] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Pure hardware circuit implementation (such as implementations only in analog and / or digital circuit systems) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits having software / firmware, and (ii) Any part of a hardware processor (including digital signal processors), software, and memory (including multiple memory) having software, which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required.

[0032] This definition of circuit system applies to all use of the term in this application (including in any claim). As another example, as used in this application, the term circuit system also covers only hardware circuitry or processors (or processors) or portions thereof and their accompanying software and / or firmware implementations. For example, and if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0033] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in the communication network can be performed according to any suitable generation communication protocol, including but not limited to third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols and / or later generation communication protocols. Embodiments of this disclosure can be applied to various communication systems. Due to the rapid development in communications, there will naturally be future types of communication technologies and systems that can be implemented using this disclosure. This should not be construed as limiting the scope of this disclosure to only the systems described above.

[0034] As used herein, the term "network device" can refer to a node in a communication network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header (RRH), a relay, or a low-power node such as a femtosecond or picosecond.

[0035] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), mobile subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing link environments), consumer electronic devices, commercially operating equipment, relay nodes, integrated access and backhaul (IAB) nodes, and / or industrial wireless networks, etc. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0036] As used herein, the term "TRP" refers to a transmit-receive point located on the network side at a specific geographical location, having an antenna array (having one or more antenna elements) that can be used to transmit and receive signals to / from terminal devices. In embodiments of this disclosure, a TRP may refer to a macrocell, microcell, RRH, relay, femtonode, piconet, etc. Although some embodiments of this disclosure are described with reference to, for example, two TRPs, these embodiments are for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. It will be understood that this disclosure described herein can be implemented in various ways other than those described below.

[0037] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink (UL) resource,” or “downlink (DL) resource” can mean any resource used to perform communication (e.g., communication between a terminal device and a network device), such as resources in the time domain, resources in the frequency domain, resources in the spatial domain, resources in the code domain, resources in a combination of more than one domain, or any other resource that enables communication. In the following, resources in the time domain (such as subframes) will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. It will be noted that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0038] As discussed above, a TA (Transmission Target) is a special command (e.g., notification) from the network to the terminal device that enables the terminal device to adjust its uplink transmission.

[0039] The TA can be delivered to the terminal device via RAR or MAC CE. A TA loop can be used to maintain the TA to ensure alignment of the UL signals (transmitted from the terminal device) at the network node within a certain time resolution. During random access, the terminal device can receive an initial TA value (e.g., an absolute TA value) in a RAR message. The TA value can then be updated using a MAC CE containing a TAC indicating the relative TA value. Alternatively, the UE can proactively update the TA by actively requesting the updated TA value. These operations for maintaining the TA are referred to as a TA loop. Typically, a TA loop can correspond to a UL transmission toward a given TRP. Furthermore, a TA loop may also correspond to one maintained within a TAG. Therefore, one TA loop can correspond to one TA, and the number of TA loops can indicate the number of TAs used. Thus, in the current embodiment, a TA loop can implicitly refer to a TA.

[0040] The Timing Advance Group (TAG) used in this document refers to a group of one or more serving cells that share the same uplink TA and the same downlink timing reference cell. Each TAG contains at least one serving cell with a configured uplink, and the mapping from each serving cell to the TAG is configured by RRC signals. In 3GPP Release 18, support for two TAs for UL multi-DCI used for multi-TRP operations in NR systems has been agreed upon. Furthermore, support for dual TA enhancements has been agreed upon for both intra-cell and inter-cell multi-DCI multi-TRP scenarios in 3GPP Release 18.

[0041] Release 18 work items for further new radio (NR) mobility enhancements are underway in 3GPP, and multiple (two) timing advance values ​​for UEs within the serving cell will be further discussed, for example, in NRMIMO Evolution WID (RP-223276), as shown in Table 1. Table 1

[0042] In addition, MAC TS 38.321 specifies the following contention resolution / successful RA process completion in RRC_CONNECTED mode for 4-step RA and 2-step RA respectively, as shown in Table 2. Table 2

[0043] In a multi-TRP scenario, a UE can have two TAGs for the serving cell (such as a special cell (SpCell, i.e., primary cell PCell or primary / secondary cell PSCell)). These TAGs will naturally use different TATs, allowing the network to provide separate timing adjustment commands using, for example, TAC MAC CE. Therefore, the TAT can be started or restarted at different times for these two TAGs.

[0044] Typically, in a multi-TRP scenario within a serving cell, a subset of the SSBs in the cell will be transmitted by one TRP, and another subset of the SSBs will be transmitted by another TRP. During the UE's random access procedure, it selects one of these SSBs and can therefore send a PRACH preamble to any of the TRPs.

[0045] Therefore, when SpCell is configured with two TAGs, one of the TATs associated with these TAGs may not be running or may have expired. Contention-based random access (CBRA) procedures can be triggered at any time for various reasons at the UE. For example, this could be due to a scheduling request (SR) when SR resources are not configured, the number of SR transmissions reaching a configured threshold, beam fault recovery (BFR), or continuous listen-before-speak (LBT) fault monitoring. In this case, it is unclear how the UE should determine that the contention resolution is successful and complete the random access procedure.

[0046] This disclosure provides example embodiments of a solution for determining a contention resolution. According to embodiments of this disclosure, a terminal device, as part of an RA (Relationship Assist) procedure and after a Msg3 or MSGA transmission, receives a PDCCH transmission in the serving cell, wherein the PDCCH transmission is addressed to an identifier of the terminal device and contains a UL (Universal License) grant for the new transmission, and the serving cell is configured with multiple TAGs. The terminal device determines whether the RA procedure or the contention resolution of the RA procedure is successful or unsuccessful based on the association between the UL grant and one of the multiple TAGs. It should be understood that the above process steps may work together, partially work together, or work independently of each other in the operational flow described in the following section.

[0047] The example embodiments provided in this disclosure for determining the RA process or a contention solution for the RA process can allow the contention solution to be determined without knowing which TAG or TRP the PRACH preamble transmission applies to. The principles of this disclosure and some example embodiments will now be described in detail with reference to the accompanying drawings.

[0048] For illustrative purposes, references will be made below. Figures 1-7 The present disclosure describes the principles and exemplary embodiments for determining resource blocks for transmission. However, it will be noted that these embodiments are given to enable those skilled in the art to understand the inventive concepts of the present disclosure and to implement the solutions presented herein, and are not intended to limit the scope of the disclosure in any way.

[0049] Figure 1 Examples of communication networks 100 that can be implemented according to some embodiments of this disclosure are illustrated. Figure 1 As illustrated, the communication network 100 includes a terminal device (also referred to as a user equipment or UE) 102 and two network devices (also referred to as gNB, BS, or TRP), such as network devices 104-1 and 104-2 (which may also be collectively referred to as "network device 104"). Although the terminal device 102 and the two network devices 104 are... Figure 1 As shown, the number of network devices and terminal devices is not limited. In other words, there are one or more network devices 104 and one or more terminal devices 102 in the communication network 100.

[0050] Network device 104 can provide services to terminal device 102, and network device 104 and terminal device 102 can communicate data and control information with each other. In some example embodiments, network device 104 and terminal device 102 can communicate via a direct link / channel.

[0051] In communication system 100, the link from network device 104 to terminal device 102 is referred to as the downlink (DL), while the link from terminal device 102 to network device 104 is referred to as the uplink (UL). In the downlink, network device 104 is a transmitting (TX) device (or transmitter), and terminal device 102 is a receiving (RX) device (or receiver). In the uplink, terminal device 102 is a transmitting (TX) device (or transmitter), and network device 104 is an RX device (or receiver). It should be understood that network device 104 can provide one or more serving cells. Figure 1 As illustrated, network device 104 together provides service cell 106, and terminal device 102 resides on service cell 106. In some embodiments, network device 104 may provide multiple service cells, and terminal device 102 may hand over from a source cell to a target cell among service cells during its mobility. It should be understood that... Figure 1 The number of serving cells shown is for illustrative purposes and does not imply any limitation.

[0052] Communication in network environment 100 may be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as fourth-generation (4G) and fifth-generation (5G), wireless local communication protocols such as IEEE 802.11, and / or any other protocol currently known or to be developed in the future. Furthermore, communication may utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other technology currently known or to be developed in the future.

[0053] In some embodiments, the serving cell 106 may include a primary or secondary cell having multiple network devices 104 (such as TRPs). Network devices 104 may transmit different PDSCHs, but the control signals (PDCCH / DCI) for the two PDSCHs are transmitted by one of the network devices 104. In some embodiments, network devices 104 may transmit two different PDSCHs, and each network device 104 transmits its own corresponding PDCCH / DCI. In some embodiments, network devices may jointly transmit DL signals and receive UL signals.

[0054] As described above, terminal device 102 may have two TAGs for serving cell 106, and employ different TATs, allowing one or more network devices to provide individual TACs. Terminal device 102 can determine that one of the TAGs is the primary TAG and the others are secondary TAGs. Upon the expiration of one or more TATs, terminal device 102 may retain one of the primary and secondary TAGs. Network device 104 providing the TAC also knows that the TAT has expired. It knows which TAG is retained at terminal device 102 and can act accordingly.

[0055] It should be understood that Figure 1 The number of devices, their connections, and types shown are for illustrative purposes and do not imply any limitation. Communication system 100 may include any suitable number of devices suitable for implementing embodiments of this disclosure.

[0056] refer to Figure 2 The illustration depicts an example signaling process 200 for determining a contention resolution according to some example embodiments of the present disclosure. As shown, after terminal device 102 sends a Msg3 or MSGA transmission to network device 104, terminal device 102 receives (204) a PDCCH transmission (206) in the serving cell. The PDCCH transmission (206) is addressed to the identifier of terminal device 102 and contains a UL authorization for the new transmission. The serving cell may be configured with multiple TAGs. In some example embodiments, network device 104 may send (202) the PDCCH transmission (206) to terminal device 102.

[0057] As an example, SpCell can be configured with two TAGs, and the CBRA process is triggered at terminal device 102. For contention resolution and / or RA process completion after the MSGA transmission for step 2 RA or after the MSG3 transmission, if terminal device 102 is not shown which TAG the TAC provided in the RAR or rollback RAR applies to, then terminal device 102 can execute determination block 208. For example, the terminal device may not know, or may not be made known by network device 104, which TAG the TAC provided in the RAR within the rollback RAR applies to.

[0058] Terminal device 102 determines (208) whether the contention resolution and / or RA process is successful or unsuccessful based on the association between the UL authorization and a TAG among a plurality of TAGs. In some example embodiments, if one of the plurality of TATs associated with SpCell is not running or has expired, and another of the plurality of TATs associated with SpCell is running, then when terminal device 102 receives a PDCCH transmission addressed to C-RNTI, terminal device 102 may consider the contention resolution successful and / or the RA process successfully completed, wherein the PDCCH transmission contains the UL authorization for the new transmission, and the UL authorization is associated with a TAG for which the TAT is running. For example, the plurality of TATs associated with SpCell are associated with a plurality of TAGs associated with the plurality of SpCells. For example, the plurality of TATs may be associated with SpCell by means of a plurality of TAGs configured for SpCell. For example, each of the plurality of TATs may be associated with a plurality of TAGs associated with / configured for SpCell.

[0059] In some example embodiments, if one of the multiple TATs associated with SpCell is not running or has expired, and another of the multiple TATs associated with SpCell is running, then when terminal device 102 receives a PDCCH transmission addressed to C-RNTI, terminal device 102 can consider the RA process to have completed successfully. This PDCCH transmission contains a UL authorization for the new transmission, and the UL authorization is associated with a TAG for which the TAT is running. For example, when the RA process is considered to have completed successfully, the contention resolution can be considered successful.

[0060] In some example embodiments, terminal device 102 can determine the association between UL authorization and a TAG for a CORESET based on the scheduled UL authorization. For example, the TAG is associated with a TAG configured for the CORESET. CORESETpoolIndex The value is associated, and the UL channel can be configured to be associated with... CORESETpoolIndex Related.

[0061] In some example embodiments, terminal device 102 may determine the association between UL authorization and TAG based on the indicated TCI status of the UL authorization. For example, the indicated TCI status may be a (uniform) joint DL / UL TCI status or a (uniform) UL TCI status, or the TCI status ID itself, or (multiple) SRS resources used as a reference for uplink transmission.

[0062] In some example embodiments, terminal device 102 may determine the association between UL authorization and a TAG based on a TAG ID, which is associated with a TCI status indicated or configured for UL transmissions scheduled by UL authorization.

[0063] In some example embodiments, terminal device 102 may determine the association between UL authorization and TAG based on TAG ID corresponding to PCI (Physical Cell ID) associated with DL RS, wherein DL RS is included in the TCI state indicated or configured for UL transmissions scheduled by UL authorization. In some example embodiments, terminal device 102 may determine the association between UL authorization and TAG based on indications in UL authorization.

[0064] In some example embodiments, if one of the multiple TATs associated with SpCell is not running or has expired, and another of the multiple TATs associated with SpCell is running, then when terminal device 102 receives a PDCCH transmission addressed to C-RNTI, terminal device 102 can store the N of the TAG. TA The application is UL timing, where the PDCCH transmission includes UL authorization for the new transmission and the UL authorization is associated with a TAG for which TAT is not running. Terminal device 102 can initiate the TAT associated with the TAG. Terminal device 102 can assume that the contention resolution was successful and / or the RA process was successfully completed.

[0065] In some example embodiments, network device 104 may instruct terminal device 102 whether N can be sent within a DCI that is scheduled to be authorized by UL. TA This applies to TAGs with non-running TATs. In some example embodiments, if network device 104 does not provide such an indication, terminal device 102 may assume that the RA process has not been successfully completed.

[0066] Figure 3 Another example signaling process 300 for determining a contention resolution according to some example embodiments of the present disclosure is illustrated. As shown, terminal device 102 receives (304) a PDCCH transmission (306) in the serving cell as part of the RA process and after a Msg3 or MSGA transmission. The PDCCH transmission (306) is addressed to an identifier of terminal device 102. The serving cell is configured with multiple TAGs, and one of the multiple TATs of the multiple TAGs is not active. In some example embodiments, network device 104 may send (302) the PDCCH transmission (306) to terminal device 102.

[0067] Terminal device 102 determines (208) the RA process or the contention resolution of the RA process as successful based on the successful decoding of the received TB and the fact that the MAC PDU corresponding to the TB contains a predetermined MAC CE. As an example, the MAC CE can be an absolute TAC MAC CE. As another example, the MAC CE can be an absolute TAC MAC CE and indicate the TAG ID associated with the TAG for which the TAT is not running.

[0068] In some example embodiments, the MAC CE may be a new empty MAC CE containing only an LCID or eLCID, which instructs the terminal device 102 to apply or continue using a TAC received in a RAR for a TAG associated with an inactive TAT. In some example embodiments, two LCIDs or eLCIDs may be specified, corresponding to different TAG IDs configured for the serving cell.

[0069] In some example embodiments, terminal device 102 can apply a TAC received in RAR or absolute TAC MAC CE to a TAG for which the associated TAT is not running or has expired, and terminal device 102 can start the TAT.

[0070] By implementing Figure 2 and 3 Example embodiments for determining contention solutions can allow the contention solution to be determined without knowing which TAG or TRP the PRACH preamble transmission applies to.

[0071] refer to Figure 4 The illustration shows an example flowchart 400 of a method implemented at a terminal device according to some example embodiments of the present disclosure. (This will be combined with...) Figure 1 For reference.

[0072] At 402, terminal device 102 receives a PDCCH transmission in the serving cell as part of the RA process and after a Msg3 or MSGA transmission. The PDCCH transmission is addressed to the identifier of terminal device 102 and contains the UL authorization for the new transmission. The serving cell is configured with multiple TAGs. At 404, terminal device 102 determines the contention resolution of the RA process as successful or unsuccessful, or determines the RA process as successfully completed or unsuccessfully completed, based on the key between the UL authorization and one of the multiple TAGs.

[0073] In some example embodiments, terminal device 102 may determine the association between a UL authorization and a TAG among multiple TAGs based on the CORESET of the scheduled UL authorization. In some example embodiments, terminal device 102 may determine the association between a UL authorization and a TAG among multiple TAGs based on the indicated TCI state of the UL authorization. In some example embodiments, terminal device 102 may determine the association between a UL authorization and a TAG among multiple TAGs based on a TAG ID associated with a TCI state indicated or configured for a UL transmission scheduled by the UL authorization.

[0074] In some example embodiments, terminal device 102 may determine the association between a UL authorization and a TAG among a plurality of TAGs based on the TAGID corresponding to the PCI associated with the DL RS, wherein the DL RS is included in a TCI state indicated or configured for UL transmissions scheduled by the UL authorization. In some example embodiments, terminal device 102 may determine the association between a UL authorization and a TAG among a plurality of TAGs based on an indication in the UL authorization.

[0075] In some example embodiments, terminal device 102 may determine that the contention resolution is successful or the RA process has successfully completed based on the determination that a TAT for a TAG ID associated with a TAG related to a UL authorization is running. In some example embodiments, terminal device 102 may determine that the contention resolution is successful or the RA process has successfully completed based on the determination that a TAT for a TAG ID associated with a TAG related to a UL authorization is not running. Terminal device 102 may apply stored TAs with TATs that are not scheduled to run as UL timed events. Terminal device 102 may initiate a TAT.

[0076] In some example embodiments, terminal device 102 can apply the stored TA of a TAG as UL timing based on a DCI instruction that determines the scheduling UL authorization: the stored TA applies to the TAG ID of the TAG. Terminal device 102 can apply the stored TA of a TAG as UL timing.

[0077] In some example embodiments, terminal device 102 can determine that the contention resolution is unsuccessful or the RA process is successfully completed by not indicating that the stored TA of the TAG with the TAT that is not running in the DCI based on the determination of the scheduling UL authorization.

[0078] In some example embodiments, terminal device 102 may receive a DCI from network device 104 indicating that terminal device 102 is not allowed to apply the stored TA of the TAG. Terminal device 102 may determine that the contention resolution was unsuccessful.

[0079] refer to Figure 5 The illustration shows another example flowchart 500 of a method implemented at a terminal device according to some example embodiments of the present disclosure. (This will be combined with...) Figure 1 For reference.

[0080] At 502, terminal device 102 receives a PDCCH transmission in the serving cell as part of the RA procedure and after the Msg3 or MSGA transmission. The PDCCH transmission is addressed to the identifier of the terminal device. The serving cell is configured with multiple TAGs, and one of the multiple TATs used for the multiple TAGs is not running. At 504, terminal device 102 determines the contention resolution as successful based on the successful decoding of the received TB and the MAC PDU corresponding to the TB containing a predetermined MAC CE.

[0081] In some example embodiments, the predetermined MAC CE may include an absolute TAC MAC CE. In some example embodiments, the predetermined MAC CE may include a TAC MAC CE and indicate a TAG ID associated with a TAG that is not running among a plurality of TATs. In some example embodiments, the predetermined MAC CE may be a new and empty MAC CE that contains an LCID or eLCID that instructs the terminal device 102 to apply or continue using the TAC received in the RAR.

[0082] In some example embodiments, multiple LCIDs or eLCIDs are specified, corresponding to multiple TAG IDs configured for the serving cell. In some example embodiments, terminal device 102 may apply a TAC received in the RAR or in the absolute TAC MAC CE to the TAG ID of a TAG for which the associated TAT is not running. Terminal device 102 may then initiate the TAT.

[0083] By implementing methods 400 and / or 500, example embodiments for determining contention solutions can be made to determine the contention solution even without knowing which TAG or TRP the PRACH preamble transmission applies to.

[0084] It should be understood that exemplary embodiments of this disclosure may be specified in TS 38.321, TS 38.212, TS38.213, and TS 38.300 as shown in Tables 3-6. Underlined text will be specified. Table 3 Table 4 Table 5 Table 6

[0085] In some example embodiments, the apparatus capable of performing method 400 may include components for performing the corresponding steps of method 400. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0086] In some example embodiments, the apparatus may include: a component for receiving a PDCCH transmission in the serving cell as part of the RA process and after a Msg3 or MSGA transmission, wherein the PDCCH transmission is addressed to an identifier of the terminal device and includes a UL authorization for the new transmission, and the serving cell is configured with a plurality of TAGs; and a component for determining whether the RA process or a contention resolution of the RA process is successful or unsuccessful based on the association between the UL authorization and a TAG among the plurality of TAGs.

[0087] In some example embodiments, the apparatus may further include: a component for determining an association between a UL authorization and a TAG among a plurality of TAGs based on at least one of: a CORESET for scheduling the UL authorization; an indicated TCI state for the UL authorization; a TAG ID associated with a TCI state indicated or configured for a UL transmission scheduled by the UL authorization; and a TAG corresponding to a PCI associated with a DL RS, which is included in the TCI state indicated or configured for a UL transmission scheduled by the UL authorization; or an indication in the UL authorization.

[0088] In some example embodiments, the components for determining a contention solution may further include: components for determining the RA process or the contention solution of the RA process as successful based on the determination that a TAT with a TAG ID associated with a UL authorization is running.

[0089] In some example embodiments, the components for determining a contention solution further include: components for determining the RA process or the contention solution of the RA process as successful based on determining that the TAT for the TAG having a TAG ID associated with UL authorization is not running; components for applying the stored timing advance TA of the TAG having the TAT not running as UL timing; and components for starting the TAT.

[0090] In some example embodiments, the component for applying the stored timing advance TA of a TAG having a non-running TAT as UL timing may further include: a component for determining, based on the scheduling UL authorization, that the stored TA is applicable to the TAG and applying the stored TA of the TAG as UL timing.

[0091] In some example embodiments, the component for determining a contention solution may further include: a component for determining the contention solution of the RA process or the RA process as unsuccessful based on the stored TA applicable to the TAG of the DCI that determines the scheduling UL authorization is not only a TAG with an inactive TAT.

[0092] In some example embodiments, the apparatus may further include: a component for receiving a DCI from a network device, the DCI indicating that the terminal device is not allowed to apply the stored TA of the TAG; and a component for determining that the contention solution is unsuccessful.

[0093] In some example embodiments, the apparatus may further include components for performing other steps in some embodiments of method 400. In some embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to enable the execution of the apparatus.

[0094] In some example embodiments, the apparatus capable of performing method 500 may include components for performing corresponding steps of method 500. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0095] In some example embodiments, the apparatus may include: a component for receiving a PDCCH transmission in the serving cell as part of a random access (RA) procedure and after a Msg3 or MSGA transmission, wherein the PDCCH transmission is addressed to an identifier of the terminal device, the serving cell is configured with multiple TAGs, and one of the multiple TATs for the multiple TAGs is not in operation; and a component for determining the RA procedure or the contention solution of the RA procedure as successful based on (i) the received TB being successfully decoded and (ii) the MAC PDU corresponding to the TB containing a predetermined MAC CE.

[0096] In some example embodiments, the predetermined MAC CE may include an absolute TAC MAC CE. In some example embodiments, the predetermined MAC CE may include a TAC MAC CE and indicate a TAG associated with a non-running TAT among a plurality of TATs.

[0097] In some example embodiments, the predetermined MAC CE may be a new and empty MAC CE containing an LCID or eLCID that instructs the terminal device to apply or continue using the TAC received in the RAR. In some example embodiments, multiple LCIDs or eLCIDs may be specified, corresponding to multiple TAG IDs configured for the serving cell.

[0098] In some example embodiments, the apparatus may include: a component for applying a TAC received in the RAR or in an absolute TAC MAC CE to the TAG ID of a TAG for which the associated TAT is not running; and a component for initiating a TAT.

[0099] In some embodiments, the apparatus may further include components for performing other steps in some embodiments of method 500. In some embodiments, the components include at least one processor and at least one memory including computer program code configured to, together with the at least one processor, cause operation of the apparatus.

[0100] refer to Figure 6 The illustration shows an example simplified block diagram of a device suitable for implementing embodiments of the present disclosure. Device 600 can be provided to implement a communication device, such as... Figure 1 The terminal device 102 shown is illustrated. As shown, device 600 includes one or more processors 610, one or more memories 620 that can be coupled to processor 610, and one or more communication modules 640 that can be coupled to processor 610.

[0101] The communication module 640 is used for bidirectional communication. The communication module 640 has at least one antenna to facilitate communication. The communication interface can represent any interface required for communication with other network elements; for example, the communication interface can be a wireless or wired interface to other network elements, or a software-based interface for communication.

[0102] Processor 610 can be of any type suitable for a local technology network, and by way of non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 600 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0103] Memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that do not persist during power outages.

[0104] Computer program 630 includes computer-executable instructions that are executed by the associated processor 610. Program 630 may be stored in ROM 624. Processor 610 may perform any suitable actions and processes by loading program 630 into RAM 622.

[0105] The embodiments of this disclosure can be implemented by a program, such that device 600 can execute the reference. Figures 2 to 5 Any process discussed in this disclosure. Embodiments of this disclosure may also be implemented in hardware or by a combination of software and hardware.

[0106] In some embodiments, program 630 may be tangibly contained in a computer-readable medium, which may be included in device 600 (such as memory 620) or in other storage devices accessible by device 600. Device 600 may load program 630 from the computer-readable medium into RAM 622 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 7 An example of a computer-readable medium 700 in the form of a CD or DVD is shown. A program 630 is stored on the computer-readable medium.

[0107] Generally, the various embodiments of this disclosure can be implemented using hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented using hardware, while others can be implemented using firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented using hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0108] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in a program module, which execute in a device on a target real or virtual processor to perform the above-mentioned... Figure 4 or Figure 5 The method described is 400 or 500. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions of a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0109] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0110] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0111] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. The term "non-transient" as used herein is a limitation on the medium itself (i.e., tangible, not signaling), not a limitation on the persistence of data storage (e.g., RAM and ROM).

[0112] Furthermore, although operations are described in a specific order, this should not be construed as requiring the operations to be performed in the specific order shown or sequentially, or to perform all of the shown operations to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0113] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features or actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A terminal device, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the terminal device to at least: As part of the random access (RA) procedure, and after the transmission of message 3 (Msg3) or message A (MSGA), a physical downlink control channel (PDCCH) transmission in the serving cell is received, wherein the PDCCH transmission is addressed to the identifier of the terminal device and contains uplink (UL) grants for the new transmission, and the serving cell is configured with multiple timing advance groups (TAGs). as well as Based on the association between the UL authorization and one of the multiple TAGs, the RA process or the contention resolution of the RA process is determined to be successful or unsuccessful.

2. The terminal device according to claim 1, wherein the terminal device is further configured to: The association between the UL authorization and the TAG among the plurality of TAGs is determined based on at least one of the following: Schedule the UL-authorized control resource set (CORESET); The UL-authorized Transmission Configuration Indication (TCI) status; A TAG ID associated with the TCI status indicated or configured for the UL transmission scheduled by the UL authorization; And the TAG ID corresponding to the Physical Cell Identifier (PCI) associated with the downlink (DL) reference signal (RS), the DL RS being included in the TCI state indicated or configured for the UL transmission scheduled by the UL authorization; or The instructions in the UL authorization.

3. The terminal device according to claim 1 or 2, wherein the terminal device is configured to determine the RA process or the contention resolution as successful by: The RA process or the contention resolution is determined to be successful based on the determination that the time alignment timer (TAT) of the TAG associated with the UL authorization is running.

4. The terminal device according to claim 1 or 2, wherein the terminal device is configured to determine the RA process or the contention resolution as successful by: Based on the determination that the TAT associated with the TAG is not running, the stored timing advance (TA) of the TAG with the non-running TAT is applied as UL timing; The TAT begins; as well as The RA process or the contention solution is determined to be successful.

5. The terminal device of claim 4, wherein the terminal device is configured to apply the TA stored in the TAG as UL timing by: Based on the downlink control information (DCI) indication that the UL-authorized downlink control information is applicable to the TAG, the stored TA of the TAG is applied as UL timing.

6. The terminal device according to claim 1 or 2, wherein the terminal device is configured to determine the RA process or the contention solution as unsuccessful by: Based on the determination that the DCI authorized by the UL does not indicate that the stored TA is applicable to the TAG with a TAT that is not running, the RA process or the contention solution is determined to be unsuccessful.

7. The terminal device according to claim 4, wherein the terminal device is further configured to: Receive downlink control information (DCI) from the network device, the DCI indicating that the terminal device is not allowed to apply the TA stored in the TAG; and It was determined that the RA process or the contention resolution was unsuccessful.

8. A terminal device, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the terminal device to at least: As part of the random access (RA) procedure, and after the transmission of message 3 (Msg3) or message A (MSGA), a physical downlink control channel (PDCCH) transmission in the serving cell is received, wherein the PDCCH transmission is addressed to the identifier of the terminal device, the serving cell is configured with multiple timing advance groups (TAGs), and the timing alignment timer (TAT) among the multiple TATs for the multiple TAGs is not running; as well as The RA process or the contention resolution of the RA process is determined to be successful based on (i) the received transport block (TB) being successfully decoded and (ii) the media access control (MAC) protocol data unit (PDU) corresponding to the TB containing a predetermined MAC control element (CE).

9. The terminal device according to claim 8, wherein the predetermined MAC CE comprises: Absolutely timed advance command (TAC) MAC CE.

10. The terminal device of claim 8, wherein the predetermined MAC CE includes a TAC MAC CE and indicates a TAG ID associated with a non-operating TAT among the plurality of TATs.

11. The terminal device according to any one of claims 8-10, wherein the predetermined MAC CE is a new and empty MAC CE containing a logical channel ID (LCID) or an extended LCID (eLCID), the LCID or the eLCID indicating that the terminal device applies or continues to use the TAC received in the random access response (RAR).

12. The terminal device of claim 11, wherein a plurality of LCIDs or eLCIDs are designated, the plurality of LCIDs or eLCIDs corresponding to a plurality of TAG IDs configured for the serving cell.

13. The terminal device according to claim 9, 11 or 12, wherein the terminal device is further configured to: The TAC received in the RAR or in the absolute TAC MAC CE is applied to the TAG ID, and for the TAG ID, the associated TAT is not running; and The TAT begins.

14. A method comprising: As part of the random access (RA) procedure, and after the transmission of message 3 (Msg3) or message A (MSGA), at the terminal device, a physical downlink control channel (PDCCH) transmission in the serving cell is received from the network device, wherein the PDCCH transmission is addressed to the identifier of the terminal device and contains uplink (UL) grants for the new transmission, and the serving cell is configured with multiple timing advance groups (TAGs). as well as Based on the association between the UL authorization and one of the multiple TAGs, the RA process or the contention solution for the RA process is determined as successful or unsuccessful at the terminal device.

15. A method comprising: As part of a random access (RA) procedure, or after the transmission of message 3 (Msg3) or message A (MSGA), at the terminal device, a physical downlink control channel (PDCCH) transmission in the serving cell is received from the network device, wherein the PDCCH transmission is addressed to the identifier of the terminal device, the serving cell is configured with multiple timing advance groups (TAGs), and the time alignment timer (TAT) of the multiple TATs for the multiple TAGs is not running; as well as Based on (i) the received Transport Block (TB) being successfully decoded and (ii) the Media Access Control (MAC) Protocol Data Unit (PDU) corresponding to the TB containing a predetermined MAC Control Element (CE), the RA process or the contention resolution of the RA process is determined to be successful at the terminal device.

16. A non-transitory computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the method according to claim 14 or 15.

Images