Identification of user equipment for physical uplink shared channel transmission

Abstract

Apparatuses, methods, and media are provided for identification of a user equipment for a PUSCH transmission. In the method, a first apparatus obtains a first identifier, the first identifier identifying the first apparatus. Prior to encoding, the first apparatus scrambles at least one of cyclic redundancy check (CRC) and data bits of a physical uplink shared channel (PUSCH) transmission using the first identifier. The first apparatus then performs the PUSCH transmission toward a second apparatus on a PUSCH resource.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure are generally related to the telecommunications field, and more particularly to methods, apparatus, devices, and computer-readable storage media for identifying user equipment for Physical Uplink Shared Channel (PUSCH) transmissions. Background Technology

[0002] In current communication systems, uplink transmissions on the Physical Uplink Shared Channel (PUSCH) can include Configured Grant (CG) PUSCH transmissions and Dynamic Grant (DG) PUSCH transmissions. For CG PUSCH transmissions, transmission resources can be semi-statically configured by network nodes or network devices via higher-layer signaling and can be dynamically activated or deactivated as needed. DG PUSCH transmissions can rely on resources dynamically allocated by network nodes and indicated in real-time via specific fields in the Scheduled Downlink Control Information (DCI). In both transmissions, the network node maintains control over resource allocation, thereby ensuring it is aware of when user equipment is scheduled or permitted to transmit. Summary of the Invention

[0003] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to at least: obtain a first identifier identifying the first apparatus; scramble at least one of a cyclic redundancy check (CRC) and data bits of a PUSCH transmission using the first identifier before encoding; and perform a PUSCH transmission toward a second apparatus on a PUSCH resource.

[0004] In a second aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to at least: receive a PUSCH transmission from a first apparatus on a PUSCH resource; and, after decoding, descramble at least one of the CRC and data bits of the PUSCH transmission using at least a first identifier identifying the first apparatus.

[0005] In a third aspect of this disclosure, a method is provided. The method includes: obtaining a first identifier identifying a first device; scrambling at least one of a CRC and data bits of a PUSCH transmission using the first identifier before encoding; and performing a PUSCH transmission toward a second device on a PUSCH resource.

[0006] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving a PUSCH transmission from a first device on a PUSCH resource; and after decoding, descrambling at least one of the CRC and data bits of the PUSCH transmission using at least a first identifier identifying the first device.

[0007] In a fifth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: means for obtaining a first identifier that identifies the first apparatus; means for scrambling at least one of a CRC and data bits of a PUSCH transmission using the first identifier before encoding; and means for performing a PUSCH transmission toward a second apparatus on a PUSCH resource.

[0008] In a sixth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving a PUSCH transmission from a first apparatus on a PUSCH resource; and components for descrambling at least one of the CRC and data bits of the PUSCH transmission after decoding, using at least a first identifier identifying the first apparatus.

[0009] In a seventh aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to at least: obtain a first identifier identifying the first apparatus; perform a PUSCH transfer toward a second apparatus on a PUSCH resource; and send an indication of the first identifier to the second apparatus via Layer 1 (L1) control signaling.

[0010] In an eighth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to at least: receive a PUSCH transmission from a first apparatus on a PUSCH resource; and receive an indication of a first identifier from the first apparatus via L1 control signaling, wherein the first identifier identifies the first apparatus.

[0011] In a ninth aspect of this disclosure, a method is provided. The method includes: obtaining a first identifier that identifies a first device; performing a PUSCH transfer toward a second device on a PUSCH resource; and sending an indication of the first identifier to the second device via L1 control signaling.

[0012] In a tenth aspect of this disclosure, a method is provided. The method includes: receiving a PUSCH transmission from a first device on a PUSCH resource; and receiving an indication of a first identifier from the first device via L1 control signaling, wherein the first identifier identifies the first device.

[0013] In the eleventh aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for obtaining a first identifier that identifies the first apparatus; components for performing a PUSCH transfer toward a second apparatus on a PUSCH resource; and components for sending an indication of the first identifier to the second apparatus via L1 control signaling.

[0014] In a twelfth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving PUSCH transmissions from a first apparatus on PUSCH resources; and components for receiving an indication of a first identifier from the first apparatus via L1 control signaling, wherein the first identifier identifies the first apparatus.

[0015] In a thirteenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon that cause an apparatus to perform at least the methods described according to the third, fourth, ninth, and tenth aspects.

[0016] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended 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: Figure 1 An example communication environment in which example embodiments of the present disclosure may be implemented is shown; Figure 2 An example signaling stream of PUSCH transmission according to some example embodiments of this disclosure is shown; Figure 3 An example signaling stream of PUSCH transmission according to some example embodiments of this disclosure is shown; Figure 4 An example signaling stream of PUSCH transmission according to some other example embodiments of this disclosure is shown; Figure 5 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 6 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 7 A flowchart is shown illustrating a method implemented at a first device according to some other exemplary embodiments of the present disclosure; Figure 8 A flowchart is shown illustrating a method implemented at a second device according to some other exemplary embodiments of the present disclosure; Figure 9A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 10 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

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

[0019] The principles 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, without imposing any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0020] 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.

[0021] References to "an embodiment," "an embodiment," "an example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment needs to include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, whether explicitly described or not, it is believed that those skilled in the art will understand the application of such features, structures, or characteristics in conjunction with other embodiments.

[0022] It should be understood that although the terms “first,” “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, and they do not restrict the order of the nouns. 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.

[0023] As used herein, “at least one of the following: ” and “at least one of ” and similar expressions, wherein the list of two or more elements is connected by “and” or “or”, means at least one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0024] As used herein, unless explicitly stated otherwise, performing the “responding to A” step does not mean that the step is performed immediately after “A” occurs, but may include one or more intervention steps.

[0025] 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 should also be understood that the terms “comprising,” “including,” “having,” “possessing,” “containing,” and / or “covering,” as used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0026] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) Hardware circuit implementation only (e.g., implemented with purely analog and / or digital circuits) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions) and (c) The operation requires software (e.g., firmware) for the operation of (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts thereof, but the software may be absent when the operation does not require the software.

[0027] This definition of "circuit" applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term "circuit" also covers only hardware circuitry or processors (or processors), or a portion of hardware circuitry or processors and their accompanying software and / or firmware implementations. For example, where applicable to a particular claim element, the term "circuit" 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.

[0028] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), 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 user equipment and network equipment in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5G Advanced, sixth-generation (6G) communication protocols, wireless LAN communication protocols (such as IEEE 802.11), and / or any other currently known or future protocols. Furthermore, communication can 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 currently known or future-developed technology. Embodiments can be applied to a variety of communication systems. Given the rapid development of communication, there will naturally be future types of communication technologies and systems that can implement this disclosure. This should not be construed as limiting the scope to the aforementioned systems.

