Systems and methods for performing redundant sidelink communications

Abstract

Systems and methods for performing redundant sidelink communications are provided. A wireless communication device can receive reporting configuration information from a network. The wireless communication device can transmit, to the network, a report based on the reporting configuration information regarding a subsequent conditional PSCell addition or change (CPAC) or a subsequent CPAC.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, including but not limited to systems and methods for performing redundant sidelink communications. Background Technology

[0002] Coverage is a key consideration in cellular network deployment. With the rise of interconnected devices, there is an increasing focus on efficient device communication. Current 3GPP (3rd Generation Partnership Project) standards cover everything from 3G (3rd Generation Mobile Communication) to 5G (5th Generation Mobile Communication) and future evolution, emphasizing the importance of seamless communication between various devices, from smart home devices to wearables. In industrial settings, the complexity of tasks often necessitates collaboration. This requires multiple collaborative operations management systems designed to create workgroups and manage different types of equipment to accomplish the required tasks. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more of the problems presented in the prior art and provide additional features that will become apparent when taken into account in conjunction with the following drawings and by reference to the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example only and are not restrictive, and that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure, as will be apparent to those skilled in the art who have read this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A wireless communication device (e.g., a UE) can receive / obtain / retrieve report configuration information from a network. The wireless communication device can send / transmit / provide to the network a report based on the report configuration information regarding a subsequent Conditional PSCell Addition or Change (CPAC) or subsequent CPAC. In a particular embodiment, the report configuration information may include at least one of the following: a first indication or threshold information.

[0005] In a particular embodiment, the first indication may instruct the wireless communication device to report the amount of time elapsed between initiating a conditional reconfiguration for a target PSCell / PCell (Primary Cell) and receiving the final conditional reconfiguration for that target PSCell / PCell. In a particular embodiment, the threshold information may indicate a threshold value representing the time elapsed between initiating a conditional reconfiguration for a target PSCell / PCell and receiving the final conditional reconfiguration for that target PSCell / PCell. In a particular embodiment, the report may include the amount of elapsed time. In a particular embodiment, the wireless communication device may send a reason for the conditional reconfiguration problem to the network.

[0006] In certain embodiments, the wireless communication device may receive a message from the network including a report request. In some embodiments, in response to the report request, the report may include at least one of the following: an indication of whether a CPAC or subsequent CPAC was performed after the last conditional reconfiguration for the target PSCell was acquired; the number of times a CPAC or subsequent CPAC was performed after the last conditional reconfiguration was acquired; a counter for subsequent CPACs; a counter for subsequent CPACs for each cell; the amount of time elapsed between the last two conditional reconfigurations; and / or a selected candidate configuration for subsequent CPACs.

[0007] In certain embodiments, the counter for the subsequent CPAC may include at least one of the following: when a conditional reconfiguration for the subsequent CPAC is performed, the wireless communication device may increment the counter by 1; and / or if the conditional reconfiguration for the subsequent CPAC is changed or released, the wireless communication device may reset the counter for the subsequent CPAC to 0. In some embodiments, the counter for the subsequent CPAC may be stored in... Var-Report (Reporting Variables) middle.

[0008] In certain embodiments, the counter for subsequent CPACs for each cell may include at least one of the following: when a conditional reconfiguration of a subsequent CPAC for a selected cell is performed, the wireless communication device may increment the counter for the subsequent CPAC for that selected cell by 1; and / or if the conditional reconfiguration of a subsequent CPAC associated with the cell is changed or released, the wireless communication device may reset the counter for the subsequent CPAC for that cell to 0. In some embodiments, the counter for the subsequent CPAC may be stored in... Var-Report In some implementations, the selected cell can be a source cell or a candidate target cell for subsequent CPAC.

[0009] In certain embodiments, the amount of time elapsed between the last two conditional reconfigurations may include at least one of the following: when a conditional reconfiguration for a subsequent CPAC is performed, the wireless communication device may stop a first timer and set the value of the first timer to a first time value; and / or if the conditional reconfiguration for a subsequent CPAC is changed or released, the wireless communication device may restart the first timer or reset the first timer to 0. In some embodiments, the first time value may be stored in... Var-Report middle.

