Configuration method and device of auxiliary carrier, medium and program product

Abstract

According to the auxiliary carrier configuration method and device, the medium and the program product provided by the embodiments of the present application, a source base station sends a switching request message to a target base station, the switching request message carrying UE service state information detected by the source base station; the target base station determines an auxiliary cell pre-establishment list according to the service state information, determines an auxiliary base station according to the auxiliary cell pre-establishment list, and sends a cross-station auxiliary carrier establishment request message to the auxiliary base station; the auxiliary base station sends a cross-station auxiliary carrier establishment response message to the target base station; and the target base station receives a cross-station auxiliary carrier establishment response message replied by the auxiliary base station, and establishes a cross-station auxiliary carrier according to the cross-station auxiliary carrier establishment response message. According to the embodiment of the invention, the technical problem that the target base station side is not supported to distribute the auxiliary carrier of the UE according to needs in the mobility switching process of the UE in the related technology is solved. And the switching target base station side decides the auxiliary carrier configuration of the UE based on the UE service state, thereby ensuring that the cross-station auxiliary carrier configuration of the UE can meet the service requirement of the UE, and reducing the waste of auxiliary carrier resources.

Description

Technical Field

[0001] The present application relates to the technical field of communication equipment, and in particular to a configuration method, equipment, medium and program product for an auxiliary carrier. Background Art

[0002] In fifth-generation (5G) mobile communication networks, inter-base station mobility handover is a crucial technology that ensures that user equipment (UE) can seamlessly transfer from a source gNB to a target gNB during mobility, thereby maintaining communication continuity.

[0003] When a UE transfers from a source base station to a target base station, the source base station's Centralized Unit (CU) and Distributed Unit (DU) work together to ensure a smooth handover. Before a mobility handover occurs, mobility handover preparation is required. During this stage, the CU is primarily responsible for receiving UE measurement reports and making handover decisions based on these reports and other network parameters. The DU, on the other hand, is primarily responsible for preparing the wireless resources required by the target base station.

[0004] In scenarios where public and non-public networks (NPNs) coexist, especially in applications requiring high bandwidth and low latency, the decision to add a secondary carrier to the UE can be made during the mobility handover preparation process to improve network performance and coverage. However, current technologies do not support the on-demand allocation of secondary carriers by the target base station during a mobility handover. This results in irrational allocation of radio resources by the target base station, resulting in waste of radio resources and a pressing technical issue to be addressed. Summary of the Invention

[0005] The embodiments of the present application propose a secondary carrier configuration method, device, medium and program product, aiming to solve the technical problem that the relevant technology does not support the target base station side to allocate the UE's secondary carrier on demand during the UE's mobility switching process, resulting in unreasonable allocation of wireless resources on the target base station side and waste of wireless resources.

[0006] In a first aspect, an embodiment of the present application provides a method for configuring a secondary carrier, which is applied to a target base station. The method includes:

[0007] receiving a handover request message, wherein the handover request message includes service status information of the terminal UE;

[0008] determining a pre-established list of secondary cells according to the service status information;

[0009] determining a secondary base station according to the secondary cell pre-establishment list, and sending an inter-site secondary carrier establishment request message to the secondary base station, so that the secondary base station replies with an inter-site secondary carrier establishment response message according to the inter-site secondary carrier establishment request message;

[0010] The cross-site secondary carrier establishment response message is received, and a secondary carrier of the UE is established according to the cross-site secondary carrier establishment response message.

[0011] In a second aspect, an embodiment of the present application provides a method for configuring a secondary carrier, which is applied to a source base station, and the method includes:

[0012] Send a handover request message to the target base station, where the handover request message carries UE service status information detected by the source base station based on the UE uplink and downlink service volume and the main service direction, so that the target base station determines a secondary cell pre-establishment list according to the service status information, determines a secondary base station according to the secondary cell pre-establishment list, and sends a cross-site secondary carrier establishment request message to the secondary base station.

[0013] Among them, during the process of the source base station detecting the UE service status information, a downlink service volume detection request message and its response message, and a downlink service volume reporting message are added between the CU-CP and the CU-UP; a new F1 port uplink service volume and main service direction detection request message and its response message, and an uplink service volume and main service direction reporting message are added between the CU-CP and the DU.

[0014] In a third aspect, an embodiment of the present application provides a method for configuring a secondary carrier, which is applied to a secondary base station. The method includes:

[0015] receiving a cross-site secondary carrier establishment request message from a target base station;

[0016] The cross-site secondary carrier establishment response message is sent to the target base station according to the cross-site secondary carrier establishment request message, so that the target base station establishes the secondary carrier of the UE according to the cross-site secondary carrier establishment response message.

[0017] In a fourth aspect, an embodiment of the present application provides a communication device, including:

[0018] one or more processors;

[0019] a memory storing one or more computer programs;

[0020] When the one or more computer programs are executed by the one or more processors, the one or more processors implement: the auxiliary carrier configuration method as described in the first aspect; or the auxiliary carrier configuration method as described in the second aspect; or the auxiliary carrier configuration method as described in the third aspect.

[0021] In a fifth aspect, a computer-readable storage medium stores a computer program thereon, and when the computer program is executed by a processor, it implements: the auxiliary carrier configuration method as described in the first aspect; or the auxiliary carrier configuration method as described in the second aspect; or the auxiliary carrier configuration method as described in the third aspect.

[0022] In a sixth aspect, a computer program product includes a computer program, which, when executed by a processor, implements: the auxiliary carrier configuration method as described in the first aspect; or the auxiliary carrier configuration method as described in the second aspect; or the auxiliary carrier configuration method as described in the third aspect.

[0023] Embodiments of the present application provide a method, device, medium, and program product for configuring a secondary carrier, wherein a source base station sends a handover request message to a target base station, where the handover request message carries UE service status information detected by the source base station based on the UE uplink and downlink service volume and the main service direction; the target base station determines a pre-established list of secondary cells based on the service status information, determines a secondary base station based on the pre-established list of secondary cells, and sends a cross-site secondary carrier establishment request message to the secondary base station; the secondary base station receives the cross-site secondary carrier establishment request message, determines the cross-site secondary carrier corresponding to the UE based on the cross-site secondary carrier establishment request message, and sends a cross-site secondary carrier establishment response message to the target base station; the target base station receives the cross-site secondary carrier establishment response message replied by the secondary base station, and establishes a cross-site secondary carrier based on the cross-site secondary carrier establishment response message. According to the solution of the embodiment of the present application, the target base station can obtain the service status information of the UE from the handover request message sent by the source base station, and then determine the cross-site secondary carrier configuration of the UE based on the service status information, output the secondary cell pre-establishment list, and send a cross-site secondary carrier establishment request message to the corresponding secondary base station based on the secondary cell pre-establishment list to establish a cross-site secondary carrier. This solves the technical problem of the current related technology that the target base station side cannot allocate the UE secondary carrier on demand during the UE mobility handover process. The handover target base station side needs to reasonably decide the UE secondary carrier configuration based on the UE's service status to ensure that the UE's cross-site secondary carrier configuration can meet the UE's service needs while reducing the waste of secondary carrier resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1a A flowchart of adding a cross-site auxiliary carrier in a scenario where the public network and NPN private network coexist, provided for related technologies;

[0025] Figure 1bA schematic diagram of a secondary carrier addition configuration process in a cross-PLMN scenario provided by an embodiment of the present application;

[0026] Figure 2a A schematic diagram of a method for configuring a secondary carrier provided in an embodiment of the present application;

[0027] Figure 2b A schematic diagram of a method for configuring a secondary carrier provided in an embodiment of the present application;

[0028] Figure 2c A schematic diagram of an XN link establishment process between a target base station and a secondary base station provided in an embodiment of the present application;

[0029] Figure 2d A schematic diagram of a method for configuring a secondary carrier provided in an embodiment of the present application;

[0030] Figure 2e A schematic diagram of a method for configuring a secondary carrier provided in an embodiment of the present application;

[0031] Figure 3 A schematic diagram of the flow of uplink and downlink packet detection and main service direction detection of the source base station provided in an embodiment of the present application;

[0032] Figure 4 A schematic diagram of a secondary carrier configuration process provided in an embodiment of the present application;

[0033] Figure 5 A schematic diagram of a flow chart for configuring a secondary carrier during mobility XN switching in a scenario where a public network and an NPN private network coexist, provided in an embodiment of the present application;

[0034] Figure 6 A schematic diagram of a process flow for determining the status of a large service packet provided in an embodiment of the present application;

[0035] Figure 7 A schematic diagram of a service packet status determination process provided in an embodiment of the present application;

[0036] Figure 8 A flowchart of a method for determining a primary service direction provided in an embodiment of the present application;

[0037] Figure 9 A schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] In order to enable those skilled in the art to better understand the technical solution of the present application, the technical solution provided by the present application is described in detail below with reference to the accompanying drawings.

[0039] Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but the described example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete and will fully convey the scope of this application to those skilled in the art.

[0040] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0041] The terms used herein are used only to describe specific embodiments and are not intended to limit this application. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and / or "made of" are used in this specification, they specify the presence of features, wholes, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or groups thereof.

[0042] In the following description, reference is made to “some embodiments”, which describes a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0043] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present application, and will not be interpreted as having an idealized or overly formal meaning, unless clearly defined in the examples of the present application.

[0044] To facilitate a better understanding of the solutions of the embodiments of the present application, the relevant technologies are first introduced below.

[0045] The core network is the core component of the mobile network. It is mainly responsible for processing and controlling user data transmission, mobility management, session management, and connections with other networks. It is a bridge connecting the base station subsystem and external networks (such as the Internet, other operator networks, etc.), providing communication services to users.

[0046] The core network primarily consists of multiple network function entities that work together to provide complete communication services. In 5G networks, the core network has further evolved into a service-based architecture (SBA), introducing new technologies such as network slicing and edge computing. This makes the core network more flexible, programmable, and scalable, able to meet the needs of different industries and scenarios.

[0047] A generation NodeB (gNB) is a base station in a 5G network. It is a newly built base station based on the 5G standard and provides wireless access services for the 5G network. Logically, a gNB consists of two parts: the CU and the DU. The gNB plays a key role in mobility switching. When a UE moves from one base station to another, the gNB needs to interact with other base stations and the core network to ensure that the UE can seamlessly switch to the new base station. This includes receiving measurement reports from the UE, making handover decisions, and preparing the radio resources required by the target base station. In addition, the gNB also supports interaction with other network entities, such as signaling interaction with the core network (such as NGC or EPC+) to support UE mobility management, session management, and other functions.

