Data transmission method, barred cell determination method, base station and communication system

Abstract

Provided in the present disclosure are a data transmission method, a barred cell determination method, a base station and a communication system. The data transmission method comprises: a base station centralized entity receives a serving cell reduced capability user equipment (RedCap UE) configuration related information, which is sent by a base station separation entity by means of an interface message in a base station, the serving cell RedCap UE configuration related information comprising at least one of a cell bar identifier of a RedCap UE of a single receiver (Rx), a cell bar identifier of a RedCap UE of a dual Rx, a cell bar identifier of an enhanced reduced capability user equipment (eRedCap UE) of the single Rx, a cell bar identifier of an eRedCap UE of the dual Rx and a cell bar identifier of a half-duplex RedCap UE; and when the serving cell RedCap UE configuration related information is present in a serving cell information field, the base station centralized entity determines, according to the serving cell RedCap UE configuration related information, to provide in system information access and reselection configuration information corresponding to different types of RedCap UEs.

Description

Data transmission method, prohibited cell determination method, base station and communication system

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure is based on and claims priority to an application with CN application number 202311048962.X and filing date August 18, 2023. The disclosure content of the CN application is hereby introduced as a whole into this disclosure. Technical Field

[0003] The present disclosure relates to the field of wireless communication technology, and in particular to a data transmission method, a prohibited cell determination method, a base station, and a communication system. Background Art

[0004] 5G application scenarios include enhanced mobile broadband (eMBB), massive machine type of communication (mMTC), ultra reliable low latency communications (uRLLC), and time sensitive communication (TSC). However, some use cases require wireless network communication capabilities that exceed those of low power wide area (LPWA) technologies, but lower than those of uRLLC and eMBB. To meet the needs of terminal IoT applications such as industrial wireless sensors, video surveillance, and wearable devices, 5G introduces the concept of reduced capability (RedCap) lightweight technology. Based on RedCap, it can reduce device complexity and cost, size, and energy consumption, and can also provide services in scenarios with limited coverage beyond eMBB, mMTC, and URLLC.

[0005] Summary of the Invention

[0006] According to one aspect of an embodiment of the present disclosure, a data transmission method is provided, including: a base station centralized entity receives service cell reduced capability user equipment RedCap UE configuration related information sent by a base station separated entity through an interface message within the base station, wherein the service cell RedCap UE configuration related information includes: a cell prohibition mark of a RedCap UE with a single receiver Rx, a cell prohibition mark of a RedCap UE with dual Rx, a cell prohibition mark of an enhanced reduced capability user equipment eRedCap UE with a single Rx, a cell prohibition mark of an eRedCap UE with dual Rx, and a cell prohibition mark of a half-duplex RedCap UE, and the base station centralized entity and the base station separated entity both belong to the first base station; when the service cell RedCap UE configuration related information exists in the service cell information field, the base station centralized entity determines to provide access and reselection configuration information corresponding to different types of reduced capability user equipment in the system information based on the service cell RedCap UE configuration related information.

[0007] Optionally, the access and reselection configuration information includes at least one of the following: access frequencies corresponding to different types of reduced-capability user equipments, and same-frequency reselection identifiers of different types of reduced-capability user equipments.

[0008] Optionally, the same-frequency reselection identifiers of different types of reduced-capability user equipment include: a reselection identifier of a RedCap UE and a reselection identifier of an eRedCap UE.

[0009] Optionally, the interface message within the base station includes: an F1 interface establishment request message, an F1 interface establishment response message, and a next generation radio access network NG-RAN node configuration update message.

[0010] Optionally, the serving cell RedCap UE configuration related information further includes: a RedCap broadcast message field, wherein the RedCap broadcast message field is used to indicate user equipment that is allowed to access the first base station.

[0011] Optionally, an uplink radio resource connection RRC message forwarded by a base station separation entity is received, wherein the uplink RRC message includes the type of user equipment sending the uplink RRC message; and the user equipment is determined to be a reduced-capability user equipment according to the uplink RRC message.

[0012] Optionally, the uplink RRC message is obtained from an RRC message sent by the terminal, and the RRC message includes: an RRC establishment request message or an RRC update request message.

[0013] Optionally, different types of reduced-capacity devices include: RedCap UE with single RX, RedCap UE with dual RX, eRedCap UE with single RX, eRedCap UE with dual RX, half-duplex RedCap UE and half-duplex eRedCap UE.

[0014] According to another aspect of an embodiment of the present disclosure, a data transmission method is provided, including: a base station separation entity sends service cell RedCap UE configuration related information to a base station centralized entity through an interface message within the base station, wherein the service cell RedCap UE configuration related information includes: a cell prohibition mark of a single Rx RedCap UE, a cell prohibition mark of a dual Rx RedCap UE, a cell prohibition mark of a single Rx eRedCap UE, a cell prohibition mark of a dual Rx eRedCap UE and a cell prohibition mark of a half-duplex RedCap UE. The base station centralized entity and the base station separation entity both belong to the first base station.

[0015] Optionally, the data transmission method also includes: receiving access and reselection configuration information corresponding to different types of reduced capability devices sent by the base station centralized entity, wherein the access and reselection configuration information includes: at least one of the access frequencies corresponding to different types of reduced capability devices and same-frequency reselection identifiers of different types of reduced capability devices.

[0016] Optionally, the data transmission method further includes: obtaining configuration information of each type of reduced capability device among multiple types of reduced capability devices; generating a broadcast message based on the configuration information, wherein the broadcast message is used to indicate the support status of each service cell in the first base station for each type of reduced capability user equipment.

[0017] Optionally, the same-frequency reselection identifiers of different types of reduced-capability devices include: the same-frequency reselection identifier of eRedCap and the same-frequency reselection identifier of RedCap; the same-frequency reselection identifier of eRedCap exists in the broadcast message, determining that the service cell in the first base station supports eRedCap UE; the same-frequency reselection identifier of eRedCap does not exist in the broadcast message, determining that the service cell in the first base station does not support eRedCap UE; the same-frequency reselection identifier of RedCap exists in the broadcast message, determining that the service cell in the first base station supports RedCap UE; the same-frequency reselection identifier of RedCap does not exist in the broadcast message, determining that the service cell in the first base station does not support RedCap UE.

[0018] Optionally, the configuration information includes: information configured by the network management device for each type of reduced-capability user equipment.

[0019] Optionally, the broadcast message includes a first type of broadcast message and a second type of broadcast message, the first type of broadcast message is information in the main system information block MIB, the first type of broadcast message includes: a first type of cell prohibition flag and a same-frequency reselection flag for non-reduced capability type user equipment, and the second type of broadcast message is information in the system information block SIB, wherein the second type of broadcast message includes at least one of the following: a second type of cell prohibition flag and a same-frequency reselection flag for reduced capability type user equipment.

[0020] Optionally, the data transmission method also includes: broadcasting the broadcast message to each type of reduced-capability user equipment, wherein the reduced-capability user equipment determines the prohibited cells that the reduced-capability user equipment is prohibited from accessing based on the broadcast message; and encapsulating the second type of broadcast information in the separated entity system information, and sending it to the base station centralized entity via the base station interface message.

[0021] Optionally, the data transmission method further includes: sending the serving cell RedCap UE configuration information to a second base station, wherein the second base station is any base station different from the first base station, and the serving cell RedCap UE configuration information is used to determine the serving cell allowed to be accessed by the reduced capability user equipment in the second base station.

[0022] Optionally, the second type of cell prohibition identification includes: cell prohibition identification of RedCap UE with single RX, cell prohibition identification of RedCap UE with dual RX, cell prohibition identification of eRedCap UE with single RX, cell prohibition identification of eRedCap UE with dual RX, cell prohibition identification of half-duplex RedCap UE and cell prohibition identification of half-duplex eRedCap UE.

[0023] Optionally, the cell prohibition identifier of the single RX RedCap UE, the cell prohibition identifier of the dual RX RedCap UE, the cell prohibition identifier of the single RX eRedCap UE, the cell prohibition identifier of the dual RX eRedCap UE, the cell prohibition identifier of the half-duplex RedCap UE and the cell prohibition identifier of the half-duplex eRedCap UE all include a prohibition field and a non-prohibition field; the value of the prohibition field in the cell prohibition identifier of the single RX RedCap UE is prohibition, determining that the service cell indicated by the cell prohibition identifier of the single RX RedCap UE does not allow the single RX RedCap UE to access; the value of the prohibition field in the cell prohibition identifier of the dual RX RedCap UE is prohibition, determining that the service cell indicated by the cell prohibition identifier of the dual RX RedCap UE does not allow the dual RX RedCap UE to access; the value of the prohibition field in the cell prohibition identifier of the single RX eRedCap UE is prohibition, determining that the service cell indicated by the cell prohibition identifier of the single RX eRedCap UE does not allow the single RX reduced capability user equipment eRedCap UE to access; the dual RX eRedCap The value of the prohibited field in the cell prohibition identifier of the UE is prohibited, which determines that the service cell indicated by the cell prohibition identifier of the dual-RX eRedCap UE does not allow the dual-RX eRedCap UE to access; the value of the prohibited field in the cell prohibition identifier of the half-duplex RedCap UE is prohibited, which determines that the service cell indicated by the cell prohibition identifier of the half-duplex RedCap UE does not allow the half-duplex RedCap UE to access; the value of the prohibited field in the cell prohibition identifier of the half-duplex eRedCap UE is prohibited, which determines that the service cell indicated by the cell prohibition identifier of the half-duplex eRedCap UE does not allow the half-duplex eRedCap UE to access.

[0024] Optionally, the data transmission method also includes: the prohibition field in the cell prohibition identifier of the single RX RedCap UE does not exist, determining that the service cell indicated by the cell prohibition identifier of the single RX RedCap UE does not allow the single RX reduced capability user equipment RedCap UE to access; the prohibition field in the cell prohibition identifier of the dual RX RedCap UE does not exist, determining that the service cell indicated by the cell prohibition identifier of the dual RX RedCap UE does not allow the dual RX RedCap UE to access; the prohibition field in the cell prohibition identifier of the single RX eRedCap UE does not exist, determining that the service cell indicated by the cell prohibition identifier of the single RX eRedCap UE does not allow the single RX reduced capability user equipment eRedCap UE to access; the prohibition field in the cell prohibition identifier of the dual RX eRedCap UE does not exist, determining that the service cell indicated by the cell prohibition identifier of the dual RX eRedCap UE does not allow the dual RX eRedCap UE to access; the prohibition field in the cell prohibition identifier of the half-duplex RedCap UE does not exist, determining that the service cell indicated by the cell prohibition identifier of the half-duplex RedCap UE does not allow the half-duplex RedCap UE to access; half-duplex eRedCap The prohibition field in the cell prohibition flag of the UE does not exist, and it is determined that the serving cell indicated by the cell prohibition flag of the half-duplex eRedCap UE does not allow the half-duplex eRedCap UE to access.

[0025] Optionally, the data transmission method further includes: receiving radio resource connection RRC messages sent by multiple types of reduced capability user equipment, and forwarding the uplink RRC message in the RRC message to the base station centralized entity, wherein the RRC message includes: RRC establishment request message, or RRC update request message.

