Discontinuous reception configuration parameters for communication

Abstract

Apparatuses, methods, and systems are disclosed for discontinuous reception configuration parameters for communication. One method (1000) includes receiving (1002), at a first user equipment and over a first radio interface, discontinuous reception configuration parameters for communication over a second radio interface. The method (1000) includes receiving (1004) a quality of service requirement for transmission over the second radio interface. The method (1000) includes determining (1006) discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirement. The method (1000) includes transmitting (1008) and receiving communication over the second radio interface based on the discontinuous reception communication parameters.

Description

[0001] Cross-references to related applications

[0002] This application claims U.S. Patent Application Serial No. 63 / 051,184, filed July 13, 2020, entitled "APPARATUSES, METHODS, AND SYSTEMS FOR A SIDELINK DRX MECHANISM-INTERACTION WITH UU DRXOPERATION", and Prateek Basu Mallick's patent application, also filed July 13, 2020, entitled "APPARATUSES, METHODS, AND SYSTEMS FOR SIDELINK POWER SAVING USING A DRX MECHANISM AND MINIMIZING ENSUING HALF DUPLEX". The entire priority of U.S. Patent Application Serial No. 63 / 051,207, entitled "Apparatus, Methods, and Systems for Power Saving of Sidelinks Using DRX Mechanisms and Minimizing Subsequent Half-Duplex Problems" filed by Dimitrios Karampatsis on July 13, 2020, entitled "Apparatus, Methods, and Systems for Supporting Power Saving for PC5 Communications"; and U.S. Patent Application Serial No. 63 / 051,217, entitled "Apparatus, Methods, and Systems for Power Saving for PC5 Communications" filed by Karthikeyan Ganesan on July 13, 2020, entitled "Apparatus, Methods, and Systems for ENHANCEMENT for SL Power Saving" is incorporated herein by reference. Technical Field

[0003] The subject matter disclosed in this article generally relates to wireless communication, and more specifically to discontinuous reception configuration parameters for communication. Background Technology

[0004] In some wireless communication networks, discontinuous reception can be used. In such embodiments, devices in the network can be configured in a variety of ways. Summary of the Invention

[0005] A method for discontinuous reception configuration parameters for communication is disclosed. Apparatus and systems also perform the functions of this method. One embodiment of the method includes receiving discontinuous reception configuration parameters for communication via a second radio interface at a first user equipment and through a first radio interface. In some embodiments, the method includes receiving quality of service (QoS) requirements for transmissions via the second radio interface. In some embodiments, the method includes determining discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the QoS requirements. In various embodiments, the method includes transmitting and receiving communication via the second radio interface based on the discontinuous reception communication parameters.

[0006] An apparatus for discontinuous reception configuration parameters for communication includes a first user equipment. In some embodiments, the apparatus includes a receiver that: receives discontinuous reception configuration parameters for communication via a second radio interface via a first radio interface; and receives quality of service (QoS) requirements for transmissions via the second radio interface. In various embodiments, the apparatus includes a processor that determines discontinuous reception communication parameters based on the discontinuous reception configuration parameters and the QoS requirements. In some embodiments, the apparatus includes a transmitter. Based on the discontinuous reception communication parameters, the transmitter transmits communication via the second radio interface, and the receiver receives the communication.

[0007] Another embodiment of the method for discontinuous reception configuration parameters for communication includes receiving a policy association request for a corresponding user equipment at a policy control function and via a first radio interface. In some embodiments, the method includes obtaining a subscription profile for the user equipment. The subscription profile includes a default discontinuous reception configuration for a second radio interface. In some embodiments, the method includes determining configuration information for the first user equipment for communication via the second radio interface. In various embodiments, the method includes transmitting the configuration information to the user equipment via non-access stratum control plane signaling through the first radio interface.

[0008] Another means for configuring discontinuous reception configuration parameters for communication includes policy and control functions. In some embodiments, the means includes a receiver that receives a policy association request for a corresponding user equipment via a first radio interface. In various embodiments, the means includes a processor that: obtains a subscription profile for the user equipment, wherein the subscription profile includes a default discontinuous reception configuration for a second radio interface; and determines configuration information for the first user equipment for communication via the second radio interface. In some embodiments, the means includes a transmitter that transmits the configuration information to the user equipment via the first radio interface through non-access stratum control plane signaling. Attached Figure Description

[0009] A more detailed description of the embodiments briefly described above will be presented with reference to the specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are not intended to be limiting of the scope; the embodiments will be described and explained with additional specificity and detail using the drawings, in which:

[0010] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system with discontinuous reception configuration parameters for communication;

[0011] Figure 2 This is a schematic block diagram illustrating one embodiment of a device for discontinuously receiving configuration parameters that can be used for communication;

[0012] Figure 3 This is a schematic block diagram illustrating one embodiment of a device for discontinuously receiving configuration parameters that can be used for communication;

[0013] Figure 4 This is a timing diagram illustrating an embodiment of a system for transmitting messages via a PC5 interface based on DRX configuration;

[0014] Figure 5 This is a schematic block diagram illustrating one embodiment of a system for extending DRX to support desired QoS;

[0015] Figure 6 This is a network communication diagram illustrating one embodiment of a DRX configuration via NAS (e.g., AMF-based);

