WO2021259157A1 - 中继确定方法、配置方法、装置、终端及网络侧设备 - Google Patents

中继确定方法、配置方法、装置、终端及网络侧设备 Download PDF

Info

Publication number
WO2021259157A1
WO2021259157A1 PCT/CN2021/100841 CN2021100841W WO2021259157A1 WO 2021259157 A1 WO2021259157 A1 WO 2021259157A1 CN 2021100841 W CN2021100841 W CN 2021100841W WO 2021259157 A1 WO2021259157 A1 WO 2021259157A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay
terminal
relay operation
remote terminal
information
Prior art date
Application number
PCT/CN2021/100841
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 JP2022579025A priority Critical patent/JP2023530186A/ja
Priority to EP21829298.5A priority patent/EP4171097A4/en
Priority to KR1020227042585A priority patent/KR20230008169A/ko
Publication of WO2021259157A1 publication Critical patent/WO2021259157A1/zh
Priority to US18/086,355 priority patent/US20230117489A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • 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
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/12—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • 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
    • 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

  • This application belongs to the field of wireless communication technology, and specifically relates to a relay determination method, configuration method, device, terminal, and network side equipment.
  • LTE Long Term Evolution
  • UE terminal 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
  • 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 link interface can also be called the PC5 interface.
  • the current sidelink transmission is mainly divided into broadcast (broadcast), multicast (groupcast), unicast (unicast) several transmission forms.
  • Unicast as its name implies, is one-to-one transmission.
  • Multicast is one-to-many transmission. Broadcasting is also one-to-many transmission, but broadcasting does not have the concept of terminals belonging to the same group.
  • Sidelink unicast and multicast communications support the physical layer hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) feedback mechanism.
  • Hybrid Automatic Repeat reQuest Hybrid Automatic Repeat reQuest, HARQ
  • the resource allocation modes of Sidelink terminals are divided into two categories:
  • the network side equipment (base station) controls and allocates resources for each terminal;
  • Each terminal independently selects resources.
  • the remote terminal passes through the Sidelink link with the relay terminal (relay UE), and the relay terminal forwards the data of the remote terminal to the target terminal.
  • the relay terminal forwards the data of the remote terminal to the target terminal.
  • data is transmitted between the remote terminal 1 and the remote terminal 2, and the relay terminal plays the role of data transfer.
  • the L2 relay architecture or the L3 relay architecture can be supported.
  • the purpose of the embodiments of the present application is to provide a relay determination method, configuration method, device, terminal, and network side equipment, which can solve the problem of how to determine which relay architecture to use.
  • an embodiment of the present application provides a relay determination method, which is applied to a remote terminal, and includes:
  • relay configuration information includes at least one configuration parameter of a relay operation
  • the relay operation to be used is determined.
  • an embodiment of the present application provides a relay configuration method, which is applied to a network side device, and includes:
  • an embodiment of the present application provides a relay determining device, which is applied to a remote terminal, and includes:
  • the first receiving module is configured to receive relay configuration information, where the relay configuration information includes at least one configuration parameter of a relay operation;
  • the relay determination module is configured to determine the relay operation to be used according to the relay configuration information.
  • an embodiment of the present application provides a relay configuration device, which is applied to a network side device, and includes:
  • the sending module is configured to send relay configuration information, where the relay configuration information includes at least one configuration parameter of a relay operation.
  • a terminal in a fifth aspect, includes a processor, a memory, and a program or instruction that is stored on the memory and can run on the processor.
  • the program or instruction When the program or instruction is executed by the processor, Implement the steps of the method as described in the first aspect.
  • a network-side device in a sixth aspect, includes a processor, a memory, and a program or instruction that is stored on the memory and can run on the processor.
  • the program or instruction is The processor implements the steps of the method described in the second aspect when executed.
  • a readable storage medium is provided, and a program or instruction is stored on the readable storage medium.
  • the program or instruction When executed by a processor, it implements the steps of the method described in the first aspect or implements The steps of the method described in the second aspect.
  • a chip in an eighth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction to implement the same as described in the first aspect. Or implement the method described in the second aspect.
  • a computer software product is provided, the computer software product is stored in a nonvolatile storage medium, and the software product is configured to be executed by at least one processor to implement the computer software product described in the first aspect.
  • a communication device configured to execute the method according to the first aspect or execute the method according to the second aspect.
  • the terminal when at least one relay operation exists, the terminal selects the corresponding relay operation for transmission according to the relay configuration information sent by the network side device, thereby making full use of the characteristics of different relay operations. It guarantees the service quality QoS of the remote terminal business, and considers the optimization of transmission efficiency, which guarantees the system efficiency while improving the user experience.
  • Fig. 1 shows a block diagram of a wireless communication system applied in an embodiment of the present application
  • FIG. 2 shows a flowchart of the steps of a relay determination method provided by an embodiment of the present application
  • FIG. 3 shows a flowchart of steps of a relay configuration method provided by an embodiment of the present application
  • FIG. 4 shows a schematic structural diagram of a relay determining apparatus provided by an embodiment of the present application
  • FIG. 5 shows a schematic structural diagram of a relay configuration device provided by an embodiment of the present application
  • FIG. 6 shows a schematic structural diagram of a communication device provided by an embodiment of the present invention.
  • FIG. 7 shows a schematic structural diagram of a terminal provided by an embodiment of the present invention.
  • Fig. 8 shows a schematic structural diagram of a network side device provided by an embodiment of the present invention.
  • first and second in the specification and claims of this application are used to distinguish similar objects, but not to describe a specific sequence or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the "first", “second”, etc. are distinguished
  • the objects are usually of one type, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims means at least one of the connected objects, and the character “/” generally means that the associated objects before and after are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used for the aforementioned systems and radio technologies as well as other systems and radio technologies.
  • NR New Radio
  • 6G 6th Generation
  • Fig. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 may also be referred to as a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer or a personal digital device.
  • UE User Equipment
  • Terminal-side devices such as Vehicle User Equipment (VUE) and Pedestrian User Equipment (PUE), and wearable devices include: bracelets, headsets, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application.
  • the network side device 12 may be a base station or a core network, where the base station may be called Node B, Evolved Node B, Access Point, Base Transceiver Station (BTS), radio base station, radio transceiver, basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, Wireless Local Area Network, WLAN ) Access point, Wireless Fidelity (WiFi) node, Transmitting Receiving Point (TRP) or some other appropriate term in the field, as long as the same technical effect is achieved, the base station is not limited to For specific technical vocabulary, it should be noted that, in the embodiments of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • L2 relay operation and/or, L3 relay operation.
  • the remote terminal passes through the Sidelink link with the relay terminal, and the relay terminal forwards its L2 data to the base station.
  • the first remote terminal and the relay terminal have only part of the L2 protocol stack and below, for example, only the RLC, MAC and PHY layers are included, and the data type transferred by the relay terminal is L2 data packets, such as RLC Service Data Unit (SDU), or Backhaul Adaptation Protocol (BAP) SDU, etc.
  • SDU RLC Service Data Unit
  • BAP Backhaul Adaptation Protocol
  • the end-to-end PDCP protocol layer is guaranteed to be transparent to the relay terminal.
  • L2 relay operation enables the data of the remote terminal to enjoy end-to-end (between the remote terminal and the base station) security, is transparent to the relay terminal, and can better provide business continuity guarantee when the remote terminal is switched. Therefore, the service transmission effect is better.
  • the remote terminal passes the Sidelink link with the relay terminal, and the relay terminal forwards its L3 data to the base station.
  • the relay terminal forwards its L3 data to the base station.
  • there is a relatively complete protocol stack between the first remote terminal and the relay terminal such as Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP) )
  • the radio resource control (Radio Resource Control, RRC) layer which also includes the radio link control (Radio Link Control, RLC) layer, the media access control (Media Access Control, MAC) layer and the physical layer (PHY)
  • the data type transferred by the relay terminal is L3 data packet, such as IP data packet.
  • L3 relay operation is characterized by relatively simple implementation and clear flow.
  • the L3 relay operation includes:
  • L3 relay protocol stack and the user plane session of the remote terminal is established by the network side device and the core network node of the relay terminal;
  • L3 relay protocol stack and the user plane session of the remote terminal is established by the network side device and the core network node of the remote terminal.
  • the network side device supports at least one type of relay operation.
  • the remote terminal uses different relays in different deployment scenarios. Operation, or choose different relay operations based on business requirements, or choose different relay operations based on the capabilities of the relay terminal, which can maximize the advantages of L2/L3 relay operations, reduce the impact of their disadvantages, and improve system efficiency and Business security.
  • an embodiment of the present application provides a relay determination method, which is applied to a remote terminal, and includes:
  • Step 201 Receive relay configuration information, where the relay configuration information includes at least one configuration parameter of a relay operation;
  • Step 202 Determine the relay operation to be used according to the relay configuration information.
  • the relay configuration information sent by the network-side device to the terminal needs to include at least one or more configuration parameters for relay operations, so that the terminal can select a suitable relay operation according to this type of configuration parameters.
  • the relay configuration information sent by the network-side device to the terminal needs to include at least one or more configuration parameters for relay operations, so that the terminal can select a suitable relay operation according to this type of configuration parameters.
  • the remote terminal determines whether to use the relay operation according to the configuration parameter of the relay operation; for another example, the relay configuration information includes two or more For the configuration parameters of the relay operation, the remote terminal first judges whether to use the relay operation according to the configuration parameters and selects a relay operation to be used according to the configuration parameters.
  • the above two types of applications have requirements.
  • base stations in these regions can be selected to support both L3 relay operation and L2 relay operation functions. This is based on the application scenario, considering the needs of different architecture deployments.
  • After determining the requirements it is necessary to upgrade or update the software and hardware versions of the network-side equipment to support the corresponding L2 and/or L2 relay operations.
  • the network-side equipment can also decide which one to support according to its own software and hardware version Relay operation, or both are supported; and the network side device needs to inform the terminal of the type of relay operation it supports.
  • the method further includes:
  • the network side device According to the configuration parameter of the relay operation, it is determined that the network side device supports the relay operation type corresponding to the configuration parameter.
  • the network side device indirectly or implicitly indicates the type of relay operation supported by the network side device through the configuration parameter of the relay operation. For example:
  • the network side device sends the configuration parameters of the L2 relay operation, which indirectly indicates that the network side device supports the L2 relay operation;
  • the network side device sends the configuration parameters of the L3 relay operation, which indirectly indicates that the network side device supports the L3 relay operation;
  • the network side device sends the configuration parameters of the L2 relay operation and the configuration parameters of the L3 relay operation, which indirectly indicates that the network side device supports both the L2 relay operation and the L3 relay operation.
  • the network side device does not send any configuration parameters related to the relay operation, it indirectly indicates that the network side device does not support the relay operation.
  • the relay configuration information further includes: a first indication field used to indicate the type of relay operation supported by the network side device.
  • the network side device directly indicates the type of relay operation supported by the network side device through the first indication field in the relay configuration information.
  • a way for a network-side device to indicate the type of relay operation it supports may be that the first indication field contains three options: L3 relay operation, L2 relay operation, and both (that is, both L3 relay operation and L2 relay operation are supported at the same time).
  • Relay operation ); or the first indication field contains four options: L3 relay operation, L2 relay operation, both (that is, both L3 relay operation and L2 relay operation are supported at the same time), none (relay operation is not supported).
  • the network side device indicates that it does not support the relay operation function by default or not appearing in this field.
  • the base station can indicate that it does not support the relay operation function by taking the value of the first indication field to be none.
  • the above-mentioned relay configuration information may be sent to the terminal in the form of system messages or dedicated signaling.
  • the relay operation types generally include:
  • the network-side device can indicate in an explicit or implicit manner.
  • the explicit method means that the network-side device indicates through an explicit information field that it does not support relay operations;
  • the formula means that as long as the network-side device does not carry any configuration instructions for relay operations, for example, if it does not indicate support, the base station does not support relay operations by default. In the case where the base station does not support the relay operation, and the terminal knows that the network side device does not support the relay operation, the terminal is not allowed to initiate a relay request and any relay operation.
  • the network side device supports only one type of relay operation, such as L2 relay operation or L3 relay operation;
  • the network-side device supports only one type of relay operation. It can be specified by the standard default or standard method that when the network-side device indicates that it supports a type of relay operation, the network-side device can indicate it through an explicit information field.
  • the terminal initiates a corresponding relay operation according to the type of relay operation supported by the base station.
  • the type is L2 relay (or L3 relay); when the terminal receives the relay configuration information of the network side device, it initiates a corresponding relay operation according to the type of relay operation supported by the network side device.
  • the network side device supports two types of relay operations, L2 relay operation and L3 relay operation, and the network side device can indicate the two types of relay operations that it supports through an explicit information field.
  • the terminal receives the relay configuration information of the network side device, it can initiate a corresponding relay operation according to the type of relay operation supported by the network side device.
  • the relay configuration information needs to directly or indirectly indicate the type of relay operation supported by the network-side device, and also need to include the configuration parameters of the relay operation (if only one type of relay operation is supported, it only needs to include that type of relay operation). Configuration parameters of the relay operation; if two types of relay operations are supported at the same time, the configuration parameters of the two operations need to be included).
  • the configuration parameter of the relay operation includes at least one of the following:
  • the first condition information for the remote terminal to allow the use of the relay operation for example, the conditions for allowing the L2 relay operation, such as the reference signal received power (RSRP) threshold condition of the remote terminal, the relay RSRP threshold conditions of the terminal, etc.; or conditions that allow L3 relay operations, such as RSRP threshold conditions of the remote terminal, RSRP threshold conditions of the relay terminal, etc.;
  • the above-mentioned L2 relay operation conditions and L3 relay operation conditions can be They are configured independently, with different thresholds or conditions, or they may be unified, that is, the L2 relay operation and the L3 relay operation use the same threshold parameters or conditions.
  • the bearer configuration information when the remote terminal uses the relay operation for example, the bearer configuration information when the terminal performs L2 relay, such as the configuration of the RLC bearer; or, the bearer configuration information when the terminal performs L3 relay , Such as sidelink radio bearer (Sidelink Radio Bearer, SLRB) and RLC bearer corresponding configuration.
  • L2 and L3 may be completely independent configurations and have different configuration domains; they may also be unified for the same part, that is, the L2 relay operation and the L3 relay operation use the same RLC bearer configuration.
  • the remote terminal selects the relay operation for data transmission, it selects the second condition information of the relay operation.
  • the second condition information includes at least one of the following:
  • Service information for example, if the service requirement or link of the terminal meets certain conditions, the L2 architecture is selected; if the service requirement or link of the terminal meets other conditions, the L3 architecture is selected. For another example, if the service of the terminal is public safety, the terminal selects the L3 architecture, and when it is other services, selects the L2 architecture;
  • Link information includes at least one of the following: link condition information of the Uu interface of the relay terminal; link condition information of the Uu interface of the remote terminal; Link condition information of the PC5 interface;
  • the association information between the remote terminal and the relay terminal for example, when the remote terminal and the relay terminal have a certain binding relationship (or called an association relationship), such as the mobile phone and wearable device of the same user, or they are in the same
  • the L3 architecture can be considered first, and the others use the L2 architecture.
  • the remote terminal and the relay terminal belong to the same PLMN; or have the same communication restrictions.
  • a pair of terminals belonging to the same Closed Subscriber Group (CSG) can be allowed to access a CSG cell at the same time.
  • CSG Closed Subscriber Group
  • L2 architecture is allowed (so in this case, the remote terminal and the relay terminal are connected to the same base station at the same time), and when the remote terminal and the relay terminal have a coordinated or negotiated charging strategy, you can choose L3 Relay operation, because in the case of L3 relay operation, the network usage cost of the remote terminal may need to be negotiated and shared with the relay terminal;
  • the business information includes at least one of the following:
  • the service QoS of the terminal meets certain requirements, such as the priority meets a certain threshold, or the block error rate meets a certain threshold, or for a specific 5G QoS identifier (5G QoS Identifier, 5QI), the service is IP/non-IP data , Use L2/L3 relay operation, otherwise use another relay operation.
  • 5G QoS Identifier 5G QoS Identifier
  • step 202 when the relay configuration information includes two or more relay operation configuration parameters (that is, the network side device supports two or more relay operations), step 202 includes :
  • one relay operation is selected from the two or more relay operations as the relay operation to be used.
  • the target parameter includes at least one of the following:
  • the network side device can support two or more relay operations
  • the network side device provides configuration parameters for two or more relay operations, and selects the medium to be used according to the service information of the remote terminal. Following the operation.
  • the terminal when the terminal needs to perform service transmission, it can first determine whether the first condition information for relay operation is satisfied. For example, if the RSRP between the terminal and the serving cell is lower than a certain threshold, it means that the terminal is at the edge of the cell and can pass other information. The user conducts transit transmission; if the L2 and L3 architectures have different condition restrictions, and when the terminal only meets one of the conditions at this time, it can only initiate a relay operation that meets the conditions for transmission. When both conditions are met, a relay operation can be selected according to the service information, where the selection condition can be configured on the network side, or pre-defined, or implemented by the terminal's own algorithm.
  • Example 1 When a terminal initiates a specific service, it can select a corresponding relay operation.
  • public safety services use L3 relay operations
  • ordinary enhanced Mobile Broadband (eMBB) services can use L2 relay operations.
  • Example 2 When a service initiated by a terminal has a specific identifier, such as a service ID or a QoS ID, which belongs to a list supported by a certain relay operation, when the terminal initiates these services, the corresponding relay operation is selected.
  • a specific identifier such as a service ID or a QoS ID, which belongs to a list supported by a certain relay operation
  • Example 3 When the service initiated by the terminal has certain characteristics, for example, IP packets can use L3 relay operations, and non-IP (non-IP) packets can use L2 relay operations.
  • IP packets can use L3 relay operations
  • non-IP (non-IP) packets can use L2 relay operations.
  • Example 4 When the terminal initiates the service, the block error rate is required to be higher, for example, lower than 10 ⁇ -6. At this time, to avoid packet loss caused by handover, L2 relay operation can be adopted.
  • Example 5 When the service initiated by the terminal has high QoS requirements, such as high priority or service continuity requirements, at this time, to avoid packet loss caused by handover, L2 relay operation can be adopted.
  • QoS requirements such as high priority or service continuity requirements
  • Example 6 when the service initiated by the terminal has a short duration, for example, after a small number of data packets are sent, the link is torn down immediately, and the L3 relay operation can be used at this time.
  • Example 7 when the terminal that initiates the service, there is a certain binding ⁇ attribution ⁇ collaboration ⁇ access restriction ⁇ cost sharing relationship with the relay terminal, for example, between the mobile phone and wearable device of the same user, or remote The terminal and the relay terminal move together in the same vehicle, and the L3 relay operation can be used at this time.
  • the remote terminal can support both types at the same time.
  • Relay operation due to version reasons, for example, the first version only supports L3 relay operation, and only the latter enhanced version can support L2 relay operation, so for the remote terminal of the first version, only L3 relay operation can be selected, and the latter one
  • the version of the remote terminal can be selected on demand among the two relay operations.
  • the functions of the relay terminal are very different, so you can also refer to the capability information of the relay terminal when selecting the relay operation.
  • the relay terminal forwards RLC SDU (RLC service data unit)/BAP SDU (BAP service data unit), and does not need to perform operations such as PDCP security and header compression, but in L2 relay operation
  • RLC SDU RLC service data unit
  • BAP SDU BAP service data unit
  • the two links of the relay terminal have the RLC bearer.
  • the configuration and mapping of the RLC bearer are generally controlled and instructed by the network side equipment.
  • IAB integrated access backhaul
  • the relay node in the middle needs to have F1 interface function to complete data transfer.
  • the relay terminal forwards IP data packets or SDAP SDU (SDAP Service Data Unit), which requires operations such as PDCP security and header compression, and the two links of the relay terminal in the L3 relay operation are respectively
  • SDAP SDU SDAP Service Data Unit
  • the protocol stack and process can be reused.
  • the mapping of the RB at both ends can be configured by the network without supporting the F1 interface function.
  • the data transfer service can be completed by processing the two links separately.
  • the capability information of the relay terminal includes:
  • Support L2 relay operation function can be used as a relay terminal in L2 relay operation
  • Support L3 relay operation function can be used as a relay terminal in L3 relay operation
  • L2 relay operation function supports both L2 relay operation function and L3 relay operation function. It can be used as a relay terminal in L2 relay operation or as a relay terminal in L3 relay operation.
  • the remote terminal selects a relay operation to be used according to its own business information or communication scenarios, and the other party confirms its needs during the interaction with the relay terminal, you can follow the selection
  • the relay operation performs the corresponding establishment and transmission process.
  • a remote terminal when a remote terminal needs to perform relay service transmission, it can first determine which type of relay operation needs to be initiated according to its own version, service information, etc. Afterwards, in the interaction with the relay terminal, the corresponding relay terminal with the relay capability can be selected.
  • the method further includes:
  • the remote terminal broadcasts to the outside through the PC5 interface, carrying its own relay service request, relay operation type (L2/L3 or both) and other information.
  • the relay terminal receives the broadcast and judges whether it can support it according to its own capabilities. For the service request of this relay operation type, if it is possible, a response message is sent to the remote terminal; if not, the request message is ignored.
  • the method further includes:
  • a terminal that supports the relay operation to be used is selected as the relay terminal.
  • the relay terminal broadcasts to the outside through the PC5 interface, carrying information such as the type of relay service that it can support, the type of relay operation (L2 or L3 or Both), etc.
  • the remote terminal receives the broadcast and judges whether it is based on its own service requirements. The relay terminal is required, and if the conditions are met, a response message is sent to the relay terminal, if not, the broadcast message is ignored.
  • the remote terminal selects the relay terminal with the best link quality condition. When it is within the range that meets the basic PC5 communication requirements, it does not find it.
  • the remote terminal can determine whether to expand the range by itself. For example, the remote terminal wants to perform L2 relay operation, but the nearby communication requirement does not have an L2 medium. If the terminal has a relay function, the remote terminal can decide by itself whether to choose one of the L3 relays that meets the communication requirements for service.
  • the relay related operations are performed under network control, that is, the remote terminal
  • the result of the operation needs to be notified to the network, so that the network can issue a reasonable configuration for subsequent relay operations; that is, the method also includes:
  • the first message is sent to the network-side device, or the relay terminal sends the second message to the network-side device; wherein the first message or the second message carries the request information of the to-be-used relay operation ;
  • the remote terminal can directly perform the RRC process with the network side device, it can inform the base station that it wants to establish the transmission of the L2 relay operation through the RRC process, and the subsequent network side device will follow this requirement Establish the corresponding transmission pipeline and allocate resources for the remote terminal.
  • the remote terminal needs to be replaced by the relay terminal to initiate a relay request to the network side device.
  • the relay terminal will also request It carries the requirements of L3 relay, and the network side equipment establishes corresponding transmission pipes and allocates resources for the remote terminal according to the requirements.
  • the remote terminal sends the request of the relay operation of its choice to the network through its own RRC signaling (this signaling passes through the relay Terminal transfer), the network side device issues the corresponding reconfiguration message (for the remote terminal, it mainly includes the SLRB configuration, the RLC bearer configuration between the remote terminal and the relay terminal), and establishes a connection with the selected relay according to this reconfiguration message Operate the corresponding bearer configuration; at the same time, the relay terminal must also cooperate with this process to send the request of the relay operation to the network through its own RRC signaling, and the network sends the corresponding reconfiguration message (for the relay terminal, including The RLC bearer configuration between the remote terminal and the relay terminal, the RLC bearer configuration between the relay terminal and the network), according to this configuration, the relay terminal establishes the RLC bearer between the remote terminal and the network RLC bearer.
  • the relay terminal since there is not necessarily an RRC connection between the remote terminal and the network, the relay terminal sends a relay operation request to the network, and the network issues the corresponding reconfiguration message (mainly including the middle Following the terminal Uu bearer configuration L3+L2 protocol stack configuration, and the bearer configuration between the relay terminal and the remote terminal L3+L2 protocol stack configuration).
  • the remote terminal establishes RRC communication with the network by itself, while only the relay terminal in L3 has an RRC connection. Therefore, through different signaling procedures, the network can know which structure of the relay is currently requested, such as the L2 relay configuration requested by the RRC signaling of the remote terminal (the signaling of the remote terminal is transferred to the relay terminal through the relay terminal). Network), the RRC signaling of the relay terminal requests the L3 relay configuration (the relay terminal has its own signaling radio bearer SRB for signaling transmission).
  • the method further includes:
  • the transmission related to the corresponding relay operation is performed.
  • the relay terminal completes different forwarding actions in different relay operations: for example, the L2 relay operation forwards L2PDU; the L3 relay operation forwards the equivalent of IP data packets, non- L3 packet of IP.
  • the relay terminal establishes its own core network bearer for remote terminal data transmission, and the other is that the relay terminal establishes the core network bearer for the remote terminal. Data transmission at the remote terminal.
  • the information carried in the above request can be distinguished, such as type indication, or other distinguishing information, so as to facilitate different subsequent operations.
  • the network if the received instructions are different, the information carried when the core network bearer is established is initiated, and even the core network node is different (the core network node corresponding to the relay terminal, the core network node corresponding to the remote terminal).
  • the IP address processing is different, which will not be explained here.
  • the configuration parameters come from the network, and the bearer configuration process is the remote terminal Between 1 and remote terminal 2 (that is, other remote terminals).
  • the remote terminal 1 may be referred to as the source terminal, and the remote terminal 2 may be referred to as the target terminal. That is to say, in the terminal-to-terminal relay scenario, the “remote terminal” mentioned in the embodiment of this application can be replaced with the “source terminal”, which is not specifically limited here.
  • the initiated remote terminal 1 needs to confirm the use of the same relay operation through the discovery process with the relay terminal, and between the relay terminal and the remote terminal 2, and negotiate the relay to be used.
  • the method further includes at least one of the following steps:
  • the third PC5 RRC message In the process of establishing a radio resource control RRC connection with the relay terminal, sending a third PC5 RRC message to the relay terminal, where the third PC5 RRC message explicitly or implicitly indicates the relay operation to be used,
  • the third PC5 RRC message also carries bearer configuration information for the relay operation;
  • the relay terminal sends a fourth PC5 RRC message to the other remote terminals.
  • the fourth PC5 RRC message contains an explicit indication or an implicit indication. Indicate the relay operation to be used, and the fourth PC5 RRC message also carries bearer configuration information of the relay operation;
  • a fifth PC5 RRC message is sent to the other remote terminals.
  • the fifth PC5 RRC message explicitly or implicitly indicates the relay operation to be used, so The fifth PC5 RRC message also carries the bearer configuration information of the relay operation.
  • the RRC process between the remote terminal 1 and the relay terminal also needs to carry the identifier of the relay operation explicitly or implicitly, and the bearer configuration related to the relay operation, such as the RLC bearer configuration (used for the relay terminal And remote terminal 1);
  • the RRC process between the remote terminal 2 and the relay terminal also needs to carry the identifier of the relay operation explicitly or implicitly, and the configuration related to the relay operation, such as the RLC bearer configuration (used for the relay terminal and Remote terminal 2).
  • the RRC process between the remote terminal 1 and the relay terminal also needs to carry the identifier of the relay operation explicitly or implicitly, and the configuration related to the relay operation, such as SLRB+RLC bearer configuration (for relay Terminal and remote terminal 1);
  • the RRC process between the remote terminal 2 and the relay terminal also needs to carry the identifier of the relay operation explicitly or implicitly, and the configuration related to the relay operation, such as SLRB+RLC bearer configuration (for relay Terminal and remote terminal 2).
  • the terminal when at least one relay operation exists, the terminal selects the corresponding relay operation for transmission according to the relay configuration information sent by the network side device, thereby making full use of the different relay operations. It not only guarantees the service quality QoS of the remote terminal service, but also considers the optimization of transmission efficiency, and improves the user experience while ensuring the system efficiency; when at least two relay operations exist, the network side instructs its support
  • the type of relay operation is based on the business information or the ability of the relay terminal to select the appropriate relay operation to carry the data bearer of the remote terminal, which can make full use of the advantages of various relay operations, avoid the shortcomings, and expand the flexibility of the system. Improve system performance and user experience.
  • an embodiment of the present application also provides a relay configuration method, which is applied to a network side device, and includes:
  • Step 301 Send relay configuration information, where the relay configuration information includes at least one configuration parameter of a relay operation.
  • the relay configuration information sent by the network-side device to the terminal needs to include at least one or more configuration parameters for relay operations, so that the terminal can select a suitable relay operation according to this type of configuration parameters.
  • the relay configuration information sent by the network-side device to the terminal needs to include at least one or more configuration parameters for relay operations, so that the terminal can select a suitable relay operation according to this type of configuration parameters.
  • the remote terminal determines whether to use the relay operation according to the configuration parameter of the relay operation; for another example, the relay configuration information includes two or more For the configuration parameters of the relay operation, the remote terminal first judges whether to use the relay operation according to the configuration parameters and selects a relay operation to be used according to the configuration parameters.
  • the above two types of applications have requirements.
  • base stations in these regions can be selected to support both L3 relay operation and L2 relay operation functions. This is based on the application scenario, considering the needs of different architecture deployments.
  • After determining the requirements it is necessary to upgrade or update the software and hardware versions of the network-side equipment to support the corresponding L2 and/or L2 relay operations.
  • the network-side equipment can also decide which one to support according to its own software and hardware version Relay operation, or both are supported; and the network side device needs to inform the terminal of the type of relay operation it supports.
  • the method further includes:
  • the configuration parameter of the relay operation indicates that the network-side device supports the type of relay operation corresponding to the configuration parameter; in other words, the network-side device indirectly or implicitly indicates that the network-side device supports the configuration parameter of the relay operation.
  • the type of relay operation For example:
  • the network side device sends the configuration parameters of the L2 relay operation, which indirectly indicates that the network side device supports the L2 relay operation;
  • the network side device sends the configuration parameters of the L3 relay operation, which indirectly indicates that the network side device supports the L3 relay operation;
  • the network side device sends the configuration parameters of the L2 relay operation and the configuration parameters of the L3 relay operation, which indirectly indicates that the network side device supports both the L2 relay operation and the L3 relay operation.
  • the network side device does not send any configuration parameters related to the relay operation, it indirectly indicates that the network side device does not support the relay operation.
  • the relay configuration information further includes: a first indication field used to indicate the type of relay operation supported by the network side device.
  • the network side device directly indicates the type of relay operation supported by the network side device through the first indication field in the relay configuration information.
  • a way for a network-side device to indicate the type of relay operation it supports may be that the first indication field contains three options: L3 relay operation, L2 relay operation, and both (that is, both L3 relay operation and L2 relay operation are supported at the same time).
  • Relay operation ); or the first indication field contains four options: L3 relay operation, L2 relay operation, both (that is, both L3 relay operation and L2 relay operation are supported at the same time), none (relay operation is not supported).
  • the network side device indicates that it does not support the relay operation function by default or not appearing in this field.
  • the base station can indicate that it does not support the relay operation function by taking the value of the first indication field to be none.
  • the above-mentioned relay configuration information may be sent to the terminal in the form of system messages or dedicated signaling.
  • the relay configuration information needs to directly or indirectly indicate the type of relay operation supported by the network-side device, and also need to include the configuration parameters of the relay operation (if only one type of relay operation is supported, it only needs to include that type of relay operation). Configuration parameters of the relay operation; if two types of relay operations are supported at the same time, the configuration parameters of the two operations need to be included).
  • the configuration parameter of the relay operation includes at least one of the following:
  • the remote terminal is allowed to use the first condition information of the relay operation; for example, the conditions for allowing the L2 relay operation, such as the RSRP threshold condition of the remote terminal, the RSRP threshold condition of the relay terminal, etc.; or the L3 is allowed Relay operation conditions, such as RSRP threshold conditions of remote terminals, RSRP threshold conditions of relay terminals, etc.; the above-mentioned L2 relay operation conditions and L3 relay operation conditions can be configured independently and have different thresholds Or the conditions may be uniform, that is, the same threshold parameters or conditions are used for the L2 relay operation and the L3 relay operation.
  • the bearer configuration information when the remote terminal uses the relay operation for example, the bearer configuration information when the terminal performs L2 relay, such as the configuration of the RLC bearer; or, the bearer configuration information when the terminal performs L3 relay , Such as the corresponding configuration of SLRB (side link radio bearer) and RLC bearer.
  • L2 and L3 may be completely independent configurations and have different configuration domains; they may also be unified for the same part, that is, the L2 relay operation and the L3 relay operation use the same RLC bearer configuration.
  • the remote terminal selects the relay operation for data transmission, it selects the second condition information of the relay operation.
  • the second condition information includes at least one of the following:
  • Service information for example, if the service requirement or link of the terminal meets certain conditions, the L2 architecture is selected; if the service requirement or link of the terminal meets other conditions, the L3 architecture is selected. For another example, if the service of the terminal is public safety, the terminal selects the L3 architecture, and when it is other services, selects the L2 architecture;
  • Link information includes at least one of the following: link condition information of the Uu interface of the relay terminal; link condition information of the Uu interface of the remote terminal; Link condition information of the PC5 interface;
  • the association information between the remote terminal and the relay terminal for example, when the remote terminal and the relay terminal have a certain binding relationship (or called an association relationship), such as the mobile phone and wearable device of the same user, or they are in the same
  • the L3 architecture may be considered first, and the other L2 architecture may be used.
  • the remote terminal and the relay terminal belong to the same PLMN; or have the same communication restrictions.
  • a pair of terminals belonging to the same CSG can be allowed to access a CSG cell at the same time, and then the L2 architecture is allowed (so in this case
  • the remote terminal and the relay terminal are connected to the same base station at the same time), and when there is a coordinated or negotiated charging policy between the remote terminal and the relay terminal, the L3 relay operation can be selected, because the L3 relay operation
  • the network usage cost of the remote terminal may need to be negotiated and shared with the relay terminal;
  • the business information includes at least one of the following:
  • the service QoS of the terminal meets certain requirements, such as the priority meets a certain threshold, or the block error rate meets a certain threshold, or for a specific 5QI, the service is IP/non-IP data, and L2/L3 relay operation is used. Otherwise, another relay operation is used.
  • the relay related operations are performed under network control, that is, the remote terminal
  • the result of the operation needs to be notified to the network, so that the network can issue a reasonable configuration for subsequent relay operations; that is, the method also includes:
  • the remote terminal can directly perform the RRC process with the network side device, it can inform the base station that it wants to establish the transmission of the L2 relay operation through the RRC process, and the subsequent network side device will follow this requirement Establish the corresponding transmission pipeline and allocate resources for the remote terminal.
  • the remote terminal needs to be replaced by the relay terminal to initiate a relay request to the network side device.
  • the relay terminal will also request It carries the requirements of L3 relay, and the network side equipment establishes corresponding transmission pipes and allocates resources for the remote terminal according to the requirements.
  • the remote terminal sends the request of the relay operation of its choice to the network through its own RRC signaling (this signaling passes through the relay Terminal transfer), the network side device issues the corresponding reconfiguration message (for the remote terminal, it mainly includes the SLRB configuration, the RLC bearer configuration between the remote terminal and the relay terminal), and establishes a connection with the selected relay according to this reconfiguration message Operate the corresponding bearer configuration; at the same time, the relay terminal must also cooperate with this process to send the request of the relay operation to the network through its own RRC signaling, and the network sends the corresponding reconfiguration message (for the relay terminal, including The RLC bearer configuration between the remote terminal and the relay terminal, the RLC bearer configuration between the relay terminal and the network), according to this configuration, the relay terminal establishes the RLC bearer between the remote terminal and the network RLC bearer.
  • the relay terminal since there is not necessarily an RRC connection between the remote terminal and the network, the relay terminal sends a relay operation request to the network, and the network issues the corresponding reconfiguration message (mainly including the middle Following the terminal Uu bearer configuration L3+L2 protocol stack configuration, and the bearer configuration between the relay terminal and the remote terminal L3+L2 protocol stack configuration).
  • the remote terminal establishes RRC communication with the network by itself, while only the relay terminal in L3 has an RRC connection. Therefore, through different signaling procedures, the network can know which structure of the relay is currently requested, such as the L2 relay configuration requested by the RRC signaling of the remote terminal (the signaling of the remote terminal is transferred to the relay terminal through the relay terminal). Network), the RRC signaling of the relay terminal requests the L3 relay configuration (the relay terminal has its own signaling radio bearer SRB for signaling transmission).
  • the terminal when at least one relay operation exists, the terminal selects the corresponding relay operation for transmission according to the relay configuration information sent by the network side device, thereby making full use of the different relay operations. It not only guarantees the service quality QoS of the remote terminal service, but also considers the optimization of transmission efficiency, and improves the user experience while ensuring the system efficiency; when at least two relay operations exist, the network side instructs its support
  • the type of relay operation is based on the business information or the ability of the relay terminal to select the appropriate relay operation to carry the data bearer of the remote terminal, which can make full use of the advantages of various relay operations, avoid the shortcomings, and expand the flexibility of the system. Improve system performance and user experience.
  • the execution subject may be a relay determination device, or a control module in the relay determination device for executing loading the relay determination method.
  • the relay determining apparatus executed by the relay determining method is taken as an example to illustrate the relay determining apparatus provided in the embodiment of the present application.
  • an embodiment of the present application also provides a relay determining device 400, which is applied to a remote terminal, and includes:
  • the first receiving module 401 is configured to receive relay configuration information, where the relay configuration information includes at least one configuration parameter of a relay operation;
  • the relay determination module 402 is configured to determine the relay operation to be used according to the relay configuration information.
  • the device further includes:
  • the type determination module is configured to determine, according to the configuration parameters of the relay operation, the network-side device supports the relay operation type corresponding to the configuration parameter;
  • the relay configuration information further includes: a first indication field used to indicate the type of relay operation supported by the network side device.
  • the configuration parameter of the relay operation includes at least one of the following:
  • the remote terminal is allowed to use the first condition information of the relay operation
  • the remote terminal selects the relay operation for data transmission, it selects the second condition information of the relay operation.
  • the second condition information includes at least one of the following:
  • the service information includes at least one of the following:
  • the link information includes at least one of the following:
  • the relay configuration information includes two or more configuration parameters for relay operations
  • the relay determination module includes:
  • the relay determination submodule is configured to select one relay operation from the two or more relay operations as the relay operation to be used according to the relay configuration information and target parameters.
  • the target parameter includes at least one of the following:
  • the device further includes:
  • Broadcast module used to broadcast the relay operation to be used
  • the response receiving module is configured to receive a response message from a terminal that supports the relay operation, and determine that the terminal sending the response message is a relay terminal.
  • the device further includes:
  • a broadcast receiving module configured to receive second indication information broadcast by other terminals, where the second indication information is used to indicate the type of relay operation supported by the other terminal;
  • the selection module is configured to select a terminal that supports the relay operation to be used as the relay terminal according to the second instruction information.
  • the device further includes:
  • the first message sending module is configured to send a first message to a network side device, or a relay terminal to send a second message to a network side device; wherein, the first message or the second message carries the waiting message Request information of the relay operation used;
  • the reconfiguration receiving module is used to receive the reconfiguration message sent by the network side device or the relay terminal;
  • the bearer establishment module is used to establish a bearer corresponding to the requested relay operation according to the reconfiguration message.
  • the device further includes:
  • the transmission module is used to perform transmission related to the corresponding relay operation according to the established bearer.
  • the device further includes at least one of the following modules:
  • the second message sending module is configured to send a third PC5 RRC message to the relay terminal in the process of establishing a radio resource control RRC connection with the relay terminal.
  • the third PC5 RRC message contains an explicit indication or an implicit indication Indicate the relay operation to be used, and the third PC5 RRC message also carries bearer configuration information of the relay operation;
  • the third message sending module is used to send a fourth PC5 RRC message to the other remote terminal by the relay terminal in the process of establishing an RRC connection between the relay terminal and other remote terminals, the fourth PC5 RRC
  • the message explicitly or implicitly indicates the relay operation to be used, and the fourth PC5 RRC message also carries the bearer configuration information of the relay operation;
  • the fourth message sending module is used to send a fifth PC5 RRC message to the other remote terminal during the process of establishing an RRC connection with the other remote terminal.
  • the fifth PC5 RRC message contains an explicit indication or an implicit indication
  • the fifth PC5 RRC message also carries bearer configuration information of the relay operation.
  • the relay operation includes at least one of the following:
  • the L3 relay operation includes:
  • L3 relay protocol stack and the user plane session of the remote terminal is established by the network side device and the core network node of the relay terminal;
  • L3 relay protocol stack and the user plane session of the remote terminal is established by the network side device and the core network node of the remote terminal.
  • the terminal when at least one relay operation exists, the terminal selects the corresponding relay operation for transmission according to the relay configuration information sent by the network side device, thereby making full use of the characteristics of different relay operations.
  • the network side instructs the relay operations it supports Type, select the appropriate relay operation to carry the data bearer of the remote terminal based on the service information or the relay terminal capability, which can make full use of the advantages of various relay operations and avoid the shortcomings, thereby expanding the flexibility of the system and improving the performance of the system And user experience.
  • the execution subject of the relay configuration method provided in the embodiment of the present application may be a relay configuration device, or a control module in the relay configuration device for executing loading the relay configuration method.
  • the relay configuration method executed by the relay configuration apparatus is taken as an example to illustrate the relay configuration apparatus provided in the embodiment of the present application.
  • an embodiment of the present application also provides a relay configuration device 500, which is applied to a network side device, and includes:
  • the sending module 501 is configured to send relay configuration information, where the relay configuration information includes at least one configuration parameter of a relay operation.
  • the device further includes:
  • An indication module configured to instruct the network side device to support the relay operation type corresponding to the configuration parameter through the configuration parameter of the relay operation
  • the relay configuration information further includes: a first indication field used to indicate the type of relay operation supported by the network side device.
  • the configuration parameter of the relay operation includes at least one of the following:
  • the remote terminal is allowed to use the first condition information of the relay operation
  • the remote terminal selects the relay operation for data transmission, it selects the second condition information of the relay operation.
  • the second condition information includes at least one of the following:
  • the service information includes at least one of the following:
  • the link information includes at least one of the following:
  • the device further includes:
  • the message receiving module is configured to receive a first message sent by a remote terminal, or receive a second message sent by a relay terminal selected by the remote terminal, wherein the first message or the second message carries the The request information of the relay operation to be used determined by the remote terminal;
  • the configuration sending module is configured to send a reconfiguration message to the remote terminal or the relay terminal, where the reconfiguration message is used to instruct the remote terminal to establish a bearer corresponding to the requested relay operation.
  • the relay operation includes at least one of the following:
  • the L3 relay operation includes:
  • L3 relay protocol stack and the user plane session of the remote terminal is established by the network side device and the core network node of the relay terminal;
  • L3 relay protocol stack and the user plane session of the remote terminal is established by the network side device and the core network node of the remote terminal.
  • the terminal when at least one relay operation exists, the terminal selects the corresponding relay operation for transmission according to the relay configuration information sent by the network side device, thereby making full use of the characteristics of different relay operations.
  • the network side instructs the relay operations it supports Type, select the appropriate relay operation to carry the data bearer of the remote terminal based on the service information or the ability of the relay terminal, which can make full use of the advantages of various relay operations and avoid the disadvantages, thereby expanding the flexibility of the system and improving the performance of the system And user experience.
  • the relay determination device or the relay configuration device in the embodiment of the present application may be a device, or a component, an integrated circuit, or a chip in a terminal.
  • the device can be a mobile electronic device or a non-mobile electronic device.
  • the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a handheld computer, a vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (personal digital assistant).
  • UMPC ultra-mobile personal computer
  • netbook or a personal digital assistant (personal digital assistant).
  • non-mobile electronic devices can be servers, network attached storage (NAS), personal computers (PC), televisions (television, TV), teller machines or self-service machines, etc., this application
  • NAS network attached storage
  • PC personal computers
  • TV televisions
  • teller machines or self-service machines etc.
  • the relay determination device or the relay configuration device in the embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
  • the relay determination device or the relay configuration device provided in the embodiments of the present application can implement the various processes implemented by the method embodiments in FIG. 2 to FIG. 3, and to avoid repetition, details are not described herein again.
  • an embodiment of the present application further provides a communication device 600, including a processor 601, a memory 602, and a program or instruction that is stored in the memory 602 and can run on the processor 601,
  • a communication device 600 including a processor 601, a memory 602, and a program or instruction that is stored in the memory 602 and can run on the processor 601
  • the communication device 600 is a terminal
  • the program or instruction is executed by the processor 601
  • each process of the foregoing relay determination method embodiment is implemented, and the same technical effect can be achieved.
  • the communication device 600 is a network-side device, when the program or instruction is executed by the processor 601, each process of the foregoing relay configuration method embodiment is realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • FIG. 7 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.
  • the terminal 700 includes but is not limited to: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, processor 710 and other components .
  • the terminal 700 may also include a power source (such as a battery) for supplying power to various components.
  • the power source may be logically connected to the processor 710 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal structure shown in FIG. 7 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than those shown in the figure, or some components may be combined, or different component arrangements, which will not be repeated here.
  • the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042.
  • the graphics processor 7041 is paired by the image capture device ( For example, the image data of the still picture or video obtained by the camera) is processed.
  • the display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 707 includes a touch panel 7071 and other input devices 7072.
  • the touch panel 7071 is also called a touch screen.
  • the touch panel 7071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.
  • the radio frequency unit 701 receives the downlink data from the network-side device and sends it to the processor 710 for processing; in addition, it sends the uplink data to the network-side device.
  • the radio frequency unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the memory 709 can be used to store software programs or instructions and various data.
  • the memory 709 may mainly include a storage program or instruction area and a data storage area, where the storage program or instruction area may store an operating system, an application program or instructions required by at least one function (such as a sound playback function, an image playback function, etc.).
  • the memory 709 may include a high-speed random access memory, and may also include a non-volatile memory, where the non-volatile memory may be a read-only memory (Read-Only Memory, ROM) or a programmable read-only memory (Programmable ROM).
  • PROM erasable programmable read-only memory
  • Erasable PROM EPROM
  • Electrically erasable programmable read-only memory Electrically EPROM, EEPROM
  • flash memory For example, at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 710 may include one or more processing units; optionally, the processor 710 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc.
  • the modem processor mainly deals with wireless communication, such as a baseband processor. It can be understood that the foregoing modem processor may not be integrated into the processor 710.
  • the radio frequency unit 701 is configured to receive relay configuration information, where the relay configuration information includes at least one configuration parameter of a relay operation;
  • the processor 710 is configured to determine a relay operation to be used according to the relay configuration information.
  • the terminal when at least one relay operation exists, the terminal selects the corresponding relay operation for transmission according to the relay configuration information sent by the network side device, thereby making full use of the characteristics of different relay operations.
  • the network side instructs the relay operations it supports Type, select the appropriate relay operation to carry the data bearer of the remote terminal based on the service information or the relay terminal capability, which can make full use of the advantages of various relay operations and avoid the shortcomings, thereby expanding the flexibility of the system and improving the performance of the system And user experience.
  • the terminal provided in the embodiments of the present application is a terminal capable of executing the foregoing relay determination method, and all the foregoing embodiments of the relay determination method are applicable to the terminal, and can achieve the same or similar beneficial effects.
  • the embodiment of the present application also provides a network side device.
  • the network equipment 800 includes: an antenna 81, a radio frequency device 82, and a baseband device 83.
  • the antenna 81 is connected to the radio frequency device 82.
  • the radio frequency device 82 receives information through the antenna 81 and sends the received information to the baseband device 83 for processing.
  • the baseband device 83 processes the information to be sent and sends it to the radio frequency device 82, and the radio frequency device 82 processes the received information and sends it out via the antenna 81.
  • the foregoing frequency band processing device may be located in the baseband device 83, and the method executed by the network side device in the foregoing embodiment may be implemented in the baseband device 83.
  • the baseband device 83 includes a processor 84 and a memory 85.
  • the baseband device 83 may include, for example, at least one baseband board, and multiple chips are arranged on the baseband board, as shown in FIG.
  • the network device shown in the above method embodiment operates.
  • the baseband device 83 may also include a network interface 86 for exchanging information with the radio frequency device 82, and the interface is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 85 and running on the processor 84, and the processor 84 calls the instructions or programs in the memory 85 to execute the modules shown in FIG. 5
  • the method of implementation and achieve the same technical effect, in order to avoid repetition, so I will not repeat it here.
  • the embodiment of the present application also 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, each of the foregoing relay determination method or relay configuration method embodiments is implemented.
  • the processor is the processor in the electronic device described in the foregoing embodiment.
  • the readable storage medium includes a computer readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disks, or optical disks.
  • An embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used to run a program or an instruction to implement the above-mentioned relay determination method or medium Following the various processes of the configuration method embodiment, the same technical effect can be achieved, 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, for example, 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 can 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 parts may be physically separated or not physically separated.
  • the parts displayed as units may be physical units or not physical units, that is, they may be located in one place, or they may be distributed to 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 this application 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 methods described in the various embodiments of the present application.
  • 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 disc, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM), etc.
  • modules, units, and subunits can be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (Digital Signal Processor, DSP), digital signal processing equipment (DSP Device, DSPD) ), programmable logic devices (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, used to execute the present disclosure Described functions in other electronic units or combinations thereof.
  • ASIC application specific integrated circuits
  • DSP Digital Signal Processor
  • DSP Device digital signal processing equipment
  • PLD programmable logic devices
  • Field-Programmable Gate Array Field-Programmable Gate Array
  • 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种中继确定方法、配置方法、装置、终端及网络侧设备，该方法包括：接收中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数；根据所述中继配置信息，确定待使用的中继操作。

Description

中继确定方法、配置方法、装置、终端及网络侧设备
相关申请的交叉引用
本申请主张在2020年6月22日在中国提交的中国专利申请号No.202010576287.8的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于无线通信技术领域，具体涉及一种中继确定方法、配置方法、装置、终端及网络侧设备。
背景技术
长期演进(Long Term Evolution，LTE)系统开始支持旁链路(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接口。
目前的sidelink传输也主要分广播(broadcast)，组播(groupcast)，单播(unicast)几种传输形式。单播顾名思义就是一对一的传输。组播为一对多的传输。广播也是一对多的传输，但是广播并没有终端属于同一个组的概念。
目前Sidelink单播和组播通信支持物理层混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)反馈机制。
Sidelink终端的资源分配模式总共分为两类：
1)由网络侧设备(基站)控制并为每个终端分配资源；
2)由每个终端自主选择资源。
典型的中继场景中，远端终端(remote UE)通过和中继终端(relay UE)之间的Sidelink链路，由中继终端将远端终端的数据与目标终端之间进行转发。在这个场景中，远端终端1和远端终端2之间进行数据传输，中继终端起到数据中转作用。
在实现本申请过程中，发明人发现现有技术中至少存在如下问题：
现有机制中，可以支持L2中继架构或者L3中继架构。但在实际应用场景中终端如何确定使用哪种中继架构进行数据传输，目前并没有直接的方案。
发明内容
本申请实施例的目的是提供一种中继确定方法、配置方法、装置、终端及网络侧设备，能够解决如何确定使用哪种中继架构问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，本申请实施例提供了一种中继确定方法，应用于远端终端，包括：
接收中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数；
根据所述中继配置信息，确定待使用的中继操作。
第二方面，本申请实施例提供了一种中继配置方法，应用于网络侧设备，包括：
发送中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数。
第三方面，本申请实施例提供了一种中继确定装置，应用于远端终端，包括：
第一接收模块，用于接收中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数；
中继确定模块，用于根据所述中继配置信息，确定待使用的中继操作。
第四方面，本申请实施例提供了一种中继配置装置，应用于网络侧设备，包括：
发送模块，用于发送中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数。
第五方面，提供了一种终端，该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种网络侧设备，该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第七方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第八方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法。
第九方面，提供了一种计算机软件产品，所述计算机软件产品被存储在非易失的存储介质中，所述软件产品被配置成被至少一个处理器执行以实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十方面，提供了一种通信设备，所述通信设备被配置成用于执行如第一方面所述的方法，或执行如第二方面所述的方法。
在本申请实施例中，在至少一种中继操作存在的情况下，终端根据网络侧设备发送的中继配置信息选择对应的中继操作进行传输，从而充分利用不同中继操作的特点，既保证了远端终端业务的服务质量QoS，并考虑优化传输效率，在提升用户体验的同时保障了系统效率。
附图说明
图1表示本申请实施例应用的无线通信系统的框图；
图2表示本申请实施例提供的中继确定方法的步骤流程图；
图3表示本申请实施例提供的中继配置方法的步骤流程图；
图4表示本申请实施例提供的中继确定装置的结构示意图；
图5表示本申请实施例提供的中继配置装置的结构示意图；
图6表示本发明实施例提供的通信设备的结构示意图；
图7表示本发明实施例提供的终端的结构示意图；
图8表示本发明实施例提供的网络侧设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”等所区分的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”，一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR 术语，尽管这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、无线局域网(Wireless Local Area Network，WLAN)接入点、无线保真(Wireless Fidelity，WiFi)节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的中继确定方法、配置方法、装置、终端及网络侧设备进行详细地说明。
本申请实施例中提及的中继操作包括：
L2中继操作，和/或，L3中继操作。
典型的L2中继操作场景中，远端终端通过和中继终端之间的Sidelink链路，由中继终端将它的L2数据与基站之间进行转发。在这个场景中，第一远端终端和中继终端之间仅具有部分L2及以下协议栈，例如，仅包含RLC，MAC和PHY层，中继终端中转的数据类型为L2数据包，例如RLC服务数据单元(service Data Unit，SDU)，或者回程适应协议(Backhaul Adaptation  Protocol，BAP)SDU等，在中继终端不对远端终端的数据进行安全操作，数据安全由基站和远端终端之间端到端的PDCP协议层进行保障，对中继终端透明。L2中继操作能够使远端终端的数据享受端到端(远端终端和基站之间)的安全，对中继终端透明，且当远端终端切换时可以更好的提供业务连续性保障，因此业务的传输效果较好。
典型的L3中继操作场景中，远端终端通过和中继终端之间的Sidelink链路，由中继终端将它的L3数据与基站之间进行转发。在这个场景中，第一远端终端和中继终端之间具有较完整的协议栈，例如包含服务数据适配协议(Service Data Adaptation Protocol，SDAP)，分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)和无线资源控制(Radio Resource Control，RRC)层，也包含无线链路控制(Radio Link Control，RLC)层，媒体接入控制(Media Access Control，MAC)层和物理层(Physical layer，PHY)，中继终端中转的数据类型为L3数据包，例如IP数据包。L3中继操作的特点是实现较为简单，流程清晰。
其中，所述L3中继操作包括：
L3中继协议栈，且远端终端的用户面会话由网络侧设备与中继终端的核心网节点建立；
和/或，
L3中继协议栈，且远端终端的用户面会话由网络侧设备与远端终端的核心网节点建立。
本申请实施例提供的中继确定方法中网络侧设备至少支持一种中继操作，在其同时支持L2和L3两种中继操作时，远端终端在不同的部署场景中使用不同的中继操作，或者基于业务需求选择不同中继操作，或者根据中继终端能力选择不同的中继操作，这样可以最大限度的发挥L2/L3中继操作的优势，降低他们劣势的影响，提升系统效率和业务保障。
如图2所示，本申请实施例提供一种中继确定方法，应用于远端终端，包括：
步骤201，接收中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数；
步骤202，根据所述中继配置信息，确定待使用的中继操作。
本申请实施例中，网络侧设备向终端发送的中继配置信息中至少需要包含1种或1种以上的中继操作的配置参数，以使终端能够根据该类配置参数选择合适的中继操作来进行中继数据传输。
例如，中继配置信息包含一种中继操作的配置参数，则远端终端根据该中继操作的配置参数确定是否使用该中继操作；再例如，中继配置信息包含两种或两种以上中继操作的配置参数，则远端终端先根据配置参数判断是否使用中继操作并根据配置参数选择一种待使用的中继操作。
由于网络部署区域的业务需求和网络侧设备支持功能不同等因素，会导致运营商在每个网络侧设备需要支持不同的特性，例如在一定的地区，只有公共安全业务的需求，该业务数据重复性较高或者连续性要求不高，可以通过数字签名等方式来解决安全问题，因此不需要中继终端提供较为复杂的数据转发服务，此时可以选择在这些地区的基站，仅支持L3中继操作功能。例如在另一些地区，只有商业应用的中继操作场景，这些业务对连续性和安全有一定的要求，因此需要中继终端提供较为完善的数据转发服务，此时可以选择在这些地区的基站，仅支持L2中继操作功能。相应的，在另一些地区，上述两类应用都有需求，此时可以选择在这些地区的基站，同时支持L3中继操作和L2中继操作功能。这是从应用场景出发，对不同架构部署的需求考虑。在确定了需求之后，还需要对网络侧设备的软硬件版本进行升级或者更新，以支持相应的L2和/或L2中继操作，网络侧设备也可以根据自己的软硬件版本，决定支持哪种中继操作，或者二者都支持；且网络侧设备需要告知终端其自身支持的中继操作类型。具体的，作为一个可选实施例，所述方法还包括：
根据所述中继操作的配置参数，确定网络侧设备支持所述配置参数对应的中继操作类型。
换言之，网络侧设备通过中继操作的配置参数间接或隐式指示该网络侧设备支持的中继操作类型。例如：
网络侧设备发送了L2中继操作的配置参数，间接表明该网络侧设备支持L2中继操作；
网络侧设备发送了L3中继操作的配置参数，间接表明该网络侧设备支持L3中继操作；
网络侧设备发送了L2中继操作的配置参数和L3中继操作的配置参数，间接表明该网络侧设备同时支持L2中继操作和L3中继操作。
特殊地，若网络侧设备没有发送任何中继操作相关的配置参数，间接表明该网络侧设备不支持中继操作。
或者，作为另一个可选实施例，所述中继配置信息还包括：用于指示网络侧设备支持的中继操作类型的第一指示域。
换言之，网络侧设备通过中继配置信息中的第一指示域来直接指示该网络侧设备支持的中继操作类型。
例如，一种网络侧设备指示自身支持的中继操作类型的方式可以为，第一指示域包含三种选项：L3中继操作，L2中继操作，both(即同时支持L3中继操作和L2中继操作)；或者第一指示域包含四种选项：L3中继操作，L2中继操作，both(即同时支持L3中继操作和L2中继操作)，none(不支持中继操作)。在三种选项的情况下，网络侧设备通过该域缺省或者不出现，来指明自己不支持中继操作功能。在四种选项的情况下，基站可以通过该第一指示域取值为none来指明自己不支持中继操作功能。
可选地，上述中继配置信息可以通过系统消息或专用信令的方式发送给终端，中继操作类型一般包括：
网络侧设备不支持任何中继操作，则网络侧设备可以通过显式或者隐式的方式进行指示，显式方式是指网络侧设备通过显式信息域来表明，自己不支持中继操作；隐式是指网络侧设备只要没有携带任何中继操作的配置指示，例如没有说明支持，则默认基站不支持中继操作。在这种基站不支持中继操作的情况下，终端在得知网络侧设备不支持中继操作的情况下，则终端不允许发起中继请求和任何中继操作。
网络侧设备仅支持一种中继操作，例如L2中继操作或者L3中继操作；
网络侧设备仅支持一种中继操作，可以通过标准默认或者标准规定的方式，规定当网络侧设备表明自己支持一种中继操作类型时，网络侧设备可以通过显式的信息域来表明，自己支持的中继操作的类型。终端根据基站支持 的中继操作类型，发起相应的中继操作。类型是L2中继(或者L3中继)；当终端接收到网络侧设备的中继配置信息，则根据网络侧设备支持的中继操作类型，发起相应的中继操作。
网络侧设备支持两种中继操作，L2中继操作和L3中继操作，则网络侧设备可以通过显式的信息域来表明，自己支持的两种中继操作的类型。当终端接收到网络侧设备的中继配置信息，则根据网络侧设备支持的中继操作类型，可以发起相应的中继操作。
进一步的，中继配置信息除了需要直接或间接指示网络侧设备支持的中继操作类型之外，还需要包含中继操作的配置参数(如果只支持一种中继操作，则只需要包含该种中继操作的配置参数；如果同时支持两种中继操作，则需要包含两种操作操作的配置参数)。
作为一个可选实施例，所述中继操作的配置参数包括下述至少一项；
1)远端终端允许使用该中继操作的第一条件信息；例如，允许进行L2中继操作的条件，如远端终端的参考信号接收功率(Reference Signal Received Power，RSRP)门限条件，中继终端的RSRP门限条件等；或者允许进行L3中继操作的条件，如远端终端的RSRP门限条件，中继终端的RSRP门限条件等；上述L2中继操作的条件和L3中继操作的条件可以是分别独立配置，具有不同的门限值或者条件，也可能是统一的，即L2中继操作和L3中继操作使用相同的门限参数或者条件。
2)远端终端在使用该中继操作时的承载配置信息；例如，终端在进行L2中继时的承载配置信息，如RLC承载的配置；或者，终端在进行L3中继时的承载配置信息，如旁链路无线承载(Sidelink Radio Bearer，SLRB)和RLC承载对应的配置。上述承载配置中L2和L3可以是完全独立配置，具有不同的配置域；也可能对于相同部分是统一的，即L2中继操作和L3中继操作使用相同的RLC承载的配置。
3)远端终端在选择进行数据传输的中继操作时，选择该中继操作的第二条件信息。
其中，所述第二条件信息包括下述至少一项：
业务信息；例如，终端的业务需求或者链路满足一定条件，选择L2架构； 终端的业务需求或者链路满足其它条件，选择L3架构。再例如，终端的业务为公共安全，则终端选择L3架构，是其它业务时，选择L2架构；
链路信息；所述链路信息包括下述至少一项：中继终端的Uu接口的链路条件信息；远端终端的Uu接口的链路条件信息；远端终端与中继终端之间的PC5接口的链路条件信息；
远端终端和中继终端的关联信息；例如，当远端终端和中继终端有一定绑定关系(或称为关联关系)，例如同一个用户的手机和可穿戴设备，或者，处于同一个交通工具中的一起运动的两个终端，可以考虑优先使用L3架构，其它的使用L2架构。再例如，远端终端和中继终端属于同一个PLMN；或者具有相同的通信限制，例如属于同一个闭合用户组(Closed Subscriber Group，CSG)的一对终端可以允许同时接入一个CSG小区，才允许选择L2架构(因此此种情况下远端终端和中继终端同时连接到同一个基站)，而当远端终端和中继终端之间具有协同或者协商的计费策略情况下，可以选择L3中继操作，因为L3中继操作情况下，远端终端的网络使用费用情况可能需要与中继终端有所协商和分担；
中继操作选择策略。
其中，所述业务信息包含下述至少一项：
业务的服务质量QoS要求；
业务的时延信息；
业务的误块率；
业务的持续时间；
业务的安全需求；
业务连续性的需求。
例如，终端的业务QoS满足一定的要求，如优先级满足一定门限，或者误块率满足一定门限，或者针对特定的5G QoS标识符(5G QoS Identifier，5QI)，业务为IP/non-IP数据，则使用L2/L3中继操作，否则使用另一种中继操作。
作为一个可选实施例，在所述中继配置信息包含两种或两种以上中继操作的配置参数(即网络侧设备支持两种或两种以上中继操作)的情况下，步 骤202包括：
根据所述中继配置信息以及目标参数，从所述两种或两种以上中继操作中选择一种中继操作作为待使用的中继操作。
其中，所述目标参数包括下述至少一项：
远端终端的业务信息；
中继终端的能力信息；
远端终端与中继终端的关联信息。
在网络侧设备能够支持两种或两种以上中继操作的情况下，网络侧设备给出两种或两种以上中继操作的配置参数，根据远端终端的业务信息，选择待使用的中继操作。
例如，当终端有需要进行业务传输时，可以先判断是否满足中继操作的第一条件信息，例如终端与服务小区之间的RSRP低于一定的门限，则说明终端处于小区边缘，可以通过其它用户进行中转传输；如果L2和L3架构有不同的条件限制，而当终端此时只满足其中一个的条件，则只能发起满足条件的中继操作进行传输。当两种条件都满足时，可以根据业务信息选择一种中继操作，其中选择条件可以是网络侧配置的，或者预先规定的，或者终端自身的算法实现。
示例1，当终端发起特定业务时，可以选择对应的中继操作，例如公共安全业务使用L3中继操作，普通增强移动宽带(enhanced Mobile Broadband，eMBB)业务可以使用L2中继操作。
示例2，当终端发起的业务，具有特定标识，例如业务ID或者QoS ID，是属于某种中继操作所支持的列表中，则当终端发起这些业务时，选择对应的中继操作。
示例3，当终端发起的业务，具有一定特性，例如IP包，可以使用L3中继操作，non-IP(非IP)包可以使用L2中继操作。
示例4，当终端发起的业务，误块率要求较高，例如低于10^-6，此时要避免切换引起的丢包，可以采取L2中继操作。
示例5，当终端发起的业务，QoS要求较高，例如优先级高，或者对业务连续性有要求，此时要避免切换引起的丢包，可以采取L2中继操作。
示例6，当终端发起的业务，持续时间较短，例如少量数目的数据包发送之后，立即拆除链路，此时可以采用L3中继操作。
示例7，当发起业务的终端，与中继终端之间有一定的绑定\归属\协同\接入限制\费用分担等关系，例如同一个用户的手机和可穿戴设备之间，或者远端终端与中继终端处于同一个交通工具中共同移动，此时可以采用L3中继操作。
对于远端终端来说，L2中继操作和L3中继操作下，远端终端的能力需求是类似的，并没有有明显的区别，因此一般情况下远端终端从能力上能够同时支持两类中继操作。但由于版本原因，例如第一个版本仅支持L3中继操作，只有后一个增强版本才可以支持L2中继操作，那么对于第一版本的远端终端就只能选择L3中继操作，而后一个版本的远端终端就可以在两个中继操作中按需选择。但是在L2中继操作和L3中继操作下，中继终端的功能具有很大的差别，因此在选择中继操作时还可以参考中继终端的能力信息。
需要说明的是，L2中继操作中中继终端是转发RLC SDU(RLC服务数据单元)/BAP SDU(BAP服务数据单元)，不需要进行PDCP安全和头压缩等操作，但是L2中继操作中中继终端的两段链路具有的是RLC承载，RLC承载的配置和映射一般由网络侧设备控制和指示，按照现有接入回传一体化(Integrated Access Backhaul，IAB)的L2架构的例子，处于中间的中继节点需要具有F1接口功能，以完成数据中转。
L3中继操作中，中继终端是转发IP数据包或者说SDAP SDU(SDAP服务数据单元)，需要进行PDCP安全和头压缩等操作，且L3中继操作中中继终端的两段链路分别为与网络侧设备之间的Uu接口，与远端终端之间的PC5接口，协议栈和流程都可以复用现有，两端RB的映射可以由网络配置，不需要支持F1接口功能，就可以通过对两段链路的分别处理完成数据中转服务。
其中，中继终端的能力信息包括：
不支持任何中继功能；
支持L2中继操作功能，可以作为L2中继操作中的中继终端；
支持L3中继操作功能，可以作为L3中继操作中的中继终端；
同时支持L2中继操作功能和L3中继操作功能，既可以作为L2中继操 作中的中继终端，也可以作为L3中继操作中的中继终端。
综上，在远端终端根据自身的业务信息或者通信场景，选择了一个待使用的中继操作后，在与中继终端的交互过程中将自己的需求得到对方的确认，则后续可以按照选择的中继操作进行相应的建立和传输过程。
例如，当一个远端终端需要进行中继业务传输时，可以先根据自身的版本，业务信息等，确定需要发起哪种中继操作类型。之后可以在与中继终端的交互中，选择对应的具有该中继能力的中继终端。
作为一个可选实施例，所述方法还包括：
广播所述待使用的中继操作；
接收支持所述中继操作的终端的响应消息，确定发送所述响应消息的终端为中继终端。
例如，远端终端通过PC5接口对外广播，携带自己的中继业务请求，中继操作类型(L2/L3或者都可以)等信息，中继终端接收到该广播，根据自己的能力判断是否可以支持该中继操作类型的业务请求，如果可以，则向远端终端发送响应消息，如果不行，则忽略该请求消息。
或者，作为另一个可选实施例，所述方法还包括：
接收其他终端广播的第二指示信息，所述第二指示信息用于指示所述其他终端支持的中继操作类型；
根据所述第二指示信息，选择支持所述待使用的中继操作的终端作为中继终端。
例如，中继终端通过PC5接口对外广播，携带自己能支持的中继业务类型，中继操作种类(L2 or L3 or Both)等信息，远端终端接收到该广播，根据自己的业务需求判断是否需要该中继终端，如果条件满足，则向中继终端发送响应消息，如果不行，则忽略该广播消息。
一般情况下，如果有不止一个中继终端满足中继操作类型和业务需求，远端终端选择其中链路质量条件最好的中继终端，当在满足基本PC5通信要求的范围内，并没有找到满足中继操作类型和业务需要的中继终端时，远端终端可以自行判断是否扩大范围，例如远端终端希望进行L2中继操作，但就近的满足通信要求的范围内，并没有具有L2中继功能的终端，则远端终端 可以自行决定是否选择其中一个满足通信要求的L3中继进行服务。
作为一个可选实施例，在中继终端与远端终端就中继操作类型协商完毕之后，在“终端to网络”的中继场景中，中继相关操作在网络控制下进行，即远端终端的操作结果需要告知网络，从而使得网络能够下发合理的配置，用于后续中继操作；即所述方法还包括：
向网络侧设备发送第一消息，或者，由中继终端向网络侧设备发送第二消息；其中，所述第一消息或所述第二消息中携带所述待使用的中继操作的请求信息；
接收网络侧设备或中继终端发送的重配置消息；
根据所述重配置消息建立与请求的中继操作对应的承载。
如果是L2中继操作，由于远端终端可以和网络侧设备之间直接进行RRC过程，因此可以通过该RRC过程，告知基站自己想要建立L2中继操作的传输，后续网络侧设备根据该需求为远端终端建立相应的传输管道和分配资源等。如果是L3中继操作，远端终端和网络侧设备之间没有直接的RRC连接，远端终端需要由中继终端替代向网络侧设备发起中继请求，类似的，中继终端也会在请求中携带L3中继的需求，由网络侧设备根据该需求为远端终端建立相应的传输管道和分配资源等。
具体的，对于L2中继操作，由于远端终端和网络之间有RRC连接，则远端终端通过自己的RRC信令将自己选择的中继操作的请求发给网络(这个信令通过中继终端中转)，由网络侧设备下发相应重配置消息(对远端终端主要包括SLRB配置，远端终端和中继终端之间的RLC承载配置)，根据这个重配置消息，建立与所选中继操作对应的承载配置；同时，中继终端也要配合这个过程，通过自己的RRC信令将中继操作的请求给网络，由网络下发相应的重配置消息(对中继终端来说，包括远端终端和中继终端之间的RLC承载配置，中继终端和网络之间的RLC承载配置)，根据这个配置，中继终端建立与远端终端之间的RLC承载，以及与网络之间的RLC承载。
具体的，对于L3中继操作，由于远端终端和网络之间不一定有RRC连接，则由中继终端将中继操作请求发送给网络，由网络下发相应的重配置消息(主要包括中继终端的Uu承载配置L3+L2协议栈配置，以及中继终端与 远端终端之间的承载配置L3+L2协议栈配置)。
需要说明的是，在上述流程中，可以不通过显式的域来指示和区分到底是L2/L3中继操作，由于L2/L3中继操作在架构和信令流程中有着显著的不同，L2中继操作是由远端终端自行建立RRC与网络通信，而L3仅有中继终端具有RRC连接。因此通过不同的信令流程，网络就可以知道当前请求的中继是哪种架构，例如远端终端的RRC信令请求的L2中继配置(远端终端的信令是通过中继终端中转给网络的)，中继终端的RRC信令请求的是L3中继配置(中继终端自己有信令无线承载SRB用于信令传输)。
进一步的，承载建立成功之后，所述方法还包括：
根据建立的承载，进行对应中继操作相关的传输。其中，按照配置的承载，中继终端在不同的中继操作中，完成不一样的转发动作：例如L2中继操作转发的是L2PDU；L3中继操作转发的是相当于IP数据包，non-IP的L3数据包。
另外，针对L3中继操作，有两个分支，一个是中继终端建立自己的核心网承载，用于远端终端数据传输，另一种是中继终端为远端终端建立核心网承载，用于远端终端数据传输。在这两种情况下，可以区分上述请求中携带信息，例如类型指示，或者其它区分信息，便于后续的不同操作。对于网络来说，收到的指示不同，则发起核心网承载建立时携带的信息，甚至核心网节点都不一样(中继终端对应的核心网节点，远端终端对应的核心网节点)。同样的，在建立好之后的传输过程，上述两种方式也会存在差别，比如IP地址处理不一样，在此不展开说明。
作为又一个可选实施例，在中继终端与远端终端就中继操作类型协商完毕之后，在“终端to终端”的中继场景中，配置参数来自于网络，承载配置过程是远端终端1与远端终端2(即其他远端终端)之间的。
需要说明的是，在“终端to终端”的中继场景中，远端终端1可以称为源终端，远端终端2可以称为目标终端。也就是说，在终端to终端”的中继场景中，本申请实施例中提及的“远端终端”均可以替换为“源终端”，在此不做具体限定。
首先，发现过程中，发起的远端终端1通过跟中继终端、以及中继终端 与远端终端2之间的发现过程，都需要确认使用相同的中继操作，协商好待使用的中继操作之后，所述方法还包括下述至少一个步骤：
在与中继终端建立无线资源控制RRC连接的过程中，向所述中继终端发送第三PC5 RRC消息，所述第三PC5 RRC消息中显式指示或隐式指示待使用的中继操作，所述第三PC5 RRC消息还携带所述中继操作的承载配置信息；
在中继终端与其他远端终端建立RRC连接的过程中，由所述中继终端向所述其他远端终端发送第四PC5 RRC消息，所述第四PC5 RRC消息中显式指示或隐式指示待使用的中继操作，所述第四PC5 RRC消息还携带所述中继操作的承载配置信息；
在与其他远端终端建立RRC连接的过程中，向所述其他远端终端发送第五PC5 RRC消息，所述第五PC5 RRC消息中显式指示或隐式指示待使用的中继操作，所述第五PC5 RRC消息还携带所述中继操作的承载配置信息。
例如，对于L2中继操作：
远端终端1和远端终端2之间有RRC过程，因此这个RRC过程中，需要显式或者隐式携带中继操作的标识，以及与该中继操作相关的承载配置，例如SLRB配置；
远端终端1和中继终端之间的RRC过程，也需要携带显式或者隐式携带中继操作的标识，以及与该中继操作相关的承载配置，例如RLC承载配置(用于中继终端和远端终端1)；
远端终端2和中继终端之间的RRC过程，也需要携带显式或者隐式携带中继操作的标识，以及与该中继操作相关的配置，例如RLC承载配置(用于中继终端和远端终端2)。
再例如，对于L3中继操作：
远端终端1和远端终端UE2之间没有直接的RRC过程；
远端终端1和中继终端之间的RRC过程，也需要携带显式或者隐式携带中继操作的标识，以及与该中继操作相关的配置，例如SLRB+RLC承载配置(用于中继终端和远端终端1)；
远端终端2和中继终端之间的RRC过程，也需要携带显式或者隐式携带中继操作的标识，以及与该中继操作相关的配置，例如SLRB+RLC承载配置 (用于中继终端和远端终端2)。
综上，在本申请实施例中，在至少一种中继操作存在的情况下，终端根据网络侧设备发送的中继配置信息选择对应的中继操作进行传输，从而充分利用不同中继操作的特点，既保证了远端终端业务的服务质量QoS，并考虑优化传输效率，在提升用户体验的同时保障了系统效率；在至少两种中继操作存在的情况下，由网络侧指示其支持的中继操作类型，由业务信息或中继终端能力来选择合适的中继操作来进行远端终端的数据承载，能够充分利用各种中继操作的优点，规避缺点，从而扩展系统的灵活性，提高系统性能和用户体验。
如图3所示，本申请实施例还提供一种中继配置方法，应用于网络侧设备，包括：
步骤301，发送中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数。
本申请实施例中，网络侧设备向终端发送的中继配置信息中至少需要包含1种或1种以上的中继操作的配置参数，以使终端能够根据该类配置参数选择合适的中继操作来进行中继数据传输。
例如，中继配置信息包含一种中继操作的配置参数，则远端终端根据该中继操作的配置参数确定是否使用该中继操作；再例如，中继配置信息包含两种或两种以上中继操作的配置参数，则远端终端先根据配置参数判断是否使用中继操作并根据配置参数选择一种待使用的中继操作。
由于网络部署区域的业务需求和网络侧设备支持功能不同等因素，会导致运营商在每个网络侧设备需要支持不同的特性，例如在一定的地区，只有公共安全业务的需求，该业务数据重复性较高或者连续性要求不高，可以通过数字签名等方式来解决安全问题，因此不需要中继终端提供较为复杂的数据转发服务，此时可以选择在这些地区的基站，仅支持L3中继操作功能。例如在另一些地区，只有商业应用的中继操作场景，这些业务对连续性和安全有一定的要求，因此需要中继终端提供较为完善的数据转发服务，此时可以选择在这些地区的基站，仅支持L2中继操作功能。相应的，在另一些地区，上述两类应用都有需求，此时可以选择在这些地区的基站，同时支持L3中继 操作和L2中继操作功能。这是从应用场景出发，对不同架构部署的需求考虑。在确定了需求之后，还需要对网络侧设备的软硬件版本进行升级或者更新，以支持相应的L2和/或L2中继操作，网络侧设备也可以根据自己的软硬件版本，决定支持哪种中继操作，或者二者都支持；且网络侧设备需要告知终端其自身支持的中继操作类型。具体的，作为一个可选实施例，所述方法还包括：
通过所述中继操作的配置参数，指示所述网络侧设备支持所述配置参数对应的中继操作类型；换言之，网络侧设备通过中继操作的配置参数间接或隐式指示该网络侧设备支持的中继操作类型。例如：
网络侧设备发送了L2中继操作的配置参数，间接表明该网络侧设备支持L2中继操作；
网络侧设备发送了L3中继操作的配置参数，间接表明该网络侧设备支持L3中继操作；
网络侧设备发送了L2中继操作的配置参数和L3中继操作的配置参数，间接表明该网络侧设备同时支持L2中继操作和L3中继操作。
特殊地，若网络侧设备没有发送任何中继操作相关的配置参数，间接表明该网络侧设备不支持中继操作。
或者，作为另一个可选实施例，所述中继配置信息还包括：用于指示网络侧设备支持的中继操作类型的第一指示域。换言之，网络侧设备通过中继配置信息中的第一指示域来直接指示该网络侧设备支持的中继操作类型。
例如，一种网络侧设备指示自身支持的中继操作类型的方式可以为，第一指示域包含三种选项：L3中继操作，L2中继操作，both(即同时支持L3中继操作和L2中继操作)；或者第一指示域包含四种选项：L3中继操作，L2中继操作，both(即同时支持L3中继操作和L2中继操作)，none(不支持中继操作)。在三种选项的情况下，网络侧设备通过该域缺省或者不出现，来指明自己不支持中继操作功能。在四种选项的情况下，基站可以通过该第一指示域取值为none来指明自己不支持中继操作功能。
可选地，上述中继配置信息可以通过系统消息或专用信令的方式发送给终端。
进一步的，中继配置信息除了需要直接或间接指示网络侧设备支持的中继操作类型之外，还需要包含中继操作的配置参数(如果只支持一种中继操作，则只需要包含该种中继操作的配置参数；如果同时支持两种中继操作，则需要包含两种操作操作的配置参数)。
作为一个可选实施例，所述中继操作的配置参数包括下述至少一项；
1)远端终端允许使用该中继操作的第一条件信息；例如，允许进行L2中继操作的条件，如远端终端的RSRP门限条件，中继终端的RSRP门限条件等；或者允许进行L3中继操作的条件，如远端终端的RSRP门限条件，中继终端的RSRP门限条件等；上述L2中继操作的条件和L3中继操作的条件可以是分别独立配置，具有不同的门限值或者条件，也可能是统一的，即L2中继操作和L3中继操作使用相同的门限参数或者条件。
2)远端终端在使用该中继操作时的承载配置信息；例如，终端在进行L2中继时的承载配置信息，如RLC承载的配置；或者，终端在进行L3中继时的承载配置信息，如SLRB(旁链路无线承载)和RLC承载对应的配置。上述承载配置中L2和L3可以是完全独立配置，具有不同的配置域；也可能对于相同部分是统一的，即L2中继操作和L3中继操作使用相同的RLC承载的配置。
3)远端终端在选择进行数据传输的中继操作时，选择该中继操作的第二条件信息。
其中，所述第二条件信息包括下述至少一项：
业务信息；例如，终端的业务需求或者链路满足一定条件，选择L2架构；终端的业务需求或者链路满足其它条件，选择L3架构。再例如，终端的业务为公共安全，则终端选择L3架构，是其它业务时，选择L2架构；
链路信息；所述链路信息包括下述至少一项：中继终端的Uu接口的链路条件信息；远端终端的Uu接口的链路条件信息；远端终端与中继终端之间的PC5接口的链路条件信息；
远端终端和中继终端的关联信息；例如，当远端终端和中继终端有一定绑定关系(或称为关联关系)，例如同一个用户的手机和可穿戴设备，或者，处于同一个交通工具中的一起运动的两个终端，可以考虑优先使用L3架构， 其它的使用L2架构。再例如，远端终端和中继终端属于同一个PLMN；或者具有相同的通信限制，例如属于同一个CSG的一对终端可以允许同时接入一个CSG小区，才允许选择L2架构(因此此种情况下远端终端和中继终端同时连接到同一个基站)，而当远端终端和中继终端之间具有协同或者协商的计费策略情况下，可以选择L3中继操作，因为L3中继操作情况下，远端终端的网络使用费用情况可能需要与中继终端有所协商和分担；
中继操作选择策略。
其中，所述业务信息包含下述至少一项：
业务的服务质量QoS要求；
业务的时延信息；
业务的误块率；
业务的持续时间；
业务的安全需求；
业务连续性的需求。
例如，终端的业务QoS满足一定的要求，如优先级满足一定门限，或者误块率满足一定门限，或者针对特定的5QI，业务为IP/non-IP数据，则使用L2/L3中继操作，否则使用另一种中继操作。
作为一个可选实施例，在中继终端与远端终端就中继操作类型协商完毕之后，在“终端to网络”的中继场景中，中继相关操作在网络控制下进行，即远端终端的操作结果需要告知网络，从而使得网络能够下发合理的配置，用于后续中继操作；即所述方法还包括：
接收远端终端发送的第一消息，或者，接收远端终端选择的中继终端发送的第二消息，其中，所述第一消息或所述第二消息中携带所述远端终端确定的待使用的中继操作的请求信息；
向远端终端或中继终端发送重配置消息，所述重配置消息用于指示远端终端建立与请求的中继操作对应的承载。
如果是L2中继操作，由于远端终端可以和网络侧设备之间直接进行RRC过程，因此可以通过该RRC过程，告知基站自己想要建立L2中继操作的传输，后续网络侧设备根据该需求为远端终端建立相应的传输管道和分配资源 等。如果是L3中继操作，远端终端和网络侧设备之间没有直接的RRC连接，远端终端需要由中继终端替代向网络侧设备发起中继请求，类似的，中继终端也会在请求中携带L3中继的需求，由网络侧设备根据该需求为远端终端建立相应的传输管道和分配资源等。
具体的，对于L2中继操作，由于远端终端和网络之间有RRC连接，则远端终端通过自己的RRC信令将自己选择的中继操作的请求发给网络(这个信令通过中继终端中转)，由网络侧设备下发相应重配置消息(对远端终端主要包括SLRB配置，远端终端和中继终端之间的RLC承载配置)，根据这个重配置消息，建立与所选中继操作对应的承载配置；同时，中继终端也要配合这个过程，通过自己的RRC信令将中继操作的请求给网络，由网络下发相应的重配置消息(对中继终端来说，包括远端终端和中继终端之间的RLC承载配置，中继终端和网络之间的RLC承载配置)，根据这个配置，中继终端建立与远端终端之间的RLC承载，以及与网络之间的RLC承载。
具体的，对于L3中继操作，由于远端终端和网络之间不一定有RRC连接，则由中继终端将中继操作请求发送给网络，由网络下发相应的重配置消息(主要包括中继终端的Uu承载配置L3+L2协议栈配置，以及中继终端与远端终端之间的承载配置L3+L2协议栈配置)。
需要说明的是，在上述流程中，可以不通过显式的域来指示和区分到底是L2/L3中继操作，由于L2/L3中继操作在架构和信令流程中有着显著的不同，L2中继操作是由远端终端自行建立RRC与网络通信，而L3仅有中继终端具有RRC连接。因此通过不同的信令流程，网络就可以知道当前请求的中继是哪种架构，例如远端终端的RRC信令请求的L2中继配置(远端终端的信令是通过中继终端中转给网络的)，中继终端的RRC信令请求的是L3中继配置(中继终端自己有信令无线承载SRB用于信令传输)。
综上，在本申请实施例中，在至少一种中继操作存在的情况下，终端根据网络侧设备发送的中继配置信息选择对应的中继操作进行传输，从而充分利用不同中继操作的特点，既保证了远端终端业务的服务质量QoS，并考虑优化传输效率，在提升用户体验的同时保障了系统效率；在至少两种中继操作存在的情况下，由网络侧指示其支持的中继操作类型，由业务信息或中继 终端能力来选择合适的中继操作来进行远端终端的数据承载，能够充分利用各种中继操作的优点，规避缺点，从而扩展系统的灵活性，提高系统性能和用户体验。
需要说明的是，本申请实施例提供的中继确定方法，执行主体可以为中继确定装置，或者该中继确定装置中的用于执行加载该中继确定方法的控制模块。本申请实施例中以中继确定装置执行中继确定方法为例，说明本申请实施例提供的中继确定装置。
如图4所示，本申请实施例还提供一种中继确定装置400，应用于远端终端，包括：
第一接收模块401，用于接收中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数；
中继确定模块402，用于根据所述中继配置信息，确定待使用的中继操作。
作为一个可选实施例，所述装置还包括：
类型确定模块，用于根据所述中继操作的配置参数，确定网络侧设备支持所述配置参数对应的中继操作类型；
或者，所述中继配置信息还包括：用于指示网络侧设备支持的中继操作类型的第一指示域。
作为一个可选实施例，所述中继操作的配置参数包括下述至少一项；
远端终端允许使用该中继操作的第一条件信息；
远端终端在使用该中继操作时的承载配置信息；
远端终端在选择进行数据传输的中继操作时，选择该中继操作的第二条件信息。
作为一个可选实施例，所述第二条件信息包括下述至少一项：
业务信息；
链路信息；
远端终端和中继终端的关联信息；
中继操作选择策略。
作为一个可选实施例，所述业务信息包含下述至少一项：
业务的服务质量QoS要求；
业务的时延信息；
业务的误块率；
业务的持续时间；
业务的安全需求；
业务连续性的需求。
作为一个可选实施例，所述链路信息包括下述至少一项：
中继终端的Uu接口的链路条件信息；
远端终端的Uu接口的链路条件信息；
远端终端与中继终端之间的PC5接口的链路条件信息。
作为一个可选实施例，在所述中继配置信息包含两种或两种以上中继操作的配置参数的情况下，
所述中继确定模块包括：
中继确定子模块，用于根据所述中继配置信息以及目标参数，从所述两种或两种以上中继操作中选择一种中继操作作为待使用的中继操作。
作为一个可选实施例，所述目标参数包括下述至少一项：
远端终端的业务信息；
中继终端的能力信息；
远端终端与中继终端的关联信息。
作为一个可选实施例，所述装置还包括：
广播模块，用于广播所述待使用的中继操作；
响应接收模块，用于接收支持所述中继操作的终端的响应消息，确定发送所述响应消息的终端为中继终端。
作为一个可选实施例，所述装置还包括：
广播接收模块，用于接收其他终端广播的第二指示信息，所述第二指示信息用于指示所述其他终端支持的中继操作类型；
选择模块，用于根据所述第二指示信息，选择支持所述待使用的中继操作的终端作为中继终端。
作为一个可选实施例，所述装置还包括：
第一消息发送模块，用于向网络侧设备发送第一消息，或者，由中继终端向网络侧设备发送第二消息；其中，所述第一消息或所述第二消息中携带所述待使用的中继操作的请求信息；
重配置接收模块，用于接收网络侧设备或中继终端发送的重配置消息；
承载建立模块，用于根据所述重配置消息建立与请求的中继操作对应的承载。
作为一个可选实施例，所述装置还包括：
传输模块，用于根据建立的承载，进行对应中继操作相关的传输。
作为一个可选实施例，所述装置还包括下述至少一个模块：
第二消息发送模块，用于在与中继终端建立无线资源控制RRC连接的过程中，向所述中继终端发送第三PC5 RRC消息，所述第三PC5 RRC消息中显式指示或隐式指示待使用的中继操作，所述第三PC5 RRC消息还携带所述中继操作的承载配置信息；
第三消息发送模块，用于在中继终端与其他远端终端建立RRC连接的过程中，由所述中继终端向所述其他远端终端发送第四PC5 RRC消息，所述第四PC5 RRC消息中显式指示或隐式指示待使用的中继操作，所述第四PC5 RRC消息还携带所述中继操作的承载配置信息；
第四消息发送模块，用于在与其他远端终端建立RRC连接的过程中，向所述其他远端终端发送第五PC5 RRC消息，所述第五PC5 RRC消息中显式指示或隐式指示待使用的中继操作，所述第五PC5 RRC消息还携带所述中继操作的承载配置信息。
作为一个可选实施例，所述中继操作包括下述至少一种：
L2中继操作；
L3中继操作。
作为一个可选实施例，所述L3中继操作包括：
L3中继协议栈，且远端终端的用户面会话由网络侧设备与中继终端的核心网节点建立；
和/或，
L3中继协议栈，且远端终端的用户面会话由网络侧设备与远端终端的核 心网节点建立。
在本申请实施例中，在至少一种中继操作存在的情况下，终端根据网络侧设备发送的中继配置信息选择对应的中继操作进行传输，从而充分利用不同中继操作的特点，既保证了远端终端业务的服务质量QoS，并考虑优化传输效率，在提升用户体验的同时保障了系统效率；在至少两种中继操作存在的情况下，由网络侧指示其支持的中继操作类型，由业务信息或中继终端能力来选择合适的中继操作来进行远端终端的数据承载，能够充分利用各种中继操作的优点，规避缺点，从而扩展系统的灵活性，提高系统性能和用户体验。
需要说明的是，本申请实施例提供的中继配置方法，执行主体可以为中继配置装置，或者该中继配置装置中的用于执行加载该中继配置方法的控制模块。本申请实施例中以中继配置装置执行中继配置方法为例，说明本申请实施例提供的中继配置装置。
如图5所示，本申请实施例还提供一种中继配置装置500，应用于网络侧设备，包括：
发送模块501，用于发送中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数。
作为一个可选实施例，所述装置还包括：
指示模块，用于通过所述中继操作的配置参数，指示所述网络侧设备支持所述配置参数对应的中继操作类型；
或者，所述中继配置信息还包括：用于指示网络侧设备支持的中继操作类型的第一指示域。
作为一个可选实施例，所述中继操作的配置参数包括下述至少一项；
远端终端允许使用该中继操作的第一条件信息；
远端终端在使用该中继操作时的承载配置信息；
远端终端在选择进行数据传输的中继操作时，选择该中继操作的第二条件信息。
作为一个可选实施例，所述第二条件信息包括下述至少一项：
业务信息；
链路信息；
远端终端和中继终端的关联信息；
中继操作选择策略。
作为一个可选实施例，所述业务信息包含下述至少一项：
业务的服务质量QoS要求；
业务的时延信息；
业务的误块率；
业务的持续时间；
业务的安全需求；
业务连续性的需求。
作为一个可选实施例，所述链路信息包括下述至少一项：
中继终端的Uu接口的链路条件信息；
远端终端的Uu接口的链路条件信息；
远端终端与中继终端之间的PC5接口的链路条件信息。
作为一个可选实施例，所述装置还包括：
消息接收模块，用于接收远端终端发送的第一消息，或者，接收远端终端选择的中继终端发送的第二消息，其中，所述第一消息或所述第二消息中携带所述远端终端确定的待使用的中继操作的请求信息；
配置发送模块，用于向远端终端或中继终端发送重配置消息，所述重配置消息用于指示远端终端建立与请求的中继操作对应的承载。
作为一个可选实施例，所述中继操作包括下述至少一种：
L2中继操作；
L3中继操作。
作为一个可选实施例，所述L3中继操作包括：
L3中继协议栈，且远端终端的用户面会话由网络侧设备与中继终端的核心网节点建立；
和/或，
L3中继协议栈，且远端终端的用户面会话由网络侧设备与远端终端的核心网节点建立。
在本申请实施例中，在至少一种中继操作存在的情况下，终端根据网络侧设备发送的中继配置信息选择对应的中继操作进行传输，从而充分利用不同中继操作的特点，既保证了远端终端业务的服务质量QoS，并考虑优化传输效率，在提升用户体验的同时保障了系统效率；在至少两种中继操作存在的情况下，由网络侧指示其支持的中继操作类型，由业务信息或中继终端能力来选择合适的中继操作来进行远端终端的数据承载，能够充分利用各种中继操作的优点，规避缺点，从而扩展系统的灵活性，提高系统性能和用户体验。
本申请实施例中的中继确定装置或中继配置装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动电子设备，也可以为非移动电子设备。示例性的，移动电子设备可以为手机、平板电脑、笔记本电脑、掌上电脑、车载电子设备、可穿戴设备、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本或者个人数字助理(personal digital assistant，PDA)等，非移动电子设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的中继确定装置或中继配置装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的中继确定装置或中继配置装置能够实现图2至图3的方法实施例实现的各个过程，为避免重复，这里不再赘述。
可选的，如图6所示，本申请实施例还提供一种通信设备600，包括处理器601，存储器602，存储在存储器602上并可在所述处理器601上运行的程序或指令，例如，该通信设备600为终端时，该程序或指令被处理器601执行时实现上述中继确定方法实施例的各个过程，且能达到相同的技术效果。该通信设备600为网络侧设备时，该程序或指令被处理器601执行时实现上述中继配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图7为实现本申请实施例的一种终端的硬件结构示意图。该终端700包 括但不限于：射频单元701、网络模块702、音频输出单元703、输入单元704、传感器705、显示单元706、用户输入单元707、接口单元708、存储器709、以及处理器710等部件。
本领域技术人员可以理解，终端700还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器710逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图7中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元704可以包括图形处理器(Graphics Processing Unit，GPU)7041和麦克风7042，图形处理器7041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元706可包括显示面板7061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板7061。用户输入单元707包括触控面板7071以及其他输入设备7072。触控面板7071，也称为触摸屏。触控面板7071可包括触摸检测装置和触摸控制器两个部分。其他输入设备7072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元701将来自网络侧设备的下行数据接收后，给处理器710处理；另外，将上行的数据发送给网络侧设备。通常，射频单元701包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器709可用于存储软件程序或指令以及各种数据。存储器709可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器709可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存 器件、或其他非易失性固态存储器件。
处理器710可包括一个或多个处理单元；可选的，处理器710可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器710中。
其中，射频单元701，用于接收中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数；
处理器710，用于根据所述中继配置信息，确定待使用的中继操作。
在本申请实施例中，在至少一种中继操作存在的情况下，终端根据网络侧设备发送的中继配置信息选择对应的中继操作进行传输，从而充分利用不同中继操作的特点，既保证了远端终端业务的服务质量QoS，并考虑优化传输效率，在提升用户体验的同时保障了系统效率；在至少两种中继操作存在的情况下，由网络侧指示其支持的中继操作类型，由业务信息或中继终端能力来选择合适的中继操作来进行远端终端的数据承载，能够充分利用各种中继操作的优点，规避缺点，从而扩展系统的灵活性，提高系统性能和用户体验。
需要说明的是，本申请实施例提供的终端是能够执行上述中继确定方法的终端，则上述中继确定方法的所有实施例均适用于该终端，且均能达到相同或相似的有益效果。
具体地，本申请实施例还提供了一种网络侧设备。如图8所示，该网络设备800包括：天线81、射频装置82、基带装置83。天线81与射频装置82连接。在上行方向上，射频装置82通过天线81接收信息，将接收的信息发送给基带装置83进行处理。在下行方向上，基带装置83对要发送的信息进行处理，并发送给射频装置82，射频装置82对收到的信息进行处理后经过天线81发送出去。
上述频带处理装置可以位于基带装置83中，以上实施例中网络侧设备执行的方法可以在基带装置83中实现，该基带装置83包括处理器84和存储器85。
基带装置83例如可以包括至少一个基带板，该基带板上设置有多个芯片， 如图8所示，其中一个芯片例如为处理器84，与存储器85连接，以调用存储器85中的程序，执行以上方法实施例中所示的网络设备操作。
该基带装置83还可以包括网络接口86，用于与射频装置82交互信息，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备还包括：存储在存储器85上并可在处理器84上运行的指令或程序，处理器84调用存储器85中的指令或程序执行图5所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述中继确定方法或中继配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的电子设备中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(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 (36)

  1. 一种中继确定方法，应用于远端终端，包括：
    接收中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数；
    根据所述中继配置信息，确定待使用的中继操作。
  2. 根据权利要求1所述的方法，还包括：
    根据所述中继操作的配置参数，确定网络侧设备支持所述配置参数对应的中继操作类型；
    或者，所述中继配置信息还包括：用于指示网络侧设备支持的中继操作类型的第一指示域。
  3. 根据权利要求1所述的方法，其中，所述中继操作的配置参数包括下述至少一项；
    远端终端允许使用该中继操作的第一条件信息；
    远端终端在使用该中继操作时的承载配置信息；
    远端终端在选择进行数据传输的中继操作时，选择该中继操作的第二条件信息。
  4. 根据权利要求3所述的方法，其中，所述第二条件信息包括下述至少一项：
    业务信息；
    链路信息；
    远端终端和中继终端的关联信息；
    中继操作选择策略。
  5. 根据权利要求4所述的方法，其中，所述业务信息包含下述至少一项：
    业务的服务质量QoS要求；
    业务的时延信息；
    业务的误块率；
    业务的持续时间；
    业务的安全需求；
    业务连续性的需求。
  6. 根据权利要求4所述的方法，其中，所述链路信息包括下述至少一项：
    中继终端的Uu接口的链路条件信息；
    远端终端的Uu接口的链路条件信息；
    远端终端与中继终端之间的PC5接口的链路条件信息。
  7. 根据权利要求1所述的方法，其中，在所述中继配置信息包含两种或两种以上中继操作的配置参数的情况下，
    所述根据所述中继配置信息，确定待使用的中继操作，包括：
    根据所述中继配置信息以及目标参数，从所述两种或两种以上中继操作中选择一种中继操作作为待使用的中继操作。
  8. 根据权利要求7所述的方法，其中，所述目标参数包括下述至少一项：
    远端终端的业务信息；
    中继终端的能力信息；
    远端终端与中继终端的关联信息。
  9. 根据权利要求1所述的方法，还包括：
    广播所述待使用的中继操作；
    接收支持所述中继操作的终端的响应消息，确定发送所述响应消息的终端为中继终端。
  10. 根据权利要求1所述的方法，还包括：
    接收其他终端广播的第二指示信息，所述第二指示信息用于指示所述其他终端支持的中继操作类型；
    根据所述第二指示信息，选择支持所述待使用的中继操作的终端作为中继终端。
  11. 根据权利要求9或10所述的方法，还包括：
    向网络侧设备发送第一消息，或者，由中继终端向网络侧设备发送第二消息；其中，所述第一消息或所述第二消息中携带所述待使用的中继操作的请求信息；
    接收网络侧设备或中继终端发送的重配置消息；
    根据所述重配置消息建立与请求的中继操作对应的承载。
  12. 根据权利要求11所述的方法，还包括：
    根据建立的承载，进行对应中继操作相关的传输。
  13. 根据权利要求9或10所述的方法，还包括下述至少一个步骤：
    在与中继终端建立无线资源控制RRC连接的过程中，向所述中继终端发送第三PC5 RRC消息，所述第三PC5 RRC消息中显式指示或隐式指示待使用的中继操作，所述第三PC5 RRC消息还携带所述中继操作的承载配置信息；
    在中继终端与其他远端终端建立RRC连接的过程中，由所述中继终端向所述其他远端终端发送第四PC5 RRC消息，所述第四PC5 RRC消息中显式指示或隐式指示待使用的中继操作，所述第四PC5 RRC消息还携带所述中继操作的承载配置信息；
    在与其他远端终端建立RRC连接的过程中，向所述其他远端终端发送第五PC5 RRC消息，所述第五PC5 RRC消息中显式指示或隐式指示待使用的中继操作，所述第五PC5 RRC消息还携带所述中继操作的承载配置信息。
  14. 根据权利要求1所述的方法，其中，所述中继操作包括下述至少一种：
    L2中继操作；
    L3中继操作。
  15. 根据权利要求14所述的方法，其中，所述L3中继操作包括：
    L3中继协议栈，且远端终端的用户面会话由网络侧设备与中继终端的核心网节点建立；
    和/或，
    L3中继协议栈，且远端终端的用户面会话由网络侧设备与远端终端的核心网节点建立。
  16. 一种中继配置方法，应用于网络侧设备，包括：
    发送中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数。
  17. 根据权利要求16所述的方法，还包括：
    通过所述中继操作的配置参数，指示所述网络侧设备支持所述配置参数对应的中继操作类型；
    或者，所述中继配置信息还包括：用于指示网络侧设备支持的中继操作类型的第一指示域。
  18. 根据权利要求16所述的方法，其中，所述中继操作的配置参数包括下述至少一项；
    远端终端允许使用该中继操作的第一条件信息；
    远端终端在使用该中继操作时的承载配置信息；
    远端终端在选择进行数据传输的中继操作时，选择该中继操作的第二条件信息。
  19. 根据权利要求18所述的方法，其中，所述第二条件信息包括下述至少一项：
    业务信息；
    链路信息；
    远端终端和中继终端的关联信息；
    中继操作选择策略。
  20. 根据权利要求19所述的方法，其中，所述业务信息包含下述至少一项：
    业务的服务质量QoS要求；
    业务的时延信息；
    业务的误块率；
    业务的持续时间；
    业务的安全需求；
    业务连续性的需求。
  21. 根据权利要求19所述的方法，其中，所述链路信息包括下述至少一项：
    中继终端的Uu接口的链路条件信息；
    远端终端的Uu接口的链路条件信息；
    远端终端与中继终端之间的PC5接口的链路条件信息。
  22. 根据权利要求16-21中任一项所述的方法，还包括：
    接收远端终端发送的第一消息，或者，接收远端终端选择的中继终端发 送的第二消息，其中，所述第一消息或所述第二消息中携带所述远端终端确定的待使用的中继操作的请求信息；
    向远端终端或中继终端发送重配置消息，所述重配置消息用于指示远端终端建立与请求的中继操作对应的承载。
  23. 根据权利要求16-21中任一项所述的方法，其中，所述中继操作包括下述至少一种：
    L2中继操作；
    L3中继操作。
  24. 根据权利要求23所述的方法，其中，所述L3中继操作包括：
    L3中继协议栈，且远端终端的用户面会话由网络侧设备与中继终端的核心网节点建立；
    和/或，
    L3中继协议栈，且远端终端的用户面会话由网络侧设备与远端终端的核心网节点建立。
  25. 一种中继确定装置，应用于远端终端，包括：
    第一接收模块，用于接收中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数；
    中继确定模块，用于根据所述中继配置信息，确定待使用的中继操作。
  26. 根据权利要求25所述的装置，还包括：
    类型确定模块，用于根据所述中继操作的配置参数，确定网络侧设备支持所述配置参数对应的中继操作类型；
    或者，所述中继配置信息还包括：用于指示网络侧设备支持的中继操作类型的第一指示域。
  27. 根据权利要求25所述的装置，其中，所述中继操作的配置参数包括下述至少一项；
    远端终端允许使用该中继操作的第一条件信息；
    远端终端在使用该中继操作时的承载配置信息；
    远端终端在选择进行数据传输的中继操作时，选择该中继操作的第二条件信息。
  28. 一种中继配置装置，应用于网络侧设备，包括：
    发送模块，用于发送中继配置信息，所述中继配置信息包含至少一种中继操作的配置参数。
  29. 根据权利要求28所述的装置，还包括：
    通过所述中继操作的配置参数，指示所述网络侧设备支持所述配置参数对应的中继操作类型；
    或者，所述中继配置信息还包括：用于指示网络侧设备支持的中继操作类型的第一指示域。
  30. 根据权利要求28所述的装置，其中，所述中继操作的配置参数包括下述至少一项；
    远端终端允许使用该中继操作的第一条件信息；
    远端终端在使用该中继操作时的承载配置信息；
    远端终端在选择进行数据传输的中继操作时，选择该中继操作的第二条件信息。
  31. 一种终端，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至15中任一项所述的中继确定方法的步骤。
  32. 一种网络侧设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求16至24中任一项所述的中继配置方法的步骤。
  33. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1-15中任一项所述的中继确定方法的步骤；或者，所述程序或指令被处理器执行时实现如权利要求16-24中任一项所述的中继配置方法的步骤。
  34. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现如权利要求1-15中任一项所述的中继确定方法，或者实现如权利要求16-24中任一项所述的中继配置方法。
  35. 一种计算机软件产品，所述计算机软件产品被存储在非易失的存储 介质中，所述软件产品被配置成被至少一个处理器执行以实现如权利要求1-15中任一项所述的中继确定方法的步骤，或者实现如权利要求16-24中任一项所述的中继配置方法的步骤。
  36. 一种通信设备，所述通信设备被配置成用于执行如权利要求1-15中任一项所述的中继确定方法，或者执行如权利要求16-24中任一项所述的中继配置方法。
PCT/CN2021/100841 2020-06-22 2021-06-18 中继确定方法、配置方法、装置、终端及网络侧设备 WO2021259157A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2022579025A JP2023530186A (ja) 2020-06-22 2021-06-18 中継決定方法、配置方法、装置、端末及びネットワーク側機器
EP21829298.5A EP4171097A4 (en) 2020-06-22 2021-06-18 RELAY DETERMINATION AND CONFIGURATION METHOD AND APPARATUS, TERMINAL AND NETWORK-SIDE DEVICE
KR1020227042585A KR20230008169A (ko) 2020-06-22 2021-06-18 릴레이 결정 방법, 구성 방법, 장치, 단말 및 네트워크측 장치
US18/086,355 US20230117489A1 (en) 2020-06-22 2022-12-21 Relay determining method and apparatus, relay configuration method and apparatus, terminal, and network side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010576287.8 2020-06-22
CN202010576287.8A CN113905397B (zh) 2020-06-22 2020-06-22 中继确定方法、配置方法、装置、终端及网络侧设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/086,355 Continuation US20230117489A1 (en) 2020-06-22 2022-12-21 Relay determining method and apparatus, relay configuration method and apparatus, terminal, and network side device

Publications (1)

Publication Number Publication Date
WO2021259157A1 true WO2021259157A1 (zh) 2021-12-30

Family

ID=79186657

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/100841 WO2021259157A1 (zh) 2020-06-22 2021-06-18 中继确定方法、配置方法、装置、终端及网络侧设备

Country Status (6)

Country Link
US (1) US20230117489A1 (zh)
EP (1) EP4171097A4 (zh)
JP (1) JP2023530186A (zh)
KR (1) KR20230008169A (zh)
CN (1) CN113905397B (zh)
WO (1) WO2021259157A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023179754A1 (zh) * 2022-03-25 2023-09-28 维沃移动通信有限公司 远端终端的识别符的分配方法、装置及终端
WO2024065137A1 (zh) * 2022-09-26 2024-04-04 Oppo广东移动通信有限公司 配置信息获取方法, 配置信息转发方法以及终端设备

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20220001454A (ko) * 2020-06-29 2022-01-05 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서 사이드링크 데이터 무선 베어러 설정을 위한 위한 방법 및 장치
US20220182130A1 (en) * 2020-12-04 2022-06-09 Qualcomm Incorporated Techniques for using multi-connected repeaters in wireless communications
CN117412409A (zh) * 2022-07-07 2024-01-16 维沃移动通信有限公司 中继控制方法、装置、终端及网络侧设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016163733A1 (en) * 2015-04-06 2016-10-13 Lg Electronics Inc. Method and apparatus for transmitting relay request indication in wireless communication system
CN106162512A (zh) * 2015-04-09 2016-11-23 中兴通讯股份有限公司 一种中继承载控制方法和装置
CN106470491A (zh) * 2015-08-14 2017-03-01 中兴通讯股份有限公司 中继用户设备控制方法、装置及用户设备
CN107637162A (zh) * 2015-05-14 2018-01-26 英特尔Ip公司 Ue到网络中继发起和配置
CN110089086A (zh) * 2016-12-27 2019-08-02 华为技术有限公司 一种中继传输的方法、相关设备及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
MX2017012886A (es) * 2015-04-08 2018-04-30 Interdigital Patent Holdings Inc Realización de repetidores móviles para comunicaciones de dispositivo a dispositivo (d2d).
CN108307472B (zh) * 2016-08-12 2023-06-30 中兴通讯股份有限公司 设备直通系统的通信方法及装置、通信系统
CN108207017B (zh) * 2016-12-20 2019-09-17 电信科学技术研究院 一种处理寻呼的方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016163733A1 (en) * 2015-04-06 2016-10-13 Lg Electronics Inc. Method and apparatus for transmitting relay request indication in wireless communication system
CN106162512A (zh) * 2015-04-09 2016-11-23 中兴通讯股份有限公司 一种中继承载控制方法和装置
CN107637162A (zh) * 2015-05-14 2018-01-26 英特尔Ip公司 Ue到网络中继发起和配置
CN106470491A (zh) * 2015-08-14 2017-03-01 中兴通讯股份有限公司 中继用户设备控制方法、装置及用户设备
CN110089086A (zh) * 2016-12-27 2019-08-02 华为技术有限公司 一种中继传输的方法、相关设备及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ITRI: "Discussion on Relay associated selection procedure for Sidelink UE-to-NW relaying", 3GPP TSG RAN WG1 MEETING #89; R1-1708383, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 14 May 2017 (2017-05-14), Hangzhou; 20170515 - 20170519, XP051273576 *
See also references of EP4171097A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023179754A1 (zh) * 2022-03-25 2023-09-28 维沃移动通信有限公司 远端终端的识别符的分配方法、装置及终端
WO2024065137A1 (zh) * 2022-09-26 2024-04-04 Oppo广东移动通信有限公司 配置信息获取方法, 配置信息转发方法以及终端设备

Also Published As

Publication number Publication date
CN113905397A (zh) 2022-01-07
EP4171097A1 (en) 2023-04-26
JP2023530186A (ja) 2023-07-13
EP4171097A4 (en) 2023-12-20
CN113905397B (zh) 2024-02-27
KR20230008169A (ko) 2023-01-13
US20230117489A1 (en) 2023-04-20

Similar Documents

Publication Publication Date Title
WO2021259157A1 (zh) 中继确定方法、配置方法、装置、终端及网络侧设备
WO2020057328A1 (zh) 一种通信方法和装置
WO2014019510A1 (zh) 用户设备到用户设备的通信方法及设备
WO2022022550A1 (zh) 副链路中继架构中的配置方法和终端
JP7035082B2 (ja) ユーザプレーンリンク確立方法、基地局、およびモビリティ管理デバイス
WO2021218785A1 (zh) 远端ue的传输方法、配置方法、装置及电子设备
WO2015131407A1 (zh) 一种中继节点RN、宿主基站DeNB及一种通信方法
WO2022171017A1 (zh) 一种通信方法、装置及系统
WO2022068714A1 (zh) 传输配置的方法、装置和设备
US20230093763A1 (en) Bearer configuration method and apparatus, and terminal
WO2022194146A1 (zh) 移动接入和回传一体化网络的建立方法、装置及设备
WO2023284682A1 (zh) 中继的识别方法、中继的确定方法、终端及网络侧设备
WO2022057892A1 (zh) 业务数据传输方法及装置、终端和基站
WO2022100667A1 (zh) 基于侧链路中继的切换方法、装置、设备及存储介质
WO2022083545A1 (zh) 中继的配置方法、装置及用户设备
WO2022127681A1 (zh) 旁链路传输的处理方法、装置、终端及网络设备
WO2022007925A1 (zh) 流量控制方法及设备
WO2021078170A1 (zh) 一种通信方法及装置
CN115708369A (zh) 用于传输数据的方法和装置
JP2022540390A (ja) サービスデータ適応プロトコル層エンティティの管理方法、送信端末及び受信端末
WO2022228437A1 (zh) 切换方法、装置、设备及可读存储介质
WO2021220971A1 (ja) 端末及び通信方法
WO2022057916A1 (zh) Sl和wlan互操作方法、装置及通信设备
WO2022017480A1 (zh) 管理目标业务的方法、装置和通信设备
WO2022022402A1 (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: 21829298

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20227042585

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2022579025

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021829298

Country of ref document: EP

Effective date: 20230123