H04W36/18

Device and Method of Handling a Handover
20230058443 · 2023-02-23 · ·

A method for handling a handover of a communication device includes receiving a radio resource control (RRC) configuration message from a source network, wherein the RRC configuration message includes at least one execution condition of at least one target network; transmitting a handover trigger message to the source network, when an execution condition of the at least one execution condition is satisfied; performing the handover from the source network to a target network of the at least one target network, wherein the target network is corresponding to the execution condition; and transmitting a handover complete message to the target network, after performing the handover.

METHOD AND APPARATUS FOR PERFORMING HANDOVER PROCEDURE IN WIRELESS COMMUNICATION SYSTEM
20220369171 · 2022-11-17 ·

An operating method of a user equipment (UE) in a wireless communication system according to an embodiment of the disclosure may include receiving configuration information from a source base station (BS), determining, based on the configuration information, whether Dual Active Protocol Stack (DAPS) handover is configured for at least one bearer, based on a result of the determining, maintaining a link to the source BS, performing the DAPS handover on a target BS, suspending a Signaling Radio Bearer (SRB) configured for the source BS, and establishing a SRB for the target BS, when it is determined that the DAPS handover fails, determining whether a radio link failure (RLF) occurs in the link to the source BS, and based on a result of the determining, when the RLF does not occur in the link to the source BS, resuming the SRB configured for the source BS and reporting the failure of the DAPS handover.

NON-SIMULTANEOUS TRANSMIT-RECEIVE (NSTR) SOFT ACCESS POINT (AP) MULTI-LINK DEVICE (MLD)

A wireless station (STA) operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with a primary link and a non-primary link determines that the non-primary link is unavailable, and transmits, on only the primary link, a frame carrying an indication of the unavailability of the non-primary link. The NSTR softAP MLD may set a Do Not Transmit (DNT) bit to a value of 1 and may operate as a single-link device on the primary link based on the unavailability of the non-primary link. In some instances, the NSTR softAP MLD determines that the non-primary link is available while operating as the single-link device on the primary link, resets the DNT bit based on the availability of the non-primary link, and transmits the reset DNT bit in another frame on only the primary link.

NON-SIMULTANEOUS TRANSMIT-RECEIVE (NSTR) SOFT ACCESS POINT (AP) MULTI-LINK DEVICE (MLD)

A wireless station (STA) operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with a primary link and a non-primary link determines that the non-primary link is unavailable, and transmits, on only the primary link, a frame carrying an indication of the unavailability of the non-primary link. The NSTR softAP MLD may set a Do Not Transmit (DNT) bit to a value of 1 and may operate as a single-link device on the primary link based on the unavailability of the non-primary link. In some instances, the NSTR softAP MLD determines that the non-primary link is available while operating as the single-link device on the primary link, resets the DNT bit based on the availability of the non-primary link, and transmits the reset DNT bit in another frame on only the primary link.

Method and apparatus for distinguishing between data formats, and communication device

The embodiments of the present disclosure provide a method and apparatus for distinguishing between data formats, and a communication device. The method includes a terminal receives a downlink data packet, and determines whether the data format of the downlink data packet is a first data format or a second data format, wherein the first data format indicates that the downlink data packet is encrypted using a first key of a source base station and/or compressed using a first header compression format of the source base station, and the second data format indicates that the downlink data packet is encrypted using a second key of a target base station and/or compressed using a second header compression format of the target base station.

Method and apparatus for distinguishing between data formats, and communication device

The embodiments of the present disclosure provide a method and apparatus for distinguishing between data formats, and a communication device. The method includes a terminal receives a downlink data packet, and determines whether the data format of the downlink data packet is a first data format or a second data format, wherein the first data format indicates that the downlink data packet is encrypted using a first key of a source base station and/or compressed using a first header compression format of the source base station, and the second data format indicates that the downlink data packet is encrypted using a second key of a target base station and/or compressed using a second header compression format of the target base station.

Xx/Xn protocol programmability

A method for Xx/Xn interface communication is disclosed, comprising: at an Xx/Xn gateway for communicating with, and coupled to, a first and a second radio access network (RAN), receiving messages from the first RAN according to a first Xx/Xn protocol and mapping the received messages to a second Xx/Xn protocol for transmission to the second RAN; maintaining state of one of the first RAN or the second RAN at the Xx/Xn gateway; executing executable code received at an interpreter at the Xx/Xn gateway as part of the received messages; altering the maintained state based on the executed executable code; and receiving and decoding an initial Xx/Xn message from the first RAN; identifying specific strings in the initial Xx/Xn message; matching the identified specific strings in a database of stored scripts; and performing a transformation on the initial Xx/Xn message, the transformation being retrieved from the database for stored scripts, the stored scripts being transformations.

Xx/Xn protocol programmability

A method for Xx/Xn interface communication is disclosed, comprising: at an Xx/Xn gateway for communicating with, and coupled to, a first and a second radio access network (RAN), receiving messages from the first RAN according to a first Xx/Xn protocol and mapping the received messages to a second Xx/Xn protocol for transmission to the second RAN; maintaining state of one of the first RAN or the second RAN at the Xx/Xn gateway; executing executable code received at an interpreter at the Xx/Xn gateway as part of the received messages; altering the maintained state based on the executed executable code; and receiving and decoding an initial Xx/Xn message from the first RAN; identifying specific strings in the initial Xx/Xn message; matching the identified specific strings in a database of stored scripts; and performing a transformation on the initial Xx/Xn message, the transformation being retrieved from the database for stored scripts, the stored scripts being transformations.

Loss-less transmission for unacknowledged mode (UM) data radio bearer (DRB)

Disclosed are techniques for wireless communication. In an aspect, a packet data convergence protocol (PDCP) entity of a receiver device receives, from a radio link control (RLC) entity of the receiver device, a plurality of RLC data packets received from a transmitter device over an RLC unacknowledged mode (UM) data radio bearer (DRB) or RLC transparent mode (TM) DRB. The PDCP entity generates a plurality of PDCP data packets corresponding to the plurality of RLC data packets. The receiver device determines to send a PDCP status report indicating a reception status at the receiver device of the plurality of PDCP data packets and transmits the PDCP status report to a PDCP entity of the transmitter device. The receiver device receives, in response to sending the PDCP status report, one or more PDCP data packets of the plurality of PDCP data packets that were not successfully received at the receiver device.

Methods Providing Transmission of UL Data to a Source Access Node after Establishing Connection with a Target Access Node and Related Wireless Devices

A method of operating a wireless device (300) is described. The method includes providing (1001) a connection with a source access node. The method also includes receiving (1005) a handover command from the source access node while providing the connection with the source access node. The method also includes establishing (1009) a connection with a target access node responsive to receiving the handover command. The method further includes transmitting (1019) uplink data to the source access node after establishing the connection with the target access node. Related wireless devices are also discussed.