Grant-free uplink transmission for new radio

Abstract

The present disclosure relates to grant-free uplink transmissions for new radio. Current methods of transmitting uplink data in a network generally require licensed resources. In an example, a node or apparatus can configure a plurality of devices to operate in a grant-free mode in accordance with a respective grant-free access allocation, such that when the plurality of devices transmit messages in the uplink in the network, the messages are transmitted using frequency resources defined by the respective grant-free access allocation, and the plurality of devices transmit the messages without transmitting the messages using a licensed access, such that the plurality of devices operate in the grant-free mode.

Description

[0001] This application is a continuation of International Application No. PCT / US2017 / 037693, entitled "Grant-Free Uplink Transmission for New Radio," filed June 15, 2017, and claiming priority to U.S. Patent Application No. 201780049898.3, filed June 15, 2016.

[0002] Cross Reference to Related Applications

[0003] This application claims the benefit of priority to U.S. Provisional Patent Application No. 62 / 350,550, filed June 15, 2016, U.S. Provisional Patent Application No. 62 / 373,691, filed August 11, 2016, U.S. Provisional Patent Application No. 62 / 399,921, filed September 26, 2016, and U.S. Provisional Patent Application No. 62 / 401,062, filed September 28, 2016, the disclosures of which are incorporated by reference herein in their entireties. BACKGROUND

[0004] It is envisioned that International Mobile Telecommunications (IMT) beyond 2020 (e.g., IMT-2020) is to be extended and support a variety of scenarios that will continue to go beyond the use cases and applications of current IMT. In addition, various capabilities can be tightly coupled with these different use cases. Example families of use cases include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), and network operation. Example operating characteristics of eMBB can include macro and small cells, 1 ms latency (air interface), support for high mobility, etc. Example operating characteristics of URLLC can include low to medium data rates (e.g., 50 kbps - 10 Mbps), less than 1 ms air interface latency, 99.999% reliability and availability, low connection setup latency, 0 - 500 km / h mobility, etc. Example mMTC operating characteristics can include low data rates (e.g., 1 - 100 kbps), high density devices (e.g., 200,000 / km2), varying latency, requirement for low power (e.g., up to 15 years of battery lifetime), asynchronous access, etc. Network operation addresses various topics such as network slicing, routing, migration and interworking, energy savings, etc.

[0005] With respect to New Radio (NR) requirements, 3GPP TR 38.913 defines scenarios and requirements for New Radio (NR) technologies. Key performance indicators (KPIs) for URLLC and mMTC devices are summarized in Table 1 below:

[0006] Table 1 - KPIs for URLLC and mMTC devices

[0007] SUMMARY

[0008] According to various embodiments, mechanisms for unlicensed uplink transmission are disclosed. In one embodiment, access allocation for unlicensed uplink transmission via device graphical user interface (GUI) or open mobile alliance (OMA) device management (DM) system configuration can be static. In another embodiment, access allocation for unlicensed uplink transmission via system broadcast / multicast and unicast or RRC / MAC message can be semi-static. In yet another embodiment, access allocation can include dynamic allocation via downlink control signal or channel. Various mechanisms for unlicensed contention based uplink transmission are disclosed herein. Two-dimensional (e.g., time and frequency) priority collision avoidance schemes for contention based access are disclosed herein.

[0009] In an example embodiment, a node or apparatus configures a plurality of devices to operate in an unlicensed mode in accordance with respective unlicensed access allocations such that the plurality of devices transmit messages in the network using frequency resources defined by the respective unlicensed access allocations when transmitting the messages in the uplink, and the plurality of devices transmit the messages without being granted access to transmit the messages such that the plurality of devices operate in the unlicensed mode.

[0010] In various embodiments described herein, unlicensed uplink transmission includes multi-user orthogonality and contention management, static contention space allocation via device GUI or OMA DM system configuration, semi-static contention space allocation via system broadcast / multicast and unicast or RRC / MAC message, dynamic contention space allocation via downlink control signal or channel, and / or multi-user orthogonality management via contention space.

[0011] In an example embodiment, different configurations are used for unlicensed slots in subframes of a reference numerology. In some cases, a wideband unlicensed slot configuration is used for high reliability low latency use cases, such as ultra-reliable low latency communications (URLLC), and a narrowband unlicensed slot configuration is used for low data rate and latency tolerant use cases, such as massive machine type communications (mMTC). The unlicensed slots can be configured using time symbols and subcarriers in frequency in a reference numerology and symbols in a UE serving specific numerology.

[0012] This summary is provided to introduce some concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used in limiting the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to solving any or all of the disadvantages with any part of the disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0013] A more detailed understanding can be had from the following description, given by way of example in conjunction with the accompanying drawings wherein:

[0014] Figure 1 is a call procedure illustrating an example of uplink (UL) transmission with dynamic scheduling;

[0015] Figure 2 is a call procedure illustrating an example of UL transmission with non-persistent scheduling;

[0016] Figure 3 is an example CSMA / CA algorithm;

[0017] Figure 4 illustrates an example of UL OFDMA based random access procedure;

[0018] Figure 5 illustrates an example use case of a power grid including smart cities;

[0019] Figure 6 illustrates a dedicated sub-band for unlicensed access according to an example embodiment;

[0020] Figure 7 illustrates an example sub-band for hybrid licensed and unlicensed access according to an example embodiment;

[0021] Figure 8 depicts an example of access allocation indicated by a pilot pattern according to an example embodiment;

[0022] Figure 9 illustrates an example dynamic allocation according to an example embodiment;

[0023] Figure 10 illustrates another example dynamic allocation according to another example embodiment;

[0024] Figure 11A and 11B illustrates an example container for dynamic access allocation according to an example embodiment;

[0025] Figure 12 illustrates an example of two-dimensional (2D) priority collision avoidance contention access according to an example embodiment;

[0026] Figure 13A -C depicts an example of contention based access;

[0027] Figure 14A -C depicts an example of contention space for unlicensed access;

[0028] Figure 15A and 15B depict examples of dynamic unlicensed access configuration intervals aligned with one and two spacing intervals, respectively;

[0029] Figure 16A and 16B depicts another example of dynamic unlicensed access configuration intervals aligned with different unlicensed intervals, such that the unlicensed intervals are not aligned with licensed intervals;

[0030] Figure 17 depicts example physical control signals and channels for unlicensed UL transmissions according to example embodiments;

[0031] Figure 18 shows an example of an unlicensed slot type with UL only (wideband);

[0032] Figure 19 shows an example of an unlicensed interval / slot type with UL only (narrowband);

[0033] Figure 20 shows an example of an unlicensed slot configuration with DL and UL (wideband);

[0034] Figure 21 shows an example of an unlicensed slot configuration with DL and UL (narrowband);

[0035] Figure 22 shows an example of unlicensed slot structure and content;

[0036] Figure 23A and 23B shows an example of retransmission in a wideband unlicensed mini-slot according to example embodiments;

[0037] Figure 24A and 24B shows an example of retransmission in a narrowband unlicensed mini-slot according to example embodiments;

[0038] Figures 25A-26B depicts a call procedure for unlicensed UL transmissions for massive machine type communication (mMTC) devices according to example embodiments;

[0039] Figures 27A-28B depicts another example call procedure for unlicensed UL transmissions for ultra-reliable and low latency communication (URLLC) devices according to another example embodiment;

[0040] Figures 29A-30B depicts an example procedure for unlicensed UL transmissions for mMTC devices according to example embodiments;

[0041] Figures 31A-32B depicts an example procedure for unlicensed UL transmissions for URLLC devices according to example embodiments;

[0042] Figure 33A and 33Bdepicts an example call procedure for registration and unlicensed setup according to example embodiments;

[0043] Figure 34A and 34B depicts an example call procedure for unlicensed and licensed UL transmission for URLLC devices according to example embodiments;

[0044] Figure 35A and 35B depicts an example call procedure for unlicensed and licensed UL transmission for mMTC devices according to example embodiments;

[0045] Figure 36 is an example GUI for UE configuration according to example embodiments;

[0046] Figure 37A illustrates one embodiment of an example communication system in which the methods and apparatuses described and claimed herein can be embodied;

[0047] Figure 37B is a block diagram of an example apparatus or device configured for wireless communication according to the embodiments illustrated herein;

[0048] Figure 37C is a system diagram of an example radio access network (RAN) and core network according to example embodiments;

[0049] Figure 37D is another system diagram of a RAN and core network according to another embodiment;

[0050] Figure 37E is another system diagram of a RAN and core network according to another embodiment; and

[0051] Figure 37F is a block diagram of an example computing system 90 in which Figure 37C One or more apparatuses of the communication network illustrated in FIG. F can be embodied. DETAILED DESCRIPTION

[0052] As an initial matter, for different RAN architectures, the mechanisms described herein can be at, for example and without limitation, a NR node, a transmission and reception point (TRP) or a remote radio head (RRH), and a central controller in the RAN or a control function in a RAN slice. Unless otherwise noted, the mechanisms described herein can be applicable to the TRPs, RRHs, central controllers, and control functions in different RAN architectures.

[0053] To transmit on an uplink shared channel (e.g., physical downlink shared channel (PDSCH)) using the current method, a UE has a valid uplink (UL) grant, which can be received dynamically on a physical downlink control channel (PDCCH) or in a random access response, or can be semi-persistently configured, as specified in 3GPP TS 36.213. As shown in Figure 1 A UL transmission with dynamic scheduling can include, for example, the following steps, as shown in FIG. 2. A radio access network (RAN) 104 can transmit first data on a DL PDSCH and / or PDCCH with a downlink control information (DCI) format 0 for UL grant and a DCI format 1 for DL data decoding. If there is no DL data, the RAN 104 can transmit only the PDCCH with DCI format 0 without any DPSCH data. A user equipment (UE) 102 can decode a physical control format indicator channel (PCFICH) to calculate a control format indicator (CFI) value. The UE 102 can decode the PDCCH and obtain information about the DCI format 1. Based on the DCI format 1, the UE 102 can decode the DL data. The UE 102 can decode information about the DCI format 0 from the PDCCH. The UE 102 can transmit ACK / NAK for the DL data through uplink control information (UCI) carried by a physical uplink control channel (PUCCH). In this example, the UE 102 checks the grant field with the DCI format 0. If the grant is allowed, the UE 102 can transmit UL data through a physical uplink shared channel (PUSCH) according to the grant. The RAN 104 decodes the PUSCH data and transmits an acknowledgement (ACK) / negative acknowledgement (NACK) via a physical hybrid-ARQ indicator channel (PHICH). For example, if the PHICH carries a NACK, the UE 102 decodes the PHICH and can retransmit the data.

[0054] In some cases of semi-persistent scheduling, the RAN 104 can allocate a predefined set of radio resources for VoIP users at 20 ms intervals, instead of scheduling each uplink or downlink transmission as described above. Thus, the UE 102 does not need to request resources every TTI, which can significantly reduce scheduling assignment overhead. This scheduling is semi-persistent in the sense that the eNB can change the type or location of resource allocation if required for link adaptation or other factors.

[0055] Turning now to an example UL transmission with non-persistent scheduling, as shown in Figure 2As shown, the UL transmission with non-persistent scheduling can include, for example, the following steps. At 202, the UE 102 transmits a scheduling request (SR) on the PUCCH. At 204, the radio access network 104 transmits a UL grant (DCI 0) on the PDCCH. At 206, the UE 206 decodes the DCI 0 based on the resource blocks (RBs) specified by the DCI 0 and transmits a PUSCH. The radio access network 104 decodes the PUSCH. At 208, the radio access network 104 transmits an ACK / NACK on the PHICH as shown. At 210, the UE 102 determines whether the message received at 208 is an ACK or a NACK. If the message is a NACK, the UE 102 can retransmit (at 212), which can be the same message as operation 202.

[0056] Turning now to contention-based multiple access, in statistical time-division multiplexing, contention is a media access method for sharing a medium by multiple devices. In contention, any device in the network can transmit data on a shared channel at any time on a first-come-first-served basis. When two devices attempt to send at the same time, the access system fails. This is called a collision. One way to handle collisions in a contention-based system is to optimize collision detection and subsequent recovery. A collision can be detected by listening to the shared medium immediately after transmission and recognizing collision characteristics. Alternatively, data can be collected from the medium and error detection can be performed. To recover, some systems have the transmitter retransmit the collided data (e.g., a backoff algorithm that reduces the retransmission rate of the transmitter when collisions persist) or use error correction techniques such as FEC. Examples of collision detection and recovery multiple access protocols include Aloha, slotted Aloha, reservation Aloha, and the like.

[0057] An alternative approach to handling collisions in a contention-based system is to try to avoid them (collision avoidance). Some systems can utilize strict scheduling guidelines to identify who can use which resources at what time. Other systems can have the transmitter listen to the shared channel immediately before transmission to determine an appropriate transmission time. Examples of collision avoidance multiple access protocols include carrier sense multiple access (CSMA), CSMA with collision detection (CSMA / CD), CSMA with collision avoidance (CSMA / CA), and the like. With respect to CSMA access schemes, each device attempts to send after listening to the network. If the network is busy, the device will wait until the network is quiet.

[0058] With respect to collision detection (CD), devices continue to listen to the network while they are transmitting. If a device detects another signal interfering with the signal it is transmitting, it stops transmitting, for example, to shorten the time needed before it can attempt a retry. Two devices can wait a random amount of time, called a backoff time, and then attempt to transmit again. With respect to collision avoidance (CA), devices can attempt to avoid collisions by transmitting only when the channel is sensed to be "idle." If the transmission channel is sensed to be busy before a transmission, the transmission is postponed for a random interval. This random interval reduces the likelihood that two or more nodes waiting to transmit will start transmitting at the same time upon detection of the termination of a transmission, thereby reducing the incidence of collisions. When transmitting, a device transmits its packet data completely. For purposes of example, a typical algorithm for CSMA / CA used in 802.11 is illustrated in FIG. 1, where request to send (RTS) and clear to send (CTS) are used between base stations (BS) and access points (AP) to resolve the hidden terminal problem. Figure 3

[0059] Turning now to random access, two typical random access schemes in an orthogonal frequency division multiplexing (OFDM) system are now described. With respect to random access in LTE, random access in LTE is initiated by a random access preamble. Each random access opportunity configured for a physical random access channel (PRACH) should first be allocated in time and then in frequency as specified in TS 36.211, and all PRACH configured opportunities required for a given density value are maintained even if time multiplexing is not sufficient to have no overlap in time. For preamble formats 0-3, frequency multiplexing is performed according to

[0060]

[0061] where n is the number of uplink resource blocks, is the first physical resource block considered for allocation to a PRACH opportunity, and where is the first physical resource block available for PRACH.

[0062] For preamble format 4, frequency multiplexing is performed according to

[0063]

[0064] where n f is the system frame number, and N SP is the number of DL to UL switching points within a radio frame. Each random access preamble occupies a bandwidth of 6 contiguous resource blocks corresponding to a two-frame structure.

[0065] ​With respect to random access 802.11, UL OFDM-based random access is specified as follows. UL OFDMA-based distributed random access is a random access mechanism for high-efficiency (HE) stations (STAs) that randomly select a resource unit (RU) assigned by an access point (AP) for transmission of an UL PLCP protocol data unit (PPDU). An HE AP can indicate parameters in a trigger frame for HE STAs to initiate random access following the transmission of the trigger frame. The HE AP can indicate a value of OCWminfor the random access operation. The random access procedure is initiated by an HE STA that receives the trigger frame for random access.

