Method and apparatus for relay operation in a wireless communication system

The method for relay nodes in 5G networks generates and applies QoS rules to both Uu and PC5 links, addressing the inconsistency in QoS treatment and ensuring end-to-end service quality in relayed communications.

JP7796110B2Active Publication Date: 2026-01-08SAMSUNG ELECTRONICS CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023509807
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-08-09
Filing Date
2021-08-11
Publication Date
2026-01-08
Estimated Expiration
2041-08-11

AI Technical Summary

Technical Problem

Existing wireless communication systems, particularly in 5G networks, lack explicit support for end-to-end Quality of Service (QoS) management in relay scenarios, specifically for uplink communications between user equipment and the network via relay nodes, leading to inconsistencies in QoS treatment between Uu and PC5 links.

Method used

A method and apparatus for a relay node to support end-to-end QoS by receiving downlink packets from the network, generating or updating QoS rules based on indicators, and applying these rules to both the Uu and PC5 links to ensure consistent QoS treatment across the communication path.

Benefits of technology

Ensures efficient and consistent Quality of Service across both Uu and PC5 links, maintaining the expected service quality in relayed communications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007796110000005
    Figure 0007796110000005
  • Figure 0007796110000006
    Figure 0007796110000006
  • Figure 0007796110000007
    Figure 0007796110000007
Patent Text Reader

Abstract

A method performed by a relay node in a wireless communication system and the relay node are provided. [Solution] A method performed by a relay node for supporting end-to-end (e2e) Quality of Service (QoS) for uplink (UL) communication between a user equipment (UE) and a network via the relay node of the present invention includes a step of receiving a downlink (DL) packet for the UE from the network, and a step of generating or updating a QoS rule, wherein the DL packet includes a value of a first indicator of a QoS flow on a first link between the relay node and the network, and the QoS rule is derived based on the value of the first indicator, and optionally, the generated or updated QoS rule corresponds to the UE or applies to a QoS flow on a second link with the UE.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a method, an apparatus and a system for reflected Quality of Service (QoS) for a user equipment (UE) in a network relay, and more particularly to a method, an apparatus and a system for reflected Quality of Service (QoS) for a user equipment (UE) in a network relay. th The present invention relates to a method, an apparatus, and a system for reflected QoS to a UE at a network relay in a (QoS generation) communication system. [Background technology]

[0002] Since the commercialization of fourth-generation (4G) communication systems, considerable efforts have been made to develop improved fifth-generation (5G) or preliminary 5G communication systems to meet the increasing demand for wireless data traffic.

[0003] This is why "5G communication systems" or "pre-5G communication systems" are called "beyond 4G network communication systems" or "post-LTE (post long term evolution) systems."

[0004] To achieve high data transmission speeds, the implementation of 5G communication systems on ultra-high frequency bands (millimeter (mmWave), e.g., the 60 GHz band) is being considered. To reduce radio wave path loss and extend the propagation distance of radio waves in the millimeter wave band, 5G communication system technologies such as beamforming, massive multiple-input multiple-output (MIMO), full-dimensional multiple-input (FD-MIMO), array antennas, analog beamforming, and large-scale antenna systems are being discussed.

[0005] In addition, technologies such as evolved small cells, advanced small cells, cloud radio access network (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, moving networks, cooperative communications, coordinated multi-points (CoMP), and receiver interference cancellation are also being developed to improve system networks for 5G communication systems.

[0006] Furthermore, in 5G communication systems, advanced coding modulation (ACM) methods such as hybrid FSK (frequency shift keying)-QAM (quadrature amplitude modulation) and sliding window superposition coding (SWSC), as well as advanced access technologies such as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) have been developed.

[0007] The Internet, a human-centered network where people generate and consume information, has evolved into the Internet of Things (IoT) network, where information is exchanged and processed among distributed, object-like components. The Internet of Everything (IoE) technology is emerging, combining IoT-related technologies with technologies for processing big data, for example, through connections to cloud servers. Achieving IoT requires a variety of technological elements, including sensing technology, wired and wireless communications and network infrastructure, service interface technology, and security technology. In recent years, research has focused on technologies such as sensor networks for connecting objects, machine-to-machine (M2M) communications, and machine-type communications (MTC). In the IoT environment, intelligent Internet technology (IT) services are provided that collect and interpret data obtained from interconnected objects, thereby creating new value for human life. As existing information technology (IT) and various industries are integrated and combined with each other, IoT will be applied to various fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and high-quality medical services.

[0008] Various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies related to sensor networks, M2M communication, and MTC are being implemented using 5G communication technologies including beamforming, MIMO, and array antennas. The application of cloud RAN as the big data processing technology mentioned above is one example of the fusion of 5G communication technology and IoT technology.

[0009] As mobile communication systems evolve, a variety of services can be provided, and therefore a method for efficiently transmitting and receiving reference signals in wireless communication systems is required.

[0010] The above information is provided solely as background information to aid in the understanding of the present invention, and no determination is being made, or any assertion being made, as to whether any of the above content is applicable as prior art with respect to the present invention. Summary of the Invention [Problem to be solved by the invention]

[0011] The present invention has been made in view of the above-mentioned conventional techniques, and an object of the present invention is to provide a method performed by a relay node in a wireless communication system, and the relay node. [Means for solving the problem]

[0012] In order to achieve the above object, according to one aspect of the present invention, a method performed by a relay node for supporting end-to-end (e2e) Quality of Service (QoS) for uplink (UL) communication between a user equipment (UE) and a network via the relay node includes the steps of receiving a downlink (DL) packet for the UE from the network, and generating or updating a QoS rule, wherein the DL packet includes a value of a first indicator of a QoS flow on a first link between the relay node and the network, and the QoS rule is derived based on the value of the first indicator. [Effects of the Invention]

[0013] SUMMARY OF THE INVENTION The present invention provides a method for efficiently transmitting and receiving reference signals in a wireless communication system.

[0014] The above-described forms and other aspects, features and advantages of embodiments of the present invention will become more apparent from the following description taken in conjunction with the drawings. [Brief explanation of the drawings]

[0015] [Figure 1]1 is a diagram illustrating a typical QoS (Quality of Service) model in a fifth generation system (5GS) according to the related art - uplink (UL) packet matching and mapping of QoS flows to access network resources. [Figure 2] 1 illustrates an example of the use of UL transmission of data following packet matching by a higher layer and mapping to a Data Radio Bearer (DRB) by a lower layer according to the related art. [Figure 3] FIG. 1 illustrates an example of the use of reflective QoS and derived QoS rules according to the related art. [Figure 4] A diagram showing communication between a remote user equipment (UE) and a 5G core network (5GC) via a relay UE according to the related art. [Figure 5] FIG. 1 illustrates an example of two UEs with two PC5 unicast links according to the related art. [Figure 6] 3 is a flowchart of message transmission and reception by a relay UE, a remote UE, and a radio access network (RAN) according to an embodiment of the present invention. [Figure 7] 1 is a diagram for explaining a problem with a predetermined technique according to an embodiment of the present invention. [Figure 8] 1 is a diagram illustrating a network entity according to an embodiment of the present invention; [Figure 9] 1 is a diagram illustrating a base station (BS) according to an embodiment of the present invention; [Figure 10] FIG. 1 illustrates a user equipment (UE) according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0016] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] The present invention will now be described in detail with reference to the accompanying drawings, in which like reference numerals refer to like parts, components, and structures throughout the drawings.

[0017] Aspects of the present invention address at least the problems and / or shortcomings discussed above and provide at least the advantages described below. Accordingly, one aspect of the present invention provides an apparatus and method for reflective Quality of Service (QoS) to a user equipment (UE) for network relay in a wireless communication system.

[0018] Additional aspects will be set forth in part in the description that follows, and in part will be apparent from such description or will be learned through aspects of the embodiments presented.

[0019] According to one aspect of the present invention, there is provided a method for supporting end-to-end (e2e) quality of service (QoS) for uplink (UL) communication between a user equipment (UE) (e.g., a remote UE) and a network (e.g., a 5G core network (5GC)) via a relay node (e.g., a relay UE). The method is performed by a relay node and includes the steps of receiving a downlink (DL) packet for the UE from the network (e.g., from a radio access network (RAN)), and generating or updating a QoS rule (e.g., a derived QoS rule), wherein the DL packet includes a value of a first indicator (e.g., a QoS flow identifier (QFI)) of a QoS flow on a first link (e.g., an access (Uu) link) between the relay node and the network, and the QoS rule is derived based on the value of the first indicator, or, alternatively, the generated or updated QoS rule applies to a QoS flow corresponding to the UE or on a second link (e.g., a first PC5 link) to the UE.

[0020] According to one aspect of the present invention, there is provided a relay node supporting end-to-end (e2e) Quality of Service (QoS) for uplink (UL) communication between a user equipment (UE) and a network via the relay node, the relay node comprising: a transceiver and at least one processor coupled to the transceiver, the at least one processor configured to receive downlink (DL) packets for the UE from the network and generate or update QoS rules, the DL packets including a value of a first indicator of a QoS flow on a first link between the relay node and the network, the QoS rules being derived based on the value of the first indicator, or alternatively, the generated or updated QoS rules apply to a QoS flow on a second link corresponding to or with the UE.

[0021] Other aspects, advantages, and principal features of the present invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the drawings, discloses various embodiments of the invention.

