Determining RAR window and ra-RNTI for multiple prach transmissions

Abstract

Various embodiments in the present disclosure provide techniques for multiple physical random access channel (PRACH) transmissions. For example, embodiments provide techniques for determining a random access response (RAR) window and / or a random access (RA)-radio network temporary identifier (RNTI) for a plurality of PRACH transmissions. Further, embodiments relate to a plurality of PRACH transmissions triggered by a physical downlink control channel (PDCCH) command. Other embodiments are described and claimed.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the priority of U.S. Provisional Patent Application No. 63 / 391,237 filed on July 21, 2022, U.S. Provisional Patent Application No. 63 / 407,793 filed on September 19, 2022, U.S. Provisional Patent Application No. 63 / 421,677 filed on November 2, 2022, and U.S. Provisional Patent Application No. 63 / 494,298 filed on April 5, 2023. Technical Field

[0003] Various embodiments may generally relate to the field of wireless communications.For example, some embodiments may relate to determining a random access response (RAR) window and / or a random access (RA)-radio network temporary identifier (RNTT) for multiple physical random access channel (PRACH) transmissions. Background Art

[0004] Mobile communications have evolved rapidly from early voice systems to today's highly complex integrated communications platforms. The next generation of wireless communication systems (5G) or New Radio (NR) will provide ubiquitous information access and data sharing by a variety of users and applications. NR is expected to be a unified network / system that aims to meet widely varying and sometimes conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. Generally speaking, NR will evolve on the basis of 3GPP Advanced Long Term Evolution (LTE), with NR having the potential to add new radio access technology (RAT) technology to enrich people's lives with better, simpler and more seamless wireless connection solutions. NR will enable wireless connectivity for everything and provide fast, rich content and services.

[0005] For a cellular system, coverage is an important factor for successful operation. Compared to LTE, NR can be deployed at relatively higher carrier frequencies in frequency range 1 (FR1), for example at 3.5 GHz. In this case, coverage loss is expected due to larger path loss, which makes it more challenging to maintain adequate quality of service. Typically, uplink coverage is the bottleneck for system operation, given the low transmit power on the UE side. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Embodiments of the present invention can be easily understood by the following detailed description in conjunction with the accompanying drawings. For the convenience of this description, the same reference numerals represent the same structural elements. Embodiments are shown in the accompanying drawings by way of example and not by way of limitation.

[0007] Figure 1 A 4-step random access channel (RACH) procedure according to various embodiments is schematically illustrated.

[0008] Figure 2A A random access response (RAR) window is shown after the last symbol of the last physical random access channel (PRACH) instant in accordance with various embodiments.

[0009] Figure 2B The RAR window after the last symbol of the actual PRACH transmission is shown according to various embodiments.

[0010] Figure 3A The RAR window after the last symbol of the first PRACH instant is shown according to various embodiments.

[0011] Figure 3B The RAR window after the last symbol of the first actual PRACH transmission is shown according to various embodiments.

[0012] Figure 4 The RAR window after the last symbol of each PRACH instance is shown according to various embodiments.

[0013] Figure 5 A wireless network according to various embodiments is schematically illustrated.

[0014] Figure 6 Components of a wireless network according to various embodiments are schematically illustrated.

[0015] Figure 7 is a block diagram illustrating components according to some exemplary embodiments that are capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed in the present disclosure.

[0016] Figure 8 , Fig. 9 and Fig.10 Depicted are exemplary procedures for practicing various embodiments discussed in this disclosure. DETAILED DESCRIPTION

[0017] The following detailed description refers to the accompanying drawings. The same figure number may be used to identify the same or identical elements in different drawings. In the following description, for the purpose of explanation rather than limitation, specific details such as specific structures, architectures, interfaces, technologies, etc. are listed to provide a thorough understanding of the various aspects of various embodiments. However, for those skilled in the art who benefit from the present disclosure, the various aspects of the various embodiments may be practiced in other examples that deviate from these specific details. In some cases, the description of familiar devices, circuits, and methods is omitted so as not to obscure the description of the various embodiments with unnecessary details. For the purposes of this disclosure, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0018] Various embodiments in the present disclosure provide techniques for multiple physical random access channel (PRACH) transmissions. For example, embodiments provide techniques for determining a random access response (RAR) window and / or a random access (RA)-radio network temporary identifier (RNTI) for multiple PRACH transmissions. In addition, embodiments also relate to multiple PRACH transmissions triggered by a physical downlink control channel (PDCCH) command.

[0019] In NR Rel-15, a 4-step process is defined. Figure 1 The 4-step RACH procedure for initial access is shown. In the first step, the UE transmits a Physical Random Access Channel (PRACH) in the uplink by randomly selecting a preamble signature, which will allow the gNB to estimate the delay between the gNB and the UE for subsequent UL timing adjustment. Subsequently, in the second step, the gNB feeds back a Random Access Response (RAR) which carries the Timing Advance (TA) command information and an uplink grant for uplink transmission in the third step. The UE expects to receive the RAR within a time window, the start and end of which are configured by the gNB via the System Information Block (SIB).

[0020] As defined in NR Rel-15, the number of repetitions for PRACH formats 1 and 2 is 2 and 4 respectively, which can help improve the coverage of the long PRACH format. However, for the short PRACH format, the repetitions are not limited. It should be noted that PRACH transmission is very important for many processes (for example, initial access and beam failure recovery). In order to improve coverage for PRACH (especially short PRACH format), multiple PRACH transmissions can be considered.

[0021] During the 4-step RACH, the UE monitors the physical downlink control channel (PDCCH) used to schedule the Msg2 transmission in the RAR monitoring window, which starts at the first symbol of the earliest control resource set (CORESET). The UE is configured to receive the PDCCH for the Type 1-PDCCH common search space (CSS) set, which is located at least one symbol after the last symbol of the PRACH time corresponding to the PRACH transmission. If multiple PRACH transmissions are supported to enhance coverage, it is necessary to develop a certain RAR monitoring window.

[0022] Various embodiments in the present disclosure provide mechanisms for determining the RAR window and / or RA-RNTI for multiple PRACH transmissions. For example, aspects of the various embodiments may include:

[0023] Determine the RAR monitoring window for multiple PRACH transmissions;

[0024] · determining the RA-RNTI for multiple PRACH transmissions; and / or

[0025] • Multiple PRACH transmissions triggered by PDCCH orders.

[0026] Embodiments in the present disclosure may improve NR PRACH coverage.

[0027] Determining the RAR monitoring window for multiple PRACH transmissions

[0028] As described above, during the 4-step RACH, the UE monitors the PDCCH for scheduling Msg2 transmission in the RAR monitoring window, the RAR monitoring window starting from the first symbol of the earliest CORESET, and the UE is configured to receive the PDCCH for the Type l-PDCCH CSS set, which is located at least one symbol after the last symbol of the PRACH moment corresponding to the PRACH transmission. In the case of supporting multiple PRACH transmissions, the previous technology for determining the RAR monitoring window may not be applicable.

[0029] Various embodiments in the present disclosure provide techniques for determining a RAR monitoring window for multiple PRACH transmissions.

[0030] In one embodiment, the RAR window starts after the last symbol of the last PRACH for multiple PRACH transmissions, in which case a single RAR window for multiple PRACH transmissions may be monitored.

[0031] For example, the RAR window starts at the first symbol of the earliest CORESET, and the UE is configured to receive a Type l-PDCCH CSS set for a PDCCH located at least one symbol after the last symbol corresponding to the last PRACH moment of the PRACH transmission, where the symbol duration corresponds to the SCS for the Type l-PDCCH CSS set.

[0032] Figure 2A An example of a RAR window after the last symbol of the last PRACH time is shown. In this example, two repetitions are applied for PRACH transmission in slot #0 and slot #3. In addition, a CORESET with Type-1 CSS is configured in slot #2 and slot #5. According to this option, the RAR window starts from the first symbol in slot #5 (which is after the second PRACH repetition).

[0033] In one option, the last PRACH time instant may correspond to the last PRACH time instant determined for the multiple PRACH transmissions, regardless of whether the last PRACH transmission in the multiple PRACH transmissions is canceled or discarded. In some aspects, a PRACH transmission may be canceled or discarded due to a collision with a DL symbol, as indicated by a dynamic slot format indication (SFI).

[0034] Under another option, the last PRACH time instant may correspond to the actual last PRACH transmission for multiple PRACH transmissions.As described above, a PRACH transmission may be cancelled or dropped due to collision with DL symbols as indicated by a dynamic slot format indication (SFI).

[0035] Figure 2B An example of a RAR window after the last symbol of the last actual PRACH transmission is shown. In this example, a PRACH moment group includes 4 PRACH moments (RO). The PRACH transmission in the last PRACH moment #3 is canceled. For this option, the RAR window starts after the last symbol of the last actual PRACH transmission in RO#2.

[0036] In another embodiment, the RAR window starts after the last symbol of the last PRACH instant for multiple PRACH transmissions. In this case, a single RAR window may be monitored for multiple PRACH transmissions.

[0037] For example, the RAR window starts at the first symbol of the earliest CORESET, and the UE is configured to receive a PDCCH for a Type 1-PDCCH CSS set that is at least one symbol after the last symbol of the first PRACH moment corresponding to the PRACH transmission. In one option, the symbol duration corresponds to the SCS of the Type 1-PDCCH CSS set.

[0038] In this case, the RAR window size can be determined based on the configured RAR window size and the position of the PRACH time corresponding to the last PRACH repetition. In one option, the RAR window starts from the above option and the last symbol of the RAR window is determined based on the configured RAR window size and the position of the PRACH time corresponding to the last PRACH repetition.

[0039] Figure 3AThe RAR window after the last symbol of the first PRACH instant is shown. In this example, two repetitions are applied for PRACH transmission in slot #0 and slot #3. In addition, a CORESET with Type-1 CSS is configured in slot #2 and slot #5. Based on this scheme, the RAR window starts from the first symbol in slot #2 (which is after the first PRACH repetition).

[0040] In one option, regardless of whether the first PRACH transmission in the plurality of PRACH transmissions is canceled or dropped, the first PRACH time instant may correspond to the first PRACH time instant determined for the plurality of PRACH transmissions. In some aspects, the PRACH transmission may be canceled or dropped due to a collision with a DL symbol as indicated by a dynamic slot format indication (SFI).

[0041] In another option, the first PRACH instant may correspond to an actual first PRACH transmission for multiple PRACH transmissions.As described above, a PRACH transmission may be cancelled or dropped due to collision with a DL symbol as indicated by a dynamic slot format indication (SFI).

[0042] Figure 3B An example of a RAR window after the last symbol of the first actual PRACH transmission is shown. In this example, a PRACH moment group includes 4 PRACH moments (RO). The PRACH transmission in the first PRACH moment #0 is cancelled. For this scheme, the RAR window starts just after the last symbol of the first actual PRACH transmission in RO#1.

[0043] In another embodiment, the RAR window starts after the last symbol of each PRACH moment for multiple PRACH transmissions. Specifically, the RAR window starts at the first symbol of the earliest CORESET, and the UE is configured to receive a PDCCH for a Typel-PDCCH CSS set, which is located at least one symbol after the last symbol of each PRACH moment corresponding to the PRACH transmission, wherein the symbol duration corresponds to the SCS for the Typel-PDCCH CSS set.

[0044] In this case, multiple RAR windows may be monitored for multiple PRACH transmissions corresponding to each PRACH repetition. This may be applicable when different Tx beams are applied to different PRACH repetitions.

[0045] Figure 4An example of a RAR window after the last symbol of each PRACH instant is shown. In this example, two repetitions are applied for PRACH transmission in slot #0 and slot #3. In addition, a CORESET with Type-1 CSS is configured in slot #2 and slot #5. Based on this option, two RAR windows are monitored, where the first RAR window starts from the first symbol in slot #2 and the second RAR window starts from the first symbol in slot #5.

[0046] In another embodiment, the RAR window starts after the last symbol of each PRACH moment in the subset of PRACH moments corresponding to the plurality of PRACH transmissions. Specifically, the RAR window starts at the first symbol of the earliest CORESET, the UE being configured to receive a PDCCH for a Type 1-PDCCH CSS set on the earliest CORESET, the PDCCH being located at least one symbol after the last symbol in each PRACH moment in the subset of PRACH moments corresponding to the PRACH transmissions, wherein the symbol duration corresponds to the SCS for the Type 1-PDCCH CSS set.

[0047] In one option, the PRACH time subset may be configured by higher layers via NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling. In another option, the PRACH time subset may be determined based on the number of repetitions used for PRACH transmission. For example, when the number of repetitions of PRACH transmission is 8, the RAR window may start after the last symbol of every 2 PRACH time instances corresponding to multiple PRACH transmissions.

[0048] Note that for this option, multiple RAR windows may be monitored for multiple PRACH transmissions corresponding to each PRACH moment in the subset of PRACH moments for the multiple PRACH transmissions.

[0049] In another embodiment, the RAR window starts after the last symbol of the PRACH instant corresponding to one of the multiple PRACH transmissions. Specifically, the RAR window starts at the first symbol of the earliest CORESET, and the UE is configured to receive a PDCCH for a Type 1-PDCCH CSS set on the earliest CORESET, the PDCCH being located at least one symbol after the last symbol of the PRACH instant corresponding to the PRACH transmission, wherein the symbol duration corresponds to the SCS for the Type 1-PDCCH CSS set.

