Energy-saving scheme of Internet of Vehicles

Abstract

Methods, apparatuses, and systems are described for implementing wireless communication techniques using device-to-device communications, such as sidelink communications. One example method includes receiving, by a first user equipment, carrier aggregation (CA) operation information, and operating the first user equipment according to the CA operation information. The first user equipment is configured to perform device-to-device communication with the second user equipment using CA without relaying over the network device.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications. Background Art

[0002] Mobile communication technologies are driving the world towards an increasingly connected and networked society. The rapid growth of mobile communications and technological advances have led to greater demands for capacity and connectivity. Other aspects such as energy consumption, equipment cost, spectrum efficiency, and latency are also important to meet the needs of various communication scenarios. Various technologies are being discussed, including new methods for providing higher quality of service, longer battery life, and improved performance. Summary of the invention

[0003] Among other things, the patent document describes techniques for communicating in a sidelink deployment of New Radio (NR).

[0004] In one example aspect, a wireless communication method is disclosed. The method includes receiving, by a first user equipment, carrier aggregation (CA) configuration information, wherein the first user equipment is configured to: perform device-to-device communication with a second user equipment using CA without relaying through a network device; and operating the first user equipment according to the CA configuration information.

[0005] In another example aspect, a wireless communication method is disclosed. The method includes: sending carrier aggregation (CA) configuration information by a wireless device to a first user equipment, wherein the first user equipment is configured to: perform device-to-device communication with a second user equipment using CA without relaying through a network device.

[0006] In another example aspect, a wireless communication method is disclosed. The method includes: sending, by a first user device to a second user device, a report request for reporting a channel state, wherein the first user device is configured to: perform device-to-device communication with the second user device using one or more carriers of N carriers without relaying through a network device, wherein N is an integer greater than 1.

[0007] In another example aspect, a wireless communication method is disclosed. The method includes: receiving, by a second user device, a report request for reporting a channel state from a first user device, wherein the second user device is configured to: perform device-to-device communication with the first user device using one or more carriers of N carriers without relaying through a network device, wherein N is an integer greater than 1; and performing a channel state information (CSI) related operation according to the report request.

[0008] In another example aspect, a wireless communication apparatus is disclosed. The apparatus includes a processor configured to implement the method disclosed in this document.

[0009] In another example aspect, a computer readable medium is disclosed. The medium has processor executable code stored thereon. The code, when executed, causes the processor to implement the method disclosed in this document.

[0010] These and other aspects are described in this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 An example wireless network in which sidelink communications are used is shown.

[0012] Figure 2 An example of message exchange for CA configuration is shown.

[0013] Figure 3 An example of a CA-configured rejection is shown.

[0014] Figure 4 An example of implementing PDCP splitting or PDCP duplication according to CA configuration is shown.

[0015] Figure 5 An example of performing channel state information (CSI) measurements using a CA configuration is shown.

[0016] Figure 6A-6D A flow chart of an example wireless communication method is shown.

[0017] Figure 7 An example of a wireless communication network is shown.

[0018] Figure 8 An example hardware platform for implementing the disclosed methods is shown. DETAILED DESCRIPTION

[0019] The headings of the following sections are intended to facilitate understanding of the disclosed subject matter and do not limit the scope of the claimed subject matter in any way. Therefore, one or more features of one example section may be combined with one or more features of another example section. In addition, for the sake of clarity of explanation, the 5G terminology is used, but the technology disclosed in this document is not limited to 5G technology, but can also be used to implement wireless systems of other protocols. Although some embodiments are described with reference to vehicle-based wireless communication functions, the disclosed technology can be used by a variety of different wireless devices, including, for example, mobile phones, tablets, and other wireless devices.

[0020] This document relates to wireless systems. More specifically, it relates to communications between UEs for sidelink communications and resource scheduling. Parameters are exchanged from one UE to another UE so that the UEs can be configured.

[0021] In the current side link technical solution, the UE needs to monitor the measurement resource pool, which leads to great power consumption. The present invention provides a UE energy saving method applicable to the side link system.

[0022] With the development of wireless multimedia services, users' demand for high data rates and user experience continues to increase, which puts higher requirements on the system capacity and coverage of traditional cellular networks. On the other hand, application scenarios such as public safety, social networks, short-distance data sharing, and local advertising have gradually increased people's needs to understand and communicate with nearby people or things (proximity services). Traditional base station-centric cellular networks have obvious limitations in high data rates and support for proximity services. Against the background of this demand, device-to-device (D2D) communication technology has emerged. The application of D2D technology can reduce the burden on cellular networks, reduce battery power consumption of user devices, increase data rates, and improve the robustness of network infrastructure, which meets the requirements of the above-mentioned high data rate services and proximity services. D2D technology is also called proximity services (ProSe), unilateral / side link / side link (SL) communication; the interface between devices is the PC5 interface.

[0023] In this document, in order to improve reliability, data rate, reduce latency and other advantages, PC5 carrier aggregation (CA) is proposed to achieve high reliability and high data rate. CA means that two or more component carriers (CCs) are aggregated to support a wider transmission bandwidth. When it comes to PC5 CA, it means that the vehicle UE can perform sidelink reception or transmission on one or more PC5 CCs simultaneously. However, there is currently no effective solution for implementing data splitting and / or data replication based on PC5 CA.

[0024] Figure 1 is a block diagram of an example V2X (vehicle-to-vehicle) communication system. In the V2X communication research based on LTE (Long Term Evolution) organized by the Third Generation Partnership Project 3GPP, user equipment (user equipment UE) can communicate using V2X communication between direct / side link links. For example, data can be sent directly from the source UE to the target UE through the air interface (PC5 interface) instead of being forwarded by the base station and the core network, such as Figure 1 shown.

[0025] With the advancement of communication technology and the development of the automation industry, V2X communication scenarios have been further expanded and have higher performance requirements. 3GPP has established a vehicle network communication study for advanced V2X services based on the fifth generation mobile communication technology (5G), including vehicle network communication based on the 5G air interface and vehicle network communication based on the 5G direct link (side link). Side link communication is an example of device-to-device communication, in which two user devices can communicate with each other via a direct link without relaying messages through the network (e.g., base station).

[0026] For NR-based vehicle-to-everything (V2X) sidelink communications, PC5 interface radio resource control RRC signaling interactions may be supported. Specifically, PC5 RRC signaling may include messages for the transmit capabilities of a UE. Among other things, this document relates to obtaining capability information of a peer UE and interacting for PC5 UE capability information exchange for sidelink transmission parameter selection. In addition, PC5 RRC signaling may not be able to be sent without security protection, and the present embodiment may provide a security protection mechanism for protecting PC5 RRC signals at an access stratum (AS) layer.

[0027] In one embodiment, assuming that UE1 sends data to UE2, due to the hidden node problem, UE2 knows which carrier is suitable for data reception. Therefore, UE2 can determine the CA configuration for UE1 to send data to UE2.

[0028] In another embodiment, if UE2 is in the RRC connected state, the gNB of UE2 determines that the CA configuration for UE1 to send data to UE2 is reasonable.

[0029] In one embodiment, it is also possible that UE1 determines the CA configuration for UE1 to send data to UE2.

[0030] In some embodiments, UE1 is in an RRC connected state, and UE1's gNB wants to determine that the CA configuration used for UE1 to send data to UE2 is reasonable.

[0031] In one embodiment, if UE2 or the gNB of UE2 determines the CA configuration for UE1 to send data to UE2, UE2 needs to know the auxiliary information to determine the CA configuration. Therefore, UE1 may need to send auxiliary information for transmission to UE2.

[0032] In one embodiment, the assistance information is used to determine the CA configuration.

[0033] In one embodiment, if the gNB of UE2 determines the CA configuration for UE1 to send data to UE2, UE2 needs to send auxiliary information to the gNB.

[0034] In one embodiment, if UE1 or UE1's gNB determines a CA configuration for UE1 to send data to UE2, UE2 may need to send auxiliary information to UE1.

[0035] If UE1's gNB determines a CA configuration for UE1's transmission, UE1 may need to send auxiliary information for the transmission to UE1.

[0036] The auxiliary information may be sent via system information, RRC signaling, or MAC CE or PHY layer signaling.

[0037] CA configuration may be sent via system information, RRC signaling, or MAC CE or PHY layer signaling.

[0038] 1. Example 1 (CA Assistance Information)

[0039] Figure 2 An example configuration is shown in which UE1 and UE2 may exchange auxiliary information related to a carrier aggregation (CA) configuration for establishing or operating a side link using CA.

