Method and apparatus for processing data for packet duplication

Abstract

This disclosure relates to a communication technology and system that integrates IoT technology with a 5G communication system to support higher data transmission rates than 4G communication systems. This disclosure can be applied to smart services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and security-related services, etc.) based on 5G communication technology and IoT-related technologies. This disclosure relates to 5G or pre-5G communication systems for supporting higher data transmission rates than 4G communication systems such as LTE. Embodiments of the invention relate to methods and structures for processing data used in packet duplication. According to embodiments of the invention, a radio bearer establishment method, packet duplication operation, and buffer status reporting method are disclosed for use in performing packet duplication.

Description

[0001] This application is a divisional application of Chinese Patent Application No. 201880020299.3, filed on February 23, 2018, entitled "Method and apparatus for processing data for group copying". Technical Field

[0002] This disclosure relates to methods and apparatus for processing data for packet duplication, and more specifically, to data structures for packet duplication. Background Technology

[0003] To meet the growing demand for wireless data services following the commercialization of 4G communication systems, efforts are underway to develop improved 5G or pre-5G communication systems. For this reason, 5G or pre-5G communication systems are referred to as post-4G network communication systems or post-LTE systems.

[0004] To achieve high data transmission rates, the implementation of 5G communication systems in millimeter-wave bands (e.g., the 60 GHz band) is being considered. In 5G communication systems, technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO are being discussed as means to mitigate propagation path loss and increase propagation distance in the millimeter-wave band.

[0005] In addition, 5G communication systems have developed technologies such as evolved small cells, advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receive interference cancellation to improve system networks.

[0006] In addition, 5G systems have developed advanced coding and modulation (ACM) schemes such as hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC), as well as advanced access technologies such as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA).

[0007] Meanwhile, the Internet has evolved from a human-oriented network of connections where humans generate and consume information to an Internet of Things (IoT) network, in which distributed components of objects exchange and process information. The Internet of Everything (IoE) technology has emerged, combining big data processing technologies with IoT technologies through connections to cloud servers and other systems. Implementing IoT requires technological factors such as sensing technology, wired / wireless communication, network infrastructure, service interface technology, and security technology, and research is currently underway on technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC). In the IoT environment, by collecting and analyzing data generated from connected objects, intelligent Internet of Things (IT) services can be provided to create new value for people's lives. Through the integration of traditional information technology (IT) with multiple industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart cars, connected cars, smart grids, healthcare, smart appliances, and high-tech medical services.

[0008] Therefore, various attempts are underway to apply 5G communication systems to IoT networks. For example, 5G communication technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) are implemented using technologies such as beamforming, MIMO, and array antennas. Cloud RAN, as an application of big data processing technology, can be seen as an example of the convergence of 5G and IoT technologies.

[0009] Meanwhile, in packet-based mobile communication systems, it is necessary to study methods and structures for processing data used for packet replication. Summary of the Invention

[0010] Technical issues

[0011] The technical problem to be solved by the embodiments of this disclosure is to provide a method and apparatus for processing data for grouped replication, and more specifically, to provide a data structure therefor.

[0012] The technical problem to be solved by this disclosure is to provide a radio bearer configuration scheme, a packet replication operation, and a buffer status reporting scheme when performing packet replication.

[0013] Technical solution

[0014] According to one embodiment of this disclosure, a method performed by a terminal in a wireless communication system includes: receiving from a base station first information about a first cell allowed by a first logical channel associated with packet replication configured for a radio bearer, second information about a first subcarrier spacing (SCS) allowed by the first logical channel, third information about a second cell allowed by a second logical channel associated with the packet replication, and fourth information about a second SCS allowed by the second logical channel; receiving from the base station a first media access control (MAC) control element (CE) indicating activation of the packet replication; transmitting first uplink data of the first logical channel to the base station, wherein the first uplink data is transmitted on a first cell based on the first information using the first SCS based on the second information; and transmitting second uplink data of the second logical channel to the base station, wherein the second uplink data is transmitted on a second cell based on the third information using the second SCS based on the fourth information, wherein the second uplink data is a copy of the first uplink data and is copied from the first uplink data based on the first MAC CE.

[0015] According to an embodiment of this disclosure, a method performed by a base station in a wireless communication system includes: sending to a terminal first information about a first cell allowed by a first logical channel associated with packet replication configured for a radio bearer, second information about a first subcarrier spacing (SCS) allowed by the first logical channel, third information about a second cell allowed by a second logical channel associated with the packet replication, and fourth information about a second SCS allowed by the second logical channel; sending to the terminal a first media access control (MAC) control element (CE) indicating activation of the packet replication; receiving from the terminal first uplink data of the first logical channel, wherein the first uplink data is received on a first cell based on the first information using the first SCS based on the second information; and receiving from the terminal second uplink data of the second logical channel, wherein the second uplink data is received on a second cell based on the third information using the second SCS based on the fourth information, wherein the second uplink data is a copy of the first uplink data and is copied from the first uplink data based on the first MAC CE.

[0016] According to one embodiment of this disclosure, a terminal in a wireless communication system includes: a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver and configured to: receive from a base station first information about a first cell allowed by a first logical channel associated with packet replication configured for a radio bearer, second information about a first subcarrier spacing (SCS) allowed by the first logical channel, third information about a second cell allowed by a second logical channel associated with packet replication, and fourth information about a second SCS allowed by the second logical channel; receive from the base station a first media access control (MAC) control element (CE) indicating activation of the packet replication; transmit to the base station first uplink data of the first logical channel, wherein the first uplink data is transmitted on a first cell based on the first information using the first SCS based on the second information; and transmit to the base station second uplink data of the second logical channel, wherein the second uplink data is transmitted on a second cell based on the third information using the second SCS based on the fourth information, wherein the second uplink data is a copy of the first uplink data and is copied from the first uplink data based on the first MAC CE.

[0017] According to one embodiment of this disclosure, a base station in a wireless communication system includes: a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver and configured to: transmit to a terminal first information about a first cell allowed by a first logical channel associated with packet replication configured for a radio bearer, second information about a first subcarrier spacing (SCS) allowed by the first logical channel, third information about a second cell allowed by a second logical channel associated with packet replication, and fourth information about a second SCS allowed by the second logical channel; transmit to the terminal a first medium access control (MAC) control element (CE) indicating activation of the packet replication; receive from the terminal first uplink data of the first logical channel, wherein the first uplink data is received on a first cell based on the first information using the first SCS based on the second information; and receive from the terminal second uplink data of the second logical channel, wherein the second uplink data is received on a second cell based on the third information using the second SCS based on the fourth information, wherein the second uplink data is a copy of the first uplink data and is copied from the first uplink data based on the first MAC CE.

[0018] According to one embodiment of this disclosure, a method of a terminal in a mobile communication system may include: receiving from a base station information for mapping a logical channel to a component carrier (CC); and, based on the information, sending to the base station data packets processed in the logical channel via the CC to which the logical channel has been mapped.

[0019] According to another embodiment of this disclosure, a terminal in a mobile communication system may include: a transceiver for transmitting or receiving signals; and a controller configured to receive information from a base station for mapping a logical channel to a component carrier (CC), and to transmit data packets processed in the logical channel to the base station via the CC to which the logical channel has been mapped, based on the information.

[0020] According to yet another embodiment of this disclosure, a method for a base station in a mobile communication system may include: sending information to a terminal for mapping a logical channel to a component carrier (CC); and receiving, based on the information, data packets processed in the logical channel from the terminal via the CC to which the logical channel has been mapped.

[0021] According to yet another embodiment of this disclosure, a base station in a mobile communication system may include: a transceiver for transmitting or receiving signals; and a controller configured to transmit information to a terminal for mapping a logical channel to a component carrier (CC), and to receive data packets processed in the logical channel from the terminal via the CC to which the logical channel has been mapped, based on the information.

[0022] The technical problems to be solved by this disclosure are not limited to the above-mentioned technical topics. Other technical topics not mentioned herein can be clearly understood by those skilled in the art through the following description.

[0023] Beneficial technical effects

[0024] Embodiments of this disclosure provide data processing methods and structures for group replication. Furthermore, embodiments of this disclosure enable efficient replication transfers in communication environments with multiple links. Attached Figure Description

[0025] Figure 1 The radio bearer architecture in an LTE CA environment is shown.

[0026] Figure 2 A basic flowchart of a transmitter for performing packet replication according to an embodiment of the present disclosure is shown.

[0027] Figure 3 A carrier structure for group replication according to an embodiment of the present disclosure is shown.

[0028] Figure 4 A carrier structure for grouped replication according to another embodiment of the present disclosure is shown.

[0029] Figure 5 A carrier structure for grouped replication according to another embodiment of the present disclosure is shown.

[0030] Figure 6A carrier structure for grouped replication according to another embodiment of the present disclosure is shown.

[0031] Figure 7 A carrier structure for grouped replication according to another embodiment of the present disclosure is shown.

[0032] Figure 8 A carrier structure for grouped replication according to another embodiment of the present disclosure is shown.

[0033] Figure 9 A radio bearer configuration message for packet replication according to an embodiment of the present disclosure is shown.

[0034] Figure 10 The configuration and release of grouped replication according to an embodiment of the present disclosure are illustrated.