[0050] In one option, the PRACH occasion for the RAR monitoring window can be configured by a higher layer via RMSI, OSI, or RRC signaling. In another option, the PRACH occasion can be determined based on the number of repetitions for PRACH transmission. Specifically, the determined PRACH occasion for the RAR monitoring window can be located after the PRACH repetition with half the number of repetitions. In one example, when the number of repetitions for PRACH transmission is 8, the RAR window can start after the last symbol of the 5th PRACH occasion for the corresponding PRACH repetition.

[0051] Note that for this option, a single RAR window can be monitored for multiple PRACH transmissions, and this window corresponds to the PRACH occasion for the corresponding PRACH repetition.

[0052] Determining RA-RNTI for multiple PRACH transmissions

[0053] As defined in the 4-step RACH, the UE monitors the PDCCH with cyclic redundancy check (CRC) during the second step for RAR reception, and this cyclic redundancy check (CRC) is scrambled by a random access - radio network temporary identity (RA-RNTI). Note that the determination of RA-RNTI is described in Section 5.1.3 of TS38.321, V16.2.0[l]:

[0054] RA-RNTI is associated with the PRACH occasion in which the random access preamble is transmitted, and RA-RNTI is calculated as follows:

[0055] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id

[0056] where s_id is the index of the first OFDM symbol of the PRACH occasion (0 < s_id < 14), t_id is the index of the first time slot of the PRACH occasion in the system frame (0 < t_id < 80), where the subcarrier spacing used to determine t_id is based on the μ value specified in Clause 5.3.2 of TS38.211[8]. f_id is the index of the PRACH occasion in the frequency domain (0 < f_id < 8), and ul_carrier_id is the UL carrier used for random access preamble transmission (0 represents the NUL carrier, and 1 represents the SUL carrier).

[0057] For multiple PRACH transmissions, the PRACH transmission can be repeated in more than one PRACH occasion. In this case, the existing formula for determining RA-RNTI may not be directly applicable. Therefore, some mechanisms for determining RA-RNTI during the 4-step RACH procedure may need to be defined.

[0058] In various embodiments of the present disclosure, techniques are provided for determining a RA-RNTI for a plurality of PRACH transmissions.

[0059] In one embodiment, for a plurality of PRACH transmissions, a symbol index, a slot index, and a frequency resource index in a formula for RA-RNTI calculation may be determined according to a first PRACH occasion among a plurality of PRACH occasions.

[0060] In one example, for RA-RNTI determination, the following text in Section 5.1.3 of TS38.321 may be updated as underlined.

[0061] The RA-RNTI associated with the PRACH occasion in which the random access preamble is transmitted is calculated as follows:

[0062] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id

[0063] where s_id is First the index of the first OFDM symbol of the PRACH occasion (0 < s_id < 14), t_id is the index of the first slot in the system frame First in which the PRACH occasion is located (0 < t_id < 80), where the subcarrier spacing used to determine t_id is based on the μ value specified in Article 5.3.2 of TS38.211[8], f_id is First the index of the PRACH occasion in the frequency domain (0

[0064] ≤ f_id < 8), and ul_carrier_id is the UL carrier used for random access preamble transmission (0 represents the NUL carrier, and 1 represents the SUL carrier).

[0065] In one example, for RA-RNTI determination, the following text in Section 5.1.3 of TS38.321 may be updated as underlined.

[0066] The RA-RNTI associated with the PRACH occasion in which the random access preamble is transmitted is calculated as follows:

[0067] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id

[0068] where s_id is First the index of the first OFDM symbol of the PRACH occasion (0 ≤ s_id

[0069] <14), where t_id is the index of the first time slot of the PRACH occasion in a system frame First (0 < t_id < 80), and the subcarrier spacing used to determine t_id is based on the μ values specified in clause 5.3.2 of TS 38.211 [8] for μ = {0, 1, 2, 3} and μ = {5, 6}, and t_id is the index of the 120 kHz time slot in the system frame that contains First the PRACH occasion (0 < t_id < 80), f_id is the index of the PRACH occasion in the frequency domain First (0 < f_id < 8), and ul_carrier_id is the UL carrier used for random access preamble transmission (0 represents the NUL carrier, and 1 represents the SUL carrier).

[0070] In one option, regardless of whether the first PRACH transmission among multiple PRACH transmissions is cancelled or discarded, the first PRACH occasion can correspond to the first PRACH occasion determined for the multiple PRACH transmissions. In some aspects, a PRACH transmission can be cancelled or discarded due to a DL symbol conflict indicated by, for example, a dynamic slot format indication (SFI).

[0071] In another option, the first PRACH occasion can correspond to the actual first PRACH transmission for the multiple PRACH transmissions. As described above, a PRACH transmission can be cancelled or discarded due to a DL symbol conflict indicated by, for example, a dynamic slot format indication (SFI).

[0072] In another embodiment, for multiple PRACH transmissions, the symbol index, time slot index, and frequency resource index in the formula for RA-RNTI calculation can be determined based on the last PRACH occasion among the multiple PRACH occasions.

[0073] In one example, to determine the RA-RNTI, the following text in section 5.1.3 of TS 38.321 can be updated as underlined.

[0074] The RA-RNTI associated with the PRACH occasion in which the random access preamble is transmitted is calculated as follows:

[0075] RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id

[0076] where s_id is at last the index of the first OFDM symbol of the PRACH occasion (0 ≤ s_id

[0077] <14), where t_id is the index of the first time slot of the PRACH occasion in a system frame at lastThe index of the first time slot at the PRACH moment (0≤t_id<80), where the subcarrier spacing used to determine t_id is based on the μ value specified in Section 5.3.2 of TS38.211[8], and f_id is the frequency domain at last f_id is the index of the PRACH instant (0≤f_id<8), and ul_carrier_id is the UL carrier used for random access preamble transmission (0 indicates NUL carrier, and 1 indicates SUL carrier).

[0078] In one example, for RA-RNTI determination, the following text in Section 5.1.3 of TS 38.321 may be updated as underlined below.

[0079] The RA-RNTI associated with the PRACH instant in which the random access preamble is transmitted is calculated as follows:

[0080] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0081] Among them, s_id is at last The index of the first OFDM symbol at the PRACH time (0≤s_id

[0082] <14), t_id is the system frame at last The index of the first time slot at the PRACH time (0≤t_id<80), where the subcarrier spacing used to determine t_id is based on the μ value specified in clause 5.3.2 of TS38.211 [8] for μ={0,1,2,3} and μ={5,6}, and t_id is contained in the system frame at last The index of the 120kHz time slot of PRACH (0≤t_id<80), f_id is the frequency domain at last f_id is the index of PRACH (0≤f_id<8), and ul_camer_id is the UL carrier used for random access preamble transmission (0 represents NUL carrier and 1 represents SUL carrier).

[0083] In one option, regardless of whether the last PRACH transmission of the multiple PRACH transmissions is canceled or discarded, the last PRACH time can correspond to the last PRACH time determined for the multiple PRACH transmissions. In some aspects, the PRACH transmission can be canceled or discarded due to a collision with a DL symbol as indicated by a dynamic slot format indication (SFI).

[0084] In another option, the last PRACH time instant may correspond to the actual last PRACH transmission for multiple PRACH transmissions.As described above, a PRACH transmission may be cancelled or dropped due to collision with a DL symbol as indicated by a dynamic slot format indication (SFI).

[0085] In another embodiment, for multiple PRACH transmissions, the symbol index, slot index, and frequency resource index in the formula for RA-RNTI calculation may be determined according to the PRACH moment in the multiple PRACH moments. The PRACH moment may be predefined in the specification or may be configured by a higher layer via NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling.

[0086] In another embodiment, for multiple PRACH transmissions, the symbol index, slot index, and frequency resource index in the formula for RA-RNTI calculation may be determined according to each of the multiple PRACH moments. In this case, the UE may monitor multiple RARs corresponding to each PRACH repetition.

[0087] Multiple PRACH transmissions triggered by PDCCH orders

[0088] Various embodiments in this disclosure provide techniques for multiple PRACH transmissions triggered by PDCCH orders.

[0089] In one embodiment, as described in [11, TS 38.321], if the random access procedure is initiated by a PDCCH order, then if requested by higher layers, the UE transmits PRACH at a selected PRACH time instant where the time between the last symbol received by the PDCCH order and the first symbol of the first PRACH transmission is greater than or equal to N T,2 +Δ BWPSwitching +Δ Delay +T switch milliseconds (msec), where N is defined in TS38.213, 16.10.0 [2] T,2 , Δ BWPSwitching , Δ Delay and T switch .

[0090] In one option, the first PRACH transmission may correspond to a first PRACH time instant determined for the plurality of PRACH transmissions, regardless of whether the first PRACH transmission of the plurality of PRACH transmissions is cancelled or dropped. In certain aspects, the PRACH transmission may be cancelled or dropped due to a collision with a DL symbol as indicated by a dynamic slot format indication (SFI).

[0091] In another option, the first PRACH transmission may correspond to the actual first PRACH transmission for multiple PRACH transmissions.As described above, a PRACH transmission may be cancelled or dropped due to collision with a DL symbol as indicated by a dynamic SFI.

[0092] In another embodiment, for a PRACH transmission by a UE triggered by a PDCCH command, the PRACH Mask Index field [5, TS38.212] (if the value of the Random Access Preamble Index field is not zero) indicates the PRACH time for the PRACH transmission, in which the PRACH time is associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of the PDCCH command. cell，offset (K 小区，偏移 ) multiplied by CellSpecific_Koffset, the first PRACH time is in time slot n+2 μ ·K cell，offset After that, where n is assumed to be T TA =0 is the time slot of the UL BWP used for PRACH transmission, which overlaps with the end of PDCCH command reception, and μ is the SCS configuration used for PRACH transmission.

[0093] In one option, regardless of whether the first PRACH transmission of the multiple PRACH transmissions is cancelled or dropped, the first PRACH time may correspond to the first PRACH time determined for the multiple PRACH transmissions. In some aspects, the PRACH transmission may be cancelled or dropped due to collision with a DL symbol as indicated by a dynamic SFI.

[0094] In another option, the first PRACH instant may correspond to the actual first PRACH transmission for multiple PRACH transmissions.As described above, a PRACH transmission may be cancelled or dropped due to collision with a DL symbol as indicated by a dynamic SFI.

[0095] System and implementation

[0096] Figure 5-Figure 7 Various systems, devices, and components are shown that can implement aspects of the disclosed embodiments.

[0097] Figure 5 A network 500 according to various embodiments is shown. The network 500 may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G / NR systems. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applicable to other networks that benefit from the principles described in the present disclosure, such as future 3GPP systems, etc.

[0098] The network 500 may include a UE 502, which may include any mobile or non-mobile computing device designed to communicate with the RAN 504 via an over-the-air connection. The UE 502 may be communicatively coupled to the RAN 504 via a Uu interface. The UE 502 may be, but is not limited to, a smartphone, a tablet computer, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment system, an in-vehicle entertainment device, a dashboard, a head-up display device, an on-board diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked device, a machine type communication device, a machine-to-machine (M2M) or device-to-device (D2D) device, an Internet of Things (IoT) device, etc.

[0099] In some embodiments, the network 500 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be machine-to-machine / device-to-device (M2M / D2D) devices that communicate using physical sidelink channels (such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.).

[0100] In some embodiments, UE 502 may also communicate with AP 506 over the air. AP 506 may manage a WLAN connection, which may be used to offload some / all network traffic from RAN 504. The connection between UE 502 and AP 506 may conform to any IEEE 802.11 protocol, where AP 506 may be a Wireless Fidelity (Wireless Fidelity) wireless network. Router. In some embodiments, UE 502, RAN 504, and AP 506 may utilize cellular-WLAN aggregation (eg, LWA / LWIP). Cellular-WLAN aggregation may involve UE 502 being configured by RAN 504 to utilize both cellular radio resources and WLAN resources simultaneously.

[0101] RAN 504 may include one or more access nodes such as AN 508. AN 508 may terminate the air interface protocol for UE 502 by providing access layer protocols including RRC, PDCP, RLC, MAC and LI protocols. In this way, AN 508 may allow data / voice connections between CN 520 and UE 502. In some embodiments, AN 508 may be implemented in a discrete device or as one or more software entities running on a server computer as part of a virtual network, such as a CRAN or a virtual baseband unit pool. AN 508 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 508 may be a macro cell base station or a low power base station that is used to provide a femto cell, pico cell or other similar cell with smaller coverage, smaller user capacity or higher bandwidth than a macro cell.

[0102] In an embodiment where the RAN 504 includes multiple ANs, the ANs may be coupled to each other via an X2 interface (if the RAN 504 is an LTE RAN) or an Xn interface (if the RAN 504 is a 5G RAN). The X2 / Xn interface (which may be divided into a control / user plane interface in some embodiments) may allow the ANs to transmit information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0103] The ANs of the RAN 504 may each manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access for the UE 502. The UE 502 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 504. For example, the UE 502 and the RAN 504 may use carrier aggregation to allow the UE 502 to connect to multiple component carriers, each of which corresponds to a Pcell or an Scell. In a dual-connectivity scenario, the first AN may be a primary node providing an MCG, and the second AN may be an auxiliary node providing an SCG. The first / second AN may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0104] RAN 504 may provide an air interface via a licensed spectrum or an unlicensed spectrum. To operate in an unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCells / Scells. Before accessing an unlicensed spectrum, a node may perform a medium / carrier sensing operation, such as a listen-before-talk (LBT) protocol.