[0010] In a particular implementation, the selected candidate configuration for subsequent CPAC may include at least one of the following: a selected cell ID for performing subsequent CPAC; the cell ID being performed or selected. condReconfigId (Conditional Reconfiguration Id) ; and / or stored in the MCG (Master Cell Group). VarConditionalReconfig (conditional reconfiguration variable) It may be stored in the SCG (Secondary Cell Group). VarConditionalReconfig The selected candidate configuration is indicated in the [reference]. In a particular implementation, the selected candidate configuration for subsequent CPAC may include at least one of the following: all selected cell IDs for performing subsequent CPAC and the associated subsequent CPAC configuration; and / or all selected [reference] cell IDs for performing subsequent CPAC. condReconfigId The subsequent CPAC configuration associated with this subsequent CPAC. In a particular implementation, the selected cell IDs can be listed in the execution order. In a particular implementation, the selected... condReconfigId They can be listed in the order of execution.

[0011] The system of the technical solution disclosed herein can support the performance of mobility robustness optimization for wireless communication based on at least one of the following example configurations (e.g., features or solutions), especially when the UE performs conditional PSCell additions or changes: Example Configuration 1: Report Configuration Reception Example Configuration 2: Time Elapsed Report Example Configuration 3: Report Reason Example Configuration 4: UE Information Request Response Example Configuration 5: Subsequent CPAC Counter Example Configuration 6: Subsequent CPAC Counters for Each Cell Example Configuration 7: Time elapsed between reconfigurations Example Configuration 8: Selected Subsequent CPAC Candidate Configuration Attached Figure Description

[0012] Various exemplary embodiments of this solution are described in detail below with reference to the following figures or drawings. These figures are provided for illustrative purposes only and depict only exemplary embodiments of this solution to aid the reader's understanding of it. Therefore, these figures should not be considered as limitations on the breadth, scope, or applicability of this solution. It should be noted that these figures are not necessarily drawn to scale for clarity and ease of explanation.

[0013] Figure 1 An example cellular communication network that can implement the techniques disclosed herein is shown according to an embodiment of the present disclosure;

[0014] Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; and

[0015] Figure 3 A flowchart is shown as an example method for performing redundant sidelink communication according to an embodiment of the present disclosure. Detailed Implementation

[0016] 1. Mobile Communication Technology and Environment

[0017] Figure 1 An example wireless communication network and / or system 100 according to an embodiment of this disclosure is illustrated, in which the technologies disclosed herein can be implemented. In the following discussion, the wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as network 100. Such an example network 100 includes base stations 102 (hereinafter referred to as "BS 102", also called wireless communication nodes) and user equipment 104 (hereinafter referred to as "UE 104", also called wireless communication devices) that can communicate with each other via communication links 110 (e.g., wireless communication channels), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are included within the corresponding geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to the intended users of that cell.

[0018] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can also be divided into subframes 120 / 127, which can include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are generally described herein as non-limiting examples of "communication nodes" capable of practicing the methods disclosed herein. According to various embodiments of this solution, such communication nodes may be capable of wireless and / or wired communication.

[0019] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM (orthogonal frequency division multiplexing) / OFDMA (orthogonal frequency division multiple access) signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating features that do not need to be described in detail herein. In one exemplary embodiment, system 200 may be configured to... Figure 1 The wireless communication environment 100 is a wireless communication environment in which communication (e.g., transmission and reception) data symbols are as described above.

[0020] System 200 generally includes base station 202 (hereinafter referred to as "BS 202") and user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes BS (base station) transceiver module 210 (hereinafter also referred to as transceiver module 210, transceiver 210 or base station transceiver 210), BS antenna 212 (hereinafter also referred to as antenna 212, downlink antenna 212 or RF antenna arrangement 212), BS processor module 214 (hereinafter also referred to as processor module 214), BS memory module 216 (hereinafter also referred to as memory module 216) and network communication module 218, each module being coupled and interconnected to each other as needed via data communication bus 220. UE 204 includes a UE (User Equipment) transceiver module 230 (hereinafter also referred to as UE transceiver 230, transceiver module 230, or transceiver 230), a UE antenna 232 (hereinafter also referred to as antenna 232, uplink antenna 232, or RF antenna arrangement 232), a UE memory module 234 (hereinafter also referred to as memory module 234), and a UE processor module 236 (hereinafter also referred to as processor module 236). Each module is coupled to and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250 (hereinafter also referred to as: wireless transmission link 250, wireless data communication link 250), which may be any wireless channel or other medium suitable for the data transmission described herein.

[0021] As those skilled in the art will understand, system 200 may also include, in addition to Figure 2 Any number of modules other than those shown herein. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally according to their functionality. Whether this functionality is implemented as hardware, firmware, or software may depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art described herein can implement such functionality in a suitable manner for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0022] According to some embodiments, UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-division duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that while the downlink transmitter is coupled to downlink antenna 212, the uplink receiver circuitry is coupled to uplink antenna 232 to receive transmissions via wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 to receive transmissions on the wireless transmission link 250 while the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0023] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to application to specific standards and associated protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0024] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, UE 204 may be embodied in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using the following devices designed to perform the functions described herein: general-purpose processors, content-addressable memory, digital signal processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), any suitable programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of multiple computing devices, such as a combination of a digital signal processor and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors coupled with a digital signal processor core, or any other such configuration.