[0026] According to another aspect of an embodiment of the present disclosure, a method for determining prohibited cells is also provided, including: a user equipment receives a broadcast message sent by a base station separation entity, wherein the broadcast message includes a first type of broadcast message and a second type of broadcast message, the first type of broadcast message is information in the main system information block MIB, the first type of broadcast message includes: a first type of cell prohibition flag and a same-frequency reselection flag for non-reduced capability type user equipment, and the second type of broadcast message is information in the system information block SIB, wherein the second type of broadcast message includes at least one of the following: a second type of cell prohibition flag and a same-frequency reselection flag for reduced capability type user equipment, the same-frequency reselection flag is used to indicate cell reselection for multiple service cells with a frequency as an access frequency; determining the prohibited cells in the first base station according to the broadcast message, wherein the first base station is the base station to which the base station separation entity belongs.

[0027] Optionally, determining prohibited cells in a base station according to a broadcast message includes: if a first-category cell prohibition identifier in a first-category broadcast message indicates prohibition, and the user equipment is a non-reduced-capability user equipment, determining the service cell indicated by the first-category cell prohibition identifier as a prohibited cell; and performing cell reselection on the remaining multiple service cells having the same frequency as the prohibited cell; if the first-category prohibition identifier in the first-category broadcast message indicates prohibition, and the user equipment is a reduced-capability user equipment, determining the prohibited cell according to a second-category broadcast message.

[0028] Optionally, determining the prohibited cell based on the second type of broadcast message includes: detecting whether the second type of broadcast message is received to obtain a detection result; if the detection result indicates that the second type of broadcast message is not received, determining the service cell indicated by the first type of prohibition identifier as a prohibited cell; and prohibiting cell reselection for the remaining multiple service cells with the same frequency as the prohibited cell; if the user equipment is in the target state, the detection result indicates that the second type of broadcast message is received, and the second type of broadcast message does not include a same-frequency reselection identifier, determining the service cell indicated by the first type of prohibition identifier as a prohibited cell, wherein the target state includes: RRC idle state, RRC inactive state and RRC activated state when the T311 timer is running; and performing cell reselection for the remaining multiple service cells with the same frequency as the prohibited cell.

[0029] Optionally, the method for determining a prohibited cell also includes: if the user equipment is any one of a single RX RedCap UE, a dual RX RedCap UE, a single RX eRedCap UE, a dual RX eRedCap UE, a half-duplex RedCap UE or a half-duplex eRedCap UE, and the second type of cell prohibition identifier in the second type of broadcast message of the user equipment indicates prohibition, the service cell indicated by the second type of cell prohibition identifier is determined to be a prohibited cell.

[0030] According to another aspect of an embodiment of the present disclosure, a data transmission device is also provided, including: a receiving module for receiving service cell reduced capability user equipment RedCap UE configuration related information sent by a base station separation entity through an interface message within the base station, wherein the service cell RedCap UE configuration related information includes: a cell prohibition identifier of a single Rx RedCap UE, a cell prohibition identifier of a dual Rx RedCap UE, a cell prohibition identifier of a single Rx reduced capability user equipment eRedCap UE, a cell prohibition identifier of a dual Rx eRedCap UE and a cell prohibition identifier of a half-duplex RedCap UE; a determination module for determining, when the service cell RedCap UE configuration related information exists in a service cell information field, access and reselection configuration information corresponding to different types of reduced capability user equipment is provided in the system information according to the service cell RedCap UE configuration related information, wherein the access and reselection configuration information includes at least one of the following: the access frequency corresponding to the different types of reduced capability user equipment, and the same-frequency reselection identifier of the different types of reduced capability user equipment.

[0031] According to another aspect of an embodiment of the present disclosure, a data transmission device is also provided, including: a sending module for sending service cell RedCap UE configuration-related information to a base station centralized entity through an interface message within the base station, wherein the service cell RedCap UE configuration-related information includes: a cell prohibition mark of a single Rx RedCap UE, a cell prohibition mark of a dual Rx RedCap UE, a cell prohibition mark of a single Rx reduced capability user equipment eRedCap UE, a cell prohibition mark of a dual Rx eRedCap UE and at least one of a cell prohibition mark of a half-duplex RedCap UE.

[0032] According to another aspect of an embodiment of the present disclosure, a prohibited cell determination device is also provided, including: a receiving module for receiving a broadcast message sent by a base station separation entity, wherein the broadcast message includes a first type of broadcast message and a second type of broadcast message, the first type of broadcast message is information in the main system information block MIB, the first type of broadcast message includes: a first type of cell prohibition identifier and an intra-frequency reselection identifier for non-reduced capability user equipment, and the second type of broadcast message is information in the system information block SIB, wherein the second type of broadcast message includes at least one of the following: a second type of cell prohibition identifier and the intra-frequency reselection identifier for reduced capability user equipment, the intra-frequency reselection identifier is used to indicate cell reselection for multiple service cells with a frequency as an access frequency; a determination module for determining a prohibited cell in a first base station based on the broadcast message, wherein the first base station is the base station to which the base station separation entity belongs.

[0033] According to another aspect of an embodiment of the present disclosure, a base station is also provided, including: the base station separation entity, used to obtain the service cell RedCap UE configuration information and the RRC message sent by the RedCap UE, and send the service cell RedCap UE configuration information and the RRC message to the base station centralized entity, wherein the service cell RedCap UE configuration information includes: at least one of the cell prohibition identifiers corresponding to multiple types of reduced capability user equipment, the cell prohibition identifier is used to indicate the service cell that the user equipment to which the cell prohibition identifier belongs is prohibited from accessing; and is also used to determine the support status of the base station to which the base station separation entity belongs for the target terminal based on the received access and reselection configuration information, wherein the support status includes: supporting access or prohibiting access; the base station centralized entity is used to receive the RRC message and the service cell RedCap UE configuration information, determine the target terminal based on the RRC message, and determine the target terminal based on the service cell RedCap The UE configuration information generates access and reselection configuration information of the target terminal, and sends the access and reselection configuration information to the base station separation entity, wherein the target terminal is a reduced-capability user equipment that sends the RRC message, and the access and reselection configuration information includes at least one of the following: access frequencies corresponding to different types of reduced-capability user equipment, and same-frequency reselection identifiers of the different types of reduced-capability user equipment.

[0034] According to another aspect of an embodiment of the present disclosure, a base station centralized entity is provided, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute the method as described in any of the above embodiments based on instructions stored in the memory.

[0035] According to another aspect of an embodiment of the present disclosure, a base station separation entity is provided, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute the method described in any of the above embodiments based on instructions stored in the memory.

[0036] According to another aspect of an embodiment of the present disclosure, a user equipment is provided, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute the method as described in any of the above embodiments based on instructions stored in the memory.

[0037] According to another aspect of an embodiment of the present disclosure, a base station is provided, comprising: a base station centralized entity as described in any of the above embodiments; and a base station separation entity as described in any of the above embodiments.

[0038] According to another aspect of an embodiment of the present disclosure, a communication system is provided, including: a base station as described in any of the above embodiments; and a user equipment as described in any of the above embodiments.

[0039] According to another aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method described in any of the above embodiments is implemented.

[0040] According to another aspect of an embodiment of the present disclosure, a computer program is provided, comprising computer instructions, wherein when the computer instructions are executed by a processor, the method as described in any one of the above embodiments is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The drawings described herein are used to provide a further understanding of the present disclosure and constitute a part of the present disclosure. The exemplary embodiments of the present disclosure and their descriptions are used to explain the present disclosure and do not constitute an improper limitation of the present disclosure. In the drawings:

[0042] FIG1 is a flowchart of a data transmission method according to an embodiment of the present disclosure;

[0043] FIG2 is a flowchart of another data transmission method according to an embodiment of the present disclosure;

[0044] FIG3 is a flowchart of a method for determining a prohibited cell according to an embodiment of the present disclosure;

[0045] FIG4 is a structural diagram of a data transmission device according to an embodiment of the present disclosure;

[0046] FIG5 is a structural diagram of another data transmission device provided according to an embodiment of the present disclosure;

[0047] FIG6 is a structural diagram of a device for determining a prohibited cell according to an embodiment of the present disclosure;

[0048] FIG7 is a schematic structural diagram of a base station with a separation architecture according to an embodiment of the present disclosure;

[0049] FIG8 is a schematic structural diagram of a base station centralized entity provided according to an embodiment of the present disclosure;

[0050] FIG9 is a schematic structural diagram of a base station separation entity provided according to an embodiment of the present disclosure;

[0051] FIG10 is a schematic structural diagram of a user equipment provided according to an embodiment of the present disclosure;

[0052] FIG11 is a schematic structural diagram of a base station provided according to an embodiment of the present disclosure;

[0053] FIG12 is a schematic structural diagram of a communication system provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0054] In order to enable those skilled in the art to better understand the solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present disclosure.

[0055] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0056] In the related art, there is a cell barring flag in the Master Information Block (MIB) to indicate whether access is allowed to the cell. If it is in the access denied state, the intra frequency reselection flag (IFRI) in the MIB will further indicate whether reselection of the same-frequency neighboring cell is allowed. In the new radio access technology (NR) stage, the cell barring indication (cellBarredbit) in the MIB message is applied to normal UE, RedCap UE and eRedCap UE. For RedCap, in order to limit the stay of RedCap UE on the cell, the operator can specifically prohibit the access of RedCap UE in the case of network congestion without affecting the cell stay of eMBB or non-RedCap UE; in the R17 stage, a cell barring indication unique to RedCap is further set. In NR, System Information Block 1 (SIB1) contains relevant information on whether the UE is allowed to access the cell and the RedCap-specific cell barred indication (cell Barred Indication), and defines the scheduling of other system information; SIB1 also contains radio resource configuration information common to all UEs and barring information used for unified access control. RedCap UE needs to read the cell barring identifier in the MIB as the first step, and then use the RedCap-specific cell barring identifier in SIB1 to decide whether to stay in the cell. The RedCap-specific IFRI means whether the RedCap UE can reselect the same frequency cell when it is barred from access.

[0057] RedCap UEs are divided into two types: 1 Transmission 1 Reception (1T1R) and 1T2R. RedCap UEs with only one receiver (RX) and those with two RXs have different data rates. RedCap UEs with only one receiver (RX) have lower data rates, which affects network throughput. When network capacity is limited, the network may prefer to prohibit RedCap UEs with only one receiver (RX), which affect network throughput. Therefore, separate cell barring indications are required for RedCap UEs with 1 RX and RedCap UEs with 2 RXs. In the R17 version, the corresponding cell barring indications are as follows: the cell barring indication for 1 RX is set to "barred" or "not barred." When multiple Public Land Mobile Networks (PLMNs) or Network Slices (NPNs) are indicated in the SIB1 message, this field is common to all PLMNs and NPNs, but only applies to RedCap UEs. The cell barring indication of 2RX is set to "barred" or "not barred"; this field is common to all PLMNs and NPNs when multiple PLMNs or NPNs are indicated in the SIB1 message. This field is only applicable to RedCap UEs. The cellBarredindication1RX value of "barred" indicates that for RedCap UEs with one Rx branch, the cell is barred, as defined in protocol TS38.304. Non-RedCap UEs ignore this field. The cellBarredindication 2RX value of "barred" indicates that for RedCap UEs with one Rx branch, the cell is barred, as defined in protocol TS38.304. Non-RedCap UEs ignore this field.

