Closed-loop power control for PUSCH

Abstract

Systems, devices, and techniques for transmit power control (TPC) in a wireless communication system are described. The described techniques performed by a user equipment (UE) include receiving a downlink control information (DCI) message corresponding to a respective physical uplink shared channel (PUSCH) transmission occasion; determining a power control adjustment state for the PUSCH transmission occasion; and transmitting at the PUSCH transmission occasion based on the power control adjustment state. Determining the power control adjustment state may include selectively applying TPC accumulation. Determining the power control adjustment state may include determining whether a first PUSCH transmission occasion occurs out of order relative to a second PUSCH transmission occasion based on the arrival order of the DCI messages, where the first PUSCH transmission occasion occurs before the second PUSCH transmission occasion.

Description

[0001] Cross - Reference to Related Applications

[0002] This disclosure claims the benefit of priority of U.S. Provisional Patent Application No. 62 / 843,156, filed on May 3, 2019, entitled "SYSTEM AND METHODS FOR CLOSEDLOOP POWER CONTROL FOR PUSCH", and U.S. Provisional Patent Application No. 62 / 844,658, filed on May 7, 2019, entitled "CLOSED LOOP POWER CONTROL FOR PUSCH". The entire disclosures of the above patent applications are incorporated herein by reference. Field of the Invention

[0003] This disclosure generally relates to wireless communication systems. Background Art

[0004] Base stations, such as nodes of a radio access network (RAN), may communicate wirelessly with wireless devices, such as user equipment (UE). Downlink (DL) transmissions refer to communications from the base station to the wireless device. Uplink (UL) transmissions refer to communications from the wireless device to another device, such as the base station. The base station may transmit control signaling to control the wireless devices operating within its network. Summary of the Invention

[0005] Systems, apparatuses, and techniques for transmit power control (TPC) in a wireless communication system are described. The described techniques performed by a user equipment (UE) include receiving a downlink control information (DCI) message corresponding to a respective physical uplink shared channel (PUSCH) transmission occasion; determining a power control adjustment state of the PUSCH transmission occasion; and transmitting at the PUSCH transmission occasion according to the power control adjustment state. Determining the power control adjustment state may include selectively applying TPC accumulation. Determining the power control adjustment state may include determining whether a first PUSCH transmission occasion occurs out of order relative to a second PUSCH transmission occasion based on the arrival order of the DCI messages, where the first PUSCH transmission occasion occurs before the second PUSCH transmission occasion. Other embodiments include corresponding systems, apparatuses, and computer programs for performing the acts of the methods defined by instructions encoded on a computer-readable storage device.

[0006] These and other embodiments may include one or more of the following features. An embodiment may include receiving, by a UE, higher layer signaling enabling transmission power control (TPC) accumulation. Determining a power control adjustment state may include determining whether to use a first power control adjustment state corresponding to a first PUSCH transmission occasion when determining a second power control adjustment state corresponding to a second PUSCH transmission occasion, where the first PUSCH transmission occasion occurs out of order relative to the second PUSCH transmission occasion. In some cases, a DCI message for the second PUSCH transmission occasion arrives before a DCI message for the first PUSCH transmission occasion, a DCI message for the second PUSCH transmission occasion arrives before a DCI message for a third PUSCH transmission occasion, a DCI message for the first PUSCH transmission occasion arrives before a DCI message for the third PUSCH transmission occasion, the first PUSCH transmission occasion ends before the second PUSCH transmission occasion and the third PUSCH transmission occasion, and the second PUSCH transmission occasion ends before the third PUSCH transmission occasion. Determining a power control adjustment state may include determining a first power control adjustment state corresponding to the first PUSCH transmission occasion, determining a second power control adjustment state corresponding to the second PUSCH transmission occasion, and determining a third power control adjustment state corresponding to the third PUSCH transmission occasion. In some embodiments, the third power control adjustment state is based on a TPC command in a DCI message for the second PUSCH transmission occasion. In some embodiments, the third power control adjustment state is based on the second power control adjustment state. In some embodiments, the third power control adjustment state is based on an addition of a TPC command value indicated in a DCI for the second PUSCH transmission occasion and a TPC command value indicated in a DCI for the third PUSCH transmission occasion.

[0007] A communication product may include: one or more communication processors, the one or more communication processors including circuitry configured to receive DCI messages corresponding to respective PUSCH transmission occasions and to transmit at the PUSCH transmission occasions according to respective power control adjustment states; and circuitry configured to perform operations including: determining a power control adjustment state for a PUSCH transmission occasion. Determining a power control adjustment state may include determining whether a first PUSCH transmission occasion occurs out of order relative to a second PUSCH transmission occasion based on an arrival order of DCI messages, where the first PUSCH transmission occasion occurs before the second PUSCH transmission occasion. In some embodiments, the UE may include one or more processors, a transceiver, and a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform the operations.

[0008] Details of one or more specific implementations are set forth in the accompanying drawings and the detailed description below. Other features and advantages will be apparent from the detailed description, the drawings, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 An example of a wireless communication system is illustrated.

[0010] Figure 2 An exemplary architecture of a system including a core network is illustrated.

[0011] Figure 3 Another exemplary architecture of a system including a core network is illustrated.

[0012] Figure 4 An example of infrastructure equipment is shown.

[0013] Figure 5 An example of a platform or device is shown.

[0014] Figure 6 Exemplary components of a baseband circuit and a radio front-end circuit are illustrated.

[0015] Figure 7 Exemplary components of a cellular communication circuit are shown.

[0016] Figure 8 An example of protocol functions that can be implemented in a wireless communication system is shown.

[0017] Figure 9 An example of a computer system is illustrated.

[0018] Figure 10 A timeline of an example of out-of-order PUSCH scheduling and transmission is shown.

[0019] Figure 11 A timeline of another example of out-of-order PUSCH scheduling and transmission is shown.

[0020] Figure 12 A flowchart of an example of a power control process is illustrated.

[0021] Figure 13 A flowchart of another example of a power control process is illustrated.

[0022] Like reference numerals in the various figures indicate like elements. DETAILED DESCRIPTION

[0023] Figure 1An example of a wireless communication system 100 is illustrated. For purposes of convenience and not limitation, the exemplary system 100 is described in the context of LTE and 5G NR communication standards defined by 3rd Generation Partnership Project (3GPP) technical specifications. However, other types of communication standards are also possible.

[0024] System 100 includes UEs 101a and 101b (collectively referred to as "UE 101"). In this example, UE 101 is shown as a smart phone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks). In other examples, any of the multiple UEs 101 can include other mobile computing devices or non-mobile computing devices, such as consumer electronic devices, cellular phones, smart phones, feature phones, tablets, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument clusters (IC), head-up display (HUD) devices, on-board diagnostic (OBD) devices, on-vehicle mobile equipment (DME), mobile data terminals (MDT), electronic engine management systems (EEMS), electronic / engine control units (ECU), electronic / engine control modules (ECM), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" home appliances, machine type communication (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, or combinations thereof, etc.

[0025] In some specific implementations, any of the UEs 101 can be an IoT UE, which can include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE can utilize technologies such as M2M or MTC to exchange data with an MTC server or device, for example, using a public land mobile network (PLMN), proximity services (ProSe), device-to-device (D2D) communication, sensor networks, IoT networks, or combinations thereof, etc. The M2M or MTC data exchange can be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which can include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE can execute background applications (e.g., keep-alive messages or status updates) to facilitate the connection to the IoT network.

[0026] UE 101 is configured to connect to (e.g., communicatively couple to) RAN 110. RAN 110 includes one or more RAN nodes 111a and 111b (collectively referred to as "RAN nodes 111"). In some embodiments, RAN 110 may be a Next Generation RAN (NGRAN), an evolved UMTS Terrestrial Radio Access Network (E-UTRAN), or a legacy RAN such as a UMTS Terrestrial Radio Access Network (UTRAN) or a GSM EDGE Radio Access Network (GERAN). As used herein, the term "NG RAN" may refer to RAN 110 operating in a 5G NR system 100, while the term "E-UTRAN" may refer to RAN 110 operating in an LTE or 4G system 100.

[0027] To connect to RAN 110, multiple UEs 101 utilize connections (or channels) 103 and 104 respectively, and each connection (or channel) may include a physical communication interface or layer as described below. In this example, connections 103 and 104 are shown as air interfaces to achieve communicative coupling and may be compliant with cellular communication protocols such as Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Push-to-Talk over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP LTE protocol, 5G NR protocol, or a combination thereof, and other communication protocols.

[0028] RAN 110 may include one or more RAN nodes 111a and 111b (collectively referred to as "RAN nodes 111") that enable connections 103 and 104. As used herein, terms such as "access node", "access point", etc. may describe equipment that provides radio baseband functionality for a data or voice connection or both between a network and one or more users. These access nodes may be referred to as base stations (BS), gNodeB, gNB, eNodeB, eNB, NodeB, RAN nodes, roadside units (RSU), etc., and may include terrestrial stations (e.g., land access points) or satellite stations, etc. that provide coverage within a geographical area (e.g., a cell). As used herein, the term "NGRAN node" may refer to RAN node 111 (e.g., gNB) operating in a 5G NR system 100, while the term "E-UTRAN node" may refer to RAN node 111 (e.g., eNB) operating in an LTE or 4G system 100. In some embodiments, RAN node 111 may be implemented as one or more of dedicated physical devices such as macrocell base stations, or low-power (LP) base stations for providing femtocells, picocells, or other similar cells with a smaller coverage area, smaller user capacity, or higher bandwidth compared to macrocells.

[0029] RAN node 111 and UE 101 may be configured for multi-input and multi-output (MIMO) communication, including single-beam or multi-beam communication. For example, UE 101 may receive transmissions from one RAN node 111 at a time, or receive transmissions from multiple RAN nodes 111 simultaneously. RAN node 111 and UE 101 may use beamforming for UL, DL, or both. For example, one or more RAN nodes 111 may transmit (Tx) beams to UE 101, and UE 101 may receive data simultaneously via one or more receive (Rx) beams. In some specific implementations, each of the RAN nodes 111 may be configured as a transmission and reception point (TRP). RAN 110 may provide higher layer signaling for configuring beamforming, such as by providing transmission configuration indication (TCI) state configuration information.

[0030] Any one of the RAN nodes 111 may serve as an end point of the air interface protocol and may be the first contact point for UE 101. In some specific implementations, any one of the RAN nodes 111 may perform various logical functions of RAN 110, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0031] In some specific implementations, multiple UEs 101 may be configured to communicate with each other or with any one of the RAN nodes 111 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication technologies, such as but not limited to OFDMA communication technology (e.g., for downlink communication) or SC-FDMA communication technology (e.g., for uplink communication), but the scope of the technologies described herein is not limited in this regard. The OFDM signal may include multiple orthogonal sub-carriers.

[0032] In some specific implementations, the downlink resource grid can be used for downlink transmissions from any of the RAN nodes 111 to the UE 101, and similar techniques can be utilized for uplink transmissions. The grid can be a frequency grid or a time-frequency grid, which is the physical resource in the downlink for each time slot. For OFDM systems, such time-frequency plane representations are common practice, which makes radio resource allocation intuitive. Each column and each row of the resource grid correspond to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one time slot in the radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element (RE). Each resource grid can include multiple resource blocks, which describe the mapping of certain physical channels to resource elements. A resource block (RB) can include a set of resource elements; in the frequency domain, this can represent the smallest amount of resources that can be currently allocated. Such resource blocks can be used to transmit physical downlink channels and uplink channels. In some cases, an RB can be referred to as a physical resource block (PRB).

[0033] The RAN node 111 can transmit to the UE 101 through one or more DL channels. Various examples of DL communication channels include the physical broadcast channel (PBCH), the physical downlink control channel (PDCCH), and the physical downlink shared channel (PDSCH). Other types of downlink channels are possible. For example, the PDSCH can carry user data and higher layer signaling to multiple UEs 101. The UE 101 can transmit to the RAN node 111 through one or more UL channels. Various examples of UL communication channels include the physical uplink shared channel (PUSCH), the physical uplink control channel (PUCCH), and the physical random access channel (PRACH). Other types of uplink channels are possible. Devices such as the RAN node 111 and the UE 101 can transmit reference signals. Examples of reference signals include the sounding reference signal (SRS), the channel state information reference signal (CSI-RS), the demodulation reference signal (DMRS or DM-RS), and the phase tracking reference signal (PTRS). Other types of reference signals are possible.

[0034] A channel such as the PDCCH may transmit different types of scheduling information for one or more downlink channels and uplink channels. The scheduling information may include downlink resource scheduling, uplink power control instructions, uplink resource grants, and indications for paging or system information. The RAN node 111 may transmit one or more downlink control information (DCI) messages on the PDCCH to provide scheduling information, such as the allocation of one or more PRBs. In some specific implementations, the DCI message transmits control information, such as a request for an aperiodic CQI report, a UL power control command for a channel, and a notification of the time slot format for a group of UEs 101. Downlink scheduling may be performed at any of the RAN nodes 111 based on channel quality information fed back from any of the UEs 101 (e.g., allocating control and shared channel resource blocks to the UE 101b within the cell). Downlink resource allocation information may be sent on the PDCCH for each UE of a UE 101 or a group of UEs. In some specific implementations, among other information, the PDCCH carries information about the transmission format and resource allocation related to the PDSCH channel. The PDCCH may also notify the UE 101 about the transmission format, resource allocation, and hybrid automatic repeat request (HARQ) information for providing HARQ feedback on the uplink channel based on the PDSCH reception.

[0035] In some specific implementations, the PDCCH uses control channel elements (CCEs) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruples and then arranged using a sub-block interleaver for rate matching. In some specific implementations, one or more of these CCEs may be used to transmit each PDCCH, where each CCE may correspond to a set of nine of four physical resource elements, collectively referred to as a resource element group (REG). Four quadrature phase shift keying (QPSK) symbols may be mapped to each REG. Depending on the size of the DCI and the channel conditions, one or more CCEs may be used to transmit the PDCCH. In some specific implementations, there may be four or more different PDCCH formats defined with different numbers of CCEs (e.g., aggregation level, L = 1, 2, 4, or 8).

[0036] Downlink and uplink transmissions can occur in one or more component carriers (CCs). One or more bandwidth part (BWP) configurations can be configured for each component carrier. In some specific implementations, the DL BWP includes at least one control resource set (CORESET). In some specific implementations, the CORESET includes one or more physical resource blocks (PRBs) in the frequency domain and one or more OFDM symbols in the time domain. In some specific implementations, a channel such as the PDCCH can be transmitted via one or more CORESETs, where each CORESET corresponds to a set of time-frequency resources. CORESET information can be provided to the UE 101, and the UE 101 can monitor the time-frequency resources associated with one or more CORESETs to receive PDCCH transmissions.

[0037] RAN nodes 111 are configured to communicate with each other using interface 112. In an example, such as if system 100 is an LTE system (e.g., when the core network 120 is Figure 2 the evolved packet core (EPC) network as shown), interface 112 can be the X2 interface 112. The X2 interface can be defined between two or more RAN nodes 111 (e.g., two or more eNBs, etc.) connected to the EPC 120, or between two eNBs connected to the EPC 120, or both. In some specific implementations, the X2 interface can include the X2 user plane interface (X2-U) and the X2 control plane interface (X2-C). The X2-U can provide a flow control mechanism for user packets transmitted through the X2 interface and can be used to convey information about the delivery of user data between eNBs. For example, the X2-U can provide specific sequence number information about user data transmitted from the primary eNB to the secondary eNB; information about the successful in-sequence delivery of PDCP protocol data units (PDUs) from the secondary eNB to the UE 101 for user data; information about PDCP PDUs not delivered to the UE 101; information about the current minimum desired buffer size at the secondary eNB for transmitting user data to the UE; and so on. The X2-C can provide intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, or user plane transmission control; load management functions; inter-cell interference coordination functions; and so on.

