Method and apparatus for supporting multiple preconfigured resources in a wireless communication system

Abstract

The present invention may provide a method for a terminal to perform transmission in a wireless communication system. The method for performing transmission may include the following steps: the terminal receives a plurality of pre-configured resources; the device determines whether the plurality of pre-configured resources conflict; the terminal selects any one of the plurality of conflicting pre-configured resources; and performs transmission on the selected pre-configured resource.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for supporting authorization of multiple configurations in a wireless communication system, and more particularly to a method and apparatus for configuring authorization of multiple configurations by a user equipment (UE) supporting ultra-reliable and low-latency communication (URLLC) and industrial Internet of Things (IIoT). Background Art

[0002] The International Telecommunication Union (ITU) is developing the International Mobile Telecommunications (IMT) framework and standards, and more recently, discussions on 5th generation (5G) communications are underway through a process called "IMT for 2020 and beyond."

[0003] In order to meet the requirements required by "IMT for 2020 and beyond", discussions are underway to support various numerologies regarding time-frequency resource unit standards by considering various scenarios, service requirements, and potential system compatibility in the 3rd Generation Partnership Project (3GPP) New Radio (NR) system.

[0004] Detailed description

[0005] Technical Topics

[0006] The present disclosure may provide a method and apparatus for supporting authorization of multiple configurations.

[0007] The present disclosure may provide a method and apparatus for configuring authorization of multiple configurations by a user equipment (UE) supporting ultra-reliable and low-latency communication (URLLC) and industrial internet of things (IIoT).

[0008] The present disclosure may provide a method and apparatus for selecting, by a UE, a single configured grant and transmitting data if multiple configured grants conflict.

[0009] The present disclosure may provide a method and apparatus for retransmitting data whose transmission is omitted by a UE through an omitted configured grant in case of a conflict between multiple configured grants.

[0010] Technical Solution

[0011] According to an example of the present disclosure, a method for performing transmission by a user equipment (UE) in a wireless communication system may be provided. Here, the method for performing transmission may include: receiving a plurality of configured grants by the UE, wherein the receiving includes receiving a configured grant for at least one service configured in a single bandwidth part (BWP), the configured grant being configured for each service, and at least one configured grant being configured for the service; verifying by the UE whether a conflict occurs between the plurality of configured grants, wherein the verification includes verifying whether transmission time points for sending services overlap between the services; selecting a single configured grant from the conflicting plurality of configured grants by the UE, wherein the selecting the single configured grant includes a process of verifying the priority of the service according to a radio resource control (RRC) message received from the base station and a process of selecting the configured grant based on the verified priority, and also includes a process of selecting an initially configured grant based on a time order when transmission time points of services for the same service overlap; and using the selected configured grant to send services for the corresponding services.

[0012] In addition, according to an example of the present disclosure, in the process of receiving the configured authorization, the first BWP supports services A, B and C, the configured authorization is configured for each of services A, B and C, and at least one configured authorization is configured for each of services A, B and C, the second BWP supports services D and E, the configured authorization is configured for each of services D and E, and at least one configured authorization is configured for each of services D and E, and the reception of the configured authorization includes a process of activating, by the UE, the BWP indicated by the BWP indicator included in the physical direct control channel (PDCCH) received from the base station and deactivating the BWP not indicated between the first BWP and the second BWP.

[0013] Furthermore, according to an example of the present disclosure, services A, B, and C, and services D and E may indicate the same service.

[0014] In addition, according to an example of the present disclosure, receiving the configured authorization may include: using the configured authorization for each of services A, B and C of the activated first BWP to verify the transmission time point of the business for each of services A, B and C; and verifying whether the transmission time points of the business overlap between services A, B and C.

[0015] In addition, according to an example of the present disclosure, the method may also include a process of receiving an uplink grant from a base station using a configured scheduling radio network temporary identifier (CS-RNTI) for retransmission of a configured grant configured for the UE, and a process of using the received uplink grant to send traffic for a service corresponding to the discarded configured grant.

[0016] Here, according to an example of the present disclosure, a process of sending a service for a service may include a process of receiving allocation of a retransmission grant addressed to a CS-RNTI, and a process of verifying retransmission of the service for the corresponding service by verifying a Hybrid Automatic Request and Repeat (HARP) process identifier (ID) of the retransmission grant.

[0017] In addition, according to an example of the present disclosure, the method may also include a process of receiving an uplink grant from a base station using the C-RNTI, and a process of using the received uplink grant to send traffic for a service corresponding to the discarded configured grant.

[0018] The features briefly described above with respect to the present disclosure are merely example aspects of the detailed description that follows and do not limit the scope of the present disclosure.

[0019] Beneficial effects

[0020] According to the present disclosure, a method and apparatus for supporting authorization of multiple configurations may be provided.

[0021] According to the present disclosure, a method and apparatus for configuring a plurality of configured authorizations by a user equipment (UE) supporting ultra-reliable and low-latency communication (URLLC) and industrial internet of things (IIoT) may be provided.

[0022] According to the present disclosure, a method and apparatus for selecting, by a UE, a single configured grant and transmitting data if multiple configured grants conflict may be provided.

[0023] According to the present disclosure, a method and apparatus for retransmitting data whose transmission is omitted by a UE through an omitted configured grant in case of a conflict between multiple configured grants may be provided.

[0024] Effects achievable from the present disclosure are not limited to the above-described effects, and other effects not described herein may be clearly understood by those having ordinary skill in the art to which the present disclosure pertains from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 A wireless communication system according to the present disclosure is shown.

[0026] Figure 2 A bandwidth part (WP) configuration according to the present invention is shown.

[0027] Figure 3 A situation in which a conflict occurs between authorizations of multiple configurations according to the present disclosure is shown.

[0028] Figure 4An uplink transmission operation of a user equipment (UE) according to the present disclosure is shown.

[0029] Figure 5 An uplink transmission operation of a UE according to the present disclosure is shown.

[0030] Figure 6 The operation of the UE according to the present disclosure is shown.

[0031] Figure 7 The operation of the UE according to the present disclosure is shown.

[0032] Figure 8 The operation of the UE according to the present disclosure is shown.

[0033] Figure 9 is a flowchart illustrating the operation of a UE according to the present disclosure.

[0034] Figure 10 is a flowchart illustrating the operation of a UE according to the present disclosure.

[0035] Figure 11 is a flowchart illustrating the operation of a UE according to the present disclosure.

[0036] Figure 12 is a diagram showing the configuration of a base station device and a terminal device according to the present disclosure.

[0037] Best Mode for Carrying Out the Invention

[0038] According to an example of the present disclosure, a method for performing transmission by a user equipment (UE) in a wireless communication system may be provided. Here, the method for performing transmission may include: receiving a plurality of configured grants by the UE, wherein the receiving includes receiving a configured grant for at least one service configured in a single bandwidth part (BWP), the configured grant being configured for each service, and at least one configured grant being configured for the service; verifying by the UE whether a conflict occurs between the plurality of configured grants, wherein the verification includes verifying whether transmission time points for sending services overlap between the services; selecting by the UE a configured grant from the conflicting plurality of configured grants, wherein the selecting a single configured grant includes a process of verifying the priority of the service according to a radio resource control (RRC) message received from the base station and a process of selecting the configured grant based on the verified priority, and further includes a process of selecting an initially configured grant based on a time order when transmission time points of services for the same service overlap; and using the selected configured grant to send services for the corresponding services. DETAILED DESCRIPTION

[0039] Various examples of the present disclosure will be described more fully below with reference to the accompanying drawings so that those skilled in the art can easily implement these examples. However, the present disclosure can be implemented in various forms and is not limited to the examples described herein.

[0040] When describing an example, for the sake of clarity and conciseness, detailed description of known configurations or functions may be omitted. Throughout the drawings and detailed description, unless otherwise specified, the same drawing reference numerals are understood to refer to the same elements, features, and structures.

[0041] In this disclosure, it will be understood that when an element is referred to as being “connected to,” “coupled to,” or “accessed to” another element, it can be directly connected, coupled, or accessed to the other element, or intervening elements may be present. Furthermore, it will be understood that when an element is described as “including / comprising” or “having” another element, it specifies the presence of the further element, but does not preclude the presence of the further element described in other manners.

[0042] In this disclosure, terms such as first, second, etc. may be used herein to describe elements in the description herein. These terms are used to distinguish one element from another. Therefore, the terms do not limit elements, arrangement order, sequence, etc. Therefore, a first element in one example may be referred to as a second element in another example. Similarly, a second element in one example may be referred to as a first element in another example.

[0043] In this disclosure, differentiating elements are provided solely for the purpose of clearly explaining the various features and do not necessarily imply that the elements must be separated from one another. In other words, multiple elements can be integrated into a single hardware or software unit. Furthermore, a single element can be distributed across multiple hardware or software units. Therefore, unless otherwise specified, integrated or distributed examples are also included within the scope of this disclosure.

[0044] In the present disclosure, the elements described in the various examples may not necessarily be necessary and may be partially optional. Therefore, examples including a partial set of elements described in the examples are also included in the scope of the present disclosure. In addition, examples including another element other than the elements described in the various examples are also included in the scope of the present disclosure.

[0045] In addition, the description described herein relates to a wireless communication network, and the operations performed in the wireless communication network may be performed in the process of controlling the network and sending data in a system (e.g., a base station) that controls the wireless communication network, or may be performed in the process of sending or receiving signals in a user device connected to the wireless communication network.

[0046] Obviously, in a network including a base station and multiple network nodes, various operations performed for communicating with a terminal may be performed by the base station or other network nodes other than the base station. Here, the term "base station (BS)" may be used interchangeably with other terms, such as a fixed station, Node B, eNode B (eNB), and access point (AP). In addition, the term "terminal" may be used interchangeably with other terms, such as user equipment (UE), mobile station (MS), mobile subscriber station (MSS), subscriber station (SS), and non-AP station (non-AP STA).

