WO2024082458A1

WO2024082458A1 - Network device and user equipment for network energy saving under dual connectivity mode

Info

Publication number: WO2024082458A1
Application number: PCT/CN2023/070916
Authority: WO
Inventors: Congchi ZHANG; Ran YUE; Mingzeng Dai; Lianhai WU
Original assignee: Lenovo (Beijing) Limited
Priority date: 2023-01-06
Filing date: 2023-01-06
Publication date: 2024-04-25

Abstract

The present application relates to a network device and a UE for NES under DC mode. The network device receives a first information from another network device, or transmit a second information to the another network device. The first information includes: an indication for indicating the network device to serve the UE based on a NES cell condition; a first NES cell status of a cell group of the another network device; or a first primary path information corresponding to the UE. The second information includes: a second NES cell status of a cell group of the network device; or a second primary path information corresponding to the UE.

Description

NETWORK DEVICE AND USER EQUIPMENT FOR NETWORK ENERGY SAVING UNDER DUAL CONNECTIVITY MODE

TECHNICAL FIELD

Embodiments of the present application generally relate to wireless communication technology, especially to a network device and a user equipment for network energy saving under dual connectivity mode.

BACKGROUND

In conventional network, the network energy saving (NES) techniques have been introduced. In general, for the sake of energy saving, when the traffic load over a cell is low, the network may operate the cell in an NES mode. For example, in the NES mode, the cell is operated with less common/user equipment specific reference signaling or is operated without system information block (SIB) and synchronization signal block (SSB) . However, specific details of applying the NES techniques to the network under dual connectivity (DC) mode have not been discussed yet and there are still some issues that need to be solved.

SUMMARY

Some embodiments of the present application provide a network device serving a user equipment (UE) under a dual connectivity (DC) mode. The network device includes: a processor and a transceiver coupled to the processor. The processor is configured to: receive, via the transceiver, a first information from another network device; or transmit, via the transceiver, a second information to the another network device. The first information includes: an indication for indicating the network device to serve the UE based on a network energy saving (NES) cell condition; a first NES cell status of a cell group of the another network device; or a first primary path information corresponding to the UE. The second information includes: a second NES cell status of a cell group of the network device; or a second primary path information corresponding to the UE.

Some embodiments of the present application provide a network device serving a UE under a DC mode. The network device includes: a processor and a transceiver coupled to the processor. The processor is configured to: transmit, via the transceiver, a first information to another network device; or receive, via the transceiver, a second information from the another network device. The first information includes: an indication for indicating the network device to serve the UE based on a NES cell condition; a first NES cell status of a cell group of the another network device; or a first primary path information corresponding to the UE. The second information includes: a second NES cell status of a cell group of the network device; or a second primary path information corresponding to the UE.

Some embodiments of the present application provide a UE served by a network under a DC mode. The UE includes: a processor and a transceiver coupled to the processor. The processor is configured to: determine one of two paths of a split bearer is served by only NES cell; and transmit, via the transceiver, uplink data or a signaling to the network according to the result of determining the one of two paths of the split bearer is served by only NES cell.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which advantages and features of the application can be obtained, a description of the application is rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. These drawings depict only example embodiments of the application and are not therefore to be considered limiting of its scope.

FIG. 1 illustrates a schematic diagram of a wireless communication system in accordance with some embodiments of the present application.

FIG. 2 is a schematic diagrams of message transmission in accordance with some embodiments of the present application.

FIG. 3 is a schematic diagram of message transmission in accordance with some embodiments of the present application.

FIG. 4 is a schematic diagram of message transmission in accordance with some embodiments of the present application.

FIG. 5 is a schematic diagram of message transmission in accordance with some embodiments of the present application.

FIG. 6 illustrates a block diagram of an apparatus in accordance with some embodiments of the present application.

DETAILED DESCRIPTION