[0038] In some specific implementations, such as if system 100 is a 5G NR system (e.g., when the core network 120 is Figure 3When referring to the 5G core network shown in the figure, interface 112 can be the Xn interface 112. The Xn interface can be defined between two or more RAN nodes 111 (such as two or more gNBs, etc.) connected to the 5G core network 120, between a RAN node 111 (such as a gNB) connected to the 5G core network 120 and an eNB, or between two eNBs connected to the 5G core network 120, or a combination of the above. In some specific embodiments, the Xn interface can include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U can provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and traffic control functions. The Xn-C can provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UEs 101 in the connected mode (such as CM-CONNECTED), including functions for managing UE mobility in the connected mode between one or more RAN nodes 111; and so on. Mobility support can include context transfer from an old (source) serving RAN node 111 to a new (target) serving RAN node 111, and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (target) serving RAN node 111. The protocol stack of the Xn-U can include a transport network layer built on the Internet Protocol (IP) transport layer, and a General Packet Radio Service Tunneling Protocol (GTP-U) layer of the user plane for carrying user plane PDUs on top of the User Datagram Protocol (UDP) or the IP layer or both. The Xn-C protocol stack can include an application layer signaling protocol (referred to as the Xn application protocol (Xn-AP or XnAP)) and a transport network layer built on the Stream Control Transmission Protocol (SCTP). The SCTP can be on top of the IP layer and can provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other specific embodiments, the Xn-U protocol stack or the Xn-C protocol stack or both can be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0039] RAN 110 is shown as communicatively coupled to a core network 120 (referred to as "CN 120"). CN 120 includes one or more network elements 122 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 101) connected to CN 120 using RAN 110. The components of CN 120 may be implemented in one physical node or separate physical nodes and may include components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some specific implementations, network function virtualization (NFV) may be used to virtualize some or all of the network node functions described herein using executable instructions stored in one or more computer-readable storage media, as will be described in further detail below. A logical instance of CN 120 may be referred to as a network slice, and a logical instance of a part of CN 120 may be referred to as a network sub-slice. The NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources that include a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, an NFV system may be used to perform virtual or reconfigurable implementations of one or more network components or functions, or both.

[0040] The application server 130 may be an element that provides applications that use IP bearer resources in conjunction with the core network (e.g., UMTS packet service (PS) domain, LTE PS data service, etc.). The application server 130 may also be configured to support one or more communication services for UE 101 using CN 120 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.). The application server 130 may communicate with one or more network elements 122 using an IP communication interface 125.

[0041] In some specific implementations, CN 120 may be a 5G core network (referred to as "5GC 120" or "5G core network 120"), and RAN 110 may be connected to CN 120 using a next-generation interface 113. In some specific implementations, the next-generation interface 113 may be divided into two parts: a next-generation user plane (NG-U) interface 114 that carries traffic data between RAN nodes 111 and the UPF (user plane function); and an S1 control plane (NG-C) interface 115 that is a signaling interface between RAN nodes 111 and the access and mobility management function (AMF). Refer to Figure 3 An example where CN 120 is a 5G core network is discussed in more detail.

[0042] In some specific implementations, CN 120 can be an EPC (referred to as "EPC 120" etc.), and RAN 110 can be connected to CN 120 using the S1 interface 113. In some specific implementations, the S1 interface 113 can be divided into two parts: the S1 user plane (S1-U) interface 114, which carries traffic data between the RAN node 111 and the serving gateway (S-GW); and the S1-MME interface 115, which is a signaling interface between the RAN node 111 and the mobility management entity (MME).

