A method and apparatus for controlling service quality

Abstract

This application provides a method and apparatus for controlling quality of service (QoS). The method includes: determining that the QoS of a first communication link does not meet QoS requirements or that the QoS of the first communication link has changed; wherein the first communication link is a communication link between a relay device and a first terminal device, and the second communication link is a communication link between the relay device and an access network device or between the relay device and a second terminal device, and the first terminal device communicates with the access network device or the second terminal device through the relay device; and sending a first message. By changing the parameters of the QoS of a second communication link according to the QoS of the first communication link, the parameters of the QoS of the second communication link correspond to the QoS of the first communication link, thereby enabling more flexible and accurate control of the QoS of the second communication link.

Description

[0001] This application claims priority to Chinese Patent Application No. 202110117244.8, filed on January 28, 2021, entitled “A method and apparatus for controlling service quality”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more specifically, to a method and apparatus for controlling quality of service. Background Technology

[0003] To improve radio spectrum utilization and provide cellular network services to terminals outside cellular network coverage, cellular communication networks have introduced proximity-based services (ProSe) communication. In ProSe communication, nearby user equipment (UEs) can directly establish communication links without needing to relay communication through a base station. Specifically, in a UE-to-Network Relay architecture, a remote UE can establish a connection with the radio access network (RAN) through a relay device. In a UE-to-UE Relay, two UEs can establish a connection through a relay device, which forwards their respective communication data to both UEs via the PC5 interface.

[0004] When a remote UE connects to a network device or a target UE via a relay device, there are two communication links: the communication link between the remote UE and the relay device, and the communication link between the relay device and the base station RAN or the UE. The data streams of both links are transmitted based on QoS streams. Currently, the base station RAN or the target UE can monitor the communication quality of the communication link between them and the relay device. When the base station RAN or the target UE detects that the radio interface quality cannot meet the requirements, it can notify the core network element SMF to change the corresponding QoS parameters, or change the QoS parameters between the target UE and the relay UE.

[0005] However, the base station RAN or the target UE is unaware of the communication quality of the link between the relay device and the remote UE. When the communication quality between the relay device and the remote UE changes, for example, the base station or the target UE obtains that the communication quality between itself and the relay device meets the requirements, but the communication quality between the relay device and the remote UE does not meet the transmission requirements, the network device or the target UE cannot adjust the corresponding QoS parameters according to the changes because the base station RAN or the target UE cannot obtain the communication quality changes in the other link. Therefore, the end-to-end QoS requirements cannot be guaranteed. Summary of the Invention

[0006] This application provides a method and apparatus for controlling the quality of service (QoS). By changing the parameters of the QoS of a second communication link according to the QoS of a first communication link, the parameters of the QoS of the second communication link correspond to the QoS of the first communication link, thereby controlling the QoS of the second communication link more flexibly and accurately.

[0007] In a first aspect, a method for controlling quality of service (QoS) is provided. The method includes: determining that the QoS of a first communication link does not meet QoS requirements or that the QoS of the first communication link has changed, wherein the first communication link is a communication link between a relay device and a first terminal device, and the first terminal device communicates with the access network device or with a second terminal device through the relay device; and sending a first message, the first message being used to request a change in parameters of the QoS of a second communication link, wherein the second communication link is a communication link between the relay device and the access network device or between the relay device and the second terminal device.

[0008] It should be understood that the determination that the service quality of the first communication link does not meet the service quality requirements or the determination that the service quality of the first communication link has changed in the embodiments of this application can correspond to two situations respectively. The first is that the service quality of the PC5 link does not meet the service quality requirements, that is, when the rate or latency does not reach the threshold, it is triggered; or, the second is that the QoS requirements of the PC5 link have changed, such as the bandwidth requirements of the relay and remote UEs becoming lower, resulting in a decrease in the service quality of the first link.

[0009] By changing the parameters of the service quality of the second communication link according to the service quality of the first communication link, the parameters of the service quality of the second communication link correspond to the service quality of the first communication link, thereby enabling more flexible and accurate control of the service quality of the second communication link.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, determining that the service quality of the first communication link does not meet the service quality requirements includes: detecting that the service quality of the first communication link is lower than a first threshold, the first threshold corresponding to the service quality requirements.

[0011] This application embodiment can determine whether the service quality of the first communication link meets the requirements by directly detecting the service quality of the first communication link. Based on the judgment result, it can further determine to initiate a request to other devices to change the second communication link, thereby overcoming the problem that the network side cannot obtain the service quality of the first communication link, which leads to the inability to meet the communication requirements of the link.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, determining that the service quality of the first communication link does not meet the service quality requirements includes: receiving a second message from the first terminal device, the second message being used to indicate a reduction in the service quality of the first communication link.

[0013] This application embodiment can determine whether the service quality of the first communication link meets the requirements by obtaining information sent by other devices. Based on the judgment result, it can further determine to initiate a request to other devices to change the second communication link, thereby overcoming the problem that the network side cannot obtain the service quality of the first communication link, which leads to the inability to meet the communication requirements of the link.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, determining that the service quality of the first communication link does not meet the service quality requirements includes: receiving a third message from the first terminal device or the relay device, the third message being used to indicate the service quality of the first communication link; and determining that the service quality of the first communication link is lower than a first threshold, the first threshold corresponding to the service quality requirements.

[0015] This application embodiment can determine whether the service quality of the first communication link meets the requirements by obtaining information sent by other devices. Based on the judgment result, it can further determine to initiate a request to other devices to change the second communication link, thereby overcoming the problem that the network side cannot obtain the service quality of the first communication link, which leads to the inability to meet the communication requirements of the link.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, sending the first message includes: sending the first message to a session management network element, wherein the first message is used to reduce the quality of service of the second communication link.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the first message includes a cause value, the cause value indicating that the quality of service of the first communication link needs to be changed.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the first message includes first indication information, which indicates that the reason for the change in the second communication link is that the service quality of the first communication link needs to be changed.

[0019] In conjunction with the first aspect, in some implementations of the first aspect, sending the first message includes: sending the first message to the access network device, the first message being used to indicate a reduction in the quality of service of the second communication link.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the first message further includes at least one of the following: QoS Flow Identifier (QFI), Service Data Flow (SDF) Information, PC5 Link QoS Flow Identifier (PFI), Data Radio Bearer (DRB) Identifier, and Side Link Radio Bearer (SLRB) Identifier.

[0021] It should be understood that the SDF information in the embodiments of this application, namely service data flow (SDF) information, is merely a flow description, which can be a 5-tuple, application identifier, etc. It can be represented as SDF information, or it can be represented as traffic description information, which can specifically include application description information (e.g., application identifier), Internet Protocol (IP) or non-IP description information (e.g., 5-tuple), etc.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, determining that the service quality of the first communication link does not meet the service quality requirements includes: determining that the service quality of the first link is higher than a second threshold, the second threshold corresponding to the service quality requirements.

[0023] By modifying the service parameters of the communication link in a targeted manner according to different service quality requirements, transmission efficiency can be improved and resources can be saved.

[0024] In conjunction with the first aspect, in some implementations of the first aspect, the first message is used to instruct for improving the quality of service of the second communication link.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, determining that the quality of service of the first communication link has changed includes: receiving a fourth message from the first terminal device, the fourth message being used to indicate the addition or removal of the first service flow.

[0026] In conjunction with the first aspect, in some implementations of the first aspect, the fourth message includes at least one of the following: Service Data Flow SDF information, PC5 Link QoS Flow Identifier (PFI).

[0027] In conjunction with the first aspect, in some implementations of the first aspect, the first message is used to indicate the addition or removal of the first service flow.

[0028] In conjunction with the first aspect, in some implementations of the first aspect, the first message includes first indication information, which is used to indicate that the reason for the change of the second communication link is the addition or removal of service flows in the first communication link.

[0029] Secondly, a method for controlling quality of service is provided, the method comprising: a first terminal device determining that the quality of service of a first communication link does not meet the quality of service requirements, the first communication link being a communication link between a relay device and the first terminal device; and sending a first message to the relay device, the first message being used to request a change in the parameters of the quality of service of the first communication link.

[0030] By initiating a change request to the relay device based on the service quality of the first communication link, the relay device can change the service parameters according to the actual situation. Furthermore, it can initiate a process to change the service quality of the second communication link, so that the service quality parameters of the second communication link correspond to the service quality of the first communication link, thereby controlling the service quality of the second communication link more flexibly and accurately.

[0031] Thirdly, a service quality control device is provided, comprising: a processing module, configured to determine that the service quality of a first communication link does not meet service quality requirements, wherein the first communication link is a communication link between a relay device and a first terminal device, and the first terminal device communicates with the access network device or with a second terminal device through the relay device; and a sending module, configured to send a first message, the first message being used to request a change in the service quality parameters of a second communication link, wherein the second communication link is a communication link between the relay device and the access network device or between the relay device and the second terminal device.

[0032] In conjunction with the third aspect, in some implementations of the third aspect, the processing module is specifically used to: detect that the service quality of the first communication link is lower than a first threshold, the first threshold corresponding to the service quality requirement.

[0033] In conjunction with the third aspect, in some implementations of the third aspect, the processing module is specifically used to: receive a second message from the first terminal device, the second message being used to indicate a reduction in the quality of service of the first communication link.

[0034] In conjunction with the third aspect, in some implementations of the third aspect, the processing module is specifically configured to: receive a third message from the first terminal device or the relay device, the third message being used to indicate the service quality of the first communication link; determine that the service quality of the first communication link is lower than a first threshold, the first threshold corresponding to the service quality requirement.

[0035] In conjunction with the third aspect, in some implementations of the third aspect, the sending module is specifically used to: send the first message to the session management network element, wherein the first message is used to reduce the service quality of the second communication link.

[0036] In conjunction with the third aspect, in some implementations of the third aspect, the first message includes a cause value, the cause value indicating that the quality of service of the first communication link needs to be changed.

[0037] In conjunction with the third aspect, in some implementations of the third aspect, the first message includes first indication information, which indicates that the reason for the change in the second communication link is that the service quality of the first communication link needs to be changed.

[0038] In conjunction with the third aspect, in some implementations of the third aspect, the sending module is specifically used to: send the first message to the access network device, wherein the first message is used to indicate a reduction in the quality of service of the second communication link.

[0039] In conjunction with the third aspect, in some implementations of the third aspect, the first message further includes at least one of the following: QoS Flow Identifier (QFI), Service Data Flow (SDF) Information, PC5 Link QoS Flow Identifier (PFI), Data Radio Bearer (DRB) Identifier, and Side Link Radio Bearer (SLRB) Identifier.

[0040] In conjunction with the third aspect, in some implementations of the third aspect, the processing module is specifically used to: determine that the service quality of the first link is higher than a second threshold, the second threshold corresponding to the service quality requirement.

[0041] In conjunction with the third aspect, in some implementations of the third aspect, the first message is used to instruct for improving the quality of service of the second communication link.

[0042] In conjunction with the third aspect, in some implementations of the third aspect, the processing module is specifically used to: receive a fourth message from the first terminal device, the fourth message being used to indicate the addition or removal of the first service flow.

[0043] In conjunction with the third aspect, in some implementations of the third aspect, the fourth message includes at least one of the following: Service Data Flow SDF information, PC5 Link QoS Flow Identifier (PFI).

[0044] In conjunction with the third aspect, in some implementations of the third aspect, the first message is used to indicate the addition or removal of the first service flow.

[0045] In conjunction with the third aspect, in some implementations of the third aspect, the first message includes first indication information, which is used to indicate that the reason for the change of the second communication link is the addition or removal of service flows in the first communication link.

[0046] Fourthly, a quality of service (QoS) control device is provided, comprising: a second processing module for determining that the QoS of a first communication link does not meet QoS requirements, wherein the first communication link is a communication link between a relay device and the device; and a second sending module for sending a first message to the relay device, wherein the first message requests a change in the QoS parameters of the first communication link.

[0047] Fifthly, a communication device is provided, which has the function of implementing the methods described in the above aspects. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0048] In a sixth aspect, a communication device is provided, comprising: a processor; the processor being coupled to a memory for calling and running a computer program from the memory to perform the methods in any possible implementation of the foregoing aspects.

