Method for repeated data transmission for high reliability communication

Abstract

Some embodiments of the present disclosure include an apparatus and method for data repetition transmission for high-reliability communication. The apparatus and method may at least include enabling general PDSCH repetition transmission by a user equipment (UE) through a radio resource control (RRC) signaling configuration, and receiving the general PDSCH repetition transmission by the UE.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit under 35 USC §119(e) of U.S. Provisional Application No. 62 / 794,288, filed on January 18, 2019, which is hereby incorporated by reference in its entirety. Background Art

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

[0004] Some embodiments of the present disclosure include apparatus and methods for data repetition transmission for high-reliability communication.

[0005] Some embodiments relate to a method for enabling physical downlink shared channel (PDSCH) repetition for single transmission reception point (TRP) or multiple TRP transmissions. The method includes enabling PDSCH repetition transmission by a user equipment (UE) in response to a radio resource control (RRC) signaling configuration, and receiving the PDSCH repetition transmission by the UE.

[0006] The method may further include PDSCH repetition transmission based on time domain transmission, frequency domain transmission or space domain transmission.

[0007] The method may further include enabling repetition based on multiple TRP transmission by the UE through RRC signaling to configure a transmission configuration indicator (TCI) state list corresponding to the multiple TPR repetition cluster.

[0008] The method may further include enabling, by the UE, a list of repetition clusters, each of the repetition clusters consisting of 2, 3 or 4 activated TCI states corresponding to the TCI state list.

[0009] The method may further include signaling, by the UE, an index of the activated repetition cluster through a TCI field in downlink control information (DCI).

[0010] The method may further include dynamically signaling, by the UE, the DCI TRP or TCI status of the repetitive cluster.

[0011] The method may further include scheduling, by the UE, a physical downlink control channel (PDCCH) for PDSCH repetition transmission, wherein a TCI field of a TCI state is to be cyclically used for subsequent PDSCH repetition transmissions.

[0012] Some embodiments relate to a non-transitory computer-readable medium having instructions stored thereon that, when executed by a computing system, cause the computing system to perform operations. The operations may include enabling PDSCH repetition transmission in response to a radio resource control (RRC) signaling configuration, and causing reception of a general PDSCH repetition transmission.

[0013] Some embodiments relate to a non-transitory computer-readable medium, wherein PDSCH repetition transmission is based on time domain transmission, frequency domain transmission, or space domain transmission.

[0014] Some embodiments relate to a non-transitory computer-readable medium, wherein the operations further include enabling repetition based on multiple TRP transmissions via RRC signaling configuration to configure a transmission configuration indicator (TCI) state list corresponding to a multiple TPR repetition cluster.

[0015] Some embodiments relate to a non-transitory computer-readable medium, wherein the operations further include enabling a list of repeating clusters, each of the repeating clusters consisting of 2, 3, or 4 activated TCI states corresponding to the TCI state list.

[0016] Some embodiments relate to a non-transitory computer-readable medium, wherein the operations further include signaling an index of the activated repetition cluster via a TCI field in downlink control information (DCI).

[0017] Some embodiments relate to a non-transitory computer-readable medium, wherein the operations further include dynamically signaling a DCI TRP or TCI status of a duplicate cluster.

[0018] Some embodiments relate to a non-transitory computer-readable medium, wherein the operations further include scheduling a physical downlink control channel (PDCCH) for a PDSCH repetition transmission, wherein a TCI field of a TCI state is to be cyclically used for subsequent PDSCH repetition transmissions.

[0019] Some embodiments relate to a user equipment (UE). The UE may include a processor configured to enable PDSCH repetition transmission in response to a radio resource control (RRC) signaling configuration. The UE may also include a radio frequency integrated circuit coupled to the processor, the radio frequency integrated circuit configured to receive a general PDSCH repetition transmission.

[0020] Some embodiments relate to a UE, wherein PDSCH repetition transmission is based on time domain transmission, frequency domain transmission, or space domain transmission.

[0021] Some embodiments relate to a UE, wherein the processor is further configured to enable repetition based on multiple TRP transmissions via RRC signaling configuration to configure a transmission configuration indicator (TCI) state list corresponding to a multiple TPR repetition cluster.

[0022] Some embodiments relate to a UE, wherein the processor is further configured to enable a list of repetition clusters, each of the repetition clusters consisting of 2, 3 or 4 activated TCI states corresponding to the TCI state list.

[0023] Some embodiments relate to a UE, wherein the processor is further configured to signal an index of the activated repetition cluster via a TCI field in downlink control information (DCI).

[0024] Some embodiments relate to a UE, wherein the processor is further configured to dynamically signal a DCI TRP or TCI status of a repetitive cluster. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 Enhanced repeated transmissions according to an embodiment are shown.

[0026] Figure 2 A list of activated TCI states according to an implementation scheme is shown.

[0027] FIG. 3A to FIG. 3C A 2-TRP / 3-TRP / 4-TRP based repeat cluster according to an embodiment is shown.

[0028] Figure 4 An exemplary system architecture according to an embodiment is shown.

[0029] Figure 5 Another exemplary system architecture according to an embodiment is shown.

[0030] Figure 6 Another exemplary system architecture according to an embodiment is shown.

[0031] Figure 7 A block diagram of exemplary infrastructure equipment is shown, according to an embodiment.

[0032] Figure 8 A block diagram of an exemplary platform according to an embodiment is shown.

[0033] Fig. 9 A block diagram of a baseband circuit and a front-end module according to an embodiment is shown.

[0034] Fig.10 A block diagram illustrating exemplary protocol functionality that may be implemented in a wireless communication device according to an embodiment.

[0035] Fig.11 A block diagram of exemplary core network components is shown, according to an embodiment.

[0036] Fig.12 A block diagram of system components for supporting network function virtualization according to an embodiment is shown.

[0037] Fig.13 A block diagram of an exemplary computer system that can be used to implement various embodiments is shown.

[0038] Fig.14 A method of operating a system according to an embodiment of the present disclosure is shown.

[0039] Features and advantages of the embodiments will become more apparent from the detailed description set forth below when taken in conjunction with the accompanying drawings, wherein like reference characters identify corresponding elements throughout. In the accompanying drawings, like reference numerals generally indicate identical, functionally similar, and / or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit in the corresponding reference numeral. DETAILED DESCRIPTION

[0040] Discussion of implementation plan

[0041] 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).

[0042] From the perspective of multiple transmission reception points (TRPs), the basic principle to improve the reliability and robustness of the transmitted data packets is to transmit multiple copies of the same data payload so that the UE can combine them in a blind repetition manner to benefit from the spatial diversity gain. And each copy is associated with a different active TCI state corresponding to a specific TRP. The outstanding issues of 3GPP are how to specify the resources for each "copy" and how to determine the TCI state for each "copy".

[0043] It should be noted that there is a certain repetition functionality in New Radio (NR) Rel-15 using the higher layer parameter pdsch-AggregationFactor, where each physical downlink shared channel (PDSCH) is transmitted in a cycle of a predefined redundancy version (RV), where a single layer of PDSCH is restricted. This principle can be extended to also include the transmission configuration indicator (TCI) state. Therefore, when the UE is configured for such robust operation, the physical downlink shared channel (PDCCH) can trigger a group of PDSCH transmissions, where each PDSCH can use a different TCI state than the TCI state activated by the group in a predefined way.

[0044] In Rel-15, these multiple PDSCHs were transmitted in a single layer in different time slots, but to reduce latency, in Rel-16 it should be possible to trigger multiple such PDSCHs in the same time slot using type B scheduling (e.g., with mini-slot-based repetition), in the same set of OFDM symbols via frequency division multiplexing (FDM, e.g., frequency-based repetition), or in overlapping resources (SDM or layer-based repetition). How the repetition "pattern" should look like and how it should be configured remains unresolved in 3GPP.

[0045] The implementation scheme of this document presents a mechanism for enabling transmission of different PDSCH repetitions (based on time / frequency / spatial domains of single TRP or multiple TRPs) using flexible RRC / MAC / DCI signaling, so that the reliability of PDSCH transmission can be improved with reasonable signaling overhead.

[0046] Implementation -1: Radio Resource Control (RRC) Configuration for Flexible PDSCH Repetition In this implementation, general PDSCH repetition transmission is enabled through RRC signaling configuration, so that time, frequency and / or spatial domain (based on single TRP or multiple TRP) repetition can be achieved.

[0047] Implementation -2: RRC configured multi-TRP repetition cluster. In this implementation, for multi-TRP based repetition, the TCI state list corresponding to the multi-TPR repetition cluster is configured by RRC signaling. The downlink control information (DCI) TCI field signals the TCI state of the first PDSCH transmission. The TCI states in the RRC configured multi-TRP repetition cluster starting from the TCI state signaled in the DCI should be used cyclically for subsequent PDSCH repetitions.

[0048] Implementation -3: MAC CE based multi-TRP repeat cluster list activation. In this implementation, the media access control element (MAC CE) can activate a list of repeat clusters, each of which consists of 2, 3 or 4 activated TCI states or some other number of activated clusters.

[0049] Implementation -4: TCI signaling in DCI for multi-TRP repetition cluster selection for MAC CE activation. In this implementation, the index of the activated repetition cluster can be signaled through the TCI field in the DCI, so that the repetition cluster can be dynamically selected from the MAC CE activation list of the repetition cluster in Implementation -3.

[0050] Implementation -5: TCI signaling in DCI for dynamic multi-TRP duplicate cluster selection. In this implementation, the TRP / TCI status of a duplicate cluster can be dynamically signaled in the DCI. Specifically, explicit TCI status list signaling and TCI status combination signaling can be used. The former has better flexibility at the cost of slightly larger signaling overhead, while the latter has smaller overhead within a duplicate cluster with the same priority.

[0051] Further details of implementation schemes are presented below.

[0052] Implementation 1: RRC configuration for flexible PDSCH repetition

[0053] In this embodiment, the RRC signaling for PDSCH configuration can be used to enable repeated transmission based on single TRP / multiple TRP. For example, the following options (underlined in the box below) can be used to signal the relevant settings of different repeated transmission schemes.

[0054]

[0055]

[0056] The parameter "pdsch-AggregationResourceAllocation" defines the resource allocation implementation for each repetition copy of the first PDSCH data packet scheduled by the PDCCH. Specifically, several parameters are defined as follows to enable flexible resource allocation for repetition transmission.

[0057] The parameter "timePeriod" defines the time periodicity in terms of the number of OFDM symbols between adjacent PDSCH repetitions. When this parameter is not present, 1 time slot of 14 OFDM symbols is applied to achieve slot-level repetition.

[0058] The parameter "freqInterval" indicates the frequency spacing in terms of the number of resource blocks between adjacent repetitions. When not present, repetitions shall use the same RBs.

[0059] The parameter "antennaPortInterval" defines the interval of antenna port numbers between adjacent repetitions. When absent, different repetitions shall use the same antenna ports.

[0060] The parameter "multiTRPSize" defines the number of TRPs to use for different repetitions in the loop. When absent, repetitions based on a single TPR are used.

[0061] Due to the above proposed parameter "pdsch-AggregationResourceAllocation", different types of repeated transmissions can be realized, such as Figure 1 shown. Figure 1 The enhanced repetition transmission according to the implementation scheme is shown. Specifically, the following repetition options can be implemented through corresponding settings:

[0062] Option-1: Time domain repetition 102 (such as Figure 1 - (a)): timePeriod = n>0

[0063] Option-2: Frequency domain repetition 104 (such as Figure 1 - (b) ): timePeriod = 0; freqInterval = n

[0064] Option-3: Spatial domain repetition 106 using multiple antenna ports (e.g. Figure 1 -(c) shows): timePeriod=0; antennaPortInterval=n1 or n2.

[0065] Implementation 2: Multiple TRPs in RRC Configuration

[0066] In this embodiment, the RRC may configure a TCI state list for a repeating cluster, as underlined in the box below.

[0067]

