Collaborative configuration authorization for packet data convergence protocol replication

Abstract

Techniques described herein are directed to collaborative configuration grant with respect to configuration grant slots for multiple cells, in particular to ultra-reliable low latency communications (URLLC) devices configured for replicating packet data convergence protocol (PDCP) for packet communications. The selection of time slots is delay aware with respect to PDCP communications. For replication communications between a user equipment communicating with a first cell and a second cell for PDCP replication by selecting a configured grant physical resource block (PRB) slot of a first serving cell to temporally align it with a configured grant PRB slot of the second cell, an end-to-end PDCP delay for PDCP communication when a user equipment performs PDCP replication with a first cell and a second cell can be reduced. Multiple UEs may be prioritized with respect to slot allocations based on their current condition data. It is also described herein that the controller proposes different configurations of the configuration authorization slots that the controller may use if the configuration is accepted by the deciding entity.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. non-provisional patent application No. 18 / 047,464 filed on October 18, 2022, and entitled “Collaborative Configuration Authorization for Packet Data Convergence Protocol Replication,” the entire contents of which are incorporated herein by reference. Background Art

[0003] Ultra-Reliable Low Latency Communication (URLLC) traffic has stringent Quality of Service (QoS) requirements, including short end-to-end delay and low packet error rate. For example, short end-to-end delay can be achieved through proactive resource allocation such as Configuration Grant (CG), and low packet error rate can be achieved through Packet Data Convergence Protocol (PDCP) replication.

[0004] Generally speaking, a configuration grant allocates a certain number of physical resource blocks (PRBs), which can be used regularly by user equipment (UE), user terminals, mobile devices, etc. for uplink data communication, that is, the device can actively transmit information in a predetermined time slot. Compared with traditional grant-based allocation, this method reduces the data transmission delay for URLLC traffic. In traditional grant-based allocation, the network first obtains a scheduling request indicating that the user has data to transmit, then sends a control signal authorizing resources for uplink data transmission, and finally receives uplink data transmission from the UE.

[0005] In some use cases where data integrity needs to be ensured, PDCP duplication can be used to add more redundancy to packets in transit. In this case, the UE is connected to multiple cells simultaneously. This consumes more energy because the UE needs to wake up for each communication of the same packet.

[0006] Generally, configuration grants and PDCP duplicate resources are statically and manually configured by the service operator at the cell level, which often results in inefficient use of spectrum and / or high energy consumption of the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The technology described herein is illustrated by way of example but not limited to the accompanying drawings, in which like reference numerals indicate similar elements, as follows:

[0008] Figure 1 is a block diagram representing a system / architecture of example components by which configuration granted time slots are selected for user equipment configured for Packet Data Convergence Protocol (PDCP) duplication in accordance with various aspects and implementations of the present disclosure.

[0009] Figure 2AIt is an example according to various aspects and implementations of the present disclosure that a user equipment uses configured granted resources to reduce latency while being connected to two cells for PDCP duplication to improve reliability.

[0010] Figure 2B is an example flow chart illustrating a method for neighbor cells to collaborate in aligning physical resource blocks and time slots in configuring grants in accordance with various aspects and implementations of the present disclosure.

[0011] Figure 3 is an example showing two cells transmitting PDCP duplicate packets in consecutive configured grant time slots before a user equipment times out according to various aspects and implementations of the present disclosure.

[0012] Figure 4 is an example showing two cells transmitting PDCP duplicate packets in selected configured grant time slots based on saving user equipment energy according to various aspects and implementations of the present disclosure.

[0013] Figure 5 is an example flow chart illustrating example operations associated with controller logic assigning configuration authorizations to user devices based on user condition data in accordance with various aspects and implementations of the present disclosure.

[0014] Figure 6 is an example data structure for configuring grant slot selection based on user equipment priority data in accordance with various aspects and implementations of the present disclosure.

[0015] Figure 7 is an example signaling and data flow diagram representation of a controller selecting a configuration grant time slot without changing the physical resource blocks of the configuration grant in accordance with various aspects and implementations of the present disclosure.

[0016] Figure 8 is an example data structure of default configured authorized time slots and proposed configured authorized time slots based on energy and delay aware logic in accordance with various aspects and implementations of the present disclosure.

[0017] Fig. 9 is an example signaling and data flow diagram representation of a controller recommending new physical resource blocks (PRBs) for configuring a granted time slot in accordance with various aspects and implementations of the present disclosure.

[0018] Fig.10 is an example flow chart illustrating selection of PRB time slot data from a cell's configuration grant to reduce end-to-end delay of PDCP duplicate communications in accordance with various aspects and implementations of the present disclosure.

[0019] Fig.11 is an example flow chart illustrating example operations associated with selecting a subset of preset configured grants from a cell reserved PRB adjacent slots for allocation to a user equipment in accordance with various aspects and implementations of the present disclosure.

[0020] Fig.12 is an example flow chart illustrating example operations related to selecting a neighboring configuration grant PRB slot of a cell for allocation to a user equipment in accordance with various aspects and implementations of the present disclosure.

[0021] Fig.13 is a block diagram representing an example computing environment in which examples of various aspects of the subject matter described herein may be incorporated.

[0022] Fig.14

[0013] In accordance with various aspects and implementations of the present disclosure, an example schematic block diagram of a computing environment that can interact / implement at least in part with the subject matter described herein is depicted. DETAILED DESCRIPTION

[0023] Aspects of the techniques described herein are generally directed to collaborative configuration grants between multiple neighboring cells serving the same user equipment (UE), user devices, mobile devices, etc. using packet copies replicated using the Packet Data Convergence Protocol (PDCP). Typically, and as will be appreciated, configuration grants between neighboring cells are coordinated based on delay-aware slot selection to align configuration grant slots on a time offset between the original packet version and (multiple) packet copies. Among the benefits, the techniques described herein reduce the UE's discontinuous reception (DRX) on / connection duration while also avoiding packet reassembly timeouts. Thus, the techniques are beneficial in many situations, including for ultra-reliable, low-latency communications (URLLC) device data services.

[0024] It should be understood that any implementation herein is non-limiting. Therefore, any of the implementations, aspects, concepts, structures, functionalities, or examples described herein are non-limiting, and the techniques may be used in various ways that provide benefits and advantages in communications and computing in general. It should also be noted that the terms used herein, such as "optimization" or "optimal", etc. (e.g., "maximize", "minimize", etc.) only indicate that the goal is to move to a more optimal state, rather than necessarily obtaining an ideal result.