[0066] For an initial UL PPDU transmission, when an HE STA obtains a value of OCWminfrom an HE AP, it can set the value of OCW to OCWminand initialize its OFDM backoff (OBO) counter to a random value in the range of 0 and OCWmin.

[0067] If the OBO counter of an HE STA is less than the number of RUs assigned to an association identifier (AID) value in the trigger frame, the HE STA can decrease its OBO counter to zero. Otherwise, the HE STA decreases its OBO counter by a value equal to the number of RUs assigned to the AID value in the trigger frame. For example, as shown in FIG. 6, HE STA 1 and HE STA 2 can decrease their non-zero OBO counters by 1 in each RU assigned to the AID value TBD for random access in the range of the trigger frame. If the OBO counter of an HE STA is a zero value, or if the OBO counter is decreased to 0, it randomly selects any one of the assigned RUs for random access and transmits its UL PPDU in the selected RU. Otherwise, the STA resumes with its OBO counter in the next trigger frame for random access. Figure 4

[0068] Turning to timing advance in LTE, timing advance is a negative offset at the UE between the start of a received downlink subframe and a transmitted uplink subframe. This offset at the UE ensures that the downlink and uplink subframes are synchronized at the eNodeB. For example, a given UE 1 that is farther away from the eNodeB can experience a greater propagation delay, such that its uplink transmission is advanced compared to a given UE 2 that is closer to the eNodeB than UE 1. Both UE 1 and UE 2 reference the arrival of a downlink subframe (together with the timing advance) to calculate uplink subframe timing, such that their UL transmissions are simultaneously synchronized and received at the eNodeB.

[0069] ​The eNodeB can estimate, during initial timing advance, from the PRACH sent by the UE. During initial access of the UE, PRACH is used as timing reference for uplink. The eNodeB sends a timing advance command in the random access response (RAR). Once the UE is in connected mode, if correction is needed, the eNodeB continues to estimate the timing advance and sends a timing advance command MAC control element to the UE. In an example, as long as the UE sends some uplink data (PUSCH / PUCCH / SRS), the eNodeB is able to estimate the uplink signal arrival time, which can then be used to calculate the required timing advance value.

[0070] With respect to transmit power control in LTE, initial PRACH power control is done in open loop, where the UE estimates the initial transmit power level based on the path loss calculated from referenceSignalPower broadcast in SIB2 and the measured received reference signal power. Once initial PRACH is complete, the UE power can be dynamically controlled by the transmission power control (TPC) command (MAC CE or TPC field in DCI 0). For example, closed loop UL transmit power can be controlled by feedback input from the eNB.

