Method and apparatus for application and resource allocation using lifetime

Abstract

In wireless communication, lifetime is a parameter that can be communicated wirelessly on the wireless access network ("RAN") side. Lifetime information is used for application and resource allocation for increased reliability. For example, when user equipment ("UE") enables replication application, lifetime status application and monitoring can be used to configure configured permission ("CG") resources.

Description

Technology Field

[0001] [preference]

[0002] This application claims priority to PCT / CN2021 / 110754, filed on August 5, 2021, under the title “METHOD AND APPARATUS FOR APPLICATION AND RESOURCE ALLOCATION WITH SURVIVAL TIME” and disclosed in its entirety as WO2023010387A1, the entire disclosure of which is incorporated herein by reference.

[0003] [Technology Field]

[0004] This document generally pertains to wireless communication. More specifically, lifetime timers are utilized for application and resource allocation. Background Technology

[0005] Wireless communication technology is driving the world toward an increasingly connected and networked society. Wireless communication relies on efficient network resource management and allocation between user mobile stations and wireless access network nodes (including, but not limited to, wireless base stations). Next-generation networks are expected to provide high-speed, low-latency, and ultra-reliable communication capabilities to meet the requirements of diverse industries and users. User mobile stations or user equipment (UEs) are becoming increasingly complex, and the volume of data being communicated is continuously increasing. Communication improvements must be made not only to support next-generation network services but also to enhance communication and meet the reliability requirements of vertical industries.

[0006] This document relates to methods, systems, and devices for communicating lifetime information for application and resource allocation. Parameters may be communicated wirelessly on the Radio Access Network ("RAN") side. The lifetime information is used for application and resource allocation for increased reliability. For example, when a User Equipment ("UE") enables duplication application, lifetime status application and monitoring may be used to configure configured grant ("CG") resources. A lifetime threshold may be used to trigger Packet Data Convergence Protocol ("PDCP") duplication.

[0007] In one embodiment, a method for wireless communication comprises: receiving a message containing information on a configured PDCP replication function and a configured permission (CG) type; and activating the replication function based on retransmission scheduling information. The activation step is performed independently by a user device ("UE") from an uplink transmission, and the message is received by the UE from a base station. The method further comprises receiving an activation message for activating a configured permission, wherein the activation message includes predefined Downlink Communication Information ("DCI") containing an indication for activating the configured permission. The PDCP replication function further comprises configurations for a plurality of radio link control ("RLC") entities, and the RLC entities are configured for the UE for activation. The configured permission type information includes a configured permission type that does not require activation or a configured permission type that requires activation by a predefined DCI. The message includes a radio resource control "RRC" message including at least one of RRCReestablishment, RRCReconfiguration, RRCResume, RRCReject, or RRCSetup.

[0008] In one embodiment, a method for wireless communication comprises the steps of: receiving status indication information after retransmitting a first packet that was subject to transmission failure; and performing a status handover after receiving the status indication information. Retransmission scheduling information is provided from a base station to a user device ("UE"), and the UE performs activation based on the status indication information. The status indication information indicates whether the first packet retransmission was successful and includes at least one of an acknowledgment of successful retransmission of the first packet, a keep survival time state indication when the retransmission is unsuccessful, an exit survival time state indication when the retransmission is successful, or a non-acknowledgment of the retransmission. The method further comprises the steps of: transmitting a second packet when the status indication information indicates that the retransmission was not received; and receiving status indication information for the second packet at any branch when the second packet is received. Status indication information indicates whether the second packet transmission was successful, and the information includes a predefined DCI or MAC control element when the retransmission was successful.

[0009] In one embodiment, a method for wireless communication includes the step of providing lifetime information during a handover process. A handover request includes lifetime information, the request is provided by a source base station to a target base station, and the handover process is from the source base station to the target base station. Interruption time and re-establishment time in the handover process and in the event of a wireless link failure are included as part of the lifetime measurement from the lifetime information. Lifetime information in uplink transmission includes at least one of an indication of the current lifetime state or an indication of the use of high priority for transmitting packets. Lifetime information in uplink transmission includes at least one of an indication of the current lifetime state, the duration of the current lifetime, an indication of the number of current consecutive error packets, an indication of the remaining time of the current lifetime, an indication of the number of error packets remaining in the current lifetime, an indication of the time to enter the lifetime state, or an indication of the use of high reliability for transmitting packets. The handover process includes a Dual Active Protocol Stack ("DAPS") handover.

[0010] In one embodiment, a method for wireless communication includes the step of receiving lifetime information during a handover process. A handover request includes lifetime information, the request is received from a source base station by a target base station, and the handover process is from the source base station to the target base station. In a random access procedure, message A or message 3 includes lifetime information, and the message is received from a user device ("UE") by the target base station. The interruption time in the handover process and the re-establishment time in a wireless link failure are included as part of the lifetime measurement from the lifetime information. Lifetime information in uplink transmission includes at least one of an indication of the current lifetime state or an indication of the use of high priority for transmitting packets. Lifetime information in downlink transmission includes at least one of an indication of the current lifetime state, the duration of the current lifetime, an indication of the number of current consecutive error packets, an indication of the remaining time of the current lifetime, an indication of the number of error packets remaining in the current lifetime, an indication of the time to enter the lifetime state, or an indication of the use of high reliability for transmitting packets. The handover process includes a dual active protocol stack ("DAPS") handover.