[0035] Figure 11 The configuration and release of grouped copying according to another embodiment of this disclosure are illustrated.

[0036] Figure 12 The configuration and release of grouped copying according to another embodiment of this disclosure are illustrated.

[0037] Figure 13 A scheme is shown that, according to an embodiment of the present disclosure, packet transmission is initiated via a logical channel for packet replication when packet replication begins.

[0038] Figure 14 A scheme for initiating packet transmission via a logical channel for packet replication when packet replication begins, according to another embodiment of the present disclosure, is illustrated.

[0039] Figure 15 A scheme for initiating packet transmission via a logical channel for packet replication when packet replication begins, according to another embodiment of the present disclosure, is illustrated.

[0040] Figure 16 The process performed when releasing a group copy is illustrated according to an embodiment of the present disclosure.

[0041] Figure 17 The procedure performed when releasing a group copy is illustrated according to another embodiment of this disclosure.

[0042] Figure 18 An example of the detailed operations when performing grouped replication is shown.

[0043] Figure 19 The transmission of an uplink buffer status report during packet replication is illustrated according to an embodiment of the present disclosure.

[0044] Figure 20The transmission of an uplink buffer status report during packet replication, according to another embodiment of this disclosure, is illustrated.

[0045] Figure 21 The transmission of an uplink buffer status report during packet replication is illustrated according to another embodiment of this disclosure.

[0046] Figure 22 An application of the number of grouped copies according to an embodiment of the present disclosure is shown.

[0047] Figure 23 The format of a group copy activation message according to an embodiment of the present disclosure is shown.

[0048] Figure 24 Another format of the group copy activation message according to an embodiment of the present disclosure is shown.

[0049] Figure 25 Another format of the group copy activation message according to an embodiment of the present disclosure is shown.

[0050] Figure 26 The format of a group copy deactivation message according to an embodiment of the present disclosure is shown.

[0051] Figure 27 Another format of the group copy deactivation message according to an embodiment of the present disclosure is shown.

[0052] Figure 28 Another format of the group copy deactivation message according to an embodiment of the present disclosure is shown.

[0053] Figure 29 Another format of a grouped copy activation / deactivation message according to an embodiment of this disclosure is shown.

[0054] Figure 30 A radio bearer configuration message for packet replication according to another embodiment of the present disclosure is shown.

[0055] Figure 31 A radio bearer configuration message for packet replication according to yet another embodiment of the present disclosure is shown.

[0056] Figure 32 Another format of the group copy activation message according to an embodiment of the present disclosure is shown.

[0057] Figure 33 Another format of the group copy deactivation message according to an embodiment of the present disclosure is shown.

[0058] Figure 34 Another format of the group copy activation message according to an embodiment of the present disclosure is shown.

[0059] Figure 35 Another format of the group copy deactivation message according to an embodiment of the present disclosure is shown.

[0060] Figure 36 The format of a message for dynamically changing the mapping relationship between a logical channel and a CC is shown according to an embodiment of the present disclosure.

[0061] Figure 37 The process of configuring the initiation of group copying according to an embodiment of the present disclosure is illustrated.

[0062] Figure 38 A terminal according to an embodiment of the present disclosure is shown.

[0063] Figure 39 A base station according to an embodiment of the present disclosure is shown.

[0064] Figure 40 The diagram illustrates the bearer structure for packet replication and the determination of the main logical channel according to an embodiment of the present disclosure.

[0065] Figure 41 The operation of a receiver according to an embodiment of the present disclosure is shown.

[0066] Figure 42 The format of a subheading according to an embodiment of this disclosure is shown.

[0067] Figure 43 The operation of a receiver according to an embodiment of the present disclosure is shown. Detailed Implementation

[0068] In the following, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that the same reference numerals denote the same structural elements in the drawings. Furthermore, detailed descriptions of known functions and configurations that may obscure the subject matter of the present disclosure will be omitted.

[0069] In describing exemplary embodiments of this disclosure, descriptions relating to technical content known in the art to which this disclosure pertains and not directly related to this disclosure will be omitted. This omission of unnecessary descriptions is intended to prevent obscuring the main concepts of this disclosure and to more clearly convey them.

[0070] For the same reason, some elements may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the dimensions of each element do not perfectly reflect the actual dimensions. In the drawings, identical or corresponding elements are given the same reference numerals.

[0071] The advantages and features of this disclosure, as well as the ways in which they are implemented, will become clear from the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose this disclosure and to inform those skilled in the art of its scope, and this disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements.

[0072] Here, it will be understood that each block of a flowchart diagram, and combinations of blocks within a flowchart diagram, can be implemented using computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, create a manner for implementing the functions specified in the flowchart blocks or blocks. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium, which can instruct the computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of art containing instruction means that implement the functions specified in the flowchart blocks or blocks. Computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, executed on the computer or other programmable apparatus, provide operations for implementing the functions specified in the flowchart blocks or blocks.

[0073] Additionally, each block in the flowchart can represent a module, segment, or section of code, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may not occur in sequence. For example, depending on the functions involved, two blocks shown consecutively may actually execute substantially simultaneously, or these blocks may sometimes execute in reverse order.

[0074] As used herein, a “unit” refers to a software element or hardware element, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), that performs a predetermined function. However, a “unit” is not always limited to software or hardware. A “unit” can be configured to be stored in addressable memory or to execute one or more processors. Therefore, a “unit” includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. Elements and functions provided by a “unit” can be combined into a “unit” of fewer elements or divided into a “unit” of more elements. Furthermore, elements and “units” can be implemented to reproduce one or more CPUs within a device or secure multimedia card.

[0075] Figure 1 Radio bearer architecture 100 in an LTE carrier aggregation (CA) environment is illustrated. In LTE CA, data streams are processed for each bearer and the data is mapped to a radio bearer. These radio bearers are mapped one-to-one to logical channels, and these logical channels are multiplexed in the MAC layer and then transmitted. CA is a technique that uses a set of multiple frequency resources by bundling multiple component carriers (CCs), where data already multiplexed in the MAC layer is transmitted through one of the CCs. Figure 1 One embodiment is shown, in which radio bearers 1 and 2, each equipped with a PDCP device and an RLC device, are mapped to logical channels #1 and #2, respectively. After these logical channels #1 and #2 are multiplexed in the MAC layer, data is then transmitted via one of CCs 1, 2, and 3. There is no limitation on the number of CCs available for transmission to each logical channel or each radio bearer. Here, a CC can be identified as a cell by the terminal and can be configured as a primary cell (PCell) or a secondary cell (SCell), as described below.

[0076] Figure 2A basic flowchart 200 for a transmitter performing packet copying is shown. When packet copying is configured for a specific radio bearer 210, the data processed by the radio bearer can undergo the packet copying process. Typically, the packet copying process includes performing data copying and then transmitting the data through different logical channels. Here, the data packets copied by packet copying can be transmitted separately through different logical channels 220 and 230, separately to different branches in a split bearer environment, separately via different CCs, or transmitted with different base parameters (numerology) or TTI types. The operation of copying data packets by packet copying is performed by one of the PDCP, RLC, and MAC layers, which are data processing layers. Furthermore, the data used here can be in the form of IP packets processed by the user. In some embodiments, the data can be control signals within a protocol, such as RRC messages.

[0077] Figure 3 An embodiment of a carrier structure 300 for grouped replication is shown. Figure 3 In the illustrated embodiment, the bearer structure includes radio bearer A310 and radio bearer B320. Typically, one or more signaling radio bearers (SRBs) and data radio bearers can be provided between the base station and the terminal. Radio bearer A310 is a bearer that allows packet copying, while radio bearer B320 is a bearer that does not allow packet copying. Figure 3 In the illustrated embodiment, a process is shown in which the PDCP device (or entity) of radio bearer A310 copies PDCP protocol data units (PDUs) and sends the copied PDCP PDUs to different RLC devices. The RLC devices are mapped to logical channels #1 (330) and #2 (340), respectively. Radio bearer B 320 is mapped to a logical channel (logical channel #3) because packet copying of it is not permitted.

[0078] Here, to perform efficient packet transmission, logical channels need to be mapped to component carriers (CCs). In other words, by mapping logical channels to CCs (i.e., by establishing / defining the mapping relationship between logical channels and CCs), it is possible to specify restrictions on the CCs that can transmit data for a particular logical channel. In the case of packet duplication, the main purpose is to increase reliability and reduce latency by performing separate data processing on the copied packets and then sending them. To achieve this effectively, the copied data packets need to be transmitted separately through different CCs. Figure 3In the illustrated embodiment, logical channel #1 330 is mapped to CC1 and CC2 such that data packets from logical channel #1 330 can be transmitted through CC1 and CC2, logical channel #2 340 is mapped to CC3 such that data packets from logical channel #2 340 can be transmitted through CC3, and data packets from logical channel #3 can be transmitted through CC2 and CC3. Because the logical channels and CCs are mapped to each other as described above, it is possible to prevent data packets from being transmitted through the same CC, even if the copied data packets undergo multiplexing processing in the MAC device (entity). In other words, two or more copies of data packets are not included in the same MAC PDU, and the original PDCP PDU and the copied PDCP PDU are not transmitted in the same transport block.