[0058] The inventors noticed that the current 17th version of the Third Generation Partnership Project (3GPP Rel-17) protocol does not subdivide different versions of RedCap UE (User Equipment). Some cells that do not support the R17 version of RedCap may support the R18 version of enhanced RedCap (eRedCap). If the R17 version of the cell prohibition identifier is still used to cover the R18 version of eRedCap, the existing R17 RedCap cell prohibition indication will not be broadcast in the cell that only supports R18 eRedCap, which will cause the eRedCap UE that can originally access the above cell to be unable to access the cell, resulting in a waste of scheduling resources. In addition, since the control unit in the base station separation architecture does not decode the Radio Resource Control (RRC) message from the separation entity, the base station centralized entity cannot determine the support strategy of different cells for various types of reduced-capability devices. In response to the above problems, no effective solution has been proposed yet.

[0059] According to the current protocol, when a base station split architecture is adopted, the base station node component (gNB-Distributed Unit, gNB-DU) generates SIB1 and MIB broadcast messages and the configuration information therein. The base station node controller unit (gNB-Centralized Unit, gNB-CU) does not read any radio resource control information RRC (RRC ASN.1) encoded in the Abstract Syntax Notation One (ASN.1) format. However, the gNB-CU still needs to obtain necessary information such as the cell's prohibition indication for RedCap contained in the SIB message to perform further configuration operations. Therefore, when the base station adopts a gNB-CU and gNB-DU separated architecture, the following problems will arise when supporting different versions of RedCap UEs: 1) There is no support for different versions of RedCap 1) For UE segmentation, some cells that do not support R17 RedCap may support R18 eRedCap. If the R17 version of the cell prohibition identifier is still used to cover the R18 version of the eRedCap, the existing R17 RedCap cell prohibition indication will not be broadcast in the cell that only supports R18 eRedCap, which will cause the eRedCap that can originally access the above cell to be unable to access the cell, resulting in a waste of scheduling resources; 2) In the base station separation architecture, the control unit does not decode the RRC message from the separation entity, and the centralized entity cannot determine the support strategy of different cells for various types of reduced-capability devices.

[0060] Accordingly, the embodiments of the present disclosure provide a data transmission method, a prohibited cell determination method, and a base station to at least solve the technical problem that the current 3GPP Rel-17 protocol does not subdivide different versions of reduced-capability devices and cannot meet the needs of scheduling RedCap users and eRedCap users in a wireless base station separation architecture.

[0061] According to an embodiment of the present disclosure, a method embodiment of a data transmission method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0062] The method provided by the embodiment of the present disclosure achieves the purpose of supporting RedCap UE in a base station separation architecture by independently configuring different types of RedCap UE. The RedCap involved in the embodiments of the present disclosure has the following differences compared to normal NR UE: 1) Its spectrum bandwidth is in the Sub-6GHz frequency band, which has a smaller spectrum bandwidth than normal NR UE. For example, the maximum bandwidth of RedCap is 20MHz (megahertz), while the maximum bandwidth of NR UE is 100MHz; 2) The number of antennas and multiple antennas for sending and receiving signals (Multiple-Input Multiple-Output, MIMO) is reduced. The receiving link of RedCap UE can be reduced to 1 or 2, and the corresponding downlink MIMO is reduced to 1 or 2 layers of reception. The number of antennas is also reduced from 2T4R antennas of NR UE to 1T1R or 1T2R; 3) A simpler orthogonal amplitude-phase modulation method (64Quadrature Amplitude Modulation, 64QAM) is adopted, which reduces the requirements for radio frequency and baseband; 4) Full duplex frequency division duplex (FD-FDD) and time division duplex (TD-FDD) are supported. 5) Enhanced discontinuous reception features include: a longer sleep mode, which reduces power consumption and improves battery life; 6) Reduced buffering requirements: the length of the packet data convergence protocol sequence number (PDCP SN) and the radio link control layer acknowledgment mode sequence number (RLC-AM SN) is reduced from 18 bits to 12 bits; 7) The theoretical peak rate is reduced to 80-90 megabits per second (Mbps); 8) Due to the limitations of antenna design and the size of the wearable terminal, coverage is reduced; 9) Half-duplex FDD (HD-FDD) cannot transmit and receive simultaneously, so the transmission delay is increased; 10) RedCap UE does not support dual connection (NE-DC) between 4G radio access network and 5G NR, nor does it support 5G Dual connectivity between NR and 4G radio access network.

[0063] FIG1 is a flowchart of a data transmission method according to an embodiment of the present disclosure. As shown in FIG1 , the method includes the following steps:

[0064] In step S102, the base station centralized entity receives the service cell reduced capability user equipment RedCap UE configuration related information sent by the base station separation entity through the base station internal interface message, wherein the service cell RedCap UE configuration related information includes: the cell prohibition mark of the RedCap UE with a single receiver Rx, the cell prohibition mark of the RedCap UE with dual Rx, the cell prohibition mark of the enhanced reduced capability user equipment eRedCap UE with single Rx, the cell prohibition mark of the eRedCap UE with dual Rx and at least one of the cell prohibition mark of the half-duplex RedCap UE, and the base station centralized entity and the base station separation entity both belong to the first base station.

[0065] Optionally, the serving cell RedCap UE configuration related information further includes: a RedCap broadcast message field, wherein the RedCap broadcast message field is used to indicate user equipment that is allowed to access the first base station.

[0066] In this embodiment, in addition to the cell prohibition identifiers of different types of RedCap UEs mentioned in the above step S102, the service cell RedCap UE configuration related information also includes a RedCap broadcast message field (RedCap Broadcast Information), which includes one or more of the cell access permission indication of single Rx RedCap UE, cell access permission indication of dual Rx RedCap UE, cell access permission indication of single Rx eRedCap UE, cell access permission indication of dual Rx eRedCap UE and cell access permission indication of half-duplex RedCap UE. Therefore, this field can be used to indicate which types of RedCap UEs are allowed to access. For example, the RedCap broadcast message field can be set to a bit string of size 8, namely BIT STRING(SIZE(8)); and the first position in the bit string is set to indicate the support status of the single Rx RedCap UE of the R17 version, when the first position of the bit string is "1", it is confirmed that the single Rx RedCap UE of the R17 version is allowed to be accessed; the second position in the bit string is set to indicate the support status of the dual Rx RedCap UE of the R17 version, when the second position of the bit string is "1", it is confirmed that the dual Rx RedCap UE of the R17 version is allowed to be accessed; the third position in the bit string is set to indicate the support status of the single Rx eRedCap UE of the R18 version, when the third position of the bit string is "1", it is confirmed that the single Rx eRedCap UE of the R18 version is allowed to be accessed; the fourth position in the bit string is set to indicate the support status of the dual Rx eRedCap UE of the R18 version, when the fourth position of the bit string is "1", it is confirmed that the dual Rx eRedCap UE of the R18 version is allowed to be accessed. UE is allowed to be accessed; the fifth position in the bit string is set to indicate the half-duplex RedCap UE support state, and when the fifth position of the bit string is set to "1", it is confirmed that the half-duplex RedCap UE is allowed to be accessed.

[0067] According to an optional embodiment of the present disclosure, the interface message within the base station includes: an F1 interface establishment request message, an F1 interface establishment response message, and a next generation radio access network NG-RAN node configuration update message.

[0068] In the above-mentioned step S102, the carrier for the base station centralized entity to receive the RedCap UE configuration-related information is the base station interface message, wherein the base station interface message can be an F1 interface establishment request message, an F1 interface establishment response message or a radio access network (NG-RAN) node configuration update message; the above-mentioned F1 interface is a point-to-point interface between two NG-RAN nodes. The F1 interface supports the exchange of signaling messages between NG-RAN nodes and can forward protocol data packets to the corresponding tunnel endpoints.

[0069] The method provided by the embodiment of the present disclosure independently configures different types of reduced-capability user equipment. In step S102, the base station centralized entity in any base station (i.e., the first base station) receives RedCap UE configuration-related information sent by the base station separation entity from the same (first) base station through the base station interface message, wherein the service cell RedCap UE configuration-related information includes: a cell prohibition mark of a single Rx RedCap UE, a cell prohibition mark of a dual Rx RedCap UE, a cell prohibition mark of a single Rx eRedCap UE, a cell prohibition mark of a dual Rx eRedCap UE, and a cell prohibition mark of a half-duplex RedCap UE. One or more of the following.

[0070] Step S104: When the serving cell RedCap UE configuration related information exists in the serving cell information field, the base station centralized entity may determine to provide access and reselection configuration information corresponding to different types of reduced capability user equipment in the system information according to the serving cell RedCap UE configuration related information.

[0071] In step S104, when the base station centralized entity of the (first) base station receives the base station interface message, the base station centralized entity detects whether there is service cell RedCap UE configuration related information in the service cell information field. Only when there is service cell RedCap UE configuration related information in the service cell information field, can the base station centralized entity use the service cell RedCap UE configuration related information to provide access and reselection configuration information corresponding to different types of RedCap UE in the system information.

[0072] Optionally, the access and reselection configuration information includes at least one of the following: access frequencies corresponding to different types of reduced capability user equipment, and intra-frequency reselection identifiers of different types of reduced capability user equipment. In an optional embodiment of the present disclosure, when the base station centralized entity provides access and reselection configuration information for different types of reduced capability user equipment in system information, the access and reselection configuration information corresponding to each type of reduced capability user equipment includes: at least one of an access frequency and an intra-frequency reselection identifier, wherein the access frequency indicates the frequency that the reduced capability user equipment corresponding to the access and reselection configuration information is allowed to access; and the intra-frequency reselection identifier (IFRI) indicates whether intra-frequency cell reselection can be performed when the reduced capability user equipment of this type is prohibited from accessing.

[0073] Optionally, the same-frequency reselection identifiers of different types of reduced-capability user equipment include: a reselection identifier of a RedCap UE and a reselection identifier of an eRedCap UE.

[0074] The intra-frequency reselection identifiers of different types of reduced-capability user equipment mentioned in the above embodiments include two types: the intra-frequency reselection identifier of the RedCap UE of the R17 version and the intra-frequency reselection identifier of the eRedCap of the R18 version.

[0075] According to some optional embodiments of the present disclosure, an uplink radio resource connection RRC message forwarded by a base station separation entity is received, wherein the uplink RRC message includes the type of user equipment sending the uplink RRC message; and the user equipment is determined to be a reduced-capability user equipment based on the uplink RRC message.

[0076] In some optional embodiments, the base station centralized entity may also receive an uplink RRC message forwarded by the base station separation entity, and the base station centralized entity may determine whether the type of the terminal (user equipment) sending the uplink RRC message is a user equipment of a reduced capability type based on the received uplink RRC message.

