Data transmission method, forbidden cell determination method, and base station of separation architecture

Abstract

The invention discloses a data transmission method, a forbidden cell determination method and a base station of a separation architecture. The method comprises the following steps that: a base station concentration entity receives RedCap configuration related information of serving cell reduced function user equipment, which is sent by a base station separation entity through an interface message in a base station, the RedCap configuration related information of the serving cell comprises at least one of a cell prohibition identifier of RedCap UE of a single receiver Rx, a cell prohibition identifier of RedCap UE of double Rx, a cell prohibition identifier of enhanced and reduced function user equipment eRedCap UE of single Rx, a cell prohibition identifier of eRedCap UE of double Rx and a cell prohibition identifier of half-duplex RedCap UE; when the RedCap configuration related information of the serving cell exists in the information field of the serving cell, the entity in the base station can determine to provide access and reselection configuration information corresponding to different types of RedCap UE in the system information according to the RedCap configuration related information of the serving cell.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a data transmission method, a method for determining a prohibited cell, and a base station with a separated architecture. Background Art

[0002] 5G application scenarios include enhanced mobile broadband (eMBB), massive machine type of communication (mMTC), ultra-reliable low latency communication (uRLLC) and time-sensitive communication (TSC), while some use cases require higher communication capabilities of wireless networks than low power wide area network technology (LPWA), but lower than uRLLC and eMBB. In order 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 the complexity and cost of equipment, reduce size and energy consumption, and provide services for blind spot scenarios other than eMBB, mMTC and URLLC.

[0003] At present, in the 17th version of the Third Generation Partnership Project (3GPP Rel-17) protocol, there is no subdivision of different versions of RedCap terminals (User Equipment, UE). 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 mark 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 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.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present application provide a data transmission method, a method for determining prohibited cells, and a base station with a separated architecture, so as to at least solve the technical problem that the demand for scheduling RedCap users and eRedCap users in a wireless base station separated architecture cannot be met due to the fact that the current 3GPP Rel-17 protocol does not subdivide different versions of reduced capability devices.

[0006] According to one aspect of an embodiment of the present application, a method for data transmission is provided, including: a base station centralized entity receives service cell reduced function user equipment RedCap configuration related information sent by a base station separated entity through an interface message within the base station, wherein the service cell RedCap 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 function user equipment eRedCap UE with a single Rx, a cell prohibition mark of an eRedCap UE with dual Rx and at least one of the cell prohibition marks 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 configuration related information exists in the service cell information field, the base station centralized entity can determine to provide access and reselection configuration information corresponding to different types of reduced function user equipment in the system information based on the service cell RedCap 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-function user equipments, and same-frequency reselection identifiers of different types of reduced-function user equipments.

[0008] Optionally, the same-frequency reselection identifiers of different types of reduced-function 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 Xn interface establishment request message, an Xn interface establishment response message, and a next generation radio access network NG-RAN node configuration update message.

[0010] Optionally, the service cell RedCap 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-function 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-function 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 application, a method for data transmission is provided, including: a base station separation entity sends service cell RedCap configuration-related information to a base station centralized entity through an interface message within the base station, wherein the service cell RedCap 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, and at least one of 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 function devices sent by a base station centralized entity, wherein the access and reselection configuration information includes: at least one of access frequencies corresponding to different types of reduced function devices and same-frequency reselection identifiers of different types of reduced function devices.

[0016] Optionally, the data transmission method also includes: obtaining configuration information of each type of reduced-function device among multiple types of reduced-function 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-function user equipment.

[0017] Optionally, the same-frequency reselection flags of different types of reduced-function equipment include: the same-frequency reselection flag of eRedCap and the same-frequency reselection flag of RedCap; the same-frequency reselection flag of eRedCap exists in the broadcast message, determining that the service cell in the first base station supports eRedCap UE; the same-frequency reselection flag 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 flag of RedCap exists in the broadcast message, determining that the service cell in the first base station supports RedCap UE; the same-frequency reselection flag 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-function 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 functional 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 functional type user equipment.

[0020] Optionally, the data transmission method also includes: broadcasting the broadcast message to each type of reduced-function user equipment, wherein the reduced-function user equipment determines a prohibited cell that the reduced-function 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.

[0021] Optionally, the data transmission method also includes: sending the service cell RedCap 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 configuration information is used to determine the service cell allowed to access for the reduced-function user equipment in the second base station.

[0022] Optionally, 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.