[0029] As used herein, the term "network device" refers to a node in a communications network through which user equipment accesses the network and receives services. Depending on the terminology and technologies applied, network devices may include base stations (BS) or access points (APs), such as Node Bs (NodeBs or NBs), evolved Node Bs (eNodeBs or eNBs), NR NBs (also known as gNBs), remote radio units (RRUs), radio heads (RHs), remote radio heads (RRHs), relays, integrated access and backhaul (IAB) nodes, low-power nodes (such as femtoseconds, picoseconds), non-terrestrial network (NTN) or non-terrestrial network devices (such as satellite network devices, low Earth orbit (LEO) satellites, and geostationary Earth orbit (GEO) satellites), spacecraft network devices, etc. In some example embodiments, network devices may utilize a radio access network (RAN) split architecture, where network devices include centralized units (CUs) and distributed units (DUs).

[0030] The term "user equipment" refers to any terminal device with wireless communication capabilities. By way of example and not limitation, user equipment may also be referred to as communication equipment, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). User equipment may include, but is not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable user devices, personal digital assistants (PDAs), portable computers, desktop computers, image acquisition user equipment (such as digital cameras), gaming user devices, music storage and playback devices, in-vehicle wireless user equipment, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless client 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 the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. User equipment may also correspond to the mobile terminal (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "user equipment," "user device," "user gear," and "UE" are used interchangeably.

[0031] Figure 1 An example communication environment 100 in which example embodiments of the present disclosure may be implemented is shown. For example... Figure 1 As shown, the communication environment 100 may include a first device 110, which can operate as a user equipment (such as a UE). The communication environment 100 may also include a second device 120, which can operate as a network device (such as a BS or gNB).

[0032] In some example embodiments, if the first device 110 is a user equipment and the second device 120 is a network device, the link from the second device 120 to the first device 110 may be referred to as a downlink (DL), and the link from the first device 110 to the second device 120 may be referred to as an uplink (UL). In the DL, the second device 120 may be a transmitting (TX) device (or transmitter), and the first device 110 may be a receiving (RX) device (or receiver). In the UL, the first device 110 may be a TX device, and the second device 120 may be an RX device.

[0033] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. The communication environment 100 may include any suitable number of devices configured to implement some of the example embodiments.

[0034] In the following description, for illustrative purposes, some example embodiments are described in which the first device 110 operates as a user equipment (e.g., a UE) and the second device 120 operates as a network device (e.g., a BS or gNB). However, in some example embodiments, the operations described in connection with the user equipment can be implemented at the network device or other devices, and the operations described in connection with the network device can be implemented at the user equipment or other devices.

[0035] In communication environment 100, the DG PUSCH can be scheduled by a second device 120 (e.g., a network device) for a first device 110 (e.g., a UE) using a scheduling DCI, wherein the scheduling DCI contains UL authorization and is transmitted on the Physical Downlink Control Channel (PDCCH). The first device 110 can monitor the PDCCH to detect possible UL authorizations addressed to a UE-specific identifier (e.g., a Cell Radio Network Temporary Identifier (C-RNTI)).

[0036] In the case of CG PUSCH, the second device 120 can semi-statically allocate PUSCH resources with two different types of configuration grants. In Type 1, periodic configured uplink grants can be provided directly via RRC signaling. There may not be a separate step to activate or deactivate the CG PUSCH. In Type 2, the periodicity of the CG PUSCH resource can be defined by RRC signaling, and the use of the CG PUSCH can be activated or deactivated using a DCI addressed to a UE-specific CS-RNTI. The DCI activating the CG PUSCH resource can indicate other parameters of the PUSCH resource.

[0037] Unlike DG PUSCH and CG PUSCH, CB PUSCH can be based on PUSCH transmissions on PUSCH resources selected from a shared pool of PUSCH resources shared by multiple user equipment. CB PUSCH can reduce latency for certain processes (such as scheduling requests), but may introduce the possibility of collisions when multiple user equipments transmit simultaneously on the same PUSCH resource. How to effectively and efficiently identify which user equipment has sent a PUSCH in CB PUSCH is a topic of interest for further research.

[0038] In the case of CB PUSCH, multiple user equipments (UEs) can be configured to use the same PUSCH resources and the same DM-RS antenna port. If each UE maintains its own UE-specific bit scrambling, the network device can perform separate descrambling and decoding for each UE at each CB PUSCH timing, leading to significant complexity. Conversely, if the UE-specific bit scrambling is removed, the network device faces challenges in identifying the transmitting UE. For example, if only one UE from multiple configured UEs transmits a PUSCH and the network device successfully decodes it, the lack of UE-specific identification renders the received signal useless because the network device cannot determine which UE transmitted it.

[0039] In another scenario, multiple user equipments (UEs) may simultaneously transmit on the same PUSCH resource using the same DM-RS antenna port, leading to collisions at the receiver. Because all transmissions use the same antenna port, the network device cannot distinguish between UEs at the physical layer. Therefore, the network device can successfully decode signals from one UE while ignoring transmissions from another clashing UE. This can occur, for example, when one UE experiences better channel conditions than another, causing signals from clashing UEs to be treated as additive noise during demodulation and decoding. Even if the network device successfully decodes the PUSCH signal, it still does not know the identity of the transmitting UE.

[0040] It should be noted that although this issue is described in the context of CB PUSCH, a similar problem can occur in CG PUSCH. If two user equipments are configured with the same resources and the same antenna ports as determined by the network device, the network device faces the same uncertainty regarding the identity of the sending user equipment. In this case, detecting a correct CRC from the received signal only confirms that the PUSCH transmission was successfully received, without indicating the origin of the transmission.

[0041] In either the CB PUSCH or CG PUSCH, the absence of a UE identifier at the network device will result in lost uplink packets. When a CRC error occurs, the network device does not request a retransmission for that antenna port. Therefore, all transmitting UEs assume their transmissions were successful, even if only one transmission was correctly received. This highlights the need for an additional method of UE identification besides relying on the DM-RS antenna port.

[0042] In some implementations, to identify the user equipment associated with the received CB PUSCH, the CB PUSCH transmission can be supplemented by a transmission on resources dedicated to the user equipment. For example, the CB PUSCH may be accompanied by a scheduling request transmission. However, this approach may require additional resource allocation.

[0043] In some other implementations, scrambling sequences initialized based on a Radio Network Temporary Identifier (RNTI) associated with the PUSCH can be used to scramble CB PUSCH transmissions (e.g., bits following coded or modulated symbols). Since the RNTI is unique and specific to the user equipment, the network device can identify the user equipment upon receiving a CB PUSCH transmission after blindly decoding the PUSCH using a possible set of scrambling sequences. However, as will be described below, this method is complex, and the PUSCH may need to be decoded multiple times.

[0044] Given the complex initialization process, the scrambling sequence can depend on multiple parameters, including RNTI, which can be further affected by higher-layer configurations and signaling conditions. When CB PUSCH is available, network devices may have to blindly decode the PUSCH signal by trying different combinations of potential scrambling sequences.

[0045] According to some example embodiments, a solution for identifying a user equipment (UE) for PUSCH transmissions is provided. In this solution, when a first device performs a PUSCH transmission toward a second device, the first device can explicitly or implicitly identify itself for the PUSCH transmission. In some example embodiments, the first device can use a first identifier (ID) identifying itself to scramble the PUSCH transmission to implicitly identify itself for the PUSCH transmission. In some other example embodiments, the first device can send an indication of the first identifier to the second device via L1 control signaling to explicitly identify itself for the PUSCH transmission.

[0046] Therefore, the second device (i.e., the network device) can determine which device (e.g., user equipment or UE) performs the PUSCH transmission based on a first identifier of the first device, which is obtained by descrambling or explicitly receiving the PUSCH transmission.

[0047] This solution is more efficient and less complex, avoiding the overhead of complex parameter initialization and multiple decoding attempts, making it more practical for identifying user equipment in PUSCH transmissions.

[0048] In the following text, CB PUSCH transports will be used as examples to describe some exemplary embodiments. It should be understood that the exemplary embodiments described herein can generally be applied to other types of PUSCH transports, such as CG PUSCH transports on resources used in a contention-based manner.

[0049] Now for reference Figure 2This illustrates an example signaling stream 200 transmitted via PUSCH according to some example embodiments. The signaling stream relates to a first device 110 and a second device 120.

[0050] like Figure 2 As shown, the first device 110 obtains (202) a first identifier that identifies the first device. The first device 110 may obtain the first identifier in any suitable manner. As an example, the first identifier may be configured by the network and thus received by the first device 110 from the second device 120. As another example, the first identifier may be predefined or specified in a communication standard such as the 3rd Generation Partnership Project (3GPP) standard.

[0051] In some example embodiments, the second device 120 may send at least one configuration of the first identifier to the first device 110. Accordingly, the first device 110 may receive at least one configuration of the first identifier from the second device 120.

[0052] The first identifier can be implemented in any suitable form. In some example embodiments, the first identifier may be at least a portion of the identifier of the first device 110 that identifies a dedicated channel scheduled by the first device 110. In some example embodiments, the identifier of the first device 110 may include a C-RNTI.

[0053] The first device 110 performs (210) a PUSCH transmission toward the second device 120 on the PUSCH resource. In some example embodiments, the PUSCH may include a CB PUSCH. Prior to the PUSCH transmission, the first device 110 scrambles (206) at least one of the CRC or data bits of the PUSCH transmission using a first identifier before encoding. As an example, the first device may generate a CRC based on a payload delivered from a higher layer and scramble the CRC using the first identifier.

[0054] In some example embodiments, when the first device 110 scrambles the CRC, the bit length of the first identifier may depend on the bit length of the CRC transmitted via PUSCH. As an example, the size of the first identifier used for CRC scrambling may depend on the size of the CRC, which can be indicated by the bit length. For example, based on the size of the payload or transport block, the CRC may include two sizes: 16 bits or 24 bits. In this case, the first device 110 may determine the size of the first identifier based on the actual CRC size used. In some example embodiments, the size of the first identifier may be predetermined or configured by the second device 120.

[0055] Depending on whether the size of the first identifier is smaller or larger than the CRC size used, CRC scrambling can be performed differently. For example, if it is determined that the size of the first identifier is smaller than the CRC size, in some example embodiments, a scrambling vector for CRC scrambling can be formed based on the first identifier, and the dimension of the scrambling vector can be determined based on the bit length of the CRC transmitted via PUSCH. For example, the scrambling vector can be padded with the first identifier and at least one dummy bit. As another example, the first identifier can be repeated cyclically up to the length of the scrambling vector.

[0056] In some example embodiments, if the bit length of the first identifier is greater than the bit length of the CRC for PUSCH transmission, a portion of the first identifier may be used for CRC scrambling in PUSCH transmission. In some example embodiments, the portion of the first identifier includes at least one of the following: the most significant bit (MSB) of the first identifier and the least significant bit (LSB) of the first identifier. As an example, if K MSBs or LBSs are used for CRC scrambling, the second device 120 may be responsible for ensuring that multiple first devices 110 having corresponding first identifiers including the same K MSBs or LBSs are not assigned to the same PUSCH resource.

[0057] In some example embodiments, CRC scrambling for PUSCH transmission may include CRC scrambling of at least one of the transport block (TB) and code block (CB) of the PUSCH transmission. As an example, when the payload is sufficiently small, CRC scrambling may be applied only to the TB with the first identifier, so that the TB may not be segmented (e.g., the TB consists of only one code block); however, this may also be applied where multiple code blocks may exist. As an alternative example, the payload may be segmented into multiple code blocks due to the size of the payload, CRC may be appended to each CB, and each CRC may be scrambled with the first identifier.

[0058] In addition to using the first identifier to CRC scramble the PUSCH transmission as described above, or as an alternative, in some example embodiments, the first device 110 may use the first identifier to scramble the data bits in the PUSCH transmission before encoding.

[0059] After the second device 120 receives (212) PUSCH transmission from the first device 110 on the PUSCH resource, the second device 120 descrambles at least one of the CRC or data bits of the PUSCH transmission using at least the first identifier that identifies the first device 110 after decoding.

[0060] In some example embodiments, when the second device 120 descrambles the CRC, the bit length of the first identifier depends on the bit length of the CRC transmitted by the PUSCH.

[0061] In some example embodiments, if the bit length of the first identifier is less than the bit length of the CRC, a descrambling vector for CRC descrambling can be formed based on the first identifier, and the dimension of the descrambling vector can be determined based on the bit length of the CRC transmitted via PUSCH. In some example embodiments, the descrambling vector may be padded with the first identifier and at least one dummy bit. In some example embodiments, the first identifier is repeated cyclically to form the descrambling vector.

[0062] In some example embodiments, if the bit length of the first identifier is greater than the bit length of the CRC of the PUSCH transmission, a portion of the first identifier can be used for CRC descrambling of the PUSCH transmission. In some example embodiments, CRC descrambling can be applied to at least one of the transport blocks or code blocks of the PUSCH transmission. In some example embodiments, descrambling of the PUSCH transmission can include descrambling the data bits in the PUSCH transmission using the first identifier after decoding.

[0063] In some example embodiments, in addition to a first identifier identifying the first device 110, the first device 110 may use a second identifier associated with the PUSCH resources used for PUSCH transmission to scramble PUSCH transmission. For example, as Figure 2 As shown, the first device 110 can obtain (204) a second identifier, which may be shared, for example, for more than one user equipment configured with a PUSCH. As an example, the second identifier may be shared for all user equipment sharing the same PUSCH resources and DM-RS ports.

[0064] Similar to the first identifier, the first device 110 can obtain the second identifier in any suitable manner. In some example embodiments, the second device 120 can send at least one configuration of the second identifier to the first device 110. Accordingly, the first device 110 can receive at least one configuration of the second identifier from the second device 120.

[0065] The first device 110 may use a second identifier to scramble (208) the PUSCH transmission after encoding. In some example embodiments, the second identifier may be used for data scrambling in the PUSCH transmission. In some example embodiments, data scrambling may include at least one of bit scrambling and modulation scrambling. In some example embodiments, the second identifier may be used in the initialization of the pseudo-random generator used for scrambling.

[0066] As an example, bit scrambling using the second identifier can occur after encoding and possibly after rate matching, but before generating modulation symbols based on bits. Scrambling can be applied throughout the payload.

[0067] In some example embodiments, after receiving a PUSCH transmission, the second device 120 may descramble the PUSCH transmission using a second identifier before decoding. In some example embodiments, the second identifier may be used for data descrambling of the PUSCH transmission. In some example embodiments, data descrambling may include at least one of bit descrambling and modulation descrambling. In some example embodiments, the second identifier may be used in the initialization of a pseudo-random generator used for descrambling.

[0068] As an example, the result of descrambling the PUSCH using the second identifier may include the log-likelihood ratio, which can be used as the input value for the decoder. Then, in the case where the TB is scrambled using the first identifier, the second device 120 can decode the received signal and descramble the TB CRC and / or data bits using all potential first identifiers configured for transmission during the PUSCH timing. As an example, after descrambling, the second device 120 can determine which user equipment sent the PUSCH signal based on the first identifier that would likely lead to a successful CRC check.

[0069] By utilizing a second identifier that may be shared by all user equipment sharing the same PUSCH resources and DM-RS ports, when resource allocation, modulation and coding scheme (MCS) and TB size are uniformly configured for all user equipment sharing the same PUSCH resources, the second device 120 may only need to perform a single decoding of the PUSCH signal, rather than decoding each potential transmitting user equipment individually.

[0070] In some example embodiments, the network device can configure PUSCH resources for the first device 110. In this example, the second device 120 can send the PUSCH resource configuration to the first device 110. Accordingly, the first device 110 can receive the PUSCH resource configuration from the second device 120.

[0071] In some example embodiments, the configuration of PUSCH resources may be associated with at least one of the following: frequency domain resource allocation (FDRA), time domain resource allocation (TDRA), DM-RS, or modulation and coding scheme (MCS). As an example, the configuration of PUSCH resources may include parameters including, for example, at least one of the following: at least one resource block, at least one symbol of the time slot allocated for PUSCH resources, the timing of PUSCH transmission, and the MCS used in PUSCH.

[0072] In some example implementations, the configuration of PUSCH resources can be shared across more than one user equipment (UE) with configured PUSCH resources. For example, for all UEs configured with the same PUSCH and the same DM-RS port, the parameter values ​​for FDRA, TDRA, DM-RS, or MSC can be identical, but the configuration signaling can be dependent on or dedicated to the UE.

[0073] In some example embodiments, the configuration of the PUSCH resource can be sent by the second device 120 and received by the first device 110 via at least one of RRC signaling and MAC signaling. In some example embodiments, at least one of the RRC signaling and MAC signaling can be specific to the first device 110. As an example, the configuration can be sent semi-statically via RRC signaling or dynamically provided via a MAC control element (CE). Alternatively, as another example, the configuration can be sent via a combination of RRC and MAC signaling. For example, some parameters are configured semi-statically via RRC signaling, and the remaining parameters are dynamically activated (e.g., as in a Type 2 CG PUSCH) or provided via MAC-CE.

[0074] It should be understood that configuration for PUSCH resources can be received via any other signaling. Semi-static configuration via RRC can provide the advantage of reduced resource allocation overhead, while the use of MAC-CE allows for faster and more flexible adaptation to changing network conditions.

[0075] Instead of scrambling the entire PUSCH payload, some example embodiments of this disclosure provide a more efficient and less complex solution by scrambling the CRC and / or data bits of the PUSCH using only a first identifier and then scrambling the data using a second identifier after encoding. In this way, scrambling and subsequent descrambling have lower complexity.

[0076] The following will refer to Figure 3 Describe an example procedure for a PUSCH transmission (e.g., a CB PUSCH transmission). In this example, UE301 is an example of a first device 110, and gNB 302 is an example of a second device 120.

[0077] like Figure 3As shown, in procedure 300, gNB 302 may send (305) a configuration of two identifiers (IDs) to UE 301, the two IDs including a scrambling ID (or a common ID, which is an example of the second identifier) ​​for configuring CB PUSCH operations between gNB 302 and UE 301, and a UE ID (as an example of the first identifier). The scrambling ID can be used to scramble the encoded CB PUSCH data and can be shared by all UEs sharing the same CB PUSCH resources and DM-RS port. The UE ID can be used to identify the UE in received CB PUSCH transmissions.

[0078] Additionally, UE 301 can be configured with other parameters for CB PUSCH operation. These parameter values ​​can be shared across all UEs sharing the same CBPUSCH resources and DMRS ports. Other parameters may include, for example, the resource blocks and symbols for the time slots allocated for CBPUSCH resources, the timing of CB PUSCH occurrences, and the modulation and coding scheme used in the CB PUSCH.

[0079] Then, UE 301 can perform (310) CB PUSCH preparation, which includes CRC and / or data bit scrambling using the configured UEID and data scrambling (bits or modulation symbols) using the configured scrambling ID after encoding. As an example, UE 301 can generate a CRC based on the payload delivered from a higher layer, and UE 301 can scramble the CRC using the UE ID. In another example, when the payload is small and the TB is not segmented, the CRC can be scrambled only for the TB using the UEID. Alternatively, scrambling using the UE ID can be applied only to the Layer 1 (L1) bits (excluding CRC bits) of the CB PUSCH data, and the CRC can be generated based on the unscrambled L1 bits of the data.

[0080] The CB PUSCH bits can then be scrambled using a scrambling ID, and this bit scrambling can occur after encoding, possibly after rate matching, and before the data bit-based modulation symbol generation process. In some example embodiments, scrambling using a scrambling ID can be applied to the entire payload.

[0081] Subsequently, UE 301 may perform (315) a CB PUSCH transmission toward gNB 302. gNB 302 may perform (320) a CB PUSCH reception, including bit descrambling or modulation symbol descrambling using a configured scrambling ID and CRC and / or data bit descrambling using a possible UE ID. As an example, the bit estimate or modulation symbol estimate obtained by descrambling using the scrambling ID can be represented by the log-likelihood ratio used as the input value of the decoder.

[0082] After descrambling the data (bits or modulation symbols) using the scrambling ID, the received signal can be decoded, and the TBCRC and / or data bits can be descrambled using all possible UE IDs that may have been transmitted during the CB PUSCH transmission period. The gNB 302 can know the set of UEs that can transmit during a specific CB PUSCH transmission period. For example, the gNB 302 can know which UEs are configured with CB PUSCH resources during a specific transmission period.

[0083] Finally, gNB 302 can identify the specific UE301 that sends the CB PUSCH signal based on the UE ID that can detect the CRC.

[0084] Instead of using a first identifier to scramble and subsequently descramble CRC or data bits of the CB PUSCH to identify the first device 110, in some other example embodiments, the identification of the first device 110 can be performed via an L1 indication of the first identifier. As an example, a portion of the L1 bits can be reserved for such an explicit indication. Reference will be made below. Figure 4 Some example embodiments related to this explicit instruction are described. Figure 4 An example signaling flow 400 for PUSCH transmission according to some other example embodiments is shown. The signaling flow involves a first device 110 and a second device 120.

[0085] like Figure 4 As shown, the first device 110 obtains (402) a first identifier that identifies the first device. As described above, the first device 110 may obtain the first identifier in any suitable manner.

[0086] The first device 110 performs (404) a PUSCH transmission toward the second device 120 on the PUSCH resource. Accordingly, the second device 120 receives (406) a PUSCH transmission from the first device 110 on the PUSCH resource. In some example embodiments, the PUSCH may include a CB PUSCH.

[0087] The first device 110 sends an indication of the first identifier to the second device 120 via Layer 1 (L1) control signaling. Accordingly, the second device 120 receives (410) the indication of the first identifier from the first device 110 via L1 control signaling. The advantage of using L1 bits (such as L1 control signaling) to indicate the first identifier is that transmission delay can be reduced.

[0088] In some example embodiments, an indication of the first identifier may be sent via at least a portion of the Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) bits in the PUSCH transmission. For example, HARQ-ACK for the Physical Downlink Shared Channel (PDSCH) may be multiplexed on the PUSCH. In this case, a HARQ-ACK mechanism including operations such as encoding and multiplexing with the Uplink Shared Channel (UL-SCH) may be used to identify the first device 110. In some example embodiments, the first identifier may be concatenated with at least one bit for HARO-ACK to form HARO-ACK bits.

