WO2022201476A1

WO2022201476A1 - Base station, and system

Info

Publication number: WO2022201476A1
Application number: PCT/JP2021/012733
Authority: WO
Inventors: 眞人谷口; 皓平原田
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2021-03-25
Filing date: 2021-03-25
Publication date: 2022-09-29
Also published as: JPWO2022201476A1

Abstract

A base station comprising a transmission unit that transmits information, which is to be used for determining whether or not to permit UE to autonomously deactivate a particular cell group in a dual connectivity, to another base station configuring said dual connectivity.

Description

Base station and system

The present invention relates to base stations in wireless communication systems.

In the 3GPP (3rd Generation Partnership Project), 5G or NR (New Radio) and A radio communication system called "NR" (the radio communication system is hereinafter referred to as "NR") is under study. In 5G, various radio technologies and network architectures are being studied in order to meet the requirements of realizing a throughput of 10 Gbps or more and keeping the delay in the radio section to 1 ms or less (for example, Non-Patent Document 1).

Furthermore, in 3GPP standardization, the function of activating/deactivating the secondary cell group (Activation/Deactivation) in dual connectivity operation (for example, Non-Patent Document 2) is being considered with the main purpose of reducing the power consumption of the terminal. there is For example, an operation that is not performed when the secondary cell group is disabled is specified to reduce power consumption.

　Network triggers and terminal triggers are being considered as triggers for deactivating secondary cell groups. Here, when a free trigger by the terminal is operated, depending on the implementation of the terminal, the secondary cell group may be activated/deactivated unintended by the network, increasing signaling and making it difficult to control from the network. there is a risk of becoming

Therefore, for example, it is conceivable that the network instructs the terminal whether or not the terminal autonomous deactivation of the secondary cell group is permitted, and only the terminal that is instructed to permit autonomous deactivation of the secondary cell group. be done.

However, with conventional technology, there is a problem that each node that configures dual connectivity may not have information for determining whether a terminal can operate autonomously.

The present invention has been made in view of the above points, and in a node of a wireless communication system that performs dual connectivity, a technology that enables acquisition of information necessary for determining whether a terminal can operate autonomously. intended to provide

According to the disclosed technology, the information used for determining whether to allow the terminal to autonomously deactivate a specific cell group in dual connectivity, other than configuring the dual connectivity A base station is provided comprising a transmitter for transmitting to a base station of .

According to the disclosed technology, a technology is provided that enables a node of a wireless communication system that performs dual connectivity to acquire information necessary for determining whether a terminal can operate autonomously.

1 is a diagram for explaining an example (1) of a wireless communication system according to an embodiment of the present invention; FIG. FIG. 2 is a diagram for explaining example (2) of a wireless communication system according to an embodiment of the present invention; It is a figure for demonstrating the example of whole operation|movement. FIG. 10 is a diagram for explaining Example 1-1; FIG. 10 is a diagram for explaining Example 1-3; FIG. 10 is a diagram for explaining Example 2-1; FIG. 10 is a diagram for explaining Example 2-1; FIG. 10 is a diagram for explaining Example 2-1; FIG. 10 is a diagram for explaining Example 2-1; FIG. 10 is a diagram for explaining Example 2-1; FIG. 10 is a diagram for explaining Example 2-1; FIG. 10 is a diagram for explaining Example 2-1; FIG. 10 is a diagram for explaining Example 2-2; It is a figure showing an example of functional composition of base station 10 in an embodiment of the invention. 2 is a diagram showing an example of the functional configuration of terminal 20 according to the embodiment of the present invention; FIG. 2 is a diagram showing an example of the functional configuration of terminal 20 according to the embodiment of the present invention; FIG. It is a figure which shows an example of the hardware constitutions of the apparatus in embodiment of this invention.

Embodiments of the present invention will be described below with reference to the drawings. In addition, the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

For the operation of the wireless communication system according to the embodiment of the present invention, existing technology may be used as appropriate. The existing technology is, for example, existing NR or LTE, but is not limited to existing NR or LTE.

FIG. 1 is a diagram for explaining example (1) of a wireless communication system according to an embodiment of the present invention. A wireless communication system according to an embodiment of the present invention includes a base station 10 and terminals 20, as shown in FIG. Although one base station 10 and one terminal 20 are shown in FIG. 1, this is an example and there may be more than one.

The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. A physical resource of a radio signal is defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. Also, a TTI (Transmission Time Interval) in the time domain may be a slot, or a TTI may be a subframe.

The base station 10 can perform carrier aggregation in which multiple cells (multiple CCs (component carriers)) are bundled and communicated with the terminal 20 . In carrier aggregation, one PCell (primary cell) and one or more SCells (secondary cells) are used.

The base station 10 transmits a synchronization signal, system information, etc. to the terminal 20. Synchronization signals are, for example, NR-PSS and NR-SSS. System information is transmitted, for example, on NR-PBCH or PDSCH, and is also called broadcast information. As shown in FIG. 1, the base station 10 transmits control signals or data to the terminal 20 on DL (Downlink) and receives control signals or data from the terminal 20 on UL (Uplink). Here, what is transmitted on control channels such as PUCCH and PDCCH is called a control signal, and what is transmitted on a shared channel such as PUSCH and PDSCH is called data. is.

The terminal 20 is a communication device having a wireless communication function, such as a smartphone, mobile phone, tablet, wearable terminal, or M2M (Machine-to-Machine) communication module. As shown in FIG. 1 , the terminal 20 receives control signals or data from the base station 10 on the DL and transmits control signals or data to the base station 10 on the UL, thereby performing various functions provided by the wireless communication system. Use communication services. Note that the terminal 20 may be called UE, and the base station 10 may be called gNB. Also, in dual connectivity, one base station 10 may be called a gNB and the other base station may be called an eNB.

FIG. 2 is a diagram for explaining example (2) of the wireless communication system according to the embodiment of the present invention. FIG. 2 shows a configuration example of a wireless communication system when dual connectivity (DC) is performed. As shown in FIG. 2, a base station 10A serving as a master node (MN: Master Node) and a base station 10B serving as a secondary node (SN: Secondary Node) are provided. The base station 10A and the base station 10B are connected to the core network 30 respectively. Terminal 20 can communicate with both base station 10A and base station 10B.

The cell group provided by the MN base station 10A is called a master cell group (MCG), and the cell group provided by the SN base station 10B is called a secondary cell group (SCG). call. In dual connectivity, an MCG is composed of one PCell and 0 or more SCells, and an SCG is composed of one PSCell (Primary SCG Cell) and 0 or more SCells.

