Service cluster updates

Abstract

The invention discloses service cluster updating equipment, a service cluster updating method, a service cluster updating device and a computer readable storage medium. The method comprises the following steps: at least based on timing advance of terminal equipment relative to a group of candidate TRP, selecting one or more target TRP associated with updating of a service cluster of the terminal equipment from the group of candidate TRP through distributed network nodes; and transmitting information related to the update of the service cluster.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and in particular to devices, methods, apparatuses, and computer-readable storage media for service cluster update. Background Art

[0002] The main goals of multiple-input multiple-output (MIMO) enhancements may involve beam management, multiple transmit and receive points (mTRP) for ultra-reliable low-latency communication (URLLC), mTRP for enhanced mobile broadband (eMBB), and time division duplex (TDD) / frequency division duplex (FDD) reciprocity.

[0003] The mTRP enhancements for eMBB increase the robustness of the Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), and Physical Uplink Control Channel (PUCCH). They also enable richer channel state information (CSI) feedback for non-coherent joint transmission (NC-JT) and optimize performance for high-speed train (HST) communication scenarios. Summary of the Invention

[0004] Generally speaking, example embodiments of the present disclosure provide a solution for service cluster updates.

[0005] In a first aspect, a distributed network device is provided. The distributed network device includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause a distributed network node to at least: select one or more target TRPs associated with an update of a service cluster of a terminal device from a set of candidate TRPs based at least on a timing advance of the terminal device relative to a set of candidate TRPs; and transmit information related to the update of the service cluster.

[0006] In a second aspect, a TRP is provided, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the TRP to at least: receive information related to an update of a service cluster of a terminal device from a distributed network node.

[0007] In a third aspect, a TRP is provided. The TRP includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the TRP to at least: determine a timing advance of a terminal device relative to the TRP based on an uplink resource allocation for the terminal device and an uplink signal received from the terminal device; and send information about the timing advance to a distributed network node.

[0008] In a fourth aspect, a terminal device is provided. The terminal device includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: receive an indication of uplink resource allocation for the terminal device from a distributed network device; and send an uplink signal to a set of candidate TRPs.

[0009] In a fifth aspect, a method is provided, comprising: selecting, by a distributed network node, one or more target TRPs associated with an update of a service cluster for the terminal device from a set of candidate TRPs based at least on a timing advance of the terminal device relative to a set of candidate TRPs; and transmitting information related to the update of the service cluster.

[0010] In a sixth aspect, a method is provided. The method includes receiving, at a TRP from a distributed network node, information about one or more target TRPs associated with an update of a service cluster of a terminal device.

[0011] In a seventh aspect, a method is provided, comprising: determining, at a TRP, a timing advance of a terminal device relative to the TRP based on an uplink resource allocation for the terminal device and an uplink signal received from the terminal device; and sending information about the timing advance to a distributed network node.

[0012] In an eighth aspect, a method is provided, comprising: receiving, at a terminal device, an indication of uplink resource allocation for the terminal device from a distributed network device; and sending an uplink signal to a group of TRPs.

[0013] In a ninth aspect, a device is provided, comprising: a component for selecting one or more target TRPs associated with an update of a service cluster of a terminal device from a set of candidate transceiver points TRPs based at least on a timing advance of the terminal device relative to a set of candidate transceiver points TRPs; and a component for sending information related to the update of the service cluster.

[0014] In a tenth aspect, an apparatus is provided, the apparatus comprising means for receiving, from a distributed network node, information about one or more apparatuses associated with an update of a service cluster of a terminal device.

[0015] In an eleventh aspect, a device is provided, comprising: a component for determining a timing advance of a terminal device relative to the device based on an uplink resource allocation for the terminal device and an uplink signal received from the terminal device; and a component for sending information about the timing advance to a distributed network node.

[0016] In a twelfth aspect, an apparatus is provided, comprising: a component for receiving an indication of an uplink resource allocation for the apparatus from a distributed network device; and a component for sending an uplink signal to a set of candidate TRPs.

[0017] In a thirteenth aspect, a computer-readable medium is provided on which a computer program is stored, which, when executed by at least one processor of a device, causes the device to perform the method of the fifth aspect, the sixth aspect, the seventh aspect or the eighth aspect.

[0018] Other features and advantages of embodiments of the present disclosure will also be apparent from the following description of specific embodiments when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The embodiments of the present disclosure are presented in an exemplary sense, and their advantages are explained in more detail below with reference to the accompanying drawings.

[0020] Figure 1 shows an example environment in which example embodiments of the present disclosure may be implemented;

[0021] Figure 2 A signaling diagram illustrating a process of service cluster update according to some example embodiments of the present disclosure;

[0022] Figure 3 A signaling diagram illustrating a process of service cluster update according to some example embodiments of the present disclosure;

[0023] Figure 4 A signaling diagram illustrating a process of service cluster update according to some example embodiments of the present disclosure;

[0024] Figure 5 A flowchart illustrating an example method of service cluster update according to some example embodiments of the present disclosure;

[0025] Figure 6 A flowchart illustrating an example method of service cluster update according to some example embodiments of the present disclosure;

[0026] Figure 7 A flowchart illustrating an example method of service cluster update according to some example embodiments of the present disclosure;

[0027] Figure 8 A flowchart illustrating an example method of service cluster update according to some example embodiments of the present disclosure;

[0028] Figure 9 shows a simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure; and

[0029] Figure 10 A block diagram of an example computer-readable medium is shown, according to some embodiments of the present disclosure.

[0030] Throughout the drawings, the same or similar reference numbers may refer to the same or similar elements. DETAILED DESCRIPTION

[0031] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and help those skilled in the art understand and implement the present disclosure without implying any limitation on the scope of the present disclosure. In addition to the manner described below, the embodiments described herein can be implemented in various ways.

[0032] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0033] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments (whether or not explicitly described).