[0077] Optionally, the uplink RRC message is obtained from an RRC message sent by the terminal, and the RRC message includes: an RRC establishment request message or an RRC update request message.

[0078] In the above embodiment, the uplink RRC message received by the base station centralized entity is generated according to the RRC message sent by the terminal, wherein the RRC message sent by the terminal may be an RRC establishment request message requesting to establish a radio resource connection or an RRC message update request message (RRC Resume) requesting to update an RRC message.

[0079] According to an optional embodiment of the present disclosure, different types of reduced-capability user equipment include: single-RX RedCap UE, dual-RX RedCap UE, single-RX eRedCap UE, dual-RX eRedCap UE, half-duplex RedCap UE and half-duplex eRedCap UE.

[0080] The method provided by the embodiments of the present disclosure supports different types of reduced-capability user equipment, for example, a single-RX RedCap UE that includes only one receiver and complies with the R17 version of the 3GPP protocol, a dual-RX RedCap UE that includes two receivers and complies with the R17 version of the 3GPP protocol, a single-RX eRedCap UE that includes only one receiver and complies with the R18 version of the 3GPP protocol, a dual-RX eRedCap UE that includes two receivers and complies with the R18 version of the 3GPP protocol, a half-duplex RedCap UE in half-duplex mode and complies with the R17 version of the 3GPP protocol, and a half-duplex eRedCap UE in half-duplex mode and complies with the R18 version of the 3GPP protocol.

[0081] Through the above steps, it is possible to achieve forwarding of reduced-capability user equipment configuration-related information from the base station separation entity to the base station centralized entity in the separation architecture, as well as forwarding of configuration information at the RAN level, thereby enabling the base station centralized entity to obtain support strategies for various types of reduced-capability user equipment in different cells, thereby enhancing the interoperability between the base station separation entity and the base station centralized entity in the base station separation architecture, and enhancing the interaction capability between RAN nodes, so that the network can independently control the residency status of various types of UEs in congested scenarios, thereby ensuring the flexibility and timeliness of network optimization strategies.

[0082] FIG2 is a flowchart of another data transmission method provided according to an embodiment of the present disclosure. As shown in FIG2 , the method includes the following steps:

[0083] In step S202, the base station separation entity sends the service cell RedCap UE configuration related information to the base station centralized entity through the base station internal interface message, wherein the service cell RedCap UE configuration related information includes: the cell prohibition mark of the single Rx RedCap UE, the cell prohibition mark of the dual Rx RedCap UE, the cell prohibition mark of the single Rx eRedCap UE, the cell prohibition mark of the dual Rx eRedCap UE and the cell prohibition mark of the half-duplex RedCap UE. Both the base station centralized entity and the base station separation entity belong to the first base station.

[0084] In step S202, for the base station separation entity that is in the same (first) base station as the base station centralized entity, the base station separation entity sends the service cell RedCap UE configuration related information including at least one of the cell prohibition identifier of single Rx RedCap UE, the cell prohibition identifier of dual Rx RedCap UE, the cell prohibition identifier of single Rx eRedCap UE, the cell prohibition identifier of dual Rx eRedCap UE and the cell prohibition identifier of half-duplex RedCap UE to the base station centralized entity through an intra-base station interface message; wherein the intra-base station interface message can be an F1 establishment request message requesting to establish an open interface (F1) or a base station separation entity configuration update message.

[0085] According to an optional embodiment of the present disclosure, the data transmission method also includes: receiving access and reselection configuration information corresponding to different types of reduced-capability user equipment sent by a base station centralized entity, wherein the access and reselection configuration information includes: at least one of the access frequencies corresponding to different types of reduced-capability user equipment and the same-frequency reselection identifiers of different types of reduced-capability user equipment.

[0086] In this embodiment, when the interface message within the base station is an F1 setup request message (F1Setup Request), after the base station separation entity sends the service cell RedCap UE configuration related information to the base station centralized entity based on the F1Setup Request, it will receive access and reselection configuration information for different types of RedCap UEs returned by the base station centralized entity, wherein the access and reselection configuration information includes the frequency at which each type of reduced-capability user equipment is allowed to access, and one or more of the same-frequency reselection identifiers (IFRIs) of each type of RedCap UE. The above-mentioned same-frequency reselection identifier (IFRI) indicates whether same-frequency cell reselection can be performed when this type of reduced-capability user equipment is prohibited from access.

[0087] According to an optional embodiment of the present disclosure, the same-frequency reselection identifiers of different types of reduced-capability user equipment include: the same-frequency reselection identifier of eRedCap and the same-frequency reselection identifier of RedCap; the same-frequency reselection identifier of eRedCap exists in the broadcast message, determining that the service cell in the first base station supports eRedCap UE; the same-frequency reselection identifier of eRedCap does not exist in the broadcast message, determining that the service cell in the first base station does not support eRedCap UE; the same-frequency reselection identifier of RedCap exists in the broadcast message, determining that the service cell in the first base station supports RedCap UE; the same-frequency reselection identifier of RedCap does not exist in the broadcast message, determining that the service cell in the first base station does not support RedCap UE.

[0088] The same-frequency reselection identifiers of different types of reduced-capability user equipment mentioned in the above embodiments include: the same-frequency reselection identifier of the RedCap UE of the R17 version and the same-frequency reselection identifier of the eRedCap of the R18 version. Whether the cell within the coverage of the (first) base station supports RedCap UE or eRedCap is determined by detecting whether the same-frequency reselection identifier of the RedCap UE or the same-frequency reselection identifier of the eRedCap is present in the broadcast message. For example, if the broadcast message generated by the base station separation entity of the first base station contains the same-frequency reselection identifier of the RedCap and eRedCap, it is determined that the cell within the coverage of the first base station supports access of RedCap UE and eRedCap UE. Otherwise, if the broadcast message generated by the base station separation entity of the first base station does not contain the same-frequency reselection identifier of the RedCap, and only the same-frequency reselection identifier of the RedCap exists, it is determined that the cell within the coverage of the first base station supports access of eRedCap UE, but does not support access of RedCap UE.

[0089] According to another optional embodiment of the present disclosure, the data transmission method also includes: obtaining configuration information of each type of reduced capability user equipment among multiple types of reduced capability user equipment; generating a broadcast message based on the configuration information, wherein the broadcast message is used to indicate the support status of each service cell in the first base station for each type of reduced capability user equipment.

[0090] In an embodiment of the present disclosure, the base station separation entity obtains configuration information of each type of reduced capability user equipment to determine, based on the configuration information, whether the support status of each cell for each type of reduced capability user equipment is support access or non-support access; and generates a broadcast message corresponding to the support status.

[0091] Optionally, the configuration information includes: information configured by the network management device for each type of reduced-capability user equipment.

[0092] The configuration information of the reduced capability user equipment in the previous embodiment can be the network management configuration of various types of reduced capability user equipment, wherein the network management configuration of the reduced capability user equipment can be in the following form: the RedCap broadcast message field is a bit string of size 8, namely BIT STRING (SIZE (8)); and each position of the bit string is defined to indicate which type of RedCap UE access is allowed by the service cell; for example, the first position "1" is defined to indicate support for R17 version single Rx RedCap UE access, the second position "1" is defined to indicate support for R17 version dual Rx RedCap UE access, the third position "1" is defined to indicate support for R18 version single Rx eRedCap UE access, the fourth position "1" is defined to indicate support for R18 version dual Rx eRedCap UE access, and the fifth position "1" is defined to indicate support for half-duplex RedCap UE access.

[0093] According to an optional embodiment of the present disclosure, the broadcast message includes a first type of broadcast message and a second type of broadcast message, the first type of broadcast message is information in the main system information block MIB, the first type of broadcast message includes: a first type of cell prohibition flag and a same-frequency reselection flag for non-reduced capability type user equipment, and the second type of broadcast message is information in the system information block SIB, wherein the second type of broadcast message includes at least one of the following: a second type of cell prohibition flag and a same-frequency reselection flag for reduced capability type user equipment.

[0094] In this embodiment, the broadcast message corresponding to the support state generated by the base station separation entity includes: MIB information (i.e., first-type broadcast information) and SIB information (i.e., second-type broadcast information). The MIB information (i.e., first-type broadcast information) includes the cell barring flag (i.e., first-type cell barring flag) and intra-frequency reselection flag for general-type terminals (i.e., non-RedCap user equipment), which is universal information. The SIB information includes: a RedCap-specific cell barring flag (i.e., second-type cell barring flag) used to determine whether a RedCap UE can reside in the serving cell of the (first) base station; the SIB information may also include a RedCap-specific intra-frequency reselection flag (IFRI) used to indicate whether a RedCap UE can reselect an intra-frequency cell when barred from access. It should be noted that the SIB may include both the RedCap-specific cell barring flag and the RedCap-specific intra-frequency reselection flag (IFRI), or may include only one of the two. The SIB also contains radio resource configuration information common to all UEs. The information in the above SIB is typically stored in System Information Block 1 (SIB1).

[0095] Optionally, the second type of cell prohibition identification includes: cell prohibition identification of RedCap UE with single RX, cell prohibition identification of RedCap UE with dual RX, cell prohibition identification of eRedCap UE with single RX, cell prohibition identification of eRedCap UE with dual RX, cell prohibition identification of half-duplex RedCap UE and cell prohibition identification of half-duplex eRedCap UE.

[0096] In this embodiment, the RedCap-specific cell barring flag (i.e., the second type of cell barring flag) is generally stored in the system information block 1 (SIB1). For example, the gNB-DU generates the SIB1 and MIB messages according to the network management configuration code. The SIB1 message includes the following types of cell barring flags: the cell barring flag of the single-Rx RedCap UE of the R17 version (cellBarred-RedCap1Rx-r17), the cell barring flag of the dual-Rx RedCap UE of the R17 version (cellBarred-RedCap2Rx-r17), the cell barring flag of the single-Rx eRedCap UE of the R18 version (cellBarred-eRedCap1Rx-r18), the cell barring flag of the dual-Rx eRedCap UE of the R18 version (cellBarred-eRedCap2Rx-r18), the cell allow flag of the half-duplex RedCap UE (halfDuplexRedCap-Allowed), and the cell barring flag of the half-duplex RedCap UE (halfDuplexRedCap-Allowed). It should be noted that SIB1 may include multiple of the above five types of cell prohibition identifiers or only one of them.

[0097] According to an optional embodiment of the present disclosure, the cell barring flag of RedCap UE with single RX, the cell barring flag of RedCap UE with dual RX, the cell barring flag of eRedCap UE with single RX, the cell barring flag of eRedCap UE with dual RX, the cell barring flag of half-duplex RedCap UE and the cell barring flag of half-duplex eRedCap UE are enumeration types.

[0098] In this embodiment, the cell barring flag of the single Rx RedCap UE (cellBarred- RedCap1Rx-r17), the cell barring flag of the dual Rx RedCap UE (cellBarred-RedCap2Rx-r17), the cell barring flag of the single Rx eRedCap UE (cellBarred-eRedCap1Rx-r18), the cell barring flag of the dual Rx eRedCap UE (cellBarred-eRedCap2Rx-r18), and the cell barring flag of the half-duplex RedCap UE (halfDuplexRedCap-Allowed) are enumerated type fields.