[0089] In some example embodiments, the first identifier can be encoded separately from the HARO-ACK information, and the encoded first identifier bits can be concatenated with the encoded HARO-ACK bits (if any). The concatenated encoded bits can then be mapped to physical resource elements in the same manner as the HARO-ACK bits. Mapping the concatenated bits to physical resources can follow the HARQ-ACK process, thereby simplifying resource management and improving spectral efficiency. Furthermore, the inherent robustness of L1, combined with mechanisms such as HARQ and independent coding, can enhance reliability even under weak radio conditions.

[0090] Furthermore, a separate beta offset factor can be defined for the indication of the first identifier. For example, the beta offset factor for the indication of the first identifier can be greater than the beta offset factor for HARO-ACK information, thereby achieving a lower code rate and higher reliability for the transmission of the indication of the first identifier. This method allows for independent optimization of coding parameters; for example, more power can be allocated to the first identifier for a separate beta offset, thereby improving the reliability of the transmission of the indication of the first identifier.

[0091] In some other example embodiments, HARQ-ACK information for PDSCH can be sent on a separate resource, rather than multiplexed with data or signaling on PUSCH. In this case, the first identifier can be indicated to the second device 120 via other L1 bits.

[0092] It should be understood that, as mentioned above, Figure 2 and Figure 3The features and operations described in relation to the first device 110 and the second device 120 during PUSCH transmission also apply to Figure 4 The process described above has a similar effect. For the sake of simplicity, its details will not be repeated.

