WO2018203739A1 - Procédé d'établissement d'une interface fronthaul, procédé de mise en œuvre d'un accès pour un équipement utilisateur, procédé et appareil de mise en œuvre d'un transfert intercellulaire pour un équipement utilisateur, procédé de transfert de données, équipement utilisateur et station de base - Google Patents

Procédé d'établissement d'une interface fronthaul, procédé de mise en œuvre d'un accès pour un équipement utilisateur, procédé et appareil de mise en œuvre d'un transfert intercellulaire pour un équipement utilisateur, procédé de transfert de données, équipement utilisateur et station de base Download PDF

Info

Publication number
WO2018203739A1
WO2018203739A1 PCT/KR2018/005290 KR2018005290W WO2018203739A1 WO 2018203739 A1 WO2018203739 A1 WO 2018203739A1 KR 2018005290 W KR2018005290 W KR 2018005290W WO 2018203739 A1 WO2018203739 A1 WO 2018203739A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
message
data
base station
allocated
Prior art date
Application number
PCT/KR2018/005290
Other languages
English (en)
Inventor
Lixiang Xu
Weiwei Wang
Xiaowan KE
Hong Wang
Shichang Zhang
Yingyang Li
Yi Wang
Xiaoning MA
Original Assignee
Samsung Electronics Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201710458428.4A external-priority patent/CN109246747B/zh
Priority claimed from CN201810010479.5A external-priority patent/CN110012480A/zh
Priority to EP21190384.4A priority Critical patent/EP3927107B1/fr
Priority to EP20206531.4A priority patent/EP3796745B1/fr
Priority to KR1020217014014A priority patent/KR102301907B1/ko
Priority to KR1020187037456A priority patent/KR102252271B1/ko
Application filed by Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Priority to EP18793976.4A priority patent/EP3479647B1/fr
Priority to US16/318,244 priority patent/US10880789B2/en
Priority to ES18793976T priority patent/ES2841848T3/es
Publication of WO2018203739A1 publication Critical patent/WO2018203739A1/fr
Priority to US16/250,519 priority patent/US10880799B2/en
Priority to US17/128,964 priority patent/US11546811B2/en
Priority to US17/128,921 priority patent/US11477703B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/087—Reselecting an access point between radio units of access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present disclosure relates to radio communications, and particularly to a method for establishing a fronthaul interface, a method for performing access for a UE, a method and apparatus for performing a handover for a user equipment (UE), a method for data forwarding in a 5G communication network, a user equipment and a base station.
  • a method for establishing a fronthaul interface a method for performing access for a UE, a method and apparatus for performing a handover for a user equipment (UE), a method for data forwarding in a 5G communication network, a user equipment and a base station.
  • the 5G or pre-5G communication system is also called a 'Beyond 4G Network' or a 'Post LTE System'.
  • the 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60GHz bands, so as to accomplish higher data rates.
  • mmWave e.g., 60GHz bands
  • MIMO massive multiple-input multiple-output
  • FD-MIMO Full Dimensional MIMO
  • array antenna an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
  • RANs Cloud Radio Access Networks
  • D2D device-to-device
  • CoMP Coordinated Multi-Points
  • FQAM Hybrid FSK and QAM Modulation
  • SWSC sliding window superposition coding
  • ACM advanced coding modulation
  • FBMC filter bank multi carrier
  • NOMA non-orthogonal multiple access
  • SCMA sparse code multiple access
  • the Internet which is a human centered connectivity network where humans generate and consume information
  • IoT Internet of Things
  • IoE Internet of Everything
  • sensing technology “wired/wireless communication and network infrastructure”, “service interface technology”, and “Security technology”
  • M2M Machine-to-Machine
  • MTC Machine Type Communication
  • IoT Internet technology services
  • IoT may be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing Information Technology (IT) and various industrial applications.
  • IT Information Technology
  • 5G communication systems to IoT networks.
  • technologies such as a sensor network, Machine Type Communication (MTC), and Machine-to-Machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas.
  • MTC Machine Type Communication
  • M2M Machine-to-Machine
  • Application of a cloud Radio Access Network (RAN) as the above-described Big Data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology.
  • RAN Radio Access Network
  • UEs User Equipments
  • gNB access nodes
  • CN core network
  • Fig.1 shows a schematic diagram of system architecture in a next generation of network or a 5G network or communication system.
  • a UE 101 is a terminal device used to receive data.
  • a next generation of radio access network (NG-RAN) 102 is a radio access network, including a base station (a gNB or an eNB that is connected to a 5G core network (5GC)) for providing an interface for the UE to access a radio network.
  • a base station a gNB or an eNB that is connected to a 5G core network (5GC)
  • 5GC 5G core network
  • An access and mobility management function (AMF) 103 is responsible for managing UE mobility context and security information.
  • a user plane function (UPF) 104 is configured to provide functions of a user plane.
  • a session management function (SMF) 105 is responsible for session management.
  • a data network (DN) 106 includes an operator's services, access to the Internet, services of the third party, and so on.
  • a gNB in the 5G may be further divided into a central unit (gNB-CU) and a distributed unit (gNB-DU) which are abbreviated as CU and DU in the following.
  • the packet data convergence protocol (PDCP) and radio resource control (RRC) functions are on the CU.
  • the radio link control (RLC), media access control (MAC) and physical layer functions are on the DU.
  • the F1 interface may be divided into a control plane (F1-C) and a user plane (F1-U).
  • the transport network layer of the F1-C is based on IP transmission.
  • a stream control transmission protocol (SCTP) protocol is added above the IP.
  • the application layer protocol of the F1 interface is F1AP.
  • the SCTP may provide reliable transmission for application layer messages.
  • UDP/IP user datagram protocol/internet protocol
  • GPRS general packet radio service tunneling protocol user plane
  • PDUs protocol data units
  • Fig. 2 is a schematic diagram of another system architecture in a 5G network or communication system.
  • a UE is connected to a gNB via an air interface (Uu interface) to transmit and receive data in a Control Plane (CP) and a User Plane (UP).
  • Uu interface air interface
  • CP Control Plane
  • UP User Plane
  • different UEs connected to a same gNB may have different radio channel conditions. Some UEs may have a great channel condition; and some UEs may have a poor channel condition, the QoS of those UEs may be influenced significantly so that the user experience will be deteriorated seriously.
  • the normal operation of users may not be satisfied if all users perform communication with a base station. Therefore, some UEs are required to help the base station to forward data of other UEs.
  • the present disclosure provides several methods for establishing a fronthaul interface, methods for performing access for a UE, methods and apparatus for performing a handover and communications for a UE, so as to achieve better intercommunications between a DU and a CU.
  • the present disclosure provides a method for establishing a fronthaul interface, including:
  • a central unit (CU) in a base station receiving, by a central unit (CU) in a base station, a fronthaul interface (F1) establishment request message from a distributed unit (DU) in the base station;
  • CU central unit
  • DU distributed unit
  • the F1 establishment request message includes one or more pieces of the following information: a DU identity of the DU, a serving cell information list on the DU, and capability information of the DU; and
  • the F1 establishment response message includes one or more pieces of the following information: a CU identity of the CU, a list of public land mobile network (PLMN) identities supported by the CU, and a cell configuration list.
  • PLMN public land mobile network
  • serving cell information in the serving cell information list on the DU includes one or more pieces of the following information: a cell identity of a cell, cell frequency information, uplink transmission bandwidth information, downlink transmission bandwidth information, a physical cell identifier, a tracking area identity (TAI) or a tracking area code (TAC), a list of broadcast PLMN identities, transmission reception point (TRP) information, beam information, information of a physical channel in the cell, information of a transport channel in the cell, information of a logic channel in the cell, and a cell access layer protocol (AP) identity used for the F1 interface allocated by the DU; and/or
  • a cell identity of a cell includes one or more pieces of the following information: a cell identity of a cell, cell frequency information, uplink transmission bandwidth information, downlink transmission bandwidth information, a physical cell identifier, a tracking area identity (TAI) or a tracking area code (TAC), a list of broadcast PLMN identities, transmission reception point (TRP) information, beam information, information of a physical channel in
  • cell configuration information in the cell configuration list includes one or more pieces of the following information: a cell identity of a cell, configuration information of a common channel in the cell, system information in the cell, scheduling information for sending the system information, a cell AP identity used for the F1 interface allocated by the CU.
  • the method includes: using, by the CU, the DU capability information to schedule the UE.
  • the method includes:
  • the cell configuration information includes one or more pieces of the following information: the cell identity of the cell, the configuration information of the common channel in the cell, the system information in the cell, the scheduling information for sending the system information, the cell AP identity for the F1 interface allocated by the CU.
  • the cell establishment request message and/or the cell establishment response message is sent through cell signaling, then the cell establishment request message and/or the cell establishment response message does/do not include the cell identity.
  • the method includes: corresponding to one or more established cells, sending, by the CU, a system information transfer message to the DU, in which, the system information transfer message includes a cell identity(s), system information in the cell(s) and/or the scheduling information for sending the system information.
  • the present disclosure further provides a method for establishing a fronthaul interface, including:
  • the F1 establishment request message includes one or more pieces of the following information: a DU identity of the DU, a serving cell information list on the DU, capability information of DU; and
  • the F1 establishment response message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, and a cell configuration list.
  • the present disclosure further provides a CU apparatus for establishing a fronthaul interface, including: a sending unit and a receiving unit; in which
  • the receiving unit is configured to receive an F1 establishment request message from a DU; in which the F1 establishment request message includes one or more pieces of the following: a DU identity of the DU, a serving cell information list on the DU, and capability information of the DU; and
  • the sending unit is configured to send an F1 establishment response message to the DU; in which the F1 establishment response message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, and a cell configuration list.
  • the present disclosure further provides a DU apparatus for establishing a fronthaul interface, including: a sending unit and a receiving unit; in which
  • the sending unit is configured to send an F1 establishment request message to a CU; in which the F1 establishment request message includes one or more pieces of the following information: a DU identity of the DU, a serving cell information list on the DU, capability information of the DU; and
  • the receiving unit is configured to receive an F1 establishment response message from the CU; in which the F1 establishment response message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, and a cell configuration list.
  • the present disclosure further provides a method for establishing a fronthaul interface, including:
  • the F1 establishment request message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, a serving cell information list on the DU, and a cell configuration list; and
  • the F1 establishment response message includes one or more pieces of the following information: a DU identity of the DU, capability information of the DU, and actual configuration information of a cell.
  • the present disclosure further provides a method for establishing a fronthaul interface, including:
  • the F1 establishment request message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, a serving cell information list on the DU, and a cell configuration list; and
  • the F1 establishment response message includes one or more pieces of the following information: a DU identity of the DU, capability information of the DU, and actual configuration information of a cell.
  • the present disclosure further provides a CU apparatus for establishing a fronthaul interface, including: a sending unit and a receiving unit; in which
  • the sending unit is configured to send an F1 establishment request message to a DU; in which the F1 establishment request message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, a serving cell information list on the DU, and a cell configuration list; and
  • the receiving unit is configured to receive an F1 establishment response message from the DU; in which the F1 establishment response message includes one or more pieces of the following information: a DU identity of the DU, capability information of the DU, actual configuration information of a cell.
  • the present disclosure further provides a DU apparatus for establishing a fronthaul interface, including: a sending unit and a receiving unit; in which
  • the receiving unit is configured to receive an F1 establishment request message from a CU for a DU; in which the F1 establishment request message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, a serving cell information list on the DU, and a cell configuration list; and
  • the sending unit is configured to send an F1 establishment response message to the CU; in which the F1 establishment response message includes one or more pieces of the following information: a DU identity of the DU, capability information of the DU, and actual configuration information of a cell.
  • the present disclosure further provides a method for establishing a fronthaul interface, including:
  • the F1 establishment required message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, and a serving cell information list on the DU;
  • the F1 establishment request message includes one or more pieces of the following information: a DU identity of the DU, a serving cell information list on the DU; and capability information of the DU; and
  • the F1 establishment response message includes one or more pieces of the following information: the list of PLMN identities supported by the CU and a cell configuration list.
  • the F1 establishment request message does not include the serving cell information list on the DU;
  • the F1 establishment response message does not include the list of PLMN identities supported by the CU.
  • the method includes: receiving, by the CU, a DU configuration updating message sent from the DU, in which the DU configuration updating message includes updated application layer information of the DU; and/or
  • the method includes: sending, by the CU, a CU configuration updating message which carries updated application layer information of the CU to the DU.
  • the CU sends updated system information and/or scheduling information of the updated system information to the DU.
  • the updated system information and/or the scheduling information of the updated system information is carried in a system information updating message or a DU configuration updating response message.
  • the present disclosure further provides a method for establishing a fronthaul interface, including:
  • the F1 establishment required message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, and a serving cell information list on the DU;
  • the F1 establishment request message includes one or more pieces of the following information: a DU identity of the DU, a serving cell information list on the DU; and capability information of the DU; and
  • the F1 establishment response message includes one or more pieces of the following information: the list of PLMN identities supported by the CU and a cell configuration list.
  • the present disclosure further provides an apparatus for establishing a fronthaul interface, including: a sending unit and a receiving unit; in which
  • the sending unit is configured to send an F1 establishment required message to a DU, and is also configured to send an F1 establishment response message to the DU after the receiving unit receives an F1 establishment request message;
  • the receiving unit is configured to receive the F1 establishment request message from the DU;
  • the F1 establishment required message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, and a serving cell information list on the DU;
  • the F1 establishment request message includes one or more pieces of the following information: a DU identity of the DU, a serving cell information list on the DU; and capability information of the DU; and
  • the F1 establishment response message includes one or more pieces of the following information: the list of PLMN identities supported by the CU and a cell configuration list.
  • the present disclosure further provides a DU apparatus for establishing a fronthaul interface, including: a sending unit and a receiving unit; in which
  • the receiving unit is configured to receive an F1 establishment required message from a CU; and is configured to receive an F1 establishment response message from the CU after the sending unit sends an F1 establishment request message;
  • the sending unit is configured to send an F1 establishment request message to the CU;
  • the F1 establishment required message includes one or more pieces of the following information: a CU identity of the CU, a list of PLMN identities supported by the CU, and a serving cell information list on the DU;
  • the F1 establishment request message includes one or more pieces of the following information: a DU identity of the DU, a serving cell information list on the DU; and capability information of the DU; and
  • the F1 establishment response message includes one or more pieces of the following information: the list of PLMN identities supported by the CU and a cell configuration list.
  • the present disclosure further provides a method for performing access for a UE, including:
  • the initial UE message transfer message includes one or more pieces of the following information: a distributed unit user equipment access layer protocol identity (DU UE AP ID) allocated for the UE by the DU, a cell identity of a cell where the DU receives the RRC connection request message, a tracking area identity (TAI), the RRC connection request message, and a cell-radio network temporary identifier (C-RNTI) allocated for the UE by the DU; and/or
  • DU UE AP ID distributed unit user equipment access layer protocol identity allocated for the UE by the DU
  • TAI tracking area identity
  • C-RNTI cell-radio network temporary identifier
  • the radio bearer configuration request message includes one or more pieces of the following information: a central unit user equipment access layer protocol identity (CU UE AP ID) allocated for the UE by the CU, the DU UE AP ID allocated for the UE by the DU, a cell identity of a cell where the UE is located, information of a radio bearer (RB) to be configured, configuration information of a physical channel, configuration information of a transport channel, configuration information of a logic channel, and uplink tunnel information; and/or
  • the radio bearer configuration response message includes one more pieces of the following information: the CU UE AP ID allocated for the UE by the CU, the DU UE AP ID allocated for the UE by the DU, information of an RB configured for the UE, the C-RNTI allocated for the UE by the DU; and/or
  • the downlink RRC transfer message includes one or more pieces of the following information: the CU UE AP ID allocated for the UE by the CU, the DU UE AP ID allocated for the UE by the DU, the RRC connection establishment message, information of a logic channel for transmitting an RRC message, uplink tunnel information, and a C-RNTI allocated for the UE by the CU; and/or
  • the DU when the DU sends the RRC connection establishment completion message to the CU, the DU sends one or more pieces of the following information to the CU: the CU UE AP ID allocated for the UE by the CU, and the DU UE AP ID allocated for the UE by the DU.
  • the DU receives a downlink non-access stratum (NAS) transfer message which is sent from an access and mobility management function (AMF) from the CU through the control plane or the user plane tunnel, and forwards the downlink NAS transfer message to the UE; and
  • NAS non-access stratum
  • AMF access and mobility management function
  • the DU receives a radio bearer reconfiguration request message from the CU, in which the radio bearer reconfiguration request message includes one or more pieces of the following information: a CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the DU, information of an RB to be added, information of an RB to be reconfigured, and information of an RB to be deleted; the DU allocates a resource, and sends a radio bearer reconfiguration response message to the CU, wherein the radio bearer reconfiguration response message comprises one or more pieces of the following information: the CU UE AP ID allocated for the UE by the CU, the DU UE AP ID allocated for the UE by the DU, configuration information of an RB; the DU receives an RRC connection reconfiguration message from the CU, and sends the RRC connection reconfiguration message to the UE; and the DU sends an RRC connection reconfiguration completion message which is sent from
  • an RRC message between the DU and the CU is transmitted through the control plane, or an RRC message on a signaling radio bearer SRB0 is transmitted through the control plane, and RRC messages on the other SRBs are transmitted through the user plane;
  • the DU and the CU establishes a user plane tunnel for transmitting the RRC message through the following three approaches:
  • the DU allocates downlink tunnel information, sends the allocated downlink tunnel information to the CU through the initial UE message transfer message, and after the CU allocates uplink tunnel information, the CU sends the allocated uplink tunnel information to the DU through a radio bearer configuration message; in which the downlink tunnel information and the uplink tunnel information includes a tunnel endpoint identifier (TEID), and/or a transport layer address;
  • TEID tunnel endpoint identifier
  • the DU allocates the downlink tunnel information, and sends the allocated downlink tunnel information to the CU through the initial UE message transfer message, and after the DU sends the radio bearer configuration response message to the CU, the CU allocates the uplink tunnel information, and sends the uplink tunnel information allocated to the DU through the downlink RRC transfer message; in which the downlink tunnel information and the uplink tunnel information includes the TEID, and/or the transport layer address;
  • the RRC messages on the other SRBs are transmitted through a same user plane tunnel, or a user plane tunnel is established for each SRB, and the RRC messages on the other SRBs are transmitted through user plane tunnels separately, and accordingly, the allocated uplink tunnel information or the downlink tunnel information corresponds to each SRB.
  • the information of the RB to be added includes one or more pieces of the following information: an RB identity of the RB, configuration information of a physical channel of the RB, configuration information of a transport channel of the RB, configuration information of a logic channel of the RB, information of a QoS flow or Qos flows mapped on the RB and/or uplink tunnel information of the RB; and the information of the QoS flow mapped on the RB includes an identity of the QoS flow and QoS information of the QoS flow; and/or
  • the uplink tunnel information includes a transport layer address and an uplink TEID;
  • the information of the RB to be reconfigured includes one or more pieces of the following information: an identity of the RB, reconfiguration information of a physical channel of the RB, reconfiguration information of a transport channel of the RB, reconfiguration information of a logic channel of the RB, information of a QoS flow or Qos flows to be added to the RB, and information of a QoS flow or Qos flows to be deleted from the RB and/ information of a QoS flow or Qos flows to be transmitted on the RB.
  • the information of the QoS flow to be added includes an identity of the QoS flow and QoS parameters to be reconfigured; and the information of the QoS flow to be deleted from the RB includes an identity of the QoS flow.
  • the present disclosure further provides a method for performing access for a UE, including:
  • the radio bearer configuration request message includes one or more pieces of the following information: a CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the DU, a cell identity of a cell where the UE is located, information of an RB to be configured, configuration information of a physical channel, configuration information of a transport channel, configuration information of a logic channel, and uplink tunnel information;
  • NAS downlink non-access stratum
  • AMF access and mobility management function
  • the radio bearer reconfiguration request message includes one or more pieces of the following information: a CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the DU, information of an RB to be added, information of an RB to be reconfigured, and information of an RB to be deleted; receiving a radio bearer reconfiguration response message from the DU, in which the radio bearer reconfiguration response message includes one or more pieces of the following information: the CU UE AP ID allocated for the UE by the CU, the DU UE AP ID allocated for the UE by the DU, configuration information of an RB; sending an RRC connection reconfiguration message to the DU, and receiving an RRC connection reconfiguration completion message which is sent from the UE and forwarded by the DU.
  • the present disclosure further provides a DU apparatus for performing access for a UE, including: a receiving unit, a sending unit, and a processing unit; in which
  • the receiving unit is configured to receive an RRC connection request message from the UE;
  • the sending unit is configured to send the RRC connection request message to the CU through a user plane tunnel or control plane between the DU and the CU;
  • the processing unit is configured to receive a radio bearer configuration request message from the CU, configure a resource according to the received radio bearer configuration request message, receive an RRC connection establishment message sent from the CU through the user plane tunnel or the control plane, and forward the RRC connection establishment message to the UE; receive an RRC connection establishment completion message from the UE, send the received RRC connection establishment completion message to the CU through the control plane or the user plane tunnel, and encapsulate an identity of the UE in a header of a data packet transmitted through the corresponding user plane tunnel or the control plane; and in case of not necessary to establish a session, receive RRC message downlink NAS transfer message sent from the CU according to an NAS transfer message of an AMF through the control plane or the user plane tunnel, and forward the RRC message downlink NAS transfer message to the UE;
  • the radio bearer configuration request message includes one or more pieces of the following information: a CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the DU, a cell identity of a cell where the UE is located, information of an RB to be configured, configuration information of a physical channel, configuration information of a transport channel, configuration information of a logic channel, and uplink tunnel information.
  • the present disclosure further provides a CU apparatus for performing access for a UE, including: a receiving unit, a sending unit, and a processing unit;
  • the receiving unit is configured to receive an RRC connection request message which is forwarded from the UE by a DU, through a user plane tunnel or control plane between the CU and the DU;
  • the sending unit is configured to send a radio bearer configuration request message to the DU; in which the radio bearer configuration request message includes one or more pieces of the following information: a CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the DU, a cell identity of a cell where the UE is located, information of an RB to be configured, configuration information of a physical channel, configuration information of a transport channel, configuration information of a logic channel, and uplink tunnel information;
  • the processing unit is configured to send an RRC connection establishment message to the DU through the user plane tunnel or the control plane between the CU and the DU, and receive an RRC connection establishment completion message forwarded by the DU from the UE, through the user plane tunnel or the control plane between the CU and the DU, encapsulate an identity of the UE in a header of a data packet of the user plane tunnel or the control plane that bears the RRC connection establishment completion message; and in case of not necessary to establish a session, receive a downlink NAS transfer message sent from an AMF, and send an RRC message downlink NAS transfer message to the DU through the control plane or the user plane tunnel.
  • the present disclosure further provides a method for performing a handover for a UE, in which a source DU and a target DU of the handover access to a same CU, and the method includes:
  • a measurement report message which is sent from the UE to a base station, through a user plane tunnel or control plane between the CU and the source DU;
  • the radio bearer configuration message includes one or more pieces of the following information: a CU UE AP ID allocated for the UE by the CU, context information of the UE on the source DU, a target cell identity, information of an RB to be configured, configuration information of a physical channel, configuration information of a transport channel, configuration information of a logic channel, uplink tunnel information, and an indication of MBB handover;
  • the radio bearer configuration response message includes one or more pieces of the following information: the CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the target DU, and RB information configured for the UE;
  • an RRC message between the DU and the CU is transmitted through the control plane, or an RRC message on a SRB0 is transmitted through the control plane, and RRC messages on the other SRBs are transmitted through the user plane.
  • the RRC messages on the other SRBs are transmitted through a same user plane tunnel, or for each SRB, a user plane tunnel is established, and the RRC messages on the other SRBs are transmitted through user plane tunnels separately, and accordingly, the allocated uplink tunnel information or the downlink tunnel information corresponds to each SRB; and/or
  • the radio bearer configuration message includes uplink tunnel information allocated by the CU; and corresponding to the approach, in which the RRC messages on the other SRBs other than the SRB0 are transmitted through the user plane, the radio bearer configuration message includes uplink tunnel information allocated for the SRBs by the CU, and the uplink tunnel information is a channel commonly used for transmitting RRC messages on all SRBs or on the SRBs other than the SRB0; and the uplink tunnel information includes a transport layer address and a TEID; and/or
  • the RB information configured for the UE includes SRB and DRB configuration information; corresponding to each DRB, the radio bearer configuration message includes downlink tunnel information allocated for the SRBs by the T-DU; corresponding to the approach, in which the RRC messages on the other SRBs other than the SRB0 are transmitted through the user plane, the radio bearer configuration message includes downlink tunnel information allocated for the SRBs by the T-DU, and the downlink tunnel information corresponds to each SRB, or is a channel commonly used for transmitting the RRC messages on SRBs except for that on the SRB0; and the downlink tunnel information comprises the transport layer address and the TEID.
  • the sending, by the CU, information of performing the handover between different DUs and/or an indication of performing MBB to the source DU includes: sending, by the CU, the information of performing the handover between different DUs and/or the indication of performing MBB to the source DU through an F1AP message, or encapsulating the information of performing the handover between different DUs and/or the indication of performing MBB in a header of a data packet of the user plane tunnel that bears the RRC connection reconfiguration message, and sending it to the source DU.
  • the header of the data packet also includes the CU UE AP ID allocated for the UE by the CU, the DU UE AP ID allocated for the UE by the S-DU and/or logic channel information that is used to send the RRC connection reconfiguration message.
  • the method includes: deciding, by the CU, a time to stop transmitting downlink data or stop communicating with the UE, and notifies the time to the source DU.
  • the transmitting, by the CU, data to the target DU includes:
  • the CU transmits the data that has not been acknowledged by the UE and that is received from the UPF to the target DU, in which the data is the PDCP PDUs, and the source DU sends RLC context at the source DU to the target DU; corresponding to PDCP PDUs, only a part of which is transmitted successfully, the target DU only transmits an RLC PDU that has not been received by the UE to the UE; and the CU receives a first RLC context transfer message from the source DU; and the CU sends a second RLC context transfer message to the target DU; and
  • the first RLC context transfer message and the second RLC context transfer message include: the CU UE AP ID allocated for the UE by the CU, the DU UE AP ID allocated for the UE by the source DU, RLC sending status and/or a PDCP sending and receiving status; wherein the RLC sending status includes a sequence number (SN) of a last GTP-U data packet that has been successfully transmitted, and an SN of a GTP-U data packet that has not been successfully transmitted and/or an RLC SN that has not been sent successfully.
  • SN sequence number
  • a method for performing a handover for a UE in which a source DU and a target DU of the handover access to a same CU, and the method includes:
  • the source DU receiving, by the source DU, a measurement report message from the UE, in which the source DU sends the measurement report message to the CU through a user plane tunnel or control plane between the source DU and the CU;
  • the present disclosure further provides a CU apparatus for performing a handover for a UE, and the CU apparatus includes: a sending unit, a processing unit, and a receiving unit;
  • the receiving unit is configured to receive a measurement report message which is sent from the UE to a base station, through a user plane tunnel or control plane between the CU and the source DU;
  • the processing unit is configured to send a radio bearer configuration message to the target DU, after determining to perform the handover for the UE; receive a radio bearer configuration response message from the target DU; send an RRC connection reconfiguration message to the source DU through the user plane tunnel or the control plane, and sending information of performing the handover between different DUs and/or an indication of performing MBB to the source DU; transmitting data to the target DU, and after the UE being synchronized to a target cell, receiving an RRC connection establishment completion message sent from the target DU through the user plane tunnel or the control plane; in which the RRC connection establishment completion message is sent from the UE to the base station; and
  • the sending unit is configured to send a UE context releasing message to the source DU;
  • the radio bearer configuration message includes one or more pieces of the following information: a CU UE AP ID allocated for the UE by the CU, context information of the UE on the source DU, a target cell identity, information of an RB to be configured, configuration information of a physical channel, configuration information of a transport channel, configuration information of a logic channel, uplink tunnel information, and an indication of MBB handover; and the radio bearer configuration response message includes one or more pieces of the following information: the CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the target DU, and RB information configured for the UE.
  • the present disclosure further provides a source apparatus for performing a handover for a UE, and the apparatus includes: a first processing unit, a second processing unit and a third processing unit;
  • the first processing unit is configured to receive a measurement report message from the UE, and send the measurement report message to the CU through a user plane tunnel or control plane between the CU and the DU;
  • the second processing unit is configured to receive an RRC connection reconfiguration message from the CU through the user plane tunnel or the control plane, and receive information of performing the handover between different DUs and/or an indication of performing MBB to the source DU;
  • the third processing unit is configured to receive a UE context releasing message from the CU.
  • the present disclosure further provides a target DU apparatus for performing a handover for a UE, including: a first processing unit, a second processing unit and a third processing unit;
  • the first processing unit is configured to receive a radio bearer configuration message sent from a CU in a base station;
  • the radio bearer configuration message includes one or more pieces of the following information: a CU UE AP ID allocated for the UE by the CU, context information of the UE on the source DU, a target cell identity, information of an RB to be configured, configuration information of a physical channel, configuration information of a transport channel, configuration information of a logic channel, uplink tunnel information, and an indication of MBB handover;
  • the second processing unit is configured to send a radio bearer configuration response message to the CU;
  • the radio bearer configuration response message includes one or more pieces of the following information: the CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the target DU, and RB information configured for the UE;
  • the third processing unit is configured to receive data transmitted from the CU, and after the UE being synchronized to a target cell, receive an RRC connection establishment completion message sent from the UE, and forward the RRC connection establishment completion message to the CU through a user plane tunnel between the CU and the target DU.
  • a method for performing access for a UE in which the access of the UE is performed by a DU-1 and a DU-2, and the DU-1 and the DU-2 access to a same CU, and the method includes:
  • a measurement report message which is sent from the UE to a base station, through a user plane tunnel or control plane between the CU and the source DU;
  • the radio bearer configuration message includes one or more pieces of the following information: a CU UE AP ID allocated for the UE by the CU, context information of the UE on the source DU, a target cell identity, information of an RB to be configured, configuration information of a physical channel, configuration information of a transport channel, configuration information of a logic channel, uplink tunnel information, and an indication of MBB handover; in which corresponding to each DRB, the radio bearer configuration message includes uplink tunnel information allocated by the CU; and the uplink tunnel information includes a transport layer address and a TEID;
  • the radio bearer configuration response message includes one or more pieces of the following information: the CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the target DU, and RB information configured for the UE;
  • an RRC connection reconfiguration message to the source DU through the user plane tunnel or the control plane, and sending one or more pieces of the following information to the source DU: the CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated by the DU-1, the RRC connection reconfiguration, information of a logic channel for transmitting RRC messages, information of an RB to be switched, and the indication of MBB handover;
  • the present disclosure further provides a CU apparatus for performing access for a UE, and the CU apparatus includes: a receiving unit, a processing unit, and a sending unit;
  • the receiving unit is configured to receive a measurement report message which is sent from the UE to a base station, through a user plane tunnel or control plane between the CU and a source DU;
  • the processing unit is configured to send a radio bearer configuration message to a target DU through the sending unit, after determining to switch a part of DRBs or all DRBs of the UE to the target DU; in which the radio bearer configuration message includes one or more pieces of the following information: a CU UE AP ID allocated for the UE by the CU, context information of the UE on the source DU, a target cell identity, information of an RB to be configured, configuration information of a physical channel, configuration information of a transport channel, configuration information of a logic channel, uplink tunnel information, and an indication of MBB handover; in which corresponding to each DRB, the radio bearer configuration message includes uplink tunnel information allocated by the CU; and the uplink tunnel information includes a transport layer address and a TEID;
  • the receiving unit is configured to receive a radio bearer configuration response message from the target DU;
  • the radio bearer configuration response message includes one or more pieces of the following information: the CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the target DU, and RB information configured for the UE;
  • the sending unit is further configured to send an RRC connection reconfiguration message to the source DU through the user plane tunnel or the control plane, to send one or more pieces of the following information to the source DU: the CU UE AP ID allocated for the UE by the CU, a DU UE AP ID allocated for the UE by the DU-1, RRC connection reconfiguration, information of a logic channel for transmitting RRC messages, information of an RB to be switched, and the indication of MBB handover;
  • the sending unit is further configured to transmit data to the target DU, and after the UE being synchronized to a target cell, receive an RRC connection establishment completion message sent from the target DU through the user plane tunnel or the control plane; in which the RRC connection establishment completion message is sent from the UE to the base station; and send a UE context releasing message to the source DU;
  • the operator needs to perform less configurations, and the intercommunication between the DU and the CU can be guaranteed.
  • the handover methods and the access methods for the UE on the F1 interface provided according to the present disclosure can guarantee that the DU and the CU can support interconnection and intercommunication of devices of different manufacturers.
  • the present disclosure provides a data forwarding method, user equipment and base station, by which a UE may forward data between a base station and other UEs.
  • the present disclosure discloses a data forwarding method, including:
  • the method further includes the following steps performed by the first UE: receiving, from the base station, scheduling information by which the base station scheduled time-frequency resources of the second UE; and
  • the forwarding, by the first UE, data between the base station and the second UE includes the following steps performed by the first UE: receiving downlink data sent to the second UE from the base station, processing the downlink data layer by layer by a protocol stack structure corresponding to the first UE in the enhanced mode, and forwarding the downlink data to the second UE on the corresponding time-frequency resources according to the scheduling information on the time-frequency resources of the second UE; and/or receiving uplink data sent to the base station from the second UE on corresponding time-frequency resources according to the scheduling information on the time-frequency resources of the second UE, processing the uplink data layer by layer by the corresponding protocol stack structure in the enhanced mode of the first UE, and forwarding the uplink data to the base station.
  • the method further includes: transmitting, by the first UE, a scheduling information on time-frequency resources to the second UE; and wherein
  • the forwarding, by the first UE, data between the base station and the second UE includes the following steps performed by the first UE: receiving downlink data sent to the second UE from the base station, processing the downlink data layer by layer by a protocol stack structure corresponding to the first UE in the enhanced mode, and forwarding, to the second UE, the downlink data on a corresponding time-frequency resources according to the scheduling information; and/or receiving uplink data sent to the base station from the second UE on the corresponding time-frequency resources according to the scheduling information, processing the uplink data layer by layer by the corresponding protocol stack structure in the enhanced mode, and forwarding the uplink data to the base station.
  • the method further includes the following steps performed by the first UE:
  • the access information is used by the second UE to access the UE;
  • the method further includes: reporting, by the first UE to the base station, channel state information of a first link, the first link being a link between the first UE and the base station, and the channel state information being used by the base station to select the first UE having a channel condition better than a first set threshold to enter the enhanced mode in order to forward data between the second UE having a channel condition worse than a second set threshold and the base station.
  • the information reported by the first UE to the base station further includes channel state information on at least one carrier between the first UE and the second UE.
  • an indication to enter an enhanced mode from the base station further includes:
  • the protocol stack structure supported by the first UE in the enhanced mode at least including one of the following structures:
  • protocol stack structure B0 including: a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer and a physical (PHY) layer in a control plane, and a Service Data Adaptation Protocol (SDAP) layer, a PDCP layer, an RLC layer, an MAC layer and a PHY layer in a user plane;
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • PHY physical
  • SDAP Service Data Adaptation Protocol
  • protocol stack structure B1 including: a PDCP layer, an RLC layer, an MAC layer and a PHY layer;
  • protocol stack structure B2 including: part of a PDCP layer, an RLC layer, an MAC layer and a PHY layer;
  • protocol stack structure B3 including: an RLC layer, an MAC layer and a PHY layer;
  • protocol stack structure B4 including: part of an RLC layer, an MAC layer and a PHY layer;
  • protocol stack structure B5 including: an MAC layer and a PHY layer;
  • protocol stack structure B6 including: part of an MAC layer and a PHY layer;
  • protocol stack structure B7 including: a PHY layer;
  • protocol stack structure B8 including: part of a PHY layer.
  • the indication from the base station includes at least one of the following information:
  • the information indicated by the base station includes the following combinations:
  • the indication from the base station includes at least one of the following information: a duplex mode used by a second link, a carrier and a bandwidth used by the second link, a physical cell ID of a cell where the second link is located, a maximum transmission power of the first UE in the second link, and an operating mode of the second link; and
  • the second link is a link between the first UE and the second UE.
  • the method before the forwarding, by the first UE, data between the base station and the second UE, the method further includes: receiving, by the first UE from the base station, configuration information related to forwarding of data of the second UE, the configuration information being used to indicate data to be forwarded; and
  • the forwarding, by the first UE, data between the base station and the second UE includes: determining, by the first UE according to the configuration information related to forwarding of data of the second UE, data to be forwarded between the base station and the second UE.
  • the configuration information related to forwarding of data of the second UE at least includes one of the following information:
  • the present disclosure further discloses a user equipment, including:
  • a mode switching module configured to enter an enhanced mode according to an indication received from a base station
  • a data forwarding module configured to forward data between the base station and a second UE.
  • the present disclosure discloses a data forwarding method, including:
  • the method further includes: transmitting, to the first UE, scheduling information on time-frequency resources of the second UE scheduled by a base station.
  • the method further includes:
  • the method further includes: receiving channel state information of a first link reported by the first UE; and
  • the transmitting, to the first UE having the capability of supporting the enhanced mode, the indication to enter the enhanced mode includes: selecting, according to channel state information of a first link reported by each UE, the first UE having a channel condition better than a first set threshold, and transmitting, to the first UE having the channel condition better than the first set threshold, an indication to enter the enhanced mode in order to forward data between the second UE having a channel condition worse than a second set threshold and the base station.
  • the indication from the base station includes at least one of the following information:
  • the method further includes:
  • the configuration information related to forwarding of data of the second UE at least includes one of the following information:
  • the present disclosure further discloses a base station, including:
  • an indicating module configured to transmit, to a first UE having the capability of supporting an enhanced mode, an indication to enter the enhanced mode
  • a forward processing module configured to forward data of a second UE by the first UE.
  • a UE enters an enhanced mode according to an indication from a base station, and then the UE forwards data between the base station and other UEs, thus achieving forwarding of data of other UEs by the UE.
  • the UE may be well solved by the method of the present disclosure. Therefore, the user experience is improved.
  • FIG.1 is a schematic diagram of system architecture in a 5G network or communication system
  • FIG.2 is a schematic diagram of another system architecture in a 5G network or communication system
  • FIG.3 is a schematic diagram of a first method of establishing a fronthaul interface according to the present disclosure
  • FIG.4 is a schematic diagram of a second method of establishing a fronthaul interface according to the present disclosure.
  • FIG.5 is a schematic diagram of a third method of establishing a fronthaul interface according to the present disclosure.
  • FIG.6 is a schematic diagram of a method for performing access for a UE according to the present disclosure.
  • FIG.7 is a schematic diagram of a method for performing a handover between different DUs of a same CU for a UE;
  • FIG.8 is a schematic diagram of a method for performing access for a UE through different DUs of a same CU
  • FIG. 1 is a schematic diagram of the system architecture in a 5G communication system.
  • FIG.9 is a schematic diagram of a preferred data forwarding method according to the present disclosure.
  • FIG.10 is a schematic diagram of a protocol stack structure B0 for a UE according to the present disclosure.
  • FIG.11 is a schematic diagram of a protocol stack structure B1 for a UE according to the present disclosure.
  • FIG.12 is a schematic diagram of a protocol stack structure B2 for a UE according to the present disclosure.
  • FIG.13 is a schematic diagram of a protocol stack structure B3 for a UE according to the present disclosure.
  • FIG.14 is a schematic diagram of a protocol stack structure B4 for a UE according to the present disclosure.
  • FIG.15 is a schematic diagram of a protocol stack structure B5 for a UE according to the present disclosure.
  • FIG.16 is a schematic diagram of a protocol stack structure B6 for a UE according to the present disclosure.
  • FIG.17 is a schematic diagram of a protocol stack structure B7 for a UE according to the present disclosure.
  • FIG.18 is a schematic diagram of a protocol stack structure B8 for a UE according to the present disclosure.
  • FIG.19 is a schematic diagram of Embodiment 7 of the present disclosure.
  • FIG.20 is a schematic diagram of Embodiment 9 of the present disclosure.
  • FIG.21 is a schematic diagram of Embodiment 10 of the present disclosure.
  • FIG.22 is a schematic diagram of Embodiment 11 of the present disclosure.
  • FIG. 23 is a illustrates a block diagram of a structure of a terminal according to embodiments of the present disclosure.
  • FIG. 24 illustrates a block diagram of a structure of a base station according to embodiments of the present disclosure.
  • the present disclosure provides three methods for establishing a fronthaul interface between a DU and a CU, and meanwhile provides methods for performing access for a UE and methods for performing a handover for a UE after establishing a fronthaul interface. The respective methods will be described in detail in the following.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • a first method for establishing a fronthaul interface is as shown in Fig.3.
  • it is a DU that initiates an F1 interface establishment procedure.
  • the method may be applicable to a situation where an O&M has an interface with a CU and with the DU, or where the O&M only has an interface with the DU.
  • the method for establishing a fronthaul interface includes processing at the DU side and at the CU side, and for description purpose, the establishing method is described through interactions between the DU and the CU, and the establishing method includes the following steps:
  • Step 201 a DU sends an F1 establishment request message to a CU.
  • An operation and maintenance system configures a transport layer address of the CU to be connected by the DU to the DU.
  • the O&M also configures application layer information of the DU to the DU.
  • the F1 establishment request message may include one or more pieces of the following information:
  • the serving cell information includes: a cell identity, cell frequency information, uplink transmission bandwidth information, downlink transmission bandwidth information, a physical cell identity, a tracking area identity (TAI) or a tracking area code (TAC), a list of broadcast public land mobile network (PLMN) identities, transmission reception point (TRP) information, beam information, information of a physical channel in the cell, information of a transport channel in the cell, information of a logic channel in the cell and/or a cell access layer protocol (AP) identity used for the F1 interface and allocated by the DU.
  • the cell identity may be a global cell identity or a cell identity unique on the DU, or other cell identities received from the O&M.
  • the cell AP identity allocated by the DU is configured to establish a cell signaling connection for the F1 interface, used to transmit information related to the cell.
  • the serving cell information also includes clock information, e.g., a system frame number (SFN).
  • SFN system frame number
  • the DU capability information includes DU buffer capability, DU capacity information, antenna capability, power capability, and/or DU fronthaul interface capability.
  • Step 202 the CU receives an F1 establishment request message.
  • the CU stores the received information, and sends an F1 establishment response message to the DU.
  • the CU uses the DU capability information to schedule the UE, e.g., deciding a DU for serving the UE, or deciding load balance between different DUs.
  • the F1 establishment response message may include one or more pieces of the following information:
  • the CU identity may be an identity of a gNB or may be a separate CU identity.
  • Configuration information of a cell in the cell configuration list includes: a cell identity, configuration information of a common channel in the cell, system information in the cell, scheduling information for sending the system information and/or a cell AP identity for an F1 interface allocated by the CU.
  • the cell identity may be a global cell identity or a cell identity unique on the DU or a cell identity unique on the CU.
  • the configuration information of the common channel includes configuration information of a physical channel, configuration information of a transport channel, and configuration information of a logic channel.
  • the system information includes master information blocks (MIBs) and system information blocks. The CU decides the scheduling information of the system information according to clock information of the cell received from the DU.
  • MIBs master information blocks
  • the CU includes the clock information of the cell (e.g., an SFN) received from the DU in the system information.
  • the cell AP identity allocated by the CU is used to establish a cell signaling connection for the F1 interface, used to transmit information related to the cell.
  • the F1 establishment response message includes the cell configuration list, then it means that the establishment of the cell is completed through the F1 establishment procedure.
  • the F1 establishment response message includes the cell configuration list
  • the cell configuration list includes the system information in the cell and the scheduling information for sending the system information, which equals to sending the system information that needs to be broadcasted in the cell to the DU, so that the DU can work rapidly.
  • the cell establishment procedure may be an independent procedure, and in this case, the F1 establishment response message does not contain the cell configuration list. Corresponding to this method, the following steps are further included:
  • Step 203 the CU sends a cell establishment request message to the DU.
  • the cell establishment request message contains information of a cell to be configured.
  • the information of the cell to be configured may be the same with the cell configuration information in the step 202, which will not be elaborated herein.
  • Step 204 the DU sends a cell establishment response message to the CU.
  • the cell establishment procedure may be used to configure one cell or multiple cells.
  • the messages in the step 203 and the step 204 are sent through the cell signaling connection, i.e., the cell establishment request message and the cell establishment response message containing a cell AP identity allocated by the DU and a cell AP identity allocated by the CU, and in this case, the cell establishment request message and the cell establishment response message may not need to contain the cell identity.
  • the system information needs to be broadcasted in the cell is sent to the DU, so that the DU can send system information as soon as possible after the cell is configured successfully.
  • the system information may be sent through an independent procedure.
  • the present method further includes the following step:
  • Step 205 the CU sends a system information transfer message to the DU.
  • the system information transfer message includes a cell identity, system information in the cell, and scheduling information for sending the system information.
  • the CU determines the scheduling information of the system information according to the clock information of the cell received from the DU.
  • the CU includes the clock information of the cell, e.g., an SFN, received from the DU in the system information.
  • the system information transfer procedure may be used to transmit system information of one or more cells. If system information of one cell is transmitted, the message in the step 205 is transmitted through the cell signaling connection, i.e., the system information transfer message contains a cell AP identity allocated by the DU and a cell AP identity allocated by the CU, and in this case, the system information transfer message may not need to contain the cell identity.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • a second method for establishing a fronthaul interface is as shown in Fig.4.
  • the method is a CU that initiates an F1 interface establishment procedure.
  • the method may be applicable to a situation where an O&M has an interface with the CU and with a DU, or where the O&M only has an interface with the CU.
  • the method for establishing a fronthaul interface includes processing at the DU side and at the CU side, and for description purpose, the establishing method is described through interactions between the DU and the CU, and the establishing method includes the following steps:
  • Step 301 a CU sends an F1 establishment request message to a DU.
  • An O&M configures a transport layer address of the DU to be connected by the CU to the CU.
  • the O&M configures the application layer information on the CU to the CU. If the O&M only has an interface with the CU, then the O&M also configures application layer information of each DU to be connected by the CU to the CU.
  • the F1 establishment request message may include one or more pieces of the following information:
  • the CU identity may be an identity of a gNB or may be a separate CU identity.
  • the serving cell information includes: a cell identity, cell frequency information, uplink transfer bandwidth information, downlink transfer bandwidth information, a physical cell identity, a TAI or a TAC, a list of broadcasted PLMN identities, TRP information, beam information, information of a physical channel in the cell, information of a transport channel in the cell, information of a logic channel in the cell and/or a cell access layer AP identity used for the F1 interface allocated by the DU.
  • the cell identity may be a global cell identity or a cell identity unique on the DU, or other cell identities received from the O&M.
  • the cell AP identity allocated by the DU is configured to establish a cell signaling connection for the F1 interface, used to transmit information related to the cell.
  • the serving cell information also includes clock information, e.g., an SFN. It is to be specified that, when the O&M only has an interface with the CU, the clock information is needed, and the O&M configures the configuration information of the DU to the CU, and sends the configuration information of the DU to a corresponding DU through the CU.
  • Configuration information of a cell in the cell configuration list includes: a cell identity, configuration information of a common channel in the cell, system information in the cell, scheduling information for sending the system information and/or a cell AP identity for an F1 interface allocated by the CU.
  • the cell identity may be a global cell identity or a cell identity unique on the DU or a cell identity unique on the CU.
  • the configuration information of the common channel includes configuration information of a physical channel, configuration information of a transport channel, and configuration information of a logic channel.
  • the system information includes master information blocks (MIBs) and system information blocks. The CU decides the scheduling information of the system information according to clock information of the DU cell.
  • MIBs master information blocks
  • the CU includes the clock information (e.g., an SFN) of the DU cell in the system information.
  • the cell AP identity allocated by the CU is used to establish a cell signaling connection for the F1 interface, used to transmit information related to the transfer cell.
  • the F1 establishment request message includes the cell configuration list, then it means that the establishment of the cell is completed during the F1 establishment procedure.
  • Step 302 the DU receives an F1 establishment request message.
  • the DU stores the F1 establishment request message received. If the DU receives cell configuration information, the DU configures a corresponding cell.
  • the DU sends an F1 establishment response message to the CU.
  • the F1 establishment response message may contain one or more of the following information:
  • the DU capability information includes DU cache capability, DU capacity information, antenna capability, power information and/or fronthaul interface capability.
  • the cell configuration information is actually configuration information configured by the DU for the cell, which may be different from the F1 establishment request message in case of receiving by the CU.
  • the CU stores the information received. If the CU receives the DU capability information, the CU uses the DU capability information to schedule the UE, for example, deciding a UE for serving the UE, or deciding load balance between different UEs. The CU sends an F1 establishment response message to the DU.
  • the F1 establishment request message includes the cell configuration list
  • the cell configuration list includes the system information in the cell and the scheduling information for sending the system information, which equals to sending the system information that needs to be broadcasted in the cell to the DU, so that the DU can work rapidly.
  • the cell establishment procedure may be an independent procedure, and in this case, the F1 establishment request message does not contain the cell configuration list. Corresponding to this method, the following steps are further included:
  • Step 303 the CU sends a cell establishment request message to the DU.
  • the cell establishment request message contains information of a cell to be configured.
  • the information of the cell to be configured is the same with the cell configuration information in the step 301, and will not be elaborated herein.
  • Step 304 the DU sends a cell establishment response message to the CU.
  • the system information needs to be broadcasted in the cell is sent to the DU, so that the DU can send system information as soon as possible after the cell is configured successfully.
  • the system information may be sent through an independent procedure.
  • the present method further includes the following steps:
  • Step 305 the CU sends a system information transfer message to the DU.
  • the system information transfer message includes a cell identity, system information in the cell, and scheduling information for sending the system information.
  • the CU determines the scheduling information of the system information according to the clock information of the DU cell.
  • the CU includes the clock information of the DU cell, e.g., an SFN, in the system information.
  • the cell establishment procedure may be used to configure one cell or multiple cells. If it is used to configure one cell, the messages in the step 303 and the step 304 are sent through the cell signaling connection, i.e., the system information transfer message containing a cell AP identity allocated by the DU and a cell AP identity allocated by the CU, and in this case, the system information transfer message may not need to contain the cell identity.
  • the system information transfer procedure may be used to send system information of one or more cells. If system information of one cell is sent, the message in the step 305 is transmitted through the cell signaling connection, i.e., the system information transfer message containing the cell AP identity allocated by the DU and the cell AP identity allocated by the CU, and in this case, the system information transfer message may not need to contain the cell identity.
  • a third method for establishing a fronthaul interface is as shown in Fig.5.
  • the method is a CU that triggers an F1 interface establishment procedure.
  • the method may be applicable to a situation where an O&M has an interface with the CU and with a DU, or where the O&M only has an interface with the CU.
  • the method for establishing a fronthaul interface includes processing at the DU side and at the CU side, and for description purpose, the establishing method is described through interactions between the DU and the CU, and the establishing method includes the following steps:
  • Step 401 the CU sends an F1 establishment required message to the DU.
  • An O&M configures a transport layer address of the DU to be connected by the CU to the CU.
  • the O&M configures application layer information of the CU to the CU. If the O&M only has an interface with the CU, the O&M also configures application layer information of each DU to be connected by the CU to the CU.
  • the F1 establishment required message may include one or more pieces of the following information:
  • the CU identity may be a gNB identity or a separate CU identity.
  • the serving cell information includes: a cell identity, cell frequency information, uplink transfer bandwidth information, downlink transfer bandwidth information, a physical cell identity, a TAI or a TAC, a list of broadcast PLMN identities, TRP information, beam information, information of a physical channel in the cell, information of a transport channel in the cell, information of a logic channel in the cell and/or a cell access layer AP identifier used for the F1 interface and allocated by the DU.
  • the cell identifier may be a global cell identity or a cell identity unique on the DU or a unique cell identity received from the O&M.
  • the cell AP identifier allocated by the DU is used to establish a cell signaling connection for the F1 interface, used to transmit information related to the cell.
  • the serving cell information may also include clock information, such as a system frame number (SFN). It is to be specified that, when the O&M only has an interface with the CU, the clock information is contained, and the O&M configures the configuration information of the DU to the CU, and passes the configuration information of the DU to the corresponding DU through the CU.
  • SFN system frame number
  • Step 402 the DU sends an F1 establishment request message to the CU.
  • the DU is configured with the application layer information on the DU through the O&M or the DU contains the application layer information on the DU through the CU.
  • the F1 establishment request message may include one or more pieces of the following information:
  • the serving cell information includes: a cell identity, cell frequency information, uplink transfer bandwidth information, downlink transfer bandwidth information, a physical cell identity, a TAI or a TAC, a list of broadcasted PLMN identities, TRP information, beam information, information of a physical channel in the cell, information of a transport channel in the cell, information of a logic channel in the cell and/or a cell access layer AP identity used for the F1 interface allocated by the DU.
  • the cell identity may be a global cell identity or a cell identity unique on the DU, or other cell identities received from the O&M.
  • the cell AP identity allocated by the DU is configured to establish a cell signaling connection for the F1 interface, used to transmit information related to the cell.
  • the serving cell information also includes clock information, e.g., an SFN.
  • the serving cell information list on the DU does not need to be contained.
  • the DU capability information includes DU buffer capability, DU capacity information, antenna capability, power information and/or DU fronthaul interface capability.
  • Step 403 the CU receives an F1 establishment request message.
  • the CU stores the received information. If the CU receives the DU capability information, the CU uses the DU capability information to schedule the UE, e.g., deciding a DU for serving the UE or deciding load balance between different DUs.
  • the CU sends an F1 establishment response message to the DU.
  • the F1 establishment response message may include one or more pieces of the following information:
  • Configuration information of a cell in the cell configuration list includes: a cell identity, configuration information of a common channel in the cell, system information in the cell, scheduling information for sending the system information and/or a cell AP identity for an F1 interface allocated by the CU.
  • the cell identity may be a global cell identity or a cell identity unique on the DU or a cell identity unique on the CU.
  • the configuration information of the common channel includes configuration information of a physical channel, configuration information of a transport channel, and configuration information of a logic channel.
  • the system information includes master information blocks (MIBs) and system information blocks. The CU decides the scheduling information of the system information according to clock information of the DU cell.
  • MIBs master information blocks
  • the CU includes the clock information of the DU cell (e.g., an SFN) in the system information.
  • the cell AP identity allocated by the CU is used to establish a cell signaling connection for the F1 interface, used to transmit information related to the cell.
  • the F1 establishment response message includes the cell configuration list, then it means that the establishment of the cell is completed during the F1 establishment procedure.
  • the F1 establishment response message includes the cell configuration list
  • the cell configuration list includes the system information in the cell and the scheduling information for sending the system information, which equals to sending the system information that needs to be broadcasted in the cell to the DU, so that the DU can work rapidly.
  • the cell establishment procedure may be an independent procedure, and in this case, the F1 establishment response message does not contain the cell configuration list. A detailed procedure is the same as that in steps 203 and 204, and will not be elaborated herein.
  • the system information needs to be broadcasted in the cell is sent to the DU, so that the DU can send system information as soon as possible after the cell is configured successfully.
  • the system information may be sent through an independent procedure.
  • a detailed step is the same as the step 205, and will not be elaborated herein.
  • the DU When the application layer information of the DU, e.g., the capability information or clock information of the DU, is updated, the DU sends a DU configuration updating message to the CU to notify the CU of the updated application layer information.
  • the CU stores the received updated application layer information.
  • the CU may sends a DU configuration updating response message to the DU.
  • the system information updating message includes updated system information and/or scheduling information of the system information.
  • the CU may send the updated system information and/or the scheduling information of the system information to the DU through the DU configuration updating response message.
  • the CU When the application layer information of the CU, e.g., the list of PLMN supported by the CU, is updated, the CU sends a CU configuration updating message to the DU to notify the DU of the updated application layer information.
  • the DU stores the received updated application layer information.
  • the DU may send a CU configuration updating response message to the CU.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • a method for performing access for a UE is as shown in Fig.6, and the method may be used in a scenario of attach, packet data network (PDN) connection establishment, etc.
  • PDN packet data network
  • the access network entity is a gNB. If the gNB is further divided into CU and DU function entities, they are transparent to the UE and the core network. Therefore, when the communication procedures between the UE and the gNB is described, what described is RRC procedures between the UE and the gNB; and when the communication procedures between the gNB and the core network, what described is procedures between the gNB and the AMF or between the gNB and the UPF.
  • the procedure between the UE and the gNB is described as a procedure between the UE and the DU, and the procedure between the gNB and the AMF or between the gNB and the UPF is described as a procedure between the CU and the AMF or between the CU and the UPF, similarly for other embodiments, which does not affect the main content of the present disclosure.
  • the detailed description irrelevant to the present disclosure is omitted, e.g., the procedure between the AMF and the SMF and between the AMF and the UPF.
  • the method shown in Fig.6 includes the following steps:
  • Step 501 the UE sends an RRC connection request message to the base station.
  • Step 502 the DU receives the RRC connection request message from the UE.
  • the DU receives the message from the UE on a common control channel (CCCH), and knows that the UE is in an idle mode or an inactive mode.
  • the DU sends an initial UE message transfer message to the CU.
  • CCCH common control channel
  • the initial UE message transfer message is an F1 application layer AP message.
  • the F1 application layer AP message may include one or more information elements of the following:
  • the cell identity is to indicate a cell, from which the DU receives the message from the UE.
  • the cell identity may be a global cell identity or a cell identity unique on the DU or a cell identity unique on the CU. If the cell identity is the cell identity unique on the DU, then the initial UE message transfer message also contains a DU identity.
  • RRC messages between the DU and the CU may be transmitted through a control plane (i.e., through an F1 AP message), or an RRC message on a signaling radio bearer SRB0 may be transmitted through the control plane, and RRC messages on other SRBs are transmitted through the user plane, i.e., through a GPRS tunneling protocol of the user plane (GTP-U).
  • a control plane i.e., through an F1 AP message
  • RRC message on a signaling radio bearer SRB0 may be transmitted through the control plane
  • RRC messages on other SRBs are transmitted through the user plane, i.e., through a GPRS tunneling protocol of the user plane (GTP-U).
  • GTP-U GPRS tunneling protocol of the user plane
  • the RRC messages on the other SRBs are transmitted through a same user plane tunnel, or for each SRB, a user plane tunnel is established, and the RRC messages on the other SRBs are transmitted through user plane tunnels separately.
  • the allocated channel information in the following corresponds to each SRB.
  • the present embodiment provides three approaches to establish a user plane tunnel for transmitting RRC messages between the DU and the CU.
  • Approach 1 in step 502, the DU allocates downlink tunnel information, and sends the allocated downlink tunnel information to the CU through an initial UE message transfer message.
  • the CU allocates uplink tunnel information, and sends the allocated uplink tunnel information to the DU through a radio bearer configuration message.
  • the downlink tunnel information and the uplink tunnel information includes a TEID and/or a transport layer address.
  • Approach 2 in step 502, the DU allocates the downlink tunnel information, and sends the allocated downlink tunnel information to the CU through the initial UE message transfer message.
  • the CU allocates the uplink tunnel information, and sends the allocated uplink tunnel information to the DU through a downlink RRC transfer message.
  • the downlink tunnel information and the uplink tunnel information includes the TEID and/or the transport layer address.
  • Approach 3 in step 503, the CU allocates uplink tunnel information, and sends the allocated uplink tunnel information to the DU through a radio bearer configuration message.
  • the DU allocates downlink tunnel information, and sends the allocated downlink tunnel information to the CU through a radio bearer configuration response message.
  • the downlink tunnel information and the uplink tunnel information includes the TEID and/or the transport layer address.
  • Step 503 the CU receives the initial UE message transfer message from the DU, and according to the RRC message contained in the initial UE message transfer message, the CU knows that the RRC message is an RRC connection request message.
  • the CU allocates a CU UE AP ID on the F1 interface for the UE.
  • the CU sends a radio bearer configuration message to the DU, to request the DU to establish UE context and configure a radio bearer for the UE, and the radio bearer is a configuration of the SRB.
  • the radio bearer configuration message may include one or more of the following information elements:
  • the cell identity is a global cell identity or a cell identifier unique on the DU or a cell identifier unique on the CU.
  • the RB contained in the radio bearer configuration message may be an SRB and/or a DRB.
  • the RB to be configured is an SRB.
  • the radio bearer configuration message includes uplink tunnel information allocated by the CU.
  • the channel information is transmitted for RRC messages on all other SRBs other than the SRB0. Or for each SRB, channel information is allocated.
  • the radio bearer configuration request message may be a UE context establishment request or may be named otherwise, which does not affect the main content of the present disclosure.
  • Step 504 the DU configures resources.
  • the DU sends a radio bearer configuration response message to the CU.
  • the radio bearer configuration response message may include one or more of the following:
  • the radio bearer configuration response message includes information of a downlink tunnel allocated by the DU.
  • the DU may send the C-RNTI allocated for the UE by the DU to the CU through this step or through the step 502.
  • the CU receives the C-RNTI allocated for the UE by the DU, the CU stores it. In this way, the CU knows the C-RNTI allocated for the UE by the DU in the cell, and during the handover procedure, when the CU needs to allocate a C-RNTI for the UE, the CU selects a C-RNTI unallocated in the cell to the UE.
  • the radio bearer configuration response message may be a UE context establishment response or may be named otherwise, which does not affect the main content of the present disclosure.
  • Step 505 the CU sends a downlink RRC transfer message to the DU.
  • the downlink RRC transfer message includes one or more of the following:
  • the RRC message in the present embodiment is an RRC connection establishment message.
  • the CU may send a C-RNTI allocated to the UE to the UE through the RRC message.
  • the downlink RRC transfer message includes uplink tunnel information allocated by the CU.
  • the uplink tunnel information is transmitted for RRC messages on other SRBs except for the SRB0. Or, for each SRB, there is one piece of channel information allocated.
  • the CU may send the RRC connection establishment message to the DU through the message in the step 503.
  • the step 505 may not be performed.
  • Step 506 the DU sends the RRC message received to the UE.
  • Step 507 the UE sends an RRC connection establishment completion message to the base station.
  • Step 508 the DU sends the received RRC message to the CU through the control plane or the user plane.
  • the DU knows that the received RRC message is a message, from which UE according to the message received from the allocated DCCH resource.
  • the DU sends an uplink RRC transfer message to the CU.
  • the uplink RRC transfer message may include one or more pieces of the following information:
  • the RRC message is an RRC connection establishment completion message.
  • the DU Corresponding to the method of sending RRC messages on SRBs except for that on the SRB0 to the CU through the user plane, the DU sends an uplink RRC message to the CU through the GTP-U.
  • the header of a packet on the user plane may include SRB information, e.g., an SRB1 or an SRB2.
  • the CU may indirectly know the SRB information in a received RRC message by analyzing the RRC message.
  • the DU selects an established user plane tunnel to transmit the RRC message to the CU according to the SRB in the RRC message received.
  • Step 509 the CU sends an initial UE message to the AMF.
  • the AMF needs only to send an NAS message to the UE, but does not need to establish a session, then the AMF sends a downlink NAS transfer message to the base station; if it needs to establish a session, then the AMF sends the initial context establishment request message of the step 510 to the base station.
  • Step 510 the AMF sends an initial UE context establishment request message to the CU.
  • the CU If the CU receives the downlink NAS transfer message from the AMF, then the CU directly performs the subsequent steps, but does not need to perform the RB reconfiguration procedures in steps 511 to 5016.
  • the CU sends an RRC message downlink NAS transfer message to the DU through a control plane or a user plane.
  • the CU sends a downlink RRC transfer message to the DU.
  • the downlink RRC transfer message may include one or more pieces of the following information:
  • the RRC message is a downlink NAS transfer message.
  • the CU Corresponding to the method of sending RRC messages on SRBs except for that on the SRB0 through the user plane, the CU sends the downlink NAS transfer message to the DU through the GTP-U.
  • the header of a packet on the user plane may include SRB information, e.g., an SRB1 or an SRB2.
  • the header of the packet on the user plane may also include information regarding on which logic channel, the RRC message is transmitted.
  • the CU sends an RRC message to the DU through a corresponding channel, and the DU knows on which SRB, the RRC message is sent to the UE according to a channel in the received information.
  • Step 511 the CU sends a radio bearer reconfiguration request message to the DU.
  • the radio bearer reconfiguration request message may include one or more pieces of the following information:
  • the information of the RB to be added includes an identity of the RB, configuration information of a physical channel of the RB, configuration information of a transport channel of the RB, configuration information of a logic channel of the RB, information of a QoS flow or Qos flows mapped on the RB and/or uplink tunnel information for the RB.
  • the information of the QoS flow mapped on the RB includes a flow identity of the QoS flow and QoS information of the QoS flow.
  • the uplink tunnel information includes a transport layer address and an uplink TEID.
  • the information of the RB to be reconfigured includes an identity of the RB, reconfiguration information of a physical channel of the RB, reconfiguration information of a transport channel of the RB, reconfiguration information of a logic channel of the RB, information of a QoS flow or Qos flows to be added to the RB, information of a QoS flow or Qos flows to be deleted from the RB and/or information of a QoS flow to be transmitted on the RB.
  • the information of the QoS flow to be added on the RB includes an identity of the QoS flow and QoS information of the QoS flow.
  • the information of the QoS flow to be reconfigured on the RB includes an identity of the QoS flow and QoS parameters to be reconfigured.
  • the information of the QoS flow to be deleted from the RB includes an identity of the QoS flow.
  • the information of the RB to be deleted includes an identity of the RB.
  • the data transfer through the user plane between the DU and the CU may be that multiple RBs share one GTP-U channel, or that each RB uses one GTP-U channel.
  • Step 512 the DU allocates resources.
  • the DU sends a radio bearer reconfiguration response message to the CU.
  • the radio bearer reconfiguration response message may include one or more of the following:
  • the configuration information of the RB includes an identity of the RB and downlink tunnel information allocated by the DU.
  • the downlink tunnel includes a transport layer address and an uplink TEID.
  • Step 513 the CU sends an RRC message RRC connection reconfiguration to the DU through the control plane or the user plane.
  • the CU sends a downlink RRC transfer message to the DU.
  • the downlink RRC transfer message may include one or more pieces of the following information:
  • the RRC message in the present embodiment is an RRC connection reconfiguration message.
  • the CU Corresponding to the method of sending RRC messages on SRBs except for that on the SRB0 through the user plane, the CU sends the RRC connection reconfiguration message to the DU through the GTP-U.
  • the header of a packet on the user plane may include SRB information, e.g., an SRB1 or an SRB2.
  • the header of the packet on the user plane may also include information regarding on which logic channel, the RRC message is transmitted.
  • the CU sends an RRC message to the DU through a corresponding channel, and the DU knows on which SRB, the RRC message is sent to the UE according to a channel in the received information.
  • Step 5014 the DU sends the RRC message received from the CU to the UE.
  • Step 5015 the UE sends an RRC connection reconfiguration completion message to the base station.
  • Step 5016 the DU sends the received RRC message to the CU through the control plane or the user plane.
  • the DU knows that the RRC message is a message of which UE according to the message received from the DCCH resources allocated.
  • the DU sends an uplink RRC transfer message to the CU.
  • the uplink RRC transfer message may include one or more pieces of the following information:
  • the RRC message in the present embodiment is an RRC connection establishment reconfiguration completion message.
  • the DU sends the uplink RRC message to the CU through the GTP-U.
  • the header of a packet on the user plane may include SRB information, e.g., the SRB1 or the SRB2.
  • the CU may indirectly know the SRB information of the received RRC message by analyzing the RRC message.
  • the DU selects to perform transfer on which established user plane tunnel according to the SRB of the RRC message received.
  • the description of the method for performing access for a UE is completed.
  • the problem of performing access for a UE is solved when the gNB is divided into a DU and a CU, and the method may be applicable to scenarios of Attach, PDU establishment, and so on, to guarantee that the DU and the CU support interconnection and intercommunication between devices of multiple manufacturers.
  • a method for performing a handover between different DUs of a same CU (i.e., a source DU and a target DU access to a same CU) for a UE is as shown in Fig.7.
  • a source DU and a target DU access to a same CU i.e., a source DU and a target DU access to a same CU
  • the method includes the following steps:
  • Step 601 the UE sends a measurement report message to a base station.
  • a DU receives an RRC message from the UE, it sends the RRC message to a CU through a control plane or a user plane.
  • the method of sending the RRC message to the CU through the control plane or the user plane is the same as what described in step 508 and step 5016, and will not be elaborated herein.
  • the DU in the step is a source DU (S-DU).
  • Step 602 the CU decides to initiate a handover for the UE.
  • a target cell of the handover is in another DU.
  • the CU decides to perform a normal handover or a make-before-break (MBB) handover.
  • the CU sends a radio bearer configuration message to a target DU (T-DU), to request the T-DU to establish UE context and configure a radio bearer for the UE, and the radio bearer includes configurations of an SRB and a DRB.
  • T-DU target DU
  • the radio bearer includes configurations of an SRB and a DRB.
  • the radio bearer configuration message may include one or more pieces of the following information:
  • the context information of the UE on the S-DU includes a cell identity of a source cell where the UE is located, configuration information of an RB or RBs of the UE on the source cell, and/or UE capability information.
  • the identity of the target cell is a global cell identity of the target cell or a cell identity unique on the DU or a cell identity unique on the CU.
  • the RB included in the radio bearer configuration message may be an SRB and/or a DRB.
  • the RB to be configured is SRB and DRB information.
  • the radio bearer configuration message includes uplink tunnel information allocated by the CU.
  • the radio bearer configuration message includes uplink tunnel information allocated to the SRBs by the CU, and the uplink tunnel information may correspond to each SRB, or may be a tunnel commonly used for transmitting the RRC messages on SRBs except for that on the SRB0.
  • the uplink tunnel information includes a transport layer address and a TEID.
  • the information may be contained when the CU decides to perform an MBB handover.
  • the radio bearer configuration message may be a UE context establishment request or may be named otherwise, which does not affect the main content of the present disclosure.
  • the present disclosure provides two methods of allocating a C-RNTI for the UE during a handover:
  • Method 1 The CU allocates a C-RNTI in a target cell where the UE is located for the UE;
  • Method 2 The target DU allocates a C-RNTI in a target cell for the UE.
  • the CU allocates the C-RNTI of the target cell where the UE is located for the UE.
  • the CU sends the C-RNTI allocated to the target DU through a radio bearer configuration message.
  • the CU allocates the C-RNTI for the UE, it needs to guarantee the unique of the C-RNTI in the cell. Because in the UE initial access procedure, it is the DU that allocates a C-RNTI for the UE, and the DU will send the C-RNTI allocated for the UE to the CU, so that the CU can send the C-RNTI allocated for the UE to the UE through an RRC message.
  • the CU After the CU receives the C-RNTI allocated for the UE by the DU, it stores the C-RNTI, so that the CU can know that the DU has allocated the C-RNTI for the UE in the cell, and if during the handover procedure, the CU needs to allocate a C-RNTI for the UE, it selects a C-RNTI not allocated in the cell, and allocates it to the UE.
  • Step 603 the T-DU configures resources.
  • the T-DU sends a radio bearer configuration response message to the CU.
  • the radio bearer configuration response message may include one or more pieces of the following information:
  • the RB information includes SRB and DRB configuration information.
  • the radio bearer configuration response message includes information of a downlink tunnel allocated by the T-DU.
  • the message includes downlink tunnel information allocated for the SRBs by the T-DU, and the downlink tunnel information may correspond to each SRB, or may be a channel commonly used for transmitting the RRC messages on SRBs except for that on the SRB0.
  • the downlink tunnel information includes a transport layer address and a TEID.
  • the radio bearer configuration response message may be a UE context establishment response, or may be named otherwise, which does not affect the main content of the present disclosure.
  • the target DU allocates the C-RNTI for the UE in the target cell where the UE is located.
  • the target DU sends the allocated C-RNTI to the CU through a radio bearer configuration response message.
  • the DU allocates the C-RNTI for the UE, it needs to guarantee the unique of the C-RNTI in the cell.
  • the target DU stores the C-RNT contained in the radio bearer configuration message received.
  • the target DU allocates a C-RNTI for the initially accessed UE, it does not use this C-RNTI. If the C-RNTI contained in the radio bearer configuration message received by the target DU has been allocated to another UE, then the DU processes this situation according to the following two approaches:
  • the target DU sends a radio bearer configuration failure message to the CU.
  • the radio bearer configuration failure message may include a reason of failure: an invalid C-RNTI.
  • the CU ends the procedure of handing over the UE to the T-DU.
  • Approach 2 the target DU allocates another C-RNTI unused to the UE, and sends the new C-RNTI to the CU through a radio bearer configuration response message. After the CU receives the new C-RNTI from the DU, the CU modifies the C-RNTI allocated to the UE.
  • Step 604 the CU sends an RRC connection reconfiguration message to the S-DU through the control plane or the user plane.
  • the CU includes the C-RNTI of the target cell allocated to the UE into the RRC connection reconfiguration message, and the C-RNTI is allocated by the CU or by the target DU.
  • the CU sends a downlink RRC transfer message to the S-DU.
  • the downlink RRC transfer message may include one or more pieces of the following information:
  • the RRC message is an RRC connection reconfiguration message.
  • the S-DU receives the information for performing a handover between different DUs, it stops transmitting data to the UE, the S-DU does not receive uplink data from the UE anymore after the S-DU sends the received RRC message to the UE.
  • the S-DU may continue to transmit data to the UE and receive uplink data from the UE.
  • the S-DU receives an indication of stopping data transmission from the CU, it stops transmiting downlink data to the UE and/or stopping receiving data from the UE.
  • the S-DU decides when to stop transmiting data to the UE, e.g., when the S-DU does not receive an uplink acknowledgment from the UE anymore, the S-DU will stop transmiting data to the UE.
  • the CU sends the following information to the S-DU through a separate F1AP message, or includes the following information in a data packet header:
  • the S-DU receives the information of handover between different DUs, it stops transmiting data to the UE, and does not receive uplink data from the UE anymore after the S-DU sends the received RRC message to the UE.
  • the S-DU may continue to transmit data to the UE and receive uplink data from the UE.
  • the S-DU receives the indication of stopping data transmission from the CU, it stops transmiting downlink data to the UE and/or stopping receiving data from the UE.
  • the S-DU decides when to stop transmiting data to the UE, e.g., when the S-DU does not receive an uplink acknowledgement from the UE anymore, the S-DU stops transmiting data to the UE.
  • the data packet header further includes the CU UE AP ID allocated for the UE by the CU, the DU UE AP ID allocated for the UE by the S-DU and/or information of a logic channel for sending RRC messages.
  • Step 605 the DU sends the RRC message received to the UE.
  • the CU Corresponding to the method of the CU deciding to use the MBB handover, and the CU deciding when the S-DU stops transmitting the downlink data to the UE or when the S-DU stops communicating with the UE, when the CU decides that the S-DU stops transmitting the downlink data to the UE or stopping communicating with the UE, the CU sends a data transfer stopping indication message to the S-DU. After the S-DU receives the corresponding data transfer stopping indication message from the CU, it stops communicating with the UE.
  • the CU may start to transmit data to the T-DU, and the CU transmits data not acknowledged by the UE and data received from the UPF to the T-DU.
  • the data is a PDCP PDU.
  • Method 1 the CU directly sends data that has not been acknowledged by the UE and that is received from the UPF to the T-DU.
  • the data is PDCP PDU. Data forwarding between the S-DU and the T-DU is not necessary.
  • Method 2 the CU directly sends data that has not been acknowledged by the UE and that is received from the UPF to the T-DU.
  • the data is PDCP PDU.
  • the S-DU sends RLC context at the source DU side to the T-DU.
  • the T-DU only transmits RLC PDUs that have not been received by the UE to the UE, and does not need to transmit all the RLC PDUs to the UE, so as to avoid repeatedly transmitting the data.
  • step 605a and step 605b should be performed. This method is applicable to a situation where the T-DU and the S-DU have a same RB configuration.
  • the S-DU may also forward RLC PDUs that have not been acknowledged by the UE to the T-DU.
  • Step 605a the S-DU sends a first RLC context transfer message to the CU.
  • the first RLC context transfer message may include one or more pieces of the following information:
  • the RLC transfer status includes the SN of the last GTP-U data packet that has been transmitted successfully, the SN(s) of GTP-U data packets that have not been transmitted successfully and/or the SN(s) of RLCs that have not been transmitted successfully.
  • Step 605b the CU sends a second RLC context transfer message to the T-DU.
  • the second RLC context transfer message may include one or more pieces of the following information:
  • the RLC transfer status includes the SN of the last GTP-U data packet that has been transmitted successfully, the SN(s) of GTP-U data packets that have not been transmitted successfully and/or the SN(s) of RLCs that have not been transmitted successfully.
  • the PDCP transmission status includes the SN of the last GTP-U data packet that has been transmitted successfully, the SN(s) of GTP-U data packets that have not been transmitted successfully and/or the receiving status of uplink PDCPs.
  • the DU according to the feedback from the UE on the RLC layer, determines that which PDCP data packets have been received by the UE, and which PDCP data packets have not been received by the UE, so as to decide the PDCP transmission and receiving status.
  • the RLC context transfer may be referred to as PDCP context transfer or may be named otherwise, which does not affect the main content of the present disclosure.
  • step 605a may be performed, to notify the PDCP transmission and receiving status to the CU, so that the CU knows that is should send which PDCP data packets to the T-DU.
  • the step 605a and the step 605b are not mandatory steps for the present disclosure.
  • Step 606 the UE is synchronized to the target cell.
  • Step 607 the UE sends an RRC connection establishment completion message to the base station.
  • the T-DU sends the RRC message received to the CU through the control plane or the user plane.
  • the method for the DU sending the RRC message to the CU is the same as that in the step 5016, and will not be elaborated herein.
  • Step 608 the CU sends a UE context releasing message to the S-DU.
  • the UE context releasing message includes the CU UE AP ID allocated for the UE by the CU, and the DU UE AP ID allocated for the UE by the S-DU.
  • the description of the method for performing a handover between different DUs for the UE is completed.
  • the problem of performing a handover for the UE is solved when the gNB is divided into DUs and a CU, which avoid data loss, and guarantees that the DUs and the CU support interconnection and intercommunication between devices of multiple manufacturers.
  • Embodiment 6 is a diagrammatic representation of Embodiment 6
  • a method for performing access for a UE through different DUs of a same CU i.e., the UE performing access through a DU-1 and a DU-2, and the DU-1 and the DU-2 access to the same CU
  • Fig.8 A method for performing access for a UE through different DUs of a same CU (i.e., the UE performing access through a DU-1 and a DU-2, and the DU-1 and the DU-2 access to the same CU) according to the present disclosure is as shown in Fig.8.
  • the detailed description of the steps irrelevant to the present disclosure is omitted, e.g., the procedures among the AMF and the SMF and the UPF.
  • the method includes the following steps:
  • Step 701 the UE sends a measurement report message to a base station.
  • the DU receives the RRC message from the UE, it sends the RRC message received to the CU through a control plane or a user plane. How to send the RRC message received to the CU through the control plane or the user plane is the same as those in step 508 and step 5016, and will not be elaborated herein.
  • the DU of the present step is a DU (the DU-1) that serves the UE.
  • Step 702 according to the measurement report message from the UE, the CU decides to switch a part of bearers of the UE to a cell of the DU-2.
  • the CU decides whether to perform a normal handover or an MBB handover.
  • the CU sends a radio bearer configuration message to the DU-2, to request the DU-2 to establish UE context and configure a radio bearer for the UE.
  • the CU decides whether to switch a part of DRBs or all DRBs to the DU-2.
  • the radio bearer configuration message may include one or more of the following information elements:
  • the context information of the UE includes a cell identifier of a DU-1 cell where the UE is located, RB configuration information of the UE on the DU-1 cell and/or UE capability information.
  • the identity of the target cell is a global cell identity or a cell identity unique on the DU or a cell identity unique on the CU.
  • the radio bearer configuration message includes uplink tunnel information allocated by the CU.
  • the uplink tunnel information includes a transport layer address and a TEID.
  • the radio bearer configuration message may be a UE context establishment request or may be named otherwise, which does not affect the main content of the present disclosure.
  • Method 1 the CU allocates a C-RNTI on the DU-2 cell for the UE;
  • Method 2 the DU-2 allocates a C-RNTI on the DU-2 cell for the UE.
  • the CU allocates a C-RNTI of the DU-2 cell where the UE is located for the UE.
  • the CU sends the C-RNTI allocated to the DU-2 through the radio bearer configuration message.
  • the CU allocates the C-RNTI for the UE, it needs to guarantee the unique of the C-RNTI in the cell. Because in the UE initial access procedure, it is the DU that allocates a C-RNTI for the UE, and the DU will send the C-RNTI allocated for the UE to the CU, so that the CU can send the C-RNTI allocated for the UE to the UE through an RRC message.
  • the CU After the CU receives the C-RNTI allocated for the UE by the DU, it stores the C-RNTI, so that the CU can know that the DU has allocated the C-RNTI for the UE in the cell, and if the CU needs to allocate a C-RNTI for the UE, it selects a C-RNTI not allocated in the cell, and allocates it to the UE.
  • Step 703 the DU-2 configures resources.
  • the DU-2 sends a radio bearer configuration response message to the CU.
  • the radio bearer configuration response message may include one or more of the following information elements:
  • the radio bearer configuration response message contains downlink tunnel information allocated by the DU-2.
  • the downlink tunnel information includes a transport layer address and a TEID.
  • the radio bearer configuration response message may be a UE context establishment response message, or may be named otherwise, which does not affect the content of the present disclosure.
  • the DU-2 allocates a C-RNTI of the DU-2 cell where the UE is located.
  • the DU-2 sends the C-RNTI allocated to the CU through a radio bearer configuration response message.
  • the DU-2 allocates C-RNTI for the UE, it needs to guarantee the unique of the C-RNTI in the cell.
  • the DU-2 stores the C-RNTI contained in the radio bearer configuration message received.
  • the DU-2 will not use the C-RNTI when it allocates a C-RNTI for the UE next time. If the C-RNTI included in the radio bearer configuration message received by the DU-2 has been allocated to another UE, then the DU-2 has two approaches to process this situation:
  • the DU-2 sends a radio bearer configuration failure message to the CU.
  • the radio bearer configuration failure message may include a reason of failure: an invalid C-RNTI.
  • the CU ends the procedure of configuring the UE to the DU-2.
  • Approach 2 the DU-2 allocates another C-RNTI unused to the UE, and sends the new C-RNTI to the CU through a radio bearer configuration response message. After the CU receives the new C-RNTI from the DU-2, it modifies the C-RNTI allocated to the UE using the new C-RNTI from the DU-2.
  • Step 704 the CU sends an RRC connection reconfiguration message to the DU-1 through the control plane or the user plane.
  • the CU includes the C-RNTI in the DU-2 cell allocated for the UE into the RRC connection reconfiguration message.
  • the C-RNTI is allocated by the CU or by the DU-2.
  • the CU sends a downlink RRC transfer message to the DU-1.
  • the downlink RRC transfer message may include one or more pieces of the following information:
  • the RRC message is an RRC connection reconfiguration message.
  • the information of the RB to be switched includes an RB identifier, a target DU identity and/or a target cell identity.
  • the DU-1 sends the RRC message received to the UE, it stops transmitting data to the UE, and does not receive uplink data from the UE anymore.
  • the CU may send the information of the RB to be switched to the DU-1 through a separate message.
  • the message, through which the CU notifies the DU of the information of the RB to be switched may be sent before or after the present step.
  • the DU-1 receives an MBB handover indication, then after the DU-1 sends the RRC message received to the UE, it may continue to send data to the UE and receive uplink data from the UE on the RB to be switched. After the DU-1 receives a data transmission stopping indication from the CU, it stops transmitting downlink data to the UE and/or stops receiving data from the UE on the corresponding RB. Or the DU-1 decides when to stop transmitting the data to the UE, e.g., the DU-1 stopping transmitting data to the UE after it does not receive uplink acknowledgment from the UE anymore.
  • Step 705 the DU-1 sends the RRC message received to the UE.
  • the CU Corresponding to the method of the CU deciding to use the MBB handover, and the CU deciding when the DU-1 to stop transmitting downlink data to the UE or stop communicating with the UE on the RB to be switched, the CU sends a data transmission stopping message to the DU-1. After the DU-1 receives the corresponding message from the CU, it stops communicating with the UE on the RB to be switched.
  • the CU may start to transmit data to the DU-2 on the RB, to which the handover is performed, and the CU transmits data that has not been acknowledged by the UE and that has been received by the UPF to the DU-2.
  • the data is PDCP PDU.
  • Method 1 the CU directly transmits data that has not been acknowledged by the UE and that is received from the UPF to the DU-2.
  • the data is PDCP PDU.
  • the data forwarding between the DU-1 and the DU-2 is not necessary.
  • the CU directly transmits data that has not been acknowledged by the UE and that is received from the UPF to the DU-2.
  • the data is PDCP PDU.
  • the DU-1 sends RLC context at the source side to the DU-2.
  • the DU-2 only transmits RLC PDUs that have not been received by the UE to the UE, and does not need to transmit all the RLC PDUs to the UE, so as to avoid repeatedly transmitting the data.
  • a step similar to step 605a and step 605b should be performed, and the DU-1 sends the RLC context to the DU-2 through the CU.
  • the difference between the step and the step 605a and the step 605b is that the RLC context is only intended for an RB to be switched, and the S-DU is the DU-1, and the T-DU is the DU-2, the other parts are same, which will not be elaborated herein.
  • the method is applicable to a situation where the RB configurations in the DU-1 and the DU-2 are same.
  • the DU-1 may forward RLC PDUs that have not been acknowledged by the UE to the DU-2.
  • the step 605a and the step 605b are not mandatory steps of the present disclosure.
  • Step 706 the UE is synchronized to the target cell.
  • Step 707 the UE sends an RRC connection establishment completion message to the base station.
  • the DU-1 sends the RRC message received to the CU through the control plane or the user plane.
  • the DU-1 sends the RRC message to the CU through a method same as that in step 5016, which will not be elaborated herein.
  • Step 708 the CU sends a radio bearer configuration completion indication message to the DU-2, and sends the RB configuration information received from the UE to the DU-2.
  • the RB configuration information may only include a delta configuration, i.e., a difference between the configuration configured by the DU-2 for the UE, but the actual configuration in the UE.
  • the message may include full configurations of the UE.
  • Step 709 the CU sends a radio bearer reconfiguration or RB releasing message to the DU-1.
  • the radio bearer reconfiguration or RB releasing message includes the CU UE AP ID allocated for the UE by the CU, and a DU UE AP ID allocated for the UE by the DU-1.
  • the message includes information of an RB to be released, or information of an RB which is switched to the DU-2 successfully.
  • the RB information includes an RB identifier.
  • Step 710 the DU-1 sends a radio bearer re-configuration response or an RB releasing response message to the CU.
  • the description of the method for performing access for a UE through different DUs of a same CU is completed.
  • the problem of performing access for the UE through different DUs is solved when a gNB is divided into DUs and a CU, which improves the throughput of the UE, avoids data loss on the switched bearers, and guarantees that the DUs and the CU support interconnection and intercommunication between devices of multiple manufacturers.
  • the methods of establishing a fronthaul interface, methods of performing access for a UE, and methods for performing a handover for a UE may solve the communication problem raised when a gNB is divided into DUs and a CU, reduce the configuration cost of the operator, improves the throughput of the UE, avoids data loss, and guarantees that the DUs and the CU support interconnection and intercommunication between devices of multiple manufacturers.
  • the present disclosure provides a method for enhancing the function of a UE and achieving data forwarding in a 5G communication network.
  • a UE enters an enhanced mode upon receiving an indication from a base station and forwards data between the base station and other UEs in the enhanced mode.
  • a UE having an enhanced function may provide a data forwarding function for other UEs.
  • the QoS of UEs having a poor channel condition is improved and the user experience is further improved.
  • the UE in the enhanced mode corresponds to the first UE mentioned in the claims, hereinafter referred to as enUE; and other UEs correspond to the second UE mentioned in the claims.
  • data transmission may still be scheduled by the base station, and may also be scheduled by the UE entering the enhanced mode.
  • the UE entering the enhanced mode receives, from the base station, scheduling information on time-frequency resources of other UEs scheduled by the base station; and forwarding, by the UE, data between the base station and other UEs includes: by the UE, receiving downlink data sent to other UEs from a base station, processing the downlink data layer by layer by a protocol stack structure corresponding to the UE in the enhanced mode, and forwarding, to the corresponding other UEs, the downlink data on the corresponding time-frequency resources according to the scheduling information on the time-frequency resources of other UEs; and/or by the UE, receiving, uplink data sent to a base station from other UEs on corresponding time-frequency resources according to the scheduling information on the time-frequency resources of other UEs, processing the uplink data layer by layer by a protocol stack structure corresponding to the UE in the enhanced mode, and forwarding the uplink data to the base station.
  • enUE receives, from the base station, scheduling information on time-frequency resources of other UEs scheduled by
  • the base station may further transmit context information and timing information of other UEs to the enUE.
  • the enUE is required to advance or delay corresponding time according to the timing information.
  • the timing information is time information to be advanced or delayed when the enUE forwards data of other UEs.
  • the UE entering the enhanced mode transmits scheduling information on time-frequency resources to other UEs; and forwarding, by the UE, data between the base station and other UEs includes: by the UE, receiving downlink data sent to other UEs from a base station, processing the downlink data layer by layer by a protocol stack structure corresponding to the UE in the enhanced mode, and forwarding, to other UEs, the downlink data on the corresponding time-frequency resources according to the scheduling information; and/or by the UE, receiving uplink data sent to a base station from other UEs on corresponding time-frequency resources according to the scheduling information, processing the uplink data layer by layer by a protocol stack structure corresponding to the UE in the enhanced mode, and forwarding the uplink data to the base station.
  • the enUE may form a new cell and accept the access of other UEs in this new cell, or may not form a new cell. If the enUE forms a new cell, the enUE needs to receive, from the base station, cell configuration information and access information used by other UEs to access the enUE, and transmit the access information and allow other UEs to access the enUE according to an access request from other UEs.
  • the enUE forms a new cell and the new cell operates in an independent mode.
  • Information sent to the enUE by the base station at least includes one of the following information (the following information is mainly information used by the enUE to serve other UEs):
  • configuration information of the formed new cell for example, cell ID, operating frequency information, bandwidth information, information carried by a broadcast channel, information carried by a synchronization channel, configuration information of an access channel used by a user to access the new cell, and more.
  • Information sent to other UEs by the base station includes:
  • configuration information of the new cell that other UEs access for example, cell ID, operating frequency information, bandwidth information, information carried by a broadcast channel, information carried by a synchronization channel, configuration information of an access channel used by a user to access the new cell, and more.
  • the enUE forms a new cell and the new cell operates in a non-independent mode.
  • Information sent to the enUE by the base station at least includes one of the following information (the following information is mainly information used by the enUE to serve other UEs):
  • configuration information of the formed new cell for example, cell ID, operating frequency information, bandwidth information, information carried by a broadcast channel, information carried by a synchronization channel, configuration information of an access channel used by a user to access the new cell, and more.
  • Information sent to other UEs by the base station includes:
  • configuration information of the new cell that other UEs access for example, cell ID, operating frequency information, bandwidth information, information carried by a broadcast channel, information carried by a synchronization channel, configuration information of an access channel used by a user to access the new cell, and more.
  • the difference between the above two modes lies in that, in the first mode, the enUE transmits access information to the new cell according to the configuration information of the base station, and in the second mode, the enUE may not transmit access information to the new cell, or the enUE transmits only information on the synchronization channel.
  • the enUE does not form a new cell.
  • Information sent to the enUE by the base station at least includes one of the following information (the following information is mainly information used by the enUE to serve other UEs):
  • timing indication information for serving other UEs the indication information being used to indicate the amount of time to be delayed or advanced when the enUE receives and/or transmits data of other UEs.
  • the base station is not required to transmit additional information to other UEs. Processing may be performed according to the existing methods in the prior art.
  • Fig. 9 is a flowchart of a preferred method according to the present disclosure, including the following steps.
  • Step 901 A UE reports, to a base station, its capability of supporting an enhanced mode.
  • the base station may know a UE's capability of supporting an enhanced mode in other ways. For example, it is considered that a UE supports the enhanced mode if this UE reports the channel state information on one or more carriers between the UE and other surrounding UEs. If a UE supports the enhanced mode, the UE may further report a protocol stack structure information (which will be described in detail below) supported in the enhanced mode.
  • a protocol stack structure is represented by explicit indication information. For example, "1" represents a first structure, "2" represents a second structure, and so on.
  • configuration information of each protocol layer in a protocol stack used by the enUE to serve other UEs may be directly given.
  • Step 902 The base station transmits, to a selected UE, an indication to enter the enhanced mode.
  • the base station may also indicate the selected UE to exit the enhanced mode by issuing signaling.
  • the base station may select a UE having a good channel condition to enter the enhanced mode, in order to forward data between a UE having a poor channel condition and the base station.
  • Step 903 The UE in the enhanced mode (hereinafter referred to as enUE) acquires scheduling information on time-frequency resources of this UE and/or time-frequency resources of other UEs scheduled by the base station.
  • the method for acquiring the scheduling information may be based on a definite signaling between the base station and the UE, or realized in other ways, for example, the time-frequency resources are configured statically.
  • This step is an optional step. If the UE forms an independent new cell after entering the enhanced mode or the scheduling of data of other UEs is executed by the enUE, the data may be forwarded between the base station and other UEs even without the scheduling information of the base station.
  • Step 904 The UE in the enhanced mode forwards data between the base station and other UEs.
  • the UE in the enhanced mode may receive downlink data sent to other UEs from the base station, process the downlink data layer by layer by a protocol stack structure corresponding to the enUE in the enhanced mode, and forward the downlink data to one or more served UEs;
  • the UE in the enhanced mode may receive uplink data sent to the base station from one or more served UEs, process the uplink data layer by layer by a protocol stack structure corresponding to the enUE in the enhanced mode, and forward the uplink data to the base station.
  • the gNB needs to provide, to the UE, at least one of the following information a to d:
  • a protocol stack structure information used when serving other UEs that is, when forwarding data for other UEs.
  • the protocol stack structure used when the enUE serves other UEs at least includes one of the following structures:
  • Protocol stack structure B0 including: a Service Data Adaptation Protocol (SDAP) layer, a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer and a PHY layer.
  • SDAP Service Data Adaptation Protocol
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • a protocol stack used for data transmission in the user plane includes an SDAP layer, a PDCP layer, an RLC layer, an MAC layer and a PHY layer
  • a protocol stack used for data transmission in the control plane includes an RRC layer, a PDCP layer, an RLC layer, an MAC layer and a PHY layer, as shown in Fig. 10.
  • Protocol stack structure B1 including: a PDCP layer, an RLC layer, an MAC layer and a PHY layer.
  • a protocol stack used for data transmission in the user plane includes a PDCP layer, an RLC layer, an MAC layer and a PHY layer; and a protocol stack used for data transmission in the control plane includes a PDCP layer, an RLC layer, an MAC layer and a PHY layer, as shown in Fig. 11.
  • Protocol stack structure B2 including: part of a PDCP layer, an RLC layer, an MAC layer and a PHY layer, as shown in Fig. 12.
  • part of a PDCP layer includes data integrity protection, and other functions of the PDCP layer are on the gNB side.
  • Protocol stack structure B3 including: an RLC layer, an MAC layer and a PHY layer, as shown in Fig. 13.
  • Protocol stack structure B4 including: part of an RLC layer, an MAC layer and a PHY layer, as shown in Fig. 14.
  • part of an RLC layer includes a segmentation function, and other functions of the RLC layer are on the gNB side.
  • Protocol stack structure B5 including: an MAC layer and a PHY layer, as shown in Fig. 15.
  • Protocol stack structure B6 including: part of an MAC layer and a PHY layer, as shown in Fig. 16.
  • part of an MAC layer includes functions having high time delay requirement, for example, HARQ, and other functions of the MAC layer are on the gNB side, for example, scheduling.
  • Protocol stack structure B7 including: a PHY layer, as shown in Fig. 17.
  • Protocol stack structure B8 including: part of a PHY layer, as shown in Fig. 18.
  • part of a PHY layer includes iFFT of the downlink signal and the addition of a cyclic prefix to the downlink signal, and FFT of the uplink signal and the removal of a cyclic prefix, and other functions of the PHY layer are on the gNB side.
  • Method 1 A protocol stack structure is represented by explicit indication information. For example, “1" represents structure B1, “2" represents structure B2, and so on.
  • Method 2 Configuration information of each protocol layer in a protocol stack used by the enUE to serve other UEs may be directly given.
  • the given information includes configuration information of the RLC layer, configuration information of the MAC layer, and configuration information of the PHY layer; and if protocol stack structure B4 is used, the given information includes part of configuration information of the RLC layer, configuration information of the MAC layer, and configuration information of the PHY layer.
  • b Information on a plane that the protocol stack structure serves (for example, the user plane, the control plane, or both the user plane and the control plane). This information is optional information. If this information is not included, it is indicated that a plane that the protocol stack structure serves includes the user plane and the control plane, or that a plane that the protocol stack structure serves is a default plane.
  • the protocol stack used by the enUE may be used only for data transmission of the user plane of other UEs, or only for data transmission of the control plane of other UEs, or for data transmission of both the user plane and the control plane of other UEs.
  • the protocol stack used for data transmission of the user plane may be different from the protocol stack used for data transmission of the control plane.
  • the protocol stack used for data transmission in the control plane and the user plane may be in any one of the above structures B0 to B8.
  • the protocol stack used by the enUE is a protocol stack indicated by B1 (including a PDCP layer, an RLC layer, an MAC layer and a PHY layer), and during the data transmission of the control plane, the protocol stack used by the enUE is a protocol stack indicated by B6 (including an MAC layer and a PHY layer).
  • the protocol stack used by the enUE is a protocol stack indicated by B3 (including an RLC layer, an MAC layer and a PHY layer)
  • the protocol stack used by the enUE is a protocol stack indicated by B1 (including a PDCP layer, an RLC layer, an MAC layer and a PHY layer).
  • a data transmission direction information of a plane that the protocol stack structure serves for example, uplink, or downlink, or both uplink and downlink. This information is optional information. If this information is not included, it is indicated that the data transmission direction in a plane that the protocol stack structure serves includes uplink and downlink, or that the data transmission direction in a plane that the protocol stack structure serves is a default direction.
  • the protocol stack used by the enUE may be used for forwarding of only a downlink signal of other UEs (the transmission of this downlink signal may be in only the control plane, in only the user plane, or inboth the user plane and the control plane), or forwarding of only an uplink signal of other UEs (the transmission of this uplink signal maybe only in the control plane, only in the user plane, or both in the user plane and the control plane).
  • ID information of a user that the enUE serves This information is optional information. If this information is not included, it is indicated that the enUE serves users all by the structures indicated by the above information a, b and c.
  • an enUE may serve different users by different protocol stack structures, different protocol stack structures may be configured for different enUEs, different protocol stack structures may be configured for different planes, and different protocol stack structures may be configured for different data transmission directions.
  • a, b, c and d are configured, or multiple sets (a1,b1,c1,d1), (a2,b2,c2,d2), ... are configured.
  • the base station may transmit, to a selected UE, configuration information related to forwarding of data of other UEs.
  • the configuration information is used to indicate data to be forwarded by the selected UE, that is, the configuration information is used to indicate which data from the base station, received by the selected UE, is to be forwarded to other UEs, or to indicate which data is data transmitted from other UEs and to be forwarded to the base station.
  • This configuration information may be transmitted to the selected UE together with the indication information which is transmitted by the base station to the selected UE in the step 902, or transmitted to the selected UE by an independent step after the step 902.
  • the configuration information At least includes one of the following information:
  • indication information of a bearer to which the data to be forwarded belongs wherein the indication information may be ID information of a bearer, and further, the indication information may indicate that the bearer is a bearer in the control plane or a bearer in the user plane;
  • ID information of a logical channel to which the data to be forwarded belongs is a logical channel used by the selected UE to receive or transmit the data forwarded by the selected UE;
  • the physical resources to which the data to be forwarded belongs are physical resources used by the selected UE to receive or transmit the data forwarded by the selected UE, for example, time resources, frequency resources, spatial resources, or time-frequency resources.
  • a UE selected by a base station needs to forward data of two other UEs (UE1 and UE2) and the following information is included in the configuration information transmitted to the UE0: ID of a bearer to which data of the UE1 forwarded by the UE0 belongs is 1 and ID of a bearer to which data of the UE2 forwarded by the UE0 belongs is 2, then:
  • a bearer to which data received by the UE0 from the base station belongs, is a bearer 1
  • the UE0 forwards the data to the UE1;
  • a bearer to which data received by the UE0 from the base station belongs, is a bearer 2
  • the UE0 forwards the data to the UE2;
  • the UE0 needs to forward the data to the base station.
  • a UE selected by a base station needs to forward data of two other UEs (UE1 and UE2) and the following information is included in the configuration information transmitted to the UE0: data of the UE1, which is forwarded by the UE0, belongs to data received on a logical channel 1, and data of the UE2, which is forwarded by the UE0, belongs to data received on a logical channel 2, then:
  • the UE0 forwards the data to the UE1;
  • the UE0 forwards the data to the UE2;
  • the data belongs to the UE2, and the UE0 needs to forward the data to the base station.
  • a UE selected by a base station needs to forward data of two other UEs (UE1 and UE2) and the following information is included in the configuration information transmitted to the UE0: data of the UE1, which is forwarded by the UE0, is from a time-frequency resource block 1, and data of the UE2, which is forwarded by the UE0, is from a time-frequency resource block 2, then:
  • the UE0 if the UE0 receives, from the time-frequency resource block 1, data from the base station, the UE0 forwards the data to the UE1;
  • the UE0 if the UE0 receives, from the time-frequency resource block 2, data from the base station, the UE0 forwards the data to the UE2;
  • the UE0 receives, from the time-frequency resource block 1, data from other UEs, the data belongs to the UE1, and the UE0 needs to forward the data to the base station;
  • the UE0 receives, from the time-frequency resource block 2, data from other UEs, the data belongs to the UE2, and the UE0 needs to forward the data to the base station.
  • the selected UE may reply the base station with a configuration response message to confirm the correct reception of the configuration information.
  • the enUE serves other UEs according to the configured protocol stack.
  • a cell supported by the base station is considered as the first cell, and a cell where enUE serves other UEs is considered as the second cell.
  • the first cell and the second cell may be a same cell or different cells. When they are different cells, they may be different cells at a same frequency or different cells at different frequencies.
  • This embodiment describes a case where the gNB configures an enUE to enter an enhanced mode B0, i.e., configures an enUE to use a protocol stack structure B0, in order to forward data of other UEs.
  • the first cell a cell supported by the gNB
  • the communication link between a UE and the gNB in the first cell is referred to as the first link.
  • the enUE will form a new cell which is referred to as the second cell, and a direct communication link between the enUE and other UEs in the second cell is referred to as the second link.
  • the first cell and the second cell may be at a same frequency or different frequencies.
  • the gNB may select, according to information reported by UEs, a UE that will become an enUE.
  • the information reported by UEs at least contains: channel state information in the first link.
  • it may contain at least one of the following information: UE location information, UE movement speed information, UE wireless capability information, information on interference strength of surrounding radio frequency bands, channel state information on one or more carriers between a UE and other UEs, video/audio information of the surrounding, etc.
  • the channel state information on one or more carriers between a UE and other UEs may assist the gNB in selecting a UE to enter an enhanced mode.
  • the gNB may determine, according to the channel state information in the first link reported by each UE, a channel condition between each UE and the gNB, and determine, according to the channel state information on at least one carrier between each UE and the surrounding other UEs, a channel condition between UEs, so as to select a UE having a good channel condition (better than a first set threshold) to enter an enhanced mode and forward data of a UE having a poor channel condition (worse than a second set threshold) by the UE entering the enhanced mode.
  • the gNB may indicate the UE to enter an enhanced mode B1 (i.e., indicate the UE to become an enUE) by using an RRC signaling (for example, RRC RECONFIGURATION) which carries configuration information of a UE-enhanced mode.
  • RRC signaling for example, RRC RECONFIGURATION
  • This configuration information may further include configuration information related to forwarding of data of other UEs.
  • the configuration information related to forwarding of data of other UEs may be transmitted to the UE by an RRC signaling different from the above RRC signaling.
  • a duplex mode used by the second link i.e., TDD, FDD, or full duplex
  • a carrier and a bandwidth used by the second link i.e., a physical cell ID of a cell where the second link is located, a maximum transmission power of the enUE in the second link, and an operating mode of the second link (i.e., stand-alone or non-stand-alone).
  • an operating mode of the second link i.e., stand-alone or non-stand-alone.
  • the UE executes corresponding configuration and enters an enhanced mode, and may reply with an RRC signaling (for example, RRC RECONFIGURATION COMPLETE) to inform the gNB of the successful execution of this operation.
  • RRC signaling for example, RRC RECONFIGURATION COMPLETE
  • the UE After the UE becomes an enUE, it operates in the enhanced mode B0.
  • the second cell operates in a stand-alone mode, and the enUE transmits a synchronization channel, a broadcast channel or the like necessary for other UEs to access the second cell and receives an access request from other UEs.
  • Other UEs are connected to the enUE by regarding the enUE as the gNB.
  • the second cell operates in a non-stand-alone mode, and the gNB may provide auxiliary information for a UE in the first cell to access the second cell.
  • the enUE communicates, by using a protocol stack which is used when serving other UEs in the enhanced mode configured by the gNB, with other UEs in the second cell, and communicates, by using its own UE protocol stack, with the gNB in the first cell.
  • the enUE forwards data according to the configuration information of the enhanced mode configured by the gNB.
  • the information on a plane served by a protocol stack used in the UE-enhanced mode includes both the control plane data and the user plane data and the data direction in the plane served by the protocol stack used in the UE-enhanced mode includes the uplink data and the downlink data
  • the enUE forwards the uplink control plane data and the uplink user plane data from other UEs to the gNB and also forwards the downlink control plane data and the downlink user plane data from the gNB, which are intended for other UEs, to other UEs.
  • the information on a plane served by a protocol stack used in the UE-enhanced mode in the configuration information may include only one of the control plane data and the user plane data, or the data direction in the plane served by the protocol stack used in the UE-enhanced mode may include only one of the uplink data and the downlink data.
  • the information on a plane served by a protocol stack used in the UE-enhanced mode includes only the user plane data, and other UEs exchange the control plane data with the gNB in other ways, for example, other UEs are directly connected to the gNB.
  • Fig. 19 is a schematic diagram of Embodiment 7 of the present disclosure. A process for processing data in the user plane and a process for processing data in the control plane in this embodiment will be described in detail below with reference to Fig. 19.
  • a process for processing downlink data between the gNB and the enUE includes the following steps.
  • Step 1 The gNB processes the raw data belonging to the enUE successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to the enUE via an interface UU1.
  • the raw data is data not yet processed by the protocol stack.
  • Step 2 The enUE processes the data received from the gNB successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data belonging to the enUE.
  • a process for processing uplink data between the gNB and the enUE includes the following steps.
  • Step 1 The enUE processes the raw data successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to the gNB via an interface UU1.
  • Step 2 The gNB processes the data received from the enUE successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data sent by the enUE.
  • a process for processing downlink data between the gNB and other UEs includes the following steps.
  • Step 1 The gNB processes raw data belonging to other UEs successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to the enUE via an interface UU1.
  • Step 2 The enUE processes, according to the received configuration information related to forwarding of data of other UEs, data belonging to other UEs which is received from the gNB successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the data belonging to other UEs.
  • Step 3 The enUE processes the data belonging to other UEs obtained in the step 2 successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to corresponding other UEs via an interface UU2.
  • Step 4 The corresponding other UEs process the received data successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data sent to itselves by the gNB.
  • raw data belonging to other UEs may not be forwarded to other UEs by the enUE. That is, in the step 1, the gNB processes the raw data belonging to other UEs successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then directly transmits the data to other UEs by an interface UU1 or other interfaces; and then, other UEs obtain the data sent to itselves by the gNB according to the step 4.
  • the UE-enhanced mode serves only the control plane data of other UEs, not the user plane data of other UEs;
  • the UE-enhanced mode serves only the uplink transmission direction of other UEs, not the downlink transmission direction of other UEs.
  • the uplink data processing, uplink control signaling processing or downlink control signaling processing between the gNB and other UEs may be implemented in a similar way, and will not be repeated here.
  • a process for processing uplink data between the gNB and other UEs includes the following steps.
  • Step 1 Other UEs process raw data sent to the gNB successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmit the data to the enUE via an interface UU2.
  • Step 2 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, the received data sent to the gNB by other UEs successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the data sent to the gNB by other UEs.
  • Step 3 The enUE processes the data sent to the gNB by other UEs obtained in the step 2 successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to the gNB via an interface UU1.
  • Step 4 The gNB processes the received data successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data sent to the gNB by other UEs.
  • the interface UU1 may perform data transmission via a wired link, or perform data transmission via a wireless link.
  • the interface UU2 performs data transmission via a wireless link.
  • a process for processing a downlink control signaling between the gNB and the enUE includes the following steps.
  • Step 1 The gNB generates a control signaling belonging to the enUE in an RRC layer.
  • Step 2 The gNB processes the control signaling generated in the step 1, successively by the PDCP, RLC, MAC and PHY layers, and then transmits it to the enUE via an interface UU1.
  • Step 3 The enUE processes the signaling received from the gNB successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling belonging to the enUE.
  • a process for processing an uplink control signaling between the gNB and the enUE includes the following steps.
  • Step 1 The enUE generates a control signaling belonging to the enUE in an RRC layer.
  • Step 2 The enUE processes the control signaling generated in the step 1 successively by the PDCP, RLC, MAC and PHY layers, and then transmits the control signaling to the gNB via an interface UU1.
  • Step 3 The gNB processes the signaling received from the enUE successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling sent by the enUE.
  • a process for processing a downlink control signaling between the gNB and other UEs includes the following steps.
  • Step 1 The gNB generates a control signaling belonging to other UEs in an RRC layer.
  • Step 2 The gNB processes the control signaling belonging to other UEs successively by the PDCP, RLC, MAC and PHY layers, and then transmits the control signaling to the enUE via an interface UU1.
  • Step 3 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, the signaling belonging to other UEs which is received from the gNB successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the signaling belonging to other UEs.
  • Step 4 The enUE processes the signaling belonging to other UEs obtained in the step 3 successively by the RRC, PDCP, RLC, MAC and PHY layers, and then transmits the signaling to corresponding other UEs via an interface UU2.
  • Step 5 The corresponding other UEs process the received signaling successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling sent to the corresponding other UEs by the gNB.
  • the control signaling belonging to other UEs may not be forwarded to other UEs by the enUE. That is, in the step 2, the gNB processes the control signaling belonging to other UEs successively by the PDCP, RLC, MAC and PHY layers, and then directly transmits the control signaling to other UEs by an interface UU1 or other interfaces; and then, other UEs obtain the control signaling sent to other UEs by the gNB according to the step 5.
  • the UE-enhanced mode serves only the user plane data of other UEs, not the control plane data of other UEs;
  • the UE-enhanced mode serves only the uplink transmission direction of other UEs, not the downlink transmission direction of other UEs.
  • the control signaling belonging to other UEs may be generated by the enUE (that is, it is not required to generate an RRC signaling for other UEs by the gNB), and then successively processed by the PDCP, RLC, MAC and PHY layers and transmitted to other UEs. Then, the control signaling sent to the UEs may be obtained according to the step 5.
  • a process for processing an uplink control signaling between the gNB and other UEs includes the following steps.
  • Step 1 Other UEs generate a control signaling in an RRC layer.
  • Step 2 Other UEs process the control signaling generated in the step 1 successively by the PDCP, RLC, MAC and PHY layers, and then transmit the control signaling to the gNB via an interface UU2.
  • Step 3 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, the signaling received from other UEs successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the signaling belonging to other UEs.
  • Step 4 The enUE processes the signaling belonging to other UEs obtained in the step 3 successively by the RRC, PDCP, RLC, MAC and PHY layers, and then transmits the signaling to the gNB via an interface UU1.
  • Step 5 The gNB processes the received data successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling sent by other UEs.
  • the control signaling may not be forwarded to the gNB by the enUE. That is, in the step 2, other UEs process the control signaling successively by the PDCP, RLC, MAC and PHY layers, and then directly transmit the control signaling to the gNB via an interface UU1 or other interfaces; and then, the gNB obtains the control signaling sent by other UEs according to the step 5.
  • the UE-enhanced mode serves only the user plane data of other UEs, not the control plane data of other UEs;
  • the UE-enhanced mode serves only the downlink transmission direction of other UEs, not the uplink transmission direction of other UEs.
  • control signaling sent by other UEs may be obtained in the following way: a control signaling is generated by other UEs, then processed by the PDCP, RLC, MAC and PHY layers and transmitted to the enUE, and then processed by the PHY, MAC, RLC, PDCP and RRC layers on the enUE side.
  • the enUE is not required to transmit an RRC signaling of other UEs to the gNB.
  • the interface UU1 may perform data transmission via a wired link, or perform data transmission via a wireless link.
  • the interface UU2 performs data transmission via a wireless link.
  • This embodiment describes a case where the gNB configures an enUE to enter an enhanced mode B0 in order to forward data of other UEs.
  • a cell supported by the gNB is referred to as the first cell, and the communication link between a UE and the gNB in the first cell is referred to as the first link.
  • the enUE After a UE becomes an enUE, the enUE still serve other UEs in the first cell, and a communication link used by the enUE to serve other UEs is referred to as the second link.
  • the gNB may select one UE, and indicate the UE to enter an enhanced mode B0 (i.e., indicate the UE to become an enUE) by using an RRC signaling (for example, RRC RECONFIGURATION) which carries configuration information of a UE-enhanced mode.
  • RRC signaling for example, RRC RECONFIGURATION
  • the gNB may select a UE that will become an enUE according to the information reported by UEs.
  • the information reported by UEs may contain at least one of the following information: channel state information in the first link, location information, movement speed information, UE wireless capability information, information on interference strength of surrounding radio frequency bands, channel state information on one or more carriers between a UE and other UEs, video/audio information of the surrounding, etc.
  • the UE executes this operation and may reply with an RRC signaling (for example, RRC RECONFIGURATION COMPLETE) to notify the gNB of the successive execution of this step.
  • RRC signaling for example, RRC RECONFIGURATION COMPLETE
  • the second link operates in a stand-alone mode, and the enUE transmits a synchronization channel, a broadcast channel or the like necessary for other UEs to access the enUE and receives an access request from other UEs.
  • Other UEs are connected to the enUE by regarding the enUE as the gNB.
  • the second link operates in a non- stand-alone mode, and the gNB may provide auxiliary information for other UEs in the first cell to access the enUE.
  • the enUE communicates, by using a protocol stack which is used when serving other UEs in the enhanced mode configured by the gNB, with other UEs in the second link, and communicates, by using its own UE protocol stack, with the gNB in the first link.
  • the enUE forwards data according to the configuration information of the enhanced mode configured by the gNB.
  • the information on a plane served by a protocol stack used by the UE in the enhanced mode includes both control plane data and user plane data and the data direction in the plane by the protocol stack used by the UE in the enhanced mode includes uplink data and downlink data
  • the enUE forwards uplink control plane data and uplink user plane data from other UEs to the gNB and also forwards downlink control plane data and downlink user plane data from the gNB, which are intended for other UEs, to other UEs.
  • the information on a plane served by a protocol stack used in the UE-enhanced mode in the configuration information may include only one of the control plane data and the user plane data, or the data direction in the plane served by the protocol stack used in the UE-enhanced mode may include only one of the uplink data and the downlink data.
  • the information on a plane served by a protocol stack used in the UE-enhanced mode includes only the user plane data, other UEs exchange the control plane data with the gNB in other ways, for example, other UEs are directly connected to the gNB.
  • This configuration information may further include configuration information related to forwarding of data of other UEs.
  • the configuration information related to forwarding of data of other UEs may be transmitted to the UE by an RRC signaling different from the above RRC signaling.
  • This embodiment describes a case where the gNB indicates an enUE to enter an enhanced mode B3 in order to forward data of other UEs.
  • the gNB may select one UE, and indicate the UE to enter an enhanced mode B3 (i.e., indicate the UE to become an enUE) by using an RRC signaling (for example, RRC RECONFIGURATION) which carries configuration information of a UE-enhanced mode.
  • RRC signaling for example, RRC RECONFIGURATION
  • the UE executes this operation and may reply with an RRC signaling (for example, RRC RECONFIGURATION COMPLETE) to notify the gNB of the successive execution of this step.
  • This configuration information may further include configuration information related to forwarding of data of other UEs.
  • the configuration information related to forwarding of data of other UEs may be transmitted to the UE by an RRC signaling different from the above RRC signaling.
  • the UE After the UE becomes an enUE, it operates in the enhanced mode B3.
  • the enUE forms a second cell as described above, preferably, in this case, the second cell operates in a non- stand-alone mode, and the gNB configures the second cell as the secondary cell for part or all of UEs in the first cell, and activates the second cell on the part or all of other UEs if necessary.
  • the gNB may activate the second cell by transmitting an activation signaling.
  • the first cell and the second cell may be at a same frequency or different frequencies.
  • the gNB shall provide context information (for example, a user ID, information carried by user data, information carried by a user signaling) of the part or all of UEs to the enUE.
  • the enUE communicates with other UEs by using a protocol stack which is used to serve other UEs in the enhanced mode configured by the gNB, and communicates with the gNB by using its own UE protocol stack.
  • the enUE forwards data according to the configuration information of the enhanced mode configured by the gNB.
  • the information on a plane served by a protocol stack used by the UE in the enhanced mode includes both control plane data and user plane data and the data direction in the plane by the protocol stack used by the UE in the enhanced mode includes uplink data and downlink data
  • the enUE forwards uplink control plane data and uplink user plane data from other UEs to the gNB and also forwards downlink control plane data and downlink user plane data from the gNB, which are intended for other UEs, to other UEs.
  • the information on a plane served by a protocol stack used in the UE-enhanced mode in the configuration information may include only one of the control plane data and the user plane data, or the data direction in the plane served by the protocol stack used in the UE-enhanced mode may include only one of the uplink data and the downlink data.
  • the information on a plane served by a protocol stack used in the UE-enhanced mode includes only the user plane data, other UEs exchange the control plane data with the gNB in other ways, for example, other UEs are directly connected to the gNB.
  • Fig. 20 is a schematic diagram of Embodiment 9 of the present disclosure. A process for processing data in the user plane and a process for processing data in the control plane in this embodiment will be described in detail below with reference to Fig. 20.
  • a process for processing downlink data between the gNB and the enUE includes the following steps.
  • Step 1 The gNB processes the raw data belonging to the enUE successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to the enUE via an interface UU1.
  • Step 2 The enUE processes the data received from the gNB successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data belonging to the enUE.
  • a process for processing uplink data between the gNB and the enUE includes the following steps.
  • Step 1 The enUE processes the raw data successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to the gNB via an interface UU1.
  • Step 2 The gNB processes the data received from the enUE successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data sent by the enUE.
  • a process for processing downlink data between the gNB and other UEs includes the following steps.
  • Step 1 The gNB processes raw data belonging to other UEs successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to the enUE via an interface UU1.
  • Step 2 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, data belonging to other UEs which is received from the gNB successively by the PHY, MAC and RLC layers, to obtain the data belonging to other UEs.
  • Step 3 The enUE processes the data belonging to other UEs obtained in the step 2 successively by the RLC, MAC and PHY layers, and then transmits the data to corresponding other UEs via an interface UU2.
  • Step 4 The corresponding other UEs process the received data successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data sent to the corresponding other UEs by the gNB.
  • a process for processing uplink data between the gNB and other UEs includes the following steps.
  • Step 1 Other UEs process raw data sent to the gNB successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmit the data to the enUE via an interface UU2.
  • Step 2 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, the received data sent to the gNB by other UEs successively by the PHY, MAC and RLC layers, to obtain the data sent to the gNB by other UEs.
  • Step 3 The enUE processes the data sent to the gNB by other UEs obtained in the step 2 successively by the RLC, MAC and PHY layers, and then transmits the data to the gNB via an interface UU1.
  • Step 4 The gNB processes the received data successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data sent to the gNB by other UEs.
  • the interface UU1 may perform data transmission via a wired link, or perform data transmission via a wireless link.
  • the interface UU2 performs data transmission via a wireless link.
  • a process for processing a downlink control signaling between the gNB and the enUE includes the following steps.
  • Step 1 The gNB generates a control signaling belonging to the enUE in an RRC layer.
  • Step 2 The gNB processes the control signaling belonging to the enUE, which is generated in the step 1, successively by the PDCP, RLC, MAC and PHY layers, and then transmits the control signaling to the enUE via an interface UU1.
  • Step 3 The enUE processes the signaling received from the gNB successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling belonging to the enUE.
  • a process for processing an uplink control signaling between the gNB and the enUE includes the following steps.
  • Step 1 The enUE generates a control signaling belonging to the enUE in an RRC layer.
  • Step 2 The enUE processes the control signaling generated in the step 1 successively by the PDCP, RLC, MAC and PHY layers, and then transmits the control signaling to the gNB via an interface UU1.
  • Step 3 The gNB processes the signaling received from the enUE successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling sent by the enUE.
  • a process for processing a downlink control signaling between the gNB and other UEs includes the following steps.
  • Step 1 The gNB generates a control signaling belonging to other UEs in an RRC layer.
  • Step 2 The gNB processes the control signaling belonging to other UEs successively by the PDCP, RLC, MAC and PHY layers, and then transmits the control signaling to the enUE via an interface UU1.
  • Step 3 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, the signaling belonging to other UEs which is received from the gNB successively by the PHY, MAC and RLC layers, to obtain the data belonging to other UEs.
  • Step 4 The enUE processes the signaling belonging to other UEs obtained in the step 3 successively by the RLC, MAC and PHY layers, and then transmits the signaling to corresponding other UEs via an interface UU2.
  • Step 5 The corresponding other UEs process the received data successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling sent to the corresponding other UEs by the gNB.
  • the control signaling belonging to other UEs may not be forwarded to other UEs by the enUE. That is, in the step 2, the gNB processes the control signaling belonging to other UEs successively by the PDCP, RLC, MAC and PHY layers, and then directly transmits the control signaling to other UEs by an interface UU1 or other interfaces; and then, other UEs obtain the control signaling sent to other UEs by the gNB according to the step 5.
  • the UE-enhanced mode serves only the user plane data of other UEs, not the control plane data of other UEs;
  • the UE-enhanced mode serves only the uplink transmission direction of other UEs, not the downlink transmission direction of other UEs.
  • a process for processing an uplink control signaling between the gNB and other UEs includes the following steps.
  • Step 1 Other UEs generate a control signaling in an RRC layer.
  • Step 2 Other UEs process the control signaling in the step 1 successively by the PDCP, RLC, MAC and PHY layers, and then transmit the control signaling to the gNB via an interface UU2.
  • Step 3 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, the signaling received from other UEs successively by the PHY, MAC and RLC layers, to obtain the data belonging to other UEs.
  • Step 4 The enUE processes the data belonging to other UEs obtained in the step 3 successively by the RLC, MAC and PHY layers, and then transmits the data to the gNB via an interface UU1.
  • Step 5 The gNB processes the received data successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling sent by other UEs.
  • the control signaling may not be forwarded to the gNB by the enUE. That is, in the step 2, other UEs process the control signaling successively by the PDCP, RLC, MAC and PHY layers, and then directly transmit the control signaling to the gNB via an interface UU1 or other interfaces; and then, the gNB obtains the control signaling sent by other UEs according to the step 5.
  • the UE-enhanced mode serves only the user plane data of other UEs, not the control plane data of other UEs;
  • the UE-enhanced mode serves only the downlink transmission direction of other UEs, not the uplink transmission direction of other UEs.
  • the interface UU1 may perform data transmission via a wired link, or perform data transmission via a wireless link.
  • the interface UU2 performs data transmission via a wireless link.
  • This embodiment describes a case where the gNB indicates an enUE to enter an enhanced mode B6 in order to forward data of other UEs.
  • the gNB may select one UE, and indicate the UE to enter an enhanced mode B6 (i.e., indicate the UE to become an enUE) by using an RRC signaling (for example, RRC RECONFIGURATION) which carries configuration information of a UE-enhanced mode.
  • RRC signaling for example, RRC RECONFIGURATION
  • the UE executes this operation and may reply with an RRC signaling (for example, RRC RECONFIGURATION COMPLETE) to notify the gNB of the successive execution of this step.
  • This configuration information may further include configuration information related to forwarding of data of other UEs.
  • the configuration information related to forwarding of data of other UEs may be transmitted to the UE by an RRC signaling different from the above RRC signaling.
  • the UE After the UE becomes an enUE, the communicates with other UEs by using a protocol stack which is used when serving other UEs in the enhanced mode configured by the gNB, and communicates with the gNB by using its own UE protocol stack.
  • the enUE forwards data according to the configuration information of the enhanced mode configured by the gNB.
  • the information on a plane served by a protocol stack used by the UE in the enhanced mode includes both control plane data and user plane data and the data direction in the plane by the protocol stack used by the UE in the enhanced mode includes uplink data and downlink data
  • the enUE forwards uplink control plane data and uplink user plane data from other UEs to the gNB and also forwards downlink control plane data and downlink user plane data from the gNB, which are intended for other UEs, to other UEs.
  • the information on a plane served by a protocol stack used in the UE-enhanced mode in the configuration information may include only one of the control plane data and the user plane data, or the data direction in the plane served by the protocol stack used in the UE-enhanced mode may include only one of the uplink data and the downlink data.
  • the information on a plane served by a protocol stack used in the UE-enhanced mode includes only the user plane data, and other UEs exchange the control plane data with the gNB in other ways, for example, other UEs are directly connected to the gNB.
  • Fig. 21 is a schematic diagram of Embodiment 10 of the present disclosure.
  • a process for processing downlink data between the gNB and the enUE includes the following steps.
  • Step 1 The gNB processes the raw data belonging to the enUE successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to the enUE via an interface UU1.
  • Step 2 The enUE processes the data received from the gNB successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data belonging to the enUE.
  • a process for processing uplink data between the gNB and the enUE includes the following steps.
  • Step 1 The enUE processes the raw data successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to the gNB via an interface UU1.
  • Step 2 The gNB processes the data received from the enUE successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data sent by the enUE.
  • a process for processing downlink data between the gNB and other UEs includes the following steps.
  • Step 1 The gNB processes raw data belonging to other UEs successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmits the data to the enUE via an interface UU1.
  • Step 2 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, data belonging to other UEs which is received from the gNB successively by the PHY layer and part of the MAC layer (L-MAC), to obtain the data belonging to other UEs.
  • the L-MAC in one embodiment includes a function having a high time delay requirement, for example, HARQ.
  • Step 3 The enUE processes the data belonging to other UEs obtained in the step 2 successively by part of the MAC layer (L-MAC) and the PHY layer, and then transmits the data to corresponding other UEs via an interface UU2.
  • the L-MAC in one embodiment includes a function having a high time delay requirement, for example, HARQ.
  • Step 4 The corresponding other UEs process the received data successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data sent to other UEs by the gNB.
  • a process for processing uplink data between the gNB and other UEs includes the following steps.
  • Step 1 Other UEs process raw data sent to the gNB successively by the SDAP, PDCP, RLC, MAC and PHY layers, and then transmit the data to the enUE via an interface UU2.
  • Step 2 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, the received data sent to the gNB by other UEs successively by the PHY layer and part of the MAC layer (L-MAC), to obtain the data sent to the gNB by other UEs.
  • the L-MAC in one embodiment includes a function having a high time delay requirement, for example, HARQ.
  • Step 3 The enUE processes the data sent to the gNB by other UEs obtained in the step 2 successively by part of the MAC layer (L-MAC) and the PHY layer, and then transmits the data to the gNB via an interface UU1.
  • the L-MAC in one embodiment includes a function having a high time delay requirement, for example, HARQ.
  • Step 4 The gNB processes the received data successively by the PHY, MAC, RLC, PDCP and SDAP layers, to obtain the raw data sent to the gNB by UEs.
  • the interface UU1 may perform data transmission via a wired link, or perform data transmission via a wireless link.
  • the interface UU2 performs data transmission via a wireless link.
  • a process for processing a downlink control signaling between the gNB and the enUE includes the following steps.
  • Step 1 The gNB generates a control signaling belonging to the enUE in an RRC layer.
  • Step 2 The gNB processes the control signaling belonging to the enUE, which is generated in the step 1, successively by the PDCP, RLC, MAC and PHY layers, and then transmits the control signaling to the enUE via an interface UU1.
  • Step 3 The enUE processes the signaling received from the gNB successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling belonging to the enUE.
  • a process for processing an uplink control signaling between the gNB and the enUE includes the following steps.
  • Step 1 The enUE generates a control signaling belonging to the enUE in an RRC layer.
  • Step 2 The enUE processes the control signaling generated in the step 1 successively by the PDCP, RLC, MAC and PHY layers, and then transmits the control signaling to the gNB via an interface UU1.
  • Step 3 The gNB processes the signaling received from the enUE successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling sent by the enUE.
  • a process for processing a downlink control signaling between the gNB and other UEs includes the following steps.
  • Step 1 The gNB generates a control signaling belonging to other UEs in an RRC layer.
  • Step 2 The gNB processes the control signaling belonging to other UEs successively by the PDCP, RLC, MAC and PHY layers, and then transmits the control signaling to the enUE via an interface UU1.
  • Step 3 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, the signaling belonging to other UEs which is received from the gNB successively by the PHY layer and part of the MAC layer (L-MAC), to obtain the data belonging to other UEs.
  • the L-MAC in one embodiment includes a function having a high time delay requirement, for example, HARQ.
  • Step 4 The enUE processes the signaling belonging to other UEs obtained in the step 3 successively by part of the MAC layer (L-MAC) and the PHY layer, and then transmits the signaling to corresponding other UEs via an interface UU2.
  • the L-MAC in one embodiment includes a function having a high time delay requirement, for example, HARQ.
  • Step 5 The corresponding other UEs process the received signaling successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling sent to the corresponding other UEs by the gNB.
  • the control signaling belonging to other UEs may not be forwarded to other UEs by the enUE. That is, in the step 2, the gNB processes the control signaling belonging to other UEs successively by the PDCP, RLC, MAC and PHY layers, and then directly transmits the control signaling to other UEs by an interface UU1 or other interfaces; and then, other UEs obtain the control signaling sent to other UEs by the gNB according to the step 5.
  • the UE-enhanced mode serves only the user plane data of other UEs, not the control plane data of other UEs;
  • the UE-enhanced mode serves only the uplink transmission direction of other UEs, not the downlink transmission direction of other UEs.
  • a process for processing an uplink control signaling between the gNB and other UEs includes the following steps.
  • Step 1 Other UEs generate a control signaling in an RRC layer.
  • Step 2 Other UEs process the control signaling in the step 1 successively by the PDCP, RLC, MAC and PHY layers, and then transmit the control signaling to the gNB via an interface UU2.
  • Step 3 The enUE processes, according to the configuration information related to forwarding of data of other UEs received by the enUE, the signaling received from other UEs successively by the PHY layer and part of the MAC layer (L-MAC), to obtain the signaling belonging to other UEs.
  • L-MAC MAC layer
  • Step 4 The enUE processes the signaling belonging to other UEs obtained in the step 3 successively by part of the MAC layer (L-MAC) and the PHY layer, and then transmits the signaling to the gNB via an interface UU1.
  • L-MAC MAC layer
  • UU1 interface
  • Step 5 The gNB processes the received signaling successively by the PHY, MAC, RLC, PDCP and RRC layers, to obtain the control signaling sent by other UEs.
  • the control signaling may not be forwarded to the gNB by the enUE. That is, in the step 2, other UEs process the control signaling successively by the PDCP, RLC, MAC and PHY layers, and then directly transmit the control signaling to the gNB via an interface UU1 or other interfaces; and then, the gNB obtains the control signaling sent by other UEs according to the step 5.
  • the UE-enhanced mode serves only the user plane data of other UEs, not the control plane data of other UEs;
  • the UE-enhanced mode serves only the downlink transmission direction of other UEs, not the uplink transmission direction of other UEs.
  • the interface UU1 may perform data transmission via a wired link, or perform data transmission via a wireless link.
  • the interface UU2 performs data transmission via a wireless link.
  • the above embodiments 1 to 4 describe data transmission in the user plane and the control plane respectively in cases where the enUE configures protocol stack structures B0, B3 and B6.
  • the data transmission method is similar, which will not be repeated here, except that the protocol stack structure used for processing data of other UEs needs to be processed according to the protocol stack structure used when serving other UEs in the enhanced mode configured by the gNB.
  • Fig. 22 is a schematic diagram of Embodiment 11 of the present disclosure, including the following steps.
  • Step 2201 The gNB selects one UE, and transmits configuration information that indicates the UE to enter an enhanced mode (i.e., indicates the UE to become an enUE) by using an RRC signaling (for example, RRC RECONFIGURATION).
  • This configuration information may further include configuration information related to forwarding of data of other UEs.
  • the configuration information related to forwarding of data of other UEs may be transmitted to the UE by an RRC signaling different from the above RRC signaling.
  • the UE executes this operation and replies with an RRC signaling (for example, RRC RECONFIGURATION COMPLETE) to notify the gNB of the successive execution of this step.
  • RRC signaling for example, RRC RECONFIGURATION COMPLETE
  • Step 2202 The frequency information used by the first link (in this embodiment, the definition of the first link and the second link is the same as that in Embodiment 7) is called a frequency band 1, and the gNB transmits, to the enUE, user plane data intended for other UEs on the frequency band 1.
  • Step 2203 The frequency information used between the gNB and other UEs is called a frequency band 2, and the gNB transmits the scheduling information to other UEs on the frequency band 2. Meanwhile, the enUE acquires the scheduling information from the gNB. Time-frequency resources that may be used for transmitting the user plane data are specified in the scheduling information.
  • Step 2204 The frequency information used by the second link is called a frequency band 3, and the frequency band 3 and the frequency band 2 may be at a same frequency or different frequencies.
  • the enUE transmits the downlink data to other UEs on the frequency band 3 according to the scheduling information from the gNB.
  • Step 2205 The gNB transmits the scheduling information to other UEs on the frequency band 2. Meanwhile, the enUE acquires the scheduling information from the gNB. Time-frequency resources that may be used for transmitting the user plane data are specified in the scheduling information.
  • Step 2206 The enUE receives the uplink data from other UEs on the frequency band 3 according to the scheduling information from the gNB.
  • the frequency band 3 and the frequency band 2 may be at a same frequency or different frequencies.
  • Step 2207 The enUE forwards, on the frequency band 1, the uplink data from other UEs to the gNB.
  • the present disclosure further provides a data forwarding UE, including:
  • a mode switching module configured to enter an enhanced mode according to an indication received from a base station
  • a data forwarding module configured to forward data between a base station and a second UE.
  • the equipment may further include a module configured to receive, from the base station, scheduling information on time-frequency resources of the second UE.
  • the data forwarding module is configured to forward data between the base station and the second UE in the following way: receiving downlink data sent to a second UE from a base station, processing the downlink data layer by layer by a protocol stack structure corresponding to the equipment in the enhanced mode, and forwarding, to the corresponding second UE, the downlink data on the corresponding time-frequency resources according to the scheduling information on the time-frequency resources of the second UE; and/or receiving uplink data sent to a base station from a second UE on corresponding time-frequency resources according to the scheduling information on the time-frequency resources of the second UE, processing the uplink data layer by layer by a protocol stack structure corresponding to the equipment in the enhanced mode, and forwarding the uplink data to the base station.
  • the equipment may further include a module configured to transmit, to the second UE, the scheduling information on the time-frequency resources.
  • the data forwarding module is configured to forward data between the base station and the second UE in the following way: receiving downlink data sent to a second UE from a base station, processing the downlink data layer by layer by a protocol stack structure corresponding to the equipment in the enhanced mode, and forwarding, to the corresponding second UE, the downlink data on the corresponding time-frequency resources according to the scheduling information; and/or receiving uplink data sent to a base station from a second UE on corresponding time-frequency resources according to the scheduling information, processing the uplink data layer by layer by a protocol stack structure corresponding to the equipment in the enhanced mode, and forwarding the uplink data to the base station.
  • the equipment may further include: a module configured to receive access information and cell configuration information from the base station, the access information is used by a second UE to access the UE; and
  • a module configured to transmit the access information and the cell configuration information to the second UE and accept an access request from the second UE.
  • the equipment may further include a module configured to report channel state information of a first link to the base station, the first link being a link between the UE and the base station.
  • the channel state information is used by the base station to select a first UE having a channel condition better than a first set threshold to enter the enhanced mode in order to forward data between a second UE having a channel condition worse than a second set threshold and the base station.
  • the equipment may further include a module configured to report, to the base station, channel state information on at least one carriers between the UE and the second UE on at least one carrier.
  • the equipment further includes a report module configured to report, to the base station, a protocol stack structure information supported by the UE in the enhanced mode.
  • the protocol stack structure supported by the equipment in the enhanced mode at least includes one of the following structures:
  • protocol stack structure B0 including: a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer and a physical (PHY) layer in the control plane, and a Service Data Adaptation Protocol (SDAP) layer, a PDCP layer, an RLC layer, an MAC layer and a PHY layer in the user plane;
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • PHY physical
  • protocol stack structure B1 including: a PDCP layer, an RLC layer, an MAC layer and a PHY layer;
  • protocol stack structure B2 including: part of a PDCP layer, an RLC layer, an MAC layer and a PHY layer;
  • protocol stack structure B3 including: an RLC layer, an MAC layer and a PHY layer;
  • protocol stack structure B4 including: part of an RLC layer, an MAC layer and a PHY layer;
  • protocol stack structure B5 including: an MAC layer and a PHY layer;
  • protocol stack structure B6 including: part of an MAC layer and a PHY layer;
  • protocol stack structure B7 including: a PHY layer;
  • protocol stack structure B8 including: part of a PHY layer.
  • the indication from the base station includes at least one of the following information:
  • information on the indication from the base station may include following combinations:
  • the indication from the base station includes at least one of the following information: a duplex mode used by a second link, a carrier and a bandwidth used by a second link, a physical cell ID of a cell where a second link is located, a maximum transmission power of a first UE in the enhanced mode in a second link, and an operating mode of a second link; and
  • the second link is a link between a first UE in the enhanced mode and a second UE.
  • the UE before forwarding, by the UE, data between the base station and a second UE, the UE further receives, from a base station, configuration information related to forwarding of data of a second UE, the configuration information being used to indicate data to be forwarded.
  • the configuration information related to forwarding of data of a second UE at least includes one of the following information:
  • the present disclosure further provides a data forwarding method on the base station side, including:
  • the method may further include: transmitting, to the first UE, scheduling information on time-frequency resources of the second UE scheduled by a base station.
  • the method may further include: transmitting, to the first UE, cell configuration information and access information used by a second UE to access the first UE; or transmitting, to a second UE, access information used by the second UE to access the first UE.
  • the method may further include: receiving channel state information of a first link reported by the first UE.
  • the transmitting, to a first UE having the capability of supporting an enhanced mode, an indication to enter the enhanced mode includes: selecting, according to channel state information of a first link reported by each UE, a first UE having a channel condition better than a first set threshold, and transmitting, to the first UE having the channel condition better than the first set threshold, an indication to enter an enhanced mode in order to forward data between a second UE having a channel condition worse than a second set threshold and a base station.
  • the indication from the base station includes at least one of the following information:
  • the method may further include: transmitting, by a base station and to a first UE, configuration information related to forwarding of data of a second UE, the configuration information being used to indicate data to be forwarded.
  • the configuration information related to forwarding of data of a second UE at least includes one of the following information:
  • the present disclosure further provides a base station, including:
  • an indicating module configured to transmit, to a first UE having the capability of supporting an enhanced mode, an indication to enter the enhanced mode
  • a forward processing module configured to forward data of a second UE by the first UE.
  • the method may further include: transmitting, to the first UE, scheduling information on time-frequency resources of the second UE scheduled by a base station.
  • the equipment may further include: a module configured to transmit, to the first UE, cell configuration information and access information used by a second UE to access the first UE; or a module configured to transmit, to a second UE, access information used by the second UE to access the first UE.
  • the equipment may further include a module configured to receive channel state information of a first link reported by the first UE.
  • the transmitting, to a first UE having the capability of supporting an enhanced mode, an indication to enter the enhanced mode includes: selecting, according to channel state information of a first link reported by each UE, a first UE having a channel condition better than a first set threshold, and transmitting, to the first UE having the channel condition better than the first set threshold, an indication to enter an enhanced mode in order to forward data between a second UE having a channel condition worse than a second set threshold and a base station.
  • the indication from the base station includes at least one of the following information:
  • the base station may also transmit, to a first UE, configuration information related to forwarding of data of a second UE, the configuration information being used to indicate data to be forwarded.
  • the configuration information related to forwarding of data of a second UE at least includes one of the following information:
  • FIG. 23 illustrates a block diagram detailing an internal structure of a terminal according to an embodiment of the present disclosure.
  • the terminal of the present disclosure may include a terminal processor 2301, a receiver 2302, and a transmitter 2303.
  • the terminal processor 2301 may control a process to operate the terminal according to embodiments of the present disclosure as described above.
  • the terminal operation can be controlled differently according to different numerologies according to embodiments of the present disclosure.
  • the terminal receiver 2302 and the terminal transmitter 2303 may be collectively referred to as a transceiver.
  • the transceiver may transmit/receive a signal to/from the base station and/or other terminals.
  • the transceiver may include an RF transmitter that up-converts and amplifies a frequency of the transmitted signal, an RF receiver that low-noise-amplifies the received signal and down-converts the frequency, or the like.
  • the transceiver may receive a signal through a radio channel and output the received signal to the terminal processor 2301 and transmit the signal output from the terminal processor 2301 through the radio channel.
  • FIG. 24 illustrates a block diagram of an internal structure of the base station according to embodiments of the present disclosure.
  • the base station of the present disclosure may include a base station processor 2401, a receiver 2402, and a transmitter 2403.
  • the structure of the base station illustrated in FIG. 24 may be applied to above described CU and/or DU.
  • the base station processor 2401 may control a process to operate the base station according to some embodiments of the present disclosure as described herein.
  • the base station operation can be controlled differently according to different numerologies.
  • the base station receiver 2402 and the base station transmitter 2403 are collectively referred to as a transceiver.
  • the transceiver may transmit/receive a signal to/from the terminal.
  • the transceiver may include an RF transmitter that up-converts and amplifies a frequency of the transmitted signal, an RF receiver that low-noise-amplifies the received signal and down-converts the frequency, or the like.
  • the transceiver may receive a signal through a radio channel and output the received signal to the base station processor 2401 and transmit the signal output from the base station processor 2401 through the radio channel.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé et un système de communication permettant de faire converger un système de communication de 5ème génération (5G) pour prendre en charge des débits de données supérieurs, au-delà de ceux d'un système de 4ème génération (4G), avec une technologie pour l'Internet des objets (IdO). La présente invention peut être appliquée à des services intelligents basés sur la technologie de communication 5G et sur la technologie associée à l'IdO, tels qu'une maison intelligente, un bâtiment intelligent, une ville intelligente, une voiture intelligente, une voiture connectée, des soins de santé, l'enseignement numérique, le commerce de détail intelligent, et des services de sécurité et de sûreté. La présente invention concerne un procédé de mise en œuvre d'un accès pour un équipement utilisateur (UE). De plus, la présente invention concerne un procédé de transfert de données et un équipement de transfert de données, un équipement utilisateur et une station de base. Grâce aux solutions techniques décrites dans la présente invention, un UE peut aider une station de base à transférer des données d'autres UE.
