System, method and apparatus for signaling for power conservation

Abstract

The present invention provides systems, methods, devices and apparatus for power saving. In at least one embodiment, a device may be configured for a discontinuous reception (DRX) mode and further receive a signal indicating whether to wake up and / or may receive a signal indicating whether to enter sleep. The signaling may be implemented as group-specific signaling.

Description

[0001] Related Applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 732,466 filed on September 17, 2018, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] Various embodiments relate generally to the field of wireless communications. Background Art

[0004] Energy efficiency is critical for the operation of UEs (e.g., 5G / NR UEs), which may have a different range of supported applications compared to LTE devices. In particular, energy consumption should be lower when the UE does not expect / receive data. For example, 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 RRC_connected mode, which does not result in any data transmission, contributes to a significant portion of UE power consumption. Therefore, some network-assisted mechanisms may be used to reduce unnecessary PDCCH monitoring operations and trigger UE dormancy whenever possible.

[0005] Furthermore, in NR, control channel monitoring, operating bandwidth, and many other transmission parameters are configured specifically for the UE. Therefore, it is important to explore UE-specific signaling mechanisms that address individual UE requirements and configurations. On the other hand, allocating control channel resources in a UE-specific manner may not always be feasible, such as when the load in the cell is high. If a group of UEs can monitor common time-frequency resources, the probability of control channel blocking and / or system overhead can be reduced. Summary of the invention

[0006] Various exemplary embodiments of the present disclosure include control channel signaling mechanisms, wherein a group of UEs monitor common channel resources, and control information may have grouped / multiplexed UE-specific information, or may also have group common information for the group of UEs. In various examples, various or several L1 control channel signaling mechanisms may be implemented to adapt DRX configuration parameters and / or trigger UEs to enter sleep or wake up behavior. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In the accompanying drawings, similar reference characters generally indicate the same parts throughout the different views. The accompanying drawings are not necessarily drawn to scale, but emphasis is generally placed on illustrating the principles of the invention. In the following description, various embodiments of the invention are described with reference to the following drawings, in which:

[0008] Figure 1The architecture of a system of a network according to various exemplary embodiments of the present disclosure is shown.

[0009] Figure 2 The architecture of a system of a network according to various exemplary embodiments of the present disclosure is shown.

[0010] Figure 3 Examples of infrastructure equipment according to various exemplary embodiments of the present disclosure are shown.

[0011] Figure 4 Examples of platforms (or "devices") according to various exemplary embodiments of the present disclosure are shown.

[0012] Figure 5 Exemplary components of a baseband circuit and a radio front end module are shown according to various embodiments.

[0013] Figure 6 Exemplary interfaces of baseband circuitry according to various embodiments are shown.

[0014] Figure 7 An illustration of a control plane protocol stack according to various exemplary embodiments of the present disclosure is shown.

[0015] Figure 8 is an illustration of a user plane protocol stack according to various embodiments.

[0016] Fig. 9 Components of a core network according to various exemplary embodiments of the present disclosure are shown.

[0017] Fig.10 Block diagrams showing components according to various exemplary embodiments of the present disclosure are shown.

[0018] FIG. 11A to FIG. 14C and Fig.17 A flow chart of monitoring and signaling according to various exemplary embodiments of the present disclosure is shown.

[0019] Figure 15 to Figure 16 and Fig.18 Exemplary message formats according to various exemplary embodiments of the present disclosure are shown.

[0020] Fig.17 A flow chart of monitoring and including a wake-up signal according to various exemplary embodiments of the present disclosure is shown.

[0021] Fig.19 An exemplary signaling flow diagram according to various exemplary embodiments of the present disclosure is shown.

[0022] Fig. 20An exemplary flow chart for processing and mapping UE-specific control information according to various exemplary embodiments of the present disclosure is shown.

[0023] Fig.21 A block diagram illustrating an exemplary set of resources according to various exemplary embodiments of the present disclosure is shown.

[0024] Fig. 22 An example of resource set RE mapping is shown.

[0025] describe

[0026] The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and embodiments in which the invention may be practiced.

[0027] The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any implementation or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other implementations or designs.

[0028] Figure 1The architecture of a system 100 of a network according to some embodiments is shown. The system 100 is shown to include user equipment (UE) 101 and UE 102. As used herein, the term "user equipment" or "UE" may refer to a device of a remote user having radio communication capabilities and that may describe network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface. In this example, UEs 101 and 102 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile 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 (IC), heads-up display (HUD) devices, on-board diagnostics (OBD) devices, dashboard mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" devices, machine type communication (MTC) devices, machine to machine (M2M), Internet of Things (IoT) devices, etc.

[0029] In some embodiments, either UE 101 and UE 102 may include an Internet of Things (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 machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communication, a sensor network, or an IoT network. 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, status updates, etc.) to facilitate connectivity to the IoT network.

[0030] UE 101 and UE 102 may be configured to connect (e.g., communicatively couple) a radio access network (RAN) 110. RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a Next Generation RAN (NGRAN), or some other type of RAN. UE 101 and UE 102 utilize connections (or channels) 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in further detail below). As used herein, the term "channel" may refer to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent to a "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" and / or any other similar term representing a path or medium through which data is transmitted. In addition, the term "link" may refer to a connection for transmitting and receiving information between two devices over a radio access technology (RAT). In this example, connection 103 and connection 104 are shown as air interfaces to achieve communication coupling, and can be consistent with cellular communication protocols, such as the Global System for Mobile Communications (GSM) protocol, the Code Division Multiple Access (CDMA) network protocol, the Push-to-Talk (PTT) protocol, the Cellular PTT protocol (POC), the Universal Mobile Telecommunications System (UMTS) protocol, the 3GPP Long Term Evolution (LTE) protocol, the Fifth Generation (5G) protocol, the New Radio (NR) protocol, etc.

[0031] In this embodiment, UE 101 and UE 102 may also exchange communication data directly via ProSe interface 105. ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface including one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH). In various specific implementations, SL interface 105 may be used for vehicle applications and communication technologies, which are generally referred to as V2X systems. V2X is a communication mode in which UEs (e.g., UE 101, 102) communicate with each other directly through PC5 / SL interface 105, and may occur when UE 101, 102 are served by RAN nodes 111, 112 or when one or more UEs are outside the coverage area of ​​RAN 110. V2X can be divided into four different types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). These V2X applications may use "cooperative awareness" to provide smarter services to end users. For example, vehicle UEs (vUEs) 101, 102, RAN nodes 111, 112, application servers 130, and pedestrian UEs 101, 102 may collect knowledge of their local environment (e.g., information received from other vehicles or nearby sensor equipment) to process and share this knowledge in order to provide smarter services, such as cooperative collision warnings, autonomous driving, etc. In these specific implementations, the UEs 101, 102 may be implemented / used as vehicle embedded communication systems (VECS) or vUEs.

[0032] UE 102 is shown configured to access access point (AP) 106 (also referred to as "WLAN node 106", "WLAN 106", "WLAN termination 106", "WT 106", etc.) via connection 107. Connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 106 may include wireless fidelity router. In this example, AP 106 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 102, RAN 110, and AP 106 may be configured to utilize LTE-WLAN aggregation (LWA) operation and / or WLAN LTE / WLAN radio level operation integrated with IPsec tunnel (LWIP). LWA operation may involve UE 102 in RRC_CONNECTED configured by RAN nodes 111, 112 to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 102 using WLAN radio resources (e.g., connection 107) via an Internet Protocol Security (IPsec) protocol tunnel to authenticate and encrypt data packets (e.g., Internet Protocol (IP) data packets) sent over connection 107. IPsec tunneling may include encapsulating the entire original IP data packet and adding a new data packet header, thereby protecting the original header of the IP data packet.

[0033] The RAN 110 may include one or more access nodes that enable connection 103 and connection 104. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as base stations (BS), Node Bs, evolved Node Bs (eNBs), next generation Node Bs (gNBs), 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). The term "roadside unit" or "RSU" may refer to any transport infrastructure entity implemented in or by a gNB / eNB / RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a "UE-type RSU" and an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU." The RAN 110 may include one or more RAN nodes (e.g., macro RAN node 111) for providing macro cells and one or more RAN nodes (e.g., low power (LP) RAN node 112) for providing femto cells or pico cells (e.g., cells having a smaller coverage area, smaller user capacity, or higher bandwidth than macro cells).

[0034] Either of the RAN node 111 and the RAN node 112 may terminate the air interface protocol and may be the first point of contact for the UE 101 and the UE 102. In some embodiments, either of the RAN nodes 111 and 112 may fulfill 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, data packet scheduling, and mobility management.

[0035] According to some embodiments, UE 101 and UE 102 may be configured to communicate with each other or with any of RAN nodes 111 and 112 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, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0036] In some embodiments, a downlink resource grid may be used for downlink transmissions from either of RAN node 111 and RAN node 112 to UE 101 and UE 102, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource 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. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements. In the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0037] The physical downlink shared channel (PDSCH) may convey user data and higher layer signaling to UE 101 and UE 102. The physical downlink control channel (PDCCH) may carry information about, among other things, transport formats and resource allocations related to the PDSCH channel. It may also inform UE 101 and UE 102 of transport formats, resource allocations, and H-ARQ (Hybrid Automatic Repeat Request) information related to uplink shared channels. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 102 within a cell) may be performed at either RAN node 111 or RAN node 112 based on channel quality information fed back from either UE 101 or UE 102. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of UE 101 and UE 102.

[0038] PDCCH can use control channel elements (CCE) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE can correspond to six resource element groups (REGs). Each REG includes a resource block in an OFDM symbol. Depending on the size of the downlink control information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. Different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, 8, or 16) can be used for the transmission of PDCCH.

[0039] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize an enhanced physical downlink control channel ("EPDCCH") that uses PDSCH resources for control information transmission. One or more enhanced control channel elements (ECCEs) may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as enhanced resource element groups (EREGs). In some cases, ECCEs may have other numbers of EREGs.

[0040] RAN 110 is shown as being communicatively coupled to a core network (CN) 120 via an S1 interface 113. In various embodiments, CN 120 may be an evolved packet core (EPC) network, a next generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 113 is divided into two parts: an S1-U interface 114, which carries communication data between RAN node 111 and RAN node 112 and a serving gateway (S-GW) 122; and an S1 mobility management entity (MME) interface 115, which is a signaling interface between RAN node 111 and RAN node 112 and MME 121.

[0041] In this embodiment, CN 120 includes MME 121, S-GW 122, Packet Data Network (PDN) Gateway (P-GW) 123 and Home Subscriber Server (HSS) 124. MME 121 can be similar in function to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 121 can manage mobility aspects in access, such as gateway selection and tracking area list management. HSS 124 can include a database for network users, which includes subscription-related information for supporting network entities to handle communication sessions. Depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc., CN 120 may include one or more HSS 124. For example, HSS 124 can provide support for routing / roaming authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0042] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 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.

[0043] The P-GW 123 may terminate the SGi interface towards the PDN. The P-GW 123 may route data packets between the EPC network 120 and an external network such as a network including an application server 130 (alternatively referred to as an application function (AF)) via an Internet Protocol (IP) interface 125. Generally, the application server 130 may be an element that provides applications that use IP bearer resources with a core network (e.g., UMTS packet service (PS) domain, LTE PS data service, etc.). In this embodiment, the P-GW 123 is shown as being communicatively coupled to the application server 130 via an IP communication interface 125. The application server 130 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 101 and UE 102 via the CN 120.

[0044] The P-GW 123 may also be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is a policy and charging control element of the CN 120. In a non-roaming scenario, there may be a single PCRF in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of a UE. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with an IP-CAN session of a UE: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in a visited public land mobile network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 130 via the P-GW 123. The application server 130 may signal the PCRF 126 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. PCRF 126 may configure the rules to a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI), which initiates the QoS and charging specified by application server 130 .

[0045] Figure 2 The architecture of a system 200 of a network according to some embodiments is shown. The system 200 is shown to include: a UE 201, which may be the same or similar to the previously discussed UE 101 and UE 102; a RAN node 211, which may be the same or similar to the previously discussed RAN node 111 and RAN node 112; a data network (DN) 203, which may be, for example, an operator service, Internet access, or a third-party service; and a 5G core network (5GC or CN) 220.

[0046] CN 220 may include an authentication server function (AUSF) 222; an access and mobility management function (AMF) 221; a session management function (SMF) 224; a network exposure function (NEF) 223; a policy control function (PCF) 226; a network function (NF) repository function (NRF) 225; a unified data management (UDM) 227; an application function (AF) 228; a user plane function (UPF) 202; and a network slice selection function (NSSF) 229.

[0047] UPF 202 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with DN 203, and a branch point to support multi-host PDU sessions. UPF 202 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 downlink packet buffering and downlink data notification triggering. UPF 202 may include an uplink classifier to support routing traffic to the data network. DN 203 may represent various network operator services, Internet access, or third-party services. DN 203 may include or be similar to the application server 130 discussed previously. UPF 202 may interact with SMF 224 via the N4 reference point between SMF 224 and UPF 202.

[0048] AUSF 222 may store data for authenticating UE 201 and handle authentication-related functions. AUSF 222 may facilitate a common authentication framework for various access types. AUSF 222 may communicate with AMF 221 via the N12 reference point between AMF 221 and AUSF 222; and may communicate with UDM 227 via the N13 reference point between UDM 227 and AUSF 222. In addition, AUSF 222 may present an interface based on Nausf services.

[0049] AMF 221 may be responsible for registration management (e.g., responsible for registering UE 201, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. AMF 221 may be the termination point of the N11 reference point between AMF 221 and SMF 224. AMF 221 may provide transport for session management (SM) messages between UE 201 and SMF 224, and act as a transparent proxy for routing SM messages. AMF 221 may also provide a communication channel between UE 201 and SMS function (SMSF) ( Figure 2 The AMF 221 may provide for the transmission of short message service (SMS) messages between the (R)AN 211 and the AMF 221 (not shown). The AMF 221 may act as a security anchor function (SEA), which may include interaction with the AUSF 222 and the UE 201, and receiving intermediate keys established as a result of the UE 201 authentication process. In the case of using UMTS User Identity Module (USIM)-based authentication, the AMF 221 may retrieve security material from the AUSF 222. The AMF 221 may also include a secure content management (SCM) function that receives keys from the SEAF for deriving access network-specific keys. In addition, the AMF 221 may be a termination point for the RAN CP interface, which may include or be the N2 reference point between the (R)AN 211 and the AMF 221; and the AMF 221 may be a termination point for NAS (N1) signaling, and perform NAS encryption and integrity protection.

[0050] The AMF 221 may also support NAS signaling with the UE 201 via an N3 interworking function (IWF) interface. The N3 IWF may be used to provide access to untrusted entities. The N3 IWF may be a termination point for the N2 interface between the (R) AN 211 and the AMF 221 for the control plane, and may be a termination point for the N3 reference point between the (R) AN 211 and the UPF 202 for the user plane. Thus, the AMF 221 may process N2 signaling for PDU sessions and QoS from the SMF 224 and the AMF 221, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and enforce QoS requirements corresponding to N3 packet markings, which may take 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 201 and the AMF 221 via the N1 reference point between the UE 201 and the AMF 221, and relay uplink and downlink user plane packets between the UE 201 and the UPF 202. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 201. The AMF 221 may present an interface based on the Namf service, and may be an N14 reference point between the two AMFs 221 and an AMF 221 and a 5G Equipment Identity Register (5G-EIR) ( Figure 2 The termination point of the N17 reference point between the two (not shown).

[0051] SMF 224 may be responsible for session management (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes). SMF 224 may also allocate and manage UE IP addresses (including optional authorization), select and control UP functions, and configure traffic steering at UPF 202 to route traffic to the correct destination. SMF 224 may also terminate the interface with the policy control function, control part of the policy enforcement and QoS, and perform lawful interception (e.g., for SM events and interfaces with LI systems). SMF 224 may also terminate the SM portion of the NAS message, provide downlink data notification, and initiate AN-specific SM information sent to the AN via the AMF over N2, and determine the session and the service continuity (SSC) mode of the session.

[0052] SMF 224 may include the following roaming functions: handling local execution to apply QoS SLA (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (for SM events and interface with LI system, in VPLMN); and support interaction with external DN to transmit signaling for PDU session authorization / authentication through external DN. In roaming scenarios, an N16 reference point between two SMFs 224 may be included in the system 200, which may be located between an SMF 224 in a visited network and another SMF 224 in a home network. In addition, SMF 224 may present an interface based on Nsmf services.

[0053] NEF 223 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 228), edge computing or fog computing systems, etc. In such embodiments, NEF 223 may authenticate, authorize and / or restrict AF. NEF 223 may also convert information exchanged with AF 228 and information exchanged with internal network functions. For example, NEF 223 may convert between AF service identifiers and internal 5GC information. NEF 223 may also receive information from other network functions (NFs) based on their exposure capabilities. The information may be stored at NEF 223 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 223 and / or used for other purposes such as analysis. In addition, NEF 223 may present an interface based on Nnef services.

[0054] NRF 225 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 225 also maintains information of available NF instances and the services they support. 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 225 may present an interface based on Nnrf services.

[0055] The PCF 226 may provide policy rules for control plane functions to enforce these functions, and may also support a unified policy framework to manage network behavior. The PCF 226 may also implement a front end (FE) to access subscription information related to policy decisions in the unified data repository (UDR) of the UDM 227. The PCF 226 may communicate with the AMF 221 via the N15 reference point between the PCF 226 and the AMF 221, which may include the PCF 226 in the visited network and the AMF 221 in the case of a roaming scenario. The PCF 226 may communicate with the AF 228 via the N5 reference point between the PCF 226 and the AF 228; and communicate with the SMF 224 via the N7 reference point between the PCF 226 and the SMF 224. The system 200 and / or the CN 220 may also include an N24 reference point between the PCF 226 (in the home network) and the PCF 226 in the visited network. Additionally, PCF 226 may present an interface based on Npcf services.

[0056] The UDM 227 may process subscription-related information to support the handling of communication sessions by network entities, and may store subscription data of the UE 201. For example, the subscription data may be transmitted via the UDM 227 and the AMF 221 ( Figure 2 The N8 reference point between the UDM 227 and the AMF 221 transmits subscription data between the UDM 227 and the AMF 221. The UDM 227 may include two parts: an application FE and a user data repository (UDR) ( Figure 2FE and UDR are not shown). The UDR may store subscription data and policy data of the UDM 227 and PCF 226, and / or structured data for exposure of the NEF 223 and application data (including packet flow descriptions (PFDs) for application detection, application request information of multiple UEs 201). A Nudr service-based interface may be presented by the UDR to allow the UDM 227, PCF 226, and NEF 223 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of changes to related data in the UDR. The UDM 227 may include a UDM FE, 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-FE accesses the subscription information stored in the UDR and performs authentication credential processing; user identity processing; access authorization; registration / mobility management; and subscription management. The UDR may interact with the SMF 224 via the N10 reference point between the UDM 227 and the SMF 224. UDM 227 may also support SMS management. SMS-FE implements similar application logic as described above. In addition, UDM 227 may present an interface based on Nudm services.

[0057] AF 228 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 5GC and AF 228 to provide information to each other via NEF 223, which can be used for edge computing implementation. In such implementations, network operators and third-party services can be hosted near the UE 201 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 202 near UE 201 and perform traffic steering from UPF 202 to DN 203 via N6 interface. This can be based on UE subscription data, UE location and information provided by AF 228. In this way, AF 228 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 228 is considered a trusted entity, the network operator can allow AF 228 to interact directly with the relevant NF. In addition, AF228 can present an interface based on Naf services.

[0058] NSSF 229 may select a set of network slice instances to serve UE 201. If necessary, NSSF 229 may also determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI). NSSF229 may also determine the AMF set, or a list of candidate AMFs 221, to serve UE 201 based on appropriate configuration and possibly by querying NRF 225. The selection of a set of network slice instances for UE 201 may be triggered by AMF 221, where UE 201 registers by interacting with NSSF 229, which may cause changes to AMF 221. NSSF 229 may interact with AMF 221 via the N22 reference point between AMF 221 and NSSF229; and may communicate via the N31 reference point ( Figure 2 The NSSF 229 may communicate with another NSSF 229 in the visited network (not shown). In addition, the NSSF 229 may present an interface based on the Nnssf service.

[0059] As previously mentioned, CN 220 may include SMSF, which may be responsible for SMS subscription checking and verification, and delivering SM messages to / from UE 201 to / from other entities, such as Short Message Service (SMS)-Global System for Mobile Communications (GMSC) / Interworking Mobile Switching Center (IWMSC) / SMS router. SMS may also interact with AMF 221 and UDM 227 for notification procedures so that UE 201 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 227 when UE 201 is available for SMS).

[0060] CN 220 may also include Figure 2 Other elements not shown, such as data storage system / architecture, 5G equipment identity register (5G-EIR), security edge protection proxy (SEPP), etc. The data storage system may include structured data storage network function (SDSF), unstructured data storage network function (UDSF), etc. Any NF can communicate with any NF and UDSF ( Figure 2 The N18 reference point between the NF and the NF (not shown) stores or retrieves unstructured data in or from the UDSF (e.g., UE context). Individual NFs may share a UDSF for storing their respective unstructured data, or individual NFs may each have their own UDSF located at or near a single NF. In addition, the UDSF may present an interface based on the Nudsf service ( Figure 2(not shown). The 5G-EIR may be a NF that checks the status of the Permanent Equipment Identifier (PEI) to determine whether to blacklist a specific device / entity from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.

[0061] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Figure 2 These interfaces and reference points are omitted. In one embodiment, CN 220 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 121) and AMF 221 to enable interworking between CN 220 and CN 120. Other example interfaces / 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; and an N31 reference point between an NSSF in a visited network and an NSSF in a home network.

[0062] In yet another example, the system 200 may include a plurality of RAN nodes 211, wherein an Xn interface is defined between two or more RAN nodes 211 (e.g., gNB, etc.) connected to the 5GC 220, and the RAN node 211 (e.g., gNB) and the eNB (e.g., Figure 1RAN nodes 111), and / or between two eNBs connected to the 5GC 220. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 201 in connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected mode between one or more RAN nodes 211. The mobility support may include context transfer from the old (source) serving RAN node 211 to the new (target) serving RAN node 211; and control of the user plane tunnel between the old (source) serving RAN node 211 and the new (target) serving RAN node 211. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer for carrying user plane PDUs on top of a UDP and / or IP layer. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on an SCTP layer. The SCTP layer may be located on top of the IP layer. The SCTP layer provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0063] Figure 3 An example of infrastructure equipment 300 according to various embodiments is shown. Infrastructure equipment 300 (or "system 300") may be implemented as a base station, a radio head, a RAN node, etc., such as RAN nodes 111 and 112 and / or AP 106 previously shown and described. In other examples, system 300 may be implemented in or by a UE, an application server 130, and / or any other element / device discussed herein. System 300 may include one or more of the following: application circuit 305, baseband circuit 310, one or more radio front-end modules 315, memory circuit 320, power management integrated circuit (PMIC) 325, power tee circuit 330, network controller circuit 335, network interface connector 340, satellite positioning circuit 345, and user interface 350. In some embodiments, device 300 may include additional elements, such as, for example, memory / storage, display, camera, sensor, or input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuitry may be separately included in more than one device for a Cloud-RAN (C-RAN) implementation).

[0064] As used herein, the term "circuit" may refer to, be or include hardware components such as electronic circuits, logic circuits, processors (shared, dedicated or group) and / or memories (shared, dedicated or group) configured to provide the described functions, application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs or programmable systems on chip (SoCs)), digital signal processors (DSPs), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. In addition, the term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing 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 may be referred to as a specific type of circuit.

[0065] The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with "processor circuitry", and may be referred to as "processor circuitry". As used herein, the term "processor circuitry" may refer to, be, or include a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations; and recording, storing, and / or transmitting digital data. The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).

