EP4444013A1 - Endgerät, funkkommunikationsverfahren und basisstation - Google Patents

Endgerät, funkkommunikationsverfahren und basisstation Download PDF

Info

Publication number: EP4444013A1
Authority: EP; European Patent Office
Prior art keywords: plmn; information; information related; configuration; rach
Prior art date: 2021-12-03
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.): Pending

Application number

EP21966434.9A

Other languages

English (en)

French (fr)

Other versions

EP4444013A4 (de

Inventor

Hiroki Harada

Mayuko OKANO

Shinya Kumagai

Satoshi Nagata

Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)

NTT Docomo Inc

Original Assignee

NTT Docomo Inc

Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)

2021-12-03

Filing date

2021-12-03

Publication date

2024-10-09

2021-12-03 Application filed by NTT Docomo Inc filed Critical NTT Docomo Inc

2024-10-09 Publication of EP4444013A1 publication Critical patent/EP4444013A1/de

2025-10-29 Publication of EP4444013A4 publication Critical patent/EP4444013A4/de

Status Pending legal-status Critical Current

Links

Images

Classifications

- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/002—Transmission of channel access control information
- H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

the present disclosure relates to a terminal, a radio communication method, and a base station in next-generation mobile communication systems.
LTE Long-Term Evolution
3GPP Third Generation Partnership Project
LTE Long Term Evolution
5G 5th generation mobile communication system
6G 6th generation mobile communication system
NR New Radio
3GPP Rel. 15 3GPP Rel. 15 (or later versions),” and so on
Non-Patent Literature 1 3GPP TS 36.300 V8.12.0 "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)," April, 2010
E-UTRA Evolved Universal Terrestrial Radio Access
E-UTRAN Evolved Universal Terrestrial Radio Access Network
a configuration for a specific UE is not able to be changed between a plurality of operators in some cases. In such cases, operation of communication may not be flexibly performed for each of the operators, causing communication quality enhancement to be suppressed.
an object of the present disclosure is to provide a terminal, a radio communication method, and a base station that allow operation of communication to be flexibly performed between operators.
a terminal includes: a receiving section that receives configuration information of a random access channel (RACH) associated with a Public Land Mobile Network (PLMN) ID, the configuration information being included in a system information block (SIB); and a control section that controls, based on the configuration information of the RACH, a random access procedure associated with the PLMN ID.
RACH random access channel
PLMN Public Land Mobile Network
SIB system information block
An aspect of the present disclosure allows operation of communication to be flexibly performed between operators.
RAN radio access network
NW for example, base station
a plurality of operators share an antenna site (a piece of land/steel tower or the like), so that the plurality of operators can split the station placing cost.
a plurality of operators share a distributed node (for example, Distributed Unit (DU))/central node (for example, Central Unit (CU)) (for example, share a hardware base), so that the plurality of operators can split the apparatus cost.
DU Distributed Unit
CU Central Unit
a plurality of operators share a frequency/antenna unit (for example, Radio Unit (RU)), which can enhance efficiency in resource utilization, such as that a resource not used by an operator is made available for another operator, for example.
RU Radio Unit
FIGS. 1A to 1D are each a diagram to show an example of network sharing.
FIG. 1A shows an example of site sharing.
a plurality of operators share an antenna site.
a service platform an HSS (Home Subscriber Server)/HLR (Home Location Register), core network (CN) packet switching (PS), a base station, and a cell/frequency are independent for each of the plurality of operators.
HSS Home Subscriber Server
HLR Home Location Register
CN core network
FIG. 1B shows an example of an MORAN (Multi Operator RAN).
a plurality of operators share a part of a base station (for example, hardware of the base station), in addition to an antenna site.
a service platform, an HSS/HLR, CN PS, another part of the base station (for example, software of the base station), and a cell/frequency are independent for each of the plurality of operators.
FIG. 1C shows an example of an MOCN (Multi Operator Core Network).
MOCN Multi Operator Core Network
a plurality of operators share a base station and a cell/frequency.
a service platform, an HSS/HLR, and CN PS are independent for each of the plurality of operators.
FIG. 1D shows an example of a GWCN (Gateway Core Network).
GWCN Global System for Mobile Communications
a plurality of operators share CN PS, a base station, and a cell/frequency.
a service platform and an HSS/HLR are independent for each of the plurality of operators.
the plurality of operators share the cell, so that it is desirable for a configuration to be able to be changed for each of the operators (for example, for each ID (Public Land Mobile Network ID (PLMN ID)) related to a PLMN).
PLMN ID Public Land Mobile Network ID
an operator-specific configuration is able to be configured as an RRC configuration, depending on a PLMN ID of the terminal.
UE User Equipment
the resource sharing in order for a part of a time resource of a shared cell to be available only for a terminal of a specific operator, terminals of the other operators are able to be configured not to use the part of the time resource.
a parameter for example, ServingCellConfigCommonSIB which is in system information block 1 (SIB1) and used for configuration of a random access channel (RACH) resource or the like is not provided for each of the PLMN IDs, so that a RACH resource for the UE is not able to be configured/changed for each of the operators.
SIB1 system information block 1
RACH random access channel
the inventors of the present invention came up with the idea of a method of flexibly applying/configuring an operation policy/parameter between operators, for efficient station placing/frequency utilization by resource sharing.
radio communication methods according to respective embodiments may each be employed individually, or may be employed in combination.
A/B and “at least one of A and B” may be interchangeably interpreted.
A/B/C may mean “at least one of A, B, and C.”
activate, deactivate, indicate, select, configure, update, determine, and the like may be interchangeably interpreted.
support may be interchangeably interpreted.
radio resource control RRC
RRC parameter RRC parameter
RRC message RRC message
IE information element
a configuration e.g., a configuration
MAC Control Element CE
update command e.g., an update command, an activation/deactivation command, and the like
the higher layer signaling may be, for example, any one or combinations of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like.
RRC Radio Resource Control
MAC Medium Access Control
the MAC signaling may use, for example, a MAC control element (MAC CE), a MAC Protocol Data Unit (PDU), or the like.
the broadcast information may be, for example, a master information block (MIB), a system information block (SIB), minimum system information (Remaining Minimum System Information (RMSI)), other system information (OSI), or the like.
MIB master information block
SIB system information block
RMSI Remaining Minimum System Information
OSI system information
the physical layer signaling may be, for example, downlink control information (DCI), uplink control information (UCI), or the like.
DCI downlink control information
UCI uplink control information
an index, an identifier (ID), an indicator, a resource ID, and the like may be interchangeably interpreted.
a sequence, a list, a set, a group, a cluster, a subset, and the like may be interchangeably interpreted.
a specific ID an ID related to a Public Land Mobile Network (PLMN), a PLMN ID, a PLMN identifier, a PLMN Identity, PLMN identifier information, PLMN Identity information, PLMN ID information, information for identifying an operator, an ID for identifying an operator, an ID for each operator, a group ID, a PLMN group ID, and the like may be interchangeably interpreted.
PLMN Public Land Mobile Network
a PLMN an operator
an operator policy a configuration for each operator
a configuration per operator and the like
SIB1 used for initial access
SIB1 a first SIB
SIB2 a specific SIB
a UE may receive information related to a frequency/time resource configured separately for each of the specific IDs.
the frequency/time resource may be, for example, a frequency resource to be configured for the UE at the time of initial access.
the frequency/time resource may be an initial DL/UL bandwidth part (BWP).
the information related to such a specific frequency/time resource may be included in configuration information of a serving cell (for example, ServingCellConfigCommonSIB) included in broadcast information (for example, system information (for example, SIB/SIB1)).
the information related to the specific frequency/time resource may be included in at least one of DL configuration (for example, downlinkConfigCommon/DownlinkConfigCommonSIB), UL configuration (for example, uplinkConfigCommon/UplinkConfigCommonSIB), and supplementary UL (supplementaryUplink/UplinkConfigCommonSIB) that are included in the configuration information of the serving cell (for example, ServingCellConfigCommonSIB) included in the system information.
DL configuration for example, downlinkConfigCommon/DownlinkConfigCommonSIB
UL configuration for example, uplinkConfigCommon/UplinkConfigCommonSIB
supplementary Uplink/UplinkConfigCommonSIB supplementaryUplink/UplinkCon
the information related to the specific frequency/time resource may be, for example, at least one of information related to an initial DL BWP (for example, initialDownlinkBWP/BWP-DownlinkCommon) and information related to an initial UL BWP (for example, initialUplinkBWP/BWP-UplinkCommon) .
the information related to the specific frequency/time resource may be associated with a specific ID (for example, PLMN ID).
the configuration information of the serving cell (for example, ServingCellConfigCommonSIB) included in the system information (for example, SIB/SIB1) may include information related to one or a plurality of specific IDs (for example, PLMN IDs).
information related to a plurality of specific IDs may be information indicating a list of specific IDs.
the information related to one or a plurality of specific IDs may be included in at least one of the DL configuration (for example, downlinkConfigCommon/DownlinkConfigCommonSIB), the UL configuration (for example, uplinkConfigCommon/UplinkConfigCommonSIB), and the supplementary UL (supplementaryUplink/UplinkConfigCommonSIB) that are included in the configuration information of the serving cell (for example, ServingCellConfigCommonSIB) included in the system information.
the DL configuration for example, downlinkConfigCommon/DownlinkConfigCommonSIB
the UL configuration for example, uplinkConfigCommon/UplinkConfigCommonSIB
the supplementary UL supplementaryUplink/UplinkConfigCommonSIB
the UE may determine, based on the specific IDs (for example, PLMN IDs) included in the SIB/SIB1, a specific frequency resource configuration for each of the specific IDs.
specific IDs for example, PLMN IDs
SIB/SIB1 a specific frequency resource configuration for each of the specific IDs.
the number (maximum number, for example, one) of frequency resources (for example, BWPs) configurable per specific ID may be defined in a specification.
the upper limit (for example, maxPLMN) of the number (total number) of frequency resources (for example, BWPs) for different specific IDs may be defined in a specification.
FIG. 2A is a diagram to show an example of association related to PLMN IDs according to a first embodiment.
Operator #1 with the PLMN ID being #1 Operator #2 with the PLMN ID being #2, and Operator #3 with the PLMN ID being #3 are defined.
a value of a PLMN ID and the number of PLMN IDs, and an operator number and the number of operators are each only an example, which are not limited to any example shown in each drawing.
ServingCellConfigCommonSIB information related to a PLMN ID (for example, plmn-Identity/plmn-IdentityList) is included in ServingCellConfigCommonSIB.
ServingCellConfigCommonSIB is defined for each PLMN ID (each operator).
DownlinkConfigCommonSIB and UplinkConfigCommonSIB included in ServingCellConfigCommonSIB, initialDownlinkBWP included in DownlinkConfigCommonSIB, and initialUplinkBWP included in UplinkConfigCommonSIB are defined for each PLMN ID (each operator).
FIG. 2B is a diagram to show another example of the association related to PLMN IDs according to the first embodiment.
correspondence relationship between the PLMN IDs and the operators is similar to that in FIG. 2A .
information related to a PLMN ID is included in DownlinkConfigCommonSIB and in UplinkConfigCommonSIB.
DownlinkConfigCommonSIB and UplinkConfigCommonSIB are defined for each PLMN ID (each operator).
initialDownlinkBWP included in DownlinkConfigCommonSIB and initialUplinkBWP included in UplinkConfigCommonSIB are defined for each PLMN ID (each operator).
a certain parameter may be configured separately for each PLMN ID and another parameter may be configured commonly for a plurality of PLMN IDs.
initialUplinkBWP may be configured for each PLMN ID and initialDownlinkBWP may be configured commonly for a plurality of PLMN IDs.
initialDownlinkBWP may be configured for each PLMN ID and initialUplinkBWP may be configured commonly for a plurality of PLMN IDs.
At least one specific ID for example, PLMN ID
configuration of an SSB different from an SSB detected for reception of an SIB/SIB1 may be supported.
a UE may receive an SSB different from an SSB detected for reception of an SIB/SIB1.
the configuration information of the serving cell (for example, ServingCellConfigCommonSIB) included in the system information (for example, SIB/SIB1) may include information related to an SSB.
the information related to the SSB may be associated with a specific ID (for example, PLMN ID).
the information related to the SSB may be at least one of information related to a frequency position of the SSB (for example, absoluteFrequencySSB), information related to a subcarrier spacing of the SSB (for example, ssbSubcarrierSpacing), information related to an SSB index (information related to an SSB index that the transmission is assumed by the UE, for example, ssb-PositionsInBurst), and information related to a periodicity of the SSB (for example, ssb-periodicityServingCell).
information related to a frequency position of the SSB for example, absoluteFrequencySSB
information related to a subcarrier spacing of the SSB for example, ssbSubcarrierSpacing
information related to an SSB index information related to an SSB index that the transmission is assumed by the UE, for example, ssb-PositionsInBurst
a periodicity of the SSB for example
Association of the information related to the SSB with a specific ID may be made in a parameter of a specific frequency resource.
the parameter of the specific frequency resource may be a parameter of an initial DL BWP (for example, initialDownlinkBWP/BWP-DownlinkCommon).
a UE may assume that an SSB associated with a certain specific ID is included in an initial DL BWP of the specific ID.
a case may be supported in which an SSB associated with a certain specific ID is not included in an initial DL BWP of the specific ID.
a UE may assume that only an SSB associated with a specific ID (for example, PLMN ID) for the UE is an SSB of a serving cell and monitor the SSB.
a specific ID for example, PLMN ID
a UE may assume that both an SSB associated with a specific ID (for example, PLMN ID) for the UE and an SSB detected for reception of system information are SSBs of a serving cell and monitor the SSBs.
a specific ID for example, PLMN ID
a UE may use, for determination of rate match, an SSB associated with an ID different from a specific ID (for example, PLMN ID) for the UE.
a specific ID for example, PLMN ID
a frequency resource (for example, initial DL/UL BWP) can be configured separately for each specific ID (for example, PLMN ID).
a UE may receive information related to a frequency/time resource configured separately for each of the specific IDs.
the frequency/time resource may be, for example, a time resource to be configured for the UE at the time of initial access.
the frequency/time resource may be a UL/DL configuration in time division duplex (TDD).
the information related to such a specific frequency/time resource may be included in configuration information of a serving cell (for example, ServingCellConfigCommonSIB) included in broadcast information (for example, system information (for example, SIB/SIB1)).
the information related to the specific frequency/time resource may be a UL/DL configuration in TDD (for example, tdd-UL-DL-ConfigurationCommon/TDD-UL-DL-ConfigCommon) .
the information related to the specific frequency/time resource may be associated with a specific ID (for example, PLMN ID).
the configuration information of the serving cell (for example, ServingCellConfigCommonSIB) included in the system information (for example, SIB/SIB1) may include information related to one or a plurality of specific IDs (for example, PLMN IDs).
the UL/DL configuration in TDD (for example, tdd-UL-DL-ConfigurationCommon/TDD-UL-DL-ConfigCommon) included in the configuration information of the serving cell (for example, ServingCellConfigCommonSIB) included in the system information may include the information related to one or a plurality of specific IDs (for example, PLMN IDs).
the UE may determine, based on the specific IDs (for example, PLMN IDs) included in the SIB/SIB1, a specific time resource configuration for each of the specific IDs.
specific IDs for example, PLMN IDs
SIB/SIB1 a specific time resource configuration for each of the specific IDs.
FIG. 3A is a diagram to show an example of association related to PLMN IDs according to a second embodiment.
correspondence relationship between the PLMN IDs and the operators is similar to that in FIG. 2A or the like.
ServingCellConfigCommonSIB information related to a PLMN ID (for example, plmn-Identity/plmn-IdentityList) is included in ServingCellConfigCommonSIB.
ServingCellConfigCommonSIB is defined for each PLMN ID (each operator).
tdd-UL-DL-ConfigurationCommon included in ServingCellConfigCommonSIB is defined for each PLMN ID (each operator).
FIG. 3B is a diagram to show another example of the association related to PLMN IDs according to the second embodiment.
correspondence relationship between the PLMN IDs and the operators is similar to that in FIG. 2A or the like.
tdd-UL-DL-ConfigurationCommon information related to a PLMN ID (for example, plmn-Identity/plmn-IdentityList) is included in tdd-UL-DL-ConfigurationCommon.
tdd-UL-DL-ConfigurationCommon is defined for each PLMN ID (each operator).
at least one of parameters for example, a parameter indicating a subcarrier spacing (referenceSubcarrierSpacing), a parameter indicating a first TDD UL/DL pattern (pattern1), and a parameter indicating a second TDD UL/DL pattern (pattern2) included in tdd-UL-DL-ConfigurationCommon is defined for each PLMN ID (each operator).
a certain parameter may be configured separately for each PLMN ID and another parameter may be configured commonly for a plurality of PLMN IDs.
the parameter indicating the first TDD UL/DL pattern (pattern1) and the parameter indicating the second TDD UL/DL pattern (pattern2) may be configured for each PLMN ID, and the parameter indicating the subcarrier spacing (referenceSubcarrierSpacing) may be configured commonly for a plurality of PLMN IDs.
the parameter indicating the first TDD UL/DL pattern may be configured for each PLMN ID
the parameter indicating the subcarrier spacing (referenceSubcarrierSpacing) and the parameter indicating the second TDD UL/DL pattern (pattern2) may be configured commonly for a plurality of PLMN IDs.
the parameter indicating the second TDD UL/DL pattern may be configured for each PLMN ID
the parameter indicating the subcarrier spacing (referenceSubcarrierSpacing) and the parameter indicating the first TDD UL/DL pattern (pattern1) may be configured commonly for a plurality of PLMN IDs.
the parameter indicating the subcarrier spacing may be configured for each PLMN ID
the parameter indicating the first TDD UL/DL pattern (pattern1) and the parameter indicating the second TDD UL/DL pattern (pattern2) may be configured commonly for a plurality of PLMN IDs.
At least one of information related to an available DL/UL resource and information related to an unavailable DL/UL resource may be included in the UL/DL configuration in TDD (for example, tdd-UL-DL-ConfigurationCommon/TDD-UL-DL-ConfigCommon). This allows configuration and notification of an available/unavailable resource to be performed for each operator.
a time resource (for example, UL/DL configuration in TDD) can be configured separately for each specific ID (for example, PLMN ID).
RACHs random access channels
PLMN IDs PLMN IDs
a RACH, a PRACH, a random access preamble, a random access, a random access procedure, and the like may be interchangeably interpreted.
a UE may receive information related to a RACH configuration configured separately for each of the specific IDs.
the UE may control, based on the information related to the RACH configuration, a random access procedure (RACH operation).
RACH operation a random access procedure
the UE may determine a time resource for the RACH, a frequency resource for the RACH, and a preamble of the RACH that are to be configured for each of the specific IDs.
the information related to the RACH configuration may be a RACH configuration (for example, RACH-ConfigCommon).
the RACH configuration (for example, RACH-ConfigCommon) may be included in the information related to the initial UL BWP (for example, initialUplinkBWP/BWP-UplinkCommon) .
the information related to the RACH configuration may be associated with a specific ID (for example, PLMN ID).
the configuration information of the serving cell (for example, ServingCellConfigCommonSIB) included in the system information (for example, SIB/SIB1) may include information related to one or a plurality of specific IDs (for example, PLMN IDs).
the UE may determine association between the specific ID(s) and the information related to the RACH configuration included in the information related to the initial UL BWP in the configuration information of the serving cell.
the information related to the initial UL BWP may include the information related to one or a plurality of specific IDs (for example, PLMN IDs).
the UE may determine association between the specific ID(s) and the information related to the RACH configuration included in the information related to the initial UL BWP.
the RACH configuration may include the information related to one or a plurality of specific IDs (for example, PLMN IDs).
the UE may determine association between at least one of information related to a time resource/format configuration for a PRACH (for example, prach-ConfigurationIndex), information related to a start position of a frequency resource for the PRACH (for example, msg1-FrequencyStart), and information related to a sequence of the PRACH (for example, prach-RootSequenceIndex) that are included in the RACH configuration (for example, RACH-ConfigCommon) and the information related to one or a plurality of specific IDs (for example, PLMN IDs).
prach-ConfigurationIndex information related to a time resource/format configuration for a PRACH
information related to a start position of a frequency resource for the PRACH for example, msg1-FrequencyStart
a sequence of the PRACH for example, prach-RootSequenceInde
the UE may determine, based on the specific IDs (for example, PLMN IDs) included in the RACH configuration, a RACH configuration for each of the specific IDs.
specific IDs for example, PLMN IDs
FIG. 4A is a diagram to show an example of association related to PLMN IDs according to a third embodiment.
correspondence relationship between the PLMN IDs and the operators is similar to that in FIG. 2A or the like.
BWP-UplinkCommon information related to a PLMN ID (for example, plmn-Identity/plmn-IdentityList) is included in BWP-UplinkCommon.
BWP-UplinkCommon is defined for each PLMN ID (each operator).
RACH-ConfigCommon included in BWP-UplinkCommon is defined for each PLMN ID (each operator).
FIG. 4B is a diagram to show another example of the association related to PLMN IDs according to the third embodiment.
correspondence relationship between the PLMN IDs and the operators is similar to that in FIG. 2A or the like.
RACH-ConfigCommon information related to a PLMN ID (for example, plmn-Identity/plmn-IdentityList) is included in RACH-ConfigCommon.
RACH-ConfigCommon is defined for each PLMN ID (each operator).
At least one of parameters (for example, information related to a time resource/format configuration for a PRACH (for example, prach-ConfigurationIndex), information related to a start position of a frequency resource for the PRACH (for example, msg1-FrequencyStart), and information related to a sequence of the PRACH (for example, prach-RootSequenceIndex)) included in RACH-ConfigCommon is defined for each PLMN ID (each operator).
parameters for example, information related to a time resource/format configuration for a PRACH (for example, prach-ConfigurationIndex), information related to a start position of a frequency resource for the PRACH (for example, msg1-FrequencyStart), and information related to a sequence of the PRACH (for example, prach-RootSequenceIndex)) included in RACH-ConfigCommon is defined for each PLMN ID (each operator).
a certain parameter may be configured separately for each PLMN ID and another parameter may be configured commonly for a plurality of PLMN IDs.
the information related to the time resource/format configuration for the PRACH may be configured for each PLMN ID
the information related to the start position of the frequency resource for the PRACH for example, msg1-FrequencyStart
the information related to the sequence of the PRACH for example, prach-RootSequenceIndex
the information related to the time resource/format configuration for the PRACH for example, prach-ConfigurationIndex
the information related to the start position of the frequency resource for the PRACH for example, msg1-FrequencyStart
the information related to the sequence of the PRACH for example, prach-RootSequenceIndex
prach-RootSequenceIndex may be configured commonly for a plurality of PLMN IDs.
the information related to the time resource/format configuration for the PRACH for example, prach-ConfigurationIndex
the information related to the sequence of the PRACH for example, prach-RootSequenceIndex
the information related to the start position of the frequency resource for the PRACH for example, msg1-FrequencyStart
msg1-FrequencyStart may be configured commonly for a plurality of PLMN IDs.
the information related to the start position of the frequency resource for the PRACH (for example, msg1-FrequencyStart) and the information related to the sequence of the PRACH (for example, prach-RootSequenceIndex) may be configured for each PLMN ID, and the information related to the time resource/format configuration for the PRACH (for example, prach-ConfigurationIndex) may be configured commonly for a plurality of PLMN IDs.
the information related to the sequence of the PRACH may be configured for each PLMN ID
the information related to the time resource/format configuration for the PRACH for example, prach-ConfigurationIndex
the information related to the start position of the frequency resource for the PRACH for example, msg1-FrequencyStart
msg1-FrequencyStart may be configured commonly for a plurality of PLMN IDs.
the information related to the start position of the frequency resource for the PRACH may be configured for each PLMN ID
the information related to the time resource/format configuration for the PRACH for example, prach-ConfigurationIndex
the information related to the sequence of the PRACH for example, prach-RootSequenceIndex
the UE may include, in a RACH (for example, Message 1 (PRACH)/Message 3 (RRCSetupRequest)/Message A), information related to a specific ID (for example, PLMN ID) and transmit the RACH.
a RACH for example, Message 1 (PRACH)/Message 3 (RRCSetupRequest)/Message A
PLMN ID information related to a specific ID
the information related to the specific ID may be information of a specific ID (PLMN ID) or may be other information associated with the information of the specific ID (PLMN ID).
a PRACH resource (at least one of a time/frequency resource and a preamble) associated with a specific ID (PLMN ID) can be separately determined/configured and a network (base station) can recognize a specific ID (PLMN ID) selected by the UE from a PRACH resource detected.
a random access channel can be configured separately for each specific ID (for example, PLMN ID).
a UE may monitor/detect/receive, besides a specific system information block (for example, SIB1), a different SIB for each specific ID (for example, PLMN ID).
SIB1 system information block
PLMN ID specific ID
the different SIB may be an SIB (for example, at least one of SIB2 to SIB14) that is other than SIB1 and that is defined in an existing specification or may be an SIB (for example, which may be referred to as SIB N (N is any alphanumeric character)) newly defined different from an SIB defined in an existing specification.
SIB1X may be referred to as SIB1X.
SIB1X the different SIB
SIB1X the different SIB
SIB1X the different SIB
Information/parameter related to an SIB associated with a specific ID may be configured in SIB1.
the UE may monitor, based on the information related to the SIB associated with the specific ID configured in SIB1, the SIB associated with the specific ID.
the information related to the SIB associated with the specific ID may be, for example, at least one of information related to a periodicity of the SIB (for example, si-Periodicity), information related to a window length of system information (for example, si-WindowLength), and information related to a configuration for transmission request for the system information (for example, si-RequestConfig) .
a periodicity of the SIB for example, si-Periodicity
information related to a window length of system information for example, si-WindowLength
si-RequestConfig information related to a configuration for transmission request for the system information
At least one of the pieces of information related to the SIB associated with the specific ID may be associated with a specific ID (for example, PLMN ID).
FIG. 5 is a diagram to show an example of association related to PLMN IDs according to a fourth embodiment.
correspondence relationship between the PLMN IDs and the operators is similar to that in FIG. 2A or the like.
SIB1 includes a parameter regarding SIB1X.
the parameter regarding SIB1X includes information related to a PLMN ID (for example, plmn-Identity/plmn-IdentityList).
the parameter regarding SIB1X (SIB1X) is defined for each PLMN ID (each operator).
At least one of parameters (for example, the information related to a periodicity of the SIB (SIB1X) (for example, si-Periodicity), the information related to the window length of the system information (for example, si-WindowLength), and the information related to the configuration for transmission request for the system information (for example, si-RequestConfig)) that are included in the parameter regarding SIB1X is defined for each PLMN ID (each operator).
SIB1X the information related to a periodicity of the SIB
the information related to the window length of the system information for example, si-WindowLength
the information related to the configuration for transmission request for the system information for example, si-RequestConfig
a certain parameter may be configured separately for each PLMN ID and another parameter may be configured commonly for a plurality of PLMN IDs.
the information related to the periodicity of the SIB may be configured for each PLMN ID, and the information related to the window length of the system information (for example, si-WindowLength) and the information related to the configuration for transmission request for the system information (for example, si-RequestConfig) may be configured commonly for a plurality of PLMN IDs.
the information related to the periodicity of the SIB for example, si-Periodicity
the information related to the window length of the system information for example, si-WindowLength
the information related to the configuration for transmission request for the system information for example, si-RequestConfig
the configuration for transmission request for the system information for example, si-RequestConfig
the information related to the periodicity of the SIB for example, si-Periodicity
the information related to the configuration for transmission request for the system information for example, si-RequestConfig
the information related to the window length of the system information for example, si-WindowLength
the information related to the window length of the system information for example, si-WindowLength
the information related to the window length of the system information (for example, si-WindowLength) and the information related to the configuration for transmission request for the system information (for example, si-RequestConfig) may be configured for each PLMN ID
the information related to the periodicity of the SIB (for example, si-Periodicity) may be configured commonly for a plurality of PLMN IDs.
the information related to the configuration for transmission request for the system information may be configured for each PLMN ID
the information related to the periodicity of the SIB for example, si-Periodicity
the information related to the window length of the system information for example, si-WindowLength
the information related to the configuration for transmission request for the system information may be configured for each PLMN ID
the information related to the periodicity of the SIB for example, si-Periodicity
the information related to the window length of the system information for example, si-WindowLength
the information related to the window length of the system information may be configured for each PLMN ID
the information related to the periodicity of the SIB for example, si-Periodicity
the information related to the configuration for transmission request for the system information for example, si-RequestConfig
the UE may change/overwrite, based on information notified with an SIB associated with a specific ID, at least one of the pieces of information notified with SIB1.
system information for each operator can be appropriately configured.
a configuration related to cell reselection and a configuration related to measurement in idle mode may be interchangeably interpreted.
a UE may receive information related to a RACH configuration configured separately for each of the specific IDs.
the UE may receive a specific parameter associated with a specific ID (for example, PLMN ID).
a specific ID for example, PLMN ID
Such a specific parameter may be included in a specific SIB.
the specific SIB may be an SIB (for example, SIB3/4) defined in an existing specification or may be SIB X described in the fourth embodiment.
the specific parameter may be, for example, at least one of information related to neighboring cells of the same frequency (intra-frequency)/different frequencies (inter-frequency) (for example, intraFreqNeighCellList/interFreqNeighCellList), information related to a non-target cell list for cell reselection (for example, intraFreqBlackCellList/interFreqBlackCellList), information related to a target cell list for cell reselection (for example, intraFreqWhiteCellList/interFreqWhiteCellList), and information related to a cell reselection configuration (for example, cellReselectionInfoCommon/cellReselectionServingFreqInfo/intraFreqCellRe selectionInfo/InterFreqCarrierFreqInfo) .
At least one of the specific parameters described above may be associated with a specific ID (for example, PLMN ID).
FIG. 6 is a diagram to show an example of association related to PLMN IDs according to a fifth embodiment.
PLMN #3 and Operator #3 are omitted for simplification.
a specific SIB (SIB3/4/1X) includes information related to a PLMN ID (for example, plmn-Identity/plmn-IdentityList) and a specific parameter related to cell reselection.
the specific parameter may be, for example, at least one of information related to neighboring cells of the same frequency (intra-frequency)/different frequencies (inter-frequency) (for example, intraFreqNeighCellList/interFreqNeighCellList), information related to a non-target cell list for cell reselection (for example, intraFreqBlackCellList/interFreqBlackCellList), information related to a target cell list for cell reselection (for example, intraFreqWhiteCellList/interFreqWhiteCellList), and information related to a cell reselection configuration (for example, cellReselectionInfoCommon/cellReselectionServingFreqInfo/intraFreqCellRe selectionInfo/InterFreqCarrierFreqInfo).
intra-frequency intraFreqNeighCellList/interFreqNeighCellList
intraFreqBlackCellList/interFreqBlackCellList information related to a target cell list for cell
a specific parameter related to cell reselection is defined for each PLMN ID (each operator).
a certain parameter may be configured separately for each PLMN ID and another parameter may be configured commonly for a plurality of PLMN IDs.
At least one of cell reselection and measurement in idle mode can be appropriately configured for each operator.
any configuration/parameter (for example, broadcast information) for a UE at the time of initial access/in idle mode may be configured/notified for each specific ID (for example, PLMN ID).
a specific ID for example, PLMN ID
a configuration related to the specific ID may correspond to each other in a one-to-one manner.
one configuration may be associated with one specific ID.
Specific IDs for example, PLMN IDs
a configuration related to the specific IDs may correspond to each other in a many (one or more)-to-one manner.
one configuration may be associated with a plurality of (one or more) specific IDs (for example, a specific ID list).
a cell where network sharing is performed may be a specific cell.
the cell where network sharing is performed may be an SCell, and the network sharing may be configured not to be performed in any PCell (SpCell).
the cell where network sharing is performed may be a PCell (SpCell), and the network sharing may be configured not to be performed in any SCell.
radio communication system a structure of a radio communication system according to one embodiment of the present disclosure will be described.
the radio communication method according to each embodiment of the present disclosure described above may be used alone or may be used in combination for communication.
FIG. 7 is a diagram to show an example of a schematic structure of the radio communication system according to one embodiment.
the radio communication system 1 may be a system implementing a communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR) and so on the specifications of which have been drafted by Third Generation Partnership Project (3GPP).
LTE Long Term Evolution
5G NR 5th generation mobile communication system New Radio
the radio communication system 1 may support dual connectivity (multi-RAT dual connectivity (MR-DC)) between a plurality of Radio Access Technologies (RATs).
the MR-DC may include dual connectivity (E-UTRA-NR Dual Connectivity (EN-DC)) between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR, dual connectivity (NR-E-UTRA Dual Connectivity (NE-DC)) between NR and LTE, and so on.
a base station (eNB) of LTE (E-UTRA) is a master node (MN), and a base station (gNB) of NR is a secondary node (SN).
a base station (gNB) of NR is an MN
a base station (eNB) of LTE (E-UTRA) is an SN.
the radio communication system 1 may support dual connectivity between a plurality of base stations in the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) where both of an MN and an SN are base stations (gNB) of NR).
dual connectivity NR-NR Dual Connectivity (NN-DC)
gNB base stations
the radio communication system 1 may include a base station 11 that forms a macro cell C1 of a relatively wide coverage, and base stations 12 (12a to 12c) that form small cells C2, which are placed within the macro cell C1 and which are narrower than the macro cell C1.
the user terminal 20 may be located in at least one cell.
the arrangement, the number, and the like of each cell and user terminal 20 are by no means limited to the aspect shown in the diagram.
the base stations 11 and 12 will be collectively referred to as "base stations 10," unless specified otherwise.
the user terminal 20 may be connected to at least one of the plurality of base stations 10.
the user terminal 20 may use at least one of carrier aggregation (CA) and dual connectivity (DC) using a plurality of component carriers (CCs).
CA carrier aggregation
DC dual connectivity
CCs component carriers
Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)).
the macro cell C1 may be included in FR1
the small cells C2 may be included in FR2.
FR1 may be a frequency band of 6 GHz or less (sub-6 GHz)
FR2 may be a frequency band which is higher than 24 GHz (above-24 GHz). Note that frequency bands, definitions and so on of FR1 and FR2 are by no means limited to these, and for example, FR1 may correspond to a frequency band which is higher than FR2.
the user terminal 20 may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.
TDD time division duplex
FDD frequency division duplex
the plurality of base stations 10 may be connected by a wired connection (for example, optical fiber in compliance with the Common Public Radio Interface (CPRI), the X2 interface and so on) or a wireless connection (for example, an NR communication).
a wired connection for example, optical fiber in compliance with the Common Public Radio Interface (CPRI), the X2 interface and so on
a wireless connection for example, an NR communication
IAB Integrated Access Backhaul
relay station relay station
the base station 10 may be connected to a core network 30 through another base station 10 or directly.
the core network 30 may include at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and so on.
EPC Evolved Packet Core
5GCN 5G Core Network
NGC Next Generation Core
the user terminal 20 may be a terminal supporting at least one of communication schemes such as LTE, LTE-A, 5G, and so on.
an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used.
OFDM Orthogonal frequency division multiplexing
DL downlink
UL uplink
DFT-s-OFDM Discrete Fourier Transform Spread OFDM
OFDMA Orthogonal Frequency Division Multiple Access
SC-FDMA Single Carrier Frequency Division Multiple Access
the wireless access scheme may be referred to as a "waveform.”
another wireless access scheme for example, another single carrier transmission scheme, another multi-carrier transmission scheme
a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), which is used by each user terminal 20 on a shared basis, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)) and so on, may be used as downlink channels.
PDSCH Physical Downlink Shared Channel
PBCH Physical Broadcast Channel
PDCCH Physical Downlink Control Channel
an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), which is used by each user terminal 20 on a shared basis, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)) and so on may be used as uplink channels.
PUSCH Physical Uplink Shared Channel
PUCCH Physical Uplink Control Channel
PRACH Physical Random Access Channel
SIBs System Information Blocks
PBCH Master Information Blocks
Lower layer control information may be communicated on the PDCCH.
the lower layer control information may include downlink control information (DCI) including scheduling information of at least one of the PDSCH and the PUSCH.
DCI downlink control information
DCI for scheduling the PDSCH may be referred to as "DL assignment,” “DL DCI,” and so on, and DCI for scheduling the PUSCH may be referred to as "UL grant,” “UL DCI,” and so on.
DL assignment DL DCI
UL grant UL DCI
the PDSCH may be interpreted as “DL data”
the PUSCH may be interpreted as "UL data.”
a control resource set (CORESET) and a search space may be used.
the CORESET corresponds to a resource to search DCI.
the search space corresponds to a search area and a search method of PDCCH candidates.
One CORESET may be associated with one or more search spaces.
the UE may monitor a CORESET associated with a certain search space, based on search space configuration.
One search space may correspond to a PDCCH candidate corresponding to one or more aggregation levels.
One or more search spaces may be referred to as a "search space set.” Note that a "search space,” a “search space set,” a “search space configuration,” a “search space set configuration,” a “CORESET,” a “CORESET configuration” and so on of the present disclosure may be interchangeably interpreted.
Uplink control information including at least one of channel state information (CSI), transmission confirmation information (for example, which may be also referred to as Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, and so on), and scheduling request (SR) may be communicated by means of the PUCCH.
CSI channel state information
HARQ-ACK Hybrid Automatic Repeat reQuest ACKnowledgement
ACK/NACK ACK/NACK
SR scheduling request
downlink may be expressed without a term of "link.”
various channels may be expressed without adding "Physical” to the head.
a synchronization signal (SS), a downlink reference signal (DL-RS), and so on may be communicated.
a cell-specific reference signal (CRS), a channel state information-reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), and so on may be communicated as the DL-RS.
CRS cell-specific reference signal
CSI-RS channel state information-reference signal
DMRS demodulation reference signal
PRS positioning reference signal
PTRS phase tracking reference signal
the synchronization signal may be at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS).
a signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for a PBCH) may be referred to as an "SS/PBCH block,” an "SS Block (SSB),” and so on.
SS/PBCH block an "SS Block (SSB),” and so on.
SSB SS Block
a sounding reference signal (SRS), a demodulation reference signal (DMRS), and so on may be communicated as an uplink reference signal (UL-RS).
SRS sounding reference signal
DMRS demodulation reference signal
UL-RS uplink reference signal
DMRS may be referred to as a "user terminal specific reference signal (UE-specific Reference Signal).”
FIG. 8 is a diagram to show an example of a structure of the base station according to one embodiment.
the base station 10 includes a control section 110, a transmitting/receiving section 120, transmitting/receiving antennas 130 and a communication path interface (transmission line interface) 140.
the base station 10 may include one or more control sections 110, one or more transmitting/receiving sections 120, one or more transmitting/receiving antennas 130, and one or more communication path interfaces 140.
the present example primarily shows functional blocks that pertain to characteristic parts of the present embodiment, and it is assumed that the base station 10 may include other functional blocks that are necessary for radio communication as well. Part of the processes of each section described below may be omitted.
the control section 110 controls the whole of the base station 10.
the control section 110 can be constituted with a controller, a control circuit, or the like described based on general understanding of the technical field to which the present disclosure pertains.
the control section 110 may control generation of signals, scheduling (for example, resource allocation, mapping), and so on.
the control section 110 may control transmission and reception, measurement and so on using the transmitting/receiving section 120, the transmitting/receiving antennas 130, and the communication path interface 140.
the control section 110 may generate data, control information, a sequence and so on to transmit as a signal, and forward the generated items to the transmitting/receiving section 120.
the control section 110 may perform call processing (setting up, releasing) for communication channels, manage the state of the base station 10, and manage the radio resources.
the transmitting/receiving section 120 may include a baseband section 121, a Radio Frequency (RF) section 122, and a measurement section 123.
the baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212.
the transmitting/receiving section 120 can be constituted with a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, or the like described based on general understanding of the technical field to which the present disclosure pertains.
the transmitting/receiving section 120 may be structured as a transmitting/receiving section in one entity, or may be constituted with a transmitting section and a receiving section.
the transmitting section may be constituted with the transmission processing section 1211, and the RF section 122.
the receiving section may be constituted with the reception processing section 1212, the RF section 122, and the measurement section 123.
the transmitting/receiving antennas 130 can be constituted with antennas, for example, an array antenna, or the like described based on general understanding of the technical field to which the present disclosure pertains.
the transmitting/receiving section 120 may transmit the above-described downlink channel, synchronization signal, downlink reference signal, and so on.
the transmitting/receiving section 120 may receive the above-described uplink channel, uplink reference signal, and so on.
the transmitting/receiving section 120 may form at least one of a transmit beam and a receive beam by using digital beam forming (for example, precoding), analog beam forming (for example, phase rotation), and so on.
digital beam forming for example, precoding
analog beam forming for example, phase rotation
the transmitting/receiving section 120 may perform the processing of the Packet Data Convergence Protocol (PDCP) layer, the processing of the Radio Link Control (RLC) layer (for example, RLC retransmission control), the processing of the Medium Access Control (MAC) layer (for example, HARQ retransmission control), and so on, for example, on data and control information and so on acquired from the control section 110, and may generate bit string to transmit.
PDCP Packet Data Convergence Protocol
RLC Radio Link Control
MAC Medium Access Control
the transmitting/receiving section 120 may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (as necessary), inverse fast Fourier transform (IFFT) processing, precoding, digital-to-analog conversion, and so on, on the bit string to transmit, and output a baseband signal.
transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (as necessary), inverse fast Fourier transform (IFFT) processing, precoding, digital-to-analog conversion, and so on, on the bit string to transmit, and output a baseband signal.
the transmitting/receiving section 120 may perform modulation to a radio frequency band, filtering, amplification, and so on, on the baseband signal, and transmit the signal of the radio frequency band through the transmitting/receiving antennas 130.
the transmitting/receiving section 120 may perform amplification, filtering, demodulation to a baseband signal, and so on, on the signal of the radio frequency band received by the transmitting/receiving antennas 130.
the transmitting/receiving section 120 may apply reception processing such as analog-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (as necessary), filtering, de-mapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, the processing of the RLC layer and the processing of the PDCP layer, and so on, on the acquired baseband signal, and acquire user data, and so on.
reception processing such as analog-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (as necessary), filtering, de-mapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, the processing of the RLC layer and the processing of the PDCP layer, and so on, on the acquired baseband signal, and acquire user data, and so on.
FFT fast Fourier transform
IDFT inverse discrete Fourier transform
filtering de-mapping
demodulation which
the transmitting/receiving section 120 may perform the measurement related to the received signal.
the measurement section 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, and so on, based on the received signal.
the measurement section 123 may measure a received power (for example, Reference Signal Received Power (RSRP)), a received quality (for example, Reference Signal Received Quality (RSRQ), a Signal to Interference plus Noise Ratio (SINR), a Signal to Noise Ratio (SNR)), a signal strength (for example, Received Signal Strength Indicator (RSSI)), channel information (for example, CSI), and so on.
the measurement results may be output to the control section 110.
the communication path interface 140 may perform transmission/reception (backhaul signaling) of a signal with an apparatus included in the core network 30 or other base stations 10, and so on, and acquire or transmit user data (user plane data), control plane data, and so on for the user terminal 20.
backhaul signaling backhaul signaling
the transmitting section and the receiving section of the base station 10 in the present disclosure may be constituted with at least one of the transmitting/receiving section 120, the transmitting/receiving antennas 130, and the communication path interface 140.
the transmitting/receiving section 120 may transmit configuration information of a serving cell associated with a Public Land Mobile Network (PLMN) ID, the configuration information being included in a first system information block (SIB, for example, SIB1).
the control section 110 may indicate, using the configuration information, at least one of a frequency resource and a time resource associated with the PLMN ID (first and second embodiments).
the transmitting/receiving section 120 may transmit configuration information of a random access channel (RACH) associated with a Public Land Mobile Network (PLMN) ID, the configuration information being included in a system information block (SIB, for example, SIB1).
the control section 110 may control, using the configuration information of the RACH, a random access procedure associated with the PLMN ID (third embodiment).
the transmitting/receiving section 120 may transmit configuration information of a second SIB (for example, SIB other than SIB1) associated with a Public Land Mobile Network (PLMN) ID, the configuration information being included in a first system information block (SIB, for example, SIB1).
SIB Public Land Mobile Network
the control section 110 may control, using the configuration information of the second SIB, transmission of the second SIB associated with the PLMN ID (fourth and fifth embodiments).
FIG. 9 is a diagram to show an example of a structure of the user terminal according to one embodiment.
the user terminal 20 includes a control section 210, a transmitting/receiving section 220, and transmitting/receiving antennas 230. Note that the user terminal 20 may include one or more control sections 210, one or more transmitting/receiving sections 220, and one or more transmitting/receiving antennas 230.
the present example primarily shows functional blocks that pertain to characteristic parts of the present embodiment, and it is assumed that the user terminal 20 may include other functional blocks that are necessary for radio communication as well. Part of the processes of each section described below may be omitted.
the control section 210 controls the whole of the user terminal 20.
the control section 210 can be constituted with a controller, a control circuit, or the like described based on general understanding of the technical field to which the present disclosure pertains.
the control section 210 may control generation of signals, mapping, and so on.
the control section 210 may control transmission/reception, measurement and so on using the transmitting/receiving section 220, and the transmitting/receiving antennas 230.
the control section 210 generates data, control information, a sequence and so on to transmit as a signal, and may forward the generated items to the transmitting/receiving section 220.
the transmitting/receiving section 220 may include a baseband section 221, an RF section 222, and a measurement section 223.
the baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212.
the transmitting/receiving section 220 can be constituted with a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, or the like described based on general understanding of the technical field to which the present disclosure pertains.
the transmitting/receiving section 220 may be structured as a transmitting/receiving section in one entity, or may be constituted with a transmitting section and a receiving section.
the transmitting section may be constituted with the transmission processing section 2211, and the RF section 222.
the receiving section may be constituted with the reception processing section 2212, the RF section 222, and the measurement section 223.
the transmitting/receiving antennas 230 can be constituted with antennas, for example, an array antenna, or the like described based on general understanding of the technical field to which the present disclosure pertains.
the transmitting/receiving section 220 may receive the above-described downlink channel, synchronization signal, downlink reference signal, and so on.
the transmitting/receiving section 220 may transmit the above-described uplink channel, uplink reference signal, and so on.
the transmitting/receiving section 220 may form at least one of a transmit beam and a receive beam by using digital beam forming (for example, precoding), analog beam forming (for example, phase rotation), and so on.
digital beam forming for example, precoding
analog beam forming for example, phase rotation
the transmitting/receiving section 220 may perform the processing of the PDCP layer, the processing of the RLC layer (for example, RLC retransmission control), the processing of the MAC layer (for example, HARQ retransmission control), and so on, for example, on data and control information and so on acquired from the control section 210, and may generate bit string to transmit.
the transmitting/receiving section 220 may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (as necessary), IFFT processing, precoding, digital-to-analog conversion, and so on, on the bit string to transmit, and output a baseband signal.
transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (as necessary), IFFT processing, precoding, digital-to-analog conversion, and so on, on the bit string to transmit, and output a baseband signal.
the transmitting/receiving section 220 may perform, for a certain channel (for example, PUSCH), the DFT processing as the above-described transmission processing to transmit the channel by using a DFT-s-OFDM waveform if transform precoding is enabled, and otherwise, does not need to perform the DFT processing as the above-described transmission process.
a certain channel for example, PUSCH
the transmitting/receiving section 220 may perform modulation to a radio frequency band, filtering, amplification, and so on, on the baseband signal, and transmit the signal of the radio frequency band through the transmitting/receiving antennas 230.
the transmitting/receiving section 220 may perform amplification, filtering, demodulation to a baseband signal, and so on, on the signal of the radio frequency band received by the transmitting/receiving antennas 230.
the transmitting/receiving section 220 may apply a receiving process such as analog-digital conversion, FFT processing, IDFT processing (as necessary), filtering, de-mapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, the processing of the RLC layer and the processing of the PDCP layer, and so on, on the acquired baseband signal, and acquire user data, and so on.
a receiving process such as analog-digital conversion, FFT processing, IDFT processing (as necessary), filtering, de-mapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, the processing of the RLC layer and the processing of the PDCP layer, and so on, on the acquired baseband signal, and acquire user data, and so on.
the transmitting/receiving section 220 may perform the measurement related to the received signal.
the measurement section 223 may perform RRM measurement, CSI measurement, and so on, based on the received signal.
the measurement section 223 may measure a received power (for example, RSRP), a received quality (for example, RSRQ, SINR, SNR), a signal strength (for example, RSSI), channel information (for example, CSI), and so on.
the measurement results may be output to the control section 210.
the transmitting section and the receiving section of the user terminal 20 in the present disclosure may be constituted with at least one of the transmitting/receiving section 220 and the transmitting/receiving antennas 230.
the transmitting/receiving section 220 may receive configuration information of a serving cell associated with a Public Land Mobile Network (PLMN) ID, the configuration information being included in a first system information block (SIB, for example, SIB1).
the control section 210 may determine, based on the configuration information, at least one of a frequency resource and a time resource associated with the PLMN ID (first and second embodiments).
the frequency resource may be at least one of an initial downlink bandwidth part and an initial uplink bandwidth part.
the frequency resource may be an initial downlink bandwidth part and an initial uplink bandwidth part (first embodiment).
the time resource may be a resource based on an uplink/downlink configuration for time division duplex (second embodiment).
the control section 210 may control, based on information related to a second SIB included in the configuration information, monitoring of such another system information block (first embodiment).
the transmitting/receiving section 220 may receive configuration information of a random access channel (RACH) associated with a Public Land Mobile Network (PLMN) ID, the configuration information being included in a system information block (SIB, for example, SIB1).
the control section 210 may control, based on the configuration information of the RACH, a random access procedure associated with the PLMN ID (third embodiment).
the configuration information of the RACH may be included in information related to an initial uplink bandwidth part.
the information related to the initial uplink bandwidth part may include the PLMN ID (third embodiment).
the configuration information of the RACH may include the PLMN ID and at least one of information related to a time resource and a format configuration for a physical random access channel (PRACH), information related to a start position of a frequency resource for the PRACH, and information related to a sequence of the PRACH (third embodiment).
PRACH physical random access channel
the control section 210 may report the PLMN ID for the terminal by using the RACH (third embodiment).
the transmitting/receiving section 220 may receive configuration information of a second SIB (for example, SIB other than SIB1) associated with a Public Land Mobile Network (PLMN) ID, the configuration information being included in a first system information block (SIB, for example, SIB1).
SIB Public Land Mobile Network
the control section 210 may control, based on the configuration information of the second SIB, monitoring of the second SIB associated with the PLMN ID (fourth and fifth embodiments).
the configuration information of the second SIB may include at least one of information related to a periodicity of the second SIB, information related to a window length of the second SIB, and information related to a configuration for transmission request for system information (fourth embodiment).
the control section 210 may change at least one of configurations based on the first SIB by using a configuration based on the second SIB (fourth embodiment).
the second SIB may include information related to cell reselection (fifth embodiment).
each functional block may be realized by one piece of apparatus that is physically or logically coupled, or may be realized by directly or indirectly connecting two or more physically or logically separate pieces of apparatus (for example, via wire, wireless, or the like) and using these plurality of pieces of apparatus.
the functional blocks may be implemented by combining softwares into the apparatus described above or the plurality of apparatuses described above.
functions include judgment, determination, decision, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, designation, establishment, comparison, assumption, expectation, considering, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), assigning, and the like, but function are by no means limited to these.
functional block (components) to implement a function of transmission may be referred to as a "transmitting section (transmitting unit)," a “transmitter,” and the like.
the method for implementing each component is not particularly limited as described above.
a base station, a user terminal, and so on may function as a computer that executes the processes of the radio communication method of the present disclosure.
FIG. 10 is a diagram to show an example of a hardware structure of the base station and the user terminal according to one embodiment.
the above-described base station 10 and user terminal 20 may each be formed as a computer apparatus that includes a processor 1001, a memory 1002, a storage 1003, a communication apparatus 1004, an input apparatus 1005, an output apparatus 1006, a bus 1007, and so on.
the words such as an apparatus, a circuit, a device, a section, a unit, and so on can be interchangeably interpreted.
the hardware structure of the base station 10 and the user terminal 20 may be configured to include one or more of apparatuses shown in the drawings, or may be configured not to include part of apparatuses.
processor 1001 may be implemented with one or more chips.
Each function of the base station 10 and the user terminals 20 is implemented, for example, by allowing certain software (programs) to be read on hardware such as the processor 1001 and the memory 1002, and by allowing the processor 1001 to perform calculations to control communication via the communication apparatus 1004 and control at least one of reading and writing of data in the memory 1002 and the storage 1003.
the processor 1001 controls the whole computer by, for example, running an operating system.
the processor 1001 may be configured with a central processing unit (CPU), which includes interfaces with peripheral apparatus, control apparatus, computing apparatus, a register, and so on.
CPU central processing unit
control section 110 210
transmitting/receiving section 120 220
so on may be implemented by the processor 1001.
the processor 1001 reads programs (program codes), software modules, data, and so on from at least one of the storage 1003 and the communication apparatus 1004, into the memory 1002, and executes various processes according to these.
programs programs to allow computers to execute at least part of the operations of the above-described embodiments are used.
the control section 110 (210) may be implemented by control programs that are stored in the memory 1002 and that operate on the processor 1001, and other functional blocks may be implemented likewise.
the memory 1002 is a computer-readable recording medium, and may be constituted with, for example, at least one of a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), and other appropriate storage media.
ROM Read Only Memory
EPROM Erasable Programmable ROM
EEPROM Electrically EPROM
RAM Random Access Memory
the memory 1002 may be referred to as a "register,” a "cache,” a “main memory (primary storage apparatus)” and so on.
the memory 1002 can store executable programs (program codes), software modules, and the like for implementing the radio communication method according to one embodiment of the present disclosure.
the storage 1003 is a computer-readable recording medium, and may be constituted with, for example, at least one of a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disc (Compact Disc ROM (CD-ROM) and so on), a digital versatile disc, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (for example, a card, a stick, and a key drive), a magnetic stripe, a database, a server, and other appropriate storage media.
the storage 1003 may be referred to as "secondary storage apparatus.”
the communication apparatus 1004 is hardware (transmitting/receiving device) for allowing inter-computer communication via at least one of wired and wireless networks, and may be referred to as, for example, a "network device,” a “network controller,” a “network card,” a “communication module,” and so on.
the communication apparatus 1004 may be configured to include a high frequency switch, a duplexer, a filter, a frequency synthesizer, and so on in order to realize, for example, at least one of frequency division duplex (FDD) and time division duplex (TDD).
FDD frequency division duplex
TDD time division duplex
the above-described transmitting/receiving section 120 (220), the transmitting/receiving antennas 130 (230), and so on may be implemented by the communication apparatus 1004.
the transmitting section 120a (220a) and the receiving section 120b (220b) can be implemented while being separated physically or logically.
the input apparatus 1005 is an input device that receives input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, and so on).
the output apparatus 1006 is an output device that allows sending output to the outside (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, and so on). Note that the input apparatus 1005 and the output apparatus 1006 may be provided in an integrated structure (for example, a touch panel).
bus 1007 for communicating information.
the bus 1007 may be formed with a single bus, or may be formed with buses that vary between pieces of apparatus.
the base station 10 and the user terminals 20 may be structured to include hardware such as a microprocessor, a digital signal processor (DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), and so on, and part or all of the functional blocks may be implemented by the hardware.
the processor 1001 may be implemented with at least one of these pieces of hardware.
a “channel,” a “symbol,” and a “signal” may be interchangeably interpreted.
“signals” may be “messages.”
a reference signal may be abbreviated as an “RS,” and may be referred to as a “pilot,” a “pilot signal,” and so on, depending on which standard applies.
a “component carrier (CC)” may be referred to as a "cell,” a “frequency carrier,” a “carrier frequency” and so on.
a radio frame may be constituted of one or a plurality of periods (frames) in the time domain.
Each of one or a plurality of periods (frames) constituting a radio frame may be referred to as a "subframe.”
a subframe may be constituted of one or a plurality of slots in the time domain.
a subframe may be a fixed time length (for example, 1 ms) independent of numerology.
numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel.
numerology may indicate at least one of a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a particular filter processing performed by a transceiver in the frequency domain, a particular windowing processing performed by a transceiver in the time domain, and so on.
SCS subcarrier spacing
TTI transmission time interval
a slot may be constituted of one or a plurality of symbols in the time domain (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, and so on). Furthermore, a slot may be a time unit based on numerology.
OFDM Orthogonal Frequency Division Multiplexing
SC-FDMA Single Carrier Frequency Division Multiple Access
a slot may include a plurality of mini-slots. Each mini-slot may be constituted of one or a plurality of symbols in the time domain. A mini-slot may be referred to as a "sub-slot.” A mini-slot may be constituted of symbols less than the number of slots.
a PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be referred to as "PDSCH (PUSCH) mapping type A.”
a PDSCH (or PUSCH) transmitted using a mini-slot may be referred to as "PDSCH (PUSCH) mapping type B.”
a radio frame, a subframe, a slot, a mini-slot, and a symbol all express time units in signal communication.
a radio frame, a subframe, a slot, a mini-slot, and a symbol may each be called by other applicable terms.
time units such as a frame, a subframe, a slot, mini-slot, and a symbol in the present disclosure may be interchangeably interpreted.
one subframe may be referred to as a "TTI”
a plurality of consecutive subframes may be referred to as a "TTI”
one slot or one mini-slot may be referred to as a "TTI.” That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, may be a shorter period than 1 ms (for example, 1 to 13 symbols), or may be a longer period than 1 ms.
a unit expressing TTI may be referred to as a "slot,” a "mini-slot,” and so on instead of a "subframe.”
a TTI refers to the minimum time unit of scheduling in radio communication, for example.
a base station schedules the allocation of radio resources (such as a frequency bandwidth and transmit power that are available for each user terminal) for the user terminal in TTI units.
radio resources such as a frequency bandwidth and transmit power that are available for each user terminal
TTIs may be transmission time units for channel-encoded data packets (transport blocks), code blocks, or codewords, or may be the unit of processing in scheduling, link adaptation, and so on. Note that, when TTIs are given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, codewords, or the like are actually mapped may be shorter than the TTIs.
one or more TTIs may be the minimum time unit of scheduling. Furthermore, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.
a TTI having a time length of 1 ms may be referred to as a "normal TTI” (TTI in 3GPP Rel. 8 to Rel. 12), a "long TTI,” a "normal subframe,” a “long subframe,” a “slot” and so on.
a TTI that is shorter than a normal TTI may be referred to as a "shortened TTI,” a “short TTI,” a “partial or fractional TTI,” a "shortened subframe,” a “short subframe,” a “mini-slot,” a "sub-slot,” a “slot” and so on.
a long TTI (for example, a normal TTI, a subframe, and so on) may be interpreted as a TTI having a time length exceeding 1 ms
a short TTI (for example, a shortened TTI and so on) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or longer than 1 ms.
a resource block is the unit of resource allocation in the time domain and the frequency domain, and may include one or a plurality of consecutive subcarriers in the frequency domain.
the number of subcarriers included in an RB may be the same regardless of numerology, and, for example, may be 12.
the number of subcarriers included in an RB may be determined based on numerology.
an RB may include one or a plurality of symbols in the time domain, and may be one slot, one mini-slot, one subframe, or one TTI in length.
One TTI, one subframe, and so on each may be constituted of one or a plurality of resource blocks.
RBs may be referred to as a "physical resource block (Physical RB (PRB)),” a “sub-carrier group (SCG),” a “resource element group (REG),”a “PRB pair,” an “RB pair” and so on.
PRB Physical resource block
SCG sub-carrier group
REG resource element group
a resource block may be constituted of one or a plurality of resource elements (REs).
REs resource elements
one RE may correspond to a radio resource field of one subcarrier and one symbol.
a bandwidth part (which may be referred to as a "fractional bandwidth,” and so on) may represent a subset of contiguous common resource blocks (common RBs) for certain numerology in a certain carrier.
a common RB may be specified by an index of the RB based on the common reference point of the carrier.
a PRB may be defined by a certain BWP and may be numbered in the BWP.
the BWP may include a UL BWP (BWP for the UL) and a DL BWP (BWP for the DL).
BWP for the UL
BWP for the DL DL
One or a plurality of BWPs may be configured in one carrier for a UE.
At least one of configured BWPs may be active, and a UE does not need to assume to transmit/receive a certain signal/channel outside active BWPs.
a "cell,” a “carrier,” and so on in the present disclosure may be interpreted as a "BWP.”
radio frames, subframes, slots, mini-slots, symbols, and so on are merely examples.
structures such as the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots included in a slot, the numbers of symbols and RBs included in a slot or a mini-slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and so on can be variously changed.
CP cyclic prefix
radio resources may be specified by certain indices.
the information, signals, and so on described in the present disclosure may be represented by using any of a variety of different technologies.
data, instructions, commands, information, signals, bits, symbols, chips, and so on may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any combination of these.
information, signals, and so on can be output in at least one of from higher layers to lower layers and from lower layers to higher layers.
Information, signals, and so on may be input and/or output via a plurality of network nodes.
the information, signals, and so on that are input and/or output may be stored in a specific location (for example, a memory) or may be managed by using a management table.
the information, signals, and so on to be input and/or output can be overwritten, updated, or appended.
the information, signals, and so on that are output may be deleted.
the information, signals, and so on that are input may be transmitted to another apparatus.
notification of information is by no means limited to the aspects/embodiments described in the present disclosure, and other methods may be used as well.
notification of information in the present disclosure may be implemented by using physical layer signaling (for example, downlink control information (DCI), uplink control information (UCI)), higher layer signaling (for example, Radio Resource Control (RRC) signaling, broadcast information (master information block (MIB), system information blocks (SIBs), and so on), Medium Access Control (MAC) signaling), and other signals or combinations of these.
DCI downlink control information
UCI uplink control information
RRC Radio Resource Control
MIB master information block
SIBs system information blocks
MAC Medium Access Control
RRC signaling may be referred to as an "RRC message,” and can be, for example, an RRC connection setup message, an RRC connection reconfiguration message, and so on.
MAC signaling may be notified using, for example, MAC control elements (MAC CEs).
notification of certain information does not necessarily have to be notified explicitly, and can be notified implicitly (by, for example, not notifying this certain information or notifying another piece of information).
Determinations may be made in values represented by one bit (0 or 1), may be made in Boolean values that represent true or false, or may be made by comparing numerical values (for example, comparison against a certain value).
Software whether referred to as “software,” “firmware,” “middleware,” “microcode,” or “hardware description language,” or called by other terms, should be interpreted broadly to mean instructions, instruction sets, code, code segments, program codes, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on.
software, commands, information, and so on may be transmitted and received via communication media.
communication media For example, when software is transmitted from a website, a server, or other remote sources by using at least one of wired technologies (coaxial cables, optical fiber cables, twisted-pair cables, digital subscriber lines (DSL), and so on) and wireless technologies (infrared radiation, microwaves, and so on), at least one of these wired technologies and wireless technologies are also included in the definition of communication media.
wired technologies coaxial cables, optical fiber cables, twisted-pair cables, digital subscriber lines (DSL), and so on
wireless technologies infrared radiation, microwaves, and so on
the terms “system” and “network” used in the present disclosure can be used interchangeably.
the “network” may mean an apparatus (for example, a base station) included in the network.
precoding a "precoder,” a “weight (precoding weight),” “quasi-co-location (QCL),” a “Transmission Configuration Indication state (TCI state),” a "spatial relation,” a “spatial domain filter,” a “transmit power,” “phase rotation,” an "antenna port,” an “antenna port group,” a “layer,” “the number of layers,” a “rank,” a “resource,” a “resource set,” a “resource group,” a “beam,” a “beam width,” a “beam angular degree,” an “antenna,” an “antenna element,” a “panel,” and so on can be used interchangeably.
a “base station (BS),” a “radio base station,” a “fixed station,” a “NodeB,” an “eNB (eNodeB),” a “gNB (gNodeB),” an “access point,” a “transmission point (TP),” a “reception point (RP),” a “transmission/reception point (TRP),” a “panel,” a “cell,” a “sector,” a “cell group,” a “carrier,” a “component carrier,” and so on can be used interchangeably.
the base station may be referred to as the terms such as a "macro cell,” a small cell,” a “femto cell,” a “pico cell,” and so on.
a base station can accommodate one or a plurality of (for example, three) cells.
the entire coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area can provide communication services through base station subsystems (for example, indoor small base stations (Remote Radio Heads (RRHs))).
RRHs Remote Radio Heads
the term "cell” or “sector” refers to part of or the entire coverage area of at least one of a base station and a base station subsystem that provides communication services within this coverage.
MS mobile station
UE user equipment
terminal terminal
a mobile station may be referred to as a "subscriber station,” “mobile unit,” “subscriber unit,” “wireless unit,” “remote unit,” “mobile device,” “wireless device,” “wireless communication device,” “remote device,” “mobile subscriber station,” “access terminal,” “mobile terminal,” “wireless terminal,” “remote terminal,” “handset,” “user agent,” “mobile client,” “client,” or some other appropriate terms in some cases.
At least one of a base station and a mobile station may be referred to as a "transmitting apparatus,” a “receiving apparatus,” a “radio communication apparatus,” and so on.
a base station and a mobile station may be a device mounted on a moving object or a moving object itself, and so on.
the moving object is a movable object with any moving speed, and naturally a case where the moving object is stopped is also included.
Examples of the moving object include a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a connected car, a loading shovel, a bulldozer, a wheel loader, a dump truck, a fork lift, a train, a bus, a trolley, a rickshaw, a ship and other watercraft, an airplane, a rocket, a satellite, a drone, a multicopter, a quadcopter, a balloon, and an object mounted on any of these, but these are not restrictive.
the moving object may be a moving object that autonomously travels based on a direction for moving.
the moving object may be a vehicle (for example, a car, an airplane, and the like), may be a moving object which moves unmanned (for example, a drone, an automatic operation car, and the like), or may be a robot (a manned type or unmanned type).
a base station and a mobile station also includes an apparatus which does not necessarily move during communication operation.
at least one of a base station and a mobile station may be an Internet of Things (IoT) device such as a sensor.
IoT Internet of Things
FIG. 11 is a diagram to show an example of a vehicle according to one embodiment.
a vehicle 40 includes a driving section 41, a steering section 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, right and left front wheels 46, right and left rear wheels 47, an axle 48, an electronic control section 49, various sensors (including a current sensor 50, a rotational speed sensor 51, a pneumatic sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service section 59, and a communication module 60.
various sensors including a current sensor 50, a rotational speed sensor 51, a pneumatic sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58
an information service section 59 including a communication module 60.
the driving section 41 includes, for example, at least one of an engine, a motor, and a hybrid of an engine and a motor.
the steering section 42 at least includes a steering wheel, and is configured to steer at least one of the front wheels 46 and the rear wheels 47, based on operation of the steering wheel operated by a user.
the electronic control section 49 includes a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (for example, an input/output (IO) port) 63.
the electronic control section 49 receives, as input, signals from the various sensors 50 to 58 included in the vehicle.
the electronic control section 49 may be referred to as an Electronic Control Unit (ECU).
ECU Electronic Control Unit
Examples of the signals from the various sensors 50 to 58 include a current signal from the current sensor 50 for sensing current of a motor, a rotational speed signal of the front wheels 46/rear wheels 47 acquired by the rotational speed sensor 51, a pneumatic signal of the front wheels 46/rear wheels 47 acquired by the pneumatic sensor 52, a vehicle speed signal acquired by the vehicle speed sensor 53, an acceleration signal acquired by the acceleration sensor 54, a depressing amount signal of the accelerator pedal 43 acquired by the accelerator pedal sensor 55, a depressing amount signal of the brake pedal 44 acquired by the brake pedal sensor 56, an operation signal of the shift lever 45 acquired by the shift lever sensor 57, and a detection signal for detecting an obstruction, a vehicle, a pedestrian, and the like acquired by the object detection sensor 58.
the information service section 59 includes various devices for providing (outputting) various pieces of information such as drive information, traffic information, and entertainment information, such as a car navigation system, an audio system, a speaker, a display, a television, and a radio, and one or more ECUs that control these devices.
the information service section 59 provides various pieces of information/services (for example, multimedia information/multimedia service) for an occupant of the vehicle 40, using information acquired from an external apparatus via the communication module 60 and the like.
the information service section 59 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, and the like) for receiving input from the outside, or may include an output device (for example, a display, a speaker, an LED lamp, a touch panel, and the like) for implementing output to the outside.
an input device for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, and the like
an output device for example, a display, a speaker, an LED lamp, a touch panel, and the like
a driving assistance system section 64 includes various devices for providing functions for preventing an accident and reducing a driver's driving load, such as a millimeter wave radar, Light Detection and Ranging (LiDAR), a camera, a positioning locator (for example, a Global Navigation Satellite System (GNSS) and the like), map information (for example, a high definition (HD) map, an autonomous vehicle (AV) map, and the like), a gyro system (for example, an inertial measurement apparatus (inertial measurement unit (IMU)), an inertial navigation apparatus (inertial navigation system (INS)), and the like), an artificial intelligence (AI) chip, and an AI processor, and one or more ECUs that control these devices.
the driving assistance system section 64 transmits and receives various pieces of information via the communication module 60, and implements a driving assistance function or an autonomous driving function.
the communication module 60 can communicate with the microprocessor 61 and the constituent elements of the vehicle 40 via the communication port 63.
the communication module 60 transmits and receives data (information) to and from the driving section 41, the steering section 42, the accelerator pedal 43, the brake pedal 44, the shift lever 45, the right and left front wheels 46, the right and left rear wheels 47, the axle 48, the microprocessor 61 and the memory (ROM, RAM) 62 in the electronic control section 49, and the various sensors 50 to 58, which are included in the vehicle 40.
the communication module 60 can be controlled by the microprocessor 61 of the electronic control section 49, and is a communication device that can perform communication with an external apparatus. For example, the communication module 60 performs transmission and reception of various pieces of information to and from the external apparatus via radio communication.
the communication module 60 may be either inside or outside the electronic control section 49.
the external apparatus may be, for example, the base station 10, the user terminal 20, or the like described above.
the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (may function as at least one of the base station 10 and the user terminal 20).
the communication module 60 may transmit at least one of signals from the various sensors 50 to 58 described above input to the electronic control section 49, information obtained based on the signals, and information based on an input from the outside (a user) obtained via the information service section 59, to the external apparatus via radio communication.
the electronic control section 49, the various sensors 50 to 58, the information service section 59, and the like may be referred to as input sections that receive input.
the PUSCH transmitted by the communication module 60 may include information based on the input.
the communication module 60 receives various pieces of information (traffic information, signal information, inter-vehicle distance information, and the like) transmitted from the external apparatus, and displays the various pieces of information on the information service section 59 included in the vehicle.
the information service section 59 may be referred to as an output section that outputs information (for example, outputs information to devices, such as a display and a speaker, based on the PDSCH received by the communication module 60 (or data/information decoded from the PDSCH)).
the communication module 60 stores the various pieces of information received from the external apparatus in the memory 62 that can be used by the microprocessor 61. Based on the pieces of information stored in the memory 62, the microprocessor 61 may perform control of the driving section 41, the steering section 42, the accelerator pedal 43, the brake pedal 44, the shift lever 45, the right and left front wheels 46, the right and left rear wheels 47, the axle 48, the various sensors 50 to 58, and the like included in the vehicle 40.
the base station in the present disclosure may be interpreted as a user terminal.
each aspect/embodiment of the present disclosure may be applied to the structure that replaces a communication between a base station and a user terminal with a communication between a plurality of user terminals (for example, which may be referred to as "Device-to-Device (D2D)," “Vehicle-to-Everything (V2X),” and the like).
user terminals 20 may have the functions of the base stations 10 described above.
the words such as "uplink” and “downlink” may be interpreted as the words corresponding to the terminal-to-terminal communication (for example, "sidelink”).
an uplink channel, a downlink channel, and so on may be interpreted as a sidelink channel.
the user terminal in the present disclosure may be interpreted as base station.
the base station 10 may have the functions of the user terminal 20 described above.
Operations which have been described in the present disclosure to be performed by a base station may, in some cases, be performed by an upper node of the base station.
a network including one or a plurality of network nodes with base stations it is clear that various operations that are performed to communicate with terminals can be performed by base stations, one or more network nodes (for example, Mobility Management Entities (MMEs), Serving-Gateways (S-GWs), and so on may be possible, but these are not limiting) other than base stations, or combinations of these.
MMEs Mobility Management Entities
S-GWs Serving-Gateways
aspects/embodiments illustrated in the present disclosure may be used individually or in combinations, which may be switched depending on the mode of implementation.
the order of processes, sequences, flowcharts, and so on that have been used to describe the aspects/embodiments in the present disclosure may be re-ordered as long as inconsistencies do not arise.
various methods have been illustrated in the present disclosure with various components of steps in exemplary orders, the specific orders that are illustrated herein are by no means limiting.
LTE Long Term Evolution
LTE-A LTE-Advanced
LTE-B LTE-Beyond
SUPER 3G IMT-Advanced
4th generation mobile communication system 4th generation mobile communication system
5G 5th generation mobile communication system
6G 6th generation mobile communication system
xG xth generation mobile communication system (where x is, for example, an integer or a decimal)
Future Radio Access FAA
RAT New-Radio Access Technology
NR New Radio
NX New radio access
FX Future generation radio access
GSM Global System for Mobile communications
CDMA 2000 Ultra Mobile Broadband
UMB Ultra Mobile Broadband
IEEE 802.11 Wi-Fi (registered trademark)
IEEE 802.16 WiMAX (registered trademark)
IEEE 802.20 Ultra-WideBand (UWB), Bluetooth (registered trademark), systems that use other adequate radio communication methods, next-generation systems that are enhanced, modified, created, or
phrase “based on” (or “on the basis of”) as used in the present disclosure does not mean “based only on” (or “only on the basis of”), unless otherwise specified.
the phrase “based on” (or “on the basis of”) means both “based only on” and “based at least on” (“only on the basis of” and “at least on the basis of”).
references to elements with designations such as “first,” “second,” and so on as used in the present disclosure does not generally limit the quantity or order of these elements. These designations may be used in the present disclosure only for convenience, as a method for distinguishing between two or more elements. Thus, reference to the first and second elements does not imply that only two elements may be employed, or that the first element must precede the second element in some way.
judging (determining) may encompass a wide variety of operations. For example, “judging (determining)” may be interpreted to mean making “judgments (determinations)” about judging, calculating, computing, processing, deriving, investigating, looking up, search and inquiry (for example, searching a table, a database, or some other data structures), ascertaining, and so on.
judging (determining) may be interpreted to mean making “judgments (determinations)” about receiving (for example, receiving information), transmitting (for example, transmitting information), input, output, accessing (for example, accessing data in a memory), and so on.
judging (determining) as used herein may be interpreted to mean making “judgments (determinations)” about resolving, selecting, choosing, establishing, comparing, and so on. In other words, “judging (determining)” may be interpreted to mean making “judgments (determinations)” about some operation.
judging (determining) may be interpreted as “assuming,” “expecting,” “considering,” and the like.
connection and “coupled,” or any variation of these terms as used in the present disclosure mean all direct or indirect connections or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” to each other.
the coupling or connection between the elements may be physical, logical, or a combination thereof. For example, “connection” may be interpreted as "access.”
the two elements when two elements are connected, the two elements may be considered “connected” or “coupled” to each other by using one or more electrical wires, cables and printed electrical connections, and, as some non-limiting and non-inclusive examples, by using electromagnetic energy having wavelengths in radio frequency regions, microwave regions, (both visible and invisible) optical regions, or the like.
the phrase "A and B are different” may mean that "A and B are different from each other.” Note that the phrase may mean that "A and B are each different from C.”
the terms “separate,” “be coupled,” and so on may be interpreted similarly to “different.”
the present disclosure may include that a noun after these articles is in a plural form.

