Ultra-reliable and low latency resource allocation for multiple transmit receive points

Abstract

The invention relates to ultra-reliable and low latency resource allocation for multiple transmit receive points. The present disclosure describes a method for an access node configured for ultra-reliable and low latency (URLLC) transmissions to a UE using multiple transmit receive points (TRPs). The access node includes a processor circuit and a radio front-end circuit. The processor circuit is configured to allocate resource blocks into a first portion and a second portion based on a resource indication value (RIV), a length (LRBS) of consecutively allocated resource blocks, and a score. The radio front-end circuit is configured to transmit the first portion to the UE via the first transmit receive point (TRP1) and the second portion to the UE via the second transmit receive point (TRP2).

Description

[0001] This application is a divisional application of the invention patent application with application date of February 17, 2020, application number 202080014482.X, and invention name “Ultra-reliable and low-latency resource allocation for multiple transmission receiving points”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This patent application claims priority to U.S. Provisional Application No. 62 / 806,640, filed on February 15, 2019, which is incorporated herein by reference in its entirety. Technical Field

[0004] Various embodiments may generally relate to the field of wireless communications. Summary of the invention

[0005] An embodiment is described, which is an access node configured for ultra-reliable and low-latency (URLLC) transmission to a UE using multiple transmission reception points (TRPs). The access node includes a processor circuit and a radio front-end circuit. The processor circuit is configured to allocate a resource block into a first part and a second part based on a resource indication value (RIV), a length of a consecutively allocated resource block (LRBS), and a fraction. The radio front-end circuit is configured to transmit the first part to the UE via a first transmission reception point (TRP1) and transmit the second part to the UE via a second transmission reception point (TRP2).

[0006] Another embodiment is a method for ultra-reliable and low-latency (URLLC) transmission to a UE using multiple transmission reception points (TRPs) by an access node, the method comprising the following steps. The method comprises allocating a resource block into a first part and a second part based on a resource indication value (RIV), a length of a consecutively allocated resource block (LRBS), and a fraction. The method also comprises transmitting the first part to the UE via a first transmission reception point (TRP1), and transmitting the second part to the UE via a second transmission reception point (TRP2).

[0007] Another embodiment is described, which is a computer readable medium (CRM) including computer instructions, wherein when the instructions are executed by one or more processors of an electronic device, the electronic device is caused to perform various steps. The steps include allocating resource blocks into a first part and a second part based on a resource indication value (RIV), a length of a consecutively allocated resource block (LRBS), and a fraction. The steps also include transmitting the first part to a UE via a first transmission reception point (TRP1), and transmitting the second part to the UE via a second transmission reception point (TRP2). BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 Multiple transmission reception point (TRP) ultra-reliable and low latency (URLLC) transmission according to some embodiments is shown.

[0009] Figure 2 Depicted is the architecture of a system of networks according to some embodiments.

[0010] Figure 3 An architecture of a system including a first core network according to some embodiments is depicted.

[0011] Figure 4 An architecture of a system including a second core network according to some embodiments is depicted.

[0012] Figure 5 Depicted are examples of infrastructure equipment according to various embodiments.

[0013] Figure 6 Exemplary components of a computer platform according to various embodiments are shown.

[0014] Figure 7 Depicted are exemplary components of baseband circuitry and radio frequency circuitry according to various embodiments.

[0015] Figure 8 is a diagram of various protocol functions that may be used in various protocol stacks according to various embodiments.

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

[0017] Fig.10 is a block diagram illustrating components of a system for supporting network function virtualization (NFV) according to some exemplary embodiments.

[0018] Fig.11 Depicted are block diagrams showing components capable of reading instructions from a machine-readable medium or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some exemplary embodiments.

[0019] Fig.12 Exemplary procedures for practicing the various embodiments discussed herein are depicted. DETAILED DESCRIPTION

[0020] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so that the description of various embodiments will not be obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0021] The present disclosure relates to 5G NR Multiple Input Multiple Output (MIMO) enhancements on enhancements to multiple Transmission Reception Points (TRP) / panel transmissions.

[0022] In the present disclosure, resource allocation from multiple TRPs using a single downlink control information (DCI) is addressed for ultra-reliable and low latency (URLLC) use cases.

[0023] When multiple TRPs are used for data transmission for reliability purposes, in addition to the normal resource allocation type 1, one or more factors that allow the UE to split virtual resource blocks (VRBs) from different TRPs are indicated.

[0024] In order to provide spatial diversity to improve multi-TRP URLLC transmission, a scheme is envisioned in which information is sent from two TRPs to the UE in an FDM (frequency division multiplexing) manner, such as Figure 1 shown. Figure 1 2 methods of improving URLLC transmission using multiple TRPs are shown, on the left, 2 copies (RV0 and RV2) of the same transport block (TB) are transmitted from TRP-1 and TRP-2, on the right, a single copy of the TB is used, and some parts of the bits are transmitted from TRP1, and the rest of the bits are transmitted from TRP-2. In both cases, the Physical Downlink Control Channel (PDCCH) scheduling this is transmitted from TRP-1.

[0025] Resource Allocation Type 0 :

[0026] In a downlink resource allocation of type 0, the resource block allocation information includes a bitmap indicating the resource block group (RBG) allocated to the scheduled UE, where an RBG is a group of consecutive virtual resource blocks defined by a higher layer parameter rbg-Size, which is configured by the PDSCH-Config and the size of the carrier bandwidth part as defined in Table 1 below (based on Table 5.1.2.2.1-1 in 3GPP TS 38.214).

[0027] Table 1: Nominal RBG size P

[0028] Bandwidth portion size Cfg 1 Cfg 2 Cfg 3 Cfg 4 1–36 2 4 8 8 37–72 4 8 16 16 73–144 8 16 16 32 145–275 16 16 16 32

[0029] Size The total number of RBGs in the downlink bandwidth part i of the PRB (N RBG )Depend on Given, where

[0030] -The size of the first RBG is

[0031] -if Then the size of the last RBG is Otherwise, P.

[0032] - All other RBGs have size P.

[0033] The size of the bitmap is N RBG bits, where each RBG has one bitmap bit so that each RBG is addressable. The RBGs shall be indexed in order of increasing frequency and start with the lowest frequency in the carrier bandwidth portion. The order of the RBG bitmap is such that RBGs 0 to Mapped from the most significant bit (MSB) to the least significant bit (LSB). If the corresponding bit value in the bitmap is 1, the RBG is allocated to the UE, otherwise the RBG is not allocated to the UE.

[0034] To indicate resource allocations from TRP-1 and TRP-2, two separate bitmaps are indicated to the UE.To reduce the payload size of the DCI, a wider PRG size may be defined as shown in Tables Cfg-3 and Cfg-4 above.

[0035] Resource Allocation Type 1 :

[0036] In the downlink resource allocation of type 1, the resource block allocation information indicates to the scheduled UE that the resource block is A set of contiguously allocated non-interleaved or interleaved virtual resource blocks within the active bandwidth part of a PRB, except when DCI format 1_0 is decoded in any common search space, in which case if CORESET 0 is configured for the cell then the size of CORESET 0 shall be used, and if CORESET 0 is not configured for the cell then the size of the initial DL bandwidth part shall be used.

[0037] The downlink type 1 resource allocation field consists of the number of RBs corresponding to the starting virtual resource block (RB start ) and the length L of the resource block allocated continuously RBs The resource indicator value is defined as

[0038] if but

[0039]

[0040] otherwise

[0041]

[0042] Where L RBs ≥1 and should not exceed

[0043] When the DCI size of DCI format 1_0 in USS is derived from the size of DCI format 1_0 in CSS but applied to When another active BWP is reached, the Downlink Type 1 Resource Block Assignment field is replaced by the resource block corresponding to the starting resource block The resource indication value (RIV) and the length of the resource block allocated according to the virtual continuous allocation Composition, of which is given by:

[0044] - if CORESET 0 is configured for the cell, the size of CORESET 0;

[0045] - Size of the initial DL bandwidth portion if CORESET 0 is not configured for the cell.

[0046] The resource indicator value is defined as

[0047] if but

[0048]

[0049] otherwise

[0050]

[0051] where L′ RBs =L RBs / K,RB′ start =RB start / K and where L′ RBs Should not exceed

[0052] if Then K is the maximum value from the set {1,2,4,8} that satisfies Otherwise K=1.

[0053] In addition to RIV and L RBs In addition, a certain factor is signaled to the UE to indicate the fraction of consecutive VRBs allocated from TRP-1 and the fraction of remaining VRBs allocated from TRP-2. The factor α can be a value such as 1 / 2, 1 / 3, 1 / 4.

[0054] Specifically, the first Consecutive VRBs are associated with TRP-1 (the first TCI state), and the remaining Continuous VRBs are associated with TRP-2 (second TCI state).

[0055] The same principle can be extended to 3 TRPs. In addition to RIV and L RBs In addition, a factor is signaled to the UE to indicate the fraction of consecutive VRBs allocated from TRP-1, TRP-2 and the fraction of remaining VRBs allocated from TRP-3. The first factor α can be a value such as 1 / 2, 1 / 3, 1 / 4, and the second factor β can be a value from 1 / 3, 1 / 4.

[0056] Specifically, the first Consecutive VRBs are associated with TRP-1 (the first TCI state), and the second A group of consecutive VRBs are associated with TRP-2 (second TCI state), and the remaining consecutive VRBs are associated with TRP-3 (third TCI state).

[0057] In this case, the first TCI state, the second TCI state, and the third TCI state may simply be based on the TCI state ID.

[0058] Fig.12A flow chart of a method 1200 for ultra-reliable and low-latency (URLLC) transmission to a UE using multiple transmission reception points (TRPs) by an access node is shown, the method comprising the following steps. Step 1210 comprises allocating a resource block into a first portion and a second portion based on a resource indication value (RIV), a length of a consecutively allocated resource block (LRBS), and a fraction. Step 1220 comprises transmitting the first portion to the UE via a first transmission reception point (TRP1). Step 1230 comprises transmitting the second portion to the UE via a second transmission reception point (TRP2).

[0059] System and implementation

[0060] Figure 2 An exemplary architecture of a system 200 of a network according to various embodiments is shown. The following description is provided for an example system 200 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0061] like Figure 2 As shown, system 200 includes UE 201a and UE 201b (collectively referred to as "UE 201"). In this example, UE 201 is shown as a smart phone (e.g., a handheld touch screen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a consumer electronic device, a mobile phone, a smart phone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-vehicle entertainment (ICE) device, an instrument panel (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine electronic control unit (ECU), an electronic / engine electronic control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a networked or "smart" appliance, an MTC device, an M2M, an Internet of Things (IoT) device, etc.

[0062] In some embodiments, any of the UEs 201 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0063] UE 201 may be configured to connect, e.g., be communicatively coupled, to RAN 210. In an embodiment, RAN 210 may be an NG RAN or 5G RAN, an E-UTRAN, or a legacy RAN, such as UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to RAN 210 operating in an NR or 5G system 200, while the term "E-UTRAN" or the like may refer to RAN 210 operating in an LTE or 4G system 200. UE 201 utilizes connections (or channels) 203 and 204, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0064] In this example, connections 203 and 204 are shown as air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, the UE 201 may directly exchange communication data via the ProSe interface 205. The ProSe interface 205 may alternatively be referred to as a SL interface 205, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0065] UE 201b is shown configured to access AP 206 (also referred to as "WLAN node 206", "WLAN 206", "WLAN terminal 206", "WT 206", etc.) via connection 207. Connection 207 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 206 will include wireless fidelity. router. In this example, AP 206 is shown as being connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 201b, RAN 210, and AP 206 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 201b in the RRC_CONNECTED state being configured by RAN nodes 211a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 201b using WLAN radio resources (e.g., connection 207) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over connection 207. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0066] The RAN 210 includes one or more AN nodes or RAN nodes 211a and 211b (collectively referred to as "RAN node 211") that enable connections 203 and 204. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" and the like may refer to a RAN node 211 (e.g., a gNB) operating in an NR or 5G system 200, while the terms "E-UTRAN node" and the like may refer to a RAN node 211 (e.g., an eNB) operating in an LTE or 4G system 200. According to various embodiments, the RAN node 211 may be implemented as one or more of dedicated physical devices such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0067] In some embodiments, all or part of the RAN node 211 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splits, such as PDCP splits, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 211; MAC / PHY splits, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 211; or "lower PHY" splits, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes 211. This virtualization framework allows idle processor cores of the RAN node 211 to execute other virtualized applications. In some specific implementations, separate RAN nodes 211 may represent a single RAN node 211 connected to a separate F1 interface ( Figure 2 In these embodiments, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 5 ), and the gNB-CU may be operated by a server (not shown) located in the RAN 210 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 211 may be a next generation eNB (ng-eNB), which is a next generation eNB that provides E-UTRA user plane and control plane protocol terminals to the UE 201 and is connected to the 5GC (e.g., Figure 4 RAN node of CN 420).

