Method and apparatus for transmitting data using resource multiplexing in wireless communication system
Resource multiplexing techniques optimize wireless communication systems by enhancing throughput, coverage, and reliability in new radio networks, addressing the challenges of data growth and user-specific resource needs in non-terrestrial networks.
Patent Information
- Application Number
- PCT/KR2025/003834
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-11-21
- Filing Date
- 2025-03-26
- Publication Date
- 2025-10-02
AI Technical Summary
Existing wireless communication systems face challenges in managing the explosive growth of data, particularly in new radio networks operating at higher frequencies, in terms of throughput, coverage, reliability, and latency, especially in non-terrestrial networks with wide coverage and varying user resource needs.
A resource multiplexing method and device are introduced, allowing communication nodes to exchange multiplexing setting and instruction information, utilize orthogonal sequences, and apply resource multiplexing techniques to enhance system performance by reducing device density and optimizing resource allocation.
The method improves system performance by enhancing throughput, coverage, and reliability, particularly in non-terrestrial networks with wide coverage, by effectively managing resource allocation and user-specific needs.
Smart Images

Figure KR2025003834_02102025_PF_FP_ABST
Abstract
Description
Data transmission method and device using resource multiplexing in a wireless communication system
[0001] The present disclosure relates to a data transmission technology in a wireless communication system, and more particularly, to a technology for transmitting data using resource multiplexing.
[0002] To handle the explosive growth of wireless data, new radio (NR) networks, such as those that utilize higher frequency bands (e.g., higher than 6 GHz) than those of long-term evolution (LTE) or LTE-A, are being considered. NR networks can support both sub-6 GHz and higher frequency bands, and can support a wider range of communication services and scenarios than LTE networks. Furthermore, requirements for NR networks may include enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC).
[0003] For example, a communication network, such as a NR network, can be classified into a terrestrial network and a non-terrestrial network (NTN). In a TN, communication services for terminals can be provided by base stations located on the ground. In an NTN, communication services for terminals can be provided by communication nodes located non-terrestrially, such as satellites, base stations, unmanned aerial vehicles (UAVs), and drones. Communications in TNs and NTNs can be performed based on NR communication technology.
[0004] Meanwhile, communication networks can be designed considering various scenarios, service requirements, and / or potential system compatibility. For example, a 5G communication network, also known as a NR network, can support wideband communication in high-frequency bands. To support wideband communication in high-frequency bands, beam-based communication can be implemented. Multiplexing transmission techniques may be required to increase the throughput or capacity of a communication network, and multiplexing transmission techniques may also be required to increase the coverage or reliability of a communication network. Multiplexing transmission techniques may also be required to improve latency performance.
[0005] The purpose of the present disclosure to address the above-mentioned needs is to provide a method and device for transmission based on resource multiplexing in a communication network.
[0006] According to one embodiment of the disclosure for achieving the above-described purpose, a method of a first communication node may include: receiving resource multiplexing setting information from a second communication node; receiving resource multiplexing instruction information from the second communication node; and transmitting data to the second communication node based on the resource multiplexing instruction information.
[0007] Each of the orthogonal sequences included in the first orthogonal sequence set and the second orthogonal sequence set may be sequences selected from a nominal sequence book that includes all sequences that are orthogonal to each other.
[0008] The above resource multiplexing indication information may indicate one of the first orthogonal sequence set and the second orthogonal sequence set based on at least one of a resource multiplexing sequence size, a resource multiplexing sequence index, or a resource multiplexing sequence type.
[0009] The above resource multiplexing sequence index may be indicated by at least one of an identifier of the first communication node or a radio network temporary identifier (RNTI) that the second communication node may provide.
[0010] The method may further include a step of transmitting resource multiplexing capability information of the first communication node to the second communication node before receiving the resource multiplexing setting information.
[0011] The resource multiplexing capability information of the first communication node may be transmitted in response to receiving the resource multiplexing capability information of the second communication node from the second communication node.
[0012] When the orthogonal sequences included in each of the first orthogonal sequence set and the second orthogonal sequence set are composed of some sequences that are consecutive in a nominal sequence book that includes all sequences, and the first orthogonal sequence set and the second orthogonal sequence set are relatively prime, the resource multiplexing indication information may be indicated by a combination of two of a start sequence index, a last sequence index, or the number of sequence indices of the orthogonal sequences to be used for resource multiplexing.
[0013] The method may further include a step of transmitting a scheduling request message to the second communication node when there is data to be transmitted to the second communication node after receiving the resource multiplexing setting information, and the resource multiplexing indication information may be included in a scheduling grant message received from the second communication node.
[0014] The method may further include a step of determining that resource multiplexing is not indicated in the resources allocated to the first communication node when there is a third communication node allocated the same resources as the resources allocated to the first communication node from the second communication node, and when at least one of resource multiplexing application status, resource multiplexing sequence size, resource multiplexing sequence type, resource multiplexing application range granularity, resource multiplexing application range size, resource multiplexing application range location, resource multiplexing application number, or resource multiplexing application order included in the resource multiplexing instruction information transmitted to the first communication node and the resource multiplexing instruction information transmitted to the third communication node is different.
[0015] If the above resource multiplexing indication information indicates resource multiplexing and repetition and slot aggregation are indicated, the method may further include a step of transmitting data using one of the resource multiplexing or the repetition and slot aggregation methods based on priority information.
[0016] According to one embodiment of the disclosure for achieving the above object, a first communication node includes at least one processor, wherein the at least one processor can cause the first communication node to: receive resource multiplexing setting information from a second communication node; receive resource multiplexing instruction information from the second communication node; and transmit data to the second communication node by multiplexing data based on the resource multiplexing instruction information.
[0017] Each of the orthogonal sequences included in the first orthogonal sequence set and the second orthogonal sequence set may be sequences selected from a nominal sequence book that includes all sequences that are orthogonal to each other.
[0018] Receive resource multiplexing capability information of the second communication node from the second communication node; and further cause the resource multiplexing capability information of the first communication node to be transmitted to the second communication node before receiving the resource multiplexing setting information.
[0019] When the orthogonal sequences included in each of the first orthogonal sequence set and the second orthogonal sequence set are composed of some sequences that are consecutive in a nominal sequence book that includes all sequences, and the first orthogonal sequence set and the second orthogonal sequence set are relatively prime, the resource multiplexing indication information may be indicated by a combination of two of a start sequence index, a last sequence index, or the number of sequence indices of the orthogonal sequences to be used for resource multiplexing.
[0020] The at least one processor may further cause the first communication node to transmit a scheduling request message to the second communication node when there is data to be transmitted to the second communication node after receiving the resource multiplexing setting information, wherein the resource multiplexing indication information may be included in a scheduling grant message received from the second communication node.
[0021] The at least one processor may further cause the first communication node to determine that resource multiplexing is not indicated in the resources allocated to the first communication node when there is a third communication node to which the same resources as the resources allocated to the first communication node exist from the second communication node, and at least one of resource multiplexing application status, resource multiplexing sequence size, resource multiplexing sequence type, resource multiplexing application range granularity, resource multiplexing application range size, resource multiplexing application range location, resource multiplexing application number, or resource multiplexing application order included in the resource multiplexing instruction information transmitted to the first communication node and the resource multiplexing instruction information transmitted to the third communication node are different.
[0022] The at least one processor may further cause the first communication node to transmit data using one of the resource multiplexing or the repetition and slot aggregation methods based on priority information when the resource multiplexing indication information indicates resource multiplexing and repetition and slot aggregation are indicated.
[0023] A method of a second communication node according to one embodiment of the disclosure for achieving the above-described purpose may include the steps of: transmitting resource multiplexing setting information to a first communication node; transmitting resource multiplexing instruction information to the first communication node; and receiving data from the first communication node based on the resource multiplexing instruction information.
[0024] The method may further include a step of transmitting resource multiplexing capability information of the second communication node to the first communication node; and a step of receiving resource multiplexing capability information of the first communication node from the first communication node before transmitting the resource multiplexing setting information.
[0025] The method may further include a step of transmitting, to the first communication node, repetition and slot aggregation indication information and resource multiplexing and priority information of the repetition and slot aggregation together with the resource multiplexing indication information.
[0026] According to one embodiment of the present disclosure, a resource multiplexing scheme can be provided in a communication network, taking into account a terrestrial TN environment or an NTN environment. For example, a resource multiplexing transmission scheme can be used to improve system performance by reducing device density in situations where a large number of UEs are expected within coverage. In particular, because NTN has very wide coverage, more UEs are expected to be within coverage than in TN. Therefore, in NTN, system performance can be improved by effectively reducing device density through resource multiplexing.
[0027] In NTN, for LEO satellites, rapid access and release of NTN resources may be required, as a large number of UEs must successfully transmit their desired data while the LEO satellite provides coverage. In such cases, resource multiplexing can improve NTN performance. Furthermore, the size of frequency resources may be limited in the initial stages of NTN. When initial frequency resources are limited, resource multiplexing can improve NTN performance. Furthermore, some users may require more resources than others depending on their traffic patterns. By further segmenting resource multiplexing for users who require more resources, system capacity can be increased.
[0028] In addition, the effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention pertains from the description below.
[0029] Figure 1 is a conceptual diagram illustrating a first embodiment of a communication network.
[0030] FIG. 2 is a block diagram illustrating a first embodiment of a communication node in a communication network.
[0031] Figure 3 is a conceptual diagram illustrating a second embodiment of a communication network.
[0032] Figure 4 is a conceptual diagram illustrating a third embodiment of a communication network.
[0033] Figure 5a is a conceptual diagram illustrating an example of a frame structure among physical resource structures.
[0034] FIG. 5b is a conceptual diagram illustrating an embodiment of a slot structure of one of the physical resource structures.
[0035] Figure 6 is a flowchart illustrating a first embodiment of a method for transmitting and receiving system information.
[0036] FIG. 7 is a flowchart illustrating a resource multiplexing procedure according to the first embodiment of the present disclosure.
[0037] FIG. 8 is a flowchart illustrating a resource multiplexing procedure according to a second embodiment of the present disclosure.
[0038] Figure 9 is a conceptual diagram for a case where resource multiplexing has 1 symbol granularity in the time domain.
[0039] Figure 10 is a conceptual diagram for a case where resource multiplexing has 1 slot granularity for the time domain.
[0040] Figure 11 is a conceptual diagram for a case where resource multiplexing has a granularity of 1 resource block in the frequency domain.
[0041] Figure 12 is a conceptual diagram for a case where resource multiplexing has 1 resource granularity for an antenna region.
[0042] Figure 13 is a conceptual diagram for a case where resource multiplexing has two-dimensional granularity for the time domain and frequency domain.
[0043] Figure 14 is a conceptual diagram for a case where resource multiplexing has granularity based on hop index.
[0044] Figure 15 is a flowchart illustrating a case where the priority between resource multiplexing and repeat / slot aggregation is determined by an explicit / implicit method.
[0045] Figure 16 is a flowchart for explaining a method for determining priority criteria values and priority of resource multiplexing or repetition / slot aggregation based on transmission parameters.
[0046] Figure 17 is a flowchart explaining a case where priority is determined based on MCS among transmission parameters.
[0047] Figure 18 is a flowchart for explaining a case where priority is determined based on the effective code rate among transmission parameters.
[0048] This disclosure may be subject to various modifications and various embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the disclosure to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the disclosure.
[0049] While terms such as "first" and "second" may be used to describe various components, these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component." The term "and / or" encompasses any combination of multiple related items or any one of multiple related items.
[0050] In embodiments of the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.” Furthermore, in embodiments of the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.”
[0051] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.
[0052] The terminology used in this disclosure is only used to describe specific embodiments and is not intended to limit the present disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, it should be understood that the terms "comprises" or "has" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.
[0053] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which this disclosure pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined herein.
[0054] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. In order to facilitate an overall understanding in describing the present disclosure, identical reference numerals are used for identical components in the drawings, and redundant descriptions of identical components are omitted.
[0055] A communication network to which embodiments according to the present disclosure are applied will be described. The communication network may be a 4G communication network (e.g., a long-term evolution (LTE) communication network, LTE-A communication network), a 5G communication network (e.g., a new radio (NR) communication network), a 6G communication network, etc. The 4G communication network can support communication in a frequency band of 6 GHz or less, and the 5G communication network can support communication in a frequency band of 6 GHz or more as well as a frequency band of 6 GHz or less. The communication network may include a TN and an NTN. The communication network to which embodiments according to the present disclosure are applied is not limited to the contents described below, and the embodiments according to the present disclosure may be applied to various communication networks. Here, the communication network may be used with the same meaning as a communication system, and "LTE" may indicate a "4G communication network," an "LTE communication network," or an "LTE-A communication network," and "NR" may indicate a "5G communication network" or an "NR communication network."
[0056] In an embodiment, "an operation (e.g., a transmission operation) is set to a communication node" may mean that "setting information for the operation (e.g., an information element (IE), a parameter)" and / or "information instructing performance of the operation" are signaled to the communication node. In other words, "an operation (e.g., a transmission operation) is set to a communication node" may mean that the communication node receives "setting information for the operation (e.g., an IE, a parameter)" and / or "information instructing performance of the operation." "an IE (e.g., a parameter) is set to a communication node" may mean "the IE is signaled to the communication node (e.g., the communication node receives the information element)."
[0057] The signaling may be at least one of system information (SI) signaling (e.g., transmission of a system information block (SIB) and / or a master information block (MIB)), radio resource control (RRC) signaling (e.g., transmission of RRC parameters and / or higher layer parameters), medium access control (MAC) control element (CE) signaling, or physical layer (PHY) signaling (e.g., transmission of downlink control information (DCI), uplink control information (UCI), and / or sidelink control information (SCI)). The signaling message may be at least one of an SI signaling message (e.g., an SI message), an RRC signaling message (e.g., an RRC message), a MAC CE signaling message (e.g., a MAC CE message, a MAC message), or a PHY signaling message (e.g., a PHY message).
[0058] Also, for ease of explanation, the physical layer may be referred to as Layer 1 (L1) or PHY, MAC or RRC may be collectively referred to as upper layers, or each may be referred to as Layer 2 (L2), Layer 3 (L3), etc. Accordingly, L1 signaling or PHY signaling may mean any signaling transmitted through a physical layer channel. Similarly, upper layer signaling in this specification may include any L2 signaling transmitted through MAC CE (control element), MAC PDU, etc., or any L3 signaling transmitted through RRC signaling, etc. Also, for ease of explanation, signaling may collectively refer to signaling itself and signaling messages.
[0059] That is, in the present disclosure, the meanings of "signaling," "instructing," "sharing," "providing," "updating," "transmitting," "requesting," "informing," etc. may mean transmitting "contents indicated through physical resources" and / or "information of the physical resources themselves" to a counterpart node through signaling. Transmission of information may include "explicit transmission of information" and / or "implicit transmission of information." Information may be estimated based on a predefined method (e.g., mathematical formula, table, etc.), or may be interpreted by combining methods such as introducing a new field, reinterpreting an existing field, and reinterpreting / utilizing a reserved field.
[0060] For example, what is indicated through a physical resource may mean a combination of the following embodiments:
[0061] - Contents and delimiters of combination units of modulation symbol(s)
[0062] > A delimiter can mean any method that can specify part or all of a unit, such as a number, identifier (ID), index, location, area, or address.
[0063] > Contents and delimiters of the sequence of modulation symbols, codewords, etc.
[0064] > Contents and delimiters of physical signals (e.g., reference signals, synchronization signals, etc.)
[0065] > Contents and identifiers of physical channels (e.g., physical broadcast channel (PBCH), physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), physical random access channel (PRACH), physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), physical sidelink broadcast channel (PSBCH), physical sidelink control channel (PSCCH), physical sidelink shared channel (PSSCH), physical sidelink feedback channel (PSFCH), etc.)
[0066] > For example, DCI transmitted via PDCCH can be included in the content of the PDCCH itself. Uplink control information (UCI) transmitted via PUCCH can be included in the content of the PUCCH itself. UCI transmitted via PUSCH can be included in the content of the PUCCH or PUSCH itself. The radio network temporary identifier (RNTI) used for cyclic redundancy check (CRC) scrambling can be included in the content of the PDCCH or PUCCH itself.
[0067] > Contents and delimiters of upper layer protocol units (e.g., MAC (sub)protocol data units (PDUs), which are combinations of MAC subheaders, MAC CEs, and / or MAC service data units (SDUs), RRC messages, RRC IEs, and other upper layer messages, information, elements, and headers).
[0068] For example, information about the physical resource itself may mean a combination of the embodiments below.
[0069] - A delimiter of all units that can be formed by combining resource elements (REs).
[0070] > A delimiter can mean any method that can specify part or all of a unit, such as a number, ID, index, location, area, or address.
[0071] > RE, sub-carrier (SC), resource block (RB), bandwidth part (BWP), resource grid (RG) delimiter
[0072] > The SC unit separator may include the SC number. In addition, the SC unit separator may optionally further include the separator of the upper unit to which the SC belongs (e.g., RB, RG, etc.).
[0073] > Delimiters of symbols, slots, subframes, and frames
[0074] > The symbol unit delimiter may include a symbol number. In addition, the symbol unit delimiter may optionally further include a delimiter of the upper unit to which the symbol belongs (e.g., slot, subframe, etc.).
[0075] > Antenna, antenna port, beam, and link identifiers
[0076] > Resource element group (REG), control channel element (CCE), control resource set (CORESET), search space identifier (e.g., number, location, area, ID)
[0077] In the present disclosure, even if a method (e.g., transmitting or receiving a signal) performed by a first communication node among communication nodes is described, a corresponding second communication node can perform a method (e.g., receiving or transmitting a signal) corresponding to the method performed by the first communication node. For example, if the operation of a terminal is described, a base station corresponding to the terminal can perform an operation corresponding to the operation of the terminal. Conversely, if the operation of a base station is described, a terminal corresponding to the base station can perform an operation corresponding to the operation of the base station. In addition, if the operation of a first terminal is described, a second terminal corresponding to the first terminal can perform an operation corresponding to the operation of the first terminal. Conversely, if the operation of a second terminal is described, a first terminal corresponding to the second terminal can perform an operation corresponding to the operation of the second terminal.
[0078] Figure 1 is a conceptual diagram illustrating a first embodiment of a communication network.
[0079] Referring to FIG. 1, a communication network (100) may be a terrestrial network. The communication network (100) may include a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). In addition, the communication network (100) may further include a core network, for example, a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), and a mobility management entity (MME). If the communication network (100) is a 5G communication network, for example, an NR network, the core network may include an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc.
[0080] A plurality of communication nodes (110 to 130) can support communication protocols specified in the 3rd generation partnership project (3GPP) standard, such as the LTE communication protocol, the LTE-A communication protocol, and the NR communication protocol. The plurality of communication nodes (110 to 130) may be configured to use code division multiple access (CDMA) technology, wideband CDMA (WCDMA) technology, time division multiple access (TDMA) technology, frequency division multiple access (FDMA) technology, orthogonal frequency division multiplexing (OFDM) technology, filtered OFDM technology, cyclic prefix (CP)-OFDM technology, discrete Fourier transform-spread-OFDM (DFT-s-OFDM) technology, orthogonal frequency division multiple access (OFDMA) technology, single carrier (SC)-FDMA technology, non-orthogonal multiple access (NOMA) technology, generalized frequency division multiplexing (GFDM) technology, filter bank multi-carrier (FBMC) technology, and general It can support technologies such as universal filtered multi-carrier (UFMC) technology and space division multiple access (SDMA) technology.
[0081] A communication network (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) may form a macro cell. Each of the fourth base station (120-1) and the fifth base station (120-2) may form a small cell. The fourth base station (120-1), the third terminal (130-3), and the fourth terminal (130-4) may be within the cell coverage of the first base station (110-1). The second terminal (130-2), the fourth terminal (130-4), and the fifth terminal (130-5) may be within the cell coverage of the second base station (110-2). The fifth base station (120-2), the fourth terminal (130-4), the fifth terminal (130-5), and the sixth terminal (130-6) may be within the cell coverage of the third base station (110-3). The first terminal (130-1) may be within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be within the cell coverage of the fifth base station (120-2).
[0082] Here, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) is a NodeB (NB), an evolved NB (eNB), a gNB, an advanced base station (ABS), a high reliability-base station (HR-BS), a base transceiver station (BTS), a radio base station, a radio transceiver, an access point, an access node, a radio access station (RAS), a mobile multihop relay-base station (MMR-BS), a relay station (RS), an advanced relay station (ARS), a high reliability-relay station (HR-RS), a home NodeB (HNB), a home eNodeB (HeNB), a road side unit (RSU), a radio remote head (radio It can be referred to as a remote head (RRH), transmission point (TP), transmission and reception point (TRP), etc.
[0083] In the present disclosure, a base station may be a conventional base station (e.g., a terrestrial base station) or a satellite base station. The base station may be interpreted as a terrestrial base station or a satellite base station depending on the context. A terrestrial base station may refer to a base station located on the ground. A satellite base station may refer to a base station located on a satellite (e.g., a non-terrestrial base station). A satellite base station may be referred to as a non-terrestrial base station or a mobile base station. Satellites may be classified into transparent satellites and regenerative satellites. Transparent satellites may perform the function of a relay for a base station. Regenerative satellites may perform the function of a base station. The satellites may be high-altitude platform station systems (HAPS), low Earth orbit (LEO) satellites, medium Earth orbit (MEO) satellites, or geostationary equatorial orbit (GEO) satellites. Additionally, satellite can mean UAV.
[0084] Each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as user equipment (UE), terminal equipment (TE), advanced mobile station (AMS), high reliability-mobile station (HR-MS), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, node, device, on board unit (OBU), etc.
[0085] Meanwhile, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in a different frequency band or may operate in the same frequency band. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to each other via an ideal backhaul link or a non-ideal backhaul link, and may exchange information with each other via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to the core network via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit a signal received from the core network to the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6), and can transmit a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) to the core network.
[0086] Additionally, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can support multiple-input multiple-output (MIMO) transmissions, such as single user (SU)-MIMO, multi user (MU)-MIMO, massive MIMO, etc., and can support coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, device to device communication (D2D) or proximity services (ProSe), internet of things (IoT) communication, dual connectivity (DC), etc. Here, each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) can perform an operation corresponding to the base station (110-1, 110-2, 110-3, 120-1, 120-2) and an operation supported by the base station (110-1, 110-2, 110-3, 120-1, 120-2). For example, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) based on the SU-MIMO scheme, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) by the SU-MIMO scheme. Alternatively, the second base station (110-2) can transmit signals to the fourth terminal (130-4) and the fifth terminal (130-5) based on the MU-MIMO method, and each of the fourth terminal (130-4) and the fifth terminal (130-5) can receive signals from the second base station (110-2) based on the MU-MIMO method.
[0087] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can transmit a signal to the fourth terminal (130-4) based on the CoMP scheme, and the fourth terminal (130-4) can receive a signal from the first base station (110-1), the second base station (110-2), and the third base station (110-3) based on the CoMP scheme. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive a signal based on the CA scheme with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage. Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can control D2D between the fourth terminal (130-4) and the fifth terminal (130-5), and each of the fourth terminal (130-4) and the fifth terminal (130-5) can perform D2D under the control of the second base station (110-2) and the third base station (110-3).
[0088] FIG. 2 is a block diagram illustrating a first embodiment of a communication node in a communication network.
[0089] Referring to FIG. 2, a communication node (200) can perform communication in the communication network (100) described above. The communication node (200) can include at least one processor (210), a memory (220), and a transmission / reception device (230) that is connected to a network and performs communication. In addition, the communication node (200) can further include an input interface device (240), an output interface device (250), a storage device (260), etc. Each component included in the communication node (200) can be connected by a bus (270) and communicate with each other.
[0090] However, each component included in the communication node (200) may be connected through an individual interface or individual bus centered around the processor (210), rather than a common bus (270). For example, the processor (210) may be connected to at least one of a memory (220), a transmission / reception device (230), an input interface device (240), an output interface device (250), or a storage device (260) through a dedicated interface.
[0091] The processor (110) can execute program commands stored in at least one of the memory (120) and the storage device (160). The processor (110) may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor in which the methods according to embodiments of the present disclosure are performed. Each of the memory (120) and the storage device (160) may be configured with at least one of a volatile storage medium or a non-volatile storage medium. For example, the memory (120) may be configured with at least one of a read-only memory (ROM) or a random access memory (RAM).
[0092] Figure 3 is a conceptual diagram illustrating a second embodiment of a communication network.
[0093] Referring to FIG. 3, the communication network may be a non-terrestrial network. The non-terrestrial network may include a satellite (310), a communication node (320), a gateway (330), a data network (340), etc. The non-terrestrial network illustrated in FIG. 3 may be a transparent payload-based non-terrestrial network. The satellite (310) may be a LEO satellite, MEO satellite, GEO satellite, a high elliptical orbit (HEO) satellite, or an unmanned aircraft system (UAS) platform. The UAS platform may include a HAPS.
[0094] The communication node (320) may include a ground-based communication node, such as a UE or terminal, and a non-ground-based communication node, such as an airplane or drone. A service link may be established between the satellite (310) and the communication node (320), and the service link may be a radio link. The satellite (310) may provide a communication service to the communication node (320) using one or more beams. The shape of the beam reception area (footprint) of the satellite (310) may be elliptical.
[0095] The communication node (320) can perform communication (e.g., downlink communication, uplink communication) with the satellite (310) using LTE technology and / or NR technology. Communication between the satellite (310) and the communication node (320) can be performed using an NR-Uu interface. When DC is supported, the communication node (320) can be connected to not only the satellite (310) but also other base stations (e.g., base stations supporting LTE and / or NR functions), and can perform DC operations based on technologies defined in the LTE and / or NR standards.
[0096] The gateway (330) may be located on the ground, and a feeder link may be established between the satellite (310) and the gateway (330). The feeder link may be a wireless link. The gateway (330) may be referred to as a "non-terrestrial network (NTN) gateway." Communication between the satellite (310) and the gateway (330) may be performed based on a NR-Uu interface or a satellite radio interface (SRI). The gateway (330) may be connected to a data network (340). A "core network" may exist between the gateway (330) and the data network (340). In this case, the gateway (330) may be connected to the core network, and the core network may be connected to the data network (340). The core network may support NR technology. For example, the core network may include AMF, UPF, SMF, etc. Communication between the gateway (330) and the core network can be performed based on the NG-C / U interface.
[0097] Alternatively, a base station and a core network may exist between the gateway (330) and the data network (340). In this case, the gateway (330) may be connected to the base station, the base station may be connected to the core network, and the core network may be connected to the data network (340). The base station and the core network may support NR technology. Communication between the gateway (330) and the base station may be performed based on the NR-Uu interface, and communication between the base station and the core network (e.g., AMF, UPF, SMF) may be performed based on the NG-C / U interface.
[0098] Figure 4 is a conceptual diagram illustrating a third embodiment of a communication network.
[0099] Referring to FIG. 4, the communication network may be a non-terrestrial network. The non-terrestrial network may include satellite #1 (411), satellite #2 (412), a communication node (420), a gateway (430), a data network (440), etc. The non-terrestrial network illustrated in FIG. 4 may be a regenerative payload-based non-terrestrial network. For example, each of satellites #1-2 (411, 412) may perform a regenerative operation (e.g., a demodulation operation, a decoding operation, a re-encoding operation, a re-modulation operation, and / or a filtering operation) on a payload received from another entity constituting the non-terrestrial network (e.g., a communication node (420), a gateway (430)) and transmit the regenerated payload.
[0100] Each of satellites #1-2 (411, 412) may be a LEO satellite, MEO satellite, GEO satellite, HEO satellite, or UAS platform. The UAS platform may include HAPS. Satellite #1 (411) may be connected to satellite #2 (412), and an inter-satellite link (ISL) may be established between satellite #1 (411) and satellite #2 (412). The ISL may operate in a radio frequency (RF) or optical band. The ISL may be configured as optional. The communication node (420) may include a communication node located on the ground (e.g., UE, terminal) and a communication node located off the ground (e.g., an airplane, a drone). A service link (e.g., a wireless link) may be established between satellite #1 (411) and the communication node (420). Satellite #1 (411) may provide communication services to a communication node (420) using one or more beams.
[0101] The communication node (420) can perform communication (e.g., downlink communication, uplink communication) with satellite #1 (411) using LTE technology and / or NR technology. Communication between satellite #1 (411) and the communication node (420) can be performed using an NR-Uu interface. If DC is supported, the communication node (420) can be connected to not only satellite #1 (411) but also other base stations (e.g., base stations supporting LTE and / or NR functions), and can perform DC operations based on technologies defined in the LTE and / or NR standards.
[0102] The gateway (430) may be located on the ground, and a feeder link may be established between satellite #1 (411) and the gateway (430), and a feeder link may be established between satellite #2 (412) and the gateway (430). The feeder link may be a wireless link. If an ISL is not established between satellite #1 (411) and satellite #2 (412), a feeder link between satellite #1 (411) and the gateway (430) may be established mandatorily.
[0103] Communication between each of satellites #1-2 (411, 412) and the gateway (430) may be performed based on the NR-Uu interface or SRI. The gateway (430) may be connected to a data network (440). A "core network" may exist between the gateway (430) and the data network (440). In this case, the gateway (430) may be connected to the core network, and the core network may be connected to the data network (440). The core network may support NR technology. For example, the core network may include AMF, UPF, SMF, etc. Communication between the gateway (430) and the core network may be performed based on the NG-C / U interface.
[0104] Alternatively, a base station and a core network may exist between the gateway (430) and the data network (440). In this case, the gateway (430) may be connected to the base station, the base station may be connected to the core network, and the core network may be connected to the data network (440). The base station and the core network may support NR technology. Communication between the gateway (430) and the base station may be performed based on the NR-Uu interface, and communication between the base station and the core network (e.g., AMF, UPF, SMF) may be performed based on the NG-C / U interface.
[0105] NTN reference scenarios can be defined as shown in Table 1 below.
[0106] NTN shown in Fig. 3 NTNGEO shown in Fig. 4 Scenario A Scenario BLEO (steerable beam) Scenario C1 Scenario D1 LEO (beam moving with satellite) Scenario C2 Scenario D2
[0107] In the non-terrestrial network illustrated in FIG. 3, if the satellite (310) is a GEO satellite (e.g., a GEO satellite supporting a transparent function), this may be referred to as “Scenario A.” In the non-terrestrial network illustrated in FIG. 4, if the satellites #1-2 (411, 412) are GEO satellites (e.g., a GEO supporting a regenerative function), this may be referred to as “Scenario B.”
[0108] In the non-terrestrial network illustrated in FIG. 3, if the satellite (310) is a LEO satellite having steerable beams, this may be referred to as "Scenario C1." In the non-terrestrial network illustrated in FIG. 3, if the satellite (310) is a LEO satellite having beams move with the satellite, this may be referred to as "Scenario C2." In the non-terrestrial network illustrated in FIG. 4, if satellites #1-2 (411, 412) are LEO satellites having steerable beams, this may be referred to as "Scenario D1." In the non-terrestrial network illustrated in FIG. 2, if satellites #1-2 (411, 412) are LEO satellites having beams move with the satellite, this may be referred to as "Scenario D2."
[0109] Parameters for the NTN reference scenarios defined in Table 1 can be defined as shown in Table 2 below.
[0110] Scenario A and B Scenario C and D Altitude 35,786 km 600 km 1,200 km Spectrum (service link) < 6 GHz (e.g. 2 GHz) > 6 GHz (e.g. DL 20 GHz, UL 30 GHz) Maximum channel bandwidth capability (service link) 30 MHz for band < 6 GHz 1 GHz for band > 6 GHz Maximum distance between satellite and communication node (e.g., UE) at minimum elevation angle 40,581 km 1,932 km (600 km altitude) 3,131 km (1,200 km altitude) Maximum round trip delay (RTD) (propagation delay only) Scenario A: 541.46 ms (service and feeder links) Scenario B: 270.73 ms (service link only) Scenario C: (Transparent payload: service and feeder links) - 25.77 ms (600 km) Scenario D: (Regeneration Payload: Only Service Link) - 12.89ms (600km Altitude) - 20.89ms (1200km Altitude) Maximum Differential Delay Within a Cell 10.3m3.12ms (600km Altitude) 3.18ms (1200km Altitude) Service Link NR as defined in 3GPP Feeder Link Radio Interface as defined in 3GPP or Non-3GPP
[0111] Additionally, in the NTN reference scenarios defined in Table 1, the delay constraint can be defined as shown in Table 3 below.
[0112] Scenario A Scenario B Scenario C1-2 Scenario D1-2 Satellite altitude 35,786 km 600 km Maximum RTD on the air interface between the base station and the UE 541.75 ms (worst case) 270.57 ms 28.41 ms 12.88 ms Minimum RTD on the air interface between the base station and the UE 477.14 ms 238.57 ms 8 ms 4 ms
[0113] In a non-terrestrial network, a base station can transmit system information (e.g., SIB19) containing satellite assistance information for NTN access. A UE can receive system information (e.g., SIB19) from the base station, check the satellite assistance information included in the system information, and perform communication (e.g., non-terrestrial communication) based on the satellite assistance information. SIB19 can include the information element(s) defined in Table 4 below.
[0114] SIB19-r17 ::= SEQUENCE {ntn-Config-r17 NTN-Config-r17t-Service-r17 INTEGER(0..549755813887)referenceLocation-r17 ReferenceLocation-r17distanceThresh-r17 INTEGER(0..65525)ntn-NeighCellConfigList-r17 NTN-NeighCellConfigList-r17lateNonCriticalExtension OCTET STRING...,[[ntn-NeighCellConfigListExt-v1720 NTN-NeighCellConfigList-r17]]}NTN-NeighCellConfigList-r17 ::= SEQUENCE (SIZE(1..maxCellNTN-r17)) OF NTN-NeighCellConfig-r17NTN-NeighCellConfig-r17 ::= SEQUENCE {ntn-Config-r17 NTN-Config-r17carrierFreq-r17 ARFCN-ValueNRphysCellId-r17 PhysCellId}
[0115] NTN-Config defined in Table 4 may include information element(s) defined in Table 5 below.
[0116] NTN-Config-r17 ::= SEQUENCE { epochTime-r17 EpochTime-r17ntn-UlSyncValidityDuration-r17 ENUMERATED{ s5, s10, s15, s20, s25, s30, s35, s40, s45, s50, s55, s60, s120, s180, s240, s900}cellSpecificKoffset-r17 INTEGER(1..1023)kmac-r17 INTEGER(1..512)ta-Info-r17 TA-Info-r17ntn-PolarizationDL-r17 ENUMERATED {rhcp,lhcp,linear}ntn-PolarizationUL-r17 ENUMERATED {rhcp,lhcp,linear}ephemerisInfo-r17 EphemerisInfo-r17ta-Report-r17 ENUMERATED {enabled}...}EpochTime-r17 ::= SEQUENCE {sfn-r17 INTEGER(0..1023),subFrameNR-r17 INTEGER(0..9)}TA-Info-r17 ::= SEQUENCE {ta-Common-r17 INTEGER(0..66485757),ta-CommonDrift-r17 INTEGER(-257303..257303)ta-CommonDriftVariant-r17 INTEGER(0..28949)}
[0117] EphemerisInfo defined in Table 5 may contain the information element(s) defined in Table 6 below.
[0118] EphemerisInfo-r17 ::= CHOICE {positionVelocity-r17 PositionVelocity-r17,orbital-r17 Orbital-r17}PositionVelocity-r17 ::= SEQUENCE {positionX-r17 PositionStateVector-r17,positionY-r17 PositionStateVector-r17,positionZ-r17 PositionStateVector-r17,velocityVX-r17 VelocityStateVector-r17,velocityVY-r17 VelocityStateVector-r17,velocityVZ-r17 VelocityStateVector-r17}Orbital-r17 ::= SEQUENCE {semiMajorAxis-r17 INTEGER (0..8589934591),eccentricity-r17 INTEGER (0..1048575),periapsis-r17 INTEGER (0..268435455),longitude-r17 INTEGER (0..268435455),inclination-r17 INTEGER (-67108864..67108863),meanAnomaly-r17 INTEGER (0..268435455)}PositionStateVector-r17 ::= INTEGER (-33554432..33554431)VelocityStateVector-r17 ::= INTEGER (-131072..131071)
[0119] FIG. 5A is a conceptual diagram illustrating an embodiment of a frame structure among physical resource structures, and FIG. 5B is a conceptual diagram illustrating an embodiment of a slot structure of one of the physical resource structures. Referring to FIG. 5A, an ith frame (500) may be classified into an ith downlink frame (501) and an ith uplink frame (502). The ith frame (500) may include 10 subframes (511, 512, …, 513, 514). One subframe may include n slots according to numerology. n may be a natural number. Each of the 10 subframes (511, 512, …, 513, 514) may be composed of the same slots. Fig. 5a is an example assuming that one subframe is 1 millisecond (ms), and if subframe 0 (511) is 1 ms, other subframes (512, …, 513, 514) may also all be 1 ms. Fig. 5a exemplifies subframe 8 (513) having a length of 1 ms. Subframe 8 (513) may be composed of one or more slots. The number of slots included in one subframe is It can be decided by a dog.
[0120] Referring to Figure 5b, one slot is T slot can be transmitted during a time interval. One slot is N in the time domain. symb may include OFDM symbols (521). One slot may include one or more subcarriers in the frequency domain. In FIG. 5b, one block may be one resource element (RE). One resource element may be indicated by a pair of a time resource index l and a subcarrier resource index k. In other words, an RE may be indicated by a pair of (k,l). One resource block (BR) may be composed of, for example, 12 subcarriers within one time index. One RB may be It can be composed of subcarriers. The number of subcarriers transmitted in one slot is It can be determined by the product of and .
[0121] Figure 6 is a flowchart illustrating a first embodiment of a method for transmitting and receiving system information.
[0122] Referring to FIG. 6, the base station may transmit a master information block (MIB) to the terminal in step S601. The terminal may receive the MIB from the base station and check the information element(s) included in the MIB. The MIB may be transmitted via a broadcast channel (BCH). The MIB may be transmitted periodically in a broadcast manner. The base station may transmit SIB1 to the terminal in step S602. The terminal may receive SIB1 from the base station and check the information element(s) included in the SIB1. SIB1 may be transmitted via a downlink (DL)-shared channel (SCH). SIB1 may be transmitted periodically in a broadcast manner. Alternatively, SIB1 may be transmitted in a unicast manner.
[0123] The base station can transmit other system information (OSI) to the terminal in step S603. The terminal can receive the OSI from the base station in step S603 and check the information element(s) included in the OSI. The OSI can be SIBn. n can be a natural number greater than or equal to 2. For example, the OSI can be one or more SIBs from SIB2 to SIB21. The OSI can be transmitted via the DL-SCH. The OSI can be transmitted periodically according to a broadcast method. Alternatively, the OSI can be transmitted according to a unicast method. Alternatively, the OSI can be transmitted according to an on-demand broadcast method or an on-demand unicast method. In the on-demand broadcast method, the OSI can be transmitted in a broadcast method at the request of the terminal. In the on-demand unicast method, the OSI can be transmitted in a unicast method at the request of the terminal.
[0124] A terminal may attempt to connect to a non-terrestrial network (e.g., a non-terrestrial base station). In other words, the terminal may perform an initial connection procedure for the non-terrestrial network. In this case, the base station (e.g., a non-terrestrial base station) may transmit SIB19 to the terminal. The terminal may receive SIB19 from the base station and check the information element(s) included in SIB19. SIB19 may include the information element(s) defined in Table 4. For example, SIB19 may include NTN-Config, and NTN-Config may include the information element(s) defined in Table 5. Additionally, SIB19 may additionally include an information element regarding a resource multiplexing scheme.
[0125] For example, in the initial access procedure between a terminal and a terrestrial / non-terrestrial network, in order to support resource multiplexing, the base station can inform the terminal of information about the resource multiplexing method or information about the resource multiplexing capability, and the terminal can also inform the base station of information about its resource multiplexing capability. At this time, the base station can inform the terminal of information about the resource multiplexing capability or resource multiplexing method through MIB or SIBn (n is 1 or greater), PHY signaling, upper layer signaling, whether or not / content of a previous message was transmitted, etc. Correspondingly, the terminal can inform the base station of information about the resource multiplexing capability through a random access channel (RACH) occasion (RO), PRACH format, PHY signaling, upper layer signaling, whether or not / content of a previous message was transmitted, etc. Additionally, the resource multiplexing method can be separately indicated for each link. For example, the resource multiplexing method of DL and the resource multiplexing method of UL can be separately indicated. In addition, one or more multiplexing schemes can be set for one node, and in this case, the scheduling node can instruct the counterpart node to use a specific resource multiplexing scheme for each transmission. For example, information about the resource multiplexing scheme can be instructed to the terminal. In this case, information about the resource multiplexing scheme to be used by the terminal can be set for the terminal. Additionally, information about the resource multiplexing scheme instructed to the terminal can be separately instructed for each link. Additionally, the resource multiplexing scheme can be separately instructed for each link. In addition, the resource multiplexing scheme during the access procedure can be instructed based on whether or not a previous message was transmitted and its contents.
[0126] Meanwhile, measurement configuration information (e.g., MeasConfig) may additionally include an IE indicating a resource multiplexing method. For example, a base station may transmit MeasConfig to a UE. The UE may check the IE(s) included in MeasConfig. MeasConfig may include measurement object information (MeasObjectNR) for which the UE must perform measurements. MeasObjectNR may include the IE(s) defined in Tables 7 to 14 below.
[0127] MeasObjectNR ::= SEQUENCE {ssbFrequency ARFCN-ValueNR OPTIONAL, -- Cond SSBorAssociatedSSBssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond SSBorAssociatedSSBsmtc1 SSB-MTC OPTIONAL, -- Cond SSBorAssociatedSSBsmtc2 SSB-MTC2 OPTIONAL, -- Cond IntraFreqConnectedrefFreqCSI-RS ARFCN-ValueNR OPTIONAL, -- Cond CSI-RSreferenceSignalConfig ReferenceSignalConfig,absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need RabsThreshCSI-RS-Consolidation ThresholdNR OPTIONAL, -- Need RnrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need RnrofCSI-RS-ResourcesToAverage INTEGER (2..maxNrofCSI-RS-ResourcesToAverage) OPTIONAL, -- Need RquantityConfigIndex INTEGER (1..maxNrofQuantityConfig),
[0128] offsetMO Q-OffsetRangeList,cellsToRemoveList PCI-List OPTIONAL, -- Need NcellsToAddModList CellsToAddModList OPTIONAL, -- Need NexcludedCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need NexcludedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need NallowedCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need NallowedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need N...,[[freqBandIndicatorNR FreqBandIndicatorNR OPTIONAL, -- Need RmeasCycleSCell ENUMERATED {sf160, sf256, sf320, sf512, sf640, sf1024, sf1280} OPTIONAL -- Need R]],
[0129] [[associatedMeasGapSSB-r17 MeasGapId-r17 OPTIONAL, -- Need RassociatedMeasGapCSIRS-r17 MeasGapId-r17 OPTIONAL, -- Need Rsmtc4list-r17 SSB-MTC4List-r17 OPTIONAL, -- Need RmeasCyclePSCell-r17 ENUMERATED {ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, spare1}OPTIONAL, -- Cond SCGcellsToAddModListExt-v1710 CellsToAddModListExt-v1710 OPTIONAL -- Need N]],[[associatedMeasGapSSB2-v1720 MeasGapId-r17 OPTIONAL, -- Cond AssociatedGapSSBassociatedMeasGapCSIRS2-v1720 MeasGapId-r17 OPTIONAL -- Cond AssociatedGapCSIRS]]}
[0130] SSB-MTC3List-r16::= SEQUENCE (SIZE(1..4)) OF SSB-MTC3-r16SSB-MTC4List-r17::= SEQUENCE (SIZE(1..3)) OF SSB-MTC4-r17T312-r16 ::= ENUMERATED { ms0, ms50, ms100, ms200, ms300, ms400, ms500, ms1000}ReferenceSignalConfig::= SEQUENCE {ssb-ConfigMobility SSB-ConfigMobility OPTIONAL, -- Need Mcsi-rs-ResourceConfigMobility SetupRelease { CSI-RS-ResourceConfigMobility} OPTIONAL -- Need M}SSB-ConfigMobility::= SEQUENCE {ssb-ToMeasure SetupRelease { SSB-ToMeasure} OPTIONAL, -- Need MderiveSSB-IndexFromCell BOOLEAN,ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, -- Need M...,[[ssb-PositionQCL-Common-r16 SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectrumssb-PositionQCL-CellsToAddModList-r16 SSB-PositionQCL-CellsToAddModList-r16 OPTIONAL, -- Need Nssb-PositionQCL-CellsToRemoveList-r16 PCI-List OPTIONAL -- Need N]],
[0131] [[deriveSSB-IndexFromCellInter-r17 ServCellIndex OPTIONAL, -- Need Rssb-PositionQCL-Common-r17 SSB-PositionQCL-Relation-r17 OPTIONAL, -- Cond SharedSpectrum2ssb-PositionQCL-Cells-r17 SetupRelease {SSB-PositionQCL-CellList-r17} OPTIONAL -- Need M]],[[cca-CellsToAddModList-r17 PCI-List OPTIONAL, -- Need Ncca-CellsToRemoveList-r17 PCI-List OPTIONAL -- Need N]]}Q-OffsetRangeList ::= SEQUENCE {rsrpOffsetSSB Q-OffsetRange DEFAULT dB0,rsrqOffsetSSB Q-OffsetRange DEFAULT dB0,sinrOffsetSSB Q-OffsetRange DEFAULT dB0,rsrpOffsetCSI-RS Q-OffsetRange DEFAULT dB0,rsrqOffsetCSI-RS Q-OffsetRange DEFAULT dB0,sinrOffsetCSI-RS Q-OffsetRange DEFAULT dB0}
[0132] ThresholdNR ::= SEQUENCE{thresholdRSRP RSRP-Range OPTIONAL, -- Need RthresholdRSRQ RSRQ-Range OPTIONAL, -- Need RthresholdSINR SINR-Range OPTIONAL -- Need R}CellsToAddModList ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddModCellsToAddModListExt-v1710 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddModExt-v1710CellsToAddMod ::= SEQUENCE {physCellId PhysCellId,cellIndividualOffset Q-OffsetRangeList}CellsToAddModExt-v1710 ::= SEQUENCE {ntn-PolarizationDL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL, -- Need Rntn-PolarizationUL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL -- Need R}
[0133] RMTC-Config-r16 ::= SEQUENCE {rmtc-Periodicity-r16 ENUMERATED {ms40, ms80, ms160, ms320, ms640},rmtc-SubframeOffset-r16 INTEGER(0..639) OPTIONAL, -- Need MmeasDurationSymbols-r16 ENUMERATED {sym1, sym14or12, sym28or24, sym42or36, sym70or60},rmtc-Frequency-r16 ARFCN-ValueNR,ref-SCS-CP-r16 ENUMERATED {kHz15, kHz30, kHz60-NCP, kHz60-ECP},...,[[rmtc-Bandwidth-r17 ENUMERATED {mhz100, mhz400, mhz800, mhz1600, mhz2000} OPTIONAL, -- Need RmeasDurationSymbols-v1700 ENUMERATED {sym140, sym560, sym1120} OPTIONAL, -- Need Rref-SCS-CP-v1700 ENUMERATED {kHz120, kHz480, kHz960} OPTIONAL, -- Need Rtci-StateInfo-r17 SEQUENCE {tci-StateId-r17 TCI-StateId,ref-ServCellId-r17 ServCellIndex OPTIONAL -- Need R} OPTIONAL -- Need R]],[[ref-BWPId-r17 BWP-Id OPTIONAL -- Need R]]}
[0134] SSB-PositionQCL-CellsToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF SSB-PositionQCL-CellsToAddMod-r16SSB-PositionQCL-CellsToAddMod-r16 ::= SEQUENCE {physCellId-r16 PhysCellId,ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16}SSB-PositionQCL-CellList-r17 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF SSB-PositionQCL-Cell-r17SSB-PositionQCL-Cell-r17 ::= SEQUENCE {physCellId-r17 PhysCellId,ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17}
[0135] At this time, MeasObjectNR may additionally include an IE indicating a resource multiplexing scheme in addition to the IE(s) defined in Tables 7 to 14 indicating a resource multiplexing scheme. For example, MeasObjectNR may include polarization information indicating polarization information for downlink (DL) and uplink (UL) in NTN and TN in CellsToAddModExt, and CellsToAddModExt may further include information indicating a resource multiplexing scheme. The terminal can check the resource multiplexing scheme included in MeasConfig. The resource multiplexing scheme information included in MeasConfig may be indicated by the scheduling node, and more than one scheme may be indicated per terminal. In other words, one resource multiplexing scheme may be set per cell, one resource multiplexing scheme may be set per terminal, or more than one resource multiplexing scheme may be set per terminal.
[0136] In addition, the measurement configuration information described above is not limited to MeasConfig, MeasObjectNR, and may be applied to IEs including configurations related to measurement, for example, synchronization signal block (SSB), channel state information (CSI)-reference signal (RS) (CSI-RS), sounding reference signal (SRS), etc. For example, instead of MeasConfig, SRS-configuration (Config) information, SRS-resource set (SRS-ResourceSet) information, CSI-resource configuration (CSI-ResourceConfig) information, CSI-report configuration (CSI-ReportConfig) information, etc. may be considered. SRS-Config may include IE(s) defined in Tables 15 to 34 below.
[0137] SRS-Config ::= SEQUENCE {srs-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need Nsrs-ResourceSetToAddModList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need Nsrs-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-ResourceId OPTIONAL, -- Need Nsrs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, -- Need Ntpc-Accumulation ENUMERATED {disabled} OPTIONAL, -- Need S...,[[srs-RequestDCI-1-2-r16 INTEGER (1..2) OPTIONAL, -- Need Ssrs-RequestDCI-0-2-r16 INTEGER (1..2) OPTIONAL, -- Need Ssrs-ResourceSetToAddModListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need Nsrs-ResourceSetToReleaseListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need Nsrs-PosResourceSetToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16OPTIONAL, -- Need N.
[0138] srs-PosResourceSetToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSet-r16 OPTIONAL,-- Need Nsrs-PosResourceToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResourceId-r16 OPTIONAL,-- Need Nsrs-PosResourceToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResource-r16 OPTIONAL -- Need N]],[[dci-TriggeringPosResourceSetLink-r18 ENUMERATED { enabled} OPTIONAL -- Need R]]}SRS-ResourceSet ::= SEQUENCE {srs-ResourceSetId SRS-ResourceSetId,srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, -- Cond SetupresourceType CHOICE {aperiodic SEQUENCE {aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1),csi-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebookslotOffset INTEGER (1..32) OPTIONAL, -- Need S...,[[aperiodicSRS-ResourceTriggerList SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2))OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL -- Need M]]},
[0139] semi-persistent SEQUENCE {associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook...},periodic SEQUENCE {associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook...}},usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching},alpha Alpha OPTIONAL, -- Need Sp0 INTEGER (-202..24) OPTIONAL, -- Cond SetuppathlossReferenceRS PathlossReferenceRS-Config OPTIONAL, -- Need Msrs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, -- Need S...,[[pathlossReferenceRSList-r16 SetupRelease { PathlossReferenceRSList-r16} OPTIONAL -- Need M]],[[usagePDC-r17 ENUMERATED {true} OPTIONAL, -- Need R
[0140] availableSlotOffsetList-r17 SEQUENCE (SIZE(1..4)) OF AvailableSlotOffset-r17 OPTIONAL, -- Need RfollowUnifiedTCI-StateSRS-r17 ENUMERATED {enabled} OPTIONAL -- Need R]],[[applyIndicatedTCI-State-r18 ENUMERATED {first, second} OPTIONAL -- Cond FollowUTCI]]}AvailableSlotOffset-r17 ::= INTEGER (0..7)PathlossReferenceRS-Config ::= CHOICE {ssb-Index SSB-Index,csi-RS-Index NZP-CSI-RS-ResourceId}PathlossReferenceRSList-r16 ::= SEQUENCE (SIZE (1..maxNrofSRS-PathlossReferenceRS-r16)) OF PathlossReferenceRS-r16PathlossReferenceRS-r16 ::= SEQUENCE {srs-PathlossReferenceRS-Id-r16 SRS-PathlossReferenceRS-Id-r16,pathlossReferenceRS-r16 PathlossReferenceRS-Config}
[0141] SRS-PathlossReferenceRS-Id-r16 ::= INTEGER (0..maxNrofSRS-PathlossReferenceRS-1-r16)SRS-PosResourceSet-r16 ::= SEQUENCE {srs-PosResourceSetId-r16 SRS-PosResourceSetId-r16,srs-PosResourceIdList-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-PosResourceId-r16OPTIONAL, -- Cond SetupresourceType-r16 CHOICE {aperiodic-r16 SEQUENCE {aperiodicSRS-ResourceTriggerList-r16 SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-1))OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL, -- Need M...},semi-persistent-r16 SEQUENCE {...},periodic-r16 SEQUENCE {...}},alpha-r16 Alpha OPTIONAL, -- Need Sp0-r16 INTEGER (-202..24) OPTIONAL, -- Cond SetuppathlossReferenceRS-Pos-r16 CHOICE {ssb-IndexServing-r16 SSB-Index,ssb-Ncell-r16 SSB-InfoNcell-r16,dl-PRS-r16 DL-PRS-Info-r16} OPTIONAL, -- Need M...,
[0142] [[srs-PosHyperSFN-Index-r18 ENUMERATED {even0, odd1} OPTIONAL -- Need S]]}SRS-ResourceSetId ::= INTEGER (0..maxNrofSRS-ResourceSets-1)SRS-PosResourceSetId-r16 ::= INTEGER (0..maxNrofSRS-PosResourceSets-1-r16)SRS-Resource ::= SEQUENCE {srs-ResourceId SRS-ResourceId,nrofSRS-Ports ENUMERATED {port1, ports2, ports4},ptrs-PortIndex ENUMERATED {n0, n1} OPTIONAL, -- Need RtransmissionComb CHOICE {n2 SEQUENCE {combOffset-n2 INTEGER (0..1),cyclicShift-n2 INTEGER (0..7)},n4 SEQUENCE {combOffset-n4 INTEGER (0..3),cyclicShift-n4 INTEGER (0..11)}},
[0143] resourceMapping SEQUENCE {startPosition INTEGER (0..5),nrofSymbols ENUMERATED {n1, n2, n4},repetitionFactor ENUMERATED {n1, n2, n4}},freqDomainPosition INTEGER (0..67),freqDomainShift INTEGER (0..268),freqHopping SEQUENCE {c-SRS INTEGER (0..63),b-SRS INTEGER (0..3),b-hop INTEGER (0..3)},groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping},resourceType CHOICE {aperiodic SEQUENCE {...},semi-persistent SEQUENCE {periodicityAndOffset-sp SRS-PeriodicityAndOffset,...},periodic SEQUENCE {periodicityAndOffset-p SRS-PeriodicityAndOffset,...}},
[0144] sequenceId INTEGER (0..1023),spatialRelationInfo SRS-SpatialRelationInfo OPTIONAL, -- Need R...,[[resourceMapping-r16 SEQUENCE {startPosition-r16 INTEGER (0..13),nrofSymbols-r16 ENUMERATED {n1, n2, n4},repetitionFactor-r16 ENUMERATED {n1, n2, n4}} OPTIONAL -- Need R]],[[spatialRelationInfo-PDC-r17 SetupRelease { SpatialRelationInfo-PDC-r17} OPTIONAL, -- Need MresourceMapping-r17 SEQUENCE {startPosition-r17 INTEGER (0..13),nrofSymbols-r17 ENUMERATED {n1, n2, n4, n8, n10, n12, n14},repetitionFactor-r17 ENUMERATED {n1, n2, n4, n5, n6, n7, n8, n10, n12, n14}} OPTIONAL, -- Need RpartialFreqSounding-r17 SEQUENCE {startRBIndexFScaling-r17 CHOICE{startRBIndexAndFreqScalingFactor2-r17 INTEGER (0..1),startRBIndexAndFreqScalingFactor4-r17 INTEGER (0..3)},enableStartRBHopping-r17 ENUMERATED {enable} OPTIONAL -- Need R} OPTIONAL, -- Need R
[0145] transmissionComb-n8-r17 SEQUENCE {combOffset-n8-r17 INTEGER (0..7),cyclicShift-n8-r17 INTEGER (0..5)} OPTIONAL, -- Need Rsrs-TCI-State-r17 CHOICE {srs-UL-TCI-State TCI-UL-StateId-r17,srs-DLorJointTCI-State TCI-StateId} OPTIONAL -- Need R]],[[repetitionFactor-v1730 ENUMERATED {n3} OPTIONAL, -- Need Rsrs-DLorJointTCI-State-v1730 SEQUENCE {cellAndBWP-r17 ServingCellAndBWP-Id-r17} OPTIONAL -- Cond DLorJointTCI-SRS]],
[0146] [[nrofSRS-Ports-n8-r18 ENUMERATED {ports8, ports8tdm} OPTIONAL, -- Need RcombOffsetHopping-r18 SEQUENCE {hoppingId-r18 INTEGER (0..1023) OPTIONAL, -- Need RhoppingSubset-r18 CHOICE {transmissionComb-n4 BIT STRING (SIZE (4)),transmissionComb-n8 BIT STRING (SIZE (8))} OPTIONAL, -- Need RhoppingWithRepetition-r18 ENUMERATED {symbol, repetition} OPTIONAL -- Need R} OPTIONAL, -- Need RcyclicShiftHopping-r18 SEQUENCE {hoppingId-r18 INTEGER (0..1023) OPTIONAL, -- Need RhoppingSubset-r18 CHOICE {transmissionComb-n2 BIT STRING (SIZE (8)),transmissionComb-n4 BIT STRING (SIZE (12)),transmissionComb-n8 BIT STRING (SIZE (6))} OPTIONAL, -- Need RhoppingFinerGranularity-r18 ENUMERATED {enable} OPTIONAL -- Need R} OPTIONAL -- Need R]]}
[0147] SRS-PosResource-r16::= SEQUENCE {srs-PosResourceId-r16 SRS-PosResourceId-r16,transmissionComb-r16 CHOICE {n2-r16 SEQUENCE {combOffset-n2-r16 INTEGER (0..1),cyclicShift-n2-r16 INTEGER (0..7)},n4-r16 SEQUENCE {combOffset-n4-r16 INTEGER (0..3),cyclicShift-n4-r16 INTEGER (0..11)},n8-r16 SEQUENCE {combOffset-n8-r16 INTEGER (0..7),cyclicShift-n8-r16 INTEGER (0..5)},...},resourceMapping-r16 SEQUENCE {startPosition-r16 INTEGER (0..13),nrofSymbols-r16 ENUMERATED {n1, n2, n4, n8, n12}},freqDomainShift-r16 INTEGER (0..268),freqHopping-r16 SEQUENCE {c-SRS-r16 INTEGER (0..63),...},
[0148] groupOrSequenceHopping-r16 ENUMERATED { neither, groupHopping, sequenceHopping},resourceType-r16 CHOICE {aperiodic-r16 SEQUENCE {slotOffset-r16 INTEGER (1..32) OPTIONAL, -- Need S...},semi-persistent-r16 SEQUENCE {periodicityAndOffset-sp-r16 SRS-PeriodicityAndOffset-r16,...,[[periodicityAndOffset-sp-Ext-r16 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL -- Need R]]},periodic-r16 SEQUENCE {periodicityAndOffset-p-r16 SRS-PeriodicityAndOffset-r16,...,[[periodicityAndOffset-p-Ext-r16 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL -- Need R]]}},
[0149] sequenceId-r16 INTEGER (0..65535),spatialRelationInfoPos-r16 SRS-SpatialRelationInfoPos-r16 OPTIONAL, -- Need R...,[[srs-PosHyperSFN-Index-r18 ENUMERATED {even0, odd1} OPTIONAL, --Need StxHoppingConfig-r18 TxHoppingConfig-r18 OPTIONAL --Need R]]}SRS-SpatialRelationInfo ::= SEQUENCE {servingCellId ServCellIndex OPTIONAL, -- Need SreferenceSignal CHOICE {ssb-Index SSB-Index,csi-RS-Index NZP-CSI-RS-ResourceId,srs SEQUENCE {resourceId SRS-ResourceId,uplinkBWP BWP-Id}}}
[0150] SRS-SpatialRelationInfoPos-r16 ::= CHOICE {servingRS-r16 SEQUENCE {servingCellId ServCellIndex OPTIONAL, -- Need SreferenceSignal-r16 CHOICE {ssb-IndexServing-r16 SSB-Index,csi-RS-IndexServing-r16 NZP-CSI-RS-ResourceId,srs-SpatialRelation-r16 SEQUENCE {resourceSelection-r16 CHOICE {srs-ResourceId-r16 SRS-ResourceId,srs-PosResourceId-r16 SRS-PosResourceId-r16},uplinkBWP-r16 BWP-Id}}},ssb-Ncell-r16 SSB-InfoNcell-r16,dl-PRS-r16 DL-PRS-Info-r16}
[0151] SSB-Configuration-r16 ::= SEQUENCE {ssb-Freq-r16 ARFCN-ValueNR,halfFrameIndex-r16 ENUMERATED {zero, one},ssbSubcarrierSpacing-r16 SubcarrierSpacing,ssb-Periodicity-r16 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2,spare1} OPTIONAL, -- Need Ssfn0-Offset-r16 SEQUENCE {sfn-Offset-r16 INTEGER (0..1023),integerSubframeOffset-r16 INTEGER (0..9) OPTIONAL -- Need R} OPTIONAL, -- Need Rsfn-SSB-Offset-r16 INTEGER (0..15),ss-PBCH-BlockPower-r16 INTEGER (-60..50) OPTIONAL -- Cond Pathloss}SSB-InfoNcell-r16 ::= SEQUENCE {physicalCellId-r16 PhysCellId,ssb-IndexNcell-r16 SSB-Index OPTIONAL, -- Need Sssb-Configuration-r16 SSB-Configuration-r16 OPTIONAL -- Need S}DL-PRS-Info-r16 ::= SEQUENCE {dl-PRS-ID-r16 INTEGER (0..255),dl-PRS-ResourceSetId-r16 INTEGER (0..7),dl-PRS-ResourceId-r16 INTEGER (0..63) OPTIONAL -- Need S}
[0152] SRS-ResourceId ::= INTEGER (0..maxNrofSRS-Resources-1)SRS-PosResourceId-r16 ::= INTEGER (0..maxNrofSRS-PosResources-1-r16)SRS-PeriodicityAndOffset ::= CHOICE {sl1 NULL,sl2 INTEGER(0..1),sl4 INTEGER(0..3),sl5 INTEGER(0..4),sl8 INTEGER(0..7),sl10 INTEGER(0..9),sl16 INTEGER(0..15),sl20 INTEGER(0..19),sl32 INTEGER(0..31),sl40 INTEGER(0..39),sl64 INTEGER(0..63),sl80 INTEGER(0..79),sl160 INTEGER(0..159),sl320 INTEGER(0..319),sl640 INTEGER(0..639),sl1280 INTEGER(0..1279),sl2560 INTEGER(0..2559)}
[0153] SRS-PeriodicityAndOffset-r16 ::= CHOICE {sl1 NULL,sl2 INTEGER(0..1),sl4 INTEGER(0..3),sl5 INTEGER(0..4),sl8 INTEGER(0..7),sl10 INTEGER(0..9),sl16 INTEGER(0..15),sl20 INTEGER(0..19),sl32 INTEGER(0..31),sl40 INTEGER(0..39),sl64 INTEGER(0..63),sl80 INTEGER(0..79),sl160 INTEGER(0..159),sl320 INTEGER(0..319),sl640 INTEGER(0..639),sl1280 INTEGER(0..1279),sl2560 INTEGER(0..2559),sl5120 INTEGER(0..5119),sl10240 INTEGER(0..10239),sl40960 INTEGER(0..40959),sl81920 INTEGER(0..81919),...}
[0154] SRS-PeriodicityAndOffsetExt-r16 ::= CHOICE {sl128 INTEGER(0..127),sl256 INTEGER(0..255),sl512 INTEGER(0..511),sl20480 INTEGER(0..20479)}SpatialRelationInfo-PDC-r17 ::= SEQUENCE {referenceSignal CHOICE {ssb-Index SSB-Index,csi-RS-Index NZP-CSI-RS-ResourceId,dl-PRS-PDC NR-DL-PRS-ResourceID-r17,srs SEQUENCE {resourceId SRS-ResourceId,uplinkBWP BWP-Id},...},...}TxHoppingConfig-r18 ::= SEQUENCE {overlapValue-r18 ENUMERATED {zeroRB, oneRB, twoRB, fourRB},numberOfHops INTEGER(1..6),slotOffsetForRemainingHopsList-r18 SEQUENCE (SIZE (1..maxNrofHops-r18-1) ) OF SlotOffsetForRemainingHops-r18,...}
[0155] SlotOffsetForRemainingHops-r18 ::= SEQUENCE {slotOffsetRemainingHops-r18 CHOICE {aperiodic-r18 SEQUENCE {slotOffset-r18 INTEGER (1..32) OPTIONAL, -- Need SstartPosition-r18 INTEGER (0..13) OPTIONAL, -- Need S...},semi-persistent-r18 SEQUENCE {periodicityAndOffset-sp-r18 SRS-PeriodicityAndOffset-r16 OPTIONAL, -- Need RperiodicityAndOffset-sp-Ext-r18 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL, -- Need R
[0156] ...},periodic-r18 SEQUENCE {periodicityAndOffset-p-r18 SRS-PeriodicityAndOffset-r16 OPTIONAL, -- Need RperiodicityAndOffset-p-Ext-r18 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL, -- Need R...},...}}
[0157] CSI-ResourceConfig may contain the IE(s) defined in Table 35 below.
[0158] CSI-ResourceConfig ::= SEQUENCE { csi-ResourceConfigId CSI-ResourceConfigId,csi-RS-ResourceSetList CHOICE { nzp-CSI-RS-SSB SEQUENCE { nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetIdOPTIONAL, -- Need Rcsi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL -- Need R},csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId},bwp-Id BWP-Id,resourceType ENUMERATED { aperiodic, semiPersistent, periodic},...,[[csi-SSB-ResourceSetListExt-r17 CSI-SSB-ResourceSetId OPTIONAL -- Need R]]}
[0159] Additionally, CSI-ReportConfig may contain the IE(s) defined in Table 36 to Table 40 below.
[0160] CSI-ReportConfig ::= SEQUENCE {reportConfigId CSI-ReportConfigId,carrier ServCellIndex OPTIONAL, -- Need SresourcesForChannelMeasurement CSI-ResourceConfigId,csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need Rnzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need RreportConfigType CHOICE {periodic SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUCCH SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUSCH SEQUENCE {reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320},reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),p0alpha P0-PUSCH-AlphaSetId},
[0161] aperiodic SEQUENCE {reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)}},reportQuantity CHOICE {none NULL,cri-RI-PMI-CQI NULL,cri-RI-i1 NULL,cri-RI-i1-CQI SEQUENCE {pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL -- Need S},cri-RI-CQI NULL,cri-RSRP NULL,ssb-Index-RSRP NULL,cri-RI-LI-PMI-CQI NULL},reportFreqConfiguration SEQUENCE {cqi-FormatIndicator ENUMERATED { widebandCQI, subbandCQI} OPTIONAL, -- Need Rpmi-FormatIndicator ENUMERATED { widebandPMI, subbandPMI} OPTIONAL, -- Need R
[0162] csi-ReportingBand CHOICE {subbands3 BIT STRING(SIZE(3)),subbands4 BIT STRING(SIZE(4)),subbands5 BIT STRING(SIZE(5)),subbands6 BIT STRING(SIZE(6)),subbands7 BIT STRING(SIZE(7)),subbands8 BIT STRING(SIZE(8)),subbands9 BIT STRING(SIZE(9)),subbands10 BIT STRING(SIZE(10)),subbands11 BIT STRING(SIZE(11)),subbands12 BIT STRING(SIZE(12)),subbands13 BIT STRING(SIZE(13)),subbands14 BIT STRING(SIZE(14)),subbands15 BIT STRING(SIZE(15)),subbands16 BIT STRING(SIZE(16)),subbands17 BIT STRING(SIZE(17)),subbands18 BIT STRING(SIZE(18)),...,
[0163] subbands19-v1530 BIT STRING(SIZE(19))} OPTIONAL -- Need S} OPTIONAL, -- Need RtimeRestrictionForChannelMeasurements ENUMERATED {configured, notConfigured},timeRestrictionForInterferenceMeasurements ENUMERATED {configured, notConfigured},codebookConfig CodebookConfig OPTIONAL, -- Need Rdummy ENUMERATED {n1, n2} OPTIONAL, -- Need RgroupBasedBeamReporting CHOICE {enabled NULL,disabled SEQUENCE {nrofReportedRS ENUMERATED {n1, n2, n3, n4} OPTIONAL -- Need S}},cqi-Table ENUMERATED {table1, table2, table3, table4-r17} OPTIONAL, -- Need RsubbandSize ENUMERATED {value1, value2},non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, -- Need R...,
[0164] [[semiPersistentOnPUSCH-v1530 SEQUENCE {reportSlotConfig-v1530 ENUMERATED {sl4, sl8, sl16}} OPTIONAL -- Need R]],[[semiPersistentOnPUSCH-v1610 SEQUENCE {reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need RreportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R} OPTIONAL, -- Need Raperiodic-v1610 SEQUENCE {reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need RreportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R} OPTIONAL, -- Need RreportQuantity-r16 CHOICE {cri-SINR-r16 NULL,ssb-Index-SINR-r16 NULL} OPTIONAL, -- Need RcodebookConfig-r16 CodebookConfig-r16 OPTIONAL -- Need R]],
[0165] [[cqi-BitsPerSubband-r17 ENUMERATED {bits4} OPTIONAL, -- Need RgroupBasedBeamReporting-v1710 SEQUENCE {nrofReportedGroups-r17 ENUMERATED {n1, n2, n3, n4}} OPTIONAL, -- Need RcodebookConfig-r17 CodebookConfig-r17 OPTIONAL, -- Need RsharedCMR-r17 ENUMERATED {enable} OPTIONAL, -- Need Rcsi-ReportMode-r17 ENUMERATED {mode1, mode2} OPTIONAL, -- Need RnumberOfSingleTRP-CSI-Mode1-r17 ENUMERATED {n0, n1, n2} OPTIONAL, -- Need RreportQuantity-r17 CHOICE {cri-RSRP-Index-r17 NULL,ssb-Index-RSRP-Index-r17 NULL,cri-SINR-Index-r17 NULL,ssb-Index-SINR-Index-r17 NULL} OPTIONAL -- Need R]],
[0166] [[semiPersistentOnPUSCH-v1720 SEQUENCE {reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need RreportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need RreportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL -- Need R} OPTIONAL, -- Need Raperiodic-v1720 SEQUENCE {reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need RreportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need RreportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL -- Need R} OPTIONAL -- Need R]],
[0167] [[codebookConfig-v1730 CodebookConfig-v1730 OPTIONAL -- Need R]],[[groupBasedBeamReporting-v1800 SEQUENCE {reportingMode-r18 ENUMERATED {jointULDL, onlyUL}} OPTIONAL, -- Need RreportQuantity-r18 TDCP-r18 OPTIONAL, -- Need RcodebookConfig-r18 CodebookConfig-r18 OPTIONAL, -- Need Rcsi-ReportSubConfigToAddModList-r18 SEQUENCE (SIZE (2..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfig-r18OPTIONAL, -- Need Ncsi-ReportSubConfigToReleaseList-r18 SEQUENCE (SIZE (2..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfigId-r18OPTIONAL -- Need N]]}
[0168] CSI-ReportPeriodicityAndOffset ::= CHOICE {slots4 INTEGER(0..3),slots5 INTEGER(0..4),slots8 INTEGER(0..7),slots10 INTEGER(0..9),slots16 INTEGER(0..15),slots20 INTEGER(0..19),slots40 INTEGER(0..39),slots80 INTEGER(0..79),slots160 INTEGER(0..159),slots320 INTEGER(0..319)}
[0169] PortIndexFor8Ranks ::= CHOICE {portIndex8 SEQUENCE{rank1-8 PortIndex8 OPTIONAL, -- Need Rrank2-8 SEQUENCE(SIZE(2)) OF PortIndex8 OPTIONAL, -- Need Rrank3-8 SEQUENCE(SIZE(3)) OF PortIndex8 OPTIONAL, -- Need Rrank4-8 SEQUENCE(SIZE(4)) OF PortIndex8 OPTIONAL, -- Need Rrank5-8 SEQUENCE(SIZE(5)) OF PortIndex8 OPTIONAL, -- Need Rrank6-8 SEQUENCE(SIZE(6)) OF PortIndex8 OPTIONAL, -- Need Rrank7-8 SEQUENCE(SIZE(7)) OF PortIndex8 OPTIONAL, -- Need Rrank8-8 SEQUENCE(SIZE(8)) OF PortIndex8 OPTIONAL -- Need R},portIndex4 SEQUENCE{rank1-4 PortIndex4 OPTIONAL, -- Need Rrank2-4 SEQUENCE(SIZE(2)) OF PortIndex4 OPTIONAL, -- Need Rrank3-4 SEQUENCE(SIZE(3)) OF PortIndex4 OPTIONAL, -- Need Rrank4-4 SEQUENCE(SIZE(4)) OF PortIndex4 OPTIONAL -- Need R},portIndex2 SEQUENCE{rank1-2 PortIndex2 OPTIONAL, -- Need Rrank2-2 SEQUENCE(SIZE(2)) OF PortIndex2 OPTIONAL -- Need R},portIndex1 NULL}
[0170] PortIndex8::= INTEGER (0..7)PortIndex4::= INTEGER (0..3)PortIndex2::= INTEGER (0..1)TDCP-r18 ::= SEQUENCE {delayDSetofLengthY-r18 SEQUENCE (SIZE (1.. maxNrofdelayD-r18)) OF DelayD,phaseReporting-r18 ENUMERATED {enable} OPTIONAL -- Need R}DelayD ::= ENUMERATED { symb4, slot1, slot2, slot3, slot4, slot5, slot6, slot10}
[0171] Additionally, at least one of SRS-Config, and / or CSI-ResourceConfig, and / or CSI-ReportConfig, as exemplified using the tables above, may further include an IE indicating a resource multiplexing method in addition to the IEs defined in each.
[0172] Additionally, the location where information indicating the resource multiplexing method is included can be set in the IE itself as exemplified above, an IE including measurement-related settings, a parent IE of an IE defined in SRS-Config, and / or CSI-ResourceConfig, and / or CSI-ReportConfig, or a child IE of an IE defined in SRS-Config, and / or CSI-ResourceConfig, and / or CSI-ReportConfig. For example, the resource multiplexing setting related IE can be included in the SRS-ResourceSet itself, or included in a child IE of the SRS-ResourceSet, or included in a parent IE including the SRS-ResourceSet.
[0173] As described above, resource multiplexing schemes can be considered in communication networks.
[0174] [Resource Multiplexing Procedure]
[0175] Below, various resource multiplexing procedures according to the present disclosure are described. The resource multiplexing procedures described below are intended to aid understanding of the present disclosure and should not be construed as limited to a single multiplexing procedure described as an example.
[0176] FIG. 7 is a flowchart illustrating a resource multiplexing procedure according to the first embodiment of the present disclosure.
[0177] Referring to FIG. 7, a resource multiplexing procedure may be performed between a first node and a second node. For example, if the first node is a transmitting node, the second node may be a receiving node, and if the first node is a receiving node, the second node may be a transmitting node. If the first node and the second node in FIG. 7 are communication nodes of a mobile communication system, the first node may be a base station, and the second node may be a UE. The first node and the second node illustrated in FIG. 7 may include all or at least a portion of the configuration of FIG. 2 described above. In addition, the first node and the second node may have additional configurations in addition to the configuration described in FIG. 2. For example, if the first node is a base station of a mobile communication system, the first node may further include an interface for connecting to a core network and / or an interface for connecting to an adjacent base station, in addition to the configuration illustrated in FIG. 2. In addition, if the second node is a UE of a mobile communication system, the second node may further include a battery module, various sensor modules, etc. to ensure mobility.
[0178] In step S710, the second node may report its resource multiplexing capability information to the first node. Therefore, in step S710, the first node may receive the resource multiplexing capability information from the second node. The reporting of the resource multiplexing capability information in step S710 may be optional. In other words, the reporting of the resource multiplexing capability information may be omitted depending on the situation.
[0179] In step S720, the first node may transmit resource multiplexing settings and resource multiplexing instructions to the second node based on the resource multiplexing capability information received in step S710 or without receiving the resource multiplexing capability information in step S710. Accordingly, the second node may receive resource multiplexing settings and resource multiplexing instructions from the first node in step S720.
[0180] In Fig. 7, step S720 is illustrated as a single step, but the detailed procedure may be divided into multiple steps and performed. Below, the cases where step S720 is performed as a single procedure, the cases where step S720 is performed as two procedures, and the cases where step S720 is performed as three procedures are described, respectively. Furthermore, for the convenience of explaining step S720, it is assumed that the first node is a 3GPP NR base station, and the second node is a 3GPP NR UE.
[0181] <S720단계가 하나의 단계로 수행되는 경우>
[0182] The base station can transmit resource multiplexing configuration information and resource multiplexing indication information to the UE in a single message. At this time, since the resource multiplexing configuration information and the resource multiplexing indication information are transmitted in a single step, the resource multiplexing configuration information may be the same information as the resource multiplexing indication information. Therefore, the base station can transmit either the resource multiplexing configuration information or the resource multiplexing indication information to the UE. Therefore, the base station can transmit the resource multiplexing configuration information or the resource multiplexing indication information to the UE using any one of the DCI transmitted via RRC signaling, MAC-CE, or PDCCH. Therefore, the UE can receive the resource multiplexing configuration information or the resource multiplexing indication information from the base station via any one of the DCI transmitted via RRC signaling, MAC-CE, or PDCCH.
[0183] If resource multiplexing configuration information or resource multiplexing indication information is transmitted to the UE using either RRC signaling or MAC-CE, the RRC signaling or MAC-CE may further include information on the time (or point in time) at which the resource multiplexing configuration information or resource multiplexing indication information will be applied. Accordingly, a UE that receives resource multiplexing configuration information or resource multiplexing indication information using either RRC signaling or MAC-CE can perform resource multiplexing from the time indicated (or set) by the RRC signaling or MAC-CE.
[0184] As another example, the base station can transmit resource multiplexing configuration information or resource multiplexing indication information to the UE using DCI, which is a physical layer (PHY) signaling. Accordingly, the UE can receive resource multiplexing configuration information or resource multiplexing indication information through DCI. The UE that has received resource multiplexing configuration information or resource multiplexing indication information can perform resource multiplexing based on the resource multiplexing configuration information or resource multiplexing indication information from the time when the DCI is applied or from a preset specific time after receiving the DCI.
[0185] <S720단계가 2개의 세부 단계로 수행되는 경우1>
[0186] A base station can transmit to the UE two or more resource multiplexing configuration information that the base station can use via RRC signaling. Accordingly, the UE can receive two or more resource multiplexing configuration information that the base station can use via RRC signaling.
[0187] Afterwards, the base station can instruct the UE via MAC-CE which resource multiplexing indication information to use for communication with the UE among two or more resource multiplexing configurations that the base station can use. When the resource multiplexing indication information is transmitted to the UE via MAC-CE, the MAC-CE may further include information on the time (or point in time) at which resource multiplexing will be performed. Accordingly, the UE can receive the resource multiplexing indication information via MAC-CE. In addition, the UE can apply the indicated resource multiplexing method based on the time (or point in time) at which resource multiplexing will be performed included in the MAC-CE.
[0188] <S720단계가 2개의 세부 단계로 수행되는 경우2>
[0189] A base station can transmit to the UE two or more resource multiplexing configuration information that the base station can use using RRC signaling, which is a higher layer signaling. Accordingly, the UE can receive two or more resource multiplexing configuration information that the base station can use through RRC signaling.
[0190] Afterwards, the base station can instruct the UE through the physical layer (PHY) PDCCH which resource multiplexing indication information to use for communication with the UE among two or more resource multiplexing configurations that the base station can use. In other words, the base station can instruct the UE about the resource multiplexing indication information using the DCI. Therefore, the UE can receive the resource multiplexing indication information through the DCI. In addition, when the UE receives the DCI, the UE can perform resource multiplexing based on the resource multiplexing indication information from the time when the DCI is applied or from a specific time point set in advance after receiving the DCI.
[0191] <S720단계가 2개의 세부 단계로 수행되는 경우3>
[0192] A base station can transmit to the UE two or more resource multiplexing configuration information that the base station can use using MAC-CE. Accordingly, the UE can receive two or more resource multiplexing configuration information that the base station can use via MAC-CE.
[0193] Afterwards, the base station can instruct the UE through the physical layer (PHY) PDCCH which resource multiplexing indication information to use for communication with the UE among two or more resource multiplexing configurations that the base station can use. In other words, the base station can instruct the UE about the resource multiplexing indication information using the DCI. Therefore, the UE can receive the resource multiplexing indication information through the DCI. In addition, when the UE receives the DCI, the UE can perform resource multiplexing based on the resource multiplexing indication information from the time when the DCI is applied or from a specific time point set in advance after receiving the DCI.
[0194] <S720단계가 3개의 세부 단계로 수행되는 경우>
[0195] A base station can transmit to the UE two or more resource multiplexing configuration information that the base station can use via RRC signaling. Accordingly, the UE can receive two or more resource multiplexing configuration information that the base station can use via RRC signaling.
[0196] Thereafter, the base station can instruct the UE via MAC-CE which resource multiplexing configurations to activate one or more resource multiplexing configurations. Accordingly, the UE can receive the resource multiplexing configuration information via MAC-CE.
[0197] The base station can use DCI to instruct the UE on one resource multiplexing instruction to use for communication with the UE among the activated resource multiplexing instructions. Accordingly, the UE can receive the resource multiplexing instruction information through DCI. When receiving DCI containing the resource multiplexing instruction information, the UE can perform resource multiplexing based on the resource multiplexing instruction information from the time the DCI is applied or from a preset specific time point after receiving the DCI.
[0198] In step S720, the second node can receive resource multiplexing setting information and resource multiplexing instruction information based on the embodiments described above.
[0199] In step S730, the second node may transmit resource-multiplexed data to the first node based on the indicated resource multiplexing method. If the first node and the second node as exemplified in FIG. 7 are a base station and a UE of a 5G NR communication system, the data transmitted by the second node may be data transmitted in an uplink. Accordingly, a transmission request message (e.g., a scheduling request message) requesting transmission for uplink transmission may be transmitted to the first node. In addition, the first node may further include a step of transmitting an approval message (e.g., a scheduling grant message) to the second node in response to the transmission request message, which approves the transmission.
[0200] If the first node and the second node communicate based on the 3GPP NR communication standard, it should be noted that the procedure of the second node transmitting a scheduling request message to the first node and the procedure of the first node transmitting a scheduling grant message to the second node in the example of FIG. 7 may be performed before step S730 and are not illustrated in FIG. 7. In addition, if the communication is based on the 3GPP NR communication standard, the scheduling grant message may be transmitted to the UE in addition to the resource multiplexing configuration information and / or included in the resource multiplexing indication information, without being performed as a separate step.
[0201] If communication is based on the 3GPP NR communication standard, the scheduling request message / scheduling grant message / resource multiplexing configuration / resource multiplexing indication in the UE's access procedure, for example, the random access procedure, may be replaced with the message signaling of the previous stage or may be included in the message signaling of the previous stage.
[0202] FIG. 8 is a flowchart illustrating a resource multiplexing procedure according to a second embodiment of the present disclosure.
[0203] Referring to FIG. 8, a resource multiplexing procedure may be performed between a first node and a second node. For example, if the first node is a transmitting node, the second node may be a receiving node, and if the first node is a receiving node, the second node may be a transmitting node. If the first node and the second node in FIG. 8 are communication nodes of a mobile communication system, the first node may be a base station, and the second node may be a UE. The first node and the second node illustrated in FIG. 8 may include all or at least a portion of the configuration of FIG. 2 described above. In addition, the first node and the second node may have additional configurations in addition to the configuration described in FIG. 2. For example, if the first node is a base station of a mobile communication system, the first node may further include an interface for connecting to a core network and / or an interface for connecting to an adjacent base station, in addition to the configuration illustrated in FIG. 2. In addition, if the second node is a UE of a mobile communication system, the second node may further include a battery module, various sensor modules, etc. to ensure mobility.
[0204] In step S800, the first node may transmit (or broadcast) a resource multiplexing capability notification message to the second node. The resource multiplexing capability notification message may include information indicating whether the first node has resource multiplexing capability or not. The resource multiplexing capability notification message may also include information about resource multiplexing capabilities that the first node can use. Accordingly, in step S800, the second node may receive the resource multiplexing capability notification message of the first node from the second node. The second node may obtain information about the presence of resource multiplexing capability and / or information about resource multiplexing capabilities that the first node can use. As illustrated in FIG. 8, step S800 may be optionally performed. In other words, the resource multiplexing capability notification message transmitted (or broadcast) by the first node may be omitted depending on the situation.
[0205] In step S810, the second node may report the resource multiplexing capability information of the second node to the first node. Accordingly, in step S810, the first node may receive the resource multiplexing capability information of the second node from the second node. Step S810 may be transmitted in response to step S800, or may be performed independently of step S800. Furthermore, as illustrated in FIG. 8, reporting of the resource multiplexing capability information in step S810 may be performed selectively. In other words, reporting of the resource multiplexing capability information may be omitted depending on the situation.
[0206] In step S820, the first node may transmit resource multiplexing settings and resource multiplexing instructions to the second node based on the resource multiplexing capability information received in step S810 or without receiving step S810. Accordingly, the second node may receive resource multiplexing settings and resource multiplexing instructions from the first node in step S820. Step S820 may be performed as a single procedure, a two-step procedure, or a three-step procedure. The detailed procedures may be the same as those described above in FIG. 7. Therefore, a duplicate description will be omitted.
[0207] In step S820, the second node may receive resource multiplexing configuration information and resource multiplexing instruction information. In step S830, the second node may transmit resource-multiplexed data to the first node based on the indicated resource multiplexing method. If the first node and the second node as exemplified in FIG. 8 are a base station and a UE of a 5G NR communication system, the data transmitted by the second node may be data transmitted in an uplink. Accordingly, a transmission request (e.g., scheduling request) message requesting transmission for uplink transmission may be transmitted to the first node. In addition, the first node may further include a step of transmitting an approval message (e.g., scheduling grant) message approving transmission to the second node in response to the transmission request message. The content described above in FIG. 7 may also be equally applied to the scheduling request message and the scheduling grant message.
[0208] [Resource Multiplication Configuration / Indication Method]
[0209] The resource multiplexing described in FIGS. 7 and 8 above can utilize, for example, orthogonal sequences. An example of an orthogonal sequence is an orthogonal cover code (OCC). For convenience of explanation, the following description will describe a case where resource multiplexing is performed using an orthogonal sequence.
[0210] When the second node transmits data by multiplexing resources, the second transmitting node can transmit the multiplexed data using an orthogonal sequence. More specifically, if the data that the second node wants to transmit is an input sequence y(j), the orthogonal sequence is w(i), and the output sequence is z(l), then the output sequence z(l) can have a relationship as shown in the following mathematical expression 1.
[0211]
[0212] In mathematical expression 1, the input sequence y(j) can generate the output sequence z(l) (hereinafter z) by resource multiplexing using the orthogonal sequence w(i). The input sequence y (hereinafter y) can be a set of complex-valued modulation symbol(s). The output sequence z(l) (hereinafter z), which is a set of complex-valued modulation symbol(s), can be generated using the orthogonal sequence w(i) (hereinafter w). In addition, another input sequence y' can generate the output sequence z' using another orthogonal sequence w'. In this case, even if z' overlaps with z, since w and w' are orthogonal, z can be distinguished from z' using w. In other words, different input sequences y and y' can be output as the output sequences z and z' using different orthogonal sequences w and w', respectively. And since z and z' can be distinguished by orthogonal sequences, z and z' can be resource-multiplexed sequences using orthogonal sequences. In this case, when the length of the sequence is L, the orthogonal sequence w can be defined as in the following mathematical expression 2.
[0213]
[0214] Therefore, determining / indicating w may be essential for setting / indicating resource multiplexing. The orthogonal sequence w may be determined or indicated in various ways depending on the situation. For example, the orthogonal sequence w may be indicated by DCI of the PHY layer or by MAC-CE, MAC message, RRC message, and / or RRC signaling of upper layers.
[0215] As another example, an orthogonal sequence w can be determined within a set of predefined orthogonal sequences w (hereinafter, a sequence book). When constructing a set for orthogonal sequences w, the sequence book must be composed of different orthogonal sequences. When a sequence book is determined to have a total of L sequences, the sequence book composed of the L sequences can be referred to as a "nominal sequence book." The set of L sequences included in the nominal sequence book can be determined as shown in the following mathematical expression 3.
[0216]
[0217] Among the sets of L sequences included in the nominal sequence book of mathematical expression 3, any nth sequence and any mth sequence can be orthogonal, and n and m can each be natural numbers. In other words, it can be seen that the nth sequence and any mth sequence have a relationship as shown in mathematical expression 4 below.
[0218]
[0219] <First embodiment of orthogonal sequence configuration>
[0220] According to the first embodiment of the present disclosure, if each of the L sequences (L is a natural number) included in the nominal sequence book of mathematical formula 3 is orthogonal as in mathematical formula 4, the present disclosure does not place any special restrictions on the type of the sequence. In other words, if each of the sequences in the set of L sequences satisfies mutual orthogonality, any sequence may be used as the type of the sequence.
[0221] In addition, an actual sequence book can be derived from a nominal sequence book. For example, the actual sequence book can be composed of only N sequence(s) (where N is a natural number) randomly among the L sequences included in the nominal sequence book. In other words, the total number of orthogonal sequences can be L included in the nominal sequence book, and the sequences included in the actually used sequence book can be N sequences randomly selected from L. Therefore, the number N of sequences included in the actual orthogonal sequence book can be equal to or less than the number L of orthogonal sequences included in the nominal sequence book.
[0222] If the number L of orthogonal sequences included in the nominal sequence book is the same as the number N of orthogonal sequences included in the actual sequence book, it may mean that the nominal sequence book itself is used as the actual sequence book. In general, the number N of sequences included in the actual sequence book may have a smaller value than the number L of orthogonal sequences included in the nominal sequence book.
[0223] <Second embodiment of orthogonal sequence configuration>
[0224] According to a second embodiment of the present disclosure, the orthogonal sequence w may be determined as a pre-specified sequence. In this case, the pre-specified sequence may have a different sequence for each value L, which is the total number of nominal sequences. For example, when L = 1, this may mean that resource multiplexing is not used. If L = 1, the orthogonal sequence w may be expressed as in the following mathematical expression 5.
[0225]
[0226] If L=2, the orthogonal sequence w may be, for example, as shown in Table 47 below. Table 47 below is one example to help understanding the present disclosure, and is not limited thereto.
[0227]
[0228] If L=4, the orthogonal sequence w may be, for example, as shown in Table 48 below. Table 48 below is one example to help understanding the present disclosure, and is not limited thereto.
[0229]
[0230] Another example for the orthogonal sequence w when L=4 may be as shown in Table 49 below. Table 49 below is an example to help understanding of the present disclosure and is not limited thereto.
[0231]
[0232] <Third embodiment of orthogonal sequence configuration>
[0233] According to the third embodiment of the present disclosure, the orthogonal sequence w can be determined by a specific mathematical formula. As an example of a method for determining the orthogonal sequence w, the nth sequence of the nominal sequence book can be determined as in the following mathematical formula 6. The following mathematical formula 6 is provided to help understanding of the present disclosure and is not limited thereto.
[0234]
[0235] In mathematical expression 6 or It can be, and the L sequences included in the nominal sequence book can be determined as in the following mathematical expression 7.
[0236]
[0237] Mathematical expression 7 is intended to illustrate one embodiment for determining an orthogonal sequence and is not limiting. In other words, in the present disclosure, any sequence may be used as long as each sequence in the set of L sequences, as described above, satisfies the orthogonality among them.
[0238] In mathematical expression 7, any nth sequence and any mth sequence among the L sequence sets included in the nominal sequence book can be orthogonal, and n and m can each be natural numbers. In other words, it can be seen that any nth sequence and any mth sequence among the L sequence sets included in the nominal sequence book have a relationship as shown in mathematical expression 8 below.
[0239]
[0240] In conclusion, the N sequences belonging to the actual sequence book can be determined as, for example, in mathematical expression 9 below. The mathematical expression 9 below is one example to help understanding the present disclosure and is not limited thereto.
[0241]
[0242] Mathematical expression 9 can be an example of a case where N consecutive sequences from the first sequence among the sequences of a nominal sequence book consisting of L sequences are selected as an actual sequence book. In other words, among the sequences included in the actual sequence book of Mathematical expression 9, may be the first sequence among the sequences included in the nominal sequence book, may be the second sequence among the sequences included in the nominal sequence book, may be the third sequence among the sequences included in the nominal sequence book, may be the Nth sequence among the sequences included in the nominal sequence book.
[0243] The example of mathematical expression 9 illustrates one method of selecting sequences included in an actual sequence book from among sequences included in a nominal sequence book. In other words, when selecting sequences included in an actual sequence book from among sequences included in a nominal sequence book, the sequences included in the actual sequence book may be consecutive sequences selected from the nominal sequence book, or N sequences may be selected so that not all sequences are consecutive. However, as explained above, if the premise that each sequence is orthogonal to each other is guaranteed, the sequences included in the actual sequence book from the nominal sequence book can be selected regardless of the order.
[0244] Meanwhile, when the first node wants to perform resource multiplexing when communicating with the second node as described in FIG. 7 or FIG. 8, the first node or the second node may be instructed to indicate one or more sequences among the sequences included in the nominal sequence book and / or the actual sequence book described above to the second node or the first node. In this case, the sequences used for resource multiplexing may be distinguished and indicated by the following information.
[0245] <Instruction information for sequences used for resource multiplexing>
[0246] (1) Resource multiplexing sequence size (corresponding to L described above)
[0247] (2) Resource multiplexing sequence index (corresponding to n described above)
[0248] (3) Type of resource multiplexing sequence (e.g., Discrete Fourier Transform (DFT) sequence, Walsh sequence, Hadamard sequence, etc.)
[0249] If the size L of the resource multiplexing sequence can be uniquely specified, the size L of the resource multiplexing sequence can be omitted. Similarly, if the resource multiplexing sequence can be specified as a specific sequence, the sequence index indicating the resource multiplexing sequence can be omitted. Also, if the type of the resource multiplexing sequence (e.g., DFT sequence, Walsh sequence, Hadamard sequence, ...) can be specified as a specific type, the sequence type can be omitted.
[0250] If the resource multiplexing sequence index can be determined based on a combination of one or more of the information below, the indication of the resource multiplexing index may be replaced with an indication of an identifier such as the information below. In other words, the indication of the resource multiplexing index may not be implicitly indicated.
[0251] [A]. A first embodiment of information that can indicate a resource multiplexing index using one or more identifiers:
[0252] - UE identifier (UE ID)
[0253] - Artificial intelligence (AI)-radio network temporary identifier (RNTI) (AI-RNTI)
[0254] - Cell (C)-RNTI (C-RNTI)
[0255] - Configured grant small data transmission (CG-SDT) - configured scheduling (CS) - RNTI (CG-SDT-CS-RNTI)
[0256] - Cell identification (CI) RNTI (CI-RNTI)
[0257] - CS-RNTI
[0258] - Group (group, G) CS-RNTI (G-CS-RNTI)
[0259] - G-RNTI
[0260] - INT-RNTI
[0261] - MCCH-RNTI
[0262] - MCS-C-RNTI
[0263] - MSGB-RNTI
[0264] - NCR-RNTI
[0265] - P-RNTI
[0266] - PEI-RNTI
[0267] - PS-RNTI
[0268] - RA-RNTI
[0269] - SFI-RNTI
[0270] - SI-RNTI
[0271] - Sidelink (SL) semi-persistent scheduling V-RNTI (SL Semi-Persistent Scheduling V-RNTI)
[0272] - SL-CS-RNTI
[0273] - SL-PRS-CS-RNTI
[0274] - SL-PRS-RNTI
[0275] - SL-RNTI
[0276] - SP-CSI-RNTI
[0277] - Temporary C-RNTI
[0278] - TPC-PUCCH-RNTI
[0279] - TPC-PUSCH-RNTI
[0280] - TPC-SRS-RNTI
[0281] [B]. The instruction information used for resource multiplexing described above (e.g., resource multiplexing sequence size, resource multiplexing sequence index, resource multiplexing sequence type) may include one or more of the following information. As another example, at least one of the following information may be implicitly indicated using one or a combination of two or more identifiers as exemplified in section [A]:
[0282] = Whether resource multiplexing is applied
[0283] = Number of sequences belonging to the sequence book (corresponding to N or L described above)
[0284] = A set of sequences belonging to a sequence book
[0285] = A set of sequence indices belonging to a sequence book
[0286] = Number of sequence books
[0287] = Book index of the sequence book
[0288] = Granularity of resource multiplexing application scope
[0289] = Total size of the scope of resource multiplexing application
[0290] = Number of resource multiplexing applications
[0291] = Order of application of resource multiplexing
[0292] Whether resource multiplexing is applied can be indirectly indicated by the resource multiplexing sequence size. For example, if L = 1, it may be interpreted that resource multiplexing is not applied, and if L > 1, it may be interpreted that resource multiplexing is applied.
[0293] If the number N of sequences included in the actual sequence book has a smaller value than the number L of sequences included in the nominal sequence book, the number of sequences included in the actual sequence book and the types of sequences may be separately indicated. On the other hand, if the number N of sequences included in the actual sequence book has the same value as the number L of sequences included in the nominal sequence book, the number of sequences included in the sequence book and the types of sequences included in the sequence book may not be separately indicated.
[0294] Additionally, when indicating a sequence to be used for resource multiplexing, it can be indicated by a sequence index, as exemplified above. Therefore, the set of sequences included in a sequence book can also be indicated by a set of sequence indices. If the set of sequence indices is indicated by consecutive sequence indices, it can be indicated by a combination of two or more of the following information so that the set of sequence indices can be inferred.
[0295] a) Starting sequence index
[0296] b) Last sequence index
[0297] c) Number of sequence indices
[0298] The resource multiplexing sequence size and the resource multiplexing index can be indicated to determine the sequence used for resource multiplexing, and if there is more than one sequence book, the number of sequence books and the sequence book index can be additionally indicated.
[0299] The granularity of the resource multiplexing application scope can mean the size of the resource area to which the pth element w(p) of any orthogonal sequence w(i) is applied, and if this is expressed as a mathematical formula, it can be exemplified as in the following mathematical formula 10.
[0300]
[0301] Additionally, the granularity of resource multiplexing coverage can be divided into time, frequency, and antenna domains, and can be indicated by a combination of one or more of these. Each of the time, frequency, and antenna domains can be exemplified as follows.
[0302] a) Granularity-time of resource multiplexing application scope
[0303] b) Granularity-frequency of resource multiplexing application scope
[0304] c) Granularity-antenna of resource multiplexing application scope
[0305] The resource multiplexing coverage granularity-time exemplified above may be referred to as "granularity time" and / or "time granularity" in the following description. The resource multiplexing coverage granularity-frequency exemplified above may be referred to as "granularity frequency" and / or "frequency granularity" in the following description. And the resource multiplexing coverage granularity-antenna exemplified above may be referred to as "granularity antenna" and / or "antenna granularity" in the following description.
[0306] Figure 9 is a conceptual diagram for a case where resource multiplexing has 1 symbol granularity in the time domain.
[0307] In describing Fig. 9, the cases of Fig. 7 and / or Fig. 8 described above are assumed. For example, a first node may allocate resources for communication to a second node. Here, the resources may include time resources, frequency resources, and orthogonal sequences for resource multiplexing. Accordingly, the second node may receive resource information allocated for transmission to the first node. Based on the resource information allocated from the first node, the second node may obtain information about time resources, frequency resources, and orthogonal sequences.
[0308] In Fig. 9, the horizontal axis (x-axis) illustrates time resources allocated to the second node, and the vertical axis (y-axis) illustrates frequency resources allocated to the second node. The granularity of the time resources illustrated in Fig. 9 is illustrated as a case where the unit is 1 symbol. In addition, the frequency resources allocated in Fig. 9 can be divided into a plurality of frequency resources (911, 912, 913, 941) based on the granularity described above. The second node can perform resource multiplexing using the orthogonal sequence W(i) (920) allocated from the first node for data to be transmitted (the input sequence described above) through the plurality of frequency resources (911, 912, 913, 941) based on the granularity for each symbol.
[0309] In the example of FIG. 9, the symbols transmitted through the frequency resources (911, 912, 913, 914) in the first symbol may be the output sequence z(0) described above. More specifically, the data to be transmitted through the first frequency resource (911) in the first symbol may be the first input sequence to be mapped to the first frequency resource (911), and the first input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node. The data to be transmitted through the second frequency resource (912) in the first symbol may be the second input sequence to be mapped to the second frequency resource (912), and the second input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node. In addition, data to be transmitted through the third frequency resource (913) in the first symbol may be a third input sequence to be mapped to the third frequency resource (913), and the third input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node. And data to be transmitted through the fourth frequency resource (914) in the first symbol may be a fourth input sequence to be mapped to the fourth frequency resource (914), and the fourth input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node.
[0310] As described above, one orthogonal sequence can be applied equally to all frequency resources transmitted in one symbol interval.
[0311] Meanwhile, in the example of FIG. 9, it is assumed that the granularity of the frequency domain application range is the entire frequency resource allocated to the second node, but in an actual embodiment, it may be applied only to a part of the allocated frequency resource.
[0312] Figure 10 is a conceptual diagram for a case where resource multiplexing has 1 slot granularity for the time domain.
[0313] In describing Fig. 10, the cases of Fig. 7 and / or Fig. 8 described above are assumed. For example, a first node may allocate resources for communication to a second node. Here, the resources may include time resources, frequency resources, and orthogonal sequences for resource multiplexing. Accordingly, the second node may receive resource information allocated for transmission to the first node. Based on the resource information allocated from the first node, the second node may obtain information about time resources, frequency resources, and orthogonal sequences.
[0314] In Fig. 10, the horizontal axis (x-axis) illustrates time resources allocated to the second node, and the vertical axis (y-axis) illustrates frequency resources allocated to the second node. The granularity of the time resources illustrated in Fig. 10 is exemplified as a case in which the unit of granularity of the time resources is 1 slot. Although Fig. 10 assumes that the unit of granularity of the time resources is 1 slot, it can be understood as an alternative case in which the unit of granularity is 1 transmission time interval (TTI). In addition, the frequency resources allocated in Fig. 10 can be divided into multiple frequency resources (1011, 1012, 1013, 1041) based on the granularity described above. The second node can perform resource multiplexing using the orthogonal sequence W(i)(1020) allocated from the first node for data to be transmitted (the input sequence described above) through multiple frequency resources (1011, 1012, 1013, 1041) based on granularity for each slot.
[0315] In the example of FIG. 10, the symbols transmitted through the frequency resources (1011, 1012, 1013, 1014) in the first symbol may be the output sequence z(0) described above. More specifically, the data to be transmitted through the first frequency resource (1011) in the first symbol may be the first input sequence to be mapped to the first frequency resource (1011), and the first input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node. The data to be transmitted through the second frequency resource (1012) in the first symbol may be the second input sequence to be mapped to the second frequency resource (1012), and the second input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node. Additionally, data to be transmitted through the third frequency resource (1013) in the first symbol may be a third input sequence to be mapped to the third frequency resource (1013), and the third input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node. Additionally, data to be transmitted through the fourth frequency resource (1014) in the first symbol may be a fourth input sequence to be mapped to the fourth frequency resource (1014), and the fourth input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node.
[0316] As described above, one orthogonal sequence can be applied equally to all frequency resources transmitted in one slot (or TTI) period.
[0317] Meanwhile, in the example of FIG. 10, it is assumed that the granularity of the frequency domain application range is the entire frequency resource allocated to the second node, but in an actual embodiment, it may be applied to only a portion of the allocated frequency resource.
[0318] In the examples of FIGS. 9 and 10 described above, antenna granularity has been omitted for convenience of explanation. However, as described above, antenna granularity may be applied in the same manner as time granularity and / or frequency granularity. For example, antenna granularity may be applied to all assigned antennas, or only to some antennas.
[0319] Figure 11 is a conceptual diagram for a case where resource multiplexing has a granularity of 1 resource block in the frequency domain.
[0320] In describing Fig. 11, the cases of Fig. 7 and / or Fig. 8 described above are assumed. For example, a first node may allocate resources for communication to a second node. Here, the resources may include time resources, frequency resources, and orthogonal sequences for resource multiplexing. Accordingly, the second node may receive resource information allocated for transmission to the first node. Based on the resource information allocated from the first node, the second node may obtain information about time resources, frequency resources, and orthogonal sequences.
[0321] In Fig. 11, the horizontal axis (x-axis) illustrates time resources allocated to the second node, and the vertical axis (y-axis) illustrates frequency resources allocated to the second node. The granularity unit of the time resources illustrated in Fig. 11 may be one symbol, one slot, or one TTI. In addition, the granularity of the frequency resources allocated in Fig. 11 may be one resource block (RB) unit. According to the example of Fig. 11, the second node may perform resource multiplexing using the orthogonal sequence W(i) (1120) allocated from the first node for a plurality of time resources (1111, 1112, 1113, 1114) for one RB.
[0322] In the example of FIG. 11, data to be transmitted through the first RB in the first time resource (1111) may be a first input sequence, and the first input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node. Data to be transmitted through the first RB in the second time resource (1112) may be a second input sequence, and the second input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node. In addition, data to be transmitted through the first RB in the third time resource (1113) may be a third input sequence, and the third input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node. In addition, data to be transmitted through the first RB in the fourth time resource (1114) may be a fourth input sequence, and the fourth input sequence may be resource multiplexed by the first orthogonal sequence W(0) allocated from the first node.
[0323] In the same way, resource multiplexing can be performed for the second RB using the time resources allocated to the first RB and the second orthogonal sequence W(1). As described above, one orthogonal sequence can be equally applied to all time resources transmitted for one RB.
[0324] Meanwhile, in the example of Fig. 11, the granularity of the application range of the time domain is assumed to be the entire time resource allocated to the second node, but in an actual embodiment, it may be applied only to a part of the allocated time resource.
[0325] Additionally, in the example of FIG. 11 described above, antenna granularity has been omitted for convenience of explanation. However, as described above, antenna granularity may be applied in the same manner as time granularity and / or frequency granularity. For example, antenna granularity may be applied to all assigned antennas, or only to some antennas.
[0326] Figure 12 is a conceptual diagram for a case where resource multiplexing has 1 resource granularity for an antenna region.
[0327] In describing Fig. 12, the cases of Fig. 7 and / or Fig. 8 described above are assumed. For example, a first node may allocate resources for communication to a second node. Here, the resources may include time resources, frequency resources, antenna resources, and orthogonal sequences for resource multiplexing. Accordingly, the second node may receive resource information allocated for transmission to the first node. Based on the resource information allocated from the first node, the second node may obtain information about time resources, frequency resources, antenna resources, and orthogonal sequences.
[0328] In Fig. 12, the horizontal axis (x-axis) illustrates the time resources allocated to the second node, the vertical axis (y-axis) illustrates the frequency resources allocated to the second node, and additionally, the z-axis illustrates the antennas allocated to the second node.
[0329] In the example of FIG. 12, data transmitted through the time resources and frequency resources (1221) assigned to the second node for the first antenna assigned to the second node may be resource multiplexed by the first orthogonal sequence W(0). In the same way, data transmitted through the time resources and frequency resources (1222) assigned to the second node for the Lth antenna assigned to the second node may be resource multiplexed by the Lth orthogonal sequence W(L-1). In the example of FIG. 12, resource multiplexing is performed for each antenna, so data transmitted through all time resources and all frequency resources assigned to the second node may be multiplexed by the orthogonal sequence for each antenna.
[0330] In explaining the example of Fig. 12, antenna granularity is assumed to be a single antenna granularity, and granularity per antenna is described for all time and frequency resources. However, Fig. 12 is intended to facilitate understanding of antenna granularity, and in actual implementations, time / frequency / antenna granularity may be set differently from the example of Fig. 12. Variations of Fig. 12 will be further described below.
[0331] Figure 13 is a conceptual diagram for a case where resource multiplexing has two-dimensional granularity for the time domain and frequency domain.
[0332] In explaining Fig. 13, the cases of Fig. 7 and / or Fig. 8 described above are assumed. For example, a first node may allocate resources for communication to a second node. Here, the resources may include time resources, frequency resources, antenna resources, and orthogonal sequences for resource multiplexing. Accordingly, the second node may receive resource information allocated for transmission to the first node. Based on the resource information allocated from the first node, the second node may obtain information about time resources, frequency resources, antenna resources, and orthogonal sequences.
[0333] In Fig. 13, the horizontal axis (x-axis) illustrates the time resources allocated to the second node, and the vertical axis (y-axis) illustrates the frequency resources allocated to the second node. According to the example of Fig. 13, the time granularity in the time domain allocated to the second node may have a granularity of 1 / 2 of the allocated time, and the frequency granularity in the allocated frequency domain may have a granularity of one subcarrier (SC).
[0334] More specifically, data transmitted through the first time resource and the first SC (1311) can be resource multiplexed by the first orthogonal sequence W (0), data transmitted through the first time resource and the second SC (1312) can be resource multiplexed by the first orthogonal sequence W (1), data transmitted through the first time resource and the R-1th SC (1313) can be resource multiplexed by the first orthogonal sequence W (R-2), and data transmitted through the first time resource and the Rth SC (1314) can be resource multiplexed by the first orthogonal sequence W (R-1). Additionally, data transmitted through the second time resource and the first SC (1315) may be resource multiplexed by the R+1-th orthogonal sequence W(R), data transmitted through the second time resource and the second SC (1316) may be resource multiplexed by the R+2-th orthogonal sequence W(R+1), data transmitted through the second time resource and the L-1-th SC (1317) may be resource multiplexed by the first orthogonal sequence W(L-2), and data transmitted through the second time resource and the L-th SC (1318) may be resource multiplexed by the first orthogonal sequence W(L-1). This set of orthogonal sequences (1321) may be configured in advance by the first node as described above.
[0335] The example of FIG. 13 described above has been described for the sake of convenience of explanation, with respect to an example in which time resources and frequency resources are combined. However, the present disclosure is not limited thereto. For example, the present disclosure may be used in combination with time resources, frequency resources, and antenna resources. In addition, in the example of FIG. 13, the granularity unit is exemplified as 1 symbol unit for the time resource, and 1 SC for the frequency resource. However, the granularity of the time resource and the frequency resource is also merely an example to aid in the convenience of understanding, and an extended form may be used. For example, the time granularity unit may be a unit of 1 symbol or more, and the frequency granularity unit may be a unit of 1 SC or more. Although not described in the example of FIG. 13, one or more antenna granularity units may be used for the antenna granularity.
[0336] Also, with respect to the granularity of the resource multiplexing application range, although symbol units are explained as an example in the time resources allocated in FIG. 13, the area where time resource multiplexing is applied may be indicated in units such as slots, subframes, frames, TTIs, and / or seconds. Although SCs are explained as an example in the frequency resources allocated in FIG. 13, the area where frequency resource multiplexing is applied may be indicated in units such as resource blocks (RBs), bandwidth parts (BWPs), and / or hertz (Hz). With respect to the antenna area, the antenna granularity may be indicated in units such as each individual antenna or port, where antenna resource multiplexing is applied.
[0337] Figure 14 is a conceptual diagram for a case where resource multiplexing has granularity based on hop index.
[0338] In describing Fig. 14, the cases of Fig. 7 and / or Fig. 8 described above are assumed. For example, a first node may allocate resources for communication to a second node. Here, the resources may include time resources, frequency resources, antenna resources, and orthogonal sequences for resource multiplexing. Accordingly, the second node may receive resource information allocated for transmission to the first node. Based on the resource information allocated from the first node, the second node may obtain information about time resources, frequency resources, antenna resources, and orthogonal sequences.
[0339] According to the example of FIG. 14, data can be transmitted continuously in the allocated time resources, and data can be transmitted based on a frequency hopping rule within the allocated frequency resources. More specifically, among the first time resource and the allocated frequency resources, a frequency resource corresponding to half of the total frequency resources from a lower frequency can be a resource of hop #0 (1411) where data is transmitted, and among the second time resource and the allocated frequency resources, the remaining frequency resources that are not allocated to hop #0 (1411) can be a resource of hop #1 (1412) where data is transmitted. The resource of hop #0 (1411) can be determined based on the time resource allocated to hop #0 and the frequency resource allocated to hop #0, and the resource of hop #1 (1412) can be determined based on the time resource allocated to hop #1 and the frequency resource allocated to hop #1.
[0340] Data transmitted through the resource of hop#0(1411) can be resource multiplexed by an orthogonal sequence corresponding to the first group of orthogonal sequences W(i), and data transmitted through the resource of hop#1(1412) can be resource multiplexed by an orthogonal sequence corresponding to the second group of orthogonal sequences W(i). In the example of Fig. 14, the first group of orthogonal sequences W(i) may be the orthogonal sequences of W(0) to W(R-1), and the second group may be the orthogonal sequences of W(R) to W(L-1). If L=2, data transmitted through the resource of hop#0(1411) may be resource multiplexed by W(0), and data transmitted through the resource of hop#1(1412) may be resource multiplexed by W(1).
[0341] Any pth orthogonal sequence w(p) in an orthogonal sequence W(i) may be applied to one or more hop indices. In other words, one resource multiplexing orthogonal sequence element may be applied to one or more hop indices.
[0342] The granularity based on the multiplexed hop index described above with reference to FIG. 14 is merely intended to aid understanding of the present disclosure, and the present disclosure is not limited thereto. For example, it may be used in combination with time resources, frequency resources, and antenna resources. The granularity unit may also be a unit of one or more symbols for the time resource, one or more SC units may be applied to the frequency resource, and one or more antenna resources may be applied to the antenna resource. Furthermore, as illustrated in FIG. 14, the hop index may also be interpreted as a combination of symbol(s) of the time resource and SC(s) of the frequency resource.
[0343] In the present disclosure according to FIGS. 9 to 14 described above, the fact that granularity is indicated in a specific unit does not necessarily mean that it must be indicated as a value of 1 in the specific unit. For example, if the time granularity is indicated in slot units, it may mean that the time granularity may be indicated in units of one slot or in units of two or more slots.
[0344] On the other hand, for the granularity of each area, if the granularity can be determined based on the allocated time-resource information, allocated frequency-resource information, and allocated antenna-resource information, a separate explicit instruction may be omitted.
[0345] In the present disclosure described above with reference to FIGS. 9 to 14, resource multiplexing may be directed to be applied more than once. For example, it may be applied first to time resources and then again to frequency resources. In another example, it may be applied first to frequency resources and then again to the time domain. In another example, after resource multiplexing is applied in the time domain, resource multiplexing may be applied in the antenna domain. Here, the order of application of resource multiplexing is not limited to the examples described above, and may be configured in any resource order. Furthermore, when resource multiplexing is applied more than once, the sequences used in each resource multiplexing domain may be different.
[0346] In the present disclosure, the resource multiplexing application size may mean the size of a resource area to which any orthogonal sequence w(i) is applied.
[0347] Additionally, in cases where the sequence to be used for resource multiplexing can be specified depending on the situation, the sequence index, the number of sequences belonging to the sequence book, the type of sequence belonging to the sequence book, the sequence book index, and / or the number of sequence books, etc. may not be separately indicated.
[0348] [Resource Multiplication Capability Notification (Indication) / Reporting Method]
[0349] A communication node can determine a resource multiplexing application method by referring to information about the resource multiplexing methods that the other node can support. If this is explained using the nodes described in FIG. 7 and / or FIG. 8 described above, a second node can report (or perform capability notification) to a first node about the resource multiplexing methods that the second node can support. The first node can receive a resource multiplexing method report (or capability notification) message from the second node. The first node can learn about the resource multiplexing capabilities of the second node based on the resource multiplexing method report (or capability notification) message received from the second node. The first node can determine a resource multiplexing method for the second node based on the resource multiplexing capabilities of the second node.
[0350] As described above, when the first node determines the resource multiplexing method for the second node, the first node can provide the second node with the resource multiplexing method information determined for the second node. In addition, the first node can also determine the resource multiplexing method for the third node based on the same procedure as the second node, and can provide the third node with the resource multiplexing method information determined for the third node.
[0351] In this case, when the second node and the third node apply the same resource multiplexing method, the second node and the third node can each transmit data to the first node through the same resources (time, frequency, and / or antenna), that is, overlapping resources. Even if the second node and the third node transmit data through overlapping resources, the data transmitted by the second node to the first node and the data transmitted by the third node to the first node can be distinguished from each other by the resource multiplexing sequence as described in the present disclosure.
[0352] If the resource multiplexing methods of the second and third nodes differ, each node can transmit data using non-overlapping resources. In other words, depending on how resource multiplexing is applied, the resource locations that each node can occupy can be identified and scheduled by the first node.
[0353] As another example, even if the resource multiplexing methods of the second and third nodes are different, the second and third nodes can each transmit data to the first node through overlapping resources. However, if the resource multiplexing methods of the second and third nodes are different and transmit data to the first node through overlapping resources, the first node may not be able to distinguish between data transmitted by the second node and data transmitted by the third node. Here, different resource multiplexing methods may mean that data transmitted through overlapping resources at the same time are not orthogonal.
[0354] In general, if the information below differs, it can be assumed that the resource multiplexing method is indicated differently. Note that different resource multiplexing sequence types below may mean that they are indicated as non-orthogonal sequences.
[0355] (a) Whether resource multiplexing is applied
[0356] (b) Resource multiplexing sequence size
[0357] (c) Resource multiplexing sequence type
[0358] (d) Granularity of resource multiplexing scope of application
[0359] (e) Size of the scope of application of resource multiplexing
[0360] (f) Location of resource multiplexing scope of application
[0361] (g) Number of resource multiplexing applications
[0362] (h) Order of application of resource multiplexing
[0363] The (a) to (h) described above can be understood as resource multiplexing method determining elements or resource self-scaling method determining factors. Accordingly, when the first node determines the resource multiplexing method for each of the second and third nodes, the first node can transmit configuration information including the resource multiplexing method determining elements (or resource multiplexing method determining factors) to the second and third nodes.
[0364] Additionally, the second node and / or the third node may report (or inform) information about the supportable resource multiplexing scheme to the first node. The supportable resource multiplexing scheme may be provided to a node performing scheduling, for example, the first node of FIG. 7 and / or FIG. 8, by combining one or more pieces of information as follows.
[0365] s1) Whether resource multiplexing is supported
[0366] s2) Maximum (or minimum) size of the supported resource multiplexing sequence
[0367] s3) A set of supportable resource multiplexing sequence sizes
[0368] s4) Types of supported resource multiplexing sequences
[0369] s5) Number of supported resource multiplexing sequences
[0370] s6) Resource location most suitable for resource multi-use
[0371] s7) A set of resource locations suitable for resource multiplexing
[0372] s8) Maximum scope of supportable resource multiplexing
[0373] s9) Minimum scope of supportable resource multiplication
[0374] s10) Set of applicable scopes for multiplexing of resources that can be supported
[0375] s11) Maximum (or minimum) granularity of the scope of application of resource multiplexing that can be supported
[0376] s12) A set of granularity values for the scope of application of multiple supported resources.
[0377] s13) Whether it can overlap with other resource multiplexing methods
[0378] s14) Whether it can overlap when resource multiplexing is not used
[0379] Each piece of information about the supportable resource multiplexing method can be provided as a separate value, divided into time resources, frequency resources, and antenna resources. In this case, for time resources, the range to which resource multiplexing is applied can be indicated in units such as symbols, OFDM symbols, slots, subframes, frames, TTIs, and / or milliseconds (ms). In addition, for frequency resources, the range to which resource multiplexing is applied can be indicated in units such as SCs, RBs, and / or BWPs. Additionally, the maximum (or minimum) value of the supportable resource multiplexing sequence size exemplified above can be the supportable resource multiplexing sequence size. If OCC is used, the supportable resource multiplexing sequence size can mean the length of the OCC. As another example, the set of supportable resource multiplexing sequence sizes can include one or more supportable resource multiplexing sequence size values. If OCC is used, the set of multiplexing sequence sizes can include one OCC length value or two or more OCC length values.
[0380] Meanwhile, regarding the resource multiplexing resource location described above, information related to the scope of resource multiplexing application, etc., whether a certain condition can be satisfied or a value for a certain condition can be provided to the first node by the second node illustrated in FIG. 7 and / or FIG. 8. Here, the certain condition can be determined by a combination of one or more of the information below.
[0381] t1) Received signal strength indicator (RSSI)
[0382] t2) Reference signal received power (RSRP)
[0383] t3) Reference signal received quality (RSRQ)
[0384] t4) signal-to-noise ratio (SNR)
[0385] t5) signal-to-interference-plus-noise ratio (SINR)
[0386] t6) Timing error
[0387] t7) Timing drift
[0388] t8) phase error
[0389] t9) phase drift
[0390] t10) Timing advance (TA)
[0391] t11) TA drift
[0392] t12) Frequency error
[0393] t13) Frequency drift
[0394] t14) Coherence time
[0395] t15) Coherence time variation
[0396] t16) Coherence bandwidth
[0397] t17) Coherence bandwidth variation
[0398] As an example of one of the above-mentioned conditions, RSRP is described as follows. A resource location suitable for resource multiplexing can be provided to a scheduling node or a counterpart node by measuring RSRP according to the size of a specific resource area, and the resource location with the best quality can be provided as the resource location suitable for resource multiplexing. In other words, the second node described in FIG. 7 and / or FIG. 8 can measure RSRP using a signal (e.g., a reference signal) received from the first node and determine the resource location with the best quality. The second node can then transmit the determined resource location information to the first node performing scheduling.
[0399] The best quality resource location may be a resource location with a quality higher than a preset threshold. In this case, there may be one or more resource locations provided to the first node by the second node. If the set of resource locations provided to the first node by the second node is continuous, the set of resource locations can be configured into a resource area suitable for resource multiplexing through a combination of a starting resource location, a final resource location, and / or a resource interval. The resource area configured in this way can be provided to the first node by the second node.
[0400] As another example of the above-mentioned conditions, a phase error is described as follows. A resource location suitable for resource multiplexing may be a resource location where the phase error between adjacent resource areas is better than a preset reference value and / or a resource location with the best quality. Information on the resource location where the phase error is better than the preset reference value and / or the resource location with the best quality may be provided to the scheduling node or the counterpart node as a resource location suitable for resource multiplexing. In other words, the second node described in FIG. 7 and / or FIG. 8 may determine a resource location where the phase error is better than a preset reference value and / or a resource location with the best quality using a signal (e.g., a reference signal) received from the first node. The second node may then transmit the determined resource location information to the first node performing scheduling.
[0401] At this time, there may be more than one resource location provided by the second node to the first node. Here, the certain condition may be defined differently for modulation order, physical channel, DFT-s-OFDM / CP-OFDM, frequency range, downlink sub-carrier spacing SCS, SSB SCS, uplink SCS, and / or PRACH SCS. In addition, whether a certain condition is satisfied or a value for a certain condition may be provided to the counterpart node or the scheduling node through periodic / aperiodic monitoring (measurement), PHY signaling, upper layer signaling, etc.
[0402] In a communication network according to the present disclosure, a communication node utilizing resource multiplexing may be required to satisfy requirements for at least one combination of the conditions described above. If a communication node does not satisfy requirements for at least one combination of the conditions described above, transmissions may be dropped or ignored. In other words, if the second node and / or the first node do not satisfy requirements for at least one combination of the conditions described above, data transmissions from the second node may be dropped.
[0403] Additionally, the first node, which is the node performing the scheduling, may set (or instruct) resource multiplexing by referring to the resource multiplexing capability information received from the second node. However, the first node performing the scheduling may apply a resource multiplexing method within the range of resource multiplexing methods supported by the other party, but may determine (or apply) a resource multiplexing method for the second node regardless of the most suitable resource multiplexing method reported by the second node.
[0404] The resource multiplexing capability information of the second node can be provided to the first node through various methods (e.g., periodic monitoring (measurement) or aperiodic monitoring (measurement)), PHY signaling, upper layer signaling (e.g., MAC message, RRC message, and / or MAC-CE, etc.). In this case, the resource multiplexing capability information can be used to change an existing resource multiplexing configuration / instruction, or to create a new resource multiplexing configuration / instruction.
[0405] In other words, resource multiplexing capability information can be used as a reference for resource multiplexing scheduling and rescheduling by the first node, which is a communication node performing scheduling. The resource multiplexing capability information can be provided as reference information that can guide the first node performing scheduling to configure transmission so that a resource multiplexing method supported by any communication node (e.g., the second node) or the most appropriate resource multiplexing method is used.
[0406] For example, a first node can use the resource multiplexing capability information received from a second node to indicate separate resource locations for each resource multiplexing method so that they do not overlap. In other words, a first node performing scheduling can appropriately schedule resource multiplexing transmissions by referring to the resource multiplexing capability information received from a second node, and can indicate the scheduled resource multiplexing transmission method to the second node.
[0407] [How to determine the behavior between resource multiplexing and repetition / aggregation]
[0408] According to one embodiment of the present disclosure, whether to use resource multiplexing may be indicated by a separate parameter. Whether to use resource multiplexing may be indicated based on the resource multiplexing configuration information and / or resource multiplexing indication information described above in FIG. 7 and / or FIG. 8. According to another embodiment of the present disclosure, whether to use resource multiplexing may be indirectly indicated through the resource multiplexing sequence size L. According to yet another embodiment of the present disclosure, whether to use resource multiplexing may be indicated by reinterpreting existing parameter values. As an example of a method for reinterpreting existing parameter values, the sequence length L may be indicated by the allocated symbol size, the allocated frequency size, the allocated antenna size (or number), and the repetition / aggregation factor (RAF).
[0409] If the use of resource multiplexing is separately indicated, and "Whether to use resource multiplexing = OFF", the resource multiplexing sequence size that is finally applied is regarded as 1 (L=1) regardless of the setting value of the resource multiplexing sequence size, and thus can be regarded as a case where resource multiplexing is not used. On the other hand, if "Whether to use resource multiplexing = ON", the resource multiplexing sequence size that is finally applied is regarded as the size of the set resource multiplexing sequence, and thus whether to use resource multiplexing can be determined according to the set resource multiplexing sequence size. The above can be summarized as shown in Table 50 below.
[0410] Whether to use resource multiplexing Resource multiplexing sequence size L on L = Set resource multiplexing sequence size Off L = 1
[0411] When only resource multiplexing is set without repetition / slot aggregation, that is, when the L value is greater than 1 (RAF = 1), resource multiplexing can be performed regardless of repetition / aggregation. In the following description, "aggregation" may mean slot aggregation and / or frequency aggregation. However, for the convenience of understanding, the present disclosure assumes slot aggregation and explains, and for the convenience of explanation, aggregation can be understood to mean slot aggregation.
[0412] On the other hand, when only repetition / aggregation is set without resource multiplexing (L = 1, RAF > 1), repetition / aggregation can be performed regardless of resource multiplexing. As another example, when both resource multiplexing and repetition / aggregation are set (L > 1, RAF > 1), the priority between resource multiplexing and repetition / aggregation can be indicated. Resource multiplexing and repetition / aggregation can be indicated together by being included in the resource multiplexing indication information described above, or can be indicated by a separate repetition / aggregation indication. Therefore, when both resource multiplexing and repetition / aggregation are set (L > 1, RAF > 1), when the priority between resource multiplexing and repetition / aggregation is indicated, it can be determined based on whether to perform resource multiplexing and repetition / aggregation and the order in which they are performed. The above can be organized as shown in Table 51 below.
[0413] Resource Multiplexing Sequence Size LRAF Value Execution Action L > 1 RAF = 1 Perform resource multiplexing L = 1 RAF > 1 Perform repetition / aggregation L > 1 RAF > 1 Determine whether to perform and the execution order based on the priority of repetition / aggregation
[0414] In addition, whether the total size of the resource multiplexing application scope exceeds the TTI interval can affect the priority between resource multiplexing and repetition / aggregation. For example, if the total size of the resource multiplexing application scope does not exceed the TTI interval, in other words, if "the total size of the resource multiplexing application scope ≤ the TTI interval," both resource multiplexing and repetition / aggregation can be performed. In this case, resource multiplexing can be performed within the TTI interval, and repetition / aggregation can be performed between different TTIs. On the other hand, if the total size of the resource multiplexing application scope exceeds the TTI interval, a priority determination between resource multiplexing and repetition / aggregation may be required. If a priority determination between resource multiplexing and repetition / aggregation is required, whether to perform / the order of performing resource multiplexing or repetition / aggregation can be determined based on the priority between resource multiplexing and repetition / aggregation.
[0415] The above contents can be summarized as shown in Table 52 below.
[0416] Total size of the scope of resource multiplexing application ≤ TTI interval Perform both resource multiplexing and repetition / aggregation - Perform resource multiplexing within a TTI, perform repetition / aggregation between TTIs Total size of the scope of resource multiplexing application > TTI interval Determine whether to perform and the order of performance based on priority
[0417] The priority between resource multiplexing and repetition / aggregation can be determined by separate instructions. For example, the priority between resource multiplexing and repetition / aggregation can be determined by explicitly indicating one of the transmission methods to be preferred, by implicitly specifying the priority by specifying a predefined rule between RAF and sequence length, or by determining it based on transmission parameters. Figure 15 is a flowchart illustrating a case where the priority between resource multiplexing and repetition / aggregation is determined by an explicit / implicit method.
[0418] In step S1500, the priority between resource multiplexing and repetition / aggregation can be set by the node performing the scheduling, for example, the first node of FIG. 7 and / or FIG. 8. The priority can be appropriately set in response to various cases as follows. For example, if the first node performing the scheduling needs to transmit data to a large number of nodes, resource multiplexing can be set to have a higher priority than repetition / aggregation. If the first node needs to transmit data to a large number of nodes, the first node can set resource multiplexing for the downlink to have a higher priority than repetition / aggregation to increase the efficiency of downlink resource usage. Similarly, if the first node performing the scheduling needs to receive data from a large number of nodes, the first node can set resource multiplexing for the uplink from the large number of nodes to have a higher priority than repetition / aggregation. Accordingly, the second node can receive the priority set by the first node from the first node. These examples are merely examples to help understanding the present disclosure, and the present disclosure is not limited to the examples described above.
[0419] In addition, the first node performing scheduling may set the priority of repetition / aggregation higher than the priority of resource multiplexing in the following cases. For example, if the first node needs to transmit a large amount of data to second nodes in an RRC-connected state at once, an aggregation method may be required. In this case, the first node may set the priority of repetition / aggregation higher than the priority of resource multiplexing to transmit a large amount of data to the second node. As another example, there may be a case where the first node needs to lower the error rate of data transmitted to the second node in an RRC-connected state. In this case, the first node may set the priority of repetition / aggregation higher than the priority of resource multiplexing to lower the error rate of data transmitted to the second node through repeated data. Accordingly, the second node may receive the priority set by the first node from the first node. These examples are merely examples to help understand the present disclosure, and the present disclosure is not limited to the examples described above.
[0420] If the priority is explicitly set in step S1500, the first node can transmit priority information to the second node (not shown in FIG. 15). If the priority in step S1500 is implicitly set, the first node can implicitly transmit priority setting information to the second node by other parameter(s). Here, the implicit setting can be set by inference from other information, interpretation by a combination of other parameters, or reinterpretation of the fields of other parameter(s) as described above. If the priority is determined implicitly, a separate priority setting operation such as step S1500 may not be performed.
[0421] In step S1510, the first node and the second node can determine a higher priority among resource multiplexing or repetition / aggregation based on the set priority. For example, if a priority is explicitly set from the first node in step S1500, the second node can determine a higher priority among resource multiplexing or repetition / aggregation based on the priority explicitly set from the first node. As another example, if a priority is implicitly set from the first node, the second node can determine a higher priority among resource multiplexing or repetition / aggregation based on the implicitly set priority.
[0422] In step S1520, the first node and the second node can check whether resource multiplexing has a high priority. If the result of the check in step S1520 shows that resource multiplexing has a high priority, the first node and the second node can perform step S1530. If the result of the check in step S1520 shows that resource multiplexing does not have a high priority, the first node and the second node can perform step S1540.
[0423] In step S1530, the first node and the second node can perform communication according to the configured resource multiplexing. For example, in the case of downlink, the first node can transmit data to the second node based on the configured resource multiplexing scheme. Accordingly, the second node can receive data from the first node based on the resource multiplexing scheme configured by the first node. Here, the resource multiplexing scheme may be any one of the resource multiplexing schemes described above, or a combination of two or more schemes.
[0424] As another example, in the case of uplink, a second node can transmit data to the first node based on the resource multiplexing scheme set by the first node. Accordingly, the first node can receive uplink data from the second node based on the set resource multiplexing scheme. Here, the resource multiplexing scheme may be any one of the resource multiplexing schemes described above, or a combination of two or more.
[0425] At step S1540, the first node and the second node can communicate according to the configured repetition / aggregation scheme. For example, in the case of downlink, the first node can transmit data to the second node based on the configured repetition / aggregation scheme. Accordingly, the second node can receive data from the first node based on the configured repetition / aggregation scheme by the first node.
[0426] As another example, in the case of uplink, a second node can transmit data to the first node based on the repetition / aggregation method set by the first node. Accordingly, the first node can receive uplink data from the second node based on the set repetition / aggregation method.
[0427] Figure 16 is a flowchart for explaining a method for determining priority criteria values and resource multiplexing or repetition / aggregation priorities based on transmission parameters.
[0428] The embodiment of FIG. 16 may be a case where the decision on whether to use resource multiplexing or repetition / aggregation is determined based on transmission parameters. The priority for resource multiplexing or repetition / aggregation may be set by a threshold value included in the transmission parameters. The transmission parameters may consider one or a combination of two or more of the following parameters.
[0429] p1) Transmission parameters related to effective code rate:
[0430] Transmission parameters related to the effective code rate may include, for example, modulation and coding scheme (MCS), code rate, number of transmissions, transmission occasion (TO), effective code rate, etc.
[0431] p2) Identifier related parameters:
[0432] Identifier-related parameters may include, for example, RNTI parameters such as C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, etc., and UE-specific identifiers.
[0433] p3) Parameters mentioned in resource multiplication setup / directive:
[0434] Parameters mentioned in the resource multiplexing setup / directive may be used, for example, the resource multiplexing sequence size L, the actual sequence book size N, the book index of the sequence book, the resource multiplexing scope granularity, the total size of the resource multiplexing scope, etc.
[0435] In step S1600, the first node can set one or more parameters among the parameters described in p1) to p3) described above as reference values required for priority determination. And the first node can transmit the reference values required for priority determination to the second node. If there is information that needs to be reported to the first node based on the reference values required for priority determination, the second node can report it to the first node (not shown in FIG. 16). If there is information required for the reference values required for priority determination, the first node can receive the reference values required for priority determination from the second node. And the first node can set the priority for resource multiplexing or repetition / aggregation based on the reference values. The first node can transmit the set priority information to the second node. Therefore, the second node can set the priority based on the priority information received from the first node.
[0436] In step S1610, the first node and the second node can determine a higher priority among resource multiplexing or repetition / aggregation based on the set priority. For example, if a priority is explicitly set from the first node in step S1600, the second node can determine a higher priority among resource multiplexing or repetition / aggregation based on the priority explicitly set from the first node. As another example, if a priority is implicitly set from the first node, the second node can determine a higher priority among resource multiplexing or repetition / aggregation based on the implicitly set priority.
[0437] In step S1620, the first node and the second node can check whether resource multiplexing has a high priority. If the result of the check in step S1620 shows that resource multiplexing has a high priority, the first node and the second node can perform step S1630. If the result of the check in step S1620 shows that resource multiplexing does not have a high priority, the first node and the second node can perform step S1640.
[0438] In step S1630, the first node and the second node can perform communication according to the configured resource multiplexing. For example, in the case of downlink, the first node can transmit data to the second node based on the configured resource multiplexing scheme. Accordingly, the second node can receive data from the first node based on the resource multiplexing scheme configured by the first node. Here, the resource multiplexing scheme may be any one of the resource multiplexing schemes described above, or a combination of two or more schemes.
[0439] As another example, in the case of uplink, a second node can transmit data to the first node based on the resource multiplexing scheme set by the first node. Accordingly, the first node can receive uplink data from the second node based on the set resource multiplexing scheme. Here, the resource multiplexing scheme may be any one of the resource multiplexing schemes described above, or a combination of two or more.
[0440] At step S1640, the first node and the second node can communicate according to the configured repetition / aggregation scheme. For example, in the case of downlink, the first node can transmit data to the second node based on the configured repetition / aggregation scheme. Accordingly, the second node can receive data from the first node based on the configured repetition / aggregation scheme by the first node.
[0441] As another example, in the case of uplink, a second node can transmit data to the first node based on the repetition / aggregation method set by the first node. Accordingly, the first node can receive uplink data from the second node based on the set repetition / aggregation method.
[0442] Figure 17 is a flowchart for explaining a case where priority is determined based on MCS among transmission parameters.
[0443] The operation of FIG. 17 may be a special example of the previously described FIG. 15 and / or FIG. 16, where the MCS included in the transmission parameters may be used as a reference value for determining priority. Accordingly, step S1700 may correspond to steps S1500 and / or S1600, and the reference value may be a case where a reference value for MCS is used. Furthermore, step S1710 may correspond to steps S1510 and / or S1610, and the reference value may be a case where a reference value for MCS is used. All other operations may be the same.
[0444] In step S1720, the first node and / or the second node may determine that resource multiplexing is given priority if the MCS is less than a specific reference value, for example, a specific MCS level (or a specific MCS value). On the other hand, if the MCS is greater than a specific MCS level (or a specific MCS value), repetition / aggregation may be determined to be given priority.
[0445] Step S1730 may be a case where resource multiplexing is performed in the same manner as steps S1530 and / or S1630 described above, and step S1740 may be a case where resource multiplexing is performed in the same manner as steps S1540 and / or S1640 described above. Therefore, duplicate descriptions of the same content will be omitted.
[0446] Figure 18 is a flowchart for explaining a case where priority is determined based on the effective code rate among transmission parameters.
[0447] The operation of FIG. 18 may be a special example of the previously described FIG. 15 and / or FIG. 16, in which the effective code rate included in the transmission parameters is used as a reference value for determining priority. Accordingly, step S1800 may correspond to steps S1500 and / or S1600, and the reference value may be a case in which a reference value for the effective code rate is used. Furthermore, step S1810 may correspond to steps S1510 and / or S1610, and the reference value may be a case in which a reference value for the effective code rate is used. All other operations may be the same.
[0448] In step S1820, the first node and / or the second node may determine that resource multiplexing is given priority if the effective code rate is less than a specific reference value, for example, a specific effective code rate. On the other hand, if the effective code rate is greater than a specific effective code rate, repetition / aggregation may be determined to be given priority.
[0449] Step S1830 may be a case where resource multiplexing is performed in the same manner as steps S1830 and / or S1830 described above, and step S1840 may be a case where resource multiplexing is performed in the same manner as steps S1540 and / or S1640 described above. Therefore, duplicate descriptions of the same content will be omitted.
[0450] In FIGS. 17 and 18, a method of using MCS and an effective code rate as transmission parameters used for priority determination has been described. However, the present disclosure is not limited thereto. In other words, the parameter(s) p1) to p3) described above may be used as a priority determination criterion by one or more combinations. In addition, the reference value may have a separate and different value for each combination of transmission parameter(s). If the reference value has a different value for each combination of transmission parameter(s), the reference value may indicate more than one value.
[0451] As an example of a case where there are two or more reference values, the reference values used for determining priorities may be set differently for each TO. More specifically, a case where priorities are determined by considering MCS and TO will be described. When MCS is used as the reference value, the MCS reference value can be indicated differently for each TO. Accordingly, the first reference value applied to the 0th TO (TO#0) and the second reference value applied to the 1st TO (TO#1) can be indicated differently. Accordingly, the reference values for each combination of parameter(s) can be determined differently. In other words, more than one reference value can be indicated, and the priority of resource multiplexing and repetition / aggregation can be determined for each combination of parameters based on the set reference values.
[0452] Furthermore, the example of the effective code rate described above can also be interpreted as an example in which the combination of MCS and TO among the transmission parameters(s) is considered in determining priority, since the effective code rate can be determined based on MCS and TO. Accordingly, the first node and / or the second node can determine the priority between resource multiplexing or repetition / aggregation based on a set specific reference value.
[0453] The reference values described in this document can be set differently for each combination of transmission parameters, and the priority of resource multiplexing or repetition / aggregation can be determined based on these reference values. Here, if a predefined value is used as the reference value or a specific value can be specified, a separate explicit indication of the reference value may not be provided.
[0454] The operations of the method according to the embodiments of the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.
[0455] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.
[0456] While some aspects of the present disclosure have been described in the context of a device, they may also represent a description of a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described as a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one or more of the most important method steps may be performed by such a device.
[0457] In embodiments, a programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described herein. In embodiments, the field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. In general, the methods are preferably performed by some hardware device.
[0458] Although the present disclosure has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the claims below.
Claims
1. In the method of the first communication node, A step of receiving resource multiplexing setting information from a second communication node; A step of receiving resource multiplexing instruction information from the second communication node; and A step of transmitting data to the second communication node based on the resource multiplexing instruction information. Method of the first communication node.
2. In claim 1, Each of the orthogonal sequences included in the first orthogonal sequence set and the second orthogonal sequence set is a sequence selected from a nominal sequence book containing all mutually orthogonal sequences. Method of the first communication node.
3. In claim 1, The above resource multiplexing indication information indicates one of the first orthogonal sequence set and the second orthogonal sequence set based on at least one of a resource multiplexing sequence size, a resource multiplexing sequence index, or a resource multiplexing sequence type. Method of the first communication node.
4. In claim 3, The above resource multiplexing sequence index is indicated by at least one of the identifier of the first communication node or the radio network temporary identifier (RNTI) that the second communication node can provide. Method of the first communication node.
5. In claim 1, Further comprising a step of transmitting resource multiplexing capability information of the first communication node to the second communication node before receiving the resource multiplexing setting information. Method of the first communication node.
6. In claim 5, The resource multiplexing capability information of the first communication node is transmitted in response to receiving the resource multiplexing capability information of the second communication node from the second communication node. Method of the first communication node.
7. In claim 1, The orthogonal sequences included in each of the first orthogonal sequence set and the second orthogonal sequence set are composed of some sequences that are consecutive in a nominal sequence book that includes all sequences, and when the first orthogonal sequence set and the second orthogonal sequence set are relatively prime, the resource multiplexing indication information is indicated by a combination of two of a start sequence index, a last sequence index, or a number of sequence indices of orthogonal sequences to be used for resource multiplexing. Method of the first communication node.
8. In claim 1, Further comprising a step of transmitting a scheduling request message to the second communication node when there is data to be transmitted to the second communication node after receiving the resource multiplexing setting information, The above resource multiplexing instruction information is included in a scheduling grant message received from the second communication node. Method of the first communication node.
9. In claim 1, A step of determining that resource multiplexing is not indicated in the resources allocated to the first communication node is further included, if there is a third communication node to which the same resources as those allocated to the first communication node exist from the second communication node, and at least one of resource multiplexing application status, resource multiplexing sequence size, resource multiplexing sequence type, resource multiplexing application scope granularity, resource multiplexing application scope size, resource multiplexing application scope location, resource multiplexing application number, or resource multiplexing application order included in the resource multiplexing instruction information transmitted to the first communication node and the resource multiplexing instruction information transmitted to the third communication node are different. Method of the first communication node.
10. In claim 1, If the resource multiplexing indication information indicates resource multiplexing and repetition and slot aggregation are indicated, the method further includes transmitting data using one of the resource multiplexing or the repetition and slot aggregation based on priority information. Method of the first communication node.
11. In the first communication node, At least one processor, wherein the first communication node comprises: Receive resource multiplexing setting information from a second communication node; Receive resource multiplexing instruction information from the second communication node; and Causing data to be resource multiplexed and transmitted to the second communication node based on the above resource multiplexing instruction information. First communication node.
12. In claim 11, Each of the orthogonal sequences included in the first orthogonal sequence set and the second orthogonal sequence set is a sequence selected from a nominal sequence book containing all mutually orthogonal sequences. First communication node.
13. In claim 11, Receive resource multiplexing capability information of the second communication node from the second communication node; and Further causing the resource multiplexing capability information of the first communication node to be transmitted to the second communication node before receiving the resource multiplexing setting information. First communication node.
14. In claim 11, The orthogonal sequences included in each of the first orthogonal sequence set and the second orthogonal sequence set are composed of some sequences that are consecutive in a nominal sequence book that includes all sequences, and when the first orthogonal sequence set and the second orthogonal sequence set are relatively prime, the resource multiplexing indication information is indicated by a combination of two of a start sequence index, a last sequence index, or a number of sequence indices of orthogonal sequences to be used for resource multiplexing. First communication node.
15. In claim 11, The at least one processor is configured such that the first communication node: After receiving the above resource multiplexing setting information, if there is data to be transmitted to the second communication node, a scheduling request message is further caused to be transmitted to the second communication node. The above resource multiplexing instruction information is included in a scheduling grant message received from the second communication node. First communication node.
16. In claim 11, The at least one processor is configured such that the first communication node: If there is a third communication node to which the same resources as those allocated to the first communication node exist from the second communication node, and at least one of the resource multiplexing application status, resource multiplexing sequence size, resource multiplexing sequence type, resource multiplexing application scope granularity, resource multiplexing application scope size, resource multiplexing application scope location, resource multiplexing application number, or resource multiplexing application order included in the resource multiplexing instruction information transmitted to the first communication node and the resource multiplexing instruction information transmitted to the third communication node are different, it is further caused to determine that resource multiplexing is not indicated in the resources allocated to the first communication node. First communication node.
17. In claim 11, The at least one processor is configured such that the first communication node: The above resource multiplexing indication information indicates resource multiplexing, and if repetition and slot aggregation are indicated, further causes data to be transmitted using one of the resource multiplexing or the repetition and slot aggregation methods based on priority information. First communication node.
18. In the method of the second communication node, A step of transmitting resource multiplexing setting information to a first communication node; A step of transmitting resource multiplexing instruction information to the first communication node; and A step of receiving data from the first communication node based on the resource multiplexing instruction information, Method of the second communication node.
19. In claim 18, A step of transmitting resource multiplexing capability information of the second communication node to the first communication node; and Further comprising a step of receiving resource multiplexing capability information of the first communication node from the first communication node before transmitting the resource multiplexing setting information. Method of the second communication node.
20. In claim 18, Further comprising a step of transmitting repetition and slot aggregation indication information and resource multiplexing and priority information of the repetition and slot aggregation together with the resource multiplexing indication information to the first communication node. Method of the second communication node.
Citation Information
Patent Citations
Method of transmitting information in wireless communication system
KR1020100019953A
Ultrasonic emission and LED lighting device used for display stand
KR1020220011358A
Systems and methods for hair rasterization
KR102638813B1
Operating method for IAB node in wireless communication system, and device using method
WO2021086147A1
KR20230133879A