[0093] Figure 5 A flowchart of an example method 500 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 500 is described by the angle of the first device 110 in the middle.

[0094] At frame 510, the first device 110 obtains a first identifier that identifies the first device.

[0095] At block 520, before encoding, the first device 110 scrambles at least one of the cyclic redundancy check (CRC) and data bits transmitted on the Physical Uplink Shared Channel (PUSCH) using a first identifier.

[0096] At box 530, the first device 110 performs a PUSCH transfer toward the second device on the PUSCH resource.

[0097] In some example embodiments, when the first device 110 scrambles the CRC, the bit length of the first identifier may depend on the bit length of the CRC transmitted by the PUSCH.

[0098] In some example embodiments, when the first device 110 scrambles the CRC, the scrambling vector used for CRC scrambling may be formed based on a first identifier, and the bit length based on the first identifier is less than the bit length of the CRC. The dimension of the scrambling vector is determined according to the bit length of the CRC transmitted by the PUSCH.

[0099] In some example embodiments, the scrambling vector may be filled with a first identifier and at least one virtual bit.

[0100] In some example embodiments, the first identifier may be repeated cyclically to form a scrambling vector.

[0101] In some example embodiments, when the first device 110 scrambles the CRC, a portion of the first identifier can be used for CRC scrambling of the PUSCH transmission because the bit length of the first identifier is greater than the bit length of the CRC transmitted by the PUSCH.