[0047] In this disclosure, "sending or receiving a channel" includes the meaning of sending or receiving information or signals via the corresponding channel. For example, "sending a control channel" means sending control information or signals via the control channel. Similarly, "sending a data channel" means sending data information or signals via the data channel.

[0048] In the following description, although the term "New Radio (NR) system" is used to distinguish a system according to various examples of the present disclosure from an existing system, the scope of the present disclosure is not limited thereto.

[0049] For example, the new radio (NR) system supports various subcarrier spacings (SCS) by taking into account various scenarios, service requirements, potential system compatibility, etc. In addition, in order to overcome adverse channel environments such as high path loss, phase noise, and frequency offset that occur at high carrier frequencies, the NR system can support the transmission of physical signals / channels through multiple beams. In this way, the NR system can support applications such as enhanced mobile broadband (eMBB), massive machine type communication (mMTC) / super machine type communication (uMTC), and ultra-reliable and low-latency communication (URLLC). Here, the term "NR system" used here is used as an example of a wireless communication system, and the term "NR system" itself is not limited to the above-mentioned features.

[0050] In addition, for example, a fifth generation (5G) mobile communication technology can be defined. Here, 5G mobile communication technology can be defined by including the existing Long Term Evolution Advanced (LTE-A) system and the above-mentioned NR system. That is, 5G mobile communication technology can operate by considering backward compatibility with previous systems and the newly defined NR system.

[0051] For example, the sidelink field of 5G can include all of the sidelink technologies in the LTE system and the sidelink technologies in the NR system. Here, the sidelink field may be necessary to enhance performance and integrate various services through ultra-high reliability and ultra-low latency.

[0052] Figure 1 is a diagram illustrating a wireless communication system to which the present disclosure is applied.

[0053] Figure 1 The network structure shown in the figure may be a network structure of NG-RAN (Next Generation Radio Access Network) or Evolved Universal Mobile Telecommunications System (E-UMTS). NG-RAN or E-UMTS may include a Long Term Evolution (LTE) system, an LTE-A system, etc., or may include a 5G mobile communication network, a New Radio (NR), etc.

[0054] Reference Figure 1 In a wireless communication system 10, a base station (BS) 11 and a user equipment (UE) 12 can wirelessly transmit and receive data. Furthermore, the wireless communication system 10 can support device-to-device (D2D) communication between UEs. Furthermore, for example, the wireless communication system 10 can support vehicle-to-everything (V2X) communication. The following may include all concepts of terminal devices used by general users and terminal devices installed in vehicles, such as smartphones for the aforementioned UEs.

[0055] Furthermore, for example, the base station (BS) 11 in the wireless communication system 10 can provide communication services to UEs located within the coverage area of the BS 11 via a predetermined frequency band. The coverage area provided by the BS is also referred to as a site. The site may include various areas 15a, 15b, and 15c, which may be referred to as sectors. The sectors included in the site may be identified by different identifiers. Each sector 15a, 15b, and 15c may be interpreted as a portion of the area covered by the BS 11.

[0056] In addition, for example, BS 11 can generally refer to a station that communicates with UE 12, and can be called an evolved Node B (eNode B), a gNode B, an ng-eNB, a base transceiver system (BTS), an access point, a micro-micro node B, a home eNode B (HeNode B), a repeater, a remote radio head (RRH), a DU (distributed unit), etc.

[0057] UE 12 may be a fixed or mobile entity and may be referred to as a mobile station (MS), mobile terminal (MT), user terminal (UT), subscriber station (SS), wireless device, personal digital assistant (PDA), wireless modem, handheld device, etc.

[0058] In addition, based on the size of the coverage provided by the corresponding BS, the BS 11 may be referred to as a "macro cell," "macro cell," "micro cell," "pico cell," "femto cell," etc. Cell may be used as a term indicating a frequency band provided by a BS, coverage of a BS, or a BS.

[0059] Hereinafter, downlink (DL) indicates communication or a communication path from BS 11 to UE 12, and uplink (UL) indicates communication or a communication path from UE 12 to BS 11. In the downlink, the transmitter may be part of BS 11, and the receiver may be part of UE 12. In the uplink, the transmitter may be part of UE 12, and the receiver may be part of BS 11.

[0060] The multiple access scheme applied to the wireless communication system 10 is not limited to a specific scheme. For example, the wireless communication system can use various multiple access schemes such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier-FDMA (SC-FDMA), OFDM-FDMA, OFDM-TDMA, OFDM-CDMA, etc. Uplink transmission and downlink transmission can be performed based on a time division duplex (TDD) scheme in which transmission is performed at different times, or based on a frequency division duplex (FDD) scheme in which transmission is performed at different frequencies.

[0061] In addition, a TDD scheme in which transmission is performed at different times may be used for uplink transmission and downlink transmission. In addition, an FDD scheme in which transmission is performed at different frequencies may be used for uplink transmission and downlink transmission. In addition, a semi-FDD scheme in which uplink transmission and downlink transmission are performed at different frequencies and different times may be used.

[0062] Table 1 below shows abbreviations used in connection with the present disclosure. For example, the terms disclosed in Table 1 may be the same as the abbreviations used in LTE and LTE-A. Furthermore, for example, in Table 1 below, the term "gNB" may be used to distinguish it from an eNB, which is a base station for LTE. Here, the term "base station" may refer to at least one of the aforementioned gNB and eNB. Although the term "base station" is used below for clarity of description, the following base station may be either a gNB or an eNB. However, this is provided merely as an example.

[0063] [Table 1]

[0064]

[0065] Furthermore, NR numerology is described as an NR system. For example, NR numerology may indicate the numerical values of the basic elements or factors that generate a resource grid in the time-frequency domain for the design of an NR system. For example, in the numerology of 3GPP LTE / LTE-A systems, the subcarrier spacing may correspond to 15 kilohertz (kHz) (or 7.5 kHz in the case of a multicast broadcast single frequency network (MBSFN)) or an extended CP. Here, subcarrier spacing is merely a single example, and the term "numerology" is not limited to referring only to subcarrier spacing. The term "numerology" may include at least one of the cyclic prefix (CP) length associated with (or determined based on) the subcarrier spacing, the transmit time interval (TTI) length, the number of orthogonal frequency division multiplexing (OFDM) symbols within a desired time interval, and the duration of a single OFDM symbol. That is, different numerologies can be distinguished from one another based on the fact that at least one of the subcarrier spacing, CP length, TTI length, the number of OFDM symbols within a desired time interval, and the duration of a single OFDM symbol has different values.

[0066] Here, for example, the NR system considers multiple numerologies in consideration of various scenarios, various service requirements, compatibility with potential new systems, etc. In detail, since the current numerology of wireless communication systems may not easily support higher frequency bands, faster mobile speeds, and lower latency, it may be necessary to define new numerology.

[0067] For example, the NR system can support applications such as enhanced mobile broadband (eMBB) considering ultra-wideband, massive machine type communication / ultra-machine type communication (mMTC / uMTC) considering multiple low-power devices, and ultra-reliable and low-latency communication (URLLC) considering low latency. In particular, the user plane delay requirement for URLLC or eMBB services can be 0.5ms in the uplink and 4ms in all uplinks and downlinks, which can be a significant delay reduction requirement compared to the 10ms delay required in 3GPP LTE and LTE-A systems.

[0068] Various numerologies need to be supported to meet such various scenarios and requirements in a single NR system. Specifically, it may be necessary to support multiple subcarrier spacings (SCSs), which is different from the single SCS supported in existing LTE / LTE-A systems.

[0069] New numerology including NR systems that support multiple SCSs can be applied to solve the problem of unavailability of wide bandwidth in existing carriers or frequency ranges, such as 700 megahertz (MHz) or 2 gigahertz (GHz). For example, the SCS can be determined differently assuming that the wireless communication system operates in a carrier or frequency range of 6 GHz or above or 40 GHz or above. However, the scope of the present disclosure is not limited to this. That is, in the NR system, different SCSs can be configured based on the frequency domain used, without being limited to the above examples.

[0070] In addition, for example, to overcome adverse channel environments such as high path loss, phase noise, and frequency offset that occur at high carrier frequencies, NR systems consider transmitting synchronization signals, random access signals, and broadcast channels through multiple beams.

[0071] In addition, the NR system can consider carrier aggregation (CA). Carrier aggregation can indicate the aggregation and use of at least two component carriers (CCs) or cells to support a wide transmission bandwidth. Here, a single CC or multiple CCs can be used to send or receive data packets according to the capabilities of the UE. When carrier aggregation is configured for at least two cells, the at least two cells may include a primary cell (PCell) and at least one secondary cell (SCell).

[0072] Here, for example, in a hierarchical structure of a UE in which carrier aggregation is configured, the UE may have a single unit MAC entity.

[0073] At the same time, the NR system may consider a dual connectivity (DC) structure. Dual connectivity refers to an operation in which a UE can be connected to a primary base station and a secondary base station at the same time. A UE configured with dual connectivity may have a hierarchical structure of UEs with a hierarchical structure for the primary base station and a hierarchical structure of UEs with a hierarchical structure for the secondary base station.

[0074] For example, a UE in which dual connectivity is configured may have two MAC entities, such as a MAC entity for a master cell group (MCG) and a MAC entity for a secondary cell group (SCG), where the MCG is a service cell group associated with a primary base station and the SCG is a service cell group associated with a secondary base station.

[0075] Here, for example, when at least two cells are configured in an MCG, the at least two cells may include a PCell and an SCell. In addition, when at least two cells are configured in an SCG, the at least two cells may include a primary secondary cell (PSCell) and an SCell. Here, for example, the PCell of the MCG and the PSCell of the SCG may be collectively defined as a special cell (SpCell). That is, depending on whether the MAC entity is associated with the MCG or the SCG, the SpCell may represent the PCell of the MCG or the PSCell of the SCG. Below, based on the above description, SpCell is used for relevant description. As described above, it may represent the PCell of the MCG or the PSCell of the SCG.