[0023] Optionally, the cell prohibition flag of the RedCap UE with single RX, the cell prohibition flag of the RedCap UE with dual RX, the cell prohibition flag of the eRedCap UE with single RX, the cell prohibition flag of the eRedCap UE with dual RX, the cell prohibition flag of the half-duplex RedCap UE and the cell prohibition flag of the half-duplex eRedCap UE all include prohibition fields and non-prohibition fields; the value of the prohibition field in the cell prohibition flag of the RedCap UE with single RX is prohibition, determining that the service cell indicated by the cell prohibition flag of the RedCap UE with single RX does not allow the RedCap UE with single RX to access; the value of the prohibition field in the cell prohibition flag of the RedCap UE with dual RX is prohibition, determining that the service cell indicated by the cell prohibition flag of the RedCap UE with dual RX does not allow the RedCap UE with dual RX to access; the value of the prohibition field in the cell prohibition flag of the eRedCap UE with single RX is prohibition, determining that the eRedCap UE with single RX The service cell indicated by the cell prohibition flag of the UE does not allow the single RX reduced capability user equipment eRedCapUE to access; the value of the prohibition field in the cell prohibition flag of the dual RX eRedCap UE is prohibition, which determines 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, which determines that the service 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, which determines that the service cell indicated by the cell prohibition flag 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 also includes: receiving wireless resource connection RRC messages sent by multiple types of reduced-function user equipment, and forwarding the 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.

[0026] According to another aspect of an embodiment of the present application, a method for determining a prohibited cell 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 a main system information block MIB, the first type of broadcast message includes: a first type of cell prohibition flag and an intra-frequency reselection flag of a non-reduced functional 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 flag and an intra-frequency reselection flag of a reduced functional type user equipment, the intra-frequency reselection flag is used to indicate cell reselection for multiple service cells with a frequency as an access frequency; determining 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.

[0027] Optionally, determining prohibited cells in a base station according to a broadcast message includes: if a first-category cell prohibition flag in a first-category broadcast message indicates prohibition, and the user equipment is a non-reduced-function user equipment, determining a service cell indicated by the first-category cell prohibition flag 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 flag in the first-category broadcast message indicates prohibition, and the user equipment is a reduced-function user equipment, determining the prohibited cell according to a second-category broadcast message.

[0028] Optionally, determining the prohibited cell according to 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 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 eRedCapUE, 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 as a prohibited cell.

[0030] According to another aspect of an embodiment of the present application, a data transmission device is also provided, including: a receiving module, a base station centralized entity receives service cell reduced function device RedCap configuration related information sent by a base station separated entity through an interface message within the base station, wherein the service cell RedCap 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 function device 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, and the base station centralized entity and the base station separated entity both belong to the first base station; a determination module, for when the service cell RedCap configuration related information exists in the service cell information field, the base station centralized entity can determine to provide access and reselection configuration information corresponding to different types of reduced function user equipment in the system information according to the service cell RedCap 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 function user equipment, and same-frequency reselection marks of different types of reduced function user equipment.

[0031] According to another aspect of an embodiment of the present application, a data transmission device is also provided, including: a sending module, wherein the base station separation entity sends the service cell RedCap configuration-related information to the base station centralized entity through an interface message within the base station, wherein the service cell RedCap 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-function device 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, and the base station centralized entity and the base station separation entity both belong to the first base station.

[0032] According to another aspect of an embodiment of the present application, a device for determining a prohibited cell is also provided, including: a receiving module, a user equipment 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 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 function 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 function user equipment, 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, used to determine 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.

[0033] According to another aspect of an embodiment of the present application, a base station with a separation architecture is also provided, including a base station separation entity and a base station centralized entity, wherein the base station separation entity is used to obtain the service cell RedCap configuration information and the RRC message sent by the RedCap terminal, and send the service cell RedCap configuration information and the RRC message to the base station centralized entity, wherein the service cell RedCap configuration information includes: at least one of the cell prohibition identifiers corresponding to multiple types of reduced function user equipment UE, 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 is used to receive the RRC message and the service cell R edCap configuration information, determines the target terminal according to the RRC message, and generates the access and reselection configuration information of the target terminal based on the service cell RedCap configuration information, and sends the access and reselection configuration information to the base station separation entity, wherein the target terminal is a terminal of the reduced function type 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 function user equipment, and same-frequency reselection identifiers of different types of reduced function user equipment; the base station separation entity is also used to determine the support status of the base station to which the base station separation entity belongs for the target terminal according to the received access and reselection configuration information, wherein the support status includes: supporting access or prohibiting access.

[0034] In an embodiment of the present application, a base station centralized entity is used to receive the service cell RedCap configuration related information sent by the base station separation entity through the base station interface message, wherein the service cell RedCap 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 reduction function device eRedCap UE with a single Rx, the cell prohibition mark of the eRedCap UE with dual Rx and the half-duplex RedCap At least one of the cell prohibition identifications of the UE, the base station centralized entity and the base station separated entity both belong to the first base station; when the service cell RedCap configuration related information exists in the service cell information field, the base station centralized entity can determine the way to provide access and reselection configuration information corresponding to different types of reduced function devices in the system information according to the service cell RedCap configuration related information, and by subdividing the indications of different types of reduced function user equipment, the centralized entity can independently control which type of reduced function user equipment is allowed to reside in the cell and whether this type of UE can perform same-frequency cell reselection in a congested scenario, thereby achieving the purpose of completely decoupling the R17 version of the reduced function user equipment RedCap and the R18 version of the reduced function user equipment eRedCap, so that the base station can identify the type of reduced function user equipment in the access process and the connection state, thereby achieving the technical effect of targeted scheduling and optimization of the R18 version of the eRedCap and the R17 version of the RedCap, reducing the impact on the performance of the traditional UE or the R18 version of the eRedCap UE, thereby solving the current 3GPP The Rel-17 protocol does not subdivide different versions of reduced-capacity devices, resulting in the inability to meet the technical problem of scheduling RedCap users and eRedCap users in a wireless base station separation architecture. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0036] Figure 1 It is a flowchart of a method for transmitting data according to an embodiment of the present application;