[0071] Reference is now made to Figure 5 , showing an example use case where different sensors or monitoring devices of a power grid system 500 of an example smart city are illustrated. Sensors of a smart home 502 (e.g., massive machine type communication (mMTC devices) can send power usage data once a week or once a month under very relaxed delay requirements. Sensors on the power transmission network 504 of the smart city (e.g., ultra-reliable low latency communication (URLLC) devices) can continuously monitor the power level and periodically report to the grid monitoring system 506, but when an abnormal power level is detected, for example, the sensor 504 is identified to need to send an immediate warning to the grid monitoring system 506, so that the grid monitoring system 506 can shut down the faulty power system and thereby be able to immediately implement a backup power system to avoid possible damage to the smart city power grid system 500 and to avoid negative impact on the operation of the smart city.

[0072] By another example use case, forest fire monitoring sensors (e.g., mission critical MTC devices) can periodically send small data with very low duty cycle, but they can need to send a fire warning message or message immediately and reliably. These devices can be sparsely located and can cover large areas of the forest. These devices can also have a limited battery life (e.g., 15 or 20 years).

[0073] As yet another example use case, medical equipment on an ambulance can be active while transporting a patient to an emergency room. For example, ultra-reliable and low latency communication (URLLC) devices can transmit patient temperature and blood pressure data and cardiac monitoring images to a hospital and physician's office. It will be appreciated that embodiments described herein can be applied to various use cases as desired.

[0074] URLLC and mMTC devices can be used for use cases. For example, URLLC devices without battery constraints can support small and medium UL data rate transmissions with ultra-low latency and very high reliability. URLLC or mission critical mMTC devices with battery limitations can support small UL data rate transmissions with ultra-low latency and extremely high reliability. mMTC devices with battery constraints and dense connectivity can support pre-scheduled or long latency tolerant small UL data rate transmissions.

[0075] As exemplified by the above use cases, URLLC devices can not be able to meet the latency requirements for UL data transmissions if current licensed-based UL data transmissions in LTE systems are used. With respect to mMTC devices, the signaling overhead of UL grant messages can be very significant compared to infrequent small UL data transmissions. It is recognized herein that this is a challenge for the battery life requirements of mMTC devices. To reduce UL transmission signaling overhead for mMTC devices and reduce UL transmission latency for URLLC devices, UL unlicensed transmissions (e.g., contention-based UL transmissions that do not undergo a grant procedure performed by a UE and a network node, such as those illustrated in Figure 1 and Figure 2 As described below, embodiments perform unlicensed UL transmissions that can meet the ultra-reliability low latency requirements for non-power-constrained URLLC devices. In addition, embodiments described herein perform unlicensed UL transmissions that meet the battery life requirements for mMTC devices.

[0076] Turning now to access allocation for unlicensed UL transmissions, according to example embodiments, a New Radio (NR) radio access network node (NR node) manages unlicensed access allocation for UL transmissions, for example but not limited to, ensuring a high success rate of contention-based access to avoid unnecessary interference to other serving devices and to optimize overall UL resource utilization in the NR system. The access allocation can be managed by the NR node statically or dynamically, as described in detail below. A sub-band or carrier is a region or group of contiguous subcarriers in the frequency domain. Sub-band and carrier are used interchangeably herein, but are not limited thereto.

[0077] Turning now to static or semi-static access allocation, as exemplified in the use cases described above, URLLC devices can require short latency and high reliability to transmit small or medium data, and mMTC devices can require low signaling overhead and reasonable reliability for delivering small data. To meet these requirements, in some examples, with respect to UL resources, devices requiring ultra-reliable low latency communication (referred to herein as URLLC devices) can use short transmission time intervals over a wide bandwidth. In examples, URLLC devices use a small number of symbols, which are scaled down via a reduced symbol length over a short transmission time, for example, to meet latency requirements. Further, with respect to UL resources, URLLC devices can use a large number of subcarriers, which can provide sufficient bandwidth for small and medium data with frequency diversity and coding / spreading gain built in the frequency domain, for example, to meet ultra-reliability requirements. To meet various requirements, in some examples, with respect to UL resources, devices performing massive machine type communication (referred to herein as mMTC devices) can use long transmission time intervals over a narrow bandwidth. In examples, mMTC devices can use scaled up symbols with increased symbol length and coding / spreading / time diversity gain in the time domain over a longer transmission time, for example, to meet low power consumption and reliability requirements. Further, with respect to UL resources, mMTC devices can use a small number of subcarriers, for example, for small data to meet low complexity and low power consumption requirements.

[0078] According to the general UL resource mapping outlined above, example grant-free access allocations 600a and 600b are illustrated in Figure 6 and example grant-free allocations 600c and 600d are illustrated in Figure 7 Allocations 600a-d can be statically configured, for example, via a UE graphical user interface (GUI) or open mobile alliance (OMA) device management (DM) system, or semi-statically managed via periodic system information broadcast and / or multicast. Such semi-static management can be based on system traffic load and resource status. Further, allocations 600a-d can be semi-statically managed via aperiodic unicast, for example, by on-demand system information requested by a UE.

[0079] With specific reference to Figure 6FIG. 6 illustrates dedicated sub-bands for unlicensed access. In example allocation 600a, sub-bands 602a for mMTC devices and sub-bands 604a for URLLC devices are separated from each other with respect to the frequency domain. In some examples, allocation 600a optimizes unlicensed access from the perspective of the UE and / or from the perspective of the service. In an example, each sub-band 602a and 604a is a RAN slice optimized for a particular type of device or service. For example, mMTC sub-bands 602a can be optimized for battery life savings, and URLLC sub-bands 604a can be optimized for short latency and high reliability. Each sub-band 602a and 604a can have the same or different numerology, which in some cases can depend on the optimization criteria.

[0080] In example allocation 600b, mMTC devices and URLLC devices use the same sub-band 601 with respect to the frequency and time domains. Example allocation 600b can optimize system resources for various example use cases, such as when both URLLC and mMTC devices have low UL traffic, or when mMTC devices and URLLC devices have different scheduling from each other for UL traffic. By sharing the total unlicensed resources between them, e.g., in sub-band 601, mMTC and URLLC devices can have the advantage of wider system bandwidth compared to approaches that do not share resources. Wider system bandwidth can allow the use of high redundancy schemes. Example schemes can allow low coding rate, high spreading factor, and more frequency diversity, which can increase the reliability of UL transmissions compared to approaches that do not share resources. In example embodiments, URLLC devices can have higher access priority than mMTC devices, e.g., due to more stringent latency and reliability requirements that can be placed on URLLC devices compared to mMTC devices. In example priority collision avoidance schemes described further below, URLLC and mMTC devices can use the same or different numerologies for subcarrier spacing, symbol length, and number of symbols in a transmission time interval. Alternatively, URLLC and mMTC devices can use partially different numerologies. For example, URLLC and mMTC devices can use the same subcarrier spacing, but use different numbers of symbols for a transmission time interval from each other.

[0081] Figure 7Example allocations 600c and 600d are shown in which a subband contains hybrid licensed and unlicensed access, which in some cases can maximize utilization of system resources. According to the illustrated examples, one or more URLLC devices can have overriding UL unlicensed transmission time intervals or subframes of devices using enhanced mobile broadband (eMBB), referred to herein as eMBB devices, particularly transmission time intervals or subframes of eMBB devices. For example, a UE can be permitted to transmit eMBB data using resources 608c, and a URLLC unlicensed UL transmission can be inserted at resources 606c, which overlap 608c. If the same UE wants to transmit eMMB data and a URLLC unlicensed UL transmission, for example, the URLLC data can preempt the eMBB data at 608c. If different UEs are transmitting eMBB data and URLLC data, the URLLC data can super position the eMBB data at 608c by using, for example, higher power, spreading codes, spatial precoding, etc., as compared to the eMBB data.

[0082] In example allocation 600c, mMTC devices transmit UL messages via a dedicated subband 602c, which is used only for mMTC devices. Further, in example allocation 600c, URLLC devices transmit unlicensed UL via a shared subband 603, and eMBB devices transmit licensed DL and / or UL messages in the same subband 603. In this example scenario, the URLLC devices can take advantage of the wide bandwidth of eMBB to meet or exceed reliability and latency requirements (e.g., with lower coding rates, higher spreading factors, more frequency diversity). With respect to the eMBB devices, in some cases, the impact of the shared subband 603 can be minimized due to wide frequency diversity, MIMO spatial gain, HARQ retransmissions, etc. For example, eMBB data can be overridden by URLLC data at resources 608c, as shown in FIG. 6B, and thus the eMBB data can be retransmitted later, e.g., if the originally transmitted data is indicated as a failure to the UE (e.g., via a NACK or via a HARQ process). Figure 7

[0083] ​In the example allocation 600d, mMTC devices transmit grant-free messages via the guard band 605 of the eMBB device. In alternative examples, mMTC devices can transmit grant-free messages via a band shared with granted DL and / or UL messages associated with the eMBB device. According to the illustrated example allocation 600d, URLLC devices can transmit grant-free messages in one or more shared sub-bands with respect to the frequency domain, e.g., in shared sub-bands 607 and 609. Sub-bands 607 and 609 can also be used by eMMB devices for granted DL and / or UL messages. In certain cases, using allocation 600d, mMTC and URLLC devices can each achieve a reliability gain, particularly when mMTC devices' traffic is pre-scheduled and / or tolerant to long delays (e.g., by being scheduled when there is very low eMBB traffic).

[0084] In some cases, certain time and frequency within the sub-bands illustrated in allocations 600c and 600d can be blocked for grant-free access, e.g., to reduce potential interference caused by grant-free access, to ensure QoS for certain eMBB devices. According to an example, sub-bands 607 and 609 each include a plurality of blocked regions 607a and 609a.

[0085] With respect to static allocations, example allocations 600a-d or the like can be pre-configured via a GUI on the device, e.g., GUI 3600 illustrated in FIG. 36B. Alternatively, example allocations 600a-d can be configured by a device manufacturer or service provider. Further alternatively, allocations 600a-d can be statically provisioned on the device using Open Mobile Alliance Device Management (OMA DM) protocols or any other Over-The_Air (OTA) device provisioning protocols. Static grant-free access allocations generally refer to allocations known to the device prior to establishing a corresponding communication session. Figure 36

[0086] ​With respect to semi-static allocation, the example allocations 600a-d above can also be signaled to the device (e.g., UE) transmitting the UL message, for example, but not limited to, via common RRC signaling, dedicated RRC signaling, or MAC control element (MAC CE) signaling. For example, using a common RRC signaling mechanism, the allocations 600a-d can be periodically broadcast or multicast by the NR node, for example, as part of system information (SI). Similarly, using dedicated RRC signaling, the example allocations 600a-d can be, for example, but not limited to, un-periodically unicast by the NR node in an RRC message or a MAC CE message as on-demand system information. In some cases, a given UE can acquire the access allocation information by searching for system information on a DL broadcast or multicast channel transmitted from the NR node. In other cases, the UE can send a request to the NR node for the access allocation information as on-demand system information. The NR node or apparatus (e.g., NextGen RAN node) can signal the UL transmission grant-free (e.g., for URLLC devices) resource allocation (configuration) to the UE in response to the request from the UE or as a result of autonomous NR node decision.

[0087] The following examples show how to signal the grant-free allocation to the UE in the RadioResourceConfigCommon system information (SI) that can be indicated to the UE via RRC signaling. Additionally or alternatively, the SI can be broadcast on a physical broadcast channel or a physical shared channel:

[0088]

[0089]

[0090]

[0091]

[0092]

[0093]

[0094] Turning to dynamic access allocation, given the dynamic patterns of services associated with different devices and services, UL access allocation (e.g., allocation 600a-d) can also be dynamically managed by a given NR node, according to some examples, enabling the management of system resources and / or control of unlicensed UL transmissions to ensure that various performance requirements of different devices and services are met. As used herein, the Dynamic Access Configuration Time Interval (DACTI) refers to a fixed or variable time interval that an application can apply to a specific access allocation scheme for DL ​​and / or UL messages. The length of the DACTI can be signaled to the UE via public RRC signaling, private RRC signaling, or via MAC CE signaling. The NR node (e.g., RAN node or device) can also signal the DACTI to the UE as a response to a request from the UE, or as a result of an autonomous NR node decision. In the example, the NR node can be configured to periodically signal the DACTI to UEs within its coverage area. The DACTI can also be dynamically signaled on the downlink control channel via downlink control information (DCI). As used herein, the access configuration signal can be shared with other control signals (e.g., pilots for synchronization or reference signals for radio link estimation or measurement). Alternatively, the access configuration signal can be a dedicated control signal used for access configuration (assignment).

[0095] refer to Figure 8 If the access configuration signal is shared with other control signals, then in this example, the pattern of pilot positions along the frequency axis (e.g., subcarriers in an OFDM mesh) can be used to indicate the current dynamic access allocation for DACTI. Figure 8 As shown, the specific pattern of pilot 802a may be located at the center of access subband 802 relative to the frequency. Alternatively or additionally, the pattern of pilot 802b may be located at the edge of subband 802. Pilots 802a and 802b may indicate the access type and allocation of the corresponding subband 802. In an example indicating unlicensed access allocation, pilots 802a and 802b may be transmitted from the NR node as configuration signals. The NR node may configure this DL configuration signal (shared or dedicated) via system information broadcast or RRC signaling message.

[0096] As used herein, an access configuration channel can refer to a shared or dedicated control channel, unless otherwise specified. If shared with other control channels, certain information elements (IEs) of the control channel message can be used to indicate dynamic access allocation. For example, a DCI of a downlink shared control channel can indicate the access type and location. A given NR node can configure this DL shared or dedicated control channel through system information broadcast or RRC signaling message. In some cases, a NR node can configure more than one DL shared control channel for a UE. Once configured, the channel can be activated or deactivated to obtain dynamic indication of grant-free access allocation. In some examples, a NR node can activate or deactivate the channel through MAC CE signaling or RRC signaling.

[0097] As Figure 9 and Figure 10 indicated, grant-free access allocation can be indicated at the channel of the first DL control signal or DACTI. These dynamic allocations can be signaled by the DL control channel or the DL control channel can signal allocations of several allocations or subbands. In some cases, a special predefined radio network temporary identifier (RNTI) can be used on the DL control channel to indicate that this allocation is for a DACTI.

[0098] With specific reference to Figure 9 , example allocation 900 represents an example full-band allocation. A first DL control signal or channel 902a within a first DACTI 904a indicates that the DACTI 904a is allocated for URLLC grant-free UL only. In an example, the DCI 902a associated with the grant-free UL configuration is decoded and then the grant-free UL allocation within the current DACTI 904a is decoded. According to the illustrated example, a second DL control signal or channel 902b within a second DACTI 904b indicates that the second DACTI 904b is allocated for eMBB licensed DL and / or UL communications mixed with URLLC grant-free UL messages. According to the illustrated example, a third DL control signal or channel 902c within a third DACTI 904c indicates that the third DACTI 904c is allocated for eMBB licensed DL and / or UL communications only. According to the illustrated example, a fourth DL control signal or channel 902d within a fourth DACTI 904d indicates that the fourth DACTI 904d is allocated for URLLC device grant-free UL only.

[0099] Reference is also made to Figure 10, the example allocation 1000 represents an example partial band allocation. According to the illustrated example, a first DL control signal or channel 1002a within a first DACTI 1004a indicates that the DACTI 1004a is split with respect to the frequency domain, such that it includes a URLLC device unlicensed UL only subband 1006a and eMBB DL and / or only UL subbands 1006b. In some examples, the DCI is decoded that configures the unlicensed UL, and then the unlicensed UL allocation within the current DACTI is decoded. According to the illustrated example, a second DL control signal or channel 1002b within a second DACTI 1004b indicates that the DACTI 1004b is split with respect to the frequency domain, such that it includes subbands 1008a and / or 1010a for mMTC device unlicensed UL access only, and subbands 1008b for eMBB licensed DL and / or UL and URLLC device unlicensed UL. According to the illustrated example, a third DL control signal or channel 1002c within a third DACTI 1004c indicates that the DACTI 1004c is split with respect to the frequency domain to include subband 1010a for mMTC device unlicensed UL access only when not indicated by the second DL control signal or channel 1002b, and subband 1010b for eMBB licensed DL and / or UL only. According to the illustrated example, a fourth DL control signal or channel 1002d within a fourth DACTI 1004d indicates that the DACTI 1004d is split with respect to the frequency domain, such that it includes subband 1012a for URLLC device unlicensed UL messages only and subband 1012b for eMBB licensed DL and / or UL communications only.

[0100] Turning now to Figure 11A and 11B , further details of dynamic access allocation in time and frequency domains are illustrated according to example embodiments. According to the illustrated example: (A) represents a licensed DL time interval; (B) represents a licensed UL time interval, (B') represents an unlicensed UL time interval; (X) represents a gap between licensed DL and UL time intervals; X' represents a gap between a DL control signal and an unlicensed UL message (with respect to the time domain).

[0101] In some examples, the DL control channel may contain DCIs for DL ​​TX, UL ACK / NACK, UL ​​licensing, and UL unlicensed configurations defined by the NR node (e.g., code seed or index for the NR node-defined codebook for UL multi-user multiplexing in the code domain). In some examples, the UL control channel may contain UCIs for UL unlicensed transmission configurations, such as DL Ack / Nack, UL HARQ schemes, and UE-selected UL unlicensed configurations (e.g., code seed or index for the codebook for UL multi-user multiplexing in the code domain). In some cases, such as... Figure 11A and Figure 11B As shown, each interval or container (A, B, X; B', X') can overlap within each DACTI, and multiple intervals can also overlap within a single DACTI, for example, if the DCI configuration for the downlink of an unlicensed UL includes multiple sub-containers. In some examples, multiple DACTIs can also overlap within a container, for example, for fast dynamic unlicensed UL management. In some cases, the unlicensed UL access allocation for a given UE can be dynamically managed by a given NR node based on, but not limited to: the UE's device type and / or capabilities; the UE's service requirements; the connection density associated with the UE; the UL data traffic pattern or scheduling associated with the UE; feedback from the UE regarding its failed contention or its contention success rate; the UE's radio link measurement reports; the UE's mobility status reports associated with the UE; the amount of unlicensed UL transmissions received by the NR node; the number of unlicensed UL packets successfully decoded by the NR node or the number of NACKs sent by the NR node for receiving UL retransmissions; system-related traffic load; system-related radio link budget, resource utilization, scheduling, and slicing; and / or interference or power control and management.

[0102] Now we turn to priority conflict avoidance for contention-based access. As mentioned above, URLLC devices need to meet very strict latency requirements, and therefore, URLLC devices may need to have a higher priority than other devices for contention-based access. Figure 12 The illustration shows an example of a CSMA / CA-based 2D (time-frequency) priority conflict avoidance contention access mechanism, where devices 1, 2, and 3 have a higher priority than device 4, which is used for UL contention access. The following terms are defined to help describe the illustrated example implementation. According to the illustrated example, the Contention Time Interval (CTI) refers to the time interval during which the UE competes for UL transmission. In some examples, the UE can obtain the CTI from system information or RRC signaling used for static or semi-static configuration. In some cases, the UE can decode the CTI from DL DCI and dynamic unlicensed UL transmission configuration. In another example, the UE can receive the CTI from the NR node in an unlicensed setup response.

[0103] With continued reference to Figure 12 , according to examples, a dedicated contention area (DCA) 1201 can refer to an area dedicated for UEs to detect UL resource availability for current CTI (e.g., lean carrier). For example, the frequency of this area 1201 can be narrow such that it contains a few subcarriers to facilitate detection and low overhead. The DCA 1201 can be located, for example, at any edge or center of a subband for contention detection. In Figure 12 , the DCA 1201a is located at the lower edge of the contention access subband. There can be one or more DCAs 1201 for contention-based access areas for allocation, and a UE can contend at one or more DCAs 1201, for example, indicated by the NR node. The UE can acquire the DCA 1201 from system information or RRC signaling for statically or semi-statically configured DCAs, can decode the DCA from DL DCI and dynamic grant-less UL transmission configuration for the DCA, or can receive the DCA from the NR node within a grant-less setup response.

[0104] Unless otherwise specified, a UE access pilot (UAP) 1203 refers to a UE pilot or reference signal that can be inserted at a given DCA 1201 to indicate that a UE is using the given resource to transmit its data. The UAP 1203 can also be interleaved with grant-less UL control information (GLUCI) (e.g., mixed with data on the UL transmission) to help the NR node decode the received GLUCI and demodulate the UL data. When interleaved with GLUCI, in some cases, the location of the UAP can be different for each UE. A given UE can acquire the location of the UAP from system information or RRC signaling for statically or semi-statically configured UAP information. Alternatively, a given UE can decode the UAP information from DL DCI and dynamic grant-less UL transmission configuration, or the UE can receive the UAP information from the NR node within a grant-less setup response. The UAP can be orthogonal among different UEs such that a receiver at a given NR node can use it to detect the UE transmitting UL data and estimate the channel for demodulating the UL data. The UAP can design the UE ID as a sequence with properties such as, but not limited to, its own cyclically shifted versions being orthogonal to each other and the cross-correlation between two prime lengths of the sequence being constant or close to constant. An example of implementation of orthogonal UAP can be a set of Zadoff-Chu sequences combined with the UE ID. Other UEs can also use the UAP at each DCA to detect whether the resource under the DCA is available for grant-less UL transmission.

[0105] Unless otherwise indicated, a grant-less UL control information (GLUCI) refers to an information element (IE) containing various control information for UL grant-less transmission, such as, but not limited to, coding rate, modulation, transmit power level, UL transmission redundancy, code seed or index for UE-defined multi-user multiplexing in code domain, etc.

[0106] Referring again to Figure 12 , as an example, according to the illustrated example, at the first CTI 1202a of time interval t0, device 1, device 2, and device 3 sense (listen) across the frequency range, dedicated DCA regions (DCAs) indicated as COi and CO2, and determine that the contention regions COi and CO2 are available for access by sensing that COi and CO2 are below a predefined detection threshold. In this example, device 4 senses only at DCA CO2, and also determines that CO2 is available for access. According to the illustrated example, device 1 randomly selects UL resources belonging to DCA COi by inserting its UAP at COi. Further, for example, if its UL transmission redundancy value is two or more, device 1 transmits a first redundancy version of its UL transmission at A02, and a second redundancy version of its UL transmission at A03. In some cases, the UL transmission redundancy value can be dynamically allocated by the NR node via a DL control channel DCI or UL grant-less setup procedure, or defined by the UE and indicated to the NR node on the UL control channel via GLUCI. In this example, both device 2 and device 3 randomly select UL resources belonging to DCA CO2 by inserting their UAPs at CO2. Continuing the example, for example, if its UL transmission redundancy value is three or more, device 2 randomly selects B01 for a first redundancy version of its UL transmission, B03 for its second redundancy version, and B04 for its third redundancy version. Device 3 randomly selects B03 for its first redundancy version of its UL transmission, and B02 for its second redundancy version, for example, its UL transmission value is two or more.

[0107] Thus, as described above, in some cases more than one device can select the same frequency and time resources to transmit their respective redundant versions of UL transmissions. In the illustrated example, device 2 and device 3 both select B03 to transmit one of their redundant versions. According to the illustrated example, in some cases, the NR node is able to detect and distinguish the overlapping UL transmissions if sufficient orthogonality is constructed between device 2's redundant version 2 transmission and device 3's redundant version 1. Different non-orthogonal multiple access schemes have different mechanisms for constructing multi-user orthogonality. For example, if multi-user orthogonality is created in the code domain, the NR node and UEs for grant-free UL transmissions can have an orthogonal codebook. If the codebook is not sufficient to cover a large number of UEs such as mMTC devices, the NR node can assign codes to UEs based on their UL transmission schedule. For example, the NR node can use a temporary code for the duration that a UE is scheduled to set the UL data; assign a code seed or index of the codebook through a DL control channel, Dlces; allocate a temporary code to a UE on demand; and / or assign a group code seed or index to a group, each UE within the group can randomly generate a code at a different time if they have different schedules for grant-free UL transmissions. The seed or index of a temporary code or a group code of the codebook can be dynamically assigned by the NR node via a DL control channel, DCI, or an UL grant-free setup procedure, or defined by the UE and indicated to the NR node on an UL control channel via GLUCI.

[0108] In other cases, for example, where no orthogonality exists between the two overlapping transmissions, the NR node is still able to decode the stronger UL data. For example, UL data can be stronger if it is received with a higher signal-to-noise and interference ratio compared to other data, such that it can be decoded by the receiver of the NR node. If the NR node is not able to decode the data, the NR node can treat the overlapping transmissions as a collision and discard the received data. In such an example, continuing to refer to Figure 12 , the NR node is still able to successfully decode the other non-overlapping transmissions from device 2 and device 3. Moreover, the NR node can combine the UL transmission redundant versions 1 and 3 from device 2. Thus, devices that require ultra-high reliability can insert multiple redundant versions for their grant-free UL transmissions to avoid UL data reception failure due to, for example, poor channel or contention collision. According to the illustrated example, device 4 waits for a backoff time before sensing that device 2 and device 3 have adopted CO 2, which can be randomly seeded by device 4 or the NR node. For example, device 4 can sense by determining that CO 2 is above a predefined detection threshold. Thus, device 4 can stop the contention for CO 2 for the remaining time in the first CTI 1202a.

[0109] Continuing to refer to Figure 12At the second CTI 102b during time interval dl, device 1 continues its transmission on Al and A3 by extending its UAP to DCA Cl, in the example illustrated in FIG. 1. Device 4 senses that DAC C12 is available and after a random backoff time, senses again that C12 is still available. Device 4 inserts its UAP at C12 and randomly selects Bl for its UL transmission. At the third CTI 102c during time interval 2 T Device 4 continues its transmission on B2 by extending its UAP to DCA C2, in the example illustrated in FIG. 1. In some cases, frequency hopping can also be applied in the 2D priority collision avoidance contention access scheme described above. The frequency hopping parameters can be statically or semi-statically configured, or can be dynamically assigned by the NR node via DL control channel DCI or UL grant.

[0110] Turning now to multi-user orthogonality and contention management examples, reference is made to Figure 13A -C, according to the contention-based UL transmission, no UE is specifically granted UL transmission resources, or scheduled to use UL transmission resources. Thus, in the example, the contention-based UL transmission is based on contention, which can cause multiple UEs to contend for the same UL resources at the same time, resulting in collisions, as depicted in Figure 13A -C.

[0111] For example, if full or partial orthogonal multi-user multiplexing is applied, it is recognized herein that advanced receivers at the NR node accessing the network are still able to demodulate the collided messages from multiple UEs. However, it is also recognized herein that the collisions increase inter-user interference, which can degrade system performance and also limit system capacity. For example, the achievable SIR can be limited to a certain value, which can depend on the number of multiplexed UEs. In example embodiments, to support the ultra-reliable performance requirements of URLLC devices and the massive connectivity requirements of mMTC devices, multi-user orthogonality with proper contention allocation is implemented in the NR network.

[0112] Non-orthogonal multiple access (NOMA) schemes are typically based on codes, sequences, or interleavers. Multi-user orthogonality is achieved through orthogonal codebook design, orthogonal or quasi-orthogonal sequence generation, or partial orthogonal interleaver pattern design. Thus, multi-user orthogonality among a large number of UEs is a challenging task to build with limited orthogonal codes, sequences, or interleaver patterns. Multi-user orthogonality with reduced collision probability of contention-based UL transmission is now discussed according to various embodiments.

[0113] In example embodiments, multi-user orthogonality and contention management is achieved by reusing the code, sequence, or interleaver pattern in time, frequency, and space; and controlling the number of UEs that contend for the same resources simultaneously for collision-based and collision-avoidance multiple access schemes.

[0114] As used herein, unless otherwise stated, a contention subcarrier group (COG) refers to a set of subcarriers allocated for competing for UL access. COGs may vary depending on the device or service. For example, various contention subcarrier groups may have different sets of system parameters, such as... Figure 14A As shown in the diagram. As used herein, unless otherwise stated, the Contention Time Interval (CTI) refers to the time interval allocated for contention of UL access. This time interval can vary for different devices or services and can have different sets of system parameters, such as... Figure 14B As shown herein, unless otherwise stated, a contention block (CB) refers to a resource block defined by a specific contention timing interval (CTI) and a specific contention subcarrier group (COG). The size of the block can vary relative to the time and number of subcarriers for different devices or services, or for different sets of system parameters, such as... Figure 14C As shown in the diagram. As used herein, unless otherwise stated, a contention space (CS) refers to a set of contention blocks that the UE competes with in the same spatial beam. A set of orthogonal or quasi-orthogonal codes, sequences, or interleaver patterns can be reused for different contention spaces.

[0115] Regarding multidimensional contention resources (MACRO): In MIMO OFDM systems, UL resources can be defined in the dimensions of time, frequency, and space. For example, micro(time(i), frequency(j), space(k)) can represent the resource of a contention block, which can be further described as: marc(CTI(i), COG(j), spatial beam(k)), which is the unit in which the UE competes for UL transmission. The UE can compete for one or more contention blocks (CBs) in the contention space. For example, using a code set, sequence, or interleaver pattern assigned by the NR node, an mMTC device can compete for two CBs (e.g., CB(Cit...). i Cog) and CB (CTI) i+1 CSG j In subcarrier group CSG j The two competition time intervals of CTI i and CTI i+1 Along a spatial beam b k ,{mdrc[CB(CTI i CSG j ),b k ],mdrc[CB(CTI i+1 CSG j ),b k UL transmission in the time-space contention of the [}]. Continuing this example, using code sets, sequences, or interleaver patterns assigned by NR nodes, URLLC devices can use two spatial beams for spatially redundant transmission.k and b k+1 in the competitive space along the frequency axis, three CBs (e.g., CB(CTI i , CSG j ), CB(CTI j+1 , CSG j+2 ), and CB(CTI i , CSG j )) of three subcarrier groups CSG i , CSG j+1 , and CSG i are competed for in the competitive time interval CTI j+2 , {mdrc[CB(CTI i , CSG j ), b k ], mdrc[CB(CTI i , CSG j+1 ), b k ], mdrc[CB(CTI i , CSG j+2 ), b k ]; mdrc[CB(CTI i , CSG j ), b k+1 ], mdrc[CB(CTI i , CSG j+1 ), b k+1 ], mdrc[CB(CTI i , CSG j+2 ), b k+1}.

[0116] In some cases, to construct multi-user orthogonality with reduced likelihood of collision, the NR node of the radio access network can define a contention space with a predetermined number of contention blocks dedicated to the contention space. Continuing the example, the NR node can further define a set, sequence, or interleaver pattern of orthogonal or quasi-orthogonal codes to be used by the group of UEs contending for the contention space. In some cases, the set, sequence, or interleaver pattern of orthogonal or quasi-orthogonal codes can be reused by different groups of UEs contending for different contention spaces. In this example, collisions can only occur between UEs contending in the same CS, and such collisions can be mitigated by multi-user orthogonality between UEs contending in the same CS. In some examples, the contention spaces can be controlled and managed by the NR node based on, by way of example and not limitation: access network available resources and accessibility; access network traffic characteristics and scheduling; access network radio link measurements (e.g., link quality); number of UEs within the relevant service area; throughput, contention access delay, and contention failure rate of the overall system; device types and functionalities within the service area; and / or other parameters associated with the UEs, such as traffic type, data rate, data size, delay requirement, error rate, contention failure rate tolerance, and other service QoS requirements.

[0117] Turning now to static or semi-static multi-user orthogonality and contention configurations, as described above, URLLC devices can require short latency and high reliability for delivery of small or medium data, and mMTC devices can require low signaling overhead and reasonable reliability for delivery of small data. To meet these requirements, according to various example embodiments, such as Figure 13A -C described above, various UL contention allocations can be used. In some examples, the multi-user orthogonality and contention configurations can contain various parameters, such as, but not limited to: parameters indicating an unlicensed UL access allocation configuration and parameters indicating a contention space allocation configuration. With respect to the contention space allocation configuration, the parameters can indicate, such as, but not limited to: available contention blocks (time, frequency); a set of orthogonal code indices, orthogonal sequence indices, or orthogonal interleaver pattern indices; a type of device and / or service for which the allocation applies, a type of RAN slice for which the allocation applies, a contention access type (e.g., contention based, contention avoidance, etc.); an access priority used for a priority-based contention access scheme and related random generation seeds, code indices, and / or other access parameters; a timeline or duration of the allocation to this CS; a numerology supported; a maximum CB allowed per UE in time and / or frequency; and a coding rate, modulation, etc. supported by the allocation.

[0118] With respect to static configuration, the example allocations described herein can be pre-configured via a GUI on the device, such as GUI 3600. In some cases, the allocations can be configured by a device manufacturer or service provider. Alternatively, the allocations can be statically provisioned on the device using Open Mobile Alliance Device Management (OMA DM) protocol or any other over-the-air (OTA) device provisioning protocol. The contention allocation (e.g., contention space with associated CB and code set, sequence, or interleaver pattern) is known to the device prior to establishing any communication session.

[0119] With respect to semi-static configuration, the example allocations described herein can also be broadcast to UEs through system information or signaled to UEs through common RRC signaling, dedicated RRC signaling, or MAC control element (MAC CE) signaling. For example, using common RRC signaling, the example allocations can be: periodically broadcast or multicast by the NR node as part of system information in RadioResourceConfigCommonSIB shown in example A below; or non-periodically unicast in RRC messages in rrcConnectionReconfiguration message or MAC CE message as on-demand system information by the NR node.

[0120] In some examples, a UE can acquire contention allocation information by searching for system information on a DL broadcast or multicast channel transmitted from the NR node. In some examples, a given UE can send a request to the NR node for contention allocation information as on-demand system information. The NR node (e.g., NextGen RAN node) can signal the contention configuration (allocation) to the UE in response to the request from the UE or as a result of an autonomous NR node decision.

[0121] Example A

[0122]

[0123]

[0124]

[0125]

[0126]

[0127]

[0128]

[0129] Turning now to dynamic multi-user orthogonality and contention management, in addition to the static and semi-static configurations discussed above, contention configuration (allocation) can also be dynamically conducted (e.g., activated and / or deactivated) via DCI on the DL control channel according to example embodiments. It is recognized herein that various devices and services can have dynamic traffic patterns, availability, etc., which can require dynamic management of multi-user orthogonality and contention by the NR node in some cases. Such dynamic management (e.g., activation, deactivation, reconfiguration, etc.) can ensure proper use of system resources to meet various unlicensed UL performance requirements.

[0130] As used herein, unless otherwise noted, a dynamic access configuration time interval (DACTI) refers to a fixed or variable time interval of DL and / or UL in which a particular access allocation scheme is applied. The length of a given DACTI can be signaled to the UE via common RRC signaling (e.g., in broadcast or multicast system information), via dedicated RRC connection reconfiguration signaling, or via MAC CE signaling. The NR node can also signal a DACTI to the UE as a response to a request from the UE, or as a result of an autonomous NR node decision. By way of example of an autonomous NR node decision, the NR node can be configured to periodically signal a DACTI to UEs within its coverage. A DACTI can also be dynamically signaled on the downlink control channel via downlink control information (DCI). As used herein, unless otherwise noted, an access configuration signal refers to a signal that can be shared with other control signals or a control signal dedicated to unlicensed access configuration. As used herein, an access configuration can be shared (e.g., shared between licensed and unlicensed) or dedicated (e.g., dedicated to licensed or licensed only) control channels. In some cases, control information elements (IEs) of the DL control channel message can be used to indicate, for example and without limitation, dynamic access allocation configuration, contention allocation configuration with associated contention blocks, and orthogonal or quasi-orthogonal code, sequence, or interleaver patterns. The NR node can configure this DL shared or dedicated control channel through an RRC signaling message. The NR node can configure more than one DL shared or dedicated control channel for a UE. Upon configuration, the channel can be activated or deactivated. The NR node can activate or deactivate the channel through MAC CE signaling or RRC signaling.

[0131] Reference is now made to Figure 15A and 15B, details of example dynamic access allocations and contention allocations in time and frequency domains are shown. As shown, example dynamic access configuration time intervals 1502a-c include the following variables: A, B, B', C, X, and X'. According to the illustrated example, A represents a licensed DL time interval, B represents a licensed UL time interval, B' represents an unlicensed UL time interval, X represents a gap with respect to time between the licensed DL and UL intervals, and X' represents a gap with respect to time between the licensed DL control signal (channel) and the unlicensed UL interval.

[0132] The DL control channel can contain DCI for DL control and / or data configuration, UL control and / or data configuration (e.g., unlicensed access allocation, contention space with associated contention block, and orthogonal or quasi-orthogonal codes, UE sequences, or interleaver patterns, etc.). The UL control channel can contain UCI for UL Tx configuration, DL Ack / Nack, etc.

[0133] In some cases, as shown in Figure 15A , each interval (A, B, X; B', X') can correspond within a respective DACTI 1502a and 1502b. In other examples, for example, if DCI for a given unlicensed UL is configured for multiple self-contained intervals, multiple containers, e.g., intervals 1504a and 1504b, can be within one DACTI 1502c.

[0134] Another example of dynamic access allocations and contention allocations in time and frequency domains is illustrated in Figure 16A and Figure 16B , where self-contained intervals 1602a-d can include the following variables: A', B1', X1', B2', and X2'. According to the illustrated example, A' represents an unlicensed DL time interval, B1' represents an unlicensed first UL time interval, B2' represents an unlicensed second UL time interval, X1' represents a gap with respect to time between the unlicensed DL and first UL, and X2' represents a gap with respect to time between the unlicensed first UL and second UL.

[0135] Reference is now made to Figure 17, exemplary grant-free physical control signals and channels 1702 and 1704 are shown. According to an example, a DL synchronization pilot 1702a can be included in the DL control channel 1702. The DL synchronization pilot can be used for fast synchronization of frequency (e.g., subcarrier spacing) and time (e.g., for TA estimation as described above) before grant-free transmission while switching from grant-free inactive state to grant-free active state. A DL reference signal 1702b can be included in the DL control channel 1702. The DL reference signal 1702b can be used for radio channel estimation and radio link measurement, e.g., received power of the reference signal can be used for UL path loss estimation as proposed above). It is recognized herein that the reference signal sequence needs to be designed with good orthogonality or quasi-orthogonality to avoid inter-call interference between different TRPs and limit inter-call interference at cell edge. M-sequence can be an example for its implementation. DL control information (DCI) 1702c can be included in the DL control channel 1702. The DCI can contain grant-free UL transmission configuration, which can include various parameters, such as but not limited to: grant-free access allocation parameters; grant-free contention space allocation parameters, grant-free contention block; code set, sequence or interleaver pattern for UL NOMA; transmit power level of DL reference signal; coding rate and modulation for UL; parameters related to access priority and related random generation seed; code index and / or other access parameters for priority-based contention access scheme; time schedule or duration (e.g., number of time intervals) allocated to this CS; indication of supported numerology; or maximum number of CBs allowed per UE in time and / or frequency.

[0136] Still referring to Figure 17 , an UL UE pilot 1704a can be included in the UL control channel / signal 1704. The UL UE pilot 1704a can be used to indicate the UE to the NR node receiver (e.g., distinguish from other UEs transmitting grant-free UL transmissions). In an example, the pilot 1704a includes the ID of the UE. In another example, the pilot 1704a is scrambled by the UE ID assigned during attach or grant-free setup with the NR node. To reduce possible collision between UE pilots, in some examples, the UE can randomly select the starting position for its pilot. For example, the UE can randomly select position 1 or 2 at the starting point for its pilot, as Figure 17The selection of the location of the pilot can also be based at least in part on the UE ID. The UL control information (UCI) 1704b that can be included in the UL control signal / channel 1704 can contain the unlicensed UL transmission configuration, which can include the following indications, presented by way of example and not limitation: code index, sequence or interleaver pattern for UL NOMA; transmit power level of UL reference signals; next transmission or scheduling update coding rate and modulation for UL; number of CBs for UL transmission; redundancy indication and index; delay indication for successful UL contention; failure rate of UL contention; radio link measurements; and device functionality or service type corresponding to the UCI.

[0137] Turning now to unlicensed UL transmissions in a subframe, by way of initial reference Figure 18 In the example subframe 1802 of a reference numerology, different kinds of unlicensed slots can be allocated differently. Example wideband unlicensed slots 1-5 are illustrated in Figure 18 Different partial subband unlicensed slots 1-3, which can be statically configured (e.g., in SI), semi-statically signaled (e.g., RRC or MAC CE), or dynamically indicated (e.g., DCI in DL control channel in slot 1), are shown in slot 1 of the reference numerology within subframe 1802, and different full subband unlicensed slots 4 and 5 are shown in slot 2 of the reference numerology within subframe 1802, which can be statically configured (e.g., in SI), semi-statically signaled (e.g., RRC or MAC CE), or dynamically indicated (e.g., DCI in DL control channel of slot 1 or secondary DL control channel in slot 2).

[0138] Example narrowband unlicensed intervals / slots 1-5 are illustrated in Figure 19 which can span across slot boundaries of a reference numerology, such as shown by unlicensed interval 1 and unlicensed interval 2. Different unlicensed intervals or slots are shown in the example subframe 1902 of a reference numerology. The unlicensed intervals / slots 1-5 can be predefined or preconfigured by the system management; via higher layer static or semi-static configuration, such as via RRC signaling or MAC CE; or dynamically signaled by unlicensed DCI carried on the DL control channel and / or secondary DL control channel, if applicable.

[0139] Example narrowband unlicensed intervals / slots 1-5 are illustrated in Figure 20 and Figure 21Examples of a midamble unlicensed slot (e.g., unlicensed mini-slot) configuration can be configured statically (e.g., in SI), signaled semi-statically (e.g., RRC or MAC CE), or indicated dynamically (DCI in DL control channel in slot 1 or slot 2), containing unlicensed DL signals and / or control information (e.g., DCI), unlicensed UL pilot / preamble, control information (e.g., UCI), and data. Unlicensed slot configurations, such as the example configuration shown in Figures 18-21 may contain the following parameters, presented by way of example and not limitation: Gap 1, which can refer to a time gap from a reference numerology of DL control, which can dynamically indicate an unlicensed slot configuration with a reference numerology (e.g., slot 1), or a time gap from a secondary DL control, which can dynamically indicate an unlicensed slot configuration with a reference numerology slot (e.g., slot 2), if applicable; Gap 2, which can be optional and can refer to a time between unlicensed slots; Length of unlicensed DL, which can refer to a number of symbols carrying unlicensed; DL synchronization for time and frequency synchronization; DL reference signals for DL path loss, DL propagation delay, DL radio link measurement, and for decoding DL control information; DL control information for carrying configuration for unlicensed UL transmission, such as contention resource pool (e.g., contention space) allocation (part sub-band of full sub-band in frequency) or unlicensed signature pool (e.g., UE pilot) to differentiate multiple UEs multiplexed; NR node DL timestamp; DL reference signal power level; Hybrid Automatic Repeat Request (HARQ) or retransmission scheme; Length of unlicensed UL, which can indicate a number of symbols carrying unlicensed; UL UE pilot / preamble used; UL control information (UCI) for supporting NR node to decode UL data (e.g., UE ID, contention block used, UL HARQ scheme, index of UL signature, retransmission scheme and / or redundancy index, UL reference signal power level, radio link measurement, delay of successful UL contention or failure rate of UL contention, device capability or service type, location, mobility, schedule (e.g., next UL transmission), etc.); UL data, which can be carried on the same symbol carrying UL UCI for small size data if wideband unlicensed is configured; and Gap 3, which can refer to a time gap between unlicensed DL and UL, if applicable.

[0140] The example configuration parameters or control information mentioned above can be predefined or preconfigured by system management, or configured semi-statically or dynamically by higher layer such as via RRC signaling or MAC CE, or indicated by DCI in one or more DL control channels, so that the UE can determine according to the parameters of the allocated grant-free slot. Based on the received parameters, the UE can also identify the parameters and / or control information associated with the slot structure and DL and UL configuration. Figure 22 An example grant-free slot structure and content 2200 is depicted in

[0141] Reference is now made to Figure 23A and 23B illustrating retransmission in a wideband grant-free mini-slot according to example embodiments. Figure 24A and 24B depicts example retransmission in a narrowband grant-free mini-slot according to another example embodiment. As shown, for example, a grant-free DL control channel 2302 can contain DCI for configuring grant-free UL transmission, and a grant-free UL control channel 2304 can contain UCI for a hybrid automatic repeat request (HARQ) scheme for grant-free UL retransmission 2306. For example, HARQ, such as ACK / NACK, is delivered by, for example, the next grant-free mini-slot 2308. The ACK / NACK can be transmitted in the same reference numerology set slot on grant-free DL control as the transmission 2306 (e.g., slot 1 as shown in Figure 23A the next slot reference numerology set slot on shared DL control 2301b or grant-free DL control 2302b (e.g., slot 2 as shown in FIG. 23). The ACK / NACK carried on the grant-free DL control channel 2308 in the next grant-free mini-slot determines whether to retransmit the grant-free UL data at 2310 / 2320b. For example, if a NACK is received, in some cases, the UL portion 2306 of the grant-free mini-slot 2306 is retransmitted. In some examples, time adjustment (TA), transmit power control (TPC), modulation and coding scheme (MCS), etc. are carried on the grant-free DL control channel in the next grant-free mini-slot, so that the retransmission parameters are indicated. As shown, for example in Figure 24B the retransmission can be at a different frequency than the original transmission.

[0142] Reference is now made to Figures 25A to 26B, an example system 2500 is shown that includes mMTC UEs 2502, NR nodes 2504, and a core network (CN) 2506. The NR nodes 2504 include a RAN slice management function or apparatus (node) 2508 and an mMTC slice 2510. The CN 2506 includes a CN slice management function or apparatus (node) 2512 and an mMTC slice 2514. The mMTC 2514 can include a mobility management node or apparatus 2516, a gateway 2518 (e.g., SWG, PGW), and a subscription management function or apparatus (node) 2520 (e.g., HSS). It will be appreciated that the example system 2500 is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of the present disclosure. In addition to systems such as Figures 25A to 26B the system illustrated in Figures 25A to 26B In addition to systems such as

[0143] With particular reference to Figure 25A At 1, according to the illustrated example, the UE 2502 is powered on. After being powered on, the UE 2502 can perform cell search and synchronization, and then the UE can acquire system information, e.g., from MIB and SIBs. At 2, the UE 2502 sends a radio connection request to the NR node 2504. In particular, the UE can send the radio connection request message to the RAN slice management apparatus 2508 (at 2A) or the mMTC slice 2510 (at 2B). The request can be a request to access to the UE selected RAN slice 2510 at the NR node 2504. The request can include various context information associated with the UE 2502. The context information can include, for example, but is not limited to, a device type of the UE 2502 (e.g., mMTC, URLLC), a service associated with the UE 2502 (e.g., forest fire monitoring or traffic monitoring), a latency requirement (e.g., ultra-low latency of 100 ms or 0.5 ms), a data traffic context (e.g., data packet size or data rate), a traffic type (e.g., non-IP or IP based), a mobility context associated with the UE 2502 (e.g., static, pedestrian, vehicle), a scheduled schedule of data transmission from the UE 2502, a type of access that can be performed by the UE 2502 (e.g., licensed access, unlicensed access, or access that switches between licensed and unlicensed). In some cases, operations 3, 4, and 5 are not performed when the UE selects the slice 2510.

[0144] In some cases, such as when the UE 2502 does not select a slice, the RAN slice management 2508 selects a slice 2510 as the radio access slice for the UE, e.g., based on the UE context in the request at 2A, at 3A. The selection can also be based on RAN traffic load and resource allocation. At 4A, the RAN slice management 2508 sends a RAN slice connection request to the selected mMTC slice 2510, according to the illustrated example. The request can also forward all or some of the UE’s context from 2A, so that a radio connection can be established between the UE 2502 and the mMTC slice 2510. At 5A, the mMTC slice 510 can send a RAN slice connection response to the RAN slice management 2508. The response can indicate whether the slice connection request has been accepted. If the request is rejected, one or more reasons for the rejection can be included in the response message.

[0145] At 6, the RAN slice management 2508 (at 6A) or the mMTRC slice 2510 (at 6B) sends a RAN slice connection response to the UE 2502, according to the illustrated example. In this message, the RAN slice management 2508 or the RAN mMTC slice 2510 can confirm whether the radio connection request has been accepted. If the request is rejected, one or more reasons for the rejection can also be included in the response message. In the illustrated example, the UE 2502 receives confirmation that a successful radio connection has been established with the mMTC slice 2510. At 7, the UE can send a registration request to the RAN slice management 2508 (at 7A) or the RAN mMTC slice 2510 (at 7B). The registration request can be sent to establish a secure service connection with the core network (CN) 2506.

[0146] Reference is now made to Figure 25BAt 8, the registration request is sent to the CN slice management 2512 (8C and 8C') or the CN mMTC slice 2514 (8D and 8D'). The request can be sent by the RAN slice management 2508 (8C and 8D) or the mMTC slice 2510 (8C' and 8D'). The request can include context information associated with the UE, information associated with the mMTC slice 2510, such as, for example, a slice ID. In some cases, when the NR node 2504 selects the CN slice 2514, the operations 9 and 10 now described are skipped. At 9C, according to the illustrated example, the CN slice management 2512 selects the mMTC IP traffic slice 2514, for example, based on the UE context, the RAN mMTC slice 2510, the traffic load of the CN 2506, available mMTC slices, etc. At 10C, according to the illustrated example, the CN slice management node 2512 sends a registration request to the mobility management node 2516. The registration request can include the context information of the UE and information associated with the RAN mMTC slice 2510.

[0147] Reference is now made to Figure 26A Continuing with the illustrated example, at 11, the mobility management node 2516 exchanges messages with the subscription management node 2520 to authenticate the UE 2502 for access to services. After authentication, at 12, the mobility management node 2516 exchanges messages with the UE 2502 so that the UE 2502 and the mobility management node 2516 mutually authenticate each other and then a security mode is established between them. At 13, according to the illustrated example, the mobility management node 2516 can exchange messages with the subscription management node 2520 so that the location of the UE 2502 is updated. Location update: mobility management exchanges messages with subscription management for location update. At 14, an IP session can be established between the RAN mMTC slice 2510 and the CN mMTC slice 2514. An IP session can also be established within the CN mMTC slice 2514.

[0148] Continuing with reference to Figure 26AAccording to the illustrated example, at 15, unlicensed operation is set up. For example, the NR node 2504, and in particular the RAN mMTC slice 2510, can exchange messages with the UE 2502 to configure the unlicensed operation parameters described herein. Example parameters include, but are not limited to: contention access allocation parameters; unlicensed configuration parameters (e.g., DACTI, CTI, DCA, UAP, GLUCI, etc.); a seed or index for an orthogonal code used for code domain multiple access; a seed or value for random backoff for priority collision avoidance contention access; redundancy parameters for reliable transmission; a timer for an inactive state (e.g., for listening to a broadcast channel for paging or system information changes, for measurements for radio link management, for updating state related to reachability and mobility, etc.); unlicensed power control values (e.g., minimum and maximum UL transmit power levels and incremental adjustments, which can be computed by the NR node 2504 based at least in part on path loss and required received signal quality during the message exchange between the UE 2502 and the NR node 2504 described above); parameters related to a schedule for unlicensed UL transmissions; coding rate; modulation scheme, etc.

[0149] At 16A, according to the illustrated example, the UE 2502 acknowledges the unlicensed configuration (allocation) with higher layers of the UE 2502, as compared to the physical layer. Alternatively or additionally, the UE 2502 can acknowledge the unlicensed setup with the NR node 2504, and in particular the RAN slice management node 2508 (at 16B) or the mMTC slice 2510 (at 16C). Thus, the UE 2502 can receive an enter "unlicensed" mode of operation command from higher layers or from the NR node 2504. At 17, the UE 2502 enters an inactive state (e.g., a low power state without data to transmit) of the unlicensed mode of operation. The inactive state can be preconfigured. In some cases, the inactive state can be triggered by a command from higher layers or the NR node to operate in unlicensed mode after registration. In some cases, the UE 2502 can automatically enter the inactive state in unlicensed mode of operation if configured to do so. At 18, according to the illustrated example, the UE 2502 receives data from higher layers that it needs to transmit in a UL transmission. Example data includes, but is not limited to, "keep alive" small data, measurement data, data associated with reachability and mobility state of the UE 2502, etc. At 19, the UE 2502 can need to check system information on a broadcast channel. As further examples, at 19, the UE 2502 can need to make radio link measurements, or select a new cell based on the results of system information or radio link measurements. At 20, according to the illustrated example, the UE 2502 synchronizes with a reference signal or available synchronization pilot (e.g., a first available synchronization pilot) at a symbol timing boundary for allocation of contention access regions.

[0150] At 21, according to the illustrated example, the UE 2502 sends a grant-free UL transmission to the NR node 2504, specifically the RAN mMTC slice 2510. In some cases, the UE 2502 can contend for the grant-free UL transmission (without a redundancy version) with an initial UL transmission power, which can be defined at the grant-free setup phase (at 15) or signaled by the NR node 2504 via system information broadcast or RRC signaling. In some cases, the UE 2502 can indicate whether this transmission requires an acknowledgement (ACK) at the transmission power level. The UE 2502 can also include radio link measurements, reachability or mobility status, or other information with the UL data transmission at 21. At 22, the UE 2502 can wait for an ACK response to its UL transmission from the mMTC slice 2510, or the like. If an ACK is required, for example, the UE 2502 can wait until an ACK timer expires. At 23, according to the illustrated example, the UE 2502 makes a retransmission of the UL message. For example, if its grant-free UL data requires a reliable transmission, the UE 2502 can contend again. At 24, according to the illustrated example, the NR node 2504, specifically the mMTC slice 2510, sends an ACK message to the UE 2502 indicating that the UL transmission from the UE 2502 was successfully received. The message at 24 can also include a power adjustment value for the UE's next grant-free UL transmission, providing a quasi-closed loop power control. At 25, the UE 2502 can enter an inactive state of the grant-free operation mode. The inactive state generally refers to a state in which the UE is not transmitting. The inactive state can be pre-configured or triggered by a higher layer command after a grant-free UL transmission. The inactive state can also be triggered when the UE 2502 receives an ACK from the NR node 2504, for example, when the transmission requires an ACK. In some cases, the UE 2502 can automatically enter the inactive state after a grant-free UL transmission, if the UE 2502 is configured to do so, for example.

[0151] Further reference is made to Figures 27A to 28BFIG. 13 illustrates an example of unlicensed UL transmissions for URLLC devices. An example system 1300 is shown that includes a URLLC UE 1302, a NR node 1304, and a core network (CN) 1306. The NR node 1304 includes a RAN slice management function or apparatus (node) 1308 and a RAN URLLC slice 1310. The CN 1306 includes a CN slice management function or apparatus (node) 1312 and a URLLC slice 1314. The URLLC slice 1314 can include a mobility management node or apparatus 1316, one or more gateways 1318 (e.g., SWG, PGW), and a subscription management function or apparatus (node) 1320 (e.g., HSS). It should be appreciated that the example system 1300 is simplified to facilitate the description of the disclosed subject matter and is not intended to limit the scope of the disclosure. Other devices, systems, and configurations can be used in addition to or instead of the systems illustrated in FIG. 13 to implement the embodiments disclosed herein, and all such embodiments are contemplated to be within the scope of the disclosure. Figures 27A to 27B In addition to or instead of systems such as those illustrated in FIG. 13, other devices, systems, and configurations can be used to implement the embodiments disclosed herein, and all such embodiments are contemplated to be within the scope of the disclosure. Figures 27A to 27B In addition to or instead of systems such as those illustrated in FIG. 13, other devices, systems, and configurations can be used to implement the embodiments disclosed herein, and all such embodiments are contemplated to be within the scope of the disclosure.

[0152] Figures 27A to 28B Example embodiments of URLLC devices illustrated in FIG. 13 can be similar to the example embodiments of mMTC devices described above, and thus reference is made to Figures 25A to 26B similar operations are described. However, with respect to URLLC devices, the context information associated with the UE 1302 can include a value that indicates that the UE 1302 can switch between licensed and unlicensed operation. Additionally, the eMBB / URLLC slice can be selected at the NR node 1304 in order to optimize overall system resource utilization. In an example, the URLLC slice 1314 is selected to meet short latency requirements across the system (network) 1300. In some examples, the UE 1302 makes its unlicensed UL transmissions with redundancy. In one example, at 24, the UE 1302 switches from unlicensed to licensed operation mode after receiving a command from a higher layer. As an example, the UE 1302 can include a traffic monitor that switches from unlicensed to licensed operation mode to upload images of a traffic incident to the network.

[0153] Reference is now made to Figures 29A to 30B, an example system 2500 is shown. In the illustrated example, unlicensed UL operation is performed for mMTC UE devices. According to the illustrated example, RAN slice management node 2508 and CN slice management node 2512 can be logical entities that perform common control functions in the RAN and CN 2506, respectively. For example, RAN slice management node 2508 and CN slice management node 2512 can exchange service subscription and policy information, which can be used to verify requests for access to a slice. Such information can also be used to establish security settings, billing parameters, etc. RAN slice management node 2508 and CN slice management node 2512 can also exchange context information associated with UE 2502. Such context information can include, for example, mobility information, location information, transmission scheduling information, data traffic information, etc. The context information can allow for selection of an appropriate (e.g., optimal) slice in the RAN and CN 2506.

[0154] Mobility management node 2516 and subscription management node 2520 can represent common functions for CN slices (slice-common) associated with a service provider. In some cases, as shown, mobility management node 2516 and subscription management node can be part of CN slice management 2506, or can represent specific functions (slice-specific) internal to CN slices 2514 provided by a particular service provider.

[0155] Referring in particular to Figure 29A and Figure 29BAt 1, according to the illustrated example, the UE 2502 powers on. After powering on, the UE 2502 can perform cell / TRP / slice search and synchronization. The UE 2502 can also acquire system information from MIB and SIB. At this point, in some cases, the UE 2502 can be in a state similar to EMM-Logged Out, ECM-Idle, and RRC Idle as defined in current LTE systems. At 2, the UE 2502 can send a radio connection request to the RAN slice management node 2508 (at 2A) or mMTC slice 2510 (at 2B). The request can include various context information associated with the UE 2502, such as, for example and without limitation: device type (e.g., mMTC or URLLC), service (e.g., service for forest fire monitoring or traffic monitoring), latency requirement (e.g., 100 ms or ultra-low latency 0.5 ms), context related to data traffic (e.g., data packet size and / or data rate and / or duty cycle), CN traffic type (e.g., based on non-IP or IP), mobility context (e.g., static, pedestrian, or vehicle, or low speed in a restricted area, etc.), location context (e.g., UE tracking area at RAN), scheduling context (e.g., scheduling of data transmission), access context (e.g., licensed or unlicensed access, whether switchable between licensed and unlicensed, access priority, etc.). In some cases, operations 4 and 5 are not performed, e.g., when the UE 2502 selects the RAN slice 2510.

[0156] At 3A, the RAN slice management node 2508 can select a RAN slice 2510. The selection can be based at least in part on context information associated with the UE 2502, traffic load and resource allocation at various RAN slices, relevant service profiles or subscriptions, charging policies, etc. The information can be stored at the NR node 2504 or received from the CN 2506 via a CN slice management node 2512 and / or a subscription management entity 2520 on the CN 2506. At 3A, the RAN slice management 2508 selects the mMTC slice 2510 as the radio access slice for the UE 2510. At 3B, the RAN slice 3510 can determine to accept the UE’s connection request to the RAN-selected or UE-selected RAN slice 3510. At 4A, the RAN slice management 2508 can send a RAN slice connection request to the mMTC slice 2510. The connection request can include context information associated with the UE 2502 so that a radio connection can be established between the UE 2502 and the slice 2510. At 5A, according to the illustrated example, the mMTC slice 2510 sends a RAN slice connection response to the RAN slice management 2508. The response can indicate whether the slice connection request has been accepted. If the request is rejected, a reason for the rejection can be included in the response message. If the request is accepted, radio configuration parameters for the selected RAN slice 2510 (e.g., dedicated radio resource configuration for SRB1-like and / or DRB-like for the UE 2502) can be included in the response.

[0157] Still referring to Figure 29A and Figure 29BAt 6, according to the illustrated example, the RAN Slice Management 2508 (at 6A) or the mMTC Slice 2510 (at 6B) sends a radio connection response to the UE 2502. The response can indicate that the radio connection is confirmed by the RAN Slice Management 2508 or the RAN mMTC Slice 2510. Reasons for rejection can also be included in the response message if the request for the selected RAN Slice 2510 is rejected. If the request is accepted, radio configuration parameters for the selected RAN Slice 2510 (e.g., dedicated resource configuration for SRB1-like and / or DRB-like for the UE 2502) can be included in the response. In some cases, the RAN Slice Management 2508 or the selected RAN Slice 2510 can send SBR1 and / or DRB resources (e.g., SRB and / or DRB configuration) dedicated for the UE 2502 (e.g., within the response message). Thus, the UE 2502 can be confirmed to have a successful radio connection with the mMTC Slice 2510, which can be a NAS connection with the selected RAN Slice 2510. At 7, according to the illustrated example, the UE 2502 can send a registration request to the RAN Slice Management 2508 (at 7A) or the RAN mMTC Slice 2510 (at 7B). The registration request can be sent at the NAS layer and can be encapsulated in a radio connection complete message, which can also include the radio configuration as indicated by the selected RAN Slice 251. The RAN Slice Management 2508 can send the registration request to the CN Slice Management 2512 (at 8A) or the mobility management 2516 (at 8D). Alternatively, the RAN mMTC Slice 2510 can send the registration request to the mobility management 2516 (at 8D’). The registration request can be sent to the mobility management 2516 when the slice 2512 is selected by the NR node 2510. In some examples, the registration request can be sent to the CN Slice Management 2512 when the RAN Slice 2510 is selected by the UE 2502 (at 8B). The registration request can include context information associated with the UE, as well as slice information (e.g., ID) associated with the mMTC Slice 2510.

[0158] In some examples, the NR node 2504 or the CN 2506 can select the CN slice 2514 based on various context information associated with the UE 2502. For example, the CN slice selection can be based at least in part on an ID assigned to the UE by the RAN slice management 2508 or the RAN slice 2510 in the NR node 2508, a type of the UE 2502 (e.g., mMTC or URLLC), a service performed by the UE 2502 (e.g., forest fire monitoring or traffic monitoring), a latency requirement (e.g., long latency 100 ms or ultra-low latency 0.5 ms for session or flow end-to-end latency); data traffic (e.g., data bit rate and / or traffic load for a session or flow); routing type (e.g., based on non-IP or IP), mobility (e.g., static, pedestrian or vehicle, or low speed in a restricted area); location (e.g., tracking and / or routing area of the UE in the network, such as TAI and ECGI in LTE systems); scheduling (e.g., scheduling of UL data transmission); charging (e.g., online or offline charging), and / or the like.

[0159] In some cases, operations 9 and 10 are not performed, for example, when the NR node 2504 selects the CN slice 2514. In other cases, at 9C, the CN slice management 2512 selects the mMTC IP traffic slice (slice 2514) based on at least part of the context information associated with the UE, the RAN mMTC slice 2510, CN traffic load, or available mMTC slice, and / or the like. At 10C, the CN slice management 2506 can send a registration request to the mobility management node 2616. The registration request can include the context information associated with the UE 2502 and information related to the RAN mMTC slice 2510. At 10C, in some cases, a connection between the NAS layer of the UE 2502 and the mobility management 2516 or the CN slice 2514 is established. The UE can then transition to various states, such as EMM-registered, ECM-connected, and RRC-connected states in LTE systems.

[0160] Reference is now made to Figure 30AAt 11, according to the illustrated example, the mobility management 2516 exchanges messages with the subscription management 2520 for authentication of the UE 2502 with the requested service. The exchanged messages can include, for example, but are not limited to, UE ID (such as IMSI and service network ID) and context, RAN slice and CN slice information (such as RAN slice ID and CN slice ID), service network ID, UE service profile or subscription and charging policy, assigned UE default IP address, etc. Security keys can be generated for establishing secure connection in the CN 2506 and RAN. At 12, the mobility management node 2516 and the UE 2502, after authentication with the subscription management 2520, can exchange messages to mutually authenticate each other and then establish a security mode for NAS signaling between them. At 23, according to the illustrated example, the mobility management 2516 and the subscription management 2520 exchange messages to update the location associated with the UE 2502. At 14, according to the illustrated example, an IP or non-IP session is established within the CN mMTC slice 2514 over the radio bearer between the UE 2502 and the mobility management 2516 in the CN 2506 through the interface between the RAN mMTC slice 2510 and the CN mMTC slice 2514 and the network connectivity in the core network 2506.

[0161] At 15, the unlicensed operation is set up. For example, the NR node 2504, in particular the RAN mMTC slice 2510, can exchange messages with the UE 2502 to configure the unlicensed operation parameters described herein. Example parameters include, but are not limited to: contention access allocation parameters; access priority and / or contention priority; unlicensed configuration parameters (e.g., DACTI, CTI, DCA, UAP, GLUCI, etc.); seed or index of orthogonal codes for code domain multiple access; seed or value of random backoff for priority collision avoidance contention access; redundancy parameters for reliable transmission; timers for being in an inactive state (e.g., for listening to a broadcast channel for paging or system information changes, for measurements for radio link management, for updating state related to reachability and mobility, etc.); unlicensed power control values (e.g., minimum and maximum UL transmit power levels and incremental adjustments, which can be computed by the NR node 2504 based at least in part on path loss and required received signal quality during the message exchange between the UE 2502 and the NR node 2504 described above); parameters related to scheduling for unlicensed UL transmissions; coding rate; modulation scheme, etc. At 16A, according to the illustrated example, the UE 2502 confirms the unlicensed configuration (allocation) with higher layers of the UE 2502, as compared to the physical layer. Alternatively or additionally, the UE 2502 can confirm the unlicensed setup with the NR node 2504, in particular the RAN slice management node 2508 (at 16B) or the mMTC slice 2510 (at 16C). Thus, the UE 2502 can receive an enter "unlicensed" operation mode command from higher layers or from the NR node 2504.

[0162] Reference is now made to Figure 30BAt 17, the UE 2502 enters into an inactive state of the unlicensed operation mode. The inactive state can be pre-configured. In some cases, the inactive state can be triggered by a command from a higher layer or a NR node to operate in the unlicensed mode after registration. In some cases, the UE 2502 can automatically enter into the inactive state in the unlicensed operation mode if configured to do so. At 18, according to the illustrated example, the UE 2502 receives data from a higher layer that it needs to send in a UL transmission. Example data includes, but is not limited to, "keep alive" small data, measurement data, data associated with reachability and mobility status of the UE 2502, etc. At 19, the UE 2502 can need to check system information on a broadcast channel. As further examples, at 19, the UE 2502 can need to make radio link measurements, or select a new cell based on the results of system information or radio link measurements. At 20, according to the illustrated example, the UE 2502 synchronizes with a reference signal or an available synchronization pilot (e.g., a first available synchronization pilot) at a symbol timing boundary for allocation of a contention access region. The UE 2502 can also estimate a time advance (TA) for unlicensed UL synchronization at 20. In addition, the UE 2502 can estimate a transmit power (TP) level using the received DL reference signal for the UL transmission.

[0163] At 21, according to the illustrated example, the UE 2502 sends an unlicensed UL transmission to the NR node 2504, specifically the RAN mMTC slice 2510. In some cases, the UE 2502 can contend for the unlicensed UL transmission (without redundancy version) with an initial UL transmission power, which can be defined at the unlicensed setup phase (at 15) or signaled by the NR node 2504 via system information broadcast or RRC signaling. In some cases, the UE 2502 can indicate whether this transmission requires an acknowledgement (ACK) at the transmission power level. The UE 2502 can also include radio link measurements, reachability or mobility status, or other information with the UL data transmission at 21. At 22, the UE 2502 can wait for an ACK response to its UL transmission from the mMTC slice 2510, or the like. If an ACK is required, for example, the UE 2502 can wait until an ACK timer expires. At 23, according to the example, the UE 2502 retransmits the UL message at an adjusted (e.g., increased) TP level if reliable transmission is required. For example, the UE 2502 can contend again if its unlicensed UL data requires reliable transmission. At 24, according to the illustrated example, the NR node 2504, specifically the mMTC slice 2510, sends an ACK message to the UE 2502 indicating that the UL transmission from the UE 2502 was successfully received. The message at 24 can also include a power adjustment value for the UE's next unlicensed UL transmission, providing quasi-closed loop power control. At 25, the UE 2502 can enter an inactive state of the unlicensed operation mode. The inactive state generally refers to a state in which the UE is not transmitting. The inactive state can be pre-configured or triggered by a higher layer command after the unlicensed UL transmission. The inactive state can also be triggered when the UE 2502 receives an ACK from the NR node 2504, for example, when the transmission required an ACK. In some cases, the UE 2502 can automatically enter the inactive state after the unlicensed UL transmission, if the UE 2502 is configured to do so, for example.

[0164] Reference is also made to Figures 31A to 32B , illustrating example embodiments of URLLC devices, which can be similar to the example embodiments of mMTC devices described above, and thus reference is made to Figures 29A to 30BSimilar operations are described. However, with respect to URLLC devices, the context information associated with the UE 2702 can include a value indicating that the UE 2702 can switch between licensed and unlicensed operations. Additionally, at 3A or 2B, the eMBB / URLLC slice 2710 can be selected at the NR node 2704 in order to optimize overall system resource utilization. In an example, at 9C or 8D, the URLLC slice 2714 is selected to meet short latency requirements across the system (network) 2700. In some examples, the UE 2702 utilizes redundancy (e.g., by using multiple contention blocks for transmitting the same data) for its unlicensed UL transmissions. In one example, at 24, the UE 2702 switches from unlicensed to licensed mode of operation after receiving a command from a higher layer. As an example, the UE 2702 can include a traffic monitor that switches from unlicensed to licensed mode of operation to upload images of a traffic incident to the network.

[0165] Turning now to an example unlicensed and licensed UL transmission, as shown in Figure 33A and Figure 33B The UE can be pre-configured with registration to a subscription management node in the core network. Alternatively, the UE can be registered via an "attach" procedure, where the UE can be configured with a network temporary ID for unlicensed access. After registration (if applicable), the UE can set unlicensed related parameters, which can be generally referred to as its unlicensed configuration. In some cases, a UE pre-configured for registration can also be pre-configured with unlicensed parameters. Figure 34A and 34B An example of unlicensed and licensed operation of a URLLC device is depicted, where the UE (URLLC device) transitions between unlicensed and licensed states according to the indication of the NR node. In Figure 35A at 4, the UE is indicated a UE radio network temporary ID. At 9, 10, and 11, the switch to licensed state is indicated by the NR node / TRP / slice, e.g., based on performance (e.g., error rate). Figure 35A and 35B An example of unlicensed and licensed operation for a mMTC device is depicted, where the UE (mMTC device) transitions between unlicensed and licensed states at higher layer (as compared to physical layer) command.

[0166] Reference is now made to Figure 36FIG. 36 depicts an example graphical user interface (GUI) 3600 for configuring a UE for unlicensed operation. Specifically, using the GUI 3600, a user can configure a UE configuration to use only unlicensed operation for transmitting UL data. Alternatively, using the GUI 3600, a user can enable the UE to switch between licensed and unlicensed operation, enabling the UE to operate in a contention state. It will be understood that the GUI can adapt to display or configure additional or alternative parameters as desired. Further, the GUI can display the parameters in various visual depictions as desired.

[0167] Thus, as described above, an apparatus can configure a plurality of devices to operate in an unlicensed mode according to respective unlicensed access allocations, such that when the plurality of devices transmit uplink messages in a network, the messages are transmitted using frequency resources defined by the respective unlicensed access allocations, and the plurality of devices transmit the messages without being granted access to transmit the messages, such that the plurality of devices operate in the unlicensed mode. In an example, the plurality of devices includes a first group of devices and a second group of devices having different operational requirements than the first group of devices. For example, the first group of devices can be ultra-reliable and low latency communication (URLLC) devices, and the second group of devices can be massive machine type communication (mMTC) devices. The apparatus can configure the first group of devices such that when the first group of devices transmit messages uplink in the network, the messages are transmitted within a first sub-band of frequency resources. The apparatus can configure the second group of devices such that when the second group of devices transmit messages uplink in the network, the messages are transmitted within a second sub-band of frequency resources separate from the first sub-band. In an example, the first sub-band defines a first slice of the network for a first type of device or service, and the second sub-band defines a second slice of the network for a second type of device or service different from the first type of device or service. In another example, the apparatus can configure the second group of devices such that when the second group of devices transmit messages uplink in the network, the messages are transmitted within the first sub-band of frequency resources, and the messages are transmitted such that they have a higher priority than messages transmitted by the first group of devices. In another example, as described above, the first sub-band can be shared by licensed enhanced mobile broadband (eMBB) devices, which are overwritten by the URLLC devices, whether or not there is a conflict between their respective message transmissions.

[0168] In yet another example, the apparatus can configure the first group of devices such that when the first group of devices transmits messages uplink in the network, the messages are transmitted within a first sub-band of the frequency resources and within a second sub-band of the frequency resources, where the first sub-band and the second sub-band are shared by the first group of devices and the third group of devices. The apparatus can also configure the second group of devices such that when the second group of devices transmits messages uplink in the network, the messages are transmitted within a guard band between the first sub-band and the second sub-band. As also described above, the apparatus can obtain context information associated with each of the plurality of devices, and based at least in part on the context information, the apparatus can determine that a respective grantless allocation is configured for each of the plurality of devices. The context information can include at least one of a device type associated with each device, a service associated with each device, a latency requirement of each device, a mobility associated with each device, a traffic type associated with each device, or a scheduled time schedule of data transmissions from each device.

[0169] As described above, the apparatus can transmit a first access allocation signal to at least one device, where the first access allocation signal includes an indication of a first access allocation scheme and a first dynamic access configuration time interval. The apparatus can receive a first grantless uplink transmission from the at least one device during the first dynamic access configuration time interval. The first grantless uplink transmission can be transmitted according to the first access allocation scheme. Further, based on traffic associated with the at least one device, the apparatus can transmit a second access allocation signal to the at least one device, where the second access allocation signal includes an indication of a second access allocation scheme and a second dynamic access configuration interval different from the first dynamic access configuration time interval. In response, the apparatus can receive a second grantless uplink transmission during the second dynamic access configuration time interval. In an example, the second grantless uplink transmission is transmitted according to a second allocation scheme different from the first allocation scheme. In another example described above, the apparatus can receive a request from the at least one device during the first dynamic access configuration time interval, and the apparatus can transmit the first allocation access signal to the at least one device in response to the request. The first access allocation signal can be transmitted periodically to a plurality of devices within a coverage area of the apparatus. Alternatively, the first access allocation signal can be transmitted over a first channel dedicated for access allocation signals or a second channel shared with other control signals.

[0170] In yet another example of the above, the apparatus obtains a first dedicated contention region and a contention time interval, and in the absence of a specific resource being granted for transmission, the apparatus transmits a message in the network in uplink during the contention time interval and within the dedicated contention region. The apparatus can receive a negative acknowledgement. In response to the negative acknowledgement, the apparatus can retransmit the message in the network in uplink during the contention time interval and within a second dedicated contention region. In an alternative example, the apparatus waits for a predetermined time, and when the predetermined time elapses while no positive acknowledgement is received, the apparatus retransmits the message in the network in uplink during the contention time interval and within the second dedicated contention region.

[0171] The various techniques described herein can be implemented in connection with hardware, firmware, software or, where appropriate, combinations thereof. Such hardware, firmware, and software can reside in apparatuses located at various nodes of a communication network. The apparatuses can operate singly or in combination with each other to affect the methods described herein. As used herein the terms "apparatus," "network apparatus," "node," "entity," "functionality," "device," and "network node" can be used interchangeably, unless otherwise specified, without restriction.

[0172] The Third Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, the core transport network, and service capabilities - including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE-Advanced standards. 3GPP has begun work on standardization of the next generation of cellular technology, referred to as New Radio (NR), which is also referred to as "5G." 3GPP NR standard development is expected to include definition of a next generation radio access technology (new RAT), which is expected to include provision of a new flexible radio access below 6 GHz, as well as provision of a new ultra-mobile broadband radio access above 6 GHz. The flexible radio access is expected to consist of a new non-backwards compatible radio access in new spectrum below 6 GHz, and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a broad set of 3GPP NR use cases with diverging requirements. The ultra-mobile broadband is expected to include centimeter and millimeter wave spectrum that will provide opportunities for ultra-mobile broadband access for, e.g., indoor applications and hotspots. In particular, the ultra-mobile broadband is expected to share a common design framework with the flexible radio access below 6 GHz, while having centimeter and millimeter wave specific design optimizations.

[0173] It will be appreciated that the above-described unlicensed UL control and management can be performed at the NR node, a transmission and reception point (TRP), a remote radio head (RRH), etc., as well as a central controller in the RAN or a control function in a RAN slice, for different RAN architectures. Embodiments described herein can also apply to the TRP, RRH, central controller, and control function in different RAN architectures.

[0174] 3GPP has identified various use cases that NR is expected to support, resulting in various user experience requirements for data rate, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, indoor ultra-high broadband access, broadband access in crowds, 50+ Mbps everywhere, ultra-low cost broadband access, vehicular mobile broadband), critical communications, massive machine type communications, network operation (e.g., network slicing, routing, migration and interworking, energy savings), and enhanced vehicle-to-everything (eV2X) communications. Specific services and applications in these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based office, first responder connectivity, automotive eCall, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile internet, and virtual reality, among others. All of these use cases and others are contemplated herein.

[0175] Figure 37A An embodiment of an example communications system 100 that can implement the methods and apparatus described and claimed herein is illustrated. As shown, the example communications system 100 can include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, and / or 102d, which generally or collectively can be referred to as WTRU 102, a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e can be any type of device configured to operate and / or communicate in a wireless environment. Although each WTRU 102a, 102b, 102c, 102d, 102e is depicted in Figures 1 A, IB, and / or 1C as a hand-held wireless communications Figures 37A-37EWTRUs can include or be implemented in any type of device or apparatus configured to send and / or receive wireless signals including but not limited to user equipment, mobile station, fixed or mobile subscriber unit, pager, cellular telephone, personal digital assistant (PDA), smartphone, laptop, tablet, netbook, notebook computer, personal computer, wireless sensor, consumer electronics, wearable device such as a smartwatch or smart clothing, medical or eHealth device, robot, industrial equipment, drone, vehicle such as a car, truck, train, or airplane, and the like.

[0176] The communications system 100 can also include a base station 114a and a base station 114b. Base stations 114a can be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or the other networks 112. Base stations 114b can be any type of device configured to wiredly and / or wirelessly interface with at least one of the RRHs (Remote Radio Heads) 118a, 118b and / or TRPs (Transmission and Reception Points) 119a, 119b to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or the other networks 112. RRHs 118a, 118b can be any type of device configured to wirelessly interface with at least one of the WTRUs 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or the other networks 112. TRPs 119a, 119b can be any type of device configured to wirelessly interface with at least one of the WTRUs 102d to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b can be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b can include any number of interconnected base stations and / or network elements.

[0177] The base stations 114a can be a part of the RAN 103 / 104 / 105, which can also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114b can be a part of the RAN 103b / 104b / 105b, which can also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a can be configured to transmit and / or receive wireless signals within a particular geographic area, which can be referred to as a cell (not shown). The base station 114b can be configured to transmit and / or receive wired and / or wireless signals within a particular geographic area, which can be referred to as a cell (not shown). Further, the cell can be divided into cell sectors. For example, the cell associated with the base station 114a can be divided into three sectors. Thus, in an embodiment, the base station 114a can include three transceivers, one for each sector of the cell. In an embodiment, the base station 114a can employ multiple-input multiple-output (MIMO) technology and, therefore, can utilize multiple transceivers for each sector of the cell.

[0178] The base stations 114a can communicate with one or more of the WTRUs 102a, 102b, 102c over the air interface 115 / 116 / 117, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared, ultraviolet, visible light, cmWave, mmWave, etc.). The air interface 115 / 116 / 117 can be established using any suitable radio access technology (RAT).

[0179] The base station 114b can communicate with one or more of the RRHs 118a, 118b and / or TRPs 119a, 119b over a wired or air interface 115b / 116b / 117b, which can be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared, ultraviolet, visible light, cmWave, mmWave, etc.). The air interface 115b / 116b / 117b can be established using any suitable radio access technology (RAT).

[0180] The RRHs 118a, 118b and / or TRPs 119a, 119b can communicate with one or more of WTRUs 102c, 102d over an air interface 115c / 116c / 117c, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115c / 116c / 117c can be established using any suitable radio access technology (RAT).

[0181] More specifically, as noted above, the communications system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, or RRHs 118a, 118b and TRPs 119a, 119b, and WTRUs 102c, 102d in the RAN 103b / 104b / 105b can implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish the air interface 115 / 116 / 117 or 115c / 116c / 117c under an unlicensed radio access (E-UTRA), using wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA).

[0182] In an embodiment, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, or RRHs 118a, 118b and TRPs 119a, 119b, and WTRUs 102c, 102d in the RAN 103b / 104b / 105b can implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can establish the air interface 115 / 116 / 117 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A). In the future, the air interface 115 / 116 / 117 can implement 3GPP NR technology.