[0048] Mobility handover is a core concept in wireless network communications. It specifically refers to the process by which a wireless communication user device (or terminal, UE), such as a smartphone, laptop, or other mobile device, seamlessly transfers its communication connection to the new base station when it moves from one base station (or cell, access point) to another, thereby maintaining communication continuity and service quality. XN handover is a type of mobility handover in 5G New Wireless, similar to X2 handover in 4G Long Term Evolution. This handover occurs when a user device moves from one gNB to another and does not require re-interpretation of user plane functions. This type of handover only applies to mobility within the same access and mobility management function. That is, if the source gNB and target gNB are connected to different mobility management functions (AMF), XN handover cannot be used.

[0049] In 5G networks, the CU is divided into two parts: the Centralized Unit Control Plane (CU-CP) and the Centralized Unit User Plane (CU-UP). The CU-CP is responsible for control plane functions, including session management, mobility management, security management, and policy control; while the CU-UP is responsible for user plane functions, including data transmission and forwarding, packet processing, flow control and congestion management, and quality of service assurance. This separation makes 5G networks more flexible and efficient.

[0050] The CU is a key component in the 5G network architecture. Responsible for handling complex control signaling and data transmission tasks, the CU hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) sublayers of the 5G base station. Furthermore, the CU handles control plane functions related to UE communications, including establishing, maintaining, and terminating connections between the UE and the network, managing UE context information, and performing control functions related to UE mobility and session management.

[0051] The DU is also a key component in the 5G network architecture, primarily responsible for handling physical layer functions and real-time Layer 2 functions. Working in conjunction with the CU, it enables the functional reconfiguration of 5G base stations. The DU hosts the radio link control (RLC), media access control (MAC), and physical layer (PHY) sublayers of the gNB. This means the DU is responsible for handling the real-time requirements associated with data transmission and the physical layer, including physical layer operations such as data coding, modulation, spreading, and demodulation, as well as MAC layer functions such as scheduling, multiplexing, and demultiplexing.

[0052] In a gNB, the CU is primarily responsible for non-real-time upper radio stack functions, including the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) sublayers. The CU centrally controls one or more DUs and handles control plane functions related to UE communications, such as establishing, maintaining, and terminating connections between the UE and the network and managing UE context information. The DU primarily handles physical layer functions and real-time Layer 2 functions, including Radio Link Control (RLC), Medium Access Control (MAC), and the physical layer. It executes instructions from the CU, such as handover commands, to ensure continuous and stable data transmission.

[0053] A carrier is the baseband signal that transmits information. It plays a crucial role in communication systems and can be considered the medium for transmitting information. In wireless communication systems, especially advanced systems like 5G, the concept of carriers has been further expanded and applied. In 5G networks, base stations (gNBs) use component carriers (CCs) as the basic unit of data transmission to provide services to users. Component carriers can be in either licensed or unlicensed frequency bands. By aggregating multiple component carriers, the data transmission capacity and efficiency of the communication system can be greatly improved.

[0054] Component carriers are further distinguished between Primary Carrier Component (PCC) and Secondary Carrier Component (SCC). The PCC is the core of a component carrier, typically carrying the initial connection of user equipment (UE) and primary information transmission. The PCC is the starting point for establishing a connection between the UE and the network, handling signaling related to key processes such as initial UE access, authentication, and network configuration. It also carries the majority of UE data traffic and is key to ensuring communication continuity and stability. Compared to the PCC, the SCC plays a complementary and supporting role within the component carrier. The SCC can be considered an extension or backup of the PCC, improving data transmission capacity and reliability. When the PCC encounters congestion or interference, the SCC can take over some data transmission tasks to ensure continued UE communication. Furthermore, the SCC can be used to implement more advanced features such as carrier aggregation. By combining multiple SCCs with the PCC, a wider data transmission channel is formed, thereby improving overall network performance and throughput. It is important to note that the PCC and SCC are not fixed. During network configuration and operation, the roles and functions of the PCC and SCC can be dynamically adjusted according to actual needs and the mobility status of the UE. This flexibility enables 5G networks to better adapt to different scenarios and needs, providing more efficient and reliable communication services. It should be noted that in some descriptions of the embodiments of this application, the primary carrier and the primary cell (Pcell) have the same meaning, and the secondary carrier and the secondary cell (Scell) have the same meaning.

[0055] During the mobility preparation phase, the CU is primarily responsible for receiving measurement reports from the UE and making handover decisions based on these reports and other network parameters. By centralizing control plane functions, the CU has a more comprehensive understanding of network status and UE requirements, enabling more accurate handover decisions. This helps reduce the likelihood of handover failures and improves handover success and efficiency.

[0056] The DU is primarily responsible for preparing the radio resources required by the target base station. By handling both physical layer functions and real-time Layer 2 functions, the DU ensures the continuity and stability of data transmission during handover. This helps reduce data loss and delays during handover, improving communication quality and reliability.

[0057] Please refer to Figure 1a , a flowchart of adding a cross-site auxiliary carrier in a scenario where a public network and an NPN private network coexist is provided for related technologies, such as Figure 1a As shown, an XN handover is performed to maintain communication continuity when a user equipment (UE) moves from source base station gNB1 to target base station gNB2. This process involves the coordinated operation of multiple components, including the core network, the UE, centralized units CU_1 and CU_2, and distributed units DU_1 and DU_2. The source base station gNB1 is divided into CU_1 and DU_1, while the target base station gNB2 is divided into CU_2 and DU_2. In addition, there is a secondary base station gNB3, which contains an NPN cross-site secondary carrier SCell. The secondary base station is divided into CU_3 and DU_3.

[0058] CU_1 of the source base station gNB1 initiates a Handover Request message to CU_2 of the target base station gNB2, where the selected target cell is located. After receiving the Handover Request, CU_2 performs admission control, grants admission, and allocates a UE instance and transmission resources. CU_2 then responds with a Handover Request ACKNOWLEDGE message to the source base station gNB1, allowing the handover. If some Protocol Data Unit (PDU) sessions fail to be handed over, the message includes a list of the failed PDU sessions. DU_1 of the source base station gNB1 sends a Radio Resource Control (RRC) Reconfiguration message to the UE, requesting that the UE perform a handover to the target cell. CU_1 sends the Packet Data Convergence Protocol (PDCP) SN to CU_2 via an SN STATUS TRANSFER message. The UE sends an RRC Reconfiguration Complete message to DU_2, completing the air interface handover to the target cell. CU_2 then sends a Path Switch Request (PATH SWITCH REQUEST) message to the core network to notify the core network of the UE's cell change. The PATH SWITCH REQUEST message contains the target cell identifier and a list of transferred PDU sessions. Upon receiving this message, the core network updates the downlink GTPU data plane, changing the GTPU address on the RAN side to that of the target base station gNB2, and sends a PATH SWITCH REQUEST ACKNOWLEDGE message to CU_2 of the target base station gNB2. If the Access and Mobility Management Function (AMF) indicates in the PATH SWI TCH REQUESTACKNOWLEDGE message that the core network failed to establish the PDU Session, the gNodeB deletes the failed PDUSession. The target base station gNB2 sends a UE CONTEXT RELEASE message to the source base station gNB1.

[0059] It should be noted that during the handover process, CU_2 will send a UE CONTEXT SETUP REQUEST message to DU_2 to apply for new user resources for the target cell. If DU_2's resources are successfully allocated, it will reply a UE CONTEXT SETUP RESPONSE message to CU_2.

[0060] Before performing mobility handover, mobility handover preparation is required. During the mobility handover preparation phase, the CU is mainly responsible for receiving the UE's measurement reports and making handover decisions based on these reports and other network parameters. The DU is mainly responsible for preparing the wireless resources required by the target base station during the mobility handover preparation phase. In scenarios where public networks and private networks with non-public networks coexist, especially in applications that require high bandwidth and low latency, in order to improve network performance and coverage, cross-site auxiliary carriers will be added during the mobility handover preparation process. However, the relevant technologies are currently under development. Figure 1a When configuring an inter-site secondary carrier during the mobility handover preparation process shown in the figure, there are the following problems on the handover target base station side and the secondary base station side where the secondary carrier is located:

[0061] (1) CU_2 does not support the configuration of the UE's secondary carrier based on the UE's service behavior during mobility handover. The 3GPP handover request (e.g., the 3GPP 38.423 protocol HANDOVER REQUEST) message does not convey the source base station's service behavior data, such as the UE's service volume and primary service direction. Therefore, the target base station cannot determine the configuration of the UE's secondary carrier based on the UE's service behavior data. The 3GPP 38.473 and 3GPP 38.463 protocols do not support the detection and reporting of the UE's uplink and downlink service volume and primary service direction.

[0062] (2) CU_2 does not support UE configuration of secondary carriers in cross-PLMN (3GPP 23.501 protocol inter-PLMN) scenarios. During the inter-site handover process, the target base station CU_2 does not transmit the UE serving PLMN information of each secondary cell in the secondary cell pre-establishment list (3GPP38.473 protocol SCell To BeSetup List) of the F1 interface. Therefore, it does not support UE configuration of secondary carriers in cross-PLMN scenarios. Figure 1b As shown, in the context of direct communication between DUs and DUs to configure cross-site auxiliary carriers, the cross-site side where the auxiliary carrier is located in the related art does not support obtaining the corresponding operator wireless resource configuration based on the UE service PLMN in the pre-established list of the secondary cell, thereby failing to meet the actual resource allocation needs of the operator and the dynamic balance of traffic between operators. Figure 1bAs shown, the primary carrier PCell of the UE is located in PLMN1, and the related technology does not support adding a secondary carrier Scell2 located in PLMN2 for the UE, that is, the related technology currently does not support adding and configuring a secondary carrier across PLMNs.

[0063] (3) The reasonable allocation of NPN private network resources cannot be guaranteed. The UE context setup request (UE CONTEXT SETUP REQUEST, 3GPP38.473 protocol) message sent by CU_2 does not carry all NPN subscription information to DU_2. When the UE is in the mobility handover process and the handover target adds a cross-site secondary carrier through direct communication between DU_2 and DU_3, ordinary PLMN UEs may preempt NPN private network resources, making it impossible to ensure the reasonable allocation of private network resources.

[0064] Based on this, the present application provides a secondary carrier configuration method, device, medium and program product, which are used to solve at least one problem existing on the switching source base station, switching target base station side and the secondary base station side where the secondary carrier is located when configuring a cross-site secondary carrier during the mobility switching preparation process.

[0065] Please refer to Figure 2a , is a schematic diagram of a method for configuring a secondary carrier provided in an embodiment of the present application, wherein the method enables the target base station to configure the secondary carrier by adding service status information, such as Figure 2a As shown, the configuration method of the secondary carrier provided in the embodiment of the present application includes but is not limited to steps S101 to S105:

[0066] Step S101: A target base station receives a handover request message from a source base station, where the handover request message includes service status information of a terminal UE.