[0068] In a V2X scenario, one or more of the RAN nodes 211 may be an RSU or act as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the road side that provides connectivity support to a passing vehicle UE 201 (vUE 201). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, etc. In addition or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication services. In addition or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0069] Any of the RAN nodes 211 may terminate the air interface protocol and may be the first point of contact for the UE 201. In some embodiments, any of the RAN nodes 211 may perform various logical functions of the RAN 210, 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.

[0070] In an embodiment, UE 201 may be configured to communicate with each other or with any of RAN nodes 211 over a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0071] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 211 to the UE 201, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0072] According to various embodiments, UE 201 and RAN node 211 communicate data (e.g., transmit data and receive data) through a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed frequency band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz frequency band.

[0073] To operate in the unlicensed spectrum, the UE 201 and the RAN node 211 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 201 and the RAN node 211 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0074] LBT is a mechanism by which equipment (e.g., UE 201, RAN node 211, etc.) senses a medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include a CCA that utilizes at least an ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an expected transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0075] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs use a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 201, AP 206, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid conflicts. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some specific implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS of LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0076] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0077] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL, and may handle activities related to RRC and NAS. Other serving cells are referred to as SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require UE 201 to undergo switching. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0078] The PDSCH carries user data and higher layer signaling to the UE 201. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It may also inform the UE 201 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 201b within a cell) may be performed at any of the RAN nodes 211 based on channel quality information fed back from any of the UEs 201. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UEs 201.

[0079] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

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

[0081] RAN nodes 211 may be configured to communicate with each other via interface 212. In embodiments where system 200 is an LTE system (eg, when CN 220 is a Figure 3 320 in the EPC 220), the interface 212 may be an X2 interface 212. The X2 interface may be defined between two or more RAN nodes 211 (e.g., two or more eNBs, etc.) connected to the EPC 220, and / or between two eNBs connected to the EPC 220. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful in-sequence delivery of PDCP PDUs from the SeNB to the UE 201 for user data; information about PDCP PDUs that were not delivered to the UE 201; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

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

[0083] RAN 210 is shown as being communicatively coupled to a core network—in this embodiment, communicatively coupled to a core network (CN) 220. The CN 220 may include a plurality of network elements 222 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 201) connected to the CN 220 via the RAN 210. The components of the CN 220 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of the CN 220 may be referred to as a network slice, and a logical instance of a portion of the CN 220 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 comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0084] Generally speaking, the application server 230 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 230 may also be configured to support one or more communication services for the UE 201 via the EPC 220 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.).

[0085] In an embodiment, CN 220 may be a 5GC (referred to as "5GC 220" or the like), and RAN 210 may be connected to CN 220 via an NG interface 213. In an embodiment, NG interface 213 may be divided into two parts: an NG user plane (NG-U) interface 214, which carries traffic data between RAN node 211 and UPF; and an S1 control plane (NG-C) interface 215, which is a signaling interface between RAN node 211 and AMF. Figure 4 An implementation of CN 220 as 5GC 220 is discussed in more detail.

[0086] In an embodiment, CN 220 may be a 5G CN (referred to as "5GC 220", etc.), while in other embodiments, CN 220 may be an EPC. In the case where CN 220 is an EPC (referred to as "EPC 220", etc.), RAN 210 may be connected to CN 220 via an S1 interface 213. In an embodiment, S1 interface 213 may be divided into two parts: an S1 user plane (S1-U) interface 214, which carries traffic data between RAN node 211 and S-GW; and an S1-MME interface 215, which is a signaling interface between RAN node 211 and MME. Figure 3 An exemplary architecture in which CN 220 is an EPC 220 is shown.

[0087] Figure 3 FIG. 3 shows an exemplary architecture of a system 300 including a first CN 320 according to various embodiments. In this example, the system 300 may implement the LTE standard, wherein the CN 320 is a Figure 2 In addition, UE 301 can communicate with Figure 2 The UE 201 is the same as or similar to the UE 201, and the E-UTRAN 310 may be Figure 2 The CN 320 may be a RAN that is the same as or similar to the RAN 210 of the mobile station, and may include the RAN node 211 discussed previously. The CN 320 may include an MME 321, an S-GW 322, a P-GW 323, an HSS 324, and an SGSN 325.

[0088] The MME 321 may be similar in function to the control plane of a conventional SGSN, and may implement MM functions to keep track of the current location of the UE 301. The MME 321 may perform various MM procedures to manage mobility aspects in access, such as gateway selection and tracking area list management. MM (also referred to as "EPS MM" or "EMM" in an E-UTRAN system) may refer to all applicable procedures, methods, data stores, etc. for maintaining knowledge of the current location of the UE 301, providing user identity confidentiality to users / subscribers, and / or performing other similar services. Each UE 301 and MME 321 may include an MM or EMM sublayer, and when the attachment procedure is successfully completed, an MM context may be established in the UE 301 and the MME 321. The MM context may be a data structure or database object that stores MM-related information of the UE 301. MME 321 may be coupled to HSS 324 via an S6a reference point, to SGSN 325 via an S3 reference point, and to S-GW 322 via an S11 reference point.

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

[0090] The HSS 324 may include a database for network users, which includes subscription-related information for supporting network entities in handling communication sessions. The EPC 320 may include one or several HSSs 324, depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc. For example, the HSS 324 may provide support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, etc. The S6a reference point between the HSS 324 and the MME 321 may enable the transfer of subscription and authentication data for authenticating / authorizing users to access the EPC 320 between the HSS 324 and the MME 321.