[0183] In an embodiment, the base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0184] Figure 37A The base station 114c in FIG. 13 can be a wireless router, Home Node B, Home eNode B, or access point, for example, and can utilize any suitable RAT for facilitating wireless connectivity access points for a local area network (LAN), such as a domain, for example. In an embodiment, the base station 114c and the WTRUs 102e can implement a radio technology such as IEEE 802.11 to establish a wireless LAN (WLAN). In an embodiment, the base station 114c and the WTRUs 102e can implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell. As shown in FIG. 13, the base station 114b can have a direct connection to the Internet 110. Thus, the base station 114c can not be required to access the Internet 110 via the core network 106 / 107 / 109. Figure 37A

[0185] The RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b can be in communication with the core network 106 / 107 / 109, which can be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 can provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication.

[0186] Although not shown in FIG. 13, a base station can be in communication with another base station. Figure 37A ​The RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b and / or the core network 106 / 107 / 109 can also be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b that can be utilizing an E-UTRA radio technology, the core network 106 / 107 / 109 can also be in communication with another RAN (not shown) that utilizes a GSM radio technology.

[0187] The core network 106 / 107 / 109 can also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 can include circuit-switched telephone networks that provide infrastructure for the

[0188] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 can include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d, and 102e can include multiple transceivers for communicating with different wireless networks over different wireless links. For example, Figure 37A The WTRU 102e shown in Figure 1 A can be configured to communicate with the base station 114a, which can employ a cellular-based radio technology, and with the base station 114c, which can employ an IEEE 802 radio technology.

