A communication method, a communication device, a readable storage medium, and a chip system

Abstract

The application provides a communication method, a communication device, a readable storage medium and a chip system, and can be applied to the technical field of communication. In the method, an access network device allocates an end-to-end quality of service (QoS) parameter configured for a protocol data unit session established for a remote user equipment (UE) to each hop path in a multi-hop path, obtains the QoS parameter of each hop path, and sends configuration information and first indication information to a first UE in a connected state. The configuration information is used for configuring the QoS parameter of a path (such as a first path) between the first UE and other relay UEs connected thereto, and the first indication information is used for instructing the first UE to send the QoS parameter of the first path to a relay UE (such as a second UE) in an inactive state. Therefore, the terminal device in the inactive state can also receive the QoS parameter configured by the access network device, and the quality of service of the end-to-end is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, communication device, readable storage medium, and chip system. Background Technology

[0002] Sidelink is a direct communication technology based on 5G technology, which supports direct communication between devices (D2D) without the need for relaying through base stations. It is widely used in multi-hop relay scenarios such as vehicle-to-everything (V2X) and public safety.

[0003] With the development of 5G V2X vehicle-to-everything (V2X) and multi-hop relay technologies, user equipment (UEs) can access the network through one or more relay terminal devices, forming multi-hop paths. When data flows through multiple PC5 hops and the final air interface (Uu) hop, the Quality of Service (QoS) parameter is crucial to the communication quality of the multi-hop path. In related technologies, to ensure the transmission quality of multi-hop paths, the QoS parameters for each path need to be configured for each relay UE. Summary of the Invention

[0004] This application provides a communication method, communication device, readable storage medium, and chip system that enables the configuration of QoS parameters to user equipment in an RRC inactive state, thereby improving end-to-end service quality.

[0005] In a first aspect, a communication method is provided. This method can be executed by a first user equipment, or by a component (such as a circuit, chip, or chip system) configured in the first user equipment, or by a logic module or software capable of implementing all or part of the functions of the first user equipment. This application does not limit this approach. The following description uses a first user equipment as an example.

[0006] The method includes: after receiving configuration information and first indication information from an access network device, a first user equipment (UE) sends a first message carrying QoS parameters of a first path to a second user equipment (BUE) based on the first indication information. The configuration information is used to configure the QoS parameters of the first path. The first path is a path between the BUE and the UE when the BUE is in a radio resource control (RRC) inactive state. The first indication information instructs the UE to send the QoS parameters of the first path to the BUE.

[0007] In this method, after the access network device determines the QoS parameters of each hop path, it sends the QoS parameters of the current path to all user equipment (UEs) in the RRC connected state. The first UE in the RRC connected state forwards the QoS parameters of the first path to the second UE, enabling the second UE in the RRC inactive state to also obtain the QoS parameters of its current path. This improves the reliability of data transmission in multi-hop paths and enhances end-to-end service quality. Furthermore, the first UE only needs to perform the operation of forwarding the QoS parameters of the first path to the second UE based on the first indication information, without participating in the determination process of the QoS parameters for each hop path. This significantly reduces the computational burden on the first UE and improves the efficiency of QoS parameter configuration for each hop path.

[0008] In one possible implementation, the first message is carried in PC5 RRC signaling, which includes a first field indicating the identification information of the second user equipment and the QoS parameters of the first path.

[0009] Therefore, the first user equipment adds a first field to the PC5 RRC signaling to indicate the identification information of the second user equipment and the QoS parameters of the first path, thus realizing the scalability and compatibility of PC5 RRC signaling.

[0010] In one possible implementation, the first field is also used to indicate the priority information of the first path and / or the validity period of the QoS parameters of the first path.

[0011] Therefore, the first user equipment can indicate the priority information of the first path and / or the validity period of the QoS parameters of the first path through the newly added first field in the PC5 RRC signaling, without creating new signaling. This not only improves compatibility with the existing network architecture, but also reduces the workload of redeveloping new signaling and interaction procedures.

[0012] In addition, the first user equipment indicates the validity period of the QoS parameters of the first path through the first field, so as to indicate that the QoS parameters of the first path are only valid within the validity period, thereby avoiding the problem that the second user equipment uses the QoS parameters of the first path for data transmission outside the validity period, which would affect the reliability of data transmission.

[0013] In one possible implementation, the configuration information is also used to configure the priority information of the first path. Thus, the first user equipment can send the priority information of the first path to the second user equipment, ensuring that the second user equipment, in an RRC connection state, considers the priority information of the first path during data transmission. This improves the reliability of data transmission and enhances the service experience.

[0014] In one possible implementation, the configuration information is carried in the RRC connection reconfiguration message. It should be understood that after the access network device determines the QoS parameters of the first path, it can send the configuration information to the first user equipment (UE) in the RRC connection reconfiguration message. In this way, after receiving the RRC connection reconfiguration message, the first UE can directly send a first message carrying the QoS parameters of the first path to the second UE based on the configured QoS parameters of the first path. This allows the second UE, when in RRC connected state, to perform data transmission based on the QoS parameters of the first path, thereby improving end-to-end service quality.

[0015] Secondly, a communication method is provided. This method can be executed by a second user equipment, or by a component (such as a circuit, chip, or chip system) configured in the second user equipment, or by a logic module or software capable of implementing all or part of the functions of the second user equipment. This application does not limit this approach. The following description uses a second user equipment as an example.

[0016] The method includes: when the second user equipment is in an RRC inactive state, receiving a first message from the first user equipment carrying QoS parameters of a first path. The first path is a path between the second user equipment and the first user equipment. When the second user equipment is in an RRC connected state, data transmission is performed based on the QoS parameters of the first path.

[0017] Therefore, the second user equipment in the RRC inactive state can obtain the QoS parameters of the first path forwarded by the first user equipment by receiving the first message from the first user equipment, which helps to improve the reliability of data transmission in multi-hop paths.

[0018] In one possible implementation, the first message is carried in PC5 RRC signaling, which includes a first field indicating the identification information of the second user equipment and the QoS parameters of the first path.

[0019] In this implementation, a first field is added to the PC5 RRC signaling received by the second user equipment to indicate the identification information of the second user equipment and the QoS parameters of the first path, thereby realizing the scalability and compatibility of PC5 RRC signaling.

[0020] In one possible implementation, the newly added first field in the PC5 RRC signaling received by the second user equipment is also used to indicate the priority information of the first path and / or the validity duration of the QoS parameters of the first path. This eliminates the need to create new signaling, improving compatibility with existing network architectures and reducing the workload of redeveloping new signaling and interaction procedures.

[0021] In one possible implementation, when the second user equipment is in RRC connected state, data transmission is performed based on the QoS parameters of the first path, including:

[0022] In response to receiving the first message, the second user equipment starts a first timer. During the operation of the first timer, while the second user equipment is in RRC connected state, the second user equipment performs data transmission based on the QoS parameters of the first path. The duration of the first timer is the valid duration of the QoS parameters of the first path.

[0023] Therefore, by setting a first timer, the second user equipment can transmit data based on the QoS parameters of the first path only during the operation of the first timer and when it is in the RRC connection state. This avoids the problem of the second user equipment using the QoS parameters of the first path to transmit data outside the effective time period, which would affect the reliability of data transmission.

[0024] Thirdly, a communication method is provided, which can be executed by an access network device, or by a component (such as a circuit, chip, or chip system) configured in the access network device, or by a logic module or software capable of implementing all or part of the functions of the access network device. This application does not limit this approach. The following description uses an access network device as an example.

[0025] The method includes: after receiving end-to-end QoS parameters configured for a Protocol Data Unit (PDU) session established for a remote user equipment (UE) from a core network device, the access network device allocates the end-to-end QoS parameters to each hop of a multi-hop path to obtain QoS parameters for each hop. The multi-hop path includes a first path, which is a path between a second UE in an RRC inactive state and a first UE, where the first UE is a device connected to the second UE in an RRC connected state. The access network device sends configuration information and first indication information to the first UE. The configuration information is used to configure the QoS parameters of the first path, and the first indication information is used to instruct the first UE to send the QoS parameters of the first path to the second UE.

[0026] In this implementation, the access network device allocates end-to-end QoS parameters to each hop of the multi-hop path. When configuring QoS parameters for user equipment in the multi-hop path, the access network device takes into account the RRC connection state of the user equipment. By instructing the first user equipment in the RRC connection state to forward the QoS parameters of the second user equipment in the active state, the access network device avoids the problem that the user equipment in the active state cannot receive the QoS parameters configured by the access network device, which would prevent data transmission based on the dynamically configured QoS parameters and affect the end-to-end service quality.

[0027] In one possible implementation, the end-to-end QoS parameters include the end-to-end packet delay budget (PDB). These QoS parameters are allocated to each hop in a multi-hop path to obtain the QoS parameters for each hop. This includes allocating the end-to-end QoS parameters based on multi-hop path context information. Since the multi-hop path context information of the remote UE contains all the key information on the multi-hop path, the access network device allocates the end-to-end QoS parameters based on this context information, resulting in more accurate QoS parameters for each hop, thereby improving the end-to-end service quality.

[0028] In one possible implementation, the multi-hop path includes a Uu link and at least one PC5 link. When the access network device allocates the end-to-end PDB based on the multi-hop path context information, it first configures the PDB for the Uu link to obtain the remaining PDB budget. Then, the access network device allocates the remaining PDB budget to at least one PC5 link to obtain the PDB for at least one PC5 link.