[0067] The service status information of the UE includes at least one of the following:

[0068] Uplink traffic volume information, used to indicate whether the uplink traffic is in a large packet state or a small packet state;

[0069] Downlink traffic volume information, used to indicate whether the downlink traffic is in the large packet state or the small packet state;

[0070] The main service direction information is used to indicate whether the main service direction is an uplink service direction or a downlink service direction.

[0071] Step S102: The target base station determines a pre-established list of secondary cells according to the service status information.

[0072] The pre-established list of secondary cells includes the NR cell global identifier (NR Cell Global Identifier, NR CGI) of each secondary cell and the secondary cell index of each secondary cell.

[0073] Step S103: Determine a secondary base station according to the pre-established secondary cell list, and the target base station sends an inter-site secondary carrier establishment request message to the secondary base station.

[0074] Step S104: The target base station receives the cross-site secondary carrier establishment response message replied by the secondary base station.

[0075] Step S105: The target base station establishes a secondary carrier for the UE according to the cross-site secondary carrier establishment response message.

[0076] According to the solution of the embodiment of the present application, the target base station can obtain the service status information of the UE from the handover request message sent by the source base station, and then determine the cross-site secondary carrier configuration of the UE based on the service status information, output a pre-established secondary cell list, and send a cross-site secondary carrier establishment request message to the corresponding secondary base station based on the pre-established secondary cell list to establish a cross-site secondary carrier. This solves the technical problem in the current related art that the handover target side does not support on-demand allocation of UE secondary carriers during UE mobility handover. The handover target side reasonably decides the UE's secondary carrier configuration based on the UE's service status, ensuring that the UE's cross-site secondary carrier configuration can meet the UE's service needs while reducing the waste of secondary carrier resources.

[0077] The target base station includes a target centralized unit CU and a target distributed unit DU.

[0078] The target CU is configured to receive the handover request message, determine the secondary cell pre-established list according to the service status information in the handover request message, and send a UE context establishment request message including the secondary cell pre-established list to the target DU.

[0079] The target DU is configured to receive a UE context establishment request message, determine a secondary base station according to the secondary cell pre-establishment list in the UE context establishment request message, send an inter-site secondary carrier establishment request message to the secondary base station, and receive an inter-site secondary carrier establishment response message.

[0080] In the target base station, the target CU passes the secondary cell pre-establishment list to the target DU through the UE context establishment request message; the target DU determines the secondary base station according to the secondary cell pre-establishment list, and then sends a cross-site secondary carrier establishment request message to the DU of the determined secondary base station to request the establishment of a cross-site secondary carrier; the DU of the secondary base station returns a cross-site secondary carrier establishment response message to the target DU; the target DU can configure the UE's to-be-aggregated carrier according to the cross-site secondary carrier establishment response message, and then returns a UE context establishment response message to the target CU.

[0081] Illustratively, the cross-site secondary carrier establishment response message carries the secondary cell wireless dedicated admission resources and the lower RLC layer offload IP address (or referred to as RLC_L layer offload IP address) of the cross-site secondary carrier.

[0082] Establishing a cross-site secondary carrier according to the cross-site secondary carrier establishment response message includes:

[0083] The target DU configures the UE's carriers to be aggregated based on the secondary cell wireless dedicated admission resources of the cross-site secondary carrier and the RLC_L layer offload IP address of each secondary carrier, and replies with a UE context establishment response message to the target CU.

[0084] It should be noted that after the target DU receives the cross-site secondary carrier establishment response message, the following operations are also included:

[0085] The target DU sends an inter-site secondary carrier modification request message to the secondary base station. The inter-site secondary carrier modification request message carries coordination configuration information, and the coordination configuration information includes a pre-established secondary cell list.

[0086] The target DU receives the cross-site secondary carrier modification response message replied by the secondary base station.

[0087] The target base station uses a cross-site secondary carrier modification request message to carry the coordination information to the secondary base station. After the cross-site secondary carrier configuration is completed, when the secondary base station receives uplink control information sent by the UE including CSI reporting and / or downlink data AN feedback, it can determine the target primary base station or secondary base station corresponding to the uplink control information based on the above coordination configuration information.

[0088] In the embodiment of the present application, determining the pre-established list of secondary cells according to the service status information may include:

[0089] Determine the secondary carrier configuration of the UE according to the service status information, where the secondary carrier configuration includes adding a secondary carrier or deleting a secondary carrier;

[0090] In the case where the secondary carrier is configured to add a secondary carrier, determining a secondary carrier to be added;

[0091] A pre-established list of secondary cells is determined according to the secondary carrier to be added.

[0092] Exemplarily, determining the secondary carrier configuration of the UE according to the service status information may include one of the following:

[0093] When the uplink service of the UE changes from a small packet state to a large packet state, the secondary carrier configuration is determined to be an uplink secondary carrier;

[0094] When the downlink service of the UE enters the large packet state from the small packet state and the main service direction is the downlink service direction, determining the secondary carrier configuration is to add a downlink secondary carrier;

[0095] When the downlink service of the UE enters the large packet state from the small packet state and the main service direction is the uplink service direction, determining the secondary carrier configuration to add an uplink secondary carrier;

[0096] When both uplink and downlink services of the UE enter a small packet state from a large packet state, the secondary carrier configuration is determined to be deleted.

[0097] Please refer to Figure 2b , is a schematic diagram of a method for configuring a secondary carrier provided in an embodiment of the present application, the method including but not limited to the following steps:

[0098] Step S201: The target CU receives a handover request message, where the handover request message includes UE service state information detected by the source base station;

[0099] Step S202: The target CU determines a pre-established list of secondary cells according to the service status information, wherein the pre-established list of secondary cells carries the UE serving PLMN information of the secondary cells;

[0100] Step S203: The target CU sends a UE context establishment request message carrying a pre-established list of secondary cells to the target DU;

[0101] Step S204: The target DU receives the UE context establishment request message and determines the secondary base station according to the secondary cell pre-established list in the UE context establishment request message;

[0102] Step S205: The target DU sends an inter-site secondary carrier establishment request message to the secondary DU of the secondary base station. The inter-site secondary carrier establishment request message carries the UE serving PLMN information of the secondary cell.

[0103] Step S206: The target DU receives the cross-site secondary carrier establishment response message returned by the secondary DU of the secondary base station.

[0104] In an embodiment of the present application, the UE serving PLMN information of the secondary cell is added to the pre-established list of the secondary cell, and the target CU transmits the UE serving PLMN information of the secondary cell to the target DU through the pre-established list of the secondary cell. The target DU then transmits the UE serving PLMN information of the secondary cell to the secondary base station through a cross-site secondary carrier establishment request message, so that the secondary base station can obtain the radio resource configuration corresponding to the secondary carrier according to the UE serving PLMN information of the secondary cell, thereby solving the technical problem that the related art does not support the addition configuration of the secondary carrier in the cross-PLMN scenario.

[0105] Please refer to Figure 2c , is a schematic diagram of a process for establishing an XN link between a target base station and a secondary base station provided in an embodiment of the present application, the method including but not limited to the following steps:

[0106] Step S301: The target base station sends an XN establishment request message to the secondary base station;

[0107] Step S302: The target base station receives an XN setup response message from the secondary base station, where the XN setup response message includes gNB-DU system information of all serving cells.

[0108] Step S303: Save the base station distributed unit system information of all serving cells, wherein the base station distributed unit system information includes NPN-only information.

[0109] In the XN link establishment process between the target base station and the secondary base station in this embodiment of the application, the secondary base station sends the target base station an XN Establishment Response message carrying the gNB-DU System Information of all serving cells on the secondary base station side. The target base station can obtain the NPN-only information of the private network cells through the gNB-DU System Information. When configuring the addition of secondary carriers, the CU of the target base station can use the pre-acquired NPN-only information of the private network cells to select cross-site secondary carrier configurations, ensuring the proper allocation of private network radio resources.

[0110] Please refer to Figure 2d , is a schematic diagram of a method for configuring a secondary carrier provided in an embodiment of the present application, the method including but not limited to the following steps:

[0111] Step S401: The target CU receives a handover request message, wherein the handover request message includes service status information and a mobility restriction list of the UE, and the mobility restriction list includes NPN subscription information;

[0112] Step S402: The target CU determines the secondary carrier configuration of the UE according to the service status information;

[0113] Step S403: The target CU determines that the secondary carrier configuration is to add a secondary carrier, and then determines the secondary carrier to be added according to the NPN subscription information and the NPN-only information of the secondary cell;

[0114] Step S404: The target CU determines a pre-established list of secondary cells according to the secondary carrier to be added;

[0115] Step S405: The target CU sends a UE context establishment request message carrying a pre-established list of secondary cells to the target DU. The pre-established list of secondary cells includes UE serving PLMN information of the secondary cells.

[0116] Step S406: The target DU receives the UE context establishment request message and determines the secondary base station according to the pre-established secondary cell list in the UE context establishment request message;

[0117] Step S407: The target DU sends an inter-site secondary carrier establishment request message to the secondary DU of the secondary base station. The inter-site secondary carrier establishment request message carries the UE serving PLMN information of the secondary cell.

[0118] Step S408: The target DU receives the cross-site secondary carrier establishment response message returned by the secondary DU of the secondary base station.

[0119] In the embodiment of the present application, the target base station combines the NPN subscription information and the base station distributed unit system information (gNB-DU System Information) in the mobility restriction list to make a network access determination for the cross-site auxiliary carrier in advance, which can speed up the UE auxiliary carrier configuration process, improve the UE user experience, and solve the technical problem that the relevant technology does not support the reasonable allocation of NPN private network resources.

[0120] Please refer to Figure 2e , is a schematic diagram of a method for configuring a secondary carrier provided in an embodiment of the present application, the method including but not limited to the following steps:

[0121] Step S501: The target CU receives a handover request message, wherein the handover request message includes service status information and a mobility restriction list of the UE, and the mobility restriction list includes NPN subscription information;

[0122] Step S502: The target CU determines the secondary carrier configuration of the UE according to the service status information;

[0123] Step S503: The target CU determines that the secondary carrier configuration is to add a secondary carrier, and determines a secondary carrier to be added;

[0124] Step S504: The target CU determines a pre-established list of secondary cells according to the secondary carrier to be added;

[0125] Step S505: The target CU sends a UE context establishment request message carrying a secondary cell pre-established list and a mobility restriction list to the target DU. The secondary cell pre-established list includes the UE serving PLMN information of the secondary cell.

[0126] Step S506: The target DU receives the UE context establishment request message and determines the secondary base station according to the secondary cell pre-established list in the UE context establishment request message;