[0025] References throughout this specification to "one embodiment," "an embodiment," "an implementation," "implementation," etc. mean that a particular feature, structure, or characteristic described in connection with that implementation is included in at least one implementation. Thus, appearances of the phrases "in one implementation," "in an implementation," etc., throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0026] Various aspects of the present disclosure will now be described more fully below with reference to the accompanying drawings, in which example components, diagrams and / or operations are shown. In the following description, for the purpose of explanation, many specific details are set forth in order to provide a thorough understanding of various implementations. However, the present disclosure can be implemented in many different forms and should not be construed as being limited to the examples set forth herein.

[0027] Figure 1 A system / architecture 100 is shown that includes a controller component 102, which includes various logical components 104-106, by which the UE periodically uses the configuration grant (CG) physical resource blocks (PRBs) to transmit uplink data. In addition, PDCP duplication (corresponding to block 105) can be employed to add more redundancy to the transmitted packets; in this case, the UE is connected to multiple cells at the same time.

[0028] In general, it should be noted that there are many tradeoffs for configuration grants (CGs) and PDCP duplication. Configuration grants help reduce latency; (in practice, configuring contiguous resources to the UE will result in minimal latency and energy usage, since the UE only enters the DRX on state when transmitting); however, if there is overlap (in time) with the neighbor's signal, the data is subject to high interference. On the other hand, if the data requires multiple time slots to be scheduled, the fragmented resource allocation to achieve diversity will result in high energy consumption and potentially large delays at the UE. In addition, configuring too many configuration grant resources (e.g., for URLLC users) will reduce the number of resources that can be allocated to other users (e.g., users that do not have configuration grant needs, such as mobile broadband users), thereby degrading spectral efficiency.

[0029] In addition, in some (e.g., critical) use cases where data integrity needs to be ensured, PDCP replication using multiple cells can be employed to add more redundancy to the transmitted packets. In this case, the UE is connected to multiple cells simultaneously and therefore consumes more energy, which adversely affects the UE battery life because the UE must wake up and process multiple transmissions of the same packet, including the UE remaining on for a longer time while waiting for redundant packets to arrive. There are also problems such as the UE receiving a packet but timing out (and thus sending a negative acknowledgment or NACK) before receiving another redundant packet. There are also challenges associated with configuring grants, where resources are pre-allocated to minimize latency, but can only be adjusted with signaling overhead. The techniques described herein take these trade-offs into account.

[0030] Back to Figure 1As will be appreciated, the controller component 102 evaluates (block 104) current UE condition data, including its capability data. In general, the UE capability and channel assessment logic 104 detects user equipment devices that support and comply with the configured authorization features, as well as any PDCP duplication requirements. In one implementation, the UE capability and channel assessment logic 104 also evaluates user channel conditions and connectivity status. The PDCP duplication requirement logic 105 collects manually configured authorized time slots and determines the time offset between the primary cell group (MCG) / secondary cell group (SCG) time slots. Multi-cell configuration authorization (CG) optimization (block 106) includes logic for selecting configuration authorization time slots after alignment between multiple cells, and as described herein, time slot recommendations may also be issued to the RAN node (network DU / CU element) 108.

[0031] More specifically, Figure 1 The example system of shows a controller 102 coupled to three cells (cell 1-cell 3) via an E2 interface (e.g., in an O-RAN compatible scenario), each cell including a corresponding distributed unit 110(1)-110(3) and a centralized unit 112(1)-112(3). It should be understood that although only three DU / CU network elements are shown in this simplified example, it should be understood that the controller can be coupled to any practical number of elements.

[0032] In one implementation where the system is O-RAN compliant, the controller is coupled via an O1 interface to a service management and orchestration (SMO) 114, which handles the orchestration, management, and automation aspects of the RAN elements. Figure 1 Also shown as part of the controller is an interface processor 116 that allows the controller to receive data from the collaboration unit and a data store (e.g., a database) for storing data received through the interface. The data maintained may include key performance indicators and allocation data related to the previous window.

[0033] Generally, the techniques described herein can be implemented in a distributed manner using a near real-time RI (Radio Access Network Intelligent Controller) and distributed units. To this end, the near real-time RIC subscribes to the configuration authorization data and PDCP data provided by (multiple) DUs and SMO 114, and aligns the time slots accordingly.

[0034] Figure 1Also shown are user equipment (UE) devices 120(1)-120(n) communicating via the RAN node 108. Such UE devices 120(1)-120(n) may be one of any number of (e.g., URLLC) devices, including but not limited to medical-related devices, vehicles, sensors, small measurement devices, etc., which may move at relatively high speeds, such as on a drone, mobile robot, etc.

[0035] Figure 2A An example of a URLLC UE 220 is shown that uses configured granted resources (to minimize latency) and is simultaneously connected to cell 1 222(1) and cell 2 222(2) for PDCP duplication (to increase reliability). Although the arrows indicate uplink communications, PDCP duplication can increase the reliability of downlink communications, including as described herein. Figure 3 as described.

[0036] like Figure 2B In summary, this paper describes a collaborative approach where neighbor cells can be aligned on PRBs and time slots for configuration grants (CGs) to achieve space and time diversity when a user is simultaneously connected to multiple cells (e.g., primary cell group (MCG) and secondary cell group (SCG) dual connectivity). This is generally Figure 2B , and achieves higher reliability without violating the packet delay budget, as shown in FIG. Figure 3 In addition, the techniques described herein operate to reduce (e.g., minimize) device energy consumption, wherein users connected to multiple cells try to complete their UL data transmissions in a common DRX ON (DRXON) window and then switch to a DRX OFF (DRX OFF) state to achieve minimum power consumption, as described in reference Figure 4 Generally described.

[0037] In one embodiment, the coordination and multi-cell alignment between neighbor cells takes into account the target packet delay of URLLC services, including by prioritizing (multiple) user equipment devices that need more configuration grant resources under poor radio conditions rather than other neighbor user equipment devices whose data has a higher chance of successful reception in the first transmission attempt. This is based on UE condition data (e.g., capabilities, channel conditions, and energy levels), such as Figure 2B As shown in box 234 in.

[0038] For backward compatibility (manual resource configuration by the service operator), the multi-cell time slot alignment logic 106 ( Figure 1) can prioritize UEs with limited configuration authorization resources or poor radio conditions. Therefore, the technology described herein is used to achieve fairness in energy consumption and packet delay. This is achieved through coordination between the controller 102 hosting the logic and the network management system (e.g., SMO 114) hosting the manual configuration.