[0011] In one embodiment, a method for wireless communication includes the step of reporting lifetime information during a handover process. In a random access procedure, message A or message 3 includes lifetime information, and the message is received by a target base station from a user device ("UE"). The lifetime information includes at least one of an indication of a current lifetime state, a duration of the current lifetime, an indication of the number of current consecutive error packets, an indication of the remaining time of the current lifetime, an indication of the number of remaining error packets of the current lifetime, an indication of the time to enter the lifetime state, an indication of the use of high reliability for transmitting packets, an indication of the current lifetime state, or an indication of the use of high priority for transmitting packets.

[0012] In one embodiment, the wireless communication device includes a processor and a memory, and the processor is configured to read code from the memory and implement any of the embodiments discussed above.

[0013] In one embodiment, a computer program product comprises computer-readable program media code stored therein, and the code, when executed by a processor, causes the processor to implement any of the embodiments discussed above.

[0014] In some embodiments, there is a wireless communication device comprising a processor and memory, wherein the processor is configured to read code from memory and implement any method mentioned in any of the embodiments. In some embodiments, in a computer program product in which computer-readable program media code is stored, the code, when executed by the processor, causes the processor to implement any method mentioned in any of the embodiments. The above and other aspects and their implementations are described in more detail in the drawings, description, and claims. Brief explanation of the drawing

[0015] Figure 1 illustrates an exemplary base station. FIG. 2 illustrates an exemplary Random Access (RA) messaging environment. Figure 3 illustrates one example of replicated messaging. Figure 4 illustrates another embodiment of replicated messaging. Figure 5 is an example of messaging with a base station regarding replication and lifetime status. Figure 6 illustrates another embodiment of messaging with a base station regarding replication and lifetime status. Figure 7 illustrates an example of lifetime monitoring in the uplink service during the handover process. Figure 8 illustrates an example of lifetime monitoring in the uplink service during the handover process. Figure 9 illustrates an example of survival time monitoring in a downlink service when the UE enters a survival time state prior to handover. Figure 10 illustrates an example of survival time monitoring in a downlink service when the UE enters a survival time state after handover. FIG. 11 illustrates an example of survival time monitoring of the distributed unit ("DU") and centralized unit ("CU") in the uplink service when the UE enters the survival time state prior to handover. FIG. 12 illustrates an example of survival time monitoring of the base station distribution unit ("DU") and base station central unit ("CU") in the uplink service when the UE enters the survival time state after handover. FIG. 13 illustrates an example of survival time monitoring of the base station distribution unit ("DU") and base station central unit ("CU") in a downlink service when the UE enters the survival time state prior to handover. FIG. 14 illustrates an example of survival time monitoring of the base station distribution unit ("DU") and base station central unit ("CU") in a downlink service when the UE enters a survival time state after handover. FIG. 15 illustrates an example of EHC parameters communicated between base station central units ("CU"). FIG. 16 illustrates communication between a base station central unit ("CU") and a base station distributed unit ("DU"). FIG. 17 illustrates communication between a base station distribution unit ("DU") and a user device ("UE") for transmitting time different information. Figure 18 illustrates an exemplary MAC CE format. Figure 19 illustrates another exemplary MAC CE format. Specific details for implementing the invention

[0016] The present disclosure will now be described in detail below with reference to the accompanying drawings, which show specific examples of embodiments in an illustrative manner that form part of the present disclosure. However, it should be noted that since the present disclosure may be embodied in various different forms, the subject matter covered or claimed is intended not to be limited to any of the embodiments presented below.

[0017] Throughout the specification and claims, terms may have nuanced meanings suggested or implied by context in addition to their explicitly stated meanings. Likewise, the phrases "in one embodiment" or "in some embodiments" as used herein do not necessarily refer to the same embodiment, nor do the phrases "in another embodiment" or "in another embodiment" as used herein refer to different embodiments. The phrases "in one implementation" or "in some implementations" as used herein do not necessarily refer to the same implementation, nor do the phrases "in another implementation" or "in another implementation" as used herein refer to different implementations. For example, the claimed subject matter is intended to include a combination of exemplary embodiments or implementations, in whole or in part.

[0018] Generally, terms may be understood at least in part from their use in context. For example, terms such as “and,” “or,” or “and / or” as used herein may include various meanings that may vary at least in part depending on the context in which such terms are used. Typically, when “or” is used to associate a list such as A, B, or C, it is intended to mean A, B, or C as used here in an exclusive sense, as well as A, B, and C as used here in an inclusive sense. Furthermore, terms such as “one or more” or “at least one” as used herein may, at least in part depending on the context, be used to describe a feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Likewise, terms such as “one (a),” “one (an),” or “the” may again, at least in part depending on the context, be understood to convey a singular use or a plural use. Furthermore, the terms "based on" or "determined by" may be understood not to be intended to convey an exclusive set of factors, but instead, at least partially depending on the context, may allow for the existence of additional factors not necessarily explicitly described.

[0019] New Radio Access ("NR") includes lifetime parameters at the application layer to mitigate quality of service ("QoS") requirements for reliability. Lifetime may be transmitted as part of TSC Assistance Information ("TSCAI") parameters. TSCAI does not always include lifetime. The Session Management Function ("SMF") determines lifetime and transmits it to the Next Generation Radio Access Network ("NG RAN") as part of the TSCAI, without requiring specific signaling exchanges with User Equipment ("UE") devices. The RAN may be part of a radio communication system that connects UE devices to other parts of the network via radio or wireless connections.

[0020] As described below, service-related lifetimes and / or parameters may be referred to as service-related parameters or information. The methods, systems, and devices described herein transmit these parameters wirelessly on the wireless access network (“RAN”) side and utilize them for lifetime measurements. A lifetime threshold may be used to trigger packet data convergence protocol (“PDCP”) replication. The parameters may be provided to user equipment (“UE”) devices by radio resource control (“RRC”) messages by the Access and Mobility Management Function (“AMF”), or provided by a base station by non-access stratum (“NAS”) signaling.