[0102] In some example embodiments, the portion of the first identifier includes at least one of the following: the MSB of the first identifier and the LSB of the first identifier.

[0103] In some example embodiments, when the first device 110 scrambles the CRC, the CRC scrambling may include CRC scrambling of at least one of the transport block and code block of the PUSCH transmission.

[0104] In some example embodiments, the first device 110 may scramble the PUSCH transmission using a second identifier after encoding.

[0105] In some example embodiments, the second identifier may be associated with a PUSCH resource used for PUSCH transmission.

[0106] In some example embodiments, the second identifier may be shared across more than one user equipment configured with PUSCH resources.

[0107] In some example embodiments, scrambling using a second identifier may include scrambling the data transmitted by the PUSCH using the second identifier.

[0108] In some example embodiments, data scrambling may include at least one of bit scrambling and modulation symbol scrambling.

[0109] In some example embodiments, the second identifier may be used in the initialization of the pseudo-random generator used for scrambling.

[0110] In some example embodiments, the first device 110 may receive at least one configuration of the second identifier from the second device 120.

[0111] In some example embodiments, the first device 110 may receive at least one configuration of the first identifier from the second device 120.

[0112] In some example embodiments, the first identifier may be at least a portion of the following identifiers of the first device 110, which identify a dedicated channel scheduled for the first device 110.

[0113] In some example embodiments, the identifier of the first device 110 may include C-RNTI.

[0114] In some example embodiments, the first device 110 may receive the configuration of the PUSCH resources from the second device.

[0115] In some example embodiments, the configuration of PUSCH resources may be received via at least one of the following: RRC signaling and MAC signaling.

[0116] In some example embodiments, at least one of the RRC signaling and MAC signaling is specific to the first device.

[0117] In some example embodiments, the configuration of PUSCH resources may be associated with at least one of the following: FDRA, TDRA, DM-RS, and MCS.

[0118] In some example implementations, the configuration of PUSCH resources can be shared by more than one user equipment that has PUSCH resources configured.

[0119] In some example embodiments, PUSCH may include CB PUSCH.