[0016] Figure 7 This is a network communication diagram illustrating another embodiment of DRX configuration for UEs communicating via a unicast sidelink of PC5;

[0017] Figure 8 This is a network communication diagram illustrating one embodiment of a DRX configuration via NAS (e.g., PCF-based);

[0018] Figure 9 This is a network communication diagram illustrating one embodiment of a DRX configuration via a relay UE (e.g., RSU);

[0019] Figure 10 This is a flowchart illustrating one embodiment of a method for discontinuous reception configuration parameters for communication; and

[0020] Figure 11 This is a flowchart illustrating another embodiment of a method for discontinuously receiving configuration parameters for communication. Detailed Implementation

[0021] As those skilled in the art will understand, aspects of the embodiments can be embodied as systems, apparatus, methods, or program products. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, which may generally be referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments can take the form of program products embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device uses only signals for accessing the code.

[0022] Certain functional units described in this specification may be designated as modules to more specifically emphasize their implementation independence. For example, modules may be implemented as hardware circuits comprising custom very large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0023] Modules can also be implemented in code and / or software for execution by various types of processors. Identified code modules may, for example, comprise one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions. However, the executable files of identified modules do not need to be physically located together, but may include different instructions stored in different locations that, when logically joined together, comprise the module and achieve the purpose stated by the module.

[0024] In practice, a module of code can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and across several memory devices. Similarly, in this document, operational data can be identified and visualized within a module, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or can be distributed across different locations, including different computer-readable storage devices. Where a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0025] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0026] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable compact disk read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0027] The code used to perform the operations of the embodiments can be any number of lines and can 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 machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer via any type of network including a local area network ("LAN") or a wide area network ("WAN"), or it can be connected to an external computer (e.g., via the Internet through an Internet service provider).

[0028] References to "an embodiment," "embodiment," or similar language in this specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, throughout this specification, the phrases "in an embodiment," "in an embodiment," and similar language may, but not necessarily all, refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, the list of enumerated items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a," "an," and "the" also mean "one or more".

[0029] Furthermore, the features, structures, or characteristics of the described embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of the specific details, or using 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.

[0030] The following description of aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

[0031] The code may also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the schematic flowchart and / or schematic block diagram boxes or blocks.

[0032] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the function / action specified in the flowchart and / or block diagram boxes or boxes.

[0033] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings 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 schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0034] It should also be noted that in some alternative implementations, the functions marked in the boxes may occur in a different order than those marked in the figures. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures can be envisioned.

[0035] While various arrow and line types may be used in flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It will also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs a specific function or action.

[0036] The description of the elements in each figure can be referenced to the elements in the preceding figures. The same numbers refer to the same elements in all figures, including alternative embodiments of the same elements.

[0037] Figure 1 An embodiment of a wireless communication system 100 for discontinuous reception configuration parameters for communication is described. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although in Figure 1 A specific number of remote units 102 and network units 104 are depicted, but those skilled in the art will recognize that any number of remote units 102 and network units 104 can be included in the wireless communication system 100.

[0038] In one embodiment, remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected televisions), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, remote unit 102 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terms used in the art. Remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0039] Network units 104 can be distributed across a geographical area. In some embodiments, network element 104 may also be referred to as and / or may include access point, access terminal, base station, base station, location server, core network (“CN”), radio network entity, node-B, evolved node-B (“eNB”), 5G node-B (“gNB”), home node-B, relay node, device, core network, air server, radio access node, access point (“AP”), new radio (“NR”), network entity, access and mobility management function (“AMF”), unified data management (“UDM”), unified data repository (“UDR”), UDM / UDR, policy control function (“PCF”), radio access network (“RAN”), network slice selection function (“NSSF”), operations, administration and management (“OAM”), session management function (“SMF”), user plane function (“UPF”), application function, authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), or any other term used in the art. Network unit 104 is typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the public switched telephone network, as well as other networks. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those skilled in the art.

[0040] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP”), wherein network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”), and remote unit 102 transmits using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme on the uplink (“UL”). However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, and CDMA2000. ZigBee, Sigfoxx, and other protocols. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0041] Network unit 104 can serve multiple remote units 102 within a service area (e.g., a cell or cell sector) via a wireless communication link. Network unit 104 transmits DL communication signals in the time, frequency, and / or spatial domains to serve the remote units 102.

[0042] In various embodiments, remote unit 102 may receive discontinuous reception configuration parameters for communication via a second radio interface at a first user equipment and through a first radio interface. In some embodiments, remote unit 102 may receive quality of service (QoS) requirements for transmissions via the second radio interface. In some embodiments, remote unit 102 may determine discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the QoS requirements. In various embodiments, remote unit 102 may transmit and receive communication via the second radio interface based on the discontinuous reception communication parameters. Therefore, remote unit 102 can be used for discontinuous reception configuration parameters for communication.