PCT/KR2018/005290 2017-05-05 2018-05-08 Procédé d'établissement d'une interface fronthaul, procédé de mise en œuvre d'un accès pour un équipement utilisateur, procédé et appareil de mise en œuvre d'un transfert intercellulaire pour un équipement utilisateur, procédé de transfert de données, équipement utilisateur et station de base WO2018203739A1 (fr)

Priority Applications (10)

Application Number Priority Date Filing Date Title
ES18793976T ES2841848T3 (es) 2017-05-05 2018-05-08 Procedimiento para establecer una interfaz de enlace de recorrido frontal y estación base
US16/318,244 US10880789B2 (en) 2017-05-05 2018-05-08 Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
EP20206531.4A EP3796745B1 (fr) 2017-05-05 2018-05-08 Procédés et appareils de réalisation de transfert pour un équipement utilisateur
KR1020217014014A KR102301907B1 (ko) 2017-05-05 2018-05-08 프런트홀 인터페이스 수립 방법, 사용자 장치에 대한 액세스 수행 방법, 사용자 장치에 대한 핸드오버 수행 방법 및 장치, 데이터 전달 방법, 사용자 장치 및 기지국
KR1020187037456A KR102252271B1 (ko) 2017-05-05 2018-05-08 프런트홀 인터페이스 수립 방법, 사용자 장치에 대한 액세스 수행 방법, 사용자 장치에 대한 핸드오버 수행 방법 및 장치, 데이터 전달 방법, 사용자 장치 및 기지국
EP21190384.4A EP3927107B1 (fr) 2017-05-05 2018-05-08 Procédé d'établissement d'une interface frontale et station de base
EP18793976.4A EP3479647B1 (fr) 2017-05-05 2018-05-08 Procédé d'établissement d'une interface fronthaul et station de base
US16/250,519 US10880799B2 (en) 2017-05-05 2019-01-17 Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
US17/128,964 US11546811B2 (en) 2017-05-05 2020-12-21 Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
US17/128,921 US11477703B2 (en) 2017-05-05 2020-12-21 Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN201710313812.5 2017-05-05
CN201710313812 2017-05-05
CN201710458428.4A CN109246747B (zh) 2017-05-05 2017-06-16 前向接口的建立方法、ue接入方法、ue切换方法及装置
CN201710458428.4 2017-06-16
CN201810010479.5A CN110012480A (zh) 2018-01-05 2018-01-05 数据转发方法、用户设备和基站
CN201810010479.5 2018-01-05