[0029] In one possible implementation, the access network device configures the PDB for the Uu link, obtains the remaining PDB budget, and then evenly distributes the remaining PDB budget to at least one PC5 link, resulting in the PDB for at least one PC5 link. Thus, by evenly distributing the remaining PDB budget, the access network device configures the same PDB for each of the multiple PC5 links, and the reliability of the multiple PC5 links is determined by the strongest PC5 link, improving end-to-end service quality and reliability. Furthermore, the access network device does not need to perform complex QoS allocation calculations for each PC5 link, reducing the processing load on the access network device and saving resource consumption.

[0030] In one possible implementation, the access network device configures the PDB of the Uu link. After obtaining the remaining PDB budget, it allocates the remaining PDB budget based on the channel quality of at least one PC5 link and / or the capability information of each relay user equipment, thus obtaining the PDB of at least one PC5 link. Therefore, by configuring the PDB of each PC5 link differently, the access network device can improve resource utilization.

[0031] In one possible implementation, the QoS parameters for each hop path are obtained by inputting multi-hop path context information into a QoS allocation model. Since the QoS allocation model is pre-trained, it can allocate QoS parameters for each hop path more accurately and efficiently. Therefore, it helps to improve the rationality and efficiency of QoS parameter allocation, enabling each hop path to transmit data efficiently and reliably based on the configured QoS parameters.

[0032] In one possible implementation, before allocating end-to-end QoS parameters based on multi-hop path context information and obtaining the QoS parameters for each hop path, the method further includes:

[0033] After receiving a first request message from a remote UE requesting access to the network via a multi-hop relay, the access network device sends a second request message to the core network device and receives core network context information from the core network device. This core network context information includes end-to-end QoS parameters, end-to-end QoS profiles, and device information of the remote UE. Based on this core network context information, the access network device establishes multi-hop path context information for the remote UE.

[0034] The multi-hop path context information is used to indicate the information required for each hop in a multi-hop path to be established between the remote UE and the access network equipment. The multi-hop path context information includes core network context information, path topology information, channel quality of each hop in the multi-hop path, and capability information of each user equipment in the multi-hop path. The path topology information includes the number of hops in the multi-hop path, equipment information of each relay user equipment arranged in hop-number order, and the Radio Resource Control (RRC) connection status of each relay user equipment.

[0035] It is evident that by establishing multi-hop path context information for remote UEs, including all key information about the multi-hop path, the access network equipment enables more accurate QoS parameters for each hop path when allocating end-to-end QoS parameters based on the multi-hop path context information.

[0036] In one possible implementation, the access network device includes a control plane unit and a distributed unit. The method further includes: the control plane unit sending a context establishment request message to the distributed unit. The context establishment request message carries a context information element field. This context information element field carries path topology information and QoS parameters for each hop path.

[0037] Therefore, without modifying existing protocol standards, the control plane unit adds a context information element field to the context establishment request message. By carrying the QoS parameters of each hop path in the newly added context information element field, dynamic configuration of the QoS parameters of each hop path can be achieved.

[0038] In one possible implementation, the context information element field is also used to carry the channel quality of each hop in the multi-hop path. Thus, after receiving the channel quality of each hop in the multi-hop path, the access network device can consider the channel quality of each hop when allocating QoS parameters to the peer, enabling user equipment in the multi-hop path to transmit data efficiently and reliably based on the allocated QoS parameters.

[0039] In one possible implementation, the configuration information is also used to configure the priority information of the first path.

[0040] In one possible implementation, the configuration information is carried in an RRC connection reconfiguration message.

[0041] In this implementation, the access network device carries configuration information in the RRC connection reconfiguration message, eliminating the need to send configuration information separately to the first user equipment, thus improving transmission efficiency and resource utilization.

[0042] Fourthly, a communication device is provided, comprising a transceiver module. The transceiver module is used to receive configuration information and first indication information from an access network device, and then, based on the first indication information, send a first message to a second user equipment, wherein the first message carries QoS parameters for a first path.

[0043] The configuration information is used to configure the Quality of Service (QoS) parameters of the first path; the first path is the path between the second user equipment and the first user equipment when the radio resource control (RRC) is inactive; the first indication information is used to instruct the first user equipment to send the QoS parameters of the first path to the second user equipment.

[0044] Fifthly, a communication device is provided, comprising a transceiver module. The transceiver module is configured to receive a first message from a first user equipment when the second user equipment is in a Radio Resource Control (RRC) inactive state; wherein the first message carries Quality of Service (QoS) parameters for a first path, the first path being a path between the second user equipment and the first user equipment; and to perform data transmission based on the QoS parameters of the first path when the second user equipment is in an RRC connected state.

[0045] Sixthly, a communication apparatus is provided, comprising a processing module and a transceiver module. The transceiver module is used to receive end-to-end QoS parameters configured for a PDU session established for a remote UE from a core network device;

[0046] The processing module is used to allocate end-to-end QoS parameters to each hop of the multi-hop path to obtain the QoS parameters of each hop path; wherein, the multi-hop path includes a first path, which is a path between the second user equipment in the RRC inactive state and the first user equipment, and the first user equipment is a device connected to the second user equipment in the RRC connected state;

[0047] The transceiver module is used to send configuration information and first indication information to the first user equipment; wherein, the configuration information is used to configure the QoS parameters of the first path, and the first indication information is used to instruct the first user equipment to send the QoS parameters of the first path to the second user equipment.

[0048] The fourth, fifth, and sixth aspects are the implementations on the device side corresponding to the first, second, and third aspects. The explanations, supplements, and descriptions of the beneficial effects of the first, second, and third aspects also apply to the fourth, fifth, and sixth aspects, and will not be repeated here.

[0049] A seventh aspect provides a communication device including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0050] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0051] Eighthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the second aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0052] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0053] A ninth aspect provides a communication device including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the third aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0054] In a tenth aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

[0055] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0056] Eleventhly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of any of the preceding aspects.

[0057] Optionally, the processor may be one or more, and the memory may be one or more.

[0058] In a twelfth aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions) that, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0059] In a thirteenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods in any possible implementation of any of the preceding aspects.

[0060] In a fourteenth aspect, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be performed. The chip system may be composed of chips or may include chips and other discrete devices.

[0061] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0062] In a fifteenth aspect, a communication system is provided, including the aforementioned first user equipment, second user equipment, access network equipment, and core network equipment. Optionally, the communication system may further include other devices that communicate with the user equipment and / or access network equipment. Attached Figure Description

[0063] Figure 1 A schematic diagram of a communication system provided in an embodiment of this application;

[0064] Figure 2 A flowchart illustrating a QoS parameter configuration method provided in an embodiment of this application;

[0065] Figure 3 A flowchart illustrating a communication method provided in an embodiment of this application;

[0066] Figure 4 A flowchart illustrating another communication method provided in an embodiment of this application;

[0067] Figure 5 A schematic block diagram of a communication device provided in an embodiment of this application;

[0068] Figure 6 A schematic block diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0069] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0070] The technical solutions provided in this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) systems, General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications.

[0071] For example, Figure 1 This is a schematic diagram of a communication system provided in an embodiment of this application. The communication system 100 is applied in a sidelink relay scenario and may include an access network device 110, a first relay user equipment (UE) 120, a second relay UE 130, and a remote UE 140.

[0072] The remote UE 140 forwards data to the access network device 110 via a sidelink link with the second relay UE 130 and the first relay UE 120. In this system, when data transmission occurs between the remote UE 140 and the access network device 110, the first relay UE 120 and the second relay UE 130 act as data relays. The remote UE 140 sends data to the second relay UE 130 via the PC5 interface. After the second relay UE 130 forwards the data to the first relay UE 120 via the PC5 interface, the first relay UE 120 transmits data with the access network device 110 via the Uu interface.

[0073] Figure 1 The number of relay UEs shown is only one and is merely an example. The number of access network devices and / or relay UEs included in the communication system 100 is not limited in this embodiment. Optionally, the communication system 100 may also include multiple relay UEs.

[0074] The network equipment in this application can be network-side equipment such as access network equipment and core network equipment. Access network equipment is sometimes also called access node. Access network equipment has wireless transceiver capabilities and is used to communicate with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the above-mentioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units that can implement some of the functions of a base station. Access network equipment can be macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, or wireless controllers in cloud radioaccess network (CRAN) scenarios. Optionally, access network equipment can also be servers, wearable devices, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form used in the access network equipment. In this application, the access network equipment is referred to as a network device.

[0075] In this application, the means for implementing the functions of a network device can be a network device itself, or a means capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This means can be installed in or connected to the network device. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.

[0076] The user equipment in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device can be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), V2X communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal device.

[0077] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solutions provided in this application, the example of a terminal device being used to implement the functions of a terminal device is used to describe the technical solutions provided in this application.

[0078] Taking network devices as access network devices and terminal devices as terminals as an example, access network devices and / or terminals can be fixed or mobile. Access network devices and / or terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on airplanes, balloons, and artificial satellites. This application does not limit the application scenarios of access network devices and terminals. Access network devices and terminal devices can be deployed in the same or different scenarios. For example, access network devices and terminal devices can be deployed simultaneously on land; or, access network devices can be deployed on land and terminal devices can be deployed on water, etc., and so on.

