[go: up one dir, main page]

WO2025065647A1 - Systèmes et procédés de détermination de ressources pour transmettre des informations de commande à un nœud intelligent - Google Patents

Systèmes et procédés de détermination de ressources pour transmettre des informations de commande à un nœud intelligent Download PDF

Info

Publication number
WO2025065647A1
WO2025065647A1 PCT/CN2023/122951 CN2023122951W WO2025065647A1 WO 2025065647 A1 WO2025065647 A1 WO 2025065647A1 CN 2023122951 W CN2023122951 W CN 2023122951W WO 2025065647 A1 WO2025065647 A1 WO 2025065647A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless communication
control information
information
pucch
resource
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/122951
Other languages
English (en)
Inventor
Shuang ZHENG
Nan Zhang
Wei Cao
Ziyang Li
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2023/122951 priority Critical patent/WO2025065647A1/fr
Publication of WO2025065647A1 publication Critical patent/WO2025065647A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals

Definitions

  • the disclosure relates generally to wireless communications, including but not limited to systems and methods for determining resources for transmitting control information to a group of network nodes (e.g., smart nodes) .
  • a group of network nodes e.g., smart nodes
  • Coverage is a fundamental aspect of cellular network deployments.
  • Mobile operators rely on different types of network nodes to offer blanket coverage in their deployments.
  • new types of network nodes have been considered to increase the flexibility of mobile operators for their network deployments.
  • IAB integrated access and backhaul
  • Another type of network node is the RF repeater which simply amplify-and-forward any signal that they receive. RF repeaters have seen a wide range of deployments in 2G, 3G and 4G to supplement the coverage provided by regular full-stack cells.
  • example embodiments disclosed herein are directed to solving the issues relating to one or multiple of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings.
  • example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.
  • At least one aspect is directed to a system, a method, an apparatus, or a computer-readable medium for determining resources for transmitting control information to a group of network nodes.
  • a network node e.g., SN
  • the forwarding link can include at least one of the following: a forwarding link from a wireless communication node to the network node; a forwarding link from the network node to the wireless communication node; a forwarding link from the network node to the wireless communication device; or a forwarding link from the wireless communication device to the network node.
  • the control information can be carried through a Physical Uplink Control Channel (PUCCH) .
  • PUCCH Physical Uplink Control Channel
  • the PUCCH resource used for the control information can be indicated by the wireless communication node to the wireless communication device and/or the network node.
  • one of the existing fields in the Downlink Control Information (DCI) can be reinterpreted to indicate the PUCCH resource for the control information.
  • DCI Downlink Control Information
  • At least one of the following can be considered: one or more existing fields in the DCI can be set as a specific value when the one of existing field in the DCI is used for indicating the PUCCH resource used for the control information; a new field can be added to the DCI to differentiate; or a new higher layer parameter can be configured to differentiate.
  • one or more dedicated resource lists can be configured via a Radio Resource Control (RRC) signaling for the PUCCH.
  • RRC Radio Resource Control
  • each dedicated resource list may include one or more resource configurations, and each resource configuration may include at least one of the following: a PUCCH resource information or the periodicity and/or offset associated with the PUCCH resource.
  • the PUCCH resource information can be an index that refers to a PUCCH resource configured by the wireless communication mode.
  • MAC Medium Access Control
  • CEs can be configured to activate one more resource configuration.
  • one or more MAC CEs can be configured to indicate the one or more PUCCH resources used for the control information.
  • at least one of the following can be considered: an existing table between a plurality of cyclic shift values and UCI bits can be re-interpreted for a mapping between the plurality of cyclic shift values and the control information; or a new table can be configured for a mapping between a plurality of cyclic shift values and the control information.
  • a Radio Network Temporary Identifier (RNTI) used for scrambling the PUCCH can be at least one of the following: an RNTI of the network node; an RNTI of the wireless communication device; or a new type of RNTI.
  • the network node can receive configuration information related to the PUCCH used for the control information.
  • the configuration information may include at least one of the following: time resource information of resources for the PUCCH; frequency resource information of the resources for the PUCCH; a PUCCH format; associated information used for decoding the PUCCH; a cell ID; information related to a Demodulation Reference Signal (DM-RS) associated with the PUCCH; beam information configured for the network node to receive the PUCCH; or an UE identity related to the resources for the PUCCH.
  • the network node can receive the configuration information from at least one of the following: a wireless communication node through at least one of an RRC signaling, a MAC CE, or a DCI; a wireless communication device; or the one or more configuration information pre-defined for the network node.
  • the control information can be carried through a Physical Uplink Shared Channel (PUSCH) .
  • the PUSCH resource used for the control information can be indicated by the wireless communication node to the wireless communication device and/or the network node.
  • a new type of Common Search Space (CSS) can be introduced for monitoring the DCI.
  • the PUSCH resource scheduled by the DCI monitored in the new CSS can be used for the control information.
  • the PUSCH resource used for the control information can be scheduled by the existing DCI with CRC scrambled by a specific RNTI.
  • the specific RNTI may include at least one of the following: a new type of RNTI; or an RNTI of the network node.
  • a new field can be added to the existing DCI to differentiate whether the DCI is for scheduling a transmission of the PUSCH, including the control information, to the network node or a transmission of the PUSCH to a wireless communication node.
  • a new RRC parameter can be added to an existing RRC signaling to differentiate whether the configuration is configured for a transmission of the PUSCH including the control information to the network node or a transmission of the PUSCH to a wireless communication node.
  • the one or more dedicated configuration can be configured for the configured grant-based PUSCH used for the control information.
  • the existing DCI signaling with CRC scrambled by a specific RNTI can be used for validating the scheduling activation or scheduling release of the one or more dedicated configured grant.
  • the specific RNTI may include at least one of the following: a new type of RNTI or a RNTI of network node.
  • a dedicated scheduling request can be configured for the wireless communication device to request resources for the PUSCH used for transmitting the control information.
  • a Radio Network Temporary Identifier (RNTI) used for scrambling the bits of PUSCH may include at least one of the following: an RNTI of the wireless communication device; an RNTI of the network node; or a new type of RNTI.
  • the network node can receive configuration information related to the PUSCH used for the control information.
  • the configuration information may include at least one of the following: time resource information of resources for the PUSCH; frequency resource information of the resources for the PUSCH; information used for decoding the PUSCH; information related to a Demodulation Reference Signal (DM-RS) associated with the PUSCH; beam information configured for the network node to receive the PUSCH; or an UE identity related to the resources for the PUSCH.
  • DM-RS Demodulation Reference Signal
  • the network node can receive the configuration information from at least one of the following: a wireless communication node through at least one of an RRC signaling; a MAC CE; or a DCI; a wireless communication device; or the one or more configuration information pre-defined for the network node.
  • the control information can be carried through a physical sidelink Channel.
  • the physical sidelink channel may include at least one of the following: a Physical Sidelink Control Channel (PSCCH) , a Physical Sidelink Shared Channel (PSSCH) , a Physical Sidelink Feedbcak Channel (PSFCH) or a Physical Sidelink Broadcast Channel (PSBCH) .
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSFCH Physical Sidelink Feedbcak Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • a new format of Sidelink Control Information (SCI) can be introduced for the control information.
  • an identifier field can be added to the existing SCI and/or the new SCI format.
  • At least one aspect is directed to a system, a method, an apparatus, or a computer-readable medium for determining resources for transmitting control information to a group of network nodes.
  • the wireless communication device can send/transmit/provide/signal control information indicating for a forwarding link to the network node.
  • the network node can receive/obtain/collect/acquire control information indicating for a forwarding link from the wireless communication device, according to at least one of the following example configurations or solutions:
  • the control information may be carried on the physical uplink control channel (PUCCH) and/or physical uplink shared channel (PUSCH) channel (s) .
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • Example configuration 2 The control information may be carried on the sidelink.
  • Example configuration 3 The types and format of the control information.
  • FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure
  • FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure
  • FIG. 3 illustrates a schematic diagram of an example network, in accordance with some embodiments of the present disclosure
  • FIG. 4 illustrates a schematic diagram of transmission links between BS to SN and SN to UE, in accordance with some embodiments of the present disclosure
  • FIG. 5 illustrates a schematic diagram of a network-controlled SN model, in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates a schematic diagram of a UE-controlled SN model, in accordance with some embodiments of the present disclosure
  • FIG. 7 illustrates a schematic diagram of a network-controlled repeater, in accordance with some embodiments of the present disclosure.
  • FIG. 8 illustrates a flow diagram of an example method for determining resources for transmitting control information to a group of smart nodes, in accordance with an embodiment of the present disclosure.
  • FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure.
  • the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100.
  • NB-IoT narrowband Internet of things
  • Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101.
  • the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126.
  • Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.
  • the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104.
  • the BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively.
  • Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128.
  • the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.
  • FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution.
  • the system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein.
  • system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of FIG. 1, as described above.
  • the System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) .
  • the BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220.
  • the UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240.
  • the BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.
  • system 200 may further include any number of modules other than the modules shown in FIG. 2.
  • modules other than the modules shown in FIG. 2.
  • the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof.
  • various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.
  • the UE transceiver 230 may be referred to herein as an “uplink” transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232.
  • a duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion.
  • the BS transceiver 210 may be referred to herein as a “downlink” transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212.
  • a downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion.
  • the operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.
  • the UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme.
  • the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
  • LTE Long Term Evolution
  • 5G 5G
  • the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example.
  • eNB evolved node B
  • the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc.
  • PDA personal digital assistant
  • the processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.
  • a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or multiple microprocessors in conjunction with a digital signal processor core, or any other such configuration.
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof.
  • the memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively.
  • the memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230.
  • the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively.
  • Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.
  • the network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202.
  • network communication module 218 may be configured to support internet or WiMAX traffic.
  • network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network.
  • the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) .
  • MSC Mobile Switching Center
  • the Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems.
  • the model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it.
  • the OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols.
  • the OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model.
  • a first layer may be a physical layer.
  • a second layer may be a Medium Access Control (MAC) layer.
  • MAC Medium Access Control
  • a third layer may be a Radio Link Control (RLC) layer.
  • a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer.
  • PDCP Packet Data Convergence Protocol
  • a fifth layer may be a Radio Resource Control (RRC) layer.
  • a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.
  • NAS Non Access Stratum
  • IP Internet Protocol
  • FIG. 3 illustrates a schematic diagram of an example network 300.
  • one or multiple BSs 102A-B e.g., BSs 102
  • can serve one or multiple UEs 104A-B e.g., UEs 104) respectively in their cells via the respective one or multiple SNs 306A-B (e.g., sometimes labeled as SN (s) 306) , such as when there are blockages between the BS (s) 102 and the UE (s) 104.
  • SNs 306A-B e.g., sometimes labeled as SN (s) 306
  • the corresponding mechanism for indicating the control information for the NCR is to indicate the beam information for the backhaul link and access link.
  • periodic indication can be enabled by RRC signaling.
  • the RRC signaling can be used to configure a list of “NCR-PeriodicFwdResourceSet” , each of which includes a number of “PeriodicFwdResourceSet” .
  • Each forwarding resource is defined as a pair of beam and time resource. Same periodicity can be shared for the forwarding resource within one PeriodicFwdResourceSet.
  • semi-persistent indication can be enabled by RRC + MAC CE signaling.
  • control information may be carried on the PUCCH and/or PUSCH channel.
  • the control information can be transmitted from the UE to the SN.
  • the UE shall know which channel resources will be used to transmit the control information to the SN.
  • the control information transmitted to the SN is carried on the PUCCH, several aspects/implementations can be considered.
  • the resource configuration of PUCCH to transmit the control information to the SN can be configured to the UE. The UE can then transmit the control information to the SN using the corresponding PUCCH resources.
  • the number of PUCCH resource sets configured to each UE can be limited (e.g., four or any positive integer) , and each PUCCH resource set can include multiple PUCCH resources.
  • the corresponding PUCCH resource can be configured to the UE.
  • a new field can be added to the existing DCI format (e.g., DCI 1_0, DCI 1_1, DCI 1_2, etc. ) to differentiate whether the PUCCH resource indicator field in the DCI signaling can be used for indicating the control information or for HARQ-ACK information.
  • a new higher layer parameter e.g., a new RRC parameter or a new MAC CE signaling
  • a new RRC parameter or a new MAC CE signaling can be defined to indicate that the PUCCH resource indicator field in the DCI signaling can be used for indicating the control information or for HARQ-ACK information.
  • this new higher later parameter can be a “1” bit value, and when this parameter is set to 1, it means/indicates that the PUCCH resource indicator field in the DCI signaling can be used for indicating the control information; otherwise, it means/indicates that the PUCCH resource indicator field in the DCI signaling is for legacy use.
  • a dedicated PUCCH resource can be defined/configured to transmit the control information. This allows for several options/implementations to be considered.
  • the one or more dedicated resource lists can be configured via the RRC signaling to the UE for using the PUCCH to transmit the control information to the SN, and the RRC signaling can be the existing RRC signaling (e.g., the existing RRC PUCCH-Config signaling) or a new RRC signaling.
  • each dedicated resource list it includes one or more resource configurations, where each resource configuration may have a corresponding resource configuration ID, and each resource configuration may include a PUCCH resource information, and may include the periodicity and/or offset information associated with the PUCCH resource.
  • new parameters can be added to the existing PUCCH-Config as follows:
  • a MAC CE signaling (e.g., a new MAC CE signaling or the existing MAC CE signaling) can be used to activate one or more resource configurations (e.g., SN-ResourceConfig ID) .
  • resource configurations e.g., SN-ResourceConfig ID
  • the UE can use the activated resource configurations to transmit the control information to the SN.
  • the applicable time of the activated resource configuration activated by the MAC CE signaling can refer to the existing specification.
  • the UE can transmit the HARQ-ACK information at slot “n” corresponding to the PDSCH carrying the MAC CE signaling, and the applicable time for the activated resource configuration can be applied from the first slot that is after slot where ⁇ is the subcarrier space (SCS) configuration for the PUCCH.
  • SCS subcarrier space
  • one of the fields in the existing MAC CE signaling can be reused to differentiate whether this MAC CE signaling is for legacy use or for activating/deactivating the resource configurations from the dedicated resource list configured in the RRC signaling.
  • the existing SP CSI reporting on PUCCH Activation/Deactivation MAC CE can be reused, and the Reserved bit field in the Oct1 can be reused to differentiate whether this MAC CE signaling is for legacy use or for activating/deactivating the resource configurations from the dedicated resource list configured in the RRC signaling.
  • the Reserved bit field in the Oct1 when the Reserved bit field in the Oct1 is set to “0” , it means/indicates that it is for legacy use, and when the Reserved bit field in the Oct1 is set to “1” , it means/indicates that this MAC CE signaling can be used for activating/deactivating the resource configurations from the dedicated resource list configured in the RRC signaling.
  • the existing Si field in the MAC CE signaling can be used to indicate the activation/deactivation status of the resource configurations.
  • a new MAC CE signaling can be used by the BS to indicate one or more PUCCH resources used to send the control information for SNs.
  • the MAC CE signaling can indicate the one or more PUCCH resources configured in the existing PUCCH-Config to be used for transmitting the control information to the UE.
  • the MAC CE signaling may include one or more PUCCH resource IDs, which directly refer to a PUCCH resource configured in the PUCCH-Config.
  • the MAC CE signaling may include one or more PUCCH resource indicators. The UE can determine a resource set according to the number of bits of control information, and the PUCCH resource indicator field values in the MAC CE signaling map to a set of PUCCH resource IDs provided by the corresponding resource set.
  • the PUCCH resource configured in the existing PUCCH resource set may not include the start slot information.
  • the start slot in which the UE uses the corresponding PUCCH resource to transmit the control information to the SN can be determined.
  • the start slot of the PUCCH resource indicated in the MAC CE signaling can have a slot offset value relative to the reference slot.
  • the reference slot can be the slot in which the UE transmits the HARQ-ACK information corresponding to the PDSCH carrying the MAC CE signaling, or it can be the slot of the applicable time of the MAC CE signaling (e.g., if the UE transmits the HARQ-ACK information at slot “n” , then the reference slot can be the first slot that is after slot where ⁇ is the SCS configuration for the PUCCH resource) .
  • the slot offset value k can be determined by several methods. For example, in certain implementations, k can be provided in the corresponding MAC CE signaling for each indicated PUCCH resource. In this way/manner, for each indicated PUCCH resource in the MAC CE signaling, there may exist an associated k value for it.
  • k can be a pre-defined value provided to the UE via OAM.
  • the existing UCI types may include the HARQ-ACK information, SR, LRR, and CSI
  • the corresponding UCI bits may include any of the HARQ-ACK information bits, SR information bits, LRR information bits, and CSI bits. If the UE transmits the control information to the SN using the PUCCH resource, and if there are dedicated PUCCH resources for transmitting the control information, the UCI types may introduce a new type, which is the control information used for the SNs.
  • the UCI bits may include the control information bits also applicable to the SN.
  • the number of bits of control information may vary (or be different) depending on the transmitted information. For example, if the UE transmits beam and time information to control the forwarding operation of the SN, the number of bits may be greater than 2, and only the PUCCH formats 2/3/4 can be used. In contrast, if the UE wants to transmit the control information to the SN and the number of bits is smaller than 2, which allows the use of PUCCH formats 0/1.
  • the PUCCH format 0/1 can be used if the number of side control information bits is 1 or 2, and PUCCH format 2/3/4 can be used if the number of side control information bits is more than 2; or a new PUCCH format can be introduced for transmitting the control information to the SN.
  • such current PUCCH format can transmit the UCI bits using the different cyclic shift value (i.e., uses the different value of m cs ) In this way/manner, the different values of m cs can be mapped to the different transmitted control information bits.
  • the 1-bit control information 2 values (or any positive integer) of m cs can be defined, and to transmit the 2-bit control information, 4 values (or any positive integer) of m cs can be defined.
  • the PUCCH resource is used to transmit the control information to the SN and the PUCCH format of the corresponding PUCCH resource is set as some specific PUCCH format (e.g., PUCCH format 0 or a new PUCCH format) .
  • the existing mapping table between the value of mcs and the UCI bits (e.g., the mapping table between the value of mcs and the HARQ-ACK information bits, or the mapping table between the value of mcs and the HARQ-ACK information bit and SR information bit) can be reused/re-interpreted for the mapping between the mcs and the control information.
  • the UE when the UE knows/determines that the configured/scheduled PUCCH resource can be used for transmitting the control information to the SN and the PUCCH resource is in PUCCH format 0, the UE can know/determine that the existing mapping table between the value of m cs and the existing UCI bits has been re-interpreted to reflect the mapping between the m cs and the control information.
  • the existing mapping of m cs values for one HARQ-ACK information bit can be reused or reinterpreted as follows: the m cs value 0 is mapped to the HARQ-ACK value 0, and the m cs value 6 is mapped to the HARQ-ACK value 1.
  • this mapping table can be reused/re-interpreted.
  • the forwarding request information can be 1 bit, with bit value 1 representing the forwarding request and bit value 0 meaning to stop the forwarding request.
  • the current m cs value 6 can be re-interpreted to be mapped to the forwarding request value 1
  • the current m cs value 0 can be re-interpreted to be mapped to the forwarding request value 0.
  • the existing mapping of m cs values for two HARQ-ACK information bits can be reused/re-interpreted.
  • the existing current m cs value 0 can be re-interpreted to be mapped to the carrier 0
  • the current m cs value 3 can be re-interpreted to be mapped to the carrier 1
  • the current m cs value 6 can be re-interpreted to be mapped to the carrier 2
  • the current m cs value 9 can be re-interpreted to be mapped to the carrier 3, among others.
  • the one or more dedicated new mapping tables can be defined for the value of m cs and the specific control information.
  • the control information is 1-bit forwarding request information
  • a dedicated mapping table for the value of m cs and the forwarding request information can be defined, as shown below:
  • the SN can also learn the above mapping relationship between m cs and control information. Therefore, when the SN receives a PUCCH from the UE, the SN can decode and obtain the control information accordingly.
  • the PUCCH resource used to transmit control information to the SN can be determined, as described herein. Additionally, the bits that carried on the PUCCH can be scrambled before modulation.
  • the scrambling sequence generator can be initialized with the data scrambling ID/cell ID and/or C-RNTI of the UE. Since the PUCCH resource is used to transmit control information to the SN, the SN is to decode the corresponding PUCCH resource to obtain the control information. As a result, security issues may arise if the PUCCH resource is configured to the SN with the C-RNTI value of the UE. To mitigate this, several options can be considered for the RNTI that is used for the scrambling of the PUCCH resource used to transmit the control information.
  • the RNTI used for the scrambling can be the RNTI of UE (e.g., the C-RNTI) .
  • the RNTI value of UE can be configured to the SN via the BS, the corresponding UE, or the OAM.
  • the RNTI used for the scrambling can be the RNTI of SN (e.g., NCR-RNTI) . In this way/manner, the RNTI of corresponding SN can be indicated/configured to the UE via the BS or the SN.
  • the RNTI used for the scrambling can be a new type of RNTI, and the value of the new type of RNTI can be known for SN and UE.
  • the scrambling sequence generator used in the scrambling procedure can be directly initialized with a specific value, and this value can be configured to the SN and the UE by the BS, pre-defined to the SN and UE, or configured to the SN by the UE. In some examples, since the UE may need to control more than one SN, the UE may need to transmit the control information to the different SNs.
  • a list of specific values used for initializing the scrambling sequence generator can be configured to the UE by the BS or pre-defined for the UE, where each specific value can be used for initializing the scrambling sequence generator of PUCCH used for transmitting the control information to a corresponding SN.
  • the SN may also need to receive and decode the PUCCH transmitted from the different UEs.
  • a list of specific values used for initializing the scrambling sequence generator can be configured to the SN by the BS or pre-defined for the SN, where each specific value can be used for initializing the scrambling sequence generator of PUCCH used for transmitting the control information from a corresponding UE.
  • the SN in addition to configuring the PUCCH resource for the UE to transmit the control information, the SN can also know/determine where and when to decode the PUCCH. In this way, several options can be considered. For example, in certain configurations/implementations, the SN-CU has the same functionality as a normal UE. As a result, the implementations used to configure the PUCCH resource for the UE to send control information can also be applied to the SN. In this way/manner, the PUCCH resource used for the control information of the SN can be configured by the BS to the SN, and the UE is to be the same.
  • the UE when the UE has configured the PUCCH resource used for the control information for SN, the UE can determine that it is to send the control information on the corresponding PUCCH resource. In contrast, when the SN has been configured with the same PUCCH resource, the SN can determine that it is to receive the information on the corresponding PUCCH resource instead of transmitting the information.
  • the information used to decode the corresponding PUCCH transmitted from the UE can also be known by the SN, e.g., the scrambling ID, the RNTI of the corresponding UE, etc.
  • the association relationship between the PUCCH resource and the UE can also be configured to the SN. In this manner, the SN can use the information of the corresponding UE to decode the PUCCH resource transmitted from the UE.
  • the SN can be configured with the relevant configuration and resource information for the PUCCH used to transmit the control information via dedicated signaling. This configuration and information can be used by the SN to decode the corresponding PUCCH transmitted from the corresponding UE.
  • the related configuration and resource information may include at least one of the following: PUCCH-related resource configuration information; the beam information used for the SN to receive the corresponding PUCCH from the UE; and/or the UE identity related to the associated PUCCH resource.
  • the PUCCH-related resource configuration information may further include at least one of the following: the time resource information of the PUCCH resource; the frequency resource information of the PUCCH resource; the PUCCH format; the related specific parameters that used for decoding the PUCCH; cell ID; and/or the information related to the demodulation-reference signal (DM-RS) associated with the PUCCH.
  • the time resource information can include, but is not limited to, at least one of a start time, a pattern, a start and length indicator value (SLIV) , a time offset, a slot offset, a symbol offset, a time domain resource allocation (TDRA) index, a duty cycle, a duration (in symbols or in slots) , a periodicity, and/or a reference SCS.
  • the frequency resource information may include at least one of a carrier index, a band index, a sub-band index, a BandWidth part (BWP) index, a passband index, a cell index, a frequency range index, a start RB index, an RB number, an RE number, a frequency offset, a reference point, the absolute radio frequency channel number (ARFCN) , and/or global synchronization raster (GSCN) .
  • the PUCCH format used to transmit the control information to the SN can be a pre-defined format known by the SN and UE.
  • the related information can be configured to the SN via at least one of the following: dedicated signaling transmitted from the BS to the SN via at least one of: RRC, MAC CE, or DCI signaling; dedicated signaling transmitted from the UE to the SN; and/or pre-defined for the SN.
  • PUSCH resource used by the UE to transmit the control information can be configured to the UE.
  • the implementation for configuring/scheduling the PUSCH transmission in the existing specification can be reused/enhanced for transmitting the control information to the SN.
  • the existing DCI format used to schedule/validate the PUSCH can be reused to schedule/validate the PUSCH for transmitting the control information to the SN.
  • the DCI signaling can be the existing DCI signaling (e.g., the DCI 0_0, DCI 0_1, DCI 0_2, etc. ) .
  • the DCI signaling is used to schedule/validate the PUSCH transmission used for transmitting the control information to the SN, several implementations can be considered to differentiate whether the PUSCH resource is scheduled to be used for legacy or for transmitting the control information to the SN.
  • the new types of common search space can be introduced for an existing DCI format (e.g., the DCI 0_1/0_0/0_2) .
  • the scheduled PUSCH in the DCI monitored in the new CSS can be used for transmitting the control information to the SN.
  • This new type of CSS can be configured to the SN and the UE.
  • the UE when the UE has been configured with such CSS, the UE can decode the DCI monitored in the corresponding CSS to obtain the scheduled PUSCH resource. The UE can then send the control information over the corresponding PUSCH resource.
  • the SN can also decode the DCI monitored in the corresponding CSS to obtain the scheduled PUSCH resource. The SN will then monitor and receive the control information transmitted from the UE on the scheduled PUSCH resource.
  • the DCI monitored in the new types of CSS have the CRC scrambled by the RNTI, and the RNTI can have several options.
  • the RNTI can be the existing RNTI (e.g., C-RNTI or CS-RNTI) .
  • the existing DCI format with CRC scrambled by the C-RNTI and monitored in the new types of CSS can be used for scheduling the PUSCH used for transmitting the control information to the SN.
  • the RNTI can be a new type of RNTI, and this new type of RNTI can be configured to the SN and the UE with the same value.
  • the RNTI can be the RNTI of SN (e.g., the NCR-RNTI of SN) , and the RNTI value of SN can be configured to the UE.
  • the following example can be considered:
  • sn-SearscSpace which means a new types of common search space, e.g., sn-SearscSpace, can be introduced in the existing RRC signaling, e.g., the PDCCH-ConfigCommon.
  • the UE and SN when the UE and SN are configured with the sn-SearscSpace and the corresponding dedicated types of RNTI values, the UE and SN can decode the DCI monitored in the corresponding sn-SearchSpace to obtain the scheduled PUSCH resource.
  • the existing DCI format used to schedule a PUSCH transmission for transmitting the control information can have the CRC scrambled by dedicated types of RNTI.
  • the search space can be the existing search space (e.g., a UE-specific search space or the existing Type-3 PDCCH CSS) or the new types of CSS.
  • the information carried in the corresponding DCI signaling with CRC scrambled by a dedicated RNTI can be used for scheduling the PUSCH transmission for transmitting the control information to the SN.
  • the dedicated types of RNTI used to scramble the DCI with CRC can include several considerations.
  • the dedicated types of RNTI can be a new type of RNTI.
  • the existing DCI format can be monitored in a UE-Specific searchspace, and in this way/manner, the dedicated types of RNTI can be new types of RNTI configured with the different values for the SN and UE.
  • the BS can then separately configure the DCI that scheduled the PUSCH to transmit the control information to the SN and UE.
  • the scheduled PUSCH resource can be the same for the SN and UE.
  • the UE can send the control information over the corresponding PUSCH resource, and the SN can monitor and receive the control information over the corresponding PUSCH resource transmitted from the UE.
  • the dedicated types of RNTI can be the RNTI of SN, e.g., the NCR-RNTI of SN.
  • the existing DCI format can be monitored in existing CSS or new types of CSS.
  • the dedicated RNTI can be the RNTI of SN, e.g., the NCR-RNTI of SN, if configured.
  • the value of RNTI of SN can also be configured/indicated to the UE, so the UE can decode the corresponding DCI transmitted from the BS.
  • a new field can be added to the existing DCI signaling to differentiate whether the DCI signaling can be used to schedule the PUSCH transmission for transmitting the information to the BS or for transmitting the control information to the SN.
  • a new parameter can be added to the existing RRC configuration for the configured grant types of PUSCH (e.g., the ConfiguredGrantConfig signaling) to differentiate whether the configuration can be used for legacy use or for transmitting the control information to the SN.
  • This parameter can only be applicable to UEs capable of sending/transmitting the control information to the SN.
  • a new parameter can be added to the existing ConfiguredGrantConfig signaling, as shown below. When this parameter is set to enabled, it indicates that the configuration is for legacy use. When this parameter is set to disabled, it indicates that the configuration can be used for transmitting the control information for SN.
  • a dedicated PUSCH resource can be configured to the UE to transmit the control information to the SN.
  • the dedicated PUSCH resource can be configured and used by the UE to transmit the control information to the SN.
  • the one or more dedicated configured grant based PUSCH resource used for transmitting the control information to the SN can be configured to the UE via the RRC signaling.
  • the RRC signaling can be the new RRC signaling or the existing RRC signaling (e.g., the existing BWP-UplinkDedicated signaling) .
  • a dedicated configured grant based PUSCH resource list (e.g., configuredGrantConfigForSNToAddModList) can be added to the existing BWP-UplinkDedicated signaling to be used for transmitting the control information to the SN.
  • the dedicated configured grant based PUSCH resource list may include one or more configured grant based PUSCH configurations (e.g., the existing ConfiguredGrantConfig) . In this way/manner, these configurations can be used for transmitting control information to the SN.
  • the maximum number of configurations in the list can be pre-defined for the UE or configured for the UE, as shown below:
  • a dedicated configured grant based PUSCH resource can be configured to the UE via the existing BWP-UplinkDedicated signaling, as shown below:
  • a DCI signaling can be used to validate the scheduling activation or scheduling release of the one or more configured grant based PUSCH configurations used for transmitting the control information to the SN.
  • the DCI can be the existing DCI format (e.g., the DCI 0_0, DCI 0_1, DCI 0_2, etc. ) that scrambled by a specific RNTI (e.g., a new dedicated type of RNTI or the RNTI of corresponding SN, such as the existing ncr-RNTI in Release-18) . All the fields can have the same set as the current specification used for validation of configured UL grant Type2 PUSCH.
  • this DCI with CRC is scrambled by the RNTI of the corresponding SN (e.g., ncr-RNTI)
  • the UE is to be configured with one or more RNTIs that belong to different SNs, either from the BS or the corresponding SN.
  • a dedicated SR configuration can be configured to the UE to request the PUSCH resource for transmitting the control information.
  • a dedicated scheduling request that used for requesting the resource for transmitting the control information to the SN can be introduced in the existing signaling or a new signaling.
  • a dedicated scheduling request resource list for requesting the resource for transmitting the control information can be added to the existing signaling (e.g., PUCCH-Config) or a new signaling, for example as follows:
  • the UE procedure for reporting the dedicated SR used for transmitting the control information for SN can have the same mechanism as the existing SR. The only difference is that when the UE sends/transmits the positive SR into the dedicated SR resources, the BS can know/determine that the scheduling request is to be used for requesting the PUSCH resource for transmitting the control information to the SN.
  • the scrambling sequence generator used in the scrambling process can be initialized with a specific value.
  • This value can be configured to the SN and the UE by the BS, pre-defined to the SN and UE, and/or configured to the SN by the UE.
  • the UE may need to control multiple or more than one SN. In such cases, the UE is to transmit the control information to the different SNs.
  • a list of specific values used to initialize the scrambling sequence generator can be configured to the UE by the BS or pre-defined for the UE.
  • the control information from the UE to the SN can be carried on one or more of the sidelink physical channels (e.g., PSBCH, PSCCH, PSSCH, PSFCH) .
  • the existing SCI (sidelink control information) format SCI 1-A carried on the PSCCH is used to schedule PSSCH and second-stage SCI on PSSCH
  • a new SCI format carried on the PSCCH can be introduced to indicate the control information to the SN.
  • an identifier field can be added to both the existing SCI format 1-A and the new SCI format.
  • the direction information may include the DL/UL information.
  • the bit fields for the direction information may be 2 bits to represent a direction of ⁇ UL, DL, FD ⁇ .
  • the direction can be ⁇ UL, DL ⁇ , and 1 bit is needed.
  • the forwarding request information may include at least one of the following: 1 bit indication, e.g., “1” means to request forwarding and “0” means to stop the requested forwarding; frequency information; time resource information; UE ID; forwarding resource index; and/or forwarding priority.
  • 1 bit indication e.g., “1” means to request forwarding and “0” means to stop the requested forwarding
  • frequency information e.g., time resource information
  • UE ID e.g., time resource information
  • UE ID e.g., forwarding resource index
  • forwarding priority e.g., the UE may transmit its ID to the SN.
  • the SN can then check whether the UE is authorized to request forwarding based on the authorization information received from the BS.
  • the BS can configure the beam information to the SN (e.g., a list of forwarding resources) , and then the UE may request the SN with the one or more forwarding resource indexes configured to the SN to forward.
  • forwarding priority may indicate the priority of the forwarding request. For example, when multiple UEs send requests to the SN, the SN can determine which UE’s request is according to the priority. The priority can be determined by at least one of the following: BS’s priority information, the UE’s capability, the UE’s type, or the transmitted signal/channel. In certain implementations, forwarding complete information can be used to indicate the SN to stop the forwarding operation.
  • Each group, pair, or forwarding resource may include a group of one or more associated resource indications. This allows the SN to be informed of the associated resources. For example, a group of forwarding resource indications can be indicated to the SN from the UE.
  • Each forwarding resource may include: a beam information used by the SN to forward the signal between the SN-UE; a beam information used by the SN to forward the signal between the BS-SN; an associated time resource information; and/or an associated frequency resource information.
  • FIG. 8 illustrates a flow diagram of a method 8000 for determining resources for transmitting control information to a group of network nodes (e.g., SNs) .
  • the method 8000 may be implemented using any of the components and devices detailed herein in conjunction with FIGS. 1–7.
  • the method 8000 may include receiving, by a network node (e.g., SN) , control information indicating for a forwarding link from a wireless communication device (e.g., UE) (8002) .
  • the method may also include sending control information indicating for a forwarding link by the wireless communication device to the network node (8004) .
  • a network node e.g., SN
  • the forwarding link can include at least one of the following: a forwarding link from a wireless communication node to the network node; a forwarding link from the network node to the wireless communication node; a forwarding link from the network node to the wireless communication device; or a forwarding link from the wireless communication device to the network node.
  • the control information can be carried through a Physical Uplink Control Channel (PUCCH) .
  • PUCCH Physical Uplink Control Channel
  • the PUCCH resource used for the control information can be indicated by the wireless communication node to the wireless communication device and/or the network node.
  • one of the existing fields in the Downlink Control Information (DCI) can be reinterpreted to indicate the PUCCH resource for the control information.
  • DCI Downlink Control Information
  • At least one of the following can be considered: one or more existing fields in the DCI can be set as a specific value when one of the existing field in the DCI is used for indicating the PUCCH resource used for the control information; a new field can be added to the DCI to differentiate; or a new higher layer parameter can be configured to differentiate.
  • one or more MAC CEs can be configured to indicate the one or more PUCCH resources used for the control information.
  • at least one of the following can be considered: an existing table between a plurality of cyclic shift values and UCI bits can be re-interpreted for a mapping between the plurality of cyclic shift values and the control information; or a new table can be configured for a mapping between a plurality of cyclic shift values and the control information.
  • a Radio Network Temporary Identifier (RNTI) used for scrambling the PUCCH can be at least one of the following: an RNTI of the network node; an RNTI of the wireless communication device; or a new type of RNTI.
  • the network node can receive configuration information related to the PUCCH used for the control information.
  • the configuration information may include at least one of the following: time resource information of resources for the PUCCH; frequency resource information of the resources for the PUCCH; a PUCCH format; associated information used for decoding the PUCCH; a cell ID; information related to a Demodulation Reference Signal (DM-RS) associated with the PUCCH; beam information configured for the network node to receive the PUCCH; or an UE identity related to the resources for the PUCCH.
  • the network node can receive the configuration information from at least one of the following: a wireless communication node through at least one of an RRC signaling, a MAC CE, or a DCI; a wireless communication device; or the one or more configuration information pre-defined for the network node.
  • the control information can be carried through a Physical Uplink Shared Channel (PUSCH) .
  • the PUSCH resource used for the control information can be indicated by the wireless communication node to the wireless communication device and/or the network node.
  • a new type of Common Search Space (CSS) can be introduced for monitoring the DCI.
  • the PUSCH resource scheduled by the DCI monitored in the new CSS can be used for the control information.
  • the PUSCH resource used for the control information can be scheduled by the existing DCI with CRC scrambled by a specific RNTI.
  • the specific RNTI may include at least one of the following: a new type of RNTI; or an RNTI of the network node.
  • a new field can be added to the existing DCI to differentiate whether the DCI is for scheduling a transmission of the PUSCH, including the control information, to the network node or a transmission of the PUSCH to a wireless communication node.
  • a new RRC parameter can be added to an existing RRC signaling to differentiate whether the configuration is configured for a transmission of the PUSCH including the control information to the network node or a transmission of the PUSCH to a wireless communication node.
  • the one or more dedicated configuration can be configured for the configured grant-based PUSCH used for the control information.
  • the existing DCI signaling with CRC scrambled by a specific RNTI can be used for validating the scheduling activation or scheduling release of the one or more dedicated configured grant.
  • the specific RNTI may include at least one of the following: a new type of RNTI or a RNTI of network node.
  • a dedicated scheduling request can be configured for the wireless communication device to request resources for the PUSCH used for transmitting the control information.
  • a Radio Network Temporary Identifier (RNTI) used for scrambling the bits of PUSCH may include at least one of the following: an RNTI of the wireless communication device; an RNTI of the network node; or a new type of RNTI.
  • the network node can receive configuration information related to the PUSCH used for the control information.
  • the configuration information may include at least one of the following: time resource information of resources for the PUSCH; frequency resource information of the resources for the PUSCH; information used for decoding the PUSCH; information related to a Demodulation Reference Signal (DM-RS) associated with the PUSCH; beam information configured for the network node to receive the PUSCH; or an UE identity related to the resources for the PUSCH.
  • DM-RS Demodulation Reference Signal
  • the network node can receive the configuration information from at least one of the following: a wireless communication node through at least one of an RRC signaling; a MAC CE; or a DCI; a wireless communication device; or the one or more configuration information pre-defined for the network node.
  • the control information can be carried through a physical sidelink Channel.
  • At least one aspect is directed to a system, a method, an apparatus, or a computer-readable medium for determining resources for transmitting control information to a group of network nodes.
  • the wireless communication device can send/transmit/provide/signal control information indicating for a forwarding link to the network node (8004) .
  • any reference to an element herein using a designation such as “first, ” “second, ” and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or multiple microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • module refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.
  • memory or other storage may be employed in embodiments of the present solution.
  • memory or other storage may be employed in embodiments of the present solution.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Sont présentés des systèmes, des procédés, des appareils ou un support lisible par ordinateur pour transmettre des informations de commande à un nœud intelligent. Un nœud de réseau peut recevoir des informations de commande indiquant une liaison de transfert à partir d'un dispositif de communication sans fil. Le dispositif de communication sans fil peut envoyer des informations de commande indiquant une liaison de transfert au nœud de réseau.