[0043] In some specific implementations, some or all of the RAN nodes 111 can be implemented as one or more software entities running on a server computer, as part of a virtual network that can be referred to as cloud RAN (CRAN) and / or virtual baseband unit pool (vBBUP). CRAN or vBBUP can implement RAN function partitioning, such as packet data convergence protocol (PDCP) partitioning, where the radio resource control (RRC) and PDCP layers are operated by CRAN / vBBUP, and other layer 2 (e.g., data link layer) protocol entities are operated by the respective RAN nodes 111; medium access control (MAC) / physical layer (PHY) partitioning, where the RRC, PDCP, MAC, and radio link control (RLC) layers are operated by CRAN / vBBUP, and the PHY layer is operated by the respective RAN nodes 111; or "lower PHY" partitioning, where the RRC, PDCP, RLC, and MAC layers and the upper part of the PHY layer are operated by CRAN / vBBUP, and the lower part of the PHY layer is operated by the respective RAN nodes 111. This virtualization framework allows the idle processor cores of the RAN nodes 111 to execute, for example, other virtualization applications. In some specific implementations, a separate RAN node 111 can represent each gNB distributed unit (DU) connected to the gNB central unit (CU) using the respective F1 interface ( Figure 1 (not shown). In some specific implementations, the gNB-DU can include one or more remote radio heads or RFEMs (see, for example, Figure 4 ), and the gNB-CU can be operated by a server (not shown) located in the RAN 110 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 111 can be a next-generation eNB (ng-eNB), including a RAN node that provides E-UTRA user plane and control plane protocol terminations to the UE101 and is connected to the 5G core network (e.g., core network 120) using a next-generation interface.

[0044] In a vehicle-to-everything (V2X) scenario, one or more RAN nodes in RAN node 111 can be or act as an RSU. The term "roadside unit" or "RSU" refers to any traffic infrastructure entity for V2X communication. The RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where the RSU implemented in or by the UE can be referred to as a "UE-type RSU", the RSU implemented in or by the eNB can be referred to as an "eNB-type RSU", the RSU implemented in or by the gNB can be referred to as a "gNB-type RSU", and so on. In some specific implementations, the RSU is a computing device coupled to a radio frequency circuit located on the roadside, and the computing device provides connectivity support to passing vehicle UEs 101 (vUE 101). The RSU may also include an internal data storage circuit for storing intersection map geometries, traffic statistics, media, and applications or other software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU can operate on the 5.9 GHz direct short-range communication (DSRC) band to provide extremely low-latency communication required for high-speed events, such as collision avoidance, traffic warnings, etc. In addition or alternatively, the RSU can operate on the cellular V2X band to provide the aforementioned low-latency communication and other cellular communication services. In addition or alternatively, the RSU can operate as a Wi-Fi hotspot (2.4 GHz band) or provide connectivity to one or more cellular networks to provide uplink and downlink communication, or both. Some or all of the computing device and the radio frequency circuit of the RSU can be encapsulated in a weather-resistant package suitable for outdoor installation and can include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network, or both.

[0045] Figure 2 An exemplary architecture of system 200 including a first CN 220 is shown. In this example, system 200 can implement the LTE standard such that CN 220 is the EPC220 corresponding to Figure 1 CN 120. Additionally, UE 201 can be the same as or similar to Figure 1 UE 101, and E-UTRAN 210 can be a RAN that is the same as or similar to Figure 1 RAN 110 and can include the RAN nodes 111 discussed previously. CN 220 can include MEE 221, S-GW 222, packet data network gateway (P-GW) 223, home subscriber server (HSS) function 224, and serving GPRS support node (GENEVA) 225.

[0046] The MME 221 may be functionally similar to the control plane of a traditional SGSN and may implement mobility management (MM) functions to keep track of the current location of the UE 201. The MME 221 may execute various mobility management processes to manage aspects of mobility in access, such as gateway selection and tracking area list management. Mobility management (also referred to as "EPSMM" or "EMM" in the E-UTRAN system) may refer to all applicable procedures, methods, data storage, etc. for maintaining knowledge of the current location of the UE 201, providing user identity confidentiality to the user / subscriber, performing other similar services, or a combination thereof, etc. Each UE 201 and MME 221 may include an EMM sublayer, and when the attachment process is successfully completed, a mobility management context may be established in the UE 201 and MME 221. The mobility management context may be a data structure or database object that stores mobility management related information of the UE 201. The MME 221 may be coupled to the HSS 224 using the S6a reference point, to the SGSN 225 using the S3 reference point, and to the S-GW 222 using the S11 reference point.

[0047] The SGSN 225 may be a node that serves the UE 201 by tracking the location of the individual UE 201 and performing security functions. In addition, the SGSN 225 may execute inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by the MME 221; handling of the UE 201 time zone function as specified by the MME 221; and MME selection for handover to the E-UTRAN 3GPP access network, etc. The S3 reference point between the MME 221 and the SGSN 225 may enable the exchange of user and bearer information for 3GPP indirect access network mobility in the idle state or the active state or both.

[0048] The HSS 224 may include a database for network users that includes subscription related information to support network entity processing of communication sessions. The EPC 220 may include one or more HSS 224, depending on the number of mobile users, the capacity of the equipment, the organization of the network, or a combination thereof, etc. For example, the HSS 224 may provide support for routing, roaming, authentication, authorization, name / address resolution, location dependency, etc. The S6a reference point between the HSS 224 and the MME 221 may enable the transmission of subscription and authentication data between the HSS 224 and the MME 221 for authenticating or authorizing user access to the EPC 220.

[0049] The S-GW 222 may terminate the S1 interface 113 towards the RAN 210 ( Figure 2("S1-U" in it), and can route data packets between the RAN 210 and the EPC 220. Additionally, the S-GW 222 can be a local mobility anchor for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other responsibilities can include lawful interception, charging, and enforcement of certain policies. The S11 reference point between the S-GW 222 and the MME 221 can provide a control plane between the MME 221 and the S-GW 222. The S-GW 222 can be coupled to the P-GW 223 using the S5 reference point.

[0050] The P-GW 223 can terminate the SGi interface towards the PDN 230. The P-GW 223 can route data packets between the EPC 220 and an external network such as a network including an application server 130 (sometimes referred to as "AF") using the IP communication interface 125 (see, for example, Figure 1 ). In some specific implementations, the P-GW 223 can be communicatively coupled to the application server (e.g., Figure 1 the application server 130 of Figure 2 or the PDN 230 in

[0051] using the IP communication interface 125 (see, for example, FIG. 1). The S5 reference point between the P-GW 223 and the S-GW 222 can provide user plane tunneling and tunnel management between the P-GW 223 and the S-GW 222. Due to the mobility of the UE 201 and whether the S-GW 222 needs to connect to a non-collocated P-GW 223 for the required PDN connectivity, the S5 reference point can also be used for S-GW 222 relocation. The P-GW 223 can also include a node for policy enforcement and charging data collection (e.g., PCEF (not shown)). Additionally, the SGi reference point between the P-GW 223 and the packet data network (PDN) 230 can be an operator-external public, private PDN, or an internal operator packet data network, for example, for providing IMS services. The P-GW 223 can be coupled to the policy control and charging rules function (PCRF) 226 using the Gx reference point.PCRF 226 is the policy and charging control element of the EPC 220. In a non-roaming scenario, there may be a single PCRF 226 in the home public land mobile network (HPLMN) associated with the Internet protocol connectivity access network (IP-CAN) session of the UE 201. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of the UE 201: the home PCRF (H-PCRF) in the HPLMN and the visited PCRF (V-PCRF) in the visited public land mobile network (VPLMN). The PCRF 226 can be communicatively coupled to the application server 230 by using the P-GW 223. The application server 230 can signal the PCRF 226 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. The PCRF 226 can configure the rule for a PCEF (not shown) with an appropriate traffic flow template (TFT) and QoS class identifier (QCI), which starts the QoS and charging specified by the application server 230. The Gx reference point between the PCRF 226 and the P-GW 223 can allow the transmission of the QoS policy and charging rules from the PCRF 226 to the PCEF in the P-GW 223. The Rx reference point can reside between the PDN 230 (or "AF 230") and the PCRF 226.

[0052] Figure 3 The architecture of a system 300 including a second CN 320 is shown. The system 300 is shown to include a UE 301, which may be the same as or similar to the previously discussed UE 101 and UE 201; a RAN 310, which may be the same as or similar to the previously discussed RAN 110 and RAN 210 and which may include the previously discussed RAN node 111; and a data network (DN) 303, which may be, for example, a carrier service, Internet access, or a 3rd party service; and a 5GC 320. The 5GC 320 may include an authentication server function (AUSF) 322; an access and mobility management function (AMF) 321; a session management function (SMF) 324; a network exposure function (NEF) 323; a policy control function (PCF) 326; a network repository function (NRF) 325; a unified data management (UDM) function 327; an AF 328; a user plane function (UPF) 302; and a network slice selection function (NSSF) 329.

[0053] The UPF 302 can act as an anchor point for mobility within and between RATs, an external PDU session point interconnected with the DN 303, and a branching point for supporting multi-homed PDU sessions. The UPF 302 can also perform packet routing and forwarding, perform packet inspection, execute the user plane part of policy rules, legally intercept packets (UP collection), execute traffic usage reporting, perform QoS handling on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), execute uplink traffic verification (e.g., SDF to QoS flow mapping), perform transport-level packet marking in the uplink and downlink, and execute downlink packet buffering and downlink data notification triggering. The UPF 302 can include an uplink classifier to support routing traffic flows to data networks. The DN 303 can represent various network operator services, Internet access, or third-party services. The DN 303 can include or be similar to the application server 130 discussed previously. The UPF 302 can interact with the SMF 324 using the N4 reference point between the SMF 324 and the UPF 302.

[0054] The AUSF 322 stores data for the authentication of the UE 301 and processes authentication-related functions. The AUSF 322 can facilitate a common authentication framework for various access types. The AUSF 322 can communicate with the AMF 321 using the N12 reference point between the AMF 321 and the AUSF 322, and can communicate with the UDM 327 using the N13 reference point between the UDM 327 and the AUSF 322. Additionally, the AUSF 322 can expose an Nausf service-based interface.

[0055] The AMF 321 is responsible for registration management (e.g., responsible for registering the UE 301, etc.), connection management, reachability management, mobility management, and legal interception of AMF-related events, as well as access authentication and authorization. The AMF 321 can be the termination point of the N11 reference point between the AMF 321 and the SMF 324. The AMF 321 can provide the transmission of SM messages between the UE 301 and the SMF 324, and act as a transparent proxy for routing SM messages. The AMF 321 can also provide the transmission of SM messages between the UE 301 and the SMSF ( Figure 3The transmission of SMS messages between (not shown in the figure). The AMF 321 can act as a Security Anchor Function (SEAF), which can include interactions with the AUSF 322 and the UE 301 to receive, for example, the intermediate key established due to the UE 301 authentication process. In the case of using Universal Mobile Telecommunications System (UMTS)-based authentication, the AMF 321 can retrieve security material from the AUSF 322. The AMF 321 can also include a Security Context Management (SCM) function that receives keys from the SEAF to derive access network-specific keys. In addition, the AMF 321 can be a termination point of the RAN control plane interface, which can include or be the N2 reference point between the RAN 310 and the AMF 321. In some specific implementations, the AMF 321 can be a termination point of NAS (N1) signaling and perform NAS encryption and integrity protection.

[0056] The AMF 321 can also support NAS signaling with the UE 301 through the N3 Interworking Function (IWF) interface (referred to as "N3IWF"). The N3IWF can be used to provide access to untrusted entities. The N3IWF can be a termination point of the N2 interface between the RAN 310 of the control plane and the AMF 321, and can be a termination point of the N3 reference point between the RAN 310 of the user plane and the UPF 302. Therefore, the AMF 321 can handle N2 signaling for PDU sessions and QoS from the SMF 324 and the AMF 321, encapsulate / de-encapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets on the uplink, and perform QoS corresponding to the N3 packet marking, taking into account the QoS requirements associated with such markings received through the N2. The N3IWF can also relay uplink and downlink control plane NAS signaling between the UE 301 and the AMF 321 using the N1 reference point between the UE 301 and the AMF 321, and relay uplink and downlink user plane packets between the UE 301 and the UPF 302. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 301. The AMF 321 can present a Namf service-based interface and can be a termination point of the N14 reference point between two AMF321s and the N17 reference point between the AMF 321 and the 5G Equipment Identity Register (EIR) ( Figure 3 not shown).

[0057] UE 301 can register with the AMF 321 to receive network services. Registration Management (RM) is used to register the UE 301 with the network (e.g., AMF 321) or deregister the UE 301, and establish a UE context in the network (e.g., AMF 321). The UE 301 can operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM DEREGISTERED state, the UE 301 is not registered with the network, and the UE context in the AMF 321 does not maintain the valid location or routing information of the UE 301, so the AMF 321 cannot reach the UE 301. In the RM REGISTERED state, the UE 301 is registered with the network, and the UE context in the AMF 321 can maintain the valid location or routing information of the UE 301, so the AMF 321 can reach the UE 301. In the RM-REGISTERED state, the UE 301 can perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiration of the periodic update timer (e.g., to notify the network that the UE 301 is still active), and perform a registration update procedure to update the UE capability information or renegotiate protocol parameters with the network, etc.

[0058] The AMF 321 can store one or more RM contexts for the UE 301, where each RM context is associated with a specific access to the network. The RM context can be, for example, a data structure or a database object, etc., which indicates or stores the registration status and the periodic update timer for each access type. The AMF 321 can also store a 5GC Mobility Management (MM) context that can be the same as or similar to the previously discussed (E)MM context. In some specific implementations, the AMF 321 can store the coverage enhancement mode B restriction parameters of the UE 301 in the associated MM context or RM context. The AMF 321 can also derive values from the usage setting parameters of the UE that have been stored in the UE context (and / or MM / RM context) when needed.

[0059] Connection Management (CM) can be used to establish and release a signaling connection between the UE 301 and the AMF 321 via the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 301 and the CN 320, and includes the signaling connection between the UE and the AN (e.g., the RRC connection for non-3GPP access or the UE-N3IWF connection) and the N2 connection of the UE 301 between the AN (e.g., the RAN 310) and the AMF 321. In some specific implementations, the UE 301 can operate under one of two CM modes (CM-IDLE mode or CM-CONNECTED mode). When the UE 301 operates in the CM-IDLE mode, the UE 301 may not have a NAS signaling connection established with the AMF 321 via the N1 interface, and there may be a RAN 310 signaling connection for the UE 301 (e.g., N2 or N3 connection or both). When the UE 301 operates in the CM-CONNECTED mode, the UE 301 may have a NAS signaling connection established with the AMF 321 via the N1 interface, and there may be a RAN 310 signaling connection for the UE 301 (e.g., N2 and / or N3 connection). Establishing an N2 connection between the RAN 310 and the AMF 321 may cause the UE 301 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the RAN 310 and the AMF 321 is released, the UE 301 may transition from the CM-CONNECTED mode to the CM-IDLE mode.

[0060] The SMF 324 may be responsible for session management (SM), such as session establishment, modification, and release, including tunnel maintenance between the UPF and the AN node; UE IP address allocation and management (including optional authorization); selection and control of the UPF function; configuration of traffic steering at the UPF to route traffic to the correct destination; termination of the interface towards the policy control function; the control part of policy enforcement and QoS; lawful interception (for SM events and the interface with the LI system); termination of the SM part of the NAS message; downlink data notification; initiation of sending AN-specific SM information to the AN via N2 using the AMF; and determination of the SSC mode of the session. SM may refer to the management of the PDU session, and the PDU session (or "session") may refer to the PDU connectivity service that provides or enables the PDU exchange between the UE 301 and the data network (DN) 303 identified by the data network name (DNN). The PDU session can be established upon request by the UE 301 using NAS SM signaling exchanged between the UE 301 and the SMF 324 via the N1 reference point, modified upon request by the UE 301 and the 5GC 320, and released upon request by the UE 301 and the 5GC 320. When requested from the application server, the 5GC 320 may trigger a specific application in the UE 301. In response to receiving the trigger message, the UE 301 may deliver the trigger message (or the relevant part / information of the trigger message) to one or more identified applications in the UE 301. The identified applications in the UE 301 may establish a PDU session to a specific DNN. The SMF 324 may check whether the UE 301 request complies with the user subscription information associated with the UE 301. In this regard, the SMF 324 may retrieve and / or request to receive an update notification on the subscription data at the SMF 324 level from the UDM 327.

[0061] The SMF 324 may include some or all of the following roaming functions: handling local execution to apply the QoS service level agreement (SLA) (e.g., in the VPLMN); charging data collection and charging interface (e.g., in the VPLMN); lawful interception (e.g., SM events and the interface with the LI system in the VPLMN); and support for interaction with the external DN to transport signaling for PDU session authorization / authentication via the external DN. The N16 reference point between two SMF 324s may be included in the system 300, which may be between another SMF 324 in the visited network and the SMF 324 in the home network in a roaming scenario. Additionally, the SMF 324 may present an Nsmf service-based interface.

[0062] The NEF 323 can provide components for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, application functions (e.g., AF 328), edge computing or fog computing systems, etc. In some specific implementations, the NEF 323 can authenticate, authorize, and / or throttle the AF. The NEF 323 can also transform the information exchanged with the AF 328 and the information exchanged with internal network functions. For example, the NEF 323 can transform between AF service identifiers and internal 5GC information. The NEF 323 can also receive information from other network functions (NFs) based on the exposure capabilities of the other NFs. This information can be stored at the NEF 323 as structured data, or stored at a data storage NF using a standardized interface. Then, the stored information can be re-exposed by the NEF 323 to other NFs and AFs, or used for other purposes such as analysis, or both. Additionally, the NEF323 can present an interface based on the Nnef service.

[0063] The NRF 325 can support service discovery functions, receive NF discovery requests from NF instances, and provide information about the discovered NF instances to the NF instances. The NRF 325 also maintains information about available NF instances and the services supported by these instances. As used herein, terms such as "instantiation" etc. can refer to the creation of an instance, and an "instance" can refer to a specific occurrence of an object, which can occur, for example, during the execution of program code. Additionally, the NRF 325 can present an interface based on the Nnrf service.

[0064] The PCF 326 can provide control plane functions for executing their policy rules, and can also support a unified policy framework for managing network behavior. The PCF 326 can also implement a front end to access subscription information related to policy decisions in the unified data repository (UDR) of the UDM 327. The PCF326 can communicate with the AMF 321 using the N15 reference point between the PCF 326 and the AMF 321, which can include the PCF 326 in the visited network and the AMF 321 in a roaming scenario. The PCF 326 can communicate with the AF 328 using the N5 reference point between the PCF 326 and the AF 328; and communicate with the SMF 324 using the N7 reference point between the PCF326 and the SMF 324. The system 300 or the CN 320 or both can also include an N24 reference point between the PCF 326 (in the home network) and the PCF 326 (in the visited network). Additionally, the PCF 326 can present an interface based on the Npcf service.

[0065] The UDM 327 can process subscription-related information to support the handling of communication sessions by network entities and can store the subscription data of the UE 301. For example, the subscription data can be transmitted between the UDM 327 and the AMF 321 using the N8 reference point between the UDM 327 and the AMF. The UDM 327 can include two parts: an application front end and a UDR ( Figure 3 The front end and the UDR are not shown). The UDR can store the subscription data and policy data of the UDM 327 and the PCF 326, or the structured data for exposure and application data (including PFDs for application detection, application request information of multiple UEs 301) of the NEF 323, or both. The Nudr service-based interface can be presented by the UDR 221 to allow the UDM 327, the PCF 326, and the NEF 323 to access a specific set of the stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM can include a UDM front end, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different front ends can serve the same user. The UDM front end accesses the subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. The UDR can interact with the SMF 324 using the N10 reference point between the UDM 327 and the SMF 324. The UDM 327 can also support SMS management, where the SMS front end implements similar application logic as previously discussed. Additionally, the UDM 327 can present a Nudm service-based interface.

[0066] The AF 328 can provide the impact of the application on traffic routing, provide access to network capability exposure (NCE), and interact with the policy framework for policy control. The NCE can be a mechanism that allows the 5GC 320 and the AF 328 to provide information to each other using the NEF 323, which can be used for edge computing implementations. In such implementations, network operators and third-party services can be hosted near the access point of the attached UE 301 to achieve efficient service delivery with reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can select a UPF 302 near the UE 301 and perform traffic steering from the UPF 302 to the DN 303 using the N6 interface. This can be based on the UE subscription data, the UE location, and the information provided by the AF 328. In this way, the AF 328 can affect the UPF (re)selection and traffic routing. Based on the operator deployment, when the AF 328 is considered a trusted entity, the network operator can allow the AF 328 to directly interact with the relevant NFs. Additionally, the AF 328 can present a Naf service-based interface.

[0067] The NSSF 329 selects a set of network slice instances that can serve the UE 301. If needed, the NSSF 329 can also determine the allowed NSSAI and the mapping to the subscribed single network slice selection assistance information (S-NSSAI). The NSSF 329 can also determine, based on appropriate configuration and possibly by querying the NRF 325, a set of AMFs or a list of candidate AMFs 321 for serving the UE 301. The selection of a set of network slice instances for the UE 301 can be triggered by the AMF 321, where the UE 301 registers by interacting with the NSSF 329, which can cause the AMF 321 to change. The NSSF 329 can interact with the AMF 321 using the N22 reference point between the AMF 321 and the NSSF 329; and can communicate with another NSSF 329 in the visited network using the N31 reference point ( Figure 3 not shown). Additionally, the NSSF 329 can expose an interface based on the Nnssf service.

[0068] As previously discussed, the CN 320 can include an SMSF, which can be responsible for SMS subscription checking and verification and relaying SM messages to or from the UE 301 to or from other entities such as SMS-GMSC / IWMSC / SMS routers. The SMS can also interact with the AMF 321 and the UDM 327 for a notification procedure that the UE 301 can use for SMS transmission (e.g., setting the UE unreachable flag and notifying the UDM 327 when the UE 301 is available for SMS).

[0069] In some specific implementations, there can be additional or alternative reference points or service-based interfaces, or both, between network function services in the network functions. However, for clarity, Figure 3 these interfaces and reference points are omitted. In one example, the CN 320 can include an Nx interface, which is an inter-CN interface between the MME (e.g., MME 221) and the AMF 321 to enable interworking between the CN 320 and the CN 220. Other exemplary interfaces or reference points can include an interface based on the N5g-EIR service exposed by the 5G-EIR, the N27 reference point between the NRF in the visited network and the NRF in the home network, or the N31 reference point between the NSSF in the visited network and the NSSF in the home network, etc.

[0070] In some specific implementations, the components of CN 220 may be implemented in one physical node or separate physical nodes and may include components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some specific implementations, the components of CN 320 may be implemented in the same or similar manner as those discussed herein with respect to the components of CN 220. In some specific implementations, NFV is used to virtualize any one or all of the above network node functions using executable instructions stored in one or more computer-readable storage media, as further described in detail below. The logical instantiation of CN 220 may be referred to as a network slice, and each logical instantiation of CN 220 may provide specific network capabilities and network characteristics. A logical instantiation of a part of CN 220 may be referred to as a network sub-slice, which may include P-GW 223 and PCRF 226.

[0071] As used herein, terms such as "instantiation" may refer to the creation of an instance, and an "instance" may refer to a specific 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 the case of different IP domains or 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.

[0072] Regarding 5G systems (see, for example Figure 3 ), a network slice may include a RAN part and a CN part. Support for network slices relies on the principle that traffic for different slices is handled by different PDU sessions. The network may implement different network slices by scheduling or by providing different L1 / L2 configurations or both. If provided by the NAS, UE 301 provides auxiliary information for network slice selection in an appropriate RRC message. Although the network may support a large number of slices, in some specific implementations the UE does not need to support more than 8 slices simultaneously.

[0073] A network slice may include a CN 320 control plane and user plane NFs, an NG-RAN 310 in the serving PLMN, and an N3IWF function in the serving PLMN. Each network slice may have a different S-NSSAI or a different SST, or both. The NSSAI includes one or more S-NSSAIs, and each network slice is uniquely identified by an S-NSSAI. The network slices may differ in terms of supported features and network function optimizations. In some specific implementations, multiple network slice instances may deliver the same service or feature, but for different groups of UEs 301 (e.g., enterprise users). For example, each network slice may deliver different promised services or may be dedicated to a specific customer or enterprise, or both. In this example, each network slice may have a different S-NSSAI with the same SST but with different slice differentiators. Additionally, a single UE may be served simultaneously by one or more network slice instances using a 5G AN, and the UE may be associated with eight different S-NSSAIs. Furthermore, an AMF 321 instance serving a single UE 301 may belong to each network slice instance serving the UE.

[0074] Network slicing in the NG-RAN 310 involves RAN slice awareness. RAN slice awareness includes differentiated handling of traffic for different network slices that have been pre-configured. Slice awareness in the NG-RAN 310 is introduced at the PDU session level by indicating the S-NSSAI corresponding to the PDU session in all signaling including PDU session resource information. How the NG-RAN 310 supports enabling slicing in terms of NG-RAN functions (e.g., a set of network functions for each slice) depends on the specific implementation. The NG-RAN 310 uses assistance information provided by the UE 301 or the 5GC 320 to select the RAN part of the network slice, and this assistance information explicitly identifies one or more network slices among the pre-configured network slices in the PLMN. The NG-RAN 310 also supports resource management and policy enforcement between slices according to the SLA. A single NG-RAN node may support multiple slices, and the NG-RAN 310 may also appropriately apply appropriate RRM policies for the SLA to each supported slice. The NG-RAN 310 may also support QoS differentiation within a slice.

[0075] The NG-RAN 310 may also use UE assistance information to select the AMF 321 (if available) during the initial attachment. The NG-RAN 310 uses the assistance information to route the initial NAS to the AMF 321. If the NG-RAN 310 cannot use the assistance information to select the AMF 321, or the UE 301 does not provide any such information, the NG-RAN 310 sends the NAS signaling to the default AMF 321, which may be in the AMF 321 pool. For subsequent accesses, the UE 301 provides the temporary ID assigned to the UE 301 by the 5GC 320 to enable the NG-RAN 310 to route the NAS message to the appropriate AMF 321, as long as the temporary ID is valid. The NG-RAN 310 knows and can reach the AMF 321 associated with the temporary ID. Otherwise, the method for initial attachment is applied.

[0076] The NG-RAN 310 supports resource isolation between slices. The NG-RAN 310 resource isolation can be achieved through RRM policies and protection mechanisms, which should avoid shared resource shortages in the case where the service level agreement of one slice is interrupted in another slice. In some specific implementations, the NG-RAN 310 resources can be fully assigned to a certain slice. How the NG-RAN 310 supports resource isolation depends on the specific implementation.

[0077] Some slices may be only partially available in the network. The NG-RAN 310 knows that the slices supported in its neighboring cells may be beneficial for inter-frequency mobility in the connected mode. Within the registration area of the UE, the slice availability may not change. The NG-RAN 310 and the 5GC 320 are responsible for handling service requests for slices that may or may not be available in a given area. Permitting or denying access to a slice may depend on factors such as the support for the slice, the availability of resources, and the support of the NG-RAN 310 for the requested service.

[0078] The UE 301 may be associated with multiple network slices simultaneously. In the case where the UE 301 is associated with multiple slices simultaneously, only one signaling connection is maintained, and for intra-frequency cell reselection, the UE 301 attempts to pre-empt the best cell. For inter-frequency cell reselection, dedicated priorities can be used to control the frequency pre-empted by the UE 301. The 5GC 320 will verify that the UE 301 has the right to access the network slice. Before receiving the initial context setup request message, based on knowing the specific slice that the UE 301 is requesting access to, the NG-RAN 310 may be allowed to apply some temporary or local policies. During the initial context setup, the slice requesting its resources is notified to the NG-RAN 310.

[0079] Figure 4 An example of infrastructure equipment 400 is shown. The infrastructure equipment 400 (or "system 400") can be implemented as a base station, a radio headend, a RAN node (such as the RAN node 111 shown and described previously), an application server 130, or any other component or device discussed herein. In other examples, the system 400 can be implemented in or by a UE.

[0080] The system 400 includes: an application circuit 405, a baseband circuit 410, one or more radio front-end modules (RFEMs) 415, a memory circuit 420, a power management integrated circuit (PMIC) 425, a power triple circuit 430, a network controller circuit 435, a network interface connector 440, a satellite positioning circuit 445, and a user interface circuit 450. In some specific implementations, the system 400 may include additional elements, such as, for example, a memory, a storage device, a display, a camera, one or more sensors, or an input / output (I / O) interface, or a combination thereof, etc. In other examples, the components described with reference to the system 400 may be included in more than one device. For example, various circuits may be separately included in more than one device for CRAN, vBBU, or other specific implementations.

[0081] The application circuit 405 may include circuits such as, but not limited to, one or more processors (or processor cores), a cache memory, one or more of the following: a low-dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C, or a general-purpose programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, general-purpose input / output (I / O or IO), a memory card controller such as a secure digital (SD) multimedia card (MMC), a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor (or core) of the application circuit 405 may be coupled to a memory or a storage element or may include a memory or a storage element, and may be configured to execute instructions stored in the memory or the storage element to enable various application programs or operating systems to run on the system 400. In some specific implementations, the memory or the storage element may include an on-chip memory circuit, which may include any suitable volatile or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, or a combination thereof, and other types of memory.

[0082] The processor of the application circuit 405 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or a combination thereof, etc. In some specific implementations, the application circuit 405 may include or may be a dedicated processor or controller configured to execute the various techniques described herein. In some specific implementations, the system 400 may not utilize the application circuit 405 and, instead, may include a dedicated processor or controller to process, for example, IP data received from the EPC or 5GC.

[0083] In some specific implementations, the application circuit 405 may include one or more hardware accelerators, which may be a microprocessor, a programmable processing device, etc. The one or more hardware accelerators may include, for example, a computer vision (CV) or deep learning (DL) accelerator or both. In some specific implementations, the programmable processing device may be: one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs), etc.; programmable logic devices (PLDs), such as complex PLDs (CPLDs) or high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable system on chips (PSoCs), or a combination thereof, etc. In such specific implementations, the circuit of the application circuit 405 may include logic blocks or a logic architecture, as well as other interconnected resources that can be programmed to perform various functions such as the processes, methods, and functions described herein. In some specific implementations, the circuit of the application circuit 405 may include memory units (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) or antifuse)) for storing logic blocks, logic architectures, data, or other data in a look-up table (LUT), etc.