[0189] Figure 37B is a block diagram of an example apparatus or device configured for wireless communication according to the embodiments illustrated herein, such as for example, a WTRU 102. As shown in Figure 37BAs shown in FIG. 10, the example WTRU 102 can include a processor 118, a transceiver 120, a transmit / receive element, antenna 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It should be appreciated that the WTRU 102 can include any sub-combination of the above-referenced elements while remaining consistent with an embodiment. Additionally, embodiments can contemplate that the base stations 114a and 114b and / or the nodes that base stations 114a and 114b can represent, such as but not limited to transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNode-B), a home evolved node-B (HeNB), a home evolved node-B gateway, and proxy nodes, among others, can include any or all of the above-referenced elements. Figure 37B Some or all of the elements depicted in FIG. 10 and described herein.

[0190] The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 can perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to the transceiver 120, which can be coupled to the transmit / receive element 122. While Figure 37B The processor 118 and the transceiver 120 are depicted as separate components, it will be appreciated that the processor 118 and the transceiver 120 can be integrated together in an electronic package or chip.

[0191] The transmit / receive element 122 can be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 115 / 116 / 117. For example, in Figure 37AThe RAN 103 / 104 / 105 and / or the core network 106 / 107 / 109 can also be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105, which can be utilizing an E-UTRA radio technology, the core network 106 / 107 / 109 can also be in communication with another RAN (not shown) that employs a GSM radio technology.

