Communication system, communication terminal device and communication node

Abstract

A communication system with low latency and high reliability is provided in NR (New Radio). The communication system includes: a communication terminal device; and a communication device capable of wirelessly communicating with the communication terminal device and capable of configuring multiple nodes for the communication terminal device, the communication terminal device performing uplink transmission to an uplink transmission node among the multiple nodes (ST809), the uplink transmission node being determined by uplink transmission node determination processing that determines a node capable of performing uplink transmission from the communication terminal device with lower latency among the multiple nodes as the uplink transmission node (ST804).

Description

[0001] This invention application is a divisional application of the invention patent application with international application number PCT / JP2018 / 040845, international application date November 2, 2018, and Chinese national phase application number 201880072358.1, entitled "Communication System, Communication Terminal Device and Communication Node". Technical Field

[0002] The present invention relates to a communication system for wireless communication between a communication terminal device such as a mobile terminal device and a base station device. Background Technology

[0003] Within the 3GPP (3rd Generation Partnership Project), the standardization organization for mobile communication systems, a communication method known as Long Term Evolution (LTE) in terms of the radio domain and System Architecture Evolution (SAE) in terms of the overall system architecture including the core network and radio access network (hereinafter collectively referred to as the network) has been studied (e.g., Non-Patent Documents 1-5). This communication method is also referred to as a 3.9G (3.9 Generation) system.

[0004] As an access method for LTE, the downlink direction uses OFDM (Orthogonal Frequency Division Multiplexing), and the uplink direction uses SC-FDMA (Single Carrier Frequency Division Multiple Access). Furthermore, unlike W-CDMA (Wideband Code Division Multiple Access), LTE does not include line switching; it is solely a packet communication method.

[0005] use Figure 1 To explain the decisions made in 3GPP concerning the frame structure of the LTE system as described in Non-Patent Document 1 (Chapter 5). Figure 1 This is an explanatory diagram showing the structure of the radio frame used in an LTE communication system. Figure 1In this system, a radio frame is 10ms long. A radio frame is divided into 10 equal-sized subframes. Each subframe is further divided into two equal-sized slots. The first and sixth subframes of each radio frame contain downlink synchronization signals. These synchronization signals include a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS).

[0006] Non-patent document 1 (Chapter 5) describes the decisions made by 3GPP regarding channel structure in LTE systems. It is assumed that CSG (Closed Subscriber Group) cells also use the same channel structure as non-CSG cells.

[0007] The Physical Broadcast Channel (PBCH) is a downlink transmission channel from a base station (hereinafter sometimes referred to as "base station") to a mobile terminal device (hereinafter sometimes referred to as "mobile terminal") or other communication terminal device (hereinafter sometimes referred to as "communication terminal"). A BCH transport block is mapped to four subframes in a 40ms interval. There is no clear signaling at 40ms intervals.

[0008] The Physical Control Format Indicator Channel (PCFICH) is a downlink transmission channel from the base station to the communication terminal. The PCFICH informs the communication terminal from the base station about the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols used for PDCCHs. The PCFICH is transmitted per subframe.

[0009] The Physical Downlink Control Channel (PDCCH) is the downlink transmission channel from the base station to the communication terminal. The PDCCH notifies the recipients of resource allocation information for the Downlink Shared Channel (DL-SCH), one of the transmission channels described later; resource allocation information for the Paging Channel (PCH), another of the transmission channels described later; and HARQ (Hybrid Automatic Repeat reQuest) information related to the DL-SCH. The PDCCH transmits uplink scheduling grants. It also transmits response signals for uplink transmissions, namely Ack (Acknowledgement) and Nack (Negative Acknowledgement). The PDCCH is also known as the L1 / L2 control signal.

[0010] The Physical Downlink Shared Channel (PDSCH) is the downlink transmission channel from the base station to the communication terminal. The PDSCH maps to both the Downlink Shared Channel (DL-SCH) used as the transport channel and the PCH used as the transport channel.

[0011] The Physical Multicast Channel (PMCH) is a downlink transmission channel from the base station to the communication terminal. The PMCH maps to the Multicast Channel (MCH), which serves as the transport channel.

[0012] The Physical Uplink Control Channel (PUCCH) is the uplink transmission channel from the communication terminal to the base station. The PUCCH transmits response signals (Ack / Nack) for downlink transmissions. It also transmits CQI (Channel Quality Indicator) reports. CQI indicates the quality of received data or the quality of the communication line. Furthermore, the PUCCH transmits scheduling requests (SRs).

[0013] The Physical Uplink Shared Channel (PUSCH) is the uplink transmission channel from the communication terminal to the base station. The PUSCH maps to the Uplink Shared Channel (UL-SCH), which is one of the transmission channels.

[0014] The Physical Hybrid ARQ Indicator Channel (PHICH) is the downlink transmission channel from the base station to the communication terminal. PHICH transmits the Ack / Nack response signals sent in response to the uplink transmission. The Physical Random Access Channel (PRACH) is the uplink transmission channel from the communication terminal to the base station. PRACH transmits the random access preamble.

[0015] Downlink reference signals (RS) are symbols known in LTE communication systems. Five types of downlink reference signals are defined: Cell-specific Reference Signal (CRS), MBSFN Reference Signal, UE-specific Reference Signal (DM-RS, also known as Demodulation Reference Signal), Positioning Reference Signal (PRS), and Channel State Information Reference Signal (CSI-RS). As a physical layer measurement for communication terminals, the received power (RSRP) of the reference signal is also measured.

[0016] The transport channel described in Non-Patent Document 1 (Chapter 5) will be explained. The broadcast channel (BCH) in the downlink transport channel is broadcast to the entire coverage area of ​​its base station (cell). The BCH is mapped to the physical broadcast channel (PBCH).

[0017] The Downlink Shared Channel (DL-SCH) employs HARQ (Hybrid ARQ)-based retransmission control. DL-SCH can broadcast over the entire coverage area of ​​a base station (cell). DL-SCH supports dynamic or semi-static resource allocation. Semi-static resource allocation is also known as persistent scheduling. DL-SCH supports discontinuous reception (DRX) of communication terminals to reduce power consumption. DL-SCH is mapped to the Physical Downlink Shared Channel (PDSCH).

[0018] The Paging Channel (PCH) supports DRX (Demand Reduction) of communication terminals to reduce power consumption. The PCH is required to broadcast over the entire coverage area of ​​the base station (cell). The PCH is mapped to physical resources such as the Physical Downlink Shared Channel (PDSCH) that can be dynamically utilized for traffic.

[0019] The Multicast Channel (MCH) is used to broadcast to the entire coverage area of ​​a base station (cell). The MCH supports SFN synthesis of MBMS (Multimedia Broadcast Multicast Service) services (MTCH and MCCH) in multi-cell transmission. The MCH supports quasi-static resource allocation. The MCH is mapped to the PMCH.

[0020] HARQ (Hybrid ARQ) based retransmission control is applied to the Uplink Shared Channel (UL-SCH) in the uplink transport channel. UL-SCH supports dynamic or semi-static resource allocation. UL-SCH is mapped to the Physical Uplink Shared Channel (PUSCH).

[0021] The Random Access Channel (RACH) is restricted to control information. RACH is subject to collision risks. RACH is mapped to the Physical Random Access Channel (PRACH).

[0022] HARQ is explained below. HARQ is a technique that improves the communication quality of a transmission line by combining Automatic Repeat Request (ARQ) and Forward Error Correction. HARQ has the following advantages: even for transmission lines where communication quality changes, retransmission can effectively enable error correction. In particular, during retransmission, the quality can be further improved by combining the received results of the initial transmission with those of the retransmission.

[0023] Here's an example illustrating the retransmission method. When the receiving side cannot correctly decode the received data—in other words, when a CRC (Cyclic Redundancy Check) error occurs (CRC = NG)—a "Nack" is sent from the receiving side to the sending side. The sending side, upon receiving the "Nack," retransmits the data. When the receiving side can correctly decode the received data—in other words, when no CRC error occurs (CRC = OK)—a "ck" is sent from the receiving side to the sending side. The sending side, upon receiving the "Ack," transmits the next data.

[0024] The logical channel described in Non-Patent Document 1 (Chapter 6) will be explained. The Broadcast Control Channel (BCCH) is a downlink channel used to broadcast system control information. The BCCH, as a logical channel, is mapped to either the Broadcast Channel (BCH) as a transmission channel or the Downlink Shared Channel (DL-SCH).

[0025] The Paging Control Channel (PCCH) is a downlink channel used to transmit paging information and system information updates. The PCCH is used when the network is unaware of the cell location of the communicating terminal. As a logical channel, the PCCH is mapped to the Paging Channel (PCH), which is used as a transport channel.

[0026] The Common Control Channel (CCCH) is a channel used for transmitting control information between a communication terminal and a base station. The CCCH is used when there is no RRC connection between the communication terminal and the network. In the downlink direction, the CCCH is mapped to the Downlink Shared Channel (DL-SCH) used as a transport channel. In the uplink direction, the CCCH is mapped to the Uplink Shared Channel (UL-SCH) used as a transport channel.

[0027] The Multicast Control Channel (MCCH) is a downlink channel used for point-to-multipoint transmission. The MCCH is used to send one or more MBMS control messages (MTCHs) from the network to the communication terminal. The MCCH is only used by the communication terminal during the MBMS reception process. The MCCH is mapped to the Multicast Channel (MCH), which serves as the transport channel.

[0028] The Dedicated Control Channel (DCCH) is a channel used to transmit dedicated control information between a communication terminal and the network in a point-to-point manner. The DCCH is used when the communication terminal is in an RRC connection. In the uplink, the DCCH is mapped to the Uplink Shared Channel (UL-SCH), and in the downlink, it is mapped to the Downlink Shared Channel (DL-SCH).

[0029] A Dedicated Traffic Channel (DTCH) is a point-to-point communication channel used to send user information to dedicated communication terminals. DTCH exists in both the uplink and downlink. In the uplink, DTCH is mapped to the Uplink Shared Channel (UL-SCH), and in the downlink, it is mapped to the Downlink Shared Channel (DL-SCH).

[0030] The Multicast Traffic Channel (MTCH) is a downlink channel used to send voice data from the network to the communication terminal. The MTCH is used only by the communication terminal during MBMS reception. The MTCH is mapped to the Multicast Channel (MCH).

[0031] CGI stands for Cell Global Identifier. ECGI stands for E-UTRAN Cell Global Identifier. In LTE, LTE-A (Long Term Evolution Advanced) and UMTS (Universal Mobile Telecommunication System), CSG (Closed Subscriber Group) cells were introduced.

[0032] A CSG (Closed Subscriber Group) cell is a cell designated by operators as having access rights to a subscriber (sometimes referred to as a "subscriber-specific cell"). The designated subscriber is permitted access to more than one cell within a PLMN (Public Land Mobile Network). The more than one cell that the designated subscriber is permitted to access is called a "CSG cell(s)". However, PLMNs have access restrictions.

[0033] A CSG cell is part of a PLMN that broadcasts a unique CSG identity (CSG ID) and uses a CSG indication to broadcast "TRUE". Members of a pre-registered and authorized joiner group access the CSG cell using the CSG ID from their access permission information.

[0034] CSG IDs are broadcast by the CSG cell or the cell itself. Multiple CSG IDs exist in LTE communication systems. Furthermore, the CSG-ID is used by the user terminal (UE) to facilitate access to CSG-associated members.

[0035] Location tracking of a communication terminal is performed on a unit consisting of one or more cells. Location tracking is used to locate the communication terminal even in standby mode, enabling calls to the terminal; in other words, it is performed to enable calls to the communication terminal. The area used for location tracking of this communication terminal is called the tracking area.

[0036] In 3GPP, base stations referred to as Home-NodeB (Home-NB; HNB) and Home-eNodeB (Home-eNB; HeNB) have been studied. HNBs in UTRAN and HeNBs in E-UTRAN are, for example, base stations providing access services for homes, corporations, and businesses. Non-Patent Document 2 discloses three different modes for accessing HeNBs and HNBs. Specifically, it discloses Open access mode, Closed access mode, and Hybrid access mode.

[0037] Furthermore, within 3GPP, the standardization of Long Term Evolution Advanced (LTE-A), version 10, is progressing steadily (see Non-Patent Documents 3 and 4). LTE-A is based on the radio inter-communication method of LTE, and is constructed by adding several new technologies.

[0038] In LTE-A systems, to support wider transmission bandwidths of up to 100MHz, carrier aggregation (CA), which combines two or more component carriers (CCs), has been studied. CA is described in Non-Patent Literature 1.

[0039] In the case of a CA (Cybernetic Association), the UE has a unique RRC connection with the network (NW). Within the RRC connection, a serving cell provides NAS (Navigation Information and Security) input. This cell is called the 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).

[0040] Based on the UE's capabilities, secondary serving cells (SCells) are constructed to form a group of serving cells together with PCells. 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).

[0041] For a UE, a serving cell group is formed by one Pcell and one or more SCells.

[0042] Furthermore, as a new technology for LTE-A, there are technologies that support wider bandwidth (Wider bandwidth extension) and Coordinated Multiple Point Transmission and Reception (CoMP) technology. CoMP, which was researched for the implementation of LTE-A in 3GPP, is described in Non-Patent Literature 1.

[0043] Furthermore, 3GPP is researching the use of small eNBs (hereinafter sometimes referred to as "small-scale base station devices") to cope with the massive traffic volume expected in the future. For example, technologies are being researched to improve frequency utilization efficiency and increase communication capacity by setting up multiple small eNBs and forming multiple small cells. Specifically, there is dual connectivity (DC), where the UE communicates by connecting to two eNBs. DC is described in Non-Patent Document 1.

[0044] Sometimes one of the eNBs that perform dual connections (DC) is called the "primary eNB (MeNB)" and the other is called the "secondary eNB (SeNB)".

[0045] Mobile network traffic is trending upwards, and communication speeds are continuously increasing. With the official implementation of LTE and LTE-A, further acceleration in communication speeds is foreseeable.

[0046] Furthermore, fifth-generation (hereinafter sometimes referred to as "5G") radio access systems are under investigation, with the goal of enabling next-generation mobile communications to begin service after 2020. For example, in Europe, the organization METIS is summarizing the requirements for 5G (see Non-Patent Document 5).

[0047] In 5G wireless access systems, for LTE systems, assuming the system capacity is 1000 times greater, the data transmission speed is 100 times greater, the data processing latency is 1 / 10th, and the number of simultaneous connections of communication terminals is 100 times greater, we can list the necessary conditions for achieving further low power consumption and low device cost.

[0048] To meet these requirements, discussions on the 5G standard are ongoing within 3GPP, as in version 15 (see Non-Patent Documents 6-10). The technology for 5G radio bands is referred to as "New Radio Access Technology" (NR), and several new technologies are under investigation (see Non-Patent Documents 11, 15, 16). For example, research is being conducted on DC utilization of LTE and NR, and frequency resource sharing between LTE and NR (see Non-Patent Documents 12, 13).

[0049] Existing technical documents

[0050] Non-patent literature

[0051] Non-patent literature 1: 3GPP TS36.300 V14.3.0

[0052] Non-patent document 2: 3GPP S1-083461

[0053] Non-patent document 3: 3GPP TR36.814 V9.2.0

[0054] Non-patent document 4: 3GPP TR36.912 V14.0.0

[0055] Non-Patent Document 5: “Scenarios, Requirements and KPIs for 5G Mobile and Wireless System”, ICT-317669-METIS / D1.1

[0056] Non-patent document 6: 3GPP TR23.799 V14.0.0

[0057] Non-patent document 7: 3GPP TR38.801 V14.0.0

[0058] Non-patent document 8: 3GPP TR38.802 V14.1.0

[0059] Non-patent document 9: 3GPP TR38.804 V14.0.0

[0060] Non-patent document 10: 3GPP TR38.912 V14.0.0

[0061] Non-patent document 11: 3GPP RP-172115

[0062] Non-patent document 12: 3GPP TS37.340 V1.0.2

[0063] Non-patent document 13: 3GPP R1-1701527

[0064] Non-patent literature 14: 3GPP R1-1712747

[0065] Non-patent document 15: 3GPP TS38.211 V1.0.0

[0066] Non-patent document 16: 3GPP TS38.300 V1.1.1

[0067] Non-patent document 17: 3GPP TS36.304 V14.4.0

[0068] Non-patent document 18: 3GPP TS36.331 V14.4.0 Summary of the Invention

[0069] The technical problem that the invention aims to solve

[0070] The NR document discusses DCs utilizing eNBs and gNBs. Furthermore, the NR document requires low-latency, high-reliability communication. However, when constructing a DC, the transmission target of uplink data from the UE is determined by the uplink data buffer capacity. Therefore, in communications requiring low latency, the UE may not be able to transmit uplink data to a base station with lower latency. Consequently, the latency in uplink data transmission increases.

[0071] Additionally, control counting for sharing the same frequency in LTE and NR is discussed. The UE switches between the LTE and NR transmitters and / or receivers to communicate with the eNB and / or gNB. However, when LTE and NR share frequencies, the timing of their synchronization signals overlaps, leading to the following problem: the UE cannot receive synchronization signals from the eNB and / or gNB, and LTE and / or NR communication cannot proceed.

[0072] In view of the above problems, one of the objectives of the present invention is to provide a low-latency and high-reliability communication system in NR.

[0073] Technical solutions adopted to solve technical problems

[0074] According to the present invention, for example, a communication system is provided, comprising: a communication terminal device; and a plurality of nodes that can be connected to the communication terminal device wirelessly and can form a branch carrying for the communication terminal device. In the communication system, the communication terminal device performs uplink transmission to an uplink transmission node among the plurality of nodes. The uplink transmission node is determined by an uplink transmission node determination process, which determines the node among the plurality of nodes that can implement the uplink transmission from the communication terminal device with lower latency as the uplink transmission node.

[0075] Furthermore, according to the present invention, for example, a communication terminal device is provided that can wirelessly communicate with a plurality of nodes that can constitute a fork bearer. The communication terminal device is configured to perform uplink transmission to an uplink transmission node selected by an uplink transmission node determination process, wherein the uplink transmission node determination process is a process of determining the node among the plurality of nodes that can perform the uplink transmission from the communication terminal device with lower latency as the uplink transmission node.

[0076] Furthermore, according to the present invention, for example, a communication node is provided that can form a fork bearer for a communication terminal device together with other communication nodes. The communication node is configured to operate as an uplink transmission node for the communication terminal device for uplink transmission by being selected by an uplink transmission node determination process. The uplink transmission node determination process is a process of determining the communication node among the plurality of communication nodes that can implement the uplink transmission from the communication terminal device with lower latency as the uplink transmission node.

[0077] Technical effect

[0078] According to the present invention, a low-latency and highly reliable communication system can be provided in NR.

[0079] The objects, features, aspects, and advantages of the present invention will become more apparent from the following detailed description and accompanying drawings. Attached Figure Description

[0080] Figure 1 This is an explanatory diagram showing the structure of the radio frame used in an LTE communication system.

[0081] Figure 2 This is a block diagram showing the overall structure of a communication system 200 using the LTE method discussed in 3GPP.

[0082] Figure 3 It is shown Figure 2 The diagram shows the structure of the mobile terminal 202.

[0083] Figure 4 It is shown Figure 2 The diagram shows the structure of base station 203.

[0084] Figure 5 This is a block diagram showing the structure of the MME.

[0085] Figure 6 This is a flowchart illustrating the process from cell search to standby mode performed by a communication terminal (UE) in an LTE communication system.

[0086] Figure 7 This is a diagram illustrating the concept of a cell structure in the case of a hybrid presence of macro eNBs and small eNBs.

[0087] Figure 8 This is a diagram illustrating an example of the process for setting the MN to which node the UE transmits uplink data in Implementation 1.

[0088] Figure 9 This is a diagram illustrating an example of the process by which the UE determines the uplink transmission node in implementation 1.

[0089] Figure 10 This is a diagram illustrating an example of the process by which the UE uses a threshold to determine the uplink transmission node in implementation 1.

[0090] Figure 11 This is a diagram illustrating an example of the process by which the UE uses a threshold to determine the uplink transmission node in implementation 1.

[0091] Figure 12 This is a variation of implementation 1, showing an example of a process in which the SN performs unlicensed transmission in a forked bearer.

[0092] Figure 13 This is a variation of implementation 1, showing an example of a process in which the SN performs unlicensed transmission in a forked bearer.

[0093] Figure 14 This is a variation of implementation 1, illustrating another example of the process of SN performing unlicensed transmission in a forked bearer.

[0094] Figure 15 This is a variation of implementation 1, illustrating another example of the process of SN performing unlicensed transmission in a forked bearer.

[0095] Figure 16 This is a variation of implementation 1, illustrating another example of the process of SN performing unlicensed transmission in a forked bearer.

[0096] Figure 17 This is a variation of implementation 1, illustrating another example of the process of SN performing unlicensed transmission in a forked bearer.

[0097] Figure 18 This is a variation of implementation 1, showing an example of a process in which MN and SN perform unlicensed transmission in a forked bearer.

[0098] Figure 19 This is a variation of implementation 1, showing an example of a process in which MN and SN perform unlicensed transmission in a forked bearer.

[0099] Figure 20 This is a variation of implementation 1, showing another example of the process of SN performing unlicensed transmission in a forked bearer.

[0100] Figure 21 This is a variation of implementation 1, illustrating another example of the process of SN performing unlicensed transmission in a forked bearer.

[0101] Figure 22 This is a variation of implementation 1, illustrating another example of the process of SN performing unlicensed transmission in a forked bearer.

[0102] Figure 23 This is a variation of implementation 1, illustrating another example of the process of SN performing unlicensed transmission in a forked bearer.

[0103] Figure 24 This is a diagram illustrating an example of the process for setting up unlicensed transmission in packet replication, relating to implementation 2.

[0104] Figure 25 This is a diagram illustrating an example of the process for setting up unlicensed transmission in packet replication, relating to implementation 2.

[0105] Figure 26 This is a diagram illustrating an example of the process for setting up unlicensed transmission in packet replication, relating to implementation 2.

[0106] Figure 27 This is a diagram illustrating an example of the process for setting up packet replication for uplink communication configured to transmit without permission, relating to implementation 2.

[0107] Figure 28 This is a diagram illustrating an example of the process for setting up packet replication for uplink communication configured to transmit without permission, relating to implementation 2.

[0108] Figure 29This is a diagram illustrating an example of the process for setting up packet replication for uplink communication configured to transmit without permission, relating to implementation 2.

[0109] Figure 30 This is a diagram illustrating an example of the process for setting up packet copying and unlicensed transmission using the same signaling to notify the act of packet copying and the act of unlicensed transmission settings, in relation to implementation 2.

[0110] Figure 31 This is a diagram illustrating an example of the process for setting up packet copying and unlicensed transmission using the same signaling to notify the act of packet copying and the act of unlicensed transmission settings, in relation to implementation 2.

[0111] Figure 32 Regarding implementation method 3, a diagram is shown illustrating uplink preemption indication using frequency resources in areas different from those used for downlink user data transmission and reception.

[0112] Figure 33 This is a diagram showing an example of uplink priority indication using PDCCH in implementation 3.

[0113] Figure 34 This is a variation of implementation 3, showing a diagram illustrating an example of information generated preferentially using prescribed reference numerals.

[0114] Figure 35 This is a diagram showing an example of the reordering of SS modules in an SS burst of NR, relating to implementation 4.

[0115] Figure 36 Regarding implementation method 4, a timing diagram is shown of the transmission of the SS module of the NR that does not repeat the non-MBSFN signal of LTE.

[0116] Figure 37 Regarding implementation 4, a diagram showing an example of setting an offset at the frame boundaries of LTE and NR is provided.

[0117] Figure 38 This is a diagram showing an example of a configuration change for the SS burst signal of NR, relating to implementation 4.

[0118] Figure 39 Regarding implementation method 5, a flowchart is shown showing the steps of instructing simplex TX / duplex TX from the main base station to the UE.

[0119] Figure 40 Regarding implementation method 5, a flowchart is shown showing the notification of SCell information when SCell is activated / deactivated.

[0120] Figure 41 This is a variation of implementation 5, showing a diagram illustrating an example of transmitting the PUCCH of LTE and the PUCCH of NR using the same subframe in simplex TX.

[0121] Figure 42 Regarding implementation method 6, a flowchart is shown showing the process of determining the path loss of SUL using downlink measurement signals from an NR base station.

[0122] Figure 43 This is a diagram showing an example of an eMBB UE using FL-DMRS priority, relating to implementation 7.

[0123] Figure 44 This is a diagram showing an example of an eMBB UE using FL-DMRS priority, relating to implementation 7.

[0124] Figure 45 Regarding implementation 7, a diagram shows an example of setting FL-DMRS and add-DMRS to prioritize FL-DMRS in the case of an eMBB UE.

[0125] Figure 46 Regarding implementation 7, a diagram shows an example of prioritizing FL-DMRS when only one time slot is used by the eMBB UE.

[0126] Figure 47 Regarding implementation 7, a flowchart is shown as an example of prioritizing the processing of FL-DMRS when only the time slot used by the eMBB UE is set for FL-DMRS.

[0127] Figure 48 Regarding implementation 7, a flowchart is shown as an example of prioritizing the processing of FL-DMRS when only the time slot used by the eMBB UE is set for FL-DMRS.

[0128] Figure 49 Regarding implementation 7, a diagram shows an example of prioritizing FL-DMRS when only one time slot is used by the eMBB UE.

[0129] Figure 50 Regarding implementation 7, a diagram shows an example of prioritizing FL-DMRS when only one time slot is used by the eMBB UE.

[0130] Figure 51 Regarding implementation 7, a diagram shows an example of prioritizing FL-DMRS when only one time slot is used by the eMBB UE.

[0131] Figure 52 Regarding implementation 7, a diagram shows an example of prioritizing FL-DMRS when only one time slot is used by the eMBB UE.

[0132] Figure 53 This is a variation of implementation 7, showing an example of prioritizing FL-DMRS, add-DMRS, and PUCCH or / and SRS for use with an eMBB UE.

[0133] Figure 54 This is a variation of implementation 7, showing an example of prioritizing FL-DMRS, add-DMRS, and PUCCH or / and SRS for use with an eMBB UE.

[0134] Figure 55 This is a variation of implementation 7, showing an example of prioritizing FL-DMRS, add-DMRS, and PUCCH or / and SRS for use with an eMBB UE.

[0135] Figure 56 This is a variation of implementation 7, showing an example of prioritizing FL-DMRS when only FL-DMRS is configured for one time slot of the eMBB UE.

[0136] Figure 57 This is a variation of embodiment 7, showing an example of a method for prioritizing completion when SRS is set.

[0137] Figure 58 This is a variation of implementation 7, showing an example of a method for prioritizing completion when PUCCH is set.

[0138] Figure 59 This is a variation 3 of implementation 7, showing an example of setting priority for SR.

[0139] Figure 60 This is a variation of implementation 7, Example 4, showing an example of a method for prioritizing the repeated transmission of data for URLLCUE, such as across time slots used by eMBB UE.

[0140] Figure 61 This is a variation of implementation 7, Example 4, showing an example of a method for prioritizing the repeated transmission of data for URLLCUE, such as across time slots used by eMBB UE.

[0141] Figure 62 This is a variation of implementation 7, Example 4, showing an example of a method for prioritizing the repeated transmission of data for URLLCUE, such as across time slots used by eMBB UE.

[0142] Figure 63 This is a variation of implementation 7, Example 4, showing an example of a method for prioritizing the repeated transmission of data for URLLCUE, such as across time slots used by eMBB UE.

[0143] Figure 64 This is a variation 5 of implementation 7, showing an example of a method for multiplexing an eMBB UE using a PDCCH and a URLLC UE using time slots.

[0144] Figure 65 This is a variation 5 of implementation 7, showing an example of a method for multiplexing an eMBB UE using a PDCCH and a URLLC UE using time slots.

[0145] Figure 66 This is a variation of implementation 7, shown in Figure 6, illustrating an example of prioritizing PDSCH resources when only FL-DMRS is configured for one time slot of the eMBB UE.

[0146] Figure 67 This is a variation of implementation 7, shown in Figure 6, illustrating an example of prioritizing PUSCH resources when only FL-DMRS is configured for one time slot of the eMBB UE.

[0147] Figure 68 This is a variation of embodiment 7, shown in Figure 6, illustrating an example of a UL having multiple completion DMRSs configured. Detailed Implementation

[0148] Implementation method 1.

[0149] Figure 2 This is a block diagram showing the overall structure of a communication system 200 using the LTE method discussed in 3GPP. Figure 2The following explanation is provided. The radio access network is referred to as E-UTRAN (Evolved Universal Terrestrial Radio Access Network) 201. The communication terminal device, namely the mobile terminal device (hereinafter referred to as "Mobile Terminal (User Equipment): UE)") 202, can wirelessly communicate with the base station device (hereinafter referred to as "Base Station (E-UTRAN NodeB): eNB)") 203, and use wireless communication to transmit and receive signals.