[0105] In the V2X scenario, the UE 502 or AN 508 may be or act as an RSU, which may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. In the case of an RSU implemented in or by the following devices: the UE may be referred to as a "UE-type RSU"; the eNB may be referred to as an "eNB-type RSU"; the gNB may be referred to as a "gNB-type RSU", etc. In one example, the RSU is a computing device that is coupled to an RF (radiofrequency) circuit located on the roadside to provide connection support for passing vehicle UEs. The RSU may also include internal data storage circuits to store intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling current vehicle and pedestrian traffic. The RSU may provide extremely low latency communications required for high-speed events such as collision avoidance, traffic warnings, etc. In addition or alternatively, the RSU may also provide other cell WLAN communication services. The components of the RSU may be housed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (such as Ethernet) to a traffic signal controller or backhaul network.

[0106] In some embodiments, the RAN 504 may be an LTE RAN 510 with an eNB (e.g., eNB 512). The LTE RAN 510 may provide an LTE air interface with the following features: SCS of 15 kHz; CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL; turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on sub-6 GHz frequency bands.

[0107] In some embodiments, the RAN 504 may be a NG-RAN 514 having a gNB (e.g., gNB 516) or an ng-eNB (e.g., ng-eNB 518). The gNB 516 may be connected to a 5G-enabled UE using a 5G NR interface. The gNB 516 may be connected to the 5G core via an NG interface (which may include an N2 interface or an N3 interface). The ng-eNB 518 may also be connected to the 5G core via an NG interface, but may be connected to the UE via an air interface via LTE. The gNB 516 and the ng-eNB 518 may be connected to each other via an Xn interface.

[0108] In some embodiments, the NG interface can be divided into two parts: an NG user plane (NG-U) interface, which transmits traffic data between the nodes of the NG-RAN 514 and the UPF 548 (e.g., the N3 interface); and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 514 and the AMF 544 (e.g., the N2 interface).

[0109] NG-RAN 514 may provide a 5G-NR air interface with the following features: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polarity codes, repetition codes, simplex codes and Reed-Muller codes for control, and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS. The 5G-NR air interface may not use CRS, but may use PBCHDMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signals for time tracking. The 5G-NR air interface may operate on FR1 bands including bands below 6 GHz or FR2 bands including bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSBs, which are regions in a downlink resource grid including PSS / SSS / PBCH.

[0110] In some embodiments, the 5G-NR air interface may use the BWP for various purposes. For example, the BWP may be used for dynamic adaptation of the SCS. For example, the UE 502 may be configured with multiple BWPs, each of which is configured with a different SCS. When a BWP change is indicated to the UE 502, the SCS of the transmission also changes. Another use case for the BWP is related to power saving. In particular, multiple BWPs may be configured for the UE 502, with different numbers of frequency resources (e.g., PRBs) supporting data transmission under different traffic load conditions. A BWP containing a smaller number of PRBs may be used for data transmission under light traffic loads while allowing power saving at the UE 502 and in some cases at the gNB 516. A BWP containing a larger number of PRBs may be used in scenarios with higher traffic loads.

[0111] RAN 504 is communicatively coupled to CN 520, which includes network elements that provide various functions to support data and telecommunication services to customers / subscribers (e.g., users of UE 502). The components of CN 520 may be implemented in one physical node or in separate physical nodes. In some embodiments, NFV may be used to virtualize any or all functions provided by the network elements of CN 520 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of CN 520 may be referred to as a network slice, and a logical instantiation of a portion of CN 520 may be referred to as a network sub-slice.

[0112] In some embodiments, CN 520 may be an LTE CN 522, which may also be referred to as an EPC. LTE CN 522 may include an MME 524, SGW 526, SGSN 528, HSS 530, PGW 532, and PCRF 534 coupled to each other via interfaces (or "reference points") as shown. The functions of the elements of LTE CN 522 may be briefly described as follows.

[0113] The MME 524 may implement mobility management functions to track the current location of the UE 502 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0114] The SGW 526 can terminate the S1 interface towards the RAN and route packets between the RAN and the LTE CN 522. The SGW 526 can be the local mobility anchor for handovers between RAN nodes and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0115] SGSN 528 can track the location of UE 502 and perform security functions and access control. In addition, SGSN 528 can also perform EPC node signaling for mobility between different RAT networks; such as PDN and S-GW selection specified by MME 524; MME selection for handover, etc. The S3 reference point between MME 524 and SGSN 528 can allow user and bearer information exchange for mobility between 3GPP access networks in idle / active states.

[0116] The HSS 530 may include a database of network users (including subscription-related information) to support network entities in handling communication sessions. The HSS 530 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. The S6a reference point between the HSS 530 and the MME 524 may allow the transmission of subscription and authentication data for authenticating / authorizing users to access the LTE CN 520.

[0117] The PGW 532 may terminate the SGi interface, which leads to a data network (DN) 536, which may include application / content servers 538. The PGW 532 may route packets between the LTE CN 522 and the data network 536. The PGW 532 may be coupled to the SGW 526 via an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 532 may also include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 532 and the data network 536 may be, for example, an operator external public network, a dedicated PDN, or an operator internal packet data network for providing IMS services. The PGW 532 may be coupled to the PCRF 534 via a Gx reference point.

[0118] PCRF 534 is the policy and charging control element of LTE CN 522. PCRF 534 may be communicatively coupled with application / content server 538 to determine appropriate QoS and charging parameters for service flows. PCRF 532 may provide association rules along with appropriate TFT and QCI to PCEF (via Gx reference point).

[0119] In some embodiments, CN 520 may be 5GC 540. 5GC 540 may include AUSF 542, AMF 544, SMF 546, UPF 548, NSSF 550, NEF 552, NRF 554, PCF 556, UDM 558 and AF 560 coupled to each other via interfaces (or "reference points") as shown. The functions of the elements of 5GC 540 may be briefly described as follows.

[0120] AUSF 542 may store data for UE 502 authentication and handle authentication-related functions. AUSF 542 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 540 via reference points as shown, AUSF 542 may also present an interface based on Nausf services.

[0121] AMF 544 may enable other functions of 5GC 540 to communicate with UE 502 and RAN 504 and subscribe to notifications about mobility events related to UE 502. AMF 544 may be responsible for registration management (e.g., for registering UE 502), connection management, reachability management, mobility management, legal interception of AMF-related events, and access authentication and authorization. AMF 544 may provide transport for SM messages between UE 502 and SMF 546 and act as a transparent proxy for routing SM messages. AMF 544 may also provide transport for SMS messages between UE 502 and SMSF 546. AMF 544 may interact with AUSF 542 and UE 502 to perform various security anchor and context management functions. In addition, AMF 544 can be the termination point of the RAN CP interface, which can include or be the N2 reference point between RAN 504 and AMF 544; and AMF 544 can be the termination point of NAS (N1) signaling and perform NAS encryption and integrity protection. AMF 544 can also support NAS signaling with UE 502 through the N3 IWF interface.

[0122] SMF 546 may be responsible for SM (e.g., session establishment, tunnel management between UPF 548 and AN 508); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering at UPF 548 to route traffic to the appropriate destination; termination of interfaces toward policy control functions; control of partial policy enforcement, charging, and QoS; lawful interception (for SM events and LI system interfaces); termination of the SM portion of NAS messages; downlink data notification; initiation of AN-specific SM information, which is sent to AN 508 via AMF 544 over N2; and determination of the SSC mode for the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or allows the exchange of PDUs between UE 502 and data network 536.

[0123] The UPF 548 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnecting with the data network 536, and a branch point to support multi-homed PDU sessions. The UPF 548 may also perform packet routing and forwarding, perform packet inspection, execute the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF to QoS traffic mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 548 may include an uplink classifier to support routing of traffic flows to the data network.

[0124] NSSF 550 may select a set of network slice instances to serve UE 502. NSSF 550 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI (if necessary). NSSF 550 may also determine the AMF set or candidate AMF list to be used to serve UE 502 based on appropriate configuration and possibly by querying NRF 554. The selection of a set of network slice instances for UE 502 may be triggered by the AMF 544 with which the UE 502 is registered by interacting with NSSF 550, which may result in a change of AMF. NSSF 550 may interact with AMF 544 via the N22 reference point; and may communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, NSSF 550 may also present an interface based on Nnssf services.

[0125] NEF 552 can securely open the services and capabilities provided by 3GPP network functions to third parties (internal opening / reopening), AFs (such as AF 560), edge computing or fog computing systems, etc. In such embodiments, NEF 552 can authenticate, authorize, or throttle AF. NEF 552 can also convert information exchanged with AF 560 and information exchanged with internal network functions. For example, NEF 552 can convert between AF service identifiers and internal 5GC information. NEF 552 can also receive information from other NFs based on the open capabilities of other NFs. This information can be stored at NEF 552 as structured data, or at a data storage NF using a standardized interface. The stored information can then be reopened by NEF 552 to other NFs and AFs, or used for other purposes such as analysis. In addition, NEF 552 can also present an interface based on Nnef services.

[0126] NRF 554 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 554 also maintains information of available NF instances and the services they support. As used in this disclosure, the terms "instantiate", "instantiation", etc. may refer to the creation of an instance, and "instance" may refer to a specific object that appears, which may appear, for example, during the execution of a program code. In addition, NRF 554 may present an interface based on Nnrf services.

[0127] PCF 556 can provide policy rules to control plane functions to execute them, and can also support a unified policy framework to manage network behavior. PCF 556 can also implement a front end to access subscription information related to policy decisions in the UDR of UDM 558. In addition to communicating with functions through reference points as shown in the figure, PCF 556 also presents an interface based on Npcf services.

[0128] The UDM 558 may process subscription-related information to support network entities that handle communication sessions, and may store subscription data for the UE 502. For example, subscription data may be transmitted between the UDM 558 and the AMF 544 via the N8 reference point. The UDM 558 may include two parts: an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 558 and the PCF 556, and / or store structured data for open and application data (including PFD for application detection, application request information for multiple UEs 502) for the NEF 552. Nudr service-based interfaces may be presented by the UDR 221 to allow the UDM 558, PCF 556, and NEF 552 to access specific stored data sets, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of changes in relevant data in the UDR. The UDM may include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front ends may provide services for the same user in different transactions. UDM-FE accesses subscription information stored in UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, UDM 558 can also present Nudm service-based interfaces.

[0129] The AF 560 can provide application influence on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0130] In some embodiments, 5GC 540 can implement edge computing by selecting an operator / third-party service that is geographically close to the point where UE 502 is attached to the network. This can reduce the latency and load of the network. In order to provide an edge computing implementation, 5GC 540 can select a UPF 548 close to UE 502 and implement traffic orientation from UPF 548 to data network 536 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 560. In this way, AF 560 can affect UPF (re) selection and traffic routing. Depending on the operator's deployment, when AF 560 is regarded as a trusted entity, the network operator can allow AF 560 to interact directly with the relevant NF. In addition, AF 560 can also present an interface based on Naf services.

[0131] The data network 536 may represent various network operator services, Internet access, or third party services, which may be provided by one or more servers including, for example, an application / content server 538 .

[0132] Figure 6 A wireless network 600 is schematically illustrated in accordance with various embodiments. The wireless network 600 may include a UE 602 in wireless communication with an AN 604. The UE 602 and the AN 604 may be similar to and substantially interchangeable with like-named components described elsewhere in this disclosure.

[0133] UE 602 may be communicatively coupled to AN 604 via connection 606. Connection 606 is shown as an air interface to achieve the communicatively coupling and may conform to a cellular communication protocol such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.

[0134] UE 602 may include a host platform 608 coupled to a modem platform 610. Host platform 608 may include application processing circuitry 612, which may be coupled to protocol processing circuitry 614 of modem platform 610. Application processing circuitry 612 may run various applications for UE 602 that are sources / sinks of application data. Application processing circuitry 612 may also implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0135] Protocol processing circuitry 614 may implement one or more of the layer operations to facilitate transmission or reception of data over connection 606. The layer operations implemented by protocol processing circuitry 614 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0136] The modem platform 610 may also include digital baseband circuitry 616 that may implement one or more layer operations that are "lower" layer operations in the network protocol stack that are performed by the protocol processing circuitry 614. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / desmapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time, space-frequency, or spatial coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0137] The modem platform 610 may also include a transmit circuit 618, a receive circuit 620, an RF circuit 622, and an RF front end (RFFE) 624, which may include or be connected to one or more antenna panels 626. In short, the transmit circuit 618 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receive circuit 620 may include an analog-to-digital converter, a mixer, an intermediate frequency component, etc.; the RF circuit 622 may include a low noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 624 may include a filter (e.g., a surface / bulk acoustic wave filter), a switch, an antenna tuner, a beamforming component (e.g., a phased array antenna component), etc. The selection and arrangement of the transmit circuit 618, the receive circuit 620, the RF circuit 622, the RFFE 624, and the antenna panel 626 (collectively referred to as "transmit / receive components") components may be specific to the details of the specific implementation, such as whether the communication is TDM or FDM, whether it is millimeter wave or sub-6gHz frequency, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be provided in the same or different chips / modules, and so on.