[0079] On the other hand, unlike the embodiments described above, logical channels can also be mapped to basic parameters or TTIs. That is, independent of or in combination with the logical channel-to-CC mapping, logical channels can be mapped to specific basic parameters and / or TTIs used for data packet transmission. Furthermore, this mapping between logical channels and CCs is not limited to the packet replication process described above and can be performed separately from packet replication.

[0080] Whether a bearer allows packet replication can be determined based on the type of service contained in the packet. Service types can be categorized as voice, video streaming, web browsing data, etc., and specific types of services can be configured to allow packet replication based on this categorization. Packet replication can also be configured based on the data's QoS configuration value. Alternatively, this QoS configuration value can be represented by an ID indicating QoS, such as a QoS stream ID. In this case, packet replication can also be allowed for specific QoS stream IDs. For example, a bearer transmitting packets with QoS stream IDs of values ​​0 to 15 can perform packet replication, while a bearer transmitting packets with other QoS stream IDs cannot. Whether a bearer allows packet replication can be determined by each of the various standards mentioned above, or a combination of two or more of them, and other standards besides those mentioned above can also be applied.

[0081] In addition, packet replication can be applied to both the SRB for transmitting control signals and the DRB for transmitting data.

[0082] Figure 4 Another embodiment of the carrier structure for grouped replication is shown (as indicated by reference numeral 400 in the figures). Figure 4In the illustrated embodiment, radio bearer A410 and radio bearer B420 are configured. Typically, one or more signaling radio bearers (SRBs) and data radio bearers can be provided between the base station and the terminal. Radio bearer A410 is a bearer that allows packet copying, while radio bearer B420 is a bearer that does not allow packet copying. Figure 4 In the illustrated embodiment, a process is shown in which the RLC device (or entity) of radio bearer A410 copies RLC protocol data units (PDUs) and transmits the copied RLC PDUs through different logical channels. The RLC device of radio bearer A410 is mapped to logical channels #1 and #2. Since packet copying is not allowed in radio bearer B, one logical channel is mapped to logical channel #3.

[0083] Here, to perform efficient packet transmission, logical channels need to be mapped to component carriers (CCs). In other words, by mapping logical channels to CCs (i.e., by establishing / defining the mapping relationship between logical channels and CCs), it becomes possible to specify restrictions on the CCs that can transmit data for a particular logical channel. In the case of packet duplication, the main purpose is to increase reliability and reduce latency by performing separate data processing on the copied packets and then sending them. To achieve this effectively, the copied data packets need to be transmitted separately through different CCs. Figure 4 In the illustrated embodiment, logical channel #1 is mapped to CC1 and CC2 such that data packets from logical channel #1 can be transmitted through CC1 and CC2; logical channel #2 is mapped to CC3 such that data packets from logical channel #2 can be transmitted through CC3; and data packets from logical channel #3 can be transmitted through CC2 and CC3. Because the logical channels and CCs are mapped as described above, even if copied data packets undergo multiplexing in the MAC device (entity) via packet duplication, data packets are prevented from being transmitted through the same CC. In other words, two or more copies of data packets are not included in the same MAC PDU, and the original PDCPPDU and the copied PDCP PDU are not transmitted in the same transport block.

[0084] On the other hand, unlike the embodiments described above, logical channels can also be mapped to basic parameters or TTIs. That is, independent of or in combination with the logical channel-to-CC mapping, logical channels can be mapped to specific basic parameters and / or TTIs used for data packet transmission. Furthermore, this mapping between logical channels and CCs is not limited to the packet replication process described above and can be performed separately from packet replication.

[0085] In addition, packet replication can be applied to both the SRB for transmitting control signals and the DRB for transmitting data.

[0086] Figure 5 Another embodiment of the bearer structure for packet replication is shown (as indicated by reference numeral 500). For the efficiency of a communication network, packet replication may need to be performed under predefined specific conditions. For this purpose, logical channels can be classified and defined as logical channels used both when packet replication is not performed and when packet replication is performed (primary logical channels) and logical channels used in data transmission when only packet replication is performed (auxiliary logical channels). Figure 5 In the illustrated embodiment, regarding the radio bearer A510 that allows packet duplication, logical channel #1 520 is configured as the primary logical channel, and logical channel #2 530 is configured as the secondary logical channel. Another bearer structure is... Figure 3 The primary and secondary logical channels are the same as defined in [the original text]. The primary and secondary logical channels can be specified by the base station through RRC configuration, etc. Additionally, the terminal can be notified of data transmission on the secondary logical channel via a packet replication activation message, etc. A specific embodiment of such a packet replication activation message will be described later.

[0087] In addition, packet replication can be applied to both the SRB for transmitting control signals and the DRB for transmitting data.

[0088] Figure 6 Another embodiment of the bearer structure for packet replication is shown (as indicated by reference numeral 600). For the efficiency of a communication network, it may be necessary to perform packet replication under predefined specific conditions. For this purpose, logical channels can be classified and defined as logical channels used both when packet replication is not performed and when packet replication is performed (primary logical channels) and logical channels used only in data transmission when packet replication is performed (auxiliary logical channels). Figure 6 In the illustrated embodiment, regarding the radio bearer A610 that allows packet duplication, logical channel #1 620 is configured as the primary logical channel, and logical channel #2 630 is configured as the secondary logical channel. Another bearer structure is... Figure 4 The primary and secondary logical channels are the same as those defined in [the original text]. These can be specified by the base station, RRC configuration, etc. Additionally, data can be transmitted via the secondary logical channel to notify the terminal, for example, through a packet replication activation message. A specific embodiment of such a packet replication activation message will be described later.

[0089] In addition, packet replication can be applied to both the SRB for transmitting control signals and the DRB for transmitting data.

[0090] Figure 7 Another embodiment of the carrier structure for grouped replication is shown (as indicated by reference numeral 700 in the figure). Figure 7 A simplified structure is shown, in which... Figures 3 to 6The embodiments shown depict a single radio bearer mapped to multiple logical channels and CCs, with PDCP and RLC devices omitted. This can be used... Figures 3 to 6 One of the mapping methods shown in the embodiments is used to implement PDCP devices and RLC devices. Figure 7 In the illustrated embodiment, the radio bearer #1 710, which has undergone packet replication, is transmitted via logical channels #1 720 and #3 750, wherein logical channel #1 720 is mapped to CC1 730 and CC3 740 and then transmitted therethrough, and logical channel #3 750 is mapped to CC4 760 and CC5 770 and then transmitted therethrough.

[0091] In addition, packet replication can be applied to both the SRB for transmitting control signals and the DRB for transmitting data.

[0092] Figure 8 Another embodiment of the carrier structure for grouped replication is shown (as indicated by reference numeral 800 in the figure). Figure 8 A simplified structure is shown, in which... Figures 3 to 6 The embodiments shown depict a single radio bearer mapped to multiple logical channels and CCs, and the PDCP and RLC devices are omitted. The PDCP and RLC devices can be used... Figures 3 to 6 One of the mapping methods in the embodiments shown is implemented. Figure 8 In the illustrated embodiment, the radio bearer #1810, to which packet replication has been performed, is transmitted via logical channels #1 820 and #3 850, wherein logical channel #1 820 is mapped to CC1 830 and CC3 840 and then transmitted therethrough, and logical channel #3 850 is mapped to CC4 860 and CC5 870 and then transmitted therethrough. Figure 8 In the illustrated embodiments, it is further shown that each CC supports multiple basic parameters (Numerology) or TTI types. For example, Type 1 of CC1 830 may have a subcarrier spacing of 15 kHz and a TTI of 1 ms, and Type 2 835 may have a subcarrier spacing of 30 kHz and a TTI of 0.25 ms. Figure 8In the illustrated embodiment, the radio bearer #1 810 to which packet replication has been performed can be transmitted via type 2 (835) of CC1 830, types 1 and 2 (845) of CC3 840, types 1, 2 and 3 (865) of CC4 (860), and type 1 (875) of CC5 (870). The above description can be understood as such that specific numerical parameters and / or TTI types have been previously mapped to logical channels and / or CCs, through which copied data packets obtained by performing packet replication are transmitted. On the other hand, the above mapping is an embodiment and can be specified differently depending on the configuration of the base station or terminal, service type, QoS flow ID, etc.

[0093] In addition, packet replication can be applied to both the SRB for transmitting control signals and the DRB for transmitting data.

[0094] Figure 9 It shows Figures 3 to 8 An embodiment of the radio bearer configuration message for packet replication described herein (as indicated by reference numeral 900 in the accompanying drawings). Figure 9 The DRB ID configured in the configuration is 6 and the DuplicationMode field is configured to True, which indicates that group replication is allowed. Figure 9 The logical channel IDs (represented by the LogicalChannelIdentity field) for performing packet replication are shown to be 4 and 5. Packets transmitted via logical channel #4 can be transmitted only with the 15kHz and 30kHz base parameters of CCs 1, 2, and 3 (represented by the Correspondingnumerology field). Packets transmitted via logical channel #5 can use all CCs but only with the 15kHz base parameter. The base parameters can be displayed in frequency intervals, such as... Figure 9 As shown, however, it can also be specified as a previously configured base parameter or TTI type. Logical channel #4 is the primary logical channel, and logical channel #5 is the secondary logical channel (as shown in the DuplicationType field). Furthermore, each logical channel can independently perform duplicate transmissions of the same packets, and can independently perform duplicate packet transmissions multiple times, the same number of times as the value configured in the NumberOfDuplication field. Independent duplicate packet transmissions mean that the sender determines to retransmit even if a NACK is not received for the ARQ.

