WO2024092637A1

WO2024092637A1 - Radio resource control segment transmission continuity

Info

Publication number: WO2024092637A1
Application number: PCT/CN2022/129613
Authority: WO
Inventors: Fangli Xu; Haijing Hu; Sethuraman Gurumoorthy; Zhibin Wu; Naveen Kumar R. PALLE VENKATA; Ralf ROSSBACH; Peng Cheng; Ping-Heng Kuo
Original assignee: Apple Inc.
Priority date: 2022-11-03
Filing date: 2022-11-03
Publication date: 2024-05-10

Abstract

The present application relates to devices and components including apparatus, systems, and methods to provide segmented message transmission continuity in wireless communication systems.

Description

RADIO RESOURCE CONTROL SEGMENT TRANSMISSION CONTINUITY

TECHNICAL FIELD

This application relates generally to wireless communication systems, and in particular relates to radio resource control segment transmission continuity.

BACKGROUND

Third Generation Partnership Project (3GPP) networks provide for messages to be exchanged between a base station and a user equipment. In some instances, a message is segmented for transmission between the base station and the user equipment (UE) . In these instances, each of the segments of the segmented message is transmitted in separate transmissions between the base station and the UE. Further, handover (HO) operations can be performed to transition a connection of the UE from a first base station to a second base station. When a HO operation is performed when a portion of the segments of the segmented message have yet to be transmitted all segments of the segmented message would be retransmitted after completion of the HO operation via the new connection.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example uplink (UL) message segment transfer arrangement in accordance with some embodiments.

FIG. 2 illustrates an example legacy radio resource control (RRC) configuration arrangement in accordance with some embodiments.

FIG. 3 illustrates an example legacy UL RRC segment arrangement in accordance with some embodiments.

FIG. 4 illustrates an example UL RRC segment handover (HO) signaling chart in accordance with some embodiments.

FIG. 5 illustrates an example signaling chart illustrating option 1 for determining successful RRC segment reception in accordance with some embodiments.

FIG. 6 illustrates an example signaling chart illustrating option 2 for determining successful RRC segment reception in accordance with some embodiments.

FIG. 7 illustrates an example signaling chart illustrated in option 3 for determining successful RRC segment reception in accordance with some embodiments.

FIG. 8 illustrates an example RRC message in accordance with some embodiments.

FIG. 9 illustrates an example packet data control protocol (PDCP) control packet data unit (PDU) in accordance with some embodiments.

FIG. 10 illustrates an example radio link control (RLC) control PDU in accordance with some embodiments.

FIG. 11 illustrates an example medium access control (MAC) control element (CE) in accordance with some embodiments.

FIG. 12 illustrates an example signaling chart showing HO with UL RRC segment continuity in accordance with some embodiments.

FIG. 13 illustrates example signaling chart showing path switching with downlink (DL) RRC segment continuity in accordance with some embodiments.

FIG. 14 illustrates an example signaling chart with RRC segment status reporting in accordance with some embodiments.

FIG. 15 illustrates another example signaling chart with RRC segment status reporting in accordance with some embodiments.

FIG. 16 illustrates an example signaling chart with timer based RRC segment status feedback in accordance with some embodiments.

FIG. 17 illustrates an example signaling chart with timer based RRC segment status feedback in accordance with some embodiments.

FIG. 18 illustrates an example procedure of operating a transmitting device in accordance with some embodiments.

FIG. 19 illustrates a first portion of an example procedure of operating a receiving device in accordance with some embodiments.

FIG. 20 illustrates a second portion of the example procedure of operating the receiving device in accordance with some embodiments.

FIG. 21 illustrates an example procedure of operating a receiving device in accordance with some embodiments.

FIG. 22 illustrates an example user equipment (UE) in accordance with some embodiments.

FIG. 23 illustrates an example next generation NodeB (gNB) in accordance with some embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase “A or B” means (A) , (B) , or (A and B) .

The following is a glossary of terms that may be used in this disclosure.

The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) , an application specific integrated circuit (ASIC) , a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA) , a programmable logic device (PLD) , a complex PLD (CPLD) , a high-capacity PLD (HCPLD) , a structured ASIC, or a programmable system-on-a-chip (SoC) ) , digital signal processors (DSPs) , etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, or transferring digital data. The term “processor circuitry” may refer an application processor, baseband processor, a central processing unit (CPU) , a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, or functional processes.

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, or the like.

The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” or “system” may refer to multiple computer devices or multiple computing systems that are communicatively coupled with one another and configured to share computing or networking resources.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, or the like. A “hardware resource” may refer to compute, storage, or network resources provided by physical hardware element (s) . A “virtualized resource” may refer to compute, storage, or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with or equivalent to “communications channel, ” “data communications channel, ” “transmission channel, ” “data transmission channel, ” “access channel, ” “data access channel, ” “link, ” “data link, ” “carrier, ” “radio-frequency carrier, ” or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices for the purpose of transmitting and receiving information.

The terms “instantiate, ” “instantiation, ” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The term “connected” may mean that two or more elements, at a common communication protocol layer, have an established signaling relationship with one another over a communication channel, link, interface, or reference point.

The term “network element” as used herein refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, or the like.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. An information element may include one or more additional information elements.

In Third Generation Partnership Project (3GPP) networks, the network may configure a user equipment (UE) with message segmentation, such as radio resource control (RRC) –segmentation. When the message segmentation is enabled and encoded messages larger than a maximum size of a packet data convergence protocol (PDCP) , the encoded messages may be segmented for transmission between the network and the UE.

Additionally, mobility event operations may be performed to transition connections of a UE from a first base station of the network to a second base station of the network, or to change a path for communication with the UE. For example, an HO operation may be initiated based on the UE being moved from a geographical area serviced by the first base station to a geographical area serviced by the second base station.

In some instances, a mobility event operation may be initiated while segments of a segmented message are being transmitted between a UE and a base station. Where the mobility event operation is initiated when a portion of the segments of a segmented message have been transmitted and another portion of the segments of the segmented message have yet to be transmitted, the transmission of the segmented message may be complicated. In legacy approaches, segments of the segmented message received by a receiving device and stored by the receiving device prior to the initiation of the mobility event operation were discarded from storage. In these instances, all of the segments of the segmented message would be retransmitted. This retransmission of all of the segments of the segmented message is inefficient and can be a waste of resources.

Approaches presented herein can address the inefficiencies of retransmitting all of the segments of the segmented message when a mobility event operation occurs. In particular, the segments of the segmented message transmitted prior to the mobility event operation may be stored and utilized for the processing of the segmented message in the approaches described herein.

Legacy SRB transmission

The signaling radio bearer (SRB) is for the control plane data transmission. SRB0 for common control channel (CCCH) transmission.

SRB

1, 2, 3, 4 for dedicated control channel (DCCH) transmission. For example, an SRB transmission may be utilized for control plane data transmission. SRB0 may be used for CCCH transmissions. SRB1, SRB2, SRB3, and SRB4 may be utilized for DCCH transmissions.

Uplink (UL) segment transmission is supported for the SRB1 and SRB4 transmission. The UE capability reporting via SRB1 and quality of experience (QoE) reporting via SRB4 support the UL segmentation transmission. The segmentation mode is explicitly configured by network (NW) based on UE and NW capability. If the RRC-segmentation is enabled, and if the encoded RRC message is larger than the maximum size of the PDCP service data unit (SDU) , UE will initiate the UL message segment transfer procedure.

For the UL RRC message segment transfer procedure. The UE segments the encoded RRC protocol data unit (PDU) based on the maximum size of a PDCP SDU, and sets the contents of the ULDedicatedMessageSegment messages as follows: 1> For each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the segmentNumber for each subsequent RRC message segment; 1> set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the segmentNumber; 1> if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message: 2> set the rrc-MessageSegmentType to lastSegment; 1> else: 2> set the rrc-MessageSegmentType to notLastSegment; 1> submit all the messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends.

FIG. 1 illustrates an example UL message segment transfer arrangement 100 in accordance with some embodiments. For example, the UL message segment transfer arrangement 100 illustrates an example segmented message transmitted in the UL direction.

The UL message segment transfer arrangement 100 may include a UE 102. The UE 102 may include one or more of the features of UE 2200 (FIG. 22) . The UE 102 may be configured in segmentation mode in the illustrated embodiment.

The UL message segment transfer arrangement 100 may include an NW element 104. The NW element 104 may comprise a nodeB, such as a next generation nodeB (gNB) , an evolved nodeB (eNB) , or some other type of nodeB. The NW element 104 may include one or more the features of the gNB 2300 (FIG. 23) . In the illustrated embodiment, the UE 102 may be connected to the NW element 104.

The UE 102 may have a message 106 to be transmitted to the NW element 104. In some embodiments, the message 106 may be in RRC message. The message 106 may be larger than a maximum size of a PDCP SDU. Due to this message 106 being larger than the maximum size of the PDCP SDU, the UE 102 may segment the message 106 into multiple segments. Each of the segments may be assigned a segment number, where a first segment may be assigned a first segment number in an order, a second segment may be assigned a second segment number in the order, and so forth. The UE 102 may transmit the segments of the message 106 to the NW element 104, where each of the segments may be transmitted in its own transmission. The NW element 104 may receive the segments and reassemble the message 106 once all of the segments of the message 106 have been received.

Legacy RRC configuration and RRC segment format

FIG. 2 illustrates an example legacy radio resource control (RRC) configuration arrangement 200 in accordance with some embodiments. For example, the RRC configuration arrangement 200 illustrates example information elements that can be utilized to indicate segmentation configuration.

The RRC configuration arrangement 200 includes a UE-NR-Capability-v1690 information element 202. The UE-NR-Capability-v1690 information element 202 includes a ul-RRC-Segmentation-r16 information element 204. The ul-RRC-Segmentation-r16 information element 204 may indicate whether the UE is configured to implement segmentation to RRC.

The RRC configuration arrangement 200 further includes an AppLayerMeasConfig information element 206. The AppLayerMeasConfig information element 206 includes an rrc-SegAllowed-r17 information element 208. The rrc-SegAllowed-r17 information element 208 may indicate whether RRC segmentation is allowed.

FIG. 3 illustrates an example legacy UL RRC segment arrangement 300 in accordance with some embodiments. The UL RRC segment arrangement 300 includes a ULDedicatedMessageSegment format 302. In the illustrated embodiment, the ULDedicatedMessageSegment format 302 is for signaling radio bearer SRB1 or SRB4. Further, the ULDedicatedMessageSegment format 302 is used for transmissions from the UE to the NW via the DCCH logical channel.

The ULDedicatedMessageSegment format 302 includes a segmentNumber field 306, a MessageSegmentContainer field 308, and a MessageSegmentType field 310. The segmentNumber field 306 identifies a sequence number of the segment within the encoded UL DCCH message. The MessageSegmentContainer field 308 includes a segment of the encoded UL DCCH message. The MessageSegmentType field 310 indicates whether the included UL DCCH message to is the last segment for not last segment. While the ULDedicatedMessageSegment format 302 illustrated is for UL segmented transmissions, it should be understood that a similar format is implemented for DL segmented transmissions.

Issue Statement

Legacy UE operation on the UL RRC segments handling during handover. When performing the HO, UE will discard the previous transmitted RRC segments, and RRC will resubmit the previous whole RRC message in the new serving cell. For example, when a HO operation is performed while segments of a segmented message are being transmitted and not all of the segments of the segmented message have been transmitted or all of the segments of the segmented message have not been confirmed as successfully received by the receiving device, the segments received by a receiving device prior to the HO operation are discarded in legacy approaches. All of the segments of the segmented message are then transmitted after the HO operation, including retransmission of the segments previously transmitted prior to the HO operation. This retransmission of the segments can be efficient and is a waste of resources.

For example, 3> if configured with application layer measurements and if application layer measurement report container has been received from upper layers for which the successful transmission of the message or at least one segment of the message has not been confirmed by lower layers: 4> re-submit the MeasurementReportAppLayer message or all segments of the MeasurementReportAppLayer message to lower layers for transmission via SRB4.

The drawback. Due to the whole RRC message retransmission in the target cell, if some segments have been successfully transmitted in the source cell, the UE still needs to retransmit these segments in the target cell. This is a waste of the radio resource.

Further enhancement. RRC segment transmission continuity during the handover can be considered, and UE does not need to retransmit the segments which has been transmitted successfully. For example, the approaches described herein may provide segment transmission continuity during a HO operation, such that segments that have been successfully transmitted prior to the HO operation do not need to be retransmitted. Accordingly, the inefficiency and waste of resources of the legacy approaches is not presented by the approaches described herein.

NOTE. The mechanism can be applicable on the current SRB4 UL segment transmission for the QoE MeasReportAppLayer transmission. The mechanism can be applicable on the UL/downlink (DL) RRC segment transmission for the new RRC message or new SRB which it’s introduced in the future, e.g., artificial intelligence (AI) , sensing related information configuration or/and report.

FIG. 4 illustrates an example UL RRC segment HO signaling chart 400 in accordance with some embodiments. For example, the UL RRC segment HO signaling chart 400 illustrates an example of transmission of segments of an RRC message within HO operation in accordance legacy approaches.

The UL RRC segment HO signaling chart 400 includes a UE 402. The UE 402 may include one or more of the features of the UE 2200 (FIG. 22) . The UE 402 may be configured in a segmentation mode. In the illustrated embodiment, the UE 402 may have a message to be transmitted to the NW. In some embodiments, the message may be an RRC message to be transmitted to the NW. Due to his size of the message, the message may be segmented into four segments in the illustrated embodiment.

The UL RRC segment HO signaling chart 400 further includes a source gNB 404 source gNB 404 may include one or more the features of the gNB 2300 (FIG. 23) . The UE 402 may a connection established with the source gNB 404 at the beginning of the signaling shown in the illustrated embodiment.

The UL RRC segment HO signaling chart 400 further includes a target gNB 406. The target gNB 46 may include one or more the features of the gNB 2300. The HO operation shown in the illustrated embodiment may transition the connection of the UE 402 from the source gNB 404 for to the target gNB 406.