[0025] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly implemented in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any practical combination thereof. Storage modules 216 and 234 can be implemented as random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, removable disks, optical disc read-only memory (CD-ROM), or any other form of storage medium known in the art. In this respect, storage modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to storage modules 216 and 234 respectively. Storage modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0026] Network communication module 218 broadly represents the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or WiMAX (World Interoperability for Microwave Access) services. In a typical but non-limiting deployment, network communication module 218 provides an 802.3 Ethernet interface, allowing base station transceiver 210 to communicate with traditional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and their various variations used in this document in relation to a specified operation or function refer to devices, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0027] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to its upper and lower layers. The OSI model also defines logical networks and effectively describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer may be any other layer.

[0028] Various exemplary embodiments of the present solution are described below with reference to the accompanying drawings to enable those skilled in the art to formulate and use the present solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of the present solution after reading this disclosure. Therefore, the present solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of the steps in the methods disclosed herein is merely illustrative. Based on design preferences, the specific order or hierarchy of the steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.

[0029] 2. Systems and methods for performing redundant sidelink communication

[0030] In a communication system, the network can control the mobility applicable to a UE in the RRC_CONNECTED state. In a particular implementation, a conditional handover (CHO) is defined as a handover performed by the UE when one or more handover execution conditions are met / satisfied. For example, the UE can begin evaluating / determining one or more execution conditions upon receiving a CHO configuration, and can stop evaluating the conditions once the handover has been performed. In a particular implementation, the CHO configuration may include the configuration of one or more CHO candidate cells generated by one or more candidate base stations and one or more execution conditions generated by the source base station. In a particular implementation, the UE can perform a handover or cell change based on the CHO configuration. A similar CHO principle can be applied to conditional PSCell (SpCell of secondary cell groups) changes and / or conditional PSCell additions (CPACs) in multi-connectivity operations when the UE is configured for multi-connectivity operations. In a particular implementation, the SpCell can be the primary cell of the primary cell group or the primary cell of the secondary cell group.

[0031] In certain implementations, it may be desirable to inform the network whether the provided CHO configuration is appropriate and whether the network should perform mobility robustness optimization. In some implementations, this optimization can detect connection failures due to premature or late handovers or handovers to the wrong cell. In certain implementations, it may be desirable to inform the network whether the provided CPAC configuration is appropriate and whether the network should perform mobility robustness optimization. In some implementations, this optimization can detect CPAC failures due to late CPC execution, premature CPC execution, or CPC / CPA execution to the wrong PSCell. When a CHO or CPAC failure occurs, the UE can store the failure information and report the failure to the network. In certain implementations, even if CPAC is successful, excessive elapsed time of timers T304, T310, or T312 can indicate / reflect that the configuration is suboptimal. In certain implementations, to analyze such suboptimal CPAC successes, the UE can collect successful PSCell change reports based on triggers configured by the network. A trigger can occur when the elapsed time of timer T310, timer T312, or timer T304 is greater than the configured / predefined threshold value for timer T310, timer T312, or timer T304. Based on this report, the network can decide / determine whether to adjust the timer value for T310, T312, or T304.

[0032] In a particular implementation, subsequent conditional PSCell addition or change (subsequent CPAC) can be defined as a conditional PSCell addition or change process performed after PSCell addition, PSCell change, PCell (SpCell of the primary cell group) change, or SCG release, based on the subsequent CPAC configuration pre-configured for (one or more) candidate PSCells, without reconfiguration and re-initiation of CPC / CPA.

[0033] In certain implementations, the UE can maintain / retain the configured subsequent CPAC configuration (unless the network instructs the release of the subsequent CPAC configuration) and evaluate the execution conditions for the candidate PSCell upon completion of PSCell addition, PSCell change, PCell change, or SCG release. In some implementations, intra-SN subsequent CPAC initiated by the SN and / or inter-SN subsequent CPAC initiated by the MN or SN can be supported. In certain implementations, the UE can maintain (or repeat) the execution of CPAC multiple times after obtaining the subsequent CPAC configuration. However, in some implementations, if the ratio of the elapsed time of timer T310 (or T312 or T304) to the configured value of timer T310 (or T312 or T304) is greater than a configured / defined threshold, the UE can only report the latest CPAC execution status. In some implementations, after providing the subsequent CPAC configuration, the network may not be able to obtain information about each CPAC execution status.