[0076] In addition, the NR system considers bandwidth parts (hereinafter referred to as BWP). For example, when the UE performs signal transmission and reception, the frequency bandwidth to be used may not necessarily be as wide as the bandwidth of the serving cell. Here, as BWP, the bandwidth can be configured as a bandwidth narrower than the bandwidth of the serving cell. The frequency position of the bandwidth can be moved. In addition, the bandwidth of the OFDM subcarrier can be changed. It can be defined as a partial set of the entire frequency bandwidth of the service, which can be referred to as the BWP as the bandwidth part. However, it is provided only as an example, and the same can be applied if the bandwidth of the partial set is used.

[0077] In detail, Figure 2 The method of configuring BWP is shown. For example, referring to Figure 2 The serving cell may include one or more BWPs 210, 220, 230, 240, and 250. In the case of a BWP for a serving cell, information regarding multiple different BWPs can be configured in the UE via the base station. Each of the uplink and downlink BWPs can be configured. The BWP configuration information may include information regarding both uplink and downlink traffic. Furthermore, for example, the number of activated BWPs among the multiple BWPs may be limited to a single BWP. If the UE is capable of activating at least one BWP, the base station may verify the information regarding the maximum number of active BWPs and, based on the verified information, may simultaneously activate multiple BWPs. Furthermore, for example, if the UE is configured with a serving cell, a single BWP may be activated for the serving cell even without separate signaling from the base station. The UE may perform initial access to the serving cell and may use the activated BWP for initial access. Furthermore, the UE may use the initial BWP until it receives UE configuration information from the base station.

[0078] Furthermore, when the UE receives a UE configuration from the base station, it may be configured with a default BWP. Here, the default BWP may be configured with a relatively narrow bandwidth. If the amount of data to be transmitted and received is small, the UE may reduce its battery consumption by activating the default BWP. Furthermore, for example, unless the UE is configured with a default BWP, the UE may use an initial BWP for the same purpose. However, this is provided as an example only.

[0079] In addition, for example, the activated BWP of the serving cell can be changed to another BWP depending on the situation. This operation can be defined as BWP switching. When performing BWP switching, the UE can deactivate the currently active BWP and can activate a new BWP. Here, the above-mentioned BWP switching operation can be performed when the UE receives a BWP switching command from the base station via a physical downlink control channel (PDCCH) command. In addition, for example, the above-mentioned BWP switching operation can be performed through RRC configuration. In addition, for example, the above-mentioned BWP switching operation can be performed by a predetermined timer "BWp-Inactivity Timer" as a BWP inactivity timer. In addition, for example, the above-mentioned BWP switching operation can be performed in response to the start of random access. Below, the situation where the above-mentioned BWP switching occurs is described.

[0080] The base station can change the active BWP in the UE's serving cell according to the situation. If the UE expects to change the active BWP, the base station can notify the switching of the BWP through the PDCCH. Here, the UE can perform the BWP switching operation through the BWP switching related information included in the PDCCH.

[0081] In addition, for example, the UE may perform a BWP switching operation through the BWP switching related information included in the RRC message.

[0082] Furthermore, for example, the aforementioned "BWP Inactivity Timer" timer may be configured for each serving cell. Here, the "BWP Inactivity Timer" may be a timer for deactivating an active BWP, and is not limited to the aforementioned name. In other words, a timer that performs the same function may be the "BWP Inactivity Timer." Although the "BWP Inactivity Timer" is used below for clarity, this is provided merely as an example.

[0083] Here, if the above timer expires, the UE may deactivate the currently active BWP and activate the default BWP. That is, handover can be performed using the default BWP. Furthermore, for example, based on the above description, if the UE is not configured with a default BWP, the UE may switch to the initial BWP. Here, the UE can reduce battery consumption by monitoring the narrow bandwidth through the above handover operation. Furthermore, the start and restart conditions of the timer can be represented by Table 2 below. That is, if the UE needs to maintain the active BWP as follows, the timer can be started or restarted to prevent the active BWP from being deactivated.

[0084] [Table 2]

[0085]

[0086]

[0087] In addition, for example, refer to Figure 2 In the BWP, at least one of the size of the frequency bandwidth used in the frequency domain, the subcarrier spacing length, and the time length occupied in the time domain can be configured differently. Figure 2 In the embodiment, the frequency bandwidth size, subcarrier spacing length, and occupied time length of each of the BWPs 210, 220, 230, 240, and 250 may be configured differently based on the BWP configuration information. However, this is provided only as an example.

[0088] Furthermore, random access resources can be configured for each BWP of a serving cell. That is, the configuration of random access resources can be different for each BWP. Therefore, if a UE wishes to perform random access, it is possible to consider a situation where no random access resources are configured in the currently active BWP. Here, for example, the UE can autonomously switch to the initial BWP and initiate random access without a command from the base station. Specifically, as described above, since the initial BWP can be configured for initial access, random access resources can always be configured in the initial BWP. Therefore, if the UE verifies that no random access resources exist in the active BWP, it can switch to the initial BWP and perform a random access procedure without separate signaling.

[0089] As described above, the NR system can support services requiring low latency and high reliability, such as URLLC, by supporting various numerologies. Here, for example, use cases with high requirements can be considered as current low latency and high reliability services. For example, at least one use case in the entertainment industry, factory automation, transportation industry, and power distribution using augmented reality (AR) or virtual reality (VR) can be considered. Here, the above use cases can further improve the requirements for low latency and high reliability when providing services. Therefore, in the NR system, it may be necessary to define the operations of UEs and base stations whose goal is to further enhance URLLC. For example, the above definition may be referred to as NR Industrial Internet of Things (IIoT). However, it is provided only as an example. For clarity of description, the definition that meets the requirements for further enhancement in the NR system is referred to as IIoT hereinafter.

[0090] IIoT can support frequency range 1 and frequency range 2 based on the existing NR system. Moreover, IIoT meets the requirements for URLLC, which considers both TDD and FDD based on the existing NR system. For example, IIoT may require a design to meet the high reliability requirements of data replication and multi-connectivity enhanced services. For example, in the case of PDCP replication, the enhancement can be considered to generate up to four copies. Here, if the number of copies increases, resource usage may increase. Therefore, it is possible to consider enhancing the PDCP replication method to efficiently use resources. For example, PDCP replication can be selectively performed for each packet without being based on a radio bearer (RB). In addition, for example, a PDCP replication active / inactive method can be considered to be an enhancement. However, it is provided as an example only.

[0091] In addition, for example, UL / DL intra-UE prioritization / multiplexing can be considered. In detail, if DL / UL radio resources conflict between control and / or data services associated with different QoS requirements, the UE can resolve the above-mentioned radio resource conflict through intra-UE prioritization and multiplexing methods. For example, when priority is assigned to the downlink in the UE, a radio resource conflict may occur. In detail, the downlink in the UE can be prioritized. The UE can correspond to different DL allocations received in sequence. The radio resources used for the DL allocations can overlap in time. Here, the UE can receive DL services by prioritizing between the DL allocations. As another example, the case of prioritizing the uplink in the UE can be considered. Here, a conflict between a configured grant and a dynamically allocated grant may occur. The dynamically allocated grant received by the UE for uplink transmission may overlap in time with the configured grant for type 1 or type 2.

[0092] Here, the dynamically allocated grant of an existing UE may always have a higher priority than the configured grant. Here, NR IIoT may need to meet requirements by focusing on URLLC services, and therefore may need to operate in a manner different from existing operations. Therefore, if a conflict occurs between the configured grant and the dynamically allocated grant, the UE can perform UL service transmission using a single grant by prioritization. In addition, for example, the case of prioritizing the uplink in the UE can be considered. Here, a conflict may occur between the configured grants. For example, in IIoT, configured grants for different services and / or business types can be configured in a given BWP of the serving cell. For example, the configured grants can be configured to improve stability in IIoT and reduce latency in IIoT. Here, in the case of existing UEs, a single configured grant can be configured in a given BWP. Therefore, if multiple configured grants are configured in the BWP, the multiple configured grants can overlap on the timeline.

[0093] Specifically, a UE may simultaneously support services and / or service types for different requirements. A configured authorization may be configured for each service and / or service type. Therefore, depending on the corresponding service and / or service type, conflicts may occur between multiple configured authorizations.

[0094] As another example, a UE can configure multiple configured grants to support multiple periodic TSN flows. Here, the period and offset can be different for each flow. Therefore, the UE can configure the configured grant for each TSN flow. As described above, conflicts may occur between the configured grants.

[0095] As another example, multiple configured grants can be configured to support a single service such as TSN. Here, in TSN, the period of data packets can vary depending on the application. Moreover, in TSN, the period of data packets may not be a multiple of the time slot or symbol period. As described above, it may be necessary to configure multiple configured grants. In addition, if multiple configured grants are configured, conflicts may occur between the configured grants. As another example, if the uplink in the UE is prioritized, conflicts may occur between dynamically allocated grants. In detail, the UE may sequentially receive multiple dynamic approvals for uplink transmissions using temporally overlapping physical uplink shared channel (PUSCH) resources from the base station. Here, considering the above situation, the UE may need to handle the priority between multiple grants. For example, the situation where a conflict occurs between control information and control information can be considered as the situation where the uplink in the UE is prioritized. Here, the UE can simultaneously trigger the transmission of control information (e.g., SR, HARQ feedback, CSI) for services with high priority and the transmission of control information for services with low priority. Here, the UE may need to handle the priority between multiple grants.

