Patent Description:
Mobile communication technologies are moving the world toward an increasingly connected and networked society. The rapid growth of mobile communications and advances in technology have led to greater demand for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency are also important to meeting the needs of various communication scenarios. Various techniques, including new ways to provide higher quality of service, longer battery life, and improved performance are being discussed.

<CIT> and 3GPP Draft S2-<NUM> form part of the prior art.

This patent document describes, among other things, techniques that use the survival time parameter that may be used by embodiments to relax Quality of Service (QoS) reliability requirements in communication services and to reconfigure or change existing connections according to conditions associated with the survival time.

In one example aspect, a wireless communication method is disclosed. The method includes receiving, by a wireless device, a message from a radio access node, wherein the message forwards configuration information about a survival time associated with a communication service, wherein the survival time is received by the radio access node from an Access and Mobility Management Function, AMF, and is included in a Time Sensitive Communication Assistance Information, TSCAI, Information Element, IE, wherein the survival time represents an amount of time that an application of the communication service is capable of continuing without receiving any anticipated message, the survival time indicating a number of consecutive incorrectly received or lost packets; and triggering, by the wireless device, a report to the radio access node based upon a condition of the survival time associated with the communication service.

In another example aspect, a wireless communication method is disclosed. The method includes receiving, by a radio access node, Time Sensitive Communication Assistance Information, TSCAI, from an Access and Mobility Management Function, AMF, wherein the TSCAI comprises a survival time associated with a communication service included in an TSCAI Information Element, IE, wherein the survival time represents an amount of time that an application of the communication service is capable of continuing without receiving any anticipated message, the survival time indicating a number of consecutive incorrectly received or lost packets; forwarding a message from the radio access node to a wireless device, wherein the message comprises configuration information about the survival time associated with the communication service; and receiving, by the radio access node, a report from the wireless device based on a condition associated with the survival time associated with the communication service.

In another example aspect, a communication apparatus is disclosed. The apparatus includes a processor that is configured to implement an above-described method.

In yet another example aspect, a computer-program storage medium is disclosed. The computer-program storage medium includes code stored thereon. The code, when executed by a processor, causes the processor to implement a described method.

These, and other, aspects are described in the present document.

Section headings are used in the present document only to improve readability and do not limit scope of the disclosed embodiments and techniques in each section to only that section. Certain features are described using the example of Fifth Generation (<NUM>) wireless protocol. However, applicability of the disclosed techniques is not limited to only <NUM> wireless systems.

Development in wireless communication technologies enables the ultra-reliable low-latency communication (URLLC) capabilities of <NUM> wireless systems, which allow operators and enterprises to address high-performance use cases such as industrial automation. However, stringent requirements for URLLC also impose challenges and in some cases relaxation of such requirements is desirable. To relax certain Quality of Service (QoS) requirements for reliability, a parameter referred to as survival time has been introduced into the application layer. The survival time may be, for example, an amount of time that an application consuming a communication service may continue without any anticipated message. That is, the survival time is a period of time in which losses of packets are tolerable for the packet data service. The survival time can be expressed as a time period or a maximum number of consecutive incorrectly received or lost message(e.g., for periodic/cyclic traffic).

<FIG> illustrates an example scenario <NUM> of using survival time in accordance with one or more embodiments of the present technology. As shown in <FIG>, the source application <NUM> sends packets to the target application <NUM> through the <NUM> System (5GS) in deterministic communication (e.g., periodic or aperiodic) that come with end-to-end latency and transfer interval. For example, a message from the source application needs to arrive in a timely manner at the target application. Only uncorrupted messages are accepted by the target application. The target application can start a timer is for its functions (e.g. an automation function). Upon expiration of the timer, the communication service for that function is declared "unavailable. " Message loss within the survival time is tolerable so long as a message is delivered successfully (e.g., timely and uncorrupted) within the survival time. Thus, the QoS requirement on reliability can be relaxed with the use of the survival time.

