Power saving of user equipment for V2X communication

Abstract

An apparatus, method, and system for user equipment power saving for V2X communications are disclosed. The apparatus (400) includes a processor (405) that determines one or more destination Layer 2 IDs for reception in vehicle-to-everything (V2X) configuration information received from a network, determines one or more quality of service ("QoS") requirements for reception for each determined destination Layer 2 ID, and provides the determined one or more QoS requirements for reception for each determined destination Layer 2 ID to an application service ("AS") layer.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 161,300, entitled “METHOD FOR SUPPORTING POWER SAVING FOR V2X COMMUNICATIONS OVER GROUPCAST ​​AND BROADCAST FOR RECEIVING UES,” filed on March 15, 2021 to Dimitrios Karampatsis, which is incorporated herein by reference.

[0002] The subject matter disclosed herein relates generally to wireless communications, and more particularly, to power saving in user equipment for V2X communications. [Background technology]

[0003] In wireless networks, for broadcast and groupcast communications, the receiving user equipment (UE) does not know the PC5 quality of service (QoS) parameters for reception and therefore cannot determine which PC5 discontinuous reception (DRX) to apply for reception. Summary of the Invention [Means for solving the problem]

[0004] Procedures are disclosed for supporting power saving for V2X communications via groupcast and broadcast for a receiving UE.

[0005] In one embodiment, a first apparatus comprises a processor, the processor determines one or more destination Layer 2 IDs for reception in vehicle-to-everything (V2X) configuration information received from a network, determines one or more quality of service ("QoS") requirements for reception for each determined one or more destination Layer 2 IDs, and provides to an application service ("AS") layer the determined one or more QoS requirements for reception for each determined one or more destination Layer 2 IDs.

[0006] In one embodiment, a first method includes determining one or more destination Layer-2 IDs for reception in vehicle-to-everything (V2X) configuration information received from a network, determining one or more quality of service ("QoS") requirements for reception for each determined destination Layer-2 ID, and providing to an application service ("AS") layer the determined one or more QoS requirements for reception for each determined destination Layer-2 ID.

[0007] In one embodiment, the second device includes a processor that receives one or more quality of service ("QoS") requirements for one or more destination Layer 2 IDs for receiving one of a groupcast transmission and a broadcast transmission from a vehicle-to-everything (V2X) layer, and determines information about an applied PC5 discontinuous reception (DRX) based on the QoS requirements.

[0008] In one embodiment, the second method includes receiving one or more quality of service ("QoS") requirements for one or more destination Layer 2 IDs for receiving one of a groupcast transmission and a broadcast transmission from a vehicle-to-everything (V2X) layer, and determining information about applied PC5 discontinuous reception (DRX) based on the QoS requirements.

[0009] A more particular description of the embodiments briefly described above will be given by reference to specific embodiments that are illustrated in the accompanying drawings, in which the embodiments will be described and explained with additional specificity and detail, with the understanding that these drawings illustrate only some embodiments and therefore should not be considered limiting in scope. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for user equipment power saving for V2X communications. [Diagram 2] A diagram showing a procedure for QoS aware power efficient PC5 communication for pedestrian UE. [Figure 3A] A diagram showing a procedure for deriving a PC5 DRX configuration for each PC5 QoS flow. [Figure 3B] This is a continuation of Figure 3A. [Figure 4] FIG. 1 is a block diagram illustrating an embodiment of a user equipment device that may be used for user equipment power saving for V2X communications. [Diagram 5] FIG. 1 is a block diagram illustrating an embodiment of a network device that may be used for user equipment power saving for V2X communications. [Figure 6] 1 is a flow chart illustrating an embodiment of a method for user equipment power saving for V2X communications. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.) or an embodiment combining software and hardware aspects.

[0012] For example, the disclosed embodiments may be implemented as hardware circuitry comprising custom very large scale integrated ("VLSI") circuits or off-the-shelf semiconductors such as gate arrays, logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may be organized as, for example, objects, procedures, or functions.

[0013] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and / or non-transmittal. The storage devices may not embody signals. In some embodiments, the storage devices use only signals to access the code.

[0014] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device that stores the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0015] More specific examples of storage devices (a non-exhaustive list) include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disk read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this specification, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0016] The code for carrying out the operations of the embodiments may be any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or in machine language, such as assembly language. The code may run entirely on the user's computer, partly on the user's computer, as a standalone software package, partly on the user's computer and partly on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN"), wireless LAN ("WLAN"), or wide area network ("WAN"), and connections may be made to external computers (e.g., via the Internet using an Internet Service Provider ("ISP").

[0017] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, one skilled in the art will recognize that the embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0018] Reference throughout this specification to "one embodiment," "an embodiment," or similar words means that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Thus, appearances throughout this specification of the phrases "in one embodiment," "in an embodiment," and similar words mean "one or more but not all embodiments," although they may, but do not necessarily, all refer to the same embodiment, unless expressly specified otherwise. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise. A list of enumerated items does not imply that some or all of the items are mutually exclusive, unless expressly specified otherwise. The terms "a," "an," and "the" also mean "one or more," unless expressly specified otherwise.

[0019] As used herein, a list with the conjunction "and / or" includes any single item in the list or combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one or more of" includes any single item in the list or combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one of" includes only one of any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C" includes only one of A, B, or C, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C, and combinations thereof" includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C.

[0020] Aspects of the embodiments are described below with reference to schematic flowchart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowchart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flowchart illustrations and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to generate a machine such that the instructions, executed via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart illustrations and / or block diagrams.

[0021] Code may also be stored in a storage device that can cause a computer, other programmable data processing device, or other device to function in a particular way, such that the instructions stored in the storage device produce an article of manufacture that includes instructions that implement the functions / acts specified in the flowchart illustrations and / or block diagrams.