[0138] In some embodiments, the protocol processing circuitry 614 may include one or more instances of control circuitry (not shown) to provide control functionality for the transmit / receive components.

[0139] UE reception may be established by and via antenna panel 626, RFFE 624, RF circuitry 622, receive circuitry 620, digital baseband circuitry 616, and protocol processing circuitry 614. In some embodiments, antenna panel 626 may receive transmissions from AN 604 via receive beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 626.

[0140] UE transmissions may be established by and via protocol processing circuitry 614, digital baseband circuitry 616, transmit circuitry 618, RF circuitry 622, RFFE 624, and antenna panel 626. In some embodiments, the transmit component of UE 604 may apply a spatial filter to the data to be transmitted to form a transmit beam that is transmitted by the antenna elements of antenna panel 626.

[0141] Similar to UE 602, AN 604 may include a host platform 628 coupled to a modem platform 630. Host platform 628 may include application processing circuitry 632 coupled to protocol processing circuitry 634 of modem platform 630. The modem platform may also include digital baseband circuitry 636, transmit circuitry 638, receive circuitry 640, RF circuitry 642, RFFE circuitry 644, and antenna panel 646. The components of AN 604 may be similar to and substantially interchangeable with the like-named components of UE 602. In addition to performing data transmission / reception as described above, the components of AN 608 may also perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and packet scheduling.

[0142] Figure 7 is a block diagram showing components according to some exemplary embodiments that are capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing any one or more of the methods discussed in the present disclosure. Specifically, Figure 7 A schematic diagram of hardware resources 700 is shown, which includes one or more processors (or processor cores) 710, one or more memory / storage devices 720, and one or more communication resources 730, each of which can be communicatively coupled via a bus 740 or other interface circuits. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 702 can be implemented to provide an execution environment for one or more network slices / subslices to utilize the hardware resources 700.

[0143] Processor 710 may include, for example, processor 712 and processor 714. Processor 710 may be 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 in the present disclosure), or any suitable combination thereof.

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

[0145] The communication resources 730 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 704 or one or more databases 706 or other network elements via the network 708. For example, the communication resources 730 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, (or Low energy consumption) components, components and other communication components.

[0146] The instructions 750 may include software, a program, an application, an applet, a mobile app, or other executable code for causing at least any one of the processors 710 to perform any one or more of the methods discussed in the present disclosure. The instructions 750 may reside (completely or partially) in at least one of the following: the processor 710 (e.g., in a cache memory of the processor), the memory / storage device 720, or any suitable combination thereof. In addition, any portion of the instructions 750 may be transferred to the hardware resources 700 from any combination of the peripheral device 704 or the database 706. Therefore, the memory of the processor 710, the memory / storage device 720, the peripheral device 704, and the database 706 are examples of computer-readable and machine-readable media.

[0147] Example process

[0148] In some embodiments, Figure 5-Figure 7 Or one or more electronic devices, one or more networks, one or more systems, one or more chips, or one or more components in other figures in the present disclosure, or a part thereof or an implementation thereof may be configured to perform one or more processes, techniques or methods as described in the present disclosure, or a part thereof. Figure 8One such process 800 is depicted. Process 800 may be performed by a UE or a portion thereof. At 802, process 800 may include encoding a plurality of physical random access channels (PRACHs) for transmission in corresponding PRACH moments of a set of PRACH moments. At 804, process 800 may also include determining a random access response (RAR) window associated with the plurality of PRACHs, wherein the RAR window begins after a last PRACH moment of a set of PRACH moments. At 806, process 800 may also include monitoring the RAR in the RAR window. In some embodiments, the last PRACH moment may be the latest PRACH moment in a set of PRACH moments, regardless of whether the corresponding PRACH is canceled or discarded. Alternatively, the last PRACH moment may be the latest PRACH moment in a set of PRACH moments in which the corresponding PRACH is actually transmitted.

[0149] Fig. 9 Another example process 900 is shown in accordance with various embodiments. Process 900 may be performed by a gNB or a portion thereof. At 902, process 900 may include: receiving from a user equipment (UE) a plurality of physical random access channels (PRACHs) in corresponding PRACH moments in a set of PRACH moments. At 904, process 900 may also include: determining a random access response (RAR) window that begins after a last PRACH moment in the set of PRACH moments. At 906, process 900 may also include: encoding a RAR for transmission in the RAR window, wherein the RAR corresponds to a plurality of PRACHs. In some embodiments, the last PRACH moment may be the latest PRACH moment in the set of PRACH moments, regardless of whether the corresponding PRACH is canceled or discarded. Alternatively, the last PRACH may be the latest PRACH in the set of PRACH moments in which the corresponding PRACH is actually transmitted.

[0150] Fig.10Another example process 1000 is shown according to various embodiments. Process 1000 may be performed by a UE or a portion thereof. At 1002, process 1000 may include: encoding a plurality of physical random access channels (PRACHs) for transmission in corresponding PRACH moments in a set of PRACH moments. At 1004, process 1000 may also include: determining a symbol index, a time slot index, and a frequency resource index for calculating a random access (RA)-radio network temporary identification (RNTI) based on a last PRACH moment in a set of PRACH moments. At 1006, process 1000 may also: calculate the RA-RNTI based on the symbol index, the time slot index, and the frequency resource index. In some embodiments, the RA-RNTI may be determined based on one or more (e.g., one, two, or all three) of the symbol index, the time slot index, and the frequency resource index. At 1008, process 1000 may also include monitoring a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) scrambled by the RA-RNTI, wherein the PDCCH corresponds to a random access response (RAR) for multiple PRACHs.

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

[0152] Example

[0153] Some non-limiting examples of various embodiments are provided below.

[0154] Example A1 may include one or more non-transitory computer-readable media (NTCRM) having instructions stored thereon, which, when executed by one or more processors of a user equipment (UE), configure the UE to: encode multiple physical random access channels (PRACHs) for transmission in corresponding PRACH moments of a set of PRACH moments; determine a random access response (RAR) window associated with the multiple PRACHs, wherein the RAR window starts after the last PRACH moment of the set of PRACH moments; and monitor the RAR in the RAR window.

[0155] Example A2 may include one or more NTCRMs according to Example A1, wherein the RAR window starts at the first symbol of an earliest control resource set (CORESET), the UE is configured to receive a physical downlink control channel (PDCCH) on the earliest control resource set, and the PDCCH is located at least one symbol after the last symbol of the last PRACH moment in the set of PRACH moments.

[0156] Example A3 may include one or more NTCRMs according to Example A2, wherein the UE is configured to receive the PDCCH on a CORESET for a Type 1-PDCCH common search space (CSS) set.

[0157] Example A4 may include one or more NTCRMs of Example A3, wherein a symbol duration of the RAR window corresponds to a subcarrier spacing (SCS) for the Type 1-PDCCH CSS set.

[0158] Example A5 may include one or more NTCRMs of Example A2, wherein the last PRACH time instant is used to determine the start of the RAR window regardless of whether the corresponding PRACH transmission is canceled or discarded.

[0159] Example A6 may include one or more NTCRMs according to Example A2, wherein the last PRACH moment corresponds to a latest PRACH moment in the set of PRACH moments, and wherein the corresponding PRACH is actually transmitted at the latest PRACH moment.

[0160] Example A7 may include one or more NTCRMs according to any one of Examples A1-A6, wherein the instruction, when executed, also configures the UE to: determine, based on the last PRACH moment in the set of PRACH moments, a symbol index, a time slot index, and a frequency resource index for calculating a random access (RA)-radio network temporary identifier (RNTI) associated with the RAR; and calculate the RA-RNTI based on the symbol index, the time slot index, and the frequency resource index.

[0161] Example A8 may include one or more NTCRMs according to Example A7, wherein monitoring the RAR includes: monitoring a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC), wherein the cyclic redundancy check (CRC) is scrambled by the calculated RA-RNTI.

[0162] Example A9 may include an apparatus implemented in a user equipment (UE), the apparatus comprising: a memory for storing configuration information for a set of physical random access channel (PRACH) moments; and a processor circuit coupled to the memory, the processor circuit being used to: encode multiple PRACHs for transmission in corresponding PRACH moments in a set of PRACH moments; determine, based on the last PRACH moment in the set of PRACH moments, a symbol index, a time slot index, and a frequency resource index for calculating a random access (RA)-radio network temporary identification (RNTI); calculate the RA-RNTI based on the symbol index, the time slot index, and the frequency resource index; and monitor a physical downlink control channel (PDCCH) with a cyclic redundancy check (CRC), the cyclic redundancy check (CRC) being scrambled with the RA-RNTI, wherein the PDCCH is used to schedule random access responses (RARs) of the multiple PRACHs.

[0163] Example A10 may include an apparatus according to Example A9, wherein the last PRACH moment is the latest PRACH moment in the set of PRACH moments regardless of whether the corresponding PRACH transmission is canceled or discarded.

[0164] Example A11 may include an apparatus according to Example A9, wherein the last PRACH moment corresponds to a latest PRACH moment in the set of PRACH moments, and wherein the corresponding PRACH is actually transmitted at the latest PRACH moment.

[0165] Example A12 may include an apparatus according to any one of Examples A9-A11, wherein the processor circuit is further used to: determine a RAR window associated with the multiple PRACHs, wherein the RAR window starts after the set of PRACH moments, and wherein monitoring the PDCCH is monitoring the RAR in the RAR window.

[0166] Example A13 may include an apparatus according to any one of Examples A9-A12, wherein the RAR window starts at the first symbol of an earliest control resource set (CORESET), and the UE is configured to receive a PDCCH for a Type l-PDCCH common search space (CSS) set on the earliest control resource set, and the PDCCH is at least one symbol after the last symbol of the last PRACH moment in the set of PRACH moments.

[0167] Example A14 may include an apparatus according to Example A13, wherein the symbol duration of the RAR window corresponds to a subcarrier spacing (SCS) for the Type 1-PDCCH CSS set.

[0168] Example A15 may include one or more non-transitory computer-readable media (NTCRM) having instructions stored thereon, which, when executed by one or more processors of a next-generation node B (gNB), configure the gNB to: receive multiple physical random access channels (PRACHs) in corresponding PRACH moments of a set of PRACH moments from a user equipment (UE); determine a random access response (RAR) window starting after a last PRACH moment in the set of PRACH moments; and encode a RAR for transmission in the RAR window, wherein the RAR corresponds to the multiple PRACHs.

[0169] Example A16 may include one or more NTCRMs according to Example A16, wherein the RAR window starts at the first symbol of an earliest control resource set (CORESET), and the UE is configured to receive a physical downlink control channel (PDCCH) for a Type l-PDCCH common search space (CSS) set on the earliest control resource set, and the physical downlink control channel is at least one symbol after the last symbol of the last PRACH moment in the set of PRACH moments.

[0170] Example A17 may include one or more NTCRMs of Example A16, wherein a symbol duration of the RAR corresponds to a subcarrier spacing (SCS) for the Type 1-PDCCH CSS set.

[0171] Example A18 may include one or more NTCRMs according to Example A15, wherein the last PRACH moment is used to determine the start of the RAR window regardless of whether the corresponding PRACH transmission is canceled or discarded; or wherein the last PRACH moment corresponds to the latest PRACH moment in the set of PRACH moments, wherein the corresponding PRACH is actually transmitted at the latest PRACH moment.

[0172] Example A19 may include one or more NTCRMs according to any one of Examples A15-A18, wherein the instructions, when executed, also configure the gNB to: determine a symbol index, a time slot index, or a frequency resource index for calculating a random access (RA)-radio network temporary identifier (RNTI) associated with the RAR based on the last PRACH moment in the set of PRACH moments; and calculate the RA-RNTI based on the symbol index, the time slot index, or the frequency resource index.

[0173] Example A20 may include one or more NTCRMs of Example A19, wherein encoding the RAR comprises encoding the RAR with a cyclic redundancy check (CRC) scrambled by the calculated RA-RNTI.

[0174] Example B1 may include a wireless communication method (e.g., for a fifth generation (5G) or new radio (NR) system), the method comprising: determining, by a UE, a random access response (RAR) window for multiple physical random access channel (PRACH) transmissions; and attempting, by the UE, to decode a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) within the determined RAR window, the cyclic redundancy check (CRC) being scrambled by a random access-radio network temporary identifier (RA-RNTI).

[0175] Example B2 may include a method according to Example B1 or other examples in the present disclosure, wherein the RAR window starts after a last symbol of the last PRACH instant for multiple PRACH transmissions.

[0176] Example B3 may include a method according to Example B2 or other examples in the present disclosure, wherein the RAR window starts at the first symbol of the earliest CORESET, the UE is configured to receive a PDCCH for a Type l-PDCCH CSS set on the earliest CORESET, the PDCCH being located at least one symbol after the last symbol of the last PRACH moment corresponding to the PRACH transmission, wherein the symbol duration corresponds to the SCS for the Type l-PDCCH CSS set.

[0177] Example B4 may include a method according to Example B1 or other examples in the present disclosure, wherein the RAR window starts after the last symbol of the last PRACH instant for multiple PRACH transmissions.

[0178] Example B5 may include a method according to Example B4 or other examples in the present disclosure, wherein the RAR window starts at the first symbol of the earliest CORESET, the UE is configured to receive a PDCCH for a Type l-PDCCH CSS set, the PDCCH being located at least one symbol after the last symbol of the first PRACH moment corresponding to the PRACH transmission, wherein the symbol duration corresponds to the SCS for the Type l-PDCCH CSS set.