[0127] Step S507: The target DU sends an inter-site secondary carrier establishment request message to the secondary DU of the secondary base station. The inter-site secondary carrier establishment request message carries the UE serving PLMN information and the mobility restriction list of the secondary cell.

[0128] Step S508: The target DU receives the cross-site secondary carrier establishment response message returned by the secondary DU of the secondary base station.

[0129] In the embodiment of the present application, the F1 interface UE context establishment request message of the target CU carries a mobility restriction list including UE NPN subscription information to the target DU, which is then passed by the target DU to the secondary base station DU. The secondary base station DU performs PNI-NPN network UE admission control under network sharing, thereby ensuring the UE's cross-site secondary carrier access selection authority, effectively improving the configuration efficiency of adding secondary carriers during the handover process and the network experience of users accessing the network, and solving the technical problem that the relevant technology does not support the reasonable allocation of NPN private network resources.

[0130] An embodiment of the present application also provides a method for configuring a secondary carrier, which is applied to a source base station, and the method includes but is not limited to the following steps: sending a handover request message to a target base station, the handover request message carrying UE service status information detected by the source base station, so that the target base station determines a secondary cell pre-establishment list based on the service status information, determines a secondary base station based on the secondary cell pre-establishment list, and sends a cross-site secondary carrier establishment request message to the secondary base station.

[0131] It should be noted that the source base station includes the source CU, the source CU includes the source CU-CP and the source CU-UP, and the service status information includes at least one of the following: uplink service volume information for indicating that the uplink service is in a large packet state or a small packet state, downlink service volume information for indicating that the downlink service is in a large packet state or a small packet state, and main service direction information for indicating that the main service direction is the uplink service direction or the downlink service direction.

[0132] The process of acquiring downlink traffic information includes but is not limited to steps S601 to S604:

[0133] Step S601: The source CU-CP sends a downlink traffic detection request message to the source CU-UP.

[0134] Step S602: The source CU-UP sends a downlink traffic detection response message to the source CU-CP.

[0135] Step S603: The source CU-UP sets the downlink service to an initialization state, periodically obtains downlink service data volume according to a preset service detection window, and determines downlink service volume information based on the downlink service data volume obtained in each service detection window.

[0136] Step S604: The source CU-UP sends downlink traffic information to the source CU-CP.

[0137] Exemplarily, determining downlink service volume information based on the amount of downlink service data acquired in each service detection window includes one of the following:

[0138] (1) When the downlink service is in the initialization state and the downlink service data volume is greater than or equal to the preset large packet entry threshold, the downlink service is determined to have entered the large packet state and the large packet holding window length is started;

[0139] (2) When the downlink service is in the large packet state, the downlink service data volume is less than the preset large packet exit threshold, and the large packet holding window length is reached, the downlink service is determined to exit the large packet state;

[0140] (3) If the downlink service is in the large packet state, the downlink service data volume is less than the preset large packet exit threshold, and the large packet holding window has not yet ended, the downlink service is determined to enter the waiting to exit large packet state;

[0141] (4) If the downlink service is waiting to exit the large packet state and the downlink service data volume is greater than or equal to the preset large packet entry threshold, the downlink service is determined to enter the large packet state;

[0142] (5) When the downlink service is waiting to exit the large packet state, the downlink service data volume is less than the preset large packet exit threshold, and the large packet holding window length is reached, the downlink service is determined to exit the large packet state;

[0143] (6) When the downlink service is exiting the large packet state and the downlink service data volume is greater than or equal to the preset large packet entry threshold, the downlink service is determined to have entered the large packet state and the large packet holding window length is started;

[0144] (7) When the downlink service is in the initialization state and the downlink service data volume is less than the preset small packet entry threshold, it is determined that the downlink service enters the small packet state;

[0145] (8) When the downlink service is in the small packet state, the downlink service data volume is less than the preset small packet exit threshold, and the large packet holding window length has not yet expired, the downlink service is determined to be waiting to enter the small packet state;

[0146] (9) When the downlink service is waiting to enter the small packet state, the downlink service data volume is less than the preset small packet entry threshold, and the large packet holding window length is reached, the downlink service is determined to enter the small packet state;

[0147] (10) When the downlink service is in the waiting state to enter the small packet state and the downlink service data volume is greater than the preset small packet exit threshold, determine that the downlink service exits the small packet state;

[0148] (11) When the downlink service is in the small packet state, the downlink service data volume is greater than the preset small packet exit threshold, and the large packet holding window length is reached, the downlink service is determined to exit the small packet state;

[0149] (12) When the downlink service is in the small packet state, the downlink service data volume is greater than the preset small packet exit threshold, and the large packet holding window length has not yet expired, the downlink service is determined to exit the small packet state;

[0150] (13) When the downlink service is in the exit state of small packets, the downlink service data volume is less than the preset small packet entry threshold and the large packet holding window length has not been reached, the downlink service is determined to be in the waiting state of entering small packets;

[0151] (14) When the downlink service data volume is less than the preset small packet entry threshold and the large packet holding window length is reached, it is determined that the downlink service enters the small packet state.

[0152] Exemplarily, the process of acquiring uplink traffic information includes but is not limited to steps S701 to S704:

[0153] Step S701: The source CU-CP sends an uplink traffic volume and main traffic direction detection request message to the source DU;

[0154] Step S702: The source DU sends an uplink traffic volume and main traffic direction detection response message to the source CU-CP.

[0155] Step S703: The source DU sets the uplink service to the initialization state and periodically obtains the uplink service data volume and the downlink service data volume according to the preset service detection window;

[0156] Step S704: The source DU determines uplink service volume information according to the uplink service data volume, and determines main service direction information according to the uplink service data volume and the downlink service data volume;

[0157] Step S705: The source DU sends uplink traffic volume information and main traffic direction information to the source CU-CP.

[0158] In step S704, uplink traffic volume information is determined according to the uplink traffic data volume, and the specific process may include one of the following:

[0159] (1) When the uplink service is in the initialization state and the uplink service data volume is greater than the preset large packet entry threshold, the uplink service is determined to have entered the large packet state and the large packet holding window length is started;

[0160] (2) When the uplink service is in the large packet state, the uplink service data volume is less than the preset large packet exit threshold, and the large packet holding window length is reached, the uplink service is determined to exit the large packet state;

[0161] (3) When the uplink service is in the large packet state, the uplink service data volume is less than the preset large packet exit threshold, and the large packet holding window has not yet ended, the uplink service is determined to enter the waiting to exit large packet state;

[0162] (4) When the uplink service is in the waiting state to exit the large packet state and the uplink service data volume is greater than the preset large packet entry threshold, it is determined that the uplink service enters the large packet state;

[0163] (5) When the uplink service is waiting to exit the large packet state and the large packet holding window length is reached, it is determined that the uplink service exits the large packet state;

[0164] (6) When the uplink service exits the large packet state and the uplink service data volume exceeds the preset large packet entry threshold, it is determined that the uplink service enters the large packet state and the large packet holding window length timing is started;

[0165] (7) When the uplink service is in the initialization state and the uplink service data volume is less than the preset small packet entry threshold, it is determined that the uplink service enters the small packet state;

[0166] (8) When the uplink service is in the small packet state, the uplink service data volume is less than the preset small packet exit threshold, and the large packet holding window length has not yet expired, the uplink service is determined to be in the waiting state to enter the small packet state;

[0167] (9) When the uplink service is waiting to enter the small packet state, the uplink service data volume is less than the preset small packet entry threshold, and the large packet holding window length is reached, it is determined that the uplink service enters the small packet state;

[0168] (10) When the uplink service is in the waiting state to enter the small packet state and the uplink service data volume is greater than the preset small packet exit threshold, it is determined that the uplink service exits the small packet state;

[0169] (11) When the uplink service is in the small packet state, the uplink service data volume is greater than the preset small packet exit threshold, and the large packet holding window length is reached, the uplink service is determined to exit the small packet state;

[0170] (12) When the uplink service is in the small packet state, the uplink service data volume is greater than the preset small packet exit threshold, and the large packet holding window length has not yet expired, the uplink service is determined to exit the small packet state;

[0171] (13) When the uplink service is in the exit small packet state, the uplink service data volume is less than the preset small packet entry threshold and the large packet holding window length has not been reached, the uplink service is determined to be in the waiting state to enter the small packet state;

[0172] (14) When the uplink service data volume is less than the preset small packet entry threshold and the large packet holding window length is reached, it is determined that the uplink service enters the small packet state.

[0173] For example, please refer to Figure 6 , is a schematic diagram of a service large packet status determination process provided by an embodiment of the present application, such as Figure 6 As shown, when the large packet determination process starts, it is first initialized, the service state is set to the initialization state, and the service detection window length is set = window length coefficient * service statistics basic period;

[0174] a. When the service is in the initialization state and the first service detection window is reached, if the service data volume is greater than the large packet entry threshold, the service enters the large packet state and starts the large packet to hold the window length timing;

[0175] b. When the service is in a large packet state, periodic detection is performed based on the service detection window length. When the service detection window length is reached, if the service data volume is greater than the large packet entry threshold, the service maintains the large packet state and starts the large packet to hold the window length timing;

[0176] c. When the service is in a large packet state and the service detection window is long, if the service data volume is detected to be less than the large packet exit threshold and the large packet is kept in the window length, the service exits the large packet state;

[0177] d. When the service is in the large packet state and the service detection window is reached, if the service data volume is detected to be less than the large packet exit threshold and the large packet holding window length has not yet arrived, the service enters the waiting state to exit the large packet;

[0178] e. When the service exits the large packet state and the service detection window is long, if the service data volume is detected to be greater than the large packet entry threshold, the service enters the large packet state and starts the large packet to hold the window length timing;

[0179] f business to exit the large packet state, the business detection window length, if the detected business data volume is less than the large packet exit threshold, the business to maintain the exit large packet state;

[0180] g. The business is waiting to exit the large packet state. When the large packet holding window is reached, the business exits the large packet state;

[0181] h. When the service is waiting to exit the large packet state, the service detection window is long, if the service data volume is detected to be less than the large packet exit threshold, the service maintains the waiting state to exit the large packet;

[0182] i. When the service is waiting to exit the large packet state and the service detection window is reached, if the service data volume is detected to be greater than the large packet entry threshold, the service enters the large packet state and starts the large packet holding window length timing.

[0183] For example, please refer to Figure 7 , is a schematic diagram of a service packet status determination process provided by an embodiment of the present application, such as Figure 7 As shown, when the packet determination process starts, it is first initialized and the service state is set to the initialization state. The service detection window length = window length coefficient * service statistics basic period;

[0184] a. When the service is in the initialization state and the first service detection window is reached, if the service data volume is detected to be less than the small packet entry threshold, the service enters the small packet state;