[0120] In some example embodiments, a first means capable of performing method 500 (e.g., Figure 1 The first device 110 may include components for performing corresponding operations of method 500 and / or any of the one or more example embodiments described herein. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In the first device 110.

[0121] Figure 6 A flowchart of an example method 600 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 600 is described by the angle of the second device 120 in the middle.

[0122] At box 610, the second device 120 receives PUSCH transmissions from the first device on the PUSCH resource.

[0123] At box 620, after decoding, the second device 120 descrambles at least one of the CRC and data bits of the PUSCH transmission using at least the first identifier that identifies the first device.

[0124] In some example embodiments, when the second device 120 descrambles the CRC, the bit length of the first identifier depends on the bit length of the CRC transmitted by the PUSCH.

[0125] In some example embodiments, when the second device 120 descrambles the CRC, the descrambling vector used for CRC descrambling may be formed based on a first identifier, and the bit length based on the first identifier is less than the bit length of the CRC. The dimension of the descrambling vector may be determined based on the bit length of the CRC transmitted by the PUSCH.

[0126] In some example embodiments, the descrambling vector may be filled with a first identifier and at least one virtual bit.

[0127] In some example embodiments, the first identifier may be repeated cyclically to form a descrambling vector.

[0128] In some example embodiments, when the second device 120 descrambles the CRC, a portion of the first identifier can be used for CRC descrambling of the PUSCH transmission because the bit length of the first identifier is greater than the bit length of the CRC transmitted by the PUSCH.

[0129] In some example embodiments, the portion of the first identifier may include at least one of the following: the MSB of the first identifier and the LSB of the first identifier.

[0130] In some example embodiments, CRC descrambling may include CRC descrambling of at least one of the transport block and code block of the PUSCH transmission.

[0131] In some example embodiments, the second device 120 may descramble the PUSCH transmission using a second identifier before decoding.

[0132] In some example embodiments, the second identifier may be associated with a PUSCH resource used for PUSCH transmission.

[0133] In some example embodiments, the second identifier can be shared across more than one user equipment configured with PUSCH resources.

[0134] In some example embodiments, descrambling using a second identifier may include: descrambling data transmitted via PUSCH using a second identifier.

[0135] In some example embodiments, data descrambling may include at least one of bit descrambling or modulation symbol descrambling.

[0136] In some example embodiments, the second identifier is used in the initialization of the pseudo-random generator used for descrambling.

[0137] In some example embodiments, the second device 120 may send at least one configuration of the second identifier to the first device.

[0138] In some example embodiments, the second device 120 may send at least one configuration of the first identifier to the first device.

[0139] In some example embodiments, the first identifier may be at least a portion of the following identifiers of the first device 110, which identify a dedicated channel scheduled for the first device 110.

[0140] In some example embodiments, the identifier of the first device 110 may include C-RNTI.

[0141] In some example embodiments, the second device 120 may send the configuration of the PUSCH resource to the first device.

[0142] In some example embodiments, the configuration of PUSCH resources may be sent via at least one of the following: RRC signaling and MAC signaling.

[0143] In some example embodiments, at least one of the RRC signaling and MAC signaling is specific to the first device.

[0144] In some example embodiments, the configuration of PUSCH resources may be associated with at least one of the following: FDRA, TDRA, DM-RS, and MCS.

[0145] In some example implementations, the configuration of PUSCH resources can be shared by more than one user equipment that has PUSCH resources configured.

[0146] In some example embodiments, PUSCH may include CB PUSCH.

[0147] In some example embodiments, a second device capable of performing any method 600 (e.g., Figure 1 The second device 120 may include components for performing corresponding operations of method 600 and / or any of the one or more example embodiments described herein. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The second device may be implemented as or included in Figure 1 In the second device 120.

[0148] Figure 7 A flowchart of an example method 700 implemented at a first device according to some other example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 700 is described by the angle of the first device 110 in the middle.

[0149] At frame 710, the first device 110 obtains a first identifier that identifies the first device 110.

[0150] At frame 720, the first device 110 performs a PUSCH transfer toward the second device 120 on the PUSCH resource.

[0151] At frame 730, the first device 110 sends an instruction for the first identifier to the second device 120 via layer 1 (L1) control signaling.

[0152] In some example embodiments, the first device 110 may obtain a second identifier and may use the second identifier to scramble the PUSCH transmission after encoding.

[0153] In some example implementations, the second identifier may be associated with a PUSCH resource.

[0154] In some example embodiments, the second identifier may be shared across more than one user equipment configured with PUSCH resources.

[0155] In some example embodiments, scrambling may include scrambling the data transmitted by PUSCH.

[0156] In some example embodiments, data scrambling may include at least one of bit scrambling and modulation symbol scrambling.

[0157] In some example embodiments, the second identifier may be used in the initialization of the pseudo-random generator used for scrambling.

[0158] In some example embodiments, the first device 110 may receive at least one configuration of the second identifier from the second device 120.

[0159] In some example embodiments, the first device 110 may receive at least one configuration of the first identifier from the second device 120.

[0160] In some example embodiments, the first identifier may be at least a portion of the following identifiers of the first device 110, which identify a dedicated channel scheduled for the first device 110.

[0161] In some example embodiments, the identifier of the first device 110 may include C-RNTI.

[0162] In some example embodiments, the indication of the first identifier may be sent via at least a portion of the HARQ-ACK bits in the PUSCH transmission.

[0163] In some example embodiments, the first identifier may be concatenated with at least one bit used for HARQ-ACK to form HARQ-ACK bits.

[0164] In some example embodiments, the first identifier and at least one bit used for HARQ-ACK can be encoded separately.

[0165] In some example embodiments, the first device 110 may receive the configuration of the PUSCH resources from the second device.

[0166] In some example embodiments, the configuration of PUSCH resources may be received via at least one of the following: RRC signaling and MAC signaling.

[0167] In some example embodiments, at least one of the RRC signaling and MAC signaling may be specific to the first device.

[0168] In some example embodiments, the configuration of PUSCH resources may be associated with at least one of the following: FDRA, TDRA, DM-RS, and MCS.

[0169] In some example implementations, the configuration of PUSCH resources can be shared by more than one user equipment that has PUSCH resources configured.

[0170] In some example embodiments, PUSCH may include CB PUSCH.

[0171] In some example embodiments, a first device capable of performing method 700 (e.g., Figure 1 The first device 110 may include components for performing corresponding operations of method 700 and / or any of the one or more example embodiments described herein. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In the first device 110.

[0172] Figure 8 A flowchart of an example method 800 implemented at a second device according to some other example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 800 is described by the angle of the second device 120 in the middle.

[0173] At box 810, the second device 120 receives PUSCH transmissions from the first device on the PUSCH resource.

[0174] At frame 820, the second device 120 receives an instruction for a first identifier from the first device via L1 control signaling, wherein the first identifier identifies the first device.

[0175] In some example embodiments, the second device 120 may descramble the PUSCH transmission using a second identifier before decoding.

[0176] In some example implementations, the second identifier may be associated with a PUSCH resource.

[0177] In some example embodiments, the second identifier can be shared across more than one user equipment configured with PUSCH resources.

[0178] In some example embodiments, descrambling may include descrambling the data transmitted in the PUSCH transmission.

[0179] In some example embodiments, data descrambling may include at least one of bit descrambling and modulation symbol descrambling.

[0180] In some example embodiments, the second identifier may be used in the initialization of the pseudo-random generator used for descrambling.

[0181] In some example embodiments, the second device 120 may send at least one configuration of the second identifier to the first device.

[0182] In some example embodiments, the second device 120 may send at least one configuration of the first identifier to the first device.

[0183] In some example embodiments, the first identifier may be at least a portion of the identifier of the first device that identifies a dedicated channel scheduled for the first device.

[0184] In some example embodiments, the identifier of the first device 110 may include C-RNTI.

[0185] In some example embodiments, the indication of the first identifier may be sent via at least a portion of the HARQ-ACK bits in the PUSCH transmission.

[0186] In some example embodiments, the first identifier may be concatenated with at least one bit used for HARQ-ACK to form HARQ-ACK bits.

[0187] In some example embodiments, the first identifier and at least one bit used for HARQ-ACK can be encoded separately.

[0188] In some example embodiments, the second device 120 may send the configuration of the PUSCH resource to the first device.

[0189] In some example embodiments, the configuration of PUSCH resources may be sent via at least one of the following: RRC signaling and MAC signaling.

[0190] In some example embodiments, at least one of the RRC signaling and MAC signaling may be specific to the first device 110.

[0191] In some example embodiments, the configuration of PUSCH resources may be associated with at least one of the following: FDRA, TDRA, DM-RS, and MCS.

[0192] In some example implementations, the configuration of PUSCH resources can be shared by more than one user equipment that has PUSCH resources configured.

[0193] In some example embodiments, the PUSCH may include a CB PUSCH.

[0194] In some example embodiments, any method 800 can be executed (e.g., Figure 1 The second device (120) may include components for performing corresponding operations of method 800 and / or any of the one or more example embodiments described herein. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 1 The second device 120 in the middle.

[0195] Figure 9 This is a simplified block diagram of a device 900 suitable for implementing an example embodiment of the present disclosure. The device 900 can be provided to implement a communication device, for example, such as... Figure 1 The user equipment 110 or network equipment 120 shown. As shown, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processors 910, and one or more communication modules 940 coupled to the processors 910.

[0196] Communication module 940 is used for bidirectional communication. Communication module 940 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface necessary for communication with other network elements. In some example embodiments, communication module 940 may include at least one antenna.

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

[0198] Memory 920 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) 924, electrically programmable read-only memory (EPROM), flash memory, hard disk, miniature optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 922 and other volatile memories that will not be maintained during power outages.

[0199] Computer program 930 includes computer-executable instructions that are executed by an associated processor 910. The instructions of program 930 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 930 may be stored in memory (e.g., ROM 924). Processor 910 can perform any suitable actions and processes by loading program 930 into RAM 922.

[0200] The exemplary embodiments of this disclosure can be implemented by program 930, thereby enabling device 900 to perform as described in the reference. Figures 2 to 8 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or a combination of software and hardware.

[0201] In some example embodiments, program 930 may be tangibly included in a computer-readable medium, which may be included in device 900 (such as in memory 920) or other storage device accessible to device 900. Device 900 may load program 930 from the computer-readable medium into RAM 922 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation of the medium itself (i.e., tangible, not tactile) and not a limitation of data storage persistence (e.g., RAM vs. ROM).

[0202] Figure 10 An example of a computer-readable medium 1000 is shown, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 1000 has a program 930 stored thereon.

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

[0204] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions, such as those included in a program module, which execute in a device on a target physical or virtual processor to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. The functionality of the program module can be combined or split as needed among program modules in various embodiments. The machine-executable instructions for the program module can execute within a local device or a distributed device. In a distributed device, the program module can reside on both local storage media and remote storage media.

[0205] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The 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 enables the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0206] In the context of this disclosure, computer program code or related data may be carried on 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.

[0207] 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 thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0208] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or requiring that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to certain embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0209] 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 and actions described above are disclosed as exemplary forms for implementing the claims.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first device to at least: Obtain a first identifier that identifies the first device; Before encoding, at least one of the cyclic redundancy check (CRC) and data bits transmitted on the Physical Uplink Shared Channel (PUSCH) is scrambled using the first identifier; as well as Perform the PUSCH transfer toward the second device on the PUSCH resource.

