Autonomous activation of features at a wireless communication device to meet application survival time for consuming communication services

Abstract

This document discloses systems and methods for autonomously activating features at a wireless communication device to satisfy the lifetime of an application consuming a communication service. In one embodiment, a method performed by the wireless communication device includes obtaining a timer associated with the lifetime, the lifetime being the amount of time an application consuming a communication service can continue without expected messages. The method also includes autonomously activating features based on the timer, such features being Packet Data Convergence Protocol (PDCP) packet replication, one or more additional PDCP packet replication tributaries if PDCP packet replication is already activated, or another mechanism to increase the reliability of packet transmission.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of provisional patent application serial number 63 / 062,020, filed on August 6, 2020, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to cellular communication systems, and more specifically, to the lifetime of applications that autonomously activate features at wireless communication devices to ensure the fulfillment of consumer communication services. Background Technology

[0004] Packet replication is a feature defined for fifth-generation (5G) New Radio (NR) to enhance the throughput and reliability of the NR radio access network. Section 16.1.3 of the 3GPP Technical Specification (TS) 38.300 v16.2 describes packet replication.

[0005] Packet replication is performed at the Packet Data Convergence Protocol (PDCP) layer, where original and replicated Protocol Data Units (PDUs) are provided to multiple lower-layer Radio Link Control (RLC) entities for transmission over different carriers. This is possible in dual connectivity (DC) and carrier aggregation (CA) protocol architectures. Both Radio Resource Control (RRC) signaling and Media Access Control (MAC) control elements (CEs) can be used by the NR base station (gNB) to control the activation / deactivation of packet replication in the User Equipment (UE) in the uplink (UL). The PDCP entities that include packet replication are configured for each radio bearer (e.g., for each Data Radio Bearer (DRB)).

[0006] In the 5G Quality of Service (QoS) framework, QoS flows are established within the 5G system and can be mapped to DRBs. A QoS flow is associated with QoS parameters such as the Packet Delay Budget (PDB) associated with a 5G QoS Identifier (5QI). Therefore, the 5G Radio Access Network (RAN) that schedules packets for this QoS flow (mapped to a DRB in the 5G RAN) should deliver the packets according to the associated QoS parameters (e.g., within the associated PDB).

[0007] Another metric discussed in the context of industrial automation communications related to PDBs is the so-called "time to live". According to 3GPP TS 22.104 v17.3, "time to live" is defined as the time an application consuming a communication service can continue without an expected message. Messages are expected at the end of the PDB, and the time to live is the maximum additional time expected after the PDB.

[0008] For Time-Sensitive Communications (TSC) service types (e.g., typical TSC service types in industrial automation communications), 3GPP TS 23.501 v16.5.0 specifies TSC Auxiliary Information (TSCAI) signaling, which can be used to provide the RAN with further information about QoS flow services from the 5G core network. This signaling currently includes information about the UL / Downlink (DL) direction, periodicity, and time of arrival of data bursts in the flow.

[0009] Whether the RAN should also be signaled with the time to live (e.g., as part of TSCAI) and how the RAN can utilize this metric depends on current discussions in 3GPP (as part of Rel-17 work item RP-201310).

[0010] It is currently unclear how the RAN can utilize lifetime metrics to ensure they are met effectively. Specifically, it is unclear how the UE should be configured and / or how the lifetime metric itself should be considered. Summary of the Invention

[0011] This document discloses systems and methods for autonomously activating features at a wireless communication device to meet the lifetime of an application consuming a communication service. In one embodiment, a method performed by the wireless communication device includes obtaining a timer associated with the lifetime, which is the amount of time an application consuming a communication service can continue without expected messages. The method also includes autonomously activating features based on the timer, such as Packet Data Convergence Protocol (PDCP) packet replication, one or more additional PDCP packet replication branches if PDCP packet replication is already activated, or another mechanism to increase the reliability of packet transmission. In this way, spectral efficiency can be provided, for example, by a wireless communication device that autonomously triggers high-reliability transmissions only when lifetime requirements need to be met, rather than always transmitting with high reliability. Furthermore, the additional reliability provided by the autonomous activation of features by the wireless communication device allows applications (e.g., industrial applications) to operate with higher availability.

[0012] In one embodiment, the timer is a PDCP discard timer, and includes an autonomous activation (406) feature based on the timer's autonomous activation feature, which includes an autonomous activation feature when a packet is discarded upon the expiration of the PDCP timer.

[0013] In one embodiment, the timer is a timer specifically designed for activating features, and timer-based autonomous feature activation includes autonomous feature activation upon timer expiration.

[0014] In one embodiment, the PDCP packet replication tributary is a radio link control (RLC) entity to which PDCP replication is activated.

[0015] In one embodiment, the method further includes sending one or more packets using the activated feature.

[0016] In one embodiment, the autonomous activation feature includes: autonomously activating PDCP packet replication or one or more additional PDCP packet replication tributaries. In one embodiment, autonomously activating PDCP packet replication or one or more additional PDCP packet replication tributaries includes: autonomously activating all configured but currently inactive PDCP packet replication tributaries. In another embodiment, autonomously activating PDCP packet replication or one or more additional PDCP packet replication tributaries includes: autonomously activating a subset of all configured but currently inactive PDCP packet replication tributaries. In one embodiment, the subset of all configured but currently inactive PDCP packet replication tributaries includes one or more PDCP packet replication tributaries associated with one or more cell groups other than the cell group to which the existing active RLC entity belongs. In another embodiment, autonomously activating PDCP packet replication or one or more additional PDCP packet replication tributaries includes: continuously activating one or more additional PDCP packet replication tributaries.

[0017] In one embodiment, autonomously activating PDCP packet replication or one or more additional PDCP packet replication branches includes: autonomously activating PDCP packet replication or one or more additional PDCP packet replication branches based on the priority associated with the PDCP packet replication branch.

[0018] In one embodiment, autonomously activating PDCP packet replication or one or more additional PDCP packet replication branches includes: activating PDCP packet replication or one or more additional PDCP packet replication branches based on a predefined or configured number of PDCP packet replication branches to be activated.

[0019] In one embodiment, autonomously activating PDCP packet replication or one or more additional PDCP packet replication tributaries includes: autonomously activating PDCP packet replication using a PDCP packet replication tributary as a fallback for split radio bearer operations.

[0020] In one embodiment, the method further includes: deactivating the activated feature. In one embodiment, deactivating the activated feature includes: deactivating the activated feature in response to signaling from a network node. In another embodiment, deactivating the activated feature includes: deactivating the activated feature in response to the expiration of a timer.

[0021] Corresponding embodiments of wireless communication devices are also disclosed. In one embodiment, a wireless communication device is adapted to obtain a timer related to lifetime, which is the amount of time an application consuming a communication service can continue without expected messages. The wireless communication device is also adapted to activate a timer-based feature, which is PDCP packet replication, one or more additional PDCP packet replication tributaries when PDCP packet replication is already activated, or another mechanism to increase the reliability of packet transmission.

[0022] In one embodiment, a wireless communication device includes one or more transmitters, one or more receivers, and processing circuitry associated with the transmitters and receivers. The processing circuitry is configured to enable the wireless communication device to acquire a timer related to time-to-live (TTL), which is the amount of time an application consuming a communication service can continue without expected messages. The processing circuitry is also configured to enable the wireless communication device to autonomously activate features based on the timer, such features being PDCP packet replication, one or more additional PDCP packet replication tributaries if PDCP packet replication is already activated, or another mechanism to increase the reliability of packet transmission.

[0023] Embodiments of a method performed by a base station are also disclosed. In one embodiment, a method performed by a base station includes providing a timer related to a time-to-live (TTL) of a wireless communication device, the TTL being the amount of time an application consuming a communication service can continue without expected messages. The method also includes providing the wireless communication device with one or more parameters related to an autonomously activated feature at the wireless communication device, which is PDCP packet replication, one or more additional PDCP packet replication tributaries if PDCP packet replication is already activated, or some other mechanism to increase the reliability of packet transmission.