[0185] b. When the service is in the small packet state, periodic detection is performed according to the service detection window length. When the service detection window length is reached, if the service data volume is detected to be less than the small packet entry threshold, the service maintains the small packet state;

[0186] c. When the service is in the small packet state, the large packet holding window length is reached or not reached, if the service data volume is detected to be greater than the small packet exit threshold, the service exits the small packet state;

[0187] d. When the service is in the small packet state, if the service data volume is detected to be less than the small packet exit threshold and the large packet hold window length has not expired, the service enters the waiting state for entering the small packet;

[0188] e. When the service is exiting the small packet state and the service detection window is reached, if the service data volume is detected to be less than the small packet entry threshold and the large packet is kept in the window length, the service enters the small packet state;

[0189] f. When the business is exiting the packet state, if the business data volume is detected to be greater than the packet exit threshold, the business maintains the exit packet state;

[0190] g. When the business is exiting the small packet state, if the business data volume is detected to be less than the small packet entry threshold and the large packet holding window length is not reached, the business enters the waiting state to enter the small packet;

[0191] h. When the business is waiting to enter the small packet state, if the business data volume is detected to be greater than the small packet exit threshold, the business enters the exit small packet state;

[0192] i. When the service is waiting to enter the small packet state, if the service data volume is detected to be less than the small packet entry threshold and the large packet holding window length is not reached, the service maintains the waiting state to enter the small packet;

[0193] j. When the service is waiting to enter the small packet state, if it is detected that the service data volume is less than the small packet entry threshold and the large packet holding window length is reached, the service enters the small packet state.

[0194] It should be noted that Figure 6 and Figure 7 The middle process can be used to determine the upstream business volume, and can also be used to determine the downstream business volume. Figure 6 The entry threshold for medium and large packets is greater than or equal to the exit threshold for large packets, and the large packet retention window is greater than or equal to the service detection window. Figure 7 The entry threshold for small and medium packets is less than or equal to the exit threshold for small packets, and the window length for large packets is greater than or equal to the service detection window length.

[0195] In step S704, the main service direction information is determined according to the uplink service data volume and the downlink service data volume, which specifically includes one of the following:

[0196] When the ratio of the uplink service data volume to the downlink service data volume is greater than a preset ratio threshold, the main service direction is determined to be the uplink service direction;

[0197] When the ratio of the downlink service data volume to the uplink service data volume is greater than a preset ratio threshold, it is determined that the main service direction is the downlink service direction.

[0198] For example, please refer to Figure 8 , is a method for determining the main business direction provided by an embodiment of the present application, such as Figure 8 As shown,

[0199] First, the service direction is set to the initial state, and the service detection window length = window length coefficient * service statistics basic period;

[0200] If the uplink data volume / downlink data volume is greater than the preset ratio threshold, the service direction is uplink, and the uplink service rate within the service detection window length is counted;

[0201] If the downlink data volume / uplink data volume is greater than the preset ratio threshold, the service direction is downlink, and the downlink service rate within the service detection window length is counted.

[0202] The secondary carrier configuration method provided in the embodiment of the present application, when applied to a secondary base station, includes but is not limited to steps S801 to S803:

[0203] Step S801: Receive an inter-site secondary carrier establishment request message sent by a target base station. The inter-site secondary carrier establishment request message is determined by the target base station based on a handover request message sent by a source base station. The handover request message carries service status information of the terminal UE.

[0204] Step S802: Determine the cross-site secondary carrier corresponding to the UE according to the cross-site secondary carrier establishment request message;

[0205] Step S803: Send an inter-site secondary carrier establishment response message to the target base station to establish the inter-site secondary carrier.

[0206] The cross-site secondary carrier establishment request message carries mobility restriction list information.

[0207] After determining the cross-site secondary carrier corresponding to the UE according to the cross-site secondary carrier establishment request message, determine whether the UE has the authority to access the cross-site secondary carrier according to the mobility restriction list information, and send a cross-site secondary carrier establishment response message to the target base station if the UE has the authority to access the cross-site secondary carrier.

[0208] It is understood that the secondary carrier configuration method provided in the embodiment of the present application further includes but is not limited to the following steps S901 to S902:

[0209] Step S901: Receive an XN establishment request message sent by a target base station;

[0210] Step S902: Send an XN setup response message to the target base station according to the XN setup request message, wherein the XN setup response message carries the base station distributed unit system information of all serving cells.

[0211] In an embodiment of the present application, after receiving the XN establishment request message sent by the target base station, the secondary base station replies to the target base station with an XN establishment response message, and carries the base station distributed unit system information (gNB-DU System Information) of all serving cells through the XN establishment response message, so that the target base station pre-obtains attributes such as cell NPN-only in the base station distributed unit system information of all serving cells on the cross-PLMN base station side. When performing cross-site secondary carrier configuration, the cell NPN-only attribute in the base station distributed unit system information of all serving cells can be used to perform network access determination of the cross-site secondary carrier in advance, thereby ensuring that the number of secondary carriers required by the UE can be successfully configured at one time, thereby improving the user's network access experience.

[0212] It is understood that the secondary carrier configuration method provided in the embodiment of the present application further includes but is not limited to the following steps S1001 to S1002:

[0213] Step S1001: Receive an inter-site secondary carrier modification request message sent by a target base station, and send an inter-site secondary carrier modification response message to the target base station, wherein the inter-site secondary carrier modification request message carries coordination configuration information, and the coordination configuration information includes a pre-established secondary cell list;

[0214] Step S1002: When uplink control information of the UE is received, the target base station or secondary base station corresponding to the uplink control information is determined in combination with the coordinated configuration information.

[0215] After the cross-site secondary carrier configuration is completed, when the secondary base station receives uplink control information including CSI reporting and / or downlink data AN feedback sent by the UE, it can determine the target primary base station or secondary base station corresponding to the uplink control information in combination with the coordinated configuration information.

[0216] The configuration method of the secondary carrier provided in the present application adds service status information carrying service behavior data information such as UE service volume size and main service direction to the handover request message, and the target base station allocates wireless resources on demand after obtaining it. A downlink service volume detection request message and its response message, and a downlink service volume reporting message are added between CU-CP and CU-UP; an F1 port uplink service volume and main service direction detection request message and its response message, and an uplink service volume and main service direction reporting message are added between CU-CP and DU; the CU transmits the UE service PLMN information of all service cells of the secondary base station to the DU through the F1 port, so that the UE can also add and configure secondary carriers in cross-PLMN scenarios, thereby improving the UE user experience; the target base station CU transmits all UE NPN subscription information to the DU through the F1UE context establishment request, and the DU then transmits it to the secondary base station DU where the secondary carrier is located, so that the UE can quickly add and configure cross-site secondary carriers in the handover scenario, which can ensure the reasonable allocation of wireless resources in the private network.

[0217] In an embodiment of the present application, a method for configuring a secondary carrier may include the following two steps:

[0218] 1. The UE accesses the source base station and completes the detection of the traffic volume and main service direction, as well as the determination of the secondary carrier configuration;

[0219] 2. The UE switches and completes the configuration of the cross-site secondary carrier based on the traffic volume and main service direction detected by the source base station.

[0220] Next, the steps of the above two embodiments are described in detail:

[0221] First, the UE accesses the source base station and completes the detection of the traffic volume and main traffic direction and the determination of the secondary carrier configuration.

[0222] After the UE accesses, the source base station (gNB) detects traffic volume information and primary traffic direction information. UE traffic volume information can be in one of the following states: uplink large packets, uplink small packets, downlink large packets, or downlink small packets. Therefore, traffic volume information detection can also be referred to as uplink and downlink large and small packet detection.

[0223] Please refer to Figure 3 , which is a schematic diagram of the interaction between uplink and downlink packet detection of the source base station provided in the embodiment of the present application, such as Figure 3 As shown, in this embodiment of the present application, the source base station is divided into CU and DU, where CU is further divided into CU-CP and CU-UP.

[0224] The detection and reporting of uplink traffic and main service direction are as follows:

[0225] The CU-CP decides whether to perform uplink traffic volume and main service direction detection. If the decision is to perform detection, an uplink traffic volume and main service direction detection request message is sent to the DU. The message carries the NR cell global identifier (NR CellGlobal Identifier, NR CGI) of the detection cell, an uplink traffic volume detection start / stop indication, and a main service direction detection start / stop indication. In this embodiment of the present application, uplink traffic volume detection can also be referred to as uplink large and small packet service detection.

[0226] After receiving the uplink traffic volume and main service direction detection request message, the DU MAC layer saves the message content, starts or stops the uplink traffic volume and main service direction detection of UEs in the cell based on the message content, and replies with an uplink traffic volume and main service direction detection response message;