Landscapes

Engineering & Computer Science (AREA)
Computer Networks & Wireless Communication (AREA)
Signal Processing (AREA)
Computer Security & Cryptography (AREA)
Mobile Radio Communication Systems (AREA)

EP21966434.9A 2021-12-03 2021-12-03 Endgerät, funkkommunikationsverfahren und basisstation Pending EP4444013A4 (de)

Applications Claiming Priority (1)

Application Number	Priority Date	Filing Date	Title
PCT/JP2021/044482 WO2023100353A1 (ja)	2021-12-03	2021-12-03	端末、無線通信方法及び基地局

Publications (2)

Publication Number	Publication Date
EP4444013A1 true EP4444013A1 (de)	2024-10-09
EP4444013A4 EP4444013A4 (de)	2025-10-29

Family

ID=86611727

Family Applications (1)

Application Number	Title	Priority Date	Filing Date
EP21966434.9A Pending EP4444013A4 (de)	2021-12-03	2021-12-03	Endgerät, funkkommunikationsverfahren und basisstation

Country Status (2)

Country	Link
EP (1)	EP4444013A4 (de)
WO (1)	WO2023100353A1 (de)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number	Priority date	Publication date	Assignee	Title
WO2025083860A1 (ja) *	2023-10-19	2025-04-24	株式会社Ｎｔｔドコモ	端末、無線通信方法及び基地局
WO2025109643A1 (ja) *	2023-11-20	2025-05-30	株式会社Ｎｔｔドコモ	端末、無線通信方法及び基地局
WO2025109644A1 (ja) *	2023-11-20	2025-05-30	株式会社Ｎｔｔドコモ	端末、無線通信方法及び基地局
WO2025154294A1 (ja) *	2024-01-19	2025-07-24	株式会社Ｎｔｔドコモ	端末及び通信方法
CN120568355A (zh) *	2024-02-27	2025-08-29	华为技术有限公司	一种通信方法及通信装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number	Priority date	Publication date	Assignee	Title
RU2727183C1 (ru) *	2017-05-03	2020-07-21	ЭлДжи ЭЛЕКТРОНИКС ИНК.	Способ для передачи и приема канала с произвольным доступом и устройство для его передачи и приема