[0049] In a seventh aspect, a communication device is provided, comprising a processor and a memory for storing a computer program, the processor for calling and running the computer program from the memory, causing the communication device to perform the methods in any possible implementation of the foregoing aspects.

[0050] Eighthly, an apparatus (e.g., a system-on-a-chip) is provided, comprising a processor for supporting the communication device in implementing the functions involved in the foregoing aspects. In one possible design, the apparatus further comprises a memory for storing program instructions and data necessary for the communication device. When the apparatus is a system-on-a-chip, it may be composed of chips or may include chips and other discrete devices.

[0051] Ninthly, a computer-readable storage medium is provided for storing a computer program including instructions for performing methods as described in any possible implementation of the foregoing aspects.

[0052] In a tenth aspect, a computer program product is provided, comprising a computer program that, when run on a computer device, causes the computer device to perform the methods described in the above aspects.

[0053] These or other aspects of this application will become more apparent in the following description of the embodiments. Attached Figure Description

[0054] Figure 1 This is a schematic diagram of a 5G ProSe communication architecture.

[0055] Figure 2 This is a schematic diagram of the user plane protocol stack using Layer 2 relay in a UE-to-Network scenario.

[0056] Figure 3 This is a schematic diagram of the user plane protocol stack using Layer 3 relay in a UE-to-Network scenario.

[0057] Figure 4 This is a schematic diagram of a service quality control method according to an embodiment of this application.

[0058] Figure 5 This is a schematic diagram of another service quality control method according to an embodiment of this application.

[0059] Figure 6 This is a schematic diagram of a process in which a relay UE initiates a QoS change request according to an embodiment of this application.

[0060] Figure 7 This is another schematic diagram of the process in which a relay UE initiates a QoS change request in an embodiment of this application.

[0061] Figure 8 This is another schematic diagram of the process in which a relay UE initiates a QoS change request in an embodiment of this application.

[0062] Figure 9 This is a schematic diagram of a process in which a base station initiates a QoS change request according to an embodiment of this application.

[0063] Figure 10 This is a schematic diagram of a process in which a remote UE initiates a QoS change request according to an embodiment of this application.

[0064] Figure 11 This is another schematic diagram of a process in which a remote UE initiates a QoS change request, according to an embodiment of this application.

[0065] Figure 12 This is a schematic diagram of a service quality control device according to an embodiment of this application.

[0066] Figure 13 This is a schematic diagram of another service quality control device according to an embodiment of this application.

[0067] Figure 14 This is a schematic diagram of a service quality control device according to an embodiment of this application.

[0068] Figure 15 This is another structural schematic diagram of a service quality control device according to an embodiment of this application. Detailed Implementation

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

[0070] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) system, 5th Generation (5G) system or New Radio (NR) system, and future evolution communication systems, etc.

[0071] The terminal device in this application embodiment can refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in a 5G network, or terminal device in a future evolved public land mobile network (PLMN), etc., but this application embodiment does not limit this.

[0072] The network device in this application embodiment can be a device for communicating with terminal devices. The network device can be a base station (BTS) in a global system of mobile communication (GSM) or code division multiple access (CDMA) system, a base station (nodeB, NB) in a wideband code division multiple access (WCDMA) system, an evolved NodeB (eNB or eNodeB) in an LTE system, a radio controller in a cloud radio access network (CRAN) scenario, or a relay station, access point, vehicle-mounted device, wearable device, network device in a 5G network, or a network device in a future evolved PLMN network, etc. The embodiments of this application are not limited.

[0073] To improve the utilization of wireless spectrum and provide cellular network services to terminals outside the coverage of cellular networks, cellular communication networks have introduced proximity-based services (ProSe) communication. In ProSe communication, nearby terminal devices can directly establish communication links without having to forward communication through base stations. Figure 1 This diagram illustrates a 5G ProSe communication architecture in the prior art. The network architecture includes terminal devices, access network devices, access management network elements, session management network elements, user plane network elements, policy control network elements, network slice selection network elements, network repository function network elements, network data analysis network elements, unified data management network elements, unified data storage network elements, authentication service function network elements, network capability opening network elements, application function network elements, and a data network (DN) connecting to the operator's network. Terminal devices can send service data to and receive service data from the data network through access network devices and user plane network elements.

[0074] Access network equipment is a device used in a network to connect terminal devices to a wireless network. This access network equipment can be a node in a radio access network, also known as a base station, or a radio access network (RAN) node (or device). Network equipment may include evolved base stations (NodeBs, eNBs, or e-NodeBs) in long-term evolution (LTE) systems or evolved LTE-Advanced (LTE-A) systems, such as traditional macro base stations (eNBs) and micro base stations (eNBs) in heterogeneous network scenarios. It may also include next-generation node Bs (gNBs) in 5th-generation (5G) new radio (NR) systems. Furthermore, it may include radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), transmission reception points (TRPs), home base stations (e.g., home evolved NodeBs or home Node Bs (HNBs), base band units (BBUs), base band pools, or WiFi access points (APs), and may also include cloud radio access networks. The centralized unit (CU) and distributed unit (DU) in the CloudRAN network system are not limited in the embodiments of this application. In the scenario where the access network equipment includes CU and DU deployed separately, the CU supports protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP); the DU mainly supports radio link control (RLC), media access control (MAC) and physical layer protocols.

[0075] Access management network elements are primarily used for terminal attachment, mobility management, and tracking area update procedures in mobile networks. They terminate non-access stratum (NAS) messages, complete registration management, connection management, reachability management, allocate tracking area lists (TAlists), and manage mobility. They also transparently route session management (SM) messages to session management network elements. In 5G communication systems, the access management network element can be an access and mobility management function (AMF). In future communication systems (such as 6G systems), the mobility management network element may remain an AMF element or have other names; this application does not limit this.

[0076] Session management network elements are primarily used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to terminals and selecting user plane network elements that provide packet forwarding capabilities. In 5G communication systems, the session management network element can be a session management function (SMF). In future communication systems (such as 6G communication systems), the session management network element may still be an SMF element, or it may have other names; this application does not limit this.

[0077] User plane network elements are primarily used for processing user packets, such as forwarding, billing, and lawful interception. User plane network elements can also be called protocol data unit (PDU) session anchors (PSAs). In 5G communication systems, user plane network elements can be user plane functions (UPFs). In future communication systems (such as 6G communication systems), user plane network elements may still be UPF elements, or they may have other names; this application does not limit this.

[0078] The policy control network element includes user subscription data management functions, policy control functions, billing policy control functions, and quality of service (QoS) control. In 5G communication systems, the policy control network element can be a policy control function (PCF). In future communication systems (such as 6G communication systems), the policy control network element can still be a PCF network element, or it can have other names; this application is not limited to these.

[0079] The network slice selection function (NSSF) network element is mainly used to select the appropriate network slice for the services of terminal devices. In 5G communication systems, the network slice selection network element can be a network slice selection function (NSSF) network element. In future communication systems (such as 6G communication systems), the network slice selection network element can still be an NSSF network element, or it can have other names. This application does not limit this.

[0080] The network repository function (NRF) network element is mainly used to provide registration and discovery functions for network elements or the services provided by network elements. In 5G communication systems, the network repository function network element can be a network repository function (NRF). In future communication systems (such as 6G communication systems), the network repository function network element can still be an NRF network element, or it can have other names. This application does not limit this.

[0081] Network data analytics elements can collect, analyze, and predict data from various network functions (NFs), such as policy control elements, session management elements, user plane elements, access management elements, and application function elements (through network capability opening function elements). In 5G communication systems, network data analytics elements can be network data analytics functions (NWDAFs). In future communication systems (such as 6G communication systems), network data analytics elements may still be NWDAF elements, or they may have other names; this application is not limiting.

[0082] The unified data management network element is mainly used to manage the subscription information of terminal devices. In 5G communication systems, the unified data management network element can be a unified data management (UDM) network element. In future communication systems (such as 6G communication systems), the unified data management network element can still be a UDM network element, or it can have other names. This application does not limit it.

[0083] A unified data storage network element is primarily used to store structured data information, including subscription information, policy information, and network data or service data with standardized formats. In 5G communication systems, the unified data storage network element can be a unified data repository (UDR). In future communication systems (such as 6G communication systems), the unified data storage network element may still be a UDR network element, or it may have other names; this application does not limit this.

[0084] The authentication service function network element is mainly used for security authentication of terminal devices. In 5G communication systems, the authentication service function network element can be an authentication server function (AUSF). In future communication systems (such as 6G communication systems), the authentication service function network element can still be an AUSF network element, or it can have other names; this application does not limit this.

[0085] Network capability open elements can expose some network functions to applications in a controlled manner. In 5G communication systems, network capability open elements can be network exposure functions (NEF). In future communication systems (such as 6G communication systems), network capability open elements can still be NEF elements, or they can have other names. This application is not limited to these.

[0086] Application function network elements can provide various application service data to the control plane network elements of the operator's communication network, or obtain network data and control information from the control plane network elements of the communication network. In 5G communication systems, application function network elements can be application functions (AF). In future communication systems (such as 6G communication systems), application function network elements can still be AF network elements, or they can have other names; this application is not limited to these.

[0087] Data networks are primarily used to provide data transmission services for terminal devices. Data networks can be private networks, such as local area networks (LANs), public data networks (PDNs), such as the Internet, or dedicated networks jointly deployed by operators, such as configured IP multimedia corenetwork subsystems (IMS) services.

[0088] It should be understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application embodiment does not specifically limit this.

[0089] like Figure 1In the 5G Prose communication architecture diagram shown, the communication between UE A, UE B, and NG-RAN can be regarded as a communication connection under the UE-to-Network Relay architecture. The remote UE (i.e., UE B) can establish a connection with the Radio Access Network (RAN) through the relay device. For example, UE A, UE B, and UE C can be regarded as a communication connection in the UE-to-UE Relay architecture. UE B acts as a relay device (relay UE) between the remote UE (UE C) and UE A, and forwards their respective signaling and data to the two UEs through the PC5 interface.

[0090] In ProSe communication, the remote UE communicates with network devices or the target UE via a relay device. For example... Figure 2 This illustrates the user plane protocol stack for Protocol Data Unit (PDU) session transmission from the UE to the network using Layer 2 relay in a UE-to-Network scenario. For example... Figure 2 As shown, the remote UE is directly connected to the PDU layer of the data network. This can be understood as the data in the application data packet being directly encoded, decoded, and transmitted between these two layers. Data in the PDU layer is encapsulated once by the New Radio-Service Data Adaptation Protocol (NR-SDAP) layer below the remote UE's PDU layer. During this process, the NR-SDAP layer maps the data packet's Quality of Service (QoS) parameters (QoS flow) to the bearer used for physical layer transmission. That is, after encapsulation, the lower layer of the SDAP layer, the Packet Data Convergence Protocol (PDCP) layer, transmits the data packet on the radio bearer (RB) corresponding to the QoS flow allocated by SDAP. NR-SDAP and NR-PDCP are the communication protocols used by the Uu interface. Figure 2As can be seen, the remote UE is directly connected to the NG-RAN's PDCP and SDAP (the SDAP layer in the diagram omits the wiring; in reality, they are connected based on the same protocol layer name. For example, the remote UE's PC5-RLC and the relay's PC5-RLC are connected accordingly, and the relay's NR-RLC is connected to the NG-RAN's NR-radio link control (NR-RLC) layer, and so on. The relay forwarding function can only perform encoding / decoding and forwarding operations of PC5 interface and Uu interface data below the PDCP layer.

[0091] Based on the above processing, when a UE uses a relay connection to the network, data security between the remote UE and the gNB can be ensured without exposing the original data at the UE-to-Network Relay. Simultaneously, the gNB needs to maintain the binding relationship between the remote UE and the relay. This is because when the gNB receives data packets from the remote UE forwarded by the relay, the information below the RLC layer is relay information, while the information above the PDCP layer is remote UE information. When allocating radio resources, the gNB needs to inform the relay UE of the radio resources used for the Uu interface and PC5 interface.