[0066] In addition, various components of the core network 120 (or the previously discussed CN 220) may be referred to as "network elements". The term "network element" may describe a physical or virtual device used to provide wired or wireless communication network services. The term "network element" may be considered and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, wireless network controller, wireless access network equipment, gateway, server, virtualized network function (VNF), network function virtualization infrastructure (NFVI), etc.

[0067] The application circuit 305 may include one or more central processing unit (CPU) cores and one or more of the following: cache memory, a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, 2C or general programmable serial interface module, real-time clock (RTC), timer-counter including interval timer and watchdog timer, general input / output (I / O or IO), memory card controller such as secure digital (SD) multimedia card (MMC) or similar products, universal serial bus (USB) interface, mobile industry processor interface (MIPI) interface and joint test access group (JTAG) test access port. As an example, application circuit 305 may include one or more Intel or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or processor; etc. In some embodiments, system 300 may not utilize application circuit 305, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0068] Additionally or alternatively, the application circuit 305 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as field programmable gate arrays (FPGAs), etc.; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs, such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 305 may include logic blocks or logic structures including other interconnected resources that may be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 305 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in lookup tables (LUTs), etc.

[0069] Baseband circuit 310 can be implemented as, for example, a solder-in substrate, which includes 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. Although not shown, baseband circuit 310 may include one or more digital baseband systems, which may be coupled to a CPU subsystem, an audio subsystem, and an interface subsystem via an interconnect subsystem. The digital baseband subsystem may also be coupled to a digital baseband interface and a mixed signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a digital signal processing 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, and / or other similar components. In one aspect of the disclosure, baseband circuitry 310 may include protocol processing circuitry having one or more control circuit instances (not shown) to provide control functionality for digital baseband circuitry and / or radio frequency circuitry (eg, radio front end module 315).

[0070] The user interface circuit 350 may include one or more user interfaces designed to enable a user to interact with the system 300 or a peripheral component interface designed to enable a peripheral component to interact with the system 300. 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, 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.

[0071] The radio front end module (RFEM) 315 may include a millimeter wave 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 millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 315. The RFEM 315 may combine both millimeter wave antennas and sub-millimeter wave antennas.

[0072] The memory circuit 320 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM), a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as a "flash memory"), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 320 may be implemented as one or more of: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0073] The PMIC 325 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 330 may provide power drawn from a network cable to provide both power and data connections for the infrastructure equipment 300 using a single cable.

[0074] The network controller circuit 335 may provide a connection to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on a multi-protocol label switching (MPLS), or some other suitable protocol. A physical connection may be used to provide a network connection to / from the infrastructure equipment 300 via a network interface connector 340, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 335 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some specific implementations, the network controller circuit 335 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0075] The positioning circuit 345 may include circuits for receiving and decoding signals transmitted by one or more navigation satellite constellations of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) may 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., navigation using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc.), etc. The positioning circuit 345 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc., to facilitate over-the-air (OTA) communications) to communicate with components of a positioning network such as navigation satellite constellation nodes.

[0076] A node or satellite of a navigation satellite constellation ("GNSS node") may provide a positioning service by continuously transmitting or broadcasting GNSS signals along a line of sight, which a GNSS receiver (e.g., positioning circuit 345 and / or positioning circuit implemented by UE 101, UE 102, etc.) may use to determine their GNSS position. The GNSS signal may include a pseudo-random code (e.g., a sequence of ones and zeros) known to the GNSS receiver and a message including a transmission time (ToT) of a code period (e.g., a defined point in the pseudo-random code sequence) and the GNSS node position at the ToT. The GNSS receiver may monitor / measure GNSS signals transmitted / broadcasted by multiple GNSS nodes (e.g., four or more satellites) and solve various formulas to determine the corresponding GNSS position (e.g., spatial coordinates). The GNSS receiver also implements a clock that is generally less stable and less accurate than the atomic clock of the GNSS node, and the GNSS receiver may use the measured GNSS signal to determine the deviation of the GNSS receiver from the true time (e.g., the offset of the GNSS receiver clock relative to the GNSS node time). In some embodiments, positioning circuitry 345 may include a micro technology for positioning, navigation, and timing (micro-PNT) IC that performs position tracking / estimation using a master timing clock without GNSS assistance.

[0077] The GNSS receiver may measure the time of arrival (ToA) of GNSS signals from multiple GNSS nodes based on its own clock. The GNSS receiver may determine the time of flight (ToF) value of each received GNSS signal based on the ToA and ToT, and then may determine the three-dimensional (3D) position and clock bias based on the ToF. The 3D position may then be converted to latitude, longitude, and altitude. The positioning circuit 345 may provide data to the application circuit 305, which may include one or more of position data or time data. The application circuit 305 may use the time data to synchronize operations with other radio base stations (e.g., RAN nodes 111, 112, 211, etc.).

[0078] Figure 3 The components shown can communicate with each other using interface circuits. As used herein, the term "interface circuit" may refer to, be part of, or include a circuit that provides information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an input / output (I / O) interface, a peripheral component interface, a network interface card, etc. Any suitable bus technology can be used in various specific implementations, which may include any number of technologies, including industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus can be a proprietary bus, for example, used in a SoC-based system. Other bus systems may be included, such as 1 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0079] Figure 4 An example of a platform 400 (or "device 400") according to various embodiments is shown. In an embodiment, the computer platform 400 may be suitable for use as a UE 101, 102, 201, an application server 130, and / or any other element / device discussed herein. The platform 400 may include any combination of components shown in the example. The components of the platform 400 may be implemented as an integrated circuit (IC), a portion thereof, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof suitable for use in the computer platform 400, or as components otherwise incorporated within a chassis of a larger system. Figure 4 The block diagram is intended to show a high-level view of the components of computer platform 400. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0080] Application circuit 405 may include circuits such as, but not limited to, a single-core or multi-core processor and one or more of the following: cache memory, a low dropout regulator (LDO), an interrupt controller, a serial interface such as a serial peripheral interface (SPI), an inter-integrated circuit (I 2 C) or general programmable serial interface circuit, real-time clock (RTC), timer-counter including interval timer and watchdog timer, general input / output (IO), memory card controller such as secure digital / multimedia card (SD / MMC) or similar products, universal serial bus (USB) interface, mobile industry processor interface (MIPI) interface and joint test access group (JTAG) test access port. The processor may include any combination of general-purpose processors and / or special-purpose processors (e.g., graphics processors, application processors, etc.). The processor (or core) may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the platform 400. In some embodiments, the processor of the application circuit 305 / 405 may process IP data packets received from the EPC or 5GC.

[0081] The application circuit 405 may be or may include a microprocessor, a multi-core processor, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, or other known processing elements. In one example, the application circuit 405 may include a processor based on Architecture Core TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA company( The processor of the application circuit 405 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia Applications Platform(OMAP) TMprocessor; MIPS-based designs from MIPS Technologies, Inc.; ARM-based designs from ARM Holdings, Ltd.; etc. In some implementations, the application circuit 405 may be part of a system on a chip (SoC), where the application circuit 405 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

[0082] Additionally or alternatively, the application circuit 405 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, etc.; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 405 may include logic blocks or logic structures including other interconnected resources that may be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 405 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in look-up tables (LUTs), etc.

[0083] Baseband circuit 410 can be implemented as, for example, 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. Although not shown, baseband circuit 410 may include one or more digital baseband systems, which may be coupled to a CPU subsystem, an audio subsystem, and an interface subsystem via an interconnect subsystem. The digital baseband subsystem may also be coupled to a digital baseband interface and a mixed signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a digital signal processing 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, and / or other similar components. In one aspect of the disclosure, baseband circuitry 410 may include protocol processing circuitry having one or more control circuit instances (not shown) to provide control functionality for digital baseband circuitry and / or radio frequency circuitry (eg, radio front end module 415).

[0084] The radio front end module (RFEM) 415 may include a millimeter wave 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 millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 415. The RFEM 415 may combine both millimeter wave antennas and sub-millimeter wave antennas.

[0085] The memory circuit 420 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 420 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SDRAM); and non-volatile memory, including high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 420 may be developed according to the Joint Electron Device Engineering Council (JEDEC) based low power double data rate (LPDDR) design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 420 may be implemented as one or more of the following: a solder-in package integrated circuit, a single die package (SDP), a dual die package (DDP) or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 420 may be an on-chip memory or register associated with the application circuit 405. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 420 may include one or more mass storage devices, which may include, among others, a solid-state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 400 may be combined with a memory device obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0086] Removable memory circuitry 423 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 400. These portable data storage devices may be used for mass storage, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.

[0087] The platform 400 may also include an interface circuit (not shown) for connecting an external device to the platform 400. The external device connected to the platform 400 via the interface circuit may include a sensor 421, such as an accelerometer, a level sensor, a flow sensor, a temperature sensor, a pressure sensor, a barometric pressure sensor, etc. The interface circuit may be used to connect the platform 400 to an electromechanical component (EMC) 422, which may allow the platform 400 to change its state, position, and / or orientation, or to move or control a mechanism or system. The EMC 422 may include one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and / or other similar electromechanical components. In an embodiment, the platform 400 may be configured to operate one or more EMCs 422 based on one or more capture events and / or instructions or control signals received from a service provider and / or various clients.

[0088] In some implementations, the interface circuit can connect the platform 400 to the positioning circuit 445, which can communicate with the reference Figure 3 The positioning circuit 345 discussed is the same or similar.

[0089] In some implementations, the interface circuit can connect the platform 400 to a near field communication (NFC) circuit 440, which can include an NFC controller coupled to an antenna element and a processing device. The NFC circuit 440 can be configured to read an electronic tag and / or connect to another NFC-enabled device.

[0090] The driver circuit 446 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 400. The driver circuit 446 may include various drivers to allow other components of the platform 400 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 400. For example, the driver circuit 446 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 400, a sensor driver for obtaining sensor readings of the sensor 421 and controlling and allowing access to the sensor 421, an EMC driver for obtaining an actuator position of the EMC 422 and / or controlling and allowing access to the EMC 422, 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.

[0091] A power management integrated circuit (PMIC) 425 (also referred to as “power management circuit 425”) can manage power provided to various components of the platform 400. In various embodiments, the PMIC 425 can control power selection, voltage scaling, battery charging, or DC-DC conversion relative to the baseband circuit 410. When the platform 400 is capable of being powered by a battery 430, for example, when the device is included in a UE 101, 102, 201, the PMIC 425 can generally be included.

[0092] In some embodiments, the PMIC 425 may control or otherwise be part of various power saving mechanisms of the platform 400. For example, if the platform 400 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 discontinuous reception mode (DRX). During this state, the platform 400 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 400 may transition to the RRC_Idle state, in which the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 400 enters a very low power state and performs paging, in which the device wakes up again periodically to listen to the network and then powers off again. The platform 400 cannot receive data in this state, and in order to receive data, it must transition back to the RRC_Connected state. 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 is completely unable to connect to the network and can be completely powered off. Any data sent during this time will incur significant latency, and it is assumed that latency is acceptable.

[0093] The battery 430 can power the platform 400, but in some examples, the platform 400 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 430 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, the battery 430 can be a typical lead-acid car battery.

[0094] In some implementations, the battery 430 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 400 to track the state of charge (SoCh) of the battery 430. The BMS may be used to monitor other parameters of the battery 430, such as the state of health (SoH) and state of function (SoF) of the battery 430 to provide fault prediction. The BMS may transmit information about the battery 430 to the application circuit 405 or other components of the platform 400. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 405 to directly monitor the voltage of the battery 430 or the current from the battery 430. The battery parameters may be used to determine actions that the platform 400 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0095] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 430. In some examples, the power block 128 can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 400. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 430 and therefore the current required. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Alliance, or the Rezence charging standard published by the Wireless Power Alliance.

[0096] Although not shown, the components of platform 400 may communicate with each other using a suitable bus technology, which may include any number of technologies, including Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), Time Triggered Protocol (TTP) system, or FlexRay system, or any number of other technologies. The bus may be a proprietary bus, such as used in SoC-based systems. Other bus systems may include, such as 1 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0097] Figure 5 Exemplary components of baseband circuitry 310 / 410 and radio front end modules (RFEM) 315 / 415 are shown according to various embodiments. As shown, the RFEM 315 / 415 may include radio frequency (RF) circuitry 506, front end module (FEM) circuitry 508, and one or more antennas 511 coupled together at least as shown.

[0098] The baseband circuit 310 / 410 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 310 / 410 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 506 and generate baseband signals for the transmit signal path of the RF circuit 506. The baseband processing circuit 310 / 410 may interact with the application circuit 305 / 405 to generate and process baseband signals and control the operation of the RF circuit 506. For example, in some embodiments, the baseband circuit 310 / 410 may include a third generation (3G) baseband processor 504A, a fourth generation (4G) baseband processor 504B, a fifth generation (5G) baseband processor 504C, or one or more other baseband processors 504D of other existing generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 310 / 410 (e.g., one or more of the baseband processors 504A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 506. In other embodiments, some or all of the functions of the baseband processors 504A-D may be included in a module stored in the memory 504G and may be executed via the central processing unit ("CPU") 504E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 310 / 410 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 310 / 410 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0099] In some embodiments, the baseband circuit 310 / 410 may include one or more audio digital signal processors (DSPs) 504F. The audio DSP 504F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 310 / 410 and the application circuit 305 / 405 may be implemented together, such as on a system on a chip (SoC).

[0100] In some embodiments, the baseband circuit 310 / 410 can provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 310 / 410 can support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuit 310 / 410 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0101] RF circuit 506 can use modulated electromagnetic radiation to communicate with a wireless network through a non-solid medium. In various embodiments, RF circuit 506 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 506 may include a receive signal path, which may include circuits for down-converting RF signals received from FEM circuit 508 and providing baseband signals to baseband circuit 310 / 410. RF circuit 506 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by baseband circuit 310 / 410 and providing RF output signals for transmission to FEM circuit 508.

[0102] In some embodiments, the receive signal path of the RF circuit 506 may include a mixer circuit 506A, an amplifier circuit 506B, and a filter circuit 506C. In some embodiments, the transmit signal path of the RF circuit 506 may include a filter circuit 506C and a mixer circuit 506A. The RF circuit 506 may also include a synthesizer circuit 506D for synthesizing frequencies used by the mixer circuit 506A for the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 506A of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 508 based on the synthesized frequency provided by the synthesizer circuit 506D. The amplifier circuit 506B may be configured to amplify the down-converted signal, and the filter circuit 506C may 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 may be provided to the baseband circuit 310 / 410 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required.In some embodiments, mixer circuit 506A of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0103] In some embodiments, mixer circuit 506A of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 506D to generate an RF output signal for FEM circuit 508. The baseband signal may be provided by baseband circuit 310 / 410 and may be filtered by filter circuit 506C.

[0104] In some embodiments, the mixer circuit 506A of the receive signal path and the mixer circuit 506A 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 embodiments, the mixer circuit 506A of the receive signal path and the mixer circuit 506A 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 embodiments, the mixer circuit 506A of the receive signal path and the mixer circuit 506A of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 506A of the receive signal path and the mixer circuit 506A of the transmit signal path may be configured for superheterodyne operation.

[0105] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 506 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuit 310 / 410 may include a digital baseband interface for communicating with the RF circuit 506.

[0106] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0107] In some embodiments, synthesizer circuit 506D may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 506D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0108] Synthesizer circuit 506D may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 506A of RF circuit 506. In some embodiments, synthesizer circuit 506D may be a fractional-N / N+1 synthesizer.

[0109] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuit 310 / 410 or the application processor 305 / 405 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 305 / 405.

[0110] The synthesizer circuit 506D of the RF circuit 506 may include a frequency divider, a delay locked loop ("DLL"), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0111] In some embodiments, the synthesizer circuit 506D can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 506 can include an IQ / polarity converter.

[0112] The FEM circuitry 508 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 511, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 506 for further processing. The FEM circuitry 508 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 506 for transmission via one or more of the one or more antennas 511. In various embodiments, amplification via the transmit signal path or the receive signal path may be performed only in the RF circuitry 506, only in the FEM 508, or in both the RF circuitry 506 and the FEM 508.

[0113] In some embodiments, the FEM circuit 508 may include a TX / RX switch to switch between transmission mode and reception mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to the RF circuit 506). The transmit signal path of the FEM circuit 508 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by the RF circuit 506); and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 511).

[0114] The processors of the application circuits 305 / 405 and the processors of the baseband circuits 310 / 410 may be used to execute elements of one or more instances of the protocol stack. For example, the processors of the baseband circuits 310 / 40 may be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, and the processors of the baseband circuits 310 / 410 may utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0115] Figure 6 An exemplary interface of a baseband circuit according to some embodiments is shown. As discussed above, Figure 3 to Figure 4 The baseband circuit 310 / 410 may include processors 504A-504E and a memory 504G utilized by the processors. Each of the processors 504A-504E may include a memory interface 604A-604E, respectively, for sending / receiving data to / from the memory 504G.

[0116] The baseband circuit 310 / 410 may also include: one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 612 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 310 / 40); an application circuit interface 614 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 310 / 40); Figure 3 to Figure 4 RF circuit interface 616 (for example, for sending / receiving data to / from application circuit 305 / 405); Figure 5an interface for sending / receiving data to / from a near field communication (NFC) component, Parts (e.g. Low power consumption), components and other communication components to send / receive data); and a power management interface 620 (eg, an interface for sending / receiving power or control signals to / from the PMIC 55).

[0117] Figure 7 is an illustration of a control plane protocol stack according to some embodiments. In this embodiment, the control plane 700 is shown as a communication protocol stack between UE 101 (or alternatively, UE 102), RAN node 111 (or alternatively, RAN node 112) and MME 121.

[0118] The PHY layer 701 may transmit or receive information used by the MAC layer 702 over one or more air interfaces. The PHY layer 701 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers (e.g., the RRC layer 705). The PHY layer 701 may further perform error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and multiple-input multiple-output (MIMO) antenna processing.

