Control channel signaling for user equipment (UE) power saving
Through the DRX configuration and DCI format provided by the UE receiving base station, PDCCH monitoring is managed, which solves the power consumption and communication efficiency problems of user equipment in low power states, and achieves more efficient wireless communication.
Patent Information
- Application Number
- CN202080044472.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-05-01
- Filing Date
- 2020-05-01
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2040-05-01
AI Technical Summary
In existing wireless communication systems, it is difficult for user equipment (UE) to efficiently manage downlink control channel (PDCCH) monitoring in low power states, resulting in increased power consumption and reduced communication efficiency.
The UE monitors wake-up signaling on the physical downlink control channel (PDCCH) through the non-continuous reception (DRX) configuration provided by the receiving base station, and determines whether to wake up according to the predetermined DCI format, thereby skipping unnecessary monitoring opportunities and entering. Sleep state.
Effectively manage the power consumption of the UE, improve communication efficiency, reduce ineffective monitoring opportunities, and improve system performance.
Smart Images

Figure CN114008960B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This disclosure claims the benefit of priority to U.S. Provisional Patent Application No. 62 / 841,766, entitled “CONTROL CHANNEL SIGNALING FOR USER EQUIPMENT (UE) POWERSAVING,” filed on May 1, 2019. The entirety of the above-described patent application is incorporated herein by reference. Technical Field
[0003] The present disclosure relates generally to wireless communication systems. Background Art
[0004] Base stations, such as nodes of a radio access network (RAN), can communicate wirelessly with wireless devices, such as user equipment (UE). Downlink (DL) transmissions refer to communications from a base station to a wireless device. Uplink (UL) transmissions refer to communications from a wireless device to another device, such as a base station. A base station can transmit control signaling in order to control wireless devices operating within its network. Summary of the invention
[0005] The present invention describes systems, devices and techniques for user equipment (UE) power control. The techniques include receiving a discontinuous reception (DRX) configuration by a UE from a base station; monitoring a downlink control information (DCI) message outside the DRX active time on a physical downlink control channel (PDCCH) by the UE based on the DRX configuration, the DCI message having a predetermined DCI format configured to provide wake-up signaling; receiving a DCI message outside the DRX active time by the UE, the DCI message having the predetermined DCI format; and determining whether to wake up based on the received DCI message by the UE. Other specific implementations include corresponding systems, devices and computer programs for performing the actions of the method defined by instructions encoded on a computer-readable storage device.
[0006] These and other implementations may include one or more of the following features. In some implementations, the received DCI message includes a wake-up indication, which may be referred to as a wake-up signal (WUS). Specific implementations may include determining whether to allow the UE to skip PDCCH monitoring for a predetermined number of opportunities based on the received DCI message. In some implementations, the DCI message includes a field for activating or deactivating one or more cells. In some implementations, the received predetermined DCI format is a group common DCI format. In some implementations, the UE is one of a plurality of UEs, and each of the plurality of UEs is configured to monitor the group common DCI format. In some implementations, the group common DCI format includes a UE-specific field indicating whether the UE is to be awakened.
[0007] When the DCI message is received outside the DRX active time and indicates no wake-up, a specific implementation may include remaining in the sleep state and skipping a predetermined number of DRX cycles. A specific implementation may include waking up from the sleep state and transitioning to the active state when a DCI message is received outside the DRX active time and indicates wake-up. In some specific implementations, the set of common DCI formats includes one or more UE-specific bits mapped to one or more of the following: wake-up indication, cross-slot scheduling configuration, triggering of reference signals, indication of uplink resources for channel status reporting, activation of cells, deactivation of cells, activation of carriers, deactivation of carriers, triggering of BWP switching, PDCCH decoding information, DRX configuration, or an indication of the number of DRX cycles to be skipped or activated.
[0008] A specific implementation may include monitoring an additional DCI message during DRX active time, the additional DCI message having a predetermined format, the predetermined format being configured to provide go-to-sleep (GTS) signaling, and including one or more UE-specific bits mapped to one or more of the following: an go-to-sleep indication for controlling whether the UE skips PDCCH monitoring or transitions from active time to external active time, the number of PDCCH monitoring opportunities to be skipped, the PDCCH skipping duration, cell activation, cell deactivation, carrier activation, or carrier deactivation.
[0009] The UE may include one or more processors, a transceiver, and a memory storing instructions, which, when executed by the one or more processors, cause the one or more processors to perform operations. The operations may include receiving a DRX configuration from a base station via a transceiver; based on the DRX configuration, monitoring a DCI message outside the DRX active time via the transceiver on a PDCCH, the DCI message having a predetermined DCI format configured to provide wake-up signaling; receiving the DCI message outside the DRX active time by the transceiver; and determining whether to wake up based on the received DCI message.
[0010] The communication circuit may include a circuit configured to receive a DRX configuration from a base station; and monitor a DCI message outside the DRX active time on a PDCCH based on the DRX configuration, the DCI message having a predetermined DCI format configured to provide wake-up signaling; and receive the DCI message outside the DRX active time; and a circuit configured to determine whether to cause wake-up based on the DCI message. The DCI message may include a wake-up indication. The communication circuit may include a circuit for determining whether to allow the UE to skip PDCCH monitoring for a predetermined number of opportunities based on the DCI message.
[0011] The details of one or more specific implementations are set forth in the drawings and description below. Other features and advantages will be apparent from the detailed description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1 An example of a wireless communication system is illustrated.
[0013] Figure 2 An exemplary architecture of a system including a core network is illustrated.
[0014] Figure 3 Another exemplary architecture of a system including a core network is illustrated.
[0015] Figure 4 An example of infrastructure equipment is shown.
[0016] Figure 5 Examples of platforms or devices are shown.
[0017] Figure 6 Exemplary components of baseband circuitry and radio front-end circuitry are illustrated.
[0018] Figure 7 Exemplary components of a cellular communications circuit are shown.
[0019] Figure 8 Example protocol functions that may be implemented in a wireless communication system are shown.
[0020] Fig. 9 An example of a computer system is illustrated.
[0021] Fig. 10A , Fig. 10B and Fig. 10C Different aspects of DRX mode operation are shown, wherein the UE is configured to receive GTS L1 signaling during the on state to cause the UE to enter the dormant state.
[0022] Fig.11 An example of timing is shown, where the GTS indicates the BWP for the subsequent DRX cycle.
[0023] Fig. 12A , Fig. 12B , Fig. 12C and Fig.12D Different examples of wake-up signaling are shown.
[0024] Fig.13A , Fig. 13B and Fig. 13C Different examples of monitoring timers for WUS, PDCCH and subsequent PDSCH are shown.
[0025] Fig.14 An example of a common DCI format structure with UE-specific fields is shown.
[0026] Fig.15 An example is shown where two UEs receive a GTS trigger in a GC-DCI, however each UE has a different DRX configuration.
[0027] Fig.16 An example of the structure of a group common DCI format including UE-specific fields and common fields is shown.
[0028] Fig.17 A flow chart showing an example of a process involving detecting network signaling and UE behavior before and after a DCI including a WUS is shown.
[0029] Fig.18 A block diagram showing an example of using a code multiplexing sequence to transmit control information.
[0030] Fig.19A , Fig.19B and Fig.19C Different examples of resource set mapping are shown.
[0031] Fig. 20 An example of a DRX related procedure is shown.
[0032] Like reference symbols in the various drawings indicate like elements. DETAILED DESCRIPTION
[0033] Figure 1 An example of a wireless communication system 100 is illustrated. For convenience and not limitation, the exemplary system 100 is described in the context of LTE and 5G NR communication standards defined by the 3rd Generation Partnership Project (3GPP) technical specifications. However, other types of communication standards are possible.
[0034] System 100 includes UE 101a and UE 101b (collectively referred to as "UE 101"). In this example, UE 101 is shown as a smartphone (eg, a handheld, touch-screen mobile computing device that can connect to one or more cellular networks). In other examples, any of the multiple UEs 101 may include other mobile computing devices or non-mobile computing devices, such as consumer electronic devices, cellular phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument clusters (ICs), heads-up display (HUD) devices, on-board diagnostic (OBD) devices, on-board mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, machine type communication (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, or combinations thereof, etc.
[0035] In some implementations, any of the UEs 101 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device using, for example, a public land mobile network (PLMN), a short-range service (ProSe), a device-to-device (D2D) communication, a sensor network, an IoT network, or a combination thereof. The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages or status updates) to facilitate connectivity to the IoT network.
[0036] The UE 101 is configured to be connected (e.g., communicatively coupled) to the RAN 110. The RAN 110 includes one or more RAN nodes 111a and 111b (collectively referred to as "RAN nodes 111"). In some implementations, the RAN 110 may be a next generation RAN (NGRAN), an evolved UMTS terrestrial radio access network (E-UTRAN), or a legacy RAN, such as a UMTS terrestrial radio access network (UTRAN) or a GSM EDGE radio access network (GERAN). As used herein, the term "NG RAN" may refer to the RAN 110 operating in a 5G NR system 100, while the term "E-UTRAN" may refer to the RAN 110 operating in an LTE or 4G system 100.
[0037] In order to connect to the RAN 110, multiple UEs 101 utilize connections (or channels) 103 and 104, respectively, each of which may include a physical communication interface or layer, as described below. In this example, connections 103 and 104 are shown as air interfaces to achieve communication coupling, and may be consistent with cellular communication protocols, such as global system for mobile communications (GSM) protocols, code division multiple access (CDMA) network protocols, push-to-talk (PTT) protocols, cellular PTT (POC) protocols, universal mobile telecommunications system (UMTS) protocols, 3GPP LTE protocols, 5G NR protocols, or combinations thereof, as well as other communication protocols.
[0038] The RAN 110 may include one or more RAN nodes 111a and 111b (collectively referred to as “RAN nodes 111”) that enable connections 103 and 104. As used herein, the terms “access node,” “access point,” and the like may describe equipment that provides radio baseband functionality for data or voice connections, or both, between a network and one or more users. These access nodes may be referred to as base stations (BS), gNodeBs, gNBs, eNodeBs, eNBs, NodeBs, RAN nodes, roadside units (RSUs), and the like, and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell), and the like. As used herein, the term “NGRAN node” may refer to a RAN node 111 (e.g., a gNB) operating in a 5G NR system 100, while the term “E-UTRAN node” may refer to a RAN node 111 (e.g., an eNB) operating in an LTE or 4G system 100. In some implementations, the RAN node 111 may be implemented as one or more of a dedicated physical device such as a macrocell base station, or a low power (LP) base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.
[0039] The RAN node 111 and the UE 101 may be configured for multiple-input and multiple-output (MIMO) communications, including single-beam or multi-beam communications. For example, the UE 101 may receive transmissions from one RAN node 111 at a time, or simultaneously from multiple RAN nodes 111. The RAN node 111 and the UE 101 may use beamforming for UL, DL, or both. For example, one or more RAN nodes 111 may transmit (Tx) beams to the UE 101, and the UE 101 may simultaneously receive data via one or more receive (Rx) beams. In some implementations, each of the RAN nodes 111 may be configured as a transmission and reception point (TRP). The RAN 110 may provide high-layer signaling for configuring beamforming, such as by providing transmission configuration indication (TCI) state configuration information.
[0040] Any of the RAN nodes 111 may serve as a termination point for the air interface protocol and may be the first point of contact for the UE 101. In some implementations, any of the RAN nodes 111 may perform various logical functions of the RAN 110, including but not limited to functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
[0041] In some implementations, multiple UEs 101 may be configured to communicate with each other or any of RAN nodes 111 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink communications), although the scope of the techniques described herein is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.
[0042] In some specific implementations, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 111 to the UE 101, while uplink transmissions may utilize similar techniques. The grid may be a frequency grid or a time-frequency grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element (RE). Each resource grid may include multiple resource blocks, which describe the mapping of certain physical channels to resource elements. A resource block (RB) may include a collection of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks may be used to transmit physical downlink channels and uplink channels. In some cases, an RB may be referred to as a physical resource block (PRB).
[0043] The RAN node 111 may transmit to the UE 101 via one or more DL channels. Various examples of DL communication channels include a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), and a physical downlink shared channel (PDSCH). The PDSCH may carry user data and higher layer signaling to multiple UEs 101. Other types of downlink channels are possible. The UE 101 may transmit to the RAN node 111 via one or more UL channels. Various examples of UL communication channels include a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH). Other types of uplink channels are possible. Devices such as the RAN node 111 and the UE 101 may transmit reference signals. Examples of reference signals include a sounding reference signal (SRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS or DM-RS), and a phase tracking reference signal (PTRS). Other types of reference signals are also possible.
[0044] A channel such as a PDCCH may convey different types of scheduling information for one or more downlink channels and uplink channels. Scheduling information may include downlink resource scheduling, uplink power control instructions, uplink resource grants, and indications for paging or system information. The RAN node 111 may transmit one or more downlink control information (DCI) messages on the PDCCH to provide scheduling information, such as the allocation of one or more PRBs. In some implementations, the DCI message transmits control information, such as a request for aperiodic CQI reporting, a UL power control command for a channel, and a notification of a slot format for a group of UEs 101. Downlink scheduling (e.g., allocating control and shared channel resource blocks to UE 101b within a cell) may be performed at any of the RAN nodes 111 based on channel quality information fed back from any of the UEs 101. Downlink resource allocation information may be sent on a PDCCH for (e.g., allocated to) a UE 101 or each UE in a group of UEs. In some implementations, the PDCCH carries information about transport formats and resource allocations related to a PDSCH channel, among other information. The PDCCH may also inform the UE 101 about transport format, resource allocation, and hybrid automatic repeat request (HARQ) information for providing HARQ feedback on uplink channels based on PDSCH reception.
[0045] In some implementations, the PDCCH uses control channel elements (CCEs) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quaternions, which may then be arranged using a sub-block interleaver for rate matching. In some implementations, one or more of these CCEs may be used to transmit each PDCCH, where each CCE may correspond to four sets of nine physical resource elements, collectively referred to as resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols may be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs may be used to transmit the PDCCH. In some implementations, there may be four or more different PDCCH formats defined with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).
[0046] Downlink and uplink transmissions may occur in one or more component carriers (CCs). One or more bandwidth part (BWP) configurations may be configured for each component carrier. In some implementations, the DL BWP includes at least one control resource set (CORESET). In some implementations, a CORESET includes one or more PRBs in the frequency domain and one or more OFDM symbols in the time domain. In some implementations, a channel such as a PDCCH may be transmitted via one or more CORESETs, where each CORESET corresponds to a set of time-frequency resources. CORESET information may be provided to the UE 101, and the UE 101 may monitor the time-frequency resources associated with one or more CORESETs to receive PDCCH transmissions.
[0047] The RAN nodes 111 are configured to communicate with each other using the interface 112. In an example, such as if the system 100 is an LTE system (eg, when the core network 120 is Figure 2 101 ), the interface 112 may be an X2 interface 112. The X2 interface may be defined between two or more RAN nodes 111 (e.g., two or more eNBs, etc.) connected to the EPC 120, or between two eNBs connected to the EPC 120, or both. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the primary eNB to the secondary eNB; information about successful in-sequence delivery of PDCP protocol data units (PDUs) from the secondary eNB to the UE 101 for user data; information about PDCP PDUs that were not delivered to the UE 101; information about the current minimum expected buffer size at the secondary eNB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, or user plane transmission control; load management function; inter-cell interference coordination function; and so on.
[0048] In some implementations, such as if system 100 is a 5G NR system (e.g., when core network 120 is Figure 3), the interface 112 may be an Xn interface 112. The Xn interface may be defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to the 5G core network 120, between a RAN node 111 (e.g., a gNB) and an eNB connected to the 5G core network 120, or between two eNBs connected to the 5G core network 120, or a combination of the above. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 101 in a connected mode (e.g., CM-CONNECTED), including functions for managing UE mobility in a connected mode between one or more RAN nodes 111; and the like. Mobility support may include context transfer from the old (source) serving RAN node 111 to the new (target) serving RAN node 111, and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (target) serving RAN node 111. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GPRS Tunneling Protocol (GTP-U) layer for carrying user plane PDUs on top of a user datagram protocol (UDP) or IP layer or both. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP or XnAP)) and a transport network layer built on a stream control transmission protocol (SCTP). SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack or the Xn-C protocol stack or both may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.
[0049] RAN 110 is shown as being communicatively coupled to a core network 120 (referred to as "CN 120"). CN 120 includes one or more network elements 122 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 101) connected to CN 120 using RAN 110. Components of CN 120 may be implemented in one physical node or separate physical nodes and may include components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some specific implementations, network function virtualization (NFV) may be used to virtualize some or all of the network node functions described herein using executable instructions stored in one or more computer-readable storage media, as will be described in further detail below. A logical instance of CN 120 may be referred to as a network slice, and a logical instance of a portion of CN 120 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, a NFV system may be used to perform virtual or reconfigurable implementations, or both, of one or more network components or functions.
[0050] The application server 130 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS packet service (PS) domain, LTE PS data services, etc.). The application server 130 may also be configured to support one or more communication services for the UE 101 using the CN 120 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.). The application server 130 may use the IP communication interface 125 to communicate with one or more network elements 122.
[0051] In some implementations, CN 120 may be a 5G core network (referred to as "5GC 120" or "5G core network 120"), and RAN 110 may be connected to CN 120 using a next generation interface 113. In some implementations, the next generation interface 113 may be divided into two parts: a next generation user plane (NG-U) interface 114, which carries traffic data between the RAN node 111 and the UPF (user plane function); and an S1 control plane (NG-C) interface 115, which is a signaling interface between the RAN node 111 and the access and mobility management function (AMF). Reference Figure 3 Discussing in more detail, CN 120 is an example of a 5G core network.
[0052] In some implementations, the CN 120 may be an EPC (referred to as “EPC 120” or the like), and the RAN 110 may be connected to the CN 120 using an S1 interface 113. In some implementations, the S1 interface 113 may be divided into two parts: an S1 user plane (S1-U) interface 114, which carries traffic data between the RAN node 111 and a serving gateway (S-GW); and an S1-MME interface 115, which is a signaling interface between the RAN node 111 and a mobility management entity (MME).
[0053] In some implementations, some or all of the RAN nodes 111 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a cloud RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). The CRAN or vBBUP may implement a RAN functional split, such as a packet data convergence protocol (PDCP) split, where the radio resource control (RRC) and PDCP layers are operated by the CRAN / vBBUP, and other layer 2 (e.g., data link layer) protocol entities are operated by individual RAN nodes 111; a medium access control (MAC) / physical layer (PHY) split, where the RRC, PDCP, MAC, and radio link control (RLC) layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 111; or a "lower PHY" split, where the RRC, PDCP, RLC, and MAC layers and the upper portion of the PHY layer are operated by the CRAN / vBBUP, and the lower portion of the PHY layer is operated by individual RAN nodes 111. The virtualization framework allows idle processor cores of the RAN node 111 to execute, for example, other virtualized applications. In some implementations, a single RAN node 111 may represent a single virtualized application using each F1 interface ( Figure 1 ) are connected to the gNB Central Unit (CU). In some implementations, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 4 ), and the gNB-CU may be operated by a server (not shown) located in the RAN 110 or by a server pool in a manner similar to the CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 111 may be a next generation eNB (ng-eNB), including a RAN node that provides E-UTRA user plane and control plane protocol terminals to the UE 101 and is connected to a 5G core network (e.g., the core network 120) using a next generation interface.
[0054] In a vehicle-to-everything (V2X) scenario, one or more of the RAN nodes 111 may be or act as an RSU. The term "roadside unit" or "RSU" refers to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on. In some specific implementations, the RSU is a computing device coupled to a radio frequency circuit located on the road side that provides connectivity support to a passing vehicle UE 101 (vUE 101). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications or other software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, and the like. In addition or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communications services. In addition or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) or provide connectivity to one or more cellular networks to provide uplink and downlink communications, or both. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network, or both.
[0055] Figure 2 FIG. 2 shows an exemplary architecture of a system 200 including a first CN 220. In this example, the system 200 may implement the LTE standard such that the CN 220 is a first CN 220 corresponding to the LTE standard. Figure 1 In addition, UE 201 can communicate with EPC 220 of CN 120. Figure 1 The UE 101 is the same as or similar to the UE 101, and the E-UTRAN 210 may be Figure 1 The CN 220 may be a RAN that is the same as or similar to the RAN 110 of the present invention and may include the RAN node 111 discussed previously. The CN 220 may include an MME 221, an S-GW 222, a PDN Gateway (P-GW) 223, a High Speed Packet Access (HSS) function 224, and a Serving GPRS Support Node (SGSN) 225.
[0056] The MME 221 may be similar in function to the control plane of a traditional SGSN, and may implement mobility management (MM) functions to keep track of the current location of the UE 201. The MME 221 may perform various mobility management processes to manage mobility aspects of the access, such as gateway selection and tracking area list management. Mobility management (also referred to as "EPSMM" or "EMM" in the E-UTRAN system) may refer to all applicable procedures, methods, data stores, etc. for maintaining knowledge of the current location of the UE 201, providing user identity confidentiality to users / subscribers, or performing other similar services, or a combination thereof, etc. Each UE 201 and the MME 221 may include an EMM sublayer, and when the attachment process is successfully completed, a mobility management context may be established in the UE 201 and the MME 221. The mobility management context may be a data structure or database object that stores mobility management related information of the UE 201. MME 221 may be coupled to HSS 224 using an S6a reference point, to SGSN 225 using an S3 reference point, and to S-GW 222 using an S11 reference point.
[0057] SGSN 225 may be a node that serves UE 201 by tracking the location of individual UE 201 and performing security functions. In addition, SGSN 225 may perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by MME 221; handling of UE 201 time zone functions, as specified by MME 221; and MME selection for handover to E-UTRAN 3GPP access network, etc. The S3 reference point between MME 221 and SGSN 225 may enable user and bearer information exchange for inter-3GPP access network mobility in an idle state or an active state or both.
[0058] The HSS 224 may include a database for network users, which includes subscription-related information for supporting network entities in handling communication sessions. The EPC 220 may include one or more HSSs 224, depending on the number of mobile users, the capacity of the equipment, the organization of the network, or a combination thereof. For example, the HSS 224 may provide support for routing, roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. The S6a reference point between the HSS 224 and the MEE 221 may enable the transmission of subscription and authentication data between the HSS 224 and the MEE 221 for authenticating or authorizing user access to the EPC 220.
[0059] The S-GW 222 may terminate the S1 interface 113 toward the RAN 210 ( Figure 2The S-GW 222 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies. The S11 reference point between the S-GW 222 and the MME 221 may provide a control plane between the MME 221 and the S-GW 222. The S-GW 222 may be coupled to the P-GW 223 using the S5 reference point.
[0060] The P-GW 223 may terminate the SGi interface toward the PDN 230. The P-GW 223 may utilize the IP communication interface 125 (see, e.g., Figure 1 ) routes data packets between EPC 220 and external networks such as a network including application server 130 (sometimes referred to as "AF"). In some implementations, P-GW 223 can utilize IP communication interface 125 (see, e.g., Figure 1 ) is communicatively coupled to an application server (e.g., Figure 1 Application server 130 or Figure 2 The S5 reference point between the P-GW 223 and the S-GW 222 may provide user plane tunneling and tunnel management between the P-GW 223 and the S-GW 222. The S5 reference point may also be used for S-GW 222 relocation due to the mobility of the UE 201 and whether the S-GW 222 needs to be connected to a non-colocated P-GW 223 for the required PDN connectivity. The P-GW 223 may also include nodes for policy implementation and charging data collection, such as a PCEF (not shown). In addition, the SGi reference point between the P-GW 223 and the packet data network (PDN) 230 may be an operator-external public, private PDN, or an internal operator packet data network, such as for providing IMS services. The P-GW 223 may be coupled to a policy control and charging rules function (PCRF) 226 using a Gx reference point.
[0061] PCRF 226 is a policy and charging control element of EPC 220. In a non-roaming scenario, there may be a single PCRF 226 in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of UE 201. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of UE 201: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in a visited public land mobile network (VPLMN). PCRF 226 may be communicatively coupled to application server 230 using P-GW 223. Application server 230 may signal PCRF 226 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. PCRF 226 may configure the rule to a PCEF (not shown) with an appropriate traffic flow template (TFT) and QoS class identifier (QCI), which initiates the QoS and charging specified by application server 230. The Gx reference point between PCRF 226 and P-GW 223 may allow for the transfer of QoS policies and charging rules from PCRF 226 to PCEF in P-GW 223. The Rx reference point may reside between PDN 230 (or "AF 230") and PCRF 226.
[0062] Figure 3 The architecture of a system 300 including a second CN 320 is shown. The system 300 is shown to include a UE 301, which may be the same or similar to the previously discussed UE 101 and UE 201; a RAN 310, which may be the same or similar to the previously discussed RAN 110 and RAN 210, and which may include the previously discussed RAN node 111; and a data network (DN) 303, which may be, for example, an operator service, Internet access, or a 3rd party service; and a 5GC 320. The 5GC 320 may include an authentication server function (AUSF) 322; an access and mobility management function (AMF) 321; a session management function (SMF) 324; a network exposure function (NEF) 323; a policy control function (PCF) 326; a network repository function (NRF) 325; a unified data management (UDM) function 327; an AF 328; a user plane function (UPF) 302; and a network slice selection function (NSSF) 329.
[0063] UPF 302 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with DN 303, and a branch point to support multi-host PDU sessions. UPF 302 may also perform packet routing and forwarding, perform packet inspection, perform the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement) on the user plane, perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 302 may include an uplink classifier to support routing traffic flows to data networks. DN 303 may represent various network operator services, Internet access, or third-party services. DN 303 may include or be similar to the application server 130 discussed previously. UPF 302 may interact with SMF 324 using the N4 reference point between SMF 324 and UPF 302.
[0064] AUSF 322 stores data for authentication of UE 301 and handles authentication-related functions. AUSF 322 may facilitate a common authentication framework for various access types. AUSF 322 may communicate with AMF 321 using the N12 reference point between AMF 321 and AUSF 322, and may communicate with UDM 327 using the N13 reference point between UDM 327 and AUSF 322. In addition, AUSF 322 may present an interface based on Nausf services.
[0065] AMF 321 is responsible for registration management (e.g., responsible for registering UE 301, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, as well as access authentication and authorization. AMF 321 can be the termination point of the N11 reference point between AMF 321 and SMF 324. AMF 321 can provide transmission of SM messages between UE 301 and SMF 324, and act as a transparent agent for routing SM messages. AMF 321 can also provide UE 301 and SMSF ( Figure 3301). The AMF 321 may act as a security anchor function (SEAF), which may include interaction with the AUSF 322 and the UE 301 to, for example, receive intermediate keys established as a result of the UE 301 authentication process. In the case of using universal user identity module (UMTS)-based authentication, the AMF 321 may retrieve security materials from the AUSF 322. The AMF 321 may also include a security context management (SCM) function that receives keys from the SEAF to derive access network specific keys. In addition, the AMF 321 may be a termination point for the RAN control plane interface, which may include or be an N2 reference point between the RAN 310 and the AMF 321. In some specific implementations, the AMF 321 may be a termination point for NAS (N1) signaling and perform NAS encryption and integrity protection.
[0066] The AMF 321 may also support NAS signaling with the UE 301 over an N3 interworking function (IWF) interface (referred to as "N3IWF"). The N3IWF may be used to provide access to untrusted entities. The N3IWF may be the termination point for the N2 interface between the RAN 310 and the AMF 321 for the control plane, and may be the termination point for the N3 reference point between the RAN 310 and the UPF 302 for the user plane. Thus, the AMF 321 may process N2 signaling for PDU sessions and QoS from the SMF 324 and the AMF 321, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and perform QoS corresponding to N3 packet markings, taking into account QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 301 and the AMF 321 using the N1 reference point between the UE 301 and the AMF 321, and relay uplink and downlink user plane packets between the UE 301 and the UPF 302. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 301. The AMF 321 may present an interface based on the Namf service, and may be an N14 reference point between the two AMFs 321 and an N14 reference point between the AMF 321 and the 5G Equipment Identity Register (EIR) ( Figure 3 The termination point of the N17 reference point between the two (not shown).
[0067] UE 301 may register with AMF 321 in order to receive network services. Registration Management (RM) is used to register UE 301 with the network (e.g., AMF 321) or deregister UE 301, and to establish a UE context in the network (e.g., AMF 321). UE 301 may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM DEREGISTERED state, UE 301 is not registered with the network, and the UE context in AMF 321 does not maintain valid location or routing information of UE 301, so AMF 321 cannot reach UE 301. In the RM REGISTERED state, UE 301 is registered with the network, and the UE context in AMF 321 may maintain valid location or routing information of UE 301, so AMF 321 may reach UE 301. In the RM-REGISTERED state, UE 301 may perform a mobility registration update procedure, perform a periodic registration update procedure triggered by expiration of a periodic update timer (e.g., to notify the network that UE 301 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.
[0068] AMF 321 may store one or more RM contexts for UE 301, each RM context being associated with a specific access to the network. The RM context may be, for example, a data structure or a database object, etc., which indicates or stores the registration status and periodic update timer for each access type. AMF 321 may also store a 5GC mobility management (MM) context that may be the same or similar to the (E)MM context discussed previously. In some specific implementations, AMF 321 may store coverage enhancement mode B restriction parameters for UE 301 in an associated MM context or RM context. AMF 321 may also derive values from the UE's usage setting parameters already stored in the UE context (and / or MM / RM context) when necessary.
[0069] Connection Management (CM) may be used to establish and release a signaling connection between the UE 301 and the AMF 321 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 301 and the CN 320, and includes a signaling connection between the UE and the AN (e.g., an RRC connection or a UE-N3IWF connection for non-3GPP access) and an N2 connection of the UE 301 between the AN (e.g., RAN 310) and the AMF 321. In some implementations, the UE 301 may operate in one of two CM modes (CM-IDLE mode or CM-CONNECTED mode). When the UE 301 operates in the CM-IDLE mode, the UE 301 may not have a NAS signaling connection established with the AMF 321 over the N1 interface, and there may be a RAN 310 signaling connection for the UE 301 (e.g., an N2 or N3 connection or both). When the UE 301 operates in the CM-CONNECTED mode, the UE 301 may have a NAS signaling connection established with the AMF 321 through the N1 interface, and there may be a RAN 310 signaling connection (e.g., N2 and / or N3 connection) for the UE 301. Establishing an N2 connection between the RAN 310 and the AMF 321 may cause the UE 301 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the RAN 310 and the AMF 321 is released, the UE 301 may transition from the CM-CONNECTED mode to the CM-IDLE mode.
[0070] SMF 324 may be responsible for session management (SM), such as session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes; UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering at UPF to route traffic to the correct destination; terminating the interface toward the policy control function; control portion of policy enforcement and QoS; lawful interception (for SM events and interface with LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN via N2 using AMF; and determining the SSC mode of the session. SM may refer to the management of a PDU session, and a PDU session (or "session") may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 301 and a data network (DN) 303 identified by a data network name (DNN). The PDU session may be established upon request by UE 301, modified upon request by UE 301 and 5GC 320, and released upon request by UE 301 and 5GC 320 using NAS SM signaling exchanged between UE 301 and SMF 324 over the N1 reference point. Upon request from an application server, 5GC 320 may trigger a specific application in UE 301. In response to receiving a trigger message, UE 301 may deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 301. The identified applications in UE 301 may establish a PDU session to a specific DNN. SMF 324 may check whether the UE 301 request complies with user subscription information associated with UE 301. In this regard, SMF 324 may retrieve and / or request to receive update notifications about SMF 324 level subscription data from UDM 327.
[0071] The SMF 324 may include some or all of the following roaming functions: handling local execution to apply QoS service level agreements (SLAs) (e.g., in a VPLMN); charging data collection and charging interfaces (e.g., in a VPLMN); lawful interception (e.g., SM events and interfaces with LI systems in a VPLMN); and supporting interaction with external DNs to transport signaling for PDU session authorization / authentication through external DNs. An N16 reference point between two SMFs 324 may be included in the system 300, which in a roaming scenario may be between another SMF 324 in a visited network and an SMF 324 in a home network. In addition, the SMF 324 may present an interface based on Nsmf services.
[0072] NEF 323 may provide components for securely exposing services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, application functions (e.g., AF 328), edge computing or fog computing systems, etc. In some specific implementations, NEF 323 may authenticate, authorize and / or throttle AF. NEF 323 may also convert information exchanged with AF 328 and information exchanged with internal network functions. For example, NEF 323 may convert between AF service identifiers and internal 5GC information. NEF 323 may also receive information from other network functions (NFs) based on their exposure capabilities. The information may be stored at NEF 323 as structured data or at a data storage NF using a standardized interface. The stored information may then be re-exposed to other NFs and AFs by NEF 323, or used for other purposes such as analysis, or both. In addition, NEF 323 may present an interface based on Nnef services.
[0073] NRF 325 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information about discovered NF instances to NF instances. NRF 325 also maintains information about available NF instances and services supported by these instances. As used herein, the term "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, which may occur, for example, during the execution of a program code. In addition, NRF 325 may present an interface based on Nnrf services.
[0074] PCF 326 may provide for control plane functions to enforce their policy rules, and may also support a unified policy framework for managing network behavior. PCF 326 may also implement a front end to access subscription information related to policy decisions in the unified data repository (UDR) of UDM 327. PCF 326 may communicate with AMF 321 using the N15 reference point between PCF 326 and AMF 321, which may include PCF 326 in a visited network and AMF 321 in a roaming scenario. PCF 326 may communicate with AF 328 using the N5 reference point between PCF 326 and AF 328; and communicate with SMF 324 using the N7 reference point between PCF 326 and SMF 324. System 300 or CN320 or both may also include an N24 reference point between PCF 326 (in the home network) and PCF 326 in the visited network. In addition, PCF 326 may present an interface based on Npcf services.
[0075] UDM 327 may process subscription-related information to support network entities in handling communication sessions, and may store subscription data for UE 301. For example, subscription data may be transferred between UDM 327 and AMF 321 using the N8 reference point between UDM 327 and AMF. UDM 327 may include two parts: an application front end and a UDR ( Figure 3 The front end and UDR are not shown). The UDR may store subscription data and policy data of the UDM 327 and PCF 326, or structured data for exposure and application data (including PFD for application detection, application request information of multiple UEs 301) of the NEF 323, or both. The Nudr service-based interface may be presented by the UDR 221 to allow the UDM 327, PCF 326, and NEF 323 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in the UDR. The UDM may include a UDM front end, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different front ends may serve the same user. The UDM front end accesses the subscription information stored in the UDR, and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. The UDR may interact with the SMF 324 using the N10 reference point between the UDM 327 and the SMF 324. UDM 327 may also support SMS management, where the SMS front end implements application logic similar to that discussed previously. Additionally, UDM 327 may present an interface based on Nudm services.
[0076] AF 328 can provide the influence of applications on traffic routing, provide access to network capability exposure (NCE), and interact with the policy framework for policy control. NCE can be a mechanism that allows 5GC320 and AF 328 to provide information to each other using NEF 323, which can be used for edge computing implementation. In such implementations, network operators and third-party services can be hosted near the UE 301 access point of the attachment to achieve effective service delivery through reduced end-to-end delay and load on the transmission network. For edge computing implementation, 5GC can select UPF 302 near UE 301 and perform traffic steering from UPF 302 to DN 303 using the N6 interface. This can be based on UE subscription data, UE location and information provided by AF 328. In this way, AF 328 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 328 is considered a trusted entity, the network operator can allow AF 328 to interact directly with the relevant NF. In addition, AF328 can present an interface based on Naf services.
[0077] NSSF 329 may select a set of network slice instances to serve UE 301. If necessary, NSSF 329 may also determine the allowed NSSAI and the mapping to the subscribed single network slice selection assistance information (S-NSSAI). NSSF 329 may also determine a set of AMFs to serve UE 301, or a list of candidate AMFs 321, based on appropriate configuration and possibly by querying NRF 325. The selection of a set of network slice instances for UE 301 may be triggered by AMF 321, where UE 301 registers by interacting with NSSF 329, which may cause AMF 321 to change. NSSF 329 may interact with AMF 321 using the N22 reference point between AMF 321 and NSSF 329; and may utilize the N31 reference point ( Figure 3 The NSSF 329 may communicate with another NSSF 329 in the visited network (not shown). In addition, the NSSF 329 may present an interface based on the Nnssf service.
[0078] As previously discussed, CN 320 may include SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to or from UE 301 to or from other entities, such as SMS-GMSC / IWMSC / SMS routers. SMS may also interact with AMF 321 and UDM 327 for notification procedures that UE 301 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 327 when UE 301 is available for SMS).
[0079] In some implementations, there may be additional or alternative reference points or service-based interfaces, or both, between network function services in a network function. However, for clarity, Figure 3 These interfaces and reference points are omitted. In one example, CN 320 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 221) and an AMF 321, so as to achieve intercommunication between CN 320 and CN 220. Other exemplary interfaces or reference points may include an interface based on N5g-EIR services presented by 5G-EIR, an N27 reference point between an NRF in a visited network and an NRF in a home network, or an N31 reference point between an NSSF in a visited network and an NSSF in a home network, etc.
[0080] In some implementations, the components of CN 220 may be implemented in one physical node or separate physical nodes and may include components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, the components of CN 320 may be implemented in the same or similar manner as discussed herein with respect to the components of CN 220. In some implementations, NFV is used to virtualize any or all of the above-mentioned network node functions using executable instructions stored in one or more computer-readable storage media, as described in further detail below. The logical instantiation of CN 220 may be referred to as a network slice, and each logical instantiation of CN 220 may provide specific network capabilities and network characteristics. The logical instantiation of a portion of CN 220 may be referred to as a network sub-slice, which may include P-GW 223 and PCRF 226.
[0081] As used herein, the terms "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the concrete occurrence of an object, which may occur, for example, during the execution of program code. A network instance may refer to information identifying a domain, which may be used for traffic detection and routing in different IP domains or in the case of overlapping IP addresses. A network slice instance may refer to a set of network function (NF) instances and the resources (e.g., computing, storage, and network resources) required to deploy a network slice.
[0082] Regarding 5G systems (see e.g. Figure 3 ), a network slice may include a RAN part and a CN part. Support for network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. The network can implement different network slices by scheduling or by providing different L1 / L2 configurations or both. If provided by NAS, the UE 301 provides auxiliary information for network slice selection in an appropriate RRC message. Although the network can support a large number of slices, in some specific implementations the UE does not need to support more than 8 slices at the same time.
[0083] The network slice may include the CN 320 control plane and user plane NF, the NG-RAN 310 in the serving PLMN, and the N3IWF function in the serving PLMN. Each network slice may have a different S-NSSAI or a different SST, or both. The NSSAI includes one or more S-NSSAIs, and each network slice is uniquely identified by the S-NSSAI. The network slices may be different for supported features and network function optimizations. In some specific implementations, multiple network slice instances may deliver the same service or feature, but for different groups of UEs 301 (e.g., enterprise users). For example, each network slice may deliver different committed services or may be dedicated to a specific customer or enterprise, or both. In this example, each network slice may have a different S-NSSAI with the same SST but with a different slice differentiator. In addition, a single UE may be served simultaneously by one or more network slice instances using a 5G AN, and the UE may be associated with eight different S-NSSAIs. In addition, an AMF 321 instance serving a single UE 301 may belong to each network slice instance serving the UE.
[0084] Network slicing in NG-RAN 310 involves RAN slice awareness. RAN slice awareness includes differentiated handling of traffic for different network slices that have been pre-configured. Slice awareness in NG-RAN 310 is introduced at the PDU session level by indicating the S-NSSAI corresponding to the PDU session in all signaling including PDU session resource information. How NG-RAN 310 supports enabling slices in terms of NG-RAN functions (e.g., a set of network functions including each slice) depends on the specific implementation. NG-RAN310 selects the RAN part of the network slice using auxiliary information provided by UE 301 or 5GC 320, which explicitly identifies one or more network slices in the pre-configured network slices in the PLMN. NG-RAN 310 also supports resource management and policy enforcement between slices according to SLA. A single NG-RAN node can support multiple slices, and NG-RAN310 can also appropriately apply appropriate RRM policies for SLA to each supported slice. NG-RAN 310 can also support QoS differentiation within a slice.
[0085] The NG-RAN 310 may also use the UE assistance information to select an AMF 321 during the initial attach, if available. The NG-RAN 310 routes the initial NAS to the AMF 321 using the assistance information. If the NG-RAN 310 cannot select an AMF 321 using the assistance information, or the UE 301 does not provide any such information, the NG-RAN 310 sends the NAS signaling to a default AMF 321, which may be in the AMF 321 pool. For subsequent access, the UE 301 provides a temporary ID assigned to the UE 301 by the 5GC 320 to enable the NG-RAN 310 to route the NAS message to the appropriate AMF 321, as long as the temporary ID is valid. The NG-RAN 310 knows and can reach the AMF 321 associated with the temporary ID. Otherwise, the method for initial attach applies.
[0086] The NG-RAN 310 supports resource isolation between slices. NG-RAN 310 resource isolation can be achieved through RRM policies and protection mechanisms that should avoid starvation of shared resources in the case where one slice disrupts the service level agreement of another slice. In some implementations, NG-RAN 310 resources can be fully assigned to a slice. How the NG-RAN 310 supports resource isolation depends on the specific implementation.
[0087] Some slices may be only partially available in the network. The NG-RAN 310 is aware of slices supported in its neighboring cells that may be beneficial for inter-frequency mobility in connected mode. Slice availability may not change within the registration area of the UE. The NG-RAN 310 and 5GC 320 are responsible for handling service requests for slices that may or may not be available in a given area. Granting or denying access to a slice may depend on factors such as support for the slice, availability of resources, and support of the requested service by the NG-RAN 310.
[0088] UE 301 may be associated with multiple network slices simultaneously. In the case where UE 301 is associated with multiple slices simultaneously, only one signaling connection is maintained and for intra-frequency cell reselection, UE 301 attempts to camp on the best cell. For inter-frequency cell reselection, dedicated priorities may be used to control the frequency that UE 301 camps on. 5GC 320 will verify that UE 301 has the right to access the network slice. Knowing the specific slice that UE 301 is requesting access to before receiving the Initial Context Setup Request message may allow NG-RAN 310 to apply some temporary or local policies. During the Initial Context Setup, NG-RAN 310 is informed of the slice whose resources are being requested.
[0089] Figure 4 An example of infrastructure equipment 400 is shown. Infrastructure equipment 400 (or "system 400") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 111 shown and described previously), an application server 130, or any other component or device discussed herein. In other examples, system 400 can be implemented in or by a UE.
[0090] System 400 includes: application circuit 405, baseband circuit 410, one or more radio front end modules (RFEM) 415, memory circuit 420, power management integrated circuit (PMIC) 425, power tee circuit 430, network controller circuit 435, network interface connector 440, satellite positioning circuit 445 and user interface circuit 450. In some implementations, system 400 may include additional elements such as, for example, memory, storage, display, camera, one or more sensors or input / output (I / O) interfaces or combinations thereof. In other examples, the components described with reference to system 400 may be included in more than one device. For example, various circuits may be separately included in more than one device for CRAN, vBBU or other implementations.
[0091] The application circuit 405 may include circuits such as, but not limited to, one or more processors (or processor cores), cache memory, one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C or a general programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, a general input / output (I / O or IO), a memory card controller such as a secure digital (SD) multimedia card (MMC), a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor (or core) of the application circuit 405 may be coupled to or may include a memory or storage element, and may be configured to execute instructions stored in the memory or storage element to enable various applications or operating systems to run on the system 400. In some implementations, the memory or storage element may include on-chip memory circuitry that may include any suitable volatile or nonvolatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, or combinations thereof as well as other types of memory.
[0092] The processor of the application circuit 405 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or a combination thereof, etc. In some specific implementations, the application circuit 405 may include or may be a dedicated processor or controller configured to perform the various techniques described herein. In some specific implementations, the system 400 may not utilize the application circuit 405, and may instead include a dedicated processor or controller to process, for example, IP data received from the EPC or 5GC.
[0093] In some implementations, the application circuit 405 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. The one or more hardware accelerators may include, for example, computer vision (CV) or deep learning (DL) accelerators or both. In some implementations, the programmable processing device may be: one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs), etc.; programmable logic devices (PLDs), such as complex PLDs (CPLDs) or high capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs), or combinations thereof, etc. In such implementations, the circuits of the application circuit 405 may include logic blocks or logic architectures, as well as other interconnected resources that can be programmed to perform various functions such as the processes, methods, functions described herein. In some implementations, the circuitry of application circuit 405 may include a memory unit (e.g., an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a static memory (e.g., a static random access memory (SRAM) or an antifuse)) for storing logic blocks, logic structures, data, or other data in a lookup table (LUT) or the like.
[0094] The user interface circuit 450 may include one or more user interfaces designed to enable a user to interact with the system 400 or a peripheral component interface designed to enable a peripheral component to interact with the system 400. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touch pad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, or a combination thereof, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.
[0095] The radio front end module (RFEM) 415 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., Figure 6 The baseband circuit 410 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.
[0096] The memory circuit 420 may include one or more of the following: a volatile memory, such as a dynamic random access memory (DRAM) or a synchronous dynamic random access memory (SDRAM); and a non-volatile memory (NVM), such as a high-speed electrically erasable memory (commonly referred to as flash memory), a phase change random access memory (PRAM), or a magnetoresistive random access memory (MRAM), or a combination thereof, etc. For example, the memory circuit 420 may be implemented as one or more of the following: a solder-in packaged integrated circuit, a socketed memory module, and a plug-in memory card.
[0097] The PMIC 425 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 430 may provide power extracted from the network cable to provide both power and data connections for the infrastructure equipment 400 using a single cable.
[0098] The network controller circuit 435 may provide connectivity to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on Multi-Protocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to and from the infrastructure equipment 400 using a network interface connector 440 using a physical connection, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 435 may include one or more dedicated processors or FPGAs, or both, for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuit 435 may include multiple controllers for providing connectivity to other networks using the same or different protocols.
[0099] The positioning circuit 445 includes circuits for receiving and decoding signals transmitted or broadcast by a positioning network of a global navigation satellite system (GNSS). Examples of GNSS include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's Beidou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS) for navigation), etc. The positioning circuit 445 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some specific implementations, the positioning circuit 445 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking and estimation without GNSS assistance. The positioning circuit 445 may also be part of or interact with the baseband circuit 410 or the RFEM 415 or both to communicate with nodes and components of the positioning network. The positioning circuit 445 may also provide data (e.g., location data, time data) to the application circuit 405, which may use the data to synchronize operations with various infrastructures (e.g., RAN node 111, etc.).
[0100] Figure 5An example of a platform 500 (or "device 500") is shown. In some implementations, the computer platform 500 may be suitable for use as a UE 101, 201, 301, an application server 130, or any other component or device discussed herein. The platform 500 may include any combination of components shown in the example. The components (or portions thereof) of the platform 500 may be implemented as integrated circuits (ICs), discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted in the computer platform 500, or as components otherwise incorporated within the chassis of a larger system. Figure 5 The block diagram is intended to show a high-level view of the components of platform 500. However, in some implementations, platform 500 may include fewer, additional, or alternative components, or Figure 5 Different arrangements of components are shown.
[0101] The application circuit 505 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more LDOs, interrupt controllers, serial interfaces (such as SPI), I2C or general programmable serial interface modules, RTCs, timer-counters (including interval timers and watchdog timers), general I / Os, memory card controllers (such as SD MMC or similar controllers), USB interfaces, MIPI interfaces, and JTAG test access ports. The processor (or core) of the application circuit 505 may be coupled to or may include a memory / storage element, and may be configured to execute instructions stored in the memory or storage device to enable various applications or operating systems to run on the system 500. In some specific implementations, the memory or storage element may be an on-chip memory circuit, which may include any suitable volatile memory or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, or combinations thereof, as well as other types of memory.
[0102] The processor of the application circuit 505 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some specific implementations, the application circuit 405 may include or may be a dedicated processor / controller for performing the techniques described herein. In some specific implementations, the application circuit 505 may be part of a system on a chip (SoC), in which the application circuit 505 and other components are formed as a single integrated circuit or a single package.
[0103] In some implementations, the application circuit 505 may include: circuits, such as but not limited to one or more field programmable devices (FPDs) such as FPGAs; PLDs such as CPLDs, HCPLDs; ASICs such as structured ASICs; PSoCs or combinations thereof, etc. In some implementations, the application circuit 505 may include logic blocks or logic structures, and other interconnected resources that can be programmed to perform various functions such as the processes, methods, functions described herein. In some implementations, the application circuit 505 may include memory cells, such as EPROMs, EEPROMs, flash memory, static memory (such as SRAM or anti-fuse) for storing logic blocks, logic structures, data or other data in LUTs, etc.
[0104] Baseband circuit 510 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Figure 6 The various hardware electronic components of baseband circuit 510 are discussed.
[0105] The RFEM 515 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave RFICs. In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., Figure 6 The antenna array 611 of the platform 500 may be connected to a plurality of antennas. In some implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical RFEM 515 that combines both millimeter wave antennas and sub-millimeter wave. In some implementations, the RFEM 515, the baseband circuit 510, or both are included in the transceiver of the platform 500.
[0106] The memory circuit 520 may include any number and type of memory devices for providing a quantitative system memory. For example, the memory circuit 520 may include one or more of volatile memory (such as RAM, DRAM, or SDRAM) and NVM (such as high-speed electrically erasable memory (commonly referred to as flash memory), PRAM, or MRAM), or a combination thereof, etc. In a low-power implementation, the memory circuit 520 may be an on-chip memory or register associated with the application circuit 505. In order to provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 520 may include one or more mass storage devices, which may include, for example, a solid-state drive (SSD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory, etc.
[0107] The removable memory circuit 523 may include a device, circuit, housing, case, port or socket, etc. for coupling a portable data storage device to the platform 500. These portable data storage devices may be used for mass storage and may include, for example, a flash memory card (e.g., a secure digital (SD) card, a micro SD card, an xD picture card), as well as a USB flash drive, an optical disk, or an external HDD or a combination thereof, etc. The platform 500 may also include an interface circuit (not shown) for connecting an external device to the platform 500. External devices connected to the platform 500 using the interface circuit include a sensor circuit 521 and an electromechanical component (EMC) 522, as well as a removable memory device coupled to the removable memory circuit 523.
[0108] Sensor circuit 521 includes a device, module, or subsystem that is intended to detect events or changes in its environment and send information about the detected events (e.g., sensor data) to one or more other devices, modules, or subsystems. Examples of such sensors include: an inertial measurement unit (IMU), such as an accelerometer, gyroscope, or magnetometer; a microelectromechanical system (MEMS) or nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other audio capture device, or a combination thereof, etc.
[0109] The EMC 522 includes devices, modules or subsystems that are intended to enable the platform 500 to change its state, position, or orientation or to move or control a mechanism, system or subsystem. In addition, the EMC 522 may be configured to generate messages or signaling and send messages or signaling to other components of the platform 500 to indicate the current state of the EMC 522. Examples of EMC 522 include one or more power switches, relays (such as electromechanical relays (EMRs) or solid-state relays (SSRs)), actuators (e.g., valve actuators), audible sound generators, visual warning devices, motors (e.g., DC motors or stepper motors), wheels, thrusters, propellers, claws, clamps, hooks, or combinations thereof, in addition to other electromechanical components. In some specific implementations, the platform 500 is configured to operate one or more EMCs 522 based on one or more capture events, instructions or control signals received from a service provider or a client or both.
[0110] In some specific implementations, the interface circuit can connect the platform 500 with the positioning circuit 545. The positioning circuit 545 includes a circuit for receiving and decoding signals transmitted or broadcast by the positioning network of the GNSS. The positioning circuit 545 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communication) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some specific implementations, the positioning circuit 545 may include a micro PNT IC that uses a master timing clock to perform position tracking or estimation without GNSS assistance. The positioning circuit 545 can also be a part of the baseband circuit 510 or RFEM515 or both or interact with it to communicate with nodes and components of the positioning network. The positioning circuit 545 can also provide data (e.g., position data, time data) to the application circuit 505, which can use the data to synchronize operations with various infrastructures (e.g., radio base stations) for turn-by-turn navigation applications, etc.
[0111] In some implementations, the interface circuit may connect the platform 500 with a near field communication (NFC) circuit 540. The NFC circuit 540 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, wherein magnetic field induction is used to enable communication between the NFC circuit 540 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 500. The NFC circuit 540 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip or IC that provides NFC functionality to the NFC circuit 540 by executing an NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 540, or initiate data transfer between the NFC circuit 540 and another active NFC device (e.g., a smart phone or an NFC-enabled POS terminal) close to the platform 500.
[0112] The driver circuit 546 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 500. The driver circuit 546 may include various drivers to allow other components of the platform 500 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 500. For example, the driver circuit 546 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 500, a sensor driver for obtaining sensor readings of the sensor circuit 521 and controlling and allowing access to the sensor circuit 521, an EMC driver for obtaining an actuator position of the EMC 522 or controlling and allowing access to the EMC 522, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.
[0113] A power management integrated circuit (PMIC) 525 (also referred to as “power management circuit 525”) may manage power provided to various components of the platform 500. Specifically, the PMIC 525 may control power selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 510. The PMIC 525 may be included when the platform 500 is capable of being powered by a battery 530, for example, when the device is included in a UE 101, 201, 301.
[0114] In some implementations, the PMIC 525 may control or otherwise be part of various power saving mechanisms of the platform 500. For example, if the platform 500 is in the RRC_CONNECTED state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as the DRX state. During this state, the platform 500 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for a longer period of time, the platform 500 may transition to the RRC_IDLE state, in which it is disconnected from the network and does not perform operations such as channel quality feedback or handover. This may allow the platform 500 to enter a very low power state in which it periodically wakes up to listen to the network and then powers off again. In some implementations, the platform 500 may not receive data in the RRC_IDLE state, but must transition back to the RRC_CONNECTED state to receive data. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device may not be able to connect to the network and may lose power completely. Any data sent during this time may be significantly delayed, and it is assumed that the delay is acceptable.
[0115] The battery 530 can power the platform 500, but in some implementations, the platform 500 can be deployed in a fixed location and can have a power source coupled to a power grid. The battery 530 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, or a lithium-air battery, etc. In some implementations, such as in V2X applications, the battery 530 can be a typical lead-acid car battery.
[0116] In some implementations, the battery 530 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 500 to track the state of charge (SoCh) of the battery 530. The BMS may be used to monitor other parameters of the battery 530, such as the state of health (SoH) and state of function (SoF) of the battery 530 to provide fault prediction. The BMS may transmit information about the battery 530 to the application circuit 505 or other components of the platform 500. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 505 to directly monitor the voltage of the battery 530 or the current from the battery 530. The battery parameters may be used to determine actions that the platform 500 may perform, such as transmission frequency, network operation, sensing frequency, etc.
[0117] The user interface circuit 550 includes various input / output (I / O) devices present in or connected to the platform 500, and includes one or more user interfaces designed to implement user interaction with the platform 500 or peripheral component interfaces designed to implement interaction with peripheral components of the platform 500. The user interface circuit 550 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, or a headset, or a combination thereof, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other information). The output device circuitry may include any number or combination of audio or visual displays, including one or more simple visual outputs or indicators (e.g., binary state indicators (e.g., light emitting diodes (LEDs)), multi-character visual outputs, or more complex outputs, such as a display device or touch screen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, or a projector), where the output of characters, graphics, or multimedia objects is generated or produced by the operation of the platform 500. The output device circuitry may also include a speaker or other audio emitting device, or a printer. In some implementations, the sensor circuitry 521 may be used as an input device circuitry (e.g., an image capture device, or a motion capture device) and one or more EMCs may be used as an output device circuitry (e.g., an actuator for providing tactile feedback). In another example, an NFC circuit may be included to read an electronic tag or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a USB port, an audio jack, or a power interface.
[0118] Figure 6 6 and 615. The baseband circuit 610 may correspond to Figure 4 The baseband circuit 410 and Figure 5 The baseband circuit 510 of FIG. RFEM 615 may correspond to Figure 4 RFEM415 and Figure 5 RFEM 515. As shown, RFEM 615 may include radio frequency (RF) circuit 606, front end module (FEM) circuit 608, and antenna array 611 coupled together. In some implementations, RFEM 615, baseband circuit 610, or both are included in a transceiver.
[0119] The baseband circuitry 610 includes circuitry configured to execute various radio or network protocols and control functions that enable communication with one or more radio networks using the RF circuitry 606. The radio control functions may include, but are not limited to, signal modulation and demodulation, encoding and decoding, and radio frequency shifting. In some implementations, the modulation and demodulation circuitry of the baseband circuitry 610 may include fast Fourier transform (FFT), precoding, or constellation mapping and demapping functions. In some implementations, the encoding and decoding circuitry of the baseband circuitry 610 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder and decoder functions. The modulation and demodulation and encoder and decoder functions are not limited to these examples and may include other suitable functions in other examples. The baseband circuitry 610 is configured to process baseband signals received from the receive signal path of the RF circuitry 606 and to generate baseband signals for the transmit signal path of the RF circuitry 606. The baseband circuitry 610 is configured to communicate with application circuitry (e.g., Figure 4 and Figure 5 4 and 505) to generate and process baseband signals and control the operation of RF circuitry 606. Baseband circuitry 610 may handle various radio control functions.
[0120] The aforementioned circuits and control logic components of the baseband circuit 610 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 604A, a 4G or LTE baseband processor 604B, a 5G or NR baseband processor 604C, or some other baseband processors 604D for other existing generations, generations under development or generations to be developed in the future (e.g., the sixth generation (6G)). In some specific implementations, some or all of the functions of the baseband processors 604A-604D may be included in a module stored in the memory 604G and executed using one or more processors such as a central processing unit (CPU) 604E. In some specific implementations, some or all of the functions of the baseband processors 604A-604D may be provided as a hardware accelerator (e.g., FPGA or ASIC) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In some implementations, the memory 604G may store program code of a real-time OS (RTOS), which, when executed by the CPU 604E (or other processor), is used to enable the CPU 604E (or other processor) to manage resources, schedule tasks, or perform other operations of the baseband circuit 610. In some implementations, the baseband circuit 610 includes one or more audio digital signal processors (DSPs) 604F. The audio DSP 604F may include elements for compression and decompression and echo cancellation, and may include other suitable processing elements in some implementations.
[0121] In some implementations, each of processors 604A-604E includes a corresponding memory interface to send data to and receive data from memory 604G. Baseband circuit 610 may also include one or more interfaces for communicatively coupling to other circuits or devices, such as an interface for sending data to and receiving data from a memory external to baseband circuit 610; an interface for sending data to and receiving data from a memory external to the baseband circuit; Figure 4 and Figure 5 The application circuit interface for sending data to the application circuit 405, 505 and receiving data from the application circuit; Figure 6 RF circuit 606 to send data and receive data from the RF circuit; an RF circuit interface for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, A wireless hardware connection interface for sending data to and receiving data from wireless hardware elements (such as low-power components, Wi-Fi components, etc.); and a power management interface for sending power or control signals to and receiving power or control signals from the PMIC 525.
[0122] In some specific implementations (which may be combined with the above examples), the baseband circuit 610 includes one or more digital baseband systems, which are coupled to each other and to the CPU subsystem, the audio subsystem, and the interface subsystem using an interconnection subsystem. The digital baseband subsystem may also be coupled to the digital baseband interface and the mixed signal baseband subsystem using another interconnection subsystem. Each of the interconnection subsystems may include a bus system, a point-to-point connection, a network on chip (NOC) structure, or some other suitable bus or interconnection technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, etc. In some specific implementations, the baseband circuit 610 may include a protocol processing circuit having one or more control circuit instances (not shown) to provide control functions to the digital baseband circuit or the radio frequency circuit (e.g., the radio front end module 615).
[0123] In some implementations, the baseband circuit 610 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuit") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functions. In some implementations, the PHY layer functions include the aforementioned radio control functions. In some implementations, the protocol processing circuit operates or implements various protocol layers or entities of one or more wireless communication protocols. For example, when the baseband circuit 610 or the RF circuit 606 or both are part of a millimeter wave communication circuit or some other suitable cellular communication circuit, the protocol processing circuit may operate an LTE protocol entity or a 5G NR protocol entity or both. In this example, the protocol processing circuit may operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In some implementations, when the baseband circuit 610 or the RF circuit 606 or both are part of a Wi-Fi communication system, the protocol processing circuit may operate one or more IEEE-based protocols. In this example, the protocol processing circuit may operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 604G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuitry 610 may also support radio communications for more than one wireless protocol.
[0124] The various hardware elements of the baseband circuit 610 discussed herein may be implemented as, for example, a solder-in substrate including one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more ICs. In some implementations, the components of the baseband circuit 610 may be appropriately combined in a single chip or a single chipset, or disposed on the same circuit board. In some implementations, some or all of the components of the baseband circuit 610 and the RF circuit 606 may be implemented together, such as, for example, a system on a chip (SoC) or a system-in-package (SiP). In some implementations, some or all of the components of the baseband circuit 610 may be implemented as a separate SoC communicatively coupled to the RF circuit 606 (or multiple instances of the RF circuit 606). In some implementations, some or all of the components of the baseband circuit 610 and the application circuits 405, 505 may be implemented together as a separate SoC mounted to the same circuit board (e.g., a "multi-chip package").
[0125] In some implementations, the baseband circuit 610 may provide communications compatible with one or more radio technologies. The RF circuit 606 may use modulated electromagnetic radiation to achieve communication with a wireless network through a non-solid medium. In some implementations, the RF circuit 606 may include switches, filters, or amplifiers and other components to facilitate communication with a wireless network. The RF circuit 606 may include a receive signal path, which may include circuits for down-converting RF signals received from the FEM circuit 608 and providing baseband signals to the baseband circuit 610. The RF circuit 606 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by the baseband circuit 610 and providing RF output signals for transmission to the FEM circuit 608.
[0126] The receiving signal path of the RF circuit 606 includes a mixer circuit 606a, an amplifier circuit 606b, and a filter circuit 606c. In some specific implementations, the transmitting signal path of the RF circuit 606 may include a filter circuit 606c and a mixer circuit 606a. The RF circuit 606 also includes a synthesizer circuit 606d for synthesizing the frequency used by the mixer circuit 606a for the receiving signal path and the transmitting signal path. In some specific implementations, the mixer circuit 606a of the receiving signal path can be configured to down-convert the RF signal received from the FEM circuit 608 based on the synthesized frequency provided by the synthesizer circuit 606d. The amplifier circuit 606b can be configured to amplify the down-converted signal, and the filter circuit 606c can be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal can be provided to the baseband circuit 610 for further processing. In some implementations, the output baseband signal can be a zero-frequency baseband signal, but this is not required.In some implementations, the mixer circuit 606a of the receive signal path can include a passive mixer.
[0127] In some implementations, the mixer circuit 606a of the transmit signal path can be configured to up-convert an input baseband signal based on a synthesized frequency provided by the synthesizer circuit 606d to generate an RF output signal for the FEM circuit 608. The baseband signal can be provided by the baseband circuit 610 and can be filtered by the filter circuit 606c.
[0128] In some implementations, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some implementations, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some implementations, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some implementations, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may be configured for superheterodyne operation.
[0129] In some implementations, the output baseband signal and the input baseband signal may be analog baseband signals. In some implementations, the output baseband signal and the input baseband signal may be digital baseband signals, and the RF circuit 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuit 610 may include a digital baseband interface to communicate with the RF circuit 606. In some dual-mode examples, separate radio IC circuits may be provided to process signals for each spectrum, but the techniques described herein are not limited in this regard.
[0130] In some implementations, the synthesizer circuit 606d may be a fractional N synthesizer or a fractional N / N+1 synthesizer, but other types of frequency synthesizers may also be used. For example, the synthesizer circuit 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider. The synthesizer circuit 606d may be configured to synthesize an output frequency based on a frequency input and a frequency divider control input for use by the mixer circuit 606a of the RF circuit 606. In some implementations, the synthesizer circuit 606d may be a fractional N / N+1 synthesizer. In some implementations, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The frequency divider control input may be provided by the baseband circuit 610 or the application circuit 405 / 505 according to the desired output frequency. In some implementations, the frequency divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 405, 505.
[0131] FEM circuitry 608 may include a receive signal path that may include circuitry configured to operate on RF signals received from antenna array 611, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 606 for further processing. FEM circuitry 608 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by RF circuitry 606 for transmission by one or more antenna elements in antenna array 611. Amplification by either the transmit signal path or the receive signal path may be accomplished only in RF circuitry 606, only in FEM circuitry 608, or in both RF circuitry 606 and FEM circuitry 608.
[0132] In some implementations, the FEM circuit 608 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 608 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 608 may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 606). The transmit signal path of the FEM circuit 608 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 606), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 611.
[0133] The antenna array 611 includes one or more antenna elements, each of which is configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, a digital baseband signal provided by the baseband circuit 610 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted using the antenna elements of the antenna array 611 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, directional, or a combination thereof. The antenna elements may be formed into a variety of arrangements as known and / or discussed herein. The antenna array 611 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 611 may be formed as a patch of metal foil (e.g., a patch antenna) of various shapes and may be coupled to the RF circuit 606 and / or the FEM circuit 608 using a metal transmission line or the like.
[0134] The processor of the application circuit 405 / 505 and the processor of the baseband circuit 610 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 610 can perform layer 3, layer 2 or layer 1 functions individually or in combination, and the processor of the application circuit 405, 505 can utilize the data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include an RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include a MAC layer, an RLC layer, and a PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 (L1) may include a PHY layer of a UE / RAN node, which will be described in further detail below.
[0135] Figure 7 2 shows exemplary components of the communication circuit 700. In some implementations, the communication circuit 700 may be implemented as Figure 4 and Figure 5 The communication circuit 700 may be communicatively coupled (e.g., directly or indirectly) to one or more antennas, such as antennas 711a, 711b, 711c, and 711d. In some implementations, the communication circuit 700 includes or is communicatively coupled to dedicated receive chains, processors, or radio components, or a combination thereof, for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, Figure 7 As shown, the communication circuit 700 includes a modem 710 and a modem 720, which may correspond to or be Figure 4 and Figure 5 4 and 510. Modem 710 may be configured to communicate in accordance with a first RAT (such as LTE or LTE-A), and modem 720 may be configured to communicate in accordance with a second RAT (such as 5G NR). In some implementations, processor 705, such as an application processor, may interact with modems 710, 720.
[0136] The modem 710 includes one or more processors 712 and a memory 716 in communication with the processor 712. The modem 710 is in communication with a radio frequency (RF) front end 730, which may correspond to Figure 4 and Figure 5RFEM 415 and 515 are shown or are part thereof. RF front end 730 may include circuits for transmitting and receiving radio signals. For example, RF front end 730 includes RX circuit 732 and TX circuit 734. In some specific implementations, receiving circuit 732 communicates with DL front end 752, which may include circuits for receiving radio signals from one or more antennas 711a. Transmitting circuit 734 communicates with UL front end 754, which is coupled to one or more antennas 711b.
[0137] Similarly, the modem 720 includes one or more processors 722 and a memory 726 in communication with the one or more processors 722. The modem 720 is in communication with the RF front end 740, which may correspond to Figure 4 and Figure 5 RFEM 415 and 515 shown or part thereof. RF front end 740 may include circuits for transmitting and receiving radio signals. For example, RF front end 740 includes receiving circuit 742 and transmitting circuit 744. In some specific implementations, receiving circuit 742 may communicate with DL front end 760, and the DL front end may include circuits for receiving radio signals from one or more antennas 711c. Transmitting circuit 744 communicates with UL front end 765, and the UL front end is coupled to one or more antennas 711d. In some specific implementations, one or more front ends may be combined. For example, an RF switch may selectively couple modems 710, 720 to a single UL front end 772 for transmitting radio signals using one or more antennas.
[0138] The modem 710 may include hardware and software components for time division multiplexing UL data (e.g., for NSA NR operation) and various other technologies described herein. The processor 712 may include one or more processing elements configured to implement the various features described herein, such as by executing program instructions stored on a memory 716 (e.g., a non-transitory computer-readable memory medium). In some specific implementations, the processor 712 may be configured as a programmable hardware element, such as an FPGA or an ASIC. In some specific implementations, the processor 712 may include one or more ICs configured to perform the functions of the processor 712. For example, each IC may include a circuit configured to perform the functions of the processor 712.
[0139] The modem 720 may include hardware and software components for time division multiplexing UL data (e.g., for NSA NR operation) and various other techniques described herein. The processor 722 may include one or more processing elements configured to implement the various features described herein, such as by executing instructions stored on a memory 726 (e.g., a non-transitory computer readable memory medium). In some implementations, the processor 722 may be configured as a programmable hardware element, such as an FPGA or ASIC. In some implementations, the processor 722 may include one or more ICs configured to perform the functions of the processor 722.
[0140] Figure 8 Various protocol functions that can be implemented in a wireless communication device are shown. Specifically, Figure 8 An arrangement 800 is included to illustrate the interconnection between various protocol layers / entities. Various protocol layers and entities operating in conjunction with the 5G NR system standard and the LTE system standard are provided. Figure 8 The following description, but Figure 8 Some or all aspects of the invention may also be applicable to other wireless communication network systems.
[0141] In addition to other higher layer functions not shown, the protocol layers of arrangement 800 may also include one or more of PHY 810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857. These protocol layers may include one or more service access points (e.g., Figure 8 Items 859, 856, 850, 849, 845, 835, 825 and 815).
[0142] PHY 810 can transmit and receive physical layer signals 805, which can be received from or transmitted to one or more other communication devices. Physical layer signals 805 may include one or more physical channels, such as those discussed herein. PHY 810 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and switching purposes) and other measurement items used by higher layers (e.g., RRC 855). PHY 810 may also further perform error detection on transmission channels, forward error correction (FEC) encoding and decoding of transmission channels, modulation and demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and MIMO antenna processing. In some specific implementations, an instance of PHY 810 may utilize one or more PHY-SAP 815 to process requests from an instance of MAC 820 and provide instructions thereto. According to some specific implementations, requests and instructions transmitted using PHY-SAP 815 may include one or more transmission channels.
[0143] An instance of MAC 820 may process requests from and provide indications to an instance of RLC 830 using one or more MAC-SAPs 825. These requests and indications transmitted using MAC-SAPs 825 may include one or more logical channels. MAC 820 may perform mapping between logical channels and transport channels, multiplexing MAC SDUs from one or more logical channels onto transport blocks (TBs) to be delivered to PHY 810 using transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 810 using transport channels to one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through HARQ, and logical channel prioritization.
[0144] An instance of RLC 830 may utilize one or more radio link control service access points (RLC-SAPs) 835 to process requests from an instance of PDCP 840 and provide indications thereto. These requests and indications transmitted using RLC-SAPs 835 may include one or more logical channels. RLC 830 may operate in a variety of operating modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC 830 may perform transmission of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 830 may also perform resegmentation of RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.
[0145] An instance of PDCP 840 may utilize one or more Packet Data Convergence Protocol Service Access Points (PDCP-SAP) 845 to process requests from an instance of RRC 855 or an instance of SDAP 847, or both, and provide indications thereto. These requests and indications transmitted using PDCP-SAP 845 may include one or more radio bearers. PDCP 840 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform in-order delivery of higher layer PDUs when lower layers are reestablished, eliminate duplication of lower layer SDUs when lower layers are reestablished for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, or integrity verification).
[0146] An instance of SDAP 847 may utilize one or more SDAP-SAPs 849 to process requests from one or more higher layer protocol entities and provide instructions thereto. These requests and instructions transmitted using SDAP-SAPs 849 may include one or more QoS flows. SDAP 847 may map QoS flows to data radio bearers (DRBs) and vice versa, and may also mark QoS flow identifiers (QFIs) in DL and UL packets. A single SDAP entity 847 may be configured for a separate PDU session. In the UL direction, NG-RAN 110 may control the mapping of QoS flows to DRBs in two different ways (reflective mapping or explicit mapping). For reflective mapping, SDAP 847 of UE 101 may monitor the QFI of the DL packets of each DRB, and may apply the same mapping to packets flowing in the UL direction. For DRBs, SDAP 847 of UE 101 may map UL packets belonging to a QoS flow corresponding to the QoS flow ID and PDU session observed in the DL packets of the DRB. To implement the reflective mapping, the NG-RAN 310 may mark the DL packets with the QoS flow ID over the Uu interface. The explicit mapping may involve the RRC 855 configuring the SDAP 847 with explicit mapping rules of QoS flows to DRBs, which may be stored and followed by the SDAP 847. In some implementations, the SDAP 847 may only be used in NR implementations and may not be used in LTE implementations.
[0147] The RRC 855 may configure aspects of one or more protocol layers using one or more management service access points (M-SAPs), which may include one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840, and SDAP 847. In some implementations, instances of the RRC 855 may utilize one or more RRC-SAPs 856 to process requests from one or more NAS entities 857 and provide instructions thereto. The main services and functions of the RRC 855 may include broadcasting of system information (e.g., included in a master information block (MIB) or system information block (SIB) related to NAS), broadcasting of system information related to the access stratum (AS), paging, establishment, maintenance, and release of the RRC connection between the UE 101 and the RAN 110 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. These MIBs and SIBs may include one or more Information Elements (IEs), each of which may include a separate data field or data structure.
[0148] NAS 857 may form the highest layer of the control plane between UE 101 and AMF 321. NAS 857 may support the mobility and session management procedures of UE 101 to establish and maintain an IP connection between UE 101 and P-GW in the LTE system.
[0149] In some implementations, one or more protocol entities of arrangement 800 may be implemented in UE 101, RAN node 111, AMF 321 in NR implementation or MME 221 in LTE implementation, UPF 302 in NR implementation or S-GW 222 and P-GW 223 in LTE implementation, etc., for control plane or user plane communication protocol stacks between the aforementioned devices. In some implementations, one or more protocol entities that may be implemented in one or more of UE 101, gNB 111, AMF 321, etc. may communicate with corresponding peer protocol entities that may be implemented in or on another device (using services of corresponding lower layer protocol entities to perform such communication). In some specific implementations, the gNB-CU of gNB 111 may host the RRC 855, SDAP 847, and PDCP 840 of the gNB that control the operation of one or more gNB-DUs, and the gNB-DUs of gNB111 may each host the RLC 830, MAC 820, and PHY 810 of gNB 111.
[0150] In some implementations, the control plane protocol stack may include, in order from the highest layer to the lowest layer, NAS 857, RRC 855, PDCP 840, RLC 830, MAC 820, and PHY 810. In this example, upper layers 860 may be built on top of NAS 857, which includes an IP layer 861, SCTP 862, and an application layer signaling protocol (AP) 863.
[0151] In some implementations such as NR implementations, AP 863 may be an NG application protocol layer (NGAP or NG-AP) 863 for the NG interface 113 defined between the NG-RAN node 111 and the AMF 321, or AP 863 may be an Xn application protocol layer (XnAP or Xn-AP) 863 for the Xn interface 112 defined between two or more RAN nodes 111.
[0152] The NG-AP 863 may support the functionality of the NG interface 113 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN node 111 and the AMF 321. The NG-AP 863 services may include two groups: UE-associated services (e.g., services related to the UE 101) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 111 and the AMF 321). These services may include functions such as, but not limited to: a paging function for sending a paging request to the NG-RAN node 111 involved in a specific paging area; a UE context management function for allowing the AMF 321 to establish, modify or release the UE context in the AMF 321 and the NG-RAN node 111; a mobility function for the UE 101 in ECM-CONNECTED mode, for intra-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signaling transmission function for transmitting or rerouting NAS messages between the UE 101 and the AMF 321; a NAS node selection function for determining the association between the AMF 321 and the UE 101; an NG interface management function for setting up the NG interface and monitoring errors through the NG interface; a warning message transmission function for providing a means for transmitting a warning message using the NG interface or cancelling an ongoing warning message broadcast; a configuration transmission function for requesting and transmitting RAN configuration information (e.g., SON information, or performance measurement (PM) data) between two RAN nodes 111 using the CN 120; or a combination thereof, etc.
[0153] XnAP 863 may support the functions of Xn interface 112 and may include XnAP basic mobility procedures and XnAP global procedures. XnAP basic mobility procedures may include procedures for handling UE mobility within NG RAN 111 (or E-UTRAN 210), such as handover preparation and cancellation procedures, SN state transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, or procedures related to dual connectivity, etc. XnAP global procedures may include procedures not related to a specific UE 101, such as Xn interface setup and reset procedures, NG-RAN update procedures, or cell activation procedures, etc.
[0154] In an LTE specific implementation, the AP 863 may be an S1 application protocol layer (S1-AP) 863 for an S1 interface 113 defined between an E-UTRAN node 111 and an MME, or the AP 863 may be an X2 application protocol layer (X2AP or X2-AP) 863 for an X2 interface 112 defined between two or more E-UTRAN nodes 111. The S1 application protocol layer (S1-AP) 863 may support the functionality of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include an S1-AP EP. The S1-AP EP may be an interaction unit between an E-UTRAN node 111 and an MME 221 within the LTE CN 120. The S1-AP 863 services may include two groups: UE-associated services and non-UE-associated services. The functions performed by these services include, but are not limited to, E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration transmission.
[0155] The X2AP 863 may support the functions of the X2 interface 112 and may include an X2AP basic mobility procedure and an X2AP global procedure. The X2AP basic mobility procedure may include a procedure for handling UE mobility within the E-UTRAN 120, such as a handover preparation and cancellation procedure, an SN state transfer procedure, a UE context retrieval and a UE context release procedure, a RAN paging procedure, or a procedure related to dual connectivity, etc. The X2AP global procedure may include a procedure not related to a specific UE 101, such as an X2 interface setup and reset procedure, a load indication procedure, an error indication procedure, or a cell activation procedure, etc.
[0156] The SCTP layer (alternatively referred to as the SCTP / IP layer) 862 may provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). The SCTP 862 may ensure reliable delivery of signaling messages between the RAN node 111 and the AMF 321 / MME 221 based in part on the IP protocol supported by the IP 861. The Internet Protocol layer (IP) 861 may be used to perform packet addressing and routing functions. In some implementations, the IP layer 861 may deliver and transmit PDUs using point-to-point transport. In this regard, the RAN node 111 may include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.
[0157] In some implementations, the user plane protocol stack may include, in order from the highest layer to the lowest layer, SDAP 847, PDCP 840, RLC 830, MAC 820, and PHY 810. The user plane protocol stack may be used for communication between UE 101, RAN node 111, and UPF 302 in NR implementations, or between S-GW 222 and P-GW 223 in LTE implementations. In this example, the upper layer 851 may be built on top of SDAP 847 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 852, a general packet radio service (GPRS) tunneling protocol layer (GTP-U) 853 for the user plane, and a user plane PDU layer (UP PDU) 863.
[0158] The transport network layer 854 (also referred to as the "transport layer") may be built on top of the IP transport, and the GTP-U 853 may be used on top of the UDP / IP layer 852 (including the UDP layer and the IP layer) to carry the user plane PDU (UP-PDU). The IP layer (also referred to as the "Internet layer") may be used to perform packet addressing and routing functions. The IP layer may assign IP addresses to user data packets, for example, in any of the IPv4, IPv6, or PPP formats.
[0159] GTP-U 853 may be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data may be packets in any of the IPv4, IPv6 or PPP formats. UDP / IP 852 may provide a checksum for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication of selected data flows. The RAN node 111 and the S-GW 222 may utilize the S1-U interface to exchange user plane data using a protocol stack including an L1 layer (e.g., PHY 810), an L2 layer (e.g., MAC 820, RLC 830, PDCP 840 and / or SDAP 847), a UDP / IP layer 852, and a GTP-U 853. The S-GW 222 and the P-GW 223 may utilize an S5 / S8a interface to exchange user plane data using a protocol stack including an L1 layer, an L2 layer, a UDP / IP layer 852, and a GTP-U 853. As previously discussed, the NAS protocol may support mobility of UE 101 and session management procedures to establish and maintain an IP connection between UE 101 and P-GW 223 .
[0160] In addition, despite Figure 8Not shown, but an application layer may exist above the AP 863 and / or transport network layer 854. The application layer may be a layer where a user of the UE 101, RAN node 111, or other network element interacts with a software application, for example, executed by the application circuitry 405 or the application circuitry 505, respectively. The application layer may also provide one or more interfaces for the software application to interact with the communication system (such as the baseband circuitry 610) of the UE 101 or RAN node 111. In some implementations, the IP layer or the application layer or both may provide functionality the same or similar to layers 5 to 7 of the Open Systems Interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).
[0161] NFV architecture and infrastructure can be used to virtualize one or more NFs onto physical resources including a combination of industry standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system can be used to perform virtual or reconfigurable implementations of one or more EPC components and functions.
[0162] Fig. 9 A block diagram of an example of a computer system including components for reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the techniques described herein is shown. In this example, Fig. 9 A schematic diagram of hardware resources 900 is shown, including one or more processors (or processor cores) 910, one or more memory or storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled using a bus 940. For specific implementations where node virtualization (e.g., NFV) is utilized, a hypervisor 902 may be executed to provide an execution environment for one or more network slices or sub-slices to utilize the hardware resources 900.
[0163] Processor 910 may include processor 912 and processor 914. Processor 910 may be, for example, a CPU, a RISC processor, a CISC processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof. Memory / storage device 920 may include main memory, disk storage, or any suitable combination thereof. Memory / storage device 920 may include, but is not limited to, any type of volatile or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, or solid-state storage, or a combination thereof, and the like.
[0164] The communication resources 930 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 904 or one or more databases 906 using the network 908. For example, the communication resources 930 may include a wired communication component (e.g., for coupling using USB), a cellular communication component, an NFC component, (or Low power consumption) components, Wi-Fi components and other communication components.
[0165] The instructions 950 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 910 to perform any one or more of the methods discussed herein. The instructions 950 may reside completely or partially in at least one of the processors 910 (e.g., within a cache memory of the processor), the memory / storage device 920, or any suitable combination thereof. In addition, any portion of the instructions 950 may be transmitted to the hardware resources 900 from any combination of the peripheral device 904 or the database 906. Therefore, the memory of the processor 910, the memory / storage device 920, the peripheral device 904, and the database 906 are examples of computer-readable media and machine-readable media.
[0166] The UE may operate in DRX mode in order to save UE power by avoiding continuous monitoring of the PDCCH. DRX may also be referred to as a connected mode discontinuous reception (C-DRX) mode. Information for configuring the UE for DRX may be provided by a higher layer, such as RRC signaling. In DRX mode, the UE is configured to operate using a DRX cycle that includes an active state duration and a sleep state duration. In the active state, the UE may also be referred to as an on state or a network access mode, and the UE may receive transmissions from the network, such as DCI in channels such as PDCCH, CSI measurement signaling, etc. In the sleep state (also referred to as an off state or a power saving state), the UE is in a state where it does not receive any transmissions from the network.
[0167] Energy efficiency is critical for the operation of 5G / NR UEs, which may have a wide range of supported applications compared to LTE devices. In particular, energy consumption should be lower when the UE expects / receives no data. Traffic patterns in many 5G use cases may be bursty and may be served for short durations. Dynamic UE transitions between active and dormant states may facilitate improved UE power consumption. In particular, control channel monitoring in the radio resource control connected (RRC_CONNECTED) mode, which does not result in any data transmission, contributes a significant portion of UE power consumption. Therefore, network-assisted mechanisms may be used to reduce unnecessary physical downlink control channel (PDCCH) monitoring operations and trigger UE dormancy as much as possible. In addition, in NR, control channel monitoring, operating bandwidth, and many other transmission parameters are specifically configured for UEs. Therefore, UE-specific signaling mechanisms that address individual UE requirements and configurations may be provided. However, it may not always be feasible to allocate control channel resources in a UE-specific manner, such as when the load in the cell to which the UE is currently connected is high. If a group of UEs can monitor common time-frequency resources, the probability of control channel blocking and / or system overhead may be reduced.
[0168] Among other things, the present disclosure describes various control channel signaling mechanisms in which a group of UEs monitor common channel resources, and the control information may include grouped or multiplexed UE-specific information. In some embodiments, the control information may include group common information for a group of UEs. Several L1 control channel signaling mechanisms are described to adapt DRX configuration parameters and / or trigger UEs to enter sleep or wake up behavior. These are applicable to various traffic types, including arrival patterns in NR that may be bursty and may occur at short intervals. The UE-specific control information transmitted via group common control channel resource signaling may allow dynamic management of switching between active and sleep states, and the UE-specific control information also minimizes signaling overhead from a network perspective.
[0169] The factors that contribute most to UE power consumption in a connected state such as RRC_CONNECTED include PDCCH monitoring (typically the UE monitors PDCCH at configured PDCCH opportunities, which does not result in an allocated grant), operating bandwidth portion size, number of UE receive / transmit (Rx / Tx) antennas and active RF chains; and measurement operations.
[0170] The UE may operate in DRX mode in order to save UE power by avoiding continuous monitoring of the PDCCH. Typical DRX operation includes an on-duration when the UE is turned on and monitors transmissions from the network as part of a DRX cycle. Existing solutions include a DRX mode configured by higher layers in a connected state, where the DRX configuration includes RRC configured parameters. Examples of such DRX configuration parameters are shown in Table 1. 3GPP TS 38.321 provides a detailed description of the parameters listed in Table 1, the contents of which are incorporated by reference into the present disclosure.
[0171]
[0172]
[0173] Table 1
[0174] In NR, UEs may support a variety of traffic types, and in some cases, data may be quite bursty and delivered in short durations. A set of semi-statically configured RRC parameters for DRX operation may not be well adapted to the various traffic patterns and bursty traffic. Certain aspects of the present disclosure provide techniques for adapting DRX operation to the dynamic nature of traffic arrival patterns in order to minimize power consumption for a given UE.
[0175] Based on the nature of the active traffic flows to and from the UE, one DRX configuration in a set of configured DRX configurations may be activated at a given time. A DRX configuration may include at least the set of parameters indicated in the list in Table 1 above. A first DRX configuration is different from a second DRX configuration if the values of at least one parameter in the DRX configuration are different. Table 2 shows an example in which K configurations may be configured for a UE by a higher layer (e.g., via RRC signaling), where an index referring to one of the configurations may be indicated, for example, by a MAC control element (CE) or DCI. Each configuration may include one or more parameters from Table 1 and possibly more parameters, such as the wake-up signal monitoring duration, an offset of the starting position of the wake-up signal monitoring duration, an offset of the starting position of the on-duration of a control channel (e.g., monitored after the wake-up signal is detected, etc.), more details of which are provided in the following sections.
[0176] DRX-Config Index Configuration Content 0 Parameter 1, parameter 2, etc. 1 …… … …… K ……
[0177] Table 2
[0178] A new MAC CE may be added to activate a DRX-Config of one of several configured DRX-Configs to be used for the MAC entity of the corresponding cell group or serving cell. This may enable the UE to adjust multiple DRX parameters more quickly through a single MAC command compared to the existing DRX configuration mechanism using a semi-static RRC reconfiguration message. The number of DRX-Configs supported by each MAC entity, such as K in Table 2, may be fixed in the UE capability parameters or specification, and also determines the size of the MAC CE. In addition, in NR, the UE may be able to communicate using multiple parameter sets in different bandwidth parts or carriers, where the UE may or may not be able to transmit / receive simultaneously with different parameter sets. Transmissions with different parameter sets require separate fast Fourier transforms (FFTs) and possibly different RF chains. Therefore, in some designs, the UE may be configured with one or more parameter set-specific, bandwidth part-specific, or carrier-specific DRX configurations.
[0179] In some implementations, different parameters may be configured for different BWPs, and BWP switching may be performed by explicit DCI commands or background timer operations (e.g., bwp-inactivityTimer). If different DRX configurations for different BWPs with various parameter sets are desired, it may be beneficial that the DRX configuration can be switched along with the BWP switching. To this end, the DRX configurations in Table 2 may be linked to a specific BWP ID and / or cell ID within a cell group. In some implementations, a DRX configuration with a larger value setting of drx-InactivityTimer may be configured for the default BWP compared to other UE-specific BWPs, which is technically driven by the fact that the default BWP is typically used when the UE has almost completed data communication and a larger value has less impact on packet delay.
[0180] In some implementations, the network may provide dynamic L1 signaling for fast adaptation of DRX parameters, transitions between active and dormant states, or both. Compared to existing solutions in which the DRX mode is configured by RRC signaling, dynamic layer 1 (L1) signaling such as DCI (e.g., in a PDCCH transmission) may be used to notify the UE of adaptation of DRX parameters, activation of a DRX mode, deactivation of a DRX mode, entry into sleep, or wakeup from sleep. In some implementations, a dynamic L1 wake-up signal and / or entry into sleep signal may be used to potentially increase the sleep duration of the UE. In some implementations, the DCI message used for wake-up signaling or entry into sleep signaling may be a group common DCI (GC-DCI). For example, the control information may be transmitted in a common downlink control channel monitored by a group of UEs. The DCI may be appended with a cyclic redundancy check (CRC) scrambled by a radio network temporary identity (RNTI) and transmitted via the PDCCH.
[0181] The network may provide signaling, such as a wake-up signal (WUS), a go-to-sleep signal (GTS), or both. In the case of a WUS, the UE may be configured to receive signaling from the network during a dormant state. If the signal is appropriately detected, the signal may trigger the UE to transition to an active state for a given subsequent duration to monitor, for example, DCI in a PDCCH transmission from the network. After detecting the WUS, the UE may be turned on after a period of time or immediately. After detecting the WUS, the UE may be triggered to wake up or monitor the DCI / PDCCH for a duration that is part of a DRX cycle, or a duration that is not part of a DRX cycle.
[0182] In the case of GTS, the UE receives signaling from the network when the network is in an active state. If a GTS signal is detected appropriately, the GTS signal may trigger the UE to transition to a dormant state for a given subsequent duration. After detecting GTS, the UE may be turned off after a period of time or immediately. After detecting a GTS signal, the UE may be triggered to enter dormancy for a duration that is part of a DRX cycle or not part of a DRX cycle.
[0183] The UE may be configured with DRX operation and operate relative to one or more active DRX configurations. When the DRX cycle is configured, the active time (which may be based on 3GPP TS 38.321) includes the time when 1) drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or ra-ContentionResolutionTimer is running; or a scheduling request is sent on the PUCCH and is pending; or after successfully receiving a random access response to a random access preamble that was not selected by the MAC entity among the contention-based random access preambles, no PDCCH indicating a new transmission of the C-RNTI addressed to the MAC entity is received.
[0184] The UE may be configured to receive GTS signaling when the UE is in an active state. In some implementations, the UE may receive high-level signaling: GTS signaling parameters (having, for example, on or off values) provided by RRC, for example, if on, the UE monitors GTS signaling; if off, the UE does not monitor GTS. Enabling or disabling GTS signal monitoring may be group-specific, for example, cell-specific, or UE-specifically configured (e.g., via dedicated RRC signaling).
[0185] When the UE is in a configured / activated DRX mode with a given / indicated DRX configuration, the UE may switch on i) as part of a DRX cycle; or ii) when the UE is not configured / activated with any DRX mode and continuously monitors transmissions / signaling from the network. GTS signaling may trigger the UE to sleep and stop monitoring PDCCH for a specified / configured / indicated sleep duration.
[0186] The GTS signaling related parameters may include an offset to the starting position of the sleep duration parameter (T_GTS_A) and the sleep duration parameter (T_GTS_B). In some implementations, the UE may be configured by a higher layer (e.g., RRC signaling) using an index value for the GTS period and the GTS slot offset, the index value pointing to a row in a predefined table that maps the index value to the GTS period and the offset. In some implementations, the offset value may be defined relative to the start of an ongoing DRX cycle. In some implementations, parameters such as T_GTS_A and T_GTS_B may be indicated as part of the GTS signaling, or may be configured by a higher layer, for example as part of a DRX configuration or a GTS signaling configuration. In one example, T_GTS_A, T_GTS_B, or both may be predefined and given by the NR specification, or a predefined mapping may be obtained based on one or more DRX parameters (such as DRX on-duration drx-onDurationTimer and / or drx-InactivityTimer, etc.). The units of the offset to the start position of the sleep duration (e.g., T_GTS_A) and the sleep duration (e.g., T_GTS_B) may be in symbols or slots for a given parameter set or in time (such as milliseconds). When the UE monitors at least the PDCCH, the UE is capable of operating in a configured C-DRX mode within a BWP or carrier, e.g., in a given DRX cycle with a specifically configured on-duration. The UE is configured to monitor L1 signaling for GTS during the active / on state of the DRX mode. Depending on how long the on-duration is configured, the GTS signaling may cause the UE to be put into sleep state before the end of the configured on-duration, see Fig. 10A , wherein the GTS signal is received during the configured on-duration period, or a micro-sleep may be triggered during the on-duration period, such as Fig. 10B The on-duration may include one or more of the following: drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, where in one example, drx-onDurationTimer is the minimum on-duration at the start of the DRX cycle, and if a grant for DL / UL transmission is received during the drx-onDurationTimer, other configured durations are used, such as drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL.
[0187] Fig. 10A , Fig. 10B and Fig. 10C Different aspects of C-DRX mode operation are shown, where a UE may receive GTS L1 signaling during an on state to put the UE into a sleep state. In these examples, L1 signaling for GTS triggers the UE to go into sleep. The UE continues to follow the existing DRX configuration, where the sleep or active state duration may be modified if a GTS trigger is received. Figure 10A-10C The dashed area in refers to the skipped on-duration period; this also applies to the other subsequent figures unless otherwise stated.
[0188] exist Fig. 10A In this example, the UE may receive GTS L1 signaling during the on-state to put the UE into a dormant state before the on-duration ends. In this example, T_GTS_B is set to put the UE into a dormant state for the remainder of the configured on-duration. Fig. 10B In this example, the UE may receive GTS L1 signaling during the on state to put the UE into a sleep state for micro-sleep within the configured on duration. In this example, T_GTS_B is a relatively small value that triggers only micro-sleep, and after the elapsed time, the UE wakes up to monitor PDCCH or other signaling for the remainder of the on duration. Fig. 10C In the example, when a GTS trigger is received, the indicated or configured sleep duration may span more than a DRX cycle. After receiving the GTS trigger, the UE skips waking up for two subsequent on durations and enjoys an extended sleep duration. In this example, the UE is signaled to sleep for three DRX cycles starting from the DRX cycle in which the UE receives the GTS signaling.
[0189] In some implementations, the T_GTS_A parameter may be a function of UE capabilities or may be fixed in the NR specification. In another example, T_GTS_B may also be a function of UE capabilities. For example, Fig. 10B The T_GTS_B parameter in may need to take into account how quickly the UE may wake up to monitor the PDCCH for the remainder of the On Duration. In one example, T_GTS_B may also be set to a value that may be equal to or greater than the DRX cycle. In some cases, if the network expects that a given UE may not receive PDCCH for one or more subsequent DRX cycles, or if a certain delay in transmission can be tolerated, it may indicate a larger T_GTS_B so that the UE may be put to sleep for one or more subsequent DRX cycles, e.g., skipping one or more subsequent On Durations, see e.g. Fig. 10C .
[0190] exist Figure 10A-10C, T_GTS_A is shown as the duration between the location where the GTS signal is detected and the start location of the sleep duration. In some implementations, T_GTS_A may refer to an offset from a given reference point to the start location of the sleep duration. In some implementations, when, for example, GTS signaling is received from symbol i, the offset is counted from the first symbol. In some implementations, the offset is counted from the next symbol after the GTS signaling is received, for example, if the GTS signaling spans symbols i, i+1, ..., i+K, K≥1, then the offset count starts from symbol i+K+1 until the symbol before or when the sleep duration starts, for example, if the sleep duration starts at j, then until symbol j-1 or j.
[0191] If the GTS signaling spans symbols i, i+1, ..., i+K, K≥1, until the symbol before or when the sleep duration starts, the offset may be counted from the last symbol where the GTS signaling was received, e.g., if the GTS signaling spans symbols i, i+1, ..., i+K, K≥1, the offset count starts from symbol i+K until the symbol starts before or at the sleep duration, e.g., until symbol j-1 or j (if the sleep duration starts at j). In some implementations, the offset may be counted from a slot boundary, e.g., from the start of the current slot where the GTS signaling is received until the symbol before or at the start of the sleep duration. In some implementations, the offset is counted from the start of the current subframe or a given subframe until the symbol before or at the start of the sleep duration.
[0192] In some implementations, L1 signaling may trigger GTS together with switching one or more DRX parameters. For example, L1 signaling may switch the UE from a long DRX cycle to a short DRX cycle, or vice versa. The UE may assume the configured values of drx-ShortCycle and drx-ShortCycleTimer, or L1 signaling may explicitly indicate these values, in which case these values override the configured values. The remaining DRX parameters are RRC configured. In one example, the updated DRX parameters or the switched DRX configuration may be valid after T_GTS_A expires or the duration indicated by T_GTS_B ends, or after the end of the current DRX cycle or from the next Nth DRX cycle (N≥1) is applied. Parameter N may be fixed in the specification, configured by higher layer signaling, or explicitly indicated in L1 signaling.
[0193] In some implementations, the L1 trigger providing the GTS may additionally indicate a BWP, causing the UE to wake up in a different BWP indicated by the received GTS. The UE may be in the newly indicated BWP for a duration configured by a timer, or until further signaling of the switch is received. If a timer is configured, upon expiration, the UE returns to the previous or given default BWP and continues the configured DRX operation. In one example, the UE may switch to the new BWP in the next DRX cycle after the dormancy duration indicated by the GTS signaling expires, or the UE may switch to the new BWP after the end of the current DRX cycle or in the next Nth DRX cycle, N≥1. In one example, the UE may continue to operate using a common DRX configuration for all bandwidth parts, or when switching to a different DRX, the UE may assume a bandwidth part-specific DRX configuration (if supported).
[0194] Fig.11 An example of timing is shown, where the GTS indicates the BWP for the subsequent DRX cycle. The UE is in an active state and continuously monitors the DCI, and L1 signaling is provided for the GTS, activation of the DRX mode, or both. When the next DRX cycle begins, the signaling may cause the UE to wake up on a different bandwidth portion following the GTS indication. In this example, the UE receives GTS signaling 1101 in bandwidth portion B1. The L1 signaling may indicate different bandwidth portions to the UE, causing the UE to be in a different bandwidth portion B2 during the active / on state in the DRX mode. As shown, B2 is a smaller bandwidth portion compared to B1, which may provide power saving gains.
[0195] The UE may be in the active state with or without any configured or activated DRX mode. Specifically, if L1 signaling is used to activate the DRX mode, the UE may be configured to receive L1 signaling to provide a GTS that may also be used as an activation of the DRX mode. Specifically, if Fig.11 As shown, when the UE is in an active state and monitors the PDCCH, the UE receives GTS signaling 1101, DRX activation signaling, or both, and enters DRX mode. The DRX configuration may be pre-configured by RRC signaling or indicated as part of the L1 signaling that activates the DRX mode or puts the UE to sleep. During the on-duration, the UE may monitor the scheduling DCI 1105, and if a scheduling DCI is received, it may exit the DRX mode, for example, the scheduling DCI is used as a deactivation of the DRX mode. In one example, if the DRX on-duration starts after an offset after the L1 signaling activates the DRX mode, the L1 activation signaling may also indicate GTS. As shown Fig.11As shown, L1 signaling (e.g., GTS signaling 1101) can provide activation of the DRX mode and trigger the UE to enter a sleep duration before the start of the DRX cycle. In one example, T_GTS_B is the duration before the start of the DRX cycle after L1 activation. In another example, the DRX cycle starts after the duration given by T_GTS_A+T_GTS_B after L1 activation. The implementation discussed in the context of T_GTS_A and T_GTS_B is also applicable to L1 activation of the DRX mode when the UE is in an active state. More generally, the L1 activation signal can be received by a configured UE, and the UE starts the DRX cycle after a delay / offset after receiving the activation signaling. The delay / offset may or may not include the duration of the off / sleep state. The delay / offset before starting the DRX signaling can be semi-statically configured by UE-specific RRC signaling. Alternatively, the delay / offset can be indicated in the L1 activation. The delay / offset can be a function of the UE capability and / or it can depend on the UE processing time of the L1 activation.
[0196] In some implementations, the UE may not be configured with a DRX configuration or may not have any activated DRX mode and DRX configuration, and the L1 signaling for the GTS may dynamically put the UE into a sleep state for a given duration. In this context, the L1 trigger of the GTS may indicate the duration of the sleep and / or the starting position of the duration. In some implementations, the GTS signaling may dynamically instruct the UE to skip monitoring the next / subsequent N≥1 PDCCH monitoring opportunities.
[0197] In terms of wake-up signaling, the UE may be configured to receive a WUS after a sleep state when the UE operates in DRX mode with a given DRX configuration. In some embodiments, the UE may receive high-level (e.g., RRC) signaling such as a WUS transmission parameter that may have an on or off value. If the UE is an on value, the UE monitors the WUS. If the UE is an off value, the UE does not monitor the WUS. Enabling / disabling WUS monitoring may be group-specific, for example, a cell-specific or UE-specific configuration (e.g., via dedicated RRC signaling). In one example, the UE may receive a WUS to transition from a deep sleep state to a shallow sleep state or an active state, or from a shallow sleep state to an active state.
[0198] The UE may be configured with a WUS monitoring duration. The UE is turned on only during this duration unless a WUS is detected, which will require the UE to wake up and monitor the configured on duration for conventional PDCCH and other signaling monitoring. This can result in more power savings compared to the case where the UE always wakes up the configured on duration for PDCCH monitoring, and the configured on duration can be much longer than the duration of WUS monitoring. In one example, the UE may monitor WUS every N DRX cycles, where N is a positive integer. The value of N may be configured by RRC signaling UE-specifically. As described above, the on duration configured after WUS detection (e.g., for PDCCH monitoring) may include one or more of drx-onDurationTimer and drx-InactivityTimer. Note that, if necessary, the WUS monitoring duration may be additionally used for beam management and / or other necessary synchronization operations, which in one example may even be performed before the UE monitors WUS. In one example, the WUS may provide the UE with additional information to achieve or maintain synchronization with one or more cells.
[0199] To this end, a parameter may be identified, such as a WUS monitoring window drx-onDurationTimer-WUS, which in one example may be configured in addition to the drx-onDurationTimer, where in one example, drx-onDurationTimer>drx-onDurationTimer-WUS. The drx-onDurationTimer will not start unless a WUS is detected during the drx-onDurationTimer-WUS. The DRX configuration may include the drx-onDurationTimer-WUS as part of the configuration. In one example, the minimum on-duration for each DRX cycle is drx-onDurationTimer-WUS, which is different from the minimum on-duration drx-onDurationTimer in the existing C-DRX mode operation that does not respond to WUS.
[0200] Fig. 12A , Fig. 12B , Fig. 12C and Fig.12D Different examples of wake-up signaling are shown. The UE is turned on according to the configured DRX cycle to monitor the WUS for a limited duration. Fig. 12A In , upon detecting a WUS, the UE wakes up after a period of time and monitors the configured on-duration. Fig. 12B In , upon detecting a WUS, the WUS may trigger the UE to switch the BWP for active state operation. Fig. 12CIn these examples, upon detecting a WUS, the UE immediately starts monitoring the PDCCH and other signaling for the configured on-duration. In these examples, the UE operates in a DRX mode with two configured on-times: drx-onDurationTimer (e.g., Figure 12A-12C ) and drx-onDurationTimer-WUS (for example, Figure 12A-12C The on time (WUS) in Figure 12A-12B In , there is a gap between the end of drx-onDurationTimer-WUS and the start of drx-onDurationTimer. Fig. 12B In , it is assumed that WUS can potentially indicate BWP, for example, the UE wakes up and starts monitoring regular PDCCH or scheduled DCI, which uses a different and possibly larger BWP than that used by WUS monitoring. Fig. 12B As shown, a WUS may be monitored in a small BWP (e.g., BWP1), and if a WUS is detected, the UE may switch to a default / configured bandwidth portion (e.g., BWP 2) or the bandwidth portion that the UE was previously in before the DRX mode was configured. Fig. 12C In the example, it is assumed that drx-onDurationTimer starts immediately after drx-onDurationTimer-WUS ends and WUS is detected.
[0201] Identifiable parameter N gap , which may indicate an inactivity duration that begins after the drxonDurationTimer-WUS expires and ends before the drx-onDurationTimer starts. gap It can be expressed in symbols or time slots within a given parameter set or in ms. In some designs, N gap may be indicated as part of the WUS signaling. In one example, if the UE detects a WUS early during the monitoring window, the UE may sleep for the remaining duration of the monitoring window and turn on when the on-duration for PDCCH monitoring begins. In this context, N gap It can be expressed as the time between the successful detection of the WUS position and the start of the on-duration for PDCCH monitoring. gap It can still be defined as the duration between the end of the WUS monitoring opportunity and the start of the on-duration for PDCCH monitoring.
[0202] In some implementations, if the UE is configured to monitor for WUS, the DRX cycle may start with a start time for WUS monitoring, e.g., drx-onDurationTimer-WUS, which may be a duration at the start of the DRX cycle instead of drx-onDurationTimer as in existing solutions that do not include WUS monitoring. In this context, drx-SlotOffset may indicate a delay before starting drx-onDurationTimer-WUS. drx-onDurationTimer may start after an offset or immediately upon detection of WUS. In some specific implementations, the DRX cycle may start at drx-onDurationTimer as in a conventional system, and the offset may be configured to identify the location of the WUS monitoring window, for example, the UE may be configured to start the WUS monitoring window for a time (e.g., drx-onDurationTimer-WUS) before the configured location, where drx-onDurationTimer should start at the configured location when WUS is detected, and there is an offset between the end of drx-onDurationTimer-WUS or the detection of WUS and the start of drx-onDurationTimer.
[0203] In some embodiments, the starting position of the on-duration drx-onDurationTimer for PDCCH monitoring may be indicated as an offset to a reference point, such as a given / current subframe or timeslot boundary or the position where a DRX cycle starts, or the position / control resource set such as CORESET where a WUS is detected or the end of the WUS monitoring window. This additional offset parameter may be part of the DRX configuration, for example, when SlotOffset is used to indicate a delay before the start of the DRX cycle before drx-onDurationTimer-WUS, or the offset may be dynamically indicated as part of the WUS. In one example, the WUS may dynamically indicate the on-duration drx-onDurationTimer. The indicated on-duration may override the configured on-duration as part of the DRX configuration. The indicated on-duration may span one or more DRX cycles. Figure 12A-12C In the DRX cycle, the DRX cycle starts from the monitoring window of WUS (e.g., drx-onDurationTimer-WUS).
[0204] Fig.12DAn example of a WUS configuration for on-off DRX operation is shown. In this example, the WUS monitoring window or duration may be Ngap symbols or time slots of a given parameter set or milliseconds before the start of a configured DRX cycle in order to keep PDCCH monitoring active in the DRX cycle as in a conventional system (if it occurs). If the UE does not detect a WUS signal in the monitoring window or opportunity indicating that the UE is to perform DRX operation in the next M DRX cycle, the UE will skip PDCCH monitoring in the next M DRX cycle. If a WUS is detected, conventional DRX operation is performed, for example, the UE turns on the configured on duration at the beginning of the DRX cycle for PDCCH monitoring. The value of M may be fixed in the specification or configured by a higher layer, and / or a value of M may be dynamically indicated by the WUS based on at least the real-time service characteristics of the UE. In addition, the Ngap value may be reported by the UE as part of the UE capabilities and then configured accordingly. Assuming M=1 in Fig.12D middle.
[0205] In some implementations, L1 signaling may trigger a WUS in conjunction with switching one or more DRX parameters. For example, L1 signaling may switch the UE from a long DRX cycle to a short DRX cycle. In some implementations, the UE may assume the configured values of drx-ShortCycle and drx-ShortCycleTimer, or L1 signaling may explicitly indicate these values, in which case these values override the configured values. The remaining DRX parameters are RRC configured. In some implementations, the WUS may indicate whether the UE exits DRX mode or wakes up only for a subsequent on-duration to monitor the scheduled DCI. In some implementations, the L1 trigger providing the WUS may additionally indicate a bandwidth part so that the UE wakes up in a different bandwidth part, see e.g. Fig. 12B The UE may be in the new bandwidth part for a duration configured by a timer, or until further signaling of the switch is received. If a timer is configured, then upon expiration the UE returns to the previous or given default bandwidth part and continues the configured DRX operation.
[0206] Fig.13A , Fig. 13B and Fig. 13C Different examples of monitoring timers for WUS, PDCCH and subsequent PDSCH are shown.WUS detection means that the UE may soon receive PDCCH / scheduled DCI or other transmissions from the network. Figure 13A-13C The timers considered in the examples in may be UE-specific or group-specific configured by RRC signaling. One or more of these timers may be part of the DRX configuration.
[0207] exist Fig.13AIn the embodiment, the UE monitors WUS according to a timer such as drx-onDurationTimer-WUS. If the UE detects WUS, the UE turns on and subsequently monitors PDCCH for a duration given by another timer, such as drx-onDurationTimer. If the UE detects PDCCH, the UE starts another timer, such as drx-InactivityTimer for subsequent PDSCH and additional PDCCH monitoring and detection. For a given parameter set, the timer for monitoring PDCCH may be started X≥1 symbol or time slot after successful detection of WUS. Similarly, for a given parameter set, the timer for PDSCH and / or subsequent PDCCH and / or other transmission, reception may be started X≥1 symbol or time slot after successful detection of PDCCH.
[0208] exist Fig. 13B In the example, two timers are configured instead of Fig.13A The three timers in the example in . Since the detection of WUS means that the PDCCH for the UE is about to occur, an on-duration timer that can be used to monitor both WUS and / or PDCCH is used. Of course, PDCCH monitoring is after WUS detection. It should be noted that WUS can be transmitted in a sequence or PDCCH / DCI. If WUS is transmitted in PDCCH, the UE directly monitors PDCCH according to the PDCCH monitoring configuration for WUS, which may be different from conventional PDCCH monitoring for data scheduling. Fig. 13BThe example assumes an initial timer as part of a DRX cycle when the UE is turned on, which includes one or more PDCCH monitoring opportunities and / or one or more WUS monitoring opportunities. After the UE detects the WUS, the UE may start monitoring the PDCCH at one or more subsequent opportunities. After detecting the PDCCH, the UE starts another timer for receiving subsequent PDSCH and / or PDCCH and / or other transmissions from the network. Here, the first timer may be a drx-onDurationTimer, in which the UE monitors both WUS and / or scheduled DCI / PDCCH. It is also possible to transmit the WUS in a PDCCH or sequence. The second timer may be similar to the drx-InactivityTimer, which, for a given parameter set, may be started X≥1 symbols or time slots after the successful detection of the PDCCH. In one example, the UE monitors the WUS PDCCH at M≥1 opportunities during the timer, and once the WUS is detected, the UE monitors the conventional PDCCH at N≥1 opportunities out of the K≥N opportunities configured in the timer. In other words, after detecting the WUS, there may be only N opportunities left in the timer to monitor the PDCCH / scheduling DCI. The PDCCH carrying the WUS and the PDCCH used for scheduling may have different configuration and monitoring properties.
[0209] exist Fig. 13C In the example, two timers are configured instead of Fig.13AThe three timers in the example in . Since the detection of WUS means that the PDCCH for the UE is about to occur, an on-duration timer that can be used to monitor WUS is used, such as drx-onDurationTimer or drx-onDurationTimer-WUS. When WUS is detected, the UE starts another timer for PDCCH and / or PDSCH reception, which timer may be similar to drx-InactivityTimer. In this example, the difference compared to the conventional system is that in the conventional system, drx-onDurationTimer is used to monitor PDCCH, and drx-InactivityTimer is started after the PDCCH is detected. In this example, it is assumed that an initial on-duration timer is used, such as drx-onDurationTimer or drx-onDurationTimer-WUS that is only used to monitor WUS. It should be noted that WUS can be transmitted in a sequence or PDCCH, where in one example, PDCCH can also be a scheduled DCI. Alternatively, WUS can be transmitted in different PDCCHs (e.g., not scheduled DCI) or sequences. In this example, the second timer includes monitoring opportunities for receiving PDCCH / scheduling DCI and receiving subsequent PDSCH, for example, unlike the conventional system, here the UE can start the second timer before receiving PDCCH. Unless WUS is transmitted in the scheduling DCI or PDCCH, the scheduling DCI / PDCCH is received during the second timer such as drx-InactivityTimer. Here, the UE starts the drx-InactivityTimer after detecting the WUS, because the network may send the WUS because there is a PDCCH to be sent to the UE, and the UE can immediately start the drx-InactivityTimer for receiving PDCCH / PDSCH, instead of using another intermediate timer, such as Fig.13AAs shown. Therefore, in one example, drx-onDurationTimer is redefined in a NR that may include only WUS monitoring opportunities, and drx-InactivityTimer may be redefined to include monitoring of PDCCH / scheduling DCI and subsequent PDSCH. Of course, if necessary, drx-InactivityTimer may be triggered multiple times, such as when the UE receives a PDCCH near the end of the current drx-InactivityTimer. Based on a given parameter set, the second timer may be started after X≥1 symbol or time slot after WUS is successfully detected during the first timer. In one example, if WUS is transmitted in the scheduling DCI during a first timer such as drx-onDurationTimer or drx-onDurationTimer-WUS (or, implicitly / explicitly if a first scheduling DCI that also serves as WUS is received), the corresponding PDSCH may be transmitted in a second timer such as drx-InactivityTimer.
[0210] In some implementations, various types of DRX mode operations may be configured for UEs in connected mode (including type 1 mode and type 2 mode). Type 1 mode is a DRX mode with at least one DRX configuration activated or deactivated by RRC or MAC CE. Type 2 mode is a DRX mode with at least one DRX configuration activated or deactivated by L1 signaling.
[0211] There are different Type 1 modes. In Type 1a, RRC signaling may be provided to configure one or more DRX parameters, and in some cases the DRX configuration may be switched. In Type 1b, L1 signaling may be provided to update the DRX parameters, and in some cases the DRX configuration may be switched. The L1 signaling may also indicate a GTS or a WUS. In Type 1c, RRC signaling or a combination of L1 and RRC signaling may be provided to configure one or more DRX parameters, and in some cases the DRX configuration may be switched. The L1 signaling in Type 1c may also indicate a GTS or a WUS. In Type 1d, a MAC Control Element (MAC-CE) for DRX parameter reconfiguration may be introduced, which is identified by a MAC Protocol Data Unit (PDU) subheader with a dedicated Logical Channel Group ID (LCID). In addition, it may have a fixed size and consist of fields to indicate a DRX parameter set or configuration index to be applied by the MAC entity. In addition, L1 signaling may be provided to indicate a GTS or a WUS.
[0212] There are different Type 2 modes. In Type 2a, RRC or MAC CE signaling may be provided to configure one or more DRX parameters and in some cases switch the DRX configuration. In Type 2b, L1 signaling may be provided to update DRX parameters and in some cases switch the DRX configuration. L1 signaling may also indicate GTS or WUS. In Type 2d, RRC and MAC CE signaling or a combination of L1, RRC, and MAC CE signaling may be provided to configure one or more DRX parameters, switch the DRX configuration, and provide GTS or WUS indication.
[0213] In some specific implementations, activation of a DRX mode with at least one DRX configuration does not necessarily mean that the DRX configuration index is always indicated in the L1 signaling that provides the activation trigger. On the contrary, it is also possible that the UE is configured with at least one DRX configuration through previous higher layer signaling (such as RRC signaling and L1 activation signaling), thereby turning on the DRX mode only with the previously indicated DRX configuration.
[0214] In some implementations, RRC signaling or L1 signaling can activate the DRX mode which can be based on the expiration of a timer. For example, if the UE receives a subsequent L1 signaling trigger, such as a WUS or scheduling DCI in the on-duration, which can be used as an indication to terminate the DRX mode, the UE can exit the DRX mode, otherwise the UE can continue to operate in the DRX mode until the timer expires.
[0215] Examples of L1 signaling include sequence-based or DCI-based transmissions, for example, in PDCCH or a combination thereof, both of which can be UE-specific or group-common. The units of one or more of the duration or period or offset of the different configurations or indications may be expressed in sub-ms, ms, symbols, or time slots of a given parameter set. Other types of units are also possible. Examples of higher layer signaling in the context of the following embodiments include NR Minimum System Information (MSI), NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling, where RRC signaling can be UE-specific or group-common.
[0216] The wireless system may provide a DCI-based L1 signaling mechanism where a group of UEs monitor common time-frequency resources to obtain control information that may be UE-specific, group-common, or both. The DCI may be transmitted in a PDCCH associated with a common RNTI. In some implementations, the DCI may be transmitted in sequence without being associated with any RNTI.
[0217] The network may transmit DCI in a PDCCH with a common RNTI. In a given cell, a group of UEs may be formed that, depending on the function of the DCI format, monitor a DCI format with a CRC masked by a common RNTI attached, for example, a PDCCH associated with a common RNTI such as a power saving RNTI (PS-RNTI), a DRX RNTI, a GTS RNTI, or a WUS RNTI. The RNTI may be configured by higher layers via NR Minimum System Information (MSI), NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI), or Radio Resource Control (RRC) signaling. DCI with a common RNTI may be received in common time-frequency resources (such as a common search space) or UE-specific time-frequency resources (such as a UE-specific search space).
[0218] Fig.14 An example of a common DCI format structure with UE-specific fields is shown. DCI based on this format may be a GC-DCI containing UE-specific content. In this example, Fig.14 There are K fields in the DCI structure shown. Each field is UE-specific and contains information for a given UE. The network can map the UE to the corresponding field in the DCI. The mapping can be obtained by the UE via high-level signaling such as RRC signaling. Each UE-specific field may have L subfields, where each subfield may have M bits. A CRC may also be included in the structure to generate product information contained in the field. There is an LM bit in each UE-specific field. In addition to the CRC bit, the DCI format has a total of KLM bits. Fig.14 , an example is shown in which K fields or blocks are configured in a DCI for K UEs, eg, each field is UE-specifically configured and contains information for a given UE.
[0219] In some implementations, a common DCI format may be used to signal GTS. In some implementations, each UE-specific field includes a single bit, where a bit value of 1 indicates GTS, and a bit value of 0 indicates no GTS trigger for that given UE. <crc>}, there are K=5 UE-specific fields for the corresponding UEs configured to monitor the common DCI. In this transmission, only the UEs mapped to the 2nd and 5th fields have a trigger indicated by the GTS, and other UEs do not have a trigger. When the DCI format is detected, the UEs mapped to the 2nd and 5th fields may go to sleep, while other UEs continue to be active until the configured on-duration ends or until further signaling is received.
[0220] In some implementations, each UE-specific field includes a single bit to indicate the activation or deactivation of the DRX mode. In this bit, a value of 1 may indicate the activation of a DRX mode with a given DRX configuration for the corresponding UE. If the UE does not operate based on any DRX mode, the activation of the DRX mode may also be used as a GTS alternatively, for example, when the UE sleeps for a certain offset before the start of the DRX cycle. GTS signaling may trigger periodic on / off behavior of the UE, which may be similar to the activation of the DRX mode. In some implementations, the GTS signaling may indicate the sleep duration of the instance without implying any periodicity, for example, the UE wakes up after the indicated sleep duration and resumes operation according to the pre-existing configuration. In some implementations, if the DCI only provides a GTS trigger, the UE receiving the trigger (e.g., a bit value of 1) may follow a set of parameters of the UE-specific configuration, such as T_GTS_A, T_GTS_B, or both. After the sleep duration expires, the UE may continue to follow the existing DRX configuration.
[0221] Fig.15 An example is shown where two UEs receive a GTS trigger in a GC-DCI, however each UE has a different DRX configuration. In general, multiple UEs receiving a GTS trigger or activation trigger in a GC-DCI may have different DRX configurations, such as different DRX cycles, different on-durations, or both.
[0222] Higher layer configuration information may be provided to the UE so that the UE reacts accordingly after the GTS trigger. If an offset is configured, the configuration information may cause the UE to start the sleep duration after the offset. If not, the speed at which the UE enters sleep may be affected by the UE's capabilities, for example, once it detects that the GTS trigger is true and turns off the RF or baseband components. In some specific implementations, the configuration information may cause the UE to sleep for a given duration. The duration may also vary with the configured on-duration, such as the remaining time the UE sleeps. In some specific implementations, the configuration information may cause the UE to switch to a different BWP in the next Kth DRX cycle, K≥1. In some specific implementations, the configuration information may cause the UE to monitor a reduced number of PDCCH candidates for one or more of the subsequent on-durations.
[0223] In some implementations, one or more UE-specific configurations may be dynamically indicated in one or more UE-specific fields, such as: an offset of the start position of the sleep duration; the sleep duration; the BWP ID when the UE wakes up in a different BWP after the sleep duration; switching DRX parameters within an existing DRX configuration, for example, switching between a long DRX cycle and a short DRX cycle; and an index of a DRX configuration, wherein the UE-specific field may include more than one bit, may have more than one subfield, or both to dynamically indicate one or more parameters. In some implementations, the UE-specific field may include K bits, wherein the field indicates an index value corresponding to a configuration in a set of configurations. Each configuration may include one or more of the above parameters or indications. For example, the UE-specific field may have 2 bits, which may be configured according to Table 3.
[0224] Place value Indicative value 00 GTS trigger is false 01 GTS trigger is true and the first pair {T_GTS_A, T_GTS_B} 10 GTS trigger is true and the second pair {T_GTS_A, T_GTS_B} 11 GTS Trigger is true and the given bandwidth part ID for handover
[0225] Table 3
[0226] A common DCI format may be used to signal a WUS. In some implementations, each UE-specific field may include a single bit, where a bit value of 1 indicates wake-up, and a bit value of 0 may indicate that a given UE is not awake. In {0,1,0,0,1, <crc>In an exemplary DCI transmission of}, there are K=5 UE-specific fields for corresponding UEs configured to monitor common DCI. In this transmission, only UEs mapped to the 2nd and 5th fields have a trigger for WUS indication, and other UEs do not have a trigger. Upon detecting a DCI transmission, UEs mapped to the 2nd and 5th fields may wake up for a subsequent duration to monitor the scheduled DCI or other PDCCH, while other UEs do not wake up and return to sleep until the end of a given DRX cycle or until the next WUS monitoring opportunity.
[0227] One or more UE-specific configurations may be dynamically indicated in the UE-specific field. Such configurations may include one or more of the following: N of the starting position of the on-duration for PDCCH monitoring gap or offset, such as drx-onDurationTimer or drx-InactivityTimer; on-duration for PDCCH monitoring; bandwidth part identifier when the UE wakes up in a different bandwidth part after WUS detection; switching of DRX parameters within an existing DRX configuration, for example, between a long DRX cycle and a short DRX cycle; an index of a DRX configuration; a PDCCH candidate set (e.g., possibly of reduced size) for monitoring one or more of the subsequent on-durations; and deactivation of a DRX mode. In some implementations, the UE-specific field may include more than one bit, may have more than one subfield, or both to dynamically indicate one or more parameters. Alternatively, one or more parameters that are not dynamically indicated may be higher layer configured, or not supported as part of a supported feature after WUS detection, or indicated as part of different signaling.
[0228] In some implementations, the K sets of PDCCH monitoring candidates during the on-duration may be configured by higher layers via UE-specific RRC signaling. L1 signaling of the WUS may dynamically indicate which set of PDCCH monitoring candidates to use during the on-duration. For example, during the on-duration for power saving, one or more search space sets or subsets of search space sets or one or more CORESETs may be disabled for PDCCH monitoring. In some implementations, the UE-specific field may include K bits indicating an index of a configuration from a set of configuration sets. Each configuration may include one or more of the above parameters or indications. For example, the UE-specific field may have 2 bits, which may be configured according to Table 4. In this table, for N gap Given a value of , the on-duration or bandwidth portion ID for PDCCH monitoring may be selected / mapped to a corresponding bit value label from a set of supported parameter values.
[0229]
[0230]
[0231] Table 4
[0232] In some implementations, if activation or deactivation of the DRX mode is indicated dynamically, GTS and WUS signaling may be used as activation and deactivation signaling, respectively, and more generally, the UE may be configured to receive one or more indications in a UE-specific field in a common DCI. Such indications may include: activation signaling; activation signaling with GTS, for example, the UE starts a DRX cycle after an offset or sleep duration; GTS signaling without activation, for example, GTS signaling may be received independently, for example, GTS signaling may be received to put the UE into micro-sleep, and after expiration, the UE resumes DRX mode operation; deactivation signaling; deactivation signaling with WUS, that is, WUS signaling itself is used for or indicates deactivation of the DRX mode; WUS signaling without deactivation, for example, the UE only monitors the on-duration of PDCCH monitoring after WUS detection and does not exit DRX mode.
[0233] In some specific implementations, the same common RNTI can be used to detect GTS and WUS if the common RNTI is configured for UE monitoring. Since GTS and WUS can be monitored at different times, from the UE's perspective, a separate RNTI may not be required. In one example, a unified DCI format with the same common RNTI can be used to indicate GTS and WUS and / or activation and deactivation of DRX mode. Since the transmission timings of WUS and GTS are mutually exclusive, it may not be necessary to explicitly indicate whether DCI is sent for GTS or WUS. For example, when the UE is active and monitors the scheduling DCI, it can only receive GTS. Similarly, when the UE is in DRX mode and is turned on from a sleep state, it can only receive WUS.
[0234] Different bit fields within the UE-specific fields in the GC DCI may have different interpretations, taking into account which state the UE is currently based on. For example, for a field indicating activation and deactivation of the DRX mode, if received during an active state while monitoring PDCCH or scheduling DCI, then: this bit field = 0 may mean activation, 1 may mean deactivation of the DRX mode, and vice versa, and if received during the WUS monitoring duration: this bit field = 0 may mean remaining in the activated DRX mode, 1 may mean deactivation of the DRX mode, and vice versa. Regarding a field for indicating an offset or on-duration for the start of sleep, if received during an active state while monitoring PDCCH or scheduling DCI, this field may indicate an offset for the start of the sleep duration, and if received during the WUS monitoring duration, this field may indicate an offset for the start of the subsequent on-duration for PDCCH monitoring. Regarding a field for indicating a duration or on-duration for subsequent sleep, if this field is received during an active state while monitoring PDCCH or scheduling DCI, this field may indicate the sleep duration. The indicated sleep duration may last less than or longer than the DRX cycle. - If received during the WUS Monitoring Duration, then: This field may indicate the on-duration for PDCCH monitoring. The indicated sleep duration may last less than or longer than the DRX cycle. For the field indicating the bandwidth part ID, if received during the active state when monitoring PDCCH or scheduling DCI, then: This field indicates the bandwidth part that the UE turns on at subsequent occasions. If received during the WUS Monitoring Duration, then: This field may indicate that the UE wakes up and monitors the bandwidth part for scheduling DCI.
[0235] As described above, the WUS and GTS may be signaled via the same DCI, for example, the same DCI format may be used. In some implementations, the group common DCI format 2_x transmitted on the PDCCH has a CRC scrambled by a configured RNTI, such as a PS-RNTI. Format 2_x may be used to signal wake-up information and go to sleep / skip PDCCH monitoring information for a given UE among a group of UEs monitoring a common DCI format, such as Fig.14 When a UE receives DCI format 2_x outside of active time, the UE shall assume that the bits in the UE-specific field / block will at least indicate whether the UE needs to wake up. Conversely, when the UE receives DCI format 2_x during DRX active time, the UE shall assume that the bits in the UE-specific field will at least indicate whether the UE can skip PDCCH monitoring for a given / indicated duration / number of PDCCH opportunities.
[0236] In some implementations, each UE-specific field has 1 bit. In one option, if the UE is outside the active time and "0" is the bit value in the field, the UE does not wake up and skips the next N≥1 DRX cycles (e.g., N can be 1). If the UE is outside the active time and "1" is the bit value in the field, the UE wakes up and transitions to the active time or starts monitoring PDCCH / scheduling DCI. Vice versa, for example, a "1" bit value indicates no wakeup, and "0" indicates wakeup. In another option, if the UE is within the active time and "0" is the bit value in the field, the UE continues PDCCH monitoring and does not go to sleep. If the UE is within the active time and "1" is the bit value in the field, the UE goes to sleep or skips PDCCH monitoring for a given / configured / specified duration (e.g., the duration can be measured in number of slots, K≥1) or for a given / configured / specified number of PDCCH monitoring opportunities (M≥1). The duration or number of monitoring opportunities that the UE skips after receiving the signal can be specifically configured by RRC signaling. Alternatively, when a "1" is received in the field during the active time, the UE may enter sleep until the next DRX cycle, for example, transition from the active time to outside the active time and stop the drx-inactivity or start the duration timer (if running). Vice versa, for example, if a "0" is received during the active time, the UE enters the sleep state, and if a "1" is received during the active time, the UE continues PDCCH monitoring and remains in the active time.
[0237] In another example, each UE-specific field / block may have N≥1 bits. Depending on whether the DCI format is received outside of active time or during active time, the N-bit field / block may be mapped to a different set of parameter indications. When the DCI format is received outside of active time and during active time, the mapping of the bit value to a set of parameters or configurations may be UE-specifically configured, for example, via RRC signaling. When the UE receives the DCI format outside of active time, the bits in the UE-specific field may be mapped to a set of parameters that may include one or more of the following: wake-up indication, for example, whether the UE transitions from external active time to active time; cross-slot scheduling configuration; triggering of RS, such as CSI-RS or TRS; indication of UL resources for CSI reporting; activation or deactivation of a carrier or cell; triggering for BWP switching or adaptation; number of MIMO layers or antenna adaptation; indication of CORESET, search space, or both for subsequent PDCCH decoding; indication of DRX configuration and / or one or more of DRX configuration parameters; and indication of the number of DRX cycles to be skipped or active. In some implementations, the cross-slot scheduling configuration may include an indication of a time domain resource allocation (TDRA) table from a set of configured TDRA tables, wherein the indicated TDRA table may enable or disable cross-slot scheduling. In some implementations, the cross-slot scheduling configuration may include an indication of a minimum value of K0, which refers to the duration between PDCCH and PDSCH in the number of time slots. If K0>0, it refers to cross-slot scheduling, i.e., PDSCH and PDCCH are received in different time slots.
[0238] In some implementations, after receiving the wake-up indication, when the UE transitions from external active time to active time, one or more of the indicated parameters may take effect. When the UE receives a DCI transmission during active time, bits in a UE-specific field in the DCI may be mapped to a set of parameters that may include one or more of the following: a GTS indication, e.g., whether the UE skips PDCCH monitoring or transitions from active time to external active time; a PDCCH skip duration, e.g., the number of time slots the UE skips PDCCH monitoring; the number of PDCCH monitoring opportunities to be skipped; and activation or deactivation information for one or more carriers or cells.
[0239] The indicated parameters may be signaled in one or more subfields in a UE-specific block. For example, a table may be constructed where each row maps to a set of parameters with certain values, such as one or more of the above, and the UE-specific field / block may indicate the row index of the table. For example, the UE may be configured with two tables, one to be used when the UE receives DCI outside of active time, and the other to be used when the UE receives DCI during active time. The table may be configured by UE-specific RRC signaling. In another example, a UE-specific block may have K ≥ 1 subfields to indicate M ≥ 1 parameters, M ≥ K, where M and K are integers.
[0240] In some implementations, each UE-specific field has N=2 bits. When the UE receives the DCI format outside the active time, examples are given in Tables 5 and 6, which show that 2 bits are mapped to a certain configuration or parameter set, or the bit value of the field indicates the row index of the configuration table.
[0241]
[0242] Table 5
[0243]
[0244] Table 6
[0245] In some implementations, a configuration such as provided in Table 7 is used. When the UE receives a DCI message during active time, two bits are shown in Table 7 to map to a specific configuration or parameter set, or the bit value of the field indicates a row index of the configuration table.
[0246]
[0247] Table 7
[0248] In some implementations, the DRX configuration is not explicitly indicated, but is implied based on other signaling. For example, if the DRX configuration has been associated with the indicated bandwidth part, the UE may be configured to identify the DRX configuration based on the indicated bandwidth part.
[0249] Fig.16 An example of the structure of a group common DCI format including UE-specific fields and common fields is shown. In this example, the DCI format may include K UE-specific fields and M common fields. Each UE configured to monitor the DCI format may obtain control information from the corresponding UE-specific fields and M common fields. The DCI format may include CRC. The DCI format and other DCI formats may include one or more reserved bit fields. In some specific implementations, if GC DCI is used for GTS, there may be one or more common fields that can be used to indicate one or more of the following: an offset to the starting position of the sleep duration, the sleep duration, or both. This means that the UE that receives the GTS trigger as true may have the same sleep duration. This may help to indicate in a public manner whether there is a correlation between the service arrival patterns of a group of UEs monitoring GC-DCI. In some specific implementations, in the context of GC DCI for WUS, one or more common fields may be used to at least indicate the start duration of PDCCH monitoring after detecting WUS DCI.
[0250] Fig.17 A flow chart of an example of a process 1701 involving network signaling and UE behavior before and after detecting a DCI including a WUS is shown. In this example, the UE is configured to monitor for common DCI including a WUS. After establishing the RRC_CONNECTED state, the UE receives one or more RRC signaling communications from the gNB providing information about the DRX configuration. The RRC signaling may include signaling for monitoring for WUS DCI, other signaling for DCI configuration, or search space association. Upon detecting the WUS DCI, the UE wakes up for PDCCH monitoring for a subsequent duration, such as monitoring for scheduling DCI, and continues according to the configured DRX mode. In some implementations, the WUS DCI indicates a switch to a different BWP.
[0251] The UE may be configured to monitor GC DCI formats for signals such as GTS or WUS in one or more common search spaces (e.g., search space sets), each common search space being associated with a CORESET in the active DL bandwidth portion. As part of the search space set configuration, the UE may obtain one or more of the following: high-level RNTI monitoring parameters to inform the UE to monitor DCI formats with DRX_RNTI in the search space set in a given CORESET; PDCCH monitoring periodicity, e.g., K ≥ 1 symbol / slot; PDCCH monitoring offset, e.g., M ≥ 0 symbol / slot, where M may be less than or equal to K; PDCCH monitoring mode, e.g., one or more initial symbols of a CORESET within a slot or a group of symbols; and PDCCH candidates for each aggregation level. Note that DRX_RNTI is used as the name of the RNTI for the GC DCI format, however, this is only an example and in principle any name for the RNTI may be used.
[0252] In some implementations, although the same search space set may be used to monitor WUS and GTS DCI, a higher layer configuration may be provided for a separate DCI format configuration, such as monitoring GTS DCI with multiple aggregation levels and monitoring WUS DCI with only one aggregation level, thereby reducing complexity and increasing power savings when the UE operates in DRX mode. In addition, the monitoring periodicity may be different for GTS DCI and WUS DCI. For example, during a WUS monitoring window that may be quite short, there may be more than one WUS monitoring opportunity so that the UE does not miss the WUS. For example, once the UE detects a WUS, it may not monitor the WUS at subsequent times. In some implementations, the DCI payload size may be configured by a higher layer via MSI, RMSI, OSI, or RRC signaling. In some implementations, the WUS or GTS may be repeated multiple times so that WUS or GTS detection is achieved with high reliability. The repetition factor may be configured by a higher layer in a UE-specific, cell-specific, or group-specific manner.
[0253] In some implementations, the network may transmit DCI in a code multiplexed sequence. Instead of appending the DCI format with a CRC scrambled by the RNTI, control information may be transmitted in a sequence without a CRC. Sequences with UE-specific control information may be code multiplexed on common time-frequency resources. A group of UEs may monitor corresponding sequences in common time-frequency resources. UE-specific sequences are multiplexed and transmitted in common time-frequency resources.
[0254] Fig.18 A block diagram of an example of using a code multiplexing sequence to transmit control information is shown. In this example, a block diagram of structure 1801 is shown as mapping UE-specific control information to a coded, modulated, and extended sequence multiplexed with symbols of other UEs, and then mapping the composite multiplexed signal of a group of UEs to a common set of REs after scrambling, layer processing, and other steps. In this example, M≥1 bits of the UE's control information payload are encoded as K bits. Repetition coding can be applied, where K can be a multiple of M. The coded bits (e.g., BPSK, QPSK, etc.) are then modulated and subsequently extended by an L-point sequence to produce LK symbols. The sequence may be specific and configured by a higher-layer UE. In one example, the sequence may be obtained based on C-RNTI. Examples of sequences may include Walsh sequences, Zadoff-Chu sequences, Gold sequences, etc. Finally, LK symbols of the UE and other UEs are multiplexed and then mapped to a set of common REs after further processing (such as layer mapping, scrambling, etc.).
[0255] An example of an extended sequence with a length of four for a normal CP is shown in Table 8. In one example, each UE is indicated an index from the group, and different UEs for sequences in a common resource set are indicated different indices by the network.
[0256]
[0257] Table 8
[0258] The examples considered above for UE-specific content transmitted in GC DCI also apply here, for example, an M-bit control information payload may be used to indicate a GTS or WUS trigger, adjust DRX parameters or switch DRX configuration.
[0259] Fig.19A , Fig.19B and Fig.19C Different examples of resource set mapping are shown. Fig.19A A resource set is shown in FIG, where a multiplexing sequence containing UE-specific control information for K UEs is mapped to 4 PRBs in 1 symbol (OS). Fig.19B In , the group is mapped to 2 PRBs in 2 OS. Finally, the group can be mapped to 1 PRB in 4 OS, as Fig.19C shown.
[0260] In each resource set, one or more search spaces may be configured to detect sequences. As part of the search space configuration, the UE may obtain one or more of the following related to the DCI format: the association between the search space and the resource set; the aggregation level; the monitoring periodicity, e.g., K≥1 symbols / slot; the monitoring offset, e.g., M symbols / slot, where e.g., M can be 0<=M<K; and the monitoring pattern, e.g., the first symbol of one or more resource sets within a slot. In some specific implementations, the search space for monitoring the DCI format based on sequences may be monitored only at one aggregation level such as 2, 4, 8, or 16 to reduce complexity.
[0261] In some specific implementations, the resource set may be one of the CORESETs configured in the active DL BWP, and the search space may be one of the common search spaces associated with the CORESET. Thus, as part of the common search space configuration, the network may notify the UE to monitor the DCI format based on the sequences without any RNTI attached in the search space. In other words, as part of the search space configuration, the UE will be notified to monitor the sequence-based DCI format with a given aggregation level in the search space. In some specific implementations, the WUS may be a sequence-based DCI without an RNTI, and the GTS in the DCI may be a PDCCH with an RNTI. This may help ensure low-complexity WUS detection.
[0262] In some specific implementations, if the resource set is different from the CORESET, the location of the resource may be implicitly obtained from the configuration of other resources (such as the resources for SSB or a given CORESET). In some specific implementations, there may be at least one CORESET configured within the DL BWP, and the frequency-domain location of the resource set for monitoring the DCI format in the sequence may be obtained as an offset from the location of the given CORESET. For example, the starting physical resource block (PRB) of the resource set may be obtained as an offset from the edge PRB of the CORESET. In Figure 19A-Figure 19C this case, an offset of 0 is considered. Other parameters of the resource set configuration may be via higher-layer configuration. In some specific implementations, the sequence may be mapped to one or more resource sets with or without repetition. The repetition factor may be configured by higher layers, such as UE-specific or group-based RRC signaling. In some specific implementations, for PDSCH scheduling, the resource set used for transmitting the sequence-based DCI for GTS may be avoided. For example, the PDSCH may be rate-matched around the resource set.
[0263] Reducing unnecessary PDCCH monitoring of some parameters as described above can improve UE power consumption through dynamic DRX mode management. One or more signaling mechanisms can be used to activate or deactivate some other parameters to improve UE power consumption in the presence or absence of in-place active DRX mode operation. Specifically, for one or more of the above-mentioned DCI signaling implementations, one or more of the following parameters may be included in a UE-specific field: activation or deactivation of a secondary carrier (for example, a K≥1 bit field may be used to indicate a carrier ID) and activation or deactivation of a set of UE antennas. In some implementations, a bit field of L≥1 may be used to indicate an index or set of indices of a UE antenna, an RF chain, or both. The network and the UE exchange the UE antenna configuration and the corresponding index of the UE antenna prior to the signaling for activation or deactivation. In some implementations, MACCE signaling may be used instead of DCI-based signaling to activate or deactivate parameters.
[0264] Fig. 20 An example of a DRX-related process is shown. At 2005, the UE receives a DRX configuration from a base station. At 2010, the UE monitors a PDCCH for DCI messages outside of the DRX active time, the DCI messages having a predetermined format configured to provide wake-up signaling. At 2015, the UE receives a DCI message outside of the DRX active time, the DCI message having a predetermined format. At 2020, the UE determines whether to wake up based on the received DCI message.
[0265] The UE power control technique may include using a group common DCI format to signal the UE's WUS information or GTS information on the PDCCH. In some specific implementations, the UE is one of a plurality of UEs, and each UE is configured to monitor the group common DCI format. In some specific implementations, the group common DCI format includes a UE-specific field indicating whether the UE is to be awakened. The technique may include determining whether the UE is to be awakened when a group common DCI format is received outside of the DRX active time. The technique may include determining whether the UE can skip PDCCH monitoring for a predetermined number of opportunities when a group common DCI format is received during the DRX active time.
[0266] A technique for managing the wake-up state and entry into a dormant state of a UE may include: when a group-common DCI message is received outside of a DRX active time and indicates no wake-up, remaining in a dormant state and skipping a predetermined number of DRX cycles; and when a group-common DCI message is received outside of a DRX active time and indicates wake-up, waking up from a dormant state and transitioning to an active time. The technique may include: when a group-common DCI message is received during a DRX active time and indicates wake-up, monitoring a PDCCH; and when a group-common DCI message is received during a DRX active time and indicates entry into dormancy, sleeping for a predetermined duration or skipping PDCCH monitoring. The technique may include sleeping, when a group-common DCI message is received during a DRX active time and indicates entry into dormancy, until the next DRX cycle.
[0267] In some implementations, when a UE receives a group-common DCI message outside of DRX active time, the DCI message includes a UE-specific bit mapped to one or more of the following: a wake-up indication, e.g., whether the UE transitions from external active time to active time; an inter-slot scheduling configuration; a trigger for an RS, such as a CSI-RS, a TRS; an indication of UL resources for a CSI report; activation or deactivation of a carrier or cell; a trigger for BWP switching / adaptation; a number of MIMO layers or antenna adaptations; an indication of a CORESET / search space / candidate for subsequent PDCCH decoding; an indication of a DRX configuration and / or one or more of the DRX configuration parameters; or an indication of the number of DRX cycles to be skipped or active. The inter-slot scheduling configuration may include an indication of a TDRA table from a set of configured TDRA tables, wherein the indicated TDRA table may enable or disable inter-slot scheduling. In some implementations, the inter-slot scheduling configuration may include an indication of a minimum value of K0, which refers to the duration between a PDCCH and a PDSCH in the number of slots. If K0>0, it means cross-slot scheduling, that is, PDSCH and PDCCH are received in different slots.
[0268] In some embodiments, when a UE receives a group-common DCI message during DRX active time, the DCI message includes a UE-specific bit mapped to one or more of the following: an entry into sleep indication, e.g., whether the UE skips PDCCH monitoring or transitions from active time to external active time; a PDCCH skip duration, e.g., the number of time slots that the UE skips PDCCH monitoring; the number of PDCCH monitoring opportunities to be skipped; and activation or deactivation of a carrier or cell.
[0269] These and other techniques may be performed by an apparatus implemented or employed in one or more types of network components, user equipment, or both. In some implementations, one or more non-transitory computer-readable media include instructions for causing an electronic device to perform one or more of the techniques described herein when the instructions are executed by one or more processors of an electronic device. An apparatus may include one or more processors and one or more computer-readable media, the computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more of the techniques described herein.
[0270] In different specific implementations, the methods described herein can be implemented in software, hardware, or a combination thereof. In addition, the order of the blocks of the method can be changed, and various elements can be added, reordered, combined, omitted, modified, etc. Various modifications and changes can be made, which will be apparent to those skilled in the art who benefit from this disclosure. The various specific implementations described herein are intended to be illustrative and not restrictive. Many variations, modifications, additions, and improvements are possible. Therefore, multiple examples can be provided for the components described herein as a single example. The boundaries between various components, operations, and data repositories are arbitrary to a certain extent, and specific operations are shown in the context of a specific exemplary configuration. Other allocations of functions are contemplated, and they may fall within the scope of the appended claims. Finally, the structure and function presented as discrete components in the exemplary configuration may be implemented as a combined structure or component.
[0271] The methods described herein may be implemented in a circuit, such as one or more of an integrated circuit, a logic circuit, a processor (shared, dedicated, or group) and / or a memory (shared, dedicated, or group), an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), or some combination thereof. Examples of processors may include Apple A series processors, Architecture Core TM Processors, such as Intel processors, ARM processors, AMD processors, and Qualcomm processors. Other types of processors are possible. In some specific implementations, the circuit can execute one or more software or firmware programs to provide at least some of the functions. The term "circuit" can also refer to a combination of one or more hardware elements and a program code for executing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code can be referred to as a specific type of circuit. The circuit can also include a radio circuit, such as a transmitter, a receiver, or a transceiver.
[0272] A plurality of specific implementations have been described. However, it should be understood that various modifications may be made. Elements in one or more specific implementations may be combined, deleted, modified or supplemented to form other specific implementations. As another example, the logic flow shown in the accompanying drawings does not require the specific order or sequential order shown to achieve the desired result. In addition, other steps may be provided or steps may be eliminated from the process, and other components may be added to the system or removed from the system. Therefore, other specific embodiments are within the scope of the following claims.< / crc> < / crc>
Claims
1. A method for wireless communication, the method comprising: receiving a configuration message indicating a wake-up configuration associated with a configured discontinuous reception (DRX) operation between a user equipment (UE) and a base station; determining a bandwidth part BWP to be monitored and a time period to be monitored for wake-up signal monitoring based at least on the wake-up configuration, wherein the time period occurs during a period configured as an off-time of a DRX operation based at least on the configuration; monitoring the BWP and a wake-up signal within the time period, wherein the wake-up signal indicates whether the UE is turned on or off within a next on time of the configured DRX operation; as well as Whether to turn on within the next turn-on time is determined based at least on the monitoring.
2. The method according to claim 1, wherein the monitoring comprises: receiving a downlink control information (DCI) message via a physical downlink control channel (PDCCH) outside the active time of the configured DRX operation; as well as The wake-up signal is detected within the DCI message.
3. The method of claim 2, wherein the configuration message is received via radio resource control (RRC) signaling, wherein the configuration message includes an offset parameter that specifies an offset relative to a start of a subsequent on-duration associated with the configured DRX operation, wherein the configuration message includes a payload size of the DCI message, and wherein the configuration message provides information about one or more search space sets in which to monitor the DCI message.
4. The method of claim 2, wherein the DCI message is associated with a group-common DCI format, and wherein the UE is one of a plurality of UEs, and each of the plurality of UEs is configured to monitor the group-common DCI format, and wherein the group-common DCI format includes a UE-specific field indicating whether the UE is to wake up.
5. The method according to claim 4, comprising: waking up from a dormant state and transitioning to an active state within the next on time based at least on the DCI message indicating the wake-up of the UE; or Based at least on the DCI message not indicating wake-up of the UE, remaining in the sleep state and skipping the next on time.
6. The method of claim 4, wherein the group common DCI format comprises one or more UE-specific bits mapped to one or more of: a wake-up indication, an inter-slot scheduling configuration, a triggering of a reference signal, an indication of uplink resources for a channel state report, an activation of a cell, a deactivation of a cell, an activation of a carrier, a deactivation of a carrier, a triggering of a BWP switching, PDCCH decoding information, a DRX configuration, or an indication of the number of DRX cycles to be skipped or activated.
7. The method according to claim 2, comprising: During the next on-time, one or more additional DCI messages are monitored, the additional DCI messages having a predetermined format, the predetermined format being configured to provide sleep entry signaling and including one or more UE-specific bits mapped to one or more of the following: a sleep entry indication for controlling whether the UE skips PDCCH monitoring or transitions from active time to external active time, the number of PDCCH monitoring opportunities to be skipped, the PDCCH skipping duration, cell activation, cell deactivation, carrier activation, or carrier deactivation.
8. An apparatus for wireless communication, the apparatus comprising: one or more processors; and A memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including: receiving a configuration message indicating a wake-up configuration associated with a configured discontinuous reception (DRX) operation between a user equipment (UE) and a base station; determining, based at least on the wake-up configuration, a bandwidth part BWP to be monitored and a time period to be monitored for wake-up signal monitoring, wherein the time period occurs during a period configured as an off-time of a DRX operation based at least on the configuration; monitoring the BWP and a wake-up signal within the time period, wherein the wake-up signal indicates whether the UE is turned on or off within a next on time of the configured DRX operation; as well as Whether to turn on within the next turn-on time is determined based at least on the monitoring.
9. The apparatus of claim 8, wherein the BWP is a first BWP, wherein the next on-time is associated with a second BWP, and wherein the configuration message includes an indication for BWP switching.
10. The apparatus of claim 8, wherein the monitoring comprises: receiving a downlink control information (DCI) message via a physical downlink control channel (PDCCH) outside the active time of the configured DRX operation; as well as The wake-up signal is detected within the DCI message.
11. The apparatus of claim 10, wherein the configuration message is received via radio resource control (RRC) signaling, wherein the configuration message includes an offset parameter that specifies an offset relative to a start of a subsequent on-duration associated with the configured DRX operation, wherein the configuration message includes a payload size of the DCI message, and wherein the configuration message provides information about one or more search space sets in which to monitor the DCI message.
12. The apparatus of claim 10, wherein determining whether to turn on within the next on time based at least on the monitoring comprises determining whether to allow the UE to skip PDCCH monitoring for a predetermined number of occasions based at least on the DCI message.
13. The apparatus of claim 10, wherein the DCI message is associated with a group-common DCI format, and wherein the UE is one of a plurality of UEs, and each of the plurality of UEs is configured to monitor the group-common DCI format, and wherein the group-common DCI format includes a UE-specific field indicating whether the UE is to wake up.
14. The apparatus according to claim 13, comprising: waking up from a dormant state and transitioning to an active state within the next on time based at least on the DCI message indicating the wake-up of the UE; or Based at least on the DCI message not indicating wake-up of the UE, remaining in the sleep state and skipping the next on time.
15. The apparatus of claim 13, wherein the group common DCI format comprises one or more UE-specific bits mapped to one or more of: a wake-up indication, an inter-slot scheduling configuration, a triggering of a reference signal, an indication of uplink resources for a channel state report, an activation of a cell, a deactivation of a cell, an activation of a carrier, a deactivation of a carrier, a triggering of a BWP switching, PDCCH decoding information, a DRX configuration, or an indication of a number of DRX cycles to be skipped or activated.
16. The apparatus according to claim 13, comprising: During the next on-time, one or more additional DCI messages are monitored, the additional DCI messages having a predetermined format, the predetermined format being configured to provide sleep entry signaling and including one or more UE-specific bits mapped to one or more of the following: a sleep entry indication for controlling whether the UE skips PDCCH monitoring or transitions from active time to external active time, the number of PDCCH monitoring opportunities to be skipped, the PDCCH skipping duration, cell activation, cell deactivation, carrier activation, or carrier deactivation.
17. An apparatus for wireless communication, the apparatus comprising: one or more processors; and A memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including: transmitting a configuration message indicating a wake-up configuration associated with a configured discontinuous reception (DRX) operation between a user equipment (UE) and a base station, wherein the configuration message provides information about a bandwidth part (BWP) to be monitored and a time period, wherein the time period occurs during a period configured as an off-time based at least on the configured DRX operation; and The BWP and a wake-up signal within the time period are transmitted, wherein the wake-up signal indicates whether the UE is turned on or off within a next on time of the configured DRX operation.
18. The apparatus of claim 17, wherein the transmitting the wake-up signal comprises: A downlink control information (DCI) message is transmitted via a physical downlink control channel (PDCCH) outside the active time of the configured DRX operation, wherein the DCI message includes the wake-up signal.
19. The apparatus of claim 18, wherein transmitting the configuration message comprises transmitting the configuration message via radio resource control (RRC) signaling, wherein the configuration message comprises an offset parameter specifying an offset relative to a start of a subsequent on-duration associated with the configured DRX operation, wherein the configuration message comprises a payload size of the DCI message, and wherein the configuration message provides information about one or more search space sets in which to monitor the DCI message.
20. The apparatus of claim 18, wherein the DCI message is associated with a group-common DCI format, and wherein the UE is one of a plurality of UEs, and each of the plurality of UEs is configured to monitor the group-common DCI format, and wherein the group-common DCI format includes a UE-specific field indicating whether the UE is to wake up.