[0043] In some embodiments, network unit 104 may receive a policy association request for a corresponding user equipment (UE) at a policy control function via a first radio interface. In some embodiments, network unit 104 may obtain a subscription profile for the UE. The subscription profile includes a default discontinuous reception configuration for a second radio interface. In some embodiments, network unit 104 may determine configuration information for the first UE for communication via the second radio interface. In various embodiments, network unit 104 may transmit the configuration information to the UE via non-access stratum control plane signaling through the first radio interface. Therefore, network unit 104 can be used for discontinuous reception configuration parameters for communication.

[0044] Figure 2 An embodiment of a device 200 for discontinuously receiving configuration parameters that can be used for communication is depicted. The device 200 includes one embodiment of a remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In some embodiments, the remote unit 102 may not include any input device 206 and / or the display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, memory 204, transmitter 210, and receiver 212, and may not include the input device 206 and / or the display 208.

[0045] In one embodiment, processor 202 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 202 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 202 executes instructions stored in memory 204 to perform the methods and routines described herein. Processor 202 is communicatively coupled to memory 204, input device 206, display 208, transmitter 210, and receiver 212.

[0046] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on remote unit 102.

[0047] In one embodiment, input device 206 may include any known computer input device, including a touch panel, button, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 206 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 206 includes two or more different devices such as a keyboard and a touch panel.

[0048] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, a liquid crystal display (“LCD”), a light-emitting diode (“LED”) display, an organic light-emitting diode (“OLED”) display, a projector, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, display 208 may include wearable displays such as smartwatches, smart glasses, head-up displays, etc. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0049] In some embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate an audible alarm or notification (e.g., a beep or ringtone). In some embodiments, display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be located near input device 206.

[0050] In some embodiments, receiver 210: receives discontinuous reception configuration parameters for communication via a second radio interface through a first radio interface; and receives quality of service (QoS) requirements for transmission via the second radio interface. In various embodiments, processor 202 determines discontinuous reception communication parameters based on the discontinuous reception configuration parameters and the QoS requirements. In some embodiments, based on the discontinuous reception communication parameters, transmitter 212 transmits communication via the second radio interface and receiver 210 receives the communication.

[0051] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 can have any suitable number of transmitters 210 and receivers 212. The transmitters 210 and receivers 212 can be of any suitable type. In one embodiment, the transmitters 210 and receivers 212 can be part of a transceiver.

[0052] Figure 3An embodiment of an apparatus 300 for discontinuously receiving configuration parameters that can be used for communication is described. The apparatus 300 includes one embodiment of a network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As will be understood, the processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to the processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of the remote unit 102, respectively.

[0053] In some embodiments, receiver 312 receives a policy association request for a corresponding user equipment (UE) via a first radio interface. In various embodiments, processor 302: obtains a subscription profile for the UE, wherein the subscription profile includes a default discontinuous reception configuration for a second radio interface; and determines configuration information for the first UE for communication via the second radio interface. In some embodiments, transmitter 310 transmits the configuration information to the UE via the first radio interface through non-access stratum control plane signaling.

[0054] In some embodiments, power-efficient sidelink communication can be supported via sidelink communication between the user equipment (“UE”) for pedestrians and the UE interface (“PC5”).