[0092] Figure 3 This illustrates the user plane protocol stack for UE-to-Network PDU session transmission implemented using Layer 3 relay in a UE-to-Network scenario. For example... Figure 3 As shown, the remote UE and the relay use the PC5-U interface for data transmission. After receiving a data packet from the remote UE, the relay decodes the lower layers (Layer 1 and Layer 2) of the packet until it reaches the IP layer (the data content within the IP layer is not decoded). Then, the relay uses the Uu interface's protocol stack to perform Layer 2 and Layer 1 packetization on the remote UE's IP data packets and sends the packets to the UPF via the access network device using the Uu interface. The UPF then forwards the packets to the corresponding application server based on the routing information indicated in the data packets. During this process, the gNB is unaware that the relay is forwarding data from the remote UE; it can be understood as simply providing the relay with traditional Uu interface cellular services.

[0093] In Layer 3 relay, similar to Layer 2 relay, a single relay UE can connect to multiple remote UEs and provide Layer 3 relay forwarding for these remote UEs. However, unlike Layer 2 relay, the PDU session used by Layer 3 relay to forward data for remote UEs is the relay UE's own PDU session. The relay UE maintains the PC5 communication mapping between remote UEs and the Uu communication link mapping between the relay UE and the gNB.

[0094] The user plane protocol stack for Layer 2 and Layer 3 relays in UE-to-UE scenarios is similar to the protocol stack in the UE-to-Network scenario described above. Please refer to existing technologies for details.

[0095] In the ProSe relay communication described above, taking UE-to-network as an example, a remote UE may use different applications (or services) within a single PDU session. These different applications (or services) require different Quality of Service (QoS) parameters. For example, video services require high bandwidth, while voice communication requires reliable low latency. Therefore, the SMF establishes different QoS flows for different services based on the remote UE's communication needs. Each QoS flow is identified by a QoS flow identifier (QFI). The QoS requirements corresponding to the same QoS flow are identical, and these requirements can be quantified using QoS parameters such as latency, bandwidth, and packet loss rate. To facilitate the representation of QoS parameters, the 3GPP standard combines indicators such as latency, packet loss rate, and packet processing priority into a standardized identifier, namely 5QI (5G QoS Identifier). In addition to the QoS parameters indicated in 5QI, depending on the service requirements, the QoS parameters corresponding to each QoS Flow also include allocation and retention priority (ARP), flow bit rate (for QoS Flows with guaranteed flow bit rate (GBR), including guaranteed rate and maximum rate), flow total rate (for QoS Flows with non-guaranteed flow bit rate (Non-GBR), etc.

[0096] After establishing a PDU session, the SMF sends the QFI and corresponding QoS parameters used for downlink data in that PDU session to the base station (e.g., gNB) via an N2 message, and configures it to the UPF via the N4 interface, thereby establishing the downlink data transmission link from the DN to the base station. The uplink data transmission rules (QoS rules) and corresponding QoS parameters used by the UE are sent to the UE by the SMF via an N1 message. In this way, the base station can allocate radio resources to the UE for transmitting different QoS streams based on the QoS parameters. Furthermore, for GBR QoS streams, the SMF can instruct the base station to monitor the channel quality between the UE and the base station. When the channel quality between the UE and the base station does not meet the QoS requirements, the SMF can be notified to adjust the corresponding QoS parameters.

[0097] Specifically, for guaranteed bit rate QoS flows (GBR QoS flows), the base station needs to determine whether the radio resources on the radio side can guarantee the bandwidth requirements corresponding to the GBR QoS flow based on the channel quality between the UE and the base station. When the base station detects that the radio interface quality cannot guarantee the GBR requirements, the base station needs to notify the SMF to change the corresponding GBR QoS requirements. Specifically, the AMF sends the information in the N2 SM container to the base station. The N2 SM information may include: PDU session identifier, QoS configuration information (QFI and its corresponding QoS parameters). For the QoS configuration information, if the QoS flow identified by the QFI is a GBR QoS flow, the SMF can also add a notification control indication to the QoS configuration, instructing the RAN-side base station to monitor the QoS flow. When the air interface transmission rate or bandwidth cannot meet the guaranteed flow bit rate (GFBR), it needs to send a notification (alarm) to the SMF. When informing the SMF that the current GFBR cannot be met, the base station can also attach the currently supported GFBR value, as well as the supported packet delay budget (PDB) and packet error rate (PER).

[0098] In addition, N2 SM information can also include optional QoS configurations (alternative QoS profiles, AQPs). Optional QoS configurations refer to the fact that the SMF can provide multiple sets of corresponding QoS parameters for the base station for the same GBR QoS flow. For example, for GBR QoS flow QFI 1, the corresponding QoS parameters are AQP 1 = {5QI = 1, GFBR = 10Mbps}, AQP 2 = {5QI = 1, GFBR = 8Mbps}, AQP 3 = {5QI = 2, GFBR = 5Mbps}, etc. Among them, 5QI (5G QoS Identifier) ​​is a standardized set of QoS parameters, composed of QoS parameters such as PDB and PER. For example, when 5QI = 1, it indicates that the QoS parameters are: default priority 20, PDB 100ms, PER 0.01, and default average window 2000ms. When SMF is used for AQP at a base station, it indicates the current or default QoS parameter group to be used, such as indicating that the base station's default AQP is AQP 1.

[0099] After the base station obtains the AQP, if it detects that the air interface rate or bandwidth cannot meet the QoS parameters of the current AQP (e.g., GFBR = 10Mbps indicated by AQP1), but can meet the QoS parameters of AQP2, the base station sends an N2 message to the SMF, which includes the QFI and the AQP information that can be met (e.g., AQP2).

[0100] In the PC5 link between the relay UE and the remote UE, the data flow is also based on QoS flow transmission, i.e., PC5 QoS flow. Each PC5 QoS flow is identified by the PC5 link QoS flow indicator (PFI).

[0101] In the above description, since the base station can detect the link quality of the Uu interface between the base station and the UE, when the link quality between the base station and the UE does not meet the communication requirements, the base station can notify the SMF to change the QoS parameters of the Uu interface. However, in scenarios where a remote UE uses a relay UE to communicate with the base station or the UE, i.e., in UE-to-Network or UE-to-UE scenarios, the base station or the core network element SMF cannot know the link quality of the PC5 link between the remote UE and the relay UE. Therefore, when the link quality of the PC5 link between the remote UE and the relay UE cannot guarantee the GBR QoS requirements, the base station cannot notify the SMF to adjust the corresponding QoS parameters of the Uu interface, thus failing to guarantee the bandwidth requirements of the remote UE or the end-to-end QoS requirements.

[0102] Similarly, in a UE-to-UE scenario, the target UE cannot perceive the link quality of the PC5 link between the relay UE and the remote UE. Therefore, when the link quality between the relay UE and the remote UE changes, the target UE cannot adjust the corresponding QoS parameters between the relay UE and the target UE, thus failing to guarantee the bandwidth requirements of the remote UE or the end-to-end QoS requirements.

[0103] This application provides a method for controlling the quality of service (QoS). By modifying the QoS parameters of a second communication link based on the QoS of a first communication link, the QoS parameters of the second communication link correspond to the QoS of the first communication link, thereby enabling more flexible and accurate control of the QoS of the second communication link. This allows a remote UE, relay UE, or base station to initiate a QoS parameter change request for the Uu interface or the PC5 link between the relay UE and the target UE based on the communication quality of the PC5 link. Therefore, when the link quality of the PC5 link between the remote UE and the relay UE does not meet transmission requirements, the network side or the target UE side can simultaneously change the QoS parameters of the Uu interface or the second PC5 link (the link between the relay device and the target UE) and the first PC5 link (the link between the relay device and the remote UE), thus ensuring end-to-end QoS requirements.

[0104] In the embodiments of this application, the first PC5 link can be a PC5 link between the relay device and the remote UE, and the second PC5 link can be a PC5 link between the relay device and the target UE. Alternatively, other names can be used to represent two different links. This application does not limit this.

[0105] Figure 4 This application illustrates a method for changing Quality of Service (QoS) according to an embodiment of the present application. The method 400 includes steps S410 to S420, which are described in detail below.

[0106] S410, determine that the quality of service of the first communication link does not meet the quality of service requirements or determine that the quality of service of the first communication link has changed.

[0107] It should be understood that the determination that the service quality of the first communication link does not meet the service quality requirements or the determination that the service quality of the first communication link has changed in the embodiments of this application can correspond to two situations respectively. The first is that the service quality of the PC5 link does not meet the service quality requirements, that is, when the rate or latency does not reach the threshold, it is triggered; or, the second is that the QoS requirements of the PC5 link have changed, such as the bandwidth requirements of the relay and remote UEs becoming lower, resulting in a decrease in the service quality of the first link.

[0108] Optionally, the embodiments of this application can be applied to a UE-to-UE scenario, that is, a remote UE (i.e., the first terminal device in the embodiments of this application) communicates with a target UE (i.e., the second terminal device in the embodiments of this application) through a relay device; or they can be applied to a UE-to-network scenario, that is, a remote UE communicates with an access network device (such as a base station) through a relay device.

[0109] As one embodiment, the first communication link is a communication link between the relay device and the first terminal device, and the second communication link is a communication link between the relay device and the access network device or between the relay device and the second terminal device. The first terminal device communicates with the access network device or with the second terminal device through the relay device.

[0110] Optionally, in this embodiment of the application, the first communication link can be a PC5 link, and the second communication link can be a Uu interface link.

[0111] Optionally, the quality of service in the embodiments of this application may include various judgment methods, including QoS parameters, such as GFBR, latency, packet loss rate, etc.

[0112] In this application embodiment, different methods can be used to determine the quality of service of the first communication link:

[0113] For example, the first method involves directly detecting the service quality of the first communication link. Specifically, determining that the service quality of the first communication link does not meet the service quality requirements includes detecting that the service quality of the first communication link is lower than a first threshold, where the first threshold corresponds to the service quality requirements.

[0114] In this scenario, Layer 3 relay can be applied. The implementing entity can be the relay device. It should be understood that in Layer 3 relay, the communication link between the first terminal device and the relay device is unknown to the access network. The relay device can monitor the quality of the PC5 link during PC5 communication. Specifically, the relay UE receives data packets from a remote UE and determines whether the PC5 channel quality can guarantee the current PC5 QoS parameter requirements (e.g., GFBR, latency, packet loss rate) or support higher QoS parameter requirements (e.g., higher GFBR, lower latency, lower packet loss rate) by checking whether the received signal power strength drops to a certain threshold (the specific value of which can be pre-configured by the base station or set on the device during terminal manufacturing).

[0115] Alternatively, this scenario can also be applied to Layer 2 relay scenarios. In this case, the executing entity can be the first terminal device (or a remote UE). The first terminal device can monitor the PC5 link quality to determine whether the PC5 link quality can guarantee the current QoS parameters or whether the channel quality of the PC5 interface can support higher QoS parameter requirements. The specific monitoring process can refer to the method described above for relay UE monitoring the PC5 link.

[0116] The second method determines the service quality of the first link by receiving information sent by other devices. Specifically, determining that the service quality of the first communication link does not meet the service quality requirements includes receiving a second message from the first terminal device, the second message indicating a reduction in the service quality of the first communication link.

[0117] In this case, it can be applied to the Layer 3 relay scenario. The executing entity can be the relay UE. In the Layer 3 relay, the communication link between the first terminal device and the relay device is unknown to the access network. If the first terminal device in the Layer 3 relay obtains the service quality of the first communication link and determines that the service quality does not meet the service requirements, the first terminal device can determine that the service quality of the first communication link needs to be changed and send the requirement to the relay device through the first message.

[0118] The third method involves indirectly determining the service quality of the first communication link by receiving service quality information from other devices. Specifically, this involves receiving a third message from the first terminal device or the relay device, the third message indicating the service quality of the first communication link; and determining that the service quality of the first communication link is lower than a first threshold, the first threshold corresponding to the service quality requirement.

[0119] Optionally, the first threshold may correspond to the value of QoS parameters, such as the value of parameters like GFBR, latency, or packet loss rate. The first threshold may be pre-configured or obtained from the network side. This application embodiment does not limit this.

