Signaling design for OCC information display

A signaling design using MAC elements and RNTI in NTN networks dynamically manages OCC operations for UEs, addressing capacity and throughput issues by optimizing UE resource utilization.

KR1020260161584APending Publication Date: 2026-11-09APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
KR1020267032872
Authority / Receiving Office
KR · KR
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-04-04
Publication Date
2026-11-09

AI Technical Summary

Technical Problem

Existing NTN networks lack a mechanism to organize UEs for efficient orthogonal cover code (OCC) operations on physical uplink shared channels (PUSCH) to enhance network capacity and data throughput.

Method used

Implementing a signaling design that uses Media Access Control (MAC) elements and/or new Radio Network Temporary Identifiers (RNTI) to signal OCC configurations and parameters to UEs, enabling dynamic activation and deactivation of OCC operations based on predefined timing conditions.

Benefits of technology

Enhances network capacity and data throughput in NTN networks by optimizing UE operations using OCCs, ensuring efficient resource utilization and network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure PCT00001_ABST
    Figure PCT00001_ABST
Patent Text Reader

Abstract

A device configured to process, based on signals received from a network, an indication that the network supports orthogonal cover code (OCC) operation on a physical uplink shared channel (PUSCH), to generate a UE capability report including an indication of the OCC operation supported by the device for transmission to the network, and to process a Media Access Control Control Element (MAC CE) that enables the OCC operation for PUSCH based on signals received from the network, wherein the MAC CE includes an indication of OCC parameters for the OCC operation for PUSCH.
Need to check novelty before this filing date? Find Prior Art

Description

Background Technology

[0001] User equipment (UE) can establish a connection to a public land mobile network (PLMN) operating at least one of a number of different networks or types of networks, for example, a radio access network (RAN). A non-terrestrial network (NTN) is a network that utilizes non-terrestrial components, for example, one or more satellites, to provide the UE with access to the PLMN.

[0002] Satellites or other components of an NTN network can have large coverage areas, such as hundreds, thousands, or millions of square kilometers. Such extensive coverage areas can include a large number of UEs. Because a large number of UEs may exist, it can be beneficial to increase the network's data throughput in the uplink (UL) (e.g., Physical Uplink Shared Channel (PUSCH)) to increase network capacity. One way to increase capacity could be for UEs to use Orthogonal Cover Codes (OCCs) in the UL. An OCC is a method in which multiple UEs share the same time and frequency resources in the UL. However, there is currently no method to organize UEs within an NTN network according to OCCs.

[0003] Some exemplary embodiments relate to a device having a processing circuit, the processing circuit being configured to process, based on signals received from a network, an indication that the network supports orthogonal cover code (OCC) operation on a physical uplink shared channel (PUSCH), to generate a UE capability report including an indication of an OCC operation supported by the device for transmission to the network, and to process a Medium Access Control Control Element (MAC CE) that enables an OCC operation for PUSCH based on signals received from the network, wherein the MAC CE includes an indication of OCC parameters for an OCC operation for PUSCH.

[0004] Other exemplary embodiments relate to a device having a processing circuit, the processing circuit being configured to process a UE capability report including an OCC operation supported by the UE based on signals received from the UE, so as to generate an indication that the network supports an orthogonal cover code (OCC) operation on a physical uplink shared channel (PUSCH) for transmission to a user device (UE), and to generate a media access control element (MAC CE) that enables an OCC operation for PUSCH for transmission to the UE, wherein the MAC CE includes an indication of OCC parameters for an OCC operation for PUSCH.

[0005] Other exemplary embodiments relate to a device having a processing circuit, the processing circuit being configured to process, based on signals received from a network, an indication that the network supports orthogonal cover code (OCC) operation on a physical uplink shared channel (PUSCH), to generate a UE capability report including an indication of an OCC operation supported by the device for transmission to the network, and to process Downlink Control Information (DCI) having a scrambled cyclic redundancy check (CRC) using Radio Network Temporary Identification (RNTI) related to the OCC operation for PUSCH based on signals received from the network, wherein one or more fields in the DCI include indications of OCC parameters for the OCC operation for PUSCH.

[0006] Additional exemplary embodiments relate to a device having a processing circuit, the processing circuit being configured to process a UE capability report including an OCC operation supported by the UE based on signals received from the UE, so as to generate an indication that the network supports an OCC operation on a physical uplink shared channel (PUSCH) for transmission to a user device (UE), and to generate downlink control information (DCI) having a scrambled circular redundancy check (CRC) using radio network temporary identification information (RNTI) related to the OCC operation for PUSCH for transmission to the UE, wherein one or more fields in the DCI include indications of OCC parameters for the OCC operation for PUSCH. Brief explanation of the drawing

[0007] FIG. 1 illustrates an exemplary network arrangement according to various exemplary embodiments. FIG. 2 illustrates an exemplary user equipment (UE) according to various exemplary embodiments. FIG. 3 illustrates an exemplary base station according to various exemplary embodiments. FIG. 4 illustrates an exemplary non-ground network (NTN) architecture according to various exemplary embodiments. FIG. 5 illustrates an exemplary method for signaling OCC information for a dynamic grant (DG) and enabling OCC operations using a Media Access Control Element (MAC CE), according to various exemplary embodiments. FIG. 6 illustrates a timing diagram for activating OCC operations based on the timing of receiving a UL-approved DCI according to various exemplary embodiments. FIG. 7 illustrates a timing diagram for activating OCC operations based on the timing of PUSCH according to various exemplary embodiments. FIG. 8 illustrates an exemplary MAC CE for OCC operations according to various exemplary embodiments. FIG. 9 illustrates an exemplary MAC CE for OCC operations that do not have a radio resource control (RRC) configuration, according to various exemplary embodiments. FIG. 10 illustrates an exemplary method for signaling OCC information for dynamic approval (DG) and enabling OCC operations using a new radio network temporary identifier (RNTI), according to various exemplary embodiments. Specific details for implementing the invention

[0008] Exemplary embodiments may be further understood by referring to the following description and the associated accompanying drawings, wherein similar elements are provided with the same reference numerals. The exemplary embodiments relate to a signaling design for displaying Orthogonal Cover Code (OCC) information for Dynamic Acceptance (DG) on a User Equipment (UE).

[0009] Exemplary embodiments are described in relation to User Equipment (UE). However, references to the UE are provided for exemplary purposes only. Exemplary embodiments may be utilized with any electronic component capable of establishing a connection to a network and consist of hardware, software, and / or firmware to exchange information and data with the network. Accordingly, the UE as described herein is used to represent any suitable electronic component.

