WO2021218787A1 - 远端终端的连接管理方法、终端及网络侧设备 - Google Patents

远端终端的连接管理方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2021218787A1
WO2021218787A1 PCT/CN2021/089119 CN2021089119W WO2021218787A1 WO 2021218787 A1 WO2021218787 A1 WO 2021218787A1 CN 2021089119 W CN2021089119 W CN 2021089119W WO 2021218787 A1 WO2021218787 A1 WO 2021218787A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay
terminal
signaling
remote terminal
rlc
Prior art date
Application number
PCT/CN2021/089119
Other languages
English (en)
French (fr)
Inventor
刘佳敏
Original Assignee
维沃移动通信有限公司
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
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to EP21795276.1A priority Critical patent/EP4145863A4/en
Priority to BR112022021139A priority patent/BR112022021139A2/pt
Priority to MX2022013394A priority patent/MX2022013394A/es
Priority to KR1020227040073A priority patent/KR20230002793A/ko
Priority to JP2022565856A priority patent/JP2023523071A/ja
Priority to AU2021265968A priority patent/AU2021265968B2/en
Publication of WO2021218787A1 publication Critical patent/WO2021218787A1/zh
Priority to US17/958,297 priority patent/US20230023135A1/en

Links

Images

Classifications

    • 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/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the embodiments of the present invention relate to the field of communication technology, and in particular to a connection management method of a remote terminal, a terminal, and a network side device.
  • LTE Long Term Evolution
  • UE User Equipment
  • LTE sidelink is suitable for specific public safety affairs (such as emergency communication in fire sites or disaster sites such as earthquakes), or vehicle to everything (V2X) communications.
  • IoV communications include various services, such as basic safety communications, advanced (autonomous) driving, formation, sensor expansion, and so on. Since LTE sidelink only supports broadcast communications, it is mainly used for basic security communications. Other advanced V2X services that have strict Quality of Service (QoS) requirements in terms of delay and reliability will pass through the New Radio (New Radio, NR) sidelink support.
  • QoS Quality of Service
  • 5 th Generation, 5G NR system may be used above 6GHz operating band is not supported by LTE, supports larger operating bandwidth, but the current version of the NR system only supports an interface between the base station and the terminal, the terminal is not yet supported Sidelink interface for direct communication between.
  • the Sidelink interface can also be called the PC5 interface.
  • the remote UE passes through the sidelink link with the relay UE, and the relay UE forwards its data to the base station.
  • data is transmitted between the remote UE and the base station, and the relay UE plays the role of data transfer.
  • the embodiments of the present invention provide a connection management method for a remote terminal, a terminal, and a network side device, which are used to solve the problem that the remote terminal cannot establish a normal connection with the network side device under the sidelink relay architecture, resulting in the inability to establish a service and Transmission problem.
  • the present invention is implemented as follows:
  • an embodiment of the present invention provides a connection management method for a remote terminal, which is applied to a relay terminal, and the method includes:
  • Receive first configuration information sent by the network-side device where the first configuration information includes: configuration information carried by a first Uu radio link control (Radio Link Control, RLC), and the first Uu RLC bearer is used for transmission Uu signaling of the remote terminal.
  • RLC Radio Link Control
  • an embodiment of the present invention provides a connection management method for a remote terminal, which is applied to a remote terminal, and the method includes:
  • the Uu signaling of the remote terminal is transmitted through the first sidelink RLC bearer established with the relay terminal, or through a sidelink radio resource control (Radio Resource Control, RRC) message.
  • RRC Radio Resource Control
  • an embodiment of the present invention provides a connection management method for a remote terminal, which is applied to a network side device, and the method includes:
  • first configuration information is sent to the relay terminal, where the first configuration information includes: configuration information of a first Uu RLC bearer, and the first U RLC bearer is used to transmit the Uu signaling of the remote terminal.
  • an embodiment of the present invention provides a terminal, including:
  • the first sending module is configured to send a first relay request to the network side device, where the first relay request is used to request the network side device to perform configuration related to the relay function;
  • the first receiving module is configured to receive first configuration information sent by the network-side device according to the first relay request, where the first relay request is used to request the network-side device to perform relay function-related configuration .
  • an embodiment of the present invention provides a terminal, including:
  • the transmission module is used to transmit the Uu signaling of the remote terminal through the first sidelink RLC bearer established with the relay terminal, or through the RRC message.
  • an embodiment of the present invention provides a network side device, including:
  • the first receiving module is configured to receive a first relay request sent by a relay terminal, where the first relay request is used to request the network side device to perform configuration related to the relay function;
  • the first sending module is configured to send first configuration information to the relay terminal according to the first relay request, where the first configuration information includes: configuration information carried by a first Uu RLC, and the first Uu
  • the RLC bearer is used to transmit Uu signaling of the remote terminal.
  • an embodiment of the present invention provides a terminal including a processor, a memory, and a program or instruction stored on the memory and capable of running on the processor, and the program or instruction is executed by the processor. When executed, the steps of the connection management method applied to the remote terminal of the first aspect are realized.
  • an embodiment of the present invention provides a terminal, including a processor, a memory, and a program or instruction stored on the memory and capable of running on the processor, and the program or instruction is executed by the processor. When executed, the steps of the connection management method applied to the second aspect are realized.
  • an embodiment of the present invention provides a network-side device, including a processor, a memory, and a program or instruction stored on the memory and capable of running on the processor.
  • the program or instruction is When the processor executes, the steps of the connection management method of the remote terminal of the third aspect described above are implemented.
  • an embodiment of the present invention provides a readable storage medium, the readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the connection of the remote terminal of the first aspect is realized.
  • the steps of the management method; or, when the program or instruction is executed by the processor, the steps of the remote terminal connection management method of the second aspect are implemented; or, the program or instruction is executed by the processor to implement the third aspect.
  • an embodiment of the present invention provides a chip that includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or an instruction to implement the first Or, implement the steps of the remote terminal connection management method of the second aspect described above; or implement the steps of the remote terminal connection management method of the third aspect described above.
  • an embodiment of the present invention provides a computer software product, the computer software product is stored in a non-volatile storage medium, and the software product is configured to be executed by at least one processor to implement the aforementioned first
  • the Uu RLC bearer between the relay terminal and the network side device is configured to transmit Uu signaling dedicated to the remote terminal, thereby realizing the establishment of the connection between the remote terminal and the network side device. In order to carry out the normal transmission of the business.
  • FIG. 1 and 2 are schematic diagrams of the architecture of a wireless communication system provided by an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a connection management method for a remote terminal according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a connection management method for a remote terminal according to another embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a connection management method for a remote terminal according to another embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a connection management method for a remote terminal according to still another embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a terminal according to another embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a network side device according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of the hardware structure of a terminal according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a terminal according to another embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a terminal according to another embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of a network side device according to another embodiment of the present invention.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present invention should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner.
  • connection management method, terminal, and network side device of the remote terminal provided by the embodiment of the present invention can be applied to a wireless communication system.
  • the wireless communication system may adopt a 5G system, or an evolved Long Term Evolution (eLTE) system, or a subsequent evolved communication system.
  • eLTE evolved Long Term Evolution
  • the wireless communication system may include: a network-side device 11 and a plurality of terminals 12.
  • the terminal 12 may also directly connect to other terminals through a sidelink interface. 12Connect.
  • the network-side device 11 provided by the embodiment of the present invention may be a base station, which may be a commonly used base station, an evolved node base station (eNB), or a network-side device in a 5G system (for example, Next generation base station (next generation node base station, gNB) or transmission and reception point (transmission and reception point, TRP)) or cell and other equipment. Or the network side device in the subsequent evolution communication system.
  • a base station which may be a commonly used base station, an evolved node base station (eNB), or a network-side device in a 5G system (for example, Next generation base station (next generation node base station, gNB) or transmission and reception point (transmission and reception point, TRP)) or cell and other equipment.
  • gNB Next generation base station
  • TRP transmission and reception point
  • the terminal 12 provided in the embodiment of the present invention may be a mobile phone, a tablet computer, a notebook computer, an Ultra-Mobile Personal Computer (UMPC), a netbook, or a Personal Digital Assistant (PDA), etc.
  • UMPC Ultra-Mobile Personal Computer
  • PDA Personal Digital Assistant
  • FIG. 3 is a schematic flowchart of a connection management method for a remote terminal according to an embodiment of the present invention. The method is applied to a relay terminal and includes:
  • Step 31 Send a first relay request to the network side device, where the first relay request is used to request the network side device to perform configuration related to the relay function;
  • Uu RLC bearer refers to the bearer of the RLC and its lower layers in the protocol stack of the Uu interface, and does not include the upper layer of the RLC.
  • the configuration information carried by the first Uu RLC includes at least one of the following: RLC configuration, and, Medium Access Control (MAC) configuration
  • the MAC configuration includes at least one of the following: logical channel Identifier (ID), logical channel priority and priority bit rate (Prioritized Bit Rate, PBR).
  • ID logical channel Identifier
  • PBR Primary Bit Rate
  • the first Uu RLC bearer is a Uu SRB RLC bearer or a Uu DRB RLC bearer.
  • Step 32 Receive first configuration information sent by the network-side device, where the first configuration information includes: configuration information carried by a first Uu RLC, and the first Uu RLC bearer is used to transmit the Uu of the remote terminal Signaling.
  • the relay terminal sends a relay request to the network side device to request to configure the Uu RLC bearer between the network side device and the relay terminal to be dedicated to the transmission of Uu signaling of the remote terminal, thereby realizing remote
  • the connection between the end terminal and the network side device is established for normal service transmission.
  • the Uu signaling of the remote terminal includes the uplink Uu signaling that the remote terminal sends to the network side, and/or the downlink Uu that the network side device sends to the remote terminal Signaling.
  • connection management method of the remote terminal may further include:
  • Receive the uplink Uu signaling of the remote terminal and forward the uplink Uu signaling to the network side device on the first Uu RLC bearer, and/or, receive the network side device on the first Uu RLC bearer
  • the sent downlink Uu signaling of the remote terminal is forwarded to the remote terminal, so as to realize the transmission of the Uu signaling of the remote terminal.
  • the uplink Uu signaling and the downlink Uu signaling may be carried out in different directions carried by the same Uu RLC, and are executed by a two-way acknowledged mode (Acknowledged Mode, AM) RLC entity.
  • AM Acknowledged Mode
  • the relay terminal may not send the Uu signaling of the remote terminal through the Uu RLC bearer, but instead carry the Uu signaling of the remote terminal in the form of a container.
  • the RRC message is transmitted to the network side device.
  • the RRC message may carry at least one of the following information: the identifier of the remote terminal, and indication information of the type of Uu signaling of the remote terminal.
  • the type of Uu signaling includes the following At least one item: Radio Resource Control (RRC) signaling and Non Access Stratum (NAS) signaling.
  • RRC Radio Resource Control
  • NAS Non Access Stratum
  • the number of remote terminals connected to the relay terminal may be one or multiple. If the number of remote terminals is greater than one, optionally, different remote terminals.
  • the Uu signaling of the terminal is transmitted using different first Uu RLC bearers; or, the Uu signaling of different remote terminals is transmitted using the same first Uu RLC bearer.
  • an indication information is carried in the Uu signaling, or sent together with the Uu signaling (for example, carried in the header of the Layer 2 Protocol Data Unit (PDU))
  • the indication information is used to indicate the identity of the remote terminal, for example, the identity of the remote terminal.
  • whether to carry or send the indication information is configured by the network side device.
  • the type of Uu signaling of the remote terminal may be one or multiple.
  • the Uu signaling of the remote terminal includes: radio resource control (RRC) signaling and non-radio resource control (RRC) signaling.
  • RRC radio resource control
  • RRC non-radio resource control
  • Access layer Non Access Stratum, NAS
  • the U RRC signaling of the remote terminal refers to the RRC signaling between the remote terminal and the network side device
  • the U NAS signaling of the remote terminal refers to the remote terminal and its core network.
  • the NAS signaling between node access and mobility management function (Access and Mobility Management Function, AMF) is end-to-end and is directly transmitted between two endpoints.
  • AMF Access and Mobility Management Function
  • SRB activates encryption and integrity protection.
  • different types of Uu signaling of the same remote terminal use the same first Uu RLC bearer transmission; or, different types of Uu signaling of the same remote terminal use different The first Uu RLC bearer transmission.
  • an indication information is carried in the Uu signaling, or sent together with the Uu signaling (for example, carried in the header of a layer 2 protocol data unit (PDU)), the indication The information is used to indicate the type of Uu signaling service.
  • whether to carry or send the indication information is configured by the network side device.
  • the first relay request includes at least one of the following information: relay indication information, where the relay indication information is used to indicate that the current message is the first relay request ; The identifier of the remote terminal; the service information of the remote terminal; relay information.
  • the service information includes at least one of the following:
  • QFI QoS flow ID
  • the QoS profile includes at least one of the following: service delay budget (packet delay budget, PDB), packet error rate (PER), priority (priority), service type (such as Guaranteed bit rate (Guaranteed bit rate, GBR), non-GBR, delayCriticalGBR, etc.), average window size (AveragingWindow), maximum data burst volume (MaxDataBurstVolume);
  • QoS parameters or QoS indicators can also be replaced by standardized QoS indicators, that is, with standardized QoS indicators, the corresponding QoS profile parameter values can be found in the specification table;
  • Maximum flow bit rate (Maximum flow bit rate, MBR/MFBR);
  • Guaranteed flow bit rate Guaranteed flow bit rate (Guaranteed flow bit rate, GBR/GFBR).
  • the relay terminal can obtain the service information that the remote terminal is about to send through the relay function through an interaction process with the remote terminal (for example, a discovery process or a connection establishment process).
  • the relay terminal when the relay terminal reports the service information of the remote terminal to the network side device, it can optionally also carry the identifier of the remote terminal at the same time, so that the network side device can distinguish which remote terminal the service information belongs to Business information, so as to provide better configuration.
  • the relay information includes at least one of the following:
  • the relay terminal needs to enter the RRC connection state first, because only the RRC connection state can transfer data and provide relay service functions for the remote terminal.
  • the relay terminal can send the first relay request to the network side during the process of entering the RRC connection state, or after the RRC connection is successfully established, send the first relay request to the network side in a special signaling process, which is feasible
  • the plan is as follows:
  • the first relay request is carried in the RRC connection establishment request sent to the network side device.
  • relay indication information can be carried, for example, carried by a 1-bit cause value, which is used to indicate that the current message is the first A relay request.
  • the first relay request is carried in the completion of the RRC connection establishment sent to the network side device.
  • the capacity of the RRC connection establishment is not limited, and a relay field can be carried. If the relay field is True, it means that this is an initiation for the relay function.
  • the connection is established, False means that this is a connection establishment of an ordinary terminal, that is, the relevant configuration of the relay function is requested from the network side by setting a special domain.
  • it may also carry at least one of the following: the identifier of the remote terminal, the service information of the remote terminal, and so on. The identifier of the remote terminal is used to indicate for which terminal the relay operation is requested.
  • the first uplink signaling is used to send the first relay request.
  • the first uplink signaling may be a multiplexed existing uplink signaling or a new uplink signaling .
  • Reusing existing uplink signaling may use existing sidelink UE Information (SidelinkUEInformation) signaling or UE Assistance Information (UEAssistanceInformation), and the new signaling may be, for example, Relay Information (RelayInformation).
  • the capacity of the first uplink signaling is not limited, and may carry specific relay information (relay info), and request the relevant configuration of the relay function from the network side.
  • the relay information includes at least one of the following: relay indication information, an identifier of the remote terminal, and service information of the remote terminal.
  • Carrying the service information of the remote terminal, the relevant configuration for requesting a complete relay function can be entered to the network side, for example, a Uu data radio bearer (Data Radio Bearer, DRB) RLC bearer that requests service data at the same time.
  • DRB Data Radio Bearer
  • a small amount of relay information may also be carried in 1) or 2) first, for example, to inform the network-side equipment that the relay terminal enters the RRC connection state for the relay function.
  • the relay information for example, can carry special values (such as relay indicator information) through the cause value, or set the 1bit relay field to True, or carry the UE identity of the remote terminal , It is convenient for the network side to carry out basic relay function signaling bearer or default data bearer configuration; subsequent special signaling procedures are used to report detailed specific information of the service that needs to be relayed, and request service data-related configuration from the network side.
  • the relay terminal needs to enter the RRC connection state first, because only the RRC connection state can transfer data and provide relay service functions for the remote terminal.
  • the relay terminal can send the first relay request to the network side during the process of entering the RRC connection state, or after the RRC connection is successfully established, send the first relay request to the network side in a special signaling process, which is feasible
  • the plan is as follows:
  • the first relay request is carried in the RRC connection recovery request sent to the network side device.
  • relay indicator information can be carried, for example, carried by a 1-bit cause value, which is used to indicate that the current message is the first relay request .
  • the capacity of the RRC connection recovery is not limited, and a relay field can be carried.
  • the relay field is True, which means it is an initiation for the relay function.
  • the connection is established, False means that this is a connection establishment of an ordinary terminal, that is, the relevant configuration of the relay function is requested from the network side by setting a special domain.
  • it may also carry at least one of the following: the identifier of the remote terminal, the service information of the remote terminal, and so on.
  • the identifier of the remote terminal is used to indicate for which terminal the relay operation is requested.
  • the first uplink signaling is used to send the first relay request.
  • the first uplink signaling may be multiplexed existing uplink signaling or new uplink signaling .
  • Reusing existing uplink signaling may use existing sidelink UE Information (SidelinkUEInformation) signaling or UE Assistance Information (UEAssistanceInformation), and the new signaling may be, for example, Relay Information (RelayInformation).
  • the capacity of the first uplink signaling is not limited, and may carry specific relay information (relay info), and request the relevant configuration of the relay function from the network side.
  • the relay information includes at least one of the following: relay indication information, an identifier of the remote terminal, and service information of the remote terminal. Carrying the service information of the remote terminal, the relevant configuration for requesting a complete relay function can be entered to the network side, for example, a Uu DRB RLC bearer that requests service data at the same time.
  • a small amount of relay information may also be carried in 1) or 2) first, for example, to inform the network-side equipment that the relay terminal enters the RRC connection state for the relay function,
  • the relay information may carry a special value (such as a relay indicator) through the cause value, or the 1bit relay field may be set to True, or the UE identity of the remote terminal may be carried. It is convenient for the network side to carry out basic relay function signaling bearer or default data bearer configuration; subsequent special signaling procedures are used to report detailed specific information of the service that needs to be relayed, and request service data-related configuration from the network side.
  • the relay terminal can use the first uplink signaling to send the first relay request.
  • the feasible solutions are as follows:
  • the relay terminal requests detailed related configuration information from the network side in a one-step manner; the configuration includes both signaling bearer information and data bearer information; in order to obtain all information at one time, it is preferable to:
  • the relay indication information and the remote terminal's identification, detailed service information, and detailed relay information need to be reported to the network side.
  • the relay indication is used to indicate that this is a report related to the relay function.
  • the relay terminal In a two-step manner, the relay terminal first requests the network side to establish the configuration information of the signaling bearer related signaling, and can also request the configuration information of the default data bearer at the same time.
  • the second step is to send the network to the network again
  • the side requests dedicated data bearer information for data transmission; if the request is divided into two steps, the report information in the first step can be relatively rough, for example, it only contains the relay indication and the identification of the remote terminal, which is used to explain that this is a basic relay configuration Request, the second step is to report detailed service information and detailed relay information to the network side.
  • the first uplink signaling may be multiplexed existing uplink signaling, or may be new uplink signaling.
  • Reusing existing uplink signaling may use existing sidelink UE Information (SidelinkUEInformation) signaling or UE Assistance Information (UEAssistanceInformation), and the new signaling may be, for example, Relay Information (RelayInformation).
  • the capacity of the first uplink signaling is not limited, and may carry specific relay information (relay info), and request the relevant configuration of the relay function from the network side.
  • the relay information includes at least one of the following: relay indication information, an identifier of the remote terminal, and service information of the remote terminal. Carrying the service information of the remote terminal, the relevant configuration for requesting a complete relay function can be entered to the network side, for example, a Uu DRB RLC bearer that requests service data at the same time.
  • the two ends are the remote terminal and the network side equipment (serving cell/base station).
  • the transmission path is the uplink Uu signaling from the remote terminal to the relay terminal through the PC5 interface first, and then by The Uu interface of the relay terminal is connected to the network side equipment, and the transmission process of the downlink Uu signaling is the other way around. That is to say, the Uu signaling of the remote terminal needs to be transmitted through two sections of air interfaces, and corresponding pipes need to be configured for bearer on the two sections of air interfaces.
  • the Uu interface refers to the interface between the relay terminal and the network side device (serving cell/base station).
  • the PC5 interface refers to the sidelink interface between the remote terminal and the relay terminal.
  • the PC5 interface refers to the communication interface between the relay terminal and the remote terminal using the sidelink protocol.
  • the network side device before sending the first relay request to the network side device, it further includes: a discovery process and/or a connection establishment process (Relay related) related to the relay between the remote terminal. discovery/link establishment).
  • a discovery process and/or a connection establishment process (Relay related) related to the relay between the remote terminal. discovery/link establishment).
  • the discovery process and/or connection establishment process related to the relay can be performed.
  • the authorization process of the relay function is controlled by the core network, and may be an authorization and relay information acquisition process performed by the remote terminal and/or the relay terminal with the network side when the remote terminal and/or the relay terminal are connected to the network. It can also be that the remote terminal is pre-configured to obtain authorization and relay information.
  • the network side can also use System Information Block (SIB), dedicated signaling or pre-configuration information to configure the remote terminal and/or the relay terminal to perform the relay operation conditions (for example, The relay terminal needs to be a terminal whose signal strength exceeds a preset threshold). After each meets the conditions for the relay operation, the remote terminal and the relay terminal can perform a relay-related discovery process and/or a connection establishment process.
  • SIB System Information Block
  • the discovery process and/or the connection establishment process are completed using the PC5 link signaling process, and further optionally, the discovery process and/or the connection establishment process uses the PC5 link signaling wireless Bearer (SRB) is performed.
  • SRB PC5 link signaling wireless Bearer
  • the relay-related discovery process and/or connection establishment process can be two processes, or can be combined into one process.
  • the two processes are the mutual discovery process between the remote terminal and the relay terminal, and then the connection establishment process.
  • One process is the process of establishing a connection between the remote terminal and the relay terminal directly. No matter which process it is, it is completed using the SRB of the PC5 link.
  • SRB0 used for the broadcast address PC5-S signaling transmission without security, such as direct communication request (direct communication request);
  • SRB1 used to initiate secure PC5-S signaling transmission, such as Security establishment/complete (security establishment/complete);
  • SRB2 Used to transmit PC5-S signaling after security is started, such as heartbeat packets, etc.;
  • SRB3 Used to transmit PC5-RRC signaling after security is started, such as capability information, reconfiguration information, etc.
  • the security establishment process In the discovery process and/or connection establishment process related to the relay, such as the discovery request and/or establishment request message of the first broadcast address, it is transmitted with the unsecured SRB0, and then the security establishment process is carried out, and the secure establishment is transmitted with SRB1.
  • Related signaling generally a security establishment request and a security establishment completion message
  • the security establishment request message has integrity protection without encryption
  • the security establishment completion message has encryption and integrity protection.
  • SRB2 is used to transmit high-level messages with security protection, which refers to the PC5-S layer signaling that requires encryption and integrity protection to be turned on. For example, it may include discovery response messages, relay connection establishment completion messages, and so on.
  • the relay terminal After completing the foregoing relay-related discovery process and/or connection establishment process, if the relay terminal determines that it wants to perform a relay data service for the remote terminal, it may send the foregoing first relay request to the network side device.
  • connection management method of the remote terminal further includes:
  • Step 33 Establish a first sidelink RLC bearer with the remote terminal according to the configuration information of the first sidelink RLC bearer on the relay terminal side, and the first sidelink RLC bearer is used to transmit the Uu of the remote terminal In signaling, the first sidelink RLC bearer has a mapping relationship with the first Uu RLC bearer.
  • the so-called sidelink RLC bearer refers to the bearer of the RLC and its lower layers in the protocol stack of the PC5 interface, excluding the upper layer of the RLC.
  • the configuration information carried by the first sidelink RLC includes at least one of the following: RLC configuration; media access control (MAC) configuration, and the MAC configuration includes at least one of the following: logical channel identifier (ID), logical channel priority, and Prioritized Bit Rate (PBR).
  • RLC configuration includes at least one of the following: RLC configuration; media access control (MAC) configuration
  • MAC configuration includes at least one of the following: logical channel identifier (ID), logical channel priority, and Prioritized Bit Rate (PBR).
  • ID logical channel identifier
  • PBR Prioritized Bit Rate
  • the first sidelink RLC bearer is a sidelink DRB bearer or a sidelink SRB RLC bearer.
  • a sidelink RLC bearer is established between the relay terminal and the remote terminal, so that the Uu signaling sent by the remote terminal can be received to the relay terminal through the sidelink RLC bearer, and the Uu signaling sent by the remote terminal is forwarded to the relay terminal through the first Uu RLC bearer
  • the network side device, or the relay terminal receives the Uu signaling sent by the network side device through the first Uu RLC bearer, and forwards it to the remote terminal through the sidelink RLC bearer, so as to realize the Uu signaling between the remote terminal and the network side device. The transmission of the order.
  • the Uu signaling of the remote terminal may include Uu RRC signaling and NAS signaling.
  • SRB generally adopts the AM transmission mode and has a default sequence number (Sequence Number, SN) length, etc.
  • SRB can adopt default configuration or designated configuration;
  • the other is to configure the sidelink RLC bearer corresponding to DRB0 and DRB1 to transmit the Uu RRC signaling and NAS signaling of the remote terminal on the PC5 interface; the DRB used to transmit signaling adopts the AM transmission mode, which is the same as the SN of the SRB.
  • DRB can adopt a default configuration (which can be equal to the default SRB configuration) or a designated configuration.
  • the biggest difference between the SRB RLC bearer and the DRB RLC bearer is whether it can reflect the signaling information.
  • the RLC bearer ID interval or the difference in the logical channel identification (Logical Channel Identify, LCID) interval can be known as the SRB information. Otherwise, if there is no distinction, they all belong to the same interval. You can also configure the priority to be higher and the PBR is infinite to achieve priority transmission of signaling.
  • the method further includes:
  • the uplink Uu signaling may be at least one of the following: RRC connection establishment request, completion of RRC connection establishment, completion of reconfiguration, various existing uplink RRC signaling of the Uu interface, and related NAS signaling.
  • the uplink Uu signaling and the downlink Uu signaling may be carried out in different directions carried by the same sidelink RLC, and are executed by a two-way acknowledgement mode (AM) RLC entity.
  • AM two-way acknowledgement mode
  • uplink Uu signaling and downlink Uu signaling adopt different sidelink RLC bearer modes.
  • the mapping relationship between the first sidelink RLC bearer and the first Uu RLC bearer is configured by the network side device or configured by the relay terminal.
  • the first Uu RLC bearer and the first sidelink RLC bearer may have a one-to-many mapping relationship or a one-to-one mapping relationship.
  • the establishment or configuration of the first sidelink RLC bearer for carrying signaling can be done in an implicit or explicit manner:
  • the so-called implicit means that once the remote terminal and the relay terminal confirm that the relay operation can be started, each establishes the first sidelink RLC bearer according to the default configuration, and then uses it;
  • the so-called explicit refers to adding the first sidelink RLC bearer and related configuration through signaling interaction.
  • This configuration is generally sent by the relay terminal to the remote terminal, and generally accepted by the relay terminal to perform the relay function for the remote terminal. Later or at the same time, the initiated configuration may also be after the relay terminal receives the network side's request for accepting the relay function of the remote terminal, or after the relay terminal receives the Uu RLC bearer configuration on the network side, according to Uu RLC bearer configuration.
  • the bearer configuration of the Uu signaling of the remote terminal of the PC5 interface can be consistent with the configuration of the Uu interface, or can be configured separately.
  • the Uu interface uses DRB RLC bearer
  • the PC5 interface uses SRB RLC bearer.
  • the relay terminal is connected to multiple remote terminals, because the PC5 link is maintained independently for each remote terminal, it can be used on the PC5 link of each remote terminal.
  • DRB0 RLC bearer and DRB1 RLC bearer carry Uu RRC and NAS signaling. Links are different endpoints, and the relay terminal can distinguish them. And the relay terminal needs to maintain the DRB0 RLC bearer and DRB1 RLC bearer and Uu interface DRB32/33 RLC bearer (the first remote terminal to access), DRB34/35 RLC bearer (second The mapping relationship of a remote terminal that accesses)...
  • the method further includes:
  • the configuration information on the relay terminal side and the remote terminal side may be different.
  • one side is the configuration of the sender and the other is the configuration of the receiver.
  • the direction from the remote terminal to the relay terminal is called uplink
  • the direction from the relay terminal to the remote terminal is called downlink.
  • the remote terminal side is configured with uplink transmission parameters and downlink reception parameters
  • the relay terminal side is configured with downlink transmission parameters and uplink reception parameters. Therefore, the specific content of the parameters is different, but the configuration content is coordinated at both ends.
  • the RLC sequence number (SN) received and sent in each direction must be the same, and the respective uplink and downlink parameters such as RLC SN are allowed to be the same or different. The whole team cooperates to complete the sending and receiving operations in two directions.
  • the configuration information carried by the first sidelink RLC is determined in at least one of the following ways:
  • the network side device when configured by the network side device, sends the configuration information carried by the first sidelink RLC to the relay terminal, and then the relay terminal forwards the configuration information to the remote terminal.
  • the network side device may configure the first Uu RLC bearer and the first sidelink RLC bearer at the same time. That is, the first configuration information sent by the network-side device to the relay terminal may include: configuration information carried by the first Uu RLC, and configuration information carried by the first sidelink RLC.
  • the relay terminal may also separately send a second relay request to the network-side device to request the network-side device to be the Uu signaling device of the remote terminal.
  • Transmission configuration sidelink RLC bearer At this time, the network side device may separately send the configuration information carried by the first sidelink RLC to the relay terminal.
  • the relay terminal configuration includes one or a combination of the following:
  • the relay terminal is configured after receiving the relay service for the remote terminal
  • the method further includes: receiving a relay request sent by the remote terminal, where the relay request is used to request the relay terminal to do the job.
  • the remote terminal provides relay services.
  • the relay terminal accepts to provide the relay service for the remote terminal, it can configure the configuration information carried by the first sidelink RLC. For example, configure according to the default parameters agreed in the agreement.
  • the relay terminal is configured after the network side device accepts its own terminal as a relay terminal;
  • the network side device after receiving the first relay request sent by the relay terminal, sends the configuration information carried by the first U RLC to the relay terminal, and the first U RLC
  • the bearer configuration information may carry relay function confirmation information, which is used to confirm the acceptance of the terminal as a relay terminal.
  • the configuration information carried by the first Uu RLC may not carry the relay function confirmation information.
  • the relay terminal After the relay terminal receives the configuration information carried by the first Uu RLC, it defaults to the network side device accepting this The terminal acts as a relay terminal.
  • the relay terminal may configure the configuration information carried by the first sidelink RLC. For example, the configuration is performed according to the configuration information carried by the first Uu RLC.
  • the relay terminal configures after receiving the configuration information carried by the first Uu RLC
  • the relay terminal performs configuration according to the configuration information carried by the first Uu RLC.
  • the relay terminal is configured according to the configuration information carried by the first Uu RLC;
  • the relay terminal is configured according to the default parameters of the protocol.
  • 1)-3) above is to limit the configuration timing of the relay terminal to configure the first sidelink RLC bearer
  • 4) and 5) are to configure the relay terminal to configure the first sidelink RLC bearer configuration Way to limit.
  • the relay terminal can receive Uu signaling sent by the remote terminal through the first sidelink RLC bearer established with the remote terminal, or send Uu signaling sent from the network side to the remote terminal.
  • the Uu signaling of the remote terminal can also be transmitted between the relay terminal and the remote terminal through a sidelink RRC message. That is, the connection management method of the remote terminal further includes: transmitting the Uu signaling of the remote terminal with the remote terminal through a sidelink RRC message.
  • the existing sidelink RRC message can be used to carry Uu signaling, which is simple to implement.
  • the sidelink RRC message refers to the RRC message of the sidelink interface between the remote terminal and the relay terminal, and can also be a PC5-RRC message.
  • the sidelink RRC message includes at least indication information of the type of Uu signaling, and the type includes at least one of the following: RRC signaling and NAS signaling.
  • the first configuration information further includes: configuration information of a first Uu DRB RLC bearer, and the first Uu DRB RLC bearer is used to transmit service data of the remote terminal.
  • the network side device can simultaneously configure: the first Uu RLC bearer used to transmit the Uu signaling of the remote terminal, and the first Uu RLC bearer used to transmit the remote terminal
  • the first Uu DRB RLC bearer of the service data of the terminal may be a Uu SRB RLC bearer or a Uu DRB RLC bearer.
  • the above-mentioned first Uu DRB RLC bearer may be a default Uu DRB RLC bearer first established by the network side device for the remote terminal. For example, if the first relay request does not carry the service information of the remote terminal, that is, when the network-side device does not know the specific situation of the service information of the remote terminal, the default setting can be established for the remote terminal first.
  • Uu DRB RLC bearer used to transmit some simple business data.
  • the default Uu DRB RLC bearer is used for data transmission in some special situations, such as some data transmission when a dedicated DRB bearer that meets QoS requirements has not been established, or the QoS requirements are not clear, or the mapped DRB corresponding to QoS cannot be found When RLC bearer, the default DRB RLC bearer can be used to transmit the service data of the remote terminal.
  • the first relay request may also carry service information of the remote terminal.
  • the first Uu DRB RLC bearer may be a Uu DRB RLC bearer that meets the QoS requirements of the service information of the remote terminal.
  • the method further includes:
  • the second Uu DRB RLC bearer is a Uu DRB RLC bearer that meets the QoS requirements of the service information of the remote terminal.
  • the third relay request includes at least one of the following information: the identifier of the remote terminal; and the service information of the remote terminal.
  • the service information includes at least one of the following: Quality of Service Flow Identification (QFI); QoS configuration file; QoS parameter or QoS indication; maximum flow bit rate (MBR/MFBR); guaranteed flow bit rate (GBR/GFBR) ).
  • QFI Quality of Service Flow Identification
  • MRR/MFBR maximum flow bit rate
  • GRR/GFBR guaranteed flow bit rate
  • the relay information includes at least one of the following: number of relay hops supported; relay architecture options; whether to support a multi-connection relay architecture.
  • an embodiment of the present invention also provides a connection management method for a remote terminal, which is applied to a remote terminal, and the method includes:
  • Step 41 Transmit the Uu signaling of the remote terminal with the relay terminal through the first sidelink RLC bearer established with the relay terminal, or through the sidelink RRC message.
  • the so-called sidelinkRLC bearer refers to the bearer of the RLC and its lower layers in the protocol stack of the sidelink interface (that is, the PC5 interface), and does not include the layers above the RLC.
  • the first sidelink RLC bearer is a sidelink DRB bearer or a sidelink SRB RLC bearer.
  • the remote terminal transmits the Uu signaling of the remote terminal with the relay terminal through the first sidelink RLC bearer or sidelink RRC message, and the relay terminal can complete the communication between the remote terminal and the network side device.
  • the Uu signaling is forwarded, so as to realize the connection establishment between the remote terminal and the network side device, so as to carry out the normal transmission of the service.
  • the Uu signaling of the remote terminal includes the uplink Uu signaling that the remote terminal sends to the network side, and/or the downlink Uu that the network side device sends to the remote terminal Signaling.
  • transmitting the Uu signaling between the remote terminal and the relay terminal through the first sidelink RLC bearer established with the relay terminal includes:
  • the uplink Uu signaling and the downlink Uu signaling may be carried out in different directions carried by the same sidelink RLC, and are executed by a two-way acknowledgement mode (AM) RLC entity.
  • AM two-way acknowledgement mode
  • the remote terminal may also carry the Uu signaling of the remote terminal in its own RRC message in the form of a container and transmit it to the relay terminal.
  • the RRC message may carry at least one of the following information: the identifier of the remote terminal, and indication information of the type of Uu signaling of the remote terminal.
  • the type of Uu signaling includes the following At least one item: Radio Resource Control (RRC) signaling and Non Access Stratum (NAS) signaling.
  • RRC Radio Resource Control
  • NAS Non Access Stratum
  • the number of remote terminals connected to the relay terminal may be one or multiple. If the number of remote terminals is greater than one, optionally, different remote terminals.
  • the Uu signaling of the terminal is transmitted using different first sidelink RLC bearers; or, the Uu signaling of different remote terminals is transmitted using the same first sidelink RLC bearer.
  • an indication information is carried in the Uu signaling or sent together with the Uu signaling (for example, carried in the header of a layer 2 protocol data unit (PDU)), the indication information It is used to indicate the identity of the remote terminal, for example, the identity of the remote terminal.
  • PDU protocol data unit
  • whether to carry or send the indication information is configured by the network side device.
  • the type of Uu signaling of the remote terminal may be one or multiple.
  • the Uu signaling of the remote terminal includes: radio resource control (RRC) signaling and non-radio resource control (RRC) signaling.
  • RRC radio resource control
  • RRC non-radio resource control
  • Access layer Non Access Stratum, NAS
  • the U RRC signaling of the remote terminal refers to the RRC signaling between the remote terminal and the network side device
  • the U NAS signaling of the remote terminal refers to the remote terminal and its core network.
  • the NAS signaling between node access and mobility management function (Access and Mobility Management Function, AMF) is end-to-end and is directly transmitted between two endpoints.
  • AMF Access and Mobility Management Function
  • different types of Uu signaling of the same remote terminal use the same first sidelink RLC bearer transmission; or, different types of Uu signaling of the same remote terminal use different The first sidelink RLC bearer transmission.
  • an indication information is carried in the Uu signaling, or sent together with the Uu signaling (for example, carried in the header of a layer 2 protocol data unit (PDU)), the indication The information is used to indicate the type of Uu signaling service.
  • whether to carry or send the indication information is configured by the network side device.
  • the method before transmitting the Uu signaling of the remote terminal with the relay terminal through the first sidelink RLC bearer established with the relay terminal, the method further includes:
  • the configuration information carried by the first sidelink RLC is determined in the following manner: network-side device configuration; the relay terminal configuration; protocol agreement.
  • the network-side device When configured by the network-side device, the network-side device can send the configuration information carried by the first sidelink RLC to the relay terminal, and the relay terminal sends the configuration information carried by the first sidelink RLC on the remote terminal side to the remote terminal.
  • the configuration information carried by the first sidelink RLC includes: RLC configuration; MAC configuration, and the MAC configuration includes at least one of the following: a logical channel identifier, a logical channel priority, and a priority bit rate.
  • the first sidelink RLC bearer established with the relay terminal optionally, before the first sidelink RLC bearer established with the relay terminal, it further includes: a discovery process and/or a connection establishment process related to the relay with the remote terminal.
  • the discovery process and/or connection establishment process are performed using the signaling radio bearer of the PC5 link.
  • the specific process refer to the description on the relay terminal side above.
  • the method further includes: receiving the configuration information carried by the first Uu forwarded by the relay terminal, where the configuration information carried by the first Uu only includes configuration information at the PDCP layer and above .
  • an embodiment of the present invention also provides a connection management method for a remote terminal, which is applied to a network side device, and the method includes:
  • Step 51 Receive a first relay request sent by a relay terminal, where the first relay request is used to request the network side device to perform configuration related to the relay function;
  • Step 52 According to the first relay request, send first configuration information to the relay terminal, where the first configuration information includes: configuration information of a first Uu RLC bearer, and the first U RLC bearer is used for The Uu signaling of the remote terminal is transmitted.
  • Uu RLC bearer refers to the bearer of the RLC and its lower layers in the protocol stack of the Uu interface, and does not include the upper layer of the RLC.
  • the configuration information carried by the first Uu RLC includes at least one of the following: RLC configuration, and, media access control (MAC) configuration
  • the MAC configuration includes at least one of the following: logical channel identifier (ID) , Logical channel priority and priority bit rate (Prioritized Bit Rate, PBR).
  • the first Uu RLC bearer is a Uu SRB RLC bearer or a Uu DRB RLC bearer.
  • the network-side device configures the Uu RLC bearer between the network-side device and the relay terminal to be dedicated to the transmission of Uu signaling of the remote terminal according to the relay request sent by the relay terminal, thereby realizing the remote
  • the connection between the terminal and the network side device is established for normal service transmission.
  • the first configuration information may further include: indication information used to display and inform the relay terminal that the relay service can be performed.
  • the Uu signaling of the remote terminal includes the uplink Uu signaling that the remote terminal sends to the network side, and/or the downlink Uu that the network side device sends to the remote terminal Signaling.
  • connection management method of the remote terminal may further include:
  • the uplink Uu signaling and the downlink Uu signaling can be carried out in different directions carried by the same Uu RLC, and are executed by a two-way acknowledgement mode (AM) RLC entity.
  • AM two-way acknowledgement mode
  • the uplink Uu signaling and the downlink Uu signaling adopt different Uu RLC bearer modes.
  • the Uu signaling of the remote terminal includes at least one of the following: RRC signaling and NAS signaling.
  • the network side device parses the Uu RRC signaling of the remote terminal, it processes it, and executes the related response or configuration. In the Uu RRC signaling downlink pipe of the remote terminal, it performs the related downlink U RRC signaling. transmission.
  • the network side device After analyzing the NAS signaling of the remote terminal, the network side device establishes a special NAS signaling channel from the network side device to the core network (such as the AMF entity) for the remote terminal, such as the XG interface, for transmitting the remote terminal.
  • the NAS signaling of the end terminal is similar to the downlink NAS signaling transmission.
  • the network side device provides corresponding configuration content according to the internal information carried in the first relay request sent by the relay terminal.
  • the network side can only know that the relay terminal is about to start the relay function at this time, but it will relay Which data is unclear, so the configurations that can be provided at this time are only the following two types:
  • the Uu signaling of the remote terminal is mainly protected by the following two types:
  • RRC connection setup request/command/complete RRC connection setup request, RRC connection setup, RRC connection setup complete
  • RRC reconfiguration/complete RRC connection setup request, RRC connection setup complete
  • Reconfiguration RRC reconfiguration complete
  • the second type refers to the NAS signaling between the remote terminal and the core network, such as service request, registration, or authentication management; this type of message uses the RRC signaling in SRB1 when the terminal is directly connected to the network side device. Make the container (Container) mode, or establish SRB2 exclusively for NAS signaling transmission.
  • the remote terminal since the remote terminal is not directly connected to the network side equipment at this time, its RRC signaling and NAS signaling need to rely on the bearer of the relay terminal for piggybacking, and the SRB1 and SRB2 of the relay terminal are exclusively used to transmit their own RRC messages and NAS messages are not suitable for the transmission of related messages of relay terminals. Therefore, RRC messages and NAS messages for remote terminals need to be transmitted in a way that can be distinguished from relay terminals and other remote terminals.
  • the network side needs to provide relevant configuration, mainly including the following methods:
  • the first is to establish a special Uu RLC bearer corresponding to the new SRB, which is used for the RRC signaling and NAS signaling bearer of the remote terminal;
  • the Uu RLC bearer of SRB4 (the reason for starting from SRB4 is that SRB0 is used to relay RRC signaling transmission on the common control channel (CCCH) of the terminal itself, and SRB1 is used for dedicated control channel (Dedicated Control Channel). , DCCH) RRC signaling transmission, SRB2 is used for NAS signaling, SRB3 is used for Secondary Cell Group (SCG) RRC signaling transmission, all occupied), SRB4 is used for RRC signaling bearer for remote terminals, The SRB5 RLC bearer is used for the NAS signaling bearer of the remote terminal.
  • DCCH DCCH
  • SRB2 is used for NAS signaling
  • SRB3 is used for Secondary Cell Group (SCG) RRC signaling transmission, all occupied)
  • SRB4 is used for RRC signaling bearer for remote terminals
  • the SRB5 RLC bearer is used for the NAS signaling bearer of the remote terminal.
  • the SRB4 RLC bearer and SRB5 RLC bearer and their corresponding configuration information are added to the relay terminal reconfiguration signaling respectively (SRB adopts AM transmission mode and has a default SN Length, etc.), and indicate that the transmission content of the SRB4 RLC bearer and SRB5 RLC bearer are RRC signaling and NAS signaling of the remote terminal respectively, or not explicitly indicated, and adopt the default or standard prescribed method.
  • the relay terminal When the relay terminal supports more than one remote terminal, it can establish SRB6 for the second connected remote terminal.
  • SRB7 RLC bearer is used for RRC signaling and NAS signaling transmission, indicating each newly established SRB and remote terminal The mapping relationship between ID and RRC/NAS message. It is also possible to directly multiplex the SRB4 RLC bearer and SRB5 RLC bearer for the transmission of RRC messages and NAS messages of all remote terminals. If all remote terminals multiplex a pair of SRB4 RLC bearer and SRB5 RLC bearer, it is necessary to distinguish which remote terminal belongs to in the signaling, for example, to explicitly carry the remote terminal ID.
  • an indication information is carried in the Uu signaling or sent together with the Uu signaling (for example, carried in the header of a layer 2 protocol data unit (PDU)), the indication information It is used to indicate the identity of the remote terminal, for example, the identity of the remote terminal.
  • PDU layer 2 protocol data unit
  • whether to carry or send the indication information is configured by the network side device.
  • the RRC signaling and NAS signaling of the remote terminal can also be placed in one SRB RLC bearer for transmission, in two ways:
  • the NAS signaling is encapsulated in RRC signaling, for example, the RRC message UL Information Transfer/DL information Transfer is used to encapsulate uplink and downlink NAS messages.
  • the simplest way is to configure different SRB RLC bearer bearers for the RRC messages and NAS messages of each remote terminal.
  • the advantage is that the pipeline is clearly divided, and the data parsed from each SRB RLC bearer belongs to which remote terminal
  • the RRC or NAS is very clear, and there is no need to carry distinguishing information in each signaling. If, on this basis, in order to further save the number of SRB RLC bearers, information multiplexing of different remote terminals can be considered, or NAS and RRC are transmitted on one SRB RLC bearer, the multiplexed signaling, if they belong to different
  • the remote terminal needs to carry the remote terminal ID in each signaling to distinguish it. If it belongs to different types, it also needs to distinguish the NAS/RRC type.
  • an indication information is carried in the Uu signaling, or sent together with the Uu signaling (for example, carried in the header of a layer 2 protocol data unit (PDU)), the indication The information is used to indicate the type of Uu signaling service.
  • whether to carry or send the indication information is configured by the network side device.
  • the second type is to establish a dedicated DRB RLC bearer, which is used to bear the RRC signaling and NAS signaling of the remote terminal;
  • Configuration information (DRB RLC bearer used to transmit signaling generally adopts AM transmission mode, you can use SN length equal to the default SN length of SRB or configure a special SN length, etc.), and indicate the transmission of DRB5 RLC bearer and DRB6 RLC bearer
  • the content is the RRC signaling and NAS signaling of the remote terminal respectively, or not explicitly pointed out, the default or standard prescribed method is adopted.
  • DRB5 RLC bearer and DRB6 RLC bearer are only used as examples, because they need to be distinguished from the relay terminal's own DRB used to carry data. If DRB1-4 has been established, you can create a new DRB5/6 RLC bearer. In addition, you can also consider reserving the existing DRB for the relay terminal itself. For example, the relay terminal uses 0-31, and other remote terminals start from 32 and 33.
  • DRB7 can be established for the second connected remote terminal.
  • DRB8 is used for RRC signaling and NAS signaling transmission, indicating each newly established DRB RLC bearer and remote terminal The mapping relationship between ID and RRC/NAS message. It is also possible to directly multiplex DRB5 RLC bearer and DRB6 RLC bearer for the transmission of RRC messages and NAS messages of all remote terminals. If all remote terminals multiplex a pair of DRB5 RLC bearer and DRB6 RLC bearer, it is necessary to distinguish which remote terminal belongs to in the signaling, for example, to explicitly carry the remote terminal ID.
  • the RRC signaling and NAS signaling of the remote terminal can also be transmitted in one DRB in two ways:
  • the NAS signaling is encapsulated in RRC signaling, for example, the RRC message UL Information Transfer/DL information Transfer is used to encapsulate uplink and downlink NAS messages.
  • the simplest way is to configure different DRB RLC bearer bearers for the RRC messages and NAS messages of each remote terminal.
  • the advantage is that the pipeline is clearly divided, and the data parsed from each DRB RLC bearer belongs to which remote terminal
  • the RRC or NAS is very clear, and there is no need to carry distinguishing information in each signaling. If on this basis, in order to further save the number of DRB RLC bearers, information multiplexing of different remote terminals can be considered, or NAS and RRC are transmitted in a DRB RLC bearer, the multiplexed signaling, if they belong to different
  • the remote terminal needs to carry the remote terminal ID in each signaling to distinguish it. If it belongs to different types, it also needs to distinguish the NAS/RRC type.
  • the network side device can first establish a default Uu DRB RLC bearer for the remote terminal, which is used for data transmission in some special situations, such as dedicated to meet QoS requirements When the DRB bearer has not been established for some data transmission, or the QoS requirements are not clear, or the mapped DRB RLC bearer with corresponding QoS cannot be found, the default DRB RLC bearer can be used to transmit remote terminal data.
  • the default DRB RLC bearer bearer is an optional configuration. It is also possible to establish a signaling bearer pipeline first, and then perform the data DRB RLC bearer configuration after the subsequent service requirements are reported.
  • the first configuration information further includes: configuration information carried by a first Uu DRB RLC, and the first Uu DRB RLC bearer is used to transmit service data of the remote terminal . That is to say, after receiving the first relay request sent by the relay terminal, the network side device can simultaneously configure: the first Uu RLC bearer used to transmit the Uu signaling of the remote terminal, and the first Uu RLC bearer used to transmit the remote terminal The first Uu DRB RLC bearer of the service data of the terminal.
  • the first Uu RLC bearer may be a Uu SRB RLC bearer or a Uu DRB RLC bearer.
  • the relay terminal when the remote terminal Uu signaling is transmitted on the Uu interface of the relay terminal, the relay terminal only needs to perform L2 related forwarding operations, that is, whether it is an SRB RLC bearer or a DRB RLC bearer, they only have RLC. /MA layer and below the protocol stack and configuration, the biggest difference between SRB RLC bearer/DRB RLC bearer is whether its RLC bearer identifier or logical channel identifier can reflect the attributes of SRB or DRB, that is, whether it is necessary to distinguish the RLC bearer carrying signaling Whether it belongs to the SRB category or the DRB category, the advantage of the distinction is that special operations can be performed on the RLC bearer of the SRB attribute.
  • the processing priority is higher, data transmission takes precedence over normal data transmission, and PBR (guaranteed bit rate) can be infinite by default .
  • PBR potential bit rate
  • SRB/DRB attributes are not distinguished, a unified RLC bearer ID/LCID number interval can also be adopted, but the RLC bearer that carries signaling is configured with higher priority and infinite PBR.
  • the uplink and downlink RRC signaling and NAS signaling of the remote terminal can be transmitted on the Uu interface.
  • the method further includes: sending configuration information of a first sidelink RLC bearer to the relay terminal, and the first sidelink RLC bearer is used to transmit the Uu information of the remote terminal.
  • the first sidelink RLC bearer and the first Uu RLC bearer have a mapping relationship.
  • the mapping relationship is configured by the network side device.
  • the configuration information carried by the first sidelink RLC is located in the first configuration information. That is, the network side device simultaneously configures the configuration information of the first Uu RLC bearer and the first sidelink RLC bearer, and sends the configuration information to the relay terminal.
  • the method before sending the configuration information carried by the first sidelink RLC to the relay terminal, the method further includes:
  • the network side device separately sends the configuration information carried by the first sidelink RLC to the relay terminal according to the second relay request.
  • the method further includes:
  • the configuration information of the second Uu DRB RLC bearer is sent to the relay terminal, and the second Uu DRB RLC bearer is used to transmit the service data of the remote terminal.
  • the second Uu DRB RLC bearer is a Uu DRB RLC bearer that meets the QoS requirements of the service information of the remote terminal.
  • the third relay request includes at least one of the following information: an identifier of the remote terminal; and service information of the remote terminal.
  • the service information includes at least one of the following: Quality of Service Flow Identification (QFI); QoS configuration file; QoS parameter or QoS indication; maximum flow bit rate (MBR/MFBR); guaranteed flow bit rate (GBR/GFBR) ).
  • QFI Quality of Service Flow Identification
  • MRR/MFBR maximum flow bit rate
  • GRR/GFBR guaranteed flow bit rate
  • the relay information includes at least one of the following: number of relay hops supported; relay architecture options; whether to support a multi-connection relay architecture.
  • the method further includes: sending configuration information of the first Uu carried by the network-side device and the remote terminal to the relay terminal, and the first Uu carried
  • the configuration information only includes the configuration information of the PDCP layer and above.
  • the remote terminal can use the SRB/DRB RLC bearer, sending RRC messages to the network side equipment, such as sending RRC uplink signaling, where the establishment request carries a special cause value, such as remote indicator, indicating that this is a remote UE access, or because the remote UE RRC message passed
  • the RLC bearer of the relay terminal arrives at the network side, and the network side can know that this is a remote terminal, which is convenient for the network side to perform special configuration for the remote terminal.
  • the special features are:
  • Special configuration for the remote terminal such as the configuration of the PC5 link of the remote terminal, which mainly includes the RLC layer and the following configurations carried by the Uu on the PC5 interface, and how the data sent by the remote terminal to the network is mapped on the PC5 SLRB, etc.
  • the RRC signaling or NAS signaling of the remote terminal, the PDCP layer and above are established end-to-end bearers, and the remote terminal ⁇ -> network side equipment performs end-to-end security, encryption and integrity protection , All signaling processes are similar to Uu terminals, but the configuration information is special.
  • the sending method is through remote terminal ⁇ -> RLC bearer between relay terminals, and relay terminal ⁇ -> RLC between network side devices The bearer performs uplink and downlink transmission.
  • FIG. 6 is a schematic flowchart of a remote terminal management method according to another embodiment of the present invention.
  • the method includes:
  • Step 60 Perform a relay-related discovery and/or connection establishment process between the remote terminal and the relay terminal;
  • Step 61 The relay terminal sends a first relay request to the base station (that is, the aforementioned network side device), where the first relay request is used to request the base station to perform relay function-related configuration;
  • Step 62 The base station sends first configuration information to the relay terminal, where the first configuration information includes: configuration information of the first Uu RLC bearer and the first sidelink RLC bearer, and the first Uu RLC bearer and the first sidelink RLC bearer Uu signaling used to transmit remote terminals;
  • Step 63 The relay terminal sends the configuration information carried by the first sidelink RLC on the remote terminal side to the remote terminal;
  • step 63 needs to be continued after step 62. It does not rule out that step 63 may perform the first sidelink RLC configuration after step 60 is completed, that is, when the relay terminal accepts to provide a relay service for the remote terminal. In this way, the Uu interface and the PC5 interface are executed in parallel, saving time delay.
  • Step 64 The remote terminal sends uplink Uu signaling of the remote terminal on the first sidelink RLC bearer
  • Step 65 After receiving the uplink Uu signaling of the remote terminal, the relay terminal sends the uplink Uu signaling of the remote terminal on the first Uu RLC bearer;
  • Step 66 If the uplink Uu signaling of the remote terminal is uplink NAS signaling, the base station sends the uplink NAS signaling of the remote terminal to the core network device;
  • Step 67 The base station receives the downlink NAS signaling of the remote terminal sent by the core network device;
  • Step 68 The base station sends downlink Uu signaling of the remote terminal on the first Uu RLC bearer
  • Step 69 After receiving the downlink Uu signaling of the remote terminal, the relay terminal sends the downlink Uu signaling of the remote terminal on the first sidelink RLC bearer.
  • the bearer configuration process of Uu RRC signaling and NAS signaling on the sidelink interface and Uu interface from the remote terminal to the network side has been opened.
  • the remote terminal can use the configured bearer to transmit Uu RRC signaling and NAS signaling.
  • the content of the signaling transmission is similar to the existing UE process, which may carry special instructions from the remote terminal to inform the base station or core network that this is a remote terminal.
  • an embodiment of the present invention also provides a terminal 70, including:
  • the first sending module 71 is configured to send a first relay request to the network side device, where the first relay request is used to request the network side device to perform configuration related to the relay function;
  • the first receiving module 72 is configured to receive first configuration information sent by the network side device, where the first configuration information includes: configuration information carried by a first Uu radio link layer control protocol RLC, and the first Uu RLC It bears Uu signaling used to transmit remote terminals.
  • the first configuration information includes: configuration information carried by a first Uu radio link layer control protocol RLC, and the first Uu RLC It bears Uu signaling used to transmit remote terminals.
  • the first Uu RLC bearer is a Uu SRB RLC bearer or a Uu DRB RLC bearer.
  • the Uu signaling of different remote terminals is transmitted by using different first Uu RLC bearers; or, the Uu signaling of different remote terminals The same first Uu RLC bearer is used for transmission.
  • different types of Uu signaling of the same remote terminal use the same first Uu RLC bearer for transmission; or, different types of Uu signaling of the same remote terminal use different first Uu RLC bearers. transmission.
  • At least one of the following indication information is carried in the Uu signaling or sent at the same time as the Uu signaling: the identifier of the remote terminal; the type of the Uu signaling.
  • whether to carry or send the indication information is configured by the network side device.
  • the first sending module is used to:
  • the first relay request is carried in the radio resource control RRC connection establishment request sent to the network side device, or the RRC connection establishment request sent to the network side device
  • the completion carries the first relay request, or, after the establishment of the RRC connection is completed, the first uplink signaling is used to send the first relay request;
  • the first relay request is carried in the RRC connection recovery request sent to the network side device, or the RRC connection recovery request sent to the network side device is completed Carry the first relay request; or, after the RRC connection is restored, use the first uplink signaling to send the first relay request;
  • the first uplink signaling is used to send the first relay request.
  • the terminal further includes: an establishment module configured to establish a first sidelink RLC bearer with the remote terminal according to the configuration information of the sidelink RLC bearer of the first secondary link on the relay terminal side,
  • the first sidelink RLC bearer is used to transmit Uu signaling of the remote terminal, and the first sidelink RLC bearer has a mapping relationship with the first Uu RLC bearer.
  • mapping relationship is configured by the network side device or configured by the relay terminal.
  • the first sidelink RLC bearer is a sidelink DRB bearer or a sidelink SRB RLC bearer.
  • the terminal further includes: a second sending module, configured to send configuration information carried by the first sidelink RLC on the remote terminal side to the remote terminal.
  • a second sending module configured to send configuration information carried by the first sidelink RLC on the remote terminal side to the remote terminal.
  • the configuration information carried by the first sidelink RLC is determined in at least one of the following manners: the network side device configuration; the relay terminal configuration; protocol agreement.
  • the relay terminal configuration includes at least one of the following:
  • the relay terminal is configured after accepting to provide a relay service for the remote terminal
  • the relay terminal is configured after the network side device accepts its own terminal as a relay terminal;
  • the relay terminal is configured according to the configuration information carried by the first Uu RLC;
  • the relay terminal is configured according to the default parameters of the protocol.
  • the configuration information of the first Uu RLC bearer and the first sidelink RLC bearer includes at least one of the following: RLC configuration; MAC configuration, and the MAC configuration includes at least one of the following: logical channel identifier, logical channel priority And priority bit rate.
  • the terminal further includes: a transmission module, configured to transmit Uu signaling of the remote terminal with the remote terminal through a sidelink RRC message.
  • a transmission module configured to transmit Uu signaling of the remote terminal with the remote terminal through a sidelink RRC message.
  • the sidelink RRC message includes at least indication information of the type of Uu signaling, and the type includes at least one of the following: RRC signaling and non-access stratum NAS signaling.
  • the first configuration information further includes: configuration information carried by a first Uu DRB RLC, and the first Uu DRB RLC bearer is used to transmit service data of the remote terminal.
  • the terminal further includes:
  • the third sending module is configured to send a third relay request to the network side device, and the third relay request is used to request the network side device to configure a Uu RLC bearer for the transmission of the service data of the remote terminal ;
  • the second receiving module is configured to receive configuration information carried by the second Uu DRB RLC sent by the network side device, and the second Uu DRB RLC bearer is used to transmit service data of the remote terminal.
  • the first relay request includes at least one of the following information:
  • Relay indication information where the relay indication information is used when the current message is the first relay request
  • the identifier of the remote terminal is the identifier of the remote terminal
  • the third relay request includes at least one of the following information:
  • the identifier of the remote terminal is the identifier of the remote terminal
  • the service information includes at least one of the following: QFI; QoS configuration file; QoS parameter or QoS indication; MBR/MFBR; GBR/GFBR.
  • the relay information includes at least one of the following: number of relay hops supported; relay architecture options; whether to support a multi-connection relay architecture.
  • the terminal further includes a connection module, which is used to perform a discovery process and/or a connection establishment process related to the relay between the remote terminal.
  • a connection module which is used to perform a discovery process and/or a connection establishment process related to the relay between the remote terminal.
  • the discovery process and/or connection establishment process are performed using the signaling radio bearer of the PC5 link.
  • the terminal provided in the embodiment of the present invention can implement each process implemented by the terminal in the method embodiment of FIG. 3, and to avoid repetition, details are not described herein again.
  • an embodiment of the present invention also provides a terminal 80, including:
  • the transmission module 81 is configured to transmit the Uu signaling of the remote terminal with the relay terminal through the first sidelink RLC bearer established with the relay terminal, or through the sidelink RRC message.
  • the first sidelink RLC bearer is a sidelink DRB bearer or a sidelink SRB RLC bearer.
  • the terminal further includes: an establishment module configured to establish the first sidelink RLC bearer with the relay terminal according to the configuration information of the first sidelink RLC bearer on the remote terminal side.
  • the configuration information carried by the first sidelink RLC is determined in the following manner: network-side device configuration; the relay terminal configuration; protocol agreement.
  • the configuration information carried by the first sidelink RLC includes: RLC configuration; MAC configuration, and the MAC configuration includes at least one of the following: a logical channel identifier, a logical channel priority, and a priority bit rate.
  • the sidelink RRC message includes at least: indication information of the type of Uu signaling of the remote terminal, and the type includes at least one of the following: RRC signaling and NAS signaling.
  • the terminal further includes: a connection module, which is used to perform a discovery process and/or a connection establishment process related to the relay between the relay terminal.
  • a connection module which is used to perform a discovery process and/or a connection establishment process related to the relay between the relay terminal.
  • the discovery process and/or connection establishment process are performed using the signaling radio bearer of the PC5 link.
  • the terminal further includes: a receiving module configured to receive configuration information carried by the first Uu forwarded by the relay terminal, where the configuration information carried by the first Uu only includes configuration information at the PDCP layer and above.
  • a receiving module configured to receive configuration information carried by the first Uu forwarded by the relay terminal, where the configuration information carried by the first Uu only includes configuration information at the PDCP layer and above.
  • the terminal provided in the embodiment of the present invention can implement each process implemented by the terminal in the method embodiment of FIG. 4, and to avoid repetition, details are not described herein again.
  • an embodiment of the present invention also provides a network side device 90, including:
  • the first receiving module 91 is configured to receive a first relay request sent by a relay terminal, where the first relay request is used to request the network side device to perform configuration related to the relay function;
  • the first sending module 92 is configured to send first configuration information to the relay terminal according to the first relay request, where the first configuration information includes: configuration information carried by a first Uu RLC, and the first The Uu RLC bearer is used to transmit the Uu signaling of the remote terminal.
  • the first Uu RLC bearer is a Uu SRB RLC bearer or a Uu DRB RLC bearer.
  • the Uu signaling of different remote terminals is transmitted by using different first Uu RLC bearers; or, the Uu signaling of different remote terminals The same first Uu RLC bearer is used for transmission.
  • different types of Uu signaling of the same remote terminal use the same first Uu RLC bearer for transmission; or, different types of Uu signaling of the same remote terminal use different first Uu RLC bearers. transmission.
  • At least one of the following indication information is carried in the Uu signaling or sent at the same time as the Uu signaling: the identifier of the remote terminal; the type of the Uu signaling.
  • whether to carry or send the indication information is configured by the network side device.
  • the terminal further includes: a second sending module, configured to send configuration information of a first sidelink RLC bearer to the relay terminal, and the first sidelink RLC bearer is used to transmit the Uu of the remote terminal In signaling, the first sidelink RLC bearer has a mapping relationship with the first Uu RLC bearer.
  • mapping relationship is configured by the network side device.
  • the first sidelink RLC bearer is a sidelink DRB bearer or a sidelink SRB RLC bearer.
  • the configuration information of the first Uu RLC bearer and the first sidelink RLC bearer includes at least one of the following: RLC configuration; MAC configuration, and the MAC configuration includes at least one of the following: logical channel identifier, logical channel priority And priority bit rate.
  • the first configuration information further includes: configuration information carried by a first Uu DRB RLC, and the first Uu DRB RLC bearer is used to transmit service data of the remote terminal.
  • the terminal further includes:
  • the second receiving module is configured to receive a third relay request sent by the relay terminal, where the third relay request is used to request the network side device to configure Uu RLC for the transmission of service data of the remote terminal Bearer
  • the third sending module is configured to send configuration information of a second Uu DRB RLC bearer to the relay terminal according to the third relay request, and the second Uu DRB RLC bearer is used to transmit the remote terminal’s Business data.
  • the terminal further includes: a fourth sending module, configured to send configuration information of the first Uu bearer between the network side device and the remote terminal to the relay terminal, and the first Uu bearer
  • the configuration information only includes the configuration information of the PDCP layer and above.
  • the terminal provided in the embodiment of the present invention can implement each process implemented by the network side device in the method embodiment of FIG. 5, and to avoid repetition, details are not described herein again.
  • the terminal 100 includes but is not limited to: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, User input unit 107, interface unit 108, memory 109, processor 1010, power supply 1011 and other components.
  • a radio frequency unit 101 includes but is not limited to: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, User input unit 107, interface unit 108, memory 109, processor 1010, power supply 1011 and other components.
  • the terminal structure shown in FIG. 10 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than those shown in the figure, or combine certain components, or arrange different components.
  • the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle-mounted terminal, a wearable device, a
  • the radio frequency unit 101 is configured to send a first relay request to a network-side device, and the first relay request is used to request the network-side device to perform configuration related to the relay function;
  • First configuration information the first configuration information includes: configuration information carried by a first Uu radio link layer control protocol RLC, and the first Uu RLC bears Uu signaling used to transmit a remote terminal.
  • the radio frequency unit 101 is configured to transmit the Uu signaling of the remote terminal with the relay terminal through the first sidelink RLC bearer established with the relay terminal, or through the sidelink RRC message.
  • the terminal provided in the embodiment of the present invention can implement each process implemented by the terminal in the method embodiment of FIG. 3 or FIG. 4, and to avoid repetition, details are not described herein again.
  • the terminal 100 includes some functional modules not shown, which will not be repeated here.
  • an embodiment of the present invention also provides a terminal 110, including a processor 111, a memory 112, a computer program stored on the memory 112 and running on the processor 111, and the computer program is executed by the processor 111.
  • a terminal 110 including a processor 111, a memory 112, a computer program stored on the memory 112 and running on the processor 111, and the computer program is executed by the processor 111.
  • the embodiment of the present invention also provides a terminal 120, including a processor 121, a memory 122, a computer program stored on the memory 122 and running on the processor 121, the computer program is used by the processor 121
  • a terminal 120 including a processor 121, a memory 122, a computer program stored on the memory 122 and running on the processor 121, the computer program is used by the processor 121
  • each process of the foregoing embodiment of the remote terminal connection management method applied to the remote terminal is realized, and the same technical effect can be achieved. In order to avoid repetition, it will not be repeated here.
  • an embodiment of the present invention also provides a network side device 130, including a processor 131, a memory 132, a computer program stored on the memory 132 and running on the processor 131, the computer program is processed
  • the device 131 is executed, each process of the above-mentioned connection management method embodiment applied to a remote terminal of a network side device is realized, and the same technical effect can be achieved. In order to avoid repetition, details are not repeated here.
  • the embodiment of the present invention also provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the embodiment of the connection management method applied to the remote terminal of the relay terminal is realized Each process can achieve the same technical effect. To avoid repetition, I won’t repeat it here.
  • the embodiment of the present invention also provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the embodiment of the connection management method applied to the remote terminal of the remote terminal is realized.
  • Each process can achieve the same technical effect. To avoid repetition, I won’t repeat it here.
  • the embodiment of the present invention also provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the embodiment of the connection management method applied to the remote terminal of the network side device is realized Each process can achieve the same technical effect. To avoid repetition, I won’t repeat it here.
  • the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk, etc.
  • An embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or an instruction to implement the
  • the processes of the embodiments of the remote terminal connection management method can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
  • chips mentioned in the embodiments of the present application may also be referred to as system-level chips, system-on-chips, system-on-chips, or system-on-chips.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the technical solution of the present invention essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the method described in each embodiment of the present invention.
  • a terminal which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.
  • the program can be stored in a computer readable storage medium. When executed, it may include the procedures of the above-mentioned method embodiments.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM), etc.
  • modules, units, and sub-units can be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (Digital Signal Processor, DSP), and digital signal processing equipment (DSP Device, DSPD). ), programmable logic devices (Programmable Logic Device, PLD), Field-Programmable Gate Array (FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, used to implement this disclosure Other electronic units or a combination of the functions described above.
  • ASIC application specific integrated circuits
  • DSP Digital Signal Processor
  • DSP Device digital signal processing equipment
  • DSPD digital signal processing equipment
  • PLD programmable logic devices
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present disclosure can be implemented by modules (for example, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • the software codes can be stored in the memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Quality & Reliability (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Selective Calling Equipment (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例提供一种远端终端的连接管理方法、终端及网络侧设备，属于通信技术领域。该远端终端的连接管理方法包括：向网络侧设备发送第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；接收所述网络侧设备发送的第一配置信息，所述第一配置信息包括：第一Uu RLC承载的配置信息，所述第一Uu RLC承载用于传输远端终端的Uu信令。

Description

远端终端的连接管理方法、终端及网络侧设备
相关申请的交叉引用
本申请主张在2020年4月28日在中国提交的中国专利申请号No.202010352343.X的优先权，其全部内容通过引用包含于此。
技术领域
本发明实施例涉及通信技术领域，尤其涉及一种远端终端的连接管理方法、终端及网络侧设备。
背景技术
1.副链路(sidelink，或译为侧链路，边链路等)介绍
长期演进(Long Term Evolution，LTE)系统从第12个发布版本开始支持sidelink，用于用户设备(User Equipment，UE，简称为终端)之间不通过网络设备进行直接数据传输。
LTE sidelink的设计适用于特定的公共安全事务(如火灾场所或地震等灾难场所进行紧急通讯)，或车联网(vehicle to everything，V2X)通信等。车联网通信包括各种业务，例如，基本安全类通信，高级(自动)驾驶，编队，传感器扩展等等。由于LTE sidelink只支持广播通信，因此主要用于基本安全类通信，其他在时延、可靠性等方面具有严格服务质量(Quality of Service，QoS)需求的高级V2X业务将通过新空口(New Radio，NR)sidelink支持。
第五代(5 th Generation，5G)NR系统可用于LTE所不支持的6GHz以上工作频段，支持更大的工作带宽，但目前版本的NR系统只支持基站与终端间的接口，尚不支持终端之间直接通信的Sidelink接口。Sidelink接口又可以称作PC5接口。
2.Sidelink中继(relay)
典型的sidelink中继场景中，远端(remote)UE通过和中继(relay)UE之间的sidelink链路，由relay UE将它的数据与基站之间进行转发。在这个场景中，remote UE和基站之间进行数据传输，relay UE起到数据中转作用。
在实现本申请过程中，发明人发现现有技术中至少存在如下问题：
现有机制中，并没有sidelink中继架构下的remote UE连接管理的相关解决方案，而按照现有Uu接口的过程，并不足以直接应用于存在中继的架构中，因为Uu接口只有一跳空口，相关信令在信令无线承载(Signalling Radio Bearer，SRB)上传输，并且哪个SRB传输什么内容都规定很清晰，但这一套流程无法直接用于remote UE，只能解决relay UE的连接过程。导致remote UE无法进行正常的连接建立，造成业务无法建立和传输，用户体验降低。
发明内容
本发明实施例提供一种远端终端的连接管理方法、终端及网络侧设备，用于解决在sidelink中继架构下，远端终端无法与网络侧设备进行正常的连接建立，造成业务无法建立和传输的问题。
为了解决上述技术问题，本发明是这样实现的：
第一方面，本发明实施例提供了一种远端终端的连接管理方法，应用于中继终端，所述方法包括：
向网络侧设备发送第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
接收所述网络侧设备发送的第一配置信息，所述第一配置信息包括：第一Uu无线链路控制(Radio Link Control，RLC)承载的配置信息，所述第一Uu RLC承载用于传输远端终端的Uu信令。
第二方面，本发明实施例提供了一种远端终端的连接管理方法，应用于远端终端，所述方法包括：
通过与中继终端之间建立的第一sidelink RLC承载，或者，通过sidelink无线资源控制(Radio Resource Control，RRC)消息，传输所述远端终端的Uu信令。
第三方面，本发明实施例提供了一种远端终端的连接管理方法，应用于网络侧设备，所述方法包括：
接收中继终端发送的第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
根据所述第一中继请求，向所述中继终端发送第一配置信息，所述第一配置信息包括：第一Uu RLC承载的配置信息，所述第一Uu RLC承载用于传输所述远端终端的Uu信令。
第四方面，本发明实施例提供了一种终端，包括：
第一发送模块，用于向网络侧设备发送第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
第一接收模块，用于接收所述网络侧设备根据所述第一中继请求发送的第一配置信息，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置。
第五方面，本发明实施例提供了一种终端，包括：
传输模块，用于通过与中继终端之间建立的第一sidelink RLC承载，或者，通过RRC消息，传输所述远端终端的Uu信令。
第六方面，本发明实施例提供了一种网络侧设备，包括：
第一接收模块，用于接收中继终端发送的第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
第一发送模块，用于根据所述第一中继请求，向所述中继终端发送第一配置信息，所述第一配置信息包括：第一Uu RLC承载的配置信息，所述第一Uu RLC承载用于传输所述远端终端的Uu信令。
第七方面，本发明实施例提供了一种终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现应用于所述第一方面的远端终端的连接管理方法的步骤。
第八方面，本发明实施例提供了一种终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现应用于第二方面的连接管理方法的步骤。
第九方面，本发明实施例提供了一种网络侧设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现上述第三方面的远端终端的连接管理方法的步骤。
第十方面，本发明实施例提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现上述第一方面的远端终端的连接管理方法的步骤；或者，所述程序或指令被处理器执行时实现上述第二方面的远端终端的连接管理方法的步骤；或者，所述程序或指令被处理器执行时实现上述第三方面的远端终端的连接管理方法的步骤。
第十一方面，本发明实施例提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述第一方面的远端终端的连接管理方法的步骤；或者，实现上述第二方面的远端终端的连接管理方法的步骤；或者，实现上述第三方面的远端终端的连接管理方法的步骤。
第十二方面，本发明实施例提供了一种计算机软件产品，所述计算机软件产品被存储在非易失的存储介质中，所述软件产品被配置成被至少一个处理器执行以实现上述第一方面的远端终端的连接管理方法的步骤；或者，实现上述第二方面的远端终端的连接管理方法的步骤；或者，实现上述第三方面的远端终端的连接管理方法的步骤。
在本发明实施例中，通过配置中继终端与网络侧设备之间的Uu RLC承载以专用于远端终端的Uu信令的传输，从而实现远端终端与网络侧设备之间的连接建立，以进行业务的正常传输。
附图说明
通过阅读下文优选实施方式的详细描述，各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目的，而并不认为是对本发明的限制。而且在整个附图中，用相同的参考符号表示相同的部件。在附图中：
图1和图2为本发明实施例提供的一种无线通信系统的架构示意图；
图3为本发明一实施例的远端终端的连接管理方法的流程示意图；
图4为本发明另一实施例的远端终端的连接管理方法的流程示意图；
图5为本发明又一实施例的远端终端的连接管理方法的流程示意图；
图6为本发明再一实施例的远端终端的连接管理方法的流程示意图；
图7为本发明一实施例的终端的结构示意图；
图8为本发明另一实施例的终端的结构示意图；
图9为本发明一实施例的网络侧设备的结构示意图；
图10为本发明一实施例的终端的硬件结构示意图；
图11为本发明又一实施例的终端的结构示意图；
图12为本发明又一实施例的终端的结构示意图；
图13为本发明另一实施例的网络侧设备的结构示意图。
具体实施方式
本申请的说明书和权利要求书中的术语“包括”以及它的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。此外，说明书以及权利要求中使用“和/或”表示所连接对象的至少其中之一，例如A和/或B，表示包含单独A，单独B，以及A和B都存在三种情况。
在本发明实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本发明实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
下面结合附图介绍本发明的实施例。本发明实施例提供的远端终端的连接管理方法、终端及网络侧设备可以应用于无线通信系统中。该无线通信系统可以采用5G系统，或者演进型长期演进(Evolved Long Term Evolution，eLTE)系统，或者后续演进通信系统。
参考图1和图2，为本发明实施例提供的一种无线通信系统的架构示意图。如图1所示，该无线通信系统可以包括：网络侧设备11和多个终端12，其中，终端12除了可以通过Uu接口与网络侧设备11连接之外，还可以通过sidelink接口直接与其他终端12连接。
本发明实施例提供的网络侧设备11可以为基站，该基站可以为通常所用的基站，也可以为演进型基站(evolved node base station，eNB)，还可以为 5G系统中的网络侧设备(例如下一代基站(next generation node base station，gNB)或发送和接收点(transmission and reception point，TRP))或者小区cell等设备。或者后续演进通信系统中的网络侧设备。
本发明实施例提供的终端12可以为手机、平板电脑、笔记本电脑、超级移动个人计算机(Ultra-Mobile Personal Computer，UMPC)、上网本或者个人数字助理(Personal Digital Assistant，PDA)等。
请参考图3，图3为本发明一实施例的远端终端的连接管理方法的流程示意图，该方法应用于中继终端，包括：
步骤31：向网络侧设备发送第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
所谓Uu RLC承载，是指Uu接口的协议栈中的RLC及其下层的承载，不包括RLC以上层。
可选的，所述第一Uu RLC承载的配置信息包括以下至少一项：RLC配置，和，媒体接入控制(Medium Access Control，MAC)配置，所述MAC配置包括以下至少一项：逻辑信道标识(Identifier，ID)、逻辑信道优先级和优先比特率(Prioritized Bit Rate，PBR)。
可选的，所述第一Uu RLC承载为Uu SRB RLC承载或者Uu DRB RLC承载。
步骤32：接收所述网络侧设备发送的第一配置信息，所述第一配置信息包括：第一Uu RLC承载的配置信息，所述第一Uu RLC承载用于传输所述远端终端的Uu信令(signaling)。
本发明实施例中，中继终端向网络侧设备发送中继请求，以请求配置网络侧设备与中继终端之间的Uu RLC承载以专用于远端终端的Uu信令的传输，从而实现远端终端与网络侧设备之间的连接建立，以进行业务的正常传输。
本发明实施例中，所述远端终端的Uu信令包括所述远端终端发送给网络侧的上行Uu信令，和/或，所述网络侧设备发送给所述远端终端的下行Uu信令。
本发明实施例中，可选的，所述远端终端的连接管理方法还可以包括：
接收远端终端的上行Uu信令，并在所述第一Uu RLC承载上将所述上行Uu信令转发给网络侧设备，和/或，在所述第一Uu RLC承载上接收网络侧设备发送的所述远端终端的下行Uu信令，并转发给远端终端，从而实现远端终端的Uu信令的传输。
本发明实施例中，可选的，上行Uu信令和下行Uu信令可以在同一个Uu RLC承载的不同方向进行，由双向确认模式(Acknowledged Mode，AM)RLC实体执行。当然，也不排除上行Uu信令和下行Uu信令采用不同的Uu RLC承载的方式。
在本发明的其他一些实施例中，中继终端也可以不通过Uu RLC承载发送远端终端的Uu信令，而是以容器(container)的方式，将远端终端的Uu信令携带在自己的RRC消息中传输给网络侧设备。该种方式下，可选的，所述RRC消息中可以携带以下信息中的至少一项：远端终端的标识，远端终端的Uu信令的类型的指示信息，Uu信令的类型包括如下至少一项：无线资源控制(RRC)信令和非接入层(None Access Stratum，NAS)信令。
本发明实施例中，与中继终端连接的远端终端的个数可以是一个，也可以是多个，若所述远端终端的个数大于一个，可选的，不同的所述远端终端的Uu信令采用不同的第一Uu RLC承载传输；或者，不同的所述远端终端的Uu信令采用相同的第一Uu RLC承载传输。
为了区分不同的远端终端，可选的，一指示信息携带在所述Uu信令中，或者与Uu信令一起发送(例如携带在层二协议数据单元(Protocol Data Unit，PDU)头部)，该指示信息用于指示所述远端终端的身份，例如为远端终端的标识。可选的，是否携带或发送所述指示信息由所述网络侧设备配置。
本发明实施例中，所述远端终端的Uu信令的类型可以为一种，也可以为多种，例如所述远端终端的Uu信令包括：无线资源控制(RRC)信令和非接入层(None Access Stratum，NAS)信令。
本发明实施例中，远端终端的Uu RRC信令，是指远端终端和网络侧设备之间的RRC信令，远端终端的Uu NAS信令，是指远端终端和它的核心网节点接入和移动性管理功能(Access and Mobility Management Function，AMF)之间的NAS信令，信令都是端到端的，直接在两个端点之间传输，默认SRB 启动加密和完整性保护。
本发明实施例中，可选的，同一所述远端终端的不同类型的Uu信令采用相同的第一Uu RLC承载传输；或者，同一所述远端终端的不同类型的Uu信令采用不同的第一Uu RLC承载传输。
为了区分不同的信令的类型，可选的，一指示信息携带在所述Uu信令中，或者与Uu信令一起发送(例如携带在层二协议数据单元(PDU)头部)，该指示信息用于指示所述Uu信令的业务的类型。可选的，是否携带或发送所述指示信息由所述网络侧设备配置。
本发明实施例中，可选的，所述第一中继请求包括以下信息中的至少一项：中继指示信息，所述中继指示信息用于指示当前消息为所述第一中继请求；所述远端终端的标识；所述远端终端的业务信息；中继信息。
可选的，所述业务信息包括以下至少一项：
服务质量流标识(QoS flow ID，QFI)；
QoS配置文件(profile)；QoS配置文件例如包含以下至少一项：业务时延预算(packet delay budge，PDB)，包错误率(packet error rate，PER)，优先级(priority)，业务类型(如保证比特率(Guaranteed bit rate，GBR)，non-GBR，delayCriticalGBR等)，平均窗口大小(AveragingWindow)，最大数据突发量(MaxDataBurstVolume)；
QoS参数或QoS指示；QoS参数还可以以标准化的QoS指示(indicator)来替代，即用标准化QoS indicator可以在规范表格中，找到对应的QoS profile参数值；
最大流比特率(Maximum flow bit rate，MBR/MFBR)；
保证流比特率(Guaranteed flow bit rate，GBR/GFBR)。
本发明实施例中，中继终端可以通过与远端终端的交互过程(例如发现过程或连接建立过程)，获得远端终端即将通过中继功能发送的业务信息。
本发明实施例中，当中继终端向网络侧设备上报远端终端的业务信息时，可选的，还可以同时携带远端终端的标识，从而可以让网络侧设备区分业务信息为哪个远端终端的业务信息，从而更好的提供配置。
可选的，所述中继信息包括以下至少一项：
支持的中继跳数；
中继架构选项(L2/L3中继)；
是否支持多连接中继架构。
(一)下面对Uu接口上的请求/上报进行说明
1、对于空闲(idle)状态的中继终端
如果中继终端处于空闲状态，则中继终端需要先进入RRC连接状态，因为只有RRC连接状态才能够为远端终端中转数据和提供中继服务功能。中继终端可以在进入RRC连接态的过程中，向网络侧发送第一中继请求，也可以在RRC连接建立成功之后，以专门的信令过程向网络侧发送第一中继请求，可行的方案如下：
1)本发明实施例中，可选的，若中继终端处于空闲状态，在发送给所述网络侧设备的RRC连接建立请求中携带所述第一中继请求。
采用RRC连接建立请求携带所述第一中继请求时，由于RRC连接建立请求一般采用随机接入(Random Access Channel，RACH)过程的MsgA或者Msg3进行携带，这种携带方法决定了所能携带的信令容量是受限的，不能携带太多内容，一般可以携带中继指示信息(relay indicator)，例如通过1比特(bit)原因值(cause value)携带，用于指示当前消息为所述第一中继请求。
2)在发送给所述网络侧设备的RRC连接建立完成中携带所述第一中继请求。
采用RRC连接建立完成携带所述第一中继请求时，RRC连接建立完成的容量不受限，可以携带一个中继域(relay field)，中继域为True代表这是一个为中继功能发起的连接建立，False代表这是一个普通终端的连接建立，即通过设置特殊域向网络侧请求中继功能的相关配置。可选的，还可以携带以下至少一项：远端终端的标识，远端终端的业务信息等。远端终端的标识用于指示为哪个终端请求中继操作。
3)在RRC连接建立完成之后，采用第一上行信令发送所述第一中继请求。
在RRC连接建立完成之后，采用第一上行信令发送所述第一中继请求时，所述第一上行信令可以是复用的现有的上行信令，也可以是新的上行信令。 复用现有上行信令，例如可以使用现有的副链路UE信息(SidelinkUEInformation)信令，或者UE协助信息(UEAssistanceInformation)，新的信令，例如可以为中继信息(RelayInformation)等。同样的，第一上行信令的容量不受限，可以携带具体的中继信息(relay info)，向网络侧请求中继功能的相关配置。可选的，中继信息包括以下至少一项：中继指示信息，远端终端的标识，远端终端的业务信息等。携带远端终端的业务信息，则可以向网络侧入请求完整的中继功能的相关配置，例如同时请求业务数据的Uu数据无线承载(Data Radio Bearer，DRB)RLC承载。
4)在本发明的一些实施例中，也可以先在1)或2)中携带少量的中继信息，例如，告知网络侧设备所述中继终端是为了中继功能进入的RRC连接状态，该中继信息例如可以通过原因值(cause value)携带特殊值(如中继指示(relay indicator)信息)，或者，1bit中继域(relay field)设置为True，或者携带远端终端的UE标识，便于网络侧进行基础的中继功能信令承载或者默认数据承载配置；后续再以专门信令过程，上报详细的需要中继的业务的具体信息，向网络侧请求业务数据相关的配置。
2、对于非激活(inactive)状态的中继终端
若所述中继终端处于非激活(inactive)状态，则中继终端需要先进入RRC连接状态，因为只有RRC连接状态才能够为远端终端中转数据和提供中继服务功能。中继终端可以在进入RRC连接态的过程中，向网络侧发送第一中继请求，也可以在RRC连接建立成功之后，以专门的信令过程向网络侧发送第一中继请求，可行的方案如下：
1)在发送给所述网络侧设备的RRC连接恢复请求中携带所述第一中继请求。
采用RRC连接恢复请求携带所述第一中继请求时，由于RRC连接恢复请求一般采用随机接入(RACH)过程的MsgA或者Msg3进行携带，这种携带方法决定了所能携带的信令容量是受限的，不能携带太多内容，一般可以携带中继指示信息(relay indicator)，例如通过1比特(bit)原因值(cause value)携带，用于指示当前消息为所述第一中继请求。
2)在发送给所述网络侧设备的RRC连接恢复完成中携带所述第一中继 请求；
采用RRC连接恢复完成携带所述第一中继请求时，RRC连接恢复完成的容量不受限，可以携带一个中继域(relay field)，中继域为True代表这是一个为中继功能发起的连接建立，False代表这是一个普通终端的连接建立，即通过设置特殊域向网络侧请求中继功能的相关配置。可选的，还可以携带以下至少一项：远端终端的标识，远端终端的业务信息等。远端终端的标识用于指示为哪个终端请求中继操作。
3)在RRC连接恢复完成之后，采用第一上行信令发送所述第一中继请求。
在RRC连接恢复完成之后，采用第一上行信令发送所述第一中继请求时，所述第一上行信令可以是复用的现有的上行信令，也可以是新的上行信令。复用现有上行信令，例如可以使用现有的副链路UE信息(SidelinkUEInformation)信令，或者UE协助信息(UEAssistanceInformation)，新的信令，例如可以为中继信息(RelayInformation)等。同样的，第一上行信令的容量不受限，可以携带具体的中继信息(relay info)，向网络侧请求中继功能的相关配置。可选的，中继信息包括以下至少一项：中继指示信息，远端终端的标识，远端终端的业务信息等。携带远端终端的业务信息，则可以向网络侧入请求完整的中继功能的相关配置，例如同时请求业务数据的Uu DRB RLC承载。
4)在本发明的一些实施例中，也可以先在1)或2)中携带少量的中继信息，例如，告知网络侧设备所述中继终端是为了中继功能进入的RRC连接状态，该中继信息例如可以通过原因值(cause value)携带特殊值(如中继指示(relay indicator))，或者，1bit中继域(relay field)设置为True，或者携带远端终端的UE标识，便于网络侧进行基础的中继功能信令承载或者默认数据承载配置；后续再以专门信令过程，上报详细的需要中继的业务的具体信息，向网络侧请求业务数据相关的配置。
3、对于RRC连接状态的中继终端
若所述中继终端处于RRC连接状态，则不需要进行任何状态的转换，所述中继终端可以采用第一上行信令发送所述第一中继请求，可行的方案如下：
1)中继终端以一步(one-step)的方式，向网络侧一次性请求详细的相关配置信息；配置既包含信令承载信息也包含数据承载信息；为了一次性获得所有信息，优选的，需要向网络侧上报中继指示信息和远端终端的标识、详细的业务信息、详细的中继信息，其中中继指示用于说明这是一个中继功能相关的上报。
2)中继终端以两步(two-step)的方式，先向网络侧请求建立信令承载相关信令的配置信息，也可以同时请求建立默认数据承载的配置信息，第二步再次向网络侧请求专用数据承载信息用于数据传输；分两步请求，则第一步的上报信息可以较为粗略，例如仅包含中继指示和远端终端的标识，用于说明这是一个中继基础配置请求，第二步再向网络侧上报详细业务信息、详细中继信息。
采用第一上行信令发送所述第一中继请求时，所述第一上行信令可以是复用的现有的上行信令，也可以是新的上行信令。复用现有上行信令，例如可以使用现有的副链路UE信息(SidelinkUEInformation)信令，或者UE协助信息(UEAssistanceInformation)，新的信令，例如可以为中继信息(RelayInformation)等。同样的，第一上行信令的容量不受限，可以携带具体的中继信息(relay info)，向网络侧请求中继功能的相关配置。可选的，中继信息包括以下至少一项：中继指示信息，远端终端的标识，远端终端的业务信息等。携带远端终端的业务信息，则可以向网络侧入请求完整的中继功能的相关配置，例如同时请求业务数据的Uu DRB RLC承载。
传输远端终端的Uu信令时，两端分别为远端终端和网络侧设备(服务小区/基站)，传输路径为上行Uu信令从远端终端先经过PC5接口到中继终端，再由中继终端的Uu接口到网络侧设备，下行Uu信令的传输过程反之。也就是说远端终端的Uu信令需要经过两段空口传输，在这两段空口上都需要配置相应的管道进行承载。
Uu接口是指中继终端和网络侧设备(服务小区/基站)之间的接口。
PC5接口是指远端终端和中继终端之间的sidelink接口。
(二)PC5接口的配置
上述实施例中，对Uu接口的管道的承载进行了说明，下面对PC5接口 的管道的承载进行说明。
PC5接口是指中继终端和远端终端之间的使用sidelink协议通信的接口。
本发明实施例中，可选的，所述向网络侧设备发送第一中继请求之前还包括：与所述远端终端之间进行中继相关的发现过程和/或连接建立过程(Relay related discovery/link establishment)。
对于一个远端终端和一个中继终端，在经过基本的中继功能授权的情况下，可以进行中继相关的发现过程和/或连接建立过程。可选的，中继功能授权过程由核心网控制，可以是远端终端和/或中继终端各自在连接网络的状态下，与网络侧进行的授权和中继信息获得过程。也可以是远端终端预配置获得授权和中继信息。
在获得授权之后，网络侧也可以通过系统信息块(System Information Block，SIB)、专用信令或预配置信息，给远端终端和/或中继终端各自配置进行中继操作的条件(例如，中继终端需要为信号强度超过预设阈值的终端)。当各自满足进行中继操作的条件之后，远端终端和中继终端之间可以进行中继相关的发现过程和/或连接建立过程。
可选的，所述发现过程和/或连接建立过程使用PC5链路(link)的信令过程完成，进一步可选的，所述发现过程和/或连接建立过程使用PC5链路的信令无线承载(SRB)进行。
中继相关的发现过程和/或连接建立过程，可以是两个过程，也可以合并成一个过程。两个过程即远端终端和中继终端之间先进行相互发现过程，再进行连接建立过程。一个过程即远端终端和中继终端之间直接进行中继相关的连接建立过程过程。无论是哪个过程，均使用PC5链路(link)的SRB完成。
在PC5接口中，支持四种SRB：
SRB0：用于未开启安全的广播地址PC5-S信令传输，例如direct communication request(直接通信请求)；
SRB1：用于启动安全的PC5-S信令传输，例如Security establishment/complete(安全建立/完成)；
SRB2：用于启动安全之后PC5-S信令传输，例如心跳包等；
SRB3：用于启动安全之后PC5-RRC信令传输，例如能力信息，重配置信息等。
中继相关的发现过程和/或连接建立过程中，例如第一条广播地址的发现请求和/或建立请求消息，以未开启安全的SRB0进行传输，接着进行安全建立过程，以SRB1传输安全建立相关的信令(一般为安全建立请求和安全建立完成消息)，安全建立请求消息具有完整性保护没有加密，而安全建立完成消息有加密也有完整性保护。之后以SRB2传输具有安全保护的高层消息，指需要开启加密和完整性保护的PC5-S层(layer)信令，例如可以包括发现响应消息，中继连接建立完成消息等。
在进行完上述中继相关的发现过程和/或连接建立过程之后，若中继终端确定自己要为远端终端进行中转数据服务，则可以向网络侧设备发送上述第一中继请求。
本发明实施例中，可选的，所述远端终端的连接管理方法还包括：
步骤33：根据中继终端侧的第一sidelink RLC承载的配置信息，与所述远端终端之间建立第一sidelink RLC承载，所述第一sidelink RLC承载用于传输所述远端终端的Uu信令，所述第一sidelink RLC承载与所述第一Uu RLC承载具有映射关系。
所谓sidelink RLC承载，是指PC5接口的协议栈中的RLC及其下层的承载，不包括RLC以上层。
所述第一sidelink RLC承载的配置信息包括以下至少一项：RLC配置；媒体接入控制(MAC)配置，所述MAC配置包括以下至少一项：逻辑信道标识(ID)、逻辑信道优先级和优先比特率(Prioritized Bit Rate，PBR)。
可选的，所述第一sidelink RLC承载为sidelink DRB承载或者sidelink SRB RLC承载。
本发明实施例中，中继终端和远端终端之间建立sidelink RLC承载，从而通过该sidelink RLC承载向中继终端可以接收远端终端发送的Uu信令，并通过第一Uu RLC承载转发给网络侧设备，或者，中继终端接收网络侧设备通过第一Uu RLC承载发送的Uu信令，并通过sidelink RLC承载转发给远端终端，以实现远端终端与网络侧设备之间的Uu信令的传输。
远端终端的Uu信令可以包括：Uu RRC信令和NAS信令。
为了承载远端终端的Uu RRC信令和NAS信令，需要配置新的RLC承载，有如下两种方式：
一种是配置SRB4和SRB5对应的sidelink RLC承载分别用于远端终端的Uu RRC信令和NAS信令在PC5接口上的传输；SRB一般采用AM传输模式，有默认的序列号(Sequence Number，SN)长度等，SRB可以采取默认配置或者指定配置；
另一种是配置DRB0和DRB1对应的sidelink RLC承载用于远端终端的Uu RRC信令和NAS信令在PC5接口上的传输；用于传输信令的DRB采用AM传输模式，与SRB的SN长度相等的SN配置等，DRB可以采取默认配置(可等于默认SRB配置)或者指定配置。
SRB RLC承载和DRB RLC承载的最大差别为是否可以体现出承载的是信令信息，例如直接可以由RLC承载ID区间，或者逻辑信道标识(Logical Channel Identify，LCID)区间的不同知道是SRB信息。否则如果没有区分，都属于相同区间，也可以通过配置优先级较高，PBR无限大来实现信令的优先传输。
本发明实施例中，可选的，所述与所述远端终端之间建立第一sidelink RLC承载之后还包括：
通过所述第一sidelink RLC承载接收所述远端终端的上行Uu信令，并通过所述第一Uu RLC承载将所述上行Uu信令转发给所述网络侧设备；
和/或
通过所述第一Uu RLC承载接收所述网络侧设备发送的所述远端终端的下行Uu信令，并通过所述第一sidelink RLC承载将所述下行Uu信令转发给所述远端终端。
所述上行Uu信令可以为以下至少一项：RRC连接建立请求，RRC连接建立完成，重配置完成，Uu接口的现有的各种上行RRC信令，以及，相关NAS信令。
本发明实施例中，可选的，上行Uu信令和下行Uu信令可以在同一个sidelink RLC承载的不同方向进行，由双向确认模式(AM)RLC实体执行。 当然，也不排除上行Uu信令和下行Uu信令采用不同的sidelink RLC承载的方式。
本发明实施例中，可选的，所述第一sidelink RLC承载与所述第一Uu RLC承载的映射关系由所述网络侧设备配置或者由所述中继终端配置。
所述第一Uu RLC承载与所述第一sidelink RLC承载可以是一对多的映射关系，也可以是一对一的映射关系。
本发明实施例中，用于承载信令的第一sidelink RLC承载的建立或者配置，可以采取隐式或者显式的方式：
所谓隐式，是指一旦远端终端和中继终端之间确认可以开始中继操作，则各自按照默认的配置建立第一sidelink RLC承载，之后进行使用；
所谓显式，是指通过信令交互的方式，增加第一sidelink RLC承载以及相关配置，这个配置一般是中继终端发送给远端终端，一般是中继终端接受为远端终端进行中继功能之后或者同时，发起的配置，也可能是中继终端在接收到网络侧的用于接受远端终端的中继功能请求之后，或者是中继终端接收到网络侧的Uu RLC承载配置之后，根据Uu RLC承载配置。
PC5接口的远端终端的Uu信令的承载配置可以与Uu接口的配置保持一致，也可以独立分别配置，例如Uu接口使用DRB RLC承载，PC5接口使用SRB RLC承载。
还需要说明的是，中继终端如果连接多个远端终端情况下，因为PC5链接(link)是针对每个远端终端独立维护的，则在每个远端终端的PC5 link上可以都使用DRB0 RLC bearer和DRB1 RLC bearer来承载Uu RRC和NAS信令，link是不同的端点，中继终端可以区分他们。并且中继终端需要自己维护每一个远端终端的DRB0 RLC bearer和DRB1 RLC bearer与Uu接口上的DRB32/33 RLC bearer(第一个接入的远端终端)，DRB34/35 RLC bearer(第二个接入的远端终端)…的映射关系。
本发明实施例中，可选的，所述与所述远端终端之间建立第一sidelink RLC承载之前还包括：
向所述远端终端发送所述远端终端侧的所述第一sidelink RLC承载的配置信息。
需要说明的是，虽然中继终端和远端终端之间建立sidelink RLC承载，但是在中继终端侧和远端终端侧的配置信息可能不同，例如，一方为发送端的配置，一方为接收端的配置。举例来说，把远端终端到中继终端这个方向称为上行，中继终端到远端终端这个方向称为下行。那么在远端终端侧配置的是上行发送参数和下行接收参数，而在中继终端侧配置的是下行发送参数和上行接收参数。因此参数具体内容是不一样的，但是配置内容两端是协调的，例如每个方向接收和发送的RLC序列号(SN)必须一致，上行和下行各自的参数例如RLC SN允许一样或者不一样，整体配合起来完成两个方向的收发操作。
本发明实施例中，可选的，所述第一sidelink RLC承载的配置信息采用以下方式中的至少一项确定：
1)所述网络侧设备配置；
其中，由网络侧设备配置时，网络侧设备将所述第一sidelink RLC承载的配置信息发送给中继终端，然后由中继终端转发给远端终端。
在本发明的一些实施例中，可选的，所述网络侧设备可以同时配置所述第一Uu RLC承载和所述第一sidelink RLC承载。也就是说，所述网络侧设备向中继终端发送的第一配置信息中可以包括：第一Uu RLC承载的配置信息，和，所述第一sidelink RLC承载的配置信息。
在本发明的另外一些实施例中，可选的，所述中继终端也可以单独向网络侧设备发送第二中继请求，用于请求所述网络侧设备为远端终端的Uu信令的传输配置sidelink RLC承载。此时，所述网络侧设备可以单独向中继终端发送所述第一sidelink RLC承载的配置信息。
2)所述中继终端配置；
3)协议约定。
本发明实施例中，可选的，所述中继终端配置包括以下之一或者组合：
1)所述中继终端在接受为所述远端终端提供中继服务之后配置；
本发明实施例中，可选的，中继终端向网络侧设备发送第一中继请求之前还包括：接收远端终端发送的中继请求，所述中继请求用于请求中继终端为所述远端终端提供中继服务。当中继终端接受为所述远端终端提供中继服 务之后，可以配置所述第一sidelink RLC承载的配置信息。例如根据协议约定的默认参数进行配置。
2)所述中继终端在所述网络侧设备接受本终端作为中继终端之后配置；
本发明实施例中，可选的，网络侧设备在接收到所述中继终端发送的第一中继请求之后，向中继终端发送第一Uu RLC承载的配置信息，所述第一Uu RLC承载的配置信息中可以携带中继功能确认信息，用于确认接受该终端作为中继终端。或者，所述第一Uu RLC承载的配置信息中也可以不携带上述中继功能确认信息，中继终端在接收到第一Uu RLC承载的配置信息之后，则默认为所述网络侧设备接受本终端作为中继终端。在所述网络侧设备接受本终端作为中继终端之后，所述中继终端可以配置所述第一sidelink RLC承载的配置信息。例如根据第一Uu RLC承载的配置信息进行配置。
3)所述中继终端接收到所述第一Uu RLC承载的配置信息之后配置；
可选的，所述中继终端根据第一Uu RLC承载的配置信息进行配置。
4)所述中继终端根据所述第一Uu RLC承载的配置信息配置；
5)所述中继终端根据协议的默认参数配置。
其中，上述1)-3)是对中继终端配置所述第一sidelink RLC承载的配置时机进行限定，而，4)和5)是对中继终端的配置所述第一sidelink RLC承载的配置方式进行的限定。
上述实施例中提到，中继终端可以通过与远端终端之间建立的第一sidelink RLC承载接收远端终端发送的Uu信令，或者，将网络侧发送给远端终端的Uu信令发送给远端终端，在本发明的其他一些实施例中，中继终端和远端终端之间也可以通过sidelink RRC消息传输所述远端终端的Uu信令。即，所述远端终端的连接管理方法还包括：通过sidelink RRC消息与所述远端终端之间传输所述远端终端的Uu信令。该种方案中，可以利用现有的sidelink RRC消息携带Uu信令，实现简单。该过sidelink RRC消息是指远端终端和中继终端之间的sidelink接口的RRC消息，也可以成为PC5-RRC消息。
可选的，所述sidelink RRC消息中至少包括所述Uu信令的类型的指示信息，所述类型包括以下至少一项：RRC信令和NAS信令。
本发明实施例中，可选的，所述第一配置信息还包括：第一Uu DRB RLC承载的配置信息，所述第一Uu DRB RLC承载用于传输所述远端终端的业务数据。
也就是说，网络侧设备在接收到中继终端发送的第一中继请求之后，可以同时配置：用于传输远端终端的Uu信令的第一Uu RLC承载，以及，用于传输远端终端的业务数据的第一Uu DRB RLC承载。其中，第一Uu RLC承载可以是Uu SRB RLC承载或者Uu DRB RLC承载。
上述第一Uu DRB RLC承载可以是网络侧设备为远端终端先建立的一条默认的Uu DRB RLC承载。例如，若第一中继请求中未携带所述远端终端的业务信息，即所述网络侧设备并不清楚远端终端的业务信息的具体情况时，可以先为远端终端建立该默认的Uu DRB RLC承载，以用于传输一些简单的业务数据。该默认的Uu DRB RLC承载，用于一些特殊情况的数据传输，例如专用符合QoS需求的DRB承载还未建立时的一些数据传输，或者QoS需求不明确，或者找不到对应QoS的映射的DRB RLC承载时，都可以使用默认DRB RLC承载，传输远端终端的业务数据。
当然，第一中继请求中也可以携带所述远端终端的业务信息，此时，上述第一Uu DRB RLC承载可以是符合所述远端终端的业务信息的QoS需求的Uu DRB RLC承载。
在本发明的其他一些实施例中，若网络侧设备在配置第一Uu RLC承载时，没有配置用于传输远端数据的Uu DRB RLC承载，或者，仅配置了默认的Uu DRB RLC承载，此时，可选的，所述向网络侧设备发送第一中继请求之后还包括：
向所述网络侧设备发送第三中继请求，所述第三中继请求用于请求所述网络侧设备为所述远端终端的业务数据的传输配置Uu RLC承载；
接收所述网络侧设备发送的第二Uu DRB RLC承载的配置信息，所述第二Uu DRB RLC承载用于传输所述远端终端的业务数据。
也就是说，所述第二Uu DRB RLC承载是符合所述远端终端的业务信息的QoS需求的Uu DRB RLC承载。
可选的，所述第三中继请求包括以下信息中的至少一项：所述远端终端 的标识；所述远端终端的业务信息。
可选的，所述业务信息包括以下至少一项：服务质量流标识(QFI)；QoS配置文件；QoS参数或QoS指示；最大流比特率(MBR/MFBR)；保证流比特率(GBR/GFBR)。
可选的，所述中继信息包括以下至少一项：支持的中继跳数；中继架构选项；是否支持多连接中继架构。
请参考图4，本发明实施例还提供一种远端终端的连接管理方法，应用于远端终端，所述方法包括：
步骤41：通过与中继终端之间建立的第一sidelink RLC承载，或者，通过sidelink RRC消息，与所述中继终端之间传输所述远端终端的Uu信令。
所谓sidelinkRLC承载，是指sidelink接口(即PC5接口)的协议栈中的RLC及其下层的承载，不包括RLC以上层。
可选的，所述第一sidelink RLC承载为sidelink DRB承载或者sidelink SRB RLC承载。
本发明实施例中，远端终端通过第一sidelink RLC承载或者sidelink RRC消息，与中继终端之间传输远端终端的Uu信令，中继终端可以完成远端终端和网络侧设备之间的Uu信令的转发，从而实现远端终端与网络侧设备之间的连接建立，以进行业务的正常传输。
本发明实施例中，所述远端终端的Uu信令包括所述远端终端发送给网络侧的上行Uu信令，和/或，所述网络侧设备发送给所述远端终端的下行Uu信令。
本发明实施例中，通过与中继终端之间建立的第一sidelink RLC承载与所述中继终端之间传输所述远端终端的Uu信令包括：
在第一sidelink RLC承载上将所述远端终端的上行Uu信令发送给中继终端，和/或，在第一sidelink RLC承载上接收所述中继终端转发的所述远端终端的下行Uu信令。
本发明实施例中，可选的，上行Uu信令和下行Uu信令可以在同一个sidelink RLC承载的不同方向进行，由双向确认模式(AM)RLC实体执行。当然，也不排除上行Uu信令和下行Uu信令采用不同的sidelink RLC承载的 方式。
在本发明的其他一些实施例中，远端终端也可以以容器(container)的方式，将远端终端的Uu信令携带在自己的RRC消息中传输给中继终端。该种方式下，可选的，所述RRC消息中可以携带以下信息中的至少一项：远端终端的标识，远端终端的Uu信令的类型的指示信息，Uu信令的类型包括如下至少一项：无线资源控制(RRC)信令和非接入层(None Access Stratum，NAS)信令。
本发明实施例中，与中继终端连接的远端终端的个数可以是一个，也可以是多个，若所述远端终端的个数大于一个，可选的，不同的所述远端终端的Uu信令采用不同的第一sidelink RLC承载传输；或者，不同的所述远端终端的Uu信令采用相同的第一sidelink RLC承载传输。
为了区分不同的远端终端，可选的，一指示信息携带在所述Uu信令中，或者与Uu信令一起发送(例如携带在层二协议数据单元(PDU)头部)，该指示信息用于指示所述远端终端的身份，例如为远端终端的标识。可选的，是否携带或发送所述指示信息由所述网络侧设备配置。
本发明实施例中，所述远端终端的Uu信令的类型可以为一种，也可以为多种，例如所述远端终端的Uu信令包括：无线资源控制(RRC)信令和非接入层(None Access Stratum，NAS)信令。
本发明实施例中，远端终端的Uu RRC信令，是指远端终端和网络侧设备之间的RRC信令，远端终端的Uu NAS信令，是指远端终端和它的核心网节点接入和移动性管理功能(Access and Mobility Management Function，AMF)之间的NAS信令，信令都是端到端的，直接在两个端点之间传输。
本发明实施例中，可选的，同一所述远端终端的不同类型的Uu信令采用相同的第一sidelink RLC承载传输；或者，同一所述远端终端的不同类型的Uu信令采用不同的第一sidelink RLC承载传输。
为了区分不同的信令的类型，可选的，一指示信息携带在所述Uu信令中，或者与Uu信令一起发送(例如携带在层二协议数据单元(PDU)头部)，该指示信息用于指示所述Uu信令的业务的类型。可选的，是否携带或发送所述指示信息由所述网络侧设备配置。
本发明实施例中，所述通过与中继终端之间建立的第一sidelink RLC承载，与所述中继终端之间传输所述远端终端的Uu信令之前还包括：
根据所述远端终端侧的第一sidelink RLC承载的配置信息，与所述中继终端之间建立所述第一sidelink RLC承载。
可选的，所述第一sidelink RLC承载的配置信息采用以下方式确定：网络侧设备配置；所述中继终端配置；协议约定。
由网络侧设备配置时，网络侧设备可以将第一sidelink RLC承载的配置信息发送给中继终端，中继终端再将远端终端侧的第一sidelink RLC承载的配置信息发送给远端终端。
所述第一sidelink RLC承载的配置信息包括：RLC配置；MAC配置，所述MAC配置包括以下至少一项：逻辑信道标识、逻辑信道优先级和优先比特率。
本发明实施例中，可选的，与中继终端之间建立的第一sidelink RLC承载之前还包括：与所述远端终端之间进行中继相关的发现过程和/或连接建立过程。可选的，所述发现过程和/或连接建立过程使用PC5链路的信令无线承载进行。具体的过程可参见上述中继终端侧的描述。
本发明实施例中，可选的，所述方法还包括：接收所述中继终端转发的第一Uu承载的配置信息，所述第一Uu承载的配置信息仅包括PDCP层及以上的配置信息。
请参考图5，本发明实施例还提供一种远端终端的连接管理方法，应用于网络侧设备，所述方法包括：
步骤51：接收中继终端发送的第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
步骤52：根据所述第一中继请求，向所述中继终端发送第一配置信息，所述第一配置信息包括：第一Uu RLC承载的配置信息，所述第一Uu RLC承载用于传输所述远端终端的Uu信令。
所谓Uu RLC承载，是指Uu接口的协议栈中的RLC及其下层的承载，不包括RLC以上层。
可选的，所述第一Uu RLC承载的配置信息包括以下至少一项：RLC配 置，和，媒体接入控制(MAC)配置，所述MAC配置包括以下至少一项：逻辑信道标识(ID)、逻辑信道优先级和优先比特率(Prioritized Bit Rate，PBR)。
可选的，所述第一Uu RLC承载为Uu SRB RLC承载或者Uu DRB RLC承载。
本发明实施例中，网络侧设备根据中继终端发送的中继请求，配置网络侧设备与中继终端之间的Uu RLC承载以专用于远端终端的Uu信令的传输，从而实现远端终端与网络侧设备之间的连接建立，以进行业务的正常传输。
本发明实施例中，所述第一配置信息中还可以包括：用于显示告知所述中继终端可以进行中继服务的指示信息。
本发明实施例中，所述远端终端的Uu信令包括所述远端终端发送给网络侧的上行Uu信令，和/或，所述网络侧设备发送给所述远端终端的下行Uu信令。
本发明实施例中，可选的，所述远端终端的连接管理方法还可以包括：
接收中继终端在所述第一Uu RLC承载上发送的远端终端的上行Uu信令，和/或，在所述第一Uu RLC承载上向中继终端发送的所述远端终端的下行Uu信令。
本发明实施例中，可选的，上行Uu信令和下行Uu信令可以在同一个Uu RLC承载的不同方向进行，由双向确认模式(AM)RLC实体执行。当然，也不排除上行Uu信令和下行Uu信令采用不同的Uu RLC承载的方式。
本发明实施例中，可选的，所述远端终端的Uu信令包括以下至少一项：RRC信令和NAS信令。
网络侧设备在解析出远端终端的Uu RRC信令之后，对其进行处理，并执行相关的响应或者配置，在远端终端的Uu RRC信令的下行管道中，进行相关下行Uu RRC消息的传输。对远端终端的的NAS信令，网络侧设备解析出之后，为远端终端的建立专门的网络侧设备到核心网(例如AMF实体)的NAS信令通道，例如XG接口，用于传输远端终端的的NAS信令，下行NAS信令传输类似。
(三)下面对Uu接口的配置进行说明。
本发明实施例中，网络侧设备根据中继终端发送的第一中继请求中携带 内信息，提供相应的配置内容。
一般来说，如果中继终端只向网络侧上报了中继指示信息和/或远端终端标识，则网络侧此时只能知道中继终端即将要开始进行中继功能，但具体会中继哪些数据，是不清楚的，因此此时能提供的配置只有如下两类：
1)远端终端的Uu信令在中继终端的Uu接口上的承载方式和相关配置(即第一Uu RLC承载的配置信息)；
远端终端的Uu信令主要是保护如下两种：
一种是指远端终端与网络侧设备之间的RRC信令，例如RRC连接建立请求/命令/完成(RRC connection setup request，RRC connection setup，RRC connection setup complete)，RRC重配置/完成(RRC reconfiguration，RRC reconfiguration complete)等，这类消息在终端直接连接网络侧设备的情况下，是采用SRB1传输的。
第二种是指远端终端与核心网之间的NAS信令，例如业务请求，注册或者鉴权管理等；这类消息在终端直接连接网络侧设备的情况下，是采用SRB1中的RRC信令容器(Container)方式，或者建立SRB2专门用于NAS信令传输。
而由于此时远端终端不是直接连接网络侧设备，因此它的RRC信令和NAS信令，需要依靠中继终端的承载进行捎带，而中继终端的SRB1和SRB2是专门用于传输自己的RRC消息和NAS消息，不适合直接用于中继终端相关消息的传输。因此需要给远端终端的RRC消息和NAS消息采取可以与中继终端区分，也可以与其它远端终端区分的方式，进行传输。
这里网络侧需要给出相关的配置，主要包括如下方法：
第一种，建立专门的新SRB对应的Uu RLC承载，用于远端终端的RRC信令和NAS信令承载；
例如配置SRB4的Uu RLC承载(之所以从SRB4开始，因为SRB0用于中继终端自己的公共控制信道(Common Control Channel，CCCH)上的RRC信令传输，SRB1用于专用控制信道(Dedicated Control Channel，DCCH)RRC信令传输，SRB2用于NAS信令，SRB3用于辅小区组(Secondary Cell Group，SCG)RRC信令传输，均已占用)，SRB4用于远端终端的RRC信令承载， SRB5 RLC承载用于远端终端的NAS信令承载，在给中继终端重配置信令中分别添加SRB4 RLC承载和SRB5 RLC承载及其对应的配置信息(SRB采用AM传输模式，有默认的SN长度等)，以及指出SRB4 RLC承载和SRB5 RLC承载的传输内容分别为远端终端的RRC信令和NAS信令，或者不显式指出，采取默认或者标准规定的方式。
当中继终端支持不止一个远端终端时，可以为第二个接入的远端终端建立SRB6，SRB7 RLC承载用于RRC信令和NAS信令传输，指明每一条新建立的SRB与远端终端ID和RRC/NAS消息的映射关系。也可以直接复用SRB4 RLC承载和SRB5 RLC承载，用于所有远端终端的RRC消息和NAS消息传输。如果所有远端终端都复用一对SRB4 RLC承载和SRB5 RLC承载，则在信令里需要区分属于哪个远端终端，例如显式携带远端终端ID。
即，若所述远端终端的个数大于一个，不同的所述远端终端的Uu信令采用不同的第一Uu RLC承载传输；或者，不同的所述远端终端的Uu信令采用相同的第一Uu RLC承载传输。为了区分不同的远端终端，可选的，一指示信息携带在所述Uu信令中，或者与Uu信令一起发送(例如携带在层二协议数据单元(PDU)头部)，该指示信息用于指示所述远端终端的身份，例如为远端终端的标识。可选的，是否携带或发送所述指示信息由所述网络侧设备配置。
另外，为了节省SRB RLC承载个数，还可以将远端终端的RRC信令和NAS信令放在一个SRB RLC承载传输，两种方式：
显式携带格式指示：例如这是RRC信令/NAS信令；
将NAS信令封装在RRC信令里，例如以RRC消息UL Information Transfer/DL information Transfer分别用于封装上下行NAS消息。
总之，最简单的方式，是为每个远端终端的RRC消息和NAS消息配置不同的SRB RLC bearer承载，好处是管道划分清晰，从每个SRB RLC承载里解析出的数据属于哪个远端终端的RRC或者NAS十分清楚明确，不需要在每个信令里携带区分信息。如果在这种的基础上为了进一步节省SRB RLC承载数目，则可以考虑不同远端终端的信息复用，或者NAS和RRC在一条SRB RLC承载传输，则复用在一起的信令，如果属于不同远端终端，需要每个信 令携带远端终端ID以区分，如果属于不同类型，则还需要区分NAS/RRC类型。
即，同一所述远端终端的不同类型的Uu信令采用相同的第一Uu RLC承载传输；或者，同一所述远端终端的不同类型的Uu信令采用不同的第一Uu RLC承载传输。为了区分不同的信令的类型，可选的，一指示信息携带在所述Uu信令中，或者与Uu信令一起发送(例如携带在层二协议数据单元(PDU)头部)，该指示信息用于指示所述Uu信令的业务的类型。可选的，是否携带或发送所述指示信息由所述网络侧设备配置。
第二种，建立专门的DRB RLC bearer，用于远端终端的RRC信令和NAS信令承载；
例如配置DRB5 RLC bearer，用于远端终端的RRC信令承载，DRB6 RLC bearer用于远端终端的NAS信令承载，在给中继终端重配置信令中分别添加DRB5和SRB6及其对应的配置信息(用于传输信令的DRB RLC bearer一般采用AM传输模式，可以使用与SRB默认的SN长度相等的SN长度或者配置专门的SN长度等)，以及指出DRB5 RLC bearer和DRB6 RLC bearer的传输内容分别为远端终端的RRC信令和NAS信令，或者不显式指出，采取默认或者标准规定的方式。这里DRB5 RLC bearer和DRB6 RLC bearer仅是用于举例说明，因为需要跟中继终端自己的用于承载数据的DRB区分，如果已经建立了DRB1-4，则可以新建DRB5/6 RLC bearer。另外，也可以考虑预留现有的DRB给中继终端自己，例如中继终端使用0-31，其它远端终端从32，33开始。
当中继终端支持不止一个远端终端时，可以为第二个接入的远端终端建立DRB7，DRB8用于RRC信令和NAS信令传输，指明每一条新建立的DRB RLC bearer与远端终端ID和RRC/NAS消息的映射关系。也可以直接复用DRB5 RLC bearer和DRB6 RLC bearer，用于所有远端终端的RRC消息和NAS消息传输。如果所有远端终端都复用一对DRB5 RLC bearer和DRB6 RLC bearer，则在信令里需要区分属于哪个远端终端，例如显式携带远端终端ID。
另外，为了节省DRB RLC bearer个数，还可以将远端终端的RRC信令和 NAS信令放在一个DRB传输，两种方式：
显式携带格式指示：例如这是RRC信令/NAS信令；
将NAS信令封装在RRC信令里，例如以RRC消息UL Information Transfer/DL information Transfer分别用于封装上下行NAS消息。
总之，最简单的方式，是为每个远端终端的RRC消息和NAS消息配置不同的DRB RLC bearer承载，好处是管道划分清晰，从每个DRB RLC bearer里解析出的数据属于哪个远端终端的RRC或者NAS十分清楚明确，不需要在每个信令里携带区分信息。如果在这种的基础上为了进一步节省DRB RLC bearer数目，则可以考虑不同远端终端的信息复用，或者NAS和RRC在一条DRB RLC bearer传，则复用在一起的信令，如果属于不同远端终端，需要每个信令携带远端终端ID以区分，如果属于不同类型，则还需要区分NAS/RRC类型。
2)远端终端的数据在中继终端的Uu接口上可以使用的默认承载信息和配置；
由于远端终端接入中继终端是为了和网络侧进行数据交互，因此网络侧设备可以为远端终端先建立一条默认Uu DRB RLC承载，用于一些特殊情况的数据传输，例如专用符合QoS需求的DRB承载还未建立时的一些数据传输，或者QoS需求不明确，或者找不到对应QoS的映射DRB RLC承载时，都可以使用默认DRB RLC承载，传输远端终端数据。
默认DRB RLC bearer承载属于可选配置，也有可能先建立信令的承载管道，后续等业务需求上报之后，再进行数据DRB RLC承载配置。
即，本发明实施例中，可选的，所述第一配置信息还包括：第一Uu DRB RLC承载的配置信息，所述第一Uu DRB RLC承载用于传输所述远端终端的业务数据。也就是说，网络侧设备在接收到中继终端发送的第一中继请求之后，可以同时配置：用于传输远端终端的Uu信令的第一Uu RLC承载，以及，用于传输远端终端的业务数据的第一Uu DRB RLC承载。其中，第一Uu RLC承载可以是Uu SRB RLC承载或者Uu DRB RLC承载。
需要说明的是，由于远端终端Uu信令在中继终端的Uu接口传输时，中继终端只需要执行L2相关转发操作，即无论是SRB RLC承载还是DRB RLC 承载，他们都是只具有RLC/MA层及以下的协议栈和配置的，SRB RLC承载/DRB RLC承载最大的差别在于其RLC承载标识或者逻辑信道标识是否能体现出SRB或者DRB属性，即是否需要区分承载信令的RLC承载到底属于SRB范畴还是DRB范畴，区分的好处是可以对SRB属性的RLC承载有特殊的操作，例如处理优先级更高，有数据优先于普通Data传输，并且PBR(保证比特速率)默认可以无限大。如过不区分SRB/DRB属性，那也可以采取统一的RLC承载ID/LCID编号区间，但是为承载信令的RLC承载配置更高的优先级，和无限大PBR。
上述信令承载和/或默认数据承载建立好之后，远端终端的上下行RRC信令和NAS信令，以及简单的数据，可以进行Uu接口的传输。
本发明实施例中，可选的，所述方法还包括：向所述中继终端发送第一sidelink RLC承载的配置信息，所述第一sidelink RLC承载用于传输所述远端终端的Uu信令，所述第一sidelink RLC承载与所述第一Uu RLC承载具有映射关系。可选的，所述映射关系由所述网络侧设备配置。
进一步可选的，所述第一sidelink RLC承载的配置信息位于所述第一配置信息中。即所述网络侧设备同时配置所述第一Uu RLC承载和第一sidelink RLC承载的配置信息，并发送给中继终端。
在本发明的另外一些实施例中，所述向所述中继终端发送第一sidelink RLC承载的配置信息之前还包括：
接收所述中继终端发送的第二中继请求，所述第二中继请求用于请求所述网络侧设备为远端终端的Uu信令的传输配置sidelink RLC承载；
此时，所述网络侧设备根据所述第二中继请求，单独将第一sidelink RLC承载的配置信息发送给中继终端。
在本发明的其他一些实施例中，若网络侧设备在配置第一Uu RLC承载时，没有配置用于传输远端数据的Uu DRB RLC承载，或者，仅配置了默认的Uu DRB RLC承载，此时，可选的，所述接收中继终端发送的第一中继请求之后还包括：
接收所述中继终端发送的第三中继请求，所述第三中继请求用于请求所述网络侧设备为所述远端终端的业务数据的传输配置Uu RLC承载；
根据所述第三中继请求，向所述中继终端发送第二Uu DRB RLC承载的配置信息，所述第二Uu DRB RLC承载用于传输所述远端终端的业务数据。
也就是说，所述第二Uu DRB RLC承载是符合所述远端终端的业务信息的QoS需求的Uu DRB RLC承载。
可选的，所述第三中继请求包括以下信息中的至少一项：所述远端终端的标识；所述远端终端的业务信息。
可选的，所述业务信息包括以下至少一项：服务质量流标识(QFI)；QoS配置文件；QoS参数或QoS指示；最大流比特率(MBR/MFBR)；保证流比特率(GBR/GFBR)。
可选的，所述中继信息包括以下至少一项：支持的中继跳数；中继架构选项；是否支持多连接中继架构。
本发明实施例中，可选的，所述方法还包括：向所述中继终端发送所述网络侧设备与所述远端终端的第一Uu承载的配置信息，所述第一Uu承载的配置信息仅包括PDCP层及以上的配置信息。
本发明实施例中，在建立好PC5接口的特殊信令承载(指用于传输远端终端的RRC信令或者NAS信令的SRB/DRB RLC承载)之后，远端终端可以使用该SRB/DRB RLC承载，向网络侧设备发送RRC消息，例如发送RRC上行信令，其中在建立请求中携带特殊cause value，例如remote indicator，指示这是一个remote UE的接入，或者由于remote UE RRC消息是通过中继终端的RLC承载到达网络侧，网络侧可以知道这是一个远端终端，便于网络侧为远端终端进行特殊配置，特殊之处在于：
由于这是一个远端终端，与网络侧之间并没有直接连接，因此并不需要像普通接入终端一样配置远端终端的Uu L3无线承载，或者说对于SRB/DRB承载仅需要配置PDCP层及以上的配置参数，而RLC及以下的Uu配置不需要；
对远端终端进行特殊配置，例如关于远端终端的PC5 link的配置，主要包括Uu承载在PC5接口的RLC层及以下配置，远端终端向网络发送的数据在PC5 SLRB上如何映射等。
如上述所述，远端终端的RRC信令或者NAS信令，PDCP层及以上建立 的是端到端承载，远端终端<->网络侧设备，执行端到端的安全，加密和完整性保护，所有的信令过程类似于Uu终端，但配置信息有特殊性，发送方式是通过远端终端<->中继终端之间的RLC承载，中继终端<->网络侧设备之间的RLC承载进行上下行传输。
请参考图6，图6为本发明另一实施例的远端终端的管理方法的流程示意图，该方法包括：
步骤60：远端终端和中继终端之间进行中继相关的发现和/或连接建立过程；
详细过程请参见中继终端侧对该部分的描述。
步骤61：中继终端向基站(即上述网络侧设备)发送第一中继请求，所述第一中继请求用于请求所述基站进行中继功能相关的配置；
步骤62：基站向中继终端发送第一配置信息，所述第一配置信息包括：第一Uu RLC承载和第一sidelink RLC承载的配置信息，所述第一Uu RLC承载和第一sidelink RLC承载用于传输远端终端的Uu信令；
步骤63：中继终端将远端终端侧的第一sidelink RLC承载的配置信息发送给远端终端；
当第一sidelink RLC承载的配置需要根据Uu RLC承载的配置生成，或者需要等网络侧接纳远端终端之后才能配置，等这些情况下，步骤63需要在步骤62之后接续发生。而也不排除步骤63可以在完成步骤60之后，即中继终端接受为远端终端提供中继服务时，就进行第一sidelink RLC的配置。这样Uu接口和PC5接口并行执行，节省时延。
步骤64：远端终端在第一sidelink RLC承载上发送远端终端的上行Uu信令；
步骤65：中继终端接收到远端终端的上行Uu信令之后，在第一Uu RLC承载上发送远端终端的上行Uu信令；
步骤66：若远端终端的上行Uu信令为上行NAS信令，基站将远端终端的上行NAS信令发送给核心网设备；
步骤67：基站接收核心网设备发送的远端终端的下行NAS信令；
步骤68：基站在第一Uu RLC承载上发送远端终端的下行Uu信令；
步骤69：中继终端接收到远端终端的下行Uu信令之后，在第一sidelink RLC承载上发送远端终端的下行Uu信令。
至此，打通了远端终端到网络侧的Uu RRC信令和NAS信令在sidelink接口和Uu接口的承载配置过程。远端终端可以使用配置好的承载进行Uu RRC信令和NAS信令的传输。信令传输的内容与现有UE过程类似，其中可能携带远端终端的特殊指示，告知基站或者核心网，这是一个远端终端。
请参考图7，本发明实施例还提供一种终端70，包括：
第一发送模块71，用于向网络侧设备发送第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
第一接收模块72，用于接收所述网络侧设备发送的第一配置信息，所述第一配置信息包括：第一Uu无线链路层控制协议RLC承载的配置信息，所述第一Uu RLC承载用于传输远端终端的Uu信令。
可选的，所述第一Uu RLC承载为Uu SRB RLC承载或者Uu DRB RLC承载。
可选的，若所述远端终端的个数大于一个；不同的所述远端终端的Uu信令采用不同的第一Uu RLC承载传输；或者，不同的所述远端终端的Uu信令采用相同的第一Uu RLC承载传输。
可选的，同一所述远端终端的不同类型的Uu信令采用相同的第一Uu RLC承载传输；或者，同一所述远端终端的不同类型的Uu信令采用不同的第一Uu RLC承载传输。
可选的，以下指示信息中的至少一项携带在所述Uu信令中或者与所述Uu信令同时发送：所述远端终端的标识；所述Uu信令的类型。
可选的，是否携带或发送所述指示信息由所述网络侧设备配置。
可选的，所述第一发送模块用于：
若所述中继终端处于空闲状态，在发送给所述网络侧设备的无线资源控制RRC连接建立请求中携带所述第一中继请求，或者，在发送给所述网络侧设备的RRC连接建立完成中携带所述第一中继请求，或者，在RRC连接建立完成之后，采用第一上行信令发送所述第一中继请求；
和/或
若所述中继终端处于非激活状态，在发送给所述网络侧设备的RRC连接恢复请求中携带所述第一中继请求，或者，在发送给所述网络侧设备的RRC连接恢复完成中携带所述第一中继请求；或者，在RRC连接恢复完成之后，采用第一上行信令发送所述第一中继请求；
和/或
若所述中继终端处于RRC连接状态，采用第一上行信令发送所述第一中继请求。
可选的，所述终端还包括：建立模块，用于根据所述中继终端侧的第一副链路sidelink RLC承载的配置信息，与所述远端终端之间建立第一sidelink RLC承载，所述第一sidelink RLC承载用于传输所述远端终端的Uu信令，所述第一sidelink RLC承载与所述第一Uu RLC承载具有映射关系。
可选的，所述映射关系由所述网络侧设备配置或者由所述中继终端配置。
可选的，所述第一sidelink RLC承载为sidelink DRB承载或者sidelink SRB RLC承载。
可选的，所述终端还包括：第二发送模块，用于向所述远端终端发送所述远端终端侧的所述第一sidelink RLC承载的配置信息。
可选的，所述第一sidelink RLC承载的配置信息采用以下方式中的至少一项确定：所述网络侧设备配置；所述中继终端配置；协议约定。
可选的，所述中继终端配置包括以下至少一项：
所述中继终端在接受为所述远端终端提供中继服务之后配置；
所述中继终端在所述网络侧设备接受本终端作为中继终端之后配置；
所述中继终端接收到所述第一Uu RLC承载的配置信息之后配置；
所述中继终端根据所述第一Uu RLC承载的配置信息配置；
所述中继终端根据协议的默认参数配置。
可选的，所述第一Uu RLC承载和第一sidelink RLC承载的配置信息包括以下至少一项：RLC配置；MAC配置，所述MAC配置包括以下至少一项：逻辑信道标识、逻辑信道优先级和优先比特率。
可选的，所述终端还包括：传输模块，用于通过sidelink RRC消息与所述远端终端之间传输所述远端终端的Uu信令。
可选的，所述sidelink RRC消息中至少包括所述Uu信令的类型的指示信息，所述类型包括以下至少一项：RRC信令和非接入层NAS信令。
可选的，所述第一配置信息还包括：第一Uu DRB RLC承载的配置信息，所述第一Uu DRB RLC承载用于传输所述远端终端的业务数据。
可选的，所述终端还包括：
第三发送模块，用于向所述网络侧设备发送第三中继请求，所述第三中继请求用于请求所述网络侧设备为所述远端终端的业务数据的传输配置Uu RLC承载；
第二接收模块，用于接收所述网络侧设备发送的第二Uu DRB RLC承载的配置信息，所述第二Uu DRB RLC承载用于传输所述远端终端的业务数据。
可选的，所述第一中继请求包括以下信息中的至少一项：
中继指示信息，所述中继指示信息用于当前消息为所述第一中继请求；
所述远端终端的标识；
所述远端终端的业务信息；
中继信息。
可选的，所述第三中继请求包括以下信息中的至少一项：
所述远端终端的标识；
所述远端终端的业务信息。
可选的，所述业务信息包括以下至少一项：QFI；QoS配置文件；QoS参数或QoS指示；MBR/MFBR；GBR/GFBR。
可选的，所述中继信息包括以下至少一项：支持的中继跳数；中继架构选项；是否支持多连接中继架构。
可选的，所述终端还包括：连接模块，用于与所述远端终端之间进行中继相关的发现过程和/或连接建立过程。
可选的，所述发现过程和/或连接建立过程使用PC5链路的信令无线承载进行。
本发明实施例提供的终端能够实现图3的方法实施例中终端实现的各个过程，为避免重复，这里不再赘述。
请参考图8，本发明实施例还提供一种终端80，包括：
传输模块81，用于通过与中继终端之间建立的第一sidelink RLC承载，或者，通过sidelink RRC消息，与所述中继终端之间传输所述远端终端的Uu信令。
可选的，所述第一sidelink RLC承载为sidelink DRB承载或者sidelink SRB RLC承载。
可选的，所述终端还包括：建立模块，用于根据所述远端终端侧的第一sidelink RLC承载的配置信息，与所述中继终端之间建立所述第一sidelink RLC承载。
可选的，所述第一sidelink RLC承载的配置信息采用以下方式确定：网络侧设备配置；所述中继终端配置；协议约定。
可选的，所述第一sidelink RLC承载的配置信息包括：RLC配置；MAC配置，所述MAC配置包括以下至少一项：逻辑信道标识、逻辑信道优先级和优先比特率。
可选的，所述sidelink RRC消息中至少包括：所述远端终端的Uu信令的类型的指示信息，所述类型包括以下至少一项：RRC信令和NAS信令。
可选的，所述终端还包括：连接模块，用于与所述中继终端之间进行中继相关的发现过程和/或连接建立过程。
可选的，所述发现过程和/或连接建立过程使用PC5链路的信令无线承载进行。
可选的，所述终端还包括：接收模块，用于接收所述中继终端转发的第一Uu承载的配置信息，所述第一Uu承载的配置信息仅包括PDCP层及以上的配置信息。
本发明实施例提供的终端能够实现图4的方法实施例中终端实现的各个过程，为避免重复，这里不再赘述。
请参考图9，本发明实施例还提供一种网络侧设备90，包括：
第一接收模块91，用于接收中继终端发送的第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
第一发送模块92，用于根据所述第一中继请求，向所述中继终端发送第一配置信息，所述第一配置信息包括：第一Uu RLC承载的配置信息，所述 第一Uu RLC承载用于传输所述远端终端的Uu信令。
可选的，所述第一Uu RLC承载为Uu SRB RLC承载或者Uu DRB RLC承载。
可选的，若所述远端终端的个数大于一个；不同的所述远端终端的Uu信令采用不同的第一Uu RLC承载传输；或者，不同的所述远端终端的Uu信令采用相同的第一Uu RLC承载传输。
可选的，同一所述远端终端的不同类型的Uu信令采用相同的第一Uu RLC承载传输；或者，同一所述远端终端的不同类型的Uu信令采用不同的第一Uu RLC承载传输。
可选的，以下指示信息中的至少一项携带在所述Uu信令中或者与所述Uu信令同时发送：所述远端终端的标识；所述Uu信令的类型。
可选的，是否携带或发送所述指示信息由所述网络侧设备配置。
可选的，所述终端还包括：第二发送模块，用于向所述中继终端发送第一sidelink RLC承载的配置信息，所述第一sidelink RLC承载用于传输所述远端终端的Uu信令，所述第一sidelink RLC承载与所述第一Uu RLC承载具有映射关系。
可选的，所述映射关系由所述网络侧设备配置。
可选的，所述第一sidelink RLC承载为sidelink DRB承载或者sidelink SRB RLC承载。
可选的，所述第一Uu RLC承载和第一sidelink RLC承载的配置信息包括以下至少一项：RLC配置；MAC配置，所述MAC配置包括以下至少一项：逻辑信道标识、逻辑信道优先级和优先比特率。
可选的，所述第一配置信息还包括：第一Uu DRB RLC承载的配置信息，所述第一Uu DRB RLC承载用于传输所述远端终端的业务数据。
可选的，所述终端还包括：
第二接收模块，用于接收所述中继终端发送的第三中继请求，所述第三中继请求用于请求所述网络侧设备为所述远端终端的业务数据的传输配置Uu RLC承载；
第三发送模块，用于根据所述第三中继请求，向所述中继终端发送第二 Uu DRB RLC承载的配置信息，所述第二Uu DRB RLC承载用于传输所述远端终端的业务数据。
可选的，所述终端还包括：第四发送模块，用于向所述中继终端发送所述网络侧设备与所述远端终端的第一Uu承载的配置信息，所述第一Uu承载的配置信息仅包括PDCP层及以上的配置信息。
本发明实施例提供的终端能够实现图5的方法实施例中网络侧设备实现的各个过程，为避免重复，这里不再赘述。
图10为实现本发明各个实施例的一种终端的硬件结构示意图，该终端100包括但不限于：射频单元101、网络模块102、音频输出单元103、输入单元104、传感器105、显示单元106、用户输入单元107、接口单元108、存储器109、处理器1010、以及电源1011等部件。本领域技术人员可以理解，图10中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。在本发明实施例中，终端包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
其中，射频单元101，用于向网络侧设备发送第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；接收所述网络侧设备发送的第一配置信息，所述第一配置信息包括：第一Uu无线链路层控制协议RLC承载的配置信息，所述第一Uu RLC承载用于传输远端终端的Uu信令。
或者，
射频单元101，用于通过与中继终端之间建立的第一sidelink RLC承载，或者，通过sidelink RRC消息，与所述中继终端之间传输所述远端终端的Uu信令。
本发明实施例提供的终端能够实现图3或图4的方法实施例中终端实现的各个过程，为避免重复，这里不再赘述。
另外，终端100包括一些未示出的功能模块，在此不再赘述。
请参考图11，本发明实施例还提供一种终端110，包括处理器111，存储器112，存储在存储器112上并可在所述处理器111上运行的计算机程序， 该计算机程序被处理器111执行时实现上述应用于中继终端的远端终端的连接管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
请参考图12，本发明实施例还提供一种终端120，包括处理器121，存储器122，存储在存储器122上并可在所述处理器121上运行的计算机程序，该计算机程序被处理器121执行时实现上述应用于远端终端的远端终端的连接管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
请参考图13，本发明实施例还提供一种网络侧设备130，包括处理器131，存储器132，存储在存储器132上并可在所述处理器131上运行的计算机程序，该计算机程序被处理器131执行时实现上述应用于网络侧设备的远端终端的连接管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本发明实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述应用于中继终端的远端终端的连接管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本发明实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述应用于远端终端的远端终端的连接管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本发明实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述应用于网络侧设备的远端终端的连接管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所 述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述任一实施例中的远端终端的连接管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述 实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本发明各个实施例所述的方法。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来控制相关的硬件来完成，所述的程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储器(Read-Only Memory，ROM)或随机存取存储器(Random Access Memory，RAM)等。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，模块、单元、子单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processor，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
上面结合附图对本发明的实施例进行了描述，但是本发明并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本发明的启示下，在不脱离本发明宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本发明的保护之内。