[0079] In practical applications, multiple access network devices can collaborate to assist terminals in achieving wireless access, with each device performing a portion of the base station's functions. For example, access network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0080] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.

[0081] To facilitate understanding of the embodiments of this application, the terminology used in this application will be briefly explained first. Optionally, the explanation of some terms may also refer to the explanations in the 3rd Generation Partnership Project (3GPP) standard protocol.

[0082] 1. A Protocol Data Unit (PDU) Set is a logical collection of protocol data units with the same or related characteristics. A PDU Set may include one or more PDUs. A PDU Set carries the payload of an information unit generated at the application layer (e.g., a frame or video clip used to extend real-world services). All PDUs within a PDU Set are transmitted within the same Quality of Service (QoS) stream.

[0083] 2. Quality of Service (QoS) flow is the smallest granularity for distinguishing service quality within a Protocol Data Unit (PDU) session in a 5G system. A PDU session can contain multiple QoS flows, each with corresponding QoS parameters to ensure the service quality of different services. Different QoS flows correspond to different QoS flow identifiers (QFIs), meaning the QFI is used to uniquely identify a QoS flow.

[0084] The data packet processing requirements, such as QoS requirements, transmitted between a user equipment and the next node (e.g., a relay user equipment or network equipment) can be collectively referred to as QoS characteristics. Specifically, the QoS characteristics of a QoS flow include the following:

[0085] (a) Resource type (RT) is used to define the allocation of transport resources required for QoS flow.

[0086] QoS flows can be categorized into the following three types based on RT:

[0087] Non-guaranteed bit rate (Non-GBR) QoS streams are suitable for services with variable bandwidth requirements, such as web browsing and streaming media. These QoS streams do not require permanent allocation of dedicated resources; instead, they meet their needs through dynamic resource allocation.

[0088] Guaranteed bit rate (GBR) QoS streams are suitable for services requiring fixed bandwidth, such as real-time video calls and online games. Network devices dynamically allocate dedicated resources for GBR QoS streams to ensure the stability and continuity of data transmission.

[0089] Delay-critical guaranteed bit rate (DCGBR) QoS stream: This is a new resource type added in 5G, used in scenarios with extremely high latency requirements, such as connected vehicles and industrial automation. This type of QoS stream not only needs to guarantee bandwidth, but also requires low latency and low jitter.

[0090] (b) Priority, used to indicate the importance of QoS flows.

[0091] The priority of QoS flows can be represented numerically. For example, the lower the value, the higher the priority of the QoS flow, and the more important the QoS flow. Priority is used to determine the scheduling order of QoS flows when resources are limited. When the network is congested, the transmission of high-priority QoS flows is prioritized.

[0092] (c) Packet delay budget (PDB) refers to the maximum allowable delay time between a data packet and the next node.

[0093] (d) Packet error rate (PER) refers to the packet loss rate allowed by QoS flow.

[0094] (e) Averaging window (AW) is used to calculate and adjust traffic statistics for QoS flows and is only applicable to QoS flows of GBR and Delay-critical GBR resource types.

[0095] (f) Maximum data burst volume (MDBV) is used to limit the maximum burst volume of data packets within the PDB period. It is only applicable to QoS flows of the Delay-critical GBR resource type and its function is to control the burst volume of data and prevent network congestion.

[0096] 3. Radio Resource Control (RRC) is a key protocol in mobile communication systems used to manage the allocation, release, and communication control of radio resources between terminal devices and network devices. The RRC status and the QoS parameter configurations for terminal devices in different RRC states are as follows:

[0097] (1) RRC Connected State (RRC_CONNECTED): In connected state, an RRC connection is established between the terminal device and the network device. Both the radio access network (RAN) and the terminal device maintain complete context information of the terminal device. The network device can send or adjust QoS parameters to the terminal device in real time. The terminal device can also report the real-time measured signal quality as needed, so that the network device can perform fine-grained segmentation and reconfiguration of QoS parameters based on the reported signal quality.

[0098] (2) RRC Inactive State (RRC_INACTIVE): In the inactive state, there is no RRC connection between the terminal device and the network device. However, the wireless access network and the terminal device retain some context information, such as security information, terminal device capability information, and QoS configuration. Although the terminal device and the network device do not maintain real-time interaction, the RRC connection can be quickly restored. Because the terminal device and the network device do not maintain real-time interaction, the network device cannot send or adjust QoS parameters to the terminal device in real time, which limits the real-time nature and flexibility of QoS parameter configuration.

[0099] (3) RRC Idle State (RRC_IDLE): In the idle state, there is no RRC connection between the terminal device and the network device. The terminal device does not retain context information, and the network device cannot configure the QoS parameters of the terminal device. The terminal device can only communicate based on the pre-configured QoS parameters or the default QoS parameters.

[0100] 4. The 5G Quality of Service Identifier (5QI) is a predefined index. Each index value corresponds to a set of pre-configured QoS characteristics. Each value of the 5QI and its corresponding QoS characteristic are predefined by the 3GPP standard. Different values ​​of the 5QI correspond to different QoS characteristics. For example, typical values ​​of the 5QI and the QoS characteristics corresponding to different values ​​are detailed in Table 1 below.

[0101] Table 1

[0102]

[0103] 5. PC5 Quality of Service Identifier (PQI): Similar to 5QI, PQI is also a predefined index, with each index value corresponding to a set of pre-configured QoS features. For example, typical PQI values ​​and the corresponding QoS features for different values ​​are detailed in Table 2 below.

[0104] Table 2

[0105]

[0106] It should be noted that the 5QI values ​​and the QoS feature configurations corresponding to different 5QI values ​​shown in Table 1 above, as well as the PQI values ​​and the QoS feature configurations corresponding to different PQI values ​​shown in Table 2 above, are only examples and are not limited in this application.

[0107] It should be understood that the technical terms used in this application are for illustrative purposes only and not as limiting. For example, as technology evolves, technical terms may also change, and other technical terms that have the same technical meaning should also apply to this application.

[0108] In multi-hop communication links, when a remote UE transmits data with a network device, the data needs to be transmitted through a relay UE to the remote UE or network device. Therefore, the configuration of QoS parameters for each hop communication link (or path) is crucial for communication quality. In related technologies, network devices can segment and allocate end-to-end QoS parameters to each hop. However, network devices can only directly configure the QoS parameters of communication links for relay UEs in RRC connected state; they cannot manage the QoS parameters of communication links for user equipment in RRC inactive or RRC idle state.

[0109] For example, Figure 2 This is a flowchart illustrating a QoS parameter configuration method provided in an embodiment of this application, as shown below. Figure 2 As shown, the configuration method includes:

[0110] S201, the remote UE sends a relay access request message to the access network device, and the corresponding access network device receives the relay access request message.

[0111] The relay access request message is used to request network access via a relay. The relay access request message includes the remote UE's identification information and initial service requirement information. The remote UE's identification information identifies the remote UE, and the initial service requirement information may include service requirements, service type, PDU session type, etc. Optionally, the initial service requirement information may also include desired QoS parameters, such as the 5QI value.

[0112] Optionally, when a remote UE establishes a PDU session, the remote UE can directly send a relay access request message to the access network device, or the remote UE can send a relay access request message to the relay UE through the PC5 interface. After receiving the relay access request message, the relay UE sends a relay access request message to the access network device. In this embodiment, the method by which the remote UE sends the relay access request message to the access network device is not limited.

[0113] Optionally, the trunk access request message can be encapsulated in a specific RRC message, such as RRCSetupRequest or RRCReconfiguration.

[0114] S202, the access network equipment and the core network equipment interact to establish a PDU session for the remote UE.

[0115] Specifically, the process of establishing a PDU session can refer to existing technologies and will not be elaborated here.

[0116] S203, the core network equipment allocates end-to-end QoS parameters for the PDU session based on the service requirements, network policies and subscription information of the remote UE.

[0117] In this embodiment, the access network device forwards the relay access request message to the access and mobility management function (AMF) network element in the core network. After the AMF network element authenticates the remote UE, the session management function (SMF) in the core network configures end-to-end QoS parameters for the remote UE's PDU session based on the remote UE's service requirements, network policies, and subscription information. The description of the network policies and subscription information, as well as the specific implementation of the core network device allocating 5QI and end-to-end QoS parameters for the PDU session based on the remote UE's service requirements, network policies, and subscription information, can refer to existing technologies and will not be elaborated further.

[0118] As exemplified in this application, end-to-end QoS parameters may include 5QI, resource type, priority, packet delay budget, packet error rate, etc.

[0119] S204, the core network device sends end-to-end QoS parameters to the access network device, and the corresponding access network device receives the end-to-end QoS parameters.

[0120] The core network equipment sends end-to-end QoS parameters to the gNB-CU. During the context establishment phase of the remote UE, the gNB-CU generates a context establishment request message. This message requests the establishment of context information for the remote UE. The gNB-CU sends a context establishment request message carrying end-to-end QoS parameters to the gNB-DU. Upon receiving the context establishment request message, the gNB-DU stores the end-to-end QoS parameters and bearer configuration carried in the message and uses the end-to-end QoS parameters for uplink traffic policing of non-GBR bearers. For example, the end-to-end QoS parameters may also include the aggregate maximum bit rate (AMBR) of the uplink PDU session. The AMBR defines the upper limit of the total uplink rate of all non-GBR QoS flows in a given PDU session of the remote UE. Bearer configuration refers to the parameters configured by the gNB-DU for the data radio bearer (DRB) to meet end-to-end QoS requirements. For example, bearer configuration may include DRB identifiers, mapping rules from QoS flows to the DRB, etc.

