Patent Application
20250071816
The present disclosure relates to a wireless communication system, and in more detail, relates to a method and an apparatus of performing a random access procedure in a wireless communication system.
A mobile communication system has been developed to provide a voice service while guaranteeing mobility of users. However, a mobile communication system has extended even to a data service as well as a voice service, and currently, an explosive traffic increase has caused shortage of resources and users have demanded a faster service, so a more advanced mobile communication system has been required.
The requirements of a next-generation mobile communication system at large should be able to support accommodation of explosive data traffic, a remarkable increase in a transmission rate per user, accommodation of the significantly increased number of connected devices, very low End-to-End latency and high energy efficiency. To this end, a variety of technologies such as Dual Connectivity, Massive Multiple Input Multiple Output (Massive MIMO), In-band Full Duplex, Non-Orthogonal Multiple Access (NOMA), Super wideband Support, Device Networking, etc. have been researched.
The technical object of the present disclosure is to provide a method and apparatus for performing a random access procedure in a wireless communication system.
A technical object of the present disclosure is to provide a method and apparatus for configuring/indicating repetition transmission of Message 3 (Msg 3) PUSCH in performing a random access procedure.
The technical objects to be achieved by the present disclosure are not limited to the above-described technical objects, and other technical objects which are not described herein will be clearly understood by those skilled in the pertinent art from the following description.
A method of performing random access procedure by a user equipment (UE) in a wireless communication system according to an aspect of the present disclosure may comprise: receiving, from a base station, information on a Modulation and Coding Scheme (MCS) index group for the Message 3 Physical Uplink Shared Channel (Msg3 PUSCH), based on repetition transmission of the Msg3 PUSCH being configured, the MCS index group includes one or more MCS index values; receiving, from the base station, MCS information indicating a specific MCS index value among the one or more MCS index values; and transmitting the Msg3 PUSCH based on the specific MCS index value indicated by the MCS information. Herein, the MCS information may be configured to some bits of an MCS field related to the Msg3 PUSCH.
A method of performing random access procedure by a base station in a wireless communication system according to an additional aspect of the present disclosure may comprise: transmitting, to a user equipment (UE), information on a Modulation and Coding Scheme (MCS) index group for the Message 3 Physical Uplink Shared Channel (Msg3 PUSCH), based on repetition transmission of the Msg3 PUSCH being configured, the MCS index group includes one or more MCS index values; transmitting, to the UE, MCS information indicating a specific MCS index value among the one or more MCS index values; and receiving the Msg3 PUSCH based on the specific MCS index value indicated by the MCS information. Herein, the MCS information may be configured to some bits of an MCS field related to the Msg3 PUSCH.
According to an embodiment of the present disclosure, a higher Modulation and Coding Scheme (MCS) value may be indicated/designated without increasing the number of bits for designating/indicating a MCS in downlink control information.
In addition, according to an embodiment of the present disclosure, when transmitting PUSCH of Msg 3 during a random access procedure, it is possible to effectively use frequency resources by adaptively indicating various MCS even in a situation where a limited MCS field is used, and resource efficiency may be improved by applying MCS to use a small amount of frequency resources.
Effects achievable by the present disclosure are not limited to the above-described effects, and other effects which are not described herein may be clearly understood by those skilled in the pertinent art from the following description.
Accompanying drawings included as part of detailed description for understanding the present disclosure provide embodiments of the present disclosure and describe technical features of the present disclosure with detailed description.
Hereinafter, embodiments according to the present disclosure will be described in detail by referring to accompanying drawings. Detailed description to be disclosed with accompanying drawings is to describe exemplary embodiments of the present disclosure and is not to represent the only embodiment that the present disclosure may be implemented. The following detailed description includes specific details to provide complete understanding of the present disclosure. However, those skilled in the pertinent art knows that the present disclosure may be implemented without such specific details.
In some cases, known structures and devices may be omitted or may be shown in a form of a block diagram based on a core function of each structure and device in order to prevent a concept of the present disclosure from being ambiguous.
In the present disclosure, when an element is referred to as being “connected”, “combined” or “linked” to another element, it may include an indirect connection relation that yet another element presents therebetween as well as a direct connection relation. In addition, in the present disclosure, a term, “include” or “have”, specifies the presence of a mentioned feature, step, operation, component and/or element, but it does not exclude the presence or addition of one or more other features, stages, operations, components, elements and/or their groups.
In the present disclosure, a term such as “first”, “second”, etc. is used only to distinguish one element from other element and is not used to limit elements, and unless otherwise specified, it does not limit an order or importance, etc. between elements. Accordingly, within a scope of the present disclosure, a first element in an embodiment may be referred to as a second element in another embodiment and likewise, a second element in an embodiment may be referred to as a first element in another embodiment.
A term used in the present disclosure is to describe a specific embodiment, and is not to limit a claim. As used in a described and attached claim of an embodiment, a singular form is intended to include a plural form, unless the context clearly indicates otherwise. A term used in the present disclosure, “and/or”, may refer to one of related enumerated items or it means that it refers to and includes any and all possible combinations of two or more of them. In addition, “/” between words in the present disclosure has the same meaning as “and/or”, unless otherwise described.
The present disclosure describes a wireless communication network or a wireless communication system, and an operation performed in a wireless communication network may be performed in a process in which a device (e.g., a base station) controlling a corresponding wireless communication network controls a network and transmits or receives a signal, or may be performed in a process in which a terminal associated to a corresponding wireless network transmits or receives a signal with a network or between terminals.
In the present disclosure, transmitting or receiving a channel includes a meaning of transmitting or receiving information or a signal through a corresponding channel. For example, transmitting a control channel means that control information or a control signal is transmitted through a control channel. Similarly, transmitting a data channel means that data information or a data signal is transmitted through a data channel.
Hereinafter, a downlink (DL) means a communication from a base station to a terminal and an uplink (UL) means a communication from a terminal to a base station. In a downlink, a transmitter may be part of a base station and a receiver may be part of a terminal. In an uplink, a transmitter may be part of a terminal and a receiver may be part of a base station. A base station may be expressed as a first communication device and a terminal may be expressed as a second communication device. A base station (BS) may be substituted with a term such as a fixed station, a Node B, an eNB (evolved-NodeB), a gNB (Next Generation NodeB), a BTS (base transceiver system), an Access Point (AP), a Network (5G network), an AI (Artificial Intelligence) system/module, an RSU (road side unit), a robot, a drone (UAV: Unmanned Aerial Vehicle), an AR (Augmented Reality) device, a VR (Virtual Reality) device, etc. In addition, a terminal may be fixed or mobile, and may be substituted with a term such as a UE (User Equipment), an MS (Mobile Station), a UT (user terminal), an MSS (Mobile Subscriber Station), an SS (Subscriber Station), an AMS (Advanced Mobile Station), a WT (Wireless terminal), an MTC (Machine-Type Communication) device, an M2M (Machine-to-Machine) device, a D2D (Device-to-Device) device, a vehicle, an RSU (road side unit), a robot, an AI (Artificial Intelligence) module, a drone (UAV: Unmanned Aerial Vehicle), an AR (Augmented Reality) device, a VR (Virtual Reality) device, etc.
The following description may be used for a variety of radio access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented by a wireless technology such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA may be implemented by a radio technology such as GSM (Global System for Mobile communications)/GPRS (General Packet Radio Service)/EDGE (Enhanced Data Rates for GSM Evolution). OFDMA may be implemented by a radio technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), etc. UTRA is a part of a UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of an E-UMTS (Evolved UMTS) using E-UTRA and LTE-A (Advanced)/LTE-A pro is an advanced version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE/LTE-A/LTE-A pro.
To clarify description, it is described based on a 3GPP communication system (e.g., LTE-A, NR), but a technical idea of the present disclosure is not limited thereto. LTE means a technology after 3GPP TS (Technical Specification) 36.xxx Release 8. In detail, an LTE technology in or after 3GPP TS 36.xxx Release 10 is referred to as LTE-A and an LTE technology in or after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR means a technology in or after TS 38.xxx Release 15. LTE/NR may be referred to as a 3GPP system. “xxx” means a detailed number for a standard document. LTE/NR may be commonly referred to as a 3GPP system. For a background art, a term, an abbreviation, etc. used to describe the present disclosure, matters described in a standard document disclosed before the present disclosure may be referred to. For example, the following document may be referred to.
For 3GPP LTE, TS 36.211 (physical channels and modulation), TS 36.212 (multiplexing and channel coding), TS 36.213 (physical layer procedures), TS 36.300 (overall description), TS 36.331 (radio resource control) may be referred to.
For 3GPP NR, TS 38.211 (physical channels and modulation), TS 38.212 (multiplexing and channel coding), TS 38.213 (physical layer procedures for control), TS 38.214 (physical layer procedures for data), TS 38.300 (NR and NG-RAN (New Generation-Radio Access Network) overall description), TS 38.331 (radio resource control protocol specification) may be referred to.
Abbreviations of terms which may be used in the present disclosure is defined as follows.
As more communication devices have required a higher capacity, a need for an improved mobile broadband communication compared to the existing radio access technology (RAT) has emerged. In addition, massive MTC (Machine Type Communications) providing a variety of services anytime and anywhere by connecting a plurality of devices and things is also one of main issues which will be considered in a next-generation communication. Furthermore, a communication system design considering a service/a terminal sensitive to reliability and latency is also discussed. As such, introduction of a next-generation RAT considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (Ultra-Reliable and Low Latency Communication), etc. is discussed and, for convenience, a corresponding technology is referred to as NR in the present disclosure. NR is an expression which represents an example of a 5G RAT.
A new RAT system including NR uses an OFDM transmission method or a transmission method similar to it. A new RAT system may follow OFDM parameters different from OFDM parameters of LTE. Alternatively, a new RAT system follows a numerology of the existing LTE/LTE-A as it is, but may support a wider system bandwidth (e.g., 100 MHz). Alternatively, one cell may support a plurality of numerologies. In other words, terminals which operate in accordance with different numerologies may coexist in one cell.
A numerology corresponds to one subcarrier spacing in a frequency domain. As a reference subcarrier spacing is scaled by an integer N, a different numerology may be defined.
In reference to
A NR system may support a plurality of numerologies. Here, a numerology may be defined by a subcarrier spacing and a cyclic prefix (CP) overhead. Here, a plurality of subcarrier spacings may be derived by scaling a basic (reference) subcarrier spacing by an integer N (or, u). In addition, although it is assumed that a very low subcarrier spacing is not used in a very high carrier frequency, a used numerology may be selected independently from a frequency band. In addition, a variety of frame structures according to a plurality of numerologies may be supported in a NR system.
Hereinafter, an OFDM numerology and frame structure which may be considered in a NR system will be described. A plurality of OFDM numerologies supported in a NR system may be defined as in the following Table 1.
NR supports a plurality of numerologies (or subcarrier spacings (SCS)) for supporting a variety of 5G services. For example, when a SCS is 15 kHz, a wide area in traditional cellular bands is supported, and when a SCS is 30 kHz/60 kHz, dense-urban, lower latency and a wider carrier bandwidth are supported, and when a SCS is 60 kHz or higher, a bandwidth wider than 24.25 GHz is supported to overcome a phase noise.
An NR frequency band is defined as a frequency range in two types (FR1, FR2). FR1, FR2 may be configured as in the following Table 2. In addition, FR2 may mean a millimeter wave (mmW).
Regarding a frame structure in an NR system, a size of a variety of fields in a time domain is expresses as a multiple of a time unit of Tc=1/(Δfmax·Nf). Here, Δfmax is 480.103 Hz and Nf is 4096. Downlink and uplink transmission is configured (organized) with a radio frame having a duration of Tf=1/(ΔfmaxNf/100)·Tc=10 ms. Here, a radio frame is configured with 10 subframes having a duration of Tsf=(ΔfmaxNf/1000)·Tc=1 ms, respectively. In this case, there may be one set of frames for an uplink and one set of frames for a downlink. In addition, transmission in an uplink frame No. i from a terminal should start earlier by TTA=(NTA+NTA,offset) Tc than a corresponding downlink frame in a corresponding terminal starts. For a subcarrier spacing configuration μ, slots are numbered in an increasing order of ns,fμ∈{0, . . . , Nslotsubframe,μ−1} in a subframe and are numbered in an increasing order of ns,fμ∈{0, . . . , Nslotframe,μ−1} in a radio frame. One slot is configured with Nsymbslot consecutive OFDM symbols and Nsymbslot is determined according to CP. A start of a slot nsμ in a subframe is temporally arranged with a start of an OFDM symbol nsμNsymbslot in the same subframe. All terminals may not perform transmission and reception at the same time, which means that all OFDM symbols of a downlink slot or an uplink slot may not be used.
Table 3 represents the number of OFDM symbols per slot (Nsymbslot), the number of slots per radio frame (Nslotframe,μ) and the number of slots per subframe (Nslotsubframe,μ) in a normal CP and Table 4 represents the number of OFDM symbols per slot, the number of slots per radio frame and the number of slots per subframe in an extended CP.
Regarding a physical resource in a NR system, an antenna port, a resource grid, a resource element, a resource block, a carrier part, etc. may be considered. Hereinafter, the physical resources which may be considered in an NR system will be described in detail.
First, in relation to an antenna port, an antenna port is defined so that a channel where a symbol in an antenna port is carried can be inferred from a channel where other symbol in the same antenna port is carried. When a large-scale property of a channel where a symbol in one antenna port is carried may be inferred from a channel where a symbol in other antenna port is carried, it may be said that 2 antenna ports are in a QC/QCL (quasi co-located or quasi co-location) relationship. In this case, the large-scale property includes at least one of delay spread, doppler spread, frequency shift, average received power, received timing.
In reference to
Point A plays a role as a common reference point of a resource block grid and is obtained as follows.
offsetToPointA for a primary cell (PCell) downlink represents a frequency offset between point A and the lowest subcarrier of the lowest resource block overlapped with a SS/PBCH block which is used by a terminal for an initial cell selection. It is expressed in resource block units assuming a 15 kHz subcarrier spacing for FR1 and a 60 kHz subcarrier spacing for FR2.
absoluteFrequencyPointA represents a frequency-position of point A expressed as in ARFCN (absolute radio-frequency channel number).
Common resource blocks are numbered from 0 to the top in a frequency domain for a subcarrier spacing configuration μ. The center of subcarrier 0 of common resource block 0 for a subcarrier spacing configuration u is identical to ‘point A’. A relationship between a common resource block number nCRBμ and a resource element (k,l) for a subcarrier spacing configuration μ in a frequency domain is given as in the following Equation 1.
In Equation 1, k is defined relatively to point A so that k=0 corresponds to a subcarrier centering in point A. Physical resource blocks are numbered from 0 to NBWP,isize,μ−1 in a bandwidth part (BWP) and i is a number of a BWP. A relationship between a physical resource block nPRB and a common resource block nCRB in BWP i is given by the following Equation 2.
NBWP,istart,μ is a common resource block that a BWP starts relatively to common resource block 0.
In reference to
A carrier includes a plurality of subcarriers in a frequency domain. An RB (Resource Block) is defined as a plurality of (e.g., 12) consecutive subcarriers in a frequency domain. A BWP (Bandwidth Part) is defined as a plurality of consecutive (physical) resource blocks in a frequency domain and may correspond to one numerology (e.g., an SCS, a CP length, etc.). A carrier may include a maximum N (e.g., 5) BWPs. A data communication may be performed through an activated BWP and only one BWP may be activated for one terminal. In a resource grid, each element is referred to as a resource element (RE) and one complex symbol may be mapped.
In an NR system, up to 400 MHz may be supported per component carrier (CC). If a terminal operating in such a wideband CC always operates turning on a radio frequency (FR) chip for the whole CC, terminal battery consumption may increase. Alternatively, when several application cases operating in one wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.) are considered, a different numerology (e.g., a subcarrier spacing, etc.) may be supported per frequency band in a corresponding CC. Alternatively, each terminal may have a different capability for the maximum bandwidth. By considering it, a base station may indicate a terminal to operate only in a partial bandwidth, not in a full bandwidth of a wideband CC, and a corresponding partial bandwidth is defined as a bandwidth part (BWP) for convenience. A BWP may be configured with consecutive RBs on a frequency axis and may correspond to one numerology (e.g., a subcarrier spacing, a CP length, a slot/a mini-slot duration).
Meanwhile, a base station may configure a plurality of BWPs even in one CC configured to a terminal. For example, a BWP occupying a relatively small frequency domain may be configured in a PDCCH monitoring slot, and a PDSCH indicated by a PDCCH may be scheduled in a greater BWP. Alternatively, when UEs are congested in a specific BWP, some terminals may be configured with other BWP for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, etc., some middle spectrums of a full bandwidth may be excluded and BWPs on both edges may be configured in the same slot. In other words, a base station may configure at least one DL/UL BWP to a terminal associated with a wideband CC. A base station may activate at least one DL/UL BWP of configured DL/UL BWP(s) at a specific time (by L1 signaling or MAC CE (Control Element) or RRC signaling, etc.). In addition, a base station may indicate switching to other configured DL/UL BWP (by L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, based on a timer, when a timer value is expired, it may be switched to a determined DL/UL BWP. Here, an activated DL/UL BWP is defined as an active DL/UL BWP. But, a configuration on a DL/UL BWP may not be received when a terminal performs an initial access procedure or before a RRC connection is set up, so a DL/UL BWP which is assumed by a terminal under these situations is defined as an initial active DL/UL BWP.
In a wireless communication system, a terminal receives information through a downlink from a base station and transmits information through an uplink to a base station. Information transmitted and received by a base station and a terminal includes data and a variety of control information and a variety of physical channels exist according to a type/a usage of information transmitted and received by them.
When a terminal is turned on or newly enters a cell, it performs an initial cell search including synchronization with a base station or the like (S601). For the initial cell search, a terminal may synchronize with a base station by receiving a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from a base station and obtain information such as a cell identifier (ID), etc. After that, a terminal may obtain broadcasting information in a cell by receiving a physical broadcast channel (PBCH) from a base station. Meanwhile, a terminal may check out a downlink channel state by receiving a downlink reference signal (DL RS) at an initial cell search stage.
A terminal which completed an initial cell search may obtain more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S602).
Meanwhile, when a terminal accesses to a base station for the first time or does not have a radio resource for signal transmission, it may perform a random access (RACH) procedure to a base station (S603 to S606). For the random access procedure, a terminal may transmit a specific sequence as a preamble through a physical random access channel (PRACH) (S603 and S605) and may receive a response message for a preamble through a PDCCH and a corresponding PDSCH (S604 and S606). A contention based RACH may additionally perform a contention resolution procedure.
A terminal which performed the above-described procedure subsequently may perform PDCCH/PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel)/PUCCH (physical uplink control channel) transmission (S608) as a general uplink/downlink signal transmission procedure. In particular, a terminal receives downlink control information (DCI) through a PDCCH. Here, DCI includes control information such as resource allocation information for a terminal and a format varies depending on its purpose of use.
Meanwhile, control information which is transmitted by a terminal to a base station through an uplink or is received by a terminal from a base station includes a downlink/uplink ACK/NACK (Acknowledgement/Non-Acknowledgement) signal, a CQI (Channel Quality Indicator), a PMI (Precoding Matrix Indicator), a RI (Rank Indicator), etc. For a 3GPP LTE system, a terminal may transmit control information of the above-described CQI/PMI/RI, etc. through a PUSCH and/or a PUCCH.
Table 5 represents an example of a DCI format in an NR system.
In reference to Table 5, DCI formats 0_0, 0_1 and 0_2 may include resource information (e.g., UL/SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to a transport block (TB) (e.g., MCS (Modulation Coding and Scheme), a NDI (New Data Indicator), a RV (Redundancy Version), etc.), information related to a HARQ (Hybrid-Automatic Repeat and request) (e.g., a process number, a DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, an antenna port, a CSI request, etc.), power control information (e.g., PUSCH power control, etc.) related to scheduling of a PUSCH and control information included in each DCI format may be pre-defined.
DCI format 0_0 is used for scheduling of a PUSCH in one cell. Information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled by a C-RNTI (Cell Radio Network Temporary Identifier) or a CS-RNTI (Configured Scheduling RNTI) or a MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.
DCI format 0_1 is used to indicate scheduling of one or more PUSCHs or configure grant (CG) downlink feedback information to a terminal in one cell. Information included in DCI format 0_1 is CRC scrambled by a C-RNTI or a CS-RNTI or a SP-CSI-RNTI (Semi-Persistent CSI RNTI) or a MCS-C-RNTI and transmitted.
DCI format 0_2 is used for scheduling of a PUSCH in one cell. Information included in DCI format 0_2 is CRC scrambled by a C-RNTI or a CS-RNTI or a SP-CSI-RNTI or a MCS-C-RNTI and transmitted.
Next, DCI formats 1_0, 1_1 and 1_2 may include resource information (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block)-PRB (physical resource block) mapping, etc.), information related to a transport block (TB) (e.g., MCS, NDI, RV, etc.), information related to a HARQ (e.g., a process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., an antenna port, a TCI (transmission configuration indicator), a SRS (sounding reference signal) request, etc.), information related to a PUCCH (e.g., PUCCH power control, a PUCCH resource indicator, etc.) related to scheduling of a PDSCH and control information included in each DCI format may be pre-defined.
DCI format 1_0 is used for scheduling of a PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled by a C-RNTI or a CS-RNTI or a MCS-C-RNTI and transmitted.
DCI format 1_1 is used for scheduling of a PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled by a C-RNTI or a CS-RNTI or a MCS-C-RNTI and transmitted.
DCI format 1_2 is used for scheduling of a PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled by a C-RNTI or a CS-RNTI or a MCS-C-RNTI and transmitted.
For the UE to connect to the NR network, the UE shall be synchronized not only for the DL but also for the UL. DL synchronization is performed by the UE detecting and decoding the SSB and PBCH broadcasted by the base station. For UL synchronization, the UE shall perform a random access procedure with the base station. Random access procedures are broadly classified into two types as follows.
CBRA includes the Msg3 transmission process of the UE, but CFRA does not include the Msg3 transmission process. Since the present disclosure proposes content related to PUSCH repetition transmission of Msg3, only CBRA is described.
Referring to
Specifically, in step S710, the UE transmits a randomly selected preamble (i.e., RA preamble) to the base station. Through this, a random access procedure is initiated.
In step S720, the base station transmits an RA response (RAR) corresponding to a response to the preamble to the UE through the PDSCH. Here, the RAR includes preamble identification information (e.g. ID, etc.), UL grant for msg3, Timing alignment (TA) information, temporary C-RNTI information, etc.
After transmitting the preamble, the UE monitors the PDCCH and attempts to receive RAR within the RAR reception window. If the UE receives a response including identification information corresponding to the transmitted RA preamble, the UE determines that the RA preamble transmission was successful. Thereafter, in step S730, the UE transmits Msg3 to the base station using the UL grant information in the RAR.
If the RAR containing identification information corresponding to the RA preamble transmitted by the UE is not received within the RAR reception window, the UE determines that the RA preamble transmission has failed and retransmits the RA preamble.
In step S740, the base station that received Msg3 transmits Msg4 to the UE for contention resolution and connection establishment (e.g., connection set up, RRC connection establishment, etc.).
Here, the RAR UL grant included in RAR includes parameter information required for Msg3 transmission.
Table 6 shows an example of a RAR UL grant in the NR system.
According to the current NR standardization standard, Msg3 PUSCH is restricted to single-slot transmission that does not perform repetition transmission.
Table 7 shows an example of specifications related to Msg3 PUSCH transmission in the current NR system.
Additionally, in relation to the current discussion on standardization of coverage enhancement, Msg3 PUSCH is being considered as one of the channels that needs coverage improvement, and discussion on improving coverage for Msg3 PUSCH may correspond to the matters shown in Table 8 below.
Referring to Table 8, in order to improve the coverage of Msg3 PUSCH, the introduction of repetitive transmission of Msg3 PUSCH is being considered, and accordingly, configuration/indication methods related to the number of repetitions, repetition types, etc. need to be additionally discussed/considered.
The Modulation and Coding scheme (MCS) table used for general PUSCH transmission includes 32 MCS indexes. In order for the base station to select one of the MCS indexes and indicate it to the UE, a 5-bit MCS field is required. As an example, the MCS field of DCI format 0_0, which indicates general PUSCH transmission, is configured/defined to have a length of 5 bits.
Regarding Msg3 PUSCH transmission in the above-described random access procedure, the MCS index to be applied by the UE to Msg3 PUSCH transmission may be indicated from the base station through the MCS field included in the RAR UL grant. As an example, referring to Table 6 above, the MCS field of the RAR UL grant is configured/defined to be 4 bits long, unlike other general MCS fields. The value indicated through this is interpreted as the MCS index of the first 16 MCS tables applicable to the UE and applied to Msg3 PUSCH transmission. That is, the UE may determine the MCS of Msg3 PUSCH transmission from the 16 indexes of the applicable MCS index table predefined for PUSCH.
At this time, as repetition transmission is introduced for Msg3 PUSCH to improve coverage, as described above, there is discussion in standardization about how the base station may indicate the repetition number to be applied by the UE. In this regard, one of the time domain resource assignment (TDRA) field, MCS field, or TPC field among the fields of the RAR UL grant may be selected and used to indicate the number of repetitions. NR standardization discussions related to this are shown in Table 9 below.
If the number of repetitions is indicated using the MCS field, and a certain bit (e.g., X bit) of the 4-bit MCS field is used for this, unlike the existing case, MCS index information for Msg3 transmission may need to be indicated through only some bits (e.g., 4-X bits) of the MCS field.
At this time, considering the MCS index indication method for coverage improvement and existing Msg3 transmission, a method of using the first 2{circumflex over ( )}(4-X) consecutive MCS indices to correspond to the number of bits (e.g., 4-X) of the remaining MCS field may be considered. However, in the case of this method, the rate (e.g. coding rate) is always limited to lower MCS use, which may be inefficient in terms of resource management.
In order to solve these problems, sa method by which the base station may indicate the appropriate/proper MCS index to the UE using the remaining part of the MCS field, when Type A PUSCH repetition (i.e., Type A PUSCH repetition) is applied to Msg3 PUSCH transmission in order to improve the coverage of the UE and the number of repetitions is indicated through part of the MCS field of the RAR UL grant will be proposed in the present disclosure.
In this regard, based on pre-configured/defined MCS table(s) (e.g., MCS table(s) related to general PUSCH transmission), a method of configuring/indicating an MCS index subset related to repeated transmission of Msg3 PUSCH may be considered/applied.
The embodiments described in the present disclosure are divided only for convenience of explanation, and each embodiment may be applied independently, or some configurations of the embodiments may be applied in combination, of course.
This embodiment relates to a method of using contiguous MCS indexes (based on pre-configured/defined MCS table(s)) but assigning/specifying only the start index.
For example, a method in which the base station additionally indicates a start index to the UE through system information (SI) (e.g., SIB, etc.) in advance (i.e., pre-) may be considered. At this time, the UE may interpret the corresponding start index value as the minimum value of the MCS index subset available for the repeatedly transmitted Msg3 PUSCH. In other words, a certain number (e.g., 2{circumflex over ( )}(4-X)) of MCS indexes consecutive from the corresponding index (i.e., the start index) may constitute a usable MCS index subset.
The base station may indicate information on the MCS index to be actually used to the UE using the MCS field of some bits (e.g., 4-X bits) remaining in the RAR UL grant. At this time, in order for the UE to interpret the indicated value as the MCS index to be actually used, the terminal may be configured to list the MCS indexes included in the MCS index subset configured as described above in increasing order and then use the MCS index of the order corresponding to the indicated value.
In the case of the method proposed in this embodiment, compared to the method of using the first certain number (e.g., 2{circumflex over ( )}(4-X)) of consecutive MCS indexes without separate pre-indication, there is an advantage in being able to use a higher MCS with a higher rate (e.g. coding rate) depending on the network situation.
This embodiment relates to a method of configuring/setting and indicating the entire MCS index subset (based on pre-configured/defined MCS table(s)).
For example, a method in which the base station configures/sets an MCS index subset to the UE through system information (SI) (e.g., SIB, etc.) in advance (i.e., pre-) may be considered. That is, the base station may select a certain number (e.g., 2{circumflex over ( )}(4-X)) of MCS indexes to form an MCS index subset and configure/indicate the UE in advance. The method may be a method of configuring/indicating a certain number (e.g., 2{circumflex over ( )}(4-X)) of MCS indexes and may be a method of indicating one of the candidates of a pre-configured/promised MCS index subset.
The base station may indicate information on the MCS index to be actually used to the UE using the MCS field of some bits (e.g., 4-X bits) remaining in the RAR UL grant. At this time, in order for the UE to interpret the indicated value as the MCS index to be actually used, the UE may be configured to list the MCS indexes included in the MCS index subset configured as described above in increasing order and then use the MCS index of the order corresponding to the indicated value.
In the case of the method proposed in this embodiment, compared to a method that has no choice but to configure an MCS index subset only with continuous MCS indexes (e.g., a method according to the existing method, the method in Embodiment 1 described above, etc.), an MCS index subset may also be configured from non-contiguous MCS indexes. This has the advantage of being able to configure an MCS index subset with MCS indices corresponding to a wider range of rates (e.g., coding rate).
This embodiment relates to a method for setting/configuring/indicating an MCS index subset (based on pre-configure/defined MCS table(s)) based on/linked to the maximum (max) value of the number of repetitions available to the UE in relation to repetition transmission of Msg3 PUSCH.
For example, a method of configuring the MCS index subset differently depending on the maximum value of the number of available repetitions may be considered. Here, the maximum value of the number of repetitions available may be information configured by the base station to the UE in advance through system information (SI) (e.g. SIB, etc.).
The following example methods may be used to configure an MCS index subset using the maximum value of the number of repetitions available to the UE.
As an example, if the maximum value of the number of available repetitions is greater than a certain reference value, the UE may configure a certain number (e.g., 2{circumflex over ( )}(4-X)) of consecutive MCS indexes with the lowest rate (e.g., coding rate) as an MCS index subset. As another example, if the maximum number of available iterations is below a certain threshold value, the UE may configure a certain number (e.g., 2{circumflex over ( )}(4-X)) of contiguous MCS indexes with the highest rate (e.g., coding rate) as an MCS index subset. Here, the base station may configure/indicate the UE with information on a specific reference value in the above-described example.
The base station may indicate information on the MCS index to be actually used to the UE using the MCS field of some bits (e.g., 4-X bits) remaining in the RAR UL grant. At this time, in order for the UE to interpret the indicated value as the MCS index to be actually used, the UE may be configured to list the MCS indexes included in the MCS index subset configured as described above in increasing order and then use the MCS index of the order corresponding to the indicated value.
In the case of the method proposed in this embodiment, by associating/linking the MCS index subset with the maximum value of the number of available repetitions, the overhead for MCS instructions may be reduced. Additionally, this method has the advantage of being able to configure and use an MCS index subset with a wider range of rates (e.g., coding rate).
This embodiment relates to a method of configuring/setting and indicating an MCS index subset based on/linked to the number of repetitions configured/indicated to the UE in relation to repetition transmission of Msg3 PUSCH.
For example, a method of configuring the MCS index subset differently depending on the repetition number value indicated to the UE may be considered. Here, the indicated repetition number value may be a value interpreted through information indicated for each UE through some bits (e.g., X bits) of the MCS field of the RAR UL grant.
The following example methods may be used for the UE to configure an MCS index subset through the indicated repetition number value.
As an example, when the indicated repetition number value is greater than a specific reference value, the UE may configure a certain number (e.g., 2{circumflex over ( )}(4-X)) of consecutive MCS indexes with the lowest rate (e.g., coding rate) as an MCS index subset. As another example, if the indicated repetition number value is below a certain reference value, the UE may configure a certain number (e.g., 2{circumflex over ( )}(4-X)) of consecutive MCS indexes with the highest rate (e.g., coding rate) as an MCS index subset. Here, the base station may configure/indicate the UE with information about a specific reference value in the above-described example.
Additionally/alternatively, in order to increase resource operation efficiency by configuring an MCS index subset with non-contiguous MCS indexes, depending on the indicated repetition number value, the interval between MCS indexes belonging to/included in the MCS index subset may be configured differently. In this regard, the following example method may be used.
For example, if the indicated repetition number value is 2N, the MCS index subset may be {(4−N)m|0<=m<2{circumflex over ( )}(4−X)}. With respect to the MCS index subset configured according to that example, if the indicated repetition number value is low, the MCS index subset may be composed of MCS indices with wider intervals. Conversely, when the indicated repetition number value is large, the MCS index subset may be composed of MCS indices with narrower intervals. That is, if the indicated repetition number value is 1, an MCS index subset may be composed of MCS indexes with the widest intervals, in order to cover the entire range of MCS indexes that were available in existing Msg3 transmission.
The base station may indicate information on the MCS index to be actually used to the UE using the MCS field of some bits (e.g., 4-X bits) remaining in the RAR UL grant. At this time, in order for the UE to interpret the indicated value as the MCS index to be actually used, the UE may be configured to list the MCS indexes included in the MCS index subset configured as described above in increasing order and then use the MCS index of the order corresponding to the indicated value.
In the case of the method proposed in this embodiment, by associating/linking the repetition number indicated for each UE with the MCS index subset, the overhead for MCS indication may be reduced. In addition, when using the remaining bits of the MCS field among the UL grant fields to indicate the repetition number value indicated for each UE, a problem of using excessively many frequency resources may occur by indicating a lower MCS value. In contrast, in the case of the method proposed in this embodiment, since various MCS values may be used adaptively according to network conditions, there is an advantage in that excessive use of frequency resources may be prevented. Additionally, the method proposed in this embodiment has the advantage of being able to configure and use MCS index subsets with a different and wider range of rates (e.g., coding rates).
In addition, the methods proposed in the embodiments described above in the present disclosure may be applied with the same/similar principles to not only when the repetition count value is indicated through part of the MCS field of the RAR UL grant, but also when it is indicated through part of the MCS field of the DCI (e.g., the MCS field of DCI format 0_0, etc.) regarding repetition transmission of Msg3 PUSCH.
In step S810, based on/according to the repetition transmission for Msg3 PUSCH being configured, the UE may receive information on the MCS index group for Msg3 PUSCH from the base station. That is, the UE may receive information on the MCS index group for repetition transmission of Msg3 PUSCH from the base station. Here, the MCS index group may include one or more MCS index values and may correspond to an MCS index subset in the above-described embodiments (e.g., Embodiments 1 to 4, especially Embodiment 2).
For example, the repetition transmission of the Msg3 PUSCH described above may be based on Type A-based PUSCH repetition transmission (e.g., PUSCH repetition Type A).
Additionally, one or more index values included in the MCS index group may include at least one of contiguous MCS index values or non-contiguous MCS index values. That is, the MCS index group may be composed of contiguous MCS index values and/or non-contiguous MCS index values. In this case, the one or more MCS index values may be assigned to codepoints of the MCS field (in increasing order) within the MCS index group.
Additionally, information on the MCS index group may be configured to the UE through system information (SI) (e.g., SIB, etc.) based on higher layer signaling (e.g., RRC signaling, etc.). Additionally, the corresponding MCS index group may be configured based on an MCS table applicable to the UE among one or more pre-defined MCS tables.
In step S820, the UE may receive MCS information indicating a specific MCS index value among the one or more MCS index values from the base station. Here, the corresponding MCS information may be configured to some bits of the MCS field related to the above-described Msg3 PUSCH.
For example, as in the embodiments described above (e.g. Embodiments 1 to 4, especially Embodiment 2), the base station may indicate the UE the MCS value to be applied to Msg3 PUSCH transmission (e.g., Msg3 PUSCH repetition transmission) through some bits (e.g. 4-X bit, 5-X bit) of the MCS field included in the information scheduling Msg3 PUSCH. At this time, the size of the corresponding some bits may be related to the number of MCS indexes included in the above-described MCS index group. As an example, if the MCS index group includes a certain number (e.g., 2{circumflex over ( )}(4-X)) of MCS indexes, the MCS value may be indicated to the UE through the above-described some bits (e.g., 4-X bits, 5-X bits) of MCS field.
At this time, as in the above-described embodiments (e.g., Embodiments 1 to 4, especially Embodiment 2), the MCS field may be included in at least one of a RAR UL grant related to the Msg3 PUSCH or downlink control information (DCI) (e.g., DCI corresponding to DCI format 0_0 related to retransmission of the Msg3 PUSCH).
In addition, the remaining bits (e.g., X bits) of the MCS field excluding the some bits above may be used to indicate the number of repetitions for the above-described repetition transmission of Msg3 PUSCH. As a specific example, the some bits (e.g., 4-X bits, 5-X bits) correspond to one or more least significant bits (LSBs) of the MCS field, and the remaining bits (e.g., X bits) may correspond to one or more most significant bits (MSBs) of the MCS field.
In step S830, the UE may transmit the Msg3 PUSCH based on the specific index value indicated by the MCS information. For example, the Msg3 PUSCH transmission may correspond to the above-described repetition transmission of Msg3 PUSCH.
In step S910, based on/according to the repetition transmission for Msg3 PUSCH being configured, the base station may transmit information on the MCS index group for Msg3 PUSCH to the UE. That is, the base station may transmit information on the MCS index group for repetition transmission of Msg3 PUSCH to the UE. Here, the MCS index group may include one or more MCS index values and may correspond to an MCS index subset in the above-described embodiments (e.g., Embodiments 1 to 4, especially Embodiment 2).
For example, the repetition transmission of the Msg3 PUSCH described above may be based on Type A-based PUSCH repetition transmission (e.g., PUSCH repetition Type A).
Additionally, one or more index values included in the MCS index group may include at least one of contiguous MCS index values or non-contiguous MCS index values. That is, the MCS index group may be composed of contiguous MCS index values and/or non-contiguous MCS index values. In this case, the one or more MCS index values may be assigned to codepoints of the MCS field (in increasing order) within the MCS index group.
Additionally, information on the MCS index group may be configured to the UE through system information (SI) (e.g., SIB, etc.) based on higher layer signaling (e.g., RRC signaling, etc.). Additionally, the corresponding MCS index group may be configured based on an MCS table applicable to the UE among one or more pre-defined MCS tables.
In step S920, the base station may transmit MCS information indicating a specific MCS index value among the one or more MCS index values to the UE. Here, the corresponding MCS information may be configured to some bits of the MCS field related to the above-described Msg3 PUSCH.
For example, as in the embodiments described above (e.g. Embodiments 1 to 4, especially Embodiment 2), the base station may indicate the UE the MCS value to be applied to Msg3 PUSCH transmission (e.g., Msg3 PUSCH repetition transmission) through some bits (e.g. 4-X bit, 5-X bit) of the MCS field included in the information scheduling Msg3 PUSCH. At this time, the size of the corresponding some bits may be related to the number of MCS indexes included in the above-described MCS index group. As an example, if the MCS index group includes a certain number (e.g., 2{circumflex over ( )}(4-X)) of MCS indexes, the MCS value may be indicated to the UE through the above-described some bits (e.g., 4-X bits, 5-X bits) of MCS field.
At this time, as in the above-described embodiments (e.g., Embodiments 1 to 4, especially Embodiment 2), the MCS field may be included in at least one of a RAR UL grant related to the Msg3 PUSCH or downlink control information (DCI) (e.g., DCI corresponding to DCI format 0_0 related to retransmission of the Msg3 PUSCH).
In addition, the remaining bits (e.g., X bits) of the MCS field excluding the some bits above may be used to indicate the number of repetitions for the above-described repetition transmission of Msg3 PUSCH. As a specific example, the some bits (e.g., 4-X bits, 5-X bits) correspond to one or more least significant bits (LSBs) of the MCS field, and the remaining bits (e.g., X bits) may correspond to one or more most significant bits (MSBs) of the MsCS field.
In step S930, the base station may receive the Msg3 PUSCH based on the specific index value indicated by the MCS information. For example, the Msg3 PUSCH transmission may correspond to the above-described repetition transmission of Msg3 PUSCH.
General Device to which the Present Disclosure May be Applied
In reference to
A first wireless device 100 may include one or more processors 102 and one or more memories 104 and may additionally include one or more transceivers 106 and/or one or more antennas 108. A processor 102 may control a memory 104 and/or a transceiver 106 and may be configured to implement description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure. For example, a processor 102 may transmit a wireless signal including first information/signal through a transceiver 106 after generating first information/signal by processing information in a memory 104. In addition, a processor 102 may receive a wireless signal including second information/signal through a transceiver 106 and then store information obtained by signal processing of second information/signal in a memory 104. A memory 104 may be connected to a processor 102 and may store a variety of information related to an operation of a processor 102. For example, a memory 104 may store a software code including commands for performing all or part of processes controlled by a processor 102 or for performing description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure. Here, a processor 102 and a memory 104 may be part of a communication modem/circuit/chip designed to implement a wireless communication technology (e.g., LTE, NR). A transceiver 106 may be connected to a processor 102 and may transmit and/or receive a wireless signal through one or more antennas 108. A transceiver 106 may include a transmitter and/or a receiver. A transceiver 106 may be used together with a RF (Radio Frequency) unit. In the present disclosure, a wireless device may mean a communication modem/circuit/chip.
A second wireless device 200 may include one or more processors 202 and one or more memories 204 and may additionally include one or more transceivers 206 and/or one or more antennas 208. A processor 202 may control a memory 204 and/or a transceiver 206 and may be configured to implement description, functions, procedures, proposals, methods and/or operation flows charts disclosed in the present disclosure. For example, a processor 202 may generate third information/signal by processing information in a memory 204, and then transmit a wireless signal including third information/signal through a transceiver 206. In addition, a processor 202 may receive a wireless signal including fourth information/signal through a transceiver 206, and then store information obtained by signal processing of fourth information/signal in a memory 204. A memory 204 may be connected to a processor 202 and may store a variety of information related to an operation of a processor 202. For example, a memory 204 may store a software code including commands for performing all or part of processes controlled by a processor 202 or for performing description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure. Here, a processor 202 and a memory 204 may be part of a communication modem/circuit/chip designed to implement a wireless communication technology (e.g., LTE, NR). A transceiver 206 may be connected to a processor 202 and may transmit and/or receive a wireless signal through one or more antennas 208. A transceiver 206 may include a transmitter and/or a receiver. A transceiver 206 may be used together with a RF unit. In the present disclosure, a wireless device may mean a communication modem/circuit/chip.
Hereinafter, a hardware element of a wireless device 100, 200 will be described in more detail. It is not limited thereto, but one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., a functional layer such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more PDUs (Protocol Data Unit) and/or one or more SDUs (Service Data Unit) according to description, functions, procedures, proposals, methods and/or operation flow charts included in the present disclosure. One or more processors 102, 202 may generate a message, control information, data or information according to description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure. One or more processors 102, 202 may generate a signal (e.g., a baseband signal) including a PDU, a SDU, a message, control information, data or information according to functions, procedures, proposals and/or methods disclosed in the present disclosure to provide it to one or more transceivers 106, 206. One or more processors 102, 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106, 206 and obtain a PDU, a SDU, a message, control information, data or information according to description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure.
One or more processors 102, 202 may be referred to as a controller, a micro controller, a micro processor or a micro computer. One or more processors 102, 202 may be implemented by a hardware, a firmware, a software, or their combination. In an example, one or more ASICs (Application Specific Integrated Circuit), one or more DSPs (Digital Signal Processor), one or more DSPDs (Digital Signal Processing Device), one or more PLDs (Programmable Logic Device) or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102, 202. Description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure may be implemented by using a firmware or a software and a firmware or a software may be implemented to include a module, a procedure, a function, etc. A firmware or a software configured to perform description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure may be included in one or more processors 102, 202 or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. Description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure may be implemented by using a firmware or a software in a form of a code, a command and/or a set of commands.
One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, a signal, a message, information, a program, a code, an instruction and/or a command in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, a flash memory, a hard drive, a register, a cash memory, a computer readable storage medium and/or their combination. One or more memories 104, 204 may be positioned inside and/or outside one or more processors 102, 202. In addition, one or more memories 104, 204 may be connected to one or more processors 102, 202 through a variety of technologies such as a wire or wireless connection.
One or more transceivers 106, 206 may transmit user data, control information, a wireless signal/channel, etc. mentioned in methods and/or operation flow charts, etc. of the present disclosure to one or more other devices. One or more transceivers 106, 206 may receiver user data, control information, a wireless signal/channel, etc. mentioned in description, functions, procedures, proposals, methods and/or operation flow charts, etc. disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 may be connected to one or more processors 102, 202 and may transmit and receive a wireless signal. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information or a wireless signal to one or more other devices. In addition, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information or a wireless signal from one or more other devices. In addition, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208 and one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, a wireless signal/channel, etc. mentioned in description, functions, procedures, proposals, methods and/or operation flow charts, etc. disclosed in the present disclosure through one or more antennas 108, 208. In the present disclosure, one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., an antenna port). One or more transceivers 106, 206 may convert a received wireless signal/channel, etc. into a baseband signal from a RF band signal to process received user data, control information, wireless signal/channel, etc. by using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, a wireless signal/channel, etc. which are processed by using one or more processors 102, 202 from a baseband signal to a RF band signal. Therefor, one or more transceivers 106, 206 may include an (analogue) oscillator and/or a filter.
Embodiments described above are that elements and features of the present disclosure are combined in a predetermined form. Each element or feature should be considered to be optional unless otherwise explicitly mentioned. Each element or feature may be implemented in a form that it is not combined with other element or feature. In addition, an embodiment of the present disclosure may include combining a part of elements and/or features. An order of operations described in embodiments of the present disclosure may be changed. Some elements or features of one embodiment may be included in other embodiment or may be substituted with a corresponding element or a feature of other embodiment. It is clear that an embodiment may include combining claims without an explicit dependency relationship in claims or may be included as a new claim by amendment after application.
It is clear to a person skilled in the pertinent art that the present disclosure may be implemented in other specific form in a scope not going beyond an essential feature of the present disclosure. Accordingly, the above-described detailed description should not be restrictively construed in every aspect and should be considered to be illustrative. A scope of the present disclosure should be determined by reasonable construction of an attached claim and all changes within an equivalent scope of the present disclosure are included in a scope of the present disclosure.
A scope of the present disclosure includes software or machine-executable commands (e.g., an operating system, an application, a firmware, a program, etc.) which execute an operation according to a method of various embodiments in a device or a computer and a non-transitory computer-readable medium that such a software or a command, etc. are stored and are executable in a device or a computer. A command which may be used to program a processing system performing a feature described in the present disclosure may be stored in a storage medium or a computer-readable storage medium and a feature described in the present disclosure may be implemented by using a computer program product including such a storage medium. A storage medium may include a high-speed random-access memory such as DRAM, SRAM, DDR RAM or other random-access solid state memory device, but it is not limited thereto, and it may include a nonvolatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices or other nonvolatile solid state storage devices. A memory optionally includes one or more storage devices positioned remotely from processor(s). A memory or alternatively, nonvolatile memory device(s) in a memory include a non-transitory computer-readable storage medium. A feature described in the present disclosure may be stored in any one of machine-readable mediums to control a hardware of a processing system and may be integrated into a software and/or a firmware which allows a processing system to interact with other mechanism utilizing a result from an embodiment of the present disclosure. Such a software or a firmware may include an application code, a device driver, an operating system and an execution environment/container, but it is not limited thereto.
Here, a wireless communication technology implemented in a wireless device 100, 200 of the present disclosure may include Narrowband Internet of Things for a low-power communication as well as LTE, NR and 6G. Here, for example, an NB-IoT technology may be an example of a LPWAN (Low Power Wide Area Network) technology, may be implemented in a standard of LTE Cat NB1 and/or LTE Cat NB2, etc. and is not limited to the above-described name. Additionally or alternatively, a wireless communication technology implemented in a wireless device 100, 200 of the present disclosure may perform a communication based on a LTE-M technology. Here, in an example, a LTE-M technology may be an example of a LPWAN technology and may be referred to a variety of names such as an eMTC (enhanced Machine Type Communication), etc. For example, an LTE-M technology may be implemented in at least any one of various standards including 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M and so on and it is not limited to the above-described name. Additionally or alternatively, a wireless communication technology implemented in a wireless device 100, 200 of the present disclosure may include at least any one of a ZigBee, a Bluetooth and a low power wide area network (LPWAN) considering a low-power communication and it is not limited to the above-described name. In an example, a ZigBee technology may generate PAN (personal area networks) related to a small/low-power digital communication based on a variety of standards such as IEEE 802.15.4, etc. and may be referred to as a variety of names.
A method proposed by the present disclosure is mainly described based on an example applied to 3GPP LTE/LTE-A, 5G system, but may be applied to various wireless communication systems other than the 3GPP LTE/LTE-A, 5G system.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2021-0131034 | Oct 2021 | KR | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2022/014722 | 9/30/2022 | WO |