[0010] Exemplary embodiments are also described in relation to 5G New Radio (NR) networks. However, references to 5G NR networks are provided only for exemplary purposes. Exemplary embodiments may be utilized with any network (e.g., 5G-advanced networks, 6G networks, etc.) capable of establishing a connection with a UE and exchanging information and data with the UE.

[0011] Exemplary embodiments are further described in relation to a 5G NR network integrated with a non-terrestrial network (NTN) utilizing one or more satellites to provide UE access to a 5G NR radio access network (RAN). The satellite-based NTN may be deployed by an aerial terrestrial mobile network (PLMN) and may be further integrated with the terrestrial network (TN) of the PLMN. Throughout this specification, the non-terrestrial component is generally described as a satellite. However, any reference to a satellite is for illustrative purposes only, and exemplary embodiments may be applied to other types of non-terrestrial components, such as airplanes, unmanned aerial vehicles (UAVs), etc.

[0012] Exemplary embodiments relate to signaling designs for displaying OCC information for DG to the UE. In some exemplary embodiments, OCC information is signaled to the UE using MAC CE. In other exemplary embodiments, OCC information is signaled to the UE using DCI scrambled by the new RNTI. Each of these exemplary embodiments is described in more detail below.

[0013] FIG. 1 illustrates an exemplary network array (100) according to various exemplary embodiments. The exemplary network array (100) includes a UE (110). The UE (110) may be any type of electronic component configured to communicate over a network, such as mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (IoT) devices, etc. An actual network array may include any number of UEs being used by any number of users. Thus, an example of a single UE (110) is provided only for exemplary purposes.

[0014] The UE (110) may be configured to communicate with one or more networks. In an example of a network array (100), the network with which the UE (110) can communicate wirelessly is a 5G NR radio access network (RAN) (120). However, the UE (110) may also communicate with other types of networks (e.g., 5G cloud RAN, next-generation RAN (NG-RAN), Long Term Evolution (RAN), legacy cellular network, WLAN, etc.), and the UE (110) may also communicate with networks via a wired connection. In relation to exemplary embodiments, the UE (110) may establish a connection with the 5G NR RAN (120). Thus, the UE (110) may have a 5G NR chipset for communicating with the NR RAN (120).

[0015] The 5G NR RAN (120) may be part of a terrestrial mobile network (PLMN) that can be deployed by a network carrier (e.g., Verizon, AT&T, T-Mobile, etc.). The 5G NR RAN (120) may include, for example, cells or base stations (Node Bs, eNode Bs, HeNBs, eNBs, gNBs, gNode Bs, macrocells, microcells, small cells, femtocells, etc.) configured to transmit and receive traffic from UEs equipped with a suitable cellular chip set.

[0016] In the network array (100), the 5G NR RAN (120) includes a base station (e.g., gNB (120A)) that may be in a terrestrial network (TN) deployment or a non-terrestrial network (NTN) deployment. For example, a satellite-based system may be integrated with the 5G NR RAN (120) to provide network access to a UE (110) in an NTN deployment, and the base station may, in some cases, be located on a non-terrestrial component, e.g., a satellite. An exemplary NTN network will be described in more detail below with reference to FIG. 4.

[0017] Returning to the network array (100) of FIG. 1, the gNB (120A) may include one or more communication interfaces for exchanging data and / or information with the UE (110), the corresponding 5G NR RAN (120), the cellular core network (130), the Internet (140), etc.

[0018] The UE (110) can be connected to the 5G NR-RAN (120) via the gNB (120A). Any association procedure may be performed to enable the UE (110) to be connected to the 5G NR-RAN (120). For example, as discussed above, the 5G NR-RAN (120) may be associated with a specific cellular provider to which the UE (110) and / or his / her user has contract and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR-RAN (120), the UE (110) may transmit corresponding credential information to be associated with the 5G NR-RAN (120). More specifically, the UE (110) may be associated with a specific cell (e.g., gNB (120A)). However, as mentioned above, the reference to 5G NR-RAN (120) is for exemplary purposes only, and any suitable type of RAN may be used.

[0019] In addition to the 5G NR RAN (120), the network array (100) also includes a cellular core network (130), the Internet (140), an IMS (IP Multimedia Subsystem) (150), and a network services backbone (160). The cellular core network (130) can be considered as an interconnected set of components that manage the operation and traffic of the cellular network. The cellular core network (130) also manages traffic flowing between the cellular network and the Internet (140).

[0020] The IMS (150) can generally be described as an architecture for delivering multimedia services to the UE (110) using IP protocols. The IMS (150) can communicate with the cellular core network (130) and the Internet (140) to provide multimedia services to the UE (110). The network service backbone (160) communicates directly or indirectly with the Internet (140) and the cellular core network (130). The network service backbone (160) can generally be described as a set of components (e.g., servers, network storage arrays, etc.) that implement a set of services that can be used to extend the capabilities of the UE (110) communicating with various networks.

[0021] FIG. 2 illustrates an exemplary UE (110) according to various exemplary embodiments. The UE (110) will be described in relation to the network array (100) of FIG. 1. The UE (110) may include a processor (205), a memory array (210), a display device (215), an input / output (I / O) device (220), a transceiver (225), and other components (230). The other components (230) may include, for example, an audio input device, an audio output device, a power supply, a data capture device, ports for electrically connecting the UE (110) to other electronic devices, etc.

[0022] The processor (205) may be configured to execute multiple engines of the UE (110). For example, the engines may include an OCC engine (235). The OCC engine (235) may perform various operations related to applying OCC operations to PUSCH transmissions to the UE (110). To provide some general examples, the OCC engine (235) may perform operations such as, but not limited to, reporting OCC capabilities to the network, enabling / disabling OCC operations for PUSCH transmissions, and determining when to enable and disable OCC operations. These and other operations are described in more detail below.

[0023] The engine (235) mentioned above, which is an application (e.g., a program) executed by the processor (205), is provided only for exemplary purposes. Functions associated with the engine (235) may also be represented as a separate integrated component of the UE (110), or as a modular component coupled to the UE (110), such as an integrated circuit with or without firmware. For example, the integrated circuit may include an input circuit for receiving signals and a processing circuit for processing signals and other information. The engine may also be implemented as a single application or as separate applications. Additionally, in some UEs, the functions described for the processor (205) are divided among two or more processors, such as a baseband processor and an application processor. Exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0024] The memory array (210) may be a hardware component configured to store data related to operations performed by the UE (110). The display device (215) may be a hardware component configured to display data to the user, while the I / O device (220) may be a hardware component that enables the user to input inputs. The display device (215) and the I / O device (220) may be separate components or may be integrated together, such as a touchscreen.