[0022] The following description with reference to the drawings is provided to aid in a comprehensive understanding of various embodiments of the present invention as defined by the claims and their equivalents. The content includes various specific details to aid in understanding, but these should be considered merely as examples. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and concept of the present invention. Furthermore, descriptions of well-known functions and structures are omitted for clarity and conciseness.

[0023] The terms and phrases used in the following description and claims are not limited to their dictionary meanings, but are used by the inventors simply to allow a clear and consistent understanding of the present invention. Therefore, those skilled in the art will clearly understand that the following description of various embodiments of the present invention is provided for illustrative purposes only, and is not intended to limit the present invention as defined by the claims and their equivalents.

[0024] It should be understood that singular forms include plural referents unless the relevant context clearly dictates otherwise. Thus, for example, a reference to "one component surface" includes a reference to one or more of such surfaces.

[0025] The terms used herein are merely used to describe specific embodiments of the present invention and do not limit the scope of other embodiments of the present invention. The singular term includes the plural term unless the context clearly dictates otherwise. Terms used herein, including technical and scientific terms, have the same meaning as commonly understood by those skilled in the art. Terms used herein that are defined in a general dictionary are interpreted as meanings consistent with or similar to the meanings in the context of the relevant art. Unless explicitly defined in the present invention, such terms are not to be interpreted in an ideal or overly formal sense. In some cases, terms defined in the present invention may not fall within the scope of the embodiments of the present invention.

[0026] Throughout this specification and the claims, the terms "comprise" and "include" and derivatives such as "comprising" and "including" mean that "comprises" does not "limit" and does not exclude other properties, components, integers, processes, operations, functions, features, and the like.

[0027] Throughout this specification and the claims, the terms "comprise" and "include" and derivatives such as "comprising" and "including" mean that "comprises" does not "limit" and does not exclude other properties, components, integers, processes, operations, functions, features, and the like.

[0028] In the various embodiments described below, a hardware-based system will be described as an example, but since the various embodiments of the present invention include techniques using both hardware and software, the various embodiments of the present invention do not exclude a software-based system.

[0029] The advantages, features, and methods for achieving the same will become clearer with reference to the following detailed description of the embodiments with reference to the drawings. In this regard, the embodiments of the present invention may take different forms and should not be construed as being limited to the content disclosed in this specification. Thus, the embodiments of the present invention are provided so that the present invention will be thorough and complete, and will fully convey the concept of the embodiments of the present invention to those skilled in the art. Throughout this specification, the same reference numerals refer to the same elements.

[0030] Furthermore, in this specification, "including at least one of a, b, or c" means "including only a, including only b, including only c, including a and b, including b and c, including a and c, or including all of a, b, and c."

[0031] Examples of terminals include user equipment (UE), mobile stations (MS), cellular phones, smartphones, computers, or multimedia systems that perform communication functions.

[0032] In this specification, the control unit is referred to as a processor.

[0033] In this specification, a hierarchy (or hierarchy device) is referred to as an entity.

[0034] It should be understood that each block in the flowchart or combination of blocks in the flowchart is implemented by computer program instructions. Such computer program instructions are implemented on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that the instructions executed by the processor of the computer or other programmable data processing device create modules that perform the functions described in the flowchart blocks. Such computer program instructions are stored in computer-executable or computer-readable memory that causes the computer or other programmable data processing device to implement the functions in a particular manner, such that the instructions stored in computer-executable or computer-readable memory can also create an article of manufacture that includes instruction modules for performing the functions described in the flowchart blocks. Computer program instructions are implemented on a computer or other programmable data processing device, such that a series of operations are performed by the computer or other programmable data processing device to create a computer-implemented process, and the instructions for the computer or other programmable data processing device provide operations for performing the functions described in the flowchart blocks.

[0035] Also, each block represents a module, segment, or portion of code including one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative embodiments, the operations described in the blocks may occur in a different order than that shown in the drawings. For example, two blocks that appear consecutive due to related functions may actually be executed substantially concurrently, or the blocks may sometimes be executed in the opposite order.

[0036] The term "module" or "unit" as used herein refers to a software component or a hardware component such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit), and the "module" or "unit" performs a corresponding function. However, the "module" or "unit" is not limited to software or hardware. The term "module" or "unit" refers to a component configured in an addressable storage medium or configured to execute one or more processors. Thus, as an example, a "module" or "unit" includes software components, object-oriented software components, class components, and task components, as well as components such as processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The components and functions provided in the "module" or "unit" may be further combined into fewer components and the "module" or "unit," or separated into additional components and the "module" or "unit." Furthermore, the components and "modules" or "units / machines" may be implemented to replicate one or more central processing units (CPUs) within a device or a security multimedia card. In an embodiment of the present invention, a "module" or "unit / machine" may include one or more processors.

[0037] In the description of this specification, if a detailed description of related well-known functions or settings is deemed to unnecessarily obscure the gist of the present invention, the detailed description will be omitted. Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

[0038] The terms for identifying access (connection) nodes, the terms for network entities, the terms for messages, the terms for interfaces between network entities, and the terms for various identification information are given as examples for the sake of convenience. Therefore, the present invention is not limited to the terms described below, and other terms for entities having equivalent technical meanings may be used.

[0039] For ease of explanation, 3GPP (registered trademark) LTE (3 rd In this specification, terms and names defined in the Generation Partnership Project Long Term Evolution (LTE) standard are used. However, the present invention is not limited to such terms and names and is equally applicable to systems based on other standards. For convenience of explanation, the term eNB (evolved Node B) used in this specification is used interchangeably with the term gNB (next generation Node B). That is, a base station described as eNB refers to a gNB. In addition, the term "terminal" refers to not only mobile phones, NB-IoT (Internet of Things) devices, and sensors, but also other wireless communication devices.

[0040] In the following, a base station allocates resources to a terminal and includes at least one of a gNodeB, an eNodeB, a NodeB, a BS (base station), a radio access unit, a base station controller, or a node on a network. Examples of a terminal include a UE (user equipment), an MS (mobile station), a cellular phone, a smartphone, a computer, or a multimedia system that performs communication functions. It goes without saying that the present invention is not limited to the above examples.

[0041] In particular, the present invention is applied to 3GPP (registered trademark) NR (New Radio (5th generation mobile communication standard)). Furthermore, the present invention is applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, health management, digital education, retail, security-related, and safety-related services) based on 5G communication technology and IoT-related technology. The term "eNB" used in the present invention is used interchangeably with the term "gNB" for convenience of explanation. That is, a base station described as an eNB indicates a gNB. Furthermore, the term "terminal" refers to not only mobile phones, NB-IoT devices, and sensors, but also other wireless communication devices.

[0042] Although LTE (long term evolution), LTE-A (long term evolution-advanced), LTE Pro, or 5G (fifth generation) (or NR (next generation mobile communication)) systems are described below as examples, embodiments of the present invention are also applicable to other communication systems having similar technical backgrounds or channel configurations. The present invention is also applicable to other communication systems with some modifications without departing from the scope of the present invention.

[0043] According to one embodiment of the present invention, the present invention provides a method, apparatus, and system for UE-to-network relay-reflected QoS (RQoS). The following examples apply to 3GPP® 5G and use terminology related thereto. However, those skilled in the art will appreciate that the techniques disclosed herein are not limited to such examples or 3GPP® 5G, but rather apply to all suitable systems and standards, such as one or more existing and / or next-generation wireless communication systems and standards.

[0044] For example, the functions and other characteristics of various network entities disclosed herein may apply to corresponding or equivalent entities or characteristics within other communication systems or standards, where a corresponding or equivalent entity or characteristic is considered to be an entity or characteristic that performs the same or similar role, function, operation, or purpose within the network.

[0045] Those skilled in the art will appreciate that the present invention is not limited to the specific examples disclosed herein.

[0046] The techniques disclosed herein are not limited to 3GPP 5G.

[0047] In the examples disclosed herein, one or more entities may be substituted with one or more other entities that are equivalent or perform a corresponding function, process, or operation.

[0048] In the examples disclosed herein, one or more messages may be replaced with one or more other messages, signals, or other types of information carriers that are equivalent or convey corresponding information.

[0049] One or more additional components, entities, and / or messages may be added to the examples disclosed herein.

[0050] One or more non-essential components, entities, and / or messages are omitted in one embodiment.

[0051] In one example, the function, process, or operation of a particular entity may be divided among two or more separate entities in another example.

[0052] In one instance, the functions, processes, or actions of two or more separate entities may be performed by a single entity in another instance.

[0053] In one example, information conveyed in a particular message may in another example be conveyed by two or more independent messages.

[0054] Information that is conveyed in two or more separate messages in one example is conveyed as one message in another example.

[0055] The order in which the operations are performed may be varied in other instances where possible.

[0056] The transmission of information between network entities is not limited to the particular formats, types, and / or sequences of messages described with respect to the examples disclosed herein.

[0057] According to one embodiment of the present invention, the present invention is provided in the form of a device / apparatus / network entity configured to perform one or more defined network functions and / or the method, and an embodiment of the present invention is provided in the form of a system (e.g., a network) including one or more such devices / apparatus / network entities and / or the method.

[0058] The following documents are referenced in this specification:

[0059] [1] 3GPP (registered trademark) TS 24.501 V16.5.1 [2] 3GPP (registered trademark) TS 23.501 V16.3.0 [3] 3GPP (registered trademark) TS 23.752 V0.4.0 [4] 3GPP (registered trademark) TS 23.287 V16.3.0 [5] 3GPP (registered trademark) TS 24.587 V16.1.0