[0150] Here, "communication terminal device" refers not only to mobile terminal devices such as mobile phone terminals, but also to stationary devices such as sensors. In the following description, "communication terminal device" may sometimes be abbreviated as "communication terminal".

[0151] If the control protocols for the mobile terminal 202, such as RRC (Radio Resource Control), and user-level protocols (hereinafter sometimes referred to as U-Plane), such as PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical layer), terminate at the base station 203, then the E-UTRAN consists of one or more base stations 203.

[0152] The Radio Resource Control (RRC) protocol between mobile terminal 202 and base station 203 performs broadcasting, paging, and RRC connection management. The states of base station 203 and mobile terminal 202 in the RRC are RRC_IDLE and RRC_CONNECTED.

[0153] During RRC_IDLE, PLMN (Public Land Mobile Network) selection, System Information (SI) broadcasting, paging, cell re-selection, and mobility checks are performed. During RRC_CONNECTED, the mobile terminal has an RRC connection and can send and receive data with the network. Furthermore, during RRC_CONNECTED, handover (HO) and neighbor cell determination (measurement) are also performed.

[0154] Base station 203 is classified into eNB 207 and Home-eNB 206. Communication system 200 includes eNB group 203-1 containing multiple eNBs 207, and Home-eNB group 203-2 containing multiple Home-eNBs 206. Furthermore, the system consisting of EPC (Evolved Packet Core) as the core network and E-UTRAN 201 as the radio access network is called EPS (Evolved Packet System). Sometimes, EPC as the core network and E-UTRAN 201 as the radio access network are collectively referred to as the "network".

[0155] The eNB 207 connects to the Mobility Management Entity (MME), Serving Gateway (S-GW), or an MME / S-GW unit (hereinafter sometimes referred to as "MME unit") 204, which includes both the MME and S-GW, via the S1 interface, and communicates control information between the eNB 207 and the MME unit 204. One eNB 207 can connect to multiple MME units 204. The eNBs 207s also connect to each other via the X2 interface, communicating control information between them.

[0156] The Home-eNB 206 connects to the MME unit 204 via the S1 interface, and communication of control information between the Home-eNB 206 and the MME unit 204 is performed. One MME unit 204 can be connected to multiple Home-eNB 206s. Alternatively, the Home-eNB 206 connects to the MME unit 204 via the HeNBGW (Home-eNB Gateway) 205. The Home-eNB 206 and HeNBGW 205 are connected via the S1 interface, and the HeNBGW 205 and MME unit 204 are connected via the S1 interface.

[0157] One or more Home-eNB206s are connected to one HeNBGW205 and communicate via the S1 interface. The HeNBGW205 is connected to one or more MME units 204 and communicates via the S1 interface.

[0158] MME 204 and HeNBGW 205 are upper-level devices, specifically upper-level nodes, that control the connection between eNB 207 and Home-eNB 206 (which act as base stations) and mobile terminal (UE) 202. MME 204 constitutes the EPC (Engineering Process Control) as the core network. Base station 203 and HeNBGW 205 constitute E-UTRAN 201.

[0159] Furthermore, the following structure was studied in 3GPP. It supports the X2 interface between Home-eNBs 206. That is, Home-eNBs 206 are connected via the X2 interface, and control information is communicated between them. From the perspective of MME 204, HeNBGW 205 can be considered as a Home-eNB 206. From the perspective of Home-eNB 206, HeNBGW 205 can be considered as MME 204.

[0160] Whether the Home-eNB206 is connected to the MME unit 204 via the HeNBGW205 or directly to the MME unit 204, the interface between the Home-eNB206 and the MME unit 204 is always the S1 interface.

[0161] Base station 203 can constitute one cell or multiple cells. Each cell has a predetermined range as its coverage area, which enables communication with mobile terminal 202, and wireless communication is conducted with mobile terminal 202 within the coverage area. When a base station 203 constitutes multiple cells, each cell is configured to communicate with mobile terminal 202.

[0162] Figure 3 It shows Figure 2 The diagram shows the structure of the mobile terminal 202. Figure 3The transmission process of the mobile terminal 202 shown will be described. First, control data from the protocol processing unit 301 and 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 transmitted to the encoding unit 304 for error correction and other encoding processing. Alternatively, data may be output directly from the transmission data buffer unit 303 to the modulation unit 305 without encoding processing. The data encoded by the encoding unit 304 is modulated in 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 wireless transmission frequency. Afterward, the transmission signal is transmitted from the antenna 307 to the base station 203.

[0163] Furthermore, the receiving process of the mobile terminal 202 is performed as follows: Wireless signals from the base station 203 are received via antenna 307. The received signal is converted from a wireless receiving frequency to a baseband signal at frequency conversion unit 306, and demodulated in demodulation unit 308. The demodulated data is transmitted to decoding unit 309 for error correction and other decoding processes. Of the decoded data, control data is transmitted to protocol processing unit 301, and user data is transmitted to application unit 302. A series of processes of the mobile terminal 202 are controlled by control unit 310. Thus, although in Figure 3 The details have been omitted, but the control unit 310 is connected to each of the units 301 to 309.

[0164] Figure 4 It shows Figure 2 The diagram shows the structure of base station 203. Figure 4 The transmission processing of the base station 203 shown will be described. The EPC communication unit 401 handles data transmission and reception between base station 203 and EPC (MME unit 204, etc.), HeNBGW 205, etc. Other base station communication units 402 handle data transmission and reception with other base stations. The EPC communication unit 401 and other base station communication units 402 exchange information with the protocol processing unit 403. Control data from the protocol processing unit 403, as well as user data and control data from the EPC communication unit 401 and other base station communication units 402, are stored in the transmission data buffer unit 404.

[0165] The data stored in the transmission data buffer 404 is transmitted to the encoding unit 405 for encoding processing such as error correction. Alternatively, data can be directly output from the transmission data buffer 404 to the modulation unit 406 without encoding processing. The encoded data is modulated in the modulation unit 406. The modulated data is converted into a baseband signal and then output to the frequency conversion unit 407, where it is converted into a wireless transmission frequency. Afterward, the transmission signal is transmitted to one or more mobile terminals 202 using the antenna 408.

[0166] Furthermore, the reception processing of base station 203 is performed as follows. Wireless signals from one or more mobile terminals 202 are received by antenna 408. The received signal is converted from a wireless receiving frequency to a baseband signal by frequency conversion unit 407, and demodulated by demodulation unit 409. The demodulated data is transmitted to decoding unit 410 for error correction and other decoding processing. Of the decoded data, control data is transmitted to protocol processing unit 403, or EPC communication unit 401, or other base station communication units 402; user data is transmitted to EPC communication unit 401 and other base station communication units 402. A series of processes of base station 203 are controlled by control unit 411. Thus, although in Figure 4 The details have been omitted, but the control unit 411 is connected to each of the units 401 to 410.

[0167] Figure 5 This is a block diagram showing the structure of the MME. Figure 5 The above is shown in the figure. Figure 2 The structure of MME 204a included in MME 204 is shown. PDN GW communication unit 501 performs data transmission and reception between MME 204a and PDN GW. Base station communication unit 502 performs data transmission and reception between MME 204a and base station 203 via the S1 interface. When the data received from the PDN GW is user data, the user data is transmitted from PDN GW communication unit 501 to base station communication unit 502 via user plane communication unit 503, and then sent to one or more base stations 203. When the data received from base station 203 is user data, the user data is transmitted from base station communication unit 502 to PDN GW communication unit 501 via user plane communication unit 503, and then sent to PDN GW.

[0168] When the data received from the PDN GW is control data, the control data is transmitted 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 transmitted from the base station communication unit 502 to the control plane control unit 505.

[0169] With HeNBGW205 present, HeNBGW communication unit 504 is set up to transmit and receive data between MME204a and HeNBGW205 via interface (IF) depending on the information type. Control data received from HeNBGW communication unit 504 is transmitted from HeNBGW communication unit 504 to control plane control unit 505. The processing result of control plane control unit 505 is sent to PDN GW via PDNGW communication unit 501. In addition, the result processed by control plane control unit 505 is sent to one or more base stations 203 via base station communication unit 502 and S1 interface, or sent to one or more HeNBGW205 via HeNBGW communication unit 504.

[0170] The control plane control unit 505 includes a NAS security unit 505-1, an SAE bearer control unit 505-2, and an idle state mobility management unit 505-3, and performs all processing for the control plane (hereinafter sometimes referred to as C-Plane). The NAS security unit 505-1 handles the security of NAS (Non-Access Stratum) messages. The SAE bearer control unit 505-2 manages the SAE (System Architecture Evolution) bearer. The idle state mobility management unit 505-3 manages mobility in standby state (idle state; LTE-IDLE state, or simply idle), generates and controls paging signals in standby state, adds, deletes, updates, retrieves, and manages the tracking area list for one or more mobile terminals 202 within the coverage area.

[0171] MME204a distributes paging signals to one or more base stations 203. Furthermore, MME204a performs mobility control in the idle state. MME204a manages the tracking area list when the mobile terminal is in idle state and in active state. MME204a initiates the paging protocol by sending a paging message to cells belonging to the tracking area registered by the UE. The management of the CSG, CSG-ID, and whitelist of the Home-eNB206 connected to MME204a can be performed by the idle state mobility management unit 505-3.

[0172] Next, an example of a cell search method in a communication system is shown. Figure 6This is a flowchart illustrating the process of a communication terminal (UE) in an LTE communication system from cell search to standby operation. If the communication terminal starts cell search, in step ST601, the first synchronization signal (P-SS) and the second synchronization signal (S-SS) sent from the surrounding base stations are used to obtain the synchronization of time slot timing and frame timing.

[0173] P-SS and S-SS are collectively referred to as the Synchronization Signal (SS). The Synchronization Signal (SS) contains a synchronization code that corresponds one-to-one with the PCI assigned to each cell. This study investigated setting the number of PCIs to 504. Synchronization was achieved using these 504 PCIs, and the PCIs of synchronized cells were detected (determined).

[0174] Next, in step ST602, the reference signal (RS) sent from the base station to each cell after synchronization is achieved, i.e., the cell-specific reference signal (CRS), is measured, and the received power (RSRP) of the RS is determined. The reference signal (RS) uses a code that corresponds one-to-one with the PCI. This code can be used to obtain correlation and thus separate the cell from other cells. By deriving the RS code of the cell based on the PCI determined in step ST601, the RS can be detected, and the received power of the RS can be measured.

[0175] Next, in step ST603, the cell with the best RS reception quality is selected from one or more cells detected up to step ST602, for example, the cell with the highest RS reception power, i.e., the best cell.

[0176] Next, in step ST604, the PBCH of the best cell is received to obtain the broadcast information, i.e., the BCCH. The BCCH on the PBCH maps to the MIB (Master Information Block), which contains cell structure information. Therefore, by receiving the PBCH and obtaining the BCCH, the MIB can be obtained. Information in the MIB includes, for example, the DL (downlink) system bandwidth (also known as transmission bandwidth configuration), the number of transmit antennas, and the SFN (System Frame Number).

[0177] Next, in step ST605, the cell structure information based on the MIB is received from the DL-SCH of the cell, and SIB (System Information Block) 1 in the broadcast information BCCH is obtained. SIB1 contains information related to accessing the cell, information related to cell selection, and scheduling information for other SIBs (SIBk; k ≥ 2 integers). In addition, SIB1 also contains the Tracking Area Code (TAC).

[0178] Next, in step ST606, the communication terminal compares the TAC of SIB1 received in step ST605 with the TAC portion of the Tracking Area Identity (TAI) in the tracking area list already stored by the communication terminal. The tracking area list is also called the TAI list. TAI is identification information used to identify the tracking area, consisting of the MCC (Mobile Country Code), MNC (Mobile Network Code), and TAC (Tracking Area Code). MCC is the country code. MNC is the network code. TAC is the tracking area code number.

[0179] If the comparison result obtained in step S606 is the same as the TAC received in step ST605, and it is also included in the tracking area list, then the communication terminal enters standby mode in that cell. If the comparison result is the same as the TAC received in step ST605, and it is not included in the tracking area list, then the communication terminal requests a change of tracking area from the core network (EPC) containing the MME, etc., through that cell to perform a TAU (Tracking Area Update).

[0180] The apparatus constituting the core network (hereinafter sometimes referred to as "core network-side apparatus") updates the tracking area list based on the TAU request signal and the identification number (UE-ID, etc.) of the communication terminal sent from the communication terminal. The core network-side apparatus sends the updated tracking area list to the communication terminal. The communication terminal rewrites (updates) its own TAC list based on the received tracking area list. Afterward, the communication terminal enters standby mode in the cell.

[0181] The widespread adoption of smartphones and tablets has led to an explosive growth in traffic volume using cellular wireless communication systems, raising concerns about a global shortage of wireless resources. To address this situation and improve frequency utilization efficiency, research has been conducted on cell miniaturization and promoting spatial separation.

[0182] In the existing cell structure, cells composed of eNBs have a wide coverage area. Previously, cells were constructed to cover a specific area by using the wide coverage area of ​​multiple cells consisting of multiple eNBs.

[0183] When cell miniaturization is implemented, cells composed of existing eNBs have a narrower coverage area compared to cells composed of existing eNBs. Therefore, similar to existing technologies, a large number of miniaturized eNBs are needed to cover a certain area compared to existing eNBs.

[0184] In the following explanation, as with conventional eNBs, cells with larger coverage areas are referred to as "macrocells," and the eNBs that make up macrocells are referred to as "macro eNBs." Furthermore, as with cells that have undergone miniaturization, cells with smaller coverage areas are referred to as "small cells," and the eNBs that make up small cells are referred to as "small eNBs."

[0185] For example, a macro eNB can be a "wide area base station" as described in Non-Patent Document 7.

[0186] Small eNBs can be, for example, low-power nodes, local nodes, and hotspots. Furthermore, small eNBs can be pico eNBs constituting pico cells, femto eNBs constituting femto cells, HeNBs, RRHs (Remote Radio Heads), RRUs (Remote Radio Units), RREs (Remote Radio Equipment), or RNs (Relay Nodes). Additionally, small eNBs can also be "Local Area Base Stations" or "Home Base Stations" as described in Non-Patent Document 7.

[0187] Figure 7 This diagram illustrates the concept of a cell structure when macro eNBs and small eNBs are combined. Macro cells, composed of macro eNBs, have a relatively large coverage area 701. Small cells, composed of small eNBs, have a smaller coverage area 702 compared to the coverage area 701 of the macro eNBs (macro cells).

[0188] When multiple eNBs are mixed together, the coverage area of ​​a cell consisting of one eNB is sometimes included in the coverage area of ​​a cell consisting of other eNBs. Figure 7 In the cell structure shown, as indicated by reference numerals "704" or "705", the coverage area 702 of a small cell consisting of small eNBs is sometimes included within the coverage area 701 of a macro cell consisting of macro eNBs.

[0189] Furthermore, as indicated by reference numeral "705", there are also cases where the coverage areas 702 of multiple, for example, two small cells are included within the coverage area 701 of a macrocell. A mobile terminal (UE) 703, for example, is included within the coverage area 702 of the small cells and communicates via the small cells.

[0190] In addition, Figure 7 In the structure of the cell shown, as indicated by reference numeral "706", the following situation will occur: the coverage area 701 of the macro cell composed of macro eNBs and the coverage area 702 of the small cell composed of small eNBs will overlap in a complex manner.

[0191] Furthermore, as indicated by reference numeral "707", the coverage area 701 of macro cells composed of macro eNBs and the coverage area 702 of small cells composed of small eNBs will not overlap.

[0192] Furthermore, as indicated by reference numeral "708", the following situation will also occur: the coverage area 702 of multiple small cells consisting of multiple small eNBs will be within the coverage area 701 of a macro cell consisting of a macro eNB.

[0193] In uplink transmission using a forked bearer with dual connectivity (DC), the decision to send uplink data to the secondary node (SN) is based on the UE's uplink data buffer capacity (see Non-Patent Document 12). The primary node (MN) (see Non-Patent Document 12) notifies the UE of an uplink data buffer capacity threshold. The UE compares its uplink data buffer capacity with this threshold. If the uplink data buffer capacity is below the threshold, it sends uplink data to the MN; if the uplink data buffer capacity is greater than the threshold, it sends uplink data to both the MN and the SN.

[0194] However, for example, if the above method is applied to uplink data requesting low latency, uplink transmission will be performed on the MN if the uplink data buffer capacity is smaller than the threshold. For example, if the SN is supporting short symbol lengths (durations), regardless of whether uplink transmission using the SN achieves low latency, the following problem will arise: uplink transmission must be performed on the MN, and low latency cannot be achieved.

[0195] The following are solutions to the above problems.

[0196] The UE can be configured to send uplink data to a specific node. The MN will notify the UE of information related to the node used for uplink transmission. The node used for uplink transmission can be the MN, SN, or both ME and SN. Information about the node used for uplink transmission can include, for example, the base station's identifier.

[0197] The information for the uplink transmission node can be cell group information. Cell group information can be primary cell group (MCG) and / or secondary cell group (SCG) information. The uplink transmission node information can also be cell information, which can be a cell identifier. This indicates the cell used by the UE for uplink transmission.

[0198] In this specification, the UE's communication target is mainly represented as a node or communication node. However, unless otherwise specified, the UE's communication target may be a cell group, base station, or cell.

[0199] Notification of information related to uplink transmitting nodes can be achieved using RRC signaling. For example, information related to uplink transmitting nodes can be included in an RRC Connection Reconfiguration message. Alternatively, information related to uplink transmitting nodes can be notified during DC configuration processing.

[0200] The SN notifies the MN of information used to determine which uplink transmission node to set from the UE (hereinafter sometimes referred to as uplink transmission node determination information). The uplink transmission node determination information may be information related to latency characteristics. Additionally, it may be information related to supported radio settings. Furthermore, it may be information related to supported communication services. Additionally, it may be information related to load conditions and resource usage. Finally, it may be information related to the radio wave transmission environment. The uplink transmission node determination information can be notified using Xn signaling or X2 signaling. For example, the uplink transmission node determination information can be notified during DC setting processing.

[0201] For example, uplink transmission node determination information can be notified during SgNB add-on processing. For example, the uplink transmission node determination information can be included in the SgNB Addition Request Acknowledge response for notification. The MN can configure the uplink transmission node for the UE at the start of the DC. Additionally, for example, uplink transmission node determination information can be notified during SgNB change processing. For example, the uplink transmission node determination information can be included in the SgNB Addition Request Acknowledge response for notification. If the processing is initiated due to a request from the SN, the uplink transmission node determination information can be included in the SgNB Modification Required notification for notification. The MN can configure the uplink transmission node for the UE when the SN structure changes.

[0202] The following are seven examples of node decision information sent in the uplink.

[0203] (1) SN supports SCS (Subcarrier Spacing). Symbol periods can be used.

[0204] (2) Does the SN support uplink ungranted transmission of information?

[0205] (3) QoS of communication services supported by the SN. QoS of uplink communication services can be used. Information representing QoS can include, for example, QoS distribution, QCI, latency, packet error rate, etc.

[0206] (4) RRC settings for SN.

[0207] (5) SN wireless settings. For example, AS settings, MAC settings, PHY settings, etc.

[0208] (6) The number of symbols in the slots supported by the SN. This can be information about whether the SN supports slots with fewer symbols than usual.

[0209] (7)(1) to (6) combinations.

[0210] The MN (Node Provider) determines the uplink transmission node for the UE. By using uplink transmission node determination information, the MN decides which node the UE should transmit uplink data to. For example, the MN uses information about the symbol duration supported by the SN (Signal Provider) obtained from the SN to determine the node with a shorter symbol duration than its own as the UE's uplink transmission node. If the symbol durations are the same, the MN determines the NB (Node Provider) of both nodes as the UE's uplink transmission node. For instance, by configuring uplink data requests to have low latency characteristics, the UE can transmit uplink data to nodes that support shorter symbol durations, enabling low-latency uplink data transmission.

[0211] As another example, the MN uses information about whether unlicensed transmission is supported from the SN to determine which nodes support unlicensed transmission as the uplink transmission nodes for the UE. If both nodes support unlicensed transmission, the MN will determine both nodes as the uplink transmission nodes for the UE. For example, by configuring uplink data requests to have low latency characteristics in this way, the UE can perform unlicensed transmission without requiring a SR, and can transmit uplink data with low latency.

[0212] The MN can request uplink transmission node determination information from the SN. This request can be made using Xn or X2 signaling. For example, the request can be made during DC configuration processing. Alternatively, it can be made during SgNB addition processing. Or, the request can be included in an SgNB Addition Request. The MN can configure the uplink transmission node for the UE at the start of DC. Additionally, the request can be made during SgNB modification processing. Or, the request can be included in an SgNB Modification Request. The MN can configure the uplink transmission node for the UE.

[0213] The UE can notify the MN of information used to determine which uplink transmission node to assign from the UE. As an example of the uplink transmission node determination information notified by the UE to the MN, there exists a QoS requested by the communication service. The uplink transmission node determination information can be the QoS requested by the uplink communication service. The uplink transmission node determination information can be information representing QoS, such as QoS distribution, QCI, desired latency, packet error rate, etc. It can include information used to determine the UE. For example, there may be an identifier used to determine the UE.

[0214] RRC signaling can be used to notify uplink transmission of node determination information. For example, uplink transmission of node determination information can be included in messages such as RRC Connection Request, RRC Connection Setup Complete, RRC Connection Reestablishment Request, and RRC Connection Reestablishment Complete. By using the RRC messages shown in the above example, the MN can use this information for the UE during DC configuration.

[0215] The MN can notify the UE of uplink transmission node determination information. This request can be made using RRC signaling. For example, the request can be included in messages such as RRC Connection Setup or RRC Connection Reestablishment. The MN can also configure the uplink transmission node for the UE.

[0216] The CN can notify the MN of information used to determine which uplink transmission node to assign from the UE. As an example of an uplink transmission node determination message notified by the CN to the MN, the message includes the identifier of the UE and the QoS requested by the UE's uplink communication service. The uplink transmission node determination information can be the QoS requested by the uplink communication service. This information can represent QoS information such as QoS distribution, QCI, desired latency, packet error rate, etc. This information can be notified using S1 signaling or NG-C signaling.

[0217] The MN can notify the CN of uplink transmission node determination information. This notification can be sent using S1 signaling or NG-C signaling. The MN can also configure the uplink transmission node for the UE.

[0218] Figure 8 This is a diagram illustrating an example of the process of setting the MN to determine which node the UE should send uplink data to. Figure 8 In the example, MgNB is represented as MN, and SgNB is represented as SN. In step ST801, the configuration process of DC using a forked bearer is performed among the UE, MgNB, and SgNB. Figure 8In the example, the configuration of the uplink data transmission node based on the UE's uplink data buffer capacity is not performed. During DC configuration processing, the MgNB can notify the UE of information indicating the configuration method for the uplink transmission node. This information can be notified using RRC signaling. Alternatively, this information can be included in the RRC connection reconfiguration message. The UE applies the notified configuration method. Figure 8 In the example, the MgNB determines the uplink transmission node and notifies the UE of the method for setting the uplink transmission node.

[0219] in addition, Figure 8 The example illustrates a method for determining the uplink transmission node using the SgNB's SCS information. In step ST802, the MgNB requests the SgNB's SCS information from the SgNB. In step ST803, the SgNB, based on the request from the MgNB, notifies the MgNB of the SCS information supported by this SgNB. Support information can be per cell. The SgNB can notify the supported SCS information on a per-cell basis. The SCS information can be notified in association with the cell's identifier.

[0220] In step ST804, the MgNB compares the SCS supported by this node with the SCS supported by the SgNB, and determines the node that supports the smaller SCS as the uplink transmission node. Figure 8 The example shows a scenario where the SgNB supports a smaller SCS than the MgNB. The MgNB determines the SgNB as the uplink transmission node.

[0221] At this point, the MgNB can use the QoS information of the UE's communication services obtained in advance. The MgNB can obtain the QoS information from the CN or from the UE. The QoS information of the communication services can be notified to the MgNB from the CN during the bearer configuration processing for the UE's communication services. The QoS information of the communication services can be included in the bearer information used for DC configuration processing.

[0222] The MgNB can determine the uplink transmission node by supporting a smaller SCS in a way that meets QoS requirements. For example, in the case where the UE requests low latency features in its communication service, the MgNB will determine the SgNB that supports a smaller SCS as the uplink transmission node. In step ST805, the MgNB notifies the UE of the SgNB that has been determined as the uplink transmission node.

[0223] The information provided by the SgNB includes node information, base station information, cell group information, or cell information. The MgNB associates the aforementioned information used to determine the SgNB with the case where it is determined to be an uplink transmission node and notifies the UE accordingly.

[0224] In step ST806, the UE begins uplink transmission processing to the uplink transmission node (SgNB) notified by the MgNB. If uplink transmission data is generated in the UE, the UE sends an SR to the SgNB in ​​step ST807. The SR settings in the MgNB and SgNB can be pre-set in the DC configuration process and notified to the UE from the MgNB. In step ST805, if the uplink transmission cell information has been notified from the MgNB, the UE does not send an SR to that cell.

[0225] In step ST808, the SgNB notifies the UE of the permission (uplink scheduling information) for uplink communication. In step ST809, the UE sends uplink data to the SgNB according to the uplink permission. The UE may also notify the BSR (Buffer Status Report). Then, the uplink data is sent by repeating steps ST808 and ST809 until the uplink data disappears.

[0226] Therefore, in the DC, the UE can transmit uplink data to the SgNB, which is designated as the uplink transmission node by the MgNB, regardless of the uplink data buffer capacity. For example, in the case of uplink data requesting low latency, even if the data is small, the UE can transmit uplink data to the SgNB that supports a smaller SCS. The capability map in the DC enables further low latency.

[0227] As described above, a method for the MN to notify the UE of information related to the uplink transmission node is disclosed. Other methods are also disclosed. The MN may notify the UE of information used to determine the uplink transmission node.

[0228] Notifications regarding information used by the UE to determine the node for uplink transmission can be provided using RRC signaling. For example, this information can be included in an RRC Connection Reconfiguration message. Alternatively, it can be notified during DC configuration processing.

[0229] Here are seven examples of information used by the UE to determine which node to use for uplink transmission.

[0230] (1) SCS (Sub Carrier Spacing) supported by each node. Symbol period can be used.

[0231] (2) Whether each node supports uplink ungranted transmission of information.

[0232] (3) QoS of communication services supported by each node. QoS of uplink communication services can be used. Information representing QoS can include, for example, QoS distribution, QCI, latency, packet error rate, etc.

[0233] (4) RRC settings for each node.

[0234] (5) Wireless settings for each node. For example, AS settings, MAC settings, PHY settings, etc.

[0235] (6) The number of symbols in the slots supported by the SN. This can be information about whether the SN supports slots with fewer symbols than usual.

[0236] (7)(1) to (6) combinations.

[0237] The above information can be associated with MN or SN. It can be determined whether the information belongs to the MN or SN. Alternatively, the above information can be associated with each node. For example, the above information can be associated with the base station identifier. It can be determined which node or base station the information belongs to. Alternatively, the above information can be associated with each cell group. The above information can be associated with MCG or SCG. It can be determined whether the above information belongs to the MCG or SCG. Alternatively, the above information can be associated with the cell. For example, the above information can be associated with the cell identifier. It can be determined which cell the information belongs to.

[0238] The SN can notify the UE of the information used by the UE to determine the uplink transmission node. This notification can be made using RRC signaling. For example, the notification can be included in an RRC Connection Reconfiguration message.

[0239] The information notified to the UE from the SN can be information from each node used by the UE to determine the uplink transmission node. The MN can also notify the SN of the MN's information regarding the UE's decision on the uplink transmission node. The SN, in turn, notifies the UE of the information used by the MN and its own nodes to determine the uplink transmission node. This configuration allows the SN to be used to set the uplink transmission node even in poor radio conditions at the MN, achieving low latency.

[0240] The information notified to the UE from the SN can be SN-specific information used by the UE to determine the uplink transmission node. Similarly, the MN-specific information used by the UE to determine the uplink transmission node can be notified to the UE from the MN. This configuration eliminates the need for communication between the MN and SN. By notifying the UE of this information from each node, the status of each node can be reflected to the UE in a timely manner.

[0241] The UE can determine the uplink transmission node. By using the information used to determine the uplink transmission node, the UE can decide which node to send uplink data to. For example, the MN informs the UE of the symbol duration information supported by both the MN and SN. Using the symbol duration information supported by each node, the UE determines the node supporting the shorter symbol duration as the UE's uplink transmission node. If the symbol durations are the same, the UE determines the NB of both nodes as the UE's uplink transmission node. For example, by configuring uplink data requesting low latency characteristics in this way, the UE can send uplink data to the node supporting the shorter symbol duration, thus enabling low-latency uplink data transmission.

[0242] As another example, the UE uses information about whether each node supports unlicensed transmission to determine which nodes support unlicensed transmission as the UE's uplink transmission nodes. If both nodes support unlicensed transmission, the UE will determine both nodes as the UE's uplink transmission nodes. For example, by configuring uplink data requesting low latency characteristics in this way, the UE can perform unlicensed transmission without requiring a transmission signal (SR) and can transmit uplink data with low latency.