Claims (55)

  1. 一种远端终端的连接管理方法，应用于中继终端，包括：
    向网络侧设备发送第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
    接收所述网络侧设备发送的第一配置信息，所述第一配置信息包括：第一Uu无线链路层控制协议RLC承载的配置信息，所述第一Uu RLC承载用于传输远端终端的Uu信令。
  2. 根据权利要求1所述的方法，其中，所述第一Uu RLC承载为Uu信令无线承载SRB RLC承载或者Uu数据无线承载DRB RLC承载。
  3. 根据权利要求1所述的方法，其中，若所述远端终端的个数大于一个；
    不同的所述远端终端的Uu信令采用不同的第一Uu RLC承载传输；
    或者，
    不同的所述远端终端的Uu信令采用相同的第一Uu RLC承载传输。
  4. 根据权利要求1所述的方法，其中，
    同一所述远端终端的不同类型的Uu信令采用相同的第一Uu RLC承载传输；
    或者，
    同一所述远端终端的不同类型的Uu信令采用不同的第一Uu RLC承载传输。
  5. 根据权利要求3或4所述的方法，其中，以下指示信息中的至少一项携带在所述Uu信令中或者与所述Uu信令同时发送：
    所述远端终端的标识；
    所述Uu信令的类型。
  6. 根据权利要求5所述的方法，其中，是否携带或发送所述指示信息由所述网络侧设备配置。
  7. 根据权利要求1所述的方法，其中，所述向网络侧设备发送第一中继请求包括：
    若所述中继终端处于空闲状态，在发送给所述网络侧设备的无线资源控 制RRC连接建立请求中携带所述第一中继请求，或者，在发送给所述网络侧设备的RRC连接建立完成中携带所述第一中继请求，或者，在RRC连接建立完成之后，采用第一上行信令发送所述第一中继请求；
    和/或
    若所述中继终端处于非激活状态，在发送给所述网络侧设备的RRC连接恢复请求中携带所述第一中继请求，或者，在发送给所述网络侧设备的RRC连接恢复完成中携带所述第一中继请求；或者，在RRC连接恢复完成之后，采用第一上行信令发送所述第一中继请求；
    和/或
    若所述中继终端处于RRC连接状态，采用第一上行信令发送所述第一中继请求。
  8. 根据权利要求1所述的方法，还包括：
    根据所述中继终端侧的第一副链路sidelink RLC承载的配置信息，与所述远端终端之间建立第一sidelink RLC承载，所述第一sidelink RLC承载用于传输所述远端终端的Uu信令，所述第一sidelink RLC承载与所述第一Uu RLC承载具有映射关系。
  9. 据权利要求8所述的方法，其中，所述映射关系由所述网络侧设备配置或者由所述中继终端配置。
  10. 根据权利要求8所述的方法，其中，所述第一sidelink RLC承载为sidelink DRB承载或者sidelink SRB RLC承载。
  11. 据权利要求8所述的方法，其中，所述与所述远端终端之间建立第一sidelink RLC承载之前还包括：
    向所述远端终端发送所述远端终端侧的所述第一sidelink RLC承载的配置信息。
  12. 据权利要求8或11所述的方法，其中，所述第一sidelink RLC承载的配置信息采用以下方式中的至少一项确定：
    所述网络侧设备配置；
    所述中继终端配置；
    协议约定。
  13. 据权利要求12所述的方法，其中，所述中继终端配置包括以下至少一项：
    所述中继终端在接受为所述远端终端提供中继服务之后配置；
    所述中继终端在所述网络侧设备接受本终端作为中继终端之后配置；
    所述中继终端接收到所述第一Uu RLC承载的配置信息之后配置；
    所述中继终端根据所述第一Uu RLC承载的配置信息配置；
    所述中继终端根据协议的默认参数配置。
  14. 根据权利要求8或11所述的方法，其中，所述第一Uu RLC承载和第一sidelink RLC承载的配置信息包括以下至少一项：
    RLC配置；
    媒体接入控制MAC配置，所述MAC配置包括以下至少一项：逻辑信道标识、逻辑信道优先级和优先比特率。
  15. 根据权利要求1所述的方法，还包括：
    通过sidelink RRC消息与所述远端终端之间传输所述远端终端的Uu信令。
  16. 根据权利要求15所述的方法，其中，所述sidelink RRC消息中至少包括所述Uu信令的类型的指示信息，所述类型包括以下至少一项：RRC信令和非接入层NAS信令。
  17. 根据权利要求1所述的方法，其中，所述第一配置信息还包括：第一Uu DRB RLC承载的配置信息，所述第一Uu DRB RLC承载用于传输所述远端终端的业务数据。
  18. 根据权利要求1所述的方法，其中，所述向网络侧设备发送第一中继请求之后还包括：
    向所述网络侧设备发送第三中继请求，所述第三中继请求用于请求所述网络侧设备为所述远端终端的业务数据的传输配置Uu RLC承载；
    接收所述网络侧设备发送的第二Uu DRB RLC承载的配置信息，所述第二Uu DRB RLC承载用于传输所述远端终端的业务数据。
  19. 根据权利要求1所述的方法，其中，所述第一中继请求包括以下信息中的至少一项：
    中继指示信息，所述中继指示信息用于当前消息为所述第一中继请求；
    所述远端终端的标识；
    所述远端终端的业务信息；
    中继信息。
  20. 根据权利要求18所述的方法，其中，所述第三中继请求包括以下信息中的至少一项：
    所述远端终端的标识；
    所述远端终端的业务信息。
  21. 据权利要求19或20所述的方法，其中，所述业务信息包括以下至少一项：
    服务质量流标识QFI；
    QoS配置文件；
    QoS参数或QoS指示；
    最大流比特率MBR/MFBR；
    保证流比特率GBR/GFBR。
  22. 据权利要求19所述的方法，其中，所述中继信息包括以下至少一项：
    支持的中继跳数；
    中继架构选项；
    是否支持多连接中继架构。
  23. 据权利要求1所述的方法，其中，所述向网络侧设备发送第一中继请求之前还包括：
    与所述远端终端之间进行中继相关的发现过程和/或连接建立过程。
  24. 据权利要求23所述的方法，其中，所述发现过程和/或连接建立过程使用PC5链路的信令无线承载进行。
  25. 一种远端终端的连接管理方法，应用于远端终端，包括：
    通过与中继终端之间建立的第一sidelink RLC承载，或者，通过sidelink RRC消息，与所述中继终端之间传输所述远端终端的Uu信令。
  26. 根据权利要求25所述的方法，其中，所述第一sidelink RLC承载为sidelink DRB承载或者sidelink SRB RLC承载。
  27. 根据权利要求25所述的方法，其中，所述通过与中继终端之间建立的第一sidelink RLC承载，与所述中继终端之间传输所述远端终端的Uu信令之前还包括：
    根据所述远端终端侧的第一sidelink RLC承载的配置信息，与所述中继终端之间建立所述第一sidelink RLC承载。
  28. 根据权利要求27所述的方法，其中，所述第一sidelink RLC承载的配置信息采用以下方式确定：
    网络侧设备配置；
    所述中继终端配置；
    协议约定。
  29. 根据权利要求27所述的方法，其中，所述第一sidelink RLC承载的配置信息包括：
    RLC配置；
    MAC配置，所述MAC配置包括以下至少一项：逻辑信道标识、逻辑信道优先级和优先比特率。
  30. 根据权利要求25所述的方法，其中，所述sidelink RRC消息中至少包括：所述远端终端的Uu信令的类型的指示信息，所述类型包括以下至少一项：RRC信令和NAS信令。
  31. 根据权利要求25所述的方法，还包括：
    与所述中继终端之间进行中继相关的发现过程和/或连接建立过程。
  32. 根据权利要求31所述的方法，其中，所述发现过程和/或连接建立过程使用PC5链路的信令无线承载进行。
  33. 根据权利要求25所述的方法，还包括：
    接收所述中继终端转发的第一Uu承载的配置信息，所述第一Uu承载的配置信息仅包括PDCP层及以上的配置信息。
  34. 一种远端终端的连接管理方法，应用于网络侧设备，包括：
    接收中继终端发送的第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
    根据所述第一中继请求，向所述中继终端发送第一配置信息，所述第一 配置信息包括：第一Uu RLC承载的配置信息，所述第一Uu RLC承载用于传输远端终端的Uu信令。
  35. 根据权利要求34所述的方法，其中，所述第一Uu RLC承载为Uu SRB RLC承载或者Uu DRB RLC承载。
  36. 根据权利要求34所述的方法，其中，若所述远端终端的个数大于一个；
    不同的所述远端终端的Uu信令采用不同的第一Uu RLC承载传输；
    或者，
    不同的所述远端终端的Uu信令采用相同的第一Uu RLC承载传输。
  37. 根据权利要求34所述的方法，其中，
    同一所述远端终端的不同类型的Uu信令采用相同的第一Uu RLC承载传输；
    或者，
    同一所述远端终端的不同类型的Uu信令采用不同的第一Uu RLC承载传输。
  38. 根据权利要求36或37所述的方法，其中，以下指示信息中的至少一项携带在所述Uu信令中或者与所述Uu信令同时发送：
    所述远端终端的标识；
    所述Uu信令的类型。
  39. 根据权利要求38所述的方法，其中，是否携带或发送所述指示信息由所述网络侧设备配置。
  40. 根据权利要求34所述的方法，还包括：
    向所述中继终端发送第一sidelink RLC承载的配置信息，所述第一sidelink RLC承载用于传输所述远端终端的Uu信令，所述第一sidelink RLC承载与所述第一Uu RLC承载具有映射关系。
  41. 据权利要求40所述的方法，其中，所述映射关系由所述网络侧设备配置。
  42. 根据权利要求40所述的方法，其中，所述第一sidelink RLC承载为sidelink DRB承载或者sidelink SRB RLC承载。
  43. 根据权利要求40所述的方法，其中，所述第一Uu RLC承载和第一sidelink RLC承载的配置信息包括以下至少一项：
    RLC配置；
    MAC配置，所述MAC配置包括以下至少一项：逻辑信道标识、逻辑信道优先级和优先比特率。
  44. 根据权利要求34所述的方法，其中，所述第一配置信息还包括：第一Uu DRB RLC承载的配置信息，所述第一Uu DRB RLC承载用于传输所述远端终端的业务数据。
  45. 根据权利要求34所述的方法，其中，所述接收中继终端发送的第一中继请求之后还包括：
    接收所述中继终端发送的第三中继请求，所述第三中继请求用于请求所述网络侧设备为所述远端终端的业务数据的传输配置Uu RLC承载；
    根据所述第三中继请求，向所述中继终端发送第二Uu DRB RLC承载的配置信息，所述第二Uu DRB RLC承载用于传输所述远端终端的业务数据。
  46. 根据权利要求34所述的方法，还包括：
    向所述中继终端发送所述网络侧设备与所述远端终端的第一Uu承载的配置信息，所述第一Uu承载的配置信息仅包括PDCP层及以上的配置信息。
  47. 一种终端，包括：
    第一发送模块，用于向网络侧设备发送第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
    第一接收模块，用于接收所述网络侧设备根据所述第一中继请求发送的第一配置信息，所述第一中继请求用于请求所述网络侧设备为远端终端的Uu信令的传输配置Uu RLC承载。
  48. 一种终端，包括：
    传输模块，用于通过与中继终端之间建立的第一sidelink RLC承载，或者，通过RRC消息，传输远端终端的Uu信令。
  49. 一种网络侧设备，包括：
    第一接收模块，用于接收中继终端发送的第一中继请求，所述第一中继请求用于请求所述网络侧设备进行中继功能相关的配置；
    第一发送模块，用于根据所述第一中继请求，向所述中继终端发送第一配置信息，所述第一配置信息包括：第一Uu RLC承载的配置信息，所述第一Uu RLC承载用于传输远端终端的Uu信令。
  50. 一种终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1-24中任一项所述的远端终端的连接管理方法的步骤。
  51. 一种终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求25-33中任一项所述的远端终端的连接管理方法的步骤。
  52. 一种网络侧设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求34-46中任一项所述的远端终端的连接管理方法的步骤。
  53. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1-24中任一项所述的远端终端的连接管理方法的步骤；或者，所述程序或指令被处理器执行时实现如权利要求25-33中任一项所述的远端终端的连接管理方法的步骤；或者，所述程序或指令被处理器执行时实现如权利要求34-46中任一项所述的远端终端的连接管理方法的步骤。
  54. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1-24中任一项所述的远端终端的连接管理方法的步骤；或者，实现如权利要求25-33中任一项所述的远端终端的连接管理方法的步骤；或者，实现如权利要求34-46中任一项所述的远端终端的连接管理方法的步骤。
  55. 一种计算机软件产品，所述计算机软件产品被存储在非易失的存储介质中，所述软件产品被配置成被至少一个处理器执行以实现如权利要求1-24中任一项所述的远端终端的连接管理方法的步骤；或者，实现如权利要求25-33中任一项所述的远端终端的连接管理方法的步骤；或者，实现如权利要求34-46中任一项所述的远端终端的连接管理方法的步骤。