[0021] Radio Resource Control ("RRC") is a protocol layer between the base station and the UE at the IP level (network layer). RRC messages are transmitted via the Packet Data Convergence Protocol ("PDCP"). As described, the UE can transmit data infrequently (periodically and / or non-periodically) in the RRC_INACTIVE state without transitioning to the RRC_CONECTED state. This can save UE power consumption and signaling overhead. This can be achieved through the Random Access Channel ("RACH") protocol method or the Configured Permission ("CG") method. CG can be used to reduce the waste of periodically allocated resources by enabling multiple devices to share periodic resources. The base station can assign CG resources to eliminate packet transmission delays and increase the utilization rate of allocated periodic radio resources. The CG method is merely one example of a protocol method for communication, and other examples are possible, including but not limited to RACH.

[0022] The lifetime may include the time during which an application consuming the communication service can continue without an expected message. The lifetime information may further include the maximum number of consecutive message transmission failures. The SMF converts the maximum number of consecutive message transmission failures into time units based on the TSCAI periodicity parameter and determines the lifetime.

[0023] The monitoring mechanism for lifetime and its application on the RAN side can be improved. In one example, when a UE enables PDCP replication, the lifetime state termination can be improved for the configuration of the configured permission ("CG") resource. In addition, the application of the lifetime monitoring mechanism can also be improved.

[0024] FIG. 1 illustrates an exemplary base station (102). The base station may also be referred to as a wireless network node. The base station (102) may be further identified as a node B (NB, e.g., eNB or gNB) in a mobile communication context. The exemplary base station may include a wireless Tx / Rx circuit (113) to receive and transmit with user equipment (UEs; 104). The base station may also include a network interface circuit (116) for coupling the base station to a core network (110), e.g., an optical or wired interconnect, Ethernet and / or other data transmission media / protocol.

[0025] The base station may also include a system circuit section (122). The system circuit section (122) may include processor(s) (124) and / or memory (126). The memory (126) may include an operation (128) and a control parameter (130). The operation (128) may include instructions for execution on one or more of the processors (124) to support the base station's function. For example, the operation may process random access transmission requests from multiple UEs. The control parameter (130) may include parameters or support the execution of the operation (128). For example, the control parameter may include network protocol settings, random access messaging format rules, bandwidth parameters, radio frequency mapping allocations, and / or other parameters.

[0026] FIG. 2 illustrates an exemplary random access messaging environment (200). In the random access messaging environment, a UE (104) can communicate with a base station (102) via a random access channel (252). In this example, the UE (104) supports one or more Subscriber Identity Modules (SIMs), such as SIM1 (202). An electrical and physical interface (206) connects SIM1 (202) to the rest of the user equipment hardware, for example, via a system bus (210).

[0027] The mobile device (200) includes a communication interface (212), system logic (214), and a user interface (218). The system logic (214) may include any combination of hardware, software, firmware, or other logic. The system logic (214) may be implemented, for example, by one or more systems on a chip (SoC), application specific integrated circuits (ASIC), discrete analog and digital circuits, and other circuit components. The system logic (214) is part of the implementation of any desired function within the UE (104). In this regard, the system logic (214) may, for example, decode and play music and video, for example, MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV; execute applications; accept user input; store and retrieve application data; establish, maintain, and terminate mobile phone calls or data connections, for example, an internet connection. It may include logic that facilitates establishing, maintaining, and terminating a wireless network connection, a Bluetooth connection, or other connection; and displaying relevant information about the user interface (218). The user interface (218) and inputs (228) may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or face recognition inputs, buttons, switches, speakers, and other user interface elements. Additional examples of inputs (228) include a microphone, video and still image cameras, a temperature sensor, a vibration sensor, a rotation and orientation sensor, a headset and microphone input / output jack, a Universal Serial Bus (USB) connector, a memory card slot, a radiation sensor (e.g., an IR sensor), and other types of inputs.

[0028] System logic (214) may include one or more processors (216) and memory (220). Memory (220) stores, for example, control instructions (222) that the processor (216) executes to perform desired functions for the UE (104). Control parameters (224) provide and specify configuration and operation options for the control instructions (222). Memory (220) may also store any BT, WiFi, 3G, 4G, 5G, or other data (226) that the UE (104) transmits or receives via the communication interface (212). In various implementations, system power may be supplied by a power storage device such as a battery (282).

[0029] In the communication interface (212), the radio frequency (RF) transmission (Tx) and reception (Rx) circuitry (230) handles the transmission and reception of signals through one or more antennas (232). The communication interface (212) may include one or more transceivers. The transceiver may be a wireless transceiver including a modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), a filter, a waveform shaper, a filter, a preamplifier, a power amplifier, and / or other logic for transmitting and receiving through one or more antennas, or (for some devices) through a physical (e.g., wired) medium.

[0030] The transmitted and received signals may be attached to any of arrays of various formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As one specific example, the communication interface (212) may include a transceiver that supports transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, and 4G / Long Term Evolution (LTE) standards. The technique described below, however, is applicable to other wireless communication technologies, regardless of whether they originate from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partnerships or standardization organizations.

[0031] Replication functions may include packet replication to ensure that packets are not lost and reliability is improved. Packet Data Convergence Protocol (PDCP) replication is one example of a replication function. The PDCP layer handles the delivery of user data, header compression, sequence numbering, replication detection, packet replication, and so on. PDCP replication can be supported for both the user and control planes. The PDCP layer at the transmitter can be responsible for packet replication, while the PDCP layer at the receiver can detect replicated packets. Replicated packets have the same PDCP sequence number that can be used for identification.