[0091] The S-GW 322 may terminate the S1 interface 213 towards the RAN 310 (at Figure 3 The S-GW 322 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies. The S11 reference point between the S-GW 322 and the MME 321 may provide a control plane between the MME 321 and the S-GW 322. The S-GW 322 may be coupled to the P-GW 323 via the S5 reference point.

[0092] The P-GW 323 may terminate the SGi interface toward the PDN 330. The P-GW 323 may communicate with the PDN 330 via the IP interface 225 (see, e.g., Figure 2 ) routes data packets between EPC 320 and external networks such as a network including application server 230 (alternatively referred to as "AF"). In an embodiment, P-GW 323 can communicate with the EPC 320 via IP communication interface 225 (see, e.g., Figure 2 ) is communicatively coupled to an application server ( Figure 2 Application server 230 or Figure 3The S5 reference point between the P-GW 323 and the S-GW 322 may provide user plane tunneling and tunnel management between the P-GW 323 and the S-GW 322. The S5 reference point may also be used for S-GW 322 relocation due to the mobility of the UE 301 and whether the S-GW 322 needs to be connected to a non-colocated P-GW 323 for the required PDN connectivity. The P-GW 323 may also include nodes for policy implementation and charging data collection, such as a PCEF (not shown). In addition, the SGi reference point between the P-GW 323 and the packet data network (PDN) 330 may be an operator-external public, private PDN, or an internal operator packet data network, such as for providing IMS services. The P-GW 323 may be coupled to the PCRF 326 via a Gx reference point.

[0093] PCRF 326 is a policy and charging control element of EPC 320. In a non-roaming scenario, there may be a single PCRF 326 in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of UE 301. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of UE 301: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in a visited public land mobile network (VPLMN). PCRF 326 may be communicatively coupled to application server 330 via P-GW 323. Application server 330 may signal PCRF 326 to indicate a new service flow and select appropriate QoS and charging parameters. PCRF 326 may configure the rule to a PCEF (not shown) with the appropriate TFT and QCI, which starts QoS and charging as specified by application server 330. The Gx reference point between PCRF 326 and P-GW 323 may allow for the transfer of QoS policies and charging rules from PCRF 326 to PCEF in P-GW 323. The Rx reference point may reside between PDN 330 (or "AF 330") and PCRF 326.

[0094] Figure 4The architecture of a system 400 including a second CN 420 according to various embodiments is shown. The system 400 is shown to include a UE 401, which may be the same or similar to the previously discussed UE 201 and UE 301; an (R) AN 410, which may be the same or similar to the previously discussed RAN 210 and RAN 310, and which may include the previously discussed RAN node 211; and a DN 403, which may be, for example, an operator service, Internet access, or a 3rd party service; and a 5GC 420. The 5GC 420 may include an AUSF 422; an AMF 421; an SMF 424; an NEF 423; a PCF 426; an NRF 425; an UDM 427; an AF 428; an UPF 402; and an NSSF 429.

[0095] UPF 402 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with DN 403, and a branch point to support multi-host PDU sessions. UPF 402 may also perform packet routing and forwarding, perform packet inspection, perform the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement) on the user plane, perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 402 may include an uplink classifier to support routing traffic flows to data networks. DN 403 may represent various network operator services, Internet access, or third-party services. DN 403 may include or be similar to the application server 230 discussed previously. UPF 402 may interact with SMF 424 via the N4 reference point between SMF 424 and UPF 402.

[0096] AUSF 422 may store data for authentication of UE 401 and handle authentication-related functions. AUSF 422 may facilitate a common authentication framework for various access types. AUSF 422 may communicate with AMF 421 via an N12 reference point between AMF 421 and AUSF 422; and may communicate with UDM 427 via an N13 reference point between UDM 427 and AUSF 422. In addition, AUSF 422 may present an interface based on Nausf services.

[0097] AMF 421 may be responsible for registration management (e.g., responsible for registering UE 401, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. AMF 421 may be the termination point of the N11 reference point between AMF 421 and SMF 424. AMF 421 may provide transport for SM messages between UE 401 and SMF 424, and act as a transparent proxy for routing SM messages. AMF 421 may also provide a transport for UE 401 and SMSF ( Figure 4 421). The AMF 421 may provide transport for SMS messages between the (R)AN 410 and the AMF 421 (not shown). The AMF 421 may act as a SEAF, which may include interaction with the AUSF 422 and the UE 401, receiving intermediate keys established as a result of the UE 401 authentication process. In the case of using USIM-based authentication, the AMF 421 may retrieve security material from the AUSF 422. The AMF 421 may also include an SCM function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF 421 may be a termination point for the RAN CP interface, which may include or be an N2 reference point between the (R)AN 410 and the AMF 421; and the AMF 421 may be a termination point for NAS (N1) signaling, and perform NAS encryption and integrity protection.

[0098] The AMF 421 may also support NAS signaling with the UE 401 over the N3 IWF interface. The N3 IWF may be used to provide access to untrusted entities. The N3 IWF may be the termination point for the N2 interface between the (R) AN 410 and the AMF 421 for the control plane, and may be the termination point for the N3 reference point between the (R) AN 410 and the UPF 402 for the user plane. Thus, the AMF 421 may process N2 signaling for PDU sessions and QoS from the SMF 424 and the AMF 421, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and perform QoS corresponding to N3 packet markings, taking into account QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 401 and the AMF 421 via the N1 reference point between the UE 401 and the AMF 421, and relay uplink and downlink user plane packets between the UE 401 and the UPF 402. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 401. The AMF 421 may present an interface based on the Namf service, and may be an N14 reference point between the two AMFs 421 and the AMF 421 and the 5G-EIR ( Figure 4 The termination point of the N17 reference point between the two (not shown).

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

[0100] AMF 421 may store one or more RM contexts for UE 401, each RM context being associated with a specific access to the network. An RM context may be a data structure, a database object, or the like, which indicates or stores, among other things, a registration status and a periodic update timer for each access type. AMF 421 may also store a 5GC MM context which may be the same or similar to the (E)MM context discussed previously. In various embodiments, AMF 421 may store CE mode B restriction parameters for UE 401 in an associated MM context or RM context. AMF 421 may also derive values ​​from usage setting parameters of the UE already stored in the UE context (and / or MM / RM context) when necessary.

[0101] The CM may be used to establish and release a signaling connection between the UE 401 and the AMF 421 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 401 and the CN 420, and includes a signaling connection between the UE and the AN (e.g., an RRC connection or a UE-N3IWF connection for non-3GPP access) and an N2 connection of the UE 401 between the AN (e.g., the RAN 410) and the AMF 421. The UE 401 may operate in one of two CM states (CM-IDLE mode or CM-CONNECTED mode). When the UE 401 operates in the CM-IDLE state / mode, the UE 401 may not have a NAS signaling connection established with the AMF 421 over the N1 interface, and there may be a (R)AN 410 signaling connection (e.g., N2 and / or N3 connection) for the UE 401. When the UE 401 operates in the CM-CONNECTED state / mode, the UE 401 may have a NAS signaling connection established with the AMF 421 through the N1 interface, and there may be a (R)AN 410 signaling connection (e.g., N2 and / or N3 connection) for the UE 401. Establishing an N2 connection between the (R)AN 410 and the AMF 421 may cause the UE 401 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the (R)AN 410 and the AMF 421 is released, the UE 401 may transition from the CM-CONNECTED mode to the CM-IDLE mode.

[0102] SMF 424 may be responsible for SM (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering of UPF to route traffic to the correct destination; terminating the interface toward the policy control function; control portion of policy enforcement and QoS; lawful interception (for SM events and interface with LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN via AMF over N2; and determining the SSC mode of the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 401 and a data network (DN) 403 identified by a data network name (DNN). The PDU session may be established upon request by UE 401, modified upon request by UE 401 and 5GC 420, and released upon request by UE 401 and 5GC 420 using NAS SM signaling exchanged between UE 401 and SMF 424 over the N1 reference point. Upon request from an application server, 5GC 420 may trigger a specific application in UE 401. In response to receiving a trigger message, UE 401 may deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 401. The identified applications in UE 401 may establish a PDU session to a specific DNN. SMF 424 may check whether the UE 401 request complies with user subscription information associated with UE 401. In this regard, SMF 424 may retrieve and / or request to receive update notifications about SMF 424 level subscription data from UDM 427.

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

[0104] NEF 423 may provide components for securely exposing services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, application functions (e.g., AF 428), edge computing or fog computing systems, etc. In such embodiments, NEF 423 may authenticate, authorize and / or restrict AF. NEF 423 may also convert information exchanged with AF 428 and information exchanged with internal network functions. For example, NEF 423 may convert between AF service identifiers and internal 5GC information. NEF 423 may also receive information from other network functions (NFs) based on their exposure capabilities. The information may be stored at NEF 423 as structured data or at a data storage NF using a standardized interface. The stored information may then be re-exposed to other NFs and AFs by NEF 423 and / or used for other purposes such as analysis. In addition, NEF 423 may present an interface based on Nnef services.

[0105] NRF 425 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information about discovered NF instances to NF instances. NRF 425 also maintains information about available NF instances and services supported by these instances. As used herein, the term "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, which may occur, for example, during the execution of a program code. In addition, NRF 425 may present an interface based on Nnrf services.

[0106] The PCF 426 may provide for control plane functions to enforce their policy rules, and may also support a unified policy framework for managing network behavior. The PCF 426 may also implement a FE to access subscription information related to policy decisions in the UDR of the UDM 427. The PCF 426 may communicate with the AMF 421 via the N15 reference point between the PCF 426 and the AMF 421, which may include the PCF 426 in the visited network and the AMF 421 in the case of a roaming scenario. The PCF 426 may communicate with the AF 428 via the N5 reference point between the PCF 426 and the AF 428; and communicate with the SMF 424 via the N7 reference point between the PCF 426 and the SMF 424. The system 400 and / or the CN 420 may also include an N24 reference point between the PCF 426 (in the home network) and the PCF 426 in the visited network. In addition, the PCF 426 may present an interface based on Npcf services.

[0107] UDM 427 may process subscription-related information to support network entities in handling communication sessions, and may store subscription data of UE 401. For example, subscription data may be transmitted between UDM 427 and AMF 421 via an N8 reference point between UDM 427 and AMF. UDM 427 may include two parts: application FE and UDR ( Figure 4 FE and UDR are not shown). UDR can store subscription data and policy data of UDM 427 and PCF 426, and / or structured data for exposure and application data of NEF 423 (including PFD for application detection, application request information of multiple UE 401). Nudr service-based interface can be presented by UDR 221 to allow UDM 427, PCF 426 and NEF 423 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete and subscribe to notifications of related data changes in UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different front ends may serve the same user. UDM-FE accesses subscription information stored in UDR, and performs authentication credential processing, user identification processing, access authorization, registration / mobility management and subscription management. UDR can interact with SMF 424 via the N10 reference point between UDM 427 and SMF 424. UDM 427 may also support SMS management, where SMS-FE implements similar application logic discussed previously.In addition, UDM 427 may present an interface based on Nudm services.

[0108] AF 428 can provide the influence of applications on traffic routing, provide access to NCE, and interact with the policy framework for policy control. NCE can be a mechanism that allows 5GC 420 and AF 428 to provide information to each other via NEF 423, which can be used for edge computing implementation. In such implementations, network operators and third-party services can be hosted near the UE 401 access point of the attachment to achieve effective service delivery through reduced end-to-end delay and load on the transmission network. For edge computing implementation, 5GC can select UPF 402 near UE 401 and perform traffic steering from UPF 402 to DN 403 via N6 interface. This can be based on UE subscription data, UE location and information provided by AF 428. In this way, AF 428 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 428 is considered a trusted entity, the network operator can allow AF 428 to interact directly with the relevant NF. In addition, AF 428 can present an interface based on Naf services.

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

[0110] As previously discussed, CN 420 may include SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to / from UE 401 to / from other entities, such as SMS-GMSC / IWMSC / SMS routers. SMS may also interact with AMF 421 and UDM 427 for notification procedures that UE 401 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 427 when UE 401 is available for SMS).

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

[0112] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Figure 4These interfaces and reference points are omitted. In one example, CN 420 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 321) and an AMF 421, so as to enable interworking between CN 420 and CN 320. Other example interfaces / reference points may include an interface based on N5g-EIR services presented by 5G-EIR, an N27 reference point between an NRF in a visited network and an NRF in a home network; and an N31 reference point between an NSSF in a visited network and an NSSF in a home network.

[0113] Figure 5 An example of infrastructure equipment 500 according to various embodiments is shown. Infrastructure equipment 500 (or "system 500") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 211 and / or AP 206 shown and described previously), an application server 230, and / or any other element / device discussed herein. In other examples, system 500 can be implemented in or by a UE.

[0114] System 500 includes: application circuit 505, baseband circuit 510, one or more radio front end modules (RFEM) 515, memory circuit 520, power management integrated circuit (PMIC) 525, power tee circuit 530, network controller circuit 535, network interface connector 540, satellite positioning circuit 545 and user interface 550. In some embodiments, device 500 may include additional elements such as, for example, memory / storage, display, camera, sensor or input / output (I / O) interface. In other embodiments, the following components may be included in more than one device. For example, the circuit may be included separately in more than one device for CRAN, vBBU or other similar implementations.

[0115] Application circuit 505 includes circuits such as, but not limited to, one or more processors (processor cores), cache memory, and one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I 2C or general programmable serial interface module, real-time clock (RTC), timer-counter including interval timer and watchdog timer, general input / output (I / O or IO), memory card controller such as secure digital (SD) multimedia card (MMC) or similar products, universal serial bus (USB) interface, mobile industry processor interface (MIPI) interface and joint test access group (JTAG) test access port. The processor (or core) of application circuit 505 can be coupled with memory / storage element or can include memory / storage element, and can be configured to execute instructions stored in memory / storage device to enable various applications or operating systems to run on system 500. In some embodiments, memory / storage element can be on-chip memory circuit, which can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

[0116] The processor of the application circuit 505 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 Acorn RISC Machine (ARM) 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 any suitable combination thereof. In some embodiments, the application circuit 505 may include or may be a dedicated processor / controller for operating according to various embodiments herein. As an example, the processor of the application circuit 505 may include one or more Intel FPGAs. or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium(TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some embodiments, system 500 may not utilize application circuit 505, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0117] In some specific implementations, the application circuit 505 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, 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), high capacity PLDs (HCPLDs), etc.; ASICs, such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuitry of the application circuit 505 may include logic blocks or logic structures, and other interconnected resources that may be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of the application circuit 505 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in a lookup table (LUT), etc.

[0118] Baseband circuit 510 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Figure 7 The various hardware electronic components of baseband circuit 510 are discussed.

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

[0120] The radio front end module (RFEM) 515 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Figure 7Antenna array 711), and the RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 515 that combines both millimeter wave antennas and sub-millimeter waves.

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

[0122] The PMIC 525 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 530 may provide power extracted from a network cable to provide both power and data connections for the infrastructure equipment 500 using a single cable.

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

[0124] The positioning circuit 545 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a global satellite navigation system (GNSS). Examples of navigation satellite constellations (or 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), etc. for navigation), etc. The positioning circuit 545 includes 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 embodiments, the positioning circuit 545 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 545 may also be part of or interact with the baseband circuit 510 and / or RFEM 515 to communicate with nodes and components of the positioning network. The positioning circuit 545 may also provide location data and / or time data to the application circuit 505, which may use the data to synchronize operations with various infrastructure (e.g., RAN node 211, etc.), etc.

[0125] Figure 5 The components shown may communicate with each other using interface circuitry that may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems may be included, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

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

[0127] Application circuit 605 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and LDO, interrupt controller, serial interface (such as SPI), I 2 C or general programmable serial interface module, RTC, timer (including interval timer and watchdog timer), general I / O, memory card controller (such as SD MMC or similar controller), USB interface, MIPI interface and JTAG test access port. The processor (or core) of the application circuit 605 can be coupled with or can include a memory / storage element, and can be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 600. In some embodiments, the memory / storage element can be an on-chip memory circuit, which can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

[0128] The processor of the application circuit 505 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuit 505 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0129] As an example, the processor of the application circuit 605 may include a processor based on Architecture TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA The processor of application circuit 605 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia Applications Platform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 605 can be part of a system on a chip (SoC), in which the application circuit 605 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

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

[0131] Baseband circuit 610 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Figure 7 The various hardware electronic components of baseband circuit 610 are discussed.

[0132] The RFEM 615 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Figure 7 Antenna array 711), and the RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 615 that combines both millimeter wave antennas and sub-millimeter waves.

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

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

[0135] The platform 600 may further include an interface circuit (not shown) for connecting external devices to the platform 600. External devices connected to the platform 600 via the interface circuit include a sensor circuit 621 and an electromechanical component (EMC) 622, and a removable memory device coupled to a removable memory circuit 623.