[0040] In some embodiments, based on carrier configurations such as time division duplex TDD, frequency division duplex FDD configuration, synchronization configuration, etc., one carrier may not be suitable or can not be aggregated with another carrier. Therefore, it may be necessary to include carriers that can be aggregated with each other in the auxiliary information. Therefore, the auxiliary information includes: one or more carrier lists indicating possible carrier combinations.

[0041] In one embodiment, carriers in one list can be aggregated with other carriers in the same list, and carriers in one list cannot be aggregated with carriers in another list.

[0042] In another embodiment, carriers in one list may be aggregated with other carriers in another list, but carriers in one list may not be aggregated with other carriers in the same list.

[0043] For example, there may be two carrier lists: (CC1, CC2) (CC3, CC4, CC5) sent from UE2 to UE1, CC1 can only be aggregated with CC2, CC1 cannot be aggregated with CC3 or CC4 or CC5, CC3, CC4, CC5 can be aggregated with each other. Here, "CC" means component carrier.

[0044] As another example, there may be two carrier lists: (CC1, CC2) (CC3, CC4, CC5) sent from UE2 to UE1, CC1 can only be aggregated with CC3 or CC4 or CC5, CC1 cannot be aggregated with CC2. Here, "CC" means component carrier.

[0045] In some embodiments, based on UE capabilities, the UE can only monitor a certain number of carriers simultaneously. Therefore, the auxiliary information may include how many carriers can be used together. For example, UE1 obtains from UE2 that a maximum of 8 carriers can be used together.

[0046] In one embodiment, another information (item) that may be sent to UE2 is the supported carriers so that UE1 knows which carriers may be used for communication with UE2. Therefore, the supported carriers may need to be included in the assistance information. For example, the assistance information includes 16 carriers supported by the peer device.

[0047] In some embodiments, based on channel quality, TX / RX requirements, Uu data requirements or other factors, the UE may prefer, or not prefer, or be unable to send / receive data on a specific carrier. Therefore, the assistance information may include at least one of the following items:

[0048] 1. Prefer one or more preferred carriers to be used for device-to-device communication

[0049] 2. One or more non-preferred carriers to be used for device-to-device communication are not preferred

[0050] 3. Prohibit one or more prohibited carriers from being used for device-to-device communications

[0051] 4. One or more allowed carriers to be used for device-to-device communication

[0052] 5. One or more carriers.

[0053] Various types of carriers may be indicated in the assistance information as follows.

[0054] The preference indicator may indicate whether the corresponding carrier in the auxiliary information is a preferred carrier.

[0055] 5 The non-preferred indicator may indicate whether the corresponding carrier in the auxiliary information is a non-preferred carrier.

[0056] 6. The prohibited carrier indicator can indicate whether the corresponding carrier in the auxiliary information is a prohibited (or prohibited) carrier

[0057] 6a. The allowed carrier indicator can indicate whether the corresponding carrier in the auxiliary information is an allowed carrier

[0058] 7. Objects to which auxiliary information is applied

[0059] 8. Carrier priority

[0060] 9. Priority order of one or more carriers.

[0061] In one embodiment, an object may be at least one of the following:

[0062] 1. LCID (Logical ID) of the RLC channel

[0063] 3. RLC channel ID of the RLC channel

[0064] 4. RB ID of the RB.

[0065] 5. Carrier.

[0066] 6. QoS flow ID of the QoS flow.

[0067] 10. Destination L2 ID.

[0068] 11.QoS profile.

[0069] 12. RLC channel configuration index of RLC channel

[0070] 14, radio bearer configuration index of RB.

[0071] In one embodiment, the RLC may be a sidelink RLC

[0072] In one embodiment, the RB may be a sidelink RB.

[0073] In one embodiment, the QoS profile may be a sidelink QoS profile

[0074] In one embodiment, the QoS flow may be a sidelink QoS flow.

[0075] In one embodiment, the state of the carrier may have a significant impact on the CA configuration determination. Therefore, the auxiliary information may include the state of each carrier. The state of each carrier includes at least one of the following items:

[0076] 1.CBR (Channel Busy Rate)

[0077] 2. RSRP (Reference Signal Received Power)

[0078] 3.CSI (Channel State Information)

[0079] In the NR system, different subcarrier spacings are supported to achieve flexible configuration. If two or more carriers with different subcarrier spacings are aggregated with each other, the UE may need to be configured with time slot aggregation. Therefore, the auxiliary information may include time slot aggregation information. The time slot aggregation information includes at least one of the following items:

[0080] 1. Whether time slot aggregation is supported (by device or by carrier)

[0081] 2. The subcarrier spacing of each carrier.

[0082] 3. Symbol length of each carrier

[0083] 4. The supported subcarrier spacing for each carrier.

[0084] 5. Supported subcarrier spacing for slot aggregation per carrier.

[0085] 6. BWP configuration for each carrier.

[0086] In the NR V2X system, a specific service may support one or more carriers. A UE using a service can only use these configured carriers. However, the gNB may not provide configuration for all supported carriers for a specific service. Therefore, if the UE can obtain the V2X communication configuration for a specific carrier from the gNB, or if the UE cannot detect at least one cell on the frequency on which the UE is configured to perform NR sidelink communication while meeting the S standard, it should consider itself to be in coverage on that carrier, otherwise, it should consider itself to be out of coverage. The coverage status of the carrier may be a factor to be considered during CA determination. In one embodiment, the auxiliary information may include the coverage status of each supported carrier. The coverage status may be at least one of the following: in coverage, out of coverage, partial coverage.

[0087] In NR V2X systems, the UE may be configured with different resource patterns for each carrier (scheduling or UE selection). Therefore, the assistance information may include the resource pattern for each carrier determined by CA.

[0088] In the NR sidelink system, in addition to service data, the UE can also send synchronization signals and management information block MIB information. However, due to the half-duplex problem, the UE sending the synchronization signal cannot receive data at the same time. Therefore, the auxiliary information may include synchronization information determined by CA for the UE. The synchronization information may include at least one of the following items:

[0089] 1. Synchronous signaling resource configuration.

[0090] 2. Synchronization priority, including at least one of the following items: gNB is prioritized, GNSS is prioritized, and UE is prioritized to be selected as the synchronization reference.

[0091] 3. Number of sidelink synchronization signal block SSB transmissions in one sidelink SSB period

[0092] 4. Should the UE send synchronization information?

[0093] 5. Priority of sidelink synchronization signaling

[0094] 6. Sidelink SSB priority

[0095] 7.(One or more) allowed synchronization references

[0096] 8. Carrier type of each carrier, including at least one of the following: serving carrier / non-serving carrier / synchronous carrier / non-synchronous carrier / uplink carrier / downlink carrier

[0097] In one embodiment, after receiving the CA configuration, UE2 may prefer to deactivate / activate carriers, or packet duplication, or packet splitting based on the transmission state. In this case, UE2 may send auxiliary information of UE1 or UE1's serving gNB to UE1 to determine the CA configuration. Therefore, the auxiliary information includes at least one of the following items:

[0098] 1.CA Configuration

[0099] 2. A preference indicator as to whether the corresponding CA configuration is a preferred CA configuration.

[0100] 3. A non-preferred indicator as to whether the corresponding CA configuration is a non-preferred CA configuration.

[0101] 4. A prohibition indicator indicating whether the corresponding CA configuration cannot be used.

[0102] 5. Objects to which auxiliary information is applied

[0103] 6. Optimize CA configuration.

[0104] 7. Non-preferred CA configuration.

[0105] 8. Prohibit CA configuration.

[0106] For example, if UE1 receives the assistance information including the CA configuration and the preference indication with carrier 1, UE1 considers that UE2 prefers to use carrier 1 for communication.

[0107] For example, if UE1 receives the auxiliary information including the CA configuration with RLC channel ID-1, the indication to activate packet duplication, and the preference indication, UE1 considers that UE2 prefers to activate packet duplication of the RLC channel with ID-1.

[0108] In the NR V2X system, the UE can communicate with other UEs and gNB at the same time. In this case, the CA configuration can be determined by the gNB. Therefore, the UE should report to the gNB the auxiliary information received from other UEs listed in this patent.

[0109] 2. Example 2 (CA configuration rejection reason)

[0110] Figure 3 An example of the configuration of a wireless device in which Embodiment 2 can be implemented is shown.

[0111] In some cases, the CA configuration from UE1 to UE2 cannot be applied, for example, UE2 may be configured to receive data on another carrier, and the carrier configured by UE1 cannot be used at the same time. Therefore, UE2 may reject the CA configuration. In this case, UE2 may send a rejection signaling to UE1 indicating that the CA configuration is rejected.

[0112] If UE1 is in RRC connected mode, it is possible that the CA configuration is configured by the gNB, and UE1 may issue a rejection signaling to the gNB indicating that the CA configuration is rejected by UE2. In this case, the rejection signaling includes the ID of UE2, which in the case of UE2 may be the DST L2 ID.