[0037] Figure 2 is a flowchart of another method step of data transmission provided according to an embodiment of the present application;

[0038] Figure 3 is a flowchart of a method for determining a prohibited cell according to an embodiment of the present application;

[0039] Figure 4 is a structural diagram of a data transmission device provided according to an embodiment of the present application;

[0040] Figure 5 is a structural diagram of another data transmission device provided according to an embodiment of the present application;

[0041] Figure 6 is a structural diagram of a device for determining a prohibited cell provided according to an embodiment of the present application;

[0042] Figure 7 It is a structural diagram of a base station with a separation architecture provided according to an embodiment of the present application. DETAILED DESCRIPTION

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

[0044] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application 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 data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising 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.

[0045] In the related technology, 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 intra-frequency neighboring cell reselection is allowed. In the new radio access technology (New Radio, 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 specific 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, and defines the scheduling of other system information; SIB1 also contains radio resource configuration information common to all UEs and barring information applied to unified access control. RedCap UE needs to read the cell barring flag in the MIB as the first step, and then decide whether to stay in the cell through the RedCap-specific cell barring flag in SIB1. The RedCap-specific IFRI means whether the RedCap UE can reselect the same-frequency cell when it is prohibited from access.

[0046] RedCap devices are divided into two types: 1 transmission antenna and 1 reception antenna (1Transmission 1 Reception, 1T1R) and 1T2R. The data rates of RedCap devices with only one receiver (Receiver, RX) and RedCap devices with two RXs are different. The rate of RedCap devices with only one receiver (Receiver, RX) is lower, which affects the network throughput. The network may tend to prohibit RedCap devices with only one receiver (Receiver, RX) that affect the network throughput when the network capacity is limited. Therefore, separate cell prohibition indications need to be set for RedCap devices with 1Rx and RedCap devices with 2Rx. In the R17 version, the corresponding cell prohibition indications are as follows: The cell prohibition indication of 1RX is set to "prohibited" or "not prohibited"; This field is common to all PLMNs and NPNs when multiple public land mobile networks (PLMNs) or network slices (NPNs) are indicated in the SIB1 message. This field is only applicable 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. cellBarredindication 1RX value "barred" means that for RedCap UEs with one Rx branch, the cell is barred, as defined in protocol TS38.304, and non-RedCap UEs ignore this field; cellBarredindication 2RX value "barred" means that for RedCap UEs with one Rx branch, the cell is barred, as defined in protocol TS38.304, and non-RedCap UEs ignore this field.

[0047] According to the current protocol, when a base station separation architecture is adopted, the base station node component (gNB-Distributed Unit, gNB-DU) generates SIB1 and MIB broadcast messages and the configuration information therein, and the base station node controller unit (gNB-Centralized Unit, gNB-CU) does not read any radio resource control information RRC (RRCASN.1) encoded in the Abstract Syntax Notation One (ASN.1) format, but the gNB-CU still needs to obtain the necessary information such as the cell's prohibition indication of RedCap contained in the SIB message for further configuration operations; therefore, when the base station adopts a gNB-CU and gNB-DU separation architecture, the following problems will exist when supporting different versions of RedCap devices: 1) There is no subdivision of different versions of RedCap UEs, and some cells that do not support R17RedCap may support R18 eRedCap. If the R17 version of the cell prohibition identifier is still used to cover the R18 version of eRedCap, the existing R17 will not be broadcast in the cell that only supports R18 eRedCap. The cell prohibition indication of RedCap will cause the eRedCap that can access the above cell to be unable to access the cell, resulting in a waste of scheduling resources; 2) The control unit in the base station separation architecture 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. In order to solve this problem, the embodiments of the present application provide relevant solutions, which are described in detail below.

[0048] According to an embodiment of the present application, 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.

[0049] The method provided in the embodiment of the present application 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 application has the following differences relative to the normal NRUE: 1) Its spectrum bandwidth is in the Sub-6GHz frequency band, which has a smaller spectrum bandwidth than the 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 antenna and multi-antenna transmission and reception signal (Multiple-Input Multiple-Output, MIMO) layers is reduced, the receiving link of the RedCap terminal can be reduced to 1 or 2, and the corresponding downlink MIMO is reduced to 1 or 2 layers of reception, and the number of antennas is also reduced from the 2T4R antenna of the NRUE to 1T1R or 1T2R; 3) A simpler orthogonal amplitude-phase modulation method (64Quadrature AmplitudeModulation, 64QAM) is adopted to reduce the requirements for radio frequency and baseband; 4) Full duplex Frequency Division Duplex (FD-FDD) and time division duplex (TD-FD) are supported. 5) Enhanced non-continuous reception features, using a longer sleep mode, allowing the terminal to reduce power consumption and obtain a higher endurance; 6) Reduced cache requirements: The length of the packet data convergence protocol layer sequence number (PDCP SN) and the radio link control layer confirmation mode sequence number (RLC-AM SN) is reduced from 18 bits (bit) 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, the coverage is reduced; 9) Half-duplex (Halfduplex FDD, HD-FDD) cannot send and receive at the same time, so the transmission delay increases; 10) RedCap UE does not support dual connection (NR eNB Dual Connection, NE-DC) between 4G wireless access network and 5G NR, nor does it support 5G Dual connectivity between NR and 4G wireless access network.