[0055] In some embodiments, the vehicle-to-everything (“V2X”) UE transmits messages for sidelink communication via PC5 at a constant rate. For example, cooperative awareness messages (“CAM”) may be transmitted via PC5 every 100 ms. This constant operation may reduce the power efficiency of the UE. However, V2X UEs (e.g., vehicles or roadside units (“RSUs”) have large battery capacities that support this constant operation. On the other hand, pedestrian UEs (e.g., smartphones, smartwatches) have limited battery capacities or available radio resources.

[0056] In various embodiments, V2X pedestrian UEs use PC5 application discontinuous reception (“DRX”) in a manner that increases power efficiency. In some embodiments, DRX synchronization is performed between V2X UEs running the same application and / or service to increase power efficiency.

[0057] It should be noted that, as used herein, the terms eNB and / or gNB are used for base stations but can be replaced by any other radio access node (e.g., base station (“BS”), eNB, gNB, access point (“AP”), new radio (“NR”), etc.). Furthermore, some embodiments described herein can be described in the context of NR V2X. However, the embodiments described herein are applicable to any mobile communication system that supports sidelink communication via the PC5 interface. Moreover, any embodiments herein can be combined.

[0058] In some embodiments, the UE may be configured with DRX for sidelink communication via PC5. In a first embodiment, the UE receives DRX configuration for sidelink communication via PC5 through Non-Access Stratum (“NAS”) signaling from an Application Management Function (“AMF”) or Policy Control Function (“PCF”). In a second embodiment, the application may provide synchronization parameters that assist the UE (e.g., a V2X layer) in identifying the required DRX parameters. In a third embodiment, the UE receives DRX configuration from a UE acting as a DRX synchronization function (e.g., an RSU UE).

[0059] In some embodiments, once the UE receives the DRX to be used via PC5, the UE applies the DRX for transmitting and / or receiving V2X messages, such as Figure 4 As shown in the diagram. In such an embodiment, the UE configures "active time" and "inactive time" for sidelink communication via PC5 based on the received DRX configuration. Furthermore, when the UE is in an "inactive time," it enters a "sleep" state and does not transmit or listen for sidelink communication messages via PC5. Conversely, when the UE is in an "active time," it can transmit data provided by the V2X application layer or listen for sidelink communication messages via PC5. If the V2X application provides data during the UE's inactive state, the UE buffers the data and transmits it during the active time period.

[0060] In various embodiments, the UE can apply the same DRX configuration used for communication through the UE to both the network interface (“Uu”) and the PC5 interface.

[0061] Figure 4 This is a timing diagram 400 illustrating an embodiment of a system for transmitting messages via a PC5 interface based on DRX configuration. Timing diagram 400 illustrates the timing of communication at application layer 402 compared to a DRX-based UE state 404. While UE state 404 is in an inactive period 406, application layer 402 transmits data 408, including a first time period from 410 to 412. Furthermore, a second time period 414 (e.g., 1 second) may occur between each data 408 transmission. UE state 404 may have an active period 416 as illustrated.

[0062] In some embodiments, NAS-based DRX configuration may exist. In a first embodiment, the UE receives the DRX configuration for sidelink communication via PC5 from the AMF or PCF via NAS signaling.

[0063] In various embodiments, the AMF determines that a DRX configuration for PC5 sidelink communication needs to be provided to the UE based on the UE subscription. More specifically, the AMF determines this by receiving a UE subscription from the Unified Data Repository (“UDR”) containing information indicating whether the UE is authorized to perform PC5 sidelink communication as a pedestrian UE. The DRX configuration provided to the UE may be based on a pre-configuration at the AMF. This pre-configuration may be performed by the network operator based on knowledge of the Quality of Service (“QoS”) requirements of the application providing pedestrian services. Once the UE receives the DRX configuration, the UE applies the DRX.

[0064] In some embodiments, certain V2X applications may require sidelink communication via PC5 for V2X services (e.g., identified by a Provider Service Identifier (“PSID”) or Intelligent Transport System Application Identifier (“ITS-AID”) with specific QoS requirements, such as low latency and high guaranteed bit rate (“GBR”) requirements. In such embodiments, the DRX configuration provided by the AMF may be insufficient to maintain low latency and / or high GBR. Furthermore, in such embodiments, the UE can add an offset to the configured DRX to extend the “active time” for transmitting data based on the application’s low latency and / or high GBR requirements. This is in… Figure 5 As shown in the image.

[0065] Specifically, Figure 5 This is a schematic block diagram 500 illustrating one embodiment of a system for extending DRX to support desired QoS. In schematic block diagram 500, UE state 502 (e.g., based on DRX supporting low-latency QoS) includes a repetition of active time 504, followed by an offset 506, and then an inactive period 508.

[0066] Figure 6 This diagram illustrates network communication 600 of one embodiment via a DRX configuration using NAS (e.g., AMF-based). Network communication 600 occurs between UE 602 (e.g., a pedestrian UE), AMF 604, and Unified Data Management (“UDM”) and / or UDR (“UDM / UDR”) 606. Each of the illustrated network communications 600 may include one or more messages.

[0067] In the first communication 608 transmitted from UE 602 to AMF 604, UE 602 transmits a message registering to the 3GPP network using a standard authentication process by sending a registration request to AMF 604. The registration request includes an indication that UE 602 has V2X capabilities.

[0068] AMF 604 performs the 610 Authentication Server Function (“AUSF”) selection, authentication, and security.

[0069] In the second communication 612 transmitted from UDM / UDR 606 to AMF 604, AMF 604 receives a subscription profile from UDR / UDM 606 during the registration process. UDM / UDR 606 contains 614 this subscription profile, which may include information indicating that UE 602 is authorized as a pedestrian UE for V2X communication via PC5.

[0070] AMF 604 determines from the subscription offer that UE 616 602 is authorized as a pedestrian UE for V2X communication via PC5.

[0071] Furthermore, AMF 604 determines the DRX configuration required for PC5 by 618. In addition, AMF 604 ensures that all UEs registered in the same service area receive the same DRX configuration.

[0072] In the third communication 620 transmitted from AMF 604 to UE 602, AMF 604 provides DRX configuration via PC5 in the registration acceptance message sent to UE 602.

[0073] Based on the received DRX configuration, UE 602 determines the 622 active and inactive times. UE 602 only transmits and / or listens for sidelink communication via PC5 during the active time. Furthermore, the Access Layer (“AS”) of UE 602 configures the active and inactive times for PC5. The AS layer in UE 602 does not transmit or monitor V2X messages during the inactive time. This can be applied to broadcast, group broadcast, and unicast transmissions.

[0074] The AS layer of UE 602 can notify higher layers (624) about the time interval at which V2X messages can be transmitted. Furthermore, the application in UE 602 requests (626) to send messages for sidelink communication via PC5 with specific QoS requirements. Additionally, UE 602 determines (628) that the configured DRX does not support the QoS requirements and determines an additional offset in the configured DRX to support the required QoS. UE 602 applies (630) DRX for all sidelink communication via PC5 for any V2X service. Once UE 602 has determined the required DRX, UE 602 can exchange DRXs with other UEs using the same V2X application and V2X service via unicast signaling.

[0075] In some embodiments, when two UEs exchange QoS requirements during sidelink communication via PC5 over a unicast link, the UEs can determine that different DRX configurations are required. This is in Figure 7 The image is shown in the middle.

[0076] Specifically, Figure 7 This diagram illustrates a network communication 700 of another embodiment for DRX configuration between UEs communicating via a unicast sidelink on PC5. Network communication 700 occurs between a first UE 702 (e.g., a pedestrian UE) and a second UE 704 (e.g., a pedestrian UE). Each of the illustrated network communications 700 may include one or more messages.

[0077] In some configurations, during the first communication 706 transmitted between the first UE 702 and the second UE 704, the first UE 702 and the second UE 704 determine active and inactive times based on the received DRX configuration. The first UE 702 and the second UE 704 transmit and / or listen for sidelink communications via PC5 only during the active time.

[0078] In the second communication 708 transmitted between the first UE 702 and the second UE 704, the AS layer of each UE can notify the higher layer of the active and inactive times.

[0079] In the third communication 710 transmitted between the first UE 702 and the second UE 704, if the first UE 702 needs to establish a unicast session with the second UE 704 via PC5, the first UE 702 establishes a unicast connection during the active time period. During the security association period, both the first UE 702 and the second UE 704 determine the QoS requirements and the associated DRX configuration.

[0080] Both UE 702 and UE 704 use the DRX negotiated by 712. If the unicast session ends, UE 702 and UE 704 fall back to the default DRX.

[0081] In various embodiments, DRX configuration is provided from the PCF via NAS. The PCF provides a default DRX via PC5 for the V2X services used by the pedestrian UE in the supplied V2X configuration information. This V2X configuration information may include: 1) a mapping of the V2X services for the pedestrian UE (e.g., identified by PSID or ITS-AID) to the default DRX configuration; 2) a mapping of the DRX configuration for each QoS requirement (e.g., QoS class, packet delay budget (“PDB”), etc.) – in one embodiment, there may be a default DRX configuration and an additional offset for each QoS requirement; and / or 3) a mapping of the DRX configuration for each playback type (e.g., broadcast, unicast, group broadcast).