Note that the dual connectivity applied in this embodiment may be a communication method using two communication standards, and any communication standards may be combined. For example, the combination may be any of LTE and LTE, NR and NR, NR and LTE, NR and 6G standard, or LTE and 6G standard. Also, when the two communication standards are different, either of the two may be applied to the MN or may be applied to the SN. For example, taking the combination of NR and LTE as an example, the MN may be NR and the SN may be LTE, or the SN may be LTE and the MN may be LTE. Also, dual connectivity may be a communication method using three or more communication standards, and may be called by other names different from dual connectivity.

The processing operations in the present embodiment are assumed to be executed with the system configuration shown in FIG. 2, but may be executed with a system configuration other than the system configuration shown in FIG.

　In 3GPP standardization, a function to activate/deactivate a secondary cell group in dual connectivity operation is being considered with the main purpose of reducing the power consumption of terminals. For example, an operation that is not performed when the secondary cell group is disabled is specified to reduce power consumption.

For example, when the secondary cell group is enabled, PDCCH monitoring, RRM (Radio Resource Management) measurement, RLM (Radio Link Monitoring), beam failure detection/recovery, CSI-RS (Channel State Information--Reference Signal) measurement and reporting, timing advance setting, and SRS (Sounding Reference Signal) transmission are executed.

On the other hand, if the secondary cell group is deactivated, for example, PDCCH monitoring and SRS transmission may not be performed.

Note that RRM measurements are measurements related to mobility such as handover and PSCell change. RLM is monitoring to detect DL loss of synchronization. Beam failure detection/recovery is a function for the terminal 20 to detect and recover from beam deviance. Timing advance is information for maintaining UL synchronization.

For example, SCG activation may be requested by the MN, SN or UE. Also, RRC signaling between MN and UE or between MN and SN may be used for SCG activation or SCG deactivation.

A NW trigger and a terminal 20 trigger are being considered as triggers for deactivating the secondary cell group.

In the case of triggering by the NW, for example, the terminal 20 transmits a request or assistance information to the NW, and the NW notifies the terminal 20 of the final SCG deactivation instruction.

In the case of a trigger by the terminal 20, for example, the terminal 20 autonomously deactivates the SCG and notifies the NW of the deactivation.

When the above NW trigger is used, there is a possibility of increased signaling due to frequent SCG de-/re-activation, so in this embodiment, the explanation will be given for terminal-autonomous SCG deactivation. A first problem and a second problem will be described below as problems with the technology according to the present embodiment.

(First issue)
As described above, in the present embodiment, the terminal 20 autonomously deactivates the SCG and notifies the NW of the deactivation. In this case, for example, the terminal 20 notifies the MN 10A that it has been deactivated. MN 10A then notifies SN 10B that the SCG has been deactivated.

When MN 10A notifies SN 10B that the SCG has been deactivated, it is possible to use, for example, the MN initiated SN modification procedure (Non-Patent Document 2). However, in the prior art, in the MN initiated SN modification procedure, SN 10B can decide whether to accept or reject the request received from MN 10A. That is, SN 10B has the veto right.

On the other hand, in terminal 20 autonomous deactivation, terminal 20 will notify the NW that it has already been deactivated, so SN 10B should not reject the notification from MN 10A. However, the conventional technology has a problem that the SN 10B cannot determine that the notification from the MN 10A should not be rejected. This is the same for notification from SN 10B to MN 10A.

(Second issue)
As described above, in the present embodiment, terminal 20 autonomously performs SCG deactivation. However, if operations such as the timing of SCG deactivation are left to the implementation of the terminal, operations unintended by the operator may occur. For example, excessive deactivation may cause deterioration in communication quality, increased signaling, and the like.

As a countermeasure, this embodiment assumes that the NW notifies the terminal 20 of an instruction (flag) for controlling whether or not UE autonomous SCG deactivation is possible.

However, there is a problem that the NW side, that is, MN 10A or SN 10B, may not have the information for determining whether to permit or disallow terminal autonomous SCG deactivation.

Hereinafter, Example 1 will be described as an example corresponding to the first problem, and Example 2 will be described as an example corresponding to the second problem. An example of the overall basic operation including

Below, deactivation is mainly referred to as "deactivation". Further, in the following description, as an example, deactivation of an activated SCG is described, but the same operation is possible when activating a deactivated SCG.

Also, in the following explanation, the target of deactivation is the SCG, but this is an example. The deactivation target may be a specific cell group other than the SCG.

(basic operation example)
A basic operation example in this embodiment will be described with reference to FIG. At S101, negotiation takes place between MN 10A and SN 10B. Specifically, for example, transmission and reception of information necessary for determining whether or not UE autonomous SCG deactivation is possible are performed between MN 10A and SN 10B.

MN 10A, for example, determines whether UE autonomous SCG deactivation for terminal 20 is possible based on its own information and information received from SN 10B, and transmits a flag based on the determination result to terminal 20 in S102.

Here, it is assumed that the SCG is active, the terminal 20 is communicating with the MCG and SCG, and the content of the flag is "UE autonomous SCG deactivation allowed". Note that the above flag may be sent to the terminal 20 together with a message for setting the SCG.

The terminal 20 that received the flag in S102 determines that UE autonomous SCG deactivation is possible.

In S103, the terminal 20 autonomously deactivates the SCG, for example, because communication using the SCG is no longer necessary. In S104, the terminal 20 notifies the MN 10A that the SCG has been deactivated. In S105, the MN 10A notifies the SN 10B that the terminal 20 has deactivated the SCG. In this embodiment, SN 10B does not reject this notification because it can judge that it cannot reject it.

In the example shown in FIG. 3, the MN 10A notifies the terminal 20 of the flag, but this is an example, and the SN 10B may notify the terminal 20 of the flag. Also, the terminal 20 may notify the SN 10B that the SCG has been deactivated.

Examples 1 and 2 will be described below. In addition, Example 1 and Example 2 can be combined and executed. Also, the first and second embodiments may be executed independently.

(Example 1)
In the first embodiment, in order to solve the first problem described above, the fact that the terminal 20 has already performed SCG deactivation is notified between MN 10A and SN 10B instead of a request for SCG deactivation. The nodes (MN 10A, SN 10B) that have received the notification can determine that the notification is not a request but an information notification that SCG deactivation has already been performed, and thus can determine that it is not subject to acceptance/rejection.

Examples 1-1 to 1-3 will be described as specific procedure examples in Example 1.

<Example 1-1>
In Example 1-1, in the MN initiated SN modification procedure, the terminal 20 notifies that the SCG deactivation has already been performed.