[0096] Furthermore, for example, a case where the uplink in the UE is prioritized and a grant conflict occurs between control information and data can be considered. For example, the UE may simultaneously trigger the transmission of control information (e.g., SR, HARQ feedback, CSI) for high-priority traffic and the transmission of data for low-priority traffic. Here, the UE may need to handle the priorities between multiple grants.

[0097] Furthermore, for example, considering TSN-related enhancements, enhancements may be required to meet requirements. For example, TSN may refer to a technology that provides low-latency and low-packet-loss services based on Layer 2 Ethernet (L2). Here, TSN may refer to a technology that reduces the delay occurring between a UE and a base station by synchronizing time between components sharing network resources and processing traffic based on the synchronized time.

[0098] For example, TSN enhancements may be required in IIoT to support use cases such as motion control. Here, motion control may target 99.9999% or higher reliability and may target clock synchronization within 1 microsecond and latency within 0.5ms. However, this is provided as an example only and the present invention is not limited to the above example. Therefore, in order to meet these requirements, methods for forwarding precise reference timing may be required in NR IIoT. In addition, in order to meet these requirements, NR IIoT may require QoS / scheduling enhancements to meet low latency and high reliability requirements. In addition, NR IIoT may consider Ethernet header compression technology to reduce overhead in packet transmission. However, this is provided as an example only.

[0099] Hereinafter, an operation in the case where a conflict occurs between configured authorizations will be described based on the above description.

[0100] Here, as described above, in IIoT, the configured grant can be configured as a transmission grant in the UE to support URLLC services. Here, the configured grant can instruct the base station to pre-configure the transmission grant to be used by the UE in the UE. In detail, in order to meet service requirements requesting low latency and high reliability, the base station can pre-configure the configured grant in the UE. If there is data to be sent, the UE can perform data transmission through the configured grant without requesting an uplink grant from the base station. Here, two types of configured grants can exist in NR. For example, type 1 (configured grant type 1) can be configured through an RRC reconfiguration message. Here, type 1 can be configured for each BWP of each carrier. For example, although the UE is not currently using the BWP of the carrier currently configured with the configured grant type 1, the configured grant based on type 1 can be valid as the configured grant. Therefore, if the UE selects the BWP configured based on type 1 as the configured grant, the UE can perform data transmission by immediately using the grant without performing additional operations. That is, the UE can meet the low latency requirement of the service by sending data immediately using the configured grant at the moment of selecting the BWP of the carrier configured with the configured grant type 1.

[0101] As another example, the configured Grant Type 1 can be configured for URLLC data transmission purposes. For example, the configured Grant Type 1 of the UE can be configured for each logical channel. That is, the UE can use the configured grant to transmit data only for logical channels that can use the configured Grant Type 1. That is, as described above, whether the configured Grant Type 1 is available can be set for the logical channel.

[0102] As another example, the configured grant type 1 can be shared with another UE. As described above, the UE can repeatedly send the same data several times to increase the transmission probability even when a collision occurs. In addition, for example, if the UE uses the configured grant type 1 to send data, the UE can operate based on the configured grant timer (configuredgrantTimer). For example, the UE can wait for hybrid automatic repeat request (HARQ) feedback during the operation of the timer. Here, if the timer expires, the UE can discard the data stored in the HARQ buffer and can send another data. That is, the timer can operate based on the HARQ process.

[0103] In contrast, Type 2 (Configured Grant Type 2) may be a grant dynamically configured via the PDCCH. For example, Type 2 may be valid only within the BWP of the currently used carrier. That is, as described above, the UE can transmit data without delaying the transmission grant selection process based on configured grants of Type 1 and Type 2.

[0104] In addition, for example, the configured grant type 2 may be configured for the purpose of periodic data transmission. Here, the UE may use the configured grant type 2 to transmit data, and may be activated or deactivated through the PDCCH.

[0105] Here, since NR IIoT requires low latency and high reliability, all configured authorizations of Type 1 and Type 2 can be used, taking these requirements into consideration. Furthermore, multiple configured authorizations can be configured in a single BWP, for example, to support different services and / or a single service. This will be further described below.

[0106] Here, for example, as described above, NR IIoT can support multiple configured authorizations to meet the strict requirements of URLLC services. Here, if multiple configured authorizations are configured, a conflict may occur between the configured authorizations. Here, if a conflict occurs between the configured authorizations, the UE can select a specific configured authorization from the conflicting configured authorizations. In addition, the network configuration can be defined based on the conflict between the configured authorizations. Hereinafter, a method is described for performing transmission by selecting the most appropriate configured authorization in the event of a conflict between the configured authorizations. In addition, a method is described for ensuring the transmission of the UE to retransmit data discarded due to a conflict between the configured authorizations. Here, the following configuration can be extended to apply not only to the above-mentioned situation, but also to fields similar to the situation of authorization conflict, without being limited to the above-mentioned example.

[0107] As described above, if a conflict occurs between configured grants, the UE may select a specific grant from the conflicting configured grants and may perform transmission.

[0108] For example, the UE may perform transmissions using multiple configured grants to support different URLLC services and / or traffic types. As another example, in order to support a single service such as the aforementioned TSN, the UE may perform transmissions using multiple configured grants. Here, for example, in TSN, the period of a data packet may vary depending on the application. In addition, in TSN, the transmission period of a data packet may not be a multiple of a time slot or symbol period. For example, a data packet may be generated based on an application layer and therefore may not be a multiple of a time slot or symbol period. However, this is provided only as an example. Here, the UE may need to perform data transmission using multiple configured grants. For example, since the transmission period of a data packet is not a multiple of a time slot or symbol period for the same service, the UE may configure multiple configured grants and may perform transmissions.

[0109] Here, for example, in addition to the above-mentioned case, multiple configured authorizations may be configured in the UE. That is, the following description may relate to UE operation and network configuration considering a case where multiple configured authorizations are configured in the UE and the multiple configured authorizations conflict, and is not limited to a method for configuring multiple configured authorizations.

[0110] The base station may configure the configured grant in the UE. Specifically, the base station may configure multiple Type 1 (configured grant Type 1) grants in the UE through an RRC message (or an RRC reconfiguration message). Furthermore, for example, as described above, the base station may configure multiple Type 2 (configured grant Type 2) grants in the UE through the PDCCH. Furthermore, for example, the base station may configure all Type 1 and Type 2 grants in the UE through an RRC message (or an RRC reconfiguration message). However, this is provided only as an example.

[0111] Here, if the base station configures a Type 1 and / or Type 2 grant in the UE, the base station may configure the UE ID and CS-RNTI used for HARQ retransmissions in the UE. Here, for example, the base station may configure the parameters in Table 3 below for each configured grant. For example, the parameters in Table 3 below may include at least one of "Period" as periodicity information, "Time Domain Offset" as time domain offset information, "Time Domain Allocation" as time domain allocation information, and "nrofHARQ-Processes" as information regarding the number of HARQ processes. Specifically, "Period" may indicate the period of the configured grant. Here, for example, as described above, one period may be indicated for each configured grant. Furthermore, "Time Domain Offset" may indicate a resource offset with respect to "SFN (System Frame Number) = 0." Furthermore, "Time Domain Allocation" may be resource allocation information configured in the time domain. For example, "Time Domain Allocation" may include "start symbol and length." Furthermore, "nrofHARQ-Processes" may indicate a number of HARQ processes for the configured grant. Furthermore, for example, the base station may configure information in the UE other than the information in Table 3 below. However, this is provided as an example only.

[0112] [Table 3]

[0113]

[0114] Here, for example, the base station may not configure "time domain offset" and "time domain allocation" for type 2. Furthermore, for example, the CS-RNTI may be used for retransmissions for type 2. Furthermore, the CS-RNTI may be used to indicate the activity or inactivity of grants for type 2. Furthermore, for example, the base station may allocate grants such that a different HARQ process may be used for each configured grant.

[0115] Here, if the UE is configured with a grant type 1, the Nth configured grant may be configured in the UE according to the following equation 1. For example, if the UE is configured with a grant type 1, the UE may verify the symbol in which the Nth configured grant is configured. Here, for example, in the following equation 1, S represents the start symbol of the time slot. Furthermore, "period" may be the above-mentioned parameter. That is, the UE may verify the grant for type 1 among the grants configured by the base station according to the following equation 1. However, this is provided only as an example.

[0116] [Equation 1]

[0117] [(SFN × number of slots per frame × number of symbols per slot) + (number of slots in frame × number of symbols per slot) + number of slots in frame] = (time domain offset × number of symbols per slot + S + N × period) modulo (1024 × number of slots per frame × number of symbols per slot), all N>=0.

[0118] As another example, if a configured grant type 2 is configured in the UE, the UE may verify a symbol in which the configured grant is configured according to the following equation 2. That is, the UE may verify a grant for type 2 among the configured grants configured by the base station according to the following equation 2.

[0119] [Equation 2]

[0120] [(SFN × number of slots per frame × number of symbols per slot) + (number of slots in frame × number of symbols per slot) + number of slots in frame] = [(SFN start time × number of slots per frame × number of symbols per slot + slot start time × number of symbols per slot + symbol start time) + N × period] modulo(1024 × number of slots per frame × number of symbols per slot), all N>=0.

[0121] As another example, if the UE uses a configured grant, the UE may perform a HARQ process. Here, the HARQ process ID associated with the case where the UE uses the configured grant can be derived according to Equation 3 below. Here, for example, the "period" and "nrofHARQ processes" can be verified by the above parameters. However, this is provided only as an example.

[0122] [Equation 3]

[0123] HARQ process ID = [floor(current_symbol / cycle)] modulo norfHARQ-process

[0124] In addition, for example, in Equation 3, current_symbol / cycle can be derived according to Equation 4 below.

[0125] [Equation 4]

[0126] Current symbol = (SFN × number of slots per frame × number of symbols per slot + slot number in frame × number of symbols per slot + slot number in frame)