2. The first apparatus according to claim 1, wherein when the CRC is scrambled, the bit length of the first identifier depends on the bit length of the CRC transmitted by the PUSCH.

3. The first apparatus according to claim 1 or 2, wherein when the CRC is scrambled, the scrambling vector for CRC scrambling is formed based on the first identifier, and the bit length based on the first identifier is less than the bit length of the CRC, and the dimension of the scrambling vector is determined according to the bit length of the CRC transmitted by the PUSCH.

4. The first apparatus of claim 3, wherein the scrambling vector is filled with the first identifier and at least one virtual bit.

5. The first apparatus of claim 3, wherein the first identifier is repeated cyclically to form the scrambling vector.

6. The first apparatus according to claim 1 or 2, wherein when scrambling the CRC, a portion of the first identifier is used for scrambling the CRC of the PUSCH transmission, based on the fact that the bit length of the first identifier is greater than the bit length of the CRC of the PUSCH transmission.

7. The first apparatus of claim 6, wherein the portion of the first identifier comprises at least one of the following: The most significant bit (MSB) of the first identifier, and The least significant bit (LSB) of the first identifier.

8. The first apparatus according to claim 1 or 2, wherein when the CRC is scrambled, the CRC scrambling includes CRC scrambling of at least one of the transport block and code block of the PUSCH transmission.

9. The first apparatus according to claim 1 or 2, wherein the instructions, when executed by the at least one processor, further cause the first apparatus to: The PUSCH transmission is scrambled using a second identifier after encoding.

10. The first apparatus of claim 9, wherein the second identifier is associated with the PUSCH resource for the PUSCH transmission.

11. The first apparatus of claim 9, wherein the second identifier is shared by more than one user equipment configured with the PUSCH resource.

12. The first apparatus of claim 9, wherein the scrambling using the second identifier comprises: The data transmitted by the PUSCH is scrambled using the second identifier.

13. The first apparatus of claim 12, wherein the data scrambling includes at least one of bit scrambling and modulation symbol scrambling.

14. The first apparatus of claim 9, wherein the second identifier is used in the initialization of the pseudo-random generator for scrambling.

15. The first apparatus of claim 9, wherein the instructions, when executed by the at least one processor, further cause the first apparatus to: Receive at least one configuration of the second identifier from the second device.

16. The first apparatus according to claim 1 or 2, wherein the instructions, when executed by the at least one processor, further cause the first apparatus to: Receive at least one configuration of the first identifier from the second device.

17. The first apparatus according to claim 1 or 2, wherein the first identifier is at least a portion of a set of identifiers of the first apparatus that identify a dedicated channel scheduled for the first apparatus.

18. The first apparatus of claim 17, wherein the identifier of the first apparatus includes a Cell Radio Network Temporary Identifier (C-RNTI).

19. The first apparatus according to claim 1 or 2, wherein the instructions, when executed by the at least one processor, further cause the first apparatus to: Receive the configuration of the PUSCH resources from the second device.