2021
- 2021-12-03 WO PCT/JP2021/044482 patent/WO2023100353A1/ja not_active Ceased
- 2021-12-03 EP EP21966434.9A patent/EP4444013A4/de active Pending

Also Published As

Publication number	Publication date
WO2023100353A1 (ja)	2023-06-08
EP4444013A4 (de)	2025-10-29

Legal Events

Date	Code	Title	Description
2023-06-10	STAA	Information on the status of an ep patent application or granted ep patent	Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE
2024-09-06	PUAI	Public reference made under article 153(3) epc to a published international application that has entered the european phase	Free format text: ORIGINAL CODE: 0009012
2024-09-06	STAA	Information on the status of an ep patent application or granted ep patent	Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE
2024-10-09	17P	Request for examination filed	Effective date: 20240619
2024-10-09	AK	Designated contracting states	Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR
2025-03-12	DAV	Request for validation of the european patent (deleted)
2025-03-12	DAX	Request for extension of the european patent (deleted)
2025-09-19	REG	Reference to a national code	Ref country code: DE Ref legal event code: R079 Free format text: PREVIOUS MAIN CLASS: H04W0074080000 Ipc: H04W0074000000
2025-10-29	A4	Supplementary search report drawn up and despatched	Effective date: 20250925
2025-10-29	RIC1	Information provided on ipc code assigned before grant	Ipc: H04W 74/00 20090101AFI20250919BHEP Ipc: H04W 48/12 20090101ALI20250919BHEP Ipc: H04W 74/0833 20240101ALN20250919BHEP

