Timing advance and channel status information enhancement

Abstract

The present disclosure generally relates to wireless communication technologies, network topologies, and implementations of communication devices, and more particularly, to a multi-transmit receive point (multi-TRP) uplink (UL) transmission scheme. The multi-TRP UL transmission scheme relates to timing advance (TA) association for multi-TRP operation, extension of channel state information (CSI), and extension of codebook structure. To extend the performance of the Rel-16 codebook, a new codebook structure is constructed by extending the Rel-16 codebook in the time dimension (TD) using mutually orthogonal discrete Fourier transform (DFT) bases while preserving the Rel-16 codebook structure in the spatial dimension (SD) and the frequency dimension (FD).

Description

[Technical Field]

[0001] [Cross-reference of related applications] This application claims priority to U.S. Provisional Application No. 63 / 336,991, filed on 29 April 2022, and U.S. Provisional Application No. 63 / 485,804, filed on 17 February 2023, the entire contents of which are incorporated herein by reference.

[0002] [Technical field] This disclosure generally relates to wireless communication technologies, network topologies, and implementations of communication devices, and more particularly to multi-transmission-reception-point (TRP) uplink (UL) transmission schemes, extensions to channel state information (CSI), and extensions to codebook structures. [Background technology]

[0003] Fifth-generation (5G) wireless networks support multi-TRP (multiple transmit / receive point) operation to provide improved reliability, coverage, and capacity performance. In multi-TRP operation, a serving cell can schedule user equipment (UE) from two transmit / receive points (TRPs) to provide better coverage, reliability, and / or data rates for physical downlink shared channels (PDSCH), physical downlink control channels (PDCCH), physical uplink shared channels (PUSCH), and physical uplink control channels (PUCCH). [Brief explanation of the drawing]

[0004] Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. For the sake of this description, similar reference numerals indicate similar structural elements. Embodiments are shown in the figures of the accompanying drawings as examples, not as limitations. [Figure 1] This shows an example of simultaneous multi-transmission / reception point (TRP) uplink (UL) transmission. [Figure 2] This shows exemplary UL-downlink (DL) timing relationships and various exemplary timing advance command messages. [Figure 3] An example of a user device precoder prediction method is shown. [Figure 4] An exemplary wireless access network node precoder instruction scheme is shown. [Figure 5] An exemplary measurement timing diagram is shown, including the time gap between adjacent measurements within the measurement time window. [Figure 6] An exemplary 3D codebook structure is shown. [Figure 7] This illustrates an exemplary wireless network. [Figure 8] This illustrates an exemplary wireless network. [Figure 9] This shows exemplary hardware resources. [Modes for carrying out the invention]

[0005] This disclosure describes techniques and methods for associating timing advances (TA) for multi-TRP (mTRP) operation and channel state information (CSI) enhancement. To enhance the performance of the Rel-16 codebook, a new codebook structure is constructed by extending the Rel-16 codebook in the time dimension (TD) using mutually orthogonal discrete Fourier transforms (DFTs) while preserving the Rel-16 codebook structure in the spatial dimension (SD) and frequency dimension (FD).

[0006] 1. Forms of Multi-TRP, Timing Advance (TA), and Channel Status Information (CSI) The new radio (NR) in Release (Rel-) 17 supports repetition / transmission of the physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH) of mTRPs, meaning that the same uplink (UL) data or control information can be transmitted to multiple TRPs as multiple repetitions / transmissions in multiple time slots or sub-slots. However, in each time slot or sub-slot, there can only be one UL transmission opportunity directed to a particular TRP. To utilize multiple TRPs more efficiently, the Rel-18 5G / NR system supports a simultaneous mTRP transmission scheme in ULs. In particular, to increase overall capacity and transmission robustness against potential channel interference, UE102 may transmit signals targeting two or more TRPs simultaneously, as shown in Figure 1.

[0007] Figure 1 shows an example of mTRP operation 100. In mTRP operation, a serving cell can schedule UE102 from two or more TRPs (e.g., TRP108-1 and TRP108-2 in Figure 1) to provide better coverage, reliability and / or data rate for PDSCH, PDCCH, PUSCH and PUCCH. In the example in Figure 1, UE102 transmits a first beam 106-1 to (or toward) a first TRP108-1 and a second beam 106-2 to (or toward) a second TRP108-2. Furthermore, the first beam 106-1 (within band 1) includes a first PUSCH iteration (rep1) to TRP108-1, and the second beam 106-2 (within band 2) includes a second PUSCH iteration (rep2) to TRP108-2. Here, UE102 may be the same as or similar to UE702, UE802, hardware resource 900 and / or any other UE discussed herein, and TRP108 may be the same as or similar to RAN704, AP706, AN708, AN804, hardware resource 900 and / or any other AN / NAN discussed herein.

[0008] For mTRP push iterations / transmissions, UE102 performs push transmissions of the same content toward two or more TRPs 108 according to instructions in a semi-statically configured grant provided via single downlink control information (DCI) or radio resource control (RRC) signaling, with the corresponding beam directions 106 associated with different spatial relationships. For mTRP push iterations, UE102 performs push transmissions of the same content toward two or more TRPs 108, with the corresponding beam directions 106 associated with different spatial relationships. For inter-cell multi-TRP operation, for mDCI push transmissions, the transmission configuration indicator (TCI) state can be associated with a synchronization signal block (SSB) having a physical cell identifier (PCI) different from the serving cell's PCI. An activated TCI state can be associated with at most one PCI different from the serving cell's PCI at any given time.

[0009] To support simultaneous mTRP transmission in UL, different transmission methods can be considered. For example, mTRP transmission can be scheduled by either a single DCI (sDCI) or multiple DCIs (mDCI), mTRP transmission opportunities can be multiplexed in the time domain (TD), frequency domain (FD), and spatial domain (SD), and resource allocation for mTRP transmission can be different, etc.

[0010] In NR, timing advance ("TA" or "T") ADV“) is a parameter or command transmitted by a base station (BS) (e.g., TRP108, RAN704, AP706, AN708, AN804, hardware resource 900, etc.) to UE102 to adjust UL (e.g., PUSCH, PUCCH, sounding reference signal (SRS), etc.) transmission timing. UE102 uses TA to adjust its UL frame timing with respect to the DL frame timing.

[0011] Figure 2 shows an exemplary UL-DL timing relationship 200, and the parameter T TA represents the TA between DL frame i and UL frame i. The UL frame i for transmission from UE102 starts at T TA before the start of the corresponding DL frame i at UE102. The parameter T TA can be calculated according to the following formula.

[0012] T TA =(N TA +N TA,offset +N TA,adj common +N TA,adj UE )T c In the above formula, N TA is the TA between DL and UL excluding msgA transmission on PUSCH, and N TA = 0 is used (see, for example, [TS38213] §4.2). N TA,offset is a fixed offset used to calculate the TA (see, for example, [TS38213] §4.2). N TA,adj common is derived from the upper layer parameters TACommon, TACommonDrift, and TACommonDriftVariation if configured, and otherwise, N TA,adj common = 0 is the network controlled timing correction (see, for example, [TS38213] §4.2). N TA,adj UEIf configured, it is calculated by UE102 based on the UE position and serving-satellite-ephemeris-related upper layer parameters; otherwise, N TA,adj UE This is a UE derivation timing correction where = 0 (see, for example, [TS38213] §4.2). c is the basic time unit of NR (see, for example, [TS38211] §4.1).

[0013] BS determines the desired TA configuration and provides the TA to UE102. UE102 uses the provided TA to determine its UL transmission timing (e.g., T) relative to the observed DL reception timing of UE102. TA ) determines. For example, the BS measures the time difference between the reception of a UL transmission (e.g., PUSCH, PUCCH, SRS, etc.) and the local subframe timing, and as a result the BS knows whether the UL transmission is arriving at the BS too early or too late. The BS then calculates or determines the TA, generates a TA command (TAC, TA command), and sends the TA / TAC to the UE120. The UE102 adjusts the next / scheduled UL transmission according to the TAC value to match the UL transmission with the BS's subframe timing. For example, if the TAC value is positive, the UE102 transmits earlier, and if the TAC value is negative, the UE102 transmits later.

[0014] The BS is responsible for maintaining the TA in order to keep Layer 1 (L1, layer 1) synchronized. Serving cells that have the same TA applied to their UL and use the same timing reference cell are grouped into a TA group (TAG). A TAG is a group of serving cells that, for cells configured by the RRC and UL, use the same timing reference cell and the same TA value. According to various embodiments, a serving cell or TAG may use at least two different TA values, as described below.

[0015] Each TAG includes at least one serving cell having a configured UL, and the mapping of each serving cell to a TAG is configured by RRC. For example, an RRC message may include a serving cell configuration (e.g., a ServingCellConfig information element (IE)) used to configure (e.g., add or modify) a UE102 in the serving cell. The configured serving cell may be a special cell (SpCell) or a secondary cell (SCell) in a master cell group (MCG) or a secondary cell group (SCG). The ServingCellConfig IE includes a "tag-Id" field containing the TAG ID to which the serving cell belongs, as described herein and / or specified in [TS38321]. RRC entities / layers also configure the following parameters to maintain UL time alignment: a timeAlignmentTimer (per TAG) that controls the length of time the MAC entity perceives when a serving cell belonging to the associated TAG is UL time aligned; an inactivePosSRS-TimeAlignmentTimer (see, e.g., Section 5.26 of [TS38321]) that controls the length of time the MAC entity perceives when a positioning SRS transmission in RRC_INACTIVE is UL time aligned; and / or a cg-SDT-TimeAlignmentTimer that controls the length of time the MAC entity perceives when a configured grant-based small data transmission (CG-SDT) is UL time aligned. For primary TAGs (PTAGs), UE102 uses the primary cell (PCell) as the timing reference, except for shared spectral channel access where SCells can also be used in certain cases (see, e.g., §7.1 of [TS38133]).Regarding secondary TAGs (STAG, secondary TAG), UE102 may use any of the activated SCells of this TAG as the timing reference cell, but it should not change them unless necessary.

[0016] Alternatively, UE102 may have a parameter for the serving cell n-TimingAdvanceOffset, which is the value of the TA offset of the serving cell N. TA,offset This can be provided. If the n-TimingAdvanceOffset parameter for the serving cell is not provided to UE102, UE102 will use the default value N for the TA offset for the serving cell, as described in [TS38133]. TA,offset Determine the same TA offset value N if UE102 consists of two UL carriers for the serving cell. TA,offset This applies to both carriers. Upon receiving the TAC for the TAG, UE102 assumes that the value N is the same for all serving cells within the TAG. TA,offset Based on this, and also based on the received TAC, the UL timing for UL transmissions (e.g., PUSCH, SRS, PUCCH, etc.) on all serving cells within the TAG is adjusted, where the UL timing for UL transmissions is the same for all serving cells within the TAG. 2 μ Regarding the subcarrier spacing (SCS) of 15kHz, the TAC for TAG is 16·64·T c / 2 μ This shows the change in UL timing relative to the current UL timing for TAGs that are multiples of [ ]. The start timing of the random access (RA) preamble is described in [TS38211].

[0017] TA updates are signaled to UE102 by BS via a TAC medium access control (MAC) control element (CE), an absolute TAC (aTAC) MAC CE, or a random access response (RAR). Figure 2 also shows an exemplary TAC MAC CE210, which is identified by a MAC subheader having a logical channel ID (LCID) as specified in Table 6.2.1-1 of [TS38321] (for example, the LCID of TAC MAC CE210 has a code point / index value of "61"). TAC MAC CE210 has a fixed size and contains a single octet. TAC MAC CE210 includes a 2-bit TAG Identity (TAG ID) field indicating the TAG identity / identifier (TAG-Id) of the addressed TAG. In some examples, TAGs containing SpCells have a TAG-Id of 0. TAC MAC CE210 also has an index value T A It includes a 6-bit TAC field containing or indicating (e.g., 0, 1, 2...63), which is used to control the amount of timing adjustment that the MAC entity must apply (see, e.g., [TS38213]). TAC MAC CE210, TAC for TAG ("T A ) is T A Current N based on index values ​​=0, 1, 2, ..., 63 TA Value ("N TA_old )'s new N TA Value ("N TA_new This indicates the adjustment to "), and for 2μ·15kHz SCS, N TA_new =N TA_old +T A -31)·16·64 / 2 μ That is the case.

[0018] Figure 2 also shows exemplary aTAC MAC CE215 and exemplary RAR MAC CE220. The aTAC MAC CE215 is identified by a MAC subheader with an extended LCID (eLCID) as specified in Table 6.2.1-1b of [TS38321] (e.g., code point value "252" and index value "316"). The aTAC MAC CE215 has a fixed size and contains 2 octets. The aTAC MAC CE215 contains a set of reserved fields (R), each of which is 1 bit and set to 0. The aTAC MAC CE215 also has an index value T A It includes a 12-bit TAC field that either contains or indicates the amount of timing adjustment that the MAC entity must apply (see, for example, [TS38213]). In some implementations, the aTAC MAC CE215 may include a 2-bit TAG ID field instead of two of the reserved bits, or the 2-bit TAG ID field may be part of the 12-bit TAC field.

[0019] The RAR MAC CE220 (also known as "MAC RAR220") is identified by a MAC subheader having a 6-bit RA preamble identifier (RAPID) field (for example, the RAPID field contains or identifies the transmitted RA preamble and / or preamble index (see, e.g., [TS38321] §5.1.3)). The MAC RAR220 has a fixed size and contains 7 octets. The MAC RAR220 includes a 1-bit reserved field (R) set to 0. The MAC RAR220 also contains an index value T used to control the amount of timing adjustment that the MAC entity must apply. AIt includes a 12-bit TAC field that contains or indicates (see, e.g., [TS38213]), a 27-bit UL Grant field that contains or indicates resources to be used on the uplink in [TS38213], and a 16-bit Temporary C-RNTI field that contains or indicates a temporary identity used by the MAC entity during the RA procedure. In some examples, the MAC RAR220 is transmitted in Msg2 during a Type-1 L1 RA procedure, or in MsgA or MsgB during a Type-2 L1 RA procedure (see, e.g., [TS38213] and [TS38300]). In some implementations, the MAC RAR220 may include a 2-bit TAG ID field instead of two of the reserved bits, or the 2-bit TAG ID field may be part of the 12-bit TAC field. The MAC payload for the MsgB message (also called fallbackRAR) may contain the same or similar payload as the MAC RAR220. Furthermore, or alternatively, the same or similar TAC fields may also be included in the successRAR MAC PDU. For RAR MAC CE220 or aTAC MAC CE215, the TAC ("T") for TAG. A ) is T A =N based on index values ​​of 0, 1, 2, ..., 3846 TA This shows that 2 μ The amount of time adjustment for a TAG with a 15kHz SCS is N TA =T A ·16·64 / 2 μ N TA This is defined in [TS38211] and relates to the SCS of the first UL transmission from the UE after the reception of the RAR MAC CE220 or aTAC MAC CE215.

[0020] Furthermore, the TAC starts or restarts one or more TAG-specific timers, which indicate whether L1 can be synchronized or not. When the timers are operating, L1 is considered synchronized; otherwise, L1 is considered asynchronous, in which case UL transmission can only be performed through MSG1 (e.g., preamble transmission for a 4-step RA type RA procedure) and / or MSGA (e.g., preamble and payload transmission for a 2-step RA type RA procedure). In one example, when the TAC MAC CE is received by UE102, N TAIf the designated TAG is maintained, the MAC entity of UE102 applies the TAC to the designated TAG, starts or restarts the inactivePosSRS-TimeAlignmentTimer associated with the designated TAG if there is an ongoing positioning SRS transmission in RRC_INACTIVE, starts or restarts the cg-SDT-TimeAlignmentTimer associated with the designated TAG if the CG-SDT procedure is triggered, and otherwise starts or restarts the timeAlignmentTimer associated with the designated TAG (see, for example, [TS38321] §5.2). In another example, if the TAC is received in a RAR message to a serving cell belonging to a TAG or a MsgB to a SpCell, and the RA preamble is not selected by the MAC entity among the competition-based RA preambles, the MAC entity of UE102 applies the TAC to this TAG and starts or restarts the timeAlignmentTimer associated with this TAG. Otherwise, if the timeAlignmentTimer associated with this TAG is not operating, the MAC entity of UT102 applies a TAC to this TAG, starts the timeAlignmentTimer associated with this TAG, and stops the timeAlignmentTimer associated with this TAG when it is deemed that the conflict resolution was unsuccessful as described in [TS38321]§5.1.5, or when it is deemed that the conflict resolution was successful for the SI request as described in [TS38321]§5.1.5 after transmitting HARQ feedback to the MAC PDU containing the UE conflict resolution identity MAC CE. If it is deemed that the conflict resolution was unsuccessful as described in [TS38321]§5.1.5, and if a triggered CG-SDT procedure is in progress as described in [TS38321]§5.27, the MAC entity of UE102 TASet the value to the value before applying the received TAC. If the conflict resolution for the RA procedure is deemed successful while the CG-SDT procedure is in progress, the MAC entity of UE102 stops the timeAlignmentTimer associated with this TAG and starts or restarts the cg-SDT-TimeAlignmentTimer associated with this TAG. If the conflict resolution for the RA procedure is deemed successful while the SRS transmission in RRC_INACTIVE is in progress, the MAC entity of UE102 starts or restarts the inactivePosSRS-TimeAlignmentTimer associated with this TAG. Otherwise, the MAC entity of UE102 ignores the received TAC.

[0021] 3GPP® Rel-16 includes TAs for single-TRP. For example, a serving cell is associated with one UL timing, and multiple serving cells within the same TAG are associated with the same UL timing. However, TAs for single-TRP do not work well for mTRP-based transmissions because transmissions to different TRPs may have different TAs. Rel-18 supports mTRP operation, including simultaneous multi-panel transmissions, which requires a serving cell to be associated with two UL timings (two TA fields). Furthermore, a serving cell may transition from single-TRP operation to mDCI mTRP operation, and vice versa, and the TA-related issues should be specified.

[0022] 1.1. TA Extension As described above, two TAs can be calculated to support mTRP operation, including simultaneous multi-panel transmissions. To properly apply the TA values ​​to UL transmissions, UE102 needs to associate the UL transmission with the TA value field (e.g., the TAC field in MAC CE210, 215, or 220). Note that DL and UL transmissions do not need to be associated with the same TRP108 (or TCI state), so reusing the parameter CORESETPoolIndex may not be sufficient. In that sense, such operation does not need to be limited to mDCI mTRP only.

[0023] In the case of intracellular mDCI mTRP operation, each TRP108 may benefit from estimating the TA from the PRACH transmission, and the TRP identifier (TRP-Id) is associated with the TA value contained in the RAR and / or MAC CE. Thus, in some embodiments, a serving cell is associated with at least two TA fields, and the activation / deactivation of the TA fields is per serving cell. Furthermore or alternatively, a unified TCI state and UL-TCI state are associated with the TRP-Id, and the TRP-Id is associated with the TA.

[0024] TRP-Id is an identifier or identity of TRP108 within a RAN node or cell, and may be represented as an integer, string, etc. Furthermore, or alternatively, TRP-Id may be based on one or more other identifiers and / or network addresses, such as cell identity (e.g., NR cell identity), PCI, NCGI, NG-RAN CGI, ARFCN, DL-PRS-ID, PLMN identity, cell sub-ID, NRPPa transaction ID and / or any of those discussed herein. In some embodiments, TRP-Id is, for example, AreaID-CellList IE, DL-PRS-ID-Info IE, ARFCN-ValueNR IE, NCGI IE, NR-PhysCellId IE, TRP Information IE, TRP ID IE (see, for example, [TS38455] §9.2.24), NRPPa Transaction ID IE, and / or any other suitable configuration / IE such as any of those discussed herein (e.g., 3GPP TS 37.355 v17.4.0 (2023-03-31) ("[TS37355]"), 3GPP TS 38.305 v17.4.0 (2023-03-28) and 3GPP TS 38.455 Appropriate configurations and / or information elements (IEs) may be provided, such as in v17.4.0 (2023-04-03) ("[TS38455]")). These configurations / IEs may be included in appropriate RRC messages, non-access stratum (NAS) messages, system information (SI) broadcasts, LTE positioning protocol (LPP) messages, NR positioning protocol (NRPP) messages, etc.

[0025] In various embodiments, the TAG-Id is indicated to or provided to the UE102 using configurations and / or IEs in any combination of the following examples.

[0026] In the first example, the TAG and / or TA are associated with an SRS resource (SRS-Resource) and / or an SRS resource ID (SRS-ResourceId). In this example, the network (NW) (e.g., BS, RAN node, or other network element) uses one or more SRS resource indicator (SRI) fields in the DCI (e.g., DCI format 0_1, 0_2, etc.) to indicate the TAG-Id to UE102. If the SRI field is not present, a default TAG is assumed by UE102.

[0027] In the second example, the TAG and / or TA are associated with an SRS resource set (SRS-ResourceSet) and / or an SRS resource set ID (srs-ResourceSetId). In this example, the NW (e.g., BS, RAN node, or other network element) uses the SRS resource set indicator field in the DCI (e.g., DCI format 0_1, 0_2, etc.) to indicate the TAG-Id to UE102. If the SRS resource set indicator field does not exist, a default TAG may be assumed by UE102. Alternatively, the TAG / TA are associated with an SRS resource set / SRS resource set ID associated with a "codebook" or "non-codebook" type.

[0028] In the third example, the TAG and / or TA are associated with the SRS-SpatialRelationInfo field / IE in the SRS-Config, the SRS-SpatialRelationInfo is applied to FR1, and UE102 ignores the referenceSignal IE as shown in Table 1.1-1. The SRS-Config IE is used to configure sounding reference signal (SRS) transmission. The configuration defines a list of SRS-Resources, a list of SRS-PosResources, a list of SRS-PosResourceSets, and a list of SRS-ResourceSets. Each resource set defines a set of SRS-Resources or SRS-PosResources. The network uses the configured aperiodicSRS-ResourceTrigger (L1 DCI) to trigger the transmission of a set of SRS-Resources or SRS-PosResources. In this example, the parameter "tag-Id" is the TAG ID associated with this SRS-SpatialRelationInfo.

[0029] [Table 1] In the fourth example, the TAG and / or TA are associated with PUSCH power control information, such as the SRI-PUSCH-PowerControl IE (see, for example, Table 1.1-2) within the PUSCH power control configuration (PUSCH-PowerControl). The PUSCH-PowerControl configuration / IE is used to configure UE-specific power control parameters for PUSCH. If there is no instruction to the UE102 for SRI-PUSCH-PowerControl information, a default TAG is assumed. In this example, the parameter "tag-Id" is the TAG ID associated with this SRI-PUSCH-PowerControl.

[0030] [Table 2] In the fifth example, the TAG and / or TA are associated with a PUCCH resource. This association may be indicated to UE102 using the RRC configuration or some other suitable mechanism. The PUCCH resource is indicated to UE102 using a field in the DCI (e.g., the PUCCH resource indicator field).

[0031] In the sixth example, in FR1, the TAG and / or TA are associated with PUCCH power control information, such as the PowerControlSetInfo IE (see, for example, Table 1.1-3) within the PUCCH power control configuration (PUCCH-PowerControl). The PUCCH-PowerControl configuration / IE is used to configure UE-specific parameters for PUCCH power control. In this example, the parameter "tag-Id" is the TAG ID associated with this SRI-PUSCH-PowerControl.

[0032] [Table 3] In the seventh example, in FR1, the TAG and / or TA are associated with PUCCH spatial relation information such as PUCCH-SpatialRelationInfo IE, as shown in Table 1.1-4. PUCCH-SpatialRelationInfo IE is used to configure the spatial settings for PUCCH transmission and the parameters for PUCCH power control (see, for example, [TS38213] §9.2.2). In this example, the parameter "tag-Id" is the TAG ID associated with this PUCCH-SpatialRelationInfo.

[0033] [Table 4] 1.2. CSI Expansion The extension of CSI is also within the scope of Rel-18. For example, Rel-18 aims to extend CSI processing under scenarios where the UE has high or moderate mobility and to design a new codebook for transmission.

[0034] Mathematically, the Rel-16 codebook can be expressed as follows:

[0035]

number

[0036]

number

[0037] CSI-RS is transmitted from the base station to UE102 for channel estimation. Rel-18 aims to extend CSI processing under scenarios where UE102 has high or moderate mobility.

[0038] In some embodiments, CSI prediction can be applied on the UE102 side. As shown in Figure 3, UE102 measures the CSI-RS instance within the time window at time t1, determines the predicted Doppler domain compressed CSI associated with the reference resource at time t3, and reports it at time t2. The specific prediction algorithm (or prediction service) used may be based on the UE implementation. As an example, the prediction algorithm (or prediction service) may include one or more machine learning (ML) models / algorithms, such as artificial neural networks, including, for example, any of those discussed herein. UE102 accesses unquantized instantaneous channel information that may be more suitable for prediction. At the same time, the complexity of the UE should be taken into consideration, and possibly new RAN4 work may also be required to establish prediction CSI tests to ensure performance requirements.

[0039] Alternatively, CSI prediction can be applied on the RAN node side (e.g., gNB716, TRP108, etc.). As shown in Figure 4, UE102 measures the time window of the CSI-RS instance at time t1, determines the Doppler domain compressed CSI associated with the reference resource at time t2, and reports it at time t3. Performing CSI prediction based on the compression information received from UE102 depends on the implementation of the RAN node (e.g., gNB716, TRP108, etc.).