20. The first apparatus of claim 19, wherein the configuration of the PUSCH resource is received via at least one of the following: Radio Resource Control (RRC) signaling, and Media Access Control (MAC) signaling.

21. The first apparatus of claim 20, wherein at least one of the RRC signaling and the MAC signaling is specific to the first apparatus.

22. The first apparatus of claim 19, wherein the configuration of the PUSCH resource is related to at least one of the following: Frequency Domain Resource Allocation (FDRA) Time-Domain Resource Allocation (TDRA) Demodulation reference signal (DM-RS), and Modulation and coding scheme (MCS).

23. The first apparatus of claim 19, wherein the configuration of the PUSCH resources is shared by more than one user equipment configured with the PUSCH resources.

24. The first apparatus according to claim 1 or 2, wherein the PUSCH includes a competition-based PUSCH.

25. A second means for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the second device to at least: Receive PUSCH transmissions from the first device on the Physical Uplink Shared Channel (PUSCH) resource; and After decoding, at least one of the cyclic redundancy check (CRC) and data bits of the PUSCH transmission is descrambled using at least the first identifier that identifies the first device.

26. The second apparatus of claim 25, wherein when the CRC is descrambled, the bit length of the first identifier depends on the bit length of the CRC transmitted by the PUSCH.

27. The second apparatus according to claim 25 or 26, wherein when the CRC is descrambled, the descrambling vector for descrambling the CRC is formed based on the first identifier, and the bit length based on the first identifier is less than the bit length of the CRC, and the dimension of the descrambling vector is determined according to the bit length of the CRC transmitted by the PUSCH.

28. The second apparatus of claim 27, wherein the descrambling vector is filled with the first identifier and at least one virtual bit.

29. The second apparatus of claim 27, wherein the first identifier is repeated cyclically to form the descrambling vector.

30. The second apparatus according to claim 25 or 26, wherein when the CRC is descrambled, a portion of the first identifier is used for descrambling the CRC of the PUSCH transmission, based on the fact that the bit length of the first identifier is greater than the bit length of the CRC transmitted by the PUSCH.

31. The second apparatus of claim 30, wherein the portion of the first identifier comprises at least one of the following: The most significant bit (MSB) of the first identifier, and The least significant bit (LSB) of the first identifier.

32. The second apparatus according to claim 25 or 26, wherein the CRC descrambling includes CRC descrambling of at least one of the transport block and code block of the PUSCH transmission.

33. The second apparatus according to claim 25 or 26, wherein the instructions, when executed by the at least one processor, further cause the second apparatus to: Before decoding, the PUSCH transmission is descrambled using a second identifier.

34. The second apparatus of claim 33, wherein the second identifier is associated with the PUSCH resource for the PUSCH transmission.

35. The second apparatus of claim 33, wherein the second identifier is shared by more than one user equipment configured with the PUSCH resource.

36. The second apparatus of claim 33, wherein the descrambling using the second identifier comprises: The data transmitted by the PUSCH is descrambled using the second identifier.

37. The second apparatus according to claim 36, wherein the data descrambling includes at least one of bit descrambling or modulation symbol descrambling.

38. The second apparatus of claim 33, wherein the second identifier is used in the initialization of the pseudo-random generator for the descrambling.

39. The second apparatus of claim 33, wherein the instructions, when executed by the at least one processor, further cause the second apparatus to: Send at least one configuration of the second identifier to the first device.

40. The second apparatus according to claim 25 or 26, wherein the instructions, when executed by the at least one processor, further cause the second apparatus to: Send at least one configuration of the first identifier to the first device.

41. The second apparatus according to claim 25 or 26, wherein the first identifier is at least a portion of a following identifier of the first apparatus, the identifier identifying a dedicated channel scheduled for the first apparatus.

42. The second apparatus of claim 41, wherein the identifier of the first apparatus includes a Cell Radio Network Temporary Identifier (C-RNTI).

43. The second apparatus according to claim 25 or 26, wherein the instructions, when executed by the at least one processor, further cause the second apparatus to: The configuration of the PUSCH resource is sent to the first device.

44. The second apparatus of claim 43, wherein the configuration of the PUSCH resource is sent via at least one of the following: Radio Resource Control (RRC) signaling, and Media Access Control (MAC) signaling.

45. The second apparatus of claim 44, wherein at least one of the RRC signaling and the MAC signaling is specific to the first apparatus.

46. ​​The second apparatus of claim 43, wherein the configuration of the PUSCH resources is related to at least one of the following: Frequency Domain Resource Allocation (FDRA) Time-Domain Resource Allocation (TDRA) Demodulation reference signal (DM-RS), and Modulation and coding scheme (MCS).

47. The second apparatus of claim 43, wherein the configuration of the PUSCH resources is shared by more than one user equipment configured with the PUSCH resources.

48. The second apparatus according to claim 25 or 26, wherein the PUSCH includes a competition-based PUSCH.

49. A method for communication, comprising: Obtain the first identifier that identifies the first device; Before encoding, at least one of the cyclic redundancy check (CRC) and data bits transmitted on the Physical Uplink Shared Channel (PUSCH) is scrambled using the first identifier; as well as Perform the PUSCH transfer toward the second device on the PUSCH resource.

50. A method for communication, comprising: Receive PUSCH transmissions from the first device on the Physical Uplink Shared Channel (PUSCH) resource; as well as After decoding, at least one of the cyclic redundancy check (CRC) and data bits of the PUSCH transmission is descrambled using at least the first identifier that identifies the first device.

51. A first means for communication, comprising: Components for obtaining a first identifier that identifies the first device; A component for scrambling at least one of the cyclic redundancy check (CRC) and data bits transmitted on the Physical Uplink Shared Channel (PUSCH) using the first identifier before encoding; as well as A component for performing the PUSCH transfer toward the second device on the PUSCH resource.

52. A second means for communication, comprising: A component for receiving PUSCH transmissions from a first device on Physical Uplink Shared Channel (PUSCH) resources; as well as A component for descrambling at least one of the cyclic redundancy check (CRC) and data bits of the PUSCH transmission after decoding, using at least a first identifier that identifies the first device.

53. A computer-readable medium comprising instructions stored thereon, said instructions, when executed by a first means, causing the first means to perform at least the following: Obtain a first identifier that identifies the first device; Before encoding, at least one of the Cyclic Redundancy Check (CRC) and data bits transmitted via the Physical Uplink Shared Channel (PUSCH) is scrambled using the first identifier; and Perform the PUSCH transfer toward the second device on the PUSCH resource.

54. A computer-readable medium comprising instructions stored thereon, said instructions, when executed by a second means, causing the second means to perform at least the following: Receive PUSCH transmissions from the first device on the Physical Uplink Shared Channel (PUSCH) resource; and After decoding, at least one of the cyclic redundancy check (CRC) and data bits of the PUSCH transmission is descrambled using at least the first identifier that identifies the first device.

Images