[0022] The code may also be loaded into a computer, other programmable data processing apparatus, or other device to generate a computer-implemented process such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / acts specified in the flowchart illustrations and / or block diagrams, such that a series of operational steps are executed on the computer, other programmable apparatus, or other device.

[0023] The call flow diagrams, flowchart diagrams, and / or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and / or block diagrams may represent a module, segment, or portion of code that includes one or more executable instructions of code for implementing the specified logical function(s).

[0024] It should also be noted that in some alternative embodiments, the functions noted in the blocks may differ from the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks of the illustrated figures, or portions thereof.

[0025] It should be understood that various arrow types and line types may be used in the call flows, flowcharts and / or block diagrams, but they are not intended to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the illustrated embodiment. For example, the arrows may indicate waiting or monitoring periods of unspecified duration between the recited steps of the depicted embodiment. It should also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by a dedicated hardware-based system that performs the specified functions or acts, or a combination of dedicated hardware and code.

[0026] The description of an element in each drawing may refer to the element in the previous drawing. Like numbers refer to like elements in all drawings, including alternative embodiments of like elements.

[0027] In general, the present disclosure describes systems, methods, and apparatuses that support power saving for vehicle-to-everything (V2X) communications via groupcast and / or broadcast for a receiving UE. In certain embodiments, the methods may be performed using computer code embedded in a computer-readable medium. In certain embodiments, the apparatus or system may include a computer-readable medium including computer-readable code that, when executed by a processor, causes the apparatus or system to perform at least a portion of the solutions described below.

[0028] The 3rd Generation Partnership Project ("3GPP") is considering extensions in Release 17 to support sidelink communications over PC5 (e.g., a reference point where a UE communicates directly with another UE over a direct channel) for pedestrian-enabled sidelink communications with power saving, e.g., in accordance with vehicular service requirements defined in TS 22.185 and TS 22.186.

[0029] In conventional solutions, V2X UEs transmit messages for sidelink communication over PC5 at a constant rate. For example, a Cooperative Awareness Message (CAM) is transmitted over PC5 every 100 ms. Such constant operation reduces the power efficiency of the UE. However, V2X UEs (e.g., cars or road side units (RSUs)) have a battery capacity that allows such constant operation. On the other hand, pedestrian UEs (e.g., smartphones, smartwatches) have limited battery capacity or available radio resources, and thus new mechanisms are needed to ensure power-efficient operation over PC5. One of the main issues agreed in Release 17 V2X TR 23.776 is to consider how to support the DRX mechanism defined over Uu for communication over PC5.

[0030] It has been agreed that for the transmitting UE, the Application Service (AS) layer in the UE will decide the PC5 DRX based on the QoS requirements provided by the V2X layer. The agreed procedure is as follows: · The V2X application requests to transmit V2X messages and provides QoS requirements to the V2X layer in the UE; The V2X layer of the UE determines PC5 QoS parameters and decides to establish a PC5 QoS flow; · The V2X layer provides PC5 QoS flows and PC5 QoS parameters to the AS layer; · The AS layer decides PC5 DRX based on PC5 QoS parameters.

[0031] One problem is that for broadcast and groupcast communications, the receiving UE does not know the PC5 QoS parameters for reception, and therefore cannot determine which PC5 DRX to apply for reception.

[0032] In one embodiment, the present disclosure solves the problem of how a V2X pedestrian UE determines which DRX over PC5 to apply for receiving broadcast and / or groupcast V2X messages.

[0033] In one embodiment, the V2X layer of the UE determines the V2X service type for reception by checking the V2X configuration information. It is additionally proposed that the V2X layer of the UE determines the QoS requirement for each of the determined V2X service types by checking the V2X configuration information. The UE then provides this information to the AS layer of the UE. The AS layer determines the PC5 DRX for reception for each V2X service type based on the QoS requirement.

[0034] FIG. 1 illustrates a wireless communication system 100 supporting user equipment power saving for V2X communications according to an embodiment of the disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network ("RAN") 120, and a mobile core network 130. The RAN 120 and the mobile core network 130 form a mobile communication network. The RAN 120 may be comprised of a base unit 121 with which the remote unit 105 communicates using a wireless communication link 115. Although a specific number of remote units 105, base units 121, wireless communication links 115, RAN 120, and mobile core network 130 are illustrated in FIG. 1, one skilled in the art will recognize that any number of remote units 105, base units 121, wireless communication links 115, RAN 120, and mobile core network 130 may be included in the wireless communication system 100.

[0035] In one implementation, the RAN 120 is compliant with a fifth generation ("5G") cellular system specified in the 3rd Generation Partnership Project ("3GPP") specifications. For example, the RAN 120 may be a Next Generation Radio Access Network ("NG-RAN") implementing a NR RAT and / or a 3GPP Long Term Evolution ("LTE") RAT. In another example, the RAN 120 may include a non-3GPP RAT (e.g., Wi-Fi or an Institute of Electrical and Electronics Engineers ("IEEE") 802.11 family compliant WLAN). In another implementation, the RAN 120 is compliant with an LTE system specified in the 3GPP specifications. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication network, such as Worldwide Interoperability for Microwave Access (WiMAX) or the IEEE 802.16 family of standards, among other networks. This disclosure is not intended to be limited to any particular wireless communications system architecture or protocol implementation.

[0036] In one embodiment, the remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smartphones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, gaming consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, the remote unit 105 includes wearable devices such as smart watches, fitness bands, optical head mounted displays, etc. Additionally, the remote unit 105 may be referred to as a UE, subscriber unit, mobile, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit ("WTRU"), device, or other terminology used in the art. In various embodiments, the remote unit 105 includes a subscriber identification and / or identification module ("SIM") and a mobile equipment ("ME") that provides mobile terminal functions (e.g., wireless transmission, handover, voice encoding and decoding, error detection and correction, signaling, and access to the SIM). In particular embodiments, the remote unit 105 may include terminal equipment ("TE") and / or may be embedded in an equipment or device (e.g., a computing device as described above).