[0243] As another example, the UE uses information about the latency supported by each node to determine the node that supports the shorter latency as the uplink transmission node. If the latency is the same, the UE will choose the node that supports both as the uplink transmission node. For example, by configuring uplink data requesting low latency in this way, the UE can transmit uplink data with low latency.

[0244] The UE can use the QoS requested by the communication service to determine the uplink transmission node. The UE can use information representing QoS, such as QoS distribution, QCI, desired latency, packet error rate, etc. For example, the UE uses information about the latency supported by each node to determine the node that supports a latency shorter than the desired latency as the UE's uplink transmission node. For example, by configuring uplink data that requests low latency characteristics in this way, the UE can transmit uplink data with low latency.

[0245] The UE can determine its method for identifying uplink transmitting nodes based on the uplink communication service. Alternatively, the method can be pre-determined statically using standards or other methods.

[0246] The method disclosed describes how the MN notifies the UE of information used by the UE to determine the uplink transmission node. The method for the MN to obtain information related to the SN from this information is as described above, applying the method for the MN to obtain the uplink transmission node determination information from the SN.

[0247] Figure 9 This illustrates an example of the process by which the UE determines the node to transmit uplink data. Figure 9 The process shown includes and Figure 8 The process shown has the same steps; therefore, the same step numbers are appended to the same steps, and common descriptions are omitted. DC setting processing is performed in step ST901. Figure 9 In the example, during the DC configuration process, information indicating the UE's decision on the method of uplink transmission using a node is communicated to the UE. Additionally, Figure 9 In the example with Figure 8 Similarly, a method for determining the uplink transmission node using SgNB's SCS information is shown.

[0248] In step ST902, the MgNB can notify the UE of information used to determine the uplink transmission node. The MgNB notifies the UE of the SCS information supported by its own node and the SCS information supported by the SgNB. The MgNB associates the information used to determine the SgNB with a candidate indicating whether it is an uplink transmission node and notifies the UE of this association. The information used to determine the SgNB may include, for example, node information, base station information, cell group information, or cell information.

[0249] In step ST903, the UE determines the node that supports a smaller SCS as the uplink transmission node. Figure 9 The example illustrates the case where the SgNB supports a smaller SCS than the MgNB. The UE determines the SgNB as the uplink transmission node.

[0250] At this point, the UE can use the QoS information of the communication service configured in the DC. The UE can determine the node supporting a smaller SCS as the uplink transmission node in a way that satisfies QoS requirements. For example, in the case where the UE requests low latency features in its communication service, the UE will determine the SgNB supporting a smaller SCS as the uplink transmission node.

[0251] In step ST806, the UE begins uplink transmission processing with the SgNB, which has been determined as the uplink transmission node. If uplink data is generated in the UE, then in steps ST807 to ST809, the UE transmits uplink data with the SgNB.

[0252] Therefore, in the DC, the UE can transmit uplink data to an SgNB designated as an uplink transmission node, regardless of the uplink data buffer capacity. For example, in the event of uplink data requests for low latency, even if the data is small, the UE can transmit uplink data to an SgNB that supports a smaller SCS. The capability map in the DC further enables low latency.

[0253] The method disclosed herein is a method by which the MN notifies the UE of information used to determine the uplink transmission node. Other methods are also disclosed. The MN may notify the UE of a threshold used to determine the uplink transmission node. The MN may notify the UE of a threshold for an indicator different from the uplink data buffer capacity in the UE, as the threshold for determining the uplink transmission node. The UE uses this threshold to determine the uplink transmission node.

[0254] Notification of the threshold used to determine the nodes for uplink transmission can be achieved using RRC signaling. For example, the threshold can be included in an RRC Connection Reconfiguration message. Alternatively, the threshold can be notified during DC configuration processing. The MN can notify information about the nodes used for uplink transmission when the metric is lower than the threshold (below the threshold) and when the metric is higher than the threshold (above the threshold). This allows for flexible configuration of the nodes used for uplink transmission.

[0255] Alternatively, nodes for uplink transmission can be pre-determined statically using standards, such as those specifying nodes that are below a threshold and those that are above a threshold. This requires less information for notification.

[0256] When the specified index is less than or above the threshold, the node used for uplink transmission can be MN, SN, or both MN and SN. Additionally, the information of the node used for uplink transmission can be the base station identifier. The information of the node used for uplink transmission can also be cell group information. The cell group information can be primary cell group (MCG) or secondary cell group (SCG) information. The information of the node used for uplink transmission can also be cell information, which can be the cell identifier. This indicates the cell used by the UE for uplink transmission.

[0257] The metrics used by the UE to determine the threshold for uplink transmission nodes can be, for example, information representing the QoS of the uplink communication service. These metrics could be, for example, the desired latency of the uplink communication service. Alternatively, these metrics could be, for example, the desired packet error rate of the uplink communication service. The MN can use the metrics requested by the uplink communication service to configure the uplink transmission nodes for the UE to obtain the desired QoS.

[0258] For example, the MN notifies the UE of a threshold for the desired latency of the uplink communication service, information about using the SN as the transmitting node if the desired latency is less than the threshold, and information about using the MN as the transmitting node if the desired latency is greater than the threshold. When the desired latency of the uplink data is less than the threshold, the UE sends the uplink data to the SN; when the desired latency is greater than the threshold, the UE sends the uplink data to the MN. For example, by setting uplink data that requests low latency characteristics in this way, the UE can send uplink data with low latency.

[0259] Figure 10 and Figure 11 This illustrates an example of the process by which the UE uses a threshold to determine the node for uplink transmission. Figure 10 and Figure 11 The example shown is an example of setting the threshold to the desired delay time. Figure 10 and Figure 11 Connect at the boundary line BL1011. Figure 10 and Figure 11 The process shown includes and Figure 8 The process shown follows the same steps; therefore, the same step numbers are appended to the same steps, and common descriptions are omitted. DC setting processing is performed in step ST1000. Figure 10 and Figure 11 In the example, during the DC setting process, information indicating that the UE uses a threshold to determine the method of uplink transmission using nodes is notified to the UE.

[0260] In step ST1001, the MgNB may notify the UE of the threshold value of the desired delay time as the threshold value for determining the nodes used for uplink transmission. The MgNB shall notify the UE of this notification, along with information on the nodes used for uplink transmission when the desired delay time is less than the threshold value, and information on the nodes used for uplink transmission when the desired delay time is greater than the threshold value. Figure 10 and Figure 11In the example, SgNB is used for uplink transmission when the desired delay time is less than the threshold, and both MgNB and SgNB are used for uplink transmission when the desired delay time is greater than the threshold. MgNB uses the SCS information obtained from SgNB in ​​steps ST802 and ST803 to determine the aforementioned node.

[0261] In step ST1002, the UE determines whether the desired delay time for the uplink communication service is less than the threshold notified from the MgNB. If the desired delay time is determined to be less than the threshold, in step ST1003, the UE decides to send uplink data to the SgNB based on the node information notified from the MgNB in ​​step ST1001. If uplink data is generated in the UE, then in steps ST1004 to ST1006, the UE performs uplink data transmission with the SgNB.

[0262] On the other hand, in step ST1002, if the UE determines that the desired delay time is above the threshold, in step ST1007, the UE decides to send uplink data to both the MgNB and the SgNB based on the node information notified from the MgNB in ​​step ST1001. If uplink data is generated in the UE, then in steps ST1008 to ST1010, the UE transmits uplink data with the MgNB, and in steps ST1011 to ST1013, the UE transmits uplink data with the SgNB.

[0263] Therefore, in the DC, regardless of the uplink data buffer capacity, the UE can transmit uplink data to nodes designated as uplink transmission nodes. For example, in the case of uplink data requesting low latency, even if the data is small, the UE can transmit uplink data to an SgNB that supports a smaller SCS. The capability map in the DC further enables low latency.

[0264] Multiple thresholds can also be used. The MN can notify the UE of multiple thresholds used to determine the node for uplink transmission. The UE uses these multiple thresholds to determine the node for uplink transmission. For example, the thresholds for the specified metrics can be set to T1 and T2. The MN can notify the UE of the following nodes: nodes used for uplink transmission when the specified metrics for uplink data are less than T1, nodes used for uplink transmission when they are greater than T1 and less than T2, and nodes used for uplink transmission when they are greater than T2. ​​The nodes used for uplink transmission can be flexibly set. Similarly, the nodes can be pre-determined statically using standards, etc. The amount of information required for notification is relatively small.

[0265] As another method of using multiple thresholds, a threshold can be set for each of the multiple metrics. Thresholds for multiple metrics can also be combined. Multiple metrics can be used to determine the uplink transmitting node.

[0266] As another method using multiple thresholds, multiple metrics can be set for nodes with hysteresis. Nodes transmitting uplink data can mitigate states that change rapidly over time.

[0267] It is disclosed that the MN will notify the UE of the threshold used to determine the uplink transmission node, but this threshold can be determined by the MN itself. The threshold can be flexibly set based on the load status in the MN and the characteristics requested by the communication service. Alternatively, the CN can determine the threshold and notify the MN. The MN then notifies the UE of the threshold. The threshold can be flexibly set considering the status of multiple nodes under the CN. Furthermore, the processing workload for determining this threshold in the MN can be reduced.

[0268] The threshold can be determined statically in advance using standards, etc. This reduces the signaling required to notify the UE from the MN. When using multiple thresholds, each threshold can be pre-assigned a number. This number is then communicated to the UE via the MN, allowing the UE to identify the threshold corresponding to that number. Additionally, indicators can be pre-associated with thresholds. For example, by communicating indicators to the UE from the MN, the UE can identify the threshold determined using standards, etc.

[0269] The method for changing the settings is disclosed. A method is disclosed whereby the MN notifies the UE of information related to the uplink transmitting node. However, the MN can change the uplink transmitting node and notify the UE of the nodes related to the changed uplink transmitting node. The UE uses the newly notified information related to the changed uplink transmitting node to send uplink data to the uplink transmitting node.

[0270] The method disclosed describes how the MN notifies the UE of the information used to determine the uplink transmission node. However, the MN can change the information used to determine the uplink transmission node and notify the UE of the changed information. The UE uses the newly received, changed information to determine the uplink transmission node.

[0271] The method disclosed describes how the MN notifies the UE of the threshold used to determine the uplink transmission node. However, the MN can change the threshold used to determine the uplink transmission node and notify the UE of the changed threshold. The UE uses the newly notified changed threshold to determine the uplink transmission node to decide on the uplink transmission node.

[0272] In cases where the CN determines the threshold, the CN can change the threshold and notify the MN of the changed threshold. The MN then notifies the UE of the changed threshold.

[0273] Therefore, settings can be changed. By changing the settings according to changes in the load status of MN and SN, wireless environment, etc., a more appropriate uplink transmitting node can be selected according to changes in conditions.

[0274] The aforementioned setting method can be configured. The MN decides which setting method to use and can notify the UE of the information indicating the setting method. The CN decides which setting method to use and can notify the MN of the information indicating the setting method. The MN then notifies the UE of the information indicating the setting method notified from the CN. If the MN needs to change the setting method, it simply notifies the UE of the new setting method. The UE applies the newly notified changed setting method.

[0275] This allows for the selection of more appropriate uplink transmitting nodes based on changes in circumstances. Instead of explicitly notifying the determination method, the method being selected can be indicated by communicating the information used in each method. This reduces the amount of information required for notification.

[0276] The above method can be appropriately applied to MC (multi-connectivity). Two or more SNs can be used. In cases such as a UN connected to one MN and two or more SNs, uplink transmission nodes can be configured from the aforementioned nodes.

[0277] The above method can be applied to fork bearers. That is, not only MCG fork bearers, but also SCG fork bearers. Furthermore, in the case of SCG fork bearers, the SN can determine the base station for uplink transmission.

[0278] Some or all of the above methods can be appropriately combined. For example, notifications of thresholds for determining uplink transmission nodes and notifications of information for determining uplink transmission nodes can be combined. The UE can be configured to use the information for determining uplink transmission nodes to decide which uplink transmission nodes to use when the index is lower than the threshold, and which uplink transmission nodes to use when the index is higher than the threshold. Thus, the UE does not perform uplink transmission on nodes that have been pre-notified or predetermined, but can perform uplink transmission on more appropriate nodes based on the status of each node.

[0279] The method, which includes determining which node to send uplink data based on the UE's uplink data buffer size, can be appropriately combined in part or in part. For example, the following example illustrates this: when the buffer capacity is less than a threshold, the determined node is chosen as the uplink transmission node; when the buffer capacity is above the threshold, the node supporting a shorter symbol period is chosen as the uplink transmission node. Even if the delay is somewhat large when the uplink data capacity is small, it is acceptable as long as the delay until the uplink data transmission is complete remains constant.

[0280] The method disclosed in Embodiment 1 allows for the selection of nodes as transmission targets for uplink data from the UE. Furthermore, the selection of nodes as transmission targets for uplink data from the UE can be based on the frame structure and functions supported by each node. By transmitting uplink data to the optimal node based on the status of each node, the QoS requested by the communication service can be obtained.

[0281] For example, regardless of the data size, the UE can utilize nodes with low-latency characteristics to send data requesting low-latency features. This reduces uplink data transmission latency.

[0282] NR requests support for URLLC (Ultra-Reliable Low-Latency Communication). Forked bearers can be supported for URLLC services. Forked bearers can be supported using the DRBs used for URLLC services. Through using forked bearers, throughput can be improved. Furthermore, the methods disclosed in Embodiment 1 can be applied to URLLC services. By applying the methods disclosed in Embodiment 1 to URLLC services, low latency characteristics can be obtained even when using forked bearers.

[0283] Therefore, communication services requesting low latency can be forked and carried out. This allows for increased throughput for low-latency communication. The result is the ability to achieve even lower latency.

[0284] Variation 1 of Implementation Method 1.

[0285] When using a Signal Controller (SN) for uplink data transmission, the UE must receive an uplink scheduling permission (sometimes simply called a permission) from the SN for uplink data transmission. First, the UE needs to send a Scheduler (SR) to the SN to obtain the uplink permission. The SR is sent at pre-set periodic intervals. Therefore, even if uplink data is generated, it cannot be transmitted directly; the UE must wait for the next SR to be sent.

[0286] Therefore, multiple processes must be performed from the generation of uplink data to the SN until the uplink data is transmitted to the SN, which can lead to significant delays. Thus, even if the method disclosed in Implementation 1 is applied to a communication service requesting low latency, thereby enabling the transmission of uplink data using the SN, a significant delay still occurs until the uplink data is transmitted to the SN.

[0287] The following are solutions to the above problems.

[0288] The SN performs unlicensed transmission. Unlicensed transmission can be configured within the SN. In other words, the SN supports unlicensed transmission. One or more cells within the SN can support unlicensed transmission. In a DC using SCG bearers, the SN can support unlicensed transmission.

[0289] Unlicensed transmission refers to SR and initial unlicensed UL transmission based solely on RRC settings. This is sometimes referred to as first-order unlicensed transmission. RRC settings include, for example, the allocation of time-frequency resources for UL transmission, UE-specific DMRS settings, and repetition counts. Other methods of unlicensed transmission include unlicensed UL transmission based on both RRC settings and L1 signaling. This is sometimes referred to as second-order unlicensed transmission. RRC settings include, for example, the period of resources used for UL transmission and power control-related information. Additionally, L1 settings include, for example, the allocation of time-frequency resources for UL transmission and information for activating / deactivating (or deactivating) uplink data transmission.

[0290] Therefore, by enabling unlicensed transmission in the SN, the uplink data transmission latency in the SN can be reduced, eliminating the need for SR reception and subsequent uplink licensed transmission by the SN.

[0291] In a DC using a forked bearer, the SN can support unlicensed transmission, achieving the same effect.

[0292] A method for enabling unlicensed transmission by the SN is disclosed. The settings for unlicensed transmission are performed by RRC. Therefore, RRC signaling is required. However, in the DC, the RRC signaling must be notified to the UE from the MN. There is a problem that the SN cannot notify the UE of its RRC settings for unlicensed transmission.

[0293] The following are solutions to the above problems.

[0294] The SN decides to transmit without permission. The SN performs RRC settings for unlicensed transmission. The SN notifies the MN of its unlicensed transmission RRC settings. The SN may notify the MN of information used to determine its own node. The SN's unlicensed transmission RRC settings may be notified in association with information used to determine its own node. For example, an identifier may exist as information used to determine its own node. The SN may notify the MN of information about the UE that is setting up unlicensed transmission. The SN's unlicensed transmission RRC settings may be notified in association with information used to determine the UE. For example, an identifier may exist as information used to determine the UE. Notifications from the SN to the MN may use X2 or Xn signaling.

[0295] The MN will notify the UE of the RRC settings of the SN received from the SN. Information used to determine the SN can be notified. By temporarily notifying the MN of the unlicensed transmission RRC settings configured by the SN, the DC can notify the UE of the unlicensed transmission RRC settings from the SN. The UE can receive the unlicensed transmission RRC settings from the SN. Using the unlicensed transmission RRC settings of the SN, the UE can implement unlicensed transmission for the SN.

[0296] Figure 12 and Figure 13 An example of a process for an SN to perform unlicensed transmission in a forked bearer is shown. Figure 12 and Figure 13 Connect at the boundary line BL1213. Figure 12 and Figure 13 The first unlicensed transmission is shown. Figure 12 and Figure 13 The process shown includes and Figure 8 The process shown has the same steps, therefore, the same step numbers are added to the same steps, and common descriptions are omitted.

[0297] In steps ST801 to ST809, within the DC, the UE transmits uplink data with the SgNB. In step ST1101, the SgNB decides to transmit without permission for the UE. For example, the SgNB may consider bearer-related information notified from the MgNB during DC configuration processing, the load status in the SgNB, and the usage status of radio resources when deciding to transmit without permission. For instance, if the uplink data communication throughput in the UE's bearer does not meet the request, but there are spare radio resources in the SgNB, the SgNB decides to transmit without permission for the UE.

[0298] In step ST1101, the SgNB, which determined unlicensed transmission for the UE, performs unlicensed transmission settings for the UE in step ST1102. In step ST1103, the SgNB notifies the MgNB of the unlicensed transmission settings. The SgNB notifies the MgNB of the unlicensed transmission settings in association with information about the UE for which the unlicensed transmission settings were determined, such as the UE's identifier. In step ST1104, the MgNB notifies the UE of the SgNB's unlicensed transmission settings.

[0299] In step ST1105, the UE configures the SgNB for unlicensed transmission. If uplink data is generated in the UE, the UE does not send an SR to the SgNB, but instead uses the unlicensed transmission configuration of the SgNB received in step ST1104 to send the uplink data to the SgNB in ​​step ST1106. The UE may also send a BSR at the same time.

[0300] Upon receiving the BSR, the SgNB sends an uplink grant to the UE in step ST1107. In step ST1108, the UE sends uplink data to the SgNB based on the received uplink grant. The UE may also send the BSR at the same time. Thus, uplink data transmission occurs between the UE and the SgNB.

[0301] Therefore, in the DC, the UE can receive the unlicensed transmission setting of the SgNB. Using the SgNB's unlicensed transmission setting, the UE can perform unlicensed transmission against the SgNB. Due to the removal of the SR and the accompanying initial uplink licensed transmission, the capability map achieves further low latency in uplink communication.

[0302] Similar to the second unlicensed transmission scenario, the RRC is used to publicly set part of the unlicensed transmission settings, while L1 is used to set other settings. The MN simply notifies the UE of the SN's unlicensed transmission RRC settings and L1 settings. The MN communicates with the UE using RRC signaling to notify the SN of the RRC settings and L1 signaling to notify the UE of the L1 settings. The L1 signaling can be included in the DCI from the MN to the UE for notification.

[0303] The SN's unlicensed transmission RRC and L1 settings can be communicated to the MN before being communicated from the MN to the UE. The SN can notify the MN of information used to determine its own node. The SN can also notify the MN of information about the UE that is configured for unlicensed transmission. The SN's unlicensed transmission RRC and L1 settings can be communicated in association with information used to determine the UE. Notifications from the SN to the MN can be made using X2 or Xn signaling.

[0304] Therefore, in cases such as the second unlicensed transmission, the DC can notify the UE of the unlicensed transmission RRC and L1 settings from the SN. The UE can receive the unlicensed transmission RRC and L1 settings from the SN. Using the unlicensed transmission RRC and L1 settings from the SN, the UE can implement unlicensed transmission against the SN.

[0305] Other methods for handling the second unlicensed transmission scenario are disclosed. The SN can notify the UE of its unlicensed transmission L1 setting. The SN's unlicensed transmission RRC setting is communicated to the UE from the MN using RRC signaling, while the SN's unlicensed transmission L1 setting is communicated from the SN to the UE using L1 signaling. The L1 signaling can be included in the DCI from the SN to the UE for notification.

[0306] The RRC setting for unlicensed transmission by the SN can be initiated by notifying the MN from the SN before notifying the UE from the MN. The notification from the SN to the MN can use X2 or Xn signaling.

[0307] Therefore, it is unnecessary to notify the SN of the L1 setting for unlicensed transmission via the MN. This reduces the latency required for Xn or X2 signaling from the SN to the MN, and the processing latency of the MN under high load conditions. Low latency allows for the execution of L1 settings from the SN to the UE. For example, from the SN to the UE, the activation / deactivation of unlicensed transmission can be appropriately executed with low latency.

[0308] Figure 14 and Figure 15 An example of a process for an SN to perform unlicensed transmission in a forked bearer is shown. Figure 14 and Figure 15 Connect at the boundary line BL1415. Figure 14 and Figure 15 The second unlicensed transmission is shown. Figure 14 and Figure 15 The process shown includes and Figure 12 and Figure 13 The process shown has the same steps, therefore, the same step numbers are added to the same steps, and common descriptions are omitted.

[0309] In step ST1105, the UE, having configured unlicensed transmission for the SgNB, receives L1 signaling from the SgNB. In step ST1201, the SgNB uses L1 signaling to notify the UE of the unlicensed transmission L1 configuration. As L1 signaling, a physical dedicated control channel that includes the L1 configuration within the DCI can be used. If uplink data is generated in the UE, the UE does not send an SR to the SgNB, but instead uses the unlicensed transmission configuration received from the SgNB in ​​step ST1104 and step ST1201 to send the uplink data to the SgNB in ​​step ST1106. The UE may also send a BSR at the same time.

[0310] Upon receiving the BSR, the SgNB sends an uplink grant to the UE in step ST1107. In step ST1108, the UE sends uplink data to the SgNB based on the received uplink grant. The UE may also send the BSR at the same time. Thus, uplink data transmission occurs between the UE and the SgNB.

[0311] Therefore, in the DC, the UE can receive both the RRC setting and L1 setting for unlicensed transmission from the SgNB. Using these SgNB unlicensed transmission settings, the UE can perform unlicensed transmission against the SgNB. Due to the removal of the SR and the accompanying initial uplink licensed transmission, the capability map achieves further low latency in uplink communication.

[0312] In the method described, the SN's unlicensed transmission RRC setting is notified to the UE via the MN. Other methods are disclosed. The SN can notify the UE of the SN's unlicensed transmission RRC setting. This reduces the latency required for Xn or X2 signaling from the SN to the MN, and the processing latency of the MN under high load conditions. The UE can then perform unlicensed transmission to the SN as quickly as possible.

[0313] The SN can notify both the UE and the MN of its unlicensed transmission RRC settings. Thus, the MN can recognize the unlicensed transmission RRC settings in the SN.

[0314] The SN can notify the UE of some or all of the RRC settings for unlicensed transmission from the SN. For example, parameters that need to be adjusted between the MN and the SN are notified to the UE via the MN, while parameters that do not need to be adjusted between the MN and the SN are notified to the UE via the SN.

[0315] For example, the uplink data transmission power setting information during unlicensed transmission can be notified from the SN to the MN, and then from the MN to the UE. For example, in the case of forked bearer, the MN can recognize the uplink data transmission power setting information of the SN, and therefore the MN can adjust its transmission power to the MN and its transmission power to the SN. For example, the transmission power to the MN can be set based on the power that the UE can transmit.

[0316] The MN can make adjustments with the SN. For an RRC setting received from the SN, the MN notifies the SN of a request to change that RRC setting. This notification may include the RRC setting requested by the MN. The SN makes the setting change and notifies the MN of the result. For example, to ensure the required power for transmission from the UE to the MN, the MN notifies the SN of the desired transmission power setting. The SN sets the uplink transmission power for unlicensed transmission based on the desired transmission power and notifies the MN of this setting.

[0317] The MN will notify the UE of the RRC setting result after adjustment between the MN and SN. Thus, the MN can make adjustments between the MN and SN.

[0318] The method for changing the settings is disclosed. The SN notifies the MN of the changed RRC settings for unlicensed transmission. The SN can notify both the RRC settings and L1 settings. The SN can notify information used to determine the local node. The SN can notify the UE of the settings change for unlicensed transmission. The changed settings can be notified in association with the information of the UE that made the settings change for unlicensed transmission. The MN notifies the UE of the changed RRC settings for unlicensed transmission. The MN notifies both the RRC settings and L1 settings. The RRC settings and L1 settings can be changed at the same time or at different time points. Flexible configuration is possible. Alternatively, only the changed settings or setting parameters can be notified from the SN to the MN.

[0319] The UE only changes the notified settings or setting parameters. This reduces the signaling or information volume required for notification. The UE re-notifies the changed RRC settings and / or L1 settings for unlicensed transmission to the SN, enabling unlicensed transmission to the SN.

[0320] The SN can notify the UE of changed L1 settings via unauthorized transmission. The SN can also notify the UE of RRC and L1 settings. RRC and L1 settings can be changed at the same or different time intervals, offering flexibility. Alternatively, the SN can notify the UE of only the changed settings or settings parameters. The UE only changes the notified settings or settings parameters, reducing the signaling or information volume required for notification.

[0321] The UE can implement unlicensed transmission for the SN by using the modified RRC settings and / or L1 settings that have been re-notified of unlicensed transmission to the SN.

[0322] The method for revoking the unlicensed transmission setting is disclosed. The SN sends a notification to the MN to revoke the unlicensed transmission setting. The SN may send information used to determine this node. The SN may send information about the UE that revoked the unlicensed transmission setting. The notification of revoking the unlicensed transmission setting can be associated with the information about the UE that revoked the unlicensed transmission setting. The MN sends a notification to the UE to revoke the unlicensed transmission setting. The UE that receives the notification revokes the unlicensed transmission setting to the SN. The SN sends a notification to the UE to revoke the unlicensed transmission setting. The UE that receives the notification revokes the unlicensed transmission setting to the SN.

[0323] The MN can request the SN to configure unlicensed transmission. Additionally, the MN can notify the SN of the requested unlicensed transmission configuration information. The MN can notify the SN of information used to determine the local node. The MN can notify the SN of information about the UE used to determine the unlicensed transmission configuration. The request for unlicensed transmission configuration can be notified in association with information about the UE used to determine the unlicensed transmission configuration. This notification can be made using Xn signaling or X2 signaling.

[0324] The unlicensed transmission configuration information can be RRC configuration parameters, L1 configuration parameters, or both. Furthermore, this unlicensed transmission configuration information can be part or all of the unlicensed transmission configuration parameters. This unlicensed transmission configuration information can indicate the first or second unlicensed transmission. The unlicensed transmission configuration information requested from the SN can be the unlicensed transmission settings set by the MN on this node.

[0325] It allows for flexible configuration of requests for the SN. For example, it can request more appropriate settings based on the load conditions of the MN and the radio wave propagation environment between the MN and the UE.

[0326] Based on the unlicensed transmission configuration request notified from the MN, the SN determines the unlicensed transmission configuration for the target UE in this node. The SN can configure unlicensed transmission. Alternatively, it can use the unlicensed transmission configuration information notified from the MN. By using the unlicensed transmission configuration information requested by the MN, it is possible to set a configuration that takes into account the load conditions of the MN, the radio wave propagation environment between the MN and the UE, etc.

[0327] Regarding the configuration information for unlicensed transmission not notified from the MN, it can be set by the SN. It can perform the necessary settings for unlicensed transmission and can implement unlicensed transmission for the UE.

[0328] The UE can notify the SN of information indicating the QoS requested by the communication service. The UE can also notify the SN of information indicating the QoS requested by the uplink communication service. Information used to determine the UE can also be notified. This information can be notified from the UE to the MN, and then from the MN to the SN.

[0329] Alternatively, the SN can use information indicating the QoS requested by the downlink communication service to derive information indicating the QoS requested by the uplink communication service. For example, the information indicating the QoS requested by the downlink communication service can be set to indicate the QoS requested by the corresponding uplink communication service. This reduces the signaling required for the UE to notify the SN of the QoS information.

[0330] The SN uses this information to determine whether unlicensed transmission is enabled in this node. For example, the SN uses the desired delay time requested by the UE's uplink communication service and the node's load status, such as resource unutilization, to determine whether unlicensed transmission is enabled for that UE.