[0121] For example, the gNB-CU sends a UE Context Setup Request signaling message to the gNB-DU, in which the UE Context Setup Request signaling message carries end-to-end QoS parameters.

[0122] S205, the access network equipment allocates and maps end-to-end QoS parameters to obtain the QoS parameters of the Uu link and the QoS parameters of each PC5 link.

[0123] Here, Uu link refers to the last hop in a multi-hop path, and PC5 link refers to the link between the remote UE and the relay UE in a multi-hop path, or the link between two relay UEs. For example, ... Figure 1 As shown, the Uu link refers to the link between the first relay UE120 and the access network device 110, and the PC5 link refers to the link between the remote UE140 and the second relay UE130, or the link between the second relay UE130 and the first relay UE120.

[0124] The QoS parameters for the Uu link are used for the Uu link between the relay UE and the access network equipment. For example, the QoS parameters for the Uu link include DRB configuration. The QoS parameters for the PC5 link are used for the PC5 link between the relay UE and the remote UE. For example, the QoS parameters for the PC5 link include PQI.

[0125] S206, the access network device sends the QoS parameters of the link where the relay UE in the RRC connection state is located to the relay UE in the RRC connection state. Correspondingly, the relay UE in the RRC connection state receives the QoS parameters of its link.

[0126] Optionally, the access network device can send the QoS parameters of the Uu link to the relay UE in the RRC connected state via RRC signaling. For example, the access network device may send the RRC reconfiguration message to the relay UE in the RRC connected state, which may include the QoS parameters of the Uu link.

[0127] Optionally, a relay UE in RRC connected state can receive QoS parameters of the PC5 link from the access network device. Alternatively, the relay UE can automatically derive the corresponding uplink QoS characteristics based on the QoS characteristics of the downlink data packets. Optionally, the relay UE receives downlink data packets from the access network device destined for a remote UE via the Uu interface, and these downlink data packets carry 5QI. The relay UE's reflection QoS function is triggered, and the relay UE maps the 5QI carried in the downlink data packet to the corresponding PQI through local mapping to obtain the QoS parameters of the PC5 link.

[0128] S207, the access network device sends the QoS parameters of the PC5 link to the remote UE in the RRC connection state.

[0129] Optionally, the access network device sends the QoS parameters of the PC5 link to the remote UE. After receiving the QoS parameters of the PC5 link, the remote UE configures its local QoS flow.

[0130] For example, still using Figure 1 For example, assuming that the RRC connection state of the remote UE140 is in the RRC inactive state, the RRC connection state of the second relay UE130 is in the RRC connected state, and the RRC connection state of the first relay UE120 is in the RRC connected state, the access network device can send the QoS parameters of the Uu link to the first relay UE120 and the QoS parameters of the PC5 link to the second relay UE130. However, since there is no RRC connection between the remote UE140 and the access network device, the access network device cannot send the QoS parameters of the PC5 link to the remote UE140.

[0131] From the above Figure 2 It is known that access network devices can configure QoS parameters for the links of a relay UE in the connected state, specifically the Uu link and the PC5 link. However, access network devices can only configure QoS parameters for relay UEs in the RRC connected state. When a relay UE is in the RRC inactive or RRC idle state, the access network device cannot configure QoS parameters for it, resulting in end-to-end QoS parameter segmentation failure. Relay UEs or remote UEs in the RRC inactive or RRC idle state can only rely on pre-configured static QoS policies for data transmission, making it difficult to adapt to dynamically changing network topologies or loads.

[0132] Furthermore, in the Sidelink relay scenario, the resource allocation modes for terminal devices include Mode 1 and Mode 2. Mode 1 is the network-side scheduling mode, where the network-side equipment (e.g., a base station) controls and allocates resources to each terminal device. Mode 2 is the terminal device autonomous mode, where each terminal device autonomously selects resources. For example, in the case of the relay UE autonomously selecting resources, the network device configures QoS parameters for the relay UE. When the relay UE is simultaneously handling services on both the Uu and PC5 interfaces and transmission conflicts occur, the relay UE needs to make a choice based on pre-configured priority thresholds and local decision-making. It is evident that the network device cannot control the service transmission on the Uu and PC5 interfaces, and there may be a significant discrepancy between the priority determined by the relay UE based on the pre-configured priority thresholds and the priority included in the QoS parameters configured by the network device.

[0133] For example, if a relay UE determines that the priority of a service on the Uu link is higher than the priority threshold, the relay UE will prioritize the transmission of services on the Uu link; otherwise, the relay UE will prioritize the transmission of services on the PC5 link. However, when the network device assigns a higher priority to services on the latency-sensitive PC5 link, if the relay UE determines that the priority of a service on the Uu link is higher than the priority threshold, the relay UE will prioritize the transmission of services on the Uu link, thus failing to meet the latency requirements of services on the latency-sensitive PC5 link.

[0134] To address the issue that terminal devices in RRC inactive state cannot receive QoS parameters configured by access network devices, this application provides a communication method. After the access network device determines the QoS parameters of each hop in a multi-hop path, it sends configuration information and first indication information to a first user equipment (User Equipment) in RRC connected state. Upon receiving the configuration information and first indication information, the first User Equipment sends a first message carrying the QoS parameters of the first path to a second User Equipment. The configuration information is used to configure the QoS parameters of the first path. The first path is the path between the second User Equipment and the first User Equipment in RRC inactive state. The first indication information instructs the first User Equipment to send the QoS parameters of the first path to the second User Equipment. This allows the second User Equipment in RRC inactive state to also obtain the QoS parameters of its path, improving the reliability of data transmission in multi-hop paths and enhancing end-to-end service quality.

[0135] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of this interactive illustration to illustrate the method, but this application does not limit the execution subjects of the interactive illustrations. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software that can implement all or part of the functions of the device.

[0136] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0137] Figure 3 This is a flowchart illustrating a communication method provided in an embodiment of this application. It can be understood that... Figure 3 The first user equipment in the process can be Figure 1The second relay UE130 can also refer to devices within the second relay UE130 (such as processors, chips, or chip systems). The second user equipment can be... Figure 1 The remote UE140 in the network can be a device within the remote UE140 (such as a processor, chip, or chip system). Access network equipment can be... Figure 1 Any access network device, or a component within an access network device (such as a processor, chip, or chip system). Figure 3 As shown, the communication method includes the following steps S310 and S320.

[0138] S310, the access network device sends configuration information and first indication information to the first user equipment, and the first user equipment receives the configuration information and first indication information accordingly.

[0139] The first user equipment (UE) is a device connected to the second UE and in RRC connection state. Configuration information is used to configure the QoS parameters of the first path. Optionally, the QoS parameters of the first path can be PQIs. In this way, the access network device only needs to send a PQI to the first UE, and the first UE can determine the QoS parameters corresponding to the received PQI based on the received PQI and the mapping relationship between the PQI and QoS characteristics.

[0140] For example, assuming the PQI received by the first user equipment is 6, the first user equipment can determine the QoS parameters of the first path based on the mapping relationship between PQI values ​​and QoS characteristics in Table 2 above. That is, the resource type is GBR, the priority is 18, the packet delay budget is 80ms, and the packet error rate is 10%. -2 .

[0141] The first path is the path between the second user equipment, which is in an RRC inactive state, and the first user equipment. For example, as follows... Figure 1 As shown, assuming that the first relay UE120 and the second relay UE130 are both in RRC connected state, and the remote UE140 is in RRC inactive state, then the first user equipment is the second relay UE130, the second user equipment is the remote UE140, and the first path is the path between the remote UE140 and the second relay UE130.

[0142] The first instruction information is used to instruct the first user equipment to send the QoS parameters of the first path to the second user equipment.

[0143] In some embodiments, after receiving the end-to-end QoS parameters configured by the core network device for the PDU session established for the remote UE, the access network device allocates the end-to-end QoS parameters to each hop in the multi-hop path, obtaining the QoS parameters for each hop. The access network device can send the QoS parameters of the path corresponding to the terminal device to all terminal devices in the RRC connected state in the multi-hop path. When there is a terminal device in the RRC inactive state (e.g., a second user equipment) in the multi-hop path, the access network device can send the QoS parameters of the first path to the first user equipment connected to the second user equipment in the RRC connected state, and instruct the first user equipment to send the QoS parameters of the first path to the second user equipment, so that the second user equipment in the RRC inactive state can receive the QoS parameters of the first path. In this way, when the second user equipment is in the RRC connected state, the second user equipment can perform data transmission based on the QoS parameters of the first path.

[0144] It should be noted that the specific implementation of the access network device allocating end-to-end QoS parameters to each hop in the multi-hop path and obtaining the QoS parameters of each hop path can be found in the description in the subsequent embodiments, and will not be described in detail here.

[0145] In this embodiment, the access network device may send configuration information to the first user equipment to configure the QoS parameters of the first path and the QoS parameters of the path between the first user equipment and its preceding hop terminal device (hereinafter referred to as the second path). Alternatively, the access network device may send two configuration information to the first user equipment: one configuration information for configuring the QoS parameters of the first path and the other configuration information for configuring the QoS parameters of the second path. In this embodiment, the number of configuration information messages sent by the access network device to the first user equipment to configure the QoS parameters of the first and second paths is not limited.