[0099] According to some optional embodiments of the present disclosure, the cell prohibition identifier of a single RX RedCap UE, the cell prohibition identifier of a dual RX RedCap UE, the cell prohibition identifier of a single RX eRedCap UE, the cell prohibition identifier of a dual RX eRedCap UE, the cell prohibition identifier of a half-duplex RedCap UE and the cell prohibition identifier of a half-duplex eRedCap UE all include a prohibition field and a non-prohibition field; the value of the prohibition field in the cell prohibition identifier of a single RX RedCap UE is prohibition, determining that the service cell indicated by the cell prohibition identifier of the single RX RedCap UE does not allow the single RX RedCap UE to access; the value of the prohibition field in the cell prohibition identifier of a dual RX RedCap UE is prohibition, determining that the service cell indicated by the cell prohibition identifier of the dual RX RedCap UE does not allow the dual RX RedCap UE to access; the value of the prohibition field in the cell prohibition identifier of a single RX eRedCap UE is prohibition, determining that the service cell indicated by the cell prohibition identifier of the single RX eRedCap UE does not allow the single RX reduced capability user equipment eRedCap UE to access; the dual RX eRedCap The value of the prohibited field in the cell prohibition identifier of the UE is prohibited, which determines that the service cell indicated by the cell prohibition identifier of the dual-RX eRedCap UE does not allow the dual-RX eRedCap UE to access; the value of the prohibited field in the cell prohibition identifier of the half-duplex RedCap UE is prohibited, which determines that the service cell indicated by the cell prohibition identifier of the half-duplex RedCap UE does not allow the half-duplex RedCap UE to access; the value of the prohibited field in the cell prohibition identifier of the half-duplex eRedCap UE is prohibited, which determines that the service cell indicated by the cell prohibition identifier of the half-duplex eRedCap UE does not allow the half-duplex eRedCap UE to access.

[0100] In some embodiments, when these five types of cell barring identifiers are enumerated type fields, the cell barring identifier of single Rx RedCap UE (cellBarred-RedCap1Rx-r17), the cell barring identifier of dual Rx RedCap UE (cellBarred-RedCap2Rx-r17), the cell barring identifier of single Rx eRedCap UE (cellBarred-eRedCap1Rx-r18), and the cell barring identifier of dual Rx eRedCap UE (cellBarred-eRedCap2Rx-r18) all enumerate the "barred" field and the "not-barred" field; and for the cell barring identifier of half-duplex RedCap UE (halfDuplexRedCap-Allowed), the "True" field (equivalent to non-barred) is enumerated and the "True" field (equivalent to prohibited) is not enumerated.

[0101] For the cell barring flag of a single-Rx RedCap UE (cellBarred-RedCap1Rx-r17), when its field value is "prohibited", it means that the cell prohibits RedCap UEs with a single Rx antenna from accessing. This field is only applicable to RedCap UEs with a single RX in R17 version. Non-RedCap UEs and eRedCap UEs in R18 version will ignore this field. For the cell barring flag of a dual-Rx RedCap UE (cellBarred-RedCap2Rx-r17), when its field value is "prohibited", it means that the cell prohibits RedCap UEs with a single Rx antenna from accessing. This field is only applicable to RedCap UEs with a dual RX in R17 version. Non-RedCap UEs and eRedCap UEs in R18 version will ignore this field. For the cell barring flag of a single-Rx eRedCap UE (cellBarred-eRedCap1Rx-r18), when its field value is "prohibited", it means that the cell prohibits eRedCap UEs with a single Rx antenna from accessing. This field is only applicable to RedCap UEs with a single Rx in R18 version. Non-RedCap UEs and RedCap UEs in R17 version will ignore this field. For the cell barring flag of a dual-Rx eRedCap UE (cellBarred-eRedCap2Rx-r18), when its field value is "prohibited", it means that the cell prohibits eRedCap UEs with dual Rx antennas from accessing. This field is only applicable to RedCap UEs with dual Rx in R18 version. Non-RedCap UEs and RedCap UEs in R17 version will ignore this field. For the cell prohibition flag (halfDuplexRedCap-Allowed) of the half-duplex RedCap UE, when its field value is "prohibited", it means that the cell prohibits the access of the half-duplex RedCap UE. This field is only applicable to the half-duplex RedCap UE. The R18 version dual RX RedCap UE and the R17 version RedCap UE will ignore this field. That is, for the R17 version RedCap UE and the R18 version eRedCap UE, the cell's support status for them is identified only by judging the "prohibited" field and the "non-prohibited" field. For the half-duplex RedCap UE, the cell's support status for them can be identified by judging the "prohibited" field and the "non-prohibited" field, and the cell's support status for them can also be determined by identifying the "allowed" field.

[0102] Optionally, the data transmission method also includes: the prohibition field in the cell prohibition identifier of the single RX RedCap UE does not exist, determining that the service cell indicated by the cell prohibition identifier of the single RX RedCap UE does not allow the single RX reduced capability user equipment RedCap UE to access; the prohibition field in the cell prohibition identifier of the dual RX RedCap UE does not exist, determining that the service cell indicated by the cell prohibition identifier of the dual RX RedCap UE does not allow the dual RX RedCap UE to access; the prohibition field in the cell prohibition identifier of the single RX eRedCap UE does not exist, determining that the service cell indicated by the cell prohibition identifier of the single RX eRedCap UE does not allow the single RX reduced capability user equipment eRedCap UE to access; the prohibition field in the cell prohibition identifier of the dual RX eRedCap UE does not exist, determining that the service cell indicated by the cell prohibition identifier of the dual RX eRedCap UE does not allow the dual RX eRedCap UE to access; the prohibition field in the cell prohibition identifier of the half-duplex RedCap UE does not exist, determining that the service cell indicated by the cell prohibition identifier of the half-duplex RedCap UE does not allow the half-duplex RedCap UE to access; half-duplex eRedCap The prohibition field in the cell prohibition flag of the UE does not exist, and it is determined that the serving cell indicated by the cell prohibition flag of the half-duplex eRedCap UE does not allow the half-duplex eRedCap UE to access.

[0103] In the embodiment of the present disclosure, for the cell barring identifier (cellBarred-RedCap1Rx-r17) of the RedCap UE with a single Rx, when its "barred" field does not exist, it means that the cell prohibits the RedCap UE with a single Rx antenna from accessing. This field is only applicable to the RedCap UE with a single RX of the R17 version. Non-RedCap UEs and eRedCap UEs of the R18 version will ignore this field. For the cell barring identifier (cellBarred-RedCap2Rx-r17) of the RedCap UE with a dual Rx, when its "barred" field does not exist, it means that the cell prohibits the RedCap UE with a single Rx antenna from accessing. This field is only applicable to the RedCap UE with a dual RX of the R17 version. Non-RedCap UEs and eRedCap UEs of the R18 version will ignore this field. For the cell barring flag of a single-Rx eRedCap UE (cellBarred-eRedCap1Rx-r18), if the "barred" field does not exist, it means that the cell prohibits access by eRedCap UEs with a single Rx antenna. This field only applies to RedCap UEs with a single Rx antenna in R18 version. Non-RedCap UEs and RedCap UEs in R17 version will ignore this field. For the cell barring flag of a dual-Rx eRedCap UE (cellBarred-eRedCap2Rx-r18), if the "barred" field does not exist, it means that the cell prohibits access by eRedCap UEs with dual Rx antennas. This field only applies to RedCap UEs with dual Rx antennas in R18 version. Non-RedCap UEs and RedCap UEs in R17 version will ignore this field. For the cell prohibition flag (halfDuplexRedCap-Allowed) of half-duplex RedCap UE, when it is the "Prohibited" field or the "True" field does not exist, it means that the cell prohibits half-duplex RedCap UE from accessing. This field is only applicable to half-duplex RedCap UE. The R18 version dual RX RedCap UE and the R17 version RedCap UE will ignore this field.

[0104] According to an optional embodiment of the present disclosure, the data transmission method also includes: broadcasting a broadcast message to each type of reduced-capability user equipment, wherein the reduced-capability user equipment determines a prohibited cell that the reduced-capability user equipment is prohibited from accessing based on the broadcast message; and encapsulating the second type of broadcast information in the separated entity system information, and sending it to the base station centralized entity via an interface message within the base station.

[0105] In this embodiment, after generating broadcast information consisting of MIB information and / or SIB1 information, the base station separation entity sends the broadcast information of each type of reduced-capability user equipment to each type of reduced-capability user equipment, thereby notifying each type of reduced-capability user equipment of which cells it is allowed to access, or notifying each type of reduced-capability user equipment of which cells it is not allowed to access. In addition, the base station separation entity also encapsulates the SIB1 information in the separation entity system information and sends it to the base station centralization entity. For example, the SIB1 message is encapsulated in the separate entity System Information of the gNB-DU, and the gNB-DU service item information (Served Cells Item), RedCap Broadcast Information field (RedCap Broadcast Information) (with a value of 00111000), and gNB-DU System Information (including cellBarred-RedCap1Rx-r17="barred", cellBarred-RedCap2Rx-r17="barred", cellBarred-eRedCap1Rx-r18="notBarred", cellBarred-eRedCap2Rx-r18="notBarred", and halfDuplexRedCap-Allowed="True") are sent to the gNB-CU via the F1Setup Request message.

[0106] According to another optional embodiment of the present disclosure, the data transmission method also includes: sending the service cell RedCap UE configuration information to a second base station, wherein the second base station is any base station different from the first base station, and the service cell RedCap UE configuration information is used to determine the service cell allowed to be accessed for the reduced capability type user equipment in the second base station.

[0107] In this embodiment, the service cell RedCap UE configuration information can be sent to another base station (i.e., the second base station) that is different from the (first) base station where the base station centralized entity is located, so as to determine the cell allowed to be accessed for the RedCap UE in another base station. The above method can use the service cell RedCap UE configuration information to determine the target cell allowed to be accessed for the reduced capability user equipment in the mobility scenario, or to select the optimal service cell allowed to be accessed for the reduced capability user equipment in the scenario where a base station needs to be selected.

[0108] According to some other optional embodiments of the present disclosure, the data transmission method also includes: receiving wireless resource connection RRC messages sent by multiple types of reduced-capability user equipment, and forwarding the uplink RRC messages in the RRC messages to a base station centralized entity, wherein the RRC messages include: RRC establishment request messages, or RRC update request messages.

[0109] In some embodiments, a separate base station entity receives an RRC message from a terminal (i.e., multiple types of RedCap UEs), generates a forwarding message for an initial uplink RRC message, and forwards the message to a centralized base station entity. For example, a gNB-DU receives an RRC connection request message from a UE, generates an initial uplink RRC message, and forwards the message to the gNB-CU of the base station. The gNB-CU receives the F1SetupRequest message and the RRC message from the UE, determines that the UE is a 2Rx RedCap UE of Release 17 based on the field indicating the RedCap UE type (NR RedCap UE Indication IE), provides a list of frequencies allowed for RedCap UEs of Release 18 in the system information based on the RedCap Broadcast Information field, configures RedCap-IFRI-R17 = "True", and sends the message to the gNB-DU.