The MN initiated SN modification procedure is a procedure for changing resource settings (eg addition, correction, release of SCG resources) on the SN 10B side of the terminal 20. FIG. 4 shows an example of the MN initiated SN modification procedure. FIG. 4 is "Figure 10.3.2-1: SN Modification procedure-MN initiated" described in Non-Patent Document 2.

It should be noted that the MN initiated SN modification procedure applied in Example 1-1 is not limited to that shown in FIG. MN initiated SN modification procedures other than those shown in FIG. 4 may be applied. FIG. 4 is an example given for explanation.

In Example 1-1, in the procedure shown in FIG. 4, information notification is performed by, for example, one of the following methods (1) to (4). Here, it is assumed that the MN 10A has received a notification that the SCG has been deactivated from the terminal 20 before step 1 in FIG. 4 is started.

(1) MN 10A, for example, in step 1 in FIG. 4, in the SN Modification Request message, a specific IE (information element) indicating UE-Triggered SCG deactivation (terminal 20 autonomously performed SCG deactivation) and send an SN Modification Request message including the IE to SN 10B.

Also, MN 10A includes a specific value indicating UE-Triggered SCG deactivation (that terminal 20 autonomously performed SCG deactivation) in the SN Modification Request message, and sends an SN Modification Request message including the value to SN 10B. may be sent to

SN 10B can receive notification of UE-Triggered SCG deactivation by SN Modification Request message, so it can determine not to reject it and, for example, execute processing such as releasing SCG resources for terminal 20 on SN 10B side. can.

(2) MN 10A, for example, in step 1 in FIG. 4, in the SN Modification Request message, a specific cause indicating UE-Triggered SCG deactivation (terminal 20 autonomously performed SCG deactivation) SN Modification Request message including this Cause is sent to SN 10B.

(3) MN 10A, for example, in step 1 in FIG. 4, includes a specific IE (information element) indicating that the message cannot be rejected in the SN Modification Request message, and sends the SN Modification Request message including the IE. Send to SN10B.

Also, MN 10A may include a specific value indicating that the message cannot be rejected in the SN Modification Request message, and transmit the SN Modification Request message including the value to SN 10B.

SN 10B determines not to reject the SN Modification Request message, and executes processing such as releasing SCG resources for terminal 20 on the SN 10B side, for example.

(4) MN 10A, for example, in step 1 in FIG. 4, includes a specific cause indicating that rejection is not possible in the SN Modification Request message, and transmits the SN Modification Request message including the cause to SN 10B. do.

It should be noted that the information described in (3) and (4) indicating that rejection is not possible may be included in the SN Modification Request message in addition to the information described in (1) and (2).

<Example 1-2>
When MN 10A receives the notification that the SCG has been deactivated from terminal 20, MN 10A notifies UE-Triggered SCG deactivation to SN 10B using a new message. Upon receiving the UE-Triggered SCG deactivation, SN 10B determines that this message cannot be rejected, and, for example, returns a response message (Acknowledge) confirming that the UE-Triggered SCG deactivation has been performed to MN 10A.

A round-trip (Class 1) procedure as described above may be used, or a one-way (Class 2) procedure in which the SN 10B that receives the UE-Triggered SCG deactivation does not return a response message may be used.

Note that SN 10B may change (release, etc.) the setting of SCG resources for terminal 20 on the SN 10B side in response to receiving a new message containing UE-Triggered SCG deactivation. Also, after the procedure of the embodiment 1-2, the MN initiated SN modification procedure shown in FIG. 4 is started, in which the setting change (release, etc.) of the SCG resource for the terminal 20 on the SN 10B side may be performed.

Also, the notification of the new message in embodiment 1-2 may be performed in existing procedures such as the MN initiated SN modification procedure. For example, the above new message may be sent from MN 10A to SN 10B immediately before or after step 1 (SN Modification Request) in FIG.

<Example 1-3>
Next, Example 1-3 will be described with reference to FIG. In S201, the terminal 20 autonomously performs SCG deactivation. In S202, the terminal 20 notifies the SN 10B that it autonomously performed the SCG deactivation.

In S203, SN 10B notifies MN 10A that terminal 20 autonomously performed SCG deactivation.

The message used in the notification of S203 may be, for example, a message for starting SCG deactivation from SN 10B, or a new message other than the message for starting SCG deactivation.

The message used in the notification of S203 includes a specific IE indicating UE-Triggered SCG deactivation, a specific value indicating UE-Triggered SCG deactivation, and Any of a specific Cause indicating UE-Triggered SCG deactivation, a specific IE indicating that rejection is not possible, or a specific value indicating that rejection is not possible may be included.

Also, a response message may be returned from MN 10A to SN 10B in response to S203.

<Effect of Example 1>
According to the first embodiment, the nodes (MN 10A, SN 10B) that have received the notification can decide not to reject the procedure. Therefore, the signaling that can be caused by rejecting the procedure can be reduced. In addition, it is possible to prevent state inconsistency between the terminal 20 and the NW, which may occur due to refusal of the procedure.

(Example 2)
Next, Example 2 for solving the second problem will be described. First, the second problem will be explained in more detail. It should be noted that the detailed description of the problem below is not a description of the problem of the conventional technology, but a consideration that is a prerequisite for the operation of the second embodiment, and is included in the technology of the second embodiment.

<Description of detailed task>
As a whole system or as a telecommunications carrier, any one of the following (a) to (f) as a criterion for determining whether or not to permit UE autonomous SCG Deactivation, or (a) to (f) A combination of any one of them is conceivable. Note that (a) to (f) are examples, and criteria other than (a) to (f) may be used.

(a) Allow only UEs with specific communication capabilities or specific functions. Specific communication capabilities or specific functions can be determined by UE Capabilities.

(b) Determine permission/non-permission based on the model of the UE. The UE model can be identified by Masked IMEISV.

(c) Determine permission/non-permission based on the setting information held by the base station. The setting information held by the base station is, for example, information indicating the following settings.

- allow/disallow UE autonomous SCG deactivation under certain MN/SN certain cells;
- Under a cell with a certain MN / SN, allow / not allow UE autonomous SCG deactivation only for a specific UE model

(d) Determine permission/non-permission based on the UE communication pattern. The communication pattern is, for example, the actual value of communication, Expected UE Behavior, and the like.

(e) Determine permission/non-permission based on the communication status of the UE. The communication status is, for example, L2 status, SgNB Activity Notification, or the like.

(f) Determine permission/non-permission based on subscriber information. For example, it will be determined based on corporate use cases, the presence or absence of a battery life improvement option contract, etc.