[0095] Figure 10An embodiment for configuring and releasing packet replication is illustrated (as shown by reference numeral 1000 in the accompanying drawings). The base station can configure packet replication of the radio bearer by sending a replication configuration message to the terminal (S1010). This message may include... Figure 9 Some configuration messages. In Figure 10 In the illustrated embodiment, when a replication configuration message is received, the terminal configures the bearer for packet replication and performs packet replication (S1020). Subsequently, when the terminal receives a duplicate release message from the base station (S1030), it can release the bearer for packet replication, release the auxiliary logical channel for packet replication, or perform a process without performing packet replication (S1040).

[0096] Figure 11 Another embodiment for configuring and releasing packet replication is shown (as indicated by reference numeral 1100 in the figures). The base station can configure packet replication of the radio bearer by sending a replication configuration message to the terminal (S1110). This message may include... Figure 9 Some configuration messages. In Figure 11 In the illustrated embodiment, when a replication configuration message is received, the terminal configures the bearer for packet replication. Then, when a replication activation message is received (S1120), the terminal performs actual packet replication (S1130). Before receiving the replication activation message, a logical channel for packet replication is generated, but no actual data is transmitted through the logical channel. At this time, data transmission via the primary logical channel can be performed only. Subsequently, when a replication deactivation message is received from the base station (S1140), the terminal stops actual packet replication (S1150). However, the bearer structure, such as that of the logical channel for packet replication, remains unchanged. If an auxiliary logical channel exists, data transmission via the auxiliary logical channel can be stopped. Subsequently, when the terminal receives a replication release message from the base station (S1160), the terminal can release the bearer for packet replication, release the auxiliary logical channel for packet replication, or perform a process without performing packet replication.

[0097] Figure 12 Another embodiment for configuring and releasing packet replication is shown (as indicated by reference numeral 1200). The base station can configure packet replication of the radio bearer by sending a replication configuration message to the terminal (S1210). This message may include... Figure 9 Some configuration messages. In Figure 12In the illustrated embodiment, when a replication configuration message is received, the terminal configures the bearer for packet replication. Subsequently, when the terminal receives a replication activation message (S1220) and the previously configured conditions for packet replication (replication conditions) are met (S1230), the terminal performs actual packet replication (S1240). The packet replication conditions can be such that the radio link quality between the terminal and the base station is equal to or lower than a certain level. Before receiving the replication activation message, a logical channel for packet replication is generated, but no actual data is transmitted through the logical channel. At this time, data transmission via the primary logical channel can be performed only. If the previously configured conditions for packet replication are no longer met, or if the conditions for canceling packet replication transmission are met, packet replication is not performed even after receiving the replication activation message. Furthermore, when a replication deactivation message is received from the base station (S1250), the terminal stops actual packet replication (S1260). However, at this time, the bearer structure, such as the logical channel for packet replication, remains unchanged. If an auxiliary logical channel exists, data transmission via the auxiliary logical channel can be stopped. Subsequently, when the terminal receives a replication release message from the base station (S1270), it can release the bearer used for packet replication, release the auxiliary logic channel used for packet replication, or perform a process of not performing packet replication.

[0098] Figure 13 An embodiment of a scheme in which packet transmission begins via a logical channel used for packet replication when packet replication starts is shown (as indicated by reference numeral 1300 in the accompanying drawings). Figure 13 In the illustrated embodiment, it is assumed that transmission via logical channel #1 (LC1, 1310) is performed only before the replication transmission, and that transmission via logical channel #2 (LC2, 1320) is also performed when packet replication begins. This can be based on... Figures 10 to 12 The various embodiments shown and described herein perform group replication based on the actual start time of group replication. Figure 13 In the illustrated embodiment, when packet replication has begun, packets that have been sent from existing logical channel #11310 but for which no ACK has yet been received can be transmitted (i.e. copied) from the buffer via logical channel #21320 in the order of the packet with the earliest sequence number (SN). Figure 13 In the illustrated embodiment, even though packets A to E have been sent, since only packets A, C, and E are in the receiving state at the start of packet copying, all packets (i.e., B to E) starting from packet B with the earliest sequence number among packets B and D that have not received an ACK are transmitted (i.e. copied) through logical channel #21320 to perform packet transmission.

[0099] In this case, the RLC sequence number (SN) for logical channel #2 1320 can start from the beginning; otherwise, the sequence number of the RLC device for logical channel #1 1320 can be used as is. If the same sequence number is used for logical channels #1 1310 and #2 1320, a portion of the RLC status information for logical channel #1 1310 can be sent to the RLC device corresponding to the receiver's logical channel #2 1320. Here, the corresponding information may include the start sequence number of the RLC SN where transmission begins (RLC SN of packet B), all RLC variables, etc. Alternatively, according to one embodiment, the corresponding information may be the PDCP SN or PDCP COUNT corresponding to each RLC packet.

[0100] Figure 14 Another embodiment of a scheme initiating packet transmission via a logical channel used for packet replication when packet replication is initiated is shown (as indicated by reference numeral 1400 in the figures). Figure 14 In the illustrated embodiment, it is assumed that transmission via logical channel #1 (LC1, 1410) is performed only before repeated transmission, and transmission via logical channel #2 (LC2, 1420) is also performed when packet replication begins. This can be based on... Figures 10 to 12 The various embodiments shown and described herein perform group replication based on the actual start time of group replication. Figure 14 In the illustrated embodiment, when packet replication begins, packets that have been sent via existing logical channel #1 1410 but have not yet received an ACK, as well as packets that have not yet been sent and are held in the buffer, can be transmitted (i.e., replicated) via logical channel #2 1420 in a sequence starting with the packet having the earliest sequence number (SN). Figure 14 In the illustrated embodiment, even though packet A has been sent to E, since only packets A, C, and E are in the receiving state at the start of packet replication, packets B and D, which have not yet received ACKs, can still be transmitted (i.e., replicated) via logical channel #2 1420 to perform their packet transmission. If all packets have received ACKs, the remaining packets in the buffer can be replicated and transmitted via logical channel #2 1420.

[0101] In this case, the RLC sequence number (SN) for logical channel #2 1420 can start from the beginning, or the sequence number of the RLC device for logical channel #1 1410 can be used as is. If the same sequence number is used for logical channels #1 1410 and #2 1420, a portion of the RLC status information for logical channel #1 1410 can be sent to the RLC device corresponding to the receiver's logical channel #2 1420. Here, the corresponding information may include the start sequence number of the RLC SN where transmission begins (the RLC SN of packet B) or all RLC variables, etc. Alternatively, according to one embodiment, the corresponding information may be the PDCP SN or PDCP COUNT corresponding to each RLC packet.

[0102] Figure 15 Another embodiment of a scheme for initiating packet transmission via the logical channel of packet replication when packet replication is initiated is shown (as indicated by reference numeral 1500 in the figure). Figure 15 In the illustrated embodiment, it is assumed that transmission via logical channel #1 (LC1, 1510) is performed only before the replication transmission, and that transmission via logical channel #2 (LC2, 1520) is also performed when packet replication begins. This can be based on... Figures 10 to 12 The various embodiments shown and described herein perform group replication based on the actual start time of group replication. Figure 15 In the illustrated embodiment, when packet replication begins, the packet with the earliest sequence number (SN) among those packets not yet sent from the existing logical channel #1 1510 can be transmitted (i.e., replicated) via logical channel #21520. Figure 15 In the illustrated embodiment, even though packets A to D have already been sent, packet replication is still performed to configure packet replication for the yet-to-be-sent packet E, since only packets A and C are in the receiving state at the start of packet replication. This replication is then transmitted (i.e., copied) via logical channels #1 1510 and #2 1520. In other words, data packets not sent via logical channel #1 1510 can be copied and transmitted via logical channel #2 1520.

[0103] In this case, the RLC sequence number (SN) for logical channel #2 1520 can start from the beginning, or it can use the sequence number of the RLC device for logical channel #1 1510 as is. If the same sequence number is used for logical channel #1 1510 and logical channel #2 1520, a portion of the RLC status information for logical channel #1 1510 can be sent to the RLC device corresponding to the receiver's logical channel #2 1520. Here, the corresponding information may include the start sequence number of the RLC SN where transmission begins (the RLC SN of packet B) or all RLC variables, etc. Alternatively, according to one embodiment, the corresponding information may be the PDCP SN or PDCP COUNT corresponding to each RLC packet.

[0104] Figure 16 An embodiment of the process performed when releasing packet replication while performing data transfer in a state in which packet replication is being performed is shown (as indicated by reference numeral 1600 in the accompanying drawings). Figure 16 The illustrated embodiment describes how packet transmission is performed via packet duplication through logical channel #1 1610 and logical channel #2 1620, according to... Figures 10 to 12 The operations performed during the release of actual group replication in the various embodiments described above. Figure 16 In the illustrated embodiment, at the moment of releasing packet replication, in logical channel #1 1610, ACKs for packets A, C, and E have been received and packets B and D have been transmitted, but ACKs for packets B and D have not yet been received. Similarly, in logical channel #2 1620, ACKs for packets B and E have been received and packets A, C, and D have been transmitted, but ACKs for packets A, C, and D have not yet been received. Here, to avoid performing packet replication, data will be cleared from one of the logical channels. Figure 16 In this context, we assume that data (1620) can be arbitrarily cleared from logical channel #2, but the logical channel can be selected based on specific conditions. Here, the specific conditions could be a scheme in which transmission is continuously performed through the main logical channel while data is cleared from the auxiliary logical channel and its transmission is not performed.