[0040] Furthermore, or alternatively, the sampling period and measurement time window for CSI processing should be optimized. As shown in Figure 5, UE102 measures the transmitted CSI-RS in the colored blocks. In Figure 5, Δt is the time gap (sampling period) between adjacent measurements, and T is the measurement time window. max If we assume that this is the maximum Doppler frequency intended to be processed, then the CSI-RS period is 1 / (2·f max )≦Δt≦1 / (f maxIf the CSI-RS period is 1 / (f), then an aliasing effect of the spurious Doppler component occurs. max If Δt ≤ 1 / (2·f), the effects of mobility are not fully captured. Therefore, to satisfy the Nyquist criterion, the sampling period and maximum Doppler frequency are given by this relationship Δt ≤ 1 / (2·f). max The following conditions should be met. Furthermore, the frequency (Doppler) resolution increases with time T, and the prediction error depends on the measurement time T.

[0041] 1.3. Extended Codebook Structure In some embodiments, a new codebook structure can be constructed by extending it in the time dimension (TD) using mutually orthogonal DFT bases while preserving the Rel16 codebook structure in the spatial and frequency dimensions (SD and FD). Figure 6 shows an exemplary codebook structure, where N1, N2, N3, and N4 are the number of azimuth, elevation, frequency, and time units (dimensions).

[0042] Extending this to time-domain compression, following the same notation as the Rel-16 codebook, an example of the codebook structure can be given as follows:

[0043]

number

[0044] 1.4. Configuration of Physical Uplink Shared Channel In addition to the information discussed in [TS38213] and [TS38214], and / or as modified according to the examples discussed herein, PUSCH transmissions can be dynamically scheduled by uplink (UL) grants in downlink control information (DCI) (e.g., DCI formats 0_0, 0_1, 0_2, etc.), or transmissions can correspond to configured grant types 1 or 2. PUSCH transmissions of configured grant type 1 are semi-statically configured to operate upon reception of higher-layer parameters of configuredGrantConfig, including rrc-ConfiguredUplinkGrant, without detection of UL grants in the DCI. PUSCH transmissions of configured grant type 2 are semi-permanently scheduled by UL grants in a valid activated DCI, according to section 10.2 of [TS38213], after reception of higher-layer parameters configuredGrantConfig, which does not include rrc-ConfiguredUplinkGrant. If configuredGrantConfigToAddModList is configured, more configured grant configurations than one of the configured grant type 1 and / or configured grant type 2 may be active simultaneously on the serving cell's active BWP.

[0045] As described in Section 12 of [TS38213], for push transmission of carrier f of serving cell c over active UL BWPb, UE102 first uses the parameters defined in Section 7.1.1 of [TS38213] to transmit power P PUSCH,b,f,c Linear value

[0046]

number

[0047]

number

[0048] 1.4.1. Transmission Method In 3GPP systems, two transmission methods are supported for PUSCH transmission: codebook-based transmission and non-codebook-based transmission. For codebook-based transmission, radio access network (RAN) nodes provide user equipment (UE) with a transmit precoding matrix indication (TPMI) in the downlink control information (DCI). UE102 uses the TPMI to select a PUSCH transmission precoder from the codebook. For non-codebook-based transmission, UE102 determines its PUSCH precoder based on the broadband sounding reference signal (SRS) resource indicator (SRI) field from the DCI.

[0049] UE102 is configured for codebook-based transmission when the upper layer parameter txConfig in push-Config is set to "codebook", and UE102 is configured for non-codebook-based transmission when the upper layer parameter txConfig is set to "nonCodebook". If the upper layer parameter txConfig is not configured, UE102 is not expected to be scheduled by DCI format 0_1 ​​or 0_2. When PUSCH is scheduled by DCI format 0_0, PUSCH transmission is based on a single antenna port. Except when the upper layer parameter enableDefaultBeamPL-ForPUSCH0-0 is set to "enabled", UE702 does not expect PUSCH to be scheduled by DCI format 0_0 in the bandwidth part (BWP) without a configured PUCCH resource having PUCCH-SpatialRelationInfo in frequency range 2 in RRC connection mode.

[0050] For codebook-based transmissions, PUSCH can be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2, or semi-statically configured to operate according to section 6.1.2.3 of [TS38214]. If PUSCH is scheduled by DCI format 0_1, DCI format 0_2, or semi-statically configured to operate according to section 6.1.2.3 of [TS38214], UE102 determines its PUSCH transmission precoder based on SRI, TPMI and transmission rank, where SRI, TPMI and transmission rank are DCI fields of one or two SRS resource indicators and one or The number of layers is given by two precoding pieces and the number of layers, or by srs-ResourceIndicator and precodingAndNumberOfLayers according to section 6.1.2.3 of [TS38214], or by srs-ResourceIndicator, srs-ResourceIndicator2, precodingAndNumberOfLayers and precodingAndNumberOfLayers2 according to section 6.1.2.3 of [TS382149]. SRS-ResourceSets applicable to PUSCH scheduled by DCI format 0_1 ​​and DCI format 0_2 are defined by entries in the higher layer parameters srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 in SRS-config, respectively.Only one or two SRS resource sets can be configured in srs-ResourceSetToAddModList having the higher layer parameter usage in the SRS-ResourceSet set in "codebook", and only one or two SRS resource sets can be configured in srs-ResourceSetToAddModListDCI-0-2 having the higher layer parameter usage in the SRS-ResourceSet set in "codebook".

[0051] When only one SRS resource set is configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, which has the upper layer parameter usage in the SRS-ResourceSet set in "codebook", the SRI and TPMI are given by the DCI field of one SRS resource indicator, one precoding information and the number of layers in sections 7.3.1.1.2 and 7.3.1.1.3 of [TS38212] for DCI formats 0_1 and 0_2, or by srs-ResourceIndicator and precodingAndNumberOfLayers in accordance with section 6.1.2.3 of [TS38214]. TPMI should be applied across layers {0...v-1} when multiple SRS resources are configured and is used to indicate the precoder corresponding to the SRS resource selected by the SRI, or, when a single SRS resource is configured, TPMI should be applied across layers {0...v-1} and is used to indicate the precoder corresponding to the SRS resource. The transmission precoder is selected from an uplink codebook having a number of antenna ports equal to the upper layer parameter nrofSRS-Ports in SRS-Config, as defined in section 6.3.1.5 of [TS38211]. When UE102 is configured with the upper layer parameter txConfig set to “codebook”, UE102 is configured with at least one SRS resource. The indicated SRI in slot n is associated with the immediate transmission of the SRS resource identified by the SRI, and the SRS resource is ahead of the PDCCH carrying the SRI.

[0052] When two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, which has the upper layer parameter usage in SRS-ResourceSet set to "codebook", one or two SRIs and one or two TPMIs are given by the DCI fields of the two SRS resource indicators, two precoding information, and the number of layers in sections 7.3.1.1.2 and 7.3.1.1.3 of [TS38212] for DCI formats 0_1 and 0_2. UE102 applies the indicated SRIs and TPMIs to one or more PUSCH iterations according to the associated SRS resource sets of the PUSCH iterations, in accordance with section 6.1.2.1 of [TS38214]. Each TPMI is used to indicate the precoder corresponding to the SRS resource selected by the corresponding SRI when multiple SRS resources are configured for an applicable SRS resource set based on the indicated code point of the SRS resource set indicator, or when a single SRS resource is configured for an applicable SRS resource set, the TPMI is used to indicate the precoder corresponding to the SRS resource when a single SRS resource is configured for an applicable SRS resource set. For one or two TPMIs, the transmission precoder is selected from an uplink codebook having a number of antenna ports equal to the upper layer parameter nrofSRS-Ports in SRS-Config for the indicated SRI, as defined in section 6.3.1.5 of [TS38211]. When two SRIs are indicated, UE102 assumes that nrofSRS-Ports are the same for the two indicated SRS resources. When UE702 is configured with the upper layer parameter txConfig set to "codebook", UE102 is configured with at least one SRS resource.Each of the one or two indicated SRIs in slot n is associated with the most recent transmission of an SRS resource in the associated SRS resource set identified by the SRI, and the SRS resource is prior to the PDCCH carrying the SRI. When two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the upper layer parameter usage in SRS-ResourceSet set in "codebook", UE102 is not expected to consist of a different number of SRS resources in the two SRS resource sets.

[0053] When a PDCCH reception includes two PDCCH candidates from two separate search space sets, the PDCCH candidate that starts earlier in time is used to determine the most recent transmission of the SRS resource identified by the SRI, as described in Section 10.1 of [TS38213].

[0054] For codebook-based transmissions, UE102 determines its codebook subset based on the TPMI and the reception of the upper layer parameter codebookSubset in push-Config for PUSCH associated with DCI format 0_1 ​​and codebookSubsetDCI-0-2 in push-Config for PUSCH associated with DCI format 0_2. This may consist of "fullyAndPartialAndNonCoherent", "partialAndNonCoherent", or "nonCoherent", depending on the capabilities of UE102. When the upper layer parameter ul-FullPowerTransmission is set to "fullpowerMode2", the upper layer parameter codebookSubset or the upper layer parameter codebookSubsetDCI-0-2 is set to "partialAndNonCoherent", and an SRS-resourceSet with usage set to "codebook" includes at least one SRS resource with 4 ports and one SRS resource with 2 ports, the codebookSubset associated with the 2-port SRS resource is "nonCoherent". The maximum transmission rank may be determined by the upper layer parameter maxRank in push-Config for PUSCH scheduled in DCI format 0_1 ​​and maxRankDCI-0-2 for PUSCH scheduled in DCI format 0_2.

[0055] UE102 reporting UE capability for "partialAndNonCoherent" transmission does not assume that it is composed of either a codebookSubset or codebookSubsetDCI-0-2 having "fullyAndPartialAndNonCoherent". UE102 reporting UE capability for "nonCoherent" transmission does not assume that it is composed of either a codebookSubset or codebookSubsetDCI-0-2 having "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". When the upper layer parameter nrofSRS-Ports in an SRS-ResourceSet with usage set to "codebook" indicates that the maximum number of configured SRS antenna ports in the SRS-ResourceSet is 2, UE102 does not assume that it is composed of an upper layer parameter codebookSubset or codebookSubsetDCI-0-2 having "partialAndNonCoherent".

[0056] For codebook-based transmissions, only one SRS resource can be directed based on the SRI from within the SRS resource set. The maximum number of configured SRS resources for codebook-based transmissions is two, except when the upper-layer parameter ul-FullPowerTransmission is set to "fullpowerMode2". If aperiodic SRS is configured for UE102, the SRS request field in DCI triggers the transmission of the aperiodic SRS resource.

[0057] UE102 does not assume that the higher-layer parameters ul-FullPowerTransmission, which is set to "fullpowerMode1", and "fullAndPartialAndNonCoherent" are configured with either codebookSubset or codebookSubsetDCI-0-2.

[0058] UE102 transmits PUSCH using the same antenna port as the SRS port in the SRS resource as indicated by DCI format 0_1 ​​or 0_2 or configuredGrantConfig in accordance with section 6.1.2.3 of [TS38214].

[0059] DM-RS antenna port in section 6.4.1.1.3 of [TS38211]

[0060]

number

[0061] Except when the upper layer parameter ul-FullPowerTransmission is set to "fullpowerMode2", when multiple SRS resources are composed of an SRS-ResourceSet with a usage set in "codebook", UE102 assumes that the upper layer parameter nrofSRS-Ports within the SRS-Resource in the SRS-ResourceSet is set to the same value for all of these SRS resources.

[0062] When the upper layer parameter ul-FullPowerTransmission is set to "fullpowerMode2", UE102 can consist of one or more SRS resources using the same or different number of SRS ports within an SRS resource set having the usage set in "codebook". When the upper layer parameter ul-FullPowerTransmission is set to "fullpowerMode2", and multiple SRS resources are configured within an SRS resource set, up to two different spatial relationships can be configured for all SRS resources within the SRS resource set having the usage set in "codebook". According to the capabilities of UE102, a maximum of two or four SRS resources are supported in an SRS resource set having the usage set in "codebook".

[0063] For non-codebook-based transmissions, PUSCH can be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2, or it can be semi-statically configured to operate in accordance with [TS38214] §6.1.2.3. If the PUSCH is scheduled according to DCI format 0_1, DCI format 0_2, or semi-statically configured to operate in accordance with [TS38214]§6.1.2.3, then when multiple SRS resources are configured, UE102 can determine its PUSCH precoder and transmission rank based on the SRI, which is given by one or two SRS resource indicators in the DCI in accordance with sections 7.3.1.1.2 and 7.3.1.1.3 of [TS38212], or by the srs-ResourceIndicator in accordance with [TS38214]§6.1.2.3, or by the srs-ResourceIndicator and srs-ResourceIndicator2 in accordance with [TS38214]§6.1.2.3. SRS-ResourceSets applicable to PUSCH scheduled by DCI format 0_1 ​​and DCI format 0_2 are defined by the entries in the higher-layer parameters srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 within the SRS-config, respectively. UE102 shall use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be configured in UE102 for simultaneous transmission of the same symbol, and the maximum number of SRS resources, are UE capabilities. SRS resources transmitted simultaneously occupy the same RB. Only one SRS port is configured for each SRS resource.Only one or two SRS resource sets can be configured in srs-ResourceSetToAddModList having the higher layer parameter usage in SRS-ResourceSet set to "nonCodebook", and only one or two SRS resource sets can be configured in srs-ResourceSetToAddModListDCI-0-2 having the higher layer parameter usage in SRS-ResourceSet set to "nonCodebook". When two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 having the higher layer parameter usage in SRS-ResourceSet set to "nonCodebook", the SRI is given by the DCI fields of the two SRS resource indicators in [TS38212] §7.3.1.1.2, §7.3.1.1.3 for DCI formats 0_1 and 0_2. UE102 applies the indicated SRI to one or more PUSCH iterations according to the associated SRS resource set of the PUSCH iteration, in accordance with [TS38214] §6.1.2.1. The maximum number of SRS resources per SRS resource set that can be configured for non-codebook-based uplink transmissions is 4. Each indicated SRI in slot n is associated with the most recent transmission of the SRS resource in the associated SRS resource set identified by the SRI, and the SRS transmission precedes the PDCCH that carries the SRI. When two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the upper layer parameter usage in the SRS-ResourceSet set to "nonCodebook", UE102 does not assume that the two SRS resource sets consist of different numbers of SRS resources.

[0064] When a PDCCH reception includes two PDCCH candidates from two separate search space sets, the PDCCH candidate that starts earlier in time is used for the purpose of determining the most recent transmission of the SRS resource identified by the SRI, as described in [TS38213]§10.1.

[0065] For non-codebook-based transmissions, UE102 can calculate the precoder used for SRS transmission based on measurements of the relevant NZP CSI-RS resources. UE102 can consist of only one NZP CSI-RS resource for each SRS resource set with the upper-layer parameter `usage` in the SRS-ResourceSet, if configured.

[0066] When an aperiodic SRS resource set is configured, the associated NZP-CSI-RS is indicated via the SRS request field in DCI formats 0_1 and 1_1, as well as DCI format 0_2 (if an SRS request field exists) and DCI format 1_2 (if an SRS request field exists), and the AperiodicSRS-ResourceTrigger and AperiodicSRS-ResourceTriggerList (indicating the association between the aperiodic SRS trigger state and the SRS resource set), the triggered SRS resource srs-ResourceSetId, and csi-RS (indicating the associated NZP-CSI-RS-ResourceId) are higher layers configured in the SRS-ResourceSet. SRS-ResourceSets associated with SRS requests by DCI formats 0_1 and 1_1 are defined by entries in the upper layer parameter srs-ResourceSetToAddModList, and SRS-ResourceSets associated with SRS requests by DCI formats 0_2 and 1_2 are defined by entries in the upper layer parameter srs-ResourceSetToAddModListDCI-0-2. The gap between the last symbol received for a periodic NZP-CSI-RS resources and the first symbol of a periodic SRS transmission is 42.2 max(0,μ-3) If it is less than this, UE102 is not expected to update the SRS precoding information. Here, SCS configuration μ is the minimum SCS configuration between the NZP-CSI-RS resource and the SRS transmission.

[0067] If UE102 is configured with an aperiodic SRS associated with an aperiodic NZP CSI-RS resource, the presence of an associated CSI-RS is indicated by the SRS request field if the value of the SRS request field is not "00" as in Table 7.3.1.1.2-24 of [TS38212], and the scheduling DCI is not used for cross-carrier or cross-bandwidth partial scheduling. If UE102 is configured with minimumSchedulingOffsetK0 in active DL BWP, and the currently applicable minimum scheduling offset limit K 0,min If the value is greater than 0, the UE does not expect to receive a scheduling DCI with an SRS request field value other than "00". The CSI-RS is placed in the same slot as the SRS request field. If UE102 is configured with a periodic SRS associated with a periodic NZP CSI-RS resource, none of the TCI states configured in the scheduling CC should be configured with a qcl-Type set to "typeD".

[0068] When a periodic or semi-permanent SRS resource set is configured, the NZP-CSI-RS-ResourceId for measurement is indicated via the higher-layer parameter associatedCSI-RS within the SRS-ResourceSet.

[0069] UE102 performs a one-to-one mapping from the designated SRI to the designated DM-RS port and their corresponding PUSCH layer {0...v-1} provided by configuredGrantConfig in ascending order according to DCI format 0_1 ​​or 0_2 or [TS38214]§6.1.2.3.

[0070] UE102 transmits PUSCH using the same antenna port as the SRS port in the SRS resource indicated by DCI format 0_1 ​​or 0_2 or by configuredGrantConfig provided in accordance with [TS38214] §6.1.2.3, and the SRS port of the (i+1)th SRS resource in the SRS resource set is p i It will be indexed as =1000+i.

[0071] [TS38211] DM-RS antenna port in §6.4.1.1.3

[0072]

number

[0073] For non-codebook-based transmissions, UE102 does not assume that both spatialRelationInfo for SRS resources and associatedCSI-RS within SRS-ResourceSet for SRS resource sets are present. For non-codebook-based transmissions, when at least one SRS resource is present in an SRS-ResourceSet with usage set to "nonCodebook", UE102 can schedule in DCI format 0_1 ​​or 0_2.

[0074] 1.5. UE Procedure for Reporting Channel Status Information (CSI) 1.5.1. CSI Framework The procedures for non-periodic CSI reporting described herein and / or in [TS38214] assume that the CSI reporting is triggered by DCI format 0_1, but these apply equally to CSI reporting triggered by DCI format 0_2 and / or other DCI formats by applying the higher layer parameter reportTriggerSizeDCI-0-2 instead of reportTriggerSize. The time and frequency resources available to UE102 for reporting CSI are controlled by RAN nodes (e.g., gNB716, etc.). CSI may include a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a CSI-RS Resource Indicator (CRI), an SS / PBCH Block Resource Indicator (SSBRI), a Layer Indicator (LI), a Rank Indicator (RI), L1-RSRP, L1-SINR, and / or CapabilityIndex. For CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR, and / or CapabilityIndex, UE102 is configured by the upper layer with N ≥ 1 CSI-ReportConfig reporting settings, M ≥ 1 CSI-ResourceConfig resource settings, and one or two lists of trigger states (provided by the upper layer parameters CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList). Each trigger state in CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs indicating resource set IDs for the channel and, optionally, for interference.Each trigger state in CSI-SemiPersistentOnPUSCH-TriggerStateList includes one associated CSI-ReportConfig. Further aspects of CQI, PMI, CSI-RS, CSI-IM, and CSI reference resources are discussed in [TS38214].

[0075] Each reporting configuration CSI-ReportConfig is associated with a single downlink bandwidth part (BWP) indicated by the higher-layer parameter BWP-Id given in the associated CSI-ResourceConfig for channel measurement, and includes parameters for one CSI reporting bandwidth, namely the codebook configuration including codebook subset limits, time-domain behavior, frequency granularity for CQI and PMI, measurement limit configuration, and CSI-related quantities to be reported by UE102, such as layer indicator (LI), L1-RSRP, L1-SINR, CRI and SSB resource indicator (SSBRI) and CapabilityIndex. The time-domain behavior of CSI-ReportConfig is indicated by the higher-layer parameter reportConfigType and can be set to "aperiodic", "semiPersistentOnPUCCH", "semiPersistentOnPUSCH", or "periodic". For "periodic" and "semiPersistentOnPUCCH" / "semiPersistentOnPUSCH" CSI reports, the configured period and slot offset are applied in the UL BWP numerology configured for CSI reporting. The upper layer parameter reportQuantity indicates the CSI-related quantity, L1-RSRP-related quantity, L1-SINR-related quantity, or CapabilityIndex-related quantity to report. reportFreqConfiguration indicates the reporting granularity in the frequency domain, including the CSI reporting bandwidth, and whether the PMI / CQI report is broadband or subband. The timeRestrictionForChannelMeasurements parameter in CSI-ReportConfig can be configured to enable time-domain restrictions for channel measurements, and timeRestrictionForInterferenceMeasurements can be configured to enable time-domain restrictions for interference measurements.CSI-ReportConfig may also include CodebookConfig, which includes configuration parameters for port selection of Type I, Type II, Extended Type II CSI, or further Extended Type II, including codebook subset restrictions where applicable, and configuration for group-based reporting. UE102 is not expected to be configured with CSI reporting settings associated with the Apex DL BWP when reportConfigType is set to "aperiodic".

[0076] Each CSI resource configuration, CSI-ResourceConfig, contains a list of S ≥ 1 CSI resource sets (given by the higher-layer parameter csi-RS-ResourceSetList), where the list consists of references to either or both NZP CSI-RS resource sets and SS / PBCH block sets, or the list consists of references to CSI-IM resource sets. Each CSI resource configuration resides in a DL BWP identified by the higher-layer parameter BWP-id, and all CSI resource configurations linked to a CSI reporting configuration have the same DL BWP.

[0077] The time-domain behavior of CSI-RS resources within a CSI resource configuration is indicated by the higher-layer parameter resourceType and can be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI resource configurations, when UE102 is configured with groupBasedBeamReporting-r17, the number of configured CSI resource sets is S=2; otherwise, the number of configured CSI-RS resource sets is limited to S=1. For periodic and semi-persistent CSI resource configurations, the configured period and slot offset are given in the numerology of the associated DL BWP, as given by the BWP-id. When UE102 is configured with multiple CSI-ResourceConfigs containing the same NZP CSI-RS resource ID, the same time-domain behavior is configured for the CSI-ResourceConfigs. When UE102 is configured with multiple CSI-ResourceConfigs containing the same CSI-IM resource ID, the same time-domain behavior is configured for the CSI-ResourceConfigs. All CSI resource settings linked to the CSI reporting settings have the same time-domain behavior.

[0078] The UE102 can be configured via upper-layer signaling for one or more CSI resource settings for channel and interference measurements, including a CSI-IM (CSI-Interference Measurement) resource for interference measurements as described in Section 5.2.2.4 of [TS38214], a non-zero power (NZP) CSI-RS resource for interference measurements as described in Section 5.2.2.3.1 of [TS38214], and an NZP CSI-RS resource for channel measurements as described in Section 5.2.2.3.1 of [TS38214].

[0079] UE102 calculates the CSI parameters (if reported) assuming the following dependencies between the CSI parameters (if reported): LI is calculated conditionally on the reported CQI, PMI, RI, and CRI. CQI is calculated conditionally on the reported PMI, RI, and CRI. PMI is calculated conditionally on the reported RI and CRI. RI is calculated conditionally on the reported CRI. The reporting configuration for CSI can be aperiodic (e.g., using PUSCH), periodic (e.g., using PUCCH), or semi-permanent (e.g., using PUCCH and DCI-activated PUSCH). CSI-RS resources can be periodic, semi-permanent, or aperiodic. For example, UE102 supports combinations of CSI reporting configurations and CSI-RS resource configurations, and how CSI reporting is triggered for each CSI-RS resource configuration, as shown in Table 5.2.1.4-1 of [TS38214].

[0080] Periodic CSI-RS is configured by the upper layer. When the CSI-RS configuration is periodic CSI-RS, there is no dynamic trigger / activation for periodic CSI reporting. For semi-persistent CSI reporting, UE102 receives an activation command as described in section 6.1.3.16 of [TS38321] to report on PUCCH, and UE102 receives a trigger on DCI for reporting on PUCCH. Semi-persistent CSI-RS is activated and deactivated as described in section 5.2.1.5.2 of [TS38214]. When the CSI-RS configuration is semi-persistent CSI-RS, periodic CSI reporting is not supported. For semi-persistent CSI reporting, UE102 receives an activation command as described in section 6.1.3.16 of [TS38214] to report on PUCCH, and UE102 receives a trigger on DCI for reporting on PUCCH. Aperiodic CSI-RS is configured and triggered / activated as described in Section 5.2.1.5.1 of [TS38214]. When the CSI-RS configuration is aperiodic CSI-RS, periodic CSI reporting and semi-persistent CSI reporting are not supported. Aperiodic CSI reporting (per I-RS configuration type) is triggered by DCI. Furthermore, sub-selection instructions, as described in Section 6.1.3.13 of [TS38321], are possible as defined in Section 5.2.1.5.1 of [TS38214]. Reporting configurations, resource setting configurations, L1-RSRP reporting configurations, L1-SINR reporting configurations, and further aspects of triggering / activating CSI reporting and CSI-RS are discussed in [TS38214].

[0081] 1.5.2. CSI Reporting Using PUSCH If UE102 successfully decodes DCI format 0_1 ​​or DCI format 0_2 which triggers an aperiodic CSI trigger state, it performs an aperiodic CSI report using PUSCH on serving cell c.

[0082] When DCI format 0_1 ​​schedules two PUSCH assignments, aperiodic CSI reports are carried on the second scheduled PUSCH. When DCI format 0_1 ​​schedules more than two PUSCH assignments, aperiodic CSI reports are carried on the second-to-last scheduled PUSCH.

[0083] Aperiodic CSI reports delivered on PUSCH support broadband and subband frequency granularity. Aperiodic CSI reports delivered on PUSCH support port-selective CSI of Type I, Type II, Extended Type II, and Further Extended Type II.

[0084] Upon successful decoding of DCI format 0_1 ​​or DCI format 0_2 to activate a semi-persistent CSI trigger state, UE102 performs a semi-persistent CSI report on PUSCH. DCI format 0_1 ​​and DCI format 0_2 include a CSI request field indicating a semi-persistent CSI trigger state to activate or deactivate. The semi-persistent CSI report on PUSCH supports port selection CSI of type I, type II with broadband and subband frequency granularity, extended type II, and further extended type II. PUSCH resources and MCS shall be semi-persistently allocated by the uplink DCI.

[0085] CSI reporting on PUSCH can be multiplexed with uplink data on PUSCH, except that semi-persistent CSI reporting on PUSCH activated by the DCI format is not expected to be multiplexed with uplink data on PUSCH. CSI reporting on PUSCH can also be performed without multiplexing with uplink data from the UE.

[0086] Type I CSI feedback is supported for CSI reporting on PUSCH. Type I broadband and subband CSI is supported for CSI reporting on PUSCH. Type II CSI is supported for CSI reporting on PUSCH.

[0087] For Type I, Type II, Extended Type II, and Further Extended Type II port selection CSI feedback on PUSCH, the CSI report consists of two parts. Part 1 has a fixed payload size and is used to identify the number of information bits in Part 2. Part 1 is transmitted in its entirety before Part 2.

[0088] For Type I CSI feedback, Part 1 includes RI (if reported), CRI (if reported), and CQI (if reported) for the first codeword. Part 2 includes PMI (if reported), LI (if reported), and, when RI is greater than 4, CQI (if reported) for the second codeword. For a CSI-ReportConfig configured with codebookType set to "typeI-SinglePanel", and a corresponding CSI-RS resource set for channel measurement consisting of two resource groups and N resource pairs, Part 1 includes RI, CRI, and CQI for the first codeword, zero-padded to a fixed payload size (if necessary). Part 2 includes CQI (if reported), LI (if reported), and PMI for the second codeword when RI is greater than 4.

[0089] For Type II CSI feedback, Part 1 includes indications for the RI (if reported), CQI, and the number of non-zero broadband amplitude coefficients per layer for Type II CSI (see, e.g., Section 5.2.2.2.3 of [TS38214]). The fields of Part 1, namely the indications for the RI (if reported), CQI, and the number of non-zero broadband amplitude coefficients for each layer, are encoded separately. Part 2 includes the PMI and LI (if reported) for Type II CSI. 1,4,l i 2,1,l (if reported) and i 2,2,l The elements (if reported) are reported in ascending order of their indices, i=0, 1, ..., 2L-1, with the element with the lowest index mapped to the most significant bit and the element with the highest index mapped to the least significant bit. Parts 1 and 2 are encoded separately.

[0090] For extended type II CSI feedback (see, e.g., section 5.2.2.2.5 of [TS38214]) and further extended type II port selection CSI feedback (see, e.g., section 5.2.2.2.7 of [TS38214]), Part 1 includes the RI (if reported), CQI, and indication of the total number of non-zero amplitude coefficients across layers. The fields of Part 1, i.e., the RI (if reported), CQI, and indication of the total number of non-zero amplitude coefficients across layers, are encoded separately. Part 2 includes the PMI for extended type II or further extended type II port selection CSI. Parts 1 and 2 are encoded separately.

[0091] Type II CSI reports transported on PUSCH shall be calculated independently of any Type II CSI reports transported on PUSCH format 3 or 4 (see, for example, sections 5.2.4 and 5.2.2 of [TS38214]).

[0092] When the upper-layer parameter reportQuantity consists of the values ​​"cri-RSRP", "ssb-Index-RSRP", "cri-SINR", or "ssb-Index-SINR", or one of "cri-RSRPIndex", "ssb-Index-RSRP-Index", "cri-SINR-Index", or "ssb-Index-SINR-Index", the CSI feedback includes a single part.

[0093] For both Type I and Type II reports configured for PUCCH but transmitted over PUCCH, the payload determination for CSI Part 1 and CSI Part 2 shall follow the PUCCH determination as described in Section 5.2.4 of [TS38214].

[0094] When the CSI report on PUSCH contains two parts, UE102 may omit part of the CSI in Part 2. The omission of the CSI in Part 2 follows the priority shown in Table 1.5.2-1. Rep This is the number of CSI reports configured to be transported on PUSCH. Priority 0 is the highest priority, and priority 2N is the highest priority. Rep This is the lowest priority, and CSI report n is defined as N in Section 5.2.5. Rep The nth smallest Pri among the individual CSI reports i,CSI This corresponds to a CSI report with (y,k,c,s) values. The subbands of a given CSI report n, indicated by the upper layer parameter csi-ReportingBand with a value of "1", are numbered sequentially in ascending order, with the lowest subband of csi-ReportingBand with a value of "1" being subband 0. When omitting CSI information in Part 2 for a particular priority level, UE102 omits all information for that priority level.

[0095] For an extended type II report for a given CSI report n, index i is indexed by l, i and f. 2,4,l i 2,5,l and i1,7,l Each reported element is associated with a priority value Pri(l,i,f) = 2·L·υ·π(f) + υ·i + l, where π(f) = min(2·n 3,l (f) ), 2·(N3 - n 3,l (f) ), l = 1, 2,..., υ, i = 0, 1,..., 2L - 1 and f = 0, 1,..., M υ -1, and n 3,l (f) is defined in section 5.2.2.2.5 of [TS38214]. The element with the highest priority has the lowest associated value Pri(l,i,f). The omission of part 2 CSI follows the priority order shown in Table 1.5.2-1. Here, group 0 includes index i 1,1 (when reported), i 1,2 (when reported) and i 1,8,l (l = 1,..., υ). Group 1 includes i 1,5 (when reported), i 1,6,l (when reported), i 1,7,l , i 2,3,l of the

[0096]

Number

[0097]

Number

[0098]

Number

[0099]

Number

[0100]

number

[0101]

number

[0102] For a further extended Type II port selection report for a given CSI report n, index i is indexed by l, i and f. 2,4,l i 2,5,l and i 1,7,l Each reported element is associated with the priority value Pri(l,i,f) = K1·υ·f + υ·i + l, where l = 1, 2, ..., v, i = 0, 1, ..., K1-1 and f = 0, ..., M-1. The element with the highest priority has the lowest association value Pri(l,i,f). The omission of CSI in Part 2 follows the priority shown in Table 1.5.2-1, where group 0 is i 1,2 (if reported), i 1,8,l (l=1, ..., υ) and i 1,6 (If reported) Group 1 is i 1,7,l (if reported), i 2,3,l of

[0103]

number

[0104]

number

[0105]

number

[0106]

number

[0107]

number

[0108]

number

[0109] [Table 5] When UE102 is scheduled to transmit a transport block on PUSCH without using iteration type B which is multiplexed with the CSI report, the CSI in part 2 is

[0110]

number

[0111]

number

[0112] CSI Part 2 starts from the lowest priority level,

[0113]

number

[0114]

number

[0115] When UE102 is scheduled to transmit a transport block on PUSCH using iteration type B which is multiplexed with the CSI report, the CSI in part 2 is

[0116]

number

[0117]

number

[0118] CSI Part 2 starts from the lowest priority level,

[0119]

number

[0120]

number

[0121] When Part 2 CSI is transmitted over PUSCH without a transport block, lower priority bits are omitted down to the Part 2 CSI code rate, which is O CSI-2 +L CSI-2 ) / (N L ·Q' CSI,2 Q m ) is given by, where O CSI-2 , L CSI-2 , N L , Q' CSI,2 Q m This is given in section 6.3.2.4 of [5,38.212]. Prior to HARQ-ACK puncturing, if present, the CSI of part 2 is a threshold code rate c lower than 1. T It fell below this level, and here,

[0122]

number

[0123] When UE102 is in a semi-persistent CSI reporting configuration active on PUSCH, CSI reporting is deactivated when either the downlink BWP or uplink BWP is changed. A separate activation command is required to enable semi-persistent CSI reporting.

[0124] 1.5.3. CSI Reporting Using PUCCH UE102 is semi-statically configured by a higher layer to perform periodic CSI reporting on PUCCH. UE102 can be configured by a higher layer for multiple periodic CSI reports, corresponding to CSI reporting settings composed of multiple higher layers, with the associated CSI resource settings configured in the higher layers. Periodic CSI reporting on PUCCH formats 2, 3, and 4 supports Type I CSI with broadband granularity.

[0125] When UE102 transmits a PUCCH with HARQ-ACK in slot n in response to the PDSCH carrying the activation command described in section 6.1.3.16 of [TS38321], slot n+3N slot subframe,μ Semi-persistent CSI reporting is performed on PUCCH, starting from the first slot after the following, where μ is the SCS configuration for PUCCH. The activation command includes one or more reporting settings in which the associated CSI resource settings are configured. Semi-persistent CSI reporting on PUCCH supports Type I CSI. Semi-persistent CSI reporting on PUCCH format 2 supports Type I CSI with broadband frequency granularity. Semi-persistent CSI reporting on PUCCH format 3 or 4 supports Type I CSI with broadband and subband frequency granularity, and Type II CSI Part 1.

[0126] When PUCCH carries a Type I CSI with broadband frequency granularity, the CSI payloads carried by PUCCH format 2 and PUCCH format 3 or 4 are identical, regardless of whether RI (if reported) or CRI (if reported) is the same. A CSI-ReportConfig with codebookType set to "typeI-SinglePanel" and the corresponding CSI-RS resource set for channel measurements, consisting of two resource groups and N resource pairs, can be configured with broadband frequency granularity only if csi-ReportMode is set to "Mode1" and numberOfSingleTRP-CSI-Mode1 is set to X=0. For Type I CSI subband reports on PUCCH format 3 or 4, the payload is divided into two parts. The first part includes RI (if reported), CRI (if reported), and CQI for the first codeword. The second part includes PMI (if reported), LI (if reported), and CQI for the second codeword (if reported) when RI > 4. For a CSI-ReportConfig consisting of subband reporting, a codebookType set to "typeI-SinglePanel", and a corresponding CSI-RS resource set for channel measurement consisting of two resource groups and N resource pairs, Part 1 includes the RI, CRI, and CQI for the first codeword, zero-padded to a fixed payload size (if necessary). Part 2 includes the CQI, LI (if reported), and PMI for the second codeword (if reported) when the RI is greater than 4.

[0127] Semi-persistent reports delivered on PUCCH format 3 or 4 support Type II CSI feedback, but only Part 1 of Type II CSI feedback (see Sections 5.2.2 and 5.2.3). Supporting Type II CSI reporting on PUCCH format 3 or 4 is UE capability type2-SP-CSI-Feedback-LongPUCCH. Type II CSI reports (Part 1 only) delivered on PUCCH format 3 or 4 shall be calculated independently of any other Type II CSI reports delivered on PUCCH (see Section 5.2.3).

[0128] When UE102 consists of a CSI report on PUCCH format 2, 3, or 4, each PUCCH resource is configured for each candidate UL BWP.

[0129] If UE102 is in an active semi-persistent CSI reporting configuration on PUCCH and has not received a deactivation command, CSI reporting will occur when the BWP configured for reporting is an active BWP; otherwise, CSI reporting will be suspended.

[0130] UE102 is not expected to report a CSI having a total number of UCI bits and CRC bits greater than 115 bits when configured in PUCCH format 4. For CSI reports transmitted over PUCCH, if all CSI reports contain one part, UE102 may omit part of the CSI report. CSI omission is defined in section 5.2.5 of [TS38214], Pri i,CSI The priority is determined by the (y,k,c,s) values. CSI reports are omitted starting from the lowest priority level until the CSI report code rate is less than or equal to that configured by the upper layer parameter maxCodeRate.

[0131] If any of the CSI reports contain two parts, UE102 may omit part of the CSI in Part 2. The omission of the CSI in Part 2 follows the priority order shown in Table 1.5.2-1. The CSI in Part 2 is omitted starting from the lowest priority level until the CSI code rate in Part 2 is less than or equal to that configured by the upper layer parameter maxCodeRate.

[0132] 1.5.4.UE CSI calculation time When a CSI request field on (or within) DCI triggers a CSI report on PUSCH, UE102 (i) has a first uplink symbol, symbol Z, to carry the corresponding CSI report, including the effects of timing advance. ref If it does not start earlier than (ii) the first uplink symbol for carrying the nth CSI report including the timing advance effect is symbol Z' ref( If it does not start earlier than n), it provides a valid CSI report for the nth triggered report, where Z ref This is the T at the end of the last symbol of the PDCCH that triggers the CSI report. proc,CSI =(Z)(2048+144)·κ2 -μ ·T c +T switch And it is defined as the next uplink symbol where that CP begins, Z' ref (n) is the time after the end of the last symbol in the time of the most recent of the aperiodic CSI-RS used for channel measurement, the aperiodic CSI-RS used for interference measurement, and the aperiodic NZP CSI-RS used for interference measurement, when the aperiodic CSI-RS is used for channel measurement for the nth triggered CSI report. proc,CSI =(Z')(2048+144)·κ2 -μ ·T c And it is defined as the next uplink symbol where that CP begins, T switch This is defined in section 6.4 of [TS38124] and applies only when Z1 in Table 1.5.4-1 is applicable.

[0133] If the PUSCH indicated by the DCI overlaps with another PUSCH, the CSI report will be multiplexed in accordance with the procedures in Section 9.2.5 of [TS38213] and Section 5.2.5 of [TS38214], if applicable; otherwise, the CSI report will be transmitted over the PUSCH indicated by the DCI.

[0134] When a CSI request field on DCI triggers a CSI report on PUSCH, the first uplink symbol for carrying the corresponding CSI report, including the timing advance effect, is symbol Z. ref When starting earlier than that, UE102 may ignore the scheduling DCI if the HARQ-ACK or transport block is not multiplexed on PUSCH.

[0135] When a CSI request field on DCI triggers a CSI report on PUSCH, the first uplink symbol for carrying the nth CSI report, including the timing advance effect, is symbol Z'. ref When it starts earlier than (n), UE102 may ignore the scheduling DCI if the number of triggered reports is 1 and the HARQ-ACK or transport block is not multiplexed on PUSCH, otherwise UE102 is not required to update the CSI for the nth triggered CSI report.

[0136] When a PDCCH reception contains two PDCCH candidates from two separate search space sets, the PDCCH candidate that ends later in time is used for the purpose of determining the last symbol of the PDCCH that triggers the CSI report, as described in 10.1 of [TS38213].

[0137] Z, Z', and μ are defined as follows:

[0138]

number

[0139]

number

[0140] [Table 6]

[0141] [Table 7] 2. Configuration and Placement of Networks, Systems, and Devices Figure 7 shows network 700 in various embodiments. Network 700 may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G / NR systems. However, exemplary embodiments are not limited thereto, and the examples described may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0142] Network 700 includes UE702, which is either a mobile or non-mobile computing device designed to communicate with RAN704 via a wireless connection. UE702 is coupled to RAN704 via a Uu interface, which may be applicable to both LTE and NR systems. Examples of UE702 applications include smartphones, tablet computers, wearable devices (e.g., smartwatches, fitness trackers, smart glasses, smart clothing / fabrics, head-mounted displays, smart shows, etc.), desktop computers, workstations, laptop computers, automotive infotainment systems, automotive entertainment systems, instrument clusters, head-up display (HUD) devices, onboard diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, machine-to-machine (M2M), device-to-device (D2D), machine-type communication (MTC) devices, Internet of Things (IoT) devices, smart appliances, drones or unmanned aerial vehicles (UAVs), ground drones or autonomous vehicles, robots, electronic signage, and single-board computers (SBCs). This includes, but is not limited to, any type of computing device such as a computer (e.g., Raspberry Pi, Arduino, Intel Edison, etc.), a plug computer, and / or any of those discussed herein.UE702 may be identical or similar to any of the other UEs discussed herein, such as UE102, UE802, hardware resource 900 and / or any other UE discussed herein.

[0143] Network 700 may include a set of UE702 directly coupled to one another via any other suitable interface such as device-to-device (D2D), proximity service (ProSe), PC5, and / or sidelink (SL) interfaces, and / or any of those discussed herein. These UE702 may be M2M, D2D, MTC, and / or IoT devices, and / or V2X systems, but are not limited to, communicating using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. The UE702 may perform blind decoding attempts of SL channels / links according to the various examples herein.

[0144] In some examples, the UE702 may further communicate with the AP706 via an over-the-air (OTA) connection. The AP706 manages a WLAN connection that may function to offload some / all of the network traffic from the RAN704. The connection between the UE702 and the AP706 may conform to any IEEE 802.11 protocol. Furthermore, the UE702, RAN704, and AP706 may utilize cellular-WLAN aggregation / integration (e.g., LWA / LWIP). Cellular-WLAN aggregation may include the UE702 configured by the RAN704 to utilize both cellular radio resources and WLAN resources.

[0145] RAN704 includes one or more access network nodes (ANs) 708. AN708 terminates the air interface for UE702 by providing access layer protocols including RRC, PDCP, RLC, MAC, and PHY / L1 protocols. Thus, AN708 enables data / voice connectivity between CN720 and UE702. AN708 may be a macrocell base station, or a low-power base station to provide a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell, or any combination thereof. In these implementations, AN708 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRP (or TRxP), etc.

[0146] One exemplary implementation is a "CU / DU split" architecture in which the AN708 is embodied as a gNB-Central Unit (CU) that is communicatively coupled to one or more gNB Distributed Units (DUs), each DU may be communicatively coupled to one or more Radio Units (RUs) (also known as RRHs, RRUs, etc.). In some implementations, the one or more RUs may be individual RSUs. In some implementations, the CU / DU split may include an ng-eNB-CU and one or more ng-eNB-DUs instead of, or in addition to, a gNB-CU and a gNB-DU, respectively. The AN708, embodied as AN7CU, may be implemented as one or more software entities running on a server computer, either on an individual device or as part of a virtual network including, for example, a virtual baseband unit (BBU) or BBU pool, cloud RAN (CRAN), radio equipment controller (REC), radio cloud center (RCC), centralized RAN (C-RAN), virtualized RAN (vRAN), etc. (however, these terms may refer to different implementation concepts). Any other type of architecture, deployment, and / or configuration may be used.

[0147] The AN708 set is coupled to each other via its respective X2 interface if RAN704 is an LTE RAN or an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 710, or via its respective Xn interface if RAN704 is an NG-RAN 714. In some examples, the X2 / Xn interfaces, which may be separated into control / user plane interfaces, may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0148] Each AN of RAN704 may manage one or more cells, cell groups, component carriers, etc., and provide an air interface for network access to UE702. UE702 may simultaneously connect to a set of cells provided by the same or different AN708s of RAN704. For example, UE702 and RAN704 may use carrier aggregation to enable UE702 to connect to a set of component carriers corresponding to Pcells or Scells, respectively. In a dual connectivity scenario, the first AN708 may be a master node providing an MCG, and the second AN708 may be a secondary node providing an SCG. The first / second AN708 may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0149] The RAN704 may provide an air interface on the licensed spectrum or the unlicensed spectrum. To operate within the unlicensed spectrum, the node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCell / Scell. Before accessing the unlicensed spectrum, the node may perform medium / carrier sensing operations, for example, based on a listen-before-talk (LBT) protocol.