[0037] The remote units 105 may communicate directly with one or more base units 121 of the RAN 120 via uplink ("UL") and downlink ("DL") communication signals. Additionally, the UL and DL communication signals may be carried over a wireless communication link 123, where the RAN 120 is an intermediate network that provides the remote units 105 with access to the mobile core network 130.

[0038] In various embodiments, the remote units 105 may communicate directly with each other (e.g., device-to-device communication) using V2X communication signals 115, where V2X transmissions may occur on V2X resources. As mentioned above, the remote units 105 may be provided with different V2X communication resources for different V2X modes. Mode 1 corresponds to an NR-based network-scheduled V2X communication mode. Mode 2 corresponds to an NR-based UE-scheduled V2X communication mode.

[0039] In some embodiments, the remote unit 105 communicates with an application server via a network connection with the mobile core network 130. For example, an application 107 (e.g., a web browser, a media client, a telephone and / or a voice over Internet protocol ("VoIP") application) in the remote unit 105 may trigger the remote unit 105 to establish a protocol data unit ("PDU") session (or other data connection) with the mobile core network 130 through the RAN 120. The mobile core network 130 then relays traffic between the remote unit 105 and the application server (e.g., a content server 151 in the packet data network 150) using the PDU session. The PDU session represents a logical connection between the remote unit 105 and the user plane function ("UPF") 131.

[0040] To establish a PDU session (or PDN connection), the remote unit 105 must register with the mobile core network 130 (also referred to as being "connected to the mobile core network" in the context of a fourth generation ("4G") system). It should be noted that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 130. Thus, the remote unit 105 may have at least one PDU session for communicating with a packet data network 150, e.g., representative of the Internet. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0041] In the context of 5G systems ("5GS"), the term "PDU session" refers to a data connection that provides an end-to-end ("E2E") user plane ("UP") connection between the remote unit 105 and a particular data network ("DN") through the UPF 131. A PDU session supports one or more Quality of Service ("QoS") flows. In certain embodiments, there may be a one-to-one mapping between QoS flows and QoS profiles such that all packets belonging to a particular QoS flow have the same 5G QoS Identifier ("5QI").

[0042] In the context of 4G / LTE systems, such as the Evolved Packet System ("EPS"), a Packet Data Network ("PDN") connection (also called an EPS session) provides an E2E UP connection between a remote unit and the PDN. The PDN connection procedure establishes an EPS bearer, i.e., a tunnel between the remote unit 105 and a Packet Gateway ("PGW", not shown) in the mobile core network 130. In certain embodiments, there is a one-to-one mapping between EPS bearers and QoS profiles, such that all packets belonging to a particular EPS bearer have the same QoS Class Identifier ("QCI").

[0043] The base units 121 may be distributed across a geographic region. In certain embodiments, the base units 121 may also be referred to as an access terminal, an access point, a base, a base station, a Node-B ("NB"), an evolved Node B (abbreviated as eNodeB or "eNB" and also known as an evolved Universal Terrestrial Radio Access Network ("E-UTRAN") Node B), a 5G / NR Node B ("gNB"), a Home Node B, a relay node, a RAN node, or any other terminology used in the art. The base units 121 are generally part of a RAN, such as the RAN 120, and may include one or more controllers communicatively coupled to one or more corresponding base units 121. These and other elements of a radio access network are not shown, but are generally well known by those skilled in the art. The base units 121 connect to a mobile core network 130 via the RAN 120.

[0044] The base unit 121 may serve several remote units 105 within a service area, such as a cell or a cell sector, via a wireless communication link 123. The base unit 121 may directly communicate with one or more of the remote units 105 via communication signals. In general, the base unit 121 transmits DL communication signals to serve the remote units 105 in time, frequency, and / or spatial domains. Furthermore, the DL communication signals may be carried on the wireless communication link 123. The wireless communication link 123 may be any suitable carrier in a licensed or unlicensed radio spectrum. The wireless communication link 123 facilitates communication between one or more of the remote units 105 and / or one or more of the base units 121. It should be noted that during NR-U operation, the base unit 121 and the remote units 105 communicate via an unlicensed radio spectrum.

[0045] In one embodiment, the mobile core network 130 is 5GC or Evolved Packet Core ("EPC") and may be coupled to a packet data network 150 such as the Internet and private data networks, among other data networks. The remote units 105 may have a subscription or other account with the mobile core network 130. Each mobile core network 130 belongs to a single Public Land Mobile Network ("PLMN"). This disclosure is not intended to be limited to any particular wireless communications system architecture or protocol implementation.

[0046] The mobile core network 130 includes several network functions ("NFs"). As shown, the mobile core network 130 includes at least one UPF 131. The mobile core network 130 also includes multiple control plane ("CP") functions, including, but not limited to, an access and mobility management function ("AMF") 133 that serves the RAN 120, a session management function ("SMF") 135, a network explorer function ("NEF") 136, a policy control function ("PCF") 137, a unified data management function ("UDM"), and a user data repository ("UDR").

[0047] The UPF 131 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU sessions for interconnecting data networks ("DNs") in the 5G architecture. The AMF 133 is responsible for NAS signaling termination, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. The SMF 135 is responsible for session management (i.e., session establishment, modification, release), remote unit (i.e., UE) Internet Protocol ("IP") address allocation and management, DE data notification, and traffic steering configuration of the UPF for proper traffic routing.

[0048] The NEF 136 is responsible for making network data and resources easily accessible to customers and network partners. Service providers activate new capabilities and expose them through APIs. These APIs allow third-party authorized applications to monitor and configure network behavior for multiple different subscribers (i.e. connected devices with different applications). The PCF 137 is responsible for the unified policy framework, providing policy rules to the CP functions and accessing subscription information for policy decisions in the UDR.