[0050] Figure 1 is a flowchart of a data transmission method according to an embodiment of the present application. Figure 1As shown, the method comprises the following steps:

[0051] Step S102, the base station centralized entity receives the service cell reduced function user equipment RedCap configuration related information sent by the base station separated entity through the base station internal interface message, wherein the service cell RedCap 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 function 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 separated entity both belong to the first base station.

[0052] Optionally, the service cell RedCap 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.

[0053] In this embodiment, the service cell RedCap configuration-related information, in addition to the cell prohibition flags of different types of RedCap UEs mentioned in the above step S102, also includes a RedCap broadcast message field (RedCap BroadcastInformation), 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, i.e., 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 supporting 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 connected; 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 takes the value of "1", it is confirmed that the half-duplex RedCap UE is allowed to be connected.

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

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

[0056] The method provided in the embodiment of the present application independently configures different types of reduced-function user equipment. In step S102, the base station centralized entity in any base station (i.e., the first base station) receives RedCap configuration-related information sent by the base station separation entity from the same (first) base station through an intra-base station interface message, wherein the service cell RedCap 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.

[0057] Step S104, when the serving cell RedCap 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 configuration related information.

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

[0059] Optionally, the access and reselection configuration information includes at least one of the following: access frequencies corresponding to different types of reduced-function user equipment, and intra-frequency reselection identifiers of different types of reduced-function user equipment. In an optional embodiment of the present application, when the base station centralized entity provides access and reselection configuration information for different types of reduced-function user equipment in the system information, the access and reselection configuration information corresponding to each type of reduced-function user equipment includes: at least one of an access frequency and an intra-frequency reselection identifier, wherein the access frequency indicates the frequency at which the reduced-function 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 type of reduced-function user equipment is prohibited from accessing.

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

[0061] The same-frequency reselection identifiers of different types of reduced-function user equipment mentioned in the above embodiments include two types: 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.

[0062] According to some optional embodiments of the present application, an uplink wireless 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-function user equipment based on the uplink RRC message.

[0063] 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 functional type based on the received uplink RRC message.

[0064] 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.

[0065] 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.

[0066] According to an optional embodiment of the present application, different types of reduced-function 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.

[0067] The method provided in the embodiments of the present application supports different types of reduced-function 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.

[0068] Through the above steps, it is possible to achieve the forwarding of reduced-function user equipment configuration related information from the base station separation entity to the base station centralized entity and the forwarding of configuration information at the RAN level in the separation architecture, so that the base station centralized entity can obtain the support strategies of different cells for various types of reduced-function user equipment, enhance the interoperability between the base station separation entity and the base station centralized entity in the base station separation architecture, and enhance the interaction capability between RAN nodes, so that the network can independently control the residence status of various types of UEs in congestion scenarios, and ensure the flexibility and timeliness of network optimization strategies.

[0069] Figure 2 is a flowchart of another method for data transmission provided according to an embodiment of the present application, such as Figure 2 As shown, the method comprises the following steps:

[0070] In step S202, the base station separation entity sends the service cell RedCap configuration related information to the base station centralized entity through the base station internal interface message, wherein the service cell RedCap 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.

[0071] 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 configuration-related information including at least one of the cell prohibition flag of single Rx RedCap UE, the cell prohibition flag of dual Rx RedCap UE, the cell prohibition flag of single Rx eRedCap UE, the cell prohibition flag of dual Rx eRedCap UE and the cell prohibition flag 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 may be an F1 establishment request message requesting to establish an open interface (F1) or a base station separation entity configuration update message.

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

[0073] In this embodiment, when the interface message within the base station is the F1 setup request message (F1 Setup Request), after the base station separation entity sends the service cell RedCap configuration-related information to the base station centralized entity based on the F1 Setup 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 frequencies at which each type of reduced-function user equipment is allowed to access, and one or more of the same-frequency reselection identifiers (IFRI) of each type of RedCap UE, and the above-mentioned same-frequency reselection identifier (IFRI) indicates whether same-frequency cell reselection can be performed when this type of reduced-function user equipment is prohibited from access.