[0331] For example, if the unused resource amount is greater than the specified value, the SN sets up no-license transmission for the UE. If the unused resource amount is less than the specified value and the desired latency is less than the specified time, the SN sets up no-license transmission for the UE. If the unused resource amount is less than the specified value and the desired latency is greater than the specified time, the SN does not set up no-license transmission for the UE. Therefore, the SN can determine whether to set up no-license transmission using the QoS information requested by the UE's communication service.

[0332] The SN, upon receiving a configuration request for unlicensed transmission from the MN, can notify the MN whether unlicensed transmission configuration has been implemented for the UE to which it is targeted. The SN can notify an acknowledgment (ack) or rejection (reject) response to the unlicensed transmission configuration request. The SN can also notify the MN of information used to determine its own node. The SN can further notify the MN of information used to determine the UE. The response to the unlicensed transmission configuration request can be associated with the information used to determine the UE.

[0333] If the SN has configured unlicensed transmission for the UE, an ACK notification is sent to the MN. The MN can recognize that the SN has configured unlicensed transmission for the UE. The method described above can be used to notify the MN or UE of the unlicensed transmission configuration from the SN. The UE can then use the SN's unlicensed transmission configuration to perform unlicensed transmission against the SN. Additionally, when the SN notifies the MN of the unlicensed transmission configuration in the SN, this notification can be set to ACK. This reduces signaling.

[0334] When the SN notifies the MN of "Reject," the notification may include reason information. Reason information could include, for example, that unlicensed transmission is not allowed, overload, or insufficient resources. Thus, the MN can identify the reason why the SN cannot configure unlicensed transmission for the UE being targeted. For example, the MN can switch the DC setting to another SN. Or, for example, the MN can switch UEs that have configured the DC using that SN and have a higher desired delay time to another SN.

[0335] When the SN notifies the MN of a Rejection, the notification can include a waiting timer. This allows the MN to request permission to send the configuration again from the SN after the waiting time has elapsed. This provides the system with greater flexibility.

[0336] Figure 16 and Figure 17 An example of a process for an SN to perform unlicensed transmission in a forked bearer is shown. Figure 16 and Figure 17 Connect at the boundary line BL1617. Figure 16 and Figure 17 This illustrates a scenario where MN requests permission to send settings to SN. Figure 16 and Figure 17 The process shown includes and Figure 12 and Figure 13 The process shown has the same steps, therefore, the same step numbers are added to the same steps, and common descriptions are omitted.

[0337] In steps ST801 to ST809, in the DC, the UE transmits uplink data with the SgNB. In step ST1301, the MgNB determines the unlicensed transmission settings in the SgNB for the UE. The MgNB determines the unlicensed transmission settings in the SgNB based on factors such as the UE's uplink communication QoS information, the SgNB's load status, and the radio resource usage status in the SgNB.

[0338] For example, the MgNB determines the unlicensed transmission settings requested from the SgNB based on the UE's uplink communication QoS information and the SgNB's load status. The MgNB can pre-obtain the UE's uplink communication QoS information and the SgNB's load status appropriately from both the UE and the SgNB. The UE's uplink communication QoS information can, for example, utilize... Figure 8 The disclosed method is used to obtain the load status. MgNB obtains the load status from SgNB. For example, MgNB requests the load status from SgNB, and SgNB notifies MgNB of its local load status. MgNB can then obtain the load status from SgNB by performing this process appropriately.

[0339] For example, if the desired uplink communication delay time for the UE is less than a specified value, the MgNB will not request unlicensed transmission configuration when the SgNB's load condition is higher than a specified value, but will request unlicensed transmission configuration when the SgNB's load condition becomes lower than the specified value. Therefore, the MgNB decides to request the unlicensed transmission configuration from the SgNB.

[0340] In step ST1301, an unlicensed transmission MgNB is determined for the UE within the SgNB. In step ST1302, an unlicensed transmission configuration is requested from the SgNB. The MgNB can notify the UE identified as the target and display the unlicensed transmission configuration request. In step ST1303, the SgNB performs unlicensed transmission configuration on the UE. In step ST1304, the SgNB notifies the MgNB of its response to the unlicensed transmission configuration request. The SgNB can notify the UE identified as the target and display the response to the unlicensed transmission configuration request. Figure 16 and Figure 17 This shows the case of a positive response (ack).

[0341] The SgNB includes the unlicensed transmission configuration information from the SgNB in ​​the response message notified in step ST1304 (a response message to the unlicensed transmission configuration request). Thus, the MgNB obtains the unlicensed transmission configuration from the SgNB for the UE. In step ST1104, the MgNB notifies the UE of the unlicensed transmission configuration information from the SgNB. In steps ST1105 to ST1108, the UE configures unlicensed transmission for the SgNB, and unlicensed transmission is performed between the UE and the SgNB when uplink data is generated in the UE.

[0342] Therefore, in the DC, the capability map achieves further low latency. Furthermore, the MgNB can request unlicensed transmission settings from the SgNB. Even in the MgNB acting as a C-Plane node, unlicensed transmission settings can be controlled for the UE. This avoids control complexity.

[0343] Unlicensed transmission settings can be implemented for both MN and SN. Unlicensed transmission settings can be implemented separately for MN and SN.

[0344] Figure 18 and Figure 19 An example of the process of unlicensed transmission between MN and SN in a forked bearer is shown. Figure 18 and Figure 19 Connect at the location of boundary line BL1819. Figure 18 and Figure 19 The process shown includes and Figure 16 and Figure 17 The process shown has the same steps, therefore, the same step numbers are added to the same steps, and common descriptions are omitted.

[0345] In step ST1400, DC setting processing is performed between UE, MgNB and SgMB. Figure 18 and Figure 19 In this process, the UE performs uplink communication between the MgNB and the SgNB. In steps ST1401 to ST1403, the UE performs uplink communication with the MgNB. In steps ST1404 to ST1406, the UE performs uplink communication with the SgNB.

[0346] In step ST1407, the MgNB determines the unlicensed transmission settings in this node for the UE. As a method of determination, for example, in... Figure 16 and Figure 17 The decision-making method disclosed herein can be applied by replacing SgNB with MgNB. MgNB, for example, determines the unlicensed transmission settings in MgNB based on the UE's uplink communication QoS information, MgNB load status, and radio resource usage in MgNB. In step ST1408, MgNB notifies the UE of its unlicensed transmission settings. In step ST1409, the UE configures the unlicensed transmission settings in MgNB. In steps ST1410 to ST1412, unlicensed transmission occurs between the UE and MgNB.

[0347] In step ST1301, the MgNB determines the unlicensed transmission configuration request in the SgNB in ​​response to the UE. As a determination method, for example, it applies... Figure 16 and Figure 17The decision method disclosed herein is sufficient. In step ST1301, the MgNB for unlicensed transmission in the SgNB is determined for the UE, and in step ST1302, the unlicensed transmission setting is requested from the SgNB. In steps ST1106 to ST1108, if uplink data is generated in the UE, unlicensed transmission is performed between the UE and the SgNB.

[0348] The order of the unlicensed transmission setting decisions in MgNB and SgNB can be reversed. The series of processes arising from each unlicensed transmission setting decision can also be reversed. Furthermore, the unlicensed transmission setting decisions in MgNB and SgNB can be performed simultaneously. The series of processes arising from each unlicensed transmission setting decision can be performed in parallel.

[0349] Therefore, in the DC, unlicensed transmission can occur between MgNB and SgNB. Through the use of two nodes, throughput can be increased. Furthermore, by utilizing unlicensed transmission between the two nodes, further low latency can be achieved, further increasing throughput.

[0350] The method disclosed involves the MN requesting the SN to configure unlicensed transmission. However, as an alternative, the MN can instruct the SN to configure unlicensed transmission. Similarly, the MN can notify the SN of the requested unlicensed transmission configuration information. The MN can also notify the SN of information used to determine the local node. The MN can notify the SN of information about the UE used to determine the unlicensed transmission configuration. The instruction to configure unlicensed transmission can be notified in association with the information used to determine the UE. This notification can be made using Xn signaling or X2 signaling.

[0351] The SN can notify the MN of its load information, uplink resource usage, and other relevant data. The SN can also notify the MN of information used to determine the location of this node. For example, the MN can use such information to determine whether to configure unlicensed transmission in the SN for the communication service of the target UE. If it decides to configure unlicensed transmission, it will send an instruction to the SN indicating whether to configure unlicensed transmission. If the UE has notified the MN of the QoS of its communication service, the MN can also use this QoS information to determine whether to configure unlicensed transmission in the SN.

[0352] The SN, upon receiving an unlicensed transmission configuration instruction from the MN, configures the UE to transmit without permission. If the MN notifies the UE of the unlicensed transmission configuration information, the SN can use this configuration received from the MN as the unlicensed transmission configuration. Therefore, the MN can control whether to implement the unlicensed transmission configuration in the SN for the UE with the configured DC.

[0353] The method for changing the settings is disclosed. The MN notifies the SN of the setting change request for unlicensed transmission. For example, if the UE's uplink communication does not meet the desired QoS, the MgNB determines to request a shorter unlicensed transmission setting for the SgNB. The MN may notify the SN of the UE's information regarding the unlicensed transmission setting change request. The setting change request may be associated with the UE's information. The SN may take this setting change request into account and change the unlicensed transmission setting for the UE being requested. The SN notifies the MN of the changed unlicensed transmission setting. The MN notifies the UE of the changed unlicensed transmission setting from the SN.

[0354] The UE only changes the notified settings or setting parameters. This reduces the signaling or information volume required for notification. The UE re-notifies the SN of the changed settings using unlicensed transmission to the SN, enabling unlicensed transmission to be implemented against the SN. The SN can notify the UE of the changed settings for unlicensed transmission. The UE re-notifies the SN of the changed settings using unlicensed transmission to the SN, enabling unlicensed transmission to be implemented against the SN.

[0355] The method for revoking the unlicensed transmission setting is disclosed. The MN notifies the SN of the revocation of the unlicensed transmission setting. For example, if the UE's uplink communication meets the desired QoS, the MgNB determines a revocation request for the unlicensed transmission setting to be made to the SgNB. The MN may notify the UE that made the unlicensed transmission setting revocation request. The revocation of the unlicensed transmission setting may be notified in association with the information of the UE that made the unlicensed transmission setting revocation request. The SN may take this setting revocation request into account and revoke the unlicensed transmission setting for the UE being targeted. The SN notifies the MN of the revocation of the unlicensed transmission setting. The MN notifies the UE of the SN of the revocation of the unlicensed transmission setting. The SN may notify the UE of the revocation of the SN of the revocation of the unlicensed transmission setting. The UE that receives this revocation notification revokes the unlicensed transmission setting from the SN.

[0356] The UE can request unlicensed transmission settings from the MN and / or SN. Additionally, the UE can request unlicensed transmission settings from the SN and / or MN. Information indicating a request for unlicensed transmission settings can be provided to notify the UE. The request for unlicensed transmission settings can include the UE's identifier. Alternatively, the identifier of the node requesting the unlicensed transmission settings can be included in the request. The node's identifier and the request for unlicensed transmission settings can be associated in the notification. This request can use RRC signaling. Alternatively, MAC signaling can be used. The request can be notified as quickly as possible with a low error rate. Alternatively, L1 / L2 signaling can be used. The request can be notified as quickly as possible.

[0357] A node that receives a configuration request for unlicensed transmission from the UE, and whose unlicensed transmission configuration is different from its own node, requests unlicensed transmission configuration from the node that configured it. For notifications between nodes, X2 or Xn signaling can be used.

[0358] For example, when the UE performs uplink communication with the SN, the UE determines whether the requested QoS (e.g., desired latency) for the communication is met. For instance, the UE can pre-determine the QoS (e.g., latency). If the requested QoS is not met, the UE requests a no-license transmission setting. Therefore, based on the communication conditions within the UE, it can request a no-license transmission setting from the appropriate node. This allows for flexible responses to changing communication conditions and ensures that the requested QoS is met.

[0359] Figure 20 and Figure 21 An example of a process for an SN to perform unlicensed transmission in a forked bearer is shown. Figure 20 and Figure 21 Connect at the location of boundary line BL2021. Figure 20 and Figure 21 This illustrates a scenario where the UE requests the MN to send settings without permission. Figure 20 and Figure 21 The process shown includes and Figure 18 and Figure 19 The process shown has the same steps, therefore, the same step numbers are added to the same steps, and common descriptions are omitted.

[0360] In step ST1501, the UE decides to request unlicensed transmission settings in the SgNB. The UE may use, for example, its uplink communication QoS information or the QoS value in actual communication to make this request. Alternatively, it may use support information from the MgNB and SgNB, such as SCS information indicating support.

[0361] When using QoS values ​​from actual communication, the UE can simply measure those values. For example, in actual communication, the UE can measure uplink packet data latency, packet loss, bit rate, etc. The UE compares the desired QoS information with the measured QoS values, and if the measured QoS values ​​do not meet the desired QoS information, it decides to request unlicensed transmission settings in the SgNB. The support information of the MgNB and SgNB can be used to determine which node's unlicensed transmission settings to request. The method by which the UE obtains the support information of the MgNB and SgNB is the method disclosed in Implementation Method 1, that is, the method by which the MgNB notifies the UE of the information used to determine the uplink transmission node.

[0362] Figure 20 and Figure 21 This illustrates a scenario where a request is made to configure unlicensed transmission in the SgNB. In step ST1502, the UE notifies the MgNB of the request to configure unlicensed transmission in the SgNB. The UE simply needs to notify the MgNB of its own information and the SgNB's information. The MgNB can then identify which UE is being requested to configure unlicensed transmission in which SgNB.

[0363] In step ST1502, the MgNB that receives the request for unlicensed transmission configuration from the SgNB determines whether to request unlicensed transmission configuration for the SgNB in ​​step ST1503. In step ST1302, the MgNB notifies the SgNB of the request for unlicensed transmission configuration. In step ST1503, the MgNB that determines the unlicensed transmission configuration for the UE requests the unlicensed transmission configuration from the SgNB in ​​step ST1302. In steps ST1106 to ST1108, if uplink data is generated in the UE, unlicensed transmission is performed between the UE and the SgNB.

[0364] Therefore, in the DC, the capability map achieves further low latency. Furthermore, the status of the UE, such as the actually measured QoS value, can be used to determine requests for unlicensed transmission settings. Thus, unlicensed transmission settings can be configured in a timely manner based on the status of the UE, and a transmission method corresponding to the status of the UE can be set.

[0365] The CN can request the MN and / or SN to configure unlicensed transmission. Additionally, the CN can request the SN and / or MN to configure unlicensed transmission. Information requesting the unlicensed transmission configuration can be displayed and communicated. The SN can communicate information used to determine the SN and / or MN. The request for unlicensed transmission configuration can include the identifier of the UE configuring unlicensed transmission. Furthermore, the identifier of the node requesting the unlicensed transmission configuration can be included in the notification. The node identifier and the request for unlicensed transmission configuration can be associated in the notification. Additionally, information related to the PDU session configuring unlicensed transmission and / or information related to QoS procedures can be included in the notification. This request can use S1 or NG-C signaling.

[0366] A node that receives a configuration request for unlicensed transmission from the CN, and whose configuration for unlicensed transmission differs from its own, requests the configuration for unlicensed transmission from the node that configured it. For notifications between nodes, X2 or Xn signaling can be used.

[0367] For example, when the UE performs uplink communication with the SN, the CN determines whether the requested QoS (e.g., desired delay time) for the communication is met. For instance, the CN can pre-determine the QoS (e.g., delay time) of the communication. If the requested QoS is not met, the CN requests a no-license transmission setting. Therefore, based on the communication status in the UE, the CN can request a no-license transmission setting from the appropriate node. This allows for flexible responses to changing communication conditions and ensures that the requested QoS is met.

[0368] Figure 22 and Figure 23 An example of the process of SN performing unlicensed transmission in a forked bearer is shown. Figure 22 and Figure 23 Connect at the boundary line BL2223. Figure 22 and Figure 23 This illustrates a scenario where CN requests MN to send settings without permission. Figure 22 and Figure 23 The process shown includes and Figure 20 and Figure 21 The process shown has the same steps, therefore, the same step numbers are added to the same steps, and common descriptions are omitted.

[0369] In step ST1601, the CN determines whether to request unlicensed transmission settings in the MgNB and SgNB. The CN may measure, for example, the actual uplink communication throughput of the target UE, and use the measurement results to determine the request. Additionally, support information from the MgNB and SgNB, such as SCS information indicating support, may be used.

[0370] For example, if the uplink communication throughput does not meet the desired value, the CN decides to request unlicensed transmission settings in both the MgNB and SgNB. The CN can use the support information from the MgNB and SgNB to determine which node's unlicensed transmission settings to request. As a method for the CN to obtain the support information from the MgNB and SgNB, a method can be applied whereby the MgNB pre-notifies the CN of the information used to determine the node for uplink transmission. This notification can use S1 signaling or NG-C signaling.

[0371] Figure 22 and Figure 23 This illustrates a scenario where a request is made to configure unlicensed transmission in both the MgNB and SgNB. In step ST1602, the CN notifies the MgNB of the request to configure unlicensed transmission in both the MgNB and SgNB. The CN simply notifies the MgNB of the information regarding the UE to be configured and the information regarding the SgNB. The MgNB can then identify which UE is being requested to configure unlicensed transmission in which SgNB.

[0372] In step ST1602, CN may notify MgNB and SgNB of some or all of their unlicensed transmission configuration information. For example, CN may set the period and offset error of the unlicensed transmission resources to be the same for both MgNB and SgNB, and notify them of this setting. As a result, the timing of unlicensed transmission by MgNB and SgNB becomes the same, which can suppress the increase in delay caused by timing differences.

[0373] In step ST1602, the MgNB, having received requests for unlicensed transmission settings from both the MgNB and SgMN, performs unlicensed transmission settings within the MgNB. Furthermore, in step ST1603, the MgNB decides to request unlicensed transmission settings from the SgNB. In step ST1302, the MgNB notifies the SgNB of the unlicensed transmission settings request.

[0374] In step ST1304, the MgNB receives information identifying the UE as the target and displays an ACK from the SgNB. The MgNB also receives unlicensed transmission configuration information from the SgNB. In step ST1604, the MgNB notifies the UE of its own unlicensed transmission configuration information and the SgNB's unlicensed transmission configuration information.

[0375] Upon confirming the success of the notification in step ST1604, the MgNB sends an unlicensed transmission configuration completion notification to the CN in step ST1605. This completion notification may include information about the UE identified as the target and information about the node that performed the unlicensed transmission configuration. Thus, the CN recognizes that unlicensed transmission configuration has been implemented in both the MgNB and SgNB.

[0376] In step ST1604, the UE is configured to perform unlicensed transmission for the MgNB and SgNB upon receiving unlicensed transmission requests from the MgNB and SgNB. If uplink data is generated in the UE, unlicensed transmission is performed between the UE and the MgNB in ​​steps ST1607 to ST1609, and between the UE and the SgNB in ​​steps ST1610 to ST1612.

[0377] Therefore, in the DC, the capability graph achieves further low latency. Additionally, the CN sets unlicensed transmission configuration requests for each node, along with part or all of these unlicensed transmission settings, thereby enabling the system to reduce uplink communication latency.

[0378] The CN can notify the MN or SN of the unlicensed transmission settings in each node. The CN can notify the node to which the unlicensed transmission settings are requested, either together with or within the unlicensed transmission settings request notified from the CN to the MN or SN. If the node that sets the unlicensed transmission settings is different from the node that sets them, the node that receives the unlicensed transmission settings request from the CN can notify the node that sets the unlicensed transmission settings.

[0379] The CN can notify some or all of the unlicensed transmission settings. Furthermore, when notifying multiple nodes of the unlicensed transmission settings, the CN can set some or all of the unlicensed transmission settings to be the same for multiple nodes and notify them of that setting. Nodes notified of the unlicensed transmission settings by the CN will take this setting into account when configuring their own unlicensed transmission settings.

[0380] For example, the CN sends an unlicensed transmission configuration request to both the MN and SN. At this time, the unlicensed transmission period is set to be the same in both the MN and SN. This ensures that the uplink data transmission delay is set to the same level in both the MN and SN. The CN can then perform unified control over the nodes of the RAN within its coverage area.

[0381] The MN or SN can notify the UE or CN of a response to the request from the UE or CN regarding the unlicensed transmission setting. The notification may include the identifier of the node that requested the unlicensed transmission setting. The node that requested the unlicensed transmission setting may be notified in association with the response to the request for the unlicensed transmission setting in that node.

[0382] The MN or SN can notify the UE, the target UE, whether or not unauthorized transmission has been configured, as a response to the request for unauthorized transmission configuration. The MN or SN can provide an acknowledgment (ack) or rejection (reject) response. The MN or SN can also provide information used to identify the target UE. The response to the request for unauthorized transmission configuration can be associated with the information used to identify the UE.

[0383] Regarding the response to the request for unlicensed transmission settings between the MN and SN, the method described above can be applied. The node receiving the response to the request for unlicensed transmission settings can then notify the UE or CN of the response. This achieves the same effect.

[0384] The method disclosed in Variation 1 of Embodiment 1 can be applied to bearer types using SCG. That is, not only MCG forked bearers and SCG forked bearers, but also SCG bearers can be applied to the method disclosed in Variation 1 of Embodiment 1. Unlicensed transmission can be performed in the SN in the SCG bearer. In addition, the method disclosed in Variation 1 of Embodiment 1 can also be appropriately applied to MC (multi-connectivity). Two or more SNs can be used. In the case where the UE is connected to one MN and two or more SNs, unlicensed transmission can be configured in one or more SNs within the range of the number of connected SNs.

[0385] By adopting the method disclosed in Variation 1 of Embodiment 1, unlicensed transmission can be performed in the SN when DC or MC is set. By enabling unlicensed transmission in the SN, the reception of SR and subsequent uplink licensed transmission performed by the SN can be eliminated, thereby reducing the uplink data transmission delay time in the SN.

[0386] Unlicensed transmission can also be performed within a Carrier Aggregation (CA). Unlicensed transmission can be configured using a CA. In other words, unlicensed transmission is supported using a CA. Unlicensed transmission can be supported in one or more CCs (cells) within a CA.

[0387] In CA (Cell-Oriented Communication), SR (Signal Transmission) is transmitted in designated cells. For example, SR is transmitted in PCell, PUCCH SCell, and SPCell. The cell configured for unlicensed transmission does not necessarily have to be a cell capable of transmitting SR. Unlicensed transmission configuration is only required for cells transmitting uplink data. Since it is not limited to cells capable of transmitting SR, unlicensed transmission can be configured for UEs in cells with good radio conditions. By implementing unlicensed transmission in cells with good radio conditions, UEs can achieve both low latency and high throughput in uplink communication.

[0388] The MN notifies the UE of the unlicensed transmission settings for one or more cells. The MN then notifies each node (MN and SN) of the unlicensed transmission settings for each cell. The MN notification is used to determine the cell information and the unlicensed transmission settings. The MN can pre-obtain the unlicensed transmission settings for each cell from the SN. This acquisition method can apply the method disclosed in the unlicensed transmission settings method in the DC described above.

[0389] Each node sends an unlicensed transmission configuration notification for one or more cells to the UE. The MN sends an unlicensed transmission configuration notification for each cell to its own node. The SN sends an unlicensed transmission configuration notification for each cell to its own node.

[0390] The RRC settings for unlicensed transmission in each cell can be notified to the UE via RRC signaling from the MN or each node. The L1 settings for unlicensed transmission in each cell can be notified to the UE via L1 signaling from each cell. The L1 settings can be included in the DCI for notification.

[0391] The cell notifies the UE of the L1 settings for unlicensed transmission from one or more other cells. This notification can be achieved by including the information about the cell used to determine the unlicensed transmission settings along with the L1 settings in the DCI. Therefore, if the UE receives the control channel of the determined cell in advance, it does not need to always receive the control channels of all cells. This achieves low power consumption for the UE.

[0392] In the case of CA (Cellular Access Control), cell scheduling for CA is handled by the MAC addresses of each node. Therefore, even if a cell notifies other cells of its L1 settings, it can promptly reflect the settings of unlicensed transmission radio resources used by other cells, as well as the activation / deactivation of unlicensed transmission. This improves the efficiency of radio resource utilization.

[0393] The UE can determine which cell among those configured for unlicensed transmission should transmit data. With L1 configuration enabled, the UE can select the cell from the active cells to transmit data. For example, the UE can measure the downlink path loss of each cell and determine which cell will transmit uplink data with the lowest path loss.

[0394] The decision of which cell to transmit data in among the cells designated for unlicensed transmission can be made by the node. Each node can determine which cell to transmit data to. Only the determined cell will send an activation notification to the UE using L1 settings. The determined cell will send an invalidation notification to other cells using L1 settings. Thus, the node can determine which cell the UE should transmit uplink data to. For example, the node can receive uplink probe signals from the UE to each cell and measure the uplink communication quality of each cell, determining which cell will transmit uplink data to the one with the best uplink communication quality.

[0395] Information about the cell from which uplink data transmission will be determined can be configured. A node can include this information in its RRC settings and notify the user using RRC signaling. Alternatively, it can include this information in its MAC CE and notify the user using MAC signaling. Unlicensed transmission can be dynamically configured. Furthermore, due to the application of HARQ, reception errors can be reduced. Alternatively, information about the cell from which uplink data transmission will be determined can be included in its L1 settings and notified the user using L1 signaling. Unlicensed transmission can be dynamically configured. For UEs that have not performed HARQ, unlicensed transmission can be configured immediately.

[0396] Unlicensed transmission settings can be partially or entirely set to be the same across multiple cells. This same unlicensed transmission setting can be common across all cells. For example, the timing of unlicensed transmission resources can be made different across multiple cells. This allows uplink data communication to begin in the shortest possible time in a cell where unlicensed transmission resources are available, starting from the timing when uplink data is generated in the UE. It also further reduces uplink communication latency.

[0397] Therefore, even within a CA (Cellular Access Control), unlicensed transmission can be performed in one or more cells. For example, a UE can initiate data communication in a cell with good radio wave propagation conditions. Furthermore, uplink communication can be initiated not only in cells where SR (Signal Transmission) is permitted, but also in other cells.

[0398] Implementation method 2.

[0399] In uplink communication where low latency is required, unlicensed transmission can be configured to achieve low latency. However, for communication services such as URLLC that require both low latency and high reliability, unlicensed transmission alone is insufficient.

[0400] The following are solutions to the above problems.

[0401] In packet duplication, where identical packets are copied and transmitted using a DC, unlicensed transmission can be configured. Unlicensed transmission can be configured in the MN (Medium). Unlicensed transmission can also be configured in the SN (Signal Array). Alternatively, unlicensed transmission can be configured in either the MN or the SN. Packet duplication settings can include packet duplication configuration processing.

[0402] For uplink communication configured with unlicensed transmission, packet replication can be configured. With packet replication implemented, unlicensed transmission can be configured even within the SN (Signal Node). Therefore, by configuring both packet replication and unlicensed transmission, both low latency and improved reliability can be achieved.

[0403] In packet replication using DC, the SN may not recognize the packet replication settings when configuring packet replication between the MN and UE. The SN can perform the same processing as normal packet data transmission and reception. On the other hand, as mentioned above, the configuration for unlicensed transmission requires RRC settings. Therefore, in packet replication using DC, when unlicensed transmission needs to be configured, the SN cannot recognize whether the unlicensed transmission setting is required, resulting in the problem that the SN cannot implement the unlicensed transmission setting.

[0404] The following are solutions to the above problems.

[0405] The MN requests the SN to configure unlicensed transmission. In the packet replication configuration, the MN requests the SN to configure unlicensed transmission. The SN notifies the MN of the unlicensed transmission configuration. The MN notifies the UE of the unlicensed transmission configuration set in this node and the SN's unlicensed transmission configuration. The method disclosed in Variation 1 of Embodiment 1 can be appropriately applied from the MN's request for unlicensed transmission configuration from the SN and the method related to the unlicensed transmission configuration between the MN, SN, and UE.

[0406] For example, instead of MN requesting SN to set up unlicensed transmission, you can apply the method where MN instructs SN to set up unlicensed transmission.

[0407] Therefore, the SN can identify whether unlicensed transmission is required, and unlicensed transmission can be configured within the SN. This allows for unlicensed transmission to be configured in packet replication using the DC, resulting in low latency and high reliability.

[0408] The MN can request the SN to set the timing of the unlicensed transmission resource in the same way. The timing of the unlicensed transmission resource can be the period and offset of the unlicensed transmission resource. The MN can notify the SN of these parameters in the unlicensed transmission configuration parameters of this node. The SN can set these parameters.

[0409] This allows the transmission timing from the UE to both nodes to be consistent, thus reducing the increase in latency caused by different transmission timings to each node.

[0410] The MN can request unlicensed transmission resources from the SN in different timings. The MN can set different values ​​for the timing-related parameters in its unlicensed transmission settings and notify the SN of these settings. The SN can set these parameters.

[0411] When the transmission timing to each node is the same, the UE's transmission power must be allocated to each node, which can lead to a reduction in the transmission power to the nodes. By making the transmission timing to each node different, the reduction in uplink transmission power from the UE to each node can be suppressed.

