Beam-Based Measurement Configuration
US-2019132066-A1 · May 2, 2019 · US
US10979941B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10979941-B2 |
| Application number | US-201916712380-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 12, 2019 |
| Priority date | Jun 16, 2017 |
| Publication date | Apr 13, 2021 |
| Grant date | Apr 13, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. The disclosure provides a method and device for switching a serving cell.
Opening claim text (preview).
What is claimed is: 1. A method performed by a network entity corresponding to a central unit (CU) of a secondary node (SN) in a wireless communication system, the method comprising: transmitting, to a network entity corresponding to a distributed unit (DU) of the SN via an F1 interface, a request message for requesting a context setup of a terminal that includes a first list of at least one candidate primary secondary cell (PSCell) and a second list of at least one secondary cell (SCell) to be setup; receiving, from the network entity corresponding to the DU via the F1 interface, a response message for confirming the context setup of the terminal that includes a third list of at least one SCell failed to setup and a cause for each SCell of the at least one SCell failed to setup in the third list; and transmitting, to a network entity corresponding to a master node (MN) associated with the SN, a message for requesting a modification of the SN based on the response message. 2. The method of claim 1 , wherein the message for requesting the modification of the SN includes secondary cell group (SCG) configuration information, a list of at least one bearer to be modified, and information on a tunnel endpoint at the SCG for delivering data of the at least one bearers, and wherein the method further comprises receiving, from the network entity corresponding to the MN, a message for confirming the modification of the SN as a response to the message for requesting the modification of the SN. 3. The method of claim 2 , further comprising: transmitting, to the network entity corresponding to the DU via the F1 interface, a message for requesting a context modification of the terminal that includes a fourth list of at least one SCell to be setup; and receiving, from the network entity corresponding to the DU via the F1 interface, a message for confirming the context modification of the terminal that includes a fifth list of at least one SCell failed to setup. 4. The method of claim 3 , wherein the message for confirming the context modification of the terminal further includes a cause associated with the fifth list of at least one SCell failed to setup included in the message for confirming the context modification of the terminal, and wherein the cause associated with the fifth list indicates an overload of an SCell failed to setup by the network entity corresponding to the DU. 5. The method of claim 2 , wherein the tunnel endpoint is used for delivering downlink data of the at least one bearer to the terminal. 6. The method of claim 1 , wherein the cause indicates an overload of an SCell failed to setup by the network entity corresponding to the DU. 7. A network entity corresponding to a central unit (CU) of a secondary node (SN) in a wireless communication system, the network entity corresponding to the CU comprising: a transceiver configured to transmit and receive a signal; and at least one processor configured to: transmit, to a network entity corresponding to a distributed unit (DU) of the SN via the transceiver via an F1 interface, a request message for requesting a context setup of a terminal that includes a first list of at least one candidate primary secondary cell (PSCell) and a second list of at least one secondary cell (SCell) to be setup, receive, from the network entity corresponding to the DU via the transceiver via the F1 interface, a response message for confirming the context setup of the terminal that includes a third list of at least one SCell failed to setup and a cause for each SCell of the at least one SCell failed to setup in the third list, and transmit, to a network entity corresponding to a master node (MN) associated with the SN, a message for requesting a modification of the SN based on the response message. 8. The network entity corresponding to the CU of claim 7 , wherein the message for requesting the modification of the SN includes secondary cell group (SCG) configuration information, a list of at least one bearer to be modified, and information on a tunnel endpoint at the SCG for delivering data of the at least one bearer, and wherein the at least one processor is further configured to receive, from the network entity corresponding to the MN via the transceiver, a message for confirming the modification of the SN as a response to the message for requesting the modification of the SN. 9. The network entity corresponding to the CU of claim 8 , wherein the at least one processor is further configured to: transmit, to the network entity corresponding to the DU via the transceiver via the F1 interface, a message for requesting a context modification of the terminal that includes a fourth list of at least one SCell to be setup, and receive, from the network entity corresponding to the DU via the transceiver via the F1 interface, a message for confirming the context modification of the terminal that includes a fifth list of at least one SCell failed to setup. 10. The network entity corresponding to the CU of claim 9 , wherein the message for confirming the context modification of the terminal further includes a cause associated with the fifth list of at least one SCell failed to setup included in the message for confirming the context modification of the terminal, and wherein the cause associated with the fifth list indicates an overload of an SCell failed to setup by the network entity corresponding to the DU. 11. The network entity corresponding to the CU of claim 8 , wherein the tunnel endpoint is used for delivering downlink data of the at least one bearer to the terminal. 12. The network entity corresponding to the CU of claim 7 , wherein the cause indicates an overload of an SCell failed to setup by the network entity corresponding to the DU. 13. A network entity corresponding to a distributed unit (DU) of a secondary node (SN) in a wireless communication system, the network entity corresponding to the DU comprising: a transceiver configured to transmit and receive a signal; and at least one processor configured to: receive, from a network entity corresponding to a central unit (CU) of the SN via the transceiver via an F1 interface, a request message for requesting a context setup of a terminal that includes a first list of at least one candidate primary secondary cell (PSCell) and a second list of at least one secondary cell (SCell) to be setup, and transmit, to the network entity corresponding to the CU via the transceiver via the F1 interface, a response message for confirming the context setup of the terminal that includes a third list of at least one SCell failed to setup and a cause for each SCell of the at least one SCell failed to setup in the third list, wherein a message for requesting a modification of the SN is transmitted to a network entity corresponding to a master node (MN) associated with the SN from the network entity corresponding to the CU based on the response message. 14. The network entity corresponding to the DU of claim 13 , wherein the message for requesting the modification of the SN includes secondary cell group (SCG) configuration information, a list of at least one bearer to be modified, and information on a tunnel endpoint at the SCG for delivering data of the at least one bearer, and wherein a message for confirming the modification of the SN is transmitted from the network entity corresponding to the MN to the network entity corresponding to the CU as a response to the message for requesting the modification of the SN. 15. The network entity corresponding to the DU of claim 14 , wherein the at least one processor is further
Random access procedures, e.g. with 4-step access · CPC title
Reselecting an access point · CPC title
in case of dual connectivity, e.g. decoupled uplink/downlink · CPC title
Connection release · CPC title
Manipulation of established connections · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.