[0105] Figure 17 Another embodiment of the process performed when releasing the packet copy during data transfer is shown in a state in which packet copy has already been performed (as indicated by reference numeral 1700). Figure 17 This illustrates the effect of packet transmission performed via packet duplication through logical channels #11710 and #21720. Figures 10 to 12 The operations performed during the release of actual group replication in the various embodiments described above. Figure 17In the illustrated embodiment, at the moment of releasing packet replication, in logical channel #1 1710, ACKs for packets A, C, and E have been received and packets B and D have been transmitted, but ACKs for packets B and D have not yet been received. Similarly, in logical channel #2 1720, ACKs for packets B and E have been received and packets A, C, and D have been transmitted, but ACKs for packets A, C, and D have not yet been received. Here, to avoid performing packet replication, data must be cleared from one of the logical channels. Figure 17 In this context, it is assumed that the data is arbitrarily cleared from logical channel #2 1720, but the logical channel can be selected based on specific conditions. Here, the specific conditions could be a scheme in which transmission is continuously performed through the main logical channel while data is cleared from the auxiliary logical channel and its transmission is not performed.

[0106] However, in the case of packet B, since the transmission has been successful, a message indicating successful transmission can be transmitted via logical channel #1 1710 before clearing logical channel #2 1720, thus preventing unnecessary retransmissions. Figure 17 In the illustrated embodiment, the RLC device (or entity) of logical channel #2 1720 notifies the RLC device of logical channel #1 1710 that packets B and E have been successfully received with ACK, and the RLC device of logical channel #1 1710 can update the status of packet B, which has not received ACK, to a successful reception status and assume that packet B has been successfully received with ACK. The transmission of this information can be performed by directly informing the RLC device of logical channel #1 1710 of the RLC sequence number (SN) of the packet sent from the RLC device of logical channel #2 1720, or by performing the transmission of this information so that the RLC device of logical channel #2 1720 notifies the PDCP device in the radio bearer of the PDCP sequence number (or RLC SN) of the corresponding packet so that the PDCP device notifies the RLC device in logical channel #1 1710 of the sequence number (RLC or PDCP SN) of the corresponding packet. If the RLC sequence numbers of logical channel #1 1710 and logical channel #2 1720 are different for each packet, a process of converting such values ​​can be performed. Here, PDCP sequence number, PDCP COUNT value, etc., can be used in the conversion process. Additionally, according to an embodiment, an RLC device in one logical channel can directly notify an RLC device in another logical channel of the PDCP SN or PDCP COUNT information of a packet that has received an ACK or NACK for the corresponding packet.

[0107] exist Figure 17In the illustrated embodiment, when packet replication transmission is released, the transmission status of each logical channel, i.e., RLC status information or ACK reception status, is sent and reflected to the other logical channel. However, this operation is not limited to the time point of releasing packet replication transmission, and even when normal packet replication is performed and transmitted, the process of notifying and reflecting the transmission status between logical channels can be performed. Such information transmission can be performed by directly notifying the RLC sequence number (SN) sent from the RLC device of logical channel #2 1720 to the RLC device of logical channel #1 1710, or by performing such information transmission so that the RLC device of logical channel #2 1720 notifies the PDCP sequence number of the corresponding packet to the PDCP device in the radio bearer so that the PDCP device notifies the RLC device of the corresponding packet to the RLC device in logical channel #1 1710. If the RLC sequence numbers of logical channel #1 1710 and logical channel #2 1720 are different for each packet, a process of converting such values ​​can be performed. Here, the PDCP sequence number, PDCP COUNT value, etc., can be used in the conversion process. According to an embodiment, the transmission interval can be configured to a pre-configured value so that information transmission does not occur too frequently. For example, the transmission interval can be configured such that the transmission status of a logical channel is sent from one logical channel to another every 10ms. Furthermore, this operation can also be applied to situations where, in HARQ mode rather than ARQ mode, packet replication is applied to different HARQ devices.

[0108] At the same time, such as Figure 16 and 17 As described in the embodiments, when packet copying is released, packet transmission can be performed continuously without packet copying for packets that exist in the PDCP buffer and have not yet been transmitted to lower layers (e.g., RLC).

[0109] Figure 18 An example of a specific operation is shown when performing grouped replication (as indicated by reference numeral 1800 in the attached figure). Figure 18The diagram illustrates the states of PDCP PDU#1 1810, PDCP PDU#2 1820, and PDCP PDU#3 1830 at any given time point. In the case of PDCP PDU#1 1810, packets arriving at the transmitter's PDCP layer are forwarded to the RLC layer to allow the addition of an RLC header, and then sent to the receiver or forwarded to the MAC layer or lower. In the case of PDCP PDU#2 1820, packets arriving at the transmitter's PDCP layer are forwarded to the RLC layer to allow the addition of an RLC header, but have not yet been forwarded to the MAC layer or lower. PDCP PDU#2 1820 can be generated when packets are pre-generated (pre-processed) before allocating UL-licensed radio resources. PDCP PDU#3 1830 can be resolved to a state where packets arriving at the transmitter's PDCP layer do not request processing from lower layers.

[0110] According to one embodiment, when performing packet replication, the replication transmission of packets that have arrived at the transmitter's PDCP layer but have not yet been transmitted to the RLC layer can begin. Figure 18 In the illustrated embodiment, PDCP PDU#31830 corresponds to a packet used for copy transmission. Transmission of copies of packets that have already been transmitted to the RLC layer (such as PDCP PDU#1 1810 and PDCP PDU#2 1820) may not be initiated.

[0111] According to another embodiment, when performing packet replication, replication transmission can be initiated for packets that have already reached the PDCP layer of the transmitter, packets that have been transmitted to the RLC layer to allow the addition of an RLC header and then transmitted to the MAC layer or lower below it, or packets that are subsequently transmitted (e.g., packets that have already reached the PDCP layer of the transmitter, packets that have already been transmitted to the RLC layer to allow the addition of an RLC header and then transmitted to the MAC layer or lower below it, or packets that are subsequently transmitted). Figure 18 PDCP PDU#1 1810 in the packet; a packet that has reached the transmitter's PDCP layer and been transmitted to the RLC layer to allow the addition of an RLC header but has not yet been transmitted to the MAC layer or lower layers below it (e.g., a packet that has reached the transmitter's PDCP layer and been transmitted to the RLC layer to allow the addition of an RLC header but has not yet been transmitted to the MAC layer or lower layers below it). Figure 18 PDCP PDU#2 1820 in the middle); packets that have reached the PDCP layer of the transmitter but have not been transmitted to the RLC layer (e.g., packets in the PDCP layer of the transmitter). Figure 18(PDCP PDU#3 1830 in the RLC). Therefore, when initiating a copy transmission, the transmitter sends (or reports) information to the PDCP layer about packets that have reached the RLC layer but have not yet been successfully acknowledged. This packet information sent to the PDCP layer may include the PDCP SN, etc. Based on this information, the transmitter can select packets corresponding to the received packet information and can begin packet copy transmission. To send packet information, the RLC or PDCP layer can manage the values ​​of the packet's RLC sequence number (SN) and PDCP SN. Based on the management of the RLC or PDCP SN, the PDCP sequence number values ​​of packets that have not yet been successfully transmitted and exist in the RLC buffer can be determined.

[0112] Figure 19 An example is shown whereby a terminal sends an uplink buffer status report to the base station when performing packet replication (as indicated by reference numeral 1900 in the figure). Figure 19 In the illustrated embodiment, radio bearers 1 and 2 do not perform packet replication and are mapped to logical channels #1 and #2, respectively. However, it is assumed that packet replication is configured for radio bearer #3 and radio bearer #3 is mapped to logical channels #3 1910 and #4 1920. Buffer status reporting is performed based on the buffer status of each logical channel. Therefore, it is necessary to determine the buffer status to be reported for the logical channel that performs packet replication at the time of sending the buffer status report.

[0113] exist Figure 19 In the illustrated embodiment, packet replication is not performed for logical channels #1 and #2, and their respective buffer states are used as is. However, for logical channels #3 1910 and #4 1920, the buffer state of logical channel #3 1910, which has the largest amount of data in the buffer (buffer state) among the two logical channels, is used for reporting (as indicated by label 1930). According to the embodiment, before sending the buffer state report, a logical channel can share RLC state information or ACK reception status with other logical channels, which is already... Figure 17 As described in the text.

[0114] Figure 20 Another embodiment is shown in which the terminal sends an uplink buffer status report to the base station during packet replication (as indicated by reference numeral 2000). Figure 20In the illustrated embodiment, radio bearer 1 and radio bearer 2 do not perform packet replication and are mapped to logical channels #1 and #2, respectively. However, it is assumed that packet replication is configured for radio bearer #3 so that radio bearer #3 is mapped to logical channels #3 2010 and #4 2020. Buffer status reports are sent based on the buffer status of each logical channel. Therefore, it is necessary to determine which buffer status to report for the logical channel that performs packet replication at the time of sending the buffer status report.