[0110] FIG3 is a flowchart of a method for determining a prohibited cell according to an embodiment of the present disclosure. As shown in FIG3 , the method includes the following steps:

[0111] In step S302, the user equipment receives a broadcast message sent by the base station separation entity, wherein the broadcast message includes a first type of broadcast message and a second type of broadcast message, the first type of broadcast message is information in the main system information block MIB, the first type of broadcast message includes: a first type of cell prohibition flag and a same-frequency reselection flag for non-reduced capability type user equipment, and the second type of broadcast message is information in the system information block SIB, wherein the second type of broadcast message includes at least one of the following: a second type of cell prohibition flag and a same-frequency reselection flag for reduced capability type user equipment, and the same-frequency reselection flag is used to indicate cell reselection for multiple service cells whose frequency is the access frequency.

[0112] For the terminal interacting with the (first) base station, in step S302, the user equipment (terminal) receives a broadcast message consisting of an MIB message (i.e., a first type of broadcast message) and / or an SIB message (i.e., a second type of broadcast message) sent by the base station classification entity in the (first) base station, wherein the MIB information (i.e., the first type of broadcast information) includes the cell prohibition identifier (i.e., the first type of cell prohibition identifier) ​​and the same-frequency reselection identifier of the general type terminal (i.e., non-RedCap type user equipment), and the SIB information includes the RedCap-specific cell prohibition identifier (i.e., the second type of cell prohibition identifier) ​​and / or the same-frequency reselection identifier.

[0113] Step S304: determining a prohibited cell in the first base station according to the broadcast message, wherein the first base station is a base station to which the base station split entity belongs.

[0114] In step S304, the UE stores the broadcast message obtained in step S202, and determines which serving cells are prohibited from accessing based on the broadcast message.

[0115] According to an optional embodiment of the present disclosure, the prohibited cells in the base station are determined according to the broadcast message, including: if the first type of cell prohibition identifier in the first type of broadcast message indicates prohibition, and the user equipment is a non-reduced capability user equipment, determining the service cell indicated by the first type of cell prohibition identifier as the prohibited cell; and performing cell reselection on the remaining multiple service cells with the same frequency as the prohibited cell; if the first type of prohibition identifier in the first type of broadcast message indicates prohibition, and the user equipment is a reduced capability user equipment, determining the prohibited cell according to the second type of broadcast message.

[0116] In this embodiment, the terminal determines the cell that is prohibited from accessing by the following method: for a terminal of a non-reduced capability type, if the cell prohibition flag read from the MIB information (i.e., the first type of broadcast information) is set to "prohibited" (i.e., cellBarred="barred"), the cell is regarded as a prohibited cell, and the cell reselection process is performed on other cells with the same frequency as the prohibited cell; for a terminal of a reduced capability type, if the cell prohibition flag read from the MIB information (i.e., the first type of broadcast information) is set to "prohibited" (i.e., cellBarred="barred"), the prohibited cell is determined through the SIB information (i.e., the second type of broadcast information).

[0117] According to another optional embodiment of the present disclosure, determining a prohibited cell based on a second type of broadcast message includes: detecting whether a second type of broadcast message is received to obtain a detection result; if the detection result indicates that the second type of broadcast message is not received, determining the service cell indicated by the first type of prohibition identifier as a prohibited cell; and prohibiting cell reselection for the remaining multiple service cells having the same frequency as the prohibited cell; if the user equipment is in a target state, the detection result indicates that a second type of broadcast message is received, and the second type of broadcast message does not include a same-frequency reselection identifier, determining the service cell indicated by the first type of prohibition identifier as a prohibited cell, wherein the target state includes: RRC idle state, RRC inactive state and RRC active state when the T311 timer is running; and performing cell reselection for the remaining multiple service cells having the same frequency as the prohibited cell.

[0118] In this embodiment, a terminal of the reduced capability type determines whether a barred cell has two situations: receiving the SIB information (i.e., the second type of broadcast information) or not receiving the SIB information (i.e., the second type of broadcast information) through SIB information (i.e., the second type of broadcast information); if the terminal does not detect the subcarrier offset (ssb-SubcarrierOffset) of the synchronized broadcast block or does not retrieve the SIB information (i.e., the second type of broadcast information), confirming that the SIB information (i.e., the second type of broadcast information) has not been received, the terminal (UE) regards the cell as a barred cell and performs a cell reselection process for other cells with the same frequency as the barred cell. If the terminal (UE) is in RRC idle state, RRC inactive state, or RRC active state with the T311 timer running, and detects the subcarrier offset (ssb-SubcarrierOffset) of the synchronized broadcast block or retrieves the SIB information (i.e., the second type of broadcast information), confirming that the SIB information (i.e., the second type of broadcast information) has been received, and the received SIB information (i.e., the second type of broadcast information) does not contain an intra-frequency reselection flag, the UE regards the cell as a barred cell.

[0119] Optionally, the data transmission method also includes: if the user equipment is any one of a single RX RedCap UE, a dual RX RedCap UE, a single RX eRedCap UE, a dual RX eRedCap UE, a half-duplex RedCap UE or a half-duplex eRedCap UE, and the second type of cell prohibition identifier in the second type of broadcast message of the user equipment indicates prohibition, the service cell indicated by the second type of cell prohibition identifier is determined to be a prohibited cell.

[0120] In the above embodiment, a RedCap terminal sets its own cell barring flag to "barred" after confirming that the cell is not already barred. For example, a RedCap UE with a single RX sets the cellBarred-RedCap1Rx-r17 field to "barred"; a RedCap UE with a dual RX sets the cellBarred-RedCap2Rx-r17 field to "barred"; a single RX eRedCap UE sets the cellBarred-eRedCap1Rx-r18 field to "barred"; and a dual RX eRedCap UE sets the cellBarred-eRedCap2Rx-r18 field to "barred". A half-duplex UE that is a RedCap UE or a half-duplex eRedCap UE can set its halfDuplexRedCapAllowed field to "not allowed" or not assign a value to halfDuplexRedCapAllowed.

[0121] Figure 4 is a structural diagram of a data transmission device provided according to an embodiment of the present disclosure. As shown in Figure 4, the data transmission device includes: a receiving module 40, a base station centralized entity receives serving cell reduced capability user equipment RedCap UE configuration related information sent by a base station separation entity through a base station internal interface message, wherein the serving cell RedCap UE configuration related information includes: a cell prohibition identifier of a single Rx RedCap UE, a cell prohibition identifier of a dual Rx RedCap UE, a cell prohibition identifier of a single Rx reduced capability user equipment eRedCap UE, a cell prohibition identifier of a dual Rx eRedCap UE, and a cell prohibition identifier of a half-duplex RedCap UE, and the base station centralized entity and the base station separation entity both belong to the first base station; a determining module 42, for when the serving cell RedCap UE configuration related information exists in the serving cell information field, the base station centralized entity can determine to provide access and reselection configuration information corresponding to different types of reduced capability user equipment in the system information according to the serving cell RedCap UE configuration related information, wherein the access and reselection configuration information includes at least one of the following: access frequencies corresponding to different types of reduced capability user equipment, and same-frequency reselection identifiers of different types of reduced capability user equipment.

[0122] It should be noted that the preferred implementation of the embodiment shown in FIG4 can refer to the relevant description of the embodiment shown in FIG1 , which will not be repeated here.

[0123] Figure 5 is a structural diagram of another data transmission device provided according to an embodiment of the present disclosure. As shown in Figure 5, the other data transmission device includes: a sending module 50, the base station separation entity sends the service cell RedCap UE configuration-related information to the base station centralized entity through the base station internal interface message, wherein the service cell RedCap UE configuration-related information includes: the cell prohibition mark of the single Rx RedCap UE, the cell prohibition mark of the dual Rx RedCap UE, the cell prohibition mark of the single Rx reduced capability user equipment eRedCap UE, the cell prohibition mark of the dual Rx eRedCap UE and at least one of the cell prohibition mark of the half-duplex RedCap UE, and the base station centralized entity and the base station separation entity both belong to the first base station.

[0124] It should be noted that the preferred implementation of the embodiment shown in FIG5 can refer to the relevant description of the embodiment shown in FIG2 , which will not be repeated here.

[0125] Figure 6 is a structural diagram of a prohibited cell determination device provided according to an embodiment of the present disclosure. As shown in Figure 6, the device includes: a receiving module 60, a user device receives a broadcast message sent by a base station separation entity, wherein the broadcast message includes a first type of broadcast message and a second type of broadcast message, the first type of broadcast message is information in the main system information block MIB, the first type of broadcast message includes: a first type of cell prohibition flag and a same-frequency reselection flag for non-reduced capability type user equipment, and the second type of broadcast message is information in the system information block SIB, wherein the second type of broadcast message includes at least one of the following: a second type of cell prohibition flag and a same-frequency reselection flag for reduced capability type user equipment, and the same-frequency reselection flag is used to indicate cell reselection for multiple service cells with a frequency as an access frequency; a determination module 62, used to determine the prohibited cell in the first base station according to the broadcast message, wherein the first base station is the base station to which the base station separation entity belongs.

[0126] It should be noted that the preferred implementation of the embodiment shown in FIG6 can refer to the relevant description of the embodiment shown in FIG3 , which will not be repeated here.

[0127] FIG7 is a structural diagram of a base station of a separation architecture provided according to an embodiment of the present disclosure. As shown in FIG7 , the base station of the separation architecture includes: a base station separation entity 70 and a base station centralized entity 72, wherein the base station separation entity 70 is used to obtain the service cell RedCap UE configuration information and the RRC message sent by the RedCap UE, and send the service cell RedCap UE configuration information and the RRC message to the base station centralized entity, wherein the service cell RedCap UE configuration information includes: at least one of the cell prohibition identifiers corresponding to multiple types of reduced capability user equipment, the cell prohibition identifier is used to indicate the service cell to which the user equipment to which the cell prohibition identifier belongs is prohibited from accessing; the base station centralized entity 72 is used to receive the RRC message and the service cell RedCap UE configuration information, determine the target terminal according to the RRC message, and determine the target terminal based on the service cell RedCap UE configuration information. The UE configuration information generates access and reselection configuration information of the target terminal, and sends the access and reselection configuration information to the base station separation entity, wherein the target terminal is a reduced capability type terminal that sends an RRC message, and the access and reselection configuration information includes at least one of the following: the access frequency corresponding to different types of reduced capability user equipment, and the same-frequency reselection identifier of different types of reduced capability user equipment; the base station separation entity 70 is also used to determine the support status of the base station to which the base station separation entity belongs for the target terminal based on the received access and reselection configuration information, wherein the support status includes: supporting access or prohibiting access.