[0034] In certain implementations, SPR reports can assist the network in determining whether timers T304, T310, or T312 are set appropriately. For example, a UE may collect SPR reports based on triggering conditions such as whether the ratio of the elapsed time of a timer (such as T304, T310, or T312) to the configured value of the timer (such as T304, T310, or T312) is greater than the configured / predefined threshold percentage of the associated timer. Based on this report, the network can optimize PSCell change / CPC configuration, associated mobility thresholds, or adjust the T304 / T310 / T312 timer values.

[0035] In certain implementations, if the ratio of the elapsed time of a timer (e.g., T304, T310, or T312) to the configured value of the timer (T304, T310, or T312) is not greater than a configured / predefined threshold percentage of the associated timer, then the UE may not send an SPR to the network regardless of whether the UE performs a CPAC or a subsequent CPAC. Therefore, the network may be unable to determine whether or when a subsequent CPAC has been performed / executed on the UE side.

[0036] In a particular implementation, in order to notify the network of the applicability of the provided subsequent CPAC or CPAC configuration, in response to determining that the elapsed time is greater than the configuration threshold, the network may instruct / indicate the UE to report initiating a conditional reconfiguration for the target PSCell and receiving the last [condition] for the SCG. conditional reconfiguration Including the target PSCell condRRCReconfig (conditions) RRC reconfiguration) The time elapsed between them.

[0037] In a specific implementation, the configuration / arrangement details on the UE side can be specified as follows:

[0038] Step 1: The UE can receive report configuration information from the network. In a particular implementation, the report configuration information may include at least one of the following: • A first instruction, which may instruct the UE to report the time elapsed between initiating a conditional reconfiguration for a target PSCell / PCell and receiving the last conditional reconfiguration for the corresponding / associated target PSCell / PCell. • Threshold information, which can refer to the threshold of the time elapsed between initiating the conditional reconfiguration of the target PSCell / PCell and receiving the last conditional reconfiguration of the associated / corresponding target PSCell / PCell.

[0039] Step 2a: After receiving the first instruction, the UE can report to the network the time elapsed between initiating the conditional reconfiguration for the target PSCell / PCell and receiving the final conditional reconfiguration for the associated / corresponding target PSCell / PCell.

[0040] Step 2b: After receiving the threshold information, if the time elapsed between initiating the conditional reconfiguration of the target PSCell / PCell and receiving the last conditional reconfiguration of the corresponding / associated target PSCell / PCell is greater than the threshold, the UE can report the time elapsed between initiating the conditional reconfiguration of the target PSCell / PCell and receiving the last conditional reconfiguration of the corresponding / associated target PSCell / PCell to the network.

[0041] In a particular implementation, the UE can send / transmit a reason for a report to the network. This reason can be used to indicate / specify the cause of the report. If the UE sends the time elapsed between initiating a conditional reconfiguration for a target PSCell / PCell and receiving the last conditional reconfiguration for the associated / corresponding target PSCell / PCell, the reason value can be set as an indication of a conditional reconfiguration problem.

[0042] In a particular implementation, the network-side configuration / layout details can be specified as follows:

[0043] Step 1: The network can send report configuration information to the UE. In a particular implementation, the report configuration information may include at least one of the following: • A first instruction, which may instruct the UE to report the time elapsed between initiating a conditional reconfiguration for a target PSCell / PCell and receiving the last conditional reconfiguration for the corresponding / associated target PSCell / PCell. • Threshold information, which can refer to the threshold of the time elapsed between initiating the conditional reconfiguration of the target PSCell / PCell and receiving the last conditional reconfiguration of the associated / corresponding target PSCell / PCell.

[0044] Step 2: The network receives information about the time elapsed between initiating a conditional reconfiguration of the target PSCell / PCell from the network and receiving the last conditional reconfiguration of the associated / corresponding target PSCell / PCell.

[0045] Step 3: The network can optimize conditional reconfiguration based on this report. For example, by changing the candidate cell list and / or the execution conditions of the conditional reconfiguration. In some implementations, if the conditional reconfiguration is provided by another network, the network can forward the report to that other network node.

[0046] In certain implementations, to notify the network of the applicability of the provided CPAC configuration, the network may instruct / indicate / instruct the UE to report the elapsed time between initiating a conditional reconfiguration for a target PSCell and receiving the last conditional reconfiguration for the associated / corresponding target PSCell. In some implementations, this time may be set as follows: TimeSinceCPAC-Reconfig-r18 ::= INTEGER (0.. 1023)