[0120] This approach can be applied to Layer 2 relay scenarios. The executing entity can be an access network device. Specifically, during communication, the base station can receive the channel quality of the PC5 link reported by the first terminal device and / or the relay device, and evaluate the received channel quality of the PC5 link. For example, the base station can determine whether the channel quality of the PC5 interface cannot guarantee the current QoS parameters, or the base station can also determine whether the channel quality of the PC5 interface can support higher QoS parameter requirements.

[0121] S420, send a first message, the first message being used to request a change in the parameters of the second communication link quality of service.

[0122] In this embodiment of the application, the first message mentioned above can be sent to the Session Management Element (SMF). Specifically, sending the first message includes sending the first message to the Session Management Element, and the first message is used to reduce the service quality of the second communication link.

[0123] At this point, it corresponds to the first situation mentioned above. When the executing entity is a relay device in a Layer 3 relay scenario, the relay device can send a first message to the session management network element. Optionally, the relay device can send a QoS change request message, i.e., the first message, to the session management network element through a PDU session change message.

[0124] It should be understood that before the relay device and the remote UE modify the QoS parameters of PC5 (i.e., the first communication link in this embodiment), the relay device needs to modify the QoS parameters of the Uu interface on the network side first. Because there is no control signaling interaction between the remote UE and the network side in the Layer 3 relay scenario, only the relay device can initiate the QoS parameter change request for the Uu interface. Before the relay device sends the QoS change request for the Uu interface to the SMF network element, it needs to confirm which service flows' QoS parameters are being changed. The relay device can map the PFI to the QFI and the PC5 QoS parameter requirements to the Uu QoS parameter requirements by obtaining the PC5 QoS change information corresponding to the SDF or PFI during PC5 link monitoring. Afterwards, the relay device sends a NAS message to the AMF network element through the base station. The message may include a PDU session identifier and an N1 session management container (N1 SM container). After receiving the NAS message, the AMF can use the Nsmf_PDUSession_UpdateSMContext service to forward the message to the SMF network element. Optionally, the first message sent by the relay UE may carry the service data flow (SDF) identifier or QFI identifier of the data flow that needs to be modified. Furthermore, the first message may also include the specific parameter information after the modification.

[0125] Alternatively, when the executing entity is the first terminal device in the Layer 2 relay, the first terminal device can send a first message to the session management network element. Optionally, the first terminal device can send a PDU session change message to the SMF via NAS. Specifically, the first terminal device can send a NAS message to the AMF. After receiving the NAS message, the AMF can use the Nsmf_PDUSession_UpdateSMContext service to forward the message to the SMF network element. Alternatively, the first terminal device can also forward the first message to the SMF network element via the UPF network element. The first message can carry the SDF identifier or QFI identifier of the data stream to be changed. Furthermore, the first message can also include the specific parameter information after the change.

[0126] Alternatively, this situation can also correspond to the third method mentioned above. In this case, the executing entity is the access network device in the Layer 2 relay scenario. After the access network device determines in S410 that the service quality in the first communication network does not meet the service requirements, it can initiate a QoS parameter change process and send a first message to the session management network element. Optionally, the first message can carry the QFI identifier of the data stream to be changed. Furthermore, the first message can also include the specific parameter information after the change.

[0127] As an example, when sending the first message, a reason value may also be carried in the first message. Specifically, the first message includes a reason value, and the reason value indicates that the service quality of the first communication link needs to be changed.

[0128] By including a cause value in the first message, the receiving end can initiate a corresponding process to change the quality of service of the second communication link.

[0129] Optionally, as another embodiment, when sending the first message, the first message may include first indication information. Specifically, the first message includes first indication information, which is used to indicate that the reason for the change of the second communication link is that the service quality of the first communication link needs to be changed.

[0130] By including a first indication in the first message, the receiving end can initiate a corresponding process to change the quality of service of the second communication link. The first indication can be explicit, such as a cause value or a specific information element, or it can be implicit, such as being reflected in the name of the first message, like a request message to change the Uu link corresponding to the PC5 link.

[0131] In this embodiment of the application, a first message may also be sent to the access network device. Specifically, sending the first message includes sending the first message to the access network device, wherein the first message is used to indicate a reduction in the quality of service of the second communication link.

[0132] In this scenario, the first scenario described above also applies. When the executing entity is a relay UE in a Layer 3 relay scenario, the relay device, upon learning that the service quality of the current first communication link does not meet the service requirements, can send a first message to the access network device. This first message can include the data radio bearer (DRB) information corresponding to the service flow whose QoS parameters need to be modified, i.e., the air interface resource information on the radio side. Furthermore, the first message can also include the modified specific parameter information.

[0133] Alternatively, when the executing entity is the first terminal device in the Layer 2 relay, during the monitoring of the PC5 link, if the first terminal device discovers that the service quality of the first communication link cannot meet the service requirements, it can send a first message to the access network device. The first message can carry the sidelink radio bearer (SLRB), DRB, PFI, or QFI identifier. Optionally, if the access network itself has already obtained the mapping relationship between PFI and QFI, the first terminal device can only provide the PFI, and the access network device can deduce the corresponding QFI. Furthermore, the first terminal device can also provide the radio resource information corresponding to the QoS parameters that need to be changed, i.e., the SLRB or DRB. Because if the access network device maintains the mapping relationship between the SLRB or DRB and the QoS flow, then the access network device can deduce the QoS flow information (QFI) that the first terminal device needs to change from this resource information.

[0134] As an example, the first message may further include at least one of the following: QFI identifier, SDF information, PFI identifier, DRB identifier, and SLRB identifier.

[0135] Optionally, in the embodiments of this application, the failure to meet the quality of service can be that the current channel quality cannot guarantee the link QoS parameter requirements, or it can be that the current channel quality can support higher QoS parameter requirements. The embodiments of this application do not limit this.

[0136] Specifically, determining that the service quality of the first communication link does not meet the service quality requirements includes: determining that the service quality of the first link is higher than a second threshold, the second threshold corresponding to the service quality requirements.

[0137] Correspondingly, the first message is used to request an improvement in the quality of service of the second communication link; specifically, the first message is used to instruct an improvement in the quality of service of the second communication link.

[0138] Optionally, determining the service quality of the first communication link in the embodiments of this application may include different situations. For example, the relay device in the current link may correspond to multiple first terminal devices, i.e., a one-to-many situation, or the relay device may correspond to one first terminal device, i.e., a one-to-one situation. In both situations, the first terminal device, the relay device, and the access network device can use the method in the embodiments of this application to determine the service quality of the first communication link and execute the process of changing the service quality of the second communication link.

[0139] This application embodiment modifies the service quality parameters of the second communication link according to the service quality of the first communication link, so that the service quality parameters of the second communication link correspond to the service quality of the first communication link, thereby controlling the service quality of the second communication link more flexibly and accurately.

[0140] Figure 5 This application illustrates a method for changing Quality of Service (QoS) according to an embodiment of the present application. The method 500 includes steps S510 to S520, which are described in detail below.

[0141] S510, the first terminal device determines that the service quality of the first communication link does not meet the service quality requirements or determines that the service quality of the first communication link has changed.

[0142] As one embodiment, the first communication link is a communication link between the relay device and the first terminal device.

[0143] Optionally, the first terminal device can be a remote UE.

[0144] S520 sends the first message to the relay device.

[0145] As an example, the first message is used to request a change in the parameters of the quality of service of the first communication link.

[0146] It should be understood that determining that the service quality of the first communication link does not meet the service quality requirements or determining that the service quality of the first communication link has changed in the embodiments of this application can correspond to two situations respectively. The first is that the service quality of the PC5 link does not meet the service quality requirements, that is, when the rate or latency does not reach the threshold, it is triggered; or, the second is that the QoS requirements of the PC5 link have changed, such as the bandwidth requirements of the remote UE becoming lower or the bandwidth resources being released due to the cessation of the use of a certain service. Both of the above situations can trigger the first terminal device to send a first message to the relay device, thereby changing the service quality of the first communication link, so that the link service quality meets the transmission requirements.

[0147] In this embodiment, when the service quality of the first communication link does not meet the requirements or the service quality requirements of the first terminal device change, the first terminal device sends a request message to the relay device to change the service quality of the first communication link, thereby enabling the link service quality to meet the transmission requirements and improving data transmission efficiency.

[0148] The following describes several QoS change processes in this application. It should be understood that in the embodiments of this application, the process of remote UE, relay UE, and network-side equipment judging the service quality of the first communication link (or PC5 link) to change the service quality of the PC5 link or Uu interface link can be triggered when the service quality of the PC5 link does not meet the service quality requirements, such as when the rate or latency does not reach the threshold. Alternatively, it can be triggered when the QoS requirements of the PC5 link change, such as when the bandwidth requirements of the relay and remote UE decrease, resulting in a decrease in the service quality of the PC5 link. Or, it can be triggered when the service quality requirements of the remote UE itself change, such as when the bandwidth requirements of the remote UE decrease or when the bandwidth resources are released due to the cessation of the use of a certain service. This application does not specifically limit the method of triggering the change request in the PC5 link.

[0149] Figure 6 This diagram illustrates the process of a relay UE initiating a QoS change request in a Layer 3 relay within a UE-to-Network scenario.

[0150] like Figure 6 As shown in S610, the remote UE establishes a data communication connection with the cellular network through the relay UE, and performs quality monitoring on the PC5 link between the remote UE and the relay UE during data transmission. Specifically, the relay UE can receive data packets from the remote UE, or when the remote UE receives network-side data packets forwarded by the relay UE, it can determine whether the PC5 channel quality can guarantee the current PC5 QoS parameter requirements (e.g., GFBR, latency, packet loss rate, etc.) or support higher QoS parameter requirements by measuring the received signal power strength or by monitoring whether the received data packets' GFBR, latency, packet loss rate, etc., have decreased to a first threshold (optionally, the specific value of the first threshold can be pre-configured by the base station, or configured to the UE by the network-side network element, such as the SMF through the N1 message, or sent to the UE by the PCF network element along with the user policy configuration information, or set by the equipment manufacturer when manufacturing the terminal equipment).

[0151] Optionally, in step S620, the remote UE sends a QoS change request message for the PC5 link to the relay UE. Specifically, when the remote UE discovers in step S660 that the PC5 link quality cannot guarantee the current QoS parameter requirements or can support higher QoS requirements (e.g., higher transmission rates), the remote UE can notify the relay UE to initiate a QoS change procedure for the PC5 link via a PC5 signaling message. In the PC5 link QoS change request message, the remote UE needs to indicate the service flow information (e.g., SDF, which can be represented by Packet Filter) or PFI information for which the QoS of the PC5 link needs to be changed, as well as the changed QoS parameter values.

[0152] In addition to changing QoS parameters, remote UEs can also add or remove (or delete) a service flow. For example, this is triggered when a remote UE stops using the application corresponding to that service flow.

[0153] Specifically, the remote UE can send a fourth message to the relay UE, which is used to indicate the addition or removal of the first service flow. The fourth message may include at least one of the following: Service Data Flow SDF information, PC5 link QoS Flow Identifier (PFI).

[0154] Optionally, the fourth message can be a PC5 link change request message. In this case, the remote UE can send a PC5 link change request message to the relay UE. This change request message can include flow description information (e.g., SDF, which can be represented by a Packet Filter) of the service flow to be added or removed, and an indication of addition or removal (e.g., the Operation carried in the message is set to add or delete). Optionally, if the remote UE accesses an N3IWF (Non-3GPP Interworking Function) through the relay UE, the flow description information of the service flow can be a combination of the N3IWF address and the SPI (Security Parameters Index). The change request message can also include the PC5 QoS flow identifier (i.e., PFI) corresponding to the service flow to be added or removed.

[0155] Steps S660 and S620 are existing technologies, and will not be described in detail in this application's embodiments.

[0156] S630, the relay UE sends a QoS parameter change request message to the SMF. Specifically, if the relay UE detects in step S660 that the link quality of the PC5 link does not meet the current QoS parameter requirements or can support higher QoS requirements, or if the relay UE receives a QoS change request for the PC5 link from a remote UE in step S620, the relay UE initiates a QoS change procedure for the Uu link to the SMF.

