WO2020139854A2

WO2020139854A2 - Protection of tolling systems from v2x spurious emissions

Info

Publication number: WO2020139854A2
Application number: PCT/US2019/068404
Authority: WO
Inventors: Markus Dominik MUECK; Leonardo Gomes Baltar
Original assignee: Intel Corporation
Priority date: 2018-12-27
Filing date: 2019-12-23
Publication date: 2020-07-02
Also published as: EP3903513A4; EP3903513A2; WO2020139854A3

Abstract

Systems, methods, and devices protect tolling systems from spurious emissions from vehicle-to-everything (V2X) communications. A V2X device may, for example, determine whether a maximum number of vehicles are to transmit using a wireless medium at a particular time. If less than the maximum number of vehicles are to transmit using the wireless medium at the particular time, the V2X device starts transmitting using the wireless medium at the particular time. If, however, the maximum number of vehicles are to transmit using the wireless medium at the particular time, the V2X device delays transmission until less than the maximum number of vehicles are transmitting.

Description

PROTECTION OF TOLLING SYSTEMS FROM V2X SPURIOUS EMISSIONS

CROSS-REFERENCE TO RELATED APPLICATIONS!

[0001] This application claims the benefit of U.S. Provisional Application No. 62/785,505, filed December 27, 2019, which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

[0002] This application relates generally to wireless communication systems, and more specifically to vehicular communications.

BACKGROUND

[0003] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device. Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide

interoperability for microwave access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLAN), which is commonly known to industry groups as Wi-Fi. In 3GPP radio access networks (RANs) in LTE systems, the base station can include a RAN Node such as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE). In fifth generation (5G) wireless RANs, RAN Nodes can include a 5G Node, new radio (NR) node or g Node B (gNB).

[0004] RANs use a radio access technology (RAT) to communicate between the RAN Node and UE. RANs can include global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN, which provide access to

communication services through a core network. Each of the RANs operates according to a specific 3GPP RAT. For example, the GERAN implements GSM and/or EDGE RAT, the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3 GPP RAT, and the E-UTRAN implements LTE RAT.

[0005] A core network can be connected to the UE through the RAN Node. The core network can include a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an access network detection and selection function (ANDSF) server, an enhanced packet data gateway (ePDG) and/or a mobility management entity (MME).

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0006] FIG. 1 illustrates an example spectrum allocation used with various embodiments.

[0007] FIG. 2 illustrates example systems used with certain embodiments.

[0008] FIG. 3 illustrates an example frame used in accordance with one embodiment.

[0009] FIG. 4 illustrates an example message sequence chart in accordance with one embodiment.

[0010] FIG. 5 illustrates an example frame used in accordance with one embodiment.

[0011] FIG. 6 illustrates an example message sequence chart in accordance with one embodiment.

[0012] FIG. 7 illustrates an example frame used in accordance with one embodiment.

[0013] FIG. 8 illustrates an example message sequence chart in accordance with one embodiment.

[0014] FIG. 9 illustrates an example frame used in accordance with one embodiment.

[0015] FIG. 10 illustrates an example message sequence chart in accordance with one embodiment.

[0016] FIG. 11 illustrates an example frame used in accordance with one embodiment.

[0017] FIG. 12 illustrates an example message sequence chart in accordance with one embodiment.

[0018] FIG. 13 illustrates an example frame used in accordance with one embodiment.

[0019] FIG. 14 illustrates an example message sequence chart in accordance with one embodiment.

[0020] FIG. 15 illustrates an example message sequence chart in accordance with one embodiment.

[0021] FIG. 16 illustrates a system in accordance with one embodiment.

[0022] FIG. 17 illustrates a device in accordance with one embodiment.

[0023] FIG. 18 illustrates example interfaces in accordance with one embodiment.

[0024] FIG. 19 illustrates components in accordance with one embodiment.

[0025] FIG. 20 illustrates a system in accordance with one embodiment.

[0026] FIG. 21 illustrates components in accordance with one embodiment. DETAILED DESCRIPTION

[0027] NAS level congestion control may be applied in general (i.e., for some or all NAS messages), per DNN, per S-NSSAI, per DNN and S-NSSAI, or for a specific group of UEs. "NAS" refers to Non-Access Stratum. "DNN" refers to Data Network Name. "S-NSSAI" refers to Single Network Slice Selection Assistance Information. The S-NSSAI is signaled by the UE to the network, and assists the network in selecting a particular Network Slice instance. An S-NSSAI includes: a Slice/Service type (SST), which refers to the expected Network Slice behavior in terms of features and services; and a Slice Differentiator (SD), which is an optional information that complements the Slice/Service type(s) to differentiate amongst multiple Network Slices of the same Slice/Service type. The S-NSSAI may be associated with a PLMN (e.g., PLMN ID) and have network-specific values or have standard values. An S-NSSAI is used by the UE in an access network in the PLMN that the S-NSSAI is associated with. "SST" refers to Slice/Service Type. "SD" refers to Slice Differentiator. "PLMN" refers to Public Land Mobile Network. "ID" refers to identifier.

[0028] NAS level congestion control is achieved by providing the UE a back-off time. To avoid that large numbers of UEs initiate deferred requests (almost) simultaneously, the 5GC may select each back-off time value so that the deferred requests are not synchronized. "5GC" refers to Fifth Generation Core network. When the UE receives a back-off time, the UE may not initiate any NAS signaling with regards to the applied congestion control until the back-off timer expires or the UE receives a mobile terminated request from the network, or the UE initiates signaling for emergency services or high priority access.

[0029] S-NSSAI based congestion control is for avoiding and handling of NAS signaling congestion for the UEs with a back-off time associated with or without an S-NSSAI, regardless of the presence of a DNN.

[0030] The UE associates the received back-off time with the S-NSSAI and DNN (i.e., no S-NSSAI and no DNN, no S-NSSAI, S-NSSAI only, an S-NSSAI and a DNN) which was included in an uplink NAS MM message carrying the corresponding NAS SM request message for the PLMN which is under congestion. "MM" refers to Mobility Management. "SM" refers to Session Management.

[0031] According to certain implantations, following are a few of the SMF and UE behaviors when an S-NSSAI (optionally with a DNN) is determined to be congested. "SMF" refers to Session Management Function. If an S-NSSAI is determined as congested, then the SMF may apply S-NSSAI based congestion control towards the UE for SM requests which includes an S-NSSAI, and provides a back-off time, an associated S-NSSAI, and optionally a DNN. Upon reception of a back-off time (or back-off time value) with an associated S- NSSAI and optionally a DNN, the UE takes the following actions: if the received back-off time is associated with an S-NSSAI only (i.e., not with a DNN) (e.g., timer T3585), the UE may not initiate any Session Management procedures for the congested S-NSSAI until the timer is stopped or expires; and if the received back-off time is associated with an S-NSSAI and a DNN (e.g., timer T3584), then the UE may not initiate any Session Management procedures for that combination of S-NSSAI and DNN until the timer is stopped or expires. This may apply, for example, on a per PLMN basis (i.e., not across PLMNs).

[0032] The AMF stores a DNN congestion back-off time on a per UE and congested DNN basis. "AMF" refers to Access and Mobility Management Function. The AMF stores an S- NSSAI congestion back-off time on a per UE, congested S-NSSAI, and optionally DNN basis.

[0033] Spurious emissions from vehicle-to-everything (V2X) communication may interfere with the operation of tolling systems. For example, FIG. 1 illustrates intelligent

transportation system (ITS) spectrum allocation 100 in Europe. For ITS safety related applications in Europe, a 30 MHz frequency band 102 is available split up into three channels of 10 MHz each. In the 5795-5815 MHz frequency band 104, however, tolling systems may operate using dedicated short-range communications (DSRC) or European Committee for Standardization (CEN) DSRC, which require specific protection from interference according to an original study focused on the ITS-G5 system (based on IEEE 802. l ip), where the name“G5” is derived from the 5 GHz frequency band. Now, however, 3GPP LTE cellular V2X (C-V2X) is an additional candidate system entering the band. Thus, it may be useful to maintain a sufficient protection of CEN DSRC from spurious emissions caused by LTE C-V2X.

[0034] ITS-G5 (IEEE 802.1 lp based) is a time division multiple access (TDMA) system based on a carrier sense multiple access with collision avoidance (CSMA/CA) distributed algorithm. For example, ITS-stations (e.g., UEs in mobile vehicles) may verify that the medium is idle for a certain period before attempting to transmit and, consequently, compete against each other for access to the channel. Preferably, only one single station has access granted during the time of its transmission. Afterwards, the process starts over, and a different station may then be granted access. Consequently, only one single station accesses the channel at a given point in time (it is the station which“won” the competition for channel access during a certain period). Interference of spurious emissions from ITS-G5 to CEN DSRC is thus typically the interference from one single transmitting station onto the CEN DSRC system. However, with a relatively low probability, collisions may happen wherein two or more stations access the channel at the same time. Nevertheless, for the matter of spurious emissions, those stations would need to be very close to each other, which significantly reduces the probability.