[0039] Figure 2B Block 236 of aligns the MCG / SCG time slots across multiple cells. Typically, and as described herein, this includes making the time offset shorter to allow the UE to have a smaller DRX on window, thereby saving energy. The operator-defined resources may be reconfigured (block 238), as described in reference to . Figure 8 and 9 as described.

[0040] Figure 3 A UE 320 is shown with a configuration grant that is aligned in such a way that both cells 321(1) and 322(2) transmit in consecutive time slots (e.g., five transmission time intervals, or 5 TTIs apart), ensuring that the UE 320 typically receives the transmitted data from both cells 321(1) and 322(2) for packet-based reassembly before timeout. The added redundancy provides greater robustness to ensure packet reception. Note that, in contrast, current methods of allocating configuration grant resources rely on manual and static configuration, where the operator performs an offline estimation of the URLLC traffic load and manually sets the resources dedicated to the configuration grant. Such resources are statically configured and therefore do not reflect the time-varying requirements of the URLLC traffic and channel conditions. In addition, the operator only considers the configuration of each cell, where pre-configured resources are selected separately for each cell, which is generally suboptimal for multi-cell scenarios. Currently, PDCP duplication occurs when each cell individually applies a time slot for the UE for monitoring, however this approach is flawed because each cell is unaware of the existence of the other cell, which may negatively impact the UE's experience. For example, if the time slots are too far apart, the UE may time out before receiving both packets, resulting in unnecessary upper layer retransmissions and delays for the UE. In fact, if the two cells' configured grants for a single UE are not closely aligned, the UE will time out after receiving a packet from cell 1 and send a NACK before receiving the redundant packet from cell 2.

[0041] exist Figure 4Another benefit of the techniques described herein is illustrated in , where the DRX on state is relatively short due to transmissions via aligned proximate (e.g., adjacent or very close) time slots. When the configuration grants cooperate as described herein, the UE's idle time can be more optimized to save battery life because the UE remains in the on state for shorter durations. This is in contrast to the limitations of existing methods, in which the time slots of multiple serving cells may be too far apart, causing the UE to remain in the DRX on state for longer periods of time, resulting in greater power consumption; that is, since the UE remains in the DRX on state for a longer duration while waiting for the arrival of (multiple) redundant packets from cell 2, relatively widely spaced time slots may adversely affect the UE battery life.

[0042] Figure 5 Example operations that a controller may perform for collaborative configuration authorization are shown. At operation 502, the controller receives from the scheduler an input list of condition data to be processed for each UE, which may include, but is not limited to, a UE capability list (capability data), PDCP delay / packet delay data, buffer status data (how much the user has in the uplink buffer), channel condition data (e.g., physical uplink shared channel or PUSCH SINR / RSRP, or signal to interference and noise ratio / reference signal received power), block error rate data, power headroom / UE energy level data, and automatic neighbor relation (ANR) data (primary cell group / secondary cell group information).

[0043] Using this data, as shown in operation 504, the controller identifies which UEs meet the conditions for configuration authorization, that is, the controller identifies user equipment that supports configuration authorization and user equipment that requires configuration authorization.

[0044] The controller also retrieves (operation 506) cell data containing PRB usage data, including the operator's manual configuration for each cell (initial configuration grant slots). Once eligible / supported user equipment has been indicated, the PRBs allocated for the configuration grant for each cell are extracted based on signals provided to the controller by the distributed unit, or the operator manual configuration (stored at the SMO).

[0045] Based on the information obtained by the controller, the controller sorts the UEs based on priority for allocation of the configuration grant, as represented by operations 508 and 510. To this end, using the input data provided, the controller identifies the users that support the configuration grant and screens the users that will benefit the most from the configuration grant, such as users with poor radio conditions (low PUSCH SINR), users that support dual connectivity and PDCP duplication (retrieved from the capability list), users with low power headroom / energy level data (periodically reported by the UE as part of the control data), and / or large packet delay data (identified from the buffer status report in the uplink).

[0046] The controller checks if the UE is ranked based on the previous configuration to ensure that users with high priority will get the pre-configured granted resources in case of resource congestion. Regarding ranking, the controller ranks the UEs to optimize based on priority, where the priority is based on "degrees of freedom" corresponding to the number of different configured grant timeslots that the UE can access, which correspond to the QoS requirements of the PDCP replication of the UE.

[0047] exist Figure 6 In the example shown in the cell 1-cell 4 timeslot configuration 660, the configuration grant timeslot is identified by a "1" in the available configuration timeslots (as opposed to a "0" indicating that the timeslot is not a configuration grant timeslot). As shown by the shaded blocks, UE1 has two degrees of freedom (i.e., time slot pairs of two cells adjacent in time) that can meet the QoS requirements of UE1. The circled timeslots can be used as configuration timeslots, but will not meet the QoS requirements of UE1 regarding PDCP duplication. Figure 6 It can also be seen that UE2 has four degrees of freedom (ie, four pairs of adjacent CG time slots that can meet the QoS requirements of UE2). Therefore, due to having fewer degrees of freedom, UE1 has a higher priority than UE2.

[0048] The QoS requirements for the UE include the end-to-end PDCP delay, which is based on how far the timeslots from each cell are from each other, i.e. the controller takes into account the MCG / SCG delay in timeslot selection. Figure 6 In the example of , the time slots are adjacent to each other, however it will be appreciated that for a given UE, the QoS requirements may be less stringent and the time slots may be adjacent to each other (relatively closely aligned) without necessarily being adjacent to each other.

[0049] return Figure 5 Once the selected UEs are sorted based on priority, operation 512 checks to determine if they are assigned CG time slots. If so, operation 512 returns to operation 502 to continue the operation of the new iteration.

[0050] If one or more UEs remain unallocated, operation 512 branches to operation 514 to check whether the primary cell group / secondary cell group time slot delay is within a certain defined range, for example, a delay parameter represented by less than or equal to x. If the time slot MCG / SCG delay of the unallocated UE is within the specified range, then via operation 516 (returning to operation 512), the time slot is allocated to each UE.