[0146] For example, as Figure 1As shown, access network device 110 determines the QoS parameter A for the path between the first relay UE 120 and access network device 110, the QoS parameter B for the path between the second relay UE 130 and the first relay UE 120, and the QoS parameter C for the path between the remote UE 140 and the second relay UE 130. Assuming the first relay UE 120 and the second relay UE 130 are in RRC connected state, and the remote UE 140 is in RRC inactive state, access network device 110 sends configuration information A to the first relay UE 120, which is used to configure QoS parameter A. Access network device 110 sends configuration information B to the second relay UE 130, which is used to configure QoS parameter B. Since the remote UE 140 is in RRC inactive state, access network device 110 cannot directly send data to the remote UE 140. Therefore, access network device 110 can send QoS parameter C and indication information A to the second relay UE 130. Specifically, indication information A is used to instruct the second relay UE130 to send QoS parameter C to the remote UE140. That is, configuration information B is used not only to configure QoS parameter B, but also to configure QoS parameter C.

[0147] Assuming the first relay UE 120 is in RRC connected state and the second relay UE 130 is in RRC inactive state, the access network device 110 sends configuration information D and indication information B to the first relay UE 120. Configuration information D configures QoS parameters A and B, and indication information B instructs the first relay UE 120 to send QoS parameter B to the second relay UE 130, enabling the second relay UE 130, in its RRC inactive state, to obtain QoS parameter B. When the second relay UE 130 is in RRC connected state, data transmission can be performed based on QoS parameter B. Because the second relay UE 130 is in RRC inactive state, there is no RRC connection between the remote UE 140 and the second relay UE 130, resulting in the remote UE 140 being unable to obtain QoS parameter C.

[0148] Alternatively, the access network device 110 sends configuration information E, configuration information F, and indication information B to the first relay UE 120, wherein configuration information E is used to configure QoS parameter A, and configuration information F is used to configure QoS parameter B.

[0149] In this embodiment of the application, the access network device not only configures the corresponding QoS parameters for each hop path in the multi-hop path, but also configures the corresponding priority information for each hop path. For example, the access network device can configure a higher priority for the path that transmits high-priority services, so that high-priority services in the multi-hop path are transmitted first, which helps to reduce service transmission latency and improve the reliability of service transmission.

[0150] Optionally, the configuration information received by the first user equipment is used not only to configure the QoS parameters of the first path, but also to configure the priority information of the first path. Therefore, when the second user equipment is in RRC connected state, it considers both the QoS parameters and priority information of the first path simultaneously when transmitting data, which helps improve the reliability of data transmission.

[0151] It should be noted that when the access network device configures priority information for each hop in a multi-hop path, the access network device can configure a higher priority for the Uu hop path to avoid the transmission performance of the entire transmission path being affected due to insufficient resources in the last hop.

[0152] In this embodiment, after determining the QoS parameters of each hop in a multi-hop path, the access network device can send the configuration information of the corresponding path to all terminal devices in the RRC connection state via an RRC connection reconfiguration message (e.g., RRCConnectionReconfiguration). For example, the access network device sends configuration information to the first user equipment via RRCConnectionReconfiguration, meaning the configuration information is carried in the RRC connection reconfiguration message. Therefore, by carrying the configuration information in the RRC connection reconfiguration message, the access network device avoids sending configuration information separately to the first user equipment, thus improving transmission efficiency and resource utilization.

[0153] S320, the first user equipment sends a first message to the second user equipment based on the first instruction information, and the corresponding second user equipment receives the first message.

[0154] The first message carries the QoS parameters for the first path.

[0155] In this embodiment, since the first user equipment and the second user equipment transmit data via a PC5 interface, the first user equipment can send a first message to the second user equipment via PC5 RRC signaling. That is, the first message is carried within the PC5 RRC signaling. When the first user equipment sends the first message to the second user equipment via PC5 RRC signaling, the second user equipment, upon receiving the PC5 RRC signaling, can obtain the QoS parameters of the first path. When the second user equipment is in RRC connected state, it can perform data transmission based on the QoS parameters of the first path carried in the first message.

[0156] This can be understood as the first user equipment (UE) instructing the second UE on its identification information and the QoS parameters of the first path based on the information carried in the fields of the PC5 RRC signaling. In this way, the first UE can determine the terminal device to receive the QoS parameters based on the second UE's identification information and then send a first message to the second UE via PC5 RRC signaling.

[0157] The identification information of the second user equipment refers to a unique identifier used to identify the second user equipment. For example, the identification information of the second user equipment can be a layer 2 identity (L2 ID), a globally unique temporary identifier (GUTI), a subscription permanent identifier (SUPI), a permanent equipment identifier (PEI), etc. In this application embodiment, the identification information of the second user equipment is not limited, and any identifier that can identify the second user equipment is applicable to this application.

[0158] Among them, the Layer 2 identifier is the link layer identifier of the PC5 interface or Uu interface, which can be used to identify each hop path or each hop path's terminal device. GUTI refers to the temporary identifier assigned by the core network equipment. SUPI refers to the unique permanent identifier for each user in the network. PEI refers to the globally unique device identifier, used to identify the hardware of the terminal device.

[0159] In some embodiments, the PC5 RRC signaling includes a first field. This first field is used to indicate the identification information of the second user equipment and the QoS parameters of the first path. Thus, by adding a first field to the PC5 RRC signaling to indicate the identification information of the second user equipment and the QoS parameters of the first path, the scalability of the PC5 RRC signaling and compatibility with new features are achieved.

[0160] For example, the access network device adds a field to the Relay QoS Configuration message to configure the QoS parameters of the first path to the first user equipment. After receiving the configuration information and the first indication information, the first user equipment can add a first field to the Direct Communication Request message to indicate the identification information of the second user equipment and the QoS parameters of the first path. For example, the first field may include the Layer 2 identifier of the second user equipment and the pre-configured PQI.

[0161] In other embodiments, the first field described above is further used to indicate the priority information of the first path and / or the validity duration of the QoS parameters of the first path. The validity duration of the QoS parameters of the first path refers to the duration during which the QoS parameters of the first path can be used by the second user equipment, starting from the moment the second user equipment receives the QoS parameters of the first path. This validity duration can be an absolute time, a relative time, etc., and is not limited thereto.

[0162] In other words, in addition to indicating the identification information of the second user equipment and the QoS parameters of the first path, the first field is also used to indicate the priority information of the first path and / or the validity period of the QoS parameters of the first path. The first user equipment indicates the priority information of the first path and / or the validity period of the QoS parameters of the first path through the first field added in the PC5 RRC signaling, without the need to create new signaling. This not only improves compatibility with the existing network architecture, but also reduces the workload of redeveloping new signaling and interaction procedures.

[0163] In this embodiment, the second user equipment (UAE) is equipped with a first timer, the duration of which is equal to the validity period of the QoS parameters of the first path. Upon receiving a first message, the second UAE starts the first timer. During the operation of the first timer, when the second UAE is in an RRC connection state, the second timer performs data transmission based on the QoS parameters of the first path. When the first timer times out, even if the second UAE is in an RRC connection state, it cannot perform data transmission based on the QoS parameters of the first path. Therefore, by setting the first timer, the second UAE only performs data transmission based on the QoS parameters of the first path during the operation of the first timer and when it is in an RRC connection state, avoiding the problem of the second UAE using the QoS parameters of the first path for data transmission outside the validity period, thus affecting the reliability of data transmission.

[0164] For example, assuming the validity period of the QoS parameters for the first path is 10 seconds (s), after receiving the first message, the second user equipment starts a first timer in response to receiving the first message. The duration of the first timer is 10 seconds. The second user equipment can perform data transmission based on the QoS parameters of the first path while in RRC connected state for 10 seconds.

[0165] In this embodiment, when the first field is not used to indicate the validity period of the QoS parameters for the first path, the QoS parameters for the first path received by the second user equipment can remain valid until the next time the network-configured QoS parameters for the first path are received. Therefore, compared to pre-configured QoS parameters, the second user equipment uses the latest configured QoS parameters for data transmission, which helps improve the reliability and stability of data transmission.

[0166] In summary, in this embodiment, after receiving configuration information and first indication information from the access network device, the first user equipment (User Equipment) in RRC connected state sends a first message carrying QoS parameters of the first path to the second user equipment (User Equipment). Upon receiving the QoS parameters of the first path, the second user equipment, while in RRC connected state, can transmit data based on these parameters. This allows the second user equipment in RRC inactive state to obtain the QoS parameters of its path, improving the reliability of data transmission in multi-hop paths. Furthermore, the first user equipment only needs to forward the QoS parameters of the first path to the second user equipment based on the first indication information, without participating in the determination of QoS parameters for each hop path, significantly reducing the computational burden on the first user equipment and improving the efficiency of QoS parameter configuration for each hop path.

[0167] In this embodiment of the application, the access network device can allocate end-to-end QoS parameters based on the multi-hop path context information of the remote UE, thereby obtaining the QoS parameters of each hop in the multi-hop path. The following is in conjunction with... Figure 4 This paper provides a detailed introduction to the specific implementation of establishing multi-hop path context information for remote UEs, and allocating end-to-end QoS parameters based on the multi-hop path context information to obtain the QoS parameters of each hop in the multi-hop path. Figure 4 A flowchart illustrating another communication method provided in an embodiment of this application is shown below. Figure 4 As shown, the method may include the following steps S410 to S470.