[0032] In one example, the base station configures an active PDCP replication via RRC signaling. CG Type 1 resources can be configured for the bandwidth portion (active state) of the serving cell corresponding to each branch of the PDCP replication. In another example, the base station configures an inactive PDCP replication via RRC signaling and activates it via a MAC Control Element ("MAC CE") when the base station determines that it needs to use it. CG Type 2 resources are configured for the bandwidth portion (active state) of the service cell corresponding to each branch of the PDCP replication, and the base station activates the required CG Type 2 resources via downlink control information ("DCI") based on current service information. Since there may be a delay in the base station activation of the PDCP replication, the UE can activate the PDCP replication independently during uplink packet transmission.

[0033] In the configuration of a UE that enables PDCP replication, a method for pre-configuring inactive PDCP replication may include configuring a plurality of wireless link control ("RLC") entities, wherein the UE may choose to enable one or more RLC entities or may include configuring one or more dedicated RLC entities for the UE to enable PDCP replication. A method for configuring CG resources for inactive PDCP replication may be illustrated in FIGS. 3 and 4.

[0034] FIG. 3 illustrates one embodiment of replication messaging. In the case of FIG. 3, the UE independently enables PDCP replication. In the transmission of an uplink packet, the UE can be triggered to independently enable PDCP replication. In block 302, the gNB (i.e., base station) configures inactive PDCP replication with CG type 1 in an RRC message. The RRC message (302) may include at least one of the following: RRCReestablishment, RRCReconfiguration, RRCResume, RRCReject, RRCSetup.

[0035] On the service cell corresponding to each branch of PDCP replication, a CG Type 1 resource may be configured for the active bandwidth part ("BWP"). The use of a CG Type 1 resource may include: 1) the resource is dedicated to the UE that triggers PDCP replication to transmit uplink data; 2) the resource is a non-dedicated resource that can be used to transmit other uplink data, but the uplink data for which the UE triggers PDCP replication for transmission has a higher priority; or 3) the resource is inactive for the UE and will be activated only when the UE triggers PDCP replication. After the UE enables the configuration of PDCP replication, a resource release must be performed for the CG resource corresponding to one or more unused RLC entities. For example, the UE independently disables the CG resource, such as when the UE does not transmit a packet to the CG resource or when the UE transmits another packet to the CG resource.

[0036] FIG. 4 illustrates another embodiment of replication messaging. In the case of FIG. 4, the UE independently enables PDCP replication. In an uplink packet transmission, the UE can trigger the UE to independently enable PDCP replication. In block 402, the gNB (i.e., base station) configures inactive PDCP replication with CG type 2 in an RRC message. The RRC message (402) may include at least one of the following: RRCReestablishment, RRCReconfiguration, RRCResume, RRCReject, RRCSetup. In block 404, the gNB (i.e., base station) uses an enable timer or gNB implementation to trigger predefined downlink control information ("DCI") to indicate the activation of the permission ("CG") configured in block 406. The CG can be used to reduce waste of periodically allocated resources by enabling multiple devices to share periodic resources. The base station can allocate CG resources to eliminate packet transmission delays and increase the utilization rate of allocated periodic radio resources. When the service is periodic, the activation timer starts when a packet is not received during the period when a packet should be received. The value of the timer can be set to a value smaller than the lifetime threshold. If a packet is received before the timer expires, the timer is reset. Alternatively, a predefined DCI in block 406 is triggered to activate the CG after the timer expires.

[0037] On the service cell corresponding to each branch of PDCP replication, an inactive CG Type 2 resource is configured for the active bandwidth portion ("BWP"). Based on information from the gNB side (retransmission schedule, timer, etc.), predefined DCI indication information to enable the CG Type 2 resource may be triggered. The predefined DCI indication information may also be enable indication information that allows the UE side to enable PDCP replication. After the CG Type 2 resource is enabled, the use of the resource includes at least one of the following: 1) the resource is a resource dedicated to the UE that triggers PDCP replication to transmit uplink data; 2) the resource is a non-dedicated resource and may be used to transmit other uplink data, but the uplink data for which the UE triggers PDCP replication for transmission has a higher priority; or 3) the resource is inactive to the UE and will be enabled only when the UE triggers PDCP replication.

[0038] After the UE enables the configuration of PDCP replication, resource release is performed for CG resources corresponding to one or more unused RLC entities. In one example of disabling PDCP replication, resource release needs to be performed for CG resources corresponding to one or more used RLC entities. Releasing CG resources may include: 1) the UE independently disables the CG resources; for example, the UE does not transmit packets from the CG resources or the UE transmits other packets from the CG resources, or 2) the gNB performs an existing disable mechanism, wherein the gNB receives indication of CG resource disablement via a CSI report or a Buffer Status Report ("BSR").

[0039] There may be resource waste and transmission delays in uplink transmission, which can be improved by using explicit feedback on data packets. It is possible to implicitly indicate that a packet was transmitted unsuccessfully through retransmission scheduling indications / information. When parameter lifetime is introduced, the UE can trigger an entry into the lifetime state based on the retransmission scheduling indications / information and independently enable PDCP replication. The information may further include how the UE determines that the PDCP replication function needs to be disabled or that the lifetime state needs to be terminated.

[0040] FIGS. 5 and 6 illustrate indications for a UE to terminate the lifetime state or disable the PDCP replication function based on communication between a base station and a UE. After the UE is triggered to enable the PDCP replication function and enter the lifetime state based on retransmission information (also referred to as ReTx permission or retransmission scheduling), the UE identification may disable the PDCP replication function or terminate the lifetime state by FIG. 6 when retransmission fails and another packet is transmitted, or by FIG. 5 when retransmission is successful.