[0127] Here, the "number of slots per frame" and the "number of symbols per slot" may refer to the number of consecutive slots per frame and the number of consecutive symbols per slot, respectively. However, this is provided as an example only.

[0128] Here, according to the above operation, multiple configured authorizations can be configured in the UE. For example, as described above, multiple configured authorizations can be configured in the UE. Here, if a conflict occurs between the multiple configured authorizations configured in the UE, the UE can select a specific authorization from the multiple configured authorizations.

[0129] For details, refer to Figure 3, configured grant 1 (configured grant 1, CG1) and configured grant 2 (configured grant 2, CG2) may be configured in the UE. However, this is provided only as an example and is not limited to the above example.

[0130] Each configured grant configured in the UE may be sent at different time periods. Here, although each configured grant has a different time period, the PUSCH transmission intervals for each configured grant may partially overlap. For example, referring to Figure 3 , PUSCH transmissions regarding CG1 and CG2 configured in the UE may overlap at t0. That is, the grant 310 of CG1 and the grant 320 of CG2 overlap at time t0. Here, the UE needs to select a single grant from the grant 310 of CG1 and the grant 320 of CG2. That is, if multiple configured grants are configured in the UE, the UE may select a single configured grant from the multiple configured grants, and may perform transmission based on the selected configured grant.

[0131] Here, for example, multiple configured grants configured in the UE may be prioritized. For example, if a conflict occurs between multiple configured grants, the UE may select a configured grant with a high priority from the multiple configured grants and may perform transmission.

[0132] As another example, if a conflict occurs between multiple configured grants, the UE may select a grant that is earlier in time from among the multiple configured grants. That is, the UE may select a grant that is earlier in time regardless of priority and may perform transmission.

[0133] As another example, if a conflict occurs between configured authorizations, the UE may verify whether they relate to the same service. However, this is provided as an example only. For example, multiple configured authorizations may be configured in the UE to support different services. Here, a conflict may occur between multiple configured authorizations for supporting different services. Here, the UE may consider the priority of each service and select a configured authorization for a service with a higher priority.

[0134] As another example, the multiple configured authorizations may be configured to support a single service. Here, a conflict may occur between the multiple configured authorizations configured in the UE. Here, the UE may select an authorization that is configured earlier in time. That is, in the case of selecting a single configured authorization, the UE needs to determine whether the configured authorization is related to the same service or to different services. Here, if multiple configured authorizations are configured for the same service in the UE, the UE may select an authorization that is configured earlier in time. In addition, for example, if multiple configured authorizations are configured for different services in the UE, the UE may select an authorization that has a higher priority configuration from the configured authorizations.

[0135] The UE may need to internally exchange information about the occurrence or non-occurrence of conflicts between the configured grants and / or information about the priority for the aforementioned operations. In detail, the MAC entity of the UE may include an entity responsible for each role (e.g., a HARQ entity and a multiplexing and assembly entity) and may perform functions (e.g., uplink grant reception, LCP, MAC PDU configuration). Here, for example, referring to Figure 4, the MAC entity 410 of the UE can verify the received grant through the uplink grant reception function. Here, the MAC entity 410 of the UE can identify the HARQ information and HARQ process ID of the corresponding grant. Next, the MAC entity 410 of the UE can forward the information about the uplink grant and the HARQ information to the HARQ entity 420 of the UE. Here, the HARQ entity 420 of the UE can forward the information for obtaining the MAC PDU to the multiplexing and assembly entity 430 of the UE regarding the corresponding HARQ process ID through the received information. Here, the multiplexing and assembly entity 430 of the UE can perform LCP in order to perform data transmission through the above-mentioned grant. Here, the LCP can indicate the use of the grant to select a logical channel to send data. In addition, the multiplexing and assembly entity 430 of the UE can configure the MAC PDU by multiplexing the data (MAC SDU) received from the selected logical channel. Here, the HARQ entity 420 of the UE can store the MAC PDU in the corresponding process ID based on the HARQ information and the HARQ process ID of the received grant. Next, the UE can perform data transmission based on the HARQ information. That is, each entity of the UE can perform each corresponding function for data transmission. Here, for example, each entity of the UE may not know the information of another entity. Therefore, it may be necessary to exchange information required for processing between the various entities. For example, the uplink grant receiving entity can verify the available grant information. Here, the uplink grant receiving entity may not know the logical channel whose data will be sent through the corresponding grant. In addition, for example, the LCP can select the logical channel to be sent through the corresponding grant, but may not know the information about whether a conflict occurs between the grants and the subsequent available transmission time.

[0136] Here, if a conflict occurs between multiple configured grants configured in the UE, the service of each grant and the priority sorting of the service can be performed through the LCP process. Here, it is possible to verify whether a conflict occurs between multiple configured grants through the uplink grant reception function of the UE. In view of this, the UE needs to exchange information internally. In detail, the UE can verify whether a conflict occurs between multiple configured grants through the uplink grant reception function. Here, the UE may not verify the logical channel in which its data is sent in the corresponding grant. That is, the UE may not know the service corresponding to the logical channel data of the corresponding grant. Therefore, the UE may not compare the priorities between the configured grants, and may not verify which configured grant the UE needs to select.

[0137] Therefore, the UE may need to provide information about the occurrence of conflicts so that the LCP can select a single configured grant by comparing the service and priority. In addition, the LCP needs to provide priority information so that the HARQ entity can send a MAC PDU with a higher priority, which will be described below.

[0138] Here, for example, reference Figure 5 , the UE can perform uplink data transmission. For details, refer to Figure 5 (a), the UE can derive the HARQ process ID associated with the PUSCH transmission interval for each activated configured grant based on the above-mentioned Equation 3 and Equation 4. Here, for example, if the "configured grant timer" is not in the working state of the corresponding HARQ process, the UE can determine that the new data indicator (NDI) for the corresponding HARQ process has been switched. Here, the MAC entity 510 of the UE can forward the configured grant and related HARQ information to the HARQ entity 520 to send new data. Here, NDI can be a parameter value for indicating whether the packet is an initial transmission or a retransmission of the corresponding HARQ process. Here, if the NDI is switched, the UE can perform an initial transmission. On the contrary, unless the NDI is switched, the UE can perform a retransmission. Here, for example, if the "configured grant timer" is not working, the UE can no longer perform a retransmission. Therefore, the UE can determine that the NDI is switched and can perform a new transmission.

[0139] Here, the HARQ entity 520 may identify the HARQ process regarding the corresponding grant through the configured grant and the HARQ information received from the MAC entity 510. Here, the HARQ entity 520 may acquire the MAC PDU to be transmitted using the identified HARQ process from the multiplexing and assembling entity 530.

[0140] Here, for example, the multiplexing and assembly entity 530 may perform LCP. Subsequently, the multiplexing and assembly entity 530 may configure the MAC PDU based on the LCP. For example, LCP may be a process that selects appropriate logical channels based on the transmission grants allocated in the uplink grant and selects the amount of data to be transmitted for each selected logical channel. Therefore, if the UE performs a new transmission, the UE may select the data to be sent based on each transmission grant by performing LCP. Here, for example, to control the scheduling of uplink data, the base station may provide the UE with parameters regarding at least one of "priority," "priority bit rate," and "bucket size duration" for each logical channel. Here, the UE may perform configuration for each logical channel based on the parameters received from the base station. Here, for example, "priority" may indicate the priority of each logical channel. For example, a higher "priority" value indicates a lower priority. Furthermore, "priority bit rate (PBR)" may indicate the priority bit rate. Furthermore, "bucket size duration" may indicate the bucket size duration. Furthermore, for example, the base station may additionally configure parameters regarding mapping restrictions to each logical channel. Here, the above parameters may be at least one of "allowed SCS-list", "maximum PUSCH-duration", "allowed configured grant type 1" and "allowed serving cells". Here, the "allowed SCS-list" may indicate the subcarrier spacing in which transmission is allowed. In addition, the "maximum PUSCH duration" may indicate the maximum PUSCH duration allowed for transmission. Moreover, the "allowed serving cell" may indicate the cell in which transmission is allowed. In addition, subcarrier spacing information, PUSCH transmission duration information and cell information may be included in each uplink grant. Therefore, the UE may select a logical channel that meets the above conditions based on the transmission information of the uplink grant. At the same time, for example, "allowed configured grant type 1" may indicate whether the configured grant type 1 can be used to send data of the corresponding logical channel. That is, if the uplink grant is configured grant type 1, the UE may select only logical channels in which "allowed configured grant type 1" is set to "true".

[0141] Here, for example, as described above, a plurality of configured grants may be configured in the UE, and a conflict may occur between the plurality of configured grants. Here, if a conflict occurs between the configured grants, the MAC entity 510 may forward the conflict indication information to the HARQ entity 520. Next, the HARQ entity 520 may forward the information about the uplink grant and the conflict indication information to the multiplexing and assembly entity 530. That is, as described above, since each entity in the UE does not know the information about the functions performed by the other entities, it is necessary to forward the information related thereto. Here, even the MAC entity 510 of the UE may forward the corresponding information to notify the HARQ entity 520 of the information about the conflict. In addition, the HARQ entity 520 may send the corresponding information to the multiplexing and assembly entity 530 constituting the MAC PDU.

[0142] Here, if the same logical channel is selected for the configured grants during which collusion occurs, the UE can know that the corresponding conflict is related to the conflict between the configured grants for the same service. Here, for example, the UE can determine to select and use the grant that is earlier in time from the conflicting configured grants. That is, as described above, if multiple configured grants are configured for the same service and a conflict occurs between the configured grants, the UE can select and use the grant that is earlier in time from the conflicting configured grants. In this way, the UE can prevent delays from occurring for the same service. At the same time, for example, the UE can configure the MAC PDU for the configured grant that is earlier in time so that data can be sent through the corresponding grant. Conversely, the UE may not configure the MAC PDU for the configured grant that is not earlier in time.