[0024] In one embodiment, the PDCP packet replication branch is an RLC entity, and PDCP replication is activated to this RLC entity.

[0025] In one embodiment, one or more parameters include information identifying one or more PDCP packet replication branches that are to be preferentially used by the wireless communication device for autonomous PDCP activation or autonomous activation of one or more additional PDCP packet replication branches.

[0026] In one embodiment, one or more parameters include information indicating the number of PDCP packet replication tributaries that can be activated by a wireless communication device for autonomous PDCP activation or autonomous activation of one or more additional PDCP packet replication tributaries.

[0027] Corresponding embodiments of the base station are also disclosed. In one embodiment, the base station is adapted to provide a timer related to lifetime to the wireless communication device, the lifetime being the amount of time an application consuming communication services can continue without expected messages. The base station is also adapted to provide the wireless communication device with one or more parameters related to an autonomous activation feature at the wireless communication device, which is PDCP packet replication, one or more additional PDCP packet replication tributaries when PDCP packet replication is already activated, or some other mechanism to increase the reliability of packet transmission.

[0028] In one embodiment, the base station includes processing circuitry configured to provide a timer related to lifetime to the wireless communication device, the lifetime being the amount of time an application consuming a communication service can continue without expected messages. The base station is also adapted to provide the wireless communication device with one or more parameters related to an autonomously activated feature at the wireless communication device, which is PDCP packet replication, one or more additional PDCP packet replication tributaries if PDCP packet replication is already activated, or some other mechanism to increase the reliability of packet transmission. Attached Figure Description

[0029] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate several aspects of this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0030] Figure 1 An example of a cellular communication system that can implement embodiments of the present disclosure is shown;

[0031] Figure 2 and Figure 3 It shows Figure 1 A different representation of an example of a cellular communication system, wherein the cellular communication system is the 3rd Generation Partnership Project (3GPP) 5th generation (5G) system;

[0032] Figure 4 Operation of a wireless communication device (e.g., a user equipment (UE)) and a base station according to at least some embodiments described herein is illustrated;

[0033] Figures 5 to 7 This is a schematic block diagram of an example embodiment of a radio access node that can implement the embodiments of this disclosure;

[0034] Figure 8 and Figure 9 This is a schematic block diagram of an example embodiment of a wireless communication device;

[0035] Figure 10 Example embodiments of a communication system that can implement the embodiments of this disclosure are shown;

[0036] Figure 11 It shows Figure 10 Example embodiments of the host computer, base station, and UE; and

[0037] Figures 12 to 15 It is shown in such as Figure 10 A flowchart of an example embodiment of a method implemented in a communication system such as a communication system. Detailed Implementation

[0038] The embodiments described below provide information that enables those skilled in the art to practice the embodiments and illustrate the best mode for practicing the embodiments. After reading the following description in conjunction with the accompanying drawings, those skilled in the art will understand the concepts of this disclosure and will recognize the applications of these concepts not specifically set forth herein. It should be understood that these concepts and applications fall within the scope of this disclosure.

[0039] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided by way of example only to convey the scope of the subject matter to those skilled in the art.

[0040] Generally, unless explicitly stated and / or implied from the context in which the term is used, all terms used herein shall be interpreted according to their common meaning in the relevant art. Unless otherwise expressly stated, all references to a / an / represented element, device, component, apparatus, step, etc., shall be openly interpreted as referring to at least one instance of an element, device, component, apparatus, step, etc. Unless it is required to explicitly describe a step as occurring after or before another step and / or implicitly imply that a step must occur after or before another step, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will become apparent from the following description.

[0041] Radio node: As used in this article, a “radio node” is a radio access node or wireless communication device.

[0042] Radio Access Node: As used herein, a “radio access node,” “radio network node,” or “radio access network node” is any node in the radio access network (RAN) of a cellular communication network that operates to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to: base stations (e.g., new radio (NR) base stations (gNBs) in 3GPP 5G (5G) NR networks or enhanced or evolved Node Bs (eNBs) in 3GPP Long Term Evolution (LTE) networks), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, home eNBs, etc.), relay nodes, network nodes that implement part of the functions of a base station (e.g., network nodes that implement a gNB central unit (gNB-CU) or a gNB distributed unit (gNB-DU),) or network nodes that implement part of the functions of some other type of radio access node.

[0043] Core Network Node: As used herein, a “core network node” is any type of node in the core network or any node that implements core network functions. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), etc. Some other examples of core network nodes include nodes that implement the following functions: Access and Mobility Management Function (AMF), User Plane Function (UPF), Session Management Function (SMF), Authentication Server Function (AUSF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Function (NF) Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), etc.

[0044] Communication equipment: As used herein, “communication equipment” is any type of device that accesses an access network. Some examples of communication equipment include, but are not limited to: mobile phones, smartphones, sensor devices, instruments, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronic device (e.g., but not limited to, televisions, radios, lighting fixtures, tablet computers, laptop computers, or personal computers PCs). Communication equipment can be portable, handheld, computer-integrated, or vehicle-mounted mobile devices capable of transmitting voice and / or data via wireless or wired connections.

[0045] Wireless communication device: One type of communication device is a wireless communication device, which can be any type of wireless device that accesses a wireless network (e.g., a cellular network) (i.e., is served by a wireless network). Some examples of wireless communication devices include, but are not limited to: User Equipment (UE), Machine-Type Communication (MTC) devices, and Internet of Things (IoT) devices in 3GPP networks. Such wireless communication devices can be or can be integrated into mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronic device (e.g., but not limited to, televisions, radios, lighting fixtures, tablet computers, laptop computers, or PCs). Wireless communication devices can be portable, handheld, computer-integrated, or vehicle-mounted mobile devices capable of transmitting voice and / or data via a wireless connection.

[0046] Network node: As used in this article, a “network node” is any node that is part of the RAN or core network of a cellular communication network / system.

[0047] Note that the descriptions presented herein focus on 3GPP cellular communication systems, and therefore frequently use 3GPP terminology or similar terms. However, the concepts disclosed herein are not limited to 3GPP systems.

[0048] PDCP Packet Replication Tributary: As used herein, “PDCP Packet Replication Tributary” or similar terms refer to a separate carrier or cell, or more specifically, a Radio Link Control (RLC) entity that can be activated for wireless communication devices (e.g., UEs) for purposes such as carrier aggregation or multiple connectivity (e.g., dual connectivity).

[0049] Note that the term “cell” may be used in the description in this article; however, in particular for the 5G NR concept, beams can be used instead of cells, so it is important to note that the concepts described in this article apply equally to both cells and beams.

[0050] Several challenges exist. As mentioned above, it is unclear how 5G RAN (also referred to as Next Generation RAN (NG-RAN) in this article) can leverage lifetime metrics to ensure they are met efficiently. Specifically, it is unclear how UEs should be configured and / or how lifetime metrics themselves should be considered.

[0051] Certain aspects of this disclosure and its embodiments may provide solutions to this or other challenges. This document discloses embodiments of a method in a UE that meets lifetime requirements by triggering high-reliability transmissions as the indicated lifetime approaches. In a particular embodiment, when a PDCP packet is discarded based on a Packet Data Convergence Protocol (PDCP) discard timer, the UE triggers a PDCP packet copy transmission for subsequent packet transmissions.

[0052] Certain embodiments may provide one or more of the following technical advantages. Embodiments of the solutions described herein can increase spectral efficiency by adaptively triggering high-reliability transmissions only when lifetime requirements need to be met, rather than always transmitting with high reliability. Furthermore, the additional reliability triggered by the UE to meet lifetime metrics thus allows applications (e.g., industrial applications) to operate with higher availability.