[0136] Sensor circuitry 621 comprises a device, module, or subsystem that is intended to detect events or changes in its environment, and to send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a microelectromechanical system (MEMS) or a nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0137] The EMC 622 includes devices, modules or subsystems that are intended to enable the platform 600 to change its state, position and / or orientation or to move or control a mechanism or (sub) system. In addition, the EMC 622 may be configured to generate messages / signaling and send messages / signaling to other components of the platform 600 to indicate the current state of the EMC 622. Examples of the EMC 622 include one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks and / or other similar electromechanical components. In an embodiment, the platform 600 is configured to operate one or more EMCs 622 based on one or more capture events and / or instructions or control signals received from a service provider and / or various clients.

[0138] In some specific implementations, the interface circuit may connect the platform 600 to the positioning circuit 645. The positioning circuit 645 includes a circuit for receiving and decoding signals transmitted / broadcasted by the positioning network of the GNSS. Examples of navigation satellite constellations (or GNSS) may include the GPS of the United States, the GLONASS of Russia, the Galileo system of the European Union, the Beidou navigation satellite system of China, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, QZSS of Japan, DORIS of France, etc.), etc. The positioning circuit 645 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communication) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 645 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 645 may also be part of the baseband circuit 510 and / or the RFEM 615 or interact with it to communicate with nodes and components of the positioning network. Positioning circuitry 645 may also provide position data and / or time data to application circuitry 605, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations) for use in turn-by-turn navigation applications, etc.

[0139] In some implementations, the interface circuit may connect the platform 600 with a near field communication (NFC) circuit 640. The NFC circuit 640 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, where a magnetic field is sensed to enable communication between the NFC circuit 640 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 600. The NFC circuit 640 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to the NFC circuit 640 by executing an NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 640, or initiate data transfer between the NFC circuit 640 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) proximate to the platform 600.

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

[0141] A power management integrated circuit (PMIC) 625 (also referred to as “power management circuit 625”) may manage power provided to various components of the platform 600. Specifically, the PMIC 625 may control power selection, voltage scaling, battery charging, or DC-DC conversion relative to the baseband circuit 610. When the platform 600 is capable of being powered by a battery 630, for example, when the device is included in a UE 201, 301, 401, the PMIC 625 may be generally included.

[0142] In some embodiments, the PMIC 625 may control or otherwise be part of various power saving mechanisms of the platform 600. For example, if the platform 600 is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the platform 600 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 600 may transition to the RRC_Idle state, in which the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 600 enters a very low power state and performs paging, in which the device wakes up periodically again to listen to the network and then powers off again. The platform 600 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

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

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

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

[0146] The user interface circuit 650 includes various input / output (I / O) devices present in or connected to the platform 600, and includes one or more user interfaces designed to implement user interaction with the platform 600 and / or a peripheral component interface designed to implement interaction with the peripheral components of the platform 600. The user interface circuit 650 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, 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, a headset, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, including, among other things, one or more simple visual outputs / indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where outputs of characters, graphics, multimedia objects, etc. are generated or produced by the operation of the platform 600. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, the sensor circuitry 621 may be used as an input device circuitry (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used as output device circuitry (e.g., an actuator for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. The peripheral component interfaces may include, but are not limited to, non-volatile memory ports, USB ports, audio jacks, power interfaces, etc.

[0147] Although not shown, the components of platform 600 may communicate with each other using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX may be a proprietary bus / IX, such as used in SoC-based systems. Other bus / IX systems, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0148] Figure 7 7 and 7. Exemplary components of a baseband circuit 710 and a radio front end module (RFEM) 715 are shown according to various embodiments. The baseband circuit 710 corresponds to Figure 5 The baseband circuit 510 and Figure 6 The baseband circuit 610. RFEM 715 respectively corresponds to Figure 5 RFEM 515 and Figure 6 RFEM 615. As shown, RFEM 715 may include radio frequency (RF) circuit 706, front end module (FEM) circuit 708, and antenna array 711 coupled together at least as shown.

[0149] The baseband circuit 710 includes circuits and / or control logic components that are configured to execute various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuit 706. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 710 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 710 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments. The baseband circuit 710 is configured to process baseband signals received from the receive signal path of the RF circuit 706 and generate baseband signals for the transmit signal path of the RF circuit 706. The baseband circuit 710 is configured to communicate with the application circuit 505 / 605 (see Figure 5 and Figure 6 ) to generate and process baseband signals and control the operation of RF circuit 706. Baseband circuit 710 may handle various radio control functions.

[0150] The aforementioned circuits and / or control logic components of the baseband circuit 710 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 704A, a 4G / LTE baseband processor 704B, a 5G / NR baseband processor 704C, or some other baseband processors 704D for other existing generations, generations under development or generations to be developed in the future (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functions of the baseband processors 704A-704D may be included in a module stored in the memory 704G and executed via a central processing unit (CPU) 704E. In other embodiments, some or all of the functions of the baseband processors 704A to 704D may be provided as a hardware accelerator (e.g., FPGA, ASIC, etc.) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In various embodiments, the memory 704G may store program code of a real-time OS (RTOS), which, when executed by the CPU 704E (or other baseband processor), will enable the CPU 704E (or other baseband processor) to manage resources of the baseband circuit 710, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) provided TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-Time Executive (VRTX) provided by Express Provided by ThreadX TM ,Depend on FreeRTOS and REX OS provided by OpenKernel (OK) OKL4 provided, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuit 710 includes one or more audio digital signal processors (DSPs) 704F. The audio DSP 704F includes elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0151] In some embodiments, each of processors 704A-704E includes a corresponding memory interface to send data to / receive data from memory 704G. Baseband circuit 710 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to baseband circuit 710; an interface for sending data to / receiving data from a memory external to the baseband circuit; Figures 5 and 6An application circuit interface for sending data to / receiving data from the application circuit 505 / 605; Figure 7 RF circuit 706 to send data / receive data from the RF circuit RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / receiving power or control signals from the PMIC 625.

[0152] In an alternative embodiment (which can be combined with the above embodiment), the baseband circuit 710 includes one or more digital baseband systems, which are coupled to each other and to the CPU subsystem, the audio subsystem and the interface subsystem via an interconnect subsystem. The digital baseband subsystem can also be coupled to the digital baseband interface and the mixed signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 710 may include a protocol processing circuit with one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit and / or the radio frequency circuit (e.g., the radio front end module 715).

[0153] although Figure 7Not shown, but in some embodiments, the baseband circuit 710 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuit") to operate one or more wireless communication protocols and various processing devices to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuit operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuit 710 and / or the RF circuit 706 are part of a millimeter wave communication circuit or some other suitable cellular communication circuit, the protocol processing circuit may operate LTE protocol entities and / or 5G / NR protocol entities. In the first example, the protocol processing circuit will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuit 710 and / or the RF circuit 706 are part of a Wi-Fi communication system, the protocol processing circuit may operate one or more IEEE-based protocols. In the second example, the protocol processing circuit will operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuit may include one or more memory structures (e.g., 704G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuit 710 may also support radio communications of more than one wireless protocol.

[0154] The various hardware elements of the baseband circuit 710 discussed herein may be implemented as, for example, a solder-in substrate including one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuit 710 may be appropriately combined in a single chip or a single chipset, or disposed on the same circuit board. In another example, some or all of the components of the baseband circuit 710 and the RF circuit 706 may be implemented together, such as, for example, a system on a chip (SoC) or a system-level package (SiP). In another example, some or all of the components of the baseband circuit 710 may be implemented as a separate SoC communicatively coupled to the RF circuit 706 (or multiple instances of the RF circuit 706). In yet another example, some or all of the components of the baseband circuit 710 and the application circuit 505 / 605 may be implemented together as a separate SoC (e.g., a "multi-chip package") mounted to the same circuit board.

[0155] In some embodiments, the baseband circuit 710 can provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 710 can support communications with E-UTRAN or other WMANs, WLANs, WPANs. Embodiments in which the baseband circuit 710 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuits.

[0156] The RF circuit 706 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, the RF circuit 706 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 706 may include a receive signal path, which may include circuits for down-converting RF signals received from the FEM circuit 708 and providing baseband signals to the baseband circuit 710. The RF circuit 706 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by the baseband circuit 710 and providing an RF output signal for transmission to the FEM circuit 708.

[0157] In some embodiments, the receive signal path of the RF circuit 706 may include a mixer circuit 706a, an amplifier circuit 706b, and a filter circuit 706c. In some embodiments, the transmit signal path of the RF circuit 706 may include a filter circuit 706c and a mixer circuit 706a. The RF circuit 706 may also include a synthesizer circuit 706d, which is used to synthesize the frequency used by the mixer circuit 706a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 706a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 708 based on the synthesized frequency provided by the synthesizer circuit 706d. The amplifier circuit 706b may be configured to amplify the down-converted signal, and the filter circuit 706c may be a low pass filter (LPF) or a band pass filter (BPF), which is configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 710 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 706a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0158] In some embodiments, mixer circuit 706a of the transmit signal path may be configured to up-convert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 706d to generate an RF output signal for FEM circuit 708. The baseband signal may be provided by baseband circuit 710 and may be filtered by filter circuit 706c.

[0159] In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may include two or more mixers and may be arranged for orthogonal down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may be configured for superheterodyne operation.

[0160] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 706 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 710 may include a digital baseband interface to communicate with the RF circuit 706.

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

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

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

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

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

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

[0167] The FEM circuitry 708 may include a receive signal path that may include circuitry configured to operate on RF signals received from the antenna array 711, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 706 for further processing. The FEM circuitry 708 may also include a transmit signal path that may include circuitry configured to amplify signals provided for transmission by the RF circuitry 706 for transmission by one or more antenna elements in the antenna array 711. In various embodiments, amplification by the transmit or receive signal paths may be accomplished only in the RF circuitry 706, only in the FEM circuitry 708, or in both the RF circuitry 706 and the FEM circuitry 708.

[0168] In some embodiments, the FEM circuit 708 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 708 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 708 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 706). The transmit signal path of the FEM circuit 708 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by the RF circuit 706), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 711.

[0169] The antenna array 711 includes one or more antenna elements, each of which is configured to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. For example, the digital baseband signal provided by the baseband circuit 710 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of the antenna array 711 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, directional, or a combination thereof. The antenna elements may be formed into a variety of arrangements as known and / or discussed herein. The antenna array 711 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 711 may be formed as a patch of metal foil of various shapes (e.g., a patch antenna) and may be coupled to the RF circuit 706 and / or the FEM circuit 708 using a metal transmission line or the like.

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

[0171] Figure 8 Various protocol functions that can be implemented in a wireless communication device according to various embodiments are shown. Specifically, Figure 8 An arrangement 800 is included to show the interconnection between various protocol layers / entities. Various protocol layers / entities operating in conjunction with 5G / NR system standards and LTE system standards are provided. Figure 8The following description, but Figure 8 Some or all aspects of the present invention may also be applicable to other wireless communication network systems.

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

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

[0174] An instance of MAC 820 may process requests from and provide indications to an instance of RLC 830 via one or more MAC-SAPs 825. These requests and indications transmitted via MAC-SAP 825 may include one or more logical channels. MAC 820 may perform mapping between logical channels and transport channels, multiplexing MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 810 via transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 810 via transport channels to one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.

[0175] An instance of RLC 830 may process requests from an instance of PDCP 840 and provide indications thereto via one or more radio link control service access points (RLC-SAPs) 835. These requests and indications transmitted via RLC-SAPs 835 may include one or more logical channels. RLC 830 may operate in a variety of operating modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC 830 may perform transmission of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 830 may also perform resegmentation of RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