[0068] The parameter "tciStateList" defines a list of TCI states associated with the corresponding TRPs to be used in multi-TRP based repeated transmissions. When not present, single TRP based repeated transmissions are used. In the PDCCH scheduling PDSCH repeated transmissions, the TCI field signals the TCI state from the list defined in the tciStateList for the first PDSCH transmission, and the TCI states in the tciStateList starting from the TCI state signaled by the DCI will be used cyclically for subsequent PDSCH repetitions.

[0069] Implementation 3: Multi-TRP Duplicate Cluster List Activation Based on MAC CE

[0070] Figure 2 An activated TCI state list 200 is shown according to an embodiment. Figure 2As shown, the 8 activated TCI states may be arranged in a list in increasing or decreasing order of the corresponding TCI state ID. And the index of the activated TCI state in the list may be used to identify the activated TCI state of the list of clusters of activated 2 / 3 / 4 activated TCI states in the proposed MAC CE. Those skilled in the art will recognize that more or less TCI states and clusters may be used.

[0071] FIG. 3A to FIG. 3C A 2-TRP / 3-TRP / 4-TRP based repeat cluster according to an embodiment is shown. FIG. 3A to FIG. 3C The new MAC CE shown in is used to signal all supported 2TRP / 3TRP / 4TRP based repetition clusters, e.g., up to 8 possible repetition clusters.

[0072] FIG. 3A to FIG. 3C The fields of the MAC CE proposed in are defined as:

[0073] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of the field is 5 bits;

[0074] BWP ID: This field contains the BWP-Id of the uplink bandwidth part to which the PUCCH transmission applies. The length of the BWP ID field is 2 bits.

[0075] TCI2-#{x,y}: This field contains the index of the yth TCI state (yth TRP) of the xth repetition cluster. The length of this field is 3 bits;

[0076] R: Reserved bit.

[0077] Implementation-4: TCI signaling in DCI for multi-TRP repeated cluster selection for MAC CE activation

[0078] like Figure 3A As shown, up to 8 repetition clusters can be activated, and the TCI status field in the DCI can signal the index of the repetition cluster activated by the MAC CE. Therefore, the repetition cluster can be changed dynamically through the DCI.

[0079] Implementation 5: TCI signaling in DCI for dynamic multi-TRP repeat cluster selection

[0080] Depending on the value of the RRC parameter multiTRPSize, 2, 3 or 4 TRPs shall be signaled via the TCI status field in the DCI. The following options may be used to signal the TCI status associated with a TRP.

[0081] Option-1: TCI List Signaling: In this option, 6 bits, 9 bits, or 14 bits shall be used to signal the index of the activated TCI states of 2, 3, or 4 TRPs, respectively. Thus, (a) for 2-TRP clusters, TCI-Status field = #index of TCI state of 1st TRP; #index of TCI state of 2nd TRP}; (b) for 3-TRP clusters, TCI-Status field = {#index of TCI state of 1st TRP; #index of TCI state of 2nd TRP; #index of TCI state of 3rd TRP}; and (c) for 4-TRP clusters, TCI-Status field = {#index of TCI state of 1st TRP; #index of TCI state of 2nd TRP; #index of TCI state of 3rd TRP; #index of TCI state of 4th TRP}.

[0082] In the case where the index of the activated TCI state is determined according to the increasing order of the TCI state ID among all activated TCI states, and since there are a maximum of 8 activated TCI states at a time, 3 bits may be used to indicate the index of each activated TCI state.

[0083] Option-2: TCI state combination signaling: To save signaling overhead, the TCI state field in the DCI can signal a combination of 2, 3, or 4 TCI states out of 8 activated TCI states. Therefore, a 4-TRP repetition cluster requires 8 bits, while Option-1 requires 12 bits. Let N define the number of TRPs in the repetition cluster signaled in "multiTRPSize", and i n , n=0...N-1 represents the index of the (n+1)th TRP in the repetition cluster. Specifically, for a TRP with index (i0,...,i N-1 ),i n >i n+1 ,i n The combination of N selected TRPs ∈ {N-1-n, ..., 7-n} can signal the following values ​​in the TCI status field. This is shown in the following formula (1):

[0084]

[0085] System and implementation

[0086] Figure 4An exemplary architecture of a system 400 of a network according to various embodiments is shown. The following description is provided for an example system 400 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.

[0087] like Figure 4 As shown, system 400 includes UE 401a and UE 401b (collectively referred to as "UE 401"). In this example, multiple UEs 401 are shown as smart phones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument panels (ICs), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0088] In some embodiments, any of the UEs 401 may include 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.

[0089] UE 401 may be configured to connect, e.g., be communicatively coupled, to RAN 410. In an embodiment, RAN 410 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 410 operating in an NR or 5G system 400, while the term "E-UTRAN" or the like may refer to RAN 410 operating in an LTE or 4G system 400. UE 401 utilizes connections (or channels) 403 and 404, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0090] In this example, connections 403 and 404 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, UE 401 may directly exchange communication data via ProSe interface 405. ProSe interface 405 may alternatively be referred to as SL interface 405, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0091] UE 401b is shown as being configured to access AP 406 (also referred to as "WLAN node 406," "WLAN 406," "WLAN terminal 406," "WT 406," etc.) via connection 407. Connection 407 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 406 will include wireless fidelity. Router. In this example, AP 406 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 401b, RAN 410, and AP 406 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 401b in RRC_CONNECTED state being configured by RAN nodes 411a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 401b using WLAN radio resources (e.g., connection 407) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through connection 407. 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.

[0092] RAN 410 includes one or more AN nodes or RAN nodes 411a and 411b (collectively referred to as "RAN node 411") that enable connections 403 and 404. 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 411 (e.g., a gNB) operating in an NR or 5G system 400, while the terms "E-UTRAN node" and the like may refer to a RAN node 411 (e.g., an eNB) operating in an LTE or 4G system 400. According to various embodiments, the RAN node 411 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.

[0093] In some embodiments, all or part of the RAN node 411 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 splitting, such as PDCP splitting, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 411; MAC / PHY splitting, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 411; or "lower PHY" splitting, 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 411. This virtualization framework allows idle processor cores of the RAN node 411 to execute other virtualized applications. In some specific implementations, individual RAN nodes 411 may represent a plurality of RAN nodes 411 connected to the RAN via individual F1 interfaces ( Figure 4 In these embodiments, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 7), and the gNB-CU may be operated by a server (not shown) located in the RAN 410 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 411 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 401 and is connected to the 5GC (e.g., Figure 6 CN 620) RAN node.

[0094] In a V2X scenario, one or more of the RAN nodes 411 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 401 (vUE 401). 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.

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

[0096] In an embodiment, multiple UEs 401 may be configured to communicate with each other or any of RAN nodes 411 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. The OFDM signal may include multiple orthogonal subcarriers.

[0097] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 411 to the UE 401, 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.

[0098] According to various embodiments, UE 401 and RAN node 411 communicate data (e.g., transmit data and receive data) through a licensed medium (also referred to as "licensed spectrum" and / or "licensed frequency band") and an unlicensed shared medium (also referred to as "unlicensed spectrum" and / or "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.

[0099] To operate in the unlicensed spectrum, the UE 401 and the RAN node 411 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 401 and the RAN node 411 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.

[0100] LBT is a mechanism by which equipment (e.g., multiple UEs 401, multiple RAN nodes 411, etc.) senses the 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.

[0101] 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 401, AP 406, 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.

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

[0103] 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 401 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.

[0104] The PDSCH carries user data and higher layer signaling to the UE 401. 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 401 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 401b within a cell) may be performed on any of the RAN nodes 411 based on channel quality information fed back from any of the UEs 401. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UEs 401.

[0105] 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).

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

[0107] RAN nodes 411 may be configured to communicate with each other via interface 412. In embodiments where system 400 is an LTE system (eg, when CN 420 is a Figure 5 401 ), the interface 412 may be an X2 interface 412. The X2 interface may be defined between two or more RAN nodes 411 (e.g., two or more eNBs, etc.) connected to the EPC 420, and / or between two eNBs connected to the EPC 420. 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 401 for user data; information about PDCP PDUs that were not delivered to the UE 401; 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.

[0108] When system 400 is a 5G or NR system (e.g., when CN 420 is Figure 6In an implementation scheme of the 5GC 620 in the 5GC 420, the interface 412 may be an Xn interface 412. The Xn interface is defined between two or more RAN nodes 411 (e.g., two or more gNBs, etc.) connected to the 5GC 420, between a RAN node 411 (e.g., a gNB) and an eNB connected to the 5GC 420, and / or between two eNBs connected to the 5GC 420. 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 401 in a connected mode (e.g., a CM connection) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 411. The mobility support may include context transfer from the old (source) serving RAN node 411 to the new (target) serving RAN node 411; and control of the user plane tunnel between the old (source) serving RAN node 411 and the new (target) serving RAN node 411. 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.

[0109] RAN 410 is shown as being communicatively coupled to a core network—in this embodiment, communicatively coupled to a core network (CN) 420. CN 420 may include a plurality of network elements 422 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 401) connected to CN 420 via RAN 410. The components of CN 420 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 CN 420 may be referred to as a network slice, and a logical instance of a portion of CN 420 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0110] Generally speaking, the application server 430 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 430 may also be configured to support one or more communication services for the UE 401 via the EPC 420 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.).

[0111] In an embodiment, CN 420 may be a 5GC (referred to as "5GC 420" or the like), and RAN 410 may be connected to CN 420 via an NG interface 413. In an embodiment, NG interface 413 may be divided into two parts: an NG user plane (NG-U) interface 414, which carries traffic data between RAN node 411 and UPF; and an S1 control plane (NG-C) interface 415, which is a signaling interface between RAN node 411 and AMF. Figure 6 Discussed in more detail, CN 420 is an implementation of 5GC 420.

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

[0113] Figure 5 FIG. 5 shows an exemplary architecture of a system 500 including a first CN 520 according to various embodiments. In this example, the system 500 may implement the LTE standard, wherein the CN 520 is a Figure 4 In addition, UE 501 may communicate with Figure 4 The UE 401 is the same as or similar to the UE 401, and the E-UTRAN 510 may be Figure 4 The CN 520 may be a RAN that is the same as or similar to the RAN 410 of the mobile network, and may include the RAN node 411 discussed previously. The CN 520 may include an MME 521, an S-GW 522, a P-GW 523, an HSS 524, and an SGSN 525.

[0114] The MME 521 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 501. The MME 521 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 storage, etc. for maintaining knowledge of the current location of the UE 501, providing user identity confidentiality, and / or performing other similar services to users / subscribers. Each UE 501 and the MME 521 may include an MM or EMM sublayer, and when the attachment procedure is successfully completed, an MM context may be established in the UE 501 and the MME 521. The MM context may be a data structure or database object that stores MM-related information of the UE 501. The MME 521 may be coupled to the HSS 524 via an S6a reference point, to the SGSN 525 via an S3 reference point, and to the S-GW 522 via an S11 reference point.

[0115] SGSN 525 may be a node that serves UE 501 by tracking the location of individual UE 501 and performing security functions. In addition, SGSN 525 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 521; handling of UE 501 time zone functions, as specified by MME 521; and MME selection for handover to E-UTRAN 3GPP access network. The S3 reference point between MME 521 and SGSN 525 may enable user and bearer information exchange for inter-3GPP access network mobility in an idle state and / or an active state.

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

