Patent Application
20240235772
Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to collision handling for sounding reference signal (SRS) transmission.
In the 3GPP New Radio (NR) Release (Rel)-15 spec, different types of SRS resource sets are supported. The SRS resource set is configured with a parameter of ‘usage’, which can be set to ‘beamManagement’, ‘codebook’, ‘nonCodebook’ or ‘antennaSwitching’. The SRS resource set configured for ‘beamManagement’ is used for beam acquisition and uplink beam indication using SRS. The SRS resource set configured for ‘codebook’ and ‘nonCodebook’ is used to determine the uplink (UL) precoding with explicit indication by transmission precoding matrix index (TPMI) or implicit indication by SRS resource index (SRI). Finally, the SRS resource set configured for ‘antennaSwitching’ is used to acquire downlink (DL) channel state information (CSI) using SRS measurements in the UE by leveraging reciprocity of the channel in time domain duplexing (TDD) systems. For SRS transmission, the time domain behavior could be periodic, semi-persistent or aperiodic.
The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase “A or B” means (A), (B), or (A and B).
As discussed above, in the 3GPP NR Rel-15 specification, different types of SRS resource sets are supported. The SRS resource set is configured with a parameter of ‘usage’, which can be set to ‘beamManagement’, ‘codebook’, ‘nonCodebook’ or ‘antennaSwitching’. The SRS resource set configured for ‘beamManagement’ is used for beam acquisition and uplink beam indication using SRS. The SRS resource set configured for ‘codebook’ and ‘nonCodebook’ is used to determine the UL precoding with explicit indication by TPMI or implicit indication by SRI. Finally, the SRS resource set configured for ‘antennaSwitching’ is used to acquire DL CSI using SRS measurements in the UE by leveraging reciprocity of the channel in TDD systems. For SRS transmission, the time domain behavior could be periodic, semi-persistent or aperiodic.
When SRS resource set is configured as ‘aperiodic’, the SRS resource set also includes configuration of trigger state(s) (aperiodicSRS-ResourceTrigger, aperiodicSRS-ResourceTriggerList). The triggering state(s) defines which DCI codepoint(s) triggers the corresponding SRS resource set transmission.
In 3GPP Rel-17 and/or another future specification, the DCI may indicate an available uplink slot for transmission of the triggered SRS. In carrier aggregation, it is possible that multiple aperiodic SRS resource sets are triggered to be transmitted in the same slot over different component carriers (CCs). The current SRS collision handling does not consider the collision among aperiodic SRS resource sets across different carriers.
Various embodiments herein provide techniques for collision handling among aperiodic SRS across different carriers, e.g., including one or more dropping rules. In some embodiments, if the SRS transmission is prior to or after PUSCH/PUCCH, and the beam/antenna/panel switching is required between the transmission of SRS and PUSCH/PUCCH, then a guard period may be configured. Additionally, or alternatively, if the time between SRS and PUSCH/PUCCH is not sufficient for beam/antenna/panel switching, then a dropping rule may be defined to handle the collision.
In an embodiment, when multiple aperiodic SRS resource sets are triggered to be transmitted in the same slot across different component carriers (CCs), if the simultaneous transmission over multiple CCs exceeds UE's capability, there should be some rules to handle the collision.
In one example, the SRS prioritization is based on SRS usage. For example, the prioritization of usage is {antenna switching}>{codebook/non-codebook}>{beam management}. If the collision happens among SRS with the same usage, then the SRS could be further prioritized by component carrier ID or SRS resource set ID.
As shown in
In another example, the SRS prioritization is based on component carrier ID, e.g., the SRS over CC with higher ID or lower ID should be prioritized.
In another example, the SRS prioritization is based on SRS resource set ID, e.g., the SRS resource set with higher ID or lower ID should be prioritized.
In another embodiment, when aperiodic SRS triggered in one CC collides with periodic/semi-persistent SRS over another CC, if the simultaneous transmission over multiple CCs exceeds UE's capability, there should be some rules to handle the collision.
In one example, the aperiodic SRS should be prioritized over periodic/semi-persistent SRS. Or the periodic/semi-persistent SRS is prioritized.
In another example, the SRS prioritization is based on SRS usage. For example, the prioritization of usage is {antenna switching}>{codebook/non-codebook}>{beam management}. If the collision happens among SRS with the same usage, then the SRS could be further prioritized by component carrier ID or SRS resource set ID.
In another example, the SRS prioritization is based on component carrier ID, e.g., the SRS over CC with higher ID or lower ID should be prioritized.
In another example, the SRS prioritization is based on SRS resource set ID, e.g., the SRS resource set with higher ID or lower ID should be prioritized.
In another embodiment, when periodic SRS in one CC collides with semi-persistent SRS over another CC, if the simultaneous transmission over multiple CCs exceeds UE's capability, there should be some rules to handle the collision.
In one example, the semi-persistent SRS should be prioritized over periodic SRS. Or the periodic SRS is prioritized.
In another example, the SRS prioritization is based on SRS usage. For example, the prioritization of usage is {antenna switching}>{codebook/non-codebook}>{beam management}. If the collision happens among SRS with the same usage, then the SRS could be further prioritized by component carrier ID or SRS resource set ID.
In another example, the SRS prioritization is based on component carrier ID, e.g., the SRS over CC with higher ID or lower ID should be prioritized.
In another example, the SRS prioritization is based on SRS resource set ID, e.g., the SRS resource set with higher ID or lower ID should be prioritized.
In another embodiment, new UE capability could be introduced indicating whether the UE supports simultaneous aperiodic SRS transmission over multiple CCs. Another UE capability could be introduced indicating whether UE supports simultaneous aperiodic SRS/periodic SRS/semi-persistent SRS transmission over multiple CCs.
In another embodiment, if the UE doesn't support simultaneous transmission for aperiodic SRS over different CC, or simultaneous transmission for aperiodic and periodic/semi-persistent SRS over different CC, or simultaneous transmission for periodic and semi-persistent SRS over different CC, the UE is not expected to be configured with overlapped transmission.
In an embodiment, for SRS with antenna switching, if the UE needs to switch antenna panel when transmitting the SRS resources within the same SRS resource set, additional guard period, for example, N symbols (N should be larger than or equal to the panel switching time), should be configured between the SRS resources.
In another embodiment, for SRS with antenna switching, if the UE needs to switch antenna panel among different SRS resource sets, the guard period, for example, N symbols (N should be larger than or equal to the panel switching time), should be configured between the SRS resource sets.
In another embodiment, for SRS with antenna switching, if the SRS transmission is before or after other uplink transmission, e.g., PUSCH/PUCCH, and the UE needs to switch antenna/beam/panel between the SRS and PUSCH/PUCCH, the guard period, for example, N symbols (N should be larger than or equal to the beam/antenna/panel switching time), should be configured between the SRS and PUSCH/PUCCH. This embodiment can also be applied to two SRS resource sets, e.g., the guard period, for example, N symbols (N should be larger than or equal to the beam/antenna/panel switching time), should be configured between the SRS resource sets.
In another embodiment, for SRS with antenna switching, if the SRS transmission is before or after other uplink transmission, e.g., PUSCH/PUCCH, and the time between SRS and PUSCH/PUCCH is not sufficient for beam/antenna/panel switching, the collision handling should be applied.
In one example, the PUSCH/PUCCH should be prioritized for transmission. Some OFDM symbols for SRS transmission will be dropped.
In another example, the SRS should be prioritized for transmission. Some OFDM symbols for PUSCH/PUCCH will be dropped.
This embodiment can also be applied to two SRS resource sets, e.g., if the time between SRS resource sets is not sufficient for beam/antenna/panel switching, the collision handling should be applied. In one example, some OFDM symbols for the first or the second SRS resource set should be dropped. In some embodiments, the prioritization may be based on:
In another embodiment, for SRS with antenna switching, if the time period between two SRS resources is larger than the required gap length (e.g., the two SRS resources could be located in the same slot, or the two SRS resources could be located in two consecutive slots), then the OFDM symbols used for gap period should be predefined or configured by RRC/MAC-CE or indicated by DCI.
In one example, if the required gap is Y symbols and the time period between two SRS resources is larger than Y symbols, then the Y symbols following the first SRS resource should be used as gap period.
For example, the required gap length is 2 symbols, and the time period between the two SRS resources is 5 symbols, then the first two OFDM symbols after the first SRS resource is used as gap.
In another example, if the required gap is Y symbols and the time period between two SRS resources is larger than Y symbols, then the Y symbols prior to the second SRS resource should be used as gap period.
In another embodiment, for SRS with antenna switching, if the required gap is Y symbols and the time period between two SRS resources is larger than Y symbols (e.g., the two SRS resources could be located in the same slot, or the two SRS resources could be located in two consecutive slots), when performing collision handling, the OFDM symbols which are predefined/configured to be used as gap should be applied with the same priority handling rule as if SRS was configured.
For example, the required gap length is 2 symbols, and the time period between the two aperiodic SRS resources is 5 symbols, and the first two symbols after the first SRS resource is used as gap. When there is PUCCH carrying periodic CSI reports in the first two symbols after the first SRS resource, the PUCCH should be dropped.
In another embodiment, for SRS with antenna switching, if the required gap is Y symbols and the time period between two SRS resources is larger than Y symbols (the two SRS resources could be located in the same slot, or the two SRS resources could be located in two consecutive slots), then all the symbols between the two SRS resources are used as gap period, e.g., there is no other uplink signal/channel transmitted in the period between the two SRS resources.
When performing collision handling, all the OFDM symbols between the two SRS resources may be applied with the same priority handling rule as if SRS was configured.
In another embodiment, for SRS with antenna switching, if the required gap is Y symbols and the time period between two SRS resources is larger than Y symbols (e.g., the two SRS resources could be located in the same slot, or the two SRS resources could be located in two consecutive slots), other uplink transmission could happen in the period between the two SRS resources excluding the symbols which are predefined/configured to be used as gap. Alternatively, other uplink transmission may be performed in all the symbols between the two SRS resources.
In an embodiment, for SRS with antenna switching, during the gap period of Y symbol(s) between two SRS resource (the two SRS resources could be located in the same slot, or the two SRS resources could be located in two consecutive slots), the UE should not transmit any other uplink signal/channel, no matter the results of collision handling between the gap period and other signal/channel (or no matter the results of collision handling between SRS and other uplink signal/channel).
In another example, during the gap period, the UE could transmit other uplink signal/channel according to the results of collision handling between the gap period and other signal/channel (or according to the results of collision handling between SRS and other signal/channel). For example, if a first SRS occasion before the gap period and a second SRS occasion after the gap period are dropped, then another uplink message (e.g., PUSCH, PUCCH, etc.) may be transmitted in the gap period.
The interval between two SRS resources could be equal to or larger than the gap period of Y symbols. If the interval is larger than Y symbols, the position of the gap should be predefined or configured, or the entire interval is treated as gap period.
In another embodiment, for SRS with antenna switching, when the number of gap symbol(s) between two SRS resource is larger than one (the two SRS resources could be located in the same slot, or the two SRS resources could be located in two consecutive slots), all the symbols of the gap should be treated together for collision handling, e.g., all the gap symbols have the same priority. If any one of the gap symbols collides with other high priority signal/channel, then the entire gap period will be low priority. Alternatively, the collision handling for the gap period could be performed symbol by symbol.
In another embodiment, for SRS with antenna switching, during the gap period of Y symbol(s) between two SRS resource (the two SRS resources could be located in the same slot, or the two SRS resources could be located in two consecutive slots), the collision handling should be based on the first symbol of the gap period, e.g., the priority of the entire gap period is determined by the first symbol of the gap.
If the first symbol is high priority or there is no collision, then the entire gap period is high priority, e.g., the UE should not transmit any other uplink signal/channel in the entire gap period.
If the first symbol is low priority, then the entire gap period should be dropped.
Alternatively, the priority of the entire gap period is determined by the last symbol of the gap.
In another embodiment, for SRS with antenna switching, the priority of the gap period of Y symbol(s) between two SRS resource (the two SRS resources could be located in the same slot, or the two SRS resources could be located in two consecutive slots) should follow the SRS resource prior to the gap period (or follow the last OFDM symbol of the SRS resource prior to the gap period).
For example, if the SRS resource prior to the gap period is high priority or there is no collision, then the entire gap period is high priority. The UE should not transmit any other uplink signal/channel in the entire gap period.
If the SRS resource prior to the gap is low priority, then the entire gap period should be dropped.
In another example, the priority of the gap period should follow the SRS resource after the gap period (or follow the first OFDM symbols of the SRS resource after the gap period).
In another embodiment, all the SRS resources and the gap period should be treated together for collision handling, e.g., all the SRS resources and the gap period have the same priority.
These embodiments may be applied to aperiodic SRS, periodic SRS or semi-persistent SRS.
Additionally, the various embodiments herein may be applied to other SRS usages, such as codebook/non-codebook, beam management, etc.
Furthermore, while embodiments are described with reference to the entire SRS occasion or gap period being dropped, in other examples of the embodiments herein, when collision happens only the overlapped symbols are dropped (e.g., the non-overlapped symbols are still transmitted).
The network 600 may include a UE 602, which may include any mobile or non-mobile computing device designed to communicate with a RAN 604 via an over-the-air connection. The UE 602 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc.
In some embodiments, the network 600 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
In some embodiments, the UE 602 may additionally communicate with an AP 606 via an over-the-air connection. The AP 606 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 604. The connection between the UE 602 and the AP 606 may be consistent with any IEEE 802.11 protocol, wherein the AP 606 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 602, RAN 604, and AP 606 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 602 being configured by the RAN 604 to utilize both cellular radio resources and WLAN resources.
The RAN 604 may include one or more access nodes, for example, AN 608. AN 608 may terminate air-interface protocols for the UE 602 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 608 may enable data/voice connectivity between CN 620 and the UE 602. In some embodiments, the AN 608 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 608 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 608 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
In embodiments in which the RAN 604 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 604 is an LTE RAN) or an Xn interface (if the RAN 604 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
The ANs of the RAN 604 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 602 with an air interface for network access. The UE 602 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 604. For example, the UE 602 and RAN 604 may use carrier aggregation to allow the UE 602 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
The RAN 604 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
In V2X scenarios the UE 602 or AN 608 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
In some embodiments, the RAN 604 may be an LTE RAN 610 with eNBs, for example, eNB 612. The LTE RAN 610 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.
In some embodiments, the RAN 604 may be an NG-RAN 614 with gNBs, for example, gNB 616, or ng-eNBs, for example, ng-eNB 618. The gNB 616 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 616 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 618 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 616 and the ng-eNB 618 may connect with each other over an Xn interface.
In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 614 and a UPF 648 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 614 and an AMF 644 (e.g., N2 interface).
The NG-RAN 614 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 602 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 602, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 602 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 602 and in some cases at the gNB 616. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
The RAN 604 is communicatively coupled to CN 620 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 602). The components of the CN 620 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 620 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 620 may be referred to as a network slice, and a logical instantiation of a portion of the CN 620 may be referred to as a network sub-slice.
In some embodiments, the CN 620 may be an LTE CN 622, which may also be referred to as an EPC. The LTE CN 622 may include MME 624, SGW 626, SGSN 628, HSS 630, PGW 632, and PCRF 634 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 622 may be briefly introduced as follows.
The MME 624 may implement mobility management functions to track a current location of the UE 602 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
The SGW 626 may terminate an S1 interface toward the RAN and route data packets between the RAN and the LTE CN 622. The SGW 626 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
The SGSN 628 may track a location of the UE 602 and perform security functions and access control. In addition, the SGSN 628 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 624; MME selection for handovers; etc. The S3 reference point between the MME 624 and the SGSN 628 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
The HSS 630 may include a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The HSS 630 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 630 and the MME 624 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 620.
The PGW 632 may terminate an SGi interface toward a data network (DN) 636 that may include an application/content server 638. The PGW 632 may route data packets between the LTE CN 622 and the data network 636. The PGW 632 may be coupled with the SGW 626 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 632 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 632 and the data network 636 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 632 may be coupled with a PCRF 634 via a Gx reference point.
The PCRF 634 is the policy and charging control element of the LTE CN 622. The PCRF 634 may be communicatively coupled to the app/content server 638 to determine appropriate QoS and charging parameters for service flows. The PCRF 632 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
In some embodiments, the CN 620 may be a 5GC 640. The 5GC 640 may include an AUSF 642, AMF 644, SMF 646, UPF 648, NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, and AF 660 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 640 may be briefly introduced as follows.
The AUSF 642 may store data for authentication of UE 602 and handle authentication-related functionality. The AUSF 642 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 640 over reference points as shown, the AUSF 642 may exhibit an Nausf service-based interface.
The AMF 644 may allow other functions of the 5GC 640 to communicate with the UE 602 and the RAN 604 and to subscribe to notifications about mobility events with respect to the UE 602. The AMF 644 may be responsible for registration management (for example, for registering UE 602), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 644 may provide transport for SM messages between the UE 602 and the SMF 646, and act as a transparent proxy for routing SM messages. AMF 644 may also provide transport for SMS messages between UE 602 and an SMSF. AMF 644 may interact with the AUSF 642 and the UE 602 to perform various security anchor and context management functions. Furthermore, AMF 644 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 604 and the AMF 644; and the AMF 644 may be a termination point of NAS (N1) signaling, and perform NAS ciphering and integrity protection. AMF 644 may also support NAS signaling with the UE 602 over an N3 IWF interface.
The SMF 646 may be responsible for SM (for example, session establishment, tunnel management between UPF 648 and AN 608); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 648 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 644 over N2 to AN 608; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 602 and the data network 636.
The UPF 648 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 636, and a branching point to support multi-homed PDU session. The UPF 648 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 648 may include an uplink classifier to support routing traffic flows to a data network.
The NSSF 650 may select a set of network slice instances serving the UE 602. The NSSF 650 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 650 may also determine the AMF set to be used to serve the UE 602, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 654. The selection of a set of network slice instances for the UE 602 may be triggered by the AMF 644 with which the UE 602 is registered by interacting with the NSSF 650, which may lead to a change of AMF. The NSSF 650 may interact with the AMF 644 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 650 may exhibit an Nnssf service-based interface.
The NEF 652 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 660), edge computing or fog computing systems, etc. In such embodiments, the NEF 652 may authenticate, authorize, or throttle the AFs. NEF 652 may also translate information exchanged with the AF 660 and information exchanged with internal network functions. For example, the NEF 652 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 652 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 652 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 652 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 652 may exhibit an Nnef service-based interface.
The NRF 654 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 654 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 654 may exhibit the Nnrf service-based interface.
The PCF 656 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 656 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 658. In addition to communicating with functions over reference points as shown, the PCF 656 exhibit an Npcf service-based interface.
The UDM 658 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 602. For example, subscription data may be communicated via an N8 reference point between the UDM 658 and the AMF 644. The UDM 658 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 658 and the PCF 656, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 602) for the NEF 652. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 658, PCF 656, and NEF 652 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 658 may exhibit the Nudm service-based interface.
The AF 660 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
In some embodiments, the 5GC 640 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 602 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 640 may select a UPF 648 close to the UE 602 and execute traffic steering from the UPF 648 to data network 636 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 660. In this way, the AF 660 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 660 is considered to be a trusted entity, the network operator may permit AF 660 to interact directly with relevant NFs. Additionally, the AF 660 may exhibit an Naf service-based interface.
The data network 636 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 638.
The UE 702 may be communicatively coupled with the AN 704 via connection 706. The connection 706 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.
The UE 702 may include a host platform 708 coupled with a modem platform 710. The host platform 708 may include application processing circuitry 712, which may be coupled with protocol processing circuitry 714 of the modem platform 710. The application processing circuitry 712 may run various applications for the UE 702 that source/sink application data. The application processing circuitry 712 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
The protocol processing circuitry 714 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 706. The layer operations implemented by the protocol processing circuitry 714 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
The modem platform 710 may further include digital baseband circuitry 716 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 714 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
The modem platform 710 may further include transmit circuitry 718, receive circuitry 720, RF circuitry 722, and RF front end (RFFE) 724, which may include or connect to one or more antenna panels 726. Briefly, the transmit circuitry 718 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 720 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 722 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 724 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 718, receive circuitry 720, RF circuitry 722, RFFE 724, and antenna panels 726 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
In some embodiments, the protocol processing circuitry 714 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
A UE reception may be established by and via the antenna panels 726, RFFE 724, RF circuitry 722, receive circuitry 720, digital baseband circuitry 716, and protocol processing circuitry 714. In some embodiments, the antenna panels 726 may receive a transmission from the AN 704 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 726.
A UE transmission may be established by and via the protocol processing circuitry 714, digital baseband circuitry 716, transmit circuitry 718, RF circuitry 722, RFFE 724, and antenna panels 726. In some embodiments, the transmit components of the UE 704 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 726.
Similar to the UE 702, the AN 704 may include a host platform 728 coupled with a modem platform 730. The host platform 728 may include application processing circuitry 732 coupled with protocol processing circuitry 734 of the modem platform 730. The modem platform may further include digital baseband circuitry 736, transmit circuitry 738, receive circuitry 740, RF circuitry 742, RFFE circuitry 744, and antenna panels 746. The components of the AN 704 may be similar to and substantially interchangeable with like-named components of the UE 702. In addition to performing data transmission/reception as described above, the components of the AN 708 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
The processors 810 may include, for example, a processor 812 and a processor 814. The processors 810 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
The memory/storage devices 820 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 820 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
The communication resources 830 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 or other network elements via a network 808. For example, the communication resources 830 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein. The instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor's cache memory), the memory/storage devices 820, or any suitable combination thereof. Furthermore, any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory/storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.
In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of
While processes 900, 1000, and 1100 are described from the perspective of the UE, it will be understood that similar processes may be performed at the network side (e.g., by a gNB).
For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
Some non-limiting Examples of various embodiments are provided below.
Example A1 may include one or more computer-readable media (CRM) having instructions, stored thereon, that when executed by one or more processors cause a user equipment (UE) to: receive configuration information for a first sounding reference signal (SRS) resource set and a second SRS resource set, wherein there is a guard period between SRS occasions of the first SRS resource set and respective SRS occasions of the second SRS resource set; determine that a first SRS occasion of the first SRS resource set and a second SRS occasion of the second SRS resource set are dropped based on a collision handling rule; and encode an uplink message for transmission in the guard period between the first and second SRS occasions based on the determination.
Example A2 may include the one or more CRM of example A1, wherein the first SRS resource set, the second resource set, and the guard period have a same priority associated with the collision handling rule.
Example A3 may include the one or more CRM of example A1, wherein the first and second SRS occasions are aperiodic SRS occasions.
Example A4 may include the one or more CRM of example A1, wherein the first and second SRS occasions are in a same slot.
Example A5 may include the one or more CRM of example A1, wherein the first and second SRS occasions are in different slots.
Example A6 may include the one or more CRM of any one of examples A1-A5, wherein the first and second SRS resource sets are in different component carriers.
Example A7 may include the one or more CRM of any one of examples A1-A5, wherein the uplink message is a physical uplink shared channel (PUSCH) message or a physical uplink control channel (PUCCH) message.
Example A8 may include an apparatus to be implemented in a user equipment (UE), the apparatus comprising: a memory to store a collision handling rule; and processor circuitry coupled to the memory, the processor circuitry to: determine to drop a first sounding reference signal (SRS) occasion of a first SRS resource set and a second SRS occasion of a second SRS resource set based on the collision handling rule, wherein the first and second SRS occasions are in different component carriers; and drop a gap period between the first and second SRS occasions based on the determination.
Example A9 may include the apparatus of example A8, wherein the processor circuitry is further to encode a physical uplink shared channel (PUSCH) message or a physical uplink control channel (PUCCH) message for transmission in the gap period.
Example A10 may include the apparatus of example A8, wherein the first SRS resource set, the second resource set, and the gap period have a same priority associated with the collision handling rule.
Example A11 may include the apparatus of example A8, wherein the first and second SRS occasions are aperiodic SRS occasions.
Example A12 may include the apparatus of any one of examples A8-A11, wherein the first and second SRS occasions are in a same slot.
Example A13 may include the apparatus of any one of examples A8-A12, wherein the first and second SRS occasions are in different slots.
Example A14 may include one or more computer-readable media (CRM) having instructions, stored thereon, that when executed by one or more processors cause a user equipment (UE) to: determine that multiple aperiodic SRS resource sets are triggered to be transmitted in a same slot across different component carriers (CCs); and drop transmission of one or more of the SRS resource sets according to a dropping rule.
Example A15 may include the one or more CRM of example A14, wherein the transmission is dropped if simultaneous transmission of the multiple aperiodic SRS resource sets over multiple CCs exceeds a capability of the UE.
Example A16 may include the one or more CRM of example A14, wherein the dropping rule includes to prioritize the respective SRS resource sets based on a SRS usage.
Example A17 may include the one or more CRM of example A16, wherein the SRS resource sets are prioritized further based on a component carrier ID or a SRS resource set ID.
Example A18 may include the one or more CRM of example A14, wherein a time period between a first SRS resource and a second SRS resource is greater than a required gap length, and wherein the instructions, when executed, are further to cause the UE to identify a set of symbols between the first and second SRS resources for a gap period.
Example A19 may include the one or more CRM of example A18, wherein the set of symbols for the gap period are predefined or configured via a message received from a next generation Node B (gNB).
Example A20 may include the one or more CRM of example A18, wherein the set of symbols immediately follows the first SRS resource or immediately precedes the second SRS resource.
Example A21 may include the one or more CRM of any of examples A14-A20, wherein the instructions, when executed, are further to cause the UE to perform collision handling for a gap period between the first and second SRS resources using a priority that is the same for the gap period as for one or both of the first and second SRS resources.
Example B1 may include a method of a gNB or UE, wherein the gNB configures the UE for SRS transmission.
Example B2 may include the method of example B1 or some other example herein, wherein when multiple aperiodic SRS resource sets are triggered to be transmitted in the same slot across different component carriers (CCs), if the simultaneous transmission over multiple CCs exceeds UE's capability, the dropping rule should be defined to handle the collision.
Example B3 may include the method of example B2 or some other example herein, wherein the SRS prioritization is based on SRS usage. If the collision happens among SRS with the same usage, then the SRS could be further prioritized by component carrier ID or SRS resource set ID.
Example B4 may include the method of example B2 or some other example herein, wherein the SRS prioritization is based on component carrier ID or the SRS prioritization is based on SRS resource set ID.
Example B5 may include the method of example B1 or some other example herein, wherein when aperiodic SRS triggered in one CC collides with periodic/semi-persistent SRS over another CC, if the simultaneous transmission over multiple CCs exceeds UE's capability, there should be some rules to handle the collision.
Example B6 may include the method of example B5 or some other example herein, wherein the aperiodic SRS should be prioritized over periodic/semi-persistent SRS or the periodic/semi-persistent SRS is prioritized over aperiodic SRS. Or the SRS prioritization is based on SRS usage. If the collision happens among SRS with the same usage, then the SRS could be further prioritized by component carrier ID or SRS resource set ID.
Example B7 may include the method of example B1 or some other example herein, wherein when periodic SRS in one CC collides with semi-persistent SRS over another CC, if the simultaneous transmission over multiple CCs exceeds UE's capability, there should be some rules to handle the collision.
Example B8 may include the method of example B7 or some other example herein, wherein the semi-persistent SRS should be prioritized over periodic SRS or the periodic SRS is prioritized over semi-persistent SRS. Or the SRS prioritization is based on SRS usage. If the collision happens among SRS with the same usage, then the SRS could be further prioritized by component carrier ID or SRS resource set ID.
Example B9 may include the method of example B1 or some other example herein, wherein new UE capability could be introduced indicating whether the UE supports simultaneous aperiodic SRS transmission over multiple CCs. Another UE capability could be introduced indicating whether UE supports simultaneous aperiodic SRS/periodic SRS/semi-persistent SRS transmission over multiple CCs.
Example B10 may include the method of example B1 or some other example herein, wherein if the UE doesn't support simultaneous transmission for aperiodic SRS over different CC, or simultaneous transmission for aperiodic and periodic/semi-persistent SRS over different CC, or simultaneous transmission for periodic and semi-persistent SRS over different CC, the UE is not expected to be configured with overlapped transmission.
Example B11 may include the method of example B1 or some other example herein, wherein for SRS with antenna switching, if the UE needs to switch antenna panel when transmitting the SRS resources within the same SRS resource set, additional guard period, for example, N symbols (N should be larger than or equal to the panel switching time), should be configured between the SRS resources.
Example B12 may include the method of example B1 or some other example herein, wherein for SRS with antenna switching, if the UE needs to switch antenna panel among different SRS resource sets, the guard period, for example, N symbols (N should be larger than or equal to the panel switching time), should be configured between the SRS resource sets.
Example B13 may include the method of example B1 or some or other example herein, wherein for SRS with antenna switching, if the SRS transmission is before or after other uplink transmission, e.g., PUSCH/PUCCH, and the UE needs to switch antenna/beam/panel between the SRS and PUSCH/PUCCH, the guard period, for example, N symbols (N should be larger than or equal to the beam/antenna/panel switching time), should be configured between the SRS and PUSCH/PUCCH.
Example B14 may include the method of example B1 or some other example herein, wherein for SRS with antenna switching, if the SRS transmission is before or after other uplink transmission, e.g., PUSCH/PUCCH, and the time between SRS and PUSCH/PUCCH is not sufficient for beam/antenna/panel switching, the collision handling should be applied.
Example B15 may include the method of example B14 or some other example herein, wherein the PUSCH/PUCCH should be prioritized for transmission. Some OFDM symbols for SRS transmission will be dropped. Or the SRS should be prioritized for transmission.
Example B16 may include a method of a UE, the method comprising: determining that multiple aperiodic SRS resource sets are triggered to be transmitted in a same slot across different component carriers (CCs); and dropping transmission of one or more of the SRS resource sets according to a dropping rule.
Example B17 may include the method of example B16 or some other example herein, where the transmission is dropped if simultaneous transmission of the multiple aperiodic SRS resource sets over multiple CCs exceeds a capability of the UE.
Example B18 may include the method of example B16-B17 or some other example herein, wherein the dropping rule includes prioritizing SRS resource sets based on SRS usage.
Example B19 may include the method of example B18 or some other example herein, wherein the SRS resource sets are prioritized further based on a component carrier ID or a SRS resource set ID.
Example B20 may include the method of example B16-B17 or some other example herein, wherein the dropping rule includes prioritizing SRS resource sets based on a component carrier ID or a SRS resource set ID.
Example B21 may include the method of example B16-B20 or some other example herein, wherein a time period between a first SRS resource and a second SRS resource is greater than a required gap length, and wherein the method further comprises determining OFDM symbols between the first and second SRS resources for a gap period.
Example B22 may include the method of example B21 or some other example herein, wherein the OFDM symbols for the gap period are predefined or configured (e.g., by RRC, MAC CE, and/or DCI).
Example B23 may include the method of example B21-B22 or some other example herein, wherein the determined OFDM symbols immediately follow the first SRS resource or immediately precede the second SRS resource.
Example B24 may include the method of example B21-B23 or some other example herein, further comprising performing collision handling using a priority handling rule for the gap period that is the same as a priority handling rule for a configured SRS.
Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples A1-A21, B1-B24, or any other method or process described herein.
Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples A1-A21, B1-B24, or any other method or process described herein.
Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples A1-A21, B1-B24, or any other method or process described herein.
Example Z04 may include a method, technique, or process as described in or related to any of examples A1-A21, B1-B24, or portions or parts thereof.
Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples A1-A21, B1-B24, or portions thereof.
Example Z06 may include a signal as described in or related to any of examples A1-A21, B1-B24, or portions or parts thereof.
Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples A1-A21, B1-B24, or portions or parts thereof, or otherwise described in the present disclosure.
Example Z08 may include a signal encoded with data as described in or related to any of examples A1-A21, B1-B24, or portions or parts thereof, or otherwise described in the present disclosure.
Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples A1-A21, B1-B24, or portions or parts thereof, or otherwise described in the present disclosure.
Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples A1-A21, B1-B24, or portions thereof.
Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples A1-A21, B1-B24, or portions thereof.
Example Z12 may include a signal in a wireless network as shown and described herein.
Example Z13 may include a method of communicating in a wireless network as shown and described herein.
Example Z14 may include a system for providing wireless communication as shown and described herein.
Example Z15 may include a device for providing wireless communication as shown and described herein.
Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 v 16.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.
For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.
The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.
The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.
The term “SSB” refers to an SS/PBCH block.
The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/.
The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.
| Number | Date | Country | Kind |
|---|---|---|---|
| PCT/CN2021/111196 | Aug 2021 | WO | international |
| PCT/CN2021/130947 | Nov 2021 | WO | international |
| PCT/CN2021/131456 | Nov 2021 | WO | international |
The present application claims priority to International Patent Application No. PCT/CN2021/111196, which was filed Aug. 6, 2021; International Patent Application No. PCT/CN2021/130947, which was filed Nov. 16, 2021; and to International Patent Application No. PCT/CN2021/131456, which was filed Nov. 18, 2021.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/US2022/039470 | 8/4/2022 | WO |