The UE 402 may transmit a first segment of the message in transmission 408, a second segment of the message in transmission 410, and a third segment of the message in transmission 412. The first segment may be transmitted in a first radio link control (RLC) PDU, the second segment may be transmitted in a second RLC PDU, and the third segment may be transmitted in a third RLC PDU. The transmission 408, the transmission 410, and the transmission 412 may be transmitted prior to the HO operation to transition the connection of the UE 402 from the source gNB 404 to the target gNB 406.

The source gNB 404 may receive the transmission 408, the transmission 410, and the transmission 412 from the UE 402. The source gNB 404 may identify the first segment from the transmission 408, the second segment from the transmission 410, and the third segment from the transmission 412. The source gNB 404 may store the first segment, the second segment, and the third segment of the segmented message. Based on the source gNB 404 storing the first segment, the second segment, and the third segment, the source gNB 404 may determine that the first segment, the second segment, and the third segment have been successfully received from the UE 402. Based on the determination that the first segment, the second segment, and the third segment have been successfully received, the source gNB 404 may transmit an acknowledgment message 414 to the UE 402 acknowledging that the first segment, the second segment, and the third segment have been successfully received. In some embodiments, the source gNB 404 may transmit separate acknowledgment messages for each of the segments received from the UE 402.

The UE 402 may identify the acknowledgment message 414 received from the source gNB 404. Based on the acknowledgment message 414 the UE 402 may determine that the first segment, the second segment, and the third segment of the segmented message have been successfully received by the source gNB 404, as indicated by MeasReportAppLayer representation 416 showing checkmarks on the first three segment of the segmented message.

After reception of the transmission 412 and HO operation may be initiated. The HO operation may include HO preparation 418 between the source gNB 404 and the target gNB 406. The HO preparation 418 may include exchanging transmissions between the source gNB 404 and the target gNB 406 to prepare for transfer of the connection for the UE 402 from the source gNB 442 the target gNB 406.

The HO operation may further include transmission of an HO command 420 from the source gNB 404 to the UE 402. For example, the source gNB 404 may transmit the HO command 420 to the UE 402 after completion of the HO preparation 418. The HO command 420 may indicates that the UE 402 is to transition a connection from the source gNB 404 to the target gNB 406. Based on the HO command 420, the UE 402 may perform an HO procedure to establish a connection with the target gNB 406 as part of the HO operation. The UE 402 may transmit an HO complete message 422 to the target gNB 406 that indicates the HO procedure has been completed.

Due to the HO operation, the source gNB 404 may purge the stored first segment, the second segment, and the third segment received from the UE 402. For example, the source gNB 404 may be configured to purge the stored first segment, the stored second segment, and the stored third segment based on the HO of the connection of the UE 402 from the source gNB 404 to the target gNB 406.

The target gNB 406 may not have received any of the segments of the segmented message upon completion of the HO operation, as indicated by MeasReportAppLayer 424 having no checkmarks on the segments of the segmented message. The UE 402 may be configured to retransmit the segments of the segmented message transmitted prior to the HO operation. In particular, the UE 402 may be configured to retransmit the first segment, the second segment, and the third segment of the segmented message to the target gNB 406 after completion of the HO operation.

The UE 402 may transmit the first segment, the second segment, the third segment, and the fourth segment of the segmented message to the target gNB 406 after completion of the HO operation. For example, the UE 402 may transmit the first segment in a transmission 426, the second segment in a transmission 428, the third segment in a transmission 430, and the fourth segment in a transmission 432 to the target gNB 406. The first segment may be transmitted in a first RLC PDU, the second segment may be transmitted in a second RLC PDU, the third segment may be transmitted in a third RLC PDU, and the fourth segment may be transmitted in a fourth RLC PDU.

As can be seen from the approach illustrated in the UL RRC segment HO signaling chart 400, the UE 402 transmits each of the first segment, the second segment, and the third segment of the segmented message twice, once to the source gNB 404 and once to the target gNB 406. Transmitting each of the segments twice is inefficient and a waste of resources. In particular, the transmission 426, the transmission 428, and transmission 430 are not needed in the approaches described throughout this disclosure.

Approach

General Description

Key points. Support the SRB level RRC segment transmission continuity during the mobility, i.e., no need to transmit all segments in the target cell. For example, transmission of segment of a segmented message may have continuity through mobility event. Support the RRC segment continuity for both UL segments and DL segments transmission. The mobility event may include the handover, RRC transmission path switch (SRB type change from one cell group (CG) to another CG) , bearer type switching, or SRB transmission switching. For handover, the continuity is across source cell and target cell; For the SRB path change in dual connectivity (DC) , the continuity is across the leg change from one CG to another CG.

Configuration and NW capability. New UE capability should be introduced for this feature. The feature is explicitly configured to UE via the RRC signaling, and the configuration can be for a special RRC message, and/or for a special SRB, and/or for UL direction/DL direction/bi-direction. For example, the NW may utilize RRC signaling to configure the UE for segment transmission continuity during mobility events as described throughout this disclosure. The NW may configure the UE for segment transmission continuity for an RRC message, for an SRB, for UL direction transmissions, for DL direction transmissions, and/or for bidirectional transmissions. Option 1: NW can configure UE to enable the RRC UL segment continuity when the corresponding SRB/function config is setup/modified; Option 2: NW can configure UE to enable the HO with RRC UL segment continuity in the mobility command. The configuration can be together with the mobility command, or when the SRB segment mode is configured. NW can decide whether to trigger the segment transmission continuity based on gNB capability.

Operation in receiving side. When the mobility event is triggered, keep (not flush) the RRC segments stored in the buffer. For example, a receiving device may receive one or more segments of a segmented message prior to a mobility event and may store the received segments in a buffer. When the mobility event occurs, the receiving device may continue to store the received segments in a buffer. After the mobility is performed successfully, receiving (Rx) side receives the remaining RRC segments and stores it in the buffer in sequence. For example, the receiving device may receive the remaining segments of a segmented message after completion of the mobility events and may store the remaining segments in the buffer in sequence. If all the RRC segments are received, assemble all the segments into the whole RRC message. For example, if the receiving device determines that all the segments of the segmented message are received, the receiving device may assemble the segmented message from the segments received by the receiving device. If the NW is the receiving side, for the inter-gNB handover case, source gNB will forwards the RRC segments to the target gNB via the data forwarding procedure, which is similar as the data radio bearer (DRB) data forwarding. For example, the source gNB to which a UE has a connection prior to a mobility event may provide the segments received prior to the mobility event to a target gNB to which the UE has a connection after the mobility event.

Operation in transmission side. When the mobility event is triggered, only submit the segments which are not transmitted or transmitted unsuccessfully. For example, the transmitting device may transmit only the segments of the segmented message which have not been transmitted or which were unsuccessfully transmitted prior to mobility event. Transmitting (Tx) side recognizes which segments are transmitted successfully via the feedback from the Rx side. For example, the receiving device may transmit one or more acknowledgment messages and/or one or more status reports that indicate which segments are successfully received by the receiving device. The transmitting device may determine which segments are successfully received based on the acknowledgment messages and/or the status reports. If the feedback is carried in layer 2 (L2) PDU, L2 informs the RRC segments receiving info to RRC via the internal L2-L3 interface, and it’s up to implementation.

L2/Data storage operation during the RRC segment continuity

RRC operation. Both Rx and Tx sides do not flush the RRC buffer, and keep the RRC segments stored in the RRC buffer (or in PDCP SDU buffer) . For example, a receiving device and a transmitting device may continue to store (rather than flush) received segments in a corresponding buffer. Tx side: the RRC segments is stored in the RRC buffer (or PDCP buffer) . For example, a transmitting device may store segments of the segmented message in an RRC buffer or a PDCP buffer of the transmitting device. Rx side: the received RRC segments are stored in the RRC buffer. For example, the receiving device may store segments of the segment message in an RRC buffer of the receiving device.

PDCP/RLC operation. Option 1: PDCP reestablishment + RLC reestablishment (or release+setup) . For example, a first option may apply to instances with PDCP reestablishment, RLC reestablishment, and/or RLC release and set up for the mobility event.

Tx side. RRC or PDCP triggers the remaining RRC segment transmission in the target cell. For example, the RRC or the PDCP of the transmitting device may trigger the transmitting device to transmit the segments of the segmented message that were not transmitted prior to the HO operation, and/or were not successfully received prior to the HO operation, to the target cell with which a connection is established based on the HO operation. PDCP processes the RRC segment as the new PDCP SDU.

Rx side. PDCP receives the PDCP PDU (including the RRC segment) according to the legacy procedure, and delivers the SDU part to RRC. For example, the PDCP of the receiving device may receive the PDCP PDU, including a segment of the segmented message, from the transmitting device and may deliver an SDU part to the RRC. RRC stores the RRC segment in RRC buffer, and assemble the RRC message if all the RRC segments are received. For example, the RRC may store the received segment of the segmented message in the RRC buffer. If all the segments of the segmented message are received the RRC may assemble the segments to produce the segmented message.

Option 2: PDCP recovery + RLC reestablishment (or release+setup) . For example, a second option may apply to instances with PDCP recovery, RLC reestablishment, and/or RLC release and set up. Tx side. PDCP performs the PDCP PDU retransmission in the target cell for the RRC segments transmitted but not received the ACK. For example, the transmitting device may determine which segments of the segmented message did not receive positive acknowledgment from the receiving device. The PDCP of the transmitting device may perform PDCP PDU retransmission of the segments that did not receive positive acknowledgment to the target cell with which a connection is established based on the HO operation. RRC delivers the RRC segment which is not transmitted to PDCP, and PDCP processes it as the PDCP SDU.

Determination on the (un) successfully transmitted RRC segment

Option 1: Based on RLC layer feedback. For example, in a first option a transmitting device may determine whether segments of a segmented message were successfully received by a receiving device based on RLC layer feedback. Assumption: SRB#X is configured with RLC acknowledge mode (AM) mode. For example, the first option may apply in instances where the SRB is configured with RLC AM mode. Rx side provides the RLC status report to Tx side to indicate which RLC PDU has been received. (legacy mechanism) . Tx side determines which RRC segments have been successfully transmitted via the RLC status report.

FIG. 5 illustrates an example signaling chart 500 illustrating option 1 for determining successful RRC segment reception in accordance with some embodiments. For example, the signaling chart 500 illustrates an approach for determining whether segments of a segmented message have been successfully received by a receiving device based on RLC layer feedback.

The signaling chart 500 may include a transmitting device 502. The transmitting device 502 may comprise a UE in some instances and may comprise a base station in other instances. The UE may include one or more of the features of the UE 2200 (FIG. 22) . The base station may include one or more the features of the gNB 2300 (FIG. 23) . The transmitting device 502 may be scheduled to transmit a message.

The signaling chart 500 may further include a receiving device 504. The receiving device 504 may comprise a base station in some instances and a UE and some other instances. For example, in instances where the transmitting device 502 is a UE, the receiving device 504 may be a base station. In instances where the transmitting device 502 is a base station, the receiving device 504 may be a UE. The UE may include one or more the features of the UE 2200. The base station may include one or more the features of the gNB 2300. The receiving device 504 may be scheduled to receive the message from the transmitting device 502.

Due to the size of the message, the transmitting device 502 may segment the message into four segments, as shown by message representation 506. The transmitting device 502 may transmit each of the segments of the message in separate RLC PDUs. For example, the transmitting device 502 transmits a first segment of the message in RLC PDU 508, a second segment of the message in RLC PDU 510, and a third segment of the message in RLC PDU 512 in the illustrated embodiment.

The receiving device 504 may receive the RLC PDUs transmitted by the transmitting device 502. The receiving device 504 may identify the segments of the message included in each of the RLC PDUs and may store the received segments. For example, the receiving device 504 may receive the RLC PDU 508, the RLC PDU 510, and the RLC PDU 512 in the illustrated embodiment. The receiving device 504 may identify the first segment within the RLC PDU 508, the second segment within the RLC PDU 510, and the third segment within the RLC PDU 512. The receiving device 504 may store the first segment, the second segment, and the third segment in a memory of the receiving device 504, such as in an RRC buffer.

The receiving device 504 may determine which segments have been successfully received based on the segments stored by the receiving device 504. In the illustrated embodiment, the receiving device 504 may determine that the first segment, the second segment, and the third segment had been successfully received. The receiving device 504 may generate a status report 514 to indicate the segments that have been successfully received. In some embodiments, the status report 514 may comprise an RLC status report. The receiving device 504 may transmit the status report 514 to the transmitting device 502.

The transmitting device 502 may receive the status report 514 received from the receiving device 504. The transmitting device 502 may determine which segments of the message have been successfully received by the receiving device 504 based on the status report 514. For example, the transmitting device 502 may determine that the receiving device 504 has successfully received the first segment, the second segment, and the third segment of the message, as shown by the checkmarks over the first segment, the second segment, and the third segment in the message representation 516. Based on the determination of the segment successfully received by the receiving device 504, the transmitting device 502 may determine that the fourth segment needs to be transmitted to the receiving device 504, as shown by the fourth segment in the message representation 516 having diagonal lines. Accordingly, a transmitting device may determine which segments have been successfully received by receiving device and which segments are to be transmitted to complete the transmission of the segmented message.

Option 2: Based on PDCP layer feedback. For example, a transmitting device may determine which segments of a segmented message transmitted to a receiving device have been successfully received by the receiving device based on PDCP layer feedback. Rx side will provide the PDCP status report to the Tx side to indicate which PDCP PDU has been received. For example, the receiving device may generate a PDCP status report that indicates which segments of the segmented message have been successfully received by the receiving device. The receiving device may provide the PDCP status report to the transmitting device. The PDCP status report can be triggered by NW request or when the mobility event is triggered.

FIG. 6 illustrates an example signaling chart 600 illustrating option 2 for determining successful RRC segment reception in accordance with some embodiments. For example, the signaling chart 600 illustrates an approach for determining whether segments of a segmented message have been successfully received by a receiving device based on PDCP layer feedback.