[0119] The MAC layer 702 can perform mapping between logical channels and transport channels, multiplex MAC service data units (SDUs) from one or more logical channels onto transport blocks (TBs) to be delivered to the PHY via transport channels, demultiplex MAC SDUs from transport blocks (TBs) delivered by the PHY via transport channels to one or more logical channels, multiplex MAC SDUs onto TBs, schedule information reporting, perform error correction through hybrid automatic repeat request (HARQ), and prioritize logical channels.

[0120] The RLC layer 703 is capable of operating in multiple modes of operation, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). The RLC layer 703 can perform transmission of higher 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. The RLC layer 703 can also perform re-segmentation 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.

[0121] The PDCP layer 704 can perform header compression and decompression of IP data, maintain the PDCP sequence number (SN), perform in-order delivery of upper layer PDUs when lower layers are re-established, eliminate duplication of lower layer SDUs when re-establishing lower layers 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, integrity verification, etc.).

[0122] The main services and functions of the RRC layer 705 may include broadcasting of system information (e.g., included in a master information block (MIB) or a system information block (SIB) related to a non-access stratum (NAS)), broadcasting of system information related to an access stratum (AS), paging, establishment, maintenance, and release of an RRC connection between a UE and an E-UTRAN (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, mobility between radio access technologies (RATs), and measurement configuration for UE measurement reporting. The MIB and SIB may include one or more information elements (IEs), each of which may include a separate data field or data structure.

[0123] UE 101 and RAN node 111 may utilize a Uu interface (eg, LTE-Uu interface) to exchange control plane data via a protocol stack including a PHY layer 701 , a MAC layer 702 , an RLC layer 703 , a PDCP layer 704 , and an RRC layer 705 .

[0124] Non-Access Stratum (NAS) protocol 706 forms the highest layer of the control plane between UE 101 and MME 121. NAS protocol 706 supports mobility of UE 101 and session management procedures to establish and maintain IP connection between UE 101 and P-GW 123.

[0125] The S1 application protocol (S1-AP) layer 715 may support the functions of the S1 interface and include an elementary procedure (EP). The EP is an interaction unit between the RAN node 111 and the CN 120. The S1-AP layer 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.

[0126] The stream control transmission protocol (SCTP) layer (also referred to as the SCTP / IP layer) 714 may ensure reliable delivery of signaling messages between the RAN node 111 and the MME 121 based in part on the IP protocol supported by the IP layer 713. The L2 layer 712 and the L1 layer 711 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[0127] The RAN node 111 and the MME 121 may exchange control plane data via a protocol stack including an L1 layer 711 , an L2 layer 712 , an IP layer 713 , an SCTP layer 714 , and an S1-AP layer 715 using an S1-MME interface.

[0128] Figure 8 800 is an illustration of a user plane protocol stack according to some embodiments. In this embodiment, the user plane 800 is shown as a communication protocol stack between the UE 101 (or alternatively, the UE 102), the RAN node 111 (or alternatively, the RAN node 112), the S-GW 122 and the P-GW 123. The user plane 800 may utilize at least some of the same protocol layers as the control plane 700. For example, the UE 101 and the RAN node 111 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack including a PHY layer 701, a MAC layer 702, a RLC layer 703, and a PDCP layer 704.

[0129] The General Packet Radio Service (GPRS) Tunneling Protocol for User Plane (GTP-U) layer 804 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. The UDP and IP Security (UDP / IP) layer 803 may provide checksums 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 122 may exchange user plane data using an S1-U interface via a protocol stack including an L1 layer 711, an L2 layer 712, a UDP / IP layer 803, and a GTP-U layer 804. The S-GW 122 and the P-GW 123 may exchange user plane data using an S5 / S8a interface via a protocol stack including an L1 layer 711, an L2 layer 712, a UDP / IP layer 803, and a GTP-U layer 804. As described above with respect to Figure 7 As discussed, the NAS protocol supports the mobility of UE 101 and session management procedures to establish and maintain an IP connection between UE 101 and P-GW 123.

[0130] Fig. 9 Components of a core network according to some embodiments are shown. The components of CN 120 may be implemented in one physical node or in separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In an embodiment, the components of CN 220 can be implemented in the same or similar manner as discussed herein with respect to the components of CN 120. In some embodiments, network function virtualization (NFV) is used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 120 may be referred to as a network slice 901, and each logical instance of CN 120 may provide specific network functions and network characteristics. A logical instance of a portion of CN 120 may be referred to as a network sub-slice 902 (e.g., a network sub-slice 902 is shown as including a PGW 123 and a PCRF 126).

[0131] 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.

[0132] Compared to 5G systems (see e.g. Figure 2 ), the network slice may include the CN control plane and user plane NF, the NG RAN in the serving PLMN, and the N3IWF function in the serving PLMN. Each network slice may have a different single network slice selection assistance information (S-NSSAI) and / or may have a different slice / service type (SST). The network slices may differ in terms of supported features and network function optimizations, and / or multiple network slice instances may deliver the same one or more services, but differ for different UE groups (e.g., enterprise users). For example, each network slice may deliver different committed services and / or may be dedicated to a specific customer or enterprise. 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 via a 5G access node (AN) and be associated with eight different S-NSSAIs. In addition, the AMF instance serving a single UE may belong to each network slice instance serving the UE.

[0133] The 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 a virtual or reconfigurable implementation of one or more EPC components / functions.

[0134] Fig.10 is a block diagram illustrating components capable of 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 methods discussed herein, according to some exemplary embodiments. For one embodiment, Fig.10A diagrammatic representation of hardware resources 1000 is shown, the hardware resources including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040. As used herein, the terms "computing resources," "hardware resources," and the like may refer to physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a particular device, such as computer equipment, mechanical equipment, memory space, processor / CPU time and / or processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database, and applications, etc. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resources 1000. "Virtualized resources" may refer to computing, storage, and / or network resources provided by a virtualized infrastructure to applications, devices, systems, and the like.

[0135] Processor 1010 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1012 and processor 1014.

[0136] The memory / storage device 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1020 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0137] The communication resources 1030 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1004 or one or more databases 1006 via the network 1008. For example, the communication resources 1030 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Parts (e.g. Low power consumption), components and other communication components. As used herein, the term "network resource" or "communication resource" may refer to a computing resource that can be accessed by a computer device via a communication network. The term "system resource" may refer to any kind of shared entity that provides a service, and may include computing resources and / or network resources. System resources may be considered a set of coherent functions, network data objects, or services accessible through a server, where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0138] The instructions 1050 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1010 to perform any one or more of the methods discussed herein. The instructions 1050 may reside completely or partially within at least one of the processors 1010 (e.g., within a cache memory of a processor), the memory / storage device 1020, or any suitable combination thereof. In addition, any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral device 1004 or the database 1006. Therefore, the memory of the processor 1010, the memory / storage device 1020, the peripheral device 1004, and the database 1006 are examples of computer-readable and machine-readable media.

[0139] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments shown in the example section below.

[0140] For one or more embodiments, at least one of the components shown in one or more of the aforementioned figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the aforementioned figures may be configured to operate according to one or more of the examples shown in the example section below. For another example, the circuits associated with the UE, base station (e.g., DN, gNodeB, etc.), network element, etc. described above in conjunction with one or more of the aforementioned figures may be configured to operate according to one or more of the examples shown in the example section below.

[0141] Factors that affect the power consumption of a mobile radio communication terminal device (eg, UE) in a connected mode (eg, RRC_connected state) are as follows:

[0142] PDCCH monitoring: The number of times the UE monitors the PDCCH at the configured PDCCH timing, which does not result in a grant allocation

[0143] Working BWP size

[0144] UE Rx / Tx # antennas and number of active RF chains f

[0145] Measurement operation

[0146] The UE may operate in a discontinuous reception (DRX) mode to save UE power by avoiding continuous monitoring of the PDCCH. The DRX operation may include an on-duration or an on-state (e.g., a monitoring state of the UE), where the UE turns on and monitors transmissions from the network as part of a DRX cycle. Existing solutions include a DRX mode configured by a higher layer in a connected state, where the DRX configuration includes the following RRC configuration parameters, such as shown in Table 1. For a detailed description of the parameters assumed to be attached to this application as a reference, see 3GPP specification 38.321.

[0147] Table 1: DRX configuration parameters

[0148]

[0149]

[0150] In (New Radio) NR, mobile radio communication terminal devices (e.g., UE) may support various 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 various traffic patterns and bursty traffic.

[0151] Various embodiments provide methods to adapt DRX operation to the dynamic nature of traffic arrival patterns in order to minimize power consumption for a given UE.

[0152] In connected mode (e.g., RRC_connected state), the biggest factors affecting UE power consumption are PDCCH monitoring (e.g., based on the number of times the UE monitors PDCCH at configured PDCCH opportunities that do not result in grant allocation), operating BWP size, number of UE Rx / Tx # antennas and active RF chains, and measurement operations.

[0153] The UE may operate in a discontinuous reception (DRX) mode to save UE power by avoiding continuous monitoring of the PDCCH. Typical DRX operation includes an on-duration as part of a DRX cycle when the UE is turned on and monitors transmissions (e.g., PDCCH) from the network. Existing solutions include a DRX mode configured by a higher layer in a connected state, where the DRX configuration includes the following RRC configuration parameters, such as shown in Table 1. Details of the parameters can be found in 3GPP specification 38.321, which is incorporated herein by reference.

[0154] In various exemplary embodiments of the present disclosure, based on the nature of active traffic flows to and from a mobile radio communication terminal device (e.g., UE), one of a set of configured DRX configurations may be activated at a given time. An exemplary DRX configuration includes at least the parameter set indicated in the list in Table 1 above. A first DRX configuration may be different from a second DRX configuration if the value of at least one parameter in the DRX configuration is different.

[0155] Table 2 shows an example in which K configurations can be configured by a higher layer (e.g., via RRC signaling) for a mobile radio communication terminal device (e.g., UE), where the index of one of the reference configurations can be indicated, for example, by a MAC control element (CE) or downlink control information (DCI). Each configuration has one or more parameters from Table 1 and possibly multiple parameters, such as the wake-up signal monitoring duration, the offset of the starting position of the wake-up signal monitoring duration, the offset of the starting position of the on-duration of the control channel (e.g., monitoring after the wake-up signal is detected, etc.), and more details of these parameters are provided in the following sections. Here, the offset of the starting position of the wake-up signal monitoring duration means that the wake-up signal can be configured to be monitored at an offset from the configured starting position of the next DRX on-duration or drx-onDurationTimer. In addition, the offset of the on-duration starting position of the control channel monitoring means an offset when the wake-up signal is detected. The embodiments provided in the following sections will explain this offset in more detail.

[0156] Table 2: Multiple configurations

[0157] DRX-Config Index Configuration Content 0 Parameter 1, parameter 2, etc. 1 ..... … ..... K .....

[0158] In various embodiments, a new MAC CE may be added to activate one of several configured DRX-Configs to be used for the MAC entity of the corresponding cell group or serving cell. This will enable a mobile radio communication terminal device (e.g., UE) to adjust multiple DRX parameters more quickly through a single MAC command compared to the existing DRX (re) configuration mechanism using a semi-static RRC reconfiguration message. The number of DRX-Configs supported by each MAC entity, i.e., K in the above table, may be fixed in a UE capability parameter or specification and also determines the size of the MAC CE.

[0159]

[0013] Furthermore, in various implementations, in NR, a mobile radio communication terminal device (e.g., UE) may be able to communicate with 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 FTFs and possibly different RF chains. Thus, in some designs, the UE may be configured with one or more parameter set-specific, bandwidth part (BWP)-specific, or carrier-specific DRX configurations.

[0160] In at least one exemplary embodiment of the present disclosure, different parameters may be configured for different BWPs, and BWP switching may be performed by explicit DCI commands or background timer operations (i.e., bwp-inactivityTimer). If different DRX configurations for different BWPs with various parameter sets are desired, it may be beneficial that the DRX configurations can be switched together 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 embodiments, a DRX configuration with a larger value setting of drx-InactivityTimer may be configured for the default BWP compared to other mobile radio communication terminal device / UE-specific BWPs, which may be technically driven by the fact that the default BWP is typically used when the mobile radio communication terminal device / UE has almost completed data communication and a larger value has less impact on packet delay.

[0161] In various exemplary embodiments, dynamic L1 signaling may be implemented to adapt DRX parameters and / or transition between active and sleep states more quickly. That is, according to exemplary embodiments of the present disclosure, and in contrast to existing solutions in which the DRX mode is configured via RRC signaling, dynamic L1 signaling such as in a PDCCH or sequence (such as downlink control information (DCI)) may be used to notify the UE of adjusting DRX parameters and / or activating / deactivating a DRX mode and / or entering sleep and / or waking up from sleep. Specifically, a dynamic L1 wake-up signal and / or entering sleep signal may be utilized to potentially increase the sleep duration of the UE.

[0162] The following are some additional terms that may be relied upon in this disclosure:

[0163]

[0164]

[0165] In an exemplary embodiment of the present disclosure, a mobile radio communication terminal device (e.g., UE) may be configured to receive GTS signaling when the UE is turned on or active. In one or more embodiments, the mobile radio communication terminal device (e.g., UE) may receive higher layer signaling GTS_Signaling=ON / OFF via RRC, i.e., if ON, the UE monitors GTS signaling, and if OFF, the UE does not monitor GTS. Enabling / disabling GTS signal monitoring may be group-specific, e.g., cell-specific, or UE-specific (e.g., via dedicated RRC signaling). -

[0166] For example, the UE may be on in the following cases: i) when the UE is in a configured / activated DRX mode with a given / indicated DRX configuration as part of a DRX cycle; ii) when it is not using any DRX mode configuration / activation and continuously monitoring transmissions / signaling from the network. GTS signaling may trigger the UE to sleep and stop monitoring PDCCH for a specified / configured / indicated sleep duration

[0167] In various embodiments, at least two parameters related to GTS signaling may be identified, such as

[0168] 1) Offset to the start of the sleep duration, T_GTS_A

[0169] 2) Sleep duration, T_GTS_B

[0170] In some exemplary embodiments, a mobile radio communication terminal device (e.g., UE) may be configured by a higher layer (e.g., RRC signaling) with an index of the GTS periodicity and the GTS slot offset, the index pointing to a row in a predefined table in the specification. More specifically, the offset value may be defined relative to the start of an ongoing DRX cycle.

[0171] T_GTS_A and / or T_GTS_B may be indicated as part of the GTS signaling, or may be higher layer configured, for example as part of the DRX configuration or the GTS signaling configuration. In at least one example, T_GTS_A and / or T_GTS_B may be fixed in the specification, or may obtain a predefined mapping based on one or more DRX parameters such as DRX on-duration drx-onDurationTimer and / or drx-InactivityTimer, etc. 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, or in ms or sub-ms for a given parameter set.

[0172] In a first example, a mobile radio communication terminal device (e.g., UE) operates in a configured C-DRX mode within a BWP or carrier, e.g., in a given DRX cycle with a specifically configured on-duration, when the UE detects at least a PDCCH. The UE may be configured to monitor L1 signaling for GTS during an active / on state of the DRX mode. Depending on how long the on-duration is configured, the GTS signaling may cause the UE to go to sleep before the end of the configured on-duration, see Fig.11A , where a GTS signal is received during the configured on-duration, or a micro-sleep may be triggered during the on-duration, such as Fig. 11B shown.

[0173] The on-duration may include one or more of the following: drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, wherein in at least 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.

[0174] Referring back to the first example, the L1 signaling for GTS only triggers the UE to enter sleep. The UE continues to follow the existing DRX configuration, where the sleep or active state duration can only be modified if a GTS trigger is received. For example, the dashed area in Figure 11 means that the on-duration is skipped, which also applies to other subsequent figures unless otherwise stated.

[0175] According to an exemplary embodiment of the present disclosure, Fig.11A and Fig. 11B FIG. 4 shows a C-DRX mode operation, in which the mobile radio communication terminal device receives GTS signaling (eg, GTS L1 signaling) during the on state. Fig.11A In an exemplary embodiment of , a mobile radio communication terminal device (eg, UE) receives GTS signaling during an on state to put the UE into a dormant state or micro-sleep before the on duration ends. Fig. 11B In an exemplary embodiment, a mobile radio communication terminal device (e.g., UE) receives GTS signaling during an on state to put the UE into a sleep state within a configured on duration and before the on duration ends. FIG. 11 shows an exemplary embodiment, wherein when a GTS trigger is received, the indicated or configured sleep duration may span more than a DRX cycle.

[0176] More specifically, if Fig.11A and Fig. 11B Two examples are shown, where Fig.11A In , T_GTS_B is set so that the UE is dormant for the remainder of the configured on-duration, while Fig. 11B In the example, T_GTS_B is a fairly small value that only triggers micro-sleep, and after a period of time, the UE wakes up to monitor PDCCH or other signaling for the remainder of the on-duration. T_GTS_A may vary with the capabilities of the mobile radio communication terminal device (e.g., UE), or alternatively may be fixed in the specification / standard. In another example, T_GTS_B may also vary with the UE capabilities. For example, Fig. 11B The T_GTS_B in the may need to take into account how quickly the UE can wake up to monitor the PDCCH for the remainder of the On Duration. In at least 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 in 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 can be put to sleep for one or more subsequent DRX cycles, i.e., skipping one or more subsequent On Durations. This is in Fig. 11C, where the UE is signaled to sleep for three DRX cycles starting from the DRX cycle in which the UE receives GTS signaling.

[0177] exist FIG. 11A to FIG. 11C In the example of , T_GTS_A is shown as the duration between the location of GTS signal detection and the start location of the sleep duration. More generally, T_GTS_A may refer to an offset from a given reference point to the start location of the sleep duration, where examples of reference time points include:

[0178] - The offset is counted from the next symbol after the GTS signaling is received, i.e., 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 at the start of the sleep duration, i.e., if the sleep duration starts at j, then until symbol j-1 or j

[0179] - Count the offset from the first symbol when the GTS signaling is received, i.e., if the GTS signaling spans symbols i, i+1, ..., i+K, K≥1, then count the offset from symbol i until the symbol before or when the sleep duration starts, if the GTS signaling spans symbols i, i+1, ..., i+K, K≥1, then count the offset from symbol i until the symbol before or when the sleep duration starts

[0180] - The offset is counted from the last symbol where GTS signaling was received, i.e., if GTS signaling spans symbols i, i+1, ..., i+K, K ≥ 1, then the offset count starts from symbol i+K until the symbol before or at the start of the sleep duration, i.e., if the sleep duration starts at j, then until symbol j-1 or j

[0181] - Count the offset from the slot boundary, i.e. from the start of the current slot when the GTS signaling is received until the symbol before or when the sleep duration starts

[0182] - Count the offset from the start of the current subframe or a given subframe until the symbol before or at the start of the sleep duration

[0183] In at least one exemplary embodiment of the present disclosure, L1 signaling may trigger GTS together with switching one or more DRX parameters. For example, L1 signaling may switch a UE from a long DRX cycle to a short DRX cycle, or vice versa. A mobile radio communication terminal device, such as a 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 ​​overwrite the configured values. The rest of the DRX parameters may then be 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.

[0184] In various exemplary embodiments of the present disclosure, the L1 trigger providing the GTS may further indicate a bandwidth part, so that a mobile radio communication terminal, such as a UE, wakes up in a different bandwidth part indicated by the received GTS. The UE may be in the newly indicated bandwidth part 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 bandwidth part and continues the configured DRX operation. In one example, the UE may switch to the new BWP in the next DRX cycle after the sleep 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 at least one example, the UE may continue to operate using a common DRX configuration for all bandwidth parts, or when switching to a different bandwidth part, the UE may assume a bandwidth part-specific DRX configuration (if supported).

[0185] According to an exemplary embodiment of the present disclosure, Fig.12 A mobile radio communication terminal device such as a UE is shown in an active state and is continuously monitoring DCI, and L1 signaling is provided for activation of GTS and / or DRX mode. As shown, when the next DRX cycle starts, the UE wakes up on different bandwidth parts according to the instructions in the GTS signaling.

[0186] exist Fig.12 In the example of FIG. 1 , it is assumed that the UE receives GTS and / or activates in bandwidth part B1, and L1 signaling may optionally indicate the bandwidth part to the UE so that the UE is in a different bandwidth part B2 during the active / on state in DRX mode. The smaller bandwidth part B2 may provide power saving gains compared to B1.

[0187] In another example, a mobile radio communication terminal device (e.g., UE) may not be configured with a DRX configuration or may not have any activated DRX mode and DRX configuration, and L1 signaling for GTS may dynamically put the UE into sleep for a given duration. In such an example, the L1 trigger for GTS may indicate the duration of sleep and / or the starting position of the duration. Alternatively, the GTS signaling may dynamically instruct the UE to skip monitoring the subsequent / subsequent N≥1 PDCCH monitoring opportunities.