[0034] It should be understood that although the terms "first," "second," etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0035] As used herein, “at least one of: ” and “at least one of ” and similar expressions (where a list of two or more elements is connected by “and” or “or”) refer to at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0036] As used herein, unless explicitly stated, performing a step "in response to A" does not mean performing the step immediately after "A" occurs and may include one or more intermediate steps.

[0037] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the example embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms "a," "an," and "the" are intended to include the plural forms as well. It will be further understood that when used herein, the terms "comprise," "including," "having," "including," and / or "comprising" specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0038] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) hardware circuit implementation only (such as implementation only in analog and / or digital circuitry), and (b) a combination of hardware circuitry and software such as (if applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) any portion of a hardware processor with software (including a digital signal processor, software and storage machines that work together to enable a device such as a mobile phone or server to perform various functions); and (c) A hardware circuit and / or processor, such as a microprocessor or portion of a microprocessor, that requires software (e.g., firmware) for operation, but in which the software may not be present when not required for operation.

[0039] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, and if applicable to the particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or networking device.

[0040] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), Enhanced Machine Type Communication (eMTC), etc. In addition, the communication between the terminal device and the network device in the communication network is performed according to any suitable generation communication protocol, including but not limited to the first generation (1G) communication protocol, the second generation (2G) communication protocol, the 2.5G communication protocol, the 2.75G communication protocol, the third generation (3G) communication protocol, the fourth generation (4G) communication protocol, the 4.5G communication protocol, the fifth generation (5G) communication protocol and / or any other protocol currently known or developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communications, there are of course future types of communication technologies and systems that can implement the present disclosure. It should not be considered that the scope of the present disclosure is limited to the above-mentioned systems.

[0041] As used herein, the terms "network equipment", "radio network equipment" and / or "radio access network equipment" refer to nodes in a communication network via which a terminal device accesses the network and receives services from it. A network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a repeater, an integrated access and backhaul (IAB) node, a low-power node (such as a femto, a pico), a non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low earth orbit (LEO) satellites and geosynchronous orbit (GEO) satellites, aircraft network equipment, etc.), depending on the terminology and technology applied. In some example embodiments, a radio access network (RAN) split architecture includes a central unit (CU) and a distributed unit (DU). In some other example embodiments, a portion of the radio access network equipment or all of the radio access network equipment may be included on an airborne or space-borne NTN vehicle.

[0042] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image acquisition terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to the mobile terminal (MT) portion of an IAB node (eg, a relay node).In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" may be used interchangeably.

[0043] As used herein, the terms "resource," "transmission resource," "resource block," "physical resource block" (PRB), "uplink resource," or "downlink resource" may refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as resources in the time domain, resources in the frequency domain, resources in the spatial domain, resources in the code domain, or any other combination thereof for achieving communication. Hereinafter, unless explicitly stated otherwise, resources in the frequency domain and the time domain will be used as examples of transmission resources for describing some example embodiments of the present disclosure. Note that the example embodiments of the present disclosure are equally applicable to other resources in other domains.

[0044] Figure 1 1 shows an example communication network 100 in which embodiments of the present disclosure may be implemented. Figure 1As shown, the communication network 100 may include a distributed network device 110 (hereinafter also referred to as a DU), which can manage multiple TRPs, namely TRPs 120-1 to TRPs 120-6. TRPs 120-1 to 120-6 (hereinafter also collectively referred to as TRPs 120) can respectively communicate with the distributed network device 110. As described above, the RAN split architecture may include a CU and a DU. DU 140 can communicate with CU 150. The term "TRP" used herein may refer to a network device, and more specifically, a macro cell, a small cell, a pico cell, a femto cell, a remote radio head, a relay node, etc.

[0045] Communication network 100 may include terminal device 130 (hereinafter also referred to as UE). Some TRPs among the plurality of TRPs, namely TRP 120-1 to TRP 120-6 under DU 110, may serve terminal device 130. For example, TRP 120-1 to TRP 120-3 currently serving terminal device 130 may form a service cluster for terminal device 130.

[0046] As the terminal device 130 moves (e.g., along direction 101), the service cluster may be changed. For example, if the terminal device 110 moves away from TRP 120-2 and TRP 120-3 and toward TRP 120-4 and TRP 120-5, the service cluster of the terminal device 130 may include TRP 120-1, TRP 120-4, and TRP 120-5 after the service cluster update.

[0047] It should be understood that Figure 1 The number of terminal devices and network devices shown is given for illustrative purposes and does not imply any limitation. Communication network 100 may include any suitable number of terminal devices and network devices.

[0048] Furthermore, it should be understood that the service cluster of the terminal device 130 may include more or fewer than three TRPs. The number of TRPs included in a service cluster (ie, how many simultaneous connections the terminal device can have with a TRP) may depend on the capabilities of the terminal device 130.

[0049] As mentioned above, mTRP enhancements have been discussed and developed. mTRP enhancements can allow the UE to receive control information and data from multiple TRPs. However, in non-coherent joint transmission, the UE can process data / control information from each TRP separately at different time frames. Now 3GPP is moving towards coherent joint transmission (CJT). With coherent transmission, the UE can see only a single link from multiple TRPs. It coherently combines the signal-to-noise ratio (SNR) of the signals. On the network side, in coherent transmission, the signals must be sent in phase alignment between different TRPs. This can provide better performance when the radio link is weak.

[0050] The scenario of inter-cell mTRP may involve the case where the cells are from the same DU or the case where the cells are from different DU / CU / nodes. In the case where the cells are not from the same DU, the establishment of a secondary TRP can be performed. Specifically, based on the UE Layer 3 (L3) measurement report, the source node that controls the source cell identifies potential secondary cells controlled by different DU / nodes and proceeds to send a "TRP Add Request" for the secondary cell. Upon receiving the response in the "TRP Add Request ACK message", it sends a radio resource control (RRC) reconfiguration with the corresponding configuration of the secondary cell (TRP) to the UE. When the source node decides to activate mTRP due to some reasons (such as heavy traffic load), it will send a MAC-CE mTRP activation to the UE. The UE then proceeds to randomly access the secondary cell and starts data transmission to multiple TRPs.