When MN 10A or SN 10B determines whether or not UE autonomous SCG deactivation is possible, for example, the above information is necessary. Therefore, considering whether or not each of the above information can be obtained by MN/SN in the current standard specifications, the following results are obtained. As follows. ○ indicates that it can be obtained, △ indicates that it can be obtained only in a specific case or only partly, and × indicates that it cannot be obtained.

(a) Capabilities
MN: △ (NR Capability is generally not referred to during EN-DC)
SN: △ (E-UTRA Capabilities are generally not referenced during EN-DC)
(b) Model MN: ○ (Masked IMEISV IE)
SN: ○ (Masked IMEISV IE)
(c) Configuration information held by the base station MN: Δ (separate parameter sets in terms of MN/SN)
SN: △ (separate parameter set in terms of MN/SN)
(d) Communication pattern MN: ○ (measured by itself or Expected UE Behavior IE)
SN: ○ (measured by itself, or Expected UE Behavior IE)
(e) Communication status MN: △ (The actual communication status can be grasped only by the bearer that hosts PDCP itself)
SN: △ (The actual communication status can only be grasped by the bearer that hosts the PDCP itself)
(f) Subscriber/contract information MN: ×
SN: x
Based on the above, if the MN alone or the SN alone determines whether UE autonomous SCG deactivation is possible, the following problems may occur.

Issue 1 (a, c, e): For criteria (UE capabilities, config, communication status) with different information obtained between nodes, one node cannot consider the information of the other node.

For example, regarding the communication status of e, when determining whether UE autonomous SCG deactivation is possible for MN terminated bearers, SCG information is unnecessary, but when targeting SN terminated bearers, SCG information is required. However, the MN cannot take that information into account as it does not have it.

Problem 2(f): Information that the RAN (base station) does not have cannot be considered.

Hereinafter, Example 2-1 will be explained from the viewpoint of Problem 1, and Example 2-2 will be explained from the viewpoint of Problem 2. Example 2-1 and Example 2-2 may be combined.

<Example 2-1>
In Example 2-1, UE autonomous SCG deactivation permission/non-permission “proposal” is notified between MN 10A and SN 10B. The node that receives the proposal compares the content of the proposal with its own information and determines whether it is actually permitted or not. "Proposal" is, for example, a proposal to permit or disallow UE autonomous SCG deactivation.

As an example, MN 10A permits UE autonomous SCG deactivation to terminal 20 when its own proposal is "permit" and the proposal received from SN 10B is also "permit". MN 10A disallows UE autonomous SCG deactivation for terminal 20 when at least one of its own proposal and the proposal received from SN 10B is "disallowed".

Also, as an example, SN 10B permits UE autonomous SCG deactivation to terminal 20 when its own proposal is "permitted" and the proposal received from MN 10A is also "permitted." SN 10B disallows UE autonomous SCG deactivation for terminal 20 when at least one of its own proposal and the proposal received from MN 10A is "disallowed".

UE autonomous SCG deactivation permission/non-permission between MN 10A and SN 10B instead of or in addition to notifying UE autonomous SCG deactivation permission/non-permission “suggestion” between MN 10A and SN 10B (eg, any one or more of (a) to (f) described above) may be notified.

As an example, MN 10A determines permission/non-permission based on its own information and information received from SN 10B, and notifies terminal 20 of the determination result. Further, SN 10B may determine permission/non-permission based on information it owns and information received from MN 10A, and notify terminal 20 of the result of the determination.

In the explanation of the procedure below, the case of using "suggestion" will be explained as an example. The same procedure is applicable if "suggestion" is replaced by "information" above. Note that the "proposal" and the above "information" may be collectively referred to as "information".

Examples of specific procedures are described below as Examples 2-1-1 to 2-1-4.

<Example 2-1-1>
In Example 2-1-1, in the SN Addition Procedure procedure, the MN 10A and the SN 10B perform proposal notification and the like.

An example of the SN Addition Procedure procedure is shown in FIG. FIG. 6 is "Figure 10.2.2-1: SN Addition procedure" in Non-Patent Document 2. Using the SN Addition Procedure procedure shown in FIG. 6 in Example 2-1-1 is an example. Procedures other than the SN Addition Procedure procedure shown in FIG. 6 may be used.

The operation procedure in Example 2-1-1 will be described with reference to FIG.

MN 10A judges whether UE autonomous SCG deactivation of terminal 20 is possible, for example, based on its own information, and uses the judgment result as a proposal for UE autonomous SCG deactivation. In S301, MN 10A notifies SN 10B of the proposal by SN Addition Request.

SN 10B, which has received the proposal from MN 10A, determines whether UE autonomous SCG deactivation is possible and, in S302, replies to MN 10A with SN Addition Request Acknowledge whether UE autonomous SCG deactivation is possible.

In S303, the MN 10A notifies the terminal 20 of the UE autonomous SCG deactivation enable/disable flag through RRC reconfiguration.

Fig. 8 shows another example. As shown in FIG. 8, in this example, SN 10B, which has received the UE autonomous SCG deactivation propriety proposal from MN 10A, notifies the terminal 20 of the UE autonomous SCG deactivation propriety flag in S402.

<Example 2-1-2>
In Example 2-1-2, the MN-initiated SN Modification procedure as shown in FIG. 4 is used to notify the UE autonomous SCG deactivation proposal, etc. In FIGS. 7 and 8, the procedure in Example 2-1-2 is obtained by replacing "Addition" with "Modification".

<Example 2-1-3>
Next, Example 2-1-3 will be described. In Example 2-1-3, in the SN-initiated SN Modification procedure, the MN 10A and SN 10B perform notification of a proposal and the like.

An example of the SN-initiated SN Modification procedure is shown in FIG. FIG. 9 is "Figure 10.3.1-2: SN Modification procedure-SN initiated with MN involvement" in Non-Patent Document 2. Using the SN-initiated SN Modification procedure shown in FIG. 9 in Example 2-1-3 is an example. Procedures other than the SN-initiated SN Modification procedure shown in FIG. 9 may be used.

The operation procedure in Example 2-1-3 will be described with reference to FIG. SN 10B determines whether UE autonomous SCG deactivation of terminal 20 is possible based on, for example, information it owns, and uses the result of the determination as a proposal for UE autonomous SCG deactivation. In S501, SN 10B notifies MN 10A of the proposal with SN Modification Required.

Upon receiving the proposal from SN 10B, MN 10A determines whether UE autonomous SCG deactivation is possible, and in S502, notifies terminal 20 of the UE autonomous SCG deactivation possible/impossible flag through RRC reconfiguration. Note that S511 shown in FIG. 10 (and S611 in FIG. 11) is used in a procedure example to be described later.