The signaling chart 600 may include a transmitting device 602. The transmitting device 602 may comprise a UE in some instances and may comprise a base station in other instances. The UE may include one or more of the features of the UE 2200 (FIG. 22) . The base station may include one or more the features of the gNB 2300 (FIG. 23) . The transmitting device 602 may be scheduled to transmit a message.

The signaling chart 600 may further include a receiving device 604. The receiving device 604 may comprise a base station in some instances and a UE and some other instances. For example, in instances where the transmitting device 602 is a UE, the receiving device 604 may be a base station. In instances where the transmitting device 602 is a base station, the receiving device 604 may be a UE. The UE may include one or more the features of the UE 2200. The base station may include one or more the features of the gNB 2300. The receiving device 604 may be scheduled to receive the message from the transmitting device 602.

Due to the size of the message, the transmitting device 602 may segment the message into four segments, as shown by message representation 606. The transmitting device 602 may transmit each of the segments of the message in separate RLC PDUs. For example, the transmitting device 602 transmits a first segment of the message in RLC PDU 608, a second segment of the message in RLC PDU 610, and a third segment of the message in RLC PDU 612 in the illustrated embodiment.

The receiving device 604 may receive the RLC PDUs transmitted by the transmitting device 602. The receiving device 604 may identify the segments of the message included in each of the RLC PDUs and may store the received segments. For example, the receiving device 604 may receive the RLC PDU 608, the RLC PDU 610, and the RLC PDU 612 in the illustrated embodiment. The receiving device 604 may identify the first segment within the RLC PDU 608, the second segment within the RLC PDU 610, and the third segment within the RLC PDU 612. The receiving device 604 may store the first segment, the second segment, and the third segment in a memory of the receiving device 604, such as in an RRC buffer.

The receiving device 604 may determine which segments have been successfully received based on the segments stored by the receiving device 604. In the illustrated embodiment, the receiving device 604 may determine that the first segment, the second segment, and the third segment had been successfully received. The receiving device 604 may generate a status report 614 to indicate the segments that have been successfully received. In some embodiments, the status report 614 may comprise a PDCP status report. The receiving device 604 may transmit the status report 614 to the transmitting device 602. In some embodiments, the generation and transmission of the status report 614 may be triggered by an NW request or a triggering of a mobility event.

The transmitting device 602 may receive the status report 614 received from the receiving device 604. The transmitting device 602 may determine which segments of the message have been successfully received by the receiving device 604 based on the status report 614. For example, the transmitting device 602 may determine that the receiving device 604 has successfully received the first segment, the second segment, and the third segment of the message, as shown by the checkmarks over the first segment, the second segment, and the third segment in the message representation 616. Based on the determination of the segment successfully received by the receiving device 604, the transmitting device 602 may determine that the fourth segment needs to be transmitted to the receiving device 604, as shown by the fourth segment in the message representation 616 having diagonal lines. Accordingly, a transmitting device may determine which segments have been successfully received by receiving device and which segments are to be transmitted to complete the transmission of the segmented message.

Option 3: Based on RRC layer feedback. For example, a transmitting device may determine which segments of a segmented message transmitted to a receiving device have been successfully received by the receiving device based on RRC layer feedback. Rx side provides the RRC status report for the SRB#X if the RRC segment is received/stored in the RRC buffer. For example, the receiving device may transmit an RRC status report that indicates which segments of the segmented message have been stored in the RRC buffer of the receiving device. RRC status report can indicate information of the received RRC segments in RRC layer, e.g., the number of received segments, or the received segment index (if the segment-index is introduced in the future) . RRC status report can be carried in the RRC message or in L2 packets (e.g., via the PDCP Control PDU or RLC Control PDU, MAC CE) . For example, the receiving device may transmit the RRC status report in an RRC message or in L2 packets. The RRC layer feedback can be triggered by NW request or when the mobility event is triggered.

FIG. 7 illustrates an example signaling chart 700 illustrated in option 3 for determining successful RRC segment reception in accordance with some embodiments. For example, the signaling chart 700 illustrates an approach for determining whether segments of a segmented message have been successfully received by receiving device based on RRC layer feedback.

The signaling chart 700 may include a transmitting device 702. The transmitting device 702 may comprise a UE in some instances and may comprise a base station in other instances. The UE may include one or more of the features of the UE 2200 (FIG. 22) . The base station may include one or more the features of the gNB 2300 (FIG. 23) . The transmitting device 702 may be scheduled to transmit a message.

The signaling chart 700 may further include a receiving device 704. The receiving device 704 may comprise a base station in some instances and a UE and some other instances. For example, in instances where the transmitting device 702 is a UE, the receiving device 704 may be a base station. In instances where the transmitting device 702 is a base station, the receiving device 704 may be a UE. The UE may include one or more the features of the UE 2200 (FIG. 22) . The base station may include one or more the features of the gNB 2300 (FIG. 23) . The receiving device 704 may be scheduled to receive the message from the transmitting device 702.

Due to the size of the message, the transmitting device 702 may segment the message into four segments, as shown by message representation 706. The transmitting device 702 may transmit each of the segments of the message in separate RLC PDUs. For example, the transmitting device 702 transmits a first segment of the message in RLC PDU 708, a second segment of the message in RLC PDU 710, and a third segment of the message in RLC PDU 712 in the illustrated embodiment.

The receiving device 704 may receive the RLC PDUs transmitted by the transmitting device 702. The receiving device 704 may identify the segments of the message included in each of the RLC PDUs and may store the received segments. For example, the receiving device 704 may receive the RLC PDU 708, the RLC PDU 710, and the RLC PDU 712 in the illustrated embodiment. The receiving device 704 may identify the first segment within the RLC PDU 708, the second segment within the RLC PDU 710, and the third segment within the RLC PDU 712. The receiving device 704 may store the first segment, the second segment, and the third segment in a memory of the receiving device 704, such as in an RRC buffer.

The receiving device 704 may determine which segments have been successfully received based on the segments stored by the receiving device 704. In the illustrated embodiment, the receiving device 704 may determine that the first segment, the second segment, and the third segment had been successfully received. The receiving device 704 may generate a status report 714 to indicate the segments that have been successfully received. The status report 714 may indicate information of the received RRC segments in the RRC layer, such as the number of received segments, index numbers of received segments, an index number of the last received segment, or some combination thereof. In some embodiments, the status report 714 may comprise an RRC segment status report. The receiving device 704 may transmit the status report 714 to the transmitting device 702. The receiving device 704 may transmit the status report 714 in an RRC message or in L2 packets, such as via PDCP control PDU, via RLC control PDU, and/or via MAC CE. In some embodiments, the generation and transmission of the status report 714 may be triggered by an NW request or a triggering of a mobility event.

The transmitting device 702 may receive the status report 714 received from the receiving device 704. The transmitting device 702 may determine which segments of the message have been successfully received by the receiving device 704 based on the status report 714. For example, the transmitting device 702 may determine that the receiving device 704 has successfully received the first segment, the second segment, and the third segment of the message, as shown by the checkmarks over the first segment, the second segment, and the third segment in the message representation 716. Based on the determination of the segment successfully received by the receiving device 704, the transmitting device 702 may determine that the fourth segment needs to be transmitted to the receiving device 704, as shown by the fourth segment in the message representation 716 having diagonal lines. Accordingly, a transmitting device may determine which segments have been successfully received by receiving device and which segments are to be transmitted to complete the transmission of the segmented message.

Option 4: Based on timer. For example, a transmitting device may determine which segments of a segment message transmitted receiving device have been successfully received by the receiving device based on a timer. Tx side starts the timer when the mobility event is performed/finished (e.g., HO, bearer type change) ; if no segment status report is received from the Rx side before the timer expiry, Tx side assumes all the transmitted segments are received successfully or unsuccessfully in the Rx side. For example, the transmitting device may initiate a countdown of a timer when a mobility event (such as an HO operation or a bearer type change) is performed or finished. If the transmitting device fails to receive a segment status report (such as the RLC status report, the PDCP status report, and/or the RRC segment status report) , the transmitting device may determine that all of the transmitted segments have been successfully received by the receiving device in some embodiments or that none of the transmitted segments have been successfully received by the receiving device in other embodiments.

Option 3: The potential format of the RRC layer feedback

As stated in option 3 of the approaches for determining which of the segments have been successfully received by a receiving device as described above, a transmitting device may receive an RRC status report. The RRC status report may have different formats in different embodiments. Formats 1 through 4 described below are some example formats of an RRC status report that can be utilized in determining which segments have since been successfully received in accordance with option 3 for determining which the segments have been successfully received.

Format 1: New RRC message. The message support both in UL and DL direction. FIG. 8 illustrates an example RRC message 800 in accordance with some embodiments. The RRC message 800 may be an example of a first format for an RRC message that can be utilized for determining which of the segments have been successfully received by a receiving device.

The RRC message 800 may comprise an RRCSegmentTransferInfo message 802. The RRCSegmentTransferInfo message 802 may include an rrcSegmentTranferInfo element 804, which may provide information elements indicating information related to which segments are successfully received by receiving device. The rrcSegmentTranferInfo element 804 may include a noofRevSegment information element 806. The noofRevSegment information element 806 may indicate a number of segments successfully received by the receiving device.

For example, the receiving device may determine which segments have been successfully received from a transmitting device and generate the RRC message 800. The RRC message 800 may include the noofRevSegment information element 806 that indicates the number of segments that the receiving device determines have been successfully received. In other embodiments, the indication of the number of segments successfully received can be replaced by a bitmap that indicates the successfully received segments or a list of the segment IDs corresponding to the successfully received segments.

Format 2: New PDCP Control PDU (PDU Type = RRC Segment Feedback of the SRB#X) . FIG. 9 illustrates an example PDCP control PDU 900 in accordance with some embodiments. The PDCP control PDU 900 may be an example of a second format for an RRC message that can be utilized for determining which of the segments have been successfully received by a receiving device.

The PDCP control PDU 900 may include a PDU type indication 902. The PDU type indication 902 may indicate a type of the PDCP control PDU 900. For the RRC layer feedback, the PDU type indication 902 may indicate that the PDCP control PDU 900 is for RRC segment feedback.

The PDCP control PDU 900 may further include a received segments indication 904. The received segments indication 904 may indicate a number of segments of the segmented message that were successfully received. In other embodiments, the indication of the number of segments successfully received can be replaced by a bitmap that indicates the successfully received segments or a list of the segment IDs corresponding to the successfully received segments.

Format 3: New RLC Control PDU (CPT = RRC Segment Feedback of the SRB#X) . FIG. 10 illustrates an example RLC control PDU 1000 in accordance with some embodiments. The RLC control PDU 1000 may be an example of a third format for an RRC message that can be utilized for determining which of the segments have been successfully received by a receiving device.

The RLC control PDU 1000 may include a control package type (CPT) indication 1002. The CPT indication 1002 may indicate a type of the RLC control PDU 1000. For the RRC layer feedback, the CPT indication 1002 may indicate that the RLC control PDU 1000 is for RC segment feedback.

The RLC control PDU 1000 may further include a received segments indication 1004. The received segments indication 1004 may indicate a number of segments of the segmented message that were successfully received. In other embodiments, the indication of the number of segments successfully received can be replaced by a bitmap that indicates the successfully received segments or a list of the segment IDs corresponding to the successfully received segments.

Format 4: New MAC CE (new LCID/eLCID is specified for the RRC Segment Feedback) . FIG. 11 illustrates an example MAC CE 1100 in accordance with some embodiments. The MAC CE 1100 may be an example of fourth format for RRC message that can be utilized for determining which of the segments have been successfully received by a receiving device.

The MAC CE 1100 may correspond to a logical channel identifier (LCID) or an extended logical channel identifier (eLCID) . The LCID or the eLCID may indicate that the MAC CE 1100 is to be utilized for RRC segment feedback.

The MAC CE 1100 may include a received segments indication 1102. The received segments indication 1102 may indicate a number of segments of the segmented message that were successfully received. In other embodiments, the indication of the number of segments successfully received can be replaced by a bitmap that indicates the successfully received segments or a list of the segment IDs corresponding to the successfully received segments.

NOTE: In each format, the number of the received RRC segments can be replaced with the following info: Opt1) A bitmap to indicate the received segment; Opt2) the list of the received RRC segment ID.

Any of the four formats for the RRC layer feedback may be utilized in the procedure for determining the successfully received segments of a segmented message. For example, the status report 714 (FIG. 7) may utilize any of the four formats for the RRC layer feedback. In some embodiments, a UE or a base station may be configured with the format for the RRC layer feedback to be utilized by the status report 714.

Example 1: Handover with UL RRC segment continuity

FIG. 12 illustrates an example signaling chart 1200 showing HO with UL RRC segment continuity in accordance with some embodiments. For example, the signaling chart 1200 illustrates signals that may be exchanged between a UE and one or more base stations when a HO is performed while segments of a segmented message being transmitted by a UE to the one or more base stations.

The signaling chart 1200 may include a UE 1202. The UE 1202 may include one or more of the features of the UE 2200 (FIG. 22) . The UE 1202 may be scheduled to transmit a message.

The signaling chart 1200 may further include a source base station 1204. The source base station 1204 may include one or more of the features of the gNB 2300 (FIG. 23) . The UE 1202 may have a connection established with the source base station 1204 at the initiation of the signaling illustrated in the signaling chart 1200.

The signaling chart 1200 may further include a target base station 1206. The target base station 1206 may include one or more of the features of the gNB 2300 (FIG. 23) . The HO operation illustrated in the signaling chart 1200 may be for transitioning the connection of the UE 1202 with the source base station 1204 to the target base station 1206. Accordingly, the UE 1202 may have a connection established with the target base station 1206 upon completion of the HO operation, while the connection between the UE 1202 and the source base station 1204 is terminated.

Precondition: The source gNB configures UE for the SRB4 with UL segment mode. For example, the source base station 1204 may configure the UE 1202 for SRB4 with UL segment mode prior to the signaling illustrated in the signaling chart 1200. Accordingly, the UE 1202 may segment messages that are larger than a maximum size of a PDCP SDU.

The UE 1202 may have a message to be transmitted to the NW via the source base station 1204. In some embodiments, the message may comprise an RRC message. The message may be larger than the maximum size of the PDCP SDU for the system. Due to the message being larger than the maximum size of the PDCP SDU, the UE 1202 may segment the message into four separate segments to be transmitted to the source base station 1204.

