U.S. patent application number 16/571821 was filed with the patent office on 2020-03-19 for method and apparatus for transmitting packet in wireless communication system.
The applicant listed for this patent is Samsung Electronics Co., Ltd.. Invention is credited to Sangkyu BAEK, Hyunjeong KANG.
Application Number | 20200092944 16/571821 |
Document ID | / |
Family ID | 69774547 |
Filed Date | 2020-03-19 |
View All Diagrams
United States Patent
Application |
20200092944 |
Kind Code |
A1 |
BAEK; Sangkyu ; et
al. |
March 19, 2020 |
METHOD AND APPARATUS FOR TRANSMITTING PACKET IN WIRELESS
COMMUNICATION SYSTEM
Abstract
A method, performed by a terminal, of transmitting and receiving
a signal in a wireless communication system is provided. The method
includes setting a value of a Next_Packet Data Convergence Protocol
(PDCP)_RX_sequence number (SN) variable as an initial value, the
Next_PDCP_RX_SN variable indicating a predicted SN of PDCP data to
be received, receiving first PDCP data from a transmission entity
after setting the initial value, and setting the value of the
Next_PDCP_RX_SN variable as a value obtained by adding a first
setting value to a value of the SN of the PDCP data.
Inventors: |
BAEK; Sangkyu; (Suwon-si,
KR) ; KANG; Hyunjeong; (Suwon-si, KR) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Samsung Electronics Co., Ltd. |
Suwon-si |
|
KR |
|
|
Family ID: |
69774547 |
Appl. No.: |
16/571821 |
Filed: |
September 16, 2019 |
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04W 4/40 20180201; H04W
80/02 20130101; H04L 47/34 20130101; H04W 28/06 20130101; H04L
1/1642 20130101; H04W 80/08 20130101 |
International
Class: |
H04W 80/08 20060101
H04W080/08; H04L 1/16 20060101 H04L001/16; H04W 4/40 20060101
H04W004/40; H04W 28/06 20060101 H04W028/06; H04W 80/02 20060101
H04W080/02 |
Foreign Application Data
Date |
Code |
Application Number |
Sep 14, 2018 |
KR |
10-2018-0110469 |
Claims
1. A method, performed by a terminal, of transmitting and receiving
a signal in a wireless communication system, the method comprising:
setting a value of a Next_Packet Data Convergence Protocol
(PDCP)_RX_sequence number (SN) variable as an initial value, the
Next_PDCP_RX_SN variable indicating a predicted SN of PDCP data to
be received; receiving first PDCP data from a transmission entity
after setting the initial value; and setting the value of the
Next_PDCP_RX_SN variable as a value obtained by adding a first
setting value to a value of the SN of the first PDCP data.
2. The method of claim 1, wherein the first setting value is 1.
3. The method of claim 1, further comprising: setting a value of a
Last_Submitted_PDCP_RX_SN variable, which indicates an SN of PDCP
data most recently transferred to an upper layer, as a value
obtained by subtracting a second setting value from a value of the
SN of the first PDCP data.
4. The method of claim 3, further comprising: starting a PDCP
reordering timer based on the value of the Next_PDCP_RX_SN variable
and the value of the Last_Submitted_PDCP_RX_SN variable.
5. The method of claim 4, further comprising: setting a value of a
Reordering_PDCP_RX_COUNT variable by using the value of the
Next_PDCP_RX_SN variable, the Reordering_PDCP_RX_COUNT variable
being used by the PDCP reordering timer.
6. The method of claim 1, wherein the PDCP data is transmitted from
the transmission entity by using a vehicle-to-everything (V2X)
communication scheme.
7. A terminal for transmitting and receiving a signal in a wireless
communication system, the terminal comprising: a transceiver; and
at least one processor configured to: set a value of a Next_Packet
Data Convergence Protocol (PDCP)_RX_sequence number (SN) variable
as an initial value, the Next_PDCP_RX_SN variable indicating a
predicted SN of PDCP data to be received, receive, from a
transmission entity via the transceiver, first PDCP data after
setting the initial value, and set the value of the Next_PDCP_RX_SN
variable as a value obtained by adding a first setting value to a
value of the SN of the first PDCP data.
8. The terminal of claim 7, wherein the first setting value is
1.
9. The terminal of claim 7, wherein the at least one processor is
further configured to set a value of a Last_Submitted_PDCP_RX_SN
variable, which indicates an SN of PDCP data most recently
transferred to an upper layer, as a value obtained by subtracting a
second setting value from a value of the SN of the first PDCP
data.
10. The terminal of claim 9, wherein the at least one processor is
further configured to start a PDCP reordering timer, based on the
value of the Next_PDCP_RX_SN variable and the value of the
Last_Submitted_PDCP_RX_SN variable.
11. The terminal of claim 10, wherein the at least one processor is
further configured to set a value of a Reordering_PDCP_RX_COUNT
variable by using the value of the Next_PDCP_RX_SN variable, the
Reordering_PDCP_RX_COUNT variable being used by the PDCP reordering
timer.
12. The terminal of claim 7, wherein the PDCP data is transmitted
from the transmission entity by using a vehicle-to-everything (V2X)
communication scheme.
Description
CROSS-REFERENCE TO RELATED APPLICATION(S)
[0001] This application is based on and claims priority under 35
U.S.C. .sctn. 119(a) of a Korean patent application number
10-2018-0110469, filed on Sep. 14, 2018, in the Korean Intellectual
Property Office, the disclosure of which is incorporated by
reference herein in its entirety.
BACKGROUND
1. Field
[0002] The disclosure relates to a wireless communication system,
and in particular, to a method and an apparatus for providing a
service in a wireless communication system. More particularly, the
disclosure relates to a method and an apparatus for transmitting a
packet in a wireless communication system.
2. Description of Related Art
[0003] To meet increasing demand with respect to an increase in
wireless data traffic after the commercialization of 4th generation
(4G) communication systems, efforts have been made to develop 5th
generation (5G) or pre-5G communication systems. For this reason,
5G or pre-5G communication systems are called `beyond 4G network`
communication systems or `post long term evolution (post-LTE)`
systems. 5G communication system specified in the 3rd Generation
Partnership Project (3GPP) is called a New Radio (NR) system. To
achieve high data rates, implementation of 5G communication systems
in an ultra-high frequency or millimeter-wave (mmWave) band (e.g.,
a 60-GHz band) is being considered. To reduce path loss and
increase a transmission distance in the ultra-high frequency band
for 5G communication systems, various technologies, such as
beamforming, massive multiple-input and multiple-output (massive
MIMO), full-dimension MIMO (FD-MIMO), array antennas, analog
beamforming, and large-scale antennas are being studied, and are
applied to the NR system. To improve system networks for 5G
communication systems, various technologies, such as evolved small
cells, advanced small cells, cloud radio access networks
(Cloud-RAN), ultra-dense networks, device-to-device communication
(D2D), wireless backhaul, moving networks, cooperative
communication, coordinated multi-points (CoMP), interference
cancellation, or the like have been developed. In addition, for 5G
communication systems, advanced coding modulation (ACM)
technologies, such as hybrid frequency-shift keying (FSK) and
quadrature amplitude modulation (QAM) (FQAM) and sliding window
superposition coding (SWSC), and advanced access technologies, such
as filter bank multi-carrier (FBMC), non-orthogonal multiple access
(NOMA), and sparse code multiple access (SCMA), have been
developed.
[0004] The Internet has evolved from a human-based connection
network, where humans create and consume information, to the
Internet of things (IoT), where distributed elements, such as
objects exchange information with each other to process the
information. Internet of everything (IoE) technology has emerged,
in which the IoT technology is combined with, for example,
technology for processing big data through connection with a cloud
server. To implement the IoT, various technological elements, such
as sensing technology, wired/wireless communication and network
infrastructures, service interface technology, and security
technology are required. In recent years, technologies related to
sensor networks for connecting objects, machine-to-machine (M2M)
communication, and machine-type communication (MTC) have been
studied. In the IoT environment, intelligent Internet technology
(IT) services may be provided to collect and analyze data obtained
from connected objects to create new value in human life. As
existing information technology (IT) and various industries
converge and combine with each other, the IoT may be applied to
various fields, such as smart homes, smart buildings, smart cities,
smart cars or connected cars, smart grids, health care, smart home
appliances, advanced medical services, or the like.
[0005] Various attempts are being made to apply 5G communication
systems to the IoT network. For example, technologies related to
sensor networks, M2M communication, and MTC are being implemented
by using 5G communication technology including beamforming,
Multiple-In Multiple-Out (MIMO), and array antennas. Application of
cloud radio access network (Cloud-RAN) as the above-described big
data processing technology may be an example of convergence of 5G
communication technology and IoT technology.
[0006] Because various services are enabled to be provided due to
the aforementioned technical features and the development of
wireless communication systems, methods for effectively providing
these services are required.
[0007] The above information is presented as background information
only to assist with an understanding of the disclosure. No
determination has been made, and no assertion is made, as to
whether any of the above might be applicable as prior art with
regard to the disclosure.
SUMMARY
[0008] Aspects of the disclosure are to address at least the
above-mentioned problems and/or disadvantages and to provide at
least the advantages described below. Accordingly, an aspect of the
disclosure is to provide a method and an apparatus for providing a
service in a wireless communication system.
[0009] Additional aspects will be set forth in part in the
description which follows and, in part, will be apparent from the
description, or may be learned by practice of the presented
embodiments.
[0010] In accordance with an aspect of the disclosure, a method,
performed by a terminal, of transmitting and receiving a signal in
a wireless communication system is provided. The method includes
setting a value of a Next_Packet Data Convergence Protocol
(PDCP)_RX_sequence number (SN) variable as an initial value, the
Next_PDCP_RX_SN variable indicating a predicted SN of PDCP data to
be received, receiving first PDCP data from a transmission entity
after setting the initial value, and setting the value of the
Next_PDCP_RX_SN variable as a value obtained by adding a first
setting value to a value of the SN of the PDCP data.
[0011] In accordance with another aspect of the disclosure, a
method, performed by a PDCP layer, of transmitting a packet in a
wireless communication system is provided. The method includes
determining a value of a Quality of Service (QoS) requirement of
the packet, comparing the value of the QoS requirement of the
packet with a threshold value, determining whether duplicate packet
transmission is required, based on a result of the comparing of the
value of the QoS requirement of the packet with the threshold
value, and selectively performing the duplicate packet
transmission, based on a result of determining whether the
duplicate packet transmission is required.
[0012] Other aspects, advantages, and salient features of the
disclosure will become apparent to those skilled in the art from
the following detailed description, which, taken in conjunction
with the annexed drawings, discloses various embodiments of the
disclosure.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The above and other aspects, features, and advantages of
certain embodiments of the disclosure will be more apparent from
the following description taken in conjunction with the
accompanying drawings, in which:
[0014] FIG. 1 is a diagram illustrating a change in a radio bearer
configuration according to whether duplicate packet transmission is
to be performed according to an embodiment of the disclosure;
[0015] FIG. 2 is a flowchart illustrating a process of determining
packet duplication in a Packet Data Convergence Protocol (PDCP)
layer of a transmitter according to an embodiment of the
disclosure;
[0016] FIG. 3 is a diagram illustrating an operation process of a
transmitter in which duplicate packet transmission is deactivated
according to an embodiment of the disclosure;
[0017] FIG. 4 is a diagram illustrating an operation process of a
transmitter in which duplicate packet transmission is deactivated
according to an embodiment of the disclosure;
[0018] FIG. 5 is a diagram illustrating an operation process of a
transmitter in which duplicate packet transmission is deactivated
according to an embodiment of the disclosure;
[0019] FIG. 6 is a flowchart illustrating an operation process of a
receiver in which duplicate packet transmission is activated or
deactivated according to an embodiment of the disclosure;
[0020] FIG. 7 is a flowchart illustrating an operation process of a
receiver in which duplicate packet transmission is activated or
deactivated according to an embodiment of the disclosure;
[0021] FIG. 8 is a flowchart illustrating an operation process of a
receiver when duplicate packet transmission is deactivated
according to an embodiment of the disclosure;
[0022] FIG. 9 is a diagram illustrating an operation process of a
receiver when duplicate packet transmission is deactivated
according to an embodiment of the disclosure;
[0023] FIG. 10 is a diagram illustrating an operation process of a
receiver when duplicate packet transmission is deactivated
according to an embodiment of the disclosure;
[0024] FIG. 11 is a flowchart illustrating operations of a
transmitter and a receiver according to whether duplicate packet
transmission is to be performed according to an embodiment of the
disclosure;
[0025] FIG. 12 illustrates a block diagram of a terminal according
to an embodiment of the disclosure;
[0026] FIG. 13 illustrates a block diagram of a base station
according to an embodiment of the disclosure;
[0027] FIG. 14 is a diagram illustrating a change in a radio bearer
configuration according to whether duplicate packet transmission is
to be performed according to an embodiment of the disclosure;
[0028] FIG. 15 is a flowchart illustrating a process of determining
packet duplication, the process being performed by a PDCP layer of
a transmitter according to an embodiment of the disclosure;
[0029] FIG. 16 is a diagram illustrating a mobility scenario of a
transmitter and a receiver in vehicle communication according to an
embodiment of the disclosure;
[0030] FIG. 17 is a diagram illustrating a method of receiving a
packet, the method being performed by a PDCP layer of a receiver
according to an embodiment of the disclosure;
[0031] FIG. 18 is a diagram illustrating an operation of starting
reception, the operation being performed by a PDCP layer of a
receiver according to an embodiment of the disclosure;
[0032] FIG. 19 is a diagram illustrating an operation of starting
reception, the operation being performed by a PDCP layer of a
receiver according to an embodiment of the disclosure;
[0033] FIG. 20 is a diagram illustrating an operation performed by
a PDCP layer of a receiver when the PDCP layer of the receiver
starts reception according to an embodiment of the disclosure;
[0034] FIG. 21 is a diagram illustrating an operation of
transmitting a packet, the operation being performed by a PDCP
layer of a transmitter according to an embodiment of the
disclosure;
[0035] FIG. 22 is a diagram illustrating an operation of
transmitting a packet, the operation being performed by a PDCP
layer of a transmitter according to an embodiment of the
disclosure;
[0036] FIG. 23 is a diagram illustrating an operation of
transmitting a packet, the operation being performed by a PDCP
layer of a transmitter according to an embodiment of the
disclosure;
[0037] FIG. 24 is a diagram illustrating an operation of receiving
a packet, the operation being performed by a PDCP layer of a
receiver according to an embodiment of the disclosure;
[0038] FIG. 25 is a diagram illustrating an operation of receiving
a packet, the operation being performed by a PDCP layer of a
receiver according to an embodiment of the disclosure;
[0039] FIG. 26 illustrates a block diagram of a terminal according
to an embodiment of the disclosure; and
[0040] FIG. 27 illustrates a block diagram of a base station
according to an embodiment of the disclosure.
[0041] Throughout the drawings, like reference numerals will be
understood to refer to like parts, components, and structures.
DETAILED DESCRIPTION
[0042] The following description with reference to the accompanying
drawings is provided to assist in a comprehensive understanding of
various embodiments of the disclosure as defined by the claims and
their equivalents. It includes various specific details to assist
in that understanding but these are to be regarded as merely
exemplary. Accordingly, those of ordinary skill in the art will
recognize that various changes and modifications of the various
embodiments described herein can be made without departing from the
scope and spirit of the disclosure. In addition, descriptions of
well-known functions and constructions may be omitted for clarity
and conciseness.
[0043] For the same reason, some elements in the drawings are
exaggerated, omitted, or schematically illustrated. In addition,
the size of each element does not entirely reflect the actual size.
In the drawings, the same or corresponding elements are denoted by
the same reference numerals.
[0044] The terms and words used in the following description and
claims are not limited to the bibliographical meanings, but, are
merely used by the inventor to enable a clear and consistent
understanding of the disclosure. Accordingly, it should be apparent
to those skill in the art that the following description of various
embodiments of the disclosure is provided for illustration purpose
only and not for the purpose of limiting the disclosure as defined
by the appended claims and their equivalents.
[0045] It is to be understood that the singular forms "a," "an,"
and "the" include plural referents unless the context clearly
dictates otherwise. Thus, for example, reference to "a component
surface" includes reference to one or more of such surfaces.
[0046] It will be understood that each block of flowchart
illustrations, and combinations of blocks in the flowchart
illustrations, may be implemented by computer program instructions.
The computer program instructions may be provided to a processor of
a general-purpose computer, special purpose computer, or other
programmable data processing apparatus, such that the instructions,
which are executed via the processor of the computer or other
programmable data processing apparatus, generate means for
performing functions specified in the flowchart block or blocks.
The computer program instructions may also be stored in a computer
usable or computer-readable memory that may direct 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 memory produce an article of
manufacture including instruction means that perform the functions
specified in the flowchart block or blocks. The computer program
instructions may also be loaded onto the 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 that are executed on the computer or other
programmable apparatus provide operations for implementing the
functions specified in the flowchart block or blocks.
[0047] In addition, each block of the flowchart illustrations may
represent a module, segment, or portion of code, which includes one
or more executable instructions for performing specified logical
function(s). It should also be noted that in some alternative
implementations, the functions noted in the blocks may occur out of
the order. For example, two blocks shown in succession may in fact
be executed substantially concurrently or the blocks may sometimes
be executed in the reverse order, depending upon the functionality
involved.
[0048] The term ".about. unit", as used in the embodiment of the
disclosure refers to a software or hardware component, such as
field-programmable gate array (FPGA) or application-specific
integrated circuit (ASIC), which performs certain tasks. However,
the term ".about. unit" does not mean to be limited to software or
hardware. A unit may be configured to be in an addressable storage
medium or configured to operate one or more processors. Thus, a
unit may include, by way of example, components, such as software
components, object-oriented software components, class components,
and task components, processes, functions, attributes, procedures,
subroutines, segments of program code, drivers, firmware,
microcode, circuitry, data, databases, data structures, tables,
arrays, and variables. The functionality provided in the components
and units may be combined into fewer components and units or
further separated into additional components and units. Further,
the components and units may be implemented to operate one or more
central processing units (CPUs) in a device or a secure multimedia
card. In addition, a unit may include one or more processors in an
embodiment of the disclosure.
[0049] Throughout the disclosure, the expression "at least one of
a, b or c" indicates only a, only b, only c, both a and b, both a
and c, both b and c, all of a, b, and c, or variations thereof.
[0050] Hereinafter, terms identifying an access node, terms
indicating network entities, terms indicating messages, terms
indicating an interface between network entities, and terms
indicating various pieces of identification information, as used in
the following description, are exemplified for convenience of
explanation. Accordingly, the disclosure is not limited to terms to
be described below, and other terms indicating objects having equal
technical meanings may be used.
[0051] Hereinafter, for convenience of explanation, the disclosure
uses terms and names defined in the 3rd generation partnership
project long term evolution (3GPP LTE) standards. However, the
disclosure is not limited to the terms and names, and may also be
applied to systems following other standards. In an embodiment of
the disclosure, an evolved node B (eNB) may be interchangeably used
with a next-generation node B (gNB) for convenience of explanation.
For example, a base station (BS) described by an eNB may represent
a gNB. In an embodiment of the disclosure, the term "terminals" may
refer to not only mobile phones, narrowband Internet of Things
(NB-IoT) devices, and sensors but also other wireless communication
devices. Hereinafter, a layer may also referred to as an
entity.
[0052] FIG. 1 is a diagram illustrating a change in a radio bearer
configuration according to whether duplicate packet transmission is
to be performed according to an embodiment of the disclosure.
[0053] Referring to FIG. 1, a radio bearer 1a-10 that does not
perform duplicate packet transmission may be connected to a Packet
Data Convergence Protocol (PDCP) layer 1a-20 and a Radio Link
Control (RLC) entity 1a-30 (also referred to as the RLC1 1a-30). In
this regard, each RLC entity may correspond to a logical channel,
and the RLC1 1a-30 may correspond to a logical channel 1 (LCH1)
1a-40. When a terminal does not perform the duplicate packet
transmission, a packet that arrives at the radio bearer 1a-10 may
not be packet-duplicated by the PDCP layer 1a-20, a PDCP header may
be added thereto, and then the packet may be transferred to the RLC
entity 1a-30. In addition, an RLC header may be added to the packet
by the RLC entity 1a-30, and the packet may be transmitted through
the LCH1 1a-40. In an embodiment of the disclosure, an RLC entity
of a receiver may identify an RLC entity of each packet by using a
logical channel identifier (LCID) included in each Medium Access
Control (MAC) subheader, such that the packet may be transferred to
the RLC entity 1a-30. After the RLC header is removed, the packet
may be transferred to the PDCP layer 1a-20 and thus the PDCP header
may be removed.
[0054] In an embodiment of the disclosure, duplicate packet
transmission may be activated due to various reasons including
settings of a base station, self-determination by the terminal, or
the like. In this regard, a radio bearer 1a-50 may be connected to
a PDCP layer 1a-60 and at least two RLC entities 1a-70 and 1a-80
(also referred to as the RLC1 1a-70 and the RLC2 1a-80). In an
embodiment of FIG. 1, two RLC entities are shown as an example, but
the number of RLC entities in the disclosure is not limited thereto
and may extend to two or more RLC entities. Each RLC entity may
correspond to a logical channel. In an embodiment of FIG. 1, the
RLC1 1a-70 and the RLC2 1a-80 may correspond to a LCH1 1a-90 and a
LCH2 1a-100 (also referred to as the LCH 1a-90 and the LCH 1a-100),
respectively. When the terminal performs the duplicate packet
transmission, packet duplication may be performed on a packet by
the PDCP layer 1a-60, the packet arriving at the radio bearer
1a-50, and a PDCP header may be added to each of the packets.
Afterward, the respective packets may be transferred to the RLC
entities 1a-70 and 1a-80. The RLC entities 1a-70 and 1a-80 may each
add an RLC header to the respective packets, and may transmit the
packets through the LCHs 1a-90 and 1a-100, respectively. An RLC
entity of a receiver may identify an RLC entity of each packet by
using an LCID included in each MAC subheader, such that the
respective packets may be transferred to the RLC entities 1a-70 and
1a-80. After the RLC header of each of the packets is removed, the
packets may be transferred to the PDCP layer 1a-60 and thus the
PDCP header may be removed.
[0055] In an embodiment of the disclosure, because a same packet
may be received from each of RLC entities, a PDCP layer may perform
a duplication detection function and thus may prevent the same
packet from being transferred to an upper layer several times. In
addition, because a time when a packet is transferred from each RLC
entity is not regular, the PDCP layer may perform a reordering
function so as to allow packets to be transferred from a PDCP layer
of the receiver to an upper layer according to an order, the
packets being transmitted from a PDCP layer of a transmitter. For
the duplication detection or the reordering function which is
described above, it is required for the PDCP layer of the receiver
to identify an order of packets, and thus, when duplicate packet
transmission is performed, a sequence number (SN) of a PDCP layer
may be included in a PDCP header.
[0056] FIG. 2 is a flowchart illustrating a process of determining
packet duplication in a PDCP layer of a transmitter according to an
embodiment of the disclosure.
[0057] Referring to FIG. 2, a packet that arrives at the PDCP layer
of the transmitter may have a Quality of Service (QoS) requirement
to be processed by the packet. The QoS requirement may include a
function index, such as a reliability level, a packet error rate, a
delay time, or the like, or may correspond to a representative
value indicating the QoS requirement.
[0058] In an embodiment of FIG. 2, as an example, a method of
determining whether to perform packet duplication, based on a ProSe
Per-Packet Reliability (PPPR) used in vehicle-to-everything (V2X)
communication, is illustrated. In the V2X communication, a PPPR
value may represent a QoS requirement of a packet to be
transmitted.
[0059] In operation 1b-10, when a packet arrives at the PDCP layer
of the transmitter, the PDCP layer may determine a PPPR value of
the packet.
[0060] In operation 1b-20, the PPPR value of the packet may be
compared with a threshold value at which duplicate packet
transmission is requested.
[0061] When the PPPR value of the packet is equal to or greater
than the threshold value at which the duplicate packet transmission
is requested, in operation 1b-30, the PDCP layer of the transmitter
may determine that the duplicate packet transmission is requested.
The PDCP layer of the transmitter may duplicate the packet and may
transfer packets to at least two RLC entities for transmission.
[0062] When the PPPR value of the packet is less than the threshold
value at which the duplicate packet transmission is performed, in
operation 1b-40, the PDCP layer of the transmitter may determine
that the duplicate packet transmission is not requested. The PDCP
layer of the transmitter may not duplicate the packet and may
transfer the packet to only one RLC entity.
[0063] FIG. 3 is a diagram illustrating an operation process of a
transmitter in which duplicate packet transmission is deactivated
according to an embodiment of the disclosure.
[0064] Referring to FIG. 3, after the duplicate packet transmission
is activated, a duplication detection function or a reordering
function of a receiver may be required. Because it is required for
a PDCP layer of the receiver to identify an order of a packet, when
the duplicate packet transmission is performed, a PDCP layer may
allocate a SN to be included in a PDCP header.
[0065] When the duplicate packet transmission is deactivated or is
not configured, the PDCP layer of the receiver may not use the
duplication detection function and the reordering function.
Therefore, the SN of the PDCP layer may not be necessarily
allocated. However, because a format of a PDCP header is fixed, and
a field corresponding to an SN exists in the PDCP header, when
packet duplication is deactivated or is not configured, an SN of a
corresponding packet may be set as 0 and then may be
transmitted.
[0066] Referring to FIG. 3, an example is illustrated, in which the
transmitter continuously performs duplicate packet transmission
(1c-10, 1c-20, and 1c-30), and after transmission of a packet 1c-40
corresponding to an SN of 20002, the duplicate packet transmission
is not required any more. For packets thereafter, the duplicate
packet transmission is not performed, and thus the transmitter may
transmit packets 1c-50, 1c-60, and 1c-70 by setting SNs as 0.
[0067] FIG. 4 is a diagram illustrating an operation process of a
transmitter in which duplicate packet transmission is deactivated
according to an embodiment of the disclosure.
[0068] Referring to FIG. 4, after the duplicate packet transmission
is activated, a duplication detection function or a reordering
function of a receiver may be required. Because it is required for
a PDCP layer of the receiver to identify an order of a packet, when
the duplicate packet transmission is performed, a PDCP layer may
allocate an SN to be included in a PDCP header.
[0069] When the duplicate packet transmission is deactivated or is
not configured, the PDCP layer of the receiver may not use the
duplication detection function and the reordering function.
Therefore, the SN of the PDCP layer may not be necessarily
allocated. However, because a format of a PDCP header is fixed, and
a field corresponding to an SN exists in the PDCP header, when
packet duplication is deactivated or is not configured, an SN of a
corresponding packet may be set as 0 and then may be
transmitted.
[0070] In an embodiment of the disclosure, in a gap between a time
when the duplicate packet transmission is performed and a time when
the duplicate packet transmission is not performed, the transmitter
may transmit, to the receiver, a message 1d-100 indicating that
packet duplication is not to be performed any more. When the
receiver receives the message 1d-100, the receiver may not perform
a receiver operation corresponding to the duplicate packet
transmission.
[0071] Referring to FIG. 4, an example is illustrated, in which the
transmitter continuously performs the duplicate packet transmission
(1d-10, 1d-20, and 1d-30), and after transmission of a packet 1d-40
corresponding to an SN of 20002, the duplicate packet transmission
is not required any more. After the transmitter transmits the
message 1d-100 indicating deactivation, the transmitter does not
perform the duplicate packet transmission on packets after the
message 1d-100, and thus may transmit packets 1d-50, 1d-60, and
1d-70 by setting SNs as 0. In an embodiment of the disclosure, in a
case where an SN is continuously set as a non-zero value even when
the packet duplication is deactivated, the receiver may not perform
a receiver operation for the duplicate packet transmission,
according to the message 1d-100 indicating deactivation. In an
embodiment of the disclosure, the receiver may perform an operation
according to deactivation of the duplicate packet transmission.
[0072] FIG. 5 is a diagram illustrating an operation process of a
transmitter in which duplicate packet transmission is deactivated
according to an embodiment of the disclosure.
[0073] Referring to FIG. 5, after the duplicate packet transmission
is activated, a duplication detection function or a reordering
function of a receiver may be required. Because it is required for
a PDCP layer of the receiver to identify an order of a packet, when
the duplicate packet transmission is performed, an SN of a PDCP
layer may be included in a PDCP header. When the duplicate packet
transmission is deactivated or is not configured, the PDCP layer of
the receiver may not use the duplication detection function and the
reordering function. Therefore, the SN of the PDCP layer may not be
necessarily allocated.
[0074] However, because a format of a PDCP header is fixed, and a
field corresponding to an SN exists in the PDCP header, when packet
duplication is deactivated or is not configured, SNs of
corresponding packets may be sequentially allocated but the
receiver may not need to use information about the SNs for
duplication detection or reordering.
[0075] In an embodiment of the disclosure, a 1-bit indicator
1e-110, 1e-120, 1e-130, 1e-140, 1e-150, 1e-160, or 1e-170
indicating whether a packet of a corresponding SN is duplicated and
duplicate transmitted when transmitting the packet may be included
in a PDCP header. In an embodiment of the disclosure, the 1-bit
indicator may be referred to as a packet duplication indicator. The
receiver may recognize deactivation of packet duplication by
interpreting the 1-bit indicator, and may not perform the receiver
operation for duplicate packet transmission. In an embodiment of
the disclosure, the receiver may perform an operation according to
deactivation of the duplicate packet transmission.
[0076] Referring to FIG. 5, an example is illustrated, in which the
transmitter continuously performs the duplicate packet transmission
(1e-10, 1e-20, and 1e-30), and after transmission of a packet 1e-40
corresponding to an SN of 20002, the duplicate packet transmission
is not required any more. The transmitter may not perform the
duplicate packet transmission on packets 1e-50, 1e-60, and 1e-70
thereafter, and may transmit the packets 1e-50, 1e-60, and 1e-70 by
including indicators 1e-150, 1e-160, and 1e-170 therein, the
indicators 1e-150, 1e-160, and 1e-170 indicating the duplicate
packet transmission is not performed.
[0077] FIG. 6 is a flowchart illustrating an operation process of a
receiver in which duplicate packet transmission is activated or
deactivated according to an embodiment of the disclosure.
[0078] Referring to FIG. 6, the operation process of a receiver may
be applied to a receiver operation corresponding to a transmitter
operation of FIG. 3 or 4.
[0079] In operation 1f-10, a PDCP layer of the receiver receives a
packet. In this regard, the PDCP layer of the receiver may read
information in a PDCP header.
[0080] In operation 1f-20, it is determined whether a packet of
which SN is 0 is received.
[0081] When the packet of which SN is 0 is received, in operation
1f-30, the receiver may determine that duplicate packet
transmission is deactivated with respect to the packet or a radio
bearer from which the packet is transmitted. When it is determined
that the duplicate packet transmission is deactivated, the PDCP
layer of the receiver of a terminal may perform a receiver
operation corresponding to a state in which packet duplication is
deactivated or is not configured. For example, the receiver may not
use a duplication detection function or a reordering function of
the PDCP layer. In an embodiment of the disclosure, the receiver
may perform an operation of deactivating the packet duplication.
For example, the receiver may perform an operation of starting a
reordering timer.
[0082] When an SN of a received packet is not 0, in operation
1f-40, the receiver may determine that the duplicate packet
transmission is activated and performed.
[0083] FIG. 7 is a flowchart illustrating an operation process of a
receiver in which duplicate packet transmission is activated or
deactivated according to an embodiment of the disclosure.
[0084] Referring to FIG. 7, an operation process of the receiver
may be applied to a receiver operation corresponding to a
transmitter operation of FIG. 5.
[0085] In operation 1g-10, the PDCP layer of the receiver receives
a packet. In this regard, the PDCP layer of the receiver may read
information in a PDCP header.
[0086] In operation 1g-20, the receiver may determine whether the
packet duplication indicator 1e-110, 1e-120, 1e-130, 1e-140,
1e-150, 1e-160, or 1e-170 of the packet indicates that duplicate
packet transmission is in a deactivation state.
[0087] When a packet duplication indicator of a received packet
indicates the deactivation state, in operation 1g-30, the PDCP
layer of the receiver may determine that duplicate packet
transmission is deactivated with respect to the packet or a radio
bearer from which the packet is transmitted. Afterward, the PDCP
layer of the receiver of the terminal may perform a receiver
operation corresponding to a state in which packet duplication is
deactivated or is not configured. For example, the receiver may not
use a duplication detection function or a reordering function of
the PDCP layer. In an embodiment of the disclosure, the receiver
may perform an operation of deactivating the packet duplication.
For example, the receiver may perform an operation of initiating a
reordering timer.
[0088] When the packet duplication indicator of the received packet
does not indicate the deactivation state, in operation 1g-40, the
PDCP layer of the receiver may determine that the packet has been
duplicated by and duplicate transmitted from a PDCP layer of a
transmitter. In addition, the receiver may determine that the
packet duplication is activated at least up to a time when the
packet is transmitted.
[0089] FIG. 8 is a flowchart illustrating an operation process of a
receiver when duplicate packet transmission is deactivated
according to an embodiment of the disclosure.
[0090] Referring to FIG. 8, in operation 1h-10, the PDCP layer of
the receiver receives a packet.
[0091] In operation 1h-20, the PDCP layer of the receiver may
determine whether duplicate packet transmission is deactivated. In
an embodiment of the disclosure, the PDCP layer of the receiver may
determine whether duplicate packet transmission is deactivated, by
using the method described above with reference to FIGS. 3 to 7.
Even when a PDCP layer of a transmitter decides deactivation of
duplicate packet transmission and thus does not perform the
duplicate packet transmission any more, the PDCP layer of the
receiver may receive, during a certain time, one or more packets on
which the duplicate packet transmission is performed, and thus a
receiver operation according to the duplicate packet transmission
has to be maintained during the certain time.
[0092] When the receiver determines that the duplicate packet
transmission is deactivated, in operation 1h-30, the receiver may
start a pre-set first timer. The receiver may perform, during a
time of the first timer, operations of processing packets that have
been transmitted by the transmitter while the duplicate packet
transmission was activated. In this regard, the first timer may
correspond to a reordering timer for reordering packets in the PDCP
layer of the receiver. In an embodiment of the disclosure, the
first timer may correspond to a separate timer, not the reordering
timer. In addition, in an embodiment of the disclosure, a pre-set
value may be used as a temporal length of a timer, or the temporal
length of the timer may be received from a base station.
[0093] In operation 1h-40, after the first timer starts, the PDCP
layer of the receiver may not transfer, to an upper layer, packets
on which packet duplication is not performed, but may store the
packets. During the time, only packets on which the duplicate
packet transmission is performed may be reordered and then
transferred to the upper layer.
[0094] After the first timer stops, the receiver may determine that
a packet on which the duplicate packet transmission is performed
will not be received any more. After the determination, in
operation 1h-50, the PDCP layer of the receiver may process the
packets on which the duplicate packet transmission is not performed
and may transfer the packets to the upper layer.
[0095] FIG. 9 is a diagram illustrating an operation process of a
receiver when duplicate packet transmission is deactivated
according to an embodiment of the disclosure.
[0096] Referring to FIG. 9, an example is illustrated in which, as
in an embodiment of the disclosure described with reference to FIG.
3, an SN of a PDCP layer is included in duplicate packet
transmission, and an SN of 0 is used when the terminal device is
not performed. However, an embodiment of FIG. 9 is not limited
thereto, and thus may be applied to a general case in which a
packet on which duplicate packet transmission is performed is
received and then the duplicate packet transmission is
deactivated.
[0097] Referring to FIG. 9, the PDCP layer of the receiver receives
a packet 1i-10 for which duplicate packet transmission with an SN
of 19999 is set. When reordering with respect to the packet is
completed, the receiver may immediately process and transfer
(1i-110) the packet 1i-10 to an upper layer. Afterward, the PDCP
layer of the receiver receives a packet 1i-20 for which duplicate
packet transmission with an SN of 20001 is set. Because a packet of
which SN is 20000 is not received when the packet 1i-20 is
received, the packet 1i-20 may not be processed for a reordering
operation but may be stored in the receiver.
[0098] In an embodiment of the disclosure, it is assumed that a
packet 1i-30 of which SN is 0 and on which duplicate packet
transmission is not performed is received. At this point, the
terminal that is the receiver may determine that the duplicate
packet transmission is deactivated.
[0099] In this regard, the receiver may start a first timer 1i-50
to receive, during a certain time, one or more packets on which the
duplicate packet transmission is performed. Afterward, it is
assumed that a packet 1i-40 of which SN is 20002, and a packet
1i-50 of which SN is 20000 are received. Because reordering with
respect to packets of which SNs are up to 20002 has been completed
when the packet 1i-50 of which SN is 20000 is received, from the
packet 1i-50 of which SN is 20000 to the packet 1i-40 of which SN
is 20002 may be processed by the PDCP layer of the receiver and may
be transferred (1i-120, 1i-130, and 1i-140) to the upper layer.
Afterward, even when a packet 1i-60 of which SN is 0 and on which
the duplicate packet transmission is not performed is received,
because the first timer is operating, the packet 1i-60 may not be
processed and may be only stored. Afterward, after the first timer
stops, stored packets may be transferred (1i-150 and 1i-160) to the
upper layer according to an order of reception. After the first
timer stops, the duplicate packet transmission is not performed,
and thus a packet 1i-70 of which SN is 0 may be immediately
processed upon reception and then may be transferred (1i-170) to
the upper layer.
[0100] FIG. 10 is a diagram illustrating an operation process of a
receiver when duplicate packet transmission is deactivated
according to an embodiment of the disclosure.
[0101] Referring to FIG. 10, an example is illustrated in which, as
in an embodiment of the disclosure described with reference to FIG.
3, an SN of a PDCP layer is included in duplicate packet
transmission, and an SN of 0 is used when the terminal device is
not performed. However, an embodiment of FIG. 10 is not limited
thereto, and thus may be applied to a general case in which a
packet on which duplicate packet transmission is performed is
received and then the duplicate packet transmission is
deactivated.
[0102] Referring to FIG. 10, the PDCP layer of the receiver
receives a packet 1j-10 for which duplicate packet transmission
with an SN of 19999 is set. When reordering with respect to the
packet is completed, the receiver may immediately process and
transfer (1j-110) the packet 1j-10 to an upper layer. Afterward,
the receiver receives a packet 1j-20 for which duplicate packet
transmission with an SN of 20001 is set. Because a packet of which
SN is 20000 is not received when the packet 1j-20 is received, the
packet 1j-20 may not be processed for a reordering operation but
may be stored in the receiver.
[0103] In an embodiment of the disclosure, it is assumed that a
packet 1j-30 of which SN is 0 and on which duplicate packet
transmission is not performed is received. At this point, the
terminal that is the receiver may determine that the duplicate
packet transmission is deactivated.
[0104] In this regard, the receiver may start a first timer 1j-100
to receive, during a certain time, one or more packets on which the
duplicate packet transmission is performed. Afterward, it is
assumed that a packet 1j-40 of which SN is 20002, and a packet
1j-50 of which SN is 20000 are received. Because reordering with
respect to packets of which SNs are up to 20002 has been completed
when the packet 1j-50 of which SN is 20000 is received, from the
packet 1j-50 of which SN is 20000 to the packet 1j-40 of which SN
is 20002 may be processed by the PDCP layer of the receiver and may
be transferred (1j-120, 1j-130, and 1j-140) to the upper layer.
[0105] In an embodiment of the FIG. 10, it is assumed that an end
marker 1j-45 indicating that the packet 1j-40 of which SN is 20002
is a last packet on which the duplicate packet transmission is
performed is inserted to a PDCP header of the packet 1j-40 of which
SN is 20002. When the packet 1j-40 including the end marker 1j-45
is received, the PDCP layer of the receiver may identify the packet
1j-40 that is a last packet on which the duplicate packet
transmission is performed. Therefore, when a reordering process is
completed up to the packet, the receiver does not need to perform a
receiver operation for duplicate packet transmission. Therefore,
the PDCP layer of the receiver may stop the first timer 1j-100 at
1j-105 after processing the packet 1j-40 of which SN is 20002.
[0106] At this time, the stored packet 1j-30 on which the duplicate
packet transmission is not performed may be processed and
transferred (1j-150) to the upper layer. After the first timer
stops at 1j-105, the duplicate packet transmission is not
performed, and thus a packet 1j-60 of which SN is 0 may be
immediately processed upon reception and then may be transferred
(1j-160) to the upper layer.
[0107] FIG. 11 is a flowchart illustrating operations of a
transmitter and a receiver according to whether duplicate packet
transmission is to be performed according to an embodiment of the
disclosure.
[0108] Referring to FIG. 11, a packet that arrives at a PDCP layer
of the transmitter may have a QoS requirement to be processed by
the packet. The QoS requirement may include a function index, such
as a reliability level, a packet error rate, a delay time, or the
like, or may correspond to a representative value indicating the
QoS requirement. In an embodiment of FIG. 11, as an example, a
method of determining whether to perform packet duplication, based
on a PPPR used in V2X communication, is illustrated. In the V2X
communication, a PPPR value may represent a QoS requirement of a
packet to be transmitted.
[0109] When a packet arrives at the PDCP layer of the transmitter,
the PDCP layer may determine a PPPR value of the packet. In
operation 1k-10, the transmitter may determine whether duplicate
packet transmission is to be performed, based on the determined
PPPR value. In an embodiment of the disclosure, when the PPPR value
of the packet is less than or is equal to or less than a threshold
value at which the duplicate packet transmission is requested, the
PDCP layer of the transmitter may determine that the duplicate
packet transmission is not requested, and thus may not duplicate
the packet and may transfer the packet to only one RLC entity.
[0110] In operation 1k-20, the transmitter may determine whether a
radio bearer has been performing the duplicate packet transmission
and then is deactivated. When the radio bearer is not a radio
bearer that has been performing the duplicate packet transmission
and then is deactivated, it means that the radio bearer did not
perform the duplicate packet transmission from a start point. At
this time, a PDCP SN is not required, and thus, in operation 1k-30,
the PDCP SN may be set as 0.
[0111] In addition, because it is not required for a PDCP layer of
the receiver to use a reordering function and a duplication
detection function, in operation 1k-40, the receiver may not use
the reordering function and the duplication detection function.
[0112] Otherwise, when the radio bearer is a radio bearer that has
been performing the duplicate packet transmission and then is
deactivated, and when a receiver operation is not changed, a PDCP
SN may be required. Therefore, in operation 1k-50, the PDCP SN may
be continuously used. In addition, in operation 1k-60, the PDCP
layer of the receiver may continuously use the reordering function
and the duplication detection function.
[0113] FIG. 12 illustrates a block diagram of a terminal according
to an embodiment of the disclosure.
[0114] Referring to FIG. 12, the terminal may include a transceiver
1l-10, a processor 1l-20, and a memory 1l-30. In an embodiment of
the disclosure, the processor 1l-20 may be defined as an integrated
circuit or at least one processor dedicated to a circuit or an
application.
[0115] The transceiver 1l-10 may transceive a signal to/from
another network entity. For example, the transceiver 1l-10 may
receive, from a base station, system information, and at least one
of a synchronization signal or a reference signal.
[0116] The processor 1l-20 may control general operations of the
terminal according to embodiments of the disclosure. For example,
the processor 1l-20 may control a signal flow between blocks to
perform operations described with reference to drawings.
[0117] The memory 1l-30 may store at least one of information
transceived through the transceiver 1l-10 or information generated
by the processor 1l-20. In addition, the memory 1l-30 may provide
stored data, in response to a request from the processor 1l-20. The
memory 1l-30 may be configured as a storage medium or a combination
of storage media including read-only memory (ROM), random-access
memory (RAM), a hard disk, compact disc-ROM (CD-ROM), digital
versatile disc (DVD), or the like. In addition, the memory 1l-30
may include a plurality of memories.
[0118] FIG. 13 illustrates a block diagram of a base station
according to an embodiment of the disclosure.
[0119] Referring to FIG. 13, the base station may include a
transceiver 1m-10, a processor 1m-20, and a memory 1m-30. In an
embodiment of the disclosure, the processor 1m-20 may be defined as
an integrated circuit or at least one processor dedicated to a
circuit or an application.
[0120] The transceiver 1m-10 may transceive a signal to/from
another network entity. For example, the transceiver 1m-10 may
transmit, to a terminal, system information, and at least one of a
synchronization signal or a reference signal.
[0121] The processor 1m-20 may control general operations of the
base station according to embodiments of the disclosure. For
example, the processor 1m-20 may control a signal flow between
blocks to perform operations described with reference to
drawings.
[0122] The memory 1m-30 may store at least one of information
transceived through the transceiver 1m-10 or information generated
by the processor 1m-20.
[0123] FIG. 14 is a diagram illustrating a change in a radio bearer
configuration according to whether duplicate packet transmission is
to be performed according to an embodiment of the disclosure.
[0124] Referring to FIG. 14, a radio bearer 2a-10 that does not
perform duplicate packet transmission may be connected to a PDCP
layer 2a-20 and an RLC entity 2a-30 (also referred to as the RLC1
2a-30). In this regard, each RLC entity may correspond to a logical
channel, and the RLC1 2a-30 may correspond to a LCH1 2a-40.
[0125] When a terminal does not perform the duplicate packet
transmission, a packet that arrives at the radio bearer 2a-10 may
not be packet-duplicated by the PDCP layer 2a-20, a PDCP header may
be added thereto, and then the packet may be transferred to the RLC
entity 2a-30. In addition, an RLC header may be added to the packet
by the RLC entity 2a-30, and the packet may be transmitted through
the LCH1 2a-40. In an embodiment of the disclosure, an RLC entity
of a receiver may identify an RLC entity of each packet by using a
LCID included in each MAC subheader, such that the packet may be
transferred to the RLC entity 2a-30. After the RLC header is
removed, the packet may be transferred to the PDCP layer 2a-20 and
thus the PDCP header may be removed.
[0126] In an embodiment of the disclosure, duplicate packet
transmission may be activated due to various reasons including
settings of a base station, self-determination by the terminal, or
the like. In this regard, a radio bearer 2a-50 may be connected to
a PDCP layer 2a-60 and at least two RLC entities 2a-70 and 2a-80
(also referred to as the RLC1 2a-70 and the RLC2 2a-80). In an
embodiment of FIG. 14, two RLC entities are shown as an example,
but the number of RLC entities in the disclosure is not limited
thereto and thus may extend to two or more RLC entities. Each RLC
entity may correspond to a logical channel, and the RLC1 2a-70 and
the RLC2 2a-80 may correspond to a LCH1 2a-90 and a LCH2 2a-100
(also referred to as the LCH 2a-90 and the LCH 2a-100),
respectively. When the terminal performs the duplicate packet
transmission, packet duplication may be performed on a packet by
the PDCP layer 2a-60, the packet arriving at the radio bearer
2a-50, and a PDCP header may be added to each of the packets, and
then the respective packets may be transferred to the RLC entities
2a-70 and 2a-80. The RLC entities 2a-70 and 2a-80 may each add an
RLC header to the respective packets, and may transmit the packets
through the LCHs 2a-90 and 2a-100, respectively.
[0127] An RLC entity of a receiver may identify an RLC entity of
each packet by using an LCID included in each MAC subheader, such
that the respective packets may be transferred to the RLC entities
2a-70 and 2a-80. After the RLC header of each of the packets is
removed, the packets may be transferred to the PDCP layer 2a-60 and
thus the PDCP header may be removed.
[0128] In an embodiment of the disclosure, because a same packet
may be received from each of RLC entities, a PDCP layer may perform
a duplication detection function and thus may prevent the same
packet from being transferred to an upper layer several times. In
addition, because a time when a packet is transferred from each RLC
entity is not regular, the PDCP layer may perform a reordering
function so as to allow packets to be transferred from a PDCP layer
of the receiver to an upper layer according to an order, the
packets being transmitted from a PDCP layer of a transmitter. For
the duplication detection or the reordering function which is
described above, it is required for the PDCP layer of the receiver
to identify an order of packets, and thus, when duplicate packet
transmission is performed, a SN of a PDCP layer may be included in
a PDCP header.
[0129] FIG. 15 is a flowchart illustrating a process of determining
packet duplication, the process being performed by a PDCP layer of
a transmitter according to an embodiment of the disclosure.
[0130] Referring to FIG. 15, a packet that arrives at the PDCP
layer of the transmitter may have a QoS requirement to be processed
by the packet. The QoS requirement may include a function index,
such as a reliability level, a packet error rate, a delay time, or
the like, or may correspond to a representative value indicating
the QoS requirement.
[0131] In an embodiment of FIG. 15, as an example, a method of
determining whether to perform packet duplication, based on a PPPR
used in V2X communication, is illustrated. In the V2X
communication, a PPPR value may represent a QoS requirement of a
packet to be transmitted.
[0132] In operation 2b-10, when a packet arrives at the PDCP layer
of the transmitter, the PDCP layer may determine a PPPR value of
the packet.
[0133] In operation 2b-20, the PPPR value of the packet may be
compared with a threshold value at which duplicate packet
transmission is requested.
[0134] When the PPPR value of the packet is equal to or greater
than or exceeds the threshold value at which the duplicate packet
transmission is requested, in operation 2b-30, the PDCP layer of
the transmitter may determine that the duplicate packet
transmission is requested. The PDCP layer of the transmitter may
duplicate the packet and may transfer packets to at least two RLC
entities for transmission.
[0135] When the PPPR value of the packet is less than the threshold
value at which the duplicate packet transmission is requested, in
operation 2b-40, the PDCP layer of the transmitter may determine
that the duplicate packet transmission is not requested. The PDCP
layer of the transmitter may not duplicate the packet and may
transfer the packet to only one RLC entity.
[0136] FIG. 16 is a diagram illustrating a mobility scenario of a
transmitter and a receiver in vehicle communication according to an
embodiment of the disclosure.
[0137] In an embodiment of the disclosure, in the vehicle
communication, a transmitter and a receiver may each have mobility,
and transceiving may become unavailable due to movement of the
transmitter or the receiver.
[0138] Referring to FIG. 16, a scenario in which the transmitter
2c-10 does not move but the receiver 2c-20 moves is illustrated.
Referring to FIG. 16, at a start point, the receiver 2c-20 is
present in a zone 2c-30 where the receiver 2c-20 cannot receive a
packet transmitted from the transmitter 2c-10. As the receiver
2c-20 continuously moves, the receiver 2c-20 may move to a zone
2c-40 where the receiver 2c-20 can receive a packet transmitted
from the transmitter 2c-10. In the zone 2c-40, the receiver 2c-20
receives the packet transmitted from the transmitter 2c-10, but it
is not guaranteed that the receiver 2c-20 receives packets starting
from a packet that was first transmitted from the transmitter
2c-10. In other words, the transmitter 2c-10 might be transmitting
packets from a previous time, the receiver 2c-20 cannot receive
packets transmitted from the transmitter 2c-10 when the receiver
2c-20 is present in the reception-disabled zones 2c-30 and 2c-50,
and only after the receiver 2c-20 enters the reception-enabled zone
2c-40, the receiver 2c-20 can receive a packet. Referring to FIG.
16, as the receiver 2c-20 continuously moves, the receiver 2c-20
moves from the reception-enabled zone 2c-40 with respect to the
transmitter 2c-10 to the reception-disabled zone 2c-50. A
phenomenon in which the receiver 2c-20 could not and then can
receive a packet from the transmitter 2c-10 may occur due to
mobility of the transmitter 2c-10 or the receiver 2c-20, but the
phenomenon may occur due to an operation of the receiver 2c-20, in
which the receiver 2c-20 does not receive a packet due to necessity
and then starts receiving a packet.
[0139] FIG. 17 is a diagram illustrating a method of receiving a
packet, the method being performed by a PDCP layer of a receiver
according to an embodiment of the disclosure.
[0140] As described above with reference to FIG. 16, when the
receiver enters a reception-enabled zone or starts a receiving
operation (2d-10), the receiver may not receive packets starting
from a packet that was first transmitted from the transmitter.
[0141] Referring to FIG. 17, an example is illustrated, in which
the receiver receives a packet 2d-20 of which SN is 39999. In this
regard, the receiver has to perform processing starting from the
packet 2d-20 with the SN of 39999.
[0142] Referring to FIG. 17, it is assumed that the receiver has
received a packet 2d-30 of which SN is 40000, a packet 2d-40 of
which SN is 40001, and a packet 2d-50 of which SN is 40002. In an
embodiment of the disclosure, the packets 2d-20, 2d-30, 2d-40, and
2d-50 for which SNs are allocated may be used for a case where
packet duplication is activated. In another embodiment of the
disclosure, the packets 2d-20, 2d-30, 2d-40, and 2d-50 for which
SNs are allocated may be used when encryption is performed or a
reordering operation is required. The receiver sequentially
receives packets after the packet 2d-20 with the SN of 39999, but
the disclosure is not limited thereto. Sequential reception of
packets by the receiver cannot be guaranteed due to reasons of
duplicate packet transmission, split bearer, or the like, and the
disclosure may also be applied to a case of nonsequential
reception.
[0143] FIG. 18 is a diagram illustrating an operation of starting
reception, the operation being performed by a PDCP layer of a
receiver according to an embodiment of the disclosure.
[0144] As described above with reference to FIG. 16, when the
receiver enters a reception-enabled zone or starts a receiving
operation, the receiver may not receive packets starting from a
packet that was first transmitted from the transmitter.
[0145] Referring to FIG. 18, an example is illustrated, in which a
packet that the PDCP layer of the receiver first receives is a
packet 2e-10 with an SN of 40000.
[0146] In this regard, the PDCP layer of the receiver may start a
first timer 2e-50 so as to wait for a packet that was transmitted
prior to the packet 2e-10 with the SN of 40000. While the first
timer 2e-50 operates, the receiver may process the packet 2e-10
with the SN of 40000, a packet 2e-20 with an SN of 39999, and a
packet 2e-30 with an SN of 40001 and may store them without
transferring them to an upper layer. In an embodiment of the
disclosure, the first timer 2e-50 may be a reordering timer or a
separately defined timer. Duration of the first timer 2e-50 may be
a value randomly determined by the terminal or may be a value
preset by the base station.
[0147] After the first timer 2e-50 stops, the PDCP layer of the
receiver may reorder the stored packets 2e-10, 2e-20, and 2e-30 and
may transfer (2e-110, 2e-120, and 2e-130) them to the upper layer.
Thereafter, variables of the PDCP layer of the receiver may be
updated based on the packets 2e-10, 2e-20, and 2e-30. For example,
the PDCP layer of the receiver may update Last_Submitted_PDCP_RX_SN
to 40001 that is the latest PDCP SN transferred to the upper layer.
In another example, Next_PDCP_RX_SN may be updated to 40002 that is
predicted to arrive according to a sequential order. In addition,
various methods of updating variables may be available.
[0148] Afterward, when a packet 2e-40 of which SN is 40002 arrives,
the PDCP layer of the receiver may process the packet 2e-40
according to a PDCP operation of the receiver and then may transfer
(2e-140) it to the upper layer.
[0149] In an embodiment of the disclosure, the PDCP layer of the
receiver may start the first timer 2e-50 at a time when the packet
2e-10 with the SN of 40000 that is predicted to arrive first
actually arrives, and may set Next_PDCP_RX_SN as 40001 that is
obtained by adding 1 to the SN of the packet 2e-10 that arrives
first. In addition, the PDCP layer of the receiver may set
Reordering_PDCP_RX_COUNT for reordering as a COUNT value that is
calculated by using Next_PDCP_RX_SN and a Hyper Frame Number (HFN)
value. In this regard, a value of Last_Submitted_PDCP_RX_SN may be
set as a value preceding, by a certain number, 40000 that is the SN
of the packet 2e-10 that arrives first. For example, the value of
Last_Submitted_PDCP_RX_SN may be set as 30000 obtained by
subtracting 10000 from 40000 that is the SN of the packet 2e-10
that arrives first. In this regard, an operation of updating a
variable 2e-200 after the first timer 2e-50 stops may be performed
by a reordering operation of the PDCP layer of the receiver, and is
matched with a result of FIG. 18.
[0150] FIG. 19 is a diagram illustrating an operation of starting
reception, the operation being performed by a PDCP layer of a
receiver according to an embodiment of the disclosure.
[0151] As described above with reference to FIG. 16, when the
receiver enters a reception-enabled zone or starts a receiving
operation, the receiver may not receive packets starting from a
packet that was first transmitted from the transmitter.
[0152] Referring to FIG. 19, an example is illustrated, in which a
packet that the PDCP layer of the receiver first receives is a
packet 2f-10 with an SN of 40000.
[0153] In this regard, when the receiver receives the packet 2f-10
with the SN of 40000, it is required for the receiver to identify
whether the packet 2f-10 is normally received or is an outdated
packet of which validity is expired in previous reception. To this
end, when a packet exceeding a PDCP reception window arrives at
receiver, the PDCP layer of the receiver may determine whether a
state in which a corresponding radio bearer does not receive a
packet has been maintained during a preset time 2f-100. The preset
time 2f-100 may be randomly set by the terminal, may be a default
set time of a system, or may be set by the base station.
[0154] In a case where the receiver receives a packet, when packet
reception did not occur during a previous certain time, the PDCP
layer of the receiver may start a first timer 2f-50 so as to wait
for a packet that has been transmitted, by the transmitter, prior
to the packet 2f-10 with the SN of 40000. While the first timer
2f-50 operates, the receiver may process the packet 2f-10 with the
SN of 40000, a packet 2f-20 with an SN of 39999, and a packet 2f-30
with an SN of 40001 and may store them without transferring them to
an upper layer. The first timer 2f-50 may be a reordering timer or
a separately defined timer. Duration of the first timer 2f-50 may
be a value randomly determined by the terminal or may be a value
preset by the base station.
[0155] After the first timer 2f-50 stops, the PDCP layer of the
receiver may reorder the stored packets 2f-10, 2f-20, and 2f-30 and
may transfer (2f-110, 2f-120, and 2f-130) them to the upper layer.
Thereafter, variables of the PDCP layer of the receiver may be
updated based on the packets 2f-10, 2f-20, and 2f-30. For example,
the PDCP layer of the receiver may update Last_Submitted_PDCP_RX_SN
to 40001 that is the latest PDCP SN transferred to the upper layer.
In another example, Next_PDCP_RX_SN may be updated to 40002 that is
predicted to arrive according to a sequential order. When a
reordering timer is used as the first timer 2f-50, when a first
arriving packet, i.e., the packet 2f-10 with the SN of 40000,
arrives, the receiver may set Reordering_PDCP_RX_COUNT as a COUNT
value by using the SN of 40001 and HFN. In addition, various
methods of updating variables may be available.
[0156] Afterward, when a packet 2f-40 of which SN is 40002 arrives,
the PDCP layer of the receiver may process the packet 2f-40
according to a PDCP operation of the receiver and then may transfer
(2f-140) it to the upper layer.
[0157] In an embodiment of the disclosure, the PDCP layer of the
receiver may start the first timer 2f-50 at a time when the packet
2f-10 with the SN of 40000 that is predicted to arrive first
actually arrives, and may set Next_PDCP_RX_SN as 40001 that is
obtained by adding 1 to the SN of the packet 2f-10 that arrives
first. In addition, the PDCP layer of the receiver may set
Reordering_PDCP_RX_COUNT for reordering as a COUNT value that is
calculated by using Next_PDCP_RX_SN and a HFN value. In this
regard, a value of Last_Submitted_PDCP_RX_SN may be set as a value
preceding, by a certain number, 40000 that is the SN of the packet
2f-10 that arrives first. For example, the value of
Last_Submitted_PDCP_RX_SN may be set as 30000 obtained by
subtracting 10000 from 40000 that is the SN of the packet 2f-10
that arrives first. In this regard, at 2f-200, an operation of
updating a variable after the first timer 2f-50 stops may be
performed by a reordering operation of the PDCP layer of the
receiver, and is matched with a result of FIG. 19.
[0158] FIG. 20 is a diagram illustrating an operation performed by
a PDCP layer of a receiver when the PDCP layer of the receiver
starts reception according to an embodiment of the disclosure.
[0159] Referring to FIG. 20, when the PDCP layer of the receiver
receives a packet 2g-10 with a SN of 40000, it is required for the
receiver to identify whether the packet 2g-10 is normally received
or is an outdated packet of which validity is expired in previous
reception. To this end, when a packet exceeding a PDCP reception
window arrives, the PDCP layer of the receiver may determine
whether a state in which a corresponding radio bearer does not
receive a packet has been maintained during a preset time 2g-100.
The preset time 2g-100 may be randomly set by the terminal, may be
a default set time of a system, or may be set by the base
station.
[0160] In a case where the receiver receives a packet, when packet
reception did not occur during a previous certain time, the PDCP
layer of the receiver may first process the received packet after
the certain time in which the packet reception did not occur, and
may transfer the packet to an upper layer. For example, as
illustrated in an embodiment of FIG. 20, the receiver may process
the packet 2g-10 with the SN of 40000 and may transfer (2g-110) it
to the upper layer. Then, variables of the PDCP layer of the
receiver may be updated based on the packet 2g-10. For example, the
PDCP layer of the receiver may update Last_Submitted_PDCP_RX_SN to
40000 that is the latest PDCP SN transferred to the upper layer. In
another example, Next_PDCP_RX_SN may be updated to 40001 that is
predicted to arrive according to a sequential order. In addition,
various methods of updating variables may be available.
[0161] Afterward, when a packet 2g-20 of which SN is 39999 arrives,
the packet 2g-20 has a value lower than Last_Submitted_PDCP_RX_SN,
and thus, the PDCP layer of the receiver may delete (2g-120) the
packet 2g-20. Afterward, when a packet 2g-30 of which SN is 40001
arrives, the PDCP layer of the receiver may process the packet
2g-30 according to a PDCP operation of the receiver and then may
transfer (2g-130) it to the upper layer
[0162] FIG. 21 is a diagram illustrating an operation of
transmitting a packet, the operation being performed by a PDCP
layer of a transmitter according to an embodiment of the
disclosure.
[0163] When the transmitter and the receiver use a SN for duplicate
packet transmission or encryption, the SN may not be able to exceed
a maximum value of a designated SN.
[0164] Referring to FIG. 21, it is assumed that the SN has a 16-bit
value, and thus a maximum value of the SN is 2{circumflex over (
)}16-1=65535. Therefore, in an embodiment of FIG. 21, when a value
of an SN exceeds 65535, it is required to initialize the SN.
However, in a case where the transmitter does not have a wraparound
function with respect to SNs, i.e., a function of re-starting SNs
from the initialization, the transmitter may not be able to
randomly initialize an SN.
[0165] An embodiment of FIG. 21 provides an example in which, when
it is a maximum value of an SN, the SN is started by using a
different identifier. In an embodiment of the disclosure, the
transmitter may transmit (2h-10, 2h-20, and 2h-30) SNs, which are
previously used, by using a first identifier, and may transmit
(2h-40, 2h-50, 2h-60, and 2h-70) SNs, which are newly started, by
using a second identifier. By changing an indicator with respect to
a radio bearer, an SN may be restarted. In this regard, the first
identifier or the second identifier may include identification (ID)
of a LCH, ID of a radio bearer, ID of a second layer, or the like
of the terminal. In an embodiment of FIG. 21, it is assumed that an
SN starts from 0, but in another embodiment of the disclosure in
which duplicate packet transmission is used or the like, the SN may
start from 1.
[0166] FIG. 22 is a diagram illustrating an operation of
transmitting a packet, the operation being performed by a PDCP
layer of a transmitter according to an embodiment of the
disclosure.
[0167] When the transmitter and the receiver use a SN for duplicate
packet transmission or encryption, the SN may not be able to exceed
a maximum value of a designated SN.
[0168] Referring to FIG. 22, it is assumed that the SN has a 16-bit
value, and thus a maximum value of the SN is 2{circumflex over (
)}16-1=65535. Therefore, when a value of an SN exceeds 65535, it is
required to initialize the SN. However, in a case where the
transmitter does not have a wraparound function with respect to
SNs, i.e., a function of re-starting SNs from the initialization,
the transmitter may not be able to randomly initialize an SN.
[0169] An embodiment of FIG. 22 provides an example in which, when
it is a maximum value of an SN, the SN is started by using a
different identifier. In an embodiment of the disclosure, the
transmitter may transmit (2i-10, 2i-20, and 2i-30) SNs, which are
previously used, by using a first identifier, and may transmit
(2i-40, 2i-50, 2i-60, and 2i-70) SNs, which are newly started, by
using a second identifier By changing an indicator with respect to
a radio bearer, an SN may be restarted. In this regard, the first
identifier or the second identifier may include ID of a LCH, ID of
a radio bearer, ID of a second layer, or the like of the
terminal.
[0170] However, when transmission is performed by using the second
identifier, it is not guaranteed, with only a change in an
identifier, that a corresponding radio bearer is the same as a
radio bearer from which transmission using a previous identifier is
performed. Therefore, in an embodiment of FIG. 22, a PDCP header
may include fields 2i-100, 2i-110, 2i-120, and 2i-130 indicating
that transmission of corresponding packets is transmission with a
changed identifier. When such field is set, the PDCP layer of the
receiver may recognize that a radio bearer from which a certain
packet is transmitted is equal to a radio bearer of previous
transmission, and an identifier is changed to a second identifier
so as to initialize SNs. In an embodiment of FIG. 22, it is assumed
that an SN starts from 0, but in another embodiment of the
disclosure in which duplicate packet transmission is used or the
like, the SN may start from 1.
[0171] FIG. 23 is a diagram illustrating an operation of
transmitting a packet, the operation being performed by a PDCP
layer of a transmitter according to an embodiment of the
disclosure.
[0172] When the transmitter and the receiver use a SN for duplicate
packet transmission or encryption, the SN may not be able to exceed
a maximum value of a designated SN.
[0173] Referring to FIG. 23, it is assumed that the SN has a 16-bit
value, and thus a maximum value of the SN is 2{circumflex over (
)}16-1=65535. Therefore, when a value of an SN exceeds 65535, it is
required to initialize the SN. However, in a case where the
transmitter does not have a wraparound function with respect to
SNs, i.e., a function of re-starting SNs from the initialization,
the transmitter may not be able to randomly initialize an SN.
[0174] Referring to FIG. 23 provides an example in which, when it
is a maximum value of an SN, the SN is started by using a different
identifier. In an embodiment of the disclosure, the transmitter may
transmit (2j-10, 2j-20, and 2j-30) SNs, which are previously used,
by using a first identifier, and may transmit (2j-40, 2j-50, 2j-60,
and 2j-70) SNs, which are newly started, by using a second
identifier. By changing an indicator with respect to a radio
bearer, an SN may be restarted. In this regard, the first
identifier or the second identifier may include ID of a LCH, ID of
a radio bearer, ID of a second layer, or the like of the
terminal.
[0175] However, when transmission is performed by using the second
identifier, it is not guaranteed, with only a change in an
identifier, that a corresponding radio bearer is the same as a
radio bearer from which transmission using a previous identifier is
performed. Therefore, in an embodiment of FIG. 23, before
transmission using the second identifier is performed, an
identifier change message 2j-100 is transmitted to the receiver,
such that the receiver may recognize that SNs are initialized by
changing an identifier. When the receiver receives such message,
the PDCP layer of the receiver may recognize that a radio bearer
from which a certain packet is transmitted is equal to a radio
bearer of previous transmission, and an identifier is changed to
the second identifier so as to initialize SNs. In an embodiment of
FIG. 23, it is assumed that an SN starts from 0, but in another
embodiment of the disclosure in which duplicate packet transmission
is used or the like, the SN may start from 1.
[0176] FIG. 24 is a diagram illustrating an operation of receiving
a packet, the operation being performed by a PDCP layer of a
receiver according to an embodiment of the disclosure.
[0177] In an embodiment of the disclosure, when a SN of a radio
bearer with respect to data transmitted from the transmitter is a
maximum value, the transmitter may initialize the SN by using the
method described with reference to FIGS. 21 to 23.
[0178] Referring to FIG. 24, it is assumed that a packet 2k-10 with
an SN of 65533 and a packet 2k-20 with an SN of 65534 are
transmitted by using a first identifier. Because the packets 2k-10
and 2k-20 are arrived in sequence at the receiver, the PDCP layer
of the receiver may immediately process the packets 2k-10 and 2k-20
upon reception and may transfer (2k-110 and 2k-120) them to an
upper layer. Afterward, a packet 2k-30 with an SN of 1 may arrive
by using a second identifier. However, it is not guaranteed for the
receiver that a packet using the first identifier will not arrive
any more. Therefore, the PDCP layer of the receiver may not
immediately process the packet 2k-30 with the SN of 1.
[0179] Referring to FIG. 24, in an embodiment of the disclosure,
the PDCP layer of the receiver may start a first timer 2k-100 of
certain duration at a time when the packet 2k-30 using the second
identifier arrives. Until the first timer 2k-100 stops, the PDCP
layer of the receiver may not process the packet 2k-30 using the
second identifier but may store the packet 2k-30.
[0180] After the packet 2k-30 with the SN of 1 arrives, a packet
2k-40 with an SN of 0 may arrive. Because the packet 2k-40 has
arrived before the first timer 2k-100 stops, the packet 2k-40 may
not be processed but may be stored. Afterward, when a packet
2k-50/2k-130 with an SN of 65535 arrives, because the packet 2k-50
that uses the first identifier is a previous packet before SNs are
initialized, the packet 2k-50 may be immediately processed as soon
as the packet 2k-50 arrives. According to an embodiment of the
disclosure, a packet may be completely reordered and then may be
processed.
[0181] The PDCP layer of the receiver may process packets
transmitted by using the second identifier, the packets having been
stored after the first timer 2k-100 stops, and may transfer (2k-140
and 2k-150) them to the upper layer. The first timer 2k-100 may be
a reordering timer or a separately defined timer. Duration of the
first timer 2k-100 may be a value randomly determined by the
terminal or may be a value preset by the base station.
[0182] FIG. 25 is a diagram illustrating an operation of receiving
a packet, the operation being performed by a PDCP layer of a
receiver according to an embodiment of the disclosure.
[0183] In an embodiment of the disclosure, when a SN of a radio
bearer with respect to data transmitted from the transmitter is a
maximum value, the transmitter may initialize the SN by using an
identifier change message, according to the method described with
reference to FIG. 23.
[0184] Referring to FIG. 25, it is assumed that a packet 2l-10 with
an SN of 65533 and a packet 2l-20 with an SN of 65534 are
transmitted by using a first identifier. Because the packets 2l-10
and 2l-20 are arrived in sequence at the receiver, the receiver may
immediately process the packets 2l-10 and 2l-20 upon reception and
may transfer (2l-110 and 2l-120) them to an upper layer. Afterward,
an identifier change message 2l-25 may arrive at the PDCP layer of
the receiver. When the identifier change message 2l-25 is received,
the receiver may determine that packets to be arrived at a later
time by using a second identifier are packets that carry the same
data and for which SNs are initialized.
[0185] In an embodiment of the disclosure, the PDCP layer of the
receiver may start a first timer 2l-100 of certain duration at a
time when the identifier change message 2l-25 arrives. Until the
first timer 2l-100 stops, the PDCP layer of the receiver may not
process a packet using the second identifier but may store the
packet.
[0186] Referring to FIG. 25, after a packet 2l-30 with an SN of 1
arrives, a packet 2l-40 with an SN of 0 may arrive. Because the
packet 2l-40 has arrived before the first timer 2l-100 stops, the
packet 2l-40 may not be processed but may be stored. Afterward,
when a packet 2l-50/2l-130 with an SN of 65535 arrives, because the
packet 2l-50 that uses the first identifier is a previous packet
before SNs are initialized, the packet 2l-50 may be immediately
processed as soon as the packet 2l-50 arrives. According to an
embodiment of the disclosure, a packet may be completely reordered
and then may be processed.
[0187] The PDCP layer of the receiver may process packets
transmitted by using the second identifier, the packets having been
stored after the first timer 2l-100 stops, and may transfer (2l-140
and 2l-150) them to the upper layer. The first timer 2l-100 may be
a reordering timer or a separately defined timer. Duration of the
first timer 2l-100 may be a value randomly determined by the
terminal or may be a value preset by the base station.
[0188] FIG. 26 illustrates a block diagram of a terminal according
to an embodiment of the disclosure.
[0189] Referring to FIG. 26, the terminal may include a transceiver
2m-10, a processor 2m-20, and a memory 2m-30. According to a
communication method of the terminal described above, the
transceiver 2m-10, the processor 2m-20, and the memory 2m-30 of the
terminal may operate. However, elements of the terminal are not
limited to the aforementioned example. For example, the terminal
may be embodied with more elements than the aforementioned elements
or may be embodied with fewer elements than the elements. In
addition, the transceiver 2m-10, the processor 2m-20, and the
memory 2m-30 may be implemented as one chip.
[0190] The processor 2m-20 may control a series of processes to
make the terminal operate according to the embodiments of the
disclosure. For example, the processor 2m-20 may control a signal
flow between blocks to perform operations according to the
embodiments of the disclosure.
[0191] The transceiver 2m-10 may transceive a signal to/from
another network entity. For example, the transceiver 2m-10 may
receive, from the base station, system information, and at least
one of a synchronization signal or a reference signal. To this end,
the transceiver 2m-10 may include a radio frequency (RF)
transmitter configured to up-convert and amplify a frequency of a
signal to be transmitted, and a RF receiver configured to low-noise
amplify a received signal and down-convert a frequency. However,
the aforementioned example is merely an embodiment of the
transceiver 2m-10, and the elements of the transceiver 2m-10 are
not limited to the RF transmitter and the RF receiver.
[0192] The memory 2m-30 may store at least one of information
transceived through the transceiver 2m-10 or information generated
by the processor 2m-20. The memory 2m-30 may store programs and
data required in operations of the terminal. In addition, the
memory 2m-30 may store control information or data included in a
signal obtained by the terminal. The memory 2m-30 may be configured
as a storage medium or a combination of storage media including
ROM, RAM, a hard disk, CD-ROM, DVD, or the like. In addition, the
memory 2m-30 may include a plurality of memories. In an embodiment
of the disclosure, the memory 2m-30 may store a program for
supporting beam-based coordinated communication.
[0193] FIG. 27 illustrates a block diagram of a base station
according to an embodiment of the disclosure.
[0194] Referring to FIG. 27, the base station may include a
transceiver 2n-10, a processor 2n-20, and a memory 2n-30. In an
embodiment of the disclosure, the processor 2n-20 may be defined as
an integrated circuit or at least one processor dedicated to a
circuit or an application. However, elements of the base station
are not limited to the aforementioned example. For example, the
base station may be embodied with more elements than the
aforementioned elements or may be embodied with fewer elements than
the elements. In addition, the transceiver 2n-10, the processor
2n-20, and the memory 2n-30 may be implemented as one chip.
[0195] The transceiver 2n-10 may transceive a signal to/from
another network entity. For example, the transceiver 2n-10 may
transmit, to a terminal, system information, and at least one of a
synchronization signal or a reference signal.
[0196] The processor 2n-20 may control general operations of the
base station according to embodiments of the disclosure. For
example, the processor 2n-20 may control a signal flow between
blocks to perform operations described with reference to
drawings.
[0197] The memory 2n-30 may store at least one of information
transceived through the transceiver 2n-10 or information generated
by the processor 2n-20. In addition, the memory 2n-30 may store
control information or data included in a signal obtained by the
base station. The memory 2n-30 may be configured as a storage
medium or a combination of storage media including a ROM, a RAM, a
hard disk, a CD-ROM, a DVD, or the like. In addition, the memory
2n-30 may include a plurality of memories. In an embodiment of the
disclosure, the memory 2n-30 may store a program for supporting
beam-based coordinated communication.
[0198] The methods according to the embodiments of the disclosure
described in the claims or the detailed description may be
implemented in hardware, software, or a combination of hardware and
software.
[0199] When the methods are implemented in software, a
computer-readable recording medium having one or more programs
(software modules) recorded thereon may be provided. The one or
more programs recorded on the computer-readable recording medium or
a computer program product are configured to be executable by one
or more processors in a device. The one or more programs include
instructions to execute the methods according to the embodiments of
the disclosure described in the claims or the detailed
description.
[0200] The programs (e.g., software modules or software) may be
stored in a RAM, a non-volatile memory including a flash memory, a
ROM, an electrically erasable programmable read-only memory
(EEPROM), a magnetic disc storage device, a CD-ROM, a DVD, another
type of optical storage device, or a magnetic cassette.
Alternatively, the programs may be stored in a memory system
including a combination of some or all of the above-mentioned
memory devices. In addition, each memory device may be included by
a plural number.
[0201] The programs may also be stored in an attachable storage
device which is accessible through a communication network, such as
the Internet, an intranet, a local area network (LAN), a wireless
LAN (WLAN), or a storage area network (SAN), or a combination
thereof. The storage device may be connected through an external
port to an apparatus according to the embodiments of the
disclosure. Another storage device on the communication network may
also be connected to the apparatus performing the embodiments of
the disclosure.
[0202] In the afore-described embodiments of the disclosure,
elements included in the disclosure are expressed in a singular or
plural form according to the embodiments of the disclosure.
However, the singular or plural form is appropriately selected for
convenience of explanation and the disclosure is not limited
thereto. As such, an element expressed in a plural form may also be
configured as a single element, and an element expressed in a
singular form may also be configured as plural elements.
[0203] Meanwhile, the embodiments of the disclosure described with
reference to the specification and the drawings are merely
illustrative of specific examples to easily facilitate description
and understanding of the disclosure, and are not intended to limit
the scope of the disclosure. In other words, it will be apparent to
one of ordinary skill in the art that other modifications based on
the technical ideas of the disclosure are feasible. In addition,
the embodiments of the disclosure may be combined with each other
as required. In addition, the embodiments of the disclosure may be
applied to other communication systems, such as a long term
evolution (LTE) system, 5th generation (5G), a new radio (NR)
system, or the like.
[0204] While the disclosure has been shown and described with
reference to various embodiments thereof, it will be understood by
those skilled in the art that various changes in form and details
may be made therein without departing from the spirit and scope of
the disclosure as defined by the appended claims and their
equivalents.
* * * * *