[0117] The S-GW 522 may terminate the S1 interface 413 towards the RAN 510 (at Figure 5 The S-GW 522 may be a local mobility anchor point 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 522 and the MME 521 may provide a control plane between the MME 521 and the S-GW 522. The S-GW 522 may be coupled to the P-GW 523 via the S5 reference point.

[0118] P-GW 523 may terminate the SGi interface toward PDN 530. P-GW 523 may route data packets between EPC 520 and external networks such as a network including application server 430 (alternatively referred to as "AF") via IP interface 425 (see, e.g. Figure 4 In an embodiment, P-GW 523 may communicate with the P-GW 523 via IP communication interface 425 (see, e.g. Figure 4 ) is communicatively coupled to an application server ( Figure 4 Application server 430 or Figure 5The S5 reference point between the P-GW 523 and the S-GW 522 may provide user plane tunneling and tunnel management between the P-GW 523 and the S-GW 522. The S5 reference point may also be used for S-GW 522 relocation due to the mobility of the UE 501 and whether the S-GW 522 needs to be connected to a non-colocated P-GW 523 for the required PDN connectivity. The P-GW 523 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 523 and the packet data network (PDN) 530 may be an operator-external public, private PDN, or an internal operator packet data network, such as for providing IMS services. The P-GW 523 may be coupled to the PCRF 526 via a Gx reference point.

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

[0120] Figure 6The architecture of a system 600 including a second CN 620 according to various embodiments is shown. The illustrated system 600 includes a UE 601, which may be the same or similar to the previously discussed UE 401 and UE 501; an (R) AN 610, which may be the same or similar to the previously discussed RAN 410 and RAN 510, and which may include the previously discussed RAN node 411; and a DN 603, which may be, for example, an operator service, Internet access, or a 3rd party service; and a 5GC 620. The 5GC 620 may include an AUSF 622; an AMF 621; an SMF 624; an NEF 623; a PCF 626; an NRF 625; an UDM 627; an AF 628; an UPF 602; and an NSSF 629.

[0121] UPF 602 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with DN 603, and a branch point to support multi-host PDU sessions. UPF 602 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 602 may include an uplink classifier for supporting routing of traffic flows to data networks. DN 603 may represent various network operator services, Internet access, or third-party services. DN 603 may include or be similar to the application server 430 discussed previously. UPF 602 may interact with SMF 624 via the N4 reference point between SMF 624 and UPF 602.

[0122] The AUSF 622 may store data for authentication of the UE 601 and handle authentication-related functions. The AUSF 622 may facilitate a common authentication framework for various access types. The AUSF 622 may communicate with the AMF 621 via the N12 reference point between the AMF 621 and the AUSF 622; and may communicate with the UDM 627 via the N13 reference point between the UDM 627 and the AUSF 622. In addition, the AUSF 622 may present an interface based on the Nausf service.

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

[0124] The AMF 621 may also support NAS signaling with the UE 601 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 610 and the AMF 621 for the control plane, and may be the termination point for the N3 reference point between the (R) AN 610 and the UPF 602 for the user plane. Thus, the AMF 621 may process N2 signaling for PDU sessions and QoS from the SMF 624 and the AMF 621, 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 601 and the AMF 621 via the N1 reference point between the UE 601 and the AMF 621, and relay uplink and downlink user plane packets between the UE 601 and the UPF 602. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 601. The AMF 621 may present an interface based on the Namf service, and may be an N14 reference point between the two AMF 621 and the AMF 621 and the 5G-EIR ( Figure 6 The termination point of the N17 reference point between the two (not shown).

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

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

[0127] The CM may be used to establish and release a signaling connection between the UE 601 and the AMF 621 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 601 and the CN 620, 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 601 between the AN (e.g., the RAN 610) and the AMF 621. The UE 601 may operate in one of two CM states (CM-IDLE mode or CM-CONNECTED mode). When the UE 601 operates in the CM-IDLE state / mode, the UE 601 may not have a NAS signaling connection established with the AMF 621 over the N1 interface, and there may be a (R)AN 610 signaling connection (e.g., N2 and / or N3 connection) for the UE 601. When the UE 601 operates in the CM-CONNECTED state / mode, the UE 601 may have a NAS signaling connection established with the AMF 621 through the N1 interface, and there may be a (R)AN 610 signaling connection (e.g., N2 and / or N3 connection) for the UE 601. Establishing an N2 connection between the (R)AN 610 and the AMF 621 may cause the UE 601 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the (R)AN 610 and the AMF 621 is released, the UE 601 may transition from the CM-CONNECTED mode to the CM-IDLE mode.

[0128] SMF 624 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 601 and a data network (DN) 603 identified by a data network name (DNN). A PDU session may be established upon request by UE 601, modified upon request by UE 601 and 5GC 620, and released upon request by UE 601 and 5GC 620 using NAS SM signaling exchanged over the N1 reference point between UE 601 and SMF 624. Upon request from an application server, 5GC 620 may trigger a specific application in UE 601. In response to receiving a trigger message, UE 601 may deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 601. The identified applications in UE 601 may establish a PDU session to a specific DNN. SMF 624 may check whether the UE 601 request complies with user subscription information associated with UE 601. In this regard, SMF 624 may retrieve and / or request to receive update notifications about SMF 624 level subscription data from UDM 627.

[0129] SMF 624 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 624 may be included in the system 600, which may be located between an SMF 624 in a visited network and another SMF 624 in a home network. In addition, SMF 624 may present an interface based on Nsmf services.

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

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

[0132] PCF 626 may provide for control plane functions to enforce their policy rules, and may also support a unified policy framework for managing network behavior. PCF 626 may also implement FE to access subscription information related to policy decisions in the UDR of UDM 627. PCF 626 may communicate with AMF 621 via the N15 reference point between PCF 626 and AMF 621, which may include PCF 626 in a visited network and AMF 621 in a roaming scenario. PCF 626 may communicate with AF 628 via the N5 reference point between PCF 626 and AF 628; and communicate with SMF 624 via the N7 reference point between PCF 626 and SMF 624. System 600 and / or CN 620 may also include an N24 reference point between PCF 626 (in the home network) and PCF 626 in the visited network. In addition, PCF 626 may present an interface based on Npcf services.

[0133] UDM 627 may process subscription-related information to support the handling of communication sessions by network entities, and may store subscription data of UE 601. For example, subscription data may be transmitted between UDM 627 and AMF 621 via an N8 reference point between UDM 627 and AMF. UDM 627 may include two parts: application FE and UDR ( Figure 6 FE and UDR are not shown). UDR can store subscription data and policy data of UDM 627 and PCF 626, and / or structured data for exposure and application data of NEF 623 (including PFD for application detection, application request information of multiple UE 601). Nudr service-based interface can be presented by UDR 221 to allow UDM 627, PCF 626 and NEF 623 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 624 via the N10 reference point between UDM 627 and SMF 624. UDM 627 may also support SMS management, where SMS-FE implements similar application logic as described above. In addition, UDM 627 may present an interface based on Nudm services.

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

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

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

[0137] CN 120 may also include Figure 6 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 6 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 6 (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.

[0138] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Figure 6These interfaces and reference points are omitted. In one example, CN 620 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 521) and an AMF 621, to enable intercommunication between CN 620 and CN 520. 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.

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

[0140] System 700 may include: application circuit 705, baseband circuit 710, one or more radio front end modules 715, memory circuit 720, power management integrated circuit (PMIC) 725, power tee circuit 730, network controller circuit 735, network interface connector 740, satellite positioning circuit 745 and user interface 750. In some embodiments, device 700 may include additional elements such as 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.

[0141] The application circuit 705 may include circuits such as, but not limited to, one or more processors (or 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, I2C or a general programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, a general input / output (I / O or IO), a memory card controller such as a secure digital (SD) multimedia card (MMC) or similar product, a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor (or core) of the application circuit 705 may be coupled to or may include a memory / storage element, and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 700. In some embodiments, the memory / storage element can be an on-chip memory circuit that may 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.

[0142] The processor of the application circuit 705 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 705 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 705 may include one or more Intel FPGAs. or Processor: Advanced Micro Devices Processor, Accelerated Processing Unit (APU) or Processor; 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, the system 700 may not utilize application circuits 705, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0143] In some implementations, the application circuit 705 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 implementations, the circuits of the application circuit 705 may include logic blocks or logic architectures, as well as other interconnected resources that may be programmed to perform various functions such as the procedures, methods, functions, etc. of the various embodiments discussed herein. In such an embodiment, the circuitry of the application circuit 705 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 architectures, data, etc. in a lookup table (LUT), etc.

[0144] Baseband circuit 710 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. Fig. 9 The various hardware electronic components of baseband circuit 710 are discussed.

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

[0146] The radio front end module (RFEM) 715 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). Fig. 9 Antenna array 911), and 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 RFEM715 that combines both millimeter wave antennas and sub-millimeter waves.

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

[0148] The PMIC 725 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 730 may provide power extracted from a network cable to provide both power and data connections for the infrastructure equipment 700 using a single cable.

[0149] The network controller circuit 735 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 700 via a network interface connector 740, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 735 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 735 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0150] The positioning circuit 745 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a global navigation satellite 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 745 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 745 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 745 may also be part of or interact with the baseband circuit 710 and / or RFEM 715 to communicate with nodes and components of the positioning network. The positioning circuit 745 may also provide location data and / or time data to the application circuit 705, which may use the data to synchronize operations with various infrastructure (e.g., RAN node 411, etc.), etc.

[0151] Figure 7 The components shown can communicate with each other using interface circuits that can 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 can be a proprietary bus, for example, used in a SoC-based system. Other bus / IX systems can be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, etc.

[0152] Figure 8 An example of a platform 800 (or "device 800") according to various embodiments is shown. In an embodiment, the computer platform 800 may be suitable for use as a UE 401, 501, 601, an application server 430, and / or any other element / device discussed herein. The platform 800 may include any combination of components shown in the example. The components of the platform 800 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 800, or as components otherwise incorporated within a chassis of a larger system. Figure 8The block diagram is intended to show a high-level view of the components of computer platform 800. 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.

[0153] The application circuit 805 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of an LDO, an interrupt controller, a serial interface (such as SPI), I2C or a general programmable serial interface module, an RTC, a timer (including an interval timer and a watchdog timer), a general I / O, a memory card controller (such as an SD MMC or similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuit 805 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 800. In some embodiments, the memory / storage element may be an on-chip memory circuit that may 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.

[0154] The processor of the application circuit 705 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 705 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0155] As an example, the processor of the application circuit 805 may include a processor based on Architecture Core TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA The processor of application circuit 805 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 805 can be part of a system on a chip (SoC), in which the application circuit 805 and other components are formed as a single integrated circuit or a single package, such as available from Edison Corporation TM or Galileo TM SoC board.

[0156] Additionally or alternatively, the application circuit 805 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 805 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 805 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.

[0157] Baseband circuit 810 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. Fig. 9 The various hardware electronic components of baseband circuit 810 are discussed.

[0158] The RFEM 815 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). Fig. 9 Antenna array 911), 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 815 that combines both millimeter wave antennas and sub-millimeter waves.

[0159] The memory circuit 820 may include any number and type of memory devices for providing a quantitative system memory. For example, the memory circuit 820 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 820 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 820 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 820 may be an on-chip memory or register associated with the application circuit 805. In order to provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 820 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 800 may be combined with a computer system obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0160] The removable memory circuitry 823 may include devices, circuits, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to the platform 800. 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.

[0161] The platform 800 may further include an interface circuit (not shown) for connecting external devices to the platform 800. External devices connected to the platform 800 via the interface circuit include a sensor circuit 821 and an electromechanical component (EMC) 822, and a removable memory device coupled to a removable memory circuit 823.

[0162] Sensor circuitry 821 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.

[0163] EMC 822 includes devices, modules or subsystems that are intended to enable platform 800 to change its state, position and / or orientation or to move or control mechanisms or (sub) systems. In addition, EMC 822 can be configured to generate messages / signaling and send messages / signaling to other components of platform 800 to indicate the current state of EMC 822. EMC 822 includes one or more power switches, relays (including electromechanical relays (EMR) and / or solid-state relays (SSR)), 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, platform 800 is configured to operate one or more EMC822 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients.

[0164] In some specific implementations, the interface circuit may connect the platform 800 to the positioning circuit 845. The positioning circuit 845 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 845 may include 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 845 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 845 may also be part of the baseband circuit 710 and / or the RFEM 815 or interact with it to communicate with nodes and components of the positioning network. Positioning circuitry 845 may also provide position data and / or time data to application circuitry 805 , which may use the data to synchronize operations with various infrastructure (eg, radio base stations) for use in turn-by-turn navigation applications, and the like.