[0060] Various abbreviations, abbreviations and definitions used herein are defined at the end of this description.

[0061] In the present invention, the following abbreviations, abbreviations and definitions are used:

[0062] 3GPP (registered trademark): 3rd Generation Partnership Project 5G: 5th Generation 5GC: 5G Core 5GCN: 5G Core Network 5GS: 5G System 5GSM: 5G Session Management 5QI: QoS on Uu link AN: Access Network DL: Downlink DRB: Data Radio Bearer e2e end-to-end ID: Identity / Identification IE: Information Element IP: Internet Protocol L2: Layer 2 N1 mode: A mode in which the UE allows access to the 5G core network via the 5G access network. NAS: Non-Access Stratum NB: Narrow Band NR:New Radio PC5: Direct communication link between capable ProSe UEs PC5-S: PC5 Signaling PDU: Protocol Data Unit PFI / PQFI: PC5 QoS Flow Identifier PQI:PC5 QFI ProSe: Proximity Services QFI: QoS Flow Identifier QoS: Quality of Service QRI:QoS Rule Identifier RAN: Radio Access Network Rel:Release RQ Timer: RQoS Timer RQI:RQoS Indication RQoS: Reflective QoS SMF: Session Management Function TS: Technical Specification UE: User Equipment UL: Uplink UPF: User Plane Function Uu interface: the air interface between the terminal and the base station / access point V2X: Vehicle-to-Everything WB: WideBand

[0063] Overview of signaled and derived QoS rules

[0064] The 5G QoS model is based on QoS flows, which are the fine-grained unit of QoS differentiation for a PDU session. A QoS flow is identified by a QoS flow identifier (QFI). A QoS flow is associated with a QoS rule and options for other QoS parameters.

[0065] Generally, there are two types of QoS rules in 5GS: signaled QoS rules and derived QoS rules.

[0066] As the name suggests, a signaled QoS rule is a QoS rule that is signaled or exchanged between the UE and the network (SME) using 5GS Session Management (5GSM) messages. The signaled QoS rule indicates, for example, whether the QoS rule is a basic QoS rule or a non-basic QoS rule. As specified in TS 24.501 [1], each signaled QoS rule includes the following:

[0067] a) an indication as to whether the QoS rule is a basic QoS rule; b) QoS Rule Identifier (QRI); c) QoS Flow Identifier (QFI); d) optionally, a set of packet filters; and e) Preference value

[0068] QoS rules and packet filters are used for uplink (UL) user data packets matching IPv4, IPv6, IPv4v6 Protocol Data Unit (PDU) session, or Ethernet Protocol Data Unit (PDU) session types, i.e., such rules and packet filters allow for association between data and QoS flows, whereby data is processed based on the characteristics of the QoS flows identified by the QFI, which is hereinafter referred to as packet matching.

[0069] On the other hand, derived rules are QoS rules that are not signaled but are derived depending on the situation. Derived rules are used by UEs that support Reflected QoS (RQoS). A UE that supports RQoS must indicate this by setting the RQoS bit to "Reflective QoS supported" in the 5GSM Capabilities IE of the PDU Session Setup Request message. RQoS means that the UE reflects the treatment of UL data packets based on the QoS treatment received on the downlink (DL). To do so, the UE derives QoS rules based on the received DL packets (to which RQoS applies), and then the UL data is processed and transmitted based on the derived QoS rules, as described below.

[0070] In a UE that supports RQoS, the lower layers of the UE receive DL packets with a QFI and an RQI (RQoS indicator) indicating that the data for the DL flow is subject to RQoS. The lower layers provide the QFI and RQI to the NAS, which then derives the QoS rules for UL transmission as follows:

[0071] a) The QFI of the derived QoS is set to the received QFI. b) The priority value of the derived QoS rule is set to 80 (decimal). c) The packet filter for the UL direction of the derived QoS rule is set to the packet filter derived for the UL direction.

[0072] When the UE derives a QoS rule, it concatenates and starts a timer T3583 (called the RQ timer) that guards the period during which the derived rule is maintained. The value of the timer is signaled to the UE using a 5GSM message, or the UE applies a base value as described in [1].

[0073] The UE updates the derivation rules (see [1]) as follows:

[0074] a) The UE shall restart timer T3583 associated with the QoS rule derived using the last received RQ timer value during the UE-Requested PDU Session Setup procedure for a PDU session or the Network-Requested PDU Session Modification procedure for a PDU session. If no RQ timer value is received during the UE-Requested PDU Session Setup procedure for a PDU session or the Network-Requested PDU Session Modification procedure for a PDU session, the base standard RQ timer value is used.

[0075] b) If the QFI value for the DL user data packet is different from the stored QFI value for the derived QoS rule, the UE shall replace the stored QFI value for the derived QoS rule with the new QFI value for the derived QoS rule.

[0076] The condition for deleting the derived QoS rule is given below from [1].

[0077] [Table 1]

[0078] The UE has both signaled and derived QoS rules, and via either one or two of them, the UE uses such rules for uplink packet matching, i.e., matching data to a particular QoS flow for transmission and processing according to the QoS profile and characteristics of the QoS flow, e.g., based on the associated QFI.

[0079] Packet matching in the UL direction is performed by the UE as follows, from TS 24.501 [1]:

[0080] [Table 2]

[0081] After a data packet is matched to a QoS flow, the UE provides the data packet and the QFI of the QoS flow to which the data packet is matched, so that the lower layer maps the QoS flow (identified with the QFI) to the access network resources, so that the data packet matched to the QoS flow (identified with the QFI) is transmitted using the mapped access network resources, and the transmission is accordingly processed by the data packet according to the QoS profile of the flow and the QFI.

[0082] FIG. 1 is a diagram illustrating a general QoS model in 5GS according to the related art—uplink (UL) packet matching and mapping of QoS flows to access network resources in one embodiment of the present invention.

[0083] Referring to Figure 1 (from TS 23.501 [2]), the general QoS model for 5GS is shown, where both UL packet matching and mapping to resources are visually described.

[0084] It must be known that multiple QoS rules have the same QFI, so that packets matched based on such different QoS rules will be subject to the same management by the same QFI.

[0085] We then propose how both the signaling and the derived QoS rules are used by the UE.

[0086] For purposes of example, assume that a UE has a PDU session #1 with two QoS rules identified as QoS Rule Identifier (QRI) A and QoS Rule Identifier QRI B. Assume that QRI A is for a basic QoS rule and QRI B is for a non-basic QoS rule. Assume that QRI A has a priority value of 2 and QRI B has a priority value of 1, meaning that QRI B will be checked before QRI A because a lower priority value means a higher priority.

[0087] Since the PDU session is of IPv6 type, it is assumed that the UE has the following components for the packet filter of the QoS rule identified by QRI B:

[0088] -Source IP address: IP-Src-Y -Destination IP address: IP-Dst-Z -Source port: #222 -Destination port: #333 -Next Header: "someHeader"

[0089] Also assume that the QoS rule identified by QRI B has an associated QFI#20. It should be noted that the above parameter values ​​are used as examples only.

[0090] FIG. 2 illustrates an example use case for UL transmission of data following packet matching by higher layers and mapping to Data Radio Bearers (DRBs) by lower layers.

[0091] 2, in conjunction with the above, in step 210 of Fig. 2, if the UE has UL data sent from the source IP address and port number shown above to the destination IP and port number shown above and the next header field set to the value shown above, it will match the UL data to the QoS flow identified by QFI#20 in step 220, since the PF matching information of the data to be transmitted is part of QRI B.

[0092] The UE then provides a UL data packet to the lower layer indicating that the QFI is #20, and the lower layer then maps the data for the QFI to the corresponding Data Radio Bearer (DRB), in this case DRB 5, in step S230 of FIG.

[0093] In the DL, if a given DL packet requires QoS treatment according to the QoS profile defined by the QFI 20, the access network (AN) typically transmits the packet via the DRB 5.

[0094] For simplicity, the interaction between the AN and the UPF is not shown in FIG.

[0095] The above example assumes that the UE has used signaling QoS rules, namely QRI A and QRI B.

[0096] FIG. 3 is a diagram illustrating an example of the use of reflective and derived QoS rules according to the related art.

[0097] Referring to Figure 3, assuming that the reflected QoS applies to this PDU session, the access network receives a DL packet with an indicator that the reflected QoS should be used for the DL packet (see section 5.7.5.3 of [2]). As shown in step S310 of Figure 3, having determined to use a different QFI for the DL packet, the AN transmits the DL packet via DRB 6, indicating to the UE that RQoS should be applied to the flow. Although not shown, the AN also indicates to the UE the QFI that should be used for the UL traffic.

[0098] While this example shows that DRB 6 is used to transmit DL packets that must be processed by the QoS profile associated with QFI 18, it should be noted that different QFIs can be mapped to the same DRB. Thus, DL packets can have a different QFI, e.g., QFI 18, but still utilize the same DRB, e.g., DRB 5, and this is also possible when DRB 5 is used to send and receive data associated with QFI 20.

[0099] When a lower layer in the UE receives a DL packet and checks the RQI indicator, it passes the packet to the upper layer, which then provides the RQI and QFI that should be used for the corresponding UL packet. The RQI indicates that RQoS should be applied to the UL, and the associated QFI indicates which UL packet should be sent with that QFI. This is shown in step S320 of Figure 3.