[0051] In addition, the inter-cell mTRP process can be made to operate in both handover (HO) with and without serving cell. Specifically, the source node initially establishes mTRP operation (serving and secondary cell), and then based on the measurement report, it identifies the handover target cell and sends a handover request and receives a corresponding response. The source node then forwards the RRC reconfiguration (HO command) to the UE and notifies the secondary node (controlling the secondary cell) of the release of the mTRP. Upon receiving the RRC reconfiguration containing the handover command, the UE performs the HO, and once the HO is completed, the UE can provide the required measurements to the target node, which can configure the inter-cell mTRP and add the same secondary cell previously configured by the source cell before the handover.

[0052] As mentioned above, how many simultaneous connections a UE can have with a TRP depends on the UE's capabilities. Assuming that a UE can support up to three simultaneous TRP connections, due to the higher density of TRPs in 6G, a UE can change its connected TRP multiple times even within the same cell.

[0053] Regardless of low-layer mobility or high-layer mobility in the case of mTRP, the HO command is triggered at the CU level based on L3 measurements during the mTRP handover process in 5G. However, L3 measurements are not up-to-date enough for high-speed scenarios, and CU-level triggering significantly slows down the process.

[0054] In addition, the handover process in 5G mobility is "interrupt before establishment". That is, the connection between the UE and the TRP can be interrupted before another connection between the UE and the new TRP is established.

[0055] Therefore, how to seamlessly handle mobility in 6G with a higher density of TRPs deployed may require further discussion. First, an interesting aspect in the intra-cell scenario that needs to be discussed is how to update the serving TRP cluster.

[0056] The solution disclosed herein proposes a service cluster update method in which the distributed network device 110 selects one or more target TRPs associated with updating the service cluster of a terminal device from a set of candidate TRPs based at least on the timing advance of the terminal device relative to the set of candidate TRPs, and sends information related to the service cluster update.

[0057] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0058] Before serving the terminal device 130, the distributed network device 110 can allocate different reference signals (such as channel state information reference signals (CSI-RS)) to different TRPs, and broadcast them to the terminal device 130 through the DL physical broadcast channel (PBCH) or DL ​​PDSCH, so that the terminal device 130 can measure and feedback the DL channel information of the corresponding TRP, and the DL PDSCH can be used to indicate the resources for subsequent triggering of CFRA transmission.

[0059] In addition, the DU can reserve a certain number of common physical random access channel (PRACH) resources for the related TRPs connected to it, which are used for the terminal device to perform UL synchronization process with multiple TRPs through one UL PRACH transmission process.