[0074] According to an optional embodiment of the present application, the same-frequency reselection identifiers of different types of reduced-function 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.

[0075] The same-frequency reselection identifiers of different types of reduced-function 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 there is the same-frequency reselection identifier of the RedCap UE or the same-frequency reselection identifier of the eRedCap 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 the access of RedCap UE and eRedCap UE. Otherwise, if there is no same-frequency reselection identifier of RedCap in the broadcast message generated by the base station separation entity of the first base station, and only the same-frequency reselection identifier of RedCap exists, it is determined that the cell within the coverage of the first base station supports the access of eRedCap UE, but does not support the access of RedCap UE.

[0076] According to another optional embodiment of the present application, the data transmission method also includes: obtaining configuration information of each type of reduced-function user equipment among multiple types of reduced-function 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-function user equipment.

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

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

[0079] The configuration information of the reduced-function user equipment in the previous embodiment may be the network management configuration of various types of reduced-function user equipment, wherein the network management configuration of the reduced-function user equipment may be in the following form: the RedCap broadcast message field is a bit string of size 8, i.e., 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" indicates support for R17 version dual Rx RedCap UE access, the third position "1" indicates support for R18 version single Rx eRedCap UE access, the fourth position "1" indicates support for R18 version dual Rx eRedCap UE access, and the fifth position "1" indicates support for half-duplex RedCap UE access.

[0080] According to an optional embodiment of the present application, 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 functional 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 functional type user equipment.

[0081] In this embodiment, the broadcast message corresponding to the support state generated by the base station separation entity includes: MIB information (i.e., the first type of broadcast information) and SIB information (i.e., the second type of broadcast information), 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), which is general information. The SIB information includes: a RedCap-specific cell prohibition identifier (i.e., the second type of cell prohibition identifier) ​​for determining whether the RedCap UE can reside in the service cell of the (first) base station; the SIB information may also include a RedCap-specific same-frequency reselection identifier (IFRI) for indicating whether the RedCap UE can reselect the same-frequency cell when it is prohibited from access. It should be noted that the SIB may include both the RedCap-specific cell prohibition identifier and the RedCap-specific same-frequency reselection identifier (IFRI), or only one of the information. The SIB also contains radio resource configuration information common to all UEs. The information in the above SIB is usually stored in the system information block 1 (SIB1).

[0082] Optionally, 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.