[0157] Alternatively, in response to a remote UE requesting the addition or removal of a first service flow, the relay UE sends a first message to the SMF, which indicates the addition or removal of the first service flow.

[0158] After the receiving end receives the first message, it can add or remove relevant service flows, and add or delete QoS-related parameters corresponding to the service flow. That is, the first message can be used to indicate the parameters for changing the quality of service of the second communication link.

[0159] Optionally, the first message may also include the first indication information mentioned above, which indicates that the reason for the change of the second communication link is the addition or removal of service flows in the first communication link.

[0160] Before a relay UE sends a QoS change request for the Uu interface to an SMF network element, it needs to confirm which service flows require QoS parameter changes. Specifically, the relay UE maps the PFI identifier to the QFI identifier and the PC5 QoS parameter requirements to the Uu QoS parameter requirements based on the PC5 QoS changes corresponding to the SDF or PFI identifiers obtained in step S610 or S620. It should be understood that in a Layer 3 relay scenario, the relay UE maintains the correspondence between the PFI and QFI identifiers, as well as the mapping relationship between their corresponding PC5 QoS parameters and Uu QoS parameters. Therefore, after obtaining the PFI or SDF identifiers that require QoS changes, the relay UE can perform the mapping.

[0161] Subsequently, the relay UE sends a QoS change request for the Uu interface to the SMF network element. Optionally, this request message can be carried in a NAS message sent by the relay UE to the AMF network element through the base station. This NAS message may include a PDU session identifier and an N1 session management container (N1 SM container). The N1 session management container includes a QoS parameter change request indication, Operation (add, modify, or delete), PDU session ID, service flow information (e.g., SDF or QFI), requested QoS parameter information, and a change reason (Cause). The Cause indicates that the QoS of the PC5 link between the relay UE and the remote UE needs to be changed, or that a service flow has been added or removed. After receiving the NAS message, the AMF can use the Nsmf_PDUSession_UpdateSMContext service to forward the message to the SMF network element. Alternatively, the relay UE can forward the QoS change request message of the Uu interface to the SMF network element through the UPF network element. The request message carries: QoS parameter change indication, PDU session ID, service flow information (such as SDF or QFI), requested QoS parameter information and change reason (Cause), etc.

[0162] It should be understood that the specific process by which the relay UE sends the change request message to the SMF through the AMF or UPF is prior art. The improvement in this application is that the change request message is initiated because the link quality of the PC5 link does not meet the QoS requirements, rather than a specific signaling transmission process. Therefore, the specific data transmission process involved in the embodiments of this application will not be described in detail.

[0163] It should be understood that before the relay UE and the remote UE can change the PC5 QoS parameters, the relay UE needs to first change the QoS parameters of the Uu interface with the network side. Because in a Layer 3 relay scenario, there is no control signaling interaction between the remote UE and the network side, only the relay UE can initiate the QoS parameter change request for the Uu interface.

[0164] S640, the SMF changes the QoS parameters of the Uu interface. Specifically, after receiving the change request message, the SMF determines whether to change the QoS parameters.

[0165] Specifically, the SMF can determine whether the UE's change request conforms to the subscription information based on the UE's subscribed session data (e.g., whether the maximum bandwidth requested by the UE exceeds the subscription limit). Alternatively, the SMF can determine whether the QoS parameters requested by the UE conform to the QoS parameter values ​​specified in the PCC rules (i.e., the services corresponding to QFI or SDF) as defined in the local PCC rules or the PCC rules obtained from the PCF. Here, the UE can be a relay UE or a remote UE. If it is a remote UE, the relay may need to send the remote UE's identification information along with the QoS change request message to the SMF, if the PDU session is multiplexed by multiple remote UEs.

[0166] If a service flow requested to be removed by a relay UE is carried solely by a GBR QoS flow, the SMF can notify the RAN to update the QoS configuration (removing the QoS flow) via an N2 message. If this service flow shares a GBR QoS flow with other service flows, the SMF needs to change the QoS parameters of the GBR QoS flow (e.g., subtract the GFBR occupied by the service flow from the GFBR of the GBR QoS flow). For example, if the GBR QoS flow was originally used to carry two service flows (service 1 and service 2, which can be used by remote UEs simultaneously, or service 1 by remote UE1 and service flow 2 by remote UE2. Service 1 and service 2 occupy 10Mbps and 5Mbps GFBRs respectively, meaning the GFBR of the GBR QoS flow is 15Mbps), when the relay UE requests the SMF to remove service 1, the SMF needs to set the GFBR of the GBR QoS flow to 5Mbps.

[0167] If the QoS parameter change requested by the UE meets the QoS parameter value restricted in the UE's subscribed session data, or the QoS parameter value that the service can perform as defined in the PPC rule, then the SMF can change the QoS parameter for the UE.

[0168] If the SMF accepts the QoS parameter change request, it modifies the QoS parameters of the service flow corresponding to the SDF identifier or QFI identifier indicated in the request message in step S630. After the change, the SMF network element synchronously updates the UPF configuration information involved in the changed QFI.

[0169] In S650, the SMF sends the modified PDU session information to the AMF. Specifically, the SMF can send the N1 SM container and the N2 SM container to the AMF via the Nsmf_PDUSession_UpdateSMContext service message.

[0170] In S660, the AMF sends the information in the N2 SM container to the base station. The N2 SM information includes: PDU session identifier and the QoS parameters corresponding to the changed QFI.

[0171] S670, the AMF sends the information in the N1 SM container to the relay UE. The N1 SM information includes: PDU session identifier and QoS parameters corresponding to the changed QoS rules.

[0172] In step S680, after receiving the N2 SM message in step S660, the base station updates the QoS parameter mapping corresponding to DRB and QFI, and sends the modified DRB configuration information (i.e., air interface resource information) to the relay UE via RRC message.

[0173] S690, the relay UE initiates a PC5 QoS change procedure with the remote UE based on the updated Uu QoS information obtained in steps S670 and S680.

[0174] It should be understood that steps S640 to S690 are prior art, and will not be described in detail here.

[0175] This application embodiment relates to QoS parameter changes in Layer 3 relays in UE-to-network scenarios. The relay UE obtains the link quality of the PC5 link, and when the PC5 link quality does not meet the QoS requirements, it initiates a QoS change request for the Uu interface. This allows the network side to synchronously change the QoS parameters of the Uu interface and the PC5 interface when the link quality of the PC5 link does not meet the requirements, thereby ensuring end-to-end QoS requirements.

[0176] Figure 7 This illustration shows another flowchart of a Layer 3 relay in a UE-to-Network scenario according to an embodiment of this application, illustrating a QoS change request initiated by a relay UE. Figure 7 As shown, with Figure 6 The difference between this application and the previous one is that in this application embodiment, the relay UE sends a QoS request message to the base station to change the Uu interface, and then the base station sends a QoS parameter change request for the Uu interface to the SMF. Figure 7 As shown:

[0177] S710 and S770 and Figure 6 S610 and S620 are the same, and will not be described in detail in the embodiments of this application.

[0178] S730, the relay UE sends a first message to the base station to request a change in the QoS parameters of the Uu interface. Specifically, the relay UE can report a first message to the base station via an RRC message, including a request to change the QoS parameters of the Uu interface due to changes in PC5 link quality. The first message can include the data radio bearer (DRB) information corresponding to the service flow or QFI whose QoS parameters need to be changed, i.e., the air interface resource information on the radio side. The first message can also include QoS parameter information, which may include the target QoS parameter to be changed and its target requirements (e.g., target bandwidth), or may include an indication that the communication quality of the current service flow or QoS flow cannot meet the QoS parameter requirements (e.g., GBR cannot be met).

[0179] It should be understood that in the Layer 3 relay scenario, the relay UE maintains the mapping relationship between the PFI identifier and the QFI identifier and their corresponding DRB. Therefore, the relay UE can map the PFI identifier or SDF identifier that needs to be changed for QoS parameters obtained from step S710 or S770 to the corresponding DRB.

[0180] In step S740, the base station sends a second message to the SMF to request a change to the QoS parameters of the Uu interface, indicating that the QoS parameters corresponding to the QFI identifier need to be changed. Specifically, the RAN-side base station can send a second message to the SMF through the AMF, indicating that the QoS parameters corresponding to the QFI identifier need to be changed. The QFI identifier is the QFI identifier corresponding to the DRB information confirmed by the base station after receiving the first message from the relay UE in step S730, based on the DRB information indicated in the first message (it should be understood that the base station is responsible for handling the mapping relationship between QFI and radio interface resources, so the base station can confirm the QFI from the DRB information based on this mapping relationship). The second message sent by the base station to the SMF may carry: PDU session identifier, QFI identifier, QoS parameter information, and request reason (Cause). The QoS parameter information may include the target QoS parameter to be changed and its target requirements (e.g., target bandwidth), or may include an indication that the communication quality of the current service flow or QoS flow cannot meet the QoS parameter requirements (e.g., GFBR cannot meet them). The request reason may be that the QoS parameters corresponding to the QFI identifier in the PC5 link need to be changed. Alternatively, the request message can be sent in the form of an N2 message.

[0181] Steps S750 to S7100 and Figure 6 The S640 to S690 are similar, so we will not go into details here.

[0182] This application embodiment relates to QoS parameter changes in Layer 3 relays in UE-to-network scenarios. The relay UE obtains the link quality of the PC5 link, and when the PC5 link quality does not meet the QoS requirements, it initiates a QoS parameter change request for the Uu interface to the base station. This allows the base station to further send the obtained change request to the SMF, enabling the network side to synchronously change the QoS parameters of the Uu interface and the PC5 interface when the link quality of the PC5 link does not meet the requirements, thereby ensuring end-to-end QoS requirements.

[0183] Figure 8 This illustration shows a flowchart of a Layer 3 relay in a UE-to-UE scenario, according to an embodiment of this application, where a QoS change request is initiated by the relay. Figure 8 As shown:

[0184] In S810, the remote UE and the target UE establish a connection through the relay UE. During data transmission, the remote UE and the relay UE perform quality monitoring on the first PC5 link between them. Specifically, the relay UE can receive data packets from the remote UE, or when the remote UE receives network-side data packets forwarded by the relay UE, it can determine whether the PC5 channel quality can guarantee the current PC5 QoS parameter requirements (e.g., GFBR, latency, packet loss rate) or support higher QoS parameter requirements by measuring the received signal power strength or by monitoring whether the received data packets' GFBR, latency, packet loss rate, etc., have decreased to a first threshold (optionally, the specific value of this first threshold can be pre-configured by the base station, or configured to the UE by the network-side network element, such as the SMF via N1 message, or sent to the UE by the PCF network element along with user policy configuration information, or set by the equipment manufacturer when manufacturing the terminal equipment).

[0185] Similarly, a service flow can be added or removed between a remote UE and a target UE, and the relay UE also needs to synchronize the addition and removal operations between the two UEs.

[0186] In the embodiments of this application, the first PC5 link is the PC5 link between the relay device and the remote UE, and the second PC5 link is the PC5 link between the relay device and the target UE. Alternatively, other names may be used to represent the two different links, and this application does not limit this.

[0187] Optionally, in step S820, the remote UE sends a QoS change request message for the first PC5 link to the relay UE. Specifically, when the remote UE discovers in step S810 that the quality of the first PC5 link cannot guarantee the current QoS parameter requirements or can support higher QoS requirements (e.g., higher transmission rates), the remote UE can notify the relay UE to initiate a QoS change procedure for the first PC5 link via a PC5 signaling message. In the QoS change request message for the first PC5 link, the remote UE needs to indicate the service flow information (e.g., SDF, which can be represented by Packet Filter) or PFI information for which the QoS of the first PC5 link needs to be changed, as well as the changed QoS parameter values.

[0188] If a remote UE sends a change request message for the first PC5 link to a relay UE, the change request message may include service flow information to be added or removed (such as SDF, which may be represented by Packet Filter), and the QoS parameter value corresponding to the new service flow.

[0189] Steps S810 and S820 are existing technologies, and will not be described in detail in this application's embodiments.