[0179] Example B6 may include a method as described in Example B1 or other examples in the present disclosure, wherein the RAR window starts after a last symbol of each PRACH instant for multiple PRACH transmissions.

[0180] Example B7 may include a method according to Example B1 or other examples in the present disclosure, wherein the RAR window starts at the first symbol of the earliest CORESET, the UE is configured to receive a PDCCH for a Typel-PDCCH CSS set on the earliest CORESET, the PDCCH being at least one symbol after the last symbol of each PRACH moment corresponding to the PRACH transmission, wherein the symbol duration corresponds to the SCS for the Type l-PDCCH CSS set.

[0181] Example B8 may include a method according to Example B1 or other examples in the present disclosure, wherein for multiple PRACH transmissions, the symbol index, time slot index, and frequency resource index in the formula for RA-RNTI calculation can be determined based on the first PRACH moment among the multiple PRACH moments.

[0182] Example B9 may include a method according to Example B1 or other examples in the present disclosure, wherein for multiple PRACH transmissions, the symbol index, time slot index and frequency resource index in the formula for RA-RNTI calculation can be determined based on the last PRACH moment among the multiple PRACH moments.

[0183] Example B10 may include a method according to Example B1 or other examples in the present disclosure, wherein for multiple PRACH transmissions, the symbol index, time slot index and frequency resource index in the formula for the RA-RNTI calculation can be determined based on each PRACH moment in the multiple PRACH moments.

[0184] Example B11 may include a method according to example B1 or other examples in the present disclosure, wherein if the random access procedure is initiated by a PDCCH order, then if requested by a higher layer, the UE transmits a PRACH at a selected PRACH time instant, wherein a time between a last symbol received by the PDCCH order and a first symbol of a first PRACH transmission is greater than or equal to N T，2 +Δ BWPSwitching +Δ Delay +T switch millisecond.

[0185] Example B12 may include a method according to Example B1 or other examples in the present disclosure, wherein if the UE is composed of K cell,offsetMultiply by CellSpecific_Koffset, then the first PRACH time is in time slot n+2 μ ·K cell，offset After that, where n is assumed to be T TA =0, the time slot of the UL BWP used for the PRACH transmission, the time slot overlapping with the end of the PDCCH command reception, and μ is the SCS configuration used for the PRACH transmission.

[0186] Example B13 may include a method according to Example B1 or other examples in the present disclosure, wherein the RAR window starts after the last symbol of each PRACH moment in the PRACH moment subset corresponding to the multiple PRACH transmissions; wherein the RAR window starts at the first symbol of the earliest CORESET, and the UE is configured to receive a PDCCH for a Type l-PDCCH CSS set on the earliest CORESET, wherein the PDCCH is at least one symbol after the last symbol of each PRACH moment in the PRACH moment subset corresponding to the PRACH transmission, and wherein the symbol duration corresponds to the SCS for the Type l-PDCCH CSS set.

[0187] Example B14 may include a method according to Example B13 or other examples in the present disclosure, wherein the PRACH time subset may be configured by a higher layer via NR Remaining Minimum System Information (RMST), NR Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling.

[0188] Example B15 may include the method of Example B13 or other examples in the present disclosure, wherein the subset of PRACH moments may be determined based on a number of repetitions for PRACH transmission;

[0189] Example B16 may include a method according to Example B1 or other examples in the present disclosure, wherein the RAR window starts after the last symbol of the PRACH moment for one of the corresponding multiple PRACH transmissions; wherein the RAR window starts at the first symbol of the earliest CORESET, and the UE is configured to receive a PDCCH for a Typel-PDCCH CSS set on the earliest CORESET, and the PDCCH is located at least one symbol after the last symbol of the PRACH moment corresponding to the PRACH transmission, and wherein the symbol duration corresponds to the SCS for the Type l-PDCCH CSS set.

[0190] Example B17 may include a method according to Example B16 or other examples in the present disclosure, wherein the PRACH moment used to determine the RAR monitoring window can be configured by a higher layer via RMSI, OSI or RRC signaling.

[0191] Example B18 may include a method according to Example B16 or other examples in the present disclosure, wherein the PRACH moment can be determined based on the number of repetitions used for PRACH transmission.

[0192] Example B19 may include a method according to Example B1 or other examples in the present disclosure, wherein the first PRACH moment may correspond to the first PRACH moment determined for multiple PRACH transmissions regardless of whether the first PRACH transmission among multiple PRACH transmissions is canceled or discarded.

[0193] Example B20 may include a method according to Example B1 or other examples in the present disclosure, wherein the first PRACH time may correspond to an actual first PRACH transmission among multiple PRACH transmissions.

[0194] Example B21 may include a method according to Example B1 or other examples in the present disclosure, wherein the last PRACH moment may correspond to the last PRACH moment determined for multiple PRACH transmissions regardless of whether the first PRACH transmission among multiple PRACH transmissions is canceled or discarded.

[0195] Example B22 may include a method according to Example B1 or other examples in the present disclosure, wherein the last PRACH time instant may correspond to an actual last PRACH transmission for multiple PRACH transmissions.

[0196] Example B23 may include a method of a user equipment (UE), the method comprising: determining a random access response (RAR) window for multiple physical random access channel (PRACH) transmissions; and monitoring a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) within the determined RAR window, wherein the cyclic redundancy check (CRC) is scrambled by a random access-radio network temporary identifier (RA-RNTI).

[0197] Example B24 may include a method according to Example B23 or other examples in the present disclosure, wherein the RAR window starts after a last symbol of a last PRACH for multiple PRACH transmissions.

[0198] Example B25 may include a method according to Example B24 or other examples in the present disclosure, wherein the RAR window starts at the first symbol of the earliest CORESET, the UE is configured to receive a PDCCH for a Type l-PDCCH common search space (CSS) set on the earliest CORESET, and the PDCCH is located at least one symbol after the last symbol of the last PRACH moment corresponding to the PRACH transmission, wherein the symbol duration corresponds to a subcarrier spacing (SCS) for the Typel-PDCCH CSS set.

[0199] Example B26 may include a method according to Example B23 or other examples in the present disclosure, wherein the RAR window starts after a last symbol of a last PRACH moment for the multiple PRACH transmissions.

[0200] Example B27 may include a method according to Example B26 or other examples in the present disclosure, wherein the RAR window starts at the first symbol of the earliest CORESET, the UE is configured to receive a PDCCH for a Type l-PDCCH CSS set on the earliest CORESET, and the PDCCH is located at least one symbol after the last symbol of the first PRACH moment corresponding to the PRACH transmission, wherein the symbol duration corresponds to the SCS for the Type l-PDCCH CSS set.

[0201] Example B28 may include a method according to Example B23 or other examples in the present disclosure, wherein the RAR window starts after the last symbol of each PRACH moment for the multiple PRACH transmissions.

[0202] Example B29 may include a method according to Example B23 or other examples in the present disclosure, wherein the RAR window starts at the first symbol of the earliest CORESET, the UE is configured to receive a PDCCH for a Type l-PDCCH CSS set on the earliest CORESET, the PDCCH being located at least one symbol after the last symbol of each PRACH moment corresponding to the PRACH transmission, wherein a symbol duration of the first symbol corresponds to the SCS for the Type l-PDCCH CSS set.

[0203] Example B30 may include a method according to Example B23 or other examples in the present disclosure, and further includes: determining a symbol index, a time slot index, and a frequency resource index associated with the RA-RNTI calculation for the multiple PRACH moments based on the first (e.g., earliest) PRACH moment among the multiple PRACH moments.

[0204] Example B31 may include a method according to Example B23 or other examples in the present disclosure, and further include determining a symbol index, a time slot index, and a frequency resource index associated with RA-RNTI calculation for the multiple PRACH moments based on the last PRACH moment among the multiple PRACH moments.

[0205] Example B32 may include a method according to Example B23 or other examples in the present disclosure, and further includes determining a symbol index, a time slot index, and a frequency resource index associated with the RA-RNTI calculation for each of the multiple PRACH moments based on the multiple PRACH moments.

[0206] Example B33 may include a method according to Example B23 or other examples in the present disclosure, wherein the random access procedure is initiated by a PDCCH command, and wherein the method further comprises transmitting a PRACH in a selected PRACH moment, wherein the time between the last symbol received by the PDCCH command and the first symbol of the first PRACH transmission is greater than or equal to N T，2 +Δ BWPSwitching +Δ Delay +T switch millisecond.

[0207] Example B34 may include a method according to Example B23 or other examples in the present disclosure, further including receiving a request for transmitting a PRACH at the selected PRACH time.

[0208] Example B35 may include the method of Example B23 or other examples in the present disclosure, further comprising receiving a value K cell，Offset (eg, via CellSpecific_Koffset), wherein the first (eg, the group-earliest) PRACH instant of the plurality of PRACH instants is in slot n+2 μ ·K cell，offset After that, where n is assumed to be T TA =0, the time slot of the UL BWP used for the PRACH transmission, the time slot overlapping with the end of the PDCCH command reception, and μ is the SCS configuration used for the PRACH transmission.

[0209] Example B36 may include a method according to Example B23 or other examples in the present disclosure, wherein the RAR window starts after the last symbol of each PRACH moment in the subset of PRACH moments used for the corresponding multiple PRACH transmissions.

[0210] Example B37 may include a method according to Example B23, B36 or other examples in the present disclosure, wherein the RAR window starts at the first symbol of the earliest CORESET, the UE is configured to receive a PDCCH for a Type l-PDCCH CSS set in the earliest CORESET, and the PDCCH is located at least one symbol after the last symbol of each PRACH moment in the subset of PRACH moments corresponding to the PRACH transmission, wherein the symbol duration corresponds to the SCS for the Type l-PDCCH CSS set.

[0211] Example B38 may include a method according to Example B23 or other examples in the present disclosure, and also includes receiving configuration information indicating a subset of PRACH moments used for the monitoring.

[0212] Example B39 may include a method according to Example B38 or other examples in the present disclosure, wherein the configuration information is received via NR Remaining Minimum System Information (RMSI), NR Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling.

[0213] Example B40 may include a method according to Examples B23, B38-B39, or other examples in the present disclosure, and further includes determining a subset of PRACH moments for the monitoring based on the number of repetitions used for the PRACH transmission.

[0214] Example B41 may include a method according to Example B23 or other examples in the present disclosure, wherein the RAR window starts after the last symbol of the PRACH moment for the corresponding PRACH transmission in multiple PRACH transmissions, and wherein the RAR window starts from the first symbol of the earliest CORESET, and the UE is configured to receive a PDCCH for a Type l-PDCCH CSS set in the earliest CORESET, and the PDCCH is at least one symbol after the last symbol of the PRACH moment corresponding to the PRACH moment, wherein the symbol duration corresponds to the SCS for the Typel-PDCCH CSS set.

[0215] Example B42 may include a method according to Example B41 or other examples in the present disclosure, wherein the PRACH moment used to determine the RAR window can be configured by a higher layer (e.g., via RMSI, OSI, or RRC signaling).

[0216] Example B43 may include a method according to Example B41 or other examples in the present disclosure, wherein the PRACH moment is determined based on the number of repetitions used for PRACH transmission.

[0217] Example B44 may include a method according to Example B23 or other examples in the present disclosure, wherein the RAR window starts after a first PRACH time determined for the multiple PRACH transmissions regardless of whether the first PRACH transmission is canceled or discarded.

[0218] Example B45 may include a method according to Example B23 or other examples in the present disclosure, wherein the RAR window starts after a first PRACH time instant determined for the multiple PRACH transmissions in which the PRACH is actually transmitted.

[0219] Example B46 may include a method according to Example B23 or other examples in the present disclosure, wherein the RAR window starts after the last PRACH time determined for the multiple PRACH transmissions regardless of whether the last PRACH transmission is canceled or discarded.

[0220] Example B47 may include a method according to Example B23 or other examples in the present disclosure, wherein the RAR window starts after the last PRACH time instant determined for the multiple PRACH transmissions in which PRACH was actually transmitted.

[0221] Example B48 may include a method of a user equipment (UE), the method comprising:

[0222] receiving a request associated with a random access procedure initiated by a physical downlink control channel (PDCCH) command;

[0223] encoding a PRACH for transmission in a selected PRACH moment in which a time between the last symbol received by the PDCCH command and the first symbol of the first PRACH transmission is greater than or equal to N T，2 +Δ BWPSwitching +Δ Delay +T switch millisecond.

[0224] Example B49 may include a method of a user equipment (UE), the method comprising:

[0225] Receive the value K associated with a random access procedure triggered by a physical downlink control channel (PDCCH) command cell，offset instructions; and

[0226] For time slot n+2 μ ·K cell，offset The PRACH transmitted in the subsequent PRACH moment is encoded, where n is the time slot of the UL BWP used for the PRACH transmission, and the time slot overlaps with the tail of the PDCCH command reception, assuming T TA =0, and μ is the SCS configuration used for the PRACH transmission.

[0227] Example Z01 may include an apparatus comprising components arranged to perform one or more elements of a method described in or related to any of Examples A1-A20, B1-B49, or any other method or process described in the present disclosure.

[0228] Example Z02 may include one or more non-transitory computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples A1-A20, B1-B49, or any other method or process described in the present disclosure.