[0025] The transceiver (225) may be a hardware component configured to establish a connection with a 5G NR-RAN (120), an LTE-RAN (not shown), a legacy RAN (not shown), a WLAN (not shown), etc. Accordingly, the transceiver (225) may operate on various different frequencies or channels (e.g., a set of consecutive frequencies). The transceiver (225) includes a circuit configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded as information implementing any of the methods described herein. A processor (205) may be operably coupled to the transceiver (225) and configured to receive signals from the transceiver (225) and / or transmit them thereto. The processor (205) may be configured to encode and / or decode signals (e.g., signaling from a base station of a network) to implement any of the methods described in this specification.

[0026] FIG. 3 illustrates an exemplary base station (300) according to various exemplary embodiments. The base station (300) may represent a gNB (120A) or any other type of access node that enables the UE (110) to establish a connection and manage network operations.

[0027] The base station (300) may include a processor (305), a memory array (310), an input / output (I / O) device (315), a transceiver (320), and other components (325). The other components (325) may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports for electrically connecting the base station (300) to other electronic devices, and / or power supplies, TxRUs, transceiver chains, antenna elements, antenna panels, etc.

[0028] The processor (305) may be configured to execute a plurality of engines for the base station (300). For example, the engines may include an OCC configuration engine (330). The OCC configuration engine (330) may perform various operations related to configuring the UE to apply OCC operations to PUSCH transmissions. To provide some general examples, the OCC configuration engine (330) may perform operations such as, but not limited to, signaling network support for OCC operations, receiving OCC capabilities from the UE, configuring OCC parameters for UE OCC operations in PUSCH, and enabling / disabling OCC operations for PUSCH transmissions. These and other operations are described in more detail below.

[0029] It is merely an example that the aforementioned engine (330) is an application (e.g., a program) executed by the processor (305). The function associated with the engine (330) may also be represented as a separate integrated component of the base station (300), or as a modular component coupled to the base station (300), such as an integrated circuit with or without firmware. For example, the integrated circuit may include an input circuit for receiving signals and a processing circuit for processing signals and other information. Additionally, in some base stations, the function described for the processor (305) is divided among a plurality of processors (e.g., a baseband processor, an application processor, etc.). Exemplary embodiments may be implemented in any of these or other configurations of the base station.

[0030] The memory array (310) may be a hardware component configured to store data related to operations performed by the base station (300). The I / O device (315) may be a hardware component or ports that enable a user to interact with the base station (300).

[0031] A transceiver (320) may be a hardware component configured to exchange data with a UE (110) and any other UE within a network array (100). The transceiver (320) may operate on various different frequencies or channels (e.g., a set of consecutive frequencies). Accordingly, the transceiver (320) may include one or more components to enable data exchange with various networks and UEs. The transceiver (320) includes a circuit configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded as information that implements any of the methods described herein. A processor (305) may be operably coupled to the transceiver (320) and configured to receive signals from the transceiver (320) and / or transmit them thereto. The processor (305) may be configured to encode and / or decode signals (e.g., signaling from the UE) to implement any of the methods described in this specification.

[0032] FIG. 4 illustrates an exemplary non-ground network (NTN) architecture (400) according to various exemplary embodiments. The NTN may be any network that uses non-ground components, such as satellites, airplanes, unmanned aerial vehicles (UAVs), etc., to provide network services to user terminals.

[0033] The NTN architecture (400) represents a network array including one or more satellites, which in this example illustrates two satellites (410, 420) integrated with a radio access network (RAN) (440). The RAN (440) may be, for example, the 5G NR RAN (120) described above in relation to FIG. 1. The NTN architecture (400) includes a gateway (430) that connects the ground network (440) to the NTN components. In the NTN architecture (400) of FIG. 4, the gateway (430) and the satellites (410, 420) communicate via feeder links. In some NTN deployments, the satellites may be served simultaneously by multiple gateways.

[0034] Satellites (410, 420) provide network services to the UE (110) via a service link (not shown). The satellites (410, 420) may implement a transparent payload or a regenerated payload. A transparent payload refers to an arrangement in which the satellites (410, 420) receive signals and transmit an amplified version of the signal using frequency conversion. For example, the satellite (410) may receive uplink communications from the UE (110) at service link frequencies and transmit an amplified version of the signal to the gateway (430) at feeder link frequencies, or receive downlink communications through the gateway (430) at feeder link frequencies and transmit an amplified version of the signal to the UE (110) at service link frequencies. The replay payload refers to an arrangement in which satellites (410, 420) act as a distributed unit (DU) or base station (e.g., gNB), where the received signals are replayed using signal processing techniques (e.g., demodulation, decoding, switching, encoding, modulation, etc.) before being retransmitted.

[0035] Referring to FIG. 1, in a replay payload array, the gNB (120A) may be positioned on an aerial component, e.g., the satellites (410 and / or 420) of FIG. 4. In a transparent payload array, the gNB (120A) may be positioned on the ground, and the satellites (410, 420) are used to mirror signals between the gNB (120A) and the UE (110) as described above. In either case, in exemplary embodiments, the satellites (410, 420) may transmit signals containing the same PCI as described in more detail below.

[0036] The exemplary NTN architecture (400) illustrated in FIG. 4 is not intended to limit exemplary embodiments in any way. NTNs may be integrated with 5G NR RAN and / or other networks in any of the various ways. For example, a typical satellite-based NTN may include a low earth orbit (LEO) constellation comprising an array of satellites and gateways having extensive interconnectivity through ground-to-ground station (G2G) links, satellite-to-satellite (S2S) links, ground-to-satellite (G2S) links, and satellite-to-ground (S2G) links. Other types of satellite-based NTNs may include geostationary-orbiting (GEO) satellites or medium-earth-orbiting (MEO) satellites.

[0037] Different types of NTNs each have their own strengths and weaknesses and can be deployed in various scenarios depending on the goal to be achieved, such as extensive coverage over a wide area, concentrated coverage in an urban environment or along a high-traffic route. Accordingly, the NTN architecture (400) described in FIG. 4 is provided only for exemplary purposes.

[0038] As described above, one way to increase throughput at ULs on PDSCH in NTN networks may be for UEs to use OCCs when transmitting data. However, there is currently no mechanism for the network to signal OCC configurations to UEs. The following provides some exemplary embodiments of a signaling method for signaling OCC configuration information to UEs in Dynamic Acknowledgment (DG). In some aspects of the exemplary embodiments, OCC activation is performed using Media Access Control (MAC) signaling. In other aspects of the exemplary embodiments, OCC activation is performed using a New Radio Network Temporary Identifier (RNTI).