[0047] In certain implementations, if the reported time is 1023, it may mean / indicate that the UE has not performed any CPAC configuration. In some implementations, this configuration / arrangement may be useful for CPAC configuration but may be ineffective for subsequent CPAC situations. In certain implementations, the UE may maintain / retain subsequent CPAC configurations for (one or more) candidate PSCells as pre-configured. In certain implementations, the UE may receive one subsequent CPAC configuration from the network but may perform / execute subsequent CPAC configurations multiple times.

[0048] In certain implementations, after a UE performs / executes subsequent CPACs multiple times, the time elapsed between initiating a conditional reconfiguration for a target PSCell and receiving the final conditional reconfiguration for the associated / corresponding target PSCell may be significantly prolonged. Therefore, the network may be unable to determine / know whether the UE has not performed / executed any subsequent CPACs, or whether the UE has performed subsequent CPACs multiple times, based on the reported time.

[0049] In a specific implementation / example, the UE can report whether a CPAC or subsequent CPAC instruction was performed after obtaining the last conditional reconfiguration for the target PSCell. In a specific implementation, the configuration / arrangement details can be specified as follows: Step 1: The UE can receive signals from the network. UEInformationRequest information. Step 2: The UE can report whether CPAC or subsequent CPAC instructions were executed after obtaining the last conditional reconfiguration for the target PSCell.

[0050] In a specific implementation / example, the UE can report the number of times CPAC or subsequent CPACs were performed after the last conditional reconfiguration was obtained. In a specific implementation, the configuration / arrangement details can be specified as follows: Step 1: The UE can receive signals from the network. UEInformationRequest information. Step 2: The UE can report the number of times CPAC or subsequent CPACs were executed after the last conditional reconfiguration was obtained.

[0051] In a specific implementation / example, the configuration / arrangement details can be specified as follows: Step 1: The UE can receive signals from the network. UEInformationRequest information. Step 2: The UE can UEInformationResponse The counter for subsequent CPACs in the message is set to Var- Report The value of the counter for subsequent CPAC. Step 3: Upon successful delivery confirmed by the lower level UEInformationResponse When a message is received, the UE can discard it. Var-Report .

[0052] Additionally, the UE can be configured before step 2. Var-Report The subsequent CPAC counters are as follows: 1) When performing conditional reconfiguration for subsequent CPACs, the UE can... Var-Report The counter for subsequent CPACs is incremented by 1. 2) If the conditional reconfiguration for subsequent CPAC is changed or released, the UE can... Var-Report The counter for subsequent CPACs is reset to 0.

[0053] In a specific implementation / example, the configuration / arrangement details can be specified as follows: Step 1: The UE can receive signals from the network. UEInformationRequest information. Step 2: For the final application RRCReconfiguration The UE can use the PSCell indicated in the message. UEInformationResponse The message sets the counter for subsequent CPACs for this cell to [value]. Var-Report The value of the counter for the subsequent CPAC of the corresponding / associated cell. In a particular implementation, the UE may maintain a counter for the subsequent CPAC for each cell (e.g., cells in the candidate cell list).

[0054] Additionally, the UE can be configured before step 2 or step 1. Var-Report The counters for subsequent CPACs associated with the cell are as follows: 1) When performing conditional reconfiguration of subsequent CPACs for the selected cell, the UE can... Var-Report The counter for subsequent CPACs of the selected cell is incremented by 1. 2) If the conditional reconfiguration associated with the cell for subsequent CPAC is changed or released, the UE can... Var- Report The counter for subsequent CPACs of this PSCell is reset to 0.

[0055] In a specific implementation / example, the UE can report the elapsed time between the last two conditional reconfigurations. Configuration / arrangement details can be specified as follows: Step 1: The UE can receive signals from the network. UEInformationRequest information. Step 2: The UE can UEInformationResponse The time elapsed between the last two conditional reconfigurations in the message is set to... Var-Report The first time value in the data.

[0056] Additionally, the UE can be configured before step 2 or step 1. Var-Report The first timer in the system is as follows: 1) When performing conditional reconfiguration for subsequent CPACs, the UE can stop the first timer and set its value to [value missing]. Var-Report The first time value in the time frame. In a particular implementation, the UE can restart the first timer or reset the first timer to 0. 2) If the conditional reconfiguration for subsequent CPAC is changed or released, the UE can restart the first timer or reset the first timer to 0.