[0053] Figure 1 An example of a cellular communication system 100 that can implement embodiments of the present disclosure is shown. In the embodiments described herein, the cellular communication system 100 is a 5G system (5GS) including a next-generation RAN (NG-RAN) and a 5G core (5GC); however, the solutions described herein are not limited thereto. In this example, the RAN includes base stations 102-1 and 102-2, which in the 5GS include NR base stations (gNBs) controlling corresponding (macro)cells 104-1 and 104-2 and optional next-generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC). Base stations 102-1 and 102-2 are generally referred to herein collectively as base station 102, and are referred to herein as base station 102, respectively. Similarly, (macro)cells 104-1 and 104-2 are generally referred to herein collectively as (macro)cell 104, and are referred to herein as (macro)cell 104, respectively. The RAN may also include a plurality of low-power nodes 106-1 to 106-4 controlling corresponding small cells 108-1 to 108-4. Low-power nodes 106-1 to 106-4 may be small base stations (e.g., pico or femto base stations) or remote radio head ends (RRHs), etc. It is worth noting that, although not shown, one or more small cells 108-1 to 108-4 may alternatively be provided by base station 102. Low-power nodes 106-1 to 106-4 are generally referred to herein as low-power node 106, and are specifically referred to as low-power node 106. Similarly, small cells 108-1 to 108-4 are generally referred to herein as small cell 108, and are specifically referred to as small cell 108. Cellular communication system 100 also includes a core network 110, which is 5GC in 5GS. Base station 102 (and optionally low-power node 106) is connected to core network 110.

[0054] Base station 102 and low-power node 106 provide services to wireless communication devices 112-1 to 112-5 in corresponding cells 104 and 108. Wireless communication devices 112-1 to 112-5 are generally referred to herein as wireless communication device 112, and are specifically referred to as wireless communication device 112. In the following description, wireless communication device 112 is generally referred to as UE, and is therefore sometimes referred to herein as UE 112, but this disclosure is not limited thereto.

[0055] Figure 2 A wireless communication system represented as a 5G network architecture consisting of core network functions (NFs) is shown, where the interaction between any two NFs is represented by a point-to-point reference point / interface. Figure 2 Can be regarded as Figure 1 A specific implementation of System 100.

[0056] From the access side, Figure 2 The 5G network architecture shown includes multiple UEs 112 connected to RAN 102 or the access network (AN) and AMF200. Typically, R(AN) 102 includes base stations, such as eNBs or gNBs. From the core network side, Figure 2 The 5GC NF shown includes NSSF 202, AUSF 204, UDM 206, AMF 200, SMF 208, PCF 210 and Application Function (AF) 212.

[0057] In the standardization specifications, reference points for the 5G network architecture are used to form detailed call flows. Reference point N1 is defined as carrying signaling between UE 112 and AMF 300. Reference points for connections between AN 102 and AMF 200, and between AN 102 and UPF 214, are defined as N2 and N3, respectively. Reference point N11 exists between AMF 200 and SMF 208, meaning that SMF 208 is at least partially controlled by AMF 200. SMF 208 and UPF 214 use N4, allowing UPF 214 to be configured using control signals generated by SMF 208, and UPF 214 to report its status to SMF 208. Specifically, N9 is the reference point for connections between different UPF 214s, and N14 is the reference point for connections between different AMF 200s. Since PCF 210 applies policies to AMF 200 and SMF 208 respectively, N15 and N7 are defined. AMF 200 requires N12 to perform authentication for UE 112. N8 and N10 are defined because AMF 200 and SMF 208 require UE 112's subscription data.

[0058] The 5GC network is designed to separate UP (User Provider) and CP (Content Provider). In the network, UP carries user services, while CP carries signaling. Figure 2 In this architecture, UPF 214 resides in the UP, while all other NFs (i.e., AMF 200, SMF 208, PCF 210, AF 212, NSSF 202, AUSF 204, and UDM 206) reside in the CP. Separating the UP and CP ensures independent scaling of resources on each plane. It also allows the UPF to be deployed separately from the CP functionality in a distributed manner. In this architecture, the UPF can be deployed very close to the UE to reduce the round-trip time (RTT) between the UE and the data network for some applications requiring low latency.

[0059] The core 5G network architecture is composed of modular functions. For example, AMF 200 and SMF 208 are independent functions within the CP (Content Provider Interface). The separate AMF 200 and SMF 208 allow for independent evolution and scaling. Other CP functions (such as PCF 210 and AUSF 204) can also be separated, such as... Figure 2 As shown. The modular functional design enables the 5GC network to flexibly support a variety of services.

[0060] Each NF interacts directly with another NF. Intermediate functions can be used to route messages from one NF to another. In CP, a set of interactions between two NFs is defined as a service so that it can be reused. This service implementation supports modularity. UP supports interactions such as forwarding operations between different UPFs.

[0061] Figure 3 This illustrates a 5G network architecture that uses service-based interfaces between NFs in the CP, rather than... Figure 2 The point-to-point reference point / interface used in the 5G network architecture. However, the above reference... Figure 2 The NF described corresponds to Figure 3 The NF shown. Services provided by an NF to other authorized NFs can be exposed to authorized NFs through service-based interfaces. Figure 3 In this context, service-based interfaces are represented by the letter "N" followed by the name of the NF. For example, the service-based interface for AMF 200 is Namf, and the service-based interface for SMF208 is Nsmf, and so on. Figure 2 Not shown in Figure 3 The NEF 300 and NRF 302 are mentioned. However, it should be clarified that although in Figure 2 There were no explicit instructions, but Figure 2 All NFs described in the text can be used with... Figure 3 The NEF 300 and NRF 302 interact.

[0062] It can be described in the following way Figure 2 and Figure 3 The diagram illustrates some properties of the NF. The AMF 200 provides UE-based authentication, authorization, mobility management, etc. Even though the UE 112 uses multiple access technologies, it is essentially connected to a single AMF 200 because the AMF 200 is independent of the access technologies. The SMF 208 is responsible for session management and assigns Internet Protocol (IP) addresses to the UE. It also selects and controls the UPF 214 for data transmission. If the UE 112 has multiple sessions, different SMFs 208 can be assigned to each session for individual management and potentially provide different functionalities for each session. The AF 212 provides information about packet flows to the PCF 210, which is responsible for policy control, to support QoS. Based on this information, the PCF 210 determines policies regarding mobility and session management to ensure the proper functioning of the AMF 200 and SMF 208. The AUSF 204 supports UE authentication functions, etc., and therefore stores data used for UE authentication, while the UDM 206 stores the UE 112's subscription data. Data networks (DNs) that are not part of the 5GC network provide internet access or carrier services, etc.

[0063] NF can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualization function instantiated on a suitable platform (e.g., cloud infrastructure).

[0064] Now, a description of some specific embodiments of this disclosure will be provided. According to some embodiments of this disclosure, UE112 proactively activates PDCP replication transmissions based on the expiration of a PDCP discard timer. This is useful, for example, when the PDCP discard timer is configured with a value close to the packet delay budget (PDB) or at least less than the lifetime. When a packet is discarded after this timer expires, and if lifetime considerations are configured for UE112, it is considered the trigger point for PDCP packet replication of subsequent transmissions, because, according to the lifetime, the application must receive subsequent packets in order to "survive." Therefore, those subsequent transmissions should be transmitted with the additional reliability provided by PDCP packet replication.

