[go: up one dir, main page]

WO2025010660A1 - 一种无线资源管理方法、装置、终端、芯片和存储介质 - Google Patents

一种无线资源管理方法、装置、终端、芯片和存储介质 Download PDF

Info

Publication number
WO2025010660A1
WO2025010660A1 PCT/CN2023/107028 CN2023107028W WO2025010660A1 WO 2025010660 A1 WO2025010660 A1 WO 2025010660A1 CN 2023107028 W CN2023107028 W CN 2023107028W WO 2025010660 A1 WO2025010660 A1 WO 2025010660A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
communication link
terminal device
network
rrc connection
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/CN2023/107028
Other languages
English (en)
French (fr)
Inventor
冷冰雪
卢前溪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2023/107028 priority Critical patent/WO2025010660A1/zh
Publication of WO2025010660A1 publication Critical patent/WO2025010660A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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

Definitions

  • the embodiments of the present application relate to the field of communication technology, and specifically to a wireless resource management method, device, terminal, chip and storage medium.
  • terminal-to-terminal UE to UE, U2U
  • terminal-to-network UE to Network, U2N
  • multi-hop relay is likely to be introduced to further enhance the coverage, that is, there may be multiple relay terminals between the source terminal and the target terminal (or base station).
  • RRM Radio Resource Management
  • Embodiments of the present application provide a wireless resource management method, device, terminal, chip and storage medium.
  • an embodiment of the present application provides a wireless resource management method, which is applied to a first device, wherein the communication link in which the first device is located includes a source terminal device, a target device, and multiple relay terminal devices between the source terminal device and the target device, and the method includes: sending first information to a second device in the communication link through a wireless resource control RRC connection, wherein the first information is related to wireless resource management.
  • an embodiment of the present application provides a wireless resource management device, wherein the communication link in which the device is located includes a source terminal device, a target device, and multiple relay terminal devices between the source terminal device and the target device, and the device includes: a first sending unit, used to send first information to a second device in the communication link through a wireless resource control RRC connection, wherein the first information is related to wireless resource management.
  • an embodiment of the present application provides a terminal, including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned wireless resource management method.
  • an embodiment of the present application provides a chip for implementing the above-mentioned wireless resource management method.
  • the chip includes: a processor for calling and running a computer program from a memory so that a device equipped with the chip executes the above-mentioned wireless resource management method.
  • an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a computer to execute the above-mentioned wireless resource management method.
  • an embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned wireless resource management method.
  • an embodiment of the present application provides a computer program which, when executed on a computer, enables the computer to execute the above-mentioned wireless resource management method.
  • the wireless resource management process in the multi-hop relay scenario is realized, or in other words, the control plane process in the multi-hop relay scenario is realized.
  • FIG1-1 is a schematic diagram of resource selection corresponding to the first mode provided in an embodiment of the present application.
  • FIG1-2 is a schematic diagram of resource selection corresponding to the second mode provided in an embodiment of the present application.
  • FIG2 is a schematic diagram of an example of a relay UE transmitting data between a source UE and a target UE provided in an embodiment of the present application;
  • FIG3 is a schematic diagram of a flow chart of establishing a connection between a source UE and a target UE provided in an embodiment of the present application;
  • FIG4 is a schematic diagram of an example of a U2U relay user plane protocol stack provided in an embodiment of the present application.
  • FIG5 is a flow chart of a wireless resource management method according to an embodiment of the present application.
  • FIG6 is a schematic diagram 1 of a network connection method in a multi-hop scenario provided in an embodiment of the present application
  • FIG7 is a second schematic diagram of a network connection method in a multi-hop scenario provided in an embodiment of the present application.
  • FIG8 is a third schematic diagram of a network connection method in a multi-hop scenario provided in an embodiment of the present application.
  • FIG9 is a fourth schematic diagram of a network connection method in a multi-hop scenario provided in an embodiment of the present application.
  • FIG. 10 is a schematic diagram of the structure of a wireless resource management device provided in an embodiment of the present application.
  • FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • D2D Device to Device
  • V2X Vehicle to Everything
  • Device-to-device communication is a sidelink (SL) transmission technology based on D2D.
  • SL sidelink
  • D2D Downlink
  • the Internet of Vehicles system uses terminal-to-terminal direct communication, so it has higher spectrum efficiency and lower transmission latency.
  • Two transmission modes are defined in the 3rd Generation Partnership Project (3GPP): the first mode (mode 3) and the second mode (mode 4).
  • Mode 1 The transmission resources of the terminal are allocated by the base station (eNB), and the terminal transmits data on the sidelink according to the resources allocated by the base station.
  • the base station can allocate resources for a single transmission to the terminal, or it can allocate resources for a semi-static transmission to the terminal.
  • the transmission resources of the terminal are allocated by the base station, and the base station allocates resources to the terminal based on the grant signaling (Grant) through the downlink, and the terminal transmits data on the sidelink according to the resources allocated by the base station.
  • Grant grant signaling
  • Second mode The terminal selects a resource in the resource pool for data transmission. As shown in Figure 1-2, the terminal selects a resource in the resource pool for data transmission.
  • D2D is divided into the following different stages for research:
  • Proximity based Service In Rel-12/13, device-to-device communication was studied for ProSe scenarios, which mainly targets public safety services.
  • the UE can transmit/receive data non-continuously on the sidelink, thereby achieving power saving.
  • V2X In Rel-14/15, the vehicle networking system studied the scenario of vehicle-to-vehicle communication, which is mainly aimed at the business of relatively high-speed vehicle-to-vehicle and vehicle-to-person communication;
  • V2X since the on-board system has a continuous power supply, power efficiency is not the main issue, but the delay of data transmission is the main issue, so the system design requires the terminal equipment to perform continuous transmission and reception.
  • 3GPP concluded that a base station can configure the discontinuous reception (DRX) parameters of a remote terminal through a relay terminal, but did not provide a conclusion on the specific details of how to configure DRX.
  • DRX discontinuous reception
  • NR V2X is not limited to broadcast scenarios, but is further expanded to unicast and multicast scenarios, and the application of V2X is studied in these scenarios.
  • NR V2X Similar to LTE V2X, NR V2X also defines two resource authorization modes: mode-1/2 (i.e. the first mode and the second mode mentioned above). Different from LTE V2X, in addition to the non-feedback, UE-initiated HARQ retransmission, NR V2X introduces feedback-based HARQ retransmission, which is not limited to unicast communication, but also includes multicast communication.
  • mode-1/2 i.e. the first mode and the second mode mentioned above.
  • NR V2X introduces feedback-based HARQ retransmission, which is not limited to unicast communication, but also includes multicast communication.
  • 3GPP studied the U2U relay function based on layer 2 and 3 relays, that is, the source UE is connected to the target UE through the relay UE, and the relay UE transfers data between the source UE and the target UE, as shown in Figure 2.
  • connection establishment steps between the source UE and the target UE are shown in Figure 3.
  • the source UE, the relay UE, and the target UE discover each other through a discovery message or a direct communication request (DCR) message.
  • the relay UE can help the source UE forward the discovery message or DCR message.
  • Relay selection can be performed, and appropriate relays are selected to establish connections with them respectively, and then the relays establish end-to-end PC5 connections.
  • establishing PC5 connections can also be understood as establishing connections through direct communication interfaces.
  • connection establishment step between the source UE and the target UE may include:
  • the U2U relay performs relay function registration and relay function parameter configuration.
  • the U2U relay may register with the core network as a relay UE with a relay function, and configure parameters related to the relay function.
  • S302 The source UE and the target UE discover each other.
  • S303 The source UE and the target UE perform relay selection.
  • S304 The source UE and the target UE establish a per hop connection with the U2U relay respectively.
  • the source UE and the target UE establish an end-to-end connection through the U2U relay.
  • FIG 4 is a schematic diagram of an example of the U2U relay user plane protocol stack.
  • 3GPP Rel-17 introduced layer 2 U2U relay.
  • the adaptation layer (ADAPT) is placed above the control plane and user plane radio link control (RLC) sublayer between the relay UE and the source/target UE.
  • the PC5 Service Data Adaptation Protocol (SDAP)/Packet Data Convergence Protocol (PDCP) and Radio Resource Control (RRC) terminate between the source UE and the target UE, while the RLC, Media Access Control (MAC) and Physical Layer (PHY) terminate in each link (i.e., the link between the source UE and the relay UE and the link between the relay UE and the target UE).
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • RRC Radio Resource Control
  • MAC Media Access Control
  • PHY Physical Layer
  • the adaptation layer of the relay UE supports the mapping of sidelink bearers between access PC5RLC channels.
  • different end-to-end bearers such as signaling radio bearers (SRB) and data radio bearers (DRB)
  • SRB signaling radio bearers
  • DRB data radio bearers
  • the Adaptation Layer is used to support UE identification for side traffic (multiplexing data from multiple UEs).
  • the identification information of the UE PC5 radio bearer and the UE is included in the Adaptation Layer so that the target UE can associate the received data packets of a specific PDCP entity associated with the radio bearer of the source UE.
  • the remote UE performs measurement reporting, and includes information such as the relay UE identifier, serving cell identifier, and reference signal receiving power (RSRP) measurement in the measurement reporting information.
  • RSRP reference signal receiving power
  • the remote UE performs a link switch from a non-direct path to a direct path, it is more recommended for the serving relay UE to use SL-RSRP for sidelink measurements; when the remote UE performs a link switch from a direct path to a non-direct path, SD-RSRP is used for sidelink measurements.
  • two new measurement reporting triggering events are defined for U2N relay switching.
  • Event 1 When the link quality of the serving relay UE is lower than the configured threshold value, and (optionally) the link quality of the adjacent cell is higher than the configured threshold value, the remote UE performs measurement reporting;
  • Event 2 When the link quality of the serving cell is lower than the configured threshold value, and the link quality of the optional relay UE is higher than the configured threshold value, the remote UE performs measurement reporting.
  • a new timer is introduced. When the remote UE receives the RRC reconfiguration message indicating the direct link to non-direct link handover, the remote UE starts the timer. When the timer times out, the remote UE performs RRC reestablishment.
  • A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.
  • the "correspondence" mentioned in the embodiments of the present application can mean that there is a direct or indirect correspondence relationship between the two, or it can mean that there is an association relationship between the two, or it can mean that there is an indication and being indicated, configuration and being configured, etc.
  • predefined or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including terminal devices and network devices), and the present application does not limit its specific implementation method.
  • the terminal device in the embodiments of the present application may refer to an access terminal, a user equipment (UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Processing (PDP) station, or a wireless communication device.
  • PDA Personal Digital Processing
  • handheld devices with wireless communication function computing devices or other processing devices connected to a wireless modem, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or terminal devices in future evolution networks, etc.
  • the network device in the embodiments of the present application may be an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.
  • Evolutional Node B, eNB or eNodeB in an LTE system
  • NG RAN Next Generation Radio Access Network
  • gNB base station
  • CRAN Cloud Radio Access Network
  • PLMN Public Land Mobile Network
  • the research on U2U/U2N relay is mainly aimed at single-hop scenarios, that is, there is only one relay terminal between the source terminal and the target terminal (or base station).
  • multi-hop relays will be introduced to further enhance the coverage, that is, there may be multiple relay terminals between the source terminal and the target terminal (or base station).
  • the PC5RRM process between multi-hop relays will be affected.
  • there is currently no solution to reveal how to implement the RRM process, or how to perform the control plane process, in a scenario where there are multiple relay terminals between the source terminal and the target terminal (or base station) that is, in a multi-hop U2U/U2N relay scenario).
  • the present application provides a wireless resource management method, apparatus, terminal, chip and storage medium.
  • the method can be applied to multi-hop U2U/U2N relay scenarios.
  • the first device in the communication link can send information related to wireless resource management to the second device through an RRC connection, thereby implementing the wireless resource management process in the multi-hop relay scenario, or in other words, implementing the control plane process in the multi-hop relay scenario.
  • FIG5 is a flow chart of a wireless resource management method provided in an embodiment of the present application.
  • the method can be applied to a first device, wherein the communication link in which the first device is located includes a source terminal device, a target device, and multiple relay terminal devices between the source terminal device and the target device.
  • the target device in the embodiment of the present application can be a network device or a terminal device.
  • the target device in the embodiment of the present application can be a network device, or it can also be a terminal device.
  • the wireless resource management method may include the following steps:
  • the first information is related to wireless resource management, and it can also be understood that the first information is related to control plane information, or it can also be understood that the first information is control plane information.
  • the second device in the embodiment of the present application may be adjacent to the first device in the communication link, or may not be adjacent to each other.
  • the second device is adjacent to the first device in the communication link, which may also be understood as that there is no relay terminal device between the second device and the first device in the communication link, or it may also be understood as that the second device is directly connected to the first device.
  • the second device is not adjacent to the first device in the communication link, which may also be understood as that there is at least one relay terminal device between the second device and the first device in the communication link, or it may also be understood as that the second device is not directly connected to the first device. It is understandable that when the second device is not adjacent to the first device, the first information is information transmitted across hops.
  • scenario 1 the scenario in which the second device and the first device are not adjacent in the communication link is recorded as scenario 1
  • scenario 2 the scenario in which the second device and the first device are adjacent in the communication link is recorded as scenario 2.
  • Scenario 1 and scenario 2 are introduced below respectively.
  • Scenario 1 The second device and the first device are not adjacent in the communication link.
  • the first device is a terminal device that does not meet the first condition in the communication link
  • the second device is a terminal device that meets the first condition in the communication link
  • the target device is a network device
  • the first information is used to request a paging message for the first device and/or system information required by the first device.
  • the system information may be, for example, a system information block (SIB).
  • the first information may include: information required for monitoring the paging message of the first device; in the case where the first information is used to request system information required by the first device, the first information includes: the type of system information required by the first device. That is, if the first device requests a paging message for the first device from the second device, the first device may carry the information required for monitoring the paging message in the first information, such as the identification (ID) of the first device, the monitoring period, etc. If the first device requests the system information required by the first device from the second device, the first device may carry the type of system information required by the first device in the first information.
  • ID identification
  • the first condition may include at least one of the following: being within the signal coverage of the network device; being the device closest to the network device in the communication link; and being able to directly obtain paging messages and/or system information from the network device.
  • failure to meet the first condition can also be understood as being outside the signal coverage range of the network device.
  • the first condition is: the device closest to the network device in the communication link
  • the terminal device closest to the network device in the communication link For example, it may be the last-hop terminal device in the uplink direction, or it may be a terminal device directly connected to the network device.
  • the first condition is: being able to directly obtain paging messages and/or system information from the network device
  • not meeting the first condition can also be understood as being unable to directly obtain paging messages and/or system information from the network device.
  • the terminal device that can directly obtain paging messages and/or system information from the network device can be, for example, a terminal device directly connected to the network device.
  • the first condition includes multiple conditions, then, in one possible way, when any one or more of the conditions are not met, it can be considered that the first condition is not met; in another possible way, when all of the conditions are not met, it can be considered that the first condition is not met.
  • the first condition includes: being located within the signal coverage range of the network device and being the device closest to the network device in the communication link, then, in one possible way, if a certain terminal device is located outside the signal coverage range of the network device and/or is not the device closest to the network device in the communication link, it can be considered that the terminal device does not meet the first condition; in another possible way, if a certain terminal device is located outside the signal coverage range of the network device and is not the device closest to the network device in the communication link, it can be considered that the terminal device does not meet the first condition.
  • a first device that does not meet the first condition may send a first message to a second device that is not adjacent and meets the first condition through an RRC connection to request a paging message for the first device and/or system information required by the first device. Since a terminal device that meets the first condition generally has the ability to obtain a paging message and/or system information from a network device, the terminal device that meets the first condition may obtain the information requested by the first device (such as a paging message for the first device and/or system information required by the first device) from the network device based on the first information, and forward the obtained information to the first device.
  • the information requested by the first device such as a paging message for the first device and/or system information required by the first device
  • the first device may request paging messages for the first device and/or system information required by the first device from multiple second devices.
  • the first device is a terminal device that satisfies a first condition in a communication link
  • the second device is a terminal device that does not satisfy the first condition in the communication link
  • the target device is a network device
  • the first information includes: a paging message for the second device, and/or system information required by the second device.
  • the first condition may include at least one of the following: being within the signal coverage of the network device; being the device closest to the network device in the communication link; and being able to directly obtain paging messages and/or system information from the network device.
  • a first device that meets the first condition can send first information to a second device that is not adjacent and does not meet the first condition through an RRC connection to convey a paging message for the second device and/or system information required by the second device to the second device.
  • the first device may convey a paging message for each second device and/or system information required by each second device to the multiple second devices.
  • the method may also include: the first device receives second information from the second device, the second information is used to request a paging message for the second device, and/or system information required by the second device.
  • the second information may include: information required for monitoring the paging message of the second device; in the case where the second information is used to request system information required by the second device, the second information may include: the type of system information required by the second device. That is, if the second device requests a paging message for the second device from the first device, the second device may carry the information required for monitoring the paging message in the second information, such as the identifier of the second device, the monitoring period, etc. If the second device requests the system information required by the second device from the first device, the second device may carry the type of system information required by the second device in the second information.
  • the first information may include: a paging message for the second device; in the case where the second information includes the type of system information required by the second device, the first information includes: system information required by the second device. That is, if the second device carries the information required for monitoring the paging message for the second device in the second information, it means that the second device requests the paging message for the second device from the first device, so the first device can carry the paging message for the second device in the first information and send it to the second device.
  • the second device If the second device carries the type of system information required by the second device in the first information, it means that the second device requests the system information required by the second device from the first device, so the first device can carry the system information required by the second device in the first information and send it to the second device.
  • the method may also include: obtaining a paging message for the second device from a network device based on information required to monitor the paging message of the second device; and/or, based on the type of system information required by the second device, obtaining system information required by the second device from the network device.
  • the first device can obtain the paging message for the second device from the network device based on the information required for monitoring the paging message of the second device, and then carry the obtained paging message in the first information and forward it to the second device.
  • the second device carries the type of system information required by the second device in the second information
  • the first device can obtain the system information required by the second device from the network device based on the type of system information required by the second device, and then carry the obtained system information in the first information and forward it to the second device.
  • the first device and the second device are different terminal devices in the communication link, and the first information is used to indicate the wireless link status of the first device, or to indicate a change in the network connection status or the wireless link status of the first device.
  • the radio link status may include: radio link failure (RLF);
  • the network connection status change may include: cell switching, cell reselection or RRC connection status change;
  • the radio link status change may include: the link quality of the radio link is reduced.
  • a first device can send first information to a non-adjacent second device via an RRC connection, thereby indicating the wireless link status of the first device to the second device, or indicating that a network connection status change or a wireless link status change has occurred in the first device.
  • the number of second devices may be multiple, that is, the first device may indicate the wireless link status of the first device to multiple second devices, or indicate to multiple second devices that the network connection status or wireless link status of the first device has changed.
  • the first device and the second device are different terminal devices in a communication link, and the first information is used to instruct the second device to measure surrounding wireless communication conditions.
  • the first information may, for example, instruct the second device to measure a channel busy ratio (CBR) and/or a link quality between the second device and at least one third device.
  • the third device may, for example, be another terminal device, or may also be a network device.
  • the link quality may, for example, include RSRP.
  • the first device may instruct the second device to measure and report the CBR measurement situation through the first information.
  • the first device may also instruct the second device through the first information to measure and report the link quality between the second device and other terminal devices, such as the Sidelink-Reference Signal Received Power (SL-RSRP) or the Sidelink Discovery-Reference Signal Received Power (Sidelink Discovery-RSRP, SD-RSRP) between the second device and the other terminal devices.
  • SL-RSRP Sidelink-Reference Signal Received Power
  • Sidelink Discovery-RSRP Sidelink Discovery-RSRP
  • SD-RSRP Sidelink Discovery-RSRP
  • the first device may also instruct the second device to measure and report the link quality between the second device and the network device, such as Uu-RSRP between the second device and the network device, through the first information.
  • the first device may send the first information to the non-adjacent second device through the RRC connection to instruct the second device to measure the wireless communication conditions around it.
  • the second device may feed back the corresponding measurement result to the first device, so that the first device can know the link status of the second device that is not directly connected to the communication link.
  • the measurement result can be used to assist the first device in making the next decision. For example, when the measurement result shows that the link quality between the second device and a terminal device is poor, the first device may instruct the second device to connect to other candidate terminal devices.
  • the first device may instruct multiple second devices to measure surrounding wireless communication conditions.
  • the first device and the second device are different terminal devices in a communication link
  • the first information is used to indicate the quality of service QoS between the second device and a fourth device, wherein the second device and the fourth device are adjacent to each other in the communication link.
  • the first device can configure the QoS between the second device and the adjacent device for the second device through the first information, or the first device can configure the QoS on a certain hop where the non-adjacent terminal device (such as the second device) is located through the cross-hop RRC connection.
  • relay terminal device #1 an example of the first device
  • relay terminal device #3 can configure the QoS on the third hop and/or the fourth hop for relay terminal device #3 through the cross-hop PC5-RRC connection between the relay terminal device #1 and the relay terminal device #3 (an example of the second device).
  • the number of second devices can be multiple, that is, the first device can configure QoS for multiple non-adjacent second devices through an RRC connection.
  • the first device when there is an RRC connection between the first device and all terminal devices in the communication link, the first device can also configure QoS for all terminal devices in the communication link through an RRC connection, or in other words, the first device can configure single-hop QoS on each hop and send the configured QoS to the corresponding terminal device through the RRC connection. In this way, the first device can coordinate the QoS allocation on the entire communication link through a centralized QoS allocation method, which is beneficial to improving the communication performance of the entire communication link.
  • the first device may be any of the following devices: a source terminal device; a target device; a device that is closest to the source terminal device in the communication link; a device that is closest to the target device in the communication link; a device determined based on a preset rule.
  • the preset rule may be specified by a protocol, for example. For example, it may be specified that the terminal device with the strongest capability in the communication link is determined as the first device; for another example, it may be specified that the terminal device in the communication link that is in a connected state or within the network coverage is determined as the first device.
  • the first device may also be referred to as a central terminal device, or a control terminal device.
  • the first device can configure QoS on a certain hop where the terminal device is located for a non-adjacent terminal device through a cross-hop RRC connection, thereby simplifying the QoS allocation method and improving the efficiency of QoS allocation.
  • the first device and the second device are different terminal devices in a communication link, and the first information is used to configure transmission resources of the second device.
  • the first device may configure transmission resources for the second device through the first information.
  • the first device may configure transmission resources for a non-adjacent terminal device (such as the second device) through a cross-hop RRC connection.
  • the number of the second devices may be multiple, that is, the first device may configure transmission resources for multiple non-adjacent second devices through an RRC connection.
  • the first device can also configure transmission resources for all terminal devices in the communication link through RRC connection. In this way, the purpose of reducing delay can be achieved through centralized resource allocation.
  • the transmission resource allocated by the first device to the second device may be selected by the first device from a resource pool.
  • the transmission resource allocated by the first device to the second device may also be allocated by the target device, and then the first device sends the transmission resource allocated by the target device to the second device to the second device.
  • the target device is a network device.
  • the first device that allocates transmission resources to the second device may be, for example, any of the following devices: a source terminal device; a target device; a device that is closest to the source terminal device in the communication link; a device that is closest to the target device in the communication link; a device determined based on a preset rule.
  • the preset rule may be specified by a protocol, for example. For example, it may be specified that the terminal device with the strongest capability in the communication link is determined as the first device; for another example, it may be specified that the terminal device in the communication link that is in a connected state or within the network coverage is determined as the first device.
  • the first device may also be referred to as a central terminal device, or a control terminal device.
  • the first device can configure transmission resources for non-adjacent terminal devices through a cross-hop RRC connection, thereby simplifying the resource allocation method and improving the efficiency of resource allocation.
  • the first device and the second device are different terminal devices in the communication link
  • the first information is an RRC reconfiguration message, which may include at least one of the following: Sidelink Relay Adaptation Protocol (SRAP) configuration, RLC configuration, and MAC configuration.
  • SRAP Sidelink Relay Adaptation Protocol
  • the SRAP configuration includes: an identifier assigned to the second device and/or identifiers of other terminal devices in the communication link.
  • the RRC reconfiguration message may be carried in the cross-hop message (first information).
  • the number of the second devices may be multiple, that is, the first device may send the RRC reconfiguration message to multiple non-adjacent second devices through the RRC connection.
  • the first device and the second device are different terminal devices in the communication link, and RLF occurs between the first device and the second device when a second condition is met.
  • the second condition includes: RLF occurs between any two adjacent devices between the first device and the second device; and/or RLF occurs between any two adjacent devices in the communication link.
  • the reason why the cross-hop RRC connection has an RLF may include at least one of the following:
  • RLF occurs between the first device and the second device, or between any two adjacent devices.
  • RLF occurs between any two adjacent devices in the communication link. That is, RLF occurs between any two adjacent devices in the communication link, which will cause RLF to occur between the first device and the second device.
  • the first device and the second device are different terminal devices in the communication link, and there is an RRC connection between the first device and the second device, and the RRC connection between the first device and the second device is released when the third condition is met.
  • the third condition includes: the RRC connection between the first device and the second device, any two adjacent devices are released; and/or, the RRC connection between any two adjacent devices in the communication link is released.
  • the reason for releasing the cross-hop RRC connection may include at least one of the following:
  • the RRC connection between the first device and the relay terminal device is released, and/or the RRC connection between the second device and the relay terminal device is released, the RRC connection between the first device and the second device will be released.
  • the RRC connection between any two adjacent devices in the communication link is released. That is, the RRC connection between any two adjacent devices in the communication link is released, which will result in the RRC connection between the first device and the second device being released.
  • the second device is a target device, and the target device is a network device, and the first information is used to indicate at least one of the following: a wireless link failure of the first device; the channel quality (such as RSRP) between the first device and at least one fifth device; and the identification of all terminal devices in the communication link.
  • a wireless link failure of the first device such as RSRP
  • the channel quality such as RSRP
  • the first device may report the first information to the network device through the cross-hop RRC connection.
  • the first device may be, for example, a source terminal device, or may also be a relay terminal device.
  • the second device is a target device, and the target device is a network device, and the transmission resources of the first device are configured for the first device by the network device through an RRC connection.
  • the network device can allocate transmission resources to the first device through the cross-hop RRC connection.
  • the first device can be, for example, a source terminal device, or can also be a relay terminal device.
  • the network device when there is an RRC connection between the network device and each terminal device in the communication link, the network device can configure transmission resources for each terminal device in the communication link (including directly connected and not directly connected terminal devices) through the RRC connection.
  • the method may further include: the first device sends a third Information, the third information is related to wireless resource management; wherein the sixth device is adjacent to the first device in the communication link.
  • the first device in addition to sending first information related to wireless resource management to a non-adjacent second device in the communication link through an RRC connection, can also send third information related to wireless resource management to an adjacent sixth device in the communication link through an RRC connection.
  • Scenario 2 The second device is adjacent to the first device in the communication link.
  • the first device is a terminal device that does not meet the first condition in the communication link
  • the target device is a network device
  • the second device is the next-hop terminal device of the first device in the uplink direction
  • the first information is used to request a paging message for the first device, and/or system information required by the first device.
  • the first information may include: information required for monitoring the paging message of the first device; in the case where the first information is used to request system information required by the first device, the first information may include: the type of system information required by the first device. That is, if the first device requests a paging message for the first device, the first device may carry the information required for monitoring the paging message in the first information, such as the identification (ID) of the first device, the monitoring period, etc. If the first device requests the system information required by the first device, the first device may carry the type of system information required by the first device in the first information.
  • ID identification
  • the first condition may include at least one of the following: being within the signal coverage of the network device; being the device closest to the network device in the communication link; and being able to directly obtain paging messages and/or system information from the network device.
  • a first device that does not meet the first condition may send a first message to an adjacent second device through an RRC connection to request a paging message for the first device, and/or system information required by the first device.
  • the second device is a terminal device (relay terminal device) that does not meet the first condition.
  • the second device may continue to forward the first information to the next-hop device, that is, forward it to the next-hop terminal device of the second device in the uplink direction until the first information is forwarded to the terminal device that meets the first condition.
  • the second device is a terminal device that meets the first condition. In this case, the second device may stop forwarding the first information to the next-hop device.
  • the first device is a terminal device that does not meet the first condition in the communication link
  • the target device is a network device
  • the second device is the next-hop terminal device of the first device in the uplink direction
  • the first information is used to request a paging message for a seventh device, and/or system information required by the seventh device
  • the seventh device in the communication link is the previous-hop terminal device of the first device in the uplink direction, the source terminal device, or any device between the first device and the source terminal device that has an RRC connection with the first device.
  • the seventh device may send the first information to the first device. If the first device does not meet the first condition, the first device may forward the first information from the seventh device to the next-hop terminal device (i.e., the second device) in the uplink direction. In one possible scenario, the second device still does not meet the first condition, then the second device may continue to forward the first information to the next-hop device, that is, forward it to the next-hop terminal device of the second device in the uplink direction, until the first information is forwarded to the terminal device that meets the first condition. In another possible scenario, the second device meets the first condition, then the second device may stop forwarding the first information to the next-hop device.
  • the next-hop terminal device i.e., the second device
  • the first information when the first information is used to request a paging message for a seventh device, the first information may include: information required for monitoring the paging message of the seventh device; when the first information is used to request system information required by the seventh device, the first information may include: the type of system information required by the seventh device.
  • the first condition may include at least one of the following: being within the signal coverage of the network device; being the device closest to the network device in the communication link; and being able to directly obtain paging messages and/or system information from the network device.
  • the method may further include: the first device receives the first information from the seventh device through the RRC connection.
  • the method may also include: the first device adds the second information to the first information, and the second information is used to request a paging message for the first device, and/or the system information required by the first device. That is to say, before the first device forwards the first information from the seventh device to the second device, it may also add the second information to the first information.
  • the first information sent by the first device to the second device may include information for requesting a paging message for the seventh device and/or the system information required by the seventh device (the content of the original first information), and information for requesting a paging message for the first device and/or the system information required by the first device (the content of the newly added second information).
  • the second information when the second information is used to request a paging message for the first device, the second information may include: information required for monitoring the paging message of the first device; when the second information is used to request system information required by the first device, the second information may include: the type of system information required by the first device.
  • the target device is a network device
  • the second device is a next-hop terminal device of the first device in the downlink direction, or is any terminal device between the first device and the source terminal device that has an RRC connection with the first device.
  • the first information includes: a paging message for the eighth device, and/or system information required by the eighth device.
  • the eighth device is the second device. That is, the eighth device is the next hop terminal device of the first device in the downlink direction, and the first device can send a paging message for the eighth device and/or system information required by the eighth device to the eighth device through an RRC connection.
  • the eighth device is a source terminal device, or any terminal device between the second device and the source terminal device. That is, the first device can send a paging message for the eighth device and/or the system information required by the eighth device to the second device through an RRC connection. In some embodiments, after the second device receives the paging message for the eighth device and/or the system information required by the eighth device, it can forward the information to the eighth device. For example, in the case where there is an RRC connection between the second device and the eighth device, the second device can forward the information to the eighth device through an RRC connection. For another example, the second device can also forward the information hop by hop to the eighth device in a hop-by-hop forwarding manner.
  • the paging message for the eighth device and/or the system information required by the eighth device may be carried in the same information as "the paging message for the second device and/or the system information required by the second device".
  • the second device after receiving the information, the second device can first remove the paging message for the second device and/or the system information required by the second device contained in the information, and then send the information to the eighth device.
  • the first information may be obtained by the first device from the network device.
  • the first condition may include at least one of the following: being within the signal coverage of the network device; being the device closest to the network device in the communication link; being able to directly obtain paging messages and/or system information from the network device. Since the terminal device that meets the first condition usually has the ability to directly obtain paging messages and/or system information from the network device, the first device can obtain the information requested by the eighth device (such as a paging message for the eighth device, and/or the system information required by the eighth device) from the network device, and send the obtained information to the second device, which is then forwarded by the second device to the eighth device.
  • the eighth device such as a paging message for the eighth device, and/or the system information required by the eighth device
  • the first information may be obtained by the first device from the ninth device in the communication link.
  • the ninth device may be, for example, the previous hop terminal device of the first device in the downlink direction, or may be any terminal device between the first device and the network device that has an RRC connection with the first device. Since the terminal device that does not meet the first condition usually does not have the ability to directly obtain paging messages and/or system information from the network device, the first device needs to obtain the information requested by the eighth device through the ninth device.
  • the information requested by the eighth device may be, for example, directly obtained by the ninth device from the network device (if the ninth device meets the first condition), or may be transmitted hop by hop from the terminal device that meets the first condition to the ninth device.
  • the method may further include: the first device receives fourth information from the eighth device through the second device, the fourth information being used to request a paging message for the eighth device and/or system information required by the eighth device.
  • the fourth information may include: information required for monitoring the paging message of the eighth device; in the case where the fourth information is used to request the system information required by the eighth device, the fourth information may include: the type of system information required by the eighth device.
  • the request information i.e., the fourth information
  • the first information may include: a paging message for the eighth device; in the case where the fourth information includes the type of system information required by the eighth device, the first information may include: system information required by the eighth device. That is to say, if the fourth information carries the information required for monitoring the paging message for the eighth device, it means that the eighth device requests the paging message for the eighth device, and therefore the paging message for the eighth device can be carried in the first information and sent to the eighth device. If the fourth information carries the type of system information required by the eighth device, it means that the eighth device requests the system information required by the eighth device, and therefore the system information required by the eighth device can be carried in the first information and sent to the eighth device.
  • the first information is used to indicate a wireless link status of the first device, or to indicate a network connection status change or a wireless link status change of the first device.
  • the radio link status may include: RLF;
  • the network connection status change may include: cell switching, cell reselection or RRC connection status change;
  • the radio link status change may include: the link quality of the radio link decreases.
  • the first device can send first information to an adjacent second device via an RRC connection, thereby indicating the wireless link status of the first device to the second device, or indicating that the network connection status or wireless link status of the first device has changed.
  • the second device may further forward the first information to a next-hop device to notify the next-hop device of the wireless link status of the first device, or notify the first device of a change in network connection status or wireless link status.
  • the second device is a next-hop terminal device of the first device
  • the first information is used to indicate the wireless link status of the tenth device, or to indicate that a network connection status change or a wireless link status change has occurred in the tenth device; wherein the tenth device is the previous-hop terminal device of the first device, or is a terminal device that is not adjacent to the first device in the communication link.
  • the first device may obtain the first information from the tenth device, and may forward the first information to the next-hop terminal device (the second terminal device). That is, the first device may forward the first information from the tenth device.
  • the first information from the tenth device may be, for example, obtained by the first device from the tenth device via an RRC connection.
  • the tenth device may also forward the first information to the first device hop by hop by hop, that is, the first information may be obtained by the first device from the previous hop terminal device.
  • the method may further include: the first device adds fifth information to the first information, the fifth information being used to indicate the radio link status of the first device, Alternatively, it is used to indicate that a network connection state or a wireless link state of the first device has changed. That is, before the first device forwards the first information from the tenth device to the second device, it may also add the fifth information to the first information.
  • the first information sent by the first device to the second device may include both the content of the original first information and the content of the newly added fifth information.
  • the original first information is used to indicate the wireless link state of the tenth device, or to indicate that a network connection state or a wireless link state of the tenth device has changed; the newly added fifth information is used to indicate the wireless link state of the first device, or to indicate that a network connection state or a wireless link state of the first device has changed.
  • the fifth information may include at least one of the following information: an identification of the first device; an identification of the number of transmission hops associated with the wireless link state of the first device; and an identification of the number of transmission hops associated with a change in the network connection state or the wireless link state of the first device.
  • the identifier of the number of transmission hops associated with the radio link state of the first device is the identifier of the hop.
  • the network connection state change includes an RRC connection state change
  • the identifier of the number of transmission hops associated with the network connection state change of the first device is the identifier of the hop.
  • the first information may also include at least one of the following: an identifier of the tenth device; an identifier of the number of transmission hops associated with the wireless link state of the tenth device; and an identifier of the number of transmission hops associated with a change in the network connection state or the wireless link state of the tenth device.
  • the first information may be used to indicate at least one of the following: the QoS between the first device and the second device; the QoS that can be allocated by the second device; and the number of transmission hops of the communication link.
  • the QoS that can be allocated by the second device may also be understood as the remaining unallocated QoS in the communication link in addition to the allocated QoS. It is understood that the total QoS that can be allocated in the communication link is the end-to-end QoS between the source terminal device and the target device.
  • the method may further include: determining (allocating) QoS between the first device and the second device.
  • the source terminal device can allocate the QoS on the first hop (that is, the QoS between the first device and the second device), and can send the QoS on the first hop and the remaining unallocated QoS in the communication link (that is, the QoS that can be allocated by the second device) to the relay terminal device #1, so that the relay terminal device #1 can allocate the QoS on the second hop from the remaining unallocated QoS, and send the QoS on the second hop and the remaining unallocated QoS to the relay terminal device #2, and so on.
  • the QoS on the first hop that is, the QoS between the first device and the second device
  • the remaining unallocated QoS in the communication link that is, the QoS that can be allocated by the second device
  • the first information may also include one or more of the following information as reference information for the second device when allocating QoS: the number of transmission hops of the communication link, the number of transmission hops where the second device is located, and the number of remaining transmission hops not allocated QoS.
  • the second device is a next-hop terminal device of the first device
  • the first information is an RRC reconfiguration message between the first device and the second device.
  • the RRC reconfiguration message may include at least one of the following: SRAP configuration; RLC configuration; and MAC configuration.
  • the first information may be determined by the first device; or, the first information may be determined by the first device based on the RRC reconfiguration message between the first hop terminal device and the last hop terminal device. That is, the RRC configuration between a certain terminal device and the next hop terminal device may be determined by the current hop terminal device, or by the current hop terminal device based on the RRC configuration between the current hop terminal device and the last hop terminal device, that is, the current hop terminal device needs to decode the RRC reconfiguration message sent to it by the last hop terminal device, and determine the RRC configuration between itself and the next hop terminal device based on the RRC reconfiguration message.
  • the second device is a target device, and the target device is a network device
  • the first information is used to indicate at least one of the following: a wireless link failure of the eleventh device; a channel quality between the eleventh device and at least one twelfth device; an identifier of the eleventh device; and a number of transmission hops between the eleventh device and the network device.
  • the eleventh device is a terminal device in the communication link that does not have an RRC connection with the network device.
  • a terminal device in a connected state can report relevant information of a terminal device in a non-connected state (such as the eleventh device) to a network device through an RRC connection, so that the network device can obtain relevant information about the terminal device in the non-connected state.
  • the method may further include: the first device sends sixth information to a thirteenth device in the communication link through an RRC connection, the sixth information being related to wireless resource management; wherein the thirteenth device and the first device are not adjacent to each other in the communication link.
  • the first device in addition to sending first information related to wireless resource management to an adjacent second device in the communication link through an RRC connection, can also send sixth information related to wireless resource management to a non-adjacent thirteenth device in the communication link through an RRC connection.
  • RRC connection between all adjacent devices in the communication link; there is an RRC connection between some or all of the non-adjacent devices in the communication link; when the target device is a network device, there is an RRC connection between some or all of the terminal devices in the communication link and the network device; when the target device is a network device, there is an RRC connection between the terminal device closest to the network device in the communication link and all or some of the other devices; there is an RRC connection between some or all of the devices in the communication link and the fourteenth device.
  • the fourteenth device may be, for example, any of the following devices: a source terminal device; a target device; a device that is closest to the source terminal device in the communication link; a device that is closest to the target device in the communication link; or a device determined based on a preset rule.
  • the preset rule may be specified by a protocol, for example. For example, it may be specified that the terminal device with the strongest capability in the communication link is determined as the fourteenth device; for another example, it may be specified that the terminal device in the communication link that is in a connected state or within the network coverage is determined as the fourteenth device.
  • the fourteenth device may also be referred to as a central terminal device, or a control terminal device.
  • whether the first device establishes an RRC connection with other devices may be determined by the first device or the network device. That is, the first device may choose to establish an RRC connection with other devices or not based on the first device's own implementation or based on the network configuration.
  • the first information can be identified by one or more of the following, for example: RLC channel; bearer ID; logical channel (Logical Channel, LCH). That is, the terminal device (such as the second device) can identify the first information by one or more of the RLC channel, bearer ID, and LCH.
  • RLC channel RLC channel
  • bearer ID logical channel
  • LCH Logical Channel
  • the first device in the communication link can send information related to wireless resource management to the second device through the RRC connection, thereby realizing the wireless resource management process in the multi-hop relay scenario, or in other words, realizing the control plane process in the multi-hop relay scenario.
  • the target device may be, for example, a target terminal device
  • the communication link may include a source terminal device, a target terminal device, and multiple relay terminal devices (relay terminal device #1 to relay terminal device #3) between the source terminal device and the target terminal device. That is, Figures 6 and 8 may be applicable to a multi-hop U2U relay scenario.
  • the target device may be, for example, a network device
  • the communication link may include a source terminal device, a network device, and multiple relay terminal devices (relay terminal device #1 to relay terminal device #3) between the source terminal device and the network device. That is, Figures 7 and 9 may be applicable to a multi-hop U2N relay scenario.
  • FIGs 6 and 7 there is an RRC connection between all non-adjacent nodes (devices).
  • RRC connection between the adjacent nodes in Figures 6 and 7 (not drawn in Figures 6 and 7).
  • the achievable process includes:
  • the RRC reconfiguration message may be carried in a cross-hop message.
  • the source terminal device may send the RRC reconfiguration message to the relay terminal device #2 via the cross-hop PC5-RRC connection between the source terminal device and the relay terminal device #2; and for another example, in Figure 6, the relay terminal device #2 may send the RRC reconfiguration message to the target terminal device via the cross-hop PC5-RRC connection between the source terminal device and the relay terminal device #2.
  • the RRC reconfiguration message may not be carried in the cross-hop message, but may be configured by per-hop signaling.
  • the source terminal device may send the RRC reconfiguration message to the relay terminal device #1 through the PC5-RRC connection between the source terminal device and the relay terminal device #1; for another example, the relay terminal device #1 may send the RRC reconfiguration message to the relay terminal device #2 through the PC5-RRC connection between the relay terminal device #2; for another example in Figure 6, the relay terminal device #3 may send the RRC reconfiguration message to the target terminal device through the PC5-RRC connection between the source terminal device and the relay terminal device #1.
  • RRC reconfiguration process can be executed by any terminal device in the communication link, for example, by a source terminal device, a target terminal device or any relay terminal device, which is not limited in this embodiment of the present application.
  • the RRC reconfiguration message may include at least one of the following: SRAP configuration, RLC configuration, MAC configuration.
  • the configuration of UE-ID and bearer ID in the SRAP layer may include: the UE-ID allocated to the current UE (i.e., the UE receiving the RRC reconfiguration message) and the UE-IDs of other UEs on the entire link.
  • the reasons for the cross-hop PC5-RRC wireless link failure may include: wireless link failure occurs in one or more intermediate hops. For example, if the wireless link fails in the first hop and/or the second hop, the PC5-RRC wireless link between the source terminal device and the relay terminal device #2 fails; for another example, in FIG6, if the wireless link fails in the third hop and/or the fourth hop, the PC5-RRC wireless link between the relay terminal device #2 and the target terminal device fails.
  • the cause of the cross-hop PC5-RRC wireless link failure may include: a wireless link failure occurs between any two adjacent devices in the communication link.
  • the PC5-RRC wireless link failure between relay terminal device #1 and relay terminal device #3 may be caused by a wireless link failure between any two adjacent devices in the communication link.
  • it may be caused by a wireless link failure between the source terminal device and relay terminal device #1 (i.e., the first hop).
  • the reason for the cross-hop PC5-RRC connection release may include: the PC5-RRC connection release occurs in one or more intermediate hops. For example, if the PC5-RRC connection release occurs in the first hop and/or the second hop, the PC5-RRC connection between the source terminal device and the relay terminal device #2 is released; for another example, in Figure 6, if the PC5-RRC connection release occurs in the third hop and/or the fourth hop, the PC5-RRC connection between the relay terminal device #2 and the target terminal device is released.
  • the reason for the cross-hop PC5-RRC connection release may include: PC5-RRC connection release occurs at any one or more hops on the other side. For example, for relay terminal device #2, when PC5-RRC connection release occurs at the third hop and/or the fourth hop, the PC5-RRC connection release between the source terminal device and the relay terminal device #2 will also be caused.
  • the reason for the cross-hop PC5-RRC connection release may include: a PC5-RRC connection release occurs between any two adjacent devices in the communication link.
  • the PC5-RRC connection release between relay terminal device #1 and relay terminal device #3 may be caused by a PC5-RRC connection release between any two adjacent devices in the communication link.
  • it may be caused by a PC5-RRC connection release between the source terminal device and relay terminal device #1 (i.e., the first hop).
  • a terminal device in the communication link may send a request message to another terminal device (e.g., terminal device #2) with an RRC connection, requesting a paging message for the terminal device #1 and/or system information required by the terminal device #1.
  • the request message may be, for example, remote UE information (Remote UE Information).
  • each hop terminal device can directly send the request message to another terminal device that meets the first condition through the RRC connection to request a paging message for the terminal device (terminal device #1) and/or the system information required by the terminal device (such as SIB).
  • each hop terminal device (such as terminal device #1) can carry the request message in any hop RRC message. If the relay terminal device that receives the request message does not meet the first condition, the relay terminal device that receives the request message needs to continue forwarding/sending forward and finally forward the request message to the terminal device that meets the first condition.
  • the first condition may include at least one of the following: being within the signal coverage of the network device; being the device closest to the network device in the communication link; and being able to directly obtain paging messages and/or system information from the network device.
  • terminal device #1 can be, for example, a source terminal device, or can also be a relay terminal device (such as a relay terminal device that does not meet the first condition), and the embodiment of the present application is not limited to this.
  • terminal device #1 may send a request message to terminal device #2 to request a paging message for terminal device #1 and/or system information required by terminal device #1.
  • a terminal device in the communication link (such as a terminal device that meets the first condition above) may obtain the information requested by terminal device #1 from the network device based on the request message, and send the information requested by terminal device #1 to terminal device #1.
  • the terminal device that meets the first condition can send the information requested by terminal device #1 directly to terminal device #1 through a PC5-RRC message (or through a PC5-RRC connection).
  • the terminal device that meets the first condition may transmit the information requested by terminal device #1 hop by hop until it is transmitted to terminal device #1.
  • the terminal device that triggers the sending of the notification message can send the notification message to each terminal device in the communication link through PC5-RRC.
  • relay terminal device #3 can send the notification message to the source terminal device, relay terminal device #1, relay terminal device #2 and target terminal device through the PC5-RRC connection.
  • the notification message can be used to indicate the radio link status (such as RLF) of relay terminal device #3, or to indicate that a network connection status change (such as cell switching, cell reselection or RRC connection status change) or a radio link status change (such as a decrease in the link quality of the radio link) occurs in relay terminal device #3.
  • the terminal device that triggers the sending of the notification message may be any terminal device in the communication link, for example, a source terminal device, a target terminal device or any relay terminal device, which is not limited in the present embodiment of the application.
  • a terminal device in a communication link may send indication information to another terminal device (for example, denoted as terminal device #2) with an RRC connection, to instruct terminal device #2 to measure the surrounding wireless communication conditions.
  • terminal device #1 may configure terminal device #2 to measure and report link conditions between terminal device #2 and other terminal devices, such as SL/SD-RSRP between terminal device #2 and other terminal devices.
  • terminal device #1 may also configure terminal device #2 to measure and report the link status between terminal device #2 and the network device, such as Uu-RSRP between terminal device #2 and the network device.
  • terminal device #1 may also configure terminal device #2 to measure and report CBR measurement status.
  • the terminal device #1 can be any terminal device in the communication link, for example, a source terminal device, a target terminal device or any relay terminal device, which is not limited in the present embodiment.
  • the central terminal device can be determined/defined, for example, as any of the following terminal devices: a source terminal device; a target terminal device; a device that is closest to the source terminal device in the communication link; a device that is closest to the target terminal device in the communication link; a device determined based on preset rules.
  • the preset rules can be specified, for example, by a protocol. For example, it can be specified that the terminal device with the strongest capability in the communication link is determined as the central terminal device; for another example, it can be specified that the terminal device in the communication link that is in a connected state or within the network coverage is determined as the central terminal device.
  • the central terminal device can configure the split QoS (single-hop QoS) on the non-local hop through the cross-hop RRC connection.
  • the relay terminal device #2 can configure the single-hop QoS on the fourth hop, that is, the QoS between the relay terminal device #3 and the target terminal device, through the cross-hop PC5-RRC connection between the relay terminal device #2 and the target terminal device.
  • This process can be executed by one of the terminal devices in the communication link (such as the central terminal device mentioned above).
  • the central terminal device can configure transmission resources for all terminal devices in the current communication link through RRC messages. In this way, the purpose of reducing latency can be achieved through centralized resource allocation.
  • the resources allocated by the central terminal device in a centralized manner can be obtained based on the aforementioned first mode or second mode, for example.
  • the achievable process includes:
  • each terminal device can report at least one of the following contents to the network device through the Uu-RRC connection: RLF occurring in the terminal device, measurement report (such as the channel quality between the terminal device and other terminal devices), identification of all terminal devices in the communication link, etc.
  • the network device can configure transmission resources in the first mode for each terminal device (including terminal devices that are not directly connected) through RRC messages.
  • FIGs 8 and 9 there is no RRC connection between non-adjacent nodes (excluding between the source terminal device and the target device), and there is an RRC connection between adjacent nodes.
  • FIG 8 there is a PC5-RRC connection for the first hop, the second hop, the third hop, and the fourth hop.
  • Figure 9 there is a PC5-RRC connection for the first hop, the second hop, and the third hop, and there is a Uu-RRC connection for the fourth hop.
  • the source terminal device and the target device such as the target terminal device in Figure 8; and the network device in Figure 9
  • the achievable process includes:
  • the configuration of each hop can be determined by the terminal device of this hop, or by the terminal device of this hop based on the configuration of the previous hop, that is, the terminal device of this hop needs to decode the configuration sent to it by the terminal device of the previous hop, and determine its own configuration based on the configuration.
  • the relay terminal device #1 in a first possible manner, can autonomously determine the configuration on the second hop (that is, the configuration between the relay terminal device #1 and the relay terminal device #2); in a second possible manner, the relay terminal device #1 can receive and decode the RRC reconfiguration message from the source terminal device, and determine the configuration on the second hop based on the RRC reconfiguration message.
  • a terminal device in the communication link may send a request message to an adjacent terminal device (e.g., terminal device #2) to request a paging message for the terminal device #1 and/or system information required by the terminal device #1.
  • the request message may be, for example, remote terminal information (Remote UE Information).
  • each hop terminal device can send its own request message to the next hop terminal device (such as terminal device #2). If the terminal device #2 that receives the request message does not meet the first condition, the terminal device #2 can continue to forward/send the request message forward (or to the next hop), and can add the request message of the terminal device #2 itself to the request message to request a paging message for the terminal device #2 and/or the system information required by the terminal device #2. If the terminal device that receives the request message meets the first condition, it can stop forwarding/sending.
  • the first condition may include at least one of the following: being within the signal coverage range of the network device; being within the distance of the network device in the communication link; The device closest to the network device; able to obtain paging messages and/or system information directly from the network device.
  • terminal device #1 can be, for example, a source terminal device, or can also be a relay terminal device (such as a relay terminal device that does not meet the first condition), and the embodiment of the present application is not limited to this.
  • each hop terminal device may decode the paging message and/or system information it has received, and continue to send the paging message and/or system information requested by other terminal devices in the subsequent communication link.
  • relay terminal device #3 can decode the obtained information and send the paging message and system information requested by relay terminal device #2 and relay terminal device #1 to relay terminal device #2.
  • relay terminal device #2 can decode the information from relay terminal device #3 and send the paging message and system information requested by relay terminal device #1 to relay terminal device #1.
  • the terminal device that triggers the notification message can send the notification message to the terminal device directly connected to it through the PC5-RRC connection, and the terminal device that receives the notification message continues to forward it backward (to the next hop).
  • the terminal device that receives the notification message may further add its own notification information to the message (if triggered), and carry the identifier of the terminal device that triggered the sending of the message, and/or the identifier of the number of transmission hops associated with triggering the sending of the message (or referred to as hop identifier/hop level) in the notification message. For example, if the triggering reason for sending the message is that a certain hop sends RLF, then the identifier of the number of transmission hops associated with triggering the sending of the message is the identifier of the hop.
  • relay terminal device #3 can send the notification message to relay terminal device #2 and the target terminal device directly connected thereto through the PC5-RRC connection.
  • the notification message can carry, for example, the identifier of relay terminal device #3, and/or the identifier of the number of transmission hops associated with triggering relay terminal device #3 to send the notification message.
  • relay terminal device #2 can add its own notification message to the notification message, and carry the identifier of relay terminal device #2, and/or the identifier of the number of transmission hops associated with triggering relay terminal device #2 to send the notification message in the notification message.
  • relay terminal device #2 can send the notification messages of relay terminal device #3 and relay terminal device #2 to relay terminal device #1.
  • the terminal device that triggers the sending of the notification message may be any terminal device in the communication link, for example, a source terminal device, a target terminal device or any relay terminal device, which is not limited in the present embodiment of the application.
  • the notification message can be used to indicate the radio link status (such as RLF) of the terminal device that triggered the sending of the notification message, or to indicate that the terminal device has a network connection status change (such as cell switching, cell reselection or RRC connection status change) or a radio link status change (such as a decrease in link quality of the wireless link).
  • RLF radio link status
  • network connection status change such as cell switching, cell reselection or RRC connection status change
  • a radio link status change such as a decrease in link quality of the wireless link.
  • each terminal device can allocate the QoS on its own hop.
  • each terminal device can also send the QoS of its own hop and the remaining unallocated QoS to the next hop terminal device, so that the next hop terminal device can further allocate the QoS on the hop where the next hop terminal device is located.
  • relay terminal device #1 can allocate QoS on the first hop and send the remaining unallocated QoS to relay terminal device #2, whereby relay terminal device #2 can allocate QoS on the second hop from the remaining unallocated QoS and send the remaining unallocated QoS to relay terminal device #3, and so on.
  • the source terminal device can allocate QoS on the first hop, and can send the QoS on the first hop and the remaining unallocated QoS to the relay terminal device #1, whereby the relay terminal device #1 can allocate QoS on the second hop from the remaining unallocated QoS, and send the QoS on the second hop and the remaining unallocated QoS to the relay terminal device #2, and so on.
  • each terminal device when QoS segmentation is performed in the above manner, each terminal device is required to obtain one or more of the following information:
  • the number of transmission hops on the communication link is 4.
  • the transmission hop number where the current terminal device is located is the first hop; and the transmission hop number where the relay terminal device #2 is located is the second hop.
  • the number of transmission hops remaining to which QoS is not allocated is 3 hops.
  • the source terminal device can send the QoS on the first hop and the remaining unallocated QoS to the relay terminal device #1, and can also inform the relay terminal device #1 of the number of transmission hops remaining to which QoS is not allocated (3 hops), so that the relay terminal device #1 can perform the next step of QoS segmentation based on the remaining unallocated QoS and the remaining number of transmission hops remaining to which QoS is not allocated.
  • the achievable process includes:
  • the terminal device in the connected state can report one or more of the following information of all the terminal devices in the non-connected state on the communication link to the network device through the Uu-RRC connection:
  • the RLF of the non-connected terminal device the measurement report of the non-connected terminal device (such as the channel quality between the non-connected terminal device and other terminal devices), the identification of the non-connected terminal device (L2ID), and the number of transmission hops between the non-connected terminal device and the network device.
  • the embodiment of the present application designs a control plane process in a multi-hop U2U/U2N relay scenario and implements RRM in a multi-hop relay scenario.
  • connection modes in Figures 7 to 9 are only examples for ease of understanding.
  • possible connection modes may also include at least one of the following:
  • the target device is a network device, that is, in a multi-hop U2N relay scenario, a Uu-RRC connection exists between some or all of the terminal devices in the communication link and the network device;
  • the target device is a network device, that is, in a multi-hop U2N relay scenario
  • the terminal device closest to the network device in the communication link has a PC5-RRC connection with all or part of the other terminal devices
  • RRC connection between some or all devices in the communication link and a determined/defined central terminal device (or referred to as a control terminal device).
  • the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
  • downlink indicates that the transmission direction of the signal or data
  • uplink is used to indicate that the transmission direction of the signal or data is the second direction sent from the user equipment of the cell to the site
  • side is used to indicate that the transmission direction of the signal or data is the third direction sent from user equipment 1 to user equipment 2.
  • downlink signal indicates that the transmission direction of the signal is the first direction.
  • the term "and/or” is only a description of the association relationship of the associated objects, indicating that three relationships can exist. Specifically, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character “/" in this article generally indicates that the front and back associated objects are in an "or" relationship.
  • the embodiments of the present application provide a corresponding wireless resource management device.
  • FIG10 is a schematic diagram of the structure of a wireless resource management device provided in an embodiment of the present application, which is applied to a first device.
  • the communication link in which the wireless resource management device 1000 is located includes a source terminal device, a target device, and multiple relay terminal devices between the source terminal device and the target device.
  • the wireless resource management device 1000 (hereinafter referred to as the device 1000) includes:
  • the first sending unit 1001 is used to send first information to a second device in a communication link through a radio resource control RRC connection, where the first information is related to radio resource management.
  • the second device is not adjacent to the apparatus 1000 in the communication link.
  • device 1000 is a terminal device that does not satisfy the first condition in the communication link
  • the second device is a terminal device that satisfies the first condition in the communication link
  • the target device is a network device
  • the first information is used to request a paging message for device 1000, and/or system information required by device 1000
  • the first condition includes at least one of the following: being within the signal coverage range of the network device; being the device closest to the network device in the communication link; and being able to obtain paging messages and/or system information directly from the network device.
  • the first information when the first information is used to request a paging message for device 1000, the first information includes: information required for monitoring the paging message of device 1000; when the first information is used to request system information required by device 1000, the first information includes: the type of system information required by device 1000.
  • the apparatus 1000 is a terminal device that meets the first condition in the communication link
  • the second device is a terminal device that does not meet the first condition in the communication link
  • the target device is a network device
  • the first information includes: a paging message for the second device, and/or system information required by the second device
  • the first condition includes at least one of the following: being within the signal coverage of the network device; being in the communication link A device that is closest to the network device; and capable of directly obtaining paging messages and/or system information from the network device.
  • the apparatus 1000 further includes a first receiving unit for receiving second information from a second device before sending first information to a second device in the communication link through an RRC connection, the second information being used to request a paging message for the second device and/or system information required by the second device; in a case where the second information is used to request a paging message for the second device, the second information includes: information required for monitoring paging messages of the second device; in a case where the second information is used to request system information required by the second device, the second information includes: the type of system information required by the second device.
  • the first information when the second information includes information required to monitor a paging message of a second device, the first information includes: a paging message for the second device; when the second information includes a type of system information required by the second device, the first information includes: the system information required by the second device.
  • the apparatus 1000 further includes a first acquisition unit for acquiring, before sending first information to a second device in the communication link via an RRC connection, a paging message for the second device from a network device based on information required for monitoring a paging message of the second device; and/or acquiring, based on a type of system information required by the second device, system information required by the second device from the network device.
  • the apparatus 1000 and the second device are different terminal devices in the communication link; the first information is used to indicate the wireless link status of the apparatus 1000, or to indicate that a network connection status change or a wireless link status change occurs in the apparatus 1000.
  • the apparatus 1000 and the second device are different terminal devices in a communication link; the first information is used to instruct the second device to measure a channel busy ratio and/or a link quality between the second device and at least one third device.
  • the link quality includes: a reference signal received power.
  • the apparatus 1000 and the second device are different terminal devices in a communication link; the first information is used to indicate the quality of service QoS between the second device and a fourth device; wherein the second device and the fourth device are adjacent to each other in the communication link.
  • the apparatus 1000 and the second device are different terminal devices in a communication link; the first information is used to configure transmission resources of the second device.
  • the transmission resource of the second device is selected by apparatus 1000 from a resource pool, or is allocated by a target device, where the target device is a network device.
  • the apparatus 1000 is any one of the following devices: a source terminal device; a target device; a device that is closest to the source terminal device in the communication link; a device that is closest to the target device in the communication link; or a device determined based on a preset rule.
  • the apparatus 1000 and the second device are different terminal devices in the communication link;
  • the first information is an RRC reconfiguration message, and the RRC reconfiguration message includes at least one of the following: sidelink relay adaptation protocol SRAP configuration; radio link control configuration; and media access control configuration; wherein the SRAP configuration includes: an identifier assigned to the second device and/or identifiers of other terminal devices in the communication link.
  • apparatus 1000 and the second device are different terminal devices in a communication link; when a second condition is met, a wireless link failure occurs between apparatus 1000 and the second device; the second condition includes: a wireless link failure occurs between apparatus 1000 and the second device, or between any two adjacent devices; or, a wireless link failure occurs between any two adjacent devices in the communication link.
  • the apparatus 1000 and the second device are different terminal devices in the communication link, and there is an RRC connection between the apparatus 1000 and the second device; when the third condition is met, the RRC connection between the apparatus 1000 and the second device is released; the third condition includes: the RRC connection between the apparatus 1000 and the second device, or between any two adjacent devices is released; or, the RRC connection between any two adjacent devices in the communication link is released.
  • the target device is a network device or a terminal device.
  • the number of the second device is one or more.
  • the second device is a target device, and the target device is a network device; the first information is used to indicate at least one of the following: a wireless link failure of apparatus 1000; a channel quality between apparatus 1000 and at least one fifth device; and, identification of all terminal devices in the communication link.
  • the second device is a target device, and the target device is a network device; the transmission resources of the apparatus 1000 are configured for the apparatus 1000 by the network device through an RRC connection.
  • the apparatus 1000 further includes a second sending unit for sending third information to a sixth device in the communication link through an RRC connection, wherein the third information is related to wireless resource management; wherein the sixth device and the apparatus 1000 are adjacent in the communication link.
  • the second device is adjacent to the apparatus 1000 in a communication link.
  • device 1000 is a terminal device that does not meet the first condition in the communication link, the target device is a network device, and the second device is the next-hop terminal device of device 1000 in the uplink direction;
  • the first information is used to request a paging message for device 1000, and/or system information required by device 1000;
  • the first condition includes at least one of the following: being located within the signal coverage range of the network device; being the device closest to the network device in the communication link; and being able to obtain paging messages and/or system information directly from the network device.
  • the first information when the first information is used to request a paging message for device 1000, the first information includes: information required for monitoring the paging message of device 1000; when the first information is used to request system information required by device 1000, the first information includes: the type of system information required by device 1000.
  • apparatus 1000 is a terminal device that does not satisfy a first condition in a communication link, a target device is a network device, and a second device is a next-hop terminal device of apparatus 1000 in an uplink direction;
  • the first information is used to request a paging message for a seventh device, and/or system information required by the seventh device;
  • the seventh device in the communication link is a previous-hop terminal device of apparatus 1000 in an uplink direction, a source terminal device, or any device between apparatus 1000 and the source terminal device that has an RRC connection with apparatus 1000;
  • the first condition includes at least one of the following: being within the signal coverage range of the network device; being the device closest to the network device in the communication link; and being able to obtain paging messages and/or system information directly from the network device.
  • the first information when the first information is used to request a paging message for a seventh device, the first information includes: information required to monitor the paging message of the seventh device; when the first information is used to request system information required by the seventh device, the first information includes: the type of system information required by the seventh device.
  • the apparatus 1000 further includes a second receiving unit configured to receive first information from a seventh device via the RRC connection before sending the first information to the second device in the communication link via the RRC connection.
  • the device 1000 also includes a first processing unit for adding second information to the first information before sending the first information to the second device in the communication link via the RRC connection, the second information being used to request a paging message for the device 1000, and/or system information required by the device 1000.
  • the second information when the second information is used to request a paging message for device 1000, the second information includes: information required for monitoring the paging message of device 1000; when the second information is used to request system information required by device 1000, the second information includes: the type of system information required by device 1000.
  • the second device is a terminal device in the communication link that satisfies the first condition.
  • the target device is a network device
  • the second device is the next-hop terminal device of the apparatus 1000 in the downlink direction, or is any terminal device between the apparatus 1000 and the source terminal device that has an RRC connection with the apparatus 1000
  • the first information includes: a paging message for an eighth device, and/or system information required by the eighth device; wherein the eighth device is the second device, the source terminal device, or any terminal device between the second device and the source terminal device.
  • the first information is obtained by the device 1000 from the network device; when the device 1000 does not satisfy the first condition, the first information is obtained by the device 1000 from a ninth device in the communication link; the ninth device is the previous-hop terminal device of the device 1000 in the downlink direction, or any terminal device between the device 1000 and the network device that has an RRC connection with the device 1000; the first condition includes at least one of the following: being located within the signal coverage range of the network device; being the device closest to the network device in the communication link; and being able to directly obtain paging messages and/or system information from the network device.
  • the apparatus 1000 further includes a third receiving unit for receiving fourth information from an eighth device through the second device before sending first information to a second device in the communication link through an RRC connection, the fourth information being used to request a paging message for the eighth device and/or system information required by the eighth device; when the fourth information is used to request a paging message for the eighth device, the fourth information includes: information required for monitoring paging messages of the eighth device; when the fourth information is used to request system information required by the eighth device, the fourth information includes: type of system information required by the eighth device.
  • the first information when the fourth information includes information required to monitor the paging message of the eighth device, the first information includes: the paging message for the eighth device; when the fourth information includes the type of system information required by the eighth device, the first information includes: the system information required by the eighth device.
  • the first information is used to indicate the wireless link status of the device 1000, or to indicate that a network connection status change or a wireless link status change occurs in the device 1000.
  • the second device is the next-hop terminal device of apparatus 1000; the first information is used to indicate the wireless link status of the tenth device, or to indicate that a network connection status change or a wireless link status change has occurred in the tenth device; wherein the tenth device is the previous-hop terminal device of apparatus 1000, or is a terminal device that is not adjacent to apparatus 1000 in the communication link.
  • the first information is obtained from a previous-hop terminal device of apparatus 1000 .
  • the device 1000 also includes a second processing unit for adding fifth information to the first information before sending the first information to the second device in the communication link through the RRC connection, wherein the fifth information is used to indicate the wireless link status of the device 1000, or to indicate a change in the network connection status or the wireless link status of the device 1000.
  • the fifth information includes at least one of: an identification of device 1000; an identification of the number of transmission hops associated with the wireless link state of device 1000; and an identification of the number of transmission hops associated with a change in the network connection state or the wireless link state of device 1000.
  • the radio link status includes: radio link failure;
  • the network connection status change includes: cell switching, cell reselection or RRC connection status change;
  • the radio link status change includes: link quality of the radio link decreases.
  • the first information is used to indicate at least one of the following: QoS between the apparatus 1000 and the second device;
  • the apparatus 1000 further includes a determining unit configured to send a second device in the communication link via the RRC connection. Before sending the first information, the QoS between the apparatus 1000 and the second device is determined.
  • the second device is a next-hop terminal device of apparatus 1000; the first information is an RRC reconfiguration message between apparatus 1000 and the second device, and the RRC reconfiguration message includes at least one of the following: SRAP configuration; wireless link control configuration; and media access control configuration.
  • the first information is determined by the apparatus 1000; or, the first information is determined by the apparatus 1000 based on an RRC reconfiguration message between the apparatus 1000 and a previous-hop terminal device.
  • the target device is a network device or a terminal device.
  • the second device is a target device, and the target device is a network device;
  • the first information is used to indicate at least one of the following: a wireless link failure of the eleventh device; the channel quality between the eleventh device and at least one twelfth device; an identification of the eleventh device; and the number of transmission hops between the eleventh device and the network device; wherein the eleventh device is a terminal device in the communication link that has no RRC connection with the network device.
  • the apparatus 1000 further includes a third sending unit for sending sixth information to a thirteenth device in the communication link through an RRC connection, wherein the sixth information is related to wireless resource management; wherein the thirteenth device and the apparatus 1000 are not adjacent in the communication link.
  • the communication link has at least one of the following characteristics: an RRC connection exists between all adjacent devices in the communication link; an RRC connection exists between some or all of the non-adjacent devices in the communication link; when the target device is a network device, an RRC connection exists between some or all of the terminal devices in the communication link and the network device; when the target device is a network device, an RRC connection exists between the terminal device closest to the network device in the communication link and all or part of the other devices; an RRC connection exists between some or all of the devices in the communication link and a fourteenth device, and the fourteenth device is any one of the following devices: a source terminal device; a target device; a device in the communication link that is closest to the source terminal device; a device in the communication link that is closest to the target device; a device determined based on preset rules.
  • whether apparatus 1000 establishes an RRC connection with other devices is determined by apparatus 1000 or a network device.
  • the first information is identified by one or more of: a radio link control channel; a bearer identifier; a logical channel.
  • Fig. 11 is a schematic structural diagram of a communication device 1100 provided in an embodiment of the present application.
  • the communication device 1100 shown in Fig. 11 includes a processor 1110, and the processor 1110 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 1100 may further include a memory 1120.
  • the processor 1110 may call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.
  • the memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .
  • the communication device 1100 may further include a transceiver 1130 , and the processor 1110 may control the transceiver 1130 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
  • the transceiver 1130 may include a transmitter and a receiver.
  • the transceiver 1130 may further include an antenna, and the number of the antennas may be one or more.
  • the communication device 1100 may specifically be the first device of the embodiment of the present application, and the communication device 1100 may implement the corresponding processes implemented by the first device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
  • Fig. 12 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 1200 shown in Fig. 12 includes a processor 1210, and the processor 1210 can call and run a computer program from a memory to implement the method according to the embodiment of the present application.
  • the chip 1200 may further include a memory 1220.
  • the processor 1210 may call and run a computer program from the memory 1220 to implement the method in the embodiment of the present application.
  • the memory 1220 may be a separate device independent of the processor 1210 , or may be integrated into the processor 1210 .
  • the chip 1200 may further include an input interface 1230.
  • the processor 1210 may control the input interface 1230 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
  • the chip 1200 may further include an output interface 1240.
  • the processor 1210 may control the output interface 1240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
  • the chip can be applied to the first device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.
  • the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software.
  • the above processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other Other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general processor can be a microprocessor or the processor can also be any conventional processor, etc.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution.
  • the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory can be a random access memory (RAM), which is used as an external cache.
  • RAM Direct Rambus RAM
  • SRAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • DDR SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced SDRAM
  • SLDRAM Synchlink DRAM
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.
  • the embodiment of the present application also provides a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to the first device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the first device in each method of the embodiment of the present application, which will not be described here for the sake of brevity.
  • the embodiment of the present application also provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the first device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding process implemented by the first device in each method of the embodiment of the present application, which will not be described here for brevity.
  • the present application also provides a computer program.
  • the computer program can be applied to the first device in the present application, and when the computer program is run on a computer, the computer executes the corresponding process implemented by the first device in each method of the present application, which will not be described in detail for the sake of brevity.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including
  • the instructions are used to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

Landscapes

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

Abstract

本申请实施例提供一种无线资源管理方法，应用于第一设备，第一设备所在的通信链路中包括源终端设备、目标设备，以及源终端设备和目标设备之间的多个中继终端设备，该方法包括：通过无线资源控制RRC连接向通信链路中的第二设备发送第一信息，第一信息与无线资源管理相关。该方法设计了多跳中继场景下的控制面流程，实现了多跳中继场景下的无线资源管理。

Description

一种无线资源管理方法、装置、终端、芯片和存储介质 技术领域
本申请实施例涉及通信技术领域，具体涉及一种无线资源管理方法、装置、终端、芯片和存储介质。
背景技术
目前，对于终端到终端(UE to UE，U2U)或终端到网络(UE to Network，U2N)中继(Relay)的研究主要针对单跳场景，也即，源终端和目标终端(或基站)之间仅存在一个中继终端。而未来很大可能会引入多跳中继来进一步增强覆盖范围，也即，源终端和目标终端(或基站)之间可能存在多个中继终端。
然而，目前尚未有方案揭示在源终端和目标终端(或基站)之间存在多个中继终端的场景下，如何实现无线资源管理(Radio Resource Management，RRM)过程。
发明内容
本申请实施例提供一种无线资源管理方法、装置、终端、芯片和存储介质。
第一方面，本申请实施例提供了一种无线资源管理方法，应用于第一设备，第一设备所在的通信链路中包括源终端设备、目标设备，以及源终端设备和目标设备之间的多个中继终端设备，该方法包括：通过无线资源控制RRC连接向通信链路中的第二设备发送第一信息，第一信息与无线资源管理相关。
第二方面，本申请实施例提供了一种无线资源管理装置，该装置所在的通信链路中包括源终端设备、目标设备，以及源终端设备和目标设备之间的多个中继终端设备，该装置包括：第一发送单元，用于通过无线资源控制RRC连接向通信链路中的第二设备发送第一信息，第一信息与无线资源管理相关。
第三方面，本申请实施例提供了一种终端，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的无线资源管理方法。
第四方面，本申请实施例提供了一种芯片，用于实现上述的无线资源管理方法。具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行上述的无线资源管理方法。
第五方面，本申请实施例提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述的无线资源管理方法。
第六方面，本申请实施例提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述的无线资源管理方法。
第七方面，本申请实施例提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述的无线资源管理方法。
通过上述技术方案，实现了多跳中继场景下的无线资源管理过程，或者说，实现了多跳中继场景下的控制面流程。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1-1是本申请实施例提供的第一模式对应的资源选择示意图；
图1-2是本申请实施例提供的第二模式对应的资源选择示意图；
图2是本申请实施例提供的中继UE在源UE和目标UE间传递数据的一例示意图；
图3是本申请实施例提供的源UE和目标UE之间建立连接的流程示意图；
图4是本申请实施例提供的U2U中继用户面协议栈的一例示意图；
图5是本申请实施例提供的无线资源管理方法的流程示意图；
图6是本申请实施例提供的多跳场景下的网络连接方式的示意图一；
图7是本申请实施例提供的多跳场景下的网络连接方式的示意图二；
图8是本申请实施例提供的多跳场景下的网络连接方式的示意图三；
图9是本申请实施例提供的多跳场景下的网络连接方式的示意图四；
图10是本申请实施例提供的无线资源管理装置的结构组成示意图；
图11是本申请实施例提供的一种通信设备示意性结构图；
图12是本申请实施例的芯片的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种侧行通信系统，为便于理解本申请实施例的技术方案，以下对本申请实施例的相关技术进行说明，以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。
1、长期演进(Long Term Evolution，LTE)中的设备到设备(Device to Device，D2D)/车联网(Vehicle to Everything，V2X)
设备到设备通信是基于D2D的一种侧行链路(Sidelink，SL)传输技术。与传统的蜂窝系统中通信数据通过基站接收或者发送的方式不同，车联网系统采用终端到终端直接通信的方式，因此具有更高的频谱效率以及更低的传输时延。在第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)中定义了两种传输模式：第一模式(模式3)和第二模式(模式4)。
第一模式：终端的传输资源是由基站(eNB)分配的，终端根据基站分配的资源在侧行链路上进行数据的发送。基站可以为终端分配单次传输的资源，也可以为终端分配半静态传输的资源。如图1-1所示，终端的传输资源是由基站分配的，基站通过下行链路基于授权信令(Grant)向终端分配资源，终端根据基站分配的资源在侧行链路上进行数据的传输。
第二模式：终端在资源池中选取一个资源进行数据的传输。如图1-2所示，终端在资源池中选取一个资源进行数据的传输。
在3GPP中，D2D分成了以下不同的阶段进行研究：
1)近距离通信(Proximity based Service，ProSe)：在Rel-12/13中，设备到设备通信针对ProSe场景进行了研究，其主要针对公共安全类的业务。
在ProSe中，通过配置资源池在时域上的位置，例如资源池在时域上非连续，达到UE在侧行链路上非连续发送/接收数据，从而达到省电的效果。
2)V2X：在Rel-14/15中，车联网系统针对车车通信的场景进行了研究，其主要面向相对高速移动的车车、车人通信的业务；
在V2X中，由于车载系统具有持续的供电，因此功率效率不是主要问题，而数据传输的时延是主要问题，因此在系统设计上要求终端设备进行连续的发送和接收。
3)可穿戴设备(FeD2D)：在Rel-14中，该场景对于可穿戴设备通过手机接入网络的场景进行了研究，其主要面向低移动速度以及低功率接入的场景。
在FeD2D中，在预研阶段3GPP结论为基站可以通过一个中继终端配置远端(Remote)终端的非连续接收(Discontinuous Reception，DRX)参数，但未对如何进行DRX配置的具体细节给出结论。
2、新无线(New Radio，NR)V2X
NR V2X在LTE V2X的基础上，不局限于广播场景，而是进一步拓展到了单播和组播的场景，在这些场景下研究V2X的应用。
类似于LTE V2X，NR V2X也定义了mode-1/2(即上述第一模式和第二模式)两种资源授权模式。不同于LTE V2X，除了无反馈的、UE自主发起的HARQ重传，NR V2X引入了基于反馈的HARQ重传，不限于单播通信，也包括组播通信。
3、侧行U2U中继技术
在Rel-17ProSe中，3GPP研究了基于层2、3中继的U2U中继功能，即源UE通过中继UE连接至目标UE，中继UE在源UE和目标UE间传递数据，如图2所示。
作为示例，源UE和目标UE间的连接建立步骤如图3所示。其中，源(Source)UE、中继(Relay)UE、目标(Target)UE之间通过发现(Discovery)消息或直连通信请求(Direct Communication Request，DCR)消息互相发现，中继UE可帮助源UE转发发现消息或DCR消息，源UE和目标UE发现对方后 即可进行中继选择，选择合适的中继分别与其建立连接，再由该中继建立端到端的PC5连接。其中，建立PC5连接还可以理解为通过直接通信接口建立连接。
如图3所示，源UE和目标UE间的连接建立步骤可包括：
S301，U2U中继进行中继功能注册，以及中继功能参数配置。
例如，U2U中继可向核心网注册成为具有中继功能的中继UE，并配置与中继功能相关的参数。
S302，源UE和目标UE互相发现。
S303，源UE和目标UE进行中继选择。
S304，源UE、目标UE分别与U2U中继建立每跳(per hop)连接。
S305，源UE和目标UE通过U2U中继建立端到端(End to End)连接。
4、U2U中继用户面协议栈
图4是U2U中继用户面协议栈的一例示意图。3GPP Rel-17引入了层二U2U中继，如图4所示，适配层(ADAPT)被放置在中继UE和源/目标UE之间的控制面和用户面无线链路控制(Radio Link Control，RLC)子层之上。PC5服务数据适配协议(Service Data Adaptation Protocol，SDAP)/分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)和无线资源控制(Radio Resource Contro，RRC)终止在源UE和目标UE之间，而RLC、媒体接入控制(Media Access Control，MAC)和物理层(Physical Layer，PHY)终止在每个链路中(即源UE和中继UE之间的链路以及中继UE和目标UE之间的链路)。在源UE和中继UE之间的PC5接口处是否也支持适配层目前尚未得出结论。
对于L2U2U中继，一方面，中继UE的适配层支持接入PC5RLC信道之间的侧行承载映射。对于侧行链路中继业务，同一远端UE和/或不同远端UE的不同端到端承载(如信令无线承载(Signalling Radio Bearer，SRB)；又如数据无线承载(Data Radio Bearer，DRB))可以在一个PC5RLC信道上进行N:1映射和数据复用。
另一方面，适配层用于支持侧行业务的UE标识(复用来自多个UE的数据)。UE PC5无线承载和UE的标识信息包括在适配层中，以便目标UE将与源UE的无线承载相关联的特定PDCP实体的接收数据分组关联起来。
5、U2N中继
远端UE进行测量上报，将中继UE标识、服务小区标识、参考信号接收功率(Reference Signal Receiving Power，RSRP)测量等信息包含在测量上报信息内。在远端UE执行非直接路径到直接路径的链路切换时，对于服务中继UE来说，更推荐使用SL-RSRP进行侧行链路上的测量；在远端UE执行直接路径到非直接路径的链路切换时，使用SD-RSRP进行侧行链路上的测量。另外，在执行测量上报时，为U2N中继切换定义了两个新的测量上报触发事件。事件1：当服务中继UE的链路质量低于所配置门限值，且(可选地)相邻小区的链路质量高于所配置门限值时，远端UE执行测量上报；事件2：当服务小区链路质量低于所配置门限值时，且可选中继UE链路质量高于所配置门限值时，远端UE执行测量上报。另外，为了辅助远端UE执行直接链路到非直接链路的切换，引入了一个新的定时器，当远端UE接收到指示直接链路到非直接链路切换的RRC重配消息时，远端UE开启定时器。当定时器超时时，远端UE执行RRC重建立。
上面对本申请实施例中涉及到的相关技术/术语做了简单说明，下文实施例中不再赘述。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。还应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。还应理解，在本申请的实施例中提到的“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。还应理解，在本申请的实施例中提到的“预定义”或“预定义规则”可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。
还应理解，本申请实施例对于终端设备和网络设备的具体形态不做限定。
本申请实施例中的终端设备可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、IoT设备、卫星手持终端、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital  Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进网络中的终端设备等。
本申请实施例中的网络设备可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是下一代无线接入网(Next Generation Radio Access Network，NG RAN)设备，或者是NR系统中的基站(gNB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备120可以为中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
目前，对于U2U/U2N中继的研究主要针对单跳场景，也即，源终端和目标终端(或基站)之间仅存在一个中继终端。而未来很大可能会引入多跳中继来进一步增强覆盖范围，也即，源终端和目标终端(或基站)之间可能存在多个中继终端。在考虑多个中继后，会对多跳中继之间的PC5RRM过程有所影响。然而，目前尚未有方案揭示在源终端和目标终端(或基站)之间存在多个中继终端的场景下(也即多跳U2U/U2N中继场景下)，如何实现RRM过程，或者说，如何进行控制面流程。
鉴于此，本申请提供一种无线资源管理方法、装置、终端、芯片和存储介质。该方法可适用于多跳U2U/U2N中继场景。在该方法中，通信链路中的第一设备可通过RRC连接向第二设备发送与无线资源管理相关的信息，从而实现多跳中继场景下的无线资源管理过程，或者说，实现多跳中继场景下的控制面流程。
为便于理解本申请实施例的技术方案，以下通过具体实施例详述本申请的技术方案。以上相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。本申请实施例包括以下内容中的至少部分内容。
图5是本申请实施例提供的无线资源管理方法的流程示意图。该方法可应用于第一设备，第一设备所在的通信链路中包括源终端设备、目标设备，以及源终端设备和目标设备之间的多个中继终端设备。需要说明的是，本申请实施例中的目标设备可以是网络设备或终端设备。一般地，在未特别说明的情况下，本申请实施例中的目标设备可以是网络设备，或者也可以是终端设备。
如图5所示，该无线资源管理方法可包括以下步骤：
S501，通过RRC连接向通信链路中的第二设备发送第一信息，第一信息与无线资源管理相关。
其中，第一信息与无线资源管理相关，还可以理解为，第一信息与控制面信息相关，或者还可以理解为，第一信息为控制面信息。
示例性地，本申请实施例中的第二设备与第一设备在通信链路中可以相邻，或者也可以不相邻。其中，第二设备与第一设备在通信链路中相邻，还可以理解为，第二设备与第一设备在通信链路中不存在中继终端设备，或者还可以理解为，第二设备与第一设备直接连接。第二设备与第一设备在通信链路中不相邻，还可以理解为，第二设备与第一设备在通信链路中存在至少一个中继终端设备，或者还可以理解为，第二设备与第一设备非直接连接。可理解的是，当第二设备与第一设备不相邻时，第一信息为跨跳传输的信息。
为便于描述，下文中将第二设备与第一设备在通信链路中不相邻的场景记为场景1，将第二设备与第一设备在通信链路中相邻的场景记为场景2。下面分别对该场景1和场景2进行介绍。
场景1：第二设备与第一设备在通信链路中不相邻。
在一些实施例中，第一设备为通信链路中不满足第一条件的终端设备，第二设备为通信链路中满足第一条件的终端设备，目标设备为网络设备，第一信息用于请求针对第一设备的寻呼(Paging)消息，和/或，第一设备所需的系统信息。其中，系统信息例如可以为系统信息块(System Information Block，SIB)。
示例性地，在第一信息用于请求针对第一设备的寻呼消息的情况下，第一信息可包括：为监听第一设备的寻呼消息所需的信息；在第一信息用于请求第一设备所需的系统信息的情况下，第一信息包括：第一设备所需的系统信息的类型。也就是说，若第一设备向第二设备请求针对第一设备的寻呼消息，则第一设备可在第一信息中携带为监听该寻呼消息所需的信息，如第一设备的标识(ID)、监听时段等。若第一设备向第二设备请求第一设备所需的系统信息，则第一设备可在第一信息中携带该第一设备所需的系统信息的类型。
示例性地，第一条件可包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网络设备最近的设备；能够直接从网络设备获取寻呼消息和/或系统信息。
一示例，假设第一条件为：位于网络设备的信号覆盖范围内，那么，不满足第一条件还可以理解为，位于网络设备的信号覆盖范围之外。
另一示例，假设第一条件为：为通信链路中距离网络设备最近的设备，那么，不满足第一条件还可以理解为，非通信链路中距离网络设备最近的设备。其中，通信链路中距离网络设备最近的终端设备， 例如可以是上行方向上的最后一跳终端设备，或者可以是与网络设备直连的终端设备。
又一示例，假设第一条件为：能够直接从网络设备获取寻呼消息和/或系统信息，那么，不满足第一条件还可以理解为，无法直接从网络设备获取寻呼消息和/或系统信息。其中，能够直接从网络设备获取寻呼消息和/或系统信息的终端设备，例如可以是与网络设备直连的终端设备。
再一示例，假设第一条件包括多项条件，那么，在一种可能的方式中，当不满足其中任意一项或多项条件时，可认为不满足第一条件；在另一种可能的方式中，当其中各项条件均不满足时，可认为不满足第一条件。举例来说，假设第一条件包括：位于网络设备的信号覆盖范围内，且为通信链路中距离网络设备最近的设备，那么，在一种可能的方式中，若某个终端设备位于网络设备的信号覆盖范围之外，和/或，非通信链路中距离网络设备最近的设备，则可认为该终端设备不满足第一条件；在另一种可能的方式中，若某个终端设备位于网络设备的信号覆盖范围之外，且非通信链路中距离网络设备最近的设备，则可认为该终端设备不满足第一条件。
应理解，上述几种示例可适用于本申请中涉及第一条件的各个实施例，为简洁，下文中不再赘述。
根据本实施例的方法，不满足第一条件的第一设备可通过RRC连接向不相邻且满足第一条件的第二设备发送第一信息，以请求针对第一设备的寻呼消息，和/或，第一设备所需的系统信息。由于满足第一条件的终端设备通常具备从网络设备获取寻呼消息和/或系统信息的能力，故满足第一条件的终端设备可基于该第一信息从网络设备获取第一设备所请求的信息(如针对第一设备的寻呼消息，和/或，第一设备所需的系统信息)，并将获取的信息转发至该第一设备。
在一些场景中，第二设备的数量可以为多个，也即，第一设备可向多个第二设备请求针对第一设备的寻呼消息，和/或，第一设备所需的系统信息。
在一些实施例中，第一设备为通信链路中满足第一条件的终端设备，第二设备为通信链路中不满足第一条件的终端设备，目标设备为网络设备，第一信息包括：针对第二设备的寻呼消息，和/或，第二设备所需的系统信息。
示例性地，第一条件可包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网络设备最近的设备；能够直接从网络设备获取寻呼消息和/或系统信息。
根据本实施例的方法，满足第一条件的第一设备可通过RRC连接向不相邻且不满足第一条件的第二设备发送第一信息，以向第二设备传达针对第二设备的寻呼消息，和/或，第二设备所需的系统信息。
在一些场景中，第二设备的数量可以为多个，也即，第一设备可向多个第二设备传达针对各个第二设备的寻呼消息，和/或，各个第二设备所需的系统信息。
在一种可能的方式中，在第一设备通过RRC连接向通信链路中的第二设备发送第一信息之前，该方法还可以包括：第一设备接收来自第二设备的第二信息，第二信息用于请求针对第二设备的寻呼消息，和/或，第二设备所需的系统信息。
其中，在第二信息用于请求针对第二设备的寻呼消息的情况下，第二信息可包括：为监听第二设备的寻呼消息所需的信息；在第二信息用于请求第二设备所需的系统信息的情况下，第二信息可包括：第二设备所需的系统信息的类型。也就是说，若第二设备向第一设备请求针对第二设备的寻呼消息，则第二设备可在第二信息中携带为监听该寻呼消息所需的信息，如第二设备的标识、监听时段等。若第二设备向第一设备请求第二设备所需的系统信息，则第二设备可在第二信息中携带该第二设备所需的系统信息的类型。
示例性地，在第二信息包括为监听第二设备的寻呼消息所需的信息的情况下，第一信息可包括：针对第二设备的寻呼消息；在第二信息包括第二设备所需的系统信息的类型的情况下，第一信息包括：第二设备所需的系统信息。也就是说，若第二设备在第二信息中携带了为监听针对第二设备的寻呼消息所需的信息，则说明第二设备向第一设备请求针对第二设备的寻呼消息，因此第一设备可将针对第二设备的寻呼消息携带于第一信息中发送至第二设备。若第二设备在第一信息中携带了第二设备所需的系统信息的类型，则说明第二设备向第一设备请求第二设备所需的系统信息，因此第一设备可将第二设备所需的系统信息携带于第一信息中发送至第二设备。
在一种可能的方式中，在第一设备通过RRC连接向通信链路中的第二设备发送第一信息之前，该方法还可以包括：基于为监听第二设备的寻呼消息所需的信息，从网络设备获取针对第二设备的寻呼消息；和/或，基于第二设备所需的系统信息的类型，从网络设备获取第二设备所需的系统信息。
举例来说，若第二设备在第二信息中携带了为监听针对第二设备的寻呼消息所需的信息，那么第一设备可基于为监听第二设备的寻呼消息所需的信息，从网络设备获取针对第二设备的寻呼消息，进而将获取的寻呼消息携带于第一信息中转发至第二设备。若第二设备在第二信息中携带了第二设备所需的系统信息的类型，那么第一设备可基于第二设备所需的系统信息的类型，从网络设备获取第二设备所需的系统信息，进而将获取的系统信息携带于第一信息中转发至第二设备。
在一些实施例中，第一设备和第二设备为通信链路中不同的终端设备，第一信息用于指示第一设备的无线链路状态，或者，用于指示第一设备发生网络连接状态改变或无线链路状态改变。
示例性地，无线链路状态可包括：无线链路失败(Radio Link Failure，RLF)；网络连接状态改变可包括：小区切换、小区重选或RRC连接状态改变；无线链路状态改变可包括：无线链路的链路质量下降。
根据本实施例的方法，第一设备可通过RRC连接向不相邻的第二设备发送第一信息，从而向第二设备指示该第一设备的无线链路状态，或指示该第一设备发生网络连接状态改变或无线链路状态改变。
在一些场景中，第二设备的数量可以为多个，也即，第一设备可向多个第二设备指示该第一设备的无线链路状态，或向多个第二设备指示该第一设备发生网络连接状态改变或无线链路状态改变。
在一些实施例中，第一设备和第二设备为通信链路中不同的终端设备，第一信息用于指示第二设备测量周围的无线通信情况。
示例性地，第一信息例如可指示第二设备测量信道繁忙比率(Channel Busy Ratio，CBR)，和/或第二设备与至少一个第三设备之间的链路质量。其中，第三设备例如可以是其他终端设备，或者还可以是网络设备。链路质量例如可包括RSRP。
作为一示例，第一设备可通过第一信息指示第二设备测量并报告CBR测量情况。
作为另一示例，第一设备还可以通过第一信息指示第二设备测量并报告第二设备与其他终端设备之间的链路质量，如第二设备与其他终端设备之间的侧行链路-参考信号接收功率(SL-RSRP)或侧行链路发现-参考信号接收功率(Sidelink Discovery-RSRP，SD-RSRP)。
作为又一示例，第一设备还可以通过第一信息指示第二设备测量并报告第二设备与网络设备之间的链路质量，如第二设备与网络设备之间的Uu-RSRP。
根据本实施例的方法，第一设备可通过RRC连接向不相邻的第二设备发送第一信息，以指示第二设备测量周围的无线通信情况。第二设备完成相应的测量后，可向第一设备反馈相应的测量结果，从而，第一设备可获知通信链路上没有直接相连的第二设备的链路情况。该测量结果可用于辅助第一设备做出下一步决策。例如，当测量结果显示第二设备与某个终端设备之间的链路质量较差时，第一设备可指示第二设备连接到其他候选终端设备。
在一些场景中，第二设备的数量可以为多个，也即，第一设备可指示多个第二设备测量周围的无线通信情况。
在一些实施例中，第一设备和第二设备为通信链路中不同的终端设备，第一信息用于指示第二设备与第四设备之间的服务质量QoS，其中，第二设备与第四设备在通信链路中相邻。
也就是说，第一设备可通过第一信息为第二设备配置该第二设备与相邻设备之间QoS，或者说，第一设备可通过跨跳的RRC连接为不相邻的终端设备(如第二设备)配置该终端设备所在的某一跳上的QoS。例如在图6中，中继终端设备#1(第一设备的一例)可通过与中继终端设备#3(第二设备的一例)之间的跨跳PC5-RRC连接，为中继终端设备#3配置第三跳和/或第四跳上的QoS。
作为一种实现方式，第二设备的数量可以为多个，也即，第一设备可通过RRC连接为多个不相邻的第二设备配置QoS。作为另一种实现方式，在第一设备与通信链路中所有终端设备之间均存在RRC连接的情况下，第一设备还可以通过RRC连接为通信链路中所有终端设备配置QoS，或者说，第一设备可配置每一跳上的单跳QoS，并通过RRC连接将配置的QoS发送至相应的终端设备。如此，第一设备可通过中心化的QoS分配方式，统筹规划整个通信链路上的QoS分配情况，从而有利于提升整个通信链路的通信性能。
示例性地，该第一设备例如可以为以下任一设备：源终端设备；目标设备；通信链路中与源终端设备距离最近的设备；通信链路中与目标设备距离最近的设备；基于预设规则确定的设备。其中，预设规则例如可由协议规定。例如，可规定将通信链路中能力最强的终端设备确定为第一设备；又例如，可规定将通信链路中处于连接态或处于网络覆盖范围内的终端设备确定为第一设备。在本实施例中，第一设备还可以称为中心终端设备，或者称为控制终端设备。
根据本实施例的方法，第一设备可通过跨跳的RRC连接为不相邻的终端设备配置该终端设备所在的某一跳上的QoS，从而可简化QoS分配方式，提高QoS分配的效率。
在一些实施例中，第一设备和第二设备为通信链路中不同的终端设备，第一信息用于配置第二设备的传输资源。
也就是说，第一设备可通过第一信息为第二设备配置传输资源。或者说，第一设备可通过跨跳的RRC连接为不相邻的终端设备(如第二设备)配置传输资源。
作为一种实现方式，第二设备的数量可以为多个，也即，第一设备可通过RRC连接为多个不相邻的第二设备配置传输资源。作为另一种实现方式，在第一设备与通信链路中所有终端设备之间均存在 RRC连接的情况下，第一设备还可以通过RRC连接为通信链路中所有终端设备配置传输资源。如此，可通过中心化的资源分配方式，达到减小时延的目的。
作为一个示例，第一设备为第二设备分配的传输资源，例如可以是第一设备从资源池中选取的。作为另一个示例，第一设备为第二设备分配的传输资源，还可以是目标设备分配的，进而由第一设备将目标设备为第二设备分配的传输资源发送至第二设备。其中，目标设备为网络设备。
示例性地，为第二设备分配传输资源的第一设备例如可以为以下任一设备：源终端设备；目标设备；通信链路中与源终端设备距离最近的设备；通信链路中与目标设备距离最近的设备；基于预设规则确定的设备。其中，预设规则例如可由协议规定。例如，可规定将通信链路中能力最强的终端设备确定为第一设备；又例如，可规定将通信链路中处于连接态或处于网络覆盖范围内的终端设备确定为第一设备。在本实施例中，第一设备还可以称为中心终端设备，或者称为控制终端设备。
根据本实施例的方法，第一设备可通过跨跳的RRC连接为不相邻的终端设备配置传输资源，从而可简化资源分配方式，提高资源分配的效率。
在一些实施例中，第一设备和第二设备为通信链路中不同的终端设备，第一信息为RRC重配消息，该RRC重配消息可包括以下至少一项：侧行中继适配协议(Sidelink Relay Adaptation Protocol，SRAP)配置、RLC配置、MAC配置。其中，SRAP配置包括：为第二设备分配的标识和/或通信链路中其他终端设备的标识。
也就是说，RRC重配消息可携带在跨跳的消息(第一信息)中。作为一种实现方式，第二设备的数量可以为多个，也即，第一设备可通过RRC连接向多个不相邻的第二设备发送RRC重配消息。
在一些实施例中，第一设备和第二设备为通信链路中不同的终端设备，在满足第二条件的情况下，第一设备与第二设备之间发生RLF。第二条件包括：第一设备和第二设备之间，任意两个相邻设备之间发生RLF；和/或，通信链路中的任意两个相邻设备之间发生RLF。
也就是说，跨跳的RRC连接发生RLF的原因可包括以下至少一项：
a.第一设备和第二设备之间，任意两个相邻设备之间发生RLF。
举例来说，假设第一设备和第二设备之间存在一个中继终端设备，那么，若第一设备与该中继终端设备之间发生RLF，和/或，第二设备与该中继终端设备之间发生RLF，则会导致第一设备与第二设备之间发生RLF。
b.通信链路中的任意两个相邻设备之间发生RLF。也即，通信链路中任意两个相邻设备之间发生RLF，均会导致第一设备与第二设备之间发生RLF。
在一些实施例中，第一设备和第二设备为通信链路中不同的终端设备，且第一设备和第二设备之间存在RRC连接，在满足第三条件的情况下，第一设备与第二设备之间的RRC连接释放。第三条件包括：第一设备和第二设备之间，任意两个相邻设备之间的RRC连接释放；和/或，通信链路中的任意两个相邻设备之间的RRC连接释放。
也就是说，跨跳的RRC连接释放的原因可包括以下至少一项：
a.第一设备和第二设备之间，任意两个相邻设备之间的RRC连接释放。
举例来说，假设第一设备和第二设备之间存在一个中继终端设备，那么，若第一设备与该中继终端设备之间的RRC连接释放，和/或，第二设备与该中继终端设备之间的RRC连接释放，则会导致第一设备与第二设备之间的RRC连接释放。
b.通信链路中的任意两个相邻设备之间的RRC连接释放。也即，通信链路中任意两个相邻设备之间的RRC连接释放，均会导致第一设备与第二设备之间的RRC连接释放。
在一些实施例中，第二设备为目标设备，且目标设备为网络设备，第一信息用于指示以下至少之一：第一设备发生无线链路失败；第一设备与至少一个第五设备之间的信道质量(如RSRP)；以及，通信链路中所有终端设备的标识。
也就是说，第一设备可通过跨跳的RRC连接向网络设备上报第一信息。其中，第一设备例如可以是源终端设备，或者也可以是某一个中继终端设备。
在一些实施例中，第二设备为目标设备，且目标设备为网络设备，第一设备的传输资源是由该网络设备通过RRC连接为第一设备配置的。
也就是说，网络设备(目标设备)可通过跨跳的RRC连接为第一设备分配传输资源。其中，第一设备例如可以是源终端设备，或者也可以是某一个中继终端设备。
作为一种实现方式，在网络设备和通信链路中的各个终端设备之间均存在RRC连接的情况下，网络设备可通过RRC连接为通信链路中的各个终端设备(包括直接连接和没有直接连接的终端设备)配置传输资源。
在一些实施例中，该方法还可以包括：第一设备通过RRC连接向通信链路中的第六设备发送第三 信息，第三信息与无线资源管理相关；其中，第六设备与第一设备在通信链路中相邻。
也就是说，在场景1中，第一设备除了可通过RRC连接向通信链路中不相邻的第二设备发送与无线资源管理相关的第一信息外，还可以通过RRC连接向通信链路中相邻的第六设备发送与无线资源管理相关的第三信息。
场景2：第二设备与第一设备在通信链路中相邻。
在一些实施例中，第一设备为通信链路中不满足第一条件的终端设备，目标设备为网络设备，第二设备为第一设备在上行方向的下一跳终端设备；第一信息用于请求针对第一设备的寻呼消息，和/或，第一设备所需的系统信息。
示例性地，在第一信息用于请求针对第一设备的寻呼消息的情况下，第一信息可包括：为监听第一设备的寻呼消息所需的信息；在第一信息用于请求第一设备所需的系统信息的情况下，第一信息可包括：第一设备所需的系统信息的类型。也就是说，若第一设备请求针对第一设备的寻呼消息，则第一设备可在第一信息中携带为监听该寻呼消息所需的信息，如第一设备的标识(ID)、监听时段等。若第一设备请求第一设备所需的系统信息，则第一设备可在第一信息中携带该第一设备所需的系统信息的类型。
示例性地，第一条件可包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网络设备最近的设备；能够直接从网络设备获取寻呼消息和/或系统信息。
根据本实施例的方法，不满足第一条件的第一设备可通过RRC连接向相邻的第二设备发送第一信息，以请求针对第一设备的寻呼消息，和/或，第一设备所需的系统信息。一种可能的情况，第二设备为不满足第一条件的终端设备(中继终端设备)，在该情况下，第二设备可将该第一信息继续向下一跳设备转发，也即，转发给第二设备在上行方向的下一跳终端设备，直到将该第一信息转发至满足第一条件的终端设备。另一种可能的情况，第二设备为满足第一条件的终端设备，在该情况下，第二设备可停止向下一跳设备转发该第一信息。
在一些实施例中，第一设备为通信链路中不满足第一条件的终端设备，目标设备为网络设备，第二设备为第一设备在上行方向的下一跳终端设备；第一信息用于请求针对第七设备的寻呼消息，和/或，第七设备所需的系统信息；第七设备在通信链路中为第一设备在上行方向的上一跳终端设备、源终端设备或第一设备与源终端设备之间的任一与第一设备存在RRC连接的设备。
作为一种实现方式，第七设备可将第一信息发送至第一设备，若第一设备不满足第一条件，则第一设备可将来自第七设备的第一信息转发至上行方向的下一跳终端设备(也即第二设备)。一种可能的情况，第二设备仍不满足第一条件，那么，第二设备可将该第一信息继续向下一跳设备转发，也即，转发给第二设备在上行方向的下一跳终端设备，直到将该第一信息转发至满足第一条件的终端设备。另一种可能的情况，第二设备满足第一条件，那么，第二设备可停止向下一跳设备转发该第一信息。
示例性地，在第一信息用于请求针对第七设备的寻呼消息的情况下，第一信息可包括：为监听第七设备的寻呼消息所需的信息；在第一信息用于请求第七设备所需的系统信息的情况下，第一信息可包括：第七设备所需的系统信息的类型。
示例性地，第一条件可包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网络设备最近的设备；能够直接从网络设备获取寻呼消息和/或系统信息。
在一种可能的方式中，在第一设备通过RRC连接向通信链路中的第二设备发送第一信息之前，该方法还可以包括：第一设备通过RRC连接，接收来自第七设备的第一信息。
在一种可能的方式中，在第一设备通过RRC连接向通信链路中的第二设备发送第一信息之前，该方法还可以包括：第一设备在第一信息中增加第二信息，第二信息用于请求针对第一设备的寻呼消息，和/或，第一设备所需的系统信息。也就是说，第一设备在向第二设备转发来自第七设备的第一信息之前，还可以在第一信息中增加第二信息。在该情况下，第一设备向第二设备发送的第一信息中，可同时包含用于请求针对第七设备的寻呼消息和/或第七设备所需的系统信息的信息(原第一信息的内容)，以及用于请求针对第一设备的寻呼消息和/或第一设备所需的系统信息的信息(新增的第二信息的内容)。
示例性地，在第二信息用于请求针对第一设备的寻呼消息的情况下，第二信息可包括：为监听第一设备的寻呼消息所需的信息；在第二信息用于请求第一设备所需的系统信息的情况下，第二信息可包括：第一设备所需的系统信息的类型。
在一些实施例中，目标设备为网络设备，第二设备为第一设备在下行方向的下一跳终端设备，或者，为第一设备与源终端设备之间的任一与第一设备存在RRC连接的终端设备。第一信息包括：针对第八设备的寻呼消息，和/或，第八设备所需的系统信息。
一种可能的情况，第八设备为第二设备。也即，第八设备为第一设备在下行方向的下一跳终端设备，且第一设备可通过RRC连接将针对该第八设备的寻呼消息和/或该第八设备所需的系统信息发送至该第八设备。
另一种可能的情况，第八设备为源终端设备，或者为第二设备与源终端设备之间的任一终端设备。也即，第一设备可通过RRC连接将针对第八设备的寻呼消息和/或第八设备所需的系统信息发送至第二设备。在一些实施例中，第二设备接收到针对第八设备的寻呼消息和/或第八设备所需的系统信息后，可将该信息转发至第八设备。例如，在第二设备与第八设备之间存在RRC连接的情况下，第二设备可通过RRC连接将该信息转发给第八设备。又例如，第二设备还可以通过逐跳转发的方式，将该信息逐跳转发至第八设备。在一种可能的方式中，“针对第八设备的寻呼消息和/或第八设备所需的系统信息”可能和“针对第二设备的寻呼消息和/或第二设备所需的系统信息”携带在同一信息中，在该情况下，第二设备在接收到该信息后，可先去掉该信息中包含的针对该第二设备的寻呼消息和/或该第二设备所需的系统信息，之后再将该信息发送至第八设备。
作为一个示例，在第一设备满足第一条件的情况下，第一信息可以是第一设备从网络设备获取的。示例性地，第一条件可包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网络设备最近的设备；能够直接从网络设备获取寻呼消息和/或系统信息。由于满足第一条件的终端设备通常具备从网络设备直接获取寻呼消息和/或系统信息的能力，故第一设备可从网络设备获取第八设备所请求的信息(如针对第八设备的寻呼消息，和/或，第八设备所需的系统信息)，并将获取的信息发送至第二设备，进而由第二设备转发至第八设备。
作为另一示例，在第一设备不满足上述第一条件的情况下，第一信息可以是第一设备从通信链路中的第九设备获取的。其中，第九设备例如可以是第一设备在下行方向的上一跳终端设备，或者，可以是第一设备与网络设备之间的任一与第一设备存在RRC连接的终端设备。由于不满足第一条件的终端设备通常不具备从网络设备直接获取寻呼消息和/或系统信息的能力，故第一设备需通过第九设备获取第八设备所请求的信息。示例性地，第八设备所请求的信息例如可以是第九设备从网络设备直接获取的(若第九设备满足第一条件)，或者可以是由满足第一条件的终端设备逐跳传输至第九设备的。
在一种可能的方式中，在第一设备通过RRC连接向通信链路中的第二设备发送第一信息之前，该方法还可以包括：第一设备通过第二设备接收来自第八设备的第四信息，第四信息用于请求针对第八设备的寻呼消息，和/或，第八设备所需的系统信息。在第四信息用于请求针对第八设备的寻呼消息的情况下，第四信息可包括：为监听第八设备的寻呼消息所需的信息；在第四信息用于请求第八设备所需的系统信息的情况下，第四信息可包括：第八设备所需的系统信息的类型。
也就是说，在第一设备向第二设备发送第八设备所请求的信息(针对第八设备的寻呼消息，和/或，第八设备所需的系统信息)之前，可先通过第二设备接收来自第八设备的请求信息(即第四信息)。
示例性地，在第四信息包括为监听第八设备的寻呼消息所需的信息的情况下，第一信息可包括：针对第八设备的寻呼消息；在第四信息包括第八设备所需的系统信息的类型的情况下，第一可信息包括：第八设备所需的系统信息。也就是说，若第四信息中携带了为监听针对第八设备的寻呼消息所需的信息，则说明第八设备请求针对第八设备的寻呼消息，因此可将针对第八设备的寻呼消息携带于第一信息中发送至第八设备。若第四信息中携带了第八设备所需的系统信息的类型，则说明第八设备请求第八设备所需的系统信息，因此可将第八设备所需的系统信息携带于第一信息中发送至第八设备。
在一些实施例中，第一信息用于指示第一设备的无线链路状态，或者，用于指示第一设备发生网络连接状态改变或无线链路状态改变。
示例性地，无线链路状态可包括：RLF；网络连接状态改变可包括：小区切换、小区重选或RRC连接状态改变；无线链路状态改变可包括：无线链路的链路质量下降。
根据本实施例的方法，第一设备可通过RRC连接向相邻的第二设备发送第一信息，从而向第二设备指示该第一设备的无线链路状态，或指示该第一设备发生网络连接状态改变或无线链路状态改变。
在一些场景中，第二设备可将该第一信息进一步向下一跳设备转发，以向下一跳设备通知该第一设备的无线链路状态，或者，通知该第一设备发生网络连接状态改变或无线链路状态改变。
在一些实施例中，第二设备为第一设备的下一跳终端设备，第一信息用于指示第十设备的无线链路状态，或者，用于指示第十设备发生网络连接状态改变或无线链路状态改变；其中，第十设备是第一设备的上一跳终端设备，或者，是通信链路中与第一设备不相邻的终端设备。
示例性地，第一设备例如可获取来自第十设备的第一信息，并可将该第一信息转发至下一跳终端设备(第二终端设备)。也即，第一设备可转发来自第十设备的第一信息。
一种可能的情况，来自第十设备的第一信息例如可以是第一设备通过RRC连接从第十设备获取的。另一种可能的情况，第十设备还可以通过逐跳转发的方式，将第一信息逐跳转发至第一设备，也即，第一信息可以是第一设备从上一跳终端设备获取的。
在一种可能的方式中，在第一设备通过RRC连接向通信链路中的第二设备发送第一信息之前，该方法还可以包括：第一设备在第一信息中增加第五信息，第五信息用于指示第一设备的无线链路状态， 或者，用于指示第一设备发生网络连接状态改变或无线链路状态改变。也就是说，第一设备在向第二设备转发来自第十设备的第一信息之前，还可以在第一信息中增加第五信息。在该情况下，第一设备向第二设备发送的第一信息中，可同时包含原第一信息的内容以及新增的第五信息的内容。其中，原第一信息用于指示第十设备的无线链路状态，或者，用于指示第十设备发生网络连接状态改变或无线链路状态改变；新增的第五信息用于指示第一设备的无线链路状态，或者，用于指示第一设备发生网络连接状态改变或无线链路状态改变。
示例性地，第五信息可包括以下信息中的至少之一：第一设备的标识；与第一设备的无线链路状态相关联的传输跳数的标识；以及，与第一设备发生网络连接状态改变或无线链路状态改变相关联的传输跳数的标识。
例如，假设无线链路状态包括RLF，那么，若第一设备所在的某一跳上发生RLF，则与第一设备的无线链路状态相关联的传输跳数的标识，即为该跳的标识。
又例如，假设网络连接状态改变包括RRC连接状态改变，那么，若第一设备所在的某一跳上的RRC连接状态改变，则与第一设备发生网络连接状态改变相关联的传输跳数的标识，即为该跳的标识。
类似地，第一信息还可以包括以下至少之一：第十设备的标识；与第十设备的无线链路状态相关联的传输跳数的标识；以及，与第十设备发生网络连接状态改变或无线链路状态改变相关联的传输跳数的标识。
在一些实施例中，第一信息可用于指示以下至少之一：第一设备与第二设备之间的QoS；第二设备可分配的QoS；以及，通信链路的传输跳数。其中，第二设备可分配的QoS，还可以理解为，除已分配的QoS之外，通信链路中剩余未分配的QoS。可以理解的是，通信链路中总共可被分配的QoS，即为源终端设备与目标设备之间的端到端的QoS。
在一种可能的方式中，在第一设备通过RRC连接向通信链路中的第二设备发送第一信息之前，该方法还可以包括：确定(分配)第一设备与第二设备之间的QoS。
举例来说，假设第一设备为图8中的源终端设备，第二设备为图8中的中继终端设备#1，那么，源终端设备可分配第一跳上的QoS(也即第一设备与第二设备之间的QoS)，并可将第一跳上的QoS和通信链路中剩余未分配的QoS(也即第二设备可分配的QoS)发送给中继终端设备#1，从而，中继终端设备#1可从剩余未分配的QoS中分配第二跳上的QoS，并将第二跳上的QoS和剩余未分配的QoS发送给中继终端设备#2，以此类推。
在一些场景中，第一信息还可以包括以下一项或多项信息，作为第二设备在进行QoS分配时的参考信息：通信链路的传输跳数、第二设备所在的传输跳数、剩余未被分配QoS的传输跳数。
在一些实施例中，第二设备为第一设备的下一跳终端设备，第一信息为第一设备与第二设备之间的RRC重配消息，RRC重配消息例如可包括以下至少一项：SRAP配置；RLC配置；以及MAC的配置。
作为一种实现方式，第一信息可以是第一设备确定的；或者，第一信息可以是第一设备基于与上一跳终端设备之间的RRC重配消息确定的。也就是说，某一终端设备与下一跳终端设备之间的RRC配置，可由本跳终端设备决定，或者由本跳终端设备根据与上一跳终端设备之间的RRC配置确定，也即，本跳终端设备需解码上一跳终端设备发给自己的RRC重配消息，并根据该RRC重配消息决定自己与下一跳终端设备之间的RRC配置。
在一些实施例中，第二设备为目标设备，且目标设备为网络设备，第一信息用于指示以下至少之一：第十一设备发生无线链路失败；第十一设备与至少一个第十二设备之间的信道质量；第十一设备的标识；以及，第十一设备与网络设备之间的传输跳数。其中，第十一设备为通信链路中与网络设备之间不存RRC连接的终端设备。
也就是说，处于连接态的终端设备(如第一设备)可通过RRC连接向网络设备报告处于非连接态的终端设备(如第十一设备)的相关信息，以使得网络设备可获知非连接态的终端设备的相关情况。
在一些实施例中，该方法还可以包括：第一设备通过RRC连接向通信链路中的第十三设备发送第六信息，第六信息与无线资源管理相关；其中，第十三设备与第一设备在通信链路中不相邻。
也就是说，在场景2中，第一设备除了可通过RRC连接向通信链路中相邻的第二设备发送与无线资源管理相关的第一信息外，还可以通过RRC连接向通信链路中不相邻的第十三设备发送与无线资源管理相关的第六信息。
需要说明的是，本申请实施例中的通信链路例如可具有以下特征中的至少之一：
通信链路中所有相邻的设备之间存在RRC连接；通信链路中的部分或全部不相邻的设备之间存在RRC连接；在目标设备为网络设备的情况下，通信链路中的部分或全部终端设备与网络设备之间存在RRC连接；在目标设备为网络设备的情况下，通信链路中距离网络设备最近的终端设备，与其他全部或部分设备之间存在RRC连接；通信链路中的部分或全部设备与第十四设备之间存在RRC连接。
其中，第十四设备例如可以为以下任一设备：源终端设备；目标设备；通信链路中与源终端设备距离最近的设备；通信链路中与目标设备距离最近的设备；基于预设规则确定的设备。其中，预设规则例如可由协议规定。例如，可规定将通信链路中能力最强的终端设备确定为第十四设备；又例如，可规定将通信链路中处于连接态或处于网络覆盖范围内的终端设备确定为第十四设备。第十四设备还可以称为中心终端设备，或者称为控制终端设备。
在一些实施例中，第一设备是否与其他设备建立RRC连接，可以由第一设备或网络设备确定。也就是说，第一设备可基于该第一设备的自身实现或基于网络配置选择与其他设备创建RRC连接或不创建RRC连接。
在一些实施例中，上述第一信息例如可通过以下一项或多项进行识别：RLC信道；承载标识(bearer ID)；逻辑信道(Logical Channel，LCH)。也即，终端设备(如第二设备)可通过RLC信道、承载标识、LCH中的一项或多项识别第一信息。
根据上述场景1和场景2中的方法，通信链路中的第一设备可通过RRC连接向第二设备发送与无线资源管理相关的信息，从而实现了多跳中继场景下的无线资源管理过程，或者说，实现了多跳中继场景下的控制面流程。
上文介绍了本申请实施例提供的一种无线资源管理方法。为便于理解本申请的实施例，下面结合图6至图9介绍适用于本申请实施例的无线资源管理方法的可能的实现流程。
在图6和图8中，目标设备例如可以为目标终端设备，该通信链路中可包括源终端设备、目标终端设备，以及源终端设备和目标终端设备之间的多个中继终端设备(中继终端设备#1至中继终端设备#3)。也即，图6和图8可适用于多跳U2U中继场景。
在图7和图9中，目标设备例如可以为网络设备，该通信链路中可包括源终端设备、网络设备，以及源终端设备和网络设备之间的多个中继终端设备(中继终端设备#1至中继终端设备#3)。也即，图7和图9可适用于多跳U2N中继场景。
作为多跳中继场景下的网络连接方式的一个示例，在图6和图7中，所有非相邻节点(设备)之间均存在RRC连接。例如，源终端设备和不相邻的中继终端设备#2之间，以及和不相邻的中继终端设备#3之间，分别存在PC5-RRC连接。又例如在图6中，中继终端设备#1和不相邻的中继终端设备#3之间，以及和不相邻的目标终端设备之间，分别存在PC5-RRC连接。需要说明的是，图6和图7中相邻节点之间也存在RRC连接(图6和图7中未予以画出)。例如在图6中，第一跳、第二跳、第三跳和第四跳均存在PC5-RRC连接。又例如在图7中，第一跳、第二跳和第三跳均存在PC5-RRC连接，第四跳存在Uu-RRC连接。还需要说明的是，由于源终端设备与目标设备(如图6中的目标终端设备；又如图7中的网络设备)之间存在业务传输，故源终端设备与目标设备之间也存在RRC连接(图6和图7中未予以画出)。
在图6和图7中，对于通过PC5-RRC连接的各个设备，可实现的流程包括：
1)RRC重配流程：
在一种可能的方式中，RRC重配消息可携带在跨跳(跨-hop)的消息中。例如在图6和图7中，源终端设备可通过与中继终端设备#2之间的跨跳PC5-RRC连接，将RRC重配消息发送至中继终端设备#2；又例如在图6中，中继终端设备#2可通过与目标终端设备之间的跨跳PC5-RRC连接，将RRC重配消息发送至目标终端设备。
在另一种可能的方式中，RRC重配消息可不携带在跨跳的消息中，而是由每跳(per-hop)的信令配置。例如，源终端设备可通过与中继终端设备#1之间的PC5-RRC连接，将RRC重配消息发送至中继终端设备#1；又例如，中继终端设备#1可通过与中继终端设备#2之间的PC5-RRC连接，将RRC重配消息发送至中继终端设备#2；再例如在图6中，中继终端设备#3可通过与目标终端设备之间的PC5-RRC连接，将RRC重配消息发送至目标终端设备。
需要说明的是，上述RRC重配流程可由通信链路中的任一终端设备执行。例如，可由源终端设备、目标终端设备或任一中继终端设备执行，本申请实施例对此不予限定。
示例性地，RRC重配消息例如可包括以下至少一项：SRAP配置、RLC配置、MAC配置。其中，SRAP层中UE-ID和承载(bearer)ID的配置可包括：为当前UE(也即接收RRC重配消息的UE)分配的UE-ID以及整个链路上的其他UE的UE-ID。
2)无线链路失败(RLF)流程：
一示例，跨跳的PC5-RRC无线链路失败的原因可包括：中间经过的一跳或多跳发生无线链路失败。例如，若第一跳和/或第二跳发生无线链路失败，则源终端设备和中继终端设备#2之间的PC5-RRC无线链路失败；又例如在图6中，若第三跳和/或第四跳发生无线链路失败，则中继终端设备#2和目标终端设备之间的PC5-RRC无线链路失败。
另一示例，跨跳的PC5-RRC无线链路失败的原因可包括：通信链路中的任意两个相邻设备之间发生无线链路失败。例如，中继终端设备#1和中继终端设备#3之间的PC5-RRC无线链路失败，可以是由于通信链路中的任意两个相邻设备之间发生无线链路失败导致的。例如，可能是由于源终端设备和中继终端设备#1之间(也即第一跳)发生无线链路失败导致的。
3)PC5-RRC连接释放流程：
一示例，跨跳的PC5-RRC连接释放的原因可包括：中间经过的一跳或多跳发生PC5-RRC连接释放。例如，若第一跳和/或第二跳发生PC5-RRC连接释放，则源终端设备和中继终端设备#2之间的PC5-RRC连接释放；又例如在图6中，若第三跳和/或第四跳发生PC5-RRC连接释放，则中继终端设备#2和目标终端设备之间的PC5-RRC连接释放。
另一示例，跨跳的PC5-RRC连接释放的原因可包括：另一侧的任意一跳或多跳发生PC5-RRC连接释放。例如，对于中继终端设备#2，在第三跳和/或第四跳发生PC5-RRC连接释放的情况下，也会导致源终端设备和中继终端设备#2之间的PC5-RRC连接释放。
又一示例，跨跳的PC5-RRC连接释放的原因可包括：通信链路中的任意两个相邻设备之间发生PC5-RRC连接释放。例如，中继终端设备#1和中继终端设备#3之间的PC5-RRC连接释放，可以是由于通信链路中的任意两个相邻设备之间发生PC5-RRC连接释放导致的。例如，可能是由于源终端设备和中继终端设备#1之间(也即第一跳)发生PC5-RRC连接释放导致的。
4)寻呼信息和/或系统信息的请求流程(适用于多跳U2N中继场景，如图7所示的场景)：
在该流程中，通信链路中的某个终端设备(例如记为终端设备#1)可向存在RRC连接的另一终端设备(例如记为终端设备#2)发送请求消息，用于请求针对该终端设备#1的寻呼消息和/或该终端设备#1所需的系统信息。该请求消息例如可以为远端终端信息(Remote UE Information)。
作为一个示例，每一跳终端设备(如终端设备#1)可通过RRC连接直接将该请求消息发送给满足第一条件的另一终端设备，以请求针对该终端设备(终端设备#1)的寻呼消息和/或该终端设备所需的系统信息(如SIB)。
作为另一示例，每一跳终端设备(如终端设备#1)可在任意跳RRC消息中携带该请求消息，若收到该请求消息的中继终端设备不满足第一条件，则收到该请求消息的中继终端设备需继续向前转发/发送，最终将该请求消息转发至满足第一条件的终端设备。
示例性地，第一条件可包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网络设备最近的设备；能够直接从网络设备获取寻呼消息和/或系统信息。
应理解，上述终端设备#1例如可以是源终端设备，或者还可以是某个中继终端设备(如不满足第一条件的某个中继终端设备)，本申请实施例对此不予限定。
5)寻呼信息和/或系统信息的下发流程(适用于多跳U2N中继场景，如图7所示的场景)：
在4)中，终端设备#1可向终端设备#2发送请求消息，以请求针对该终端设备#1的寻呼消息和/或该终端设备#1所需的系统信息。在5)中，通信链路中的某一终端设备(如满足上述第一条件的终端设备)可基于该请求消息，从网络设备获取终端设备#1所请求的信息，并将终端设备#1所请求的信息下发至该终端设备#1。
作为一个示例，满足第一条件的终端设备在获取终端设备#1所请求的信息之后，可将终端设备#1所请求的信息直接通过PC5-RRC消息(或者说通过PC5-RRC连接)发送至终端设备#1。
作为另一个示例，满足第一条件的终端设备在获取终端设备#1所请求的信息之后，可将终端设备#1所请求的信息逐跳传输，直至传输至终端设备#1。
6)通知消息(Notification Message)的传输流程：
在该流程中，可由触发通知消息发送的终端设备通过PC5-RRC，将该通知消息发送至通信链路中的每一个终端设备。
例如在图6中，若中继终端设备#3触发通知消息发送，则中继终端设备#3可通过PC5-RRC连接，将该通知消息发送至源终端设备、中继终端设备#1、中继终端设备#2和目标终端设备。该通知消息可用于指示中继终端设备#3的无线链路状态(如RLF)，或者，用于指示中继终端设备#3发生网络连接状态改变(如小区切换、小区重选或RRC连接状态改变)或无线链路状态改变(如无线链路的链路质量下降)。
应理解，触发通知消息发送的终端设备可以是通信链路中的任一终端设备。例如，可以是源终端设备、目标终端设备或任一中继终端设备，本申请实施例对此不予限定。
7)测量流程：
在本申请实施例中，通信链路中的某个终端设备(例如记为终端设备#1)可向存在RRC连接的另一终端设备(例如记为终端设备#2)发送指示信息，用于指示终端设备#2测量周围的无线通信情况。
一示例，终端设备#1可配置终端设备#2测量并报告终端设备#2与其他终端设备之间的链路情况，如终端设备#2与其他终端设备之间的SL/SD-RSRP。
另一示例，终端设备#1还可以配置终端设备#2测量并报告终端设备#2与网络设备之间的链路情况，如终端设备#2与网络设备之间的Uu-RSRP。
再一示例，终端设备#1还可以配置终端设备#2测量并报告CBR测量情况。
应理解，上述终端设备#1可以是通信链路中的任一终端设备。例如，可以是源终端设备、目标终端设备或任一中继终端设备，本申请实施例对此不予限定。
8)QoS分割(Split)流程：
该流程例如可以由确定/定义的中心终端设备(或者称为控制终端设备)执行。中心终端设备例如可以确定/定义为以下任一终端设备：源终端设备；目标终端设备；通信链路中与源终端设备距离最近的设备；通信链路中与目标终端设备距离最近的设备；基于预设规则确定的设备。其中，预设规则例如可由协议规定。例如，可规定将通信链路中能力最强的终端设备确定为中心终端设备；又例如，可规定将通信链路中处于连接态或处于网络覆盖范围内的终端设备确定为中心终端设备。
在该流程中，中心终端设备可通过跨跳的RRC连接配置非所在跳上的分割QoS(单跳QoS)。例如在图6中，中继终端设备#2可通过与目标终端设备之间的跨跳PC5-RRC连接，配置第四跳上的单跳QoS，也即中继终端设备#3和目标终端设备之间的QoS。
9)资源分配流程：
该流程可由通信链路中的其中一个终端设备(如上述中心终端设备)执行。
以该流程由中心终端设备执行为例，中心终端设备可通过RRC消息，为当前通信链路中的所有终端设备配置传输资源。如此，通过中心化的资源分配方式，可达到减小时延的目的。其中，该中心终端设备通过中心化的方式分配的资源例如可基于前述第一模式或第二模式获取。
在图7中，对于通过Uu-RRC连接的各个设备，可实现的流程包括：
1)侧行终端设备信息(Sidelink UE Information)的上报流程：
在该流程中，各个终端设备可通过Uu-RRC连接向网络设备上报以下内容中的至少之一：该终端设备发生RLF、测量报告(如该终端设备与其他终端设备之间的信道质量)、该通信链路中所有终端设备的标识等。
2)资源分配流程：
在该流程中，网络设备可通过RRC消息为各个终端设备(包括没有直接连接的终端设备)配置第一模式下的传输资源。
作为多跳中继场景下的网络连接方式的另一示例，在图8和图9中，非相邻节点之间(不包括源终端设备和目标设备之间)均不存在RRC连接，相邻节点之间存在RRC连接。例如在图8中，第一跳、第二跳、第三跳和第四跳均存在PC5-RRC连接。又例如在图9中，第一跳、第二跳和第三跳均存在PC5-RRC连接，第四跳存在Uu-RRC连接。需要说明的是，由于源终端设备与目标设备(如图8中的目标终端设备；又如图9中的网络设备)之间存在业务传输，故源终端设备与目标设备之间也存在RRC连接。
在图8和图9中，对于通过PC5-RRC连接的各个设备，可实现的流程包括：
1)RRC重配流程：
在该流程中，每一跳的配置可由本跳终端设备决定，或由本跳终端设备根据上一跳配置决定，即本跳终端设备需解码上一跳终端设备发给自己的配置，并根据该配置决定自己的配置。
以图7中的中继终端设备#1为例，在第一种可能的方式中，中继终端设备#1可自主确定第二跳上的配置(也即中继终端设备#1和中继终端设备#2之间的配置)；在第二种可能的方式中，中继终端设备#1可接收并解码来自源终端设备的RRC重配消息，并基于该RRC重配消息确定第二跳上的配置。
2)寻呼信息和/或系统信息的请求流程(适用于多跳U2N中继场景，如图9所示的场景)：
在该流程中，通信链路中的某个终端设备(例如记为终端设备#1)可向相邻的终端设备(例如记为终端设备#2)发送请求消息，用于请求针对该终端设备#1的寻呼消息和/或该终端设备#1所需的系统信息。该请求消息例如可以为远端终端信息(Remote UE Information)。
作为一个示例，每一跳终端设备(如终端设备#1)可将自己的请求消息发送给下一跳终端设备(如终端设备#2)。若收到该请求消息的终端设备#2不满足第一条件，则终端设备#2可将该请求消息继续向前(或者说向下一跳)转发/发送，并可在该请求消息中增加该终端设备#2自身的请求消息，以请求针对该终端设备#2的寻呼消息和/或该终端设备#2所需的系统信息。若收到该请求消息的终端设备满足第一条件，则可停止向前转发/发送。
示例性地，第一条件可包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网 络设备最近的设备；能够直接从网络设备获取寻呼消息和/或系统信息。
应理解，上述终端设备#1例如可以是源终端设备，或者还可以是某个中继终端设备(如不满足第一条件的某个中继终端设备)，本申请实施例对此不予限定。
3)寻呼信息和/或系统信息的下发流程(适用于多跳U2N中继场景，如图9所示的场景)：
在该流程中，每一跳终端设备可将自己收到的寻呼消息和/或系统信息解码，并将包括后续该通信链路的其他终端设备所请求的寻呼消息和/或系统信息继续向后发送。
以图9为例，假设中继终端设备#3从网络设备获取的信息包括：中继终端设备#3、中继终端设备#2和中继终端设备#1所请求的寻呼消息和系统信息，那么，中继终端设备#3可将获取的信息解码后，将中继终端设备#2和中继终端设备#1所请求的寻呼消息和系统信息发送至中继终端设备#2。进一步地，中继终端设备#2可将来自中继终端设备#3的信息解码后，将中继终端设备#1所请求的寻呼消息和系统信息发送至中继终端设备#1。
4)通知消息(Notification Message)的传输流程：
在该流程中，可由触发通知消息发送的终端设备通过PC5-RRC连接，将该通知消息发送至与其直连的终端设备，并由收到该通知消息的终端设备继续向后(向下一跳)转发。
在一些实施例中，收到该通知消息的终端设备还可以进一步在该消息中增加自己的通知信息(若被触发)，并在该通知消息中携带触发该消息发送的终端设备的标识，和/或，与触发该消息发送相关联的传输跳数的标识(或者称为hop标识/hop等级(level))。例如，若触发该消息发送的原因为某一跳发送RLF，那么，与触发该消息发送相关联的传输跳数的标识即为该跳的标识。
例如在图8中，若中继终端设备#3触发通知消息发送，则中继终端设备#3可通过PC5-RRC连接，将该通知消息发送至与其直连的中继终端设备#2和目标终端设备，该通知消息中例如可携带中继终端设备#3的标识，和/或，与触发中继终端设备#3发送该通知消息相关联的传输跳数的标识。中继终端设备#2在收到该通知消息后，可在该通知消息中增加自己的通知消息，并在该通知消息中携带中继终端设备#2的标识，和/或，与触发中继终端设备#2发送该通知消息相关联的传输跳数的标识。进一步地，中继终端设备#2可将中继终端设备#3和中继终端设备#2的通知消息发送至中继终端设备#1。
应理解，触发通知消息发送的终端设备可以是通信链路中的任一终端设备。例如，可以是源终端设备、目标终端设备或任一中继终端设备，本申请实施例对此不予限定。
该通知消息可用于指示触发该通知消息发送的终端设备的无线链路状态(如RLF)，或者，用于指示该终端设备发生网络连接状态改变(如小区切换、小区重选或RRC连接状态改变)或无线链路状态改变(如无线链路的链路质量下降)。
5)QoS分割(Split)流程：
在该流程中，每个终端设备可分配自己所在跳上的QoS。在一些实施例中，每个终端设备还可以将自己所在跳的QoS和剩余未分配的QoS发送给下一跳终端设备，以便于下一跳终端设备进一步分配该下一跳终端设备所在跳上的QoS。
一示例，在图8和图9中，中继终端设备#1可分配第一跳上的QoS，并可将剩余未分配的QoS发送给中继终端设备#2，从而，中继终端设备#2可从剩余未分配的QoS中分配第二跳上的QoS，并将剩余未分配的QoS发送给中继终端设备#3，以此类推。
另一示例，在图8和图9中，源终端设备可分配第一跳上的QoS，并可将第一跳上的QoS和剩余未分配的QoS发送给中继终端设备#1，从而，中继终端设备#1可从剩余未分配的QoS中分配第二跳上的QoS，并将第二跳上的QoS和剩余未分配的QoS发送给中继终端设备#2，以此类推。
在一些实施例中，通过上述方式进行QoS分割，还需要每个终端设备获取以下一项或多项信息：
a.该通信链路上的传输跳数。例如在图8和图9中，传输跳数为4跳。
b.当前终端设备所在的传输跳数。例如在图8和图9中，中继终端设备#1所在的传输跳数为第一跳；中继终端设备#2所在的跳数传输为第二跳。
c.剩余未被分配QoS的传输跳数。例如在图8和图9中，源终端设备分配第一跳上的QoS后，剩余未被分配QoS的传输跳数为3跳。从而，源终端设备可将第一跳上的QoS和剩余未分配的QoS发送给中继终端设备#1，同时还可以将剩余未被分配QoS的传输跳数(3跳)告知给中继终端设备#1，以便于中继终端设备#1基于剩余未分配的QoS以及剩余未被分配QoS的传输跳数进行下一步的QoS分割。
d.与CBR相关的信息。
在图9中，对于通过Uu-RRC连接的各个设备，可实现的流程包括：
1)侧行终端设备信息(Sidelink UE Information)的上报流程：
在该流程中，处于连接态的终端设备可通过Uu-RRC连接，向网络设备报告该通信链路上所有非连接态的终端设备的以下一项或多项信息：
非连接态的终端设备发生RLF、非连接态的终端设备的测量报告(如非连接态的终端设备与其他终端设备之间的信道质量)、非连接态的终端设备的标识(L2ID)、非连接态的终端设备与网络设备之间的传输跳数。
本申请实施例设计了多跳U2U/U2N中继场景下的控制面流程，实现了多跳中继场景下的RRM。
需要说明的是，图7至图9中的网络连接方式仅为便于理解进行的举例。在本申请实施例的多跳中继场景下，可能的连接方式还可以包括以下至少之一：
在目标设备为网络设备的情况下，也即，在多跳U2N中继场景下，通信链路中的部分或全部终端设备与网络设备之间存在Uu-RRC连接；
在目标设备为网络设备的情况下，也即，在多跳U2N中继场景下，通信链路中距离网络设备最近的终端设备，与其他全部或部分终端设备之间存在PC5-RRC连接；
通信链路中的部分或全部设备与确定/定义的中心终端设备(或者称为控制终端设备)之间存在RRC连接。
在一些实施例中，还可以基于UE实现或网络配置选择创建RRC连接或不创建。或者说，某一终端设备是否与其他设备建立RRC连接，可以由该终端设备或网络设备确定的。
还需要说明的是，在本申请实施例的各个网络连接方式中，若非相邻节点之间存在RRC连接，则可适用于上述图6和图7对应的流程；若非相邻节点之间不存在RRC连接，则可适用于上述图8和图9对应的流程。
还需要说明的是，在多跳U2N中继中，若中继终端和网络设备之间不存在RRC连接，则表示支持空闲状态(IDLE)/非活跃状态(INACTIVE)终端作为中继终端为远端终端传输数据。
以上结合附图详细描述了本申请的优选实施方式，但是，本申请并不限于上述实施方式中的具体细节，在本申请的技术构思范围内，可以对本申请的技术方案进行多种简单变型，这些简单变型均属于本申请的保护范围。例如，在上述具体实施方式中所描述的各个具体技术特征，在不矛盾的情况下，可以通过任何合适的方式进行组合，为了避免不必要的重复，本申请对各种可能的组合方式不再另行说明。又例如，本申请的各种不同的实施方式之间也可以进行任意组合，只要其不违背本申请的思想，其同样应当视为本申请所公开的内容。又例如，在不冲突的前提下，本申请描述的各个实施例和/或各个实施例中的技术特征可以和现有技术任意的相互组合，组合之后得到的技术方案也应落入本申请的保护范围。
还应理解，在本申请的各种方法实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。此外，在本申请实施例中，术语“下行”、“上行”和“侧行”用于表示信号或数据的传输方向，其中，“下行”用于表示信号或数据的传输方向为从站点发送至小区的用户设备的第一方向，“上行”用于表示信号或数据的传输方向为从小区的用户设备发送至站点的第二方向，“侧行”用于表示信号或数据的传输方向为从用户设备1发送至用户设备2的第三方向。例如，“下行信号”表示该信号的传输方向为第一方向。另外，本申请实施例中，术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系。具体地，A和/或B可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
基于前述的实施例，本申请实施例提供相应的无线资源管理装置。
图10是本申请实施例提供的无线资源管理装置的结构组成示意图，应用于第一设备。无线资源管理装置1000所在的通信链路中包括源终端设备、目标设备，以及源终端设备和目标设备之间的多个中继终端设备。如图10所示，无线资源管理装置1000(以下简称为装置1000)包括：
第一发送单元1001，用于通过无线资源控制RRC连接向通信链路中的第二设备发送第一信息，第一信息与无线资源管理相关。
在一些实施例中，第二设备与装置1000在通信链路中不相邻。
在一些实施例中，装置1000为通信链路中不满足第一条件的终端设备，第二设备为通信链路中满足第一条件的终端设备，目标设备为网络设备；第一信息用于请求针对装置1000的寻呼消息，和/或，装置1000所需的系统信息；第一条件包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网络设备最近的设备；以及，能够直接从网络设备获取寻呼消息和/或系统信息。
在一些实施例中，在第一信息用于请求针对装置1000的寻呼消息的情况下，第一信息包括：为监听装置1000的寻呼消息所需的信息；在第一信息用于请求装置1000所需的系统信息的情况下，第一信息包括：装置1000所需的系统信息的类型。
在一些实施例中，装置1000为通信链路中满足第一条件的终端设备，第二设备为通信链路中不满足第一条件的终端设备，目标设备为网络设备；第一信息包括：针对第二设备的寻呼消息，和/或，第二设备所需的系统信息；第一条件包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中 距离网络设备最近的设备；以及，能够直接从网络设备获取寻呼消息和/或系统信息。
在一些实施例中，装置1000还包括第一接收单元，用于在通过RRC连接向通信链路中的第二设备发送第一信息之前，接收来自第二设备的第二信息，第二信息用于请求针对第二设备的寻呼消息，和/或，第二设备所需的系统信息；在第二信息用于请求针对第二设备的寻呼消息的情况下，第二信息包括：为监听第二设备的寻呼消息所需的信息；在第二信息用于请求第二设备所需的系统信息的情况下，第二信息包括：第二设备所需的系统信息的类型。
在一些实施例中，在第二信息包括为监听第二设备的寻呼消息所需的信息的情况下，第一信息包括：针对第二设备的寻呼消息；在第二信息包括第二设备所需的系统信息的类型的情况下，第一信息包括：第二设备所需的系统信息。
在一些实施例中，装置1000还包括第一获取单元，用于在通过RRC连接向通信链路中的第二设备发送第一信息之前，基于为监听第二设备的寻呼消息所需的信息，从网络设备获取针对第二设备的寻呼消息；和/或，基于第二设备所需的系统信息的类型，从网络设备获取第二设备所需的系统信息。
在一些实施例中，装置1000和第二设备为通信链路中不同的终端设备；第一信息用于指示装置1000的无线链路状态，或者，用于指示装置1000发生网络连接状态改变或无线链路状态改变。
在一些实施例中，装置1000和第二设备为通信链路中不同的终端设备；第一信息用于指示第二设备测量信道繁忙比率，和/或第二设备与至少一个第三设备之间的链路质量。
在一些实施例中，链路质量包括：参考信号接收功率。
在一些实施例中，装置1000和第二设备为通信链路中不同的终端设备；第一信息用于指示第二设备与第四设备之间的服务质量QoS；其中，第二设备与第四设备在通信链路中相邻。
在一些实施例中，装置1000和第二设备为通信链路中不同的终端设备；第一信息用于配置第二设备的传输资源。
在一些实施例中，第二设备的传输资源是装置1000从资源池中选取的，或者，是目标设备分配的，目标设备为网络设备。
在一些实施例中，装置1000为以下任一设备：源终端设备；目标设备；通信链路中与源终端设备距离最近的设备；通信链路中与目标设备距离最近的设备；基于预设规则确定的设备。
在一些实施例中，装置1000和第二设备为通信链路中不同的终端设备；第一信息为RRC重配消息，RRC重配消息包括以下至少一项：侧行中继适配协议SRAP配置；无线链路控制配置；以及媒体接入控制配置；其中，SRAP配置包括：为第二设备分配的标识和/或通信链路中其他终端设备的标识。
在一些实施例中，装置1000和第二设备为通信链路中不同的终端设备；在满足第二条件的情况下，装置1000与第二设备之间发生无线链路失败；第二条件包括：装置1000和第二设备之间，任意两个相邻设备之间发生无线链路失败；或者，通信链路中的任意两个相邻设备之间发生无线链路失败。
在一些实施例中，装置1000和第二设备为通信链路中不同的终端设备，且装置1000和第二设备之间存在RRC连接；在满足第三条件的情况下，装置1000与第二设备之间的RRC连接释放；第三条件包括：装置1000和第二设备之间，任意两个相邻设备之间的RRC连接释放；或者，通信链路中的任意两个相邻设备之间的RRC连接释放。
在一些实施例中，目标设备为网络设备或终端设备。
在一些实施例中，第二设备的数量为一个或多个。
在一些实施例中，第二设备为目标设备，且目标设备为网络设备；第一信息用于指示以下至少之一：装置1000发生无线链路失败；装置1000与至少一个第五设备之间的信道质量；以及，通信链路中所有终端设备的标识。
在一些实施例中，第二设备为目标设备，且目标设备为网络设备；装置1000的传输资源，是由网络设备通过RRC连接为装置1000配置的。
在一些实施例中，装置1000还包括第二发送单元，用于通过RRC连接向通信链路中的第六设备发送第三信息，第三信息与无线资源管理相关；其中，第六设备与装置1000在通信链路中相邻。
在一些实施例中，第二设备与装置1000在通信链路中相邻。
在一些实施例中，装置1000为通信链路中不满足第一条件的终端设备，目标设备为网络设备，第二设备为装置1000在上行方向的下一跳终端设备；第一信息用于请求针对装置1000的寻呼消息，和/或，装置1000所需的系统信息；第一条件包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网络设备最近的设备；以及，能够直接从网络设备获取寻呼消息和/或系统信息。
在一些实施例中，在第一信息用于请求针对装置1000的寻呼消息的情况下，第一信息包括：为监听装置1000的寻呼消息所需的信息；在第一信息用于请求装置1000所需的系统信息的情况下，第一信息包括：装置1000所需的系统信息的类型。
在一些实施例中，装置1000为通信链路中不满足第一条件的终端设备，目标设备为网络设备，第二设备为装置1000在上行方向的下一跳终端设备；第一信息用于请求针对第七设备的寻呼消息，和/或，第七设备所需的系统信息；第七设备在通信链路中为装置1000在上行方向的上一跳终端设备、源终端设备或装置1000与源终端设备之间的任一与装置1000存在RRC连接的设备；第一条件包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网络设备最近的设备；以及，能够直接从网络设备获取寻呼消息和/或系统信息。
在一些实施例中，在第一信息用于请求针对第七设备的寻呼消息的情况下，第一信息包括：为监听第七设备的寻呼消息所需的信息；在第一信息用于请求第七设备所需的系统信息的情况下，第一信息包括：第七设备所需的系统信息的类型。
在一些实施例中，装置1000还包括第二接收单元，用于在通过RRC连接向通信链路中的第二设备发送第一信息之前，通过RRC连接，接收来自第七设备的第一信息。
在一些实施例中，装置1000还包括第一处理单元，用于在通过RRC连接向通信链路中的第二设备发送第一信息之前，在第一信息中增加第二信息，第二信息用于请求针对装置1000的寻呼消息，和/或，装置1000所需的系统信息。
在一些实施例中，在第二信息用于请求针对装置1000的寻呼消息的情况下，第二信息包括：为监听装置1000的寻呼消息所需的信息；在第二信息用于请求装置1000所需的系统信息的情况下，第二信息包括：装置1000所需的系统信息的类型。
在一些实施例中，第二设备为通信链路中满足第一条件的终端设备。
在一些实施例中，目标设备为网络设备，第二设备为装置1000在下行方向的下一跳终端设备，或者，为装置1000与源终端设备之间的任一与装置1000存在RRC连接的终端设备；第一信息包括：针对第八设备的寻呼消息，和/或，第八设备所需的系统信息；其中，第八设备为第二设备、源终端设备或第二设备与源终端设备之间的任一终端设备。
在一些实施例中，在装置1000满足第一条件的情况下，第一信息是装置1000从网络设备获取的；在装置1000不满足第一条件的情况下，第一信息是装置1000从通信链路中的第九设备获取的；第九设备为装置1000在下行方向的上一跳终端设备，或者，为装置1000与网络设备之间的任一与装置1000存在RRC连接的终端设备；第一条件包括以下至少之一：位于网络设备的信号覆盖范围内；为通信链路中距离网络设备最近的设备；以及，能够直接从网络设备获取寻呼消息和/或系统信息。
在一些实施例中，装置1000还包括第三接收单元，用于在通过RRC连接向通信链路中的第二设备发送第一信息之前，通过第二设备接收来自第八设备的第四信息，第四信息用于请求针对第八设备的寻呼消息，和/或，第八设备所需的系统信息；在第四信息用于请求针对第八设备的寻呼消息的情况下，第四信息包括：为监听第八设备的寻呼消息所需的信息；在第四信息用于请求第八设备所需的系统信息的情况下，第四信息包括：第八设备所需的系统信息的类型。
在一些实施例中，在第四信息包括为监听第八设备的寻呼消息所需的信息的情况下，第一信息包括：针对第八设备的寻呼消息；在第四信息包括第八设备所需的系统信息的类型的情况下，第一信息包括：第八设备所需的系统信息。
在一些实施例中，第一信息用于指示装置1000的无线链路状态，或者，用于指示装置1000发生网络连接状态改变或无线链路状态改变。
在一些实施例中，第二设备为装置1000的下一跳终端设备；第一信息用于指示第十设备的无线链路状态，或者，用于指示第十设备发生网络连接状态改变或无线链路状态改变；其中，第十设备是装置1000的上一跳终端设备，或者，是通信链路中与装置1000不相邻的终端设备。
在一些实施例中，第一信息是从装置1000的上一跳终端设备获取的。
在一些实施例中，装置1000还包括第二处理单元，用于在通过RRC连接向通信链路中的第二设备发送第一信息之前，在第一信息中增加第五信息，第五信息用于指示装置1000的无线链路状态，或者，用于指示装置1000发生网络连接状态改变或无线链路状态改变。
在一些实施例中，第五信息包括以下至少之一：装置1000的标识；与装置1000的无线链路状态相关联的传输跳数的标识；以及，与装置1000发生网络连接状态改变或无线链路状态改变相关联的传输跳数的标识。
在一些实施例中，无线链路状态包括：无线链路失败；网络连接状态改变包括：小区切换、小区重选或RRC连接状态改变；无线链路状态改变包括：无线链路的链路质量下降。
在一些实施例中，第一信息用于指示以下至少之一：装置1000与第二设备之间的QoS；
第二设备可分配的QoS；以及，通信链路的传输跳数。
在一些实施例中，装置1000还包括确定单元，用于在通过RRC连接向通信链路中的第二设备发送 第一信息之前，确定装置1000与第二设备之间的QoS。
在一些实施例中，第二设备为装置1000的下一跳终端设备；第一信息为装置1000与第二设备之间的RRC重配消息，RRC重配消息包括以下至少一项：SRAP配置；无线链路控制配置；以及媒体接入控制的配置。
在一些实施例中，第一信息是装置1000确定的；或者，第一信息是装置1000基于与上一跳终端设备之间的RRC重配消息确定的。
在一些实施例中，目标设备为网络设备或终端设备。
在一些实施例中，第二设备为目标设备，且目标设备为网络设备；第一信息用于指示以下至少之一：第十一设备发生无线链路失败；第十一设备与至少一个第十二设备之间的信道质量；第十一设备的标识；以及，第十一设备与网络设备之间的传输跳数；其中，第十一设备为通信链路中与网络设备之间不存RRC连接的终端设备。
在一些实施例中，装置1000还包括第三发送单元，用于通过RRC连接向通信链路中的第十三设备发送第六信息，第六信息与无线资源管理相关；其中，第十三设备与装置1000在通信链路中不相邻。
在一些实施例中，通信链路具有以下特征中的至少之一：通信链路中所有相邻的设备之间存在RRC连接；通信链路中的部分或全部不相邻的设备之间存在RRC连接；在目标设备为网络设备的情况下，通信链路中的部分或全部终端设备与网络设备之间存在RRC连接；在目标设备为网络设备的情况下，通信链路中距离网络设备最近的终端设备，与其他全部或部分设备之间存在RRC连接；通信链路中的部分或全部设备与第十四设备之间存在RRC连接，第十四设备为以下任一设备：源终端设备；目标设备；通信链路中与源终端设备距离最近的设备；通信链路中与目标设备距离最近的设备；基于预设规则确定的设备。
在一些实施例中，装置1000是否与其他设备建立RRC连接是由装置1000或网络设备确定的。
在一些实施例中，第一信息通过以下一项或多项进行识别：无线链路控制信道；承载标识；逻辑信道。
本领域技术人员应当理解，本申请实施例的上述无线资源管理装置的相关描述可以参照本申请实施例的无线资源管理方法的相关描述进行理解。
图11是本申请实施例提供的一种通信设备1100示意性结构图。图11所示的通信设备1100包括处理器1110，处理器1110可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图11所示，通信设备1100还可以包括存储器1120。其中，处理器1110可以从存储器1120中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1120可以是独立于处理器1110的一个单独的器件，也可以集成在处理器1110中。
可选地，如图11所示，通信设备1100还可以包括收发器1130，处理器1110可以控制该收发器1130与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1130可以包括发射机和接收机。收发器1130还可以进一步包括天线，天线的数量可以为一个或多个。
该通信设备1100具体可为本申请实施例的第一设备，并且该通信设备1100可以实现本申请实施例的各个方法中由第一设备实现的相应流程，为了简洁，在此不再赘述。
图12是本申请实施例的芯片的示意性结构图。图12所示的芯片1200包括处理器1210，处理器1210可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图12所示，芯片1200还可以包括存储器1220。其中，处理器1210可以从存储器1220中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1220可以是独立于处理器1210的一个单独的器件，也可以集成在处理器1210中。
可选地，该芯片1200还可以包括输入接口1230。其中，处理器1210可以控制该输入接口1230与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片1200还可以包括输出接口1240。其中，处理器1210可以控制该输出接口1240与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
该芯片可应用于本申请实施例中的第一设备，并且该芯片可以实现本申请实施例的各个方法中由第一设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其 他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。该计算机可读存储介质可应用于本申请实施例中的第一设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由第一设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。该计算机程序产品可应用于本申请实施例中的第一设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由第一设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。该计算机程序可应用于本申请实施例中的第一设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由第一设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若 干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (58)

  1. 一种无线资源管理方法，应用于第一设备，所述第一设备所在的通信链路中包括源终端设备、目标设备，以及所述源终端设备和所述目标设备之间的多个中继终端设备，所述方法包括：
    通过无线资源控制RRC连接向所述通信链路中的第二设备发送第一信息，所述第一信息与无线资源管理相关。
  2. 根据权利要求1所述的方法，其中，所述第二设备与所述第一设备在所述通信链路中不相邻。
  3. 根据权利要求2所述的方法，其中，所述第一设备为所述通信链路中不满足第一条件的终端设备，所述第二设备为所述通信链路中满足所述第一条件的终端设备，所述目标设备为网络设备；
    所述第一信息用于请求针对所述第一设备的寻呼消息，和/或，所述第一设备所需的系统信息；
    所述第一条件包括以下至少之一：
    位于所述网络设备的信号覆盖范围内；
    为所述通信链路中距离所述网络设备最近的设备；以及，
    能够直接从所述网络设备获取寻呼消息和/或系统信息。
  4. 根据权利要求3所述的方法，其中，
    在所述第一信息用于请求针对所述第一设备的寻呼消息的情况下，所述第一信息包括：为监听所述第一设备的寻呼消息所需的信息；
    在所述第一信息用于请求所述第一设备所需的系统信息的情况下，所述第一信息包括：所述第一设备所需的系统信息的类型。
  5. 根据权利要求2所述的方法，其中，所述第一设备为所述通信链路中满足第一条件的终端设备，所述第二设备为所述通信链路中不满足所述第一条件的终端设备，所述目标设备为网络设备；
    所述第一信息包括：针对所述第二设备的寻呼消息，和/或，所述第二设备所需的系统信息；
    所述第一条件包括以下至少之一：
    位于所述网络设备的信号覆盖范围内；
    为所述通信链路中距离所述网络设备最近的设备；以及，
    能够直接从所述网络设备获取寻呼消息和/或系统信息。
  6. 根据权利要求5所述的方法，其中，在所述通过RRC连接向所述通信链路中的第二设备发送第一信息之前，所述方法还包括：
    接收来自所述第二设备的第二信息，所述第二信息用于请求针对所述第二设备的寻呼消息，和/或，所述第二设备所需的系统信息；
    在所述第二信息用于请求针对所述第二设备的寻呼消息的情况下，所述第二信息包括：为监听所述第二设备的寻呼消息所需的信息；
    在所述第二信息用于请求所述第二设备所需的系统信息的情况下，所述第二信息包括：所述第二设备所需的系统信息的类型。
  7. 根据权利要求6所述的方法，其中，
    在所述第二信息包括为监听所述第二设备的寻呼消息所需的信息的情况下，所述第一信息包括：针对所述第二设备的寻呼消息；
    在所述第二信息包括所述第二设备所需的系统信息的类型的情况下，所述第一信息包括：所述第二设备所需的系统信息。
  8. 根据权利要求6或7所述的方法，其中，在所述通过RRC连接向所述通信链路中的第二设备发送第一信息之前，所述方法还包括：
    基于为监听所述第二设备的寻呼消息所需的信息，从所述网络设备获取针对所述第二设备的寻呼消息；和/或，
    基于所述第二设备所需的系统信息的类型，从所述网络设备获取所述第二设备所需的系统信息。
  9. 根据权利要求2所述的方法，其中，
    所述第一设备和所述第二设备为所述通信链路中不同的终端设备；
    所述第一信息用于指示所述第一设备的无线链路状态，或者，用于指示所述第一设备发生网络连接状态改变或无线链路状态改变。
  10. 根据权利要求2所述的方法，其中，
    所述第一设备和所述第二设备为所述通信链路中不同的终端设备；
    所述第一信息用于指示所述第二设备测量信道繁忙比率，和/或所述第二设备与至少一个第三设备 之间的链路质量。
  11. 根据权利要求10所述的方法，其中，
    所述链路质量包括：参考信号接收功率。
  12. 根据权利要求2所述的方法，其中，
    所述第一设备和所述第二设备为所述通信链路中不同的终端设备；
    所述第一信息用于指示所述第二设备与第四设备之间的服务质量QoS；其中，所述第二设备与所述第四设备在所述通信链路中相邻。
  13. 根据权利要求2所述的方法，其中，
    所述第一设备和所述第二设备为所述通信链路中不同的终端设备；
    所述第一信息用于配置所述第二设备的传输资源。
  14. 根据权利要求13所述的方法，其中，
    所述第二设备的传输资源是所述第一设备从资源池中选取的，或者，是所述目标设备分配的，所述目标设备为网络设备。
  15. 根据权利要求12至14中任一项所述的方法，其中，
    所述第一设备为以下任一设备：
    所述源终端设备；
    所述目标设备；
    所述通信链路中与所述源终端设备距离最近的设备；
    所述通信链路中与所述目标设备距离最近的设备；
    基于预设规则确定的设备。
  16. 根据权利要求2所述的方法，其中，
    所述第一设备和所述第二设备为所述通信链路中不同的终端设备；
    所述第一信息为RRC重配消息，所述RRC重配消息包括以下至少一项：
    侧行中继适配协议SRAP配置；无线链路控制配置；以及媒体接入控制配置；
    其中，所述SRAP配置包括：为所述第二设备分配的标识和/或所述通信链路中其他终端设备的标识。
  17. 根据权利要求2至16中任一项所述的方法，其中，
    所述第一设备和所述第二设备为所述通信链路中不同的终端设备；
    在满足第二条件的情况下，所述第一设备与所述第二设备之间发生无线链路失败；所述第二条件包括：
    所述第一设备和所述第二设备之间，任意两个相邻设备之间发生无线链路失败；或者，
    所述通信链路中的任意两个相邻设备之间发生无线链路失败。
  18. 根据权利要求2至17中任一项所述的方法，其中，
    所述第一设备和所述第二设备为所述通信链路中不同的终端设备，且所述第一设备和所述第二设备之间存在RRC连接；
    在满足第三条件的情况下，所述第一设备与所述第二设备之间的RRC连接释放；所述第三条件包括：
    所述第一设备和所述第二设备之间，任意两个相邻设备之间的RRC连接释放；或者，
    所述通信链路中的任意两个相邻设备之间的RRC连接释放。
  19. 根据权利要求9至18中所述的方法，其中，
    所述目标设备为网络设备或终端设备。
  20. 根据权利要求2至19中任一项所述的方法，其中，
    所述第二设备的数量为一个或多个。
  21. 根据权利要求2所述的方法，其中，
    所述第二设备为所述目标设备，且所述目标设备为网络设备；
    所述第一信息用于指示以下至少之一：
    所述第一设备发生无线链路失败；
    所述第一设备与至少一个第五设备之间的信道质量；以及，
    所述通信链路中所有终端设备的标识。
  22. 根据权利要求2或21所述的方法，其中，
    所述第二设备为所述目标设备，且所述目标设备为网络设备；
    所述第一设备的传输资源，是由所述网络设备通过RRC连接为所述第一设备配置的。
  23. 根据权利要求2至22中任一项所述的方法，其中，所述方法还包括：
    通过RRC连接向所述通信链路中的第六设备发送第三信息，所述第三信息与无线资源管理相关；其中，所述第六设备与所述第一设备在所述通信链路中相邻。
  24. 根据权利要求1所述的方法，其中，所述第二设备与所述第一设备在所述通信链路中相邻。
  25. 根据权利要求24所述的方法，其中，所述第一设备为所述通信链路中不满足第一条件的终端设备，所述目标设备为网络设备，所述第二设备为所述第一设备在上行方向的下一跳终端设备；
    所述第一信息用于请求针对所述第一设备的寻呼消息，和/或，所述第一设备所需的系统信息；
    所述第一条件包括以下至少之一：
    位于所述网络设备的信号覆盖范围内；
    为所述通信链路中距离所述网络设备最近的设备；以及，
    能够直接从所述网络设备获取寻呼消息和/或系统信息。
  26. 根据权利要求25所述的方法，其中，
    在所述第一信息用于请求针对所述第一设备的寻呼消息的情况下，所述第一信息包括：为监听所述第一设备的寻呼消息所需的信息；
    在所述第一信息用于请求所述第一设备所需的系统信息的情况下，所述第一信息包括：所述第一设备所需的系统信息的类型。
  27. 根据权利要求24所述的方法，其中，所述第一设备为所述通信链路中不满足第一条件的终端设备，所述目标设备为网络设备，所述第二设备为所述第一设备在上行方向的下一跳终端设备；
    所述第一信息用于请求针对第七设备的寻呼消息，和/或，所述第七设备所需的系统信息；所述第七设备在所述通信链路中为所述第一设备在上行方向的上一跳终端设备、所述源终端设备或所述第一设备与所述源终端设备之间的任一与所述第一设备存在RRC连接的设备；
    所述第一条件包括以下至少之一：
    位于所述网络设备的信号覆盖范围内；
    为所述通信链路中距离所述网络设备最近的设备；以及，
    能够直接从所述网络设备获取寻呼消息和/或系统信息。
  28. 根据权利要求27所述的方法，其中，
    在所述第一信息用于请求针对所述第七设备的寻呼消息的情况下，所述第一信息包括：为监听所述第七设备的寻呼消息所需的信息；
    在所述第一信息用于请求所述第七设备所需的系统信息的情况下，所述第一信息包括：所述第七设备所需的系统信息的类型。
  29. 根据权利要求27或28所述的方法，其中，在所述通过RRC连接向所述通信链路中的第二设备发送第一信息之前，所述方法还包括：
    通过RRC连接，接收来自所述第七设备的所述第一信息。
  30. 根据权利要求27至29中任一项所述的方法，其中，在所述通过RRC连接向所述通信链路中的第二设备发送第一信息之前，所述方法还包括：
    在所述第一信息中增加第二信息，所述第二信息用于请求针对所述第一设备的寻呼消息，和/或，所述第一设备所需的系统信息。
  31. 根据权利要求30所述的方法，其中，
    在所述第二信息用于请求针对所述第一设备的寻呼消息的情况下，所述第二信息包括：为监听所述第一设备的寻呼消息所需的信息；
    在所述第二信息用于请求所述第一设备所需的系统信息的情况下，所述第二信息包括：所述第一设备所需的系统信息的类型。
  32. 根据权利要求25至31中任一项所述的方法，其中，
    所述第二设备为所述通信链路中满足所述第一条件的终端设备。
  33. 根据权利要求24所述的方法，其中，所述目标设备为网络设备，所述第二设备为所述第一设备在下行方向的下一跳终端设备，或者，为所述第一设备与所述源终端设备之间的任一与所述第一设备存在RRC连接的终端设备；
    所述第一信息包括：针对第八设备的寻呼消息，和/或，所述第八设备所需的系统信息；其中，所述第八设备为所述第二设备、所述源终端设备或所述第二设备与所述源终端设备之间的任一终端设备。
  34. 根据权利要求33所述的方法，其中，
    在所述第一设备满足第一条件的情况下，所述第一信息是所述第一设备从所述网络设备获取的；
    在所述第一设备不满足所述第一条件的情况下，所述第一信息是所述第一设备从所述通信链路中的 第九设备获取的；所述第九设备为所述第一设备在下行方向的上一跳终端设备，或者，为所述第一设备与所述网络设备之间的任一与所述第一设备存在RRC连接的终端设备；
    所述第一条件包括以下至少之一：
    位于所述网络设备的信号覆盖范围内；
    为所述通信链路中距离所述网络设备最近的设备；以及，
    能够直接从所述网络设备获取寻呼消息和/或系统信息。
  35. 根据权利要求33或34所述的方法，其中，在所述通过RRC连接向所述通信链路中的第二设备发送第一信息之前，所述方法还包括：
    通过所述第二设备接收来自所述第八设备的第四信息，所述第四信息用于请求针对所述第八设备的寻呼消息，和/或，所述第八设备所需的系统信息；
    在所述第四信息用于请求针对所述第八设备的寻呼消息的情况下，所述第四信息包括：为监听所述第八设备的寻呼消息所需的信息；
    在所述第四信息用于请求所述第八设备所需的系统信息的情况下，所述第四信息包括：所述第八设备所需的系统信息的类型。
  36. 根据权利要求35所述的方法，其中，
    在所述第四信息包括为监听所述第八设备的寻呼消息所需的信息的情况下，所述第一信息包括：针对所述第八设备的寻呼消息；
    在所述第四信息包括所述第八设备所需的系统信息的类型的情况下，所述第一信息包括：所述第八设备所需的系统信息。
  37. 根据权利要求24所述的方法，其中，
    所述第一信息用于指示所述第一设备的无线链路状态，或者，用于指示所述第一设备发生网络连接状态改变或无线链路状态改变。
  38. 根据权利要求24所述的方法，其中，
    所述第二设备为所述第一设备的下一跳终端设备；
    所述第一信息用于指示第十设备的无线链路状态，或者，用于指示所述第十设备发生网络连接状态改变或无线链路状态改变；其中，所述第十设备是所述第一设备的上一跳终端设备，或者，是所述通信链路中与所述第一设备不相邻的终端设备。
  39. 根据权利要求38所述的方法，其中，
    所述第一信息是从所述第一设备的上一跳终端设备获取的。
  40. 根据权利要求38或39所述的方法，其中，在所述通过RRC连接向所述通信链路中的第二设备发送第一信息之前，所述方法还包括：
    在所述第一信息中增加第五信息，所述第五信息用于指示所述第一设备的无线链路状态，或者，用于指示所述第一设备发生网络连接状态改变或无线链路状态改变。
  41. 根据权利要求40所述的方法，其中，
    所述第五信息包括以下至少之一：
    所述第一设备的标识；
    与所述第一设备的无线链路状态相关联的传输跳数的标识；以及，
    与所述第一设备发生网络连接状态改变或无线链路状态改变相关联的传输跳数的标识。
  42. 根据权利要求9、37至41中任一项所述的方法，其中，
    所述无线链路状态包括：无线链路失败；
    所述网络连接状态改变包括：小区切换、小区重选或RRC连接状态改变；
    所述无线链路状态改变包括：无线链路的链路质量下降。
  43. 根据权利要求24所述的方法，其中，
    所述第一信息用于指示以下至少之一：
    所述第一设备与所述第二设备之间的QoS；
    所述第二设备可分配的QoS；以及，
    所述通信链路的传输跳数。
  44. 根据权利要求43所述的方法，其中，在所述通过RRC连接向所述通信链路中的第二设备发送第一信息之前，所述方法还包括：
    确定所述第一设备与所述第二设备之间的QoS。
  45. 根据权利要求24所述的方法，其中，
    所述第二设备为所述第一设备的下一跳终端设备；
    所述第一信息为所述第一设备与所述第二设备之间的RRC重配消息，所述RRC重配消息包括以下至少一项：SRAP配置；无线链路控制配置；以及媒体接入控制的配置。
  46. 根据权利要求45所述的方法，其中，
    所述第一信息是所述第一设备确定的；或者，
    所述第一信息是所述第一设备基于与上一跳终端设备之间的RRC重配消息确定的。
  47. 根据权利要求37至46中任一项所述的方法，其中，
    所述目标设备为网络设备或终端设备。
  48. 根据权利要求24所述的方法，其中，
    所述第二设备为所述目标设备，且所述目标设备为网络设备；
    所述第一信息用于指示以下至少之一：
    第十一设备发生无线链路失败；
    第十一设备与至少一个第十二设备之间的信道质量；
    第十一设备的标识；以及，
    第十一设备与所述网络设备之间的传输跳数；
    其中，所述第十一设备为所述通信链路中与所述网络设备之间不存RRC连接的终端设备。
  49. 根据权利要求24至48中任一项所述的方法，其中，所述方法还包括：
    通过RRC连接向所述通信链路中的第十三设备发送第六信息，所述第六信息与无线资源管理相关；其中，所述第十三设备与所述第一设备在所述通信链路中不相邻。
  50. 根据权利要求1至49中任一项所述的方法，其中，所述通信链路具有以下特征中的至少之一：
    所述通信链路中所有相邻的设备之间存在RRC连接；
    所述通信链路中的部分或全部不相邻的设备之间存在RRC连接；
    在所述目标设备为网络设备的情况下，所述通信链路中的部分或全部终端设备与所述网络设备之间存在RRC连接；
    在所述目标设备为网络设备的情况下，所述通信链路中距离所述网络设备最近的终端设备，与其他全部或部分设备之间存在RRC连接；
    所述通信链路中的部分或全部设备与第十四设备之间存在RRC连接，所述第十四设备为以下任一设备：
    所述源终端设备；所述目标设备；所述通信链路中与所述源终端设备距离最近的设备；所述通信链路中与所述目标设备距离最近的设备；基于预设规则确定的设备。
  51. 根据权利要求1至50中任一项所述的方法，其中，
    所述第一设备是否与其他设备建立RRC连接是由所述第一设备或网络设备确定的。
  52. 根据权利要求1至51中任一项所述的方法，其中，
    所述第一信息通过以下一项或多项进行识别：
    无线链路控制信道；承载标识；逻辑信道。
  53. 一种无线资源管理装置，所述装置所在的通信链路中包括源终端设备、目标设备，以及所述源终端设备和所述目标设备之间的多个中继终端设备，所述装置包括：
    第一发送单元，用于通过无线资源控制RRC连接向所述通信链路中的第二设备发送第一信息，所述第一信息与无线资源管理相关。
  54. 一种终端，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至52中任一项所述的方法。
  55. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至52中任一项所述的方法。
  56. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至52中任一项所述的方法。
  57. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至52中任一项所述的方法。
  58. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至52中任一项所述的方法。