[0227] The DU MAC layer detects the request content based on the stored uplink traffic volume and main service direction, and based on the UE large packet service detection process (see Figure 6 The process shown) and UE packet service detection process (refer to Figure 7 The process shown) detects the uplink size packets of the uplink business, and the detection process based on the main business direction (refer to Figure 8 The primary service direction is detected (see the process shown in the figure). When the periodic service detection window expires, if the uplink traffic volume or the primary service direction status changes, an uplink traffic volume and primary service direction reporting message is sent, carrying the UE's uplink traffic volume information and primary service direction information. Within the periodic service detection window, UE detection results are reported in batches. UEs that have not reported in the current detection cycle are reserved for reporting in the next detection cycle.

[0228] The DU MAC layer sends out a report message on the uplink traffic volume and the main service direction. After receiving the report message on the uplink traffic volume and the main service direction, the CU decides on the configuration of the secondary carrier.

[0229] The uplink packet size service detection is performed at the MAC layer. The MAC layer calculates the UE's uplink packet data volume within the service statistics basic period (the service statistics basic period is configurable and the default value can be set to 1s) based on the logical channel.

[0230] UE uplink data volume = primary carrier uplink data volume + secondary carrier uplink data volume;

[0231] Primary carrier uplink data volume = primary carrier uplink scheduling data + primary carrier uplink BSR;

[0232] Secondary carrier uplink data volume = secondary carrier uplink scheduling data + secondary carrier uplink BSR.

[0233] The amount of detection data within the service detection window length is further calculated based on the configured statistical window length coefficient; wherein,

[0234] Service detection window length = window length coefficient * service statistics basic period;

[0235] The window length coefficient can be configured and adjusted in integer multiples within a desired range (e.g., 1 to 1000). Afterwards, based on all logical channels associated with the UE, the data volume of all logical channels detected within the service detection window is further calculated, aggregated, and reported.

[0236] The specific process for detecting and reporting downlink traffic is as follows:

[0237] The CU-CP decides whether to perform downlink traffic detection. If so, the CU-CP sends a downlink traffic detection request message to the CU-UP, which carries a downlink traffic detection start / stop indication. In this embodiment of the present application, downlink traffic detection can also be referred to as downlink large and small packet traffic detection.

[0238] The CU-UP performs downlink large and small packet detection for downlink traffic based on the UE large packet detection process and the UE small packet detection process. If the downlink traffic status changes when the periodic traffic detection window expires, the CU-UP sends a downlink traffic report message to the CU-CP, carrying the UE's downlink traffic information. Within the periodic traffic detection window, each UE's detection results are reported in batches. UEs that did not report during the current detection period are reserved for reporting in the next detection period.

[0239] It should be noted that the specific process of CU-UP performing downlink large and small packet service detection is as follows:

[0240] After the downlink packet size detection switch is turned on, CU-UP calculates the amount of downlink packet data detected by the UE within the service statistics basic period (the service statistics basic period is configurable and the default value can be set to 1s) in units of DRB, and further calculates the amount of detection data within the service detection window length based on the configured statistical window length coefficient;

[0241] Service detection window length = window length coefficient * service statistics basic period;

[0242] The window length coefficient can be configured and adjusted in integer multiples within the desired range (e.g. 1 to 1000);

[0243] Afterwards, based on all DRBs associated with the UE, the data volume of all DRBs detected in the service detection window length is further calculated, summarized and reported to the CU-CP. The downlink large packet service detection module and the downlink small packet service detection module perform downlink large and small packet service detection based on the statistical downlink packet data volume.

[0244] It is understandable that UE large packet service detection can refer to Figure 6The process shown in the figure can be referred to for UE small packet service detection. Figure 7 The process shown.

[0245] The target base station configures the auxiliary carrier based on the traffic volume and main traffic direction detected by the source base station. Please refer to Figure 4 , is a schematic diagram of a secondary carrier configuration process proposed in an embodiment of the present application. Figure 4 As shown, in one example, the secondary carrier configuration process includes the following steps:

[0246] When the user traffic volume or main traffic direction changes, determine whether the secondary carrier configuration switch for the UE traffic volume and main traffic direction is turned on. If not, execute the original secondary carrier addition process;

[0247] If the UE traffic volume and the secondary carrier configuration switch of the main traffic direction are turned on, determine whether the maintained "secondary carrier adding UE traffic direction" is flipped or whether the traffic volume changes. If not, do not process the secondary carrier;

[0248] If the maintained "secondary carrier adding UE service direction" is reversed or the service volume changes, it is determined whether there is an existing secondary carrier. If so, the secondary carrier reconfiguration function is triggered. If not, the above secondary carrier addition decision is performed.

[0249] It should be noted that when the UE is not configured with a secondary carrier and the UE's uplink and / or downlink traffic changes from a small packet state to a large packet state, it can be considered that the current UE has no existing secondary carrier and needs to add a secondary carrier. When the UE has been configured with a secondary carrier and the traffic state of the uplink and downlink traffic changes from a large packet state to a small packet state, it can be considered that the current UE has an existing secondary carrier and the UE is reconfigured to a single carrier state, that is, the UE's secondary carrier is deleted.

[0250] The source base station sends a HANDOVER REQUEST message to the target base station. The HANDOVER REQUEST message carries a mobility restriction list information element (Mobility Restriction List defined in 3GPP 38.423 protocol) and additionally carries UE uplink and downlink packet status and main service direction information.

[0251] Then, the UE switches and completes the configuration of the cross-site secondary carrier based on the traffic volume and the main traffic direction. Figure 5 , is a flow chart of configuring a secondary carrier during mobility XN switching in a scenario where a public network and an NPN private network coexist, provided by an embodiment of the present application, which can be Figure 2e A complete flow chart of Figure 5As shown, the source base station is divided into CU_1 and DU_1, the target base station is divided into CU_2 and DU_2, and the secondary base station is divided into CU_3 and DU_3. The steps for configuring the cross-site secondary carrier based on the UE traffic volume and the main service direction during the handover process are as follows:

[0252] Step S1101: The target base station receives an XN handover request HANDOVER REQUEST message, and CU_2 obtains and saves the context in the handover request message.

[0253] In step S1102, the CU-CP in CU_2 sends a bearer context setup request message (3GPP 38.463 protocol BEARER CONTEXT SETUP REQUEST) to CU-UP. The request message carries the PDU Session Resource To Setup List, the AS Security Information and UE Security Capabilities carried in the handover request message, and the security information (Security Information) derived from the network management configuration information of the target base station, the UE downlink maximum aggregation bit rate (UE DLAggregate Maximum Bit Rate) and other information to CU-UP. The CU-CP obtains the CU-UP bearer context setup response message (3GPP 38.463 protocol BEARER CONTEXT SETUP RESPONSE), and the response message carries the PDU Session Resource Setup List (3GPP 38.463 protocol PDU Session Resource Setup List).

[0254] Step S1103: The CU-CP in CU_2 sends a UE context setup request message (UE CONTEXT SETUP REQUEST in 3GPP 38.473 protocol) to DU_2. The message carries the target cell NR CGI (SpCell ID in 3GPP 38.473 protocol), the primary cell serving cell index (ServCellIndex defined in 3GPP 38.473 protocol), UE capability information (UE-CapabilityRAT-ContainerList defined in 3GPP38.473 protocol), UE handover preparation information (Handover Preparation Information defined in 3GPP 38.473 protocol), a secondary cell pre-established list with the newly added UE serving PLMN information for each secondary cell (the secondary cell pre-established list is aligned with the SCell To Be Setup List defined in 3GPP 38.473 protocol), a mobility restriction list (aligned with the Mobility Restriction List defined in 38.423 protocol), and SRB1 and SRB2 pre-established lists (SRB to Be Setup List defined in 38.473 protocol). List), DRB pre-establishment list (DRB to Be Setup List defined in protocol 38.473), UE uplink maximum bit rate (gNB-DU UE Aggregate Maximum Bit Rate Uplink defined in protocol 38.473);

[0255] Step S1104: DU_2 obtains the UE context establishment information in the received F1 interface UE context establishment request message;

[0256] Step S1105: Configure the cross-site auxiliary carrier:

[0257] (1) The target base station DU_2 determines that the SCell (secondary carrier) in the secondary cell pre-establishment list information element is not within the cell range configured by gNodeB_2, but the gNodeB_3 to which the SCell belongs has a CA collaborative relationship with the current gNodeB_2 in a MAC layer logical connection. DU_2 sends an inter-site secondary carrier setup request message to DU_3 where the SCell is located. The message information elements include: the global gNB ID of the primary cell to which the UE is switching in gNodeB_2, the global gNB ID of gNodeB_3 where the secondary cell is located, the NR CGI of the primary cell, information related to the UE secondary carrier: the secondary carrier identifier (SCellIndex) in the UE, the NR CGI of the secondary cell requested to be added, the CA type (whether uplink CA is supported), the physicalCellGroupConfig and mac-CellGroupConfig information of the secondary carrier configured for the UE on the inter-site gNB_3 DU_3 side, the C-RNTI (Cell Radio Network Temporary Identifier), the UE capability information and mobility restriction list information, the reference admission resource of the SCell in DU_3: the UE primary cell dedicated radio admission resource (spCellConfigDedicated information, aligned with the primary cell dedicated configuration information of the 3GPP 38.331 protocol), the signaling radio bearer (SRB) and data radio bearer (DRB) of the UE in the secondary carrier. bearer, DRB) and the source DU primary carrier RLC_H offload IP address and other information.

[0258] After processing, DU_3 replies with a cross-station secondary carrier establishment response message, which carries the secondary cell wireless dedicated admission resources of the SCell allocated by the target station (aligned with the secondary cell dedicated configuration SCellConfigDedicated of the 3GPP 38.331 protocol) and the RLC_L layer offload IP address of the SCell allocated by the target station.

[0259] (2) DU_2 receives the cross-site auxiliary carrier establishment response message from DU_3.

[0260] (3) After DU_2 collects all the UE wireless dedicated reception resources of the SCell, it staggers and configures them with the resources of the target base station's main carrier cell_1; at the same time, it notifies the RLC layer deployment module of the main control DU_2 where the main carrier cell_1 is located of the RLC offload target IP address of the DU where the SCell is located.

[0261] (4) DU_2 sends a cross-site secondary carrier modification request message to DU_3 to notify the coordinated configuration information. The coordinated configuration information includes the wireless dedicated admission resource spCellConfigDedicated of the primary carrier of the UE, the wireless dedicated admission resource (SCellConfigDedicated) of all secondary carriers of the UE, the physical cell identifiers, carrier identifiers and NR cell global identifiers of all carriers to be aggregated, the NR cell global identifier of the primary carrier, the serving cell index of the primary carrier, and the pre-established list of secondary cells.

[0262] The secondary carrier establishment request message sent by DU_2 to DU_3 where the SCell is located carries the mobility restriction list information transmitted by CU_2. After receiving it, DU_3 uses the terminal UE NPN subscription information in the mobility restriction list combined with the NPN network configuration information supported by each DU secondary cell to make an SCell acceptance decision, thereby deciding to add cross-site secondary carriers in the NPN scenario.

[0263] The base station flexibly allocates radio resources based on the operator's PLMN information, meeting the operator's actual resource allocation needs, achieving dynamic balancing of traffic between operators, and improving spectrum utilization efficiency. The secondary carrier establishment request message sent by DU_2 to DU_3, where the SCell resides, carries the serving PLMN information passed by CU_2. DU_3 then uses this serving PLMN information to obtain the secondary cell radio resource configuration allocated to the corresponding UE.

[0264] Step S1106: DU_2 replies with a UE CONTEXT SETUP RESPONSE message (3GPP 38.473 protocol) at the F1 interface to CU_2. The message carries cellGroupId, rlc-BearerToAddModList, rlc-BearerToReleaseList (the source base station UE rlc-BearerToAddModList carried in the Handover Preparation Information), mac-CellGroupConfig, physicalCellGroupConfig, spCellConfig, sCellToAddModList, and sCellToReleaseList (the source base station UE sCellToAddModList carried in the HandoverPreparation Information).

[0265] Step S1107: The CU-CP in CU_2 sends a bearer context modification request message (3GPP 38.463 protocol BEARER CONTEXT MODIFICATION REQUEST) to the CU-UP. The request message carries a PDU Session Resource To Modify List (PDU Session Resource To Modify List) containing the downlink user plane transport layer address information of each DRB and obtains a CU-UP bearer context modification response message (BEARER CONTEXT MODIFICATION RESPONSE message defined in the 3GPP 38.463 protocol).

[0266] Step S1108: The target base station replies with a handover request response message (HANDOVERREQUEST ACKNOWLEDGE message defined in 3GPP 38.423) to the source base station, which includes the transparently transmitted handover reconfiguration RRCReconfiguration message content;

