Communication system, terminal equipment and SgNB
By allowing terminal devices to transmit small data to secondary base stations in an RRC_INACTIVE state with packet duplication, the communication system addresses issues of reduced speed and quality in NR and LTE due to excessive signaling and power reduction, enhancing overall performance.
Patent Information
- Application Number
- JP2023216405
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2017-09-27
- Filing Date
- 2023-12-22
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2038-09-27
AI Technical Summary
In the context of NR and LTE communication systems, the signaling between base stations for RRC_INACTIVE state management in dual connectivity configurations leads to decreased communication speed due to increased band occupancy, and reducing transmission power for UAV-UEs to mitigate interference results in deteriorated reception power and communication quality.
A communication system is implemented where a terminal device transmits small data to a secondary base station (SgNB) in an RRC_INACTIVE state, utilizing packet duplication and reducing unnecessary signaling between master and secondary base stations.
This approach enhances communication speed and quality by minimizing signaling overhead and maintaining reception power, particularly for UAV-UEs, thereby improving overall system efficiency.
Smart Images

Figure 0007595737000001 
Figure 0007595737000002 
Figure 0007595737000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a communication system or the like that performs wireless communication between a terminal device such as a mobile terminal device and a base station. [Background technology]
[0002] 3GPP (3rd Generation Partnership Project), a standardization organization for mobile communication systems, is considering a communication method called Long Term Evolution (LTE) for wireless sections and System Architecture Evolution (SAE) for the overall system configuration including a core network and a wireless access network (hereinafter collectively referred to as a network) (for example, Non-Patent Documents 1 to 5). This communication method is also called a 3.9G (3.9 Generation) system.
[0003] LTE uses OFDM (Orthogonal Frequency Division Multiplexing) for downlink and SC-FDMA (Single Carrier Frequency Division Multiple Access) for uplink as its access method. Also, unlike W-CDMA (Wideband Code Division Multiple Access), LTE does not include circuit switching and is only a packet communication method.
[0004] The decisions made by 3GPP regarding the frame configuration in the LTE system, which are described in Non-Patent Document 1 (Chapter 5), will be described with reference to FIG. 1. FIG. 1 is an explanatory diagram showing the configuration of a radio frame used in an LTE communication system. In FIG. 1, one radio frame is 10 ms. The radio frame is divided into 10 equally sized subframes. The subframe is divided into two equally sized slots. The first and sixth subframes of each radio frame include a downlink synchronization signal. The synchronization signal includes a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS).
[0005] The decisions made by 3GPP regarding the channel configuration in the LTE system are described in Non-Patent Document 1 (Chapter 5). It is assumed that the same channel configuration as that of a non-CSG cell is used in a CSG (Closed Subscriber Group) cell.
[0006] The Physical Broadcast Channel (PBCH) is a channel for downlink transmission from a base station device (hereinafter, sometimes simply referred to as a "base station") to a communication terminal device (hereinafter, sometimes simply referred to as a "communication terminal") such as a mobile terminal device (hereinafter, sometimes simply referred to as a "mobile terminal"). A BCH transport block is mapped to four subframes in a 40 ms interval. There is no explicit signaling of the 40 ms timing.
[0007] The Physical Control Format Indicator Channel (PCFICH) is a channel for downlink transmission from a base station to a communication terminal. The PCFICH notifies the communication terminal of the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols used for PDCCHs from the base station. The PCFICH is transmitted every subframe.
[0008] The Physical Downlink Control Channel (PDCCH) is a channel for downlink transmission from a base station to a communication terminal. The PDCCH reports resource allocation information for a Downlink Shared Channel (DL-SCH), which is one of the transport channels described below, resource allocation information for a Paging Channel (PCH), which is one of the transport channels described below, and Hybrid Automatic Repeat reQuest (HARQ) information for the DL-SCH. The PDCCH carries an uplink scheduling grant. The PDCCH carries Acknowledgement (Acknowledgement) / Nack (Negative Acknowledgement), which are response signals to uplink transmission. The PDCCH is also called an L1 / L2 control signal.
[0009] A physical downlink shared channel (PDSCH) is a channel for downlink transmission from a base station to a communication terminal. A downlink shared channel (DL-SCH), which is a transport channel, and a PCH, which is a transport channel, are mapped to the PDSCH.
[0010] A physical multicast channel (PMCH) is a channel for downlink transmission from a base station to communication terminals. A multicast channel (MCH), which is a transport channel, is mapped to the PMCH.
[0011] The Physical Uplink Control Channel (PUCCH) is a channel for uplink transmission from a communication terminal to a base station. The PUCCH carries Ack / Nack, which is a response signal to a downlink transmission. The PUCCH carries a CQI (Channel Quality Indicator) report. CQI is quality information that indicates the quality of received data or the quality of the communication path. The PUCCH also carries a Scheduling Request (SR).
[0012] A Physical Uplink Shared Channel (PUSCH) is a channel for uplink transmission from a communication terminal to a base station. An Uplink Shared Channel (UL-SCH), which is one of the transport channels, is mapped to the PUSCH.
[0013] The Physical Hybrid ARQ Indicator Channel (PHICH) is a channel for downlink transmission from a base station to a communication terminal. The PHICH carries Ack / Nack, which is a response signal to an uplink transmission. The Physical Random Access Channel (PRACH) is a channel for uplink transmission from a communication terminal to a base station. The PRACH carries a random access preamble.
[0014] Downlink reference signals (RS) are known symbols in LTE communication systems. The following five types of downlink reference signals are defined: Cell-specific Reference Signal (CRS), MBSFN Reference Signal, UE-specific Reference Signal (DM-RS) Demodulation Reference Signal (PRS), Positioning Reference Signal (PRS), and Channel State Information Reference Signal (CSI-RS). Measurement of the physical layer of a communication terminal includes measurement of the reference signal received power (RSRP).
[0015] The transport channel described in Non-Patent Document 1 (Chapter 5) will be explained. Among the downlink transport channels, the broadcast channel (BCH) is broadcast to the entire coverage of the base station (cell). The BCH is mapped to the physical broadcast channel (PBCH).
[0016] Retransmission control using HARQ (Hybrid ARQ) is applied to the Downlink Shared Channel (DL-SCH). DL-SCH can be broadcast to the entire coverage of a base station (cell). DL-SCH supports dynamic or semi-static resource allocation. Semi-static resource allocation is also called persistent scheduling. DL-SCH supports discontinuous reception (DRX) of communication terminals to reduce power consumption of communication terminals. DL-SCH is mapped to the physical downlink shared channel (PDSCH).
[0017] The Paging Channel (PCH) supports DRX of communication terminals to enable low power consumption of the communication terminals. The PCH is required to be broadcast to the entire coverage of the base station (cell). The PCH is mapped to physical resources such as the Physical Downlink Shared Channel (PDSCH) that can be dynamically used for traffic.
[0018] The Multicast Channel (MCH) is used for broadcasting to the entire coverage of a base station (cell). The MCH supports SFN combining of MBMS (Multimedia Broadcast Multicast Service) services (MTCH and MCCH) in multi-cell transmission. The MCH supports semi-static resource allocation. The MCH is mapped to the PMCH.
[0019] Among the uplink transport channels, the uplink shared channel (UL-SCH) is subject to retransmission control using HARQ (Hybrid ARQ). The UL-SCH supports dynamic or semi-static resource allocation. The UL-SCH is mapped to the physical uplink shared channel (PUSCH).
[0020] The Random Access Channel (RACH) is limited to control information. The RACH is subject to collision risk. The RACH is mapped to the Physical Random Access Channel (PRACH).
[0021] Let us explain about HARQ. HARQ is a technology that improves the communication quality of a transmission line by combining Automatic Repeat reQuest (ARQ) and Forward Error Correction. HARQ has the advantage that error correction works effectively by retransmission even for transmission lines whose communication quality changes. In particular, it is possible to obtain further quality improvement by combining the reception result of the initial transmission and the reception result of the retransmission when retransmitting.
[0022] An example of a retransmission method will be described below. If the received data cannot be decoded correctly on the receiving side, in other words, if a CRC (Cyclic Redundancy Check) error occurs (CRC=NG), the receiving side will send a "Nack" to the transmitting side. The transmitting side that receives the "Nack" will retransmit the data. If the received data can be decoded correctly on the receiving side, in other words, if no CRC error occurs (CRC=OK), the receiving side will send an "Ack" to the transmitting side. The transmitting side that receives the "Ack" will send the next data.
[0023] The logical channel described in Non-Patent Document 1 (Chapter 6) will be explained. The Broadcast Control Channel (BCCH) is a downlink channel for broadcast system control information. The logical channel BCCH is mapped to the broadcast channel (BCH) or the downlink shared channel (DL-SCH), which are transport channels.
[0024] The Paging Control Channel (PCCH) is a downlink channel for transmitting paging information and changes to system information. The PCCH is used when the network does not know the cell location of the communication terminal. The PCCH, which is a logical channel, is mapped to the Paging Channel (PCH), which is a transport channel.
[0025] A Common Control Channel (CCCH) is a channel for transmission control information between a communication terminal and a base station. CCCH is used when a communication terminal does not have an RRC connection with the network. In the downlink direction, CCCH is mapped to a transport channel, the Downlink Shared Channel (DL-SCH). In the uplink direction, CCCH is mapped to a transport channel, the Uplink Shared Channel (UL-SCH).
[0026] The Multicast Control Channel (MCCH) is a downlink channel for point-to-multipoint transmission. The MCCH is used for transmission of MBMS control information for one or several MTCHs from the network to communication terminals. The MCCH is used only by communication terminals receiving MBMS. The MCCH is mapped to the Multicast Channel (MCH), which is a transport channel.
[0027] A Dedicated Control Channel (DCCH) is a channel that transmits dedicated control information between a communication terminal and a network on a one-to-one basis. DCCH is used when a communication terminal is in an RRC connection. DCCH is mapped to an uplink shared channel (UL-SCH) in the uplink and to a downlink shared channel (DL-SCH) in the downlink.
[0028] A Dedicated Traffic Channel (DTCH) is a one-to-one communication channel for transmitting user information to an individual communication terminal. DTCH exists in both uplink and downlink. DTCH is mapped to an uplink shared channel (UL-SCH) in uplink and to a downlink shared channel (DL-SCH) in downlink.
[0029] A Multicast Traffic Channel (MTCH) is a downlink channel for transmitting traffic data from a network to a communication terminal. The MTCH is a channel used only by communication terminals receiving MBMS. The MTCH is mapped to a Multicast Channel (MCH).
[0030] CGI stands for Cell Global Identifier. ECGI stands for E-UTRAN Cell Global Identifier. CSG (Closed Subscriber Group) cells are introduced in LTE, LTE-A (Long Term Evolution Advanced) (described below), and UMTS (Universal Mobile Telecommunication System).
[0031] A CSG (Closed Subscriber Group) cell is a cell for which an operator has specified available subscribers (hereinafter sometimes referred to as a "specified subscriber cell"). The specified subscribers are permitted to access one or more cells in a PLMN (Public Land Mobile Network). The one or more cells to which the specified subscribers are permitted to access are called "CSG cell(s)". However, there are access restrictions in the PLMN.
[0032] A CSG cell is a part of a PLMN that broadcasts a unique CSG identity (CSG ID) and broadcasts a CSG indication of "TRUE". Members of a pre-registered and authorized subscriber group access the CSG cell using the CSG ID, which is access permission information.
[0033] The CSG ID is broadcast by a CSG cell or cells. There are a plurality of CSG IDs in an LTE communication system. The CSG ID is used by a communication terminal (UE) to facilitate access of CSG-related members.
[0034] The location of a communication terminal is tracked in units of an area consisting of one or more cells. Location tracking is performed to track the location of the communication terminal even when it is in standby mode and to enable the communication terminal to be called, in other words, to allow the communication terminal to receive calls. The area for tracking the location of this communication terminal is called a tracking area.
[0035] In 3GPP, base stations called Home-NodeB (Home-NB; HNB) and Home-eNodeB (Home-eNB; HeNB) are under consideration. HNB in UTRAN and HeNB in E-UTRAN are base stations for home, corporate and commercial access services, for example. Non-Patent Document 2 discloses three different modes of access to HeNB and HNB. Specifically, an open access mode, a closed access mode and a hybrid access mode are disclosed.
[0036] 3GPP is also working on the development of standards for Long Term Evolution Advanced (LTE-A) as Release 10 (see Non-Patent Documents 3 and 4). LTE-A is based on the LTE wireless communication method, and is configured by adding several new technologies to it.
[0037] In the LTE-A system, in order to support wider frequency bandwidths (transmission bandwidths) up to 100 MHz, Carrier Aggregation (CA) is being considered, which aggregates two or more Component Carriers (CCs) (also called "aggregation"). CA is described in Non-Patent Document 1.
[0038] When CA is configured, the UE has only one RRC connection with the network (NW). In the RRC connection, one serving cell provides NAS mobility information and security input. This cell is called a Primary Cell (PCell). In the downlink, the carrier corresponding to the PCell is the Downlink Primary Component Carrier (DL PCC). In the uplink, the carrier corresponding to the PCell is the Uplink Primary Component Carrier (UL PCC).
[0039] Depending on the UE's capabilities, a secondary cell (SCell) is configured to form a set of serving cells together with the PCell. In the downlink, the carrier corresponding to the SCell is the downlink secondary component carrier (DL SCC). In the uplink, the carrier corresponding to the SCell is the uplink secondary component carrier (UL SCC).
[0040] A set of serving cells, which includes one PCell and one or more SCells, is configured for one UE.
[0041] New technologies for LTE-A include a technology that supports wider bandwidth (Wider Bandwidth Extension) and a Coordinated Multiple Point transmission and reception (CoMP) technology. CoMP, which is being considered for LTE-A by 3GPP, is described in Non-Patent Document 1.
[0042] In addition, in 3GPP, in order to handle the huge traffic in the future, the use of small eNBs (hereinafter sometimes referred to as "small-scale base station devices") that configure small cells is being considered. For example, technologies are being considered that improve frequency utilization efficiency and increase communication capacity by installing many small eNBs and configuring many small cells. Specifically, there is dual connectivity (abbreviated as DC) in which a UE connects to two eNBs to communicate. DC is described in Non-Patent Document 1.
[0043] Of the eNBs performing dual connectivity (DC), one may be referred to as a "master eNB (abbreviated as MeNB)" and the other as a "secondary eNB (abbreviated as SeNB)."
[0044] Mobile network traffic is on the rise, and communication speeds are also getting faster. Once LTE and LTE-A are fully operational, communication speeds are expected to become even faster.
[0045] Furthermore, to cope with the increasing sophistication of mobile communications, fifth-generation (hereinafter sometimes referred to as "5G") wireless access systems are being considered, with the goal of starting services after 2020. For example, in Europe, an organization called METIS has compiled requirements for 5G (see Non-Patent Document 5).
[0046] Compared to the LTE system, the 5G wireless access system requires a system capacity that is 1,000 times greater, a data transmission speed that is 100 times greater, data processing delay that is one-tenth (1 / 10), and 100 times the number of simultaneous connections of communication terminals, while also achieving further reductions in power consumption and reductions in equipment costs.
[0047] In order to meet such demands, 3GPP is currently studying 5G standards as Release 15 (see Non-Patent Documents 6 to 10). The technology for 5G wireless sections is called "New Radio Access Technology" ("New Radio" is abbreviated as "NR"), and several new technologies are being studied (see Non-Patent Document 11). For example, inactivity control in UE using DC is being studied. Furthermore, studies are also being conducted on the extension of the LTE standard. For example, power control in UE mounted on unmanned aerial vehicles is being studied (see Non-Patent Documents 12 and 13). [Prior art documents] [Non-patent literature]
[0048] [Non-Patent Document 1] 3GPP TS 36.300 V14.3.0 [Non-Patent Document 2] 3GPP S1-083461 [Non-Patent Document 3] 3GPP TR 36.814 V9.2.0 [Non-Patent Document 4] 3GPP TR 36.912 V14.0.0 [Non-Patent Document 5] "Scenarios, requirements and KPIs for 5G mobile and wireless system", ICT-317669-METIS / D1.1 [Non-Patent Document 6] 3GPP TR 23.799 V14.0.0 [Non-Patent Document 7] 3GPP TR 38.801 V14.0.0 [Non-Patent Document 8] 3GPP TR 38.802 V14.1.0 [Non-Patent Document 9] 3GPP TR 38.804 V14.0.0 [Non-Patent Document 10] 3GPP TR 38.912 V14.0.0 [Non-Patent Document 11] 3GPP R2-1706892 [Non-Patent Document 12] 3GPP RP-171050 [Non-Patent Document 13] 3GPP R1-1708433 [Summary of the Invention] [Problems to be Solved by the Invention]
[0049] In NR, a control technique for the RRC_INACTIVE state is being discussed as a technique for reducing the power consumption of the UE and quickly resuming communication. The RRC_INACTIVE state control for the UE using the DC configuration is also being discussed. The MgNB inquires of the SgNB whether data is available to the MgNB and the SgNB to confirm whether data is available to be transmitted or received. However, the signaling between the MgNB and the SgNB for the inquiry occupies the bandwidth between the base stations. As a result, the communication speed between the base stations in DC decreases, and the communication speed between the MgNB, the SgNB, and the UE decreases.
[0050] In addition, technology is being considered for reducing interference with surrounding base stations in communication with UEs mounted on unmanned aerial vehicles (hereinafter, sometimes referred to as UAV-UE). However, reducing the transmission power from the UAV-UE to reduce interference with surrounding base stations reduces the received power in the serving cell, degrading the communication quality between the UAV-UE and the serving cell and decreasing the communication speed.
[0051] In view of the above problems, one object of the present invention is to provide a high-speed communication system and the like in NR and LTE. [Means for solving the problem]
[0052] According to the present invention, for example, a communication system is provided, comprising a terminal device and a plurality of base stations each of which wirelessly communicates with the terminal device, the plurality of base stations including an MgNB and an SgNB that form dual connectivity with the terminal device, and the terminal device performs small data transmission to the SgNB in an RRC_INACTIVE state.
[0053] According to the present invention, for example, there is provided a communication system in which packet duplication is applied in the small data transmission by the terminal device.
[0054] According to the present invention, for example, there is provided a terminal device in a communication system including a terminal device and a plurality of base stations each of which wirelessly communicates with the terminal device, the plurality of base stations including an MgNB and an SgNB that form dual connectivity with the terminal device, the terminal device performing small data transmission to the SgNB in an RRC_INACTIVE state.
[0055] According to the present invention, for example, there is provided an SgNB in a communication system including a terminal device and a plurality of base stations each of which wirelessly communicates with the terminal device, the plurality of base stations including an MgNB and an SgNB that form dual connectivity with the terminal device, the SgNB receiving small data transmitted from the terminal device in an RRC_INACTIVE state. Effect of the Invention
[0056] According to the present invention, it is possible to provide a high-speed communication system in NR and LTE.
[0057] The objects, features, aspects and advantages of the present invention will become more apparent from the following detailed description and the accompanying drawings. [Brief description of the drawings]
[0058] [Figure 1] FIG. 1 is an explanatory diagram showing the configuration of a radio frame used in an LTE communication system. [Diagram 2] 1 is a block diagram showing the overall configuration of a communication system 200 based on the LTE standard that is being discussed in 3GPP. [Diagram 3] FIG. 3 is a block diagram showing a configuration of a mobile terminal 202 shown in FIG. 2, which is a communication terminal according to the present invention. [Figure 4] FIG. 3 is a block diagram showing a configuration of a base station 203 shown in FIG. 2 which is a base station according to the present invention. [Diagram 5] FIG. 2 is a block diagram showing the configuration of an MME according to the present invention. [Figure 6]1 is a flowchart showing an overview of operations from cell search to standby performed by a communication terminal (UE) in an LTE communication system. [Figure 7] A diagram showing the concept of a cell configuration when macro eNBs and small eNBs are mixed. [Figure 8] 4 is a sequence diagram showing an operation of a UE transitioning to an RRC_INACTIVE state and an operation of the UE returning to an RRC_CONNECTED state in accordance with the first embodiment. FIG. [Figure 9] 4 is a sequence diagram showing an operation of a UE transitioning to an RRC_INACTIVE state and an operation of the UE returning to an RRC_CONNECTED state in accordance with the first embodiment. FIG. [Figure 10] FIG. 11 is a sequence diagram showing an operation in which the RRC_INACTIVE state transition in the UE is interrupted by an RRC_INACTIVE state transition interrupt instruction from the MgNB, in accordance with the first modification of the first embodiment. [Figure 11] FIG. 11 is a sequence diagram showing an operation in which the RRC_INACTIVE state transition in the UE is interrupted due to the occurrence of uplink data, according to the first modification of the first embodiment. [Figure 12] A sequence diagram showing the operation of a UE in an RRC_INACTIVE state determining an SgNB in accordance with the second variant of the first embodiment. [Figure 13] A sequence diagram showing the operation of a UE in an RRC_INACTIVE state determining an SgNB in accordance with the second variant of the first embodiment. [Figure 14] A sequence diagram showing the operation of a UE in an RRC_INACTIVE state determining an SgNB in accordance with the second variant of the first embodiment. [Figure 15] FIG. 11 is a sequence diagram showing an operation of an MgNB determining an SgNB for communication with a UE in an RRC_INACTIVE state, in accordance with a second variant of the first embodiment. [Figure 16] FIG. 11 is a sequence diagram showing an operation of an MgNB determining an SgNB for communication with a UE in an RRC_INACTIVE state, in accordance with a second variant of the first embodiment. [Figure 17] FIG. 11 is a sequence diagram showing an operation of an MgNB determining an SgNB for communication with a UE in an RRC_INACTIVE state, in accordance with a second variant of the first embodiment. [Figure 18] FIG. 11 is a sequence diagram showing an operation of a UE in an RRC_INACTIVE state determining a target MgNB and a target SgNB, according to a second variant of the first embodiment. [Figure 19] FIG. 11 is a sequence diagram showing an operation of a UE in an RRC_INACTIVE state determining a target MgNB and a target SgNB, according to a second variant of the first embodiment. [Figure 20] FIG. 11 is a sequence diagram showing an operation of a UE in an RRC_INACTIVE state determining a target MgNB and a target SgNB, according to a second variant of the first embodiment. [Figure 21] FIG. 11 is a sequence diagram showing small data transmission from a UE to an SgNB in accordance with a second embodiment. [Figure 22] FIG. 11 is a sequence diagram showing small data transmission from a UE to an MgNB and an SgNB in accordance with a second embodiment. [Diagram 23] FIG. 13 is a sequence diagram showing an operation in a case where a DC is used for packet duplication of small data, in accordance with the first modification of the second embodiment. [Figure 24] FIG. 13 is a sequence diagram showing an operation in a case where a DC is used for packet duplication of small data, in accordance with the first modification of the second embodiment. [Figure 25] FIG. 13 is a sequence diagram showing an operation when CA is used for packet duplication of small data, according to the first modification of the second embodiment. [Figure 26] FIG. 11 is a pattern diagram showing an example in which a different frequency hopping pattern is given to a UAV-UE for each cell, in accordance with the third embodiment. [Figure 27] A sequence diagram showing the operation of UAV-UE determining a communication mode for embodiment 5. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0059] Embodiment 1 Fig. 2 is a block diagram showing the overall configuration of an LTE-based communication system 200 being discussed in 3GPP. Fig. 2 will now be described. The radio access network is called E-UTRAN (Evolved Universal Terrestrial Radio Access Network) 201. A mobile terminal device (hereinafter referred to as "mobile terminal (User Equipment: UE)") 202, which is a communication terminal device, is capable of wireless communication with a base station device (hereinafter referred to as "base station (E-UTRAN NodeB: eNB)") 203, and transmits and receives signals via wireless communication.
[0060] Here, the term "communication terminal device" includes not only mobile terminal devices such as mobile mobile phone terminal devices, but also stationary devices such as sensors. In the following description, the "communication terminal device" may be simply referred to as a "communication terminal."
[0061] If control protocols for mobile terminals 202, such as RRC (Radio Resource Control), and user planes (hereinafter sometimes referred to as U-Planes), such as PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical layer), terminate in a base station 203, E-UTRAN is composed of one or more base stations 203.
[0062] A control protocol RRC (Radio Resource Control) between the mobile terminal 202 and the base station 203 performs broadcast, paging, RRC connection management, etc. The states of the base station 203 and the mobile terminal 202 in RRC include RRC_IDLE and RRC_CONNECTED.
[0063] In RRC_IDLE, PLMN (Public Land Mobile Network) selection, system information (SI) broadcast, paging, cell re-selection, mobility, etc. are performed. In RRC_CONNECTED, the mobile terminal has an RRC connection and can transmit and receive data with the network. In addition, in RRC_CONNECTED, handover (HO), measurement of neighbor cells, etc. are performed.
[0064] The base station 203 is classified into an eNB 207 and a Home-eNB 206. The communication system 200 includes an eNB group 203-1 including a plurality of eNBs 207, and a Home-eNB group 203-2 including a plurality of Home-eNBs 206. A system including an EPC (Evolved Packet Core) which is a core network and an E-UTRAN 201 which is a radio access network is called an EPS (Evolved Packet System). The EPC which is a core network and the E-UTRAN 201 which is a radio access network may be collectively called a "network."
[0065] The eNB207 is connected to a Mobility Management Entity (MME), or a Serving Gateway (S-GW), or an MME / S-GW unit (hereinafter sometimes referred to as an "MME unit") 204 including an MME and an S-GW via an S1 interface, and control information is communicated between the eNB207 and the MME unit 204. A plurality of MME units 204 may be connected to one eNB207. The eNBs 207 are connected to each other via an X2 interface, and control information is communicated between the eNBs 207.
[0066] The Home-eNB 206 is connected to the MME unit 204 via an S1 interface, and control information is communicated between the Home-eNB 206 and the MME unit 204. A plurality of Home-eNBs 206 are connected to one MME unit 204. Alternatively, the Home-eNB 206 is connected to the MME unit 204 via a Home-eNB GateWay (HeNBGW) 205. The Home-eNB 206 and the HeNBGW 205 are connected to each other via an S1 interface, and the HeNBGW 205 and the MME unit 204 are connected to each other via the S1 interface.
[0067] One or more Home-eNBs 206 are connected to one HeNBGW 205, and information is communicated through an S1 interface. The HeNBGW 205 is connected to one or more MME units 204, and information is communicated through an S1 interface.
[0068] The MME unit 204 and the HeNBGW 205 are upper devices, specifically, upper nodes, and control connections between the eNB 207 and the Home-eNB 206, which are base stations, and the mobile terminal (UE) 202. The MME unit 204 constitutes the EPC, which is a core network. The base station 203 and the HeNBGW 205 constitute the E-UTRAN 201.
[0069] Furthermore, 3GPP is considering the following configuration. The X2 interface between Home-eNBs 206 is supported. That is, the Home-eNBs 206 are connected via the X2 interface, and control information is communicated between the Home-eNBs 206. From the MME unit 204, the HeNBGW 205 appears as the Home-eNB 206. From the Home-eNB 206, the HeNBGW 205 appears as the MME unit 204.
[0070] In either case where the Home-eNB 206 is connected to the MME unit 204 via the HeNBGW 205 or where the Home-eNB 206 is directly connected to the MME unit 204, the interface between the Home-eNB 206 and the MME unit 204 is the same, that is, the S1 interface.
[0071] The base station 203 may configure one cell or multiple cells. Each cell has a predetermined range as a coverage area in which communication with the mobile terminal 202 is possible, and performs wireless communication with the mobile terminal 202 within the coverage area. When one base station 203 configures multiple cells, each cell is configured to be able to communicate with the mobile terminal 202.
[0072] FIG. 3 is a block diagram showing the configuration of the mobile terminal 202 shown in FIG. 2, which is a communication terminal according to the present invention. The transmission process of the mobile terminal 202 shown in FIG. 3 will be described. First, the control data from the protocol processing unit 301 and the user data from the application unit 302 are stored in the transmission data buffer unit 303. The data stored in the transmission data buffer unit 303 is passed to the encoder unit 304, where encoding such as error correction is performed. There may be data that is directly output from the transmission data buffer unit 303 to the modulation unit 305 without encoding. The data that has been encoded by the encoder unit 304 is modulated by the modulation unit 305. The modulated data is converted into a baseband signal, and then output to the frequency conversion unit 306, where it is converted into a radio transmission frequency. Thereafter, a transmission signal is transmitted from the antenna 307 to the base station 203.
[0073] Moreover, the receiving process of the mobile terminal 202 is executed as follows. A radio signal from the base station 203 is received by the antenna 307. The received signal is converted from a radio receiving frequency to a baseband signal by the frequency conversion unit 306, and demodulated by the demodulation unit 308. The demodulated data is passed to the decoder unit 309, where decoding such as error correction is performed. Of the decoded data, the control data is passed to the protocol processing unit 301, and the user data is passed to the application unit 302. A series of processes of the mobile terminal 202 is controlled by the control unit 310. Therefore, although the control unit 310 is omitted in FIG. 3, it is connected to each of the units 301 to 309.
[0074] Fig. 4 is a block diagram showing the configuration of the base station 203 shown in Fig. 2 which is a base station according to the present invention. A transmission process of the base station 203 shown in Fig. 4 will be described. The EPC communication unit 401 transmits and receives data between the base station 203 and the EPC (MME unit 204, etc.), the HeNBGW 205, etc. The other base station communication unit 402 transmits and receives data with other base stations. The EPC communication unit 401 and the other base station communication unit 402 each exchange information with a protocol processing unit 403. The control data from the protocol processing unit 403, and the user data and control data from the EPC communication unit 401 and the other base station communication unit 402 are stored in a transmission data buffer unit 404.
[0075] The data stored in the transmission data buffer unit 404 is passed to the encoder unit 405, where it is subjected to encoding processing such as error correction. Some data may be output directly from the transmission data buffer unit 404 to the modulator unit 406 without being encoded. The encoded data is modulated in the modulator unit 406. The modulated data is converted into a baseband signal, and then output to the frequency converter unit 407, where it is converted into a radio transmission frequency. The transmission signal is then transmitted from the antenna 408 to one or more mobile terminals 202.
[0076] Moreover, the reception process of the base station 203 is executed as follows. A radio signal from one or more mobile terminals 202 is received by an antenna 408. The received signal is converted from a radio reception frequency to a baseband signal by a frequency conversion unit 407, and demodulated by a demodulation unit 409. The demodulated data is passed to a decoder unit 410, where a decoding process such as error correction is performed. Of the decoded data, the control data is passed to a protocol processing unit 403 or an EPC communication unit 401 or an other base station communication unit 402, and the user data is passed to the EPC communication unit 401 and the other base station communication unit 402. A series of processes of the base station 203 is controlled by a control unit 411. Therefore, although the control unit 411 is omitted in FIG. 4, it is connected to each unit 401 to 410.
[0077] FIG. 5 is a block diagram showing the configuration of the MME according to the present invention. FIG. 5 shows the configuration of the MME 204a included in the MME unit 204 shown in FIG. 2 described above. The PDN GW communication unit 501 transmits and receives data between the MME 204a and the PDN GW. The base station communication unit 502 transmits and receives data between the MME 204a and the base station 203 via the S1 interface. If the data received from the PDN GW is user data, the user data is passed from the PDN GW communication unit 501 to the base station communication unit 502 via the user plane communication unit 503 and transmitted to one or more base stations 203. If the data received from the base station 203 is user data, the user data is passed from the base station communication unit 502 to the PDN GW communication unit 501 via the user plane communication unit 503 and transmitted to the PDN GW.
[0078] When the data received from the PDN GW is control data, the control data is passed from the PDN GW communication unit 501 to the control plane control unit 505. When the data received from the base station 203 is control data, the control data is passed from the base station communication unit 502 to the control plane control unit 505.
[0079] The HeNBGW communication unit 504 is provided when a HeNBGW 205 is present, and transmits and receives data via an interface (IF) between the MME 204a and the HeNBGW 205 depending on the information type. Control data received from the HeNBGW communication unit 504 is passed from the HeNBGW communication unit 504 to a control plane control unit 505. A result of processing in the control plane control unit 505 is transmitted to the PDN GW via the PDN GW communication unit 501. In addition, a result of processing in the control plane control unit 505 is transmitted to one or more base stations 203 by the S1 interface via the base station communication unit 502, and is also transmitted to one or more HeNBGW 205 via the HeNBGW communication unit 504.
[0080] The control plane control unit 505 includes a NAS security unit 505-1, an SAE bearer control unit 505-2, an idle state mobility management unit 505-3, etc., and performs general processing for the control plane (hereinafter, sometimes referred to as C-Plane). The NAS security unit 505-1 performs security for NAS (Non-Access Stratum) messages, etc. The SAE bearer control unit 505-2 performs management of SAE (System Architecture Evolution) bearers, etc. The idle state mobility management unit 505-3 performs mobility management in the idle state (also called the LTE-IDLE state or simply idle), generation and control of paging signals in the idle state, addition, deletion, update, search, and tracking area list management of one or more mobile terminals 202 under its control.
[0081] The MME 204a distributes a paging signal to one or more base stations 203. The MME 204a also performs mobility control in an idle state. The MME 204a manages a tracking area list when the mobile terminal is in an idle state and in an active state. The MME 204a initiates a paging protocol by transmitting a paging message to a cell that belongs to a tracking area in which the UE is registered. The idle state mobility management unit 505-3 may manage the CSG, CSG ID, and whitelist of the Home-eNB 206 connected to the MME 204a.
[0082] Next, an example of a cell search method in a communication system is shown. Fig. 6 is a flow chart showing an outline of a process from cell search to standby operation performed by a communication terminal (UE) in an LTE communication system. When the communication terminal starts a cell search, in step ST601, the communication terminal synchronizes slot timing and frame timing using a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS) transmitted from a surrounding base station.
[0083] P-SS and S-SS are collectively called the Synchronization Signal (SS). The Synchronization Signal (SS) is assigned a synchronization code that corresponds one-to-one to the PCI assigned to each cell. 504 different PCIs are being considered. These 504 different PCIs are used to achieve synchronization and to detect (identify) the PCI of the synchronized cell.
[0084] Next, in step ST602, for the synchronized cell, a cell-specific reference signal (CRS), which is a reference signal (RS) transmitted from the base station for each cell, is detected and the RS received power (Reference Signal Received Power: RSRP) is measured. A code that has a one-to-one correspondence with the PCI is used for the reference signal (RS). By correlating with the code, it is possible to separate the cell from other cells. By deriving the code for the RS of the cell from the PCI identified in step ST601, it is possible to detect the RS and measure the RS received power.
[0085] Next, in step ST603, the cell with the best RS reception quality, for example the cell with the highest RS reception power, that is, the best cell, is selected from among one or more cells detected up to step ST602.
[0086] Next, in step ST604, the PBCH of the best cell is received to obtain a BCCH, which is broadcast information. A MIB (Master Information Block), which includes cell configuration information, is mapped to the BCCH on the PBCH. Therefore, the MIB can be obtained by receiving the PBCH and obtaining the BCCH. Examples of MIB information include DL (downlink) system bandwidth (also called transmission bandwidth configuration: dl-bandwidth), the number of transmitting antennas, SFN (System Frame Number), and the like.
[0087] Next, in step ST605, the DL-SCH of the cell is received based on the cell configuration information in the MIB, and SIB (System Information Block) 1 in the broadcast information BCCH is obtained. SIB 1 includes information on access to the cell, information on cell selection, and scheduling information of other SIBs (SIBk; k is an integer ≧2). SIB 1 also includes a tracking area code (TAC).
[0088] Next, in step ST606, the communication terminal compares the TAC of the SIB1 received in step ST605 with the TAC portion of the tracking area identity (TAI) in the tracking area list that the communication terminal already holds. The tracking area list is also called a TAI list. The TAI is identification information for identifying a tracking area, and is composed of a MCC (Mobile Country Code), an MNC (Mobile Network Code), and a TAC (Tracking Area Code). The MCC is a country code. The MNC is a network code. The TAC is a code number of the tracking area.
[0089] If the TAC received in step ST605 is the same as the TAC included in the tracking area list as a result of the comparison in step ST606, the communication terminal enters standby mode in the cell. If the TAC received in step ST605 is not included in the tracking area list as a result of the comparison, the communication terminal requests a core network (EPC) including an MME, etc., to change the tracking area in order to perform a Tracking Area Update (TAU) through the cell.
[0090] An apparatus constituting a core network (hereinafter sometimes referred to as a "core network side apparatus") updates the tracking area list based on an identification number (such as a UE-ID) of a communication terminal sent from the communication terminal together with a TAU request signal. The core network side apparatus transmits the updated tracking area list to the communication terminal. The communication terminal rewrites (updates) the TAC list held by the communication terminal based on the received tracking area list. After that, the communication terminal enters standby mode in the cell.
[0091] The spread of smartphones and tablet terminal devices has led to an explosive increase in traffic via cellular wireless communications, raising concerns about a shortage of wireless resources around the world. In response to this, efforts are being made to create smaller cells and promote spatial separation in order to improve frequency utilization efficiency.
[0092] In a conventional cell configuration, a cell configured by an eNB has a relatively wide coverage area. Conventionally, a cell is configured to cover a certain area by the relatively wide coverage areas of a plurality of cells configured by a plurality of eNBs.
[0093] In the case of small cell configuration, the cell configured by the eNB has a narrower coverage range than the coverage of the cell configured by the conventional eNB. Therefore, as in the past, in order to cover a certain area, a large number of small cell eNBs are required compared to the conventional eNBs.
[0094] In the following description, a cell with a relatively large coverage, such as a cell configured by a conventional eNB, is referred to as a "macro cell," and an eNB that configures the macro cell is referred to as a "macro eNB." Also, a cell with a relatively small coverage, such as a cell that has been made into a small cell, is referred to as a "small cell," and an eNB that configures the small cell is referred to as a "small eNB."
[0095] The macro eNB may be, for example, a “Wide Area Base Station” as described in Non-Patent Document 7.
[0096] The small eNB may be, for example, a low power node, a local area node, a hotspot, etc. Also, the small eNB may be a pico eNB constituting a pico cell, a femto eNB constituting a femto cell, a HeNB, a remote radio head (RRH), a remote radio unit (RRU), a remote radio equipment (RRE), or a relay node (RN). Also, the small eNB may be a "local area base station" or a "home base station" as described in Non-Patent Document 7.
[0097] 7 is a diagram showing the concept of a cell configuration when macro eNBs and small eNBs are mixed. A macro cell configured by a macro eNB has a relatively wide coverage area 701. A small cell configured by a small eNB has a coverage area 702 that is smaller than the coverage area 701 of the macro eNB (macro cell).
[0098] When multiple eNBs are mixed, the coverage of a cell configured by one eNB may be included in the coverage of a cell configured by another eNB. In the cell configuration shown in Fig. 7, as shown by reference numerals "704" and "705", the coverage 702 of a small cell configured by a small eNB may be included in the coverage 701 of a macro cell configured by a macro eNB.
[0099] Also, as indicated by reference numeral "705," the coverage of multiple, for example, two, small cells 702 may be included within the coverage of one macro cell 701. A mobile terminal (UE) 703 is included, for example, within the coverage 702 of the small cell and communicates via the small cell.
[0100] Furthermore, in the cell configuration shown in FIG. 7, as indicated by reference numeral "706," there may be cases where coverage 701 of a macro cell formed by a macro eNB and coverage 702 of a small cell formed by a small eNB overlap in a complex manner.
[0101] Also, as indicated by reference numeral "707," there may be cases where coverage 701 of a macro cell configured by a macro eNB and coverage 702 of a small cell configured by a small eNB do not overlap.
[0102] Furthermore, as indicated by reference numeral "708," there may be cases where the coverage 702 of multiple small cells formed by multiple small eNBs is formed within the coverage 701 of one macro cell formed by one macro eNB.
[0103] In NR, the UE transitions to the RRC_INACTIVE state upon receiving an instruction from the base station. For a UE using a DC configuration, the MgNB instructs the UE to transition to the RRC_INACTIVE state. The MgNB inquires of the SgNB whether data passing through the SCG bearer and the SCG split bearer is inactive, i.e., data passing through the bearer is not being conducted. The SgNB notifies the inactivity status of data passing through all SCG bearers and SCG split bearers used by the UE. The MgNB uses the notification to instruct the UE to transition to the RRC_INACTIVE state. This enables the MgNB to transition the UE to the RRC_INACTIVE state after correctly reflecting the inactivity status of data passing through the SCG bearer / SCG split bearer.
[0104] Also, the base station transmits paging to the UE in the RRC_INACTIVE state. The MgNB transmits paging to the UE in the RRC_INACTIVE state that holds the DC configuration. The SgNB notifies the MgNB that data passing through the SCG bearer and / or the SCG split bearer has occurred. The UE requests the MgNB to resume the RRC connection. The MgNB instructs the UE to resume the RRC connection. Also, the MgNB requests the SgNB to resume the RRC connection for the UE. The SgNB notifies the MgNB of the response to the resumption of the RRC connection for the UE. This allows the MgNB to return the UE from the RRC_INACTIVE state to RRC_CONNECTED due to the occurrence of data passing through the SCG bearer and / or the SCG split bearer.
[0105] When the above-mentioned method is applied, the following problems occur. For example, when data continuity using an SCG bearer and / or an SCG split bearer continues, in response to the inquiry from the MgNB to the SgNB, the SgNB notifies that data passing through the bearer is in an active state, and the MgNB cannot transition the UE to the RRC_INACTIVE state. The MgNB needs to repeatedly transmit the inquiry to the SgNB in order to appropriately grasp the data continuity status using the bearer and appropriately manage the state of the UE. In addition, the SgNB repeatedly notifies the MgNB of the status. This increases the amount of signaling in the base station interface and increases the amount of processing in the MgNB and SgNB.
[0106] Solutions to the aforementioned problems are disclosed below.
[0107] The SgNB notifies that data passing through the SgNB is inactive in communication between the SgNB and a connected UE. The data passing through the SgNB may be data using an SCG bearer, data passing through an SCG split bearer, or data passing through an MCG split bearer. The notification may be transmitted when the data satisfies an inactive condition. The notification may be transmitted only once or multiple times. For example, when the data transitions between a case where the data satisfies an inactive condition and a case where the data does not satisfy the inactive condition, the SgNB may transmit the notification multiple times. As another example, the SgNB may transmit the notification periodically.
[0108] The MgNB does not need to inquire of the SgNB whether data passing through the SgNB is inactive, which can reduce, for example, the amount of signaling in the interface between base stations.
[0109] The MgNB may notify the SgNB of an instruction to start evaluating the inactivity of data passing through the SgNB. The SgNB may use the instruction to start evaluating the inactivity of data passing through its own SgNB. As another example, the MgNB may not notify the SgNB of an instruction to start the evaluation. The SgNB may automatically start the evaluation. For example, the SgNB may start the evaluation when the DC configuration is established. This makes it possible to reduce, for example, the amount of signaling in the interface between base stations.
[0110] The conditions for determining whether data passing through the SgNB is inactive may be predefined in a standard.
[0111] As another example, the judgment condition may be determined by an upper NW device and notified to a subordinate gNB. The above-mentioned upper NW device may be, for example, an AMF (Access and Mobility Management Function) or an SMF (Session Management Function). The judgment condition may be different for each UE or for each gNB. Flexible setting is possible for each UE or for each gNB.
[0112] The upper NW device may notify the MgNB of the judgment condition determined by the upper NW device. The MgNB may notify the SgNB of the judgment condition. As another example, the upper NW device may determine the judgment condition and notify the subordinate gNB. Since the upper NW device can notify the judgment condition only to the MgNB and SgNB, the amount of signaling between the upper NW device and the base station can be reduced.
[0113] As another example, the judgment condition may be determined by the MgNB. The MgNB may notify the secondary base station of the determined judgment condition. The determination of the judgment condition by the MgNB and / or the notification of the judgment condition to the SgNB may be applied when the MgNB makes the above-mentioned inquiry to the SgNB, or when the above-mentioned inquiry is not made. The judgment condition may be included in signaling in the DC establishment sequence with the SgNB, or may be included in an inquiry from the MgNB to the SgNB about whether data passing through the SCG bearer and the SCG split bearer is inactive. It may be included in the instruction to start the evaluation of inactivity of data passing through the SgNB.
[0114] As another example, the SgNB may determine the judgment condition. For example, it is possible to reduce the amount of signaling required for notifying the judgment condition.
[0115] The above-mentioned judgment condition may be given by time. For example, when the SgNB does not communicate with the UE for a certain period of time or more, the SgNB may judge that the data is inactive. The above-mentioned certain period of time may be given for each bearer. Also, the above-mentioned period of time may be given according to the number of UEs in the RRC_CONNECTED state. Thereby, for example, when the number of UEs in the RRC_CONNECTED state is large, the time until the data is judged to be inactive can be shortened, thereby improving the efficiency of communication in the entire system.
[0116] The aforementioned time may be determined using information about the UE. For example, the aforementioned time may be set shorter than that of a normal UE using information indicating that the UE is for IoT. As another example, the aforementioned time may be set shorter for a UE with a small battery capacity using information about the battery capacity. This makes it possible to reduce the power consumption of the UE, for example.
[0117] The MgNB and / or SgNB may notify the eNB / gNB in the RAN area related to paging of the UE AS context in advance. The above-mentioned UE AS context may include only the information of the MgNB / SgNB, or may include information of both the MgNB and the SgNB. For example, only the MgNB may notify the base station in the RAN area related to paging of the UE AS context including information of both the MgNB and the SgNB. As another example, each of the MgNB and the SgNB may notify the base station in the RAN area related to paging of the UE AS context including information of its own gNB. This enables, for example, a quick start of communication after paging when UE mobility occurs.
[0118] As another example, each of the MgNB and the SgNB may notify the UE AS context including information of both the MgNB and the SgNB. The notification may be performed, for example, when the RAN areas related to paging of the MgNB and the SgNB are different. This enables, for example, state control of the UE in the above case.
[0119] The eNB / gNB may inquire about the UE AS context to another eNB / gNB in the RAN area for paging. The inquiry may be performed during a random access process between the UE and the eNB / gNB. The other eNB / gNB may notify the eNB / gNB of the UE AS context. The UE AS context may include information of the MgNB / SgNB alone, or may include information of both the MgNB and the SgNB. The amount of signaling in the inter-base station interface can be reduced.
[0120] The downlink data notification transmitted from the SgNB to the MgNB may include information on a random access preamble used by the UE in random access processing with the SgNB. The information on the random access preamble of the SgNB in the downlink data notification may be added to the notification of the random access preamble when DC is configured. The information on the random access preamble may be different from or the same as the information on the random access preamble notified from the SgNB to the MgNB when DC is configured. This allows, for example, the random access processing between the UE and the SgNB to be performed quickly. In addition, information on the transmission power from the UE of the random access preamble may be included. The same effect as above can be obtained. In addition, information on the beam of the SgNB used for communication between the SgNB and the UE may be included. This allows the UE to quickly capture the beam of the SgNB. In addition, other information necessary for paging may be included. For example, it may be information on the identifier of the UE, information on the PDU session, or information on the QoS flow. Information on the RAN area to which the SgNB belongs and used for paging may be included.
[0121] The paging from the MgNB to the UE may include information indicating that data has been generated in the SgNB. The information may be, for example, an identifier indicating that data has been generated in the SgNB, or an identifier of the SgNB. In addition, the same information as the downlink data notification transmitted from the SgNB to the MgNB described above may be included. The same effect as that obtained by the information included in the downlink data notification can be obtained.
[0122] In paging from the MgNB to the UE, information indicating that data has been generated in the MgNB may be included. The information may be the same as the information indicating that data has been generated in the SgNB. Also, information regarding a random access preamble used by the UE in random access processing with the MgNB may be included. This allows, for example, the random access processing between the UE and the MgNB to be performed quickly. Also, information regarding the transmission power from the UE of the random access preamble may be included. The same effect as above can be obtained. Also, information regarding the beam of the MgNB used for communication between the MgNB and the UE may be included. This allows the UE to quickly capture the beam of the MgNB.
[0123] The UE may use the paging to initiate a random access procedure with the MgNB. The UE may request the MgNB to resume the RRC connection. The UE may make the request after a random access response from the MgNB. The MgNB may instruct the UE to resume the RRC connection. The indication may be made after the request from the UE to the MgNB. The UE may use the indication to return to the RRC_CONNECTED state.
[0124] The UE may initiate a random access process to the SgNB. The random access process performed by the UE to the SgNB may be performed after the UE returns to the RRC_CONNECTED state. This makes it possible to avoid the complexity of the design of the communication system. Alternatively, the random access process may be performed while the UE is in the RRC_INACTIVE state. For example, the UE may transmit a random access preamble to the SgNB without waiting for a random access response from the MgNB. As another example, the UE may transmit a random access preamble to the SgNB after waiting for a random access response from the MgNB. This allows, for example, the UE to quickly resume data transmission and reception with the SgNB.
[0125] Figures 8 and 9 are sequence diagrams showing an operation of a UE transitioning to an RRC_INACTIVE state and an operation of a UE returning to an RRC_CONNECTED state in the present embodiment 1. Figures 8 and 9 are connected at the position of a boundary line BL0809. Figures 8 and 9 show an example in which the MgNB does not inquire of the SgNB whether data passing through the SgNB is inactive.
[0126] In step ST801 shown in Fig. 8, the UE is in an RRC_CONNECTED state. In step ST802, the SgNB determines that data passing through its own SgNB has become inactive. In step ST803, the SgNB notifies the MgNB that all data using bearers passing through its own SgNB is inactive.
[0127] In Step ST805 shown in FIG. 8, the MgNB instructs the UE to transition to the RRC_INACTIVE state, using the notification received from the SgNB in Step ST803 and the fact that data using a bearer passing through the MgNB is inactive. The instruction includes an identifier used to return to RRC_CONNECTED, for example, a resume ID. The instruction may also use signaling of an RRC connection release. The signaling of the RRC connection release includes information indicating that the UE is to transition to RRC_INACTIVE. Through Step ST805, the UE transitions to the RRC_INACTIVE state in Step ST808.
[0128] In the example shown in Fig. 8, the signaling of the RRC connection release is used in Step ST805, but other RRC signaling may be used. The other RRC signaling described above may also include an identifier used for returning to the RRC_CONNECTED state, or may include information indicating that the UE is to transition to the RRC_INACTIVE state.
[0129] In step ST806 shown in Fig. 8, the MgNB notifies the SgNB of the suspension of the connection with the UE. The SgNB uses step ST806 to suspend the connection with the UE. The suspension of the connection may be, for example, suspension of the SCG bearer, the SCG side path of the SCG split bearer, and the SCG side path of the MCG split bearer.
[0130] In step ST804 shown in Fig. 8, downlink data from the UPF is transmitted to the SgNB. In step ST807, the SgNB notifies the MgNB that downlink data to the UE has been generated. In this notification, the UE may notify information on a random access preamble that is used for random access processing with the SgNB.
[0131] Steps ST809 to ST813, ST816, and ST820 shown in FIG. 9 show a procedure for returning from an RRC_INACTIVE state to an RRC_CONNECTED state between an MgNB and a UE. In step ST809, the MgNB transmits a paging to the UE. The paging may include an identifier of the SgNB. Also, information on a random access preamble used in random access processing with each of the MgNB and the SgNB may be notified.
[0132] In step ST810 shown in FIG. 9, the UE transmits a random access preamble to the MgNB, and in step ST811, the MgNB notifies the UE of a random access response. In step ST812, the UE requests the MgNB to return to RRC_CONNECTED. The request includes an identifier used for returning to RRC_CONNECTED, which was notified to the UE from the MgNB in step ST805. The request may use, for example, signaling of an RRC connection resume request (RRCConnectionResumeRequest). The MgNB uses the request in step ST812 and the identifier to determine whether or not to return the UE to the RRC_CONNECTED state. In step ST813, the MgNB instructs the UE to return to the RRC_CONNECTED state. In step ST816, the UE returns to the RRC_CONNECTED state. In step ST820, the UE notifies the MgNB that it has returned to the RRC_CONNECTED state. For this notification, for example, signaling of RRC connection resume complete (RRCConnectionResumeComplete) may be used.
[0133] In steps ST814 and ST815 shown in Fig. 9, the connection between the SgNB and the UE is resumed. The resumption may be, for example, the resumption of the SCG bearer, the SCG side path of the SCG split bearer, and the SCG side path of the MCG split bearer. In step ST814, the MgNB requests the SgNB to resume the connection with the UE. In step ST815, the SgNB notifies the MgNB that the connection with the UE has been resumed.
[0134] In steps ST817 and ST818 shown in Fig. 9, a random access process is performed between the UE and the SgNB. In step ST817, a random access preamble is transmitted from the UE to the SgNB. The random access preamble may be a random access preamble notified to the UE from the MgNB in step ST829. In step ST818, a random access response is notified to the UE from the SgNB.
[0135] 9, downlink data including the data transmitted from the UPF to the SgNB in Step ST804 is transmitted from the SgNB to the UE. This resumes downlink communication passing through the SgNB.
[0136] 8 and 9 show an example in which the random access process between the UE and the SgNB is performed in the RRC_CONNECTED state, but it may be performed in the RRC_INACTIVE state. For example, steps ST817 and ST818 may be performed between steps ST809 and ST816. Step ST817 may be performed before step ST810, after step ST810, or after step ST811. This makes it possible to quickly resume communication between the UE and the SgNB, for example.
[0137] This embodiment 1 makes it possible to reduce the amount of signaling between base stations regarding inactivity status inquiries and / or notifications of data using SCG bearers and SCG split bearers. Also, even when data is generated through the SgNB, the MgNB can transition the UE to the RRC_CONNECTED state. This makes it possible to efficiently realize communication using DC.
[0138] According to the first embodiment, for example, the following configuration is provided.
[0139] A communication system is provided that includes a communication terminal device and a plurality of base station devices configured to be able to wirelessly communicate with the communication terminal device. More specifically, the plurality of base station devices include a master base station device and a secondary base station device that configure a bearer for the communication terminal device. When the secondary base station device detects a data inactive state in which downlink data to the communication terminal device is inactive for all bearers, the secondary base station device notifies the master base station device of the occurrence of the data inactive state even without an inquiry from the master base station device. By receiving the notification of the occurrence of the data inactive state, the master base station device transmits an instruction to the communication terminal device to transition from an RRC_CONNECTED state to an RRC_INACTIVE state. The communication terminal device transitions to the RRC_INACTIVE state in response to an instruction from the master base station device.
[0140] In this configuration, at least one of the master base station apparatus and the secondary base station apparatus may hold information regarding the connection with the communication terminal apparatus even after the communication terminal apparatus has transitioned to the RRC_INACTIVE state.
[0141] According to the first embodiment, for example, the following configuration is also provided.
[0142] A communication system is provided that includes a communication terminal device and a plurality of base station devices configured to be able to wirelessly communicate with the communication terminal device. More specifically, the plurality of base station devices include a master base station device and a secondary base station device that configure a bearer for the communication terminal device. When the secondary base station device detects that downlink data to the communication terminal device in the RRC_INACTIVE state has occurred, the secondary base station device notifies the master base station device of the occurrence of the downlink data. Upon receiving the notification of the occurrence of the downlink data, the master base station device transmits paging to the communication terminal device. Upon receiving the paging, the communication terminal device requests the master base station device to return to the RRC_CONNECTED state. Here, the paging includes at least one of information regarding the connection between the communication terminal device and the master base station device and information regarding the connection between the communication terminal device and the secondary base station device.
[0143] The above configuration can be modified in various ways based on the disclosures and suggestions of this specification, including embodiment 1. According to the above configuration and modified configurations, the above problems can be solved and the above effects can be obtained.
[0144] Variation 1 of the first embodiment The following problem occurs in the state control of a UE using a DC configuration. That is, the operation of the UE, MgNB, and SgNB is not defined when downlink data for the UE is transmitted from an upper NW device to the MgNB or SgNB immediately after the MgNB notifies the UE of a transition instruction to the RRC_INACTIVE state. Therefore, for example, a problem occurs in which a discrepancy in the UE state occurs between the UE and the MgNB or SgNB. The same problem occurs even when uplink data occurs in the UE immediately after the MgNB notifies the UE of the transition instruction.
[0145] Solutions to the aforementioned problems are disclosed below.
[0146] The UE transitions to the RRC_INACTIVE state once and then returns to the RRC_CONNECTED state. The MgNB may instruct the UE to transition to the RRC_INACTIVE state.
[0147] The above-mentioned operation may be applied when downlink data is generated. That is, the MgNB may transmit paging to the UE. The transmission of the paging from the MgNB to the UE may be immediately after the instruction to transition to the RRC_INACTIVE state. The MgNB may transmit the paging to the UE using the reception of downlink data from an upper NW device. Alternatively, the MgNB may transmit the paging to the UE using a notification indicating the generation of downlink data from the SgNB to the MgNB. The SgNB may transmit the notification to the MgNB using the reception of downlink data from the upper NW device.
[0148] The SgNB may transmit a notification indicating the occurrence of downlink data to the MgNB prior to a notification of UE connection stop from the MgNB to the SgNB. This allows for a reduction in the amount of processing in the SgNB. Alternatively, the notification indicating the occurrence of downlink data may be transmitted after the notification of UE connection stop. This allows for a reduction in the complexity of the communication system design.
[0149] The operation of the UE transitioning to the RRC_INACTIVE state once and then returning to the RRC_CONNECTED state may be applied when uplink data is generated. That is, the UE may start a random access process to the MgNB. The subsequent process may be the same as when downlink data is generated. Also, when uplink data is generated, the UE may perform a random access process to the SgNB after the UE returns to the RRC_CONNECTED state, or may perform the process during the RRC_INACTIVE state. The random access process to the SgNB by the UE may be performed after waiting for a random access response from the MgNB, or may be performed before the random response access from the MgNB. A random access preamble may be transmitted from the UE to the SgNB before the random access preamble is transmitted from the UE to the MgNB. The same effect as when downlink data is generated can be obtained.
[0150] As an example of a sequence in which a UE transitions to the RRC_INACTIVE state once and then returns to the RRC_CONNECTED state, step ST804 in Fig. 8 may be a sequence between steps ST803 and ST806. As an example of a sequence in which a UE transitions to the RRC_INACTIVE state once and then returns to the RRC_CONNECTED state, step ST807 in Fig. 8 may be a sequence before or after step ST806.
[0151] Another solution is presented: the UE suspends the transition to the RRC_INACTIVE state. This makes it possible, for example, to reduce the delay until data transmission and reception between the UE and the SgNB is resumed.
[0152] The MgNB may not notify the UE of the RRC connection release (RRCConnectionRelease). The above operation may be applied, for example, to a case where DL data transmission from the UPF to the SgNB and downlink data notification from the SgNB to the MgNB are performed before the MgNB transmits the RRC connection release signaling to the UE. In the above case, the MgNB may not notify the SgNB of the UE connection stop instruction. This makes it possible, for example, to quickly resume communication between the UE and the SgNB.
[0153] Another example is disclosed. A waiting time may be provided in the UE between the reception of an RRC_INACTIVE state transition instruction from the MgNB and the start of a transition process to the RRC_INACTIVE state. The UE may suspend the transition to the RRC_INACTIVE state using uplink data to the MgNB and / or SgNB that occurs during the waiting time. The UE may also use the reception of downlink data from the MgNB and / or SgNB. The UE may also use an instruction from the MgNB to suspend the RRC_INACTIVE state transition. The UE transitions to the RRC_INACTIVE state after the waiting time has elapsed.
[0154] The waiting time may be set by the MgNB. The MgNB may suspend the transition of the UE to the RRC_INACTIVE state during the waiting time using the occurrence of downlink data passing through the MCG bearer or the MCG split bearer. The MgNB may also suspend the transition of the UE to the RRC_INACTIVE state using the reception of a downlink data notification from the SgNB. The MgNB may also suspend the transition of the UE to the RRC_INACTIVE state using information on uplink data from the UE, such as uplink data, SR, and BSR. The MgNB may determine that the UE has transitioned to the RRC_INACTIVE state after the waiting time has elapsed.
[0155] The waiting time may be set by both the UE and the MgNB. The waiting times in the UE and the MgNB may be the same or different. The UE and / or the MgNB may set a waiting time for uplink data and a waiting time for downlink data separately. The waiting time for uplink data and the waiting time for downlink data may be the same or different. For example, the base station may set the waiting time for uplink data longer than the waiting time set by the UE. As another example, the UE may set the waiting time for downlink data longer than the waiting time set by the MgNB. This makes it possible to prevent a discrepancy in understanding between the UE and the MgNB regarding the RRC state of the UE when the waiting time for uplink data in the UE is exceeded during the HARQ retransmission of the uplink data, for example.
[0156] The waiting time may be determined by a standard. This makes it possible to avoid complexity in designing a communication system. As another example, the waiting time may be determined by the MgNB. The MgNB may notify the UE of the waiting time. Signaling at the time of DC configuration may be used to notify the waiting time. For example, the MgNB may include information about the waiting time in the signaling of RRC connection reconfiguration and notify the UE of the waiting time.
[0157] A method for a UE to abort a transition to an RRC_INACTIVE state is disclosed. The MgNB may notify the UE of an instruction to abort a transition to an RRC_INACTIVE state. The UE may abort a transition to an RRC_INACTIVE state using the instruction. The instruction may be an RRC dedicated signaling. For example, a new signaling called an RRC connection release cancel may be provided as the RRC dedicated signaling. The instruction may include an identifier, for example, a resume ID, used to return to an RRC_CONNECTED state.
[0158] Other signaling may be used as the above-mentioned RRC dedicated signaling. For example, RRCConnectionResume may be used. The RRC connection resume signaling may include information indicating the interruption of the transition to the RRC_INACTIVE state. Also, an identifier used for returning to the RRC_CONNECTED state, for example, a resume ID, may be included. This makes it possible to avoid system complexity by suppressing an increase in the types of RRC signaling.
[0159] The MgNB may notify the UE of the suspension instruction by using the occurrence of downlink data passing through the MgNB during the waiting time. In the above, the downlink data passing through the MgNB may be downlink data using an MCG bearer, downlink data using an MCG split bearer, or downlink data using an SCG split bearer. The MgNB may notify the UE of the suspension instruction by using the fact that a downlink data notification is received from the SgNB during the waiting time.
[0160] Figure 10 is a sequence diagram showing an operation in which the RRC_INACTIVE state transition in the UE is interrupted by an RRC_INACTIVE state transition interrupt instruction from the MgNB. Like Figures 8 and 9, Figure 10 shows an example in which downlink data to the UE is transmitted from the UPF to the SgNB immediately after an SCG data inactivity notification from the SgNB to the MgNB. The sequence shown in Figure 10 includes the same steps as the sequences shown in Figures 8 and 9, so the same step numbers are assigned to the same steps and common explanations are omitted.
[0161] Steps ST801 to ST807 in FIG. 10 are the same as those in FIG. 8, and therefore the description thereof will be omitted.
[0162] In FIG. 10, the MgNB receives the downlink data notification in step ST807 within a certain period of time from the transmission of the RRC_INACTIVE transition instruction in step ST805, and thus instructs the UE to suspend the RRC_INACTIVE transition in step ST901. The instruction includes an identifier used for returning to RRC_CONNECTED, for example, a resume ID. The instruction may also use, for example, signaling of RRC connection release suspension (RRCConnectionReleaseCancel). In step ST901, the UE suspends transition to the RRC_INACTIVE state and maintains the RRC_CONNECTED state.
[0163] In the example shown in FIG. 10, signaling of RRC connection release interruption is used in step ST901, but other RRC signaling may be used. The above-mentioned other RRC signaling may also include an identifier used for returning to RRC_CONNECTED. For example, RRC connection resume may be used. The signaling of the RRC connection resume may include information indicating interruption of transition to the RRC_INACTIVE state.
[0164] Steps ST814 to ST815 in FIG. 10 are the same as those in FIG. 9, and therefore the description thereof will be omitted.
[0165] In FIG. 10, the UE maintains the RRC_CONNECTED state, and therefore does not perform random access processing with the MgNB and SgNB, unlike in FIG. 8 and FIG.
[0166] Step ST819 shown in FIG. 10 is the same as that in FIG. 9, and therefore the explanation will be omitted.
[0167] In FIG. 10, the SgNB may transmit a downlink data notification shown in step ST807 to the MgNB without waiting for a UE connection stop instruction shown in step ST806. The MgNB may not notify the SgNB of a UE connection stop instruction. The operation in which the MgNB does not notify the SgNB of a UE connection stop instruction may be applied to the case in which the SgNB transmits a downlink data notification to the MgNB without waiting for a UE connection stop instruction. The UE connection resumption request and the UE connection resumption response may be the same as the UE connection stop instruction described above. This makes it possible to reduce the amount of signaling in the interface between base stations.
[0168] Also, the MgNB may transmit the UE connection stop instruction to the SgNB after a certain time has elapsed since the reception of the SCG data inactivity notification. The certain time may be the same as a waiting time provided in the UE from the reception of the RRC_INACTIVE state transition instruction from the MgNB to the start of the transition process to the RRC_INACTIVE state. This allows the SgNB to grasp the time until the UE transitions to RRC_INACTIVE, for example, and thus makes it easier to control the UE in the SgNB.
[0169] Another method for the UE to suspend the transition to the RRC_INACTIVE state is disclosed. The UE suspends the transition to the RRC_INACTIVE state by receiving downlink data. The MgNB may transmit downlink data to the UE immediately after the MgNB issues an RRC_INACTIVE state transition instruction to the UE. The SgNB may transmit the downlink data to the UE. The SgNB may transmit the downlink data immediately after the SCG data inactivity notification. The downlink data transmitted by the MgNB and / or SgNB to the UE may be data passing through the MCG bearer and / or the MCG split bearer, or may be data passing through the SCG bearer and / or the SCG split bearer. The SgNB may transmit a downlink data notification to the MgNB. The management of the UE state in the MgNB is facilitated. The MgNB may transmit a UE connection stop instruction to the SgNB after the above-mentioned waiting time has elapsed. The SgNB is able to grasp the time until the UE transitions to RRC_INACTIVE, which facilitates the control of the SgNB.
[0170] Another method for the UE to suspend the transition to the RRC_INACTIVE state is disclosed. The UE suspends the transition to the RRC_INACTIVE state by transmitting uplink data to the MgNB and / or SgNB. Since an RRC_INACTIVE state transition suspension instruction from the MgNB to the UE is not required, the amount of signaling can be reduced. The uplink data may be data passing through the MCG bearer and / or the MCG split bearer, or may be data passing through the SCG bearer and / or the SCG split bearer. An SR may be used instead of the uplink data. The SR may be an SR addressed to the MgNB or an SR addressed to the SgNB. Alternatively, a BSR (Buffer Status Report) may be used. The BSR may be a BSR addressed to the MgNB or a BSR addressed to the SgNB. The MgNB and / or the SgNB may determine that the transition to the RRC_INACTIVE state of the UE has been suspended by using the fact that the uplink data buffer amount included in the BSR is not empty. The SgNB may transmit a notification to the MgNB indicating that it has received uplink data from the UE. Since the MgNB can grasp the status of uplink data passing through the SgNB, state control in the MgNB is facilitated. The above-mentioned uplink data notification may be transmitted to the MgNB when the SgNB receives an SR from the UE, or may be transmitted to the MgNB when the SgNB receives a BSR from the UE.
[0171] Figure 11 is a sequence diagram showing an operation in which the RRC_INACTIVE state transition in the UE is interrupted by the occurrence of uplink data. Figure 11 shows an example in which an SR for uplink data transmission is transmitted from the UE to the SgNB immediately after an SCG data inactivity notification from the SgNB to the MgNB. The sequence shown in Figure 11 includes the same steps as the sequences shown in Figures 8 and 9, so the same step numbers are assigned to the same steps and common descriptions are omitted.
[0172] Steps ST801, ST803, ST805, and ST806 in FIG. 11 are the same as those in FIG. 8, and therefore the description thereof will be omitted.
[0173] In step ST1001 shown in Fig. 11, in response to the occurrence of uplink data from the UE to the SgNB immediately after receiving the UE connection suspension instruction in step ST806, the UE transmits an SR to the SgNB. In step ST1002, the SgNB notifies the UE of a grant for transmitting uplink data, and in step ST1003, the SgNB transmits an uplink data notification to the MgNB.
[0174] Steps ST814 to ST815 in FIG. 11 are the same as those in FIG. 9, and therefore the description thereof will be omitted.
[0175] 11, the UE maintains the RRC_CONNECTED state. In Step ST1004, the UE transmits uplink data to the SgNB, and in Step ST1005, the SgNB transmits the uplink data to the UPF.
[0176] In the example shown in FIG. 11, the RRC_CONNECTED state is maintained by transmitting an SR in step ST1001, but a BSR may be used. Alternatively, uplink data transmission itself may be used. For example, the RRC_CONNECTED state can be maintained even in uplink data transmission without a grant.
[0177] In addition, in the example shown in Fig. 11, the SgNB transmits an uplink data notification to the MgNB after the grant for uplink data, but the uplink data notification may be transmitted before the grant for uplink data. For example, it becomes possible to quickly grasp the UE state in the MgNB.
[0178] In FIG. 11, the SR transmission shown in step ST1001 and the uplink data notification shown in step ST1003 may be executed before the UE connection stop instruction shown in step ST806. The MgNB may not notify the SgNB of the UE connection stop instruction shown in step ST806. The operation of the MgNB not notifying the SgNB of the UE connection stop instruction may be applied, for example, when the uplink data notification transmitted from the SgNB to the MgNB is performed before the UE connection stop instruction. Similarly, the MgNB may not notify the SgNB of the UE connection resumption request shown in step ST814, and the SgNB may not notify the MgNB of the UE connection resumption response shown in step ST815. This makes it possible to reduce the amount of signaling in the inter-base station interface, for example.
[0179] In addition, the MgNB may transmit the UE connection stop instruction to the SgNB after the above-mentioned waiting time has elapsed. Since the SgNB can know the time until the UE transitions to RRC_INACTIVE, it becomes easier to control the SgNB.
[0180] The method disclosed in this modified example 1 may be applied to a base station and a UE that are not in a DC configuration. The base station and the UE that are not in a DC configuration may be, for example, a configuration in which the UE is connected to one base station, or a configuration of multi-connectivity (abbreviated as MC). The same effect as the configuration in DC can be obtained.
[0181] This first variant makes it possible to prevent malfunctions when data is sent or received immediately after the UE receives an RRC_INACTIVE transition instruction from the MgNB, thereby improving the robustness of the system.
[0182] Variation 2 of embodiment 1 As a mobility method for a UE in the RRC_INACTIVE state, a procedure that combines Inter-gNB Resume, MN (Master Node) handover, and SN change (Secondary Node Change) is used.
[0183] When the above-mentioned method is applied, the following problem occurs. That is, it is not clear who decides the destination SgNB for a UE in the RRC_INACTIVE state. Therefore, a problem occurs in that a UE in the RRC_INACTIVE state cannot perform SgNB mobility.
[0184] Solutions to the aforementioned problems are disclosed below.
[0185] The UE determines the SgNB. The UE uses cell reselection to determine the SgNB. The UE determines the cell detected in cell reselection as the SgNB.
[0186] The UE may measure neighboring cells periodically, which may be determined by a standard or may be the same as the DRX period.
[0187] Alternatively, the UE may measure neighboring cells when receiving paging, which can reduce the amount of processing performed by the UE in the RRC_INACTIVE state.
[0188] The UE notifies the MgNB of information on the determined SgNB. The information may be, for example, an identifier of the SgNB, or an identifier of a cell belonging to the SgNB, for example, a physical cell identity (PSCell). The information may be included in RRC dedicated signaling from the UE to the MgNB, for example, an RRC connection resume request (RRCConnectionResumeRequest), or may be included in small data that can be transmitted in the RRC_INACTIVE state.
[0189] 12 to 14 are sequence diagrams showing the operation of a UE in an RRC_INACTIVE state to determine an SgNB. FIGS. 12 to 14 are connected at the positions of borders BL1213 and BL1314. FIGS. 12 to 14 show an example in which mobility of an SgNB occurs in an RRC_INACTIVE state in a UE using a DC configuration, and switching occurs from an S-SgNB to a T-SgNB. In FIGS. 12 to 14, the UE returns to RRC_CONNECTED due to the occurrence of downlink data passing through the SgNB. The sequences shown in FIGS. 12 to 14 include the same steps as the sequences shown in FIGS. 8 and 9, and therefore the same step numbers are assigned to the same steps, and common explanations are omitted.
[0190] In step ST1101 shown in Fig. 12, the UE is in an RRC_INACTIVE state. In step ST1102, the UE determines a destination SgNB. In the examples of Figs. 12 to 14, the destination SgNB is a T-SgNB. The UE may use cell reselection in determining the SgNB.
[0191] In step ST1103 shown in FIG. 12, the UPF does not know that the SgNB of the UE has become the T-SgNB, and therefore transmits downlink data to the S-SgNB, which is the source SgNB. In step ST1104, the S-SgNB transmits a downlink data notification to the MgNB. The downlink data notification in step ST1104 may be the same as that in step ST807 in FIG. 8.
[0192] Steps ST809 to ST811 in FIG. 12 are the same as those in FIG. 9, and therefore the description thereof will be omitted.
[0193] In Step ST1108 in FIG. 12, the UE requests the MgNB to return to RRC_CONNECTED. The request includes information on the destination SgNB determined by the UE. The UE may notify the request by using signaling of an RRC connection resume request (RRCConnectionResumeRequest).
[0194] In step ST1109 in FIG. 13, the MgNB requests a UE context from the S-SgNB. In step ST1110, the S-SgNB transmits the UE context to the MgNB. In step ST1109, the MgNB may include information indicating a request for information for a secondary base station from among the UE context in the request. In step ST1110, the SgNB may transmit only information for a secondary base station from among the UE context to the MgNB. This makes it possible to reduce the amount of signaling related to UE context transmission, for example.
[0195] In Step ST1111 in FIG. 13, the MgNB notifies the T-SgNB of a secondary base station addition request (SN Addition Request). The request may include the UE context acquired from the S-SgNB. In the examples of FIGS. 12 to 14, the T-SgNB decides to accept the request. In Step ST1112, the T-SgNB notifies an acknowledgment to the request (secondary base station addition request acknowledgment; SN Addition Request ACK). In Step ST1113, the MgNB notifies the S-SgNB of a secondary base station release request (SN Release Request).
[0196] Steps ST813, ST816, and ST820 in FIG. 13 are the same as those in FIG. 9, and therefore the description thereof will be omitted.
[0197] In Step ST1115 shown in Fig. 13, the MgNB requests the T-SgNB to set up a connection with the UE. In Step ST1116, the T-SgNB notifies the MgNB that the setting has been completed.
[0198] In steps ST1118 and ST1119 shown in Fig. 14, random access processing is performed between the UE and the T-SgNB. The processing in steps ST1118 and ST1119 is similar to steps ST817 and ST818, respectively, shown in Fig. 9.
[0199] Steps ST1120 and ST1121 shown in Fig. 14 are processes in which the S-SgNB transfers a PDCP sequence number reception / delivery status to the T-SgNB via the MgNB. In step ST1120, the S-SgNB transfers to the MgNB the reception / delivery status of the PDCP sequence number transmitted and received from the UE. In step ST1121, the MgNB transfers the status received from the S-SgNB in step ST1120 to the T-SgNB.
[0200] Steps ST1123 and ST1124 shown in FIG.14 are processes of transferring downlink transmission data stored in the PDCP buffer of the S-SgNB to the T-SgNB via the MgNB. In step ST1123, the S-SgNB transfers the PDCP PDU stored in the PDCP buffer to the MgNB. In step ST1124, the MgNB transfers the PDCP PDU received from the S-SgNB in step ST1123 to the T-SgNB. The data transferred in steps ST1123 and ST1124 may include the data transmitted to the S-SgNB by the UPF in step ST1103.
[0201] In step ST1125 shown in FIG. 14, the MgNB notifies the SMF of a PDU session modification request. The PDU session modified by the request may be a PDU session passing through the SCG. In addition, in step ST1126, the SMF and the UPF modify the PDU session included in the PDU session modification request of step ST1125. In step ST1126, the PDU session may also be modified between the AMF and the UPF, as in step ST1125.
[0202] In Fig. 12 to Fig. 14, the SMF may be an AMF. Also, the SMF may be connected between the UPF and the AMF, and the AMF may be connected to each gNB, i.e., the MgNB, the T-SgNB, and the S-SgNB. This, for example, increases the flexibility of the configuration in the communication system. The same may be true hereinafter in the present invention.
[0203] In step ST1127 shown in FIG. 14, an end marker is added to the last packet when the route of the packet transmitted from the UPF switches from the S-SgNB to the T-SgNB, and the packet is transmitted from the UPF to the S-SgNB. In steps ST1128 and ST1129, the packet to which the end marker is added is forwarded from the S-SgNB to the T-SgNB via the MgNB. In step ST1128, the packet is forwarded from the S-SgNB to the MgNB, and in step ST1129, the packet is forwarded from the MgNB to the T-SgNB.
[0204] 14, the route of the packet transmitted from the UPF is switched from the S-SgNB to the T-SgNB, and the packet is transmitted from the UPF to the T-SgNB. In step ST1131, the packet transmitted in step ST1130 is transmitted from the T-SgNB to the UE.
[0205] In Step ST1132 shown in Fig. 14, the SMF notifies the MgNB that the PDU session change has been completed. In Step ST1133, the MgNB instructs the S-SgNB to release the UE context notified to the MgNB in Step ST1110, and the S-SgNB releases the UE context. In Step ST1132, the AMF may also perform the notification instead of the SMF, as in Steps ST1125 and ST1126.
[0206] In the examples shown in Fig. 12 to Fig. 14, the UE determines the destination SgNB using cell reselection, but the UE may use the measurement configuration notified from the MgNB. The measurement configuration may be the configuration acquired from the MgNB when the UE was in the RRC_CONNECTED state. For example, it is possible to increase the flexibility of the SgNB determination method.
[0207] When determining the SgNB, the UE may select the first detected cell among cells that satisfy a predetermined condition as the SgNB. For example, the SgNB detection can be performed quickly. Alternatively, the cell with the best condition may be selected as the SgNB. This makes it possible to improve the reliability of communication.
[0208] Another solution is presented. The MgNB determines the SgNB. The MgNB determines the SgNB using the measurement result notified from the UE.
[0209] The UE may perform the measurements periodically. The period may be determined by a standard. Alternatively, the period may be the same as the DRX period. Alternatively, the MgNB may notify the UE individually. Alternatively, the MgNB may report the measurements to the subordinate UEs.
[0210] Alternatively, the UE may perform the measurement when receiving a paging message, which can reduce the amount of processing performed by the UE in the RRC_INACTIVE state.
[0211] The UE may notify the MgNB of the measurement result. The UE may do this by using small data that can be transmitted in the RRC_INACTIVE state. This allows for quick notification of the measurement result. As another example, the measurement result may be notified as a measurement report. Alternatively, the measurement result may be included in the signaling of an RRC connection resume request (RRCConnectionResumeRequest).
[0212] The MgNB may use cell reselection criteria to determine the SgNB. The UE may inform the MgNB of measurement results used for cell reselection.
[0213] 15 to 17 are sequence diagrams showing the operation of the MgNB to determine the SgNB in communication with a UE in the RRC_INACTIVE state. FIGS. 15 to 17 are connected at the borders BL1516 and BL1617. FIGS. 15 to 17 show the case where the UE notifies the MgNB of the measurement result by using small data that can be transmitted in the RRC_INACTIVE state. In FIGS. 15 to 17, the UE returns to RRC_CONNECTED due to the occurrence of downlink data passing through the SgNB. The sequences shown in FIGS. 15 to 17 include the same steps as the sequences shown in FIGS. 8 and 9 and FIGS. 12 to 14, and therefore the same step numbers are assigned to the same steps and common explanations are omitted.
[0214] Steps ST1101, ST1103, and ST1104 shown in Fig. 15 are similar to those in Fig. 12, and therefore description thereof will be omitted. Fig. 15 is different from Fig. 12 in that the SgNB determination in the UE shown in step ST1102 in Fig. 12 is not performed.
[0215] Steps ST809 to ST812 in FIG. 15 are the same as those in FIG. 9, and therefore the description thereof will be omitted.
[0216] In step ST1202 shown in FIG. 15, the UE notifies the MgNB of the measurement result. In the example of FIG. 15, the notification is included in small data that can be transmitted in the RRC_INACTIVE state. Furthermore, the MgNB may notify the UE of the configuration related to the measurement when the UE is in the RRC_CONNECTED state. In step ST1203, the MgNB decides a destination SgNB. For this decision, the measurement result notified by the UE in step ST1202 may be used. In the examples of FIG. 15 to FIG. 17, a case is shown in which the destination SgNB is decided to be the T-SgNB.
[0217] Steps ST1109 to ST1113 in FIG. 16 are the same as those in FIG. 13, and therefore the description thereof will be omitted.
[0218] In step ST1204 shown in FIG. 16, similarly to step ST813 in FIG. 13, the MgNB instructs the UE to transition to RRC_CONNECTED. The instruction in step ST1204 includes information on the target SgNB determined by the MgNB. The information on the target SgNB may be, for example, an SgNB identifier or a PSCell identifier, for example, a physical cell identifier. The UE recognizes that the target SgNB is a T-SgNB using step ST1204.
[0219] The sequence from step ST816 onward in FIGS. 16 and 17 is similar to that in FIGS. 13 and 14, and therefore description thereof will be omitted.
[0220] Another solution is presented. Both the case where the MgNB determines the SgNB and the case where the UE determines the SgNB are provided. Information about the entity that determines the SgNB may be defined in the standard, may be notified from the MgNB to the UE, or may be notified from an upper NW device, such as the SMF or AMF, to the MgNB and / or the UE.
[0221] As an example of a standard that defines the subject of determining the SgNB, the presence or absence of the mobility of the MgNB in the UE in the RRC_INACTIVE state may be used. For example, when the mobility of the MgNB occurs, the UE may determine the SgNB, or when the mobility of the MgNB occurs, the destination MgNB may determine the SgNB. In the above, the mobility of the MgNB may be determined by the UE.
[0222] In determining the SgNB in the UE, for example, cell reselection may be used. Alternatively, measurement configuration notified from the MgNB in the RRC_CONNECTED state may be used.
[0223] In determining the SgNB in the UE, for example, among cells that satisfy a certain condition, the first detected cell may be the destination MgNB, or the next detected cell may be the destination SgNB. This allows, for example, the UE to quickly determine the MgNB and SgNB.
[0224] As another example, the cell with the best condition may be the MgNB, and the cell with the second best condition may be the SgNB. This allows for improved reliability of communication. Alternatively, conversely, the cell with the best condition may be the SgNB, and the cell with the second best condition may be the MgNB. For example, when C-Plane communication is assigned to the MgNB, and U-Plane communication is assigned to the SgNB, it allows for improved transmission speed and reliability in U-Plane communication.
[0225] In determining the SgNB in the MgNB, for example, the measurement configuration notified to the UE from the MgNB in the RRC_CONNECTED state may be used. Alternatively, the measurement configuration used in cell reselection may be used.
[0226] 18 to 20 are sequence diagrams showing the operation of a UE in an RRC_INACTIVE state to determine a destination MgNB and a destination SgNB. FIGS. 18 to 20 are connected at the positions of borders BL1819 and BL1920. The examples of FIGS. 18 to 20 show the case where the source MgNB and the destination MgNB are S-MgNB and T-MgNB, respectively, and the source SgNB and the destination SgMB are S-SgNB and T-SgNB, respectively. In FIGS. 18 to 20, the UE returns to RRC_CONNECTED due to the occurrence of downlink data passing through the SgNB. In addition, in FIGS. 18 to 20, the S-MgNB and the T-MgNB belong to the same RAN area. The sequences shown in FIGS. 18 to 20 include the same steps as the sequences shown in FIGS. 8 and 9, and FIGS. 12 to 14, so the same step numbers are assigned to the same steps and common explanations are omitted.
[0227] In FIG. 18, steps ST1101 and ST1103 are the same as those in FIG. 12, and therefore the description thereof will be omitted.
[0228] In step ST1300 shown in FIG. 18, the UE determines the target MgNB and target SgNB to be the T-MgNB and the T-SgNB, respectively.
[0229] In Step ST1301 shown in FIG. 18, the S-SgNB notifies the S-MgNB that downlink data has occurred. In Step ST1302, the S-MgNB notifies the T-MgNB belonging to the same RAN area of paging information for the UE.
[0230] In step ST1303 shown in FIG18, the T-MgNB transmits paging to the UE using the paging information notified in step ST1302. In steps ST1304 and ST1305, the UE performs random access processing with the T-MgNB. This random access processing is similar to steps ST810 and ST811 shown in FIG9.
[0231] In Step ST1306 shown in Fig. 18, the UE notifies the T-MgNB of a request to return to the RRC_CONNECTED state. Step ST1306 may use signaling of an RRC connection resume request (RRCConnectionResumeRequest) as in Step ST812 in Fig. 9. Also, the notification in Step ST1306 may include information indicating the destination MgNB and destination SgNB determined by the UE. In the example in Fig. 18, information on the T-MgNB and the T-SgNB is included.
[0232] Steps ST1307 and ST1308 shown in FIG. 18 represent a UE context transfer process for the MgNB. In step ST1307, the T-MgNB requests a UE context from the S-MgNB. In step ST1308, the S-MgNB transmits the UE context to the T-MgNB. In step ST1307, the T-MgNB may include information indicating a request for information for the master base station from among the UE context, in the request. In step ST1308, the S-MgNB may transmit only information for the master base station from among the UE context to the T-MgNB. This makes it possible to reduce the amount of signaling related to UE context transmission, for example.
[0233] Steps ST1309 to ST1311 shown in Fig. 19 represent a UE context transfer process for an SgNB and an SgNB addition process. The UE context is transferred from the S-SgNB to the T-SgNB via the T-MgNB. Steps ST1309 to ST1311 perform the same processes as steps ST1109 to ST1111 shown in Fig. 13. In step ST1312, the T-SgNB sends a positive response to the secondary base station addition request to the T-MgNB. In step ST1313, the T-MgNB sends a secondary base station release request to the S-SgNB.
[0234] In Step ST1315 shown in Fig. 19, the T-MgNB transmits an instruction to the UE to transition to RRC_CONNECTED. The instruction may be the same as that in Step ST813 in Fig. 9.
[0235] In Step ST816 shown in Fig. 19, the UE transitions to the RRC_CONNECTED state. In Step ST1318, the UE notifies the T-MgNB that the transition to the RRC_CONNECTED state has been completed.
[0236] Steps ST1316 and ST1317 shown in FIG. 19 are steps ST814 and ST815 shown in FIG. 9 in which the MgNB is replaced with a T-MgNB and the SgNB is replaced with a T-SgNB.
[0237] Steps ST1118 and ST1119 in FIG. 19 are similar to those in FIG. 14, and therefore the description thereof will be omitted.
[0238] Steps ST1321 to ST1327 shown in FIG. 20 are steps ST1120 to ST1124 shown in FIG. 14, where MgNB is replaced with T-MgNB.
[0239] In the example of Fig. 20, the PDCP sequence number reception / delivery status and PDCP PDU are transferred directly from the S-SgNB to the T-MgNB in steps ST1321 and ST1325, but they may be transferred via the S-MgNB. For example, even if a connection between the S-SgNB and the T-MgNB is not established, switching of both the MgNB and the SgNB is possible.
[0240] In step ST1328 shown in FIG. 20, the T-MgNB requests the SMF to switch the communication path (Path Switch Request). The request may include a request for switching the PDU session in the MgNB and SgNB. In step ST1329, the communication path is switched between the SMF and the UPF. The PDU session may be switched in the MgNB and the SgNB. Also, in steps ST1328 and ST1329, the AMF may be used instead of the SMF.
[0241] Steps ST1330 to ST1332 shown in Fig. 20 are obtained by replacing the MgNB with a T-MgNB in steps ST1127 to ST1129 shown in Fig. 14. Step ST1331 may be performed via an S-MgNB, similar to steps ST1321 and ST1325.
[0242] Steps ST1130 and ST1131 in FIG. 20 are similar to those in FIG. 14, and therefore the description thereof will be omitted.
[0243] In Step ST1336 shown in FIG. 20, the SMF notifies the T-MgNB of the completion of switching of the communication path (Path Switch Complete). In Step ST1337, the T-MgNB instructs the S-MgNB to release the UE context for the MgNB. In Step ST1338, the T-MgNB instructs the S-SgNB to release the UE context for the SgNB.
[0244] In step ST1338 shown in FIG. 20, an example has been shown in which the T-MgNB notifies the UE context release for the SgNB, but the notification may be made via the S-MgNB. Alternatively, the S-MgNB may notify the S-SgNB of an instruction to release the UE context for the SgNB. In step ST1337, the T-MgNB may include an instruction to release the UE context for the SgNB in the notification to the S-MgNB. This makes it possible to reduce the amount of signaling in the interface between base stations.
[0245] Another solution is presented. The upper NW device determines the SgNB. The upper NW device may be an AMF or an SMF. The upper NW device notifies the MgNB of the information of the determined SgNB. The MgNB notifies the UE of the information of the SgNB.
[0246] The upper network device may determine the SgNB using the load status of the subordinate gNB. The load status may be, for example, the load in the interface between base stations, the processing load, the load of radio resources, the number of accommodated UEs, or a combination of the above information. This makes it possible to determine the SgNB according to the load status of the gNB, for example, and thus enables optimization as a communication system.
[0247] The MgNB and / or SgNB may notify the UE AS context to the eNB / gNB in the RAN area related to paging in advance. In the above-mentioned notification, the same method as that of the first embodiment may be used. For example, when the mobility of the UE occurs, it is possible to start communication quickly after paging.
[0248] Alternatively, the eNB / gNB may inquire about the UE AS context to another eNB / gNB in the RAN area for paging. The inquiry may be performed during a random access process between the UE and the eNB / gNB. The other eNB / gNB may notify the eNB / gNB of the UE AS context. The UE AS context may include information of the MgNB / SgNB alone, or may include information of both the MgNB and the SgNB. This makes it possible to reduce the amount of signaling in the interface between base stations.
[0249] By using this variant example 2, SgNB mobility is possible for UEs in RRC_INACTIVE state.
[0250] Embodiment 2 A DC-configured UE transmits small data to an MgNB in an RRC_INACTIVE state. The MgNB may change the bearer configuration when the UE transitions to RRC_INACTIVE. The bearer configuration may be changed, for example, from an SCG bearer to an MCG bearer. As another example, the bearer configuration may be changed from an SCG bearer to an SCG split bearer. This enables communication with low latency by transmitting small data for data that used an SCG bearer before the bearer change.
[0251] When the above-mentioned method is applied, the following problem occurs: When the UE transitions to RRC_INACTIVE, the bearer configuration is changed, and therefore the amount of signaling between the MgNB and the SgNB increases.
[0252] Solutions to the aforementioned problems are disclosed below.
[0253] The UE transmits small data to the SgNB. It may also transmit small data to the MgNB. That is, the DC configuration may also be applied to small data transmission in RRC_INACTIVE. This makes it unnecessary to change the bearer between the MgNB and the SgNB, making it possible to reduce the amount of signaling on the interface between base stations.
[0254] The small data may be data of an SCG bearer, data of an SCG split bearer, data of an MCG split bearer, or MCG data. For example, by transmitting the small data of an MCG split bearer to an SgNB, even if the wireless channel condition between the UE and the MgNB deteriorates, the small data can be transmitted quickly.
[0255] The UE may determine the base station to which the small data is to be transmitted using information on the bearer through which the small data passes. For example, the small data using the MCG bearer or the MCG split bearer may be transmitted to the MgNB. The small data using the SCG bearer or the SCG split bearer may be transmitted to the SgNB. For example, since the continuity of the interface between the base stations is not required, it is possible to quickly notify the small data from the UE to the upper NW device.
[0256] In the above, the UE may determine the base station to which the data is to be transmitted using information on the measurement results of the downlink signal. For example, when the measurement results of the SgNB are better than those of the MgNB, the UE may transmit small data to the SgNB using an MCG split bearer or an SCG split bearer. The downlink signal may be, for example, a synchronization signal (SS). The information on the measurement results may be, for example, an RSRP or an RSRQ. This allows the UE to perform small data communication using a base station with good communication quality, thereby improving the reliability of communication.
[0257] In the above, the UE may determine the base station to which the small data is to be transmitted by combining information on the bearer through which the small data passes and information on the measurement results of the downlink signal. For example, the small data using the MCG bearer may be transmitted to the MgNB. The small data using the SCG bearer may be transmitted to the SgNB. The UE may determine the destination of the small data using the MCG split bearer or the SCG split bearer by using information on the measurement results of the downlink signal. This makes it possible to achieve both rapid small data notification and improved reliability.
[0258] When transmitting small data from the UE to the SgNB, the UE may transmit a random access preamble to the SgNB. The SgNB may transmit a random access response to the UE. The random access response may be transmitted after the random access preamble transmission from the UE to the SgNB.
[0259] The UE may request the SgNB to return to RRC_CONNECTED. The request may be made after the SgNB transmits a random access response to the UE.
[0260] The UE may include in the request an identifier used for returning to RRC_CONNECTED, for example, a resume ID. The UE may also include in the request information indicating the MgNB, for example, an identifier of the MgNB. This makes it possible to prevent malfunctions due to, for example, duplication of a resume ID number issued by the SgNB as a master base station for other UEs. As another example, the UE may include in the request an identifier of the UE. This, for example, can provide the same effect as described above.
[0261] The SgNB may query the MgNB regarding the identifier to be used for recovery. The query may include the identifier of the UE.
[0262] The MgNB may notify the SgNB of the identifier used for recovery. The notification may include information indicating the MgNB. Alternatively, the identifier of the UE may be included. The notification may be performed after the inquiry from the SgNB to the MgNB, or may be performed in advance. The notification performed in advance may be included in a UE connection stop notification transmitted from the MgNB to the SgNB, or may be notified as a separate signaling. The MgNB may notify the SgNB of the identifier used for recovery.
[0263] The SgNB may hold information on the identifier used for recovery. The SgNB may hold information on the identifier used for recovery in combination with information indicating the MgNB, or in combination with the identifier of the UE. This makes it possible to prevent malfunctions due to, for example, duplication of the resume ID number with a resume ID issued by the SgNB as a master base station for other UEs.
[0264] The UE may transmit small data to the SgNB. The transmission may be performed after the UE returns to RRC_CONNECTED to the SgNB. The small data may be data passing through an SCG bearer, data passing through an SCG split bearer, or a bearer passing through an MCG split bearer.
[0265] The SgNB may notify the UE of a response to the request to return to RRC_CONNECTED. The response may be an instruction for the UE to remain in the RRC_INAVTIVE state. The response may include an identifier used to return to RRC_CONNECTED, information indicating the MgNB, or an identifier of the UE.
[0266] The SgNB may not notify the UE of a response to the request to return to RRC_CONNECTED. The SgNB may notify the UE of a response to the small data instead of the response.
[0267] The identifier used for returning to RRC_CONNECTED, for example, a resume ID, may include information indicating the MgNB. For example, a part of the resume ID may be the same as the ID of the MgNB. This makes it easier for the MgNB and SgNB to control the return, since the identifier used for returning is unique between gNBs.
[0268] Fig. 21 is a sequence diagram showing an operation when a UE transmits small data to an SgNB. The sequence shown in Fig. 21 includes the same steps as the sequences shown in Fig. 8 and Fig. 9, so the same step numbers are used for the same steps and common explanations are omitted.
[0269] Steps ST801, ST803, ST805, and ST808 in FIG. 21 are the same as those in FIG. 8, and therefore the description thereof will be omitted.
[0270] In Step ST1401 shown in FIG. 21, the MgNB notifies the SgNB of UE connection suspension. The notification includes a resume ID and an ID of the MgNB. As another example, the resume ID including an ID of the MgNB as a part thereof may be included. The SgNB holds the resume ID and the ID of the MgNB.
[0271] In step ST1407 shown in Fig. 21, uplink transmission data is generated from the UE to the SgNB. In steps ST817 and ST818 shown in Fig. 21, the UE performs random access processing to the SgNB. Steps ST817 and ST818 in Fig. 21 are the same as those in Fig. 9.
[0272] In Step ST1410 in Fig. 21, the UE requests the SgNB to return to RRC_CONNECTED. The request may include a resume ID or an identifier of the MgNB.
[0273] In Step ST1416 in Fig. 21, the UE transmits small data to the SgNB. The small data may be data passing through an SCG bearer, may be data passing through an SCG split bearer, or may be a bearer passing through an MCG split bearer.
[0274] In Step ST1419 shown in Fig. 21, the SgNB notifies the UE of an instruction to maintain the RRC_INACTIVE state. The instruction may include a resume ID or an identifier of the MgNB.
[0275] The UE may transmit small data to both the MgNB and the SgNB. For example, the UE may transmit small data to the MgNB using an MCG bearer or an MCG split bearer. The UE may transmit small data to the SgNB using an SCG bearer or an SCG split bearer.
[0276] Fig. 22 is a sequence diagram showing an operation when a UE transmits small data to an MgNB and an SgNB. The sequence shown in Fig. 22 includes the same steps as the sequences shown in Fig. 8, Fig. 9, and Fig. 21, so the same step numbers are used for the same steps and common descriptions are omitted.
[0277] The sequence from steps ST801 to ST1407 in FIG. 22 is the same as that in FIG. 21, so the description will be omitted.
[0278] In steps ST810 and ST811 shown in Fig. 22, the UE performs random access processing to the MgNB. In steps ST817 and ST818, the UE performs random access processing to the SgNB. Steps ST810, ST811, ST817, and ST818 in Fig. 22 are the same as those in Fig. 9.
[0279] Step ST812 in Fig. 22 is the same as Fig. 9. In Step ST1513, the UE transmits small data to the MgNB. The small data may be data passing through an MCG bearer, data passing through an MCG split bearer, or a bearer passing through an SCG split bearer.
[0280] In Step ST1410 in FIG. 22, the UE requests the SgNB to return to RRC_CONNECTED. The request may include a resume ID or may include an identifier of the MgNB. The request may include both. The resume ID may include an identifier of the MgNB.
[0281] In Step ST1416 in Fig. 22, the UE transmits small data to the SgNB. The small data may be data passing through an SCG bearer, may be data passing through an SCG split bearer, or may be a bearer passing through an MCG split bearer.
[0282] In Step ST1518 shown in Fig. 22, the MgNB notifies the UE of an instruction to maintain the RRC_INACTIVE state. The instruction may include a resume ID.
[0283] In Step ST1419 shown in Fig. 22, the SgNB notifies the UE of an instruction to maintain the RRC_INACTIVE state. The instruction may include a resume ID or an identifier of the MgNB.
[0284] 21 and 22 show an example in which the UE maintains the RRC_INACTIVE state, but the UE may transition to RRC_CONNECTED. When the UE transitions to RRC_CONNECTED, the sequence shown in the first embodiment may be applied.
[0285] By using the second embodiment, it becomes possible to transmit small data to the SgNB. As a result, it becomes unnecessary to change the bearer when transitioning to RRC_INACTIVE, and it becomes possible to reduce the amount of signaling in the interface between base stations.
[0286] According to the second embodiment, for example, the following configuration is provided.
[0287] A communication system is provided that includes a communication terminal device and a plurality of base station devices configured to be able to wirelessly communicate with the communication terminal device. More specifically, the plurality of base station devices include a master base station device and a secondary base station device that configure a bearer for the communication terminal device. The communication terminal device in an RRC_INACTIVE state performs random access processing with the secondary base station device, requests the secondary base station device to return to an RRC_CONNECTED state after the random access processing, and transmits uplink data to the secondary base station device as small data that can be transmitted in the RRC_INACTIVE state before returning to the RRC_CONNECTED state.
[0288] In this configuration, a communication terminal device in the RRC_INACTIVE state may perform random access processing with the master base station device, request the master base station device to return to the RRC_CONNECTED state after the random access processing, and transmit uplink data as small data to the master base station device before returning to the RRC_CONNECTED state.
[0289] The above configuration can be modified in various ways based on the disclosures and suggestions of this specification, including embodiment 2. According to the above configuration and modified configurations, the above problems can be solved and the above effects can be obtained.
[0290] Variation 1 of embodiment 2 Packet duplication may be used as a communication method that requires low latency and high reliability. As a packet duplication method, a DC configuration or a CA configuration may be used.
[0291] When the above-mentioned method is applied to infrequent communication that requires low latency and high reliability, such as emergency communication for earthquakes and emergency control signals for autonomous driving, the following problem occurs. In infrequent communication, the UE transitions to the RRC_INACTIVE state. However, it is not clear how to perform packet duplication in the RRC_INACTIVE state. As a result, a problem occurs in that infrequent communication that requires low latency and high reliability cannot be realized.
[0292] Solutions to the aforementioned problems are disclosed below.
[0293] Packet duplication is applied for small data transmissions that a UE in RRC_INACTIVE state can perform.
[0294] The above-mentioned packet duplication of small data may use a DC configuration, which may be the same as that in the second embodiment.
[0295] The MgNB may set the UE and the SgNB to perform packet duplication. The above-mentioned setting may be included in the setting of the DC configuration, for example. This makes it possible to omit the setting of packet duplication during small data transmission, for example, and therefore to start small data transmission quickly.
[0296] In the above, the default on / off state of packet duplication may be set to “on.” This allows, for example, small data transmission to be started quickly.
[0297] The UE may perform random access processing to both the MgNB and the SgNB. The random access processing to be performed by the UE to the SgNB may be performed after waiting for a random access response from the MgNB, or may be performed prior to the random response access from the MgNB. A random access preamble may be transmitted from the UE to the SgNB prior to the random access preamble transmission from the UE to the MgNB. The random access processing may be performed when uplink transmission data is generated.
[0298] Figures 23 and 24 are sequence diagrams showing the operation when DC is used for packet duplication of small data. Figures 23 and 24 are connected at the position of the boundary line BL2324. Figures 23 and 24 perform packet duplication using MCG split bearer. The sequences shown in Figures 23 and 24 include the same steps as the sequences shown in Figures 8, 9, 21, and 22, so the same step numbers are used for the same steps and common explanations are omitted.
[0299] Steps ST801 to ST818 in FIG. 23 are the same as those in FIG. 22, and therefore the description thereof will be omitted.
[0300] In step ST1610 shown in FIG. 24, the UE performs packet duplication of uplink transmission data.
[0301] Steps ST812 to ST1410 in FIG. 24 are the same as those in FIG. 22, and therefore the description thereof will be omitted.
[0302] In step ST1416 shown in Fig. 24, the UE transmits, as small data, the packet that was not transmitted in step ST1513, of the packets duplicated in step ST1610, to the SgNB. In step ST1612, the SgNB transfers the uplink transmission data received from the UE in step ST1416 to the MgNB. In step ST1613, the MgNB detects duplication of the uplink transmission data and deletes all but one of the duplicated uplink transmission data.
[0303] Steps ST1518 and ST1419 shown in FIG. 24 are the same as those in FIG. 22, and therefore the description thereof will be omitted.
[0304] A CA configuration may be used in packet duplication of small data. The UE and the gNB may retain information about the connection between the terminal and the base station, such as a UE AS context. The UE AS context may be retained when the UE transitions to the RRC_INACTIVE state.
[0305] Similar to packet duplication using a DC configuration, the gNB may notify the eNB / gNB in the RAN area for paging of the UE AS context in advance, or the eNB / gNB may inquire about the UE AS context from other eNB / gNB in the RAN area for paging.
[0306] The base station may set the UE to perform packet duplication. The above-mentioned setting may be included in the CA configuration setting for the UE. For example, the above-mentioned setting may be included in the signaling of the RRC connection reconfiguration for the UE. This makes it possible to omit the setting of packet duplication during small data transmission, and thus to start small data transmission quickly.
[0307] In the above, the default on / off state of packet duplication may be set to “on.” This allows, for example, small data transmission to be started quickly.
[0308] The UE may perform random access processing on the PCell and SCell of the gNB. The random access processing performed by the UE on the SCell may be performed after waiting for a random access response from the PCell, or may be performed prior to the random response access from the PCell. A random access preamble may be transmitted from the UE to the SCell prior to the random access preamble transmission from the UE to the PCell. This makes it possible to quickly transmit data using the SCell. Alternatively, the random access processing may be performed at different timings. The random access processing may be performed when uplink transmission data is generated.
[0309] Fig. 25 is a sequence diagram showing an operation when CA is used for packet duplication of small data. In the example of Fig. 25, packet duplication is performed using PCell and SCell. Also, in the example of Fig. 25, the gNB transmits signaling to the UE using PCell. Since the sequence shown in Fig. 25 includes the same steps as the sequences shown in Figs. 8 and 9, and Fig. 21, the same step numbers are assigned to the same steps, and common explanations are omitted.
[0310] Step ST801 in FIG. 25 is the same as that in FIG. 8, and therefore the explanation will be omitted.
[0311] In Step ST1702 shown in Fig. 25, the gNB instructs the UE to transition to RRC_INACTIVE via the PCell. The instruction may be similar to Step ST805 in Fig. 8.
[0312] Steps ST808 and ST1407 in FIG. 25 are the same as those in FIG. 21, and therefore the description thereof will be omitted.
[0313] In Steps ST1705 and ST1706 shown in FIG. 25, the UE performs random access processing with the PCell, and in Steps ST1707 and ST1708, the UE performs random access processing with the SCell.
[0314] In Step ST1709 in Fig. 25, the UE requests the gNB to resume the RRC connection via the PCell. This request may be similar to Step ST812 in Fig. 9.
[0315] In step ST1610 shown in FIG. 25, the UE performs packet duplication of the uplink transmission data. In step ST1711, the UE transmits one of the duplicated uplink transmission data as small data to the gNB via the PCell. In step ST1712, the UE transmits the other of the duplicated uplink transmission data as small data to the gNB via the SCell. In step ST1713, the gNB detects duplication of the uplink transmission data and deletes all but one of the duplicated uplink transmission data.
[0316] In Step ST1714 shown in Fig. 25, the MgNB notifies the UE of an instruction to maintain the RRC_INACTIVE state. Step ST1714 may be an instruction to transition to the RRC_CONNECTED state.
[0317] According to this modification 1, it is possible to realize communication that is infrequent, has low latency, and is highly reliable.
[0318] Embodiment 3 A transmission power control different from that for ground terminals is applied to UEs mounted on unmanned aerial vehicles. For example, a limit may be placed on the maximum transmission power for UAV-UEs. As another example, the transmission power may be different between a target SIR (Target-SIR) ground terminal and UAV-UE. This makes it possible to reduce uplink interference from UAV-UEs to a base station.
[0319] When the above-mentioned method is applied, the following problem occurs: Since the above-mentioned transmission power control reduces the transmission power to the serving cell, the reception quality of the signal transmitted from the UAV-UE to the serving cell deteriorates.
[0320] Solutions to the aforementioned problems are disclosed below.
[0321] Repetition is applied to upstream transmission.
[0322] The repetition may be performed when the above-mentioned transmission power reduction method is applied, which makes it possible to, for example, ensure the reliability of uplink transmission while suppressing uplink interference power.
[0323] As an example of the case where the transmission power reduction method is applied, the difference may be between a UAV-UE and a normal UE. For example, the transmission power reduction method may be applied to a UAV-UE.
[0324] As another example, the difference may be between a UE in a ground mode and a UE in an aerial mode. For example, a transmission power reduction method may be applied to a UE in an aerial mode. The UE may be a UAV-UE or a normal UE.
[0325] As another example, whether to apply the transmission power reduction method may be determined using information on the altitude of the UE. For example, when the altitude of the UE is high, the transmission power reduction method may be applied. The UE may be a UAV-UE or a normal UE.
[0326] As another example, the information of the reception interference level at the base station may be used to determine whether to apply the transmission power reduction method. For example, in communication with a base station with a high reception interference level, the transmission power reduction method of the UE may be applied. The UE may be a UAV-UE or a normal UE.
[0327] In the uplink transmission, the following (1) to (5) are disclosed as examples of channels and / or signals to which repetition is applied.
[0328] (1) PUSCH.
[0329] (2) PUCCH.
[0330] (3) PRACH.
[0331] (4) RS.
[0332] (5) A combination of (1) to (4) above.
[0333] The RS in (4) above may be a DMRS, an SRS, or both. The repetition of the SRS may be a shortened SRS transmission cycle, or a new symbol may be provided for the repetition transmission.
[0334] The UAV-UE may transmit to the base station by hopping the frequency for each repetition. The UAV-UE may change the RB of the uplink transmission signal for each repetition number.
[0335] Regarding the above-mentioned frequency hopping, the UAV-UE may transmit to the base station by hopping the frequency for each repetition. The hopping pattern may be given for each cell. For example, the hopping pattern may be given using a cell ID, for example, PCI.
[0336] As an example of the frequency hopping described above, an offset may be provided to the RB transmitted by the UAV-UE for each repetition. The offset may be provided for each cell. For example, the offset may be determined using a cell ID, for example, a PCI.
[0337] Fig. 26 is a pattern diagram showing an example of giving a different frequency hopping pattern to a UAV-UE for each cell. Fig. 26 shows an example of PUSCH. Fig. 26 also shows an example in which the number of repetitions of uplink transmission from the UAV-UE is set to three.
[0338] An example using Cell#1 in Fig. 26 will be described. In the first transmission of PUSCH, the UAV-UE transmits to the base station using RB1801. In the first retransmission, the UAV-UE transmits to the base station using RB1802, which is one RB higher in the frequency direction than the first transmission. Similarly, for the second and third retransmissions, the UAV-UE transmits to the base station using RB1803 and RB1804, which are one RB higher in the frequency direction than the first and second retransmissions, respectively.
[0339] An example using Cell#2 in Fig. 26 will be described. In the first transmission of PUSCH, the UAV-UE transmits to the base station using RB1811. In the first retransmission, the UAV-UE transmits to the base station using RB1812, which is 2 RBs higher in the frequency direction than the first transmission. Similarly, for the second and third retransmissions, the UAV-UE transmits to the base station using RB1813 and RB1814, which are 2 RBs higher in the frequency direction than the first and second retransmissions, respectively.
[0340] 26 shows an example in which the frequency domain used for each uplink transmission is one RB, but multiple RBs may be used. The multiple RBs may be continuous in the frequency direction, or may be discontinuous, for example, discrete frequency domains.
[0341] In FIG. 26, an example is shown in which the frequency domain used for each uplink transmission is given using an offset in the frequency direction, but it may be given using the accumulation of the offset in the frequency direction and the remainder of the entire frequency domain available to the UAV-UE. For example, in the example of FIG. 26, when the frequency domain allocated to the PUSCH used by the UAV-UE is 10 RBs and the frequency offset for each transmission is 7 RBs, the first transmission may be transmitted using the lowest RB in the frequency direction, the first retransmission may be transmitted using the eighth RB from the bottom, the second retransmission may be transmitted using the fifth RB from the bottom, and the third retransmission may be transmitted using the second RB from the bottom. This makes it possible to increase the number of frequency hopping patterns, for example, and therefore to increase the number of UAV-UEs that can be accommodated.
[0342] As another example of providing the hopping pattern, it may be for each UAV-UE. This makes it possible to distribute the frequency pattern between other UAV-UEs, for example. As a result, it becomes possible to reduce the uplink interference power in the base station, for example.
[0343] The base station may notify the UE of the frequency hopping pattern. For example, L1 / L2 signaling may be used for the notification. This allows, for example, rapid frequency resource allocation by the base station. As another example, MAC signaling may be used. This allows, for example, highly reliable notification by HARQ retransmission. As another example, RRC signaling may be used. This allows, for example, a lot of information to be notified.
[0344] Regarding the notification, the base station may notify the hopping pattern every time repetition occurs. This allows flexible scheduling in the base station. Alternatively, the frequency hopping patterns of the initial transmission and the repetition may be notified together. This makes it possible to avoid the complexity of processing in the UE.
[0345] The base station may inform the UEs of the frequency hopping pattern, which may, for example, reduce the amount of signaling.
[0346] As another example, the hopping pattern may be provided in advance by a standard. For example, the hopping pattern may be determined using an identifier of the UE. This allows, for example, a reduction in the amount of signaling between the base station and the UAV-UE.
[0347] In the third embodiment, the uplink communication has been disclosed, but the present invention may be applied to the downlink communication. This makes it possible to reduce the downlink interference power from the base station to the UAV-UE, for example. In addition, it is possible to ensure the reliability of the downlink communication.
[0348] The downlink communication may be, for example, a PDSCH. The base station may perform repetition of the PDSCH for the UAV-UE. Frequency hopping may also be performed.
[0349] As another example, the downlink communication may be a PDCCH. The base station may repeat DCI included in the PDCCH to the UAV-UE.
[0350] As another example, the downlink communication may be E-PDCCH. The base station may repeat the E-PDCCH to the UAV-UE. Frequency hopping may be performed.
[0351] In the third embodiment, the UAV-UE is described, but the method may be applied to a normal UE. For example, the method shown in the third embodiment may be applied to a normal UE by using information indicating that the altitude of the UE is high. This makes it possible to reduce interference power and ensure reception quality similar to that of a UAV-UE, even when a normal UE is mounted on a UAV and flies.
[0352] According to the third embodiment, it is possible to increase the received signal power at the base station and / or UAV-UE by repetition. In addition, it is possible to reduce the uplink and / or downlink interference power by distributing frequency resources with other UAV-UE by frequency hopping. This makes it possible to improve the reception quality in the communication between the base station and the UAV-UE.
[0353] According to the third embodiment, for example, the following configuration is provided.
[0354] A communication system is provided that includes a communication terminal device and a plurality of base station devices configured to be capable of wireless communication with the communication terminal device. More specifically, when the altitude difference between the location of the communication terminal device and the location of the base station device is equal to or greater than a threshold, at least one of the communication terminal device and the base station device performs repetition control to repeatedly transmit a transmission target. Note that in this configuration, the repetition control may include control to hop the transmission frequency of the transmission target.
[0355] The above configuration can be modified in various ways based on the disclosures and suggestions of this specification, including embodiment 3. According to the above configuration and modified configurations, the above problems can be solved and the above effects can be obtained.
[0356] Variation 1 of embodiment 3 Another method for reducing uplink interference from a UAV-UE is disclosed.
[0357] A limit is set to the number of UEs multiplexed in the PUCCH, which may be the number of UEs multiplexed in one RB of the PUCCH.
[0358] For example, the UE multiplexing number of PUCCHs may be different between normal UEs and UAV-UEs. For example, the UE multiplexing number of PUCCHs in UAV-UEs may be smaller than the PUCCH multiplexing number in normal UEs.
[0359] As another example, the UE multiplexing number of PUCCH may be different between a UE in ground mode and a UE in flight mode. For example, the UE multiplexing number of PUCCH in flight mode UE may be smaller than the PUCCH multiplexing number in ground mode UE. The UE may be a UAV-UE or a normal UE.
[0360] As another example, the UE multiplexing number of PUCCHs may be different using information on the altitude of the UE. For example, the UE multiplexing number of PUCCHs in a UE with a high altitude may be smaller than the PUCCH multiplexing number in a UE with a low altitude. The UE may be a UAV-UE or a normal UE.
[0361] As another example, the UE multiplexing number of PUCCH may be changed using information on the reception interference level at the base station. For example, the UE multiplexing number of PUCCH may be decreased in communication with a base station with a high reception interference level, and the UE multiplexing number of PUCCH may be increased in communication with a base station with a low reception interference level. The UE may be a UAV-UE or a normal UE. This makes it possible to ensure a certain level of communication quality between the base station and the UE, for example.
[0362] The above-mentioned UE multiplexing number may be determined in advance by a standard. For example, a parameter indicating the UE multiplexing number of the PUCCH in the UAV-UE may be newly provided. As another example, a parameter indicating the UE multiplexing number of the PUCCH in the flight mode may be newly provided. This makes it easier to control the UE multiplexing number in the base station, for example.
[0363] As another example, the above-mentioned multiplexing number of UEs may be determined by an upper NW device. The upper NW device may be, for example, an MME or an AMF. The upper NW device may notify the base station of the above-mentioned multiplexing number of UEs. This makes it possible to flexibly control interference power according to the number of UEs accommodated, for example.
[0364] As another example, the base station may determine the number of UEs multiplexed as described above. The base station may determine the number of beams, for example. This allows for flexible control according to the number of beams, for example.
[0365] In this first modification, the multiplexing number with a limit may be prioritized over the multiplexing number without a limit. For example, the base station may use the multiplexing number with a limit when UAV-UE and normal UE are mixed among the connected UEs. This makes it possible to suppress interference power at the base station even when UAV-UE and normal UE are mixed.
[0366] As another example, the unlimited multiplexing number may be prioritized over the limited multiplexing number. For example, the base station may use the unlimited multiplexing number when UAV-UE and normal UE are mixed among the connected UEs. This allows the base station to accommodate many UEs.
[0367] According to this first modification, the number of UEs multiplexed per 1 RB of PUCCH can be reduced, making it possible to reduce uplink interference.
[0368] Embodiment 4 The selection of the serving cell in the UAV-UE is performed using the RSRP. For example, in cell selection and / or cell reselection, the UAV-UE selects the cell with the highest RSRP. Alternatively, the UAV-UE reports the measurement result of the RSRP to the serving cell. The serving cell uses the measurement result to determine the handover destination.
[0369] When the above-mentioned method is applied, the following problem occurs: Since the transmission power of the RS differs for each cell, when the serving cell is determined based on the measurement result of the downlink RSRP, the uplink transmission power for the serving cell is not necessarily low.
[0370] A method for solving the above problems is disclosed below: Path loss is used to select a serving cell: The UAV-UE measures the path loss of cells.
[0371] The path loss may be used for cell selection and / or cell reselection, for example, a path loss criterion may be used as a threshold for cell selection and / or cell reselection.
[0372] The UAV-UE may switch between the path loss condition and the RSRP condition. For example, the UAV-UE may use the path loss condition when using a transmission power control different from that on the ground, as described in the third embodiment. Also, when using the same transmission power as on the ground, the UE may use the RSRP condition. This makes it possible to avoid design complexity in the UAV-UE.
[0373] The threshold value may be determined in advance by a standard, or may be notified to the UE by the base station.
[0374] As another example, the threshold may be notified individually from the base station to the UE. The individual notification from the base station to the UE may be performed when the UE is in the RRC_CONNECTED state. The UE may use the threshold included in the notification when transitioning from the RRC_CONNECTED state to the RRC_IDLE state or the RRC_INACTIVE state. Flexible cell reselection control for each UE is possible.
[0375] A combination of path loss and RSRP may be used for cell selection and / or cell reselection. For example, a path loss condition may be used as a threshold for cell selection and / or cell reselection, or a RSRP condition may be used, or a combination of path loss and RSRP conditions may be used. As another example, a path loss threshold and an RSRP threshold may be used. For example, the RSRP threshold may be used as a minimum required value for RSRP. The RSRP threshold may be applied to the UAV-UE. This makes it possible to reduce uplink interference while ensuring a minimum received power in the UAV-UE.
[0376] As a method of cell selection and / or reselection determination in the UAV-UE, for example, the UAV-UE may select a cell with a small path loss. The cell may be the cell with the smallest path loss. This allows, for example, a reduction in the transmission power from the UAV-UE to reduce interference in the cell.
[0377] As another example of the determination method, a threshold may be set for the path loss. The UAV-UE may select a cell whose path loss is smaller than the threshold. The cell may be, for example, a cell that is detected first among the cells whose path loss is smaller than the threshold. This allows, for example, the UAV-UE to quickly select a cell whose transmission power can be kept below a certain level.
[0378] As another example of the determination method, both the path loss and the RSRP may be used. For example, the threshold of the RSRP may be used. The UAV-UE may select, for example, a cell with a small path loss among cells with a RSRP threshold or more. The cell may be, for example, a cell with the smallest path loss. This makes it possible to reduce interference in a cell by reducing the transmission power from the UAV-UE while maintaining a certain level of downlink reception power in the UAV-UE.
[0379] As another example of the determination method using both the path loss and the RSRP, a path loss threshold may be used. The UAV-UE may select, for example, a cell with a large RSRP among cells with a path loss threshold or less. The cell may be, for example, a cell with the largest RSRP. This makes it possible to ensure downlink reception power in the UAV-UE while reducing interference in the cell to a certain level or more.
[0380] As another method to solve the above problem, path loss may be used for handover.
[0381] The UAV-UE may measure the path loss. The UAV-UE may include information on the measured path loss in signaling of a measurement report to the base station. Alternatively, a measurement report for notifying the measurement result of the path loss may be newly provided.
[0382] In the measurement report, a new event trigger using path loss may be provided, which enables the UAV-UE to quickly notify the serving cell of the measurement result of a cell that satisfies a certain condition regarding path loss.
[0383] A parameter used for the above-mentioned event trigger may be newly provided. The parameter may be, for example, a path loss threshold or a difference in path loss between a serving cell and a neighboring cell. The parameter may be notified from the base station to the UE, or may be notified individually to each UE. Alternatively, the parameter may be notified individually to the UAV-UE.
[0384] The above-mentioned event trigger may include a path loss condition. For example, a path loss condition may be newly added to an existing event trigger. For example, an event trigger using RSRP, RSRQ, and path loss may be provided. This makes it possible to reduce interference with cells and ensure reception power and reception quality in the UAV-UE.
[0385] The UAV-UE may switch between an event trigger including a path loss condition and an event trigger including a conventional RSRP condition. For example, the UAV-UE may use an event trigger including a path loss condition when using a transmission power control different from that on the ground, as described in the third embodiment. Also, when using the same transmission power as on the ground, the UAV-UE may use an event trigger including an RSRP condition. This makes it possible to avoid design complexity in the UAV-UE.
[0386] For handover using path loss, the cell may derive the path loss. The UAV-UE may notify the serving cell of the RSRP from the serving cell and / or the neighboring cell. The serving cell and the neighboring cell may notify each other of the RS transmission power of the own cell. The serving cell may derive the path loss using the RSRP notified from the UE and the RS transmission power notified between the cells. This makes it possible to reduce the amount of processing in the UE.
[0387] The serving cell may use the path loss to determine the handover destination of the UAV-UE. As a method of determination, for example, the serving cell may determine a cell with a small path loss. This makes it possible to reduce uplink interference from the UAV-UE.
[0388] The serving cell may switch the method of determining the handover destination of the UAV-UE. For example, when the UAV-UE uses a transmission power control different from that on the ground, as described in the third embodiment, the serving cell may use a path loss to determine the handover destination of the UAV-UE. Also, when the UAV-UE uses the same transmission power as that on the ground, the serving cell may use RSRP to determine the handover destination of the UAV-UE. This makes it possible to avoid, for example, the complexity of the design in the communication system.
[0389] As another example, a cell with a path loss of a certain threshold or less may be determined. The cell may be, for example, the cell that the serving cell first detects among the cells with a path loss of the certain threshold or less. It becomes possible to quickly detect a cell that reduces uplink interference from the UAV-UE by a certain amount or more.
[0390] As another example, a cell with a small path loss may be selected from among cells with an RSRP equal to or greater than a certain threshold. This makes it possible to reduce uplink interference from the UAV-UE while ensuring a certain received power at the UAV-UE.
[0391] As another example, a cell with a large RSRP may be selected from among cells with a certain path loss or less. This makes it possible to ensure the reception power at the UAV-UE while reducing uplink interference from the UAV-UE to a certain level or more.
[0392] In the fourth embodiment, the UAV-UE is described, but the method may be applied to a normal UE. For example, the method shown in the fourth embodiment may be applied to a normal UE by using information indicating that the altitude of the UE is high. This makes it possible to reduce interference power and ensure reception quality similar to that of a UAV-UE, even when a normal UE is mounted on a UAV and flies.
[0393] In the fourth embodiment, the case where the path loss is used has been described, but the transmission power of the cell may be used. For example, a cell whose transmission power is equal to or less than a certain threshold may be the cell selection / reselection destination and / or the handover destination. This makes it possible to reduce downlink interference power from the cell to other UEs, for example.
[0394] According to the fourth embodiment, it becomes possible to detect a cell capable of transmitting with low uplink transmission power. By using the path loss for cell selection and / or cell reselection, it becomes possible to select a cell capable of transmitting with low transmission power from the UAV-UE. In addition, by using the path loss for handover, the serving cell becomes capable of handing over to a cell capable of transmitting with low transmission power by the UAV-UE. As a result, it becomes possible to reduce the uplink interference power in the UAV-UE.
[0395] According to the fourth embodiment, for example, the following configuration is provided.
[0396] A communication system is provided that includes a communication terminal device and a plurality of base station devices configured to be able to wirelessly communicate with the communication terminal device. More specifically, when an altitude difference between a position of the communication terminal device and a position of the base station device is equal to or greater than a threshold, at least one of cell selection, cell reselection, and handover destination cell determination is performed using path loss information.
[0397] The above configuration can be modified in various ways based on the disclosures and suggestions of this specification, including embodiment 4. According to the above configuration and modified configurations, the above problems can be solved and the above effects can be obtained.
[0398] Variation 1 of embodiment 4 In the above-mentioned fourth embodiment, for example, by performing handover to a cell with less path loss, the following problem occurs. That is, the possibility of handover failure increases as the UAV-UE repeats handover. The handover failure makes it impossible to control the UAV-UE, and for example, causes a problem that the UAV-UE falls during flight.
[0399] In this first modification, a method for solving the above-mentioned problem will be disclosed.
[0400] As a method of determining a cell selection / cell reselection destination in the fourth embodiment, for example, the UAV-UE may select a cell with a large path loss. The cell may be the cell with the largest path loss. This allows the UAV-UE to select a cell with a wide range, for example.
[0401] As another example of the determination method, a threshold may be set for the path loss. The UAV-UE may select a cell having a path loss greater than the threshold. The cell may be, for example, a cell that is detected first among the cells having a path loss greater than the threshold. This allows the UAV-UE to quickly select cells within a certain range or more.
[0402] As another example of the determination method, both the path loss and the RSRP may be used. For example, the threshold of the RSRP may be used. The UAV-UE may select, for example, a cell with a large path loss among cells with an RSRP threshold or more. The cell may be, for example, a cell with the largest path loss. This makes it possible to select a wide range of cells that can ensure a certain level of downlink reception power in the UAV-UE.
[0403] As another example of the determination method using both the path loss and the RSRP, a path loss threshold may be used. The UAV-UE may select, for example, a cell with a large RSRP among cells with a path loss threshold or more. The cell may be, for example, a cell with the largest RSRP. This makes it possible to select cells within a certain range or more and to ensure downlink reception power in the UAV-UE.
[0404] Another solution will be disclosed. As a handover destination selection method in the fourth embodiment, for example, the serving cell may determine a cell with a large path loss. This makes it possible to detect cells with a wide cell range.
[0405] As another example, a cell with a path loss of a certain threshold or more may be determined. The cell may be, for example, a cell that is first detected by the serving cell among the cells with a path loss of the certain threshold or more. This makes it possible to quickly detect cells within a certain range or more.
[0406] As another example, a cell with a large path loss may be selected from among cells with an RSRP equal to or greater than a certain threshold. This makes it possible to detect cells with a wide cell range while ensuring a certain reception power at the UAV-UE.
[0407] As another example, a cell with a large RSRP may be selected from among cells with a certain path loss or more. This makes it possible to detect cells within a certain range and ensure reception power in the UAV-UE.
[0408] Another solution is disclosed. The cells accessed by the UAV-UE are differentiated between the C-Plane and the U-Plane. A DC configuration may also be used. This makes it possible to improve the reliability of communication, for example.
[0409] In the above, the method of selecting the cell for C-Plane and the cell for U-Plane may be changed. For example, the method disclosed in the present modified example 1 may be used for selecting the cell for C-Plane. The method disclosed in the fourth embodiment may be used for selecting the cell for U-Plane. This makes it possible to reduce the uplink interference power in the base station while ensuring the robustness of the communication between the UAV-UE and the base station.
[0410] Although the present modified example 1 has been described with respect to a UAV-UE, it may be applied to a normal UE. For example, the method described in the present modified example 1 may be applied to a normal UE by using information indicating that the altitude of the UE is high. This allows a wide cell to be selected, for example, even when a normal UE is mounted on a UAV and flies, as in the case of a UAV-UE.
[0411] In this first modification, the transmission power of a cell may be used as in the fourth embodiment. For example, a cell whose transmission power is equal to or greater than a certain threshold may be the cell selection / reselection destination and / or handover destination. This makes it possible to select a cell with a wide cell range, for example, and to reduce the number of handovers. As a result, it becomes possible to reduce the possibility of handover failure.
[0412] The method shown in this modified example 1 allows the UAV-UE to use a cell with a large path loss and thus a cell with a wide cell range. By using a cell with a wide cell range, the number of handovers can be reduced, and as a result, the possibility of handover failure can be reduced. In addition, by applying this modified example 1 to cell selection / cell reselection, it is possible to reduce the transition of the UAV-UE out of range.
[0413] Embodiment 5. The following problem occurs in communication between the UAV-UE and the base station: Since the radio wave propagation environment differs depending on the altitude at which the UAV-UE communicates with the base station, the uplink interference to the base station differs depending on the altitude, and the methods described in the third embodiment, the first modification of the third embodiment, the fourth embodiment, and the first modification of the fourth embodiment may not be effective.
[0414] In the fifth embodiment, a method for solving the above-mentioned problems will be presented.
[0415] A new communication mode is provided in the UAV-UE. The communication mode may be, for example, a communication mode for the UAV-UE in flight (hereinafter, the communication mode may be referred to as a flight mode). In the flight mode, the UAV-UE may perform communication using parameter settings different from those in a conventional communication mode, for example, a normal mode. The parameters in the flight mode may be, for example, the parameters shown in the third embodiment, the first modified example of the third embodiment, the fourth embodiment, and the first modified example of the fourth embodiment. The base station may notify the UAV-UE of the parameters in the flight mode. The parameters in the normal mode may be included. As an example of the notification, system information may be used.
[0416] Alternatively, the base station may notify the UAV-UE of parameters in the flight mode. Parameters in the normal mode may also be included. The base station may notify the UAV-UE in advance. For example, RRC dedicated signaling may be used as the notification. This makes it possible to reduce the amount of signaling from the base station to the UE, for example.
[0417] The base station may transmit the notification to the UAV-UE multiple times. For example, every time the communication mode is switched, the base station may transmit the parameters in the switched communication mode to the UAV-UE. For example, RRC individual signaling may be used as the notification. In the same mode, the parameters to be set may be variable. This makes it possible to increase the flexibility of operation according to the radio wave environment of the base station at the time of mode switching, even in the same flight mode.
[0418] As another example, when the UAV-UE is communicating in flight mode and a change occurs in the parameters of the flight mode, the base station may notify the UAV-UE of the parameters for the changed flight mode. The same may be done in normal mode. This allows, for example, the base station to flexibly change the parameters, thereby increasing the flexibility of the communication system.
[0419] The UAV-UE may perform communication by switching between a normal mode and a flight mode, which enables appropriate transmission power control during takeoff and landing and during flight, for example.
[0420] The switching may be determined by the UAV-UE. The UAV-UE may determine the switching and apply it to the UAV-UE. The UAV-UE may notify the base station of the switching. For example, the amount of processing in the base station may be reduced.
[0421] The notification may be made using RRC signaling. Since it is possible to send a lot of data, it is possible to include, for example, information on the measurement results used for the switching. This makes it easier, for example, for the base station to appropriately control the UAV-UE.
[0422] As another example of the notification, MAC signaling may be used. HARQ retransmissions can ensure high reliability and enable fast notification.
[0423] As another example of the notification, L1 / L2 signaling may be used, which allows for even faster notification.
[0424] The UAV-UE may determine the switching by using RSRP. The UAV-UE may determine the switching by using path loss. The UAV-UE may determine the switching by combining both. In the determination, thresholds of RSRP and / or path loss may be set. For example, the UAV-UE may determine the transition from the normal mode to the flight mode by detecting a predetermined number or more of cells that satisfy the conditions using the thresholds of RSRP and path loss. This allows the UAV-UE to switch between the normal mode and the flight mode without using positioning information. This makes it possible to avoid complexity in the design of the UAV-UE.
[0425] The thresholds of RSRP and / or path loss in this judgment may be predefined in a standard, may be notified from the base station to the UAV-UE, or may be notified from the base station to the UAV-UE individually. The same may be true for the above-mentioned predetermined number.
[0426] FIG. 27 is a sequence diagram showing the operation of the UAV-UE to determine the communication mode. FIG. 27 shows an example in which the parameters in the normal mode and the flight mode are notified in advance from the base station to the UAV-UE. In the example of FIG. 27, the UAV-UE switches from the normal mode to the flight mode, and then switches back to the normal mode. In the example of FIG. 27, the UAV-UE notifies the base station of the switching of the communication mode by using L1 / L2 signaling.
[0427] 27, the base station notifies the UAV-UE of RRC parameters. The RRC parameters include parameters in the normal mode and the flight mode.
[0428] In Step ST1902 shown in Fig. 27, the UAV-UE measures a downlink signal. The measurement target may be RSRP, may be path loss, or may be a combination of both.
[0429] In step ST1903 shown in Fig. 27, the UAV-UE determines that the flight mode transition condition is satisfied using the measurement result in step ST1902. The UAV-UE transitions to the flight mode. The UAV-UE performs uplink transmission using the flight mode parameters acquired in step ST1901. In step ST1904, the UAV-UE notifies the base station of the transition to the flight mode by using L1 / L2 signaling.
[0430] In Step ST1905 shown in Fig. 27, the UAV-UE measures a downlink signal. The measurement target may be the same as that in Step ST1902.
[0431] In step ST1906 shown in FIG. 27, the UAV-UE determines that the normal mode transition condition is satisfied using the measurement result in step ST1905. The UAV-UE transitions to the normal mode. The UAV-UE performs uplink transmission using the normal mode parameters acquired in step ST1901. In step ST1907, the UAV-UE notifies the base station of the transition to the normal mode by using L1 / L2 signaling.
[0432] In FIG. 27, an example is shown in which the parameters in the normal mode and the flight mode are notified to the UAV-UE from the base station in advance, but the parameters may be notified from the base station to the UAV-UE multiple times. For example, in step ST1901, the parameters notified from the base station to the UAV-UE may be parameters for the normal mode. Also, after step ST1904, the base station may notify the UAV-UE of parameters for the flight mode. Similarly, after step ST1907, the base station may notify the UAV-UE of parameters for the normal mode. This makes it possible to reduce the amount of signaling between the base station and the UAV-UE, for example, in a UAV-UE that rarely switches between the normal mode and the flight mode. As another example, when a change occurs in parameters in the flight mode while the UAV-UE is communicating in the flight mode as shown in step ST1903, the base station may notify the UAV-UE of parameters for the flight mode after the change. The same may be done in the normal mode shown in step ST1906. This allows, for example, the base station to flexibly change parameters, thereby improving the flexibility of the communication system.
[0433] As another example of the switching, the base station may determine the switching, and the base station may instruct the UAV-UE to switch. This makes it easier for the base station to control the UAV-UE, for example.
[0434] The indication may be carried by RRC signaling, for example, the indication may be included in other RRC signaling, which may reduce the amount of signaling.
[0435] Another example of the indication may be MAC signaling, where HARQ retransmissions provide high reliability and fast notification.
[0436] As another example, the indication may be via L1 / L2 signaling, allowing for more immediate notification.
[0437] The base station may determine the switching using RSRP, may determine the switching using path loss, or may determine the switching using a combination of both. The determination in the base station may be the same as the determination in the UAV-UE described above.
[0438] The base station may determine the switching using a cell, a beam, or a combination of the two. The cell and / or beam may be, for example, a cell and / or beam that requires interference reduction using a flight mode. The base station may notify the UAV-UE of information on the cell and / or beam. The information may be an identifier of the cell and / or beam. The UAV-UE may perform the switching using the information on the cell and / or beam. For example, the UAV-UE may switch from the normal mode to the flight mode when communicating with the base station using the cell and / or beam. This enables efficient operation of the communication system, for example, by reducing interference for a cell and / or beam that requires interference reduction and ensuring transmission and reception quality for other cells and / or beams.
[0439] The communication mode and the switching of the communication mode disclosed in the fifth embodiment may be applied to a normal UE. For example, the communication mode and the switching may be applied to a normal UE located at a high place. The switching conditions applied to the normal UE may be the same as or different from the conditions applied to the UAV-UE. This makes it possible to control interference to a base station caused by uplink transmission power from a normal UE located at a high place such as the rooftop of a building.
[0440] The fifth embodiment may be applied to the third embodiment, the first modification of the third embodiment, the fourth embodiment, and the first modification of the fourth embodiment. That is, the UAV-UE in the third embodiment, the first modification of the third embodiment, the fourth embodiment, and the first modification of the fourth embodiment may be a UE in a flight mode. The UE in the flight mode may be a UAV-UE or a normal UE. This makes it possible to appropriately control the transmission power of, for example, a flying UAV-UE and / or a UE at a high altitude.
[0441] According to the fifth embodiment, appropriate power control according to the flight altitude of the UE becomes possible.
[0442] According to the fifth embodiment, for example, the following configuration is provided.
[0443] A communication system is provided that includes a communication terminal device and a plurality of base station devices configured to be able to wirelessly communicate with the communication terminal device. More specifically, the communication terminal device and the base station device communicate with each other by switching among a plurality of communication modes according to an altitude difference between the position of the communication terminal device and the position of the base station device.
[0444] The above configuration can be modified in various ways based on the disclosures and suggestions of this specification, including embodiment 5. According to the above configuration and modified configurations, the above problems can be solved and the above effects can be obtained.
[0445] The above-described embodiments and their modifications are merely examples of the present invention, and the embodiments and their modifications can be freely combined within the scope of the present invention. In addition, any component of the embodiments and their modifications can be appropriately modified or omitted.
[0446] For example, in each of the above-mentioned embodiments and their modifications, a subframe is an example of a time unit of communication in a fifth generation base station communication system. It may be a scheduling unit. In each of the above-mentioned embodiments and their modifications, the processing described as a subframe unit may be performed in a TTI unit, a slot unit, a subslot unit, or a minislot unit.
[0447] Although the present invention has been described in detail, the above description is illustrative in all respects and does not limit the present invention. It is understood that countless variations not illustrated can be assumed without departing from the scope of the present invention. [Explanation of symbols]
[0448] 200 communication system, 202 communication terminal equipment, 203,800 base station equipment.
Claims
1. A terminal device; a plurality of base stations each of which wirelessly communicates with the terminal device; The plurality of base stations are a communication system including an MgNB and an SgNB that configure dual connectivity with the terminal device, The terminal device performs small data transmission to the SgNB in the RRC_INACTIVE state. Communication systems.
2. Applying packet duplication to the small data transmission by the terminal device The communication system according to claim 1 .
3. A terminal device; a plurality of base stations each of which wirelessly communicates with the terminal device; The plurality of base stations are terminal devices in a communication system including an MgNB and an SgNB that configure dual connectivity with the terminal device, Perform small data transmission to the SgNB in RRC_INACTIVE state Terminal device.
4. A terminal device; a plurality of base stations each of which wirelessly communicates with the terminal device; The plurality of base stations are SgNBs in a communication system including an MgNB and an SgNB that configure dual connectivity with the terminal device, Receive small data transmitted from the terminal device in the RRC_INACTIVE state SgNB.