[0083] In this embodiment, the cell barring flag unique to RedCap (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 SIB1 and MIB messages according to the network management configuration code, wherein 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 permission 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 at the same time or only one of them.

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

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

[0086] According to some optional embodiments of the present application, the cell prohibition flag of a RedCap UE with a single RX, the cell prohibition flag of a RedCap UE with a dual RX, the cell prohibition flag of a eRedCap UE with a single RX, the cell prohibition flag of a eRedCap UE with a dual RX, the cell prohibition flag of a half-duplex RedCap UE and the cell prohibition flag 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 flag of the RedCap UE with a single RX is prohibition, determining that the service 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 RedCap UE with a dual RX is prohibition, determining that the service cell indicated by the cell prohibition flag of the RedCap UE with a dual RX does not allow the RedCap UE with a dual RX to access; the value of the prohibition field in the cell prohibition flag of the eRedCap UE with a single RX is prohibition, determining that the service cell indicated by the cell prohibition flag of the eRedCap UE with a single RX does not allow the reduced-capacity user equipment eRedCap UE with a single RX to access; the eRedCap UE with a dual RX The value of the prohibited field in the cell prohibition flag of the UE is prohibited, which determines 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 prohibited field in the cell prohibition flag of the half-duplex RedCap UE is prohibited, which determines that the service 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 prohibited field in the cell prohibition flag of the half-duplex eRedCap UE is prohibited, which determines that the service cell indicated by the cell prohibition flag of the half-duplex eRedCap UE does not allow the half-duplex eRedCap UE to access.

[0087] In some embodiments, when these five types of cell barring flags are enumerated type fields, the cell barring flag of single Rx RedCap UE (cellBarred-RedCap1Rx-r17), the cell barring flag of dual Rx RedCap UE (cellBarred-RedCap2Rx-r17), the cell barring flag of single Rx eRedCap UE (cellBarred-eRedCap1Rx-r18), and the cell barring flag of dual Rx eRedCap UE (cellBarred-eRedCap2Rx-r18) all enumerate the "barred" field and the "not-barred" field; and for the cell barring flag 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.

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

[0089] 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.

[0090] In the embodiment of the present application, for the cell prohibition flag (cellBarred-RedCaplRx-r17) of the RedCap UE with a single Rx, when its "prohibited" 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, and the non-RedCap UE and the eRedCap UE of the R18 version will ignore this field. For the cell prohibition flag (cellBarred-RedCap2Rx-r17) of the RedCap UE with dual Rx, when its "prohibited" 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, and the non-RedCap UE and the eRedCap UE of the R18 version will ignore this field. For the cell barring flag (cellBarred-eRedCaplRx-r18) of the eRedCap UE with single Rx, when its "barred" field does not exist, it means that the cell prohibits the eRedCap UE with single Rx antenna from accessing. This field is only applicable to the RedCap UE with single RX of R18 version, and non-RedCap UE and RedCap UE of R17 version will ignore this field. For the cell barring flag (cellBarred-eRedCap2Rx-r18) of the eRedCap UE with dual Rx, when its "barred" field does not exist, it means that the cell prohibits the eRedCap UE with dual Rx antennas from accessing. This field is only applicable to the RedCap UE with dual RX of R18 version, and non-RedCap UE and RedCap UE of 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.

[0091] According to an optional embodiment of the present application, the data transmission method also includes: broadcasting a broadcast message to each type of reduced-function user equipment, wherein the reduced-function user equipment determines a prohibited cell that is prohibited from accessing the reduced-function user equipment 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.

[0092] In this embodiment, after generating broadcast information composed of MIB information and / or SIB1 information, the base station separation entity sends the broadcast information of each type of reduced-function user equipment to each type of reduced-function user equipment to notify each type of reduced-function user equipment which cells allow it to access, or notify each type of reduced-function user equipment which cells do not allow it 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 centralized entity. For example, the SIB1 message is encapsulated in the separate entity system information (System Information) of the gNB-DU, and the gNB-DU service item information (Served Cells Item), RedCap broadcast message field (RedCap Broadcast Information) (the value is 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 through the F1 Setup Request message.

[0093] According to another optional embodiment of the present application, the data transmission method also includes: sending the service cell RedCap 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 configuration information is used to determine the service cell allowed to access for the reduced functional type user equipment in the second base station.

[0094] In this embodiment, the service cell RedCap 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 concentration entity is located, so that the cell allowed to be accessed can be determined in another base station for the RedCap UE. The above method can use the service cell RedCap configuration information to determine the target cell allowed to be accessed for the reduced-function user equipment in the mobility scenario, or to select the optimal service cell allowed to be accessed for the reduced-function user equipment in the scenario where the base station selection is required.

[0095] According to some other optional embodiments of the present application, the data transmission method also includes: receiving wireless resource connection RRC messages sent by various types of reduced-function 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.

[0096] In some embodiments, the base station separation entity receives an RRC message sent by a terminal (i.e., multiple types of RedCap UEs), generates a forwarding message of an initial uplink RRC message, and forwards the uplink RRC message to the base station centralized entity, for example, the gNB-DU receives an RRC connection request message (RRC connectionrequest) sent by the UE, generates an initial uplink RRC (initial UL RRC) message, and forwards the RRC message to the gNB-CU of the base station. The gNB-CU receives the F1 Setup Request message and the RRC message from the UE, determines that the UE is a 2RxRedCap UE of R17 version according to the field (NR RedCap UEIndication IE) used to indicate the type of RedCap UE; and provides a frequency list in the system information that allows the access of the RedCap UE of R18 version according to the RedCap broadcast message field (RedCapBroadcast Information), configures RedCap-IFRI-R17 = "True", and sends it to the gNB-DU.

[0097] Figure 3 is a flowchart of a method for determining a prohibited cell according to an embodiment of the present application. Figure 3 As shown, the method comprises the following steps:

[0098] 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 of a non-reduced functional 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 a same-frequency reselection flag of a reduced functional 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.

[0099] For the terminal interacting with the (first) base station, in step S302, the user equipment (terminal) receives a broadcast message consisting of a MIB message (i.e., a first type of broadcast message) and / or a 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 a cell prohibition identifier (i.e., a first type of cell prohibition identifier) ​​and a same-frequency reselection identifier for general type terminals (i.e., non-RedCap type user equipment), and the SIB information includes a RedCap-specific cell prohibition identifier (i.e., a second type of cell prohibition identifier) ​​and / or a same-frequency reselection identifier.

[0100] Step S304: 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.

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

[0102] According to an optional embodiment of the present application, 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 function user equipment, the service cell indicated by the first type of cell prohibition identifier is determined as a prohibited cell; and cell reselection is performed 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 function user equipment, the prohibited cell is determined according to the second type of broadcast message.

[0103] In this embodiment, the terminal determines the cell that is prohibited from accessing by the following method: for a terminal of a non-reduced functionality type, if the cell prohibition flag is read from the MIB information (i.e., the first type of broadcast information) and is set to "prohibited" (i.e., cellBarred="barred"), the cell is regarded as a prohibited cell, and a cell reselection process is performed on other cells with the same frequency as the prohibited cell; for a terminal of a reduced functionality type, if the cell prohibition flag is read from the MIB information (i.e., the first type of broadcast information) and 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).

[0104] According to another optional embodiment of the present application, determining a prohibited cell according to 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 mark 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 mark, determining the service cell indicated by the first type of prohibition mark 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 having the same frequency as the prohibited cell.

[0105] In this embodiment, the terminal with reduced functional type determines through SIB information (i.e., the second type of broadcast information) whether the prohibited cell has two situations: receiving SIB information (i.e., the second type of broadcast information) and not receiving 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) is not received, the terminal (UE) regards the cell as a prohibited cell, and performs a cell reselection process for other cells with the same frequency as the prohibited cell. If the terminal (UE) is in RRC idle state, RRC inactive state, or RRC active state when the T311 timer is 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), confirms that the SIB information (i.e., the second type of broadcast information) is received, and there is no same-frequency reselection identifier in the received SIB information (i.e., the second type of broadcast information), the UE regards the cell as a prohibited cell.