[0082] In some embodiments, if an application requests to send sidelink communication via PC5, the UE uses the DRX configuration within its V2X configuration to determine the DRX. If the application has specific QoS requirements, the UE determines an additional offset based on the received DRX configuration. The process of providing the UE with the DRX configuration from the PCF is as follows: Figure 8 As shown.

[0083] Specifically, Figure 8 This diagram illustrates network communication 800 of one embodiment via a DRX configuration using NAS (e.g., PCF-based). Network communication 800 occurs between a first UE 802 (e.g., a pedestrian UE), a second UE 804 (e.g., a pedestrian UE), RAN 806, AMF 808, UDM / UDR 810, and PCF 812. Each of the illustrated network communications 800 may include one or more messages.

[0084] In the first communication 814 transmitted from the second UE 804 to the AMF 808 and / or in the second communication 816 transmitted from the first UE 802 to the AMF 808, the first UE 802 and the second UE 804 register with the 3GPP network using a standard authentication process by sending a registration request. The registration request includes an indication that the first UE 802 and the second UE 804 have V2X capabilities.

[0085] AMF 808 implements 818AUSF selection, authentication, and security.

[0086] In a third communication 820 transmitted between AMF 808 and UDM / UDR 810, AMF 808 receives a subscription profile from UDR / UDM 810 during the registration process. UDM / UDR 810 contains 822 this subscription profile, which may include information indicating that the UE, as a pedestrian UE, is authorized for V2X communication via PC5.

[0087] AMF 808 determines from the subscription provider that UE 824 is authorized as a pedestrian UE for V2X communication via PC5 and selects PCF 812.

[0088] In the fourth communication 826 transmitted between AMF 808 and PCF 812, AMF 808 and PCF 812 establish a UE policy association including V2X capability indication.

[0089] In the fifth communication 828 transmitted from AMF 808 to the second UE 804 and / or in the sixth communication 830 transmitted from AMF 808 to the first UE 802, AMF 808 completes the registration with the UE using a registration accept message.

[0090] The PCF 812 determines the 832 V2X configuration based on subscription information provided by the UDM / UDR 810. The PCF 812 includes DRX configuration for sidelink communication via PC5 in the V2X configuration.

[0091] In the seventh communication 834 transmitted from PCF 812 to the first UE 802 and / or in the eighth communication 836 transmitted from PCF 812 to the second UE 804, PCF 812 provides V2X configuration to the UE via transparent UE configuration update using UE policy delivery.

[0092] Based on the received DRX configuration and V2X application requirements (e.g., QoS requirements, application periodicity), the first UE 802 and the second UE 806 determine the active and inactive times of 838. The first UE 802 and the second UE 806 transmit and / or listen for V2X messages via PC5 only during the active time period for specific V2X services used by pedestrians (e.g., based on the DRX configuration via PC5).

[0093] In the second embodiment, an application-layer DRX configuration may exist. Furthermore, in the second embodiment, the application's message periodicity and QoS requirements are provided from the upper layer to the UE's V2X layer. The V2X layer determines the optimal DRX configuration based on the requirements of each application and the DRX configuration received as in the first embodiment.