Another example is shown in FIG. SN 10B determines whether UE autonomous SCG deactivation of terminal 20 is possible based on, for example, information it owns, and uses the result of the determination as a proposal for UE autonomous SCG deactivation. In S601, SN 10B notifies MN 10A of the proposal with SN Modification Required. In S602, the SN 10B notifies the terminal 20 of the UE autonomous SCG deactivation enable/disable flag through RRC reconfiguration.

In the two procedures described with reference to FIGS. 10 and 11, MN 10A may not adopt the proposal from SN 10B. In that case, MN 10A may Refuse the SN Modification procedure. At this time, in S511 of FIG. 10 and S611 of FIG. 11, the MN 10A may notify the SN 10B of the cause that the UE autonomous SCG deactivation proposal is not accepted. In the example of FIG. 11, SN 10B notifies terminal 20 of the UE autonomous SCG deactivation flag by RRC reconfiguration only when its own proposal is not rejected by MN 10A (when Refuse is not received). good.

Next, another procedure example will be described with reference to FIGS. Here, S511 in FIG. 10 and S611 in FIG. 11 are used for purposes other than Refuse.

First, a description will be given with reference to FIG. In S501, SN 10B notifies MN 10A of its own proposal with SN Modification Required. The MN 10A determines whether or not the UE autonomous SCG deactivation is possible, and notifies the SN 10B of whether or not the UE autonomous SCG deactivation is possible in S511. Also, in S502, the MN 10A notifies the terminal 20 of a UE autonomous SCG deactivation enable/disable flag through RRC reconfiguration.

Next, another example will be described with reference to FIG. In S601, SN 10B notifies MN 10A of its own proposal with SN Modification Required. The MN 10A determines whether or not the UE autonomous SCG deactivation is possible, and in S611, notifies the SN 10B of whether or not the UE autonomous SCG deactivation is possible. In S602, the SN 10B notifies the terminal 20 of the UE autonomous SCG deactivation enable/disable flag through RRC reconfiguration.

As a detailed procedure example of the above example explained with reference to FIG. 11, the direction of the message and an example of information notified by the message are shown below. Hereinafter, numbers such as "1." correspond to the procedure numbers in FIG.