[0192] The core network 106 / 107 / 109 can also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 can include circuit-switched telephone networks that provide infrastructure for the

[0193] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 can include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, and 102d can include multiple transceivers for communicating with different wireless networks over different wireless links. For example, Figure 37A The WTRU 102c shown in Figure 1 A can be configured to communicate with the base station 114a, which can employ a cellular-based radio technology, and with the base station 114b, which can employ an IEEE 802 radio technology.

[0194] Figure 37B is a block diagram of an example apparatus or device configured for wireless communication according to the embodiments illustrated herein, such as for example, a WTRU 102. As shown in Figure 37BAs shown in FIG. 11, the example WTRU 102 can include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It should be appreciated that the WTRU 102 can include any sub-combination of the above-referenced elements while remaining consistent with an embodiment. Additionally, embodiments can contemplate that the base stations 114a and 114b and / or the nodes that base stations 114a and 114b can represent, such as but not limited to transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNode-B), a home evolved node-B (HeNB), a home evolved node-B gateway, and proxy nodes, among others, can include any or all of the above-referenced elements. Figure 37B Some or all of the elements depicted in FIG. 11 and described herein.

[0195] The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 can perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to the transceiver 120, which can be coupled to the transmit / receive element 122. While Figure 37B The processor 118 and the transceiver 120 are depicted as separate components, it is to be understood that the processor 118 and the transceiver 120 can be integrated together in an electronic package or chip.