[0176] An instance of PDCP 840 may process requests from an instance of RRC 855 and / or an instance of SDAP 847 via one or more Packet Data Convergence Protocol Service Points (PDCP-SAP) 845 and provide indications thereto. These requests and indications transmitted via PDCP-SAP 845 may include one or more radio bearers. PDCP 840 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform in-order delivery of upper layer PDUs when lower layers are reestablished, eliminate duplication of lower layers when reestablishing lower layer SDUs for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0177] An instance of SDAP 847 may process requests from one or more higher layer protocol entities via one or more SDAP-SAPs 849 and provide indications thereto. These requests and indications transmitted via SDAP-SAPs 849 may include one or more QoS flows. SDAP 847 may map QoS flows to DRBs and vice versa, and may also mark QFIs in DL and UL packets. A single SDAP entity 847 may be configured for a separate PDU session. In the UL direction, NG-RAN 210 may control the mapping of QoS flows to DRBs in two different ways (reflective mapping or explicit mapping). For reflective mapping, SDAP 847 of UE 201 may monitor the QFI of the DL packets of each DRB, and may apply the same mapping to packets flowing in the UL direction. For DRBs, SDAP 847 of UE 201 may map UL packets belonging to a QoS flow corresponding to the QoS flow ID and PDU session observed in the DL packets of the DRB. To implement the reflective mapping, the NG-RAN 410 may mark the DL packets with a QoS flow ID over the Uu interface. The explicit mapping may involve the RRC 855 configuring the SDAP 847 with explicit mapping rules of QoS flows to DRBs, which may be stored and followed by the SDAP 847. In an embodiment, the SDAP 847 may be used only in NR implementations and may not be used in LTE implementations.

[0178] The RRC 855 may configure aspects of one or more protocol layers, which may include one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840, and SDAP 847, via one or more Management Service Access Points (M-SAPs). In an embodiment, an instance of the RRC 855 may process requests from one or more NAS entities 857 and provide instructions thereto via one or more RRC-SAPs 856. The main services and functions of the RRC 855 may include broadcasting of system information (e.g., included in a MIB or SIB related to NAS), broadcasting of system information related to the access stratum (AS), paging, establishment, maintenance, and release of an RRC connection between the UE 201 and the RAN 210 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. These MIBs and SIBs may include one or more IEs, each of which may include a separate data field or data structure.

[0179] NAS 857 may form the highest layer of the control plane between UE 201 and AMF 421. NAS 857 may support mobility and session management procedures of UE 201 to establish and maintain an IP connection between UE 201 and P-GW in the LTE system.

[0180] According to various embodiments, one or more protocol entities of arrangement 800 may be implemented in UE 201, RAN node 211, AMF 421 in NR implementation or MME 321 in LTE implementation, UPF 402 in NR implementation or S-GW 322 and P-GW 323 in LTE implementation, etc., for control plane or user plane communication protocol stacks between the aforementioned devices. In such embodiments, one or more protocol entities that may be implemented in one or more of UE 201, gNB 211, AMF 421, etc. may communicate with corresponding peer protocol entities that may be implemented in or on another device (using services of corresponding lower layer protocol entities to perform such communication). In some embodiments, the gNB-CU of gNB 211 may host the RRC 855, SDAP 847, and PDCP 840 of the gNB that control operations of one or more gNB-DUs, and the gNB-DUs of gNB 211 may each host the RLC 830, MAC 820, and PHY 810 of gNB 211.

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

[0182] In a NR specific implementation, AP 863 can be an NG application protocol layer (NGAP or NG-AP) 863 for the NG interface 213 defined between the NG-RAN node 211 and the AMF 421, or AP 863 can be an Xn application protocol layer (XnAP or Xn-AP) 863 for the Xn interface 212 defined between two or more RAN nodes 211.

[0183] The NG-AP 863 may support the functionality of the NG interface 213 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN node 211 and the AMF 421. The NG-AP 863 services may include two groups: UE-associated services (e.g., services related to the UE 201) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 211 and the AMF 421). These services may include functions including, but not limited to: a paging function for sending a paging request to the NG-RAN node 211 involved in a specific paging area; a UE context management function for allowing the AMF 421 to establish, modify and / or release the UE context in the AMF 421 and the NG-RAN node 211; a mobility function for the UE 201 in ECM-CONNECTED mode, for intra-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signaling transport function for transmitting or rerouting NAS messages between the UE 201 and the AMF 421; a NAS node selection function for determining the association between the AMF 421 and the UE 201; an NG interface management function for setting up the NG interface and monitoring errors through the NG interface; a warning message sending function for providing a means to transmit a warning message via the NG interface or to cancel an ongoing warning message broadcast; a NAS signaling transport function for transmitting or rerouting NAS messages between the UE 201 and the AMF 421; a NAS node selection function for determining the association between the AMF 421 and the UE 201; a ... 220 A configuration transmission function for requesting and transmitting RAN configuration information (eg, SON information, performance measurement (PM) data, etc.) between two RAN nodes 211; and / or other similar functions.

[0184] The XnAP 863 may support the functions of the Xn interface 212 and may include XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may include procedures for handling UE mobility within the NG RAN 211 (or E-UTRAN 310), such as handover preparation and cancellation procedures, SN state transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, procedures related to dual connectivity, etc. The XnAP global procedures may include procedures that are not related to a specific UE 201, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, etc.

[0185] In an LTE specific implementation, AP 863 can be an S1 application protocol layer (S1-AP) 863 for the S1 interface 213 defined between the E-UTRAN node 211 and the MME, or AP 863 can be an X2 application protocol layer (X2AP or X2-AP) 863 for the X2 interface 212 defined between two or more E-UTRAN nodes 211.

[0186] The S1 application protocol layer (S1-AP) 863 may support the functionality of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include an S1-AP EP. The S1-AP EP may be an interaction unit between the E-UTRAN node 211 and the MME 321 within the LTE CN 220. The S1-AP 863 services may include two groups: UE-associated services and non-UE-associated services. The functions performed by these services include, but are not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration transmission.

[0187] The X2AP 863 may support the functions of the X2 interface 212 and may include an X2AP basic mobility procedure and an X2AP global procedure. The X2AP basic mobility procedure may include a procedure for handling UE mobility within the E-UTRAN 220, such as a handover preparation and cancellation procedure, an SN state transfer procedure, a UE context retrieval and a UE context release procedure, a RAN paging procedure, a procedure related to dual connectivity, etc. The X2AP global procedure may include a procedure that is not related to a specific UE 201, such as an X2 interface setup and reset procedure, a load indication procedure, an error indication procedure, a cell activation procedure, etc.

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

[0189] In a second example, the user plane protocol stack may include SDAP 847, 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 UE 201, RAN node 211, and UPF 402 in NR implementation, or communication between S-GW 322 and P-GW 323 in LTE implementation. In this example, the upper layer 851 may be built on top of SDAP 847 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 852, a general packet radio service (GPRS) tunneling protocol layer (GTP-U) 853 for the user plane, and a user plane PDU layer (UP PDU) 863.

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

[0191] 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 a packet in any of the IPv4, IPv6 or PPP formats. UDP / IP 852 may provide a checksum for data integrity, a port number for addressing different functions at the source and destination, and encryption and authentication of selected data flows. The RAN node 211 and the S-GW 322 may utilize the S1-U interface to exchange user plane data via a protocol stack including an L1 layer (e.g., PHY 810), an L2 layer (e.g., MAC 820, RLC 830, PDCP 840 and / or SDAP 847), a UDP / IP layer 852, and a GTP-U 853. The S-GW 322 and the P-GW 323 may utilize the S5 / S8a interface to exchange user plane data via a protocol stack including an L1 layer, an L2 layer, a UDP / IP layer 852, and a GTP-U 853. As previously discussed, the NAS protocol may support mobility of UE 201 and session management procedures to establish and maintain an IP connection between UE 201 and P-GW 323 .

[0192] In addition, despite Figure 8Not shown, but an application layer may exist above the AP 863 and / or transport network layer 854. The application layer may be a layer where a user of the UE 201, RAN node 211, or other network element interacts with a software application, for example, executed by the application circuitry 505 or the application circuitry 605, respectively. The application layer may also provide one or more interfaces for the software application to interact with the communication system of the UE 201 or RAN node 211, such as the baseband circuitry 710. In some implementations, the IP layer and / or the application layer may provide functionality that is the same or similar to layers 5 to 7 of the Open Systems Interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).

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

[0194] As used herein, the terms "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the concrete occurrence of an object, which may occur, for example, during the execution of program code. A network instance may refer to information identifying a domain, which may be used for traffic detection and routing in different IP domains or in the case of overlapping IP addresses. A network slice instance may refer to a set of network function (NF) instances and the resources (e.g., computing, storage, and networking resources) required to deploy a network slice.

[0195] Regarding 5G systems (see e.g. Figure 4), a network slice always includes a RAN part and a CN part. Support for network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. The network can implement different network slices by scheduling and also by providing different L1 / L2 configurations. If NAS has provided an RRC message, UE 401 provides auxiliary information for network slice selection in an appropriate RRC message. Although the network can support a large number of slices, the UE does not need to support more than 8 slices at the same time.

[0196] The network slice may include the CN 420 control plane and user plane NF, the NG-RAN 410 in the serving PLMN, and the N3IWF function in the serving PLMN. Each network slice may have a different S-NSSAI and / or may have a different SST. The NSSAI includes one or more S-NSSAIs, and each network slice is uniquely identified by the S-NSSAI. The network slice may be different for supported features and network function optimizations, and / or multiple network slice instances may deliver the same service / function, but different for different groups of UE 401 (e.g., enterprise users). For example, each network slice may deliver different committed services and / or may be dedicated to a specific customer or enterprise. In this example, each network slice may have a different S-NSSAI with the same SST but with a different slice differentiator. In addition, a single UE may be served simultaneously with one or more network slice instances via a 5G AN and be associated with eight different S-NSSAIs. In addition, an AMF 421 instance serving a single UE 401 may belong to each network slice instance serving the UE.

[0197] Network slicing in NG-RAN 410 involves RAN slice awareness. RAN slice awareness includes differentiated handling of traffic for different network slices that have been pre-configured. Slice awareness in NG-RAN 410 is introduced at the PDU session level by indicating the S-NSSAI corresponding to the PDU session in all signaling including PDU session resource information. How NG-RAN 410 supports slice activation in terms of NG-RAN functions (e.g., a set of network functions including each slice) is implementation specific. NG-RAN 410 selects the RAN portion of the network slice using assistance information provided by UE 401 or 5GC 420 that explicitly identifies one or more of the pre-configured network slices in the PLMN. NG-RAN 410 also supports resource management and policy enforcement between slices per SLA. A single NG-RAN node can support multiple slices, and NG-RAN 410 can also apply appropriate RRM policies for SLAs in appropriate locations to each supported slice. NG-RAN 410 can also support QoS differentiation within a slice.

[0198] If available, the NG-RAN 410 may also use UE assistance information for selecting an AMF 421 during the initial attach. The NG-RAN 410 uses the assistance information for routing the initial NAS to the AMF 421. If the NG-RAN 410 is not able to select the AMF 421 using the assistance information, or the UE 401 does not provide any such information, the NG-RAN 410 sends the NAS signaling to the default AMF 421, which may be in the pool of AMFs 421. For subsequent access, the UE 401 provides the temp ID assigned to the UE 401 by the 5GC 420 to enable the NG-RAN 410 to route the NAS message to the appropriate AMF 421, as long as the temp ID is valid. The NG-RAN 410 knows and can reach the AMF 421 associated with the temp ID. Otherwise, the method for initial attach applies.