1. MN<-SN: SgNB Modification required
- UE autonomous SCG deactivation propriety proposal to notify MN - RRC Reconf (notify UE, set SCG (NR RRC))
2. MN->SN: SgNB Modification request
- UE autonomous SCG deactivation availability (proposal from MN's point of view)
3. MN<-SN: SgNB Modification request ack
-RRC Reconf (including setting of SCG (NR RRC) to be notified to UE, UE autonomous SCG deactivation to UE)
4. UE<-MN: RRC Reconf
- Set MCG - Set SCG (received from SN, including UE autonomous SCG deactivation flag to UE)
<Example 2-1-4>
Next, Example 2-1-4 will be described. In Example 2-1-4, MN->UE and SN->UE notify whether or not UE autonomous SCG deactivation is possible, and the UE determines whether or not UE autonomous SCG deactivation is possible based on this information.

Fig. 12 shows the procedure of Example 2-1-4. As shown in FIG. 12 , in S701 and S702, each of MN 10A and SN 10B transmits to terminal 20 a proposal as to whether or not UE autonomous SCG deactivation is possible.

In S703, the terminal 20 determines whether UE autonomous SCG deactivation is possible. For example, when both the proposal from MN 10A and the proposal from SN 10B are "possible", the terminal 20 determines that UE autonomous SCG deactivation is possible, and at least the proposal from MN 10A and the proposal from SN 10B If one is "impossible", it is determined that the UE autonomous SCG deactivation is impossible.

Also, for example, when both the proposal from MN 10A and the proposal from SN 10B are "impossible", terminal 20 determines that UE autonomous SCG deactivation is impossible, and is "possible", it may be determined that UE autonomous SCG deactivation is possible.

<Effect of Example 2-1>
According to Example 2-1, it is possible to determine whether or not UE autonomous SCG deactivation is possible by combining information that only one of MN 10A and SN 10B can have, so that an appropriate permission/non-permission flag can be notified to terminal 20. FIG.

<Example 2-2>
Next, an embodiment 2-2 that solves the above-mentioned problem 2 (information not possessed by the RAN (base station) cannot be considered) will be described. Here, an example in which Example 2-1 and Example 2-2 are combined is described, but Example 2-2 may be carried out independently of Example 2-1.

In the embodiment 2-2, from a core NW side device (eg AMF, MME) having subscriber information etc. (or able to access subscriber information etc.), a base station (MN or SN, or MN and SN both), the information that serves as the judgment criteria for judging whether UE autonomous SCG deactivation is possible is notified.

An example of the procedure in Example 2-2 will be described with reference to FIG. In S801, the core NW 100 (for example, AMF or MME) notifies the MN 10A of information that serves as a criterion for determination. In S802, the core NW 100 notifies the SN 10B of information that serves as a criterion for determination. Note that only one of S801 and S802 may be performed.

Next, the negotiation described in Example 2-1 is executed between MN10A and SN10B. Note that if the MN 10A or SN 10B can independently determine whether or not UE autonomous SCG deactivation is possible based on the determination criteria information from the core NW, this negotiation may not be performed.

In S803, the MN 10A notifies the terminal 20 of the UE autonomous SCG deactivation flag. Alternatively, in S804, SN 10B notifies terminal 20 of a UE autonomous SCG deactivation flag.

Any procedure/message may be used to transmit the criterion information from the core NW 100 to the MN 10A/SN 10B, but for example, the following procedure/message may be used.

・ UE Context Management procedure (Initial Context Setup Request, UE Context Modification Request)
・Mobility-related procedures (HO Request, Path Switch Request Ack)
・DL NAS Transport
- New message Further, the following (1) and (2) show examples of IE value patterns that serve as criteria information to be included in the message notified from the core NW 100 to the MN 10A/SN 10B.

(1) the following information about UE autonomous SCG deactivation:
- permission (allowed/not)
- allowed (allowed/(absent))
- not-allowed/(absent)
- Policy (required/recommended/neutral (or absent)/discouraged/not-allowed)
(2) NW-triggered SCG deactivation, or the same information as (1) about the entire SCG deactivation (regardless of initiating node) <Effect of Example 2-2>
According to the embodiment 2-2, it is possible to notify the RAN (base station) of information that can only be held in the core NW, such as contract information. can.

(Device configuration)
Next, functional configuration examples of the base station 10, the terminal 20, and the device 30 on the core NW side that execute the processes and operations described above will be described. The base station 10, the terminal 20, and the device 30 on the core NW side include functions for executing the above-described embodiments. However, each of the base station 10, the terminal 20, and the device 30 on the core NW side may be provided with only the function proposed by one of the embodiments.

<Base station 10>
FIG. 14 is a diagram showing an example of the functional configuration of the base station 10. As shown in FIG. As shown in FIG. 14, the base station 10 has a transmitting section 110, a receiving section 120, a setting section 130, and a control section 140. The functional configuration shown in FIG. 9 is merely an example. As long as the operation according to the embodiment of the present invention can be executed, the functional division and the names of the functional units may be arbitrary. The transmitting unit 110 and the receiving unit 120 may be called a communication unit. A base station 10 can be either an MN or an SN.

The transmission unit 110 includes a function of generating a signal to be transmitted to the terminal 20 side and wirelessly transmitting the signal. The receiving unit 120 includes a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, higher layer information from the received signals. Also, the transmitting unit 110 has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL/UL control signals, DL data, etc. to the terminal 20 . The transmitting section 110 also has a function of transmitting information to other base stations, and the receiving section 120 also has a function of receiving information from other base stations.

The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in the storage device, and reads them from the storage device as necessary. The control unit 140 performs overall control of the base station 10 including control related to signal transmission/reception, for example. It should be noted that the functional unit related to signal transmission in control unit 140 may be included in transmitting unit 110 , and the functional unit related to signal reception in control unit 140 may be included in receiving unit 120 . Also, the transmitting unit 110 and the receiving unit 120 may be called a transmitter and a receiver, respectively.

<Terminal 20>
FIG. 15 is a diagram showing an example of the functional configuration of the terminal 20. As shown in FIG. As shown in FIG. 15, the terminal 20 has a transmitting section 210, a receiving section 220, a setting section 230, and a control section 240. The functional configuration shown in FIG. 15 is merely an example. As long as the operation according to the embodiment of the present invention can be executed, the functional division and the names of the functional units may be arbitrary. The transmitting unit 210 and the receiving unit 220 may be called a communication unit.

The transmission unit 210 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal. The receiving unit 220 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal. Also, the transmitting unit 210 transmits HARQ-ACK, and the receiving unit 220 receives the setting information and the like described in the embodiment.

The setting unit 230 stores various types of setting information received from the base station 10 by the receiving unit 220 in the storage device, and reads them from the storage device as necessary. The setting unit 230 also stores preset setting information. The control unit 240 performs overall control of the terminal 20 including control related to signal transmission/reception. Also, the control unit 240 includes a function to autonomously perform SCG deactivation. It should be noted that the functional unit related to signal transmission in control unit 240 may be included in transmitting unit 210 , and the functional unit related to signal reception in control unit 240 may be included in receiving unit 220 . Also, the transmitting section 210 and the receiving section 220 may be called a transmitter and a receiver, respectively.

<Device 30 on Core NW>
FIG. 16 is a diagram showing an example of the functional configuration of the device 30 on the core NW side. As shown in FIG. 16, the device 30 on the core NW side has a transmitting section 310, a receiving section 320, a setting section 330, and a control section 340. FIG. The functional configuration shown in FIG. 15 is merely an example. As long as the operation according to the embodiment of the present invention can be executed, the functional division and the names of the functional units may be arbitrary. The transmitting unit 310 and the receiving unit 320 may be called a communication unit.

The transmitting unit 310, for example, transmits to the base station 10 the criteria information for determining whether UE autonomous SCG deactivation is possible. For example, the receiving unit 320 acquires criteria information for determining whether UE autonomous SCG deactivation is possible from other devices as necessary.

The setting unit 330 stores various types of setting information in a storage device, and reads them from the storage device as needed. In addition, the setting unit 330 may store determination criteria information for whether or not UE autonomous SCG deactivation is possible. The control unit 340 controls the entire device 30 . Also, the transmitting unit 310 and the receiving unit 320 may be called a transmitter and a receiver, respectively.

(Hardware configuration)
The block diagrams (FIGS. 14 to 16) used to describe the above embodiments show blocks in units of functions. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of implementing each functional block is not particularly limited. That is, each functional block may be implemented using one device that is physically or logically coupled, or directly or indirectly using two or more devices that are physically or logically separated (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices. A functional block may be implemented by combining software in the one device or the plurality of devices.

Functions include judging, determining, determining, calculating, calculating, processing, deriving, investigating, searching, checking, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, assuming, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. can't For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. In either case, as described above, the implementation method is not particularly limited.

For example, the base station 10, the terminal 20, etc. according to the embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 17 is a diagram illustrating an example of hardware configurations of the base station 10, the terminal 20, and the device 30 on the core NW side according to an embodiment of the present disclosure. Physically, the base station 10, the terminal 20, and the device 30 on the core NW side described above include a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. may be configured as a computer device including

In the following explanation, the term "apparatus" can be read as a circuit, device, unit, or the like. The hardware configuration of the base station 10 and terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.

Each function of the base station 10 and the terminal 20 is performed by the processor 1001 performing calculations and controlling communication by the communication device 1004 by loading predetermined software (programs) onto hardware such as the processor 1001 and the storage device 1002. or by controlling at least one of data reading and writing in the storage device 1002 and the auxiliary storage device 1003 .

The processor 1001, for example, operates an operating system and controls the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like. For example, the control unit 140 , the control unit 240 and the like described above may be implemented by the processor 1001 .

In addition, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes according to them. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, control unit 140 of base station 10 shown in FIG. 14 may be implemented by a control program stored in storage device 1002 and operated by processor 1001 . Also, for example, the control unit 240 of the terminal 20 shown in FIG. 15 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001 . Although it has been explained that the above-described various processes are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. FIG. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.

The storage device 1002 is a computer-readable recording medium, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be configured. The storage device 1002 may also be called a register, cache, main memory (main storage device), or the like. The storage device 1002 can store executable programs (program code), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

The auxiliary storage device 1003 is a computer-readable recording medium, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu -ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, and/or the like. The storage medium described above may be, for example, a database, server, or other suitable medium including at least one of storage device 1002 and secondary storage device 1003 .

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of, for example, frequency division duplex (FDD) and time division duplex (TDD). may consist of For example, a transmitting/receiving antenna, an amplifier section, a transmitting/receiving section, a transmission line interface, etc. may be implemented by the communication device 1004 . The transceiver may be physically or logically separate implementations for the transmitter and receiver.

The input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

Each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between devices.

In addition, the base station 10, the terminal 20, and the device 30 on the core NW side include a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), etc., and part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

(Summary of embodiment)
Disclosed herein are devices, systems, and methods described in the following sections.

Regarding Example 1, it is as follows.
(Section 1)
A receiving unit that receives first information indicating that the terminal has autonomously deactivated a specific cell group in dual connectivity from the terminal;
A base station that transmits second information indicating that the terminal has autonomously deactivated the specific cell group to another base station that configures the dual connectivity.
(Section 2)
2. The base station of claim 1, wherein the base station is a master node and the other base stations are secondary nodes.
(Section 3)
2. The base station of claim 1, wherein the base station is a secondary node and the other base station is a master node.
(Section 4)
4. The base station according to any one of items 1 to 3, wherein the second information includes information indicating that the other base station cannot reject the second information.
(Section 5)
A first base station comprising a transmission unit that transmits information indicating that the terminal has autonomously deactivated a specific cell group in dual connectivity to a second base station that configures the dual connectivity;
A system comprising: the second base station comprising a receiving unit that receives the information; and a control unit that determines not to reject the information.
(Section 6)
A step of receiving from the terminal first information indicating that the terminal has autonomously deactivated a specific cell group in dual connectivity;
A step of transmitting second information indicating that the terminal has autonomously deactivated the specific cell group to another base station that configures the dual connectivity, information executed by the base station. Notification method.

Any of items 1 to 6 provides a technology that enables appropriate signaling between nodes in response to autonomous operation of terminals in a wireless communication system that performs dual connectivity. . Also, according to the second and third terms, information can be appropriately notified between the MN and the SN. Clause 4 makes it possible to know explicitly that it cannot be refused.

Regarding Example 2, it is as follows.
(Section 1)
Transmission that transmits information used for determining whether to allow the terminal to autonomously deactivate a specific cell group in dual connectivity to other base stations that configure the dual connectivity A base station comprising:
(Section 2)
If the information is not rejected by the other base station after the information is transmitted to the other base station, the transmitting unit allows autonomous deactivation of the specific cell group. 2. The base station according to claim 1, which notifies the terminal whether or not to perform.
(Section 3)
Information used for determining whether to allow the terminal to autonomously deactivate a specific cell group in dual connectivity is received from another base station that configures the dual connectivity. a receiver;
A base station that uses information received from the other base station to determine whether or not to allow the terminal to autonomously deactivate the specific cell group.
(Section 4)
a receiver that receives information from a core network that is used to determine whether to allow the terminal to autonomously deactivate a particular cell group;
A base station that uses information received from the core network to determine whether to allow the terminal to autonomously deactivate the specific cell group.
(Section 5)
Transmission of information used to determine whether to allow the terminal to autonomously deactivate a specific cell group in dual connectivity to the second base station that configures the dual connectivity a first base station comprising:
A second base station comprising a control unit that uses the information received from the first base station to determine whether to permit the terminal to autonomously deactivate the specific cell group. A system comprising and .
(Section 6)
6. The system according to claim 5, wherein the second base station transmits the determination result to the first base station or the terminal.

Any of the first to sixth paragraphs, in a node of a wireless communication system that performs dual connectivity, a technology that enables acquisition of information necessary to determine whether the terminal can operate autonomously is provided. be. Also, according to the second term, the flag can be sent to the terminal after confirming that it will not be rejected.

(Supplement to the embodiment)
Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art can understand various modifications, modifications, alternatives, replacements, and the like. be. Although specific numerical examples have been used to facilitate understanding of the invention, these numerical values are merely examples and any appropriate values may be used unless otherwise specified. The division of items in the above description is not essential to the present invention, and the items described in two or more items may be used in combination as necessary, and the items described in one item may be used in another item. may apply (unless inconsistent) to the matters set forth in Boundaries of functional or processing units in functional block diagrams do not necessarily correspond to boundaries of physical components. The operations of a plurality of functional units may be physically performed by one component, or the operations of one functional unit may be physically performed by a plurality of components. As for the processing procedures described in the embodiments, the processing order may be changed as long as there is no contradiction. For convenience of explanation of the processing, the base station 10, the terminal 20, and the device 30 on the core NW side are explained using functional block diagrams, but such devices are realized by hardware, software, or a combination thereof. may be The software operated by the processor of the base station 10 according to the embodiment of the present invention and the software operated by the processor of the terminal 20 according to the embodiment of the present invention are stored in random access memory (RAM), flash memory, read-only memory, respectively. (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other appropriate storage medium.

Also, notification of information is not limited to the aspects/embodiments described in the present disclosure, and may be performed using other methods. For example, notification of information includes physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.In addition, RRC signaling may also be called an RRC message, for example, RRC It may be a connection setup (RRC Connection Setup) message, an RRC connection reconfiguration message, or the like.

Each aspect/embodiment described in the present disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system) system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark) )), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other suitable systems and extended It may be applied to at least one of the next generation systems. Also, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G, etc.).