[0165] In some implementations, the interface circuit may connect the platform 800 with a near field communication (NFC) circuit 840. The NFC circuit 840 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 840 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 800. The NFC circuit 840 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 840 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 840, or initiate data transfer between the NFC circuit 840 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) proximate to the platform 800.

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

[0167] A power management integrated circuit (PMIC) 825 (also referred to as “power management circuit 825”) may manage power provided to various components of the platform 800. Specifically, the PMIC 825 may control power selection, voltage regulation, battery charging, or DC-DC conversion relative to the baseband circuit 810. When the platform 800 is capable of being powered by a battery 830, for example, when the device is included in a UE 401, 501, 601, the PMIC 825 may be generally included.

[0168] In some embodiments, the PMIC 825 may control or otherwise be part of various power saving mechanisms of the platform 800. For example, if the platform 800 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 800 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 800 may transition to the RRC_Idle state, in which the platform is disconnected from the network and no operations such as channel quality feedback, handovers, etc. are performed. The platform 800 enters an extremely low power state and performs paging, in which the platform periodically wakes up to listen to the network and then powers off again. The platform 800 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 several 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.

[0169] The battery 830 can power the platform 800, but in some examples, the platform 800 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 830 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 830 can be a typical lead-acid car battery.

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

[0171] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 830. 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 800. 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 830 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.

[0172] The user interface circuit 850 includes various input / output (I / O) devices present in or connected to the platform 800, and includes one or more user interfaces designed to implement user interaction with the platform 800 and / or a peripheral component interface designed to implement interaction with the peripheral components of the platform 800. The user interface circuit 850 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, in particular, 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 800. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, the sensor circuitry 821 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 interface may include, but is not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, etc.

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

[0174] Fig. 9 9 and 915. Exemplary components of a baseband circuit 910 and a radio front end module (RFEM) 915 are shown according to various embodiments. The baseband circuit 910 corresponds to Figure 7 and Figure 8Baseband circuits 710 and 810. RFEM 915 corresponds accordingly Figure 7 and Figure 8 RFEM 715 and 815. As shown, RFEM 915 may include radio frequency (RF) circuitry 906, front end module (FEM) circuitry 908, and an antenna array 911 coupled together at least as shown.

[0175] The baseband circuit 910 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 906. 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 910 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 910 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 910 is configured to process baseband signals received from the receive signal path of the RF circuit 906 and generate baseband signals for the transmit signal path of the RF circuit 906. The baseband circuit 910 is configured to communicate with the application circuit 705 / 805 (see Figure 7 and Figure 8 ) are connected to generate and process baseband signals and control the operation of RF circuit 906. Baseband circuit 910 can handle various radio control functions.

[0176] The aforementioned circuits and / or control logic components of the baseband circuit 910 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 904A, a 4G / LTE baseband processor 904B, a 5G / NR baseband processor 904C, or some other baseband processors 904D 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 904A-D may be included in a module stored in the memory 904G and executed via a central processing unit (CPU) 904E. In other embodiments, some or all of the functions of the baseband processors 904A-D may be provided as a hardware accelerator (e.g., FPGA, ASIC, etc.) loaded with an appropriate bitstream or logic block stored in a corresponding memory unit. In various embodiments, the memory 904G may store program code of a real-time OS (RTOS), which, when executed by the CPU 904E (or other baseband processor), will enable the CPU 904E (or other baseband processor) to manage resources of the baseband circuit 910, 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 910 includes one or more audio digital signal processors (DSPs) 904F. The audio DSP 904F includes elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0177] In some embodiments, each of processors 904A-904E includes a corresponding memory interface to send data to / receive data from memory 904G. Baseband circuit 910 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 910; an interface for sending data to / receiving data from a memory external to the baseband circuit; Figures 7 to 9An application circuit interface for sending data to / receiving data from the application circuit 705 / 805; Fig. 9 RF circuit 906 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 825.

[0178] In an alternative embodiment (which can be combined with the above embodiment), the baseband circuit 910 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 interconnection subsystem. The digital baseband subsystem can also be coupled to the digital baseband interface and the mixed signal baseband subsystem via another interconnection subsystem. Each of the interconnection subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure and / or some other suitable bus or interconnection technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 910 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 915).

[0179] although Fig. 9Not shown, but in some embodiments, the baseband circuit 910 includes various processing devices (e.g., "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 910 and / or the RF circuit 906 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 a first example, the protocol processing circuit will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuit 910 and / or the RF circuit 906 are part of a Wi-Fi communication system, the protocol processing circuit may operate one or more IEEE-based protocols. In a 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., 904G) 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 910 may also support radio communications of more than one wireless protocol.

[0180] The various hardware elements of the baseband circuit 910 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 910 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 910 and the RF circuit 906 may be implemented together, such as, for example, a system on a chip (SoC) or a system-in-package (SiP). In another example, some or all of the components of the baseband circuit 910 may be implemented as a separate SoC communicatively coupled to the RF circuit 906 (or multiple instances of the RF circuit 906). In yet another example, some or all of the components of the baseband circuit 910 and the application circuit 705 / 805 may be implemented together as a separate SoC mounted to the same circuit board (e.g., a "multi-chip package").

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

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

[0183] In some embodiments, the receive signal path of the RF circuit 906 may include a mixer circuit 906a, an amplifier circuit 906b, and a filter circuit 906c. In some embodiments, the transmit signal path of the RF circuit 906 may include a filter circuit 906c and a mixer circuit 906a. The RF circuit 906 may also include a synthesizer circuit 906d, which is used to synthesize the frequency used by the mixer circuit 906a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 906a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 908 based on the synthesized frequency provided by the synthesizer circuit 906d. The amplifier circuit 906b may be configured to amplify the down-converted signal, and the filter circuit 906c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 910 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 906a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

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

[0185] In some embodiments, the mixer circuit 906a of the receive signal path and the mixer circuit 906a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 906a of the receive signal path and the mixer circuit 906a 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 906a of the receive signal path and the mixer circuit 906a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 906a of the receive signal path and the mixer circuit 906a of the transmit signal path may be configured for superheterodyne operation.

[0186] 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 906 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 910 may include a digital baseband interface to communicate with the RF circuit 906.

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

[0188] In some embodiments, synthesizer circuit 906d can 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 906d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

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

[0190] 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 910 or the application circuit 705 / 805 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 705 / 805.

[0191] The synthesizer circuit 906d of the RF circuit 906 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 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.

[0192] In some embodiments, the synthesizer circuit 906d 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 906 can include an IQ / polarity converter.

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

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

[0195] The antenna array 911 includes one or more antenna elements, each of which is configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, a digital baseband signal provided by the baseband circuit 910 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 911 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 911 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 911 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 906 and / or the FEM circuit 908 using a metal transmission line or the like.

[0196] The processor of the application circuit 705 / 805 and the processor of the baseband circuit 910 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 910 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 705 / 805 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.

[0197] Fig.10 Various protocol functions that may be implemented in a wireless communication device according to some embodiments are shown. Specifically, Fig.10 An arrangement 1000 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. Fig.10The following description, but Fig.10 Some or all aspects of the invention may also be applicable to other wireless communication network systems.

[0198] In addition to other higher layer functions not shown, the protocol layers of arrangement 1000 may also include one or more of PHY 1010, MAC 1020, RLC 1030, PDCP 1040, SDAP 1047, RRC 1055, and NAS layer 1057. These protocol layers may include one or more service access points (e.g., Fig.10 Items 1059, 1056, 1050, 1049, 1045, 1035, 1025 and 1015).

[0199] PHY 1010 can send and receive physical layer signals 1005, which can be received or sent from one or more other communication devices to one or more other communication devices. Physical layer signals 1005 may include one or more physical channels, such as those discussed herein. PHY 1010 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and switching purposes) and other measurements used by higher layers (e.g., RRC1055). PHY 1010 may 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 1010 may process a request from an instance of MAC1020 via one or more PHY-SAP 1015 and provide an indication thereto. According to some embodiments, the request and indication transmitted via PHY-SAP 1015 may include one or more transmission channels.

[0200] An instance of MAC 1020 may process requests from and provide indications to an instance of RLC 1030 via one or more MAC-SAPs 1025. These requests and indications transmitted via MAC-SAP 1025 may include one or more logical channels. MAC 1020 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 1010 via transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 1010 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.

[0201] An instance of RLC 1030 may process requests from an instance of PDCP 1040 and provide indications thereto via one or more radio link control service access points (RLC-SAPs) 1035. These requests and indications transmitted via RLC-SAPs 1035 may include one or more logical channels. RLC 1030 may operate in a variety of operating modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC 1030 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 1030 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.

[0202] An instance of PDCP 1040 may process requests from an instance of RRC 1055 and / or an instance of SDAP 1047 and provide indications thereto via one or more Packet Data Convergence Protocol Service Points (PDCP-SAP) 1045. These requests and indications transmitted via PDCP-SAP 1045 may include one or more radio bearers. PDCP 1040 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 layer SDUs when lower layers are reestablished for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0203] An instance of SDAP 1047 may process requests from one or more higher layer protocol entities and provide indications thereto via one or more SDAP-SAPs 1049. These requests and indications transmitted via SDAP-SAP 1049 may include one or more QoS flows. SDAP 1047 may map QoS flows to DRBs and vice versa, and may also mark QFIs in DL packets and UL packets. A single SDAP entity 1047 may be configured for a separate PDU session. In the UL direction, NG-RAN 410 may control the mapping of QoS flows to DRBs in two different ways (reflective mapping or explicit mapping). For reflective mapping, SDAP 1047 of UE 401 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 1047 of UE 401 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 610 may mark the DL packets with a QoS flow ID over the Uu interface. The explicit mapping may involve the RRC 1055 configuring the SDAP 1047 with explicit mapping rules of QoS flows to DRBs, which may be stored and followed by the SDAP 1047. In an embodiment, the SDAP 1047 may be used only in NR implementations and may not be used in LTE implementations.

[0204] The RRC 1055 may configure aspects of one or more protocol layers, which may include one or more instances of PHY 1010, MAC 1020, RLC 1030, PDCP 1040, and SDAP 1047, via one or more Management Service Access Points (M-SAPs). In an embodiment, an instance of the RRC 1055 may process requests from and provide indications to one or more NAS entities 1057 via one or more RRC-SAPs 1056. The main services and functions of the RRC 1055 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 401 and the RAN 410 (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.

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

[0206] According to various embodiments, one or more protocol entities of arrangement 1000 may be implemented in UE 401, RAN node 411, AMF 621 in NR implementation or MME 521 in LTE implementation, UPF 602 in NR implementation or S-GW 522 and P-GW 523 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 401, gNB 411, AMF 621, 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 411 may host the gNB's RRC 1055, SDAP 1047, and PDCP 1040 that control operations of one or more gNB-DUs, and the gNB-DUs of gNB 411 may each host the RLC 1030, MAC 1020, and PHY 1010 of gNB 411.

[0207] In a first example, the control plane protocol stack may include, in order from the highest layer to the lowest layer, NAS 1057, RRC 1055, PDCP 1040, RLC 1030, MAC 1020, and PHY 1010. In this example, an upper layer 1060 may be built on top of NAS 1057, which includes an IP layer 1061, SCTP 1062, and an application layer signaling protocol (AP) 1063.

[0208] In a NR specific implementation, AP 1063 can be an NG application protocol layer (NGAP or NG-AP) 1063 for the NG interface 413 defined between the NG-RAN node 411 and the AMF 621, or AP 1063 can be an Xn application protocol layer (XnAP or Xn-AP) 1063 for the Xn interface 412 defined between two or more RAN nodes 411.

[0209] The NG-AP 1063 may support the functionality of the NG interface 413 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN point 411 and the AMF 621. The NG-AP 1063 services may include two groups: UE-associated services (e.g., services related to the UE 401) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 411 and the AMF 621). These services may include functions including, but not limited to: a paging function for sending a paging request to the NG-RAN node 411 involved in a specific paging area; a UE context management function for allowing the AMF 621 to establish, modify and / or release the UE context in the AMF 621 and the NG-RAN node 411; a mobility function for the UE 401 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 401 and the AMF 621; a NAS node selection function for determining the association between the AMF 621 and the UE 401; 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 for transmitting a warning message via the NG interface or cancelling an ongoing warning message broadcast; a NAS signaling transport function for transmitting or rerouting NAS messages between the UE 401 and the AMF 621; a NAS node selection function for determining the association between the AMF 621 and the UE 401; a ... 420 A configuration transmission function for requesting and transmitting RAN configuration information (eg, SON information, performance measurement (PM) data, etc.) between two RAN nodes 411; and / or other similar functions.