Phase 1: Before HO. For one SRB4 message, the UE divides it into 4 RRC segments for transmission, and 3 segments have been transmitted to NW side successfully. For example, the UE 1202 may transmit to the source base station 1204 the segments of the message via RLC PDUs. For example, the UE 1202 may transmit a first segment via a first RLC PDU 1208, a second segment via a second RLC PDU 1210, and a third segment via a third RLC PDU 1212 in the illustrated embodiment. The message representation 1216 illustrates that the first three segments have been transmitted based on the checkmarks on the first three segments of the segmented message.

The source base station 1204 may receive the RLC PDUs from the UE 1202. For example, source base station 1204 may receive the first RLC PDU 1208, the second RLC PDU 1210, and the third RLC PDU 1212 in the illustrated embodiment. The source base station 1204 may identify the segments of the segmented message received in the RLC PDUs. In the illustrated embodiment, the source base station 1204 may identify the first segment received in the first RLC PDU 1208, the second segment received in the second RLC PDU 1210, and the third segment received in the third RLC PDU 1212. The source base station 1204 may store the segments, such as in a RRC buffer. The received segments representation 1218 illustrates that the first three segments of the message have been received by the source base station 1204 by showing the three segments.

The source base station 1204 may generate acknowledgment message 1214 that indicates the segments successfully received. In some embodiments, the acknowledgment message 1214 may comprise an RLC acknowledgment message. The source base station 1204 may determine that the segments received from the UE 1202 and stored by the source base station 1204 successfully received. In the illustrated embodiment, the acknowledgment message 1214 may indicate that the first segment, the second segment, the third segment was successfully received. While the acknowledgment message 1214 is illustrated a single message in the illustrated embodiment, it should be understood that the acknowledgment message 1214 may comprise multiple messages.

Phase 2: HO trigger. When NW triggers the HO command with the SRB4 segment continuity configuration, the source gNB can keep the segment#1#2#3 in the buffer. In case that the target and source gNB are different, the source gNB forwards the segment#1#2#3 of the SRB4 to the target gNB, and target gNB stores them in the RRC receiving buffer.

For example, HO procedure may be initiated after the first three segments of the segmented message have been transmitted by the UE 1202, but prior to the fourth segment of the segmented message being transmitted by the UE 1202. The HO procedure may include a HO process 1220 performed between the source base station 1204 and the target base station 1206. The HO process 1220 may prepare the target base station 1206 for establishment of the connection with the UE 1202. The HO procedure may further include the source base station 1204 transmitting an HO command 1222 to the UE 1202 that indicates the UE 1202 is to establish a connection with the target base station 1206. The HO procedure may further include the UE 1202 transmitting an HO complete message 1224 to the target base station 1206 to establish the connection with the target base station 1206 and complete the HO. The source base station 1204 may store the first three segments of the segmented message received prior to the HO procedure during the HO procedure.

Phase 3: HO execution. When UE receives the HO command with the SRB4 segment continuity configuration, UE determines the segment#1/2/3 are successfully received. UE only transmits the 4th SRB4 RRC segment after the HO complete message in target cell. NOTE: UE can start the RRC Segment#4 transmission after receiving the RRC segment status report from NW side, to determine the segment#1/2/3 are successfully received. When NW receives the 4th segment, NW will perform the SRB4 RRC message reassembly and get the whole RRC message.

After the HO procedure has been completed, the source base station 1204 may transmit a PDCP status report or RRC status report 1226 to the UE 1202. The PDCP status report or the RRC status report 1226 may indicate the segments of the segmented message stored by the source base station 1204 after completion of the HO. In some embodiments, the PDCP status report or the RRC status report 1226 may include one or more of the features of the PDCP control PDU 900 (FIG. 9) . In other embodiments, the PDCP status report or the RRC status report 1226 may include one or more of the features of the RRC message 800 (FIG. 8) .

The UE 1202 may receive the PDCP status report or the RRC status report 1226. Based on this PDCP status report or the RRC status report 1226, the UE 1202 may determine the segments that the source base station 1204 has stored after completion of the HO. For example, the UE 1202 may determine that the source base station 1204 has the first segment, the second segment, and the third segment stored after completion of the HO in the illustrated embodiment. The UE 1202 may determine which segments are to be transmitted after the completion of the HO based on the segments stored by the source base station 1204 after completion of the HO. For example, the UE 1202 may determine that the fourth segment of the segmented message is to be transmitted after completion of the HO, and that the first three segments of the segmented message are not to be transmitted after completion of the HO in the illustrated embodiment based on the determination that the source base station 1204 has the first three segments stored after completion of the HO. A measurement report 1228 indicates the determination by the UE 1202 that the fourth segment is to be transmitted after completion of the HO by diagonal lines being shown in the fourth segment.

The source base station 1204 may provide the stored segments to the target base station 1206. For example, the source base station 1204 may provide the first three segments of the segmented message that were received and stored by the source base station 1204 prior to the HO to the target base station 1206. The source base station 1204 may transmit a data message 1230 that includes the first three segments to the target base station 1206.

The target base station 1206 may receive the first three segments from the source base station 1204. The target base station 1206 may store the first three segments received from the source base station 1204 to be utilized for reassembling the segmented message.

The UE 1202 may transmit the segments of the segmented message determined to be transmitted after the HO to the target base station 1206. For example, the UE 1202 may transmit the fourth segment of the segmented message to the target base station 1206. The UE 1202 may transmit the segments via one or more RLC PDUs. In the illustrated embodiment, the UE 1202 may transmit the fourth segment via a fourth RLC PDU 1232 to the target base station 1206.

The target base station 1206 may receive the remaining segments of the segmented message transmitted by the UE 1202 after completion of the HO. For example, the target base station 1206 may receive the fourth RLC PDU 1232 and identify the fourth segment. The target base station 1206 may store the fourth segment, such as by storing the fourth segment in an RRC buffer of the target base station 1206. The target base station 1206 may store the segments received from the UE 1202 after completion of the HO in order with the segments received from the source base station 1204. For example, the target base station 1206 may store the first segment, the second segment, the third segment, and the fourth segment in order, as shown by buffer representation 1234.

The target base station 1206 may determine when all of the segments of the segmented message have been received. In some embodiments, the target base station 1206 may determine when all the segments have been received based on segment IDs of the received segments. Once the target base station 1206 has determined that all of the segments of the segmented message have been received, the target base station 1206 may reassemble the segmented message from the segments as shown by reassembly 1236. For example, the target base station 1206 may reassemble the segmented message from the first segment, the second segment, the third segment, and the fourth segment received in the illustrated embodiment.

As can be seen by the signaling chart 1200, the UE 1202 transmits each of the segments of the segmented message to the NW (via the source base station 1204 or the target base station 1206) only once. This can improve on the performance of legacy approaches that would transmit segments of the segmented message multiple times based on a purge of segments due to an HO in the legacy approaches. Accordingly, the illustrated approach can reduce overhead signaling for segmented messages transmitted during an HO.

Example 2: The path switching with DL RRC segment continuity

FIG. 13 illustrates example signaling chart 1300 showing path switching with DL RRC segment continuity in accordance with some embodiments. For example, the signaling chart 1300 illustrates a plurality of transmissions and operations that may occur when path switching is performed during transmission of segments of a segmented message.

The signaling chart 1300 may include a UE 1302. The UE 1302 may include one or more of the features of the UE 2200 (FIG. 22) . The UE 1302 may be scheduled to transmit a message.

The signaling chart 1300 may further include a master base station 1304. The master base station 1304 may include one or more of the features of the gNB 2300 (FIG. 23) . The UE 1302 may have a connection established with the master base station 1304 at the initiation of the signaling illustrated in the signaling chart 1300.

The signaling chart 1300 may further include a secondary base station 1306. The secondary base station 1306 may include one or more of the features of the gNB 2300. The path switching illustrated in the signaling chart 1300 may be for changing the path for transmissions to the UE 1302 from the master base station 1304 to the secondary base station 1306. Accordingly, the UE 1302 may transmit transmissions via the secondary base station 1306 upon completion of the path switching.

Example. The NW configures UE for the SRB#X with DL segment mode and the transmission path is master gNB (MgNB) . For example, the master base station 1304 may configure the UE 1302 for SRB4 with DL segment mode prior to the signaling illustrated in the signaling chart 1200. Accordingly, the base stations may segment messages that are larger than a maximum size of a PDCP SDU.

For the SRB#X message, the NW divides it into 4 RRC segments for Tx, and 3 segments have been transmitted to UE side. For example, the NW may have a message to be transmitted to the UE 1302. In some embodiments, the message may comprise an RRC message. The message may be larger than the maximum size of the PDCP SDU for the system. Due to the message being larger than the maximum size of the PDCP SDU, the NW may segment the message into four separate segments to be transmitted to the UE 1302.

The signaling of the signaling chart 1300 may initiate with the master base station 1304 transmitting segments of the segmented message to the UE 1302. For example, the master base station 1304 may transmit to the UE 1302 the segments of the message via RLC PDUs. For example, the master base station 1304 may transmit a first segment via a first RLC PDU 1308, a second segment via a second RLC PDU 1310, and a third segment via a third RLC PDU 1312 in the illustrated embodiment. The message representation 1314 illustrates that the first three segments have been transmitted based on the checkmarks on the first three segments of the segmented message.

The UE 1302 may receive the RLC PDUs from the master base station 1304. For example, UE 1302 may receive the first RLC PDU 1308, the second RLC PDU 1310, and the third RLC PDU 1312 in the illustrated embodiment. The UE 1302 may identify the segments of the segmented message received in the RLC PDUs. In the illustrated embodiment, the UE 1302 may identify the first segment received in the first RLC PDU 1308, the second segment received in the second RLC PDU 1310, and the third segment received in the third RLC PDU 1312. The UE 1302 may store the segments, such as in a RRC buffer. The received segments representation 1316 illustrates that the first three segments of the message have been received by the UE 1302 by showing the three segments.

When NW triggers the SRB#X transmission path from MCG to SCG with the SRB4 segment continuity configuration, MgNB forwards all the segments to the secondary gNB (SgNB) , UE keeps all the RRC segments in the RRC buffer. For example, the NW may trigger a path switch for the UE 1302 from the master base station 1304 to the secondary base station 1306. The path switch may include a coordination operation 1318 performed between the master base station 1304 and the secondary base station 1306. The coordination operation 1318 may prepare the secondary base station 1306 for the path switch. The path switch may further include the master base station 1304 transmitting an RRC reconfiguration message 1320 the UE 1302 to indicate a path switch from the master base station 1304 to the secondary base station 1306. The path switch may further include the UE 1302 transmitting an RRC reconfiguration complete message 1322 to the master base station indicating that the UE 1302 has successfully completed the path switch.

The UE 1302 may continue to store the segments received prior to the path switch during the path switch operation. For example, the UE 1302 may store the first segment, the second segment, and the third segment during the path switch operation. Accordingly, the UE 1302 may still have the segments stored after completion of the path switch operation. For example, the UE 1302 may still have the segments stored in an RRC buffer of the UE 1302 after completion of the path switch operation.

Based on the completion of the path switch, the master base station 1304 may transmit the segmented message to the secondary base station 1306 for completion of transmitting the segmented message to the UE 1302. For example, the master base station 1304 may transmit the segmented message to the secondary base station 1306 via a data forwarding message 1324 in the illustrated embodiment. The data forwarding message 1324 may include all the segments of the segmented message. For example, the data forwarding message 1324 includes the first segment, the second segment, the third segment, and the fourth segment in the illustrated embodiment. In some other embodiments, the data forwarding message 1324 may include a portion of the segments of the segmented message, such as a portion of the segments for which the master base station 1304 did not receive positive acknowledgment of reception from the UE 1302.

UE provides the PDCP status report to SgNB which indicates the segment#1#2#3 have been received. For example, the UE 1302 may generate a PDCP status report or RRC status report 1326. In some embodiments, the PDCP status report or RRC status report 1326 may include one or more the features of the PDCP control PDU 900 (FIG. 9) . In other embodiments, the PDCP status report or RRC status report 1326 may include one or more the features of the RRC message 800 (FIG. 8) . The PDCP status report or RRC status report 1326 may indicate which segments of the segmented message have been successfully received by the UE 1302. For example, the PDCP status report or RRC status report 1326 may indicate that the first segment, the second segment, and a third segment of the segmented message have been successful received by the UE 1302 in the illustrated embodiment. The UE 1302 may transmit the PDCP status report or RRC status report 1326 to the secondary base station 1306.

The secondary base station 1306 may receive the PDCP status report or RRC status report 1326. The secondary base station 1306 may determine which segments of the segmented message have been successful received by the UE 1302. For example, the secondary base station 1306 may determine that the first segment, the second segment, and the third segment have been successful received by the UE 1302. Based on the segments successful received by the UE 1302, the secondary base station 1306, may determine which segments to transmit to the UE 1302 after completion of the path switch. For example, the secondary base station 1306 may determine that the fourth segment is to be transmitted after the path switch in the first segment, the second segment, and the third segment are not to be transmitted after the path switch based on the secondary base station 1306 determining that the UE 1302 has successful received the first segment, the second segment, and the third segment. The message representation 1328 indicates that the secondary base station 1306 has determined that the fourth segment is to be transmitted after the path switch by the diagonal lines in the fourth segment.

The SgNB transmits the fourth SRB4 RRC segment only via the SgNB to UE. For example, the secondary base station 1306 may transmit the remaining segments that have not been successful received by the UE 1302 to the UE 1302. The secondary base station 1306 may transmit the remaining segments via one or more RLC PDUs. For example, the secondary base station 1306 may transmit the fourth segment of the segmented message in a fourth RLC PDU 1330 in the illustrated embodiment.