[0199] NG-RAN 410 supports resource isolation between slices. NG-RAN 410 resource isolation can be achieved through RRM policies and protection mechanisms, which should avoid the shortage of shared resources in the case where one slice disrupts the service level agreement of another slice. In some implementations, NG-RAN 410 resources can be fully assigned to a slice. How NG-RAN 410 supports resource isolation is implementation-dependent.

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

[0201] UE 401 may be associated with multiple network slices simultaneously. In the case where UE 401 is associated with multiple slices simultaneously, only one signaling connection is maintained and for intra-frequency cell reselection, UE 401 attempts to camp on the best cell. For inter-frequency cell reselection, dedicated priorities may be used to control the frequency that UE 401 camps on. 5GC 420 will verify that UE 401 has the right to access the network slice. Prior to receiving the Initial Context Setup Request message, NG-RAN 410 may be allowed to apply some temporary / local policies based on the awareness of the specific slice that UE 401 is requesting access to. During the Initial Context Setup, NG-RAN 410 is informed of the slice for which resources are being requested.

[0202] NFV architecture and infrastructure can be used to virtualize one or more NFs onto physical resources including a combination of industry standard server hardware, storage hardware or switches (alternatively performed by proprietary hardware). In other words, the NFV system can be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0203] Fig.10 1000 is a block diagram illustrating components of a NFV-enabled system 1000 according to some exemplary embodiments. System 1000 is shown to include VIM 1002, NFVI 1004, VNFM 1006, VNF 1008, EM 1010, NFVO 1012, and NM 1014.

[0204] The VIM 1002 manages resources of the NFVI 1004. The NFVI 1004 may include physical or virtual resources and applications (including a hypervisor) for executing the system 1000. The VIM 1002 may utilize the NFVI 1004 to manage the lifecycle of virtual resources (e.g., creation, maintenance, and teardown of VMs associated with one or more physical resources), track VM instances, track performance, failures, and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

[0205] The VNFM 1006 may manage the VNF 1008. The VNF 1008 may be used to perform EPC components / functions. The VNFM 1006 may manage the lifecycle of the VNF 1008 and track the performance, failures, and security of the virtual aspects of the VNF 1008. The EM 1010 may track the performance, failures, and security of the functional aspects of the VNF 1008. The tracking data from the VNFM 1006 and the EM 1010 may include, for example, PM data used by the VIM 1002 or the NFVI 1004. The VNFM 1006 and the EM 1010 may both scale up / down the number of VNFs of the system 1000.

[0206] The NFVO 1012 may coordinate, authorize, release, and engage the resources of the NFVI 1004 in order to provide the requested service (e.g., to execute an EPC function, component, or slice). The NM 1014 may provide an end-user functional package responsible for network management, which may include network elements with VNFs, non-virtualized network functions, or both (management of the VNFs may occur via the EM 1010).

[0207] Fig.11is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Fig.11 A schematic diagram of hardware resources 1100 is shown, including one or more processors (or processor cores) 1110, one or more memory / storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled via a bus 1140. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1102 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1100.

[0208] Processor 1110 may include, for example, processor 1112 and processor 1114. Processor 1110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a 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.

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

[0210] The communication resources 1130 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1104 or one or more databases 1106 via the network 1108. For example, the communication resources 1130 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

[0211] The instructions 1150 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1110 to perform any one or more of the methodologies discussed herein. The instructions 1150 may reside in whole or in part in at least one of the processor 1110 (e.g., in a cache memory of the processor), the memory / storage device 1120, or any suitable combination thereof. In addition, any portion of the instructions 1150 may be transmitted to the hardware resources 1100 from any combination of the peripheral device 1104 or the database 1106. Thus, the memory of the processor 1110, the memory / storage device 1120, the peripheral device 1104, and the database 1106 are examples of computer-readable and machine-readable media.

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

[0213] Example

[0214] Embodiment 1 may include a method for performing PDSCH resource allocation from a first TCI state (first TRP) and a second TCI state (second TRP) using RIV, LPRB, and factor α.

[0215] Embodiment 2 may include a method according to embodiment 1 or some other embodiments herein, wherein the PDSCH is a single TB, a portion of which is transmitted from a first TRP and the remainder is transmitted from a second TRP.

[0216] Embodiment 3 may include a method according to embodiment 1 or some other embodiments herein, wherein the PDSCH is two copies of a TB, a first copy or redundant version is transmitted from a first TRP, and the remaining copies or redundant versions are transmitted from a second TRP.

[0217] Embodiment 4 may include the method of embodiment 1, wherein the RIV, LPRB, and factor α are used to approximately separate the fraction of αVRB from TRP-2 and the remainder from TRP-1.

[0218] Embodiment 5 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Embodiments 1 to 4, or any other method or process described herein.

[0219] Embodiment 6 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described or related to any one of Embodiments 1 to 4 or any other method or process described herein.

[0220] Embodiment 7 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of a method as described or related to any of Embodiments 1 to 4, or any other method or process described herein.

[0221] Embodiment 8 may include methods, techniques or processes as described or related to any one of Embodiments 1 to 4, or parts or components thereof.

[0222] Embodiment 9 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any one of Embodiments 1 to 4, or a portion thereof.

[0223] Embodiment 10 may include a signal as described or related to any one of embodiments 1 to 4, or a portion or component thereof.

[0224] Embodiment 11 may include signals in a wireless network as shown and described herein.

[0225] Embodiment 12 may include a method of communicating in a wireless network as shown and described herein.

[0226] Embodiment 13 may include a system for providing wireless communications as shown and described herein.

[0227] Embodiment 14 may include an apparatus for providing wireless communications as shown and described herein.

[0228] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be acquired from the practice of the various embodiments.

[0229] abbreviation

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

[0231] 3GPP Third Generation Partnership Project

[0232] 4G Fourth Generation

[0233] 5G Fifth Generation

[0234] 5GC 5G Core Network

[0235] ACK

[0236] AF Application Function

[0237] AM Confirmation Mode

[0238] AMBR Aggregate Maximum Bit Rate

[0239] AMF Access and Mobility Management Function

[0240] AN Access Network

[0241] ANR Automatic Neighbor Relation

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

[0243] API Application Programming Interface

[0244] APN Access Point Name

[0245] ARP Assignment Reserve Priority

[0246] ARQ Automatic Repeat Request

[0247] AS Access Layer

[0248] ASN.1 Abstract Syntax Notation One

[0249] AUSF authentication server function

[0250] AWGN Additive White Gaussian Noise

[0251] BCH Broadcast Channel

[0252] BER Bit Error Rate

[0253] BFD Beam Failure Detection

[0254] BLER Block Error Rate

[0255] BPSK Binary Phase Shift Keying

[0256] BRAS Broadband Remote Access Server

[0257] BSS Business Support System

[0258] BS Base Station

[0259] BSR Buffer Status Report

[0260] BW Bandwidth

[0261] BWP Bandwidth Part

[0262] C-RNTI Cell Radio Network Temporary Identifier

[0263] CA Carrier Aggregation, Certification Authority

[0264] CAPEX Capital Expenditure

[0265] CBRA Contention-based random access

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

[0267] CCA Clear Channel Assessment

[0268] CCE Control Channel Element

[0269] CCCH Common Control Channel

[0270] CE Coverage Enhancement

[0271] CDM Content Delivery Network

[0272] CDMA Code Division Multiple Access

[0273] CFRA Contention-free random access

[0274] CG Cell Group

[0275] CI Cell ID

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

[0277] CIM Common Information Model

[0278] CIR Carrier to Interference Ratio

[0279] CK Cryptographic Key

[0280] CM Connection Management, Conditional Mandatory

[0281] CMAS Commercial Mobile Alert Service

[0282] CMD command

[0283] CMS Cloud Management System

[0284] CO Conditional optional

[0285] CoMP Coordinated Multipoint

[0286] CORESET Control Resource Set

[0287] COTS Commercial Off-the-Shelf

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

[0289] CPD Connection Point Descriptor

[0290] CPE user terminal equipment

[0291] CPICH Common Pilot Channel

[0292] CQI Channel Quality Indicator

[0293] CPU CSI processing unit, central processing unit

[0294] C / R Command / Response field bit

[0295] CRAN Cloud Radio Access Network, Cloud RAN

[0296] CRB Common Resource Block

[0297] CRC Cyclic Redundancy Check

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

[0299] C-RNTI Cell RNTI

[0300] CS Circuit Switched

[0301] CSAR Cloud Service Archive

[0302] CSI Channel State Information

[0303] CSI-IM CSI interference measurement

[0304] CSI-RS CSI reference signal

[0305] CSI-RSRP CSI reference signal received power

[0306] CSI-RSRQ CSI reference signal reception quality

[0307] CSI-SINR CSI signal to interference plus noise ratio

[0308] CSMA Carrier Sense Multiple Access

[0309] CSMA / CA CSMA with collision avoidance

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

[0311] CTS Clear to Send

[0312] CW codeword

[0313] CWS Contention Window Size

[0314] D2D Device to Device

[0315] DC dual connection, direct current

[0316] DCI Downlink Control Information

[0317] DF deployment preferences

[0318] DL Downlink

[0319] DMTF Distributed Management Task Force

[0320] DPDK Data Plane Development Kit

[0321] DM-RS, DMRS Demodulation Reference Signal

[0322] DN Data Network

[0323] DRB Data Radio Bearer

[0324] DRS Discovery Reference Signal

[0325] DRX Discontinuous Reception

[0326] DSL Domain Specific Language, Digital Subscriber Line

[0327] DSLAM DSL Access Multiplexer

[0328] DwPTS Downlink Pilot Time Slot

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

[0330] E2E End-to-End

[0331] ECCA Extended Clear Channel Assessment, Extended CCA

[0332] ECCE Enhanced Control Channel Element, Enhanced CCE

[0333] ED Energy Detection

[0334] EDGE Enhanced Data rates for GSM Evolution (GSM Evolution)

[0335] EGMF exposes governance management functions

[0336] EGPRS Enhanced GPRS

[0337] EIR Equipment Identity Register

[0338] eLAA Enhanced License Assisted Access, enhanced LAA

[0339] EM Element Manager

[0340] eMBB Enhanced Mobile Broadband

[0341] EMS Element Management System

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

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

[0344] EPC Evolved Packet Core

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

[0346] EPRE Energy per resource element

[0347] EPS Evolved Packet System

[0348] EREG Enhanced REG, Enhanced Resource Element Group

[0349] ETSI European Telecommunications Standards Institute

[0350] ETWS Earthquake and Tsunami Warning System

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

[0352] E-UTRA Evolved UTRA

[0353] E-UTRAN Evolved UTRAN

[0354] EV2X Enhanced V2X

[0355] F1AP F1 Application Protocol

[0356] F1-C F1 control plane interface

[0357] F1-U F1 User Plane Interface

[0358] FACCH Fast Associated Control Channel

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

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

[0361] FACH Forward Access Channel

[0362] FAUSCH Fast Uplink Signalling Channel

[0363] FB Function Block

[0364] FBI Feedback

[0365] FCC Federal Communications Commission

[0366] FCCH Frequency Correction Channel

[0367] FDD Frequency Division Duplex

[0368] FDM Frequency Division Multiplexing

[0369] FDMA Frequency Division Multiple Access

[0370] FE Front End

[0371] FEC Forward Error Correction

[0372] FFS for further study

[0373] FFT Fast Fourier Transform

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

[0375] FN Frame Number

[0376] FPGA Field Programmable Gate Array

[0377] FR Frequency Range

[0378] G-RNTI GERAN Radio Network Temporary Identity

[0379] GERAN GSM EDGE RAN, GSM EDGE Radio Access Network

[0380] GGSN Gateway GPRS Support Node

[0381] GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System)

[0382] gNB Next Generation Node B

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

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

[0385] GNSS Global Navigation Satellite System

[0386] GPRS General Packet Radio Service

[0387] GSM Global System for Mobile Communications, Mobile Experts Group