[0065] In another embodiment, the PDCP packet replication following the aforementioned activation is deactivated again when a deactivation signaling is received from base station 102 (e.g., gNB). In another related embodiment, it is deactivated again after a specific time. For this purpose, a timer can be configured to reactivate PDCP packet replication in UE 112. The timer value can be the lifetime. If the timer is configured, it can be stopped by a PDCP packet replication status command sent from base station 102 (e.g., gNB) via a Media Access Control (MAC) Control Element (CE) or Radio Resource Control (RRC). In one embodiment, the timer is not restarted if the same triggering condition is met, such as the PDCP discard timer expiring. This is useful when the lifetime is a multiple of the configured PDCP discard timer value of the PDB.

[0066] If such a timer is not considered in UE 112, alternatively, the base station (e.g., gNB) implementation can ensure that PDCP packet replication is deactivated again after a specific time (e.g., a specific time after the base station (e.g., gNB) successfully receives packets (e.g., both replicated and original)).

[0067] In one embodiment, UE 112 activates all configured but currently inactive PDCP replication tributaries. In another embodiment, UE 112 is provided with a subset of configured but inactive PDCP replication tributaries, and UE 112 activates all PDCP replication tributaries in that subset. This subset may be configured by the network (e.g., RRC-configured).

[0068] In another embodiment, UE 112 is provided with a list of priority PDCP replication tributaries for potential activation based on the method described above—for cases where more than one replication tributary is available. Tributaries in cell groups other than those associated with the currently active Radio Link Control (RLC) entity can be configured with higher priority. In one embodiment, a replication tributary considered a fallback to a split bearer operation (which can be configured) is considered the priority PDCP replication tributary. This is to achieve better diversity gain by transmitting replication in another cell group, since previous packets that do not meet the delay budget can be transmitted in any cell within the same cell group, and all cells may be in poor coverage. Furthermore, in this embodiment, the number of PDCP replication tributaries to be activated according to the method described above can be configured for UE 112 (which can be less than the maximum number of inactive PDCP replication tributaries).

[0069] In a subsequent embodiment of the preceding embodiment, a UE 112 can continuously activate more PDCP replication tributaries until the maximum number of tributaries that can be activated is reached. For example, after detecting that a packet transmission has expired, the UE 112 activates a tributary, and if the second packet is still not transmitted, the UE 112 activates another tributary. This is particularly useful for use cases where the lifetime can be multiple transmission intervals (e.g., the three shown in Table 5.2-1 of 3GPP TS 22.104).

[0070] In the variant, the expiration of the PDCP discard timer is not considered a trigger, but another timer specifically used for this purpose is considered by UE 112 to trigger the activation of PDCP packet replication.

[0071] In another variant, PDCP replication is not activated based on the timer's expiration; instead, another reliability-enhancing mechanism is activated for subsequent packets. Some examples of other reliability-enhancing mechanisms that can be activated include, but are not limited to, more robust modulation and coding schemes, repetition, or multiple antenna techniques.

[0072] In yet another variant, replication (or a high-reliability scheme) is applied not only to subsequent packets but also to the original packet that triggered replication / reliability activation; for example, the original packet can be retransmitted in a replicated / reliable manner. Simultaneously, replicated / reliable retransmission can also be applied to all other packets following the triggering packet.

[0073] In another scenario, PDCP replication may already be activated for UE 112, for example, by activating two RLC entities for PDCP replication. The above method is applicable to situations where additional RLC entities (e.g., up to two or more as specified in Rel-16) can be further activated based on similar triggering conditions related to lifetime.

[0074] Figure 4 The operation of UE 112 and base station 102 according to at least some of the embodiments described above is illustrated. Note that although this document is in... Figure 4 The description does not repeat all the details of the above embodiments, but it should be understood that all the above details apply to Figure 4 The process. Note that optional steps are indicated by dashed lines / boxes.

[0075] As shown in the figure, UE 112 receives the time to live (TTL) or a timer associated with TTL from base station 102 (step 400). As described above, TTL is the time an application consuming communication services can continue without an expected message. Messages are expected at the end of the PDB, and TTL is the maximum additional time after the expected message in the PDB. As described herein, in one embodiment, a timer associated with TTL is received, wherein the timer is, for example, a PDCP drop timer or a timer specifically for the purpose of autonomously activating features (e.g., PDCP packet replication, additional PDCP replication tributaries, or some other reliability enhancement mechanism). Optionally, UE 112 is configured (e.g., in this example, received from base station 102) to have a list of PDCP replication tributaries to be preferentially used for potential activation by UE 112 (step 402). Each PDCP replication tributary is a separate carrier or cell, or more specifically, an associated RLC entity, which can be activated by UE 112 for, for example, carrier aggregation or multiple connectivity (e.g., dual connectivity). As described above, in one embodiment, replicated tributaries in cell groups other than those associated with the currently active RLC entity are given higher priority for potential activation by UE 112. Note that in one embodiment, PDCP replicated tributaries considered as fallbacks to split bearer operations (which can be configured) are considered priority PDCP replicated tributaries for potential activation by UE 112. In one embodiment, UE 112 is configured (e.g., receiving a configuration message from base station 102 in this example) to have a number of PDCP replicated tributaries to be potentially activated by UE 112 (step 404).

[0076] UE 112 autonomously activates PDCP packet replication based on a trigger (e.g., a trigger related to lifetime), activates additional PDCP replication tributaries, or activates some other reliability enhancement mechanism for subsequent packets (and optionally current packets) (step 406). As described above, in one embodiment, the trigger is the expiration of a PDCP discard timer. In another embodiment, the trigger is the expiration of some other timer (e.g., defined for the purpose of autonomously activating PDCP packet replication, additional PDCP replication tributaries, or some other reliability enhancement mechanism). As described above, regarding the activation of PDCP packet replication, in one embodiment, UE 112 activates all configured but currently inactive PDCP replication tributaries. In another embodiment, UE 112 activates a subset of configured but currently inactive PDCP replication tributaries. This subset can be determined, for example, based on a list of configured PDCP replication tributaries from step 402 and / or the number of PDCP replication tributaries to be configured from step 404. UE 112 uses the activated features to send packets (e.g., subsequent packets) (step 408). As described above, in one embodiment, UE 112 iteratively activates more PDCP replication branches until packet transmission is successful.

[0077] Optionally, UE 112 then deactivates the PDCP packet replication activated in step 406, additional activated PDCP replication tributaries, or other reliability enhancement mechanisms (step 410). As described above, in one embodiment, UE 112 performs this deactivation in response to signaling from base station 102. In another embodiment, UE 112 performs this deactivation based on the expiration of a timer.

[0078] Figure 5This is a schematic block diagram of a radio access node 500 according to some embodiments of the present disclosure. Optional features are indicated by dashed boxes. The radio access node 500 may be, for example, a base station 102 or 106, or a network node implementing all or part of the functions of the base station 102 or gNB described herein. As shown, the radio access node 500 includes a control system 502, which includes one or more processors 504 (e.g., a central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), etc.), a memory 506, and a network interface 508. The one or more processors 504 are also referred to herein as processing circuitry. In addition, the radio access node 500 may include one or more radio units 510, each radio unit 510 including one or more transmitters 512 and one or more receivers 514 coupled to one or more antennas 516. The radio unit 510 may be referred to as radio interface circuitry or part of radio interface circuitry. In some embodiments, the radio unit 510 is external to the control system 502 and is connected to the control system 502 via, for example, a wired connection (e.g., optical fiber). However, in some other embodiments, the radio unit 510 and possibly the antenna 516 are integrated with the control system 502. One or more processors 504 operate to provide one or more functions of the radio access node 500 as described herein (e.g., one or more functions of the base station 102 or other RAN node as described herein). In some embodiments, the functions are implemented as software, for example, stored in memory 506 and executed by one or more processors 504.

[0079] Figure 6 This is a schematic block diagram illustrating a virtualized embodiment of a radio access node 500 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have similar virtualization architectures. Similarly, optional features are indicated by dashed boxes.