Related Child Applications (3)

Application Number Title Priority Date Filing Date
US16/318,244 A-371-Of-International US10880789B2 (en) 2017-05-05 2018-05-08 Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
US16/250,519 Continuation US10880799B2 (en) 2017-05-05 2019-01-17 Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
US17/128,921 Continuation US11477703B2 (en) 2017-05-05 2020-12-21 Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station

Publications (1)

Publication Number Publication Date
WO2018203739A1 true WO2018203739A1 (fr) 2018-11-08

Family

ID=64016170

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/005290 WO2018203739A1 (fr) 2017-05-05 2018-05-08 Procédé d'établissement d'une interface fronthaul, procédé de mise en œuvre d'un accès pour un équipement utilisateur, procédé et appareil de mise en œuvre d'un transfert intercellulaire pour un équipement utilisateur, procédé de transfert de données, équipement utilisateur et station de base

Country Status (2)

Country Link
ES (1) ES2886519T3 (fr)
WO (1) WO2018203739A1 (fr)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536331A (zh) * 2019-01-29 2019-12-03 中兴通讯股份有限公司 一种非公众网络的配置方法、装置、cu、du和基站
GB2577854A (en) * 2018-06-22 2020-04-15 Nec Corp Communication system
CN111182651A (zh) * 2018-11-09 2020-05-19 中国移动通信有限公司研究院 一种信息生成及数据传输方法、装置和存储介质
WO2020159168A1 (fr) * 2019-01-28 2020-08-06 Samsung Electronics Co., Ltd. Procédé de réplication de données, procédé de comptage de données, entités et supports correspondants
CN112867153A (zh) * 2020-12-30 2021-05-28 中电科仪器仪表(安徽)有限公司 一种5g终端模拟器中协议栈rrc消息解码方法
WO2022086233A1 (fr) * 2020-10-21 2022-04-28 Samsung Electronics Co., Ltd. Procédé et dispositif de transmission de multidiffusion
WO2022086217A1 (fr) * 2020-10-21 2022-04-28 Samsung Electronics Co., Ltd. Nœuds, équipements utilisateur et procédés associés
WO2023069669A1 (fr) * 2021-10-21 2023-04-27 Google Llc Gestion de configurations pour des communications multidiffusions et monodiffusions
WO2023219314A1 (fr) * 2022-05-07 2023-11-16 Samsung Electronics Co., Ltd. Procédé et système de conception de porteuse radio de signalisation et de gestion de l'émission et de la réception de données de plan de commande
US11924791B2 (en) 2019-02-15 2024-03-05 Sony Group Corporation User equipment, centralized unit device, wireless communication method and storage medium

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017010693A1 (fr) * 2015-05-15 2017-01-19 주식회사 케이티 Procédé de configuration de connexion sans fil de terminal et appareil associé

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017010693A1 (fr) * 2015-05-15 2017-01-19 주식회사 케이티 Procédé de configuration de connexion sans fil de terminal et appareil associé

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"CU -DU interface: overall categorization of C-plane and U-plane", R3-170618, 3GPP TSG RAN WG3 MEETING #95, 7 February 2017 (2017-02-07), Athens, Greece, XP051213198 *
"Transmission of RRC message via CU -DU interface", R3-170405, 3GPP TSG RAN WG3 MEETING #95, 7 February 2017 (2017-02-07), Athens, Greece, XP051224253 *
ERICSSON: "CU -DU interface functions", R3-171163, 3GPP TSG RAN WG3 MEETING #95BIS, 25 March 2017 (2017-03-25), Spokane, USA, XP051255540 *
ZTE: "Discussion on CU -DU interface control plane functions", R3-171019, 3GPP TSG RAN WG3 MEETING #95BIS, 24 March 2017 (2017-03-24), Spokane, USA, XP051255362 *

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11546810B2 (en) 2018-06-22 2023-01-03 Nec Corporation Obtaining distributed unit's configuration information by a central unit of a base station
GB2577854A (en) * 2018-06-22 2020-04-15 Nec Corp Communication system
CN111182651A (zh) * 2018-11-09 2020-05-19 中国移动通信有限公司研究院 一种信息生成及数据传输方法、装置和存储介质
CN111182651B (zh) * 2018-11-09 2021-11-16 中国移动通信有限公司研究院 一种信息生成及数据传输方法、装置和存储介质
WO2020159168A1 (fr) * 2019-01-28 2020-08-06 Samsung Electronics Co., Ltd. Procédé de réplication de données, procédé de comptage de données, entités et supports correspondants
CN110536331A (zh) * 2019-01-29 2019-12-03 中兴通讯股份有限公司 一种非公众网络的配置方法、装置、cu、du和基站
CN110536331B (zh) * 2019-01-29 2023-09-12 中兴通讯股份有限公司 一种非公众网络的配置方法、装置、cu、du和基站
US11924791B2 (en) 2019-02-15 2024-03-05 Sony Group Corporation User equipment, centralized unit device, wireless communication method and storage medium
WO2022086233A1 (fr) * 2020-10-21 2022-04-28 Samsung Electronics Co., Ltd. Procédé et dispositif de transmission de multidiffusion
WO2022086217A1 (fr) * 2020-10-21 2022-04-28 Samsung Electronics Co., Ltd. Nœuds, équipements utilisateur et procédés associés
CN112867153B (zh) * 2020-12-30 2023-01-17 中电科思仪科技(安徽)有限公司 一种5g终端模拟器中协议栈rrc消息解码方法
CN112867153A (zh) * 2020-12-30 2021-05-28 中电科仪器仪表(安徽)有限公司 一种5g终端模拟器中协议栈rrc消息解码方法
WO2023069669A1 (fr) * 2021-10-21 2023-04-27 Google Llc Gestion de configurations pour des communications multidiffusions et monodiffusions
WO2023219314A1 (fr) * 2022-05-07 2023-11-16 Samsung Electronics Co., Ltd. Procédé et système de conception de porteuse radio de signalisation et de gestion de l'émission et de la réception de données de plan de commande