PCT/CN2021/089119 2020-04-28 2021-04-23 远端终端的连接管理方法、终端及网络侧设备 WO2021218787A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP21795276.1A EP4145863A4 (en) 2020-04-28 2021-04-23 CONNECTION MANAGEMENT METHOD FOR REMOTE USER DEVICE AND USER DEVICE AND NETWORK-SIDE DEVICE
BR112022021139A BR112022021139A2 (pt) 2020-04-28 2021-04-23 Método para gerenciamento de conexão de terminal remoto, terminal e dispositivo de lado de rede.
MX2022013394A MX2022013394A (es) 2020-04-28 2021-04-23 Metodo para la gesion de conexion de terminales remotas, terminal y dispositivo del lado de la red.
KR1020227040073A KR20230002793A (ko) 2020-04-28 2021-04-23 원격 단말의 연결 관리 방법, 단말 및 네트워크 측 기기
JP2022565856A JP2023523071A (ja) 2020-04-28 2021-04-23 遠端端末の接続管理方法、端末及びネットワーク側機器
AU2021265968A AU2021265968B2 (en) 2020-04-28 2021-04-23 Connection management method for remote user equipment, and user equipment and network-side device
US17/958,297 US20230023135A1 (en) 2020-04-28 2022-09-30 Method for remote terminal connection management, terminal, and network-side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010352343.X 2020-04-28
CN202010352343.XA CN113573422B (zh) 2020-04-28 2020-04-28 远端终端的连接管理方法、终端及网络侧设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/958,297 Continuation US20230023135A1 (en) 2020-04-28 2022-09-30 Method for remote terminal connection management, terminal, and network-side device