[0049] The UDM is responsible for generating Authentication and Key Agreement (AKA) credentials, handling user identification, access authorization, and subscription management. The UDR is a repository of subscriber information and can be used to service a number of network functions. For example, the UDR can store subscription data, policy related data, subscriber related data that is allowed to be exposed to third party applications, etc. In some embodiments, the UDM is co-located with the UDR, shown as a combined entity "UDM / UDR" 139.

[0050] In various embodiments, the mobile core network 130 may also include an Authentication Server Function ("AUSF") (acting as an authentication server), a Network Repository Function ("NRF") (providing registration and discovery of NF services, allowing NFs to identify appropriate services to each other and communicate with each other via application programming interfaces ("APIs"), or other NFs defined for 5GC. In particular embodiments, the mobile core network 130 may include an Authentication, Authorization, and Accounting ("AAA") server.

[0051] In various embodiments, the mobile core network 130 supports different types of mobile data connections and different types of network slices, with each mobile data connection utilizing a particular network slice, where a "network slice" refers to a portion of the mobile core network 130 optimized for a particular traffic type or communication service. A network slice instance may be identified by a single network slice selection assistance information ("S-NSSAI"), while a set of network slices that the remote unit 105 is authorized to use is identified by a network slice selection assistance information ("NS SAI").

[0052] Here, "NSSAI" refers to a vector value that includes one or more S-NSSAI values. In certain embodiments, various network slices may include separate instances of network functions, such as SMF 135 and UPF 131. In some embodiments, different network slices may share some common network functions, such as AMF 133. For ease of explanation, different network slices are not shown in FIG. 1, but their support is assumed. The mobile core network 130 in which the different network slices are deployed includes a network slice selection function ("NSSF") that is responsible for selecting a network slice instance to serve the remote unit 105, determining the allowed NSSAI, and determining the AMF set to be used to serve the remote unit 105.

[0053] 1, one skilled in the art will recognize that any number and type of network functions may be included in the mobile core network 130. Furthermore, in LTE variants in which the mobile core network 130 comprises an EPC, the depicted network functions may be replaced with appropriate EPC entities, Mobility Management Entity (MME), Serving Gateway ("SGW"), PGW, Home Subscriber Server ("HSS"), etc. For example, the AMF 133 is mapped to the MME, the SMF 135 is mapped to the control plane portion of the PGW and / or the MME, the UPF 131 is mapped to the SGW and user plane portion of the PGW, the UDM / UDR 139 is mapped to the HSS, etc.

[0054] Although FIG. 1 shows components of a 5G RAN and a 5G core network, the described embodiments apply to other types of communications networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications ("GSM", i.e., 2G digital cellular network), General Packet Radio Service ("GPRS"), UMTS, LTE variants, CDMA2000, Bluetooth, ZigBee, Sigfox, etc.

[0055] In the following description, the term "gNB" is used for base station, but can be replaced by any radio access node, e.g., RAN node, base station ("BS"), access point ("AP"), NR, etc. Furthermore, the operation is primarily described in the context of 5G NR. However, the proposed solutions / methods are equally applicable to other mobile communication systems supporting higher frequency CSI extensions.

[0056] There is a method disclosed in S2-2004714 for QoS aware power efficient PC5 communication for pedestrian UEs, which proposes that the UE derives DRX based on active applications running in the UE and negotiates DRX with other UEs running the same applications, as shown in Figure 2.

[0057] A disadvantage of the procedure shown in Figure 2 is that DRX can only be synchronized for unicast V2X operation and does not support groupcast or broadcast communication. In addition, the specific method includes an AMF that provides a default PC5 DRX configuration to the UE. If the UE determines that it cannot support the default PC5 DRX configuration based on the QoS requirements of the application, the UE determines an offset that extends the DRX active time to support such QoS requirements.

[0058] Additionally, a method is disclosed in which an Application Function ("AF") / Policy Control Function ("PCF") provides a PC5 DRX configuration for each V2X service. The UE's V2X layer provides the AS layer with a PC5 DRX configuration that the AS layer uses to determine which PC5 DRX to apply.

[0059] The solution for applying PC5 DRX in the receiving UE is as follows.

[0060] The receiving UE applies the default PC5 DRX provided by the AMF (if provided) or determines the PC5 DRX from the V2X configuration information as follows: The receiving UE determines the V2X service type to listen on based on the configured destination Layer-2 ID, e.g. as specified in TS 23.287, clause 5.6.1.2. The receiving UE then determines the PC5 QoS parameters based on the mapping of V2X service types to PC5 QoS parameters or based on the QoS requirements provided by the application, e.g. as specified in TS 23.287, subclause 5.1.2.1. The receiving UE then provides PC5 DRX according to the mapping of presentation quality index (PQI) to PC5 DRX configuration.

[0061] There are two options for how the PC5 DRX for reception is determined.

[0062] In a first embodiment, the PC5 DRX for each V2X service type is determined in the AS layer, which determines the PC5 QoS parameters based on the mapping of V2X service types to PC5 QoS parameters or based on the QoS requirements provided by the application, as specified in TS 23.287, section 5.1.2.1. The V2X layer then passes the QoS parameters for each V2X service type to the AS layer for reception. The AS layer determines the PC5 DRX to apply for reception according to the QoS requirements, for example using (pre)configuration, such as RRC signaling.

[0063] In a second embodiment, the PC5 DRX for each V2X service type is determined in the V2X layer, and the V2X layer determines the PC5 DRX configuration for each V2X service type based on the V2X configuration information provided by the AF or PCF. In one embodiment, the V2X configuration information includes a default PQI for each V2X service type and a PC5 DRX for each PQI. The V2X layer determines a default PQI (if no QoS requirements are provided by the application) and determines the PC5 DRX based on the PQI. In an alternative embodiment, the V2X layer determines the PC5 DRX for reception based on the PC5 DRX configuration for each V2X service type included in the V2X configuration information. The V2X layer then provides the PC5 DRX configuration for reception for each determined V2X service type to the AS layer. The AS layer then applies the PC5 DRX configuration.

[0064] A procedure for user equipment power saving for V2X communications is shown in Figures 3A and 3B.

[0065] In one embodiment, in step 1 (see block 302 ), the UE 301 receives a PC5 DRX configuration from the AF / PCF and / or AMF 309 .

[0066] In one embodiment, in step 2 (see block 304), a V2X application 303 requests to send a message via V2X and provides its application requirements, which may include QoS requirements.

[0067] In one embodiment, in step 3 (see block 306), the V2X layer 305 determines the V2X service type for reception, for example for broadcast and groupcast, based on the V2X configuration information, as described in 3GPP TS 23.287.

[0068] In a first embodiment (see block 308), the PC5 DRX per V2X service type is determined in the AS layer 307.

[0069] In one embodiment, in step 4a (see block 310), the receiving UE 301 determines the PC5 QoS parameters based on the mapping of V2X service types to PC5 QoS parameters as specified in clause 5.1.2.1 of TS 23.287 or based on the QoS requirements provided by the application.

[0070] In one embodiment, in step 5a (see messaging 312), the V2X layer 305 provides the AS layer 307 with QoS requirements for each determined V2X service type.

[0071] In one embodiment, in step 6a (see block 314), the AS layer 307 determines the PC5 DRX based on the QoS requirements of each V2X service type.

[0072] In a second embodiment (see block 316), the PC5 DRX per V2X service type is determined in the V2X layer 305.

[0073] In one embodiment, in step 4b (see block 318), the V2X layer 305 determines the PC5 DRX configuration for each V2X service type from the V2X configuration information, for example as described above in the first embodiment (see block 308).

[0074] In one embodiment, in step 5b (see block 320), the V2X layer 305 provides the AS layer 307 with a PC5 DRX configuration for each V2X service type.

[0075] In one embodiment, in step 6b (see block 322), the AS layer 307 of the UE 301 applies a PC5 DRX configuration.

[0076] In one embodiment, in step 7 (see block 324), the AS layer 307 provides information to the V2X layer 305 about the applied PC5 DRX per V2X service type.

[0077] FIG. 4 illustrates a user equipment device 400 that may be used for user equipment power saving for V2X communications, according to an embodiment of the disclosure. In various embodiments, the user equipment device 400 is used to implement one or more of the solutions described above. The user equipment device 400 may be an embodiment of a UE, such as the remote unit 105 and / or the UE 205, as described above. Additionally, the user equipment device 400 may include a processor 405, a memory 410, an input device 415, an output device 420, and a transceiver 425. In some embodiments, the input device 415 and the output device 420 are combined into a single device, such as a touch screen. In certain embodiments, the user equipment device 400 may not include any input device 415 and / or output device 420. In various embodiments, the user equipment device 400 may include one or more of the processor 405, the memory 410, and the transceiver 425, and may not include the input device 415 and / or the output device 420.

[0078] As shown, the transceiver 425 includes at least one transmitter 430 and at least one receiver 435, where the transceiver 425 communicates with one or more base units 121. In addition, the transceiver 425 supports at least one network interface 440 and / or an application interface 745. The application interface 745 supports one or more APIs. The network interface 440 supports 3GPP reference points, such as Uu and PC5. As will be appreciated by those skilled in the art, other network interfaces 440 may be supported.

[0079] In one embodiment, the processor 405 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 405 may be a microcontroller, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), an auxiliary processing unit, a field programmable gate array ("PFGA"), a digital signal processor ("DSP"), a co-processor, an application specific processor, or a similar programmable controller. In some embodiments, the processor 405 executes instructions stored in the memory 410 to perform the methods and routines described herein. The processor 405 is communicatively coupled to the memory 410, the input device 415, the output device 420, and the transceiver 425. In a particular embodiment, the processor 405 may include an application processor (also referred to as a "main processor") that manages application areas and operating system ("OS") functions, and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0080] In one embodiment, memory 410 is a computer-readable storage medium. In some embodiments, memory 410 includes volatile computer storage media. For example, memory 410 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 410 includes non-volatile computer storage media. For example, memory 410 may include a hard disk drive, flash memory, or other suitable non-volatile computer storage device. In some embodiments, memory 410 includes both volatile and non-volatile computer storage media.