[0100] Based on the received indication, the (higher layer of) the UE generates derived QoS rules and concatenately starts timer T3583 as described in [1].

[0101] This is shown in step S330 of FIG.

[0102] Although not shown in FIG. 3, any UL packets corresponding to the DL packets with the indicated RQI are concatenated to QFI 18 until the UE deletes the derived QoS rule, e.g., after T3583 expires.

[0103] <5G Proximity Service (ProSe) Overview>

[0104] Proximity Services (ProSe) for 5GS is being studied in TR 23.752 [3]. One of the main topics under study is support for a UE-to-network relay (hereinafter referred to as a "relay UE") that operates in a manner that allows a remote UE to connect to 5GS (in this case, the remote UE is considered to be out of coverage). In this way, the remote UE connects to the relay UE via a direct connection over the air (specifically, using 3GPP® NR (new radio) access technology), and the relay UE acts as a layer 3 type relay. Although other proposals exist in which the relay UE acts as a layer 2 relay, this specification assumes that the relay UE essentially acts as a layer 3 relay entity.

[0105] All possible direct communication between ProSe UEs, e.g., between a remote UE and a relay UE, is via a direct link using NR access, the so-called PC5, while the relay UE uses the Uu interface to communicate with the network.

[0106] FIG. 4 is a diagram illustrating communication between a remote user equipment (UE) and a 5G core network (5GC) via a relay UE according to the related art.

[0107] Referring to Figure 4 (from [3]), an example is shown in which a remote UE is connected to a 5G core (5GC) via a relay UE.

[0108] Referring to Figure 3, communication between the remote UE and the 5GC must support end-to-end (e2e) QoS so that the service in use is satisfied in terms of processing data packets.

[0109] To meet e2e QoS requirements, the QoS on the PC5 link, i.e., PQI, must correspond to the QoS on the Uu link, i.e., 5QI. For example, there must be a predetermined match between the 5QI and PQI in use on that interface so that e2e service meets a predetermined set of requirements and expectations. Therefore, changes in the QoS level on one link (e.g., the Uu link) are expected to affect the overall e2e QoS, even if the QoS on the PC5 link (i.e., PQI) remains unchanged.

[0110] The following is explained in solution #24 of [3] regarding the e2e QoS processing of the model with reference to Figure 2.

[0111] [Table 3]

[0112] Based on the text cited in Table 3, it is expected that for a known 5QI on the Uu interface, the relay UE will select a matching QoS level, i.e., PQI, for the PC5 link with the remote UE. To do so, it is also expected that the relay UE will be appropriately configured with information that enables it to match the 5QI value to the appropriate corresponding PQI value, so that the e2e communication achieves the expected quality of experience.

[0113] For PC5 links, 5G ProSe will most likely use existing or similar solutions defined for vehicle-to-everything (V2X) communications, some of which support the establishment and modification of direct links between two vehicles. For example, TS 23.287 [4] describes different procedures for the establishment and modification of PC5 links, while details on the associated messages can be found in TS 24.587 [5].

[0114] FIG. 5 is a diagram illustrating an example of two UEs with two PC5 unicast links according to the related art.

[0115] Referring to Figure 5 (from [4]), an example of a PC5 unicast link being set up between two UEs is shown.

[0116] While Figure 5 assumes that the application example using the PC5 link is for V2X communications, the PC5 link is also used for ProSe in Rel-17. Therefore, the V2X example is for illustrative purposes to understand how the current PC5 link works, but should not be considered limited to PC5 communications only for V2X services. The following content pertains to the use of the PC5 link for V2X communications.

[0117] A PC5 unicast link between two UEs enables V2X communication between one or more peer V2X services in the UE. All V2X services in a UE using the same PC5 unicast link use the same application hierarchical ID.

[0118] A PC5 unicast link supports one or more of the above V2X service types when one or more V2X service types are associated with at least the peer application tier ID of the PC5 unicast link. For example, as shown in Figure 5, UE A and UE B have two PC5 unicast links, one link between peer application tier ID1 / UE A and application tier ID2 / UE B, and one link between peer application tier ID3 / UE A and application tier ID4 / UE B.

[0119] When multiple V2X service types utilize a PC5 unicast link, one PC5 QoS flow identified by a PFI (PC5 QoS Flow Identifier, also abbreviated as PQFI) is associated with two or more V2X service types.

[0120] The preceding information is provided solely as background information to aid in the understanding of the present invention, and no determination is being made or any assertion made as to whether any of the foregoing is applicable as prior art with respect to the present invention.

[0121] The prior art has at least the following problems.

[0122] It is not clear how the reflected QoS on the Uu link affects the QoS on the PC5 link.

[0123] For true support of e2e QoS, a change in QoS on one leg / link of a communication requires a change in QoS on the other leg / link of the communication. In particular, the QoS on the Uu link, i.e., between the relay UE and the RAN, changes due to the use of RQoS. When this occurs, the relay UE begins to utilize a different QFI and hence QoS treatment for UL transmissions on the Uu interface. However, the current behavior of such a UE with respect to the QoS used on PC5 is not specified.

[0124] That means that when RQoS is applied, true e2e QoS is still not explicit or supported.

[0125] Therefore, in summary, the use of RQoS by relay UEs and its impact on PC5 link QoS is not specified.

[0126] An embodiment of the present invention provides a solution to this problem. For example, in light of the above-mentioned problems, an embodiment of the present invention provides one or more of the following solutions.

[0127] In one embodiment of the present invention, the relay UE adjusts the QoS of the PC5 used to communicate with the remote UE following the use and application of the RQoS by the relay UE to UL data relating to the remote UE.

[0128] For example, coordinating PC5 QoS between the relay UE and the remote UE may be performed by the relay UE by one or more of the following:

[0129] - Modifying the current PC5 link configured with the remote UE so that a different PC5 QFI (PQI) is used (the PQI corresponds to the QFI (or 5QI) of the Uu link for which RQoS is used). The PQI used is based on the configuration information in the relay UE.

[0130] - Within the current PC5 link, use the existing PC5 flow with a PQI that corresponds to the QFI (or 5QI) that is applied to the Uu link as a result of RQoS.

[0131] -RQoS creates a new PC5 QoS flow with a PQI corresponding to the QFI (or 5QI) of the Uu link.

[0132] One embodiment of the present invention is described in further detail below.

[0133] Those skilled in the art will appreciate that the techniques disclosed herein may be used in any suitable combination.

[0134] 1. Adjusting PC5 QoS by using RQoS on Uu links

[0135] This solution assumes that a relay UE (i.e., a relay from the UE to the network) is configured with required information including a mapping between the QoS profile of the Uu link and the QoS profile of the PC5 link. The QoS profile information is in the form of a QFI or PFI of the link, where each QFI on Uu is associated with a 5QI, and each PFI on the PC5 link is associated with a PC5 5QI (PQI) accordingly. As an example, assume that the relay UE has the following configuration information regarding the QFI mapping between the QFI on Uu and the PFI on PC5:

[0136] [Table 4]

[0137] Assume that the relay UE is using QFI A1 when transmitting data over the UL on the Uu link, and the data is associated with a specific remote UE. As such, the matching PC5 QoS of the flow between the remote UE and the relay UE (i.e., PFI X1) has PQI X according to the above table.

[0138] The relay UE receives DL packets on Uu of the remote UE (the DL packets carry an RQI bit, i.e., indicating that RQoS should be used) and the QFI that should be applied in the UL direction. As an example, assume that the indicated QFI is B2, which is associated with 5QI B over Uu.

[0139] When this occurs, in addition to the derived QoS rules for the UL Uu, the relay UE optionally generates PC5 derived QoS rules, and the PC5 derived QoS rules correspond to the remote UE. To do so, the relay determines the PQI corresponding to the PC5 QI indicated on the DL Uu by the RQoS. The relay UE uses any configuration information to make such a determination. The relay UE locally associates the remote UE (or a PC5 QoS flow with the remote UE) with the derived PC5 QoS rules and / or the RQoS timers corresponding to the derived PC5 QoS rules. Such association is performed using an identifier for the remote UE, such as, but not limited to, the remote UE's destination tier 2 ID, PFI, ProSe service ID, application tier ID, IP address, or prefix, or any combination of such identifiers.

[0140] The relay UE must then modify the mapping between the associated PC5 QoS flow or Uu float PC5 QoS flow towards the remote UE, so that the PQI of the PQI link / flow matches the 5QI on Uu (and the QFI indicated on Uu). Returning to the example above, the relay UE modifies the mapping so that the PC5 QoS flow or PQIY with the remote UE is now set, and changes the matching to 5QI B for QFI B2, the latter now being used as part of the RQoS on the Uu link (in the UL direction).

[0141] To modify PC5 QoS flows with different QFIs on Uu, for example by using RQoS or by deriving QoS rules with RQoS, the relay UE has one or more of the following options described below:

[0142] Option 1: Modify the PFI for the current PC5 QoS flow with the remote UE

[0143] In this option, the relay UE modifies the PQI of the current PC5 QoS flow with the remote UE to match the Uu level 5 QI indicated by (or for) the RQoS, for example, after the relay UE generates the QoS rules derived by the RQoS.