[0190] S830, the relay UE sends a second PC5 link QoS change request message to the target UE. Specifically, if the relay UE detects in step S810 that the link quality of the first PC5 link does not meet the current QoS parameter requirements or can support higher QoS requirements, or if the relay UE receives a QoS change request for the first PC5 link from the remote UE in step S820, the relay UE initiates a second PC5 link QoS change procedure to the target UE.

[0191] Before the relay UE sends a QoS change request for the second PC5 link to the target UE, it needs to confirm which service flows' corresponding QoS parameters need to be changed. Specifically, the relay UE maps the first PFI identifier to the second PFI identifier and the first PC5 QoS parameter requirements to the second PC5 QoS parameter requirements based on the changes to the first PC5 QoS corresponding to the SDF or first PFI identifier obtained in step S810 or S820. It should be understood that in the Layer 3 relay scenario, the relay UE maintains the correspondence between the first PFI identifier and the second PFI identifier, as well as the mapping relationship between their corresponding first PC5 QoS parameters and second PC5 QoS parameters. Therefore, after obtaining the PFI identifier or SDF identifier that needs to be changed for QoS, the relay UE can perform the corresponding mapping.

[0192] When a remote UE indicates the addition of a new service flow, the relay UE needs to confirm whether the service flow can reuse an existing PC5 QoS flow. If it cannot be reused, the relay UE needs to add a new PC5 QoS flow (e.g., a third PC5 QoS flow) to carry the new service flow, and map the QoS value corresponding to the new service flow provided by the remote UE to the parameters of the PC5 QoS flow (e.g., mapping QoS requirements such as latency and packet loss rate to PQI, and mapping minimum bandwidth requirements to the corresponding GFBR). Afterwards, the relay UE needs to synchronously send the updated (new) service flow information and QoS parameters to the target UE, and either the relay UE or the target UE adds a new PC5 QoS flow (e.g., a fourth PC5 QoS flow) to carry the service flow.

[0193] When a remote UE indicates the removal of a service flow, the relay UE notifies the target UE of the removal message. If the service flow is carried by only one PC5 QoS flow, the relay UE can initiate the cancellation of this PC5 QoS flow. If the service flow is multiplexed with other service flows or other remote UEs, and the PC5 QoS flow is a GBR QoS flow, the relay UE needs to subtract the corresponding GFBR from the GFBR of the PC5 QoS flow. For example, two remote UEs (UE1 and UE2) communicate with a target UE through the same relay UE. Each remote UE and relay UE establishes a GBR QoS flow. The GFBR of the GBR QoS flow (PFI 1) between UE1 and the relay UE is 10 Mbps, and the GFBR of the GBR QoS flow (PFI 2) between UE2 and the relay UE is 5 Mbps. These two QoS flows can reuse a GBR QoS flow (PFI 3) between the relay UE and the target UE, which has a GFBR of 15 Mbps (the sum of the bandwidth of the two PC5 QoS flows). When the service flow carried by the GBR QoS flow (PFI 1) between UE1 and the relay UE is cancelled, the relay UE needs to synchronously update the GFBR of the GBR QoS flow (PFI 3) between the relay UE and the target UE to 5 Mbps. Another scenario is that UE1 has two different service flows carried on the same GBR QoS flow (PFI 4). Service 1 has a GFBR of 10 Mbps, and Service 2 has a GFBR of 5 Mbps. Service 1 and Service 2 communicate simultaneously through a GBR QoS flow (PFI 5) between the relay UE and the target UE. When the remote UE cancels Service 1, UE1 updates the GFBR of PFI 4 to 5 Mbps with the relay UE, and the relay UE updates the GFBR of PFI 5 to 5 Mbps with the target UE.

[0194] In the embodiments of this application, the first PFI identifier can be the identifier of the data flow in the first PC5 link, and the second PFI identifier can be the identifier of the data flow in the second PC5 link. Alternatively, other names can be used to represent the identifier of the data flow in the two links. The embodiments of this application do not limit this.

[0195] Subsequently, the relay UE sends a QoS change request for the second PC5 link to the target UE. This request message may include a QoS parameter change request indication, a PDU session ID, service flow information (e.g., SDF information or a second PFI identifier), the requested QoS parameter information, and a reason for the change. The QoS parameter information may include the target QoS parameter to be changed and its target requirements (e.g., target bandwidth), or it may include an indication that the current quality of the first PC5 link cannot meet the QoS parameter requirements (e.g., GBR cannot be satisfied). The reason for the request may be that the QoS parameter corresponding to the second PFI identifier in the first PC5 link needs to be changed.

[0196] It should be understood that the specific process by which the relay UE F sends the change request message to the target UE is prior art. The improvement in this application is that the change request message is initiated because the link quality of the first PC5 link does not meet the QoS requirements, rather than a specific signaling transmission process. Therefore, the specific data transmission process involved in the embodiments of this application will not be described in detail.

[0197] It should be understood that before the relay UE and the remote UE change the first PC5 QoS parameters, the relay UE needs to change the QoS parameters of the second PC5 link to the target UE. Because there is no control signaling interaction between the remote UE and the target UE in a Layer 3 relay scenario, only the relay UE can initiate the QoS parameter change request for the second PC5 link.

[0198] S840, the target UE sends the first message to the relay UE.

[0199] As one possible implementation, the first message could be a change request confirmation message, in which the target UE receives the change request from the relay UE and completes the change of the QoS parameters of the PC5 link between the target UE and the relay UE.

[0200] Alternatively, as another possible implementation, the first message could be a change request rejection message, in which case the target UE rejects the relay UE's change request.

[0201] S850, the relay UE sends a second message to the remote UE.

[0202] As one possible implementation, when the first message is a change request confirmation message, the second message can also be a change request confirmation message. In this case, the QoS parameters of the second PC5 link have been changed between the relay UE and the remote UE.

[0203] Alternatively, as another possible implementation, when the first message is a change request rejection message, the second message can also be a change request rejection message. In this case, the relay UE and the remote UE do not perform QoS changes on the first PC5 link. Optionally, the remote UE can choose to disconnect from the relay UE or choose another relay UE to connect to.

[0204] This application embodiment relates to QoS parameter changes in Layer 3 relays in UE-to-UE scenarios. The relay UE obtains the link quality of the first PC5 link, and when the link quality of the first PC5 link does not meet the QoS requirements, it initiates a QoS change request for the second PC5 link. This allows the target UE to synchronously change the QoS parameters of the second PC5 link and the first PC5 link when the link quality of the first PC5 link does not meet the requirements, thereby ensuring end-to-end QoS requirements.

[0205] Figure 9 This illustration shows a flowchart of a QoS change request initiated by a base station in a Layer 2 relay according to an embodiment of this application. Figure 9 As shown:

[0206] In S910, the remote UE establishes a data communication connection with the cellular network through the relay UE, and performs quality monitoring on the PC5 link between the remote UE and the relay UE during data transmission. Specifically, the relay UE can receive data packets from the remote UE, or when the remote UE receives network-side data packets forwarded by the relay UE, it can determine whether the PC5 channel quality can guarantee the current PC5 QoS parameter requirements (such as GFBR, latency, packet loss rate, etc.) or support higher QoS parameter requirements by measuring the received signal power strength or by monitoring whether the GFBR, latency, packet loss rate, etc. of the received data packets have decreased to a first threshold (optionally, the specific value of the first threshold can be pre-configured by the base station or set by the equipment manufacturer when manufacturing the terminal equipment).

[0207] S920, Optionally, the relay UE sends a first message to the base station. The first message may include the channel quality monitoring results of the PC5 link.

[0208] In existing technologies, relay UEs can report the channel quality of the Uu interface to the base station. Specifically, the base station can assess the channel quality of the Uu interface through the received power of data packets uploaded by the relay UE or reference information received on the measurement channel.

[0209] When the base station allocates a DRB and a sidelink radio bearer (SLRB) to the relay UE, the relay UE in this embodiment can simultaneously report channel quality information of the Uu interface and the PC5 interface to the base station.

[0210] S930, Optionally, the remote UE sends a second message to the base station. The second message may include the channel quality monitoring results of the PC5 link. Additionally, the second message may also include the identification information of the relay UE.

[0211] It should be understood that the PC5 link quality results in the embodiments of this application may be sent to the base station only by the relay UE, or only by the remote UE, or optionally, both the relay UE and the remote UE may send the PC5 link quality results to the base station. The embodiments of this application do not limit this.

[0212] In step S940, the base station determines whether a QoS parameter change request for the Uu interface needs to be initiated. Specifically, the base station assesses whether the current QoS parameters need to be changed based on the channel quality of the PC5 interface and / or Uu interface obtained from step S920 or S930. Specifically, when the base station receives the channel quality monitoring result of the relay UE's PC5 link from step S920, it determines whether the PC5 link currently used by the relay UE can support data transmission of the Uu link based on the information in the result (e.g., the signal strength of the remote UE data packets received by the relay UE on the PC5 interface, or the bandwidth, latency, or packet loss rate that the current PC5 interface can support, statistically obtained during the transmission of remote UE data packets). That is, it assesses whether the current QoS parameters of the Uu interface need to be changed. For example, if the bandwidth currently supported by the PC5 link is less than the bandwidth resources configured for the Uu interface, the base station needs to reduce the bandwidth of the Uu interface to match the bandwidth of the PC5 interface. Here, the PC5 link information reported by the relay UE can be an SLRB identifier; in this case, the base station needs to change the QoS parameters of the DRB corresponding to the SLRB. When the DRB carries a QFI, the base station performs QoS modification processing on that QFI. When the DRB carries multiple QFIs, the base station needs to process all of these QFIs simultaneously.

[0213] If the base station receives a second message from the remote UE in step S990, the PC5 link information in the second message can be an SLRB identifier, a DRB identifier, or a QFI. If the base station receives an SLRB or DRB identifier, it needs to confirm the QFI requiring QoS change processing through the mapping relationship. If it receives a QFI identifier, the base station can directly perform QoS parameter change processing evaluation on that QFI. The specific evaluation process is described above.

[0214] When the channel quality of either the PC5 interface or the Uu interface is insufficient to guarantee the current QoS parameters, or when the channel quality of either the PC5 interface or the Uu interface can support higher QoS parameter requirements, the base station initiates a QoS parameter change procedure. Specifically, taking the PC5 link as an example, the channel quality of the PC5 interface obtained by the base station can be monitored at the SLRB granularity or at the physical channel granularity. Based on the obtained PC5 link quality results, the base station determines whether the link quality results meet a first threshold (optionally, this threshold can be configured locally by the base station or obtained from the network side). For example, if the base station determines that the monitoring result corresponding to SLRB1 in the current PC5 link quality results does not meet the first threshold (it could be GBR, latency, or packet loss rate, etc.), then it can be determined that a QoS parameter change request needs to be sent.

[0215] S950, the base station determines that it is initiating a QoS parameter change request for the Uu interface and sends a third message. Optionally, this third message may be sent in the form of a PDU session change request message.

[0216] The third message is used to request changes to the QoS parameters of the Uu interface. This third message may include the QFI identifier for which the QoS parameters need to be changed, the QoS parameter information, and the reason for the request. Specifically, for example, when the base station determines in the S950 that the QoS parameters corresponding to SLRB1 need to be changed, it can map SLRB1 to the corresponding QFI according to the locally maintained SLRB and QFI mapping relationship, thereby obtaining the QFI identifier for which the QoS parameters need to be changed. The QoS parameter information may include the target QoS parameter to be changed and its target requirements (e.g., target bandwidth), or it may include an indication that the current PC5 link quality cannot meet the QoS parameter requirements (e.g., GBR cannot be met). The reason for the request may be that the QoS parameters corresponding to the QFI identifier in the PC5 link need to be changed.

[0217] S960, the SMF changes the QoS parameters of the Uu interface. Specifically, after receiving the change request message, the SMF determines whether to change the QoS parameters. If the QoS parameter change request is accepted, the QoS parameters of the QoS flow corresponding to the QFI identifier indicated in the request message in step S950 are changed. After the change, the SMF network element synchronously updates the UPF configuration information involved in the changed QFI.