[0081] In some embodiments, memory 410 stores data related to higher frequency CSI extensions. For example, memory 410 may store parameters, configurations, resource allocations, policies, etc., as described above. In particular embodiments, memory 410 also stores program code and associated data and one or more software applications, such as an operating system or other controller algorithms that operate on user equipment device 400.

[0082] In one embodiment, the input device 415 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 415 may be integrated with an output device 420, such as, for example, a touch screen or similar touch-sensitive display. In some embodiments, the input device 415 may include a touch screen such that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 415 includes two or more different devices, such as a keyboard and a touch panel.

[0083] In one embodiment, output device 420 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 420 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 420 may include, without limitation, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, output device 420 may include a wearable display communicatively coupled to, but separate from, the remainder of user equipment device 400, such as a smart watch, smart glasses, a head-up display, and the like. Additionally, output device 420 may be a component of a smartphone, a personal digital assistant, a television, a tablet computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0084] In certain embodiments, output device 420 includes one or more speakers for generating sound. For example, output device 420 can generate an audible alert or notification (e.g., a beep or chime). In some embodiments, output device 420 includes one or more haptic devices for producing vibration, motion, or other haptic feedback. In some embodiments, all or a portion of output device 420 can be integrated with input device 415. For example, input device 415 and output device 420 can form a touchscreen or similar touch-sensitive display. In other embodiments, output device 420 is located near input device 415.