[0035] On the other hand, 3GPP LTE C-V2X is not a TDMA only based system. Rather, 3GPP LTE C-V2X provides time-frequency resource blocks (RBs), which may be shared among multiple ITS-stations. Therefore, multiple ITS-stations can access the channel simultaneously (on distinct RBs such that no collision occurs). Thus, the spurious emissions of multiple stations (transmitting simultaneously) may be aggregated and the instantaneous interference to CEN DSRC can be increased as compared to ITS-G5 systems. To alleviate the problem, some LTE C-V2X designs may introduce power spectral density (PSD) limit masks, which ensures that the spurious emissions of individual stations are limited.

[0036] By way of example, FIG. 2 illustrates generation of unwanted (spurious) emissions by an ITS-G5 system 202 and an LTE C-V2X system 204. In the ITS-G5 system 202, a first vehicle 206, a second vehicle 208, and a third vehicle 210 each occupy a full channel bandwidth 220 (10 MHz) at different times. Thus, spurious emissions from one single vehicle creates interference for a CEN DSRC System 212 at a given time. A study has shown that without mitigation techniques, ITS unwanted emissions of -65 dBm/MHz equivalent isotropically radiated power (EIRP) would protect a roadside unit (RSU) in all cases in an interference zone of the CEN DSRC System 212. Thus, with only one client (e.g., vehicle) transmitting at a given time, it is relatively straightforward to keep spurious emissions below -65 dBm/MHz at the CEN DSRC System 212.

[0037] For the LTE C-V2X system 204, however, a first vehicle 214, a second vehicle 216, and a third vehicle 218 may each access RBs or sub-channels of a frame 220 at the same time. In FIG. 2 (as well as FIG. 3, FIG. 5, FIG. 7, FIG. 9, FIG. 11, and FIG. 13), each of the rectangles in the frame 220 (i.e., three shown in the vertical (frequency) direction and eight shown in the horizontal (time) direction) may represent a resource block (RB) or a group of resource blocks in a sub-channel. Thus, unless specifically indicated otherwise, RBs and sub-channels may be used interchangeably herein. Further, skilled persons will recognize from the disclosure herein that the number of RBs or sub-channels shown for each frame is merely illustrative and that any number of RBs or sub-channels may be used (e.g., as may be defined by a particular standard).

[0038] In the example shown in FIG. 2, the first vehicle 214 and the third vehicle 218 each use respective RBs or sub-channels (groupings of RBs) that overlap in time. Thus, spurious emissions from multiple vehicles may create interference at a given time at the CEN DSRC System 212. According to a study, for the same average air time as for the ITS-G5 case, compatibility is assumed if in the context of two (or more) simultaneous transmissions by C- V2X within the interference zone, the system design is such that the aggregate spurious emission level is below -45 dBm/MHz.

[0039] For practical implementations, the LTE C-V2X solution is preferred because of the less restrictive limit for spurious emissions (-45 dBm/MHz limit for unwanted emissions). However, this limit is an aggregate limit of all simultaneous C-V2X emissions combined. The problem is complicated by the difficulty of predicting or controlling spurious emissions. For example, reducing transmission power by 3 dB does not necessarily reduce spurious emissions of each vehicle by 3 dB.

[0040] Embodiments herein provide an implementation solution to meet the aggregate limit (e.g., -45 dBm/MHz) for unwanted emissions (spurious emissions).“Aggregate” means that the unwanted (spurious) emissions of all simultaneously transmitting devices (typically accessing to distinct RBs) are combined.

[0041] The existing solution is to meet the highest level of protection, e.g., a spurious emission limit of -65 dBm/MHz. This is a per-device limit (and not an aggregate limit); i.e., any device meeting this requirements can access the channel without any further restrictions. The per-device spurious emission limit of -65 dBm/MHz can be extremely difficult and costly to meet. If such a solution is used, the cost per unit (of client devices / modem chipsets) may significantly increase.

[0042] Embodiments herein may provide a solution on how LTE C-V2X based ITS- stations can meet the aggregate spurious emission limit of -45 dBm/MHz. Thus, a lower complexity and cheaper implementation of modem chipsets is possible. Certain

embodiments limit the number of simultaneously accessing stations in a fully distributed system environment. As shown in FIG. 2, for LTE C-V2X, multiple vehicles (e.g., the first vehicle 214 and the third vehicle 218) access the wireless medium simultaneously but in distinct RBs or sub-channels. Note that the concept of an aggregate spurious interference level is challenging in a distributed (ad hoc) system, since there is no central controller which can take track of the overall usage of the resource.

[0043] Embodiments herein may include three LTE C-V2X modes: (A) Mode 4 in fully distributed mode, wherein vehicles apply peer-to-peer connections with no coordination from the road infrastructure (no vehicle-to-infrastructure (V2I)) and no access to a cellular network (no vehicle-to-network (V2N)); (B) Mode 4 with road infrastructure coordination, wherein vehicles apply peer-to-peer connections and also connections to the road infrastructure; and (C) Mode 3 with cellular network coordination, wherein signaling is done through a network link via cellular operator (V2N), but data is exchanged through peer-to- peer links.

(A) 3GPP LTE C-V2X Mode 4 solutions in fully distributed mode

[0044] In certain embodiments, mitigation techniques may be applicable within the interference zone or protection zone of CEN DSRC systems, i.e., in close proximity of CEN DSRC infrastructure. This is typically achieved through exploiting a-priori information on the location of CEN DSRC stations. In case the in-vehicle location system (e.g., global navigation satellite system (GNSS) based) identifies that the vehicle is entering the interference zone, then one of the embodiments below may be activated. There may be different mechanisms to detect the proximity to a CEN DSRC tolling station, including GNSS/location based, beaconing and radio signal strength.

[0045] (A)(1) Self-enforce that only a single vehicle accesses the medium within any given frame.

[0046] One embodiment includes self-enforcing that only a single vehicle accesses the medium within any given frame. For example, FIG. 3 illustrates a frame 300 that is accessed by only a single vehicle at any given time. As shown, a first vehicle 302 accesses RBs of the frame 300 at a first time, while a second vehicle 304 and a third vehicle 306 refrain from using the resources of the frame 300. At a later second time, either the second vehicle 304 or the third vehicle 306 may access the resources of the frame 300 while the other two vehicles (including the first vehicle 302) are not given access. To provide that only a single vehicle accesses the frame 300 at any given point in time, certain embodiments require vehicles and/or other devices in 3GPP LTE C-V2X to scan the medium for a predetermined period of time (e.g., 1 second) before self-allocating and accessing any resource blocks.

[0047] FIG. 4 illustrates an example message sequence chart wherein only a single vehicle accesses a medium at any given point in time. By way of example, a plurality of vehicles is shown, including a first vehicle 402, a second vehicle 404, a third vehicle 406... , and a Nth vehicle 408. In this example, the first vehicle 402 scans the medium for any C-V2X transmission for 1 second (Is), identifies the medium to be unused, and starts transmission. The second vehicle 404, the third vehicle 406... , and the Nth vehicle 408 scan the medium for any C-V2X transmission for Is, identify the medium as being used (e.g., by the first vehicle 402), and recheck the medium after some waiting time for any C-V2X transmission. As used herein, the waiting time may be a predetermined waiting time. Optionally, in certain embodiments, each vehicle may apply a random waiting time period within a pre-determined interval of a duration between“t low” time and“t high” time. A constant distribution may be applied to find a random waiting time that leads to a fairer distribution of access to the medium. A similar mechanism is applied in the CSMA/CA protocol used in IEEE 802. l ip.

[0048] With this approach, only a single vehicle is transmitting at any given instant in time and thus a per-vehicle requirement of -45 dBm/MHz spurious emission level is sufficient. There is no further aggregation of spurious emissions.

[0049] In certain embodiments, the vehicles can choose in this method if they will allocate all frequency resources or remain in specific chunks or sub-channels. An advantage of staying on chunks or sub-channels is to allow continuity after the protected zone is left.

[0050] (A)(2) Self-enforce that only a single vehicle accesses resource blocks at a given instant of time.

[0051] One embodiment includes self-enforcing that only a single vehicle is accessing RBs at a given instant of time, however different vehicles may use RBs in the same frame in non overlapping time instances. For example, FIG. 5 illustrates a frame 500 accessed by a first vehicle 502, a second vehicle 504, and a third vehicle 506, wherein only a single vehicle accesses respective RBs at any given point in time. In other words, the first vehicle 502, the second vehicle 504, and the third vehicle 506 do not access RBs within the frame 500 at the same time. The first vehicle 502 accesses respective RBs at first times, the second vehicle 504 accesses respective RBs at a second time, and the third vehicle accesses respective RBs at a third time.