The detailed description of the appended drawings is intended as a description of preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It should be understood that the same or equivalent functions may be accomplished by different embodiments that are intended to be encompassed within the spirit and scope of the present application.

Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. Embodiments of the present application may be provided in a network architecture that adopts various service scenarios, for example but is not limited to, 3GPP 3G, long-term evolution (LTE) , LTE-Advanced (LTE-A) , 3GPP 4G, 3GPP 5G NR (new radio) , etc. It is contemplated that along with the 3GPP and related communication technology development, the terminologies recited in the present application may change, which should not affect the principle of the present application.

Referring to FIG. 1, a wireless communication system 100 may include a user equipment (UE) 101,

network devices

102A, 102B and a core network (CN) 103. Although a specific number of the UE 101, the

network devices

102A, 102B and the CN 103 are depicted in FIG. 1, it is contemplated that any number of the UEs 101, the

network devices

102A, 102B and the CNs 103 may be included in the wireless communication system 100.

The CN 103 may include a core Access and Mobility management Function (AMF) entity. The BS 102, which may communicate with the CN 103, may operate or work under the control of the AMF entity. The CN 103 may further include a User Plane Function (UPF) entity, which communicatively coupled with the AMF entity.

The

network devices

102A, 102B may be distributed over a geographic region. In certain embodiments of the present application, any of the

network devices

102A, 102B may also be referred to as an access point, an access terminal, a base, a base unit, a macro cell, a Node-B, an evolved Node B (eNB) , a gNB, a Home Node-B, a relay node, a master node (MN) of dual connectivity (DC) , a secondary node (SN) of DC, or described using other terminology used in the art. The

network devices

102A, 102B are generally part of a radio access network that may include one or more controllers communicably coupled to one or more corresponding network device (s) . In some embodiments of the present application, the

network devices

102A, 102B may communicate with each other via some interfaces such as Xn/X2 interface between two BSs.

The UE 101 may include, for example, but is not limited to, computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , Internet of Thing (IoT) devices, or the like.

According to some embodiments of the present application, the UE 101 may include, for example, but is not limited to, a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, a wireless sensor, a monitoring device, or any other device that is capable of sending and receiving communication signals on a wireless network.

In some embodiments of the present application, the UE 101 may include, for example, but is not limited to, wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the UE 101 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art. The UE 101 may communicate directly with the

network devices

102A, 102B via uplink (UL) communication signals.

The wireless communication system 100 may be compatible with any type of network that is capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a Time Division Multiple Access (TDMA) -based network, a Code Division Multiple Access (CDMA) -based network, an Orthogonal Frequency Division Multiple Access (OFDMA) -based network, a Long Term Evolution (LTE) network, a 3GPP-based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.

In some embodiments of the present application, the wireless communication system 100 is compatible with the 5G New Radio (NR) of the 3GPP protocol or the 5G NR-light (or reduced capability NR UEs) of the 3GPP protocol, wherein the

network devices

102A, 102B transmit data using an OFDM modulation scheme on the downlink (DL) and the UE 101 transmits data on the UL using a single-carrier frequency division multiple access (SC-FDMA) or OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocols, for example, WiMAX, among other protocols.

In some embodiments of the present application, the UE 101 and the

network devices

102A, 102B may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Further, in some embodiments of the present application, the UE 101 and the

network devices

102A, 102B may communicate over licensed spectrums, whereas in other embodiments, the UE 101 and the

network devices

102A, 102B may communicate over unlicensed spectrums. The present application is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In yet some embodiments of present application, the

network devices

102A, 102B may communicate with the UE 101 using the 3GPP 5G protocols.

In some embodiments of the present application, a network energy saving (NES) cell of the

network devices

102A or 102B may be the cell operated in power saving condition (e.g., operated with less common/UE specific reference signaling or being operated without system information block (SIB) and synchronization signal block (SSB) ) . A non-NES cell of the

network devices

102A or 102B may be the cell operated without power saving condition.

In some embodiments of the present application, a master cell group (MCG) may be a group of serving cells associated with the MN. The MCG includes the primary cell (PCell) and optionally one or more secondary cells (SCells) . The secondary cell group (SCG) may be a group of serving cells associated with the SN. The SCG includes the primary secondary cell (PSCell) and optionally one or more SCells. An MCG/SCG bearer be a radio bearer terminating at MN/SN. A split bearer may be a radio bearer with radio link control (RLC) bearers both in MCG and SCG. An MN/SN terminated MCG bearer may be an MCG bearer terminated at the MN/SN An MN/SN terminated SCG bearer may be an SCG bearer terminated at the MN/SN. An MN/SN terminated split bearer may be a split bearer terminated at the MN/SN.