The order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this specification may be changed as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.

A specific operation performed by the base station 10 in this specification may be performed by its upper node in some cases. In a network consisting of one or more network nodes with base station 10, various operations performed for communication with terminal 20 may be performed by base station 10 and other network nodes other than base station 10 ( (eg, but not limited to MME or S-GW). Although the case where there is one network node other than the base station 10 is illustrated above, the other network node may be a combination of a plurality of other network nodes (for example, MME and S-GW). .

Information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may be input and output via multiple network nodes.

Input/output information may be stored in a specific location (for example, memory) or managed using a management table. Input/output information and the like can be overwritten, updated, or appended. The output information and the like may be deleted. The entered information and the like may be transmitted to another device.

The determination in the present disclosure may be performed by a value represented by 1 bit (0 or 1), may be performed by a boolean value (Boolean: true or false), or may be performed by comparing numerical values (e.g. , comparison with a predetermined value).

Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.

In addition, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, the software uses at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.) to website, Wired and/or wireless technologies are included within the definition of transmission medium when sent from a server or other remote source.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of

The terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, the channel and/or symbols may be signaling. A signal may also be a message. A component carrier (CC) may also be called a carrier frequency, a cell, a frequency carrier, or the like.

The terms "system" and "network" used in this disclosure are used interchangeably.

In addition, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. may be represented. For example, radio resources may be indexed.

The names used for the parameters described above are not restrictive names in any respect. Further, the formulas, etc., using these parameters may differ from those expressly disclosed in this disclosure. Since the various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are in no way restrictive names. is not.

In the present disclosure, "base station (BS)", "radio base station", "base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB ( gNB)", "access point", "transmission point", "reception point", "transmission/reception point", "cell", "sector", " Terms such as "cell group", "carrier", "component carrier" may be used interchangeably. A base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.