This patent document discloses various techniques that can be implemented in wireless communication systems, e.g., on the access node or base station side, to effectively make use of the survival time, e.g., based on combining the survival time with Packet Delay Budget (PDBs) or the number of retransmissions allowed for a packet. The disclosed techniques allow the access nodes or the base stations to perform efficient resource allocation, e.g. increasing spectral efficiency by decreasing modulation and coding scheme or intentional discarding of certain messages that do not affect the QoS requirement. The disclosed techniques also allow either the base station or the User Equipment (UE) to initiate connection reconfiguration, cell reselection, and/or Packet Data Convergence Protocol (PDCP) Duplication should the current connection fails to meet the relaxed QoS requirements as indicated by the survival time.

<FIG> is a flowchart of a method for wireless communication <NUM> in accordance with one or more embodiments of the present technology. The method <NUM> includes, at operation <NUM>, triggering, by a wireless device, a report to a radio access node due to occurrence of a condition of a survival time associated with a communication service. The survival time represents an amount of time an application consuming the communication service is capable of continuing without receiving any anticipated message. The survival time can indicate a number of consecutive incorrectly received or lost packets.

In some embodiments, determining the survival time comprises examining a PDB associated with the radio access node, which will be discussed in detail in Embodiments <NUM> and <NUM>. Here, the PDB indicates an upper limit of a delay suffered by a packet.

In some embodiments, determining the survival time comprises examining a packet retransmitted up to a maximum number of retransmissions, which will be discussed in detail in Embodiments <NUM> and <NUM>. In some embodiments, the method also includes determining, based on a packet header in a previous packet, an association between a currently transmitted packet and other packets.

In some embodiments, the survival time is represented using a survival time counter, and the condition specifies that the report is triggered in case the survival time counter reaches or exceeds a threshold. In some embodiments, the survival time is represented using a survival time timer, and the condition specifies that the report is triggered in case the survival time timer expires, or the survival time timer reaches or exceeds a threshold. In some embodiments, the threshold comprises at least one of: (<NUM>) a value of one (e.g., each time the counter is incremented), (<NUM>) a value defined by the wireless device, (<NUM>) an allowable number of consecutive packet losses, or (<NUM>) a percentage value. In some embodiments, the method includes receiving, by the wireless device, the threshold from the radio access node.

In some embodiments, the report comprises information at least one of: a service quality improvement indicator associated with the survival time, a performance index associated with the survival time, a status indication associated with the survival time, a counter value associated with the survival time, a service identifier for the communication service, a request associated with the survival time, a message associated with the survival time, or a timer value associated with the survival time.

In some embodiments, the method includes triggering, by the wireless device, a cell reselection procedure based on the condition associated with the survival time. In some embodiments, the method includes triggering, by the wireless device, an activation of a PDCP Duplication process based on the condition associated with the survival time. These features will be discussed in detail in Embodiment <NUM>.

In some embodiments, the method includes switching, by the wireless device, from a current logical channel having a first priority to a second logical channel having a second priority based on the condition associated with the survival time. In some embodiments, the method includes switching, by the wireless device, a first priority to a second priority of a current logical channel based on the condition associated with the survival time. In some embodiments, the method includes selecting, by the wireless device, the second priority based on the condition associated with the survival time. These features will be discussed in detail in Embodiments <NUM> and <NUM>.

<FIG> is a flowchart of a method for wireless communication <NUM> in accordance with one or more embodiments of the present technology. The method <NUM> includes, at operation <NUM>, receiving, by a radio access node, a report from a wireless device based on a condition associated with a survival time associated with a communication service. The survival time represents an amount of time an application consuming the communication service is capable of continuing without receiving any anticipated message. The survival time can indicate a number of consecutive incorrectly received or lost packets.

In some embodiments, the survival time is determined based on a Packet Delay Budget (PDB) associated with the radio access node, which will be discussed in detail in Embodiments <NUM> and <NUM>. Here, the PDB indicates an upper limit of a delay suffered by a packet. In some embodiments, the survival time is determined based on a packet retransmitted up to a maximum number of retransmissions, which will be discussed in detail in Embodiments <NUM> and <NUM>.

In some embodiments, the report comprises information at least one of: a service quality improvement indicator associated with the survival time, a performance index associated with the survival time, a status indication associated with the survival time, a counter value associated with the survival time, a service identifier for the communication service, a request associated with the survival time, a message associated with the survival time, or a timer value associated with the survival time. In some embodiments, the method includes forwarding, by the radio access node, configuration information about the survival time from a network node to the wireless device (e.g., as will be discussed in detail in Embodiment <NUM>).