[0080] As used herein, a “virtualized” radio access node is an implementation of radio access node 500 in which at least a portion of the functionality of radio access node 500 is implemented as a virtual component (e.g., via a virtual machine executed on a physical processing node in a network). As illustrated, in this example, radio access node 500 may include a control system 502 and / or one or more radio units 510, as described above. Control system 502 may be connected to radio unit 510 via, for example, fiber optic cable. Radio access node 500 includes one or more processing nodes 600, which are coupled to or included in network 602 as part of network 602. If present, control system 502 or radio units are connected to processing node 600 via network 602. Each processing node 600 includes one or more processors 604 (e.g., CPU, ASIC, FPGA, etc.), memory 606, and network interface 608.

[0081] In this example, the functions 610 of the radio access node 500 described herein (e.g., one or more functions of the base station 102 or other RAN nodes as described herein) are implemented at one or more processing nodes 600, or distributed in any desired manner across one or more processing nodes 600 and control system 502 and / or radio unit 510. In some specific embodiments, some or all of the functions 610 of the radio access node 500 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by processing node 600. As those skilled in the art will recognize, additional signaling or communication between processing node 600 and control system 502 is used to perform at least some of the desired functions 610. It is noteworthy that in some embodiments, control system 502 may be omitted, in which case radio unit 510 communicates directly with processing node 600 via a suitable network interface.

[0082] In some embodiments, a computer program including instructions is provided that, when executed by at least one processor, causes the at least one processor to perform one or more functions of the radio access node 500 or a node (e.g., processing node 600) in a virtual environment implementing the function 610 of the radio access node 500 according to any embodiment described herein. In some embodiments, a carrier including the computer program product described above is provided. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0083] Figure 7This is a schematic block diagram of a radio access node 500 according to some other embodiments of the present disclosure. The radio access node 500 includes one or more modules 700, each of which is implemented in software. Modules 700 provide the functionality of the radio access node 500 described herein (e.g., one or more functions of a base station 102 or other RAN node as described herein). This discussion also applies to... Figure 6 The processing node 600, wherein the module 700 may be implemented at one of the processing nodes 600 or distributed across multiple processing nodes 600 and / or distributed across the processing node 600 and the control system 502.

[0084] Figure 8 This is a schematic block diagram of a wireless communication device 800 according to some embodiments of the present disclosure. The wireless communication device 800 may be, for example, a UE 112. As shown, the wireless communication device 800 includes one or more processors 802 (e.g., CPU, ASIC, FPGA, etc.), a memory 804, and one or more transceivers 806, each transceiver 806 including one or more transmitters 808 and one or more receivers 810 coupled to one or more antennas 812. As will be understood by those skilled in the art, the transceiver 806 includes radio front-end circuitry connected to the antenna 812, the radio front-end circuitry being configured to modulate signals transmitted between the antenna 812 and the processor 802. The processor 802 is also referred to herein as processing circuitry. The transceiver 806 is also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 800 described above (e.g., the functionality of the UE 112 described above) may be implemented wholly or partially in software, for example, stored in the memory 804 and executed by the processor 802. Note that the wireless communication device 800 may include... Figure 8 Additional components not shown may include, for example, one or more user interface components (e.g., input / output interfaces including displays, buttons, touchscreens, microphones, speakers, etc., and / or any other components that allow information to be input to and / or output from the wireless communication device 800), power supplies (e.g., batteries and associated power circuitry), etc.

[0085] In some embodiments, a computer program including instructions is provided that, when executed by at least one processor, causes the at least one processor to perform the functions of a wireless communication device 800 according to any embodiment described herein. In some embodiments, a carrier including the computer program product described above is provided. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0086] Figure 9This is a schematic block diagram of a wireless communication device 800 according to some other embodiments of the present disclosure. The wireless communication device 800 includes one or more modules 900, each of which is implemented in software. Modules 900 provide the functionality of the wireless communication device 800 described herein (e.g., the functionality of UE 112 described above).

[0087] Reference Figure 10 According to an embodiment, the communication system includes a telecommunications network 1000 (e.g., a 3GPP-type cellular network), which includes an access network 1002 (e.g., a RAN) and a core network 1004. The access network 1002 includes multiple base stations 1006A, 1006B, and 1006C (e.g., Node B, eNB, gNB, or other types of radio access points (APs)), each defining a corresponding coverage area 1008A, 1008B, or 1008C. Each base station 1006A, 1006B, or 1006C can be connected to the core network 1004 via a wired or wireless connection 1010. A first UE 1012 located in coverage area 1008C is configured to wirelessly connect to or be paged by the corresponding base station 1006C. A second UE 1014 located in coverage area 1008A can wirelessly connect to the corresponding base station 1006A. Although multiple UEs 1012 and 1014 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 1006.

[0088] Telecommunication network 1000 is connected to host computer 1016, which may be implemented as a standalone server, a cloud-based server, a distributed server, or as a processing resource in a server cluster. Host computer 1016 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. Connections 1018 and 1020 between telecommunications network 1000 and host computer 1016 may extend directly from core network 1004 to host computer 1016, or may be made via optional intermediate network 1022. Intermediate network 1022 may be one or more of public, private, or bearer networks; intermediate network 1022 (if present) may be a backbone network or the Internet; specifically, intermediate network 1022 may include two or more subnetworks (not shown).

[0089] Figure 10The communication system as a whole implements the connection between the connected UEs 1012 and 1014 and the host computer 1016. This connection can be described as an over-the-top (OTT) connection 1024. The host computer 1016 and the connected UEs 1012 and 1014 are configured to transmit data and / or signaling via the OTT connection 1024 using the access network 1002, core network 1004, any intermediate network 1022, and possibly other infrastructure (not shown) as intermediaries. The OTT connection 1024 can be transparent in the sense that the participating communication devices traversing the OTT connection 1024 are unaware of the routing of uplink and downlink communications. For example, it may not be necessary to notify the base station 1006 of the past routes of input downlink communications with data originating from the host computer 1016 to be forwarded (e.g., handed over) to the connected UE 1012. Similarly, base station 1006 does not need to be aware of future routes for uplink communication originating from UE 1012 to host computer 1016.

[0090] Now refer to Figure 11 This section describes example implementations of the UE, base station, and host computer discussed in the preceding paragraphs according to embodiments. In communication system 1100, host computer 1102 includes hardware 1104, which includes a communication interface 1106 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of communication system 1100. Host computer 1102 also includes processing circuitry 1108, which may have storage and / or processing capabilities. Specifically, processing circuitry 1108 may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. Host computer 1102 also includes software 1110, which is stored in or accessible by host computer 1102 and executable by processing circuitry 1108. Software 1110 includes host application 1112. Host application 1112 is operable to provide services to a remote user (e.g., UE 1114), which is connected via an OTT connection 1116 terminated at UE 1114 and host computer 1102. When providing services to the remote user, host application 1112 can provide user data sent using OTT connection 1116.

[0091] The communication system 1100 also includes a base station 1118 provided in the telecommunications system. The base station 1118 includes hardware 1120 that enables it to communicate with the host computer 1102 and the UE 1114. Hardware 1120 may include: a communication interface 1122 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 1100; and a radio interface 1124 for establishing and maintaining connections with at least the coverage area served by the base station 1118. Figure 11 The wireless connection 1126 of UE1114 (not shown in the diagram) is used. Communication interface 1122 can be configured to facilitate connection 1128 to host computer 1102. Connection 1128 can be direct, or it can pass through the core network of the telecommunications system (…). Figure 11 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 1120 of base station 1118 also includes processing circuitry 1130, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. Base station 1118 also has software 1132 stored internally or accessible via an external connection.