[0188] In various exemplary embodiments of the present disclosure, a mobile radio communication terminal device, such as a UE, may be configured to receive a wake-up signal (WUS) after a sleep state when the UE operates in a DRX mode with a given DRX configuration. In at least one embodiment, the UE may receive higher layer signaling WUS_transmission=ON / OFF via RRC. That is, if it is ON, the UE monitors WUS, and if it is OFF, the UE does not monitor WUS. Enabling / disabling WUS monitoring may be group-specific, for example, cell-specific or device-specific (e.g., UE), and may be configured (e.g., via dedicated RRC signaling). In one or more examples, 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.

[0189] In various exemplary embodiments of the present disclosure, a mobile radio communication terminal device / UE may be configured with a WUS monitoring duration. In such examples, the UE is turned on only during the 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. Compared with the case where the UE always wakes up the configured on duration for PDCCH monitoring, this can lead to more power savings, and the configured on duration can be much longer than the duration of WUS monitoring. In one example, the UE can monitor WUS every N DRX cycles, where N is a positive integer. The value of N can be device / UE specific and configured by RRC signaling. As described above, the on duration configured after WUS detection (e.g., performing PDCCH monitoring) may include one or more of drx-onDurationTimer, drx-InactivityTimer. It should be noted that, if necessary, the WUS monitoring duration may be additionally used for beam management and / or other necessary synchronization operations, which may even be performed before the UE monitors WUS in at least one example. In one or more examples, the WUS may provide or include additional information for the UE to achieve or maintain synchronization with one or more cells.

[0190] Therefore, a parameter such as a WUS monitoring window drx-onDurationTimer-WUS may be identified, 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 drxonDurationTimer-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.

[0191] FIG. 13A to FIG. 13D FIG. 1 shows a mobile radio communication terminal device, such as a UE, operating in a DRX mode (such as with two configured on-times) according to an exemplary embodiment of the present disclosure. One configured on-time is drx-onDurationTimer ( FIG. 13A to FIG. 13C The on-time configured in ), and the on-time of another configuration is drx-onDurationTimer-WUS( FIG. 13A to FIG. 13C The on time (WUS) in the Fig.13D An exemplary WUS configuration for on-off DRX operation is shown.

[0192] exist Fig.13A In the example of , a mobile radio communication terminal device, such as a UE, turns on to monitor for WUS for a limited duration according to the configured DRX cycle, and if a WUS is detected, it wakes up after a period of time and monitors for the configured on-duration. In the following examples, this period of time or duration is referred to as an offset or gap. Fig. 13B In the example of , if the UE detects a WUS, the UE may be triggered to switch the BWP for active state operation. Fig. 13C In the example of FIG. 4 , after detecting a WUS, the UE immediately starts monitoring the PDCCH and other signaling for the configured on-duration.

[0193] exist FIG. 13A to FIG. 13B In the example of , there is a gap between the end of drxonDurationTimer-WUS and the start of drx-onDurationTimer. Alternatively, the gap may be referred to as an offset. Figure 3In (b), it is assumed that WUS can potentially indicate BWP, i.e., 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. 13B As shown, a WUS may be monitored in a small BWP (e.g., BWP 1), 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. 13C In the example of , it is assumed that drx-onDurationTimer starts immediately after drx-onDurationTimer-WUS ends and WUS is detected.

[0194] In various embodiments, the parameter N may be identified gap , which may indicate an inactivity duration that begins after the drxonDurationTimer-WUS expires and ends before the drx-onDurationTimer starts. gap is the offset l,e, i.e., the duration for the UE to prepare for the next DRX on duration. gap It may be expressed in symbols or time slots in a given parameter set or in ms. In some designs or examples, N gap may be indicated as part of WUS signaling. In at least one example, if the UE detects 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.

[0195] In one example, if a mobile radio communication terminal device, such as a UE, is configured to monitor WUS, the DRX cycle may start with a start time drx-onDurationTimer-WUS for WUS monitoring, which is 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. Thus, drx-onDurationTimer may start after an offset or immediately when WUS is detected. Alternatively, in another example, 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.

[0196] In another example, 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 begins, or the position / CORESET where a WUS is detected or the end of a 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 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.

[0197] FIG. 13A to FIG. 13C The example shown in may assume that DRX starts from a WUS monitoring window or drx-onDurationTimer-WUS. In at least one other exemplary embodiment, reference Fig.13D , the WUS monitoring window or duration can be N for a given parameter set gapsymbol or time slot or ms 210 before the start of the configured DRX cycle, so as to keep the PDCCH monitoring activity in the DRX cycle, as in the traditional system (if it occurs). If the UE does not detect a WUS signal in the monitoring window or opportunity indicating that the UE performs DRX operation in the next M DRX cycles, the UE will skip PDCCH monitoring in the next M DRX cycles; if WUS is detected, traditional DRX operation is performed, that is, the UE turns on the configured turn-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 is dynamically indicated by the WUS based on at least the real-time service characteristics of the UE. In addition, the Ngap value can be reported by the UE as part of the UE capabilities and then configured accordingly. Assuming that Fig.13D In the example, M=1.

[0198] In at least one embodiment, L1 signaling may trigger a WUS along with switching one or more DRX parameters. For example, L1 signaling may switch a mobile radio communication terminal (e.g., UE) from a long DRX cycle to a short DRX cycle. 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 rest of the DRX parameters may be RRC configured.

[0199] In at least one other example, the L1 trigger providing the WUS may additionally indicate a bandwidth portion such that the UE wakes up in a different bandwidth portion, such as in Fig. 13B In the example of . The UE may be in the new bandwidth part for a duration configured by the timer, or until further signaling of the switch is received. If a timer is configured, then upon expiration, the UE may return to the previous or given default bandwidth part and continue the configured DRX operation.

[0200] In at least one example, the WUS may indicate whether the mobile radio communication terminal device / UE should exit the DRX mode or only wake up for a subsequent on-duration for monitoring the scheduling DCI.

[0201] FIG. 14A to FIG. 14C Different examples of monitoring timers for WUS, PDCCH, and subsequent PDSCH according to exemplary embodiments of the present disclosure are shown.

[0202] In various examples, WUS detection may mean that a mobile radio communication device terminal (eg, UE) may soon receive a PDCCH / scheduled DCI or other transmission from the network. In at least one example, for example, according to Fig.14A, a mobile radio communication terminal device (e.g., 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-lnactivityTimer 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, a timer for PDSCH and / or subsequent PDCCH and / or other transmissions, receptions may be started X≥1 symbol or time slot after successful detection of PDCCH.

[0203] In at least one other example, for example, according to Fig. 14B , two timers are configured instead of Fig.14A 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. 14BThe 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. 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-lnactivityTimer, which, for a given parameter set, may be started X≥1 symbols or time slots after the successful detection of the PDCCH. In at least 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 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.

[0204] In at least one other example, for example, according to Fig. 14C , two timers are configured instead of Fig.14AIn the three timers. 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-lnactivityTimer. 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-lnactivityTimer 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 a monitoring opportunity for receiving PDCCH / scheduling DCI and receiving subsequent PDSCH. For example, unlike the conventional system, 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-lnactivityTimer. Here,

[0205] 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 directly start the drx-lnactivityTimer correctly for receiving PDCCH / PDSCH instead of using another intermediate timer such as Fig.14AAs shown. Therefore, in one example, drx-onDurationTimer is redefined in a NR that may include only WUS monitoring opportunities, and drx-lnactivityTimer 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-lnactivityTimer.

[0206] Figure 4 The timers considered in the example of 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] According to various exemplary embodiments, the following types of DRX mode operations may be configured for a mobile radio communication terminal device (eg, UE) in connected mode:

[0208] Type 1: Activation and / or deactivation of DRX mode with at least one DRX configuration configured via RRC or MAC CE

[0209] i. Type 1a: RRC signaling may be provided to (re)configure one or more DRX parameters / switch DRX configuration

[0210] ii. Type 1b: L1 signaling can be provided to update DRX parameters / switch DRX configuration, and / or indicate sleep and / or wake-up triggers

[0211] iii. Type 1c: RRC signaling or a combination of L1 and RRC signaling may be provided to (re)configure one or more DRX parameters / switch DRX configurations, and / or L1 signaling may be provided to indicate a sleep and / or wake-up trigger

[0212] iv. Type 1d: A new MAC Control Element (CE) for DRX parameter reconfiguration may be introduced, which is identified by a MAC PDU subheader with a dedicated LCID (Logical Channel Group ID). In addition, it may have a fixed size and consist of fields to indicate the DRX parameter set or configuration index to be applied by the MAC entity. In addition, L1 signaling may be provided to indicate entry into sleep and / or wake-up triggers

[0213] Type 2: Activation and / or deactivation of DRX mode with at least one DRX configuration configured via L1 signaling

[0214] i. Type 2a: RRC or MAC CE signaling may be provided to reconfigure one or more DRX parameters / switch DRX configuration

[0215] ii. Type 2b: L1 signaling can be provided to update DRX parameters / switch DRX configuration, and / or indicate sleep and / or wake-up triggers

[0216] iii. Type 2c: RRC / MAC CE signaling or a combination of L1 and RRC / MAC CE signaling may be provided to (re)configure one or more DRX parameters / switch DRX configuration, and / or L1 signaling may be provided to indicate entry into sleep and / or wake-up triggers.

[0217] In various exemplary embodiments, 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 providing the activation trigger. On the contrary, it is also possible that the mobile radio communication terminal device / UE is configured with at least one DRX configuration through previous higher layer signaling (such as RRC signaling and L1 activation signaling), so that the DRX mode is only turned on with the previously indicated DRX configuration.

[0218] In at least one exemplary embodiment of the present disclosure, RRC signaling or L1 signaling can activate a DRX mode that can be based on the expiration of a timer. For example, if a mobile radio communication terminal device (e.g., UE) receives a subsequent L1 signaling trigger, such as a WUS or a 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.

[0219] Examples of L1 signaling may include sequence-based or DCI-based transmissions, for example, in PDCCH or a combination thereof, both of which may be device (e.g., 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 and / or ms and / or symbol / slot of a given parameter set. 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 may be mobile radio

[0220] Communication terminal device (eg UE) specific or group common.

[0221] In various exemplary embodiments of the present disclosure, a DCI-based L1 signaling design can be implemented, for example, where a group of mobile radio communication terminals (e.g., UEs) monitor common time-frequency resources to obtain control information that can be UE-specific and / or group-common. The DCI can be transmitted in a PDCCH associated with a common RNTI, or the DCI can be transmitted in a sequence without being associated with any RNTI. Although we consider RRC_connected mode UEs in this patent application, it should be understood that similar mechanisms can be applied to UEs in other states / modes, such as idle or inactive states, if relevant.

[0222] In various examples, in a given cell, a group of mobile radio communication terminal devices (e.g., UEs) may be formed that monitor a DCI format with a CRC masked by a common RNTI attached, e.g., a PDCCH associated with a common RNTI such as a power saving RNTI, a DRX RNTI, a GTS RNTI, or a WUS RNTI, as a function of the DCI format. 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.

[0223] In such examples, the 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).

[0224] The following is an example where the Group Common DCI (GC-DCI) has mobile radio communication terminal equipment (eg UE) specific content.

[0225] Fig.15A common DCI format structure with a mobile radio communication terminal device (eg, UE) specific field according to an exemplary embodiment of the present disclosure is shown. In other words, Fig.15 is an example of a generic structure of a group-common DCI with device-specific content.

[0226] exist Fig.15 In the example of , there are K ≥ 1 fields for a mobile radio communication terminal device (e.g., UE) that is specifically configured, for example, the network maps the device / UE to a corresponding field that can be obtained via previous higher layer signaling (such as, RRC signaling). Each device / UE specific field may have L ≥ 1 subfields, wherein each subfield may have M ≥ 1 bits. Thus, in addition to the CRC bits, the DCI format has an overall KLM bit, wherein there is a LM bit in each UE specific field.

[0227] In at least one example, a common DCI format may be used to signal GTS.In one embodiment, each radio communication terminal device / UE specific field may have only 1 bit, where bit=1 may indicate GTS and bit=0 may indicate no GTS trigger for a given UE.

[0228] Fig.16 A common DCI format structure with five UE-specific fields is shown, wherein each UE-specific field has 1 bit. According to an exemplary embodiment of the present disclosure, bit = 1 indicates that the GTS trigger is true, and bit = 0 indicates that the GTS trigger is false. That is, Fig.16 An example is shown in which K=5 UEs are configured to monitor a common DCI, wherein only the UEs mapped to the 2nd and 5th fields are indicated with a GTS trigger, and other mobile radio communication terminal devices (e.g., UEs) do not have any GTS trigger. Therefore, upon detecting a DCI format, the mobile radio communication terminal devices (e.g., UEs) mapped to the 2nd and 5th fields may enter sleep, while other UEs continue to be active until the configured on-duration ends or until further signaling is received.

[0229] In at least one example, the unit field may also be used to indicate activation and / or deactivation of the DRX mode. Fig.16As shown, a bit value of 1 may indicate activation of a DRX mode with a given DRX configuration for a corresponding mobile radio communication terminal device (e.g., UE). If the UE does not operate based on any DRX mode, activation of the DRX mode may alternatively also be used as a GTS, for example, when the UE sleeps for a certain offset before the start of the DRX cycle. In other words, the GTS signaling may trigger a periodic on / off behavior of the UE, which may be similar to the activation of the DRX mode, or alternatively, the GTS signaling may indicate a sleep duration of an instance without implying any periodicity, that is, the UE wakes up after the indicated sleep duration and resumes operation according to the pre-existing configuration.

[0230] If the DCI only provides a GTS trigger, a mobile radio communication terminal device (e.g., UE) that receives the trigger as true may follow a device / UE-specific configured parameter set, such as T_GTS_A and / or T_GTS_B, as described herein with respect to GTS signaling. After the sleep duration expires, the mobile radio communication terminal device / UE may continue to follow the existing DRX configuration.

[0231] In various examples, multiple mobile radio communication terminal devices (eg, UEs) receiving the GTS and / or activation trigger in the GC-DCI may have different DRX configurations, such as different DRX cycles and / or different on-durations, etc. For example, in Fig.17 In the exemplary embodiment of FIG. 1 , two mobile radio communication terminal devices (eg UEs) are shown which have received a GTS or activation trigger in a GC DCI, however each UE has a different DRX configuration.

[0232] In at least one example, one or more of the following higher layer configurations may be provided to a mobile radio communication terminal device (eg, UE) so that the UE reacts accordingly after a GTS trigger:

[0233] - If an offset is configured, the sleep duration starts after the offset.

[0234] - If not, the speed at which the UE goes to sleep may be affected by the UE's capabilities, ie once it detects the GTS trigger is true and turns off the RF or baseband components.

[0235] - Sleep for a given duration. The duration may also vary with the configured on-duration, such as the time remaining for the UE to sleep

[0236] - Switch to a different BWP in the next K-th DRX cycle, K ≥ 1

[0237] -Monitor a reduced number of PDCCH candidates for one or more of the subsequent On-Durations

[0238] In at least one example, one or more mobile radio communication terminal device (e.g., UE) specific configurations may be dynamically indicated in a mobile radio communication terminal device (e.g., UE) specific field, such as:

[0239] - offset to start of sleep duration

[0240] - Sleep duration

[0241] - Bandwidth Part ID, when the UE wakes up in a different bandwidth part after the sleep duration,

[0242] - Switching DRX parameters within an existing DRX configuration, e.g. switching between long and short DRX cycles

[0243] -DRX configuration index

[0244] The UE-specific field may include more than one bit and / or may have more than one subfield in order to dynamically indicate one or more parameters.

[0245] In at least one example, a mobile radio communication terminal device or UE specific field may have K bits indicating an index of a configuration from a set of configurations. Each configuration may include one or more of the above parameters or indications. For example, a UE specific field may have 2 bits, which may be configured as follows:

[0246] Place value Indication value / parameter set / trigger 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

[0247] In one or more exemplary embodiments of the present disclosure, a common DCI format may be used to signal the WUS. In at least one exemplary embodiment, each mobile radio communication terminal device / UE specific field may have only 1 bit, where bit=1 may indicate wake-up, and bit=0 may indicate no wake-up for a given mobile radio communication terminal device / UE.

[0248] Fig.18 The exemplary embodiment of shows a common DCI format structure with five mobile radio communication terminal device / UE specific fields, wherein each mobile radio communication terminal device / UE specific field has 1 bit therein. Bit=1 indicates that the WUS trigger is true, and bit=0 indicates that the WUS trigger is false. Fig.18An example is shown in which K=5 mobile radio communication terminals (e.g., UEs) are configured to monitor common DCI, and in which only UEs mapped to the 2nd and 5th fields are indicated with a WUS trigger, and other UEs do not have any WUS trigger. Therefore, upon detecting a DCI format, the UEs mapped to the 2nd and 5th fields may wake up for a subsequent duration to monitor the scheduling 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.

[0249] In one or more exemplary embodiments of the present disclosure, one or more mobile radio communication terminal device / UE specific configurations may be dynamically indicated in a mobile radio communication terminal device / UE specific field, such as:

[0250] -N gap Or the offset to the start of the on-duration for PDCCH monitoring, such as drx-onDurationTimer or drx-InactivityTime

[0251] - Duration of PDCCH monitoring

[0252] - Bandwidth Part ID, when UE wakes up in a different bandwidth part after WUS detection,

[0253] - Switching DRX parameters within an existing DRX configuration, e.g. switching between long and short DRX cycles

[0254] -DRX configuration index

[0255] - A PDCCH candidate set (e.g., possibly of reduced size) for monitoring one or more of the subsequent On-Durations

[0256] -Deactivation of DRX mode

[0257] The UE-specific field may include more than one bit and / or may have more than one subfield 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 supported features after WUS detection, or indicated as part of different signaling. For example, N gap May be configured by a higher layer rather than indicated in the WUS.

[0258] In at least one other embodiment or option, 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.

[0259] In one or more examples, the mobile radio communication terminal device / UE specific field may have K bits, which indicate an index of a configuration from a set of configurations. Each configuration may include one or more of the above parameters or indications. For example, the mobile radio communication terminal device / UE specific field may have 2 bits, which may be configured as follows:

[0260]

[0261] In various examples, 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.

[0262] In one or more examples, if activation / deactivation of the DRX mode is indicated dynamically or GTS and WUS signaling may be used as activation and deactivation signaling, respectively, more generally, the mobile radio communication terminal device / UE may be configured to receive one or more of the following indications in a mobile radio communication terminal device / UE specific field in a common DCI:

[0263] -Activation signaling

[0264] - Activation signaling with GTS - the mobile radio communication terminal / UE starts the DRX cycle after an offset or sleep duration

[0265] - without activated GTS signalling, i.e. GTS signalling may be received independently, e.g. GTS signalling may be received to put the mobile radio communication device / UE into micro-sleep, and after expiry, the mobile radio communication device / UE resumes DRX mode operation

[0266] -Deactivation signaling

[0267] -Deactivation signaling with WUS, i.e. WUS signaling itself is used for or indicates deactivation of DRX mode

[0268] - No WUS signaling with deactivation, that is, the mobile radio communication device / UE only monitors the on-duration of PDCCH monitoring after WUS detection and does not exit DRX mode

[0269] In one or more examples, if configured for monitoring by a mobile radio communication terminal device (e.g., UE), the same common RNTI may be used to detect GTS and WUS. Since GTS and WUS are monitored at different times, from the perspective of the UE, a separate RNTI may not be required. In at least one example, a unified DCI format with the same common RNTI may be used to indicate GTS and WUS and / or activation and deactivation of a DRX mode. Since the transmission timings of WUS and GTS are mutually exclusive, an explicit indication of whether DCI is sent for GTS or WUS may not be required. 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 dormant state, it can only receive WUS. Therefore, considering which state the UE is currently in, different bit fields within the UE-specific field in the GC DCI may have different interpretations, such as:

[0270] Field used to indicate activation and deactivation of DRX mode:

[0271] - If received during active state while monitoring PDCCH or scheduling DCI: Bit field = 0 may mean activation, 1 may mean deactivation of DRX mode, and vice versa

[0272] - If received during the WUS monitoring duration, then: Bit field = 0 may mean remaining in activated DRX mode, 1 may mean deactivation of DRX mode, and vice versa.

[0273] Fields used to indicate the offset to the start of the sleep or on duration:

[0274] - If received during active state while monitoring PDCCH or scheduling DCI, then: This field may indicate the offset to the start of the sleep duration

[0275] - If received during the WUS Monitoring Duration, then: This field may indicate the offset to the start of the subsequent On Duration for PDCCH monitoring

[0276] Fields to indicate sleep or power-on durations for:

[0277] - If received during active state while monitoring PDCCH or scheduling DCI, then: This field may indicate the sleep duration

[0278] - The indicated sleep duration may last less than or longer than the DRX cycle

[0279] - If received during the WUS Monitoring Duration, then: This field indicates the on-duration for PDCCH monitoring.

[0280] - The indicated sleep duration may last less than or longer than the DRX cycle

[0281] Field used to indicate bandwidth section ID

[0282] - If received during active state while monitoring PDCCH or scheduling DCI, then: This field indicates the bandwidth portion that the UE turns on at subsequent occasions

[0283] - If received during the WUS monitoring duration, then: This field instructs the UE to wake up and monitor the bandwidth portion of the scheduling DCI

[0284] Field used to indicate an update to the number of PDCCH candidates

[0285] In at least one example, the DRX configuration is not explicitly indicated, and along with the indication of the bandwidth portion, the mobile radio communication terminal device (eg, UE) identifies the DRX configuration if the DRX configuration is associated with the bandwidth portion.

[0286] In at least one example, the GC DCI may have both mobile radio communication terminal device (eg, UE) specific fields and common fields. Fig.19 The exemplary embodiment of shows the general structure of such a DCI format, in which there are K mobile radio communication terminal device / UE specific fields and M common fields. Each mobile radio communication terminal device / UE configured to monitor the DCI format will obtain control information from the corresponding UE specific field and the M common fields.

[0287] For example, 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:

[0288] - offset to start of sleep duration

[0289] - Sleep duration - This means that UEs that receive a GTS trigger true may have the same sleep duration. This may help indicate in a common way whether there is a correlation between the traffic arrival patterns of a group of UEs monitoring GC-DCI

[0290] Similarly, in the context of GC DCI for WUS, a common field may be used to indicate at least the on-duration for PDCCH monitoring after detection of WUS DCI.

[0291] Although not shown in the above structure, the GC DCI format used for DRX mode adaptation and / or power saving signaling triggers such as WUS / GTS may also have some reserved bit fields.

[0292] According to an exemplary embodiment of the present disclosure, Fig. 20 A call flow diagram is included showing some signaling and mobile radio communication terminal device / UE behavior steps before and after detecting a WUS DCI. That is, Fig. 20 The flowchart of the embodiment shows an example of the steps of UE operation when a mobile radio communication terminal device (e.g., UE) is configured to monitor WUS in a common DCI. After the RRC_connection state is established, the UE receives one or more RRC signaling for receiving DRX configuration, a start signaling for monitoring WUS DCI, other necessary signaling for DCI configuration, search space association, etc. When the WUS DCI is detected, the UE wakes up for PDCCH monitoring in a subsequent duration and continues according to the configured DRX mode.

[0293] In various embodiments of the present disclosure, DRX_RNTI may be 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. A mobile radio communication terminal device (e.g., UE) may be configured to monitor GTS and / or WUS and / or other DRX mode adaptive GC DCI formats 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:

[0294] - A higher layer parameter RNTI_monitoring, which is used to inform the UE that it should monitor DCI formats with DRX_RNTI in the search space set in a given CORESET

[0295] -PDCCH monitoring periodicity, e.g., K ≥ 1 symbol / slot

[0296] -PDCCH monitoring offset, e.g. M ≥ 0 symbols / slot,

[0297] -In one example, M ≤ K

[0298] -PDCCH monitoring mode

[0299] - In one example, the first symbol of a CORESET is within a slot or a group of symbols

[0300] -PDCCH candidates per aggregation level

[0301] In one or more examples, 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, while monitoring WUS DCI with only one aggregation level, thereby reducing complexity and increasing power savings when the mobile radio communication terminal device / UE operates in DRX mode. In addition, the monitoring periodicity may be different for GTS DCI and WUS DCI. For example, during a possibly relatively short WUS monitoring window, there may be more than one WUS monitoring opportunity, so that the mobile radio communication terminal device / UE does not miss the WUS. For example, once the mobile radio communication terminal device / UE detects a WUS, it may not monitor the WUS at subsequent opportunities.

[0302] In at least one other example, the DCI payload size may be configured by higher layers via MSI, RMSI, OSI, or RRC signaling.

[0303] In one or more examples, 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 higher layer configurable in a mobile radio communication terminal device (eg UE)-specific, cell-specific or group-specific manner.

[0304] In various exemplary embodiments of the present disclosure, instead of a DCI format with a CRC scrambled by RNTI attached, control information can be transmitted in a sequence without a CRC, especially when the payload is small. However, in order to achieve effective resource management from a network perspective, sequences with mobile radio communication terminal equipment / UE-specific control information can be code-multiplexed on common time-frequency resources. In other words, a group of mobile radio communication terminal equipment / UE monitors / receives corresponding sequences in common time-frequency resources. Mobile radio communication terminal equipment / UE-specific sequences are multiplexed and transmitted in common time-frequency resources.

[0305] Fig.21 The exemplary embodiment of includes a general structure for mapping mobile radio communication terminal device (e.g., UE) specific control information to a coding, modulation and spreading sequence, which is multiplexed with symbols of other mobile radio communication terminal devices / UEs, and then mapping the composite multiplexed signal of a group of UEs to a set of common REs after necessary scrambling, layer processing and other necessary steps. That is, Fig.21A general structure is shown, in which M≥1 bits of the control information payload of a mobile radio communication terminal device / UE are encoded into K bits, for example, a simple repetition coding can be applied, where K can be a multiple of M. The coded bits are then modulated and subsequently spread by an L-point sequence. The sequence can be UE-specific configured by a higher layer. In one example, the sequence can be obtained based on the C-RNTI. The selection of sequences can include Walsh sequences, Zadoff-Chu sequences, Gold sequences, etc. Finally, the LK spread symbols of different UEs are multiplexed and then mapped to a set of common REs after further processing (such as layer mapping, scrambling, etc.).

[0306] In the table below, examples of extended sequences of length four for a normal CP are shown. In one example, each mobile radio communication terminal device / UE is indicated an index from the group, and different UEs for sequences in a common set of resources are indicated different indices by the network.

[0307]

[0308] The examples considered above for mobile radio communication terminal device / UE specific content transmitted in GC DCI also apply here, for example, M-bit control information payload can be used to indicate GTS / WUS triggering and / or adjust DRX parameters and / or switch DRX configuration, etc.

[0309] In various exemplary embodiments of the present disclosure, a mobile radio communication terminal device (e.g., UE) needs to know where it finds at least one resource set of sequence-based control information. In one example, one or more resource sets are configured to the UE for each configured DL BWP. The configuration of the resource set may be provided together with the bandwidth part configuration or provided separately. The configuration of each resource set includes one or more of the following:

[0310] - Resource set index

[0311] - Number of consecutive symbols

[0312] -PRB Set

[0313] -CCE to REG mapping

[0314] -REG bundling size, in case of interleaved CCE to REG mapping

[0315] - Cyclic shift for REG bundling interleaver

[0316] More generally, in various examples, a resource set may be mapped to K ≥ 1 PRBs and M ≥ 1 consecutive symbols. Several examples of resource set RE mapping are given in Fig. 22In one or more alternatives, the K physical resource blocks (PRBs) may or may not be continuous in the frequency domain.

[0317] Fig. 22 An exemplary embodiment shows a resource set, in which a multiplexing sequence of mobile radio communication terminal device / UE-specific control information including K mobile radio communication terminal devices / UEs is shown as being mapped to (4 PRBs, 1 offset (OS)), (2 PRBs, 2 OS), (1 PRB, 4 OS) as examples.

[0318] In various examples, in each resource set, there may be one or more search spaces configured as detection sequences. As part of the search space configuration, the mobile radio communication terminal device / UE may obtain one or more of the following related to the DCI format:

[0319] -The relationship between the search space and the resource set

[0320] - Aggregation level

[0321] -Monitoring periodicity, e.g., K ≥ 1 symbol / slot

[0322] - Monitoring offset, e.g., M symbols / slots, where, for example, M may be

[0323] 0≤M <K

[0324] - Monitoring pattern, e.g. the first symbol of one or more resource sets within a time slot

[0325] In one or more examples, to reduce complexity, only one aggregation level (such as 2, 4, 8, or 16) may be utilized to monitor the search space for sequence-based monitoring of DCI formats.

[0326] In one or more examples, 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 inform the mobile radio communication terminal device / UE to monitor DCI formats based on sequences in the search space without any RNTI attached. In other words, as part of the search space configuration, the mobile radio communication terminal device / UE will be informed to monitor sequence-based DCI formats with a given aggregation level in the search space.

[0327] In one or more examples, the WUS may be a sequence-based DCI without RNTI, while the GTS DCI may be a PDCCH with RNTI. This may help ensure low complexity WUS detection.

[0328] In another example, 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 resources for SSB, a given CORESET, etc.). In one example, 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 to the given CORESET location. For example, the starting PRB of the resource set may be obtained as an offset from the edge PRB of the CORESET. Fig.10 In the example, offset = 0 is considered. Other parameters of the resource set configuration are configured by higher layers.