[0113] In one embodiment, in order to help UE1 identify the reason why CA configuration cannot be applied (for example, the reason why UE2 rejects the configuration), UE2 may provide some necessary information to UE1, and the information includes at least one of the following items:

[0114] 1. The CBR (channel busy rate) of the configured carrier is higher than the CBR threshold.

[0115] 2. The carrier is not supported.

[0116] 3. The carrier is rejected by the serving cell or gNB.

[0117] 4. The carrier is disabled.

[0118] 5. Number of RLC bearers.

[0119] 6. The number of logical channels is unacceptable.

[0120] 7. The carrier is used for transmission or synchronization signal transmission or uplink transmission or downlink transmission.

[0121] In another embodiment, if the CA configuration from UE1 cannot be applied, UE2 may also provide a recommended CA configuration to UE1. The recommended CA configuration is a CA configuration recommended by UE2.

[0122] 3. Example 3.1 (CA Configuration)

[0123] Figure 4 An example configuration of a wireless device is shown in which embodiments 3.1 and 3.2 may be implemented.

[0124] In a traditional NR sidelink system, the UE is configured with a mapping rule between a service and one or more carriers (e.g., a carrier list is associated with a service). A UE sending service data can only use the carriers in the carrier list associated with the service. For sidelink multicast and broadcast, since RRC signaling is not supported, the TX UE and RX UE cannot exchange carrier capabilities, so the TX UE must select the carrier associated with the service based on its own capabilities. For sidelink unicast during link establishment, the same problem exists, that is, the TX UE must select the carrier associated with the service. Therefore, for GC / BC / unicast initial signaling, the TX UE assumes that all carriers associated with the service will be supported by the RX UE. After the unicast link is established, the UE can exchange radio resource control RRC signaling with other UEs, and the UE can obtain the carrier capabilities of the peer UE.

[0125] In one embodiment, the UE may be configured with a carrier list associated with a service, the carrier list including default carriers assumed to be supported by the peer UE. For example, in the absence of the peer UE's carrier capabilities, the UE may use these carriers to send multicast / broadcast / unicast initial link establishment signaling to the peer UE.

[0126] In another embodiment, the UE may be configured with a carrier list associated with a service, the carrier list including optional carriers supported based on UE capabilities. For example, after checking the carrier capabilities of a peer UE, the UE may use carriers supported by the peer UE.

[0127] In another embodiment, after acquiring the supported carriers of the peer UE, a carrier associated with the service that is not included in the carrier list may also be used to communicate with the peer UE. In another embodiment, the UE is configured with whether to allow the use of a carrier associated with the service that is not included in the carrier list, which may be used to communicate with the peer UE after acquiring the supported carriers of the peer UE.

[0128] For example, carrier list 1 includes: a default carrier list that UEs interested in the service must support, and carrier list 2 includes optional carriers. In order to use the carriers listed in list 2, UE1 needs to check whether the carriers in list 2 are supported by UE-2, that is, UE2 provides supported carriers to UE1. Before establishing a connection with UE2, UE1 cannot obtain the carrier capability of UE2. UE1 can only select a carrier from carrier list 1 during link establishment to send connection signaling, such as direct communication request signaling, security mode command signaling, security mode completion signaling, and direct communication response signaling. After the connection is established, UE1 can obtain the carrier capability of UE2, such as which carrier UE2 supports, and then UE1 can use the carriers in list 1 or list 2 supported by UE-2. In another embodiment, only one list is configured, and some of the carriers in the list can be used without the carrier capability of the peer UE, and another part of the carriers in the list can be used only after checking the UE capability of the peer UE.

[0129] In one embodiment, the CA configuration includes at least one of the following:

[0130] 1. One or more carrier waves used for communication.

[0131] 2. The object to which the CA configuration applies.

[0132] For example, if the gNB of UE1 determines a CA configuration for UE1 to send data to UE2, UE1 receives a CA configuration including carrier 1 and the DST L2 ID of UE2, and UE1 should communicate with the DST L2 ID of UE2 using carrier 1. Then, UE1 notifies UE2 that carrier 1 will be used for communication by sending carrier 1 to UE2.

[0133] Another example is that if UE2 determines a CA configuration for UE1 to send data to UE2, UE1 receives a CA configuration including carrier 1 for communication from UE2, which indicates that UE1 should communicate with UE2 using carrier 1. In the case where UE1 is in RRC connected mode, UE1 reports the CA configuration including carrier 1 and UE2's DST L2 ID to the gNB.

[0134] In one embodiment, the carrier is identified by at least one of a carrier index and a carrier frequency.

[0135] In another embodiment, after receiving the carrier for communication, the UE does not need to use all carriers immediately, in other words, these carriers are deactivated or activated. Activation signaling is sent to indicate which carrier is activated or deactivated. Therefore, the CA configuration includes at least one of the following items:

[0136] 1. Carrier status indicator. In another embodiment, the carrier status indicator may be at least one of the following: activating a carrier or deactivating a carrier.

[0137] 2. The object to which the CA configuration applies.

[0138] 4. Example 3.2 (CA configuration: group splitting and replication configuration)

[0139] The benefit of CA is to perform data splitting or duplication to increase data rate or reliability. For data duplication, the TXUE can send duplicate sidelink packets on multiple carriers. The RX UE can detect the duplication and discard the duplicated packets. In one embodiment, the packet duplication can be at least one of PDCP duplication or MAC duplication.

[0140] For packet splitting, parallel transmission of different packets on multiple carriers can be considered. Since the radio resources of multiple carriers can be used for transmitting (Tx) UE, the data rate of sidelink transmission can be increased. On the other hand, in order to support packet splitting, from the perspective of receiving (Rx) UE, simultaneous reception on multiple carriers can be supported. In one embodiment, packet splitting is at least one of PDCP splitting or MAC splitting.

[0141] For a radio bearer (RB) configured with PDCP duplication, the PDCP entity duplicates the PDCP PDU and delivers the packet to two or more different RLC entities. For PDCP data splitting, the PDCP entity may deliver the PDCP PDU to different RLC entities according to preconfigured rules.

[0142] Group replication and splitting are two independent features and can be configured and / or used separately.

[0143] In one embodiment, the CA configuration may include at least one of the following:

[0144] 1. Configuration of transmission scheme

[0145] 2. Objects to which CA configuration applies

[0146] In one embodiment, the transmission scheme may be at least one of the following:

[0147] 1. Group replication.

[0148] 2. Group splitting.

[0149] In one embodiment, to perform packet duplication or packet splitting, the CA configuration includes at least one of the following:

[0150] 1. PDCP configuration associated with one or more RLC channels.

[0151] 2. The object to which the CA configuration applies.

[0152] In one embodiment, if a PDCP entity is associated with more than one RLC channel, not all RLC channels for the associated PDCP entity are activated, so the CA configuration includes at least one of the following:

[0153] 1. RLC channel status In another embodiment, the RLC channel status indicator includes at least one of the following: activating the RLC channel or deactivating the RLC channel.

[0154] 2. The object to which the CA configuration applies.

[0155] In one embodiment, the RLC channel state may be at least one of activated or deactivated.

[0156] For example, if an RLC channel is deactivated, the UE cannot submit packets to the deactivated RLC channel. Alternatively, if an RLC channel is deactivated for PDCP duplication, the UE cannot submit duplicate packets to the RLC channel. Alternatively, if an RLC channel is deactivated for PDCP splitting, the UE cannot submit packets to the RLC channel. In one embodiment, not all PDCPs associated with more than one RLC channel may use the transmission scheme, and the corresponding scheme may be further activated or deactivated for an RLC channel. If PDCP duplication is activated for a PDCP entity, the UE may duplicate packets and submit the duplicate packets to more than one RLC channel. If PDCP splitting is activated for a PDCP entity, the UE may submit packets to more than one RLC channel.

[0157] In one embodiment, after receiving the transmission scheme configuration, the transmission scheme is not used immediately. In other words, when the UE receives the CA configuration, the transmission scheme may be deactivated or activated, and the UE1 may activate or deactivate the transmission scheme accordingly based on some predefined condition or CA configuration. Therefore, the CA configuration received by the UE includes:

[0158] 1. Transmission scheme status indicator. In another embodiment, the transmission scheme status indicator may be at least one of the following: (1) activating packet replication, (2) deactivating packet replication, (3) activating packet splitting, (4) deactivating packet splitting.

[0159] 2. The object to which the CA configuration applies.

[0160] In one embodiment, if a PQI and a packet transmission state are included in the CA configuration, packet transmission is applied to the RB of the QoS flow having the PQI.