[0143] As another example, refer to Figure 5 (b), if different logical channels are selected regarding the configured grants between which the conflict occurs, the UE can verify that the corresponding conflict is related to the conflict between the configured grants for different services. Here, the MAC entity 510 of the UE can forward the conflict indication information to the HARQ entity 520. Next, the HARQ entity 520 can forward the information about the uplink grant and the conflict indication information to the multiplexing and assembly entity 530. That is, as described above, since each entity in the UE does not know the information about the functions performed by other entities, it is necessary to forward information related thereto. Here, even the MAC entity 510 of the UE can forward the corresponding information to notify the HARQ entity 520 of the information about the conflict. In addition, the HARQ entity 520 can send the corresponding information to the multiplexing and assembly entity 530 that configures the MAC PDU.

[0144] As described above, the UE can compare the priorities of the logical channels for the corresponding grants through the LCP procedure. Here, the UE can select the logical channel with a higher priority and the grant configured for the logical channel, and can perform transmission. That is, the UE can configure the MAC PDU based on the logical channel with a higher priority and its configured grant.

[0145] For example, even when using a logical channel with a low priority and its configured grant, the UE may configure a MAC PDU. Here, when configuring a MAC PDU for each configured grant, the UE's multiplexing and assembly entity 530 may provide priority information about the MAC PDU to the UE's HARQ entity 520. Here, the HARQ entity 520 may receive the priority information and the MAC PDU and store it in a HARQ buffer. Here, the HARQ entity 520 may perform transmission for a MAC PDU with a higher priority.

[0146] Furthermore, for example, if grants conflicting between different logical channels are selected, the UE may determine to select and use a grant that is earlier in time from among the conflicting configured grants. That is, as described above, if multiple configured grants are configured for different services and a conflict occurs between the configured grants, the UE may select and use a grant that is earlier in time from among the conflicting configured grants. Thus, the UE may select and use a grant that is earlier in time for different services. However, this is provided only as an example. At the same time, for example, the UE may configure a MAC PDU for a grant that is earlier in time so that data can be transmitted using the corresponding grant. Conversely, the UE may not configure a MAC PDU for a grant that is not earlier in time. That is, if a conflict occurs between the configured grants, the UE may perform transmission using a grant that is earlier in time, regardless of whether the configured grants are related to the same service. However, this is provided only as an example.

[0147] At the same time, as described above, if a conflict occurs between the configured authorizations, the UE can select a single authorization, and the selected authorization can be used to perform transmission. Here, for example, if a conflict occurs between the configured authorizations configured for a single service, the base station may expect to select and use a single transmission authorization. Here, for example, if multiple configured authorizations are configured to support different services, all multiple configured authorizations can target the URLLC service. That is, as described above, as a case where multiple configured authorizations are configured to ensure low latency and high reliability, if a conflict occurs, the UE may need to guarantee data transmission of the discarded configured authorizations based on priority. For example, the base station can assign a retransmission authorization to the CS-RNTI of the UE to ensure transmission of data whose transmission was omitted. This will be further described below.

[0148] Figure 6 FIG. 4 shows the operation of the UE according to the present disclosure. Figure 6 , multiple configured grants may be configured in the UE. Here, the configured grants may be configured based on different periods. For example, if a conflict occurs between multiple configured grants, the UE may select a grant that is earlier in time from the configured grants and may perform transmission. Here, the UE may configure a MAC PDU for a grant that is earlier in time, and not configure a MAC PDU for a subsequent grant in which the conflict occurs. That is, referring to Figure 6, the grant 610 for the configured grant 1 (CG1) and the grant 620 for the configured grant 2 (CG2) may conflict at time t0. That is, a first conflict may occur between the multiple configured grants configured in the UE at time t0. Here, the UE may configure a MAC PDU for the CG1 that is earlier in time, and may store the MAC PDU in the corresponding HARQ process, without configuring a MAC PDU for the CG2 in which the collusion occurs. Similarly, for example, the grant 630 for CG1 and the grant 640 for CG2 may conflict at time t1. That is, a second conflict may occur between the multiple configured grants configured in the UE at time t1. Here, the UE may configure a MAC PDU for the CG2 that is earlier in time, and may store the MAC PDU in the corresponding HARQ process, without configuring a MAC PDU for the CG1 in which the collusion occurs. That is, the UE may configure a MAC PDU for the grant that is earlier in time, and may not configure a MAC PDU for the grant that is not earlier in time at each conflict time point. Here, for example, the above description may be applied to the case where multiple configuration grants are configured for the same service. For example, as described above, multiple grants may be configured for the same service to support periods of data packets that are not transmitted at multiple symbols and / or slot periods within the TSN. As described above, if the grants are configured for the same service, the base station can identify the point in time when conflicts between grants occur. Since the grants relate to the same service, the UE can select a single grant that is earlier in time and perform transmission, which can reduce packet transmission delay. Therefore, the UE can configure a MAC PDU for the earlier grant. For example, when configuring a MAC PDU, the UE can select an appropriate logical channel based on the transmission grant information through the LCP procedure. Based on the selected logical channels, transmission grants corresponding to the PBR values set for the logical channels can be allocated to the corresponding logical channels, starting with the logical channel with the highest priority. If any grants remain, the UE can allocate grants to the corresponding logical channels based on the priority of the selected logical channels until all uplink grants or data for the corresponding logical channels are consumed. The UE can configure a MAC SDU based on the allocated grants so that available data can be transmitted to each logical channel. Next, the UE can configure a single MAC PDU by multiplexing the MAC SDUs configured from various logical channels. As described above, if the UE configures a MAC PDU, the UE's HARQ entity can store the MAC PDU, uplink grant, and HARQ information in the corresponding HARQ process. Next, the UE's HARQ entity can indicate the identified HARQ process to trigger a new transmission.Here, if the uplink grant is a configured grant and the UE performs transmission for the HARQ process, a "configured grant timer" may be started or restarted. The UE may expect to retransmit the MAC PDU stored in the corresponding HARQ during the operation of the "configured grant timer." Conversely, the HARQ entity may determine that there is no data to be transmitted for a grant for which a MAC PDU was not obtained, and may not perform transmission. That is, during. Figure 6 In the example, the UE may select CG1 that is earlier in time at the first of the two conflicts. On the contrary, in the second conflict, the UE may select CG2 that is earlier in time and may perform transmission. However, this is provided only as an example.

[0149] Furthermore, for example, although the description is based on a case where multiple configured grants are configured for the same service, the multiple configured grants may be configured for different services. In this case, the UE may perform transmission using the grant that was configured earlier in time. However, this is provided as an example only.

[0150] also, Figure 7 The operation of the UE according to the present disclosure is shown. Figure 7, multiple configured grants may be configured in the UE. Here, a conflict may occur between the multiple configured grants configured in the UE. Here, the UE may determine the priority of the multiple configured grants based on the above description. That is, among the multiple configured grants, a specific configured grant may have a high priority. Here, as described above, the UE may configure a MAC PDU for the configured grant with a high priority and may perform transmission. At the same time, for example, as described above, the UE may configure a MAC PDU for the configured grant whose transmission is omitted. For example, the UE's HARQ entity may send a MAC PDU corresponding to a high priority based on the priority information provided by the LCP. Conversely, the UE's HARQ entity may not send a MAC PDU corresponding to a low priority. Here, even for the MAC PDU whose transmission is omitted, the UE may expect to perform transmission using a retransmission grant addressed to the CS-RNTI. For example, the UE may retransmit the MAC PDU whose transmission is omitted using the grant addressed to the CS-RNTI described above. Therefore, the UE may need to start a "configured grant timer" for the MAC PDU whose transmission is omitted. That is, even though the UE does not perform a transmission, it can expect to receive a retransmission grant by starting the "Configured Grant Timer" during the transmission interval of the corresponding grant. In response to receiving the retransmission grant, the UE can immediately transmit the configured MAC PDU. Specifically, as described above, if the "Configured Grant Timer" is not in an operating state for the corresponding HARQ process, the UE can determine that the NDI of the corresponding HARQ process has been switched and can transmit new data. Alternatively, if the "Configured Grant Timer" is not in an operating state for the corresponding HARQ process, the UE can ignore uplink grants received using the CS-RNTI. The UE can receive a grant for retransmission and perform a retransmission only when the "Configured Grant Timer" is operating. Therefore, if the "Configured Grant Timer" is not operating, the UE can ignore uplink grants received using the corresponding CS-RNTI and may not perform a transmission. That is, if the "Configured Grant Timer" is not in an operating state, the UE may no longer perform a retransmission. Considering the above aspects, the UE can start the "Configured Grant Timer" to retransmit the MAC PDU whose transmission was omitted. Here, if the UE receives a retransmission grant using the CS-RNTI, the UE can immediately perform transmission without performing additional processing for configuring the MAC PDU, which is advantageous in reducing delay. Here, for example, in association with the above-mentioned operation, multiple configured grants may relate to different services. That is, for different services, the UE may need to consider URLLC to perform retransmission for the corresponding service, which is different from the case where multiple configured grants relate to the same service.If, taking the above aspects into account, multiple configured grants are related to different services, the UE may configure the MAC PDU and may start the "Configured Grant Timer" although the transmission is omitted.

[0151] Furthermore, for example, since retransmission can be performed even for the same service, the UE can configure the MAC PDU and can start a "configured grant timer", although transmission is omitted, but is not limited to the above example.

[0152] As another example, the UE may configure MAC PDUs only for logical channels (LCHs) and grants with high priority. Here, for example, the HARQ entity may perform MAC PDU transmission only for the HARQ process for which the MAC PDU was acquired.