[0084] The user interface circuit 450 may include one or more user interfaces designed to enable a user to interact with the system 400 or a peripheral component interface, which is designed to enable a peripheral component to interact with the system 400. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., a light-emitting diode (LED)), a physical keyboard or keypad, a mouse, a touchpad, a touch screen, a speaker or other audio emitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, or a combination thereof, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0085] The radio front-end module (RFEM) 415 may include a millimeter-wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some specific 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 (see, for example Figure 6 the antenna array 611), and the RFEM may be connected to multiple antennas. In some specific implementations, the radio functions of both millimeter-wave and sub-millimeter-wave may be implemented in the same physical RFEM 415 that combines millimeter-wave antennas and sub-millimeter-wave. The baseband circuit 410 may be implemented as, for example, a solder-in substrate, a single-packaged integrated circuit soldered to the main circuit board, or a multi-chip module containing two or more integrated circuits.

[0086] The memory circuit 420 may include one or more of the following: volatile memory, such as dynamic random access memory (DRAM) or synchronous dynamic random access memory (SDRAM); and non-volatile memory (NVM), such as high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), or magnetoresistive random access memory (MRAM), or a combination thereof, etc. For example, the memory circuit 420 may be implemented as one or more of the following: a solder-in packaged integrated circuit, a socketed memory module, and a plug-in memory card.

[0087] The PMIC 425 may include voltage regulators, surge protectors, power alert detection circuits, and one or more backup power sources, such as a battery or a capacitor. The power alert detection circuit may detect one or more of a power-down (undervoltage) and a surge (overvoltage) condition. The power pass-through circuit 430 may provide power extracted from a network cable to supply both power and data connection to the infrastructure equipment 400 using a single cable.

[0088] The network controller circuit 435 may provide connectivity to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on Multi-Protocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to and from the infrastructure equipment 400 using a network interface connector 440 using a physical connection, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 435 may include one or more dedicated processors or FPGAs, or both, for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuit 435 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0089] The positioning circuit 445 includes circuits for receiving and decoding signals transmitted or broadcast by a positioning network of a global navigation satellite system (GNSS). Examples of GNSS include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's Beidou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS) for navigation), etc. The positioning circuit 445 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some specific implementations, the positioning circuit 445 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking and estimation without GNSS assistance. The positioning circuit 445 may also be part of or interact with the baseband circuit 410 or the RFEM 415 or both to communicate with nodes and components of the positioning network. The positioning circuit 445 may also provide data (e.g., location data, time data) to the application circuit 405, which may use the data to synchronize operations with various infrastructures (e.g., RAN node 111, etc.).

[0090] Figure 5An example of platform 500 (or "device 500") is shown. In some specific implementations, computer platform 500 may be adapted to be used as UE 101, 201, 301, application server 130, or any other component or device discussed herein. Platform 500 may include any combination of the components shown in the example. The components (or portions thereof) of platform 500 may be implemented as integrated circuits (ICs), discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within computer platform 500, or as components otherwise incorporated within a chassis of a larger system. Figure 5 The block diagram of Figure 5 is intended to show a high-level view of the components of platform 500. However, in some specific implementations, platform 500 may include fewer, additional, or alternative components, or Figure 5 different arrangements of the components shown.

[0091] Application circuitry 505 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces (such as SPI), I2C or general programmable serial interface modules, RTC, timer-counters (including interval timers and watchdog timers), general-purpose I / Os, memory card controllers (such as SD MMC or similar controllers), USB interfaces, MIPI interfaces, and JTAG test access ports. The processor (or core) of application circuitry 505 may be coupled to or may include memory / storage elements and may be configured to execute instructions stored in the memory or storage device to enable various application programs or operating systems to run on system 500. In some specific implementations, the memory or storage element may be an on-chip memory circuit that may include any suitable volatile or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, or combinations thereof, and other types of memory.

[0092] The processor of application circuit 505 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, some other known processing elements, or any suitable combination thereof. In some specific implementations, application circuit 405 may include or may be a dedicated processor / controller for performing the techniques described herein. In some specific implementations, application circuit 505 may be part of a system-on-chip (SoC), where application circuit 505 and other components are formed as a single integrated circuit or a single package.

[0093] In some specific implementations, application circuit 505 may include: circuitry such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs; PLDs such as CPLDs, HCPLDs; ASICs such as structured ASICs; PSoCs, or combinations thereof, etc. In some specific implementations, application circuit 505 may include logic blocks or logic architectures, and other interconnected resources that can be programmed to perform various functions such as the processes, methods, functions described herein. In some specific implementations, application circuit 505 may include memory units for storing logic blocks, logic structures, data, or other data in LUTs, etc., such as EPROMs, EEPROMs, flash memories, static memories (such as SRAMs or antifuses).

[0094] Baseband circuit 510 may be implemented as, for example, a solder-in substrate that includes one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module that includes two or more integrated circuits. Refer to Figure 6 Discuss the various hardware electronic components of baseband circuit 510.

[0095] RFEM 515 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave RFICs. In some specific 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 (see, for example, Figure 6 antenna array 611), and the RFEM may be connected to multiple antennas. In some specific implementations, the radio functions of both millimeter wave and sub-millimeter wave may be implemented in the same physical RFEM 515 that combines millimeter wave antennas and sub-millimeter waves. In some specific implementations, RFEM515, baseband circuit 510, or both are included in the transceiver of platform 500.

[0096] Memory circuit 520 may include any number and type of memory devices for providing a given amount of system memory. For example, memory circuit 520 may include one or more of volatile memory (such as RAM, DRAM, or SDRAM) and NVM (such as high-speed electrically erasable memory (commonly referred to as flash memory), PRAM, or MRAM), or a combination thereof, etc. In a low-power implementation, memory circuit 520 may be an on-chip memory or register associated with application circuit 505. To provide persistent storage of information such as data, application programs, operating systems, etc., memory circuit 520 may include one or more mass storage devices, which may include, for example, solid state drives (SSDs), hard disk drives (HDDs), micro-HDDs, resistive change memories, phase change memories, holographic memories, or chemical memories, etc.

[0097] Removable memory circuit 523 may include a device, circuit, housing, casing, port, or socket, etc. for coupling a portable data storage device to platform 500. These portable data storage devices may be used for mass storage and may include, for example, flash memory cards (such as Secure Digital (SD) cards, micro SD cards, xD Picture Cards), as well as USB flash drives, optical discs, or external HDDs, or a combination thereof, etc. Platform 500 may also include interface circuitry (not shown) for connecting external devices to platform 500. External devices connected to platform 500 using this interface circuitry include sensor circuit 521 and electromechanical components (EMC) 522, as well as removable memory devices coupled to removable memory circuit 523.