[0161] In one embodiment, if a QoS profile and a packet transmission state are included in the CA configuration, packet transmission is applied to the RBs of the QoS flow having the QoS profile.

[0162] For example, if UE1 receives a CA configuration including packet replication activation and LCID 1 from UE2 with DST L2 ID 1, UE1 shall activate packet replication for the RLC channel with LCID 1. If UE1 is in RRC connected mode, UE1 shall issue a CA configuration including packet replication activation, LCID 1 and DST L2 ID 1 to the gNB.

[0163] For example, UE1 receives a CA configuration including activation of packet replication and LCID 1, DST L2 ID 1 from the gNB, then UE1 should activate packet replication for the RLC channel with LCID 1 for the peer UE with DST L2 ID 1. Then UE1 sends out the CA configuration including activation of packet replication and LCID 1 to UE2 with DST L2 ID 1 to inform UE2 of the activation of packet replication.

[0164] In the NR system, for a specific radio bearer, one parameter of PDCP security is the logical channel identifier (LCID). When the transmission scheme is configured, more than one RLC channel with different LCIDs will be associated with a PDCP entity. Therefore, the UE needs to know which LCID will be used as the parameter for PDCP security. In one embodiment, at least one of the following IDs will be used to determine the parameters of PDCP security:

[0165] 1. LCID of the primary RLC channel used for PDCP security.

[0166] 2. The LCID of the first RLC bearer in the RLC bearer list associated with the same RB shall be used for PDCP security

[0167] 3. Radio Bearer ID (instead of LCID) will be used for PDCP security.

[0168] 4. Radio Bearer Configuration Index (instead of LCID) will be used for PDCP security.

[0169] In one embodiment, the UE receives at least one of the following configurations to determine parameters for PDCP security:

[0170] 1. The RLC bearer configuration includes: an indicator as to whether the LCID of the RLC channel will be used for PDCP security.

[0171] 2. An indicator that the LCID will be used for PDCP security of a specific RB. In one embodiment, the indicator may be at least one of the LCID, the RLC bearer ID, the RLC configuration index, and the RLC channel ID.

[0172] To determine whether the transmission scheme should be enabled, at least one of the following may be applied on the UE:

[0173] 1. The UE is configured with a CA configuration that includes: MFBR (Maximum Flow Bit Rate) or GFBR (Guaranteed Flow Bit Rate) threshold. In a further embodiment, if the MFBR or GFBR of at least one QoS flow associated with a particular RB (Radio Bearer) is higher than the MFBR or GFBR threshold, respectively, the UE shall enable the transmission scheme for that particular RB. In another embodiment, the sum of the MFBR or GFBR of all GBR QoS flows associated with the RB may be higher than the threshold, and the UE shall enable the transmission scheme.

[0174] 2. The UE is configured with a CA configuration that includes an AMBR (aggregate maximum bit rate) threshold. In the sidelink, the AMBR limits the aggregate bit rate that is expected to be provided over the PC5 unicast link with peer UEs across all non-GBR QoS flows. In one embodiment, if the AMBR of all non-GBR QoS flows associated with a specific destination is above the threshold, the UE shall enable the transmission scheme for the RBs associated with that destination.

[0175] 3. The UE is configured with a CA configuration including a data splitting threshold. In one embodiment, if the total amount of data to be transmitted is equal to or greater than the configured threshold, the UE shall enable the transmission scheme. The UE may also be configured with more than one data splitting threshold, and if the total amount of data to be transmitted is equal to or greater than the first threshold, the UE may submit the PDU to the first split RLC channel, and if the corresponding amount is higher than the second threshold, the UE may submit the PDU to the first split RLC channel or the second split RLC channel, and so on. For example, the UE is configured with a data splitting threshold list [100, 200, 300], and if the amount of data to be transmitted is less than 100, the UE shall submit the packet to the first RLC channel. If the amount of data to be transmitted is greater than 100 and less than 200, the UE shall submit the packet to the first RLC channel or the second RLC channel, and if the amount of data to be transmitted is greater than 200 and less than 300, the UE shall submit the packet to the first RLC channel or the second RLC channel or the third RLC channel.

[0176] 4. Since PQI identifies a set of QoS parameters for a QoS flow, the QoS parameters include priority, reliability, maximum data burst, etc. The UE can enable a transmission scheme based on the PQI of the QoS flow. The CA configuration includes a specific PQI (PC55G Quality of Service Identifier) ​​or a list of PQIs for enabling a transmission scheme. In other words, a configuration for enabling a transmission scheme for each PQI

[0177] - If the PQI of at least one QoS flow associated with a particular RB is configured to enable the transmission scheme, the UE enables the transmission scheme for that particular RB. In another embodiment, the UE shall enable the transmission scheme only for PDUs belonging to a QoS flow whose PQI is equal to the configured PQI.

[0178] For example, if the UE is configured with PQI list [1,2,3] to enable PDCP duplication, the UE shall enable PDCP duplication for RBs with PQI 1, 2 or 3 for at least one QoS flow

[0179] The UE's QoS parameters may use non-standard parameters (e.g., not identified by a PQI), which are included in the QoS profile. Thus, the UE may enable a transmission scheme according to the QoS profile. The QoS profile includes an indication of whether the UE should enable a transmission scheme for a QoS flow with the QoS profile.

[0180] If the QoS profile of at least one QoS flow associated with the RB includes the indication, the UE shall enable the transmission scheme for the RB. In another embodiment, in this case, the UE shall enable the transmission scheme only for PDUs that belong to the QoS flow associated with the QoS profile including the indication.

[0181] 5. RSRP (Reference Signal Received Power) Threshold: In one embodiment, if the RSRP of a communication carrier is below the configured RSRP threshold, the UE shall enable the transmission scheme for the allowed RBs on that communication carrier. In another embodiment, if the RSRP of all allowed communication carriers associated with an RB is below the configured RSRP threshold, the UE shall enable the transmission scheme for that RB.

[0182] 6. The UE is configured with a packet error rate (PER) threshold: If the PER of at least one QoS flow associated with the RB is lower than the configured PER threshold, the UE shall enable the transmission scheme for the RB. In another embodiment, the UE shall only replicate PDUs belonging to QoS flows whose PER is lower than the configured threshold. The UE may also be configured with a PER threshold list. If the PER of at least one QoS flow associated with the RB is lower than a first PER threshold, the UE shall submit the replicated PDUs to a first replication RLC channel, and if the PER is lower than a second PER threshold, the UE shall submit the replicated PDUs to the first replication RLC channel and the second replication RLC channel, and so on. For example, a PDCP entity is associated with three RLC channels for replication, two of which are used when replication is enabled. The UE is configured with a PER threshold list: [10 -1 ,10 -2 ,10 -3 ], if the PER of the QoS flow is less than 10 -1 , the UE shall only copy the PDCP PDU and submit the copied PDU to the first RLC channel and the second RLC channel. If the PER of the QoS flow is lower than 10 -2 , the UE shall only copy the PDCP PDU and submit the copied PDU to the first RLC channel, the second RLC channel and the third RLC channel.

[0183] 1. Threshold: The number of consecutive DTX or NACK indicates that the reliability of the transmission cannot be guaranteed, and the UE should enable the transmission scheme to ensure reliability. In one embodiment, if the number of consecutive discontinuous reception (DRX) is higher than the threshold, the UE should enable the transmission scheme. In one embodiment, if the number of consecutive NACKs is higher than the threshold, the UE should enable the transmission scheme. In one embodiment, if the number of consecutive NACKs and DTXs is higher than the threshold, the UE should enable the transmission scheme.

[0184] 2. Ratio threshold: For multicast, the TX UE may receive HARQ feedback from more than one RX UE, therefore, if the ratio of the number of discontinuous transmissions DTX to the expected number of hybrid automatic repeat request HARQ feedbacks is higher than the threshold, it indicates that reliability cannot be guaranteed and the UE should enable a transmission scheme to improve reliability. In one embodiment, if the ratio of the number of discontinuous transmissions DTX to the expected number of hybrid automatic repeat request HARQ feedbacks is higher than the configured threshold, the UE should enable a transmission scheme. In another embodiment, if the ratio of the number of DTX to the expected number of HARQ feedbacks is higher than the threshold, the UE should enable a transmission scheme.

[0185] 3. Two thresholds A and B: In one embodiment, the UE first calculates the ratio of the number of DTXs to the expected number of HARQ feedbacks, if the number of ratios above threshold A is higher than threshold B, the UE should enable packet duplication.

[0186] 4. CA configuration includes whether to activate the transmission scheme for SL SRB.