[0267] Step S1109: The source base station sends a handover reconfiguration message (RRCReconfiguration message defined in 3GPP 38.331 protocol) to the UE.

[0268] Step S1110: The source base station sends an SN STATUS TRANSFER message to the target base station, which carries the uplink PDCP SN reception status and the downlink PDCP SN transmission status; the target base station receives the PDCP SN information and applies it to the retransmitted or newly transmitted PDCP SDU message;

[0269] Step S1111: The target base station receives an RRC reconfiguration complete message (RRCReconfigurationComplete message defined in 3GPP 38.331 protocol) from the terminal UE.

[0270] Step S1112: Target base station CU_2 sends an F1 interface reconfiguration complete indication message (UE CONTEXT MODIFICATION REQUEST with RRCReconfiguration Complete Indicator according to 3GPP 38.473 protocol). After receiving the forwarded F1 interface reconfiguration complete indication message, DU_2 implements the configuration of each 3GPP service protocol layer. DU_2 then sends a cross-site secondary carrier reconfiguration complete confirmation message to DU_3.

[0271] Step S1113: The target base station CU_2 receives the F1 interface reconfiguration completion indication response message (UE CONTEXT MODIFICATION RESPONSE message defined in 3GPP 38.473 protocol);

[0272] Step S1114: The target base station CU_2 sends a PATH SWITCH REQUEST message to the core network and waits for processing of an end marker message sent by the core network.

[0273] Step S1115: The target base station CU_2 receives the PATH SWITCH REQUEST ACKNOWLEDGE message.

[0274] Step S1116: The target base station CU_2 sends an XN interface context release indication UE CONTEXT RELEASE to the source base station CU_1.

[0275] Step S1117: After the secondary carrier switching process is completed, the CU-CP of CU_2 decides to start and stop uplink and downlink packet detection; subsequently, the target base station performs a secondary carrier reconfiguration process based on the traffic volume and main traffic direction.

[0276] In one embodiment of the present application, in a scenario where a public network and an NPN private network coexist, the inter-site source base station and the target base station configure the secondary carrier switch based on the UE traffic volume and the main service direction. During the mobility handover process, the DU on the target base station side and the DU on the secondary base station side communicate directly, and the process of configuring the cross-site secondary carrier is as follows:

[0277] The target eNB sends an XN setup request message (XN SETUP REQUEST message defined in 3GPP 38.423) to the secondary eNB where the secondary carrier is located in advance. The secondary eNB where the secondary carrier is located returns the gNB-DU system information of all serving cells (gNB-DU System Information defined in 3GPP 38.473) to the target eNB by adding it to the XN setup response message (XN SETUP RESPONSE message defined in 3GPP 38.423). The target eNB obtains and saves the information.

[0278] In the scenario where the public network and NPN private network coexist, after the target base station receives the UE XN handover request message (HANDOVER REQUEST message defined in the 3GPP 38.423 protocol) sent by the source base station, and before the target base station CU sends a UE context establishment request message carrying a pre-established secondary carrier list to the DU, the target base station CU combines the UE mobility restriction list information in the handover request message and the base station distributed unit system information of all serving cells pre-acquired by the target base station before the UE switches in, and can flexibly select the cross-site secondary carrier configured by the UE in advance.

[0279] The target base station CU-CP outputs a secondary carrier pre-establishment list by combining the UE mobility restriction list information and the base station distributed unit system information pre-acquired by the target base station before the UE switches in.

[0280] The above method can speed up the process of UE successfully configuring the secondary carrier, ensure the reasonable allocation of NPN private network resources, and improve the user experience of UE.

[0281] For example, the XN target base station where the public network UE is located is set to gNB. The public network UE pre-determines in the CU of the gNB that two cross-site secondary carriers need to be added, namely SCell_1 of gNB_1 and SCell_2 of gNB_2. The UE NPN subscription information is carried to the secondary base stations gNB_1 and gNB_2 by carrying the mobility restriction list through the F1 interface UE context establishment request message to match the NPN-only and other attributes of the corresponding cells. If SCell_1 matches successfully and SCell_2 fails to match, considering the handover delay performance, the UE can only successfully configure one cross-site secondary carrier at the same time during the XN handover process; however, the XN target base station CU of the present application obtains the cell NPN-only and other attributes in the base station distributed unit system information of all serving cells of the secondary base station in advance. The UE can perform network access judgment of the cross-site secondary carrier in advance at the XN target base station CU, thereby ensuring that the required number of secondary carriers can be successfully configured in this process, thereby improving the user's network access experience.

[0282] The present application also provides a communication device, such as Figure 9 As shown, the communication device 1400 includes:

[0283] one or more processors 1410;

[0284] The memory 1420 stores one or more programs. When the one or more programs are executed by the one or more processors 1410, the one or more processors 1410 implement the secondary carrier configuration method described in any of the above embodiments.

[0285] The memory 1420 is a non-transient network system that can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory 1420 may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 1420 may optionally include a memory 1420 remotely located relative to the processor 1410, and these remote memories 1420 may be connected to the processor 1410 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0286] The memory 1420 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1420 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1420 and is called by the processor 1410 to execute the methods of the embodiments of this application.

[0287] The processor 1410 can be implemented using a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0288] In some embodiments, the communication device further comprises:

[0289] Input / output interface, used to realize information input and output;

[0290] Communication interface, used to realize communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, Wi-Fi, Bluetooth, etc.);

[0291] A bus that transmits information between various components of the device (e.g., the processor 1410, memory 1420, input / output interfaces, and communication interfaces);

[0292] The processor 1410 , the memory 1420 , the input / output interface, and the communication interface can be communicatively connected to each other within the device via a bus.

[0293] An embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the method for configuring a secondary carrier described in any of the above embodiments.

[0294] An embodiment of the present application further provides a computer program product, including a computer program or computer instructions, where the computer program or computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, so that the computer device executes the secondary carrier configuration method described in any of the above embodiments.

[0295] The system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0296] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0297] Those skilled in the art will appreciate that all or some of the steps and systems in the method disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, and the computer-readable medium can include computer storage media (or non-transitory media) and communication media (or temporary media). As known to those skilled in the art, the term computer storage media is included in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data) and is volatile and non-volatile, removable, and non-removable. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0298] It should be understood that in this application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0299] The above description of some embodiments of the present application with reference to the accompanying drawings does not limit the scope of the present invention. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present invention shall be within the scope of the present application.

Claims

1. A method for configuring a secondary carrier, applied to a target base station, the method comprising: receiving a handover request message, wherein the handover request message includes service status information of the terminal UE; determining a pre-established list of secondary cells according to the service status information; determining a secondary base station according to the secondary cell pre-establishment list, and sending an inter-site secondary carrier establishment request message to the secondary base station, so that the secondary base station replies with an inter-site secondary carrier establishment response message according to the inter-site secondary carrier establishment request message; The cross-site secondary carrier establishment response message is received, and a secondary carrier of the UE is established according to the cross-site secondary carrier establishment response message.

2. The method according to claim 1, characterized in that The target base station includes a target centralized unit CU and a target distributed unit DU; The target CU is configured to receive the handover request message, determine the secondary cell pre-established list according to the service status information in the handover request message, and send a UE context establishment request message including the secondary cell pre-established list to the target DU; The target DU is configured to receive the UE context establishment request message, determine a secondary base station according to the secondary cell pre-establishment list in the UE context establishment request message, send the cross-site secondary carrier establishment request message to the secondary base station, and receive the cross-site secondary carrier establishment response message.

3. The method according to claim 2, characterized in that The UE context establishment request message includes UE serving public land mobile network PLMN information of the secondary cell.

4. The method according to claim 3, characterized in that The UE serving PLMN information of the secondary cell is carried in the pre-established list of the secondary cell.

5. The method according to any one of claims 1 to 4, characterized in that: The cross-site secondary carrier establishment request message includes UE serving PLMN information of the secondary cell.

6. The method according to claim 1 or 2, characterized in that The determining the pre-established list of secondary cells according to the service status information includes: Determining a secondary carrier configuration of the UE according to the service status information, where the secondary carrier configuration includes adding a secondary carrier or deleting a secondary carrier; In a case where the secondary carrier is configured to add a secondary carrier, determining a secondary carrier to be added; The pre-established list of secondary cells is determined according to the secondary carrier to be added.

7. The method according to claim 6, characterized in that The service status information includes at least one of the following: Uplink traffic volume information, used to indicate whether the uplink traffic is in a large packet state or a small packet state; Downlink traffic volume information, used to indicate whether the downlink traffic is in the large packet state or the small packet state; The main service direction information is used to indicate whether the main service direction is an uplink service direction or a downlink service direction.

8. The method according to claim 7, characterized in that The determining the secondary carrier configuration of the UE according to the service status information includes one of the following: When the uplink service of the UE enters the large packet state from the small packet state, determining that the secondary carrier configuration is to add an uplink secondary carrier; When the downlink service of the UE enters the large packet state from the small packet state and the main service direction is the downlink service direction, determining that the secondary carrier configuration is to add a downlink secondary carrier; When the downlink service of the UE enters the large packet state from the small packet state and the main service direction is the uplink service direction, determining that the secondary carrier configuration is to add an uplink secondary carrier; When both the uplink and downlink services of the UE enter the small packet state from the large packet state, it is determined that the secondary carrier configuration is to delete the secondary carrier.

9. The method according to claim 8, characterized in that The handover request message further includes a mobility restriction list, where the mobility restriction list includes non-public network (NPN) subscription information.

10. The method according to claim 9, characterized in that Before determining the pre-established list of secondary cells according to the service status information, the method further includes: Sending an XN establishment request message to the secondary base station; receiving an XN setup response message from the secondary base station, wherein the XN setup response message includes base station distributed unit system information of all serving cells; The base station distributed unit system information of all the serving cells is saved.

11. The method according to claim 10, characterized in that The base station distributed unit system information includes NPN-only information, and when the secondary carrier is configured to add a secondary carrier, determining the secondary carrier to be added includes: In a case where the secondary carrier is configured to add a secondary carrier, the secondary carrier to be added is determined according to the NPN subscription information and the NPN-only information.

12. The method according to claim 9, characterized in that The UE context establishment request message includes the mobility restriction list; The cross-site secondary carrier establishment request message includes the mobility restriction list; The secondary base station determines, according to the NPN subscription information in the mobility restriction list, whether the UE has the authority to access the secondary carrier.

13. The method according to claim 1, wherein The cross-site secondary carrier establishment response message includes the secondary cell wireless dedicated admission resource of the cross-site secondary carrier and the lower radio link layer control protocol RLC layer IP address of each secondary carrier; The establishing the cross-site secondary carrier according to the cross-site secondary carrier establishment response message includes: The target DU configures the carrier to be aggregated of the UE according to the secondary cell wireless dedicated admission resources of the cross-site secondary carrier and the lower RLC layer offload IP address of each secondary carrier, and sends a UE context establishment response message to the target CU.