[0150] Alternatively, each UE702 provides radio information to one or more AN708s and / or one or more edge computing nodes (e.g., edge servers / hosts). The radio information may be in the form of one or more measurement reports and / or may include, for example, signal strength measurements, signal quality measurements, etc. Each measurement report is tagged with a timestamp and the location of the measurement (e.g., the current location of the UE702). For example, the measurements collected by the UE702 and / or included in measurement reports include the following: bandwidth (BW), network or cell load, latency, jitter, round trip time (RTT), number of interrupts, out-of-order delivery of data packets, transmit power, bit error rate, bit error ratio (BER), block error rate (BLER), packet error ratio (PER), packet loss rate, packet reception rate (PRR), data rate, peak data rate, end-to-end delay, signal-to-noise ratio (SNR), signal-to-noise and interference ratio (SINR), signal-plus-noise-plus-distortion to noise-plus-distortion (SINAD) ratio, and carrier-to-interference plus noise ratio (CINR). (ratio), Additive White Gaussian Noise (AWGN), Energy per bit to noise power density ratio (Eb / N0), Energy per chip to noise power density ratio (Ec / I0), Energy per chip to noise power density ratio (Ec / N0,Energy per chip to noise power density ratio, peak-to-average power ratio (PAPR), reference signal received power (RSRP), reference signal received path power (RSRPP), reference signal received quality (RSRQ), reference signal time difference (RSTD), Real-Time Kinematic (RTK), received signal strength indicator (RSSI), received channel power indicator (RCPI), received signal to noise indicator (RSNI), received signal code power (RSCP), average noise plus interference (ANPI). GNSS timing of cell frames for UE positioning of E-UTRAN or 5G / NR (e.g., timing between AP or RAN node reference time and GNSS-specific reference time of a given GNSS), GNSS code measurement (e.g., GNSS code phase (integer and fractional parts) of the spreading code of the i-th GNSS satellite signal), GNSS carrier phase measurement (e.g., the number of carrier phase cycles (integer and fractional parts) of the i-th GNSS satellite signal measured since locking on to the signal, also called accumulated delta range (ADR)), channel interference measurement, thermal noise power measurement, received interference power measurement, power histogram measurement, channel load measurement, STA statistics, relative time difference (RTD), Rx time delay, Rx timing error, Rx time delay, Rx timing error, ADR, arrival time difference (TDOA,This may include one or more of the following: time difference of arrival, observed TDOA (OTDOA), relative TOA (RTOA), angle of arrival (AoA), azimuth-AoA (A-AoA), zenith-AoA (Z-AoA), angle of departure (AoD), time of arrival (ToF), and / or other similar measurements. RSRP, RSSI, and / or RSRQ measurements are used for cell-specific reference signals, channel state information reference signals (CSI-RS), and / or synchronization signals (SS) or SS blocks for 3GPP networks (e.g., LTE or 5G / NR), and for various beacons, fast initial link setup (FILS), for WLAN / WiFi (e.g., [IEEE80211]) networks.The Fast Initial Link Setup may include RSRP, RSSI, RSRQ, RCPI, RSNI, and / or ANPI measurements of the discovery frame or probe response frame. 3GPP TS 36.214 v17.0.0(2022-03-31)(``[TS36214]''), 3GPP TS 38.215 v17.3.0(2023-03-30)(``[TS38215]''), 3GPP TS 38.314 v17.2.0(2023-01-13)(``[TS38314]''), [TS37355], IEEE Standard for Information Technology - Telecommunications and Information Exchange between Systems - Local and Metropolitan Area Networks - Specific Requirements - Part 11: Wireless LAN Medium Access Control(MAC) and Physical Layer(PHY) Specifications, IEEE Std 802.11-2020, pp.1-4379(26 Other measurements, such as those discussed in Feb. 2021 ("IEEE80211"), may be used as additional or alternative measurements. Alternatively, any of the above measurements (or combinations thereof) may be collected by one or more AN708s and provided to the edge computing node.

[0151] Furthermore, or alternatively, the measurements may include the following: measurements related to Data Radio Bearers (DRBs) (e.g., number of DRBs attempted to be configured, number of DRBs successfully configured, number of active DRBs released, DRB session activity time, number of DRBs attempted to be resumed, number of DRBs successfully resumed, etc.), measurements related to RRCs (e.g., average number of RRC connections, maximum number of RRC connections, average number of stored inactive RRC connections, maximum number of stored inactive RRC connections, number of attempted RRC connection establishments, number of successful and / or failed RRC connection establishments, etc.), measurements related to UE Context (UECNTX), measurements related to Radio Resource Utilization (RRUs) (e.g., total DL PRB utilization, total UL PRB utilization, distribution of total DL PRB utilization, distribution of total UL PRB utilization, DL PRBs used for data traffic, UL PRBs used for data traffic, total DL available PRBs, total UL available PRBs, etc.), and Registration Management (RM). Measurements related to Management, Session Management (SM) (number of PDU sessions that requested configuration, number of PDU sessions that were successfully configured, number of PDU sessions that failed to be configured, etc.), GTP Management (GTP) Measurements related to IP Management (IP) Measurements related to Policy Association (PA), Mobility Management (MM,Measurements related to Mobility Management (e.g., for inter-RAT, intra-RAT and / or intra-frequency / inter-frequency handovers and / or conditional handovers, the number of requested handover preparations, the number of successful handover preparations and / or failed handover preparations, the number of requested handover resource allocations, the number of successful handover resource allocations and / or failed handover resource allocations, the number of requested handover executions, the number of successful handover executions and / or failed handover executions, the average and / or maximum time of requested handover executions, the number of successful handover executions and / or failed handover executions per beam pair, etc.), measurements related to Virtualized Resources (VR), measurements related to Carriers (CARR), and QoS Flow (QF). Measurements related to Flow (e.g., number of active QoS flows released, number of QoS flows attempted to release, in-session activity time of QoS flows, in-session activity time of UE702, number of QoS flows attempted to configure, number of QoS flows successfully established, number of QoS flows that failed to configure, number of initial QoS flows attempted to configure, number of initial QoS flows successfully established, number of initial QoS flows that failed to configure, number of QoS flows attempted to correct, number of QoS flows that successfully corrected, number of QoS flows that failed to correct, etc.), measurements related to Application Triggering (AT), measurements related to Short Message Service (SMS), measurements related to Power, Energy and Environment (PEE), measurements related to NF service (NFS), measurements related to Packet Flow Description (PFD), measurements related to Random Access Channel (RACH), measurements related to Measurement Report (MR), Layer 1 measurements (L1M,It may include one or more of the following other performance metrics, such as those discussed in 3GPP TS 28.552 v18.2.0 (2023-03-30) ("TS28552"), 3GPP TS 32.425 v17.1.0 (2021-06-24) ("[TS32425]"), etc.

[0152] Wireless information may be reported in response to and / or periodically to trigger events. Alternatively, individual UE702s may report wireless information and / or other information relating to data transfer at either a low or high frequency, depending on the data transfer to be performed. Alternatively, edge compute nodes may request measurements from AN708 at a low or high frequency, or AN708 may provide measurements to edge compute nodes at a low or high frequency. Alternatively, edge compute nodes may obtain other relevant data, such as key performance indicators (KPIs), from other edge compute nodes, core network functions (NFs), application functions (AFs), and / or other UE702s, either together with or separately from measurement reports.

[0153] Furthermore, or alternatively, the RAN node 708 may also perform or collect various measurements, such as any of those discussed herein. Examples of measurements performed / collected by the RAN node 708 include secondary synchronization signal (SSS) transmit power (e.g., a linear average (in units of [W]) over the power contributions of resource elements carrying the secondary synchronization signal within the secondary synchronization signal (SSS) bandwidth), and UL relative arrival time (TUL-RTOA) (e.g., T0+t SRS Here, T0 is the nominal start time of SFN0 provided by the SFN initialization time [15, TS 38.455], and t SRS =(10n f +n sf ) × 10 -3 n f and n sf g is the system frame number and the SRS subframe number, respectively), NB Rx-Tx time difference (for example, T gNB-RX -TgNB-TX Defined as, where T gNB-RX This is the TRP reception timing of uplink subframe #i, which includes the SRS associated with the UE, and is defined by the first detected path in time. gNB-TX , UL Angle of Arrival (UL AoA) (e.g., estimated azimuth angle (A-AoA) and perpendicular angle (Z-AoA) of the UE702 with respect to the reference direction), UL SRS reference signal received power (UL SRS-RSRP) (e.g., linear average of the power contributions of resource elements carrying the sounding reference signal (SRS) in units of [W]), UL SRS reference signal received path power (UL SRS-RSRPP) (e.g., the linear average of the channel response at the i-th path delay of resource elements carrying the received UL SRS signal configured for measurement, where UL SRS-RSRPP at the first path delay is the power contribution corresponding to the path first detected in time), Timing Advance ("TA" or "T"). ADV )(For example, time difference T ADV =( T gNB-RX -T gNB-TX ) and here, T gNB-RX This is the TRP reception (Rx) timing of UL subframe #i containing PRACH transmitted from UE702, and is defined by the path that was first detected in time. gNB-TX This includes the TRP transmit (Tx) timing of DL subframe #j, which is temporally closest to subframe #i received from UE702. The detected PRACH is used to determine the start of one subframe containing that PRACH. gNB-RXReference points for this include the Rx antenna connector of a Type 1-C base station, the Rx antenna of a Type 1-O or 2-O base station (i.e., the center position of the Rx antenna's radiation area), and the Rx transceiver array boundary connector of a Type 1-H base station (see, for example, 3GPP TS 38.104). gNB-TX The reference points for include the Tx antenna connector for Type 1-C base stations, the Tx antenna for Type 1-O or 2-O base stations (i.e., the center position of the radiation area of ​​the Tx antenna), the Tx transceiver array boundary connector for Type 1-H base stations, and / or the UE-gNB RTT (e.g., the sum of the TA values ​​of the UE (e.g., see [TS38211] §4.3.1) and kmac; in some examples, the UE-gNB RTT is used for non-terrestrial networks).

[0154] Furthermore, or alternatively, if there are inconsistencies in the observed data from one or more UEs, one or more RAN nodes, and / or core network NFs (e.g., missing reports, erroneous data, etc.), simple imputation may be performed to supplement the acquired observed data, such as substituting values ​​from previous reports and / or historical data, or applying extrapolation filters. Furthermore, or alternatively, acceptable boundaries for observed data may be predetermined or configured. For example, CQI and MCS measurements may be configured to be only within ranges defined by appropriate 3GPP standards. If reported data values ​​do not make sense (e.g., values ​​exceed acceptable ranges / boundaries, etc.), such values ​​may be dropped for the current learning / training episode or epoch. For example, a packet delivery delay limit may be defined or configured, and packets determined to have been received after the packet delivery delay limit may be dropped.

[0155] The UE702 can also perform reference signal (RS) measurement and reporting procedures to provide a network with information regarding the quality of one or more wireless channels and / or generally the communication medium, and this information can be used to optimize various aspects of the communication system. For example, the measurement and reporting procedures performed by UE702 are 3GPP TS 38.211 v17.4.0 (2023-01-04) ("[TS38211]"), 3GPP TS 38.212 v17.5.0 (2023-03-30) ("[TS38212]"), 3GPP TS 38.213 v17.5.0 (2023-03-30) ("[TS38213]"), 3GPP TS 38.214 v17.5.0 (2023-03-30) ("[TS38214]"), [TS38215], and 3GPP TS 38.101-1 This may include v18.1.0(2023-04-07)("[TS38101-1]"), 3GPP TS 38.104 v18.1.0(2023-04-07)("[TS38104]"), 3GPP TS 38.133 v18.1.0(2023-04-07)("[TS38133]"), [TS38331], etc. The physical signal and / or reference signal may include a modulation reference signal (DM-RS), a phase-tracking reference signal (PT-RS), a positioning reference signal (PRS), a channel-state information reference signal (CSI-RS), a synchronization signal block (SSB), a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a sounding reference signal (SRS).

[0156] In any of the examples discussed herein, any suitable data acquisition and / or measurement mechanism may be used to acquire observational data. For example, data marking (e.g., sequence numbering), packet tracking, signal measurement, data sampling, and / or timestamp techniques may be used to determine any of the above metrics / observations. Data acquisition may be based on the occurrence of an event that triggers data acquisition. Alternatively, data acquisition may occur at the start or end of an event. Data acquisition may be continuous or discontinuous, and / or have start and stop times. Data acquisition techniques / mechanisms may or may not be specific to the hardware configuration / implementation, or may be based on various software parameters (e.g., OS type and version). Various configurations may be used to define any of the above data acquisition parameters. Such configurations may be defined by appropriate specifications / standards such as 3GPP (e.g., [SA6Edge]), ETSI (e.g., [MEC]), O-RAN (e.g., [O-RAN]), Intel® Smart Edge Open (formerly OpenNESS) (e.g., [ISEO]), IETF (e.g., MAMS [RFC8743]), IEEE / WiFi (e.g., [IEEE80211], [WiMAX], [IEEE16090], etc.), and / or any other similar standards discussed herein.

[0157] In a V2X scenario, UE702 or AN708 may be a roadside unit (RSU) or may operate as an RSU, where the RSU may represent any transport infrastructure entity used for V2X communication. The RSU may be implemented within or by a suitable AN or stationary (or relatively stationary) UE. An RSU implemented within or by a UE may be called a “UE-type RSU,” an eNB may be called an “eNB-type RSU,” a gNB may be called a “gNB-type RSU,” and so on. In one example, the RSU is a computing device coupled with a roadside radio frequency circuit that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry that stores intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. The RSU may provide very low-latency communication required for high-speed events such as collision avoidance and traffic warnings. Furthermore, or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing a traffic signal controller or a wired connection (e.g., Ethernet®) to a backhaul network. Furthermore, one or more V2X RATs may be used, which enable V2X nodes to communicate directly with infrastructure equipment (e.g., AN708) and / or other devices / nodes. In some implementations, at least two separate V2X RATs may be used, including a WLAN V2X (W-V2X) RAT based on IEEE V2X technology (e.g., DSRC for the US and ITS-G5 for Europe) and a cellular V2X (C-V2X) RAT based on 3GPP V2X technology (e.g., LTE V2X, 5G / NR V2X, and later). In one example, the C-V2X RAT may utilize a C-V2X air interface, and the WLAN V2X RAT may utilize a W-V2X air interface.

[0158] W-V2X RAT includes, for example, the IEEE Guide for Wireless Access in Vehicular Environments (WAVE) Architecture, IEEE STANDARDS ASSOCIATION, IEEE 1609.0-2019 (10 Apr. 2019) ("[IEEE16090]"), V2X Communications Message Set Dictionary, SAE INT'L (23 Jul. 2020) ("[J2735_202007]"), Intelligent Transport Systems in the 5 GHz frequency band (ITS-G5) (WAVE, DSRC, and the L1 and Layer 2 (L2, layer 2) portions of ITS-G5) and / or the IEEE Standard for Air Interface for Broadband Wireless Access Systems, IEEE Std 802.16-2017, pp.1-2726 (02 Mar. 2018) ("[WiMAX]"). The term "DSRC" refers to vehicle communications in the 5.9 GHz frequency band commonly used in the United States, and "ITS-G5" refers to vehicle communications in the 5.9 GHz frequency band in Europe. Since any number of different RATs that may be used in any geographic or political territory are applicable, the terms "DSRC" (used in the United States and in other territories) and "ITS-G5" (used in Europe and in other territories) may be used interchangeably throughout this disclosure. The access layer of the ITS-G5 interface is outlined in ETSI EN 302 663 V1.3.1 (2020-01) (hereinafter, "EN302663"), which describes the access layer of the ITS-S reference architecture. The ITS-G5 access layer includes Decentralized Congestion Control (DCC), as discussed in [IEEE80211] and ETSI TS 102 687 V1.2.1 (2018-04) ("[TS102687]").The access layer for 3GPP LTE-V2X-based interfaces is outlined, in particular, in ETSI EN 303 613 V1.1.1 (2020-01) and 3GPP TS 23.285 v16.2.0 (2019-12), while 3GPP 5G / NR-V2X is outlined, in particular, in 3GPP TR 23.786 v16.1.0 (2019-06) and 3GPP TS 23.287 v18.0.0 (2023-03-31) ("[TS23287]").

[0159] In the example where RAN704 is an E-UTRAN710 having one or more eNB712s, the E-UTRAN710 provides an LTE air interface (Uu) having parameters and characteristics such as those discussed in at least 3GPP TS 36.300 v17.2.0(2022-09-30) ("[TS36300]"). In the example where RAN704 is a next-generation (NG)-RAN having a set of gNB716s, each gNB716 connects to a 5G-enabled UE702 using a 5G-NR air interface (may also be called a Uu interface) having parameters and characteristics such as those discussed in [TS38300] among many other 3GPP standards. If NG-RAN714 includes a set of ng-eNB718s, one or more ng-eNB718s connect to the UE702 via 5G Uu and / or LTE Uu interfaces. The gNB716 and ng-eNB718 connect to the 5GC740 through their respective NG interfaces, which include the N2 interface, the N3 interface, and / or other interfaces. The gNB716 and ng-eNB718 are connected to each other on the Xn interface. Furthermore, each gNB716 is connected to each other via its respective Xn interface, and each ng-eNB718 is connected to each other via its respective Xn interface. In some examples, the NG interface may be divided into two parts: the NG user plane (NG-U) interface (e.g., the N3 interface) which carries traffic data between the NG-RAN714 node and the UPF748, and the NG control plane (NG-C) interface (e.g., the N2 interface) which is the signaling interface between the NG-RAN714 node and the AMF744. In some examples, individual gNB716 and / or individual ng-eNB718 may service several TRPs (e.g., remote units, remote radio heads, UL-SRS dedicated RPs, DL-PRS dedicated TPs, etc.).

[0160] NG-RAN714 may provide a 5G-NR air interface (also known as a Uu interface) having the following characteristics: variable SCS, CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL, polar, repetitive, simplex and Reed-Muller code for control, and LDPC for data. The 5G-NR air interface may depend on CSI-RS and PDSCH / PDCCH DMRS, similar to an LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for PDSCH phase tracking, and a tracking reference signal for time tracking. The 5G-NR air interface may operate in the FR1 band including the sub-6GHz band or the FR2 band including the 24.25GHz to 52.6GHz band. The 5G-NR air interface may include SSB, which is the region of the downlink resource grid including PSS / SSS / PBCH.

[0161] A 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCSs. For instance, a UE702 can be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is instructed to the UE702, the SCS of the transmission is also changed accordingly. Another example of a use case for BWPs relates to power saving. In particular, multiple BWPs can be configured for the UE702 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP with fewer PRBs can be used for data transmission under low traffic loads, while allowing power savings in the UE702 and, in some cases, the gNB716. A BWP with more PRBs can be used for scenarios with higher traffic loads.

[0162] In some implementations, an individual gNB716 may contain a set of gNB-CUs and gNB-DUs. Alternatively, a gNB716 may contain one or more RUs. In these implementations, a gNB-CU may be connected to each gNB-DU via its respective F1 interface. For network sharing with multiple cell ID broadcasts, each cell identity associated with a subset of PLMNs corresponds to a gNB-DU and the gNB-CU to which it is connected, sharing the same physical layer cell resources. For resilience, a gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. Furthermore, a gNB-CU can be separated into gNB-CU control plane (gNB-CU-CP) functionality and gNB-CU user plane (gNB-CU-UP) functionality. A gNB-CU-CP is connected to a gNB-DU via the F1 control plane interface (F1-C), a gNB-CU-UP is connected to a gNB-DU via the F1 user plane interface (F1-U), and a gNB-CU-UP is connected to a gNB-CU-CP via the E1 interface. In some implementations, one gNB-DU is connected to only one gNB-CU-CP, and one gNB-CU-UP is connected to only one gNB-CU-CP. For flexibility, a gNB-DU and / or gNB-CU-UP may be connected to multiple gNB-CU-CPs depending on the appropriate implementation. One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP, and one gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP. Data transfer between gNB-CU-UP during a handover within gNB-CU-CP may be supported by Xn-U.

[0163] Similarly, individual ng-eNB718s may include sets of ng-eNB-CUs and ng-eNB-DUs. In these implementations, the ng-eNB-CUs and each ng-eNB-DU are connected to each other through their respective W1 interfaces. An ng-eNB may include an ng-eNB-CU-CP, one or more ng-eNB-CU-UPs, and one or more ng-eNB-DUs. The ng-eNB-CU-CP and ng-eNB-CU-UPs are connected via the E1 interface. An ng-eNB-DU is connected to the ng-eNB-CU-CP via the W1-C interface and to the ng-eNB-CU-UP via the W1-U interface. The general principles described herein with respect to gNB configurations also apply to ng-eNB configurations and their corresponding E1 and W1 interfaces, unless otherwise explicitly specified.

[0164] Nodes hosting the user plane portion of the PDCP protocol layer (e.g., gNB-CU, gNB-CU-UP, and those for EN-DC, MeNB, or SgNB depending on bearer partitioning) perform user inactivity monitoring and further notify nodes with control plane connections to the core network (e.g., E1, X2, etc.) of their inactivity or (re)activation. Nodes hosting the RLC protocol layer (e.g., gNB-DU) may also perform user inactivity monitoring and further notify nodes hosting the control plane (e.g., gNB-CU or gNB-CU-CP) of their inactivity or (re)activation.

[0165] In these implementations, NG-RAN714 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN714 architecture (e.g., NG-RAN logical nodes and the interfaces between them) is part of the RNL. For each NG-RAN interface (e.g., NG, Xn, F1, etc.), the relevant TNL protocol and function are specified. The TNL provides services for user plane transport and / or signaling transport. In an NG-Flex configuration, each NG-RAN node is connected to all AMF744s in an AMF set within an AMF region that supports at least one slice also supported by the NG-RAN node. The AMF set and AMF region are defined in [TS23501].

[0166] RAN704 is communicatively coupled to CN720, which includes network elements and / or network functions (NFs) to provide various functions for supporting data and telecommunications services to customers / subscribers (e.g., UE702). The components of CN720 may be implemented in one physical node or separate physical nodes. In some examples, NFV may be used to virtualize some or all of the functions provided by the network elements of CN720 onto physical computing / storage resources in servers, switches, etc. Logical instantiations of CN720 may be called network slices, and some logical instantiations of CN720 may be called network subslices.

[0167] CN720 may also be LTE CN722 (also called Evolved Packet Core (EPC) 722), and EPC722 may include MME724, SGW726, SGSN728, HSS730, PGW732, and PCRF734 coupled to each other on the interface (or "reference point") as shown in the figure. The NF in EPC722 is briefly introduced as follows: MME724 implements mobility management functions to track the current location of UE702 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc. SGW726 terminates the S1 interface to RAN710 and routes data packets between RAN710 and EPC722. SGW726 may also be a local mobility anchor point for handover between RAN nodes, and may also provide an anchor for 3GPP mobility. Other roles may include lawful intercept, billing, and any policy enforcement. SGSN728 tracks the location of UE702 and performs security functions and access control. SGSN728 may also perform EPC node signaling for mobility between different RAT networks, PDN and S-GW selection specified by MME724, MME724 selection for handover, etc. An S3 reference point between MME724 and SGSN728 enables the exchange of user and bearer information for mobility between 3GPP access networks in idle / active states. HSS730 contains a database for network users, including join-related information to support the handling of communication sessions by network entities. HSS730 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. An S6a reference point between HSS730 and MME724 may enable the transfer of join and authentication data for authenticating / authorizing user access to EPC720.PGW732 may terminate an SGI interface to a data network (DN) 736, which may include an application / content server (app) 738. PGW732 routes data packets between EPC722 and the data network 736. PGW732 is communicatively coupled to SGW726 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW732 may further include nodes (e.g., PCEF) for policy enforcement and billing data collection. Furthermore, an SGi reference point may communicatively couple PGW732 to the same or a different data network 736. PGW732 may communicatively couple to PCRF734 via a Gx reference point. PCRF734 is the policy and billing control element of EPC722. PCRF734 may communicatively couple to the application / content server 738 to determine appropriate QoS and billing parameters for the service flow. PCRF732 also provisions rules related to PCEF (via Gx reference points) using appropriate TFTs and QCIs.

[0168] CN720 may be a 5GC740 including an Authentication Server Function (AUSF) 724, an Access and Mobility Management Function (AMF) 744, a Session Management Function (SMF) 746, a User Plane Function (UPF) 748, a Network Slice Selection Function (NSSF) 750, a Network Exposure Function (NEF) 752, a Network Repository Function (NRF) 754, a Policy Control Function (PCF) 756, a Unified Data Management (UDM) 758, a Unified Data Repository (UDR) 759, and a Unified Data Repository (AF) 760, which are coupled to each other on various interfaces as shown in the figure. The NFs 740 within the 5GC are briefly introduced as follows.

[0169] The AUSF 742 stores data for the authentication of the UE 702 and processes functions related to authentication. The AUSF 742 may facilitate a common authentication framework for various access types.

[0170] AMF744 may also enable other functions of 5GC740 to communicate with UE702 and RAN704 and participate in notifications regarding mobility events related to UE702. AMF744 also serves roles in registration management (e.g., for registering UE702), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF744 provides transport for SM messages between UE702 and SMF746 and functions as a transparent proxy for routing SM messages. AMF744 also provides transport for SMS messages between UE702 and SMSF. AMF744 interacts with AUSF742 and UE702 to perform various security anchor and context management functions. Further, AMF744 is the termination point of the RAN CP interface including the N2 reference point between RAN704 and AMF744. AMF744 is also the termination point of NAS (N1) signaling and performs NAS encryption and integrity protection.

[0171] The AMF744 also supports NAS signaling with the UE702 over the N3IWF interface. The N3IWF provides access to untrusted entities. The N3IWF may be the termination point of the N2 interface between the (R)AN704 and the AMF744 for the control plane, or the termination point of the N3 reference point between the (R)AN704 and the AMF744 for the user plane. Thus, the AMF744 handles N2 signaling from the SMF746, encapsulates / decapsulates packets for IPSec and N3 tunneling for PDU sessions and QoS, marks N3 user plane packets on the uplink, and implements QoS corresponding to N3 packet marking, taking into account the QoS requirements associated with such marking received on N2. N3IWF may also relay UL and DL control plane NAS signaling between UE702 and AMF744 via the N1 reference point between UE702 and UPF748, and relay uplink and downlink user plane packets between UE702 and UPF748. N3IWF also provides a mechanism for establishing an IPsec tunnel with UE702. AMF744 may expose a Namf service-based interface, which may be a termination point for the N14 reference point between the two AMFs, and the N17 reference point between AMF744 and 5G-EIR (not shown in Figure 7).

[0172] The SMF746 is responsible for SM (e.g., session establishment and tunnel management between UPF748 and AN708), UE IP address allocation and management (including permission for arbitrary selection), selection and control of UP functions, configuration of traffic steering in UPF748 for routing traffic to appropriate destinations, termination of interfaces toward policy control functions, policy enforcement, control of some aspects of billing and QoS, lawful interception (for SM events and interfaces to LI systems), termination of the SM portion of NAS messages, downlink data notification, initiation of AN-specific SM information sent to AN708 via AM744 on N2, and determination of the session's SSC mode. SM refers to the management of PDU sessions, and PDU sessions or "sessions" refers to PDU connectivity services that provide or enable the exchange of PDUs between UE702 and DN736. SMF746 may also include the following features to support edge computing extensions: selection of EASDF761 and provision of its address to the UE as a DNS server for PDU sessions; use of EASDF761 as defined in [TS23548]; and provision and updating of ECS address configuration information to the UE to support the application layer architecture as defined in [TS23558]. The procedure for discovering and selecting EASDF is discussed in [TS23501]§6.3.23.

[0173] The UPF748 functions as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to data network 736, and a branching point for supporting multi-homed PDU sessions. The UPF748 also performs packet routing and forwarding, performs packet inspection, enforces the user plane portion of policy rules, lawfully intercepts packets (UP collection), performs traffic usage reporting, performs QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), performs uplink traffic verification (e.g., SDF-to-QoS flow mapping), performs transport-level packet marking on uplinks and downlinks, and performs downlink packet buffering and downlink data notification triggers. The UPF748 may include an uplink classifier to support routing traffic flows to the data network.

[0174] The NSSF750 selects a set of network slice instances to serve the UE702. The NSSF750 also determines, if necessary, the mapping to the authorized NSSAI and the joined S-NSSAI. The NSSF750 also determines the set of AMFs to be used to serve the UE702, or, based on the appropriate configuration, determines a list of candidate AMF744s by potentially querying the NRF754. The selection of a set of network slice instances for the UE702 may also be triggered by the AMF744 to which the UE702 is registered by interacting with the NSSF750, which may result in a change to the AMF744. The NSSF750 may interact with the AMF744 via the N22 reference point and communicate with another NSSF in the visited network via the N31 reference point (not shown).

[0175] NEF752 securely exposes services and capabilities provided by 3GPP NFs for third parties, internal exposure / re-exposure, AF760, edge computing or fog computing systems (edge ​​computing nodes), etc. In such examples, NEF752 may authenticate, authorize, or throttle AFs. NEF752 may also translate information exchanged with AF760 and information exchanged with internal network capabilities. For example, NEF752 may translate between AF service identifiers and internal 5GC information. NEF752 may also receive information from other NFs based on the exposed capabilities of other NFs. This information may be stored in NEF752 as structured data, or in a data storage NF using a standardized interface. The stored information can then be re-exposed by NEF752 to other NFs and AFs, or used for other purposes such as analysis.

[0176] The NRF754 supports service discovery functionality, receiving NF discovery requests from NF instances and providing information about discovered NF instances to the NF instances. The NRF754 also maintains information about available NF instances and the services they support. The NRF754 also supports service discovery functionality, receiving NF discovery requests from NF instances or SCPs (not shown) and providing information about discovered NF instances to the NF instances or SCPs.

[0177] The PCF756 provides policy rules to control plane functions to enforce policy rules and supports a unified policy framework for managing network behavior. The PCF756 may also implement a front-end to access subscription information related to policy decisions in the UDR759 of the UDM758. In addition to communicating with functions on a reference point as shown in the diagram, the PCF756 presents an Npcf service-based interface.

[0178] The UDM758 processes join-related information to support the handling of communication sessions by network entities and stores join data for the UE702. For example, join data may be communicated via an N8 reference point between the UDM758 and the AMF744. The UDM758 may include two parts: an application frontend and a UDR. The UDR may store join data and policy data for the UDM758 and PCF756, and / or structured data for public and application data for the NEF752 (including a PFD for application discovery and application request information for multiple UE702s). A Nudr service-based interface may be presented by the UDR, allowing the UDM758, PCF756, and NEF752 to access specific sets of stored data, read notifications of relevant data changes in the UDR, update (e.g., add, modify), delete, and join. The UDM758 may also include a UDM-FE, which is responsible for credential processing, location management, join management, etc. Several different frontends may serve the same user in different transactions. The UDM-FE accesses the enrollment information stored in the UDR and performs authentication certificate processing, user identification processing, access permission, enrollment / mobility management, and enrollment management. In addition to communicating with other NFs on a reference point as shown in the diagram, the UDM758 may present a Nudm service-based interface.

[0179] The Edge Application Server Discovery Function (EASDF) 761 exposes a Neasdf service-based interface and connects to the SMF 746 via the N88 interface. One or more EASDF instances may reside within the PLMN, and the interaction between the 5GC NF and the EASDF 761 takes place within the PLMN. The EASDF 761 includes one or more of the following functions: registration with the NRF 754 for discovery and selection of the EASDF 761, processing DNS messages in accordance with instructions from the SMF 746, and / or termination of DNS security when used. Processing DNS messages in accordance with instructions from SMF746 includes one or more of the following functions: receiving DNS message processing rules and / or BaselineDNSPattern from SMF746; exchanging DNS messages with and from UE702; forwarding DNS messages to C-DNS or L-DNS for DNS queries; adding the EDNS client subnet (ECS) option for FQDNs to DNS queries; reporting information about received DNS messages to SMF746; and / or buffering / discarding DNS messages from UE702 or DNS servers. EASDF has a direct user plane connection (e.g., without NAT) over N6 for the transmission of DNS signaling exchanged with UE. The placement of NAT between EASDF761 and PSA UPF748 may or may not be supported. Further embodiments of EASDF761 are discussed in [TS23548].

[0180] AF760 provides application influence on traffic routing, provides access to NEF752, and interacts with the policy framework for policy control. AF760 may also influence the (re)selection and traffic routing of UPF748. Based on operator placement, when AF760 is considered a trusted entity, the network operator may allow AF760 to interact directly with the relevant NF. In some implementations, AF760 is used in edge computing implementations.

[0181] The 5GC740 may enable edge computing by selecting an operator / third-party service that is geographically closer to where the UE702 is attached to the network. This may reduce latency and load on the network. In an implementation of edge computing, the 5GC740 may select a UPF748 closer to the UE702 and perform traffic steering from the UPF748 to the DN736 via the N6 interface. This may be based on UE join data, UE location, and information provided by the AF760, which allows the AF760 to influence the (re)selection and traffic routing of the UPF.

[0182] The data network (DN) 736 may represent various network operator services, internet access, or third-party services that may be provided by one or more servers, for example, including an application (app) / content server 738. DN736 may also be, for example, an operator-external public, private PDN, or an operator-internal packet data network for providing IMS services. In this example, the app server 738 can connect to IMS via an S-CSCF or I-CSCF. In some implementations, DN736 may represent one or more local area DNs (LA DNs), where the local area DN is a DN736 (or DN name (DNN)) accessible by the UE 702 within one or more specific areas. Outside these specific areas, the UE 702 cannot access the LADN / DN736.

[0183] Furthermore, or alternatively, DN736 may be Edge DN736, which is a (local) DN that supports the architecture for enabling edge applications. In these examples, app server 738 may represent a physical hardware system / device that provides app server functionality, and / or application software that resides in the cloud or on an edge compute node running server functionality. In some examples, app / content server 738 provides an edge hosting environment that provides the support necessary for running the edge application server.

[0184] In some examples, 5GS can use one or more edge compute nodes to provide interfaces and offload the processing of wireless communication traffic. In these examples, the edge compute nodes may be contained within one or more RAN710, 714, or they may be located in the same location as one or more RAN710, 714. For example, an edge compute node can provide connectivity between RAN714 and UPF748 within a 5GC740. The edge compute node can handle wireless connectivity with RAN710 and UPF748 using one or more NFV instances instantiated on the virtualization infrastructure within the edge compute node.

[0185] In some implementations, edge compute nodes provide a distributed computing environment for application and service hosting, and also provide storage and processing resources so that data and / or content can be processed closer to subscribers (e.g., users of UE702) for faster response times. Edge compute nodes also support a multi-tenancy runtime and hosting environment for applications, including, among other things, virtual appliance applications, middleware applications and infrastructure services, content delivery services including content caching, mobile big data analytics, and compute offloading, which can be delivered as packaged virtual machine (VM) images. Computation offloading includes offloading compute tasks, workloads, applications and / or services from UE702, CN720, DN736 and / or Server 738 to edge compute nodes or vice versa. For example, a device application or client application running on UE702 may offload application tasks or workloads to one or more edge compute nodes. In another example, an edge compute node may offload application tasks or workloads to a set of UE702s (e.g., for distributed machine learning computations).

[0186] An edge compute node may include, or be part of, an edge system that uses one or more edge computing technologies (ECT) (also known as an “edge computing framework”). An edge compute node may also be called an “edge host” or “edge server”. An edge system includes a collection of edge servers and edge management systems (not shown) necessary to run edge computing applications within an operator network or a subset of an operator network. An edge server is a physical computer system that includes an edge platform and / or virtualization infrastructure and is capable of providing compute, storage, and network resources to edge computing applications. Each edge server is located at the edge of the corresponding access network and configured to provide compute resources and / or various services (e.g., offloading compute tasks and / or workloads, cloud computing capabilities, IT services, and other similar resources and / or services as discussed herein) relatively close to the UE702. The VI of an edge compute node provides a virtualization environment and virtualization resources for the edge host, and edge computing applications may run as VMs and / or application containers on top of the VI.

[0187] In one exemplary implementation, the ECT includes ETSI GR MEC 001 v3.1.1(2022-01), ETSI GS MEC 003 v3.1.1(2022-03), ETSI GS MEC 009 v3.1.1(2021-06), ETSI GS MEC 010-1 v1.1.1(2017-10), ETSI GS MEC 010-2 v2.2.1(2022-02), ETSI GS MEC 011 v2.2.1(2020-12), ETSI GS MEC 012 V2.2.1(2022-02), ETSI GS MEC 013 V2.2.1(2022-01), ETSI GS MEC 014 v2.1.1(2021-03), ETSI GS MEC 015 v2.1.1(2020-06), ETSI GS MEC 016 v2.2.1(2020-04), ETSI GS MEC 021 v2.2.1(2022-02), ETSI GR MEC 024 v2.1.1(2019-11), ETSI GS MEC 028 V2.2.1(2021-07), ETSI GS MEC 029 v2.2.1(2022-01), ETSI MEC GS 030 v2.1.1(2020-04), ETSI GR MEC 031 The MEC framework and / or operation therein is as discussed in v2.1.1(2020-10), U.S. Provisional Application No. 63 / 003,834 ("US'834") filed on 1 April 2020, and International Application No. PCT / US2020 / 066969 ("PCT'696") filed on 23 December 2020 (collectively referred to herein as "MEC"), and all of the contents of each of these are incorporated herein by reference.This exemplary implementation (and / or any other exemplary implementations discussed herein) also includes ETSI GR NFV 001 V1.3.1(2021-03), ETSI GS NFV 002 V1.2.1(2014-12), ETSI GR NFV 003 V1.6.1(2021-03), ETSI GS NFV 006 V2.1.1(2021-01), ETSI GS NFV-INF 001 V1.1.1(2015-01), ETSI GS NFV-INF 003 V1.1.1(2014-12), ETSI GS NFV-INF 004 V1.1.1(2015-01), and ETSI GS NFV-MAN 001. v1.1.1(2014-12), and / or FNV and / or other similar virtualization technologies such as Israel et al., OSM Release FIVE Technical Overview, ETSI OPEN SOURCE MANO, OSM White Paper, 1st ed.(Jan.2019), https: / / osm.etsi.org / images / OSM-Whitepaper-TechContent-ReleaseFIVE-FINAL.pdf (collectively referred to as "[ETSINFV]"), all of which are incorporated herein by reference.Other virtualization technologies and / or service orchestration and automation platforms may be used, such as the 3GPP Service Based Management Architecture (SBMA), as discussed in, for example, E2E Network Slicing Architecture, GSMA, Official Doc. NG.127, v1.0 (03 Jun.2021), https: / / www.gsma.com / newsroom / wp-content / uploads / / NG.127-v1.0-2.pdf, Open Network Automation Platform (ONAP) documentation, Release Istanbul, v9.0.1 (17 Feb.2022), https: / / docs.onap.org / en / latest / index.html ("[ONAP]"), and 3GPP TS 28.533 v17.1.0 (2021-12-23) ("[TS28533]"), all of which are incorporated herein by reference.

[0188] In another exemplary implementation, ECT is the O-RAN framework and / or operates accordingly. Typically, vendors and carriers of front-end and back-end devices work closely together to ensure compatibility. A drawback of such a working model is that plug-and-play with other devices becomes extremely difficult, which can hinder innovation. To address this and promote openness and interoperability at all levels, several key players interested in the wireless domain (e.g., carriers, device manufacturers, academic institutions, etc.) formed the Open RAN Alliance ("O-RAN") in 2018. The O-RAN network architecture is the building block for designing a virtualized RAN on programmable hardware with radio access control powered by AI / ML. Various aspects of the O-RAN architecture are described in O-RAN Working Group 1(Use Cases and Overall Architecture): O-RAN Architecture Description, O-RAN ALLIANCE WG1, O-RAN Architecture Description v08.00, Release R003(Mar.2023), O-RAN Operations and Maintenance Architecture Specification v04.00, O-RAN ALLIANCE WG1(Feb.2021), O-RAN Working Group 2 AI / ML workflow description and requirements v01.03 O-RAN ALLIANCE WG2(Oct.2021), O-RAN Working Group 2(Non-RT RIC and A1 interface WG): R1 interface: General Aspects and Principles 4.0, v04.00, Release R003(Mar.2023), O-RAN Working Group 2(Non-RT RIC and A1 interface WG) Non-RT RIC Architecture v02.01(Oct.2022)、O-RAN Working Group 3(Near-Real-time RAN Intelligent Controller and E2 Interface Working Group): Near-RT RIC Architecture, v04.00, Release R003(Mar.2023)、O-RAN Working Group 4(Open Fronthaul Interfaces WG) Control, User and Synchronization Plane Specification, v11.00, Release R003(Mar.2023)、O-RAN Fronthaul Working Group 4 Cooperative Transport Interface Transport Control Plane Specification, v03.00(Oct.2022)、O-RAN Fronthaul Working Group 4 Cooperative Transport Interface Transport Management Plane Specification, v11.00, Release R003(Mar.2023)、O-RAN Open X-haul Transport Working Group Management interfaces for Transport Network Elements, v05.00, Release R003(Mar.2023)、O-RAN Open Transport Working Group 9 Xhaul Packet Switched Architectures and Solutions, v03.00, Release R003(Mar.2023)、O-RAN Open X-haul Transport Working Group Synchronization Architecture and Solution Specification, v03.00(Oct.2022)、O-RAN Open Xhaul Transport WG9 WDM-based Fronthaul Transport, v03.This is described in v08.00, Release R003 (Mar. 2023), O-RAN Operations and Maintenance Architecture (v08.00, Release R003 (Mar. 2023) ("ORAN OAM-Arch"), and O-RAN Operations and Maintenance Interface Specification (v09.00, Release R003 (Mar. 2023) (collectively referred to as "O-RAN"), and all of the contents of each of these are incorporated herein by reference.

[0189] In another exemplary implementation, ECT is used with 3GPP TS 23.558 v18.1.0 (2022-12-23) ("[TS23558]"), 3GPP TS 23.501 v18.0.0 (2022-12-21) ("[TS23501]"), 3GPP TS 23.502 v18.1.1 (2023-04-05) ("[TS23502]"), 3GPP TS 23.548 v18.1.0 (2023-04-06) ("[TS23548]"), 3GPP TS 28.538 v18.2.0 (2023-03-30) ("[TS28538]"), and 3GPP TR 23.700-98. v18.0.0(2022-12-23)(``[TR23700-98]''), 3GPP TS 23.222 v18.0.0(2022-12-23)(``[TS23222]''), 3GPP TS 33.122 v18.0.0(2022-12-16)(``[TS33122]''), 3GPP TS 29.222 v17.1.0(2021-06-25)(``[TS29222]''), 3GPP TS 29.522 v18.0.0(2022-12-16)("[TS29522]"), 3GPP TS 29.122 The 3rd Generation Partnership Project (3GPP) System Aspects Working Group 6 (SA6) Architecture for enabling Edge Applications ("referred to as 3GPP Edge Computing") and / or operates in accordance with the 3rd Generation Partnership Project (3GPP) System Aspects Working Group 6 (SA6) Architecture for enabling Edge Applications ("3GPP Edge Computing"), as discussed in v18.0.0 (2022-12-16) ("TS29122"), 3GPP TS 23.682 v17.3.0 (2022-06-15) ("TS23682"), 3GPP TS 23.434 v18.3.0 (2022-12-23) ("TS23434"), and 3GPP TS 23.401 v18.0.0 (2022-12-21) (collectively referred to as "SA6Edge"), and all of the contents of each of these are incorporated herein by reference.

[0190] In another exemplary implementation, ECT is and / or operates in accordance with the Intel® Smart Edge Open framework, as discussed in the Intel® Smart Edge Open Developer Guide, version 21.09 (30 Sep. 2021) ("ISEO"), available at https: / / smart-edge-open.github.io / , all of which are incorporated herein by reference.

[0191] In another exemplary implementation, the ECT operates according to a Multi-Access Management Service (MAMS), as discussed in Kanugovi et al., Multi-Access Management Services (MAMS), INTERNET ENGINEERING TASK FORCE (IETF), Request for Comments (RFC) 8743 (Mar. 2020) (“[RFC8743]”), Ford et al., TCP Extensions for Multipath Operation with Multiple Addresses, IETF RFC 8684 (Mar. 2020), De Coninck et al., Multipath Extensions for QUIC (MP-QUIC), IETF DRAFT-DECONINCK-QUIC-MULTIPATH-07, IETA, QUIC Working Group (03-May-2021), Zhu et al., User-Plane Protocols for Multiple Access Management Service, IETF DRAFT-ZHU-INTAREA-MAMS-USER-PROTOCOL-09, IETA, INTAREA (04-Mar-2020), and Zhu et al., Generic Multi-Access (GMA) Convergence Encapsulation Protocols, IETF RFC 9188 (Feb. 2022) (collectively referred to as “[MAMS]”), and all of the respective contents thereof are incorporated herein by reference.

[0192] The above examples of edge computing frameworks / ECTs and service deployments are merely illustrative examples of ECTs, and it should be understood that this disclosure may be applicable to many other edge computing / networking technologies or further edge computing / networking technologies in various combinations and layouts of devices located at the edge of a network, including various edge computing networks / systems described herein. Furthermore, the technologies disclosed herein may relate to other IoT edge network systems and configurations, and other intermediate processing entities and architectures may also be applicable to this disclosure. Examples of such edge computing / networking technologies include [MEC], [O-RAN], [ISEO], [SA6Edge], Content Delivery Networks (CDNs), Mobility Service Provider (MSP) edge computing and / or MaaS (Mobility as a Service) provider systems (e.g., used in AECC architectures), Nebula edge cloud systems, Fog computing systems, Cloudlet edge cloud systems, Mobile Cloud Computing (MCC) systems, Central Office Re-architected as a Datacenter (CORD), Mobile CORD (M-CORD) and / or Converged Multi-Access and Core (COMAC) systems. Furthermore, the technologies disclosed herein may relate to other IoT edge network systems and configurations, and other intermediate processing entities and architectures may also be used for the purposes of this disclosure.

[0193] The 5GC740 interface includes reference point and service-based interfaces. The reference points are N1 (between UE702 and AMF744), N2 (between RAN714 and AMF744), N3 (between RAN714 and UPF748), N4 (between SMF746 and UPF), N5 (between PCF756 and AF760), N6 (between UPF748 and DN736), N7 (between SMF746 and PCF756), N8 (between UDM758 and AMF744), N9 (between two UPF748s), N10 (between UDM758 and SMF746), N11 (AM This includes N12 (between F744 and SMF746), N13 (between AUSF742 and AMF744), N14 (between two AMF744s, not shown), N15 (between PCF756 and AMF744 in a non-roaming scenario, or between PCF756 and AMF744 in a visited network in a roaming scenario), N16 (between two SMF746s, not shown), and N22 (between AMF744 and NSSF750). Other reference point representations not shown in Figure 7 may also be used. The service-based representation in Figure 7 represents NFs in the control plane that allow other authorized NFs to access these services. Service-based interfaces (SBIs) include Namf (SBI exposed by AMF744), Nsmf (SBI exposed by SMF746), Nnef (SBI exposed by NEF752), Npcf (SBI exposed by PCF756), Nudm (SBI exposed by UDM758), Naf (SBI exposed by AF760), Nnrf (SBI exposed by NRF754), Nnssf (SBI exposed by NSSF750), and Nausf (SBI exposed by AUSF742). Other service-based interfaces not shown in Figure 7 (e.g., Nudr, N5g-eir, and Nudsf) may also be used. In some examples, NEF752 can provide an interface to edge compute node 736x, which can then be used to handle wireless connectivity with RAN714.

[0194] Although not shown in Figure 7, System 700 also includes, for example, the following functions discussed in [TS23501]: Unstructured Data Storage Function (UDSF), Network Slice Admission Control Function (NSACF), Network Slice-specific and SNPN Authentication and Authorization Function (NSSAAF), UE Radio Capability Management Function (UCMF), 5G-Equipment Identity Register (5G-EIR), Network Data Analytics Function (NWDAF), Charge Function (CHF), Time Sensitive Networking AF (TSN AF), Time Sensitive Communication and Time Synchronization Function (TSCTSF), Data Collection Coordination Function (DCCF), and Analytics Data Repository Function (ADRF). Repository Function), Messaging Framework Adapter Function (MFAF), Non-Seamless WLAN Offload Function (NSWOF), Service Communication Proxy (SCP), Security Edge Protection Proxy (SEPP), Non-3GPP Interworking Function (N3IWF,It may include non-3GPP interworking functions (NFs) not shown, such as Non-3GPP Interworking Function (Non-3GPP Interworking Function), Trusted Non-3GPP Gateway Function (TNGF), Wireline Access Gateway Function (W-AGF), and / or Trusted WLAN Interworking Function (TWIF).

[0195] Figure 8 schematically illustrates the wireless network 800. The wireless network 800 includes a UE802 that wirelessly communicates with an AN804. The UE802 may be identical or similar to any of the UEs discussed herein, such as UE102, UE702, hardware resource 900, and / or any other UE discussed herein, and may be substantially interchangeable. The AN804 may be identical or similar to any of the ANs (Network Access Nodes (NANs)) discussed herein, such as TRP108, AP706, AN708, RAN704, hardware resource 900, and / or any other AN / NAN discussed herein, and may be substantially interchangeable.

[0196] UE802 may be coupled to AN804 for communication via connection 806. Connection YY06 is shown as an air interface to enable communication coupling and can be coupled with cellular communication protocols such as LTE or 5G NR protocols operating at mmWave or sub-6GHz frequencies.

[0197] UE802 includes a host platform 808 coupled with a modem platform 810. The host platform 808 includes an application processing circuit 812, which may be coupled with a protocol processing circuit 814 of the modem platform 810. The application processing circuit 812 may run various applications for UE802 that source / sink application data. The application processing circuit 812 may further implement one or more layer operations for sending / receiving application data to a data network. These layer operations include transport (e.g., UDP) and internet (e.g., IP) operations.

[0198] The protocol processing circuit 814 may implement one or more layer operations to facilitate the transmission or reception of data over connection 806. Layer operations implemented by the protocol processing circuit 814 include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0199] The modem platform 810 may further include a digital baseband circuit 816 that can implement one or more layer operations that lie "below" the layer operations performed by the protocol processing circuit 814 in the network protocol stack. These operations include PHY operations that include, for example, HARQ-ACK functionality, scrambling / descrambling, coding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bitmetric determination, multi-antenna port precoding / decoding (including one or more of space-time coding, space-frequency coding, or spatial coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and one or more other related functions.

[0200] The modem platform 810 may further include a transmitting circuit 818, a receiving circuit 820, an RF circuit 822, and an RF front end (RFFE) 824, which include or are connected to one or more antenna panels 826. In short, the transmitting circuit 818 includes a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receiving circuit 820 includes an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 822 includes a low-noise amplifier, a power amplifier, a power tracking component, etc.; and the RFFE 824 includes filters (e.g., surface / bulk acoustic wave filters), switches, an antenna tuner, a beamforming component (e.g., a phase array antenna component), etc. The selection and arrangement of components for the transmitting circuit 818, receiving circuit 820, RF circuit 822, RFFE 824, and antenna panel 826 (collectively referred to as the "transmitting / receiving components" or "Tx / Rx components") may be specific to the details of the implementation, such as whether the communication is TDM or FDM, or whether the frequency is mmWave or sub-6GHz. In some examples, the transmitting / receiving components may be arranged in multiple parallel transmit / receive chains, or they may be located on the same or different chips / modules.

[0201] In some examples, the protocol processing circuit 814 includes one or more instances of a control circuit (not shown) for providing control functions to the transmit / receive components. UE reception may be established by and through antenna panel 826, RFFE 824, RF circuit 822, receiving circuit 820, digital baseband circuit 816, and protocol processing circuit 814. In some examples, antenna panel 826 may receive transmissions from AN804 by received beamforming signals received by a set of antennas / antenna elements of one or more antenna panels 826.

[0202] UE transmission may be established by and through the protocol processing circuit 814, the digital baseband circuit 816, the transmitting circuit 818, the RF circuit 822, the RFFE 824, and the antenna panel 826. In some examples, the transmitting component of UE 804 may apply a spatial filter to the transmitted data to form a transmitted beam radiated by the antenna elements of the antenna panel 826. Similar to the UE802, the AN804 includes a host platform 828 coupled to a modem platform 830. The host platform 828 includes an application processing circuit 832 coupled to the protocol processing circuit 834 of the modem platform 830. The modem platform may further include a digital baseband circuit 836, a transmit circuit 838, a receive circuit 840, an RF circuit 842, an RFFE circuit 844, and an antenna panel 846. The components of the AN804 are similar to the components of the same name in the UE802 and may be substantially interchangeable. In addition to performing data transmission / reception as described above, the components of the AN808 may perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0203] Examples of antenna elements for antenna panel 826 and / or antenna elements for antenna panel 846 include planar inverted-F antennas (PIFA), monopole antennas, dipole antennas, loop antennas, patch antennas, Yagi antennas, parabolic antennas, omnidirectional antennas, and the like.

[0204] Figure 9 shows a component capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-temporary machine-readable storage medium) and executing one or more of the methods discussed herein. Specifically, Figure 9 shows a schematic diagram of a hardware resource 900 including one or more processors (or processor cores) 910, one or more memory / storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940 or other interface circuitry. In embodiments utilizing node virtualization (e.g., NFV), a hypervisor 902 may be run to provide an execution environment for one or more network slices / subslices for utilizing the hardware resource 900.

[0205] The processor 910 may include, for example, processors 912 and 914. The processor 910 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), other processors (including those discussed herein), or any appropriate combination thereof.

[0206] The memory / storage device 920 may include main memory, disk storage, or any appropriate combination thereof. The memory / storage device 920 may include, but is not limited to, any type of volatile, non-volatile, and semi-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.

[0207] The communication resource 930 may include interconnects or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 904 or one or more databases 906 or other network elements via the network 908. For example, the communication resource 930 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0208] Instruction 950 may include other executable code causing at least one of the following to perform one or more of the methods discussed herein: software, programs, applications, applets, apps, or processor 910. Instruction 950 may reside entirely or partially in at least one of the following: processor 910 (e.g., the processor's cache memory), memory / storage device 920, or any suitable combination thereof. Furthermore, any portion of instruction 950 may be transferred to hardware resource 900 from either peripheral device 904 or database 906. Thus, the memory of processor 910, memory / storage device 920, peripheral device 904, and database 906 are examples of computer-readable and machine-readable media.

[0209] 3. Exemplary Implementation Further examples of the methods, devices, systems, and networks described herein that are discussed herein include the following non-limiting exemplary implementations. Each of the following non-limiting examples may stand on its own or be combined in any permutation or combination with one or more of the other examples provided below or throughout this disclosure.

[0210] Example 1 includes a method for associating Timing Advance (TA) for single TRP and multi-TRP operation, where two TAs are associated with two TRP-IDs.

[0211] Example 2 includes a method for CSI prediction, where precoder prediction can be performed on the UE side or the gNB side.

[0212] Example 3 includes a method for CSI measurement, where the CSI-RS sampling period and maximum Doppler frequency are defined as Nyquist criterion Δt ≤ 1 / (2·f). max ) satisfies the condition.

[0213] Example 4 includes a method for designing a codebook, in which the new codebook is designed based on spatial, frequency, and time dimensions.

[0214] Example 5 includes a method that includes the step of performing one or more of Examples 1 to 4 and / or some other example methods herein.

[0215] Example 6 includes a method for operating a UE, which includes the steps of: receiving timing advance information for a serving cell, the timing advance information including the respective timing advances for a plurality of TRPs associated with the serving cell; and transmitting one or more uplink signals based on the timing advance information.

[0216] Example 7 includes the method of Example 6 and / or some other example herein, where the timing advance is associated with each TRP ID of multiple TRPs.

[0217] Example 8 includes the methods of Examples 6-7 and / or some other examples herein, wherein the step of transmitting one or more uplink signals includes the step of performing simultaneous multi-TRP transmission to two or more of the TRPs.

[0218] Example 9 includes a method that includes the step of performing one or more of Examples 1 to 8 and / or some other example methods herein.

[0219] Example Z01 includes one or more computer-readable media containing instructions, and the execution of instructions by the processor circuit causes the processor circuit to perform one of the methods in Examples 1 to 9.

[0220] Example Z02 includes a computer program that contains the instructions of Example Z01.

[0221] Example Z03 includes an application programming interface that defines functions, methods, variables, data structures, and / or protocols for the computer program of Example Z02.

[0222] Example Z04 includes an API or specification that defines or involves the use of any or part of Examples 1-9, or that defines a function, method, variable, data structure, protocol, etc., related to any or part of Examples 1-9.

[0223] Example Z05 includes a device that includes a circuit into which the instruction of Example Z01 has been loaded.

[0224] Example Z06 includes a device that includes a circuit capable of operating to execute the instructions of Example Z01.

[0225] Example Z07 includes an integrated circuit that includes one or more processor circuits from Example Z01 and one or more computer-readable media from Example Z01.

[0226] Example Z08 includes a computing system comprising one or more computer-readable media and processor circuits as in Example Z01.

[0227] Example Z09 includes a device that includes means for executing the instructions of Example Z01.

[0228] Example Z10 includes signals generated as a result of executing the instruction in Example Z01.

[0229] Example Z11 includes a data unit generated as a result of executing the instruction in Example Z01.

[0230] Example Z12 includes a data unit from Example Z10 and / or some other examples herein, where the data unit is a datagram, network packet, data frame, data segment, protocol data unit (PDU), service data unit (SDU), message, or database object.

[0231] Example Z13 includes a signal encoded in the data units of Example Z11 and / or Z12.

[0232] Example Z14 includes an electromagnetic signal that carries the instruction of Example Z01.

[0233] Example Z15 includes an apparatus that includes means for carrying out the methods of any one of Examples 1 to 9 and / or some other examples herein.

[0234] Example Z16 includes an edge compute node that runs a service as part of one or more edge applications instantiated on a virtualization infrastructure, the service relating to Examples 1-9, parts thereof, and / or any other examples herein.

[0235] 4. Terminology For the purposes of this disclosure, the following terms and definitions are applicable to the examples and embodiments discussed herein. As used herein, singular terms are intended to include plural forms unless the context clearly indicates otherwise. As used herein, the terms “comprises” and / or “comprising” specify the presence of the features, integers, steps, actions, elements and / or components mentioned, but do not exclude the presence or addition of one or more other features, integers, steps, actions, elements, components and / or groups thereof. The phrase “A and / or B” means (A), (B) or (A and B). For the purposes of this disclosure, the phrase “A, B and / or C” means (A), (B), (C), (A and B), (A and C), (B and C) or (A, B and C). The phrase “X” means one or more X or a set of X. The description may use phrases such as “in one embodiment,” “in some embodiments,” “in one implementation,” “in some implementations,” and “in some examples,” each of which may refer to one or more of the same or different embodiments, implementations, and / or examples. Furthermore, terms such as “comprising,” “including,” and “having” as used in this disclosure are synonymous.

[0236] The terms “master” and “slave” refer, in at least some examples, to a model of asymmetric communication or control in which one device, process, element, or entity ("master") controls one or more other devices, processes, elements, or entities ("slaves"). The terms “master” and “slave” are used in this disclosure only for their technical meanings. The terms “master” or “grandmaster” may be replaced by any of the following terms, namely “main,” “source,” “primary,” “initiator,” “requester,” “transmitter,” “host,” “maestro,” “controller,” “provider,” “producer,” “client,” “source,” “mix,” “parent,” “chief,” “manager,” “reference” (e.g., “reference clock”), etc. Furthermore, the term “slave” may be replaced by any of the following terms, namely “receiver,” “secondary,” “dependent,” “replica,” “target,” “responder,” “device,” “executor,” “agent,” “standby,” “consumer,” “peripheral,” “follower,” “server,” “child,” “helper,” “worker,” “node,” etc.

[0237] The terms “joined” and “communicatively joined” are used herein together with their derivatives. The term “joined” may mean that two or more elements are in direct physical or electrical contact with each other, that two or more elements are indirectly in contact with each other but still cooperate or interact with each other, and / or that one or more other elements are joined or connected between elements said to be joined together. The term “directly joined” may mean that two or more elements are in direct contact with each other. The term “communicatively joined” may mean that two or more elements are in contact with each other by means of communication, including through wired or other interconnection connections, through wireless communication channels or links, etc.

[0238] In at least some examples, the term “establish” or “establish” refers to an act, task, action, etc. (partial or complete) relating to actively or passively making something exist or preparing to make something exist (e.g., exposing a device identity or entity identity). Furthermore or alternatively, in at least some examples, the term “establish” or “establish” refers to an act, task, action, etc. (partial or complete) relating to initiating, starting or warming up a communication, or initiating, starting or warming up a relationship between two entities or elements (e.g., establishing a session, establishing a session, etc.). Furthermore or alternatively, in at least some examples, the term “establish” or “establish” refers to initiating something into a state of work readiness. In at least some examples, the term “established” refers to a state of being operational or ready for use (e.g., fully established). Furthermore, any definition of the term “establish” or “establish” as defined in any specification or standard may be used for the purposes of this disclosure, and such definition is not negated by any of the definitions above.

[0239] In at least some examples, the term “take” refers to the (partial or complete) act, task, operation, etc. of intercepting, moving, copying, taking, or acquiring (e.g., from memory, an interface, or a buffer) the original packet stream or a copy of the packet stream (e.g., a new instance). Other forms of taking or receiving may involve instantiating, enabling, or controlling the ability to take or receive a stream of packets (or the following parameters and templates or template values).

[0240] In at least some examples, the term “receive” refers to any action (or set of actions) involved in receiving or acquiring an object, data, data unit, etc., and / or the fact that the object, data, data unit, etc., has been received. In at least some examples, the term “receive” also refers to an object, data, data unit, etc., being pushed to a device, system, element, etc. (for example, often called a push model), or being pulled by a device, system, element, etc. (for example, often called a pull model).

[0241] In at least some examples, the term “element” refers to a unit that is indivisible at a given level of abstraction and has clearly defined boundaries, and an element may be any type of entity, including, for example, one or more devices, systems, controllers, network elements, modules, engines, components, etc., or combinations thereof. In at least some examples, the term “entity” refers to a separate element of a component, architecture, platform, device, and / or system. Furthermore, or alternatively, in at least some examples, the term “entity” refers to information being transferred as a payload.

[0242] In at least some examples, the term “measurement” refers to the observation and / or quantification of attributes of an object, event, or phenomenon. Further or alternatively, in at least some examples, the term “measurement” refers to a set of actions intended to determine a measurement or measurement result, and / or an actual instance or execution of actions that yield a measurement. Further or alternatively, in at least some examples, the term “measurement” refers to data recorded during testing. In at least some examples, the term “metric” refers to a quantity generated in the evaluation of a measurement. Further or alternatively, in at least some examples, the term “metric” refers to data derived from a set of measurements. Further or alternatively, in at least some examples, the term “metric” refers to a set of events that are combined with or possibly grouped into one or more values. Further or alternatively, in at least some examples, the term “metric” refers to a combination of measurements or a set of collected data points. Further or alternatively, in at least some examples, the term “metric” refers to a standard definition of a quantity generated in the evaluation of network performance and / or reliability that has intended utility and is carefully specified to convey the precise meaning of the measurements.

[0243] In at least some examples, the term “signal” refers to an observable change in quality and / or quantity. Further or alternatively, in at least some examples, the term “signal” refers to the ability to transmit information about an object, event, or phenomenon. Further or alternatively, in at least some examples, the term “signal” refers to any time-varying voltage, current, or electromagnetic wave that may or may not carry information. In at least some examples, the term “digital signal” refers to a signal constructed from a discrete set of waveforms of a physical quantity to represent a series of discrete values.

[0244] In at least some examples, the terms “ego” (e.g., in “ego device”) and “object” (e.g., in “data object”) refer to entities, elements, devices, systems, etc. that are under consideration or being examined. In at least some examples, the terms “neighbor” and “proximity” (e.g., in “proximity device”) refer to entities, elements, devices, systems, etc. other than ego devices or object devices.

[0245] In at least some examples, the term “identifier” refers to a value or set of values ​​that uniquely identifies an identity within a specific range. Further or alternatively, in at least some examples, the term “identifier” refers to a sequence of characters that identifies or indicates the identity of a unique object, element, or entity, or a unique class of an object, element, or entity. Further or alternatively, in at least some examples, the term “identifier” refers to a string used to identify or indicate an application, program, session, object, element, entity, variable, set of data, etc. In at least some examples, the previously mentioned “string” refers to one or more names, labels, words, numbers, letters, symbols, and / or any combination thereof. Further or alternatively, in at least some examples, the term “identifier” refers to a name, address, label, distinction index, and / or attribute. Further or alternatively, in at least some examples, the term “identifier” refers to an instance of identification. In at least some examples, the term “persistent identifier” refers to an identifier that is reused indefinitely by a device associated with the same person or group of people, or by another device. In at least some examples, the term “identification” refers to the process of recognizing an identity as distinct from other identities within a particular scope or context, which may involve processing identifiers to reference identities in an identity database. In at least some examples, the terms “application identifier,” “application ID,” or “app ID” refer to an identifier that can be mapped to a specific application, application instance, or application instance. In the context of 3GPP 5G / NR, in at least some examples, “application identifier” refers to an identifier that can be mapped to a specific application traffic detection rule.

[0246] In at least some examples, the term “circuit” refers to a circuit or a system of circuits configured to perform a particular function in an electronic device. A circuit or system of circuits may be part of, or include, one or more hardware components configured to provide the described functions, such as logic circuits, processors (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic controllers (PLCs), single-board computers (SBCs), system-on-chip (SoCs), system-in-packages (SiPs), multi-chip packages (MCPs), digital signal processors (DSPs), etc. Furthermore, the term “circuit” may also refer to a combination of one or more hardware elements and program code used to perform the functions of their program code. Some types of circuits may run one or more software or firmware programs to provide at least some of the described functions. Such a combination of hardware elements and program code may be called a specific type of circuit.

[0247] In at least some examples, 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 capable of recording, storing, and / or transferring digital data. In at least some examples, the term “processor circuit” refers to one or more application processors, one or more baseband processors, a physical 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 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 also be referred to as “processor circuit.”

[0248] In at least some instances, the terms “memory” and / or “memory circuit” refer to one or more hardware devices for storing data, including random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), magnetoresistive RAM (MRAM), conductive bridge random access memory (CB-RAM), spin transfer torque (STT)-MRAM, phase change RAM (PRAM), core memory, read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), flash memory, non-volatile RAM (NVRAM), magnetic disk storage medium, optical storage medium, flash memory device, or other machine-readable medium for storing data. The term “computer-readable media” includes, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other media capable of storing, containing, or transporting instructions or data.

[0249] In at least some examples, the term “interface circuit” refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. In at least some examples, the term “interface circuit” refers to one or more hardware interfaces, such as a bus, I / O interface, peripheral component interface, network interface card, etc.

[0250] In at least some examples, the term “Infrastructure Processing Unit” or “IPU” refers to an advanced networking device with enhanced accelerator and network connectivity (e.g., Ethernet®) that accelerates and manages infrastructure functions using tightly coupled, dedicated programmable cores. In some implementations, the IPU provides complete infrastructure offloading and an additional layer of security by acting as a control point for the host to run infrastructure applications. The IPU is capable of offloading the entire infrastructure stack from the host and can control how the host connects to this infrastructure. This provides the service provider with an additional layer of security and control implemented in hardware by the IPU.

[0251] In at least some examples, the term “device” refers to a physical entity embedded within or attached to another nearby physical entity, which has the ability to transmit digital information to or from that physical entity. In at least some examples, the term “controller” refers to an element or entity that has the ability to influence a physical entity by changing its state or moving the physical entity, etc. In at least some examples, the term “scheduler” refers to an entity or element that allocates resources (e.g., processor time, network links, memory space, etc.) to perform a task. In at least some examples, the term “network scheduler” refers to a node, element, or entity that manages network packets in the transmit and / or receive queues of one or more protocol stacks of a network access circuit (e.g., a network interface controller (NIC), a baseband processor, etc.). In at least some examples, the term “network scheduler” can be used interchangeably with the terms “packet scheduler,” “queuing rules,” or “qdisc,” and / or “queuing algorithm.”

[0252] In at least some examples, the term “terminal” refers to a point where a conductor from a component, device, or network terminates; and, or alternatively, in at least some examples, the term “terminal” refers to an electrical connector that acts as an interface to a conductor, creating a point to which an external circuit can be connected. In some examples, terminals may include electrical leads, electrical connectors, solder cups or buckets, etc.

[0253] In at least some examples, the terms “computation node” or “computation device” refer to an identifiable entity that implements a mode of computational operation, whether it is part of a larger system, a distributed collection of systems, or a standalone device. In some examples, a compute node may be referred to as a “computation device,” “computation system,” etc., whether it is operating as a client, server, or intermediate entity. A particular implementation of a compute node may be incorporated into a server, base station, gateway, roadside unit, on-premise unit, user equipment, end-consumer device, appliance, etc. For the purposes of this disclosure, the term “node” in at least some examples refers to and / or is interchangeable with terms such as “device,” “component,” “subsystem.”

[0254] In at least some examples, the term “computer system” refers to any type of interconnected electronic devices, computer devices, or components thereof. Furthermore, in at least some examples, the terms “computer system” and / or “system” refer to various components of a computer that are interconnected in a communicative manner. Furthermore, in at least some examples, the terms “computer system” and / or “system” refer to multiple computer devices and / or multiple computing systems that are interconnected in a communicative manner and configured to share computing and / or networking resources.

[0255] In at least some examples, the term “server” refers to a computing device or system that includes processing hardware and / or process space, associated storage media such as memory devices or databases, and, in some examples, appropriate applications as known in the art. The terms “server system” and “server” may be used interchangeably herein, and in at least some examples, these terms refer to one or more computing systems that provide access to a pool of physical and / or virtual resources. The various servers discussed herein include computer devices having rack computing architecture components, tower computing architecture components, blade computing architecture components, etc. A server may represent a cluster of servers, a server farm, a cloud computing service, or any other grouping or pool of servers that may be located in one or more data centers. A server may also be connected to or associated with one or more data storage devices (not shown). Furthermore, a server includes an operating system (OS) that provides executable program instructions for the general management and operation of individual server computer devices, and includes computer-readable media that, when executed by the server’s processor, stores instructions that enable the server to perform these intended functions. Appropriate implementations for the server's operating system and general functions are known or commercially available and can be easily implemented by those skilled in the art.

[0256] In at least some instances, the term “platform” refers to an environment on which instructions, program code, software elements, etc., can be executed or operate, and examples of such environments include architectures (e.g., motherboards, computing systems, etc.), one or more hardware elements (e.g., embedded systems, etc.), clusters of compute nodes, sets of distributed compute nodes or networks, operating systems, virtual machines (VMs), virtualization containers, software frameworks, client applications (e.g., web browsers, etc.) and associated application programming interfaces, cloud computing services (e.g., Platform as a Service (PaaS)), or other underlying software that runs together with instructions, program code, software elements, etc.

[0257] In at least some examples, the term “architecture” refers to computer architecture or network architecture. In at least some examples, the term “computer architecture” refers to the physical and logical design or arrangement of software and / or hardware elements in a computing system or platform, including technical standards for their interaction. In at least some examples, the term “network architecture” refers to the physical and logical design or arrangement of software and / or hardware elements in a network, including communication protocols, interfaces, and media transmissions.

[0258] In at least some examples, terms such as “appliance” and “computer appliance” refer to a computer device or computer system that has program code (e.g., software or firmware) specifically designed to provide a particular computing resource. In at least some examples, the term “virtual appliance” refers to a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or is dedicated to providing a particular computing resource. In at least some examples, terms such as “security appliance” and “firewall” refer to a computer appliance designed to protect a computer network from unwanted traffic and / or malicious attacks. In at least some examples, the term “policy appliance” refers to a technical control and logging mechanism for enforcing or coordinating policy rules (information usage rules) and ensuring accountability in an information system. In at least some examples, the term “gateway” refers to a network appliance that enables data to flow from one network to another, or a computing system or application configured to perform such a task. Examples of gateways include IP gateways, Internet-to-Orbit (I2O) gateways, IoT gateways, cloud storage gateways, etc.

[0259] In at least some examples, the term “User Equipment” or “UE” refers to a device with wireless communication capabilities and may describe a remote user of network resources within a communication network. The term “User Equipment” or “UE” may be considered synonymous with, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, station, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “User Equipment” or “UE” includes any type of wireless / wired device or any computing device including a wireless communication interface. Examples of UEs, client devices, etc., include desktop computers, workstations, laptop computers, mobile data terminals, smartphones, tablet computers, wearable devices, machine-to-machine (M2M) devices, machine-type communication (MTC) devices, Internet of Things (IoT) devices, embedded systems, sensors, autonomous vehicles, drones, robots, in-vehicle infotainment systems, instrument clusters, onboard diagnostic devices, dashboard mobile devices, electronic engine management systems, electronic / engine control units / modules, microcontrollers, control modules, server devices, network appliances, head-up display (HUD) devices, helmet-mounted display devices, augmented reality (AR) devices, virtual reality (VR) devices, mixed reality (MR) devices, and / or other similar systems or devices.In at least some examples, the term “station” or “STA” refers to a logical entity that is a single addressable instance of a medium access control (MAC) and physical layer (PHY) interface to a wireless medium (WM). In at least some examples, the term “wireless medium” or “WM” refers to a medium used to implement the transfer of protocol data units (PDUs) between peer physical layer (PHY) entities of a wireless local area network (LAN).

[0260] In at least some examples, the term “network element” refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless network services. The term “network element” may be considered synonymous with, and / or referred to as, networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, wireless network controllers, network access nodes (NANs), base stations, access points (APs), RAN devices, RAN nodes, gateways, servers, network appliances, network functions (NFs), virtualized NFs (VNFs), etc. In at least some examples, the term “network controller” refers to a functional block that centralizes some or all of the control and management functions of a network domain and can provide an abstract view of the network domain to other functional blocks via interfaces. In at least some examples, the term “network access node” or “NAN” refers to a network element in a radio access network (RAN) that is responsible for transmitting and receiving radio signals to and from a UE or station within one or more cells or coverage areas. A "Network Access Node" or "NAN" may have an integrated antenna or may be connected to an antenna array by a feeder cable. Furthermore, or alternatively, a "Network Access Node" or "NAN" may include dedicated digital signal processing, network function hardware, and / or computing hardware for operating as a computing node. In some examples, a "Network Access Node" or "NAN" may be divided into multiple functional blocks that operate in software for flexibility, cost, and performance.In some examples, “Network Access Node” or “NAN” may be a base station (e.g., evolved node B (eNB) or next-generation node B (gNB)), access point and / or wireless network access point, router, switch, hub, radio unit or remote radio head, TRP, gateway device (e.g., residential gateway, wireline 5G access network, wireline 5G cable access network, wireline BBF access network, etc.), network appliance, and / or any other network access hardware. In at least some examples, the term “Access Point” or “AP” refers to an entity that includes a station (STA) and provides access to distribution services via a wireless medium (WM) for the associated STA. The AP includes the STA and a distribution system access function (DSAF).

[0261] In at least some examples, the term “cell” refers to a radio network object that can be uniquely identified by a UE from an identifier (e.g., cell ID) broadcast from a network access node (NAN) across a geographical area. Furthermore, or alternatively, in at least some examples, the term “cell” refers to the geographical area covered by the NAN. In at least some examples, the term “serving cell” refers to a primary cell (PCell) for a UE that is in connected mode or state (e.g., RRC_CONNECTED) and is not configured with carrier aggregation (CA) and / or dual connectivity (DC). Furthermore, or alternatively, in at least some examples, the term “serving cell” refers to a set of cells that is in connected mode or state (e.g., RRC_CONNECTED) and is configured with CA, including zero or more special cells and one or more secondary cells. In at least some examples, the term “primary cell” or “PCell” refers to a Master Cell Group (MCG) cell operating on the primary frequency from which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. In at least some examples, the term “secondary cell” or “SCell” refers to a cell that provides additional radio resources on top of a special cell (SpCell) for a UE configured in a CA. In at least some examples, the term “special cell” or “SpCell” refers to a PCell for non-DC operation, or a PCell for an MCG or a PSCell for an SCG for DC operation. In at least some examples, the term “master cell group” or “MCG” refers to a group of serving cells associated with a “master node” that includes SpCells (PCells) and one or more SCells of any choice.In at least some examples, the term “secondary cell group” or “SCG” refers to a subset of serving cells, including a primary SCell (PSCell, Primary SCell) for a UE configured in a DC, and zero or more optional SCells. The term “primary SCG cell” refers to an SCG cell on which a UE performs random access when performing a reconfiguration with a synchronization procedure for DC operation. In at least some examples, the term “handover” refers to the transfer of a user’s connection from one radio channel to another radio channel (which may be the same cell or a different cell). Furthermore, or alternatively, in at least some examples, the term “handover” refers to the process by which a radio access network changes the radio transmitter, radio access mode, and / or radio system used to provide bearer services, while maintaining a defined bearer service QoS.

[0262] In at least some examples, the term “master node” or “MN” refers to a NAN that provides control plane connectivity to the core network. In at least some examples, the term “secondary node” or “SN” refers to a NAN that provides resources to the UE in addition to the resources provided by the MN, and / or a NAN that does not have control plane connectivity to the core network. In at least some examples, the terms “E-UTEAN node B,” “eNodeB,” or “eNB” refer to a RAN node that provides E-UTRA user plane (e.g., PDCP, RLC, MAC, PHY) and control plane (e.g., RRC) protocol termination to the UE and is connected to the Evolved Packet Core (EPC) via the S1 interface. Two or more eNBs are interconnected with each other (and / or with one or more en-gNBs) via the X2 interface. In at least some examples, the term “next-generation eNB” or “ng-eNB” refers to a RAN node that provides E-UTRA user plane and control plane protocol termination to the UE and is connected to the 5GC via the NG interface. Two or more ng-eNBs are interconnected with each other (and / or with one or more gNBs) via an Xn interface. In at least some examples, the terms “next-generation node B,” “gNodeB,” or “gNB” refer to a RAN node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC via an NG interface. In some examples, two or more gNBs are interconnected with each other (and / or with one or more ng-eNBs) via an Xn interface. In at least some examples, the terms “E-UTRA-NR gNB” or “en-gNB” refer to a RAN node that provides NR user plane and control plane protocol termination to the UE and functions as a secondary node in an E-UTRA-NR Dual Connectivity (EN-DC) scenario (see, for example, 3GPP TS 37.340 v17.0.0 (2022-04-15) ("[TS37340]")).Two or more en-gNBs are interconnected with each other (and / or with one or more eNBs) via an X2 interface. In at least some examples, the terms “next-generation RAN node” or “NG-RAN node” refer to either a gNB or an ng-eNB. In at least some examples, the term “IAB node” refers to a RAN node that supports new radio (NR) access links to user equipment (UE) and NR backhaul links to parent and child nodes. In at least some examples, the term “IAB donor” refers to a RAN node (e.g., a gNB) that provides network access to the UE via a network of backhaul and access links. In at least some examples, the term “Central Unit” or “CU” refers to a logical node that hosts the radio resource control (RRC), Service Data Adaptation Protocol (SDAP), and / or Packet Data Convergence Protocol (PDCP) protocols / layers of an NG-RAN node, or the RRC and PDCP protocols of an en-gNB that controls the operation of one or more DUs, and the CU terminates an F1 interface connected to a DU and may be connected to multiple DUs. In at least some examples, the term “distributed unit” or “DU” refers to a logical node that hosts the Backhaul Adaptation Protocol (BAP), F1 Application Protocol (F1AP), Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY) layer of an NG-RAN node or en-gNB, whose operation is partially controlled by a CU, where a single DU supports one or more cells, and a single cell is supported by only one DU, and the DU terminates the F1 interface connected to the CU.In at least some examples, the term “radio unit” or “RU” refers to a logical node that hosts the PHY layer or low PHY layer and radio frequency (RF) processing based on lower-layer functional partitioning. In at least some examples, the term “partitioned architecture” refers to an architecture in which the CU, DU, and / or RU are physically separated from each other. Furthermore, or alternatively, in at least some examples, the term “partitioned architecture” refers to a RAN architecture such as those discussed in 3GPP TS 38.401 v17.3.0 (2023-01-06) and / or 3GPP TS 38.410 v17.1.0 (2022-06-23), all of which are incorporated herein by reference. In at least some examples, the term “integrated architecture” refers to an architecture in which the RU and DU are implemented on a single platform, and / or an architecture in which the DU and CU are implemented on a single platform.

[0263] In at least some examples, the term “transmit / receive point” or “TRP” refers to a set of geographically identical antennas (e.g., an antenna array with one or more antenna elements) that support transmit point (TP) and / or receive point (RP) functions. In at least some examples, the term “transmit point” or “TP” refers to a set of geographically identical transmit antennas (e.g., an antenna array with one or more antenna elements) for an individual cell, a portion of an individual cell, or a dedicated DL-PRS TP. In some examples, a TP may include antennas of a base station (eNB, gNB, ng-eNB, etc.), a remote radio head, a base station's remote antenna, an antenna of a dedicated PRS TP, etc. In some examples, a single cell may be formed by or include one or more TPs. In some examples, each TP may correspond to a single cell for homogeneous deployment. In at least some examples, the term “PRS-only TP” refers to a TP that transmits only PRS or DL-PRS (positioning) signals (e.g., for a PRS-based terrestrial beacon system (TBS)) and is not associated with a cell. In at least some examples, the term “receiving point” or “RP” refers to a set of geographically identical receiving antennas (e.g., an antenna array with one or more antenna elements) for an individual cell, a portion of an individual cell, or an individual UL-SRS-only RP. In some examples, an RP may include a base station (ng-eNB or gNB) antenna, a remote radio head, a base station's remote antenna, an antenna for a UL-SRS-only RP, etc. In some examples, a single cell may contain one or more RPs. In some examples, each RP may correspond to a single cell for homogeneous deployment. In at least some examples, the term “SRS-only RP” refers to an RP that receives only UL-SRS signals and is not associated with a cell.

[0264] In at least some examples, the term “Residential Gateway” or “RG” refers to a device that provides, for example, voice, data, broadcast video, and video on demand to other devices within the customer’s premises. In at least some examples, the term “Wireline 5G Access Network” or “W-5GAN” refers to a wireline AN that connects to 5GC via N2 and N3 reference points. W-5GAN can be either W-5GBAN or W-5GCAN. In at least some examples, the term “Wireline 5G Cable Access Network” or “W-5GCAN” refers to an access network as defined by CableLabs. In at least some examples, the term “Wireline BBF Access Network” or “W-5GBAN” refers to an access network as defined by the Broadband Forum (BBF). In at least some examples, the term “Wireline Access Gateway Function” or “W-AGF” refers to a network function in W-5GAN that provides connectivity to the 3GPP 5G Core Network (5GC) to 5G-RG and / or FN-RG. In at least some examples, the term "5G-RG" refers to a 5GC-connectable RG that acts as a user device in relation to 5GC, supporting a secure element and exchanging N1 signaling with 5GC. 5G-RG can be either 5G-BRG or 5G-CRG.

[0265] The term "SMTC" refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. The term "SSB" refers to an SS / PBCH block.

[0266] The term "primary cell" refers to an MCG cell operating on the primary frequency on which a UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. The term "primary SCG cell" refers to an SCG cell on which a UE performs random access when performing a reconfiguration with a synchronization procedure for DC operation. The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured in CA. The term "secondary cell group" refers to a subset of serving cells, including a PSCell for a UE configured in DC and zero or more secondary cells. The term "serving cell" refers to a primary cell for a UE that is in RRC_CONNECTED and not configured in CA / DC, and there is only one serving cell consisting of a primary cell. The term "serving cell" or "serving cell" refers to a set of cells, including a special cell for a UE in the RRC_CONNECTED state configured in CA and all secondary cells. The term "special cell" refers to an MCG PCell or SCG PSCell for DC operation; otherwise, the term "special cell" refers to a PCell.

[0267] In at least some examples, the term “edge computing” refers to an implementation or configuration of distributed computing elements that move processing activities and resources (e.g., compute, store, accelerate, and / or network resources) toward the “edge” of the network in order to reduce latency and increase throughput for endpoint users (client devices, user equipment, etc.). Furthermore or alternatively, in at least some examples, the term “edge computing” refers to a set of services hosted relatively close to the access points of the client / UE connected to the network in order to achieve relatively efficient service delivery through reduced end-to-end latency and / or load on the transport network. In some examples, an implementation of edge computing involves providing services and / or resources in a cloud-like system, function, application, and subsystem from one or more locations accessible via a wireless network. Furthermore or alternatively, in at least some examples, the term “edge computing” refers to the concept described in [TS23501], which allows operator and third-party services to be hosted near the access points of the UE connected to the network in order to achieve efficient service delivery through reduced end-to-end latency and load on the transport network. In at least some examples, the terms “edge compute node” or “edge compute device” refer to an identifiable entity that implements a mode of edge computing operation, whether it is part of a larger system, a distributed collection of systems, or a standalone device. In some examples, compute nodes may be called “edge nodes,” “edge devices,” or “edge systems,” whether they are acting as clients, servers, or intermediate entities.Furthermore, or alternatively, in at least some examples, the term “edge compute node” refers to a real-world, logical, or virtualized implementation of a computeable element in the form of a device, gateway, bridge, system, subsystem, or component, regardless of whether it operates in server, client, endpoint, or peer mode, and whether it is located at the “edge” of the network or at a more connected location within the network. However, references to “edge computing system” generally refer to a distributed architecture, organization, or collection of multiple nodes and devices organized to achieve or provide some form of service or resource in an edge computing configuration. In at least some examples, the term “edge computing platform” or “edge platform” refers to a set of functions used to instantiate, run, or operate edge applications on a particular edge compute node (e.g., virtualized infrastructure), enabling such edge applications to provide and / or consume edge services, and / or provide one or more edge services in other ways. In at least some examples, the term “edge application” or “edge app” refers to an application that can be instantiated or run on an edge compute node within an edge computing network, system, or framework, and that can potentially provide and / or consume edge computing services. In at least some examples, the term “edge services” refers to services provided by either the edge platform itself or / or edge applications, via edge compute nodes and / or the edge platform.

[0268] In at least some examples, the terms “cloud computing” or “cloud” refer to a paradigm for enabling network access to a scalable and flexible pool of shareable computing resources without active management by the user, using on-demand self-service provisioning and management. Cloud computing provides cloud computing services (or cloud services), and a cloud computing service is one or more capabilities delivered via cloud computing that are invoked using a defined interface (e.g., an API).

[0269] In at least some examples, the term “Network Function” or “NF” refers to a functional block within a network infrastructure having one or more external interfaces and defined functional behaviors. In at least some examples, the term “Network Service” or “NS” refers to a configuration or set of NFs and / or network services defined by the specifications of their functions and behaviors. In at least some examples, the term “RAN Function” or “RANF” refers to a functional block within a RAN architecture having one or more external interfaces and defined behaviors relating to the operation of the RAN or RAN node. Further or alternatively, in at least some examples, the term “RAN Function” or “RANF” refers to a set of functions and / or NFs that are part of the RAN. In at least some examples, the term “Application Function” or “AF” refers to an element or entity that interacts with the 3GPP core network to provide services. Further or alternatively, in at least some examples, the term “Application Function” or “AF” refers to an edge compute node or ECT framework from the perspective of a 5G core network. In at least some examples, the term “Management Function” refers to a logical entity that acts as a service consumer and / or service producer. In at least some examples, the term “Management Service” refers to a set of management capabilities provided. In at least some examples, the term “Network Function Virtualization” or “NFV” refers to the principle of separating network functions from the hardware on which they operate by using virtualization techniques and / or virtualization technologies. In at least some examples, the term “Virtualized Network Function” or “VNF” refers to an implementation of NF that can be deployed on Network Function Virtualisation Infrastructure (NFVI).In at least some examples, the term “Network Functions Virtualization Infrastructure Manager” or “NFVI” refers to the entire set of hardware and software components that make up the environment in which a VNF is deployed. In at least some examples, the term “Virtualization Infrastructure Manager” or “VIM” refers to a functional block typically responsible for controlling and managing NFVI compute, storage, and network resources within an infrastructure domain of a single operator. In at least some examples, the terms “Virtualization Container,” “Execution Container,” or “Container” refer to a partition of compute nodes that provides an isolated virtualized compute environment. In at least some examples, the term “OS Container” refers to a virtualization container that utilizes the shared operating system (OS) kernel of its host, where the host providing the shared OS kernel can be a physical compute node or another virtualization container. Furthermore, or alternatively, in at least some examples, the term “Container” refers to a standard unit of software (or package) containing code and its associated dependencies, and / or an abstraction in the application layer that packages the code and dependencies together. Furthermore, or alternatively, in at least some examples, the term “container” or “container image” refers to a lightweight, standalone executable software package that includes everything necessary to run an application, such as code, runtime environment, system tools, system libraries, and configuration. In at least some examples, the term “virtual machine” or “VM” refers to a virtualized computing environment that operates identically to or in a broadcast manner to a physical computer and / or server. In at least some examples, the term “hypervisor” refers to a software element that partitions the underlying physical resources of computing nodes, creates VMs, manages resources for VMs, and isolates individual VMs from one another.

[0270] In at least some examples, the term “data network” or “DN” refers to a network that hosts data-centric services, such as operator services, the Internet, third-party services, or enterprise networks. Furthermore, or alternatively, in at least some examples, a DN refers to a service network belonging to an operator or a third party, provided as a service to client or user equipment (UE). A DN is sometimes referred to as a “packet data network” or “PDN.” In at least some examples, the term “local area data network” or “LADN” refers to a DN that is accessible by the UE only at specific locations, provides connectivity to a particular DNN, and whose availability is provided to the UE.

[0271] In at least some instances, the term “Internet of Things” or “IoT” refers to a system of interconnected computing devices, machines, and digital machines capable of transferring data with little or no human interaction, and may be associated with technologies such as real-time analytics, machine learning and / or AI, embedded systems, wireless sensor networks, control systems, and automation (e.g., smart home, smart building, and / or smart city technologies). IoT devices are typically low-power devices with little computing or memory capacity.

[0272] In at least some examples, the term “protocol” refers to a set of predetermined procedures or methods for performing one or more actions. Furthermore, or alternatively, in at least some examples, the term “protocol” refers to a common means (sometimes called an interface) for unrelated objects to communicate with one another. In at least some examples, the term “communication protocol” refers to a set of standardized rules or instructions implemented by a communication device and / or system to communicate with other devices and / or systems, including instructions for packetizing / depacketing data, instructions for modulating / demodulating signals, and implementations of protocol stacks. In various implementations, “protocol” and / or “communication protocol” may be represented using a protocol stack, a finite state machine (FSM), and / or any other suitable data structure. In at least some examples, the term “standard protocol” refers to a protocol whose specifications are published, known to the public, and controlled by a standards body. In at least some examples, the term “protocol stack” or “network stack” refers to an implementation of a protocol suite or family of protocols. In various implementations, a protocol stack includes a set of protocol layers, where the lowest-level protocol handles low-level interactions with hardware and / or communication interfaces, and each higher layer adds further capabilities. Furthermore, or alternatively, in at least some examples, the term “protocol” refers to a formal set of procedures employed to ensure communication between two or more functions within the same layer of a functionality hierarchy.

[0273] In at least some examples, the term “application layer” refers to an abstraction layer that specifies the shared communication protocols and interfaces used by hosts within a communication network. More or alternatively, in at least some examples, the term “application layer” refers to an abstraction layer that interacts with software applications that implement communication components, including identifying communication partners, determining resource availability, and synchronizing communications. Examples of application layer protocols include HTTP, HTTPS, File Transfer Protocol (FTP), Dynamic Host Configuration Protocol (DHCP), Internet Message Access Protocol (IMAP), Lightweight Directory Access Protocol (LDAP), MQTT (MQ Telemetry Transport), Remote Authentication Dial-In User Service (RADIUS), Diameter Protocol, Extensible Authentication Protocol (EAP), RDMA over Converged Ethernet version 2 (RoCEv2), Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP), Real Time Streaming Protocol (RTSP), SBMV Protocol, Skinny Client Control Protocol (SCCP), Session Initiation Protocol (SIP), Session Description Protocol (SDP,This includes protocols such as Session Description Protocol, Simple Mail Transfer Protocol (SMTP), Simple Network Management Protocol (SNMP), Simple Service Discovery Protocol (SSDP), Small Computer System Interface (SCSI), Internet SCSI (iSCSI), iSCSI Extensions for RDMA (iSER), Transport Layer Security (TLS), Voice over IP (VoIP), Virtual Private Network (VPN), and Extensible Messaging and Presence Protocol (XMPP).

[0274] In at least some examples, the term “session layer” refers to an abstraction layer that controls the interactions and / or connections between entities or elements, and may include establishing, managing, and terminating connections between entities or elements.

[0275] In at least some examples, the term “transport layer” refers to the protocol layer that provides end-to-end (e2e) communication services such as connectivity-oriented communication, reliability, flow control, and multiplexing. Examples of transport layer protocols include datagram congestion control protocol (DCCP), fiber channel protocol (FBC), generic routing encapsulation (GRE), GPRS tunneling (GTP), micro transport protocol (μTP), multipath TCP (MPTCP), multipath QUIC (MPQUIC), multipath UDP (MPUDP), quick UDP Internet Connections (QUIC), remote direct memory access (RDMA), resource reservation protocol (RSVP), stream control transmission protocol (SCTP), transmission control protocol (TCP), and user datagram protocol (UDP).

[0276] In at least some examples, the term “network layer” refers to a protocol layer that includes means for forwarding network packets from source to destination across one or more networks. Furthermore, or alternatively, in at least some examples, the term “network layer” refers to a protocol layer responsible for packet forwarding and / or routing through intermediate nodes. Furthermore, or alternatively, in at least some examples, the term “network layer” or “Internet layer” refers to a protocol layer that includes interworking methods, protocols, and specifications used to forward network packets between networks. Examples of network layer protocols include the Internet Protocol (IP), IP Security (IPsec), Internet Control Message Protocol (ICMP), Internet Group Management Protocol (IGMP), Open Shortest Path First Protocol (OSPF), Routing Information Protocol (RIP), RDMA over Converged Ethernet version 2 (RoCEv2), Subnetwork Access Protocol (SNAP), and / or several other Internet or network protocol layers.

[0277] In at least some examples, the terms “link layer” or “data link layer” refer to the protocol layer that transfers data between nodes on a network segment across the physical layers. Examples of link layer protocols include logical link control (LLC), medium access control (MAC), Ethernet®, and RDMA over Converged Ethernet version 1 (RoCEv1).

[0278] In at least some examples, the terms “Radio Resource Control,” “RRC Layer,” or “RRC” refer to a protocol layer or sublayer that performs system information handling, paging, establishment, maintenance, and release of RRC connections, security functions, establishment, configuration, maintenance, and release of signaling radio bearers (SRBs) and data radio bearers (DRBs), mobility functions / services, QoS management, and several sidelink-specific services and functions on the Uu interface (see, for example, 3GPP TS 36.331 v17.4.0 (2023-03-30) ("TS36331") and / or 3GPP TS 38.331 v17.4.0 (2023-03-30) ("TS38331")).

[0279] In at least some examples, the terms “Service Data Adaptive Protocol,” “SDAP Layer,” or “SDAP” refer to a protocol layer or sublayer that performs mapping between QoS flows and data radio bearers (DRBs) and marks QoS flow IDs (QFIs) in both DL and UL packets (see, for example, 3GPP TS 37.324 v17.0.0 (2022-04-13) (see "[TS37324]").

[0280] In at least some examples, the terms “Packet Data Convergence Protocol,” “PDCP Layer,” or “PDCP” refer to a protocol layer or sublayer that performs the forwarding of user plane data or control plane data, maintains PDCP sequence numbers (SN), performs header compression and decompression using the Robust Header Compression (ROHC) protocol and / or the Ethernet Header Compression (EHC) protocol, performs encryption and decryption, performs integrity protection and integrity verification, performs timer-based SDU discarding, performs routing for split bearers, performs replication and replication discarding, performs sorting and sequential distribution, and / or out-of-order distribution (see, for example, 3GPP TS 36.323 v17.2.0 (2023-01-13) and / or 3GPP TS 38.323 v17.4.0 (2023-03-28) ("[TS38323]")).

[0281] In at least some examples, the terms “Radio Link Control Layer,” “RLC Layer,” or “RLC” refer to a protocol layer or sublayer that performs forwarding of upper-layer PDUs, sequence numbering independent of that in PDCP, error correction via ARQ, segmentation and / or resegmentation of RLC SDUs, reassembly of SDUs, duplicate detection, RLC SDU discarding, RLC re-establishment, and / or protocol error detection (see, for example, 3GPP TS 36.322 v17.0.0 (2022-04-15) and 3GPP TS 38.322 v17.2.0 (2023-01-13) ("TS38322")).

[0282] In at least some examples, the terms “Medium Access Control Protocol,” “MAC Protocol,” or “MAC” refer to a protocol that manages access to a transmission medium in a network to enable the exchange of data between stations in the network. Furthermore, or alternatively, in at least some examples, the terms “Medium Access Control Layer,” “MAC Layer,” or “MAC” refer to a protocol layer or sublayer that performs functions to provide frame-based connectionless mode (e.g., datagram style) data transfer between stations or devices. Furthermore, or alternatively, in at least some examples, the terms “Media Access Control Layer,” “MAC Layer,” or “MAC” refer to a protocol layer or sublayer that performs mapping between logical channels and transport channels, multiplexing / demultiplexing MAC SDUs belonging to one or different logical channels to / from transport blocks (TBs) delivered to / from the physical layer on the transport channel, scheduling information reporting, error correction through HARQ (one HARQ entity per cell in the case of CA), priority processing between UEs by dynamic scheduling, priority processing between logical channels of a single UE by logical channel prioritization, priority processing between duplicate resources of a single UE, and / or padding (see, for example, 3GPP TS 36.321 v17.3.0 (2023-01-13) and 3GPP TS 38.321 v17.4.0 (2023-03-29) ("[TS38321]")).

[0283] In at least some examples, the terms “physical layer,” “PHY layer,” or “PHY” refer to a protocol layer or sublayer that includes the capability to transmit and receive modulated signals for communication in a communication network (see, for example, 3GPP TS 36.201 v17.0.0 (2022-03-31) and 3GPP TS 38.201 v17.0.0 (2022-01-05) ("TS38201")).

[0284] In at least some examples, the term “access technology” refers to the technology used for the underlying physical connection to a communication network. In at least some examples, the term “wireless access technology” or “RAT” refers to the technology used for the underlying physical connection to a wireless-based communication network. In at least some examples, the term “wireless technology” refers to the technology for wireless transmission and / or reception of electromagnetic radiation for information transfer. In at least some examples, the term “RAT type” may identify the transmission technology and / or communication protocol used in the access network. Examples of access technologies include wireless access technologies / RAT, wired, wired cables, wireline broadband forum (wireline-BBF), Ethernet® (e.g., IEEE Standard for Ethernet, IEEE Std 802.3-2018 (31 Aug. 2018)) (see "[IEEE8023]") and its variations, optical fiber networks (e.g., ITU-T G.651, ITU-T G.652, Optical Transport Network (OTN), Synchronous optical networking (SONET), and synchronous digital hierarchy (SDH), etc.), digital subscriber line (DSL) and its variations, Data Over Cable Service Interface Specification (DOCSIS) technology, and hybrid fiber-coaxial (HFC) technology. Examples of RAT (or RAT type) and / or communication protocols include Advanced Mobile Phone System (AMPS) technology (e.g., Digital AMPS (D-AMPS), Total Access Communication System (TACS)).This includes technologies such as Total Access Communication System (TACS) and its variations like Extended TACS (ETACS), Global System for Mobile Communications (GSM) technologies (e.g., Circuit Switched Data (CSD), High-Speed ​​CSD (HSCSD), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE)), Third Generation Partnership Project (3GPP) technologies (e.g., Universal Mobile Telecommunications System (UMTS) and its variations (e.g., UMTS Terrestrial Radio Access (UTRA), Wideband Code Division Multiple Access (W-CDMA), Freedom of Multimedia Access (FOMA), Time Division-Code Division Multiple Access (TD-CDMA), and Time Division-Synchronized Code Division Multiple Access (TD-SCDMA)). Division (Synchronous Code Division Multiple Access), etc.), Generic Access Network (GAN) / Unlicensed Mobile Access (UMA), High Speed ​​Packet Access (HSPA) and its variations (e.g., HSPA+), Long Term Evolution (LTE) and its variations (e.g., LTE-A,LTE-Advanced, Evolved UTRA (E-UTRA), LTE Extra, LTE-A Pro, LTE LAA, MuLTEfire, etc.), 5th Generation (5G) or New Radio (NR), Narrowband IoT (NB-IoT), 3GPP Proximity Services (ProSe), etc.), ETSI RAT (e.g., High Performance Radio Metropolitan Area Network (HiperMAN), Intelligent Transport Systems (ITS) (e.g., ITS-G5, ITS-G5B, ITS-G5C, etc.), Institute of Electrical and Electronics Engineers (IEEE) technologies and / or WiFi (e.g., IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture, IEEE Std 802-2014, pp.1-74 (30 Jun.2014) ("[IEEE802]"), IEEE Standard for Information Technology--Telecommunications and Information Exchange between Systems - Local and Metropolitan Area Networks--Specific Requirements - Part 11: Wireless LAN Medium Access Control(MAC) and Physical Layer(PHY) Specifications, IEEE Std 802.11-2020, pp.1-4379(26 Feb.2021)(``[IEEE80211]''), IEEE802.15 technology (e.g., IEEE Standard for Low-Rate Wireless Networks, IEEE Std 802.15.4-2020,pp.1-800 (23 July 2020) ("[IEEE802154]") and its variations (e.g., ZigBee, WirelessHART, MiWi, ISA100.11a, Thread, 6LoWPAN (IPv6 over Low power WPAN), etc.), IEEE Standard for Local and metropolitan area networks - Part 15.6: Wireless Body Area Networks, IEEE Std 802.15.6-2012, pp. 1-271 (29 Feb.2012), etc.), WLAN V2X RAT (e.g., IEEE Standard for Information technology--Local and metropolitan area networks--Specific requirements--Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 6: Wireless Access in Vehicular Environments, IEEE Std 802.11p-2010, pp.1-51 (15 July) 2010) ("[IEEE80211p]") (currently part of [IEEE80211]), IEEE Guide for Wireless Access in Vehicular Environments (WAVE) Architecture, IEEE STANDARDS ASSOCIATION, IEEE 1609.0-2019 (10 Apr. 2019) ("[IEEE16090]"), IEEE802.11bd, DSRC (Dedicated Short Range Communications), etc.), WiMAX (Worldwide Interoperability for Microwave Access) (for example, IEEE Standard for Air Interface for Broadband Wireless Access Systems, IEEE Std 802.16-2017,pp.1-2726 (02 Mar.2018) ("[WiMAX]"), MBWA (Mobile Broadband Wireless Access) / iBurst (e.g., IEEE802.20 and its variations), WiGig (Wireless Gigabit Alliance) standards (e.g., IEEE802.11ad, IEEE802.11ay, etc.), iDEN (Integrated Digital Enhanced Network) and its variations (e.g., WiDEN (Wideband Integrated Digital Enhanced Network)), millimeter wave (mmWave) technology / standards (e.g., wireless systems operating on 10-300GHz and 3GPP 5G), short-range and / or wireless personal area network (WPAN) technology / standards (e.g., IEEE802.15 technology (e.g., the aforementioned)), Bluetooth® and its variations (e.g., Bluetooth 5.3, LBE (Bluetooth Low Energy)). Energy) etc.), WiFi-Direct, Miracast, ANT / ANT+, Z-Wave, Universal Plug and Play (UPnP), Low Power Wide Area Network (LPWAN), Long Range Wide Area Network (LoRA or LoRaWAN) etc.), Optical and / or Visible Light Communication (VLC) technologies / standards (e.g., IEEE Standard for Local and metropolitan area networks - Part 15.7: Short-Range Optical Wireless Communications, IEEE Std 802.15.7-2018,pp.1-407 (23 Apr. 2019), etc.), Sigfox, Mobitex, 3GPP2 technologies (e.g., cdmaOne (2G), CDMA2000 (Code Division Multiple Access 2000), and EVDO (Evolution-Data Optimized or Evolution-Data Only), PTT (Push-to-talk), MTS (Mobile Telephone System) and its variations (e.g., IMTS (Improved MTS), AMTS (Advanced MTS), etc.), Personal Digital Cellular (PDC), Personal Handy-phone System (PHS), Cellular Digital Packet Data (CDPD), DataTAC, DECT (Digital Enhanced Cordless Telecommunications) and its variations (e.g., DECT ULE (DECT Ultra Low) This includes RATs or protocols such as Energy, DECT-2020, DECT-5G, UHF (Ultra High Frequency) communications, VHF (Very High Frequency) communications, and / or any other suitable RATs or protocols. In addition to the above RATs / standards, any number of satellite uplink technologies, including, for example, radios conforming to standards issued by the International Telecommunication Union (ITU) or ETSI, may be used for the purposes of this disclosure. Therefore, the examples provided herein are understood to be applicable to a variety of other communication technologies, both existing and yet to be devised.

[0285] In at least some examples, the term “channel” refers to a tangible or intangible transmission medium used to communicate data or data streams. The term “channel” may also be synonymous and / or equivalent to any other similar term that indicates a path or medium through which data is communicated, such as “communication channel,” “data communication channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radio frequency carrier,” and / or other similar terms. Furthermore, in at least some examples, the term “link” refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0286] In at least some examples, the term “carrier” refers to the modulated waveform carrying one or more physical channels (e.g., 5G / NR, E-UTRA, UTRA, and / or GSM / EDGE physical channels). In at least some examples, the term “carrier frequency” refers to the center frequency of a cell.

[0287] In at least some examples, the term "bearer" refers to an information transmission path with defined capacity, latency, bit error rate, etc. In at least some examples, the term "wireless bearer" refers to a service provided by Layer 2 (L2) for the transfer of user data between user equipment (UE) and radio access network (RAN). In at least some examples, the term "wireless access bearer" refers to a service provided by the access layer to the non-access layer for the transfer of user data between the UE and CN.

[0288] In at least some examples, the terms “beamforming” and “beam steering” refer to a spatial filtering mechanism used in a transmitter (Tx) to improve the received signal power, signal-to-noise ratio (SNR), or any other signaling metric at the intended receiver (Rx). In at least some examples, the term “beamformer” refers to an STA that transmits a physical layer PDU (PPDU) using a beamforming steering matrix. In at least some examples, the term “beamforming steering matrix” refers to a matrix determined using knowledge of the channel between Tx and the intended Rx, mapping from a spatiotemporal stream to a transmitting antenna, with the aim of improving the signal power, SNR, and / or any other signaling metric at the intended Rx.

[0289] In at least some examples, the term "subframe" refers to a time interval in which a signal is signaled. In some implementations, a subframe is equal to 1 millisecond (ms). In at least some examples, the term "time slot" refers to an integer multiple of consecutive subframes. In at least some examples, the term "superframe" refers to a time interval containing two time slots.

[0290] In at least some examples, the term “channel coding” refers to a process and / or technique for adding redundancy to messages or packets to make them more robust to noise, channel interference, limited channel bandwidth and / or other errors. For the purposes of this disclosure, the term “channel coding” may be used interchangeably with the terms “forward error correction” or “FEC,” “error correction coding,” “error correction code” or “ECC,” and / or “network coding” or “NC.” In at least some examples, the term “network coding” refers to a process and / or technique in which transmitted data is encoded and decoded to improve network performance. In at least some examples, the term “code rate” refers to the percentage of a data stream or flow that is useful or non-redundant (for example, for a code rate of k / n, for every k bits of useful information, the (en)coder generates a total of n bits of data, of which nk bits are redundant). In at least some examples, the term “systematic code” refers to any error correction code embedded in the encoded output of the input data. In at least some examples, the term “non-systematic code” refers to any error correction code in which input data is not embedded in the encoded output. In at least some examples, the term “interleaving” refers to the process of rearranging code symbols to spread a burst of errors across multiple codewords that can be corrected by ECC. In at least some examples, the term “codeword” or “codeword” refers to an element of a code or protocol that is assembled according to specific rules of the code or protocol.

[0291] In at least some examples, the term “network address” refers to an identifier for a node or host within a computer network, which may be a unique identifier between networks and / or unique to a locally managed portion of the network. Examples of identifiers and / or network addresses include application identifiers, Bluetooth hardware device addresses (BD_ADDR), cellular network addresses (e.g., Absolute Radio-Frequency Channel Number (ARFCN)), access point names (APN), AMF names and / or AMF identifiers (ID), AF service identifiers, cell global identifiers (CGI) (e.g., NCGI (NR CGI), CGI NG-RAN, CGI EUTRA, etc.), closed access group identifiers (CAG-ID), edge application server (EAS) IDs, data network access identifiers (DNAI), data network names (DNN), evolved cell global identifiers (ECGI), EPS bearer identities (EBI), and equipment identity registers (EIR). Register) and / or 5G-EIR, Extended Unique Identifier (EUI), Group ID for Network Selection (GIN), Generic Public Subscription Identifier (GPSI), Global Unique AMF Identifier (GUAMI,Globally Unique AMF Identifier, Globally Unique Temporary Identifier (GUTI) and / or 5G-GUTI, gNB Identifier (gNB ID), Global gNB ID, International Mobile Equipment Identity (IMEI), IMEI Type Allocation Code (IMEA / TAC), International Mobile Subscriber Identity (IMSI), IMSI software version (IMSISV), Permanent Equipment Identifier (PEI), Local Area Data Network (LADN) DNN, Local NG-RAN Node Identifier, Mobile Subscriber Identification Number (MSIN), Mobile Subscriber / Station ISDN Number (MSISDN), Network Identifier (NID), Network Slice Instance (NSI) ID, Network Slice AS Group (NSAG) Group), Permanent Equipment Identifier (PEI), Public Land Mobile Network (PLMN) Identity (ID), Physical Cell Identifier (PCI), QoS Flow Identifier (QFI), and / or 5G QoS Identifier (5QI), RAN ID, Routing Indicator, Radio Network Temporary Identifier (RNTI),Radio Network Temporary Identifier) ​​and its variations (e.g., any of those discussed in Section 8 of 3GPP TS 38.300 v17.4.0 (2023-03-28)) ("[TS38300]"), SMS Function (SMSF) ID, Stand-alone Non-Public Network (SNPN) ID, Single Network Slice Selection Assistance information (S-NSSAI), Sidelink Identifier (e.g., Source Layer 2 ID, Destination Layer 2 ID, PC5 Link Identifier, etc.), Subscription Concealed Identifier (SUCI), Subscription Permanent Identifier (SUPI), Temporary Mobile Subscriber Identity (TMSI) and its variations, Tracking Area Identity (TAI) Identity, UE Access Category and Identity, and / or other cellular network-related identifiers), CAG-ID, Driver's License Number, Global Trade Item Number (GTIN) (e.g., Australian Product Number (APN), EPC, European Article Number (EAN), Universal Product Code (UPC), etc.), Email Address, Enterprise Application Server (EAS), Endpoint, Address as defined by the EPCglobal Tag Data Standard, Electronic Product Code (EPC), Fully Qualified Domain Name (FQDN),Fully Qualified Domain Name), Flow ID and / or Flow Hash, Hash Value, Index, Internet Protocol (IP) address within an IP network (e.g., IP version 4 (IPv4), IP version 6 (IPv6, etc.), Internet Packet Exchange (IPX) address, LAN ID, MAC address, Personal Area Network (PAN) ID, Port Number (e.g., TCP port number, UDP port number, etc.), Price Lookup Code (PLC), Product Key, QUIC Connection ID, RFID Tag, Sequence Number, Service Set Identifier (SSID) and its variations, Screen Name, Serial Number, Stock Keeping Unit (SKU), Socket Address, Social Security Number (SSN), Telephone Number (e.g., in a Public Switched Telephone Network (PTSN)), Unique Identifier (UID) (e.g., Global UID, Universally Unique Identifier (UUID)) Identifiers (e.g., those specified in ISO / IEC 11578:1996), Universal Resource Locator (URL) and / or Universal Resource Identifier (URI), Username (e.g., ID for logging into a service provider platform such as a social network and / or some other service), Vehicle Identification Number (VIN), Virtual LAN (VLAN),This may include a Virtual LAN ID, X.21 address, X.25 address, Zigbee® ID, Zigbee® device network ID, and / or any other appropriate network address and its components.