[0229] Example Z03 may include a device comprising logic, modules, or circuits to perform one or more elements of a method described or related to any of Examples A1-A20, B1-B49, or any other method or process described in the present disclosure.

[0230] Example Z04 may include methods, techniques, or processes described or related to any one or a portion of Examples A1-A20, B1-B49.

[0231] Example Z05 may include a device comprising: one or more processors and one or more computer-readable media containing instructions, which, when executed by the one or more processors, cause the one or more processors to perform methods, techniques, or processes described in or related to any one or part of Examples A1-A20, B1-B49.

[0232] Example Z06 may include a signal according to or related to any one or a portion of Examples A1-A20, B1-B49.

[0233] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described or related to any one or part of Examples A1-A20, B1-B49, or otherwise described in the present disclosure.

[0234] Example Z08 can include a signal encoded with data as described or associated with any one or a portion of Examples A1-A20, B1-B49, or otherwise described in this disclosure.

[0235] Example Z09 may include a signal encoded by: a datagram, packet, frame, segment, protocol data unit (PDU), or message described in accordance with or associated with any one or a portion of Examples A1-A20, B1-B49, or otherwise described in the present disclosure.

[0236] Embodiment Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein implementation of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any one or a portion of Examples A1-A20, B1-B49.

[0237] Example Z11 may include a computer program comprising instructions, wherein implementation of the program by a processing element causes the processing element to perform a method, technique, or process described or related to any one or a portion of Examples A1-A20, B1-B49.

[0238] Embodiment Z12 may include signals in a wireless network as shown and described in this disclosure.

[0239] Embodiment Z13 may include a method of communicating in a wireless network as shown and described in this disclosure.

[0240] Example Z14 may include a system for providing wireless communications as shown and described in the present disclosure.

[0241] Example Z15 may include means for providing wireless communications as shown and described in the present disclosure.

[0242] Unless otherwise explicitly stated, any of the above examples may be combined with any other example (or combination of examples). The above description of one or more embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Based on the above teachings, modifications and variations are possible or can be learned by practicing various different embodiments.

[0243] Abbreviations

[0244] Unless used differently in this disclosure, the terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR21.905v16.0.0 (2019-06). For the purposes of this disclosure, the following abbreviations may be applied to the examples and embodiments discussed in this disclosure.

[0245] 3GPP Third Generation Partnership Project

[0246] 4G Fourth Generation

[0247] 5G Fifth Generation

[0248] 5GC 5G Core Network

[0249] AC Application Customers

[0250] ACR Application Context Relocation

[0251] ACK

[0252] ACID Application Client Identity

[0253] AF Application Function

[0254] AM Confirmation Mode

[0255] AMBR Aggregate Maximum Bit Rate

[0256] AMF Access and Mobility Management Function

[0257] AN Access Network

[0258] ANR Automatic Neighbor Relation

[0259] AOA Angle of Arrival

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

[0261] API Application Programming Interface

[0262] APN Access Point Name

[0263] ARP Allocation and Reservation Priority

[0264] ARQ Automatic Repeat Request

[0265] AS Access Layer

[0266] ASP Application Service Provider

[0267] ASN.l Abstract Syntax Notation One

[0268] AUSF authentication server function

[0269] AWGN Additive White Gaussian Noise

[0270] BAP Backhaul Adaptation Protocol

[0271] BCH Broadcast Channel

[0272] BER Bit Error Rate

[0273] BFD Beam Failure Detection

[0274] BLER Block Error Rate

[0275] BPSK Binary Phase Shift Keying

[0276] BRAS Broadband Remote Access Server

[0277] BSS Business Support System

[0278] BS Base Station

[0279] BSR Buffer Status Report

[0280] BW Bandwidth

[0281] BWP Bandwidth Part

[0282] C-RNTI Cell Radio Network Temporary Identifier

[0283] CA operator aggregation, certificate authority

[0284] CBD candidate beam detection

[0285] CAPEX Capital Expenditure

[0286] CBRA Contention Based Access

[0287] CC component carrier, country code, cryptographic checksum

[0288] CCA Clear Channel Assessment

[0289] CCE Control Channel Element

[0290] CCCH Common Control Channel

[0291] CE Coverage Enhancement

[0292] CDM Content Delivery Network

[0293] CDMA Code Division Multiple Access

[0294] CDR Charging Data Request

[0295] CDR charging data response

[0296] CFRA Contention-free random access

[0297] CG Cell Group

[0298] CGF Billing Gateway Function

[0299] CHF billing function

[0300] Cl cell identifier

[0301] CID Cell ID (e.g. positioning method)

[0302] CIM Common Information Model

[0303] CIR Carrier to Interference Ratio

[0304] CK Cryptographic Key

[0305] CM connection management, conditional enforcement

[0306] CMAS Commercial Mobile Alert Service

[0307] CMD command

[0308] CMS Cloud Management System

[0309] CO conditionally optional

[0310] CoMP Coordinated Multipoint

[0311] CORESET Control Resource Set

[0312] COTS Commercial Off-the-Shelf

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

[0314] CPD Connection Point Descriptor

[0315] CPE Customer Premise Equipment

[0316] CPICH Common Pilot Channel

[0317] CQI Channel Quality Indicator

[0318] CPU CSI processing unit, central processing unit

[0319] C / R Command / Response field bit

[0320] CRAN Cloud Radio Access Network, Cloud RAN

[0321] CRB Common Resource Block

[0322] CRC Cyclic Redundancy Check

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

[0324] C-RNTI Cell RNTI

[0325] CS Circuit Switched

[0326] CSCF Call Session Control Function

[0327] CSAR Cloud Service Archives

[0328] CSI Channel State Information

[0329] CSI-IM CSI interference measurement

[0330] CSI-RS CSI reference signal

[0331] CSI-RSRP CSI reference signal received power

[0332] CSI-RSRQ CSI reference signal reception quality

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

[0334] CSMA Carrier Sense Multiple Access

[0335] CSMA / CA CSMA Carrier Sense Multiple Access with Collision Avoidance

[0336] CSS Common Search Space, Cell-Specific Search Space

[0337] CTF Billing Trigger Function

[0338] CTS Clear to Send

[0339] CW codeword

[0340] CWS Contention Window Size

[0341] D2D Device to Device

[0342] DC dual connection, direct current

[0343] DCI Downlink Control Information

[0344] DF deployment style

[0345] DL Downlink

[0346] DMTF Distributed Management Task Force

[0347] DPDK Data Plane Development Kit

[0348] DM-RS, DMRS demodulation reference signal

[0349] DN Data Network

[0350] DNN data network name

[0351] DNAI Data Network Access Identifier

[0352] DRB Data Radio Bearer

[0353] DRS Discovery Reference Signal

[0354] DRX Discontinuous Reception

[0355] DSL Domain Specific Language, Digital Subscriber Line

[0356] DSLAM DSL Access Multiplexer

[0357] DwPTS Downlink Pilot Time Slot

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

[0359] E2E End to End

[0360] EAS Edge Application Server

[0361] ECCA Extended Clear Channel Assessment, Extended CCA

[0362] ECCE Enhanced Control Channel Element, Enhanced CCE

[0363] ED Energy Detection

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

[0365] EAS Edge Application Server

[0366] EASID Edge Application Server Identifier

[0367] ECS Edge Configuration Server

[0368] ECSP Edge Computing Service Provider

[0369] EDN Edge Data Network

[0370] EEC Edge Enabler Client

[0371] EECID Edge Enabler Client Identifier

[0372] EES Edge Enabler Server

[0373] EESID Edge Enabler Server ID

[0374] EHE Edge Hosting Environment

[0375] EGMF Risk Governance Management Functions

[0376] EGPRS Enhanced GPRS

[0377] EIR Equipment Identification Register

[0378] eLAA Enhanced License Assisted Access, enhanced LAA

[0379] EM Element Manager

[0380] eMBB Enhanced Mobile Broadband

[0381] EMS Element Management System

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

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

[0384] EPC Evolved Packet Core

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

[0386] EPRE Energy per resource element

[0387] EPS Evolved Packet System

[0388] EREG Enhanced REG, Enhanced Resource Element Group

[0389] ETSI European Telecommunications Standards Institute

[0390] ETWS Earthquake and Tsunami Early Warning System

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

[0392] E-UTRA Evolved UTRA

[0393] E-UTRAN Evolved UTRAN

[0394] EV2X Enhanced V2X

[0395] F1AP F1 Application Protocol

[0396] Fl-C F1 control plane interface

[0397] F1-U F1 User Plane Interface

[0398] FACCH Fast Associated Control Channel

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

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

[0401] FACH Forward Access Channel

[0402] FAUSCH Fast Uplink Signalling Channel

[0403] FB Function Block

[0404] FBI Feedback

[0405] FCC Federal Communications Commission

[0406] FCCH Frequency Correction Channel

[0407] FDD Frequency Division Duplex

[0408] FDM Frequency Division Multiplexing

[0409] FDMA Frequency Division Multiple Access

[0410] FE Front End

[0411] FEC Forward Error Correction

[0412] FFS for further study

[0413] FFT Fast Fourier Transform

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

[0415] FN Frame Number

[0416] FPGA Field Programmable Gate Array

[0417] FR Frequency Range

[0418] FQDN Fully Qualified Domain Name

[0419] G-RNTI GERAN Radio Network Temporary Identity

[0420] GGERAN GSM EDGE RAN, GEM EDGE Radio Access Network

[0421] GGSN Gateway GPRS Support Node

[0422] GLONASS Global Navigation Satellite System

[0423] gNB Next Generation NodeB

[0424] gNB-CU gNB-centralized unit, next generation NodeB centralized unit

[0425] gNB-DU gNB-distributed unit, next generation NodeB distributed unit

[0426] GNSS Global Navigation Satellite System

[0427] GPRS General Packet Radio Service

[0428] GPSI General Public Subscription Identifier

[0429] GSM Global System for Mobile Communications, Mobile Task Force

[0430] GTP GPRS Tunneling Protocol

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

[0432] GTS enters sleep signal (related to WUS)

[0433] GUMMEI Globally Unique MME Identifier

[0434] GUTI Globally Unique Temporary UE Identifier

[0435] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

[0436] HANDO Switch HFN, HyperFrame number

[0437] HHO Hard Handover

[0438] HLR Home Location Register

[0439] HN Home Network

[0440] HO Switchover

[0441] HPLMN Home Public Land Mobile Network

[0442] HSDPA High Speed ​​Downlink Packet Access

[0443] HSN Hopping Sequence Number

[0444] HSPA High Speed ​​Packet Access

[0445] HSS Home Subscriber Server

[0446] HSUPA High Speed ​​Uplink Packet Access

[0447] HTTP Hypertext Transfer Protocol

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

[0449] I-Block Information Block

[0450] ICCID Integrated Circuit Card Identification

[0451] IAB Integrated Access and Backhaul

[0452] ICIC Inter-cell Interference Cooperation

[0453] ID, identifier

[0454] IDFT Inverse Discrete Fourier Transform

[0455] IE Information Elements

[0456] IBE In-Band Emission

[0457] IEEE Institute of Electrical and Electronics Engineers

[0458] IEI Information Element Identifier

[0459] IEIDL Information Element Identifier Data Length

[0460] IETF Internet Engineering Task Force

[0461] IF Infrastructure

[0462] IIOT Industrial Internet of Things

[0463] IM Interference Measurement, Intermodulation, IP Multimedia

[0464] IMC IMS Certificate

[0465] IMEI International Mobile Equipment Identity

[0466] IMGI International Mobile Group Identity

[0467] IMPI IP Multimedia Special Identifier

[0468] IMPU IP Multimedia Public Identity

[0469] IMS IP Multimedia Subsystem

[0470] IMSI International Mobile Subscriber Identity

[0471] IoT

[0472] IP Internet Protocol

[0473] Ipsec IP security, Internet Protocol security

[0474] IP-CAN IP-Connection Access Network

[0475] IP-M IP Multicast

[0476] IPv4 Internet Protocol version 4

[0477] IPv6 Internet Protocol Version 6

[0478] IR

[0479] IS Synchronization

[0480] IRP Integration Reference Point

[0481] ISDN Integrated Services Digital Network

[0482] ISIM IM Service Identity Module

[0483] ISO International Organization for Standardization

[0484] ISP Internet Service Provider

[0485] IWF interworking function

[0486] I-WLAN Intercommunication WLAN

[0487] Constraint length of convolutional code, USIM

[0488] Separate key

[0489] kB kilobyte (1000 bytes)

[0490] kbps kilobits per second

[0491] Kc encryption key

[0492] Ki Individual subscriber authentication key

[0493] KPI Key Performance Indicator

[0494] KQI Key Quality Indicator

[0495] KSI Key Setting Identifier

[0496] ksps kilosymbols per second

[0497] KVM Kernel Virtual Machine

[0498] L1 Layer 1 (physical layer)

[0499] Ll-RSRP Layer 1 reference signal received power

[0500] L2 Layer 2 (Data Link Layer)

[0501] L3 Layer 3 (Network Layer)

[0502] LAA Licensed Assisted Access

[0503] LAN Local Area Network

[0504] LADN Local Area Data Network

[0505] LBT Listen before you speak

[0506] LCM Life Cycle Management

[0507] LCR Low Chip Rate

[0508] LCS Location Services

[0509] LCID Logical Channel ID