[0052] FIG. 6 an example message sequence chart wherein only a single vehicle accesses a set of RBs at any given point in time. A first vehicle 602, a second vehicle 604, a third vehicle 606... , and an Nth vehicle 608 scan the medium for any C-V2X transmission for Is, identify that all RBs in a given time are unused, and starts transmission. In this example, there is an overlap in time for the transmissions. Typically, the transmissions do not start at the same time but in their duration they may overlap and collide. There may typically be a small number (e.g., two) of transmissions that collide, but not all of them.

[0053] In certain embodiments, if multiple instants of time have unused RBs, then a random selection of the time slot to be used is applied such that multiple vehicles (likely) will use distinct resources. There may be a residual probability that some vehicles will take the same RBs and thus collisions may occur. The same problem may occur for ITS-G5 when multiple vehicles compete for channel access. It is up to a station implementation to determine whether multiple signals can be received even if there are collisions.

[0054] With this approach, only a single vehicle is transmitting at any given instant in time and thus a per-vehicle requirement of -45 dBm/MHz spurious emission level is sufficient. There is no further aggregation of spurious emissions.

[0055] (A)(3) Self-enforce that only a limited number of vehicles may access a frame simultaneously.

[0056] One embodiment includes self-enforcing that only a limited number of vehicles (more than a single vehicle, e.g., 2 or 3 vehicles) may access a frame simultaneously. For example, FIG. 7 illustrates a frame 700 that is accessed by a maximum number of vehicles (in this example, two vehicles) at any given point in time. As shown, a first vehicle 702 accesses a first group of RBs and a second vehicle 704 access a second group of RBs at the same time. However, a third vehicle 706 is not allowed to access the frame 700 while both the first vehicle 702 and the second vehicle 704 access the frame 700. In certain

embodiments, a predetermined observation time (e.g., 1 second) may be used (e.g., as discussed above with respect to FIG. 3 and FIG. 4).

[0057] FIG. 8 illustrates an example message sequence chart wherein a predetermined maximum number of vehicles access a frame at a given time. In particular, in this example, only two vehicles may access the frame at the same time. A first vehicle 802 and a second vehicle 804 scan the medium for any C-V2X transmission for Is, identify that the frame is used by less than two vehicles, and start transmission. A third vehicle 806 and an Nth vehicle 808 scan the medium for any C-V2X transmission for Is, identify the frame is used by at least two vehicles (or greater than or equal to two vehicles) and re-check the medium after some waiting time to determine whether two vehicles are already using the frame. In certain embodiments, the number of users (e.g., vehicles) accessing the channel can be extracted from a control channel.

[0058] With this approach, only a limited number of vehicles transmits at any given instant in time and thus a per-vehicle requirement of -45 dBm/MHz spurious emission level is sufficient. There is no further aggregation of spurious emissions.

[0059] The effect on out of band / spurious emissions may depend on which resource blocks are actually used. Some resource blocks may create higher out of band /spurious emissions compared to others and vice versa. This is implementation dependent and may be different for each device. For example, the following embodiments may be considered. [0060] In one embodiment, in areas close to tolling stations (or other critical areas), only those resource blocks may be allocated to a specific device which create low out of band / spurious emissions. Alternatively, the level of spurious emissions is designed to remain below a certain threshold and the respective devices apply a resource pool (or other selection method for resource blocks) which ensures that the out of band / spurious emissions stay below the threshold.

[0061] In one embodiment, a hierarchy is calculated (typically for each mobile device type) identifying which resource pool identifier (ID) leads to the lowest out of band / spurious emissions, the second lowest, third lowest, etc. A certain number of the“best” resource pool IDs (i.e., that produce the lowest out of band / spurious emissions) are reserved for the vehicles in proximity to the tolling stations (or other critical areas) and the other resource pool IDs are used outside of the tolling station area.

[0062] In one embodiment, if vehicles are able to select such resource pool IDs that lead to ultra-low out of band / spurious emissions (or lead to out of band / spurious emissions below a given threshold), a larger number of vehicles (e.g., 2, 3, 4 or 5, etc.) may be allowed to transmit simultaneously in proximity to the tolling stations (or other critical areas). If only a higher threshold can be met, then the number of devices is reduced which may transmit simultaneously. In the extreme case, only a single device may be allowed to transmit at a time. In case that a given device type is overly“dirty” (i.e., creates too much out of band / spurious emissions), its usage may be prohibited or at least certain resource block configurations may be prohibited in the proximity of a tolling station (or other critical areas).

[0063] The above example embodiments may also apply to the other embodiments disclosed herein.

[0064] (A)(4) Self-enforce that only a limited number of vehicles may access resource blocks of a given point in time simultaneously.

[0065] One embodiment includes self-enforcing that only a limited number of vehicles (more than a single vehicle, e.g., 2 or 3 vehicles) may access RBs of a given point in time simultaneously. This embodiment does not necessarily limit the number of vehicles that may access a frame. Rather, the number of vehicles that may transmit at the same time is limited. For example, FIG. 9 illustrates a frame 900 that may be accessed by a first vehicle 902, a second vehicle 904, and a third vehicle 906. However, in this example, only two of the vehicles may access RBs in any given time instant. As shown, at a first time only the first vehicle 902 and the second vehicle 904 access respective RBs simultaneously, and at a second time only the second vehicle 904 and the third vehicle 906 access respective RBs simultaneously. In certain embodiments, a predetermined observation time (e.g., 1 second) may be used (e.g., as discussed above with respect to FIG. 3 and FIG. 4).

[0066] FIG. 10 illustrates an example message sequence chart wherein a maximum number of vehicles access RBs at a given time. In particular, in this example, only two vehicles may access respective RBs at the same time. A first vehicle 1002 and a second vehicle 1004 scan the medium for any C-V2X transmission for Is, identify that a given instant is used by less than two vehicles, and start transmission. A third vehicle 1006 and a Nth vehicle 1008 scan the medium for any C-V2X transmission for Is, identify that all instants (e.g., in the frame) is used by at least two vehicles (or greater than or equal to two vehicles) and re-check the medium after some waiting time to determine whether two vehicles are using all instants within the frame. In certain embodiments, the number of users (e.g., vehicles) accessing the channel can be extracted from a control channel.

[0067] With this approach, only a single vehicle is transmitting at any given instant in time and thus a per-vehicle requirement of -45 dBm/MHz spurious emission level is sufficient. There is no further aggregation of spurious emissions.

[0068] (A)(5) Self-enforce that only a limited number of vehicles may access resource blocks of a given point in time simultaneously with location analysis.

[0069] One embodiment includes self-enforcing that only a limited number of vehicles (more than a single vehicle, e.g. 2, 3 or more vehicles) may access RBs of a given point in time simultaneously with location analysis. Vehicle location is one of the fundamental types of information that is exchanged in V2X communications. Thus, certain embodiments assume that each received message includes the location information about the transmitter. The location and resources utilized by other vehicles are then available for each vehicle. After or during the scanning of the medium for Is, the vehicles analyze the location of other vehicles and avoid simultaneous transmissions with others in close proximity. A dynamic threshold to the inter-vehicle distance for simultaneous transmission is set depending on the distance to the tolling station. Accordingly, a very efficient use of the spectrum may be achieved.

[0070] FIG. 11 illustrates a frame 1100 wherein vehicles in close proximity to one another and to a tolling station avoid simultaneous transmissions. As shown, when a first vehicle 1102 and a second vehicle 1104 determine that they are within close proximity to one another and to a tolling station, the first vehicle 1102 and the second vehicle 1104 do not use RBs in the frame 1100 that overlap in time. The second vehicle 1104 may determine that it is sufficiently far away from a third vehicle 1106 and/or that the third vehicle is sufficiently far away from the tolling station so as to not add to interference at the tolling station due spurious emissions from the second vehicle 1104. Thus, the second vehicle 1104 and the third vehicle 1106 access RBs in the frame 1100 that overlap in time.

[0071] FIG. 12 illustrates an example message sequence chart wherein a maximum number of vehicles are allowed to access RBs of a given point in time after analyzing the location of the other vehicles. In particular, in this example, only two vehicles may access RBs that overlap in time based on vehicle location information. A first vehicle 1202 and a second vehicle 1204 scan the medium for any C-V2X transmission for Is and analyze the locations of other vehicles. Based on the location information, the first vehicle 1202 and a second vehicle 1204 identify that a given instant in time is used by less than two vehicles in proximity to a tolling station. The first vehicle 1202 and a second vehicle 1204 then start C- V2X transmission. A third vehicle 1206 and a Nth vehicle 1208 also scan the medium for any C-V2X transmission for Is and analyze the locations of other vehicles. However, the third vehicle 1206 and the Nth vehicle 1208 identify that all instants within a frame are used by at least two nearby vehicles (or greater than or equal to two nearby vehicles) and re check the medium after some waiting time.