[0292] In the context of computer networks, the term “port” in at least some examples refers to a communication endpoint, a virtual data connection between two or more entities, and / or a virtual point where a network connection begins and ends. Furthermore, or alternatively, in at least some examples, “port” is associated with a particular process or service. Furthermore, or alternatively, in at least some examples, the term “port” refers to a particular interface of a designated device (or apparatus) that has an electromagnetic environment (for example, any connection point on that device intended for cable connections to or from the device can be considered a port).

[0293] In at least some examples, the term “delay” refers to the time interval between two events. Furthermore, or alternatively, in at least some examples, the term “delay” refers to the time interval between the propagation of a signal and its reception. In at least some examples, the term “delay limit” refers to a predetermined or configured amount of acceptable delay. In at least some examples, the term “packet delay limit” refers to a predetermined or configured amount of acceptable packet delay within which packets that are not processed and / or transmitted are considered delivery failures and are discarded or dropped. In at least some examples, the term “good put” refers to the number of useful information bits delivered by the network to a particular destination per unit time. In at least some examples, the term “jitter” refers to the deviation of an estimated periodic signal from a predetermined ("true") period relative to a reference clock signal. In at least some examples, the term “latency” refers to the amount of time required to transfer the first / initial data unit in a data burst from one point to another. Furthermore, or alternatively, in at least some examples, the term “latency” refers to the delay experienced by a data unit (e.g., a frame) during its propagation between two points in a network, measured from the time it takes for a known reference point in a frame to pass a first point to the time it takes for a reference point in a data unit to pass a second point. In at least some examples, the term “network delay” refers to the delay of a data unit in a network (e.g., an IP packet in an IP network). In at least some examples, the term “packet delay” refers to the time required to forward any packet from one point to another. Furthermore, or alternatively, in at least some examples, the term “packet delay” or “packet delay” refers to the difference between the packet reception time and the packet transmission time. Furthermore, or alternatively, “packet delay” or “packet delay” can be measured by subtracting the packet transmission time from the packet reception time, provided that the transmitter and receiver are at least somewhat synchronized.In at least some examples, the term “packet drop rate” refers to the percentage of packets that were not sent to the target due to high traffic load or traffic management, and should be considered part of the packet loss rate. In at least some examples, the term “packet loss rate” refers to the percentage of packets that were not received by the target, including dropped packets, packets lost in transmission, and packets received in an incorrect format. In at least some examples, the term “performance indicator” refers to aggregated performance data across a group of network functions (NFs), derived from performance measurements collected in the NFs belonging to the group, according to the aggregation method identified in the performance indicator definition. In at least some examples, the term “physical rate” or “PHY rate” refers to the speed at which one or more bits are actually transmitted on the transmission medium. Furthermore, or alternatively, in at least some examples, the term “physical rate” or “PHY rate” refers to the speed at which data can travel between the wireless link between the transmitter and receiver. In at least some examples, the term “processing delay” refers to the amount of time required for a network node to process a packet. In at least some examples, the term “propagation delay” refers to the amount of time required for the signal header to travel from the transmitter to the receiver. In at least some examples, the term “queuing delay” refers to the amount of time a job waits in a queue before it can be executed. Alternatively, in at least some examples, the term “queuing delay” refers to the amount of time a packet waits in a queue before it can be processed and / or transmitted. In at least some examples, the term “throughput” or “network throughput” refers to the rate of production or the rate at which something is processed. Alternatively, in at least some examples, the term “throughput” or “network throughput” refers to the rate of successful message (data) delivery over a communication channel.In at least some examples, the term "transmission delay" refers to the amount of time required (or necessary) to push a packet (or all the bits of a packet) onto the transmission medium.