[0144] The relay UE sends a PC5 message to the remote UE, in which the relay UE must identify the PC5 QoS flows whose PQIs must be updated (e.g., using PFI). The relay UE must also include the updated PQIs in the PC5 QoS flows used (where the PQIs match the PQI requirements on the Uu link, as indicated by RQoS). The relay UE also conveys other types of information via the PC5 message, such as the ProSe services to which such changes apply. The PC5 message sent to the remote UE is a PC5 signaling (PC5-S) message. The PC5 message may be a new type of message defined to change the characteristics of the PC5 QoS flows, or it may be the same as or similar to the direct link change request message used for V2X communication (see, e.g., [5]). If the Direct Link Modify Request message is reused, the relay UE may configure an action such as "Modify PC5 QoS parameters of existing PC5 QoS flows" as defined in [5], or a new action may be defined such as "Modify PC5 QoS parameters of existing PC5 QoS flows by RQoS". This new action is used when the relay UE needs to inform the remote UE that the change regarding PC5 level PQI is based on the Uu level 5 QI indicated by (or for) RQoS.

[0145] When a V2X message, such as a Direct Link Change Request message or other message in [5], is used for ProSe communication, the "V2X Service Identifier" field is set to a new value to indicate that the message is for a ProSe service. One embodiment of the present invention applies to any PC5-S message, for example in [5], and is not necessarily limited to messages for changing the direct link. Thereby, the relay UE also identifies the specific ProSe service for which the PC5 message is sent.

[0146] If the relay UE does not have any other existing PC5 QoS flows with PQIs matching the indicated Uu Level 5 QI based on RQoS, the relay UE operates as disclosed above (e.g., based on Option 1 above).

[0147] Option 2: Use existing PC5 QoS flows with PQIs that match Uu level 5 QIs via RQoS.

[0148] In this option, the relay UE checks whether there are other existing PC5 QoS flows whose PQIs match the Uu level 5 QI indicated based on RQoS, for example, after the relay UE generates the QoS rules derived by RQoS.

[0149] If such an existing PC5 QoS flow is available, in the above example, the PC5 QoS flow becomes the flow whose QoS profile has PQIY (matching 5QI B on Uu), and the relay UE modifies the packet filter of the PC5 QoS rule so that flow B2 packets on Uu are directed to PQIY2 on PC5. That is, the relay UE now uses that PC5 QoS flow (i.e., with PQIY in this example) to transmit DL data to the remote UE. The relay UE sends a PC5 message, e.g., a PC5-S message (optionally a Direct Link Change Request message (e.g., see [5])), to the remote UE to associate PC5 QoS flow Y2 with the ProSe service replacing flow X1 (if not already associated), and optionally (if necessary) to remove the ProSe service associated with X1. To do so, the relay UE includes the ProSe service identifier to be added to the identified QoS flow, i.e., Y2.

[0150] The relay UE also sends a PC5 message, e.g., a PC5-S message (optionally, the message is a direct link change request message (e.g., see [5])) to the remote UE to release the previous QoS flow used to exchange data before using RQoS on the Uu link, as long as the QoS flow (i.e., X1 in the above example) is not still in use for other related ProSe services. The relay UE then releases the QoS flow (i.e., X1 in the above example) on the PC5 link with the remote UE. Optionally, the relay UE changes the PC5 link so that the ProSe service that was in use on PC5 flow X1 is removed. In this way, PC5 QoS flow X1 is still maintained and can be reused in the future. In the future, in order to reuse the QoS flow, for example, after removing the QoS rules derived in PC5 and resetting the signaled QoS rules, the relay UE modifies the PC5 link (for example, by transmitting a related PC5 message to the remote UE) and further adds the ProSe service on the PC5 QoS flow X1, which means that both the relay UE and the remote UE resume the ProSe service (i.e., exchange data for the ProSe service) via the identified QoS flow on the PC5 link.

[0151] The relay UE may first modify the PC5 link as disclosed above and then release the other QoS flow (whose PQI is X, i.e., X1 in the above example), or may perform such actions simultaneously, or may release the QoS flow first and modify the rest as disclosed above, or may perform any combination of the above suggestions in any order. It is also possible for the relay UE to perform one or more of the above disclosed actions, i.e., send one message to modify the PC5 link and release the others.

[0152] Option 3: Create a new PC5 QoS flow with a PQI that matches the Uu level 5 QI using RQoS.

[0153] In this option, the relay UE creates or configures a new PC5 QoS flow on the PC5 link, so that the PQI of the new flow matches or corresponds to the PQI of the Uu link by RQoS, for example, after the relay UE creates a QoS rule derived by RQoS.

[0154] To do so, the relay UE must transmit a PC5 message to the remote UE, for example, it can be a PC5-S message, or optionally a Direct Link Setup Request message, or a Direct Link Modification Request message (see, for example, [5]). The relay UE includes the PQI for this QoS flow, where the PQI (in the above example, it is PQI Y whose PC5 QoS flow ID is Y2) corresponds to the 5QI of the Uu link according to RQoS (in the above example, it is 5QI B).

[0155] The relay UE indicates the ProSe service that must be used on the PC5 QoS flow via a PC5 message transmitted to the remote UE.

[0156] The relay UE also sends a PC5 message, e.g., a PC5-S message (optionally, this message is a direct link release request message (e.g., see [5])) to the remote UE to release the previous PC5 QoS flow (i.e., X1 in the above example) used to exchange data before the use of RQoS on the Uu link. In this way, the relay UE releases the PC5 QoS flow (i.e., X1 in the above example) (and, optionally, the packet filters in the signaled QoS rule) on the PC5 link that was used before the derivation of the QoS rule by RQoS. Optionally, the relay UE modifies the PC5 link / flow (i.e., X1) so that the ProSe service that was in use on it is now removed. In this way, the QoS flow is maintained and can be reused in the future. In the future, in order to reuse that QoS flow (i.e., X1 in the above example), for example, after removing the derived QoS rule and reusing the signaled QoS rule, the relay UE modifies the PC5 link (by transmitting the relevant PC5 message to the remote UE) and adds the same ProSe service onto the QoS flow, which means that both the relay UE and the remote UE resume the ProSe service (i.e., exchange data for the ProSe service) via the identified QoS flow (i.e., X1 in the above example) on the PC5 link.

[0157] The relay UE may first create a PC5 link as disclosed above and then release other (existing) QoS flows (those with PQI X, i.e., X1 in the above example), or perform such actions simultaneously, or release QoS flows first and create the rest as disclosed above, or perform any combination of the above techniques in any order. It is also possible for the relay UE to perform one or more of the above-disclosed operations, i.e., send one message to create a PC5 link and release the other.

[0158] FIG. 6 is a flowchart of message transmission and reception by a relay UE, a remote UE, and a radio access network (RAN) according to an embodiment of the present invention.

[0159] FIG. 6 summarizes the techniques disclosed above for the relay UE 62 and its operation as follows:

[0160] Referring to FIG. 6, in operation S610-A, relay UE 62 has a PC5 link and PC5 QoS flow with remote UE 60 with PQI of X (ie, PFI X1).

[0161] At operation S610-B, the relay UE 62 has a corresponding Uu level QoS flow with 5QI A (ie, QFI A1).

[0162] As such, the ProSe service is carried over the PC5 link with PQI X and 5QI A and the Uu link.

[0163] In operation S620, the relay UE 62 receives a DL packet for the ProSe service being used by the remote UE 60 from the RAN 64. The relay UE 62 receives the DL packet with an instruction to apply RQoS (the RQI bit is set) and a QFI used with the RQoS. In the above example, it is assumed that the QFI (or 5QI) is B1 (or 5QI B) (it should be noted that this is just an example).

[0164] In operation S630, the relay UE 62 generates PC5-derived QoS rules for RQoS, which are then associated with the remote UE 60. The relay UE 62 uses an identifier for the remote UE 60, such as, but not limited to, the destination Layer 2 ID, PFI, ProSe service ID, application Layer ID, IP address or prefix of the remote UE 60, or any combination of such identifiers, and locally associates the PC5-derived QoS rules with the remote UE 60.

[0165] In operation S640, relay UE 62 determines the PQI that must be used to match the Uu level 5 QI for which RQoS is used. Such determination utilizes local information (e.g., configuration information) that has a mapping between Uu level 5 QI and PC5 level PQI.

[0166] In operation S650, the relay UE 62 transmits a PC5 message to the remote UE 60, which enables the use of the determined PQI (for the PC5 QoS flow) so that the PC5 level PQI corresponds to (or matches) the Uu level 5 QI as described in operation S640. The PC5 message can be any one of the messages disclosed in the other options above. For example, the message can be a request to change the PQI of a PC5 QoS flow used for ProSe service.

[0167] In operation S660, the relay UE 62 transmits a PC5 message to the remote UE 60 to (optionally) suspend the use of the previous PQI for the ProSe service, in the form of either releasing the PC5 QoS flow with the previous PQI, or maintaining the PC5 QoS flow but removing the ProSe service for the previous PQI.

[0168] Those skilled in the art will appreciate that the operations disclosed above are merely examples of how the techniques disclosed herein may be used and should not be considered limiting.

[0169] Additionally, those skilled in the art will appreciate that examples of the present invention are not limited to the specific operations or the specific order of operations disclosed in the figures. As such, those skilled in the art will appreciate that the relay UE may perform other actions in different orders and in any combination other than the specific examples disclosed herein.

[0170] The relay UE continues to use the PC5 QoS flow with the determined PQI until it terminates the use of RQoS on the Uu link. The relay UE terminates the use of RQoS on the Uu link under different conditions, such as expiration of RQoS timer T3583 or after the derived QoS rule (for the remote UE) is deleted.