A base station can accommodate one or more (eg, three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being associated with a base station subsystem (e.g., an indoor small base station (RRH: The term "cell" or "sector" refers to part or all of the coverage area of at least one of the base stations and base station subsystems serving communication services in this coverage. point to

In the present disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably. .

A mobile station is defined by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be called a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

At least one of the base station and mobile station may be called a transmitting device, a receiving device, a communication device, or the like. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and mobile station may be an IoT (Internet of Things) device such as a sensor.

Also, the base station in the present disclosure may be read as a user terminal. For example, communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the terminal 20 may have the functions of the base station 10 described above. Also, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be read as side channels.

Similarly, user terminals in the present disclosure may be read as base stations. In this case, the base station may have the functions that the above-described user terminal has.

The terms "determining" and "determining" used in this disclosure may encompass a wide variety of actions. "Judgement" and "determination" are, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (eg, lookup in a table, database, or other data structure), ascertaining as "judged" or "determined", and the like. Also, "judgment" and "determination" are used for receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access (accessing) (for example, accessing data in memory) may include deeming that a "judgment" or "decision" has been made. In addition, "judgment" and "decision" are considered to be "judgment" and "decision" by resolving, selecting, choosing, establishing, comparing, etc. can contain. In other words, "judgment" and "decision" may include considering that some action is "judgment" and "decision". Also, "judgment (decision)" may be read as "assuming", "expecting", "considering", or the like.

The terms "connected", "coupled", or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements being "connected" or "coupled." Couplings or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access". As used in this disclosure, two elements are defined using at least one of one or more wires, cables, and printed electrical connections and, as some non-limiting and non-exhaustive examples, in the radio frequency domain. , electromagnetic energy having wavelengths in the microwave and optical (both visible and invisible) regions, and the like.

The reference signal can also be abbreviated as RS (Reference Signal), and may also be called Pilot depending on the applicable standard.

The term "based on" as used in this disclosure does not mean "based only on" unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

Any reference to elements using the "first," "second," etc. designations used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, reference to a first and second element does not imply that only two elements can be employed or that the first element must precede the second element in any way.

"Means" in the configuration of each device described above may be replaced with "unit", "circuit", "device", or the like.

Where "include," "including," and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising." is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive OR.

A radio frame may consist of one or more frames in the time domain. Each frame or frames in the time domain may be referred to as a subframe. A subframe may also consist of one or more slots in the time domain. A subframe may be of a fixed length of time (eg, 1 ms) independent of numerology.

A numerology may be a communication parameter that applies to the transmission and/or reception of a signal or channel. Numerology, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, transceiver It may indicate at least one of certain filtering operations performed in the frequency domain, certain windowing operations performed by the transceiver in the time domain, and/or the like.

A slot may consist of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbol, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbol, etc.) in the time domain. A slot may be a unit of time based on numerology.

A slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.

Radio frames, subframes, slots, minislots and symbols all represent time units when transmitting signals. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations.

For example, one subframe may be called a Transmission Time Interval (TTI), a plurality of consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. may That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms may be Note that the unit representing the TTI may be called a slot, mini-slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum scheduling time unit in wireless communication. For example, in the LTE system, the base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each terminal 20) to each terminal 20 on a TTI basis. Note that the definition of TTI is not limited to this.

A TTI may be a transmission time unit such as a channel-encoded data packet (transport block), code block, or codeword, or may be a processing unit such as scheduling and link adaptation. Note that when a TTI is given, the time interval (for example, the number of symbols) in which transport blocks, code blocks, codewords, etc. are actually mapped may be shorter than the TTI.

When one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, or the like. A TTI that is shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.

Note that the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms, and the short TTI (e.g., shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms A TTI having the above TTI length may be read instead.

A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the numerology, and may be 12, for example. The number of subcarriers included in an RB may be determined based on numerology.

Also, the time domain of an RB may include one or more symbols and may be 1 slot, 1 minislot, 1 subframe, or 1 TTI long. One TTI, one subframe, etc. may each consist of one or more resource blocks.

One or more RBs are physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. may be called.

Also, a resource block may be composed of one or more resource elements (RE: Resource Element). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

A bandwidth part (BWP) (which may also be called a bandwidth part) may represent a subset of contiguous common resource blocks (RBs) for a certain numerology on a certain carrier. Here, the common RB may be identified by an RB index based on the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured for terminal 20 within one carrier.

At least one of the configured BWPs may be active, and the terminal 20 may not expect to transmit or receive a given signal/channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

The structures such as radio frames, subframes, slots, minislots and symbols described above are only examples. For example, the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. can be varied.

In this disclosure, if articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are plural.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean that "A and B are different from C". Terms such as "separate," "coupled," etc. may also be interpreted in the same manner as "different."

Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching along with execution. In addition, the notification of predetermined information (for example, notification of “being X”) is not limited to being performed explicitly, but may be performed implicitly (for example, not notifying the predetermined information). good too.

Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be practiced with modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Accordingly, the description of the present disclosure is for illustrative purposes and is not meant to be limiting in any way.

10 base station 110 transmitting unit 120 receiving unit 130 setting unit 140 control unit 20 terminal 210 transmitting unit 220 receiving unit 230 setting unit 240 control unit 310 transmitting unit 320 receiving unit 330 setting unit 340 control unit 30 core network, device 1001 processor 1002 storage Device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

Transmission that transmits information used for determining whether to allow the terminal to autonomously deactivate a specific cell group in dual connectivity to other base stations that configure the dual connectivity A base station comprising:
If the information is not rejected by the other base station after the information is transmitted to the other base station, the transmitting unit allows autonomous deactivation of the specific cell group. The base station according to claim 1, which notifies the terminal whether or not to perform.
Receiving information used to determine whether to allow the terminal to autonomously deactivate a specific cell group in dual connectivity from another base station that configures the dual connectivity Department and
A base station that uses information received from the other base station to determine whether or not to allow the terminal to autonomously deactivate the specific cell group.
a receiver that receives information from the core network that is used to determine whether to allow the terminal to autonomously deactivate a particular cell group;
A base station that uses information received from the core network to determine whether to allow the terminal to autonomously deactivate the specific cell group.
Transmission of information used to determine whether to allow the terminal to autonomously deactivate a specific cell group in dual connectivity to the second base station that configures the dual connectivity a first base station comprising:
A second base station comprising a control unit that uses the information received from the first base station to determine whether to permit the terminal to autonomously deactivate the specific cell group. A system comprising and .
The system according to claim 5, wherein the second base station transmits the determination result to the first base station or the terminal.