[0115] exist Figure 20 In the illustrated embodiment, packet replication is not performed for logical channels #1 and #2, and their respective buffer states are used as is. However, for logical channels #3 2010 and #4 2020, only the buffer state of logical channel #4 2020, which has been configured as the primary logical channel, is reported (as indicated by reference numeral 2030). Alternatively, the terminal can arbitrarily select logical channels or can notify the base station which logical channel is used for buffer state reporting. According to one embodiment, before sending the buffer state, a logical channel can share RLC state information or ACK reception state with other logical channels, which has already been implemented. Figure 17 As described in the instructions.

[0116] Figure 21 An example is shown whereby a terminal sends an uplink buffer status report to the base station when performing packet replication (as indicated by reference numeral 2100 in the figure). Figure 21 In the illustrated embodiment, radio bearers 1 and 2 do not perform packet replication and are mapped to logical channels #1 and #2, respectively. However, it is assumed that packet replication is configured for radio bearer #3, and radio bearer #3 is mapped to logical channels #32110 and #42120. Buffer status reporting is performed based on the buffer status of each logical channel. Therefore, it is necessary to determine which buffer status to report for the logical channel for which packet replication is performed when sending the buffer status report.

[0117] exist Figure 21 In the illustrated embodiment, packet replication is not performed for logical channels #1 and #2, and the corresponding buffer states are used as is. However, for logical channels #3 2110 and #4 2120, buffer state report messages are generated using the buffer states of each logical channel as is (as indicated by reference numeral 2130). According to one embodiment, before sending the buffer state report, a logical channel can share RLC state information or ACK reception state with other logical channels, which has already been implemented. Figure 17 As described in the instructions.

[0118] Figure 22An example is shown (as indicated by reference numeral 2200) of how many times group replication is applied when performing group replication. This can be achieved by applying... Figure 9 The NumberOfDuplication field, as described in [the document], is used to perform packet replication. The NumberOfDuplication field indicates the number (or number of times) packet replication is applied to the logical channel. Here, because transmitting too early after performing packet replication can reduce its efficiency, transmissions need to be performed at certain intervals. Figure 22 In the illustrated embodiment, the NumberOfDuplication value is configured to 3, such that at the first transmission of a packet, the first transmission can begin with a Duplication Count configured to be 3, which is the NumberOfDuplication value (as shown by reference numeral 2210). Subsequently, copied packets can be sent after a pre-configured timer value, and the Duplication Count can be reduced to 2. Similarly, operations can be performed such that copied packets can be sent after a predetermined timer value 2220 to reduce the Duplication Count to 1. When the Duplication Count becomes 0, transmission of copied packets is no longer performed (as shown by reference numeral 2240).

[0119] Here, the transmission of copied packets can be performed through different logical channels or different HARQ devices.

[0120] Figure 23 It shows the relationship with Figure 11 and 12 An embodiment relating to the format of the replication activation message as defined herein (as shown by reference numeral 2300). Here, the replication activation message 2310 may be transmitted in MAC Control Element (CE) format. Furthermore, an indication that the message is a replication activation message may be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a replication activation message may be included in the ID field. Alternatively, a particular message may include an indication that the message is a replication activation message, and such a message may be transmitted in DCI format.

[0121] Figure 24 It shows the relationship with Figure 11 and 12An embodiment relating to the format of the replication activation message as defined in the figure (as indicated by reference numeral 2400) is shown. Here, the replication activation message 2410 can be transmitted in MAC Control Element (CE) format. Furthermore, an indication that the message is a replication activation message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a replication activation message can be included in the ID field. Alternatively, a specific message can include an indication that the message is a replication activation message. Alternatively, the replication activation message 2410 can be transmitted by adding the ID of the logical channel that allows packet replication to the radio bearer. Additionally, such a message can also be transmitted in DCI format.

[0122] Figure 25 It shows the relationship with Figure 11 and 12 An embodiment related to the format of the replication activation message as defined in the figure (as shown by reference numeral 2500). Here, the replication activation message 2510 can be transmitted in MAC Control Element (CE) format. Furthermore, an indication that the message is a replication activation message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a replication activation message can be included in the ID field. Alternatively, a specific message can include an indication that the message is a replication activation message. Alternatively, it can include CC information that allows packet replication and send it to the radio bearer. In this case, packet replication can be performed in a manner that activates a logical channel, which enables transmission through the corresponding CC (or a logical channel mapped to the corresponding CC). Additionally, such a message can also be transmitted in DCI format.

[0123] Figure 26 Showing with Figure 11 and 12 An embodiment relating to the format of the copy deactivation message as defined in [reference numeral 2600] is described below. Here, the copy deactivation message 2610 can be transmitted in MAC Control Element (CE) format. Furthermore, an indication that the message is a copy deactivation message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a copy deactivation message can be included in the ID field. Alternatively, a specific message may include an indication that the message is a copy deactivation message, and such a message can be transmitted in DCI format.

[0124] Figure 27 It shows the relationship with Figure 11 and 12An embodiment relating to the format of the copy deactivation message as defined in [reference numeral 2700] is described here. Here, the copy deactivation message 2710 can be transmitted in MAC Control Element (CE) format. Furthermore, an indication that the message is a copy deactivation message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a copy deactivation message can be included in the ID field. Alternatively, a specific message can include an indication that the message is a copy deactivation message for that specific message. Furthermore, the copy deactivation message 2710 can be transmitted while the ID of the logical channel used to stop packet copying has been added to the radio bearer. Additionally, such a message can also be transmitted in DCI format.

[0125] Figure 28 Showing with Figure 11 and 12 An embodiment relating to the format of the copy deactivation message as defined herein (denoted by reference numeral 2800) is described. Here, the copy deactivation message 2810 can be transmitted in MAC Control Element (CE) format. Furthermore, an indication that the message is a copy deactivation message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a copy deactivation message can be included in the ID field. Alternatively, a specific message can include an indication that the message is a copy deactivation message. Furthermore, CC information for stopping packet copying can be included in the message and sent to the radio bearer. In this case, packet copying can be stopped by deactivating a logical channel, wherein the logical channel enables transmission via the corresponding CC (or a logical channel mapped to the corresponding CC). Additionally, such a message can also be transmitted in DCI format.

[0126] Figure 29 This is a diagram illustrating another format of the group copy activation / deactivation message according to an embodiment of this disclosure (indicated by reference numeral 2900). Figure 29 In this context, a replication activation / deactivation message 2910 can be transmitted in MAC CE format. Furthermore, an indication that the message is a replication activation / deactivation message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Meanwhile, Figure 29 In one embodiment shown, group replication is enabled / disabled or activated / deactivated based on the replication index. That is, as... Figure 29As shown, the replication activation / deactivation message 2910 may include replication indices I1, I2, ..., and I8, and each replication index may have a value of 1 (activation) or 0 (deactivation), the meanings of which can be configured to be opposite. As described above, packet replication is activated or deactivated based on a bitmap of replication indices, thereby enabling packet replication activation / deactivation relative to multiple radio bearers / logical channels / CCs.

[0127] Figure 30 A diagram (as indicated by reference numeral 3000) illustrates a radio bearer configuration message for packet replication according to another embodiment of this disclosure. Figure 30 In the radio bearer configuration message shown, a replication index is assigned to each replicated radio bearer. In this case, if in Figure 29 If the replication index value described in the document is configured to 1 to indicate activation, then packet replication of the corresponding replicated radio bearer is activated.

[0128] Figure 31 A diagram (as indicated by reference numeral 3100) illustrates a radio bearer configuration message for packet replication according to another embodiment of this disclosure. Figure 31 In the radio bearer configuration message shown, a replication index is assigned to each logical channel. In this case, if in Figure 29 When the replication index value described in the document is configured to 1 to indicate activation, packet replication for the corresponding logical channel is activated. Conversely, if the replication index value is configured to 0 to indicate deactivation, packet replication for the corresponding logical channel is deactivated.

[0129] Figure 32 A diagram (denoted by reference numeral 3200) illustrates another format of a packet replication activation message according to another embodiment of this disclosure. Here, the replication activation message 3210 can be transmitted in MAC Control Element (CE) format. Furthermore, an indication that the message is a replication activation message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a replication activation message can be included in the ID field. Alternatively, a specific message can include an indication that the message is a replication activation message. Additionally, the ID of the radio bearer for which packet replication is permitted can also be included separately in the replication activation message and then transmitted. Here, packet replication can be performed on data packets transmitted via the respective radio bearer. Additionally, such a message can also be transmitted in DCI format.

[0130] Figure 33A diagram (denoted by reference numeral 3300) illustrates another format of a packet copy deactivation message according to an embodiment of the present disclosure. Here, the copy deactivation message 3310 can be transmitted in MAC Control Element (CE) format. Furthermore, an indication that the message is a copy deactivation message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a copy deactivation message can be included in the ID field. Alternatively, a specific message can include an indication that the message is a copy deactivation message. Additionally, the ID of the radio bearer for which packet copying is stopped can also be included separately in the copy deactivation message and then transmitted. Here, packet copying can be stopped / interrupted for data packets transmitted via the corresponding radio bearer. Additionally, such a message can also be transmitted in DCI format.