Publication	Publication Date	Title
EP4444013A1 (de)	2024-10-09	Endgerät, funkkommunikationsverfahren und basisstation
US20250097917A1 (en)	2025-03-20	Terminal, radio communication method, and base station
US20250015952A1 (en)	2025-01-09	Terminal, radio communication method, and base station
US20250097909A1 (en)	2025-03-20	Terminal, radio communication method, and base station
EP4518551A1 (de)	2025-03-05	Endgerät, funkkommunikationsverfahren und basisstation
EP4478806A1 (de)	2024-12-18	Endgerät, drahtloskommunikationsverfahren und basisstation
US20240430057A1 (en)	2024-12-26	Terminal, radio communication method, and base station
US20250024477A1 (en)	2025-01-16	Terminal, radio communication method, and base station
US20250184095A1 (en)	2025-06-05	Terminal, radio communication method, and base station
EP4486035A1 (de)	2025-01-01	Endgerät, funkkommunikationsverfahren und basisstation
EP4486022A1 (de)	2025-01-01	Endgerät, drahtloskommunikationsverfahren und basisstation
US20250031132A1 (en)	2025-01-23	Terminal, radio communication method, and base station
US20250125933A1 (en)	2025-04-17	Terminal, radio communication method, and base station
EP4478768A1 (de)	2024-12-18	Endgerät, drahtloskommunikationsverfahren und basisstation
WO2024095363A1 (ja)	2024-05-10	端末、無線通信方法及び基地局
WO2024095364A1 (ja)	2024-05-10	端末、無線通信方法及び基地局
WO2023100351A1 (ja)	2023-06-08	端末、無線通信方法及び基地局
EP4543069A1 (de)	2025-04-23	Endgerät, funkkommunikationsverfahren und basisstation
US20250280360A1 (en)	2025-09-04	Radio communication apparatus and radio communication method
US20260122703A1 (en)	2026-04-30	Terminal, radio communication method, and base station
EP4543068A1 (de)	2025-04-23	Endgerät, drahtloskommunikationsverfahren und basisstation
US20250211971A1 (en)	2025-06-26	Terminal, radio communication method, and base station
EP4510734A1 (de)	2025-02-19	Endgerät, funkkommunikationsverfahren und basisstation
US20260101321A1 (en)	2026-04-09	Terminal, radio communication method, and base station
US20250192835A1 (en)	2025-06-12	Terminal, radio communication method, and base station