[0085] The transceiver 425 includes at least one transmitter 430 and at least one receiver 435. As described herein, the transceiver 425 may be used to provide UL communication signals to the base unit 121 and receive DL communication signals from the base unit 121. Similarly, as described herein, the transceiver 425 may be used to transmit and receive SL signals (e.g., V2X communications). Although only one transmitter 430 and one receiver 435 are shown, the user equipment device 400 may have any suitable number of transmitters 430 and receivers 435. Furthermore, the transmitter 430 and receiver 435 may be any suitable type of transmitter and receiver. In one embodiment, the transceiver 425 includes a first transmitter / receiver pair used to communicate with a mobile communication network over a licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communication network over an unlicensed radio spectrum.

[0086] In certain embodiments, a first transmitter / receiver pair used to communicate with a mobile communications network over a licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communications network over an unlicensed radio spectrum may be combined into a single transceiver unit, such as, for example, a single chip that performs functions for use in both the licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, a particular transceiver 425, transmitter 430, and receiver 435 may be implemented as physically separate components that access shared hardware and / or software resources, such as, for example, a network interface 440.

[0087] In various embodiments, one or more transmitters 430 and / or one or more receivers 435 may be implemented in and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-chip, an ASIC, or other type of hardware component. In particular embodiments, one or more transmitters 430 and / or one or more receivers 435 may be implemented in and / or integrated into a multi-chip module. In some embodiments, other components, such as a network interface 440, or hardware components / circuits, may be integrated into a single chip with any number of transmitters 430 and / or receivers 435. In such embodiments, the transmitters 430 and receivers 435 may be logically configured as a transceiver 425 using one or more common control signals or as modularized transmitters 430 and receivers 435 implemented in the same hardware chip or multi-chip module.

[0088] In one embodiment, the processor 405 determines one or more destination Layer 2 IDs for reception in vehicle-to-everything (V2X) configuration information received from the network, determines one or more quality of service ("QoS") requirements for reception for each determined destination Layer 2 ID or IDs, and provides the determined one or more QoS requirements for each determined destination Layer 2 ID or IDs to an application services ("AS") layer.

[0089] In one embodiment, the processor 405 determines, for each determined destination Layer 2 ID or IDs, one or more QoS requirements for reception by determining an associated V2X service type for each of the one or more destination Layer 2 IDs and an associated PC5 QoS parameter for each V2X service type.

[0090] In one embodiment, the transceiver 425 receives a V2X configuration over the first air interface, the V2X configuration including one or more destination Layer 2 IDs for each V2X service type and one or more QoS requirements for each determined V2X service type for communication over the second air interface.

[0091] In one embodiment, the transceiver 425 receives a request from an application to receive data over the second wireless interface, the request including one or more QoS requirements.

[0092] In one embodiment, the processor 405 determines one or more QoS requirements based on at least one of the V2X configuration and requests from the application.

[0093] In one embodiment, the V2X configuration is received from a Policy Control Function (“PCF”) or an Application Function.

[0094] In one embodiment, the processor 405 receives information about applied PC5 discontinuous reception (DRX) for each determined V2X service type from the AS layer.

[0095] In one embodiment, the processor 405 receives one or more quality of service ("QoS") requirements for one or more destination Layer 2 IDs for reception of one of a groupcast and broadcast transmission from a vehicle-to-everything (V2X) layer, and determines information for an applied PC5 discontinuous reception (DRX) based on the QoS requirements.

[0096] In one embodiment, the processor 405 determines information about the applied PC5 DRX based on the V2X configuration information.

[0097] 5 illustrates an embodiment of a network device 500 that may be used for user equipment power saving for V2X communications, according to an embodiment of the disclosure. In some embodiments, the network device 500 may be an embodiment of a RAN node and its supporting hardware, such as a base unit 121 and / or a gNB, as described above. Additionally, the network device 500 may include a processor 505, a memory 510, an input device 515, an output device 520, and a transceiver 525. In certain embodiments, the network device 500 does not include any input device 515 and / or output device 520.

[0098] As shown, the transceiver 525 includes at least one transmitter 530 and at least one receiver 535. In some embodiments, the transceiver 525 communicates with one or more cells (or wireless coverage areas) supported by one or more base units 121. Additionally, the transceiver 525 may support at least one network interface 540 and / or application interface 545. The application interface 545 may support one or more APIs. The network interface 540 may support 3GPP reference points such as Uu, Nl, N2, N3, N5, N6, and / or N7. As will be appreciated by one skilled in the art, other network interfaces 540 may be supported.

[0099] In one embodiment, the processor 5605 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 505 may be a microcontroller, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), an auxiliary processing unit, a field programmable gate array ("FPGA"), a digital signal processor ("DSP"), a co-processor, an application specific processor, or a similar programmable controller. In some embodiments, the processor 505 executes instructions stored in the memory 510 to perform the methods and routines described herein. The processor 505 is communicatively coupled to the memory 510, the input device 515, the output device 520, and the transceiver 525. In a particular embodiment, the processor 505 may include an application processor (also known as a "main processor") that manages application domains and operating system ("OS") functions, and a baseband processor (also known as a "baseband radio processor") that manages radio functions. In various embodiments, the processor 505 controls the network device 500 to implement the behavior of the network entities (e.g., of a gNB) described above for power saving of user equipment for V2X communications.

[0100] Memory 510, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 510 includes a volatile computer storage medium. For example, memory 510 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 510 includes a non-volatile computer storage medium. For example, memory 510 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 510 includes both volatile and non-volatile computer storage media.