[0294] In at least some examples, the term “application” or “app” refers to a computer program designed to perform specific tasks other than those related to the operation of the computer itself. Furthermore, or alternatively, in at least some examples, the term “application” or “app” refers to a complete, deployable package environment for achieving specific functionality in an operating environment. In at least some examples, the term “process” refers to an instance of a computer program executed by one or more threads. In some implementations, a process may consist of multiple execution threads that execute instructions concurrently. In at least some examples, the term “algorithm” refers to a clear specification of how a problem or class of problems is solved by performing computations, input / output operations, data processing, automated reasoning tasks, etc.

[0295] In at least some examples, the term “Application Programming Interface” or “API” refers to a set of subroutine definitions, communication protocols, and tools for building software. Furthermore, or alternatively, in at least some examples, the term “Application Programming Interface” or “API” refers to a set of clearly defined methods for communication between various components. In some examples, an API may be defined or used for web-based systems, operating systems, database systems, computer hardware, software libraries, and so on.

[0296] In at least some examples, terms such as "instantiate" or "instantiate" refer to the creation of an instance. In at least some examples, "instance" also refers to the specific occurrence of an object that may occur, for example, during the execution of program code.

[0297] In at least some examples, the terms “reference point” or “base point” refer to a conceptual point in the joining of two non-overlapping functional groups, elements, or entities.