[0041] FIG. 5 is an example of messaging with a base station regarding replication and lifetime states. In FIG. 5, after an initial transmission failure of a packet, the UE enters a lifetime state based on the reception of retransmission information transmitted by the base station. When the retransmission packet is successfully transmitted, the base station must notify the UE via indication information. The indication information (also referred to as status indication information) notifies the UE of the successful retransmission of packet A. If the indication information does not indicate a successful transmission of the packet, the lifetime state is maintained. The base station informs the UE that the indication information may be via a predefined DCI or MAC CE. The indication information may include a description of whether the retransmission packet was successful. This indication information may include: 1) an explicit acknowledgment (ACK) transmitted for a successful retransmission packet, which fails by default if the UE does not receive the indication; 2) a continuing lifetime state indication for the retransmission packet indicating that the packet failed to be transmitted; 3) a terminated lifetime state indication for the transmitted retransmission packet indicating that the packet was successfully transmitted; or 4) An explicit negative acknowledgment (NACK) sent by default for the last successful retransmitted packet if no indication is received.

[0042] FIG. 6 illustrates another embodiment of messaging with a base station regarding replication and lifetime status. In the event of a failed retransmission of a packet, the UE defaults to the failed delivery of the current packet and is ready to transmit the next packet (Packet B) in the next cycle. After the UE transmits the first packet of the next packet via PDCP replication, the base station may receive multiple identical packets. The base station may notify the UE that the first transmission of the next packet was successful through the indication information described above. Examples of indication information include: 1) if the UE does not receive retransmission information for any branch, the packet is successfully transmitted by default; 2) if the UE receives a predefined DCI or MAC CE for any branch containing an ACK indication of successful delivery of the packet, the packet is successfully transmitted; Or 3) When the UE receives information that the first transmission of a packet failed on all branches (i.e., that each branch needs to retransmit the packet), if the packet was successfully transmitted after the UE received the above indication information, the UE exits the lifetime state and disables PDCP replication. If the packet was not successfully transmitted, the UE remains in the lifetime state.

[0043] In the process of mobile handover, lifetime information can be utilized differently. For example, in traditional handover, the service interruption time can be as long as at least 5 milliseconds. In Dual Active Protocol Stack ("DAP") handover, while the UE maintains data transmission with the source base station, the UE receives a handover command to initiate a random access procedure. In both traditional and DAPS handovers, parameter lifetime may be included along with indication information regarding the lifetime status in the handover process. The base station may be divided into two physical entities named Central Unit ("CU") and Distributed Unit ("DU"). To ensure that the lifetime does not exceed an acceptable range, the target base station (e.g., Target Distributed Unit ("DU")) may need to transmit / receive data packets more reliably based on lifetime monitoring information.

[0044] In the handover process, based on the definition of lifetime, lifetime measurements on the UE side or the base station side must not be restarted due to a handover interruption. In other words, the interruption time in the handover process is included in the lifetime measurement. In the case of a wireless link failure, the re-establishment time may also be included in the lifetime measurement. In uplink transmission, lifetime monitoring information may include at least one of an indication of the current lifetime status or an indication of the use of high reliability for transmitting packets. In downlink transmission, lifetime monitoring information may include at least one of an indication of the current lifetime status, an indication of the duration of the current lifetime, an indication of the number of current consecutive error packets, an indication of the remaining time of the current lifetime, an indication of the number of error packets remaining in the current lifetime, an indication of the time to enter the lifetime status, or an indication of the use of high reliability for transmitting packets. Handovers may be divided into base station-to-base station handovers (gNB-gNB) and base station distribution unit handovers (gNB-DU to gNB-DU).

[0045] FIGS. 7 and 8 illustrate a UE implementing a lifetime monitoring mechanism in an uplink service. FIG. 7 illustrates an example of lifetime monitoring in an uplink service when the UE enters a lifetime state prior to handover. In block 702, the UE first enters a lifetime state. A handover request (704) is transmitted and notifies the target base station containing lifetime information. The target base station performs acknowledgment control (706).

[0046] FIG. 8 illustrates an example of lifetime monitoring in an uplink service when the UE enters a lifetime state after a handover. A handover request (802) is transmitted by the source base station before the UE enters a lifetime state (806). Acknowledgment control (804) and a handover acknowledgment (808) come from the target base station. A handover command (810) is provided from the source base station to the UE. The target base station obtains lifetime monitoring information by at least one of the following two options: 1) lifetime information may be included in a message of a random access procedure (812), the message including message A in a 2-stage RACH (random access channel) and message 3 in a 4-stage RACH; or 2) lifetime information may be included in the handover complete of the UE (814).

[0047] FIGS. 9 and 10 illustrate a base station implementing a survival time monitoring mechanism in a downlink service. FIG. 9 illustrates an example of survival time monitoring in a downlink service when a UE enters a survival time state prior to handover. As illustrated in FIG. 9, when a source base station enters a survival time state (902) prior to handover, the source base station notifies the target base station by including survival time information in a handover request (904). The target base station has an acknowledgment control (906).

[0048] FIG. 10 illustrates an example of survival time monitoring in a downlink service when a UE enters a survival time state after a handover. A handover request (1002) precedes the source base station entering a survival time state (1004). The target base station has an acknowledgment control (1006) and provides a handover acknowledgment (1008) to the source base station. A handover command (1010) from the source base station to the UE includes survival time information. The target base station obtains survival time monitoring information by at least one of the following: 1) survival time information is included in a message of a random access procedure (1012), the message including message A in a 2-stage RACH (random access channel) and message 3 in a 4-stage RACH; or 2) survival time information is included in the completion of the handover of the UE (1014).