[0094] In the third embodiment, dynamic DRX synchronization via a relay UE may exist. Furthermore, in the third embodiment, a UE synchronized with the DRX configuration supporting one or more V2X services via PC5 (e.g., this UE is designated as a "DRX synchronized" UE and / or a relay UE) is synchronized via sidelink communication via PC5. The DRX synchronized UE may be an RSU supporting sidelink communication via PC5 and / or Uu. The DRX synchronized UE announces its supported V2X services (e.g., support for V2X communication for pedestrian services identified by PSID or ITS-AID) via broadcast signaling. The UE may also additionally broadcast support for DRX synchronization for one or more V2X services.

[0095] In some embodiments, UEs interested in services advertised by DRX-synchronized UEs establish unicast connections using DRX synchronization information based on the V2X services the UEs are active with.

[0096] In some embodiments, a relay UE or DRX synchronization UE periodically broadcasts a DRX configuration for each service type of a pedestrian UE, and the pedestrian UE can use the DRX configuration to broadcast messages to other pedestrian UEs.

[0097] In various embodiments, the DRX synchronization UE maintains the same DRX configuration for all UEs interested in the service. The DRX synchronization UE advertises and updates the DRX configuration to all UEs based on the QoS requirements of each UE that has established a unicast connection with the DRX synchronization UE.

[0098] Figure 9 This diagram illustrates network communication 900 of one embodiment of a DRX configuration via a relay UE (e.g., RSU). Network communication 900 occurs between a first UE 902 (e.g., a pedestrian UE), a second UE 904 (e.g., a pedestrian UE), and a relay UE 906 (e.g., a DRX synchronization UE). Each of the illustrated network communications 900 may include one or more messages.

[0099] In a first communication 908 transmitted from relay UE 906 to second UE 904 and / or in a second communication 910 transmitted from relay UE 906 to first UE 902, relay UE 906, acting as DRX synchronization UE, announces support for DRX synchronization for one or more V2X services to first UE 902 and second UE 904 via broadcast signaling.

[0100] The first UE 902 determines 912 based on the “specified layer-2 ID” of the first communication 908 to establish a unicast connection with the PC5-based RSU.

[0101] In the second communication 914 transmitted from the first UE 902 to the relay UE 906, the first UE 902 sends a direct communication request to the relay UE 906, including source user information and / or the requested V2X service (e.g., within V2X service information).

[0102] In a potential third communication 916 transmitted between the first UE 902 and the relay UE 906, a security association (e.g., RSU-based PC5) is established between the first UE 902 and the relay UE 906. During the security association, the first UE 902 provides its QoS requirements. In various embodiments, the first UE 902 can provide its current DRX configuration. The relay UE 906 can determine the required DRX configuration and update the first UE 902.

[0103] In the fourth communication 918 transmitted from relay UE 906 to first UE 902, once the security association is completed, relay UE 906 sends a direct communication acceptance message.

[0104] In some embodiments, the second UE 904 establishes a unicast connection 920 with the relay UE 906 via steps 912 to 918.

[0105] If the relay UE 906 determines that the 922DRX configuration has changed, the relay UE updates all UEs with the new DRX configuration for the service.

[0106] In an optional fifth communication 924 transmitted from relay UE 906 to first UE 902, relay UE 906 initiates a transmission of a link modification request to all UEs with unicast connections and provides updated DRX configurations (e.g., V2X service information, DRX information).

[0107] In an optional sixth communication 926 transmitted from the first UE 902 to the relay UE 906, the first UE 902 sends a link modification confirmation.

[0108] UE applications 928 and 930 configure DRX for all V2X communications corresponding to the V2X services advertised by relay UE 906.

[0109] Figure 10 This is a flowchart illustrating one embodiment of a method 1000 for discontinuous reception of configuration parameters for communication. In some embodiments, method 1000 is performed by a device, such as remote unit 102. In some embodiments, method 1000 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0110] In various embodiments, method 1000 includes receiving 1002 discontinuous reception configuration parameters for communication via a second radio interface at a first user equipment and via a first radio interface. In some embodiments, method 1000 includes receiving 1004 quality of service requirements for transmission via the second radio interface. In some embodiments, method 1000 includes determining 1006 discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements. In various embodiments, method 1000 includes transmitting 1008 and receiving communication via the second radio interface based on the discontinuous reception communication parameters.

[0111] In some embodiments, receiving discontinuous reception configuration parameters includes receiving the discontinuous reception configuration parameters from a policy control function. In some embodiments, determining discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on quality of service requirements includes determining an offset to the discontinuous reception configuration parameters to satisfy the quality of service requirements. In various embodiments, determining the offset is based on a mapping from the offset parameters to the quality of service requirements included in the discontinuous reception configuration parameters. In one embodiment, receiving the quality of service requirements for transmissions via a second radio interface includes receiving the quality of service requirements from a second user equipment.

[0112] In some embodiments, determining discontinuous reception communication parameters based on discontinuous reception parameters includes determining active and inactive times. In some embodiments, inactive time includes the time during which the first user equipment is in a sleep state and does not transmit or listen for sidelink communication messages through the second radio interface. In various embodiments, receiving discontinuous reception configuration parameters includes receiving a default discontinuous reception configuration.