[0510] LI layer indicator

[0511] LLC Logical Link Control, Low Layer Compatibility

[0512] LMF Location Management Function

[0513] LOS Line of Sight

[0514] LPLMN Local PLMN

[0515] LPP LTE Positioning Protocol

[0516] LSB Least Significant Bit

[0517] LTE Long Term Evolution

[0518] LWA LTE-WLAN Aggregation

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

[0520] LTE Long Term Evolution

[0521] M2M Machine to Machine

[0522] MAC Media Access Control (Protocol Layer Context)

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

[0524] MAC-A MAC for authentication and key protocols (TSG TWG3 context) and MAC-IMAC for data integrity of signaling messages (TSG TWG3 context)

[0525] MANO Management and Orchestration

[0526] MBMS Multimedia Broadcast and Multicast Service

[0527] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0528] MCC Mobile Country Code

[0529] MCG Master Unit Group

[0530] MCOT Maximum Channel Occupancy Time

[0531] MCS Modulation and Coding Scheme

[0532] MDAF Management Data Analysis Function

[0533] MDAS Management Data Analysis Service

[0534] MDT Minimized Drive Testing ME Mobile Device

[0535] MeNB master eNB MER message error rate

[0536] MGL Measurement Gap Length

[0537] MGRP Measurement Gap Repetition Period

[0538] MIB Master Information Block, Management Information Base

[0539] MIMO Multiple Input Multiple Output

[0540] MLC Mobile Location Center

[0541] MM Mobility Management

[0542] MME Mobility Management Entity

[0543] MN Master Node

[0544] MNO Mobile Network Operator

[0545] MO measurement object, mobile origination

[0546] MPBCH MTC Physical Broadcast Channel

[0547] MPDCCH MTC Physical Downlink Control Channel

[0548] MPDSCH MTC Physical Downlink Shared Channel

[0549] MPRACH MTC Physical Random Access Channel

[0550] MPUSCH MTC Physical Uplink Shared Channel

[0551] MPLS Multiprotocol Label Switching

[0552] MS Mobile Station

[0553] MSB Most Significant Bit

[0554] MSC Mobile Switching Center

[0555] MSI minimum system information, MCH scheduling information

[0556] MSID Mobile Station Identifier

[0557] MSIN Mobile Station Identification Number

[0558] MSISDN Mobile Subscriber ISDN Number

[0559] MT Mobile Terminated, Mobile Terminated

[0560] MTC Machine Type Communication

[0561] mMTC Massive MTC, Massive Machine Type Communication

[0562] MU-MIMO Multi-User MIMO

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

[0564] NACK Negative Acknowledgement

[0565] NAI Network Access Identifier

[0566] NAS non-access layer (layer), non-access layer (stratum layer)

[0567] NCT Network Connection Topology

[0568] NC-JT Non-coherent joint transmission

[0569] NEC network capabilities exposed

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

[0571] NEF Network Exposure Function

[0572] NF Network Function

[0573] NFP Network Forwarding Path

[0574] NFPD Network Forwarding Path Descriptor

[0575] NFV Network Function Virtualization

[0576] NFVI NFV Infrastructure

[0577] NFVO NFV Orchestrator

[0578] NG Next Generation, Next Gen

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

[0580] NM Network Manager

[0581] NMS Network Management System

[0582] N-PoP Network Point of Presence

[0583] NMIB, N-MIB Narrowband MIB

[0584] NPBCH Narrowband Physical Broadcast Channel

[0585] NPDCCH Narrowband Physical Downlink Control Channel

[0586] NPDSCH Narrowband Physical Downlink Shared Channel

[0587] NPRACH Narrowband Physical Random Access Channel

[0588] NPUSCH Narrowband Physical Uplink Shared Channel

[0589] NPSS Narrowband Primary Synchronization Signal

[0590] NSSS Narrowband Secondary Synchronization Signal

[0591] NR New Radio, Neighbor Relations

[0592] NRF NF Repository Functionality

[0593] NRS Narrowband Reference Signal

[0594] NS Network Services

[0595] NSA Non-standalone operation mode

[0596] NSD Network Service Descriptor

[0597] NSR Network Service Record

[0598] NSSAI Network Slice Selection Assistance Information

[0599] S-NNSAI Single NSSAI

[0600] NSSF network slice selection function

[0601] NW Network

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

[0603] NZP Non Zero Power

[0604] O&M Operation and Maintenance

[0605] ODU2 Optical Channel Data Unit - Type 2

[0606] OFDM Orthogonal Frequency Division Multiplexing

[0607] OFDMA Orthogonal Frequency Division Multiple Access

[0608] OOB Out of Band

[0609] OOS Out of Sync

[0610] OPEX Operating Expenses

[0611] OSI Other System Information

[0612] OSS Operation Support System

[0613] OTA

[0614] PAPR Peak-to-Average Power Ratio

[0615] PAR Peak to Average Ratio

[0616] PBCH Physical Broadcast Channel

[0617] PC Power Control, Personal Computer

[0618] PCC Primary Component Carrier, Primary CC

[0619] P-CSCF Proxy CSCF

[0620] Pcell Primary cell

[0621] PCI Physical Cell ID, Physical Cell Identifier

[0622] PCEF Policy and Charging Enforcement Function

[0623] PCF Policy Control Function

[0624] PCRF Policy Control and Charging Rules Function

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

[0626] PDCCH Physical Downlink Control Channel

[0627] PDCP Packet Data Convergence Protocol

[0628] PDN Packet Data Network, Public Data Network

[0629] PDSCH Physical Downlink Shared Channel

[0630] PDU Protocol Data Unit

[0631] PEI Persistent Equipment Identifier

[0632] PFD Packet Flow Description

[0633] P-GW PDN Gateway

[0634] PHICH Physical Hybrid ARQ Indicator Channel

[0635] PHY Physical Layer

[0636] PLMN Public Land Mobile Network

[0637] PIN Personal Identification Number

[0638] PM performance measurement

[0639] PMI Precoding matrix indicator

[0640] PNF Physical Network Function

[0641] PNFD Physical Network Functional Descriptor

[0642] PNFR Physical Network Function Record

[0643] PTT over POC cellular network

[0644] PP, PTP point to point

[0645] PPP Point-to-Point Protocol

[0646] PRACH Physical RACH

[0647] PRB Physical Resource Block

[0648] PRG Physical Resource Group

[0649] ProSe proximity services, proximity-based services

[0650] PRS Positioning Reference Signal

[0651] PRR Packet Receive Radio

[0652] PS Packet Service

[0653] PSBCH Physical Sidelink Broadcast Channel

[0654] PSDCH Physical Sidelink Downlink Channel

[0655] PSCCH Physical Sidelink Control Channel

[0656] PSSCH Physical Sidelink Shared Channel

[0657] PSFCH Physical Sidelink Feedback Channel

[0658] PSCell Primary SCell

[0659] PSS Primary Synchronization Signal

[0660] PSTN Public Switched Telephone Network

[0661] PT-RS Phase Tracking Reference Signal

[0662] PTT Push to Talk

[0663] PUCCH Physical Uplink Control Channel

[0664] PUSCH Physical Uplink Shared Channel

[0665] QAM Quadrature Amplitude Modulation

[0666] QCI QoS Class Identifier

[0667] QCL Quasi-Co-sited

[0668] QFI QoS flow ID, QoS flow identifier

[0669] QoS Quality of Service

[0670] QPSK Quadrature (Quaternary) Phase Shift Keying

[0671] QZSS Quasi-Zenith Satellite System

[0672] RA-RNTI Random Access RNTI

[0673] RAB Radio Access Bearer, Random Access Burst

[0674] RACH Random Access Channel

[0675] RADIUS Remote Authentication Dial-In User Service

[0676] RAN Radio Access Network

[0677] RAND Random number (for authentication)

[0678] RAR Random Access Response

[0679] RAT Radio Access Technology

[0680] RAU Routing Area Update

[0681] RB Resource Block, Radio Bearer

[0682] RBG Resource Block Group

[0683] REG Resource Element Group

[0684] Rel release version

[0685] REQ REQuest

[0686] RF

[0687] RI Rank Indicator

[0688] RIV Resource Indicator Value

[0689] RL Radio Link

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

[0691] RLC AM RLC Acknowledgement Mode

[0692] RLC UM RLC Unacknowledged Mode

[0693] RLF Radio Link Failure

[0694] RLM Radio Link Monitoring

[0695] RLM-RS RLM reference signal

[0696] RM Registration Management

[0697] RMC Reference Measurement Channel

[0698] RMSI Remaining MSI, Remaining Minimum System Information

[0699] RN Relay Node

[0700] RNC Radio Network Controller

[0701] RNL Radio Network Layer

[0702] RNTI Radio Network Temporary Identifier

[0703] ROHC Robust Header Compression

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

[0705] RRM Radio Resource Management

[0706] RS reference signal

[0707] RSRP Reference Signal Received Power

[0708] RSRQ Reference Signal Received Quality

[0709] RSSI Received Signal Strength Indicator

[0710] RSU Roadside Unit

[0711] RSTD Reference Signal Time Difference

[0712] RTP Real Time Protocol

[0713] RTS Ready to send

[0714] RTT Round Trip Time

[0715] Rx receiving, receiving, receiver

[0716] S1AP S1 Application Protocol

[0717] S1-MME is used for control plane

[0718] S1-U S1 for user plane

[0719] S-CSCF Serving CSCF

[0720] S-GW Service Gateway

[0721] S-RNTI SRNC Radio Network Temporary Identifier

[0722] S-TMSI SAE Temporary Mobile Site Identifier

[0723] SA Standalone Operation Mode

[0724] SAE system architecture evolution

[0725] SAP Service Access Point

[0726] SAPD Service Access Point Descriptor

[0727] SAPI Service Access Point Identifier

[0728] SCC Secondary Component Carrier, Secondary CC

[0729] Scell

[0730] SCEF Service Capability Exposure Function

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

[0732] SCG Secondary Cell Group

[0733] SCM Security Context Management

[0734] SCS subcarrier spacing

[0735] SCTP Stream Control Transmission Protocol

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

[0737] SDL Supplemental Downlink

[0738] SDNF Structured Data Storage Network Function

[0739] SDP Session Description Protocol

[0740] SDSF structured data storage function

[0741] SDT Small Data Transfer

[0742] SDU Service Data Unit

[0743] SEAF safety anchor function

[0744] SeNB Secondary eNB

[0745] SEPP Security Edge Protection Proxy

[0746] SFI Slot Format Indicator

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

[0748] SFN System Frame Number

[0749] SgNB Secondary gNB

[0750] SGSN Serving GPRS Support Node

[0751] S-GW Service Gateway

[0752] SI System Information

[0753] SI-RNTI System Information RNTI

[0754] SIB System Information Block

[0755] SIM Subscriber Identity Module

[0756] SIP Session Initiation Protocol

[0757] System in a SiP Group

[0758] SL Side Link

[0759] SLA Service Level Agreement

[0760] SM Session Management

[0761] SMF session management functions

[0762] SMS Short Message Service

[0763] SMSF SMS Function

[0764] SMTC SSB-based measurement timing configuration

[0765] SN Secondary node, serial number

[0766] SoC System on Chip

[0767] SON Self-Organizing Network

[0768] SpCell Dedicated Cell

[0769] SP-CSI-RNTI Semi-Permanent CSI-RNTI

[0770] SPS Semi-Permanent Scheduling

[0771] SQN Serial Number

[0772] SR Scheduling Request

[0773] SRB Signalling Radio Bearer

[0774] SRS Sounding Reference Signal

[0775] SS Sync Signal

[0776] SSB Synchronous Signal Block

[0777] SSID Service Set Identifier

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

[0779] SSC Session and Service Continuity

[0780] SS-RSRP Synchronization signal based on reference signal received power

[0781] SS-RSRQ Synchronization signal based on reference signal reception quality

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

[0783] SSS Secondary sync signal

[0784] SSSG Search Space Group

[0785] SSSIF Search Space Set Indicator

[0786] SST Slice / Service Type

[0787] SU-MIMO Single User MIMO

[0788] SUL Supplementary Uplink

[0789] TA Timing Advance, Tracking Area

[0790] TAC Tracking Area Code

[0791] TAG Timing Advance Group

[0792] TAI Tracking Area Identifier

[0793] TAU Tracking Area Updates

[0794] TB Transfer Block

[0795] TBS Transport Block Size

[0796] TBD

[0797] TCI Transmission Configuration Indicator

[0798] TCP transport communication protocol

[0799] TDD Time Division Duplex

[0800] TDM Time Division Multiplexing

[0801] TDMA Time Division Multiple Access

[0802] TE Terminal Equipment

[0803] TEID Tunnel Endpoint Identifier

[0804] TFT Business Flow Template

[0805] TMSI Temporary Mobile Subscriber Identity

[0806] TNL Transport Network Layer

[0807] TPC Transmit Power Control

[0808] TPMI transmitted precoding matrix indicator

[0809] TR Technical Report

[0810] TRP, TRxP Transmission Receive Point

[0811] TRS Tracking Reference Signal

[0812] TRx Transceiver

[0813] TS Technical Specifications, Technical Standards

[0814] TTI Transmission Time Interval

[0815] Tx Transmitting, Transmitting, Transmitter

[0816] U-RNTI UTRAN Radio Network Temporary Identity

[0817] UART Universal Asynchronous Receiver and Transmitter