[0412] The MN can request unlicensed transmission resources from the SN in different ways within a specified range. The MN can set the timing-related parameters in its unlicensed transmission settings to different values ​​within a specified range and notify the SN of these settings. The SN can set these parameters.

[0413] Therefore, it is possible to suppress the reduction of uplink transmission power to each node, and by suppressing the transmission timing to each node within a specified range, the latency can be reduced.

[0414] In the MN, if packet replication needs to be configured for uplink communication with unlicensed transmission enabled, the SN cannot recognize whether unlicensed transmission needs to be configured, thus causing the problem that the unlicensed transmission configuration cannot be implemented in the SN.

[0415] The following are solutions to the above problems.

[0416] The MN notifies the UE that packet duplication using the DC is used for uplink communication configured with unlicensed transmission. Additionally, the MN requests unlicensed transmission configuration from the SN. The MN may notify the SN of the unlicensed transmission configuration instruction. The SN notifies the MN of the unlicensed transmission configuration. The MN notifies the UE of the unlicensed transmission configuration set in this node and the SN's unlicensed transmission configuration. The method disclosed in Variation 1 of Embodiment 1 can be appropriately applied to the methods related to unlicensed transmission configuration between the MN, SN, and UE, such as the MN's request for unlicensed transmission configuration from the SN.

[0417] Therefore, the SN can identify whether unlicensed transmission is required, and unlicensed transmission can be configured within the SN. Thus, for uplink communication where unlicensed transmission is configured in the MN, packet replication can be set up, achieving both low latency and high reliability.

[0418] Figures 24-26 This illustrates an example of the process for setting up unlicensed transmission in group replication. Figures 24-26 The nodes are connected at boundary lines BL2425 and BL2526. In step ST1701, the MgNB determines that uplink packet replication using a forked bearer is used for the UE. In step ST1702, the MgNB performs configuration processing for the DC using the forked bearer between the UE and the SgNB. In step ST1703, the MgNB notifies the UE of the uplink packet replication configuration. RRC signaling can be used for this notification. In step ST1704, the MgNB notifies the UE of the packet replication ack. MAC signaling can be used for this notification.

[0419] The UE that receives the packet replication action in step ST1704 starts packet replication in step ST1705. The UE that has started packet replication replicates uplink data and transmits uplink data to the MgNB and SgNB. Uplink data transmission to the MgNB occurs in steps ST1706 to ST1708, and uplink data transmission to the SgNB occurs in steps ST1709 to ST1711.

[0420] In step ST1712, the SgNB sends the uplink data received from the UE to the MgNB. This uplink data transmission can use either the S1 interface or the Xn interface. In step ST1713, the MgNB compares the uplink data received from the MgNB with the uplink data received from the SgNB and removes duplicate uplink data. Thus, uplink packet replication using the forked bearers of the MgNB and SgNB is performed.

[0421] In step ST1714, MgNB determines the unlicensed transmission settings for both MgNB and SgNB. This determination method applies... Figure 16 and Figure 17 The disclosed decision method is sufficient. When setting unlicensed transmission for uplink data with packet replication, the unlicensed transmission settings for both the MgNB and SgNB can be determined. In step ST1715, the MgNB notifies the SgNB of the unlicensed transmission setting. The MgNB may notify the SgNB of the information of the UE identified as the target. The MgNB may notify the SgNB of part or all of the unlicensed transmission settings.

[0422] The MgNB can notify the SgNB of the period and offset of the unlicensed transmission resources as unlicensed transmission configuration information. By matching the period and offset of the unlicensed transmission resources of the SgNB and MgNB, the increase in latency caused by the timing difference of the unlicensed transmission resources of the SgNB and MgNB can be suppressed.

[0423] Upon receiving an unlicensed transmission configuration instruction from the MgNB, the SgNB performs unlicensed transmission configuration in step ST1716. This unlicensed transmission configuration is accompanied by the preservation of radio resources, but the SgNB, upon receiving the instruction from the MgNB, prioritizes other UEs and performs the unlicensed transmission configuration for the target UE. In step ST1717, the SgNB notifies the UE of its response to the unlicensed transmission configuration instruction from the MgNB. Here, the SgNB notifies an ACK. The SgNB notifies the UE of the identified target UE along with its own unlicensed transmission configuration. In step ST1718, the MgNB notifies the UE of its own unlicensed transmission configuration and the SgNB's unlicensed transmission configuration.

[0424] In step ST1719, the UE performs unlicensed transmission settings for both the MgNB and SgNB. In steps ST1720 to ST1722, the UE performs unlicensed transmission for the MgNB. Additionally, in steps ST1723 to ST1725, the UE performs unlicensed transmission for the SgNB. In step ST1726, the SgNB transmits the uplink data received from the UE to the MgNB. In step ST1727, the MgNB deletes duplicate uplink data.

[0425] In the example above, MgNB notifies SgNB of the indication to configure unlicensed transmission, but MgNB can also notify SgNB of a request to configure unlicensed transmission. Furthermore, SgNB sends an ACK notification to MgNB, but SgNB can also send a Reject notification to MgNB. For example, if SgNB receives a request to configure unlicensed transmission but cannot configure it due to insufficient resources on its node, it will notify MgNB of a Reject notification. Insufficient resources can be included as a reason in the notification.

[0426] If a MgNB that receives a Reject notification decides to configure unlicensed transmission only for its own node, it can notify the UE of the unlicensed transmission configuration only.

[0427] If the MgNB again requests unlicensed transmission settings from the SgNB, it can notify the SgNB of this request. If the resource shortage has been resolved, the SgNB will include its unlicensed transmission settings in the Ack (Acceptance Message) and then notify the MgNB. The MgNB can notify the UE of the unlicensed transmission settings of both the MgNB and the SgMN. If the MgNB's unlicensed transmission settings remain unchanged, it can notify only the SgNB of the unlicensed transmission settings.

[0428] Therefore, unlicensed transmission is possible in uplink packet replication using forked bearers of MgNB and SgNB. This also enables further low latency during packet replication, resulting in high reliability and low latency characteristics.

[0429] Uplink packet replication configuration can be performed during DC configuration processing. For example, this information can be communicated by including the uplink packet replication configuration information in the RRC connection reconfiguration message sent from the MN to the UE. Upon receiving the RRC connection reconfiguration message during DC configuration processing, the UE performs both DC configuration and uplink packet replication configuration. This reduces RRC signaling traffic.

[0430] Figures 27-29 This illustrates an example of the process for configuring packet replication for uplink communication with unlicensed transmission. Figures 27-29 Connect at the positions of boundary lines BL2728 and BL2829. Figures 27-29 The process shown includes and Figure 24 and Figure 26 The process shown has the same steps, therefore, the same step numbers are added to the same steps, and common descriptions are omitted.

[0431] In step ST1801, the MgNB notifies the UE of its unlicensed transmission configuration. In step ST1802, the UE performs unlicensed transmission configuration for the MgNB. In steps ST1803 to ST1805, if uplink data is generated in the UE, unlicensed transmission is performed between the UE and the MgNB.

[0432] In step ST1806, the MgNB determines that packet replication using a forked bearer is used. In step ST1714, the MgNB determines the unlicensed transmission settings for both the MgNB and the SgNB. Having determined the use of packet replication using a forked bearer in step ST1806, the MgNB performs DC configuration processing between the UE and the SgNB in ​​step ST1807. After the DC configuration processing in step ST1807, in step ST1715, the MgNB notifies the SgNB of the unlicensed transmission setting indication.

[0433] In steps ST1716 to ST1719, the UE is configured for unlicensed transmission by the MgNB and SgNB. The MgNB changes its unlicensed transmission configuration, and in step ST1718, the MgNB can notify the UE of the changed unlicensed transmission configuration. Having notified the MgNB and SgNB of the unlicensed transmission configuration in step ST1718, the MgNB notifies the UE of the uplink packet replication configuration in step ST1808. RRC signaling can be used for this notification. In step ST1809, the MgNB notifies the UE of the packet replication ACK. MAC signaling can be used for this notification.

[0434] In step ST1809, the UE that receives the packet copy from the MgNB begins uplink data copying in step ST1810. If uplink data is generated in the UE, uplink data packet copying is performed. In steps ST1720 to ST1722, unlicensed transmission is performed between the UE and the MgNB. In addition, in steps ST1723 to ST1725, unlicensed transmission is performed between the UE and the SgNB.

[0435] Therefore, a setting allows for packet replication in uplink communication where unlicensed transmission is configured. Thus, for uplink communication that achieves low latency through unlicensed transmission, packet replication further enhances reliability. This results in both low latency and high reliability.

[0436] Unlicensed transmission configuration can be performed during DC configuration processing. For example, the unlicensed transmission configuration request and the unlicensed transmission configuration indication can be included in an Xn / X2 message notified from the MN to the SN, such as an SgNB modification request message. Alternatively, unlicensed transmission configuration information can be included in an Xn / X2 message notified from the SN to the MN, such as an SgNB modification request acknowledge message. This method can be applied to the method disclosed in Variation 1 of Embodiment 1. This reduces the Xn / X2 signaling volume.

[0437] Alternatively, for example, this information can be communicated by including the unlicensed transmission configuration information in the RRC connection reconfiguration message notified to the UE from the MN. The UE that receives the RRC connection reconfiguration message during DC configuration processing performs DC configuration and unlicensed transmission configuration. This method can be applied to the method disclosed in Variation 1 of Embodiment 1. This reduces RRC signaling traffic.

[0438] Uplink packet replication configuration can be performed during DC configuration processing. For example, this information can be communicated by including the uplink packet replication configuration information in the RRC connection reconfiguration message sent from the MN to the UE. Upon receiving the RRC connection reconfiguration message during DC configuration processing, the UE performs DC configuration and uplink packet replication configuration. This reduces RRC signaling traffic.

[0439] Uplink packet replication configuration can be performed during the unlicensed transmission configuration process. For example, this information can be communicated by including the uplink packet replication configuration information in the RRC signaling used to notify the UE of the unlicensed transmission configuration from the MN. The UE that receives the RR signaling for unlicensed transmission configuration performs both the unlicensed transmission configuration and the uplink packet replication configuration. This reduces the amount of RRC signaling.

[0440] In the unlicensed transmission configuration, MAC signaling can be used to activate / deactivate the unlicensed transmission configuration. Activation / deactivation information for unlicensed transmission can be configured for each node. This information can be included in the MAC CE. The MN notifies the UE of the activation / deactivation of the unlicensed transmission configuration via the MAC CE. The SN can also notify the UE of the activation / deactivation of the unlicensed transmission configuration via the MAC CE.

[0441] Upon receiving activation / deactivation information for unlicensed transmission settings from each node, the UE implements unlicensed transmission settings for each node. By setting activation / deactivation information for unlicensed transmission settings for each node in MAC signaling, the unlicensed transmission settings for the UE can be implemented dynamically and in a timely manner. This reduces unnecessary use of radio resources.

[0442] Packet replication activation / deactivation settings are configured via MAC signaling. This information can be communicated by including the unlicensed transmission of activation / deactivation information from each node within a MAC signaling message containing the activation / deactivation settings for packet replication. By utilizing the same MAC signaling for notification, signaling volume can be reduced.

[0443] Figure 30 and Figure 31 This is a diagram illustrating an example of the process of using the same signaling to notify the packet replication act and the unlicensed transmission act of the packet replication and unlicensed transmission settings. Figure 30 and Figure 31 Connect at the location of boundary line BL3031. Figure 30 and Figure 31 The process shown includes and Figures 27-29 The process shown has the same steps, therefore, the same step numbers are added to the same steps, and common descriptions are omitted.

[0444] In step ST1901, the MgNB determines that packet replication using a forked bearer is used for the UE, and at this time, it determines the unlicensed transmission settings for both the MgNB and the SgNB. In step ST1902, the MgNB performs DC setting processing between the UE and the SgMB. After the DC setting processing in step ST1902, in step ST1715, the MgNB notifies the SgNB of the unlicensed transmission setting indication.

[0445] In steps ST1716 to ST1718, unlicensed transmission settings for the MgNB and SgNB are configured for the UE. In step ST1718, the MgNB notified of the unlicensed transmission settings for the MgNB and SgNB notifies the UE of the uplink packet replication settings in step ST1808. In step ST1903, the MgNB uses the same signaling to notify the UE of the activation of packet replication and the activation of the unlicensed transmission settings for the MgNB and SgNB. MAC signaling can be used for this notification.

[0446] For example, a notification can be sent by including an active MAC CE containing packet copying and an active MAC CE containing unlicensed transmission settings for MgNB and SgNB in ​​the same MAC PDU. Upon receiving the activation of packet copying and the activation of unlicensed transmission settings for MgNB and SgNB in ​​step ST1903, the UE performs unlicensed transmission settings for MgNB and SgNB in ​​step ST1904 and begins packet copying.

[0447] If uplink data is generated in the UE, uplink data packet replication is performed. In steps ST1720 to ST1722, unlicensed transmission is performed between the UE and the MgNB. In addition, in steps ST1723 to ST1725, unlicensed transmission is performed between the UE and the SgNB.

[0448] This results in low latency and high reliability. Furthermore, by utilizing MAC CE to activate / deactivate unlicensed transmission settings, dynamic control can be achieved when the MgNB initiates or stops unlicensed transmission for the UE. This improves the efficiency of radio resource utilization. Additionally, by using the same MAC signaling to notify both packet replication activation / deactivation and unlicensed transmission settings, signaling load can be reduced.

[0449] In packet replication where the same packets are copied and transmitted using CA, unlicensed transmission can be configured. Unlicensed transmission can be configured within the cell where packet replication is performed. Packet replication settings can include packet replication configuration processing.

[0450] For uplink communication configured to transmit without permission, packet replication (CA) can be configured. With packet replication enabled, unlicensed transmission can be configured even within the cell where packet replication is performed.

[0451] The node will send an unlicensed transmission configuration notification to the UE for the cell in which packet replication has been performed. This notification method may be appropriately applied to any of the methods disclosed for configuring unlicensed transmission in packet replication utilizing the aforementioned DC.

[0452] Therefore, unlicensed transmission can be configured in packet replication (CA). Packet replication (CA) can be configured for uplink communication with unlicensed transmission enabled. This results in low latency and high reliability. Furthermore, low latency and high reliability can be achieved using a single node.

[0453] Implementation method 3.

[0454] In uplink priority transmission (refer to Non-Patent Document 14 (R1-1712747)), the UE performing priority transmission sends a SR to the gNB. The UE performing priority transmission may be, for example, a UE performing URLLC communication. The gNB notifies the priority UE of the situation indicating that priority communication has occurred. This notification information may include information related to frequency resources used for priority transmission. This notification information may include information related to time resources. This notification information may include information related to power resources. The priority UE may be, for example, a UE performing eMBB communication.

[0455] The gNB can configure all or some of its subordinate UEs to receive information indicating a priority communication situation. A UE can use this configuration to begin receiving information indicating a priority communication situation. The UE receiving priority can be any UE that has this configuration enabled. The same configuration can be applied to the following UEs.

[0456] The prioritized UE can use this notification to reduce uplink transmission power on the frequency and / or time resources used for priority transmission. Alternatively, the prioritized UE can stop uplink transmission power on those resources. This improves the reliability of priority communication.

[0457] The prioritized UE may not transmit uplink data scheduled for transmission on the frequency and / or time resources where priority transmission is required. This reduces the processing load on both the UE and the gNB. As another example, the UE may use resources other than the specified resources to transmit the uplink data. For instance, the UE may transmit the uplink data with a time offset backward from the time resources for priority communication. The UE may also abort the transmission of uplink data that was not completed within the scheduling clearance indicated by the gNB. The decision to not transmit the uplink data as described above, and / or to use resources other than the specified resources, can be determined using the gNB's decoding characteristics. Improving the HARQ decoding characteristics during uplink transmission enhances the reliability of uplink communication for the prioritized UE.

[0458] As another example, the prioritized UE can re-encode and re-modulate the data. This re-encoding and re-modulation can, for example, be applied to uplink data transmitted using time resources after the prioritized transmission. In this re-encoding and re-modulation, for example, the coding rate can be increased. The method for re-encoding and re-modulating the data during the prioritized transmission (e.g., coding rate, pre-encoded data of the object being re-encoded, etc.) can be determined in advance using standards, or the prioritized UE can notify the base station of information related to this method. This notification can be made using uplink L1 / L2 signaling or MAC signaling, for example. Thus, for example, it is possible to prevent the loss of uplink data transmissions from the prioritized UE during the prioritized transmission.

[0459] The gNB notifies the UE that will prioritize uplink transmission of the uplink permission. The UE that will prioritize uplink transmission uses the permission.

[0460] Applying the above method leads to the following problem: The UE prioritizing uplink transmission needs to send the SR to the gNB after generating the data for uplink transmission; therefore, there is actually time before the priority transmission begins. This results in a situation where low latency cannot be guaranteed in uplink priority transmission.

[0461] As a solution to the above problems, the UE performing priority transmission can notify the prioritized UE (hereinafter sometimes referred to as the prioritized UE) of this priority communication situation. This notification information may include information related to frequency resources used for priority transmission. This notification information may include information related to time resources. This notification information may include information related to power resources. The prioritized UE may not transmit uplink data scheduled for transmission on the frequency and / or time resources where priority transmission is performed. Therefore, the UE performing priority transmission can quickly perform priority transmission.

[0462] Applying the above method can lead to the following problems. Specifically, when the distance between the UE prioritizing the transmission and the UE receiving priority increases, the UE receiving priority may not correctly receive the notification. As a result, the UE receiving priority may transmit uplink data at the timing of the priority transmission, interfering with the priority transmission. Furthermore, the gNB cannot determine the timing of the priority transmission, and therefore may fail to correctly receive the priority transmission signal. This results in a decrease in the reliability of priority communication.

[0463] The following are solutions to the above problems.

[0464] The gNB provides a preemption indication to the UE that is being prioritized. This indication may show a timing at which priority transmission is likely to occur. That is, priority transmission may or may not occur at that timing. The timing indicated by this indication may be a single timing or multiple timings.

[0465] The frequency resources used to transmit priority indications from the gNB can be in a different region than the region used for downlink user data reception by the prioritized UE. For example, frequency resources for priority indication can be set. Thus, the prioritized UE can more easily determine the generation of priority.

[0466] The gNB can broadcast information related to frequency resources used for sending priority indications to its subordinate UEs. The UEs subordinate to the gNB mentioned above may include the UEs that are prioritized. As another example, the gNB can separately notify its subordinate UEs of information related to the frequency resources. This separate notification can use RRC-specific signaling. For example, information related to the frequency resources can be included in the RRC Connection Reconfiguration signaling from the gNB to its subordinate UEs.

[0467] As another example of this frequency resource, the same area used for downlink user data reception for the prioritized UE can be used. For example, a PDCCH can be used. The gNB can include information related to multiple timings that may lead to prioritized communication in the PDCCH. This saves frequency resources in the communication system. The aforementioned PDCCH can be a UE-dedicated PDCCH, allowing for flexible resource control for each UE. A shared PDCCH for multiple UEs, such as a group common PDCCH, can be used, reducing the signaling volume required for priority indication.

[0468] The gNB can use information related to the prioritized UE to encode and / or modulate a priority indication. For example, the gNB can use the C-RNTI of the prioritized UE to encode and / or modulate a priority indication. The prioritized UE can use this information to obtain the priority indication. Thus, for example, it can prevent the erroneous acquisition of priority indications for other UEs, thereby preventing a decrease in the efficiency of the communication system.

[0469] As an example of the priority indication encoding and / or modulation described above, a scrambling code for the CRC symbol, such as the CRC symbol itself, can be used, along with a scrambling code that uses all or part of the C-RNTI. This scrambling code can, for example, be an exclusive logical OR operation between the CRC symbol and the bits of the C-RNTI. As another example, a priority indication information bit can be used, along with a scrambling code that uses all or part of the C-RNTI. As yet another example, the CRC symbol can be derived using a bit column resulting from combining the priority indication information bit with all or part of the C-RNTI. This bit column can be used for other encoding processes.

[0470] As another example, information related to the prioritized UE can be used for modulation. For instance, information related to the DMRS procedure accompanying the priority indication can be determined using information related to the prioritized UE. Procedure-related information could be, for example, the routing index in the ZC (Zadoff-Chu) symbol, the cyclic shift (hereinafter sometimes referred to as CS), or a combination of both. For example, the routing index and cyclic shift in the ZC symbol can be determined using C-RNTI. Another example of procedure-related information could be a scrambling identifier. Thus, for example, processing load in UEs other than the prioritized UE can be reduced.

[0471] As another example, information related to the prioritized UE can be used to change the constellation values ​​of each RE after priority information modulation. For example, after extracting a specified number of bits from the initial C-RNTI, a constellation value is converted, and an operation is performed between the obtained constellation value and the constellation value of the initial RE after priority information modulation, and the result can be used for transmission. After extracting a specified number of bits from the next bit of the C-RNTI, a constellation value is converted, and an operation can be performed between the obtained constellation value and the constellation value of the second RE after priority information modulation. Similarly, operations can then be performed between the constellation values ​​of each RE after priority information modulation and the C-RNTI. The above operations can be, for example, complex multiplication. In the above complex multiplication, the constellation values ​​of each RE after priority information modulation and / or the constellation values ​​converted from C-RNTI can use complex conjugates. Through the above operations, for example, the amount of computation in the modulation process can be reduced.

[0472] The information contained in the priority indication sent from the gNB to the priority UE is disclosed as follows (1) to (6).

[0473] (1) Frequency resources used for priority transmission.

[0474] (2) Time resources used for priority sending.

[0475] (3) Whether there is an uplink transmission from a UE that is given priority.

[0476] (4) Uplink transmission power of the UE that is prioritized.

[0477] Information regarding the frequency / time resources used for transmitting and prioritizing the transmission of repetitive uplink data. Three specific examples of this information (5-1) to (5-3) are shown below.

[0478] (5-1) Do not send.

[0479] (5-2) Repeatedly send with priority.

[0480] (5-3) Use frequency / time resources other than those for priority transmission to send.

[0481] (6) Combinations of (1) to (5) above.

[0482] The above (1) could be, for example, an RB unit. Thus, for example, the prioritized UE can use frequency resources other than those used for priority transmission to transmit uplink data.

[0483] The above (2) can be, for example, a symbol unit. This symbol unit can be the symbol unit in the prioritized UE. Thus, for example, the prioritized UE can use symbols other than those used by the prioritized transmission to transmit uplink data.

[0484] For example, (3) above can be configured to not perform uplink transmission for the prioritized UE. This can reduce interference with priority communication. Thus, for example, the reliability of priority communication can be improved. As another example, uplink transmission for the prioritized UE can be performed. Thus, for example, uplink transmission control in the prioritized UE becomes easier.

[0485] The above (4) can be, for example, a value of the uplink transmission power, or a value showing the difference in uplink transmission power. Thus, for example, by reducing the uplink transmission power of the prioritized UE during the priority transmission timing, the reliability of priority transmission can be ensured.

[0486] In (5-1) above, the prioritized UE may not transmit uplink data that overlaps with the prioritized transmission. For example, the UE may block uplink data that overlaps with the prioritized transmission. This simplifies the processing in the gNB and the UE and ensures the reliability of the prioritized transmission.

[0487] In (5-2) above, the prioritized UE can utilize the frequency / time resources in the priority transmission to transmit uplink data that overlaps with the priority transmission. This makes the processing in the gNB and the UE easier.

[0488] In (5-3) above, the prioritized UE can reconfigure uplink data that overlaps with the prioritized transmission onto a different frequency / time resource than the one used in the prioritized transmission, and then transmit that uplink data. Information regarding the frequency / time resource used for the reconfiguration can be included in (5-3) above. The prioritized transmission time resource can use a frequency resource different from the prioritized transmission frequency resource. Alternatively, a frequency / time resource later than the prioritized transmission time resource can be used. Therefore, for example, since the continuity of uplink transmission data for the prioritized UE can be ensured, the HARQ decoding performance in the gNB can be improved.

[0489] As another example of (5-3) above, the prioritized UE can re-encode and re-modulate. This re-encoding can, for example, be applied to uplink data transmitted using time resources after the prioritized transmission. In this re-encoding, for example, the coding rate can be increased. The method for re-encoding and re-modulating the prioritized transmission (e.g., coding rate, pre-encoded data of the object being re-encoded, etc.) can be determined in advance using standards, or the prioritized UE can notify the base station of information related to this method. This notification can be made, for example, using uplink L1 / L2 signaling or MAC signaling. Thus, for example, it is possible to prevent the loss of uplink data transmission from the prioritized UE during the prioritized transmission.

[0490] The gNB can include information related to the activation / deactivation of priority transmission in the priority indication. The timing for activating priority transmission can be determined, for example, by further selecting whether transmission is possible from the aforementioned transmission timings where priority communication is possible. The prioritized UE can use this information to determine whether priority communication is possible. Information related to activation can be used instead of information related to activation / deactivation. The prioritized UE can use the absence of information related to activation to determine that priority transmission is invalid. Thus, for example, more time resources available for uplink transmission can be ensured in the prioritized UE.

[0491] The gNB can broadcast and / or notify priority indications to UEs that may be given priority. UEs that may be given priority can be all UEs within the cell coverage area, or a subset of UEs. In this embodiment 3, the notification from the gNB to the prioritized UE will, as described above, be a broadcast and / or notification to the UEs that may be given priority.

[0492] As a priority indication for all UEs within the cell coverage area, broadcast information can be used. Alternatively, a notification similar to the notification for the priority UE described above can be used. This notification could, for example, be a notification encoded and / or modulated using an RNTI for system information. Alternatively, the notification could, for example, be a notification encoded and / or modulated using a common identifier within the beam of the base station used by the UE, such as the beam's identifier. UEs within the cell can use this RNTI to obtain the notification. Thus, priority indication for multiple UEs can be performed with less signaling.