[0128] The base station of the above-mentioned separation architecture includes a base station separation entity 70 and a base station centralized entity 72. When the base station separation entity 70 and the base station centralized entity 72 determine the support status of the service cell in the base station of the separation architecture for the RedCap type terminal to be accessed, the base station separation entity 70 sends the service cell RedCap UE configuration-related information to the first base station centralized entity through the base station interface message, wherein the RedCap UE configuration-related information includes: at least one of the cell prohibition mark of the single Rx RedCap UE, the cell prohibition mark of the dual Rx RedCap UE, the cell prohibition mark of the single Rx eRedCap UE, the cell prohibition mark of the dual Rx eRedCap UE and the cell prohibition mark of the half-duplex RedCap UE; the base station separation entity 70 will also forward the uplink RRC message in the RRC message received from the terminal to the base station centralized entity 72. After the base station centralized entity 72 receives the uplink RRC message and the service cell RedCap UE configuration related information contained in the base station interface message, it determines the type of the terminal sending the message based on the uplink RRC message. If the terminal is confirmed to be of the RedCap type, it generates an access and reselection configuration message for the reduced-capability user equipment based on the received service cell RedCap UE configuration related information; and returns the access and reselection configuration message to the base station separation entity 70. Since the access and reselection configuration message includes a cell prohibition flag for indicating the access frequency of the reduced-capability user equipment and / or an intra-frequency reselection flag indicating whether intra-frequency cell reselection can be performed, the base station separation entity 70 can determine whether the support status of the base station to which it belongs for the terminal to access is allowing access or not allowing access based on the received access and reselection configuration message.

[0129] In some embodiments, the present disclosure provides a base station centralized entity. As shown in FIG8 , the base station centralized entity includes a memory 81 and a processor 82 .

[0130] The memory 81 is used to store instructions. The processor 82 is coupled to the memory 81 . The processor 82 is configured to execute the method involved in any embodiment in FIG. 1 based on the instructions stored in the memory.

[0131] As shown in Figure 8, the base station centralized entity also includes a communication interface 83 for exchanging information with other devices. At the same time, the base station centralized entity also includes a bus 84 through which the processor 82, the communication interface 83, and the memory 81 communicate with each other.

[0132] Memory 81 may include high-speed RAM memory, or may also include non-volatile memory, such as at least one disk storage device. Memory 81 may also be a memory array. Memory 81 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0133] Furthermore, the processor 82 may be a central processing unit (CPU), or may be an application-specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the present disclosure.

[0134] In some embodiments, the present disclosure provides a base station separation entity, as shown in Figure 9. In Figure 9, the base station separation entity includes a memory 91, a processor 92, a communication interface 93, and a bus 94. The difference between Figure 9 and Figure 8 is that, in the embodiment shown in Figure 9, the processor 92 is configured to execute instructions stored in the memory to implement the method involved in any of the embodiments shown in Figure 2.

[0135] In some embodiments, the present disclosure provides a user device, as shown in Figure 10. In Figure 10, the user device includes a memory 1001, a processor 1002, a communication interface 1003, and a bus 1004. The difference between Figure 10 and Figure 9 is that, in the embodiment shown in Figure 10, the processor 1002 is configured to execute instructions stored in the memory to implement the method involved in any of the embodiments shown in Figure 3.

[0136] In some embodiments, the present disclosure provides a base station, as shown in Figure 11. In Figure 11, the base station includes a base station centralized entity 1101 and a base station separation entity 1102, wherein the base station centralized entity 1101 is the base station centralized entity involved in any embodiment in Figure 8, and the base station separation entity 1102 is the base station separation entity involved in any embodiment in Figure 9.

[0137] In some embodiments, the present disclosure provides a communication system, as shown in Figure 12. In Figure 12, the communication system includes a base station 1201 and a user equipment 1202. The base station 1201 is the base station described in any of the embodiments in Figures 7 and 11, and the user equipment 1202 is the user equipment involved in any of the embodiments in Figure 10.

[0138] In some embodiments, the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method involved in any one of the embodiments of Figures 1-3 is implemented.

[0139] In some embodiments, the present disclosure provides a computer program, comprising computer instructions, wherein the computer instructions, when executed by a processor, implement the method involved in any one of the embodiments of FIG. 1-3 .

[0140] By using the above method, key information is sent in the interface message within the base station, thereby enhancing the interoperability between the separated entity and the centralized entity in the separated architecture. This solves the problem that the control unit in the base station separated architecture does not decode the RRC message from the separated entity, and the centralized entity cannot determine the support strategy of different cells for various types of reduced-capability devices. The solution provided by the embodiment of the present disclosure subdivides the indications of different types of reduced-capability user equipment, allowing the centralized entity to independently control which type of RedCap UE is allowed to reside on the cell and whether this type of UE can perform same-frequency cell reselection in a congested scenario, thereby improving the flexibility and timeliness of the network optimization strategy.

[0141] At the same time, the solution provided by the embodiment of the present disclosure completely decouples the R18 and R17 versions of RedCap. The base station can identify the type of reduced-capability user equipment during the access process and connection state, and perform targeted scheduling and optimization, thereby reducing the impact on the performance of traditional UEs or R18 version eRedCap UEs, making it easier for the network to meet the personalized communication needs of thousands of industries. In addition, the method provided by the embodiment of the present disclosure has no special requirements on the terminal side, and therefore has the advantage of facilitating the deployment and implementation of emergency call services in a wireless base station separation architecture.

[0142] It should be noted that the various modules in the above-mentioned data transmission device and the device for determining the prohibited cell are program modules (for example, a set of program instructions for implementing a certain specific function) and hardware modules. For the latter, it can be expressed in the following form, but is not limited to this: the expression form of each of the above-mentioned modules is a processor, or the functions of each of the above-mentioned modules are implemented by a processor.

[0143] The serial numbers of the above-mentioned embodiments of the present disclosure are for description only and do not represent the advantages or disadvantages of the embodiments.

[0144] In the above embodiments of the present disclosure, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0145] In the several embodiments provided in the present disclosure, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0146] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0147] In addition, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0148] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0149] The above is only a preferred embodiment of the present disclosure. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present disclosure. These improvements and modifications should also be regarded as within the scope of protection of the present disclosure.

Claims

1. A data transmission method, comprising: The base station centralized entity receives the service cell reduced capability user equipment RedCap UE configuration related information sent by the base station separation entity through the base station internal interface message, wherein the service cell RedCap UE configuration related information includes: a cell prohibition mark of a RedCap UE with a single receiver Rx, a cell prohibition mark of a RedCap UE with dual Rx, a cell prohibition mark of an enhanced reduced capability user equipment eRedCap UE with a single Rx, a cell prohibition mark of an eRedCap UE with dual Rx, and at least one of a cell prohibition mark of a half-duplex RedCap UE, and the base station centralized entity and the base station separation entity both belong to the first base station; When the serving cell RedCap UE configuration related information exists in the serving cell information field, the base station centralized entity determines to provide access and reselection configuration information corresponding to different types of reduced capability user equipment in the system information according to the serving cell RedCap UE configuration related information.

2. The method according to claim 1, wherein: The access and reselection configuration information includes at least one of the following: access frequencies corresponding to the different types of reduced-capability user equipments, and same-frequency reselection identifiers of the different types of reduced-capability user equipments.

3. The method according to claim 2, wherein: The same-frequency reselection identifiers of different types of reduced-capability user equipment include: a reselection identifier of a RedCap UE and a reselection identifier of an eRedCap UE.

4. The method according to claim 1, wherein: The interface message within the base station includes: an F1 interface establishment request message, an F1 interface establishment response message, and a next generation radio access network NG-RAN node configuration update message.

5. The method according to claim 1, wherein: The serving cell RedCap UE configuration related information further includes: a RedCap broadcast message field, wherein the RedCap broadcast message field is used to indicate user equipment that is allowed to access the first base station.

6. The method according to claim 1, wherein: Receiving an uplink radio resource connection RRC message forwarded by the base station separation entity, wherein the uplink RRC message includes a type of user equipment that sends the uplink RRC message; Determine, according to the uplink RRC message, that the user equipment is a reduced capability user equipment.

7. The method according to claim 6, wherein: The uplink RRC message is obtained from an RRC message sent by the terminal, and the RRC message includes: an RRC establishment request message or an RRC update request message.

8. The method according to claim 1, wherein: The different types of reduced-capability user equipment include: RedCap UE with single RX, RedCap UE with dual RX, eRedCap UE with single RX, eRedCap UE with dual RX, half-duplex RedCap UE and half-duplex eRedCap UE.

9. A data transmission method, comprising: The base station separation entity sends the service cell RedCap UE configuration related information to the base station centralized entity through the base station internal interface message, wherein the service cell RedCap UE configuration related information includes: the cell prohibition mark of the single Rx RedCap UE, the cell prohibition mark of the dual Rx RedCap UE, the cell prohibition mark of the single Rx eRedCap UE, the cell prohibition mark of the dual Rx eRedCap UE and the cell prohibition mark of the half-duplex RedCap UE. The base station centralized entity and the base station separation entity both belong to the first base station.

10. The method according to claim 9, wherein: The method also includes: receiving access and reselection configuration information corresponding to different types of reduced-capability user equipment sent by the base station centralized entity, wherein the access and reselection configuration information includes: at least one of the access frequencies corresponding to the different types of reduced-capability user equipment and the same-frequency reselection identifiers of the different types of reduced-capability user equipment.

11. The method according to claim 10, wherein: The method further comprises: Acquire configuration information of each type of reduced capability user equipment among the different types of reduced capability user equipment; A broadcast message is generated according to the configuration information, wherein the broadcast message is used to indicate the support status of each serving cell in the first base station for each type of reduced capability user equipment.

12. The method according to claim 11, wherein: The same-frequency reselection identifiers of different types of reduced-capability user equipment include: the same-frequency reselection identifier of eRedCap and the same-frequency reselection identifier of RedCap; The same-frequency reselection flag of the eRedCap exists in the broadcast message, and the service in the first base station is determined. The serving cell supports the eRedCap UE; the same-frequency reselection flag of the eRedCap does not exist in the broadcast message, and it is determined that the serving cell in the first base station does not support the eRedCap UE; The RedCap's same-frequency reselection flag exists in the broadcast message, determining that the service cell in the first base station supports the RedCap UE; the RedCap's same-frequency reselection flag does not exist in the broadcast message, determining that the service cell in the first base station does not support the RedCap UE.

13. The method according to claim 11, wherein: The configuration information includes: information configured by the network management device for each type of reduced-capability user equipment.

14. The method according to claim 11, wherein: The broadcast message includes a first type of broadcast message and a second type of broadcast message, the first type of broadcast message is information in the main system information block MIB, the first type of broadcast message includes: a first type of cell prohibition flag and a same-frequency reselection flag for non-reduced capability type user equipment, the second type of broadcast message is information in the system information block SIB, wherein the second type of broadcast message includes at least one of the following: a second type of cell prohibition flag and the same-frequency reselection flag for reduced capability type user equipment.

15. The method according to claim 14, wherein: The method also includes: broadcasting the broadcast message to the various types of reduced capability user equipment, wherein the reduced capability user equipment determines a prohibited cell that is prohibited from accessing the reduced capability user equipment based on the broadcast message; and encapsulating the second type of broadcast information in separate entity system information, and sending it to the base station centralized entity via the base station internal interface message.

16. The method according to claim 14, wherein: The method also includes: sending the serving cell RedCap UE configuration information to a second base station, wherein the second base station is any base station different from the first base station, and the serving cell RedCap UE configuration information is used to determine a serving cell allowed to be accessed for the reduced capability type user equipment in the second base station.