[0218] In S970, the SMF sends the modified PDU session information to the AMF. Specifically, the SMF can send the N1 SM container and the N2 SM container to the AMF via the Nsmf_PDUSession_UpdateSMContext service message.

[0219] In S980, the AMF sends the information in the N2 SM container to the base station. The N2 SM information includes: PDU session identifier and the QoS parameters corresponding to the changed QFI.

[0220] S990, the AMF sends the information in the N1 SM container to the remote UE. The N1 SM information may include: PDU session identifier, and QoS parameters corresponding to the changed QoS rules.

[0221] In step S9100, after receiving the N2 SM message from step S980, the base station updates the QoS parameter mapping corresponding to DRB and QFI, and sends the modified DRB configuration information (i.e., air interface resource information) to the relay UE via an RRC message. If the base station performs SLRB configuration, it simultaneously sends the DRB and SLRB configuration information to both the remote UE and the relay UE, or sends it only to the relay UE, which then forwards the SLRB configuration information to the remote UE.

[0222] Optionally, the base station may instruct the relay UE to initiate a PC5 QoS parameter update in the RRC message, and the specific update steps are subject to existing technology.

[0223] S9110, the remote UE initiates a PC5 QoS change procedure with the relay UE based on the updated Uu QoS information obtained in step S990, or the relay UE initiates a PC5 QoS change procedure with the remote UE based on the PC5 QoS parameter update indication obtained in step S9100. The specific update steps are described in the prior art, and will not be elaborated on in detail here.

[0224] This application embodiment relates to QoS parameter changes in Layer 2 relays in UE-to-network scenarios. The link quality of the PC5 link is obtained by the base station, and when the PC5 link quality does not meet the QoS requirements, a QoS change request for the Uu interface is initiated to the SMF. This allows the network side to synchronously change the QoS parameters of the Uu interface and the PC5 interface when the link quality of the PC5 link does not meet the requirements, thereby ensuring end-to-end QoS requirements.

[0225] Figure 10 This illustration shows a flowchart of a QoS change request initiated by a remote UE in a Layer 2 relay according to an embodiment of this application. Figure 10 As shown:

[0226] S1001 and Figure 9 The steps for S910 are the same, so I won't go into detail here.

[0227] S1002, the remote UE sends a first message to the base station. This first message can be used to request changes to the QoS parameters of the Uu interface and / or PC5 interface.

[0228] Specifically, when the remote UE monitors the PC5 link quality in step S1001 and finds that the PC5 link quality cannot guarantee the current QoS parameters or that the channel quality of the PC5 interface can support higher QoS parameter requirements, the remote UE can send a QoS parameter change request to the base station through RRC signaling.

[0229] As one possible implementation, when the remote UE and the relay UE negotiate to maintain the resources of the PC5 link, the first message can be used only to request changes to the QoS parameters of the Uu interface. Since the remote UE maintains the resources of the PC5 link, after the QoS parameters of the Uu interface are changed and the network side reconfigures the changed QoS parameter information to the remote UE, the remote UE can initiate the QoS parameter change process of the PC5 link based on the resources it maintains.

[0230] Alternatively, when the PC5 link resources are maintained by the base station, the first message sent by the remote UE should simultaneously request changes to the QoS of both the Uu interface and the PC5 interface.

[0231] In the first message, the remote UE needs to inform the base station which data streams' corresponding QoS parameters need to be changed. This means the base station needs to obtain two types of information: QoS stream information (such as QFI) and target QoS parameter information. If the base station has already obtained the mapping relationship between PFI and QFI, the remote UE can provide only the PFI, and the base station can deduce the corresponding QFI. Alternatively, the remote UE can also provide the radio resource information corresponding to the QoS parameters that need to be changed, i.e., SLRB or DRB. Since the base station maintains the mapping relationship between SLRB or DRB and QoS streams, it can deduce the QoS stream information (QFI) that the remote UE needs to change from this resource information. Alternatively, the remote UE can directly provide the QFI identifier that needs to be changed for the QoS parameters. Specifically, for example, after monitoring the quality of the PC5 link according to existing technology steps, the remote UE finds that the QoS parameters of the QoS stream corresponding to PFI1 do not meet the current transmission requirements. Since the remote UE can perceive the QFI granularity in a Layer 2 relay scenario, it can map the identifier of PFI1 to the identifier of the QFI and send this identifier to the base station. The remote UE in this application embodiment may also use other forms to send the identifier of the QoS flow that needs to be changed to the base station, and this application embodiment does not limit this.

[0232] S1003, the base station sends a second message to the SMF.

[0233] The RAN-side base station can send a second message to the SMF via the AMF, indicating that the QoS parameters corresponding to the QFI need to be changed.

[0234] The second message may include the QFI identifier of the QoS flow that needs to be changed (the QFI identifier can be obtained according to the method in step S420), QoS parameter information, and cause. The QoS parameter information may include the QoS parameters that need to be changed and their target requirements (e.g., target bandwidth), or it may include an indication that the communication quality of the current data flow cannot meet the QoS parameter requirements (e.g., GBR cannot be met). The reason for the request may be that the QoS parameters of the QoS flow corresponding to the QFI identifier in the PC5 link need to be changed.

[0235] As one possible implementation, the second message could be sent in the form of an N2 message.

[0236] Optionally, when the base station receives a QoS change request from a remote UE, the base station needs to assess whether to accept the request. One possible assessment scenario is that if the remote UE requests increased communication bandwidth, the base station needs to determine, based on air interface resource availability, whether the remote UE is initiating a QoS parameter change request to the network side. Specifically, this could involve whether the base station has sufficient resources to provide to the remote UE, or whether the UE's maximum bandwidth limit (UE-AMBR) on the base station side allows the remote UE to increase bandwidth, etc.

[0237] S1004 to S1009 and Figure 9 S960 to S9110 are the same, and will not be described in detail here.

[0238] This application embodiment relates to QoS parameter changes in Layer 2 relays in UE-to-network scenarios. By remotely obtaining the link quality of the PC5 link, and when the PC5 link quality does not meet QoS requirements, a QoS change request for the Uu interface is initiated to the base station. This allows the base station to further send the obtained change request to the SMF, enabling the network side to synchronously change the QoS parameters of the Uu interface and the PC5 interface when the PC5 link quality does not meet requirements, thereby ensuring end-to-end QoS requirements.

[0239] Figure 11 This illustration shows another flowchart of a QoS change request initiated by a remote UE in a Layer 2 relay according to an embodiment of this application. The embodiments of this application are similar to... Figure 10 Similar to the embodiments in the previous one, the difference is that in this embodiment, after obtaining the link quality of the PC5 link, the remote UE will directly send a QoS parameter change request for the Uu interface to the SMF. For example... Figure 11 As shown:

[0240] S1101 is the same as S1001, and will not be described in detail in the embodiments of this application.

[0241] S1102, the remote UE sends a first message to the SMF. Optionally, this first message may be sent in the form of a PDU session change message.

[0242] The first message may include the identifier of the QoS flow that needs to be changed (e.g., an SDF identifier or a QFI identifier), QoS parameter information, and the reason for requesting the change. The QoS parameter information may include the target QoS parameter that needs to be changed and its target requirements (e.g., target bandwidth), or it may include an indication that the current data flow's communication quality cannot meet the QoS parameter requirements (e.g., GBR cannot be met). The reason for the request may be that the QoS parameters of the QoS flow corresponding to the QFI identifier in the PC5 link need to be changed.

[0243] Specifically, a remote UE can send a PDU session change message to the SMF via NAS. The remote UE sends a NAS message to the AMF, including an N1 session management container and a PDU session ID. The N1 session management container may include a QoS parameter change request indication, the PDU session ID, service flow information (e.g., SDF or QFI), QoS parameter information, and a change reason. After receiving the NAS message, the AMF can use the Nsmf_PDUSession_UpdateSMContext service to forward the message to the SMF network element.

[0244] As another possible implementation, the remote UE can also forward the first message to the SMF network element through the UPF network element.

[0245] The remaining steps and Figure 10 The steps in the corresponding embodiments of the application are the same, and will not be repeated in this embodiment.

[0246] This application embodiment relates to QoS parameter changes in Layer 2 relays in UE-to-network scenarios. It obtains the link quality of the PC5 link through a remote UE, and when the PC5 link quality does not meet the QoS requirements, it directly initiates a QoS change request for the Uu interface to the SMF. This allows the network side to synchronously change the QoS parameters of the Uu interface and the PC5 interface when the link quality of the PC5 link does not meet the requirements, thereby ensuring end-to-end QoS requirements.

[0247] Figure 12A schematic diagram of a quality of service (QoS) control device according to an embodiment of this application is shown. As shown, the device 1200 includes a processing module 1201 and a sending module 1202. The device 1200 can be used to implement the QoS control function involved in any of the above method embodiments. For example, the device 1200 can be a terminal device or an access network device.

[0248] The device 1200 can process messages as a terminal device (such as a remote UE or relay device) or an access network device, and execute the steps in the above method embodiments where the terminal device (such as a remote UE or relay device) or access network device processes the quality of service of the first communication link. The processing module 1201 can be used to support the device 1200 in performing the processing actions in the above method, for example, executing... Figure 4 Or, in option 5, processing actions performed by a terminal device (such as a remote UE or relay device) or an access network device; the sending module 1202 can be used to support the device 1200 in communication, for example, performing... Figure 4 or Figure 5 The receiving action is performed by the terminal device (such as a remote UE or relay device) or access network device. Specifically, please refer to the following description:

[0249] Processing module 1201 is used to determine that the service quality of the first communication link does not meet the service quality requirements or that the service quality of the first communication link has changed. The first communication link is a communication link between a relay device and a first terminal device, and the second communication link is a communication link between the relay device and an access network device or between the relay device and a second terminal device. The first terminal device communicates with the access network device or with the second terminal device through the relay device. Sending module 1202 is used to send a first message, which is used to request a change in the parameters of the service quality of the second communication link.

[0250] Optionally, the processing module is specifically configured to: detect that the service quality of the first communication link is lower than a first threshold, the first threshold corresponding to the service quality requirement.

[0251] Optionally, the processing module is specifically configured to: receive a second message from the first terminal device, the second message being used to indicate a reduction in the quality of service of the first communication link.

[0252] Optionally, the processing module is specifically configured to: receive a third message from the first terminal device or the relay device, the third message being used to indicate the service quality of the first communication link; and determine that the service quality of the first communication link is lower than a first threshold, the first threshold corresponding to the service quality requirement.

[0253] Optionally, the sending module is specifically used to: send the first message to the session management network element, wherein the first message is used to reduce the quality of service of the second communication link.

[0254] Optionally, the first message includes a cause value, the cause value indicating that the service quality of the first communication link needs to be changed.

[0255] Optionally, the first message includes first indication information, which indicates that the reason for the change in the second communication link is that the service quality of the first communication link needs to be changed.

[0256] Optionally, the sending module is specifically configured to: send the first message to the access network device, wherein the first message is used to indicate a reduction in the quality of service of the second communication link.

[0257] Optionally, the first message may further include at least one of the following: QoS Flow Identifier (QFI), Service Data Flow (SDF) Information, PC5 Link QoS Flow Identifier (PFI), Data Radio Bearer (DRB) Identifier, and Side Link Radio Bearer (SLRB) Identifier.

[0258] Optionally, the processing module is specifically used to: determine that the service quality of the first link is higher than a second threshold, the second threshold corresponding to the service quality requirement.

[0259] Optionally, the first message is used to instruct the improvement of the quality of service of the second communication link.

[0260] Optionally, determining that the quality of service of the first communication link has changed includes: receiving a fourth message from the first terminal device, the fourth message being used to indicate the addition or removal of the first service flow.

[0261] Optionally, the fourth message includes at least one of the following: Service Data Flow SDF information, PC5 Link QoS Flow Identifier (PFI).

[0262] Optionally, the first message is used to indicate the addition or removal of the first service flow.

[0263] Optionally, the first message includes first indication information, which indicates that the reason for the change in the second communication link is the addition or removal of service flows in the first communication link.