PCT/CN2023/107028 2023-07-12 2023-07-12 一种无线资源管理方法、装置、终端、芯片和存储介质 Pending WO2025010660A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/107028 WO2025010660A1 (zh) 2023-07-12 2023-07-12 一种无线资源管理方法、装置、终端、芯片和存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/107028 WO2025010660A1 (zh) 2023-07-12 2023-07-12 一种无线资源管理方法、装置、终端、芯片和存储介质

Publications (1)

Publication Number Publication Date
WO2025010660A1 true WO2025010660A1 (zh) 2025-01-16

Family

ID=94214406

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/107028 Pending WO2025010660A1 (zh) 2023-07-12 2023-07-12 一种无线资源管理方法、装置、终端、芯片和存储介质

Country Status (1)

Country Link
WO (1) WO2025010660A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022205349A1 (zh) * 2021-04-01 2022-10-06 Oppo广东移动通信有限公司 无线通信方法、终端设备和网络设备
CN115380548A (zh) * 2020-07-29 2022-11-22 Oppo广东移动通信有限公司 中继发现方法和终端
WO2023065910A1 (zh) * 2021-10-21 2023-04-27 大唐移动通信设备有限公司 远端终端信息的发送方法、接收方法及设备
WO2023102693A1 (zh) * 2021-12-06 2023-06-15 Oppo广东移动通信有限公司 无线通信的方法、远端终端和网络设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115380548A (zh) * 2020-07-29 2022-11-22 Oppo广东移动通信有限公司 中继发现方法和终端
WO2022205349A1 (zh) * 2021-04-01 2022-10-06 Oppo广东移动通信有限公司 无线通信方法、终端设备和网络设备
WO2023065910A1 (zh) * 2021-10-21 2023-04-27 大唐移动通信设备有限公司 远端终端信息的发送方法、接收方法及设备
WO2023102693A1 (zh) * 2021-12-06 2023-06-15 Oppo广东移动通信有限公司 无线通信的方法、远端终端和网络设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC. (EMAIL DISCUSSION RAPPORTEUR): "Summary of [AT111-e][605][Relay] L2 Relay Mechanism", 3GPP DRAFT; R2-2008254, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200817 - 20200828, 1 September 2020 (2020-09-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051926256 *

Similar Documents

Publication Publication Date Title
US20250294545A1 (en) Sidelink relay communication method and apparatus, device and medium
CN102883441B (zh) 一种无线宽带通信方法和装置
KR102261172B1 (ko) 통신 방법 및 장치
US11064557B2 (en) Method and device for establishing radio resource control connection
CN105357773B (zh) 一种无线宽带通信方法，装置和系统
US20200221538A1 (en) Data transmission method, terminal device, and network device
EP3735084B1 (en) Method and apparatus for sending data quantity report
CN108366398A (zh) 一种数据传输方法、网络设备及终端设备
CN108184249A (zh) 回程链路的信息传输方法及系统、代理设备、接入设备
CN115314970A (zh) 发现和选择中继用户设备的方法及用户设备
WO2022021165A1 (zh) 中继发现方法和终端
US20250008371A1 (en) Communication method and apparatus, and storage medium
WO2022036555A1 (zh) 中继传输的方法、中继终端和远端终端
CN115136651A (zh) 切换方法和通信装置
CN116419334A (zh) 一种网元选择方法及装置、网络设备
WO2024027412A1 (zh) 通信方法、通信装置及通信系统
WO2022006863A1 (zh) 无线通信方法、终端设备和网络设备
CN118476273A (zh) 收发信息的方法、装置和通信系统
WO2025019993A1 (zh) 中继通信方法和设备
WO2025010660A1 (zh) 一种无线资源管理方法、装置、终端、芯片和存储介质
WO2024065137A1 (zh) 配置信息获取方法, 配置信息转发方法以及终端设备
CN118318470A (zh) 无线通信方法、终端设备以及网络设备
CN117837178A (zh) 无线通信的方法、远端终端和网络设备
CN121195559A (zh) 一种无线资源管理方法、装置、终端、芯片和存储介质
US20250184249A1 (en) Communication method, communication apparatus, and communication system

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023944680

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023944680

Country of ref document: EP

Effective date: 20251205