17. The method according to claim 14, wherein: The second type of cell prohibition mark includes: the cell prohibition mark of RedCap UE with single RX, the cell prohibition mark of RedCap UE with dual RX, the cell prohibition mark of eRedCap UE with single RX, the cell prohibition mark of eRedCap UE with dual RX, the cell prohibition mark of half-duplex RedCap UE and the cell prohibition mark of half-duplex eRedCap UE.

18. The method according to claim 17, wherein: The cell prohibition flag of the single RX RedCap UE, the cell prohibition flag of the dual RX RedCap UE, the cell prohibition flag of the single RX eRedCap UE, the cell prohibition flag of the dual RX eRedCap UE, the cell prohibition flag of the half-duplex RedCap UE and the cell prohibition flag of the half-duplex eRedCap UE all include a prohibition field and a non-prohibition field; The value of the prohibition field in the cell prohibition flag of the RedCap UE with a single RX is prohibition, and it is determined that the serving cell indicated by the cell prohibition flag of the RedCap UE with a single RX does not allow the RedCap UE with a single RX to access; The value of the prohibition field in the cell prohibition flag of the dual RX RedCap UE is prohibition, and it is determined that the service cell indicated by the cell prohibition flag of the dual RX RedCap UE does not allow the dual RX RedCap UE to access; The value of the prohibition field in the cell prohibition flag of the eRedCap UE with a single RX is prohibition, and it is determined that the serving cell indicated by the cell prohibition flag of the eRedCap UE with a single RX does not allow the reduced capability user equipment eRedCap UE with a single RX to access; The value of the prohibition field in the cell prohibition flag of the dual RX eRedCap UE is prohibition, and it is determined that the service cell indicated by the cell prohibition flag of the dual RX eRedCap UE does not allow the dual RX eRedCap UE to access; The value of the prohibition field in the cell prohibition flag of the half-duplex RedCap UE is prohibition, and it is determined that the serving cell indicated by the cell prohibition flag of the half-duplex RedCap UE does not allow the half-duplex RedCap UE to access; The value of the prohibition field in the cell prohibition flag of the half-duplex eRedCap UE is prohibition, and it is determined that the serving cell indicated by the cell prohibition flag of the half-duplex eRedCap UE does not allow the half-duplex eRedCap UE to access.

19. The method according to claim 18, wherein: The method further comprises: The prohibition field in the cell prohibition flag of the single RX RedCap UE does not exist, determining that the serving cell indicated by the cell prohibition flag of the single RX RedCap UE does not allow the single RX reduced capability user equipment RedCap UE to access; The prohibition field in the cell prohibition flag of the dual RX RedCap UE does not exist, and it is determined that the serving cell indicated by the cell prohibition flag of the dual RX RedCap UE does not allow the dual RX RedCap UE access; The prohibition field in the cell prohibition flag of the eRedCap UE with a single RX does not exist, and it is determined that the serving cell indicated by the cell prohibition flag of the eRedCap UE with a single RX does not allow the reduced capability user equipment eRedCap UE with a single RX to access; The prohibition field in the cell prohibition flag of the dual RX eRedCap UE does not exist, and it is determined that the serving cell indicated by the cell prohibition flag of the dual RX eRedCap UE does not allow the dual RX eRedCap UE to access; The prohibition field in the cell prohibition flag of the half-duplex RedCap UE does not exist, determining that the serving cell indicated by the cell prohibition flag of the half-duplex RedCap UE does not allow the half-duplex RedCap UE to access; The prohibition field in the cell prohibition flag of the half-duplex eRedCap UE does not exist, and it is determined that the serving cell indicated by the cell prohibition flag of the half-duplex eRedCap UE does not allow the half-duplex eRedCap UE to access.

20. The method according to claim 9, wherein: The method further comprises: Receive radio resource connection RRC messages sent by multiple types of reduced-capability user equipment, and forward uplink RRC messages in the RRC messages to the base station centralized entity, wherein the RRC messages include: RRC establishment request messages, or RRC update request messages.

21. A method for determining a prohibited cell, comprising: The user equipment receives a broadcast message sent by a base station separation entity, wherein the broadcast message includes a first type of broadcast message and a second type of broadcast message, the first type of broadcast message is information in a main system information block MIB, the first type of broadcast message includes: a first type of cell prohibition identifier and a same-frequency reselection identifier of a non-reduced capability type user equipment, and the second type of broadcast message is information in a system information block SIB, wherein the second type of broadcast message includes at least one of the following: a second type of cell prohibition identifier and a same-frequency reselection identifier of a reduced capability type user equipment, and the same-frequency reselection identifier is used to indicate that a cell reselection is performed on multiple serving cells whose frequency is an access frequency; A prohibited cell in a first base station is determined according to the broadcast message, wherein the first base station is a base station to which the base station separation entity belongs.

22. The method according to claim 21, wherein: Determining a prohibited cell in the base station according to the broadcast message includes: If the first type of cell prohibition flag in the first type of broadcast message indicates prohibition, and the user equipment is the non-reduced capability user equipment, determining the serving cell indicated by the first type of cell prohibition flag as the prohibited cell; and performing cell reselection on the remaining multiple serving cells having the same frequency as the prohibited cell; If the first type of prohibition indicator in the first type of broadcast message indicates prohibition, and the user equipment is the reduced capability user equipment, the prohibited cell is determined according to the second type of broadcast message.

23. The method according to claim 22, wherein: Determining the prohibited cell according to the second-type broadcast message includes: Detecting whether the second-type broadcast message is received and obtaining a detection result; If the detection result indicates that the second type of broadcast message is not received, determining the serving cell indicated by the first type of prohibition identifier as the prohibited cell; and prohibiting cell reselection for the remaining multiple serving cells having the same frequency as the prohibited cell; If the user equipment is in the target state, the detection result indicates that the second type of broadcast message is received, and the second type of broadcast message does not include the same-frequency reselection identifier, the service cell indicated by the first type of prohibition identifier is determined as the prohibited cell, wherein the target state includes: RRC idle state, RRC inactive state and RRC activated state when the T311 timer is running; and, performing cell reselection on the remaining multiple service cells having the same frequency as the prohibited cell.

24. The method according to claim 22, wherein: The method further comprises: If the user equipment is any one of a single RX RedCap UE, a dual RX RedCap UE, a single RX eRedCap UE, a dual RX eRedCap UE, a half-duplex RedCap UE or a half-duplex eRedCap UE, and the second type of cell prohibition identifier in the second type of broadcast message of the user equipment indicates prohibition, the service cell indicated by the second type of cell prohibition identifier is determined to be a prohibited cell.

25. A data transmission device, comprising: A receiving module is used to receive the service cell reduced capability user equipment RedCap UE configuration related information sent by the base station separation entity through the base station interface message, wherein the service cell RedCap UE configuration related information includes: a cell prohibition mark of a single Rx RedCap UE, a cell prohibition mark of a dual Rx RedCap UE, a cell prohibition mark of a single Rx reduced capability user equipment eRedCap UE, and a cell prohibition mark of a dual Rx eRedCap UE. At least one of a cell prohibition mark and a cell prohibition mark of a half-duplex RedCap UE; A determination module is used to determine, when the service cell RedCap UE configuration related information exists in the service cell information field, to provide access and reselection configuration information corresponding to different types of reduced capability user equipment in the system information according to the service cell RedCap UE configuration related information, wherein the access and reselection configuration information includes at least one of the following: the access frequency corresponding to the different types of reduced capability user equipment and the same-frequency reselection identifier of the different types of reduced capability user equipment.

26. A data transmission device, comprising: A sending module is used to send the service cell RedCap UE configuration related information to the base station centralized entity through an interface message within the base station, wherein the service cell RedCap UE configuration related information includes: a cell prohibition mark of a single Rx RedCap UE, a cell prohibition mark of a dual Rx RedCap UE, a cell prohibition mark of a single Rx reduced capability user equipment eRedCap UE, a cell prohibition mark of a dual Rx eRedCap UE and at least one of the cell prohibition marks of a half-duplex RedCap UE.

27. A prohibited cell determination device, comprising: A receiving module, configured to receive a broadcast message sent by a base station separation entity, wherein the broadcast message includes a first type of broadcast message and a second type of broadcast message, the first type of broadcast message is information in a main system information block MIB, the first type of broadcast message includes: a first type of cell prohibition flag and a same-frequency reselection flag of a non-reduced capability user equipment, and the second type of broadcast message is information in a system information block SIB, wherein the second type of broadcast message includes at least one of the following: a second type of cell prohibition flag and a same-frequency reselection flag of a reduced capability user equipment, and the same-frequency reselection flag is used to indicate that a cell reselection is performed on multiple serving cells whose frequency is an access frequency; A determination module is used to determine a prohibited cell in a first base station according to the broadcast message, wherein the first base station is a base station to which the base station separation entity belongs.

28. A base station, comprising a base station separation entity and a base station concentration entity, wherein: The base station separation entity is used to obtain the service cell RedCap UE configuration information and the RRC message sent by the RedCap UE, and send the service cell RedCap UE configuration information and the RRC message to the base station concentration entity, wherein the service cell RedCap UE configuration information includes: at least one of the cell prohibition identifiers corresponding to multiple types of reduced capability user equipment, the cell prohibition identifier is used to indicate the service cell that the user equipment to which the cell prohibition identifier belongs is prohibited from accessing; and is also used to obtain the service cell according to the received access and reselection configuration information. Determine the support status of the target terminal by the base station to which the base station separation entity belongs based on the configuration information, wherein the support status includes: supporting access or prohibiting access; The base station centralized entity is used to receive the RRC message and the service cell RedCap UE configuration information, determine the target terminal according to the RRC message, and generate access and reselection configuration information of the target terminal based on the service cell RedCap UE configuration information, and send the access and reselection configuration information to the base station separation entity, wherein the target terminal is a reduced capability user equipment that sends the RRC message, and the access and reselection configuration information includes at least one of the following: access frequencies corresponding to different types of reduced capability user equipment and same-frequency reselection identifiers of the different types of reduced capability user equipment.

29. A base station centralized entity, comprising: Memory; A processor is coupled to the memory, and the processor is configured to execute the method according to any one of claims 1 to 8 based on instructions stored in the memory.

30. A base station separation entity, comprising: Memory; A processor is coupled to the memory, and the processor is configured to execute the method according to any one of claims 9 to 20 based on instructions stored in the memory.

31. A user equipment, comprising: Memory; A processor is coupled to the memory, and the processor is configured to execute the method according to any one of claims 21-24 based on the instructions stored in the memory.

32. A base station, comprising: The base station centralized entity as claimed in claim 29; A base station separation entity as claimed in claim 30.

33. A communication system comprising: The base station according to claim 28 or 32; A user equipment as claimed in claim 31.

34. A computer-readable storage medium, wherein: The computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method according to any one of claims 1 to 24 is implemented.

35. A computer program comprising computer instructions, wherein the computer instructions implement the method according to any one of claims 1 to 24 when executed by a processor.

Images