[0264] Figure 13A schematic diagram of another quality of service (QoS) control device according to an embodiment of this application is shown. As shown, the device 1300 includes a second processing module 1301 and a second sending module 1302. The device 1300 can be used to implement the QoS control function involved in any of the above method embodiments. For example, the device 1300 can be a terminal device or an access network device.

[0265] The device 1300 can process messages as a terminal device (such as a remote UE or relay device) or an access network device, and execute the steps in the above method embodiments where the terminal device (such as a remote UE or relay device) or access network device processes the quality of service of the first communication link. The processing module 1301 can be used to support the device 1300 in performing the processing actions in the above method, for example, executing... Figure 4 Or, in option 5, processing actions performed by a terminal device (such as a remote UE or relay device) or an access network device; the sending module 1302 can be used to support the device 1300 in communication, for example, performing... Figure 4 or Figure 5 The receiving action is performed by the terminal device (such as a remote UE or relay device) or access network device. Specifically, please refer to the following description:

[0266] The second processing module 1301 is used to determine that the service quality of the first communication link does not meet the service quality requirements or to determine that the service quality of the first communication link has changed, wherein the first communication link is a communication link between the relay device and the device; the second sending module 1302 is used to send a first message to the relay device, wherein the first message is used to request a change in the parameters of the service quality of the first communication link.

[0267] Figure 14 A schematic diagram of a quality of service control device according to an embodiment of this application is shown. The communication device 1400 can be used to implement the methods described in the above method embodiments regarding terminal devices (such as remote UEs or relay devices) or access network devices. The communication device 1400 may be a chip.

[0268] The communication device 1400 includes one or more processors 1401, which can support the implementation of the communication device 1400. Figure 4 or Figure 5The communication device 1400 includes a method for controlling the quality of service. The processor 1401 can be a general-purpose processor or a dedicated processor. For example, the processor 1401 can be a central processing unit (CPU) or a baseband processor. The baseband processor can be used to process communication data, and the CPU can be used to control the communication device (e.g., network equipment, terminal equipment, or chip), execute software programs, and process the data of the software programs. The communication device 1400 may also include a transceiver unit 1405 for implementing signal input (reception) and output (transmission).

[0269] For example, the communication device 1400 may be a chip, the transceiver unit 1405 may be the input and / or output circuit of the chip, or the transceiver unit 1405 may be the communication interface of the chip, and the chip may be a component of a terminal device, network device or other wireless communication device.

[0270] The communication device 1400 may include one or more memories 1402, which store a program 1404. The program 1404 can be executed by a processor 1401 to generate instructions 1403, causing the processor 1401 to execute the method described in the above method embodiments according to the instructions 1403. Optionally, the memory 1402 may also store data. Optionally, the processor 1401 may also read data stored in the memory 1402, which may be stored at the same memory address as the program 1404, or it may be stored at a different memory address than the program 1404.

[0271] The processor 1401 and memory 1402 can be configured separately or integrated together, for example, integrated on a single board or system on chip (SOC).

[0272] The communication device 1400 may also include a transceiver unit 1405 and an antenna 1406. The transceiver unit 1405 may be referred to as a transceiver, transceiver circuit, or transceiver, and is used to realize the transmission and reception functions of the communication device through the antenna 1406.

[0273] It should be understood that the steps of the above method embodiments can be implemented by hardware logic circuits or software instructions in the processor 1401. The processor 1401 may be a CPU, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, such as discrete gate, transistor logic devices, or discrete hardware components.

[0274] Figure 15 A schematic diagram of a quality of service control device according to an embodiment of this application is shown. The communication device 1500 can be used to implement the methods described in the above method embodiments regarding terminal devices (such as remote UEs or relay devices) or access network devices. The communication device 1500 may be a chip.

[0275] The communication device 1500 includes one or more processors 1501, which can support the implementation of the communication device 1500. Figure 4 or Figure 5 The communication device 1500 includes a method for controlling the quality of service. The processor 1501 can be a general-purpose processor or a dedicated processor. For example, the processor 1501 can be a central processing unit (CPU) or a baseband processor. The baseband processor can be used to process communication data, and the CPU can be used to control the communication device (e.g., network equipment, terminal equipment, or chip), execute software programs, and process the data of the software programs. The communication device 1500 may also include a transceiver unit 1505 for implementing signal input (reception) and output (transmission).

[0276] For example, the communication device 1500 may be a chip, the transceiver unit 1505 may be the input and / or output circuit of the chip, or the transceiver unit 1505 may be the communication interface of the chip, and the chip may be a component of a terminal device, network device or other wireless communication device.

[0277] The communication device 1500 may include one or more memories 1502, which store a program 1504. The program 1504 can be executed by a processor 1501 to generate instructions 1503, causing the processor 1501 to execute the method described in the above method embodiments according to the instructions 1503. Optionally, the memory 1502 may also store data. Optionally, the processor 1501 may also read data stored in the memory 1502, which may be stored at the same memory address as the program 1504, or it may be stored at a different memory address than the program 1504.

[0278] The processor 1501 and memory 1502 can be configured separately or integrated together, for example, integrated on a single board or system on chip (SOC).

[0279] The communication device 1500 may also include a transceiver unit 1505 and an antenna 1506. The transceiver unit 1505 may be referred to as a transceiver, transceiver circuit, or transceiver, and is used to realize the transmission and reception functions of the communication device through the antenna 1506.

[0280] It should be understood that the steps of the above method embodiments can be implemented by hardware logic circuits or software instructions in the processor 1501. The processor 1501 may be a CPU, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, such as discrete gate, transistor logic devices, or discrete hardware components.

[0281] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may be used in actual implementation.

[0282] The methods in the embodiments of this application, if implemented as software functional units and sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution or part of the technical solution of this application can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The storage medium includes at least: USB flash drive, mobile hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, and other media capable of storing program code. The above descriptions are merely specific embodiments of this application, but the protection scope of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for controlling service quality, characterized in that, include: If it is determined that the service quality of the first communication link does not meet the service quality requirements or that the service quality of the first communication link has changed, the first communication link is a communication link between a relay device and a first terminal device, and the first terminal device communicates with the access network device or with a second terminal device through the relay device. Send a first message, which requests a change in the parameters of the quality of service of the second communication link, wherein the second communication link is a communication link between the relay device and the access network device or between the relay device and the second terminal device.

2. The method according to claim 1, characterized in that, The determination that the service quality of the first communication link does not meet the service quality requirements or that the service quality of the first communication link has changed includes: The service quality of the first communication link is detected to be lower than a first threshold, which corresponds to the service quality requirement.

3. The method according to claim 1, characterized in that, The determination that the service quality of the first communication link does not meet the service quality requirements or that the service quality of the first communication link has changed includes: A second message is received from the first terminal device, the second message being used to indicate a reduction in the quality of service of the first communication link.

4. The method according to claim 1, characterized in that, The determination that the service quality of the first communication link does not meet the service quality requirements or that the service quality of the first communication link has changed includes: Receive a third message from the first terminal device or the relay device, the third message being used to indicate the quality of service of the first communication link; It is determined that the service quality of the first communication link is lower than a first threshold, the first threshold corresponding to the service quality requirement.

5. The method according to any one of claims 1-4, characterized in that, Sending the first message includes: The first message is sent to the session management network element, and the first message is used to reduce the quality of service of the second communication link.

6. The method according to claim 5, characterized in that, The first message includes a cause value, which indicates that the quality of service of the first communication link needs to be changed.

7. The method according to claim 5, characterized in that, The first message includes a first indication information, which indicates that the reason for the change in the second communication link is that the service quality of the first communication link needs to be changed.

8. The method according to claim 2, characterized in that, Sending the first message includes: The first message is sent to the access network device, and the first message is used to indicate a reduction in the quality of service of the second communication link.

9. The method according to any one of claims 1-4 and 6-8, characterized in that, The first message also includes at least one of the following: QoS Flow Identifier (QFI), Service Data Flow SDF Information, PC5 Link QoS Flow Identifier (PFI), Data Radio Bearer (DRB) Identifier, and Side Link Radio Bearer (SLRB) Identifier.

10. The method according to claim 1, characterized in that, The determination that the service quality of the first communication link does not meet the service quality requirements or that the service quality of the first communication link has changed includes: The service quality of the first communication link is determined to be higher than a second threshold, which corresponds to the service quality requirement.

11. The method according to claim 9, characterized in that, The first message is used to instruct the improvement of the quality of service of the second communication link.

12. The method according to claim 1, characterized in that, The determination that the quality of service of the first communication link has changed includes: A fourth message is received from the first terminal device, the fourth message being used to indicate the addition or removal of the first service flow.

13. The method according to claim 12, characterized in that, The fourth message includes at least one of the following: Service data stream SDF information, PC5 link QoS flow identifier PFI.

14. The method according to claim 12 or 13, characterized in that, The first message is used to indicate the addition or removal of the first service flow.

15. The method according to claim 14, characterized in that, The first message includes a first indication information, which indicates that the reason for the change in the second communication link is the addition or removal of a service flow in the first communication link.

16. A service quality control device, characterized in that, include: The processing module is used to determine that the service quality of the first communication link does not meet the service quality requirements or to determine that the service quality of the first communication link has changed. The first communication link is a communication link between a relay device and a first terminal device. The first terminal device communicates with the access network device or with a second terminal device through the relay device. The sending module is used to send a first message, which requests a change in the parameters of the quality of service of a second communication link, wherein the second communication link is a communication link between the relay device and the access network device or between the relay device and the second terminal device.

17. The apparatus according to claim 16, characterized in that, The processing module is specifically used for: The service quality of the first communication link is detected to be lower than a first threshold, which corresponds to the service quality requirement.

18. The apparatus according to claim 16, characterized in that, The processing module is specifically used for: A second message is received from the first terminal device, the second message being used to indicate a reduction in the quality of service of the first communication link.

19. The apparatus according to claim 16, characterized in that, The processing module is specifically used for: Receive a third message from the first terminal device or the relay device, the third message being used to indicate the quality of service of the first communication link; It is determined that the service quality of the first communication link is lower than a first threshold, the first threshold corresponding to the service quality requirement.

20. The apparatus according to any one of claims 16-19, characterized in that, The sending module is specifically used for: The first message is sent to the session management network element, and the first message is used to reduce the quality of service of the second communication link.

21. The apparatus according to claim 20, characterized in that, The first message includes a cause value, which indicates that the quality of service of the first communication link needs to be changed.

22. The apparatus according to claim 20, characterized in that, The first message includes a first indication information, which indicates that the reason for the change in the second communication link is that the service quality of the first communication link needs to be changed.

23. The apparatus according to claim 17, characterized in that, The sending module is specifically used for: The first message is sent to the access network device, and the first message is used to indicate a reduction in the quality of service of the second communication link.

24. The apparatus according to claim 23, characterized in that, The first message also includes at least one of the following: QoS Flow Identifier (QFI), Service Data Flow SDF Information, PC5 Link QoS Flow Identifier (PFI), Data Radio Bearer (DRB) Identifier, and Side Link Radio Bearer (SLRB) Identifier.

25. The apparatus according to claim 16, characterized in that, The processing module is specifically used for: The service quality of the first communication link is determined to be higher than a second threshold, which corresponds to the service quality requirement.

26. The apparatus according to claim 25, characterized in that, The first message is used to instruct the improvement of the quality of service of the second communication link.

27. The apparatus according to claim 16, characterized in that, The processing module is specifically used for: A fourth message is received from the first terminal device, the fourth message being used to indicate the addition or removal of the first service flow.

28. The apparatus according to claim 27, characterized in that, The fourth message includes at least one of the following: Service data stream SDF information, PC5 link QoS flow identifier PFI.

29. The apparatus according to claim 27 or 28, characterized in that, The first message is used to indicate the addition or removal of the first service flow.

30. The apparatus according to claim 29, characterized in that, The first message includes a first indication information, which indicates that the reason for the change in the second communication link is the addition or removal of a service flow in the first communication link.

31. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program for execution by the device, the computer program including program instructions for performing the method as described in any one of claims 1-15.

32. A chip, characterized in that, The chip includes a processor and a data interface. The processor reads program instructions stored in the memory through the data interface to execute the method as described in any one of claims 1-15.

Images