14. The method according to claim 2, characterized in that The target DU is further configured to send a cross-site secondary carrier modification request message to the secondary base station, and receive a cross-site secondary carrier modification response message from the secondary base station; The cross-site secondary carrier modification request message carries coordination configuration information; After receiving the uplink control information from the UE, the secondary base station determines the target base station or the secondary base station corresponding to the uplink control information according to the coordination configuration information.

15. A method for configuring a secondary carrier, applied to a source base station, the method comprising: A handover request message is sent to a target base station, where the handover request message carries service status information of the terminal UE, so that the target base station determines a pre-established list of secondary cells according to the service status information.

16. The method according to claim 15, characterized in that The service status information includes at least one of the following: Uplink traffic volume information, used to indicate whether the uplink traffic is in a large packet state or a small packet state; Downlink traffic volume information, used to indicate whether the downlink traffic is in the large packet state or the small packet state; The main service direction information is used to indicate whether the main service direction is an uplink service direction or a downlink service direction.

17. The method according to claim 15, characterized in that The source base station includes a source CU, the source CU includes a source CU-CP and a source CU-UP, and the process of acquiring the downlink traffic volume information includes: The source CU-CP sends a downlink traffic detection request message to the source CU-UP; The source CU-UP sends a downlink traffic detection response message to the source CU-CP; The source CU-UP sets the downlink service of the UE to an initialized state, periodically obtains the downlink service data volume of the UE according to a preset service detection window, and determines the downlink service volume information for the downlink service data volume obtained in each service detection window; The source CU-UP sends the downlink traffic volume information to the source CU-CP.

18. The method according to claim 17, characterized in that The determining the downlink service volume information based on the downlink service data volume obtained for each service detection window includes one of the following: When the downlink service is in the initialization state and the downlink service data volume is greater than the preset large packet entry threshold, determining that the downlink service enters the large packet state and starting the large packet holding window length timing; When the downlink service is in a large packet state, the downlink service data volume is less than a preset large packet exit threshold, and the large packet holding window length is reached, determining that the downlink service exits the large packet state; When the downlink service is in a large packet state, the downlink service data volume is less than a preset large packet exit threshold, and the large packet holding window has not yet ended, determining that the downlink service enters a waiting to exit large packet state; When the downlink service is in a waiting state to exit the large packet state and the downlink service data volume is greater than a preset large packet entry threshold, determining that the downlink service enters the large packet state; When the downlink service is in a waiting state to exit the large packet state and the large packet holding window length is reached, determining that the downlink service exits the large packet state; When the downlink service is exiting the large packet state and the downlink service data volume is greater than the preset large packet entry threshold, it is determined that the downlink service has entered the large packet state and the large packet holding window length is started; When the downlink service is in the initialization state and the downlink service data volume is less than a preset small packet entry threshold, determining that the downlink service enters the small packet state; When the downlink service is in a small packet state, the downlink service data volume is less than a preset small packet exit threshold, and the large packet holding window length has not yet expired, determining that the downlink service is waiting to enter a small packet state; When the downlink service is waiting to enter the small packet state, the downlink service data volume is less than the preset small packet entry threshold and the large packet holding window length is reached, determining that the downlink service enters the small packet state; When the downlink service is waiting to enter the small packet state and the downlink service data volume is greater than a preset small packet exit threshold, determining that the downlink service exits the small packet state; When the downlink service is in a small packet state, the downlink service data volume is greater than a preset small packet exit threshold, and the large packet holding window length is reached, determining that the downlink service exits the small packet state; When the downlink service is in a small packet state, the downlink service data volume is greater than a preset small packet exit threshold, and the large packet holding window length has not expired, determining that the downlink service exits the small packet state; When the downlink service is in the exit small packet state, the downlink service data volume is less than the preset small packet entry threshold and the large packet holding window length has not been reached, determining that the downlink service is in the waiting to enter small packet state; When the downlink service data volume is less than a preset small packet entry threshold and the large packet holding window length is reached, it is determined that the downlink service enters the small packet state.

19. The method according to claim 13, wherein The source base station includes a source CU and a source DU, the source CU includes a source CU-CP, and the process of acquiring the uplink traffic volume information and the main service direction information includes: The source CU-CP sends an uplink traffic volume and main service direction detection request message to the source DU; The source DU sends an uplink traffic volume and main service direction detection response message to the source CU-CP; The source DU sets the uplink service to an initialization state and periodically obtains the uplink service data volume and the downlink service data volume according to a preset service detection window; The source DU determines the uplink service volume information according to the uplink service data volume, and determines the main service direction information according to the uplink service data volume and the downlink service data volume; The source DU sends the uplink traffic volume information and the main traffic direction information to the source CU-CP.

20. The method according to claim 16, wherein The determining the uplink traffic volume information according to the uplink traffic data volume includes one of the following: When the uplink service is in the initialization state and the uplink service data volume is greater than a preset large packet entry threshold, determining that the uplink service enters the large packet state and starting the large packet holding window length timing; When the uplink service is in a large packet state, the uplink service data volume is less than a preset large packet exit threshold, and the large packet holding window length is reached, determining that the uplink service exits the large packet state; When the uplink service is in a large packet state, the uplink service data volume is less than a preset large packet exit threshold, and the large packet holding window has not yet ended, determining that the uplink service enters a waiting to exit large packet state; When the uplink service is in a waiting state to exit the large packet state and the data volume of the uplink service is greater than a preset large packet entry threshold, determining that the uplink service enters the large packet state; When the uplink service is in a waiting state to exit the large packet state and the large packet holding window length is reached, determining that the uplink service exits the large packet state; When the uplink service is exiting the large packet state and the uplink service data volume is greater than a preset large packet entry threshold, determining that the uplink service has entered the large packet state and starting the large packet holding window length timing; When the uplink service is in the initialization state and the uplink service data volume is less than a preset small packet entry threshold, determining that the uplink service enters the small packet state; When the uplink service is in a small packet state, the uplink service data volume is less than a preset small packet exit threshold, and the large packet holding window length has not expired, determining that the uplink service is waiting to enter a small packet state; When the uplink service is waiting to enter the small packet state, the uplink service data volume is less than the preset small packet entry threshold and the large packet holding window length is reached, determining that the uplink service enters the small packet state; When the uplink service is waiting to enter the small packet state and the uplink service data volume is greater than a preset small packet exit threshold, determining that the uplink service exits the small packet state; When the uplink service is in a small packet state, the uplink service data volume is greater than a preset small packet exit threshold, and the large packet holding window length is reached, determining that the uplink service exits the small packet state; When the uplink service is in a small packet state, the uplink service data volume is greater than a preset small packet exit threshold, and the large packet holding window length has not expired, determining that the uplink service exits the small packet state; When the uplink service is in the exit small packet state, the uplink service data volume is less than the preset small packet entry threshold and the large packet holding window length has not been reached, determining that the uplink service is in the waiting to enter small packet state; When the uplink service data volume is less than a preset small packet entry threshold and the large packet holding window length is reached, it is determined that the uplink service enters the small packet state.

21. The method according to claim 16, wherein The determining the main service direction information according to the uplink service data volume and the downlink service data volume includes one of the following: When a ratio obtained by dividing the uplink service data volume by the downlink service data volume is greater than a preset ratio threshold, determining that the main service direction is the uplink service direction; When a ratio obtained by dividing the downlink service data volume by the uplink service data volume is greater than a preset ratio threshold, it is determined that the main service direction is the downlink service direction.

22. The method according to claim 12, wherein: The handover request message further includes a mobility restriction list, where the mobility restriction list includes non-public network (NPN) subscription information.

23. A method for configuring a secondary carrier, applied to a secondary base station, the method comprising: receiving a cross-site secondary carrier establishment request message from a target base station; The cross-site secondary carrier establishment response message is sent to the target base station according to the cross-site secondary carrier establishment request message, so that the target base station establishes the secondary carrier of the UE according to the cross-site secondary carrier establishment response message.

24. The method according to claim 23, wherein The cross-site secondary carrier establishment request message includes UE serving PLMN information of the secondary cell; after receiving the cross-site secondary carrier establishment request message from the target base station, the method further includes: The radio resource configuration corresponding to the secondary carrier is acquired according to the UE serving PLMN information of the secondary cell.

25. The method according to claim 23, characterized in that The cross-site secondary carrier establishment request message further includes a mobility restriction list, where the mobility restriction list includes non-public network (NPN) subscription information; and the sending the cross-site secondary carrier establishment response message to the target base station according to the secondary cell radio resource configuration corresponding to the UE includes: Determining a secondary carrier to be added according to the secondary cell radio resource configuration corresponding to the UE; determining, according to the NPN subscription information in the mobility restriction list, whether the UE has permission to access the secondary carrier to be added; In a case where the UE has the permission to access the to-be-added secondary carrier, the cross-site secondary carrier establishment response message is sent to the target base station.

26. The method according to claim 23, wherein The method further comprises: Receiving an XN establishment request message sent by the target base station; An XN setup response message is sent to the target base station according to the XN setup request message, wherein the XN setup response message carries base station distributed unit system information of all serving cells, and the base station distributed unit system information includes NPN-only information.

27. The method according to claim 23, characterized in that The cross-site secondary carrier establishment response message includes the secondary cell wireless dedicated admission resources and the lower RLC layer offload IP address of the cross-site secondary carrier.

28. The method according to claim 23, wherein The method further comprises: receiving an inter-site secondary carrier modification request message from the target base station, wherein the inter-site secondary carrier modification request message includes coordination configuration information; Sending a cross-site secondary carrier modification response message to the target base station; When uplink control information is received from the UE, the target base station or the secondary base station corresponding to the uplink control information is determined according to the coordinated configuration information.

29. A communication device comprising: one or more processors; A memory having one or more computer programs stored thereon, wherein when the one or more computer programs are executed by the one or more processors, the one or more processors implement: the method for configuring the auxiliary carrier according to any one of claims 1 to 14, the method for configuring the auxiliary carrier according to any one of claims 15 to 22, or the method for configuring the auxiliary carrier according to any one of claims 23 to 29.

30. A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements: the auxiliary carrier configuration method according to any one of claims 1 to 14, or the auxiliary carrier configuration method according to any one of claims 15 to 22, or the auxiliary carrier configuration method according to any one of claims 23 to 29.

31. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements: the method for configuring a secondary carrier according to any one of claims 1 to 14, or the method for configuring a secondary carrier according to any one of claims 15 to 22, or the method for configuring a secondary carrier according to any one of claims 23 to 29.

Images