[0329] In one or more examples, the sequence may be mapped to one or more resource sets with or without repetition. The repetition factor may be higher layer configured, such as UE-specific or group-based RRC signaling.

[0330] In one or more examples, resource sets used to transmit sequence-based DCI for the GTS may be avoided from being used for PDSCH scheduling, that is, the PDSCH may be rate matched around the resource sets.

[0331] Although reducing unnecessary PDCCH monitoring can improve mobile UE power consumption through dynamic DRX mode management, some general signaling mechanisms can be used to activate / deactivate some parameters to improve mobile radio communication terminal equipment / UE power consumption in the presence or absence of active DRX mode operation. In particular, for any of the DCI signaling implementations considered above, one or more of the following parameters may be included in a mobile radio communication terminal equipment (e.g., UE) specific field:

[0332] - Activation and / or deactivation of secondary carriers

[0333] - K ≥ 1 bit field can be used to indicate the carrier ID

[0334] - Activation and / or deactivation of a group of UE antennas

[0335] - L ≥ 1 bit field can be used to indicate the index or set of indices of UE antennas and / or RF chains

[0336] - The network and the UE exchange UE antenna configurations and corresponding indices of the UE antennas prior to signaling for activation / deactivation.

[0337] Alternatively, MAC CE signaling may be used instead of DCI-based signaling to activate / deactivate the parameters.

[0338] In various exemplary embodiments, the monitoring opportunity of the power saving signal / channel outside of the active time is "indicated" to the UE by the access node (e.g., gNB) with an offset before DRX is turned on. For example, by explicit signaling through higher layer signaling or through CORESET / search space access mode.

[0339] In various exemplary embodiments, for power saving signals / channels configured outside of active time (scheduled on or monitoring time, such as DRX_ON), ​​a new DCI format may be used for the UE, where the UE is configured to monitor the new DCI format, where the UE's power saving information may be configured by RRC.

[0340] In various exemplary embodiments, a new RNTI (eg, PS-RNTI) may be used for PDCCH-based power saving signaling / channel decoding at least outside of active time, and may be UE-specifically configurable.

[0341] In various exemplary embodiments, more than one monitoring occasion for a UE may be configured within one or more time slots prior to implementing DRX on (eg, monitoring).

[0342] In various exemplary embodiments, the maximum number of CORESETs of PDCCH-based power saving signals / channels outside of active time may not be greater than the maximum number that can be configured during active time. In various embodiments, the wireless device may be a base station, such as an eNodeB, a gnB, a network, etc. In various embodiments of the present disclosure, the wake-up indication may indicate to the UE whether to wake up. For example, the wake-up indication may indicate to the UE to wake up—for example, it may include or be implemented as a wake-up signal trigger, or it may be implemented as a signal to suppress or prevent wake-up in the UE.

[0343] The following examples relate to further exemplary implementations:

[0344] Embodiment 1 is a method, comprising receiving, by a first user equipment (UE), a first signaling for configuring a discontinuous reception (DRX) mode, the DRX mode including at least one DRX configuration; operating by the first UE in the DRX mode configured with the at least one DRX configuration; receiving, by the first UE, a configuration of a second signaling; receiving by the first UE the second signaling in a time-frequency resource of a common search space, wherein the first UE receives the second signaling during a closed / inactive state of the DRX mode configured with the at least one DRX configuration, and wherein the second signaling includes a wake-up indication; detecting by the first UE the wake-up indication in the second signaling, wherein the wake-up indication indicates that the first UE wakes up; and waking up by the first UE to monitor downlink control information (DCI) in a physical downlink control channel (PDCCH) after a first duration after detecting the wake-up indication in the second signaling ends.

[0345] In embodiment 2, according to the method of embodiment 1, the common search space is associated or allocated to be monitored by at least one UE other than the first UE. In embodiment 3, according to the method of embodiment 2, the common search space is associated with or allocated to be monitored by a group of UEs, wherein the UE belongs to the group of UEs. In embodiment 4, according to the method of any one of embodiments 1 to 3, the first signaling includes radio resource control (RRC) signaling. In embodiment 5, according to the method of any one of embodiments 1 to 4, the second signaling includes L1 signaling. In embodiment 6, according to the method of embodiment 5, the L1 signaling includes a group common DCI message transmitted in a PDCCH. In embodiment 7, according to the method of embodiment 6, the group common DCI message is attached with a cyclic redundancy check (CRC) scrambled by a common radio network temporary identifier (RNTI). In embodiment 8, according to the method of embodiment 7, the common RNTI is a power saving RNTI (PS-RNTI). In embodiment 9, according to the method of any one of embodiments 1 to 8, the first duration is configured by higher layer signaling received by the UE before the second signaling. In embodiment 10, according to the method of any one of embodiments 1 to 9, the first UE receives the second signaling in a first bandwidth part (BWP), and the first UE wakes up in a second BWP after the first duration ends, and the second BWP is different from the first BWP. In embodiment 11, according to the method of embodiment 10, the second BWP is greater than the first BWP. In embodiment 12, according to the method of any one of embodiments 10 or 11, the configuration of the second control signaling indicates a UE-specific field in the group common DCI, a PDCCH monitoring periodicity, and / or a PDCCH monitoring offset. In embodiment 13, according to the method of any one of embodiments 5 to 12, the group common DCI message includes a plurality of UE-specific fields. In embodiment 14, according to the method of embodiment 13, the plurality of UE-specific fields of the group common DCI message correspond to a plurality of UEs, respectively. In embodiment 15, according to the method of embodiment 13 or 14, each of the plurality of UE-specific fields contains at least one information bit. In embodiment 16, according to the method of embodiment 14 or 15, at least one UE-specific field of the plurality of UE-specific fields contains a wake-up indication of at least one corresponding UE of the corresponding UEs. In embodiment 17, according to the method described in any one of embodiments 14 to 16, at least one UE-specific field among the multiple UE-specific fields contains information indicating an identifier for the at least one corresponding UE to wake up the BWP in an on / active state after the wake-up indication.In embodiment 18, according to the method of any one of embodiments 1 to 17, the first duration is a non-zero gap between the end of the resource of receiving the second signaling and the next on / active state of the UE after the second signaling. In embodiment 19, according to the method of any one of embodiments 1 to 18, it also includes first receiving and detecting a third signaling by the UE via higher layer signaling before receiving the second signaling, wherein the third signaling configures the first UE to monitor the second signaling. In embodiment 20, according to the method described in any one of embodiments 1 to 19, the at least DRX configuration of the DRX mode includes configurations for: the duration at the start of the DRX cycle of the DRX mode when the first UE monitors at least PDCCH (drx-onDurationTimer); the delay before the first UE starts the drx-onDurationTimer (drx-SlotOffset); the subframe of the DRX cycle in which the first UE starts the DRX mode (drx-StartOffset); the duration after the UE receives a message in the PDCCH indicating a new uplink (UL) or downlink (DL) transmission for a MAC entity (drx-I nactivityTimer); the maximum duration until a DL retransmission is received (drx-RetransmissionTimerDL); the maximum duration until an authorization for UL retransmission is received (drx-RetransmissionTimerUL); the long DRX cycle (drx-LongCycle); the short DRX cycle (drx-ShortCycle); the duration that the first UE should be in the on / active state after the short DRX cycle (drx-ShortCycleTimer); the minimum duration before the MAC entity expects a DL allocation for HARQ retransmission (drx-HARQ-RTT-TimerDL) and / or the minimum duration before the MAC entity expects a UL HARQ retransmission authorization (drx-HARQ-RTT-TimerUL).

[0346] Embodiment 21 is a device implemented in a user equipment (UE), the device comprising: an interface circuit; and a processing circuit, the processing circuit being coupled to the interface circuit and configured to: receive via the interface circuit a first signaling for configuring a DRX mode including at least one discontinuous reception (DRX) configuration; operate in the DRX mode having the at least one DRX configuration; receive via the interface circuit a configuration of a second signaling; during a closed / inactive state of the DRX mode configured with the at least one DRX configuration, receive via the interface circuit the second signaling in a time-frequency resource of a common search space, wherein the second signaling includes a wake-up indication; detect the wake-up indication in the second signaling, wherein the detected wake-up indication indicates that the UE wakes up; and after a first duration after the wake-up indication is detected in the second signaling, wake up to an on / active state to monitor at least downlink control information (DCI) in a physical downlink control channel (PDCCH).

[0347] In embodiment 22, the apparatus of embodiment 21, wherein the first signaling comprises receiving radio resource control (RRC) signaling. In embodiment 23, the apparatus of embodiment 21 or 22, wherein receiving the second signaling comprises L1 signaling. In embodiment 24, the apparatus of embodiment 23, wherein the L1 signaling comprises a group common DCI message transmitted in a PDCCH. In embodiment 25, the apparatus of embodiment 24, wherein the group common DCI message is appended with a CRC scrambled by a common radio network temporary identifier (RNTI). In embodiment 26, the apparatus of embodiment 25, wherein the common RNTI is a power saving RNTI (PS-RNTI). In embodiment 27, the apparatus of embodiment 26, wherein the length of the first duration is configured by higher layer signaling. In embodiment 28, the apparatus of any one of embodiments 21 to 27, wherein the processing circuit is further configured to receive the first signaling in a first bandwidth part (BWP) via the interface circuit, and wherein the one or more processors cause the UE to wake up in a second BWP, the second BWP being different from the first BWP. In embodiment 29, the apparatus according to embodiment 28, wherein the bandwidth of the second BWP is less than the bandwidth of the first BWP. In embodiment 30, the apparatus according to embodiment 28 or 29, wherein the configuration of the second control signaling indicates a UE-specific field in the group common DCI, a PDCCH monitoring periodicity, and / or a PDCCH monitoring offset. In embodiment 31, the apparatus according to any one of embodiments 24 to 30, wherein the group common DCI message includes a plurality of UE-specific fields. In embodiment 32, the apparatus according to embodiment 31, wherein the plurality of UE-specific fields of the group common DCI message correspond to a plurality of UEs, respectively. In embodiment 33, the apparatus according to embodiment 31 or 32, wherein each of the plurality of UE-specific fields contains at least one information bit. In embodiment 34, the apparatus according to any one of embodiments 32 to 33, wherein at least one UE-specific field of the plurality of UE-specific fields of the group common DCI message includes information indicating a wake-up indication for at least one of the corresponding UEs. In embodiment 35, the apparatus of any one of embodiments 32 to 34, wherein at least one UE-specific field of the plurality of UE-specific fields of the group common DCI message includes information indicating an identity of a BWP for at least one corresponding UE to wake up after a wake-up indication. In embodiment 36, the apparatus of any one of embodiments 21 to 35, wherein the first duration is a non-zero gap between an end of a resource in which the second signaling is received and a start of a next on / active state after the second signaling.In embodiment 37, according to an apparatus as described in any one of embodiments 21 to 36, the processing circuit is further configured to receive and detect third signaling via higher layer signaling and before the second signaling, wherein the third signaling causes the processing circuit to monitor the second signaling. In embodiment 38, according to an apparatus as described in any one of embodiments 21 to 37, the at least DRX configuration of the DRX mode includes configurations for: the duration at the start of the DRX cycle of the DRX mode when the first UE monitors at least PDCCH (drx-onDurationTimer); the delay before the first UE starts the drx-onDurationTimer (drx-SlotOffset); the subframe at which the first UE starts the DRX cycle of the DRX mode (drx-StartOffset); the duration after the UE receives a PDCCH message indicating a new uplink (UL) or downlink (DL) transmission for a MAC entity (drx-StartOffset); rx-InactivityTimer); the maximum duration until a DL retransmission is received (drx-RetransmissionTimerDL); the maximum duration until an authorization for UL retransmission is received (drx-RetransmissionTimerUL); a long DRX cycle (drx-LongCycle); a short DRX cycle (drx-ShortCycle); the duration of the short DRX cycle that the first UE should follow (drx-ShortCycleTimer); the minimum duration before the MAC entity expects a DL allocation for HARQ retransmission (drx-HARQ-RTT-TimerDL) and / or the minimum duration before the MAC entity expects a UL HARQ retransmission authorization (drx-HARQ-RTT-TimerUL). In embodiment 39, an apparatus according to any one of embodiments 21 to 38, wherein the common search space is associated or allocated to be monitored by at least one UE other than the first UE. In embodiment 40, the apparatus according to embodiment 39, wherein the common search space is associated with or allocated to be monitored by a group of UEs, wherein the UE belongs to the group of UEs.