[0106] 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 eRedCapUE, 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 as a prohibited cell.

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

[0108] Figure 4 is a structural diagram of a data transmission device provided according to an embodiment of the present application, such as Figure 4 As shown, the data transmission device includes: a receiving module 40, a base station centralized entity receives the service cell reduced function user equipment RedCap configuration related information sent by the base station separation entity through the base station interface message, wherein the service cell RedCap 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 function user equipment eRedCap UE, a cell prohibition mark of a dual Rx eRedCap UE and 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; a determination module 42, which is used for when the service cell RedCap configuration related information exists in the service cell information field, the base station centralized entity can determine to provide access and reselection configuration information corresponding to different types of reduced function user equipment in the system information according to the service cell RedCap 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 function user equipment, and same-frequency reselection marks of different types of reduced function user equipment.

[0109] It should be noted that Figure 4 The preferred implementation of the illustrated embodiment can be found in Figure 1 The relevant description of the illustrated embodiment will not be repeated here.

[0110] Figure 5 is a structural diagram of another data transmission device provided according to an embodiment of the present application, such as Figure 5As shown, another data transmission device includes: a sending module 50, the base station separation entity sends the service cell RedCap configuration related information to the base station centralized entity through the base station internal interface message, wherein the service cell RedCap 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 function 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.

[0111] It should be noted that Figure 5 The preferred implementation of the illustrated embodiment can be found in Figure 2 The relevant description of the illustrated embodiment will not be repeated here.

[0112] Figure 6 is a structural diagram of a device for determining a prohibited cell provided in an embodiment of the present application, such as Figure 6 As shown, the device includes: a receiving module 60, 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 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 functional 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 flag and a same-frequency reselection flag of a reduced functional 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 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.

[0113] It should be noted that Figure 6 The preferred implementation of the illustrated embodiment can be found in Figure 3 The relevant description of the illustrated embodiment will not be repeated here.

[0114] Figure 7 is a schematic diagram of a structure of a base station with a separation architecture provided according to an embodiment of the present application, such as Figure 7As shown, 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 configuration information and the RRC message sent by the RedCap terminal, and send the service cell RedCap configuration information and the RRC message to the base station centralized entity, wherein the service cell RedCap configuration information includes: at least one of the cell prohibition identifiers corresponding to multiple types of reduced-function 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; the base station centralized entity 72 is used to receive the RRC message and the service cell RedCap configuration information. The base station separation entity 70 is further used to determine the support status of the base station to which the base station separation entity belongs for the target terminal according to the received access and reselection configuration information, wherein the support status includes: supporting access or prohibiting access.

[0115] 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 support status of the service cell in the base station of the separation architecture for the RedCap type terminal to be accessed is determined by the base station separation entity 70 and the base station centralized entity 72, the base station separation entity 70 sends the service cell RedCap configuration-related information to the first base station centralized entity through the base station internal interface message, wherein the RedCap 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 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-function user equipment based on the received service cell RedCap 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-function 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, based on the received access and reselection configuration message, whether the support status of the base station to which it belongs for the terminal to access is to allow access or not allow access.

[0116] Through the above method, by sending key information in the interface message within the base station, the interoperability between the separated entity and the centralized entity in the separated architecture is enhanced, and 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 is solved. The solution provided by the embodiment of the present application subdivides the indications of different types of reduced-capability user equipment, so that the centralized entity can independently control which type of RedCap UE is allowed to reside on the cell and whether this type of UE can reselect the same-frequency cell in a congested scenario, thereby improving the flexibility and timeliness of the network optimization strategy.

[0117] At the same time, the solution provided by the embodiment of the present application completely decouples the R18 and R17 versions of RedCap, and the base station can identify the type of reduced-function 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 versions of 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 application has no special requirements on the terminal side, and therefore, it also has the advantage of facilitating the deployment and implementation of emergency call services in the wireless base station separation architecture.

[0118] It should be noted that the various modules in the above-mentioned data transmission device and the device for determining the prohibited cell can be program modules (for example, a set of program instructions to implement a specific function) or hardware modules. For the latter, it can be expressed in the following forms, 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.

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

[0120] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0121] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, 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.

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