[0493] As a priority indication for a subset of UEs within the cell coverage area, the same notification described above as that for the priority UEs can be used. This notification, for example, can use the identifier of the group to which the subset of UEs belongs (e.g., the group's RNTI) instead of the C-RNTI for encoding and / or modulation. Thus, for example, priority indication for multiple UEs can be performed with less signaling. The group can be determined using a service (e.g., eMBB) used in the communication system, or it can be determined using other methods. For example, the group identifier can be provided using the service identifier.

[0494] As another example, the gNB can notify a subset of UEs within a specific beam. This subset of beams could be, for example, the beam used by the UE performing the priority communication, or the beam used by the UE that is being prioritized.

[0495] The UEs within a certain beam mentioned above could be, for example, all UEs within that beam. As a priority indication for all UEs within that beam, the same notification as that for the prioritized UE can be used. This notification could, for example, be a notification that uses the RNTI for system information instead of the C-RNTI for encoding and / or modulation. Alternatively, the notification could, for example, be a notification that uses a common identifier within the beam, such as the beam's identifier, for encoding and / or modulation. In the above, the beam identifier can be reset.

[0496] The UEs within a certain beam mentioned above may be, for example, a subset of UEs within that beam. As a priority indication for a subset of UEs within that beam, the same notification as that for the prioritized UEs can be used. This notification may, for example, use the identifier of the group to which the aforementioned subset of UEs belongs (e.g., the group's RNTI) instead of the C-RNTI for encoding and / or modulation. The aforementioned group may be determined using the service used in the communication system (e.g., eMBB), or it may be determined using other methods. For example, the identifier of the group may be provided using the identifier of the service.

[0497] The prioritized UE receives a priority instruction. This UE can stop the uplink transmission as an action that duplicates the priority transmission. This, for example, ensures the reliability of the priority transmission. The UE can choose not to transmit (e.g., block) uplink data scheduled to be transmitted in the interval where the aforementioned uplink transmission was stopped. Alternatively, the UE can reconfigure the uplink data scheduled to be transmitted in the interval where the aforementioned uplink transmission was stopped to other frequency / time resources, thereby transmitting the uplink data. As a reconfiguration method, the example shown in (5-3), disclosed as information contained in the priority instruction sent from the gNB to the prioritized UE, can be applied.

[0498] As another example, the UE can perform uplink transmissions that overlap with the priority transmission. As examples of uplink transmissions that overlap with the priority transmission, the following (1) to (4) are disclosed.

[0499] (1) Use low power for transmission.

[0500] (2) Transmit frequency resources at intervals.

[0501] (3) Send time resources at intervals.

[0502] (4) Combinations of (1) to (3) above.

[0503] In (1) above, by reducing the uplink transmission power that overlaps with the priority transmission, reliability in the priority transmission can be ensured, for example.

[0504] In (2) above, the UE can transmit frequency resources at intervals of RB units or at intervals of RE units. Thus, for example, the same effect as (1) can be achieved.

[0505] In (3) above, the UE can, for example, transmit time resources at intervals of symbol units. Thus, for example, the same effect as (1) can be achieved.

[0506] Similar to the example shown in (503), which is disclosed as information included in the priority indication sent from the gNB to the priority UE, the priority UE can re-encode and re-modulate. Regarding the re-encoding method described above, the examples shown in (5-3), which are disclosed as information included in the priority indication sent from the gNB to the priority UE, can be applied. Thus, for example, it is possible to prevent the loss of uplink data transmission from the priority UE during priority transmission.

[0507] Regarding the aforementioned uplink transmission actions that overlap with the priority transmissions in the UE, one or more pre-defined patterns can be configured. These patterns can be determined using standards or by the gNB. The gNB can broadcast or individually notify the UE of the determined configuration pattern. RRC-specific signaling can be used in this notification.

[0508] In the above, the gNB may include an identifier showing the setting pattern in the priority indication sent to the UE. Thus, for example, by reducing the transmission size of the priority indication, the frequency resources used for transmitting the priority indication can be reduced.

[0509] As another example, the priority indication described above may not include an identifier showing the setting pattern. For instance, if there is only one setting pattern, the identifier showing the setting pattern may not be included in the priority indication. This, for example, could further reduce the frequency resources used to transmit the priority indication.

[0510] The gNB notifies the priority UE of the uplink grant. This uplink grant is sent to the UE even if there is no SR from that UE.

[0511] The UE can use the uplink permission to send data preferentially. Alternatively, the UE can choose not to send data preferentially. The UE can choose not to send data preferentially if it has no uplink data to send preferentially.

[0512] Priority indication from the gNB to the prioritized UE and uplink permission from the gNB to the prioritized UE can be performed using the same signaling. For example, a shared PDCCH for multiple UEs can be used for this signaling. This, for example, can reduce the signaling load from the gNB to each UE.

[0513] As another example, the priority indication from the gNB to the priority UE and the uplink grant from the gNB to the priority UE can be delivered using different signaling. For example, the uplink grant can be sent earlier than the priority indication. Thus, the priority UE can, for example, ensure the timing of encoding / modulation processing after receiving the uplink grant.

[0514] In the above, the symbol lengths used for priority indication and uplink grant can be different from each other. Alternatively, priority indication and uplink grant can use different TTIs. Thus, for example, even when the symbol lengths and / or TTIs of the prioritized UE and the priority UE are different from each other, the method shown in Embodiment 3 can still be applied.

[0515] The gNB can periodically send the aforementioned priority notification to the prioritized UE. This period can be determined using standards, or it can be determined by the gNB and broadcast to subordinate UEs, or it can be sent individually to the UE. This notification can use dedicated RRC signaling. The uplink permission granted by the gNB to the prioritized UE can also be set to the same as the priority notification.

[0516] In the above context, priority notification can be priority instruction.

[0517] The gNB can modify this period. For example, the gNB can utilize RRC-specific signaling during this period modification. The modified period can be, for example, a radio frame unit, a time slot unit, a micro-time slot unit, a symbol unit, or other time units. Thus, by lengthening the period, for example, the frequency of priority indication reception in the prioritized UE is reduced. As a result, power consumption in the prioritized UE can be reduced.

[0518] The gNB can send this priority indication to the prioritized UE non-periodically. The prioritized UE can either always receive the priority indication within the frequency resources on which it is sent, or it can receive it in advance at the priority indication transmission timing notified by the gNB. The priority indication transmission timing can be notified to the prioritized UE from the gNB using RRC signaling.

[0519] As another example of the gNB providing this priority indication aperiodically to the prioritized UE, the prioritized UE can monitor the PDCCH for the priority UE. The gNB can encode the PDCCH for the priority UE using a group identifier that includes both the priority UE and the prioritized UE. This group identifier can be, for example, a beam identifier, an RNTI for system information, or other identifiers.

[0520] As another example, the gNB can notify the priority UE in advance of its identifier, such as C-RNTI. The group identifier of UEs that are likely to have priority communication can be used instead of the priority UE's identifier. The priority UE may belong to that group.

[0521] The prioritized UE can obtain PDCCH information for the prioritized UE using the group identifier containing both the prioritized UE and the prioritized UE, or the identifier of the prioritized UE, such as the prioritized UE's C-RNTI, or the group identifier of UEs that may perform priority communication. The prioritized UE can use this information to determine whether there is priority transmission and the frequency / time resources used for that priority transmission. Thus, for example, no new frequency resources for priority indication are needed, resulting in efficient utilization of the communication system.

[0522] The gNB can semi-persistently send the priority indication to the prioritized UE. This reduces, for example, the number of priority indications sent from the gNB, resulting in reduced power consumption in the gNB. The semi-persistent notification may include some or all of the information disclosed in Embodiment 3, as information included in the priority indication to the prioritized UE. The semi-persistent notification may include information indicating whether it contains information related to priority transmission during the notification's validity period, i.e., the period to which the notification ends.

[0523] The gNB can use pre-determined frequency / time resources to send the semi-persistent notification. For example, the semi-persistent notification can be sent using broadcast information, RRC-specific signaling, MAC signaling, or L1 / L2 signaling. Alternatively, new frequency / time resources can be set for sending the semi-persistent notification. The gNB can pre-notify the prioritized UE of information related to these resources.

[0524] The gNB can perform this priority indication to the prioritized UE in a quasi-static manner. This, for example, can reduce the signaling volume from the gNB to the prioritized UE. The quasi-static notification may include part or all of the information disclosed as part of the priority indication sent from the gNB to the prioritized UE, as part of the priority indication to the prioritized UE. The gNB can perform this quasi-static notification, for example, using broadcast information or RRC-specific signaling.

[0525] The above methods can also be combined. For example, the gNB can combine a quasi-static priority indication with a priority indication utilizing PDCCH and then notify the prioritized UE. For instance, the quasi-static priority indication may include information related to the priority transmission timing and frequency resources, as well as information related to the prioritized UE's actions when priority transmission occurs. The priority indication utilizing PDCCH may include information related to the activation / deactivation of priority transmission. Using the quasi-static priority indication and the priority indication utilizing PDCCH, the prioritized UE can, for example, stop uplink transmission at the transmission timing that activates priority transmission. Thus, the gNB can, for example, provide priority indication to the prioritized UE with less signaling.

[0526] As other examples, in a quasi-static priority indication, the gNB can contain information related to the actions of the prioritized UE when priority transmission occurs. In a priority indication utilizing PDCCH, the gNB can contain information related to the priority transmission timing and frequency resources. Using both quasi-static and PDCCH-utilized priority indications, the prioritized UE can, for example, stop uplink transmission at the priority transmission timing. Thus, in addition to the effects described above, it allows for flexible control of frequency / time resources in priority communication.

[0527] As another example of a combination of the methods described above, gNB can use a semi-persistent priority indicator and a priority indicator utilizing PDCCH. The information contained in the semi-persistent priority indicator can be the same as that in the quasi-static priority indicator in the examples above, or it can contain information related to the validity period of the notification. Thus, the same effect as described above can be achieved.

[0528] Figure 32 This diagram illustrates the use of frequency resources different from those used for downlink user data transmission and reception to the prioritized UE, to perform uplink preemption indication (UL preemption indication) from the gNB for the prioritized UE. Figure 32 An example of FDM is shown. Additionally, Figure 32 Examples of eMBB communication in the prioritized UE and URLLC communication in the prioritized UE are shown. Figure 32 An example is shown where the timing for priority transmission exists twice within a single time slot.

[0529] exist Figure 32In this process, the gNB sends uplink priority indications 4001 and 4002 to the prioritized UE. The transmission of these priority indications can utilize different frequency resources than PDCCH 4003 and PDSCH 4004. At timing 4006 indicated by uplink priority indication 4001, the prioritized UE stops eMBB uplink communication 4005. At timing 4007 indicated by priority indication 4002, the prioritized UE also stops eMBB uplink communication 4005. The prioritized UE does not perform URLLC communication at timing 4006, and sends URLLC communication 4008 at timing 4007.

[0530] Figure 33 This is an example of using PDCCH to indicate uplink priority from the eNB to the prioritized UE. Figure 33 An example of FDM is shown. Additionally, Figure 33 An example is shown where eMBB communication is performed in the prioritized UE and URLLC communication is performed in the prioritized UE. Additionally, Figure 33 An example is shown where the timing for priority transmission occurs twice within a single time slot. Figure 33 In the middle, to and Figure 32 Repeating signals are labeled with the same number, and common descriptions are omitted.

[0531] exist Figure 33 In this process, the uplink priority indication 4101 is sent to the prioritized UE using the start symbol of PDCCH4003. This uplink priority indication 4101 contains information related to priority communication timings 4006 and 4007. The prioritized UE receives the uplink priority indication 4101 and obtains the information related to timings 4006 and 4007. The prioritized UE stops eMBB uplink transmission at timings 4006 and 4007.

[0532] exist Figure 33 In the middle, others and Figure 32 Similarly, the explanation is omitted.

[0533] exist Figure 33 The example shown illustrates the use of the start symbol of the PDCCH4003 to transmit the uplink priority indication 4101, but the start symbol can also be omitted. For example, the final symbol or intermediate symbols can be used. Furthermore, the uplink priority indication 4101 can occupy a portion of the frequency resources of the PDCCH4003.

[0534] Figure 33The example shown is an example of FDM, but it can be applied to TDM. For example, in TDM, the uplink priority indication 4101 can be included in the PDCCH 4003 for transmission. The priority communication timing indicated by the uplink priority indication 4101 can be included in the transmission timing of the UL in TDM. Thus, for example, even in TDM, an uplink priority indication from the base station for the prioritized UE can be transmitted.

[0535] The gNB can set one or more priority transmission times for each time slot. The gNB can concentrate this time allocated to multiple priority transmission UEs into one or more. Therefore, for example, even if there are multiple priority transmission UEs, uplink transmission resources in the priority UE can be guaranteed. Alternatively, the gNB can distribute the time allocated to multiple priority transmission UEs across multiple locations. This, for example, can reduce the possibility of priority transmission time conflicts between multiple priority transmission UEs.

[0536] The gNB can receive priority transmissions from multiple priority UEs using contention-based conditions. The gNB and priority UEs can use HARQ feedback for priority retransmission processing. Therefore, the gNB can receive priority transmissions in sequence based on contention conditions.

[0537] Other solutions are disclosed. The gNB will notify the prioritized UE in advance of the time and / or frequency resources that may generate priority communication. Information related to the period of priority communication can be included in the notification. Information related to the repeated actions of the uplink transmission in the UE can be included in the notification. The information related to the action can be, for example, information indicating that the uplink transmission has stopped, or information as an example of the uplink transmission repeated with the priority transmission disclosed above (1) to (4). The notification can be broadcast to UEs under the gNB or can be notified separately to the prioritized UE. As the separate notification mentioned above, RRC dedicated signaling, such as RRC connection resetting signaling, can be used. The prioritized UE can use the notification to stop the uplink transmission, or can perform the actions shown in (1) to (4) as examples of the uplink transmission repeated with the priority transmission disclosed above. Thus, for example, since dynamic priority indication for the prioritized UE is not required, frequency / time resources can be used effectively.

[0538] This solution differs from the priority indication solution described above in that it quasi-statically notifies the priority UE of information related to priority transmission.

[0539] The gNB can notify the priority UE of this notification. That is, the gNB can notify the priority UE in advance of the available time and / or frequency resources for priority communication. As a result, scheduling in the priority UE becomes easier.

[0540] The gNB notifies the priority UE of the uplink grant. The information contained in the uplink grant, and the actions of the priority UE after receiving the uplink grant, can be set to be the same as the solution described above for using the priority indication. Thus, for example, since dynamic scheduling can be performed for the priority UE in accordance with the radio channel conditions, the reliability of priority communication can be ensured.

[0541] Other solutions are disclosed. The gNB transmits without permission to the priority UE. That is, the gNB notifies the priority UE of the time and / or frequency resources available for priority communication. This notification may include information related to the period of priority communication. The notification may also include information regarding uplink permission for the priority UE. This notification can be broadcast to all UEs under the gNB or sent individually to the priority UE. As an individual notification, RRC-specific signaling, such as RRC connection reconfiguration signaling, can be used.

[0542] Regarding the notification from the gNB to the prioritized UE and the UE's actions, the method shown in the solution of notifying time resources and / or frequency resources that may generate priority communication can be applied. This can reduce the signaling volume in the notification from the gNB to the prioritized UE.

[0543] The notification from the gNB to the prioritized UE and the broadcast and / or notification from the gNB to the prioritized UE can be different signaling. As another example, information from both can be included in the same signaling. This reduces the signaling volume from the gNB to each UE.

[0544] As another example of unlicensed transmission, the gNB may pre-broadcast or notify the priority UE of information related to the transmission timing and / or transmission power that allows priority communication. This transmission timing may be information related to the transmission period. The information related to the transmission timing may be in micro-slot units or symbol units. RRC signaling may be used in this broadcast or notification.

[0545] The gNB can notify the priority UE of information related to the activation / deactivation of priority transmission. The timing for priority transmission to become active is determined by the gNB, for example, by further selecting whether transmission is possible from the aforementioned transmission timings where priority communication is possible. Information related to activation can be used instead of information related to activation / deactivation. The priority UE can use information without activation to determine priority transmission as invalid.

[0546] The gNB may include information related to resources used for priority transmission in the information related to the activation / deactivation of priority transmission. This resource may be information related to time resources or frequency resources. The gNB may also include information required for modulation and / or coding of priority transmission in the information related to the activation / deactivation of priority transmission. This modulation and / or coding information may, for example, be information related to the modulation scheme, the coding rate, or the HARQ process number.

[0547] The gNB can use the PDCCH of the priority UE to transmit information related to the priority transmission of activation / deactivation. Alternatively, a new frequency / time resource can be set for transmitting this information. The gNB can notify the priority UE in advance of the information related to the aforementioned new frequency / time resource.

[0548] The gNB can notify the prioritized UE of information related to priority transmission. This information may be the same as the priority indication disclosed in Embodiment 3. This information may, for example, include information related to transmission timing. The information related to transmission timing may, for example, be information related to the timing at which priority transmission becomes active. This information may include part or all of the activation / deactivation information notified to the prioritized UE from the gNB. The prioritized UE can use this information to determine the timing at which priority transmission may occur.

[0549] For the prioritized UE, the gNB can use the PDCCH used by the prioritized UE to transmit information related to priority transmission. Alternatively, a new frequency / time resource can be configured for transmitting this information. The gNB can notify the prioritized UE in advance of the information related to the aforementioned new frequency / time resource.

[0550] This third implementation method reduces latency in priority communication. Furthermore, it ensures reliability in priority communication.

[0551] Variation 1 of Implementation Method 3.

[0552] In uplink priority transmission, the following problem arises: When the gNB notifies the prioritized UE of timing information that may lead to priority transmission, the prioritized UE may still stop uplink transmission or reduce power to transmit even on frequencies / time resources where priority transmission is not actually required. This results in reduced uplink transmission efficiency for the prioritized UE.

[0553] The following are solutions to the above problems.

[0554] The priority UE notifies the gNB of its request for priority transmission. This information can, for example, use a predefined symbol. The predefined symbol can be generated in a process that does not require or is relatively easy to encode and decode. For example, the predefined symbol could be a ZC (Zadoff-Chu) symbol, an m-series symbol, or a Hadamard symbol. The priority UE can notify the gNB of this information after the priority data transmission is generated.

[0555] As examples of information relating to the aforementioned prescribed symbols, (1) to (8) are disclosed below.

[0556] (1) Series in ZC symbols (e.g., value q).

[0557] (2) Cyclic shift.

[0558] (3) Number of code elements.

[0559] (4) Number of times sent.

[0560] (5) Information related to frequency hopping.

[0561] (6) Information related to process jumps.

[0562] (7) Information related to the timing of transmission.

[0563] (8) Combinations of (1) to (7) above.

[0564] The above (1) could be, for example, the value of the routing index in the ZC symbol.

[0565] Regarding (3) above, the number of symbols can be, for example, one symbol or multiple symbols. Thus, for example, by using one symbol, the symbol can be quickly notified. On the other hand, for example, by using multiple symbols, a longer sequence length of the symbol can be obtained, thereby improving reliability.

[0566] By using (4) above, for example, by setting the number of transmissions to multiple times, the reliability of the symbol notification can be improved.

[0567] Through the above (5), for example, through frequency diversity, the reliability of the symbol notification can be improved.

[0568] By means of the above (6), for example by avoiding interference in the case of sending the same symbol from other UEs and / or other base stations, the reliability of the symbol notification can be improved.

[0569] The information mentioned in (7) above could be, for example, information related to the time resolution at which the UE can transmit the symbol. This time resolution could be, for example, per symbol, per microslot, or per slot. Thus, for example, if the time resolution is set to per symbol, the symbol can be notified quickly.

[0570] Information related to the aforementioned symbols can be determined using standards. This information can, for example, be shared among UEs under a gNB. Alternatively, this information can be determined individually for each UE. This information can be determined using the UE's identifier (e.g., UE-ID). Thus, for example, since symbol allocation processing for each UE is not required, the processing workload related to symbol allocation can be reduced.

[0571] As another example, information related to the aforementioned specified symbols can be determined and notified to the UE by the gNB. This information can be shared among UEs under the gNB. This information can be determined using an identifier indicating the base station (e.g., gNB-ID) or an identifier indicating the cell (e.g., cell ID). Alternatively, the gNB can assign this information individually to each UE. The gNB can broadcast this information to each UE or use RRC-specific signaling for quasi-static notification. For example, this can reduce the signaling volume associated with notifying this information. Alternatively, this information can be dynamically notified using MAC signaling. For example, this can ensure the reliability of retransmission control and allow for flexible allocation based on surrounding cells, the status of subordinate UEs, etc. Alternatively, L1 / L2 signaling can also be used. For example, this can enable rapid notification.

[0572] Regarding the information related to the specified symbols mentioned above, each UE may use one piece of information or multiple pieces of information. As an example of using multiple symbols, information related to the amount of data transmitted in uplink priority mode can be used to distinguish which symbols are used. Thus, for example, the gNB can perform flexible scheduling that utilizes the amount of data transmitted in uplink priority mode.

[0573] The frequency band for the priority UE to transmit designated symbols can be the entire frequency band available to the priority UE, or a portion thereof. The dispersed frequency band can be used per RB or per RE. A combination of both is possible. That is, within a frequency band dispersed by per RB, designated symbols can be allocated relative to a frequency band dispersed by per RE. Thus, for example, flexible frequency band allocation is possible.

[0574] The frequency band in which the priority UE transmits the specified symbol can be a different frequency band than that available to the priority UE. That is, the uplink signal transmission from the priority UE and the transmission of the specified symbol from the priority UE can occur in different frequency bands. This, for example, can reduce the interference power during the reception of the specified symbol by the gNB. As a result, the reliability of the specified symbol transmission from the priority UE can be improved.

[0575] As another example, the frequency band in which the priority UE transmits the specified symbol may include a portion or all of the frequency band available to the priority UE. That is, the transmission of the uplink signal from the priority UE and the transmission of the specified symbol from the priority UE may at least partially overlap in frequency bands. The gNB can simultaneously receive the specified symbol and the uplink signal. The gNB can separate the specified symbol and the uplink signal. In the above separation, the gNB can extract the specified symbol from the simultaneously received signal using the same pattern as the specified symbol. The gNB can process the remaining signal extracted above as the uplink signal from the priority UE. Thus, for example, frequency resources in the communication system can be used efficiently.

[0576] The frequency band for priority UE to transmit designated symbols can be determined using standards, or it can be determined by the gNB and notified to the UE. This notification method can be the same as the method used for notifying information related to designated symbols as described above.

[0577] The timing of the priority UE's transmission of a specified symbol can be determined in advance using a standard. For example, the priority UE may transmit the symbol only in the symbols preceding a specified period from the start of priority transmission. As another example, the priority UE may transmit the symbol in the specified symbols in one or more micro-slots preceding the micro-slot in which priority transmission takes place.

[0578] The symbols specified in the above-mentioned "only specified period" can be multiple symbols. The priority UE can use a portion of these multiple symbols to transmit the specified symbol, or it can use all of them. For example, if a portion of the multiple symbols includes timing elements that cannot be prioritized, the priority UE can use the symbols after removing the timing elements that cannot be prioritized to transmit the specified symbol. This, for example, improves the reliability of the priority transmission setting. As another example, the priority UE can use all of the above-mentioned multiple symbols to repeatedly transmit the specified signal. This, for example, improves the reliability of the transmission of the specified symbol from the priority UE.

[0579] As another example, the timing for transmitting a specified symbol to a priority UE can be determined by the gNB. The gNB can broadcast or individually notify its subordinate UEs of this timing. This notification may use RRC-specific signaling. When determining this timing in the gNB, the gNB may use processing capabilities related to the reception of that symbol within its own gNB, processing capabilities related to the transmission of that symbol in the UE, and processing capabilities related to the transmission of that symbol from the gNB to the priority UE, as described later, and / or processing capabilities related to the reception of that symbol by the UE. These processing capabilities related to the transmission of that symbol in the UE, and / or processing capabilities related to the reception of that symbol by the UE from the gNB to the priority UE, may, for example, be included in the UE's capabilities. Thus, for example, the gNB can determine the timing in a way that keeps pace with the processing time of the gNB and the UE in that symbol.

[0580] The priority UE can transmit the specified symbol at a timing different from the transmission timing of the DMRS and / or PUCCH and / or SRS from the priority UE. This different timing can, for example, apply to situations where the specified symbol uses the same frequency resources as the DMRS, PUCCH, or SRS. The priority UE can change the transmission timing of the specified symbol. This change can, for example, be made within a range of multiple symbols from which the specified symbol can be transmitted from the priority UE. Thus, for example, the priority UE can quickly notify the gNB of the specified symbol. The gNB can notify the priority UE in advance of information related to the transmission timing of the DMRS and / or PUCCH and / or SRS of the priority UE. Alternatively, the information related to the timing can be determined in advance using the standard. Thus, for example, the priority UE can identify the timing at which the specified symbol can be transmitted.

[0581] In the above, the priority UE can be configured not to transmit the specified symbol within the range where the specified symbol can be transmitted, for example, if a timing different from the transmission timing of the DMRS and / or PUCCH and / or SRS from the priority UE does not exist. The priority UE can then transmit the specified symbol within the subsequent range where the specified symbol can be transmitted. Thus, for example, the complexity of control related to priority transmission in the communication system can be avoided.

[0582] The method for changing the transmission timing of the specified symbol can be determined in advance using a standard. This method could be, for example, shifting the transmission timing of the specified symbol forward sequentially for each symbol within a range of multiple symbols that can be transmitted, or shifting it backward sequentially for each symbol, or a combination of both.

[0583] As another example of a method for changing the timing of the transmission of this specified symbol, the gNB may notify the priority UE of this change method separately. This notification may be, for example, RRC-specific signaling, MAC signaling, or L1 / L2 signaling.

[0584] As another example, the transmission timing of the specified symbol within a time slot can be determined in advance using the standard, or it can be broadcast or notified to the priority UE in advance from the gNB. The transmission timing of the DMRS and / or PUCCH and / or SRS from the priority UE can be set at a timing other than the transmission timing of the specified symbol. This, for example, avoids the complexity of priority transmission control in the communication system.

[0585] As another example, the prioritized UE can transmit the specified symbol at the same timing as the DMRS transmission timing from the prioritized base station. This same timing transmission, for example, can be applied when the specified symbol and the DMRS utilize different frequency resources.

[0586] The gNB can assign different procedures to the specified symbol and the DMRS separately. This assignment can, for example, apply when the specified symbol and the DMRS use the same frequency resources. The gNB can notify the prioritized UE and / or the priority UE of this assignment. This notification can be, for example, RRC-specific signaling, MAC signaling, or L1 / L2 signaling. Thus, the gNB can, for example, receive both the specified symbol and the DMRS simultaneously.

[0587] As another example, the specified symbol and the DMRS can be frequency-division multiplexed. Frequency division multiplexing can be performed per subcarrier, per multiple subcarriers, per resource element group (REG), or using other methods. The gNB can notify the prioritized UE and / or the priority UE of this frequency division multiplexing method. This notification can be, for example, RRC-specific signaling, MAC signaling, or L1 / L2 signaling. Thus, for example, the gNB can receive both the specified symbol and the DMRS simultaneously.

[0588] The gNB receives a specified symbol sent from the priority UE. The gNB identifies the priority transmission request by receiving this symbol.

[0589] The gNB notifies the prioritized UE of a request for priority transmission. This information may, for example, use a predefined symbol. This predefined symbol may be the same as the symbol sent from the prioritized UE to the gNB as a request for priority transmission. The symbol used to send the information from the gNB to the prioritized UE may be the same as or different from the symbol used to send the information from the prioritized UE to the gNB. After recognizing the request for priority transmission, the gNB may immediately send this information to the prioritized UE.

[0590] The information relating to the aforementioned specified symbols may be the same as the information relating to the symbols sent from the priority UE to the gNB. The method for determining the information relating to the aforementioned specified symbols, and the method for broadcasting and / or notifying subordinate UEs from the gNB, may also be set to the same.

[0591] Regarding the information related to the specified symbols mentioned above, each UE may use one piece of information or multiple pieces of information. As an example of using multiple symbols, information related to the frequency resources used for priority transmission can be used to distinguish the symbols used. Thus, for example, the gNB can perform flexible scheduling that utilizes the amount of data in uplink priority transmission.

[0592] The timing of transmitting the aforementioned specified symbols can be determined using the same method as the timing of transmitting specified symbols by the priority UE.

[0593] The frequency band used by the gNB to transmit designated symbols can be the same as the frequency band used by the priority UE to transmit designated symbols. For example, the frequency band used by the gNB to transmit designated symbols can be the entire frequency band available to the priority UE, or a portion thereof. In other examples, the area near the center of the frequency band used by the gNB can be used as the frequency band for transmitting designated symbols by the gNB. By using the same frequency band as the synchronization signal and broadcast information channel, for example, UEs subordinate to the gNB can commonly receive the aforementioned symbols.

[0594] The prioritized UE receives a specified symbol transmitted from the gNB. The prioritized UE identifies the occurrence of the priority transmission by receiving this symbol.

[0595] The prioritized UE can stop uplink transmissions that overlap with the prioritized transmission by receiving the aforementioned symbols, or it can perform the actions shown in (1) to (4) as examples of uplink transmissions that overlap with the prioritized transmission disclosed in Embodiment 3. The related actions of uplink transmissions that overlap with the prioritized transmission in the prioritized UE can be determined using a standard, or they can be broadcast in advance to the prioritized UE from the gNB, or they can be notified separately. Regarding the above-mentioned determinations, broadcasts, or separate notifications generated by the standard, the method shown in Embodiment 3 can be applied.

[0596] The gNB notifies the priority UE of information relating to uplink clearance for priority transmission. This information may, for example, be an uplink clearance using the PDCCH of the priority UE. As another example, this information may use a predefined symbol. This predefined symbol may be the same as the symbol sent from the priority UE to the gNB as information indicating a request for priority transmission. The symbol used for information sent from the gNB to the priority UE may be the same as or different from the symbol used for information sent from the priority UE to the gNB.

[0597] Information relating to the specified symbols notified from the gNB to the priority UE may be the same information as that relating to the symbols sent from the priority UE to the gNB. The method for determining information relating to the aforementioned specified symbols, and the method for broadcasting and / or notifying subordinate UEs from the gNB, may also be set to be the same.

[0598] Regarding the information concerning the designated symbols notified from the gNB to the priority UE, one or more pieces of information may be used for each UE. As an example of using multiple symbols, information related to the frequency resources used for priority transmission can be used to distinguish the symbols used. As another example, information related to the transmission power for priority communication can be used to distinguish the symbols used. Thus, the gNB can, for example, flexibly schedule uplink priority transmission. The gNB can notify the priority UE of the aforementioned multiple pieces of information in advance.

[0599] The timing for transmitting the specified symbol from the gNB to the priority UE can be handled using the same method as the timing for the priority UE to transmit the specified symbol.

[0600] The frequency band used by the gNB to transmit specified symbols for the priority UE can be the same as the frequency band used by the priority UE to transmit specified symbols. For example, the entire frequency band available to the priority UE can be used, or a portion of the frequency band can be used. In other examples, the area near the center of the frequency band used by the gNB can be used. By using the same frequency band as the synchronization signal and broadcast information channel, UEs under the gNB can, for example, jointly receive the aforementioned symbols.

[0601] Priority UEs use information related to the aforementioned uplink permission to transmit first.

[0602] If the priority UE does not receive information related to the aforementioned uplink grant, it can be determined that the priority request has failed. This determination can be made, for example, if information related to the aforementioned uplink grant has not been received by a predetermined time interval.

[0603] The priority UE can retransmit its priority request. This retransmission can occur, for example, if it is determined that the priority UE has failed in its priority request. The priority UE can then retransmit the priority request at a time after this determination, when a priority request can be sent. Thus, for example, a rapid priority request can be made within the priority UE.

[0604] The priority UE can set a retransmission prohibition timer in the priority request. The priority UE can be set not to send or retransmit the priority request until the retransmission prohibition timer expires. This can, for example, prevent the pressure on frequency / time resources caused by repeated retransmission of priority requests.

[0605] A retransmission disable timer for priority requests can, for example, start when a priority request is sent. This timer can, for example, stop upon uplink reception from the gNB.

[0606] The value of this timer can be determined in advance using standards, or it can be determined by the gNB and broadcast or individually notified to priority UEs. This notification can be RRC signaling, MAC signaling, or L1 / L2 signaling. By having the gNB determine the timer value, flexible control can be implemented, for example, in accordance with the usage of frequency / time resources.

[0607] Figure 34 This is a diagram illustrating the use of prescribed symbols to represent information indicating a priority request. Figure 34 An example of FDM is shown. Additionally, Figure 34 An example is shown where eMBB communication is performed in the prioritized UE and URLLC communication is performed in the prioritized UE. Figure 34 In the middle, to and Figure 32 Common signals are labeled with the same number, and common descriptions are omitted.

[0608] exist Figure 34 In this process, the preferred UE sends symbol 4201, indicating a preemption request, to the gNB. Symbol 4201 can be transmitted using the frequency band used for priority communication or a different frequency band. The gNB receives symbol 4201 and recognizes the priority request. The gNB then sends an uplink priority indication 4202 to the preferred UE. The uplink priority indication 4202 can be the same symbol as symbol 4201 or the same symbol as in Implementation 3. Furthermore, the uplink priority indication 4202 can be transmitted using the frequency band used for PDCCH 4003 and PDSCH 4004 or a different frequency band.

[0609] This Modification 1 can be used in combination with Embodiment 3. For example, the base station and the gNB notify the priority UE in advance of the time resources and / or frequency resources that may generate priority communication. Information related to the uplink transmission operation and the operation of repeated priority transmission in the UE can be included in the notification. The priority UE sends the specified symbol shown in this Modification 1 to the base station, and the base station can send the specified symbol shown in this Modification 1 to the priority UE. The priority UE can stop uplink transmission by receiving the specified symbol, or it can perform the operations shown in (1) to (4) as examples of uplink transmission that are repeated with priority transmission. The priority UE can continue uplink transmission without receiving the specified symbol. Thus, for example, in the priority UE, uplink transmission in frequency / time resources that do not actually generate priority transmission can be performed, thereby ensuring the uplink transmission efficiency in the priority UE.

[0610] According to this variation 1, since the gNB does not need to perform or can perform SR decoding, uplink grant encoding, and uplink priority indication encoding, it can perform rapid notification. Furthermore, for example, in the prioritized UE, uplink transmission in frequency / time resources that do not actually generate priority transmission can be performed, thus ensuring uplink transmission efficiency in the prioritized UE.

[0611] Implementation method 4.

[0612] In LTE-NR coexistence on the same downlink carrier, the gNB uses MBFSN subframes in LTE to transmit NR signals. The gNB also uses MBSFN subframes to transmit NR signals. The gNB can use non-MBSFN subframes to transmit NR signals. The gNB can use micro-slots when transmitting NR signals.

[0613] In the above, the gNB and the LTE base station (eNB) can be base stations that constitute a DC in a UE, or they can not be base stations that constitute a DC. For example, the gNB and eNB can be base stations located nearby to each other. Thus, for example, interference from the gNB in ​​UEs that only support LTE can be reduced.

[0614] The aforementioned NR signal can be an SS signal, a PBCH signal, or both. The gNB can use one module (hereinafter sometimes referred to as the SS module) in each beam to transmit both the SS and PBCH.

[0615] The gNB can burst-transmit SS and PBCH signals (hereinafter sometimes referred to as SS bursts). For example, within a predetermined time period, the gNB can transmit the SS and / or PBCH signals of each beam. The aforementioned SS and / or PBCH signals within the predetermined time period can be transmitted according to other predetermined cycles. The aforementioned SS and / or PBCH signals within the predetermined time period can be transmitted using the SS module.

[0616] Applying the above method will result in the following problem: The SS burst signal of NR conflicts with signals present in non-MBSFNs of LTE, such as synchronization signals, broadcast information, and paging information. As a result, in the coexistence of LTE-NR, the UE cannot establish synchronization with the eNB and / or gNB.

[0617] The following are solutions to the above problems.

[0618] A priority order is set between LTE non-MBSFN subframe signals and NR SS burst signals. For example, in the interval where the two signals collide, only one signal is transmitted. The aforementioned LTE non-MBSFN subframe signals can be, for example, LTE synchronization signals, LTE broadcast information channels, or LTE paging signals. The aforementioned NR SS burst signals can be, for example, NR synchronization signals or NR broadcast information channels.

[0619] For example, LTE non-MBSFN subframe signals can be prioritized. This, for example, can reduce interference in LTE non-MBSFN subframes. The gNB can choose not to transmit any SS burst signals within subframes that overlap with LTE non-MBSFN subframes, or only a portion thereof. Instead of the overlapping subframes described above, these can be overlapping time slots, overlapping micro-time slots, or overlapping symbols. As another example, the gNB can choose not to transmit only the NR SS burst signals that overlap with non-MBSFN subframe signals. This prevents unnecessary SS burst interruptions.

[0620] The gNB can transmit NR SS burst signals that repeat with the LTE non-MBSFN subframe signals. The two signals mentioned above can be separable signals, for example, signals with a predetermined pattern. Separable signals can be, for example, a combination of LTE SS and NR PBCH, a combination of LTE PBCH and NR SS, or a combination of LTE paging signals and NR SS. The UE can receive the repeated signals and separate each signal. For example, the UE can extract the signal with the predetermined pattern and obtain the difference between the original received signal and the extracted signal as another signal. Thus, for example, the UE can receive both LTE and NR signals.

[0621] The eNB can modify the paging transmission timing to its subordinate UEs. For example, this modification can centralize the paging transmission timing to one or more subordinate UEs. This, for example, reduces the overlap between the NR's SS burst signal and the LTE's paging transmission timing, thus eliminating the need to stop SS burst transmission in the gNB and reducing NR SS burst transmissions that interfere with the eNB's signal.

[0622] As an example of paging timing modification, the POs of subordinate UEs can be centralized into one type. This, for example, avoids the overlap of NR SS burst transmission and LTE paging timing. As an example of a method for centralizing this PO, as described in Non-Patent Document 17 (3GPP TS 36.304V14.4.0), the value of parameter Ns, which indicates the number of subframes allocating paging signals in one radio frame, can be set to 1. The eNB can set the value of parameter Ns to 1 by setting the value of parameter nB, as described in Non-Patent Document 17 (3GPP TS 36.304V14.4.0), to less than one times T. The eNB can broadcast the modified value of parameter nB to its subordinate UEs. This broadcast can, for example, use SIB2 (see Non-Patent Document 18 (3GPP TS 36.331)). Thus, for example, the eNB can centralize the POs of subordinate UEs into one type with less signaling.

[0623] The paging transmission timing changes mentioned above can include, for example, changing the paging frame (PF), the paging timing (PO), and the paging transmission period. Multiple of these can be combined.

[0624] When the paging transmission timing changes, the eNB can modify the parameters used to determine the paging transmission timing. This parameter can be, for example, the UE-ID. The eNB can then notify the UE of information related to the change of this parameter.

[0625] An eNB can increase the number of target UEs that can be paged within a single paging transmission time. This increase can be determined in advance using standards, for example. Thus, the eNB can, for example, perform paging to multiple UEs in fewer paging transmission times.

[0626] The eNB can notify neighboring eNBs of this information. These neighboring eNBs could be, for example, multiple eNBs belonging to the same tracking area as the current eNB. These multiple eNBs can use this information to page the UE. Thus, for example, paging can be successfully performed even when the UE has moved.

[0627] The eNB can notify the upper-level NW device of this information. This notification can utilize the interface between the upper-level NW device and the base station. The upper-level NW device can be either an AMF (Advanced Feature Controller) or an SMF (Small Feature Controller). The upper-level NW device can send a notification to the eNB indicating its agreement or rejection of the parameter change.

[0628] The higher-level NW device can notify its subordinate eNBs of this information. These subordinate eNBs can, for example, be multiple eNBs belonging to the same tracking area as the current eNB. These multiple eNBs can use this information to page the UE. Thus, for example, paging can be successfully performed even when movement occurs within the UE.

[0629] The gNB can obtain information related to non-MBFSN subframes of LTE. As information related to non-MBFSN subframes of LTE, the following (1) to (5) are disclosed.

[0630] (1) LTE frame timing.

[0631] (2) Information related to SS for LTE.

[0632] (3) Information related to the LTE communication method.

[0633] (4) Information related to paging timing.

[0634] (6) Combinations of (1) to (4) above.

[0635] The gNB can use the cell search shown in Implementation 1 to obtain the LTE frame timing described above (1). The gNB may have the function of performing cell search. The gNB may set the timing for performing cell search. As another example, the gNB may request information from the eNB regarding the difference between the frame timings of LTE and NR. The eNB may notify the gNB of this information. This request and / or notification may be made using an inter-base station interface, such as the Xn interface. The eNB may obtain the NR frame timing. For example, the eNB may use cell search to obtain the NR frame timing. Thus, for example, the gNB may obtain information related to the non-MBSFN subframes of LTE.

[0636] The gNB can request the information mentioned in (2) above from the eNB. The eNB can notify the gNB of the information mentioned in (2) above. This request and / or notification can be made using an inter-base station interface, such as the Xn interface. The information mentioned in (2) above can be, for example, information related to the symbol series and cyclic offset of the LTE PSS, or information related to the symbol series and cyclic offset of the LTE SSS. The gNB can use the information mentioned in (2) above to perform cell search. Thus, for example, cell search processing in the gNB can be performed quickly. In addition, for example, false detection of LTE cells in the gNB can be prevented.

[0637] As another example, the gNB can use cell search to obtain the information mentioned in (2) above. This can, for example, reduce the signaling volume between base stations.

[0638] The information in (3) above may include information related to the LTE duplex mode (e.g., TDD, FDD) or half-duplex mode, or information related to the cyclic prefix (e.g., the duration of the cyclic prefix). The gNB may request the information in (3) above from the eNB. The eNB may notify the gNB of this information. This request and / or notification may be made using an inter-base station interface, such as the Xn interface. The gNB may use this information to derive the location of signals in non-MBSFN subframes of LTE. Thus, for example, the gNB can quickly obtain information related to non-MBSFN subframes of LTE.

[0639] As another example of (3) above, the gNB can obtain the information in (3) above through LTE broadcast information. Thus, for example, the signaling volume between base stations can be reduced.

[0640] The information mentioned in (4) above may include, for example, information about the paging frame (PF), paging timing (PO), and paging period used by the eNB. The gNB may request this information from the eNB. The eNB may notify the gNB of this information. The eNB may notify the gNB of this information after receiving a request from the gNB, or it may notify the gNB of this information if there are changes in this information. The gNB may use this information to transmit SS burst signals in non-MBFSN subframes. For example, in a subframe to which the eNB is not assigned paging information, the gNB may transmit SS burst signals. This ensures the timing of SS burst signal transmission in the gNB.

[0641] The information in (4) above may include, for example, information about subframes that the eNB did not actually use for paging transmission. The gNB can use this information to transmit SS burst signals in subframes that were not actually used for paging transmission. Thus, for example, the timing of SS burst signal transmission in the gNB can be ensured.

[0642] The upper-level NW device can notify the gNB of information related to paging from the eNB to the UE. This notification can occur when paging to the UE occurs. The upper-level NW device can notify both the eNB and gNB simultaneously, or at different times. The gNB can use this notification to derive the subframe in which the paging signal will actually be sent from the eNB to the UE. The gNB can then transmit SS burst signals in subframes other than the derived subframe. For example, the timing of SS burst signal transmission in the gNB can be ensured.

[0643] The gNB may not transmit a portion of the signal in an SS burst. For example, the gNB can reduce the number of SS modules transmitted as SS bursts. This, for example, can reduce interference to non-MBSFN subframes in LTE.

[0644] The gNB can reorder the order of the SS modules that constitute an SS burst. This reordering can be performed quasi-statically or periodically. Thus, for example, even in the event of a conflict with a non-MBFSN subframe signal in LTE, the gNB can still send all SS modules to the UE.

[0645] In the above, the reordering of the SS modules can be performed on a subframe basis. For example, if SS modules #0 and #1 are sent in subframe #0, and SS modules #2 and #3 are sent in subframe #1, the order of the SS modules can be reordered so that SS modules #2 and #3 are sent in subframe #0, and SS modules #0 and #1 are sent in subframe #1. This makes reordering control easier, for example.

[0646] As another example, SS modules can be reordered by time slot unit. This allows for reordering of SS modules even when the symbol lengths of LTE and NR differ.

[0647] As another example, SS modules can be reordered by SS module unit. This allows for flexible control, for example, in gNB.

[0648] Figure 35 This is a diagram illustrating an example of SS module reordering in an NR SS burst. Figure 35 In the diagram, the upper segment shows the LTE signal, and the lower segment shows the NR signal. Additionally, within both the upper and lower segments, the left 5 milliseconds represent the signal before SS module reordering, and the right 5 milliseconds represent the signal after SS module reordering. Figure 35 This illustrates the case where the symbol length of NR is the same as that of LTE, and the number of SS modules in NR is 8.

[0649] Figure 35 In the middle, as a non-MBSFN subframe signal from the eNB, SS4501, PBCH4502, PDCCH4503 in the paging signal, and paging signal 4504 are transmitted.

[0650] exist Figure 35 Before the SS modules in the frame are reordered, SS modules #0 (SS module 4510) and #1 (SS module 4511) configured in subframe #0 are not transmitted because they are duplicates of SS4501 and PBCH4502. SS modules #2 (SS module 4512) to #7 (SS module 4517) configured in subframes #1 to #3 are transmitted.

[0651] exist Figure 35 After the SS modules in the subframe are reordered, the SS modules in subframe #0 and subframe #1 are also reordered. As a result, SS modules #2 (SS module 4522) and #3 (SS module 4523) configured in subframe #0 are not transmitted, while SS modules #0 (SS module 4520), #1 (SS module 4521), and #4 (SS module 4514) to #7 (SS module 4517) configured in subframes #1 to #3 are transmitted.

[0652] exist Figure 35 If the reordering cycle is exceeded after the SS modules are reordered, the configuration can be restored to its state before reordering. This, for example, can prevent a continuous stop in transmission for any of the SS modules #0 to #3.

[0653] Figure 36 This is a timing diagram showing the transmission of the SS module of NR, which does not repeat the non-MBSFN signal of LTE. Figure 36 This illustrates the repetition between LTE non-MBFSN subframes and NR SS bursts when the symbol lengths of LTE and NR differ. Figure 36 This illustrates the case where the symbol length of NR is half that of LTE, i.e., the subcarrier spacing of NR is 30kHz, which is a multiple of that of LTE.

[0654] Figure 36 In the NR configuration, SS module #0 (SS module 4610) is transmitted because it is not a duplicate of LTE's SS4601 and PBCH4602. NR's SS module #1 (SS module 4611) is not transmitted because it is a duplicate of LTE's SS4601. NR's SS modules #2 (SS module 4612) and #3 (SS module 4613) are not transmitted because they are a duplicate of LTE's PBCH4602.

[0655] As a method for reordering SS modules, a looping approach can be used. For example, after repeating an SS burst arranged in the order of SS modules #0, #1, #2, #3, #4, #5, #6, #7 a certain number of times, the SS burst arranged in the order of SS modules #6, #7, #0, #1, #2, #3, #4, #5 is repeated a certain number of times. Afterward, an SS burst arranged in the order of SS modules #4, #5, #6, #7, #0, #1, #2, #3 can be sent. This allows for an equal opportunity to acquire SS modules in each beam, thus reducing the maximum time required for terminal synchronization.

[0656] In the method of looping SS modules, the loop unit can be each SS module, each time slot, or each subframe. Furthermore, the loop direction in the time direction can be clockwise or counterclockwise.

[0657] The gNB can notify the UE of information related to the order of the SS modules in the reordered NR. Thus, for example, the UE can continue to capture the SS modules of the NR even after the reordering has occurred.

[0658] This information can be included, for example, in system information. It can also be included in the minimum SI. This information can be broadcast to subordinate UEs or notified as an RMSI (Remaining Minimum System Information). Alternatively, this information can be broadcast as another SI or notified separately to subordinate UEs.

[0659] The broadcast or notification of this information can utilize a carrier different from the carrier of the NR that generated the reordering of the SS modules. This allows the UE to quickly grasp the information, for example. Alternatively, the carrier of the NR that generated the reordering of the SS modules can be used. This reduces signaling load, for example, because the carriers of several other NRs do not need to broadcast or notify information related to the reordering of the SS modules.

[0660] For example, the eNB can broadcast or notify this information. Broadcasts or notifications from the eNB can utilize the same methods as broadcasts or notifications from the gNB. Thus, for example, the UE can quickly grasp this information.

[0661] Alternatively, neither the gNB nor the eNB needs to notify this information. The UE can automatically recapture the NR's SS modules after the SS modules have been reordered. This reduces signaling load.

[0662] As examples of the information contained in this information, the following (1) to (4) are disclosed.

[0663] (1) Information related to the reordering cycle of the SS module.

[0664] (2) Information related to the reordered SS modules.

[0665] (3) Information related to the method of reordering.

[0666] (4) Combinations of (1) to (3) above.

[0667] Regarding (1) above, the period can be, for example, a subframe unit. As another example, it can be a value in terms of the maximum duration of the SS burst (e.g., 5 milliseconds). As another example, it can be a radio frame unit (e.g., 10 milliseconds) or a value in terms of the transmission period of the SS burst.

[0668] Regarding (2) above, for example, this information could be the number of the reordered SS module. For example, in the above... Figure 35 In the example, this information could be SS modules #0, #1, #2, and #3. This allows for flexible SS module reordering, for example. As another example, slot numbers can be used. This allows for reordering even when LTE and NR have different symbol lengths, for example. As another example, subframe numbers can be used. This reduces the processing overhead associated with reordering, for example.

[0669] As another example of (2) above, this information could be related to the reordered unit. Information related to the reordered unit could, for example, be applied in cases utilizing cyclic reordering. The reordered unit could be, for example, an SS module unit, a time slot unit, or a subframe unit.

[0670] Regarding (3) above, for example, the information could be information showing the exchange of SS modules, or it could be information showing a cyclical reordering. The information could include information showing whether the cycle is clockwise or counterclockwise in the time direction.

[0671] The gNB can automatically change the paging transmission timing within a beam by reordering the SS modules corresponding to that beam. The UE can also automatically change its paging reception timing in response to the SS module reordering. The correspondence between the SS module order and the paging transmission timing can be determined using standards. This ensures consistency in the relationship between the SS modules and the paging transmission / reception timing, thus simplifying paging-related control within the gNB.

[0672] The UE can obtain information related to paging reception timing. This information can be obtained after the SS module has reordered the data. Information related to paging reception timing may include, for example, the Control Channel Resource Set (CORESET) containing paging information.

[0673] As another example, the gNB can set the paging transmission timing in this beam to a fixed value. This, for example, makes the paging reception timing in the UE fixed, thus reducing the amount of processing related to paging in the UE.

[0674] The PRACH transmission timing from the UE in the beam that accompanies the reordering of the SS module can be set to the same as the paging transmission and reception timing.

[0675] As another example relating to the priority order between LTE non-MBSFN subframe signals and NR SS burst signals, NR SS burst signals can be prioritized over LTE non-MBSFN subframe signals. This, for example, can reduce interference received by NR SS bursts. The gNB may not transmit any or only a portion of the LTE non-MBSFN subframe signals within subframes that overlap with NR SS bursts. Instead of the overlapping subframes described above, there could be overlapping time slots or overlapping micro-time slots. As another example, the eNB may only omit the LTE non-MBSFN subframe signals that overlap with NR SS burst signals. This prevents unnecessary stops of LTE non-MBSFN subframes.

[0676] The gNB can transmit LTE non-MBSFN subframe signals that repeat the SS burst signal of NR. These two signals can be separable, for example, signals with a predetermined signal pattern. Separable signals can be configured in the same way as those prioritizing the aforementioned LTE non-MBSFN subframe signals. Thus, for example, the UE can receive both LTE and NR signals.

[0677] The eNB can modify the paging transmission timing to its subordinate UEs. For example, this modification can centralize the paging transmission timing to one or more subordinate UEs. This, for example, reduces the overlap between NR's SS burst signal and LTE's paging transmission timing, thus eliminating the need to stop paging transmission in the eNB and reducing interference to NR's SS burst signal.

[0678] As an example of paging timing modification, the POs of subordinate UEs can be centralized into one type. This, for example, avoids the overlap of NR SS burst transmission and LTE paging timing. As an example of a method for centralizing this PO, as described in Non-Patent Document 17 (3GPP TS 36.304V14.4.0), the value of parameter Ns, which indicates the number of subframes allocating paging signals in one radio frame, can be set to 1. The eNB can set the value of parameter Ns to 1 by setting the value of parameter nB, as described in Non-Patent Document 17 (3GPP TS 36.304V14.4.0), to less than one times T. The eNB can broadcast the modified value of parameter nB to its subordinate UEs. This broadcast can, for example, utilize SIB2 (see Non-Patent Document 18 (3GPP TS 36.311)). Thus, for example, the eNB can centralize the POs of subordinate UEs into one type with less signaling.

[0679] The paging transmission timing changes mentioned above can include, for example, changing the paging frame (PF), the paging timing (PO), and the paging transmission period. Multiple of these can be combined.

[0680] When the paging transmission timing changes, the eNB can modify the parameters used to determine the paging transmission timing. This parameter can be, for example, the UE-ID. The eNB can then notify the UE of information related to the change of this parameter.

[0681] The eNB can notify neighboring eNBs of this information. These neighboring eNBs could be, for example, multiple eNBs belonging to the same tracking area as the current eNB. These multiple eNBs can then use this information to page the UE. Thus, for example, paging can be successfully performed even when the UE has moved.

[0682] The eNB can notify the upper-level NW device of this information. This notification can be made via the interface between the upper-level NW device and the base station. The upper-level NW device can be either an AMF or an SMF. The upper-level NW device can send a notification to the eNB indicating whether it agrees to or rejects the parameter change.

[0683] The higher-level NW device can notify its subordinate eNBs of this information. These subordinate eNBs can, for example, be multiple eNBs belonging to the same tracking area as the current eNB. These multiple eNBs can then use this information to page the UE. Thus, for example, paging can be successfully performed even when movement occurs within the UE.

[0684] The eNB can obtain information related to SS bursts of the NR. As information related to SS bursts of the NR, the following (1) to (4) are disclosed.

[0685] (1) NR frame timing.

[0686] (2) Information related to NR's SS.

[0687] (3) Information related to the communication method of NR.

[0688] (4) Combinations of (1) to (3) above.

[0689] The gNB can use the cell search shown in Implementation 1 to obtain the NR frame timing described above (1). The cell search can obtain the P-SS and S-SS of the NR. The eNB can have the function of performing cell search. The eNB can set the timing for performing cell search. As another example, the eNB can request information from the gNB related to the difference between the frame timing of LTE and NR. The gNB can notify the eNB of this information. This request and / or notification can be made using an inter-base station interface, such as the Xn interface. The gNB can obtain the LTE frame timing. For example, the gNB can use cell search to obtain the LTE frame timing. Thus, for example, the eNB can obtain information related to the SS burst of NR.

[0690] The eNB can request the information mentioned in (2) above from the gNB. The gNB then notifies the eNB of the information mentioned in (2). This request and / or notification can be made using an inter-base station interface, such as the Xn interface. The information mentioned in (2) above may be, for example, information related to the symbol series and cyclic offset of the NR's PSS, or information related to the symbol series and cyclic offset of the NR's SSS. The information mentioned in (2) above may include information related to the duration of the NR's SS burst. The information mentioned in (2) above may include information related to the period of the NR's SS burst. The eNB can use the information mentioned in (2) above to perform cell search. Thus, for example, cell search processing in the eNB can be performed quickly. In addition, for example, false detection of NR cells in the eNB can be prevented.

[0691] As another example, the eNB can use cell search to obtain the information mentioned in (2) above. This can, for example, reduce the signaling volume between base stations.

[0692] The information in (3) above may include information related to the multiplexing method of the NR (e.g., TDM, FDM), or information related to the cyclic prefix (e.g., the duration of the cyclic prefix). The information in (3) above may also include information related to the symbol length of the NR. The eNB may request the information in (3) above from the gNB. The gNB may notify the eNB of this information. This request and / or notification may be made using an inter-base station interface, such as the Xn interface. The eNB may use this information to derive the location of the SS burst signal of the NR. Thus, for example, the eNB may quickly obtain information related to the SS burst of the NR.

[0693] As another example of (3) above, the eNB can obtain the information in (3) above through the broadcast information of the NR. Thus, for example, the signaling volume between base stations can be reduced.

[0694] Other solutions are disclosed. LTE non-MBSFN subframe signals and NR SS burst signals can be transmitted simultaneously. These two signals can be separable, for example, signals with a predetermined pattern. Separable signals can be, for example, a combination of LTE SS and NR PBCH, a combination of LTE PBCH and NR SS, or a combination of LTE paging signals and NR SS. The UE can receive the aforementioned repeated signals and separate each signal. For example, the UE can extract the signal with the predetermined pattern and obtain the difference between the original received signal and the extracted signal as the other signal. Thus, for example, the UE can receive both LTE and NR signals.

[0695] Other workarounds are disclosed. Offsets can be set at frame boundaries in LTE and NR. These offsets can be in subframe units, time slot units, or symbol units. The offset can be a unit smaller than a symbol, such as the system's minimum time unit (e.g., Ts).

[0696] gNB and eNB can transmit NR SS burst signals that overlap with LTE non-MBSFN subframe signals. For this transmission, signals that are separable from each other, as disclosed in the above solution, can be transmitted. Thus, for example, LTE non-MBSFN subframe signals and NR SS burst signals can coexist.

[0697] Figure 37 This is a diagram illustrating an example of setting offsets at the frame boundaries in LTE and NR. Figure 37 The example shows a case where the frame boundary of NR is one symbol slower than that of LTE. Figure 37 The example shows the case where LTE and NR have the same symbol length, and the number of SS modules in the NR SS burst is set to 8.

[0698] exist Figure 37 In this configuration, by making the NR frame boundary one symbol slower than the LTE frame boundary, the initial PBCH4710 of NR subframe #0 overlaps with LTE's SS4701. Additionally, the second SS4711 of NR subframe #0 overlaps with LTE's PBCH4702. PBCH4710 and SS4701 are separable, therefore the gNB can transmit PBCH4710. The same applies to NR's SS4711.

[0699] Figure 37 In the example, by allowing the simultaneous transmission of the PBCH of the LTE SS and the initial NR SS module, the non-MBSFN subframes of LTE and the SS bursts of NR can coexist. This allows for rapid UE synchronization capture, for example, in NR.

[0700] The gNB can change the frame timing of the NR. The gNB can notify its subordinate UEs of this change, or it can broadcast it. The gNB can also notify the upper-level NW device of the frame timing change. This notification can utilize the interface between the upper-level NW device and the base station. The upper-level NW device can be an AMF or an SMF. The upper-level NW device can send a notification to the gNB indicating whether it agrees to or rejects the frame timing change. The upper-level NW device can also indicate the frame timing change to its subordinate gNBs. This indication can be directed to gNBs near the gNB. Thus, for example, gNBs near the gNB containing the gNB can ensure that the NR frame timing is consistent among themselves.

[0701] The eNB can change the LTE frame timing. This change can be performed using the same method as the NR frame timing change performed by the gNB described above.

[0702] Information related to frame timing changes in NR and / or LTE can be included in system information, for example. This information can be included in the minimum SI. This information can be broadcast to subordinate UEs or notified as an RMSI (Remaining Minimum System Information). Alternatively, this information can be broadcast as another SI or notified separately to subordinate UEs.

[0703] In broadcasting or notifying information related to this change, a carrier different from the carrier of the NR coexisting with LTE can be used. This allows the UE to quickly grasp the information, for example. Alternatively, in broadcasting or notifying information related to this change, a carrier of the NR coexisting with LTE can be used. This reduces signaling load, for example, because multiple other NR carriers do not need to broadcast or notify information related to this change.

[0704] For example, the eNB can broadcast or notify information related to the change. Broadcasts or notifications from the eNB can utilize the same methods as broadcasts or notifications from the gNB. Thus, for example, the UE can quickly obtain information related to the change.

[0705] Alternatively, both the gNB and eNB can choose not to notify the user of information related to the change. The UE can automatically follow frame timing changes for both LTE and NR. This reduces signaling load.

[0706] Other solutions are disclosed. In NR's SS burst, the configuration of the SS module can be modified. For example, the signal of the NR SS module can be configured in a micro-timeslot. A single SS module can be configured in different micro-timeslots. For example, two of the four symbols of a single SS module can be configured in one micro-timeslot, and the remaining two symbols can be configured in the next micro-timeslot. This modified configuration, for example, can avoid the configuration of LTE's CRS. Thus, for example, mutual interference between the NR SS module and LTE's CRS can be prevented.

[0707] In NR's SS burst, the configuration patterns of multiple SS modules can be predetermined using standards. Multiple patterns can be determined for a single symbol length. The UE can use this pattern information to synchronously capture SS modules. Therefore, the UE can automatically capture SS modules in a configuration with multiple patterns.

[0708] The gNB can notify the UE of information related to configuration changes of the NR's SS module. This information may, for example, indicate whether the SS module configuration of the aforementioned pattern is being used. Thus, for example, the UE can continue to capture the NR's SS module even after the NR's SS module configuration has changed.

[0709] This information can be included, for example, in system information. It can also be included in the minimum SI. This information can be broadcast to subordinate UEs or notified as an RMSI (Remaining Minimum System Information). Alternatively, this information can be broadcast as another SI or notified separately to subordinate UEs.

[0710] The broadcast or notification of this information can utilize a carrier different from the carrier of the NR that generated the configuration change for the SS module. This allows the UE to quickly grasp the information, for example. Alternatively, the broadcast or notification of this information can utilize the carrier of the NR that generated the configuration change for the SS module. This reduces signaling load, for example, because multiple other NR carriers do not need to broadcast or notify information related to the configuration change for the SS module.

[0711] For example, the eNB can broadcast or notify this information. The same methods can be used in broadcasts or notifications from the eNB as those from the gNB. Thus, the UE can quickly grasp this information, for example.

[0712] Alternatively, neither the gNB nor the eNB needs to notify the UE of this information. The UE can automatically recapture the SS module after the NR configuration change. This reduces signaling load.

[0713] The solutions disclosed in Embodiment 4 can be combined with each other. For example, LTE non-MBSFN subframe signals and NR SS burst signals can be transmitted simultaneously, and offsets can be set at the frame boundaries of LTE and NR. Thus, for example, LTE non-MBSFN subframe signals and NR SS burst signals can coexist. In addition, when using different symbol lengths in LTE and NR, LTE non-MBSFN subframe signals and NR SS burst signals can also coexist.

[0714] Figure 38 This is a diagram illustrating an example of an SS burst signal with a modified NR configuration. Figure 38 This illustrates a configuration example where the four symbols of the SS module are divided into two symbols. Additionally, Figure 38 An example is shown where SS is configured with NR in the first two symbols and PBCH is configured with NR in the following two symbols. Additionally, Figure 38In the diagram, the SS module indicated by vertical stripes represents SS, and the SS module indicated by horizontal stripes represents PBCH.

[0715] Figure 38 In NR, SS4810 and PBCH4811 are configured to avoid LTE's CRS4800, SS4801, PBCH4802, and paging signal 4805. NR's SS4820 is configured to avoid CRS4800 in areas overlapping with LTE's PBCH4802. NR's PBCH4821 is configured to overlap with LTE's SS4801. This can be... Figure 38 The LTE SS4801 and NR PBCH4821 shown are configured as separable signals. Additionally, they can be... Figure 38 The LTE PBCH4802 and NR SS4820 shown are configured as signals that can be separated from each other.

[0716] according to Figure 38 As shown in the configuration, the NR SS module signal avoids CRS and is separable from the LTE SS and PBCH, so the NR SS module signal can coexist with the LTE non-MBSFN subframe signal.

[0717] According to this embodiment 4, when LTE and NR coexist, the non-MBSFN subframe signals of LTE and the SS burst signals of NR can coexist, thus balancing communication utilizing both LTE and NR. As a result, the utilization efficiency of the communication system is improved.

[0718] Variation 1 of Implementation Method 4.

[0719] In LTE-NR coexistence, priority communication can be applied. This priority communication can be uplink or downlink. For example, in uplink priority, during uplink transmission from the UE to the eNB, the UE can interrupt uplink communication to the gNB. As another example, in downlink priority, during downlink transmission from the eNB to the UE, the gNB can interrupt the downlink transmission to the UE. The above illustrates an example of priority communication between the gNB and the UE, but the eNB can also engage in priority communication with the UE.

[0720] Priority communication under LTE-NR coexistence can be, for example, in uplink communication from the UE, where the eNB and gNB utilize the same frequency band for uplink communication, thus prioritizing uplink communication under LTE-NR coexistence. Alternatively, priority communication under LTE-NR coexistence can be, for example, in downlink communication to the UE, where the eNB and gNB utilize the same frequency band for downlink communication, thus prioritizing downlink communication under LTE-NR coexistence.

[0721] Applying the above method presents the following problem: A method for priority communication in LTE-NR coexistence is not disclosed. As a result, in LTE-NR coexistence, the following problems arise: an appropriate process for priority communication cannot be implemented, and low-latency / high-reliability communication cannot be guaranteed.

[0722] The following are solutions to the above problems.

[0723] The UE prioritizes uplink transmissions to the base station with which it has priority communication (hereinafter, sometimes referred to as the priority base station). The priority base station can notify the base station that received an interruption through the priority communication (hereinafter, sometimes referred to as the priority base station) of the information indicating that priority was given. As a result, the priority base station can perform decoding processing, for example, by removing the received data at the timing corresponding to the priority communication, thereby improving the reliability of communication between the priority base station and the UE.

[0724] The information described above regarding the occurrence of priority can include information related to the resources that generated the priority. This information can be timing-related, such as subframe number, time slot number, micro-time slot number, or symbol number. It can also include information related to the number of micro-time slots or the number of symbols. Furthermore, it can include frequency band-related information, such as information related to the frequency resources utilized by the priority transmission. It can also include power-related information. The priority base station can use the power-related information to separate priority communication from interrupted communication. This separation can, for example, be used when there is a significant difference in power between priority communication and interrupted communication. Thus, the priority base station can, for example, receive both priority communication and interrupted communication.

[0725] A priority base station can notify a UE performing LTE-NR coexistence of uplink clearance. This notification can, for example, occur during the UE's reception of a downlink signal from the priority base station. Therefore, for example, the UE does not need to switch between LTE and NR downlink receive circuits during uplink clearance reception, thus reducing latency in uplink priority transmission.

[0726] As another method, the priority base station can notify the priority base station of uplink permission information for the UE. The priority base station can then use this uplink permission information to stop uplink reception from the UE. This achieves, for example, the same effect as described above.

[0727] As another method, the priority base station can notify the UE of uplink permission information via the priority base station. This notification via the priority base station can, for example, occur during the UE's reception of downlink signals from the priority base station. The uplink permission can include information indicating that the uplink transmission target is the priority base station. This information could be, for example, an identifier indicating which is the primary / secondary base station, the base station ID, or the cell ID of the transmission target. This notification from the priority base station to the priority base station can be performed using an inter-base station interface (e.g., the Xn interface). The priority base station can use the uplink permission information to stop uplink reception from the UE. The priority base station notifies the UE of the uplink permission information. Thus, for example, the UE does not need to switch between LTE and NR downlink reception circuits along with uplink permission reception, thereby reducing latency in uplink priority transmission.

[0728] In the above, the cessation of uplink reception from the UE in the priority base station can be performed at a timing generated by the priority transmission indicated by the uplink permission.

[0729] The UE can send a Scheduler (SR) for a priority base station via the priority base station. This SR may contain information indicating that the scheduling request target is the priority base station. This information could be, for example, an identifier indicating which base station is primary / secondary, the base station ID, or the cell ID of the transmission target. The priority base station can notify the priority base station of receiving an SR for the priority base station. This notification from the priority base station to the priority base station can utilize an inter-base station interface (e.g., the Xn interface). Thus, for example, the UE does not need to switch uplink transmission circuits for LTE and NR along with the SR transmission, thereby reducing latency in uplink priority transmission.

[0730] In the SR sent from the UE to the prioritized base station, as another example of including information indicating that the scheduling request target is the prioritized base station, the SR procedure can be made different depending on the scheduling request target. For example, the path index of the procedure can be different, the loop offset can be different, or both can be different. The prioritized base station can use this SR procedure to determine the scheduling request target. Thus, for example, the amount of information in the SR can be reduced.

[0731] As another example, the DMRS procedure accompanying the PUCCH containing the SR can be made different depending on the scheduling request target. The prioritized base station can use this DMRS procedure to determine the scheduling request target. Thus, similarly to the above, the amount of information in the SR can be reduced, for example.

[0732] The priority base station can configure the SR (Signal Sending Message) sent to it by the UE. This configuration can be made directly to the UE by the priority base station or through the priority base station.

[0733] The prioritized base station can configure the SR (Signal Transmission) sent by the UE to the prioritized base station via this base station. The SR configuration may include settings related to the SR transmission period and offset, settings related to the maximum number of retransmissions of the SR, and settings related to the frequency resources of the SR. The SR configuration may also include settings related to the procedure for transmitting the SR. These procedure-related settings may, for example, be settings related to the path index or settings related to the cyclic offset. The SR configuration may also include information related to the procedure of the DMRS (Device Management System) attached to the PUCCH containing the SR.

[0734] The settings relating to the SR sent by the UE to the priority base station and the settings relating to the SR sent by the UE to the priority base station via the priority base station can be different from each other, or they can be the same. They can also be partially the same.

[0735] The settings of the SR sent by the UE to the priority base station via the priority base station and the settings of the SR sent by the UE to the priority base station can be at least partially different. For example, the cyclic offsets of the procedures for sending the SR can be different from each other. As another example, the procedures used by the DMRS attached to the PUCCH containing the SR can be different from each other. Thus, for example, the priority base station can determine whether the SR is for its own base station or for the SR sent via the priority base station. As a result, malfunctions in the priority base station can be prevented.

[0736] The priority base station can request the priority base station to perform the SR settings sent by the priority base station to the priority base station. This request may include, for example, information related to the settings of the SR. The priority base station can use this information to configure the SR for the UE.

[0737] The request to be executed can be included in signaling on the inter-base station interface (e.g., the Xn interface). This signaling can be, for example, a Sub-base Station Modification Request (SN Modification Request), a Sub-base Station Addition Request (SN Addition Request), or a Sub-base Station Modification Confirmation (SN Modification Confirmation) signaling. These three signaling methods can be used, for example, when the primary base station is the main base station. As another example, the signaling can be a Sub-base Station Modification Request Acknowledge response, a Sub-base Station Addition Request Acknowledge response, or a notification indicating the existence of a Sub-base Station Modification Required (SN Modification Required). These three signaling methods can be used, for example, when the primary base station is the sub-base station. This signaling can be other signaling methods, or new signaling can be set.

[0738] The priority base station can configure the SR (Service Request) sent to it by the priority base station to the UE. The information included in the SR configuration can be the same as described above. The priority base station can request information from the priority base station related to the SR configuration sent to it by the priority base station. The priority base station can then notify the priority base station of this information. This information can, for example, be the same as the SR configuration described above. As another example, this information can include information related to an SR already assigned by the priority base station. The SR configuration sent from the priority base station to the UE can utilize the information notified from the priority base station. This, for example, prevents duplication of the SR configuration with the SR configuration already assigned by the priority base station. As a result, interference in the priority base station can be reduced, and malfunctions can be prevented.

[0739] RRC signaling can be used in the SR settings from the priority base station to the UE, transmitted from the priority base station to this base station. For example, the RRC connection reconfiguration signaling from the priority base station to the UE can include information related to the SR settings. This can, for example, reduce the signaling volume from the priority base station to each UE. As other examples, MAC information or L1 / L2 signaling can be used. This can, for example, allow for rapid execution of the SR settings from the priority base station to the UE.

[0740] The request from the priority base station to the priority base station concerning information related to the settings of the SR sent by the priority base station to this base station can utilize signaling from an inter-base station interface, such as the Xn interface. This signaling can be the same signaling as the request from the priority base station to the priority base station concerning the settings of the SR sent by the priority base station to the priority base station by the UE.

[0741] From the notification from the prioritized base station regarding the settings of the SR (Security Request), signaling via an inter-base station interface, such as the Xn interface, can be used. This signaling can be, for example, a Sub-Base Station Modification Request Acknowledge response, a Sub-Base Station Addition Request Acknowledge response, or a notification indicating the existence of a Sub-Base Station Modification Required. These three signaling methods can be used, for example, when the prioritized base station is the primary base station. As another example, a Sub-Base Station Modification Confirmation can also be used. This signaling can be used, for example, when the prioritized base station is a secondary base station. This signaling can be other signaling methods or can be newly set.

[0742] Combinations of the aforementioned SR settings can also be used. For example, a priority base station can configure both the SR directly sent to itself and the SR sent to itself via the prioritized base station for the UE. This configuration can be performed using the same signaling or different signaling. As another example, the priority base station configures the SR directly sent to itself for the UE, while the prioritized base station configures the SR sent to the priority base station via its own signaling for the UE.

[0743] The UE can send a Service Request (SR) to either a priority base station or a base station that is being prioritized. This transmission can, for example, be directed to the base station whose transmission timing is earlier than the one in the UE. Thus, for example, rapid transmission of the SR from the UE can be performed with less processing power. As another example, the transmission can be directed to the base station whose SR arrives at the priority base station faster. In transmitting the SR to the base station whose SR arrives at the priority base station faster, for example, the communication delay of the inter-base station interface can be used as decision material in the UE. This communication delay can be notified to the UE in advance. Thus, the priority base station can receive the SR quickly.

[0744] The UE can send SRs to both the priority base station and the priority base station. This, for example, improves the reliability of SR transmission. As described above, the SR retransmission prohibition timer can be set separately for direct SR transmission to the priority base station and for SR transmission via the priority base station. This, for example, avoids complexity in SR control. As another example, the SR retransmission prohibition timer can be shared for both direct SR transmission to the priority base station and SR transmission via the priority base station. In the SR retransmission prohibition timer, the UE can send an SR only once to a base station that is not the target of the SR transmission that initiated the timer.

[0745] The aforementioned SR settings, for example, in the setting of SR transmission timing, can avoid utilizing information related to the allocation between base stations from the UE's uplink signal reception timing. In the aforementioned SR transmission timing, the UE may not transmit SRs for the priority base station and / or the priority base station. That is, the transmission of SRs from the UE to each base station can be performed at a timing corresponding to the aforementioned SR transmission timing, allocated to that base station from the UE's uplink signal reception timing. For example, if the uplink signal reception timing from the UE is allocated to the priority base station, the UE may not perform the SR transmission at the timing specified for the priority base station. This, for example, avoids the complexity of SR settings during LTE-NR coexistence.

[0746] As another example, in the above-described SR settings, information related to the allocation between base stations regarding the uplink signal reception timing from the UE can be utilized. For instance, the transmission timing of the SR in the UE can be set from the timing in which the uplink signal reception timing from the UE is allocated to the target base station for the SR transmission. As another example, the transmission timing settings of the SR in the UE can be used to set the uplink signal reception timing from the UE in the target base station for the SR transmission. Thus, for example, the uplink signal reception timing from the UE is allocated to the target base station for the SR transmission in the SR transmission timing, and therefore, for example, the SR transmission from the UE can be performed quickly.

[0747] Multiple settings can be configured for the SRs sent from the UE to each base station. For example, in the SR sent from the UE to a priority base station, two settings can be used: one with a period of 5 milliseconds and a subframe offset of 0, and the other with a period of 5 milliseconds and a subframe offset of 2. This improves the flexibility of SR settings.

[0748] The SR-related settings described above can be applied to settings related to other UCIs. For example, the SR-related settings described above can be applied to CSI settings. Thus, for example, transmissions of other UCIs can achieve the same effect as SR transmissions.

[0749] Priority can also be applied to SRs sent from the UE to the priority base station. For example, the UE can interrupt uplink transmission to the priority base station and send the SR to the priority base station instead. After the SR is sent, the UE can choose to resume uplink transmission to the priority base station or not. Thus, the UE can, for example, quickly notify the SR.

[0750] In the above, the UE can use settings related to the SR sent to the priority base station to perform the transmission of the SR. That is, the UE can use information related to the SR transmission timing contained in the settings (e.g., SR transmission period, SR transmission offset) to transmit the SR.

[0751] In the transmission timing of the SR (Signal Transmission) sent from the UE to the priority base station, the priority base station may not allocate uplink transmissions from the UE to itself. These uplink transmissions may include, for example, PUSCH, DMRS, PUCCH, SRS, or other uplink signals. The priority base station may notify the priority base station of information related to the settings of the SR transmissions from the UE to itself. The priority base station can use this notification to determine or change the allocation of uplink transmission timings from the UE to itself.

[0752] As another example, a priority base station can be configured to remove the timing for transmitting an SR (Signal Transfer Signal) from the timing of uplink transmissions from the UE to the priority base station. This uplink transmission can be, for example, DMRS, SRS, or other uplink signals. The priority base station can query the priority base station for information related to the timing of generating the uplink transmission. The priority base station can then notify the priority base station of this information. The priority base station can use this notification to inform the priority base station of information related to the settings for SR transmissions from the UE to its base station. It can be configured to remove the timing for transmitting an SR from the UE to the priority base station from the timing of uplink transmissions from the UE to the priority base station.

[0753] The priority base station notifies the priority base station of information related to the timing at which uplink priority transmission may occur. This information may be the same as that shown in Embodiment 3. The priority base station can then stop uplink reception from the UE at that timing. This can, for example, reduce the delay in uplink priority transmission.

[0754] The UE notifies the priority base station of the information indicating the generation of priority transmission data. This information can be provided using a predefined symbol, for example. This symbol can be the same as that shown in Variation 1 of Implementation 3. The UE can notify the priority base station of this information after the priority transmission data is generated. This can, for example, reduce latency in uplink priority transmission.

[0755] In the above, the information from the UE to the priority base station can be notified via the priority base station. This notification via the priority base station can, for example, occur during the UE's uplink signal transmission to the priority base station. The notification from the priority base station to the priority base station can utilize an inter-base station interface (e.g., the Xn interface). Therefore, for example, the UE does not need to switch between LTE and NR uplink transmission circuits during SR transmission, thus reducing latency in uplink priority transmission.

[0756] Other solutions are disclosed. In downlink priority communication, the priority base station can notify the priority base station of information indicating that priority transmission has occurred. This information may include, for example, information related to the timing of the downlink priority, or information related to the scheduling of downlink priority communication. The priority base station can then stop downlink transmission at the priority transmission timing. This reduces interference in downlink priority communication.

[0757] The prioritized base station can notify the UE of this situation, indicating that priority communication has occurred. This notification can occur before or after the notification made by the priority base station to the prioritized base station. The UE can use this notification to switch between LTE and NR downlink receive circuits. This, for example, can reduce latency in downlink priority communication.

[0758] In the aforementioned notification to the UE, a predefined symbol may be used, for example. This symbol may be the same as the symbol shown in Variation 1 of Implementation 3. The UE can receive this symbol to switch between LTE and NR downlink receive circuits. This, for example, can further reduce latency in downlink-priority communication.

[0759] Priority base stations can query the priority base stations in advance for priority or non-priority time slots.

[0760] The base station being prioritized can notify the base station in advance of information related to the timing at which priority communication is possible. This notification can occur, for example, after the aforementioned query or without such query. This information can be related to the timing at which priority communication is not possible. The timing at which priority communication is not possible could be, for example, the timing at which the prioritized base station sends a synchronization signal, the timing at which it sends a notification message, or the timing at which it sends a PDCCH. Using this information, the base station can choose to perform priority communication or not. For example, the base station can perform priority transmission at a timing when priority is possible.

[0761] Information related to timings that allow or disallow priority communication may include, for example, information about the priority or non-priority subframes, information about the period during which the subframe is repeated, and information about the duration of the priority or non-priority timing. A non-priority subframe may be, for example, a subframe transmitting an SS (synchronization signal) burst in an NR, or any other subframe. In the above, a subframe can be a radio frame, a time slot, a micro-time slot, or a symbol. This information may also be a combination of multiple pieces of information. As another example, this information may be presented as a bitmap indicating the priority or non-priority symbols. These symbols can be subframes, time slots, micro-time slots, or other time units. This information may be presented periodically or aperiodically. This information may include information related to the period to which the information is received. Thus, for example, flexibility in setting priority or non-priority timing can be improved.

[0762] Other solutions are disclosed. In downlink priority communication, the priority base station can notify the UE of information indicating that priority transmission has occurred. This information may include, for example, information related to the timing of the downlink priority, or information related to the scheduling of the downlink priority communication. This notification to the UE can be made via the priority base station. The UE can use this notification to extract the priority communication data from the received downlink signals. As an extraction method, for example, a method for correcting the offset of the DC component between LTE and NR can be used. This can, for example, reduce the signaling load between the base station and the UE before priority communication.

[0763] The solutions disclosed in Modification 1 can be combined with each other. For example, the priority base station can notify the priority base station of information indicating that priority transmission has occurred. The priority base station can use this information to stop downlink transmission at the timing of priority communication. Alternatively, the priority base station can notify the UE of information indicating that priority transmission has occurred. The UE can use this notification to extract the priority communication data from the received downlink signals. Thus, for example, the signaling volume between the base station and the UE before priority communication can be reduced, and interference with downlink communication can be reduced.

[0764] According to this variation 1, priority communication can be performed when LTE-NR coexist. Therefore, low-latency / high-reliability communication can be achieved when LTE-NR coexist.

[0765] Variation 2 of Implementation Method 4.

[0766] In LTE-NR coexistence, the following problem arises: When the timing of PUCCH and / or SRS transmissions from the UE to the NR base station conflicts with the timing of PUCCH and / or SRS transmissions from the UE to the LTE base station, the communication system lacks a defined procedure for handling this conflict. Therefore, malfunctions may occur in the communication system.

[0767] As a solution to the above problems, the method shown in variation 1 of embodiment 5 described later can be applied.

[0768] For example, the following can be applied. Figure 41 The example shown illustrates this. A UE can transmit both a PUCCH to an LTE base station and a PUCCH to an NR base station within the same subframe.

[0769] According to this variation 2, malfunctions caused by conflicts between LTE and NR PUCCH and / or SRS can be prevented.

[0770] Implementation method 5.

[0771] In LTE and NR DCs, the UE can switch between simplex TX transmitted by switching one transmitter in LTE and NR, and between full-duplex TX transmitted using their respective transmitters in LTE and NR. The switching between simplex TX and full-duplex TX can be achieved, for example, through DC settings and / or switching.

[0772] The primary base station can determine the handover between simplex (TX) and duplex (TX) and notify the UE. This determination can utilize the Maximum Sensitivity Degradation (MSD), which represents the maximum reduction in sensitivity caused by uplink transmission on one carrier to downlink reception on another carrier.

[0773] The following provides an example of the process for switching between simplex TX and duplex TX in LTE and NR DC.

[0774] The UE notifies the primary base station of information relating to combinations of carriers that can be used concurrently. This combination may be included in the UE's capabilities. For example, this combination may be a combination of carriers that satisfy the conditions for utilizing the MSD specified in the standard. The primary base station uses the information relating to the carrier combinations to derive the MSD within that combination.

[0775] The UE notifies the base station of the carrier signal measurement results. The primary base station determines the carrier to be used in the CA and / or DC. Additionally, the primary base station determines whether the UE uses simplex TX or duplex TX. The primary base station makes this decision using the MSD value. For example, the primary base station may determine the carrier combination with higher receive sensitivity considering the MSD as the carrier to be used in the CA and / or DC. As another example, the primary base station determines to use simplex TX if the MSD value in the carrier combination used is above or greater than a specified threshold. In this decision, the primary base station can derive the MSD of the aforementioned carrier combination according to a standard.

[0776] The primary base station will notify the UE of the information regarding the carrier being used and / or whether the UE is using simplex TX or duplex TX. This notification can be made using RRC-specific signaling, such as RRC connection reconfiguration signaling.

[0777] Applying the above method leads to the following problem: the information regarding whether simultaneous transmission by the two transmitters in the UE is permitted does not reflect the actual UE performance. As a result, this leads to low communication efficiency in the communication system.

[0778] The solutions to the aforementioned problems are disclosed. In determining the carrier used in CA and / or DC, and / or in determining the handover between simplex TX and duplex TX, the UE's Sensitivity Degradation (SD) is utilized. The primary base station can use information related to SD to perform handover between simplex TX and duplex TX. This handover can, for example, be a quasi-static handover. A quasi-static handover can, for example, be a handover utilizing RRC signaling.

[0779] The SD can be a pre-determined value. For example, it can be the SD measured at the time of shipment or the SD measured during use. The SD measured during use could be, for example, the SD measured during calibration.

[0780] As examples of information used by the main base station in determining the handover between simplex TX and duplex TX, the following (1) to (8) are disclosed.

[0781] (1) Information related to SD.

[0782] (2) Information related to whether duplex TX is permitted.

[0783] (3) Information related to MSD.

[0784] (4) Information related to whether simplex TX is permitted.

[0785] (5) Information related to the UE’s transmit power.

[0786] (6) Shows information about a portion of the frequency band of the carrier using gNB.

[0787] (7) Information related to frame timing.

[0788] (8) Combinations of (1) to (7) above.

[0789] The information shown in (1) above can be set for each combination of carriers. Thus, for example, the base station can select a combination of carriers with less sensitivity degradation. Alternatively, the information related to SD can be set for each combination of frequency bands. Thus, for example, the amount of information related to SD can be reduced.

[0790] The information shown in (1) above could be, for ...

Claims

1. A communication system comprising a user equipment and a plurality of base stations that wirelessly communicate with the user equipment, characterized in that, The plurality of base stations include a primary base station and a secondary base station constituting dual connectivity for the user equipment. The primary base station is configured to set a first license configuration related to unlicensed transmission of the uplink for each of the more than one cells formed by the primary base station, and the secondary base station is configured to set a second license configuration related to unlicensed transmission of the uplink for each of the more than one cells formed by the secondary base station. The user equipment is configured to, The system receives configuration information from the main base station indicating that the first license configuration and the second license configuration are set independently of each other. Based on the first license configuration, uplink transmission is performed for the main base station. Based on the second license configuration, uplink transmission is performed for the secondary base station.

2. The communication system as described in claim 1, characterized in that, The unlicensed transmission based on the second license configuration is an uplink transmission that does not require a license provided by the secondary base station based on a request from the user equipment. The unlicensed transmission based on the first license configuration is an uplink transmission that does not require a license provided by the main base station based on a request from the user equipment.

3. The communication system as described in claim 1, characterized in that, The secondary base station notifies the primary base station of the second license configuration. The main base station will notify the user equipment of the second license configuration.

4. The communication system as described in claim 1, characterized in that, The secondary base station notifies the user equipment of the L1 setting, which is used to determine the setting of the second license configuration.

5. The communication system as described in claim 1, characterized in that, The secondary base station will notify the user equipment of some or all of the RRC settings corresponding to the second license configuration.

6. The communication system as described in claim 1, characterized in that, The secondary base station will notify the primary base station of the changes to the configuration of the second license. The primary base station will notify the user equipment of the information received from the secondary base station.

7. The communication system as described in claim 1, characterized in that, The secondary base station will notify the primary base station of the cancellation of the unlicensed transmission based on the second license configuration. The primary base station will notify the user equipment of the information received from the secondary base station.

8. The communication system as described in claim 1, characterized in that, The primary base station sets the first license configuration in packet replication.

9. The communication system as described in claim 1, characterized in that, The user equipment measures the Quality of Service (QoS) value and the latency of uplink packet data.

10. The communication system as described in claim 1, characterized in that, The secondary base station applies the second license configuration to the SCG bearer or fork bearer corresponding to the secondary base station.

11. The communication system as described in claim 1, characterized in that, At least one of the base stations sets a license configuration related to unlicensed transmission of the uplink in carrier aggregation.

12. The communication system as described in claim 11, characterized in that, In the carrier aggregation with the aforementioned permission configuration set, packet replication is also configured.

13. The communication system as described in claim 1, characterized in that, The secondary base station sets the second license configuration in packet replication.

14. The communication system as described in claim 1, characterized in that, In radio resources where unlicensed transmission is configured, the user equipment performs uplink transmissions according to the priority order based on information notified using RRC signaling.

15. The communication system as described in claim 14, characterized in that, The priority order followed by the user equipment is a priority order corresponding to the channel.

16. A user equipment, comprising a user equipment and a plurality of base stations wirelessly communicating with the user equipment, wherein the user equipment is characterized in that... The plurality of base stations include a primary base station and a secondary base station constituting dual connectivity for the user equipment. The master base station is configured to set a first license configuration related to unlicensed transmission on the uplink for each of the more than one cells formed by the master base station. The secondary base station is configured to set a second permission configuration related to unlicensed transmission of the uplink for each of the more than one cells formed by the secondary base station. The user equipment is configured to, The system receives configuration information from the main base station indicating that the first license configuration and the second license configuration are set independently of each other. Based on the first license configuration, uplink transmission is performed for the primary base station, and based on the second license configuration, uplink communication is performed for the secondary base station.

17. A main base station, which is a main base station in a communication system including a user equipment and multiple base stations that respectively communicate wirelessly with the user equipment, characterized in that, The plurality of base stations include a primary base station and a secondary base station constituting dual connectivity for the user equipment. The master base station is configured to set a first license configuration related to unlicensed transmission on the uplink for each of the more than one cells formed by the master base station. The secondary base station is configured to set a second permission configuration related to unlicensed transmission of the uplink for each of the more than one cells formed by the secondary base station. The main base station is configured to send configuration information to the user equipment in which the first license configuration and the second license configuration are set independently of each other.

Images