When UE receives the fourth segment, UE will assemble all the segments. For example, the UE 1302 may determine whether all segments of the segmented message have been received. Based on the UE 1302 determining that all of the segments of the segmented message have been received, the UE 1302 may reassemble the segmented message from the segments. For example, the UE 1302 may receive the fourth RLC PDU 1330. The UE 1302 may identify the fourth segment in the RLC PDU 1330 and store the fourth segment in order with the other segments received for the segmented message. For example, the UE 1302 may store the first segment, the second segment, the third segment, and the fourth segment in order, as shown by the buffer representation 1332. The UE 1302 may determine that all of the segments of the segmented message have been received based on the first segment, the second segment, and the third segment being stored by the UE 1302. In some embodiments, the UE 1302 may determine that all the segments of the segmented message have been received based on segment IDs for the received segments.

Once the UE 1302 has received all of the segments of the segmented message, the UE 1302 may reassemble the segmented message from the received segments. For example, the UE 1302 may reassemble the first segment, the second segment, the third segment, and the fourth segment to produce segmented message, as illustrated by reassembly 1334.

As can be seen by the signaling chart 1300, the NW (via the master base station 1304 or the secondary base station 1306) transmits each of the segments of the segmented message to the UE 1302 only once. This can improve on the performance of legacy approaches that would transmit segments of the segmented message multiple times based on a purge of segments due to a path switch in the legacy approaches. Accordingly, the illustrated approach can reduce overhead signaling for segmented messages transmitted during a path switch.

Example 3: RRC segment status report based on NW RRC request

Example 1: For UL RRC segment continuity during HO, UE can request the NW the SRB#4 segment reception status in HOComplete message, and NW provides the RRC feedback based on the request. FIG. 14 illustrates an example signaling chart 1400 with RRC segment status reporting in accordance with some embodiments. For example, the signaling chart 1400 illustrates a plurality of transmissions and/or operations that may be performed in relation to RRC segment status reporting for example 1.

The signaling chart 1400 may include a UE 1402. The UE 1402 may include one or more of the features of the UE 2200 (FIG. 22) . The UE 1402 may be scheduled to transmit a message.

The signaling chart 1400 may further include a network element 1404, which may be a base station, or may be connected to the UE 1402 via a base station where the base station may transmit and/or receive the transmissions for the network element 1404. The network element 1404 may include one or more of the features of the gNB 2300 (FIG. 23) . The UE 1402 may have a connection established with the network element 1404 at the initiation of the signaling illustrated in the signaling chart 1400.

The network element 1404 may configure the UE 1402 for SRB4 with UL segment mode prior to the signaling illustrated in the signaling chart 1400. Accordingly, the UE 1402 may segment messages that are larger than a maximum size of a PDCP SDU.

The UE 1402 may have a message to be transmitted to the NW via the network element 1404. In some embodiments, the message may comprise an RRC message. The message may be larger than the maximum size of the PDCP SDU for the system. Due to the message being larger than the maximum size of the PDCP SDU, the UE 1402 may segment the message into four separate segments to be transmitted to the network element 1404, as shown by message representation 1406.

The UE 1402 may transmit to the network element 1404 the segments of the message via RLC PDUs. For example, the UE 1402 may transmit a first segment via a first RLC PDU 1408, a second segment via a second RLC PDU 1410, and a third segment via a third RLC PDU 1412 in the illustrated embodiment.

The network element 1404 may receive the RLC PDUs from the UE 1402. For example, network element 1404 may receive the first RLC PDU 1408, the second RLC PDU 1410, and the third RLC PDU 1412 in the illustrated embodiment. The network element 1404 may identify the segments of the segmented message received in the RLC PDUs. In the illustrated embodiment, the network element 1404 may identify the first segment received in the first RLC PDU 1408 and the second segment received in the second RLC PDU 1410 (whereas the network element 1404 may have failed to identify and/or store the third segment in the illustrated embodiment) . The network element 1404 may store the segments, such as in a RRC buffer. The received segments representation 1414 illustrates that the first two segments of the message have been received by the network element 1404 by showing the two segments.

An HO procedure may be initiated after the first two segments of the segmented message have successfully received by the network element 1404, but prior to the third and fourth segments of the segmented message being successfully received by the network element 1404. The HO procedure may include the network element 1404 transmitting an HO command 1416 to the UE 1402 that indicates the UE 1402 is to perform an HO operation. The HO procedure may further include the UE 1402 transmitting an HO complete message 1418 to the network element 1404 to complete the HO. The network element 1404 may store the first two segments of the segmented message received prior to the HO procedure during the HO procedure.

The network element 1404 may generate in RRC segment status 1420. The RRC segment status 1420 may indicate the segments successfully received by the network element 1404 prior to the HO. For example, the RRC segment status 1420 may indicate that the first segment and the second segment have been successfully received by the network element 1404 in the illustrated embodiment. The network element 1404 may transmit the RRC segment status 1420 the UE 1402.

The UE 1402 may receive the RRC segment status 1420. Based on the RRC segment status 1420, the UE 1402 may determine which segments are to be transmitted after the completion of the HO. For example, the UE 1402 may determine that the RRC segment status 1420 indicates that the first segment and the second segment have been successfully received by the network element 1404. Accordingly, the UE 1402 may determine that the third segment and the fourth segment are to be transmitted to the network element 1404 after completion of the HO, as indicated by a message representation 1422 that shows the first segment and the second segment with checkmarks to indicate that the segments have been successfully received by the network element and the third segment and fourth segment with diagonal lines to indicate the segments to be transmitted after completion of the HO.

The UE 1402 may transmit the segments of the segmented message determined to be transmitted after the HO to the network element 1404. For example, the UE 1402 may transmit the third segment and the fourth segment of the segmented message to the network element 1404. The UE 1402 may transmit the segments via one or more RLC PDUs. In the illustrated embodiment, the UE 1402 may transmit the third segment via the third RLC PDU 1424 and the fourth segment via a fourth RLC PDU 1426 to the network element 1404.

The network element 1404 may receive the remaining segments of the segmented message transmitted by the UE 1402 after completion of the HO. For example, the network element 1404 may receive the third RLC PDU 1424 and identify the third segment. The network element 1404 may further receive the fourth RLC PDU 1426 and identify the fourth segment. The network element 1404 may store the third segment and the fourth segment, such as by storing the third segment and the fourth segment in an RRC buffer of the network element 1404. The network element 1404 may store the segments received from the UE 1402 after completion of the HO in order. For example, the network element 1404 may store the first segment, the second segment, the third segment, and the fourth segment in order.

The network element 1404 may determine when all of the segments of the segmented message have been received. In some embodiments, the network element 1404 may determine when all the segments have been received based on segment IDs of the received segments. Once the network element 1404 has determined that all of the segments of the segmented message have been received, the network element 1404 may reassemble the segmented message from the segments. For example, the network element 1404 may reassemble the segmented message from the first segment, the second segment, the third segment, and the fourth segment received in the illustrated embodiment.

As can be seen by the signaling chart 1400, the UE 1402 does not retransmit segments to the NW (via the network element 1404) that the NW has already successfully received. This can improve on the performance of legacy approaches that would transmit segments of the segmented message multiple times based on a purge of segments due to an HO in the legacy approaches. Accordingly, the illustrated approach can reduce overhead signaling for segmented messages transmitted during an HO.

Example 2: For UL RRC segment continuity during HO, UE can request the NW the SRB#4 segment reception status via a new RRC message, and NW provides the RRC feedback based on the request. FIG. 15 illustrates another example signaling chart 1500 with RRC segment status reporting in accordance with some embodiments. For example, the signaling chart 1500 illustrates a plurality of transmissions and/or operations that may be performed in relation to RRC segment status reporting for example 2.

The signaling chart 1500 may include a UE 1502. The UE 1502 may include one or more of the features of the UE 2200 (FIG. 22) . The UE 1502 may be scheduled to transmit a message.

The signaling chart 1500 may further include a network element 1504, which may be a base station, or may be connected to the UE 1502 via a base station where the base station may transmit and/or receive the transmissions for the network element 1504. The network element 1504 may include one or more of the features of the gNB 2300 (FIG. 23) . The UE 1502 may have a connection established with the network element 1504 at the initiation of the signaling illustrated in the signaling chart 1500.

The network element 1504 may configure the UE 1502 for SRB4 with UL segment mode prior to the signaling illustrated in the signaling chart 1500. Accordingly, the UE 1502 may segment messages that are larger than a maximum size of a PDCP SDU.

The UE 1502 may have a message to be transmitted to the NW via the network element 1504. In some embodiments, the message may comprise an RRC message. The message may be larger than the maximum size of the PDCP SDU for the system. Due to the message being larger than the maximum size of the PDCP SDU, the UE 1502 may segment the message into four separate segments to be transmitted to the network element 1504, as shown by message representation 1506.

The UE 1502 may transmit to the network element 1504 the segments of the message via RLC PDUs. For example, the UE 1502 may transmit a first segment via a first RLC PDU 1508, a second segment via a second RLC PDU 1510, a third segment via a third RLC PDU 1512, and a fourth segment via a fourth RLC PDU 1514 in the illustrated embodiment.

The network element 1504 may receive the RLC PDUs from the UE 1502. For example, network element 1504 may receive the first RLC PDU 1508, the second RLC PDU 1510, the third RLC PDU 1512, and the fourth RLC PDU 1514 in the illustrated embodiment. The network element 1504 may identify the segments of the segmented message received in the RLC PDUs. In the illustrated embodiment, the network element 1504 may identify the first segment received in the first RLC PDU 1508 and the second segment received in the second RLC PDU 1510 (whereas the network element 1504 may have failed to identify and/or store the third segment and the fourth segment in the illustrated embodiment) . The network element 1504 may store the segments, such as in a RRC buffer. The received segments representation 1516 illustrates that the first two segments of the message have been received by the network element 1504 by showing the two segments.

For example, an HO procedure may be initiated after the first two segments of the segmented message have successfully received by the network element 1504, but prior to the third and fourth segments of the segmented message being successfully received by the network element 1504. The HO procedure may include the network element 1504 transmitting an HO command 1518 to the UE 1502 that indicates the UE 1502 is to perform an HO operation. The HO procedure may further include the UE 1502 transmitting an HO complete message 1520 to the network element 1504 to complete the HO. The network element 1504 may store the first two segments of the segmented message received prior to the HO procedure during the HO procedure.

After completing the HO, the UE 1502 may query the network element 1504 status of the segments successfully received by the network element 1504. For example, the UE 1502 may transmit a segment status enquiry 1522 to the network element 1504 requesting that the network element 1504 provide a segment status.

The network element 1504 may identify the segment status enquiry 1522 received from the UE 1502. The network element 1504 may generate an RRC segment status 1524 based on receiving the segment status enquiry 1522. The RRC segment status 1524 may indicate the segments that were successfully received by the network element 1504. For example, the RRC segment status 1524 may indicate that the first segment and the second segment were successfully received by the network element 1504 in the illustrated embodiment. The network element 1504 may transmit the RRC segment status 1524 to the UE 1502.

The UE 1502 may identify the received RRC segment status 1524. Based on the RRC segment status 1524, the UE 1502 may determine which segments are to be transmitted after the completion of the HO. For example, the UE 1502 may determine that the RRC segment status 1524 indicates that the first segment and the second segment have been successfully received by the network element 1504. Accordingly, the UE 1502 may determine that the third segment and the fourth segment are to be transmitted to the network element 1504 after completion of the HO, as indicated by a message representation 1526 that shows the first segment and the second segment with checkmarks to indicate that the segments have been successfully received by the network element and the third segment and fourth segment with diagonal lines to indicate the segments to be transmitted after completion of the HO.

The UE 1502 may transmit the segments of the segmented message determined to be transmitted after the HO to the network element 1504. For example, the UE 1502 may transmit the third segment and the fourth segment of the segmented message to the network element 1504. The UE 1502 may transmit the segments via one or more RLC PDUs. In the illustrated embodiment, the UE 1502 may transmit the third segment via a third RLC PDU 1528 and the fourth segment via a fourth RLC PDU 1530 to the network element 1504.

The network element 1504 may receive the remaining segments of the segmented message transmitted by the UE 1502 after completion of the HO. For example, the network element 1504 may receive the third RLC PDU 1528 and identify the third segment. The network element 1504 may further receive the fourth RLC PDU 1530 and identify the fourth segment. The network element 1504 may store the third segment and the fourth segment, such as by storing the third segment and the fourth segment in an RRC buffer of the network element 1504. The network element 1504 may store the segments received from the UE 1502 after completion of the HO in order. For example, the network element 1504 may store the first segment, the second segment, the third segment, and the fourth segment in order.

The network element 1504 may determine when all of the segments of the segmented message have been received. In some embodiments, the network element 1504 may determine when all the segments have been received based on segment IDs of the received segments. Once the network element 1504 has determined that all of the segments of the segmented message have been received, the network element 1504 may reassemble the segmented message from the segments. For example, the network element 1504 may reassemble the segmented message from the first segment, the second segment, the third segment, and the fourth segment received in the illustrated embodiment.

As can be seen by the signaling chart 1500, the UE 1502 does not retransmit segments to the NW (via the network element 1504) that the NW has already successfully received. This can improve on the performance of legacy approaches that would transmit segments of the segmented message multiple times based on a purge of segments due to an HO in the legacy approaches. Accordingly, the illustrated approach can reduce overhead signaling for segmented messages transmitted during an HO.

Example 4: Timer based RRC segment status feedback

Example 1: For UL RRC segment continuity during HO, after UE send out the request, UE does not receive RRC segment reception status report within T, UE assumes all segments are received in NW side. FIG. 16 illustrates an example signaling chart 1600 with timer based RRC segment status feedback in accordance with some embodiments. For example, the signaling chart 1600 illustrates a plurality of transmissions and/or operations that may be performed in relation to timer based RRC segment status reporting for example 1.

The signaling chart 1600 may include a UE 1602. The UE 1602 may include one or more of the features of the UE 2200 (FIG. 22) . The UE 1602 may be scheduled to transmit a message.

The signaling chart 1600 may further include a network element 1604, which may be a base station or may be connected to the UE 1602 via a base station. The network element 1604 may include one or more of the features of the gNB 2300 (FIG. 23) . The UE 1602 may have a connection established with the network element 1604 at the initiation of the signaling illustrated in the signaling chart 1600.