FIG. 2 is a schematic diagram of message transmission in accordance with some embodiments of the present application. In particular, the network device 102A is an MN serving the UE 101 under the DC mode, and the network device 102B is an SN serving the UE 101 under the DC mode. The network device 102A transmits a message M11 including an information to the network device 102B. The information may be an indication for indicating the network device 102B to server the UE 101 based on an NES cell condition. After receiving the message M11, the network device 102B transmits a message M12 to the network device 102A for acknowledging receiving the message M11.

In some embodiments, the message M11 may include an Xn application protocol (XnAP) message. For example, the message M11 is an SN ADDITION REQUEST XnAP message (which is defined in 3GPP specification) during: (1) SN addition procedure; (2) SN change procedure; (3) conditional primary secondary cell (PSCell) addition procedure; or (4) conditional PSCell change procedure. In some embodiments, the message M11 is an SN MODIFICATION REQUEST XnAP message (which is defined in 3GPP specification) during an MN initiated SN modification procedure.

In some embodiments, after receiving the message M11 (e.g., SN MODIFICATION REQUEST or SN MODIFICATION REQUEST) including the information from the network device 102A, the network device 102B may accept the message M11, and may follow the NES cell condition during later configuration/reconfiguration procedure (s) (e.g., an SN initiated a secondary cell group (SCG) reconfiguration procedure or a PSCell change procedure) when serving the UE 101.

In some embodiments, the NES cell condition includes : (1) the network device 102B serves (or being allowed to serve) the UE 101 with only NES cell in an SCG; (2) the network device 102B serves (or being allowed to serve) the UE 101 with at least one non-NES cell in the SCG; (3) the network device 102B serves (or being allowed to serve) the UE 101 with only non-NES cell in the SCG; or (4) the network device 102B is prohibited from configuring a PSCell in the SCG as NES cell.

In other words, the indication indicates the network device 102B that: (1) the network device 102B shall serve the UE 101 with only NES cell in the SCG; (2) the network device 102B shall not serve the UE 101 with only NES cell in the SCG; (3) the network device 102B shall not serve the UE 101 with any NES cell in the SCG; or (4) the network device 102B shall not configure the PSCell in the SCG as NES cell.

In some implementations, when the indication indicates the network device 102B that the network device 102B shall serve the UE 101 with only NES cell in the SCG, the network device 102B shall configure the PSCell and all possible secondary cell (SCell) (s) , which are in the SCG, to serve the UE 101 in NES mode. The UE 101 may expect to have low UL/DL traffic load over the SCG. In some cases, when the SCG has only one cell, it is a PSCell.

In some implementations, when the indication indicates the network device 102B that the network device 102B shall not serve the UE 101 with only NES cell in the SCG, the network device 102B shall configure and activate at least one non-NES cell (e.g., may be either PSCell or SCell) in the SCG for serving the UE 101. The UE 101 may expect to have medium UL/DL traffic load over the SCG. For example, when an MN terminated SCG bearer or an MN terminated split bearer is configured and the network device 102A may mainly use an SCG path for DL transmission, the

network devices

102A and 102B configures and activates at least one non-NES cell in the SCG. In some cases, when the SCG has only one cell, it is a PSCell.

In some implementations, when the indication indicates the network device 102B that the network device 102B shall not serve the UE 101 with any NES cell in the SCG, the network device 102B shall configure the PSCell and all possible SCell (s) , which are in the SCG, to serve the UE 101 in non-NES mode. The UE 101 may expect to have high UL/DL traffic load over the SCG. In some cases, when the SCG has only one cell, it is a PSCell.