In some embodiments, the method includes transmitting, by the radio access node, a reconfiguration indication to the wireless device to reconfigure a current connection between the wireless device and the radio access node (e.g., as will be discussed in detail in Embodiment <NUM>).

In some embodiments, the method includes transmitting, from the radio access node, a threshold associated with the survival time to the wireless device. In some embodiments, the method includes triggering, by the radio access node, an activation of a Packet Data Convergence Protocol (PDCP) Duplication process based on the condition associated with the survival time. In some embodiments, the method includes triggering, by the wireless device, an activation of a PDCP Duplication process based on the condition associated with the survival time. These features will be discussed in detail in Embodiment <NUM>.

In some embodiments, the method includes transmitting, by the radio access node, a switching indication to the wireless device to switch from a current logical channel to a second logical channel having a different priority. In some embodiments, the method includes transmitting, by the radio access node prior to transmitting the switching indication, information about the current logical channel and the second logical channel to the wireless device. In some embodiments, the method includes transmitting, by the radio access node, a switching indication to the wireless device to switch from a first priority to a second priority of a current logical channel. In some embodiments, the method includes transmitting, by the radio access node prior to transmitting the switching indication, information about multiple priorities of the current logical channel to the wireless device. The switching indication/procedure is further described in Embodiments <NUM> and <NUM>.

To inform the mobile devices of the survival time, the Access and Mobility Management Function (AMF) in the <NUM> core network can use Non-Access-Stratum (NAS) Protocol Data Unit (PDU) in NAS signaling transmitted via the access node/the base station. The NAS signaling includes at least one of: PDU SESSION RESOURCE SETUP REQUEST, PDU SESSION RESOURCE RELEASE COMMAND, PDU SESSION RESOURCE MODIFY REQUEST, INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, INITIAL UE MESSAGE, or DOWNLINK NAS TRANSPORT. To inform the access nodes/base stations of the survival time, the AMF can also include the survival time in Time Sensitive Communication Assistance Information (TSCAI). Table <NUM> shows an example TSCAI information element (IE) that provides assistance information for a TSC QoS flow in the uplink or downlink direction.

In periodic communications, data packets may not be transmitted in every transmission period/cycle. It is thus desirable to indicate whether there is data transmission in each transmission cycle to reduce overhead in keeping track of survival time. For example, the packet header can include an indicator (e.g., <NUM> bit) indicating whether there is any data packet in the next transmission period. The access node(s) or base station(s) can skip operations of timer or counter related to the survival time if no data packet is to be transmitted. In some embodiments, if the packet to be sent is not received in every transmission cycle, operations of timer or counter related to lifetime is skipped by default. In some embodiments, the UE can send empty packets to indicate that there is no uplink data for transmission (e.g., in the uplink transmission of measurement statistics).

In some embodiments, the survival time can be used in conjunction with the Packet Delay Budget (PDB). <FIG> illustrates an example scenario <NUM> in which the PDB is used in conjunction with the survival time in accordance with one or more embodiments of the present application. In this embodiment, the survival time can be implemented as a counter to track the number of unsuccessful transmissions. When a data packet is transmitted either in the uplink direction (e.g., from a mobile device to a base station/an access communication node) or downlink direction (e.g., from a base station/an access communication node to a mobile device), a PDB timer is used to determine whether the packet is successfully transmitted. The survival time counter is used in conjunction with the PDB timer to determine if certain packet loss(es) can be deemed tolerable given the relaxed QoS reliability requirement. Example operations that can be performed by the access communication node/base station are described below. Note that <FIG> depicts uplink transmission from the User Equipment (UE)/mobile device to the gNB/base station, but the operations are similarly applicable to downlink transmissions.

Operation <NUM>: After data in the QoS flow reaches the UE, the UE starts a timer for a Radio Access Node (RAN) PDB, which can be configured by the gNB. The value of RAN PDB can be the difference between a reference PDB and Core Network (CN) PDB.

Operation 202a: If the packet is transmitted successfully before the RAN PDB timer expires, the UE can reset the timer of RAN PDB as well as the counter of survival time.