[0168] S410, the remote UE sends a first request message to the access network device, and the corresponding access network device receives the first request message.

[0169] The first request message is used to request network access via a multi-hop relay. This first request message can be replaced by the relay access request message described in S201 above. For a detailed description of the first request message, please refer to the description of the relay access request message in S201 above, which will not be repeated here.

[0170] In this embodiment of the application, the specific implementation of the remote UE sending the first request message to the access network device can also refer to the description of the remote UE sending the relay access network request message to the access network device in S201 above, and will not be repeated here.

[0171] S420, the access network device sends a second request message to the core network device, and the core network device receives the second request message accordingly.

[0172] In this embodiment, after receiving the first request message, the access network device interacts with the core network device to establish a PDU session for the remote UE. Upon receiving the first request message, the core network device encapsulates the initial service requirement information carried in the first request message into a second request message (e.g., a non-access stratum (NAS) message) and sends the second request message to the core network device. The second request message is used to request the establishment of a PDU session for the remote UE. After receiving the second request message, the core network device interacts with the access network device to establish the PDU session for the remote UE and then configures end-to-end QoS parameters for the PDU session.

[0173] The specific implementation of configuring end-to-end QoS parameters for the PDU session established by the core network equipment for the remote UE can be found in the description of S203 above, and will not be repeated here.

[0174] S430, core network equipment establishes core network context information. This core network context information includes end-to-end QoS parameters.

[0175] The core network context information refers to the context information of the remote UE generated by the core network equipment. The specific implementation of establishing the core network context information by the core network equipment can refer to existing technologies and will not be elaborated upon here.

[0176] In this embodiment, after receiving a context establishment request message from the access network device, the core network device establishes core network context information. This core network context information includes not only PDU session information and end-to-end QoS parameters, but also end-to-end QoS profiles and device information of the remote UE.

[0177] The end-to-end QoS profile is a standardized set of QoS features defined by 3GPP standards, used to provide a unified QoS description of service flows. The end-to-end QoS profile includes 5QIs and the corresponding QoS features for each 5QI. For example, the end-to-end QoS profile may include multiple values ​​for the 5QIs listed in Table 1 above and the corresponding QoS features for each 5QI.

[0178] The device information of the remote UE includes its identification information, capability information, and status information. Capability information includes hardware capabilities (e.g., supported frequency bands and bandwidth), processing capabilities (e.g., processing unit performance), battery level, and relay access capabilities. Status information refers to the remote UE's RRC connection status, PDU session status, and battery status. Optionally, the remote UE may send a first request message containing its device information to the access network device. The access network device then sends a second request message to the core network device. Upon receiving the second request message, the core network device obtains the remote UE's device information.

[0179] S440, the core network device sends core network context information to the access network device, and the access network device receives the core network context information accordingly.

[0180] S450, the access network device establishes multi-hop path context information for the remote UE based on the core network context information.

[0181] Among them, the multi-hop path context information is the initial context information of the remote UE established by the access network device.

[0182] In this embodiment, after receiving the core network context information, the access network device establishes multi-hop path context information for the remote UE based on the core network context information. The multi-hop path context information includes partial information from the core network context information (such as end-to-end QoS parameters), path topology information, channel quality of each hop in the multi-hop path, and capability information of each terminal device in the multi-hop path. At this point, the multi-hop path context information is a preliminary and incomplete set of context information.

[0183] The path topology information includes the number of hops in the multi-hop path, the device information of each relay UE arranged in hop-number order, and the RRC connection status of each relay UE. For example, as shown below... Figure 1 As shown, the number of hops in the multi-hop path is 3. The two relay UEs are arranged in hop order as the second relay UE130 and the first relay UE120. Assuming that the RRC connection state of the second relay UE130 is connected and the RRC connection state of the first relay UE120 is connected, then... Figure 1 The path topology information of the multi-hop path includes the device information of the second relay UE130 and the first relay UE120, which have a hop count of 3 and are arranged in hop count order. The RRC connection status of the second relay UE130 and the first relay UE120 is connected.

[0184] In a multi-hop path, the channel quality of each hop is determined by the access network equipment based on the measurement reports reported by each relay UE. The channel quality of each hop can be measured by at least one of the following parameters: reference signal received power (RSRP), reference signal received quality (RSRQ), or signal to interference plus noise ratio (SINR).

[0185] For example, as Figure 1 As shown, the channel quality of the path between the remote UE140 and the second relay UE130 can be measured by the second relay UE130. Then, the second relay UE130 reports a measurement report to the access network device 110, which includes the channel quality of the path between the remote UE140 and the second relay UE130. Optionally, the remote UE140 sends a measurement reference signal to the second relay UE130. The second relay UE130 measures the measurement reference signal in real time or periodically on the PC5 interface. After obtaining the measurement result, the second relay UE130 sends the measurement result in a measurement report back to the access network device 110.

[0186] S460: The access network device allocates and maps end-to-end QoS parameters based on multi-hop path context information to obtain the QoS parameters for each hop path.

[0187] In this embodiment, the control plane unit of the access network device allocates and maps end-to-end QoS parameters based on multi-hop path context information to obtain the QoS parameters for each hop path.

[0188] In some embodiments, since the multi-hop path includes a Uu link and at least one PC5 link, when the access network device configures the PDU in the QoS parameters for the multi-hop path, the access network device can configure the PDB of the Uu link, obtain the remaining PDB budget, and then configure the PDB of at least one PC5 link according to the remaining PDB budget. The remaining PDB budget is the PDB remaining after allocating the end-to-end PDB to the Uu link.

[0189] When a multi-hop path includes a PC5 link, the remaining PDB budget is the PDB of that PC5 link.

[0190] In the case where a multi-hop path includes multiple PC5 links, the access network device allocates the remaining PDB budget to obtain the PDB for each PC5 link among the multiple PC5 links.

[0191] In this application embodiment, the access network device allocates the remaining PDB budget to obtain the specific implementation of PDB for multiple PC5 links, including at least the following two implementation methods.

[0192] In the first implementation, the access network device can evenly distribute the remaining PDB budget across multiple PC5 links, resulting in a PDB for each of the multiple PC5 links. In other words, the access network device configures the same PDB for multiple PC5 links. Therefore, by evenly distributing the remaining PDB budget, the access network device configures the same PDB for each of the multiple PC5 links, and the reliability of the multiple PC5 links is determined by the strongest PC5 link, improving end-to-end service quality and reliability. Furthermore, the access network device does not need to perform complex PDB allocation calculations for each PC5 link, reducing the processing load on the access network device and saving resource consumption.

[0193] For example, still using Figure 1 Taking multi-hop paths in the example, Figure 1 The multi-hop paths include the PC5 link between remote UE140 and the second relay UE130, the PC5 link between the second relay UE130 and the first relay UE120, and the Uu link between the first relay UE120 and the access network device 110. Assume that the end-to-end QoS parameters configured by access network device 110 for the PDU session established for remote UE140 include an end-to-end PDB of 100ms. Access network device 110 allocates a PDB of 20ms to the Uu link between the first relay UE120 and access network device 110, and the remaining PDB budget includes a remaining PDB of 80ms. Since the multi-hop path includes two PC5 hop paths, access network device 110 can evenly distribute the remaining PDB across these two PC5 links, that is, allocating a PDB of 40ms to the PC5 link between remote UE140 and the second relay UE130, and also allocating a PDB of 40ms to the PC5 link between the second relay UE130 and the first relay UE120.

[0194] Optionally, the access network device 110 may also allocate 35ms of PDB for the PC5 link between the remote UE 140 and the second relay UE 130, and also allocate 35ms of PDB for the PC5 link between the second relay UE 130 and the first relay UE 120. Then, the access network device 110 uses the remaining 10ms of PDB as redundancy for processing and handover to ensure the reliability and stability of data transmission.

[0195] In the second implementation, the access network device can allocate the remaining PDB budget based on the channel quality of multiple PC5 links and / or the capability information of each relay UE, thus obtaining the PDB for each PC5 link. It is evident that by configuring the PDB of each PC5 link differently, the access network device can improve resource utilization.

[0196] For example, still using Figure 1 Taking a multi-hop path as an example, assuming that the end-to-end QoS parameters configured by access network device 110 for the PDU session established for remote UE 140 still include an end-to-end PDB of 100ms. Access network device 110 allocates a PDB of 20ms for the Uu link between the first relay UE 120 and access network device 110, and the remaining PDB budget includes a remaining PDB of 80ms. Assuming that the channel quality of the PC5 link between remote UE 140 and the second relay UE 130 is higher than that of the PC5 link between the second relay UE 130 and the first relay UE 120, then access network device 110 can allocate a PDB of 20ms for the PC5 link between remote UE 140 and the second relay UE 130, and a PDB of 50ms for the PC5 link between the second relay UE 130 and the first relay UE 120. Access network device 110 uses the remaining 10ms of PDB as redundancy for processing and handover.

[0197] Optionally, the access network device can allocate the remaining PDB budget based on the capability information of each relay UE in multiple PC5 links, and configure different PDBs for PC5 links where relay UEs with different capabilities reside.