[0072] (A)(6) Self-enforce the use of specific resources for specific sub-areas inside the protected zone (sub-zoning).

[0073] One embodiment includes self-enforcing the use of specific resources for specific sub-areas inside the protected zone. Such embodiments may be referred to herein as sub zoning. Mobile ITS-stations possess or may dynamically download maps of the protected zone where specific time-frequency resource pools are defined and preconfigured for each sub-area of the protected zone. The mapping of resource pools and sub-areas may be defined in a way that stations transmitting simultaneously are geographically distant one another resulting in negligible aggregated interference.

[0074] FIG. 13 illustrates a frame 1300 wherein vehicles in the same preconfigured sub- area avoid simultaneous transmissions. As shown, a first vehicle 1302 and a second vehicle 1304 in a first sub-area 1306 do not use RBs in the frame 1300 that overlap in time.

However, the second vehicle 1304 in the first sub-area 1306 and a third vehicle 1308 in a second sub-area 1310 access RBs in the frame 1300 that overlap in time.

[0075] FIG. 14 illustrates an example message sequence chart wherein a maximum number of vehicles are allowed to access RBs of a given point in time only if they are located in separate pre-configured sub-areas. In particular, in this example, only two vehicles within the same sub-area may access RBs that overlap in time. A first vehicle 1402 scans the medium for any C-V2X transmission for Is only on RBs mapped to a first sub-area, identifies that a given instant in time is to be used by less than two vehicles, and starts transmission. A second vehicle 1404 scans the medium for any C-V2X transmission for Is only on RBs mapped to a second sub-area, identifies that a given instant in time is to be used by less than two vehicles, and starts transmission. A third vehicle 1406 scans the medium for any C-V2X transmission for Is only on RBs mapped to the first sub-area, identifies that all instants are to be used by at least two vehicles (or greater than or equal to two vehicles) nearby (i.e., in the first sub-area), and re-checks the medium after some waiting time. An Nth vehicle 1408 scans the medium for any C-V2X transmission for Is only on RBs mapped to the second sub-area, identifies that all instants are to be used by at least two vehicles (or greater than or equal to two vehicles) nearby (i.e., in the second sub- area), and re-checks the medium after some waiting time.

(B) 3GPP LTE C-V2X Mode 4 solutions with road infrastructure coordination

[0076] In certain embodiments, a fixed ITS-station, which may or may not be associated and connected to the CEN DSRC tolling station, can transmit a specific message informing whether and which of the five methods described in section (A) should be adopted by approaching mobile ITS-stations. Moreover, other specific messages may provide a preferred and specific allocation scheme. For example, an indication of a specific allocation scheme may be based on a dependence on distance to the tolling station for vehicles in the same lane or sub-zoning inside of the protected zone with reserved resources for each sub zone, similar to the embodiment described in section (A)(6) but dynamically controlled by the fixed ITS station.

[0077] For example, FIG. 15 illustrates a message sequence chart where an RSU 1502 broadcasts an allocation message. In this example, the allocation method broadcast by the RSU 1502 indicates to a first vehicle 1504, a second vehicle 1506, a third vehicle 1508... , and a Nth vehicle 1510 to use the embodiment described herein in section (A)(1), i.e., to self-enforce that only a single vehicle may access the medium within any given time frame. Thus, the first vehicle 1504 receives the allocation method broadcast by the RSU 1502, scans the medium for any C-V2X transmission for Is, identifies the medium to be unused, and starts transmission. The second vehicle 1506, the third vehicle 1508... , and the Nth vehicle 1510 receive the allocation method broadcast by the RSU 1502, scan the medium for any C-V2X transmission for Is, identify the medium as being used (e.g., by the first vehicle 1502), and recheck the medium after some waiting time for any C-V2X transmission.

[0078] In an analogous way, the allocation methods described herein in sections (A)(2) to

(A)(6) can be employed. In the case of method (A)(6), for example, the RSU message may also provide the configuration of the sub-area of the protected zone.

(C) 3GPP LTE C-V2X Mode 3 solutions with mobile network coordination

[0079] In certain embodiments, a mobile network infrastructure has full control of the time-frequency resources. The mobile network can provide any of the allocations described herein in section (A), with the advantage that mobile ITS-stations do not need to sense the medium before transmitting and do not make any decision on which resource to transmit. The mobile network has full access of the full picture and can provide a very flexible and dynamic scheduling of the resources. Moreover, the mobile network may also have connection to the road infrastructure and to the tolling infrastructure, which provides even more information for the scheduling decisions.

[0080] In certain embodiments, the decision of whether the mobile network will allow or will not allow simultaneous transmissions of multiple mobile stations may depend on availability of information about the position of the mobile station and of the tolling station. For example, there may be different possibilities if the vehicles report to the base station information about their location. Mobile stations may also report position of other stations, including fixed ones, to the base station.

(D) Mixed scenario with 3 GPP LTE C-V2X Mode 3 and 4 solutions

[0081] It is also possible that even in areas with coverage of a mobile network, some vehicles are operation in the Mode 4. Those vehicles may use one of the autonomous modes of operation or also be configured by a roadside infrastructure as described herein in section

(B). In such embodiments, the base station may or may not communicate with the roadside infrastructure.

[0082] In certain embodiments, if the base station does not communicate with the roadside infrastructure, the base station may receive information about the medium usage via reporting by the mobile ITS-stations.

[0083] In certain embodiments, when the base station has information about the medium, the base station can dynamically or semi-statically allocate the resources. [0084] In certain embodiments, if the base station does not have information about the medium, a separation of resources has to exist between stations in Modes 3 and 4.

[0085] Example radio technologies

[0086] Any of the embodiments described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3 GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3 GPP Long Term Evolution (LTE), 3 GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit- Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access

(HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division-Synchronous Code Division Multiple Access (TD- CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel. 19, etc ), 3 GPP 5G, 5G, 5G New Radio (5G NR), 3 GPP 5G New Radio, 3 GPP LTE Extra, LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System/Extended Total Access Communication System (TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), ARP

(Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handy-phone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. l lad, IEEE 802.1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802. l ip and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to- Vehicle (12 V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range

Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European ITS-G5 system (i.e. the European flavor of IEEE 802. l ip based DSRC, including ITS-G5A (i.e., Operation of ITS- G5 in European ITS frequency bands dedicated to ITS for safety related applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz) etc.

[0087] Aspects described herein can be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, license exempt spectrum, (licensed) shared spectrum (such as LSA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizen Broadband Radio System in 3.55-3.7 GHz and further

frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300 220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note:

allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (l lb/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, 3400 - 3800 MHz, 3.55-3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio Service), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for example in EU (ETSI EN 301 893)), 5.47-5.65 GHz (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under

consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57- 64/66 GHz (note: this band has near-global designation for Multi-Gigabit Wireless Systems (MGWS WiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[0088] Aspects described herein can also implement a hierarchical application of the scheme is possible, e.g., by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.

[0089] Aspects described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC),

OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0090] Some of the features described herein are defined for the network side, such as Access Points, eNodeBs, New Radio (NR) or next generation Node Bs (gNodeB or gNB - note that this term is typically used in the context of 3GPP fifth generation (5G)

communication systems), etc. Still, a UE may take this role as well and act as an Access Point, eNodeB, gNodeB, etc. Fe., some or all features defined for network equipment may be implemented by a UE.

[0091] Example Systems and Apparatuses

[0092] FIG. 16 illustrates an architecture of a system 1600 of a network in accordance with some embodiments. The system 1600 is shown to include a UE 1602; a 5G access node or RAN node (shown as (R)AN node 1608); a User Plane Function (shown as UPF 1604); a Data Network (DN 1606), which may be, for example, operator services, Internet access or 3rd party services; and a 5G Core Network (5GC) (shown as CN 1610).

[0093] The CN 1610 may include an Authentication Server Function (AUSF 1614); a Core Access and Mobility Management Function (AMF 1612); a Session Management Function (SMF 1618); a Network Exposure Function (NEF 1616); a Policy Control Function (PCF 1622); a Network Function (NF) Repository Function (NRF 1620); a Unified Data

Management (UDM 1624); and an Application Function (AF 1626). The CN 1610 may also include other elements that are not shown, such as a Structured Data Storage network function (SDSF), an Unstructured Data Storage network function (UDSF), and the like.

[0094] The UPF 1604 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN 1606, and a branching point to support multi -homed PDU session. The UPF 1604 may also perform packet routing and forwarding, packet inspection, enforce user plane part of policy rules, lawfully intercept packets (UP collection); traffic usage reporting, perform QoS handling for 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 downlink packet buffering and downlink data notification triggering. UPF 1604 may include an uplink classifier to support routing traffic flows to a data network. The DN 1606 may represent various network operator services, Internet access, or third party services.

[0095] The AUSF 1614 may store data for authentication of UE 1602 and handle authentication related functionality. The AUSF 1614 may facilitate a common

authentication framework for various access types.

[0096] The AMF 1612 may be responsible for registration management (e.g., for registering UE 1602, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. AMF 1612 may provide transport for SM messages for the SMF 1618, and act as a transparent proxy for routing SM messages. AMF 1612 may also provide transport for short message service (SMS) messages between UE 1602 and an SMS function (SMSF) (not shown by FIG. 16). AMF 1612 may act as Security Anchor Function (SEA), which may include interaction with the AUSF 1614 and the UE 1602, receipt of an intermediate key that was established as a result of the UE 1602 authentication process. Where USIM based authentication is used, the AMF 1612 may retrieve the security material from the AUSF 1614. AMF 1612 may also include a Security Context Management (SCM) function, which receives a key from the SEA that it uses to derive access-network specific

keys. Furthermore, AMF 1612 may be a termination point of RAN CP interface (N2 reference point), a termination point of NAS (NI) signaling, and perform NAS ciphering and integrity protection.

[0097] AMF 1612 may also support NAS signaling with a UE 1602 over an N3

interworking -function (IWF) interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 and N3 interfaces for control plane and user plane, respectively, and as such, may handle N2 signaling from SMF and AMF for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated to such marking received over N2. N3IWF may also relay uplink and downlink control-plane NAS (NI) signaling between the UE 1602 and AMF 1612, and relay uplink and downlink user-plane packets between the UE 1602 and UPF 1604. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 1602.

[0098] The SMF 1618 may be responsible for session management (e.g., session

establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation & management (including optional Authorization); Selection and control of UP function; Configures traffic steering at UPF to route traffic to proper destination; termination of interfaces towards Policy control functions; control part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI System);

termination of SM parts of NAS messages; downlink Data Notification; initiator of AN specific SM information, sent via AMF over N2 to AN; determine SSC mode of a session. The SMF 1618 may include the following roaming functionality: handle local enforcement to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI System); support for interaction with external DN for transport of signaling for PDU session

authorization/authentication by external DN.

[0099] The NEF 1616 may provide means for securely exposing the services and capabilities provided by 3 GPP network functions for third party, internal exposure/re exposure, Application Functions (e.g., AF 1626), edge computing or fog

computing systems, etc. In such embodiments, the NEF 1616 may authenticate, authorize, and/or throttle the AFs. NEF 1616 may also translate information exchanged with the AF 1626 and information exchanged with internal network functions. For example, the NEF 1616 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 1616 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 1616 as structured data, or at a data storage NF using a standardized

interfaces. The stored information can then be re-exposed by the NEF 1616 to other NFs and AFs, and/or used for other purposes such as analytics.

[0100] The NRF 1620 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 1620 also maintains information of available NF instances and their supported services.

[0101] The PCF 1622 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behavior. The PCF 1622 may also implement a front end (FE) to access subscription information relevant for policy decisions in a UDR of UDM 1624.

[0102] The UDM 1624 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE

1602. The UDM 1624 may include two parts, an application FE and a User Data Repository (UDR). The UDM may include a UDM FE, which is in charge of processing of 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. The UDR may interact with PCF 1622 . UDM 1624 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously.

[0103] The AF 1626 may provide application influence on traffic routing, access to the Network Capability Exposure (NCE), and interact with the policy framework for policy control. The NCE may be a mechanism that allows the 5GC and AF 1626 to provide information to each other via NEF 1616, which may be used for edge computing

implementations. In such implementations, the network operator and third party services may be hosted close to the UE 1602 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF 1604 close to the UE 1602 and execute traffic steering from the UPF 1604 to DN 1606 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1626. In this way, the AF 1626 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1626 is considered to be a trusted entity, the network operator may permit AF 1626 to interact directly with relevant NFs.

[0104] As discussed previously, the CN 1610 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 1602 to/from other entities, such as an SMS-GMSC/IWMSC/SMS- router. The SMS may also interact with AMF 1612 and UDM 1624 for notification procedure that the UE 1602 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 1624 when UE 1602 is available for SMS).

[0105] The system 1600 may include the following service-based interfaces: Namf:

Service-based interface exhibited by AMF; Nsmf: Service-based interface exhibited by SMF; Nnef: Service-based interface exhibited by NEF;

Npcf: Service-based interface exhibited by PCF; Nudm: Service-based interface exhibited by UDM; Naf: Service-based interface exhibited by AF; Nnrf: Service-based interface exhibited by NRF; and Nausf: Service-based interface exhibited by AUSF.

[0106] The system 1600 may include the following reference points: Nl : Reference point between the UE and the AMF; N2: Reference point between the (R)AN and the AMF; N3 : Reference point between the (R)AN and the UPF; N4: Reference point between the SMF and the UPF; and N6: Reference point between the UPF and a Data Network. There may be many more reference points and/or service-based interfaces between the NF services in the NFs, however, these interfaces and reference points have been omitted for clarity. For example, an NS reference point may be between the PCF and the AF; an N7 reference point may be between the PCF and the SMF; an Nl 1 reference point between the AMF and SMF; etc. In some embodiments, the CN 1610 may include an Nx interface, which is an inter-CN interface between the MME (e.g., MME(s) 1914) and the AMF 1612 in order to enable interworking between CN 1610 and CN 1906.

[0107] Although not shown by FIG. 16, the system 1600 may include multiple RAN nodes (such as (R)AN node 1608) wherein an Xn interface is defined between two or more (R)AN node 1608 (e.g., gNBs and the like) that connecting to 5GC 410, between a (R)AN node 1608 (e.g., gNB) connecting to CN 1610 and an eNB, and/or between two eNBs connecting to CN 1610.

[0108] In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 1602 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more (R)AN node 1608. The mobility support may include context transfer from an old (source) serving (R)AN node 1608 to new (target) serving (R)AN node 1608; and control of user plane tunnels between old (source) serving (R)AN node 1608 to new (target) serving (R)AN node 1608.

[0109] A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on an SCTP layer. The SCTP layer may be on top of an IP layer. The SCTP layer provides the guaranteed delivery of application layer messages. In the transport IP layer point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

[0110] FIG. 17 illustrates example components of a device 1700 in accordance with some embodiments. In some embodiments, the device 1700 may include application circuitry 1702, baseband circuitry 1704, Radio Frequency (RF) circuitry (shown as RF circuitry 1720), front-end module (FEM) circuitry (shown as FEM circuitry 1730), one or more antennas 1732, and power management circuitry (PMC) (shown as PMC 1734) coupled together at least as shown. The components of the illustrated device 1700 may be included in a UE or a RAN node. In some embodiments, the device 1700 may include fewer elements (e.g., a RAN node may not utilize application circuitry 1702, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 1700 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

[0111] The application circuitry 1702 may include one or more application processors. For example, the application circuitry 1702 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any

combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 1700. In some embodiments, processors of application circuitry 1702 may process IP data packets received from an EPC.

[0112] The baseband circuitry 1704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1704 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1720 and to generate baseband signals for a transmit signal path of the RF circuitry 1720. The baseband circuitry 1704 may interface with the application circuitry 1702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1720. For example, in some embodiments, the baseband circuitry 1704 may include a third generation (3G) baseband processor (3G baseband processor 1706), a fourth generation (4G) baseband processor (4G baseband processor 1708), a fifth generation (5G) baseband processor (5G baseband processor 1710), or other baseband processor(s) 1712 for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 1704 (e.g., one or more of baseband processors) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1720. In other embodiments, some or all of the functionality of the illustrated baseband processors may be included in modules stored in the memory 1718 and executed via a Central Processing Unit (CPU 1714). The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 1704 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1704 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder

functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0113] In some embodiments, the baseband circuitry 1704 may include a digital signal processor (DSP), such as one or more audio DSP(s) 1716. The one or more audio DSP(s) 1716 may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 1704 and the application circuitry 1702 may be implemented together such as, for example, on a system on a chip (SOC).

[0114] In some embodiments, the baseband circuitry 1704 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1704 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), or a wireless personal area network

(WPAN). Embodiments in which the baseband circuitry 1704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0115] The RF circuitry 1720 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1720 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. The RF circuitry 1720 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1730 and provide baseband signals to the baseband circuitry 1704. The RF circuitry 1720 may also include a transmit signal path which may include circuitry to up- convert baseband signals provided by the baseband circuitry 1704 and provide RF output signals to the FEM circuitry 1730 for transmission.

[0116] In some embodiments, the receive signal path of the RF circuitry 1720 may include mixer circuitry 1722, amplifier circuitry 1724 and filter circuitry 1726. In some

embodiments, the transmit signal path of the RF circuitry 1720 may include filter circuitry 1726 and mixer circuitry 1722. The RF circuitry 1720 may also include synthesizer circuitry 1728 for synthesizing a frequency for use by the mixer circuitry 1722 of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1722 of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1730 based on the synthesized frequency provided by synthesizer circuitry 1728. The amplifier circuitry 1724 may be configured to amplify the down- converted signals and the filter circuitry 1726 may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 1704 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, the mixer circuitry 1722 of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0117] In some embodiments, the mixer circuitry 1722 of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1728 to generate RF output signals for the FEM circuitry 1730. The baseband signals may be provided by the baseband circuitry 1704 and may be filtered by the filter circuitry 1726.

[0118] In some embodiments, the mixer circuitry 1722 of the receive signal path and the mixer circuitry 1722 of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 1722 of the receive signal path and the mixer circuitry 1722 of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1722 of the receive signal path and the mixer circuitry 1722 may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 1722 of the receive signal path and the mixer circuitry 1722 of the transmit signal path may be configured for super-heterodyne operation.

[0119] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 1720 may include analog-to-digital converter (ADC) and digital -to-analog converter (DAC) circuitry and the baseband circuitry 1704 may include a digital baseband interface to communicate with the RF circuitry 1720.

[0120] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0121] In some embodiments, the synthesizer circuitry 1728 may be a fractional -N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1728 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0122] The synthesizer circuitry 1728 may be configured to synthesize an output frequency for use by the mixer circuitry 1722 of the RF circuitry 1720 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1728 may be a fractional N/N+l synthesizer.