[0210] The XnAP 1063 may support the functions of the Xn interface 412 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 411 (or E-UTRAN 510), 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 401, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, etc.

[0211] In an LTE specific implementation, the AP 1063 may be an S1 application protocol layer (S1-AP) 1063 for the S1 interface 413 defined between the E-UTRAN node 411 and the MME, or the AP 1063 may be an X2 application protocol layer (X2AP or X2-AP) 1063 for the X2 interface 412 defined between two or more E-UTRAN nodes 411.

[0212] The S1 application protocol layer (S1-AP) 1063 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 411 and the MME 521 within the LTE CN 420. The S1-AP 1063 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.

[0213] The X2AP 1063 may support the functions of the X2 interface 412 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 420, 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 unrelated to a specific UE 401, such as an X2 interface setup and reset procedure, a load indication procedure, an error indication procedure, a cell activation procedure, etc.

[0214] The SCTP layer (alternatively referred to as the SCTP / IP layer) 1062 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 1062 may ensure reliable delivery of signaling messages between the RAN node 411 and the AMF 621 / MME 521 based in part on the IP protocol supported by the IP 1061. The Internet Protocol layer (IP) 1061 may be used to perform packet addressing and routing functions. In some implementations, the IP layer 1061 may deliver and transmit PDUs using point-to-point transport. In this regard, the RAN node 411 may include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.

[0215] In a second example, the user plane protocol stack may include SDAP 1047, PDCP 1040, RLC 1030, MAC 1020, and PHY 1010 in order from the highest layer to the lowest layer. The user plane protocol stack may be used for communication between UE 401, RAN node 411, and UPF 602 in NR implementation, or communication between S-GW 522 and P-GW 523 in LTE implementation. In this example, the upper layer 1051 may be built on top of SDAP 1047 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 1052, a general packet radio service (GPRS) tunneling protocol for a user plane layer (GTP-U) 1053, and a user plane PDU layer (UP PDU) 1063.

[0216] The transport network layer 1054 (also referred to as the "transport layer") may be built on top of an IP transport, and a GTP-U 1053 may be used on top of a UDP / IP layer 1052 (including a UDP layer and an IP layer) to carry a 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.

[0217] GTP-U 1053 may be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data may be packets in any of the IPv4, IPv6, or PPP formats. UDP / IP 1052 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication of selected data flows. The RAN node 411 and the S-GW 522 may utilize the S1-U interface to exchange user plane data via a protocol stack including an L1 layer (e.g., PHY 1010), an L2 layer (e.g., MAC 1020, RLC 1030, PDCP 1040, and / or SDAP 1047), a UDP / IP layer 1052, and a GTP-U 1053. S-GW 522 and P-GW 523 may utilize an S5 / S8a interface to exchange user plane data via a protocol stack including an L1 layer, an L2 layer, a UDP / IP layer 1052, and a GTP-U 1053. As previously discussed, the NAS protocol may support the mobility and session management procedures of UE 401 to establish and maintain an IP connection between UE 401 and P-GW 523.

[0218] In addition, despite Fig.10Not shown, but an application layer may exist above the AP 1063 and / or transport network layer 1054. The application layer may be a layer where a user of the UE 401, RAN node 411, or other network element interacts with a software application, for example, executed by the application circuit 705 or the application circuit 805, respectively. The application layer may also provide one or more interfaces for the software application to interact with the communication system (such as the baseband circuit 910) of the UE 401 or RAN node 411. In some implementations, the IP layer and / or the application layer may provide the same or similar functionality as 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).

[0219] Fig.11 Components of a core network according to various embodiments are shown. The components of CN 520 may be implemented in one physical node or in separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In an embodiment, the components of CN 620 can be implemented in the same or similar manner as discussed herein with respect to the components of CN 520. 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 520 may be referred to as a network slice 1102, and each logical instance of CN 520 may provide specific network functions and network characteristics. A logical instance of a portion of CN 520 may be referred to as a network sub-slice 1104 (e.g., network sub-slice 1104 is shown as including P-GW 523 and PCRF 526).

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

[0221] Compared to 5G systems (see e.g. Figure 6), 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 the appropriate RRC message has been provided by NAS, UE601 provides auxiliary information for network slice selection in the 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.

[0222] The network slice may include the CN 620 control plane and user plane NF, the NG-RAN 610 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 UE 601 groups (e.g., enterprise users). For example, each network slice may deliver different committed services and / or may be dedicated to a specific customer or enterprise. In this example, each network slice may have a different S-NSSAI with the same SST but with a different slice differentiator. In addition, a single UE may be served simultaneously with one or more network slice instances via a 5G AN and be associated with eight different S-NSSAIs. In addition, an AMF 621 instance serving a single UE may belong to each network slice instance serving the UE 601.

[0223] Network slicing in NG-RAN 610 involves RAN slice awareness. RAN slice awareness includes differentiated processing of traffic for different network slices that have been pre-configured. Slice awareness in NG-RAN 610 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 610 supports slice activation in terms of NG-RAN functions (e.g., a set of network functions including each slice) depends on the specific implementation. NG-RAN 610 selects the RAN part of the network slice using auxiliary information provided by UE 601 or 5GC 620, which explicitly identifies one or more of the pre-configured network slices in the PLMN. NG-RAN 610 also supports resource management and policy enforcement between slices according to SLA. A single NG-RAN node can support multiple slices, and NG-RAN 610 can also apply appropriate RRM policies for SLAs in appropriate locations to each supported slice. NG-RAN 610 can also support QoS differentiation within a slice.

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

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

[0226] Some slices may be only partially available in the network. Awareness of the NG-RAN 610 of supported slices 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 610 and 5GC 620 are responsible for handling service requests for slices that may or may not be available in a given area. Admission or denial of slice access may depend on factors such as support for the slice, availability of resources, support of the requested service by the NG-RAN 610.

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

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

[0229] Fig.12 12 is a block diagram illustrating components of a NFV-enabled system 1200 according to some exemplary embodiments. System 1200 is shown to include VIM 1202, NFVI 1204, VNFM 1206, VNF 1208, EM 1210, NFVO 1212, and NM 1214.

[0230] The VIM 1202 manages resources of the NFVI 1204. The NFVI 1204 may include physical or virtual resources and applications (including a hypervisor) for executing the system 1200. The VIM 1202 may utilize the NFVI 1204 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.

[0231] The VNFM 1206 may manage the VNF 1208. The VNF 1208 may be used to perform EPC components / functions. The VNFM 1206 may manage the lifecycle of the VNF 1208 and track the performance, failures, and security of the virtual aspects of the VNF 1208. The EM 1210 may track the performance, failures, and security of the functional aspects of the VNF 1208. The tracking data from the VNFM 1206 and the EM 1210 may include, for example, PM data used by the VIM 1202 or the NFVI 1204. The VNFM 1206 and the EM 1210 may both scale up / down the number of VNFs of the system 1200.

[0232] NFVO 1212 may coordinate, authorize, release, and engage resources of NFVI 1204 in order to provide requested services (e.g., to execute EPC functions, components, or slices). NM 1214 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 VNFs may occur via EM 1210).

[0233] Fig.13is 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.13 A schematic diagram of hardware resources 1300 is shown, including one or more processors (or processor cores) 1310, one or more memory / storage devices 1320, and one or more communication resources 1330, each of which may be communicatively coupled via a bus 1340. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1302 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1300.

[0234] Processor 1310 may include, for example, processor 1312 and processor 1314. Processor 1310 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.

[0235] The memory / storage device 1320 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1320 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.

[0236] The communication resources 1330 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1304 or one or more databases 1306 via the network 1308. For example, the communication resources 1330 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.

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

[0238] Fig.14 A method 1400 of an operating system according to an embodiment of the present disclosure is shown. The method 1400 includes enabling or configuring a general PDSCH repetition transmission using a radio resource control (RRC) signaling configuration by a user equipment (UE) or an access point (AP), as shown in block 1402. The enabling of the general PDSCH repetition transmission may include transmitting and receiving one or more configuration messages between the UE and the AP to indicate and / or set the enabling, wherein the configuration message may be sent via RRC signaling. The method 1400 further includes receiving the general PDSCH repetition transmission by the UE. The steps in flowchart 1400 may be performed by one or more of the application circuit 705 or 805, the baseband circuit 710 or 810, or the processor 1314.

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

[0240] Example

[0241] Embodiment 1 may include a method for utilizing flexible RRC / MAC / DCI signaling to enable PDSCH repetition for time domain transmission / frequency domain transmission / spatial domain transmission based on a single TRP or multiple TRPs to improve the reliability of PDSCH transmission.

[0242] Embodiment 2 may include the apparatus of embodiment 1 or some other embodiment herein, wherein the method includes enabling general PDSCH repetition transmission through RRC signaling configuration.

[0243] Embodiment 3 may include the apparatus of embodiment 1 or some other embodiment herein, wherein the method includes enabling multi-TRP based repetition via RRC signaling to configure a TCI state list corresponding to a multi-TPR repetition cluster.

[0244] Embodiment 4 may include the apparatus of embodiment 1 or some other embodiment herein, wherein the method includes enabling, via a MAC CE, a list of repetition clusters, each of the repetition clusters consisting of 2, 3, or 4 activated TCI states.

[0245] Embodiment 5 may include the apparatus of embodiment 1 or some other embodiment herein, wherein the method comprises enabling by signaling an index of an activated repetition cluster by a TCI field in a DCI.

[0246] Embodiment 6 may include the apparatus of embodiment 1 or some other embodiment herein, wherein the method comprises enabling by dynamically signaling a DCI TRP / TCI status of a duplicate cluster.

[0247] Embodiment 7 may include enabling single TRP / multiple TRP based repeated transmission using RRC signaling for PDSCH configuration. And the following options (underlined in the box below) may be used to signal the relevant settings of different repeated transmission schemes.

[0248]

[0249]

[0250] Embodiment 8 may include that the parameter "pdsch-AggregationResourceAllocation" in Embodiment 7 defines a resource allocation method for each repetition copy of the first PDSCH data packet scheduled by the PDCCH.

[0251] Embodiment 9 may include that the parameters in "pdsch-AggregationResourceAllocation" in Embodiment 8 are defined as follows to enable flexible resource allocation for repeated transmissions.

[0252] The parameter "timePeriod" defines the time periodicity in terms of the number of OFDM symbols between adjacent PDSCH repetitions. When this parameter is not present, 1 time slot of 14 OFDM symbols is applied to achieve slot-level repetition.

[0253] The parameter "freqInterval" indicates the frequency spacing in terms of the number of resource blocks between adjacent repetitions. When not present, repetitions shall use the same RBs.

[0254] The parameter "antennaPortInterval" defines the interval of antenna port numbers between adjacent repetitions. When absent, different repetitions shall use the same antenna ports.

[0255] The parameter "multiTRPSize" defines the number of TRPs to use for different repetitions in the loop. When absent, repetitions based on a single TPR are used.

[0256] Embodiment 10 may include Figure 1 Different types of repeated transmissions are implemented as shown. Specifically, the following repetition options can be implemented through corresponding settings:

[0257] Option-1: Time domain repetition 102 (such as Figure 1 - (a)): timePeriod = n>0

[0258] Option-2: Frequency domain repetition 104 (as shown in 1-(b)): timePeriod = 0; freqInterval = n

[0259] Option-3: Spatial domain repetition 106 (as shown in 1-(c)): timePeriod=0; antennaPortInterval=n1 or n2.

[0260] Embodiment 11 may include a TCI state list for an RRC configurable repeating cluster, as shown underlined in the box below.