[0057] In certain implementations / exemplifications, subsequent CPAC configuration may involve multiple network nodes, and more than one network node may be involved in providing subsequent CPAC configuration information. In some implementations, the UE may report all selected subsequent CPAC candidate configurations to the network. Configuration details may be specified as follows: Step 1: The UE can receive signals from the network. UEInformationRequest Message. In a particular implementation, UEInformationRequest The message may include instructions to report subsequent CPAC-related information. Step 2: The UE can... UEInformationResponse The selected subsequent CPAC candidate configuration is sent in the message.

[0058] In a particular implementation, the selected candidate configuration for subsequent CPAC may include at least one of the following: the selected cell ID for subsequent CPAC execution; the condReconfigId to be executed or selected; and / or the selected candidate configuration for subsequent CPAC is stored in the primary cell group (MCG). VarConditionalReconfig (conditional reconfiguration variable) It may still be stored in SCG VarConditionalReconfig The instructions in the document.

[0059] In a particular implementation, the selected subsequent CPAC candidate configuration may include at least one of the following: all selected cell IDs associated with the subsequent CPAC configuration for subsequent CPAC execution; and / or all selected cell IDs associated with the subsequent CPAC configuration for subsequent CPAC execution. condReconfigId .

[0060] In a specific implementation, when the network obtains the aforementioned information, the network can know / determine the subsequent CPAC execution status and decide whether to modify the subsequent CPAC configuration. In a specific implementation, when the network obtains the information stored in the MCG... VarConditionalReconfig The data may be stored in the secondary cell group (SCG). VarConditionalReconfig When the network receives information about the selected subsequent CPAC configuration, it can know / determine which network node (MN node, SN node, or both MN node and SN node) provided the subsequent CPAC candidate configuration. The network can then forward the received report to that network node.

[0061] In certain implementations / exemplifications, due to the specifics of subsequent CPACs, it is conceivable that the SCG (possibly in FR2) will automatically change from one candidate SCG to another within a set of candidate SCGs, while the MCG remains unchanged (in lower frequency bands, such as 3.5 GHz or even 700 MHz). It is advantageous for the network to configure one SCG pool for a UE and for everything else to be automated. For subsequent CPACs, the UE may frequently change its SCG. If subsequent CPACs are configured for the UE, various reports may need to be generated more frequently. However, suboptimal success reports or failure reports may be overwritten. If subsequent CPACs continue and the network fails to obtain reports in a timely manner, such information may never be known to the network. To avoid this problem, the UE should retain information in suboptimal success reports or failure reports until the lower layer confirms successful delivery of the information. In certain implementations / exemplifications, when the UE is configured to provide SPR information or failure information, the UE may not clear the currently stored SPR information or failure information; instead, the UE will add new SPR information or failure information to the report. In certain implementations / exemplifications, when information is successfully delivered to the network, the UE will clear or discard the SPR information or failure information.

[0062] In certain implementations / exemplifications, the network may wish to know the UE's mobility trajectory for subsequent CPACs. For example, the network can use the UE's mobility history information for subsequent CPACs to better configure future UEs (different UEs with similar mobility trajectories based on location information) or as input for future network automation / prediction. In certain implementations / exemplifications, when the UE receives a report request from the network, the UE can report to the network one or more PSCells in the selected / service sequence. Furthermore, it can also report to the network the dwell time in each selected / service PSCell.

[0063] Now refer to Figure 3 , Figure 3 A flowchart of a method 300 for performing redundant side-link communication is shown. This can be achieved by combining... Figure 1 and Figure 2Any components and devices detailed herein shall implement method 300. In summary, method 300 may include a wireless communication device receiving report configuration information from a network (step 302). The method may include the wireless communication device sending a report to the network based on the report configuration information regarding a subsequent Conditional PSCell Addition or Change (CPAC) or a subsequent CPAC (step 304). The method may include the network sending the report configuration information to the wireless communication device (step 306). The method may include the network receiving a report from the wireless communication device based on the report configuration information regarding a subsequent Conditional PSCell Addition or Change (CPAC) or a subsequent CPAC (step 308).

[0064] In a specific configuration, the wireless communication device (e.g., UE) can receive / obtain / retrieve report configuration information from the network (step 302). The wireless communication device can send / transmit / provide to the network a report based on the report configuration information regarding subsequent Conditional PSCell Addition or Change (CPAC) or subsequent CPAC (step 304). In a specific configuration, the report configuration information may include at least one of the following: a first indication or threshold information.