[0092] The communication system 1100 also includes the previously mentioned UE 1114. The hardware 1134 of UE 1114 may include a radio interface 1136 configured to establish and maintain a wireless connection 1126 with a base station serving the coverage area currently occupied by UE 1114. The hardware 1134 of UE 1114 also includes processing circuitry 1138, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) suitable for executing instructions. UE 1114 also includes software 1140, which is stored in or accessible by UE 1114 and executable by processing circuitry 1138. Software 1140 includes a client application 1142. Client application 1142 is operable to provide services to human or non-human users via UE 1114 with the support of host computer 1102. In host computer 1102, the executing host application 1112 can communicate with the executing client application 1142 via an OTT connection 1116 terminated at UE 1114 and host computer 1102. When providing services to a user, client application 1142 can receive request data from host application 1112 and provide user data in response to the request data. OTT connection 1116 can transmit both request data and user data. Client application 1142 can interact with the user to generate the user data it provides.

[0093] Notice, Figure 11 The host computer 1102, base station 1118, and UE 1114 shown can be respectively connected to Figure 10 The host computer 1016, base stations 1006A, 1006B, and 1006C, and UEs 1012 and 1014 are similar to or identical to each other. That is, the internal workings of these entities can be as follows: Figure 11 As shown, and independently, the surrounding network topology can be Figure 10 The network topology.

[0094] exist Figure 11 The OTT connection 1116 has been abstractly depicted to illustrate communication between host computer 1102 and UE 1114 via base station 1118, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine this route, which can be configured to be hidden from UE 1114, from the service provider operating host computer 1102, or from both. While OTT connection 1116 is active, the network infrastructure can also make decisions to dynamically change the route (e.g., based on load balancing considerations or network reconfiguration).

[0095] The wireless connection 1126 between UE 1114 and base station 1118 is based on the teachings of the embodiments described throughout this disclosure. One or more embodiments in the various embodiments improve the performance of OTT services provided to UE 1114 using OTT connection 1116, wherein wireless connection 1126 forms the final segment of OTT connection 1116. More specifically, the teachings of these embodiments can improve, for example, reliability, thereby providing benefits such as better responsiveness or a better user experience.

[0096] For the purpose of monitoring data rates, latency, and other factors improved in one or more embodiments, a measurement process may be provided. Optional network functions may also be available for reconfiguring the OTT connection 1116 between host computer 1102 and UE 1114 in response to changes in measurement results. The measurement process and / or network functions for reconfiguring the OTT connection 1116 may be implemented using software 1110 and hardware 1104 of host computer 1102, or software 1140 and hardware 1134 of UE 1114, or both. In some embodiments, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 1116 passes; the sensor may participate in the measurement process by providing values ​​of the monitored quantities illustrated above or by providing values ​​of other physical quantities that the software 1110, 1140 may use to calculate or estimate the monitored quantities. Reconfiguration of OTT connection 1116 may include message formatting, retransmission settings, preferred routing, etc.; this reconfiguration does not need to affect base station 1118, and it may be unknown or imperceptible to base station 1118. Such processes and functions may be known and practiced in the art. In a particular embodiment, measurement may involve proprietary UE signaling that facilitates host computer 1102 in measuring throughput, propagation time, latency, etc. This measurement may be implemented as follows: software 1110 and 1140 enable the sending of messages (specifically, empty messages or "fake" messages) using OTT connection 1116 while monitoring propagation time, errors, etc.

[0097] Figure 12 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 10 and Figure 11 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 12 The diagram is referenced. In step 1200, the host computer provides user data. In sub-step 1202 of step 1200 (which may be optional), the host computer provides user data by executing a host application. In step 1204, the host computer initiates a transmission carrying user data to the UE. In step 1206 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1208 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0098] Figure 13This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 10 and Figure 11 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 13 The diagram is referenced. In step 1300 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1302, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, this transmission may be via a base station. In step 1304 (which may be optional), the UE receives the user data carried in the transmission.

[0099] Figure 14 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 10 and Figure 11 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 14 The diagram references [the relevant information]. In step 1400 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1402, the UE provides user data. In sub-step 1404 of step 1400 (which may be optional), the UE provides user data by executing a client application. In sub-step 1406 of step 1402 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in sub-step 1408 (which may be optional). In step 1410 of the method, the host computer receives user data sent from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0100] Figure 15 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be a reference... Figure 10 and Figure 11 The host computer, base station, and UE are described. For the sake of brevity, this section will only include descriptions of... Figure 15The diagram is referenced. In step 1500 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 1502 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 1504 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0101] Any suitable steps, methods, features, functions, or benefits disclosed herein can be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented by processing circuitry, which may include one or more microprocessors or microcontrollers and other digital hardware (including digital signal processors (DSPs), application-specific digital logic, etc.). The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions according to one or an embodiment of this disclosure.

[0102] While the processes in the accompanying drawings illustrate a particular sequence of operations performed in certain embodiments of this disclosure, it should be understood that such sequence is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).

[0103] Some example embodiments of this disclosure are as follows:

[0104] Group A Examples

[0105] Example 1: A method performed by a wireless communication device (112) includes: obtaining (400) a time-to-live, which is the amount of time an application consuming a communication service can continue without expected messages; and autonomously activating (406) a feature based on the time-to-live, which is PDCP packet replication, one or more additional PDCP packet replication branches when PDCP packet replication is already activated, or some other mechanism to increase the reliability of packet transmission.

[0106] Example 2: According to the method described in Example 1, wherein the PDCP group replication branch is an RLC entity, and PDCP replication is activated to the RLC entity.

[0107] Example 3: The method according to Example 1 or 2 further includes: using the activated feature to send (408) one or more packets.

[0108] Example 4: The method according to any one of Examples 1 to 3, wherein autonomous activation (406) includes: autonomous activation (406) in response to a trigger.

[0109] Example 5: According to the method described in Example 4, the trigger is the expiration of the PDCP discard timer.

[0110] Example 6: According to the method described in Example 4, the trigger is the expiration of the timer.

[0111] Example 7: According to the method described in Example 4, the trigger is the expiration of a timer specifically defined for the autonomous activation of the following: PDCP packet replication, one or more additional PDCP packet replication tributaries when PDCP packet replication is already activated, or some other mechanism to increase the reliability of packet transmission.

[0112] Example 8: The method according to any one of Examples 1 to 7, wherein the autonomous activation (406) feature includes: autonomous activation of PDCP packet replication or one or more additional PDCP packet replication branches.

[0113] Example 9: According to the method described in Example 8, wherein autonomously activating PDCP packet replication or one or more additional PDCP packet replication branches includes: autonomously activating all configured but currently inactive PDCP packet replication branches.

[0114] Example 10: According to the method described in Example 8, wherein autonomously activating PDCP packet replication or one or more additional PDCP packet replication branches includes: autonomously activating a subset of all configured but currently inactive PDCP packet replication branches.

[0115] Example 11: According to the method of Example 10, wherein a subset of all configured but currently inactive PDCP packet replication tributaries includes one or more PDCP packet replication tributaries associated with one or more cell groups other than the cell group to which the existing active RLC entity belongs.

[0116] Example 12: The method according to any one of Examples 8 to 11, wherein autonomously activating PDCP packet replication or one or more additional PDCP packet replication branches includes: activating PDCP packet replication or one or more additional PDCP packet replication branches based on the priority associated with the PDCP packet replication branch.

[0117] Example 13: The method according to any one of Examples 8 to 12, wherein autonomously activating PDCP packet replication or one or more additional PDCP packet replication branches includes: activating PDCP packet replication or one or more additional PDCP packet replication branches based on a predefined or configured number of PDCP packet replication branches to be activated.

[0118] Example 14: The method according to any one of Examples 8 to 12, wherein autonomous activation of PDCP packet replication or one or more additional PDCP packet replication branches includes: autonomously activating PDCP packet replication using PDCP packet replication branches as a fallback for split radio bearer operation.

[0119] Example 15: The method according to any one of Examples 1 to 14 further includes: deactivating (410) the activated feature.