[0298] In at least some examples, the term "use case" refers to a description of a system from the user's perspective. Use cases sometimes treat the system as a black box, with interactions with the system, including system responses, perceived as being from outside the system. Use cases typically avoid technical jargon and instead prefer the language of the end-user or domain expert.

[0299] In at least some examples, the term “user” refers to an abstract representation of any entity that issues commands, requests, and / or data to a compute node or system, and / or consumes or uses services. Furthermore, or alternatively, in at least some examples, the term “user” refers to an entity that uses 3GPP system services but is not part of the 3GPP system (e.g., a person using a 3GPP system mobile station as a mobile phone). In at least some examples, the term “user profile” refers to a set of information for providing a consistent and personalized service environment to a user, regardless of the user’s location or the device used (within the limitations of the device and serving network).

[0300] In at least some examples, the terms “configuration,” “policy,” “rule set,” and / or “operational parameters” refer to machine-readable information objects that include instructions, conditions, parameters, and / or criteria related to a device, system, or other element / entity.

[0301] In at least some examples, the term “datagram” refers to a basic unit of forwarding related to a packet-switched network, and a datagram may be structured to have a header section and a payload section. In at least some examples, the term “datagram” may be synonymous with any of the following terms, namely “data unit,” “protocol data unit,” or “PDU,” “service data unit,” or “SDU,” “frame,” “packet,” “network packet,” “segment,” “block,” “cell,” “chunk,” “type length value,” or “TLV,” even if these terms may represent different aspects. Examples of datagrams, network packets, etc., include Internet Protocol (IP) packets, Internet Control Message Protocol (ICMP) packets, UDP packets, TCP packets, SCTP packets, ICMP packets, Ethernet frames, RRC messages / packets, SDAP PDUs, SDAP SDUs, PDCP PDUs, PDCP SDUs, MAC PDUs, MAC SDUs, and BAP PDUs. BAP SDUs, RLC PDUs, RLC SDUs, and WiFi frames, as discussed in IEEE 802 protocols / standards (e.g., IEEE 80211), include a Type Length Value (TLV) and / or other similar data structures. In at least some examples, the term “packet” refers to an information unit identified by a label at Layer 3 of the OSI reference model. In some examples, “packet” may also be called a “Network Protocol Data Unit” or “NPDU.” In at least some examples, the term “Protocol Data Unit” refers to a unit of data designated at the protocol layer, including (N) protocol control information and possibly (N) user data.