[0153] Here, for example, if multiple configured grants are configured to support different services, the discarded configured grant may also target the URLLC service. Therefore, even for data that is not sent due to priority, the UE may need to guarantee transmission. Here, for example, in order to guarantee transmission of data whose transmission is omitted, the base station may allocate a transmission grant to the UE's C-RNTI. However, this is provided only as an example.

[0154] For example, see Figure 7 , at time t0, a conflict may occur between the grant 710 for the configured grant 1 (CG1) and the grant 720 for the configured grant 2 (CG2). Here, for example, the priority of CG1 may be higher than the priority of CG2. Therefore, the UE may configure a MAC PDU for CG1 and may perform transmission at time t0. At the same time, the UE may configure a MAC PDU for CG2. That is, the UE may configure a MAC PDU for CG2 whose transmission is omitted. Moreover, the UE may start a "configured grant timer" for the MAC PDU for CG2. Next, the UE may receive an allocation of a grant 730 for retransmission from the base station based on the CS-RNTI. Here, the UE may perform the MAC PDU for CG2 with the grant 730 allocated for retransmission. However, this is provided only as an example.

[0155] In addition, for example, reference Figure 8, multiple configured grants may be configured in the UE. As described above, the UE may verify the configured grant with a high priority. Here, the UE may configure the MAC PDU only for the configured grant with a high priority, and may perform transmission. That is, the UE may not configure the MAC PDU for the grant whose transmission is omitted as a configured grant with a low priority. Here, the HARQ entity may perform MAC PDU transmission only for the HARQ process for which the MAC PDU is acquired. Here, for example, the UE may use an uplink grant addressed to the C-RNTI to send data whose transmission is omitted and thus discarded. In detail, the UE may expect to use an uplink grant addressed to the C-RNTI to send data whose transmission is omitted and discarded. Here, as described above, the UE may store the configured MAC PDU in the corresponding HARQ process through the LCP and MAC PDU configuration process for the uplink grant addressed to the C-RNTI, and may then perform transmission. Therefore, with Figure 7 Unlike the example of , in the case of performing retransmission for a grant whose transmission is omitted, the UE may perform an additional process and then perform transmission. Therefore, the transmission may be delayed. Here, for example, the UE may need to transmit additionally generated data at the time point when the UE transmits data for the configured grant whose transmission is omitted. Therefore, unlike Figure 7 Unlike the example of , the UE may not configure a MAC PDU for the configured grant whose transmission is omitted at the conflicting time point. Next, as described above, the UE may store the configured MAC PDU in the corresponding HARQ process through the LCP and MAC PDU configuration procedures and then perform transmission. However, this is provided only as an example.

[0156] As another example, if the UE performs transmission using a dynamically allocated uplink grant through the PDCCH, the parameter "configuredgrantAllowed" may not be applied. That is, if the UE performs retransmission for a grant whose transmission is omitted, the UE may even send data other than URLLC data. That is, based on the above situation, if the UE performs retransmission for data whose transmission is omitted, additional restrictions may be configured in the UE to ensure URLLC data transmission. For example, a case where the UE receives an uplink grant addressed to the C-RNTI may be considered to be a case where a conflict occurs between the configured grants. Here, if the HARQ process ID of the corresponding uplink grant is the same as the HARQ process ID of the data whose transmission is omitted, the UE may configure the MAC PDU for the data whose transmission is omitted and discarded as described above, and may give priority to sending the discarded data. Here, for example, as described above, the base station may allocate an additional grant so that the UE may perform retransmission for the grant whose transmission is omitted, thereby ensuring URLLC data transmission. Therefore, the UE may perform retransmission for the grant whose transmission is omitted for the grant allocated from the base station.

[0157] At the same time, for example, in association with the above-mentioned operation, a case where a conflict occurs between configured grants can be applied to a case where multiple configured grants for different services are configured in the UE. That is, for different services, it is necessary to consider the transmission of URLLC data transmission to ensure the transmission of the grant whose transmission is omitted. Therefore, as described above, the UE can configure a MAC PDU for the grant whose transmission is omitted and can perform transmission. However, this is provided only as an example.

[0158] For example, see Figure 8 , the UE may perform transmission through the configured grant 1 (CG1) and the configured grant 2 (CG2). Here, if a conflict occurs between the grant 810 for CG1 and the grant 820 for CG2, the UE may configure the MAC PDU for the configured grant with a higher priority and perform transmission. For example, in Figure 8In, the UE may perform transmission by selecting the grant 810 for CG1 and by configuring the MAC PDU for the selected grant 810. Here, the UE may not select the grant 820 for CG2 having a low priority and may not configure the MAC PDU for CG2. Next, the UE may configure the MAC PDU for CG2 with the additional grant 830 and may perform transmission. Here, for example, as described above, the UE may expect to perform transmission using the uplink grant 830 addressed to the C-RNTI. Here, as described above, the UE may configure the MAC PDU only for the LCH and the grant having a high priority with respect to the uplink grant 830 addressed to the C-RNTI. As another example, in order to guarantee URLLC data transmission, if the HARQ process ID of the corresponding uplink grant 830 is the same as the HARQ process ID whose transmission is omitted, the UE may configure the MAC PDU for the data whose transmission is omitted and may perform transmission through the corresponding uplink grant 830, as described above. Here, in Figure 8 In the embodiment, the HARQ process ID of the omitted transmission may be HARQ process #2, and the HARQ process ID for the uplink grant 830 newly allocated to the UE may also be HARQ process #2. That is, as described above, since the HARQ process ID of the corresponding uplink grant 830 is the same as the HARQ process ID of the omitted transmission, the UE can perform retransmission for the grant whose transmission is omitted through the corresponding uplink grant 830.

[0159] Figure 9 is a flow chart illustrating the operation of a UE according to the present disclosure. For example, in operation S910, multiple configuration authorizations may be configured in the UE. Here, as mentioned above, Figures 1 to 8 As described above, in operation S920, the UE may verify whether a conflict occurs between the configured grants. Here, if a conflict occurs between multiple configured grants, in operation S930, the UE may perform an LCH comparison between the configured grants. In detail, as described above, the UE may perform an LCP procedure to verify whether multiple configured grants are configured for the same service. Here, in operation S940, if multiple configured grants involve the same LCH, the UE may verify that the multiple configured grants are configured for the same service. Here, as described above, Figures 1 to 8As described above, in operation S950, the UE may select a grant that is earlier in time from among the conflicting multiple configured grants and may configure a MAC PDU. Here, as described above, the UE may not configure a MAC PDU for the configured grant whose transmission is omitted. In operation S960, the UE may transmit the configured MAC PDU as described above. At the same time, for example, as described above, unless a conflict occurs between multiple configured grants, in operation S970 the UE may configure a MAC PDU for the corresponding configured grant and may transmit the MAC PDU.

[0160] In addition, for example, Figure 10 1 is a flow chart illustrating a method for operating a UE in the event of a conflict between multiple configured authorizations according to the present disclosure. For example, in operation S1010, multiple configured authorizations may be configured in the UE. Here, as described above with reference to Figures 1 to 8 As described above, in operation S1020, the UE may verify whether a conflict occurs between the configured authorizations. Here, if a conflict occurs between multiple configured authorizations, in operation S1030, the UE may perform an LCH comparison between the configured authorizations. In detail, as described above, the UE may perform an LCP procedure to verify whether the multiple configured authorizations are configured for the same service. Here, in operation S1040, if the multiple configured authorizations involve different LCHs, the UE may verify that the multiple configured authorizations are configured for different services. Here, as described above, Figures 1 to 8 As described above, in operation S1050, the UE may compare the LCH priorities between the conflicting multiple configured grants. In operation S1060, the UE may select a grant with a higher LCH priority and may configure a MAC PDU for the selected grant. Next, in operation S1070, the UE may transmit the configured MAC PDU. At the same time, for example, the UE may configure a MAC PDU for the configured grant whose transmission is omitted. For example, as described above, the UE may request a retransmission grant by starting a "configured grant timer" without transmitting the configured MAC PDU. Here, the UE performs transmission for the configured grant whose transmission is omitted using a grant allocated from the base station based on the CS-RNTI. Here, as described above, since the MAC PDU is configured, the UE may immediately transmit the MAC PDU for the configured grant whose transmission is omitted, thereby preventing delays. At the same time, for example, as described above, unless a conflict occurs between the multiple configured grants, in operation S1080, the UE may configure a MAC PDU for the corresponding configured grant and may transmit the MAC PDU.

[0161] In addition, for example, Figure 111 is a flow chart illustrating a method for operating a UE in the event of a conflict between multiple configured authorizations according to the present disclosure. For example, in operation S1110, multiple configured authorizations may be configured in the UE. Here, as described above with reference to Figures 1 to 8As described above, in operation S1120, the UE may verify whether a conflict occurs between the configured grants. Here, if a conflict occurs between multiple configured grants, in operation S1130, the UE may perform an LCH comparison between the configured grants. In detail, as described above, the UE may perform an LCP procedure to verify whether the multiple configured grants are configured for the same service. That is, in operation S1140, the UE may verify whether the multiple configured grants relate to the same LCH. Here, if the multiple configured grants relate to the same LCH, in operation S1150, the UE may select a chronologically earlier configured grant and may configure a MAC PDU for the selected configured grant. Next, the UE may transmit the configured MAC PDU as described above. That is, if the multiple configured grants are configured for the same service, the UE may configure a MAC PDU for the chronologically earlier configured grant and may perform transmission. Conversely, in operation S1180, if the logical channel selected through the LCP procedure is different for each of the conflicting grants, the UE may verify that the configured grants relate to different services. Here, in operation S1180, the UE may select a single grant to perform transmission by comparing priorities between logical channels. For example, in operation S1180, the UE may configure a MAC PDU for a grant whose transmission is determined based on priority, and may store the configured MAC PDU in the corresponding HARQ process. In addition, although the UE may configure a MAC PDU based on priority or even for a grant whose transmission is omitted, and may store the configured MAC PDU in the corresponding HARQ process, in operation S1190, the UE may expect to retransmit the grant by starting a "configured grant timer" without performing transmission, as described above. Here, if the UE receives an uplink grant addressed to the CS-RNTI, the UE may immediately send the MAC PDU, thereby satisfying the requirement for URLLC data not to be sent due to priority. Alternatively, the UE may not configure a MAC PDU for a grant whose transmission is omitted based on priority, and may perform transmission in operation S1190 by an additional uplink grant addressed to the C-RNTI, as described above. Here, as described above, in order to transmit the discarded data through the grant, if the HARQ process ID of the corresponding uplink grant is the same as the HARQ process ID of the grant whose transmission the UE omitted, then in operation S1160, the UE can configure and transmit the MAC PDU as data for the corresponding logical channel with the purpose of transmitting the data whose transmission was omitted and discarded. That is, if a conflict occurs between the configured grants configured for different services, the UE can support the transmission of all packets, thereby satisfying the requirements of the URLLC data.On the contrary, unless a conflict occurs between the configured grants, in operation S1170, the UE may configure a MAC PDU for the corresponding grant and may perform transmission as described above.