[0101] In some embodiments, memory 510 stores data related to indicating contention for sidelink resources using the feedback channel and / or mobile behavior. For example, memory 510 may store parameters, configurations, resource allocations, policies, etc., as described above. In particular embodiments, memory 510 also stores program code and associated data, such as an operating system ("OS") or other controller algorithms operating on device 500.

[0102] The input device 515, in one embodiment, may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 515 may be integrated with the output device 520, for example, as a touch screen or similar touch-sensitive display. In some embodiments, the input device 515 includes a touch screen, such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 515 includes two or more different devices, such as a keyboard and a touch panel.

[0103] In one embodiment, the output device 520 may include any known electronically controllable display or display device. The output device 520, in one embodiment, is designed to output visual, auditory, and / or tactile signals. In some embodiments, the output device 520 includes an electronically controllable display or display device capable of outputting visual data to a user. Furthermore, the output device 520 may be a component of a smartphone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0104] In certain embodiments, output device 520 includes one or more speakers for generating sound. For example, output device 520 may generate an audible alert or notification (e.g., a beep or chime). In some embodiments, output device 520 includes one or more haptic devices for generating vibration, movement, or other haptic feedback. In some embodiments, all or a portion of output device 520 may be integrated with input device 515. For example, input device 515 and output device 520 may form a touch screen or similar touch-sensitive display. In other embodiments, output device 520 may be located near input device 515.

[0105] As described above, the transceiver 525 communicates with one or more remote units and / or one or more interworking functions that provide access to one or more PLMNs. The transceiver 525 also communicates with one or more network functions (e.g., of the mobile core network 80). The transceiver 525 operates under the control of the processor 505 to transmit messages, data, and other signals and to receive messages, data, and other signals. For example, the processor 505 selectively activates the transceiver (or portions thereof) at particular times to transmit and receive messages.

[0106] The transceiver 525 includes one or more transmitters 530 and one or more receivers 535. In particular embodiments, the one or more transmitters 530 and / or the one or more receivers 535 may share transceiver hardware and / or circuitry. For example, the one or more transmitters 530 and / or the one or more receivers 535 may share antennas, antenna tuners, amplifiers, filters, oscillators, mixers, modulators / demodulators, power supplies, etc. In one embodiment, the transceiver 525 implements multiple logical transceivers that use different communication protocols or protocol stacks while using common physical hardware.

[0107] 6 is a flow chart of a method 600 for user equipment power saving for V2X communications. The method 600 may be performed by a UE, such as, for example, a remote unit 105 and / or a user equipment device 400, as described herein. In some embodiments, the method 600 may be performed by a processor, such as, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or the like, executing program code.

[0108] In one embodiment, method 600 first determines 605 one or more destination Layer 2 IDs for reception within vehicle-to-everything (V2X) configuration information received from the network. In one embodiment, method 600 determines 610 one or more V2X service types for reception of one of groupcast and broadcast transmissions based on the one or more destination Layer 2 IDs. In one embodiment, method 600 determines 615 one or more quality of service ("QoS") requirements for reception for each determined one or more destination Layer 2 IDs. In one embodiment, method 600 provides 620 the determined one or more QoS requirements for reception for each determined one or more destination Layer 2 IDs to an application services ("AS") layer, and method 600 ends.

[0109] A first apparatus is disclosed for user equipment power saving for V2X communications. The first apparatus may be executed by a UE, such as, for example, a remote unit 105 and / or a user equipment device 400, as described herein. In some embodiments, the first apparatus may be executed by a processor, such as, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc., executing program code.

[0110] In one embodiment, the first device includes a processor that determines one or more destination Layer 2 IDs for reception within vehicle-to-everything (V2X) configuration information received from the network, determines one or more quality of service ("QoS") requirements for reception for each determined one or more destination Layer 2 IDs, and provides the determined one or more QoS requirements for each determined one or more destination Layer 2 IDs to an application services ("AS") layer.

[0111] In one embodiment, the processor determines, for each determined one or more destination Layer 2 IDs, one or more QoS requirements for reception by determining an associated V2X service type for each of the one or more destination Layer 2 IDs and an associated PC5 QoS parameter for each V2X service type.

[0112] In one embodiment, the first device includes a transceiver that receives a V2X configuration over a first air interface, the V2X configuration including one or more destination Layer 2 IDs for each V2X service type and one or more QoS requirements for each determined V2X service type for communication over the second air interface.

[0113] In one embodiment, the transceiver receives a request from an application to receive data over a second wireless interface, the request including one or more QoS requirements.

[0114] In one embodiment, the processor determines one or more QoS requirements based on at least one of a V2X configuration and a request from an application.

[0115] In one embodiment, the V2X configuration is received from a Policy Control Function (“PCF”) or an Application Function.

[0116] In one embodiment, the processor receives information about applied PC5 discontinuous reception (DRX) for each determined V2X service type from the AS layer.

[0117] A first method is disclosed for user equipment power saving for V2X communications. The first method may be performed by a UE, such as, for example, a remote unit 105 and / or a user equipment device 400, as described herein. In some embodiments, the first method may be performed by a processor, such as, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc., executing program code.

[0118] In one embodiment, a first method determines one or more destination Layer 2 IDs for reception within vehicle-to-everything (V2X) configuration information received from a network, determines one or more quality of service ("QoS") requirements for reception for each determined destination Layer 2 ID, and provides the determined one or more QoS requirements for each determined destination Layer 2 ID to an application services ("AS") layer.

[0119] In one embodiment, the first method determines, for each determined one or more destination Layer 2 IDs, one or more QoS requirements for reception by determining an associated V2X service type for each of the one or more destination Layer 2 IDs and an associated PC5 QoS parameter for each V2X service type.

[0120] In one embodiment, a first method includes receiving a V2X configuration over a first air interface, the V2X configuration including one or more destination Layer 2 IDs for each V2X service type and one or more QoS requirements for each determined V2X service type for communication over a second air interface.