For example, when the network device 102A transmits the message M11 including the indication to the network device 102B to indicates that network device 102B shall not serve the UE 101 with only NES cell (s) , the network device 102B configures at least one activated serving cell (e.g., a PSCell or possible SCell (s) ) in the SCG being non-NES cell during possible procedure (s) .

FIG. 3 is a schematic diagram of message transmission in accordance with some embodiments of the present application. In particular, the network device 102A is an MN serving the UE 101 under the DC mode, and the network device 102B is an SN serving the UE 101 under the DC mode. The network device 102A transmits a message M21 including an information to the network device 102B. The information may be: (1) an NES cell status of a cell group (e.g., master cell group (MCG) ) of the network device 102A; or (2) a primary path information corresponding to the UE 101. After receiving the message M21, the network device 102B transmits a message M22 to the network device 102A for acknowledging receiving the message M11.

In some embodiments, the message M21 may include an XnAP message. For example, the message M11 is an SN ADDITION REQUEST XnAP message (which is defined in 3GPP specification) during: (1) SN addition procedure; (2) SN change procedure; (3) conditional primary secondary cell (PSCell) addition procedure; or (4) conditional PSCell change procedure. For another example, the message M21 is an SN MODIFICATION REQUEST XnAP message (which is defined in 3GPP specification) during an MN initiated SN modification procedure.

In some embodiments, the NES cell status indicates to the network device 102B that each cell in the MCG of the network device 102A is an NES cell. In other words, all cell (s) in the MCG of the network device 102A is (are) NES cell (s) . The network device 102B is prohibited from configuring an SN terminated MCG bearer when each cell in the MCG of the network device 102A is the NES cell. In other words, after being aware of that the cell (s) in the MCG is (are) NES cell (s) , the network device 102B shall not configure any SN terminated MCG bearer. In addition, regarding an SN terminated split bearer, the network device 102B shall configure the SCG path as a primary path because the network device 102B may need to reduce the DL traffic transmitted over the SN terminated MCG bearer or over an MCG path of the SN terminated split bearer.

In some embodiments, the primary path information includes that the primary path of the MN terminated split bearer is the SCG path. The network device 102B shall configure the SCG with at least one activated non-NES cell when the primary path information includes that the primary path of the MN terminated split bearer is the SCG path.

FIG. 4 is a schematic diagram of message transmission in accordance with some embodiments of the present application. In particular, the network device 102A is an MN serving the UE 101 under the DC mode, and the network device 102B is an SN serving the UE 101 under the DC mode. The network device 102B transmits a message M31 including an information to the network device 102A. The information may be: (1) an NES cell status of a cell group (e.g., SCG) of the network device 102B; or (2) a primary path information corresponding to the UE 101. After receiving the message M31, the network device 102A transmits a message M32 to the network device 102B for acknowledging receiving the message M31.

In some embodiments, the message M31 may include an XnAP message. For example, the message M31 is an SN MODIFICATION REQUIRED XnAP message (which is defined in 3GPP specification) during an SN initiated SN modification procedure.

In some embodiments, the NES cell status indicates to the network device 102A that each cell in the SCG of the network device 102B is an NES cell. In other words, all cell (s) in the SCG of the network device 102B is (are) NES cell (s) . The network device 102A is prohibited from configuring an MN terminated SCG bearer when each cell in the SCG of the network device 102B is the NES cell. In other words, after being aware of that the cell (s) in the SCG is (are) NES cell (s) , the network device 102A shall not configure any MN terminated SCG bearer. In addition, regarding an MN terminated split bearer, the network device 102A shall configure the MCG path as a primary path because the network device 102A may need to reduce the DL traffic transmitted over the MN terminated SCG bearer or over the SCG path of the MN terminated split bearer.

In some embodiments, the primary path information includes that the primary path of the SN terminated split bearer is the MCG path. The network device 102A shall configure the MCG with at least one activated non-NES cell when the primary path information includes that the primary path of the SN terminated split bearer is the MCG path.

FIG. 5 is a schematic diagram of message transmission in accordance with some embodiments of the present application. In particular, the network, which includes the

network devices