[0098] Sensor circuit 521 includes a device, module, or subsystem that is intended to detect events or changes in its environment and send information about the detected events (such as sensor data) to one or more other devices, modules, or subsystems. Examples of such sensors include: inertial measurement units (IMUs), such as accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including three-axis accelerometers, three-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (such as thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (such as cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (such as infrared radiation detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other audio capture devices, or a combination thereof, etc.

[0099] The EMC 522 includes devices, modules, or subsystems that are intended to enable the platform 500 to change its state, position, or orientation, or to move or control mechanisms, systems, or subsystems. Additionally, the EMC 522 can be configured to generate messages or signaling and send messages or signaling to other components of the platform 500 to indicate the current state of the EMC 522. Examples of the EMC 522 include, among other electromechanical components, one or more power switches, relays (such as electromechanical relays (EMRs) or solid-state relays (SSRs)), actuators (e.g., valve actuators), audible sound generators, visual warning devices, motors (e.g., DC motors or stepper motors), wheels, thrusters, propellers, claws, clamps, hooks, or combinations thereof. In some specific implementations, the platform 500 is configured to operate one or more EMC 522s based on one or more capture events, instructions, or control signals received from a service provider or a client or both.

[0100] In some specific implementations, the interface circuit can connect the platform 500 to the positioning circuit 545. The positioning circuit 545 includes circuitry for receiving and decoding signals transmitted or broadcast by the positioning network of the GNSS. The positioning circuit 545 includes various hardware elements (e.g., including hardware devices for facilitating OTA communication such as switches, filters, amplifiers, antenna elements, etc.) to communicate with components of the positioning network such as nodes of the navigation satellite constellation. In some specific implementations, the positioning circuit 545 can include a micro PNT IC that uses a primary timing clock to perform position tracking or estimation without GNSS assistance. The positioning circuit 545 can also be part of or interact with the baseband circuit 510 or the RFEM 515 or both to communicate with nodes and components of the positioning network. The positioning circuit 545 can also provide data (e.g., position data, time data) to the application circuit 505, which can use the data to synchronize operations with various infrastructure (e.g., radio base stations) for turn-by-turn navigation applications and the like.

[0101] In some specific implementations, the interface circuit may connect the platform 500 to a Near Field Communication (NFC) circuit 540. The NFC circuit 540 is configured to provide non-contact short-range communication based on Radio Frequency Identification (RFID) standards, where magnetic field sensing is used to enable communication between the NFC circuit 540 and an NFC-enabled device external to the platform 500 (e.g., an "NFC contact point"). The NFC circuit 540 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip or IC that provides NFC functionality to the NFC circuit 540 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit short-range RF signals. The RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 540, or initiate data transfer between the NFC circuit 540 and another active NFC device (e.g., a smart phone or an NFC-enabled POS terminal) near the platform 500.

[0102] The driver circuit 546 may include software elements and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 500. The driver circuit 546 may include various drivers, thereby allowing other components of the platform 500 to interact with or control various input / output (I / O) devices that may be present within or connected to the platform 500. For example, the driver circuit 546 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to the touch screen interface of the platform 500, a sensor driver for obtaining sensor readings from the sensor circuit 521 and controlling and allowing access to the sensor circuit 521, an EMC driver for obtaining the actuator position of the EMC 522 or controlling and allowing access to the EMC 522, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0103] A Power Management Integrated Circuit (PMIC) 525 (also referred to as "power management circuit 525") may manage the power provided to various components of the platform 500. Specifically, with respect to the baseband circuit 510, the PMIC 525 may control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMIC 525 may be included when the platform 500 is capable of being powered by a battery 530, e.g., when the device is included in the UE 101, 201, 301.

[0104] In some specific implementations, the PMIC 525 can control or otherwise be part of various power-saving mechanisms of the platform 500. For example, if the platform 500 is in the RRC_CONNECTED state, in which the platform remains connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform can enter a state called discontinuous reception mode (DRX). During this state, the platform 500 can power off for short intervals, thus saving power. If there is no data traffic activity for a longer period of time, the platform 500 can transition to the RRC_IDLE state, in which it is disconnected from the network and does not perform operations such as channel quality feedback or handover. This can allow the platform 500 to enter a very low-power state, in which it wakes up periodically to listen for the network and then powers off again. In some specific implementations, the platform 500 cannot receive data in the RRC_IDLE state but must transition back to the RRC_CONNECTED state to receive data. Additional power-saving modes can cause the device to be unavailable to the network for longer than the paging interval (ranging from a few seconds to several hours). During this period, the device may not be able to connect to the network and may power off completely. Any data sent during this period may experience significant latency, and it is assumed that the latency is acceptable.

[0105] The battery 530 can power the platform 500, but in some specific implementations, the platform 500 can be deployed in a fixed location and can have a power source coupled to the power grid. The battery 530 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, or a lithium-air battery, etc. In some specific implementations, such as in V2X applications, the battery 530 can be a typical lead-acid automotive battery.

[0106] In some specific implementations, the battery 530 can be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS can be included in the platform 500 to track the state of charge (SoCh) of the battery 530. The BMS can be used to monitor other parameters of the battery 530, such as the state of health (SoH) and the state of function (SoF) of the battery 530 to provide fault prediction. The BMS can transmit information about the battery 530 to the application circuit 505 or other components of the platform 500. The BMS can also include an analog-to-digital (ADC) converter that allows the application circuit 505 to directly monitor the voltage of the battery 530 or the current from the battery 530. Battery parameters can be used to determine actions that the platform 500 can perform, such as transmission frequency, network operation, sensing frequency, etc.

[0107] The user interface circuit 550 includes various input / output (I / O) devices present in or connected to the platform 500, and includes one or more user interfaces designed to implement user interaction with the platform 500 or a peripheral component interface designed to implement interaction with peripheral components of the platform 500. The user interface circuit 550 includes an input device circuit and an output device circuit. The input device circuit includes any physical or virtual device for accepting input, including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, or a headset, or a combination thereof, etc. The output device circuit includes any physical or virtual device for displaying information or otherwise communicating information (such as sensor readings, actuator positions, or other information). The output device circuit may include any number or combination of audio or visual displays, including one or more simple visual outputs or indicators (e.g., binary state indicators (e.g., light-emitting diodes (LEDs))), multi-character visual outputs, or more complex outputs such as a display device or a touch screen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, or a projector), where the output of characters, graphics, or multimedia objects is generated or produced by the operation of the platform 500. The output device circuit may also include a speaker or other audio emitting device, or a printer. In some specific embodiments, the sensor circuit 521 may be used as an input device circuit (e.g., an image capture device, or a motion capture device) and one or more EMCs may be used as an output device circuit (e.g., an actuator for providing tactile feedback). In another example, an NFC circuit may be included to read an electronic tag or connect to another NFC-enabled device, and the NFC circuit includes an NFC controller and a processing device coupled to an antenna element. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a USB port, an audio jack, or a power interface.

[0108] Figure 6 Exemplary components of the baseband circuit 610 and the radio frequency front-end module (RFEM) 615 are shown. The baseband circuit 610 may respectively correspond to Figure 4 the baseband circuit 410 of Figure 5 and Figure 4 the RFEM 415 of Figure 5 and the RFEM 515 of

[0109] The baseband circuit 610 includes circuitry configured to perform various radio or network protocols and control functions that enable communication with one or more radio networks using the RF circuit 606. The radio control functions may include, but are not limited to, signal modulation and demodulation, encoding and decoding, and radio frequency shifting. In some embodiments, the modulation and demodulation circuitry of the baseband circuit 610 may include fast Fourier transform (FFT), precoding, or constellation mapping and demapping functions. In some embodiments, the encoding and decoding circuitry of the baseband circuit 610 may include convolutional, tail-biting convolutional, turbo, Viterbi, or low density parity check (LDPC) encoder and decoder functions. The modulation and demodulation, and encoder and decoder functions are not limited to these examples and may include other suitable functions in other examples. The baseband circuit 610 is configured to process baseband signals received from the receive signal path of the RF circuit 606 and generate baseband signals for the transmit signal path of the RF circuit 606. The baseband circuit 610 is configured to interact with application circuitry (e.g., Figure 4 and Figure 5 the application circuitry 405, 505 shown in

[0110] to generate and process baseband signals and control the operation of the RF circuit 606. The baseband circuit 610 may process various radio control functions.

[0111] In some specific implementations, each of the processors 604A - 604E includes a corresponding memory interface to send data to and receive data from the memory 604G. The baseband circuit 610 may also include one or more interfaces for communicatively coupling to other circuits or devices, such as an interface for sending data to and receiving data from a memory external to the baseband circuit 610; an application circuit interface for sending data to and receiving data from the application circuits 405, 505 of Figure 4 and Figure 5 ; an RF circuit interface for sending data to and receiving data from the RF circuit 606 of Figure 6 ; a wireless hardware connection interface for sending data to and receiving data from one or more wireless hardware elements (e.g., near - field communication (NFC) components, low - power components, Wi - Fi components, etc.); and a power management interface for sending power or control signals to the PMIC 525 and receiving power or control signals from the PMIC.

[0112] In some specific implementations (which may be combined with the above examples), the baseband circuit 610 includes one or more digital baseband systems that are coupled to each other and to the CPU subsystem, audio subsystem, and interface subsystem using an interconnection subsystem. The digital baseband subsystems may also be coupled to the digital baseband interface and the mixed - signal baseband subsystem using another interconnection subsystem. Each of the interconnection subsystems may include a bus system, point - to - point connectors, a network - on - chip (NOC) architecture, or some other suitable bus or interconnection technology, such as those discussed herein. The audio subsystem may include DSP circuits, buffer memories, program memories, voice - processing accelerator circuits, data - converter circuits such as analog - to - digital converter circuits and digital - to - analog converter circuits, analog circuits including one or more of amplifiers and filters, etc. In some specific implementations, the baseband circuit 610 may include protocol - processing circuitry having one or more instances of control circuits (not shown) to provide control functions to the digital baseband circuit or the radio - frequency circuit (e.g., radio front - end module 615).

[0113] In some specific embodiments, the baseband circuit 610 includes various processing devices for operating one or more wireless communication protocols (e.g., a "multi-protocol baseband processor" or "protocol processing circuit") and various processing devices for implementing PHY layer functions. In some specific embodiments, the PHY layer functions include the aforementioned radio control functions. In some specific embodiments, the protocol processing circuit operates or implements various protocol layers or entities of one or more wireless communication protocols. For example, when the baseband circuit 610 or the RF circuit 606 or both are part of a millimeter-wave communication circuit or some other suitable cellular communication circuit, the protocol processing circuit can operate the LTE protocol entity or the 5G NR protocol entity or both. In this example, the protocol processing circuit can operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In some specific embodiments, when the baseband circuit 610 or the RF circuit 606 or both are part of a Wi-Fi communication system, the protocol processing circuit can operate one or more IEEE-based protocols. In this example, the protocol processing circuit can operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuit can include one or more memory structures (e.g., 604G) for storing program code and data for operating protocol functions, and one or more processing cores for executing the program code and performing various operations using the data. The baseband circuit 610 can also support radio communication for more than one wireless protocol.

[0114] The various hardware elements of the baseband circuit 610 discussed herein can be implemented as, for example, a soldered-in substrate that includes one or more integrated circuits (ICs), a single-packaged integrated circuit soldered to a main circuit board, or a multi-chip module that includes two or more ICs. In some specific embodiments, the components of the baseband circuit 610 can be appropriately combined in a single chip or a single chipset, or disposed on the same circuit board. In some specific embodiments, some or all of the components of the baseband circuit 610 and the RF circuit 606 can be implemented together, such as, for example, a system-on-chip (SoC) or a system-in-package (SiP). In some specific embodiments, some or all of the components of the baseband circuit 610 can be implemented as a separate SoC communicatively coupled to the RF circuit 606 (or multiple instances of the RF circuit 606). In some specific embodiments, some or all of the components of the baseband circuit 610 and the application circuits 405, 505 can be implemented together as separate SoCs (e.g., a "multi-chip package") mounted on the same circuit board.

[0115] In some specific embodiments, the baseband circuit 610 may provide communications compatible with one or more radio technologies. The RF circuit 606 may use modulated electromagnetic radiation to communicate with a wireless network through a non-solid medium. In some specific embodiments, the RF circuit 606 may include switches, filters, or amplifiers, as well as other components, to facilitate communication with the wireless network. The RF circuit 606 may include a receive signal path, which may include circuitry for downconverting an RF signal received from the FEM circuit 608 and providing a baseband signal to the baseband circuit 610. The RF circuit 606 may also include a transmit signal path, which may include circuitry for upconverting a baseband signal provided by the baseband circuit 610 and providing an RF output signal for transmission to the FEM circuit 608.

[0116] The receive signal path of the RF circuit 606 includes a mixer circuit 606a, an amplifier circuit 606b, and a filter circuit 606c. In some specific embodiments, the transmit signal path of the RF circuit 606 may include the filter circuit 606c and the mixer circuit 606a. The RF circuit 606 also includes a synthesizer circuit 606d for synthesizing frequencies for use by the mixer circuits 606a of the receive signal path and the transmit signal path. In some specific embodiments, the mixer circuit 606a of the receive signal path may be configured to downconvert an RF signal received from the FEM circuit 608 based on the synthesized frequency provided by the synthesizer circuit 606d. The amplifier circuit 606b may be configured to amplify the downconverted signal, and the filter circuit 606c may be a low-pass filter (LPF) or a band-pass filter (BPF), which is configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 610 for further processing. In some specific embodiments, the output baseband signal may be a zero-frequency baseband signal, but this is not required. In some specific embodiments, the mixer circuit 606a of the receive signal path may include a passive mixer.

[0117] In some specific embodiments, the mixer circuit 606a of the transmit signal path may be configured to upconvert an input baseband signal based on the synthesized frequency provided by the synthesizer circuit 606d to generate an RF output signal for the FEM circuit 608. The baseband signal may be provided by the baseband circuit 610 and may be filtered by the filter circuit 606c.

[0118] In some specific embodiments, the mixer circuit 606a in the receive signal path and the mixer circuit 606a in the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion respectively. In some specific embodiments, the mixer circuit 606a in the receive signal path and the mixer circuit 606a in the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some specific embodiments, the mixer circuit 606a in the receive signal path and the mixer circuit 606a in the transmit signal path may be arranged for direct downconversion and direct upconversion respectively. In some specific embodiments, the mixer circuit 606a in the receive signal path and the mixer circuit 606a in the transmit signal path may be configured for superheterodyne operation.

[0119] In some specific embodiments, the output baseband signal and the input baseband signal may be analog baseband signals. In some specific embodiments, the output baseband signal and the input baseband signal may be digital baseband signals, and the RF circuit 606 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 610 may include a digital baseband interface for communicating with the RF circuit 606. In some dual-mode examples, separate radio IC circuits may be provided to process signals of each spectrum, but the techniques described herein are not limited in this regard.

[0120] In some specific embodiments, the synthesizer circuit 606d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but other types of frequency synthesizers may also be used. For example, the synthesizer circuit 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider. The synthesizer circuit 606d may be configured to synthesize an output frequency based on a frequency input and a frequency divider control input for use by the mixer circuit 606a of the RF circuit 606. In some specific embodiments, the synthesizer circuit 606d may be a fractional-N / N+1 synthesizer.

[0121] In some specific embodiments, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not necessary. The frequency divider control input may be provided by the baseband circuit 610 or the application circuit 405 / 505 according to the desired output frequency. In some specific embodiments, the frequency divider control input (e.g., N) may be determined from a look-up table based on the channel indicated by the application circuits 405, 505.

[0122] The synthesizer circuit 606d of the RF circuit 606 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 modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide an input signal by N or N+1 (e.g., based on a carry output) to provide a fractional division ratio. In some embodiments, the DLL may include cascaded, tunable, delay elements, a phase detector, a charge pump, and a set of D-type flip-flops. The delay elements may be configured to divide the VCO period into Nd equal phase bins, 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 period.

[0123] In some embodiments, the synthesizer circuit 606d may be configured to generate a carrier frequency as the output frequency, while in other examples, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and may be used with an orthogonal generator and a frequency divider circuit to generate multiple signals having multiple different phases relative to each other at that carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 606 may include an IQ or a polarity converter.

[0124] The FEM circuit 608 may include a receive signal path that may include circuitry configured to operate on an RF signal received from the antenna array 611, amplify the received signal, and provide an amplified version of the received signal to the RF circuit 606 for further processing. The FEM circuit 608 may also include a transmit signal path that may include circuitry configured to amplify a transmit signal provided by the RF circuit 606 for transmission by one or more antenna elements in the antenna array 611. Amplification through the transmit signal path or the receive signal path may be done only in the RF circuit 606, only in the FEM circuit 608, or in both the RF circuit 606 and the FEM circuit 608.

[0125] In some embodiments, the FEM circuit 608 may include a TX / RX switch to switch between transmit mode and receive mode operations. The FEM circuit 608 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 608 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 606). The transmit signal path of the FEM circuit 608 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 606), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 611.

[0126] The antenna array 611 includes one or more antenna elements, each configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, a digital baseband signal provided by the baseband circuit 610 is converted into an analog RF signal (e.g., a modulated waveform), which will be amplified and transmitted using an antenna element of the antenna array 611 that includes one or more antenna elements (not shown). The antenna elements can be omnidirectional, directional, or a combination thereof. The antenna elements can form various arrangements as known and / or discussed herein. The antenna array 611 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 611 can be formed as a patch of metal foil in various shapes (e.g., a patch antenna), and can be coupled to the RF circuit 606 and / or the FEM circuit 608 using metal transmission lines and the like.

[0127] The processors of the application circuit 405 / 505 and the baseband circuit 610 can be used to execute elements of one or more instances of a protocol stack. For example, the processor of the baseband circuit 610, alone or in combination, can execute layer 3, layer 2, or layer 1 functions, while the processors of the application circuits 405, 505 can utilize the data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include the RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include the MAC layer, the RLC layer, and the PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 may include the PHY layer of the UE / RAN node, which will be described in further detail below.