[0121] In one embodiment, a first method includes receiving a request from an application to receive data over a second wireless interface, the request including one or more QoS requirements.

[0122] In one embodiment, the first method determines one or more QoS requirements based on at least one of a V2X configuration and a request from an application.

[0123] In one embodiment, the V2X configuration is received from a Policy Control Function (“PCF”) or an Application Function.

[0124] A second device is disclosed for user equipment power saving for V2X communications. The second device may be executed by a UE, such as, for example, the remote unit 105 and / or the user equipment device 400, as described herein. In some embodiments, the second device may be executed by a processor, such as, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc., executing program code.

[0125] In one embodiment, the second device includes a processor that receives one or more quality of service ("QoS") requirements for one or more destination Layer 2 IDs for reception of one of a groupcast and broadcast transmission from a vehicle-to-everything (V2X) layer, and determines information about an applied PC5 discontinuous reception (DRX) based on the QoS requirements.

[0126] In one embodiment, the processor determines information about the applied PC5 DRX based on the V2X configuration information.

[0127] A second method is disclosed for user equipment power saving for V2X communications. The second method may be performed by a UE, such as, for example, a remote unit 105 and / or a user equipment device 400, as described herein. In some embodiments, the second method may be performed by a processor, such as, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc., executing program code.

[0128] In one embodiment, a second method receives one or more quality of service ("QoS") requirements for one or more destination Layer 2 IDs for reception of one of a groupcast and broadcast transmission from a vehicle-to-everything (V2X) layer, and determines information for an applied PC5 discontinuous reception (DRX) based on the QoS requirements.

[0129] In one embodiment, the second method determines information about the applied PC5 DRX based on V2X configuration information.

[0130] The embodiments may be embodied in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is therefore indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope. [Explanation of symbols]

[0131] 100 Wireless communication system 105 Remote Unit 107 Applications 115 Wireless Communication Links 120 RAN 121 Base Unit 123 Wireless Communication Links 130 Mobile Core Network 131 UPF 133 AMF 135 SMF 136 NEF 137 PCF 139 UDM / UDR 150 Packet Data Network 151 Content Server

Claims

1. A user equipment (UE) having a processor for wireless communication, At least one memory; and at least one processor coupled to the at least one memory, the at least one processor configured to: Receiving vehicle-to-everything (V2X) configuration information including one or more destination Layer 2 identifiers (IDs) for reception; determining the one or more destination Layer 2 IDs for reception according to the V2X configuration information; determining, at a first layer of the UE, one or more Quality of Service (QoS) requirements for reception for each determined one or more destination Layer 2 IDs; providing the determined QoS requirement(s) for each determined destination layer 2 ID(s) for reception to a second layer of the UE; The UE is configured to:

2. 2. The UE of claim 1, wherein the processor is configured to cause the UE to determine, for each determined one or more destination Layer 2 IDs, one or more QoS requirements for reception by determining an associated V2X service type for each of the one or more destination Layer 2 IDs and an associated PC5 QoS parameter for each V2X service type.

3. The UE of claim 1, further comprising a transceiver configured to cause the UE to receive a V2X configuration over a first radio interface, the V2X configuration including one or more destination Layer 2 IDs for each V2X service type and one or more QoS requirements for each determined V2X service type for communication over a second radio interface.

4. 4. The UE of claim 3, wherein the transceiver is configured to cause the UE to receive a request from an application to receive data over the second radio interface, the request including the one or more QoS requirements.

5. 4. The UE of claim 3, wherein the processor is configured to cause the UE to determine the one or more QoS requirements based on at least one of the V2X configuration and a request from an application.

6. 10. The UE of claim 1, wherein the V2X configuration is received from a policy control function (PCF) and an application function.

7. The UE of claim 1, wherein the processor receives, for the UE, information about an applied PC5 discontinuous reception (DRX) for each determined V2X service type from the second layer.

8. A method for wireless communication, comprising: receiving vehicle-to-everything (V2X) configuration information including one or more destination Layer 2 identifiers (IDs) for reception; determining the one or more destination Layer 2 IDs for reception according to the V2X configuration information; determining, for each determined one or more destination Layer 2 IDs, one or more Quality of Service (QoS) requirements for reception at a first layer of a User Equipment (UE); providing the determined QoS requirement(s) for each determined destination layer 2 ID(s) for reception to a second layer of the UE; A method comprising:

9. 10. The method of claim 8, further comprising determining, for each determined one or more destination Layer-2 IDs, one or more QoS requirements for reception by determining an associated V2X service type for each of the one or more destination Layer-2 IDs and an associated PC5 QoS parameter for each V2X service type.

10. 10. The method of claim 8, further comprising receiving, over a first air interface, a V2X configuration, the V2X configuration including one or more destination Layer 2 IDs for each V2X service type and one or more QoS requirements for each determined V2X service type for communication over a second air interface.

11. The method of claim 10 , further comprising receiving a request from an application to receive data over the second wireless interface, the request including the one or more QoS requirements.

12. 11. The method of claim 10, further comprising determining the one or more QoS requirements based on at least one of the V2X configuration and a request from an application.

13. 10. The method of claim 8, wherein the V2X configuration is received from a Policy Control Function (PCF) and an Application Function.

14. A user equipment (UE) for wireless communications, comprising: At least one memory; at least one processor coupled to the at least one memory; The processor may further include a step of: receiving one or more quality of service (QoS) requirements for one or more destination layer 2 IDs for receiving one of a groupcast transmission and a broadcast transmission from a vehicle-to-everything (V2X) layer; and determining information about an applied PC5 DRX (discontinuous reception) based on the QoS requirement.

15. The UE of claim 14, wherein the processor is configured to cause the UE to determine information about the applied PC5 DRX based on V2X configuration information.

Images