[0388] GTP GPRS Tunneling Protocol

[0389] GTP-U GPRS Tunneling Protocol for the User Plane

[0390] GTS Go to sleep signal (related to WUS)

[0391] GUMMEI Globally Unique MME Identifier

[0392] GUTI Globally Unique Temporary UE Identifier

[0393] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

[0394] HANDO,HO switch

[0395] HFN Superframe Number

[0396] HHO Hard Handover

[0397] HLR Home Location Register

[0398] HN Home Network

[0399] HO Handover

[0400] HPLMN Home Public Land Mobile Network

[0401] HSDPA High Speed ​​Downlink Packet Access

[0402] HSN Hopping Sequence Number

[0403] HSPA High Speed ​​Packet Access

[0404] HSS Home Subscriber Server

[0405] HSUPA High Speed ​​Uplink Packet Access

[0406] HTTP Hypertext Transfer Protocol

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

[0408] I-Block Information Block

[0409] ICCID Integrated Circuit Card Identifier

[0410] ICIC Inter-cell Interference Coordination

[0411] ID

[0412] IDFT Inverse Discrete Fourier Transform

[0413] IE Information Elements

[0414] IBE In-Band Emission

[0415] IEEE Institute of Electrical and Electronics Engineers

[0416] IE1 Information Element Identifier

[0417] IEIDL Information Element Identifier Data Length

[0418] IETF Internet Engineering Task Force

[0419] IF Infrastructure

[0420] IM Interference Measurement, Intermodulation, IP Multimedia

[0421] IMC IMS credentials

[0422] IMEI International Mobile Equipment Identity

[0423] IMGI International Mobile Group Identity

[0424] IMPI IP Multimedia Privacy Identity

[0425] IMPU IP Multimedia Public Identity

[0426] IMS IP Multimedia Subsystem

[0427] IMSI International Mobile Subscriber Identity

[0428] IoT

[0429] IP Internet Protocol

[0430] IPsec IP security, Internet Protocol security

[0431] IP-CAN IP connection access network

[0432] IP-M IP Multicast

[0433] IPv4 Internet Protocol version 4

[0434] IPv6 Internet Protocol version 6

[0435] IR

[0436] IS Synchronization

[0437] IRP Integration Reference Point

[0438] ISDN Integrated Services Digital Network

[0439] ISIM IM Service Identity Module

[0440] ISO International Organization for Standardization

[0441] ISP Internet Service Provider

[0442] IWF interworking function

[0443] I-WLAN Intercommunication WLAN

[0444] K is the constraint length of the convolutional code, USIM individual key

[0445] kB kilobyte (1000 bytes)

[0446] kbps kilobits per second

[0447] Kc Cryptographic key

[0448] Ki Individual user authentication key

[0449] KPI Key Performance Indicator

[0450] KQI Key Quality Indicator

[0451] KSI Key Set Identifier

[0452] ksps kilosymbols per second

[0453] KVM Kernel Virtual Machine

[0454] L1 Layer 1 (physical layer)

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

[0456] L2 Layer 2 (Data Link Layer)

[0457] L3 Layer 3 (Network Layer)

[0458] LAA License Assisted Access

[0459] LAN Local Area Network

[0460] LBT Listen before you speak

[0461] LCM Lifecycle Management

[0462] LCR Low Chip Rate

[0463] LCS Location Services

[0464] LCID Logical Channel ID LI layer indicator

[0465] LLC Logical Link Control, Low Layer Compatibility

[0466] LPLMN Local PLMN LPP LTE Positioning Protocol

[0467] LSB Least Significant Bit

[0468] LTE Long Term Evolution

[0469] LWA LTE-WLAN Aggregation

[0470] LWIP LTE / WLAN radio level integration with IPsec tunneling LTE Long Term Evolution

[0471] M2M Machine to Machine

[0472] MAC Medium Access Control (Protocol Layer Context)

[0473] MAC Message Authentication Code (Security / Cryptography Context)

[0474] MAC-A MAC for authentication and key agreement (TSG T WG3 context)

[0475] MAC-I MAC for data integrity of signalling messages (TSG T WG3 context)

[0476] MANO Management and Orchestration

[0477] MBMS Multimedia Broadcast Multicast Service

[0478] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0479] MCC Mobile Country Code

[0480] MCG Master Cell Group

[0481] MCOT Maximum Channel Occupancy Time

[0482] MCS Modulation and Coding Scheme

[0483] MDAF Management Data Analysis Function

[0484] MDAS Management Data Analysis Service

[0485] Minimization of MDT-driven testing

[0486] ME Mobile Equipment

[0487] MeNB Master eNB

[0488] MER message error rate

[0489] MGL Measurement Gap Length

[0490] MGRP measurement gap repetition period

[0491] MIB Master Information Block, Management Information Base

[0492] MIMO Multiple Input Multiple Output

[0493] MLC Mobile Location Center

[0494] MM Mobility Management

[0495] MME Mobility Management Entity

[0496] MN Master Node

[0497] MO measurement object, mobile station calling

[0498] MPBCH MTC Physical Broadcast Channel

[0499] MPDCCH MTC Physical Downlink Control Channel

[0500] MPDSCH MTC Physical Downlink Shared Channel

[0501] MPRACH MTC Physical Random Access Channel

[0502] MPUSCH MTC Physical Uplink Shared Channel

[0503] MPLS Multi-Protocol Label Switching

[0504] MS Mobile Station

[0505] MSB Most Significant Bit

[0506] MSC Mobile Switching Center

[0507] MSI minimum system information, MCH scheduling information

[0508] MSID Mobile Station Identifier

[0509] MSIN Mobile Station Identification Number

[0510] MSISDN Mobile Subscriber ISDN Number

[0511] MT Mobile station called, mobile terminal

[0512] MTC Machine Type Communication

[0513] mMTC Massive MTC, Massive Machine Type Communication

[0514] MU-MIMO Multi-User MIMO

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

[0516] NACK Negative Acknowledgement

[0517] NAI Network Access Identifier

[0518] NAS Non-Access Stratum, Non-Access Stratum

[0519] NCT Network Connection Topology

[0520] NEC network capabilities exposed

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

[0522] NEF Network Exposure Function

[0523] NF Network Function

[0524] NFP Network Forwarding Path

[0525] NFPD Network Forwarding Path Descriptor

[0526] NFV Network Function Virtualization

[0527] NFVI NFV Infrastructure

[0528] NFVO NFV Orchestrator

[0529] NG Next generation, next generation

[0530] NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity

[0531] NM Network Manager

[0532] NMS Network Management System

[0533] N-PoP Network Point of Presence

[0534] NMIB, N-MIB Narrowband MIB

[0535] NPBCH Narrowband Physical Broadcast Channel

[0536] NPDCCH Narrowband Physical Downlink Control Channel

[0537] NPDSCH Narrowband Physical Downlink Shared Channel

[0538] NPRACH Narrowband Physical Random Access Channel

[0539] NPUSCH Narrowband Physical Uplink Shared Channel

[0540] NPSS Narrowband Primary Synchronization Signal

[0541] NSSS Narrowband Secondary Synchronization Signal

[0542] NR New Radio, Neighbor Relations

[0543] NRF NF Repository Functionality

[0544] NRS Narrowband Reference Signal

[0545] NS Network Services

[0546] NSA Non-standalone operation mode

[0547] NSD Network Service Descriptor

[0548] NSR Network Service Record