[0051] If it is considered that the operator manual configuration cannot meet the requirements of the UE, the controller attempts to modify the PRB and configure the authorized reserved time slots to reduce (e.g., minimize) the UE packet delay. To this end, if the time slot MCG / SCG delay of any unassigned UE is still outside the specified range, operation 518 reorganizes the configuration of the authorized PRB time slots for the cell to minimize the delay.

[0052] Therefore, the controller 102 ( Figure 1 ) attempts to override the default configuration of the configuration grant for the cell and sends an update to the SMO 114 to define the new proposed configuration grant time slot. The SMO 114 can confirm or reject the proposed configuration grant time slot (or possibly send a different set). In the case of rejection, the controller reverts the configuration back to / maintains the previous configuration.

[0053] Figure 7 711 is an example signaling / data flow diagram in which the controller 102 selects a timeslot for a configuration grant for the UE 720 (without attempting to change the PRB used for the configuration grant). The DU / CU (block 711) obtains the manually set PRB utilization for the configuration grant (the controller also receives the PRB utilization information via Figure 5 Operation 506 obtains).

[0054] As described herein, UE 720 sends its condition / capability data to DU / CU 711, which forwards the data to controller logic 102, e.g. Figure 1 Based on the data, the controller 102 selects a configuration grant time slot for the UE 720 and sends it to the DU / CU 711, which in turn sets the configuration grant time slot with the UE 720.

