Device, method and computer readable medium for communications
By incorporating duplex-specific indications in UEInformationResponse and dedicated resource configurations, the solution addresses inefficiencies in SON/MDT procedures, enhancing power control and random access success in DC environments.
Patent Information
- Application Number
- PCT/CN2025/095512
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-16
- Publication Date
- 2026-11-19
AI Technical Summary
Existing technologies do not adequately consider duplex operation characteristics in self-organization network (SON) and minimized drive-test (MDT) procedures, leading to inefficient power control and random access failures in dual connectivity (DC) scenarios.
Enhanced UEInformationResponse message to include duplex-specific indications for random access attempt failures, and dedicated resource configurations for secondary cell addition in DC to facilitate targeted power control and resource allocation.
Improves network parameter adjustment efficiency and random access success rates by accurately identifying and addressing duplex operation-related failures, preventing unnecessary adjustments to non-duplex parameters.
Smart Images

Figure CN2025095512_19112026_PF_FP_ABST
Abstract
Description
DEVICE, METHOD AND COMPUTER READABLE MEDIUM FOR COMMUNICATIONSFIELD
[0001] Embodiments of the present disclosure generally relate to the field of communication, and in particular, to devices, methods and computer readable medium for dual connectivity (DC) with a duplex operation.BACKGROUND
[0002] To enhance the frequency spectrum efficiency and uplink coverage, a subband non-overlapping full duplex (SBFD) operation was proposed on the basis of time division duplexing (TDD) pattern. In SBFD operations, a time unit (for example, a symbol, slot, sub-frame, frame, and so on) , which may be also referred to as an SBFD time unit, can be divided into a plurality of frequency subbands in the frequency domain. The plurality of frequency subbands may be respectively used for different link directions, for example, uplink (UL) frequency subband or downlink (DL) frequency subband. That is, for example, on a DL symbol configured as an SBFD symbol, the network device may perform the DL transmission on the DL subband and perform the UL reception on the configured UL subband during this DL symbol.
[0003] Self-organization network (SON) enables wireless networks to automatically manage tasks like configuration, optimization, and healing (e.g., self-configuration of new nodes, automatic neighbor relation management) to reduce human intervention and operational costs. Minimized Drive-Test (MDT) utilizes user equipment (UE) to collect network performance data (e.g., signal strength, interference levels) during normal usage, replacing traditional manual drive tests to efficiently monitor and optimize network coverage with reduced cost and improved scalability. DC refers to a technology where a user equipment (UE) is simultaneously connected to two different access nodes (e.g., network devices) in a wireless network. This approach enhances network reliability, improves data throughput, and enables seamless mobility by utilizing resources from both nodes to support the UE's communication needs. During the DC mode, the UE needs to consider allocating power for different cells (or cell groups) for the DC.SUMMARY
[0004] In general, example embodiments of the present disclosure relate to devices, methods, and computer readable medium for the dual-connectivity (DC) with duplex operation.
[0005] In a first aspect, there is provided a terminal device. The terminal device comprises a processor. The processor is configured to cause the terminal device to determine that one or more random access attempts on a resource related to duplex operation have failed. The terminal device is further caused to transmit, to a network device, information response comprising an indication that indicates a failure of a random access attempt related to the duplex operation.
[0006] In a second aspect, there is provided a network device. The network device comprises a processor. The processor is configured to cause the network device to receive, from a terminal device, information response comprising an indication that indicates a failure of random access attempt related to the duplex operation.
[0007] In a third aspect, there is provided a terminal device. The terminal device comprises a processor. The processor is configured to cause the terminal device to receive, from a first network device, a configuration comprising a first set of resources for random access. The first set of resources is related to a duplex operation. The terminal device is further caused to perform a random access to a second network device based on the configuration.
[0008] In a fourth aspect, there is provided a first network device. The first network device comprises a processor. The processor is configured to cause the first network device to transmit, to a second network device, a secondary cell addition request. The first network device is further caused to receive, from the second network device, an addition request acknowledge message comprising a first set of resources for random access. The first set of resources is related to a duplex operation. The first network device is further caused to transmit, a terminal device, a configuration comprising the first set of resources.
[0009] In a fifth aspect, there is provided a second network device. The second network device comprises a processor. The processor is configured to cause the second network device to receive, from a first network device, a secondary cell addition request. The second network device is further caused to transmit, to the first network device, an addition request acknowledge message comprising a first set of resources for random access. The first set of resources is related to a duplex operation.
[0010] In a sixth aspect, there is provided a terminal device. The terminal device comprises a processor. The processor is configured to cause the terminal device to transmit, to a network device, an indication related to a capability of dynamic power sharing for dual connectivity (DC) . A secondary cell associated with the DC enables a sub-band full duplex (SBFD) operation. The terminal device is further caused to reduce transmission power for a main cell associated with the DC based on the indication that indicates the capability of dynamic power sharing.
[0011] In a seventh aspect, there is provided a method implemented at a terminal device. In the method, the terminal device determines that one or more random access attempts on a resource related to duplex operation have failed. Then, the terminal device transmits, to a network device, information response comprising an indication that indicates a failure of a random access attempt related to the duplex operation.
[0012] In an eighth aspect, there is provided a method implemented at a network device. In the method, the network device receives, from a terminal device, information response comprising an indication that indicates a failure of random access attempt related to the duplex operation.
[0013] In a ninth aspect, there is provided a method implemented at a terminal device. In the method, the terminal device receives, from a first network device, a configuration comprising a first set of resources for random access. The first set of resources is related to a duplex operation. Then, the terminal device performs a random access to a second network device based on the configuration.
[0014] In a tenth aspect, there is provided a method implemented at a first network device. In the method, the first network device transmits, to a second network device, a secondary cell addition request. The first network device receives, from the second network device, an addition request acknowledge message comprising a first set of resources for random access. The first set of resources is related to a duplex operation. Then, the first network device transmits, a terminal device, a configuration comprising the first set of resources.
[0015] In an eleventh aspect, there is provided a method implemented at a second network device. In the method, the second network device receives, from a first network device, a secondary cell addition request. Then, the second network device transmits, to the first network device, an addition request acknowledge message comprising a first set of resources for random access. The first set of resources is related to a duplex operation.
[0016] In a twelfth aspect, there is provided a method implemented at a terminal device. In the method, the terminal device transmits, to a network device, an indication related to a capability of dynamic power sharing for dual connectivity (DC) . A secondary cell associated with the DC enables a sub-band full duplex (SBFD) operation. Then, the terminal device reduces transmission power for a main cell associated with the DC based on the indication that indicates the capability of dynamic power sharing.
[0017] In a thirteenth aspect, there is provided a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method of any of the seventh aspect to the twelfth aspect.
[0018] It is to be understood that the summary section is not intended to identify key or essential features of example embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Some example embodiments will now be described with reference to the accompanying drawings, where:
[0020] FIG. 1 illustrates an example environment in which some embodiments of the present disclosure can be implemented;
[0021] FIG. 2 illustrates an example signaling process for reporting information response related to duplex operation according to some embodiments of the present disclosure;
[0022] FIG. 3 illustrates an example signaling process for the addition of a secondary cell (group) enabling duplex operation according to some embodiments of the present disclosure;
[0023] FIG. 4 illustrates a specific example of the addition of a secondary cell (group) enabling duplex operation according to some embodiments of the present disclosure;
[0024] FIG. 5 illustrates a flowchart of an example method for allocating power in the DC mode with duplex operation according to some embodiments of the present disclosure;
[0025] FIG. 6 illustrates a flowchart of an example method implemented at a terminal device according to some embodiments of the present disclosure;
[0026] FIG. 7 illustrates a flowchart of an example method implemented at a network device according to some embodiments of the present disclosure;
[0027] FIG. 8 illustrates a flowchart of an example method implemented at a terminal device according to some embodiments of the present disclosure;
[0028] FIG. 9 illustrates a flowchart of an example method implemented at a first network device according to some embodiments of the present disclosure;
[0029] FIG. 10 illustrates a flowchart of an example method implemented at a second network device according to some embodiments of the present disclosure;
[0030] FIG. 11 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure.
[0031] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0032] Principle of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitations as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.
[0033] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0034] As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure / network, devices for Integrated Access and Backhaul (IAB) , Small Data Transmission (SDT) , mobility, Multicast and Broadcast Services (MBS) , positioning, dynamic / flexible duplex in commercial networks, reduced capability (RedCap) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast / broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may be also incorporated one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal, a wireless device or a reduced capability terminal device.
[0035] As used herein, the term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , Network-controlled Repeaters, and the like.
[0036] The terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information. The terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz –7125 MHz) , FR2 (24.25 GHz to 71 GHz) , 71 GHz to 114 GHz, and frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed / unlicensed / shared spectrum. The terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
[0037] The network device may have the function of network energy saving, Self-Organizing Networks (SON) / Minimization of Drive Tests (MDT) . The terminal may have the function of power saving.
[0038] The embodiments of the present disclosure may be performed in test equipment, e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
[0039] The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
[0040] In one embodiment, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs) . In one embodiment, the first network device may be a first RAT device and the second network device may be a second RAT device. In one embodiment, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device. In one embodiment, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In one embodiment, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
[0041] As used herein, the singular forms ‘a’ , ‘an’a nd ‘the’a re intended to include the plural forms as well, unless the context clearly indicates otherwise. The term ‘includes’a nd its variants are to be read as open terms that mean ‘includes, but is not limited to. ’ The term ‘based on’ is to be read as ‘at least in part based on. ’ The term ‘one embodiment’a nd ‘an embodiment’a re to be read as ‘at least one embodiment. ’ The term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’ The terms ‘first, ’ ‘second, ’a nd the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
[0042] In some examples, values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
[0043] The term “circuitry” used herein may refer to hardware circuits and / or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and / or digital hardware circuits with software / firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software / firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and / or firmware. In this disclosure, the subband and the frequency subband may be used interchangeable without any limitation. The group size of a RBG may be also referred to as the RBG size without any limitation. In this disclosure, the control channel may be interchangeably used with the physical downlink control channel (PDCCH) without any limitation.
[0044] In some example embodiments of the disclosure, the slot / symbol configured with SBFD communication or configuration may be also referred to as SBFD slot / symbol, and the slot / symbol not configured with SBFD communication may be also referred to as non-SBFD slot / symbol. The non-SBFD time unit may include UL slot / symbol and / or DL slot / symbol. Only for discussion simplicity, the SBFD time unit may be also referred to as the “full duplex time unit” in some example embodiments of the disclosure.
[0045] In some example embodiments of the disclosure, the term “SBFD slot” refers to a slot including at least one SBFD symbol which is configured with frequency subbands for different link directions. In addition to the at least one SBFD symbol, the SBFD slot may further include one or more non-SBFD symbols, such as DL symbols, UL symbols and / or flexible symbols.
[0046] Moreover, based on the basic concept of SBFD, the overlapped subband full duplex (OSFD) time unit is further studied. In the OSFD, there is a certain overlap in both of the time and frequency of the frequency subband (which may be also referred to as OSFD frequency subband or flexible frequency subband) used for transmission and reception. This design aims to further optimize the utilization of spectrum resources and communication performance.
[0047] In some example embodiments of the disclosure, the terms “full duplex slot” and “subband full duplex slot” can be used interchangeably. In some example embodiments of the disclosure, the full duplex slot includes non-overlapping subband full duplex (SBFD) slot and overlapped subband full duplex (OSFD) slot.
[0048] In some example embodiments of the disclosure, the “duplex operation” may be performed in the SBFD time unit or OSFD time unit without any limitation. For example, the duplex operation includes that the network device transmits DL transmission and receive UL transmission during the SBFD time unit or OSFD time unit, simultaneously.
[0049] In some example embodiments of the disclosure, the time unit may be any metric of the time domain. For example, the time unit may be a frame, a subframe, a slot, or a symbol. Without any limitation, the time unit may be any other time duration.
[0050] In some example embodiments of the disclosure, the expression “frequency resources within a subband of the SBFD time unit” only refers to the resources located within the subband with respect to the frequency domain; however, the time duration of the resources is unnecessary to be limited in one or more SBFD time units if the time duration is not indicated.
[0051] As mentioned above, before introducing the duplex operation, self-organization network (SON) , minimized Drive-Test (MDT) and dual connectivity (DC) technologies had been discussed or adopted to enhance the network configuration efficiency, throughout and robust. However, the duplex operation characteristics are not considered in the procedures related to these adopted technologies.
[0052] Taking the SON / MDT as an example, the UE may transmit information response message (e.g., “UEInformationResponse-information element, IE” ) for reporting, e.g., a measurement report, connection status details and / or device-specific capabilities, to the network. Then, the network may optimize handovers, troubleshoot issues, and adapt resource allocation dynamically. However, there is no detailed field related to the duplex operation.
[0053] As an example, it has been agreed that when the UE tries to random access with duplex resources and falls back to non-duplex resources, the power ramping counter will still be increased. As such, there may be a case where the UE performs several random access attempts on the duplex operation resource (e.g., random access occasion, RO, associated with SBFD or OSFD slot) to a network device, but fails. Then, the UE may perform the random access attempt on the non-duplex operation resource (e.g., RO associated with the UL slot) , and succeed. In this case, the transmitted information response message only includes the power ramping counter value, but does not reflect the details of the failed random access attempts. As an example, the possible two situations of the power ramping counter incrementing are listed in Table 1. Table 1
[0054] As shown in the example of Table 1, in a first case, the UE may perform RACH attempts on the duplex resource for twice at first, but fails. Then, the UE may perform third RACH attempt on the non-duplex resource. In this case, the value of power ramping counter may be “three” , and it may be indicated in the information response message. In a second case, the UE may directly perform RACH attempts on the non-duplex resource, until the third time RACH attempt succeeds. In this case, the value of power ramping counter may be also “three” , and it may be indicated in the information response message. That is, from the SON / MDT perspective, the RACH is being completed on the 3rd RACH attempt but the network has no way of knowing if the first two steps are carried out on duplex or non-duplex RACH. If the network is to adjust its parameters, it would adjust the parameters for the non-duplex power control. This will not only unnecessarily change the non-duplex parameters, but also do not fix the issue of the duplex parameters needing to be updated.
[0055] Furthermore, in the addition procedure of the secondary cell (group) for DC and the power allocation related to the DC with duplex operation, the duplex operation characteristics are also not considered.
[0056] In view of these analysis and considerations, a new solution for the DC with duplex operation is proposed in some embodiments of the present disclosure. Specifically, the UE may indicate information related to the RACH attempt failure occurred on the duplex operation resource in the information response.
[0057] In an aspect, a terminal device determines that one or more random access attempts on a resource related to duplex operation have failed. Then, the terminal device transmits, to a network device, information response comprising an indication that indicates a failure of a random access attempt related to the duplex operation.
[0058] In this way, UEInformationResponse can be enhanced by including duplex-specific indications, such as duplex RACH failure fields. This allows the network to accurately identify failures related to duplex operations during random access, enabling correct adjustment of power control parameters for duplex scenarios. By distinguishing between duplex and non-duplex RACH failure causes, it prevents unnecessary changes to non-duplex parameters and facilitates targeted optimization of duplex resource access, thereby improving the efficiency of network parameter adjustment and the success rate of random access in duplex environments.
[0059] Principle and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. FIG. 1 illustrates an example environment 100 in which example embodiments of the present disclosure can be implemented.
[0060] The environment 100, which may be a part of a communication network, comprises a terminal device 110, a (first) network device 120 and a second network device 130. In some embodiments, the communication network may include NTN, NB-IoT and / or eMTC. In some other embodiments, the communication network may include any other possible communication network. It is to be understood that the number of network devices and terminal devices is given only for illustration without suggesting any limitations. The communication network may include any suitable number of network devices and / or terminal devices adapted for implementing embodiments of the present disclosure. Although not shown, it would be appreciated that one or more terminal devices may be located in the environment 100.
[0061] In the example of FIG. 1, the (first) network device 120 may be the network device providing the main cell (group) for the terminal device 110. In some embodiments of the disclosure, the terminal device 110 has already connected to the (first) network device 120 or the main cell (group) . The second network device 130 may be the network device providing the secondary cell (group) . In some embodiments, the secondary cell (group) or the second network device 130 may enable the full duplex operation, e.g., the secondary cell (group) or the second network device 130 may be configured with the SBFD or OSFD configuration. In some embodiments, the terminal device 110 achieve the DC mode via the main cell (group) / (first) network device and the secondary cell (group) / second network device. In some embodiments, the terminal device 110 seeks to access to the secondary cell (group) or the second network device 130.
[0062] It is to be understood that the number of units and other objects in FIG. 1 is provided merely for the purpose of illustration without implying any limitations to the device environment 100. The environment 100 may include any suitable number of functionality units configured to implement example embodiments of the subject disclosure. Although not shown, it would be appreciated that one or more terminal devices may be located in the environment 100. Some embodiments of the disclosure are discussed with reference to FIGS. 2 to 11.
[0063] FIG. 2 illustrates an example signaling process 200 for reporting information response related to duplex operation according to some embodiments of the present disclosure. It would be appreciated that although the signaling process 200 has been described with respect to communication environment of FIG. 1, this signaling process 200 may be likewise applied to other communication environments.
[0064] In the signaling process 200, the terminal device 110 determines (210) that one or more random access attempts on a resource related to duplex operation have failed. In some embodiments, the resource related to the duplex operation may include a random access channel (RACH) resource for a further network device that supports SBFD operation (or OSFD operation) . In the example of FIG. 1, the resource may be the RACH resource provided by the second network device 130 supporting the SBFD operation. For example, the terminal device 110 may perform one or more random access attempts to the second network device 130 on the RACH occasion (RO) configured within the uplink frequency subband of the SBFD slot of the second network device 130. In another example, to perform the one or more random access attempts, the terminal device 110 may transmit a Message 3 (Msg 3) related to the random access procedure within the uplink frequency subband of the SBFD slot of the second network device 130. In other words, the resource may include any resources for the random access attempt to the network device supporting the duplex operation, such as resources for preamble transmission, Msg 2 transmission, Msg 3 transmission and / or Msg 4 transmission.
[0065] However, the one or more of the random access attempts have failed. That is, in this example, the one or more random access attempts for the SBFD-capable network device associated with the dual connectivity (DC) fail. Alternatively, in some embodiments, without any limitation, the one or more random access attempts may be performed for the network device 110. That is, the one or more random access attempts may not be performed in association with the DC mode.
[0066] Then, the terminal device 110 transmits (220) information response 225 including an indication that indicates a failure of random access attempt related to the duplex operation. In some embodiments, the information response 225 may be the “UEInformationResponse IE”. In this case, the indication may be carried in “RA-report” field of the UEInformationResponse IE.
[0067] In this way, the UEInformationResponse IE is enhanced by indicating whether the random access attempt failure is on the duplex operation capable resource. As such, upon receiving (230) the information response 225, the network device 120 may be aware that the random access attempt failure is related to the legacy resource (non-duplex operation-related resource) or duplex operation-related resource. Accordingly, the network device 120 accurately identify failures related to duplex operations during random access, enabling correct adjustment of power control parameters.
[0068] In addition, in some embodiments, the information response 225 may further include an indication of a type of a random access attempt of the one or more random access attempts. The type of random access attempt may include a first type of contention-based random access (CBRA) and a second type of contention-free random access (CFRA) . That is, the information response 225 may indicate the failed random access attempt is CBRA or CFRA. This may help the network determine the access type of failures, in order to adjust the network parameters accordingly.
[0069] In addition or alternatively, in some embodiments, the information response 225 further include a failure reason. As an example, the random access attempt failure may be caused by cross link interference (CLI) . The failure reason may be the CLI. Without any limitation, the failure reason may include any other reason, such as channel quality, spatial link state, and so on.
[0070] As an example, the following information may be added info the “RA-InformationCommon” field: SBFD-failed This field is included when the RA report entry is included because of SBFD and if the SBFD transmission has failed. This field includes a field for failures due to CLI if CLI was determined to be the cause of failure.
[0071] In view of the above, UEInformationResponse can be enhanced by including duplex-specific indications, such as duplex RACH failure fields. By distinguishing between duplex and non-duplex RACH failure causes, it prevents unnecessary changes to non-duplex parameters and facilitates targeted optimization of duplex resource access, thereby improving the efficiency of network parameter adjustment and the success rate of random access in duplex environments.
[0072] As mentioned above, in the addition procedure of the secondary cell (group) for DC and the power allocation related to the DC with duplex operation, the duplex operation characteristics are also not considered.
[0073] A new solution for the DC with duplex operation is proposed in some embodiments of the present disclosure. Specifically, additional information of set of resources dedicated to random access related to duplex operation is configured for the secondary cell addition.
[0074] In another aspect, a terminal device receives from a first network device a configuration including a first set of resources for random access. The first set of resources is related to a duplex operation. Then, the terminal device performs a random access to a second network device based on the configuration, to implement the secondary cell addition supporting the duplex operation.
[0075] In this way, a UE behavior for the secondary node addition procedure considering duplex operation characteristics is defined.
[0076] FIG. 3 illustrates an example signaling process 300 for the addition of a secondary cell (group) enabling duplex operation according to some embodiments of the present disclosure It would be appreciated that although the signaling process 300 has been described with respect to communication environment of FIG. 1, this signaling process 300 may be likewise applied to other communication environments.
[0077] In the signaling process 300, the first network device 120 transmits (310) a secondary cell addition request 315 to the second network device 130. The second network device 130 receives (130) the secondary cell addition request 315. Then, the second network device130 enabling the duplex operation transmits (330) an addition request acknowledge message 335 to the first network device 120, and the addition request acknowledge message 335 includes a first set of resources for random access related to a duplex operation. Alternatively, the information on the first set of resources may be also transmitted separately from the additional request acknowledge message 335.
[0078] In some embodiments, the first set of resources may be for the CFRA attempt associated with the duplex operation towards the second network device 130. For example, the second network device 130 may provide to the first network device 120 the dedicated resources for RACH procedure associated with the duplex operation. The RACH procedure associated with the duplex operation may be that the RACH procedure for performing communication on the SBFD slot or OSFD slot in the future.
[0079] In addition, in some embodiments, the addition request acknowledge message 335 may include an indication of a random access type. The random access type may include a first random access type associated with a duplex operation or a second random access type associated with a non-duplex operation. In this way, if the second network device supports the duplex operation and non-duplex operation, the second network device 130 may indicate a preferred access type to the terminal device. For example, if the second network device 130 determines that the channel condition does not fulfill a requirement for the duplex operation, the second network device 130 may indicate the second random access type.
[0080] In addition, in some embodiments, the addition request acknowledge message 335 may further include a second set of resources for random access, and the second set of resources is related to non-duplex operation. For example, the second set of resources is also for the CFRA attempt to the second network device 130. However, the CFRA attempt on the second set of resources is not for the future duplex operation. In some embodiments, the second set of resources is for the legacy RACH procedure to the second network device 130.
[0081] In addition or alternatively, in some embodiments, the addition request acknowledge message 335 may further include information of a synchronization signal block (SSB) for the second network device 130. In this way, if the terminal device determines that the CBRA attempts on the first set of resources and / or the second set of resources fail, the terminal device may fallback to perform a random access procedure to the second network device 130 based on the information of SSB. In some embodiments, ff the addition request acknowledge message 335 only includes the first set of resources, enabling a simpler UE behavior for secondary node addition procedure that is quicker for access and determination of failure.
[0082] In addition, in some embodiments, the second network device 130 may provide the information related to the timing adjustment and path loss. For example, the second network device 130 may provide a timing adjustment parameter that compensates the synchronized time differences between the first network device 120 and the second network device 130. In an example, the timing adjustment parameter may be calculated after the second network device 130 receive s the secondary addition request 315. In addition, the timing adjustment parameter may be measured from the current cell serving the terminal device 110 (provided by the first network device 120) and the intended cell of the second network device 130.
[0083] In another example, the second network device 130 may provide the measurement of path loss between the first network device 120 and the second network device 130: PLMN-SN b, f, c, where MN represents the first network device, the SN represents the second network device, b represents a bandwidth for the active uplink, f represents a carrier for the DC and c represents a cell for the DC. The measurement may be performed by the second network device 130 and may help the terminal device 110 determine the path loss between the secondary network (or the second network device 130) and the terminal device 110.
[0084] In some embodiments, the measurement of path loss may be used by the terminal device to locate itself with respect to the two network devices 120 and 130. This may allow for the terminal device to calculate the necessary parameters for pathloss estimation between the second network device 130 and the terminal device 110.
[0085] In addition, in some embodiments, the second network device 130 may further provide a set of power control parameters, and the set of power control parameters is specific to the RACH procedure by the terminal device 110 for the duplex operation capable cell. In some embodiments, the set of power control parameters may include: msg3-DeltaPreamble for a UE, preambleReceivedTargetPower, DELTA_PREAMBLE, Max preamble transmission times, and / or PREAMBLE_POWER_RAMPING_STEP. The parameter msg3-DeltaPreamble for a UE represents a power ramping step size from the Msg 1 to Msg 3 of the random access procedure. The parameter DELTA_PREAMBLE represents a power offset related to a preamble format. The parameter Max preamble transmission times represents Max preamble transmission times represents the maximum number of retransmitting the preamble. The parameter PREAMBLE_POWER_RAMPING_STEP represents a power ramping step when retransmitting the same message.
[0086] Similarly, in response to the secondary cell addition request 315, the above timing adjustment parameter, measurement of path loss and power control parameters may be carried in the addition request acknowledge message 335 or may be transmitted separately from the additional request acknowledge message 335.
[0087] Still referring to FIG. 3, the first network device 120 receives (340) the addition request acknowledge message 335 (and possible above information that may be transmitted separately) . Then, the first network device 120 transmits (350) a configuration 355 including the first set of resources to the terminal device 110. In some embodiments, the configuration 355 may include the radio resource control (RRC) connection reconfiguration.
[0088] In some embodiments, the configuration may further include other information which is transmitted from the second network device 130 to the first network device 120 in the addition request acknowledge message 335, or the above information which is transmitted separately from the addition request acknowledge message 335.
[0089] For example, the first configuration 355 may include both duplex and non-duplex resources (e.g., the first set or second set of resources) for the random access procedure of the second network device 130. As mentioned above, in some embodiments, the first set of resources and the second set of resources are dedicated to the CFRA.
[0090] The terminal device 110 receives (360) the first configuration 355 accordingly. Then, when the terminal device is triggered to enter the DC mode, the terminal device 110 performs (370) a random access to the second network device 130 based on the first configuration 355. For example, the terminal device 110 may transmit a RACH preamble on the first set of resources to the second network device 130. In this case, the terminal device 110 may perform duplex operation (e.g., transmitting UL channel on the SBFD time unit) , if the random access procedure succeeds.
[0091] In some embodiments, assuming that the first configuration 355 includes the first set of resources and the second set of resources. The terminal device 110 may select one of them to perform the random access to the second network device 130. For example, the terminal device 110 may perform the random access to the second network device using the first set of resources or the second set of resources based on a predefined rule. As an example, the predefined rule may include at least one of a first priority level of the first set of resources or a second priority level of the second set of resources. In this case, the terminal device 110 may perform the random access procedure (type) with a higher priority level. In addition, there may be a fallback mechanism for the CFRA. For example, if the terminal device 110 determines that the first random access performed using one of the first set of resources or the second set of resources is failed, the terminal device 110 may perform a second random access to the second network device using another one of the first set of resources or the second set of resources. In some embodiments, the predefined rule may be the default behavior at the terminal device side.
[0092] In addition or alternatively, as mentioned above, the addition request acknowledge message 335 may include an indication of a (preferred) random access type. In this case, the terminal device 110 may perform the random access based on the indicated random access type.
[0093] In addition, in some embodiments, if the CFRAs based on both the first set of resources and the second set of resources are determined as failed, the terminal device 110 may fallback to the CBRA procedure. For example, the first configuration 355 may include the information of SSB that is provided by the second network device 140, as mentioned above. The terminal device 110 may perform the random access to the second network device based on measuring the SSBs indicated in the information.
[0094] In addition, in some embodiments, the terminal device 110 may perform the CBRA by determining whether the first configuration 355 includes the timing adjustment or path loss related information. As an example, if the first configuration 355 includes the timing adjustment or path loss related information which is provided by the second network device 130 as mentioned above, the terminal device 110 may perform the CBRA. For example, the terminal device 110 may use the timing adjustment parameter to synchronize with the SN.
[0095] Otherwise, if the first configuration 355 does not include the timing adjustment or path loss related information, the terminal device 110 may determine to perform the CBRA. In an example, if the terminal device 110 requires synchronization directly from SN (e.g., in the case that the above timing adjustment or path loss related information is invalid or is not existed) , the full RACH procedure will be triggered for the terminal device. That is, if the above timing adjustment or path loss related information is not provided, the terminal device 110 may treat this as a preference of the second network device 130 to access through CBRA means and will trigger a RACH process through the SSB resource.
[0096] In addition, the provided timing adjustment or path loss related information may be valid until the terminal device performs a procedure that requires the reading of PSS / SSS of the second network device 130, in which the TA alignment will be based on the SS of the SN instead.
[0097] In addition, the terminal device 110 may further report the failure or success of the random access procedure. In some embodiments, after performing an attempt of the random access 370, the terminal device 110 may transmit a connection reconfiguration complete message indicating the failure or success to the first network device 120. As an example, the connection reconfiguration complete message may be “RRCConnectionReconfigurationComplet” . As an example, the connection reconfiguration complete message may include a first indication indicating that a random access procedure is failed or successful.
[0098] In addition, in some embodiments, if the random access is determined as failed, the first network device 120 may transmit request for measuring a cross link interference (CLI) . Correspondingly, the terminal device 110 may determine whether the failure of the random access procedure is caused by the CLI based on the request. In this case, the connection reconfiguration complete message may further include an indication of a failure reason (which may be also referred to as the third indication) .
[0099] In addition or alternatively, in some embodiments, if the terminal device 110 is unable to use the first configuration 355, the terminal device 110 may perform the corresponding reconfiguration failure procedure and indicates this through the connection reconfiguration complete message.
[0100] In addition or alternatively, in some embodiments, the connection reconfiguration complete message may further include one or more of: a second indication indicating that the random access procedure is related to a duplex operation or non-duplex operation, or a fourth indication indicting that a reconfiguration failure procedure is performed. This may be similar as the information response 225 discussed above.
[0101] In turn, the first network device 120 may further indicate the information included in the connection reconfiguration complete message to the second network device 130. For example, the first network device 120 may transmit, in SgNB reconfiguration complete message, to the second network device 130 the information included in the connection reconfiguration complete message.
[0102] As an specific example of the above embodiments, during the random access procedure, if the terminal device 110 is to begin access on duplex resources but is not able to complete the procedure, the terminal device 110 will attempt to access through non duplex resources.
[0103] If the terminal device 110 is not able to complete the RACH on the indicated duplex resource (i.e., the first set of resources) , the terminal device 110 may transmit to the first network device 120 a connection reconfiguration complete message indicating a failure of the attempted RACH being of a certain RACH type.
[0104] In this case, the terminal device 110 may receive from the network device 120 a CLI measurement request on the associated resource. Then, if the terminal device 110 determines that the failure was due to CLI. This information may be stored and reported in the connection reconfiguration complete message or the information response which will be discussed in the below.
[0105] In addition, for the random access procedure on the first set of resources, the terminal device 110 may be configured with a power ramping counter maximum value that is smaller than the corresponding value for the random access based on the SSB. As mentioned above, the random access procedure on the first set of resources may have a separate power ramping step configuration to account for the smaller values of power ramping counter. The reason for a smaller value of power ramping counter is to allow for the network to reduce the latency while trying to access the duplex networks. If it is apparent that the CLI is too high for access, it can change to a non-duplex resource quicker.
[0106] If the terminal device 110 is able to successfully complete the random access procedure, the connection reconfiguration complete message information may indicate it has been completed. In addition, the terminal device 110 may store the resource information where the RACH was completed upon. This can be duplex resource provided (i.e., the first set of resources) , non-duplex resource provided (i.e., the second set of resources) or SSB resource provided.
[0107] Still referring to FIG. 2, in addition to the connection reconfiguration complete message or alternatively, the terminal device 110 may further transmit the information response message to the first network device and / or second network device. In some embodiments, the information response message may be similar as the information response 225 discussed in FIG. 2. As an example, the information response message may include an indication that indicates a failure of a random access procedure related to the duplex operation or a failure of a random access procedure related to a non-duplex operation. In addition, the information response message may include an indication of a type of a random access procedure and a failure reason (e.g., CLI) . In addition, the information response may further include the resource information where the RACH was completed upon, as mentioned above.
[0108] In some embodiments, the information response may be triggered by the information request from the first network device or the second network device, or the information response is transmitted by the terminal device 110. Some examples are listed as below.
[0109] In an example, the first network device 120 may transmit SgNB Reconfiguration complete message to the second network device that indicates the status of secondary node addition.
[0110] At this time, the first network device 120 may will trigger the information response message. This will allow the first network device 120to understand the reasons for the failure of RACH. The first network device 120 may transmit this information to the second network device 130 afterwards.
[0111] Alternatively, the terminal device 110 may send the information response message through RRC without a trigger indication. This information response message may be transmitted to either the first network device 120 (who will forward the information to the second network device 130) or to the second network device 130 directly.
[0112] Alternatively, after the DC has been completed, the second network device 130 will trigger information response message that it is able to collect the information itself. The second network device 130 does not need to immediately trigger this response. This is used to lower impact on the network.
[0113] FIG. 4 illustrates a specific example of the addition of a secondary cell (group) enabling duplex operation according to some embodiments of the present disclosure. In the example of FIG. 4, UE 110 may be an example of the terminal device 110. the main network (MN) may be an example of the network provided by the first network device 120, and the secondary network (SN) may be an example of the network provided by the second network device 130. Without any limitation, the UE may be also represented by the UE 110, the MN may be also represented by the reference number 120 and the SN may be also represented by the reference number 130.
[0114] As shown in FIG. 4, the first network device 120 may transmit a SgNB addition request 410 to the second network device 130. The SgNB addition request 410 may be the same as the secondary cell addition request 315 in the above. Then, the second network device 130 feeds back the SgNB addition request acknowledge (ACK) 420 to the MN 120 in response to the request 410. In some embodiments, the ACK 420 may be the same as the addition request acknowledge message 335. Then, based on the ACK 420, the first network device 120 transmits RRCConnectionReconfiguration 430 to the terminal device 110. In some embodiments, the RRCConnectionReconfiguration 430 may be the same as the first configuration 355 discussed in FIG. 3. Then, based on the RRCConnectionReconfiguration, UE 110 performs random access procedure 440 with the SN 130. For example, the terminal device may select one of the first set of resources (that is shown as a1. duplex resource) or the second set of resources (that is shown as a2. non-duplex resource) to perform the CFRA. If the CFRA on both the duplex resources and the non-duplex resources is failed, the terminal device may fallback to perform the random access through SSB information.
[0115] Then, the UE 110 may transmit RRCConnectionReconfigurationComplete 450 to the MN 120. In some embodiments, the RRCConnectionReconfigurationComplete 450 may be the connection reconfiguration complete message discussed above. Then, the MN 120 may transmit the SgNB ReconfigurationComplete message to the SN 130. In some embodiments, the SgNB ReconfigurationComplete 460 may be SgNB reconfiguration complete message discussed above.
[0116] In addition, the UE 110 may transmit UEInformationResponse 470 and / or 474 to the MN 120 and / or SN 130. The UEInformationResponse may be the same as the information response message discussed above. For example, the UEInformationResponse may be transmitted directly, or is triggered by the request from the MN 120 or SN 130.
[0117] In view of the above, UE behavior for secondary node addition procedure associated with the duplex operation is defined.
[0118] In addition, as mentioned above, the power allocation related to the DC with duplex operation also does not consider the duplex operation characteristics. In general, the UE is to reduce the power allocation for the secondary cell in the DC mode, or refrain from the transmission to the secondary cell in most cases. However, when the secondary cell (group) enables the duplex operation, the importance of secondary cell (group) relative to the main cell may be re-evaluated. In the DC with duplex operation, the power control for duplex operations may be different from legacy behavior, since separate power control methods can be used for duplex and non-duplex cells.
[0119] For the cell power of DC cells, the duplex open loop power control paired with the existing power control may lead to UL power overload. For legacy behavior where DC is established first on one cell and DC is brought in through second cell, the existence of SBFD cell would mean different power ramping parameters may be used. A major aspect of SBFD is to have increased coverage so the SBFD secondary cell group (SCG) needs to have priority over non-SBFD main cell group (MCG) .
[0120] For example, if there was no need for the secondary cell enabling the duplex operation, the networks will not schedule the communications at the same time. As such, if the secondary cell is needed and the duplex RACH is needed, it means it needs to be done with a higher priority than the access within the main cell. Therefore, there is reason to believe when MCG is non-duplex cell while SCG is duplex cell and the UE is transmitting as an duplex UE, the PRACH of duplex UE is given a higher priority. This also includes the case where the duplex-aware terminal device has attempted to access through the duplex resources but is unsuccessful and has fallen back to transmitting on a non-duplex resource within the SCG.
[0121] In a further aspect, a new solution for allocating power in the DC mode with duplex operation is proposed. Specifically, if the secondary cell (group) in the DC enables the duplex operation, the transmission to the main cell (group) in the DC may be refrained from, or the power allocation to the main cell (group) may be reduced, depending whether the terminal device 110 indicates the dynamic power sharing capability.
[0122] In this way, the power calculation requirements for the duplex operations in DC is changed.
[0123] FIG. 5 illustrates a flowchart 500 of an example method for allocating power in the DC mode with duplex operation according to some embodiments of the present disclosure. It would be appreciated that although the signaling process 200 has been described with respect to communication environment of FIG. 1, this signaling process 200 may be likewise applied to other communication environments.
[0124] In the flowchart 500, at 510, the terminal device 110 transmits an indication related to a capability of dynamic power sharing for dual connectivity (DC) . In some embodiments, the terminal device 110 may indicate capability of dynamic power sharing between main cell (group) and secondary cell (group) for the DC. As an example, the indication may indicate the capability of dynamic power sharing. Alternatively, in some embodiments, the terminal device 110 does not indicate the capability. As an example, the indication may not indicate the capability, or indicate the terminal device does not support the capability.
[0125] In some cases, as mentioned above, when the SCG for the DC is in duplex open loop power control and the MCG for the DC is in close loop power control, the adaptations need to be made to the two cells to enable power control parameters are meet.
[0126] In some embodiments, if the terminal device 110 does not indicate the capability for dynamic power sharing between MCG (e.g., for NR) and SCG (e.g., the next generation of the communication) . The terminal device 110 may refrain from a transmission to the main cell using a first resource. In turn, the terminal device 110 may perform a further transmission to the secondary cell using the first resource. As an example, for the terminal device that do not indicate a capability for dynamic power sharing between NR and 6GR, the open loop power controlled (OLPC) transmission will take priority over close loop power controlled (CLPC) parameters. The terminal device 110 may not transmit on the MCG subframe that is scheduled to have transmissions that are CLPC.
[0127] Alternatively, in some embodiments, if the terminal device 110 indicates the capability of dynamic power sharing. The terminal device 110 may reduce transmission power for a main cell associated with the DC. As an example, the terminal device 110 may reduce the power of a transmission that is using CLPC in MCG, if the transmission is scheduled. In addition, the terminal device 110 may perform the transmission using separate power ramping parameters in the SCG cell (i.e., the secondary cell) with duplex operation.
[0128] In some embodiments, the terminal device 110 may use the maximum transmission power for the secondary cell directly, without power ramping procedure. For example, the terminal device may perform, based on the maximum transmission power, a physical random access channel (PRACH) transmission to the secondary cell at a starting PRACH occasion. Furthermore, the transmission power for the secondary cell may be not updated throughout the complete process.
[0129] In this case, at 520 in FIG. 5, the terminal device 110 may reduce the transmission power allocated to the main cell by only using remaining power of the terminal device 110 for the main cell in addition to the maximum transmission power for the secondary cell.
[0130] In some embodiments, the maximum transmission power may be calculated based on the following equation (1) . PSCG (i2) =min {PCMAX, f, c, PPRACH, targetMAX, f, c+PLMN-SN b, f, c+2×msg3-DeltaPreamble} (1) where PCMAX, f, c represents the UE configured maximum output power, and for carrier f of cell c within transmission occasion i. PPRACH, targetMAX, f, c represents the maximum PRACH target reception power for the active UL bandwidth (BWP) b of carrier f of cell c; and PLMN-SN b, f, c represents a pathloss between the first network device and the second network device for the active UL BWP b of carrier f based on the reference signal on active BWP of cell c.
[0131] In an example, the PPRACH, targetMAX, f, c may be calculated by the following: PPRACH, targetMAX, f, c=preambleReceivedTargetPower (in RRC) + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER_MAX) *PREAMBLE_POWER_RAMPING_STEP - (plus PL) (2) where preambleReceivedTargetPower represents the target received power of the preamble, the DELTA_PREAMBLE represents a power compensation corresponding to a preamble format, PREAMBLE_POWER_RAMPING_COUNTER_MAX represents the maximum value for the power ramping counter dedicated to the duplex operation, PREAMBLE_POWER_RAMPING_STEP represents a step size of one power ramping, and the plus PL represents an path loss value.
[0132] In addition or alternatively, the PPRACH, targetMAX, f, c may be calculated by the following: PPRACH, targetMAX, f, c= max {PPRACH, targetMAXDuplex, f, c, PPRACH, targetMAXnonDuplex, f, c} (3) where PPRACH, targetMAXDuplex, f, c represents the maximum target received power of preamble for the duplex operation, and the PPRACH, targetMAXnonDuplex, f, c represents the maximum target received power of preamble for the non-duplex operation.
[0133] In addition or alternatively, in some embodiments, the transmission power for the SCG may be calculated based on the random access type. In this case, if the information of PLb, f, c is lacking, the terminal device 110 may consider the pathloss based on the PL that was measured by the first network device (or MN) and the second network device (SN) . For example, PLSN-UE b, f, c (i.e., the pathloss between the terminal device and the second network device) may be determined based on the pathloss between the UE and MN, and the pathloss between the MN and SN.
[0134] In this case, the transmission power for the SCG may be calculated by the following: PSCG (i2) =min {PCMAX, f, c (i) , PPRACH, target, f, c (i) +PLSN-UE b, f, c} (4) Then, the terminal device may reduce the transmission power allocated to the main cell by only using remaining power of the terminal device 110 for the main cell in addition to the calculated transmission power for the secondary cell.
[0135] In addition, in some embodiments, the terminal device may determine the PSCG (i2) based on a power ramping step size dedicated to a cell enabling the SBFD operation. For example, the above target received power PPRACH, target, f, c (i) in equation (4) may be calculated as below: PPRACH, target, f, c (i) =PREAMBLE_RECEIVED_TARGET_POWER=preambleReceivedTa rgetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER) *PREAMBLE_POWER_RAMPING_STEP (5)
[0136] In some embodiments, the parameters in equation (5) are provided by the first network device and are used only for the access during DC (e.g., of next generation of the communication-NR) . As such, these parameters are separate from the SSB contained values of these parameters as the UE has not read the SSB of the SN.
[0137] In addition, there may be an “early” offset for calculating the target received power PPRACH, target, f, c (i) (or the transmission power for the SCG) , in order to reserve an extra bit of headroom in case the next transmission is immediate and there is no time to update the values accordingly. In an example, the above target received power PPRACH, target, f, c (i) in equation (4) may be calculated as below: PPRACH, target, f, c (i) =PREAMBLE_RECEIVED_TARGET_POWER=preambleReceivedTarg etPower (in RRC) + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER 2+Noffset) PREAMBLE_POWER_RAMPING_STEP (6) Similarly, the parameters in equation (6) may be provided by the first network device and are used only for the access during DC (e.g., of next generation of the communication-NR) .
[0138] In addition, as mentioned above, an additional parameter “msg3-DeltaPreamble” to dedicated to the indicated access type is allowed. This is used because DC may require different indicated power to offset for the noise environment of duplex. For example, the transmission power for the SCG may be calculated by the following: PSCG (i2) =PreambleReceivedTargetPower + (2 x msg3-DeltaPreamble-DC) (7)
[0139] In a further aspect, when the terminal device is in the DC mode, the power allocation or transmission priority level related to the main cell or secondary cell for the DC mode depends on which one of the main cell or secondary cell is the SBFD cell.
[0140] Specifically, the terminal device transmits, to a network device, an indication related to a capability of dynamic power sharing for dual connectivity (DC) . In response to determining that one of a main cell or secondary cell associated with the DC is or belongs to the SBFD cell, the terminal device reduces the transmission power for the other cell (i.e., the other non-SBFD cell) of the main cell or secondary cell, or refrain from perform a transmission with the other cell if there is also scheduled a transmission for the one cell (i.e., the SBFD cell) on the same resource. Whether to reduce the transmission power or refrain from performing the transmission depends on whether the terminal device indicates the capability of dynamic power sharing, as mentioned above.
[0141] As an example, assuming that the terminal device indicates the capability of dynamic power sharing, and main cell is configured as the SBFD cell. In this case, the terminal device may reduce the transmission power for the secondary cell. The manner of the reducing the transmission power for the secondary cell may be the same as mentioned above, for example, by adopting the maximum transmission power for the SBFD cell at the first RO, using specific power ramping parameter for the SBFD cell, and / or using an “early” offset for the SBFD cell.
[0142] As another example, assuming that the terminal device does not indicate the capability of dynamic power sharing, and main cell is configured as the SBFD cell. In this case, if the same communication resource is scheduled with a first transmission for the main cell (i.e., SBFD cell) and a second transmission for the secondary cell, the terminal device may refrain from performing the second transmission, and perform the first transmission, as similar to the embodiments discussed in FIG. 5.
[0143] The reason is that if there was no need for the duplex cell (e.g., SBFD cell) , the networks will not be scheduling the communications at the same time. As such, if the duplex cell is needed, it means it needs to be done with a higher priority than the other non-SBFD cell.
[0144] In view of the above, optimizing power control in Dual Connectivity for duplex cells, resolving conflicts with traditional methods to enhance uplink coverage and system reliability. This may introduce independent power strategies for duplex and non-duplex cells, preventing uplink power overload and prioritizing duplex PRACH in mixed scenarios.
[0145] FIG. 6 illustrates a flowchart of a method 600 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. The method 600 can be implemented at the terminal device 110 shown in FIG. 1. For the purpose of discussion, the method 600 will be described with reference to FIG. 1. It is to be understood that the method 600 may include additional acts not shown and / or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
[0146] At 610, the terminal device 110 determines that one or more random access attempts on a resource related to duplex operation have failed. At 620, the terminal device 110 transmits, to a network device, information response comprising an indication that indicates a failure of a random access attempt related to the duplex operation.
[0147] In some embodiments, the resource comprises a random access channel (RACH) resource for a further network device which supports a sub-band full duplex (SBFD) operation.
[0148] In some embodiments, the information response further comprises at least one of the following: an indication of a type of a random access attempt of the one or more random access attempts; or a failure reason.
[0149] In some embodiments, the type of random access attempt comprises: a first type of contention-based random access (CBRA) ; and a second type of contention-free random access (CFRA) . In some embodiments, the failure reason comprises a cross link interference (CLI) reason.
[0150] FIG. 7 illustrates a flowchart of a method 700 of communication implemented at a network device in accordance with some embodiments of the present disclosure. The method 700 can be implemented at the network device 120 shown in FIG. 1. For the purpose of discussion, the method 700 will be described with reference to FIG. 1. It is to be understood that the method 700 may include additional acts not shown and / or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
[0151] At 710, the network device 110 receives, from a terminal device, information response comprising an indication that indicates a failure of random access attempt related to the duplex operation.
[0152] In some embodiments, the random access attempt is performed on a random access channel (RACH) resource for a further network device which supports a sub-band full duplex (SBFD) operation.
[0153] In some embodiments, the information response further comprises at least one of the following: an indication of a type of a random access attempt of the one or more random access attempts; or a failure reason.
[0154] In some embodiments, the type of random access attempt comprises: a first type of contention-based random access (CBRA) ; and a second type of contention-free random access (CFRA) . In some embodiments, the failure reason comprises a cross link interference (CLI) reason.
[0155] FIG. 8 illustrates a flowchart of a method 800 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. The method 800 can be implemented at the terminal device 110 shown in FIG. 1. For the purpose of discussion, the method 800 will be described with reference to FIG. 1. It is to be understood that the method 800 may include additional acts not shown and / or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
[0156] At 810, the terminal device 110 receives, from a first network device 120, a configuration comprising a first set of resources for random access. The first set of resources is related to a duplex operation. At 820, the terminal device 110 performs a random access to a second network device 130 based on the configuration.
[0157] In some embodiments, the configuration further comprises the following: a second set of resources for random access, wherein the second set of resource is related to non-duplex operation; and information of a synchronization signal block (SSB) for the second network device.
[0158] In some embodiments, the first set of resources and the second set of resources are configured for contention-free random access (CFRA) .
[0159] In some embodiments, the terminal device may perform the random access by the following: perform the random access to the second network device using the first set of resources or the second set of resources based on a predefined rule. The predefined rule comprises at least one of a first priority level of the first set of resources or a second priority level of the second set of resources.
[0160] In some embodiments, the random access is a first random access, and the terminal device may further: determine that the first random access performed using one of the first set of resources or the second set of resources is failed; and perform a second random access to the second network device using another one of the first set of resources or the second set of resources.
[0161] In some embodiments, the terminal device may further determine that the further random access is failed; and perform a third random access to the second network device based on the information of SSB for the second network device.
[0162] In some embodiments, the terminal device may further transmit, to the first network device, a connection reconfiguration complete message.
[0163] In some embodiments, the connection reconfiguration complete message indicates one or more of the following: a first indication indicating that a random access procedure is failed or successful; a second indication indicating that the random access procedure is related to a duplex operation or non-duplex operation; a third indication of a failure reason; or a fourth indication indicting that a reconfiguration failure procedure is performed.
[0164] In some embodiments, the terminal device may further receive, from the first network device, a request for measuring a cross link interference (CLI) , wherein the request is response to a failure of a random access procedure; and determine whether the failure of the random access procedure is caused by the CLI based on the request.
[0165] In some embodiments, the configuration further comprises an indication of a random access type, and the terminal device may perform the random access by the following: performing the random access based on the random access type. The random access type comprises a first random access type associated with a duplex operation or a second random access type associated with a non-duplex operation.
[0166] In some embodiments, the configuration further comprises one or more of the following: a timing adjustment parameter; a path loss parameter; or a phase difference parameter.
[0167] In some embodiments, the terminal device may perform the random access by the following: perform the random access to the second network device based on at least one of the timing adjustment parameter, the path loss parameter or the phase difference parameter.
[0168] In some embodiments, the terminal device may perform the random access by the following: determining that the configuration does not comprise information related to timing advance (TA) ; and perform the random access to the second network device based on information of a SSB for the second network device.
[0169] In some embodiments, the terminal device may further: transmit, to the first network device or the second network device, information response comprising an indication that indicates a failure of a random access procedure related to the duplex operation or a failure of a random access procedure related to a non-duplex operation.
[0170] In some embodiments, the information response further comprises at least one of the following an indication of a type of a random access procedure; or a failure reason.
[0171] In some embodiments, the type of random access procedure comprises: a first type of contention-based random access (CBRA) ; and a second type of contention-free random access (CFRA) .
[0172] In some embodiments, the terminal device may transmit the information response by the following: receiving, from the first network device, a first trigger message; or receiving, from the second network device, a second trigger message.
[0173] In some embodiments, the terminal device is configured with a first power ramping counter associated with a duplex operation, and a first maximum value of the first power ramping counter is smaller than a second maximum value of a second power ramping counter associated with a non-duplex operation.
[0174] FIG. 9 illustrates a flowchart of a method 900 of communication implemented at a first network device in accordance with some embodiments of the present disclosure. The method 900 can be implemented at the first network device 120 shown in FIG. 1. For the purpose of discussion, the method 900 will be described with reference to FIG. 1. It is to be understood that the method 900 may include additional acts not shown and / or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
[0175] At 910, the first network 120 transmits, to a second network device 130, a secondary cell addition request. At 920, the first network device 120 receives, from the second network device 130, an addition request acknowledge message comprising a first set of resources for random access. The first set of resources is related to a duplex operation. At 930, the first network device 120 transmits, a terminal device, a configuration comprising the first set of resources.
[0176] In some embodiments, at least one of the addition request acknowledge message or the configuration further comprises: a second set of resources for random access, wherein the second set of resource is related to non-duplex operation; and information of a synchronization signal block (SSB) for the second network device.
[0177] In some embodiments, the first network device may further receive, from the terminal device, a connection reconfiguration complete message after a random access procedure performed by the terminal device to the second network device.
[0178] In some embodiments, the connection reconfiguration complete message indicates one or more of the following: a first indication indicating that a random access procedure is failed or successful; a second indication indicating that the random access procedure is related to a duplex operation or non-duplex operation; a third indication of a failure reason; or a fourth indication indicting that a reconfiguration failure procedure is performed.
[0179] In some embodiments, the first network device 120 may further determine that a random access procedure between the terminal device and the second network device is failed; and transmit, to the terminal device, a request for measuring a cross link interference (CLI) .
[0180] In some embodiments, at least one of the addition request acknowledge message or the configuration further comprises: an indication of a random access type. The random access type comprises a first random access type associated with a duplex operation or a second random access type associated with a non-duplex operation.
[0181] In some embodiments, at least one of the addition request acknowledge message or the configuration further comprises: a timing adjustment parameter; a path loss parameter; or a phase difference parameter.
[0182] In some embodiments, the first network device may further receive, from the terminal device, information response comprising an indication that indicates a failure of a random access procedure related to the duplex operation or a failure of a random access procedure related to a non-duplex operation.
[0183] In some embodiments, the information response further comprises at least one of the following an indication of a type of a random access procedure; or a failure reason.
[0184] In some embodiments, the type of random access procedure comprises: a first type of contention-based random access (CBRA) ; and a second type of contention-free random access (CFRA) .
[0185] In some embodiments, the first network device may receive the information response by the following: transmitting, to the terminal device, a first trigger message.
[0186] FIG. 10 illustrates a flowchart of a method 1000 of communication implemented at a second network device in accordance with some embodiments of the present disclosure. The method 1000 can be implemented at the second network device 130 shown in FIG. 1. For the purpose of discussion, the method 1000 will be described with reference to FIG. 1. It is to be understood that the method 1000 may include additional acts not shown and / or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
[0187] At 1010, the second network device 130 receives, from a first network device, a secondary cell addition request. At 1020, the second network device 130 transmits, to the first network device, an addition request acknowledge message comprising a first set of resources for random access. The first set of resources is related to a duplex operation.
[0188] In some embodiments, the addition request acknowledge message comprises: a second set of resources for random access, wherein the second set of resource is related to non-duplex operation; and information of a synchronization signal block (SSB) for the second network device.
[0189] In some embodiments, the second network device may further receive, from a terminal device, a random access preamble based on the configuration.
[0190] In some embodiments, the addition request acknowledge message further comprises: an indication of a random access type, wherein the random access type comprises a first random access type associated with a duplex operation or a second random access type associated with a non-duplex operation.
[0191] In some embodiments, the addition request acknowledge message further comprises: a timing adjustment parameter; a path loss parameter; or a phase difference parameter.
[0192] In some embodiments, the second network device may further receive, from the first network device, a connection reconfiguration complete message after a random access procedure performed by the terminal device to the second network device.
[0193] In some embodiments, the connection reconfiguration complete message indicates one or more of the following: a first indication indicating that a random access procedure is failed or successful; a second indication indicating that the random access procedure is related to a duplex operation or non-duplex operation; a third indication of a failure reason; or a fourth indication indicting that a reconfiguration failure procedure is performed.
[0194] In some embodiments, the second network device may further: receive, from a terminal device, , information response comprising an indication that indicates a failure of a random access procedure related to the duplex operation or a failure of a random access procedure related to a non-duplex operation.
[0195] In some embodiments, the information response further comprises at least one of the following: an indication of a type of a random access procedure; or a failure reason.
[0196] In some embodiments, the type of random access procedure comprises: a first type of contention-based random access (CBRA) ; and second type of contention-free random access (CFRA) .
[0197] In some embodiments, the second network device may receive the information response by the following: transmitting, to the terminal device, a second trigger message.
[0198] FIG. 11 is a simplified block diagram of a device 1100 that is suitable for implementing some embodiments of the present disclosure. The device 1100 can be considered as a further example embodiment of the terminal device 110, the (first) network device 120 or the second network device 130 as shown in FIG. 1. Accordingly, the device 1100 can be implemented at or as at least a part of the above network devices or terminal devices.
[0199] As shown, the device 1100 includes a processor 1110, a memory 1120 coupled to the processor 1110, a suitable transceiver 1140 coupled to the processor 1110, and a communication interface coupled to the transceiver 1140. The memory 1110 stores at least a part of a program 1130. The transceiver 1140 may be for bidirectional communications or a unidirectional communication based on requirements. The transceiver 1140 may include at least one of a transmitter 1142 and a receiver 1144. The transmitter 1142 and the receiver 1144 may be functional modules or physical entities. The transceiver 1140 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2 / Xn interface for bidirectional communications between eNBs / gNBs, S1 / NG interface for communication between a Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and the eNB / gNB, Un interface for communication between the eNB / gNB and a relay node (RN) , or Uu interface for communication between the eNB / gNB and a terminal device.
[0200] The program 1130 is assumed to include program instructions that, when executed by the associated processor 1110, enable the device 1100 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGS. 1-10. The embodiments herein may be implemented by computer software executable by the processor 1110 of the device 1100, or by hardware, or by a combination of software and hardware. The processor 1110 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1110 and memory 1120 may form processing means 1150 adapted to implement various embodiments of the present disclosure.
[0201] The memory 1120 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1120 is shown in the device 1100, there may be several physically distinct memory modules in the device 1100. The processor 1110 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1100 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0202] In some embodiments, a terminal device comprises circuitry configured to perform a method 500, 600 and / or 800.
[0203] In some embodiments, a network device comprises circuitry configured to perform a method 700, 900 and / or 1000.
[0204] The components included in the apparatuses and / or devices of the present disclosure may be implemented in various manners, including software, hardware, firmware, or any combination thereof. In one embodiment, one or more units may be implemented using software and / or firmware, for example, machine-executable instructions stored on the storage medium. In addition to or instead of machine-executable instructions, parts or all of the units in the apparatuses and / or devices may be implemented, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs) , Application-specific Integrated Circuits (ASICs) , Application-specific Standard Products (ASSPs) , System-on-a-chip systems (SOCs) , Complex Programmable Logic Devices (CPLDs) , and the like.
[0205] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, technique terminal devices or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0206] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to any of FIGS. 2 to 10. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0207] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0208] The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0209] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific embodiment details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.
[0210] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
[0211] In summary, embodiments of the present disclosure may provide the following solutions.
[0212] A terminal device comprising: a processor, and the processor is configured to cause the terminal device to: determine that one or more random access attempts on a resource related to duplex operation have failed; and transmit, to a network device, information response comprising an indication that indicates a failure of a random access attempt related to the duplex operation.
[0213] In one embodiment, wherein the resource comprises a random access channel (RACH) resource for a further network device which supports a sub-band full duplex (SBFD) operation.
[0214] In one embodiment, wherein the information response further comprises at least one of the following: an indication of a type of a random access attempt of the one or more random access attempts; or a failure reason.
[0215] In one embodiment, wherein the type of random access attempt comprises: a first type of contention-based random access (CBRA) ; and a second type of contention-free random access (CFRA) .
[0216] In one embodiment, wherein the failure reason comprises a cross link interference (CLI) reason.
[0217] A network device comprising: a processor, and the processor is configured to cause the network device to: receive, from a terminal device, information response comprising an indication that indicates a failure of random access attempt related to the duplex operation.
[0218] In one embodiment, wherein the random access attempt is performed on a random access channel (RACH) resource for a further network device which supports a sub-band full duplex (SBFD) operation.
[0219] In one embodiment, wherein the information response further comprises at least one of the following: an indication of a type of a random access attempt of the one or more random access attempts; or a failure reason.
[0220] In one embodiment, wherein the type of random access attempt comprises: a first type of contention-based random access (CBRA) ; and a second type of contention-free random access (CFRA) .
[0221] In one embodiment, wherein the failure reason comprises a cross link interference (CLI) reason.
[0222] A terminal device comprising: a processor, and the processor is configured to cause the terminal device to: receive, from a first network device, a configuration comprising a first set of resources for random access, wherein the first set of resources is related to a duplex operation; and perform a random access to a second network device based on the configuration.
[0223] In one embodiment, wherein the configuration further comprises the following: a second set of resources for random access, wherein the second set of resource is related to non-duplex operation; and information of a synchronization signal block (SSB) for the second network device.
[0224] In one embodiment, wherein the first set of resources and the second set of resources are configured for contention-free random access (CFRA) .
[0225] In one embodiment, wherein the terminal device is caused to perform the random access by the following: perform the random access to the second network device using the first set of resources or the second set of resources based on a predefined rule, wherein the predefined rule comprises at least one of a first priority level of the first set of resources or a second priority level of the second set of resources.
[0226] In one embodiment, wherein the random access is a first random access, and wherein the terminal device is further caused to: determine that the first random access performed using one of the first set of resources or the second set of resources is failed; and perform a second random access to the second network device using another one of the first set of resources or the second set of resources.
[0227] In one embodiment, wherein the terminal device is further caused to: determine that the further random access is failed; and perform a third random access to the second network device based on the information of SSB for the second network device.
[0228] In one embodiment, wherein the terminal device is further caused to: transmit, to the first network device, a connection reconfiguration complete message.
[0229] In one embodiment, wherein the connection reconfiguration complete message indicates one or more of the following: a first indication indicating that a random access procedure is failed or successful; a second indication indicating that the random access procedure is related to a duplex operation or non-duplex operation; a third indication of a failure reason; or a fourth indication indicting that a reconfiguration failure procedure is performed.
[0230] In one embodiment, wherein the terminal device is further caused to: receive, from the first network device, a request for measuring a cross link interference (CLI) , wherein the request is response to a failure of a random access procedure; and determine whether the failure of the random access procedure is caused by the CLI based on the request.
[0231] In one embodiment, wherein the configuration further comprises an indication of a random access type, and wherein the terminal device is caused to perform the random access by the following: performing the random access based on the random access type, wherein the random access type comprises a first random access type associated with a duplex operation or a second random access type associated with a non-duplex operation.
[0232] In one embodiment, wherein the configuration further comprises one or more of the following: a timing adjustment parameter; a path loss parameter; or a phase difference parameter.
[0233] In one embodiment, wherein the terminal device is caused to perform the random access by the following: perform the random access to the second network device based on at least one of the timing adjustment parameter, the path loss parameter or the phase difference parameter.
[0234] In one embodiment, wherein the terminal device is caused to perform the random access by the following: determining that the configuration does not comprise information related to timing advance (TA) ; and perform the random access to the second network device based on information of a SSB for the second network device.
[0235] In one embodiment, wherein the terminal device is further caused to: transmit, to the first network device or the second network device, information response comprising an indication that indicates a failure of a random access procedure related to the duplex operation or a failure of a random access procedure related to a non-duplex operation.
[0236] In one embodiment, wherein the information response further comprises at least one of the following: an indication of a type of a random access procedure; or a failure reason.
[0237] In one embodiment, wherein the type of random access procedure comprises: a first type of contention-based random access (CBRA) ; and a second type of contention-free random access (CFRA) .
[0238] In one embodiment, wherein the terminal device is caused to transmit the information response by the following: receiving, from the first network device, a first trigger message; or receiving, from the second network device, a second trigger message.
[0239] In one embodiment, wherein the terminal device is configured with a first power ramping counter associated with a duplex operation, and wherein a first maximum value of the first power ramping counter is smaller than a second maximum value of a second power ramping counter associated with a non-duplex operation.
[0240] A first network device comprising: a processor, and the processor is configured to cause the first network device to: transmit, to a second network device, a secondary cell addition request; and receive, from the second network device, an addition request acknowledge message comprising a first set of resources for random access, wherein the first set of resources is related to a duplex operation; and transmit, a terminal device, a configuration comprising the first set of resources.
[0241] In one embodiment, wherein at least one of the addition request acknowledge message or the configuration further comprises: a second set of resources for random access, wherein the second set of resource is related to non-duplex operation; and information of a synchronization signal block (SSB) for the second network device.
[0242] In one embodiment, the first network device is further caused to: receive, from the terminal device, a connection reconfiguration complete message after a random access procedure performed by the terminal device to the second network device.
[0243] In one embodiment, wherein the connection reconfiguration complete message indicates one or more of the following: a first indication indicating that a random access procedure is failed or successful; a second indication indicating that the random access procedure is related to a duplex operation or non-duplex operation; a third indication of a failure reason; or a fourth indication indicting that a reconfiguration failure procedure is performed.
[0244] In one embodiment, wherein the first network device is further caused to: determine that a random access procedure between the terminal device and the second network device is failed; and transmit, to the terminal device, a request for measuring a cross link interference (CLI) .
[0245] In one embodiment, wherein at least one of the addition request acknowledge message or the configuration further comprises: an indication of a random access type, wherein the random access type comprises a first random access type associated with a duplex operation or a second random access type associated with a non-duplex operation.
[0246] In one embodiment, wherein at least one of the addition request acknowledge message or the configuration further comprises: a timing adjustment parameter; a path loss parameter; or a phase difference parameter.
[0247] In one embodiment, wherein the first network device is further caused to: receive, from the terminal device, information response comprising an indication that indicates a failure of a random access procedure related to the duplex operation or a failure of a random access procedure related to a non-duplex operation.
[0248] In one embodiment, wherein the information response further comprises at least one of the following: an indication of a type of a random access procedure; or a failure reason.
[0249] In one embodiment, wherein the type of random access procedure comprises: a first type of contention-based random access (CBRA) ; and a second type of contention-free random access (CFRA) .
[0250] In one embodiment, wherein the first network device is caused to receive the information response by the following: transmitting, to the terminal device, a first trigger message.
[0251] A second network device comprising: a processor, and the processor is configured to cause the second network device to: receive, from a first network device, a secondary cell addition request; and transmit, to the first network device, an addition request acknowledge message comprising a first set of resources for random access, wherein the first set of resources is related to a duplex operation.
[0252] In one embodiment, wherein the addition request acknowledge message comprises: a second set of resources for random access, wherein the second set of resource is related to non-duplex operation; and information of a synchronization signal block (SSB) for the second network device.
[0253] In one embodiment, wherein the second network device is further caused to: receive, from a terminal device, a random access preamble based on the configuration.
[0254] In one embodiment, wherein the addition request acknowledge message further comprises: an indication of a random access type, wherein the random access type comprises a first random access type associated with a duplex operation or a second random access type associated with a non-duplex operation.
[0255] In one embodiment, wherein the addition request acknowledge message further comprises: a timing adjustment parameter; a path loss parameter; or a phase difference parameter.
[0256] In one embodiment, wherein the second network device is further caused to: receive, from the first network device, a connection reconfiguration complete message after a random access procedure performed by the terminal device to the second network device.
[0257] In one embodiment, wherein the connection reconfiguration complete message indicates one or more of the following: a first indication indicating that a random access procedure is failed or successful; a second indication indicating that the random access procedure is related to a duplex operation or non-duplex operation; a third indication of a failure reason; or a fourth indication indicting that a reconfiguration failure procedure is performed.
[0258] In one embodiment, wherein the second network device is further caused to: receive, from a terminal device, , information response comprising an indication that indicates a failure of a random access procedure related to the duplex operation or a failure of a random access procedure related to a non-duplex operation.
[0259] In one embodiment, wherein the information response further comprises at least one of the following: an indication of a type of a random access procedure; or a failure reason.
[0260] In one embodiment, wherein the type of random access procedure comprises: a first type of contention-based random access (CBRA) ; and a second type of contention-free random access (CFRA) .
[0261] In one embodiment, wherein the second network device is caused to receive the information response by the following: transmitting, to the terminal device, a second trigger message.
[0262] A terminal device comprising: a processor, and the processor is configured to cause the terminal device to: transmit, to a network device, an indication related to a capability of dynamic power sharing for dual connectivity (DC) , wherein a secondary cell associated with the DC enables a sub-band full duplex (SBFD) operation; and reduce transmission power for a main cell associated with the DC based on the indication that indicates the capability of dynamic power sharing.
[0263] In one embodiment, wherein the terminal device is further caused to: refrain from a transmission to the main cell using a first resource, based on the indication that does not indicate the capability of dynamic power sharing; and perform a further transmission to the secondary cell using the first resource.
[0264] In one embodiment, wherein the terminal device is caused to reduce the transmission power for the main cell by the following: determining maximum transmission power for the secondary cell.
[0265] In one embodiment, wherein the terminal device is further caused to: perform, based on the maximum transmission power, a physical random access channel (PRACH) transmission to the secondary cell at a starting PRACH occasion.
[0266] In one embodiment, wherein the terminal device is caused to reduce the transmission power for the main cell by the following: determining a transmission power for the secondary cell based on information related to pathloss between the main cell and the secondary cell.
[0267] In one embodiment, wherein the terminal device is caused to determine the transmission power for the secondary cell based on one or more of the following: a power ramping step size dedicated to a cell enabling the SBFD operation; or an offset parameter for calculating a transmission power.
[0268] A method of communication, comprising: determining, at a terminal device, that one or more random access attempts on a resource related to duplex operation have failed; and transmitting, to a network device, information response comprising an indication that indicates a failure of a random access attempt related to the duplex operation.
[0269] A method of communication, comprising: receiving, at a network device from a terminal device, information response comprising an indication that indicates a failure of random access attempt related to the duplex operation.
[0270] A method of communication, comprising: receiving, at a terminal device from a first network device, a configuration comprising a first set of resources for random access, wherein the first set of resources is related to a duplex operation; and performing a random access to a second network device based on the configuration.
[0271] A method of communication, comprising: transmitting, at a first network device to a second network device, a secondary cell addition request; and receiving, from the second network device, an addition request acknowledge message comprising a first set of resources for random access, wherein the first set of resources is related to a duplex operation; and transmitting, a terminal device, a configuration comprising the first set of resources.
[0272] A method of communication, comprising: receiving, at a second network device from a first network device, a secondary cell addition request; and transmitting, to the first network device, an addition request acknowledge message comprising a first set of resources for random access, wherein the first set of resources is related to a duplex operation.
[0273] A method of communication, comprising: transmitting, at a terminal device to a network device, an indication related to a capability of dynamic power sharing for dual connectivity (DC) , wherein a secondary cell associated with the DC enables a sub-band full duplex (SBFD) operation; and reducing transmission power for a main cell associated with the DC based on the indication that indicates the capability of dynamic power sharing.
[0274] A computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method according to the above embodiment.
Claims
1.A terminal device comprising:a processor, and the processor is configured to cause the terminal device to:determine that one or more random access attempts on a resource related to duplex operation have failed; andtransmit, to a network device, information response comprising an indication that indicates a failure of a random access attempt related to the duplex operation.2.The terminal device of claim 1, wherein the resource comprises a random access channel (RACH) resource for a further network device which supports a sub-band full duplex (SBFD) operation.3.The terminal device of claim 1, wherein the information response further comprises at least one of the following:an indication of a type of a random access attempt of the one or more random access attempts; ora failure reason.4.The terminal device of claim 3, wherein the type of random access attempt comprises:a first type of contention-based random access (CBRA) ; anda second type of contention-free random access (CFRA) .5.The terminal device of claim 3, wherein the failure reason comprises a cross link interference (CLI) reason.6.A terminal device comprising:a processor, and the processor is configured to cause the terminal device to:receive, from a first network device, a configuration comprising a first set of resources for random access, wherein the first set of resources is related to a duplex operation; andperform a random access to a second network device based on the configuration.7.The terminal device of claim 6, wherein the configuration further comprises the following:a second set of resources for random access, wherein the second set of resource is related to non-duplex operation; andinformation of a synchronization signal block (SSB) for the second network device.8.The terminal device of claim 7, wherein the first set of resources and the second set of resources are configured for contention-free random access (CFRA) .9.The terminal device of claim 6, wherein the terminal device is caused to perform the random access by the following:perform the random access to the second network device using the first set of resources or the second set of resources based on a predefined rule,wherein the predefined rule comprises at least one of a first priority level of the first set of resources or a second priority level of the second set of resources.10.The terminal device of claim 9, wherein the terminal device is further caused to:determine that the further random access is failed; andperform a third random access to the second network device based on the information of SSB for the second network device.11.The terminal device of any of claims 6 to 10, wherein the terminal device is further caused to:transmit, to the first network device, a connection reconfiguration complete message.12.The terminal device of claim 11, wherein the connection reconfiguration complete message indicates one or more of the following:a first indication indicating that a random access procedure is failed or successful;a second indication indicating that the random access procedure is related to a duplex operation or non-duplex operation;a third indication of a failure reason; ora fourth indication indicting that a reconfiguration failure procedure is performed.13.The terminal device of any of claims 6 to 12, wherein the terminal device is further caused to:receive, from the first network device, a request for measuring a cross link interference (CLI) , wherein the request is response to a failure of a random access procedure; anddetermine whether the failure of the random access procedure is caused by the CLI based on the request.14.The terminal device of claim 6, wherein the configuration further comprises an indication of a random access type, and wherein the terminal device is caused to perform the random access by the following:performing the random access based on the random access type,wherein the random access type comprises a first random access type associated with a duplex operation or a second random access type associated with a non-duplex operation.15.The terminal device of claim 6, wherein the configuration further comprises one or more of the following:a timing adjustment parameter;a path loss parameter; ora phase difference parameter.16.The terminal device of claim 6, wherein the terminal device is caused to perform the random access by the following:determining that the configuration does not comprise information related to timing advance (TA) ; andperform the random access to the second network device based on information of a SSB for the second network device.17.The terminal device of any claims 6 to 16, wherein the terminal device is further caused to:transmit, to the first network device or the second network device, information response comprising an indication that indicates a failure of a random access procedure related to the duplex operation or a failure of a random access procedure related to a non-duplex operation.18.A first network device comprising:a processor, and the processor is configured to cause the first network device to:transmit, to a second network device, a secondary cell addition request; andreceive, from the second network device, an addition request acknowledge message comprising a first set of resources for random access, wherein the first set of resources is related to a duplex operation; andtransmit, a terminal device, a configuration comprising the first set of resources.19.A second network device comprising:a processor, and the processor is configured to cause the second network device to:receive, from a first network device, a secondary cell addition request; andtransmit, to the first network device, an addition request acknowledge message comprising a first set of resources for random access, wherein the first set of resources is related to a duplex operation.20.A terminal device comprising:a processor, and the processor is configured to cause the terminal device to:transmit, to a network device, an indication related to a capability of dynamic power sharing for dual connectivity (DC) , wherein a secondary cell associated with the DC enables a sub-band full duplex (SBFD) operation; andreduce transmission power for a main cell associated with the DC based on the indication that indicates the capability of dynamic power sharing.