[0818] UCI Uplink Control Information

[0819] UE User Equipment

[0820] UDM Unified Data Management

[0821] UDP User Datagram Protocol

[0822] UDSF Unstructured Data Storage Network Function

[0823] UICC Universal Integrated Circuit Card

[0824] UL Uplink

[0825] UM Unconfirmed Mode

[0826] UML Unified Modeling Language

[0827] UMTS Universal Mobile Telecommunications System

[0828] UP User Plane

[0829] UPF User Plane Function

[0830] URI Uniform Resource Identifier

[0831] URL Uniform Resource Locator

[0832] URLLC Ultra-Reliable Low Latency

[0833] USB Universal Serial Bus

[0834] USIM Universal Subscriber Identity Module

[0835] USS UE-specific search space

[0836] UTRA UMTS Terrestrial Radio Access

[0837] UTRAN Universal Terrestrial Radio Access Network

[0838] UwPTS Uplink Pilot Time Slot

[0839] V2I Vehicle to Infrastructure

[0840] V2P Vehicle to Pedestrian

[0841] V2V Vehicle to Vehicle

[0842] V2X Vehicle to Everything

[0843] VIM Virtualization Infrastructure Manager

[0844] VL Virtual Link

[0845] VLAN Virtual LAN, Virtual Local Area Network

[0846] VM Virtual Machine

[0847] VNF Virtualized Network Function

[0848] VNFFG VNF forwarding graph

[0849] VNFFGD VNF Forwarding Graph Descriptor

[0850] VNFM VNF Manager

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

[0852] VPLMN Visited Public Land Mobile Network

[0853] VPN Virtual Private Network

[0854] VRB Virtual Resource Block

[0855] WiMAX Worldwide Interoperability for Microwave Access

[0856] WLAN Wireless Local Area Network

[0857] WMAN Wireless Metropolitan Area Network

[0858] WPAN Wireless Personal Area Network

[0859] X2-C X2 control plane

[0860] X2-U X2 user plane

[0861] XML Extensible Markup Language

[0862] XRES Expected User Response

[0863] XOR

[0864] ZC Zadov-First

[0865] ZP Zero Power

[0866] the term

[0867] For the purposes of this disclosure, the following terms and definitions apply to the examples and embodiments discussed in this disclosure.

[0868] The term "application" can refer to a complete and deployable software package or environment that implements a certain function in an operating environment. The term "AI / ML application" can refer to an application that contains some AI / ML models and application-level descriptions.

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

[0870] The term "processor circuit" as used in the present disclosure refers to the following circuit or a part thereof, or includes the following circuit: the circuit is capable of automatically performing a series of arithmetic or logical operations in sequence, or recording, storing and / or transmitting digital data. The processing circuit may include one or more processing cores for implementing instructions, and one or more memory structures for storing program and data information. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor and / or any other device that can implement or otherwise operate computer executable instructions (such as program code, software modules and / or functional processes). The processing circuit may include more hardware accelerators that may be microprocessors, programmable processing devices, etc. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may therefore also be referred to as "processor circuit".

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

[0872] The term "user equipment" or "UE" as used in the present disclosure refers to a device with wireless communication capabilities and can describe a remote user of network resources in a communication network. The term "user equipment" or "UE" can be considered synonymous with or refer to the following items: client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable wireless device, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" can include: any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0873] The term "network element" as used in this disclosure refers to a physical or virtualized device and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or refer to the following items: a networked computer, networking hardware, a network device, a network node, a router, a switch, a hub, a bridge, a radio network controller, a RAN device, a RAN node, a gateway, a server, a virtualized VNF, a NFVI, etc.

[0874] The term "computer system" as used in this disclosure refers to any type of interconnected electronic devices, computer devices, or components thereof. In addition, the terms "computer system" and / or "system" may refer to various components in a computer that are communicatively coupled to each other. In addition, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or network resources.

[0875] As used in this disclosure, the terms "device", "computer device", etc. refer to a computer device or computer system with program code (such as software or firmware) that is dedicated to providing specific computing resources. A "virtual device" is a virtual machine image implemented by a device equipped with a hypervisor that virtualizes or emulates a computer device or is otherwise dedicated to providing specific computing resources.

[0876] The term "resource" as used in the present disclosure refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, power, input / output operations, a port or network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a workload unit, etc. "Hardware resources" may refer to computing, storage and / or network resources provided by one or more physical hardware elements. "Virtualized resources" may refer to computing, storage and / or network resources provided by a virtualization infrastructure to an application, device, system, etc. The term "network resource" or "communication resource" may refer to a resource accessible by a computer device / system via a communication network. The term "system resource" may refer to any type of shared entity that provides a service, and may include computing resources and / or network resources. System resources may be viewed as a set of coherent functions, network data objects, or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

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

[0878] The terms "instantiate", "instantiation" and the like used in this disclosure refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, such as that which may occur during the execution of program code.

[0879] The terms "coupled," "communicatively coupled," and their derivatives are used in this disclosure. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other, but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by means of communication, including through wires or other interconnecting connections, through wireless communication channels or links, etc.

[0880] The term "information unit" refers to a structural unit containing one or more fields. The term "field" refers to a single content of an information unit or a data unit containing content.

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

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

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

[0884] The term "primary SCG cell" refers to an SCG cell to which a UE performs random access when performing reconfiguration with a synchronization procedure for DC operation.

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

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

[0887] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and has only one serving cell consisting of the primary cell.

[0888] The term "serving cell" or "cells" refers to a group of cells including the dedicated cell(s) and all secondary cells for a UE in RRC-CONNECTED configured with CA / .

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

[0890] The term "machine learning" or "ML" refers to the use of computer systems to implement algorithms and / or statistical models to perform one or more specific tasks without the use of explicit instructions, but relying on patterns and reasoning. ML algorithms build or estimate one or more mathematical models (called "ML models", etc.) based on sample data (called "training data", "model training information", etc.) to make predictions or decisions without being explicitly programmed to perform such tasks. In general, ML algorithms are computer programs that learn from experience with some tasks and some performance measures, while "ML" models can be any object or data structure created after training a machine learning algorithm with one or more training data sets. After training, ML models can be used to make predictions on new data sets. Although the term "ML algorithm" refers to a different concept from the term "ML model", for the purposes of this disclosure, these terms discussed in this disclosure can be used interchangeably.

[0891] The terms "machine learning model", "ML model", etc. may also refer to ML methods and concepts used by ML-assisted solutions. "ML-assisted solutions" are solutions that use ML algorithms to solve specific use cases during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor method (KNN), decision tree algorithm, support machine vector, Bayesian algorithm, ensemble algorithm, etc.), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA)), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, etc. According to an embodiment, a specific ML model may have many sub-models as components, and the ML model may train all sub-models together. During inference, separately trained ML models may also be connected in series in an ML circuit. An ML circuit may include one or more data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and participants. "Participant" refers to an entity that hosts an ML-assisted solution using the inference output of an ML model). The term "ML training host" refers to an entity (such as a network function) that hosts model training. The term "ML inference host" refers to the entity (such as a network function) that hosts the model during inference mode (which includes model implementation and any online learning (if applicable)). The ML host informs the participants of the output of the ML algorithm, and the participants make decisions about actions (participants perform "actions" based on the output of the ML assistance scheme). The term "model inference information" refers to the information used as input to the ML model to determine inferences; the data used to train the ML model and the data used to determine inferences can overlap, however, "training data" and "inference data" refer to different concepts.

Claims

1. One or more non-transitory computer readable media (NTCRM) having instructions stored thereon, which when executed by one or more processors of a user equipment (UE), configure the UE to: encoding a plurality of physical random access channels (PRACHs) for transmission in corresponding PRACH moments of a set of PRACH moments; determining a random access response (RAR) window associated with the plurality of PRACHs, wherein the RAR window starts after a last PRACH time instant of the set of PRACH time instants; as well as Monitor the RAR in the RAR window.

2. One or more NTCRMs according to claim 1, wherein: The RAR window starts from the first symbol of the earliest control resource set (CORESET), and the UE is configured to receive a physical downlink control channel (PDCCH) on the earliest control resource set (CORESET), and the physical downlink control channel is located at least one symbol after the last symbol of the last PRACH moment in the set of PRACH moments.

3. One or more NTCRMs according to claim 2, wherein: The UE is configured to receive a PDCCH on a CORESET for a Type 1-PDCCH common search space (CSS) set.

4. One or more NTCRMs according to claim 3, wherein: The symbol duration of the RAR window corresponds to a subcarrier spacing (SCS) for the Type 1-PDCCH CSS set.

5. One or more NTCRMs according to claim 2, wherein: Regardless of whether the corresponding PRACH transmission is cancelled or discarded, the last PRACH time is used to determine the start of the RAR window.

6. One or more NTCRMs according to claim 2, wherein: The last PRACH moment corresponds to the latest PRACH moment in the group of PRACH moments, wherein the corresponding PRACH is actually transmitted at the latest PRACH moment.

7. One or more NTCRMs according to any one of claims 1-6, wherein: When the instructions are executed, the UE is further configured to: Determining, based on a last PRACH moment in the set of PRACH moments, a symbol index, a time slot index, and a frequency resource index for calculating a random access (RA)-radio network temporary identifier (RNTI) associated with the RAR; and An RA-RNTI is calculated based on the symbol index, the time slot index and the frequency resource index.

8. One or more NTCRMs according to claim 7, wherein: Monitoring the RAR includes monitoring a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) scrambled by the calculated RA-RNTI.

9. An apparatus implemented in a user equipment (UE), the apparatus comprising: A memory for storing configuration information for a set of physical random access channel (PRACH) moments; as well as a processor circuit coupled to the memory, the processor circuit being configured to: encoding a plurality of PRACHs for transmission in corresponding PRACH moments in a set of PRACH moments; Determining, according to a last PRACH moment in the set of PRACH moments, a symbol index, a time slot index, and a frequency resource index for calculating a random access (RA)-radio network temporary identifier (RNTI); Calculate the RA-RNTI based on the symbol index, the time slot index and the frequency resource index; as well as monitoring a physical downlink control channel (PDCCH) having a cyclic redundancy check (CRC) scrambled with the RA-RNTI, The PDCCH is used to schedule random access responses (RARs) of the multiple PRACHs.

10. The device according to claim 9, wherein: No matter whether the corresponding PRACH transmission is cancelled or discarded, the last PRACH moment is the latest PRACH moment in the set of PRACH moments.

11. The device according to claim 9, wherein: The last PRACH moment corresponds to a latest PRACH moment in the group of PRACH moments, wherein the corresponding PRACH is actually transmitted at the latest PRACH moment.

12. The device according to any one of claims 9 to 11, wherein: The processor circuit is further configured to: A RAR window associated with the plurality of PRACHs is determined, wherein the RAR window starts after the set of PRACH time instants, wherein monitoring the PDCCH is monitoring the RAR in the RAR window.

13. The device according to claim 12, wherein: The RAR window starts from the first symbol of the earliest control resource set (CORESET), and the UE is configured to receive a PDCCH for a Type l-PDCCH common search space (CSS) set on the earliest control resource set (CORESET), and the PDCCH is located at least one symbol after the last symbol of the last PRACH moment in the group of PRACH moments.

14. The device according to claim 13, wherein: The symbol duration of the RAR window corresponds to a subcarrier spacing (SCS) for the Type 1-PDCCH CSS set.

15. One or more non-transitory computer readable media (NTCRM) having instructions stored thereon, which when executed by one or more processors of a next generation Node B (gNB), configure the gNB to: receiving, from a user equipment (UE), a plurality of physical random access channels (PRACHs) in corresponding PRACH moments of a set of PRACH moments; determining a random access response (RAR) window starting after a last PRACH time instant of the set of PRACH time instants; and A RAR is encoded for transmission in the RAR window, wherein the RAR corresponds to the plurality of PRACHs.

16. One or more NTCRMs according to claim 16, wherein: The RAR window starts from the first symbol of the earliest control resource set (CORESET), and the UE is configured to receive a physical downlink control channel (PDCCH) for a Type l-PDCCH common search space (CSS) set on the earliest control resource set, and the physical downlink control channel is located at least one symbol after the last symbol of the last PRACH moment in the set of PRACH moments.

17. One or more NTCRMs according to claim 16, wherein: The symbol duration of the RAR corresponds to a subcarrier spacing (SCS) used for the Type 1-PDCCH CSS set.

18. The one or more NTCRMs of claim 15, wherein: Regardless of whether the corresponding PRACH transmission is cancelled or discarded, the last PRACH time is used to determine the start of the RAR window; or The last PRACH moment corresponds to the latest PRACH moment in the group of PRACH moments, and the corresponding PRACH is actually transmitted at the latest PRACH moment.

19. One or more NTCRMs according to any one of claims 15-18, wherein: The instructions, when executed, further configure the gNB to: Determining a symbol index, a time slot index, or a frequency resource index for calculating a random access (RA)-radio network temporary identifier (RNTI) associated with the RAR based on a last PRACH time in the set of PRACH time; and The RA-RNTI is calculated based on the symbol index, the time slot index or the frequency resource index.

20. One or more NTCRMs according to claim 19, wherein: Encoding the RAR includes encoding the RAR with a cyclic redundancy check (CRC), the cyclic redundancy check (CRC) being scrambled by the calculated RA-RNTI.

Images