[0055] Figure 8 The controller determines the proposed configuration authorization time slot through the controller, where (eg Figure 6 102. The controller 102 overrides the default 880 configuration of the configuration grant for the cell and sends an update to the SMO 114 to define the new proposed configuration grant time slot configuration 882. The SMO 114 can confirm or reject the proposed configuration grant time slot. In the case of rejection, the controller will restore the configuration.

[0056] Fig. 9 is an example signaling / data flow diagram in which the controller 102 recommends a new PRB for configuring a grant slot. Figure 7 As shown, the default available CG time slot is known to the controller and the UE 920 sends / the controller obtains (from the DU / CU) 711 UE condition / capability data. Figure 7 Unlike the example Fig. 9 In the example, the controller 102 does not choose to use the default time slot, but instead sends a request change to the configuration grant (CG) time slot to the DU / CU 711, receives the updated time slot data, and sends a suggested CG time slot to the DU / CU 711 for setting up with the UE 920. Note that although not in Fig. 9 It is explicitly shown in FIG, but it should be understood that the SMO 114 coupled to the DU / CU 711 may be part of the decision as to whether to accept or reject the proposed time slot, i.e., the decision entity may be the DU / CU, the SMO, or a combination of both.

[0057] One or more aspects may be embodied in, for example, Fig.10 The example operation may include an operation 1002, which indicates obtaining condition data indicating a condition of a user equipment. The example operation 1004 indicates determining, based on the condition data, that the user equipment meets the condition of a preset configuration authorization. The example operation 1006 indicates obtaining first configuration authorization physical resource block time slot data indicating a first time slot for a first cell, and obtaining second configuration authorization physical resource block time slot data indicating a second time slot for a second cell. The example operation 1008 indicates selecting from the first configuration authorization physical resource block time slot data and the second configuration authorization physical resource block time slot data in a time-aligned manner to allocate a first subgroup of the first time slot of the first configuration authorization physical resource block time slot data, and allocate a second subgroup of the second time slot of the second configuration authorization physical resource block time slot data, the time alignment being determined to reduce an end-to-end packet data convergence protocol delay for duplicate communications between the first cell and the user equipment and between the second cell and the user equipment. Note that a subgroup may be a single time slot among those available time slots.

[0058] The time alignment may correspond to a first time slot of the first subset being adjacent to a second time slot of the second subset.

[0059] Selecting from the first configured authorized physical resource block time slot data and the second configured authorized physical resource block time slot data may also include: selecting the first configured authorized physical resource block time slot data and the second configured authorized physical resource block time slot data that have been determined to save energy of the user equipment according to the energy saving function.

[0060] The condition data may include at least one of the following: user equipment capability data indicating capabilities of the user equipment, radio condition data indicating radio conditions of a radio associated with the user equipment, packet data convergence protocol delay data indicating packet data convergence protocol delay associated with the user equipment, packet delay data indicating packet delay associated with the user equipment, buffer status data indicating a status of a buffer of the user equipment, channel condition data indicating channel conditions of a channel associated with the user equipment, block error rate data indicating a block error rate applicable to transmissions associated with the user equipment, power headroom data indicating an amount of transmission power to which the user equipment can be increased, user equipment energy level data indicating an energy level of transmissions associated with the user equipment, or automatic neighbor relation data indicating neighbor relations of network devices to which the user equipment can be connected.

[0061] The user equipment may include an ultra-reliable low-latency communication device.

[0062] The network device may include a radio access network intelligent controller. Further operations may include: requesting, by the radio access network intelligent controller, a change to at least one of the first configured authorized physical resource block time slot data or the second configured authorized physical resource block time slot data from the radio access network element, obtaining updated configured authorized physical resource block time slot data from the radio access network element in response to the request, and sending suggested configured authorized physical resource block time slot data for the user equipment to the radio access network element based on the updated configured authorized physical resource block time slot data.

[0063] The user equipment may be a first user equipment, the condition data may include first condition data indicating a first condition of the first user equipment, and further operations may include: obtaining second condition data indicating a second condition of a second user equipment; and prioritizing the first user equipment with respect to physical resource block time slot allocation to have a higher priority than the second user equipment based on the first condition data and the second condition data. Prioritization may include determining that the first user equipment has a number of configured authorized physical resource block time slots that can meet a first quality of service specification of the first user equipment that is less than a number of configured authorized physical resource block time slots that can meet a second quality of service specification of the second user equipment.

[0064] The network device may include a radio access network intelligent controller, and further operations may include: determining, by the radio access network intelligent controller, a proposed change to a default configuration of at least one of: a first configuration authorized physical resource block time slot data or a second configuration authorized physical resource block time slot data; sending, by the controller, the proposed configuration authorized physical resource block time slot data to a service management and orchestration network element based on the proposed change; in response to the sending, receiving a reply communication to the sending of the proposed configuration authorized physical resource block time slot data; in response to the reply communication including first information confirming the proposed configuration authorized physical resource block time slot data, changing the configuration authorized physical resource block time slot data to the proposed configuration authorized physical resource block time slot data; and in response to the reply communication including second information rejecting the proposed configuration authorized physical resource block time slot data, retaining the default configuration of the configuration authorized physical resource block time slot data.

[0065] One or more example aspects such as example operations corresponding to a method are described in Fig.11 . Example operation 1102 indicates that a controller including a processor obtains condition data of a user equipment. Example operation 1104 indicates that the controller determines, based on the condition data, that the user equipment meets the condition of the reserved physical resource block time slots of the preset configuration authorization data. Example operation 1106 indicates that the controller obtains the authorized physical resource block time slot data of the first configuration from the first cell. Example operation 1108 indicates that the controller obtains the authorized physical resource block time slot data of the second configuration from the second cell. Example operation 1110 indicates that the controller selects a first subset of the reserved physical resource block time slots of the preset configuration authorization data for a first allocation to the user equipment. Example operation 1112 indicates that the controller selects a second subset of the reserved physical resource block time slots of the preset configuration authorization data for a second allocation to the user equipment, wherein the first subset and the second subset are selected to include adjacent time slots relative to each other.

[0066] Further operations may include transmitting, by the controller, configured authorized time slot information indicating the first subgroup and the second subgroup to a network element, the network element being used to set the configured authorized time slot with the user equipment.

[0067] The condition data may include first condition data, the user equipment may be a first user equipment, the adjacent time slot may include a first adjacent time slot, and further operations may include: obtaining, by a controller, second condition data of a second user equipment; determining, by the controller based on the second condition data, that the second user equipment meets the condition of the reserved physical resource block time slot of the preset configuration authorization data; selecting, by the controller, a third subgroup of the reserved physical resource block time slot of the preset configuration authorization data for a third allocation to the second user equipment; and selecting, by the controller, a fourth subgroup of the reserved physical resource block time slot of the preset configuration authorization data for a fourth allocation to the second user equipment, wherein the third subgroup and the fourth subgroup are selected as second adjacent time slots relative to each other. Selecting the first subgroup and selecting the second subgroup may be based on prioritizing the first user equipment over the second user equipment.

[0068] Further operations may include, in response to determining that the primary cell group and the secondary cell group time slot delay data do not meet the threshold delay data value relative to the unassigned user equipment, reorganizing the preset configuration authorization data by the controller.

[0069] Fig.12 Summarizing various example operations corresponding to, for example, a machine-readable medium, including executable instructions that, when executed by a processor, facilitate the performance of the operations. Example operation 1202 represents obtaining user equipment condition data indicating a device that is configured for packet duplication and that meets the configured authorization condition. Example operation 1204 represents obtaining a first configured authorized physical resource block time slot of a first cell and a second configured authorized physical resource block time slot of a second cell. Example operation 1206 represents selecting a first time slot of the first configured authorized physical resource block time slot and a second time slot of the second configured authorized physical resource block time slot based on the user equipment condition data, wherein the first time slot and the second time slot are selected to be adjacent to each other. Example operation 1208 represents allocating the first time slot and the second time slot to a user equipment.

[0070] Selecting the first time slot and the second time slot may include evaluating a time delay between the first time slot and the second time slot.

[0071] Selecting the first time slot and the second time slot may include selecting adjacent time slots.

[0072] The user equipment may be a first user equipment, wherein the condition data may be first condition data, and further operations include: prioritizing the first user equipment over the second user equipment with respect to selection of the first time slot and the second time slot; the prioritization is based on the first condition data and the second condition data. Obtaining a first configured authorized physical resource block time slot in response to requesting a change to a previously configured authorized physical resource block time slot

[0073] As can be seen, the techniques described herein facilitate cooperative configuration grants between multiple neighboring cells serving the same UE, including alignment of the time offset between the original packet version and its copy. The time slot configuration based on alignment of the configuration grant time slots between multiple cells reduces the DRX on duration for the UE and avoids reassembly timeouts.

[0074] Fig.13 13 is a schematic block diagram of a computing environment 1300 with which the disclosed subject matter can interact. System 1300 includes one or more remote components 1310. Remote component(s) 1310 can be hardware and / or software (e.g., threads, processes, computing devices). In some implementations, remote component(s) 1310 can be a distributed computer system connected to a local autoscaling component and / or a program using resources of the distributed computer system via a communication framework 1340. Communication framework 1340 can include wired network devices, wireless network devices, mobile devices, wearable devices, wireless access network devices, gateway devices, femtocell devices, servers, etc.

[0075] The system 1300 also includes one or more local components 1320. The local component(s) 1320 may be hardware and / or software (e.g., threads, processes, computing devices). In some embodiments, the local component(s) 1320 may include an automatic scaling component connected to a remotely located distributed computing system via a communication framework 1340 and / or a program that transfers / uses remote resources 1310 and 1320, etc.

[0076] One possible communication between the remote component(s) 1310 and the local component(s) 1320 may be in the form of data packets suitable for transmission between two or more computer processes. Another possible communication between the remote component(s) 1310 and the local component(s) 1320 may be in the form of circuit-switched data suitable for transmission between two or more computer processes in a radio time slot. The system 1300 includes a communication framework 1340 that can be used to facilitate communication between the remote component(s) 1310 and the local component(s) 1320, and may include an air interface via a Long Term Evolution (LTE) network, such as a Uu interface of a UMTS network. The remote component(s) 1310 may be operably connected to one or more remote data stores 1350 that can be used to store information on the remote component(s) 1310 side of the communication framework 1340, such as a hard drive, solid state drive, SIM card, device memory, etc. Similarly, the local component 1320 can be operably connected to one or more local data stores 1330 , which can be used to store information on the local component 1320 side of the communication framework 1340 .

[0077] To provide additional context for the various implementations described herein, Fig.14 The following discussion is intended to provide a brief, general description of a suitable computing environment 1400 in which various implementations of the implementations described herein may be implemented. Although the implementations are described above in the general context of computer-executable instructions that may be executed on one or more computers, those skilled in the art will recognize that the implementations may also be implemented in combination with other program modules and / or as a combination of hardware and software.

[0078] Generally, program modules include routines that perform specific tasks or implement specific abstract data types, programs, components, data structures, etc. In addition, those skilled in the art will appreciate that the methods may be practiced with other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, Internet of Things devices, distributed computing systems, and personal computers, handheld computing devices, microprocessor-based or programmable consumer electronics, etc., each of which may be operably coupled to one or more associated devices.

[0079] The illustrated embodiments of the embodiments herein may also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0080] Computing devices typically include a variety of media, which may include computer-readable storage media, machine-readable storage media, and / or communication media, the two terms being used differently from each other herein as follows. Computer-readable storage media or machine-readable storage media can be any available storage media that can be accessed by a computer, and include volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, computer-readable storage media or machine-readable storage media can be implemented in conjunction with any method or technology for storing information such as computer-readable or machine-readable instructions, program modules, structured data or unstructured data.