[0198] For example, still using Figure 1 Taking a multi-hop path as an example, assuming that the remaining PDB budget includes 80ms of remaining PDB, and the relay access capability of the remote UE140 is higher than that of the second relay UE130, then the access network device 110 can allocate 20ms of PDB for the PC5 link between the remote UE140 and the second relay UE130, and allocate 50ms of PDB for the PC5 link between the second relay UE130 and the first relay UE120. The access network device 110 uses the remaining 10ms of PDB as redundancy for processing and handover.

[0199] Optionally, the access network device can simultaneously allocate the remaining PDB budget based on the channel quality of multiple PC5 links and the capability information of each relay UE, thereby obtaining the PDB of each PC5 link among the multiple PC5 links.

[0200] For example, assuming the remaining PDB budget includes 80ms of PDB, and the battery level of the remote UE 140 is lower than that of the second relay UE 130, but the channel quality of the PC5 link between the remote UE 140 and the second relay UE 130 is higher than that of the PC5 link between the second relay UE 130 and the first relay UE 120, then the access network device 110 can allocate 40ms of PDB for the PC5 link between the remote UE 140 and the second relay UE 130, and 30ms of PDB for the PC5 link between the second relay UE 130 and the first relay UE 120. The access network device 110 uses the remaining 10ms of PDB as redundancy for processing and handover. This allows the remote UE 140, with its lower battery level, to transmit data within a limited battery capacity.

[0201] In another implementation, the access network device can input multi-hop path context information into the QoS allocation model, and the QoS allocation model can output the QoS parameters for each hop path.

[0202] Since the QoS allocation model is pre-trained, it can allocate QoS parameters to each hop path more accurately and efficiently. Therefore, it helps to improve the rationality and efficiency of QoS parameter allocation, enabling each hop path to transmit data efficiently and reliably based on the configured QoS parameters.

[0203] In this embodiment, the control plane unit of the access network device determines the QoS parameters of each hop path and generates a context establishment request message. The context establishment request message carries the QoS parameters allocated for the paths managed by the distributed unit. The context establishment request message is used to request the distributed unit to allocate and manage radio resources for data transmission for the remote UE. A new context information element field is added to the context establishment request message, which carries path topology information and the QoS parameters of each hop path. For example, the context establishment request message carries a Multi-hop Path Context field, which carries path topology information and the QoS parameters of each hop path.

[0204] Optionally, after determining the QoS parameters for each hop path, the control plane unit of the access network device fills the QoS parameters and path topology information of each hop path into the corresponding positions in the context information element field and sends it to the distributed unit. Thus, without modifying existing protocol standards, the control plane unit adds a context information element field to the context establishment request message. By carrying the QoS parameters of each hop path in the newly added context information element field, dynamic configuration of the QoS parameters for each hop path can be achieved.

[0205] Optionally, the context information element field can also carry the channel quality of each hop in the multi-hop path. This allows the access network device to receive the channel quality of each hop when allocating end-to-end QoS parameters, taking the channel quality of each hop into account. This enables terminal devices in the multi-hop path to transmit data efficiently and reliably based on the allocated QoS parameters.

[0206] After generating a context establishment request message, the control plane unit sends a context establishment request message to the distributed unit. Upon receiving the context establishment request, the distributed unit obtains the QoS parameters allocated to the paths under its jurisdiction.

[0207] Optionally, when the access network device includes multiple distributed units, the control plane unit allocates and maps end-to-end QoS parameters based on multi-hop path context information. After obtaining the QoS parameters for each hop path, the control plane unit can send the QoS parameters of the paths managed by each distributed unit to each distributed unit through the F1 interface. The control plane unit does not need to send the QoS parameters of each hop path to all distributed units, thereby avoiding information redundancy in the parameter transmission process and saving transmission resources.

[0208] For example, assuming the access network device includes three distributed units, namely distributed unit A, distributed unit B, and distributed unit C, when the control plane unit sends QoS parameters for the paths managed by distributed unit A to distributed unit A, distributed units B and C will not receive the QoS parameters sent to distributed unit A. After the access network device allocates end-to-end PDUs to the Uu link and each PC5 link, the access network device can directly map 5QI to the data radio bearers of the Uu link and PC5 link. The access network device configures parameters such as the logical channel mode and logical channel priority of the DRB according to the characteristics corresponding to 5QI. The access network device maps 5QI to the PQI corresponding to each PC5 link according to the standardized mapping table between 5QI and PQI or local configuration. The relay UE corresponding to the PC5 link can determine the QoS characteristics corresponding to the PC5 link based on the mapping relationship between PQI and QoS characteristics in Table 2 above.

[0209] For example, suppose the access network device is configured with end-to-end QoS parameters including 5QI of 1, resource type of GRB, end-to-end PDB of 100ms, and packet error rate of 10. -2 Access network equipment can allocate end-to-end PDBs to Uu links and each PC5 link. The specific allocation method can refer to any of the allocation methods described above.

[0210] Access network devices can directly use the QoS features corresponding to 5QI as 1 to configure DRB. Then, assuming the access network device maps 5QI as 1 to PQI as 3 according to the standardized mapping table between 5QI and PQI, it configures the QoS features corresponding to PQI as PC5 link.

[0211] In this embodiment of the application, the specific implementation of mapping end-to-end QoS parameters to QoS parameters of each PC5 link can be referred to the prior art, and will not be described in detail here.

[0212] S470, the access network device sends configuration information and first indication information to the first UE.

[0213] In this embodiment, the access network device allocates end-to-end QoS parameters. After obtaining the QoS parameters for each hop path, the access network device sends corresponding configuration information to the terminal device in the RRC connection state to configure the QoS parameters of the path where the terminal device in the RRC connection state is located.

[0214] Optionally, if a second UE in an RRC inactive state exists in the multi-hop path, the access network device can send configuration information and a first indication information to the first UE in the last hop of the multi-hop path that is in an RRC connected state. After receiving the configuration information and the first indication information, the first UE sends a first message carrying the QoS parameters of the first path to the second UE. For the specific implementation of the first UE sending the first message to the second UE, please refer to the description of S420 above, which will not be repeated here.

[0215] In summary, after establishing the multi-hop path context information for remote UEs, the access network device allocates end-to-end QoS parameters based on this context information, obtaining the QoS parameters for each hop path. It is evident that the access network device dynamically allocates QoS parameters to the Uu link and each PC5 link based on the channel quality of each hop path, the relay UE's capability information, and overall service requirements, thereby improving end-to-end service quality and avoiding the problem of overall performance degradation caused by local optimization. When configuring QoS parameters for terminal devices in the multi-hop path, the access network device considers the RRC connection state of the terminal devices. By instructing the terminal device in the last hop of the multi-hop path that is in the RRC connection state to forward the QoS parameters of the active terminal device, it avoids the problem that the active terminal device cannot receive the QoS parameters configured by the access network device, thus preventing data transmission based on the dynamically configured QoS parameters and affecting end-to-end service quality.

[0216] It should be understood that Figures 1 to 4 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 4The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0217] The above text combined Figures 1 to 4 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figures 5 to 6 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0218] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; 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 embodiments of this application.

[0219] Figure 5 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 5 As shown, the communication device may include a communication module 520. The communication module 520 can implement corresponding communication functions, which can be internal communication functions of the communication device or communication functions between the communication device and other devices. Optionally, the communication module 520 may also be referred to as a communication interface or transceiver module. Optionally, the communication device further includes a processing module 510. The processing module 510 can implement corresponding processing functions.

[0220] Optionally, the communication device further includes a storage module, which can be used to store instructions and / or data; the processing module 510 can read the instructions and / or data in the storage module so that the communication device can implement the aforementioned method embodiments.

[0221] In one possible design, the communication device may correspond to the first user equipment in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the first user equipment. The communication device can be used to perform the steps or processes executed by the first user equipment in any of the above method embodiments.

[0222] For example, the communication module 520 is used to receive configuration information and first indication information from the access network device; wherein, the configuration information is used to configure the QoS parameters of the first path; the first path is the path between the second user equipment in the RRC inactive state and the first user equipment; the first indication information is used to instruct the first user equipment to send the QoS parameters of the first path to the second user equipment.

[0223] The communication module 520 is also used to send a first message to the second user equipment based on the first indication information, wherein the first message carries QoS parameters of the first path.

[0224] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0225] In one possible design, the communication device may correspond to the second user equipment in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the second user equipment. The communication device can be used to perform the steps or processes executed by the second user equipment in any of the above method embodiments.

[0226] The communication module 520 is used to receive a first message from the first user equipment when the second user equipment is in an RRC inactive state; wherein the first message carries QoS parameters of a first path, the first path being the path between the second user equipment and the first user equipment; and when the second user equipment is in an RRC connected state, data transmission is performed based on the QoS parameters of the first path.

[0227] In one possible design, the communication device may correspond to the access network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the access network device. The communication device can be used to perform the steps or processes executed by the access network device in any of the above method embodiments.

[0228] For example, the communication module 520 is used to receive end-to-end QoS parameters configured for a PDU session established for a remote UE from the core network equipment.

[0229] The processing module 510 is used to allocate end-to-end QoS parameters to each hop path in the multi-hop path to obtain the QoS parameters of each hop path; wherein, the multi-hop path includes a first path, which is a path between a second user equipment in an inactive state and a first user equipment, and the first user equipment is the last hop terminal equipment in the connected state in the multi-hop path.

[0230] The communication module 520 is also used to send configuration information and first indication information to the first user equipment; wherein, the configuration information is used to configure the QoS parameters of the first path, and the first indication information is used to instruct the first user equipment to send the QoS parameters of the first path to the second user equipment.