[0060] During normal data transmission of the terminal device 130, the distributed network device 110 may trigger the terminal device 130 to send a TRP to its current serving cluster (e.g., Figure 1 TRPs 120-1 through 120-3 shown) and other related TRPs such as those adjacent to its current serving cluster (e.g., Figure 1Channel measurements of TRPs 120-4 through 120-6 are shown. Related TRPs may include TRPs outside of the serving cluster of the terminal device 130, for example, requested by the network or visibility.

[0061] Thereafter, the terminal device 130 may send the best K channel measurement reports to the distributed network device 110 in a periodic, semi-persistent, aperiodic, or event-triggered manner. The distributed network device 110 may determine up to K TRPs that can receive common UL resources from the terminal device 130 and estimate the timing advance (TA). These TRPs may form a measurement cluster.

[0062] For example, Figure 1 As shown, TRPs 120-1 to 120-3 are included in the current serving cluster of terminal device 130. As terminal device 130 moves, the serving cluster of terminal device 130 may change. After performing channel measurement, distributed network device 110 may select a group of TRPs from TRPs 120-1 to 120-6 to form a measurement cluster. For example, TRP 120-1, TRP 120-4, TRP 120-5, and TRP 120-6 may be selected to form a measurement cluster. Hereinafter, the TRPs 120-1 and 120-6 in the measurement cluster may also be referred to as a group of candidate TRPs 120-1, 120-4, 120-5, and 120-6. The distributed network device 110 may select one or more TRPs from a set of candidate TRPs 120-1, 120-4, 120-5, and 120-6 to form an updated service cluster. Hereinafter, the TRPs forming the updated service cluster may be referred to as target TRPs.

[0063] Now refer to Figure 2 ,Should Figure 2 2 shows a signaling diagram 200 for communication according to some example embodiments of the present disclosure. Figure 2 As shown, the signaling diagram 200 involves the distributed network device 110, the terminal device 130, and the candidate TRP 120-1, the candidate TRP 120-4, the candidate TRP 120-5, or the candidate TRP 120-6, the TRP of the updated service cluster that was already in the previous service cluster 120-1, and the TRP that newly joins the updated service cluster 120-4 or 120-5. For the purpose of discussion, reference is made to Figure 1 2. Signaling diagram 200 is described below.

[0064] like Figure 2As shown, the terminal device 130 may send 202 a channel measurement report of the terminal device 130 to the distributed network device. The distributed network device 110 may then select 204 a set of candidate groups to form a measurement cluster.

[0065] The distributed network device 110 may notify 206 the terminal device 130 of the UL resources in the time domain and / or the frequency domain and a contention-free random access (CFAR) preamble. The distributed network device 110 may also notify 208 the candidate TRP 120-1, the candidate TRP 120-4, the candidate TRP 120-5, or the candidate TRP 120-6 of the UL resources in the time domain and / or the frequency domain and the CFAR preamble allocated to the terminal device 130.

[0066] The terminal device 130 may then send 210 a random access message (eg, message 1), a sounding reference signal (SRS), or at least one of the scheduled time-frequency resources to the candidate TRP 120-1, the candidate TRP 120-4, the candidate TRP 120-5, or the candidate TRP 120-6.

[0067] Each of candidate TRP 120-1, candidate TRP 120-4, candidate TRP 120-5, or candidate TRP 120-6 may then estimate 212 a TA of terminal device 130 relative to itself. Candidate TRP 120-1, candidate TRP 120-4, candidate TRP 120-5, or candidate TRP 120-6 may send 214 its corresponding TA information of terminal device 130 to distributed network device 110. Based on the received TA information, distributed network device 110 may select 216 one or more TRPs from the measurement cluster to form an updated serving cluster. One or more TRPs may simultaneously send data / control information to the UE. The selected TRP for the updated serving cluster may also be referred to as a target TRP hereinafter.

[0068] In some example embodiments, distributed network device 110 may select a target TRP from among candidate TRP 120-1, candidate TRP 120-4, candidate TRP 120-5, and candidate TRP 120-6 based on the TA information and some other rules.

[0069] For example, if the TA measurement of the candidate TRP does not align with the final determined TA value, the candidate TRP may not be selected as the target TRP. In other example embodiments, if the radio link quality and / or load of the candidate TRP does not meet a threshold level, the candidate TRP may not be selected as the target TRP. If the candidate TRP is an existing TRP in the previous service cluster, the candidate TRP may be removed from the updated service cluster.

[0070] In contrast, if the TA measurement of the candidate TRP is aligned with the final determined TA value, the candidate TRP may be selected as the target TRP. Alternatively or additionally, if the TA measurement of the candidate TRP meets (e.g., exceeds) a predefined threshold, the candidate TRP may be selected as the target TRP. Alternatively, if the TA measurement of the candidate TRP is higher than the TA measurement of the existing service cluster by a threshold, the candidate TRP may be selected as the target TRP. For example, if the TA measurement of the new TRP is higher than the TA measurement of the previous service cluster by a threshold, the new TRP may be added to the updated service cluster.

[0071] That is, the one or more target TRPs used to form the updated service cluster of the terminal device 130 may include one or more existing TRPs that were previously in the service cluster and one or more new TRPs that are newly added to the updated service cluster.

[0072] For example, in process 200, TRP 120-1 may be selected as a target TRP for forming an updated service cluster, which is an existing TRP that was previously in the service cluster. TRP 120-4 and TRP 120-5 may also be selected as target TRPs that are newly added to the updated service cluster.

[0073] After determining the target TRP, as an option, the distributed network device 110 may send 218 an activation command regarding the new RRC configuration of the new TRP 120-4 and the new TRP 120-5 to the TRP 120-1 (which may also be referred to as the existing TRP in the updated service cluster).

[0074] As another option, the distributed network device 110 may send 222 an activation command regarding the new RRC configuration of the new TRP 120-4 and the new TRP 120-5 to the TRP 120-4 or the TRP 120-5 (which may also be referred to as the new TRP in the updated service cluster).

[0075] The activation command may include frequency and time resources for the terminal device 130 to later send a media access control-control element (MAC-CE) request. Optionally or additionally, the activation command may also include a TA value. If this field does not exist, the terminal device 130 can use the traditional TA, and if the field contains a new TA value, the terminal device 130 can apply the TA to all TRPs in the service cluster. In this step, the distributed network device 110 can schedule resources for different physical (PHY) layer technologies and indicate that the distributed network device can be updated via MAC-CE for the TRP modification.

[0076] For scenarios in distributed MIMO (dMIMO), the resources are known and common to all TRPs in the service cluster. The distributed network device 110 can use a 1-bit indication to indicate whether a new TRP 120-4 or a new TRP 120-5 will notify the distributed network device 110 of updates, or whether the existing TRP 120-1 will notify the distributed network device 110 of updates.

[0077] For scenarios in NC-JT or CJT, if the distributed network device 110 wants to receive updates from an existing TRP, the distributed network device 110 can schedule resources for receiving MAC-CE updates, which are visible only to the existing TRP 120-1, otherwise visible to the new TRP 120-4 or the new TRP 120-5.

[0078] After receiving the RRC configuration for activating the new TRP, the existing TRP 120-1 may send 220 an activation command to the terminal device 130 via an existing connection or dynamic DL scheduling of frequency and time resources regarding a MAC-CE command from the terminal device 130 and the TA value associated with the terminal device 130 from each TRP and the new TRP configuration.

[0079] The terminal device 130 may then send 226 a TRP modification request ACK to the existing TRP 120-1 in the serving cluster via MAC-CE in response to the request from action 220. The existing TRP 120-1 in the serving cluster may then send 228 a TRP modification update message to the distributed network device 110 to update the distributed network device 110.

[0080] After receiving the RRC configuration for activating the new TRP, the new TRP 120-4 or the new TRP 120-5 in the service cluster can send 224 an activation command to the terminal device 130 via predetermined resources (such as those frequency and time resources regarding the MAC-CE command from the terminal device 130 in action 210) and the TA value associated with the terminal device 130 from each TRP and the new TRP configuration.

[0081] The terminal device 130 may then send 230 a TRP modification request ACK to the new TRP 120-4 or the new TRP 120-5 in the serving cluster via MAC-CE in response to the request from action 224. The new TRP 120-4 or the new TRP 120-5 in the serving cluster may then send 232 a TRP modification update message to the distributed network device 110 to update the distributed network device 110.

[0082] Now refer to Figure 3 ,Should Figure 3 3 shows a signaling diagram 300 for communication according to some example embodiments of the present disclosure. Figure 3 As shown, the signaling diagram 300 involves the distributed network device 110, the terminal device 130 and the candidate TRP 120-1, the candidate TRP 120-4, the candidate TRP 120-5 or the candidate TRP 120-6, the TRP 120-1 in the updated service cluster that was already in the previous service cluster and the TRP 120-4 or TRP 120-5 that newly joins the updated service cluster. For the purpose of discussion, reference is made to Figure 1 3. Signaling diagram 300 is described below.

[0083] exist Figure 3 In the scenario of , TRP 120 - 1 may be referred to as an αTRP (Alpha TRP), which means that TRP 120 - 1 is allowed to send control information in the existing service cluster (before the update).

[0084] The process for forming a measurement cluster (determining a set of candidate TRPs) and an updated serving cluster (determining one or more target TRPs) (acts 302 to 316) is similar to the process for forming a measurement cluster (determining a set of candidate TRPs) and an updated serving cluster (determining one or more target TRPs). Figure 2 The described scenario is similar and is omitted here.

[0085] After determining one or more target TRPs, as an option, the distributed network device 110 can notify 318 TRP 120-1 (considered to be the αTRP) of the TRPs that need to be changed, for example, a new TRP (e.g., new TRP 120-4 or new TRP 120-5) requesting to join, and / or an old TRP (in the service cluster before the update) requesting to exit.

[0086] TRP 120-1 may then send 320 a TRP modification request to new TRP 120-4 or new TRP 120-5. TRP 120-4 or TRP 120-5 may respond 322 with a modification response to TRP 120-1.

[0087] As another option, the distributed network device 110 may notify 324 the TRP that needs to be changed (e.g., the new TRP 120-4 or the new TRP 120-5) of the TRP that needs to be changed, such as the new TRP (e.g., the new TRP 120-4 or the new TRP 120-5) that requested to join, and / or the old TRP (in the service cluster before the update) that requested to leave, as well as information of the αTRP (e.g., TRP 120-1). Then, TRP 120-4 or TRP 120-5 may send 326 a TRP modification request to TRP 120-1, and TRP 120-1 may respond 328 with a modification response to TRP 120-4 or TRP 120-5.

[0088] In this way, the distributed network device 110 can update the αTRP regarding the new TRP, and the αTRP can add the new TRP to the service cluster without involving the terminal device.

[0089] In some example embodiments, there may not be an αTRP in the updated service cluster. Figure 4 ,Should Figure 4 4 shows a signaling diagram 400 for communication according to some example embodiments of the present disclosure. Figure 4 As shown, the signaling diagram 400 involves the distributed network device 110, the terminal device 130, and the candidate TRP 120-1, the candidate TRP 120-4, the candidate TRP 120-5 or the candidate TRP 120-6 and the TRP 120-4 or TRP 120-5 newly added to the updated service cluster. For the purpose of discussion, reference is made to Figure 1 4. The signaling diagram 400 is described below.

[0090] The process for forming a measurement cluster (determining a set of candidate TRPs) and an updated serving cluster (determining one or more target TRPs) (acts 402 to 416) is similar to the process for forming a measurement cluster (determining a set of candidate TRPs) and an updated serving cluster (determining one or more target TRPs). Figure 2 The described scenario is similar and is omitted here.

[0091] In some example embodiments, after determining the one or more target TRPs, distributed network device 110 may update 418 the service cluster based on the one or more target TRPs.

[0092] Then, the distributed network device 110 may send 420 a TRP modification request indicating the TRP that needs to be changed (e.g., the new TRP 120-4 or the new TRP 120-5), for example, a new TRP (e.g., TRP 120-4 or TRP 120-5) requesting to join, and / or an old TRP (in the service cluster before the update) requesting to leave. The TRP 120-4 or TRP 120-5 may respond 422 with a TRP modification response to the distributed network device 110.

[0093] In this way, in the absence of an αTRP, the distributed network device 110 can add a new TRP to the service cluster and notify the new TRP of the modification without involving the end device.

[0094] The solution of the present disclosure is applicable to scenarios of NCJT, CJT, and dMIMO transmission at the PHY layer. The novel PHY layer and MAC layer of the proposed solution can be first noticed in the case of a service cluster update within the same cell. However, the proposed solution can also form the basis for later development into more complex scenarios (such as across different cells, DU or CU mobility).

[0095] Figure 5 A flowchart of an example method 500 for updating a service cluster according to some example embodiments of the present disclosure is shown. The method 500 may be implemented in a manner such as Figure 1 For the purpose of discussion, reference will be made to the distributed network device 110. Figure 1 Method 500 is described.

[0096] At 510 , the distributed network device 110 selects one or more target TRPs associated with an update of a serving cluster for a terminal device from a set of candidate TRPs based at least on a timing advance of the terminal device relative to a set of candidate transceiver points TRPs.

[0097] At 520 , distributed network device 110 sends information related to the update of the service cluster.

[0098] In some exemplary embodiments, the distributed network device may also send an indication of uplink resource allocation for the terminal device to the terminal device and a set of candidate TRPs.

[0099] In some example embodiments, the distributed network device may also receive information about the timing advance of the terminal device relative to the set of candidate TRPs from the set of candidate TRPs.

[0100] In some example embodiments, selecting the one or more target TRPs associated with the update of the service cluster includes selecting a first candidate TRP in a set of candidate TRPs as the one or more target TRPs if a timing advance of the first candidate TRP is determined to satisfy a threshold timing advance.

[0101] In some example embodiments, the distributed network device may also cause the second candidate TRP to not be selected as one or more target TRPs if it is determined that the timing advance of the second candidate TRP in a group of candidate TRPs does not satisfy a threshold timing advance; or if it is determined that the timing advance of the second candidate TRP in a group of candidate TRPs satisfies the threshold timing advance and the radio link quality of the second candidate TRP does not satisfy a threshold quality level; or if it is determined that the timing advance of the second candidate TRP in a subset of candidate TRPs satisfies the threshold timing advance and the load of the second candidate TRP does not satisfy a threshold load level.

[0102] In some example embodiments, the one or more target TRPs include at least one of the following: one or more existing TRPs already existing in the service cluster, or one or more new TRPs newly added to the service cluster.

[0103] In some example embodiments, sending information related to an update of a service cluster includes sending an activation command to one or more target TRPs, the activation command including at least one of: an RRC configuration of one or more new TRPs, an indication of a timing advance value for the service cluster, or an indication associated with a notification of an update of a media access control-control element from one or more existing TRPs or one or more new TRPs.

[0104] In some example embodiments, sending information related to an update of a service cluster includes sending information about at least one of the following to an existing TRP selected from one or more existing TRPs: one or more new TRPs that need to join the service cluster, or one or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

[0105] In some example embodiments, sending information related to an update of a service cluster includes sending information about at least one of the following to the TRP that needs to be changed: an existing TRP selected from one or more existing TRPs, one or more new TRPs that need to join the service cluster, or one or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

[0106] In some example embodiments, sending information related to an update of a service cluster includes sending a TRP modification request to the TRP that needs to be changed regarding at least one of: one or more new TRPs that need to join the service cluster, or one or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

[0107] In some example embodiments, the distributed network device may also receive a TRP modification response from the TRP that needs to be changed.

[0108] In some example embodiments, the distributed network device may also update information about the TRP in the service cluster of the terminal device after the service cluster is updated.

[0109] Figure 6 A flowchart of an example method 600 for updating a service cluster according to some example embodiments of the present disclosure is shown. The method 600 may be implemented in a manner such as Figure 1 For the purposes of this discussion, reference will be made to the TRP 120. Figure 1 Method 600 is described.

[0110] At 610, the TRP receives information related to an update of a service cluster for a terminal device from a distributed network node.

[0111] In some example embodiments, the one or more TRPs include at least one of the following: one or more existing TRPs already existing in the service cluster, or one or more new TRPs newly added to the service cluster.

[0112] In some example embodiments, the information relating to one or more TRPs includes: an activation command comprising at least one of: an RRC configuration of one or more new TRPs; an indication of a timing advance value for a service cluster, or at least one indication associated with a notification of an update of a media access control-control element from one or more existing TRPs or one or more new TRPs.

[0113] In some exemplary embodiments, the TRP may also send an indication to the terminal device for activating a new TRP at the terminal device.

[0114] In some example embodiments, the TRP may also receive a TRP modification request confirmation from the terminal device.

[0115] In some example embodiments, if the TRP includes an existing TRP selected from one or more existing TRPs, the information related to the one or more TRPs includes: one or more new TRPs that need to join the service cluster, or one or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

[0116] In some example embodiments, the TRP may also send a TRP modification request confirmation to one or more new TRPs; and receive a TRP modification response from one or more new TRPs.

[0117] In some example embodiments, if the TRP includes a TRP that needs to be changed, the information related to the one or more TRPs includes at least one of the following: an existing TRP selected from one or more existing TRPs, one or more new TRPs that need to join the service cluster, or one or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

[0118] In some example embodiments, the TRP that needs to be changed may also send a TRP modification request confirmation to the existing TRP; and receive a TRP modification response from the existing TRP.

[0119] In some example embodiments, if the TRP includes a TRP that needs to be changed, the information related to one or more TRPs includes: a TRP modification request indicating at least one of the following: one or more new TRPs that need to join the service cluster, or one or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

[0120] In some example embodiments, the TRP that needs to be changed may also send a TRP modification response to the distributed network node.

[0121] Figure 7 A flowchart of an example method 700 for updating a service cluster according to some example embodiments of the present disclosure is shown. The method 700 may be implemented in a manner such as Figure 1 For the purposes of this discussion, reference will be made to the TRP 120. Figure 1 Method 700 is described.

[0122] At 710, the TRP determines a timing advance of the terminal device relative to the TRP based on an uplink resource allocation for the terminal device and an uplink signal received from the terminal device.

[0123] At 720, the TRP sends information about the timing advance to the distributed network nodes.

[0124] In some example embodiments, the uplink signal is received via at least one of a random access message, a sounding reference signal, or a common uplink resource based on an uplink resource allocation.

[0125] Figure 8 A flowchart of an example method 800 for updating a service cluster according to some example embodiments of the present disclosure is shown. The method 800 may be implemented in a manner such as Figure 1 For the purpose of discussion, reference will be made to the terminal device 130. Figure 1Method 800 is described.

[0126] At 810 , a terminal device receives an indication of an uplink resource allocation for the terminal device from a distributed network device.

[0127] At 820, the terminal device sends an uplink signal to a set of candidate TRPs.

[0128] In some example embodiments, the uplink signal is transmitted via at least one of a random access message, a sounding reference signal, or a common uplink resource based on an uplink resource allocation.

[0129] In some exemplary embodiments, the terminal device 130 may also receive an indication for activating a new TRP at the terminal device from the new TRP joined in association with the update of the terminal device's service cluster.

[0130] In some example embodiments, the indication also includes the timing advance of the terminal device relative to the new TRP and the configuration of the new TRP.

[0131] In some exemplary embodiments, the terminal device 130 may also send a TRP modification request confirmation to an existing TRP and / or a new TRP already existing in the service cluster.

[0132] In some example embodiments, an apparatus capable of performing method 500 (e.g., implemented at distributed network device 110) may include components for performing the corresponding steps of method 500. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0133] In some example embodiments, the apparatus includes: a component for selecting one or more target TRPs associated with an update of a service cluster for a terminal device from a set of candidate TRPs based at least on a timing advance of the terminal device relative to the set of candidate TRPs; and a component for sending information related to the update of the service cluster.