[0348] Embodiment 41 is a method, comprising: transmitting by a wireless device a first signaling for configuring a discontinuous reception (DRX) mode, the DRX mode comprising at least one DRX configuration in at least one user equipment (UE); transmitting by the wireless device a configuration of a second signaling; transmitting by the wireless device the second signaling in time-frequency resources of a common search space during an expected scheduled off / inactive state in the DRX mode of the at least one UE, wherein the second signaling comprises a wake-up indication, wherein the wake-up indication indicates that the at least one UE wakes up; and in response to the wake-up indication of the second signaling, transmitting by the wireless device at least one message in a physical downlink control channel (PDCCH) or a physical sidelink shared channel (PSSCH) message during an expected on / active state in the at least one UE for monitoring a PDCCH or PSSCH message of the at least one UE.

[0349] In embodiment 42, according to the method of embodiment 41, the common search space is allocated to a UE group including the at least one UE or is associated with monitoring of the UE group. In embodiment 43, according to the method of embodiment 41 or 42, the first signaling includes radio resource control (RRC) signaling. In embodiment 44, according to any one of embodiments 41 to 43, the second signaling includes L1 signaling. In embodiment 45, according to the method of embodiment 44, the L1 signaling includes a group common DCI message transmitted in a PDCCH. In embodiment 46, according to the method of embodiment 45, the group common DCI message is attached with a CRC scrambled by a common radio network temporary identifier (RNTI). In embodiment 47, according to the method of embodiment 46, the common RNTI is a power saving RNTI (PS-RNTI). In embodiment 48, according to the method of embodiment 45, the length of the first duration is indicated in the signaling transmitted before the second signaling. In embodiment 49, according to the method of any one of embodiments 41 to 48, the mobile radio communication device transmits the second signaling in a first bandwidth part (BWP) and transmits the PDCCH or PSSCH message in a second BWP, and the second BWP is different from the first BWP. In embodiment 50, according to the method of embodiment 49, the second BWP is greater than the first BWP. In embodiment 51, according to the method of any one of embodiments 45 to 50, the configuration of the second control signaling indicates a UE-specific field in the group common DCI, a PDCCH monitoring periodicity and / or a PDCCH monitoring offset. In embodiment 52, according to the method of any one of embodiments 45 to 51, the group common DCI message includes multiple UE-specific fields. In embodiment 53, according to the method of embodiment 52, the multiple UE-specific fields of the group common DCI message correspond to multiple UEs respectively. In embodiment 54, according to the method of embodiment 52 or 53, each UE-specific field of the multiple UE-specific fields contains at least one information bit. In embodiment 55, according to the method of embodiment 53 or 54, at least one UE-specific field among the multiple UE-specific fields contains information indicating a wake-up indication for at least one of the corresponding UEs. In embodiment 56, according to the method of any one of embodiments 52 to 55, at least one UE-specific field among the multiple UE-specific fields contains information indicating an identifier of a BWP for the at least one corresponding UE to wake up after the sent wake-up indication.In embodiment 57, according to the method described in any one of embodiments 41 to 56, the at least DRX configuration of the DRX mode includes configurations for: the duration at the start of the DRX cycle of the DRX mode when the first UE monitors at least PDCCH (drx-onDurationTimer); the delay before the first UE starts the drx-onDurationTimer (drx-SlotOffset); the subframe at which the first UE starts the DRX cycle of the DRX mode (drx-StartOffset); the duration after the UE receives a PDCCH message indicating a new uplink (UL) or downlink (DL) transmission for a MAC entity (drx- rx-InactivityTimer); the maximum duration until a DL retransmission is received (drx-RetransmissionTimerDL); the maximum duration until an authorization for UL retransmission is received (drx-RetransmissionTimerUL); a long DRX cycle (drx-LongCycle); a short DRX cycle (drx-ShortCycle); the duration that the first UE should follow the short DRX cycle (drx-ShortCycleTimer); the minimum duration before the MAC entity expects a DL allocation for HARQ retransmission (drx-HARQ-RTT-TimerDL) and / or the minimum duration before the MAC entity expects a UL HARQ retransmission authorization (drx-HARQ-RTT-TimerUL). In embodiment 58, the method according to any one of embodiments 41 to 57 also includes: before transmitting the second signaling, first the wireless device transmits a third signaling via a higher layer signaling, wherein the third signaling is configured to instruct the at least one UE to monitor the second signaling.

[0350] Embodiment 59 is an apparatus to be implemented in a wireless device, the apparatus comprising: an interface circuit; and a processing circuit, the processing circuit coupled to the interface circuit to: transmit a first signaling for configuring a discontinuous reception (DRX) mode via the interface circuit, the DRX mode comprising at least one DRX configuration in at least one user equipment (UE); transmit the configuration of a second signaling via the interface circuit; transmit the second signaling in time-frequency resources of a common search space during an expected off / inactive state of the DRX mode in the at least one UE via the interface circuit, wherein the second signaling includes a wake-up indication, and wherein the wake-up indication indicates that the at least one UE wakes up; and in response to the wake-up indication of the second signaling, transmit at least one message in a physical downlink control channel (PDCCH) or a physical sidelink shared channel (PSSCH) by at least one transmitter during an expected on / active state in the at least one UE.

[0351] In embodiment 60, the apparatus of embodiment 59, wherein the common search space is associated with or allocated to a group of UEs for monitoring, wherein the group of UEs includes the at least one UE. In embodiment 61, the apparatus of embodiment 59 or 60, wherein the first signaling includes radio resource control (RRC) signaling. In embodiment 62, the apparatus of any one of embodiments 59 to 61, wherein the second signaling includes L1 signaling. In embodiment 63, the apparatus of embodiment 62, wherein the L1 signaling includes a group common DCI message transmitted in a PDCCH. In embodiment 64, the apparatus of embodiment 63, wherein the group common DCI message is appended with a CRC scrambled by a common radio network temporary identifier (RNTI). In embodiment 65, the apparatus of embodiment 64, wherein the common RNTI is a power saving RNTI (PS-RNTI). In embodiment 66, the apparatus of embodiment 63, wherein the one or more processors cause the wireless device to transmit signaling before the transmission of the second signaling, the signaling indicating the length of the first duration of the at least one UE after the second signaling. In embodiment 67, the apparatus according to any one of embodiments 59 to 66, wherein the processing circuit further transmits the second signaling in a first bandwidth part (BWP) via the interface circuit, and transmits a PDCCH or PSSCH message in a second BWP, the second BWP being different from the first BWP. In embodiment 68, the apparatus according to embodiment 67, wherein the second BWP is greater than the first BWP. In embodiment 69, the apparatus according to any one of embodiments 63 to 68, wherein the configuration of the second control signaling indicates a UE-specific field in the group common DCI, a PDCCH monitoring periodicity, and / or a PDCCH monitoring offset. In embodiment 70, the apparatus according to any one of embodiments 63 to 69, wherein the group common DCI message includes a plurality of UE-specific fields. In embodiment 71, the apparatus according to embodiment 70, wherein the plurality of UE-specific fields of the group common DCI message correspond to a plurality of UEs, respectively. In embodiment 72, the apparatus according to embodiment 70 or 71, wherein each of the plurality of UE-specific fields contains at least one information bit. In embodiment 73, according to any one of embodiments 70 or 72, at least one UE-specific field of the plurality of UE-specific fields includes information indicating a wake-up indication for at least one of the corresponding UEs. In embodiment 74, according to any one of embodiments 70 to 73, at least one UE-specific field of the plurality of UE-specific fields includes information indicating an identifier of a BWP for the at least one corresponding UE to wake up after the sent wake-up indication.In embodiment 75, according to the device described in any one of embodiments 59 to 74, the at least DRX configuration of the DRX mode includes configurations for: the duration at the beginning of the DRX cycle of the DRX mode when the first UE monitors at least PDCCH (drx-onDurationTimer); the delay before the first UE starts the drx-onDurationTimer (drx-SlotOffset); the subframe of the DRX cycle of the DRX mode at which the first UE starts (drx-StartOffset); the duration after the UE receives a PDCCH message indicating a new uplink (UL) or downlink (DL) transmission for a MAC entity (drx- rx-InactivityTimer); the maximum duration until a DL retransmission is received (drx-RetransmissionTimerDL); the maximum duration until an authorization for UL retransmission is received (drx-RetransmissionTimerUL); a long DRX cycle (drx-LongCycle); a short DRX cycle (drx-ShortCycle); the duration of the short DRX cycle that the first UE should follow (drx-ShortCycleTimer); the minimum duration before the MAC entity expects a DL allocation for HARQ retransmission (drx-HARQ-RTT-TimerDL) and / or the minimum duration before the MAC entity expects a UL HARQ retransmission authorization (drx-HARQ-RTT-TimerUL).

[0352] Embodiment 76 is one or more non-transitory computer-readable media comprising instructions, which, when executed by at least one processor of a user equipment (UE), causes the UE to: receive first signaling for configuring a DRX mode including at least one discontinuous reception (DRX) configuration; operate in the DRX mode configured with the at least one DRX configuration; receive configuration of a second signaling; during an off / inactive state of the DRX mode configured with the at least one DRX configuration, receive the second signaling in a time-frequency resource of a common search space, wherein the second signaling includes a wake-up indication; detect the wake-up indication in the second signaling, wherein the wake-up indication indicates that the UE wakes up; and after a first duration after receiving the second signaling, wakes up to an on / active state to monitor at least downlink control information (DCI) in a physical downlink control channel (PDCCH).

[0353] In embodiment 77, according to one or more non-transitory computer-readable media of embodiment 76, the common search space is a search space associated with at least one other UE or allocated to the at least one other UE for monitoring. In embodiment 78, according to one or more non-transitory computer-readable media of embodiment 76 or 77, the first signaling includes radio resource control (RRC) signaling. In embodiment 79, according to one or more non-transitory computer-readable media of any one of embodiments 76 to 78, the second signaling includes L1 signaling. In embodiment 80, according to one or more non-transitory computer-readable media of any one of embodiments 76 to 79, the L1 signaling includes a group common DCI message. In embodiment 81, according to one or more non-transitory computer-readable media of embodiment 80, the group common DCI message includes PDCCH signaling, the PDCCH signaling includes a group common DCI message transmitted in a PDCCH message. In embodiment 82, according to one or more non-transitory computer-readable media of embodiment 81, the group common DCI message is attached with a cyclic redundancy check (CRC) scrambled by a common radio network temporary identifier (RNTI). In embodiment 83, according to one or more non-transitory computer-readable media of embodiment 82, the common RNTI is a power saving RNTI (PS-RNTI). In embodiment 84, according to one or more non-transitory computer-readable media of any one of embodiments 76 to 83, the at least one processor further causes the UE to receive and detect third signaling, wherein the third signaling configures the length of the first duration. In embodiment 85, according to one or more non-transitory computer-readable media of any one of embodiments 76 to 84, the at least one processor further causes the UE to receive the first signaling in a first bandwidth part (BWP) and wake up in a second BWP, the second BWP being different from the first BWP. In embodiment 86, according to one or more non-transitory computer-readable media of embodiment 85, the second BWP is less than the first BWP. In embodiment 87, according to one or more non-transitory computer-readable media of any one of embodiments 76 to 86, the configuration of the second control signaling indicates a UE-specific field in the group common DCI, a PDCCH monitoring periodicity, and / or a PDCCH monitoring offset. In embodiment 88, according to one or more non-transitory computer-readable media of any one of embodiments 80 to 87, the group-common DCI message includes a plurality of UE-specific fields. In embodiment 89, according to one or more non-transitory computer-readable media of embodiment 88, the plurality of UE-specific fields of the group-common DCI message correspond to a plurality of UEs, respectively.In embodiment 90, according to one or more non-transitory computer-readable media of embodiment 88 or 89, each UE-specific field of the plurality of UE-specific fields comprises at least one information bit. In embodiment 91, according to one or more non-transitory computer-readable media of any one of embodiments 88 to 90, at least one UE-specific field of the plurality of UE-specific fields comprises a wake-up indication for at least one corresponding UE of the corresponding UEs. In embodiment 92, according to one or more non-transitory computer-readable media of any one of embodiments 88 to 91, at least one UE-specific field of the plurality of UE-specific fields comprises information indicating an identification of a BWP for the at least one corresponding UE to wake up after the wake-up indication. In embodiment 93, according to one or more non-transitory computer-readable media of any one of embodiments 76 to 92, the first duration is a non-zero gap between the end of the resource in which the second signaling is received and the beginning of the next on / active state after the second signaling. In embodiment 94, according to one or more non-transitory computer-readable media described in any one of embodiments 76 to 93, the at least DRX configuration of the DRX mode includes configurations for: the duration at the beginning of the DRX cycle of the DRX mode when the first UE monitors at least PDCCH (drx-onDurationTimer); the delay before the first UE starts the drx-onDurationTimer (drx-SlotOffset); the subframe at which the first UE starts the DRX cycle of the DRX mode (drx-StartOffset); the time after the UE receives a PDCCH message indicating a new uplink (UL) or downlink (DL) transmission for a MAC entity; duration (drx-InactivityTimer); maximum duration until DL retransmission is received (drx-RetransmissionTimerDL); maximum duration until authorization for UL retransmission is received (drx-RetransmissionTimerUL); long DRX cycle (drx-LongCycle); short DRX cycle (drx-ShortCycle); duration of the short DRX cycle that the first UE should follow (drx-ShortCycleTimer); minimum duration before the MAC entity expects DL allocation for HARQ retransmission (drx-HARQ-RTT-TimerDL) and / or the minimum duration before the MAC entity expects UL HARQ retransmission authorization (drx-HARQ-RTT-TimerUL).

[0354] Embodiment 95 is one or more non-transitory computer-readable media having instructions, which, when executed by one or more processors of a wireless device, cause the wireless device to perform the following operations, including: transmitting a first signaling for configuring a discontinuous reception (DRX) mode, the DRX mode including at least one DRX configuration in at least one user equipment (UE); transmitting a configuration of a second signaling; transmitting the second signaling in time-frequency resources of a common search space in an expected off / inactive state in the DRX mode of the at least one UE, wherein the second signaling includes a wake-up indication, wherein the wake-up indication indicates that the at least one UE wakes up; and in response to the second signaling including the wake-up indication, transmitting a message in a physical downlink control channel (PDCCH) or a physical sidelink shared channel (PSSCH) during an expected on / active state in the at least UE.

[0355] In embodiment 96, according to one or more computer-readable media of embodiment 95, the common search space is associated with or assigned to a group of UEs including the at least one UE. In embodiment 97, according to one or more computer-readable media of embodiment 95 or 96, the first signaling comprises radio resource control (RRC) signaling. In embodiment 98, according to one or more computer-readable media of any one of embodiments 95 to 97, the second signaling comprises L1 signaling. In embodiment 99, according to one or more computer-readable media of embodiment 98, the L1 signaling comprises a group common DCI message transmitted in a PDCCH. In embodiment 100, according to one or more non-transitory computer-readable media of embodiment 99, the group common DCI message is appended with a cyclic redundancy check (CRC) scrambled by a common radio network temporary identifier (RNTI). In embodiment 101, according to one or more computer-readable media of embodiment 100, the common RNTI is a power saving RNTI (PS-RNTI). In embodiment 102, according to one or more computer-readable media of embodiment 101, one or more processors further cause the UE to transmit higher layer signaling for configuring the length of the first duration before the transmission of the second signaling. In embodiment 103, according to one or more computer-readable media of any one of embodiments 95 to 102, the mobile radio communication device transmits the second signaling in a first bandwidth part (BWP) and transmits the PDCCH or PSSCH message in a second BWP, the second BWP being different from the first BWP. In embodiment 104, according to one or more computer-readable media of embodiment 103, the second BWP is greater than the first BWP. In embodiment 105, according to one or more computer-readable media of any one of embodiments 99 to 104, the configuration of the second control signaling indicates a UE-specific field in the group common DCI, a PDCCH monitoring periodicity, and / or a PDCCH monitoring offset. In embodiment 106, according to one or more computer-readable media of any one of embodiments 99 to 105, the group common DCI message includes a plurality of UE-specific fields. In embodiment 107, according to one or more computer-readable media of embodiment 106, the plurality of UE-specific fields of the group common DCI message respectively correspond to a plurality of UEs. In embodiment 108, according to one or more computer-readable media of any one of embodiments 106 or 107, each UE-specific field of the plurality of UE-specific fields comprises at least one information bit.In embodiment 109, according to one or more computer-readable media of embodiment 107, at least one UE-specific field of the multiple UE-specific fields contains a wake-up indication for at least one corresponding UE of the corresponding UEs. In embodiment 110, according to one or more computer-readable media of any one of embodiments 106 to 109, at least one UE-specific field of the multiple UE-specific fields contains information indicating an identification of a BWP for the at least one corresponding UE to wake up after the transmitted wake-up indication. In embodiment 111, according to one or more non-transitory computer-readable media of any one of embodiments 95 to 110, at least the DRX configuration of the DRX mode includes configurations for: a duration at the beginning of a DRX cycle of the DRX mode when the first UE monitors at least a PDCCH (drx-onDurationTimer); a delay before the first UE starts the drx-onDurationTimer (drx-SlotOffset); a subframe at which the first UE starts the DRX cycle of the DRX mode (drx-StartOffset); a time after the UE receives a PDCCH message indicating a new uplink (UL) or downlink (DL) transmission for a MAC entity duration (drx-InactivityTimer); maximum duration until DL retransmission is received (drx-RetransmissionTimerDL); maximum duration until authorization for UL retransmission is received (drx-RetransmissionTimerUL); long DRX cycle (drx-LongCycle); short DRX cycle (drx-ShortCycle); duration of the short DRX cycle that the first UE should follow (drx-ShortCycleTimer); minimum duration before the MAC entity expects DL allocation for HARQ retransmission (drx-HARQ-RTT-TimerDL), and / or minimum duration before the MAC entity expects UL HARQ retransmission authorization (drx-HARQ-RTT-TimerUL). In embodiment 112, according to one or more computer-readable media described in embodiment 95, it also includes: before transmitting the second signaling, the wireless device first transmits a third signaling, wherein the third signaling configures the at least one UE to monitor the second signaling.

[0356] In embodiment 109, a device implemented in a user equipment (UE) is disclosed, the device including: an interface circuit; and a processing circuit, the processing circuit being coupled to the interface circuit and configured to: receive via the interface circuit a first signaling for configuring a DRX mode including at least one discontinuous reception (DRX) configuration; operate in the DRX mode; receive a configuration of a second signaling via the interface circuit; during a closed / inactive state of the DRX mode configured with the at least one DRX configuration, receive the second signaling in a time-frequency resource of a common search space via the interface circuit, wherein the second signaling includes a wake-up indication; detect the wake-up indication in the second signaling, wherein the detected wake-up indication indicates that the UE wakes up; and after an offset after detecting the wake-up indication in the second signaling, wake up to an on / active state to monitor at least downlink control information (DCI) in a physical downlink control channel (PDCCH).

[0357] According to one aspect of the present disclosure, any reference to a “duration” such as “first duration”, “second duration”, or “at the end of the first duration” may be referred to as an “offset”, such as “first offset”, “second offset”, etc.

[0358] According to one aspect of the present invention, references to PSSCH may be implemented in PSCCH. Therefore, it is contemplated that the process, method or apparatus (reference implementation in PSSCH) implementing any principle described herein may be configured such that the referenced elements are executed in PSCCH.

[0359] It should be noted that one or more features of any of the above-described embodiments / implementations may be combined with any of the other embodiments / implementations.

[0360] abbreviation

[0361] For the purposes of this document, the following abbreviations may be applied to the examples and implementations discussed herein.

[0362] 3GPP Third Generation Partnership Project

[0363] 4G Fourth Generation

[0364] 5G Fifth Generation

[0365] 5GC 5G Core Network

[0366] ACK

[0367] AF Application Function

[0368] AM Confirmation Mode

[0369] AMBR Aggregate Maximum Bit Rate

[0370] AMF Access and Mobility Management Function

[0371] AN Access Network

[0372] ANR Automatic Neighbor Relation

[0373] AP application protocol, antenna port, access point

[0374] API Application Programming Interface

[0375] APN Access Point Name

[0376] ARP Assignment Reserve Priority

[0377] ARQ Automatic Repeat Request

[0378] AS Access Layer

[0379] ASN.1 Abstract Syntax Notation

[0380] AUSF authentication server function

[0381] AWGN Additive White Gaussian Noise

[0382] BCH Broadcast Channel

[0383] BER Bit Error Rate

[0384] BLER Block Error Rate

[0385] BPSK Binary Phase Shift Keying

[0386] BRAS Broadband Remote Access Server

[0387] BSS Business Support System

[0388] BS Base Station

[0389] BSR Buffer Status Report

[0390] BW Bandwidth

[0391] BWP Bandwidth Part

[0392] C-RNTI Cell Radio Network Temporary Identifier

[0393] CA Carrier Aggregation, Certification Authority

[0394] CAPEX Capital Expenditure

[0395] CBRA Contention-based random access

[0396] CC component carrier, country code, encryption checksum

[0397] CCA Clear Channel Assessment

[0398] CCE Control Channel Element