[0039] FIG. 5 illustrates an exemplary method (500) for signaling OCC information for dynamic acknowledgment (DG) and enabling OCC operations using a media access control control element (MAC CE), according to various exemplary embodiments. The method is performed between a network (e.g., 5G NR RAN (120)) and a UE (e.g., UE (110)).

[0040] In 510, the UE (110) receives the network configuration of the OCC based on PUSCH transmissions. The configuration may be a cell-specific configuration returned from a System Information Block (SIB). The SIB used to return the network configuration may be, for example, SIB1 (e.g., a SIB containing PUSCH information), SIB19 (e.g., a SIB containing NTN information), a new SIB, etc.

[0041] The network configuration may include, for example, a set of supported OCC lengths (e.g., {2, 4, 8}), a set of supported OCC codes (e.g., Walsh or Discrete Fourier Transform (DFT) sequences), or any other information that can be used by the UE for the purpose of implementing OCC. Additionally, the network configuration may include an OCC sequence and an index for each supported OCC length and supported OCC code, for example, for OCC length = 2 and Walsh OCC codes, OCC sequence index 0 has

[0011] ; OCC sequence index 1 has [1-1], etc.

[0042] In 520, the UE (110) reports its capabilities of spreading OCC of PUSCH into the network in response to receiving a network configuration for OCC-based PUSCH transmissions. The UE capability report may include an indication of the UE's capability to apply OCC in PUSCH transmissions. The UE capability report may include an indication of OCC operations supported by the UE. These capabilities may include an indication of a subset(s) of OCC lengths supported by the UE, an indication of a subset(s) of OCC codes supported by the UE, etc.

[0043] In 530, the UE receives a radio resource configuration (RRC) of OCC parameters to be used for PUSCH transmissions, for example, the network may configure a specific configuration of OCC parameters based on network support parameters and UE capability reports. The contents of the RRC configuration may include OCC lengths, OCC codes, and / or OCC sequence indices corresponding to OCC lengths / codes. Some UEs may support multiple configurations. For example, the UE may receive OCC configuration #1 having an exemplary OCC configuration with an OCC length of 2, Walsh OCC codes, and OCC sequence index 1 = [1 - 1], and OCC configuration #2 having an exemplary OCC configuration with an OCC length of 4, DFT sequence OCC codes, and OCC sequence index 3 = [ + 1, + j, - 1, - j ].

[0044] As described in more detail below, in some exemplary embodiments, the UE (110) may not receive the RRC configuration.

[0045] In 540, the network may want to enable OCC operations for the UE (110) by transmitting the MAC control element (MAC CE) of the RRC configuration of the OCC-based PUSCH to the UE (110). The MAC CE may include, for example, an index of the RRC configuration to be enabled. If the UE is configured with multiple RRC configurations as described in the example above, only one RRC configuration may be enabled at a time.

[0046] When the UE (110) receives an activation command via MAC CE, the UE (110) can determine an activation time regarding when to activate the OCC operations. Exemplary embodiments provide various options for the activation time for the OCC operations.

[0047] In some exemplary embodiments, the activation time may be based on the timing when UL-approved downlink control information (DCI) is received on the physical downlink control channel. In these exemplary embodiments, if the UL-approved DCI is received after a predetermined time (e.g., X ms) after the last symbol of the PDSCH that returns the MAC CE enabling the OCC operations, the UE (110) will use the OCC operations for the corresponding PUSCH. Otherwise, the UE (110) will not use the OCC operations for the corresponding PUSCH. The value of X during the predetermined time may be set to any value, e.g., 1 ms, 3 ms, etc. These exemplary embodiments will be described with reference to FIG. 6.

[0048] FIG. 6 illustrates a timing diagram (600) for activating OCC operations based on the timing of receiving a UL-approved DCI according to various exemplary embodiments.

[0049] At time t0, the UE (110) is not performing OCC operations as exemplified in FIG. 6. The UE (110) receives a UL acknowledgment (610) via DCI 1. At time t1, the UE (110) receives a MAC CE (620) that enables OCC operations as described above with reference to 540 in FIG. 5. At time t2, the UE (110) receives a UL acknowledgment (630) via DCI 2. In the example of FIG. 6, the UL acknowledgment (630) is received by the UE (110) X ms (e.g., a predetermined time) after the MAC CE (620) is received.

[0050] As described above, if a UL acknowledgment DCI is received after a predetermined time (e.g., X ms) following the last symbol of the PDSCH that returns the MAC CE enabling OCC operations, the UE (110) will use OCC operations for the corresponding PUSCH. Otherwise, the UE (110) will not use OCC operations for the corresponding PUSCH. In the example of FIG. 6, the UL acknowledgment (610) is received before the MAC CE (620) that enables OCC operations. Therefore, for the PUSCH (640) corresponding to the UL acknowledgment (610), the UE does not use OCC operations. However, as illustrated in FIG. 6, the UL acknowledgment (630) is received after X ms following the MAC CE (620) that enables OCC operations. Therefore, for the PUSCH (650) corresponding to the UL acknowledgment (630), the UE uses OCC operations.

[0051] In other exemplary embodiments, the activation time may be based on the timing of the PUSCH. In these exemplary embodiments, if the PUSCH transmission occurs after a predetermined time (Y ms) following the last symbol of the MAC CE acknowledgment (ACK) that activates the OCC operations, the PUSCH will use the OCC operations regardless of when the UL acknowledgment PDCCH is received. Otherwise, the PUSCH will not use the OCC operations. The predetermined time (e.g., Y ms) may be fixed (e.g., 3 ms as defined by the standard) or configured in other signaling associated with the MAC CE or OCC operations. These exemplary embodiments will be described with reference to FIG. 7.

[0052] FIG. 7 illustrates a timing diagram (700) for activating OCC operations based on the timing of PUSCH according to various exemplary embodiments.

[0053] At time t0, the UE (110) is not performing OCC operations as exemplified in FIG. 7. The UE (110) receives a UL acknowledgment (710) via DCI 1. At time t1, the UE (110) receives a MAC CE (720) that enables OCC operations as described above with reference to 540 in FIG. 5. At time t2, the UE (110) transmits an ACK (730) acknowledging the reception of the MAC CE (720). At time t3, the UE (110) receives a UL acknowledgment (740) via DCI 2. In the example of FIG. 7, the PUSCH (750) corresponding to the UL acknowledgment (710) occurs at time t4, which is Y ms after the ACK (730). Therefore, even if the UL approval (710) is received prior to the MAC CE (720), the corresponding PUSCH (750) is executed by the UE (110) using OCC operations. Similarly, the PUSCH (760) corresponding to the UL approval (740) occurring at time t5 is also executed using OCC operations.