[0128] Figure 7 Exemplary components of the communication circuit 700 are shown. In some embodiments, the communication circuit 700 may be implemented as Figure 4 and Figure 5Part of the illustrated system 400 or platform 500. The communication circuitry 700 may be communicatively coupled (e.g., directly or indirectly) to one or more antennas, such as antennas 711a, 711b, 711c, and 711d. In some embodiments, the communication circuitry 700 includes or is communicatively coupled to dedicated receive chains, processors, or radio components for multiple RATs, or combinations thereof (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as Figure 7 shown, the communication circuitry 700 includes modems 710 and 720, which may correspond to or be part of the baseband circuitry 410 and 510 shown in Figure 4 and Figure 5 . The modem 710 may be configured to communicate according to a first RAT, such as LTE or LTE-A, and the modem 720 may be configured to communicate according to a second RAT, such as 5G NR. In some embodiments, a processor 705, such as an application processor, may interact with the modems 710, 720.

[0129] The modem 710 includes one or more processors 712 and a memory 716 communicatively coupled to the processors 712. The modem 710 communicates with a radio frequency (RF) front end 730, which may correspond to or be part of the RFEMs 415 and 515 shown in Figure 4 and Figure 5 . The RF front end 730 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 730 includes an RX circuit 732 and a TX circuit 734. In some embodiments, the receive circuit 732 communicates with a DL front end 752, which may include circuitry for receiving radio signals from one or more antennas 711a. The transmit circuit 734 communicates with a UL front end 754, which is coupled to one or more antennas 711b.

[0130] Similarly, the modem 720 includes one or more processors 722 and a memory 726 communicatively coupled to the one or more processors 722. The modem 720 communicates with an RF front end 740, which may correspond to or be part of the RFEMs 415 and 515 shown in Figure 4 and Figure 5Shown is the RFEM 415 and 515 or a part thereof. The RF front end 740 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 740 includes a receiving circuit 742 and a transmitting circuit 744. In some specific embodiments, the receiving circuit 742 may communicate with the DL front end 760, which may include circuitry for receiving radio signals from one or more antennas 711c. The transmitting circuit 744 communicates with the UL front end 765, which is coupled to one or more antennas 711d. In some specific embodiments, one or more front ends may be combined. For example, an RF switch may selectively couple the modems 710, 720 to a single UL front end 772 for transmitting radio signals using one or more antennas.

[0131] The modem 710 may include hardware and software components for time division multiplexing UL data (e.g., for NSA NR operation) and various other techniques described herein. The processor 712 may include one or more processing elements configured to implement various features described herein, such as by executing program instructions stored in a memory 716 (e.g., a non-transitory computer-readable memory medium). In some specific embodiments, the processor 712 may be configured as a programmable hardware element, such as an FPGA or an ASIC. In some specific embodiments, the processor 712 may include one or more ICs configured to perform the functions of the processor 712. For example, each IC may include circuitry configured to perform the functions of the processor 712.

[0132] The modem 720 may include hardware and software components for time division multiplexing UL data (e.g., for NSA NR operation) and various other techniques described herein. The processor 722 may include one or more processing elements configured to implement various features described herein, such as by executing instructions stored in a memory 726 (e.g., a non-transitory computer-readable memory medium). In some specific embodiments, the processor 722 may be configured as a programmable hardware element, such as an FPGA or an ASIC. In some specific embodiments, the processor 722 may include one or more ICs configured to perform the functions of the processor 722.

[0133] Figure 8 Illustrated are various protocol functions that may be implemented in a wireless communication device. Specifically, Figure 8 An arrangement 800 is included that shows the interconnection between various protocol layers / entities. The following description is provided for various protocol layers and entities operating in conjunction with the 5G NR system standard and the LTE system standard, but Figure 8 some or all aspects of Figure 8 may also be applicable to other wireless communication network systems.

[0134] In addition to other higher layer functions not shown, the protocol layer of arrangement 800 may also include one or more of PHY 810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857. These protocol layers may include one or more service access points that can provide communication between two or more protocol layers (e.g., Figure 8 items 859, 856, 850, 849, 845, 835, 825, and 815 in

[0135] PHY 810 can transmit and receive physical layer signals 805, which can be received from one or more other communication devices or transmitted to one or more other communication devices. Physical layer signals 805 may include one or more physical channels, such as those discussed herein. PHY 810 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers (e.g., RRC 855). PHY 810 may further perform error detection on the transport channel, forward error correction (FEC) encoding and decoding of the transport channel, modulation and demodulation of the physical channel, interleaving, rate matching, mapping onto the physical channel, and MIMO antenna processing. In some specific embodiments, an instance of PHY 810 may process requests from an instance of MAC 820 and provide indications thereto using one or more PHY-SAP 815. According to some specific embodiments, the requests and indications transmitted using PHY-SAP 815 may include one or more transport channels.

[0136] An instance of MAC 820 may process requests from an instance of RLC 830 and provide indications thereto using one or more MAC-SAP 825. These requests and indications transmitted using MAC-SAP 825 may include one or more logical channels. MAC 820 may perform mapping between logical channels and transport channels, multiplex MAC SDUs from one or more logical channels onto transport blocks (TBs) to be delivered to PHY 810 using the transport channel, demultiplex MAC SDUs from the TBs delivered from PHY 810 using the transport channel onto one or more logical channels, multiplex MAC SDUs onto TBs, schedule information reporting, error correction via HARQ, and logical channel prioritization.

[0137] Instances of RLC 830 may utilize one or more radio link control service access points (RLC-SAPs) 835 to process requests from and provide indications to instances of PDCP 840. These requests and indications transmitted using RLC-SAP 835 may include one or more logical channels. RLC 830 may operate in multiple operation modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC 830 may perform the transmission of upper layer protocol data units (PDUs), error correction by automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 830 may also perform re-segmentation of RLC data PDUs for AM data transmission, reordering of RLC data PDUs for UM and AM data transmission, detection of duplicate data for UM and AM data transmission, discarding of RLC SDUs for UM and AM data transmission, detection of protocol errors for AM data transmission, and perform RLC re-establishment.

[0138] Instances of PDCP 840 may utilize one or more packet data convergence protocol service access points (PDCP-SAPs) 845 to process requests from and provide indications to instances of RRC 855 or SDAP 847 or both. These requests and indications transmitted using PDCP-SAP 845 may include one or more radio bearers. PDCP 840 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform in-sequence delivery of higher layer PDUs upon re-establishment of the lower layer, eliminate duplicate lower layer SDUs upon re-establishment of the lower layer for radio bearers mapped to RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discarding, and perform security operations (e.g., encryption, decryption, integrity protection, or integrity verification).

[0139] Instances of SDAP 847 can utilize one or more SDAP-SAPs 849 to process requests from one or more higher layer protocol entities and provide indications thereto. These requests and indications transmitted using SDAP-SAP 849 can include one or more QoS flows. SDAP 847 can map QoS flows to data radio bearers (DRBs) and vice versa, and can also mark QoS flow identifiers (QFIs) in DL packets and UL packets. A single SDAP entity 847 can be configured for a separate PDU session. In the UL direction, NG-RAN 110 can control the mapping of QoS flows to DRBs in two different ways (reflection mapping or explicit mapping). For reflection mapping, the SDAP 847 of UE 101 can monitor the QFI of DL packets of each DRB, and can apply the same mapping for the packets flowing in the UL direction. For a DRB, the SDAP 847 of UE 101 can map UL packets belonging to a QoS flow that corresponds to the QoS flow ID and PDU session observed in the DL packets of that DRB. To implement reflection mapping, NG-RAN 310 can mark DL packets with the QoS flow ID via the Uu interface. Explicit mapping can involve RRC 855 configuring SDAP 847 with an explicit mapping rule of QoS flows to DRBs, which can be stored and followed by SDAP 847. In some specific implementations, SDAP 847 can be used only in NR specific implementations and not in LTE specific implementations.

[0140] RRC 855 can configure aspects of one or more protocol layers using one or more management service access points (M-SAPs), and the one or more protocol layers can include one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840, and SDAP 847. In some specific implementations, an instance of RRC 855 can utilize one or more RRC-SAPs 856 to process requests from one or more NAS entities 857 and provide indications thereto. The main services and functions of RRC 855 can include broadcasting of system information (e.g., included in the master information block (MIB) or system information block (SIB) related to NAS), broadcasting of system information related to the access stratum (AS), paging, establishment, maintenance, and release of the RRC connection between UE 101 and RAN 110 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, mobility between RATs, and measurement configuration for UE measurement reports. These MIBs and SIBs can include one or more information elements (IEs), each of which can include individual data fields or data structures.

[0141] NAS 857 can form the top layer of the control plane between the UE 101 and the AMF 321. NAS 857 can support the mobility and session management procedures of the UE 101 to establish and maintain an IP connection between the UE 101 and the P-GW in the LTE system.

[0142] In some specific implementations, one or more protocol entities of the arrangement 800 can be implemented in the UE 101, the RAN node 111, the AMF 321 in the NR implementation or the MME 221 in the LTE implementation, the UPF 302 in the NR implementation or the S-GW 222 and the P-GW 223 in the LTE implementation, etc., for the control plane or user plane communication protocol stacks between the aforementioned devices. In some specific implementations, one or more protocol entities that can be implemented in one or more of the UE 101, the gNB 111, the AMF 321, etc., can communicate with the corresponding peer protocol entities that can be implemented in another device or on another device (using the services of the corresponding lower layer protocol entities to perform such communication). In some specific implementations, the gNB-CU of the gNB 111 can host the RRC 855, SDAP 847, and PDCP 840 of the gNB that control the operation of one or more gNB-DUs, and the gNB-DUs of the gNB 111 can each host the RLC 830, MAC 820, and PHY 810 of the gNB 111.

[0143] In some specific implementations, the control plane protocol stack can include, in order from the top layer to the bottom layer, NAS 857, RRC 855, PDCP 840, RLC 830, MAC 820, and PHY 810. In this example, the upper layer 860 can be built on top of the NAS 857, which includes an IP layer 861, an SCTP 862, and an application layer signaling protocol (AP) 863.

[0144] In some specific implementations such as NR implementations, the AP 863 can be the NG Application Protocol layer (NGAP or NG-AP) 863 for the NG interface 113 defined between the NG-RAN node 111 and the AMF 321, or the AP 863 can be the Xn Application Protocol layer (XnAP or Xn-AP) 863 for the Xn interface 112 defined between two or more RAN nodes 111. The NG-AP 863 can support the functions of the NG interface 113 and can include elementary procedures (EPs). The NG-AP EPs can be the interaction units between the NG-RAN node 111 and the AMF 321. The NG-AP863 services can include two groups: UE-associated services (e.g., services related to the UE101) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 111 and the AMF 321). These services can include functions such as, but not limited to: a paging function for sending a paging request to the NG-RAN node 111 involved in a specific paging area; a UE context management function for allowing the AMF 321 to establish, modify, or release the UE context in the AMF 321 and the NG-RAN node 111; a mobility function for the UE101 in the ECM-CONNECTED mode, for in-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signaling transmission function for transmitting or rerouting NAS messages between the UE 101 and the AMF 321; a NAS node selection function for determining the association between the AMF 321 and the UE 101; an NG interface management function for setting up the NG interface and monitoring errors through the NG interface; a warning message transmission function for providing a means to transmit warning messages or cancel the ongoing broadcast of warning messages using the NG interface; a configuration transmission function for requesting and transmitting RAN configuration information (e.g., SON information, or performance measurement (PM) data) between two RAN nodes 111 using the CN 120; or a combination thereof, etc.

[0145] The XnAP 863 can support the functions of the Xn interface 112 and can include XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures can include procedures for handling UE mobility within the NG RAN111 (or E-UTRAN 210), such as handover preparation and cancellation procedures, SN status transmission procedures, UE context retrieval and UE context release procedures, RAN paging procedures, or procedures related to dual connectivity, etc. The XnAP global procedures can include procedures not related to a specific UE 101, such as Xn interface setup and reset procedures, NG-RAN update procedures, or cell activation procedures, etc.

[0146] In an LTE implementation, AP 863 can be the S1 Application Protocol layer (S1-AP) 863 for the S1 interface 113 defined between the E-UTRAN node 111 and the MME, or AP 863 can be the X2 Application Protocol layer (X2AP or X2-AP) 863 for the X2 interface 112 defined between two or more E-UTRAN nodes 111.

[0147] The S1 Application Protocol layer (S1-AP) 863 can support the functions of the S1 interface, and similar to the previously discussed NG-AP, the S1-AP can include the S1-AP EP. The S1-AP EP can be the interaction unit between the E-UTRAN node 111 and the MME 221 within the LTE CN 120. The S1-AP 863 services can 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.

[0148] The X2AP 863 can support the functions of the X2 interface 112 and can include the X2AP basic mobility procedures and the X2AP global procedures. The X2AP basic mobility procedures can include procedures for handling UE mobility within the E-UTRAN 120, such as handover preparation and cancellation procedures, SN status transmission procedures, UE context retrieval and UE context release procedures, RAN paging procedures, or procedures related to dual connectivity, etc. The X2AP global procedures can include procedures not related to a specific UE 101, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, or cell activation procedures, etc.

[0149] The SCTP layer (alternatively referred to as the SCTP / IP layer) 862 can provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in an NR implementation, or S1-AP or X2AP messages in an LTE implementation). The SCTP 862 can ensure reliable delivery of signaling messages between the RAN node 111 and the AMF 321 / MME 221 partly based on the IP protocol supported by the IP 861. The Internet Protocol layer (IP) 861 can be used to perform packet addressing and routing functions. In some implementations, the IP layer 861 can use point-to-point transmission to deliver and transfer PDUs. In this regard, the RAN node 111 can include communication links (e.g., wired or wireless) with the L2 and L1 layers of the MME / AMF to exchange information.

[0150] In some specific implementations, the user plane protocol stack may include SDAP847, PDCP 840, RLC 830, MAC 820, and PHY 810 in order from the highest layer to the lowest layer. The user plane protocol stack may be used for communication between UE101, RAN node 111, and UPF 302 in an NR specific implementation, or for communication between S-GW 222 and P-GW 223 in an LTE specific implementation. In this example, the upper layer 851 may be built on top of SDAP 847 and may include the User Datagram Protocol (UDP) and IP Security layer (UDP / IP) 852, the General Packet Radio Service (GPRS) Tunneling Protocol layer for the user plane (GTP-U) 853, and the User Plane PDU layer (UP PDU) 863.

[0151] The transport network layer 854 (also referred to as the "transport layer") may be built on top of IP transport, and GTP-U 853 may be used on top of the UDP / IP layer 852 (including the UDP layer and the IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also referred to as the "internet layer") may be used to perform packet addressing and routing functions. The IP layer may assign IP addresses to user data packets in any one of, for example, IPv4, IPv6, or PPP formats.

[0152] GTP-U 853 may be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data may be packets in any one of IPv4, IPv6, or PPP formats. UDP / IP852 may provide a checksum for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication for selected data flows. The RAN node 111 and S-GW 222 may utilize the S1-U interface to exchange user plane data using a protocol stack including the L1 layer (e.g., PHY 810), the L2 layer (e.g., MAC 820, RLC 830, PDCP 840, and / or SDAP 847), the UDP / IP layer 852, and the GTP-U 853. The S-GW 222 and P-GW 223 may utilize the S5 / S8a interface to exchange user plane data using a protocol stack including the L1 layer, the L2 layer, the UDP / IP layer 852, and the GTP-U 853. As previously discussed, the NAS protocol may support the mobility and session management processes of the UE 101 to establish and maintain an IP connection between the UE 101 and the P-GW 223.

[0153] In addition, although Figure 8Although not shown, an application layer may exist above the AP 863 and / or the transport network layer 854. The application layer may be a layer in which users of the UE 101, RAN node 111, or other network elements interact with software applications, such as those executed by the application circuit 405 or the application circuit 505, respectively. The application layer may also provide one or more interfaces for the software applications to interact with the communication system (such as the baseband circuit 610) of the UE 101 or the RAN node 111. In some specific implementations, the IP layer or the application layer or both may provide the same or similar functions as those of layers 5 to 7 or parts thereof of the Open Systems Interconnection (OSI) model (e.g., OSI layer 7 - application layer, OSI layer 6 - presentation layer, and OSI layer 5 - session layer).

[0154] The NFV architecture and infrastructure can be used to virtualize one or more NFs onto physical resources that include a combination of industry-standard server hardware, storage hardware, or switches (alternatively implemented by proprietary hardware). In other words, the NFV system can be used to implement virtual or reconfigurable implementations of one or more EPC components and functions.

[0155] Figure 9 A block diagram of an example of a computer system including components for reading instructions from a machine-readable medium or a computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the techniques described herein is shown. In this example, Figure 9 A schematic diagram of hardware resources 900 is shown, including one or more processors (or processor cores) 910, one or more memories or storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled using a bus 940. For implementations in which node virtualization (e.g., NFV) is utilized, a hypervisor 902 may be executed to provide an execution environment for one or more network slices or sub-slices to utilize the hardware resources 900.

[0156] The processor 910 may include a processor 912 and a processor 914. The processor 910 may be, for example, a CPU, a RISC processor, a CISC processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof. The memory / storage device 920 may include a main memory, a disk storage device, or any suitable combination thereof. The memory / storage device 920 may include, but is not limited to, any type of volatile or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, or solid-state memory, or a combination thereof, and so on.

[0157] The communication resource 930 may include an interconnect device or a network interface component or other suitable device to communicate with one or more peripheral devices 904 or one or more databases 906 using the network 908. For example, the communication resource 930 may include a wired communication component (e.g., for coupling using USB), a cellular communication component, an NFC component, (or low-power) component, a Wi-Fi component, and other communication components.

[0158] The instructions 950 may include software, programs, applications, applets, apps, or other executable code for causing at least any one of the processors 910 to execute any one or more of the methods discussed herein. The instructions 950 may reside entirely or partially in at least one of the processors 910 (e.g., within the cache memory of the processor), the memory / storage device 920, or any suitable combination thereof. In addition, any part of the instructions 950 may be transmitted from any combination of the peripheral devices 904 or the databases 906 to the hardware resource 900. Thus, the memory of the processor 910, the memory / storage device 920, the peripheral devices 904, and the databases 906 are examples of computer-readable media and machine-readable media.

[0159] A UE (e.g., an NR-capable UE) may support various different services. In addition, the transmission of a service may be more urgent than the transmission of another service. In some cases, the UE may perform one or more transmissions in an out-of-order (OOO) manner. In some systems. For example, the gNB may transmit a first scheduling DCI and a second scheduling DCI to schedule a first uplink transmission and a second uplink transmission. Assuming that the first scheduling DCI is transmitted before the second scheduling DCI, the OOO transmission means that the uplink transmission corresponding to the second DCI (e.g., the second PUSCH transmission) occurs before the uplink transmission corresponding to the first DCI (e.g., the first PUSCH transmission). In some specific implementations, on a specific active BWP of a given serving cell, the UE may be scheduled using a second PUSCH transmission associated with a HARQ process x that starts earlier than the end symbol of a first PUSCH transmission associated with a HARQ process y (x!= y), where the second scheduling DCI is in the PDCCH and the end symbol of the second scheduling DCI is not earlier than the end symbol of the PDCCH carrying the first scheduling DCI.