[0134] In some example embodiments, an apparatus capable of performing method 600 (e.g., implemented at TRP 120) may include components for performing the corresponding steps of method 600. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0135] In some example embodiments, the apparatus comprises means for receiving, from a distributed network node, information relating to one or more apparatuses associated with an update of a service cluster of terminal devices.

[0136] In some example embodiments, an apparatus capable of performing method 700 (e.g., implemented at TRP 120) may include components for performing the corresponding steps of method 700. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0137] In some example embodiments, the apparatus comprises: a component for determining a timing advance of the terminal device relative to the apparatus based on an uplink resource allocation for the terminal device and an uplink signal received from the terminal device; and a component for sending information about the timing advance to a distributed network node.

[0138] In some example embodiments, an apparatus capable of performing method 800 (e.g., implemented at terminal device 130) may include components for performing the corresponding steps of method 800. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0139] In some example embodiments, the apparatus includes: means for receiving an indication of an uplink resource allocation for the apparatus from a distributed network device; and means for sending an uplink signal to a set of candidate TRPs.

[0140] Figure 9 is a simplified block diagram of a device 900 suitable for implementing an example embodiment of the present disclosure. The device 900 may be provided to implement a communication device, such as Figure 1 The distributed network device 110, TRP 120 or terminal device 130 is shown. As shown in the figure, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processor 910, and one or more communication modules 940 coupled to the processor 910.