[0399] CCCH Common Control Channel

[0400] CE Coverage Enhancement

[0401] CDM Content Delivery Network

[0402] CDMA Code Division Multiple Access

[0403] CFRA Contention-free random access

[0404] CG Cell Group

[0405] Cl cell identifier

[0406] CID Cell ID (eg, positioning method)

[0407] CIM Common Information Model

[0408] CIR Carrier to Interference Ratio

[0409] CK Cryptographic Key

[0410] CM connection management, conditional enforcement

[0411] CMAS Commercial Mobile Alert Service

[0412] CMD command

[0413] CMS Cloud Management System

[0414] CO conditions optional

[0415] CoMP Coordinated Multi-Point Transmission

[0416] CORESET Control Resource Set

[0417] COTS Commercial Off-the-Shelf

[0418] CP Control Plane, Cyclic Prefix, Attachment Point

[0419] CPD Connection Point Descriptor

[0420] CPE user terminal equipment

[0421] CPICH Common Pilot Channel

[0422] CQI Channel Quality Indicator

[0423] CPU CSI processing unit, central processing unit

[0424] C / R Command / Response field bit

[0425] CRAN Cloud Radio Access Network, Cloud RAN

[0426] CRB Common Resource Block

[0427] CRC Cyclic Redundancy Check

[0428] CRI Channel State Information Resource Indicator, CSI-RS Resource Indicator

[0429] C-RNTI Cell RNTI

[0430] CS Circuit Switched

[0431] CSAR Cloud Service Archive

[0432] CSI Channel State Information

[0433] CSI-IM CSI interference measurement

[0434] CSI-RS CSI reference signal

[0435] CSI-RSRP CSI reference signal received power

[0436] CSI-RSRQ CSI reference signal reception quality

[0437] CSI-SINR CSI signal-to-noise ratio and interference ratio

[0438] CSMA Carrier Sense Multiple Access

[0439] CSMA / CA CSMA Collision Avoidance

[0440] CSS Common Search Space, Cell Specific Search Space

[0441] CTS Clear End

[0442] CW codeword

[0443] CWS Contention Window Size

[0444] D2D Device to Device

[0445] DC dual connection, direct current

[0446] DCI Downlink Control Information

[0447] DF deployment specifications

[0448] DL Downlink

[0449] DMTF Distributed Management Working Group

[0450] DPDK Data Plane Development Kit

[0451] DM-RS, DMRS demodulation reference signal

[0452] DN Data Network

[0453] DRB Data Radio Bearer

[0454] DRS Discovery Reference Signal

[0455] DRX Discontinuous Reception

[0456] DSL Domain Specific Language Digital Subscriber Line

[0457] DSLAM DSL Access Multiplexer

[0458] DwPTS Downlink Pilot Time Slot

[0459] E-LAN ​​Ethernet Local Area Network

[0460] E2E End to End

[0461] ECCA Extended Clear Channel Assessment, Extended CCA

[0462] ECCE Enhanced Control Channel Element, Enhanced CCE

[0463] ED Energy Detection

[0464] EDGE Enhanced Data Rates for GSM Evolution (GSM Evolution)

[0465] EGMF Exposure Management Function

[0466] EGPRS Enhanced GPRS

[0467] EIR Equipment Identity Register

[0468] eLAA Enhanced License Assisted Access, enhanced LAA

[0469] EM Component Manager

[0470] eMBB Enhanced Mobile Broadband

[0471] EMS Component Management System

[0472] eNB Evolved Node B, E-UTRAN Node B

[0473] EN-DC E-UTRA-NR Dual Connectivity

[0474] EPC Evolved Packet Core

[0475] EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel

[0476] EPRE Energy per resource element

[0477] EPS Evolved Packet System

[0478] EREG Enhanced REG, Enhanced Resource Element Group

[0479] ETSI European Telecommunications Standards Institute

[0480] ETWS Earthquake and Tsunami Warning System

[0481] eUICC embedded UICC, embedded universal integrated circuit card

[0482] E-UTRA Evolved UTRA

[0483] E-UTRAN Evolved UTRAN

[0484] F1AP F1 Application Protocol

[0485] F1-C F1 control plane interface

[0486] F1-U F1 User Plane Interface

[0487] FACCH Fast Associated Control Channel

[0488] FACCH / F Fast Associated Control Channel / Full Rate

[0489] FACCH / H Fast Associated Control Channel / Half Rate

[0490] FACH Forward Access Channel

[0491] FAUSCH Fast Uplink Signaling Channel

[0492] FB Function Block

[0493] FBI Feedback

[0494] FCC Federal Communications Commission

[0495] FCCH Frequency Correction Channel

[0496] FDD Frequency Division Duplex

[0497] FDM Frequency Division Multiplexing

[0498] FDMA Frequency Division Multiple Access

[0499] FE Front End

[0500] FEC Forward Error Correction

[0501] FFS For further study

[0502] FFT Fast Fourier Transform

[0503] feLAA Further Enhanced License Assisted Access, Further Enhanced LAA

[0504] FN Frame Number

[0505] FPGA Field Programmable Gate Array

[0506] FR Frequency Range

[0507] G-RNTI GERAN Radio Network Temporary Identity

[0508] GERAN GSM EDGE Radio Access Network

[0509] GGSN Gateway GPRS Support Node

[0510] GLONASS Global Navigation Satellite System

[0511] gNB Next Generation Node B

[0512] gNB-CU gNB centralized unit, next generation Node B centralized unit

[0513] gNB-DU gNB distributed unit, next generation Node B distributed unit

[0514] GNSS Global Navigation Satellite System

[0515] GPRS General Packet Radio Service

[0516] GSM Global System for Mobile Communications, Mobile Association

[0517] GTP GPRS Tunneling Protocol

[0518] GTP-U User Plane GPRS Tunneling Protocol

[0519] GUMMEI Globally Unique MME Identifier

[0520] GUTI Globally Unique Temporary UE Identifier

[0521] HARQ Hybrid Automatic Repeat Request

[0522] HANDO, HO switching

[0523] HFN Hyperframe Number

[0524] HHO Hard Handover

[0525] HLR Home Location Register

[0526] HN Home Network

[0527] HPLMN Home Public Land Mobile Network

[0528] HSDPA High Speed ​​Downlink Packet Access

[0529] HSN Hopping Sequence Number

[0530] HSPA High Speed ​​Packet Access

[0531] HSS Home Subscriber Server

[0532] HSUPA High Speed ​​Uplink Packet Access

[0533] HTTP Hypertext Transfer Protocol

[0534] HTTPS Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL, i.e., port 443)

[0535] I-Block Information Block

[0536] ICCID Integrated Circuit Card Identifier

[0537] ICIC Inter-cell Interference Coordination

[0538] ID

[0539] IDFT Inverse Discrete Fourier Transform

[0540] IE Information Element

[0541] IEEE Institute of Electrical and Electronics Engineers

[0542] IEI Information Element Identifier

[0543] IEIDL Information Element Identifier Data Length

[0544] IETF Internet Engineering Task Force

[0545] IF Infrastructure

[0546] IM Interference Measurement, Intermodulation, IP Multimedia

[0547] IMC IMS credentials

[0548] IMEI International Mobile Equipment Identity

[0549] IMGI International Mobile Group Identifier

[0550] IMPI IP Multimedia Private Identity

[0551] IMPU IP Multimedia Public Identity

[0552] IMS IP Multimedia Subsystem

[0553] IMSI International Mobile Subscriber Identity

[0554] IoT

[0555] IP Internet Protocol

[0556] Ipsec IP security, Internet Protocol security

[0557] IP-CAN IP connection access network

[0558] IP-M IP Multicast

[0559] IPv4 Internet Protocol version 4

[0560] IPv6 Internet Protocol version 6

[0561] IR

[0562] IRP General Reference Point

[0563] ISDN Integrated Services Digital Network

[0564] ISIM IM Service Identity Module

[0565] ISO International Organization for Standardization

[0566] ISP Internet Service Provider

[0567] IWF interworking function

[0568] I-WLAN Intercommunication WLAN

[0569] K convolutional code constraint length, USIM personal key

[0570] kB kilobyte (1000 bytes)

[0571] kbps kilobits per second

[0572] Kc encryption key

[0573] Ki Personal user authentication key

[0574] KPI Key Performance Indicator

[0575] KQI Key Quality Indicator

[0576] KSI Key Set Identifier

[0577] ksps kilosymbols per second

[0578] KVM Kernel Virtual Machine

[0579] L1 Layer 1 (Physical Layer)

[0580] L1-RSRP Layer 1 reference signal received power

[0581] L2 Layer 2 (Data Link Layer)

[0582] L3 Layer 3 (Network Layer)

[0583] LAA License Assisted Access

[0584] LAN Local Area Network

[0585] LAN Listen before you speak

[0586] LCM Lifecycle Management

[0587] LCR Low Chip Rate

[0588] LCS Location Services

[0589] LI layer indicator

[0590] LLC Logical Link Control, Low Layer Compatibility

[0591] LPLMN Local PLMN

[0592] LPP LTE Positioning Protocol

[0593] LSB Least Significant Bit

[0594] LTE Long Term Evolution

[0595] LWA LTE-WLAN Aggregation

[0596] LWIP LTE / WLAN radio class integrated with IPsec tunneling

[0597] LTE Long Term Evolution

[0598] M2M Machine to Machine

[0599] MAC Media Access Control (protocol layer content)

[0600] MAC message authentication code (security / encrypted content)

[0601] MAC-A MAC for authentication and key agreement (TSG T WG3 content)

[0602] MAC-I MAC for signaling message data integrity (TSG T WG3 content)

[0603] MANO Management and Orchestration

[0604] MBMS Multimedia Broadcast and Multicast Service

[0605] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0606] MCC Mobile Country Code

[0607] MCG Master Cell Group

[0608] MOOT Maximum channel occupation time

[0609] MCS Modulation and Coding Scheme

[0610] MDAF Management Data Analysis Function

[0611] MDAS Management Data Analysis Service

[0612] MDT Minimized Drive Test

[0613] ME Mobile Equipment

[0614] MeNB Master eNB

[0615] MER message error rate

[0616] MGL Measurement Gap Length

[0617] MGRP measurement gap repetition period

[0618] MIB Master Information Block, Management Information Base

[0619] MIMO Multiple Input Multiple Output

[0620] MLC Mobile Location Center

[0621] MM Mobility Management

[0622] MME Mobility Management Entity

[0623] MN Master Node

[0624] MO measurement object, mobile station initiated

[0625] MPBCH MTC Physical Broadcast Channel

[0626] MPDCCH MTC Physical Downlink Control Channel

[0627] MPDSCH MTC Physical Downlink Shared Channel

[0628] MPRACH MTC Physical Random Access Channel

[0629] MPUSCH MTC Physical Uplink Shared Channel

[0630] MPLS Multi-Protocol Label Switching

[0631] MS Mobile Station

[0632] MSB Most Significant Bit

[0633] MSC Mobile Switching Center

[0634] MSI minimum system information, MCH scheduling information

[0635] MSID Mobile Station Identifier

[0636] MSIN Mobile Station Identification Number

[0637] MSISDN Mobile Subscriber ISDN Number

[0638] MT Mobile Station Termination, Mobile Terminal

[0639] MTC Machine Type Communication

[0640] mMTC Massive MTC, Massive Machine Type Communication

[0641] MU-MIMO Multi-User MIMO

[0642] MWUS MTC wake-up signal, MTC WUS

[0643] NACK Negative Acknowledgement

[0644] NAI Network Access Identifier

[0645] NAS Non-Access Stratum

[0646] NCT Network Connection Topology

[0647] NEC network capabilities exposed

[0648] NE-DC NR-E-UTRA dual connectivity

[0649] NEF Network Exposure Function

[0650] NF Network Function

[0651] NFP Network Forwarding Path

[0652] NFPD Network Forwarding Path Descriptor

[0653] NFV Network Function Virtualization

[0654] NFVI NFV Infrastructure

[0655] NFVO NFV Rasterizer

[0656] NG Next Generation

[0657] NGEN-DC NG-RAN, E-UTRA-NR dual connectivity

[0658] NM Network Manager

[0659] NMS Network Management System

[0660] N-PoP Network Point of Presence

[0661] NMIB, N-MIB Narrowband MIB

[0662] NPBCH Narrowband Physical Broadcast Channel

[0663] NPDCCH Narrowband Physical Downlink Control Channel

[0664] NPDSCH Narrowband Physical Downlink Shared Channel

[0665] NPRACH Narrowband Physical Random Access Channel

[0666] NPUSCH Narrowband Physical Uplink Shared Channel

[0667] NPSS Narrowband Primary Synchronization Signal

[0668] NSSS Narrowband Secondary Synchronization Signal

[0669] NR New Radio, Adjacent Bus Relationships

[0670] NRF NF Repository Functionality

[0671] NRS Narrowband Reference Signal

[0672] NS Network Services

[0673] NSA Non-standalone operation mode

[0674] NSD Network Service Descriptor

[0675] NSR Network Service Record

[0676] NSSAI Network Slice Selection Assistance Information

[0677] S-NNSAI Single NSSAI

[0678] NSSF network slice selection function

[0679] NW Network

[0680] NWUS Narrowband wake-up signal, narrowband WUS

[0681] NZP Non Zero Power

[0682] O&M Operation and Maintenance

[0683] ODU2 Optical Channel Data Unit - Type 2

[0684] OFDM Orthogonal Frequency Division Multiplexing

[0685] OFDMA Orthogonal Frequency Division Multiple Access

[0686] OOB Out of Band

[0687] OPEX Operating Expenditure

[0688] OSI Other System Information

[0689] OSS Operation Support System

[0690] OTA Wireless

[0691] PAPR Peak to Average Power Ratio

[0692] PAR Peak to Average Ratio

[0693] PBCH Physical Broadcast Channel

[0694] PC Power Control, Personal Computer

[0695] PCC Primary Component Carrier, Primary CC

[0696] Pcell Primary cell

[0697] PCI Physical Cell ID, Physical Cell Identifier

[0698] PCEF Policy and Charging Enforcement Function

[0699] PCF Policy Control Function

[0700] PCRF Policy Control and Charging Rules Function

[0701] PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer

[0702] PDCCH Physical Downlink Control Channel

[0703] PDCP Packet Data Convergence Protocol

[0704] PDN Packet Data Network, Public Data Network

[0705] PDSCH Physical Downlink Shared Channel

[0706] PDU Protocol Data Unit

[0707] PEI Permanent Equipment Identifier

[0708] PFD Packet Flow Description

[0709] P-GW PDN Gateway

[0710] PHICH Physical Hybrid ARQ Indicator Channel

[0711] PHY Physical Layer

[0712] PLMN Public Land Mobile Network

[0713] PIN Personal Identification Number

[0714] PM performance measurement

[0715] PMI Precoding matrix indicator

[0716] PNF Physical Network Function

[0717] PNFD Physical Network Functional Descriptor

[0718] PNFR Physical Network Function Record

[0719] POC Mobile Intercom Service

[0720] PP, PTP point to point

[0721] PPP Point-to-Point Protocol

[0722] PRACH Physical RACH

[0723] PRB Physical Resource Block

[0724] PRG Physical Resource Group

[0725] ProSe proximity services, proximity-based services

[0726] PRS Positioning Reference Signal

[0727] PS Packet Service

[0728] PSBCH Physical Sidelink Broadcast Channel

[0729] PSDCH Physical Sidelink Downlink Channel

[0730] PSCCH Physical Sidelink Control Channel

[0731] PSSCH Physical uplink shared channel

[0732] PSCell Primary SCell

[0733] PSS Primary Synchronization Signal

[0734] PSTN Public Switched Telephone Network

[0735] PT-RS Phase Tracking Reference Signal

[0736] PTT Push to Talk

[0737] PUCCH Physical Uplink Control Channel

[0738] PUSCH Physical Uplink Shared Channel

[0739] QAM Quadrature Amplitude Modulation

[0740] QCI QoS Class Identifier

[0741] QCL Quasi-Co-sited

[0742] QFI QoS flow ID, QoS flow identifier

[0743] QoS Quality of Service

[0744] QPSK Quadrature (Quaternary) Phase Shift Keying

[0745] QZSS Quasi-Zenith Satellite System

[0746] RA-RNTI Random Access RNTI

[0747] RAB Radio Access Bearer, Random Access Burst

[0748] RACH Random Access Channel

[0749] RADIUS Remote Authentication Dial-In User Service

[0750] RAN Radio Access Network

[0751] RAND Random access number (for authentication)

[0752] RAR Random Access Response

[0753] RAT Radio Access Technology

[0754] RAU Routing Area Update

[0755] RB Resource Block, Radio Bearer

[0756] RBG Resource Block Group

[0757] REG Resource Element Group

[0758] Rel version

[0759] REQ Request

[0760] RF

[0761] Rl rank indicator

[0762] RIV Resource Indicator Value

[0763] RL Radio Link

[0764] RLC Radio Link Control, Radio Link Control Layer

[0765] RLF Radio Link Failure

[0766] RLM Radio Link Monitoring

[0767] RLM-RS RLM reference signal

[0768] RM Registration Management

[0769] RMC Reference Measurement Channel

[0770] RMSI Remaining MSI, Remaining Minimum System Information

[0771] RN Relay Node

[0772] RNC Radio Network Controller

[0773] RNL Radio Network Layer

[0774] RNTI Radio Network Temporary Identifier

[0775] ROHC Robust Header Compression

[0776] RRC Radio Resource Control, Radio Resource Control Layer

[0777] RRM Radio Resource Management

[0778] RS reference signal

[0779] RSRP Reference Signal Received Power

[0780] RSRQ Reference Signal Received Quality

[0781] RSSI Received Signal Strength Indicator

[0782] RSU Road Side Unit

[0783] RSTD Reference Signal Time Difference

[0784] RTP Real Time Protocol

[0785] RTS Ready to send

[0786] RTT Round Trip Time

[0787] Rx

[0788] S1AP S1 Application Protocol

[0789] S1-MME control plane S1

[0790] S1-U User plane S1

[0791] S-GW Service Gateway

[0792] S-RNTI SRNC Radio Network Temporary Identifier

[0793] S-TMSI SAE Mobile Station Temporary Identifier

[0794] SA Standalone Operation Mode

[0795] SAE system architecture evolution

[0796] SAP Service Access Point

[0797] SAPD Service Access Point Descriptor

[0798] SAPI Service Access Point Identifier

[0799] SCC Secondary Component Carrier, Secondary CC

[0800] SCell Secondary Cell

[0801] SC-FDMA Single Carrier Frequency Division Multiple Access

[0802] SCG Secondary Cell Group

[0803] SCM Security Context Management

[0804] SCS Subcarrier Spacing

[0805] SCTP Stream Control Transmission Protocol

[0806] SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer

[0807] SDL Supplemental Downlink

[0808] SDNF Structured Data Storage Network Function

[0809] SDP Service Discovery Protocol (Bluetooth related)

[0810] SDSF structured data storage function

[0811] SDU Service Data Unit

[0812] SEAF Security Anchoring Function

[0813] SeNB Secondary eNB

[0814] SEPP Security Edge Protection Proxy

[0815] SFI Slot Format Indicator

[0816] SFTD Space Frequency Time Diversity, SFN and Frame Timing Difference

[0817] SFN System Frame Number

[0818] SgNB

[0819] SGSN Serving GPRS Support Node

[0820] S-GW Service Gateway

[0821] SI System Information

[0822] SI-RNTI System Information RNTI

[0823] SIB System Information Block

[0824] SIM Subscriber Identity Module

[0825] SIP Session Initiation Protocol

[0826] SiP System in Package

[0827] SL Side Link

[0828] SLA Service Level Agreement

[0829] SM Session Management

[0830] SMF session management functions

[0831] SMS Short Message Service

[0832] SMSF SMS Function

[0833] SMTC SSB-based measurement timing configuration

[0834] SN Secondary Node, Serial Number

[0835] SoC System on Chip

[0836] SON Self-Organizing Network

[0837] SpCell Special Cell

[0838] SP-CSI-RNTI Semi-persistent CSI-RNTI

[0839] SPS Semi-Persistent Scheduling

[0840] SON Serial Number

[0841] SR Scheduling Request

[0842] SRB Signalling Radio Bearer

[0843] SRS Sounding Reference Signal

[0844] SS Sync Signal

[0845] SSB Synchronization Signal Block, SS / PBCH Block

[0846] SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator

[0847] SSC Session and Service Continuity

[0848] SS-RSRP Reference signal received power based on synchronization signal

[0849] SS-RSRQ Reference signal reception quality based on synchronization signal

[0850] SS-SINR Signal-to-noise ratio and interference ratio based on synchronization signal

[0851] SSS Secondary synchronization signal

[0852] SST Slice / Service Type

[0853] SU-MIMO Single User MIMO

[0854] SUL Supplementary Uplink

[0855] TA Timing Advance, Tracking Area

[0856] TAC Tracking Area Code

[0857] TAG Timing Advance Group