[0261]

[0262] Embodiment 12 may include the parameter "tciStateList" in embodiment 11, which defines a list of TCI states associated with corresponding TRPs to be used in repeated transmission based on multiple TRPs. When not present, repeated transmission based on a single TRP is adopted.

[0263] Embodiment 13 may include, in a PDCCH scheduling PDSCH repetition transmission, the TCI field signals a TCI state from a list defined in a tciStateList for a first PDSCH transmission, and the TCI states in the tciStateList starting from the TCI state signaled by the DCI will be cyclically used for subsequent PDSCH repetitions.

[0264] Embodiment 14 may include Figure 2 As shown, the 8 activated TCI states can be arranged in a list in increasing or decreasing order of the corresponding TCI state ID. And the index of the activated TCI state in the list can be used to identify the activated TCI state of the list of repeated clusters of activated 2 / 3 / 4 activated TCI states in the proposed MAC CE.

[0265] Embodiment 15 may include the proposed MAC CE shown in FIG. 3 for signaling all supported 2TRP / 3TRP / 4TRP based repetition clusters, eg, up to 8 possible repetition clusters.

[0266] Embodiment 16 may include that the fields of the proposed MAC CE in FIG. 3 are defined as:

[0267] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of the field is 5 bits;

[0268] BWP ID: This field contains the BWP-Id of the uplink bandwidth part to which the PUCCH transmission applies. The length of the BWP ID field is 2 bits.

[0269] TCI2-#{x,y}: This field contains the index of the yth TCI state (yth TRP) of the xth repetition cluster. The length of this field is 3 bits;

[0270] R: Reserved bit.

[0271] Embodiment 17 may include that in the case where up to 8 repetition clusters may be activated as shown in Figure 3, the TCI status field in the DDCI may signal the index of the repetition cluster activated by the MAC CE. Therefore, the repetition cluster may be dynamically changed through the DCI.

[0272] Embodiment 18 may include that, depending on the value of the RRC parameter multiTRPSize, 2, 3 or 4 TRPs may be signaled via the TCI status field in the DCI to dynamically select different TRPs for PDSCH repeated transmissions.

[0273] Example 19 may include that in one embodiment, 6 bits, 9 bits, or 14 bits should be used to signal the index of the activated TCI state of 2TRP, 3TRP, or 4TRP, respectively.