[0054] In other exemplary embodiments, the activation time may be based on both of the above exemplary embodiments. For example, if any UL acknowledgment DCI exists X ms after the last symbol of the PDSCH returning the MAC CE that enables the OCC operation, and if the corresponding PUSCH transmission exists Y ms after the last symbol of the MAC CE's ACK that enables the OCC operation, the PUSCH will use the OCC operation. Otherwise, the PUSCH will not use the OCC operation. That is, in these exemplary embodiments, both of the conditions of the above exemplary embodiments must be satisfied for the OCC operation to be used in the PUSCH.

[0055] To provide examples of these exemplary embodiments, the example of FIG. 7 may be reconsidered. As described above, PUSCH (750) and PUSCH (760) satisfy the condition that the corresponding PUSCH transmission occurs Y ms after the last symbol of the MAC CE's ACK that activates the OCC operations. However, UL acknowledgment (710) does not satisfy the condition that it is received after a predetermined time (e.g., X ms) after the last symbol of the PDSCH that returns the MAC CE that activates the OCC operations, whereas UL acknowledgment (740) satisfies this condition. Therefore, in this example, PUSCH (750) will not be performed using OCC operations, but PUSCVH (760) will be performed using OCC operations.

[0056] Returning to method (500), at 550, the UE (110) can receive dynamic acknowledgment of PUSCH and, for example, apply OCC-based PUSCH using OCC parameters activated based on the timing described above.

[0057] In 560, the UE (110) can receive a MAC CE-based disable of the RRC configuration of the OCC-based PUSCH, and the UE (110) can then disable the OCC operations for the PUSCH. In some exemplary embodiments, the MAC CE used for disablement may be the same MAC CE used for enablement. Some examples of this type of MAC CE are described below. In other exemplary embodiments, the MAC CE may be a single bit indicating the disablement of OCC operations because only a single OCC configuration can be enabled at any given time.

[0058] The deactivation timeline may be similar to the examples of the activation timeline described above, for example, based on the time of received UL acknowledgments and / or based on the time of the scheduled PUSCH and the ACK associated with the deactivation of MAC CE.

[0059] FIG. 8 illustrates an exemplary media access control element (MAC CE) (800) for OCC operations according to various exemplary embodiments. The MAC CE (800) may be a MAC CE transmitted to the UE (110) by the network, for example, at 540 (enabled) or 560 (disabled).

[0060] MAC CE (800) may include a single bit (810) for enabling or disabling the existing RRC configuration of the OCC. The following bits (820) may indicate the index of the RRC configuration to be enabled or disabled.

[0061] As mentioned above, in some exemplary embodiments, the UE (110) may not receive the RRC configuration, for example, 530 of FIG. 5 may not occur. In these exemplary embodiments, the MAC CE providing the enable / disable command may indicate the OCC length and OCC sequence index being enabled / disabled.

[0062] FIG. 9 illustrates an exemplary MAC CE (900) for OCC operations that do not have a radio resource control (RRC) configuration according to various exemplary embodiments. Similar to MAC CE (800), MAC CE (900) may include a single bit (910) for enabling or disabling OCC operations. However, because the UE (110) may not have received an RRC configuration for OCC, MAC CE (900) may also indicate an OCC length (920) and an OCC sequence index (930) (e.g., information that may be provided in the RRC configuration). For example, the OCC code may be predefined as Walsh or DFT-based, and MAC CE (900) may include an OCC length (920) of (2, 4, 8) and an OCC sequence index (930) of a value of

[0007] .

[0063] In the exemplary MAC CE (800, 900), exemplary fields are shown with exemplary bit numbers. These are merely examples, and the number of bits used in any field may be modified based on the type or quantity of OCC information to be indicated by the field.

[0064] As described above, in other aspects of the exemplary embodiments, the activation of OCC is performed using the new RNTI. The following will describe examples of using the new RNTI to activate OCC operations.

[0065] FIG. 10 illustrates an exemplary method (1000) for signaling OCC information for dynamic acknowledgment (DG) and enabling OCC operations using a new radio network temporary identifier (RNTI), according to various exemplary embodiments. The method is performed between a network (e.g., a 5G NR RAN (120)) and a UE (e.g., a UE (110)).

[0066] The operations (1010 to 1030) are similar to the operations (510 to 530) described above with reference to FIG. 5 and will not be described again.

[0067] In 1040, the UE (110) receives a PDCCH with dynamic acknowledgment of PUSCH, where the DCI circular redundancy check (CRC) is scrambled using a new RNTI. The new RNTI may be referred to as OCC-RNTI, but this is only an example, and the new RNTI may be referred to by any name.

[0068] When the UE (110) receives a new RNTI, the UE (110) may reinterpret the DCI fields. For example, certain fields of the DCI format 0_0 / 0_1 / 0_2 may be reinterpreted to represent OCC-related information. The following provides some examples of fields that may be reinterpreted in one or more of the DCI formats to represent OCC-related information.

[0069] In the first example, the most significant bit (MSB) or least significant bit (LSB) of the modulation and coding scheme (MCS) field may be repurposed to represent OCC information. This is based on the fact that the MCS may be limited in OCC-based PUSCH transmissions, because OCC operations may be used when the UE is in bad channel conditions, and therefore only a subset of the available MCS may be used by the UE. Thus, some bit(s) may be available for OCC information. To provide an arbitrary example, in DCI format 0_0, the MCS field may be 5 bits, but only 3 bits are required for the MCS. Thus, 3 LSBs may be used for the MCS, and 2 MSBs may be used for OCC-related information.

[0070] In the second example, the MSBs or LSBs of the Frequency Domain Resource Assignment (FDRA) field may be repurposed to represent OCC information. This is based on the fact that only a certain range of the UL bandwidth part (BOP) can be used for OCC-based PUSCH transmissions. Thus, some bit(s) may be available for OCC information.

[0071] In the third example, the MSBs or LSBs of the Time Domain Resource Assignment (TDRA) field can be repurposed to represent OCC information.

[0072] In the fourth example, some or all bits of the redundancy version (RV) field may be repurposed to represent OCC information. This is based on the fact that only RV=0 can be used for OCC-based PUSCH transmissions. Therefore, some bit(s) may be available for OCC information.