Also Published As

Publication number Publication date
ES2886519T3 (es) 2021-12-20

Similar Documents

Publication Publication Date Title
EP3479647A1 (fr) Procédé d'établissement d'une interface fronthaul, procédé de mise en uvre d'un accès pour un équipement utilisateur, procédé et appareil de mise en uvre d'un transfert intercellulaire pour un équipement utilisateur, procédé de transfert de données, équipement utilisateur et station de base
WO2018203739A1 (fr) Procédé d'établissement d'une interface fronthaul, procédé de mise en œuvre d'un accès pour un équipement utilisateur, procédé et appareil de mise en œuvre d'un transfert intercellulaire pour un équipement utilisateur, procédé de transfert de données, équipement utilisateur et station de base
WO2018203736A1 (fr) Système, procédé de transmission de données et équipement de réseau prenant en charge un procédé de fonction de duplication pdcp et dispositif de transfert d'informations de configuration de porteuse de liaison montante supplémentaire et procédé et dispositif de réalisation d'ajustement de mobilité de connexion
WO2019031915A1 (fr) Procédé et dispositif d'établissement de connectivité double
WO2020166895A1 (fr) Procédé et appareil de prise en charge d'un regroupement de porteuses dans un système de communications sans fil
WO2019031901A1 (fr) Procédé et dispositif pour exploiter et commander un flux de données
WO2020167007A1 (fr) Procédé et appareil pour effectuer une procédure de capacité d'équipement utilisateur pour prendre en charge une communication de véhicule dans un système de communication mobile de prochaine génération
WO2020122676A1 (fr) Appareil et procédé pour un accès initial dans un système de communication sans fil
WO2020197361A1 (fr) Procédé et appareil de transfert sans interruption de transmission et de réception de données dans un système de communication mobile de prochaine génération
WO2018128494A1 (fr) Procédé de transfert sur réseau d'accès radio, station de base et procédé de communication de la station de base
WO2019031941A1 (fr) Procédé permettant de prendre en charge un transfert intercellulaire et appareil correspondant
WO2020222499A1 (fr) Procédé et dispositif permettant de gérer des informations dans un système de communication sans fil
WO2021060941A1 (fr) Procédé et appareil de transfert
WO2015020356A1 (fr) Procédé de transmission d'un rapport d'état de tampon dans une communication entre dispositifs et dispositif associé
WO2020166906A1 (fr) Procédés et appareils pour transmettre et recevoir des données dans un système de communication sans fil
WO2019066573A1 (fr) Procédé et dispositif d'accès au réseau
WO2020060245A1 (fr) Procédé et appareil pour identifier la clé de sécurité dans un système de communication mobile de nouvelle génération
WO2020067715A1 (fr) Procédé et dispositif pour configurer un nœud en vue de la transmission et de la réception de données
WO2018231035A1 (fr) Procédé et dispositif de commutation d'une cellule de desserte et procédé et dispositif prenant en charge un message d'information de système à la demande
EP3616434A1 (fr) Système, procédé de transmission de données et équipement de réseau prenant en charge un procédé de fonction de duplication pdcp et dispositif de transfert d'informations de configuration de porteuse de liaison montante supplémentaire et procédé et dispositif de réalisation d'ajustement de mobilité de connexion
WO2020197368A1 (fr) Procédé et dispositif de support à la communication de véhicule dans un système de communication sans fil
WO2018030826A1 (fr) Procédé de commande d'un équipement d'utilisateur
WO2022015109A1 (fr) Procédé et nœud de communication dans un système de communication prenant en charge un accès et une liaison terrestre intégrés (iab)
EP3485695A1 (fr) Procédé de commande d'un équipement d'utilisateur
WO2021242035A1 (fr) Procédé et dispositif de prise en charge d'un transfert intercellulaire

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18793976

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20187037456

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018793976

Country of ref document: EP

Effective date: 20190131

NENP Non-entry into the national phase

Ref country code: DE