Operation 202b: If the packet is not transmitted successfully and the RAN PDB timer expires, the UE can increment the survival time counter by one and reset the RAN PDB timer.

Operation <NUM>: If the survival time counter reaches or exceeds a maximum threshold, the survival time counter is reset by the UE.

In addition to the operations described above, the UE can trigger reporting of the measurement results based on the survival time counters. In some embodiments, each time the survival time counter is incremented (e.g., in Operation 202b), the UE triggers a measurement report. In some embodiments, the UE can be configured with an additional threshold. When the survival time counter reaches or exceeds the threshold, the UE triggers a measurement report. For example, the UE is configured with an additional threshold Tx=<NUM>. When the survival time counter has a value between [<NUM>, <NUM>], no measurement report is triggered. When the survival time counter reaches <NUM>, the UE triggers a measurement report. In some embodiments, the UE can start triggering measurement reports each time the survival time counter is incremented subsequently (e.g., value of the survival time is changed to <NUM>, <NUM>, <NUM>,. Alternatively, the UE does not trigger any more measurement reports until another triggering condition is satisfied. For example, the UE can trigger measurement reports when the survival time counter reaches or exceeds the maximum threshold (e.g., in Operation <NUM>).

<FIG> illustrates another example scenario <NUM> in which the PDB is used in conjunction with the survival time in accordance with one or more embodiments of the present application. In this embodiment, the survival time can be implemented as a timer. When a data packet is transmitted either in the uplink direction (e.g., from a mobile device to a base station/an access communication node) or downlink direction (e.g., from a base station/an access communication node to a mobile device), a PDB timer is used to determine whether the packet is successfully transmitted. The survival time timer is used in conjunction with the PDB timer to determine if certain packet loss(es) can be deemed tolerable given the relaxed QoS reliability requirement. Example operations that can be performed by the access communication node/base station are described below. Note that <FIG> depicts downlink transmission from the gNB/base station to the User Equipment (UE)/mobile device, but the operations are similarly applicable to uplink transmissions.

Operation <NUM>: After the data from the QoS flow reaches the gNB, the gNB starts the RAN PDB timer and the survival time timer. The survival time timer expires at a preconfigured or predetermined time limit (e.g., in the unit of frame, subframe, or millisecond) that is related to the communication cycle.

Operation 302a: If the packet is transmitted successfully before the RAN PDB timer expires, the UE can reset both timers: the RAN PDB timer as well as the survival time timer.

Operation 302b: If the packet is not transmitted successfully and the RAN PDB timer expires, the UE can reset the RAN PDB timer. The survival time timer is not reset and continue to keep track of the time.

Operation <NUM>: If the survival time timer expires (e.g., reaches the preconfigured or predetermined time limit), the survival time counter is reset by the gNB.

In addition to the operations described above, the gNB can trigger the UE to report measurement results based on the survival time timer. In some embodiments, the gNB can configure an additional threshold for the survival time timer. When the survival time timer reaches or exceeds the additional threshold, a measurement report is triggered accordingly. Alternatively, and in addition, measurement reports can be triggered when the survival time timer reaches or exceeds the preconfigured or predetermined time limit (e.g., in Operation <NUM>).

In some embodiments, the survival time can be used in conjunction with negative-acknowledgments (NACKs) in Radio Link Control (RLC) layer. <FIG> illustrates an example scenario <NUM> in which the RLC NACK is used in conjunction with the survival time in accordance with one or more embodiments of the present application. In this embodiment, the survival time can be implemented as a counter to track the number of unsuccessful transmissions.

One of the most important features of RLC Acknowledgement Mode (AM) is the polling mechanism for reliable data traffic. The transmitter side sends a pool request, and the receiver side reports its status carrying ACK, NACK etc. The survival time counter is used in conjunction with the NACK messages (e.g., the pooling mechanism) to determine if certain packet loss(es) can be deemed tolerable given the relaxed QoS reliability requirement. Example operations that can be performed by the access communication node/base station are described below. Note that <FIG> depicts uplink transmission from the User Equipment (UE)/mobile device to the gNB/base station, but the operations are similarly applicable to downlink transmissions.

Operation <NUM>: The UE transmits a data packet to the gNB.

Operation 402a: If the UE receives an ACK message that includes the corresponding serial number (SN), the UE can reset the survival time counter.

Operation 402b: If the UE receives a NACK message from the gNB with the corresponding SN, the UE continues to send the polling bit in the next packet and increments the survival time counter.

In addition to the operations described above, the UE can trigger reporting of the measurement results based on the survival time counter. In some embodiments, each time the survival time counter is incremented (e.g., in Operation 402b), the UE triggers a measurement report. In some embodiments, the UE can be configured with an additional threshold. When the survival time counter reaches or exceeds the threshold, the UE triggers a measurement report. For example, the UE is configured with an additional threshold Tx=<NUM>. When the survival time counter has a value between [<NUM>, <NUM>], no measurement report is triggered. When the survival time counter reaches <NUM>, the UE triggers a measurement report. In some embodiments, the UE can start triggering measurement reports each time the survival time counter is subsequently incremented (e.g., value of the survival time is changed to <NUM>, <NUM>, <NUM>,. Alternatively, the UE does not trigger any more measurement reports until another triggering condition is satisfied. For example, the UE can trigger measurement reports when the survival time counter reaches or exceeds the maximum threshold (e.g., in Operation <NUM>).

<FIG> illustrates an example scenario <NUM> in which the RLC NACK is used together with the survival time in accordance with one or more embodiments of the present application. In this embodiment, the survival time can be implemented as a timer. The survival time timer is used in conjunction with the NACK messages (e.g., the pooling mechanism) to determine if certain packet loss(es) can be deemed tolerable given the relaxed QoS reliability requirement. Example operations that can be performed by the access communication node/base station are described below. Note that <FIG> depicts downlink transmissions from the gNB/base station to the User Equipment (UE)/mobile device, but the operations are similarly applicable to uplink transmissions.

Operation <NUM>: The gNB transmits a data packet to the UE and starts the survival time timer. The survival time timer expires at a preconfigured or predetermined time limit (e.g., in the unit of frame, subframe, or millisecond) that is related to the communication cycle.

Operation 502a: If the gNB receives an ACK message that includes the corresponding serial number (SN), the gNB can reset the survival time timer.

Operation 502b: If the gNB receives a NACK message from the UE with the corresponding SN, the gNB continues to send the polling bit in the next packet. The survival time timer is not reset and continue to keep track of the time.

As discussed in Embodiments <NUM>-<NUM>, measurement reports from the UE to the gNB can be triggered when certain conditions with respective the survival time are satisfied. Furthermore, based on the measurements reports, the gNB can initiate changes to the current connection, such as Radio Resource Control (RRC) reconfiguration or activation/deactivation of Packet Data Convergence Protocol (PDCP) duplication function. <FIG> illustrates an example signaling sequence <NUM> for uplink packet transmissions in accordance with one or more embodiments of the present technology.

Operation <NUM>: The AMF can inform the UE of the survival time in a NAS signaling (e.g., as described in Embodiment <NUM>). For example, a maximum upper limit of the survival time (either in the form of a counter or a timer) can be transmitted to the UE.

Operation <NUM>: Based on the actual transmissions, the UE can trigger a measurement report to the gNB (e.g., as described in Embodiments <NUM>-<NUM>). The measurement report cam include at least one of the following: a service quality improvement indicator associated with the survival time, a performance index associated with the survival time, a status indication associated with the survival time, a counter value associated with the survival time, a service identifier for the communication service, a request associated with the survival time, a message associated with the survival time, or a timer value associated with the survival time.

In some embodiments, the measurement report(s) can be included in the Uplink Control Indication (UCI) carried on either the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH). In some embodiments, a logical channel identifier (LCID) can be reserved in the Medium Access Control (MAC) Control Element (CE) that is carried in the Uplink Shared Channel (ULSCH). In some embodiments, the measurement results can be included in an RRC message, such as RRCSystemInfoRequest, RRCSetupRequest, RRCResumeRequest, RRCResumeRequest1, or RRCReestablishmentRequest.

Operation <NUM>: After the gNB receives the measurement report from the UE, the gNB can initiate an RRC reconfiguration process by sending an RRC reconfiguration request. The reconfiguration request can further update the maximum retransmission number of RLC (e.g., maxRetxThreshold) and/or activate PDCP duplication function.

Operation <NUM>: The UE sends a response message to the gNB indicating the completion of the reconfiguration.

Operation <NUM>: After the UE completes the reconfiguration, the UE can continue to send measurement reports based on the conditions of subsequent communications (e.g., as discussed in Embodiments <NUM>-<NUM>). In some embodiments, the gNB can start a timer to track the amount of measurement reports from the UE to determine further actions. For example, if the number of triggered measurement reports is less than a threshold when the timer expires and the channel quality indication reported by the UE is greater than another threshold, the gNB can activate the PDCP duplication function via either MAC layer (e.g., MAC CE) or the physical layer (e.g., DCI signaling). For example, indication of activation of the PDCP duplication function can be sent using Semi-Persistent Scheduling (SPS) or Configured Grant (CG) configuration information.

<FIG> illustrates an example signaling sequence <NUM> for uplink packet transmissions in accordance with one or more embodiments of the present technology.

Operation <NUM>: Measurement reports can be triggered based on the transmission conditions (e.g., as discussed in Embodiments <NUM>-<NUM>). Based on the measurement reports, the UE activate Packet Data Convergence Protocol (PDCP) duplication function. For example, the UE can activate the PDCP duplication function via either MAC layer (e.g., MAC CE) or the physical layer (e.g., UCI signaling).

As discussed in Embodiments <NUM>-<NUM>, additional thresholds can be configured to enable the UE and/or the gNB to trigger measurement reports or perform subsequent actions such as RRC reconfiguration or PDCP duplication activation/deactivation. The gNB can send the threshold information to the UE via RRC, MAC, or DCI signaling messages. In some embodiments, the threshold information can enable the UE to initiate a cell resection procedure or a PDCD duplication process by itself. <FIG> illustrates an example signaling sequence <NUM> for cell reselection in accordance with one or more embodiments of the present technology.

Operation <NUM>: The AMF can also inform the gNB of the survival time in a TSCAI (e.g., as described in Embodiment <NUM>). The maximum upper limit of the survival time (either in the form of a counter or a timer) can be transmitted to the gNB.

Operation <NUM>: The gNB configures the threshold(s) and sends the threshold(s) to UE via RRC, MAC, or DCI messages. The threshold(s) can include a threshold for a counter, a threshold for a timer, and/or a threshold for the number of measurement reports for triggering an RRC reconfiguration, a cell reselection, or a PDCP duplication. In some embodiments, the threshold(s) can be included in at least one of the following RRC messages: RRCReestablishment, RRCReconfiguration, RRCResume, RRCReject, RRCSetup. In some embodiments, the threshold(s) can be included in a logical channel identifier (LCID) that is reserved in the Medium Access Control (MAC) Control Element (CE).

Operation <NUM>: Subsequently, the UE can be triggered to send measurement reports to the gNB based on the transmission conditions (e.g., as discussed in Embodiments <NUM>-<NUM>). In some embodiments, if the UE has been configured with a threshold indicating the number of measurement reports for triggering a cell reselection procedure, the UE is triggered to measure the cell attributes so as to start the cell reselection process.

In some embodiments, if the UE has been configured with a threshold indicating the number of measurement reports for triggering a PDCP duplication process, the UE is triggered to activate the PDCP duplication process when the threshold is met or exceeded.

In some embodiments, based on the measurements results received from the mobile device/UE, the access node/base station can instruct the mobile device/UE to switch to a different logical channel or switch to a different priority in the same logical channel. <FIG> illustrates an example signaling sequence <NUM> for logical channel switching in accordance with one or more embodiments of the present technology.

Operation <NUM>: The AMF can inform the gNB of the survival time in a TSCAI (e.g., as described in Embodiment <NUM>). For example, a maximum upper limit of the survival time (either in the form of a counter or a timer) can be transmitted to the gNB.

Operation <NUM>: The gNB configures two LCHs with different priority or a LCH with multiple priorities for UE through RRC message. In this example, the UE initially chooses to send uplink packet on LCH with low priority.

Operation <NUM>: The gNB determines whether the packets sent by UE are successful based on Cell Group timing and uplink energy detection configured for UE. When the survival time is about to time out, the gNB can instruct the UE to switch to the high priority LCH to send uplink packets in an indication. The indication can be carried in a MAC CE or a DCI signaling.

In some embodiments, the gNB can instruct the UE to switch to a different priority in the same LCH for subsequent uplink transmissions.

<FIG> illustrates another example signaling sequence <NUM> for logical channel switching in accordance with one or more embodiments of the present technology.

Operation <NUM>: Before the measurement of the survival time, the gNB configures two LCHs with different priority or a LCH with multiple priorities for UE through RRC message. In this example, the UE initially chooses to send uplink packet on LCH with low priority.

Operation <NUM>: The UE transmits measurement reports upon certain conditions associated with the survival time are satisfied (e.g., as discussed in Embodiments <NUM>-<NUM>). Based on the measurement reports, the UE can initiate the logical channel switching operation on its own (e.g., switching from low priority channel to high priority channel). Alternatively, the gNB can instruct the UE to switch to the high priority LCH to send uplink packets in an indication. The indication can be carried in a MAC CE or a DCI signaling.

<FIG> shows an example of a wireless communication system <NUM> where techniques in accordance with one or more embodiments of the present technology can be applied. A wireless communication system <NUM> can include one or more base stations (BSs) 1305a, 1305b, one or more wireless devices 1310a, 1310b, 1310c, 1310d, and a core network <NUM>. A base station 1305a, 1305b can provide wireless service to wireless devices 1310a, 1310b, 1310c and 1310d in one or more wireless sectors. In some implementations, a base station 1305a, 1305b includes directional antennas to produce two or more directional beams to provide wireless coverage in different sectors.

The core network <NUM> can communicate with one or more base stations 1305a, 1305b. The core network <NUM> provides connectivity with other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases to store information related to the subscribed wireless devices 1310a, 1310b, 1310c, and 1310d. A first base station 1305a can provide wireless service based on a first radio access technology, whereas a second base station 1305b can provide wireless service based on a second radio access technology. The base stations 1305a and 1305b may be co-located or may be separately installed in the field according to the deployment scenario. The wireless devices 1310a, 1310b, 1310c, and 1310d can support multiple different radio access technologies. The techniques and embodiments described in the present document may be implemented by the base stations of wireless devices described in the present document.

<FIG> is a block diagram representation of a portion of a radio station in accordance with one or more embodiments of the present technology can be applied. A radio station <NUM> such as a base station or a wireless device (or wireless device) can include processor electronics <NUM> such as a microprocessor that implements one or more of the wireless techniques presented in this document. The radio station <NUM> can include transceiver electronics <NUM> to send and/or receive wireless signals over one or more communication interfaces such as antenna <NUM>. The radio station <NUM> can include other communication interfaces for transmitting and receiving data. Radio station <NUM> can include one or more memories (not explicitly shown) configured to store information such as data and/or instructions. In some implementations, the processor electronics <NUM> can include at least a portion of the transceiver electronics <NUM>. In some embodiments, at least some of the disclosed techniques, modules or functions are implemented using the radio station <NUM>. In some embodiments, the radio station <NUM> may be configured to perform the methods described herein.

It will be appreciated that the present document discloses techniques that can be embodied in various embodiments to allow the access nodes/the base stations to perform efficient resource allocation based on relaxed QoS reliability requirement using the survival time parameter. The disclosed techniques also allow either the base station or the UE to initiate procedures (e.g., connection reconfiguration, cell reselection, or PDCP duplication) should the current connection fails to meet the relaxed QoS requirements as indicated by the survival time parameter.

While this patent document contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment.

Claim 1:
A method for wireless communication, comprising:
receiving (<NUM>), by a wireless device, a message from a radio access node, wherein the message forwards configuration information about a survival time associated with a communication service, wherein the survival time is received by the radio access node from an Access and Mobility Management Function, AMF, and is included in a Time Sensitive Communication Assistance Information, TSCAI, Information Element, IE, wherein the survival time represents an amount of time that an application of the communication service is capable of continuing without receiving any anticipated message, the survival time indicating a number of consecutive incorrectly received or lost packets; and
triggering (<NUM>), by the wireless device, a report to the radio access node based upon a condition of the survival time associated with the communication service.