[0049] FIGS. 11 and 12 illustrate a UE implementing a lifetime monitoring mechanism in an uplink service when switching between base station distributed units ("DU"). FIG. 11 illustrates an example of lifetime monitoring of base station distributed units ("DU") and base station central units ("CU") in an uplink service when the UE enters a lifetime state prior to handover. The UE first enters a lifetime state (1102). A measurement report (1104) is provided to the source base station DU. The measurement report (1104) may be information for the UE to report measurements to the base station to assist in handover decisions. The measurement report may include lifetime information for the base station CU (1106). Lifetime information may be included within a UE context setup request (1108) from the base station CU to the target base station DU. In response, a UE context setup response (1110) is provided. In other words, the UE enters a survival time state prior to handover, and the base station CU includes survival time information in a UE context setup request (1108) that notifies the target base station-DU, and the base station-CU has survival time information obtained through a measurement report (1106).

[0050] FIG. 12 illustrates an example of survival monitoring by the base station distributed unit ("DU") and base station central unit ("CU") in the uplink service when the UE enters the survival state after a handover. A measurement report (1202) is provided from the UE to the source base station-DU, which then provides a measurement report (1204) to the next base station-CU. The survival state (1206) is entered after a handover request that is part of the measurement report. After a UE context setup request (1208) and a UE context setup response (1210), a UE context modification request (1212) is provided to the source base station-DU, which provides RRC reconfiguration (1214) to the UE and a UE context modification response (1216) to the base station-CU. When the UE enters a lifetime state after handover, the target base station-DU obtains lifetime monitoring information by at least one of the following two options: 1) the lifetime information is included in a message of the random access procedure (1218), the message includes message A in the 2nd stage RACH (random access channel) and message 3 in the 4th stage RACH; or 2) the lifetime information is included in the completion of the RRC reconfiguration of the UE (1220).

[0051] FIGS. 13 and 14 illustrate a base station implementing a survival time monitoring mechanism in a downlink service. FIG. 13 illustrates an example of survival time monitoring by a base station distributed unit ("DU") and a base station central unit ("CU") in a downlink service when a UE enters a survival time state prior to handover. When a UE enters a survival time state (1302) prior to handover (measurement report (1304)), the base station-CU includes survival time information within a UE context setup request (1306) that notifies the target base station-DU, and the base station-CU has survival time information obtained through the measurement report handover request (1304). A UE context setup response (1308) is provided as a response.

[0052] FIG. 14 illustrates an example of survival monitoring by the base station distribution unit ("DU") and base station central unit ("CU") in a downlink service when the UE enters the survival state after a handover. A handover request or measurement report (1402) is provided by the UE to the source base station-DU, which is then provided from the source base station-DU to the base station-CU (1404). Then, the UE enters the survival state (1406), which is after the handover request. A UE context modification request (1408) and a UE context modification response (1410) are communicated. The UE context modification response (1410) includes survival information along with a UE context setup request (1412) from the base station-CU to the target base station-DU. A UE context setup response (1414) and a UE context modification request (1416) are made. An RRC reconfiguration (1418) from the source base station-DU to the UE includes survival information and is followed by a UE context modification response (1420). When the UE enters a lifetime state after handover, the target base station-DU obtains lifetime monitoring information by at least one of the following: 1) lifetime information is included in the UE context setup request (1412) of the base station-CU; 2) lifetime information is included in a message of the random access procedure (1422), the message including message A in the 2nd stage RACH (random access channel) and message 3 in the 4th stage RACH; and / or lifetime information is included in the RRC reconfiguration completion (1424) of the UE (1426) provided to the base station-CU (1426). In one embodiment, the base station-CU obtains lifetime information by a UE context modification response, and the UE obtains lifetime information by RRC reconfiguration.

[0053] In DAPS handover, since there is no interruption in packet transmission, it may be necessary to consider an example where the previous packet is at the source base station and the next packet is at the target base station. Since the DAPS handover process can be the same as the traditional handover process, the method of transmitting survival time monitoring information in traditional handover can also be applied to the DAPS handover process.

[0054] FIG. 15 illustrates an example of Ethernet header compression ("EHC") parameters communicated between base station central units ("CU"). For multiple centralized unit upper planes ("CU-UP") of UEs, the base station can ensure that the total number of EHC contexts of the UEs is less than or equal to the maximum number of EHC contexts supported by the UEs (e.g., maxNumberEHC-Context). For centralized unit control planes ("CU-CP"), the maximum number of EHC contexts supported by the UEs (e.g., maxNumberEHC-Context) and the maximum number of uplink EHC contexts supported for each data radio bearer ("DRB") (e.g., maxCID-EHC-UL) are known, where one CU-CP corresponds to multiple CU-UPs. To avoid a total number of EHC contexts exceeding maxNumberEHC-Context when the UE contains more than one CU-UP, CU-CP may be enhanced in one of two processes. In the first process, CU-CP notifies CU-UP by including the maximum number of downlink EHC contexts for CU-UP (maxCID-EHC-DL) in the EHC parameter. This value is determined by CU-CP based on the maxNumberEHC-Context supported by the DRB for the UE and all maxCID-EHC-ULs. In the second process, CU-CP notifies CU-UP by including the maximum number of uplink and downlink EHC contexts for CU-UP (maxCID-EHC) in the EHC parameter. This value may be determined by CU-CP based on the UE's maxNumberEHC-Context.In other words, maxCID-EHC-DL (maximum number of downlink EHC contexts) or maxCID-EHC (maximum number of uplink and downlink EHC contexts) can be included in the EHC parameter.