[0141] The communication module 940 is configured for bidirectional communication. The communication module 940 has one or more communication interfaces to facilitate communication with one or more other modules or devices. A communication interface may represent any interface necessary for communicating with other network elements. In some example embodiments, the communication module 940 may include at least one antenna.

[0142] Processor 910 may be of any type suitable for the local technology network and may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples. Device 900 may have multiple processors, such as application specific integrated circuit chips, that are time-slave to a clock synchronized with a main processor.

[0143] The memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 924, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact discs (CDs), digital video discs (DVDs), optical discs, laser discs, and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 922 and other volatile memories that will not persist until power is removed.

[0144] The computer program 930 includes computer-executable instructions executed by the associated processor 910. The instructions of the program 930 may include instructions for performing the operations / actions of some example embodiments of the present disclosure. The program 930 may be stored in a memory (e.g., ROM 924). The processor 1210 may perform any suitable actions and processes by loading the program 930 into the RAM 922.

[0145] The exemplary embodiments of the present disclosure may be implemented by the program 930 so that the device 900 may execute the following steps: Figures 2 to 8 Any process of the present disclosure discussed. The exemplary embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0146] In some example embodiments, the program 930 may be tangibly embodied in a computer-readable medium that may be included in the device 900 (such as in the memory 920) or in another storage device accessible by the device 900. The device 900 may load the program 930 from the computer-readable medium into the RAM 922 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transitory" as used herein refers to the limitation of the medium itself (i.e., tangible, not a signal), not to the limitation on the persistence of data storage (e.g., RAM versus ROM).