[0113] In one embodiment, the user equipment uses default discontinuous receive configuration parameters to fall back to default discontinuous receive communication. In some embodiments, the default discontinuous receive configuration includes a mapping of configurations from per vehicle to all service types. In some embodiments, the default discontinuous receive configuration includes a mapping of discontinuous receive configuration parameters per quality of service requirement.

[0114] In various embodiments, the default discontinuous reception configuration includes a mapping of discontinuous reception configuration parameters for each multicast, broadcast, or unicast transmission via the second radio interface. In one embodiment, transmitting and receiving communication via the second radio interface includes transmitting and receiving communication with a second user equipment via the PC5 interface. In some embodiments, transmissions via the first radio interface include communication with the mobile core network via the Uu interface.

[0115] Figure 11This is a flowchart illustrating one embodiment of a method 1100 for discontinuous reception of configuration parameters for communication. In some embodiments, method 1100 is performed by a device, such as network unit 104. In some embodiments, method 1100 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0116] In various embodiments, method 1100 includes receiving, 1102, a policy association request for a corresponding user equipment at a policy control function and via a first radio interface. In some embodiments, method 1100 includes obtaining, 1104, a subscription profile for the user equipment. This subscription profile includes a default discontinuous reception configuration for a second radio interface. In some embodiments, method 1100 includes determining, 1106, configuration information for the first user equipment for communication via the second radio interface. In various embodiments, method 1100 includes transmitting, 1108, configuration information to the user equipment via non-access stratum control plane signaling through the first radio interface.

[0117] In one embodiment, a method includes: receiving discontinuous reception configuration parameters for communication via a second radio interface at a first user equipment and via a first radio interface; receiving quality of service requirements for transmissions via the second radio interface; determining discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements; and transmitting and receiving communication via the second radio interface based on the discontinuous reception communication parameters.

[0118] In some embodiments, receiving discontinuous reception configuration parameters includes receiving discontinuous reception configuration parameters from a policy control function.

[0119] In some embodiments, determining discontinuous reception communication parameters based on discontinuous reception configuration parameters and based on quality of service requirements includes determining an offset to the discontinuous reception configuration parameters to meet the quality of service requirements.

[0120] In various embodiments, the offset is determined based on a mapping of the offset parameter to the quality of service requirements included in the discontinuous reception configuration parameters.

[0121] In one embodiment, receiving a quality of service (QoS) requirement for a transmission via the second radio interface includes receiving the QoS requirement from the second user equipment.

[0122] In some embodiments, determining discontinuous reception communication parameters based on discontinuous reception parameters includes determining active and inactive times.

[0123] In some embodiments, inactive time includes the time during which the first user equipment is in sleep mode and does not transmit sidelink communication messages through the second radio interface or listen for sidelink communication messages through the second radio interface.

[0124] In various embodiments, receiving discontinuous reception configuration parameters includes receiving default discontinuous reception configuration.

[0125] In one embodiment, the user equipment uses default discontinuous reception configuration parameters to fall back to default discontinuous reception communication.

[0126] In some embodiments, the default discontinuous reception configuration includes a mapping of per-vehicle to all service types configurations.

[0127] In some embodiments, the default discontinuous reception configuration includes a mapping of discontinuous reception configuration parameters per quality of service requirement.

[0128] In various embodiments, the default discontinuous reception configuration includes a mapping of discontinuous reception configuration parameters transmitted per multicast, broadcast, or unicast via the second radio interface.

[0129] In one embodiment, transmitting and receiving communications via the second radio interface includes transmitting and receiving communications with a second user equipment via the PC5 interface.

[0130] In some embodiments, transmissions via the first radio interface include communication with the mobile core network via the Uu interface.

[0131] In one embodiment, an apparatus includes a first user equipment. The apparatus further includes a receiver that: receives discontinuous reception configuration parameters for communication via a second radio interface via a first radio interface; and receives quality of service (QoS) requirements for transmission via the second radio interface; a processor that determines discontinuous reception communication parameters based on the discontinuous reception configuration parameters and the QoS requirements; and a transmitter that transmits communication via the second radio interface based on the discontinuous reception communication parameters, and the receiver receives the communication.

[0132] In some embodiments, receiving discontinuous reception configuration parameters by the receiver includes receiving discontinuous reception configuration parameters from a policy control function.

[0133] In some embodiments, the processor determines discontinuous reception communication parameters based on discontinuous reception configuration parameters and quality of service requirements, including determining an offset to the discontinuous reception configuration parameters to meet the quality of service requirements.

[0134] In various embodiments, the processor determines the offset based on a mapping of the offset parameter to the quality of service requirements included in the discontinuous reception configuration parameters.

[0135] In one embodiment, the receiver receiving quality of service (QoS) requirements for transmissions via the second radio interface includes the receiver receiving QoS requirements from the second user equipment.

[0136] In some embodiments, the processor determines discontinuous reception communication parameters based on discontinuous reception parameters, including the processor determining active and inactive times.

[0137] In some embodiments, inactive time includes the time during which the first user equipment is in sleep mode and does not transmit sidelink communication messages through the second radio interface or listen for sidelink communication messages through the second radio interface.

[0138] In various embodiments, the receiver receiving discontinuous reception configuration parameters include the receiver receiving a default discontinuous reception configuration.

[0139] In one embodiment, the user equipment uses default discontinuous reception configuration parameters to fall back to default discontinuous reception communication.