[0162] Figure 12 is a diagram illustrating a device configuration according to the present disclosure.

[0163] The base station device 1200 may include a processor 1220 , an antenna device 1212 , a transceiver 1214 , and a memory 1216 .

[0164] The processor 1220 may perform baseband-related signal processing and may include upper layer processing 1230 and physical (PHY) layer processing 1240. The upper layer processing 1230 may handle the operation of the PHY layer (e.g., uplink receive signal processing and downlink transmit signal processing). In addition to performing baseband-related signal processing, the processor 1220 may also control the overall operation of the base station device 1200.

[0165] Antenna device 1212 may include at least one physical antenna. If antenna device 1212 includes multiple antennas, multiple-input multiple-output (MIMO) transmission and reception may be supported. Transceiver 1214 may include a radio frequency (RF) transmitter and an RF receiver. Memory 1216 may store operational processing information for processor 1220, software associated with the operation of base station device 1200, an operating system (OS), applications, and the like, and may include components such as a buffer.

[0166] The processor 1220 of the base station 1200 may be configured to implement the operations of the base station in the examples described herein.

[0167] The terminal device 1250 may include a processor 1270, an antenna device 1262, a transceiver 1264, and a memory 1266. Meanwhile, for example, communication between terminal devices may be performed here based on uplink / downlink communication. That is, the terminal device 1250 performing uplink / downlink communication in this specification may be either the base station device 1200 or a device communicating with the terminal device 1250. However, this is provided merely as an example.

[0168] Processor 1270 may perform baseband-related signal processing and may include upper layer processing 1280 and PHY layer processing 1290. Upper layer processing 1280 may process operations of the MAC layer, RRC layer, or more upper layers. PHY layer processing 1290 may process operations of the PHY layer (e.g., downlink receive signal processing and uplink transmit signal processing). In addition to performing baseband-related signal processing, processor 1270 may also control the overall operation of terminal device 1250.

[0169] Antenna device 1262 may include at least one physical antenna. If antenna device 1262 includes multiple antennas, MIMO transmission and reception may be supported. Transceiver 1264 may include an RF transmitter and an RF receiver. Memory 1266 may store operational processing information for processor 1270 and software, an operating system, applications, and the like associated with the operation of terminal device 1250, and may include components such as a buffer.

[0170] The processor 1270 of the terminal device 1250 may be configured to implement the operations of the terminal in the examples described herein.

[0171] In addition, for example, as described above, the processor 1220 of the base station 1200 may configure the configured grant in the terminal device 1250. Here, as described above, the configured grant may be configured in the terminal based on type 1 or type 2.

[0172] For example, the processor 1220 of the base station 1200 may configure the type 1 configured grant in the terminal through an RRC message (or an RRC reconfiguration message). In addition, the processor 1220 of the base station 1200 may provide parameter information about the configured grant to the terminal. Here, the processor 1270 of the terminal device 1250 may perform data transmission through the configured grant based on the parameter information.

[0173] In addition, for example, the processor 1220 of the base station 1200 may dynamically configure the grant of configuration of type 2 in the terminal through the PDCCH. Here, as described above, the processor 1270 of the terminal device 1250 may perform data transmission through the configured grant.

[0174] In addition, for example, as described above, the processor 1270 of the terminal device 1250 can verify whether a conflict occurs between multiple configured authorizations. For example, the upper layer processing 1280 of the terminal device 1250 can confirm whether a conflict occurs between multiple configured authorizations. Here, the processor 1270 of the terminal device 1250 can compare the logical channels for the multiple configured authorizations. As described above, the processor 1270 of the terminal device 1250 can verify whether the multiple configured authorizations involve the same service. Here, as described above, with respect to authorizations configured for the same service, the processor 1270 of the terminal device 1250 can configure a MAC PDU for an authorization configured earlier in time, and can perform transmission. In addition, for example, as described above, with respect to authorizations configured for different services, the processor 1270 of the terminal device 1250 can configure a MAC PDU for the configured authorizations based on priority, and can perform transmission.

[0175] The various examples herein are for explaining representative aspects of the present disclosure rather than describing all possible combinations, and matters described in the various examples may be applied independently or by a combination of at least two thereof.

[0176] In addition, various examples of the present disclosure may be implemented by hardware, firmware, software, or a combination thereof. In the case of hardware implementation, the examples may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), general purpose processors, controllers, microcontrollers, microprocessors, and the like.

[0177] The scope of the present disclosure includes software or machine-executable instructions (e.g., OS, applications, firmware, programs, etc.) that enable the operations of various example methods to be performed on a device or computer, as well as non-transitory computer-readable media that store such software or instructions for execution on a device or computer.

[0178] Industrial Applicability

[0179] The present disclosure is applicable when a user equipment (UE) supporting ultra-reliable and low-latency communication (URLLC) and industrial internet of things (IIoT) configures authorization for multiple configurations in a wireless communication system.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: receiving, by the UE, a plurality of configured grants, wherein the receiving comprises receiving a configured grant for at least one service configured in a single bandwidth part (BWP); Determining, by the UE, whether a conflict occurs between the multiple configured grants, wherein the determining comprises determining whether transmission points used for sending traffic overlap in time; selecting, by the UE, a first configured grant from a plurality of overlapping configured grants, wherein the selection of the first configured grant is based on a priority for a logical channel corresponding to the first configured grant, and wherein the priority is indicated by a radio resource control (RRC) message received from a base station; sending traffic associated with the logical channel using the first configured grant; and receiving an indication of uplink resources from the base station using a configured scheduling radio network temporary identifier (CS-RNTI) for retransmission of a second configured grant configured for the UE; and sending traffic for a service corresponding to the discarded configured grant using the uplink resources, The method also includes: for the sending of the service for the service: receiving an allocation of a retransmission grant addressed to the CS-RNTI; and determining the retransmission of the service for the corresponding service by verifying the hybrid automatic repeat request HARQ process identifier ID of the retransmission grant.

2. The method according to claim 1, wherein The first BWP supports services A, B, and C; The plurality of configured authorizations are associated with the services A, B, and C; as well as At least one configured authorization of the plurality of configured authorizations is configured for each of the services A, B, and C.

3. The method according to claim 2, wherein: The second BWP supports services D and E; The plurality of configured authorizations are associated with the services D and E; and At least one configured authorization of the plurality of configured authorizations is configured for each of the services D and E.

4. The method according to claim 3, further comprising: activating, by the UE, one of the first BWP or the second BWP indicated by a BWP indicator, the BWP indicator being included in a physical direct control channel (PDCCH) received from the base station; as well as The other of the first BWP or the second BWP not indicated by the BWP indicator is deactivated.

5. The method according to claim 2, further comprising: determining a transmission point in time for traffic for each of the services A, B, and C using the configured grants in the services A, B, and C for the first BWP, respectively; and Determine whether the transmission points of traffic between the services A, B, and C overlap in time.

6. The method according to claim 1, further comprising: receiving an indication of uplink resources from the base station using a cell radio network temporary identifier (C-RNTI); as well as Traffic for the service corresponding to the discarded configured grant is sent using the uplink resources.

7. A method comprising: Receiving, by a wireless user device, a plurality of configured authorizations associated with a bandwidth portion BWP; Determining, by the wireless user equipment, whether a conflict occurs between the plurality of configured grants, wherein the determining comprises determining whether transmission points used for transmitting traffic overlap in time; selecting, by the wireless user equipment, a first configured grant from among the overlapping configured grants based on overlapping configured grants among the plurality of configured grants, wherein the selection of the first configured grant is based on a priority associated with the first configured grant, and wherein the priority is indicated by a radio resource control (RRC) message received from a base station; and Based on the first configured grant, the wireless user equipment transmits an uplink signal associated with the first configured grant, The method further includes: receiving an indication of uplink resources from the base station using a configured scheduling radio network temporary identifier (CS-RNTI) for retransmission of a second configured grant configured for the wireless user equipment; and transmitting an uplink signal associated with the discarded configured grant using the uplink resources, The method further includes: receiving an allocation of a retransmission grant addressed to the CS-RNTI; and Retransmission of the uplink signal is performed based on a hybrid automatic repeat request HARQ process identifier ID of the retransmission grant.

8. The method according to claim 7, wherein: Uplink resources for hybrid automatic repeat request (HARQ) transmission or HARQ retransmission are allocated via the plurality of configured grants.

9. The method according to claim 7, further comprising: receiving an indication of uplink resources from the base station using a cell radio network temporary identifier (C-RNTI); as well as An uplink signal associated with the discarded configured grant is transmitted using the uplink resources.

Images