[0073] In the fifth example, the MSB(s) or LSB(s) of the Hybrid Automatic Repeat Request (HARQ) process number field may be repurposed to represent OCC information. This is based on the fact that only certain HARQ process numbers may be suitable for OCC-based PUSCH transmissions. Thus, some bit(s) may be available for OCC information.

[0074] In some exemplary embodiments of the repurposed DCI fields described above, bits may be used to indicate the index of the RRC configuration for OCC information. Such an example uses the RRC configuration of OCC parameters as illustrated in 1030 of FIG. 10.

[0075] In other exemplary embodiments of the repurposed DCI fields described above, bits may be used to represent the OCC length and the OCC sequence index according to the OCC length. In these exemplary embodiments, the RRC configuration of the OCC parameters may not be used. Thus, similar to the examples described above, the RRC configuration of the OCC parameters may not be used, for example, the operation (1030) of FIG. 10 may not be performed.

[0076] Returning to the method (1000) of Fig. 10, the UE (110) can then apply an OCC-based PUSCH using the indicated OCC parameters that were decoded based on the new RNTI.

[0077] Examples

[0078] In the first example, the method comprises, based on signals received from a network, processing an indication that the network supports an orthogonal cover code (OCC) operation on a physical uplink shared channel (PUSCH); generating a UE capability report including an indication of an OCC operation supported by a device for transmission to the network; and processing a media access control element (MAC CE) that enables an OCC operation for PUSCH based on signals received from the network, wherein the MAC CE includes an indication of OCC parameters for an OCC operation for PUSCH.

[0079] In the second example, the method of the first example further comprises the steps of processing a dynamic acknowledgment (DG) for a PUSCH based on signals received from a network and applying OCC parameters for an OCC operation in the PUSCH to the PUSCH corresponding to the DG.

[0080] In the third example, the processing circuit applies OCC parameters when DG is received after a predetermined time after the last symbol of MAC CE that activates the OCC operation, the method of the second example.

[0081] In the fourth example, the method of the second example further includes the step of generating an acknowledgment (ACK) associated with a MAC CE that enables an OCC operation for transmission to a network, wherein the processing circuit applies OCC parameters when a PUSCH corresponding to a DG is scheduled after a predetermined time after the last symbol of the ACK.

[0082] In the fifth example, the method of the second example further includes the step of generating an acknowledgment (ACK) associated with a MAC CE that enables an OCC operation for transmission to a network, wherein the processing circuit schedules a PUSCH corresponding to a DG after a predetermined time after the last symbol of the ACK, and applies OCC parameters when the DG is received after a predetermined time after the last symbol of the MAC CE that enables the OCC operation.

[0083] In the 6th example, the method of the 1st example further comprises the step of processing a second MAC CE that disables the OCC operation for PUSCH based on signals received from the network.

[0084] In the 7th example, the method of the 6th example, wherein the 1st and 2nd MAC CEs are of the same type or different types of MAC CEs.

[0085] In the 8th example, the method of the 6th example further comprises the step of disabling the OCC operation for DGs received after a predetermined time after the last symbol of the 2nd MAC CE that disables the OCC operation.

[0086] In the ninth example, the method of the sixth example further comprises the step of generating an ACK for a second MAC CE that disables an OCC operation for transmission to a network, wherein the processing circuit disables an OCC operation for a PUSCH corresponding to DGs scheduled after a predetermined time after the last symbol of the ACK.

[0087] In the 10th example, the method of the 6th example further comprises the step of generating an ACK associated with a second MAC CE that disables the OCC operation for transmission to a network, wherein the processing circuit disables the OCC operation for a PUSCH corresponding to DGs scheduled after a predetermined time after the last symbol of the ACK, and for DGs received after a predetermined time after the last symbol of the second MAC CE that disables the OCC operation.

[0088] In the 11th example, the method of the 1st example further comprises the step of processing a radio resource control (RRC) configuration including OCC parameters for OCC operation for PUSCH based on signals received from a network, wherein MAC CE includes identification information of the RRC configuration.

[0089] In Example 12, the identification information includes the OCC configuration index, the method of Example 11.

[0090] In the 13th example, the RRC configuration includes multiple RRC configurations, wherein each of the multiple RRC configurations includes an index, and the identification information in MAC CE is the identification information of one of the indexes, the method of the 11th example.

[0091] In the 14th example, the method of the 1st example, in which an indication that the network supports OCC operation in PUSCH is received in the system information block (SIB).

[0092] In the 15th example, the method of the 14th example comprises one or more supported OCC lengths, one or more supported OCC codes, and one or more OCC sequences corresponding to each of the supported OCC lengths and supported OCC codes.

[0093] In Example 16, the UE capability report includes one or more supported OCC lengths and one or more supported OCC codes, the method of Example 1.

[0094] In the 17th example, the OCC parameters include (i) OCC lengths and OCC codes, or (ii) OCC sequence indices corresponding to OCC lengths and OCC codes, the method of the 1st example.

[0095] In the 18th example, MAC CE is the method of the 1st example, which includes OCC parameters.

[0096] In Example 19, a processor configured to perform any of Examples 1 through 18.

[0097] In the 20th example, the UE comprises, as user equipment (UE), a transceiver configured to communicate with a network, and a processor configured to communicateably coupled to the transceiver and configured to perform any of the first through 18 examples.

[0098] In the 21st example, as a method, the method comprises: generating an indication that the network supports an orthogonal cover code (OCC) operation on a physical uplink shared channel (PUSCH) for transmission to a user device (UE); processing a UE capability report including an OCC operation supported by the UE based on signals received from the UE; and generating a media access control element (MAC CE) that enables an OCC operation for PUSCH for transmission to the UE, wherein the MAC CE includes an indication of OCC parameters for an OCC operation for PUSCH.

[0099] In Example 22, the method of Example 21 further comprises the step of generating a dynamic acknowledgment (DG) for PUSCH for transmission to the UE.

[0100] In Example 23, the method of Example 21 further comprises the step of generating a second MAC CE that disables the OCC operation for PUSCH for transmission to the UE.

[0101] In Example 24, the method of Example 21, wherein the first and second MAC CEs are of the same type or different types of MAC CEs.

[0102] In Example 25, the method of Example 21 further comprises the step of generating a radio resource control (RRC) configuration including OCC parameters for OCC operations for PUSCH for transmission to a UE, wherein MAC CE includes identification information of the RRC configuration.

[0103] In Example 26, the method of Example 25, wherein the identification information includes an OCC configuration index.