The network element 1604 may configure the UE 1602 for SRB4 with UL segment mode prior to the signaling illustrated in the signaling chart 1600. Accordingly, the UE 1602 may segment messages that are larger than a maximum size of a PDCP SDU.

The UE 1602 may have a message to be transmitted to the NW via the network element 1604. In some embodiments, the message may comprise an RRC message. The message may be larger than the maximum size of the PDCP SDU for the system. Due to the message being larger than the maximum size of the PDCP SDU, the UE 1602 may segment the message into four separate segments to be transmitted to the network element 1604, as shown by message representation 1606.

For example, the UE 1602 may transmit to the network element 1604 the segments of the message via RLC PDUs. For example, the UE 1602 may transmit a first segment via a first RLC PDU 1608, a second segment via a second RLC PDU 1610, a third segment via a third RLC PDU 1612, and a fourth segment via a fourth RLC PDU 1614 in the illustrated embodiment.

The network element 1604 may receive the RLC PDUs from the UE 1602. For example, network element 1604 may receive the first RLC PDU 1608, the second RLC PDU 1610, the third RLC PDU 1612, and the fourth RLC PDU 1614 in the illustrated embodiment. The network element 1604 may identify the segments of the segmented message received in the RLC PDUs. In the illustrated embodiment, the network element 1604 may identify the first segment received in the first RLC PDU 1608, the second segment received in the second RLC PDU 1610, the third segment received in the third RLC PDU 1612, and the fourth segment received in the fourth RLC PDU 1614. The network element 1604 may store the segments, such as in a RRC buffer. The received segments representation 1616 illustrates that all four segments of the message have been received by the network element 1604 by showing the checkmarks on the four segments.

An HO procedure may be initiated after the four segments of the segmented message have successfully received by the network element 1604. The HO procedure may include the network element 1604 transmitting an HO command 1618 to the UE 1602 that indicates the UE 1602 is to perform an HO operation. The HO procedure may further include the UE 1602 transmitting an HO complete message 1620 to the network element 1604 to complete the HO. The network element 1604 may store the four segments of the segmented message received prior to the HO procedure during the HO procedure.

The UE 1602 may initiate a countdown of a timer 1622 based on the HO. For example, the UE 1602 may initiate countdown of the timer 1622 at the beginning of the HO procedure, at the end of the HO procedure, or some other time during the HO procedure. In the illustrated embodiment, the UE 1602 initiates the countdown of the timer 1622 at the completion of the HO. The UE 1602 may determine whether the segments have been received based on whether an RRC segment reception status is received during the countdown of the timer 1622. In the illustrated embodiment, the UE 1602 may be configured to determine that the segments have been successfully received based on the UE 1602 not receiving an RRC segment reception status prior to expiration of the timer 1622. Accordingly, the UE 1602 may determine that one or more of the segments have not been successfully received by the network element 1604 based on the UE 1602 receiving an RRC segment reception status prior to expiration of the timer 1622. In the illustrated instance, the UE 1602 does not receive an RRC segment reception status prior to the expiration of the timer 1622. Accordingly, the UE 1602 may determine that all of these segments transmitted to the network element 1604 have been successfully received, as indicated by the measurement report representation 1624 showing checkmarks over all of the segments.

As can be seen by the signaling chart 1600, the UE 1602 does not retransmit segments to the NW (via the network element 1604) that the NW has already successfully received. This can improve on the performance of legacy approaches that would transmit segments of the segmented message multiple times based on a purge of segments due to an HO in the legacy approaches. Accordingly, the illustrated approach can reduce overhead signaling for segmented messages transmitted during an HO.

Example 2: For UL RRC segment continuity during HO, UE does not receive RRC segment reception status report within T, UE assumes all segments are not received in NW side. FIG. 17 illustrates an example signaling chart 1700 with timer based RRC segment status feedback in accordance with some embodiments. For example, the signaling chart 1700 illustrates a plurality of transmissions and/or operations that may be performed in relation to timer based RRC segment status reporting for example 2.

The signaling chart 1700 may include a UE 1702. The UE 1702 may include one or more of the features of the UE 2200 (FIG. 22) . The UE 1702 may be scheduled to transmit a message.

The signaling chart 1700 may further include a network element 1704, which may be a base station or may be connected to the UE 1702 via a base station. The network element 1704 may include one or more of the features of the gNB 2300 (FIG. 23) . The UE 1702 may have a connection established with the network element 1704 at the initiation of the signaling illustrated in the signaling chart 1700.

The network element 1704 may configure the UE 1702 for SRB4 with UL segment mode prior to the signaling illustrated in the signaling chart 1700. Accordingly, the UE 1702 may segment messages that are larger than a maximum size of a PDCP SDU.

The UE 1702 may have a message to be transmitted to the NW via the network element 1704. In some embodiments, the message may comprise an RRC message. The message may be larger than the maximum size of the PDCP SDU for the system. Due to the message being larger than the maximum size of the PDCP SDU, the UE 1702 may segment the message into four separate segments to be transmitted to the network element 1704, as shown by message representation 1706.

For example, the UE 1702 may transmit to the network element 1704 the segments of the message via RLC PDUs. For example, the UE 1702 may transmit a first segment via a first RLC PDU 1708, a second segment via a second RLC PDU 1710, a third segment via a third RLC PDU 1712, and a fourth segment via a fourth RLC PDU 1714 in the illustrated embodiment.

The network element 1704 may receive the RLC PDUs from the UE 1702. For example, network element 1704 may receive the first RLC PDU 1708, the second RLC PDU 1710, the third RLC PDU 1712, and the fourth RLC PDU 1714 in the illustrated embodiment. The network element 1704 may identify the segments of the segmented message received in the RLC PDUs. In the illustrated embodiment, the network element 1704 may identify the first segment received in the first RLC PDU 1708, the second segment received in the second RLC PDU 1710, the third segment received in the third RLC PDU 1712, and the fourth segment received in the fourth RLC PDU 1714. The network element 1704 may store the segments, such as in an RRC buffer.

An HO procedure may be initiated after the four segments of the segmented message have successfully received by the network element 1704. The HO procedure may include the network element 1704 transmitting an HO command 1716 to the UE 1702 that indicates the UE 1702 is to perform an HO operation. The HO procedure may further include the UE 1702 transmitting an HO complete message 1718 to the network element 1704 to complete the HO. The network element 1704 may store the four segments of the segmented message received prior to the HO procedure during the HO procedure.

The UE 1702 may initiate a countdown of a timer 1720 based on the HO. For example, the UE 1702 may initiate countdown of the timer 1720 at the beginning of the HO procedure, at the end of the HO procedure, or some other time during the HO procedure. In the illustrated embodiment, the UE 1702 initiates the countdown of the timer 1720 at the completion of the HO. The UE 1702 may determine whether the segments have been received based on whether an RRC segment reception status is received during the countdown of the timer 1720. In the illustrated embodiment, the UE 1702 may be configured to determine that the segments have been successfully received based on the UE 1702 receiving an RRC segment reception status prior to expiration of the timer 1720. Accordingly, the UE 1702 may determine that one or more of the segments have not been successfully received by the network element 1704 based on the UE 1702 not receiving an RRC segment reception status prior to expiration of the timer 1720.

In the illustrated instance, the UE 1702 does not receive an RRC segment reception status prior to the expiration of the timer 1720. Accordingly, the UE 1702 may determine that all of these segments transmitted to the network element 1704 have not been successfully received, as indicated by the measurement report representation 1722 showing the segments without checkmarks. Based on the UE 1702 determining that the segments have not been successfully received by the network element 1704, the UE 1702 may retransmit the first segment, the second segment, the third segment, and the fourth segment in transmission 1724. While the transmission 1724 is shown as a single transmission, it should be understood that the transmission 1724 may comprise multiple transmissions in other embodiments where the segments may be transmitted in separate transmissions.

FIG. 18 illustrates an example procedure 1800 of operating a transmitting device in accordance with some embodiments. The transmitting device may comprise a UE (such as the UE 2200 (FIG. 22) ) or a base station (such as the gNB 2300 (FIG. 23) ) .

The procedure 1800 may include initiating a first transmission of a plurality of segments in 1802. For example, the transmitting device may initiate a first transmission is a plurality of segments of a segmented message. In some embodiments, the segmented message may comprise an RRC segmented message. The message may be segmented based on size of the message being larger than a threshold size, such as being larger than the maximum size of a PDCP SDU.

The procedure 1800 may include determining an HO operation is to be performed in 1804. For example, the transmitting device may determine in HO operation is to be performed during transmission of the plurality of segments. In some embodiments, the HO operation may be to transition a connection for a receiving device to each second transmitting device. Further, the HO operation may be to transition a connection for the receiving device to a second cell in some embodiments. In some embodiments, the HO operation may be to transition a connection for the transmitting device to a second receiving device.

The procedure 1800 may include receiving a PDCP control PDU in 1806. For example, the receiving device may receive a PDCP control PDU. The PDCP control PDU may include a PDU type that indicates the PDCP control PDU is for RRC segment feedback. In some embodiments, 1806 may be omitted.

The procedure 1800 may include receiving and RLC control PDU in 1808. For example, the receiving device may receive the RLC control PDU. The RLC control PDU may include a CPT that indicates the RLC control PDU is for RRC segment feedback. In some embodiments, 1808 may be omitted.

The procedure 1800 may include receiving a MAC CE in 1810. For example, the receiving device may receive the MAC CE. The MAC CE may include a LCID or an eLCID that indicates the MAC CE is for RRC segment feedback. In some embodiments, 1810 may be omitted.

The procedure 1800 may include determining a first portion of the plurality of segments were successfully received in 1812. For example, the year transmitting device may determine a first portion of the plurality of segments were successfully received by receiving device.

In some embodiments, determining the first portion of the plurality of segments were successfully received by the receiving device comprises receiving an RRC feedback message that indicates the first portion of the plurality of segments were successfully received. In other embodiments, determining the first portion of the plurality of segments were successfully received by the receiving device comprises receiving a PDCP control PDU that indicates the first portion of the plurality of segments were successfully received. Further, determining the first portion of the plurality of segments were successfully received by the receiving device comprises receiving and RLC control PDU that indicates the first portion of the plurality of segments were successfully received in other embodiments. In other embodiments, determining the first portion of the plurality of segments were successfully received by the receiving device comprises receiving a MAC CE that indicates the first portion of the plurality of segments were successfully received.

In some embodiments, determining the first portion of the plurality of segments were successfully received by the receiving device comprises receiving an RLC status report that indicates the first portion of the plurality of segments were successful received. In other embodiments, determining the first portion of the plurality of segments were successfully received by the receiving device comprises receiving a PDCP status report that indicates the first portion of the plurality of segments were successfully received.

In some embodiments, determining the first portion of the plurality of segments were successful received by the receiving device comprises storing a timer based on the HO operation. Further, the receiving device may determine whether the plurality of segments have been scuffling received by the receiving device based on whether a segment status report has been received prior to the expiration of the timer.

The procedure 1800 may include initiating a second transmission of a second portion of the plurality of segments. For example, the transmitting device may initiate a second transmission of a second portion of the plurality of segments after the HO operation based on said determining that the first portion of the plurality of segments were successfully received by receiving device.

In some embodiments, the transmitting device may be a first transmitting device. The HO operation may be to transition connection for the receiving device to a second transmitting device. In these instances, initiating the second transmission may comprise providing the second portion of the plurality of segments to the second transmitting device for the second transmitting device to transmit to the receiving device.

In some embodiments, the transmitting device may operate a first cell. The HO operation may be to transition a connection for the receiving device to a second cell. In these instances, initiating the second transmission may comprise coordinating a transmission of the second portion of the plurality of segments with the second cell.

In some embodiments, the receiving device may be a first receiving device. The HO operation may be to transition a connection for the transmitting device to a second receiving device. In these instances, initiating the second transmission may comprise transmitting the second portion the plurality of segments to the second receiving device.

While FIG. 18 may arguably imply in order to the procedure 1800, it should be understood that the operations of the procedure 1800 may be performed in a different order, and/or one or more of the operations may be performed concurrently, in other embodiments. Further, it should be understood that one or more additional operations may be added to the procedure 1800, and/or one or more operations of the procedure 1800 may be omitted, in other embodiments.

FIG. 19 illustrates a first portion of an example procedure 1900 of operating a receiving device in accordance with some embodiments. FIG. 20 illustrates a second portion of the example procedure 1900 of operating the receiving device in accordance with some embodiments. The receiving device may comprise a UE (such as the UE 2200 (FIG. 22) ) or a base station (such as the gNB 2300 (FIG. 23) ) .

The procedure 1900 may include receiving a first portion of a plurality of segments in 1902. For example, the receiving device may receive a first portion of a plurality of segments from a transmission of a segmented message from a transmitting device.

The procedure 1900 may include storing the first portion of the plurality of segments in 1904. For example, the receiving device may store the first portion of plurality of segments. In some embodiments, the receiving device may store the first portion of the plurality of segments in an RRC buffer of the receiving device.

The procedure 1900 may include determining an HO operation is to be performed in 1906. For example, the receiving device may determine an HO operation is to be performed during the transmission of the segmented message.

The procedure 1900 may include providing an RLC status report in 1908. For example, the transmitting device may be a first transmitting device. The receiving device may provide, to the first transmitting device or to a second transmitting device, and RLC status report that indicates the first portion of the plurality of segments have been successfully received. In some embodiments, 1908 may be omitted.

The procedure 1900 may include providing a PDCP status report in 1910. For example, the transmitting device may be a first transmitting device. The receiving device may provide, to the first transmit device or to a second transmitting device, a first PDCP status report that indicates the first portion of the plurality of segments have been successfully received. In some embodiments, 1910 may be omitted.

The procedure 1900 may include providing an RRC message in 1912 for example, the transiting device may be a first transmitting device. The receiving device may provide, to the first transmitting device or to a second transmitting device, an RRC message that indicates that the first portion of the plurality of segments have been successfully received. In some embodiments, 1912 may be omitted.