[0549] NSSAI `Network Slice Selection Assistance Information

[0550] S-NNSAI Single NSSAI

[0551] NSSF network slice selection function

[0552] NW Network

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

[0554] NZP Non Zero Power

[0555] O&M Operation and Maintenance

[0556] ODU2 Optical Channel Data Unit - Type 2

[0557] OFDM Orthogonal Frequency Division Multiplexing

[0558] OFDMA Orthogonal Frequency Division Multiple Access

[0559] OOB Out of Band

[0560] OOS Out of Sync

[0561] OPEX Operational Expenses

[0562] OSI Other System Information

[0563] OSS Operation Support System

[0564] OTA Air

[0565] PAPR Peak to Average Power Ratio

[0566] PAR Peak to Average Ratio

[0567] PBCH Physical Broadcast Channel

[0568] PC Power Control, Personal Computer

[0569] PCC primary component carrier, primary CC

[0570] PCell Primary Cell

[0571] PCI Physical Cell ID, Physical Cell Identity

[0572] PCEF Policy and Charging Enforcement Function

[0573] PCF Policy Control Function

[0574] PCRF Policy Control and Charging Rules Function

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

[0576] PDCCH Physical Downlink Control Channel

[0577] PDCP Packet Data Convergence Protocol

[0578] PDN Packet Data Network, Public Data Network

[0579] PDSCH Physical Downlink Shared Channel

[0580] PDU Protocol Data Unit

[0581] PEI Permanent Equipment Identifier

[0582] PFD Packet Flow Description

[0583] P-GW PDN Gateway

[0584] PHICH Physical Hybrid ARQ Indicator Channel

[0585] PHY Physical Layer

[0586] PLMN Public Land Mobile Network

[0587] PIN Personal Identification Number

[0588] PM performance measurement

[0589] PMI Precoding matrix indicator

[0590] PNF Physical Network Function

[0591] PNFD Physical Network Functional Descriptor

[0592] PNFR Physical Network Function Record

[0593] POC PTT over Cellular

[0594] PP,PTP Point to Point

[0595] PPP Point-to-Point Protocol

[0596] PRACH Physical RACH

[0597] PRB Physical Resource Block

[0598] PRG Physical Resource Group

[0599] ProSe Proximity Services, Proximity-Based Services

[0600] PRS Positioning Reference Signal

[0601] PRR Packet Receive Radio

[0602] PS Packet Service

[0603] PSBCH Physical Sidelink Broadcast Channel

[0604] PSDCH Physical Sidelink Downlink Channel

[0605] PSCCH Physical Sidelink Control Channel

[0606] PSSCH Physical Sidelink Shared Channel

[0607] PSCell Primary SCell

[0608] PSS Primary Synchronization Signal

[0609] PSTN Public Switched Telephone Network

[0610] PT-RS Phase Tracking Reference Signal

[0611] PTT Push to Talk

[0612] PUCCH Physical Uplink Control Channel

[0613] PUSCH Physical Uplink Shared Channel

[0614] QAM Quadrature Amplitude Modulation

[0615] QCI QoS Class Identifier

[0616] QCL Quasi-Co-sited

[0617] QFI QoS flow ID, QoS flow identifier

[0618] QoS Quality of Service

[0619] QPSK Quadrature (Quaternary) Phase Shift Keying

[0620] QZSS Quasi-Zenith Satellite System

[0621] RA-RNTI Random Access RNTI

[0622] RAB Radio Access Bearer, Random Access Burst

[0623] RACH Random Access Channel

[0624] RADIUS Remote Authentication Dial-In User Service

[0625] RAN Radio Access Network

[0626] RAND random number (for authentication)

[0627] RAR Random Access Response

[0628] RAT Radio Access Technology

[0629] RAU Routing Area Update

[0630] RB Resource Block, Radio Bearer

[0631] RBG Resource Block Group

[0632] REG Resource Element Group

[0633] Rel Release

[0634] REQ Request

[0635] RF

[0636] RI Rank Indicator

[0637] RIV Resource Indicator Value

[0638] RL Radio Link

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

[0640] RLC AM RLC Acknowledgement Mode

[0641] RLC UM RLC Unacknowledged Mode

[0642] RLF Radio Link Failure

[0643] RLM Radio Link Monitoring

[0644] RLM-RS Reference signal for RLM

[0645] RM Registration Management

[0646] RMC Reference Measurement Channel

[0647] RMSI Remaining MSI, Remaining Minimum System Information

[0648] RN Relay Node

[0649] RNC Radio Network Controller

[0650] RNL Radio Network Layer

[0651] RNTI Radio Network Temporary Identifier

[0652] ROHC Robust Header Compression

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

[0654] RRM Radio Resource Management

[0655] RS reference signal

[0656] RSRP Reference Signal Received Power

[0657] RSRQ Reference Signal Received Quality

[0658] RSSI Reference Signal Strength Indicator

[0659] RSU Road Side Unit

[0660] RSTD Reference Signal Time Difference

[0661] RTP Real Time Protocol

[0662] RTS Ready to Send

[0663] RTT Round Trip Time

[0664] Rx receive, receive, receiver

[0665] S1AP S1 Application Protocol

[0666] S1-MME is used for S1 control plane

[0667] S1-U S1 for user plane

[0668] S-GW Service Gateway

[0669] S-RNTI SRNC Radio Network Temporary Identifier

[0670] S-TMSI SAE temporary mobile station identifier

[0671] SA Standalone Operation Mode

[0672] SAE system architecture evolution

[0673] SAP Service Access Point

[0674] SAPD Service Access Point Descriptor

[0675] SAPI Service Access Point Identifier

[0676] SCC Secondary Component Carrier, Secondary CC

[0677] SCell Secondary Cell

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

[0679] SCG Secondary Cell Group

[0680] SCM Security Context Management

[0681] SCS Subcarrier Spacing

[0682] SCTP Stream Control Transmission Protocol

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

[0684] SDL Supplemental Downlink

[0685] SDNF Structured Data Storage Network Function

[0686] SDP Session Description Protocol

[0687] SDSF structured data storage function

[0688] SDU Service Data Unit

[0689] SEAF Security Anchoring Function

[0690] SeNB Assisted eNB

[0691] SEPP Security Edge Protection Proxy

[0692] SFI Slot Format Indicator

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

[0694] SFN System Frame Number

[0695] SgNB

[0696] SGSN Serving GPRS Support Node

[0697] S-GW Service Gateway

[0698] SI System Information

[0699] SI-RNTI System Information RNTI

[0700] SIB System Information Block

[0701] SIM Subscriber Identity Module

[0702] SIP Session Initiation Protocol

[0703] SiP System in Package

[0704] SL Side Link

[0705] SLA Service Level Agreement

[0706] SM Session Management

[0707] SMF session management functions

[0708] SMS Short Message Service

[0709] SMSF SMS Function

[0710] SMTC SSB-based measurement timing configuration

[0711] SN Secondary node, serial number

[0712] SoC System on Chip

[0713] SON Self-Organizing Network

[0714] SpCell Special Cell

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

[0716] SPS Semi-persistent Scheduling

[0717] SQN serial number

[0718] SR Scheduling Request

[0719] SRB Signalling Radio Bearer

[0720] SRS Sounding Reference Signal

[0721] SS Sync Signal

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

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

[0724] SSC Session and Service Continuity

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

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

[0727] SS-SINR Signal to Interference and Noise Ratio based on synchronization signal

[0728] SSS Secondary synchronization signal

[0729] SSSG Search Space Group

[0730] SSSIF Search Space Set Indicator

[0731] SST Slice / Service Type

[0732] SU-MIMO Single User MIMO

[0733] SUL Supplementary Uplink

[0734] TA Timing Advance, Tracking Area

[0735] TAC Tracking Area Code

[0736] TAG Timing Advance Group

[0737] TAU Tracking Area Updates

[0738] TB Transfer Block

[0739] TBS Transport Block Size

[0740] TBD To be defined

[0741] TCI Transmission Configuration Indicator

[0742] TCP transport communication protocol

[0743] TDD Time Division Duplex

[0744] TDM Time Division Multiplexing

[0745] TDMA Time Division Multiple Access

[0746] TE Terminal Equipment

[0747] TEID Tunnel Endpoint Identifier

[0748] TFT Business Flow Template

[0749] TMSI Temporary Mobile Subscriber Identity

[0750] TNL Transport Network Layer

[0751] TPC Transmit Power Control

[0752] TPMI Transmitted Precoding Matrix Indicator

[0753] TR Technical Report

[0754] TRP,TRxP Transmission Receive Point

[0755] TRS Tracking Reference Signal

[0756] TRx Transceiver

[0757] TS Technical Specifications, Technical Standards

[0758] TTI Transmission Time Interval

[0759] Tx transmission, transmission, transmitter

[0760] U-RNTI UTRAN Radio Network Temporary Identity

[0761] UART Universal Asynchronous Receiver and Transmitter

[0762] UCI Uplink Control Information

[0763] UE User Equipment

[0764] UDM Unified Data Management

[0765] UDP User Datagram Protocol

[0766] UDSF Unstructured Data Storage Network Function

[0767] UICC Universal Integrated Circuit Card

[0768] UL Uplink

[0769] UM Unconfirmed Mode

[0770] UML Unified Modeling Language

[0771] UMTS Universal Mobile Telecommunications System

[0772] UP User Plane

[0773] UPF User Plane Function

[0774] URI Uniform Resource Identifier

[0775] URL Uniform Resource Locator

[0776] URLLC Ultra-Reliable Low Latency

[0777] USB Universal Serial Bus

[0778] USIM Universal Subscriber Identity Module

[0779] USS UE-specific search space

[0780] UTRA UMTS Terrestrial Radio Access

[0781] UTRAN Universal Terrestrial Radio Access Network

[0782] UwPTS Uplink Pilot Time Slot

[0783] V2I Vehicle to Infrastructure

[0784] V2P Vehicle to Pedestrian

[0785] V2V Vehicle to Vehicle

[0786] V2X: Vehicle-to-Everything

[0787] VIM Virtualization Infrastructure Manager

[0788] VL Virtual Link

[0789] VLAN Virtual LAN, Virtual Local Area Network

[0790] VM Virtual Machine

[0791] VNF Virtualized Network Function

[0792] VNFFG VNF forwarding graph

[0793] VNFFGD VNF Forwarding Graph Descriptor

[0794] VNFM VNF Manager

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

[0796] VPLMN Visited Public Land Mobile Network

[0797] VPN Virtual Private Network

[0798] VRB Virtual Resource Block

[0799] WiMAX Worldwide Interoperability for Microwave Access

[0800] WLAN Wireless Local Area Network

[0801] WMAN Wireless Metropolitan Area Network

[0802] WPAN Wireless Personal Area Network

[0803] X2-C X2 control plane

[0804] X2-U X2 user plane

[0805] XML Extensible Markup Language

[0806] XRES Expected User Response

[0807] XOR

[0808] ZC Zadoff-Chu

[0809] ZP Zero Power

[0810] the term

[0811] For the purposes of this document, the following terms and definitions apply to the examples and implementations discussed herein.

[0812] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

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

[0814] As used herein, the term "interface circuit" refers to a circuit that enables, is a part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0815] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0816] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with and / or may be referred to as networked computers, networked hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN equipment, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, etc.

[0817] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.

[0818] As used herein, the terms "appliance", "computer appliance", etc. refer to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image to be implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

[0819] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time and / or a processor / CPU usage rate, a processor and accelerator load, a hardware time or usage rate, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage rate, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computing, storage and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage and / or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources and / or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0820] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" and / or any other similar terms representing a path or medium through which data is transmitted. In addition, the term "link" as used herein refers to a connection between two devices for transmitting and receiving information over a RAT.

[0821] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0822] The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by means of communication, including through a wire or other interconnect connection, through a wireless communication channel or link, etc.

[0823] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents.

[0824] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0825] The term "SSB" refers to SS / PBCH block.

[0826] The term "primary cell" refers to an MCG cell operating on a primary frequency, where the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0827] The term "primary SCG cell" refers to an SCG cell in which a UE performs random access when reconfiguration is performed using a synchronization procedure for DC operation.

[0828] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured with CA.

[0829] The term "secondary cell group" refers to a subset of serving cells including a PSCell and zero or more secondary cells for a UE configured with DC.

[0830] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED without CA / DC configured, where there is only one serving cell including the primary cell.

[0831] The term "serving cell" refers to a cell group including a special cell for a UE configured with CA and in RRC_CONNECTED and all secondary cells.

[0832] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term "special cell" refers to the Pcell.

Claims

1. A method for ultra-reliable and low-delay URLLC transmission to a user equipment UE using multiple transmission reception points (TRPs) by an access node, the method comprising: Allocating the virtual resource blocks into a first part and a second part within the active bandwidth part based on the resource indication value RIV, the length LRBS of the consecutively allocated resource blocks and the fraction; using the first part to transmit to the UE via a first transmission reception point TRP1 associated with a first transmission configuration indicator TCI state, and The second part is transmitted to the UE via a second transmission reception point TRP2 associated with a second TCI state.

2. The method of claim 1, wherein the fraction is one-half, one-third or one-quarter. The method of claim 1 , wherein the RIV corresponds to a starting virtual resource block. 4 . The method of claim 1 , wherein the second portion is a remaining portion of the virtual resource block after allocating the first portion of the virtual resource block.

5. The method of claim 1, wherein allocating virtual resource blocks further comprises allocating into the first portion, the second portion, and a third portion, and wherein further allocating is also based on a second fraction.

6. The method of claim 5, wherein the fraction is one-half, one-third or one-quarter, and wherein the second fraction is one-third or one-quarter.

7. The method of claim 1, further comprising providing an indication of the allocated virtual resource blocks using a single downlink control information (DCI).

8. An access node, comprising: a processor circuit configured to allocate the virtual resource blocks into a first part and a second part within the active bandwidth part based on a resource indication value RIV, a length LRBS of consecutively allocated resource blocks and a fraction; and A radio front-end circuit, the radio front-end circuit being configured to: The first part is used for transmission to a user equipment UE via a first transmission reception point TRP1 associated with a first transmission configuration indicator TCI state, and the second part is transmitted to the UE via a second transmission reception point TRP2 associated with a second TCI state.

9. The access node of claim 8, wherein the fraction is one-half, one-third or one-quarter.

10. The access node of claim 8, wherein the RIV corresponds to a starting virtual resource block.

11. The access node of claim 8, wherein the second portion is a remaining portion of the virtual resource block after allocating the first portion of the virtual resource block.

12. The access node of claim 8, wherein the processor circuit is further configured to allocate the virtual resource block into the first portion, the second portion, and a third portion, and wherein the further allocation is based on a second fraction.

13. The access node of claim 12, wherein the fraction is one-half, one-third or one-quarter, and wherein the second fraction is one-third or one-quarter.

14. The access node of claim 8, wherein the processor circuit is further configured to provide an indication of the allocated virtual resource blocks using a single downlink control information (DCI).

15. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one of a plurality of elements of a method, the method comprising: Allocating the virtual resource blocks into a first part and a second part within the active bandwidth part based on the resource indication value RIV, the length LRBS of the consecutively allocated resource blocks and the fraction; using said first part for transmission to a user equipment UE via a first transmission reception point TRP1 associated with a first transmission configuration indicator TCI state, and The second part is transmitted to the UE via a second transmission reception point TRP2 associated with a second TCI state.

16. The non-transitory computer readable medium of claim 15, wherein the fraction is one-half, one-third, or one-quarter.

17. The non-transitory computer-readable medium of claim 15, wherein the RIV corresponds to a starting virtual resource block.

18. The non-transitory computer-readable medium of claim 15, wherein the second portion is a remaining portion of the virtual resource block after the first portion of the virtual resource block is allocated.

19. The non-transitory computer readable medium of claim 15, wherein allocating virtual resource blocks further comprises allocating into the first portion, the second portion, and a third portion, and wherein further allocating is also based on a second fraction.

20. The non-transitory computer readable medium of claim 19, wherein the fraction is one-half, one-third, or one-quarter, and wherein the second fraction is one-third or one-quarter.

Images