Publications (1)

Publication Number Publication Date
WO2021218787A1 true WO2021218787A1 (zh) 2021-11-04

Family

ID=78158248

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/089119 WO2021218787A1 (zh) 2020-04-28 2021-04-23 远端终端的连接管理方法、终端及网络侧设备

Country Status (9)

Country Link
US (1) US20230023135A1 (zh)
EP (1) EP4145863A4 (zh)
JP (1) JP2023523071A (zh)
KR (1) KR20230002793A (zh)
CN (1) CN113573422B (zh)
AU (1) AU2021265968B2 (zh)
BR (1) BR112022021139A2 (zh)
MX (1) MX2022013394A (zh)
WO (1) WO2021218787A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115380548A (zh) * 2020-07-29 2022-11-22 Oppo广东移动通信有限公司 中继发现方法和终端
WO2023130368A1 (zh) * 2022-01-07 2023-07-13 富士通株式会社 收发信息的方法、装置和通信系统
CN117241397A (zh) * 2022-06-02 2023-12-15 华为技术有限公司 数据传输的方法、装置和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3148285A1 (en) * 2015-09-25 2017-03-29 Panasonic Intellectual Property Corporation of America Improved radio bearer mapping for proximity services ue to network relay with associated priority signalling
WO2017099833A1 (en) * 2015-12-11 2017-06-15 Intel IP Corporation Control plane enhancements over sidelink for low power devices
CN108307489A (zh) * 2016-08-11 2018-07-20 中兴通讯股份有限公司 信息处理方法、装置、用户设备及基站
CN109245845A (zh) * 2017-05-05 2019-01-18 中兴通讯股份有限公司 一种信令传输方法及设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2832067C (en) * 2011-04-01 2019-10-01 Interdigital Patent Holdings, Inc. Method and apparatus for controlling connectivity to a network
WO2017014716A1 (en) * 2015-07-23 2017-01-26 Intel IP Corporation Layer 2 relay protocols and mobility relay method
GB2548374A (en) * 2016-03-16 2017-09-20 Nec Corp Communication system
CN107889080B (zh) * 2016-09-29 2023-06-06 中兴通讯股份有限公司 一种支持远端用户设备移动性的方法及装置
AR109780A1 (es) * 2016-09-30 2019-01-23 Ericsson Telefon Ab L M Establecimiento de conexión de control de recursos de radio
CN108391285B (zh) * 2017-02-03 2023-05-05 中兴通讯股份有限公司 一种设备直通系统的通信方法、数据转发方法及装置
CN110249670B (zh) * 2017-02-06 2022-04-26 Lg 电子株式会社 在无线通信系统中执行具有与第一ue的连接的第二ue的寻呼有关的操作的方法及其装置
WO2018155908A1 (ko) * 2017-02-22 2018-08-30 엘지전자(주) 무선 통신 시스템에서 릴레이를 통한 데이터 송수신 방법 및 이를 위한 장치
WO2018176416A1 (zh) * 2017-03-31 2018-10-04 华为技术有限公司 中继通信方法、装置和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3148285A1 (en) * 2015-09-25 2017-03-29 Panasonic Intellectual Property Corporation of America Improved radio bearer mapping for proximity services ue to network relay with associated priority signalling
WO2017099833A1 (en) * 2015-12-11 2017-06-15 Intel IP Corporation Control plane enhancements over sidelink for low power devices
CN108307489A (zh) * 2016-08-11 2018-07-20 中兴通讯股份有限公司 信息处理方法、装置、用户设备及基站
CN109245845A (zh) * 2017-05-05 2019-01-18 中兴通讯股份有限公司 一种信令传输方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4145863A4 *