[0120] Example 16: According to the method described in Example 15, the feature activated by deactivation (410) includes: deactivating the feature activated by (410) in response to signaling from a network node.

[0121] Example 17: According to the method described in Example 15, the feature activated by deactivation (410) includes: deactivating the feature activated by (410) in response to the expiration of the timer.

[0122] Example 18: The method according to any one of the foregoing embodiments further includes: providing user data; and forwarding the user data to a host computer via transmission to a base station.

[0123] Group B Implementation Examples

[0124] Example 19: A method performed by a base station (102) includes: providing (400) a lifetime to a wireless communication device (112), the lifetime being the amount of time an application consuming a communication service can continue without expected messages; and providing (402-404) one or more parameters related to an autonomously activated feature at the wireless communication device (112), the feature being PDCP packet replication, one or more additional PDCP packet replication tributaries if PDCP packet replication is already activated, or some other mechanism to increase the reliability of packet transmission.

[0125] Example 20: According to the method described in Example 19, wherein the PDCP group replication branch is an RLC entity, and PDCP replication is activated to the RLC entity.

[0126] Example 21: The method according to Example 19 or 20, wherein one or more parameters include information (e.g., a list) identifying one or more PDCP packet replication branches to be preferentially used by the wireless communication device (112) for autonomous PDCP activation or autonomous activation of one or more additional PDCP packet replication branches.

[0127] Example 22: The method according to any one of Examples 19 to 21, wherein one or more parameters include information indicating the number of PDCP packet replication branches that can be activated by the wireless communication device (112) for autonomous PDCP activation or autonomous activation of one or more additional PDCP packet replication branches.

[0128] Example 23: The method according to any one of the foregoing embodiments further includes: obtaining user data; and forwarding the user data to a host computer or wireless communication device.

[0129] Group C Implementation Examples

[0130] Example 24: A wireless communication device includes: a processing circuit configured to perform any step of any of the embodiments in Group A; and a power supply circuit configured to supply power to the wireless communication device.

[0131] Example 25: A base station includes: a processing circuit configured to perform any step of any of the examples in Group B; and a power supply circuit configured to supply power to the base station.

[0132] Example 26: A user equipment (UE) includes: an antenna configured to transmit and receive radio signals; a radio front-end circuit connected to the antenna and the processing circuit, and configured to modulate signals transmitted between the antenna and the processing circuit; a processing circuit configured to perform any step of any of the embodiments in Group A; an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface connected to the processing circuit and configured to output information processed by the processing circuit from the UE; and a battery connected to the processing circuit and configured to power the UE.

[0133] Example 27: A communication system including a host computer, the host computer including: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE); wherein the cellular network includes a base station having a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any step of any of the examples in Group B.

[0134] Example 28: The communication system according to the previous example further includes a base station.

[0135] Example 29: The communication system according to the first two examples further includes a UE, wherein the UE is configured to communicate with a base station.

[0136] Example 30: A communication system according to the preceding three examples, wherein: the processing circuitry of the host computer is configured to execute a host application to provide user data; and the UE includes processing circuitry configured to execute a client application associated with the host application.

[0137] Example 31: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at the host computer; and initiating a transmission carrying the user data to the UE via a cellular network including the base station at the host computer, wherein the base station performs any step of any of the examples in Group B.

[0138] Example 32: The method according to the previous example further includes: transmitting user data at the base station.

[0139] Example 33: According to the method described in the first two examples, in which user data is provided at the host computer by executing a host application, the method further includes: executing a client application associated with the host application at the UE.

[0140] Example 34: A user equipment (UE) configured to communicate with a base station, the UE including a radio interface and processing circuitry configured to perform the methods of the preceding three examples.

[0141] Example 35: A communication system including a host computer, the host computer including: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE); wherein the UE includes a radio interface and processing circuitry, and components of the UE are configured to perform any step of any of the examples in Group A.

[0142] Example 36: The communication system according to the previous example, wherein the cellular network further includes a base station configured to communicate with the UE.

[0143] Example 37: The communication system according to the preceding two examples, wherein: the processing circuitry of the host computer is configured to execute a host application to provide user data; and the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0144] Example 38: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at the host computer; and initiating a transmission carrying the user data to the UE via a cellular network including the base station at the host computer, wherein the UE performs any step of any of the examples in Group A.

[0145] Example 39: The method according to the previous example further includes: receiving user data from the base station at the UE.

[0146] Example 40: A communication system including a host computer, the host computer including: a communication interface configured to receive user data transmitted from a user equipment (UE) to a base station; wherein the UE includes a radio interface and processing circuitry, the processing circuitry of the UE being configured to perform any step of any of the examples in Group A.

[0147] Example 41: The communication system according to the previous example further includes a UE.

[0148] Example 42: The communication system according to the preceding two examples further includes a base station, wherein the base station includes: a radio interface configured to communicate with the UE; and a communication interface configured to forward user data carried in transmissions from the UE to the base station to a host computer.

[0149] Example 43: The communication system according to the first three examples, wherein: the processing circuit of the host computer is configured to execute a host application; and the processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0150] Example 44: A communication system according to the preceding four examples, wherein: the processing circuitry of the host computer is configured to execute a host application to provide requested data; and the processing circuitry of the UE is configured to execute a client application associated with the host application to provide user data in response to the requested data.

[0151] Example 45: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted from the UE to the base station, wherein the UE performs any step of any of the examples in Group A.

[0152] Example 46: The method according to the previous example further includes: providing user data to the base station at the UE.

[0153] Example 47: The method according to the preceding two examples further includes: at the UE, executing a client application to provide user data to be sent; and at the host computer, executing a host application associated with the client application.

[0154] Example 48: The method according to the preceding three examples further includes: executing a client application at the UE; and receiving input data for the client application at the UE, the input data being provided at a host computer by executing a host application associated with the client application; wherein the user data to be sent is provided by the client application in response to the input data.

[0155] Example 49: A communication system including a host computer, the host computer including a communication interface configured to receive user data originating from a user equipment (UE) transmitted to a base station, wherein the base station includes a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any step of any of the examples in Group B.

[0156] Example 50: The communication system according to the previous example further includes a base station.

[0157] Example 51: The communication system according to the first two examples further includes a UE, wherein the UE is configured to communicate with a base station.

[0158] Example 52: A communication system according to the preceding three examples, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0159] Example 53: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: at the host computer, receiving from the base station user data transmitted from the base station that has been received from the UE, wherein the UE performs any step of any of the examples in Group A.

[0160] Example 54: The method according to the previous example further includes: receiving user data from the UE at the base station.

[0161] Example 55: The method described in the preceding two examples further includes: at the base station, initiating the transmission of the received user data to the host computer.

[0162] Those skilled in the art will recognize improvements and modifications to the embodiments of this disclosure. All such improvements and modifications are considered to fall within the scope of the concept disclosed herein.

Claims

1. A method performed by a wireless communication device (112), comprising: Obtain (400) a timer associated with the lifetime, the lifetime being the amount of time an application consuming the communication service can continue without the expected message; as well as Based on the timer self-activation (406) feature, the feature is Packet Data Convergence Protocol (PDCP) packet replication, one or more additional PDCP packet replication tributaries when PDCP packet replication is already activated, or another mechanism to increase the reliability of packet transmission. Wherein, the timer is a PDCP discard timer, and the feature of autonomous activation based on the timer (406) includes: autonomously activating the feature of (406) when discarding packets when the PDCP discard timer expires, and The ability to autonomously activate PDCP packet replication or one or more additional PDCP packet replication branches includes: autonomously activating all configured but currently inactive PDCP packet replication branches.

2. The method of claim 1, wherein, The PDCP discard timer value is configured to be equal to the packet delay budget (PDB) value.