[0131] Figure 34 A diagram (denoted by reference numeral 3400) illustrates another format of a packet replication activation message according to an embodiment of this disclosure. Here, the replication activation message 3410 can be transmitted in MAC Control Element (CE) format. Furthermore, an indication that the message is a replication activation message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a replication activation message can be included in the ID field. Alternatively, a specific message can include an indication that the message is a replication activation message. Additionally, the transmitted replication activation message can include multiple logical channel IDs and an E field for each logical channel ID. When a specific E field has a value of 1 (or 0), the logical channel ID corresponding to the corresponding E field can be added to the next byte. In this embodiment, a radio bearer ID instead of multiple logical channel IDs can be included in the replication activation message. Alternatively, such a message can also be transmitted in DCI format.

[0132] Figure 35A diagram illustrating another format of a packet copy deactivation message according to an embodiment of this disclosure is shown (as indicated by reference numeral 3500). Here, the copy deactivation message 3510 can be transmitted in MAC Control Element (CE) format. Furthermore, an indication that the message is a copy deactivation message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a copy deactivation message can be included in the ID field. Alternatively, a specific message can include an indication that the message is a copy deactivation message. Additionally, the transmitted copy deactivation message can include multiple logical channel IDs and an E field for each logical channel ID. When a particular E field has a value of 1 (or 0), the logical channel ID corresponding to the corresponding E field can be added to the next byte. In this embodiment, a radio bearer ID, instead of multiple logical channel IDs, can be included in the copy deactivation message. Alternatively, such a message can also be transmitted in DCI format.

[0133] Figure 36 A diagram illustrating the format of a message that dynamically changes the mapping relationship between a logical channel and a CC according to an embodiment of this disclosure (as shown by reference numeral 3600). Here, a duplicated carrier mapping message 3610 can be transmitted in MAC control element (CE) format. Furthermore, an indication that the message is a duplicated carrier mapping message can be included in the Logical Channel ID (LCID) portion of the transmitted MAC CE. Alternatively, if the message includes an ID field in addition to the LCID, an indication that the message is a duplicated carrier mapping message can be included in the ID field. Alternatively, a specific message can include an indication that the message is a duplicated carrier mapping message.

[0134] Meanwhile, the replicated carrier mapping message 3610 is a message used to dynamically change the mapping between the logical channel and the carrier in which packet replication is performed, and as... Figure 36 As shown, the replicated carrier mapping message can include the Ci value (i = 1, 2, 3, ...) of each of multiple CCs. When the Ci value is 0, the corresponding CC is used in the primary logical channel, and when the Ci value is 1, the corresponding CC is used in the secondary logical channel. The terminal can receive... Figure 36 The duplicate carrier mapping message 3610 is used to change the mapping between the logical channel and the CC. However, even if the mapping between the logical channel and the CC changes, ongoing retransmissions (e.g., HARQ) in a particular logical channel can proceed as is.

[0135] Figure 37 An embodiment of the configuration process for initiating group replication is shown (as indicated by reference numeral 3700 in the accompanying drawings). Figure 37In the illustrated embodiment, the terminal determines whether the previously configured triggering conditions for a measurement report are met and measures the reference signal (RS), etc. (S3710). Here, if the measured value meets the triggering conditions (S3720), the terminal sends a measurement report message to the base station (S3730), and based on this, the base station instructs the configuration of the radio bearer to perform packet replication (S3740). This configuration can be... Figure 9 The message format in the text, and can be applied Figure 9 Certain fields in the [database name]. Upon receiving a message, the terminal and base station can configure the radio bearer to perform packet replication (S3750). The bearer format can be [format missing]. Figures 3 to 8 One of the formats described in [the document / document].

[0136] Figure 38 A diagram of a terminal according to an embodiment of the present disclosure is shown (indicated by reference numeral 3800).

[0137] See Figure 38 Terminal 3800 may include transceiver 3810 and controller 3830. Controller 3830 may include at least one processor. Transceiver 3810 and controller 3830 may be electrically connected to each other. Controller 3830 may control transceiver 3810 to send or receive signals. The transmission and / or reception of signals, information, messages, etc. by controller 3830 can be understood to cause controller 3830 to control transceiver 3810 to send and / or receive signals, information, messages, etc.

[0138] Terminal 3800 can send and / or receive signals via transceiver 3810. Controller 3830 can control the overall operation of terminal 3800. Furthermore, controller 3830 can control signals already transmitted via... Figures 1 to 37 The description of the terminal operation.

[0139] Figure 39 A diagram of a base station according to an embodiment of the present disclosure is shown (as indicated by reference numeral 3900).

[0140] See Figure 39 The base station 3900 may include a transceiver 3910 and a controller 3930. The controller 3930 may include at least one processor. The transceiver 3910 and the controller 3930 may be electrically connected to each other. The controller 3930 may control the transceiver 3910 to transmit or receive signals. The controller 3930's transmission and / or reception of signals, information, messages, etc., can be understood to cause the controller 3930 to control the transceiver 3910 to transmit and / or receive signals, information, messages, etc.

[0141] Base station 3900 can transmit and / or receive signals via transceiver 3910. Controller 3930 can control the overall operation of base station 3900. Furthermore, controller 3930 can control signals already transmitted via... Figures 1 to 37 The operation of the base station is described.

[0142] Figure 40 An embodiment of a carrier structure for grouped replication is shown (as indicated by reference numeral 4000). Figure 40 In the illustrated embodiment, a radio bearer is configured to allow packet replication, and the radio bearer ID value is configured as x. Typically, one or more signaling radio bearers (SRBs) and data radio bearers can be provided between the base station and the terminal. Figure 40 In the illustrated embodiment, a PDCP device (or entity) of a radio bearer copies a PDCP protocol data unit (PDU) and then sends the copied PDCP PDU to different RLC devices for processing. The RLC devices are mapped to logical channels respectively. Figure 40 In the illustrated embodiment, each logical channel ID is represented by y1 4010 and y2 4020.

[0143] Here, for efficient packet transmission, mapping to cells is necessary. In other words, by mapping logical channels to cells, it's possible to specify restrictions on cells that can transmit data on specific logical channels. Such cells can be replaced by component carriers (CC), bandwidth portions (BWP), etc. Figure 40 In the illustrated embodiment, logical channel 4010 with logical channel ID y1 is mapped to PCell (or PSCell or PSCell with auxiliary cell group) and SCell 2, and logical channel 4020 with logical channel ID y2 is mapped to SCell 3. As described above, logical channels and cells are mapped to each other, thus preventing copied data packets from being sent to the same cell (or the same CC, the same BWP) even if data packets are multiplexed in the MAC device (entity). In other words, two or more copies of data packets are not included in the same MAC PDU, and the original PDCP PDU and the copied PDCP PDU are not transmitted in the same transport block.

[0144] Here, regarding the bearer that allows needles to replicate in groups, it can be configured as already... Figure 5 , 6The primary logical channel and secondary logical channel are described in sections 9, 30, and 31. Regardless of the activation of packet replication, the primary logical channel always transmits / receives data packets. However, the secondary logical channel only transmits / receives packets when packet replication is activated. That is, when packet replication is activated, the same PDCP PDU is transmitted through both the primary and secondary logical channels. Here, the PDCP PDUs already transmitted through the primary and secondary logical channels can be referred to as the original PDCP PDU and the copied PDCP PDU, respectively. When packet replication is deactivated, PDCP PDUs are transmitted only through the primary logical channel. When packet replication is deactivated, the secondary logical channel can be re-established by the RLC device. Whether a specific logical channel is a primary or secondary logical channel can be specified by the base station based on RRC configuration, etc., but rules can be defined to make the above determination when such configuration is not required. In the packet replication structure, one of the following rules can be used to determine the primary logical channel.

[0145] - The logical channel with the smallest logical channel ID value is determined as the primary logical channel. If three or more logical channels exist, the logical channel with the smallest logical channel ID is determined as the primary logical channel. The remaining logical channels are determined as auxiliary logical channels.

[0146] The logical channel with the largest logical channel ID is designated as the primary logical channel. If three or more logical channels exist, the logical channel with the largest logical channel ID is designated as the primary logical channel. The remaining logical channels are designated as secondary logical channels.

[0147] - In cells that have been mapped to logical channels, logical channels with PCells are designated as primary logical channels. The remaining logical channels are designated as secondary logical channels.

[0148] - Logical channels with PCell or PSCell in cells that have already been mapped to logical channels are designated as primary logical channels. The remaining logical channels are designated as secondary logical channels.

[0149] - Logical channels with PCell or PSCell in cells already mapped to logical channels are designated as primary logical channels. If the primary logical channel is not determined by the above rules, then the logical channel whose minimum SCell index value among the SCells mapped to the logical channel is less than the minimum SCell index value of other logical channels is designated as the primary logical channel. The remaining logical channels are designated as secondary logical channels.

[0150] - In cells already mapped to logical channels, logical channels with PCells or PSCells are designated as primary logical channels. If the primary logical channel is not determined according to the above rules, then the logical channel whose maximum SCell index value among the SCells mapped to the logical channel is greater than the maximum SCell index value of other logical channels is designated as the primary logical channel. The remaining logical channels are designated as secondary logical channels.