[0081] Computer-readable storage media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CDROM), digital versatile disk (DVD), Blu-ray disk (BD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, solid-state drives or other solid-state storage devices, or other tangible and / or non-transitory media that can be used to store the desired information. In this regard, the terms "tangible" or "non-transitory" as applied herein to storage devices, memories, or computer-readable media should be understood to exclude only propagating transient signals per se as a modifier, and not to disclaim all standard storage devices, memories, or computer-readable media that do not only propagate transient signals per se.

[0082] Computer-readable storage media may be accessed by one or more local or remote computing devices, eg, through access requests, queries, or other data retrieval protocols, for various operations regarding the information stored by the media.

[0083] Communication media typically embodies computer readable instructions, data structures, program modules, or other structured or unstructured data in a data signal such as a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery or transmission media. The term "modulated data signal" or "multiple signals" refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal or signals. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[0084] Reference again Fig.14 , an example environment 1400 for implementing various implementations of various aspects described herein includes a computer 1402, which includes a processing unit 1404, a system memory 1406, and a system bus 1408. The system bus 1408 couples system components including, but not limited to, the system memory 1406 to the processing unit 1404. The processing unit 1404 can be any of a variety of commercially available processors. Dual microprocessors and other multi-processor architectures can also be used as the processing unit 1404.

[0085] The system bus 1408 may be any of several types of bus structures, which may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 1406 includes ROM 1410 and RAM 1412. A basic input / output system (BIOS) containing the basic routines that help transfer information between elements within the computer 1402, such as during startup, may be stored in a nonvolatile memory such as ROM, an erasable programmable read-only memory (EPROM), or EEPROM. RAM 1412 may also include high-speed RAM, such as static RAM for caching data.

[0086] The computer 1402 also includes an internal hard disk drive (HDD) 1414 (e.g., EIDE, SATA), and may include one or more external storage devices 1416 (e.g., a magnetic floppy disk drive (FDD) 1416, a memory stick or flash drive reader, a memory card reader, etc.). Although the internal HDD 1414 is shown as being located within the computer 1402, the internal HDD 1414 may also be configured for external use in an appropriate enclosure (not shown). Additionally, although not shown in the environment 1400, a solid state drive (SSD) may be used in addition to or in place of the HDD 1414.

[0087] Other internal or external storage may include at least one other storage device 1420 having a storage medium 1422 (e.g., a solid-state storage device, a non-volatile storage device, and / or an optical drive that can read or write from a removable medium such as a CD-ROM disk, a DVD, a BD, etc.). External memory 1416 may be facilitated by a network virtual machine. HDD 1414, external storage device 1416, and storage device (e.g., drive) 1420 may be connected to the system bus 1408 via a HDD interface 1424, an external storage interface 1426, and a drive interface 1428, respectively.

[0088] The drives and their associated computer-readable storage media provide non-volatile storage of data, data structures, computer-executable instructions, etc. For the computer 1402, the drives and storage media accommodate the storage of any data in an appropriate digital format. Although the above description of computer-readable storage media refers to corresponding types of storage devices, it should be understood by those skilled in the art that other types of computer-readable storage media, whether currently existing or developed in the future, can also be used in the exemplary operating environment, and further, any such storage media can contain computer-executable instructions for performing the methods described herein.

[0089] Program modules may be stored in the drives and RAM 1412, including an operating system 1430, one or more applications 1432, other program modules 1434, and program data 1436. All or portions of the operating system, applications, modules, and / or data may also be cached in RAM 1412. The systems and methods described herein may be implemented using various commercially available operating systems or combinations of operating systems.

[0090] Computer 1402 may optionally include emulation technology. For example, a hypervisor (not shown) or other intermediary may emulate the hardware environment of operating system 1430, and the emulated hardware may optionally communicate with the operating system 1430. Fig.14 The hardware shown is different. In such an implementation, the operating system 1430 may include one of multiple virtual machines (VMs) hosted at the computer 1402. In addition, the operating system 1430 may provide a runtime environment for the application 1432, such as a Java runtime environment or a .NET framework. The runtime environment is a consistent execution environment that allows the application 1432 to run on any operating system that includes a runtime environment. Similarly, the operating system 1430 may support containers, and the application 1432 may be in the form of a container, which is a lightweight, independent, executable software package that includes, for example, code, runtime, system tools, system libraries, and settings for the application.

[0091] In addition, the computer 1402 may have a security module, such as a trusted processing module (TPM). For example, with a TPM, before loading the next boot component, the boot component hashes the next boot component in time and waits for the result to match the security value. This process may occur at any layer in the code execution stack of the computer 1402, for example, at the application execution level or at the operating system (OS) kernel level, thereby implementing security at any code execution level.

[0092] A user may enter commands and information into the computer 1402 through one or more wired / wireless input devices, such as a keyboard 1438, a touch screen 1440, and a pointing device such as a mouse 1442. Other input devices (not shown) may include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control or other remote control, a joystick, a virtual reality controller and / or a virtual reality headset, a game pad, a stylus, an image input device (e.g., a camera), a gesture sensor input device, a visual motion sensor input device, an emotion or facial detection device, a biometric input device (e.g., a fingerprint or iris scanner), etc. These and other input devices are typically connected to the processing unit 1404 through an input device interface 1444, which may be coupled to the system bus 1408, but may also be connected through other interfaces, such as a parallel port, an IEEE 1494 serial port, a game port, a USB port, an R interface, Interfaces, etc.

[0093] A monitor 1446 or other type of display device may also be connected to the system bus 1408 via an interface, such as a video adapter 1448. In addition to the monitor 1446, computers typically include other peripheral output devices (not shown), such as speakers, printers, and the like.

[0094] The computer 1402 can operate in a networked environment using logical connections to one or more remote computers (e.g., remote computer 1450) via wired and / or wireless communications. The remote computer 1450 can be a workstation, server computer, router, personal computer, portable computer, microprocessor-based entertainment device, peer device, or other public network node, and typically includes many or all of the elements described relative to the computer 1402, although only a memory / storage device 1452 is shown for the purpose of simplicity. The depicted logical connections include wired / wireless connections to a local area network (LAN) 1454 and / or a larger network (e.g., a wide area network (WAN) 1456). Such LAN and WAN networking environments are common in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can be connected to a global communication network, such as the Internet.

[0095] When used in a LAN networking environment, the computer 1402 can be connected to the local network 1454 through a wired and / or wireless communication network interface or adapter 1458. The adapter 1458 can facilitate wired or wireless communication to the LAN 1454, which can also include a wireless access point (AP) disposed thereon for communicating with the adapter 1458 in a wireless mode.

[0096] When used in a WAN networking environment, the computer 1402 may include a modem 1460, or may be connected to a communication server on the WAN 1456 via other means for establishing communications on the WAN 1456, such as through the Internet. The modem 1460, which may be internal or external and a wired or wireless device, may be connected to the system bus 1408 via the input device interface 1444. In a networked environment, program modules described relative to the computer 1402, or portions thereof, may be stored in the remote memory / storage device 1452. It should be appreciated that the network connections shown are examples and other means of establishing a communications link between the computers may be used.

[0097] When used in a LAN or WAN networking environment, the computer 1402 may access a cloud storage system or other network-based storage system in addition to or in place of the external storage devices 1416 described above. Typically, the connection between the computer 1402 and the cloud storage system may be established over the LAN 1454 or WAN 1456, for example, through an adapter 1458 or a modem 1460, respectively. When the computer 1402 is connected to the associated cloud storage system, the external storage interface 1426 may manage the storage provided by the cloud storage system with the help of the adapter 1458 and / or the modem 1460, just like other types of external storage. For example, the external storage interface 1426 may be configured to provide access to cloud storage sources as if those sources were physically connected to the computer 1402.

[0098] The computer 1402 can be operable to communicate with any wireless device or entity operable to be arranged in wireless communication, such as printers, scanners, desktop and / or portable computers, portable data assistants, communication satellites, any device or location associated with a wireless detectable tag (e.g., a kiosk, a newsstand, a store shelf, etc.), and telephones. This can include Wireless Fidelity (Wi-Fi) and Wireless technology. Therefore, the communication can be a predetermined structure like traditional networks, or just an ad hoc communication between at least two devices.

[0099] The above description of exemplary implementations of the present disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed implementations to the precise forms disclosed. Although specific embodiments and implementations are described herein for illustrative purposes, various modifications may be considered within the scope of these embodiments and implementations as those skilled in the relevant art can recognize.

[0100] In this regard, while the disclosed subject matter has been described in conjunction with various implementations and corresponding figures, it should be understood that other similar implementations may be used, or modifications and additions may be made to the described implementations to perform the same, similar, alternative, or substitute functions of the disclosed subject matter without departing from the invention. Accordingly, the disclosed subject matter should not be limited to any single implementation described herein, but rather should be interpreted in accordance with the breadth and scope of the claims appended hereto.

[0101] As used in this specification, the term "processor" may refer to substantially any computing processing unit or device including but not limited to a single-core processor, a single processor with software multithreaded execution capability, a multi-core processor, a multi-core processor with software multithreaded execution capability, a multi-core processor with hardware multithreading technology, a parallel platform, and a parallel platform with distributed shared memory. In addition, a processor may refer to an integrated circuit, an application-specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein. The processor may utilize nanoscale architectures, such as but not limited to transistors, switches, and gate circuits based on molecules and quantum dots, in order to optimize space utilization or improve the performance of user devices. The processor may also be implemented as a combination of computing processing units.

[0102] As used in this application, the terms "component", "system", "platform", "layer", "selector", "interface", etc. are intended to refer to an entity associated with a computer or an entity associated with an operating device having one or more specific functions, wherein the entity can be hardware, a combination of hardware and software, software, or software in execution. As an example, a component can be, but is not limited to, a process processor, an object, an executable program, an execution thread, a program, and / or a computer running on a processor. As an illustration and not limitation, both applications running on a server and servers can be components. One or more components may reside within a process and / or execution thread, and a component may be located on one computer and / or distributed between two or more computers. In addition, these components may be executed from various computer-readable media having various data structures stored thereon. These components may communicate via local and / or remote processes, for example, according to a signal having one or more data packets (e.g., data from a component that interacts with a local system, another component in a distributed system, and / or interacts with other systems across a network such as the Internet via the signal). As another example, a component may be a device having a specific functionality provided by mechanical parts operated by electrical or electronic circuits, which is operated by a software or firmware application executed by a processor, where the processor may be internal or external to the device and executes at least a portion of the software or firmware application. As yet another example, a component may be a device having a specific functionality provided by an electronic component having no mechanical parts, where a processor may be included in the electronic component to execute the software or firmware that at least partially imparts the functionality to the electronic component.

[0103] Furthermore, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless specified otherwise, or clear from the context, "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing instances.

[0104] Although implementations are susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described in detail above. However, it should be understood that it is not intended to limit the various implementations to the particular forms disclosed, but rather to cover all modifications, alternative constructions and equivalents falling within the spirit and scope.

[0105] In addition to the various implementations described herein, it should be understood that other similar implementations may be used, or the described implementations may be modified and added to perform the same or equivalent functions of the corresponding implementations without departing from the present invention. In addition, multiple processing chips or multiple devices may share the performance of one or more functions described herein, and similarly, storage may be implemented across multiple devices. Therefore, the various implementations are not limited to any single implementation, but should be interpreted in accordance with the breadth, spirit, and scope of the appended claims.

Claims

1. A network device, comprising: processor; as well as a memory storing executable instructions that, when executed by the processor, facilitate performing operations comprising: obtaining condition data representing a condition of a user device; Determining, based on the condition data, that the user equipment meets a preset configuration authorization condition; Obtaining first configured authorized physical resource block time slot data representing a first time slot for a first cell, and obtaining second configured authorized physical resource block time slot data representing a second time slot for a second cell; and Selecting from the first configured authorized physical resource block time slot data and the second configured authorized physical resource block time slot data in a time-aligned manner to allocate a first subset of the first time slots of the first configured authorized physical resource block time slot data and to allocate a second subset of the second time slots of the second configured authorized physical resource block time slot data, the time alignment being determined to reduce end-to-end packet data convergence protocol delay for duplicate communications between the first cell and the user equipment and between the second cell and the user equipment. 2 . The system of claim 1 , wherein the time alignment corresponds to a first time slot of the first subset being adjacent to a second time slot of the second subset.

3. The system of claim 1, wherein the selecting from the first configuration granted physical resource block time slot data and the second configuration granted physical resource block time slot data further comprises: The first configured granted physical resource block time slot data and the second configured granted physical resource block time slot data which have been determined to save energy of the user equipment are selected according to an energy saving function.

4. The system of claim 1 , wherein the condition data comprises at least one of the following: user equipment capability data indicating capabilities of the user equipment, radio condition data indicating radio conditions of a radio channel associated with the user equipment, packet data convergence protocol delay data indicating packet data convergence protocol delay associated with the user equipment, packet delay data indicating packet delay associated with the user equipment, buffer status data indicating a status of a buffer of the user equipment, channel condition data indicating channel conditions of a channel associated with the user equipment, block error rate data indicating a block error rate applicable to transmissions associated with the user equipment, power headroom data indicating an amount of transmission power of the user equipment that can be increased, user equipment energy level data indicating an energy level of transmissions associated with the user equipment, or automatic neighbor relation data indicating neighbor relations of network devices to which the user equipment can be connected.

5. The system of claim 1, wherein the user equipment comprises an ultra-reliable low-latency communication device.

6. The system of claim 1, wherein the network device comprises a radio access network intelligent controller.

7. The system of claim 6, wherein the operations further comprise: requesting, by the radio access network intelligent controller, a change to at least one of the first configured authorized physical resource block time slot data or the second configured authorized physical resource block time slot data from a radio access network element, acquiring updated configured authorized physical resource block time slot data from the radio access network element in response to the request, and sending suggested configured authorized physical resource block time slot data for the user equipment to the radio access network element based on the updated configured authorized physical resource block time slot data.

8. The system of claim 1, wherein the user device is a first user device, wherein the condition data comprises first condition data representing a first condition of the first user device, and wherein the operations further comprise: Second condition data representing a second condition of a second user equipment is obtained, and the first user equipment is prioritized with respect to physical resource block time slot allocation to have a higher priority than the second user equipment based on the first user condition and the second user condition.

9. The system of claim 8, wherein the prioritization comprises: It is determined that the number of configured authorized physical resource block time slots of the first user equipment that can meet a first quality of service specification of the first user equipment is less than the number of configured authorized physical resource block time slots that can meet a second quality of service specification of the second user equipment.

10. The system of claim 1, wherein the network device comprises a radio access network intelligent controller, and wherein the operations further comprise: determining, by the radio access network intelligent controller, a proposed change to a default configuration of at least one of: the first configuration granting physical resource block time slot data or the second configuration granting physical resource block time slot data; sending, by the controller, proposed configuration granted physical resource block time slot data to a service management and orchestration network element based on the proposed change; receiving, in response to said transmitting, a reply communication to said transmitting of said proposed configuration of granted physical resource block time slot data; In response to the reply communication including first information confirming the proposed configuration authorized physical resource block time slot data, changing the configured authorized physical resource block time slot data to the proposed configuration authorized physical resource block time slot data; as well as In response to the reply communication including second information rejecting the proposed configuration of granted physical resource block time slot data, retaining the default configuration of the configuration of granted physical resource block time slot data.

11. A method comprising: Acquiring, by a controller including a processor, condition data of a user device; The controller determines, based on the condition data, that the user equipment meets the condition of the reserved physical resource block time slot of the preset configuration authorization data; The controller obtains first configured authorized physical resource block time slot data from the first cell; The controller obtains second configuration authorized physical resource block time slot data from the second cell; selecting, by the controller, a first subset of the reserved physical resource block time slots of the preset configuration grant data for a first allocation to the user equipment; as well as A second subset of the reserved physical resource block time slots of the preset configuration grant data is selected by the controller for a second allocation to the user equipment, wherein the first subset and the second subset are selected to include adjacent time slots relative to each other.

12. The method according to claim 11, further comprising: The controller transmits configuration authorization time slot information indicating the first subgroup and the second subgroup to a network element for use in setting configuration authorization time slots with the user equipment.

13. The method according to claim 11, wherein the condition data comprises first condition data, wherein the user equipment is a first user equipment, wherein the adjacent time slot is a first adjacent time slot, and the method further comprises: The controller acquires second condition data of a second user equipment; The controller determines, based on the second condition data, that the second user equipment meets the condition of the reserved physical resource block time slot of the preset configuration authorization data; selecting, by the controller, a third subset of the reserved physical resource block time slots of the preset configuration grant data for a third allocation to the second user equipment; A fourth subset of the reserved physical resource block time slots of the preset configuration grant data is selected by the controller for a fourth allocation to the second user equipment, wherein the third subset and the fourth subset are selected as second adjacent time slots relative to each other.

14. The method of claim 13, wherein the selection of the first subgroup and the selection of the second subgroup are based on prioritizing the first user device relative to the second user device.

15. The method according to claim 11, further comprising: The controller reorganizes the preset configuration authorization data in response to determining that the time slot delay data of the primary cell group and the secondary cell group does not meet the threshold delay data value relative to the unassigned user equipment.

16. A non-transitory machine-readable medium comprising executable instructions that, when executed by a processor, facilitate performing operations comprising: Acquiring user equipment condition data, the user equipment condition data indicating a device configured for packet replication that meets a configuration authorization condition; Obtaining a first configured authorized physical resource block time slot for the first cell and a second configured authorized physical resource block time slot for the second cell; selecting, based on the user equipment condition data, a first time slot of the first configuration authorized physical resource block time slot and a second time slot of the second configuration authorized physical resource block time slot, wherein the first time slot and the second time slot are selected to be adjacent to each other; and The first time slot and the second time slot are allocated to the user equipment.

17. The non-transitory machine-readable medium of claim 16, wherein the selection of the first time slot and the second time slot comprises evaluating a time delay between the first time slot and the second time slot.

18. The non-transitory machine-readable medium of claim 16, wherein the selection of the first time slot and the second time slot comprises selecting adjacent time slots.

19. The non-transitory machine-readable medium of claim 16, wherein the user device is a first user device, wherein the condition data is first condition data, and wherein the operations further comprise: The first user equipment is prioritized over a second user equipment with respect to the selection of the first time slot and the second time slot, wherein the prioritization is based on the first condition data and the second condition data.

20. The non-transitory machine-readable medium of claim 19, wherein the obtaining of the first configured granted physical resource block slot is in response to requesting a change to a previously configured granted physical resource block slot.

Images