[0171] 2. Adjustment of PC5 QoS after use of RQoS on Uu link ends

[0172] The relay UE suspends the use of RQoS on the Uu link, where RQoS is associated with traffic exchanged on PC5 QoS flows with the remote UE. The relay UE suspends the use of RQoS, for example, when the RQoS timer expires.

[0173] When the use of RQoS is suspended, the relay UE resumes the use of the signaling QoS rule (and optionally, packet filters for the remote UE) on the Uu link for remote UE traffic. When this occurs, the relay UE again determines a PC5 level PQI that corresponds to (or matches) the QFI (or 5QI) of the signaling QoS rule, for example, based on configuration information. In the above example, the relay UE suspends the use of RQoS, which is 5QI B, and resumes the use of 5QI A (for the signaling QoS rule). The UE then determines to use PQI X as a match for 5QI A over the PC5 flow.

[0174] Having determined the PQI that should be used as disclosed above, the relay UE changes the PQI of the QoS flow in use at the remote UE to PQI X. As such, the relay UE operates as disclosed in one of the above options as long as the new PQI matches the PQI of the signaled QoS rule.

[0175] The relay UE uses one of the options disclosed above based on the previous action taken by the relay to adjust the PC5 QoS when RQoS was used. For example, if the relay UE changes the existing QoS flow on the PC5 link to use a different PQI, the relay UE must now again change the QoS flow on the PC5 link with the remote UE so that the PQI corresponds to the 5QI under RQoS. Specifically, the PQI must be the PQI corresponding to the 5QI under the signaling QoS rule due to the termination of RQoS. Another option is also achieved by the UE using an appropriate PQI according to the configuration information, where the PQI corresponds to the 5QI under the signaling QoS rule currently used after RQoS is discontinued.

[0176] 3. Trigger for deleting QoS rules derived in relay UE

[0177] The relay UE deletes the QoS flows on the PC5 link and / or the PC5-derived QoS for a particular remote UE (where relevant based on any one of the identifiers disclosed herein) when any one or more of the following occurs:

[0178] - the associated PC5 QoS flow is deleted (by the remote UE or intermediate UE); - the ProSe service performed via the associated PC5 QoS flow is removed (by the remote UE or intermediate UE); - The PC5 link between the remote UE and the relay UE is released; - Expiration of RQoS timer T3583 (for the remote UE) over the Uu link.

[0179] In the present invention, the term PFI is referred to as PQFI (PC5 QoS Flow Identifier), for example as defined in [5].

[0180] One embodiment of the present invention enables true e2e QoS for remote UEs using UE over network relay.

[0181] One embodiment allows the relay UE to optimize the QoS on the PC5 link to match the QoS of the Uu link, which changes when RQoS is applied (or ceases to be applied).

[0182] An embodiment of the present invention is applied to dynamic QoS processing without the assistance of a dynamic PCC.

[0183] In particular, one embodiment does not require any explicit arbitration from the SMF, which temporarily saves signaling between the SMF and relay UEs for frequent modification of relay PDU sessions over Uu (e.g., when Uu level 5QI changes dynamically to accommodate changes in AN level packet delay budget).

[0184] FIG. 7 is a diagram illustrating a problem with a given technique according to an embodiment of the present invention.

[0185] The following summarizes various techniques proposed by an embodiment of the present invention to solve certain problems associated with related techniques. Those skilled in the art will recognize that the present invention is not limited to the following examples.

[0186] 1. Referring to Figure 7, a remote UE (outside the coverage of the network) uses a UE-to-network repeater (within the coverage of the network) to access and use a PDU session.

[0187] (a) The link between the remote UE and the relay UE is a PC5 link. The link between the relay and the network from the UE to the network is a Uu interface.

[0188] (b) When providing services to a remote UE, it is desirable to ensure that the QoS of the session is supported end-to-end, i.e., the QoS of the PC5 link (referred to as PQI) must correspond to the QoS of the Uu link (referred to as 5QI (or QFI)).

[0189] 2. The QoS rule is either a signaled QoS rule or a derived QoS rule. If the reflected QoS (RQoS) is used in the network, the derived QoS rule is used.

[0190] (a) RQoS allows the network and UE to apply different QoS handling (ie, using different QFIs) "on the fly," i.e., without being signaled via the NAS protocol.

[0191] (b) For example, the network decides to change the QFI of the downlink flow from QFI A to QFI B, and further indicates that the UE should also use QFI B in the uplink direction.

[0192] i. To apply RQoS, the network transmits a downlink packet and sets the RQI bit to indicate that RQoS should be used by the UE. The network also indicates the QFI to be used (e.g., QFI B).

[0193] ii. The lower layer of the UE provides the RQoS indicator to the NAS along with the QFI (e.g., QFI B) of the downlink packet.

[0194] iii. The UE (NAS) derives QoS rules so that uplink packets are processed via the QFI indicated by the lower layer (e.g., QFI B).

[0195] 3. RQoS leads to the generation of derived QoS rules in the UE. The derived rules are used for a period defined by the RQoS timer. When the timer expires, the UE deletes the derived rules and uses the existing signaling QoS rules. To understand the problem, let us assume the following initial situation:

[0196] The UE to Network Relay 72 has a PDU session with the network and uses a QoS of "QFI A" to exchange data regarding the network 74 and the remote UE 70 (see operation S710-1A in Figure 7).

[0197] - The remote UE 70 has a PC5 link with a repeater 72 from the UE to the network, with a QoS of "PQI X" (see operation S710-1B in Figure 7).

[0198] -End-to-end QoS<PC5 link QoS><Uu interface QoS> =<PQI X><QFI A> (See operations S710-1A and S710-1B in FIG. 7).

[0199] The above assumptions mean that on the Uu link (between the UE to network repeater 72 and the network 74) packets are using QoS with QFI A.

[0200] Correspondingly, the PC5 link (between the remote UE 70 and the UE to network repeater 72) uses PQI X because it is the option that best corresponds to QFI A.

[0201] Therefore, end-to-end QoS is<PQI X><QFI A> is obtained by

[0202] Problem: During a PDU session of the relay 72 from the UE to the network, the network 74 decides to use RQoS for downlink packets (see operation S720 in FIG. 7). For example, the network 74 decides to apply RQoS to downlink packets, and thereby decides to apply QFI B instead of the existing QFI A (see operation S730-A in FIG. 7). When this happens, the end-to-end QoS is<PQI X><QFI B> (See operations S730-A and S730-B in FIG. 7).

[0203] The problem is,<PQI X> but<QFI A> corresponds to, but this time<QFI B> What should the corresponding PQI, i.e., end-to-end QoS, be?<PQIであるか><QFI Bであるか> That is what it means.

[0204] In summary, if the UE-to-network repeater 72 does not change the PQI when RQoS is used on the Uu link so that the QFI is changed, true end-to-end QoS is not possible. New operations are required for the UE-to-network repeater 72 to determine and implement end-to-end QoS starting from RQoS.

[0205] An embodiment of the present invention uses one or more of the following operations to solve the above-mentioned problems.

[0206] 1) When the UE-to-network repeater 72 receives a DL packet with a reflected QoS indicator (RQI), the UE-to-network repeater 72 derives / updates the QoS rules of the remote UE 70 associated with the UL direction.

[0207] 2) If there is a PC5 whose PC5 QoS corresponds to the new QFI (from RQoS) based on the new QFI on Uu by RQoS, the UE-to-network relay 72 performs an L2 link change procedure to move DL traffic on the PC5 QoS flow with a PQI that matches the new QFI.

[0208] 3) PC5 Based on New QFI on Uu with RQoS If there is no PC5 QoS (from RQoS) corresponding to the new QFI, the UE-to-network relay 72 determines a new PQI based on the new QFI.

[0209] 4) Once a new PQI is determined for the new QFI, the UE-to-network relay 72 uses the L2 link modification procedure to set up a new PC5 QoS flow with the determined PQI.

[0210] 5) When the derived QoS rule is deleted, for example, after the RQoS timer expires, the UE-to-network repeater 72 uses the signaling QoS rule for the Uu link, and the UE-to-network repeater 72 performs the L2 link change procedure again so that the QoS for the PC5 QoS flow now matches the QFI of the signaling QoS rule.

[0211] The above-mentioned operation 1 corresponds to operation S630 in Figure 6. The above-mentioned operation 3 corresponds to operation S640 in Figure 6. The above-mentioned operation 2 corresponds to operation S650 in Figure 6. The above-mentioned operation 4 also corresponds to operation S650 in Figure 6. The above-mentioned operation 5 corresponds to an operation similar to operation S650 in Figure 6. In one example of the present invention, the procedure corresponding to the above-mentioned operation 4 is also used in the situation of the above-mentioned operation 5.

[0212] Referring to Figure 4, as defined in clause 5.6.5.3 of TS 23.501, reflected QoS control over Uu is used for dynamic QoS handling of a remote UE 70 to save signaling between the SMF and the 5G ProSe Layer 3 UE-to-network repeater. Upon receiving a DL packet with an RQI over Uu for the remote UE 70, based on the indicated QFI, the 5G ProSe UE-to-network repeater 72 generates a derived QoS rule or updates an existing derived QoS rule corresponding to the remote UE 70, as defined in TS 23.501. The derived QoS rule is for an UL packet from the remote UE 70 on the Uu interface.

