Lifetime for relaxation of quality of service requirements
By introducing the combination of survival time parameters and packet delay budget, the service quality reliability requirements in 5G wireless communication systems are relaxed, the needs of high-performance use cases are solved, and spectral efficiency and system performance are improved.
Patent Information
- Application Number
- CN202080104441.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-07-31
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2040-07-31
AI Technical Summary
In 5G wireless communication systems, strict quality of service (QoS) requirements lead to high reliability requirements, which makes it difficult to meet the needs of high-performance use cases in some cases, especially in terms of capacity, energy consumption, and spectrum efficiency.
Introducing time-of-survival parameters to relax reliability requirements for quality of service and adjust communication resource configuration by combining with packet delay budget (PDB) or retransmission times to allow reconfiguration between wireless devices and access nodes Connect to improve spectrum efficiency.
By relaxing certain requirements for service quality, the ability to communicate at low latency and high reliability in 5G wireless communication systems is achieved, and the ability to support high-performance use cases is improved, while reducing equipment costs and energy consumption.
Smart Images

Figure CN116097736B_ABST
Abstract
Description
Technical Field
[0001] The present invention is generally directed to wireless communications. Background Art
[0002] Mobile communication technology is driving the world towards an increasingly connected and networked society. The rapid growth of mobile communications and technological advances have led to greater demand for capacity and connectivity. Other aspects, such as energy consumption, equipment cost, spectrum efficiency and latency are also important to meet the needs of various communication scenarios. Various technologies are being discussed, including new methods to provide higher quality of service, longer battery life and improved performance. Summary of the invention
[0003] Among other things, the present invention describes techniques for using a time-to-live parameter that can be used by embodiments to relax quality of service (QoS) reliability requirements in communication services and to reconfigure or change existing connections based on conditions associated with the time-to-live.
[0004] In one example aspect, a wireless communication method is disclosed. The method includes triggering, by a wireless device, a report to a radio access node based on a condition of a time-to-live associated with a communication service. The time-to-live indicates the amount of time an application of the communication service can continue without receiving any expected messages. The time-to-live may indicate the number of consecutive erroneously received or lost packets.
[0005] In another example aspect, a method of wireless communication is disclosed. The method includes receiving, by a radio access node, a report from a wireless device based on a condition associated with a time to live associated with a communication service.
[0006] In another exemplary aspect, a communication device is disclosed, wherein the device includes a processor configured to implement the above method.
[0007] In yet another example aspect, a computer program storage medium is disclosed. The computer program storage medium includes code stored thereon. When the code is executed by a processor, the processor implements the described method.
[0008] These and other aspects are described in this document. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Figure 1 An exemplary scenario for using time to live in accordance with one or more embodiments of the present technology is shown.
[0010] Figure 2 is a flow chart of a method for wireless communication in accordance with one or more embodiments of the present technology.
[0011] Figure 3is a flow chart of another method for wireless communication in accordance with one or more embodiments of the present technology.
[0012] Figure 4 An exemplary scenario is shown in which a packet delay budget (PDB) is used in conjunction with a time to live according to one or more embodiments of the present application.
[0013] Figure 5 Another exemplary scenario in which PDB is used in conjunction with the survival time according to one or more embodiments of the present application is shown.
[0014] Figure 6 An exemplary scenario is shown in which a radio link control (RLC) negative acknowledgement (NACK) is used in conjunction with a time to live according to one or more embodiments of the present application.
[0015] Figure 7 Another exemplary scenario in which RLC NACK is used in conjunction with a life time according to one or more embodiments of the present application is shown.
[0016] Figure 8 An exemplary signaling sequence for uplink data packet transmission according to one or more embodiments of the present technology is shown.
[0017] Fig. 9 An exemplary signaling sequence for uplink data packet transmission according to one or more embodiments of the present technology is shown.
[0018] Fig.10 An exemplary signaling sequence for cell reselection according to one or more embodiments of the present technology is shown.
[0019] Fig.11 An exemplary signaling sequence for logical channel switching according to one or more embodiments of the present technology is shown.
[0020] Fig.12 Another exemplary signaling sequence for logical channel switching according to one or more embodiments of the present technology is shown.
[0021] Fig.13 An example of a wireless communication system is shown in which techniques according to one or more embodiments of the present technology can be applied.
[0022] Fig.14 is a block diagram representation of a portion of a radio station in accordance with one or more embodiments of the present technology that may be applied. DETAILED DESCRIPTION
[0023] The section headings used in this disclosure are intended only to improve readability and do not limit the scope of the embodiments and techniques disclosed in each section to that section. Certain features are described using examples of fifth generation (5G) wireless protocols. However, the applicability of the disclosed techniques is not limited to 5G wireless systems.
[0024] Developments in wireless communication technology have enabled the low-latency, high-reliability communication (URLLC) capabilities of 5G wireless systems, which allow operators and enterprises to address high-performance use cases (such as industrial automation). However, the strict requirements for URLLC also bring challenges, and it is desirable to relax such requirements in some cases. In order to relax certain quality of service (QoS) requirements on reliability, a parameter called lifetime has been introduced to the application layer. For example, the lifetime can be the amount of time that an application for a communication service can continue without any expected messages. In other words, the lifetime is the time period that is tolerable for packet data service packet loss. The lifetime can be expressed as a time period or the maximum number of consecutive erroneous receptions or lost messages (for example, for periodic / cyclic traffic).
[0025] Figure 1 An exemplary scenario 100 for using time to live according to one or more embodiments of the present technology is shown. Figure 1 As shown, the source application 101 sends a data packet to the target application 103 through a 5G system (5GS) in a deterministic communication (e.g., periodic or aperiodic) with end-to-end latency and delivery interval. For example, messages from the source application need to reach the target application in a timely manner. The target application only accepts undamaged messages. The target application can start a timer for its function (e.g., an automation function). After the timer expires, the communication service for the function is declared "unavailable". As long as the message is delivered successfully (e.g., timely and undamaged) within the lifetime, message loss within the lifetime is tolerable. Therefore, the QoS requirements for reliability can be relaxed by using the lifetime.
[0026] The present invention discloses various techniques that can be implemented in a wireless communication system (e.g., on an access node or on a base station side) to effectively utilize the survival time, for example, based on combining the survival time with a packet delay budget (PDB) or the number of retransmissions allowed for a data packet. The disclosed techniques allow an access node or a base station to perform efficient resource allocation, such as improving spectrum efficiency by reducing modulation and coding schemes or intentionally discarding certain messages that do not affect QoS requirements. The disclosed techniques also allow a base station or a user equipment (UE) to initiate a connection reconfiguration, cell reselection, and / or packet data convergence protocol (PDCP) duplication if the current connection fails to meet the relaxed QoS requirements indicated by the survival time.
[0027] Figure 2 2 is a flow chart of a method 200 for wireless communication according to one or more embodiments of the present technology. The method 200 includes, at operation 210, triggering a report to a radio access node by a wireless device based on a condition of a lifetime associated with a communication service. The lifetime represents the amount of time that an application of a communication service can continue without receiving any expected messages. The lifetime may indicate the number of consecutive erroneous receptions or lost packets.
[0028] In some embodiments, determining the time to live includes monitoring a PDB associated with the radio access node, which will be discussed in detail in embodiments 2 and 3. Here, the PDB indicates an upper limit on the delay allowed by the data packet.
[0029] In some embodiments, determining the survival time includes monitoring a maximum number of retransmissions received by a data packet, which will be discussed in detail in Examples 4 and 5. In some embodiments, the method further includes determining a correlation between the currently transmitted data packet and other data packets based on data packet headers in previous data packets.
[0030] In some embodiments, a time-to-live counter is used to represent the time-to-live, and the condition provides for triggering a report if the time-to-live counter reaches or exceeds a threshold. In some embodiments, a time-to-live timer is used to represent the time-to-live, and the condition provides for triggering a report if the time-to-live timer expires or the time-to-live timer reaches or exceeds a threshold. In some embodiments, the threshold comprises at least one of: (1) a value of 1 (e.g., each time the counter is incremented), (2) a value defined by the wireless device, (3) an allowable number of consecutive packet losses, or (4) a percentage value. In some embodiments, the method includes receiving, by the wireless device, the threshold from a radio access node.
[0031] In some embodiments, the report includes at least one of the following information: a service quality improvement indication associated with the lifetime, a performance indicator associated with the lifetime, a status indication associated with the lifetime, a counter value associated with the lifetime, a service type for the communication service, a request associated with the lifetime, a message associated with the lifetime, or a timer value associated with the lifetime.
[0032] In some embodiments, the method includes triggering, by the wireless device, a cell reselection procedure based on a condition associated with the lifetime. In some embodiments, the method includes triggering, by the wireless device, activation of a PDCP duplication procedure based on a condition associated with the lifetime. These features will be discussed in detail in Example 8.
[0033] 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 a condition associated with the survival time. In some embodiments, the method includes switching, by the wireless device, the first priority of the current logical channel to the second priority based on a 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 9 and 10.
[0034] Figure 3 3 is a flow chart of a method 300 for wireless communication according to one or more embodiments of the present technology. The method 300 includes, at operation 310, receiving, by a radio access node, a report from a wireless device based on a condition associated with a time to live related to a communication service. The time to live indicates the amount of time that an application of a communication service can continue without receiving any expected messages. The time to live may indicate the number of consecutive erroneous receptions or lost packets.
[0035] 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 2 and 3. Here, the PDB indicates an upper limit on the delay allowed by the data packet. In some embodiments, the survival time is determined based on the data packet retransmitted to a maximum number of retransmissions, which will be discussed in detail in embodiments 4 and 5.
[0036] In some embodiments, the report includes at least one of the following information: a service quality improvement indication associated with the survival time, a performance indicator associated with the survival time, a status indication associated with the survival time, a counter value associated with the survival time, a service type for a 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 the network node to the wireless device (e.g., as will be discussed in detail in Embodiment 1).
[0037] In some embodiments, the method includes sending, by the radio access node, a reconfiguration indication to the wireless device for reconfiguring a current connection between the wireless device and the radio access node (eg, as will be discussed in detail in Embodiment 6).
[0038] In some embodiments, the method includes transmitting a threshold associated with the survival time from the radio access node to the wireless device. In some embodiments, the method includes triggering, by the radio access node, activation of a packet data convergence protocol (PDCP) replication procedure based on a condition associated with the survival time. In some embodiments, the method includes triggering, by the wireless device, activation of a PDCP replication procedure based on a condition associated with the survival time. These features will be discussed in detail in Example 8.
[0039] In some embodiments, the method includes sending, by the radio access node, a switching indication to the wireless device for switching 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, information about the current logical channel and the second logical channel to the wireless device before sending the switching indication. In some embodiments, the method includes sending, by the radio access node, a switching indication to the wireless device to switch from a first priority level of the current logical channel to a second priority level. In some embodiments, the method includes transmitting, by the radio access node, information about a plurality of priorities of the current logical channel to the wireless device before sending the switching indication. The switching indication / process is further described in embodiments 9 and 10.
[0040] Example 1
[0041] In order to notify the mobile device of the survival time, the access and mobility management function (AMF) in the 5G core network can use the non-access stratum (NAS) protocol data unit (PDU) in the NAS signaling transmitted via the access node / base station. NAS signaling includes at least one of the following: 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. In order to notify the access node / base station of the survival time, the AMF may also include the survival time in the time-sensitive communication assistance information (TSCAI). Table 1 shows an example TSCAI information element (IE) that provides assistance information for a TSC QoS flow in the uplink or downlink direction.
[0042] Table 1 Example TSCAI
[0043] IE / Group Name Presence Periodicity M Burst arrival time O Survival time O
[0044] In periodic communications, data packets may not be transmitted in every transmission cycle / cycle. Therefore, it is necessary to indicate whether there is data transmission in each transmission cycle to reduce the overhead of keeping track of the lifetime. For example, the data packet header may include an indicator (e.g., 1 bit) indicating whether there are any data packets in the next transmission cycle. If no data packets are to be transmitted, one or more access nodes or one or more base stations may skip the operation of a timer or counter related to the lifetime. In some embodiments, if no data packet to be sent is received in each transmission cycle, the operation of the timer or counter related to the lifetime is skipped by default. In some embodiments, the UE may send an empty data packet to indicate that there is no uplink data for transmission (e.g., in uplink transmissions for measuring statistics).
[0045] Example 2
[0046] In some embodiments, the time to live may be used in conjunction with a packet delay budget (PDB). Figure 4 An exemplary scenario 400 is shown in which a PDB is used in conjunction with a time to live according to one or more embodiments of the present application. In this embodiment, the time to live can be implemented as a counter to track the number of unsuccessful transmissions. When transmitting a data packet in the uplink direction (e.g., from a mobile device to a base station / access communication node) or the downlink direction (e.g., from a base station / access communication node to a mobile device), the PDB timer is used to determine whether the data packet is successfully transmitted. The time to live counter is used in conjunction with the PDB timer to determine whether certain data packet losses can be considered tolerable given relaxed QoS reliability requirements. Exemplary operations that can be performed by an access communication node / base station are described below. Note that, Figure 4 An uplink transmission from a user equipment (UE) / mobile device to a gNB / base station is depicted, but the operations apply similarly to downlink transmissions.
[0047] Operation 201, after data in a QoS flow arrives at a UE, the UE starts a timer for a radio access node (RAN) PDB, which may be configured by a gNB. The value of the RAN PDB may be the difference between a reference PDB and a core network (CN) PDB.
[0048] Operation 202a: If the data packet is successfully transmitted before the RAN PDB timer expires, the UE may reset the timer of the RAN PDB and the counter of the lifetime.
[0049] Operation 202b: If the data packet is not successfully transmitted and the RAN PDB timer expires, the UE may increment the time-to-live counter by 1 and reset the RAN PDB timer.
[0050] Operation 203: If the lifetime counter reaches or exceeds the maximum threshold, the UE resets the lifetime counter.
[0051] In addition to the operations described above, the UE may also trigger a report of measurement results based on a lifetime counter. In some embodiments, each time the lifetime counter is incremented (e.g., in operation 202b), the UE triggers a measurement report. In some embodiments, the UE may be configured with an additional threshold. When the lifetime counter reaches or exceeds the threshold, the UE triggers a measurement report. For example, the UE is configured with an additional threshold Tx=5. When the lifetime counter has a value between [0,4], a measurement report is not triggered. When the lifetime counter reaches 5, the UE triggers a measurement report. In some embodiments, each time the lifetime counter is subsequently incremented (e.g., the value of the lifetime is changed to 6, 7, 8, ...), the UE may start triggering a measurement report. Alternatively, the UE no longer triggers any measurement report until another trigger condition is met. For example, when the lifetime counter reaches or exceeds the maximum threshold (e.g., in operation 203), the UE may trigger a measurement report.
[0052] Example 3
[0053] Figure 5 Another exemplary scenario 500 is shown in which the PDB is used in conjunction with a time to live according to one or more embodiments of the present application. In this embodiment, the time to live can be implemented as a timer. When transmitting a data packet in the uplink direction (e.g., from a mobile device to a base station / access communication node) or the downlink direction (e.g., from a base station / access communication node to a mobile device), the PDB timer is used to determine whether the data packet is successfully transmitted. The time to live timer is used in conjunction with the PDB timer to determine whether certain data packet losses can be considered tolerable given the relaxed QoS reliability requirements. Exemplary operations that can be performed by an access communication node / base station are described below. Note that, Figure 5 Downlink transmissions from a gNB / base station to a user equipment (UE) / mobile device are depicted, but the operations apply similarly to uplink transmissions.
[0054] At operation 301, after data from a QoS flow arrives at the gNB, the gNB starts a RAN PDB timer and a time-to-live timer. The time-to-live timer expires at a preconfigured or predetermined time limit (e.g., in frames, subframes, or milliseconds) associated with a communication cycle.
[0055] Operation 302a: If the data packet is successfully transmitted before the RAN PDB timer expires, the UE may reset two timers: the RAN PDB timer and the Time to Live timer.
[0056] Operation 302b: If the data packet is not successfully transmitted and the RAN PDB timer expires, the UE may reset the RAN PDB timer. The Time to Live timer is not reset and continues to keep track of time.
[0057] Operation 303: If the time-to-live timer expires (e.g., reaches a preconfigured or predetermined time limit), the time-to-live counter is reset by the gNB.
[0058] In addition to the operations described above, the gNB may also trigger the UE to report measurement results based on the lifetime timer. In some embodiments, the gNB may configure an additional threshold for the lifetime timer. When the lifetime timer reaches or exceeds the additional threshold, the measurement report is triggered accordingly. Alternatively, and in addition, when the lifetime timer reaches or exceeds a preconfigured or predetermined time limit (e.g., in operation 303), the measurement report may be triggered.
[0059] Example 4
[0060] In some embodiments, the time to live may be used in conjunction with a negative acknowledgement (NACK) in the radio link control (RLC) layer. Figure 6 An exemplary scenario 600 in which RLC NACK is used in conjunction with a time-to-live according to one or more embodiments of the present disclosure is shown. In this embodiment, the time-to-live may be implemented as a counter to track the number of unsuccessful transmissions.
[0061] One of the most important features of RLC Acknowledged 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. A time-to-live counter is used in conjunction with NACK messages (e.g., the pool mechanism) to determine whether certain packet losses can be considered tolerable given the relaxed QoS reliability requirements. Example operations that can be performed by an access communication node / base station are described below. Note that Figure 6 An uplink transmission from a user equipment (UE) / mobile device to a gNB / base station is depicted, but the operations apply similarly to downlink transmissions.
[0062] Operation 401: The UE transmits a data packet to the gNB.
[0063] Operation 402a: If the UE receives an ACK message including a corresponding sequence number (SN), the UE may reset the time-to-live counter.
[0064] Operation 402b: If the UE receives a NACK message with a corresponding SN from the gNB, the UE continues to send the polling bit in the next data packet and increments the time-to-live counter.
[0065] Operation 403: If the lifetime counter reaches or exceeds the maximum threshold, the UE resets the lifetime counter.
[0066] In addition to the operations described above, the UE may also trigger a report of measurement results based on a lifetime counter. In some embodiments, each time the lifetime counter is incremented (e.g., in operation 402b), the UE triggers a measurement report. In some embodiments, the UE may be configured with an additional threshold. When the lifetime counter reaches or exceeds the threshold, the UE triggers a measurement report. For example, the UE is configured with an additional threshold Tx=5. When the lifetime counter has a value between [0,4], a measurement report is not triggered. When the lifetime counter reaches 5, the UE triggers a measurement report. In some embodiments, each time the lifetime counter is subsequently incremented (e.g., the value of the lifetime is changed to 6, 7, 8, ...), the UE may start triggering a measurement report. Alternatively, the UE no longer triggers any measurement report until another trigger condition is met. For example, when the lifetime counter reaches or exceeds the maximum threshold (e.g., in operation 403), the UE may trigger a measurement report.
[0067] Example 5
[0068] Figure 7 An exemplary scenario 700 is shown in which RLC NACK is used with a life time according to one or more embodiments of the present application. In this embodiment, the life time can be implemented as a timer. The life time timer is used in conjunction with a NACK message (e.g., a pool mechanism) to determine whether certain packet losses can be considered tolerable given relaxed QoS reliability requirements. The following describes exemplary operations that can be performed by an access communication node / base station. Note that, Figure 7 Downlink transmissions from a gNB / base station to a user equipment (UE) / mobile device are depicted, but the operations apply similarly to uplink transmissions.
[0069] Operation 501: The gNB transmits a data packet to the UE and starts a time-to-live timer. The time-to-live timer expires at a preconfigured or predetermined time limit (e.g., in frames, subframes, or milliseconds) associated with a communication cycle.
[0070] Operation 502a: If the gNB receives an ACK message including a corresponding sequence number (SN), the gNB may reset the time-to-live timer.
[0071] Operation 502b: If the gNB receives a NACK message with a corresponding SN from the UE, the gNB continues to send the polling bit in the next data packet. The Time to Live timer is not reset and continues to keep track of time.
[0072] Operation 503: If the time-to-live timer expires (e.g., reaches a preconfigured or predetermined time limit), the time-to-live counter is reset by the gNB.
[0073] In addition to the operations described above, the gNB may also trigger the UE to report measurement results based on the lifetime timer. In some embodiments, the gNB may configure an additional threshold for the lifetime timer. When the lifetime timer reaches or exceeds the additional threshold, the measurement report is triggered accordingly. Alternatively, and in addition, when the lifetime timer reaches or exceeds a preconfigured or predetermined time limit (e.g., in operation 503), the measurement report may be triggered.
[0074] Example 6
[0075] As discussed in Embodiments 2-5, measurement reporting from the UE to the gNB may be triggered when certain conditions with respective lifetimes are met. In addition, based on the measurement reporting, the gNB may initiate changes to the current connection, such as radio resource control (RRC) reconfiguration or activation / deactivation of the packet data convergence protocol (PDCP) duplication functionality. Figure 8 An exemplary signaling sequence 800 for uplink data packet transmission is shown in accordance with one or more embodiments of the present technology.
[0076] Operation 801: AMF may notify the UE of the lifetime in NAS signaling (for example, as described in Embodiment 1). For example, the maximum upper limit of the lifetime (in the form of a counter or timer) may be transmitted to the UE.
[0077] Operation 802: Based on the actual transmission, the UE may trigger a measurement report to the gNB (e.g., as described in Embodiments 2-5). The measurement report may include at least one of the following: a service quality improvement indication associated with the lifetime, a performance indicator associated with the lifetime, a state indication associated with the lifetime, a counter value associated with the lifetime, a service type for the communication service, a request associated with the lifetime, a message associated with the lifetime, or a timer value associated with the lifetime.
[0078] In some embodiments, one or more measurement reports may be included in an uplink control indication (UCI) carried on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). In some embodiments, a logical channel identifier (LCID) may be retained in a media access control (MAC) control element (CE) carried in an uplink shared channel (ULSCH). In some embodiments, the measurement results may be included in an RRC message, such as RRCSystemInfoRequest, RRCSetupRequest, RRCResumeRequest, RRCResumeRequest1, or RRCReestablishmentRequest.
[0079] Operation 803: After the gNB receives the measurement report from the UE, the gNB may initiate an RRC reconfiguration process by sending an RRC reconfiguration request. The reconfiguration request may further update the maximum number of RLC retransmissions (e.g., maxRetxThreshold) and / or activate the PDCP duplication function.
[0080] Operation 804: The UE sends a response message to the gNB indicating that the reconfiguration is complete.
[0081] Operation 805: After the UE completes the reconfiguration, the UE may continue to send measurement reports based on the conditions for subsequent communications (as discussed in Examples 2-5). In some embodiments, the gNB may start a timer to track the number of measurement reports from the UE to determine further actions. For example, if the number of measurement reports triggered when the timer expires is less than a threshold and the channel quality indication reported by the UE is greater than another threshold, the gNB may activate the PDCP duplication function via the MAC layer (e.g., MAC CE) or the physical layer (e.g., DCI signaling). For example, the indication to activate the PDCP duplication function may be sent using semi-persistent scheduling (SPS) or configuration grant (CG) configuration information.
[0082] Example 7
[0083] Fig. 9 An example signaling sequence 900 for uplink data packet transmission in accordance with one or more embodiments of the present technology is shown.
[0084] Operation 901: AMF may notify the UE of the lifetime in NAS signaling (for example, as described in Embodiment 1). For example, the maximum upper limit of the lifetime (in the form of a counter or a timer) may be transmitted to the UE.
[0085] Operation 902: A measurement report may be triggered based on a transmission condition (e.g., as discussed in Embodiments 2-5). Based on the measurement report, the UE activates a packet data convergence protocol (PDCP) duplication function. For example, the UE may activate the PDCP duplication function via a MAC layer (e.g., MAC CE) or a physical layer (e.g., UCI signaling).
[0086] Example 8
[0087] As discussed in Embodiments 2-7, additional thresholds may be configured to enable the UE and / or gNB to trigger measurement reporting or perform subsequent actions such as RRC reconfiguration or PDCP duplication activation / deactivation. The gNB may send the threshold information to the UE via RRC, MAC, or DCI signaling messages. In some embodiments, the threshold information may enable the UE to initiate a cell resection procedure or a PDCP duplication procedure on its own. Fig.10 An exemplary signaling sequence 1000 for cell reselection in accordance with one or more embodiments of the present technique is shown.
[0088] Operation 1001: AMF may notify the UE of the lifetime in NAS signaling (for example, as described in Embodiment 1). For example, the maximum upper limit of the lifetime (in the form of a counter or timer) may be transmitted to the UE.
[0089] Operation 1002: The AMF may also notify the gNB of the lifetime in the TSCAI (e.g., as described in Embodiment 1). The maximum upper limit of the lifetime (in the form of a counter or timer) may be transmitted to the gNB.
[0090] Operation 1003: The gNB configures one or more thresholds and sends the one or more thresholds to the UE via an RRC, MAC, or DCI message. The one or more thresholds may include a threshold for a counter, a threshold for a timer, and / or a threshold for the number of measurement reports used to trigger RRC reconfiguration, cell reselection, or PDCP duplication. In some embodiments, the one or more thresholds may be included in at least one of the following RRC messages: RRCReestablishment, RRCReconfiguration, RRCResume, RRCReject, RRCSetup. In some embodiments, the one or more thresholds may be included in a logical channel identifier (LCID) that is retained in a media access control (MAC) control element (CE).
[0091] Operation 1004: Subsequently, the UE may be triggered to send a measurement report to the gNB based on the transmission conditions (e.g., as discussed in Embodiments 2-5). In some embodiments, if the UE has been configured with a threshold indicating the number of measurement reports for triggering a cell reselection process, the UE is triggered to measure cell attributes in order to initiate a cell reselection process.
[0092] In some embodiments, if the UE has been configured with a threshold indicating the number of measurement reports for triggering the PDCP duplication procedure, the UE is triggered to activate the PDCP duplication procedure when the threshold is met or exceeded.
[0093] Example 9
[0094] In some embodiments, based on the measurement results received from the mobile device / UE, the access node / base station may direct the mobile device / UE to switch to a different logical channel or to a different priority in the same logical channel. Fig.11 An exemplary signaling sequence 1100 for logical channel switching is shown in accordance with one or more embodiments of the present technology.
[0095] Operation 1101: The AMF may notify the gNB of the lifetime in the TSCAI (e.g., as described in Embodiment 1). For example, the maximum upper limit of the lifetime (in the form of a counter or timer) may be transmitted to the gNB.
[0096] Operation 1102: The gNB configures two LCHs with different priorities or one LCH with multiple priorities for the UE through an RRC message. In this example, the UE initially selects to send an uplink data packet on an LCH with a low priority.
[0097] Operation 1103: The gNB determines whether the data packet sent by the UE is successful based on the cell group timing and uplink energy detection configured for the UE. When the life time is about to expire, the gNB may instruct the UE to switch to a high priority LCH to send the uplink data packet in an indication. The indication may be carried in MAC CE or DCI signaling.
[0098] In some embodiments, the gNB may direct the UE to switch to a different priority level in the same LCH for subsequent uplink transmissions.
[0099] Example 10
[0100] Fig.12 Another exemplary signaling sequence 1200 for logical channel switching in accordance with one or more embodiments of the present technology is shown.
[0101] Operation 1201: The AMF may notify the UE of the lifetime in NAS signaling (for example, as described in Embodiment 1). For example, the maximum upper limit of the lifetime (in the form of a counter or a timer) may be transmitted to the UE.
[0102] Operation 1202: Before measuring the lifetime, the gNB configures two LCHs with different priorities or one LCH with multiple priorities for the UE through an RRC message. In this example, the UE initially selects to send an uplink data packet on an LCH with a low priority.
[0103] Operation 1203: The UE transmits a measurement report when certain conditions associated with the lifetime are met (e.g., as discussed in Embodiment 2-5). Based on the measurement report, the UE may initiate a logical channel switching operation (e.g., switching from a low priority channel to a high priority channel) on its own. Alternatively, the gNB may direct the UE to switch to a high priority LCH to send uplink data packets in an indication. The indication may be carried in MAC CE or DCI signaling.
[0104] Fig.13 An example of a wireless communication system 1300 is shown in which techniques according to one or more embodiments of the present technology may be applied. The wireless communication system 1300 may include one or more base stations (BSs) 1305a, 1305b, one or more wireless devices 1310a, 1310b, 1310c, 1310d, and a core network 1325. The base stations 1305a, 1305b may provide wireless services to the wireless devices 1310a, 1310b, 1310c, and 1310d in one or more wireless sectors. In some embodiments, the base stations 1305a, 1305b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors.
[0105] The core network 1325 can communicate with one or more base stations 1305a, 1305b. The core network 1325 provides connections 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 subscribed wireless devices 1310a, 1310b, 1310c and 1310d. The first base station 1305a can provide wireless services based on a first radio access technology, and the second base station 1305b can provide wireless services based on a second radio access technology. Depending on the deployment scenario, base stations 1305a and 1305b can be co-located or can be installed on site separately. Wireless devices 1310a, 1310b, 1310c and 1310d can support a variety of different radio access technologies. The techniques and embodiments described in this document can be implemented by the base stations of the wireless devices described in this document.
[0106] Fig.14 1405 is a block diagram representation of a portion of a radio station according to one or more embodiments of the present technology that can be applied. A radio station 1405, such as a base station or a wireless device (or wireless device), may include a processor electronic device 1410, such as a microprocessor, which implements one or more wireless technologies proposed in this document. The radio station 1405 may include a transceiver electronic device 1415 to send and / or receive wireless signals through one or more communication interfaces (such as antenna 1420). The radio station 1405 may include other communication interfaces for transmitting and receiving data. The radio station 1405 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some embodiments, the processor electronic device 1410 may include at least a portion of the transceiver electronic device 1415. In some embodiments, the radio station 1405 is used to implement at least some of the disclosed technologies, modules, or functions. In some embodiments, the radio station 1405 may be configured to perform the methods described herein.
[0107] It will be understood that the present document discloses techniques that can be embodied in various embodiments to allow access nodes / base stations to perform effective resource allocation using lifetime parameters based on relaxed QoS reliability requirements. If the current connection fails to meet the relaxed QoS requirements as indicated by the lifetime parameters, the disclosed techniques also allow the base station or UE to initiate a process (e.g., connection reconfiguration, cell reselection, or PDCP duplication). The disclosure and other embodiments, modules, and functional operations described in this document can be implemented in digital electronic circuits or computer software, firmware, or hardware (including the structures disclosed in this document and their structural equivalents), or in a combination of one or more of them. The disclosure and other embodiments can be implemented as one or more computer program products, i.e., one or more modules in computer program instructions encoded on a computer-readable medium, for execution by a data processing device or control of the operation of the data processing device. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a material combination that affects a machine-readable propagation signal, or one or more combinations thereof. The term "data processing device" covers all devices, equipment, and machines for processing data, including, for example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the apparatus may also include code that creates an execution environment for the computer program in question, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.A propagated signal is an artificially generated signal, such as a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
[0108] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored as part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single document dedicated to the program in question, or in multiple coordinated documents (e.g., files storing one or more modules, subroutines, or portions of code). A computer program may be deployed on a single computer or on multiple computers located at a single site or distributed across multiple sites and interconnected by a communications network for execution.
[0109] The processes and logic flows described in this document may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating input data and generating output. The processes and logic flows may also be performed by, and the apparatus may also be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
[0110] Processors suitable for executing computer programs include, by way of example, general and special purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include or be operatively coupled to one or more mass storage devices (e.g., magnetic, magneto-optical, or optical disks) for storing data to receive data from or transfer data to or both. However, a computer need not have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, by way of example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CDROM and DVD-ROM disks. The processor and memory may be supplemented by or incorporated into a dedicated logic circuit.
[0111] Although the present invention includes many details, these should not be interpreted as limitations on the scope of any invention or content that may be claimed, but rather as descriptions of features that may be specific to a particular embodiment of a particular invention. Certain features described in the context of a separate embodiment in the present invention may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination. In addition, although features may be described above as working in certain combinations, and even initially claimed as such, in some cases, one or more features from the claimed combination may be deleted from the combination, and the claimed combination may be directed to a variant of a sub-combination or a sub-combination.
[0112] Similarly, while operations are depicted in a particular order in the drawings, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all of the illustrated operations be performed to achieve the desired results. Furthermore, the separation of various system components in the embodiments described in the present invention should not be understood as requiring such separation in all embodiments.
[0113] Only a few implementations and examples are described, and other implementations, enhancements, and variations can be made based on what is described and illustrated in this disclosure.
Claims
1. A method for wireless communication, comprising: receiving, by the wireless device, a message from a radio access node, wherein the message forwards configuration information about a time to live associated with a communication service, wherein the time to live is received by the radio access node from a network node access and mobility management function (AMF) and is included in a time sensitive communication assistance information (TSCAI) information element (IE), wherein the time to live represents an amount of time that an application of the communication service can continue without receiving any expected messages, the time to live indicating a number of consecutive erroneously received or lost data packets; and Reporting to the radio access node is triggered by the wireless device based on a time-to-live condition associated with the communication service.
2. The method according to claim 1, wherein: Determining the time to live comprises monitoring a packet delay budget (PDB) associated with the radio access node, wherein the PDB indicates an upper limit on a delay allowed for a packet.
3. The method according to claim 1, wherein: Determining the lifetime includes monitoring a maximum number of retransmissions received by a data packet.
4. The method according to claim 3, further comprising: Based on the packet headers in the previous packets, a correlation between the currently transmitted packet and other packets is determined.
5. The method according to any one of claims 1 to 4, wherein: The time to live is represented using a time to live counter, and wherein the condition specifies that the report is triggered if the time to live counter reaches or exceeds a threshold.
6. The method according to claim 5, wherein: The threshold value includes at least one of the following: a value 1, a value defined by the wireless device, an allowable number of consecutive data packet losses, and a percentage value.
7. The method according to any one of claims 1 to 4, wherein: The time to live is expressed using a time to live timer, and wherein the condition specifies that the report is triggered if the time to live timer expires or the time to live timer reaches or exceeds a threshold.
8. The method according to claim 7, wherein: The threshold value includes at least one of the following: a value 1, a value defined by the wireless device, an allowable number of consecutive data packet losses, and a percentage value.
9. The method according to claim 6 or 8, comprising: The threshold is received by the wireless device from the radio access node.
10. The method according to any one of claims 1 to 4, wherein: The report includes at least one of the following information: a service quality improvement indication associated with the lifetime, a performance indicator associated with the lifetime, a status indication associated with the lifetime, a counter value associated with the lifetime, a service type for the communication service, a request associated with the lifetime, a message associated with the lifetime, or a timer value associated with the lifetime.
11. The method according to any one of claims 1 to 4, comprising: A cell reselection process is triggered by the wireless device based on the condition associated with the lifetime.
12. The method according to any one of claims 1 to 4, comprising: Activation of a Packet Data Convergence Protocol (PDCP) duplication procedure is triggered by the wireless device based on the condition associated with the lifetime.
13. The method according to any one of claims 1 to 4, comprising: 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 lifetime.
14. The method according to claim 13, comprising: The second priority is selected by the wireless device based on the condition associated with the time to live.
15. The method according to any one of claims 1 to 4, comprising: The wireless device switches a first priority of a current logical channel to a second priority based on the condition associated with the lifetime.
16. The method according to claim 15, comprising: The second priority is selected by the wireless device based on the condition associated with the time to live.
17. A method for wireless communication, comprising: receiving, by the radio access node, time-sensitive communication assistance information TSCAI from a network node access and mobility management function AMF, wherein the TSCAI includes a lifetime associated with a communication service and included in a TSCAI information element IE, wherein the lifetime represents an amount of time that an application of the communication service can continue without receiving any expected message, and the lifetime indicates a number of consecutive erroneously received or lost data packets; forwarding a message from the radio access node to a wireless device, wherein the message includes configuration information regarding a time to live associated with the communication service; and A report is received by the radio access node from the wireless device based on a condition associated with a time to live associated with a communication service.
18. The method according to claim 17, wherein: The time to live is determined based on a packet delay budget PDB associated with the radio access node, the PDB indicating an upper limit on the allowed delay of a data packet.
19. The method according to claim 17, wherein: The survival time is determined based on retransmitting a data packet that reaches a maximum number of retransmissions.
20. A method according to any one of claims 17 to 19, comprising: A reconfiguration indication is sent by the radio access node to the wireless device for reconfiguring a current connection between the wireless device and the radio access node.
21. A method according to any one of claims 17 to 19, comprising: A switching indication is sent by the radio access node to the wireless device for switching from a current logical channel to a second logical channel having a different priority.
22. The method according to claim 21, comprising: Information about the current logical channel and the second logical channel is transmitted by the radio access node to the wireless device before sending the handover indication.
23. A method according to any one of claims 17 to 19, comprising: A switching indication is sent by the radio access node to the wireless device to switch from a first priority to a second priority of a current logical channel.
24. The method according to claim 23, comprising: Information about a plurality of priorities of the current logical channel is transmitted by the radio access node to the wireless device before sending the handover indication.
25. A method according to any one of claims 17 to 19, comprising: A threshold associated with the time to live is transmitted from the radio access node to the wireless device.
26. The method according to any one of claims 17 to 19, wherein: The report includes at least one of the following information: a service quality improvement indicator associated with the lifetime, a performance indicator associated with the lifetime, a status indication associated with the lifetime, a counter value associated with the lifetime, a service type for the communication service, a request associated with the lifetime, a message associated with the lifetime, or a timer value associated with the lifetime.
27. A method according to any one of claims 17 to 19, comprising: Activation of a Packet Data Convergence Protocol (PDCP) duplication procedure is triggered by the radio access node based on the condition associated with the time to live.
28. A communication device, comprising a processor and a memory, wherein the memory stores instructions, and when the instructions are executed by the processor, the processor implements the method according to any one of claims 1 to 27.
29. A computer program product having stored thereon code which, when executed by a processor, causes the processor to carry out the method of any one of claims 1 to 27.