[0151] Figure 41 The diagram illustrates the processing procedure when a packet corresponding to a bearer that allows packet replication is received (as shown by reference numeral 4100). When a packet is received (S4110), if packet replication is active, the receiver sends the packet to the corresponding logical channel for processing (S4120, S4130). If packet replication is deactivated, the receiver can determine whether the packet corresponds to the primary logical channel (S4120, S4140), and if the packet is the primary logical channel, the receiver sends the packet to the corresponding logical channel and performs processing (S4130). Otherwise, the packet can be identified as a packet for an auxiliary logical channel, and the packet is discarded and not transmitted through the logical channel (S4150).

[0152] Figure 42 The MAC sub-header format is shown (as indicated by reference numeral 4200 in the attached figure). The MAC sub-header informs information about MAC layer data, known as MAC Service Data Units (SDUs). The MAC sub-header may include reserved fields (R), format fields (F), logical channel ID fields (LCID), length fields (L), etc. The R field is a reserved field and is typically configured to zero, which is the default value. The F field indicates the length of the reserved field. The LCID field indicates the logical channel ID (MAC SDU) of the data. The L field indicates the length of the MACSDU. Generally, the above values ​​should be configured correctly; if unconfigured values ​​(unused values, invalid values) are configured, a data packet failure may be considered. For example, if the R field is configured to 1, it can be treated as an unused value.

[0153] Figure 43 The process by which the receiver processes a packet upon receipt is shown (as indicated by reference numeral 4300 in the attached figure). Figure 43An embodiment is shown in which processing is performed by the MAC device (MAC entity) upon receiving a MAC PDU. The received MAC PDU may include a MAC SDU (S4310). Here, the MAC PDU may include at least one unused value. At this point, it can be determined that it includes an SDU or subheader with the corresponding value. If the SDU may not be correctly identified, the entire received MAC PDU can be discarded. Otherwise, if the MAC SDU can be identified, it is checked whether the MAC SDU or subheader includes an unused value. If there is no unused value, data (SDU) is transmitted through the corresponding logical channel to perform packet processing (S4320, S4330). If an unused value is included, it is necessary to check whether the value corresponds to the LCID field used in the last RRC reconfiguration (the reconfiguration immediately preceding the most recent RRC reconfiguration) (S4320, S4340). As a result of the check, if the LCID field has been used in the recently passed RRC reconfiguration, the LCID field may be a portion generated before the latest RRC reconfiguration and may not be an error that occurred during transmission / reception. In other words, the value used in the recent reconfiguration may be a value that was not used in the latest reconfiguration. In this case, only the corresponding MAC SDU can be discarded (S4350). This may happen when an RRC reconfiguration occurs without a MAC reset or RRC reconstruction. If the unused value is the ID of the logical channel to which packet replication is deactivated, the unused value may be data generated when packet replication is activated or data sent by a transmitter whose deactivation is not identified. In the case of including the ID of the logical channel to which packet replication is allowed but which is deactivated, the operation of discarding only the corresponding MAC SDU can be performed (S4360, S4350). If unused values ​​other than those mentioned above are included, the entire MAC PDU can be discarded (S4360, S4370).

[0154] The embodiments disclosed in the specification and drawings are provided merely for ease of description and to aid in a thorough understanding of this disclosure, and are not intended to limit the scope of this disclosure. Therefore, it should be understood that all modifications and variations, or forms of modifications and variations, derived from the technical concept of this disclosure, other than those disclosed herein, fall within the scope of this disclosure.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: receiving, from a base station, first information about a first cell allowed for a first logical channel associated with packet duplication configured for a radio bearer, second information about a first sub-carrier spacing (SCS) allowed for the first logical channel, third information about a second cell allowed for a second logical channel associated with the packet duplication, and fourth information about a second SCS allowed for the second logical channel; receiving, from the base station, a first medium access control (MAC) control element (CE) indicating activation of the packet duplication; transmitting, to the base station, first uplink data for the first logical channel, wherein the first uplink data is transmitted on the first cell based on the first information by using the first SCS based on the second information; and transmitting, to the base station, second uplink data for the second logical channel, wherein the second uplink data is transmitted on the second cell based on the third information by using the second SCS based on the fourth information, wherein the second uplink data is a duplicate of the first uplink data, and the second uplink data is duplicated from the first uplink data based on the first MAC CE.

2. The method of claim 1, wherein, in case that successful delivery of data is confirmed by a first radio link control (RLC) entity associated with the first logical channel, a packet data convergence protocol (PDCP) entity of the radio bearer indicates the successful delivery of the data to a second RLC entity associated with the second logical channel. 3.The method of claim 1, further comprising: receiving, from the base station, a second MAC CE indicating deactivation of the packet duplication, wherein all duplicated data in the secondary RLC entity is flushed based on the second MAC CE. 4.The method of claim 1, wherein the first logical channel and the second logical channel are associated with one MAC entity, and the first cell and the second cell are different cells. 5.A method performed by a base station in a wireless communication system, the method comprising: transmitting, to a terminal, first information about a first cell allowed for a first logical channel associated with packet duplication configured for a radio bearer, second information about a first sub-carrier spacing (SCS) allowed for the first logical channel, third information about a second cell allowed for a second logical channel associated with the packet duplication, and fourth information about a second SCS allowed for the second logical channel; transmitting, to the terminal, a first medium access control (MAC) control element (CE) indicating activation of the packet duplication; receiving, from the terminal, first uplink data for the first logical channel, wherein the first uplink data is received on the first cell based on the first information by using the first SCS based on the second information; and receiving, from the terminal, second uplink data for the second logical channel, wherein the second uplink data is received on the second cell based on the third information by using the second SCS based on the fourth information, wherein the second uplink data is a duplicate of the first uplink data, and the second uplink data is duplicated from the first uplink data based on the first MAC CE.

6. The method of claim 5, wherein, The first and second logical channels are associated with one MAC entity, and the first and second cells are different cells. 7.The method of claim 5, further comprising: transmitting, to the terminal, a second MAC CE indicating deactivation of the packet duplication, wherein all duplicated data in the secondary RLC entity is flushed based on the second MAC CE. 8.A terminal in a wireless communication system, the terminal comprising: a transceiver configured to transmit and receive signals; and a controller coupled with the transceiver and configured to: receive, from a base station, first information about a first cell allowed for a first logical channel associated with packet duplication configured for a radio bearer, second information about a first sub-carrier spacing (SCS) allowed for the first logical channel, third information about a second cell allowed for a second logical channel associated with the packet duplication, and fourth information about a second SCS allowed for the second logical channel, receive, from the base station, a first medium access control (MAC) control element (CE) indicating activation of the packet duplication, transmitting first uplink data of a first logical channel to the base station, wherein, transmit first uplink data on the first cell based on the first information by using the first SCS based on the second information, and transmit, to the base station, second uplink data of the second logical channel, wherein the second uplink data is transmitted on the second cell based on the third information by using the second SCS based on the fourth information, wherein the second uplink data is a duplication of the first uplink data, and the second uplink data is duplicated from the first uplink data based on the first MAC CE.

9. The terminal according to claim 8, wherein in case of successful delivery of data is confirmed by a first radio link control (RLC) entity associated with the first logical channel, a packet data convergence protocol (PDCP) entity of the radio bearer indicates the successful delivery of the data to a second RLC entity associated with the second logical channel.

10. The terminal of claim 8, wherein, the controller is further configured to: receive, from the base station, a second MAC CE indicating deactivation of the packet duplication, and wherein all duplicated data in the secondary RLC entity is flushed based on the second MAC CE.

11. The terminal of claim 8, wherein, The first and second logical channels are associated with one MAC entity, and the first and second cells are different cells. 12.A base station in a wireless communication system, the base station comprising: a transceiver configured to transmit and receive signals; and a controller coupled with the transceiver and configured to: transmit, to a terminal, first information about a first cell allowed for a first logical channel associated with packet duplication configured for a radio bearer, second information about a first sub-carrier spacing (SCS) allowed for the first logical channel, third information about a second cell allowed for a second logical channel associated with the packet duplication, and fourth information about a second SCS allowed for the second logical channel, transmit, to the terminal, a first medium access control (MAC) control element (CE) indicating activation of the packet duplication, receiving first uplink data for a first logical channel from a terminal, wherein, receive first uplink data on the first cell based on the first information by using the first SCS based on the second information, and transmit, to the base station, second uplink data of the second logical channel, wherein the second uplink data is transmitted on the second cell based on the third information by using the second SCS based on the fourth information, receiving, from the terminal, second uplink data for a second logical channel, wherein the second uplink data is received on a second cell based on third information using a second SCS based on fourth information, wherein the second uplink data is a duplication of the first uplink data, and the second uplink data is duplicated from the first uplink data based on the first MAC CE.

13. The base station of claim 12, wherein, the controller is further configured to: send, to the terminal, a second MAC CE indicating deactivation of the packet duplication, and wherein all duplicated data in the secondary RLC entity is flushed based on the second MAC CE. 14.The base station of claim 12, wherein the first logical channel and the second logical channel are associated with one MAC entity, and the first cell and the second cell are different cells.

Images