[0213] Based on the signaled QoS rules (via SMF) or derived QoS rules (uplink Uu via reflected QoS), the 5G ProSe UE to network relay 72 updates existing PC5 QoS flows or sets up new PC5 QoS flows (if no QFI to PC5 QoS flow mapping exists) using the L2 link modification procedure as defined in clause 6.4.3.4 of TS 23.304 (V1.0.0).

[0214] For example, when the 5G ProSe UE-to-network repeater deletes the derived QoS rule after the RQ timer expires, the 5G ProSe UE-to-network repeater performs the L2 link change procedure as defined in clause 6.4.3.4 of TS 23.304 (V1.0.0), thereby utilizing the PQI mapped from the PQI of the currently used QoS rule after the deletion of the derived QoS rule.

[0215] In one embodiment of the present invention, a method performed by a relay node (e.g., a relay UE) for supporting end-to-end (e23) Quality of Service (QoS) for uplink (UL) communication between a user equipment (UE) (e.g., a remote UE) and a network (e.g., a 5GC) via the relay node includes receiving a downlink (DL) packet for the UE from the network (e.g., from a RAN); and generating or updating a QoS rule (e.g., a derived QoS rule), wherein the DL packet includes a value of a first indicator (e.g., QFI) for a QoS flow on a first link (e.g., Uu) between the relay node and the network, and the derived QoS rule is derived based on the value of the first indicator, and optionally the generated or updated QoS rule corresponds to the UE or applies to a QoS flow on a second link (e.g., a first PC5 link) with the UE.

[0216] In one embodiment, the method further comprises determining a value of a second indicator (e.g., PFI) of a QoS flow on a link with the UE, wherein the determined value of the second indicator corresponds to the value of the received first indicator (e.g., to satisfy a predetermined e2e QoS requirement).

[0217] In one embodiment, the method further includes, if a QoS flow exists on a third link (e.g., a second PC5 link) with the UE, whose QoS corresponds to the determined second indicator value, performing a procedure (e.g., an L2 link change procedure) to move DL traffic on the second link to the existing QoS flow.

[0218] In one embodiment, the method further includes a step of performing a procedure (e.g., an L2 link change procedure) to create a new QoS flow having the determined second indicator value on a third link (e.g., a PC5 link) with the UE for DL ​​traffic if there is no QoS flow whose QoS corresponds to the determined second indicator value.

[0219] In one embodiment, performing the procedure includes transmitting a message to the UE that includes the determined second indicator value.

[0220] In one embodiment, performing the procedure includes instructing the UE on services (e.g., ProSe services) associated with the second link and / or the third link (e.g., services associated with the second link before the procedure and services associated with the third link after the procedure when the services move from the second link to the third link).

[0221] In one embodiment, the value of the second indicator is determined based on a predetermined mapping between the values ​​of the first indicator and the values ​​of the second indicator.

[0222] In one embodiment, the packet includes a third indicator (e.g., RQI) having a value indicating that the QoS treatment for the UL should reflect the QoS treatment for the DL (e.g., the reflected QoS should be used).

[0223] In one embodiment, the UE and the relay node support proximity services (ProSe).

[0224] In one embodiment, the QoS rule is a derived QoS rule corresponding to the UE for UL packets.

[0225] In one embodiment, the method further comprises deleting the QoS rule.

[0226] In one embodiment, the method further includes starting a timer (e.g., timer T3583) when a QoS rule is created or updated, and the QoS rule is deleted when the timer expires.

[0227] In one embodiment, the method further includes applying the signaled QoS rule to the first link if the QoS rule is deleted, and determining a second value of a second indicator (e.g., PFI) of the QoS flow on the link to the UE, wherein the determined second value of the second indicator corresponds to the value of the first indicator associated with the signaled QoS rule.

[0228] In one embodiment, the method further includes a step of performing a procedure (e.g., an L2 link change procedure) to move DL traffic on the second link to an existing QoS flow on a fourth link (e.g., a third PC5 link) with the UE, the QoS of which corresponds to the second value of the determined second indicator.

[0229] In one embodiment, the method further includes a step of performing a procedure (e.g., an L2 link change procedure) to create a new QoS flow for DL ​​traffic having the second value of the determined second indicator on a fourth link with the UE.

[0230] In one embodiment, performing the procedure includes instructing the UE on a service (e.g., a ProSe service) associated with at least one of the second link or the fourth link (e.g., a service associated with the second link before the procedure and associated with the fourth link after the procedure when the service moves from the second link to the fourth link).

[0231] An embodiment of the present invention provides a relay node configured to operate according to any aspect, example, embodiment, and / or claimed method disclosed herein.

[0232] An embodiment of the present invention provides a network (or wireless communication system) including a relay node and a UE according to the above examples.

[0233] An embodiment of the present invention provides a computer program product comprising instructions that, when executed by a computer or processor, cause the computer or processor to perform any aspect, example, embodiment, and / or claimed method disclosed herein.

[0234] An embodiment of the present invention provides a computer or processor readable data carrier storing a computer program according to the above examples.

[0235] FIG. 8 is a schematic diagram of a network entity according to an embodiment of the present invention.

[0236] Referring to Figure 8, a block diagram of a network entity used in the examples of the present invention is shown. Those skilled in the art will appreciate that the network entities shown in Figure 8 may be embodied as, for example, network elements on dedicated hardware, software instances running on dedicated hardware, or virtualized functions implemented on a suitable platform such as a cloud infrastructure.

[0237] Entity 800 includes a processor (or controller) 801, a transmitter 803, and a receiver 805. Receiver 805 is configured to receive one or more messages or signals from one or more other network entities. Transmitter 803 is configured to transmit one or more messages or signals to one or more other network entities. Processor 801 is configured to perform one or more operations and / or functions as described above.

[0238] FIG. 9 is a diagram illustrating a base station (BS) according to one embodiment of the present invention.

[0239] Referring to Figure 9, a base station 900 includes a processor 910, a transceiver 920, and a memory 930. However, not all of the components shown are required. The base station 900 may be implemented with more or fewer components than those shown in Figure 9. In addition, the processor 910, the transceiver 920, and the memory 930 may be implemented on a single chip in other embodiments.

[0240] The above mentioned components are described in detail below.

[0241] The processor 910 includes one or more processors or other processing devices that control the functions, processes, and / or methods described herein. The operations of the base station 900 are implemented by the processor 910.

[0242] The transceiver 920 includes an RF transmitter for upconverting and amplifying signals to be transmitted, and an RF receiver for downconverting the frequency of received signals.

[0243] However, according to other embodiments, the transceiver 920 is implemented with more or fewer components than those shown.

[0244] The transceiver 920 is coupled to the processor 910 to transmit and / or receive signals.

[0245] The signal contains control information and data.

[0246] The transceiver 920 also receives signals over a wireless channel and outputs the signals to the processor 910 .

[0247] The transceiver 920 transmits the signals output from the processor 910 over a wireless channel.

[0248] The memory 930 stores control information and data included in signals received by the base station 900. The memory 930 is coupled to the processor 910 to store at least one instruction, protocol, or parameter related to the proposed functions, processes, and / or methods. The memory 930 may include a read-only memory (ROM), a random access memory (RAM), a hard disk, a compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), and / or other storage devices.

[0249] In one embodiment, the processor 910 is configured to generate an indication regarding a set of power control parameters for a channel for transmitting data with the first priority and transmit the indication to a user equipment (UE).

[0250] FIG. 10 is a diagram illustrating a user equipment (UE) according to an embodiment of the present invention.

[0251] The UE 1000 may be a remote UE 60, a relay UE 62, a remote UE 70, or a UE-to-network relay 72.

[0252] Referring to Figure 10, UE 1000 includes a processor 1010, a transceiver 1020, and a memory 1030. However, not all of the components shown are required. UE 1000 may be implemented with more or fewer components than those shown in Figure 10. In addition, processor 1010, transceiver 1020, and memory 1030 may be implemented on a single chip in other embodiments.

[0253] The above mentioned components are described in detail below.

[0254] The processor 1010 may include one or more processors or other processing devices that control the functions, processes, and / or methods described herein. The operations of the UE 1000 are implemented by the processor 1010.

[0255] The transceiver 1020 includes an RF transmitter for upconverting and amplifying signals to be transmitted, and an RF receiver for downconverting the frequency of received signals, although in other embodiments the transceiver 1020 may be implemented with more or fewer components than those shown.

[0256] The transceiver 1020 is coupled to the processor 1010 to transmit and / or receive signals. The signals include control information and data. The transceiver 1020 also receives signals via a wireless channel and outputs the signals to the processor 1010. The transceiver 1020 transmits the signals output from the processor 1010 via a wireless channel.

[0257] Memory 1030 stores control information and data contained in signals obtained by UE 1000 .

[0258] The memory 1030 is coupled to the processor 1010 and stores at least one instruction, protocol, or parameter related to the proposed functions, processes, and / or methods. The memory 1030 may include a ROM and / or RAM and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage device.

[0259] The techniques described herein may be implemented using any suitably configured apparatus and / or system. Such an apparatus and / or system may be configured to perform a method according to any aspect, embodiment, example, or claim disclosed herein. Such an apparatus may include one or more components, such as a receiver, transmitter, transceiver, processor, controller, module, unit, etc., each configured to perform one or more corresponding process, operation, and / or method actions to implement the techniques described herein. For example, an operation / function of X is performed by a module configured to perform X (or an X module). One or more components may be embodied in hardware, software, or a combination of hardware and software.