[0858] TAU Tracking Area Updates

[0859] TB Transfer Block

[0860] TBS Transport Block Size

[0861] TBD To be defined

[0862] TCI Transmission Configuration Indicator

[0863] TCP Transmission Control Protocol

[0864] TDD Time Division Duplex

[0865] TDM Time Division Multiplexing

[0866] TDMA Time Division Multiple Access

[0867] TE Terminal Equipment

[0868] TEID Tunnel End Point Identifier

[0869] TFT Business Flow Template

[0870] TMSI International Mobile Subscriber Identity

[0871] TNL Transport Network Layer

[0872] TPC Transmit Power Control

[0873] TPMI Transmit Precoding Matrix Indicator

[0874] TR Technical Report

[0875] TRP, TRxP Transmission Receive Point

[0876] TRS Tracking Reference Signal

[0877] Trx Transceiver

[0878] TS Technical Specifications, Technical Standards

[0879] TTI Transmit Time Interval

[0880] Tx Transmitter

[0881] U-RNTI UTRAN Radio Network Temporary Identity

[0882] UART Universal Asynchronous Receiver and Transmitter

[0883] UCI Uplink Control Information

[0884] UE User Equipment

[0885] UDM Unified Data Management

[0886] UDP User Datagram Protocol

[0887] UDSF Unstructured Data Storage Network Function

[0888] UICC Universal Integrated Circuit Card

[0889] UL Uplink

[0890] UM Unconfirmed Mode

[0891] UML Unified Modeling Language

[0892] UMTS Universal Mobile Telecommunications System

[0893] UP User Plane

[0894] UPF User Plane Function

[0895] URI Uniform Resource Identifier

[0896] URL Uniform Resource Locator

[0897] URLLC Ultra-Reliable Low Latency Communications

[0898] USB Universal Serial Bus

[0899] USIM Universal Subscriber Identity Module

[0900] USS UE-specific search space

[0901] UTRA UMTS Terrestrial Radio Access

[0902] UTRAN Universal Terrestrial Radio Access Network

[0903] UwPTS Uplink Pilot Time Slot

[0904] V2I Vehicle to Infrastructure

[0905] V2P Vehicle to Pedestrian

[0906] V2V Vehicle to Vehicle

[0907] V2X Vehicle to Everything

[0908] VIM Virtual Infrastructure Manager

[0909] VL Virtual Link

[0910] VLAN Virtual LAN, Virtual Local Area Network

[0911] VM Virtual Machine

[0912] VNF Virtual Network Function

[0913] VNFFG VNF forwarding graph

[0914] VNFFGD VNF Forwarding Graph Descriptor

[0915] VNFM VNF Manager

[0916] VoIP Voice over IP, Voice over Internet Protocol

[0917] VPLMN Visited Public Land Mobile Network

[0918] VPN Virtual Private Network

[0919] VRB Virtual Resource Block

[0920] WiMAX Worldwide Interoperability for Microwave Access

[0921] WLAN Wireless Local Area Network

[0922] WMAN Wireless Metropolitan Area Network

[0923] WPAN Wireless Personal Area Network

[0924] X2-C X2 control plane

[0925] X2-U X2 user plane

[0926] XML Extensible Markup Language

[0927] XRES Expected User Response

[0928] XOR

[0929] ZC area code

[0930] ZP Zero Power

[0931] In this disclosure, “SMTC” refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0932] "SSB" refers to SS / PBCH block; "field" may refer to the individual contents of an information element;

[0933] "Information Element" means a structural element containing single or multiple fields;

[0934] "Primary cell" refers to an MCG cell operating on the primary frequency, in which the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure;

[0935] “primary SCG cell” refers to the SCG cell in which the UE performs random access when performing reconfiguration using the synchronization procedure for DC operation;

[0936] "Secondary cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured with CA;

[0937] “Secondary cell group” means a subset of serving cells including a PSCell and zero or more secondary cells for a UE configured with DC;

[0938] "Serving cell" means a primary cell for a UE in RRC_CONNECTED without CA / DC configured, where there is only one serving cell including the primary cell;

[0939] "Serving cell" refers to the cell group including special cells and all secondary cells for a UE configured with CA / DC and in RRC_CONNECTED; and

[0940] “Special cell” refers to the PCell of an MCG or the PSCell of an SCG for DC operation; otherwise, the term “special cell” refers to the PCell.

[0941] Although the present invention has been shown and described with reference to particular embodiments, it will be understood by those skilled in the art that various changes in form and details may be made herein without departing from the spirit and scope of the present invention as defined by the appended claims. The scope of the present invention is therefore indicated by the appended claims, and all changes that come within the meaning and range of equivalents of the claims are therefore intended to be encompassed.

Claims

1. A baseband processor, comprising: A memory storing instructions that, when executed, cause the baseband processor to: receiving a first configuration for a connected mode discontinuous reception (C-DRX) mode and a second configuration for receiving a wake-up indication in a first downlink control information (DCI) format on a physical downlink control channel (PDCCH), wherein the first DCI format comprises a plurality of UE-specific fields; monitoring the first DCI format during an off / inactive state of the C-DRX mode based at least in part on the second configuration, wherein one or more of the plurality of UE-specific fields of the first DCI format comprises a 1-bit indication, To indicate whether there is a wake-up indication; as well as Based at least in part on receiving the first DCI format with the 1-bit indication indicating the wake-up indication, waking up at a beginning of a next C-DRX On period associated with the first configuration for downlink signaling monitoring.

2. The baseband processor of claim 1 , wherein the instructions are further executable to cause the baseband processor to: Receive the first DCI format on the PDCCH in a common search space, the first DCI format including the 1-bit indication for the UE in a user equipment UE-specific field of the received first DCI, wherein the 1-bit indication indicates a wake-up signal, and wherein the common search space is a search space associated with at least one other UE or allocated to be monitored by the at least one other UE. 3 . The baseband processor of claim 1 , wherein the first configuration is included in radio resource control (RRC) signaling.

4. The baseband processor of claim 1 , wherein the instructions are further executable to cause the baseband processor to: A third configuration for a common search space for monitoring the first DCI on the PDCCH is received, wherein the monitoring is performed according to the third configuration. 5 . The baseband processor of claim 1 , wherein the first DCI format comprises a plurality of user equipment (UE) specific fields, and wherein the first DCI format is a group common DCI message comprising the plurality of UE specific fields. 6 . The baseband processor according to claim 5 , wherein the group common DCI message is appended with a cyclic redundancy check CRC scrambled by a common radio network temporary identifier RNTI.

7. The baseband processor of claim 6, wherein the common RNTI is a Power Saving Radio Network Temporary Identifier (PS-RNTI).

8. The baseband processor of claim 1, wherein the instructions are further executed to cause the baseband processor to: operating in the C-DRX mode using the first configuration; receiving the first DCI in a first bandwidth part BWP, and After receiving the first DCI format including the wake-up indication, waking up in a second BWP, wherein the second BWP is different from the first BWP. 9 . The baseband processor of claim 8 , wherein the first DCI format indicates a switch from the first BWP to the second BWP, and wherein a bandwidth of the second BWP is smaller than a bandwidth of the first BWP. 10 . The baseband processor according to claim 1 , wherein the first value or the second value of the 1-bit indication respectively indicates whether there is a wake-up indication.

11. The baseband processor of claim 1 , wherein the instructions are further executable to cause the baseband processor to: and refraining from starting a drx-onDurationTimer for the downlink signaling monitoring at the beginning of the next C-DRX on period unless the wake-up indication is detected.

12. A non-transitory computer readable medium storing instructions, wherein the instructions, when executed by at least one processor, cause a user equipment UE to: receiving a first configuration for a connected mode discontinuous reception (C-DRX) mode and a second configuration for receiving a wake-up indication in a first downlink control information (DCI) format on a physical downlink control channel (PDCCH), wherein the first DCI format comprises a plurality of UE-specific fields; monitoring the first DCI format during an off / inactive state of the C-DRX mode based at least in part on the second configuration, wherein one or more of the plurality of UE-specific fields of the first DCI format comprises a 1-bit indication, To indicate whether there is a wake-up indication; as well as Based at least in part on receiving the first DCI format with the 1-bit indication indicating the wake-up indication, waking up at a beginning of a next C-DRX On period associated with the first configuration for downlink signaling monitoring.

13. The non-transitory computer-readable medium of claim 12, wherein the instructions, when executed by the at least one processor, further cause the user equipment UE to: Receive the first DCI format on the PDCCH in a common search space, the first DCI format including the 1-bit indication for the UE in a user equipment UE-specific field of the received first DCI, wherein the 1-bit indication indicates a wake-up signal, and wherein the common search space is a search space associated with at least one other UE or allocated to be monitored by the at least one other UE.

14. The non-transitory computer-readable medium of claim 12, wherein the first configuration is included in radio resource control (RRC) signaling.

15. The non-transitory computer-readable medium of claim 12, wherein the instructions, when executed by the at least one processor, further cause the user equipment UE to: A third configuration for a common search space for monitoring the first DCI on the PDCCH is received, wherein the monitoring is performed according to the third configuration.

16. The non-transitory computer-readable medium of claim 12, wherein the first DCI format comprises a plurality of user equipment (UE) specific fields, and wherein the first DCI format is a group common DCI message comprising the plurality of UE specific fields.

17. The non-transitory computer readable medium of claim 16, wherein the group common DCI message is appended with a cyclic redundancy check (CRC) scrambled by a common radio network temporary identifier (RNTI), wherein the common RNTI is a power saving radio network temporary identifier (PS-RNTI).

18. The non-transitory computer-readable medium of claim 12, wherein the instructions, when executed by the at least one processor, further cause the UE to: operating in the C-DRX mode using the first configuration; receiving the first DCI in a first bandwidth part BWP; and After receiving the first DCI format including the wake-up indication, waking up in a second BWP, wherein the second BWP is different from the first BWP. 19 . The non-transitory computer-readable medium of claim 18 , wherein the first DCI format indicates a switch from the first BWP to the second BWP, and wherein a bandwidth of the second BWP is less than a bandwidth of the first BWP.

20. The non-transitory computer-readable medium of claim 13, wherein the instructions, when executed by the at least one processor, further cause the UE to: and refraining from starting a drx-onDurationTimer for the downlink signaling monitoring at the beginning of the next C-DRX on period unless the wake-up indication is detected.

21. An apparatus comprising: a memory storing instructions that, when executed, cause the wireless device to: transmit a first configuration for a connected mode discontinuous reception (C-DRX) mode and a second configuration for a wake-up indication to be transmitted in a first downlink control information (DCI) on a physical downlink control channel (PDCCH), wherein the first DCI format includes a plurality of UE-specific fields, and one or more of the plurality of UE-specific fields of the first DCI format include a 1-bit indication to indicate whether a wake-up indication exists; The first DCI format is transmitted to the UE on the PDCCH during a scheduled OFF / inactive state of the C-DRX mode associated with the first configuration for the UE, wherein the 1-bit indication indicates that the UE wakes up at the beginning of a C-DRX ON period for downlink signal monitoring.

22. The apparatus of claim 21, wherein the instructions are further executable to cause the wireless device to: The first DCI format is transmitted on the PDCCH in a common search space, the first DCI format comprising the 1-bit indication for the UE in a user equipment UE specific field of the received first DCI, wherein the 1-bit indication indicates a wake-up signal.

23. The apparatus of claim 21, wherein the first configuration is included in Radio Resource Control (RRC) signaling.

24. The apparatus of claim 21, wherein the instructions are further executable to cause the wireless device to: A third configuration for a common search space for monitoring the first DCI on the PDCCH is transmitted.

25. The apparatus of claim 21, wherein the first DCI format comprises a plurality of user equipment (UE) specific fields, and wherein the first DCI format is a group common DCI message comprising the plurality of UE specific fields.

26. The apparatus of claim 25, wherein the group common DCI message is appended with a cyclic redundancy check (CRC) scrambled by a common radio network temporary identifier (RNTI), wherein the common RNTI is a power saving radio network temporary identifier (PS-RNTI).

27. The apparatus of claim 21, wherein the instructions are further executable to cause the wireless device to: transmitting the second signaling in a first bandwidth part BWP; and The message is transmitted in the PDCCH or PSCCH in a second BWP, the second BWP being different from the first BWP, wherein the second BWP is greater than the first BWP.

28. A non-transitory computer readable medium storing instructions, wherein the instructions, when executed by one or more processors, cause a wireless device to perform the following operations, comprising: transmitting a first configuration for a connected mode discontinuous reception (C-DRX) mode and a second configuration for a wake-up indication to be transmitted in a first downlink control information (DCI) on a physical downlink control channel (PDCCH), wherein the first DCI format comprises a plurality of UE-specific fields, and one or more of the plurality of UE-specific fields of the first DCI format comprises a 1-bit indication to indicate whether a wake-up indication exists; The first DCI format is transmitted to the UE on the PDCCH during a scheduled OFF / inactive state of the C-DRX mode associated with the first configuration for the UE, wherein the 1-bit indication indicates that the UE wakes up at the beginning of a C-DRX ON period for downlink signal monitoring.

29. The computer-readable medium of claim 28, wherein the instructions, when executed by the one or more processors, further cause the wireless device to: The first DCI format is transmitted on the PDCCH in a common search space, the first DCI format comprising the 1-bit indication for the UE in a user equipment UE specific field of the received first DCI, wherein the 1-bit indication indicates a wake-up signal.

30. The computer-readable medium of claim 28, wherein the first configuration is included in Radio Resource Control (RRC) signaling.

31. The computer-readable medium of claim 28, wherein the instructions, when executed by the one or more processors, further cause the wireless device to: A third configuration for a common search space for monitoring the first DCI on the PDCCH is transmitted.

32. The computer-readable medium of claim 28, wherein the first DCI format comprises a plurality of user equipment (UE) specific fields, and wherein the first DCI format is a group common DCI message comprising the plurality of UE specific fields.

33. The computer-readable medium of claim 28, wherein the instructions, when executed by the one or more processors, further cause the wireless device to: transmitting the second signaling in a first bandwidth part BWP; and The message is transmitted in the PDCCH or PSCCH in a second BWP, the second BWP being different from the first BWP, wherein the second BWP is greater than the first BWP.

34. A method implemented at a user equipment UE, the method comprising: receiving a first configuration for a connected mode discontinuous reception (C-DRX) mode and a second configuration for receiving a wake-up indication in a first downlink control information (DCI) format on a physical downlink control channel (PDCCH), wherein the first DCI format comprises a plurality of UE-specific fields; monitoring the first DCI format during an off / inactive state of the C-DRX mode based at least in part on the second configuration, wherein one or more of the plurality of UE-specific fields of the first DCI format comprises a 1-bit indication, To indicate whether there is a wake-up indication; as well as Based at least in part on receiving the first DCI format with the 1-bit indication indicating the wake-up indication, waking up at a beginning of a next C-DRX On period associated with the first configuration for downlink signaling monitoring.

35. The method of claim 34, further comprising: Receive the first DCI format on the PDCCH in a common search space, the first DCI format including the 1-bit indication for the UE in a user equipment UE-specific field of the received first DCI, wherein the 1-bit indication indicates a wake-up signal, and wherein the common search space is a search space associated with at least one other UE or allocated to be monitored by the at least one other UE.

36. The method of claim 34, wherein the first configuration is included in Radio Resource Control (RRC) signaling.

37. The method of claim 34, further comprising: A third configuration for a common search space for monitoring the first DCI on the PDCCH is received, wherein the monitoring is performed according to the third configuration.

38. The method of claim 34, wherein the first DCI format comprises a plurality of user equipment (UE) specific fields, and wherein the first DCI format is a group common DCI message comprising the plurality of UE specific fields.

39. The method of claim 38, wherein the group common DCI message is appended with a cyclic redundancy check (CRC) scrambled by a common radio network temporary identifier (RNTI).

40. The method of claim 39, wherein the common RNTI is a Power Saving Radio Network Temporary Identifier (PS-RNTI).

41. The method of claim 34, further comprising: operating in the C-DRX mode using the first configuration; receiving said first signalling in a first bandwidth part BWP, and After receiving the first DCI format including the wake-up indication, waking up in a second BWP, wherein the second BWP is different from the first BWP.

42. The method of claim 41, wherein the bandwidth of the second BWP is less than the bandwidth of the first BWP.

43. The method of claim 34, wherein the first value or the second value of the 1-bit indication respectively indicates whether a wake-up indication is present.

44. The method of claim 34, further comprising: and refraining from starting a drx-onDurationTimer for the downlink signaling monitoring at the beginning of the next C-DRX on period unless the wake-up indication is detected.

45. A method implemented at a wireless device, the method comprising: transmitting a first configuration for a connected mode discontinuous reception (C-DRX) mode and a second configuration for a wake-up indication to be transmitted in a first downlink control information (DCI) on a physical downlink control channel (PDCCH), wherein the first DCI format comprises a plurality of UE-specific fields, and one or more of the plurality of UE-specific fields of the first DCI format comprises a 1-bit indication to indicate whether a wake-up indication exists; The first DCI format is transmitted to the UE on the PDCCH during a scheduled OFF / inactive state of the C-DRX mode associated with the first configuration for the UE, wherein the 1-bit indication indicates that the UE wakes up at the beginning of a C-DRX ON period for downlink signal monitoring.

46. ​​The method of claim 45, wherein the wireless device is a base station.

47. The method of claim 45, wherein the first configuration is included in Radio Resource Control (RRC) signaling.

48. The method of claim 45, further comprising: A third configuration for a common search space for monitoring the first DCI on the PDCCH is transmitted.

49. The method of claim 45, wherein the first DCI format comprises a plurality of user equipment (UE) specific fields, and wherein the first DCI format is a group common DCI message comprising the plurality of UE specific fields.

50. The method of claim 49, wherein the group common DCI message is appended with a cyclic redundancy check (CRC) scrambled by a common radio network temporary identifier (RNTI), wherein the common RNTI is a power saving radio network temporary identifier (PS-RNTI).

51. The method of claim 45, further comprising: transmitting the second signaling in a first bandwidth part BWP; and The message is transmitted in the PDCCH or PSCCH in a second BWP, the second BWP being different from the first BWP, wherein the second BWP is greater than the first BWP.

52. A device implemented at a user equipment UE, the device comprising: means for receiving a first configuration for a connected mode discontinuous reception (C-DRX) mode and a second configuration for receiving a wake-up indication in a first downlink control information (DCI) format on a physical downlink control channel (PDCCH), wherein the first DCI format comprises a plurality of UE-specific fields; means for monitoring for the first DCI format during an OFF / inactive state of the C-DRX mode based at least in part on the second configuration, wherein one or more of the plurality of UE-specific fields of the first DCI format comprises a 1-bit indication to indicate whether a wake-up indication is present; as well as Means for waking up at a beginning of a next C-DRX On period associated with the first configuration for downlink signaling monitoring based at least in part on receiving the first DCI format with the 1-bit indication indicating the wake-up indication.

53. An apparatus implemented at a wireless device, the apparatus comprising: means for transmitting a first configuration for a connected mode discontinuous reception (C-DRX) mode and a second configuration for a wake-up indication to be transmitted in a first downlink control information (DCI) on a physical downlink control channel (PDCCH), wherein the first DCI format comprises a plurality of UE-specific fields, one or more of the plurality of UE-specific fields of the first DCI format comprising a 1-bit indication to indicate whether a wake-up indication is present; means for transmitting the first DCI format to the UE on the PDCCH during a scheduled OFF / inactive state of the C-DRX mode associated with the first configuration for the UE, wherein the 1-bit indication indicates that the UE wakes up at the beginning of a C-DRX ON period for downlink signal monitoring.

54. A method comprising: transmitting a first configuration for a connected mode discontinuous reception (C-DRX) mode and a second configuration for a wake-up indication to be transmitted in a first downlink control information (DCI) on a physical downlink control channel (PDCCH), wherein the first DCI format comprises a plurality of UE-specific fields, and one or more of the plurality of UE-specific fields of the first DCI format comprises a 1-bit indication to indicate whether a wake-up indication exists; as well as The first DCI format is transmitted to the UE on the PDCCH during a scheduled OFF / inactive state of the C-DRX mode associated with the first configuration for the UE, wherein the 1-bit indication indicates that the UE wakes up at the beginning of a C-DRX ON period for downlink signal monitoring.

55. The method of claim 54, wherein the first DCI format comprises a plurality of user equipment (UE) specific fields, and wherein the first DCI format is a group common DCI message comprising the plurality of UE specific fields.

56. The method of claim 54, wherein the first value or the second value of the 1-bit indication respectively indicates whether a wake-up indication is present.

57. The method of claim 54, further comprising: The first DCI format is transmitted on the PDCCH in a common search space, the first DCI format comprising the 1-bit indication for the UE in a user equipment UE specific field of the received first DCI, wherein the 1-bit indication indicates a wake-up signal.

58. The method of claim 54, further comprising: A third configuration for a common search space for monitoring the first DCI on the PDCCH is transmitted to the UE.

Images