[0123] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 1704 or the application circuitry 1702 (such as an applications processor) depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 1702. [0124] Synthesizer circuitry 1728 of the RF circuitry 1720 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these

embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0125] In some embodiments, the synthesizer circuitry 1728 may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 1720 may include an IQ/polar converter.

[0126] The FEM circuitry 1730 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1732, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1720 for further processing. The FEM circuitry 1730 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1720 for transmission by one or more of the one or more antennas 1732. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1720, solely in the FEM circuitry 1730, or in both the RF circuitry 1720 and the FEM circuitry 1730.

[0127] In some embodiments, the FEM circuitry 1730 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry 1730 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 1730 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1720). The transmit signal path of the FEM circuitry 1730 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry 1720), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1732).

[0128] In some embodiments, the PMC 1734 may manage power provided to the baseband circuitry 1704. In particular, the PMC 1734 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 1734 may often be included when the device 1700 is capable of being powered by a battery, for example, when the device 1700 is included in a UE. The PMC 1734 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation

characteristics.

[0129] FIG. 17 shows the PMC 1734 coupled only with the baseband circuitry 1704.

However, in other embodiments, the PMC 1734 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry 1702, the RF circuitry 1720, or the FEM circuitry 1730.

[0130] In some embodiments, the PMC 1734 may control, or otherwise be part of, various power saving mechanisms of the device 1700. For example, if the device 1700 is in an RRC Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 1700 may power down for brief intervals of time and thus save power.

[0131] If there is no data traffic activity for an extended period of time, then the device 1700 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1700 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 1700 may not receive data in this state, and in order to receive data, it transitions back to an

RRC Connected state.

[0132] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few

hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable. [0133] Processors of the application circuitry 1702 and processors of the baseband circuitry 1704 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 1704, alone or in combination, may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 1702 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[0134] FIG. 18 illustrates example interfaces 1800 of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 1704 of FIG. 17 may comprise 3G baseband processor 1706, 4G baseband processor 1708, 5G baseband processor 1710, other baseband processor(s) 1712, CPU 1714, and a memory 1718 utilized by said processors. As illustrated, each of the processors may include a respective memory interface 1802 to send/receive data to/from the memory 1718.