102A and 102B, serves the UE 101 under the DC mode. The UE 101 may determine that one of two paths of a split bearer is served by only NES cell. The UE 101 may transmit a message M41 to the network according to the result of determining the one of two paths of the split bearer is served by only NES cell. The message M41 may include an uplink data or a signaling (i.e., control signal) .

In some embodiments, the one of two paths is a primary path and the other of the two paths is a secondary path. The UE 101 may transmits the uplink data or the signaling to the network via the primary path or the secondary path according to the result of determining the one of two paths of the split bearer is served by only NES cell.

For example, when the primary path of the split bearer is served by only NES cell and the secondary path of the split bearer is served by at least one non-NES cell, the UE 101 ignores a primary path configuration (e.g., the ul-DataSplitThreshold which is defined in 3GPP specification) . Then, the UE 101: (1) always uses the secondary path for UL data transmission; or (2) selects the primary path or the secondary path for UL data transmission.

In some embodiments, the UE 101 may determine that: (1) the one of two paths of the split bearer is served by only NES cell; and (2) the other of the two paths is served by at least one non-NES cell. The UE 101 may transmit the uplink data or the signaling to the network via the other of the two paths according to the results of determining the one of two paths of the split bearer is served by only NES cell and determining the other of two paths of the split bearer is served by at least one non-NES cell.

For example, among the two paths of the split DRB, when the one path is only served by NES cell and the other path is served by at least one non-NES cell, the UE 101: (1) always uses the path served by at least one non-NES cell as the primary path without applying the primary path configuration (e.g., the ul-DataSplitThreshold which is defined in 3GPP specification) ; or (2) automatically uses the path served by at least one non-NES cell as the primary path and ignores the configuration from the network.

In some embodiments, the one of two paths of the split bearer is the primary path and the signaling may include an indication for indicating to the network that the primary path is served by only NES cell. For example, when the primary path of the split bearer is served with only NES cell, the UE 101 generates the indication and transmits the indication to the network. The indication may be a radio resource control (RRC) message for indicating inappropriate configuration of that the primary path of the split bearer is served with only NES cell. The indication may an RRC message, a media access control-control element (MAC-CE) or a downlink control information (DCI) requesting at least one of the cell (s) for the primary path to enter non-NES mode.

FIG. 6 illustrates an example block diagram of an apparatus 6 according to an embodiment of the present disclosure.

As shown in FIG. 6, the apparatus 6 may include at least one non-transitory computer-readable medium (not illustrated in FIG. 6) , a transceiver 601 and a processor 603 electrically coupled to the non-transitory computer-readable medium (not illustrated in FIG. 6) and the transceiver 601. The apparatus 6 may be a UE or a network device such as a BS.

Although in this figure, elements such as transceiver 601 and processor 603 are described in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present disclosure, the transceiver 601 may be separated into to circuitry, such as a receiving circuitry and a transmitting circuitry. In certain embodiments of the present disclosure, the apparatus 6 may further include an input device, a memory, and/or other components.

In some embodiments of the present disclosure, the non-transitory computer-readable medium may have stored thereon computer-executable instructions to cause a processor to implement the operations with respect to the UE or the network devices as described above. For example, the computer-executable instructions, when executed, cause the processor 603 interacting with the transceiver 601, so as to perform the operations with respect to the UE or the network devices depicted in the figures.

Those having ordinary skill in the art would understand that the operations of a method described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Additionally, in some aspects, the steps of a method may reside as one or any combination or set of codes and/or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.

While this disclosure has been described with specific embodiments thereof, it is evident that many alternatives, modifications, and variations may be apparent to those skilled in the art. For example, various components of the embodiments may be interchanged, added, or substituted in the other embodiments. Also, all of the elements of each figure are not necessary for operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments would be enabled to make and use the teachings of the disclosure by simply employing the elements of the independent claims. Accordingly, embodiments of the disclosure as set forth herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the disclosure.

In this document, the terms "includes" , "including" , or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "a" , "an" , or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element. Also, the term "another" is defined as at least a second or more. The term "having" and the like, as used herein, are defined as "including" .