3. The method according to claim 1, wherein, The timer is a timer specifically designed for activating the feature, and autonomously activating the feature based on the timer (406) includes: autonomously activating the feature when the timer expires.

4. The method according to claim 1, wherein, The PDCP packet replication tributary is a radio link control (RLC) entity, and PDCP replication is activated to the RLC entity.

5. The method according to claim 1, further comprising: Use the activated features to send (408) one or more packets.

6. The method according to claim 1, wherein, The features of autonomous activation (406) include: autonomous activation of PDCP packet replication or one or more additional PDCP packet replication branches.

7. The method according to claim 6, wherein, Activating PDCP packet replication or one or more additional PDCP packet replication branches includes: activating a subset of all configured but currently inactive PDCP packet replication branches.

8. The method according to claim 7, wherein, The subset of all configured but currently inactive PDCP packet replication tributaries includes one or more PDCP packet replication tributaries associated with one or more cell groups other than the cell groups to which existing active RLC entities belong.

9. The method according to claim 6, wherein, Autonomous activation of PDCP packet replication or one or more additional PDCP packet replication branches includes: continuously activating one or more additional PDCP packet replication branches.

10. The method according to claim 6, wherein, The autonomous activation of PDCP packet replication or one or more additional PDCP packet replication branches includes: activating PDCP packet replication or one or more additional PDCP packet replication branches based on the priority associated with the PDCP packet replication branch.

11. The method according to claim 6, wherein, The autonomous activation of PDCP packet replication or one or more additional PDCP packet replication branches includes: activating PDCP packet replication or one or more additional PDCP packet replication branches based on a predefined or configured number of PDCP packet replication branches to be activated.

12. The method according to claim 6, wherein, Autonomous activation of PDCP packet replication or one or more additional PDCP packet replication tributaries includes: autonomous activation of PDCP packet replication using a PDCP packet replication tributary that is a fallback operation of split radio bearer operation.

13. The method according to claim 1, further comprising: Deactivate the features activated by (410).

14. The method according to claim 13, wherein, The features activated by deactivation (410) include: deactivating the features activated by (410) in response to signaling from a network node.

15. The method according to claim 13, wherein, The features activated by deactivation (410) include: deactivating the features activated by (410) in response to the expiration of the timer.

16. A wireless communication device (112), comprising: One or more modules (900) are configured as follows: Obtain (400) a timer associated with the lifetime, the lifetime being the amount of time an application consuming the communication service can continue without the expected message; as well as Based on the timer self-activation (406) feature, the feature is Packet Data Convergence Protocol (PDCP) packet replication, one or more additional PDCP packet replication tributaries when PDCP packet replication is already activated, or another mechanism to increase the reliability of packet transmission. Wherein, the timer is a PDCP discard timer, and the feature of autonomous activation based on the timer (406) includes: autonomously activating the feature of (406) when discarding packets when the PDCP discard timer expires, and The ability to autonomously activate PDCP packet replication or one or more additional PDCP packet replication branches includes: autonomously activating all configured but currently inactive PDCP packet replication branches.

17. The wireless communication device (112) according to claim 16, wherein, The one or more modules (900) are also configured to perform the method according to any one of claims 2 to 15.

18. A wireless communication device (112; 800), comprising: One or more transmitters (808); One or more receivers (810); as well as A processing circuit (802), associated with the one or more transmitters (808) and the one or more receivers (810), is configured to cause the wireless communication device (112; 800): Obtain (400) a timer associated with the lifetime, the lifetime being the amount of time an application consuming the communication service can continue without the expected message; as well as Based on the timer self-activation (406) feature, the feature is Packet Data Convergence Protocol (PDCP) packet replication, one or more additional PDCP packet replication tributaries when PDCP packet replication is already activated, or another mechanism to increase the reliability of packet transmission. Wherein, the timer is a PDCP discard timer, and the feature of autonomously activating (406) based on the timer includes: the processing circuit (802) being configured to cause the wireless communication device (112; 800) to autonomously activate (406) the feature when discarding packets upon the expiration of the PDCP discard timer, and The ability to autonomously activate PDCP packet replication or one or more additional PDCP packet replication branches includes: autonomously activating all configured but currently inactive PDCP packet replication branches.

19. The wireless communication device (112) according to claim 18, wherein, The processing circuit (802) is also configured to cause the wireless communication device (112; 800) to perform the method according to any one of claims 2 to 15.

20. A method performed by a base station (102), comprising: Provide (400) a timer related to lifetime to the wireless communication device (112), the lifetime being the amount of time an application consuming the communication service can continue without the expected message; as well as Provide the wireless communication device (112) with one or more parameters (402-404) related to an autonomously activated feature at the wireless communication device (112), the feature being Packet Data Convergence Protocol (PDCP) packet replication, one or more additional PDCP packet replication tributaries when PDCP packet replication is already activated, or some other mechanism to increase the reliability of packet transmission; The timer is a PDCP discard timer, and the autonomous activation of the feature based on the timer includes: autonomously activating the feature when discarding packets upon the expiration of the PDCP discard timer, and The ability to autonomously activate PDCP packet replication or one or more additional PDCP packet replication branches includes: autonomously activating all configured but currently inactive PDCP packet replication branches.

21. The method according to claim 20, wherein, The PDCP packet replication tributary is a radio link control (RLC) entity, and PDCP replication is activated to the RLC entity.

22. The method according to claim 20, wherein, The one or more parameters include information identifying one or more PDCP packet replication branches that are to be preferentially used by the wireless communication device (112) for autonomous PDCP activation or autonomous activation of one or more additional PDCP packet replication branches.

23. The method of claim 20, wherein, The one or more parameters include information indicating the number of PDCP packet replication branches that can be activated by the wireless communication device (112) for autonomous PDCP activation or autonomous activation of one or more additional PDCP packet replication branches.

24. A base station (102), comprising: One or more modules (700) are configured as follows: Provide (400) a timer related to lifetime to the wireless communication device (112), the lifetime being the amount of time an application consuming the communication service can continue without the expected message; as well as Provide the wireless communication device (112) with one or more parameters (402-404) related to an autonomously activated feature at the wireless communication device (112), the feature being Packet Data Convergence Protocol (PDCP) packet replication, one or more additional PDCP packet replication tributaries when PDCP packet replication is already activated, or some other mechanism to increase the reliability of packet transmission; The timer is a PDCP discard timer, and the autonomous activation of the feature based on the timer includes: autonomously activating the feature when discarding packets upon the expiration of the PDCP discard timer, and The ability to autonomously activate PDCP packet replication or one or more additional PDCP packet replication branches includes: autonomously activating all configured but currently inactive PDCP packet replication branches.

25. The base station (102) according to claim 24, wherein, The one or more modules (700) are also configured to perform the method according to any one of claims 21 to 23.

26. A base station (102; 500), comprising: Processing circuit (504; 504), is configured to cause the base station (102; 500): Provide (400) a timer related to lifetime to the wireless communication device (112), the lifetime being the amount of time an application consuming the communication service can continue without the expected message; as well as Provide the wireless communication device (112) with one or more parameters (402-404) related to an autonomously activated feature at the wireless communication device (112), the feature being Packet Data Convergence Protocol (PDCP) packet replication, one or more additional PDCP packet replication tributaries when PDCP packet replication is already activated, or some other mechanism to increase the reliability of packet transmission; The timer is a PDCP discard timer, and the autonomous activation of the feature based on the timer includes: autonomously activating the feature when discarding packets upon the expiration of the PDCP discard timer, and The ability to autonomously activate PDCP packet replication or one or more additional PDCP packet replication branches includes: autonomously activating all configured but currently inactive PDCP packet replication branches.

27. The base station (102; 500) according to claim 26, wherein, The processing circuit (504; 504) is further configured to cause the base station (102; 500) to perform the method according to any one of claims 21 to 23.

Images