The procedure 1900 may include providing a PDCP control PDU in 1914. For example, the transmitting device may be a first transmitting device. The receiving device may provide, to the first transiting device or to the second transmitting device, a PDCP control PDU that indicates that the first portion of the plurality of segments have been successfully received. In some embodiments, the PDCP control PDU may include a PDU type that indicates the PDCP control PDU is for RRC segment feedback. In some embodiments, 1914 may be omitted.

The procedure 1900 may include providing an RLC control PDU in 1916. For example, the transmitting device may be a first transmitting device. The receiving device may provide, to the first transmitting device or to the second transmitting device, an RLC control PDU that indicates that the first portion of the plurality of segments have been successfully received. In some embodiments, the RLC control PDU may include a CPT that indicates the RLC control PDU is for RRC segment feedback. In some embodiments, 1916 may be omitted.

The procedure 1900 may include providing a MAC CE in 1918. For example, the transmitting device may be a first transmitting device. The receiving device may provide, to the first transmitting device or to the second transmitting device, a MAC CE that indicates that the first portion of the plurality of segments have been successfully received. In some embodiments, the MAC CE includes an LCID or an eLCID that indicates the MAC CE is for RRC segment feedback. In some embodiments, 1918 may be omitted.

The procedure 1900 may proceed from 1918 to 1920.1920 of FIG. 19 may be the same as 1920 of FIG. 20, such that the procedure 1900 proceeds from 1920 of FIG. 19 to 1920 of FIG. 20.1920 of FIG. 20 may proceed to 2002.

The procedure 1900 may include transmitting a segments status report within a period of time in 2002. For example, the transmitting device may be a first transmitting device. The receiving device may transmit, to the first transmitting device or to a second transmitting device, a segments status report within a period of time of the HO operation to indicate whether entirety of the plurality of segments from the transmission of the segmented message have been successfully received. In some embodiments, 2002 may be omitted.

The procedure 1900 may include receiving a second portion of the plurality of segments in 2004. For example, the receiving device may receive a second portion of the plurality of segments after completion of the HO operation. In some embodiments, 2004 may be omitted.

The procedure 1900 may include determining that the first portion of the plurality of segments and the second portion of the plurality of segments comprise an entirety of the plurality of segments in 2006. For example, the receiving device may determine that the first portion of the plurality of segments and the second portion of the plurality of segments comprise an entirety of the plurality of segments from the transmission of the segmented message. In some embodiments, 2006 may be omitted.

The procedure 1900 may include utilizing the stored first portion of the plurality of segments in 2008. For example, the receiving device may utilize the stored first portion of the plurality of segments for processing of the segmented message.

In some embodiments where the receiving device determines that the first portion and the second portion of the plurality of segments comprise an entirety of the plurality of segments, utilizing the stored first portion of the plurality of segments may comprise utilizing the first portion of the property segments and the second portion the plurality of segments to assemble the segmented message.

In some embodiments, the receiving device may be a first receiving device. In these instances, utilizing the stored first portion of the plurality of segments may comprise providing the stored first portion of the plurality of segments to second receiving device for assembly of the segmented message.

While FIG. 19 and FIG. 20 may arguably imply in order to the procedure 1900, it should be understood that the operations of the procedure 1900 may be performed in a different order, and/or one or more of the operations may be performed concurrently, in other embodiments. Further, it should be understood that one or more additional operations may be added to the procedure 1900, and/or one or more operations of the procedure 1900 may be omitted, in other embodiments.

FIG. 21 illustrates an example procedure 2100 of operating a receiving device in accordance with some embodiments. The receiving device may comprise a UE (such as the UE 2200 (FIG. 22) ) or a base station (such as the gNB 2300 (FIG. 23) ) .

The procedure 2100 may include determining an HO operation is to be performed in 2102. For example, the receiving device may determine an HO operation is to be performed while the receiving device is receiving segments of a segmented message from a first transmission device.

The procedure 2100 may include determining a portion of the segments were successful received in 2104. For example, the receiving device may determine a portion of the segments were successful received prior to the HO operation.

The procedure 2100 may include providing indication of the portion of segments in 2106. For example, the receiving device may provide, to the first transmitting device or to a second transmitting device related to the HO operation, an indication of the portion of the segments that were successfully received.

In some embodiments, providing the indication of the portion of the segments that were successfully received may comprise providing, to the first transmitting device or to the second transmitting device, an RLC status report or a PDCP status report that indicates the portion of the segments that were successfully received.

In some embodiments, providing the indication of the portion of the segments successfully received may comprise providing, to the first transmitting device or to the second transmitting device, an RRC message that indicates the portion of the segments were successfully received. In other embodiments, providing the indication of the portion of the segments is also received may comprise providing, to the first transmitting device or to the second transmitting device, a PDCP control PDU that indicates the portion of the segments were successfully received. Further, providing the indication of the portion the segments successfully received may comprise providing, to the first transmitting device or to the second transmitting device, an RLC control PDU that indicates the portion of the segments were successfully received in other embodiments. In other embodiments, providing the indication of the portion of the segments successfully received may comprise providing, to the first transmitting device or to the second transmitting device, a MAC CE that indicates the portion of the segments were successfully received.

The procedure 2100 may include receiving a second portion of the segments in 2108. For example, the receiving device may receive a second portion of the segments of the segmented message after completion of the HO operation. In some embodiments, 2108 may be omitted.

The procedure 2100 may include determining that the first portion of the segments and the second portion of the segments comprise an entirety of the segments in 2110. For example, the receiving device may determine that the first portion of the segments and the second portion of the segments comprise an entirety of the segments of the segmented message. In some embodiments, 2110 may be omitted.

The procedure 2100 may include assembling the first portion the segments and the second portion of the segments in 2112. For example, the receiving device may assemble the first portion of the segments and the second portion the segments to produce the segmented message. In some embodiments, 2112 may be omitted.

While FIG. 21 may arguably imply in order to the procedure 2100, it should be understood that the operations of the procedure 2100 may be performed in a different order, and/or one or more of the operations may be performed concurrently, in other embodiments. Further, it should be understood that one or more additional operations may be added to the procedure 2100, and/or one or more operations of the procedure 2100 may be omitted, in other embodiments.

FIG. 22 illustrates an example UE 2200 in accordance with some embodiments. The UE 2200 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, electric voltage/current meters, actuators, etc. ) , video surveillance/monitoring devices (for example, cameras, video cameras, etc. ) , wearable devices (for example, a smart watch) , relaxed-IoT devices. In some embodiments, the UE 2200 may be a RedCap UE or NR-Light UE.

The UE 2200 may include processors 2204, RF interface circuitry 2208, memory/storage 2212, user interface 2216, sensors 2220, driver circuitry 2222, power management integrated circuit (PMIC) 2224, antenna structure 2226, and battery 2228. The components of the UE 2200 may be implemented as integrated circuits (ICs) , portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 22 is intended to show a high-level view of some of the components of the UE 2200. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

The components of the UE 2200 may be coupled with various other components over one or more interconnects 2232, which may represent any type of interface, input/output, bus (local, system, or expansion) , transmission line, trace, optical connection, etc. that allows various circuit components (on common or different chips or chipsets) to interact with one another.

The processors 2204 may include processor circuitry such as, for example, baseband processor circuitry (BB) 2204A, central processor unit circuitry (CPU) 2204B, and graphics processor unit circuitry (GPU) 2204C. The processors 2204 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory/storage 2212 to cause the UE 2200 to perform operations as described herein.

In some embodiments, the baseband processor circuitry 2204A may access a communication protocol stack 2236 in the memory/storage 2212 to communicate over a 3GPP compatible network. In general, the baseband processor circuitry 2204A may access the communication protocol stack to: perform user plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a non-access stratum layer. In some embodiments, the PHY layer operations may additionally/alternatively be performed by the components of the RF interface circuitry 2208.

The baseband processor circuitry 2204A may generate or process baseband signals or waveforms that carry information in 3GPP-compatible networks. In some embodiments, the waveforms for NR may be based cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

The memory/storage 2212 may include one or more non-transitory, computer-readable media that includes instructions (for example, communication protocol stack 2236) that may be executed by one or more of the processors 2204 to cause the UE 2200 to perform various operations described herein. The memory/storage 2212 include any type of volatile or non-volatile memory that may be distributed throughout the UE 2200. In some embodiments, some of the memory/storage 2212 may be located on the processors 2204 themselves (for example, L1 and L2 cache) , while other memory/storage 2212 is external to the processors 2204 but accessible thereto via a memory interface. The memory/storage 2212 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM) , static random access memory (SRAM) , eraseable programmable read only memory (EPROM) , electrically eraseable programmable read only memory (EEPROM) , Flash memory, solid-state memory, or any other type of memory device technology.

The RF interface circuitry 2208 may include transceiver circuitry and radio frequency front module (RFEM) that allows the UE 2200 to communicate with other devices over a radio access network. The RF interface circuitry 2208 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

In the receive path, the RFEM may receive a radiated signal from an air interface via antenna structure 2226 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processors 2204.

In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna 2226.

In various embodiments, the RF interface circuitry 2208 may be configured to transmit/receive signals in a manner compatible with NR access technologies.

The antenna 2226 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged into one or more antenna panels. The antenna 2226 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna 2226 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna 2226 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.

The user interface circuitry 2216 includes various input/output (I/O) devices designed to enable user interaction with the UE 2200. The user interface 2216 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button) , a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position (s) , or other like information. Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (for example, binary status indicators such as light emitting diodes “LEDs” and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays (LCDs) , LED displays, quantum dot displays, projectors, etc. ) , with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 2200.

The sensors 2220 may include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units comprising accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems comprising 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (for example, thermistors) ; pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (for example, cameras or lensless apertures) ; light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like) ; depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other like audio capture devices; etc.

The driver circuitry 2222 may include software and hardware elements that operate to control particular devices that are embedded in the UE 2200, attached to the UE 2200, or otherwise communicatively coupled with the UE 2200. The driver circuitry 2222 may include individual drivers allowing other components to interact with or control various input/output (I/O) devices that may be present within, or connected to, the UE 2200. For example, driver circuitry 2222 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensor circuitry 2220 and control and allow access to sensor circuitry 2220, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

The PMIC 2224 may manage power provided to various components of the UE 2200. In particular, with respect to the processors 2204, the PMIC 2224 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.

In some embodiments, the PMIC 2224 may control, or otherwise be part of, various power saving mechanisms of the UE 2200. For example, if the platform UE is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the UE 2200 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the UE 2200 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The UE 2200 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The UE 2200 may not receive data in this state; in order to receive data, it must transition back to RRC_Connected state. An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours) . During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

A battery 2228 may power the UE 2200, although in some examples the UE 2200 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 2228 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 2228 may be a typical lead-acid automotive battery.

FIG. 23 illustrates an example gNB 2300 in accordance with some embodiments. The gNB 2300 may include processors 2304, RF interface circuitry 2308, core network (CN) interface circuitry 2312, memory/storage circuitry 2316, and antenna structure 2326.

The components of the gNB 2300 may be coupled with various other components over one or more interconnects 2328.

The processors 2304, RF interface circuitry 2308, memory/storage circuitry 2316 (including communication protocol stack 2310) , antenna structure 2326, and interconnects 2328 may be similar to like-named elements shown and described with respect to FIG. 22.

The CN interface circuitry 2312 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC-compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to/from the gNB 2300 via a fiber optic or wireless backhaul. The CN interface circuitry 2312 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 2312 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

Examples

In the following sections, further exemplary embodiments are provided.

Example 1 may include a method of operating a transmitting device, comprising initiating a first transmission of a plurality of segments of a segmented message, determining a mobility event is to be performed during transmission of the plurality of segments, determining a first portion of the plurality of segments were successfully received by a receiving device, and initiating a second transmission of a second portion of the plurality of segments after the mobility event based on said determining that the first portion of the plurality of segments were successfully received by the receiving device.

Example 2 may include the method of example 1, wherein the transmitting device is a first transmitting device, wherein the mobility event is to transition a connection for the receiving device to a second transmitting device, and wherein initiating the second transmission comprises providing the second portion of the plurality of segments to the second transmitting device for the second transmitting device to transmit to the receiving device.

Example 3 may include the method of example 1, wherein the transmitting device operates a first cell, wherein the mobility event is to transition a connection for the receiving device to a second cell, and wherein initiating the second transmission comprises coordinating transmission of the second portion of the plurality of segments with the second cell.

Example 4 may include the method of example 1, wherein the receiving device is a first receiving device, wherein the mobility event is to transition a connection for the transmitting device to a second receiving device, and wherein initiating the second transmission comprises transmitting the second portion of the plurality of segments to the second receiving device.

Example 5 may include the method of example 1, wherein determining the first portion of the plurality of segments were successfully received by the receiving device comprises receiving a radio resource control (RRC) feedback message that indicates the first portion of the plurality of segments were successfully received, receiving a packet data convergence protocol (PDCP) control protocol data unit (PDU) that indicates the first portion of the plurality of segments were successfully received, receiving a radio link control (RLC) control PDU that indicates the first portion of the plurality of segments were successfully received, or receiving a medium access control (MAC) control element (CE) that indicates the first portion of the plurality of segments were successfully received.

Example 6 may include the method of example 5, wherein the method comprises receiving the PDCP control PDU, and wherein the PDCP control PDU includes a PDU type that indicates the PDCP control PDU is for RRC segment feedback, the method comprises receiving the RLC control PDU, and wherein the RLC control PDU includes a control package type (CPT) that indicates the RLC control PDU is for RRC segment feedback, or the method comprises receiving the MAC CE, and wherein the MAC CE includes a logical channel identifier (LCID) or an extended logical channel identifier (eLCID) that indicates the MAC CE is for RRC segment feedback.

Example 7 may include the method of example 1, wherein determining the first portion of the plurality of segments were successfully received by the receiving device comprises receiving a radio link control (RLC) status report that indicates the first portion of the plurality of segments were successfully received, or receiving a packet data convergence protocol (PDCP) status report that indicates the first portion of the plurality of segments were successfully received.

Example 8 may include the method of example 1, wherein determining the first portion of the plurality of segments were successfully received by the receiving device comprises starting a timer based on the mobility event, and determining whether the plurality of segments have been successfully received by the receiving device based on whether a segment status report has been received prior to expiration of the timer.