PCT/CN2023/122951 2023-09-28 2023-09-28 Systèmes et procédés de détermination de ressources pour transmettre des informations de commande à un nœud intelligent Pending WO2025065647A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/122951 WO2025065647A1 (fr) 2023-09-28 2023-09-28 Systèmes et procédés de détermination de ressources pour transmettre des informations de commande à un nœud intelligent

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/122951 WO2025065647A1 (fr) 2023-09-28 2023-09-28 Systèmes et procédés de détermination de ressources pour transmettre des informations de commande à un nœud intelligent

Publications (1)

Publication Number Publication Date
WO2025065647A1 true WO2025065647A1 (fr) 2025-04-03

Family

ID=95204609

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/122951 Pending WO2025065647A1 (fr) 2023-09-28 2023-09-28 Systèmes et procédés de détermination de ressources pour transmettre des informations de commande à un nœud intelligent

Country Status (1)

Country Link
WO (1) WO2025065647A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022195888A1 (fr) * 2021-03-19 2022-09-22 株式会社Ｎｔｔドコモ Dispositif de relais sans fil et procédé de relais sans fil
CN116097855A (zh) * 2022-08-09 2023-05-09 北京小米移动软件有限公司 回程链路的波束确定方法、装置、介质及产品
CN116647261A (zh) * 2023-06-21 2023-08-25 中国联合网络通信集团有限公司 一种智能超表面的控制方法、装置及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022195888A1 (fr) * 2021-03-19 2022-09-22 株式会社Ｎｔｔドコモ Dispositif de relais sans fil et procédé de relais sans fil
CN116097855A (zh) * 2022-08-09 2023-05-09 北京小米移动软件有限公司 回程链路的波束确定方法、装置、介质及产品
CN116647261A (zh) * 2023-06-21 2023-08-25 中国联合网络通信集团有限公司 一种智能超表面的控制方法、装置及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Discussions on L1/L2 signaling for side control information", 3GPP DRAFT; R1-2204814, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 30 April 2022 (2022-04-30), XP052144075 *