Also Published As

Publication number Publication date
KR20230002793A (ko) 2023-01-05
CN113573422B (zh) 2023-10-20
AU2021265968B2 (en) 2024-05-23
BR112022021139A2 (pt) 2022-11-29
EP4145863A1 (en) 2023-03-08
CN113573422A (zh) 2021-10-29
EP4145863A4 (en) 2023-11-01
MX2022013394A (es) 2022-11-30
AU2021265968A1 (en) 2022-10-20
JP2023523071A (ja) 2023-06-01
US20230023135A1 (en) 2023-01-26

Similar Documents

Publication Publication Date Title
WO2021159906A1 (zh) sidelink中继通信方法、装置、设备及介质
JP6718103B2 (ja) 通信方法
US11564268B2 (en) Radio resource control connection establishment
US10122441B2 (en) Method of utilizing a relay node in wireless communication system
WO2021218787A1 (zh) 远端终端的连接管理方法、终端及网络侧设备
WO2018028694A1 (zh) 设备直通系统的通信方法及装置、通信系统
TWI804992B (zh) 層2使用者設備透過網路中繼進行信令傳輸的方法
CN105357773B (zh) 一种无线宽带通信方法，装置和系统
CN109691197B (zh) 一种数据传输方法、设备及系统
EP3952398B1 (en) Radio bearer configuration method, apparatus and system
USRE48316E1 (en) Communications system, base station, user equipment, and signaling transmission method
WO2020143690A1 (zh) 一种无线承载的配置方法、终端及通信装置
WO2019192458A1 (zh) 通信方法和装置
EP3692738B1 (en) Method and apparatus for controlling packet duplication
WO2014048224A1 (zh) 通过控制面信令传输数据的方法、设备及系统
WO2019192492A1 (zh) 一种请求系统信息的指示方法、相关设备及系统
JP7413507B2 (ja) 通信制御方法
TWI804984B (zh) 用於第2層ue到網絡中繼的連接建立方法與設備
CN114258104A (zh) 层2用户设备通过网络中继进行信令传输的方法
WO2022082798A1 (zh) 通信方法及装置
US20230086337A1 (en) Methods, infrastructure equipment and wireless communications networks
WO2024065667A1 (zh) 用于侧行通信的方法以及通信设备
WO2024138295A1 (zh) 用于传输数据的方法、终端设备以及网络设备
WO2022001641A1 (zh) 用于切换的数据传输的方法和装置

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: 21795276

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021265968

Country of ref document: AU

Date of ref document: 20210423

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112022021139

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2022565856

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20227040073

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 112022021139

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20221018

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021795276

Country of ref document: EP

Effective date: 20221128