[0274] For a 2-TRP cluster, the TCI-Status field = {#index of TCI status of the 1st TRP; #index of TCI status of the 2nd TRP}.

[0275] For a 3-TRP cluster, the TCI-Status field = {#index of TCI status of the 1st TRP; #index of TCI status of the 2nd TRP; #index of TCI status of the 3rd TRP}.

[0276] For a 4-TRP cluster, the TCI-status field = {#index of TCI status of the 1st TRP; #index of TCI status of the 2nd TRP; #index of TCI status of the 3rd TRP; #index of TCI status of the 4th TRP}.

[0277] Embodiment 20 may be included in embodiment 13 or some other embodiment herein, wherein the index of the activated TCI state is determined based on the increasing / decreasing order of the TCI state ID among all activated TCI states, and since there are a maximum of 8 activated TCI states at a time, 3 bits may be used to indicate the index of each activated TCI state.

[0278] Example 21 may include in another embodiment, the TCI-state field in the DCI may signal a combination of 2, 3 or 4 TCI states out of 8 activated TCI states. Therefore, the 4-TRP repeat cluster requires 8 bits, while the method in Example 13 requires 12 bits.

[0279] Embodiment 22 may include letting N define the number of TRPs of a repeating cluster signaled as "multiTRPSize", and i n , n=0...N-1 represents the index of the (n+1)th TRP in the repetition cluster. Specifically, for a TRP with index (i0,...,i N-1 ),i n >i n+1 ,i n ∈{N-1-n, ..., 7-n}, the following values ​​may be signaled in the TCI Status field. This is shown in formula (1), where Definition n choose Nn number of combinations.

[0280] Embodiment 23 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 22, or any other method or process described herein.

[0281] Embodiment 24 may include one or more non-transitory computer-readable media, which include 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 in or related to any one of Embodiments 1 to 22 or any other method or process described herein.

[0282] Embodiment 25 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 22, or any other method or process described herein.

[0283] Embodiment 26 may include methods, techniques or processes described in or related to any one of Embodiments 1 to 22, or parts or components thereof.

[0284] Embodiment 27 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, or portions thereof, as described or related to any one of Embodiments 1 to 22.

[0285] Embodiment 28 may include a signal as described or associated with any one of Embodiments 1 to 22, or a portion or component thereof.

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

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

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

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

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

[0291] abbreviation

[0292] For the purposes of this document, the following abbreviations may be applied to the examples and implementations discussed herein but are not intended to be limiting.

[0293] 3GPP Third Generation Partnership Project

[0294] 4G Fourth Generation

[0295] 5G Fifth Generation

[0296] 5GC 5G Core Network

[0297] ACK

[0298] AF Application Function

[0299] AM Confirmation Mode

[0300] AMBR Aggregate Maximum Bit Rate

[0301] AMF Access and Mobility Management Function

[0302] AN Access Network

[0303] ANR Automatic Neighbor Relation

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

[0305] API Application Programming Interface

[0306] APN Access Point Name

[0307] ARP Assignment Retention Priority

[0308] ARQ Automatic Repeat Request

[0309] AS Access Layer

[0310] ASN.1 Abstract Syntax Notation One

[0311] AUSF authentication server function

[0312] AWGN Additive White Gaussian Noise

[0313] BCH Broadcast Channel

[0314] BER Bit Error Rate

[0315] BFD Beam Failure Detection

[0316] BLER Block Error Rate

[0317] BPSK Binary Phase Shift Keying

[0318] BRAS Broadband Remote Access Server

[0319] BSS Business Support System

[0320] BS Base Station

[0321] BSR Buffer Status Report

[0322] BW Bandwidth

[0323] BWP Bandwidth Part

[0324] C-RNTI Cell Radio Network Temporary Identifier

[0325] CA Carrier Aggregation, Certification Authority

[0326] CAPEX Capital Expenditure

[0327] CBRA Contention-based random access

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

[0329] CCA Clear Channel Assessment

[0330] CCE Control Channel Element

[0331] CCCH Common Control Channel

[0332] CE Coverage Enhancement

[0333] CDM Content Delivery Network

[0334] CDMA Code Division Multiple Access

[0335] CFRA Contention-free random access

[0336] CG Cell Group

[0337] CI Cell ID

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

[0339] CIM Common Information Model

[0340] CIR Carrier to Interference Ratio

[0341] CK Cryptographic Key

[0342] CM connection management, conditional enforcement

[0343] CMAS Commercial Mobile Alert Service

[0344] CMD command

[0345] CMS Cloud Management System

[0346] CO Conditional optional

[0347] CoMP Coordinated Multi-Point Transmission

[0348] CORESET Control Resource Set

[0349] COTS Commercial Off-the-Shelf

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

[0351] CPD Connection Point Descriptor

[0352] CPE user terminal equipment

[0353] CPICH Common Pilot Channel

[0354] CQI Channel Quality Indicator

[0355] CPU CSI processing unit, central processing unit

[0356] C / R Command / Response field bit

[0357] CRAN Cloud Radio Access Network, Cloud RAN

[0358] CRB Common Resource Block

[0359] CRC Cyclic Redundancy Check

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

[0361] C-RNTI Cell RNTI

[0362] CS Circuit Switched

[0363] CSAR Cloud Service Archive

[0364] CSI Channel State Information

[0365] CSI-IM CSI interference measurement

[0366] CSI-RS CSI reference signal

[0367] CSI-RSRP CSI reference signal received power

[0368] CSI-RSRQ CSI reference signal reception quality

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

[0370] CSMA Carrier Sense Multiple Access

[0371] CSMA / CA CSMA with collision avoidance

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

[0373] CTS Clear to Send

[0374] CW codeword

[0375] CWS Contention Window Size

[0376] D2D Device to Device

[0377] DC dual connection, direct current

[0378] DCI Downlink Control Information

[0379] DF deployment specifications

[0380] DL Downlink

[0381] DMTF Distributed Management Task Force

[0382] DPDK Data Plane Development Kit

[0383] DM-RS, DMRS Demodulation Reference Signal

[0384] DN Data Network

[0385] DRB Data Radio Bearer

[0386] DRS Discovery Reference Signal

[0387] DRX Discontinuous Reception

[0388] DSL Domain Specific Language Digital Subscriber Line

[0389] DSLAM DSL Access Multiplexer

[0390] DwPTS Downlink Pilot Time Slot

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

[0392] E2E End to End

[0393] ECCA Extended Clear Channel Assessment, Extended CCA

[0394] ECCE Enhanced Control Channel Element, Enhanced CCE

[0395] ED Energy Detection

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

[0397] EGMF exposes governance management functions

[0398] EGPRS Enhanced GPRS

[0399] EIR Equipment Identity Register

[0400] eLAA Enhanced License Assisted Access, enhanced LAA

[0401] EM Element Manager

[0402] eMBB Enhanced Mobile Broadband

[0403] EMS Element Management System

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

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

[0406] EPC Evolved Packet Core

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

[0408] EPRE Energy per resource element

[0409] EPS Evolved Packet System

[0410] EREG Enhanced REG, Enhanced Resource Element Group

[0411] ETSI European Telecommunications Standards Institute

[0412] ETWS Earthquake and Tsunami Warning System

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

[0414] E-UTRA Evolved UTRA

[0415] E-UTRAN Evolved UTRAN

[0416] EV2X Enhanced V2X

[0417] F1AP F1 Application Protocol

[0418] F1-C F1 control plane interface

[0419] F1-U F1 User Plane Interface

[0420] FACCH Fast Associated Control Channel

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

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

[0423] FACH Forward Access Channel

[0424] FAUSCH Fast Uplink Signalling Channel

[0425] FB Function Block

[0426] FBI Feedback

[0427] FCC Federal Communications Commission

[0428] FCCH Frequency Correction Channel

[0429] FDD Frequency Division Duplex

[0430] FDM Frequency Division Multiplexing

[0431] FDMA Frequency Division Multiple Access

[0432] FE Front End

[0433] FEC Forward Error Correction

[0434] FFS For further study

[0435] FFT Fast Fourier Transform

[0436] feLAA Further Enhanced Authorization Assisted Access, Further Enhanced LAA

[0437] FN Frame Number

[0438] FPGA Field Programmable Gate Array

[0439] FR Frequency Range

[0440] G-RNTI GERAN Radio Network Temporary Identity

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

[0442] GGSN Gateway GPRS Support Node

[0443] GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya

[0444] Sistema (Global Navigation Satellite System)

[0445] gNB Next Generation Node B

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

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

[0448] GNSS Global Navigation Satellite System

[0449] GPRS General Packet Radio Service

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

[0451] GTP GPRS Tunneling Protocol

[0452] GTP-U User Plane GPRS Tunneling Protocol

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

[0454] GUMMEI Globally Unique MME Identifier

[0455] GUTI Globally Unique Temporary UE Identifier

[0456] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

[0457] HANDO,HO switch

[0458] HFN Hyperframe Number

[0459] HHO Hard Handover

[0460] HLR Home Location Register

[0461] HN Home Network

[0462] HO Handover

[0463] HPLMN Home Public Land Mobile Network

[0464] HSDPA High Speed ​​Downlink Packet Access

[0465] HSN Hopping Sequence Number

[0466] HSPA High Speed ​​Packet Access

[0467] HSS Home Subscriber Server

[0468] HSUPA High Speed ​​Uplink Packet Access

[0469] HTTP Hypertext Transfer Protocol

[0470] HTTPS Hypertext Transfer Protocol Secure (https is a protocol over SSL

[0471] http / 1.1, i.e., port 443)

[0472] I-Block Information Block

[0473] ICCID Integrated Circuit Card Identifier

[0474] ICIC Inter-cell Interference Coordination

[0475] ID

[0476] IDFT Inverse Discrete Fourier Transform

[0477] IE Information Elements

[0478] IBE In-Band Emission

[0479] IEEE Institute of Electrical and Electronics Engineers

[0480] IEI Information Element Identifier

[0481] IEIDL Information Element Identifier Data Length

[0482] IETF Internet Engineering Task Force

[0483] IF Infrastructure

[0484] IM Interference Measurement, Intermodulation, IP Multimedia

[0485] IMC IMS credentials

[0486] IMEI International Mobile Equipment Identity

[0487] IMGI International Mobile Group Identity

[0488] IMPI IP Multimedia Private Identity

[0489] IMPU IP Multimedia Public Identity

[0490] IMS IP Multimedia Subsystem

[0491] IMSI International Mobile Subscriber Identity

[0492] IoT

[0493] IP Internet Protocol

[0494] Ipsec IP security, Internet Protocol security

[0495] IP-CAN IP connection access network

[0496] IP-M IP Multicast

[0497] IPv4 Internet Protocol version 4

[0498] IPv6 Internet Protocol version 6

[0499] IR

[0500] IS Synchronization

[0501] IRP Integration Reference Point

[0502] ISDN Integrated Services Digital Network

[0503] ISIM IM Service Identity Module

[0504] ISO International Organization for Standardization

[0505] ISP Internet Service Provider

[0506] IWF interworking function

[0507] I-WLAN Intercommunication WLAN

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

[0509] kB kilobyte (1000 bytes)

[0510] kbps kilobits per second

[0511] Kc encryption key

[0512] Ki Personal user authentication key

[0513] KPI Key Performance Indicator

[0514] KQI Key Quality Indicator

[0515] KSI Key Set Identifier

[0516] ksps kilosymbols per second

[0517] KVM Kernel Virtual Machine

[0518] L1 Layer 1 (physical layer)

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

[0520] L2 Layer 2 (Data Link Layer)

[0521] L3 Layer 3 (Network Layer)

[0522] LAA Authorized Assisted Access

[0523] LAN Local Area Network

[0524] LBT Listen before you speak

[0525] LCM Lifecycle Management

[0526] LCR Low Chip Rate

[0527] LCS Location Services

[0528] LCID Logical Channel ID

[0529] LI layer indicator

[0530] LLC Logical Link Control, Low Layer Compatibility

[0531] LPLMN Local PLMN

[0532] LPP LTE Positioning Protocol

[0533] LSB Least Significant Bit

[0534] LTE Long Term Evolution

[0535] LWA LTE-WLAN Aggregation

[0536] LWIP LTE / WLAN radio level integration with IPsec tunneling

[0537] LTE Long Term Evolution

[0538] M2M Machine to Machine

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

[0540] MAC Message Authentication Code (security / encrypted content)

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

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

[0543] MANO Management and Orchestration

[0544] MBMS Multimedia Broadcast and Multicast Service

[0545] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0546] MCC Mobile Country Code

[0547] MCG Master Cell Group

[0548] MCOT Maximum Channel Occupancy Time

[0549] MCS Modulation and Coding Scheme

[0550] MDAF Management Data Analysis Function

[0551] MDAS Management Data Analysis Service

[0552] MDT Minimized Drive Test

[0553] ME Mobile Equipment

[0554] MeNB Master eNB

[0555] MER Message Error Rate

[0556] MGL Measurement Gap Length

[0557] MGRP measurement gap repetition period

[0558] MIB Master Information Block, Management Information Base

[0559] MIMO Multiple Input Multiple Output

[0560] MLC Mobile Location Center

[0561] MM Mobility Management

[0562] MME Mobility Management Entity

[0563] MN Master Node

[0564] MO measurement object, mobile station initiated

[0565] MPBCH MTC Physical Broadcast Channel

[0566] MPDCCH MTC Physical Downlink Control Channel

[0567] MPDSCH MTC Physical Downlink Shared Channel

[0568] MPRACH MTC Physical Random Access Channel

[0569] MPUSCH MTC Physical Uplink Shared Channel

[0570] MPLS Multi-Protocol Label Switching

[0571] MS Mobile Station

[0572] MSB Most Significant Bit

[0573] MSC Mobile Switching Center

[0574] MSI minimum system information, MCH scheduling information

[0575] MSID Mobile Station Identifier

[0576] MSIN Mobile Station Identification Number

[0577] MSISDN Mobile Subscriber ISDN Number

[0578] MT Mobile Station Termination, Mobile Terminal

[0579] MTC Machine Type Communication

[0580] mMTC Massive MTC, Massive Machine Type Communication

[0581] MU-MIMO Multi-User MIMO

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

[0583] NACK Negative Acknowledgement

[0584] NAI Network Access Identifier

[0585] NAS Non-Access Stratum

[0586] NCT Network Connection Topology

[0587] NEC network capabilities exposed

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

[0589] NEF Network Exposure Function

[0590] NF Network Function

[0591] NFP Network Forwarding Path

[0592] NFPD Network Forwarding Path Descriptor

[0593] NFV Network Function Virtualization

[0594] NFVI NFV Infrastructure

[0595] NFVO NFV Orchestrator

[0596] NG Next Generation

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

[0598] NM Network Manager

[0599] NMS Network Management System

[0600] N-PoP Network Point of Presence

[0601] NMIB, N-MIB Narrowband MIB

[0602] NPBCH Narrowband Physical Broadcast Channel

[0603] NPDCCH Narrowband Physical Downlink Control Channel

[0604] NPDSCH Narrowband Physical Downlink Shared Channel

[0605] NPRACH Narrowband Physical Random Access Channel

[0606] NPUSCH Narrowband Physical Uplink Shared Channel

[0607] NPSS Narrowband Primary Synchronization Signal

[0608] NSSS Narrowband Secondary Synchronization Signal

[0609] NR New Radio, Adjacent Bus Relationships

[0610] NRF NF Repository Functionality

[0611] NRS Narrowband Reference Signal

[0612] NS Network Services

[0613] NSA Non-standalone operation mode

[0614] NSD Network Service Descriptor

[0615] NSR Network Service Record

[0616] NSSAI Network Slice Selection Assistance Information

[0617] S-NNSAI Single NSSAI

[0618] NSSF network slice selection function

[0619] NW Network

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

[0621] NZP Non Zero Power

[0622] O&M Operation and Maintenance

[0623] ODU2 Optical Channel Data Unit - Type 2

[0624] OFDM Orthogonal Frequency Division Multiplexing

[0625] OFDMA Orthogonal Frequency Division Multiple Access

[0626] OOB Out of Band

[0627] OOS Out of Sync

[0628] OPEX Operational Expenses

[0629] OSI Other System Information

[0630] OSS Operation Support System

[0631] OTA

[0632] PAPR Peak to Average Power Ratio

[0633] PAR Peak to Average Ratio

[0634] PBCH Physical Broadcast Channel

[0635] PC Power Control, Personal Computer

[0636] PCC primary component carrier, primary CC

[0637] PCell Primary Cell

[0638] PCI Physical Cell ID, Physical Cell Identifier

[0639] PCEF Policy and Charging Enforcement Function

[0640] PCF Policy Control Function

[0641] PCRF Policy Control and Charging Rules Function

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

[0643] PDCCH Physical Downlink Control Channel

[0644] PDCP Packet Data Convergence Protocol

[0645] PDN Packet Data Network, Public Data Network

[0646] PDSCH Physical Downlink Shared Channel

[0647] PDU Protocol Data Unit

[0648] PEI Permanent Equipment Identifier

[0649] PFD Packet Flow Description

[0650] P-GW PDN Gateway

[0651] PHICH Physical Hybrid ARQ Indicator Channel

[0652] PHY Physical Layer

[0653] PLMN Public Land Mobile Network

[0654] PIN Personal Identification Number

[0655] PM performance measurement

[0656] PMI Precoding matrix indicator

[0657] PNF Physical Network Function

[0658] PNFD Physical Network Functional Descriptor

[0659] PNFR Physical Network Function Record

[0660] POC Mobile Intercom Service

[0661] PP,PTP Point to Point

[0662] PPP Point-to-Point Protocol

[0663] PRACH Physical RACH

[0664] PRB Physical Resource Block

[0665] PRG Physical Resource Group

[0666] ProSe proximity services, proximity-based services

[0667] PRS Positioning Reference Signal

[0668] PRR Packet Receive Radio

[0669] PS Packet Service

[0670] PSBCH Physical Sidelink Broadcast Channel

[0671] PSDCH Physical Sidelink Downlink Channel

[0672] PSCCH Physical Sidelink Control Channel

[0673] PSSCH Physical Sidelink Shared Channel

[0674] PSCell Primary SCell

[0675] PSS Primary Synchronization Signal

[0676] PSTN Public Switched Telephone Network

[0677] PT-RS Phase Tracking Reference Signal

[0678] PTT Push to Talk

[0679] PUCCH Physical Uplink Control Channel

[0680] PUSCH Physical Uplink Shared Channel

[0681] QAM Quadrature Amplitude Modulation

[0682] QCI QoS Class Identifier

[0683] QCL Quasi-Co-sited

[0684] QFI QoS flow ID, QoS flow identifier

[0685] QoS Quality of Service

[0686] QPSK Quadrature (Quaternary) Phase Shift Keying

[0687] QZSS Quasi-Zenith Satellite System

[0688] RA-RNTI Random Access RNTI

[0689] RAB Radio Access Bearer, Random Access Burst

[0690] RACH Random Access Channel

[0691] RADIUS Remote Authentication Dial-In User Service

[0692] RAN Radio Access Network

[0693] RAND random number (for authentication)

[0694] RAR Random Access Response

[0695] RAT Radio Access Technology

[0696] RAU Routing Area Update

[0697] RB Resource Block, Radio Bearer

[0698] RBG Resource Block Group

[0699] REG Resource Element Group

[0700] Rel version

[0701] REQ Request

[0702] RF

[0703] RI Rank Indicator

[0704] RIV Resource Indicator Value

[0705] RL Radio Link

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

[0707] RLC AM RLC Acknowledgement Mode

[0708] RLC UM RLC Unacknowledged Mode

[0709] RLF Radio Link Failure

[0710] RLM Radio Link Monitoring

[0711] RLM-RS Reference signal for RLM

[0712] RM Registration Management

[0713] RMC Reference Measurement Channel

[0714] RMSI Remaining MSI, Remaining Minimum System Information

[0715] RN Relay Node

[0716] RNC Radio Network Controller

[0717] RNL Radio Network Layer

[0718] RNTI Radio Network Temporary Identifier

[0719] ROHC Robust Header Compression

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

[0721] RRM Radio Resource Management

[0722] RS reference signal

[0723] RSRP Reference Signal Received Power

[0724] RSRQ Reference Signal Received Quality

[0725] RSSI Received Signal Strength Indicator

[0726] RSU Road Side Unit

[0727] RSTD Reference Signal Time Difference

[0728] RTP Real Time Protocol

[0729] RTS Ready to send

[0730] RTT Round Trip Time

[0731] Rx Receive, Receiver

[0732] S1AP S1 Application Protocol

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

[0734] S1-U S1 for user plane

[0735] S-GW Service Gateway

[0736] S-RNTI SRNC Radio Network Temporary Identifier

[0737] S-TMSI SAE temporary mobile station identifier

[0738] SA Standalone Operation Mode

[0739] SAE system architecture evolution

[0740] SAP Service Access Point

[0741] SAPD Service Access Point Descriptor

[0742] SAPI Service Access Point Identifier

[0743] SCC Secondary Component Carrier, Secondary CC

[0744] SCell Secondary Cell

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

[0746] SCG Secondary Cell Group

[0747] SCM Security Context Management

[0748] SCS Subcarrier Spacing

[0749] SCTP Stream Control Transmission Protocol

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

[0751] SDL Supplemental Downlink

[0752] SDNF Structured Data Storage Network Function

[0753] SDP Service Discovery Protocol (Bluetooth related)

[0754] SDSF structured data storage function

[0755] SDU Service Data Unit

[0756] SEAF Security Anchoring Function

[0757] SeNB Secondary eNB

[0758] SEPP Security Edge Protection Proxy

[0759] SFI Slot Format Indicator

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

[0761] SFN System Frame Number

[0762] SgNB

[0763] SGSN Serving GPRS Support Node

[0764] S-GW Service Gateway

[0765] SI System Information

[0766] SI-RNTI System Information RNTI

[0767] SIB System Information Block

[0768] SIM Subscriber Identity Module

[0769] SIP Session Initiation Protocol

[0770] SiP System in Package

[0771] SL Side Link

[0772] SLA Service Level Agreement

[0773] SM Session Management

[0774] SMF session management functions

[0775] SMS Short Message Service

[0776] SMSF SMS Function

[0777] SMTC SSB-based measurement timing configuration

[0778] SN Secondary Node, Serial Number

[0779] SoC System on Chip

[0780] SON Self-Organizing Network

[0781] SpCell Special Cell

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

[0783] SPS Semi-Persistent Scheduling

[0784] SQN Serial Number

[0785] SR Scheduling Request

[0786] SRB Signalling Radio Bearer

[0787] SRS Sounding Reference Signal

[0788] SS Sync Signal

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

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

[0791] SSC Session and Service Continuity

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

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

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

[0795] SSS Secondary synchronization signal

[0796] SSSG Search Space Cluster

[0797] SSSIF Search Space Set Indicator

[0798] SST Slice / Service Type

[0799] SU-MIMO Single User MIMO

[0800] SUL Supplementary Uplink

[0801] TA Timing Advance, Tracking Area

[0802] TAC Tracking Area Code

[0803] TAG Timing Advance Group

[0804] TAU Tracking Area Updates

[0805] TB Transfer Block

[0806] TBS Transport Block Size

[0807] TBD To be defined

[0808] TCI Transmission Configuration Indicator

[0809] TCP transport communication protocol

[0810] TDD Time Division Duplex

[0811] TDM Time Division Multiplexing

[0812] TDMA Time Division Multiple Access

[0813] TE Terminal Equipment

[0814] TEID Tunnel End Point Identifier

[0815] TFT Business Flow Template

[0816] TMSI Temporary Mobile Subscriber Identity

[0817] TNL Transport Network Layer

[0818] TPC Transmit Power Control

[0819] TPMI Transmitted Precoding Matrix Indicator

[0820] TR Technical Report

[0821] TRP,TRxP Transmission Receive Point

[0822] TRS Tracking Reference Signal

[0823] TRx Transceiver

[0824] TS Technical Specifications, Technical Standards

[0825] TTI Transmission Time Interval

[0826] Tx transmission, transmitter

[0827] U-RNTI UTRAN Radio Network Temporary Identity

[0828] UART Universal Asynchronous Receiver and Transmitter

[0829] UCI Uplink Control Information

[0830] UE User Equipment

[0831] UDM Unified Data Management

[0832] UDP User Datagram Protocol

[0833] UDSF Unstructured Data Storage Network Function

[0834] UICC Universal Integrated Circuit Card

[0835] UL Uplink

[0836] UM Unconfirmed Mode

[0837] UML Unified Modeling Language

[0838] UMTS Universal Mobile Telecommunications System

[0839] UP User Plane

[0840] UPF User Plane Function

[0841] URI Uniform Resource Identifier

[0842] URL Uniform Resource Locator

[0843] URLLC Ultra-Reliable Low Latency

[0844] USB Universal Serial Bus

[0845] USIM Universal Subscriber Identity Module

[0846] USS UE-specific search space

[0847] UTRA UMTS Terrestrial Radio Access

[0848] UTRAN Universal Terrestrial Radio Access Network

[0849] UwPTS Uplink Pilot Time Slot

[0850] V2I Vehicle to Infrastructure

[0851] V2P Vehicle to Pedestrian

[0852] V2V Vehicle to Vehicle

[0853] V2X Vehicle to Everything

[0854] VIM Virtualization Infrastructure Manager

[0855] VL Virtual Link

[0856] VLAN Virtual LAN, Virtual Local Area Network

[0857] VM Virtual Machine

[0858] VNF Virtualized Network Function

[0859] VNFFG VNF forwarding graph

[0860] VNFFGD VNF Forwarding Graph Descriptor

[0861] VNFM VNF Manager

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

[0863] VPLMN Visited Public Land Mobile Network

[0864] VPN Virtual Private Network

[0865] VRB Virtual Resource Block

[0866] WiMAX Worldwide Interoperability for Microwave Access

[0867] WLAN Wireless Local Area Network

[0868] WMAN Wireless Metropolitan Area Network

[0869] WPAN Wireless Personal Area Network

[0870] X2-C X2 control plane

[0871] X2-U X2 user plane

[0872] XML Extensible Markup Language

[0873] XRES Expected User Response

[0874] XOR

[0875] ZC Zadoff-Chu

[0876] ZP Zero Power

[0877] the term

[0878] For the purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein but are not intended to be limiting.

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

[0880] 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".

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0899] 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 enabling physical downlink shared channel (PDSCH) repetition for single transmission reception point (TRP) or multiple TRP transmissions, the method comprising: PDSCH repetition transmission is enabled by a user equipment UE in response to a radio resource control RRC signaling configuration, wherein the RRC signaling configuration includes a first parameter, the first parameter defines a resource allocation for each repetition copy of a first PDSCH data packet scheduled by a physical downlink control channel PDCCH, wherein the first parameter includes a plurality of parameters, the plurality of parameters including: a second parameter defining a time periodicity based on a number of orthogonal frequency division multiple access (OFDM) symbols between adjacent repetitions; a third parameter representing a frequency spacing according to a number of resource blocks between adjacent repetitions; a fourth parameter defining an antenna port number spacing between adjacent repetitions; and a fifth parameter defining the number of TRPs to be used cyclically for different repetitions; The plurality of parameters are configured with different value settings for different types of repeated transmissions, and the different value settings of the plurality of parameters include: For time domain repetition, the value of the second parameter is set equal to a positive integer n; For frequency domain repetition, the value of the second parameter is set equal to 0, and the value of the third parameter is set equal to n; For spatial domain repetition, the value of the second parameter is set equal to 0, and the value of the fourth parameter is set to n1 or n2, where n1 and n2 are different antenna port number intervals defined for the fourth parameter; and The PDSCH repetition transmission is received by the UE. 2 . The method according to claim 1 , wherein the PDSCH repetition transmission is based on time domain transmission, frequency domain transmission or space domain transmission.

3. The method according to claim 1, wherein the multiple parameters also include a sixth parameter, which is used to define a transmission configuration indicator TCI state list associated with the corresponding TRP to be used in the repetition based on multi-TRP transmission.

4. The method of claim 3, further comprising enabling, by the UE, a list of repetition clusters, each of the repetition clusters consisting of 2 or more activated TCI states corresponding to the TCI state list.

5. The method according to claim 1, further comprising signaling, by the UE, an index of the activated repetition cluster through a transmission configuration indicator (TCI) field in downlink control information (DCI).

6. The method of claim 1, further comprising dynamically signaling, by the UE, a downlink control information (DCI) TRP or a transmission configuration indicator (TCI) status of a repetition cluster.

7. The method according to claim 1, further comprising scheduling, by the UE, a PDCCH for the PDSCH repetition transmission, wherein a TCI field of a transmission configuration indicator TCI state is cyclically used for subsequent PDSCH repetition transmissions.

8. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a processor, cause the processor to perform operations including: Physical downlink shared channel PDSCH repetition transmission is enabled by radio resource control RRC signaling configuration, wherein the RRC signaling configuration includes a first parameter, the first parameter defines resource allocation for each repetition copy of a first PDSCH data packet scheduled by a physical downlink control channel PDCCH, wherein the first parameter includes a plurality of parameters, the plurality of parameters including: a second parameter defining a time periodicity based on a number of orthogonal frequency division multiple access (OFDM) symbols between adjacent repetitions; a third parameter representing a frequency spacing according to a number of resource blocks between adjacent repetitions; a fourth parameter, the fourth parameter defining an antenna port number interval between adjacent repetitions; as well as a fifth parameter defining the number of TRPs to be used cyclically for different repetitions; The plurality of parameters are configured with different value settings for different types of repeated transmissions, and the different value settings of the plurality of parameters include: For time domain repetition, the value of the second parameter is set equal to a positive integer n; For frequency domain repetition, the value of the second parameter is set equal to 0, and the value of the third parameter is set equal to n; For spatial domain repetition, the value of the second parameter is set equal to 0, and the value of the fourth parameter is set to n1 or n2, where n1 and n2 are different antenna port number intervals defined for the fourth parameter; and This enables receiving repeated transmission of the PDSCH. 9 . The non-transitory computer-readable medium of claim 8 , wherein the PDSCH repetition transmission is based on time domain transmission, frequency domain transmission, or space domain transmission.

10. The non-transitory computer-readable medium of claim 8, wherein the plurality of parameters further comprises a sixth parameter for defining a transmission configuration indicator (TCI) state list associated with corresponding TRPs to be used in repetitions based on multi-TRP transmissions.

11. The non-transitory computer readable medium of claim 10, wherein the operations further comprise enabling a list of repeating clusters, each of the repeating clusters consisting of 2 or more activated TCI states corresponding to the TCI state list.

12. The non-transitory computer-readable medium of claim 8, wherein the operations further comprise signaling an index of the activated repetition cluster through a transmission configuration indicator (TCI) field in downlink control information (DCI).

13. The non-transitory computer-readable medium of claim 8, wherein the operations further comprise dynamically signaling a downlink control information (DCI) TRP or a transmission configuration indicator (TCI) status of a repetition cluster.

14. The non-transitory computer readable medium of claim 8, wherein the operations further comprise scheduling a PDCCH for the PDSCH repetition transmission, wherein a TCI field of a transmission configuration indicator (TCI) state is cyclically used for subsequent PDSCH repetition transmissions.

15. A user equipment UE, the UE comprising: A processor, the processor being configured to: A physical downlink shared channel (PDSCH) repetition transmission is enabled in response to a radio resource control (RRC) signaling configuration, wherein the RRC signaling configuration includes a first parameter, the first parameter defining a resource allocation for each repetition copy of a first PDSCH data packet scheduled by a physical downlink control channel (PDCCH), wherein the first parameter includes a plurality of parameters, the plurality of parameters including: a second parameter defining a time periodicity based on a number of orthogonal frequency division multiple access (OFDM) symbols between adjacent repetitions; a third parameter representing a frequency spacing according to a number of resource blocks between adjacent repetitions; a fourth parameter defining an antenna port number spacing between adjacent repetitions; and a fifth parameter defining the number of TRPs to be used cyclically for different repetitions; The plurality of parameters are configured with different value settings for different types of repeated transmissions, and the different value settings of the plurality of parameters include: For time domain repetition, the value of the second parameter is set equal to a positive integer n; For frequency domain repetition, the value of the second parameter is set equal to 0, and the value of the third parameter is set equal to n; For spatial domain repetition, the value of the second parameter is set equal to 0, and the value of the fourth parameter is set to n1 or n2, where n1 and n2 are different antenna port number intervals defined for the fourth parameter; and A radio frequency integrated circuit is coupled to the processor, and is configured to receive the PDSCH repetitive transmission. 16 . The UE according to claim 15 , wherein the PDSCH repetition transmission is based on time domain transmission, frequency domain transmission or space domain transmission.

17. The UE according to claim 15, wherein the multiple parameters also include a sixth parameter, and the sixth parameter is used to define a transmission configuration indicator TCI state list associated with the corresponding TRP to be used in the repetition based on multi-TRP transmission.

18. The UE of claim 17, wherein the processor is further configured to enable a list of repetition clusters, each of the repetition clusters consisting of 2 or more activated TCI states corresponding to the TCI state list.

19. The UE of claim 15, wherein the processor is further configured to signal an index of the activated repetition cluster through a transmission configuration indicator (TCI) field in downlink control information (DCI).

20. The UE of claim 15, wherein the processor is further configured to dynamically signal a downlink control information (DCI TRP) or a transmission configuration indicator (TCI) status of a repetition cluster.

Images