[0302] In at least some examples, the term “information element” or “IE” refers to a structural element containing one or more fields. Furthermore, or alternatively, in at least some examples, the term “information element” or “IE” refers to a field or set of fields defined in a standard or specification used to carry data and / or protocol information. In at least some examples, the term “field” refers to the individual contents of an information element, or a data element containing content. In at least some examples, the terms “data frame,” “data field,” or “DF” refer to a data type containing more than one data element in a predetermined order. In at least some examples, the term “data element” or “DE” refers to a data type containing a single data. Furthermore, or alternatively, in at least some examples, the term “data element” refers to the atomic state of a particular object having at least one specific property at a particular point in time, and may include one or more of the data element name or identifier, data element definition, one or more descriptive terms, enumeration values ​​or codes (e.g., metadata), and / or lists of synonyms for the data element in other metadata registries. Furthermore, or alternatively, in at least some examples, “data element” refers to a data type containing a single data. A data element may store data that may be called the data element's content (or "content item"). A content item may contain text content, attributes, properties, and / or other elements called "child elements." Furthermore, or alternatively, a data element may contain zero or more properties and / or zero or more attributes, each of which may be defined as a database object (e.g., a field, a record, etc.), an object instance, and / or other data element. In at least some examples, an "attribute" represents a markup structure containing name-value pairs that exist within a start tag or an empty element tag. Attributes contain data related to that element and / or control the element's behavior.In at least some examples, the terms “Type Length Value,” “Tag Length Value,” or “TLV” refer to an encoding scheme used for information elements in a protocol, and TLVs are sometimes used to encode further or optional information elements in a protocol. In some examples, a TLV-encoded data stream includes a code relating to the value type, the value length, and the value itself. In some examples, the type in the TLV includes a binary and / or alphanumeric code indicating the type of field represented by this part of the message, the length in the TLV includes the size of the value field (e.g., in bytes), and the value in the TLV includes a variable-sized sequence of bytes containing the data for this part of the message.