[0147] Figure 10 An example of a computer readable medium 1000 is shown, which may be in the form of a CD, DVD, or other optical storage disc.The computer readable medium 900 has a program 930 stored thereon.

[0148] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0149] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer-readable medium (such as a non-volatile computer-readable medium). The computer program product includes computer-executable instructions, such as those included in a program module, that are executed in a device on a target entity or virtual processor to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of the program modules can be combined or split between program modules as needed in various embodiments. The machine-executable instructions for the program modules can be executed in a local or distributed device. In a distributed device, the program modules can be located in local and remote storage media.

[0150] The program code for performing the method of the present disclosure can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that the program code, when executed by the processor or controller, causes the implementation of the functions / operations specified in the flow chart and / or block diagram. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0151] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer-readable media, etc.

[0152] The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include an electrical connection with one or more wires, a portable computer disk, 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.

[0153] In addition, although 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 described operations be performed, to achieve the desired result. In some cases, multitasking and parallel processing can be advantageous. Similarly, although several specific implementation details have been included in the above discussion, these should not be interpreted as limiting the scope of this disclosure, but rather as describing features that may be specific to a particular embodiment. Unless explicitly stated, certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, unless explicitly stated, various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination.

[0154] Although the disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the 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.

Claims

1. A distributed network node, comprising: at least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the distributed network node to at least perform: selecting, based at least on a timing advance of the terminal device relative to a set of candidate transceiver points (TRPs), one or more target TRPs associated with an update of a serving cluster for the terminal device from the set of candidate TRPs; as well as Information related to the update of the service cluster is sent.

2. The distributed network node of claim 1 , wherein the distributed network node is further configured to: An indication of uplink resource allocation for the terminal device is sent to the terminal device and the set of candidate TRPs.

3. The distributed network node of claim 1 , wherein the distributed network node is further configured to: Information regarding a timing advance of the terminal device relative to the set of candidate TRPs is received from the set of candidate TRPs.

4. The distributed network node of claim 1 , wherein selecting the one or more target TRPs associated with the update of the service cluster comprises: If it is determined that the timing advance of the first candidate TRP in the group of candidate TRPs meets the threshold timing advance, the first candidate TRP is selected as the one or more target TRPs.

5. The distributed network node of claim 1 , wherein the distributed network node is further configured to: If it is determined that the timing advance of the second candidate TRP in the set of candidate TRPs does not meet the threshold timing advance; or If it is determined that the timing advance of a second candidate TRP in the set of candidate TRPs satisfies the threshold timing advance and the radio link quality of the second candidate TRP does not satisfy the threshold quality level; or If it is determined that the timing advance of a second candidate TRP in the candidate TRP subgroup satisfies the threshold timing advance and the load of the second candidate TRP does not satisfy the threshold load level, the second candidate TRP is not selected as the one or more target TRPs.

6. The distributed network node according to any one of claims 1 to 5, wherein the one or more target TRPs include at least one of the following: One or more existing TRPs already in the service cluster, or One or more new TRPs newly added to the service cluster.

7. The distributed network node of claim 6, wherein sending the information related to the update of the service cluster comprises: Sending an activation command to the one or more target TRPs, the activation command including at least one of the following: The RRC configuration of the one or more new TRPs. an indication of a timing advance value for the serving cluster, or An indication associated with a notification of an update of a media access control-control element from the one or more existing TRPs or the one or more new TRPs.

8. The distributed network node of claim 6, wherein sending the information related to the update of the service cluster comprises: Sending information regarding at least one of the following to an existing TRP selected from the one or more existing TRPs: One or more new TRPs that need to join the service cluster, or One or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

9. The distributed network node of claim 6, wherein sending the information related to the update of the service cluster comprises: Send information to the TRP that needs to be changed regarding at least one of the following: an existing TRP selected from said one or more existing TRPs, One or more new TRPs that need to join the service cluster, or One or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