[0160] Figure 10Timeline 1001 showing an example of out-of-order PUSCH scheduling and transmission. Scheduling DCIs (e.g., DCI-A, DCI-B, DCI-C) for PUSCH transmissions (labeled PUSCH-A, PUSCH-B, and PUSCH-C) arrive at the UE consecutively. In this example, DCI-B arrives after DCI-A, yet PUSCH-B is transmitted before PUSCH-A. Thus, the PUSCH-B transmission is out of order with respect to the arrival order of the DCIs. Thus, the PUSCH-B transmission is out of order with respect to the PUSCH-A transmission. The scheduling DCI may include a corresponding transmission power control (TPC) command for its corresponding PUSCH transmission. The TPC command for the PUSCH may be dynamically indicated in the scheduling DCI or the group common DCI. Thus, the DCI for PUSCH-A may have signaled a particular TPC command to be applied to transmit PUSCH-A. However, in between, the UE receives another DCI for PUSCH-B, where PUSCH-B is transmitted before PUSCH-A. In this context, whether the UE still follows the TPC command in the DCI for PUSCH-A for the PUSCH-A transmission, or whether it modifies the TPC command value based on the more recent DCI (e.g., the DCI for PUSCH-B) can be configured by network signaling.

[0161] Furthermore, the present disclosure provides a mechanism for closed-loop power control for PUSCH, including a mechanism for adjusting the PUSCH power control adjustment state at a given UE. The present disclosure describes how to update or calculate the TPC command at the time of its corresponding PUSCH transmission (including those PUSCH transmissions that occur out-of-order (OOO) with respect to the arrival order of the corresponding DCI). Unless otherwise specified, these and other specific implementations disclosed herein are applicable to licensed or unlicensed systems, FDD or TDD systems.