[0055] FIG. 16 illustrates communication between a base station central unit ("CU") and a base station distributed unit ("DU"). The base station is divided between the gNB-CU and the gNB-DU. When a UE needs to perform Propagation Delay Compensation ("PDC"), the base station-CU notifies the base station-DU to transmit gNB Rx-Tx, which is base station time difference information requested from the gNB-CU to the gNB-DU. The requested information includes at least one of the following: reference time information reporting control, reset, error indication, GNB-CU configuration update, GNB-DU resource coordination request, paging, and system information delivery commands.

[0056] FIG. 17 illustrates communication between a base station distributed unit ("DU") and a user device ("UE") for transmitting time difference information. As illustrated in FIG. 17, the triggering condition for transmitting gNB Rx-Tx time difference information from the base station-DU to the UE is transmitted either actively by the base station-DU or based on the base station-CU request illustrated in FIG. 16. In this example, the gNB Rx-Tx time difference is transmitted via a predefined MAC CE, and the Logical Channel ID ("LCID") reserved value in the Downlink Shared Channel ("DL-SCH") indicates the predefined MAC CE format. For example, the MAC CE format of the gNB Rx-Tx time difference of the basic time unit ("Tc") for NR is illustrated in FIG. 18 and 19. T c = 1 / (△ fmax · N f ) and, here △ f max = 480·10 3 It is Hz and N f = 4096.

[0057] FIG. 18 illustrates an exemplary MAC CE format. The MAC CE format includes 21 bits (used to represent the gNB Rx-Tx time difference) and 3 bits (used to represent reserved bits).

[0058] FIG. 19 illustrates another exemplary MAC CE format. The MAC CE format includes 21 bits (used to represent the gNB Rx-Tx time difference) and 3 bits (used to represent the k value in the reporting resolution). The reporting resolution is defined as Tc*2k, where k is selected by the gNB from the set {0, 1, 2, 3, 4, 5}.

[0059] The system and process described above may be encoded in a computer-readable medium, such as memory, or a signal-bearing medium, which is programmed within a device such as one or more integrated circuits or one or more processors, or processed by a controller or computer. The data may be analyzed within a computer system and used to generate a spectrum. Where the method is performed by software, the software may reside in memory that is interfaced with or resides in non-volatile or volatile memory communicating with a storage device, a synchronization device, a communication interface, or a transmitter. A circuit or electronic device is designed to transfer data to another location. Memory may contain an ordered list of executable instructions for implementing a logic function. Any system element or logic function described may be implemented through an optical circuit, through a digital circuit, through source code, through an analog circuit, or through an analog source such as an analog electrical, audio, or video signal or combination. Software may be implemented in any computer-readable or signal-bearing medium in connection with the system, device, or device in relation to executable instructions, or for use by means of such instructions. Such a system may include a computer-based system, a system including a processor, or an instruction-executable system capable of executing instructions, or another system capable of selectively fetching instructions from a device or device.

[0060] "Computer-readable media," "machine-readable media," "propagated signal" media, and / or "signal-bearing media" may include any device that stores, communicates, propagates, or transmits software associated with or for use by an instruction-executable system, device, or device. Machine-readable media may be, optionally but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or propagation media. An incomplete list of examples of machine-readable media will include: electrically connected "electronic" devices having one or more wires, portable magnetic or optical discs, volatile memory, e.g., random access memory "RAM," read-only memory "ROM," erasable programmable read-only memory (EPROM or flash memory), or optical fiber. Machine-readable media may also include tangible media on which software is printed. This is because software can be stored electronically as an image or in another format (e.g., via optical scanning) and then compiled, and / or interpreted or otherwise processed. Next, the processed medium can be stored in computer and / or system memory.

[0061] The examples of embodiments described herein are intended to provide a general understanding of the structures of various embodiments. The examples are not intended to be provided as a complete description of all elements and features of devices and systems utilizing the structures or methods described herein. Many other embodiments may be apparent to a person skilled in the art in reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, and such structural and logical substitutions and modifications may be made without departing from the scope of the disclosure. Additionally, the examples are merely illustrative and may not be drawn to scale. Certain proportions within the examples may be exaggerated, while others may be minimized. Accordingly, the disclosure and drawings should be regarded as illustrative rather than restrictive.

[0062] One or more embodiments of the disclosure may be referred to herein by the term “invention” for convenience only, without any intention of voluntarily limiting the scope of the application to any particular invention or concept of invention. Furthermore, it should be understood that while specific embodiments have been illustrated and described herein, any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments illustrated. This disclosure is intended to cover any and all subsequent adaptations or variations of the various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to a person skilled in the art upon reviewing the specification.

[0063] The phrase “coupled with” is defined to mean being directly or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware and software-based components. Variations in the arrangement and type of components may be made without departing from the spirit or scope of the claims set forth herein. Additional, different, or fewer components may be provided.

[0064] The subject matter disclosed above should be considered exemplary and not limiting, and the appended claims are intended to cover all such modifications, improvements, and other embodiments that fall within the true spirit and scope of the invention. Accordingly, to the maximum extent permitted by law, the scope of the invention shall be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be limited or restricted by the foregoing detailed description. Although various embodiments of the invention have been described, it will be apparent to a person skilled in the art that more embodiments and implementations are possible within the scope of the invention. Accordingly, the invention shall not be excluded or limited in light of the appended claims and their equivalents.

Claims