[0065] In a specific configuration, the first indication may instruct the wireless communication device to report the amount of time elapsed between initiating a conditional reconfiguration for a target PSCell / PCell and receiving the final conditional reconfiguration for that target PSCell / PCell. In a specific configuration, threshold information may indicate a threshold value representing the time elapsed between initiating a conditional reconfiguration for a target PSCell / PCell and receiving the final conditional reconfiguration for that target PSCell / PCell. In a specific configuration, the report may include the amount of elapsed time. In a specific configuration, the wireless communication device may send the reason for the conditional reconfiguration problem to the network.

[0066] In a specific configuration, the wireless communication device may receive a message from the network including a report request. In some implementations, in response to the report request, the report may include at least one of the following: an indication of whether a CPAC or subsequent CPAC was performed after the last conditional reconfiguration for the target PSCell was acquired; the number of times a CPAC or subsequent CPAC was performed after the last conditional reconfiguration was acquired; a counter for subsequent CPACs; a counter for subsequent CPACs for each cell; the amount of time elapsed between the last two conditional reconfigurations; and / or a selected candidate configuration for subsequent CPACs.

[0067] In a specific configuration, the counter for a subsequent CPAC may include at least one of the following: when a conditional reconfiguration for a subsequent CPAC is performed, the wireless communication device may increment the counter by 1; and / or if the conditional reconfiguration for a subsequent CPAC is changed or released, the wireless communication device may reset the counter for the subsequent CPAC to 0. In a specific configuration, the counter for a subsequent CPAC for each cell may include at least one of the following: when a conditional reconfiguration for a subsequent CPAC for a selected cell is performed, the wireless communication device may increment the counter for the subsequent CPAC for that selected cell by 1; and / or if the conditional reconfiguration for a subsequent CPAC associated with a cell is changed or released, the wireless communication device may reset the counter for the subsequent CPAC for that cell to 0. In some implementations, the selected cell may be a source cell or a candidate target cell for the subsequent CPAC.

[0068] In a particular configuration, the amount of time elapsed between the last two conditional reconfigurations may include at least one of the following: when a conditional reconfiguration for a subsequent CPAC is performed, the wireless communication device may stop a first timer and set the value of the first timer to a first time value; and / or if a conditional reconfiguration for a subsequent CPAC is changed or released, the wireless communication device may restart the first timer or reset the first timer to 0.

[0069] In a specific configuration, the selected candidate configuration for subsequent CPAC may include at least one of the following: the selected cell ID for performing subsequent CPAC; the cell ID being performed or selected. condReconfigId ; and / or stored in MCG VarConditionalReconfig It may be stored in SCG VarConditionalReconfig The selected candidate configuration is indicated. In a specific configuration, the selected candidate configuration for subsequent CPAC may include at least one of the following: all selected cell IDs for performing the subsequent CPAC and the associated subsequent CPAC configuration; and / or all selected cell IDs for performing the subsequent CPAC. condReconfigId The subsequent CPAC configuration associated with this subsequent CPAC. In a specific configuration, the selected cell IDs can be listed in the execution order. In a specific configuration, the selected... condReconfigId They can be listed in the order of execution.

[0070] At least one aspect relates to a system, method, apparatus, or computer-readable medium. In a particular configuration, the network can send / transmit / provide report configuration information to a wireless communication device (step 306). In a particular configuration, the network can receive / obtain / retrieve from the wireless communication device a report based on the report configuration information regarding subsequent Conditional PSCell Addition or Change (CPAC) or subsequent CPAC (step 308).

[0071] While various embodiments / implementations of this solution have been described above, it should be understood that these embodiments are presented by way of example only and not by way of limitation. Similarly, various schematic diagrams may depict exemplary architectures or configurations, which are provided to enable those skilled in the art to understand exemplary features and functions of this solution. However, those skilled in the art will understand that the solution is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment / implementation herein may be combined with one or more features of another embodiment / implementation described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0072] It should also be understood that any references to elements in this document using names such as "first," "second," etc., generally do not restrict the number or order of these elements. Rather, these names may be used in this document as a convenient means of distinguishing two or more elements, or multiple instances of a single element. Therefore, a reference to the first element and the second element does not imply that only two elements can be used, or that the first element must somehow precede the second element.

[0073] Furthermore, those skilled in the art will understand that various techniques and skills can be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols that may be mentioned in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0074] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate the interchangeability of hardware, firmware, and software, the various exemplary components, blocks, modules, circuits, and steps described above are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation will not depart from the scope of this disclosure.

[0075] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or any other suitable configuration that performs the functions described herein.

[0076] If these functions are implemented in software, they can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, with the latter including any medium capable of transferring a computer program or code from one location to another. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and that is accessible to a computer.