[0187] In some cases, QoS related metrics cannot be applied to determine SL SRBs, considering that QoS flows can only be mapped to data radio bearers DRBs.For signaling radio bearers (SRBs), the UE may be configured with a CA configuration, which includes whether a transmission scheme should be enabled for SL SRBs.

[0188] The preferred configuration only shows the preference of UE2, and whether to apply the configuration may depend on the decision of UE1 or UE1's gNB.

[0189] 5. Example 4 (CSI report of CA)

[0190] In a legacy NR sidelink that supports only one carrier, a UE can issue a CSI request to a peer UE to obtain a CSI report, and the UE does not need to identify which carrier should be measured. However, if CA is used, if the UE receives a CSI request from one carrier, it should identify which carrier needs to be measured and which carrier is used to issue the CSI report.

[0191] Figure 5 An example of a wireless system configuration is shown in which CSI reporting for CA may be performed in a sidelink configuration.

[0192] 6. Carrier of CSI request example

[0193] In one embodiment, if the UE wants to obtain the CSI report of one carrier, the UE should send a CSI request on the carrier. For example, if the UE wants to obtain the CSI of carrier 1, the UE should also send a CSI request on carrier 1.

[0194] 7. CSI measurement example

[0195] In one embodiment, the carrier on which the UE measures CSI is the carrier on which the CSI request is received. For example, if the UE receives a CSI request from carrier 1, the UE should also measure the CSI of carrier 1.

[0196] In one embodiment, the UE should measure CSI of all carriers after receiving a CSI request.

[0197] In one embodiment, the CSI request includes an indicator on which carrier the measurement should be made. The CSI request includes at least one of the following:

[0198] 1. Carrier

[0199] 2.BWP

[0200] 3. Resource Pool

[0201] In one embodiment, the carrier is identified by at least one of the following: carrier ID, carrier index, carrier frequency.

[0202] In one embodiment, a resource pool is identified by at least one of the following items: a resource pool ID, a resource pool index.

[0203] In one embodiment, a BWP is identified by at least one of the following: BWP ID

[0204] For example, if the CSI request includes a carrier ID, the carrier measured by the RX UE is the carrier identified by the carrier ID.

[0205] If the CSI request includes a resource pool index or a resource pool ID, the carrier measured by the RX UE is a carrier including the resource pool identified by the resource pool index or the resource pool ID.

[0206] If the CSI request includes a BWP ID, the carrier measured by the RX UE is the carrier including the BWP identified by the BWP ID.

[0207] 8. CSI Report Example

[0208] In one embodiment, when a UE issues a CSI request in one carrier, in order to help the UE distinguish which carrier the received CSI belongs to, the UE should not trigger CSI reporting in another carrier before the delay bound of the CSI report expires.

[0209] In one embodiment, for a UE to receive a CSI report, the CSI included in the received CSI report is the CSI of the carrier for which the CSI report is received.

[0210] In another embodiment, for the UE to receive a CSI report to identify to which carrier the received CSI report belongs, the CSI report includes at least one of the following items:

[0211] 1. Carrier

[0212] 2.BWP

[0213] 3. Resource Pool

[0214] In this case, if the CSI report includes a carrier ID, the CSI report belongs to the carrier identified by the carrier ID.

[0215] In this case, if the CSI report includes a resource pool ID, the CSI report belongs to a carrier including a resource pool identified by the resource pool ID.

[0216] If the CSI report includes a BWP ID, the carrier of the CSI report is the carrier including the BWP identified by the BWP ID.

[0217] In one embodiment, the UE sends a CSI report on the carrier on which the CSI request is received. For example, if the UE receives a CSI request from carrier 1, the UE should also send a CSI report on carrier 1.

[0218] In one embodiment, the UE should send a CSI report on the carrier on which the CSI is measured. For example, if the UE measures the CSI of carrier 1, the UE should also send a CSI report on carrier 1.

[0219] 9. Additional Embodiments (Example Use Cases)

[0220] A use case could be:

[0221] Example 1:

[0222] The TX UE and RX UE are in RRC connected mode.

[0223] Step 1: TX UE receives CA configuration including preferred carrier from RX UE

[0224] Step 2: The TX UE reports to the gNB the CA configuration, preferred carrier and DST L2 ID of the RX UE received from the RX UE.

[0225] Step 3: The TX UE receives the CA configuration from the TX UE’s gNB, which includes the carriers and PDCP duplication configuration for communication.

[0226] Step 4: The TX UE sends the received CA configuration to the RX UE, the CA configuration including the carriers and PDCP duplication used for communication.

[0227] Step 5: The RX UE reports the received CA configuration including the carriers and PDCP duplication used for communication to the gNB of the RX UE.

[0228] Step 6: The gNB of the TX UE sends a CA configuration to the TX UE to activate carrier 1 and activate PDCP duplication for RB-1, i.e., the CA configuration includes: activation indication, carrier 1, DST L2 ID of the RX UE, activation duplication indication, RB1. Then, the TX UE cannot use carrier 1 and can use PDCP duplication for RB-1.

[0229] Step 7: The TX UE sends a CA configuration to the RX UE, including: activation indication, carrier 1. Then, the RX UE does not need to monitor carrier 1 to obtain received data from the TX UE.

[0230] Step 8: The RX UE reports these two indications to the RX UE’s gNB.

[0231] Example:

[0232] Example-1 assumes that the TX UE is responsible for setting the CA configuration (i.e., UE1 is the TX UE and UE2 is the RX UE), but due to the hidden node problem, the RX UE can obtain a more accurate transmission status. Therefore, the RX UE can be responsible for setting the CA configuration (i.e., UE1 is the RX UE and UE2 is the TX UE). This example shows how the RX UE sets the CA configuration.

[0233] Step 1: The RX UE sends activation of the PDCP duplication of RB-1 and activation of one carrier 1 to the TX UE.

[0234] Step 2: The TX UE shall activate PDCP duplication for RB-1 and use carrier 1 for communication.

[0235] The following list discloses technical solutions implemented by some preferred embodiments.