[0123] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0124] 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 application, 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, which is stored in a storage medium and includes several instructions for 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 application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0125] The above is only a preferred implementation of the present application. 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 application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for data transmission, characterized in that: include: The base station centralized entity receives the service cell reduced function user equipment RedCap configuration related information sent by the base station separation entity through the base station internal interface message, wherein the service cell RedCap 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 function 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 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-function user equipment in the system information according to the serving cell RedCap configuration related information.

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

3. The method according to claim 2, characterized in that The same-frequency reselection identifiers of the different types of reduced-function 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, characterized in that: The base station internal interface message includes: an Xn interface establishment request message, an Xn interface establishment response message, and a next generation radio access network NG-RAN node configuration update message.

5. The method according to claim 1, characterized in that The service cell RedCap configuration related information also 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, characterized in that 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-function user equipment.

7. The method according to claim 6, characterized in that 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, characterized in that The different types of reduced-function 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 method for data transmission, characterized in that: include: The base station separation entity sends the service cell RedCap configuration related information to the base station centralized entity through the base station internal interface message, wherein the service cell RedCap configuration related information includes: the cell prohibition mark of single Rx RedCap UE, the cell prohibition mark of dual Rx RedCap UE, the cell prohibition mark of single Rx eRedCap UE, the cell prohibition mark of dual Rx eRedCap UE and at least one of the cell prohibition mark of 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, characterized in that The method also includes: receiving access and reselection configuration information corresponding to different types of reduced-function 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-function user equipment and the same-frequency reselection identifiers of the different types of reduced-function user equipment.

11. The method according to claim 10, characterized in that The method further comprises: Acquire configuration information of each type of reduced-function user equipment among the different types of reduced-function 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-function user equipment.

12. The method according to claim 11, characterized in that The same-frequency reselection identifiers of different types of reduced-function 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 it is determined that the serving cell in the first base station 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, characterized in that The configuration information includes: information configured by the network management device for each type of reduced-function user equipment.

14. The method according to claim 11, characterized in that 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 functional 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 functional type user equipment.

15. The method according to claim 14, characterized in that The method also includes: broadcasting the broadcast message to the various types of reduced-function user equipment, wherein the reduced-function user equipment determines a prohibited cell that is prohibited from accessing the reduced-function 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, characterized in that The method also includes: sending the service cell RedCap 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 configuration information is used to determine a service cell allowed to be accessed for the reduced functionality type user equipment in the second base station.

17. The method according to claim 14, characterized in that 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, characterized in that 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, characterized in that The method further comprises: if the prohibition field in the cell prohibition flag of the RedCap UE with single RX does not exist, determining that the serving cell indicated by the cell prohibition flag of the RedCap UE with single RX does not allow the RedCap UE with single RX 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 to 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, characterized in that The method further includes: receiving radio resource connection RRC messages sent by multiple types of reduced-function user equipment, and forwarding 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, characterized in that: include: 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 flag and a same-frequency reselection flag of a non-reduced functional 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 flag and a same-frequency reselection flag of a reduced functional type 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 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, characterized in that 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 function 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-function user equipment, the prohibited cell is determined according to the second type of broadcast message.

23. The method according to claim 22, characterized in that 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, characterized in that 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, characterized in that: include: A receiving module, a base station centralized entity receives information related to RedCap configuration of a service cell reduced-function user equipment sent by a base station separation entity through an interface message within the base station, wherein the information related to the RedCap configuration of the service cell 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-function 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, and the base station centralized entity and the base station separation entity both belong to the first base station; A determination module is used for, when the service cell RedCap configuration related information exists in the service cell information field, the base station centralized entity can determine to provide access and reselection configuration information corresponding to different types of reduced function user equipment in the system information based on the service cell RedCap 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 function user equipment, and the same-frequency reselection identifier of the different types of reduced function user equipment.

26. A data transmission device, characterized in that: include: The sending module, the base station separation entity sends the service cell RedCap configuration related information to the base station centralized entity through the base station internal interface message, wherein the service cell RedCap 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 function 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.

27. A device for determining a prohibited cell, characterized in that: include: A receiving module, 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 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 function 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 function 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 with a separated architecture, characterized in that: It includes 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 configuration information and the RRC message sent by the RedCap terminal, and send the service cell RedCap configuration information and the RRC message to the base station centralized entity, wherein the service cell RedCap configuration information includes: at least one of the cell prohibition identifiers corresponding to multiple types of reduced-function user equipment, and 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; The base station centralized entity is used to receive the RRC message and the serving cell RedCap configuration information, determine the target terminal according to the RRC message, and generate the access and reselection configuration information of the target terminal based on the serving cell RedCap configuration information, and send the access and reselection configuration information to the base station separation entity, wherein the target terminal is a reduced function 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 function user equipment, and same-frequency reselection identifiers of the different types of reduced function user equipment; The base station separation entity is further used to determine the support status of the base station to which the base station separation entity belongs for the target terminal according to the received access and reselection configuration information, wherein the support status includes: supporting access or prohibiting access.

Images