10. The distributed network node of claim 6, wherein sending the information related to the update of the service cluster comprises: Send a TRP modification request to the TRP that needs to be changed regarding at least one of the following: One or more new TRPs that need to join the service cluster, or One or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

11. The distributed network node according to claim 10, wherein the distributed network node is further configured to: A TRP modification response is received from the TRP that needs to be changed.

12. The distributed network node of claim 1 , wherein the distributed network node is further configured to: After the updating of the service cluster, information about the TRP in the service cluster of the terminal device is updated.

13. A transceiver point TRP, comprising: at least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the TRP to at least perform: Information related to an update of a service cluster for a terminal device is received from a distributed network node.

14. The TRP of claim 13, wherein the one or more TRPs include at least one of: One or more existing TRPs already in the service cluster, or One or more new TRPs newly added to the service cluster.

15. The TRP of claim 14, wherein the information related to one or more TRPs comprises: Activation command, including at least one of the following: The RRC configuration of the one or more new TRPs. an indication of a timing advance value for the serving cluster, or An indication associated with a notification of an update of a media access control-control element from the one or more existing TRPs or the one or more new TRPs.

16. The TRP of claim 14, wherein the TRP is further caused to perform: An indication is sent to the terminal device for activating the new TRP at the terminal device.

17. The TRP of claim 16, wherein the TRP is further caused to perform: A TRP modification request confirmation is received from the terminal device.

18. The TRP of claim 14, wherein the TRP comprises an existing TRP selected from the one or more existing TRPs, and wherein the information related to the one or more TRPs comprises: One or more new TRPs that need to join the service cluster, or One or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

19. The TRP of claim 18, wherein the existing TRP is further caused to perform: sending a TRP modification request confirmation to the one or more new TRPs; and A TRP modification response is received from the one or more new TRPs.

20. The TRP of claim 14, wherein the TRP includes a TRP that needs to be changed, and wherein the information related to the one or more TRPs includes at least one of the following: an existing TRP selected from said one or more existing TRPs, One or more new TRPs that need to join the service cluster, or One or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

21. The TRP of claim 20, wherein the TRP that requires change is further caused to perform: Sending a TRP modification request confirmation to the existing TRP; and A TRP modification response is received from the existing TRP.

22. The TRP of claim 14, wherein the TRP includes a TRP that requires change, and wherein the information related to the one or more TRPs includes: TRP modification request indicating at least one of the following: One or more new TRPs that need to join the service cluster, or One or more existing TRPs that were previously in the service cluster and need to exit the service cluster.

23. The TRP of claim 22, wherein the TRP that requires change is further caused to perform: Sending a TRP modification response to the distributed network node.

24. A transceiver point TRP, comprising: at least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the TRP to at least perform: determining a timing advance of a terminal device relative to the TRP based on an uplink resource allocation for the terminal device and an uplink signal received from the terminal device; and Information about the timing advance is sent to a distributed network node.

25. The TPR of claim 24, wherein the uplink signal is received via at least one of a random access message, a sounding reference signal, or a common uplink resource based on the uplink resource allocation.

26. A terminal device comprising: at least one processor; as well as At least one memory stores instructions, which, when executed by the at least one processor, cause the terminal device to at least perform: receiving, from a distributed network device, an indication of an uplink resource allocation for the terminal device; as well as An uplink signal is sent to a set of candidate transceiver points TRP.

27. The terminal device of claim 26, wherein the uplink signal is transmitted via at least one of a random access message, a sounding reference signal, or a common uplink resource based on the uplink resource allocation.

28. The terminal device according to claim 26, wherein the terminal device is further configured to perform: An indication for activating the new TRP at the terminal device is received from the new TRP joined in association with the update of the service cluster of the terminal device.

29. The terminal device of claim 28, wherein the indication further comprises a timing advance of the terminal device relative to the new TRP and a configuration of the new TRP.

30. The terminal device according to claim 28, wherein the terminal device is further configured to perform: Send a TRP modification request confirmation to the existing TRP and / or the new TRP already existing in the service cluster.

31. A method comprising: selecting, by the distributed network node, one or more target TRPs associated with an update of a serving cluster for the terminal device from the set of candidate TRPs based at least on a timing advance of the terminal device relative to the set of candidate TRPs; as well as Information related to the update of the service cluster is sent.

32. A method comprising: Information regarding one or more target TRPs associated with an update of a service cluster for a terminal device is received at the TRP from the distributed network node.

33. A method comprising: determining, at a TRP, a timing advance of a terminal device relative to the TRP based on an uplink resource allocation for the terminal device and an uplink signal received from the terminal device; as well as Information about the timing advance is sent to a distributed network node.

34. A method comprising: receiving, at a terminal device, from a distributed network device, an indication of an uplink resource allocation for the terminal device; as well as An uplink signal is sent to a set of candidate transceiver points TRP.

35. An apparatus comprising: means for selecting one or more target TRPs associated with an update of a serving cluster for a terminal device from a set of candidate transceiver points TRPs based at least on a timing advance of the terminal device relative to the set of candidate TRPs; as well as Means for sending information related to said updating of the service cluster.

36. An apparatus comprising: Means for receiving, from a distributed network node, information regarding one or more devices associated with an update of a service cluster of terminal devices.

37. An apparatus comprising: means for determining a timing advance of a terminal device relative to the apparatus based on an uplink resource allocation for the terminal device and an uplink signal received from the terminal device; as well as Means for sending information about said timing advance to distributed network nodes.

38. An apparatus comprising: means for receiving an indication of an uplink resource allocation for the apparatus from a distributed network device; as well as A component for sending uplink signals to a set of candidate transceiver points TRP.

39. A non-transitory computer-readable medium comprising program instructions for causing an apparatus to at least perform the method of claim 31, the method of claim 32, the method of claim 33, or the method of claim 34.

Images