[0104] In Example 27, the RRC configuration includes multiple RRC configurations, wherein each of the multiple RRC configurations includes an index, and the identification information in MAC CE is the identification information of one of the indexes, the method of Example 25.

[0105] In Example 28, the method of Example 21, in which an indication that the network supports OCC operation in PUSCH is transmitted in the System Information Block (SIB).

[0106] In Example 29, the method of Example 28 comprises one or more supported OCC lengths, one or more supported OCC codes, and one or more OCC sequences corresponding to each of the supported OCC lengths and supported OCC codes.

[0107] In Example 30, the UE capability report includes one or more supported OCC lengths and one or more supported OCC codes, the method of Example 21.

[0108] In the 31st example, the method of the 21st example, wherein the OCC parameters include (i) OCC lengths and OCC codes, or (ii) OCC sequence indices corresponding to OCC lengths and OCC codes.

[0109] In Example 32, MAC CE is the method of Example 21, which includes OCC parameters.

[0110] In Example 33, a processor configured to perform any of Examples 21 through 32.

[0111] In Example 34, the base station comprises a transceiver configured to communicate with user equipment (UE), and a processor coupled to the transceiver in a communicable manner and configured to perform any of Examples 1 through 18.

[0112] In the 35th example, the method comprises, based on signals received from a network, processing an indication that the network supports an orthogonal cover code (OCC) operation on a physical uplink shared channel (PUSCH); generating a UE capability report including an indication of an OCC operation supported by a device for transmission to the network; and based on signals received from the network, processing downlink control information (DCI) having a scrambled circular redundancy check (CRC) using radio network temporary identification information (RNTI) associated with the OCC operation for PUSCH, wherein one or more fields in the DCI include indications of OCC parameters for the OCC operation for PUSCH.

[0113] The method of Example 35, further comprising, in Example 36, a step of processing a dynamic acknowledgment (DG) for a PUSCH based on signals received from a network, and a step of applying OCC parameters for an OCC operation in a PUSCH to a PUSCH corresponding to the DG.

[0114] In Example 37, the method of Example 35, wherein DCI includes DCI format 0_0, DCI format 0_1, or DCI format 0_2.

[0115] In Example 38, the method of Example 37, wherein one or more fields in DCI format 0_0, DCI format 0_1, or DCI format 0_2 include OCC parameters for OCC operations in PUSCH.

[0116] In Example 39, the method of Example 38, wherein one or more fields include a modulation and coding scheme (MCS) field, a frequency domain resource allocation (FDRA) field, a time domain resource allocation (TDRA) field, a redundancy version (RV) field, or a hybrid automatic repeat request (HARQ) process number field.

[0117] The method of Example 35, in Example 40, further comprises the step of processing a radio resource control (RRC) configuration including OCC parameters for OCC operation for PUSCH based on signals received from a network, wherein one or more fields in DCI include identification information of the RRC configuration.

[0118] In Example 41, the method of Example 40, wherein the identification information includes an OCC configuration index.

[0119] In Example 42, the RRC configuration includes multiple RRC configurations, wherein each of the multiple RRC configurations includes an index, and the identification information in the DCI is the identification information of one of the indexes, the method of Example 40.

[0120] In Example 43, the method of Example 35, in which an indication that the network supports OCC operation in PUSCH is received in the System Information Block (SIB).

[0121] In Example 44, the method of Example 43 comprises one or more supported OCC lengths, one or more supported OCC codes, and one or more OCC sequences corresponding to each of the supported OCC lengths and supported OCC codes.

[0122] In Example 45, the method of Example 35, wherein the UE capability report includes one or more supported OCC lengths and one or more supported OCC codes.

[0123] In Example 46, the method of Example 35, wherein the OCC parameters include (i) OCC lengths and OCC codes, or (ii) OCC sequence indices corresponding to OCC lengths and OCC codes.

[0124] In Example 47, the method of Example 46, wherein one or more fields of the DCI include OCC parameters.

[0125] In Example 48, a processor configured to perform any of Examples 35 through 47.

[0126] In Example 49, the UE comprises, as user equipment (UE), a transceiver configured to communicate with a network, and a processor configured to communicateably coupled to the transceiver and configured to perform any of Examples 35 through 47.

[0127] In the 50th example, as a method, the method comprises: generating an indication that the network supports an orthogonal cover code (OCC) operation on a physical uplink shared channel (PUSCH) for transmission to a user device (UE); processing a UE capability report including an OCC operation supported by the UE based on signals received from the UE; and generating downlink control information (DCI) having a scrambled circular redundancy check (CRC) using radio network temporary identification information (RNTI) associated with the OCC operation for PUSCH for transmission to the UE, wherein one or more fields in the DCI include indications of OCC parameters for the OCC operation for PUSCH.

[0128] In Example 51, the method of Example 50 further comprises the step of generating a dynamic acknowledgment (DG) for PUSCH for transmission to the UE.

[0129] In Example 52, the method of Example 50, wherein DCI includes DCI format 0_0, DCI format 0_1, or DCI format 0_2.

[0130] In Example 53, the method of Example 52, wherein one or more fields in DCI format 0_0, DCI format 0_1, or DCI format 0_2 include OCC parameters for OCC operations in PUSCH.

[0131] In Example 54, the method of Example 53, wherein one or more fields include a modulation and coding scheme (MCS) field, a frequency domain resource allocation (FDRA) field, a time domain resource allocation (TDRA) field, a redundancy version (RV) field, or a hybrid automatic repeat request (HARQ) process number field.

[0132] In Example 55, the method of Example 50 further comprises the step of generating a radio resource control (RRC) configuration including OCC parameters for OCC operations for PUSCH for transmission to a UE, wherein one or more fields in DCI include identification information of the RRC configuration.

[0133] In Example 56, the identification information includes the OCC configuration index, the method of Example 54.

[0134] In Example 57, the RRC configuration includes multiple RRC configurations, wherein each of the multiple RRC configurations includes an index, and the identification information in the DCI is the identification information of one of the indexes, the method of Example 54.

[0135] In Example 58, the method of Example 50, in which an indication that the network supports OCC operation in PUSCH is transmitted in the System Information Block (SIB).

[0136] In Example 59, the method of Example 58 comprises one or more supported OCC lengths, one or more supported OCC codes, and one or more OCC sequences corresponding to each of the supported OCC lengths and supported OCC codes.

[0137] In Example 60, the method of Example 50, wherein the UE capability report includes one or more supported OCC lengths and one or more supported OCC codes.

[0138] In Example 61, the OCC parameters include (i) OCC lengths and OCC codes, or (ii) OCC sequence indices corresponding to OCC lengths and OCC codes, the method of Example 50.