[0260] It will be appreciated that embodiments of the present invention may be embodied in the form of hardware, software, or a combination of hardware and software, such software being stored in the form of non-volatile or volatile storage such as ROM, whether erasable or rewritable, or in the form of memory such as RAM, memory chips, devices or integrated circuits, or on optically or magnetically readable recording media such as CDs, DVDs, magnetic disks or magnetic tapes.

[0261] It will be appreciated that the storage device and recording medium are embodiments relating to a device-readable storage unit suitable for storing a program including instructions that, when executed, embody embodiments of the present invention. Accordingly, embodiments provide a program including code for embodying a method, device, or system according to any example, embodiment, aspect, and / or claim disclosed herein, and / or a device-readable storage unit storing such a program. Furthermore, such a program may be transmitted electronically via any medium, for example, a communication signal transmitted via a wired or wireless connection.

[0262] Although the present invention has been shown and described with reference to one embodiment, those skilled in the art will recognize that various changes in form and detail may be made therein without departing from the scope of the invention as defined in the claims.

[0263] Those skilled in the art will understand that computer program instructions are used to implement each block of the structural diagrams and / or block diagrams and / or flowcharts, and combinations of blocks in the structural diagrams and / or block diagrams and / or flowcharts. Those skilled in the art will understand that when such computer program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing means for implementation, the solutions shown in the blocks of the structural diagrams and / or block diagrams and / or flowcharts are performed by the processor of the computer or other programmable data processing means.

[0264] Those skilled in the art will recognize that the operations, methods, acts in flowcharts, measurements, and solutions discussed herein may be replaced, modified, combined, or deleted. Other operations, measurements, and solutions already discussed herein may also be replaced, modified, rearranged, decomposed, combined, or deleted. Prior art having operations, methods, acts in flowcharts, measurements, and solutions discussed herein may also be replaced, modified, rearranged, decomposed, combined, or deleted.

[0265] The above are some of the embodiments of the present invention, and it should also be known to those skilled in the art that various improvements and modifications can be made without departing from the principle of the present application, which will be regarded as the protection scope of the present invention.

[0266] Methods according to embodiments of the present invention as claimed and described herein may be embodied in hardware, software, or a combination of hardware and software.

[0267] When embodied as software, a non-transitory computer-readable recording medium storing one or more programs (software modules) is provided. The one or more programs stored in the non-transitory computer-readable recording medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to perform the method described in the claims and specification of the present invention according to an embodiment of the present invention.

[0268] One or more programs (software modules, software, etc.) may be stored in RAM, non-volatile memory including flash memory, ROM, electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, CD-ROM, DVD, or other form of optical storage device, magnetic cassette, or any combination of such devices. Alternatively, one or more programs may be stored in memory provided through any combination of such devices, in whole or in part. Each memory may also be comprised of multiple configuration memories.

[0269] The one or more programs may be stored in an attachable storage device accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wireless local area network (WLAN), or a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device that performs an embodiment of the present invention via an external port. Alternatively, a separate storage device on the communication network may be connected to a device that performs an embodiment of the present invention.

[0270] According to various embodiments of the present invention, methods are provided for efficiently transmitting and receiving reference signals in a wireless communication system.

[0271] The technical problems to be solved by the present invention are not limited to those described above, and other technical problems not described herein will be clearly understood by those skilled in the art from the present disclosure.

[0272] In certain embodiments of the present invention, elements included in the present invention are expressed in the singular or plural form according to the specific embodiment of the present invention proposed. However, the singular or plural form is appropriately selected according to the context presented for convenience of description and is not intended to limit the present invention to singular or plural elements. Even when a certain element is expressed in the plural form, it may be provided as one element, and even when a certain element is expressed in the singular form, it may be provided as multiple elements.

[0273] While the present invention has been shown and described with reference to various embodiments, those skilled in the art will recognize that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined in the appended claims and equivalents thereof. [Explanation of symbols]

[0274] 60, 70 Remote UE 62 Relay UE 64 RAN 72 UE to network repeater 74 Network / RAN 800 entities 801, 910, and 1010 processors 803 Transmitter 805 receiver 900 base stations 920, 1020 transmitter and receiver 930, 1030 memory 1000

Claims

1. A method for performing QoS (Quality of Service) control by a relay user equipment (UE), comprising: receiving a downlink (DL) packet having a reflective QoS indication (RQI) and a QoS flow identifier (QFI) for a remote UE over a Uu interface between a radio access network (RAN) and the relay UE; generating a derived QoS rule based on reception of the DL packet having the RQI; generating derived PC5 QoS rules for the remote UE based on the derived QoS rules; determining a PQI (PC5 5G QoS identifier) ​​based on the derived 5QI (5G QoS identifier) ​​according to the PC5 QoS rules; and transmitting a link change request message to the remote UE based on the determined PQI.

2. The method further includes a step of checking whether a PC5 QoS flow having the determined PQI exists; The method of claim 1 , wherein if a PC5 QoS flow having the determined PQI exists, the PC5 QoS flow is modified based on the link modification request message.

3. The method of claim 2, wherein if there is no PC5 QoS flow with the determined PQI, a new PC5 QoS flow is established based on the link change request message.

4. 2. The method of claim 1, further comprising: if the derived QoS rule is deleted after expiration of a reflective QoS (RQoS) timer, sending a link modification request message to the remote UE, the link modification request message including a new PQI mapped to a new PQI of the configured QoS rule.

5. The method of claim 1, wherein the derived QoS rules are generated using the received QFI.

6. A method for performing Quality of Service (QoS) control by a remote User Equipment (UE), comprising: generating a derived PC5 QoS rule for the remote UE based on a derived QoS rule in a relay UE, and determining a PQI (PC5 5G QoS identifier) ​​based on a 5QI (5G QoS identifier) ​​according to the derived PC5 QoS rule; receiving a link change request message from the relay UE based on the determined PQI; transmitting uplink packets based on the derived PC5 QoS rules; and when a downlink (DL) packet having a reflective QoS indication (RQI) and a QoS flow identifier (QFI) for the remote UE is received on a UE interface between a radio access network (RAN) and the relay UE, the derived QoS rule is generated based on reception of the DL packet having the RQI at the relay UE.

7. If a PC5 QoS flow having the determined PQI exists, the PC5 QoS flow is modified based on the link modification request message; The method of claim 6, wherein if there is no PC5 QoS flow with the determined PQI, a new PC5 QoS flow is established based on the link change request message.

8. 7. The method of claim 6, further comprising receiving a link change request message from the relay UE, the link change request message including a new PQI that is mapped to a new PQI of the configured QoS rule if the derived QoS rule is deleted after expiration of a reflective QoS (RQoS) timer.

9. A relay user equipment (UE) that performs a quality of service (QoS) control method, A transmitter / receiver, at least one processor coupled to the transceiver; The at least one processor receiving a downlink (DL) packet having a reflective QoS indication (RQI) and a QoS flow identifier (QFI) for a remote UE on a Uu interface between a radio access network (RAN) and the relay UE; generating a derived QoS rule based on reception of the DL packet having the RQI; generating derived PC5 QoS rules for the remote UE based on the derived QoS rules; Determine a PQI (PC5 5G QoS identifier) ​​based on the derived 5QI (5G QoS identifier) ​​according to the PC5 QoS rules; The relay UE is configured to send a link change request message to the remote UE based on the determined PQI.

10. The at least one processor: further configured to check whether a PC5 QoS flow having the determined PQI exists; The relay UE of claim 9, wherein if a PC5 QoS flow having the determined PQI exists, the PC5 QoS flow is modified based on the link modification request message.

11. The relay UE of claim 10, wherein if a PC5 QoS flow having the determined PQI does not exist, a new PC5 QoS flow is established based on the link modification request message.

12. The at least one processor 10. The relay UE of claim 9, further configured to: if the derived QoS rule is deleted after expiration of a reflective QoS (RQoS) timer, send to the remote UE a link modification request message including a new PQI mapped to a new PQI of the configured QoS rule.

13. A remote UE (User Equipment) that performs a Quality of Service (QoS) control method, A transmitter / receiver, at least one processor coupled to the transceiver; The at least one processor A derived PC5 QoS rule for the remote UE is generated based on the derived QoS rule in the relay UE, and a PQI (PC5 5G QoS identifier) ​​is determined based on a 5QI (5G QoS identifier) ​​according to the derived PC5 QoS rule. If a PQI (PC5 5G QoS identifier) ​​is determined, a link change request message is received from the relay UE based on the determined PQI; configured to transmit uplink packets based on the derived PC5 QoS rules; When a downlink (DL) packet having a reflective QoS indication (RQI) and a QoS flow identifier (QFI) for the remote UE is received on a Uu interface between a radio access network (RAN) and the relay UE, the derived QoS rule is generated based on reception of the DL packet having the RQI at the relay UE.

14. If a PC5 QoS flow having the determined PQI exists, the PC5 QoS flow is modified based on the link modification request message; The remote UE of claim 13, wherein if a PC5 QoS flow having the determined PQI does not exist, a new PC5 QoS flow is established based on the link modification request message.

15. The at least one processor 14. The remote UE of claim 13, further configured to receive, from the relay UE, a link modification request message including a new PQI that is mapped to a new PQI of the configured QoS rule if the derived QoS rule is deleted after expiration of a reflective QoS (RQoS) timer.

Citation Information

Patent Citations

  • Methods and devices to determine the quality of service mechanisms for vehicle-to-everything mobile device communications

    WO2019161269A1