[0303] In at least some examples, the term "reference" refers to data that can be used to locate other data, and may be implemented in various ways (e.g., pointers, indexes, handles, keys, identifiers, hyperlinks, etc.).

[0304] In at least some examples, the term “data set” or “dataset” refers to a collection of data, and a “data set” or “dataset” may be formed or arranged in any type of data structure. In some examples, one or more characteristics may define or influence the structure and / or characteristics of a dataset, such as the number and types of attributes and / or variables, and various statistical measures (e.g., standard deviation, kurtosis, etc.). In at least some examples, the term “data structure” refers to the data organization, management, and / or storage format. Furthermore, or alternatively, in at least some examples, the term “data structure” refers to a collection of data values, the relationships between these data values, and / or functions, behaviors, tasks, etc., that can be applied to the data. Examples of data structures include primitives (e.g., Booleans, characters, floating-point numbers, fixed-point numbers, integers, references or pointers, enumerations, etc.), composites (e.g., arrays, records, strings, unions, tagged unions, etc.), abstract data types (e.g., data containers, lists, tuples, associative arrays, maps, dictionaries, sets (or datasets), multisets or bags, stacks, queues, graphs (e.g., trees, heaps, etc.)), routing tables, symbol tables, quad-edges, blockchains, and purely functional data structures (e.g., stacks, queues, (multi)sets, random access lists, hash consing, zipper data structures, etc.).

[0305] In at least some examples, the terms “Nyquist criterion” or “Nyquist frequency” describe a characteristic of a sampler that transforms a continuous function or signal into a discrete sequence. Furthermore, or alternatively, in at least some examples, the terms “Nyquist criterion” or “Nyquist frequency” describe a frequency (e.g., cycles per second) for a given sampling rate (e.g., samples per second) where the cycle length (or period) is twice the interval between samples.

[0306] In at least some examples, the term “machine learning” or “ML” refers to the use of computer systems to optimize performance criteria using exemplary (training) data and / or past experience. ML involves using algorithms to perform a particular task without using explicit instructions to do so, and / or relying on patterns, predictions, and / or inferences. ML uses statistics to build ML models (also called “models”) to make predictions or decisions based on sample data (e.g., training data).

[0307] In at least some examples, the term “machine learning model” or “ML model” refers to an application, program, process, algorithm, and / or function that is capable of making predictions, inferences, or decisions based on an input dataset, and / or detecting patterns based on an input dataset. In some examples, the “machine learning model” or “ML model” is trained on training data to detect patterns and / or make predictions, inferences, and / or decisions. In some examples, the “machine learning model” or “ML model” is based on a mathematical and / or statistical model. For the purposes of this disclosure, terms such as “ML model,” “AI model,” and “AI / ML model” may be used interchangeably. In at least some examples, the term “mathematical model” refers to a system of assumptions, data, and inferences presented as a mathematical description of an entity or situation, including governing formulas, assumptions, and constraints. In at least some examples, the term “statistical model” refers to a mathematical model that embodies a set of statistical assumptions about the generation of sample data from a population and / or similar data, and in some examples, the “statistical model” represents a data generation process.

[0308] In at least some examples, the terms “machine learning algorithm” or “ML algorithm” refer to an application, program, process, algorithm, and / or function that builds or estimates an ML model based on sample data or training data. Furthermore, or alternatively, in at least some examples, the terms “machine learning algorithm” or “ML algorithm” refer to a program, process, algorithm, and / or function that learns from experience with respect to some task and some performance measure / metric, and an ML model is an object or data structure created after an ML algorithm has been trained on training data. For the purposes of this disclosure, terms such as “ML algorithm,” “AI algorithm,” and “AI / ML algorithm” may be used interchangeably. Furthermore, the term “ML algorithm” may refer to a different concept from the term “ML model,” but these terms may be used interchangeably for the purposes of this disclosure.

[0309] In at least some examples, the terms “machine learning application” or “ML application” refer to an application, program, process, algorithm, and / or functionality that includes several AI / ML models and application-level descriptions. Furthermore, or alternatively, in at least some examples, the terms “machine learning application” or “ML application” refer to a complete and deployable application and / or package that includes at least one ML model and / or other data capable of achieving a particular function and / or performing a set of actions or tasks in an operating environment. For the purposes of this disclosure, terms such as “ML application,” “AI application,” and “AI / ML application” may be used interchangeably.

[0310] The terms “artificial neural network,” “neural network,” or “NN” refer to a machine learning technique that includes a collection of connected artificial neurons or nodes that (loosely) model neurons in a biological brain that can transmit signals to other trunk neurons or nodes, where the connections (or edges) between the artificial neurons or nodes are (loosely) modeled on synapses in a biological brain. The artificial neurons and edges typically have weights that adjust as learning progresses. The weights increase or decrease the intensity of the signal at the connection. Neurons may have thresholds such that a signal is transmitted only if the aggregated signal exceeds that threshold. Artificial neurons can be aggregated or grouped into one or more layers, and different layers may perform different transformations on these inputs. Signals travel from the first layer (input layer) to the last layer (output layer), possibly traversing layers multiple times. NNs are typically used for supervised learning, but can also be used for unsupervised learning. Examples of neural networks (NNs) include deep NNs (DNNs), feedforward NNs (FFNs), deep FNNs (DFFs), convolutional NNs (CNNs), deep CNNs (DCNs), deconvolutional NNs (DNNs), deep belief NNs, perception NNs, recurrent NNs (RNNs) (including, for example, Long Short-Term Memory (LSTM) algorithms, gated recurrent units (GRUs), echo state networks (ESNs), etc.), spiking NNs (SNNs), deep stacking networks (DSNs), Markov chains, perception NNs, generative adversarial networks (GANs), transformers, and probabilistic NNs (e.g., Bayesian networks (BNs)). Network), Bayesian Belief Network (BBN,This includes Bayesian belief networks, Bayesian NNs (BNN), deep BNNs (DBNN), dynamic BNNs (DBN), probabilistic graphical models (PGM), Boltzmann machines, restricted Boltzmann machines (RBM), Hopfield networks or Hopfield NNs, convolutional deep belief networks (CDBN), etc., linear dynamical systems (LDS), switching LDS (SLDS), optical NNs (ONN), and NNs for reinforcement learning (RL) and / or deep RL (DRL).

[0311] In at least some examples, the term “optimization” refers to the act, process, or methodology of making something (e.g., a design, system, or decision) as complete, functional, or effective as possible. Optimization typically involves mathematical procedures such as finding the maximum or minimum value of a function. In at least some examples, the term “optimal” refers to the most desirable or satisfactory result, outcome, or output. In at least some examples, the term “optimum” refers to the quantity or degree of what is most favorable for some outcome. In at least some examples, the term “optima” refers to the conditions, degree, quantity, or compromise that produce the best possible outcome. Furthermore, or alternatively, in at least some examples, the term “optima” refers to the most favorable or advantageous outcome or result.

[0312] In at least some examples, the term “probability” refers to a numerical description of how likely an event is to occur and / or how likely a proposition is to be true. In at least some examples, the term “probability distribution” refers to a mathematical function that gives the probability of different possible outcomes occurring for an experiment or event.

[0313] In at least some examples, the term “predictive service” refers to a service model that provides reliable performance but allows for variations in specified performance criteria.

[0314] In at least some examples, the term “Timing Advance Group” or “TAG” refers to a group of serving cells that use the same Timing Reference Cell and the same Timing Advance (TA) value for a cell configured by RRC and UL. In some examples, a TAG containing a MAC entity is called a Primary TAG (PTAG), and the term Secondary TAG (STAG) refers to other TAGs.

[0315] Many of the examples above are provided using specific cellular / mobile network terminology, including the use of 4G / 5G 3GPP network components (or assumed terahertz-based 6G / 6G+ technologies), but it should be understood that these examples may also apply to many other deployments of wide-area and local wireless networks, as well as the integration of wired networks (including optical networks and associated fibers, transceivers, etc.). Furthermore, various standards (e.g., 3GPP, ETSI, etc.) may define various message formats, PDUs, containers, frames, etc., as containing sequences of optional or required data elements (DE), data frames (DF), information elements (IE), etc. However, the requirements of any particular standard should not limit the examples discussed herein, and it should be understood that any combination of containers, frames, DFs, DEs, IEs, values, actions, and / or features is possible in various examples, including any combination of containers, frames, DFs, DEs, IEs, values, actions, and / or features that are strictly required to be followed in order to comply with such standards, or any combination of containers, frames, DFs, DEs, IEs, values, actions, and / or features that are strongly recommended and / or used with or in the presence / absence of optional elements.

[0316] Aspects of the subject matter of the present invention may be referred to individually and / or collectively herein for convenience only, without the intention of voluntarily limiting the scope of this application to any single aspect or inventive concept if more than one is actually disclosed. Therefore, it should be recognized that while certain aspects are illustrated and described herein, any configuration calculated to achieve the same objective may be substituted for any particular aspect shown. This disclosure is intended to cover any and all adaptations or variations of any of the various aspects. Combinations of the above aspects with other aspects not specifically described herein will become apparent to those skilled in the art by considering the above description.

Claims

1. A user equipment (UE) device for operating a media access control (MAC) entity for multi-transmit / receive point (TRP) operation, It includes a processor circuit and one or more computer-readable media containing instructions, The execution of the instruction by the processor circuit results in the UE receiving, The system receives a Timing Advance Command (TAC) that includes a Timing Advance (TA) field. The MAC entity receives a Timing Advance Group (TAG) Identity (TAG ID) that identifies a group of serving cells to which the TAC applies, where at least one serving cell in the group of serving cells is associated with at least two TA fields, each of which contains a TA value. Using one of the TA values ​​in each of the two aforementioned TA fields, the UL timing for uplink (UL) transmission is adjusted. A device that causes the UL transmission to be performed according to the adjusted UL timing.

2. The apparatus according to claim 1, wherein the instruction causes the processor circuit to further receive the TAG ID indicated by the radio resource control (RRC) configuration.

3. The apparatus according to claim 1, wherein the transmission configuration indicator (TCI) state is associated with the TA value.

4. The apparatus according to claim 1, wherein the TAC is included in a TAC media access control (MAC) control element (CE), an absolute TAC MAC CE, or a random access response (RAR) message.

5. The apparatus according to claim 1, wherein the UL transmission is PUSCH transmission, PUCCH transmission, or SRS transmission.

6. This is a next-generation node B (gNB) device, It includes one or more processors and memory storing computer-readable instructions, The computer-readable instruction is provided to one or more processors. A timing advance command (TAC) is generated and transmitted to the user equipment (UE), where the TAC includes a timing advance field used to adjust the uplink transmission timing of the UE's uplink transmission. The UE generates a Timing Advance Group (TAG) Identity (TAG ID) that identifies a group of serving cells to which the TAC applies, where at least one serving cell in the group of serving cells is associated with at least two TA fields, each of which contains a TA value. Processing the uplink transmission received from the UE according to the adjusted uplink timing. A device that issues commands.

7. The apparatus according to claim 6, wherein the computer-readable instruction instructs one or more processors to generate a radio resource control (RRC) configuration indicating the TAG ID.

8. The apparatus according to claim 6, wherein the transmission configuration indicator (TCI) state is associated with the TA value.

9. The apparatus according to claim 6, wherein the TAC is included in a TAC media access control (MAC) control element (CE), an absolute TAC MAC CE, or a random access response (RAR) message.

10. The apparatus according to claim 6, wherein the uplink transmission is PUSCH transmission, PUCCH transmission, or SRS transmission.

11. One or more data storage devices that store computer-readable instructions, The aforementioned computer-readable instruction is transmitted to one or more processors. The system processes a Radio Resource Control (RRC) configuration received from a Radio Access Network (RAN) node, wherein the RRC configuration comprises a UE with a serving cell associated with at least two Timing Advance (TA) Groups (TAGs). Processing at least two TA commands (TACs) received from the RAN node, wherein the at least two TACs indicate the at least two TA fields corresponding to the at least two TAGs in order to associate the serving cell with at least two TA fields, Using one of the respective TA values ​​in at least two of the aforementioned TA fields, the UL timing for uplink (UL) transmission is adjusted. The UL transmission is performed according to the adjusted UL timing. One or more data storage devices configured to issue commands.

12. The instruction causes one or more processors to further receive the TAG ID indicated by the radio resource control (RRC) configuration, as described in claim 11, for one or more data storage devices.

13. One or more data storage devices according to claim 11, wherein the transmission configuration indicator (TCI) state is associated with the TA value.

14. The TAC is included in a TAC media access control (MAC) control element (CE), an absolute TAC MAC CE, or a random access response (RAR) message, one or more data storage devices according to claim 11.

15. The data storage device according to claim 11, wherein the UL transmission is PUSCH transmission, PUCCH transmission, or SRS transmission.

Images