Method and device for processing PDCP replication
By utilizing RLC and PDCP status reporting and signaling mechanisms in the NR side link, the problem of successful delivery and deactivation of PDCP PDU in the relay path is solved, and the reliability and efficiency of data transmission are improved.
Patent Information
- Application Number
- CN202380032559.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-04
- Filing Date
- 2023-03-10
- Publication Date
- 2024-11-15
AI Technical Summary
In the indirect path in the NR side link, the RLC entity and the PDCP entity are not co-located, making it impossible to determine whether the PDCP PDU is successfully delivered, and when PDCP replication is activated, the UE has difficulty in notifying the relevant RLC entity to deactivate signaling.
By receiving RLC status reports or PDCP status reports from the relay UE, we determine whether the PDCP PDU is successfully delivered, and when PDCP replication is activated, signaling mechanisms such as RLC status reports, PDCP status reports, RRC signaling, etc. are used to ensure the success of the PDCP PDU. Transmission and deactivation.
The determination and deactivation of the successful delivery of the PDCP PDU in the NR side line link is realized, which improves the reliability and efficiency of data transmission and ensures the normal operation of PDCP replication in multi-path scenarios.
Smart Images

Figure CN118975384A_ABST
Abstract
Description
Technical Field
[0001] Non-limiting and exemplary embodiments of the present disclosure generally relate to the field of communication technology, and more particularly to methods and apparatus for handling Packet Data Convergence Protocol (PDCP) duplication. Background Art
[0002] This section introduces aspects that may help to better understand the present disclosure. Therefore, the statements in this section should be read in this light and should not be understood as admissions of what is in the prior art or what is outside the prior art.
[0003] In communication networks such as LTE (Long Term Evolution) and NR (New Radio) defined by the 3rd Generation Partnership Project (3GPP), various relay scenarios may exist, such as UE (User Equipment) to Network (NW) relay based on the second layer.
[0004] In addition, packet replication can be used in communication networks such as LTE and NR. When replication is configured for a radio bearer, at least one secondary entity is added to the radio bearer to handle the replicated packets, where the logical channel corresponding to the primary entity is called a primary logical channel and the physical channel corresponding to the secondary entity is called a secondary logical channel. Summary of the invention
[0005] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
[0006] Sidelink (SL) relay is being standardized in 3GPP NR Release 17 (Rel-17), which enables a remote UE to connect to a network node (such as a base station) through a relay UE. During the 3GPP NR Release 17 time period, the remote UE may be in coverage (IC) or out of coverage (OOC). For a remote UE that is in IC and has a direct connection and an indirect connection, the remote UE is only allowed to use a single connection to transmit data. Due to this restriction, it is reasonable and direct for the remote UE to transmit data to the network node using only an indirect connection. Due to this restriction, i.e., the remote UE uses only a single connection for data transmission and reception, it is beneficial to simplify the design work in 3GPP NR Release 17. However, the disadvantage is that the remote UE cannot utilize the second connection, although it is available. In the case of high data volume, it would be very helpful if the remote UE in the IC could utilize the direct connection and the indirect connection to achieve the aggregate data rate on the two connections.
[0007] In the draft for NR Sidelink Relay Enhancements (i.e. 3GPP TSG RAN Meeting #94e, RP-213585, Electronic Meeting, December 6-17, 2021), the following study objectives are defined and will be studied within the 3GPP Release 18 timeframe.
[0008] 3. Study the benefits and potential solutions of multipath support in the following scenarios [RAN2, RAN3] to improve reliability and throughput (e.g., by switching between multiple paths or utilizing multiple paths simultaneously):
[0009] A. The UE connects to the same gNB using one direct path and one indirect path via 1) Layer 2 UE-to-network relay.
[0010] As emphasized in the above objectives, a UE is allowed to connect to the same gNB using both direct and indirect paths via an L2 (Layer 2) UE to Network Relay UE.
[0011] Since one of the purposes of supporting multipathing is to improve reliability, it is straightforward to support packet replication in this case.
[0012] An important function of packet duplication is to delete the duplicated protocol data units (PDUs) at the Packet Data Convergence Protocol (PDCP) layer in situations including the following:
[0013] 1) If successful delivery of a PDCP data PDU is acknowledged by one of the associated AM (Acknowledged Mode) RLC (Radio Link Control) entities,
[0014] 2) If deactivation of PDCP duplication is indicated for a data radio bearer (DRB), or
[0015] 3) If deactivation of PDCP duplication is indicated for at least one associated RLC entity.
[0016] In addition, if the PDCP layer instructs, the UE also needs to delete the SDU of the RLC layer.
[0017] For the case where the UE is configured with both direct and indirect paths and PDCP duplication is enabled for at least one Radio Bearer (RB), all the above procedures require enhancement due to the following observed issues:
[0018] Problem 1: The indirect path contains two hops, where an RLC entity is established at each hop for duplication purposes. Therefore, in this case, it is necessary to study how to determine whether the PDCP PDU has been successfully delivered. It may not be sufficient for the UE to determine only by the RLC status provided by one hop.
[0019] Question 2: In the indirect path, the RLC entity and the PDCP entity are not collocated. In the case where the UE receives signaling indicating deactivation of PDCP duplication of RBs from a network node, such as a gNB, it is also necessary to study how the UE notifies the relevant RLC entity of the signaling.
[0020] Therefore, it is necessary to study the above problems and formulate corresponding solutions.
[0021] In a first aspect of the present disclosure, a method performed by a first UE is provided. The method may include, for an uplink radio bearer that has been activated by packet data convergence protocol (PDCP) duplication, determining that a PDCP protocol data unit (PDU) has been successfully delivered to a network node by a relay UE on a UE-to-network relay path. The method may also include discarding at least one duplicated PDCP PDU on at least one other UE-to-network path.
[0022] In one embodiment, the at least one other UE-to-network path may include at least one of a UE-to-network relay path or a UE-to-network direct path.
[0023] In one embodiment, determining that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path may include: receiving a radio link control (RLC) status report from the relay UE, and determining that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path based on the RLC status report. The RLC status report indicates that the PDCP PDU has been successfully sent to the relay UE in a sidelink.
[0024] In one embodiment, determining that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path may include: receiving a PDCP status report from the network node, and determining that the PDCP PDU has been successfully delivered to the network node on the UE-to-network relay path based on the PDCP status report. The PDCP status report indicates that the PDCP PDU has been successfully received by the network node through the UE-to-network relay path.
[0025] In one embodiment, the PDCP status report can be received from the network node when at least one of the following conditions is met: the upper layer requests PDCP entity re-establishment, the upper layer requests PDCP data recovery, the upper layer requests uplink data switching, the upper layer reconfigures the PDCP entity to release the dual active protocol stack (DAPS) and configures daps-SourceRelease at the upper layer, the upper layer determines that a PDCP status report needs to be triggered, the periodic timer expires, or PDCP duplication has been activated and at least one path of the PDCP duplication is a UE to network relay path.
[0026] In one embodiment, the upper layer may include a radio resource control (RRC) layer.
[0027] In one embodiment, the PDCP status report is received from a network node via a UE-to-network direct path and / or a UE-to-network relay path.
[0028] In one embodiment, determining that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path may include: receiving first signaling from the relay UE, and determining based on the first signaling that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path. The first signaling indicates that the relay UE has received an RLC status report of the PDCP PDU from the network node. The RLC status report indicates that the PDCP PDU has been successfully sent to the network node in the Uu link.
[0029] In one embodiment, determining that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path may include: receiving second signaling from the network node via the UE-to-network direct path, and determining based on the second signaling that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path. The second signaling indicates that the PDCP PDU has been successfully received by the network node through the UE-to-network relay path.
[0030] In one embodiment, the method may further include receiving a third signaling from the network node. The third signaling indicates deactivation of the PDCP duplication of the uplink radio bearer. The method may further include performing at least one of the following operations: deactivating the PDCP duplication of the uplink radio bearer; discarding at least one first duplicate PDCP PDU and / or RLC service data unit (SDU) associated with the uplink radio bearer; or sending a fourth signaling to the relay UE. The fourth signaling instructs the relay UE to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0031] In one embodiment, the at least one second duplicate PDCP PDU and / or RLC SDU may include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from the first UE and stored in at least one sidelink RLC entity, or at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer stored in at least one Uu RLC entity.
[0032] In one embodiment, the method may further include receiving a fifth signaling from the network node. The fifth signaling indicates deactivation of the PDCP duplication of the uplink radio bearer of at least one sidelink RLC entity. The method may further include performing at least one of discarding at least one third duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer of at least one RLC entity; or sending a sixth signaling to the relay UE. The sixth signaling instructs the relay UE to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and at least one RLC entity.
[0033] In one embodiment, at least one fourth replicate PDCP PDU and / or RLC SDU may include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from at least one RLC entity of the first UE and stored in one or more sidelink RLC entities of the relay UE, or include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from at least one RLC entity of the first UE and stored in at least one Uu RLC entity of the relay UE.
[0034] In one embodiment, the fifth signaling may be received from the network node via a UE-to-network relay path or a UE-to-network direct path.
[0035] In one embodiment, the method may further include maintaining a mapping table between Uu PDCP PDUs and sidelink RLC PDUs in the UE-to-network relay path.
[0036] In one embodiment, the mapping table may include at least one of a mapping of a Uu PDCP PDU to one or more PC5 RLC PDUs, or a mapping of one or more Uu PDCP PDUs to PC5 RLC PDUs.
[0037] In one embodiment, the Uu PDCP PDU in the mapping table may be identified by its sequence number (SN) value, while the sidelink RLC PDU may be identified by its SN value.
[0038] In one embodiment, when the Uu PDCP PDU is delivered to the sidelink RLC layer, an entry corresponding to the Uu PDCP PDU may be added to the mapping table, and when the sidelink RLC layer indicates to the Uu PDCP layer that the Uu PDCP PDU has been successfully transmitted to the recipient, or when a timer or counter expires and the Uu PDCP PDU has become invalid, the entry corresponding to the Uu PDCP PDU may be deleted.
[0039] In one embodiment, the signaling between the network node and the first UE may include at least one of RRC signaling, a medium access control (MAC) control element (CE), or layer 1 signaling.
[0040] In one embodiment, the signaling between the relay UE and the first UE may include at least one of RRC signaling, MAC CE, or control PDU of the protocol layer.
[0041] In a second aspect of the present disclosure, a method performed by a relay UE is provided. The method may include receiving a PDCP PDU of an uplink radio bearer from a first UE. The uplink radio bearer has been activated by PDCP duplication. The method also includes sending an indication to the first UE that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path.
[0042] In one embodiment, the PDCP PDU may be delivered to the network node via at least one of a UE-to-network relay path or a UE-to-network direct path.
[0043] In one embodiment, the indication is an RLC status report indicating that the PDCP PDU has been successfully sent to the relay UE in the sidelink.
[0044] In one embodiment, the indication may indicate that the relay UE has received an RLC status report of the PDCP PDU from the network node.
[0045] In one embodiment, the method may further include receiving signaling from the first UE. The signaling instructs the relay UE to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer. The method may further include discarding at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0046] In one embodiment, the at least one second duplicate PDCP PDU and / or RLC SDU may include at least one of the one or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer received from the first UE and stored in at least one sidelink RLC entity, or at least one of the one or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer stored in at least one Uu RLC entity.
[0047] In one embodiment, the method may further include receiving signaling from the first UE. The signaling instructs the relay UE to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and at least one RLC entity. The method may further include discarding at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and at least one RLC entity.
[0048] In one embodiment, at least one fourth duplicate PDCP PDU and / or RLC SDU may include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from at least one RLC entity of the first UE and stored in one or more sidelink RLC entities, or include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from at least one RLC entity of the first UE and stored in at least one Uu RLC entity.
[0049] In one embodiment, the method may further include receiving signaling including an identifier of the first UE from a network node. The signaling indicates discarding duplicate PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer. The method may further include discarding duplicate PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer.
[0050] In one embodiment, the method may further include receiving signaling including an identifier of the first UE from a network node. The signaling indicates deactivating at least one RLC entity of an uplink radio bearer in a UE-to-network relay path. The method may further include deactivating at least one RLC entity of an uplink radio bearer in a UE-to-network relay path.
[0051] In one embodiment, the method may further include maintaining a mapping table between Uu PDCP PDUs and sidelink RLC PDUs in the UE-to-network relay path.
[0052] In one embodiment, the mapping table may include at least one of a mapping of a PC5 RLC PDU to one or more Uu PDCP PDUs, or a mapping of one or more PC5 RLC PDUs to Uu PDCP PDUs.
[0053] In one embodiment, the Uu PDCP PDU in the mapping table may be identified by a sequence number (SN) value of the Uu PDCP PDU, while the sidelink RLC PDU is identified by the SN value of the sidelink RLC PDU, an identifier of an uplink radio bearer, and an identifier of the first UE.
[0054] In one embodiment, the signaling between the network node and the relay UE may include at least one of RRC signaling, a medium access control (MAC) control element (CE), or layer 1 signaling.
[0055] In one embodiment, the signaling between the relay UE and the first UE may include at least one of RRC signaling, MAC CE, or control PDU of the protocol layer.
[0056] In a third aspect of the present disclosure, a method performed by a network node is provided. The method may include: for a downlink radio bearer that has been activated with PDCP duplication, determining that a PDCP PDU has been successfully delivered to a first UE via a relay UE on a UE-to-network relay path. The method may also include discarding at least one duplicated PDCP PDU on at least one other UE-to-network path.
[0057] In one embodiment, the at least one other UE-to-network path may include at least one of a UE-to-network relay path or a UE-to-network direct path.
[0058] In one embodiment, determining that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path may include receiving an RLC status report from the relay UE, and determining that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path based on the RLC status report. The RLC status report indicates that the PDCP PDU has been successfully transmitted to the relay UE in the Uu link.
[0059] In one embodiment, determining that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path may include receiving a PDCP status report from the first UE, and determining that the PDCP PDU has been successfully delivered to the first UE on the UE-to-network relay path based on the PDCP status report. The PDCP status report indicates that the PDCP PDU has been successfully received by the first UE through the UE-to-network relay path.
[0060] In one embodiment, the network node may receive a PDCP status report when at least one of the following conditions is met: the upper layer requests PDCP entity re-establishment, the upper layer requests PDCP data recovery, the upper layer requests downlink data switching, the upper layer reconfigures the PDCP entity to release the dual active protocol stack (DAPS) and configures daps-SourceRelease at the upper layer, the upper layer determines that a PDCP status report needs to be triggered, the periodic timer expires, or PDCP duplication has been activated and at least one path of the PDCP duplication is a UE-to-network relay path.
[0061] In one embodiment, the upper layer may include a radio resource control (RRC) layer.
[0062] In one embodiment, the PDCP status report is received by the network node via a direct path and / or a UE-to-network relay path.
[0063] In one embodiment, determining that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path may include receiving first signaling from the relay UE, and determining based on the first signaling that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path. The first signaling indicates that the relay UE has received an RLC status report of the PDCP PDU from the first UE. The RLC status report indicates that the PDCP PDU has been successfully sent to the first UE on the sidelink.
[0064] In one embodiment, determining that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path may include receiving second signaling from the first UE via the UE-to-network direct path, and determining based on the second signaling that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path. The second signaling indicates that the PDCP PDU has been successfully received by the first UE via the UE-to-network relay path.
[0065] In one embodiment, the method may further include determining to deactivate PDCP duplication of a downlink radio bearer. The method may further include performing at least one of the following operations: deactivating PDCP duplication of a downlink radio bearer; sending a third signaling to a first UE; sending a fourth signaling to a first UE; sending a fifth signaling to a relay UE; discarding at least one duplicated PDCP PDU and / or RLC SDU associated with a downlink radio bearer; or sending a sixth signaling to a relay UE. The sixth signaling indicates discarding at least one second duplicated PDCP PDU and / or RLC SDU associated with a downlink radio bearer. The third signaling indicates deactivating PDCP duplication of a downlink radio bearer. The fifth signaling indicates deactivating at least one Uu and PC5 RLC entity of a downlink radio bearer on a UE-to-network relay path. The fourth signaling indicates deactivating at least one sidelink RLC entity of a downlink radio bearer on a UE-to-network relay path.
[0066] In one embodiment, the at least one second duplicate PDCP PDU and / or RLC SDU may include at least one of one or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer received from the network node and stored in at least one Uu RLC entity of the relay UE, or at least one of one or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer stored in at least one sidelink RLC of the relay UE.
[0067] In one embodiment, the method may further include maintaining a mapping table between Uu PDCP PDUs and Uu RLC PDUs in the UE-to-network relay path.
[0068] In one embodiment, the mapping table may include at least one of a mapping of a Uu PDCP PDU to one or more Uu RLC PDUs, or a mapping of one or more Uu PDCP PDUs to a Uu RLC PDU.
[0069] In one embodiment, the Uu PDCP PDU in the mapping table may be identified by a sequence number (SN) value of the Uu PDCP PDU, and the Uu RLC PDU may be identified by a sequence number (SN) value of the Uu RLC PDU.
[0070] In one embodiment, when a Uu PDCP PDU is delivered to the Uu RLC layer, an entry corresponding to the Uu PDCP PDU is added to the mapping table, and when the Uu RLC layer indicates to the Uu PDCP layer that the Uu PDCP PDU has been successfully sent to the recipient, or when a timer or counter expires and the Uu PDCP PDU has become invalid, the entry corresponding to the Uu PDCP PDU is deleted.
[0071] In one embodiment, the signaling between the network node and the first UE may include at least one of RRC signaling, a medium access control (MAC) control element (CE), or layer 1 signaling.
[0072] In one embodiment, the signaling between the relay UE and the first UE may include at least one of RRC signaling, MAC CE, or control PDU of the protocol layer.
[0073] In a fourth aspect of the present disclosure, a first user equipment (UE) is provided. The first UE may include a processor and a memory coupled to the processor. The memory contains instructions executable by the processor. The first UE is used to determine, for an uplink radio bearer activated by packet data convergence protocol (PDCP) duplication, that a PDCP protocol data unit (PDU) has been successfully delivered to a network node by a relay UE on a UE-to-network relay path. The first UE is also used to discard at least one duplicated PDCP PDU on at least one other UE-to-network path.
[0074] In a fifth aspect of the present disclosure, a relay UE is provided. The relay UE may include a processor and a memory coupled to the processor. The memory contains instructions executable by the processor. The relay UE is used to receive a PDCP PDU of an uplink radio bearer from a first UE. The uplink radio bearer has been activated by PDCP duplication. The relay UE is also used to send an indication to the first UE that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path.
[0075] In a sixth aspect of the present disclosure, a network node is provided. The network node may include a processor and a memory coupled to the processor. The memory contains instructions executable by the processor. The network node is used to determine that a PDCP PDU has been successfully delivered to a first UE through a relay UE on a UE-to-network relay path for a downlink radio bearer that has been activated with PDCP duplication. The network node is also used to discard at least one duplicated PDCP PDU on at least one other UE-to-network path.
[0076] In a seventh aspect of the present disclosure, a first UE is provided. The first UE may include a determination module configured to determine, for an uplink radio bearer that has been activated by packet data convergence protocol (PDCP) duplication, that a PDCP protocol data unit (PDU) has been successfully delivered to a network node by a relay UE on a UE-to-network relay path. The first UE may also include a discard module configured to discard at least one duplicated PDCP PDU on at least one other UE-to-network path.
[0077] In one embodiment, the first UE may further include a first receiving module configured to receive a third signaling from the network node. The third signaling indicates deactivation of the PDCP duplication of the uplink radio bearer.
[0078] In one embodiment, the first UE may further include a first execution module configured to perform at least one of the following operations: deactivate PDCP duplication of the uplink radio bearer; discard at least one first duplicate PDCP PDU and / or RLC service data unit (SDU) associated with the uplink radio bearer; or send a fourth signaling to the relay UE. The fourth signaling instructs the relay UE to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0079] In one embodiment, the first UE may further include a second receiving module configured to receive fifth signaling from the network node. The fifth signaling indicates deactivation of PDCP duplication of uplink radio bearers of at least one sidelink RLC entity.
[0080] In one embodiment, the first UE may further include a second execution module, which is configured to perform at least one of the following operations: discarding at least one third duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer of at least one RLC entity; or sending a sixth signaling to the relay UE. The sixth signaling instructs the relay UE to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and at least one RLC entity.
[0081] In one embodiment, the first UE may further include a maintenance module configured to maintain a mapping table between Uu PDCP PDU and sidelink RLC PDU in a UE-to-network relay path.
[0082] In an eighth aspect of the present disclosure, a relay UE is provided. The relay UE may include a first receiving module configured to receive a PDCP PDU of an uplink radio bearer from a first UE. The uplink radio bearer has been activated by PDCP duplication. The relay UE may include a sending module configured to send an indication to the first UE that the PDCP PDU has been successfully delivered to a network node through the relay UE on a UE-to-network relay path.
[0083] In one embodiment, the relay UE may further include a second receiving module configured to receive signaling from the first UE. The signaling instructs the relay UE to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer. The relay UE may also include a first discarding module configured to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0084] In one embodiment, the relay UE may further include a third receiving module configured to receive signaling from the first UE. The signaling instructs the relay UE to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and at least one RLC entity. The relay UE may also include a second discarding module configured to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and at least one RLC entity.
[0085] In one embodiment, the relay UE may further include a fourth receiving module configured to receive signaling including an identifier of the first UE from the network node. The signaling indicates discarding the duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer. The relay UE may also include a third discarding module configured to discard the duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0086] In one embodiment, the relay UE may further include a fifth receiving module configured to receive signaling including an identifier of the first UE from the network node. The signaling indicates to deactivate at least one RLC entity of the uplink radio bearer in the UE-to-network relay path. The relay UE may also include a deactivation module configured to deactivate at least one RLC entity of the uplink radio bearer in the UE-to-network relay path.
[0087] In one embodiment, the relay UE may further include a maintenance module configured to maintain a mapping table between Uu PDCP PDUs and sidelink RLC PDUs in a UE-to-network relay path.
[0088] In a ninth aspect of the present disclosure, a network node is provided. The network node may include a first determining module configured to determine, for a downlink radio bearer that has been activated by PDCP duplication, that a PDCP PDU has been successfully delivered to a first UE via a relay UE on a UE-to-network relay path. The network node may also include a discarding module configured to discard at least one duplicated PDCP PDU on at least one other UE-to-network path.
[0089] In one embodiment, the network node may further include a second determining module configured to determine to deactivate the PDCP duplication of the downlink radio bearer.
[0090] In one embodiment, the network node may also include an execution module, which is configured to perform at least one of the following operations: deactivate PDCP duplication of a downlink radio bearer; send a third signaling to the first UE; send a fourth signaling to the first UE; send a fifth signaling to the relay UE; discard at least one duplicate PDCP PDU and / or RLC SDU associated with the downlink radio bearer; or send a sixth signaling to the relay UE. The sixth signaling indicates discarding at least one second duplicate PDCP PDU and / or RLC SDU associated with the downlink radio bearer. The third signaling indicates deactivation of PDCP duplication of the downlink radio bearer. The fourth signaling indicates deactivation of at least one sidelink RLC entity of the downlink radio bearer on the UE to network relay path. The fifth signaling indicates deactivation of at least one Uu and PC RLC entity of the downlink radio bearer on the UE to network relay path.
[0091] In one embodiment, the network node may further include a maintenance module configured to maintain a mapping table between Uu PDCP PDU and Uu RLC PDU in a UE-to-network relay path.
[0092] In another aspect of the present disclosure, a computer program product is provided, comprising instructions, which when executed by at least one processor causes the at least one processor to perform the method according to any one of the first, second and third aspects.
[0093] In another aspect of the present disclosure, a computer-readable storage medium storing instructions is provided. When executed by at least one processor, the instructions cause the at least one processor to perform the method according to any one of the first, second and third aspects.
[0094] In another aspect of the present disclosure, a communication system including a host is provided. The host includes a processing circuit configured to provide user data and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network includes the above-mentioned network node and / or terminal device (such as the above-mentioned first UE and relay UE).
[0095] In an embodiment of the present disclosure, the system further includes a terminal device. The terminal device is configured to communicate with the network node.
[0096] In an embodiment of the present disclosure, a processing circuit of the host is configured to execute a host application to provide user data; and the terminal device includes a processing circuit configured to execute a client application associated with the host application.
[0097] In another aspect of the present disclosure, a communication system is provided, including a host and a network node. The host includes a communication interface configured to receive user data transmitted from a terminal device. The transmission is from the terminal device to the network node. The network node is as described above, and / or the terminal device is as described above, a first UE and a relay UE.
[0098] In an embodiment of the present disclosure, the processing circuit of the host is configured to execute a host application. The terminal device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host.
[0099] In another aspect of the present disclosure, a method implemented in a communication system is provided, the communication system may include a host, a network node and a terminal device. The method may include providing user data at the host. Optionally, the method may include initiating, at the host, a transmission carrying user data to the terminal device via a cellular network including a network node, the network node may perform any steps of the method according to the third aspect of the present disclosure.
[0100] In another aspect of the present disclosure, a communication system including a host is provided. The host may include a processing circuit configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network may include a network node having a radio interface and a processing circuit. The processing circuit of the network node may be configured to perform any step of the method according to the third aspect of the present disclosure.
[0101] In another aspect of the present disclosure, a method implemented in a communication system is provided, the communication system may include a host, a network node and a terminal device. The method may include providing user data at the host. Optionally, the method may include initiating a transmission carrying user data to the terminal device via a cellular network including the network node at the host. The terminal device may perform any steps of the method according to the first and second aspects of the present disclosure.
[0102] In another aspect of the present disclosure, a communication system including a host is provided. The host may include a processing circuit configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The terminal device may include a radio interface and a processing circuit. The processing circuit of the terminal device may be configured to perform any steps of the method according to the first and second aspects of the present disclosure.
[0103] In another aspect of the present disclosure, a method implemented in a communication system is provided, the communication system may include a host, a network node and a terminal device. The method may include receiving user data sent from the terminal device to the network node at the host, and the terminal device may perform any steps of the method according to the first and second aspects of the present disclosure.
[0104] In another aspect of the present disclosure, a communication system including a host is provided. The host may include a communication interface configured to receive user data originating from a transmission from a terminal device to a network node. The terminal device may include a radio interface and a processing circuit. The processing circuit of the terminal device may be configured to perform any steps of the method according to the first and second aspects of the present disclosure.
[0105] In another aspect of the present disclosure, a method implemented in a communication system is provided, which may include a host, a network node, and a terminal device. The method may include receiving, at the host, from the network node, user data originating from a transmission received by the network node from the terminal device. The network node may perform any steps of the method according to the third aspect of the present disclosure.
[0106] In another aspect of the present disclosure, a communication system is provided, which may include a host. The host may include a communication interface configured to receive user data originating from a transmission from a terminal device to a network node. The network node may include a radio interface and a processing circuit. The processing circuit of the network node may be configured to perform any steps of the method according to the third aspect of the present disclosure.
[0107] Embodiments herein may provide many advantages, the following is a non-exhaustive list of examples. In some embodiments herein, it may avoid transmitting redundant duplicate PDUs. In some embodiments herein, it may ensure that PDCP duplication works properly in Uu and SL mixed multipath scenarios. Embodiments herein are not limited to the above features and advantages. Those skilled in the art will recognize additional features and advantages after reading the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0108] The above and other aspects, features and benefits of various embodiments of the present disclosure will become more apparent through examples through the following detailed description with reference to the accompanying drawings, in which the same reference numerals or letters are used to represent the same or equivalent elements. The accompanying drawings are shown to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale, wherein:
[0109] Figure 1a The protocol stack of the user plane from L2 UE to network relay UE is shown;
[0110] Figure 1b The protocol stack of the control plane from L2 UE to network relay UE is shown;
[0111] Figure 1c An architectural model using ProSe 5G UE to network relay is shown;
[0112] Figure 1d shows the protocol stack for layer 3 UE to network relay;
[0113] Figure 1e An example of packet duplication is shown;
[0114] Figure 2a The high-level architecture in the fifth generation network according to an embodiment of the present disclosure is schematically shown;
[0115] Figure 2b The system architecture in a 4G network according to an embodiment of the present disclosure is schematically shown;
[0116] Figure 3a A flowchart of a method according to an embodiment of the present disclosure is shown;
[0117] Figure 3b A flowchart of a method according to another embodiment of the present disclosure is shown;
[0118] Figure 3c A flowchart of a method according to another embodiment of the present disclosure is shown;
[0119] Figure 3d A flowchart of a method according to another embodiment of the present disclosure is shown;
[0120] Figure 4a A flowchart of a method according to another embodiment of the present disclosure is shown;
[0121] Figure 4b A flowchart of a method according to another embodiment of the present disclosure is shown;
[0122] Figure 4c A flowchart of a method according to another embodiment of the present disclosure is shown;
[0123] Figure 4d A flowchart of a method according to another embodiment of the present disclosure is shown;
[0124] Figure 4e A flowchart of a method according to another embodiment of the present disclosure is shown;
[0125] Figure 4f A flowchart of a method according to another embodiment of the present disclosure is shown;
[0126] Figure 5a A flowchart of a method according to another embodiment of the present disclosure is shown;
[0127] Figure 5b A flowchart of a method according to another embodiment of the present disclosure is shown;
[0128] Figure 6 A flowchart of a method according to another embodiment of the present disclosure is shown;
[0129] Figure 7 is a block diagram illustrating an apparatus suitable for implementing some embodiments of the present disclosure;
[0130] Figure 8a is a block diagram illustrating a first UE according to an embodiment of the present disclosure;
[0131] Figure 8b is a block diagram illustrating a relay UE according to an embodiment of the present disclosure;
[0132] Figure 8c is a block diagram illustrating a network node according to an embodiment of the present disclosure;
[0133] Fig. 9 is a schematic diagram illustrating a wireless network according to some embodiments;
[0134] Fig.10 is a schematic diagram illustrating a user equipment according to some embodiments;
[0135] Fig.11 is a schematic diagram illustrating a virtualized environment according to some embodiments;
[0136] Fig.12 is a schematic diagram illustrating a telecommunications network connected to a host via an intermediate network according to some embodiments;
[0137] Fig.13 is a schematic diagram illustrating a host communicating with a user device via a base station over a partial wireless connection according to some embodiments;
[0138] Fig.14 is a schematic diagram illustrating a method implemented in a communication system including a host, a base station and a user equipment according to some embodiments;
[0139] Fig.15 is a schematic diagram illustrating a method implemented in a communication system including a host, a base station and a user equipment according to some embodiments;
[0140] Fig.16 is a schematic diagram illustrating a method implemented in a communication system including a host, a base station and a user equipment according to some embodiments; and
[0141] Fig.17 is a schematic diagram illustrating a method implemented in a communication system including a host, a base station and a user equipment according to some embodiments. DETAILED DESCRIPTION
[0142] Embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and therefore implement the present disclosure, rather than to impose any limitation on the scope of the present disclosure. References to features, advantages or similar language throughout this specification do not mean that all features and advantages that the present disclosure can achieve should or have been in any single embodiment of the present disclosure. On the contrary, the language referring to features and advantages is understood to mean that the specific features, advantages or characteristics described in conjunction with the embodiments are included in at least one embodiment of the present disclosure. In addition, the features, advantages and characteristics of the present disclosure may be combined in one or more embodiments in any suitable manner. Those skilled in the relevant art will recognize that the present disclosure can be practiced without one or more specific features or advantages of a specific embodiment. In other cases, additional features and advantages that may not be present in all embodiments of the present disclosure may be recognized in certain embodiments.
[0143] As used herein, the term "network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA) and other wireless networks. A CDMA network can implement wireless technologies such as Universal Terrestrial Radio Access (UTRA). UTRA includes other variants of WCDMA and CDMA. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, ad hoc networks, wireless sensor networks, etc. In the following description, the terms "network" and "system" can be used interchangeably. In addition, communication between two devices in the network can be performed according to any suitable communication protocol, including but not limited to communication protocols defined by standard organizations such as 3GPP. For example, the communication protocol may include first generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols and / or any other protocol currently known or developed in the future.
[0144] The term "network node" refers to any suitable network function (NF) that can be implemented in a network element (physical or virtual) of a communication network. For example, a network function may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an appropriate platform, such as on a cloud infrastructure. For example, a 5G system (5GS) may include multiple NFs, such as AMF (Access and Mobility Management Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Exposure Function), UPF (User Plane Function) and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Agent), NWDAF (Network Data Analysis Function), NSSF (Network Slice Selection Function), NSWAF (Network Slice Specific Authentication and Authorization Function), etc. For example, a 4G system (such as LTE) may include an MME (mobility management entity), an HSS (home subscriber server), a policy and charging rules function (PCRF), a packet data network gateway (PGW), a PGW control plane (PGW-C), a serving gateway (SGW), a SGW control plane (SGW-C), an E-UTRAN node B (eNB), etc. In other embodiments, the network function may include different types of NFs, for example, depending on the specific network.
[0145] A network node may be an access network node with access function in a communication network, through which a terminal device accesses the network and receives services therefrom. An access network node may include a base station (BS), an access point (AP), a multi-cell / multicast coordination entity (MCE), a controller, or any other suitable device in a wireless communication network. For example, a BS may be a Node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next generation NodeB (gNodeB or gNB), a remote radio unit (RRU), a radio head (RH), an integrated access and backhaul (IAB) node, a remote radio head (RRH), a repeater, a low power node such as a femto, a pico, etc.
[0146] Further examples of access network nodes include multi-standard radio (MSR) radio equipment, such as an MSR BS, a network controller, such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a positioning node, etc. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured, arranged and / or operable to enable and / or provide a terminal device with access to a wireless communication network, or to provide a certain service to a terminal device that has access to the wireless communication network.
[0147] The term "terminal device" refers to any terminal device that can access a communication network and receive services therefrom. As an example and not limitation, a terminal device refers to a mobile terminal, a user equipment (UE) or other suitable device. A UE may be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT). A terminal device may include, but is not limited to, a portable computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), etc. In the following description, the terms "terminal device", "terminal", "user equipment" and "UE" may be used interchangeably. As an example, a terminal device may represent a UE configured to communicate in accordance with one or more communication standards promulgated by 3GPP (3rd Generation Partnership Project), such as 3GPP's LTE standard or NR standard. As used herein, "user equipment" or "UE" does not necessarily have a "user" in the sense of a human user who owns and / or operates the associated device. In some embodiments, the terminal device may be configured to send and / or receive information without direct human-computer interaction. For example, a terminal device may be designed to transmit information to a network on a predetermined schedule when triggered by an internal or external event, or in response to a request from a communication network. In contrast, a UE may represent a device that is intended to be sold to or operated by a human user, but may not initially be associated with a specific human user.
[0148] As another example, in an Internet of Things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring and / or measurement, and transmits the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a machine type communication (MTC) device in the 3GPP context. As a specific example, a terminal device may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances, such as refrigerators, televisions, personal wearable devices such as watches, etc. In other scenarios, a terminal device may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions related to its operation.
[0149] References in the specification to "one embodiment," "an embodiment," and "an example embodiment" indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, whether or not explicitly described, it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments.
[0150] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.
[0151] As used herein, the phrase "at least one of A and B" or "at least one of A or B" should be understood as "only A, only B, or both A and B." The phrase "A and / or B" should be understood as "only A, only B, or both A and B."
[0152] The terms used herein are only used to describe specific embodiments and are not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" used herein also include plural forms. It should also be understood that the terms "comprise", "include", "have", "have", "include" and / or "include" when used in this article specify the presence of the features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0153] Note that these terms used in this document are only for convenience in describing and distinguishing nodes, devices or networks, etc. As technology develops, other terms with similar / same meanings may also be used.
[0154] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
[0155] NR sidelink
[0156] NR Sidelink communications are specified by 3GPP Release 16. NR SL is an evolution of LTE Sidelink, specifically the functionality for Vehicle-to-Everything (V2X) communications introduced in 3GPP Release 14 and 3GPP Release 15. Some of the most relevant features of NR Sidelink are as follows:
[0157] In addition to the broadcast transmission already supported in LTE, unicast and multicast transmission are also supported.
[0158] Support for HARQ (Hybrid Automatic Repeat Request) feedback for unicast and multicast over SL. This feedback is transmitted by the receiving UE to the transmitting UE using the Physical Sidelink Feedback Channel (PSFCH). This feature is new in NR compared to LTE.
[0159] To mitigate resource conflicts between different sidelink transmissions initiated by different UEs, it enhances the channel sensing and resource selection process, which also leads to a new design of the physical channel that carries the Sidelink Control Information (SCI). The new design of the SCI simplifies coexistence between versions by grouping all information related to resource allocation (which is critical for coexistence) into a single channel in a robust predefined format. Other control information is carried in a more flexible way through other means.
[0160] The grant-free transmission supported in NR uplink transmission is also provided in NR sidelink transmission to improve latency performance.
[0161] To achieve high connection density, congestion control is supported in NR sidelink transmission, thereby supporting QoS (Quality of Service) management.
[0162] NR SL physical channel
[0163] In the NR sidelink, the following physical layer (PHY) channels are defined:
[0164] PSCCH (Physical Sidelink Common Control Channel): This channel carries Sidelink Control Information (SCI), including part of the Scheduling Assignment (SA), allowing the receiver to further process and decode the corresponding PSSCH (e.g., Demodulation Reference Signal (DMRS) pattern and antenna port, MCS (Modulation and Coding Scheme), etc.). In addition, PSCCH indicates resources reserved for the future. This allows the RX (receiver) to sense and predict the utilization of the channel in the future. This sensing information is used for the purpose of UE autonomous resource allocation (Mode 2), which will be described below.
[0165] PSSCH (Physical Sidelink Shared Channel): PSSCH is sent by the sidelink transmitter UE, which transmits sidelink transmission data (i.e., SL shared channel SL-SCH) and part of the sidelink control information (SCI). In addition, PSSCH can be used to carry higher-layer control information (e.g., MAC (Media Access Control) CE (Control Element), Radio Resource Control (RRC) signaling, etc.). For example, channel state information (CSI) is carried in the Media Access Control (MAC) Control Element (CE) via PSSCH instead of PSFCH.
[0166] PSFCH (Physical Sidelink Feedback Channel): PSFCH is transmitted by the sidelink receiver UE for unicast and multicast. It conveys SL HARQ acknowledgment which may consist of ACK / NACK (acknowledgement / negative acknowledgement) (for unicast and multicast option 2) or just NACK (for multicast option 1).
[0167] Physical Sidelink Broadcast Channel (PSBCH): PSBCH conveys synchronization related information such as Direct Frame Number (DFN), indication of slot and symbol-level time resources used for sidelink transmission, in-coverage indicator, etc. SSB is transmitted periodically every 160 milliseconds. PSBCH is transmitted together with S-PSS / S-SSS (Sidelink Primary / Secondary Synchronization Signal) as Sidelink Synchronization Signal Block (S-SSB).
[0168] The sidelink primary / secondary synchronization signals (S-PSS / S-SSS) are used by UEs to establish a common timing reference between UEs in the absence of other references, such as GNSS time of NW time.
[0169] Along with different physical channels, reference signals (RS) are transmitted for different purposes, including demodulation (DM-RS), phase tracking RS (PT-RS), or RS for channel state information acquisition (CSI-RS).
[0170] Another new feature is the two-stage Sidelink Control Information (SCI). The first part (Phase 1) of the SCI is sent on the PSCCH. This part is used for channel sensing purposes (including time-frequency resources reserved for transmission, demodulation reference signal (DMRS) pattern and antenna ports, etc.) and can be read by all UEs, while the rest of the SCI (Phase 2) carries the remaining scheduling and control information, such as the 8-bit source identification (ID) and 16-bit destination ID, NDI (New Data Indicator), RV (Redundancy Version) and HARQ process ID, which is sent on the PSSCH and decoded by the receiving UE.
[0171] Resource Allocation
[0172] NR sidelink supports the following two resource allocation modes:
[0173] Mode 1: Sidelink resources are scheduled by the gNB.
[0174] Mode 2: The UE autonomously selects the sidelink resource from a (pre-)configured sidelink resource pool. To avoid collisions between UEs, a procedure based on channel sensing and resource reservation is used.
[0175] The gNB can configure UEs within the coverage area to use Mode 1 or Mode 2. For UEs outside the coverage area, only Mode 2 can be used.
[0176] As in LTE, sidelink scheduling in NR is done differently for Mode 1 and Mode 2.
[0177] In Mode 1, the grant is provided by the gNB. The following two grants are supported:
[0178] Provides dynamic grants for one or more transmissions of a single data packet (i.e., transport block). When traffic to be sent over the sidelink arrives at the transmitting UE (i.e., at the corresponding TX (transmit) buffer), the UE initiates a four-message exchange process to request sidelink resources from the gNB (SR (Scheduling Request) on the UL (Uplink), Grant, BSR (Buffer Status Report) on the UL, Data Grant on the SL sent to the UE). The gNB indicates the resource allocation for PSCCH and PSSCH in the Downlink Control Information (DCI) transmitted by the PDCCH (Physical Downlink Control Channel) with a CRC (Cyclic Redundancy Check) scrambled with the SL-RNTI (Radio Network Temporary Identity) of the corresponding UE. A UE receiving such DCI assumes that it has obtained a SL dynamic grant only if it detects that the CRC of the DCI has been scrambled with its SL-RNTI. The transmitting UE then indicates the allocated time-frequency resources and transmission scheme of the PSSCH in the PSCCH and starts PSCCH and PSSCH on the allocated resources for sidelink transmission. When obtaining a grant from the gNB, the transmitting UE can only send a single TB. Therefore, this grant is suitable for services with relaxed latency requirements.
[0179] Configured Grants: For traffic with strict latency requirements, performing a four-message exchange procedure to request sidelink resources may result in unacceptable latency. In this case, before the traffic arrives, the sender UE can perform a four-message exchange procedure and request a set of resources. If a grant is available from the gNB, the requested resources are reserved in a periodic manner. When traffic arrives at the sender UE, the UE can start the PSCCH and PSSCH at the upcoming resource instant. This grant is also called grant-free transmission.
[0180] Note that only the transmitting UE is scheduled by the gNB. The receiving UE does not receive any information directly from the gNB. Instead, it is scheduled by the transmitting UE through the SCI. Therefore, the receiving UE should perform blind decoding to identify the presence of PSCCH and find the resources of PSSCH through SCI.
[0181] In Mode 2 resource allocation, the grant is generated by the UE itself. When traffic arrives at the sending UE (i.e., at the corresponding TX buffer), the transmitter autonomously selects resources for PSCCH and PSSCH. In order to further improve the probability of successful TB (transport block) decoding in one go, thereby suppressing the probability of performing retransmissions, the sending UE can repeat TB transmissions at the same time as the initial TB transmission. These retransmissions can be triggered by the corresponding SL HARQ feedback, or can be sent blindly by the sending UE. In either case, in order to minimize the collision probability of potential retransmissions, the sending UE can also reserve corresponding resources for PSCCH / PSSCH for retransmissions. That is, the sending UE selects resources for:
[0182] 1) PSCCH / PSSCH corresponding to the first transmission.
[0183] 2) PSCCH / PSCCH corresponding to retransmissions. Resources for up to 2 retransmissions can be reserved. These reserved resources are always used in case of blind retransmissions. If SL HARQ feedback is used, the use of the reserved resources is conditional on a negative SLHARQ ACK.
[0184] Since each sender UE in the sidelink transmission should autonomously select resources for its own transmission, preventing different sender UEs from selecting the same resources is a key issue in Mode 2. Therefore, a specific resource selection process is imposed on Mode 2 based on channel sensing. The channel sensing algorithm involves detecting reservations sent by other UEs and performing power measurements (i.e., Reference Signal Received Power or RSRP) on incoming transmissions.
[0185] NR Sidelink Layer 2 (L2) UE to Network Relay
[0186] In 3GPP TR 23.752 V17.0.0, a layer 2 based UE to network relay is described, the disclosure of which is incorporated herein by reference in its entirety.
[0187] A protocol architecture supporting L2 UE to network relay UE is provided.
[0188] L2 UE to network relay UE provides forwarding functionality and can relay any type of traffic over the PC5 link.
[0189] L2 UE to Network Relay UE provides the functionality to support remote UEs to connect to 5GS (5G System). If the UE has successfully established a PC5 link to L2 UE to Network Relay UE, the UE is considered to be a remote UE. The remote UE can be located within or outside the NG-RAN coverage.
[0190] Figure 1a The user plane protocol stack for L2 UE to network relay UE is shown, which is the same as Figure A.2.1-1 of 3GPP TR 23.752 V17.0.0. APP means application. PDU means protocol data unit. SDAP means service data adaptation protocol. RLC means radio link control. MAC means medium access control. PHY means physical layer. L2 means layer 2. The PDU layer corresponds to the PDU carried between the remote UE and the data network (DN) through the PDU session. It is worth noting that the two endpoints of the PDCP link are the remote UE and the gNB. The relay function is performed below the PDCP. This means that data security is ensured between the remote UE and the gNB without exposing the original data at the UE to network relay UE.
[0191] UE to Network Relay The Adaptation Relay layer within the UE can distinguish between Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs) for a specific remote UE. The Adaptation Relay layer is also responsible for mapping PC5 traffic to one or more DRBs of Uu.
[0192] Figure 1b The protocol stack of the control plane from L2 UE to network relay UE is shown, which is the same as Figure A.2.2-1 of 3GPP TR23.752 V17.0.0. NAS stands for non-access stratum. SM stands for session management. MM stands for mobility management.
[0193] NAS messages are transparently transferred between the remote UE and 5G-AN (access network) via a Layer 2 UE to Network Relay UE using:
[0194] - PDCP end-to-end connection where UE to network relay The role of the UE is to relay the PDUs on the signalling radio bearer without any modification.
[0195] -N2 connection between 5G-AN and AMF on N2.
[0196] - N11 connection between AMF and SMF on N11.
[0197] UE to Network Relay The role of the UE is to relay PDUs from the signalling radio bearers without any modification.
[0198] NRSL Layer 3 (L3) UE to Network Relay
[0199] In 3GPP TR 23.752 V17.0.0 clause 6.6, layer 3 based UE to network relay is described.
[0200] Figure 1c The architecture model of 5G UE to network relay using ProSe is shown, which is consistent with 3GPP TR23.752V17.0.0 Figure 6 .Same as 6.1-1.
[0201] The ProSe 5G UE-to-network relay entity provides the functionality to support remote UEs to connect to the network. It can be used for both public safety services and commercial services (such as interactive services).
[0202] If the UE has successfully established a PC5 link to this ProSe 5G UE to Network Relay, the UE is considered to be a remote UE of a certain ProSe UE to Network Relay. The remote UE can be located inside or outside the NG-RAN coverage.
[0203] ProSe 5G UE to Network Relay shall relay unicast traffic (UL (uplink) and DL (downlink)) between remote UE and the network. ProSe UE to Network Relay shall provide generic functionality that can relay any IP traffic.
[0204] As described in the solution to key issue #2 in 3GPP TR 23.752 V17.0.0, one-to-one direct communication is used between the remote UE and the ProSe 5G UE to the network relay for unicast services.
[0205] Figure 1d The protocol stack of the Layer 3 UE to Network Relay is shown, in accordance with 3GPP TR 23.752 V17.0.0 Figure 6 .6.1-2 are the same.
[0206] PC5 links and Uu links support hop-by-hop security. If there are requirements other than hop-by-hop security for the protection of remote UE services, IP layer security needs to be applied.
[0207] Packet replication in NR
[0208] Figure 1e An example of packet duplication is shown, which is consistent with 3GPP TS 38.300 V16.8.0 Fig.16 .1.3-1, the entire contents of which are incorporated herein by reference.
[0209] As described in clause 16.1.3 of TS 38.300 V16.8.0, when RRC configures replication for a radio bearer, at least one secondary RLC entity is added to the radio bearer to handle the replicated PDCP PDU, where the logical channel corresponding to the primary RLC entity is called the primary logical channel, and the logical channel corresponding to the secondary RLC entity is called the secondary logical channel. All RLC entities have the same RLC mode. Therefore, the replication of PDCP includes submitting the same PDCP PDU multiple times: once to each activated RLC entity for the radio bearer. Through multiple independent transmission paths, data packet replication therefore improves reliability and reduces latency, which is particularly beneficial for URLLC services.
[0210] NOTE: PDCP Control PDUs are not repeated and are always submitted to the primary RLC entity.
[0211] When duplication is configured for a DRB, the RRC also sets the state of the PDCP duplication (activated or deactivated) upon (re)configuration. Once configured, the PDCP duplication state can be dynamically controlled via MAC control elements, and in DC (dual connectivity), the UE applies a MACCE command regardless of its source (MCG (primary cell group) or SCG (secondary cell group)). When duplication is configured for an SRB, the state is always active and cannot be dynamically controlled. When duplication is configured for a DRB with multiple secondary RLC entities, the RRC also sets the state of each entity (i.e. activated or deactivated). Subsequently, the Media Access Control (MAC) Control Element (CE) can be used to dynamically control whether each configured secondary RLC entity of the DRB should be activated or deactivated, i.e. which RLC entities should be used for duplicate transmission. The primary RLC entity cannot be deactivated. When duplication of a DRB is deactivated, all secondary RLC entities associated with that DRB are deactivated. When a secondary RLC entity is deactivated, it is not reestablished, the HARQ buffer is not flushed, and the sending PDCP entity shall indicate to the secondary RLC entity to discard all duplicated PDCP PDUs.
[0212] When duplication is activated for a DRB, the NG-RAN shall ensure that at least one serving cell is activated for each logical channel associated with the activated RLC entity of the DRB; and when deactivation of the Scell (secondary cell) leaves the logical channel of the DRB without a serving cell activated, the NG-RAN (Next Generation Radio Access Network) shall ensure that the duplication of the RLC entity associated with the logical channel is also deactivated.
[0213] When replication is activated, the original PDCP PDU and the corresponding copy shall not be transmitted on the same carrier. The logical channels of the radio bearers configured with replication may belong to the same MAC entity (called CA (Carrier Aggregation) replication) or to different MAC entities (called DC (Dual Connectivity) replication). When replication on more than two RLC entities is configured for a radio bearer, CA replication as well as DC replication may also be configured in either or both of the MAC entities. In CA replication, logical channel mapping restrictions are used in the MAC entity to ensure that different logical channels of the radio bearers in the MAC entity are not sent on the same carrier. When CA replication is configured for an SRB, one of the logical channels associated with the SRB is mapped to the SpCell.
[0214] When the CA replication of a DRB in a MAC entity is deactivated (i.e., none or only one of the RLC entities of the DRB in the MAC entity remains activated), the logical channel mapping restrictions for the logical channels of the DRB are lifted as long as the CA replication remains deactivated.
[0215] When the RLC entity acknowledges the transmission of a PDCP PDU, the PDCP entity shall instruct other RLC entities to discard it. In addition, in case of CA duplication, when the RLC entity limited to the SCell reaches the maximum number of retransmissions of the PDCP PDU, the UE notifies the gNB but does not trigger a Radio Link Failure (RLF).
[0216] Duplicate PDUs are discarded at the PDCP layer
[0217] As described in clause 5.11.2 of TS 38.323 V16.6.0, which is incorporated herein by reference in its entirety, for a PDCP entity configured with PDCP duplication pdcp-Duplication, the transmitting PDCP entity shall:
[0218] - If successful delivery of the PDCP data PDU is acknowledged by one of the associated AM RLC entities:
[0219] - Instruct other AM RLC entities to discard duplicate PDCP data PDUs;
[0220] - If DRB is instructed to deactivate PDCP duplication:
[0221] - instruct RLC entities other than the master RLC entity to discard all duplicated PDCP data PDUs;
[0222] - If deactivation of PDCP duplication is indicated for at least one associated RLC entity:
[0223] - Instruct the RLC entity that deactivated PDCP duplication to discard all duplicated PDCP data PDUs.
[0224] RLC layer SDU discard
[0225] As described in clause 5.4 of TS 38.322 V16.2.0, when a specific RLC Service Data Unit (SDU) is indicated to be discarded from the upper layer (i.e., PDCP), the transmitting side of an acknowledged mode (AM) RLC entity or a transmitting UM (unacknowledged mode (UM)) RLC entity shall discard the indicated RLC SDU if neither the RLC SDU nor its segments have been submitted to the lower layer. The transmitting side of an AM RLC entity shall not introduce RLC SN (sequence number) gaps when discarding the RLC SDU.
[0226] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to systems that conform to Figure 2a-2b The exemplary system architecture shown is described in detail with reference to the communication system. Figure 2a-2b The system architecture of the present invention only depicts some exemplary elements. In practice, the communication system may also include any additional elements suitable for supporting communication between terminal devices or between a wireless device and another communication device, such as a fixed telephone, a service provider, or any other network node or terminal device. The communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices to access and / or use services provided by or via the communication system.
[0227] Figure 2a The high-level architecture in the fifth generation network according to an embodiment of the present disclosure is schematically shown. For example, the fifth generation network may be 5GS. Figure 2a The architecture is the same as Figure 4.2.3-2 described in 3GPP TS 23.501 V17.2.0, the entire content of which is incorporated herein by reference. Figure 2a The system architecture may include some exemplary elements, such as AUSF, AMF, DN (data network), NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP (service communication agent), NSSAF (network slice specific authentication and authorization function), NSACF (network slice admission control function), etc.
[0228] According to an exemplary embodiment, the UE may establish a signaling connection with the AMF via reference point N1, such as Figure 2aAs shown. The signaling connection can realize the NAS (non-access layer) signaling exchange between the UE and the core network, including the signaling connection between the UE and the (R)AN and the N2 connection between the UE in the (R)AM and the AMF. The (R)AN can communicate with the UPF via reference point N3. The UE establishes a protocol data unit (PDU) session to the DN (data network, such as an operator network or the Internet) via the UPF on reference point N6.
[0229] like Figure 2a As further shown, the exemplary system architecture also includes some reference points, such as N1, N2, N3, N4, N6, N9, N15, etc., which can support the interaction between NF services in NF. For example, in order to implement a specific system process, these reference points can be implemented through corresponding NF service-based interfaces and by specifying some NF service consumers and providers and their interactions. AM related policies are provided to AMF by PCF for registered UEs through N15 interface. AMF can obtain AM policies during the AM policy association establishment / modification process.
[0230] Figure 2a The various NFs shown in may be responsible for functions such as session management, mobility management, authentication, security, etc. AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP, NSACF may include, for example, the functions defined in Section 6.2 of 3GPP TS23.501V17.2.0.
[0231] Figure 2b The system architecture in a 4G network according to an embodiment of the present disclosure is schematically shown, which is the same as FIG. 4.2-1a of 3GPP TS 23.682 V17.2.0, the entire content of which is incorporated herein by reference. Figure 2b The system architecture may include some exemplary elements, such as service capability server (SCS), application server (AS), SCEF (service capability exposure function), HSS, UE, RAN (radio access network), SGSN (serving GPRS (general packet radio service) support node), MME, MSC (mobile switching center), S-GW (serving gateway), GGSN / P-GW (gateway GPRS support node / PDN (packet data network) gateway), MTC-IWF (machine type communication-interworking function), CDF / CGF (charging data function / charging gateway function), MTC-AAA (machine type communication authentication, authorization and charging), SMS-SC / GMSC / IWMSC (short message service-service center / gateway MSC / interworking MSC) IP-SM-GW (Internet protocol short message gateway). Figure 2bThe network elements and interfaces shown may be the same as the corresponding network elements and interfaces described in 3GPP TS 23.682 V17.2.0.
[0232] The system architecture shows the architecture of a UE for MTC connected to a 3GPP network (UTRAN (Universal Terrestrial Radio Access Network), E-UTRAN (Evolved UTRAN), GERAN (GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network, etc.) via the Um / Uu / LTE Uu interface. The system architecture also shows that the 3GPP network service capabilities are exposed to the SCS and AS.
[0233] like Figure 2b As further shown, the exemplary system architecture also includes various reference points.
[0234] Tsms: A reference point used by entities outside the 3GPP network to communicate with UEs for MTC via SMS (Short Message Service).
[0235] Tsp: A reference point used by SCS for control plane signaling communications with MTC-IWF.
[0236] T4: Reference point used between MTC-IWF and SMS-SC in HPLMN.
[0237] T6a: Reference point used between SCEF and serving MME.
[0238] T6b: Reference point used between SCEF and serving SGSN.
[0239] T8: Reference point used between SCEF and SCS / AS.
[0240] S6m: A reference point used by MTC-IWF to query the HSS / HLR (Home Location Register).
[0241] S6n: A reference point used by MTC-AAA to query HSS / HLR.
[0242] S6t: Reference point used between SCEF and HSS.
[0243] SG: Reference point used between MSC and MME.
[0244] Gi / SGi: Reference point used between GGSN / P-GW and application server and between GGSN / P-GW and SCS.
[0245] Rf / Ga: Reference point used between MTC-IWF and CDF / CGF.
[0246] Gd: Reference point used between SMS-SC / GMSC / IWMSC and SGSN.
[0247] SGd: Reference point used between SMS-SC / GMSC / IWMSC and MME.
[0248] E: Reference point used between SMS-SC / GMSC / IWMSC and MSC.
[0249] End-to-end communication between the MTC application in the UE and the MTC application in the external network uses services provided by the 3GPP system and optionally uses services provided by a Service Capability Server (SCS).
[0250] MTC applications in external networks are usually hosted by application servers (AS) and may use SCS to provide additional value-added services. The 3GPP system provides transmission, user management and other communication services, including various architectural enhancements driven by MTC (e.g., control plane device triggering) but not limited to MTC.
[0251] In the communication between AS and 3GPP system, different models are predicted for machine type services based on the SCS provider. The different architecture models supported by the architecture reference model include direct model, indirect model and hybrid model described in 3GPP TS23.682V17.2.0.
[0252] The term "node" is used, which can be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB. MeNB (Master eNB), SeNB (Secondary eNB), Integrated Access Backhaul (IAB) node, network controller, Radio Network Controller (RNC), Base Station Controller (BSC), Repeater, Donor Node Control Repeater, Base Transceiver Station (BTS), Central Unit (e.g. in gNB), Distributed Unit (e.g. in gNB), Baseband Unit, Centralized Baseband, C-RAN (Centralized RAN), Access Point (AP), Transmission Point, Transmission Node, Remote Radio Unit (RRU), Remote Radio Head (RRH), Node in Distributed Antenna System (DAS), Core Network Node (e.g. MSC, MME, etc.), O&M (Operation and Maintenance), Operation Support System (OSS), Self-Organizing Network (SON), Positioning Node (e.g. E-SMLC (Evolved Serving Mobile Positioning Center)), etc.
[0253] Another example of a node is a user equipment (UE), which is a non-limiting term referring to any type of wireless device that communicates with a network node and / or with another UE in a cellular or mobile communication system. Examples of UEs include a target device, a device-to-device (D2D) UE, a vehicle-to-vehicle (V2V), a machine type UE, an MTC UE or a UE capable of machine-to-machine (M2M) communication, a PDA, a tablet, a mobile terminal, a smartphone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, etc.
[0254] In some embodiments, the general term "radio network node" or simply "network node (NW node)" is used. It can be any type of network node, which may include a base station, a radio base station, a base transceiver station, a base station controller, a network controller, an evolved Node B (eNB), a Node B, a gNodeB (gNB), a relay node, an access point, a radio access point, a remote radio unit (RRU), a remote radio head (RRH), a central unit (e.g., in a gNB), a distributed unit (e.g., within a gNB), a baseband unit, a centralized baseband, a C-RAN, an access point (AP), etc.
[0255] The term radio access technology or RAT may refer to any RAT, such as UTRA, E-UTRA, Narrowband Internet of Things (NB-IoT), WiFi, Bluetooth, Next Generation RAT, New Radio (NR), 4G, 5G, etc. Any device denoted by the term node, network node or radio network node may be capable of supporting a single or multiple RATs.
[0256] In addition, the term "direct path" is used to refer to a direct connection from a remote UE to a gNB (e.g., over an NR air interface), and we use the term "indirect path" to refer to an indirect connection between a remote UE and a gNB through an intermediate node, also called a relay UE. In the following embodiments, we assume that the indirect path contains two hops, namely a PC5 hop between the remote UE and the relay UE, and a Uu hop between the relay UE and the gNB. However, the embodiments are not limited to two hops. The embodiments are also applicable to indirect paths containing more than two hops.
[0257] Embodiments are described in the context of NR, i.e., the remote UE and the relay UE are deployed in the same or different NR cells. These embodiments are applicable to relay scenarios including UE-to-network (U2N) relays, where the link between the remote UE and the relay UE can be based on an LTE sidelink or an NR sidelink, and the Uu connection between the relay UE and the base station can be an LTE Uu or an NR Uu. The connection between the remote UE and the relay UE is also not limited to the sidelink. Any short-range communication technology, such as Wifi, is equally applicable.
[0258] These embodiments are also applicable to relay scenarios, where the relay UE is configured with multiple connections (ie, the number of connections is equal to or greater than two) to the RAN (eg, dual connectivity, carrier aggregation, etc.).
[0259] In an embodiment, a UE (e.g., a remote UE) may be connected to the same network node (e.g., a gNB) via a direct path and an indirect path (e.g., the UE is also connected to the gNB via a relay UE).
[0260] In the following embodiments, for Uu RBs configured with PDCP duplication, corresponding RLC entities are established in both the direct path and the indirect path. For example, it is assumed that the direct path is the primary path and the indirect path is the secondary path. Accordingly, the RLC entity on the primary path is the primary RLC entity, and the RLC-entity on the secondary path is the secondary RLC entity. However, the embodiments are not limited thereto. In the case where the indirect path is the primary path and the direct path is the secondary path, the embodiments are also applicable.
[0261] After activating PDCP duplication of Uu RB, in addition to the direct path, the UE also needs to establish / set up an RLC entity for the RB on the indirect path. These RLC entities can be called secondary RLC entities, including RLC entities on PC5 hop and Uu hop. PC5 RLC entity and Uu RLC entity correspond to each other. At the same time, the RLC entity of the RB on the direct path can be called the primary RLC entity.
[0262] The methods and solutions disclosed in the embodiments are described in the context of NR sidelink (SL) communications. However, most of the embodiments are generally applicable to any type of direct communication between UEs involving device-to-device (D2D) communication, such as LTE SL.
[0263] The embodiments are described from the perspective of remote UE and relay UE. In addition, it is assumed that the SL UE and its serving network node, such as gNB (if the UE is within NW coverage), operate using the same radio access technology (RAT), such as NR, LTE, etc. However, all embodiments are applicable to any RAT combination between the SL UE and its serving network node without loss of meaning.
[0264] A link or radio link that transmits signals between at least two UEs for D2D operation is referred to herein as a sidelink (SL). Signals transmitted between UEs for D2D operation are referred to herein as SL signals. The term SL may also be interchangeably referred to as a D2D link, a V2X link, a proximity service link, a peer link, a PC5 link, etc. SL signals may also be interchangeably referred to as V2X signals, D2D signals, proximity service signals, PC5 signals, peer signals, etc.
[0265] These embodiments are applicable to L2 relay scenarios. For example, these embodiments are applicable to L2-based UE-to-NW (U2N) relay. A UE-to-NW relay UE is denoted as a relay UE.
[0266] Furthermore, the term "direct path" is used to describe a direct connection between a UE and a network operating over a Uu interface. Furthermore, the term "indirect path" is used to describe a connection between a UE and a network via or with the help of an intermediate node referred to as a "relay UE" in this disclosure. In both terms, the UE is also referred to as a "remote UE" without losing any meaning.
[0267] As used herein, the term "Uu interface" may refer to a wireless interface between a terminal device and a network node (such as a base station, gNB, eNB, etc.). The term "PC5 interface" may refer to a radio interface between any two terminal devices.
[0268] Figure 3a A flow chart of a method according to an embodiment of the present disclosure is shown, which can be implemented in a first user equipment (UE) or as a first user equipment, or can be performed by a device that is communicatively coupled to the first UE. Therefore, the device can provide a device or module for implementing various parts of the method 300, and a device or module for implementing other processes in combination with other components.
[0269] In one embodiment, the first UE may be a remote UE in a UE-to-network relay scenario.
[0270] In one embodiment, PDCP duplication of the RB is activated, the first UE has established / set up at least one PC5 RLC entity for the RB on an indirect path through the relay UE, and established / set up at least one UuRLC entity for the RB on a direct path.
[0271] In one embodiment, at least one Uu RLC entity may be a primary RLC entity and at least one PC5 RLC entity may be a secondary RLC entity.
[0272] In one embodiment, at least one PC5 RLC entity may be a primary RLC entity and at least one Uu RLC entity may be a secondary RLC entity.
[0273] At block 302, for an uplink radio bearer that has been activated via Packet Data Convergence Protocol (PDCP) duplication, a first UE may determine that a PDCP protocol data unit (PDU) has been successfully delivered to a network node via a relay UE on a UE-to-network relay path.
[0274] The first UE may determine in various ways that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path. For example, the first UE may receive information from the relay UE or the network node indicating that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path. For example, when the network node receives the PDCP PDU, it may send such information to the first UE on the UE-to-network relay path or the UE-to-network direct path. The relay UE may send such information when receiving the PDCP PDU from the first UE, or send the PDCP PDU to the network node, or receive such information from the network node. In addition, the first UE may determine that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path based on any other suitable information from the relay UE or the network node.
[0275] In one embodiment, the first UE may receive a radio link control (RLC) status report from the relay UE. The RLC status report indicates that the PDCP PDU has been successfully sent to the relay UE in the side link. The first UE may determine based on the RLC status report that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path. For example, this determination method may be used when the Uu link quality of the relay UE is good enough or greater than a threshold value so that the relay UE can ensure that the PDCP PDU can be sent to the network node. Since this determination method is fast, the first UE can quickly discard the duplicated PDCP PDU on another path and save resources.
[0276] In one embodiment, the first UE may receive a PDCP status report from the network node. The PDCP status report indicates that the PDCP PDU has been successfully received by the network node from the UE to the network relay path. The first UE may determine based on the PDCP status report that the PDCP PDU has been successfully delivered to the network node on the UE to the network relay path. The determination method is accurate.
[0277] In one embodiment, a PDCP status report is received from a network node when at least one of the following conditions is met: an upper layer requests a PDCP entity reestablishment, an upper layer requests a PDCP data recovery, an upper layer requests an uplink data switch, an upper layer reconfigures a PDCP entity to release a dual active protocol stack (DAPS) and daps-SourceRelease is configured at the upper layer, an upper layer determines that a PDCP status report needs to be triggered, a periodic timer expires, or PDCP duplication is activated and at least one path of the PDCP duplication is a UE-to-network relay path. The above trigger conditions may be considered jointly or individually.
[0278] The following trigger conditions may be the same as the corresponding trigger conditions described in clause 5.4.1 of TS 38.323v16.6.0: upper layers request PDCP entity re-establishment, upper layers request PDCP data recovery, upper layers request uplink data handover, upper layers reconfigure PDCP entity to release dual active protocol stack (DAPS), and daps-SourceRelease is configured at upper layers.
[0279] The upper layer may determine that a PDCP status report needs to be triggered due to various reasons. For example, when a PDCP receiving entity needs to provide a PDCP status report to a PDCP sending entity, the upper layer may determine that a PDCP status report needs to be triggered due to various reasons. When the link quality of the UE to the network direct path is good enough or greater than a threshold, the upper layer may determine that a PDCP status report needs to be triggered. When a network node receives a request for a PDCP status report from a first UE, the upper layer may determine that a PDCP status report needs to be triggered.
[0280] The periodic timer may be set to any suitable value. For example, the periodic timer may be set by an operator.
[0281] In one embodiment, when PDCP duplication has been activated and at least one path is a relay path, the network node may send a PDCP status report to the first UE.
[0282] In one embodiment, the upper layer may include a radio resource control (RRC) layer.
[0283] In one embodiment, the PDCP status report is received from the network node via a UE-to-network direct path and / or a UE-to-network relay path.
[0284] In one embodiment, the first UE may receive a first signaling from the relay UE. The first signaling indicates that the relay UE has received an RLC status report of a PDCP PDU from the network node. The RLC status report indicates that the PDCP PDU has been successfully transmitted to the network node over the Uu link. The first UE may determine based on the first signaling that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path. For example, the first signaling may be RRC signaling (e.g., PC5-RRC) or MAC CE.
[0285] In one embodiment, the first UE may receive second signaling from the network node via a direct path from the UE to the network. The second signaling indicates that the PDCP PDU has been successfully received by the network node via the UE to the network relay path. The first UE may determine based on the second signaling that the PDCP PDU has been successfully delivered to the network node via the relay UE on the UE to the network relay path.
[0286] For example, a PDCP entity of a network node such as a gNB may provide a status report to the first UE via the direct path, indicating successful reception of the PDCP PDU over the indirect path. A network node such as a gNB may indicate successful reception of the PDCP PDU over the indirect path using other signaling options including RRC signaling, MAC CE, or L1 signaling (e.g., DCI on PDCCH) via the direct path.
[0287] In one embodiment, the method for determining that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path may be configured by the network node, pre-configured in the UE and relay UE, or hard-coded in the specification.
[0288] At block 304, the first UE may discard at least one duplicated PDCP PDU on the path from at least one other UE to the network. By discarding, resources may be saved.
[0289] In one embodiment, the at least one other UE-to-network path may include at least one of a UE-to-network relay path or a UE-to-network direct path.
[0290] For example, there may be a UE-to-network relay path and a UE-to-network direct path. When a PDCP PDU has been successfully delivered to a network node via a relay UE on the UE-to-network relay path, the first UE may discard at least one duplicated PDCP PDU or RLC PDU on the UE-to-network direct path.
[0291] For example, there may be two UE-to-network relay paths. When a PDCP PDU has been successfully delivered to the network node via the relay UE on one UE-to-network relay path, the first UE may discard at least one duplicated PDCP PDU or RLC PDU on another UE-to-network direct path.
[0292] For example, there may be two UE-to-network relay paths and one UE-to-network direct path. When a PDCP PDU has been successfully delivered to a network node through the relay UE on one UE-to-network relay path, the first UE may discard at least one duplicated PDCP PDU on another UE-to-network indirect path and the UE-to-network direct path.
[0293] As a first example, in order to discard at least one duplicated PDCP PDU on the UE-to-network relay path, the first UE may perform at least one of the following actions:
[0294] - discard the associated PDCP PDU or PC5 RLC PDU, or
[0295] -Send signaling to the relay UE, indicating the relevant PDCP PDU or PC5 RLC PDU that needs to be discarded. The signaling can be carried by PC5-RRC signaling, MAC CE or control PDU of the protocol layer, such as the Sidelink Adaptation Layer (SRAP).
[0296] As a second example, to discard at least one duplicated PDCP PDU on the UE-to-network direct path, the first UE may discard the associated PDCP PDU or Uu RLC PDU.
[0297] Figure 3b A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in or as a first user equipment (UE), or communicatively coupled to the first UE. Therefore, the device can provide a device or module for implementing various parts of the method 310, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0298] At block 312, the first UE may receive third signaling from the network node. The third signaling indicates deactivation of PDCP duplication of the uplink radio bearer.
[0299] In one embodiment, the third signaling may be received from the network node via a UE-to-network relay path or a UE-to-network direct path.
[0300] In one embodiment, when the third signaling is received from the network node via the UE-to-network direct path, the third signaling may include at least one of RRC signaling, MAC CE, or L1 signaling (eg, DCI on PDCCH).
[0301] At block 314, the first UE may perform at least one of the following operations: deactivate PDCP duplication of the uplink radio bearer; discard at least one first duplicate PDCP PDU and / or RLC service data unit (SDU) associated with the uplink radio bearer; or send fourth signaling to the relay UE. The fourth signaling instructs the relay UE to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0302] The fourth signaling may include at least one of PC5 RRC signaling or MAC CE.
[0303] In one embodiment, at least one second duplicate PDCP PDU and / or RLC SDU may include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from the first UE and stored in at least one sidelink RLC entity, or at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer stored in at least another Uu RLC entity.
[0304] Figure 3c A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a first user equipment (UE), or implemented as a first user equipment, or communicatively coupled to a first UE. Therefore, the device can provide a device or module for implementing various parts of method 320, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0305] At block 322, the first UE may receive fifth signaling from the network node. The fifth signaling indicates deactivation of PDCP duplication of uplink radio bearers of at least one sidelink RLC entity.
[0306] In one embodiment, the fifth signaling may be received from the network node via a UE-to-network relay path or a UE-to-network direct path.
[0307] In one embodiment, when the fifth signaling is received from the network node via the UE-to-network direct path, the fifth signaling may include at least one of RRC signaling, MAC CE, or L1 signaling (eg, DCI on PDCCH).
[0308] At block 324, the first UE may perform at least one of discarding at least one third duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer of the at least one RLC entity or sending a sixth signaling to the relay UE. The sixth signaling instructs the relay UE to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and the at least one RLC entity.
[0309] In one embodiment, the sixth signaling may include at least one of PC5 RRC signaling or MAC CE.
[0310] In one embodiment, at least one fourth replicate PDCP PDU and / or RLC SDU may include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from at least one RLC entity of the first UE and stored in one or more sidelink RLC entities of the relay UE, or include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from at least one RLC entity of the first user equipment and stored in at least one Uu RLC entity of the relay user equipment.
[0311] Figure 3d A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a first user equipment (UE), or implemented as a first user equipment, or communicatively coupled to a first UE. Therefore, the device can provide a device or module for implementing various parts of the method 330, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0312] At block 332, the first UE may maintain a mapping table between Uu PDCP PDUs and sidelink RLC PDUs in the UE-to-network relay path.
[0313] In one embodiment, the mapping table may include at least one of a mapping of a Uu PDCP PDU to one or more PC5 RLC PDUs, or a mapping of one or more Uu PDCP PDUs to PC5 RLC PDUs.
[0314] In one embodiment, the Uu PDCP PDU in the mapping table is identified by a sequence number (SN) value of the Uu PDCP PDU, and the sidelink RLC PDU is identified by the SN value of the sidelink RLC PDU.
[0315] In one embodiment, when a Uu PDCP PDU is delivered to the sidelink RLC layer, an entry corresponding to the Uu PDCP PDU is added to the mapping table, and when the sidelink RLC layer indicates to the Uu PDCP layer that the Uu PDCP PDU has been successfully transmitted to the recipient, or when a timer or counter expires and the Uu PDCP PDU has become invalid, the entry corresponding to the Uu PDCP PDU is deleted.
[0316] For example, the mapping table may show at least one of the following:
[0317] -How the Uu PDCP PDU is mapped to one or more PC5 RLC PDUs, or
[0318] - How one or more Uu PDCP PDUs are mapped to PC5 RLC PDUs.
[0319] In one embodiment, the sequence number (SN) values of the Uu PDCP PDU and PC5 RLC PDU may be used as input in the mapping table.
[0320] In one embodiment, when a Uu PDCP PDU is delivered to the PC5 RLC layer, a new entry corresponding to the Uu PDCP PDU is added to the table. The entry is deleted when the PC5 RLC layer indicates to the Uu PDCP layer that the corresponding Uu PDCP PDU has been successfully transmitted to the recipient, which means that either the corresponding PC5 RLC status report has been received from the recipient, indicating successful transmission, or a timer or counter has expired, indicating that the Uu PDCP PDU is invalid because the PC5 RLC has exhausted all retransmission opportunities of the related PC5 RLC PDU.
[0321] Based on the mapping table, whenever the remote UE determines to discard the duplicate PDCP PDU or RLC PDU, the remote UE may perform at least one of the following actions:
[0322] - discard the associated PDCP PDU or PC5 RLC PDU, or
[0323] -Send signaling to the relay UE, indicating the relevant PDCP PDU or PC5 RLC PDU that needs to be discarded. The signaling can be carried by PC5-RRC signaling, MAC CE or control PDU of the protocol layer, such as the Sidelink Adaptation Layer (SRAP).
[0324] In one embodiment, the signaling between the network node and the first UE may include at least one of RRC signaling, a medium access control (MAC) control element (CE), or layer 1 signaling.
[0325] In one embodiment, the signaling between the relay UE and the first UE may include at least one of RRC signaling, MAC CE, or a control PDU of a protocol layer. For example, the control PDU of the protocol layer may be a sidelink adaptation layer (SRAP).
[0326] Figure 4aA flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a relay UE, implemented as a relay UE, or communicatively coupled to a relay UE. Therefore, the device can provide a device or module for implementing various parts of method 400, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0327] At block 402, the relay UE may receive a PDCP PDU for an uplink radio bearer from a first UE, wherein the uplink radio bearer has been activated through PDCP duplication.
[0328] In one embodiment, the PDCP PDU will be delivered to the network node via at least one of a UE-to-network relay path or a UE-to-network direct path.
[0329] At block 404, the relay UE may send an indication to the first UE that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path.
[0330] In one embodiment, the indication is an RLC status report indicating that the PDCP PDU has been successfully sent to the relay UE on the sidelink. For example, when the relay UE has successfully received the PDCP PDU from the first UE, the relay UE may send an RLC status report to the first UE.
[0331] In one embodiment, the indication indicates that the relay UE has received an RLC status report of the PDCP PDU from the network node. For example, when the relay UE has received an RLC status report of the PDCP PDU from the network node, the relay UE may send an indication to the first UE indicating that the relay UE has received an RLC status report of the PDCP PDU from the network node.
[0332] In one embodiment, which indication to use may be configured by the network node, preconfigured in the first UE and the relay UE, or hard-coded in the specification.
[0333] Figure 4b A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a relay UE, implemented as a relay UE, or communicatively coupled to a relay UE. Therefore, the device can provide a device or module for implementing various parts of method 410, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0334] At block 412, the relay UE may receive signaling from the first UE. The signaling instructs the relay UE to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer. The signaling may be PC5-RRC signaling, MACCE, or control PDU of a protocol layer, such as a sidelink adaptation layer (SRAP).
[0335] At block 414, the relay UE may discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0336] In one embodiment, at least one second duplicate PDCP PDU and / or RLC SDU may include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from the first UE and stored in at least one sidelink RLC entity, or at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer stored in at least one Uu RLC entity.
[0337] Figure 4c A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a relay UE, implemented as a relay UE, or communicatively coupled to a relay UE. Therefore, the device can provide a device or module for implementing various parts of method 420, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0338] At block 422, the relay UE may receive signaling from the first UE. The signaling instructs the relay UE to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and at least one RLC entity. The signaling may be PC5-RRC signaling, MAC CE, or control PDU of a protocol layer, such as a sidelink adaptation layer (SRAP).
[0339] At block 424, the relay UE may discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and the at least one RLC entity.
[0340] In one embodiment, at least one fourth duplicate PDCP PDU and / or RLC SDU may include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from at least one RLC entity of the first UE and stored in one or more sidelink RLC entities, or include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from at least one RLC entity of the first user equipment and stored in at least one Uu RLC entity.
[0341] Figure 4d A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a relay UE, implemented as a relay UE, or communicatively coupled to a relay UE. Therefore, the device can provide a device or module for implementing various parts of method 430, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0342] At block 432, the relay UE may receive signaling including an identifier of the first UE from the network node. The signaling indicates discarding duplicate PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer. The relay UE may use the identifier of the first UE to know to which uplink radio bearer the relay UE belongs.
[0343] At block 434, the relay UE may discard the duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0344] Figure 4e A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a relay UE, implemented as a relay UE, or communicatively coupled to a relay UE. Therefore, the device can provide a device or module for implementing various parts of method 440, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0345] At block 442, the relay UE may receive signaling including an identifier of the first UE from the network node. The signaling indicates to deactivate at least one RLC entity of an uplink radio bearer in the UE-to-network relay path.
[0346] At block 444, the relay UE may deactivate at least one RLC entity of the uplink radio bearer in the UE-to-network relay path.
[0347] Figure 4f A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a relay UE, implemented as a relay UE, or communicatively coupled to a relay UE. Therefore, the device can provide a device or module for implementing various parts of method 450, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0348] At block 452, the relay UE may maintain a mapping table between Uu PDCP PDUs and sidelink RLC PDUs in the UE-to-network relay path.
[0349] In one embodiment, the mapping table may include at least one of a mapping of a PC5 RLC PDU to one or more Uu PDCP PDUs, or a mapping of one or more PC5 RLC PDUs to Uu PDCP PDUs.
[0350] In one embodiment, the Uu PDCP PDU in the mapping table is identified by a sequence number (SN) value of the Uu PDCP PDU, and the sidelink RLC PDU is identified by the SN value of the sidelink RLC PDU, an identifier of an uplink radio bearer, and an identifier of the first UE.
[0351] In one embodiment, the signaling between the network node and the relay UE may include at least one of RRC signaling, a medium access control (MAC) control element (CE), or layer 1 signaling.
[0352] In one embodiment, the signaling between the relay UE and the first UE may include at least one of RRC signaling, MAC CE, or control PDU of the protocol layer.
[0353] Figure 5a A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a network node, implemented as a network node, or communicatively coupled to a network node. Therefore, the device can provide a device or module for implementing various parts of the method 500, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0354] At block 502, for a downlink radio bearer that has been activated with PDCP duplication, the network node may determine that a PDCP PDU has been successfully delivered to a first UE through a relay UE on a UE-to-network relay path.
[0355] The network node may determine in various ways that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path. For example, the network node may receive information from the relay UE or the first UE indicating that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path. For example, when the first UE receives the PDCP PDU, it may send such information to a network node on the UE-to-network relay path or the UE-to-network direct path. When the relay UE receives the PDCP PDU from the network node, the relay UE may send such information to the network node, or send the PDCP PDU to the first UE, or receive such information from the first UE. In addition, the network node may determine that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path based on any other suitable information from the relay UE or the first UE.
[0356] In one embodiment, the network node may receive an RLC status report from the relay UE. The RLC status report indicates that the PDCP PDU has been successfully transmitted to the relay UE of the Uu link. The network node may determine based on the RLC status report that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path.
[0357] In one embodiment, the network node may receive a PDCP status report from the first UE. The PDCP status report indicates that the PDCP PDU has been successfully received by the first UE over the UE-to-network relay path. The network node may determine, based on the PDCP status report, that the PDCP PDU has been successfully delivered to the first UE over the UE-to-network relay path.
[0358] In one embodiment, the network node receives the PDCP status report when at least one of the upper layer requests PDCP entity reestablishment, the upper layer requests PDCP data recovery, the upper layer requests downlink data switching, the upper layer reconfigures the PDCP entity to release the dual active protocol stack (DAPS) and daps-SourceRelease is configured at the upper layer, the upper layer determines that a PDCP status report needs to be triggered, a periodic timer expires, or PDCP duplication has been activated and at least one path for PDCP duplication is a UE-to-network relay path. The above trigger conditions may be considered jointly or individually.
[0359] In one embodiment, the upper layer may include a radio resource control (RRC) layer.
[0360] In one embodiment, the network node may receive the PDCP status report via a direct path and / or a UE-to-network relay path.
[0361] In one embodiment, the network node may receive first signaling from the relay UE. The first signaling indicates that the relay UE has received an RLC status report of a PDCP PDU from the first UE. The RLC status report indicates that the PDCP PDU has been successfully sent to the first UE in the sidelink. The network node may determine based on the first signaling that the PDCP PDU has been successfully delivered to the first UE via the relay UE on the UE-to-network relay path.
[0362] In one embodiment, the network node may receive second signaling from the first UE via a UE-to-network direct path. The second signaling indicates that the PDCP PDU has been successfully received by the first UE via the UE-to-network relay path. The network node may determine based on the second signaling that the PDCP PDU has been successfully delivered to the first UE via the relay UE on the UE-to-network relay path.
[0363] In one embodiment, the method for determining that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path is configured by the core network entity, or hard-coded in the specification.
[0364] At block 504, the network node may discard at least one duplicated PDCP PDU on at least one other UE-to-network path.
[0365] In one embodiment, the at least one other UE-to-network path may include at least one of a UE-to-network relay path or a UE-to-network direct path.
[0366] For example, there may be one UE-to-network relay path and one UE-to-network direct path. When the PDCP PDU has been successfully delivered to the network node via the relay UE on the UE-to-network relay path, the first UE may discard at least one duplicated PDCP PDU on the UE-to-network direct path.
[0367] For example, there may be two UE-to-network relay paths. When a PDCP PDU has been successfully delivered to a first UE via a relay UE on one UE-to-network relay path, the network node may discard at least one duplicate PDCP PDU on another UE-to-network direct path.
[0368] For example, there may be two UE-to-network relay paths and one UE-to-network direct path. When a PDCP PDU has been successfully delivered to a first UE via a relay UE on one UE-to-network relay path, the network node may discard at least one duplicated PDCP PDU on another UE-to-network indirect path and the UE-to-network direct path.
[0369] As a first example, in order to discard at least one duplicated PDCP PDU on the UE-to-network relay path, the network node may perform at least one of the following actions:
[0370] - discard the associated RLC PDU, or
[0371] -Send signaling to the relay UE, indicating the associated PC5 RLC PDU that needs to be discarded. The signaling can be carried by RRC signaling, MAC CE or L1 signaling.
[0372] As a second example, when the network node discards at least one duplicated PDCP PDU on the UE-to-network direct path, the first UE may discard the associated Uu RLC PDU.
[0373] Figure 5b A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a network node, implemented as a network node, or communicatively coupled to a network node. Therefore, the device can provide a device or module for implementing various parts of the method 510, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0374] At block 512, the network node may determine to deactivate the PDCP duplication of the downlink radio bearer.
[0375] At block 514, the network node may perform at least one of the following operations: deactivate the PDCP duplication of the downlink radio bearer; send a third signaling to the first UE; send a fourth signaling to the first UE; send a fifth signaling to the relay UE; discard at least one duplicated PDCP PDU and / or RLC SDU associated with the downlink radio bearer; or send a sixth signaling to the relay UE. The sixth signaling indicates discarding at least one second duplicated PDCP PDU and / or RLC SDU associated with the downlink radio bearer. The third signaling indicates deactivation of the PDCP duplication of the downlink radio bearer. The fourth signaling indicates deactivation of at least one sidelink RLC entity of the downlink radio bearer on the UE to network relay path. The fifth signaling indicates deactivation of at least one Uu and PC5 RLC entity of the downlink radio bearer on the UE to network relay path.
[0376] In one embodiment, the at least one second duplicate PDCP PDU and / or RLC SDU may include at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer received from the network node and stored in at least one Uu RLC entity of the relay UE, or at least one of one or more PDCP PDUs and / or RLC SDUs associated with an uplink radio bearer stored in the relay UE.
[0377] Figure 6 A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device in a network node, implemented as a network node, or communicatively coupled to a network node. Therefore, the device can provide a device or module for implementing various parts of method 600, and a device or module for implementing other processes in combination with other components. For some parts described in the above embodiments, their description is omitted here for the sake of brevity.
[0378] At block 602, the network node may maintain a mapping table between Uu PDCP PDUs and Uu RLC PDUs in a UE-to-network relay path.
[0379] In one embodiment, the mapping table may include at least one of a mapping of a Uu PDCP PDU to one or more Uu RLC PDUs, or a mapping of one or more Uu PDCP PDUs to a Uu RLC PDU.
[0380] In one embodiment, the Uu PDCP PDU in the mapping table is identified by a sequence number (SN) value of the Uu PDCP PDU, and the Uu RLC PDU is identified by a sequence number (SN) value of the Uu RLC PDU.
[0381] In one embodiment, when a Uu PDCP PDU is delivered to the Uu RLC layer, an entry corresponding to the Uu PDCP PDU is added to the mapping table, and when the Uu RLC indicates to the Uu PDCP layer that the Uu PDCP PDU has been successfully sent to the recipient, or when a timer or counter expires and the Uu PDCP PDU has become invalid, the entry corresponding to the Uu PDCP PDU is deleted.
[0382] In one embodiment, the signaling between the network node and the first UE may include at least one of RRC signaling, a medium access control (MAC) control element (CE), or layer 1 signaling.
[0383] In one embodiment, the signaling between the relay UE and the first UE may include at least one of RRC signaling, MAC CE, or control PDU of the protocol layer.
[0384] Based on the mapping table, whenever the network node determines to discard the duplicate PDCP PDU of the RB belonging to a certain remote UE, the network node may perform at least one of the following actions:
[0385] - discard the associated Uu RLC PDU which has not been transmitted, or
[0386] -Send signaling to the relay UE. The signaling indicates the relevant Uu RLC PDU that needs to be discarded. The signaling can be carried by Uu-RRC signaling, MAC CE or control PDU of the protocol layer, such as the sidelink adaptation layer (SRAP).
[0387] Hereinafter, Group A embodiments and Group B embodiments are described.
[0388] Group A Embodiments—Handling PDCP Duplication of UL RBs
[0389] For a UL radio bearer (RB) activated by PDCP duplication, whenever a remote UE (e.g., UE1) successfully transmits a PDCP PDU on one of multiple paths (e.g., a UE-to-network relay path and a UE-to-network direct path), the remote UE may discard the duplicated PDCP PDUs on other paths.
[0390] For the A-1 embodiment, for a UL radio bearer (RB), the remote UE determines whether the PDCP PDU has been successfully delivered to a network node on an indirect path, such as a gNB, using one of the following options.
[0391] Option 1: One of the associated PC5 transmitting RLC entities has received a corresponding RLC status report from the relay UE (eg, the relay UE), indicating that the PDCP PDU has been successfully transmitted in the PC5 hop.
[0392] Option 2: The PDCP entity (e.g., transmitting entity) of the remote UE has received a corresponding PDCP status report from a network node such as a gNB, indicating that the PDCP PDU has been successfully received by the network node such as the gNB through an indirect path. In order to enable the PDCP entity (e.g., receiving entity) to provide a status report to the PDCP transmitting entity, in addition to the following existing PDCP status report triggering conditions (as described in TS 38.323v16.6.0 clause 5.4.1), at least one new condition may be configured for the PDCP receiving entity (e.g., a network node such as a gNB in this case):
[0393] - Upper layers request PDCP entity re-establishment;
[0394] - Upper layers request PDCP data recovery;
[0395] - Upper layers request uplink data switching; or
[0396] - The upper layer reconfigures the PDCP entity to release DAPS and configures daps-SourceRelease in the upper layer (ie RRC).
[0397] In one embodiment, at least one of the following new conditions is configured for the PDCP receiving entity:
[0398] - The upper layer (i.e., RRC) determines that a PDCP status report needs to be triggered, for example, the PDCP receiving entity needs to provide a PDCP status report to the PDCP sending entity,
[0399] - the periodic timer has expired, or
[0400] -PDCP duplication is activated and at least one path is a relay path.
[0401] Option 3: The relay UE has sent signaling to the remote UE indicating that the relay UE has received a corresponding RLC status report for the PDCP PDU from a network node such as a gNB, indicating that the PDCP PDU has been successfully transmitted in the Uu hop. The signaling can be transmitted in one of the following ways:
[0402] -RRC signaling (e.g., PC5-RRC), or
[0403] -MAC-CE.
[0404] Option 4: A network node such as the gNB provides signaling to the remote UE over the direct path to acknowledge receipt of the PDCP PDU over the indirect path.
[0405] For this option, the PDCP entity of the network node may provide a status report to the remote UE over the direct path, indicating successful reception of the PDCP PDU over the indirect path.
[0406] For this option, a network node such as a gNB may use other signaling options including RRC signaling, MACCE, or L1 signaling (e.g., DCI on PDCCH) to indicate successful reception of a PDCP PDU over the indirect path via the direct path.
[0407] Which option should be applied by the remote UE and relay UE can be configured by a network node such as the gNB or captured in the specification in a hard-coded manner.
[0408] For the A-2 embodiment, for a UL radio bearer (RB), upon receiving signaling indicating PDCP duplication deactivation for the RB from a network node such as a gNB, the remote UE performs at least one of the following corresponding actions:
[0409] -Deactivate PDCP duplication of RB;
[0410] - instruct the PC5 RLC entity of the remote UE associated with the RB to discard all duplicated PDCP PDUs / RLC SDUs;
[0411] - Sending signaling (e.g., PC5 RRC signaling or MAC CE) to the relay UE, indicating that the relay UE should discard all duplicate PDCP PDUs / RLC SDUs associated with the RB received from the remote UE, including: those received in a PC5 hop and stored in all PC5 RLC entities associated with the RB, - Those stored in the Uu RLC entity of the Uu hop associated with the RB.
[0412] For the A-3 embodiment, for a UL radio bearer (RB), upon receiving signaling indicating PDCP duplication deactivation of at least one related RLC entity (e.g., PC5 RLC entity) from a network node such as a gNB, the remote UE performs at least one of the following corresponding actions:
[0413] - The PC5 RLC entity of the remote UE indicated in the instructing signaling discards all duplicated PDCP PDUs / RLC SDUs;
[0414] - Sending signaling (e.g., PC5 RRC signaling or MAC CE) to the relay UE, indicating that the relay UE should discard all duplicate PDCP PDUs / RLC SDUs associated with the RB received from the remote UE, including: those received in the PC5 hop and stored in the PC5 RLC entity indicated in the signalling, or - Those associated with the RBs stored in the Uu RLC entity of the Uu hop and received from the indicated PC5 RLC entity.
[0415] In addition, the relay UE and the remote UE may receive signaling from a network node such as a gNB to deactivate the RLC entity of the RB in the indirect path.
[0416] In addition, the relay UE may receive signaling from a network node such as a gNB to discard duplicate PDCP PDUs and / or RLC SDUs associated with the RB. In the case where the relay UE serves multiple remote UEs, the signaling should also indicate the ID of the remote UE to which the RB belongs.
[0417] For the A-4 embodiment, for an UL radio bearer (RB) with PDCP duplication activated, the remote UE maintains a mapping table between the Uu PDCP PDU and the PC5 RLC PDU in the indirect path. In other words, the mapping table shows at least one of the following:
[0418] -How the Uu PDCP PDU is mapped to one or more PC5 RLC PDUs, or
[0419] - How one or more Uu PDCP PDUs are mapped to PC5 RLC PDUs.
[0420] The sequence number (SN) value of the Uu PDCP PDU and PC5 RLC PDU is used as input in the mapping table.
[0421] When a Uu PDCP PDU is delivered to the PC5 RLC layer, a new entry corresponding to the Uu PDCP PDU is added to the table. This entry is deleted when the PC5 RLC layer indicates to the Uu PDCP layer that the corresponding Uu PDCP PDU has been successfully transmitted to the receiver, which means:
[0422] - a corresponding PC5 RLC status report indicating successful transmission has been received from the recipient, or
[0423] - Expiration of a timer or counter indicating that the Uu PDCP PDU has become invalid because the PC5 RLC layer has exhausted all retransmission opportunities for the associated PC5 RLC PDU.
[0424] Based on the mapping table, whenever the remote UE determines to discard the duplicated PDCP PDU, the remote UE may perform at least one of the following actions:
[0425] - Discard the associated PC5 RLC PDU.
[0426] -Sending signaling to the relay UE indicating that the associated PC5 RLC PDU needs to be discarded. The signaling can be carried by PC5-RRC signaling, MAC CE or control PDU of the protocol layer, such as Sidelink Adaptation Layer (SRAP).
[0427] For the A-5 embodiment, for the UL radio bearer, the relay UE maintains a mapping table between the PC5 RLC PDU and the Uu RLC PDU. In other words, the mapping table shows at least one of the following:
[0428] - How the PC5 RLC PDU is mapped into one or more Uu RLC PDUs, or
[0429] - How one or more PC5 RLC PDUs are mapped to Uu RLC PDUs.
[0430] In the mapping table, the remote UE ID, RB ID and SN of PC5 RLC PDU are used as identifiers of PC5 RLC PDUs, because there may be multiple remote UEs connected to the relay UE at the same time. In addition, the SN of Uu RLC PDU is also used as input in the mapping table to represent Uu RLC PDUs.
[0431] Based on the mapping table, whenever the relay UE receives signaling from the remote UE to discard one or more PC5 RLC PDUs, the relay UE will find the corresponding Uu RLC PDU. The relay UE can also discard these indicated PC5 RLC PDUs and / or Uu RLC PDUs.
[0432] The relay UE may also have some Uu RLC SDUs in the queue and waiting for transmission over the Uu hop. For these Uu RLC SDUs, if the relay UE has received signaling from the remote UE to discard one or more PC5 RLC PDUs, the relay UE may find the corresponding Uu RLC SDDUs and discard them.
[0433] Group B Embodiments—Handling PDCP Duplication of DL RBs
[0434] For a DL radio bearer (RB) that has been activated with PDCP duplication, whenever a network node such as a gNB successfully transmits a PDCP PDU on one of multiple paths (e.g., UE-to-network relay path and UE-to-network direct path), the network node such as the gNB may discard the duplicated PDCP PDUs on other paths.
[0435] For the B-1 embodiment, for a DL radio bearer (RB), a network node such as a gNB determines whether a PDCP PDU has been successfully delivered to a remote UE over an indirect path using one of the following options:
[0436] Option 1: One of the associated Uu transmitting RLC entities has received a corresponding RLC status report from the relay UE indicating that the PDCP PDU has been successfully transmitted in the Uu hop.
[0437] Option 2: The PDCP entity (e.g., transmitting entity) of a network node such as a gNB has received a corresponding PDCP status report from a remote UE. In order to enable the PDCP entity (e.g., receiving entity) to provide a status report to the PDCP sending entity, in addition to the following existing PDCP status report triggering conditions (as described in TS 38.323v16.6.0 Section 5.4.1), at least one new condition may be configured for the PDCP receiving entity (e.g., the remote UE in this case):
[0438] The upper layer requests the PDCP entity to reestablish;
[0439] The upper layer requests PDCP data recovery;
[0440] The upper layer requests uplink data switching;
[0441] The upper layer reconfigures the PDCP entity to release the DAPS and configures daps-SourceRelease in the upper layer (ie, RRC).
[0442] In one embodiment, at least one of the following new conditions is configured for the PDCP receiving entity:
[0443] - The upper layer (i.e., RRC) determines that a PDCP status report needs to be triggered, for example, the PDCP receiving entity needs to provide a PDCP status report to the PDCP sending entity,
[0444] - the periodic timer has expired, or
[0445] -PDCP duplication is activated and at least one path is a relay path.
[0446] Option 3: The relay UE has sent signaling to a network node such as the gNB, indicating that the relay UE has received the corresponding RLC status report for the PDCP PDU from the remote UE, which means that the PDCP PDU has been successfully transmitted in the PC5 hop. The signaling can be carried in one of the following ways:
[0447] -RRC signaling, or
[0448] -MAC CE.
[0449] Option 4: The remote UE provides signaling to a network node such as the gNB over the direct path. This signaling acknowledges receipt of the PDCP PDU over the indirect path.
[0450] For this option, the PDCP entity of the remote UE can provide a status report to a network node such as the gNB over the direct path. The status report indicates the successful reception of the PDCP PDU over the indirect path.
[0451] For this option, the remote UE may use other signaling options including RRC signaling, MACCE, or L1 signaling (e.g., UCI on PUCCH) over the direct path to indicate successful reception of the PDCP PDU over the indirect path.
[0452] Which option a network node such as a gNB should apply may be configurable by a core network entity, or captured in a hard-coded manner in the specification, or until implementation of a network node such as a gNB.
[0453] For the B-2 embodiment, for a DL radio bearer (RB), a network node such as a gNB may determine to deactivate a PDCP duplication of the RB. The network node such as the gNB performs at least one of the following corresponding actions for deactivating the PDCP duplication of the RB:
[0454] -Deactivate PDCP duplication of RB;
[0455] - Sending signaling to the remote UE to deactivate the PDCP copy of the RB;
[0456] - Sending signaling to the remote UE to deactivate the PC5 RLC entity on the indirect path;
[0457] - Send signaling to the relay UE to deactivate the Uu and PC5 RLC entities on the indirect path;
[0458] - instruct the Uu RLC entity associated with the RB of the network node such as the gNB to discard all duplicated PDCP PDUs / RLC SDUs;
[0459] - Sending signaling (e.g., Uu RRC signaling or MAC CE) to the relay UE to indicate that the relay UE should discard all duplicate PDCP PDUs / RLC SDUs associated with RBs of the remote UE received from a network node such as a gNB, including:
[0460] - those received in a Uu hop and stored in all Uu RLC entities associated with the RBs of the remote UE, and
[0461] - Those associated with the remote UE's RBs stored in the PC5 RLC entity of the PC5 hop.
[0462] For the B-3 embodiment, for a DL radio bearer (RB), upon receiving signaling indicating PDCP duplication deactivation of at least one RLC entity (such as a PC5 RLC entity) associated with the DL RB from a network node such as a gNB, the remote UE performs at least one of the following corresponding actions:
[0463] - The PC5 RLC entity of the remote UE indicated in the instructing signalling discards all duplicated PDCP PDUs / RLC SDUs from the associated DL RBs;
[0464] - Sending signaling (e.g., PC5 RRC signaling or MAC CE) to the relay UE indicating that the relay UE should discard all duplicate PDCP PDUs / RLC SDUs received from the indicated DL RB and associated with the indicated RLC entity, which are received from the gNB, including:
[0465] - those received in the Uu hop and stored in the Uu RLC entity indicated in the signalling, and
[0466] - Those stored in the PC5 RLC entity indicated in the signalling.
[0467] For the B-4 embodiment, for a DL radio bearer (RB) with PDCP duplication activated, a network node such as a gNB maintains a mapping table between Uu PDCP PDU and Uu RLC PDU in an indirect path. In other words, the mapping table shows at least one of the following:
[0468] -How Uu PDCP PDU is mapped to one or more Uu RLC PDUs
[0469] - How one or more Uu PDCP PDUs are mapped to Uu RLC PDUs
[0470] The SN of the Uu PDCP PDU and Uu RLC PDU is used as input in the mapping table.
[0471] When a Uu PDCP PDU is delivered to the Uu RLC layer, a new entry corresponding to the Uu PDCP PDU is added to the table. This entry is deleted when the Uu RLC layer indicates to the Uu PDCP layer that the corresponding Uu PDCP PDU has been successfully transmitted to the receiver, which means:
[0472] - a corresponding Uu RLC status report indicating successful transmission has been received from the receiver, or
[0473] The expiration of the timer or counter indicates that the Uu PDCP PDU has become invalid because the Uu RLC layer has exhausted all retransmission opportunities for the associated PC5 RLC PDU.
[0474] Based on the mapping table, whenever a network node such as a gNB determines to discard a duplicate PDCP PDU of an RB belonging to a certain remote UE (e.g., a remote UE), the network node such as the gNB may perform at least one of the following actions:
[0475] - discarding the associated Uu RLC PDUs that have not been transmitted.
[0476] -Sending signaling of the related Uu RLC PDUs that need to be discarded to the relay UE. The signaling can be carried by Uu RRC signaling, MAC CE or control PDU of the protocol layer, such as the Sidelink Adaptation Layer (SRAP).
[0477] For the B-5 embodiment, for the DL radio bearer, the relay UE maintains a mapping table between the Uu RLC PDU and the PC5 RLC PDU. In other words, the mapping table shows at least one of the following:
[0478] - How the Uu RLC PDU is mapped to one or more PC5 RLC PDUs, and
[0479] - How one or more Uu RLC PDUs are mapped to PC5 RLC PDUs.
[0480] In the mapping table, the remote UE ID, RB ID and SN of the UuRLC PDU are used as the identifier of the Uu RLC PDU, since there may be multiple remote UEs connected to the relay UE at the same time as the relay UE. In addition, the SN of the PC5 RLC PDU is also used as an input in the mapping table to represent the PC5 RLC PDU.
[0481] Based on the mapping table, whenever the relay UE receives signaling from a network node such as a gNB to discard one or more Uu RLC PDUs, the relay UE finds the corresponding PC5 RLC PDU. The relay UE may also discard these indicated Uu RLC PDUs and / or PC5 RLC PDUs.
[0482] For a UE connected to the same network node, such as a gNB, via both a direct path and an indirect path, various embodiments cover how to remove duplicate PDUs in the indirect path in situations including the following:
[0483] 1) If successful delivery of the PDCP data PDU is confirmed by one of the associated AM RLC entities,
[0484] 2) If DRB is instructed to deactivate PDCP duplication, or
[0485] 3) If deactivation of PDCP duplication is indicated for at least one associated RLC entity.
[0486] The embodiments cover the UL (uplink) case and the DL (downlink) case respectively.
[0487] Embodiments herein may provide many advantages, the following is a non-exhaustive list of examples. In some embodiments herein, it may avoid transmitting redundant duplicate PDUs. In some embodiments herein, it may ensure that PDCP duplication works properly in Uu and SL mixed multipath scenarios. Embodiments herein are not limited to the above features and advantages. Those skilled in the art will recognize additional features and advantages after reading the following detailed description.
[0488] Figure 7 700 is a block diagram showing an apparatus suitable for implementing some embodiments of the present disclosure. For example, any one of the first UE, relay UE and network node described above may be implemented as the apparatus 700 or implemented by the apparatus 700.
[0489] The apparatus 700 includes at least one processor 721, such as a digital processor (DP), and at least one memory (MEM) 722 coupled to the processor 721. The apparatus 700 may also include a transmitter TX and a receiver RX723 coupled to the processor 721. The MEM 722 stores a program (PROG) 724. The PROG 724 may include instructions that, when executed on the associated processor 721, enable the apparatus 700 to operate according to embodiments of the present disclosure. The combination of the at least one processor 721 and the at least one MEM 722 may form a processing device 725 suitable for implementing various embodiments of the present disclosure.
[0490] Various embodiments of the present disclosure may be implemented by a computer program executable by one or more of the processor 721 , software, firmware, hardware, or a combination thereof.
[0491] As non-limiting examples, MEM 722 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
[0492] By way of non-limiting example, processor 721 may be of any type suitable to the local technical environment, and may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture.
[0493] In an embodiment where the apparatus is implemented as or at a first UE, the memory 722 contains instructions executable by the processor 721, whereby the first UE operates according to any method related to the first UE as described above.
[0494] In an embodiment where the apparatus is implemented as or at a relay UE, the memory 722 contains instructions executable by the processor 721, whereby the relay UE operates according to any method related to the relay UE as described above.
[0495] In embodiments where the apparatus is implemented as or at a network node, the memory 722 contains instructions executable by the processor 721, whereby the network node operates according to any of the methods related to network nodes described above.
[0496] Figure 8a 800 is a block diagram showing a first UE according to an embodiment of the present disclosure. As shown in the figure, the first UE 800 includes a determination module 801, which is configured to determine that, for an uplink radio bearer that has been activated by packet data convergence protocol (PDCP) duplication, a PDCP protocol data unit (PDU) has been successfully delivered to a network node through a relay UE on a UE-to-network relay path. The first UE 800 may also include a discard module 802, which is configured to discard at least one duplicated PDCP PDU on at least one other UE-to-network path.
[0497] In one embodiment, the first UE 800 may further include a first receiving module 803 configured to receive a third signaling from the network node. The third signaling indicates deactivation of the PDCP duplication of the uplink radio bearer.
[0498] In one embodiment, the first UE 800 may further include a first execution module 804, which is configured to perform at least one of the following operations: deactivate PDCP duplication of the uplink radio bearer; discard at least one first duplicate PDCP PDU and / or RLC service data unit (SDU) associated with the uplink radio bearer; or send a fourth signaling to the relay UE. The fourth signaling instructs the relay UE to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0499] In one embodiment, the first UE 800 may further include a second receiving module 805 configured to receive fifth signaling from the network node. The fifth signaling indicates deactivation of PDCP duplication of uplink radio bearers of at least one sidelink RLC entity.
[0500] In one embodiment, the first UE 800 may further include a second execution module 806, which is configured to perform at least one of the following operations: discarding at least one third duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer of at least one RLC entity; or sending a sixth signaling to the relay UE. The sixth signaling instructs the relay UE to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and at least one RLC entity.
[0501] In one embodiment, the first UE 800 may further include a maintenance module 807 configured to maintain a mapping table between Uu PDCP PDUs and sidelink RLC PDUs in a UE-to-network relay path.
[0502] Figure 8b 8 is a block diagram illustrating a relay UE 850 according to an embodiment of the present disclosure. As shown, the relay UE 850 includes a first receiving module 851 configured to receive a PDCP PDU of an uplink radio bearer from a first UE. The uplink radio bearer has been activated by PDCP duplication. The relay UE 850 includes a sending module 852 configured to send an indication to the first UE that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path.
[0503] In one embodiment, the relay UE 850 may further include a second receiving module 853 configured to receive signaling from the first UE. The signaling instructs the relay UE to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer. The relay UE 850 may also include a first discarding module 854 configured to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0504] In one embodiment, the relay UE 850 may further include a third receiving module 855 configured to receive signaling from the first UE. The signaling instructs the relay UE to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and at least one RLC entity. The relay UE 850 may also include a second discarding module 856 configured to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and at least one RLC entity.
[0505] In one embodiment, the relay UE 850 may further include a fourth receiving module 857, which is configured to receive signaling including an identifier of the first UE from the network node. The signaling indicates discarding the duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer. The relay UE 850 may also include a third discarding module 858, which is configured to discard the duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
[0506] In one embodiment, the relay UE 850 may further include a fifth receiving module 859 configured to receive signaling including an identifier of the first UE from the network node. The signaling indicates to deactivate at least one RLC entity of the uplink radio bearer in the UE-to-network relay path. The relay UE 850 may further include a deactivation module 860 configured to deactivate at least one RLC entity of the uplink radio bearer in the UE-to-network relay path.
[0507] In one embodiment, the relay UE 850 may further include a maintenance module 861 configured to maintain a mapping table between Uu PDCP PDUs and sidelink RLC PDUs in the UE-to-network relay path.
[0508] Figure 8c 8 is a block diagram illustrating a network node according to an embodiment of the present disclosure. As shown in the figure, the network node 880 includes a first determination module 881, which is configured to determine that, for a downlink radio bearer that has been activated by PDCP duplication, a PDCP PDU has been successfully delivered to a first UE through a relay UE on a UE-to-network relay path. The network node 880 may also include a discard module 882, which is configured to discard at least one duplicated PDCP PDU on at least one other UE-to-network path.
[0509] In one embodiment, the network node 880 may further include a second determining module 883 configured to determine to deactivate the PDCP duplication of the downlink radio bearer.
[0510] In one embodiment, the network node 880 may further include an execution module 884, which is configured to perform at least one of the following operations: deactivate PDCP duplication of a downlink radio bearer; send a third signaling to the first UE; send a fourth signaling to the first UE; send a fifth signaling to the relay UE; discard at least one duplicated PDCP PDU and / or RLC SDU associated with the downlink radio bearer; or send a sixth signaling to the relay UE. The sixth signaling indicates discarding at least one second duplicated PDCP PDU and / or RLC SDU associated with the downlink radio bearer. The fifth signaling indicates deactivating at least one Uu and PC5 RLC entity of the downlink radio bearer on the UE to network relay path. The third signaling indicates deactivating PDCP duplication of the downlink radio bearer. The fourth signaling indicates deactivating at least one sidelink RLC entity of the downlink radio bearer on the UE to network relay path.
[0511] In one embodiment, the network node 880 may further include a maintenance module 885 configured to maintain a mapping table between Uu PDCP PDUs and Uu RLC PDUs in a UE-to-network relay path.
[0512] The term unit or module may have a conventional meaning in the field of electronics, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, procedures, calculations, output and / or display functions, etc., such as those described herein.
[0513] For the functional unit, the first UE, relay UE or network node may not need a fixed processor or memory, and any computing resources and storage resources can be arranged from the first UE, relay UE or network node in the communication system. The introduction of virtualization technology and network computing technology can improve the efficiency of network resource utilization and the flexibility of the network.
[0514] According to one aspect of the present disclosure, there is provided a computer program product, which is tangibly stored on a computer-readable storage medium and includes instructions, which when executed on at least one processor cause the at least one processor to perform any of the above methods.
[0515] According to one aspect of the present disclosure, a computer-readable storage medium storing instructions is provided. When executed by at least one processor, the instructions cause the at least one processor to perform any of the methods described above.
[0516] Furthermore, an exemplary overall communication system including a terminal device and a network node will be described as follows.
[0517] An embodiment of the present disclosure provides a communication system, including a host, the host including: a processing circuit configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network includes a base station such as the above-mentioned network node and / or a terminal device such as the above-mentioned first UE and relay UE.
[0518] In an embodiment of the present disclosure, the system further includes a terminal device. The terminal device is configured to communicate with the base station.
[0519] In an embodiment of the present disclosure, the processing circuit of the host is configured to execute a host application to provide user data; and the terminal device includes a processing circuit configured to execute a client application associated with the host application.
[0520] An embodiment of the present disclosure also provides a communication system, the communication system comprising a host, the host comprising: a communication interface configured to receive user data transmitted from a terminal device; a base station. The transmission is from the terminal device to the base station. The base station is the above-mentioned network node, and / or the terminal device is the above-mentioned.
[0521] In an embodiment of the present disclosure, the processing circuit of the host is configured to execute a host application. The terminal device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host.
[0522] Fig. 9 is a schematic diagram illustrating a wireless network according to some embodiments.
[0523] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks (such as Fig. 9 For simplicity, Fig. 9 The wireless network of FIG. 1 depicts only the network 1006, the network nodes 1060 (corresponding to the network side nodes) and 1060b, and the WDs (corresponding to the terminal devices) 1010, 1010b, and 1010c. In practice, the wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device, such as a fixed telephone, a service provider, or any other network node or terminal device. In the components shown, the network node 1060 and the wireless device (WD) 1010 are depicted in more detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate wireless devices to access and / or use services provided by or via the wireless network.
[0524] A wireless network may include and / or interface with any type of communication, telecommunication, data, cellular and / or wireless network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as the IEEE 802.11 standard; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.
[0525] The network 1006 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
[0526] The network node 1060 and the WD 1010 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether through wired or wireless connections.
[0527] As used herein, a network node refers to a device that is capable, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (Bs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)). Base stations can be classified according to the coverage they provide (or, in other words, their transmit power levels), and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may be integrated with an antenna as an antenna-integrated radio, or may not be integrated with an antenna. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) devices, such as MSR BS, network controllers, such as radio network controllers (RNC) or base station controllers (BSC), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), core network nodes (such as MSC, MME), O&M nodes, OSS nodes, SON nodes, positioning nodes (such as E-SMLC) and / or MDT. As another example, the network node can be a virtual network node, as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) that is capable, configured, arranged and / or operable to enable and / or provide access to a wireless network to a wireless device, or to provide a certain service to a wireless device that has access to a wireless network.
[0528] exist Fig. 9 In FIG. 1 , the network node 1060 includes a processing circuit 1070, a device readable medium 1080, an interface 1090, an auxiliary device 1084, a power supply 1086, a power supply circuit 1087, and an antenna 1062. Fig. 9The network node 1060 shown in the example wireless network of can represent a device including the combination of hardware components shown, but other embodiments can include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node 1060 are depicted as a single box located within a larger box, or nested within multiple boxes, in practice, the network node may include multiple different physical components that make up the single shown component (for example, the device readable medium 1080 may include multiple separate hard drives and multiple RAM modules).
[0529] Similarly, the network node 1060 can be composed of multiple physically independent components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which can have its own corresponding components. In certain scenarios where the network node 1060 includes multiple individual components (e.g., BTS and BSC components), one or more individual components can be shared between several network nodes. For example, a single RNC can control multiple NodeBs. In this scenario, each unique NodeB and RNC pair can be regarded as a separate network node in some cases. In some embodiments, the network node 1060 can be configured to support multiple radio access technologies (RATs). In such an embodiment, some components can be copied (e.g., separate device readable media 1080 for different RATs), and some components can be reused (e.g., RATs can share the same antenna 1062). The network node 1060 can also include multiple groups of various components shown for different wireless technologies integrated into the network node 1060, such as GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1060 .
[0530] The processing circuit 1070 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) provided by the network node as described herein. Such operations performed by the processing circuit 1070 may include processing information obtained by the processing circuit 1070, for example, by converting the obtained information to other information, comparing the obtained or converted information to information stored in the network node, and / or performing one or more operations based on the obtained or converted information and making a determination as a result of the processing.
[0531] The processing circuit 1070 may include a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, combination of one or more of resources, or a combination of hardware, software and / or encoded logic, which may provide network node 1060 functionality alone or in combination with other network node 1060 components, such as device readable medium 1080. For example, the processing circuit 1070 may execute instructions stored in the device readable medium 1080 or in a memory within the processing circuit 1070. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 1070 may include a system on a chip (SOC).
[0532] In some embodiments, processing circuitry 1070 may include one or more of radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074. In some embodiments, radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074 may be on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of RF transceiver circuitry 1072 and baseband processing circuitry 1074 may be on the same chip or set of chips, boards, or units.
[0533] In some embodiments, some or all of the functions provided by a network node, base station, eNB, or other such network node described herein may be performed by processing circuit 1070 executing instructions stored on device-readable medium 1080 or memory within processing circuit 1070. In alternative embodiments, some or all of the functions may be provided by processing circuit 1070 without executing instructions stored on a separate or discrete device-readable medium, such as in a hardwired manner. In any of these embodiments, processing circuit 1070 may be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to separate processing circuits 1070 or other components of network node 1060, but are shared by network node 1060 as a whole and / or by end users and wireless networks.
[0534] Device readable medium 1080 may include any form of volatile or non-volatile computer readable memory, including but not limited to persistent memory, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD), or digital video disk (DVD)), and / or any other volatile, non-volatile, non-transitory device readable and / or computer executable storage device that stores information, data, and / or instructions that can be used by processing circuit 1070. Device readable medium 1080 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that can be executed by processing circuit 1070 and used by network node 1060. Device readable medium 1080 may be used to store any computations performed by processing circuit 1070 and / or any data received via interface 1090. In some embodiments, processing circuit 1070 and device readable medium 1080 may be considered integrated.
[0535] Interface 1090 is used for wired or wireless communication of signaling and / or data between network node 1060, network 1006 and / or WD1010. As shown, interface 1090 includes port / terminal 1094 for sending data to network 1006 and receiving data from network 1006 via wired connection. Interface 1090 also includes radio front-end circuit 1092, which can be coupled to antenna 1062, or in some embodiments, coupled to a part of antenna 1068. Radio front-end circuit 1092 includes filter 1098 and amplifier 1096. Radio front-end circuit 1092 can be connected to antenna 1062 and processing circuit 1070. Radio front-end circuit can be configured to adjust the signal transmitted between antenna 1062 and processing circuit 1070. Radio front-end circuit 1092 can receive digital data, which will be sent to other network nodes or WDs via wireless connection. The radio front end circuit 1092 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1098 and / or amplifiers 1096. The radio signal may then be transmitted through the antenna 1062. Similarly, when receiving data, the antenna 1062 may collect the radio signal, which may then be converted into digital data by the radio front end circuit 1092. The digital data may be delivered to the processing circuit 1070. In other embodiments, the interface may include different components and / or different combinations of components.
[0536] In some alternative embodiments, the network node 1060 may not include a separate radio front end circuit 1092, and instead, the processing circuit 1070 may include the radio front end circuit and may be connected to the antenna 1062 without the need for a separate radio front end circuit 1092. Similarly, in some embodiments, all or some of the RF transceiver circuit 1072 may be considered part of the interface 1090. In other embodiments, the interface 1090 may include one or more ports or terminals 1094, the radio front end circuit 1092, and the RF transceiver circuit 1072 as part of a radio unit (not shown), and the interface 1090 may communicate with the baseband processing circuit 1074, which is part of a digital unit (not shown).
[0537] Antenna 1062 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1062 may be coupled to radio front-end circuit 1092 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1062 may include one or more omnidirectional, sector or panel antennas for sending / receiving radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from devices within a specific area, and panel antennas may be line-of-sight antennas for sending / receiving radio signals in a relatively straight line. In some cases, the use of multiple antennas may be referred to as MIMO. In some embodiments, antenna 1062 may be separate from network node 1060 and may be connected to network node 1060 via an interface or port.
[0538] Antenna 1062, interface 1090 and / or processing circuit 1070 can be configured to perform any receiving operation and / or certain acquisition operation performed by the network node as described herein. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network device. Similarly, antenna 1062, interface 1090 and / or processing circuit 1070 can be configured to perform any transmitting operation performed by the network node as described herein. Any information, data and / or signal can be transmitted to a wireless device, another network node and / or any other network device.
[0539] The power circuit 1087 may include or be coupled to a power management circuit and is configured to supply power to the components of the network node 1060 to perform the functions described herein. The power circuit 1087 may receive power from the power supply 1086. The power supply 1086 and / or the power circuit 1087 may be configured to provide power to the various components of the network node 1060 in a form suitable for the various components (e.g., at the voltage and current levels required by each respective component). The power supply 1086 may be included in the power circuit 1087 and / or the network node 1060 or external to it. For example, the network node 1060 may be connected to an external power source (e.g., a power outlet) via an input circuit or an interface such as a cable, whereby the external power source supplies power to the power circuit 1087. As another example, the power supply 1086 may include a power source in the form of a battery or a battery pack, which is connected to or integrated in the power circuit 1087. If the external power source fails, the battery can provide backup power. Other types of power sources, such as photovoltaic devices, may also be used.
[0540] Alternative embodiments of network node 1060 may include Fig. 9 Additional components other than those shown may be responsible for providing certain aspects of the network node functionality, including any functionality described herein and / or any functionality required to support the subject matter described herein. For example, the network node 1060 may include a user interface device to allow information to be input into the network node 1060 and to allow information to be output from the network node 1060. This may allow a user to perform diagnostics, maintenance, repair, and other management functions on the network node 1060.
[0541] As used herein, a wireless device (WD) refers to a device that can, configure, arrange and / or operably communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with a user equipment (UE) in this article. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network on a predetermined schedule when triggered by an internal or external event or in response to a request from a network. Examples of WD include, but are not limited to, smartphones, mobile phones, mobile phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, notebook embedded devices (LEEs), laptop computer installation devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted wireless terminal devices, etc. WD can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), in which case it can be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement, and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery or household or personal appliances (such as refrigerators, televisions, etc.), personal wearable devices (such as watches, fitness trackers, etc.). In other cases, WD may represent a vehicle or other device that can monitor and / or report its operating status or other functions related to its operation. WD as described above can represent an endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, the WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
[0542] As shown, wireless device 1010 includes antenna 1011, interface 1014, processing circuit 1020, device readable medium 1030, user interface device 1032, auxiliary device 1034, power supply 1036 and power supply circuit 1037. WD 1010 can include multiple groups of one or more of the components shown for different wireless technologies supported by WD 1010, such as GSM, WCDMA, LTE, NR, WiFi, WiMAX or Bluetooth wireless technology, to name a few. These wireless technologies can be integrated into the same or different chips or chipsets as other components within WD 1010.
[0543] Antenna 1011 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and connected to interface 1014. In some alternative embodiments, antenna 1011 may be separated from WD 1010 and connected to WD 1010 via an interface or port. Antenna 1011, interface 1014 and / or processing circuit 1020 may be configured to perform any receiving or transmitting operation performed by WD as described herein. Any information, data and / or signal may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 1011 may be considered an interface.
[0544] As shown, the interface 1014 includes a radio front-end circuit 1012 and an antenna 1011. The radio front-end circuit 1012 includes one or more filters 1018 and an amplifier 1016. The radio front-end circuit 1014 is connected to the antenna 1011 and the processing circuit 1020 and is configured to condition the signal transmitted between the antenna 1011 and the processing circuit 1020. The radio front-end circuit 1012 may be coupled to the antenna 1011 or a portion of the antenna 1011. In some embodiments, the WD 1010 may not include a separate radio front-end circuit 1012; instead, the processing circuit 1020 may include a radio front-end circuit and may be connected to the antenna 1011. Similarly, in some embodiments, some or all of the RF transceiver circuit 1022 may be considered as part of the interface 1014. The radio front-end circuit 1012 may receive digital data, which will be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 1012 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filters 1018 and / or amplifiers 1016. The radio signal may then be transmitted via antenna 1011. Similarly, when receiving data, antenna 1011 may collect the radio signal, which may then be converted to digital data by radio front end circuit 1012. The digital data may be passed to processing circuit 1020. In other embodiments, the interface may include different components and / or different combinations of components.
[0545] Processing circuit 1020 may include a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, a combination of one or more of a resource, or a combination of hardware, software, and / or encoded logic, which may provide WD 1010 functionality alone or in conjunction with other WD 1010 components, such as device readable medium 1030. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuit 1020 may execute instructions stored in device readable medium 1030 or in a memory within processing circuit 1020 to provide functionality disclosed herein.
[0546] As shown, the processing circuit 1020 includes one or more of the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 1020 of the WD 1010 may include a SOC. In some embodiments, the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 1024 and the application processing circuit 1026 may be combined into one chip or a set of chips, and the RF transceiver circuit 1022 may be on a separate chip or chipset. In another alternative embodiment, part or all of the RF transceiver circuit 1022 and the baseband processing circuit 1024 may be on the same chip or chipset, and the application processing circuit 1026 may be on a separate chip or chipset. In some other alternative embodiments, part or all of the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026 can be combined in the same chip or chipset. In some embodiments, the RF transceiver circuit 1022 can be part of the interface 1014. The RF transceiver circuit 1022 can condition the RF signal for the processing circuit 1020.
[0547] In some embodiments, some or all of the functions performed by the WD described herein may be provided by a processing circuit 1020 executing instructions stored on a device-readable medium 1030, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by the processing circuit 1020 without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of these specific embodiments, the processing circuit 1020 may be configured to perform the functions described, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to separate processing circuits 1020 or other components of the WD 1010, but are generally enjoyed by the WD 1010 as a whole and / or by end users and wireless networks.
[0548] Processing circuit 1020 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) performed by WD as described herein. Such operations performed by processing circuit 1020 may include processing information obtained by processing circuit 1020 by, for example, converting the obtained information into other information, comparing the obtained or converted information with information stored by WD 1010, and / or performing one or more operations based on the obtained or converted information and making determinations as a result of the processing.
[0549] Device readable medium 1030 may be used to store computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that can be executed by processing circuit 1020. Device readable medium 1030 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device for storing information, data, and / or instructions that may be used by processing circuit 1020. In some embodiments, processing circuit 1020 and device readable medium 1030 may be considered integrated.
[0550] The user interface device 1032 may provide a component that allows a human user to interact with the WD 1010. This interaction may be in a variety of forms, such as visual, auditory, tactile, etc. The user interface device 1032 may be used to generate output to the user and allow the user to provide input to the WD 1010. The type of interaction may vary depending on the type of user interface device 1032 installed in the WD 1010. For example, if the WD 1010 is a smart phone, the interaction may be performed through a touch screen; if the WD 1010 is a smart meter, the interaction may be performed through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 1032 may include input interfaces, devices, and circuits, as well as output interfaces, devices, and circuits. The user interface device 1032 is configured to allow information to be input into the WD 1010 and is connected to the processing circuit 1020 to allow the processing circuit 1020 to process the input information. The user interface device 1032 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a USB port, or other input circuits. The user interface device 1032 is also configured to allow information to be output from the WD 1010 and to allow the processing circuit 1020 to input information from the WD 1010. The user interface device 1032 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 1032, the WD 1010 can communicate with end users and / or wireless networks and allow them to benefit from the functionality described herein.
[0551] Auxiliary device 1034 is operable to provide more specific functions that cannot normally be performed by a WD. This may include specialized sensors for measuring for various purposes, interfaces for other types of communication such as wired communication, etc. The inclusion and type of components of auxiliary device 1034 may vary depending on the embodiment and / or scenario.
[0552] In some embodiments, the power source 1036 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery. The WD 1010 may also include a power circuit 1037 for delivering power from the power source 1036 to various parts of the WD 1010 that require power from the power source 1036 to perform any functions described or indicated herein. In some embodiments, the power circuit 1037 may include a power management circuit. The power circuit 1037 may additionally or alternatively be used to receive power from an external power source; in this case, the WD 1010 may be connected to an external power source (e.g., a power outlet) via an input circuit or an interface such as a power cable. In some embodiments, the power circuit 1037 may also be used to deliver power from an external power source to the power source 1036. For example, this may be used to charge the power source 1036. The power circuit 1037 may perform any formatting, conversion, or other modifications to the power from the power source 1036 so that the power is suitable for the various components of the WD 1010 being powered.
[0553] Fig.10 is a schematic diagram illustrating a user equipment according to some embodiments.
[0554] Fig.10 An embodiment of a UE in accordance with various aspects described herein is shown. As used herein, a user equipment or UE does not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user, but may not be associated with a specific human user (e.g., a smart sprinkler controller), or may not initially be associated with a specific human user. Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart meter). UE 1100 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Fig.10 As shown, UE 1100 is an example of a WD configured to communicate in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Therefore, although Fig.10 It is UE, but the components discussed in this article are also applicable to WD and vice versa.
[0555] exist Fig.10In the embodiment, UE 1100 includes a processing circuit 1101, which is operably coupled to an input / output interface 1105, a radio frequency (RF) interface 1109, a network connection interface 1111, a memory 1115 including a random access memory (RAM) 1117, a read-only memory (ROM) 1119, and a storage medium 1121, a communication subsystem 1131, a power supply 1113, and / or any other components, or any combination thereof. The storage medium 1121 includes an operating system 1123, an application 1125, and data 1127. In other embodiments, the storage medium 1121 may include other similar types of information. Some UEs may utilize Fig.10 All components shown in the , or only a subset of these components may be utilized. The level of integration between components may vary from UE to UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0556] exist Fig.10 , processing circuit 1101 may be configured to process computer instructions and data. Processing circuit 1101 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored-program, general-purpose processors, such as a microprocessor or digital signal processor (DSP), and appropriate software; or any combination of the foregoing. For example, processing circuit 1101 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
[0557] In the depicted embodiment, the input / output interface 1105 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 1100 may be configured to use an output device via the input / output interface 1105. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE 1100. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 1100 may be configured to use an input device via the input / output interface 1105 to allow a user to capture information into the UE 1100. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
[0558] exist Fig.10 In the embodiment of the present invention, the RF interface 1109 can be configured to provide a communication interface to RF components, such as transmitters, receivers, and antennas. The network connection interface 1111 can be configured to provide a communication interface to the network 1143a. The network 1143a can include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, other similar networks, or any combination thereof. For example, the network 1143a can include a Wi-Fi network. The network connection interface 1111 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 1111 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software, or firmware, or can be implemented separately.
[0559] RAM 1117 may be configured to be connected to processing circuit 1101 via bus 1102 to provide storage or caching of data or computer instructions during execution of software programs such as operating systems, applications, and device drivers. ROM 1119 may be configured to provide computer instructions or data to processing circuit 1101. For example, ROM 1119 may be configured to store unchanged low-level system code or data for basic system functions such as basic input and output (I / O) stored in non-volatile memory, startup, or receiving keystrokes from a keyboard. Storage medium 1121 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cassette, or flash drive. In one example, storage medium 1121 may be configured to include operating system 1123, application 1125 such as a web browser application, widget or gadget engine, or other application, and data file 1127. The storage medium 1121 may store any of a variety of operating systems or combinations of operating systems for use by the UE 1100 .
[0560] The storage medium 1121 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory such as a user identity module or a removable user identity (SIM / RUIM) module, other memory or any combination thereof. The storage medium 1121 may allow the UE 1100 to access computer executable instructions, applications, etc. stored on a transient or non-transient storage medium to unload data or upload data. An article such as utilizing a communication system may be tangibly embodied in the storage medium 1121, which may include a device-readable medium.
[0561] exist Fig.10In the embodiment of the present invention, the processing circuit 1101 can be configured to communicate with the network 1143b using the communication subsystem 1131. The network 1143a and the network 1143b can be the same network or different networks. The communication subsystem 1131 can be configured to include one or more transceivers for communicating with the network 1143b. For example, the communication subsystem 1131 can be configured to include one or more transceivers for communicating with another device capable of wireless communication, such as another WD, UE or a base station of a radio access network (RAN), according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc., One or more remote transceivers communicate. Each transceiver may include a transmitter 1133 and / or a receiver 1135 to respectively implement a transmitter or receiver function suitable for a RAN link (e.g., frequency allocation, etc.). In addition, the transmitter 1133 and the receiver 1135 of each transceiver may share circuit components, software or firmware, or may be implemented separately.
[0562] In the illustrated embodiment, the communication functions of the communication subsystem 1131 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a global positioning system (GPS) to determine the location, other similar communication functions, or any combination thereof. For example, the communication subsystem 1131 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1143b may include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, other similar networks, or any combination thereof. For example, the network 1143b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1113 may be configured to provide alternating current (AC) or direct current (DC) to the components of the UE 1100.
[0563] The features, benefits and / or functions described herein may be implemented in one component of UE 1100 or may be divided across multiple components of UE 1100. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 1131 may be configured to include any component described herein. In addition, the processing circuit 1101 may be configured to communicate with any such component via a bus 1102. In another example, any such component may be represented by program instructions stored in a memory, which, when executed by the processing circuit 1101, perform the corresponding functions described herein. In another example, the functions of any such component may be divided between the processing circuit 1101 and the communication subsystem 1131. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.
[0564] Fig.11 is a schematic diagram illustrating a virtualized environment according to some embodiments.
[0565] Fig.11 12 is a schematic block diagram illustrating a virtualized environment 1200 in which the functions implemented by some embodiments may be virtualized. In the present context, virtualization means creating a virtual version of a device or apparatus, which may include virtualized hardware platforms, storage devices, and network resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized wireless access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components (e.g., by one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).
[0566] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1200 hosted by one or more hardware nodes 1230. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), then the network nodes may be fully virtualized.
[0567] These functions may be implemented by one or more applications 1220 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.) that are used to implement some features, functions, and / or benefits of some embodiments disclosed herein. The applications 1220 run in a virtualized environment 1200 that provides hardware 1230 including a processing circuit 1260 and a memory 1290-1. The memory 1290-1 contains instructions 1295 that can be executed by the processing circuit 1260, whereby the applications 1220 are operable to provide one or more features, benefits, and / or functions disclosed herein.
[0568] The virtualized environment 1200 includes a general or special purpose network hardware device 1230 that includes a set of one or more processors or processing circuits 1260, which may be commercial off-the-shelf (COTS) processors, dedicated application-specific integrated circuits (ASICs), or any other type of processing circuit including digital or analog hardware components or special purpose processors. Each hardware device may include a memory 1290-1, which may be a non-persistent memory for temporarily storing instructions 1295 or software executed by the processing circuit 1260. Each hardware device may include one or more network interface controllers (NICs) 1270, also known as network interface cards, which include a physical network interface 1280. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium 1290-2 in which software 1295 and / or instructions executable by the processing circuit 1260 are stored. The software 1295 may include any type of software, including software for instantiating one or more virtualization layers 1250 (also known as hypervisors), software for executing virtual machines 1240, and software that allows them to perform functions, features, and / or benefits associated with some embodiments described herein.
[0569] The virtual machine 1240 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and may be run by a corresponding virtualization layer 1250 or hypervisor. Different embodiments of instances of the virtual device 1220 may be implemented on one or more virtual machines 1240 and may be implemented in different ways.
[0570] During operation, processing circuitry 1260 executes software 1295 to instantiate a hypervisor or virtualization layer 1250, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1250 may present to virtual machines 1240 a virtual operating platform that appears to be network hardware.
[0571] like Fig.11As shown, hardware 1230 can be an independent network node with common or specific components. Hardware 1230 can include antenna 12225, and some functions can be implemented through virtualization. Alternatively, hardware 1230 can be part of a larger hardware cluster (for example, in a data center or customer premise equipment (CPE)), where many hardware nodes work together and are managed by management and orchestration (MANO) 12100, which is responsible for overseeing the life cycle management of application 1220.
[0572] Virtualization of hardware is sometimes referred to as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premises.
[0573] In the context of NFV, a virtual machine 1240 may be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each virtual machine 1240 and a portion of the hardware 1230 on which it executes, whether dedicated to that virtual machine and / or hardware shared by that virtual machine and other virtual machines 1240, form a separate virtual network element (VNE).
[0574] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 1240 on top of the hardware network infrastructure 1230 and corresponds to Fig.11 Application 1220.
[0575] In some embodiments, one or more radio units 12200 may be coupled to one or more antennas 12225, each radio unit including one or more transmitters 12220 and one or more receivers 12210. The radio units 12200 may communicate directly with the hardware nodes 1230 via one or more appropriate network interfaces, and may be used in conjunction with virtual components to provide radio capabilities to virtual nodes, such as radio access nodes or base stations.
[0576] In some embodiments, some signaling may be accomplished using a control system 12230 , which may alternatively be used for communications between the hardware node 1230 and the radio unit 12200 .
[0577] Fig.12 is a schematic diagram illustrating a telecommunications network connected to a host via an intermediate network according to some embodiments.
[0578] Reference Fig.12According to one embodiment, the communication system includes a telecommunication network 1310, such as a cellular network of the 3GPP type, which includes an access network 1311, such as a wireless access network, and a core network 1314. The access network 1311 includes a plurality of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 1313a, 1313b, 1313c. Each base station 1312a, 1312b, 1312c can be connected to the core network 1314 via a wired or wireless connection 1315. A first UE 1391 located in the coverage area 1313c is configured to be wirelessly connected to or paged by the corresponding base station 1312c. A relay UE 1392 in the coverage area 1313a can be wirelessly connected to the corresponding base station 1312a. Although multiple UEs 1391, 1392 are shown in this example, the disclosed embodiments are equally applicable to situations where only a UE is located in the coverage area or a only UE is connected to the corresponding base station 1312a or 1312b or 1312c.
[0579] The telecommunications network 1310 itself is connected to a host 1330, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host 1330 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 1321 and 1322 between the telecommunications network 1310 and the host 1330 may extend directly from the core network 1314 to the host 1330, or may be via an optional intermediate network 1320. The intermediate network 1320 may be a combination of one or more of a public, private, or managed network; the intermediate network 1320 (if any) may be a backbone network or the Internet; in particular, the intermediate network 1320 may include two or more sub-networks (not shown).
[0580] Fig.12The communication system as a whole implements a connection between connected UEs 1391, 1392 and a host 1330. The connection may be described as an over-the-top (OTT) connection 1350. The host 1330 and the connected UEs 1391, 1392 are configured to use the access network 1311, the core network 1314, any intermediate networks 1320, and possibly other infrastructure (not shown) as intermediaries to communicate data and / or signaling via the OTT connection 1350. The OTT connection 1350 may be transparent because the participating communication devices are unaware of the routing of uplink and downlink communications. For example, the base station 1312a or 1312b or 1312c may not need or need to be informed of the past routing of incoming downlink communications, the data of which originated from the host 1330 and will be forwarded (e.g., switched) to the connected UE 1391. Similarly, base station 1312a or 1312b or 1312c need not be aware of the future routing of outgoing uplink communications originating from UE 1391 to host 1330.
[0581] Fig.13 is a schematic diagram showing a host communicating with a user device via a base station through a partial wireless connection according to some embodiments.
[0582] Now refer to Fig.13 Describe the example implementation of the UE, base station and host discussed in the previous paragraph according to the embodiment. In the communication system 1400, the host 1410 includes hardware 1415, which includes a communication interface 1416, which is configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 1400. The host 1410 may also include a processing circuit 1418, which may have storage and / or processing capabilities. In particular, the processing circuit 1418 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host 1410 may also include software 1411, which is stored in the host 1410 or accessible by the host 1410 and can be executed by the processing circuit 1418. Software 1411 includes a host application 1412. The host application 1412 can be used to provide services to remote users, such as UE 1430 connected via an OTT connection 1450, which terminates at UE 1430 and host 1410. When providing services to remote users, the host application 1412 may provide user data transmitted using the OTT connection 1450 .
[0583] The communication system 1400 also includes a base station 1420, which is set in the telecommunication system and includes hardware 1425 to enable it to communicate with the host 1410 and the UE 1430. The hardware 1425 may include a communication interface 1426 for establishing and maintaining a wired or wireless connection with the interface of different communication devices of the communication system 1400, and a radio interface 1427 for establishing and maintaining a connection with a network located in the coverage area ( Fig.13 1470 of at least a wireless connection 1470 to a UE 1430 in the communication interface 1426. The communication interface 1426 may be configured to facilitate a connection 1460 with the host 1410. The connection 1460 may be direct or may be through a core network ( Fig.13 1420) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1425 of the base station 1420 also includes processing circuitry 1428, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) adapted to execute instructions. The base station 1420 also has software 1421 stored internally or accessible via an external connection.
[0584] The communication system 1400 also includes the UE 1430 already mentioned. Its hardware 1435 may include a radio interface 1437, which is configured to establish and maintain a wireless connection 1470 with a base station serving the coverage area where the UE 1430 is currently located. The hardware 1435 of the UE 1430 also includes a processing circuit 1438, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE 1430 may also include software 1431, which is stored in the UE 1430 or accessible by the UE 1430 and can be executed by the processing circuit 1438. The software 1431 includes a client application 1432. The client application 1432 can be used to provide services to human or non-human users via the UE 1430 with the support of the host 1410. In the host 1410, the executing host application 1412 can communicate with the executing client application 1432 through the OTT connection 1450 terminated at the UE 1430 and the host 1410. When providing services to the user, the client application 1432 can receive request data from the host application 1412 and provide user data in response to the request data. The OTT connection 1450 can transmit the request data and the user data. The client application 1432 can interact with the user to generate the user data it provides.
[0585] It should be noted that Fig.13 The host 1410, base station 1420 and UE 1430 shown in FIG. Fig.12The host 1330, one of the base stations 1312a, 1312b, 1312c and one of the UEs 1391, 1392 in the embodiment may be similar or identical. That is, the internal working principles of these entities may be as follows: Fig.13 As shown, independently, the surrounding network topology could be Fig.12 shown.
[0586] exist Fig.13 , an OTT connection 1450 is abstractly drawn to illustrate communications between a host 1410 and a UE 1430 through a base station 1420, without explicit reference to any intermediate devices and the precise routing of messages through those devices. The network infrastructure can determine the routing, which can be configured to hide the routing from the UE 1430 or from the service provider operating the host 1410, or both. The network infrastructure can also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network) while the OTT connection 1450 is active.
[0587] The wireless connection 1470 between the UE 1430 and the base station 1420 is consistent with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments improves the performance of the OTT service provided to the UE 1430 using the OTT connection 1450, where the wireless connection 1470 forms the last segment. More specifically, in some embodiments herein, it can avoid transmitting redundant duplicate PDUs. In some embodiments herein, it can ensure that PDCP duplication works properly in Uu and SL mixed multipath scenarios.
[0588] A measurement process may be provided for monitoring data rates, delays, and other factors that are improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 1450 between the host 1410 and the UE 1430 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 1450 may be implemented in the software 1411 and hardware 1415 of the host 1410, or in the software 1431 and hardware 1435 of the UE 1430. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 1450 passes; the sensor may participate in the measurement process by providing the values of the monitored quantities of the above examples, or providing the values of other physical quantities that the software 1411, 1431 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1450 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 1420, and the base station 1420 may not know or be aware of it. These processes and functions are known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling to facilitate host 1410 measurements of throughput, propagation time, latency, etc. The measurements may be accomplished by software 1411 and 1431 using OTT connection 1450 to send messages, particularly empty messages or "dummy" messages, while monitoring propagation time, errors, etc.
[0589] Fig.14 is a schematic diagram illustrating a method implemented in a communication system including a host, a base station and a user equipment according to some embodiments.
[0590] Fig.14 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.12 and 13 For simplicity of this disclosure, this section will only include Fig.14 Reference is made to the accompanying drawings of . In step 1510, the host provides user data. In sub-step 1511 of step 1510 (which may be optional), the host provides the user data by executing a host application. In step 1520, the host initiates a transmission carrying the user data to the UE. In step 1530 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host to the UE. In step 1540 (which may also be optional), the UE executes a client application associated with the host application executed by the host.
[0591] Fig.15 is a schematic diagram illustrating a method implemented in a communication system including a host, a base station and a user equipment according to some embodiments.
[0592] Fig.15 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.12 and 13 For simplicity of this disclosure, this section will only include Fig.15 Reference is made to the accompanying drawings of the present invention. In step 1610 of the method, the host provides user data. In an optional sub-step (not shown), the host provides the user data by executing a host application. In step 1620, the host initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission can be transmitted via a base station. In step 1630 (which may be optional), the UE receives the user data carried in the transmission.
[0593] Fig.16 is a schematic diagram illustrating a method implemented in a communication system including a host, a base station and a user equipment according to some embodiments.
[0594] Fig.16 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.12 and 13 For simplicity of this disclosure, this section will only include Fig.16 . In step 1710 (which may be optional), the UE receives input data provided by the host. Additionally or alternatively, in step 1720, the UE provides user data. In sub-step 1721 of step 1720 (which may be optional), the UE provides user data by executing a client application. In sub-step 1711 of step 1710 (which may be optional), the UE executes a client application that provides user data in response to received input data provided by the host. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner in which the user data is provided, the UE initiates a transmission of user data to the host in sub-step 1730 (which may be optional). In step 1740 of the method, the host receives user data sent from the UE in accordance with the teachings of the embodiments described throughout the present disclosure.
[0595] Fig.17 is a schematic diagram illustrating a method implemented in a communication system including a host, a base station and a user equipment according to some embodiments.
[0596] Fig.17 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.12 and13 To simplify this disclosure, this section will only include Fig.17 In step 1810 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. In step 1820 (which may be optional), the base station initiates a transmission of user data to the host. In step 1830 (which may be optional), the host receives the user data carried in the transmission initiated by the base station.
[0597] In addition, the present disclosure may also provide a carrier containing the above-mentioned computer program, wherein the carrier is one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disc or an electronic storage device such as a RAM (random access memory), a ROM (read-only memory), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray disc, etc.
[0598] The techniques described herein can be implemented in various ways, so that the device that implements one or more functions of the corresponding device described in conjunction with the embodiment includes not only prior art means, but also means for implementing one or more functions of the corresponding device described in conjunction with the implementation, and it can include separate means for each separate function, or can be configured to perform two or more functions. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (more than one module), or a combination thereof. For firmware or software, it can be implemented by a module (e.g., a process, a function, etc.) that performs the functions described herein.
[0599] Exemplary embodiments of the present invention have been described above with reference to block diagrams and flow charts of methods and apparatus. It should be understood that each block of the block diagrams and flow charts, and combinations of blocks in the block diagrams and flow charts, can be implemented in various ways, including computer program instructions. These computer program instructions can be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed in the computer or other programmable data processing device create a device for implementing the functions specified in the flow chart blocks.
[0600] In addition, although operations are described in a particular order, this should not be construed as requiring that the operations be performed in the particular order or sequence shown, or that all of the operations shown be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the subject matter described herein, but rather as descriptions of features that may be unique to a particular embodiment. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination.
[0601] Although this specification contains many specific implementation details, these details should not be interpreted as limitations on any implementation or the scope of what may be claimed, but rather as descriptions of features that are unique to a particular embodiment of a particular implementation. Certain features described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments. In addition, although the above-mentioned features may be described as functioning in certain combinations or even initially claimed, in some cases, one or more features in the claimed combination may be deleted from the combination, and the claimed combination may refer to a sub-combination or a variation of a sub-combination.
[0602] It will be apparent to those skilled in the art that, as technology advances, the inventive concept can be implemented in various ways. The above embodiments are provided to describe rather than limit the present disclosure, and it should be understood that modifications and variations may be made without departing from the spirit and scope of the present disclosure, as readily understood by those skilled in the art. Such modifications and variations are considered to be within the scope of the present disclosure and the appended claims. The scope of protection of the present disclosure is defined by the appended claims.
Claims
1. A method (300) performed by a first user equipment UE, comprising: For an uplink radio bearer activated using packet data convergence protocol PDCP duplication, determining (302) that a PDCP protocol data unit PDU has been successfully delivered to a network node via a relay UE on a UE-to-network relay path; and At least one duplicate PDCP PDU on at least one other UE-to-network path is discarded (304).
2. The method according to claim 1, wherein: The at least one other UE-to-network path comprises at least one of the following: UE to network relay path, or UE to network direct path.
3. The method according to claim 1 or 2, wherein: Determining that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path includes: receiving a radio link control (RLC) status report from the relay UE, wherein the RLC status report indicates that the PDCP PDU has been successfully sent to the relay UE in a sidelink; and Based on the RLC status report, it is determined that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path.
4. The method according to any one of claims 1 to 3, wherein: Determining that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path includes: receiving a PDCP status report from the network node, wherein the PDCP status report indicates that the PDCP PDU has been successfully received by the network node over the UE-to-network relay path; and Based on the PDCP status report, it is determined that the PDCP PDU has been successfully delivered to the network node over the UE-to-network relay path.
5. The method according to claim 4, wherein: The PDCP status report is received from the network node when at least one of the following occurs: The upper layer requests the PDCP entity to reestablish, The upper layer requests PDCP data recovery, The upper layer requests uplink data switching, The upper layer reconfigures the PDCP entity to release the Dual Active Protocol Stack (DAPS) and configures daps-SourceRelease in the upper layer. The upper layer determines that a PDCP status report needs to be triggered. The periodic timer expires, or PDCP duplication has been activated, and at least one path of PDCP duplication is the UE-to-network relay path. The method according to claim 5 , wherein the upper layer comprises a Radio Resource Control (RRC) layer.
7. The method according to any one of claims 4 to 6, wherein: The PDCP status report is received from the network node via a UE-to-network direct path and / or the UE-to-network relay path.
8. The method according to any one of claims 1 to 7, wherein: Determining that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path includes: receiving a first signaling from the relay UE, wherein the first signaling indicates that the relay UE has received an RLC status report of the PDCP PDU from the network node, wherein the RLC status report indicates that the PDCP PDU has been successfully sent to the network node in a Uu link; and A determination is made based on the first signaling that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path.
9. The method according to any one of claims 1 to 7, wherein: Determining that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path includes: receiving second signaling from the network node via a UE-to-network direct path, wherein the second signaling indicates that the PDCP PDU has been successfully received by the network node via the UE-to-network relay path; and Based on the second signaling, it is determined that the PDCP PDU has been successfully delivered to the network node through the relay UE on the UE-to-network relay path.
10. The method according to any one of claims 1 to 9, further comprising: receiving (312) third signaling from the network node, wherein the third signaling indicates deactivation of PDCP duplication of the uplink radio bearer; and Perform (314) at least one of the following operations: deactivating the PDCP duplication of the uplink radio bearer; discarding at least one first duplicate PDCP PDU and / or RLC service data unit SDU associated with the uplink radio bearer; or A fourth signaling is sent to the relay UE, wherein the fourth signaling instructs the relay UE to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer.
11. The method according to claim 10, wherein: The at least one second duplicate PDCP PDU and / or RLC SDU comprises at least one of the following: one or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer received from the first UE and stored in at least one sidelink RLC entity, or One or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer stored in at least one Uu RLC entity.
12. The method according to any one of claims 1 to 11, further comprising: receiving (322) fifth signaling from the network node, wherein the fifth signaling indicates deactivation of PDCP duplication for uplink radio bearers of at least one sidelink RLC entity; and Perform (324) at least one of the following operations: discarding at least one third duplicate PDCP PDU and / or RLC SDU associated with an uplink radio bearer of the at least one RLC entity; or A sixth signaling is sent to the relay UE, wherein the sixth signaling instructs the relay UE to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and the at least one RLC entity.
13. The method according to claim 12, wherein: The at least one fourth duplicate PDCP PDU and / or RLC SDU comprises at least one of the following: one or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer received from at least one RLC entity of the first UE and stored in one or more sidelink RLC entities of the relay UE, or One or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer are received from at least one RLC entity of the first UE and stored in at least one Uu RLC entity of the relay UE.
14. The method according to any one of claims 12 to 13, wherein: The fifth signaling is received from the network node via the UE-to-network relay path or the UE-to-network direct path.
15. The method according to any one of claims 1 to 14, further comprising: Maintain (332) a mapping table between Uu PDCP PDUs and sidelink RLC PDUs in the UE-to-network relay path.
16. The method according to claim 15, wherein the mapping table comprises at least one of the following: Mapping of a Uu PDCP PDU to one or more PC5 RLC PDUs, or Mapping of one or more Uu PDCP PDUs to PC5 RLC PDUs.
17. The method according to claim 15 or 16, wherein: In the mapping table, the Uu PDCP PDU is identified by the sequence number SN value of the Uu PDCP PDU, and the sidelink RLC PDU is identified by the SN value of the sidelink RLC PDU.
18. The method according to any one of claims 15 to 17, wherein: When the Uu PDCP PDU is delivered to the sidelink RLC layer, an entry corresponding to the Uu PDCP PDU is added to the mapping table, and when the sidelink RLC layer indicates to the Uu PDCP layer that the Uu PDCP PDU has been successfully transmitted to the recipient, or when a timer or counter expires and the Uu PDCP PDU has become invalid, the entry corresponding to the Uu PDCP PDU is deleted.
19. The method according to any one of claims 1 to 18, wherein: The signaling between the network node and the first UE includes at least one of the following: RRC signaling, Media Access Control MAC Control Element CE, or Layer 1 signaling.
20. The method according to any one of claims 1 to 19, wherein: The signaling between the relay UE and the first UE includes at least one of the following: RRC signaling, MAC CE, or Control PDU of the protocol layer.
21. A method (400) performed by a relay UE, comprising: receiving (402) a PDCP PDU for an uplink radio bearer from a first UE, wherein the uplink radio bearer has been activated by PDCP duplication; and An indication is sent (404) to the first UE that the PDCP PDU has been successfully delivered to a network node through a relay UE on a UE-to-network relay path.
22. The method according to claim 21, wherein: The PDCP PDU is delivered to the network node via at least one of: UE to network relay path, or UE to network direct path.
23. The method according to claim 21 or 22, wherein: The indication is an RLC status report indicating that the PDCP PDU has been successfully sent to the relay UE in the sidelink.
24. The method according to any one of claims 21 to 23, wherein: The indication indicates that the relay UE has received an RLC status report of the PDCP PDU from the network node.
25. The method according to any one of claims 21 to 24, further comprising: receiving (412) signaling from the first UE, wherein the signaling instructs the relay UE to discard at least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer; and At least one second duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer is discarded (414).
26. The method according to claim 25, wherein: The at least one second duplicate PDCP PDU and / or RLC SDU comprises at least one of the following: one or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer received from the first UE and stored in at least one sidelink RLC entity, or One or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer stored in at least one Uu RLC entity.
27. The method according to any one of claims 21 to 26, further comprising: receiving (422) signaling from the first UE, wherein the signaling instructs the relay UE to discard at least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and the at least one RLC entity; and At least one fourth duplicate PDCP PDU and / or RLC SDU associated with the uplink radio bearer and the at least one RLC entity is discarded (424).
28. The method according to claim 27, wherein: The at least one fourth duplicate PDCP PDU and / or RLC SDU comprises at least one of the following: one or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer received from at least one RLC entity of the first UE and stored in one or more sidelink RLC entities, or One or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer are received from at least one RLC entity of the first UE and stored in at least one Uu RLC entity.
29. The method according to any one of claims 21 to 28, further comprising: receiving (432) signaling from the network node including an identifier of the first UE, wherein the signaling indicates discarding duplicate PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer; and Duplicate PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer are discarded (434).
30. The method according to any one of claims 21-29, further comprising: receiving (442) signaling including an identifier of the first UE from the network node, wherein the signaling indicates to deactivate at least one RLC entity of an uplink radio bearer in a UE-to-network relay path; and At least one RLC entity of the uplink radio bearer in the UE-to-network relay path is deactivated (444).
31. The method according to any one of claims 21 to 30, further comprising: Maintain (452) a mapping table between Uu PDCP PDUs and sidelink RLC PDUs in the UE-to-network relay path.
32. The method of claim 31 , wherein the mapping table comprises at least one of the following: Mapping of PC5 RLC PDU to one or more Uu PDCP PDUs, or Mapping of one or more PC5 RLC PDUs to Uu PDCP PDUs.
33. The method according to claim 31 or 32, wherein: In the mapping table, a Uu PDCP PDU is identified by a sequence number SN value of the Uu PDCP PDU, and a sidelink RLC PDU is identified by the SN value of the sidelink RLC PDU, an identifier of the uplink radio bearer, and an identifier of the first UE.
34. The method according to any one of claims 21 to 33, wherein: The signaling between the network node and the relay UE includes at least one of the following: RRC signaling, Media Access Control MAC Control Element CE, or Layer 1 signaling.
35. The method according to any one of claims 21 to 34, wherein: The signaling between the relay UE and the first UE includes at least one of the following: RRC signaling, MAC CE, or Control PDU of the protocol layer.
36. A method (500) performed by a network node, comprising: for a downlink radio bearer activated by PDCP duplication, determining (502) that the PDCP PDU has been successfully delivered to the first UE via a relay UE on a UE-to-network relay path; and At least one duplicate PDCP PDU on at least one other UE-to-network path is discarded (504).
37. The method of claim 36, wherein: The at least one other UE-to-network path comprises at least one of the following: UE to network relay path, or UE to network direct path.
38. The method according to claim 36 or 37, wherein: Determining that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path includes: receiving an RLC status report from the relay UE, wherein the RLC status report indicates that the PDCP PDU has been successfully sent to the relay UE in a Uu link; and Based on the RLC status report, it is determined that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path.
39. The method according to any one of claims 36 to 38, wherein: Determining that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path includes: receiving a PDCP status report from the first UE, wherein the PDCP status report indicates that the first UE has successfully received the PDCP PDU via the UE-to-network relay path; and Based on the PDCP status report, it is determined that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path.
40. The method of claim 39, wherein: The network node receives the PDCP status report when at least one of the following situations occurs: The upper layer requests the PDCP entity to reestablish, The upper layer requests PDCP data recovery, The upper layer requests downlink data switching, The upper layer reconfigures the PDCP entity to release the dual active protocol stack DAPS and configures daps-SourceRelease in the upper layer. The upper layer determines that a PDCP status report needs to be triggered. The periodic timer expires, or PDCP duplication has been activated, and at least one path of PDCP duplication is the UE-to-network relay path. The method of claim 40 , wherein the upper layer comprises a Radio Resource Control (RRC) layer.
42. The method according to any one of claims 39 to 41, wherein: The PDCP status report is received by the network node via a direct path and / or the UE-to-network relay path.
43. The method according to any one of claims 36 to 42, wherein: Determining that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path includes: receiving first signaling from the relay UE, wherein the first signaling indicates that the relay UE has received an RLC status report of the PDCP PDU from the first UE, wherein the RLC status report indicates that the PDCP PDU has been successfully transmitted to the first UE in a sidelink; and Based on the first signaling, it is determined that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path.
44. The method according to any one of claims 36 to 43, wherein: Determining that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path includes: receiving second signaling from the first UE via a UE-to-network direct path, wherein the second signaling indicates that the PDCP PDU has been successfully received by the first UE via the UE-to-network relay path; and Based on the second signaling, it is determined that the PDCP PDU has been successfully delivered to the first UE through the relay UE on the UE-to-network relay path.
45. The method according to any one of claims 36 to 44, further comprising: determining (512) to deactivate the PDCP duplication of the downlink radio bearer; Perform (514) at least one of the following operations: deactivating the PDCP duplication of the downlink radio bearer; Sending a third signaling to the first UE, wherein the third signaling indicates deactivation of the PDCP duplication of the downlink radio bearer; Sending a fourth signaling to the first UE, wherein the fourth signaling indicates deactivating at least one sidelink RLC entity of the downlink radio bearer on a UE-to-network relay path; Sending a fifth signaling to the relay UE, wherein the fifth signaling indicates deactivating at least one Uu and PC5 RLC entity of the downlink radio bearer on the UE-to-network relay path; discarding at least one duplicate PDCP PDU and / or RLC SDU associated with the downlink radio bearer; or A sixth signaling is sent to the relay UE, wherein the sixth signaling indicates discarding at least one second duplicate PDCP PDU and / or RLC SDU associated with the downlink radio bearer.
46. The method of claim 45, wherein: The at least one second duplicate PDCP PDU and / or RLC SDU comprises at least one of the following: one or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer received from the network node and stored in at least one Uu RLC entity of the relay UE, or One or more PDCP PDUs and / or RLC SDUs associated with the uplink radio bearer stored in at least one sidelink RLC entity of the relay UE.
47. The method according to any one of claims 36 to 46, further comprising: A mapping table between Uu PDCP PDU and Uu RLC PDU in the UE-to-network relay path is maintained (600).
48. The method of claim 47, wherein the mapping table comprises at least one of the following: Mapping of a Uu PDCP PDU to one or more Uu RLC PDUs, or Mapping of one or more Uu PDCP PDUs to Uu RLC PDUs.
49. The method according to claim 47 or 48, wherein: In the mapping table, the Uu PDCP PDU is identified by the sequence number SN value of the Uu PDCP PDU, and the Uu RLC PDU is identified by the SN value of the Uu RLC PDU.
50. The method according to any one of claims 47 to 49, wherein: When a Uu PDCP PDU is delivered to the Uu RLC layer, an entry corresponding to the Uu PDCP PDU is added to the mapping table, and when the Uu RLC indicates to the Uu PDCP layer that the Uu PDCP PDU has been successfully transmitted to the receiving party, or when a timer or a counter expires and the Uu PDCP PDU has become invalid, the entry corresponding to the Uu PDCP PDU is deleted.
51. The method according to any one of claims 36 to 50, wherein: The signaling between the network node and the first UE includes at least one of the following: RRC signaling, Media Access Control MAC Control Element CE, or Layer 1 signaling.
52. The method according to any one of claims 36 to 51, wherein: The signaling between the relay UE and the first UE includes at least one of the following: RRC signaling, MAC CE, or Control PDU of the protocol layer.
53. A first user equipment UE (700), comprising: Processor (721); and a memory (722) coupled to the processor (721), the memory (722) comprising instructions executed by the processor (721), whereby the first UE (700) operates to: for an uplink radio bearer activated using packet data convergence protocol PDCP duplication, determining that a PDCP protocol data unit PDU has been successfully delivered to a network node via a relay UE on a UE-to-network relay path; and At least one duplicate PDCP PDU on at least one other UE-to-network path is discarded.
54. The first UE according to claim 53, wherein: The first UE is further operable to perform the method of any one of claims 2 to 20.
55. A relay UE (700), comprising: Processor (721); and a memory (722) coupled to the processor (721), the memory (722) comprising instructions executed by the processor (721), whereby the relay UE (700) operates to: receiving a PDCP PDU for an uplink radio bearer from a first UE, wherein the uplink radio bearer has been activated by PDCP duplication; and An indication is sent to the first UE that the PDCP PDU has been successfully delivered to a network node through a relay UE on a UE-to-network relay path.
56. The relay UE according to claim 55, wherein: The relay UE is further operable to perform the method of any one of claims 22 to 35.
57. A network node (700), comprising: Processor (721); and a memory (722) coupled to the processor (721), the memory (722) comprising instructions executed by the processor (721), whereby the network node (700) is operative to: for a downlink radio bearer that has been activated by PDCP duplication, determining that the PDCP PDU has been successfully delivered to the first UE via the relay UE on a UE-to-network relay path; and At least one duplicate PDCP PDU on at least one other UE-to-network path is discarded.
58. The network node of claim 57, wherein the network node is further operative to perform the method of any one of claims 37 to 54.
59. A computer readable storage medium storing instructions which, when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 54.
60. A computer program product comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 54.