[0236] 1. A wireless communication method (eg, Fig. 6A The method 610 described in the embodiment of the present invention comprises: receiving (612) carrier aggregation CA operation information by a first user equipment, wherein the first user equipment is configured to: perform device-to-device communication with a second user equipment using CA without relaying through a network device; and operating (614) the first user equipment according to the CA operation information. Various examples of CA operation information are disclosed in this document, such as Section 1 describing CA assistance information and Section 3 describing CA configuration information.

[0237] 2. The method according to solution 1, wherein the CA operation information is received from the second user equipment.

[0238] 3. The method of solution 1, wherein the CA operation information is received from the network device.

[0239] 4. The method according to solution 1 or 2, wherein the first user equipment reports the received CA operation information to the network.

[0240] 5. A method according to any one of solutions 1 to 4, wherein the CA operation information includes CA auxiliary information, and the CA auxiliary information includes at least one of the following items: one or more preferred carriers that are preferably to be used for device-to-device communication, or one or more non-preferred carriers that are not preferably to be used for device-to-device communication, or one or more prohibited carriers that should not be used for device-to-device communication, or one or more allowed carriers that can be used for device-to-device communication, a preferred indicator as to whether the corresponding carrier in the auxiliary information is a preferred carrier, or a non-preferred indicator as to whether the corresponding carrier in the auxiliary information is a non-preferred carrier, or a prohibited carrier indicator as to whether the corresponding carrier in the auxiliary information is a prohibited carrier, or an allowed carrier indicator as to whether the corresponding carrier in the auxiliary information is an allowed carrier, or an object to which the auxiliary information is applied, or a priority of the carrier, or a priority order of one or more carriers.

[0241] 6. The method according to any one of solutions 1 to 4, wherein the CA operation information includes: CA assistance information indicating time slot aggregation related information.

[0242] 7. The method according to solution 6, wherein the time slot aggregation related information includes at least one or more of the following items:

[0243] whether time slot aggregation is supported by the second user equipment,

[0244] The subcarrier spacing of each of the N carriers,

[0245] The symbol length of each of the N carriers,

[0246] the subcarrier spacing supported for each of the N carriers,

[0247] the subcarrier spacing supported for timeslot aggregation on each of the N carriers, or

[0248] The bandwidth part BWP of each of the N carriers is configured.

[0249] 8. The method according to any one of solutions 1 to 4, wherein the CA operation information includes CA assistance information, and the CA assistance information includes the coverage status of each carrier in the N carriers.

[0250] 9. The method according to any one of solutions 1 to 4, wherein the CA operation information includes CA assistance information, and the CA assistance information includes a resource pattern of each carrier in the N carriers.

[0251] 10. The method according to any one of solutions 1 to 4, wherein the CA operation information includes CA assistance information, and the CA assistance information includes synchronization information.

[0252] 11. A method according to any one of solutions 1 to 4, wherein the CA operation information includes CA auxiliary information, and the CA auxiliary information includes at least one of the following items: a CA configuration, a preferred indication as to whether the corresponding CA configuration is a preferred CA configuration, a non-preferred indication indicating whether the corresponding CA configuration is a non-preferred CA configuration, a prohibited indication indicating whether the corresponding CA configuration cannot be used, an object to which the auxiliary information is applied, a preferred CA configuration, a non-preferred CA configuration, or a prohibited CA configuration.

[0253] 12. The method according to any one of solutions 1 to 4, wherein the CA operation information includes CA assistance information, the CA assistance information includes synchronization information, and the synchronization information includes one or more of the following items:

[0254] Synchronization signaling resource configuration for each of the N carriers,

[0255] priority information of synchronization signaling in the device-to-device communication,

[0256] priority information about synchronization signal block transmission in the device-to-device communication,

[0257] (one or more) allow synchronization references; or

[0258] The carrier type for each carrier.

[0259] 13. The method according to any one of solutions 1 to 12, wherein the operating the first user equipment comprises:

[0260] Sending a rejection message for rejecting the CA operation information to the source device of the CA operation information.

[0261] 14. The method of solution 13, wherein the rejection message indicates a rejection reason.

[0262] 15. The method according to any one of solutions 13 to 14, wherein the rejection message indicates a recommended CA configuration.

[0263] 16. The method according to any one of solutions 1 to 4, wherein the CA operation information includes CA configuration information, and the CA configuration information includes one or more mapping rules between services and carriers.

[0264] 17. According to the method of solution 16, the mapping rule is to associate a service with a carrier list including one or more carriers.

[0265] 18. The method of solution 17, wherein the carrier list includes a default carrier assumed to be supported by the peer device.

[0266] 19. The method of solution 17, wherein the carrier list includes optional carriers that are supported based on device capabilities.

[0267] 20. The method according to any one of solutions 1 to 4, wherein the CA operation information includes CA configuration information.

[0268] 21. A method according to any one of solutions 11 to 20, wherein the CA configuration information indicates at least one of the following items: an object to which the CA configuration information is applied, a configuration of a transmission scheme, a carrier status indicator, an RLC channel status indicator, a transmission scheme status indicator, or one or more carriers used for the device-to-device communication.

[0269] 22. The method of solution 21, wherein the carrier status indicator indicates one of: the carrier is activated or the carrier is deactivated.

[0270] 23. The method of solution 21, wherein the RLC channel status indicator indicates at least one of: activating the RLC channel, or deactivating the RLC channel.

[0271] 24. The method of solution 21, wherein the transmission scheme status indicator indicates at least one of: packet duplication is activated, packet duplication is deactivated, packet splitting is activated, or packet splitting is deactivated.

[0272] 25. The method according to solution 21, wherein the transmission scheme is at least one of the following: a packet duplication scheme, or a packet splitting scheme.

[0273] 26. The method of solution 24, wherein the packet duplication is at least one of a Packet Data Convergence Protocol (PDCP) duplication or a Media Access Control (MAC) duplication.

[0274] 27. The method of solution 24, wherein the packet splitting is at least one of a Packet Data Convergence Protocol (PDCP) splitting or a Media Access Control (MAC) splitting.

[0275] 28. The method of solution 21, wherein the transmission scheme is enabled based on a condition, wherein the condition includes one or more of the following:

[0276] Maximum Stream Bit Rate (MFBR) threshold,

[0277] the guaranteed stream bit rate (GFBR) threshold, or

[0278] Aggregate Maximum Bit Rate (AMBR) threshold.

[0279] Additional details of Solutions 1 to 28 are disclosed in Sections 1 to 9 of this document.

[0280] 29. A wireless communication method (e.g., Figure 6B The method 620 depicted in the figure includes: sending (622) carrier aggregation CA configuration information by a wireless device to a first user device, wherein the first user device is configured to: use CA to perform device-to-device communication with a second user device without relaying through a network device.

[0281] 30. The method of solution 29, wherein the wireless device is a second user equipment.

[0282] 31. The method of solution 29, wherein the wireless device is a network device.

[0283] 32. The method according to any one of solutions 29 to 31, wherein the CA configuration information indicates a preferred carrier.

[0284] 33. The method according to any one of solutions 29 to 31, wherein the CA configuration information indicates a non-preferred carrier or a prohibited carrier that will not be used for the device-to-device communication.

[0285] 34. A method according to any one of solutions 29 to 33, wherein the CA configuration information indicates time slot aggregation related information.

[0286] 35. The method according to solution 34, wherein the time slot aggregation related information includes one or more of the following items:

[0287] whether time slot aggregation is supported by the second user equipment,

[0288] The subcarrier spacing of each of the N carriers,

[0289] The symbol length of each of the N carriers,

[0290] the subcarrier spacing supported for each of the N carriers,

[0291] the subcarrier spacing supported for timeslot aggregation on each of the N carriers, or

[0292] The bandwidth part BWP of each of the N carriers is configured.

[0293] 36. A method according to any one of solutions 29 to 35, wherein the CA configuration information includes: the coverage status of each carrier in the N carriers.

[0294] 37. A method according to any one of solutions 29 to 35, wherein the CA configuration information includes: a resource pattern for each of the N carriers.

[0295] 38. A method according to any one of solutions 29 to 37, wherein the CA configuration information includes synchronization information.

[0296] 39. The method of solution 38, wherein the synchronization information includes one or more of the following:

[0297] Synchronization signaling resource configuration for each of the N carriers,

[0298] priority information of synchronization signaling in the device-to-device communication, or

[0299] Priority information regarding transmission of synchronization signal blocks in the device-to-device communication.

[0300] 40. The method of any one of solutions 29 to 39, wherein operating the wireless device comprises:

[0301] Send a rejection message for rejecting the CA configuration information to the source device of the CA configuration information.

[0302] 41. The method of solution 40, wherein the rejection message indicates a rejection condition.

[0303] 42. The method according to any one of solutions 40 to 41, wherein the first user equipment further indicates a recommended CA configuration.

[0304] 43. A method according to any one of solutions 29 to 42, wherein the CA configuration information includes two mapping rules between services and carriers.

[0305] 44. The method of solution 43, wherein one of the mapping rules is mandatory and the other mapping rule is optional.

[0306] 45. A method according to any one of solutions 29 to 44, wherein the CA configuration information includes: a split or copy configuration at the Packet Data Convergence Protocol PDCP layer, wherein the split or copy configuration identifies: a radio link control (RLC) channel or a logical channel identifier (ID) for protecting packet data.

[0307] 46. ​​The method of solution 45, wherein the copy or split operation is selectively performed based on a condition, wherein the condition includes one or more of the following:

[0308] Maximum Stream Bit Rate (MFBR) threshold,

[0309] Guaranteed Stream Bit Rate (GFBR) threshold,

[0310] Aggregate Maximum Bit Rate (AMBR) threshold.

[0311] Additional details of Solutions 1 to 46 are disclosed in Sections 1 to 9 of this document.

[0312] 47. A wireless communication method (e.g., Figure 6C The method 630 depicted in the embodiment includes: sending (632) a request for reporting channel state information (CSI) by a first user device to a second user device, wherein the first user device is configured to use one or more carriers of N carriers to perform device-to-device communication with the second user device without relaying through a network device, wherein N is an integer greater than 1.

[0313] 48. The method of solution 47, wherein the request identifies a carrier from among N carriers whose channel status is to be reported.

[0314] 49. The method of solution 47, wherein the request comprises at least one of: a carrier, a bandwidth part (BWP), or a resource pool.

[0315] 50. A wireless communication method, comprising:

[0316] receiving, by the first user equipment, a channel state report including channel state information (CSI) from the second user equipment using device-to-device communication,

[0317] The first user equipment is configured to use one or more carriers among N carriers to perform the device-to-device communication with the second user equipment without relaying through a network device, wherein N is an integer greater than 1.

[0318] 51. The method of solution 50, wherein the channel state report comprises at least one of: a carrier, a bandwidth part (BWP), or a resource pool.

[0319] 52. The method of solution 49 or 51, wherein the carrier is identified by at least one of the following: carrier ID, carrier index, carrier frequency.

[0320] 53. A method according to solution 49 or 51, wherein the resource pool is identified by at least one of the following: a resource pool ID or a resource pool index.

[0321] 54. The method of solution 49 or 51, wherein the BWP is identified by a BWP ID.

[0322] 55. The method of solution 50, wherein the first user equipment considers that the CSI included in the received CSI report is the CSI of the carrier on which the CSI report is received.

[0323] 56. A wireless communication method (e.g., Fig.6D The method 640 depicted in the embodiment includes: receiving (642) a report request for reporting a channel state by a second user device from a first user device, wherein the second user device is configured to: use one or more carriers among N carriers to perform device-to-device communication with the first user device without relaying through a network device, wherein N is an integer greater than 1; and performing (644) a channel state information (CSI) related operation according to the report request.

[0324] 57. The method of solution 56, wherein the report request identifies a carrier from among N carriers whose channel status is to be reported.

[0325] 58. The method according to any one of solutions 56 to 57, wherein the CSI operation comprises:

[0326] A channel state report is sent by the second user equipment using the device-to-device communication, the channel state report comprising: a channel state report for each of the N carriers.

[0327] 59. The method according to any one of solutions 56 to 57, wherein the CSI operation comprises:

[0328] A channel state report for the requested carrier is sent from the second user equipment in a separate channel state report message using the device-to-device communication.

[0329] 60. The method according to any one of solutions 56 to 59, further comprising:

[0330] The report request is received by the second user equipment from the first user equipment on a carrier, and the carrier is preconfigured for transmission of the report request.

[0331] 61. The method according to any one of solutions 56 to 60, further comprising:

[0332] A carrier to be used for transmission of a channel state report is received by the second user equipment from the first user equipment.

[0333] 62. The method according to any one of solutions 56 to 61, further comprising:

[0334] A measurement carrier is received by the second user equipment from the first user equipment, and channel state measurement is performed on the measurement carrier.

[0335] Other examples of CSI reporting, measurements, and carriers used for CSI are disclosed in Sections 5 to 8 of this document.

[0336] 63. A wireless communication device, comprising a processor, wherein the processor is configured to implement the method as described in the above solution. The device may use Figure 8 The hardware platform described is implemented.

[0337] 64. A computer readable medium having processor executable codes stored thereon, which, when executed by a processor, cause the processor to implement the method described above.

[0338] Figure 7 An example of a wireless communication system 1700 in which the technology according to one or more embodiments of the present technology can be applied is shown. The wireless communication system 1700 may include one or more base stations (BSs) 1705a, 1705b, one or more wireless devices 1710a, 1710b, 1710c, 1710d, and a core network 1725. The base stations 1705a, 1705b may provide wireless services to the wireless devices 1710a, 1710b, 1710c, and 1710d in one or more wireless sectors. In some implementations, the base stations 1705a, 1705b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors.

[0339] The core network 1725 can communicate with one or more base stations 1705a, 1705b. The core network 1725 provides connections with other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases to store information related to subscribed wireless devices 1710a, 1710b, 1710c, and 1710d. The first base station 1705a can provide wireless services based on a first wireless access technology, and the second base station 1705b can provide wireless services based on a second wireless access technology. Depending on the deployment scenario, base stations 1705a and 1705b can be co-located or installed separately on site. Wireless devices 1710a, 1710b, 1710c, and 1710d can support a variety of different wireless access technologies. The techniques and embodiments described in this document can be implemented by the base stations of the wireless devices described in this document.

[0340] Figure 8 1805 is a block diagram representation of a portion of a wireless station to which one or more embodiments of the present technology may be applied. A wireless station 1805 (such as a base station or a wireless device (or UE), such as various enumerated wireless devices described in this document) may include a processor electronic device 1810, such as a microprocessor that implements one or more wireless technologies proposed in this document. The wireless station 1805 may include a transceiver electronic device 1815 to send and / or receive wireless signals through one or more communication interfaces (such as an antenna 1820). The wireless station 1805 may include other communication interfaces for sending and receiving data. The wireless station 1805 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some implementations, the processor electronic device 1810 may include at least a portion of the transceiver electronic device 1815. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using the wireless station 1805. In some embodiments, the wireless station 1805 may be configured to perform the methods described herein.

[0341] It should be appreciated that this document discloses techniques that can benefit various embodiments to perform sidelink communications using carrier aggregation. In one advantageous aspect, the disclosed techniques can be used to reduce power consumption of user equipment.

[0342] It should be understood that this document discloses technologies that can be embodied in various embodiments and configurations. It should be understood that concepts from some embodiments can be used in other embodiments. The disclosure and other embodiments, modules and functional operations described in this document can be implemented in digital electronic circuit systems, or in computer software, firmware or hardware, including the structures disclosed in this document and their structural equivalents, or in a combination of one or more of them. The disclosed embodiments and other embodiments can be implemented as one or more computer program products, that is, one or more modules of computer program instructions encoded on a computer-readable medium for a data processing device to execute or control the operation of the data processing device. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that affects a machine-readable propagation signal, or a combination of one or more of them. The term "data processing device" covers all devices, devices and machines for processing data, including, for example, a programmable processor, a computer or multiple processors or computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, for example, code that constitutes a processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, such as a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

[0343] A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any manner, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more code modules, subroutines, or portions). A computer program may be deployed to execute on one or more computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

[0344] The processes and logic flows described in this document may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be performed by, and apparatus may also be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0345] For example, processors suitable for executing computer programs include general and special purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, or be operably coupled to such mass storage devices to receive data from them or to transmit data to them or both. However, a computer does not necessarily have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by or incorporated into a dedicated logic circuit system.

[0346] Although this document contains many details, these should not be interpreted as limitations on the scope of any invention or what may be claimed, but rather as descriptions of features that may be specific to a particular embodiment of a particular invention. Certain features described in this patent document in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination. In addition, although features may be described above as working in certain combinations and even initially claimed as such, one or more features may be removed from the claimed combination in some cases, and the claimed combination may involve sub-combinations or variations of sub-combinations.

[0347] Similarly, although operations are depicted in a particular order in the drawings, this should not be understood as requiring that these operations be performed in the particular order shown or in sequence, or that all of the operations shown be performed to obtain the desired results. In addition, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

[0348] Only a few implementations and examples are described, and other implementations, enhancements, and variations may be made based on what is described and illustrated in this patent document.

Claims

1. A wireless communication method, comprising: Receiving carrier aggregation (CA) operation information by a first user equipment, wherein the first user equipment is configured to: perform device-to-device communication with a second user equipment using CA without relaying through a network device; and The first user equipment is operated according to the CA operation information. 2 . The method of claim 1 , wherein the CA operation information is received from the second user equipment. The method of claim 1 , wherein the CA operation information is received from the network device. The method according to claim 1 or 2, wherein the first user equipment reports the received CA operation information to a network.

5. The method according to any one of claims 1 to 4, wherein the CA operation information includes CA auxiliary information, and the CA auxiliary information includes at least one of the following items: one or more preferred carriers that are preferably to be used for device-to-device communication, or one or more non-preferred carriers that are not preferably to be used for device-to-device communication, or one or more prohibited carriers that should not be used for device-to-device communication, or one or more allowed carriers that can be used for device-to-device communication, a preferred indicator as to whether the corresponding carrier in the auxiliary information is a preferred carrier, or a non-preferred indicator as to whether the corresponding carrier in the auxiliary information is a non-preferred carrier, or a prohibited carrier indicator as to whether the corresponding carrier in the auxiliary information is a prohibited carrier, or an allowed carrier indicator as to whether the corresponding carrier in the auxiliary information is an allowed carrier, or an object to which the auxiliary information is applied, or a priority of a carrier, or a priority order of one or more carriers.

6. The method according to any one of claims 1 to 4, wherein the CA operation information comprises: CA assistance information indicating timeslot aggregation related information.

7. The method according to claim 6, wherein the time slot aggregation related information comprises at least one or more of the following items: whether time slot aggregation is supported by the second user equipment, The subcarrier spacing of each of the N carriers, The symbol length of each of the N carriers, the subcarrier spacing supported for each of the N carriers, the subcarrier spacing supported for timeslot aggregation on each of the N carriers, or The bandwidth part BWP of each of the N carriers is configured.

8. The method according to any one of claims 1 to 4, wherein the CA operation information comprises CA assistance information, and the CA assistance information comprises a coverage status of each carrier in N carriers.

9. The method according to any one of claims 1 to 4, wherein the CA operation information comprises CA assistance information, the CA assistance information comprising a resource pattern of each of the N carriers.

10. The method according to any one of claims 1 to 4, wherein the CA operation information comprises CA assistance information, and the CA assistance information comprises synchronization information.

11. The method according to any one of claims 1 to 4, wherein the CA operation information includes CA auxiliary information, and the CA auxiliary information includes at least one of the following items: a CA configuration, a preferred indication as to whether the corresponding CA configuration is a preferred CA configuration, a non-preferred indication indicating whether the corresponding CA configuration is a non-preferred CA configuration, a prohibited indication indicating whether the corresponding CA configuration cannot be used, an object to which the auxiliary information is applied, a preferred CA configuration, a non-preferred CA configuration, or a prohibited CA configuration.

12. The method according to any one of claims 1 to 4, wherein the CA operation information comprises CA assistance information, the CA assistance information comprises synchronization information, and the synchronization information comprises one or more of the following items: Synchronization signaling resource configuration for each of the N carriers, priority information of synchronization signaling in the device-to-device communication, priority information about synchronization signal block transmission in the device-to-device communication, (one or more) allow synchronization references; or The carrier type for each carrier.

13. The method according to any one of claims 1 to 12, wherein the operating the first user equipment comprises: Sending a rejection message for rejecting the CA operation information to the source device of the CA operation information. The method of claim 13 , wherein the rejection message indicates a rejection reason.

15. The method according to any one of claims 13 to 14, wherein the rejection message indicates a recommended CA configuration.

16. The method according to any one of claims 1 to 4, wherein the CA operation information comprises CA configuration information, and the CA configuration information comprises one or more mapping rules between services and carriers.

17. The method according to claim 16, wherein the mapping rule is that one service is associated with a carrier list including one or more carriers.

18. The method of claim 17, wherein the carrier list comprises: The default carrier assumed to be supported by the peer device.

19. The method of claim 17, wherein the carrier list comprises: Optional carriers supported based on device capabilities.

20. The method according to any one of claims 1 to 4, wherein the CA operation information comprises CA configuration information.

21. The method according to any one of claims 11 to 20, wherein the CA configuration information indicates at least one of the following items: an object to which the CA configuration information applies, a configuration of a transmission scheme, a carrier status indicator, an RLC channel status indicator, a transmission scheme status indicator, or one or more carriers used for the device-to-device communication.

22. The method of claim 21, wherein the carrier status indicator indicates one of: the carrier is activated, or the carrier is deactivated.

23. The method of claim 21, wherein the RLC channel status indicator indicates at least one of: activating the RLC channel, or deactivating the RLC channel.

24. The method of claim 21, wherein the transmission scheme status indicator indicates at least one of: packet duplication is activated, packet duplication is deactivated, packet splitting is activated, or packet splitting is deactivated.

25. The method of claim 21, wherein the transmission scheme is at least one of the following: a packet duplication scheme, or a packet splitting scheme.

26. The method of claim 24, wherein the packet duplication is at least one of Packet Data Convergence Protocol (PDCP) duplication or Media Access Control (MAC) duplication.

27. The method of claim 24, wherein the packet splitting is at least one of a Packet Data Convergence Protocol (PDCP) splitting or a Media Access Control (MAC) splitting.

28. The method of claim 21, wherein the transmission scheme is enabled based on a condition, wherein the condition comprises one or more of the following: Maximum Stream Bit Rate (MFBR) threshold, the guaranteed stream bit rate (GFBR) threshold, or Aggregate Maximum Bit Rate (AMBR) threshold.

29. A wireless communication method, comprising: Carrier aggregation (CA) configuration information is sent by a wireless device to a first user equipment, wherein the first user equipment is configured to perform device-to-device communication with a second user equipment using CA without relaying through a network device.

30. The method of claim 29, wherein the wireless device is a second user equipment.

31. The method of claim 29, wherein the wireless device is a network device.

32. The method according to any one of claims 29 to 31, wherein the CA configuration information indicates a preferred carrier.

33. The method according to any one of claims 29 to 31, wherein the CA configuration information indicates a non-preferred carrier or a prohibited carrier which is not to be used for the device-to-device communication.

34. The method according to any one of claims 29 to 33, wherein the CA configuration information indicates time slot aggregation related information.

35. The method according to claim 34, wherein the time slot aggregation related information comprises one or more of the following: whether time slot aggregation is supported by the second user equipment, The subcarrier spacing of each of the N carriers, The symbol length of each of the N carriers, the subcarrier spacing supported for each of the N carriers, the subcarrier spacing supported for timeslot aggregation on each of the N carriers, or The bandwidth part BWP of each of the N carriers is configured.

36. The method according to any one of claims 29 to 35, wherein the CA configuration information comprises: The coverage status of each of the N carriers.

37. The method according to any one of claims 29 to 35, wherein the CA configuration information comprises: A resource pattern for each of the N carriers.

38. The method according to any one of claims 29 to 37, wherein the CA configuration information comprises synchronization information.

39. The method of claim 38, wherein the synchronization information comprises one or more of the following: Synchronization signaling resource configuration for each of the N carriers, priority information of synchronization signaling in the device-to-device communication, or Priority information regarding transmission of synchronization signal blocks in the device-to-device communication.

40. The method of any one of claims 29 to 39, wherein said operating said wireless device comprises: Send a rejection message for rejecting the CA configuration information to the source device of the CA configuration information. The method of claim 40 , wherein the rejection message indicates a rejection condition.

42. The method according to any one of claims 40 to 41, wherein the first user equipment further indicates a recommended CA configuration.

43. The method according to any one of claims 29 to 42, wherein the CA configuration information comprises two mapping rules between services and carriers.

44. The method of claim 43, wherein one of the mapping rules is mandatory and the other mapping rule is optional.

45. The method according to any one of claims 29 to 44, wherein the CA configuration information comprises: A split or duplicate configuration at a Packet Data Convergence Protocol (PDCP) layer, wherein the split or duplicate configuration identifies: a Radio Link Control (RLC) channel or a logical channel identifier (ID) for protecting packet data.

46. ​​The method of claim 45, wherein the copy or split operation is selectively performed based on a condition, wherein the condition comprises one or more of the following: Maximum Stream Bit Rate (MFBR) threshold, Guaranteed Stream Bit Rate (GFBR) threshold, Aggregate Maximum Bit Rate (AMBR) threshold.

47. A wireless communication method, comprising: The first user equipment sends a request for reporting channel state information (CSI) to the second user equipment, The first user equipment is configured to use one or more carriers among N carriers to perform device-to-device communication with the second user equipment without relaying through a network device, wherein N is an integer greater than 1.

48. The method of claim 47, wherein the request identifies a carrier from among N carriers whose channel status is to be reported.

49. The method of claim 47, wherein the request comprises at least one of: a carrier, a bandwidth part (BWP), or a resource pool.

50. A wireless communication method, comprising: receiving, by the first user equipment, a channel state report including channel state information (CSI) from the second user equipment using device-to-device communication, The first user equipment is configured to use one or more carriers among N carriers to perform the device-to-device communication with the second user equipment without relaying through a network device, wherein N is an integer greater than 1.

51. The method of claim 50, wherein the channel state report comprises at least one of: a carrier, a bandwidth part (BWP), or a resource pool.

52. The method of claim 49 or 51, wherein the carrier is identified by at least one of: carrier ID, carrier index, carrier frequency.

53. The method of claim 49 or 51, wherein the resource pool is identified by at least one of: a resource pool ID or a resource pool index.

54. The method of claim 49 or 51, wherein the BWP is identified by a BWP ID.

55. The method of claim 50, wherein the first user equipment considers that the CSI included in the received CSI report is the CSI of the carrier for which the CSI report is received.

56. A wireless communication method, comprising: Receiving, by a second user equipment, a report request for reporting a channel state from a first user equipment, wherein the second user equipment is configured to: perform device-to-device communication with the first user equipment using one or more carriers of N carriers without relaying through a network device, wherein N is an integer greater than 1; as well as A channel state information (CSI) related operation is performed according to the report request.

57. The method of claim 56, wherein the report request identifies a carrier whose channel status is to be reported from among N carriers.

58. The method of any one of claims 56 to 57, wherein the CSI operation comprises: A channel state report is sent by the second user equipment using the device-to-device communication, the channel state report comprising: a channel state report for each of the N carriers.

59. The method of any one of claims 56 to 57, wherein the CSI operation comprises: A channel state report for the requested carrier is sent from the second user equipment in a separate channel state report message using the device-to-device communication.

60. The method according to any one of claims 56 to 59, further comprising: The report request is received by the second user equipment from the first user equipment on a carrier, and the carrier is preconfigured for transmission of the report request.

61. The method according to any one of claims 56 to 60, further comprising: A carrier to be used for transmission of a channel state report is received by the second user equipment from the first user equipment.

62. The method according to any one of claims 56 to 61, further comprising: A measurement carrier is received by the second user equipment from the first user equipment, and channel state measurement is performed on the measurement carrier.

63. A wireless communication apparatus comprising a processor, wherein the processor is configured to implement the method according to one or more of claims 1 to 62.

64. A computer readable medium having stored thereon processor executable code, which, when executed by a processor, causes the processor to implement the method according to any one or more of claims 1 to 62.

Images