[0231] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0232] Figure 6 This is a schematic block diagram of another communication device provided in an embodiment of this application. The communication device may be a chip, chip system, or processor, etc., in a terminal device or network device that implements the above-described method. This communication device can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0233] like Figure 6 As shown, the communication device may include one or more processors 610, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 610 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device (e.g., base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0234] In an alternative design, the processor 610 may also store instructions and / or data that can be executed by the processor 610 to cause the communication device to perform the methods described in the above method embodiments.

[0235] In another alternative design, the communication device may include a communication interface 620 for implementing receiving and transmitting functions. For example, the communication interface 620 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0236] Optionally, the communication device may include one or more memories 630, which may store instructions that can be executed on the processor 610 to cause the communication device to perform the methods described in the above method embodiments. Optionally, the memories 630 may also store data. Optionally, the processor 610 may also store instructions and / or data. The processor 610 and the memories 630 may be provided separately or integrated together.

[0237] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0238] In one implementation, the communication device may correspond to the first user equipment or the second user equipment in the above method embodiments, and may be used to execute the various steps and / or processes executed by the first user equipment or the second user equipment in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the first user equipment or the second user equipment.

[0239] In another implementation, the communication device may correspond to the access network device in the above method embodiments, and may be used to execute the various steps and / or processes executed by the access network device in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the access network device.

[0240] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0241] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0242] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0243] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0244] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned access network equipment, first user equipment, second user equipment, and core network equipment.

[0245] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the core network device, the first user equipment, and the second user equipment in any of the foregoing method embodiments.

[0246] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code. When the program code is run on a computer, it causes the computer to execute the various steps or processes performed by the core network device, the first user equipment, and the second user equipment in any of the foregoing method embodiments.

[0247] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0248] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0249] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0250] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0251] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. 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 embodiments of this application.

[0252] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method characterized by comprising: The method applied to a first user equipment comprises: receiving configuration information and first indication information from an access network device; wherein the configuration information is used for configuring quality of service (QoS) parameters of a first path; the first path is a path between a second user equipment in a radio resource control (RRC) inactive state and the first user equipment; the first indication information is used for instructing the first user equipment to send the QoS parameters of the first path to the second user equipment; the QoS parameters of the first path are obtained by allocating and mapping end-to-end QoS parameters based on multi-hop path context information; the multi-hop path context information comprises core network context information, path topology information, channel quality of each hop in the multi-hop path, and capability information of each user equipment in the multi-hop path; based on the first indication information, sending a first message to the second user equipment, wherein the first message carries the QoS parameters of the first path.

2. The method of claim 1, wherein: the first message is carried in PC5 RRC signaling, and the PC5 RRC signaling comprises a first field used for indicating identification information of the second user equipment and the QoS parameters of the first path.

3. The method of claim 2, wherein: the first field is further used for indicating priority information of the first path and / or a validity duration of the QoS parameters of the first path.

4. The method of any one of claims 1-3, wherein: the configuration information is further used for configuring priority information of the first path.

5. The method of any one of claims 1-3, wherein: the configuration information is carried in an RRC connection reconfiguration message.

6. A communication method characterized by comprising: The method applied to a second user equipment comprises: receiving a first message from a first user equipment when the second user equipment is in a radio resource control (RRC) inactive state; wherein the first message carries quality of service (QoS) parameters of a first path between the second user equipment and the first user equipment; the QoS parameters of the first path are obtained by allocating and mapping end-to-end QoS parameters based on multi-hop path context information; the multi-hop path context information comprises core network context information, path topology information, channel quality of each hop in the multi-hop path, and capability information of each user equipment in the multi-hop path; performing data transmission based on the QoS parameters of the first path when the second user equipment is in an RRC connected state.

7. The method of claim 6, wherein: the first message is carried in PC5 RRC signaling, and the PC5 RRC signaling comprises a first field used for indicating identification information of the second user equipment and the QoS parameters of the first path.

8. The method of claim 7, wherein: The first field is further used for indicating priority information of the first path and / or a valid time length of the QoS parameter of the first path.

9. The method of claim 7, wherein, In a case where the second user equipment is in an RRC connected state, the data transmission based on the QoS parameter of the first path comprises: In response to receiving the first message, starting a first timer, a running time of the first timer being the valid time length of the QoS parameter of the first path; During running of the first timer, in a case where the second user equipment is in an RRC connected state, performing data transmission based on the QoS parameter of the first path.

10. A communication method characterized by comprising: Applied to an access network device, the method comprises: Receiving an end-to-end QoS parameter of a protocol data unit (PDU) session configuration established for a remote user equipment from a core network device; Allocating the end-to-end QoS parameter to each hop path in a multi-hop path to obtain a QoS parameter of each hop path, wherein the multi-hop path comprises a first path, the first path being a path between a second user equipment in a radio resource control (RRC) inactive state and a first user equipment in an RRC connected state connected with the second user equipment; Sending configuration information and first indication information to the first user equipment, wherein the configuration information is used for configuring the QoS parameter of the first path, and the first indication information is used for instructing the first user equipment to send the QoS parameter of the first path to the second user equipment.

11. The method of claim 10, wherein, The end-to-end QoS parameter comprises an end-to-end packet delay budget (PDB), and the allocating the end-to-end QoS parameter to each hop path in a multi-hop path to obtain a QoS parameter of each hop path comprises: Allocating the end-to-end QoS parameter based on multi-hop path context information to obtain the QoS parameter of each hop path.

12. The method of claim 11, wherein, The multi-hop path comprises a Uu link and at least one PC5 link, and the allocating the end-to-end QoS parameter based on multi-hop path context information to obtain the QoS parameter of each hop path comprises: Configuring a PDB of the Uu link to obtain a remaining PDB budget; Allocating the remaining PDB budget to at least one PC5 link to obtain a PDB of the at least one PC5 link.

13. The method of claim 12, wherein, The allocating the remaining PDB budget to at least one PC5 link to obtain a PDB of the at least one PC5 link comprises: Equally allocating the remaining PDB budget to at least one PC5 link to obtain a PDB of the at least one PC5 link; or Allocating the remaining PDB budget based on channel quality of the at least one PC5 link and / or capability information of each relay user equipment to obtain a PDB of the at least one PC5 link.

14. The method of claim 11, wherein The QoS parameter of each hop path is obtained by inputting the multi-hop path context information into a QoS allocation model.

15. The method according to any one of claims 11-14, characterized in that, Before the allocating the end-to-end QoS parameter based on the multi-hop path context information to obtain the per-hop path QoS parameter, the method further comprises: receiving a first request message sent by a remote user equipment; wherein, the first request message is used to request to access a network through a multi-hop relay; sending a second request message to the core network device; wherein, the second request message is used to request to establish a PDU session of the remote user equipment; receiving core network context information from the core network device; the core network context information comprises the end-to-end QoS parameter, an end-to-end QoS configuration file and device information of the remote user equipment; based on the core network context information, establishing multi-hop path context information of the remote user equipment; wherein, the multi-hop path context information is used to indicate information required for establishing each hop path in a multi-hop path between the remote user equipment and the access network device, and the multi-hop path context information comprises the core network context information, path topology information, channel quality of each hop path in the multi-hop path and capability information of each user equipment in the multi-hop path; the path topology information comprises the number of hops in the multi-hop path, device information of each relay user equipment arranged in order of hop number and radio resource control (RRC) connection state of each relay user equipment.

16. The method of claim 15, wherein, The access network device comprises a control plane unit and a distributed unit, and the method further comprises: the control plane unit sends a context establishment request message to the distributed unit; wherein, the context establishment request message carries a context information element field, and the context information element field is used to carry the path topology information and the QoS parameter of each hop path.

17. The method of claim 16, wherein, the context information element field is further used to carry the channel quality of each hop path in the multi-hop path.

18. The method of any one of claims 10-14, wherein, the configuration information is further used to configure priority information of the first path.

19. The method of any one of claims 10-14, wherein, the configuration information is carried in an RRC connection reconfiguration message.

20. A communications device comprising one or more processors, memory, and a computer program stored on the memory, wherein the computer program is configured to instruct the one or more processors to perform the method of any one of claims 1-19. The processor executes the computer program to implement the method of any one of claims 1-5; and / or, implement the method of any one of claims 6-9; and / or, implement the method of any one of claims 10-19.

21. A computer readable storage medium having stored thereon computer programs / instructions, characterized in that, The computer program / instruction is executed by the processor to implement the method of any one of claims 1-5; and / or, implement the method of any one of claims 6-9; and / or, implement the method of any one of claims 10-19.

22. A chip system comprising a memory and a processor, characterized in that The program / instruction stored in the memory is executed by the processor to implement the method of any one of claims 1-5; and / or, implement the method of any one of claims 6-9; and / or, implement the method of any one of claims 10-19.

23. A communication system, characterized by comprising a first user equipment, a second user equipment and an access network equipment; wherein the first user equipment is configured to perform the method of any one of claims 1-5; the second user equipment is configured to perform the method of any one of claims 6-9; the access network equipment is configured to perform the method of any one of claims 10-19.

24. A computer program product, characterised in that, The computer program product comprises: a computer program or instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1-5; and / or, implement the method of any one of claims 6-9; and / or, implement the method of any one of claims 10-19.

Images