In this document, the terms "comprises, " "comprising, " or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "a, " "an, " or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element. Also, the term "another" is defined as at least a second or more. The terms "including, " "having, " and the like, as used herein, are defined as "comprising. "

Claims

A network device serving a user equipment (UE) under a dual connectivity (DC) mode, comprising:

a processor; and

a transceiver coupled to the processor;

wherein the processor is configured to:

receive, via the transceiver, a first information from another network device, wherein the first information includes:

an indication for indicating the network device to serve the UE based on a network energy saving (NES) cell condition;

a first NES cell status of a cell group of the another network device; or

a first primary path information corresponding to the UE; or

transmit, via the transceiver, a second information to the another network device, wherein the second information includes:

a second NES cell status of a cell group of the network device; or

a second primary path information corresponding to the UE.
The network device of claim 1, wherein the network device is a secondary node (SN) and the another network device is a master node (MN) under the DC mode.
The network device of claim 2, wherein the NES cell condition includes that:

the SN is allowed to serve the UE with only NES cell in a secondary cell group (SCG) ;

the SN serves the UE with at least one non-NES cell in the SCG;

the SN serves the UE with only non-NES cell in the SCG; or

the SN is prohibited from configuring a primary secondary cell (PSCell) in the SCG as NES cell.
The network device of claim 2, wherein the first NES cell status indicates to the SN that each cell in a master cell group (MCG) of the MN is an NES cell, and the second NES cell status indicates to the MN that each cell in a secondary cell group (SCG) of the SN is an NES cell.
The network device of claim 4, wherein the processor is further configured to:

prohibit from configuring an SN terminated MCG bearer when each cell in the MCG of the MN is the NES cell.
The network device of claim 4, wherein the processor is further configured to:

configure an SCG path as a primary path for an SN terminated split bearer.
The network device of claim 2, wherein the first primary path information includes that a first primary path of an MN terminated split bearer is a secondary cell group (SCG) path, and the second primary path information includes that a second primary path of an SN terminated split bearer is a master cell group (MCG) path.
The network device of claim 7, wherein the processor is further configured to:

configure an SCG with at least one activated non-NES cell when the first primary path information includes that the first primary path of the MN terminated split bearer is the SCG path.
The network device of claim 1, wherein the first information or the second information is included in an Xn application protocol (XnAP) message.
A network device serving a user equipment (UE) under a dual connectivity (DC) mode, comprising:

a processor; and

a transceiver coupled to the processor;

wherein the processor is configured to:

transmit, via the transceiver, a first information to another network device, wherein the first information includes:

an indication for indicating the network device to serve the UE based on a network energy saving (NES) cell condition;

a first NES cell status of a cell group of the network device; or

a first primary path information corresponding to the UE; or

receive, via the transceiver, a second information from the another network device, wherein the second information includes:

a second NES cell status of a cell group of the another network device; or

a second primary path information corresponding to the UE
The network device of claim 10, wherein the network device is a master node (MN) and the another network device is a secondary node (SN) under the DC mode.
A user equipment (UE) served by a network under a dual connectivity (DC) mode, comprising:

a processor; and

a transceiver coupled to the processor;

wherein the processor is configured to:

determine one of two paths of a split bearer is served by only network energy saving (NES) cell; and

transmit, via the transceiver, uplink data or a signaling to the network according to the result of determining the one of two paths of the split bearer is served by only NES cell.
The UE of claim 12, wherein the one of two paths is a primary path, the other of the two paths is a secondary path, and the processor is further configured to:

transmit, via the transceiver, the uplink data or the signaling to the network via the primary path or the secondary path according to the result of determining the one of two paths of the split bearer is served by only NES cell.
The UE of claim 12, wherein the processor is further configured to:

determine the other of the two paths is served by at least one non-NES cell;

transmit, via the transceiver, the uplink data or the signaling to the network via the other of the two paths according to the results of determining the one of two paths of the split bearer is served by only NES cell and determining the other of two paths of the split bearer is served by at least one non-NES cell.
The UE of claim 12, wherein the one of two paths of the split bearer is a primary path, and the signaling includes an indication for indicating to the network that the primary path is served by only NES cell.