Similar Documents

Publication Publication Date Title
US20230208606A1 (en) Methods and apparatuses for demodulation reference signal configuratio
CN104012061B (zh) 用于监控控制信道的方法和无线装置
WO2019170089A1 (fr) Procédé et appareil de transmission d'informations et nœud de communication
EP4042796B1 (fr) Procédé et appareil de partage dynamique de ressources fréquence dans un système de communication sans fil
RU2731366C1 (ru) Пользовательский терминал и способ радиосвязи
JP2020523894A (ja) 参照信号送信方法、参照信号受信方法及び通信装置
CN116318587A (zh) 多个无线电接入技术共存场景中的共享信道重映射
CN105122861A (zh) 小规模小区中的接收方法和用户设备
US12219587B2 (en) Apparatus and method for inter-cell interference control for wireless communication system
US20180302254A1 (en) Systems and methods for multi-physical structure system
WO2021087856A1 (fr) Système et procédé pour des indicateurs de modes de répétition de transmission
US12166717B2 (en) Method of sound reference signal time bundling
WO2014092429A1 (fr) Procédé de transmission d'informations système dans un système d'accès sans fil prenant en charge une ultra-haute fréquence et dispositif destiné à fonctionner selon ce procédé
EP4113881A1 (fr) Procédé et dispositif de transmission et de réception de signal de référence dans un système de communication sans fil
KR20230157979A (ko) 무선 통신 시스템에서 업링크 제어 정보의 송신을 위한 디폴트 빔 및 경로 손실 기준 신호를 선택하는 방법 및 장치
WO2021128233A1 (fr) Synchronisation directionnelle et acquisition d'informations de système
RU2758469C1 (ru) Терминал, способ радиосвязи и базовая станция
US20240389162A1 (en) Systems, methods, and non-transitory computer-readable media for transmission mode switching
US20240113827A1 (en) Systems and methods for non-codebook based transmission
WO2025065647A1 (fr) Systèmes et procédés de détermination de ressources pour transmettre des informations de commande à un nœud intelligent
KR20230038699A (ko) 사이드링크 통신들을 위한 동기화 신호 블록 파형 설계를 위한 기법들
JP2024025700A (ja) リソースキャンセル方法及びユーザ機器
WO2025050397A1 (fr) Systèmes et procédés pour nœud de réseau commandé par ue
WO2025050258A1 (fr) Systèmes et procédés de détermination d'indication d'informations de ressource pour nœud intelligent
WO2025030540A1 (fr) Systèmes et procédés de détermination d'un groupe de nœuds de réseau

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23953791

Country of ref document: EP

Kind code of ref document: A1