[0135] The baseband circuitry 1704 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1804 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1704), an application circuitry interface 1806 (e.g., an interface to send/receive data to/from the application circuitry 1702 of FIG. 17), an RF circuitry interface 1808 (e.g., an interface to send/receive data to/from RF circuitry 1720 of FIG. 17), a wireless hardware connectivity interface 1810 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 1812 (e.g., an interface to send/receive power or control signals to/from the PMC 1734.

[0136] FIG. 19 illustrates components 1900 of a core network in accordance with some embodiments. The components of the CN 1906 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, Network Functions Virtualization (NFV) is utilized to virtualize any or all of the above described network node functions via executable instructions stored in one or more computer readable storage mediums (described in further detail below). A logical instantiation of the CN 1906 may be referred to as a network slice 1902 (e.g., the network slice 1902 is shown to include the HSS 1908, the MME(s) 1914, and the S-GW 1912). A logical instantiation of a portion of the CN 1906 may be referred to as a network sub-slice 1904 (e.g., the network sub-slice 1904 is shown to include the P-GW 1916 and the PCRF 1910).

[0137] NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

[0138] FIG. 20 is a block diagram illustrating components, according to some example embodiments, of a system 2000 to support NFV. The system 2000 is illustrated as including a virtualized infrastructure manager (shown as VIM 2002), a network function virtualization infrastructure (shown as NFVI 2004), a VNF manager (shown as VNFM 2006), virtualized network functions (shown as VNF 2008), an element manager (shown as EM 2010), an NFV Orchestrator (shown as NFVO 2012), and a network manager (shown as NM 2014).

[0139] The VIM 2002 manages the resources of the NFVI 2004. The NFVI 2004 can include physical or virtual resources and applications (including hypervisors) used to execute the system 2000. The VIM 2002 may manage the life cycle of virtual resources with the NFVI 2004 (e.g., creation, maintenance, and tear down of virtual machines (VMs) associated with one or more physical resources), track VM instances, track performance, fault and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

[0140] The VNFM 2006 may manage the VNF 2008. The VNF 2008 may be used to execute EPC components/functions. The VNFM 2006 may manage the life cycle of the VNF 2008 and track performance, fault and security of the virtual aspects of VNF

2008. The EM 2010 may track the performance, fault and security of the functional aspects of VNF 2008. The tracking data from the VNFM 2006 and the EM 2010 may comprise, for example, performance measurement (PM) data used by the VIM 2002 or the NFVI

2004. Both the VNFM 2006 and the EM 2010 can scale up/down the quantity of VNFs of the system 2000.

[0141] The NFVO 2012 may coordinate, authorize, release and engage resources of the NFVI 2004 in order to provide the requested service (e.g., to execute an EPC function, component, or slice). The NM 2014 may provide a package of end-user functions with the responsibility for the management of a network, which may include network elements with VNFs, non-virtualized network functions, or both (management of the VNFs may occur via the EM 2010).

[0142] FIG. 21 is a block diagram illustrating components 2100, according to some example embodiments, able to read instructions from a machine-readable or computer- readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 21 shows a diagrammatic representation of hardware resources 2102 including one or more processors 2112 (or processor cores), one or more memory/storage devices 2118, and one or more communication resources 2120, each of which may be communicatively coupled via a bus 2122. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 2104 may be executed to provide an execution environment for one or more network slices/sub- slices to utilize the hardware resources 2102.

[0143] The processors 2112 (e.g., 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 digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 2114 and a processor 2116.

[0144] The memory/storage devices 2118 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 2118 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM),

Flash memory, solid-state storage, etc.

[0145] The communication resources 2120 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 2106 or one or more databases 2108 via a network 2110. For example, the communication resources 2120 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components. [0146] Instructions 2124 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 21 12 to perform any one or more of the methodologies discussed herein. The instructions 2124 may reside, completely or partially, within at least one of the processors 21 12 (e.g., within the processor’s cache memory), the memory/storage devices 21 18, or any suitable combination thereof. Furthermore, any portion of the instructions 2124 may be transferred to the hardware resources 2102 from any combination of the peripheral devices 2106 or the databases 2108. Accordingly, the memory of the processors 21 12, the memory/storage devices 21 18, the peripheral devices 2106, and the databases 2108 are examples of computer-readable and machine-readable media.

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

[0148] Example Section

[0149] The following examples pertain to further embodiments.

[0150] Example 1 is an apparatus including a memory interface and a processor. The memory interface to send or receive, to or from a memory device, a value corresponding to a maximum number of vehicles. The processor to: determine whether the maximum number of vehicles are to transmit using a wireless medium at a first time; if less than the maximum number of vehicles are to transmit using the wireless medium at the first time, start a transmission using the wireless medium at the first time; and if at least the maximum number of vehicles are to transmit using the wireless medium at the first time, delay transmission using the wireless medium until a second time.

[0151] Example 2 includes the apparatus of Example 1, wherein to determine whether the maximum number of vehicles are to transmit using the wireless medium at the first time comprises to: determine that the V2X UE has entered a protection zone of a tolling station; and in response to determining that the V2X UE has entered the protection zone of the tolling station, set a limit on the maximum number of vehicles allowed to transmit at a same time.

[0152] Example 3 includes the apparatus of Example 2, wherein the tolling station comprises a dedicated short-range communications (DSRC) station.

[0153] Example 4 includes the apparatus of Example 2, wherein the processor is further configured to: analyze vehicle location information to determine first distances between the V2X UE and other vehicles; determine one or more nearby vehicles that are within a threshold distance to the V2X UE; and include only the nearby vehicles to determine whether the maximum number of vehicles are to transmit using the wireless medium at the first time.

[0154] Example 5 includes the apparatus of Example 4, wherein the processor is further configured to dynamically adjust the threshold distance based on a second distance between the V2X UE and the tolling station.

[0155] Example 6 includes the apparatus of Example 4, wherein the processor is further configured to process a message from a roadside unit (RSEi), the message comprising the threshold distance.

[0156] Example 7 includes the apparatus of Example 2, wherein different resource pools are defined and preconfigured for respective sub-areas of the protection zone, and wherein the processor is further configured to: determine that the V2X UE is within a first sub-area of the protection zone; include one or more first vehicles in the first sub-area of the protection zone to determine whether the maximum number of vehicles are to transmit using the wireless medium at the first time; and exclude one or more second vehicles in a second sub-area of the protection zone to determine whether the maximum number of vehicles are to transmit using the wireless medium at the first time.

[0157] Example 8 includes the apparatus of Example 7, wherein the processor is further configured to process a message from a roadside unit (RSEI), the message comprising configuration information for the first sub-area of the protection zone.

[0158] Example 9 includes the apparatus of Example 1, wherein the processor is further configured to process a broadcast message from a roadside unit (RSEI), the broadcast message comprising an indication of a resource allocation method.

[0159] Example 10 includes the apparatus of any one of Example 1 to Example 9, wherein to determine whether the maximum number of vehicles are to transmit using the wireless medium at the first time, the processor is further configured to: scan the wireless medium for cellular V2X transmissions for a first period of time; and based on the scan, determine whether the wireless medium is used or unused.

[0160] Example 11 includes the apparatus of Example 10, wherein the wireless medium comprises a frame including a plurality of resources, wherein the maximum number of vehicles comprises a single vehicle allowed to access the frame at a given time. The processor is further configured to: if the wireless medium is unused, start the transmission using one or more of the plurality of resources of the frame; and if the wireless medium is used, wait for a second period of time before re-scanning the wireless medium to determine whether the wireless medium is used or unused.

[0161] Example 12 includes the apparatus of Example 10, wherein the wireless medium comprises a frame including sub-channels comprising a plurality of resource blocks (RBs), wherein the maximum number of vehicles comprises a single vehicle allowed to access one or more of the sub-channels or the plurality of RBs at a given time within the frame, and wherein the processor is further configured to: if the one or more of the sub-channels or the plurality of RBs are unused at the first time, start the transmission using the one or more of the sub-channels or the plurality of RBs at the first time within the frame; and if the one or more of the sub-channels or the plurality of RBs are used at the first time, start the transmission using the one or more of the sub-channels or the plurality of RBs at the second time within the frame.

[0162] Example 13 includes the apparatus of Example 10, wherein the wireless medium comprises a frame including a plurality of resources, wherein the maximum number of vehicles comprises a predetermined number of vehicles allowed to access the frame at a given time, and wherein the processor is further configured to: if the frame is identified to be used by less than the predetermined number of vehicles, start the transmission using one or more of the plurality of resources of the frame; and if the frame is identified to be used by at least the predetermined number of vehicles, wait for a second period of time before re scanning the wireless medium to determine whether the wireless medium is used or unused.

[0163] Example 14 includes the apparatus of Example 10, wherein the wireless medium comprises a frame including sub-channels comprising a plurality of resource blocks (RBs), wherein the maximum number of vehicles comprises a predetermined number of vehicles allowed to access one or more of the sub-channels or the plurality of RBs at a given time within the frame, and wherein the processor is further configured to: if the one or more of the sub-channels or the plurality of RBs are identified to be used by less than the

predetermined number of vehicles at the first time, start the transmission using the one or more of the sub-channels or the plurality of RBs at the first time within the frame; and if the one or more of the sub-channels or the plurality of RBs are identified to be used by at least the predetermined number of vehicles at the first time, start the transmission using the one or more of the sub-channels or the plurality of RBs at the second time within the frame.

[0164] Example 15 includes the apparatus of Example 14, wherein the processor is further configured to: if the one or more of the sub-channels or the plurality of RBs are identified to be used by at least the predetermined number of vehicles at all time instants within the frame, wait for a second period of time before re-scanning the wireless medium to determine whether the wireless medium is used or unused.

[0165] Example 16 is a non-transitory computer-readable storage medium. The computer- readable storage medium includes instructions that when executed by a processor in a wireless network, cause the processor to: determine a number of vehicle-to-everything (V2X) devices within a protection zone of a tolling station; and dynamically allocate resources to limit the number of V2X devices that simultaneously transmit within the protection zone.

[0166] Example 17 includes the computer-readable storage medium of Example 16, the instructions further to: process a message from a first V2X device, the message comprising location information; and determine the number of V2X devices within the protection zone based on the location information.

[0167] Example 18 includes the computer-readable storage medium of Example 16, wherein the location information indicates a location of at least one of the first V2X device, one or more second V2X device, a roadside unit (RSEi), the protection zone, and the tolling station.

[0168] Example 19 includes the computer-readable storage medium of any one of Example 16 to Example 18, the instructions further to: process a message from roadside

infrastructure, the message comprising information corresponding to a wireless medium for V2X communication; and determine the number of V2X devices within the protection zone based on the information corresponding to the wireless medium.

[0169] Example 20 includes the computer-readable storage medium of Example 16, the instructions further to: configure a first pool of resources for use by a first set of V2X devices and a second pool of resources for use by a second set of V2X devices, wherein to dynamically allocate the resources comprises to dynamically allocate the first pool of resources for the first set of V2X devices, and wherein the second set of V2X devices are configured for autonomous use of the second pool of resources.

[0170] Example 21 includes the computer-readable storage medium of Example 16, the instructions further to: broadcast a message to the second set of devices, the message comprising an indication of a resource allocation method for the autonomous use of the second pool of resources.

[0171] Example 22 includes the computer-readable storage medium of Example 16, wherein the tolling station comprises a dedicated short-range communications (DSRC) station.

[0172] Example 23 includes the computer-readable storage medium of Example 16, wherein to dynamically allocate the resources is based on a threshold distance between V2X devices in the protection zone.

[0173] Example 24 includes the computer-readable storage medium of Example 16, the instructions further to: dynamically change the threshold distance between V2X devices based on a distance between the tolling station and the V2X devices.

[0174] Example 25 includes the computer-readable storage medium of Example 16, wherein to dynamically allocate the resources is based on locations of respective V2X devices within sub-areas of the protection zone.

[0175] Example 26 includes the computer-readable storage medium of Example 16, wherein to dynamically allocate the resources is based on allowing a single V2X device to access a frame at a given time.

[0176] Example 27 includes the computer-readable storage medium of Example 16, wherein to dynamically allocate the resources is based on allowing a single V2X device to access one or more sub-channels or resource blocks (RBs) at a given time within a frame.

[0177] Example 28 includes the computer-readable storage medium of Example 16, wherein to dynamically allocate the resources is based on allowing two or more V2X devices to access a frame at a given time.

[0178] Example 29 includes the computer-readable storage medium of Example 16, wherein to dynamically allocate the resources is based on allowing two or more V2X devices to access one or more sub-channels or plurality of resource blocks (RBs) at a given time within a frame.

[0179] Example 30 is a method for mobile communications. The method includes:

calculating a hierarchy of resource pool identifiers based on lowest to highest out of band or spurious emissions produced by mobiles devices when using respective resources of the resource pool identifiers; and reserving one or more first resource pool identifiers of the hierarchy producing the lowest out of band or spurious emissions for use by one or more of the mobile devices when operating within a protection zone.

[0180] Example 31 includes the method of Example 30, wherein calculating the hierarchy comprises determining a different hierarchy for each of a plurality of different mobile device types.

[0181] Example 32 includes the method of Example 30, further comprising using one or more second resource pool identifiers of the hierarchy outside of the protection zone, the one or more second resource pool identifiers being different than the one or more first resource pool identifiers.

[0182] Example 33 includes the method of any of Examples 30-32, wherein the protection zone corresponds to a geographic area in proximity to a tolling station.

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

[0184] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general- purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.

[0185] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters/attributes/aspects/etc. of one embodiment can be used in another embodiment. The parameters/attributes/aspects/etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters/attributes/aspects/etc. can be combined with or substituted for

parameters/attributes/etc. of another embodiment unless specifically disclaimed herein. [0186] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of

implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. An apparatus, the apparatus comprising:

a memory interface to send or receive, to or from a memory device, a value corresponding to a maximum number of vehicles; and

a processor to:

determine whether the maximum number of vehicles are to transmit using a wireless medium at a first time;

if less than the maximum number of vehicles are to transmit using the wireless medium at the first time, start a transmission using the wireless medium at the first time; and

if at least the maximum number of vehicles are to transmit using the wireless medium at the first time, delay transmission using the wireless medium until a second time.

2. The apparatus of claim 1, wherein to determine whether the maximum number of vehicles are to transmit using the wireless medium at the first time comprises to:

determine that the V2X UE has entered a protection zone of a tolling station; and in response to determining that the V2X UE has entered the protection zone of the tolling station, set a limit on the maximum number of vehicles allowed to transmit at a same time.

3. The apparatus of claim 2, wherein the tolling station comprises a dedicated short-range communications (DSRC) station.

4. The apparatus of claim 2, wherein the processor is further configured to:

analyze vehicle location information to determine first distances between the V2X UE and other vehicles;

determine one or more nearby vehicles that are within a threshold distance to the V2X UE; and

include only the nearby vehicles to determine whether the maximum number of vehicles are to transmit using the wireless medium at the first time.

5. The apparatus of claim 4, wherein the processor is further configured to dynamically adjust the threshold distance based on a second distance between the V2X UE and the tolling station.

6. The apparatus of claim 4, wherein the processor is further configured to process a message from a roadside unit (RSU), the message comprising the threshold distance.

7. The apparatus of claim 2, wherein different resource pools are defined and preconfigured for respective sub-areas of the protection zone, and wherein the processor is further configured to:

determine that the V2X UE is within a first sub-area of the protection zone;

include one or more first vehicles in the first sub-area of the protection zone to determine whether the maximum number of vehicles are to transmit using the wireless medium at the first time; and

exclude one or more second vehicles in a second sub-area of the protection zone to determine whether the maximum number of vehicles are to transmit using the wireless medium at the first time.

8. The apparatus of claim 7, wherein the processor is further configured to process a message from a roadside unit (RSU), the message comprising configuration information for the first sub-area of the protection zone.

9. The apparatus of claim 1, wherein the processor is further configured to process a broadcast message from a roadside unit (RSU), the broadcast message comprising an indication of a resource allocation method.

10. The apparatus of any one of claim 1 to claim 9, wherein to determine whether the maximum number of vehicles are to transmit using the wireless medium at the first time, the processor is further configured to:

scan the wireless medium for cellular V2X transmissions for a first period of time; and

based on the scan, determine whether the wireless medium is used or unused.

11. The apparatus of claim 10, wherein the wireless medium comprises a frame including a plurality of resources, wherein the maximum number of vehicles comprises a single vehicle allowed to access the frame at a given time, and wherein the processor is further configured to:

if the wireless medium is unused, start the transmission using one or more of the plurality of resources of the frame; and if the wireless medium is used, wait for a second period of time before re-scanning the wireless medium to determine whether the wireless medium is used or unused.

12. The apparatus of claim 10, wherein the wireless medium comprises a frame including sub-channels comprising a plurality of resource blocks (RBs), wherein the maximum number of vehicles comprises a single vehicle allowed to access one or more of the sub channels or the plurality of RBs at a given time within the frame, and wherein the processor is further configured to:

if the one or more of the sub-channels or the plurality of RBs are unused at the first time, start the transmission using the one or more of the sub-channels or the plurality of RBs at the first time within the frame; and

if the one or more of the sub-channels or the plurality of RBs are used at the first time, start the transmission using the one or more of the sub-channels or the plurality of RBs at the second time within the frame.

13. The apparatus of claim 10, wherein the wireless medium comprises a frame including a plurality of resources, wherein the maximum number of vehicles comprises a predetermined number of vehicles allowed to access the frame at a given time, and wherein the processor is further configured to:

if the frame is identified to be used by less than the predetermined number of vehicles, start the transmission using one or more of the plurality of resources of the frame; and

if the frame is identified to be used by at least the predetermined number of vehicles, wait for a second period of time before re-scanning the wireless medium to determine whether the wireless medium is used or unused.

14. The apparatus of claim 10, wherein the wireless medium comprises a frame including sub-channels comprising a plurality of resource blocks (RBs), wherein the maximum number of vehicles comprises a predetermined number of vehicles allowed to access one or more of the sub-channels or the plurality of RBs at a given time within the frame, and wherein the processor is further configured to:

if the one or more of the sub-channels or the plurality of RBs are identified to be used by less than the predetermined number of vehicles at the first time, start the

transmission using the one or more of the sub-channels or the plurality of RBs at the first time within the frame; and if the one or more of the sub-channels or the plurality of RBs are identified to be used by at least the predetermined number of vehicles at the first time, start the transmission using the one or more of the sub-channels or the plurality of RBs at the second time within the frame.

15. The apparatus of claim 14, wherein the processor is further configured to:

if the one or more of the sub-channels or the plurality of RBs are identified to be used by at least the predetermined number of vehicles at all time instants within the frame, wait for a second period of time before re-scanning the wireless medium to determine whether the wireless medium is used or unused.

16. A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a processor in a wireless network, cause the processor to:

determine a number of vehicle-to-everything (V2X) devices within a protection zone of a tolling station; and

dynamically allocate resources to limit the number of V2X devices that

simultaneously transmit within the protection zone.

17. The computer-readable storage medium of claim 16, the instructions further to:

process a message from a first V2X device, the message comprising location information; and

determine the number of V2X devices within the protection zone based on the location information.

18. The computer-readable storage medium of claim 16, wherein the location information indicates a location of at least one of the first V2X device, one or more second V2X device, a roadside unit (RSU), the protection zone, and the tolling station.

19. The computer-readable storage medium of any one of claim 16 to claim 18, the instructions further to:

process a message from roadside infrastructure, the message comprising information corresponding to a wireless medium for V2X communication; and

determine the number of V2X devices within the protection zone based on the information corresponding to the wireless medium.

20. The computer-readable storage medium of claim 16, the instructions further to: configure a first pool of resources for use by a first set of V2X devices and a second pool of resources for use by a second set of V2X devices,

wherein to dynamically allocate the resources comprises to dynamically allocate the first pool of resources for the first set of V2X devices, and

wherein the second set of V2X devices are configured for autonomous use of the second pool of resources.

21. The computer-readable storage medium of claim 16, the instructions further to:

broadcast a message to the second set of devices, the message comprising an indication of a resource allocation method for the autonomous use of the second pool of resources.

22. The computer-readable storage medium of claim 16, wherein the tolling station comprises a dedicated short-range communications (DSRC) station.

23. The computer-readable storage medium of claim 16, wherein to dynamically allocate the resources is based on a threshold distance between V2X devices in the protection zone.

24. The computer-readable storage medium of claim 16, the instructions further to:

dynamically change the threshold distance between V2X devices based on a distance between the tolling station and the V2X devices.

25. The computer-readable storage medium of claim 16, wherein to dynamically allocate the resources is based on locations of respective V2X devices within sub-areas of the protection zone.

26. The computer-readable storage medium of claim 16, wherein to dynamically allocate the resources is based on allowing a single V2X device to access a frame at a given time.

27. The computer-readable storage medium of claim 16, wherein to dynamically allocate the resources is based on allowing a single V2X device to access one or more sub-channels or resource blocks (RBs) at a given time within a frame.

28. The computer-readable storage medium of claim 16, wherein to dynamically allocate the resources is based on allowing two or more V2X devices to access a frame at a given time.

29. The computer-readable storage medium of claim 16, wherein to dynamically allocate the resources is based on allowing two or more V2X devices to access one or more sub-channels or plurality of resource blocks (RBs) at a given time within a frame.

30. A method for mobile communications, the method comprising:

calculating a hierarchy of resource pool identifiers based on lowest to highest out of band or spurious emissions produced by mobiles devices when using respective resources of the resource pool identifiers; and

reserving one or more first resource pool identifiers of the hierarchy producing the lowest out of band or spurious emissions for use by one or more of the mobile devices when operating within a protection zone.

31. The method of claim 30, wherein calculating the hierarchy comprises determining a different hierarchy for each of a plurality of different mobile device types.

32. The method of claim 30, further comprising using one or more second resource pool identifiers of the hierarchy outside of the protection zone, the one or more second resource pool identifiers being different than the one or more first resource pool identifiers.

33. The method of any of claims 30-32, wherein the protection zone corresponds to a geographic area in proximity to a tolling station.