The present disclosure relates to a radio communication technology.
Background
[0002]
In the 3rd Generation Partnership Project (3GPP) being a standard organization of mobile
communication systems, a fifth generation (which may be hereinafter referred to as "5G") radio
access system is studied (for example, NPL 2) as a successor to Long Term Evolution (LTE) and
Long Term Evolution Advanced (LTE-A) being one of fourth generation radio access systems (see
NPL 1). A technology of 5G radio sections is referred to as "New Radio Access Technology"
("New Radio" is abbreviated to "NR"). The NR system has been studied, based on the LTE
system and the LTE-A system.
[0003]
For example, in Europe, requirements for 5G are summarized in an organization named
METIS (see NPL 3). The 5G radio access system is required to implement lower power
consumption and lower apparatus costs, making its system capacity 1000 times as high as, data
transmission rate 100 times as high as, data processing delay one fifth (1/5) of, and number of
simultaneously connected communication terminals 100 times as large as those of the LTE system
(see NPL 3).
[0004]
To satisfy these requirements, in 3GPP, standardization of 5G has been studied (see NPLs
4 to 23).
[0005]
As NR access schemes, orthogonal frequency division multiplexing (OFDM) is used in a
downlink direction, and OFDM and discrete Fourier transform-spread-OFDM (DFT-s-OFDM) are
used in an uplink direction. As with LTE and LTE-A, the 5G system employs only a packet
communication method, without including circuit switching.
[0006]
In NR, frequencies higher than those in LTE are available in order to enhance the
transmission rate and reduce the processing delay.
[0007]
In NR in which frequencies higher than those in LTE may be used, cell coverage is
secured by forming a narrow beam-like transmission and reception range (beamforming) and
3
changing directions of beams (beam sweeping).
[0008]
Decisions on a frame configuration in the NR system in 3GPP described in NPL 1
(Section 5) will be described with reference to Fig. 1. Fig. 1 is an explanatory diagram illustrating
a configuration of radio frames used in an NR communication system. In Fig. 1, one radio frame
has 10 ms. The radio frame is divided into 10 subframes having equal sizes. The frame
configuration in NR supports one or a plurality of numerologies, that is, one or a plurality of
subcarrier spacings (SCSs). In NR, one subframe includes 1 ms and one slot includes 14 symbols,
regardless of the subcarrier spacing. The number of slots included in one subframe is one with
the subcarrier spacing of 15 kHz, and the number of slots with other subcarrier spacings increases
in proportion to the subcarrier spacing (see NPL 11 (3GPP TS 38.211)).
[0009]
Decisions on a channel configuration in the NR system in 3GPP are described in NPL 2
(Section 5) and NPL 11.
[0010]
A physical broadcast channel (PBCH) is a downlink transmission channel from a base
station apparatus (which may be hereinafter simply referred to as a "base station") to a
communication terminal apparatus (which may be hereinafter referred to as a "communication
terminal" or a "terminal") such as a mobile terminal apparatus (which may be hereinafter simply
referred to as a "mobile terminal"). The PBCH is transmitted together with a downlink
synchronization signal.
[0011]
The downlink synchronization signal in NR includes a primary synchronization signal (PSS) and a secondary synchronization signal (S-SS). The synchronization signal is transmitted as
a synchronization signal burst (which may be hereinafter referred to as an SS burst) from the base
station with predetermined periodicity for predetermined duration. The SS burst includes a
synchronization signal block (which may be hereinafter referred to as an SS block) of each beam
of the base station.
[0012]
The base station transmits, by changing the beams, the SS block of each beam within the
duration of the SS burst. The SS block includes the P-SS, the S-SS, and the PBCH.
[0013]
A physical downlink control channel (PDCCH) is a downlink transmission channel from
the base station to the communication terminal. The PDCCH carries downlink control
4
information (DCI). The DCI includes resource allocation information of a downlink shared
channel (DL-SCH) being one of transport channels to be described later, resource allocation
information of a paging channel (PCH) being one of transport channels to be described later,
hybrid automatic repeat request (HARQ) information on the DL-SCH, and the like. The DCI
may include an uplink scheduling grant. The DCI may include an acknowledgement
(Ack)/negative acknowledgement (Nack) being a response signal for uplink transmission. For
flexible switching of DL/UL in the slot, the DCI may include a slot format indication (SFI). The
PDCCH or the DCI is also referred to as an L1/L2 control signal.
[0014]
In NR, a time/frequency domain as candidates including the PDCCH is provided. The
domain is referred to as a control resource set (CORESET). The communication terminal
monitors the CORESET and acquires the PDCCH.
[0015]
A physical downlink shared channel (PDSCH) is a downlink transmission channel from
the base station to the communication terminal. To the PDSCH, a downlink shared channel (DLSCH) being a transport channel and a PCH being a transport channel are mapped.
[0016]
A physical uplink control channel (PUCCH) is an uplink transmission channel from the
communication terminal to the base station. The PUCCH carries uplink control information
(UCI). The UCI includes an Ack/Nack being a response signal for downlink transmission,
channel state information (CSI), a scheduling request (SR), and the like. The CSI includes a rank
indicator (RI), a precoding matrix indicator (PMI), and a channel quality indicator (CQI) report.
The RI is rank information of a channel matrix in Multiple Input Multiple Output (MIMO). The
PMI is information of a precoding weight matrix used in MIMO. The CQI is quality information
indicating received data quality or communication path quality. The UCI may be carried on a
PUSCH to be described later. The PUCCH or the UCI is also referred to as an L1/L2 control
signal.
[0017]
A physical uplink shared channel (PUSCH) is an uplink transmission channel from the
communication terminal to the base station. To the PUSCH, an uplink shared channel (UL-SCH)
being one of transport channels is mapped.
[0018]
A physical random access channel (PRACH) is an uplink transmission channel from the
communication terminal to the base station. The PRACH carries a random access preamble.
5
[0019]
A downlink reference signal (RS) is known symbols in the NR communication system.
The following four types of downlink reference signals are defined. They are a data
demodulation reference signal (DM-RS) being a UE-specific reference signal, a phase tracking
reference signal (PT-RS), a positioning reference signal (PRS), and a channel state information
reference signal (CSI-RS). Measurement of a physical layer of the communication terminal
includes reference signal received power (RSRP) measurement and reference signal received
quality (RSRQ) measurement.
[0020]
An uplink reference signal is also similarly known symbols in the NR communication
system. The following three types of uplink reference signals are defined. They are a data
demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), and a
sounding reference signal (SRS).
[0021]
Transport channels described in NPL 2 (Section 5) will be described. A broadcast
channel (BCH), among downlink transport channels, is broadcast to the entire coverage of the base
station (cell). The BCH is mapped to the physical broadcast channel (PBCH).
[0022]
HARQ retransmission control is applied to the downlink shared channel (DL-SCH).
The DL-SCH can be broadcast to the entire coverage of the base station (cell). The DL-SCH
supports dynamic or semi-static resource allocation. The semi-static resource allocation is also
referred to as semi-persistent scheduling. The DL-SCH supports discontinuous reception (DRX)
of the communication terminal in order to implement low power consumption of the
communication terminal. The DL-SCH is mapped to the physical downlink shared channel
(PDSCH).
[0023]
The paging channel (PCH) supports DRX of the communication terminal in order to
enable low power consumption of the communication terminal. The PCH is required to be
broadcast to the entire coverage of the base station (cell). The PCH is mapped to physical
resources that can be dynamically used for traffic, such as the physical downlink shared channel
(PDSCH).
[0024]
HARQ retransmission control is applied to the uplink shared channel (UL-SCH) among
uplink transport channels. The UL-SCH supports dynamic or semi-static resource allocation.
6
The semi-static resource allocation is also referred to as a configured grant. The UL-SCH is
mapped to the physical uplink shared channel (PUSCH).
[0025]
A random access channel (RACH) is limited to control information. The RACH has a
risk of collision. The RACH is mapped to the physical random access channel (PRACH).
[0026]
HARQ will be described. HARQ is a technology for enhancing communication quality
of a transmission path, using a combination of an automatic repeat request (ARQ) and error
correction (forward error correction). HARQ has an advantage in that, owing to retransmission,
error correction effectively functions even for a transmission path with varying communication
quality. Particularly, in retransmission, it is also possible to further enhance quality by
combining reception results of first transmission and reception results of retransmission.
[0027]
An example of a method of retransmission will be described. In a case in which a
receiver fails to correctly decode received data, that is, a cyclic redundancy check (CRC) error
occurs in the receiver (CRC = NG), a "Nack" is transmitted from the receiver to a transmitter.
The transmitter that has received the "Nack" retransmits data. In a case in which the receiver
successfully correctly decodes received data, that is, a CRC error does not occur in the receiver
(CRC = OK), an "Ack" is transmitted from the receiver to the transmitter. The transmitter that
has received the "Ack" transmits subsequent data.
[0028]
Another example of a method of retransmission will be described. In a case in which a
CRC error occurs in the receiver, a retransmission request is performed from the receiver to the
transmitter. The retransmission request is performed using toggling of a new data indicator
(NDI). The transmitter that has received the retransmission request retransmits data. In a case
in which a CRC error does not occur in the receiver, the retransmission request is not performed.
In a case in which the transmitter does not receive the retransmission request for a predetermined
time, the transmitter considers that no CRC error has occurred in the receiver.
[0029]
Logical channels described in NPL 1 (Section 6) will be described. A broadcast control
channel (BCCH) is a downlink channel for broadcasting system control information. The BCCH
being a logical channel is mapped to the broadcast channel (BCH) or the downlink shared channel
(DL-SCH) being transport channels.
[0030]
7
A paging control channel (PCCH) is a downlink channel for transmitting paging
information and system information change. The PCCH being a logical channel is mapped to the
paging channel (PCH) being a transport channel.
[0031]
A common control channel (CCCH) is a channel for transmitting control information
between the communication terminal and the base station. The CCCH is used in a case in which
the communication terminal does not have RRC connection with the network. In the downlink
direction, the CCCH is mapped to the downlink shared channel (DL-SCH) being a transport
channel. In the uplink direction, the CCCH is mapped to the uplink shared channel (UL-SCH)
being a transport channel.
[0032]
A dedicated control channel (DCCH) is a channel for transmitting dedicated control
information between the communication terminal and the network on a one-to-one basis. The
DCCH is used in a case in which the communication terminal has RRC connection with the
network. The DCCH is mapped to the uplink shared channel (UL-SCH) in the uplink, and is
mapped to the downlink shared channel (DL-SCH) in the downlink.
[0033]
A dedicated traffic channel (DTCH) is a channel for one-to-one communication to the
communication terminal for transmission of user information. The DTCH is present in both of
the uplink and the downlink. The DTCH is mapped to the uplink shared channel (UL-SCH) in
the uplink, and is mapped to the downlink shared channel (DL-SCH) in the downlink.
[0034]
Location tracking of the communication terminal is performed in a unit of an area
consisting of one or more cells. Location tracking is performed to enable tracking the location
of the communication terminal even in an idle state, and enable calling the communication terminal,
that is, enable the communication terminal to receive a call. The area for location tracking of the
communication terminal is referred to as a tracking area (TA).
[0035]
NR supports calling the communication terminal in a range in a unit of an area smaller
than the tracking area. The range is referred to as a RAN notification area (RNA). Paging of
the communication terminal in an RRC_INACTIVE state to be described later is performed in the
range.
[0036]
In NR, carrier aggregation (CA) is studied, in which two or more component carriers
8
(CCs) are aggregated to support wide frequency bandwidths (transmission bandwidths). CA is
described in NPL 1.
[0037]
In a case in which CA is configured, the UE being a communication terminal has a single
RRC connection with the network (NW). In RRC connection, one serving cell provides NonAccess Stratum (NAS) mobility information and security input. The cell is referred to as a
primary cell (PCell). A secondary cell (SCell) is configured to form a group of serving cells with
the PCell, according to a UE capability. The group of serving cells consisting of one PCell and
one or more SCells is configured for one UE.
[0038]
3GPP has dual connectivity (abbreviated to DC) or the like in which the UE connects to
two base stations and perform communication, in order to further increase communication capacity.
DC is described in NPLs 1 and 22.
[0039]
One of the base stations performing dual connectivity (DC) may be referred to as a
"master base station (master node (MN))", and the other may be referred to as a "secondary base
station (secondary node (SN))". The serving cells configured by the master base station may be
collectively referred to as a master cell group (MCG), and the serving cells configured by the
secondary base station may be collectively referred to as a secondary cell group (SCG). In DC,
a primary cell in the MCG or the SCG is referred to as a special cell (SpCell or SPCell). The
special cell in the MCG is referred to as a PCell, and the special cell in the SCG is referred to as a
primary SCG cell (PSCell).
[0040]
In NR, the base station configures a part of the carrier frequency band (the part may be
hereinafter referred to as a bandwidth part (BWP)) for the UE in advance, and the UE performs
transmission and reception to and from the base station in the BWP, to thereby reduce power
consumption in the UE.
[0041]
In 3GPP, support of services (which may be applications) using sidelink (SL)
communication (also referred to as PC5 communication) both in an Evolved Packet System (EPS)
and a 5G core system to be described later is studied (see NPLs 1, 2, and 26 to 28). In SL
communication, communication is performed between the terminals. Examples of the services
using SL communication include a vehicle-to-everything (V2X) service, a proximity-based service,
and the like. The SL communication proposes not only direct communication between the
9
terminals but also communication between the UE and the NW via relay (see NPLs 26 and 28).
[0042]
Physical channels used in the SL (see NPLs 2 and 11) will be described. A physical
sidelink broadcast channel (PSBCH) carries information on a system and synchronization, and is
transmitted from the UE.
[0043]
A physical sidelink control channel (PSCCH) carries control information from the UE for
sidelink communication and V2X sidelink communication.
[0044]
A physical sidelink shared channel (PSSCH) carries data from the UE for sidelink
communication and V2X sidelink communication.
[0045]
A physical sidelink feedback channel (PSFCH) carries sidelink HARQ feedback from the
UE that has received PSSCH transmission to the UE that has transmitted the PSSCH.
[0046]
Transport channels used in the SL (see NPL 1) will be described. A sidelink broadcast
channel (SL-BCH) has a predetermined transport format, and is mapped to the PSBCH being a
physical channel.
[0047]
A sidelink shared channel (SL-SCH) supports broadcast transmission. The SL-SCH
supports both of UE autonomous resource selection and resource allocation scheduled by the base
station. UE autonomous resource selection has a risk of collision, and in a case in which
dedicated resources are allocated to the UE by the base station, there is no collision. The SLSCH supports dynamic link adaptation by changing transmit power, modulation, and coding.
The SL-SCH is mapped to the PSSCH being a physical channel.
[0048]
Logical channels used in the SL (see NPL 2) will be described. A sidelink broadcast
control channel (SBCCH) is a sidelink channel for broadcasting sidelink system information from
one UE to another UE. The SBCCH is mapped to the SL-BCH being a transport channel.
[0049]
A sidelink traffic channel (STCH) is a one-to-many sidelink traffic channel for
transmitting user information from one UE to another UE. The STCH is used only by the UE
having a sidelink communication capability and the UE having a V2X sidelink communication
capability. One-to-one communication between the UEs having two sidelink communication
10
capabilities is also implemented on the STCH. The STCH is mapped to the SL-SCH being a
transport channel.
[0050]
A sidelink control channel (SCCH) is a sidelink control channel for transmitting control
information from one UE to another UE. The SCCH is mapped to the SL-SCH being a transport
channel.
[0051]
In LTE, only broadcast is supported in the SL communication. In NR, support of unicast
and groupcast in addition to broadcast in the SL communication is studied (see NPL 27 (3GPP TS
23.287)).
[0052]
In SL unicast communication and groupcast communication, HARQ feedback
(Ack/Nack), a CSI report, and the like are supported.
[0053]
In 3GPP, an integrated access and backhaul (IAB) is studied, in which both of an access
link being a link between the UE and the base station and a backhaul link being a link between the
base stations are performed wirelessly (see NPLs 2, 20, and 29).
[0054]
Some new technologies are required for the mobile communication system. For
example, new technologies are required to introduce, into the mobile communication system,
Internet of Things (IoT) devices having ultra-low power consumption, such as battery-less devices
and devices that do not require replacement or charging and are capable of communication only
with an energy storing function. In 3GPP, discussion on such new technologies has begun (NPLs
30, 31, 32, and 33).In the mobile communication system, communication for various services is performed,
and thus it is assumed that an enormous number of IoT devices such as wearable terminals and
sensors are to be used in the future. Thus, IoT devices having ultra-low power consumption, such
as battery-less devices and devices that do not require replacement or charging and are capable of
communication only with an energy storing function, are required to be used. New technologies
for introducing such IoT devices having ultra-low power consumption into the mobile
communication system are required. In 3GPP, discussion on the new technologies has begun
(NPLs 30, 31, 32, and 33). However, no disclosures have been made on a specific method for
introducing such IoT devices having ultra-low power consumption into the mobile communication
system. For example, resources for performing communication with an IoT device having ultralow power consumption, a method of communication between an IoT device and a UE or a gNB,
and the like have not been disclosed, and accordingly the IoT devices having ultra-low power
consumption cannot be introduced into the mobile communication system and communication
cannot be performed.
[0057]
In view of the problem, the present disclosure has one object to implement a
communication system for enabling communication with an IoT device having ultra-low power
consumption.
Solution to Problem
[0058]
A communication system according to the present disclosure includes a base station
supporting a fifth generation radio access system, a communication terminal configured to connect
to the base station, and a device configured to connect to the base station or the communication
terminal, in which the base station is configured to transmit, to the communication terminal,
configuration information for communication being information about a configuration for
communication between the communication terminal and the device, and configuration
information for device data transmission being information about a configuration for transmitting
device data acquired from the device by the communication terminal to the base station, and the
communication terminal is configured to perform communication with the device using the
configuration information for communication received from the base station, and transmit the
device data to the base station using the configuration information for device data transmission
received from the base station.
13
Advantageous Effects of Invention
[0059]
According to the present disclosure, a communication system for enabling
communication with an IoT device having ultra-low power consumption can be implemented.
[0060]
The objects, features, aspects and advantages of the present disclosure will become more
apparent from the following detailed description and the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0061]
Fig. 1 is an explanatory diagram illustrating a configuration of radio frames used in an
NR communication system;
Fig. 2 is a block diagram illustrating an overall configuration of an NR communication
system 210 discussed in 3GPP;
Fig. 3 is a configuration diagram of DC performed by base stations to connect to an NG
core;
Fig. 4 is a block diagram illustrating a configuration of a mobile terminal 202 illustrated
in Fig. 2;
Fig. 5 is a block diagram illustrating a configuration of a base station 213 illustrated in
Fig. 2;
Fig. 6 is a block diagram illustrating a configuration of a 5GC unit;
Fig. 7 is a flowchart illustrating an outline from cell search to idle operation performed
by a communication terminal (UE) in an NR communication system;
Fig. 8 is a diagram illustrating an example of a configuration of a cell in an NR system;
Fig. 9 is a connection configuration diagram illustrating an example of a connection
configuration of terminals in SL communication;
Fig. 10 is a connection configuration diagram illustrating an example of a connection
configuration of base stations supporting an integrated access and backhaul;
Fig. 11 is a diagram illustrating a sequence example in which a UE transmits device data
acquired from a device to a base station according to a first embodiment;
Fig. 12 is a diagram illustrating a sequence example in which the UE transmits device
data acquired from a plurality of devices to the base station according to the first embodiment;
Fig. 13 is a diagram illustrating another sequence example in which the UE transmits
14
device data acquired from the plurality of devices to the base station according to the first
embodiment;
Fig. 14 is a diagram illustrating a sequence example in which a UE being not connected
to a base station transmits device data acquired from a device to a base station according to a
second embodiment;
Fig. 15 is a diagram illustrating a sequence example of device data communication
between a device and a NW according to a third embodiment;
Fig. 16 is a diagram illustrating a first other sequence example of device data
communication between the device and the NW according to the third embodiment;
Fig. 17 is a diagram illustrating a second other sequence example of device data
communication between the device and the NW according to the third embodiment; and
Fig. 18 is a diagram illustrating a third other sequence example of device data
communication between the device and the NW according to the third embodiment.
DETAILED DESCRIPTION
[0062]
First Embodiment
Fig. 2 is a block diagram illustrating an overall configuration of an NR communication
system 210 discussed in 3GPP. Fig. 2 will be described. A radio access network is referred to
as a next generation radio access network (NG-RAN) 211. A mobile terminal apparatus
(hereinafter referred to as a "mobile terminal (user equipment (UE))") 202 being a communication
terminal apparatus is capable of radio communication with a base station apparatus (hereinafter
referred to as an "NR base station (NG-RAN Node B (gNB))") 213, and transmits and receives
signals in radio communication. The NG-RAN 211 includes one or a plurality of NR base
stations 213.
[0063]
Here, the "communication terminal apparatus" includes not only the mobile terminal
apparatus such as a mobile cellular phone terminal apparatus, but also includes an immobile device
such as a sensor. In the following description, the "communication terminal apparatus" may be
simply referred to as a "communication terminal".
[0064]
A protocol of Access Stratum (AS) is terminated between the UE 202 and the NG-RAN
211. As the protocol of AS, for example, Radio Resource Control (RRC), Service Data
Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control
15
(RLC), Medium Access Control (MAC), and Physical layer (PHY) are used. The RRC is used
in a control plane (which may be hereinafter also referred to as a C plane, a C-Plane, or a CP), the
SDAP is used in a user plane (which may be hereinafter also referred to as a U plane, a U-Plane,
or a UP), and the PDCP, the MAC, the RLC, and the PHY are used in both of the C plane and the
U plane.
[0065]
The control protocol Radio Resource Control (RRC) between the UE 202 and the NR
base station 213 performs broadcast, paging, RRC connection management, and the like. States
between the NR base station 213 and the UE 202 in RRC include RRC_IDLE,
RRC_CONNECTED, and RRC_INACTIVE.
[0066]
In RRC_IDLE, public land mobile network (PLMN) selection, system information (SI)
broadcast, paging, cell re-selection, mobility, and the like are performed. In
RRC_CONNECTED, the mobile terminal has RRC connection, and can transmit and receive data
to and from a network. In RRC_CONNECTED, handover (HO), neighbor cell measurement,
and the like are performed. In RRC_INACTIVE, connection between a 5G core unit 214 and the
NR base station 213 is maintained, and system information (SI) broadcast, paging, cell re-selection,
mobility, and the like are performed.
[0067]
The gNB 213 is connected to the 5G core unit (which may be hereinafter referred to as a
"5GC unit") 214 including an Access and Mobility Management Function (AMF), a Session
Management Function (SMF), a User Plane Function (UPF), and the like via an NG interface.
Control information and/or user data is communicated between the gNB 213 and the 5GC unit 214.
The NG interface is a general term for an N2 interface between the gNB 213 and an AMF 220, an
N3 interface between the gNB 213 and a UPF 221, an N11 interface between the AMF 220 and
an SMF 222, and an N4 interface between the UPF 221 and the SMF 222. A plurality of 5GC
units 214 may be connected to one gNB 213. The gNBs 213 are connected via an Xn interface,
and control information and/or user data is communicated between the gNBs 213.
[0068]
The 5GC unit 214 is an upper apparatus, or specifically an upper node, and performs
control of connection between the NR base station 213 and the mobile terminal (UE) 202,
distribution of paging signals to one or a plurality of NR base stations (gNBs) 213 and/or LTE
base stations (E-UTRAN Node Bs (eNBs)), and the like. The 5GC unit 214 performs mobility
control of an idle state. In a case in which the mobile terminal 202 is in an idle state, an inactive
16
state, and an active state, the 5GC unit 214 manages a tracking area list. The 5GC unit 214
transmits a paging message to a cell belonging to a tracking area in which the mobile terminal 202
is registered, and thereby starts a paging protocol.
[0069]
The gNB 213 may configure one or a plurality of cells. In a case in which one gNB 213
configures a plurality of cells, every single cell is configured to be capable of communicating with
the UE 202.
[0070]
The gNB 213 may be divided into a central unit (which may be hereinafter referred to as
a CU) 215 and a distributed unit (which may be hereinafter referred to as a DU) 216. One CU
215 is configured in the gNB 213. One or a plurality of DUs 216 are configured in the gNB 213.
One DU 216 configures one or a plurality of cells. The CU 215 is connected to the DU 216 via
an F1 interface, and control information and/or user data is communicated between the CU 215
and the DU 216. The F1 interface includes an F1-C interface and an F1-U interface. The CU
215 has a function of each protocol of the RRC, the SDAP, and the PDCP, and the DU 216 has a
function of each protocol of the RLC, the MAC, and the PHY. One or a plurality of transmission
reception points (TRPs) 219 may be connected to the DU 216. The TRP 219 transmits and
receives radio signals to and from the UE.
[0071]
The CU 215 may be divided into a C-plane CU (CU-C) 217 and a U-plane CU (CU-U)
218. One CU-C 217 is configured in the CU 215. One or a plurality of CU-Us 218 are
configured in the CU 215. The CU-C 217 is connected to the CU-U 218 via an E1 interface, and
control information is communicated between the CU-C 217 and the CU-U 218. The CU-C 217
is connected to the DU 216 via an F1-C interface, and control information is communicated
between the CU-C 217 and the DU 216. The CU-U 218 is connected to the DU 216 via an F1-
U interface, and user data is communicated between the CU-U 218 and the DU 216.
[0072]
In the 5G communication system, a Unified Data Management (UDM) function and a
Policy Control Function (PCF) described in NPL 10 (3GPP TS 23.501) may be included. The
UDM and/or the PCF may be included in the 5GC unit 214 of Fig. 2.
[0073]
In the 5G communication system, a Location Management Function (LMF) described in
NPL 24 (3GPP TS 38.305) may be provided. As disclosed in NPL 25 (3GPP TS 23.273), the
LMF may be connected to the base station via the AMF.
17
[0074]
In the 5G communication system, a Non-3GPP Interworking Function (N3IWF)
described in NPL 10 (3GPP TS 23.501) may be included. The N3IWF may terminate an access
network (AN) between the N3IWF and the UE in non-3GPP access with the UE.
[0075]
Fig. 3 is a diagram illustrating a configuration of dual connectivity (DC) to connect to an
NG core. In Fig. 3, the solid line indicates connection of the U-Plane, and the broken line
indicates connection of the C-Plane. In Fig. 3, a master base station 240-1 may be a gNB or an
eNB. A secondary base station 240-2 may be a gNB or an eNB. For example, in Fig. 3, a DC
configuration in which the master base station 240-1 is a gNB and the secondary base station 240-
2 is an eNB may be referred to as NG-EN-DC. Although Fig. 3 illustrates an example in which
U-Plane connection between the 5GC unit 214 and the secondary base station 240-2 is performed
via the master base station 240-1, the U-Plane connection may be directly performed between the
5GC unit 214 and the secondary base station 240-2. In Fig. 3, in place of the 5GC unit 214, an
Evolved Packet Core (EPC), which is a core network connected to the LTE system or the LTE-A
system, may be connected to the master base station 240-1. U-Plane connection between the
EPC and the secondary base station 240-2 may be directly performed.
[0076]
Fig. 4 is a block diagram illustrating a configuration of the mobile terminal 202 illustrated
in Fig. 2. Transmission processing of the mobile terminal 202 illustrated in Fig. 4 will be
described. First, control data from a control unit 310 and user data from an application unit 302
are transmitted to a protocol processing unit 301. The control data and the user data may be
buffered. The buffers of the control data and the user data may be provided in the control unit
310, may be provided in the application unit 302, or may be provided in the protocol processing
unit 301. The protocol processing unit 301 performs protocol processing of the SDAP, the PDCP,
the RLC, the MAC, and the like, for example, operation such as determination of a transmission
destination base station in DC or the like and provision of a header in each protocol. The data
subjected to the protocol processing is delivered to an encoder unit 304, and is subjected to
encoding processing such as error correction. There may be data that is directly output from the
protocol processing unit 301 to a modulating unit 305 without being subjected to the encoding
processing. The data subjected to the encoding processing in the encoder unit 304 is subjected
to modulation processing in the modulating unit 305. In the modulating unit 305, MIMO
precoding may be performed. The modulated data is converted into a baseband signal, and is
then output to a frequency converting unit 306 to be converted into a radio transmission frequency.
18
Subsequently, transmission signals are transmitted from antennas 307-1 to 307-4 to the base station
213. Although Fig. 4 illustrates an example of a case in which the number of antennas is four,
the number of antennas is not limited to four.
[0077]
Reception processing of the mobile terminal 202 is performed as follows. A radio signal
from the base station 213 is received by the antennas 307-1 to 307-4. The received signal is
converted from a radio reception frequency into a baseband signal in the frequency converting unit
306, and is subjected to demodulation processing in a demodulating unit 308. In the
demodulating unit 308, weight calculation and multiplication processing may be performed. The
demodulated data is delivered to a decoder unit 309, and is subjected to decoding processing such
as error correction. The decoded data is delivered to the protocol processing unit 301, and is
subjected to protocol processing of the MAC, the RLC, the PDCP, the SDAP, and the like, for
example, operation such as removal of a header in each protocol. Of the data subjected to the
protocol processing, the control data is delivered to the control unit 310 and the user data is
delivered to the application unit 302.
[0078]
The series of processing of the mobile terminal 202 is controlled by the control unit 310.
Thus, the control unit 310 is also connected to each of the units 302 and 304 to 309, of which
illustration is omitted in Fig. 4.
[0079]
Each unit of the mobile terminal 202, such as the control unit 310, the protocol processing
unit 301, the encoder unit 304, and the decoder unit 309, is implemented by processing circuitry
including a processor and a memory, for example. For example, the control unit 310 is
implemented by the processor executing a program describing the series of processing of the
mobile terminal 202. The program describing the series of processing of the mobile terminal 202
is stored in the memory. Examples of the memory include non-volatile or volatile semiconductor
memories, such as a random access memory (RAM), a read only memory (ROM), and a flash
memory. Each unit of the mobile terminal 202, such as the control unit 310, the protocol
processing unit 301, the encoder unit 304, and the decoder unit 309, may be implemented by
dedicated processing circuitry such as a field programmable gate array (FPGA), an application
specific integrated circuit (ASIC), and a digital signal processor (DSP). In Fig. 4, the number of
antennas used by the mobile terminal 202 for transmission and the number of antennas used
thereby for reception may be the same or different.
[0080]
19
Fig. 5 is a block diagram illustrating a configuration of the base station 213 illustrated in
Fig. 2. Transmission processing of the base station 213 illustrated in Fig. 5 will be described.
An EPC communication unit 401 transmits and receives data between the base station 213 and the
EPC. A 5GC communication unit 412 transmits and receives data between the base station 213
and the 5GC (such as the 5GC unit 214). Another base station communication unit 402 transmits
and receives data to and from another base station. Each of the EPC communication unit 401,
the 5GC communication unit 412, and such another base station communication unit 402
exchanges information with a protocol processing unit 403. Control data from a control unit 411
and user data and control data from the EPC communication unit 401, the 5GC communication
unit 412, and such another base station communication unit 402 are transmitted to the protocol
processing unit 403. The control data and the user data may be buffered. The buffers of the
control data and the user data may be provided in the control unit 411, may be provided in the EPC
communication unit 401, may be provided in the 5GC communication unit 412, or may be
provided in such another base station communication unit 402.
[0081]
The protocol processing unit 403 performs protocol processing of the SDAP, the PDCP,
the RLC, the MAC, and the like, for example, operation such as routing of transmission data in
DC or the like and provision of a header in each protocol. The data subjected to the protocol
processing is delivered to an encoder unit 405, and is subjected to encoding processing such as
error correction. There may be data that is directly output from the protocol processing unit 403
to a modulating unit 406 without being subjected to the encoding processing. The data may be
transmitted from the protocol processing unit 403 to such another base station communication unit
402. For example, in DC, the data transmitted from the 5GC communication unit 412 or the EPC
communication unit 401 may be transmitted to another base station, such as the secondary base
station, via such another base station communication unit 402. The encoded data is subjected to
modulation processing in the modulating unit 406. In the modulating unit 406, MIMO precoding
may be performed. The modulated data is converted into a baseband signal, and is then output
to a frequency converting unit 407 to be converted into a radio transmission frequency.
Subsequently, transmission signals are transmitted from antennas 408-1 to 408-4 to one or a
plurality of mobile terminals 202. Although Fig. 5 illustrates an example of a case in which the
number of antennas is four, the number of antennas is not limited to four.
[0082]
Reception processing of the base station 213 is performed as follows. A radio signal
from one or a plurality of mobile terminals 202 is received by the antennas 408-1 to 408-4. The
20
received signal is converted from a radio reception frequency into a baseband signal in the
frequency converting unit 407, and is subjected to demodulation processing in a demodulating unit
409. The demodulated data is delivered to a decoder unit 410, and is subjected to decoding
processing such as error correction. The decoded data is delivered to the protocol processing unit
403, and is subjected to protocol processing of the MAC, the RLC, the PDCP, the SDAP, and the
like, for example, operation such as removal of a header in each protocol. Of the data subjected
to the protocol processing, the control data is delivered to the control unit 411, the 5GC
communication unit 412, the EPC communication unit 401, or such another base station
communication unit 402, and the user data is delivered to the 5GC communication unit 412, the
EPC communication unit 401, or such another base station communication unit 402. The data
transmitted from such another base station communication unit 402 may be transmitted to the 5GC
communication unit 412 or the EPC communication unit 401. The data may be uplink data
transmitted to the 5GC communication unit 412 or the EPC communication unit 401 unit via
another base station in DC, for example.
[0083]
The series of processing of the base station 213 is controlled by the control unit 411.
Thus, the control unit 411 is also connected to each of the units 401, 402, 405 to 410, and 412, of
which illustration is omitted in Fig. 5.
[0084]
Each unit of the base station 213, such as the control unit 411, the protocol processing
unit 403, the 5GC communication unit 412, the EPC communication unit 401, such another base
station communication unit 402, the encoder unit 405, and the decoder unit 410, is implemented
by processing circuitry including a processor and a memory or dedicated processing circuitry such
as an FPGA, an ASIC, and a DSP, as in the case of the mobile terminal 202 described above. In
Fig. 5, the number of antennas used by the base station 213 for transmission and the number of
antennas used thereby for reception may be the same or different.
[0085]
As an example of a configuration of the CU 215 illustrated in Fig. 2, a configuration
provided with a DU communication unit may be used, except the encoder unit 405, the modulating
unit 406, the frequency converting unit 407, the antennas 408-1 to 408-4, the demodulating unit
409, and the decoder unit 410 illustrated in Fig. 5. The DU communication unit is connected to
the protocol processing unit 403. The protocol processing unit 403 in the CU 215 performs
protocol processing of the PDCP, the SDAP, and the like.
[0086]
21
As an example of a configuration of the DU 216 illustrated in Fig. 2, a configuration
provided with a CU communication unit may be used, except the EPC communication unit 401,
such another base station communication unit 402, and the 5GC communication unit 412
illustrated in Fig. 5. The CU communication unit is connected to the protocol processing unit
403. The protocol processing unit 403 in the DU 216 performs protocol processing of the PHY,
the MAC, the RLC, and the like.
[0087]
Fig. 6 is a block diagram illustrating a configuration of the 5GC unit. Fig. 6 illustrates
a configuration of the 5GC unit 214 illustrated in Fig. 2 described above. Fig. 6 illustrates a case
in which a configuration of the AMF, a configuration of the SMF, and a configuration of the UPF
are included in the 5GC unit 214 illustrated in Fig. 2. In the example illustrated in Fig. 6, the
AMF may have a function of a control plane control unit 525, the SMF may have a function of a
session management unit 527, and the UPF may have a function of a user plane communication
unit 523 and a data network communication unit 521. The data network communication unit 521
transmits and receives data between the 5GC unit 214 and a data network. The base station
communication unit 522 transmits and receives data between the 5GC unit 214 and the base station
213 via an NG interface. User data transmitted from the data network is delivered from the data
network communication unit 521 to the base station communication unit 522 via the user plane
communication unit 523, and is transmitted to one or a plurality of base stations 213. User data
transmitted from the base station 213 is delivered from the base station communication unit 522
to the data network communication unit 521 via the user plane communication unit 523, and is
transmitted to the data network.
[0088]
Control data transmitted from the base station 213 is delivered from the base station
communication unit 522 to the control plane control unit 525. The control plane control unit 525
may deliver the control data to the session management unit 527. The control data may be
transmitted from the data network. The control data transmitted from the data network may be
transmitted from the data network communication unit 521 to the session management unit 527
via the user plane communication unit 523. The session management unit 527 may transmit the
control data to the control plane control unit 525.
[0089]
The user plane control unit 523 includes a PDU processing unit 523-1, a mobility
anchoring unit 523-2, and the like, and performs general processing on the user plane (which may
be hereinafter also referred to as a U-Plane). The PDU processing unit 523-1 performs
22
processing of data packets, for example, transmission and reception of packets to and from the
data network communication unit 521 and transmission and reception of packets to and from the
base station communication unit 522. The mobility anchoring unit 523-2 anchors a data path at
the time of mobility of the UE.
[0090]
The session management unit 527 performs management of a PDU session provided
between the UE and the UPF and the like. The session management unit 527 includes a PDU
session control unit 527-1, a UE IP address assigning unit 527-2, and the like. The PDU session
control unit 527-1 performs management of a PDU session between the mobile terminal 202 and
the 5GC unit 214. The UE IP address assigning unit 527-2 performs assignment of an IP address
to the mobile terminal 202 and the like.
[0091]
The control plane control unit 525 includes a NAS security unit 525-1, an idle state
mobility management unit 525-2, and the like, and performs general processing on the control
plane (which may be hereinafter also referred to as a C-Plane). The NAS security unit 525-1
performs security of a Non-Access Stratum (NAS) message and the like. The idle state mobility
management unit 525-2 performs mobility management of the idle state (which may also be simply
referred to as an "RRC_IDLE state" or "idle"), generation and control of a paging signal in the idle
state, addition, deletion, update, search, and tracking area list management of a tracking area of
one or a plurality of served mobile terminals 202, and the like.
[0092]
The series of processing of the 5GC unit 214 is controlled by a control unit 526. Thus,
the control unit 526 is connected to each of the units 521 to 523, 525, and 527, of which illustration
is omitted in Fig. 6. Each unit of the 5GC unit 214 is implemented by processing circuitry
including a processor and a memory or dedicated processing circuitry such as an FPGA, an ASIC,
and a DSP, for example, as in the case of the control unit 310 of the mobile terminal 202 described
above.
[0093]
Next, an example of a cell search method in the communication system will be described.
Fig. 7 is a flowchart illustrating an outline from cell search to idle operation performed by the
communication terminal (UE) in the NR communication system. After the communication
terminal starts cell search, in Step ST601, the communication terminal establishes synchronization
of a slot timing and a frame timing, using a primary synchronization signal (P-SS) and a secondary
synchronization signal (S-SS) transmitted from a surrounding base station.
23
[0094]
The P-SS and the S-SS are collectively referred to as a synchronization signal (SS). The
synchronization signal (SS) is assigned a synchronization code that corresponds to a physical cell
identifier (PCI) assigned to each cell on a one-to-one basis. It is studied that the number of PCIs
is 1008. The communication terminal establishes synchronization using the 1008 PCIs, and
detects (identifies) the PCI(s) of synchronized cell(s).
[0095]
Next, in Step ST602, the communication terminal receives a PBCH of the synchronized
cell. A master information block (MIB) including cell configuration information is mapped to a
BCCH on the PBCH. Thus, by receiving the PBCH and obtaining the BCCH, the MIB can be
obtained. Examples of information of the MIB include a system frame number (SFN),
scheduling information of a system information block (SIB) 1, subcarrier spacing for the SIB1 or
the like, information of a DM-RS position, and the like.
[0096]
The communication terminal acquires an SS block identifier on the PBCH. A part of a
bit string of the SS block identifier is included in the MIB. The rest of the bit string is included
in an identifier used to generate a DM-RS sequence accompanying the PBCH. The
communication terminal acquires the SS block identifier, using the MIB included in the PBCH
and the DM-RS sequence accompanying the PBCH.
[0097]
Next, in Step ST603, the communication terminal measures received power of an SS
block.
[0098]
Next, in Step ST604, the communication terminal selects a cell having the best received
quality, for example, a cell having the highest received power, that is, the best cell, out of the one
or more cells detected up to Step ST603. The communication terminal selects a beam having the
best received quality, for example, a beam having the highest received power of the SS block, that
is, the best beam. In selection of the best beam, for example, received power of the SS block of
each SS block identifier is used.
[0099]
Next, in Step ST605, the communication terminal receives a DL-SCH based on the
scheduling information of the SIB1 included in the MIB, and obtains the SIB 1 in the broadcast
information BCCH. The SIB1 includes information on access to the cell, cell configuration
information, and scheduling information of another SIB (SIBk: k is an integer satisfying k ≥ 2).
24
The SIB1 includes a tracking area code (TAC).
[0100]
Next, in Step ST606, the communication terminal compares the TAC of the SIB1 received
in Step ST605 and a TAC part of a tracking area identity (TAI) in a tracking area list already stored
in the communication terminal. The tracking area list is also referred to as a TAI list. The TAI
is identification information for identifying the tracking area, and includes a mobile country code
(MCC), a mobile network code (MNC), and a tracking area code (TAC). The MCC is a country
code. The MNC is a network code. The TAC is a code number of a tracking area.
[0101]
As a result of the comparison in Step ST606, if the TAC received in Step ST605 is the
same as the TAC included in the tracking area list, the communication terminal starts idle operation
in the cell. As a result of the comparison, if the TAC received in Step ST605 is not included in
the tracking area list, the communication terminal requests, via the cell, the core network (EPC)
including an MME and the like to change the tracking area in order to perform tracking area update
(TAU).
[0102]
An apparatus configuring the core network (which may be hereinafter referred to as a
"core network-side apparatus") updates the tracking area list, based on an identification number (a
UE-ID or the like) of the communication terminal transmitted from the communication terminal
together with a TAU request signal. The core network-side apparatus transmits the updated
tracking area list to the communication terminal. The communication terminal rewrites (updates)
a TAC list stored in the communication terminal, based on the received tracking area list.
Subsequently, the communication terminal starts idle operation in the cell.
[0103]
Next, an example of a random access method in the communication system will be
described. In random access, 4-step random access and 2-step random access are used. In each
of the 4-step random access and the 2-step random access, there are contention-based random
access, that is, random access which may cause contention of timings with other mobile terminals,
and contention-free random access.
[0104]
An example of a contention-based 4-step random access method will be described. As
a first step, the mobile terminal transmits a random access preamble to the base station. The
random access preamble may be selected by the mobile terminal from a predetermined range, or
may be individually assigned to the mobile terminal and notified from the base station.
25
[0105]
As a second step, the base station transmits a random access response to the mobile
terminal. The random access response includes uplink scheduling information to be used in a
third step, a terminal identifier to be used in uplink transmission in the third step, and the like.
[0106]
As the third step, the mobile terminal performs uplink transmission to the base station.
The mobile terminal uses the information acquired in the second step in the uplink transmission.
As a fourth step, the base station notifies the mobile terminal as to whether contention resolution
is achieved. The mobile terminal notified of "without contention" ends random access processing.
The mobile terminal notified of "with contention" resumes processing from the first step.
[0107]
A contention-free 4-step random access method is different from the contention-based 4-
step random access method in the following. In other words, prior to the first step, the base
station assigns a random access preamble and uplink scheduling to the mobile terminal in advance.
A notification as to whether contention resolution is achieved in the fourth step is unnecessary.
[0108]
An example of a contention-based 2-step random access method will be described. As
a first step, the mobile terminal performs transmission of a random access preamble and uplink
transmission to the base station. As a second step, the base station notifies the mobile terminal
as to whether there is contention. The mobile terminal notified of "without contention" ends
random access processing. The mobile terminal notified of "with contention" resumes
processing from the first step.
[0109]
A contention-free 2-step random access method is different from the contention-based 2-
step random access method in the following. In other words, prior to the first step, the base
station assigns a random access preamble and uplink scheduling to the mobile terminal in advance.
As a second step, the base station transmits a random access response to the mobile terminal.
[0110]
Fig. 8 illustrates an example of a configuration of a cell in NR. In a cell in NR, a narrow
beam is formed and is transmitted with its direction being changed. In the example illustrated in
Fig. 8, a base station 750 performs transmission and reception to and from the mobile terminal,
using a beam 751-1 at a certain time. At another time, the base station 750 performs transmission
and reception to and from the mobile terminal, using a beam 751-2. Subsequently, similarly, the
base station 750 performs transmission and reception to and from the mobile terminal, using one
26
or a plurality of beams 751-3 to 751-8. In this manner, the base station 750 configures a cell 752
having a wide range.
[0111]
Although Fig. 8 illustrates an example in which the number of beams used by the base
station 750 is eight, the number of beams may be different from eight. In the example illustrated
in Fig. 8, although the number of beams simultaneously used by the base station 750 is one, the
number of beams may be more than one.
[0112]
A concept of quasi-colocation (QCL) is used in identification of a beam (see NPL 14
(3GPP TS 38.214)). In other words, identification is performed using information indicating as
which beam of a reference signal (for example, an SS block, a CSI-RS) the beam can be considered
to be the same. The information may include types of information regarding aspects in which
the beam can be considered to be the same beam, for example, information on a Doppler shift, a
Doppler shift spread, an average delay, an average delay spread, and a spatial Rx parameter (see
NPL 14 (3GPP TS 38.214)).
[0113]
In 3GPP, a sidelink (SL) is supported for device-to-device (D2D) communication and
vehicle-to-vehicle (V2V) communication (see NPL 1 and NPL 16). The SL is defined by a PC5
interface.
[0114]
In SL communication, support of PC5-S signaling is studied in order to support unicast
and groupcast in addition to broadcast (see NPL 27 (3GPP TS 23.287)). For example, the PC5-
S signaling is performed to establish the SL, that is, a link for performing PC5 communication.
The link is performed in a V2X layer, and is also referred to as a layer 2 link.
[0115]
In the SL communication, support of RRC signaling is studied (see NPL 27 (3GPP TS
23.287)). The RRC signaling in the SL communication is also referred to as PC5 RRC signaling.
For example, notification of a UE capability and notification of an AS layer configuration and the
like for performing V2X communication using the PC5 communication between the UEs
performing the PC5 communication are proposed.
[0116]
An example of a connection configuration of the mobile terminals in the SL
communication is illustrated in Fig. 9. In the example illustrated in Fig. 9, a UE 805 and a UE
806 are present inside coverage 803 of a base station 801. UL/DL communication 807 is
27
performed between the base station 801 and the UE 805. UL/DL communication 808 is
performed between the base station 801 and the UE 806. SL communication 810 is performed
between the UE 805 and the UE 806. A UE 811 and a UE 812 are present outside the coverage
803. SL communication 814 is performed between the UE 805 and the UE 811. SL
communication 816 is performed between the UE 811 and the UE 812.
[0117]
As an example of communication between the UE and the NW via relay in the SL
communication, the UE 805 illustrated in Fig. 9 relays communication between the UE 811 and
the base station 801.
[0118]
A configuration similar to that of Fig. 4 may be used for the UE performing the relay.
Relay processing in the UE will be described with reference to Fig. 4. Relay processing
performed by the UE 805 in communication from the UE 811 to the base station 801 will be
described. A radio signal from the UE 811 is received by the antennas 307-1 to 307-4. The
received signal is converted from a radio reception frequency into a baseband signal in the
frequency converting unit 306, and is subjected to demodulation processing in the demodulating
unit 308. In the demodulating unit 308, weight calculation and multiplication processing may be
performed. The demodulated data is delivered to the decoder unit 309, and is subjected to
decoding processing such as error correction. The decoded data is delivered to the protocol
processing unit 301, and is subjected to protocol processing of the MAC, the RLC, and the like
used for communication with the UE 811, for example, operation such as removal of a header in
each protocol. Protocol processing of the RLC, the MAC, and the like used for communication
with the base station 801, for example, operation such as provision of a header in each protocol, is
performed. In the protocol processing unit 301 of the UE 811, protocol processing of the PDCP
and the SDAP may be performed. The data subjected to the protocol processing is delivered to
the encoder unit 304, and is subjected to encoding processing such as error correction. There
may be data that is directly output from the protocol processing unit 301 to the modulating unit
305 without being subjected to the encoding processing. The data subjected to the encoding
processing in the encoder unit 304 is subjected to modulation processing in the modulating unit
305. In the modulating unit 305, MIMO precoding may be performed. The modulated data is
converted into a baseband signal, and is then output to the frequency converting unit 306 to be
converted into a radio transmission frequency. Subsequently, transmission signals are
transmitted from the antennas 307-1 to 307-4 to the base station 801.
[0119]
28
Although the above description illustrates an example of the relay performed by the UE
805 in communication from the UE 811 to the base station 801, similar processing is also used in
relay in communication from the base station 801 to the UE 811.
[0120]
A 5G base station can support an integrated access and backhaul (IAB) (see NPLs 2 and
20). A base station supporting the IAB (which may be hereinafter referred to as an IAB base
station) includes an IAB donor CU being a CU of the base station that operates as an IAB donor
providing an IAB function, an IAB donor DU being a DU of the base station that operates as an
IAB donor, and an IAB node connected to the IAB donor DU and the UE using a radio interface.
An F1 interface is provided between the IAB node and the IAB donor CU (see NPL 2).
[0121]
An example of connection of the IAB base stations is illustrated in Fig. 10. An IAB
donor CU 901 is connected to an IAB donor DU 902. An IAB node 903 is connected to the IAB
donor DU 902, using a radio interface. The IAB node 903 is connected to an IAB node 904,
using a radio interface. In other words, multi-stage connection of the IAB nodes may be
performed. A UE 905 is connected to the IAB node 904, using a radio interface. A UE 906
may be connected to the IAB node 903 using a radio interface, or a UE 907 may be connected to
the IAB donor DU 902 using a radio interface. A plurality of IAB donor DUs 902 may be
connected to the IAB donor CU 901, a plurality of IAB nodes 903 may be connected to the IAB
donor DU 902, or a plurality of IAB nodes 904 may be connected to the IAB node 903.
[0122]
A Backhaul Adaptation Protocol (BAP) layer is provided in connection between the IAB
donor DU and the IAB node and connection between the IAB nodes (see NPL 29). The BAP
layer performs operation such as routing of received data to the IAB donor DU and/or the IAB
node and mapping of the received data to an RLC channel (see NPL 29).
[0123]
As an example of a configuration of the IAB donor CU, a configuration similar to that of
the CU 215 is used.
[0124]
As an example of a configuration of the IAB donor DU, a configuration similar to that of
the DU 216 is used. In the protocol processing unit of the IAB donor DU, processing of the BAP
layer, for example, processing such as provision of a BAP header in downlink data, routing to the
IAB node, and removal of the BAP header in uplink data, is performed.
[0125]
29
As an example of a configuration of the IAB node, a configuration except the EPC
communication unit 401, such another base station communication unit 402, and the 5GC
communication unit 412 illustrated in Fig. 5 may be used.
[0126]
Transmission and reception processing in the IAB node will be described with reference
to Fig. 5 and Fig. 10. Transmission and reception processing of the IAB node 903 in
communication between the IAB donor CU 901 and the UE 905 will be described. In uplink
communication from the UE 905 to the IAB donor CU 901, a radio signal from the IAB node 904
is received by the antenna(s) 408 (a part or all of the antennas 408-1 to 408-4). The received
signal is converted from a radio reception frequency into a baseband signal in the frequency
converting unit 407, and is subjected to demodulation processing in the demodulating unit 409.
The demodulated data is delivered to the decoder unit 410, and is subjected to decoding processing
such as error correction. The decoded data is delivered to the protocol processing unit 403, and
is subjected to protocol processing of the MAC, the RLC, and the like used for communication
with the IAB node 904, for example, operation such as removal of a header in each protocol.
Routing to the IAB donor DU 902 using a BAP header is performed, and protocol processing of
the RLC, the MAC, and the like used for communication with the IAB donor DU 902, for example,
operation such as provision of a header in each protocol, is performed. The data subjected to the
protocol processing is delivered to the encoder unit 405, and is subjected to encoding processing
such as error correction. There may be data that is directly output from the protocol processing
unit 403 to the modulating unit 406 without being subjected to the encoding processing. The
encoded data is subjected to modulation processing in the modulating unit 406. In the modulating
unit 406, MIMO precoding may be performed. The modulated data is converted into a baseband
signal, and is then output to the frequency converting unit 407 to be converted into a radio
transmission frequency. Subsequently, transmission signals are transmitted to the IAB donor DU
902 from the antennas 408-1 to 408-4. Similar processing is also performed in downlink
communication from the IAB donor CU 901 to the UE 905.
[0127]
Transmission and reception processing similar to that of the IAB node 903 is also
performed in the IAB node 904. In the protocol processing unit 403 of the IAB node 903, as
processing of the BAP layer, for example, processing such as provision of a BAP header in uplink
communication, routing to the IAB node 904, and removal of the BAP header in downlink
communication is performed.
[0128]
30
In 3GPP, introducing an IoT devices (which may be hereinafter referred to as “device”)
having ultra-low power consumption into the mobile communication system has been discussed.
It is proposed that the IoT device having ultra-low power consumption performs communication
with the UE or base station by using a communication scheme different from the communication
scheme used in air interfaces defined in conventional 3GPP (NPLs 31, 33, and 34). In the mobile
communication system in which the device is incorporated, it is assumed that the UE
communicating with the device has to perform communication with the NW. A method for
allowing such a UE to communicate with the device and the NW will be disclosed.
[0129]
Communication between a device and a UE is direct communication between the device
and the UE, and communication between a device and a base station is direct communication
between the device and the base station. Communication between a UE and another UE is direct
communication between the UEs, and communication between a UE and a base station is direct
communication between the UE and the base station.
[0130]
The communication between the device and the UE may be communication between the
device and the UE for communication between the device and the NW via the UE.
[0131]
In order to incorporate the device into the mobile communication system, the base station
transmits, to the UE, a configuration for UE-device communication. The base station may
transmit, to the UE, a configuration for device data transmission from the UE to the base station.
[0132]
A method for transmitting the above-described configurations from the base station to the
UE will be disclosed. The base station may broadcast the above-described pieces of
configuration information. The base station may include the pieces of configuration information
in an SIB. The base station may broadcast the SIB. The SIB can be transmitted to the entire
cell, so that UEs in the cell area can receive the pieces of configuration information. The base
station may transmit the pieces of configuration information to the UE in a dedicated manner.
The base station may transmit the pieces of configuration information to the UE by using RRC
signaling. An RRC message including the pieces of configuration information may be
transmitted. For example, An RRCReconfiguration message including the pieces of
configuration information may be transmitted. The transmission dedicated for the UE can be
performed, and therefore, the pieces of configuration information dedicated for the UE can be
transmitted.
31
[0133]
Another method will be disclosed. The base station may transmit the pieces of
configuration information by using MAC signaling. For example, a MAC CE including the
pieces of configuration information may be transmitted. The base station may multiplex the
pieces of configuration information with other MAC data, and send them to the UE. This enables
efficient transmission because the pieces of configuration information can be transmitted together
with other data. Another method will be disclosed. The base station may transmit the pieces of
configuration information by using L1/L2 signaling. The base station may include the pieces of
configuration information in DCI. The base station may transmit the DCI to the UE on the
PDCCH. This enables early transmission of the pieces of configuration information.
[0134]
Fourteen examples of the configuration information for UE-device communication are
disclosed below.
[0135]
(1) Communication frequency information.
(2) Communication time information.
(3) Communication period information.
(4) Time information.
(5) Communication area information.
(6) Grouping information.
(7) Reception quality information.
(8) Information about a service.
(9) Information about a device.
(10) Information about a transmission source node.
(11) Information to be transmitted from the UE to the device.
(12) Information about a beam.
(13) Information about interference.
(14) Combination of (1) to (13).
[0136]
(1) is information about a frequency at which UE-device communication is performed.
For example, it may include a frequency, a bandwidth, and the like. For example, it may be BWP
information. For example, it may be information about an RB (Resource Block) or a subcarrier.
For example, it may be information about a subcarrier spacing. (1) may include one or more
pieces of the above-described information. (2) is information about a time at which UE-device
32
communication is performed. For example, it may include a communication start time, a
communication termination time, a communication time interval, a periodicity, an offset, and the
like. For example, it may be information about a symbol length. (2) may include one or more
pieces of the above-described information. The time unit may be a time or a time unit used
between the UE and the base station. For example, the time unit used between the UE and the
base station may be a symbol unit, a slot unit, a subframe unit, a TTI (Transmission Timing
Interval) unit, a radio frame unit, or the like. Using the time unit used between the UE and the
base station facilitates control for the UE. (3) is information about a period of time during which
UE-device communication is performed. It may be a service period of time for UE-device
communication. The communication is performed within the communication period, for
example, at the time disclosed in (2). (3) may include one or more pieces of the above-described
information. The communication period may be configured by using a timer. UE-device
communication may be enabled with the timer configuration, and the UE-device communication
may be disabled with expiration of the timer. By configuring the communication time in (2) and
the communication period in (3), for example, it is possible to provide a service that requires
scheduled or periodic communication with the device.
[0137]
(4) is information for configuring a time for the UE. An absolute time on the NW side
may be transmitted. (4) may include one or more pieces of the above-described information.
The UE may derive, for example, a communication time with the device based on information
about a time at which a signal is received. In this way, it is possible to use synchronized time
between UEs. The time information may be notified to the device. The time information may
be transmitted from the base station or UE to the device. For example, it may be used for
allowing the device to derive information about a data acquisition time. This enables to use
synchronized time information between devices.
[0138]
(5) is information about an area where UE-device communication can be performed. It
may be information about an area where UE-device communication cannot be performed (or UEdevice communication is prohibited). It may be a list including one or more areas. It may be a
list of areas for communication between devices. (5) may include one or more pieces of the
above-described information. The area information may be, for example, a beam, a cell, a base
station, an RNA (RAN Notification Area), a TA, a PLMN, an NPN (Non-Public Network), or the
like. The area information may be information for identifying the above-described information,
for example, an identifier. It may be, for example, an identifier of a beam with which UE-device
33
communication can be performed.
[0139]
One or more devices may be grouped. (6) is information about a group to which one or
more devices belong. It may be information about which device is assigned to which group. (6)
may include one or more pieces of the above-described information. A grouping method may be
used, and the grouping method may be, for example, grouping by service, grouping by device type,
or grouping by area. Service types may include, for example, a device for an asset management
service, a device for a temperature management service, a service dedicated for a certain company,
and the like. Device types may include, for example, a velocity/acceleration sensor device, a
temperature sensor device, a pressure sensor device, and the like. Information for identifying the
device group may be provided. The information may be, for example, a device group identifier.
There may be provided information that associates an identifier of a device group with a device
identifier belonging to the device group.
[0140]
(7) is information about a quality of reception from the device with which UE-device
communication can be performed. It may be information about a quality of reception from the
device with which UE-device communication cannot be performed. (7) may include one or more
pieces of the above-described information. The reception quality information may include, for
example, a reception quality, a received power, a RSSI (Received Signal Strength Indicator), a
SINR (Signal to Interference plus Noise Ratio), and the like. The reception quality information
may be, for example, an error rate. The reception quality information may be a BER (Bit Error
Rate), or a FER (Frame Error Rate). For the reception quality information, there may be
configured a predetermined value at which UE-device communication can be performed or cannot
be performed. A threshold may be provided.
[0141]
(8) is information about a service that uses UE-device communication. For example,
services may include, for example, a device for asset management service, a device for temperature
management service, a service dedicated for a certain company, and the like. The services may
include, for example, eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type
Communication), and URLLC (Ultra-Reliability Low Latency Communication). (8) may
include one or more pieces of the above-described information. Information for identifying a
service may be provided. The information may be, for example, a service identifier. There may
be provided information that associates a service identifier with a device identifier corresponding
the service identifier. There may be provided information that associates a service identifier with
34
a group identifier corresponding to the service identifier. The information may be, for example,
information about an Application Function (AF) or Application Server (AS) used for a service.
The information may be, for example, an address.
[0142]
(9) is information about a device that can communicate with the UE. The information
may be information about a device that cannot communicate with the UE (or a device that is
prohibited from communicating with the UE). It may be information for identifying a device, for
example, an identifier. For example, it may be a device name. For example, it may be a sensor
name. (9) may include one or more pieces of the above-described information. A list of pieces
of information about one or more devices may be provided.
[0143]
(10) is information about a transmission source node that transmits the configuration for
UE-device communication. It may be information about a transmission source node that
transmits the configuration for device data transmission. It may be information indicating from
which node the configuration is transmitted. The information may indicate a node from which
the configuration is transmitted directly or a node from which the configuration is transmitted
indirectly. For example, the node may be an AF, a CN node, a MnS (Management Service), a
base station, or the like. The CN node may be, for example, an AMF, a PCF, or the like. The
MnS may be, for example, a MaS (Management System). The UE that has received the
information can recognize from which node the configuration is transmitted.
[0144]
(11) is information transmitted from the UE to the device. The information may be data
to be transmitted to the device, or configuration information for UE-device communication. The
UE transmits the information to the device.
[0145]
(12) is information about a beam with which the UE communicates with the device. It
may be information about a beam formed by the UE. It may be information about a beam formed
by the base station. The information may be information for identifying a beam, for example, an
identifier of the beam.
[0146]
(13) is information about interference in UE-device communication. For example, it
may be information about interference being received by the device. It may be information about
interference being given by the device. It may be information about interference caused by the
transmission and reception of two or more radio schemes within the UE. It may be information
35
about interference being received by another UE. The information about the interference may
include, for example, a radio scheme causing interference, a radio scheme being subject to
interference, a frequency causing interference, a frequency being subject to interference, a time
causing interference, a time being subject to interference, power causing interference, power being
subject to interference, information about a device causing interference, and information about a
device being subject to interference. The information about interference may be information
about interference avoidance. The UE can acquire the information about interference in UEdevice communication. For example, by using the above-described pieces of information, it is
possible to reduce interference in UE-device communication.
[0147]
One or a plurality of configurations for UE-device communication disclosed above may
be provided. There may be provided information for identifying the configuration for UEdevice communication, for example, an identifier thereof. The base station may transmit the
identifier to the UE in association with the configuration. A list of one or a plurality of
configurations may be provided. The list may include an identifier for one or a plurality of
configurations to be configured.
[0148]
Upon receiving the configuration for UE-device communication from the base station,
the UE performs UE-device communication using the configuration information. For example,
the UE transmits a data transmission indication to the device using the configuration information,
and receives data transmitted in response to the indication.
[0149]
The UE transmits the data acquired from the device (this data may be referred to as
"device data" in the following description) to a destination node to which the device data is to be
transmitted. The base station configures the UE for allowing the UE to transmit the device data.
Seven examples of the configuration for device data transmission, which is transmitted from the
base station to the UE, are disclosed below.
[0150]
(1) Information about a device.
(2) Information about a group.
(3) Information about a service.
(4) Transmission timing configuration and/or information about a transmission timing.
(5) Information about a transmission destination node.
(6) Information about a node used for device data communication.
36
(7) Combination of (1) to (6).
[0151]
(1) is information indicating from which device the device data is transmitted. The
information may be, for example, information for identifying a device, for example, an identifier
thereof. (1) may include one or more pieces of the above-described information. A list of
pieces of information about one or more devices may be provided. The information about the
device may be the number of devices. A maximum number of devices may be configured for the
number of devices that transmit device data. In a case where the UE receives data from a
predetermined number of devices, the UE may transmit the data, and therefore, the predetermined
number of devices may be used.
[0152]
(2) is information indicating from which group of devices the device data is transmitted.
The information may be information for identifying a device group, for example, an identifier
thereof. (2) may include one or more pieces of the above-described information. A list of
pieces of information about one or more device groups may be provided. The information may
be information that associates a device group identifier with a device identifier belonging to the
group.
[0153]
(3) is information indicating from which service device the device data is transmitted.
The information may be information for identifying a service, for example, an identifier thereof.
(3) may include one or more pieces of the above-described information. A list of pieces of
information about one or more services may be provided. The information may be information
that associates a service identifier with a device identifier for the service.
[0154]
(4) is information about a timing configuration for transmitting the device data from the
UE. Eight examples of information about a transmission timing configuration are disclosed
below.
[0155]
(4-1) Transmission time configuration.
(4-2) Periodic transmission.
(4-3) After UE-device communication is terminated.
(4-4) After a time configured for UE-to-device communication is terminated.
(4-5) After device data is received.
(4-6) Event trigger.
37
(4-7) After a device data transmission indication is received.
(4-8) Combination of (4-1) to (4-7).
[0156]
In the case of (4-1), the UE transmits the device data at a configured transmission time.
The transmission time may include, for example, a transmission start time, a transmission
termination time, a transmission duration time, and the like. The transmission time may be
included in the information about the transmission timing. This enables to flexibly configure the
timing of device data transmission from the UE.
[0157]
In the case of (4-2), the UE transmits the device data at a configured periodicity.
Information on a periodicity and offset may be included in the information about the transmission
timing. For example, this is useful in a case where UE-device communication is periodic. The
periodicity may be equal to or an integer multiple of a periodicity configured in the configuration
for UE-device communication. The standards, etc. may statically define that the periodicity may
be equal to or an integer multiple of a periodicity configured in the configuration for UE-device
communication. This simplifies control.
[0158]
In the case of (4-3), the UE transmits the device data after UE-device communication is
terminated. It may be configured that the UE transmits the device data immediately after the
communication is terminated. Alternatively, it may be configured to transmit the device data
after a predetermined period of time has elapsed since the communication is terminated. For
example, this configuration can be applied to a case where UE-device communication is not
periodic. The predetermined period of time may be included in the information about the
transmission timing. If the predetermined period of time is set to 0, it may be configured to
transmit the device data immediately after the predetermined period of time has elapsed since the
communication is terminated.
[0159]
In the case of (4-4), the UE transmits the device data after a time configured for UEdevice communication is terminated. It may be configured that the UE transmits the device data
immediately after the time configured for communication is terminated. Alternatively, it may be
configured to transmit the device data after a predetermined period of time has elapsed since the
time configured for communication is terminated. The predetermined period of time may be
included in the information about the transmission timing. If the predetermined period of time is
set to 0, it may be configured to transmit the device data immediately after the predetermined
38
period of time has elapsed since the time configured for communication is terminated. As the
time configured for UE-device communication, the information included in the configuration
information for UE-device communication may be used.
[0160]
In the case of (4-5), the UE transmits the device data after receiving the device data. It
may be configured that the UE transmits the device data immediately after receiving the device
data. Alternatively, it may be configured to transmit the device data after a predetermined period
of time has elapsed since the device data is received. For example, this configuration can be
applied to a case where it is not known when UE-device communication is performed. The
predetermined period of time may be included in the information about the transmission timing.
If the predetermined period of time is set to 0, it may be configured to transmit the device data
immediately after receiving the device data.
[0161]
In the case of (4-6), the UE transmits the device data when a condition configured in an
event trigger is satisfied. Five examples of the event trigger condition are disclosed below. The
event trigger condition may be included in the configuration information for device data
transmission.
[0162]
(4-6-1) Device data amount.
(4-6-2) Number of devices.
(4-6-3) Number of times device data is received.
(4-6-4) Number of communications with a device.
(4-6-5) Combination of (4-6-1) to (4-6-4).
[0163]
Regarding (4-6-1), when the UE has received a predetermined amount of device data, the
UE transmits the device data. The predetermined amount of device data may be configured for
each device. For example, it can be configured according to characteristics of each device. The
predetermined amount of device data may be configured for each device or for each two or more
devices. For example, this enables to reduce the amount of configuration information. The
predetermined amount of device data may be configured for each device group. For example,
this enables control using the total device data amount of one or more devices belonging to a device
group. The predetermined amount of device data may be configured for each service. For
example, this enables control using the total device data amount of one or more devices for a
certain service. The predetermined amount of device data may be configured per UE. For
39
example, this configuration may be applied to a case where it is not predetermined which device
the UE is to communicate with.
[0164]
Regarding (4-6-2), when the UE receives device data from a predetermined number of
devices, the UE transmits the device data received from the devices. The predetermined number
of devices may be configured for each device group, for each service, or for each UE. This
provides the technical advantages as described above.
[0165]
Regarding (4-6-3), when the UE has received the device data from the device a
predetermined number of times, the UE transmits the device data received from the device.
There may be one or more devices. The predetermined number of times the device data is
received may be configured for each device, for one or more devices, for each device group, for
each service, or for each UE. This provides the technical advantages as described above.
[0166]
Regarding (4-6-4), when the UE has communicated with the device a predetermined
number of times, the UE transmits the device data received from the device. There may be one
or more devices. The predetermined number of times the UE communicates with the device may
be configured for each device, for one or more devices, for each device group, for each service, or
for each UE. This provides the technical advantages as described above.
[0167]
The predetermined amount may be included in the configuration information for device
data transmission.
[0168]
In the case of (4-7), when the UE receives the device data transmission indication from
the base station, the UE transmits the device data. It may be configured that the UE transmits the
device data immediately after receiving the device data transmission indication. Alternatively, it
may be configured to transmit the device data after a predetermined period of time has elapsed
since the device data transmission indication is received. The predetermined period of time may
be included in the information about the transmission timing. If the predetermined period of time
is set to 0, it may be configured to transmit the device data immediately after the communication
is terminated. The predetermined period of time may be included in the configuration
information for device data transmission. The base station can indicate the timing of device data
transmission from the UE. The device data transmission timing can be dynamically controlled.
[0169]
40
(5) is information about a transmission destination node of the device data. The
information may indicate to which node the device data is to be transmitted. It may indicate a
node to which the device data is transmitted directly, or a node to which the device data is
transmitted indirectly. The transmission destination node may be, for example, an AS, a CN node,
a MnS, a base station, or the like. The CN node may be, for example, an NF (Network Function),
an AMF, an SMF, an UPF, an NWDAF (Network Data Analytics Function), an NEF, or the like.
There may be provided a node (this may be an entity or function) for managing (or collecting) the
device data in the CN. Hereinafter, the node is referred to as a “DMF (Device Management
Function)”. The MnS may be a MaS. There may be provided a node (this may be an entity or
function) for managing (or collecting) the device data in the MnS. Hereinafter, the node is
referred to as a “DCE (Device data Collection Entity)”. In this way, the UE can recognize to
which node the UE should transmit the device data.
[0170]
Regarding (6), the node is, for example, a base station, a CN node, a MnS, an AS, an AF,
or the like. Information about the node used for device data communication in (6) may be, for
example, information about a transmission route of the device data. The information may include
one or more transmission destination nodes. For example, the information may include
information about a device or UE that is a transmission source of the device data. For example,
the information may include information about a device, a UE, a base station, an AMF, a NEF
(Network Exposure Function), an AF, and the like. There may be provided information for
identifying the transmission route of the device data, for example, an identifier thereof. An
identifier for the transmission route of the device data may be associated with an identifier or
address of a node included in the transmission route. There may be provided one or more
configurations for the transmission route of the device data. In this way, the UE can recognize
the device data transmission route.
[0171]
One or a plurality of configurations for device data transmission disclosed above may be
provided. There may be provided information for identifying the configuration for device data
transmission, for example, an identifier thereof. The base station may transmit the identifier to
the UE in association with the configuration. A list of one or a plurality of configurations may
be provided. The list may include an identifier for one or a plurality of configurations to be
configured.
[0172]
Upon receiving the configuration for device data transmission from the base station, the
41
UE transmits the device data using the configuration information.
[0173]
The UE may transmit, to the base station, a request relating to the configuration for UEdevice communication. In a case where the UE does not have the configuration for UE-device
communication, the UE may transmit the request. Even in a case where the UE has the
configuration for UE-device communication, the UE may transmit the request for reconfiguration.
The base station that has received the request can recognize that the UE is requesting the
configuration for UE-device communication. Upon receiving the request, the base station may
configure UE-device communication for the UE, and transmit the configuration to the UE.
[0174]
The UE may transmit, to the base station, a request relating to the configuration for device
data transmission. The method for the configuration for UE-device communication as disclosed
above may be applied as appropriate. This provides the technical advantages as described above.
[0175]
The UE may transmit, to the base station, a request for starting UE-device communication.
The request may be the request relating to the configuration for UE-device communication. The
base station that has received the request can recognize that the UE is requesting UE-device
communication. Upon receiving the request, the base station may configure UE-device
communication for the UE, and transmit the configuration to the UE.
[0176]
The UE may transmit, to the base station, a request for starting device data transmission.
The method for the request for starting UE-device communication as disclosed above may be
applied as appropriate. This provides the technical advantages as described above.
[0177]
The UE may transmit, to the base station, an activation/deactivation (hereinafter referred
to as act/deact) request relating to the configuration for UE-device communication. In a case
where the base station has already configured one or more configurations for UE-device
communication, the base station that has received the request may transmit the configuration to be
activated/deactivated. The UE can perform UE-device communication by using the
configuration.
[0178]
The UE may transmit, to the base station, an act/deact request relating to the configuration
for device data transmission. In a case where the base station has already configured one or more
configurations for device data transmission, the base station that has received the request may
42
transmit the configuration to be activated/deactivated. The UE can perform device data
transmission by using the configuration.
[0179]
The base station may transmit, to the UE, a start/termination indication for UE-device
communication. The base station may transmit an identifier of the configuration for UE-device
communication used for communication to be started/terminated. For example, the base station
may transmit the identifier together with the indication or transmit the indication including the
identifier.
[0180]
The base station may transmit, to the UE, a start/termination indication for device data
transmission. The base station may transmit an identifier of the configuration for device data
transmission used for communication to be started/terminated. For example, the base station may
transmit the identifier together with the indication or transmit the indication including the identifier.
[0181]
The base station may transmit, to the UE, an act/deact relating to the configuration for
UE-device communication. The base station may transmit an identifier of the configuration for
UE-device communication to be activated/deactivated. In a case where one or more
configurations for UE-device communication have been already configured, it is no longer
necessary to have all configurations enabled. This simplifies UE processing and reduces power
consumption.
[0182]
The base station may transmit, to the UE, an act/deact relating to the configuration for
device data transmission. The base station may transmit an identifier of the configuration for
device data transmission to be activated/deactivated. In a case where one or more configurations
for device data transmission have been already configured, it is no longer necessary to have all
configurations enabled. This simplifies UE processing and reduces power consumption.
[0183]
The base station may reconfigure, for the UE, the configuration for UE-device
communication. The base station may modify the configuration for UE-device communication
for the UE. In a case where the base station may modify the configuration for UE-device
communication for the UE, the base station may notify the UE of part or all of pieces of
information about the configuration. The base station may notify the UE of only pieces of
information to be modified, as part of pieces of information about the configuration. The abovedescribed configuration method for UE-device communication may be appropriately applied to
43
the method for the base station to reconfigure or modify the configuration for UE-device
communication for the UE.
[0184]
The base station may reconfigure, for the UE, the configuration for device data
transmission. The base station may modify the configuration for device data transmission for the
UE. In a case where the base station may modify the configuration for device data transmission
for the UE, the base station may notify the UE of part or all of pieces of information about the
configuration. The base station may notify the UE of only pieces of information to be modified,
as part of pieces of information about the configuration. The above-described configuration
method for device data transmission may be appropriately applied to the method for the base
station to reconfigure or modify the configuration for device data transmission for the UE.
[0185]
The base station may reconfigure, for the UE, configuration used for UE-device
communication. The base station may modify the configuration used for UE-device
communication for the UE. The base station may transmit, to the UE, an identifier of the
configuration used for UE-device communication. The base station may transmit, to the UE, an
identifier of a modified configuration used for UE-device communication.
[0186]
The act/deact may be used for the above-described reconfiguration or modification. The
base station may deactivate, for the UE, the configuration before modification which is currently
used for UE-device communication. The base station may transmit an identifier of the
configuration to be deactivated. The base station may activate for the UE, the configuration after
modification which is to be used for UE-device communication. The base station may transmit
an identifier of the configuration to be activated.
[0187]
The act/deact may be used for the above-described reconfiguration or modification. The
base station may deactivate, for the UE, the configuration before modification which is currently
used for device data transmission. The base station may transmit an identifier of the
configuration to be deactivated. The base station may activate, for the UE, the configuration after
modification which is to be used for device data transmission. The base station may transmit an
identifier of the configuration to be activated. This enables to reconfigure the configuration used
for UE-device communication early. The UE and/or base station may discard the configuration
that has been deactivated for a predetermined period of time. The base station may notify the UE
of the predetermined period of time. The predetermined period of time may be included, for
44
example, in the configuration for UE-device communication. For example, this enables to reduce
the memory amount of the UE.
[0188]
The base station may reconfigure or modify the configuration for UE-device
communication when indicating, to the UE, start/termination for UE-device communication.
The base station may reconfigure or modify the configuration for device data transmission when
indicating, to the UE, start/termination for device data transmission. The above-described
methods may be applied as appropriate.
[0189]
The above embodiments allow to reconfigure or modify the configuration, and therefore,
flexible control suited to the communication situation can be performed.
[0190]
A method for releasing the configuration for UE-device communication will be disclosed.
The base station notifies the UE of release of the configuration for UE-device communication.
The above-described methods for notifying the configuration for UE-device communication may
be applied to the method for notifying the release as appropriate. The UE can receive the release
of the configuration for UE-device communication. Upon receiving the release of the
configuration for UE-device communication, the UE releases the configuration for UE-device
communication being currently configured. The release notified to the UE by the base station
may include information for identifying the configuration for UE-device communication to be
released. The UE that has received the release may use the information to identify the
configuration for UE-device communication to be released. Upon receiving the release of the
configuration for UE-device communication, the UE may release all the configurations for UEdevice communication being currently configured.
[0191]
Upon receiving the release of the configuration for UE-device communication, the UE
releases the configuration for UE-device communication. The UE may discard the configuration
information for UE-device communication to be released. By releasing the configuration in this
manner, for example, in a case where UE-device communication is not performed, the UE does
not need to retain unnecessary configurations for UE-device communication. The memory and
the like of the UE can be used efficiently.
[0192]
The base station may notify the UE of the release of the configuration for device data
transmission. For the method for notifying the release, the above-described method for notifying
45
the configuration for device data transmission may be applied. The UE can receive the release
of the configuration for device data transmission. Upon receiving the release of the configuration
for device data transmission, the UE releases the configuration for device data transmission being
currently configured. The release notified to the UE by the base station may include information
for identifying the configuration for device data transmission to be released. The UE that has
received the release may use the information to identify the configuration for device data
transmission to be released. Upon receiving the release of the configuration for device data
transmission, the UE may release all the configurations for device data transmission being
currently configured.
[0193]
After releasing the configuration for device data transmission, the UE may clear the
device data remaining in a buffer. The UE can use the buffer capacity of the UE for other
purposes at an early stage. In another method, after releasing the configuration for device data
transmission, the UE may transmit the device data remaining in the buffer. For example, the UE
may transmit the device data until there is no more device data in the buffer. For example, the
UE may release the configuration for device data transmission at the end of service. This allows
the UE to transmit the device data up to the end of service.
[0194]
Configuration for the processing of transmitting the device data in the buffer after
receiving the release of the configuration for device data transmission described above may be
provided. The base station may notify the UE of the transmission processing method. For
example, regarding information about the transmission processing method, the base station may
include the transmission processing method in the configuration for UE-device communication or
the configuration for device data transmission, and transmit it to the UE. This enables flexible
control suitable for the situations of the UE and base station and the service contents.
[0195]
Upon receiving the configuration for UE-device communication, the UE starts UE-device
communication. Upon receiving the release of the configuration for UE-device communication,
the UE terminates the UE-device communication. In another method, the UE may start UEdevice communication upon receipt of the start indication for UE-device communication. The
UE may terminate the UE-device communication upon receipt of the termination indication for
UE-device communication. In another method, the UE may start UE-device communication
upon receipt of the act relating to the configuration for UE-device communication. The UE may
terminate the UE-device communication upon receipt of the deact relating to the configuration for
46
UE-device communication.
[0196]
Information indicating whether or not the device data is terminated may be provided.
For example, the device may generate the information. The device may notify the UE of the
information indicating whether or not the device data is terminated. In another method, the UE
may generate the information. The UE may transmit the information to the base station. The
base station may send the information to the CN node. The information may be transmitted
together with the device data or separately from the device data. In this way, the UE, base station
or CN node that has received the information can recognize that the transmission of device data
from the device has ended.
[0197]
The UE may store the device data received from the device. A buffer for storing the
device data may be provided in the UE. The device data may be stored, for example, on a perdevice or per-device group basis. The device data may be stored in association with a device
identifier or device group identifier. The device data may be stored, for example, per UE-device
communication. This enables flexible control in handling the device data and in transmitting the
device data from the UE to the base station.
[0198]
An upper limit may be configured on the number of UE-device communications to
receive the device data corresponding to a single data transmission to the base station. For
example, when the number of communications exceeds the upper limit, the UE may not store the
device data. Alternatively, when the number of communications reaches the upper limit, the UE
may not perform further UE-device communication. Alternatively, when the number of
communications exceeds the upper limit, the UE may clear the oldest device data. The UE may
clear the oldest device data and store device data acquired in new UE-device communication.
When the device data is transmitted, the number of communications may be cleared. The device
data may be transmitted when the UE-device communication has been performed a predetermined
number of times. For example, the limit can be configured on the number of UE-device
communications to simplify control for the UE.
[0199]
A lower limit may be configured on the number of UE-device communications to receive
the device data corresponding to a single data transmission to the base station. For example,
when the number of communications falls below the lower limit, the UE may not transmit the
device data. Alternatively, when the number of communications reaches the lower limit, the UE
47
may transmit the device data. When the UE transmits the device data, the number of
communications may be cleared. For example, by limiting the number of UE-device
communications required for device data transmission, the device data communication load from
the UE to the base station can be reduced.
[0200]
The base station may transmit the upper limit and/or lower limit for the number of
communications to the UE. The upper limit and/or lower limit may be included in the
configuration for UE-device communications or the configuration for device data transmission.
The upper and lower limits for the number of communications can be configured. This enables
flexible control.
[0201]
The UE transmits the device data to the base station using the configuration for device
data transmission received from the base station. The UE starts transmitting the device data upon
receipt of the configuration for device data transmission. The UE terminates transmitting the
device data upon receipt of the release of the configuration for device data transmission. In
another method, the UE may start transmitting the device data upon receipt of the start indication
for device data transmission. The UE may terminate the device data transmission upon receipt
of the termination indication for device data transmission. In another method, the UE may start
transmitting the device data upon receipt of the act relating to the configuration for device data
transmission. The UE may terminate the device data transmission upon receipt of the deact
relating to the configuration for device data transmission.
[0202]
A method of transmitting the device data from the UE to the base station will be disclosed.
The UE may transmit the device data to the base station using RRC signaling. An RRC message
including the device data may be transmitted. A larger amount of data can be transmitted. The
device data may be included, for example, in an ULInformationTransfer message or
RRCReconfigurationComplete message and transmitted. The UE may include the device data in
a NAS message and transmit it using RRC signaling, for example. In another method, an RRC
message for device data transmission may be newly provided. This enables to provide a message
suitable for the configuration for device data transmission and the device data to be transmitted.
[0203]
Another method will be disclosed. The UE may transmit the device data to the base
station using MAC signaling. For example, a MAC CE including the device data may be
transmitted. The UE may multiplex the device data with other MAC data and transmit them to
48
the base station. This enables efficient transmission because the device data can be transmitted
together with other data.
[0204]
Another method will be disclosed. The UE may transmit the device data to the base
station using L1/L2 signaling. For example, the device data may be included in UCI. The UE
may include the device data in the UCI and transmit it on the PUCCH. This enables device data
communication between the UE and the base station earlier.
[0205]
Another method will be disclosed. The UE may transmit the device data to the base
station in Random Access (RA) processing. For example, the UE may include the device data in
a Msg3 and transmit it in 4-step RA process, or may include the device data in a MsgA and transmit
it in 2-step RA process. This enables device data communication between the UE and the base
station earlier.
[0206]
Fig. 11 is a diagram illustrating a sequence example in which the UE transmits device
data acquired from the device to the base station. In Step ST1101, the UE being connected to the
base station (may be in RRC_Connected state) notifies the base station of information indicating
that the UE has the capability to perform communication with the device. The information
indicating that the UE has the capability to perform communication with the device may be
information indicating that the UE supports a RAT (Radio Access Technology) or communication
method used for communication with the device. The information may be the number of devices
with which the UE can communicate. The information may be information about a frequency
for communication with the device. The information about the frequency for communication
may be a frequency band. The information may be a combination of the above-described pieces
of information. The information may be included in UE capability.
[0207]
In Step ST1102, the base station transmits, to the UE, the configuration for UE-device
communication and the configuration for device data transmission. For example, RRC signaling
may be used for this transmission. For example, an RRCReconfiguration message including the
configurations may be transmitted. The UE that has received the configurations can receive
configuration information for communication with the device and configuration information for
transmitting device data to the base station. In Step ST1103, the UE that has received the
configuration for UE-device communication communicates with the device using the
configuration information. For example, in a case where UE-device communication is
49
configured to be performed periodically, the UE communicates with the device periodically.
Upon receiving data from the device, the UE stores the device data in Step ST1104. The device
data may be stored in the buffer provided in the UE. The device data may be stored in the buffer
until the device data is transmitted to the base station.
[0208]
In Step ST1105, the UE transmits the device data to the base station using the
configuration for device data transmission received in Step ST1102. For example, in a case
where the UE is configured to transmit the device data in the same periodicity as the periodicity
of UE-device communication, the UE transmits the device data received in each periodicity to the
base station. For example, in a case where the UE is configured to transmit the device data when
the amount of device data stored in the buffer exceeds a predetermined amount, the UE transmits
the device data to the base station when the amount of device data stored in UE-device
communication exceeds the predetermined amount. The base station can receive the device data
transmitted from the UE. The configuration for device data transmission transmitted in Step
ST1102 may be transmitted using separate signaling from signaling for the configuration for UEdevice communication. For example, RRC signaling may be used for the device data
transmission in Step ST1105. For example, an RRCReconfigurationComplete message
including the device data may be transmitted.
[0209]
The UE may store device data-related information. The UE may transmit the device
data-related information to the base station. The details of the device data-related information
will be described later. In Step ST1104, the UE may store the device data-related information
together with the device data. In Step ST1105, the UE may transmit the device data-related
information to the base station. For example, in a case where the configuration for device data
transmission includes configuration information for transmitting the device data-related
information, the UE may store the device data-related information together with the device data in
Step ST1104, and transmit the device data-related information together with the device data in
Step ST1105. The base station can receive the device data-related information.
[0210]
In a case where the configuration for UE-device communication and/or the configuration
for device data transmission are modified, the base station transmits the respective modifications
of the configurations to the UE in Step ST1106. For example, RRC signaling may be used for
transmitting the configuration modifications. For example, an RRCReconfiguration message
including the configuration modifications may be transmitted. Upon receiving the modification
50
of the configuration for UE-device communication, the UE communicates with the device using
the modified configuration information in Step ST1107. Upon receiving data from the device,
the UE stores the device data in Step ST1108.
[0211]
The UE transmits the device data to the base station in Step ST1109 using the
modification of the configuration for device data transmission received in Step ST1106. The
base station can receive the device data transmitted from the UE. The modification of the
configuration for device data transmission sent in Step ST1106 may be transmitted using separate
signaling from signaling for the modification of the configuration for UE-device communication.
For example, RRC signaling may be used for the device data transmission in Step ST1109. For
example, an RRCReconfigurationComplete message including the device data may be transmitted.
[0212]
In Step ST1109, the UE may transmit the device data-related information to the base
station. The base station can receive the device data-related information.
[0213]
In Step ST1110, the base station transmits, to the UE, release of the configuration for UEdevice communication and release of the configuration for device data transmission. For
example, RRC signaling may be used for this transmission. For example, an
RRCReconfiguration message including the release configurations may be transmitted. Upon
receiving the release of the configuration for UE-device communication, the UE terminates the
UE-device communication at Step ST1111. Upon receipt of the release of the configuration for
device data transmission, the UE terminates the device data transmission to the base station in Step
ST1111. The release of the configuration for device data transmission may be transmitted in
separate signaling from signaling for the release of the configuration for UE-device
communication. The method disclosed above may be applied to the transmission processing of
the device data in the buffer when the UE receives the release of the configuration for device data
transmission.
[0214]
The above embodiment enables UE-device communication and transmission of device
data received from the device to the base station. The base station can receive the device data
from the device via the UE. This enables communication between the device and the NW.
[0215]
The PUSCH may be used for device data transmission from the UE to the base station.
The UE transmits the device data to the base station on the PUSCH. The UE may transmit a
51
Scheduling Request (SR) to the base station to request scheduling of PUSCH for device data
transmission. The base station that has received the SR may transmit, to the UE, scheduling
information relating to the PUSCH for device data transmission. Upon receiving the scheduling
information relating to the PUSCH for device data transmission from the base station, the UE
transmits the device data with the PUSCH using the information.
[0216]
The base station may transmit, to the UE, DCI including the scheduling information
relating to the PUSCH for device data transmission. A new DCI may be provided for scheduling
relating to the PUSCH for device data transmission. The DCI including the scheduling
information relating to the PUSCH for device data transmission may be detected using an RNTI
(Radio Network Temporary Identifier) of the UE. In another method, the RNTI for device data
transmission may be different from an RNTI for data transmission of existing services. A new
RNTI may be provided for detecting the DCI including the scheduling information relating to the
PUSCH for device data transmission. The UE can recognize whether DCI is scheduling
information for device data transmission or scheduling information for data transmission of
existing services. The UE can selectively receive those DCIs.
[0217]
The base station may preconfigure, for the UE, the PUSCH for device data transmission.
For example, the base station may configure a CG (Configured Grant) for device data transmission.
The CG for device data transmission may be CG type 1 or CG type 2. This enables to reduce the
amount of signaling. Further, since the SR is not required, the device data can be transmitted
early at a device data transmission timing from the UE to the base station. The base station may
transmit, to the UE, the configuration for device data transmission including the CG configuration.
The configuration for device data transmission and the CG configuration used for device data
transmission may be transmitted in association with each other. The UE can recognize which CG
configuration is to be used for device data transmission.
[0218]
When the PUSCH for device data transmission is configured using the CG, an RNTI for
the CG may be provided. The UE may detect and receive DCI for the CG using the RNTI for
the CG. This allows the UE to selectively receive either DCI used for the CG for device data
transmission or DCI for the CG used for data transmission of existing services.
[0219]
A case where the UE communicates with a plurality of devices will be disclosed. The
configuration for UE-device communication is provided for each device. The configuration
52
information for UE-device communication may be provided per device. This enables to
configure the configuration information for UE-device communication suitable for each device.
The configuration for device data transmission may be provided for each device. The
configuration information for device data transmission may be provided per device. This enables
to configure the configuration information for device data transmission suitable for device data of
each device.
[0220]
The UE may store device data for each device. The UE may store a device identifier
and device data in association with each other. This allows to identify which device the device
data belongs to. The UE may transmit the device data for each device to the base station. The
UE transmits the device data to the base station using the configuration for device data
transmission for each device.
[0221]
In this way, the UE can transmit the device data acquired from each device to the base
station even when the UE communicates the plurality of devices. This enables configurations for
UE-device communication and device data transmission that are suitable for services using devices,
and therefore, the QoS required for each service can be satisfied, for example.
[0222]
Fig. 12 is a diagram illustrating a sequence example in which the UE transmits device
data acquired from a plurality of devices to the base station. The example in Fig. 12 illustrates
two devices (device #1 and device #2). The steps common to those of Fig. 11 are denoted by the
same step numbers, and common description is omitted.
[0223]
In Step ST1102, the base station transmits, to the UE, the configuration for UE-device
communication and configuration for device data transmission for each device. In Step ST1201,
the UE communicates with the device #1 using the configuration for UE-device communication
configured for the device #1. In Step ST1202, the UE stores the device data received from the
device #1 in the buffer of the UE. In Step ST1203, the UE transmits the device data to the base
station using the configuration for device data transmission for the device #1 received in Step
ST1102. The base station can receive the device data of the device #1 transmitted from the UE.
[0224]
In Step ST1204, the UE communicates with the device #2 using the configuration for UEdevice communication configured for the device #2. In Step ST1205, the UE stores the device
data received from the device #2 in the buffer of the UE. In Step ST1206, the UE transmits the
53
device data to the base station using the configuration for device data transmission for the device
#2 received in Step ST1102. The base station can receive the device data of the device #2
transmitted from the UE.
[0225]
The example in Fig. 12 illustrates that the UE-device #2 communication is performed
after the UE-device #1 communication. However, the UE-device #1 communication period and
the UE-device #2 communication period may overlap. For example, the UE-device #1
communication and the UE-device #2 communication may be alternately performed.
[0226]
The configuration for device data transmission transmitted in Step ST1102 may be
transmitted using separate signaling from signaling for the configuration for UE-device
communication. In Steps ST1203 and ST1206, the UE may transmit device data-related
information for each device to the base station. The base station can receive the device datarelated information for each device.
[0227]
Information indicating whether or not the device data is terminated may be provided for
each device. The device may generate the information and transmit it to the UE. In another
method, the UE may generate the information. The UE may transmit the information to the base
station. The information may be transmitted together with the device data or separately from the
device data. In this way, the UE or base station that has received the information can recognize
that the transmission of device data from the device has been terminated.
[0228]
In this way, the UE can communicate with the plurality of devices and transmit the device
data received from the plurality of devices to the base station. The base station can receive the
device data from the plurality of devices via the UE. This enables to communicate between the
plurality of devices and the NW.
[0229]
Another method in which the UE communicates with the plurality of devices will be
disclosed. The configuration for UE-device communication is shared between the plurality of
devices. The configuration information for UE-device communication is commonly used among
the plurality of devices. One configuration for UE-device communication may be provided.
The same configuration is used for communication between one or more devices and the UE. For
example, the UE may communicate with one or more devices within a configured period for UEdevice communication.
54
[0230]
The configuration for device data transmission is shared between the plurality of devices.
The configuration information for device data transmission is commonly used among the plurality
of devices. One configuration for device data transmission may be provided. The same
configuration is used for transmitting device data of one or more devices. For example, the UE
may transmit device data of one or more devices in a configured periodicity for device data
transmission.
[0231]
This enables to reduce the amount of information required for configuration. Since it is
possible to communicate with one or more devices with the same configuration and to transmit
device data, the complexity of the UE control can be reduced.
[0232]
The UE may store pieces of device data for one or more devices collectively. The UE
may store a device identifier and device data in association with each other. Even in a case where
the pieces of device data for one or more devices are stored collectively, the UE can recognize
which device the piece of device data belongs to. The UE may transmit information indicating
which device the piece of device data belongs to, together with the piece of device data. For
example, the UE may associate the device identifier with the piece of device data, and transmit
them to the base station. In this way, the base station can recognize which device the piece of
device data belongs to.
[0233]
Fig. 13 is a diagram illustrating another sequence example in which the UE transmits
device data acquired from a plurality of devices to the base station. The example in Fig. 13
illustrates two devices (device #1 and device #2). The steps common to those of Fig. 11 are
denoted by the same step numbers, and common description is omitted.
[0234]
In Step ST1102, the base station transmits, to the UE, one configuration for UE-device
communication and one configuration for device data transmission. Using the received
configuration for UE-device communication, the UE communicates with the device #1 in Step
ST1301 and communicates with the device #2 in Step ST1302. For example, in a UE-device
communication time configured in the configuration for UE-device communication, the
communication between the UE and the device #1 in Step ST1301 and the communication between
the UE and the device #2 in Step ST1302 are performed.
[0235]
55
In Step ST1303, the UE stores device data received from each of the devices #1 and #2
in the buffer of the UE. The UE may store the device data received from each device in
association with an identifier of each device. This allows to recognize which device the device
data is received from. In Step ST1304, the UE transmits the device data for each of the devices
#1 and #2 to the base station using the configuration for device data transmission received in Step
ST1102. The UE may transmit the device data of each device in association with the identifier
of each device. This enables to recognize which device the device data corresponds to. The
base station can receive the device data of each of the devices #1 and #2 transmitted from the UE.
[0236]
The configuration for device data transmission transmitted in Step ST1102 may be
transmitted in separate signaling from signaling for the configuration for UE-device
communication. In Step ST1304, the UE may transmit device data-related information of each
device to the base station. The device data-related information of each device may be transmitted
in association with the device identifier. The base station can receive the device data-related
information of each device.
[0237]
Information indicating whether or not device data from the plurality of devices is
terminated may be provided. The UE may generate the information. This is useful when the
UE transmits the device data of the plurality of devices collectively. The UE may transmit the
information to the base station. The information may be transmitted together with the device
data or separately from the device data. In this way, the UE or base station that has received the
information can recognize that the transmission of device data from each device has been
terminated.
[0238]
In this way, the UE can communicate with the plurality of devices and transmit the device
data received from each of the plurality of devices to the base station. The base station can
receive the device data from each of the plurality of devices via the UE. This enables
communication between the plurality of devices and the NW. In addition, control can be
facilitated because there is no need to configure each device or to transmit device data per device.
[0239]
The methods disclosed above may be combined as appropriate. In the example of Fig.
13, the base station transmits, to the UE, one configuration for UE-device communication and one
configuration for device data transmission. However, either one of the configurations may be
configured per device as shown in the example of Fig. 12. For example, the base station may
56
transmit one configuration for UE-device communication to the UE, and transmit the configuration
for device data transmission for each device to the UE. The UE-device communication is
performed using one configuration received by the UE. The UE may transmit device data of each
device stored in the buffer of the UE to the base station using the configuration for device data
transmission for each device. The above appropriate combination of the methods enables flexible
control more suitable for services using the devices.
[0240]
The UE may communicate with the device that can communicate in a configured period
for UE-device communication. The UE may communicate with a device that has not been
explicitly indicated to the UE in advance. For example, the UE may communicate with a device
detected by the UE itself in the configured period for UE-device communication. In this way,
the UE can receive device data from the device with which the UE can communicate. The base
station can receive the device data from the device with which the UE can communicate.
[0241]
Another method will be disclosed for a case where the UE communicates with the
plurality of devices. The configuration for UE-device communication may be configured for
each device group including one or more devices. The configuration information for UE-device
communication may be configured per device group including one or more devices. The UE
communicates with one or more devices included in the device group using the same configuration.
For example, the UE may communicate with one or more devices included in the device group in
the configured period for UE-device communication.
[0242]
The configuration for device data transmission may be configured for each device group
including one or more devices. The configuration information for device data transmission may
be configured per device group including one or more devices. The UE transmits device data of
one or more devices included in the device group using the same configuration. For example,
the UE may transmit device data of one or more devices included in the device group in the
configured periodicity for device data transmission.
[0243]
This enables to reduce the amount of information required for configuration. Since it is
possible to communicate with one or more devices and transmit device data with the same
configuration, the complexity of UE control can be reduced. In addition, by providing the
configuration for each device group, it is possible to make configuration more suitable for each
device group.
57
[0244]
For example, the device group may be provided for each service. A device group
including devices used for a certain service may be provided. For example, the device group may
be provided for each area. A device group including devices in a certain area may be provided.
Device groups may be predefined. In another method, a NW node may determine device groups.
Information for identifying a device group, for example, an identifier, may be provided. A device
group identifier and an identifier of each device included in the device group may be associated
with each other. The NW node transmits information about one or more device groups to the UE.
The information about the device group may include, for example, information about devices
included in the device group, information about a service, information about an area, and the like.
The above pieces of information may be included in the configuration for UE-device
communication or in the configuration for device data transmission. The UE can recognize
which device group the configuration is configured for.
[0245]
Depending on each service, the configuration for UE-device communication and/or the
configuration for device data transmission may be configured individually for each UE, commonly
for a plurality of UEs, or for each group. The base station may make such configuration for each
service that uses devices for communication. The NW node may make such configuration.
This allows for flexible configuration more suitable for each service.
[0246]
The UE may store device data received from devices in association with the device group
identifier. For example, the UE can store the device data per service or per area. The UE may
store data received from devices in association with the device group identifier and the device
identifier. This enables to store the device data not only for each device group but also for each
device.
[0247]
The UE transmits the device data to the base station using the configuration for device
data transmission configured for each device group. The UE may transmit the device data
received from one or more devices included in the device group to the base station. The UE may
associate the device group identifier and device data with each other, and transmit them to the base
station. The base station can recognize which device group the device data is received from.
The UE may associate the device group identifier, device identifier and device data with each other,
and transmit them to the base station. The base station can recognize not only which device
group the device data belongs to but also which device the device data belongs to.
] A communication system comprising:
a base station supporting a fifth generation radio access system;
a communication terminal configured to connect to the base station; and
a device configured to connect to the base station or the communication terminal, wherein
the base station is configured to transmit, to the communication terminal, configuration
information for communication being information about a configuration for communication
between the communication terminal and the device, and configuration information for device data
transmission being information about a configuration for transmitting device data acquired from
the device by the communication terminal to the base station, and
the communication terminal is configured to
perform communication with the device using the configuration information for
communication received from the base station, and
transmit the device data to the base station using the configuration information
for device data transmission received from the base station.
[Claim 2] The communication system according to claim 1, wherein
in a case where the communication terminal communicates with the device and acquires
the device data when the communication terminal is not connected to the base station,
the communication terminal is configured to store the acquired device data, and transmit
the stored device data to the base station when the communication terminal is connected to the
base station.
[Claim 3] The communication system according to claim 1 or 2, wherein
the configuration information for device data transmission includes device data
transmission route configuration information being information about a transmission route of the
device data, and
the communication terminal is configured to transmit the device data on a route according
to the device data transmission route configuration information included in the configuration
information for device data transmission received from the base station.