[0162] In one mechanism, the UE considers the TPC command value in the most recent UL grant (e.g., the most recent UL grant received for a second PUSCH that is OOO with respect to the first PUSCH) received before transmitting the first PUSCH (e.g., the PUSCH-A transmission in Figure 10 . In some specific implementations, the UE may ignore the TPC command value in the original UL grant for the first PUSCH. In some specific implementations, the UE may treat the TPC command value indicated in the UL grant for the out-of-order PUSCH as accumulative or non-accumulative.

[0163] In another mechanism, the gNB can dynamically indicate to the UE in the UL grant whether TPC command accumulation is enabled or disabled. In yet another mechanism, if the PUSCH is OOO, the UE can consider the TPC command value indicated in the DCI in a non-accumulative manner. In some specific implementations, this behavior can be applied regardless of the higher layer configuration of TPC accumulation.

[0164] The closed-loop power control of the UE can depend on the PUSCH power control adjustment state f of the active UL BWP b of carrier f of serving cell c at PUSCH transmission occasion i (b,f,c)(i,l) , and the PUSCH power control adjustment state f_(b,f,c)(i,l) is in turn a function of δ (PUSCH,b,f,c)(i,l) . Here, δ (PUSCH,b,f,c)(i,l) is the TPC command value included in a DCI message (such as a DCI format 0_0 or DCI format 0_1 message) that schedules the PUSCH transmission occasion i on the active UL BWP b of carrier f of serving cell c, or is jointly encoded with other TPC commands in DCI format 2_2 with a CRC scrambled by TPC-PUSCH-RNTI. The index l is the closed-loop power control loop index; if the UE is configured with twoPUSCH-PC-AdjustmentStates, then l ∈ {0,1}, and if the UE is not configured with twoPUSCH-PC-AdjustmentStates or if the PUSCH transmission is scheduled by a random access response (RAR) UL grant, then l = 0. For PUSCH transmissions configured by ConfiguredGrantConfig, the value of l ∈ {0,1} is provided to the UE via powerControlLoopToUse. In some cases, the PUSCH transmission can be a retransmission. If the UE is provided with SRI-PUSCH-PowerControl, the UE obtains the mapping between a set of values of the SRI field in DCI format 0_1 and the value l provided by sri-PUSCH-ClosedLoopIndex. If the PUSCH transmission is scheduled by DCI format 0_1 and if DCI format 0_1 includes the SRI field, the UE determines the value of l mapped to the SRI field value. If the PUSCH transmission is scheduled by DCI format 0_0 or by DCI format 0_1 that does not include the SRI field, or if SRI-PUSCH-PowerControl is not provided to the UE, then l = 0. If the UE obtains a TPC command from DCI format 2_2 with a CRC scrambled by TPC-PUSCH-RNTI, the value of l is provided by the closed-loop indicator field in DCI format 2_2.

[0165] In some wireless systems, the PUSCH power control adjustment state f(b,f,c)(i,l) Update as follows:

[0166]

[0167] If the UE is provided with a tpc-Accumulation configuration, δ PUSCH,b,f,c The value is given in Table 1. The summation term is the sum of the TPC command values in group D with a cardinality i of the TPC command values in group D, where the cardinality is the number of symbols on the active UL BWP b of carrier f of serving cell c for the PUSCH power control adjustment state l of the UE before the PUSCH transmission occasion i - i 0 before K PUSCH (i - i 0 ) - 1 symbols and before the K PUSCH (i) symbols received before the PUSCH transmission occasion i, where i 0 > 0 is the smallest integer such that the K 0 before the PUSCH transmission occasion i - i PUSCH (i - i 0 ) symbols are earlier than the K PUSCH (i) symbols before the PUSCH transmission occasion i.

[0168] If the PUSCH transmission is scheduled by a DCI format (e.g., DCI format 0_0 or DCI format 0_1), then K PUSCH (i) is the number of symbols on the UL BWP b of carrier f of serving cell c after the last symbol of the corresponding PDCCH reception and before the first symbol of the PUSCH transmission.

[0169] If the PUSCH transmission is configured by ConfiguredGrantConfig, then K PUSCH (i) is the product of the number of symbols per time slot and the minimum value provided by k2 in PUSCH-ConfigCommon for the active UL BWP b of carrier f of serving cell c PUSCH,min times the number of K

[0170] If the UE is not provided with a tpc-Accumulation configuration, then f b,f,c (i, l) = δ PUSCH,b,f,c (i, l) is the PUSCH power control adjustment state of the active UL BWP b of carrier f of serving cell c and the PUSCH transmission occasion i, where the absolute δ PUSCH,b,f,c value is given in Table 1.

[0171] TPC Command Field <![CDATA[Accumulated δ PUSCH,b,f,c [dB]]]> <![CDATA[Absolute δ PUSCH,b,f,c [dB]]]> 0 -1 -4 1 0 -1 2 1 1 3 3 4

[0172] Table 1

[0173] Figure 11 The timeline 1101 shows another example of out-of-order PUSCH scheduling and transmission. In this example, the PUSCHs are indexed according to the transmission order, i.e., PUSCH-B, PUSCH-A, and PUSCH-C are the PUSCH transmission occasion 1, PUSCH transmission occasion 2, and PUSCH transmission occasion 3, respectively. In some wireless systems, such as those using formula (1), Figure 11 the power control adjustment state of each PUSCH in

[0174] f b,f,c (A, l) = f + TPC_A,

[0175] f b,f,c (B, l) = f + TPC_B,

[0176] f b,f,c (C, l) = f b,f,c (A, l) + TPC_B + TPC_C,

[0177] where for a UE configured with tpc-Accumulation via higher layers, f = f b,f,c (A0, l); f b,f,c (A0, l) corresponds to the power control adjustment state when the UL grant for PUSCH A is received at the UE, otherwise, f = 0. However, PUSCH-B is out of order with respect to PUSCH-A, and although the DCI of PUSCH-A ends before the DCI of PUSCH-B, PUSCH-B occurs at transmission occasion 1 while PUSCH-A occurs at transmission occasion 2. Since there is no PUSCH transmission occasion before PUSCH-B in this example, f b,f,c (B, l) can be given by the TPC command indicated only in the DCI of PUSCH-B. The PUSCH transmission occasion (occasion 3) immediately before PUSCH-C is PUSCH-A (occasion 2), and in order to calculate f b,f,c (C, l), the TPC commands available between the start of K PUSCH (2) and the start of K PUSCH (3) are considered, i.e., assuming TPC accumulation is enabled, the TPC command for PUSCH-B and the DCI for PUSCH-C indicated in the DCI are added to f b,f,c(A, l). Therefore, in this example, the power control for PUSCH-C is affected by the presence of out-of-order PUSCH transmissions. This may be undesirable in some cases. In addition, the TPC command in the DCI of PUSCH-A is transmitted before the DCI of PUSCH-B. Therefore, the TPC command in the DCI of PUSCH-A can be deactivated at the moment of PUSCH-A transmission.

[0178] Technology 1

[0179] The UE may be provided with a tpc-Accumulation configuration by a higher layer. In some cases, the DCI of PUSCH occasion 1 may end after the DCI of PUSCH occasion 2, and the DCI of PUSCH occasion 0 ( Figure 11 (not shown) may end before the DCI of PUSCH occasion 2. If the UE is configured with tpc-Accumulation by a higher layer, the power control adjustment state of PUSCH occasion 2 can be given by

[0180] f b,f,c (2, l) = f b,f,c (0, l) + TPC_1 + TPC_2 (2)

[0181] where TPC_i is the TPC command indicated in the DCI of the PUSCH occasion. It should be noted that according to the traditional process, f b,f,c (2, l) = f b,f,c (0, l) + TPC_2, that is, the TPC command in the DCI of out-of-order PUSCH is not considered. According to formula (2), when calculating the power control adjustment state of PUSCH occasion 2, the UE adds the TPC command value to the DCI of out-of-order PUSCH.

[0182] The power control adjustment state of PUSCH occasion 1 (out-of-order PUSCH) can be given by:

[0183] f b,f,c (1, l) = f b,f,c (0, l) + TPC_1.

[0184] In some specific implementations, the power control adjustment state of PUSCH occasion 2 can be given by:

[0185] f b,f,c (2, l) = f b,f,c (0, l) + TPC_1 (3)

[0186] Among them, the power control adjustment state of PUSCH occasion 2 is updated by adding the TPC command available in the most recent DCI before PUSCH occasion 2. In this example, the most recent DCI is the DCI of PUSCH occasion 1. Therefore, in formula (3), the TPC command in the DCI of PUSCH occasion 2 is not considered or used, and this TPC command may expire at PUSCH occasion 2.

[0187] In some specific embodiments, the power control adjustment state of PUSCH occasion 2 can be given by the following formula

[0188] f b,f,c (2, l) = f b,f,c (1, l) (4)

[0189] Among them, the power control adjustment state of PUSCH occasion 2 is after the power control adjustment state of PUSCH occasion 1. Here, if the UE determines that an out-of-order PUSCH (here, this is PUSCH occasion 1) has been scheduled before a given PUSCH occasion, the UE ignores the TPC command indicated in the DCI of the given PUSCH occasion (such as PUSCH occasion 2 here), but follows the power control adjustment state of the OOO PUSCH transmitted before the given PUSCH.

[0190] In some specific embodiments, the power control adjustment state of PUSCH occasion 2 can be given by the following formula

[0191] f b,f,c (2, l) = TPC_1 (5)

[0192] Among them, the power control adjustment state of PUSCH occasion 2 follows the TPC command in the DCI of PUSCH occasion 1. Here, if the UE recognizes that an out-of-order PUSCH (here, this is PUSCH occasion 1) has been scheduled before a given PUSCH occasion (such as PUSCH occasion 2 here), the UE ignores the TPC command indicated in the DCI of the given PUSCH occasion, but follows the TPC command indicated in the DCI of the OOO PUSCH transmitted before the given PUSCH.

[0193] The UE can be configured by higher layers, such as UE-specific RRC signaling, where an indication can be provided to enable or disable one or more of the behaviors or processes described herein. In the above example, if there is no PUSCH occasion 0, then f b,f,c (0, l) = 0.

[0194] In some specific embodiments, the power control adjustment state of PUSCH occasion 3 can be given by the following formula

[0195] f b,f,c(3, l) = f b,f,c (2, l) + TPC_3

[0196] Among them, the TPC_1 command in the DCI of the out-of-order PUSCH, that is, PUSCH 1, is ignored, which will be considered according to the Rel-15 considerations.

[0197] Assume that the PUSCH occasion i–1 and the PUSCH occasion i are in order. Then, K ≥ 1 out-of-order PUSCHs can be scheduled between the DCI of the PUSCH occasion i–1 and the DCI of the PUSCH occasion i. In view of this, the power control adjustment state of the PUSCH occasion i can be given by f b，f，c (i, l) = f b，f，c (i - 1, l) + TPC_i. Among them, for updating the power control adjustment state that is not an out-of-order PUSCH, the TPC command in the DCI for the out-of-order PUSCH is not considered. It should be noted that in some specific implementations, the cumulative effect of the TPC commands of one or more out-of-order PUSCHs may still be applicable.

[0198] If K > 1 out-of-order PUSCHs are scheduled, then in some specific implementations, for each out-of-order PUSCH, accumulate the TPC of the previous out-of-order PUSCH (that is, the previous out-of-order PUSCH that is also out-of-order relative to the given PUSCH). That is, for the k-th out-of-order PUSCH occasion, i OOO,k = (i - 1) + j k , k = 0, …, K - 1, the power control adjustment state is given by

[0199] f b,f,c (i OOO,0 , l) = f b,f,c (i - 1, l) + TPC_{i OOO,0} (for k = 0),

[0200] f b,f,c (i OOO,1 , l) = f b,f,c (i OOO,0 , l) + TPC_{i OOO,1} (for k = 1), and

[0201] f b,f,c (i OOO,k , l) = f b,f,c (i OOO,k-1 , l) + TPC_{i OOO,k}.

[0202] This is referred to as UE "behavior A" in this article. In this example, i - 1 is the latest non-OOO PUSCH scheduled before the K out-of-order PUSCHs. Here, j kis an integer and j k+1 > j k . For example, for k = 0, j 0 can be 1, and for k = 1, j 1 can be 4, which means that between consecutive PUSCHs that are not out-of-order, there can be zero or more PUSCHs that are not out-of-order.

[0203] In some specific implementations, for each out-of-order PUSCH, the TPC of any previous out-of-order PUSCH is not accumulated. That is, for the k-th out-of-order PUSCH occasion, k = 0, …, K - 1, the power control adjustment state can be given by the following formula

[0204] f b,f,c (i OOO,k , l) = f b,f,c (i - 1, l)+TPC_{i OOO,k}.

[0205] Here, i - 1 refers to the most recent PUSCH occasion that was not out-of-order before i OOO,k . The TPC command is updated based on the previous PUSCH occasion that was not out-of-order. This is referred to as UE "behavior B" in this document. In some specific implementations, it is dynamically indicated in the DCI whether the UE applies behavior A or behavior B for out-of-order PUSCHs. Such dynamic indication can be explicit or implicit.

[0206] Technology 2

[0207] If the PUSCH is scheduled out-of-order, the power control adjustment state of the PUSCH occasion can be given by the absolute value based on the TPC command indicated in the DCI of the PUSCH occasion. In this case, the power control adjustment states of PUSCH occasion 1, PUSCH occasion 2, and PUSCH occasion 3 can be given as follows:

[0208] f b,f,c (1, l) = TPC_1,

[0209] f b,f,c (2, l) = f b,f,c (0, l)+TPC_1, and

[0210] f b,f,c (3, l) = f b,f,c (0, l)+TPC_1+TPC_3.

[0211] The UE can be configured to have TPC accumulation. In some specific implementations, if an out-of-order PUSCH is scheduled, this configuration can be overridden. In this case, the UE assumes non-accumulative power control for out-of-order PUSCH transmissions and applies the TPC command value indicated as an absolute value, for example, the third column of Table 1. For subsequent PUSCH occasions that are not out-of-order, such as in Equation (1), the UE can apply the TPC accumulation process after high-layer configuration.

[0212] In some specific implementations, if PUSCH occasion i - 1 is not out-of-order relative to PUSCH occasion i and i is out-of-order relative to PUSCH occasion i + 1, and there are K => 1 DCIs scheduling PUSCH occasions greater than i, where the K DCIs appear between the DCIs of PUSCH occasions i - 1 and i, then the power control adjustment state of PUSCH occasion i can be given by the following formula:

[0213] f b，f，c (i, l) = f b，f，c (i - 1, l) + TPC i

[0214] where the TPC commands corresponding to the K DCIs are ignored.

[0215] In some specific implementations, if out-of-order PUSCH handling is supported as a UE capability, the UE can be configured to have a separate tpc-Accumulation configuration that applies only to out-of-order PUSCH. For PUSCH, there may be a separate tpc-Accumulation configuration that is not out-of-order. If tpc-Accumulation is provided for OOO PUSCH, the UE can apply the legacy Rel-15 process to out-of-order PUSCH. If tpc-Accumulation is not provided for out-of-order PUSCH, the UE can apply the absolute value of the TPC command as the power control adjustment.

[0216] Technology 3

[0217] In some specific implementations, the DCI containing the UL grant includes a field for enabling or disabling TPC accumulation. For example, if a 1-bit field indicates 0, the UE can assume that TPC accumulation is not applied and assume the absolute value corresponding to the indicated TPC command, and if a 1-bit field indicates 1, the UE can assume that TPC accumulation is applied, and vice versa. Specifically, this is for cases where TPC accumulation may not be applied and the absolute value is used based on the TPC command (e.g., δ given in Table 1) PUSCH,b,f,cOut-of-order PUSCH scheduling with power control based on absolute value may be beneficial. The DCI indication can override the existing higher layer configuration of TPC accumulation. For example, even if TPC accumulation is provided to the UE, the DCI can disable it for a given PUSCH transmission, and the UE will use the absolute value for power control instead.

[0218] In some specific implementations, for a UE with a higher layer configuration of tpc-Accumulation, the power control state of OOO PUSCH assumes TPC accumulation, and the dynamic indication indicates whether the TPC for OOO PUSCH should be accumulated at subsequent PUSCH opportunities.

[0219] Figure 12 A flowchart illustrating an example of power control process 1201 is shown. This process 1201 can be executed by a device such as a UE. In some specific implementations, the operations shown for process 1201 can be overlapped in time, combined, and / or interleaved. At 1205, the UE receives signaling regarding TPC accumulation. Receiving signaling regarding TPC accumulation can include receiving one or more RRC parameters. In some specific implementations, the DCI can provide signaling regarding TPC accumulation.

[0220] At 1210, the UE receives a DCI message corresponding to a PUSCH transmission opportunity. This DCI message can include a TPC command. In some specific implementations, the DCI message can provide signaling to control whether a previous power control adjustment state is applied to the PUSCH transmission corresponding to the DCI message.

[0221] At 1215, the UE determines the power control adjustment state for the PUSCH transmission opportunity based on the power control information. In some specific implementations, the UE can determine whether to enable TPC accumulation. In some specific implementations, the UE can determine whether the signaling in the DCI message overrides a previously enabled TPC accumulation configuration. In some specific implementations, the UE can determine whether the PUSCH transmission opportunity occurs out of order relative to the arrival order of the DCI message. At 1215, the UE transmits at the PUSCH transmission opportunity according to the power control adjustment state.

[0222] Figure 13 A flowchart illustrating another example of power control process 1301 is shown. At 1305, the UE receives signaling enabling TPC accumulation. In some specific implementations, this signaling is carried by the RRC. At 1310, the UE is configured to determine a power control instruction based on a dynamic indication regarding whether the TPC for an out-of-order PUSCH should be accumulated for subsequent PUSCH opportunities. In some specific implementations, this dynamic indication is carried in the DCI message. For example, the DCI message for a subsequent PUSCH opportunity can include an indication overriding a previously configured TPC accumulation setting.

[0223] Power control techniques performed by devices such as UEs may include receiving DCI for a first PUSCH opportunity, a second PUSCH opportunity, and a third PUSCH opportunity, wherein the DCI for the second PUSCH opportunity ends after the DCI for the third PUSCH opportunity, the DCI for the first PUSCH opportunity ends before the DCI for the third PUSCH opportunity, the first PUSCH opportunity ends before the second PUSCH opportunity and the third PUSCH opportunity, and the second PUSCH opportunity ends before the third PUSCH opportunity; receiving higher layer signaling providing TPC accumulation; and transmitting the third PUSCH opportunity with a transmit power based on the TPC command in the DCI for the second PUSCH opportunity. The DCI message may include a scheduling DCI message in the UL grant.

[0224] In some specific implementations, higher layer signaling enabling power control adjustment is provided to the UE. In some specific implementations, higher layer signaling is provided to the UE that makes the power control adjustment for the second PUSCH opportunity non-accumulative and given by the absolute value of the TPC command indicated in the DCI. In some specific implementations, the power control adjustment for the third PUSCH opportunity may be given by the power control adjustment for the second PUSCH opportunity. In some specific implementations, the power control adjustment for the third PUSCH opportunity may be given by adding the TPC command values indicated in the DCI for the second PUSCH opportunity and the third PUSCH opportunity. In some specific implementations, the technique may include based on f b,f,c (3,l) = f b,f,c (2,l) + TPC_3 to determine the power control adjustment status for PUSCH opportunity 3. In some specific implementations, the technique may include based on f b,f,c (i,l) = f b,f,c (i - 1,l) + TPC_i to determine the power control adjustment status for PUSCH opportunity i. In some specific implementations, techniques for operating a UE configured by a higher layer with tpc-Accumulation may include assuming TPC accumulation for the power control state of out-of-order PUSCHs and determining an instruction based on a dynamic indication of whether TPC for out-of-order PUSCHs should be accumulated for subsequent PUSCH opportunities.

[0225] These and other techniques may be performed by apparatus implemented in or employed by one or more types of network components, user equipment, or both. In some particular implementations, one or more non-transitory computer-readable media include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more of the techniques described herein. An apparatus may include one or more processors and one or more computer-readable media, the computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more of the techniques.

[0226] In different particular implementations, the methods described herein may be implemented in software, hardware, or a combination thereof. Additionally, the order of the blocks of the methods may be changed, and various elements may be added, reordered, combined, omitted, modified, etc. Various modifications and changes will be apparent to those skilled in the art who benefit from this disclosure. The various particular implementations described herein are intended to be illustrative and not restrictive. Many variations, modifications, additions, and improvements are possible. Thus, multiple examples may be provided for components described herein as a single example. The boundaries between various components, operations, and data repositories are to some extent arbitrary, and particular operations are shown in the context of specific exemplary configurations. Other allocations of functionality are anticipated and may fall within the scope of the appended claims. Finally, the structure and functionality presented as discrete components in an exemplary configuration may be implemented as a combined structure or component.

[0227] The methods described herein may be implemented in circuitry such as one or more of the following: integrated circuits, logic circuits, processors (shared, dedicated, or group) and / or memories (shared, dedicated, or group), 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 SoCs), digital signal processors (DSPs), or some combination thereof. Examples of processors may include Apple A-series processors, Architecture Core TMProcessors, ARM processors, AMD processors, and Qualcomm processors. Other types of processors are possible. In some specific implementations, the circuitry may execute one or more software or firmware programs to provide at least some of the functions. The term "circuitry" may also refer to a combination of one or more hardware elements and program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these implementations, the combination of the hardware elements and the program code may be referred to as a particular type of circuitry. The circuitry may also include radio circuitry, such as a transmitter, a receiver, or a transceiver.

[0228] Multiple specific implementations have been described. However, it should be understood that various modifications can be made. Elements in one or more specific implementations may be combined, deleted, modified, or supplemented to form additional specific implementations. As another example, the logical flows shown in the figures do not require the particular order or sequential order shown to achieve the desired result. Additionally, other steps may be provided or steps may be eliminated from the process, and other components may be added to or removed from the system. Accordingly, other specific implementations are within the scope of the following claims.

Claims

1. A method for communication, comprising: receiving, by a user equipment (UE), a downlink control information (DCI) message corresponding to a physical uplink shared channel (PUSCH) transmission occasion; determining, by the UE, a power control adjustment state of the PUSCH transmission occasion, wherein determining the power control adjustment state includes determining that a first PUSCH transmission occasion, a second PUSCH transmission occasion, and a third PUSCH transmission occasion occur out of order with respect to an arrival order of the DCI message, wherein the PUSCH transmission occasions occur in an order of the first PUSCH transmission occasion, the second PUSCH transmission occasion, and the third PUSCH transmission occasion; wherein determining the power control adjustment state includes: determining a first power control adjustment state corresponding to the first PUSCH transmission occasion, determining a second power control adjustment state corresponding to the second PUSCH transmission occasion, and determining a third power control adjustment state corresponding to the third PUSCH transmission occasion; and in response to determining that a PUSCH transmission occasion occurs out of order before a given PUSCH transmission occasion among the first PUSCH transmission occasion, the second PUSCH transmission occasion, and the third PUSCH transmission occasion, ignoring a transmit power control (TPC) command value indicated in the DCI message for the given PUSCH transmission occasion to use a power control adjustment state of a PUSCH transmission occasion before the given PUSCH transmission occasion as a power control adjustment state corresponding to the given PUSCH transmission occasion; and transmitting, by the UE, at the PUSCH transmission occasion according to the power control adjustment state.

2. The method according to claim 1, comprising: receiving, by the UE, higher layer signaling enabling transmit power control (TPC) accumulation.

3. The method according to claim 1, wherein determining the power control adjustment state includes: when the first PUSCH transmission occasion occurs out of order with respect to the second PUSCH transmission occasion, determining whether to use the first power control adjustment state corresponding to the first PUSCH transmission occasion when determining the second power control adjustment state corresponding to the second PUSCH transmission occasion.

4. The method according to claim 1, wherein: the DCI message of the second PUSCH transmission occasion arrives before the first PUSCH transmission occasion, the DCI message of the second PUSCH transmission occasion arrives before the DCI message of the third PUSCH transmission occasion, the DCI message of the first PUSCH transmission occasion arrives before the DCI message of the third PUSCH transmission occasion, the first PUSCH transmission occasion ends before the second PUSCH transmission occasion and the third PUSCH transmission occasion, and the second PUSCH transmission occasion ends before the third PUSCH transmission occasion.

5. A user equipment (UE), the UE comprising: One or more processors; A transceiver; And A memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including: Receiving, via the transceiver, a downlink control information (DCI) message corresponding to a respective physical uplink shared channel (PUSCH) transmission occasion; Determining a power control adjustment state of the PUSCH transmission occasion, wherein determining the power control adjustment state includes determining that a first PUSCH transmission occasion, a second PUSCH transmission occasion, and a third PUSCH transmission occasion occur out of order with respect to the arrival order of the DCI message, wherein the PUSCH transmission occasions occur in the order of the first PUSCH transmission occasion, the second PUSCH transmission occasion, and the third PUSCH transmission occasion; Wherein determining the power control adjustment state includes: Determining a first power control adjustment state corresponding to the first PUSCH transmission occasion, determining a second power control adjustment state corresponding to the second PUSCH transmission occasion, and determining a third power control adjustment state corresponding to the third PUSCH transmission occasion; and In response to determining that a PUSCH transmission occasion occurs out of order before a given PUSCH transmission occasion among the first PUSCH transmission occasion, the second PUSCH transmission occasion, and the third PUSCH transmission occasion, ignoring the transmit power control (TPC) command value indicated in the DCI message for the given PUSCH transmission occasion and using the power control adjustment state of the PUSCH transmission occasion before the given PUSCH transmission occasion as the power control adjustment state corresponding to the given PUSCH transmission occasion; and Transmitting, via the transceiver, according to the power control adjustment state at the PUSCH transmission occasion.

6. The UE according to claim 5, Wherein, The operations include: Receiving higher layer signaling enabling transmit power control (TPC) accumulation.

7. The UE according to claim 5, Wherein, Determining the power control adjustment state includes: when the first PUSCH transmission occasion occurs out of order with respect to the second PUSCH transmission occasion, determining whether to use the first power control adjustment state corresponding to the first PUSCH transmission occasion when determining the second power control adjustment state corresponding to the second PUSCH transmission occasion.

8. The UE according to claim 5, Wherein: The DCI message of the second PUSCH transmission occasion arrives before the first PUSCH transmission occasion, The DCI message of the second PUSCH transmission occasion arrives before the DCI message of the third PUSCH transmission occasion, The DCI message of the first PUSCH transmission occasion arrives before the DCI message of the third PUSCH transmission occasion, The first PUSCH transmission occasion ends before the second PUSCH transmission occasion and the third PUSCH transmission occasion, and the second PUSCH transmission occasion ends before the third PUSCH transmission occasion.

9. A device for communication, comprising: a circuit configured to receive a downlink control information DCI message corresponding to a respective physical uplink shared channel PUSCH transmission occasion, the circuit further being configured to perform transmission at the PUSCH transmission occasion according to a respective power control adjustment state; and a circuit configured to perform operations including: determining the power control adjustment state of the PUSCH transmission occasion, wherein determining the power control adjustment state includes determining a first PUSCH transmission occasion, a second PUSCH transmission occasion, and a third PUSCH transmission occasion occur out of order with respect to the arrival order of the DCI message, wherein the PUSCH transmission occasions occur in the order of the first PUSCH transmission occasion, the second PUSCH transmission occasion, and the third PUSCH transmission occasion, wherein determining the power control adjustment state includes: determining a first power control adjustment state corresponding to the first PUSCH transmission occasion, determining a second power control adjustment state corresponding to the second PUSCH transmission occasion, and determining a third power control adjustment state corresponding to the third PUSCH transmission occasion, and in response to determining that a PUSCH transmission occasion occurs out of order before a given PUSCH transmission occasion among the first PUSCH transmission occasion, the second PUSCH transmission occasion, and the third PUSCH transmission occasion, ignoring the TPC command value indicated in the DCI message for the given PUSCH transmission occasion to use the power control adjustment state of the PUSCH transmission occasion before the given PUSCH transmission occasion as the power control adjustment state corresponding to the given PUSCH transmission occasion.

10. The device according to claim 9, wherein, the operations include: receiving higher layer signaling enabling transmission power control TPC accumulation.

11. The device according to claim 9, wherein, determining the power control adjustment state includes: when the first PUSCH transmission occasion occurs out of order with respect to the second PUSCH transmission occasion, determining whether to use the first power control adjustment state corresponding to the first PUSCH transmission occasion when determining the second power control adjustment state corresponding to the second PUSCH transmission occasion.

12. The device according to claim 9, wherein: the DCI message of the second PUSCH transmission occasion arrives before the first PUSCH transmission occasion, the DCI message of the second PUSCH transmission occasion arrives before the DCI message of the third PUSCH transmission occasion, The DCI message of the first PUSCH transmission occasion arrives before the DCI message of the third PUSCH transmission occasion, the first PUSCH transmission occasion ends before the second PUSCH transmission occasion and the third PUSCH transmission occasion, and the second PUSCH transmission occasion ends before the third PUSCH transmission occasion.

Images