[0196] The transmit / receive element 122 can be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 115 / 116 / 117. For example, in an embodiment, the transmit / receive element 122 can be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 can be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 can be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0197] In addition, although the transmit / receive element 122 is depicted in the embodiments as a single element, the WTRU 102 can include any number of transmit / receive elements 122. More specifically, the WTRU 102 can employ MIMO technology. In one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117. Figure 37BThe WTRU 102 is in communication with the pico cell 152, which can be within the coverage area 150 of the macro cell 110. The pico cell 152 can be owned by the same operator or a different operator than the macro cell 110. The WTRU 102 can be located in the coverage area 154 of the pico cell 152 and can be outside the coverage area 150 of the macro cell 110. In the embodiment, the WTRU 102 can be in communication with the pico cell 152 via the air interface 115 / 116 / 117.

[0198] The transceiver 120 can be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 can have multi-mode

[0199] The processor 118 of the WTRU 102 can be coupled to, and can receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad / indicators 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad / indicators 128. In addition, the processor 118 can access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 can include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 can include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In embodiments, the processor 118 can access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0200] The processor 118 can receive power from the power source 134 and can be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 can be any suitable device for powering the WTRU 102. For example, the power source 134 can include one or more dry cell batteries, solar cells, fuel cells, and the like.

[0201] The processor 118 can also be coupled to the GPS chipset 136, which can be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or

[0202] The processor 118 can further be coupled to other peripherals 138, which can include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 can include various sensors such as an accelerometer, biometrics (e.g., finger print) sensors, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port or other interconnectivity ports, a vibration device, a television transceiver, a FM radio unit, a digital music player, a media player, a video game player module, an Internet browser, and / or the like.

[0203] The WTRU 102 can be embodied in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smartwatch or smart clothing, a medical or eHealth device, a robot, an industrial appliance, a drone, a vehicle such as a car, truck, train, or airplane. The WTRU 102 can connect to other components, modules, or systems of such apparatuses or devices via one or more interconnectivity interfaces, such as an interconnectivity interface that can be included in the peripherals 138.

[0204] Figure 37C is a system diagram of the RAN 103 and the core network 106 according to an embodiment. As Figure 37CAs shown in FIG. 1A, the RAN 103 can include node-Bs 140a, 140b, 140c, which can each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115. The node-Bs 140a, 140b, 140c can each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 can also include RNCs 142a, 142b. It will be appreciated that the RAN 103 can include any number of node-Bs and RNCs, which can be in communication with each other.

[0205] As Figure 37C As shown in FIG. 1A, the RAN 103 can include node-Bs 140a, 140b, 140c, which can each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115. The node-Bs 140a, 140b, 140c can each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 can also include RNCs 142a, 142b. It will be appreciated that the RAN 103 can include any number of node-Bs and RNCs, which can be in communication with each other.

[0206] Figure 37C The core network 106 shown in FIG. 1A can include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and / or a gateway GPRS support node (GGSN) 150. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements can be owned and / or operated by an entity other than the core network operator.

[0207] The RNC 142a in the RAN 103 can be connected to the MSC 146 in the core network 106 via an IuCS interface. The MSC 146 can be connected to the MGW 144. The MSC 146 and the MGW 144 provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional

[0208] The RNC 142a in the RAN 103 can also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 can be connected to the GGSN 150. The SGSN 148 and the GGSN 150 can provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between and the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0209] As noted above, the core network 106 can also be connected to the networks 112, which can include other wired or wireless networks that are owned and / or operated by other service providers.

[0210] Figure 37D is a system diagram of the RAN 104 and the core network 107 according to an embodiment. As noted above, the RAN 104 can employ E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 can also be in communication with the core network 107.

[0211] The RAN 104 can include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 can include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c can each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c can implement MIMO technology. Thus, the eNode-B 160a, for example, can use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0212] Each of the eNode-Bs 160a, 160b, 160c can be associated with a particular cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and / or downlink, and the like. As shown, the eNode-Bs 160a, 160b, 160c can communicate with one another over an X2 interface. Figure 37D

[0213] Figure 37D ​The core network 107 shown in Figure 1 can include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements are depicted as part of the core network 107, it will be appreciated that any one of these elements can be owned and / or operated by an entity other than the core network operator.

[0214] The MME 162 can be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and can serve as a control node. For example, the MME 162 can be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 can also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0215] The serving gateway 164 can be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via the SI interface. The serving gateway 164 generally routes and forwards user data packets to / from the WTRUs 102a, 102b, 102c. The serving gateway 164 can also perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0216] The serving gateway 164 can also be connected to the PDN gateway 166, which can provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0217] Core network 107 can facilitate communication with other networks. For example, core network 107 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional landline communication equipment. For example, core network 107 may include or can communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between core network 107 and PSTN 108. Furthermore, core network 107 can provide WTRUs 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0218] Figure 37E This is a system diagram of RAN 105 and core network 109 according to an embodiment. RAN 105 may be an access service network (ASN) that uses IEEE 802.16 radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 117. As will be discussed further below, communication links between different functional entities of WTRUs 102a, 102b, 102c, RAN 105, and core network 109 can be defined as reference points.

[0219] like Figure 37E As shown, RAN 105 may include base stations 180a, 180b, 180c and ASN gateway 182; however, it should be understood that RAN 105 may include any number of base stations and ASN gateways while remaining consistent with the embodiment. Base stations 180a, 180b, and 180c may each be associated with a specific cell in RAN 105 and may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 117. In the embodiment, base stations 180a, 180b, and 180c may implement MIMO technology. Therefore, base station 180a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a. Base stations 180a, 180b, and 180c may also provide mobility management functions such as handover triggering, tunnel establishment, radio resource management, service classification, and Quality of Service (QoS) policy enforcement. ASN Gateway 182 can be used as a service aggregation point and can be responsible for paging, subscriber profile caching, routing to the core network 109, etc.

[0220] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 can be defined as an Rl reference point that implements the IEEE 802.16 specification. In addition, each of the WTRUs 102a, 102b, 102c can establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 can be defined as an R2 reference point, which can be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0221] The communication link between each of the base stations 180a, 180b, 180c can be defined as an R8 reference point that includes protocols for facilitating WTRU handovers and the transfer of data between base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 can be defined as an R6 reference point. The R6 reference point can include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.

[0222] As shown in FIG. 1C, the RAN 105 can be connected to the core network 109. The communication link between the RAN 105 and the core network 109 can defined as an R3 reference point that includes protocols for facilitating data transfer and mobility management capabilities, for example. Figure 37E The core network 109 can include a mobile IP home agent (MIP-HA) 184, an authentication, authorization, accounting (AAA) server 186, and a gateway 188. While each of the foregoing elements are depicted as part of the core network 109, it will be appreciated that any one of these elements can be owned and / or operated by an entity other than the core network operator.

[0223] MIP-HA manages IP addresses and enables WTRUs 102a, 102b, and 102c to roam between different ASNs and / or different core networks. MIP-HA 184 provides WTRUs 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110) to facilitate communication between WTRUs 102a, 102b, and 102c and IP-enabled devices. AAA server 186 handles user authentication and supports user services. Gateway 188 facilitates interoperability with other networks. For example, gateway 188 provides WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional landline communication equipment. In addition, gateway 188 can provide WTRUs 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0224] Despite Figure 37E As not shown, however it should be understood that RAN 105 can connect to other ASNs and core network 109 can connect to other core networks. The communication link between RAN 105 and other ASNs can be defined as an R4 reference point, which may include protocols for coordinating the mobility of WTRUs 102a, 102b, and 102c between RAN 105 and other ASNs. The communication link between core network 109 and other core networks can be defined as an R5 reference point, which may include protocols for facilitating interoperability between the home core network and the visited core network.

[0225] Described in this article and Figure 37A , Figure 37C , Figure 37D and Figure 37E The core network entities illustrated in the diagram are identified by the names given to those entities in certain existing 3GPP specifications. However, it should be understood that these entities and functions may be identified by other names in the future, and certain entities or functions may be combined in future specifications released by 3GPP (including future 3GPP NR specifications). Therefore, Figure 37A , Figure 37B , Figure 37C , Figure 37D and Figure 37E The specific network entities and functions described and illustrated herein are provided as examples only, and it should be understood that the subject matter disclosed and claimed herein may be specifically implemented or implemented in any similar communication system, whether or not it is currently defined or will be defined in the future.

[0226] Figure 37F It can be implemented in practice. Figure 37A , Figure 37C , Figure 37D and Figure 37E The diagram illustrates an exemplary computing system 90 of one or more devices in a communication network (such as certain nodes or functional entities in RAN 103 / 104 / 105, core network 106 / 107 / 108, PSTN 108, Internet 110, or other networks 112). The computing system 90 may include a computer or server and may be controlled primarily by computer-readable instructions, which may be in the form of software, regardless of where or by what means such software is stored or accessed. Such computer-readable instructions may be executed within a processor 91 to enable the computing system 90 to function. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that enables the computing system 90 to operate within the communication network. Coprocessor 81 is an optional processor, distinct from main processor 91, that can perform additional functions or assist processor 91. Processor 91 and / or coprocessor 81 can receive, generate, and process data relating to the methods and apparatus disclosed herein.

[0227] In operation, processor 91 fetches instructions, decodes and executes them, and transfers information to and from other resources via the main data transfer path (system bus 80) of the computing system. This system bus connects components within the computing system 90 and defines the medium for data exchange. System bus 80 typically includes data lines for transmitting data, address lines for transmitting addresses, and control lines for transmitting interrupts and for the operating system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0228] Memory that is coupled to system bus 80 includes random access memory (RAM) 82 and read only memory (ROM) 93. Such memory stores instructions and data that are needed by the processor 91 to implement the desired functions. ROM 93 is generally used to store instructions and / or data that are read during boot-up but that are not greatly altered. RAM 82 can also provide

[0229] Additionally, computing system 90 can contain peripherals controller (I / O controller) 83 responsible for managing input and output for the peripherals 84 of the computing system 90. Peripherals controller 83 can manage peripherals such as printer 94, keyboard 84, mouse 95 and disk drives 85.

[0230] Display 86 is controlled by display controller 96 that includes electronic components required to generate a video signal that is sent to display 86. The video signal that is generated by display controller 96 can include text, graphical, animated and video data. The video data can be provided in the form of a graphical user interface (GUI). Display 86 can be implemented with a CRT-based video display, an LCD-based flat-panel display, gas plasma-based flat-panel display, or a touch-panel. Display controller 96 includes the electronic components required to generate a video signal that is sent to display 86.

[0231] Additionally, computing system 90 can contain communication circuitry, such as for example a network adapter 97, that can be used to connect computing system 90 to an external communications network, such as a Local Area Network (LAN), Wide Area Network (WAN) or the Internet through a variety of wired and wireless communications medium (not shown). Figure 37A 、 Figure 37B 、 Figure 37C 、 Figure 37D and Figure 37E RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108, Internet 110, or Other Networks 112 so that computing system 90 can communicate with other nodes or functional entities of those networks. The communication circuitry alone or in combination with the processor 91 can be used to perform the transmitting and receiving steps of certain apparatuses, nodes or functional entities described herein.

[0232] It should be appreciated that any or all of the apparatuses, systems, methods, and processes described herein can be embodied in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium which instructions, when executed by a processor (such as processor 118 or 91), cause the processor to perform and / or implement the systems, methods, and processes described herein. Specifically, any of the steps, operations, or functions described herein can be implemented in the form of such computer executable instructions which are executed by a processor of an apparatus or computing system configured for wireless and / or wired network communications. Computer readable storage media include volatile and nonvolatile, removable and non-removable media implemented in any non- transitory (e.g., tangible or physical) method or technology for storage of information such as computer readable instructions, data structures, program code, computer programs, metadata, and / or other data. Computer readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible or physical medium which can be used to store the desired information and which can be accessed by a computing system.

[0233] The following is a list of acronyms related to access technologies that can appear in the above description. Unless otherwise specified, the acronyms used herein refer to the corresponding terms listed below.

[0234] ACK acknowledgement

[0235] AID association identifier (802.11)

[0236] AP access point (802.11)

[0237] APN access point name

[0238] AS access stratum

[0239] BS base station

[0240] CA collision avoidance

[0241] CD collision detection

[0242] CFI control format indicator

[0243] CN core network

[0244] CMAS commercial mobile alert system

[0245] C-RNTI cell radio network temporary identifier

[0246] CSMA carrier sense multiple access

[0247] CSMA / CD Carrier Sense Multiple Access with Collision Detection

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

[0249] DCA Dedicated Conflict Area

[0250] DCI Downlink Control Information

[0251] DACTI Dynamic Access Configuration Time Interval

[0252] DL Downlink

[0253] DRX Discontinuous Reception

[0254] ECGI E-UTRAN Cell Global Identifier

[0255] ECM EPS Connection Management

[0256] eMBB Enhanced Mobile Broadband

[0257] EMM EPS Mobility Management

[0258] eNB Evolved Node B

[0259] ETWS Earthquake and Tsunami Warning System

[0260] E-UTRA Evolved Universal Terrestrial Radio Access

[0261] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0262] FDM Frequency Division Multiplexing

[0263] FFS For Further Study

[0264] GERAN GSM EDGE Radio Access Network

[0265] GSM Global System for Mobile Communications

[0266] GUTI Globally Unique Temporary UE Identity

[0267] HE High Efficiency

[0268] HSS Home Subscriber Server

[0269] IE Information Element

[0270] IMSI International Mobile Subscriber Identity

[0271] IMT International Mobile Telecommunication

[0272] KPI Key Performance Indicator

[0273] LTE Long Term Evolution

[0274] MAC Medium Access Control

[0275] MBMS Multimedia Broadcast Multicast Service

[0276] MCL Maximum Coupling Loss

[0277] MIB Master Information Block

[0278] MME Mobile Management Entity

[0279] MTC Machine Type Communication

[0280] mMTC Massive Machine Type Communication

[0281] NACK Negative Acknowledgment

[0282] NAS Non-Access Stratum

[0283] NR New Radio

[0284] OBO OFDM Backoff (802.11)

[0285] OFDM Orthogonal Frequency Division Multiplexing

[0286] PDCCH Physical Downlink Control Channel

[0287] PDSCH Physical Downlink Shared Channel

[0288] PHY Physical Layer

[0289] PCFICH Physical Control Format Indicator Channel

[0290] PDCP Packet Data Convergence Protocol

[0291] PHICH Physical Hybrid-ARQ Indicator Channel

[0292] PPDU PLCP Protocol Data Unit (802.11)

[0293] PRACH Physical Random Access Channel

[0294] PRB Physical Resource Block

[0295] PUCCH Physical Uplink Control Channel

[0296] PUSCH Physical Uplink Shared Channel

[0297] QoS Quality of Service

[0298] RA Random Access

[0299] RACH random access channel

[0300] RAN radio access network (3GPP)

[0301] RMSU reachability and mobility status update

[0302] RB resource block

[0303] RLC radio link control

[0304] RNTI radio network temporary identifier

[0305] RRC radio resource control

[0306] RU resource unit (802.11)

[0307] SI system information

[0308] SIB system information block

[0309] SR scheduling request

[0310] STA station (802.11)

[0311] TAI tracking area indicator

[0312] TAU tracking area update

[0313] TBD to be defined

[0314] TDM time division multiplexing

[0315] TEID tunnel endpoint ID

[0316] TRP transmission and reception point

[0317] TTI transmission time interval

[0318] UCI uplink control information

[0319] UE user equipment

[0320] UL uplink

[0321] UR / LL ultra-reliable-low latency

[0322] URLLC ultra-reliable low-latency communication

[0323] This written description uses examples to disclose the application, including the best mode, and also to enable any person skilled in the art to practice the application, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the application is defined by the claims, and can include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent

Claims

1. A wireless transmit / receive unit (WTRU) comprising: a receiver configured to receive one or more grant-free configurations including at least one of a first grant-free allocation or a second grant-free allocation, the first grant-free allocation indicating first time and frequency resources and the second grant-free allocation indicating second time and frequency resources; a transmitter configured to transmit a message via an uplink channel of an access network using the first time and frequency resources; and when a transmission redundancy value is greater than one, the transmitter is further configured to retransmit the message via the uplink channel of the access network using the first time and frequency resources or the second time and frequency resources.

2. The WTRU of claim 1, wherein, the one or more grant-free configurations include at least a first grant-free configuration and a second grant-free configuration, the first grant-free configuration including the first grant-free allocation and the second grant-free configuration including the second grant-free allocation.

3. The WTRU of claim 1, wherein, the one or more grant-free configurations are received via static configuration carried via a dedicated radio resource control message.

4. The WTRU of claim 1, wherein, the first grant-free configuration and the second grant-free allocation are indicated via dynamic indication carried via a downlink control channel from the access network.

5. The WTRU of claim 4, wherein, an activation indication and a deactivation indication are received on the downlink control channel from the access network.

6. The WTRU of claim 4, wherein, the downlink control channel is a dedicated control channel.

7. The WTRU of claim 4, wherein, the downlink control channel is scrambled using an identifier of the WTRU.

8. The WTRU of claim 7, wherein, the WTRU is assigned a radio network temporary ID for grant-free access.

9. The WTRU of claim 1, wherein, the first grant-free configuration and the second grant-free allocation include a time interval.

10. The WTRU of claim 9, wherein, the time interval includes one or more respective contention spaces available for selecting a grant-free transmission.

11. The WTRU of claim 1, wherein, the one or more grant-free configurations further include a transmission redundancy value and a redundancy version associated with the transmission redundancy value.

12. The WTRU of claim 1, wherein, the one or more grant-free configurations further include at least one of a modulation and coding scheme or a frequency hopping scheme.

13. The WTRU of claim 1, the transmitter is further configured to transmit an uplink grant-free transmission, the uplink grant-free transmission including a front-loaded reference signal allocated at a first symbol of the uplink grant-free transmission.

14. The WTRU of claim 13, wherein, the front-loaded reference signal is used to indicate that the WTRU is performing a grant-free uplink transmission.

15. A method for use in a wireless transmit / receive unit (WTRU), the method comprising: receiving one or more grant-free configurations including at least one of a first grant-free allocation or a second grant-free allocation, the first grant-free allocation indicating first time and frequency resources and the second grant-free allocation indicating second time and frequency resources; transmitting a message via an uplink channel of an access network using the first time and frequency resources; and when a transmission redundancy value is greater than one, retransmitting the message via the uplink channel of the access network using the first time and frequency resources or the second time and frequency resources.

Images