[0140] In some embodiments, the default discontinuous reception configuration includes a mapping of per-vehicle to all service types configurations.

[0141] In some embodiments, the default discontinuous reception configuration includes a mapping of discontinuous reception configuration parameters per quality of service requirement.

[0142] In various embodiments, the default discontinuous reception configuration includes a mapping of discontinuous reception configuration parameters transmitted via each group of broadcast, broadcast, or unicast transmissions through the second radio interface.

[0143] In one embodiment, transmitting communication via a second radio interface transmitter and receiving communication via a receiver includes transmitting communication with a second user equipment via a PC5 interface and receiving communication with the second user equipment via the transmitter.

[0144] In some embodiments, transmissions via the first radio interface include communication with the mobile core network via the Uu interface.

[0145] In one embodiment, a method includes: receiving a policy association request for a corresponding user equipment at a policy control function and via a first radio interface; obtaining a subscription profile for the user equipment; wherein the subscription profile includes a default discontinuous reception configuration for a second radio interface; determining configuration information for the first user equipment for communication via the second radio interface; and transmitting the configuration information to the user equipment via non-access stratum control plane signaling through the first radio interface.

[0146] In one embodiment, an apparatus includes policy and control functions. The apparatus further includes: a receiver that receives a policy association request for a corresponding user equipment via a first radio interface; a processor that: obtains a subscription profile for the user equipment; wherein the subscription profile includes a default discontinuous reception configuration for a second radio interface; and determines configuration information for the first user equipment for communication via the second radio interface; and a transmitter that transmits the configuration information to the user equipment via the first radio interface through non-access stratum control plane signaling.

[0147] Other specific embodiments may be practiced. The described embodiments should be considered in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All variations falling within the meaning and equivalents of the claims should be included within their scope.

Claims

1. An apparatus including a first user equipment, the apparatus further comprising: Receiver, the receiver: Receive discontinuous reception configuration parameters for communication via the second radio interface through the first radio interface; processor, the processor Discontinuous reception communication parameters are determined based on the discontinuous reception configuration parameters and the quality of service (QoS) requirements of the application provided from the upper layer of the first user equipment, wherein the QoS requirements are for the transmissions requested by the application of the first user equipment via the second radio interface; and Transmitter; Based on the discontinuous reception communication parameters, the transmitter transmits communication and the receiver receives communication through the second radio interface.

2. The apparatus according to claim 1, wherein, The receiver receiving the discontinuous reception configuration parameters includes: the receiver receiving the discontinuous reception configuration parameters from the policy control function.

3. The apparatus according to claim 1, wherein, The processor determines the discontinuous reception communication parameters based on the discontinuous reception configuration parameters and the quality of service requirements, including: the processor determines the offset to the discontinuous reception configuration parameters to meet the quality of service requirements.

4. The apparatus according to claim 3, wherein, The processor determines the offset based on the mapping of the offset parameter to the quality of service requirements included in the discontinuous reception configuration parameters.

5. The apparatus according to claim 1, wherein, The processor determines the discontinuous reception communication parameters based on the discontinuous reception parameters, including: the processor determines the active time and the inactive time.

6. The apparatus according to claim 5, wherein, The inactive time includes the time during which the first user equipment is in a sleep state and does not transmit sidelink communication messages through the second radio interface or listen for sidelink communication messages through the second radio interface.

7. The apparatus according to claim 1, wherein, The receiver receiving the discontinuous reception configuration parameters includes: the receiver receiving the default discontinuous reception configuration.

8. The apparatus according to claim 7, wherein, The user equipment uses the default discontinuous reception configuration parameters to fall back to the default discontinuous reception communication.

9. The apparatus according to claim 7, wherein, The default discontinuous reception configuration includes a mapping of configurations from each vehicle to all service types.

10. The apparatus according to claim 7, wherein, The default discontinuous reception configuration includes a mapping of discontinuous reception configuration parameters for each quality of service requirement.

11. The apparatus according to claim 7, wherein, The default discontinuous reception configuration includes a mapping of discontinuous reception configuration parameters transmitted per multicast, broadcast, or unicast via the second radio interface.

12. The apparatus according to claim 1, wherein, The transmitter transmitting communication via the second radio interface and the receiver receiving communication include: the transmitter transmitting communication with a second user equipment via a PC5 interface and the receiver receiving communication with the second user equipment.

13. The apparatus according to claim 1, wherein, Transmissions via the first radio interface include communication with the mobile core network via the Uu interface.

14. An apparatus including strategy and control functions, the apparatus further comprising: A receiver that receives a policy association request for a corresponding user equipment via a first radio interface; Processor, the processor: Obtain the subscription profile for the user device; The subscription profile includes a default discontinuous reception configuration for the second radio interface; and To determine configuration information for the user equipment for communication via the second radio interface; as well as A transmitter transmits the configuration information to the user equipment via a non-access stratum control plane signaling through the first radio interface, wherein the discontinuous reception configuration for the user equipment is determined based on the configuration information and based on the quality of service requirements of an application provided from the upper layer of the user equipment, wherein the quality of service requirements are for the transmissions requested by the application of the user equipment through the second radio interface.

Images