Claim 1 A method for wireless communication performed by a wireless communication system comprising a base station and a wireless device, comprising the step of transmitting, by means of a Centralized Unit Control Plane (CU-CP) of the base station, from a CU-CP of the base station to a CU-UP among a plurality of CU User Planes (CU-UPs) of the base station, an EHC parameter indicating the maximum number of downlink (DL) Ethernet Header Compression (EHC) contexts supported by the wireless device for said CU-UP, wherein the wireless device is configured to communicate with the plurality of CU-UPs; and the CU-CP corresponds to the plurality of CU-UPs and knows the maximum number of EHC contexts supported by the wireless device and the maximum number of uplink EHC contexts supported by each data radio bearer (DRB) on the wireless device; A method for wireless communication, wherein for each of the plurality of CU-UPs, the maximum number of downlink EHC contexts supported by the wireless device is determined by the CU-CP based on both the maximum number of uplink EHC contexts supported on each DRB and the maximum number of EHC contexts supported by the wireless device. Claim 2 A method for wireless communication according to claim 1, wherein the maximum number of EHC contexts supported by the wireless device is the sum of the maximum number of downlink (DL) EHC contexts supported by the wireless device and the maximum number of uplink (UL) EHC contexts supported by the wireless device. Claim 3 A method for wireless communication according to claim 1, further comprising the step of transmitting a request message requesting base station receive-transmit (Rx-Tx) time difference information from the base station CU to a distributed unit (DU). Claim 4 A method for wireless communication according to paragraph 3, wherein the base station Rx-Tx time difference information is used by the wireless device to perform propagation delay compensation (PDC). Claim 5 A method for wireless communication according to paragraph 3, wherein the request message comprises at least one of a reference time information reporting control message; a reset message; an error indication message; a gNB-CU configuration update message; a gNB-DU resource coordination request message; a paging message; and a system information transmission command. Claim 6 A method for wireless communication according to claim 3, further comprising the step of receiving a response to the request message from the DU to the CU, wherein the response includes base station Rx-Tx time difference information. Claim 7 A method for wireless communication according to claim 3, further comprising: receiving a message including configured packet data convergence protocol (PDCP) replication function and configured grant (CG) type information by the wireless device; and activating the replication function based on retransmission scheduling information by the wireless device. Claim 8 A method for wireless communication according to claim 7, wherein the activation is performed independently by the wireless device during uplink transmission, and the message is received by the wireless device from the base station. Claim 9 A method for wireless communication according to claim 8, further comprising the step of receiving an activation message for activating the CG by the wireless device, wherein the activation message comprises predefined Downlink Communication Information (DCI) including an indication for activating the CG. Claim 10 A method for wireless communication according to claim 8, wherein the PDCP replication function further comprises configurations for a plurality of radio link control (RLC) entities, and the RLC entities are configured for the wireless device for the activation. Claim 11 A method for wireless communication according to claim 9, wherein the CG type information includes a CG type that does not require activation or a CG type that requires activation by the predefined DCI. Claim 12 A method for wireless communication according to claim 7, wherein the message includes a radio resource control (RRC) message, and the radio resource control (RRC) message includes at least one of RRCReestablishment, RRCReconfiguration, RRCResume, RRCReject, and RRCSetup. Claim 13 A method for wireless communication according to claim 1, further comprising: a step of receiving a first status indication information from the base station to the wireless device after retransmitting a first packet that was subject to transmission failure; and a step of performing a status handover after receiving the first status indication information. Claim 14 A method for wireless communication according to claim 13, wherein the first status indication information indicates whether the retransmission of the first packet was successful, and comprises at least one of an acknowledgment of successful retransmission of the first packet, a keep survival time state indication when the retransmission is not successful, an exit survival time state indication when the retransmission is successful, and a non-acknowledgment of the retransmission. Claim 15 A method for wireless communication according to claim 13, further comprising: a step of transmitting a second packet transmission to the base station by the wireless device when the first status indication information indicates that the retransmission is not received; and a step of receiving a second status indication information for the second packet on any branch of PDCP replication from the base station by the wireless device when the second packet is received. Claim 16 A method for wireless communication according to claim 15, wherein the second status indicator information indicates whether the second packet transmission was successful, and the second status indicator information includes a predefined DCI or MAC control element when the retransmission is not successful. Claim 17 A wireless communication system comprises a base station and a wireless device, wherein the base station and the wireless device comprise one or more processors and one or more storage devices that store instructions that cause the wireless communication system to perform an operation when executed by the one or more processors, and the operation comprises transmitting an EHC parameter indicating the maximum number of downlink (DL) Ethernet header compression (EHC) contexts supported by the wireless device to a CU-UP among a plurality of CU user planes (CU-UP) of the base station from a central unit control plane (CU-CP) of the base station, and the wireless device is configured to communicate with the plurality of CU-UPs; the CU-CP corresponds to the plurality of CU-UPs and knows the maximum number of EHC contexts supported by the wireless device and the maximum number of uplink EHC contexts supported by each data radio bearer (DRB) on the wireless device; A wireless communication system in which the maximum number of downlink EHC contexts supported by the wireless device for each of the plurality of CU-UPs is determined by the CU-CP based on both the maximum number of uplink EHC contexts supported on each DRB and the maximum number of EHC contexts supported by the wireless device. Claim 18 A wireless communication system according to claim 17, wherein the maximum number of EHC contexts supported by the wireless device is the sum of the maximum number of downlink (DL) EHC contexts supported by the wireless device and the maximum number of uplink (UL) EHC contexts supported by the wireless device. Claim 19 A wireless communication system according to claim 17, wherein the above operation further includes the operation of transmitting a request message requesting base station receive-transmit (Rx-Tx) time difference information from the CU of the base station to the distribution unit (DU). Claim 20 A wireless communication system according to claim 19, wherein the base station Rx-Tx time difference information is used by the wireless device to perform propagation delay compensation (PDC). Claim 21 delete Claim 22 delete Claim 23 delete Claim 24 delete Claim 25 delete Claim 26 delete Claim 27 delete Claim 28 delete Claim 29 delete

Images