Example 9 may include one or more non-transitory, computer-readable media having instructions that, when executed by one or more processors, cause a receiving device to receive, from a transmitting device, a first portion of a plurality of segments from a transmission of a segmented message, store the first portion of the plurality of segments, determine a mobility event is to be performed during the transmission of the segmented message, and utilize the stored first portion of the plurality of segments to process the segmented message.

Example 10 may include the one or more non-transitory, computer-readable media of example 9, wherein the instructions, when executed by the one or more processors, further cause the receiving device to receive a second portion of the plurality of segments after completion of the mobility event, and determine that the first portion of the plurality of segments and the second portion of the plurality of segments comprise an entirety of the plurality of segments from the transmission of the segmented message, and wherein to utilize the stored first portion of the plurality of segments comprises to utilize the first portion of the plurality of segments and the second portion of the plurality of segments to assemble the segmented message.

Example 11 may include the one or more non-transitory, computer-readable media of example 9, wherein the receiving device is a first receiving device, and wherein to utilize the stored first portion of the plurality of segments comprises to provide the stored first portion of the plurality of segments to a second receiving device for assembly of the segmented message.

Example 12 may include the one or more non-transitory, computer-readable media of example 9, wherein the transmitting device is a first transmitting device, and wherein the instructions, when executed by the one or more processors, further cause the receiving device to provide, to the first transmitting device or to a second transmitting device, a radio link control (RLC) status report that indicates the first portion of the plurality of segments have been successfully received.

Example 13 may include the one or more non-transitory, computer-readable media of example 9, wherein the transmitting device is a first transmitting device, and wherein the instructions, when executed by the one or more processors, further cause the receiving device to provide, to the first transmitting device or to a second transmitting device, a packet data convergence protocol (PDCP) status report that indicates the first portion of the plurality of segments have been successfully received.

Example 14 may include the one or more non-transitory, computer-readable media of example 9, wherein the transmitting device is a first transmitting device, and wherein the instructions, when executed by the one or more processors, further cause the receiving device to provide, to the first transmitting device or to a second transmitting device, a radio resource control (RRC) message that indicates that the first portion of the plurality of segments have been successfully received, provide, to the first transmitting device or to the second transmitting device, a packet data convergence protocol (PDCP) control protocol data unit (PDU) that indicates that the first portion of the plurality of segments have been successfully received, provide, to the first transmitting device or to the second transmitting device, a radio link control (RLC) control PDU that indicates that the first portion of the plurality of segments have been successfully received, or provide, to the first transmitting device or to the second transmitting device, a medium access control (MAC) control element (CE) that indicates that the first portion of the plurality of segments have been successfully received.

Example 15 may include the one or more non-transitory, computer-readable media of example 14, wherein the instructions, when executed by the one or more processors, further cause the receiving device to provide the PDCP control PDU, and wherein the PDCP control PDU includes a PDU type that indicates the PDCP control PDU is for RRC segment feedback, the instructions, when executed by the one or more processors, further cause the receiving device to provide the RLC control PDU, and wherein the RLC control PDU includes a control package type (CPT) that indicates the RLC control PDU is for RRC segment feedback, and the instructions, when executed by the one or more processors, further cause the receiving device to provide the MAC CE, and wherein the MAC CE includes a logical channel identifier (LCID) or an extended logical channel identifier (eLCID) that indicates the MAC CE is for RRC segment feedback.

Example 16 may include the one or more non-transitory, computer-readable media of example 9, wherein the transmitting device is a first transmitting device, and wherein the instructions, when executed by the one or more processors, further cause the receiving device to transmit, to the first transmitting device or to a second transmitting device, a segment status report within a period of time of the mobility event to indicate whether an entirety of the plurality of segments from the transmission of the segmented message have been successfully received.

Example 17 may include a receiving device, comprising memory to store one or more segments of a segmented message, and one or more processors coupled to the memory, the one or more processors to determine a mobility event is to be performed while the receiving device is receiving segments of a segmented message from a first transmitting device, determine a portion of the segments were successfully received prior to the mobility event, and provide, to the first transmitting device or to a second transmitting device related to the mobility event, an indication of the portion of the segments that were successfully received.

Example 18 may include the receiving device of example 17, wherein the portion of the segments is a first portion of the segments, and wherein the receiving device is further to receive a second portion of the segments of the segmented message after completion of the mobility event, determine that the first portion of the segments and the second portion of the segments comprise an entirety of the segments of the segmented message, and assemble the first portion of the segments and the second portion of the segments to produce the segmented message.

Example 19 may include the receiving device of example 17, wherein to provide the indication of the portion of the segments that were successfully received comprises to provide, to the first transmitting device or to the second transmitting device, a radio link control (RLC) status report or a packet data convergence protocol (PDCP) status report that indicates the portion of the segments that were successfully received.

Example 20 may include the receiving device of example 17, wherein to provide the indication of the portion of the segments successfully received comprises to provide, to the first transmitting device or to the second transmitting device, a radio resource control (RRC) message that indicates the portion of the segments were successfully received, provide, to the first transmitting device or to the second transmitting device, a packet data convergence protocol (PDCP) control protocol data unit (PDU) that indicates the portion of the segments were successfully received, provide, to the first transmitting device or to the second transmitting device, a radio link control (RLC) control PDU that indicates the portion of the segments were successfully received, or provide, to the first transmitting device or to the second transmitting device, a medium access control (MAC) control element (CE) that indicates the portion of the segments were successfully received.

Example 21 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.

Example 22 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.

Example 23 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.

Example 24 may include a method, technique, or process as described in or related to any of examples 1-20, or portions or parts thereof.

Example 25 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.

Example 26 may include a signal as described in or related to any of examples 1-20, or portions or parts thereof.

Example 27 may include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.

Example 28 may include a signal encoded with data as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.

Example 29 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.

Example 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.

Example 31 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.

Example 32 may include a signal in a wireless network as shown and described herein.

Example 33 may include a method of communicating in a wireless network as shown and described herein.

Example 34 may include a system for providing wireless communication as shown and described herein.

Example 35 may include a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples) , unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

A method of operating a transmitting device, comprising:

initiating a first transmission of a plurality of segments of a segmented message;

determining a mobility event is to be performed during transmission of the plurality of segments;

determining a first portion of the plurality of segments were successfully received by a receiving device; and

initiating a second transmission of a second portion of the plurality of segments after the mobility event based on said determining that the first portion of the plurality of segments were successfully received by the receiving device.
The method of claim 1, wherein the transmitting device is a first transmitting device, wherein the mobility event is to transition a connection for the receiving device to a second transmitting device, and wherein initiating the second transmission comprises providing the second portion of the plurality of segments to the second transmitting device for the second transmitting device to transmit to the receiving device.
The method of claim 1 or claim 2, wherein the transmitting device operates a first cell, wherein the mobility event is to transition a connection for the receiving device to a second cell, and wherein initiating the second transmission comprises coordinating transmission of the second portion of the plurality of segments with the second cell.
The method of any of claims 1 to 3, wherein the receiving device is a first receiving device, wherein the mobility event is to transition a connection for the transmitting device to a second receiving device, and wherein initiating the second transmission comprises transmitting the second portion of the plurality of segments to the second receiving device.
The method of any of claims 1 to 4, wherein determining the first portion of the plurality of segments were successfully received by the receiving device comprises:

receiving a radio resource control (RRC) feedback message that indicates the first portion of the plurality of segments were successfully received;

receiving a packet data convergence protocol (PDCP) control protocol data unit (PDU) that indicates the first portion of the plurality of segments were successfully received;

receiving a radio link control (RLC) control PDU that indicates the first portion of the plurality of segments were successfully received; or

receiving a medium access control (MAC) control element (CE) that indicates the first portion of the plurality of segments were successfully received.
The method of claim 5, wherein:

the method comprises receiving the PDCP control PDU, and wherein the PDCP control PDU includes a PDU type that indicates the PDCP control PDU is for RRC segment feedback;

the method comprises receiving the RLC control PDU, and wherein the RLC control PDU includes a control package type (CPT) that indicates the RLC control PDU is for RRC segment feedback; or

the method comprises receiving the MAC CE, and wherein the MAC CE includes a logical channel identifier (LCID) or an extended logical channel identifier (eLCID) that indicates the MAC CE is for RRC segment feedback.
The method of any of claims 1 to 6, wherein determining the first portion of the plurality of segments were successfully received by the receiving device comprises:

receiving a radio link control (RLC) status report that indicates the first portion of the plurality of segments were successfully received; or

receiving a packet data convergence protocol (PDCP) status report that indicates the first portion of the plurality of segments were successfully received.
The method of any of claims 1 to 7, wherein determining the first portion of the plurality of segments were successfully received by the receiving device comprises:

starting a timer based on the mobility event; and

determining whether the plurality of segments have been successfully received by the receiving device based on whether a segment status report has been received prior to expiration of the timer.
One or more computer-readable media having instructions that, when executed by one or more processors, cause a receiving device to:

receive, from a transmitting device, a first portion of a plurality of segments from a transmission of a segmented message;

store the first portion of the plurality of segments;

determine a mobility event is to be performed during the transmission of the segmented message; and

utilize the stored first portion of the plurality of segments to process the segmented message.
The one or more computer-readable media of claim 9, wherein the instructions, when executed by the one or more processors, further cause the receiving device to:

receive a second portion of the plurality of segments after completion of the mobility event; and

determine that the first portion of the plurality of segments and the second portion of the plurality of segments comprise an entirety of the plurality of segments from the transmission of the segmented message, and wherein to utilize the stored first portion of the plurality of segments comprises to utilize the first portion of the plurality of segments and the second portion of the plurality of segments to assemble the segmented message.
The one or more computer-readable media of claim 9 or claim 10, wherein the receiving device is a first receiving device, and wherein to utilize the stored first portion of the plurality of segments comprises to provide the stored first portion of the plurality of segments to a second receiving device for assembly of the segmented message.
The one or more computer-readable media of any of claims 9 to 11, wherein the transmitting device is a first transmitting device, and wherein the instructions, when executed by the one or more processors, further cause the receiving device to provide, to the first transmitting device or to a second transmitting device, a radio link control (RLC) status report that indicates the first portion of the plurality of segments have been successfully received.
The one or more computer-readable media of any of claims 9 to 12, wherein the transmitting device is a first transmitting device, and wherein the instructions, when executed by the one or more processors, further cause the receiving device to provide, to the first transmitting device or to a second transmitting device, a packet data convergence protocol (PDCP) status report that indicates the first portion of the plurality of segments have been successfully received.
The one or more computer-readable media of any of claims 9 to 13, wherein the transmitting device is a first transmitting device, and wherein the instructions, when executed by the one or more processors, further cause the receiving device to:

provide, to the first transmitting device or to a second transmitting device, a radio resource control (RRC) message that indicates that the first portion of the plurality of segments have been successfully received;

provide, to the first transmitting device or to the second transmitting device, a packet data convergence protocol (PDCP) control protocol data unit (PDU) that indicates that the first portion of the plurality of segments have been successfully received;

provide, to the first transmitting device or to the second transmitting device, a radio link control (RLC) control PDU that indicates that the first portion of the plurality of segments have been successfully received; or

provide, to the first transmitting device or to the second transmitting device, a medium access control (MAC) control element (CE) that indicates that the first portion of the plurality of segments have been successfully received.
The one or more computer-readable media of claim 14, wherein:

the instructions, when executed by the one or more processors, further cause the receiving device to provide the PDCP control PDU, and wherein the PDCP control PDU includes a PDU type that indicates the PDCP control PDU is for RRC segment feedback;

the instructions, when executed by the one or more processors, further cause the receiving device to provide the RLC control PDU, and wherein the RLC control PDU includes a control package type (CPT) that indicates the RLC control PDU is for RRC segment feedback; and

the instructions, when executed by the one or more processors, further cause the receiving device to provide the MAC CE, and wherein the MAC CE includes a logical channel identifier (LCID) or an extended logical channel identifier (eLCID) that indicates the MAC CE is for RRC segment feedback.
The one or more computer-readable media of any of claims 9 to 15, wherein the transmitting device is a first transmitting device, and wherein the instructions, when executed by the one or more processors, further cause the receiving device to:

transmit, to the first transmitting device or to a second transmitting device, a segment status report within a period of time of the mobility event to indicate whether an entirety of the plurality of segments from the transmission of the segmented message have been successfully received.
A receiving device, comprising:

memory to store one or more segments of a segmented message; and

one or more processors coupled to the memory, the one or more processors to:

determine a mobility event is to be performed while the receiving device is receiving segments of a segmented message from a first transmitting device;

determine a portion of the segments were successfully received prior to the mobility event; and

provide, to the first transmitting device or to a second transmitting device related to the mobility event, an indication of the portion of the segments that were successfully received.
The receiving device of claim 17, wherein the portion of the segments is a first portion of the segments, and wherein the receiving device is further to:

receive a second portion of the segments of the segmented message after completion of the mobility event;

determine that the first portion of the segments and the second portion of the segments comprise an entirety of the segments of the segmented message; and

assemble the first portion of the segments and the second portion of the segments to produce the segmented message.
The receiving device of claim 17 or claim 18, wherein to provide the indication of the portion of the segments that were successfully received comprises to provide, to the first transmitting device or to the second transmitting device, a radio link control (RLC) status report or a packet data convergence protocol (PDCP) status report that indicates the portion of the segments that were successfully received.
The receiving device of any of claims 17 to 19, wherein to provide the indication of the portion of the segments successfully received comprises to:

provide, to the first transmitting device or to the second transmitting device, a radio resource control (RRC) message that indicates the portion of the segments were successfully received;

provide, to the first transmitting device or to the second transmitting device, a packet data convergence protocol (PDCP) control protocol data unit (PDU) that indicates the portion of the segments were successfully received;

provide, to the first transmitting device or to the second transmitting device, a radio link control (RLC) control PDU that indicates the portion of the segments were successfully received; or

provide, to the first transmitting device or to the second transmitting device, a medium access control (MAC) control element (CE) that indicates the portion of the segments were successfully received.