[0139] In Example 62, the method of Example 61, wherein one or more fields of the DCI include OCC parameters.

[0140] In Example 63, a processor configured to perform any of Examples 50 through 62.

[0141] In Example 64, the base station comprises a transceiver configured to communicate with user equipment (UE), and a processor coupled to the transceiver to enable communication and configured to perform any of Examples 50 through 62.

[0142] Those skilled in the art will understand that the exemplary embodiments described above may be implemented in any suitable software or hardware configuration or a combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms having a compatible operating system, Windows OS, MAC platforms, and mobile devices having an operating system such as MAC OS, iOS, Android, etc. Exemplary embodiments of the method described above may be implemented as a program comprising lines of code stored on a non-transient computer-readable storage medium that can be executed on a processor or microprocessor when compiled.

[0143] Although the present application describes various embodiments having different features in various combinations, those skilled in the art will understand that any of the features of one embodiment may be combined with features of other embodiments in any manner that is not specifically identified or that is not functionally or logically inconsistent with the operation of the device or the mentioned functions of the disclosed embodiments.

[0144] It is well understood that the use of personally identifiable information must follow privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data must be managed and processed to minimize the risk of unintended or unauthorized access or use, and the nature of authorized use must be clearly indicated to users.

[0145] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Accordingly, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that such modifications and variations fall within the scope of the appended claims and their equivalents.

Claims

Claim 1 A device comprising a processing circuit, wherein the processing circuit is configured to process, based on signals received from a network, an indication that the network supports an Orthogonal Cover Code (OCC) operation on a Physical Uplink Shared Channel (PUSCH); to generate a UE capability report including an indication of an OCC operation supported by the device for transmission to the network; and to process a Medium Access Control Control Element (MAC CE) that enables the OCC operation for PUSCH based on signals received from the network, wherein the MAC CE includes an indication of OCC parameters for the OCC operation for PUSCH. Claim 2 The apparatus according to claim 1, wherein the processing circuit is further configured to process a dynamic grant (DG) for a PUSCH based on signals received from the network; and to apply the OCC parameters for the OCC operation in the PUSCH to the PUSCH corresponding to the DG. Claim 3 In paragraph 2, the processing circuit unit applies the OCC parameters when the DG is received after a predetermined time after the last symbol of the MAC CE that activates the OCC operation. Claim 4 In paragraph 2, the processing circuit is further configured to generate an acknowledgment (ACK) associated with the MAC CE that enables the OCC operation for transmission to the network, and the processing circuit applies the OCC parameters when the PUSCH corresponding to the DG is scheduled after a predetermined time after the last symbol of the ACK. Claim 5 In paragraph 2, the processing circuit is further configured to generate an acknowledgment (ACK) associated with the MAC CE that enables the OCC operation for transmission to the network, and the processing circuit applies the OCC parameters when the DG is received after a predetermined time after the last symbol of the ACK and when the DG is received after a predetermined time after the last symbol of the MAC CE that enables the OCC operation. Claim 6 A device according to claim 1, wherein the processing circuit is further configured to process a second MAC CE that disables the OCC operation for PUSCH based on signals received from the network. Claim 7 In claim 6, the processing circuit is further configured to disable the OCC operation for DGs received after a predetermined time after the last symbol of the second MAC CE that disables the OCC operation. Claim 8 In claim 6, the processing circuit is further configured to generate an ACK for the second MAC CE that disables the OCC operation for transmission to the network, and the processing circuit disables the OCC operation for a PUSCH corresponding to DGs scheduled after a predetermined time after the last symbol of the ACK. Claim 9 In claim 6, the processing circuit is further configured to generate an ACK associated with the second MAC CE that disables the OCC operation for transmission to the network, and the processing circuit disables the OCC operation for a PUSCH corresponding to DGs scheduled after a predetermined time after the last symbol of the ACK, and for DGs received after a predetermined time after the last symbol of the second MAC CE that disables the OCC operation. Claim 10 In claim 1, the processing circuit is further configured to process a radio resource control (RRC) configuration including OCC parameters for the OCC operation for PUSCH based on signals received from the network, and the MAC CE includes identification information of the RRC configuration. Claim 11 In paragraph 10, the above identification information is a device including an OCC configuration index. Claim 12 A device according to claim 10, wherein the RRC configuration comprises a plurality of RRC configurations, each of the plurality of RRC configurations comprises an index, and the identification information in the MAC CE is the identification information of one of the indexes. Claim 13 A device according to claim 1, wherein the OCC parameters include (i) OCC lengths and OCC codes, or (ii) OCC sequence indices corresponding to OCC lengths and OCC codes. Claim 14 A device comprising a processing circuit, wherein the processing circuit is configured to process, based on signals received from a network, an indication that the network supports an orthogonal cover code (OCC) operation on a physical uplink shared channel (PUSCH); to generate a UE capability report including an indication of an OCC operation supported by the device for transmission to the network; and to process Downlink Control Information (DCI) having a scrambled cyclic redundancy check (CRC) using Radio Network Temporary Identification (RNTI) associated with the OCC operation for PUSCH based on signals received from the network, wherein one or more fields in the DCI include indications of OCC parameters for the OCC operation for PUSCH. Claim 15 In claim 14, the processing circuit is further configured to process a dynamic acknowledgment (DG) for a PUSCH based on signals received from the network; and to apply the OCC parameters for the OCC operation in the PUSCH to the PUSCH corresponding to the DG. Claim 16 A device according to claim 1, wherein DCI comprises DCI format 0_0, DCI format 0_1, or DCI format 0_2, and one or more fields in said DCI format 0_0, DCI format 0_1, or DCI format 0_2 comprise said OCC parameters for said OCC operation in PUSCH. Claim 17 A device according to claim 16, wherein one or more of the fields include a Modulation and Coding Scheme (MCS) field, a Frequency Domain Resource Assignment (FDRA) field, a Time Domain Resource Assignment (TDRA) field, a redundancy version (RV) field, or a Hybrid Automatic Repeat Request (HARQ) process number field. Claim 18 In claim 14, the processing circuit is further configured to process a radio resource control (RRC) configuration including OCC parameters for the OCC operation for PUSCH based on signals received from the network, and the one or more fields in the DCI include identification information of the RRC configuration. Claim 19 In paragraph 18, the above identification information is a device including an OCC configuration index. Claim 20 A device according to claim 18, wherein the RRC configuration comprises a plurality of RRC configurations, each of the plurality of RRC configurations comprises an index, and the identification information in the DCI is the identification information of one of the indices.