[0077] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the relevant functions described herein. Furthermore, for purposes of discussion, individual modules are described as discrete modules; however, as will be apparent to those skilled in the art, two or more modules can be combined to form a single module that performs the relevant functions according to embodiments of the present solution.

[0078] Furthermore, memory or other storage devices, as well as communication components, may be used in embodiments of this solution. It should be understood that, for clarity, the above description refers to embodiments of this solution described with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains can be used without impairing this solution. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functions and do not indicate a strict logical or physical structure or organization.

[0079] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is given the broadest scope consistent with the novel features and principles disclosed herein as set forth in the following claims.

Claims

1. A wireless communication method, comprising: The wireless communication device receives report configuration information from the network; as well as The wireless communication device sends a report to the network based on the report configuration information regarding subsequent conditional PSCell additions or changes (CPACs) or subsequent CPACs.

2. The wireless communication method according to claim 1, wherein, The report configuration information includes at least one of the following: a first indication or threshold information.

3. The wireless communication method according to claim 2, wherein, The first indication is used to instruct the wireless communication device to report the amount of time elapsed between initiating a conditional reconfiguration for the target PSCell / PCell and receiving the final conditional reconfiguration for the target PSCell / PCell.

4. The wireless communication method according to claim 2, wherein, The threshold information indicates the threshold of the time elapsed between initiating a conditional reconfiguration of the target PSCell / PCell and receiving the last conditional reconfiguration of the target PSCell / PCell.

5. The wireless communication method according to claim 3, wherein, The report includes the amount of time that has elapsed.

6. The wireless communication method according to claim 3 or 4, further comprising: The reason for the problem of the conditional reconfiguration being sent from the wireless communication device to the network.

7. The wireless communication method according to claim 1, further comprising: The wireless communication device receives a message from the network including a report request; In response to the report request, the report includes at least one of the following: After obtaining the last conditional reconfiguration for the target PSCell, was the instruction of the CPAC or the subsequent CPAC executed? The number of times the CPAC or subsequent CPAC is executed after the last conditional reconfiguration is obtained; The counter for the subsequent CPAC; The counter for the subsequent CPAC for each cell; The amount of time elapsed between the last two conditional reconfigurations; or The selected candidate configuration for the subsequent CPAC.

8. The wireless communication method according to claim 7, wherein, The counter for the subsequent CPAC includes at least one of the following: When a conditional reconfiguration for the subsequent CPAC is performed, the wireless communication device increments the counter for the subsequent CPAC by 1; or If the conditional reconfiguration for the subsequent CPAC is changed or released, the wireless communication device resets the counter for the subsequent CPAC to 0.

9. The wireless communication method according to claim 7, wherein, The counters for subsequent CPACs for each cell include at least one of the following: When a conditional reconfiguration of a subsequent CPAC for the selected cell is performed, the wireless communication device increments the counter for the subsequent CPAC of the selected cell by 1; or If the conditional reconfiguration associated with the cell for the subsequent CPAC is changed or released, the wireless communication device will reset the counter for the subsequent CPAC of the cell to 0. The selected cell can be a source cell or a candidate target cell for the subsequent CPAC.

10. The wireless communication method according to claim 7, wherein, The elapsed time between the last two conditional reconfigurations includes at least one of the following: When the conditional reconfiguration for the subsequent CPAC is executed, the wireless communication device stops the first timer and sets the value of the first timer to a first time value; or If the conditional reconfiguration for the subsequent CPAC is changed or released, the wireless communication device restarts the first timer or resets the first timer to 0.

11. The wireless communication method according to claim 7, wherein, The selected candidate configurations used for the subsequent CPAC include at least one of the following: The selected cell ID used to perform the subsequent CPAC; Executed or selected condReconfigId ;or Stored in MCG VarConditionalReconfig It may be stored in SCG VarConditionalReconfig The indication of the selected candidate configuration.

12. The wireless communication method according to claim 7, wherein, The selected candidate configurations for the subsequent CPAC include at least one of the following: The subsequent CPAC configuration used to execute the subsequent CPAC for all selected cell IDs and the associated subsequent CPAC; or All selected for executing the subsequent CPAC condReconfigId The subsequent CPAC configuration associated with the subsequent CPAC.

13. The wireless communication method according to claim 12, wherein, The selected cell IDs are listed in the order of execution.

14. The wireless communication method according to claim 12, wherein, The selected condReconfigId Listed in the order of execution.

15. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 14.

16. A computer program product comprising a computer-readable program medium on which code is stored, the code causing the processor to perform the method according to any one of claims 1 to 14 when executed by a processor.

Images